Eucalyptus comes with the euca_conf script for configuring Eucalyptus. For some requests it
modifies the configuration file located in '$EUCALYPTUS/etc/eucalyptus/eucalyptus.conf'
(which can also be edited manually), for other requests it modifies the database maintained by
the Cloud Controller (much of that functionality is duplicated in the Web interface, to be
described later).
In addition to modifying the configuration, euca_conf attempts to synchronize x509 credentials
across the nodes of a Eucalyptus installation by relying on rsync and scp. We highly recommend
setting up password-less SSH access for the root user across all nodes of your Eucalyptus
installation (otherwise, euca_conf will prompt you for remote system passwords).
As explained in the overview, a Eucalyptus installation consists of five types of components:
cloud controller (CLC), Walrus, cluster controller (CC), storage controller (SC), and the node
controller(s) (NCs). In following instructions we assume that all components except the NCs are
co-located on a machine that we will refer to as the front end and that NCs run on compute
nodes.
First, make sure that you have all of the runtime dependencies of Eucalyptus installed, based on
your chosen set of configuration parameters. If there is a problem with runtime dependencies (for
instance, if Eucalyptus cannot find/interact with them), all errors will be reported in log files
located in $EUCALYPTUS/var/log/eucalyptus.
Next, inspect the contents of $EUCALYPTUS/etc/eucalyptus/eucalyptus.conf carefully, on each
machine, to make sure that the settings are appropriate for your environment.
Once everything is configured properly, enable the cloud services that you wish to run on your
front-end, then use the init-scripts to start each component on the appropriate host. Most likely,
on the front-end you would run:
# enable services on the front-end
$EUCALYPTUS/usr/sbin/euca_conf --enable cloud --enable walrus --enable sc
# start enabled front-end services
$EUCALYPTUS/etc/init.d/eucalyptus-cloud start
# start the cluster controller
$EUCALYPTUS/etc/init.d/eucalyptus-cc start
And on each of the compute nodes you would run:
$EUCALYPTUS/etc/init.d/eucalyptus-nc start
To stop them you call the script with stop instead of start.
NOTE: if you later decide to make changes to
$EUCALYPTUS/etc/eucalyptus/eucalyptus.conf that will effect the cluster-controller, make
sure to use the 'cleanstart', 'cleanstop', and/or 'cleanrestart' directives to the init scripts (as