Changes between Version 42 and Version 43 of NEuca-in-orca

Show
Ignore:
Timestamp:
01/23/11 16:03:45 (8 years ago)
Author:
ibaldin (IP: 108.65.61.102)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NEuca-in-orca

    v42 v43  
    343343See [source:orca/tags/Bella-2.2/handlers/ec2/ec2.site.sample.properties sample ec2.site.properties for Bella 2.2] and [source:orca/trunk/handlers/ec2/ec2.site.sample.properties sample ec2.site.properties for Camano 3.0+ ] files for more details. 
    344344 
     345== Eucanet handler == 
     346 
     347Usually a NEuca cluster has an ORCA-controlled switch that ethX (ethX != eth0) of all worker nodes are connected to. In order to perform things like site embedding (embedding a topology in a single NEuca site), you must configure another authority actor for VLANs and use the appropriate handler that will configure VLANs on the switch as needed. The handler definition should look something like this: 
     348{{{ 
     349                                        <handler path="providers/euca-sites/renci.euca.net.xml"> 
     350                                                <properties> 
     351                                                        <!-- name of the site that helps locate appropriate property definitions (Camano 3.0+) --> 
     352                                                        <property name="euca.site" value="renci" /> 
     353                                                        <!-- credentials for logging into the switch  (Bella 2.2) --> 
     354                                                        <property name="eucanet.credentials" value="/opt/orca/config/eucanet.cred.properties" /> 
     355                                                </properties> 
     356                                        </handler> 
     357}}} 
     358 
    345359== Accessing VMs Created by NEuca == 
    346360