This is an old revision of the document!

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 few starter images that can be used by experimenters.

ExoGENI VM images typically consist of three separate parts:

  • The kernel
  • The ramdisk
  • The filesystem

Kernels and ramdisks can be mixed and matched with different filesystems, if desired, as long as necessary modules to mount the filesystem are in the ramdisk.

A simple XML-based meta-file format is used to describe images. Image parts are referenced by the URLs of the metafile and the image itself is used by providing ExoGENI tools (Flukes, omni or Flack) with the URL of the metafile and its SHA1 signature. Note that since image elements are referenced by URLs, the different parts of the image and the metafile itself can all be hosted by different webservers.

		<signature>FS IMAGE SHA1 HASH</signature>
		<signature>KERNEL IMAGE SHA1 HASH</signature>
		<signature>RAMDISK IMAGE SHA1 HASH</signature>

Finding existing images

Well-known and tested images are listed 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.

Note that due to licensing requirements we cannot list or provide non Open-Source OS images (MS Windows, Solaris etc).

Building your own images

You can build your own image yourself on any Linux computer and add NEuca guest tools to it. For testing VM images, ExoGENI offers the use of the image playpen, where images can be debugged.

Making your images useful to other experimenters

If you have an image you would like to share with the community, please send an email to geni-orca-users list and ask for the image to be added to this list. Please provide detailed information about what is on the image and who created it.