Changes between Version 18 and Version 19 of Eucalyptus-2.0-Setup

Show
Ignore:
Timestamp:
09/08/10 14:44:51 (9 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Eucalyptus-2.0-Setup

    v18 v19  
    5555 
    5656This setup assumes that a single NIC in each physical host is dedicated to Eucalyptus functions. Other NICs can be used for extra data-plane connectivity. The MANAGED-NOVLAN mode places no requirements for the supported network switches. To properly setup the network configuration it is important to know two things: 
    57  * The name of the '''physical interface''' on '''master''' node that has access to worker nodes (and in this case also is public; it is named eth1)  
    58  * The name of the '''bridge''' on '''worker''' nodes that KVM or XEN uses. In this case it is also eth1, because Xen is used as an example. In case of KVM it is typically br0. 
     57 1 The name of the '''physical interface''' on '''master''' node that has access to worker nodes (and in this case also is public; it is named eth1)  
     58 2 The name of the '''bridge''' on '''worker''' nodes that KVM or XEN uses. In this case it is also eth1, because Xen is used as an example. In case of KVM it is typically br0. 
    5959 
     60 * Perform step 6 a and b of the installation instructions (add user 'eucalyptus' to all nodes; configure hypervisor  
     61 * On worker nodes initialize the configuration file (note that instances directory does not have to be /usr/local/eucalyptus; you can configure it to be anything you want and this step will create and initialize it): 
     62{{{ 
     63root@worker$ $EUCALYPTUS/usr/sbin/euca_conf -d $EUCALYPTUS --hypervisor kvm --instances /usr/local/eucalyptus --user eucalyptus --setup 
     64}}} 
     65  * Initialize config file on master node: 
     66{{{ 
     67root@master$ $EUCALYPTUS/usr/sbin/euca_conf -d $EUCALYPTUS --setup 
     68root@master$ $EUCALYPTUS/usr/sbin/euca_conf -d $EUCALYPTUS --enable cloud --enable walrus --enable sc 
     69}}} 
     70  * Make sure master node has dhcpd installed (typically /usr/sbin/dhcpd or /usr/sbin/dhcpd3). It must not be configured. The worker nodes '''cannot''' deal with multiple DHCP servers on the same subnet in this Eucalyptus mode. The only DHCP server on that subnet must be the one used by Eucalyptus. 
     71  * Modify the configuration of the master node ($EUCALYPTUS/etc/eucalyptus/eucalyptus.conf; only the relevant stanzas are shown; make sure no other VNET_MODE statements are uncommented in the file). Note that in the shown configuration the 10.100.x.x range is used internally by Eucalyptus, while 192.168.203.x range is 'public' (even though it comes from a reserved address space): 
     72{{{ 
     73VNET_PUBINTERFACE="eth1" 
     74VNET_PRIVINTERFACE="eth1" 
     75VNET_DHCPDAEMON="/usr/sbin/dhcpd3" 
     76 
     77VNET_MODE="MANAGED-NOVLAN" 
     78VNET_SUBNET="10.100.0.0" 
     79VNET_NETMASK="255.255.0.0" 
     80VNET_DNS="192.168.201.254" 
     81VNET_ADDRSPERNET="32" 
     82VNET_PUBLICIPS="192.168.203.31-40" 
     83}}} 
     84  * Modify the configuration of worker nodes ($EUCALYPTUS/etc/eucalyptus/eucalyptus.conf): 
     85{{{ 
     86VNET_MODE="MANAGED-NOVLAN" 
     87VNET_BRIDGE="eth1" 
     88}}} 
    6089== Running and testing Eucalyptus == 
    6190