Changes between Initial Version and Version 1 of User Guide/Portal/Disk Images


Ignore:
Timestamp:
Mar 30, 2026, 5:54:05 PM (6 hours ago)
Author:
editor
Comment:

New: Disk Images sub-page

Legend:

Unmodified
Added
Removed
Modified
  • User Guide/Portal/Disk Images

    v1 v1  
     1[[Include(WikiToC)]]
     2= Disk Images =
     3
     4The Disk Images page in the COSMOS Portal lets you browse, search, and manage the testbed's library of disk images. Disk images (`.ndz` files) are compressed snapshots of a node's hard drive that can be loaded onto testbed nodes using the `omf load` command. The image library includes baseline images maintained by the testbed administrators, shared images from other users, and your own custom images saved with `omf save`.
     5
     6Access the Disk Images page from the '''Disk Images''' link in the portal sidebar. This page is available to all authenticated users.
     7
     8----
     9
     10== Browsing Images ==
     11
     12The Disk Images page organizes images into three tabs:
     13
     14=== My Images ===
     15
     16Shows images that you own — images you saved using `omf save` or images that have been assigned to you by an administrator. For each image, you see:
     17
     18* '''Image name''' — the `.ndz` filename (e.g., `jsmith-node1-1.sb1.cosmos-lab.org-2026-03-15.ndz`)
     19* '''Description''' — a human-readable description (if set)
     20* '''Size''' — the compressed image size on disk
     21* '''Created''' — when the image was saved
     22* '''Visibility''' — whether the image is public (available to all users) or private (only you can see it)
     23
     24=== Public Images ===
     25
     26Shows images that other users have marked as public, making them available for anyone to load. This is where you find shared experiment images, specialized configurations, and community-contributed setups. Public images are read-only — you cannot modify or delete another user's image, but you can load it onto your reserved nodes.
     27
     28=== All Images ===
     29
     30Shows the complete image library including your private images, all public images, and (for administrators) all images across all users. This tab is useful for finding images by name or description when you are not sure who owns them.
     31
     32----
     33
     34== Image Details ==
     35
     36Each image entry displays the following information:
     37
     38||= Field =||= Description =||
     39|| '''Name''' || The filename of the `.ndz` disk image ||
     40|| '''Owner''' || The username of the person who saved the image ||
     41|| '''Group''' || The Linux group the image belongs to (affects visibility) ||
     42|| '''Size''' || Compressed image size in megabytes or gigabytes ||
     43|| '''Description''' || Human-readable text describing the image contents, software installed, and intended use ||
     44|| '''Created''' || Date the image was saved ||
     45|| '''Public''' || Whether the image is readable by all users or restricted to the owner/group ||
     46
     47----
     48
     49== Searching and Sorting ==
     50
     51The image table supports:
     52
     53* '''Text search''' — type in the search box to filter images by name or description. The filter applies in real time as you type.
     54* '''Column sorting''' — click any column header (Name, Description, Size, Created) to sort the table. Click again to reverse the sort order.
     55* '''Pagination''' — images are displayed 25 per page with navigation controls at the top and bottom of the table.
     56
     57----
     58
     59== Managing Your Images ==
     60
     61For images you own, you can perform these operations:
     62
     63=== Setting Visibility ===
     64
     65By default, newly saved images are '''private''' — only you can see them. To share an image with other users:
     66
     671. Find the image in the '''My Images''' tab
     682. Click on the image to expand its details
     693. Toggle the '''Public''' switch to make it visible to everyone
     70
     71Making an image public means any authenticated user can see it in the '''Public Images''' tab and load it onto their reserved nodes using `omf load -i <imagename>`. They cannot modify or delete your image.
     72
     73To make a public image private again, toggle the switch off. The image immediately disappears from other users' Public Images view.
     74
     75=== Deleting Images ===
     76
     77To delete an image you own:
     78
     791. Click on the image to expand its details
     802. Click the '''Delete''' button
     813. Confirm the deletion in the dialog
     82
     83'''Warning:''' Deletion is permanent. The image file is removed from the testbed storage and cannot be recovered. Make sure you have a backup if you might need the image again.
     84
     85You can only delete images you own. Administrators can delete any image.
     86
     87----
     88
     89== Baseline Images ==
     90
     91The testbed provides several baseline images maintained by the administrators. These are available to all users and serve as starting points for experiments:
     92
     93||= Image Name =||= Description =||
     94|| `baseline.ndz` || Ubuntu-based image with basic testbed tools pre-installed (OMF resource controller, SSH access, network configuration). This is the recommended starting point for most experiments. ||
     95|| `baseline-uhd.ndz` || Baseline image with UHD (USRP Hardware Driver) pre-installed for software-defined radio experiments with USRP devices. ||
     96|| `baseline-gr.ndz` || Baseline image with UHD and GNU Radio pre-installed for SDR signal processing experiments. ||
     97
     98When you load a baseline image, nodes are configured with:
     99* Root SSH access from the testbed internal networks (your console server can reach the nodes)
     100* Network interfaces configured via DHCP for the testbed management network
     101* The `omf` resource controller (RC) which handles imaging and power management commands
     102* Standard development tools (gcc, make, python, etc.)
     103
     104To load a baseline image onto all nodes in your reservation:
     105{{{
     106omf load -t all -i baseline.ndz
     107}}}
     108
     109For detailed information about loading and saving images, see the [wiki:UserGuide/OmfQuickStart OMF Quick Start Guide].
     110
     111----
     112
     113== Saving Custom Images ==
     114
     115After installing software, configuring services, or setting up your experiment environment on a testbed node, you can save the node's disk as a custom image using `omf save`. Your saved image appears in the '''My Images''' tab and can be loaded onto the same or different nodes in future experiments.
     116
     117The basic workflow is:
     118
     1191. Load a baseline image and boot the node
     1202. SSH into the node and install/configure your software
     1213. Save the customized disk: `omf save <node>`
     1224. The image is automatically named `<username>-<hostname>-<timestamp>.ndz` and stored on the testbed
     123
     124For detailed save instructions and options, see the [wiki:UserGuide/OmfQuickStart OMF Quick Start Guide].
     125
     126----
     127
     128== Storage and Retention ==
     129
     130Disk images are stored on NFS-mounted storage accessible from all console servers at `/mnt/images/`. Image sizes vary depending on how much of the disk is used — the `omf save` command automatically shrinks the partition to minimize the compressed image size.
     131
     132There is currently no automatic image expiration policy. However, if storage space becomes constrained, administrators may contact users with very large or very old images to discuss cleanup. Good practice is to periodically review your '''My Images''' tab and delete images you no longer need.