Differences

This shows you the differences between two versions of the page.

Link to this comparison view

public:experimenters:images [2013/05/28 12:27]
ibaldin [Making your images useful to other experimenters]
public:experimenters:images [2016/09/07 11:46] (current)
ibaldin [Building and using your own images]
Line 1: Line 1:
 ====== ExoGENI VM Images ====== ====== ExoGENI VM Images ======
  
-ExoGENI is a BYOI testbed - unlike Emulab/InstaGENI the images are not hosted by the testbed. Instead, VM images can be created by anyone, uploaded to any webserver and then used to create slices. ExoGENI does provide a [[http://geni.renci.org:12080/registry/images.jsp | few starter images]] that can be used by experimenters.+ExoGENI is a BYOI testbed - unlike Emulab/InstaGENI the images are not hosted by the testbed. Instead, VM images can be created by anyone, uploaded to any webserver and then used to create slices. ExoGENI control software is provided with a URL of the metafile, containing the parts of the image, based on which it retrieves the image and boots VM instances with it. ExoGENI does provide a [[http://geni.renci.org:15080/registry/images.jsp | few starter images]] that can be used by experimenters.
  
 ExoGENI VM images typically consist of three separate parts:  ExoGENI VM images typically consist of three separate parts: 
Line 33: Line 33:
 </images> </images>
 </code> </code>
 +
 +To see a working example, simply click on any URLs in the listing provided by the [[http://geni.renci.org:15080/registry/images.jsp | Image Registry Service]]
 ===== Finding existing images ===== ===== Finding existing images =====
  
-Well-known and tested images are listed [[http://geni.renci.org:12080/registry/images.jsp | on this page]]. There is also an XMLRPC service that is available for tool builders (see same page). For example Flukes automatically reads all images listed by this service at startup. +Well-known and tested images are listed [[http://geni.renci.org:15080/registry/images.jsp | on this page]] through an Image Registry ServiceIn addition to providing a human-readable web page, there is also an XMLRPC service that is available for tool builders (see same page). For example Flukes automatically reads all images listed by this service at startup. 
  
 Note that due to licensing requirements we cannot list or provide non Open-Source OS images (MS Windows, Solaris etc).  Note that due to licensing requirements we cannot list or provide non Open-Source OS images (MS Windows, Solaris etc). 
Line 41: Line 43:
 ===== Building and using your own images ===== ===== Building and using your own images =====
  
-You can [[https://geni-orca.renci.org/trac/wiki/virtual-machines | build your own image yourself]] on any Linux computer and add [[https://geni-orca.renci.org/trac/wiki/NEuca-guest-configuration | NEuca guest tools to it]]. For testing VM images, ExoGENI offers the use of the [[:public:experimenters:playpen | image playpen]], where images can be debugged.+You can [[https://geni-orca.renci.org/trac/wiki/virtual-machines | build your own image yourself]] on any Linux computer and add [[https://geni-orca.renci.org/trac/wiki/NEuca-guest-configuration | NEuca guest tools to it]]. 
  
 After you have placed the image metafile on some Internet-facing webserver and calculated its SHA1 signature (using e.g. 'sha1sum' program under Linux), you can After you have placed the image metafile on some Internet-facing webserver and calculated its SHA1 signature (using e.g. 'sha1sum' program under Linux), you can
   * Add the image to the [[https://geni-orca.renci.org/trac/wiki/flukes#Clientdiskimages | list of images]] known to your Flukes    * Add the image to the [[https://geni-orca.renci.org/trac/wiki/flukes#Clientdiskimages | list of images]] known to your Flukes 
-  * Input the image metafile URL and SHA1 signature into Flukes image dialog+  * Input the image metafile URL and SHA1 signature into Flukes image dialog 
   * Input the image metafile URL and SHA1 signature into RSpec (for omni and Flack)   * Input the image metafile URL and SHA1 signature into RSpec (for omni and Flack)
 +
 +You can then launch a slice using this image. 
 +
 +Note that since ExoGENI software needs to fetch parts of your image from the webserver prior to launching your slice, the first time you launch a slice with a particular image in a particular site, you may incur a significant delay. 
 +
 +There is a helpful script attached to [[https://geni-orca.renci.org/trac/wiki/virtual-machines | this page]] that helps create an image descriptor XML file. 
 ===== Making your images useful to other experimenters ===== ===== Making your images useful to other experimenters =====
  
Navigation
Print/export