Volumes: Small virtual filesystems that may be attached to the Users running/active Instances.
Files/data saved to a Volume are maintained across successive attachment/detachment actions to the User's Instances.
Volume actions with the Atmosphere interface:
Volumes can also be controlled directly from the OpenStack API.
REMINDER: Volumes can only be detached if:
- they are not in active use by a process on the instance
- fuser -m /<volume> to LIST all processes using a volume
- You might also try sudo fuser -m /volume if nothing comes up – this will check for root processes holding the volume open
- fuser -km /<volume> to KILL all processes using a volume
- If you get results with sudo above, you'll need to do sudo fuser -km /<volume> to kill the processes
- the instance to which they are attached is active
Cost and Size:
While Volumes are available to facilitate research at no additional Service Unit charge, and may be requested during initial or supplemental Jetstream allocation requests, large capacity storage is beyond the scope of Jetstream.
Users who have been approved for Volumes are limited to 10 volumes with an aggregate capacity of 100 GB by default.
Project and Providers:
As with Instances, Volumes are associated/organized with User Projects and with particular Providers (e.g. IU or TACC).
(i.e. you cannot attach a Volume from one Provider to an instance on a different Provider.)
Volumes may only be attached to one active Instance at a time.
Volumes may be shared using standard methods (e.g. NFS) to other active Instances within Jetstream.
Backup & Exporting:
Users should regularly backup (via ssh, rsync, tar, or the like) any critical data contained on Volumes as no automated backup functions are currently provided by Jetstream.