Changes between Version 31 and Version 32 of flukes

Show
Ignore:
Timestamp:
12/05/11 12:54:11 (8 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • flukes

    v31 v32  
    9292An unbound node group may be split by the system among multiple domains depending on the availability of resources. A bound node group is never split and is allocated from the specific domain. A user can indicate the splittability of the group by checking the appropriate box in node group properties. 
    9393 
     94=== Client disk images === 
     95 
     96ORCA allows experimenters to create their own filesystem, kernel and ramdisk images to be used for a slice. An experimenter can create the images, create an [wiki:image-proxy-with-orca ImageProxy] metafile describing the images, place them on a web server and use the image URL in the request. 
     97 
     98VM Images are defined using the 'Images' button. The user can add new images or edit the properties of existing images. Each image must have: 
     99 
     100 * A unique short name 
     101 * A URL of the ImageProxy metafile from which it can be downloaded 
     102 * A SHA-1 hash of the metafile 
     103 
     104Images 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.  
     105 
     106If 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. 
     107 
    94108=== Post Boot Scripts and templates  === 
    95109 
    96 Flukes allows a post boot script to be associated with each node or node group.  Post boot scripts are the preferred way to create customized instances from a shared image.   Specifically, a post boot script can contain an arbitrary script that is a executed immediately after the instance has booted.    
     110Flukes allows a post boot script to be associated with each node or node group.  Post boot scripts are the preferred way to create customized instances from a shared image.  Specifically, a post boot script can contain an arbitrary script that is a executed immediately after the instance has booted.    
    97111 
    98112Simple example: 
     
    125139}}} 
    126140 
    127 == Boot images ==  
     141=== Graph Layouts === 
    128142 
    129 Look at [wiki:image-proxy-with-orca this page] for instructions on how to create image descriptors for !ImageProxy. In Flukes, click on the 'Client Images' button to add new images, which can then be assigned to nodes, node groups or reservations. 
     143There are several graph layouts available from a pull-down menu in Flukes. When a graph is saved in NDL-OWL, its layout is not preserved, so this feature is provided as a convenience. After loading a graph a user can experiment with different layouts to find the most convenient one. 
    130144 
     145