Version 4 (modified by ibaldin, 8 years ago)


Using ImageProxy with ORCA


ImageProxy allows independent Ecalyptus sites to create VMs with identical images. Images are identified by a URL and a GUID, representing image hash. Provided with these two parameters ImageProxy? associated with a Eucalyptus site can download and install that image and provide ORCA with site-specific AMI/EMI that can be used to create guest VMs on that site. Even though AMI/EMI will be different for each site, VMs will be runnning the same user-supplied image.

ORCA Integration

Resource Specification

Image URL and GUID can be passed to ORCA as part of Reservation instance of the NDL-OWL request as follows:

    <request:Reservation rdf:about="#id-mp-request-2">
        <compute:hasVMImage rdf:resource="#DukeVMImageTest"/>
        <collections:element rdf:resource="&Request2;tblink-l4"/>
        <collections:element rdf:resource="&Request2;tblink-l5"/>
        <collections:element rdf:resource="&Request2;tblink-l6"/>
        <request:inDomain rdf:resource="&DukeVMSite2;Domain"/>
        <layer:atLayer rdf:resource="&ethernet;EthernetNetworkElement"/>

    <compute:VMImage rdf:about="#DukeVMImageTest">
        <topology:hasGUID rdf:datatype="&xsd;string">1234567890</topology:hasGUID>

Handler Integration

The interface to ImageProxy SOAP service is implemented as an OrcaAntTask? named ImgProxyRegisterTask? in the orca.handlers.ec2.tasks.imgproxy package (under handlers/ec2). The task is integrated into the standard EC2 handler used with Eucalyptus/NEuca. ImageProxy-specific settings can be passed to orca via file. The relevant properties are:

# Image Proxy (use it or not true/false)
# SOAP URL of the image proxy
# SOAP timeout (in sec; adjust only if you know what you're doing)

For more information see the sections about NEuca handler.