need ability to snapshot python client logfile

[hppritcha]

need ability to snapshot python client logfile

[rhc54]

I'm a little puzzled here. The Python client includes a resource manager plugin - e.g., Slurm. That plugin has the ability to request an allocation in it. The intent was that the Python client would not need to be started from within an allocation, but would instead execute its initial operations (fetching and building things) and then request an allocation when one was needed for actually running the tests.

The only issue we have encountered with that method is that the allocation request can take some time to be granted. Our internal solution was to simply create a high-priority queue for MTT operations and submit the request to it.

Is this not adequate for ECP systems? If not, note that the Python client already has a C/R capability in that you can have one ini file that downloads and builds things, and another ini file that flags the download/build components with ASIS to indicate that MTT is to use the existing installations if present. Does that not also solve the problem?

[hppritcha]

I don't see how this would work with the current IU database reporter. Anyway I've written the code and it appears to serve my purposes.

[rhc54]

You are welcome to use your code - however, the methods I described work just fine with the current IU reporter. We use it every day precisely that way. The builds are reported correctly even if previously built.

[ribab]

Hi @hppritcha , I am trying to understand your use-case and how it differs from ours. Your process allocates the cluster from a compute node? How does this work?

You said:

the requesting process is typically put on some compute node

This means the process that requested an allocation runs on a compute node? Don't you need an allocation before running anything on a compute node?

[hppritcha]

@ribab one invokes the allocation command from a front end node - the one you get placed on when you ssh to the system. For example with the ANL theta cluster, here's how you'd get an allocation:

ssh theta
XXX@thetalogin6:qsub -n 8 --jobname ompi -q debug-flat-quad -t 60 -I

upon granting the allocation, the user is placed on one of the internal mom nodes on theta. Then one uses aprun or mpirun to launch the application.

A similar thing occurs on SLURM configured systems like NERSC cori. One can try using the salloc --no-shell option to remain on one of the cori login nodes, but we've found that option to be unreliable for running many tests like we do in MTT.

The only way I can see how one might use MTT ALPS plugin on theta would be for the allocate command to include the name of a script which would somehow continue the MTT run on the backend mom node. The front end process running the ALPS plugin up to that point would be disconnected with whatever was going on in the backend.

The way the MTT SLURM and ALPS plugins are written, I suspect systems configured similar to some of Cray's internal systems were being used. There, SLURM is configured so that when one does an salloc, one remains on the front end nodes, not ssh'd into a compute or mom node on the backend. In this case, the plugins as is with their allocate/deallocate commands should work fine. PBS was similarly configured on those systems.

[hppritcha]

closed via #916