Changes between Version 51 and Version 52 of NEuca-in-orca

Show
Ignore:
Timestamp:
03/03/11 10:33:50 (8 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NEuca-in-orca

    v51 v52  
    308308== Eucanet handler == 
    309309 
    310 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 (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): 
     310Usually 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 resource pool for VLANs (eg. unc-net-site or renci-net-site) and use the appropriate handler that will configure VLANs on the switch as needed. Usually the pool is operated by the same authority actor as NEuca. The handler definition should look something like this (also above in the larger example): 
    311311{{{ 
    312312                                        <!-- For Bella 2.2 you have to specify a site-specific handler (e.g. renci.euca.net.xml)