diff --git a/www/beginexp.php3 b/www/beginexp.php3 index 759d2ad2329012d5ce687507ef1b90abaee1a51d..773da9250a8ef4f8347e338cd295c87f2377053b 100644 --- a/www/beginexp.php3 +++ b/www/beginexp.php3 @@ -356,7 +356,7 @@ function SPITFORM($formfields, $errors) file first!
  • You can view a list of OSIDs that are available for you to use in your NS file. -
  • Create your own +
  • Create your own custom disk images. \n"; diff --git a/www/newimageid.php3 b/www/newimageid.php3 index 0c267f32828cde5a78775e6ff484c601031b5a93..f354b2d8a0f0e378957312b0c7209b7285dfd288 100644 --- a/www/newimageid.php3 +++ b/www/newimageid.php3 @@ -1,7 +1,7 @@ - -

    -This page will allow you to create your own custom disk image, -described by what we call an Image Descriptor. An Image Descriptor -indicates what operating system is contained in the image, what DOS -partition (or "slice" in BSD-speak) the image goes in, where the -image data file should be stored on disk, etc. Once you have created -the description, you can create the image from a node in one of your -experiments, and then load that image on other nodes (say, in a new -experiment). The image data file is in a compressed format that can be -quickly and easily loaded onto a node, or onto a group of nodes all at -the same time. - -

    -The most common approach is to use the New Image Descriptor form to create -a disk image that contains a customized version of the standard Redhat -Linux partition or the FreeBSD partition. Or, you can start from -scratch and load your own operating system in any of the DOS -partitions, and then capture that partition when you are done. Either -way, all you need to do is enter the node name in the form, and the -testbed system will create the image for you automatically, notifying -you via email when it is finished. You can then use that image in -subsequent experiments by specifying the descriptor name in your NS -file with the - -tb-set-node-os directive. When the experiment is -configured, the proper image will be loaded on each node automatically by -the Testbed system. - -

    -There is a -list of descriptors that -have already been created in your project (and are available for you -to use in your experiments). - -long form.\n"; -} -?> - -

    -If you already have an Image Descriptor defined, and you want to -create a new version of the image using a node that is allocated in -one of your experiments and setup the way you want it, use the -create_image command. Log into users and run: - - 

    -	create_image -p <pid> <imageid> <node>
    - -This will reboot your node and create the new image, writing it to the -filename specified in the descriptor. This program is going exit -immediately and then send you email about 5-10 minutes later, after -the image is finished. In the meantime you should not do anything to -your node. Log out and leave it alone. If you do not get email, its -possible that the node froze up on reboot, which happens -sometimes. Let us know if you do not receive notification in a -reasonable amount of time. - -

    -If you ever want to reload a node in your experiment, either with one -of your images or with one of the default images, you can use the -os_load command. Log into users and run: - - 

    -	os_load -p <pid> -i <imageid> <node>
    - -This program will run in the foreground, waiting until the image has -been loaded. At that point you should log in and make sure everything -is working oaky. You might want to watch the console line as well (see -the FAQ). If you want to load the default image, then simply run: - - 
    -	os_load <node>
    - - diff --git a/www/newimageid_ez.php3 b/www/newimageid_ez.php3 index cd7b891b0ead2cb089b2780fe46e4405bd1de24b..e4f2edc6b630091aa426a860057cd415ddb8083b 100644 --- a/www/newimageid_ez.php3 +++ b/www/newimageid_ez.php3 @@ -74,6 +74,19 @@ function SPITFORM($formfields, $errors) $featurelist; global $TBDB_IMAGEID_IMAGENAMELEN, $TBDB_NODEIDLEN; global $TBDB_OSID_VERSLEN, $TBBASE; + + echo "
    + See the + + tutorial for more info on creating/using custom Images. +
    \n"; + + if ($isadmin) { + echo "
    + Administrators get to use the + long form. +
    \n"; + } if ($errors) { echo " @@ -103,7 +103,7 @@ a disk image of the node in question, and later reloading it to a new node after you swap in again. Disk images in effect create a "custom OS" that can be loaded automatically based on your NS file. More information about disk images can be found on our Disk Image +href="https://www.emulab.net/newimageid_ez.php3"> Disk Image page (you must be logged in to use it). We are currently working on a system that will allow you to save disk images from all the nodes in your experiment at swapout time, and reload them automatically when diff --git a/www/tutorial/tutorial.html b/www/tutorial/tutorial.html index 286caa300d726139456f8c9f3726be7f29620713..d92d212f612bb23bcd6fa47b65aab658cbd37ce4 100644 --- a/www/tutorial/tutorial.html +++ b/www/tutorial/tutorial.html @@ -1072,7 +1072,7 @@ file. Emulab allows you to create your own disk images and load them on your experimental nodes, automatically when your experiment is created or swapped in. Once you have created a custom disk image (and the -associated +associated image/osid descriptor for it, you can use that OSID in your NS file. When your experiment is swapped in, the testbed system will arrange for your disks to be loaded in parallel using a locally @@ -1083,18 +1083,18 @@ it may seem like overkill to create your own disk image, we can assure you it is not!

    -The most common approach is to use the New Image Descriptor form to create -a disk image that contains a customized version of the standard Redhat -Linux partition or the FreeBSD partition. Or, you can start from -scratch and load your own operating system in any of the DOS -partitions, and then capture that partition when you are done. Either -way, all you need to do is enter the node name in the form, and the -testbed system will create the image for you automatically, notifying -you via email when it is finished. You can then use that image in -subsequent experiments by specifying the descriptor name in your NS -file with the - +The most common approach is to use the +New Image Descriptor +form to create a disk image that contains a customized version of the +standard Redhat Linux partition or the FreeBSD partition. Or, you can +start from scratch and load your own operating system in any of the +DOS partitions, and then capture that partition when you are +done. Either way, all you need to do is enter the node name in the +form, and the testbed system will create the image for you +automatically, notifying you via email when it is finished. You can +then use that image in subsequent experiments by specifying the +descriptor name in your NS file with the + tb-set-node-os directive. When the experiment is configured, the proper image will be loaded on each node automatically by the Testbed system. @@ -1160,7 +1160,18 @@ default images as a base, goes like this: -More information on creating and loading your own disk images can be -found at -https://www.emulab.net/newimageid_explain.php3. +If you ever want to reload a node in your experiment, either with one +of your images or with one of the default images, you can use the +os_load command. Log into users and run: + 

    +	os_load -p <pid> -i <imageid> <node>
    + +This program will run in the foreground, waiting until the image has +been loaded. At that point you should log in and make sure everything +is working oaky. You might want to watch the console line as well (see +the FAQ). If you want to load the +default image, then simply run: + + 
    +	os_load <node>