Changes between Version 12 and Version 13 of image-proxy-with-orca

Show
Ignore:
Timestamp:
04/26/11 22:18:46 (8 years ago)
Author:
prateek (IP: 152.3.68.8)
Comment:

Guid for metadata file is no longer required

Legend:

Unmodified
Added
Removed
Modified
  • image-proxy-with-orca

    v12 v13  
    33== Overview == 
    44 
    5 !ImageProxy allows  independent Ecalyptus sites to create VMs with identical images. Images are identified by a URL and a GUID, representing image hash. A metadata file containing information about the different types of images needs to be created.  
     5!ImageProxy allows  independent Ecalyptus sites to create VMs with identical images. Images are identified by a URL and a GUID, SHA-1 hash of the image. A metadata file containing information about the different types of images needs to be created.  
    66{{{ 
    77Sample metadata file. Node element names and keywords representing image type are case sensitive. 
     
    99        <image> 
    1010                <type>FILESYSTEM</type> 
    11                 <guid>FS_IMAGE</guid> 
     11                <guid>FS_IMAGE_HASH</guid> 
    1212                <url>http://url_filesystem_image</url> 
    1313        </image> 
    1414        <image> 
    1515                <type>KERNEL</type> 
    16                 <guid>KERNEL_Image1</guid> 
     16                <guid>KERNEL_IMAGE_HASH</guid> 
    1717                <url>http://url_kernel_image</url> 
    1818        </image> 
    1919        <image> 
    2020                <type>RAMDISK</type> 
    21                 <guid>RAM_Image1</guid> 
     21                <guid>RAMDISK_IMAGE_HASH</guid> 
    2222                <url>http://url_ramdisk_image</url> 
    2323        </image> 
     
    2525}}} 
    2626 
    27 The metadata file itself is also identified by a URL and a GUID, representing metadata file hash. Provided with the URL and GUID for the metadata file, !ImageProxy associated with a Eucalyptus site can download and install the required images and provide ORCA with site-specific image ids (AMI/EMI, AKI/EKI, ARI/ERI) that can be used to create guest VMs on that site. Even though image ids will be different for each site, VMs will be runnning the same user-supplied image.  
     27The metadata file itself also needs to be hosted. Provided with the URL for the metadata file, !ImageProxy associated with a Eucalyptus site can download and install the required images and provide ORCA with site-specific image ids (AMI/EMI, AKI/EKI, ARI/ERI) that can be used to create guest VMs on that site. Even though image ids will be different for each site, VMs will be runnning the same user-supplied image.  
    2828 
    2929== ORCA Integration (Camano 3.0+) == 
     
    3131=== Resource Specification === 
    3232 
    33 Image URL and GUID can be passed to ORCA as part of Reservation instance of the NDL-OWL request as follows: 
     33URL for the image metadata file can be passed to ORCA as part of Reservation instance of the NDL-OWL request as follows: 
    3434 
    3535{{{ 
     
    4848 
    4949    <compute:VMImage rdf:about="#DukeVMImageTest"> 
    50         <topology:hasGUID rdf:datatype="&xsd;string">1234567890</topology:hasGUID> 
    5150        <topology:hasURL>http://geni-orca.renci.org/image/duke</topology:hasURL> 
    5251    </compute:VMImage> 
     
    6564}}} 
    6665 
    67 The handler expects config.image.url and config.image.guid properties to be passed to it by the AM.  
     66The handler expects config.image.url property to be passed to it by the AM.  
    6867 
    6968For more information see the sections about [wiki:NEuca-in-orca#NEucaHandler NEuca handler] and [wiki:Neuca-handler-testing NEuca handler testing].