Cray's burst buffer API, and Slurm's code to support it are still
evolving. Once that is stable, we plan to backport the
burst_buffer/cray plugin to burst_buffer/generic and restore it's
operation.
Quoting Ulf Markwardt <[email protected]>:
Dear Slurm developers,
I left the SLUG meeting with the strong impression in mind that generic
burst buffers are a piece of cake and extremely useful for us since we
run a shared file system based on SSDs.
We now are using the SchedMD example scripts in a test environment. But
it is not really clear how a user should work with the burst buffer:
I start an interactive job using the example
srun --bb="capacity=1G access=striped type=scratch" a.out
Bute then I see no used resources:
scontrol.test show burst
Name=generic DefaultPool=(null) Granularity=1 TotalSpace=1000G
UsedSpace=0...
How can I now use this scratch buffer associated with the job.
Is there anybody around who can help us with the first steps, or tell us
his/her configuration and a working example? The documentation on the web
is a little sparse in this respect.
Thank you,
Ulf
--
___________________________________________________________________
Dr. Ulf Markwardt
Technische Universität Dresden
Center for Information Services and High Performance Computing (ZIH)
01062 Dresden, Germany
Phone: (+49) 351/463-33640 WWW: http://www.tu-dresden.de/zih
