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

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

--

Legend:

Unmodified
Added
Removed
Modified
  • NEuca-in-orca

    v43 v44  
    345345== Eucanet handler == 
    346346 
    347 Usually 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"> 
     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 (eg. unc-net-site or renci-net-site) and use the appropriate handler that will configure VLANs on the switch as needed. The handler definition should look something like this (also above in the larger example): 
     348{{{ 
     349                                        <!-- For Bella 2.2 you have to specify a site-specific handler (e.g. renci.euca.net.xml)  
     350                                        For Camano 3.0+  a unified handler can be used --> 
     351                                        <handler path="providers/euca-sites/unified.euca.net.xml"> 
    350352                                                <properties> 
    351353                                                        <!-- name of the site that helps locate appropriate property definitions (Camano 3.0+) -->