Changes between Version 89 and Version 90 of flukes

Show
Ignore:
Timestamp:
06/07/13 10:51:41 (6 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • flukes

    v89 v90  
    161161=== Client disk images === 
    162162 
    163 ORCA allows experimenters to create their own filesystem, kernel and ramdisk images to be used for a slice. As a starting point an experimenter can use a [wiki:neuca-images number of pre-existing NEuca-enabled images] or start with a [http://open.eucalyptus.com/wiki/EucalyptusUserImageCreatorGuide base Eucalyptus image] and add [wiki:NEuca-guest-configuration NEuca tools] to them to enable post boot configuration of network interfaces and the execution of post-boot scripts. An experimenter can then create an [wiki:virtual-machines ImageProxy] metafile describing the images, place them on a web server and use the URL of the metafile (and its SHA-1 signature) in the slice request.  
    164  
    165 VM Images are defined within Flukes using the 'Images' button. The user can add new images or edit the properties of existing images. Each image must have: 
     163ORCA allows experimenters to create their own filesystem, kernel and ramdisk images to be used for a slice. A number of standard images [http://geni.renci.org:12080/registry/images.jsp are available already]. The images listed with this service are automatically visible in Flukes under 'images' button. 
     164 
     165The user can add new images. Each image must have: 
    166166 
    167167 * A unique short name 
     
    169169 * A SHA-1 hash of the metafile 
    170170 
    171 Images can be specified per reservation (as part of reservation properties) or per node. Images must first be defined using the 'Images|New' dialog and then can be referenced from pull down menus in reservation and node properties.  
    172  
    173 If no images are specified in the request, the sites to which the slivers are bound will select default images which are not guaranteed to be the same across all sites. 
    174  
    175 Note that there are two ways to customize a boot image. One is to create your own filesystem/kernel/ramdisk images, describe them in a metafile and use this metafile in the slice request. Another is to use the a [wiki:neuca-images stock image] and use a post-boot script described below to load additional software onto the image after the VM boots.  
    176  
    177 In order to allow reusing the same image descriptions across multiple requests, Flukes users can edit ~/.flukes.properties file to add their favorite images: 
     171Images can be specified for each node or nodegroup independently. New images must first be defined using the 'Images|New' dialog and then can be referenced from pull down menus in reservation and node properties. Users are required to specify an image for each node or nodegroup.  
     172 
     173If the user has an image that should always be part of the Flukes environment, there are two approaches - request that the image is listed with [http://geni.renci.org:12080/registry/images.jsp the image service] (this way the image becomes visible to all Flukes users) or privately define the image in .flukes.properties file. 
     174Flukes users can edit ~/.flukes.properties file to add their favorite images: 
    178175 
    179176{{{