Changes between Version 6 and Version 7 of sol4/IDMS/CreateImages


Ignore:
Timestamp:
06/18/14 17:26:02 (5 years ago)
Author:
ezkissel@indiana.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • sol4/IDMS/CreateImages

    v6 v7  
    55 * Note: The following assumes you would like to bootstrap a new filesystem and OS in your local development environment.  Alternatives include:
    66
    7  1) Download an existing image tarball, extract the filesystem, make changes, and repackage the image as needed.  You can start from "Making changes to the image" section below.
    8 
    9  2) Use the ExoGENI playpen to boot existing images and make live changes with the option of saving the modified image.  See [http://www.exogeni.net/2014/06/creating-a-custom-image-from-an-existing-virtual-machine/] for more information.
     7  1. Download an existing image tarball, extract the filesystem, make changes, and repackage the image as needed.  You can start from "Making changes to the image" section below.
     8  2. Use the ExoGENI playpen to boot existing images and make live changes with the option of saving the modified image.  See [http://www.exogeni.net/2014/06/creating-a-custom-image-from-an-existing-virtual-machine/] for more information.
    109
    1110== Create a file to store the new OS filesystem ==
     
    124123 * Create the image metadata file and place in a web directory as per these intructions: [https://geni-orca.renci.org/trac/wiki/virtual-machines ExoGENI/ORCA Virtual Machine Images]
    125124
    126 == Converting a running ExoGENI image for use on ProtoGENI ==
     125== Converting a running ExoGENI image for use on ProtoGENI/InstaGENI ==
    127126
    128  * To complete this process, you need an account on a given site's Emulab instance.  For instance, at Utah, information can be found at [http://www.emulab.net]
     127 * Note: a converted image with only the Neuca tools installed and enabled will boot on PG/IG but with limited capabilities.  The caveats include:
     128  1. No user account creation.
     129  2. No user ssh keys installed.  --> The accounts and keys that existed on the running EG image will persist and allow you to login to the node.
     130  3. Data plan interfaces will exist but configuration (e.g., IPs) will not be assigned.
     131 
     132To resolve the above issues, the Emulab client tools must be installed on the EG image before the conversion process.  The tools may be installed on the running EG VM right before the conversion step or they may be included on the saved EG image filesystem.  The instructions for this install process can be found:
     133
     134==> [wiki:sol4/IDMS/EmulabClientTools Installing Emulab Client Tools] (for EG images)
     135
     136 * To complete the conversion process, you need an account on a given site's Emulab instance.  For instance, at Utah, information can be found at [http://www.emulab.net]
    129137 * Create a sliver with an EG node you would like to convert.  Make sure the running image has the minimum dependencies as described above.
    130138 * Once logged in, follow these steps: