Changes between Version 29 and Version 30 of User Guide/Disk Images

Timestamp:

Feb 10, 2026, 10:59:59 PM (4 days ago)

Author:

jennyshane

Comment:

—

User Guide/Disk Images

@@ -4 +4 @@
 === Summary
 
-The imaging process is executed by the commands 'omf load' and 'omf save'
-
-These provision a full disk image onto a set of nodes, and should work for any ext2/3/4 filesystem.
-
-After saving an image from one node, and loading it onto another, it will appear to the user that a copy of the hard disk has been made. Specifically, this is a block based copy, not a file based one.
-
-The baseline image is a recommended starting point, as this provisioning tool does not currently work with standard .iso or similar files, instead using a custom compressed .ndz format.
+Disk images are deployed on testbed machines using 'omf load' and generated from testbed machines using 'omf save'.
+
+The load command provisions a full disk image onto a set of nodes, and should work for any ext2/ext3/ext4 filesystem.
+
+After saving an image from one node and loading it onto another, the contents of the hard disk on the new node will be the same as the old one, except for files generated by the OS to reference system hardware. The copying process is block-based, not file-based.
+
+All testbed users will need to start with one of a number of "baseline" images that have been pre-built. These images are .ndz files. Machines in the Cosmos testbed can only use baseline images or disk image files that have been created with 'omf save'.
 
 === Working with Image files
 These images are loaded and saved using [wiki:UserGuide/OmfQuickStart OMF commands].
 
-Saved images can be seen in the directory `/export/omf-images-5.4/` on the Consoles.
+Saved images can be seen in the directory `/mnt/images/` on the Consoles.
 
 [[Include(UserGuide/Omf/SaveImage#files)]]