Changes between Version 57 and Version 58 of Eucalyptus-2.0-Setup

Show
Ignore:
Timestamp:
09/30/10 17:16:43 (9 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Eucalyptus-2.0-Setup

    v57 v58  
    111111root@master$ $EUCALYPTUS/usr/sbin/euca_conf -d $EUCALYPTUS --enable cloud --enable walrus --enable sc 
    112112}}} 
    113  * 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. '''Apparmor, if running, may need to be configured to allow dhcpd to read/write files from custom locations (e.g. $EUCALYPTUS/var/run/eucalyptus/net ). ''' 
     113 * 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. It is important to know if DHCPD needs to be run as user root or dhcpd. '''Apparmor, if running, may need to be configured to allow dhcpd to read/write files from custom locations (e.g. $EUCALYPTUS/var/run/eucalyptus/net ). ''' 
     114 * Read [http://open.eucalyptus.com/wiki/EucalyptusNetworkConfiguration_v2.0 networking configuration notes]. Examples here presume master node has a single interface (eth1) that is both public (allows anyone to reach the host) and is used to communicate to the rest of the cluster. Your setup may be different.  
    114115 * 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): 
    115116{{{ 
     
    192193==== Using the correct JDK ==== 
    193194 * If your Java 1.6 installation is non-standard, you need to update $EUCALYPTUS/etc/init.d/eucalyptus-cloud to define JAVA_HOME in its opening part and updating PATH to include $JAVA_HOME/bin 
     195 
     196==== DHCP does not work ==== 
     197 
     198Most common problem seems to be that VMs startup properly but Eucalyptus either fails to update the dhcpd configuration file or fails to (re)start dhcpd. All these problems are related to file and or user permissions. Consult Cluster Controller logfiles (on master node $EUCALYPTUS/var/log/eucalyptus/cc.log and look for string "DHCP"). Culprits may be running dhcpd as a wrong user (set through eucalyptus.conf) or Apparmor interfering and preventing dhcpd from creating/modifying files.