Version 3 (modified by aydan, 9 years ago)

--

Using NEuca in Orca

Overview

This page contains notes about how NEuca is to be used in Orca.

NEuca Site Authority

To use NEuca, you need a NEuca-enabled Eucalyptus cluster and an Orca site authority actor configured to interact with NEuca.

TODO: add links to instructions about setting up Encalyptus with Neuca.

To define an actor to interact with NEuca, you can use the following template:

    <actor>
            <type>site</type>
            <name>YOUR_ACTOR_NAME</name>
             <guid>GENERATE_YOUR_ACTOR_GUID</guid>
            <pools>
                <pool>
                    <type>YOUR_RESOURCE_TYPE_NAME</type>
                    <label>Eucalyptus Virtual Machine</label>
                    <description>A virtual machine</description>
                    <units>10</units>
                    <start>2010-01-30T00:00:00</start>
                    <end>2011-01-30T00:00:00</end>
                    <handler path="ec2/handler.xml">
                        <properties>
                            <!-- 
                            By default the handler assumes that the keys are under $ORCA_HOME/ec2. 
                            If you want the handler to use keys from a different location, specify it here.
                            Note: it must be an absolute path.
                            -->
                            <!-- <property name="ec2.keys" value="path_to_keys_dir" /> -->
                        </properties>
                    </handler>
                </pool>
            </pools>
            <controls>
                <control type="YOUR_RESOURCE_TYPE_NAME" class="orca.policy.core.SimpleVMControl" />
            </controls>
        </actor>

Please replace the text in caps with text appropriate for your setup. You probably also want to change the units and the start/end parameters for the resource type.

NEuca Handler

The NEuca handler supports creating VMs using the NEuca extension. The current version of the handler supports the following:

  • multiple network interfaces
  • ip addresses per network interface
  • an instance configuration ip address
  • user SSH public key