Changes between Version 29 and Version 30 of Eucalyptus-1.5.2-Setup

Show
Ignore:
Timestamp:
02/25/10 18:10:09 (9 years ago)
Author:
ibaldin (IP: 152.54.9.131)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Eucalyptus-1.5.2-Setup

    v29 v30  
    194194[CN] /var/log/eucalyptus/nc.log 
    195195 
    196 == Modifying networking setup == 
     196== Modifying networking setup to work with ORCA == 
    197197 
    198198In order to use Eucalyptus with ORCA each physical host must have two interfaces: one to the switch that is the dataplane (Cisco 6509 in RENCI's case) and one that leads either to a management network or to the public internet, to allow connection with ORCA actors. ORCA site authority for Euca will be deployed on the Eucalyptus master node and it must have 
     
    223223and rebooting. 
    224224 
    225 == Installing ORCA patches == 
     225== Installing ORCA-related patches on master node == 
    226226 
    227227There are two patches - one for the VM creation template (to allow creation of VMs with more than one interface), the other to enable to specify the VLAN tag to be used for a particular security group.  
    228228 1. Install the updated VM creation template on client nodes by replacing files gen_kvm_libvirt_xml  and gen_libvirt_xml in Eucalyptus. In Ubuntu/Debian they can be found under $EUCALYPTUS/usr/share/eucalyptus. The two files are attached to this page. 
    229  1. Install the patch (vlan.patch attached to this page) for Eucalyptus security group VLAN forcing on master node.  
     229 1. Install the patch (vlan.patch attached to this page) for Eucalyptus security group VLAN forcing on master node. Note that the user doing make and make install must have $JAVA_HOME, $EUCALYPTUS and $EUCALYPTUS_SRC defined and ant and java executables must be on the $PATH. 
    230230{{{ 
    231231$ cd eucalyptus-1.5.2/clc 
    232232$ patch -p2 < vlan.patch 
    233 }}} 
     233$ make; make install 
     234}}} 
     235 Restart the cloud controller and the portal, try the following as a regular user: 
     236{{{ 
     237$ euca-add-group -d testvlan vlan22 
     238$ euca-run-instances -g vlan22 <usual parameters from above> 
     239}}} 
     240If this works, you should see that 'eucabr22' bridge has been created on every host and a 802.1q tagged interface (typycally eth0.22) was created and is part of that bridge. If VLAN id 22 is enabled between all hosts, then you should be able to reach the new VM on the IP address indicated by Eucalyptus and it will be on the private VLAN 22. 
    234241 
    235242= Undoing an install =