Corporate Home Open Source Home
Syndicate content
Eucalyptus

Installing Eucalyptus (1.6) on openSUSE 11

Eucalyptus can be installed on openSUSE 11 from source, or by using binary RPM packages. This document details the steps required to install Eucalyptus from RPMs. In what follows, the value of $VERSION must be substituted accordingly (e.g., as 1.6.1, 1.6.2, etc.) for example we can set the value of 1.6.2 using bash:

export VERSION=1.6.2

Prerequisites

If you start with a standard openSUSE installation, you will satisfy all prerequisites with the following steps:

  1. Front-end, node and client machine system clocks are syncronized (i.e. using NTP).
    sntp -P no -r pool.ntp.org
    yast2 -i ntp
    /etc/init.d/ntp restart
    
  1. Install all dependency packages that are required for Eucalyptus to run on the front-end
    yast2 -i apache2 apache2-prefork java-1_6_0-openjdk java-1_6_0-openjdk-devel libvirt curl vlan dhcp-server bridge-utils
    
    and on the node
    yast2 -i xen libvirt vlan apache2
    
  1. Node has a fully installed and configured installation of Xen.
    • RECOMMENDED: verify your Xen installation by manually bringing up a VM and testing that it has network connectivity using bridged networking.
    • To set up bridged networking on your node, use the 'yast2' command and go through the following steps:
      • Network Devices
      • Network Settings
      • Select 'OK' to get past information box
      • Traditional Method with ifup
      • Overview
      • Add
      • Device Type: Bridge
      • Next
      • Bridged Devices: select eth0 (or the name of your primary interface)
      • Next
      • Continue
      • Ok
    • make sure that the libvirt daemon (libvirtd) is running and configured properly
      • /etc/init.d/libvirtd start
      • check eucalyptus can interact with libvirt
        su eucalyptus -c "virsh list"

        you may see this error (which could show up in the logs too)

        Attempting to obtain authorization for org.libvirt.unix.manage.
        polkit-grant-helper: given auth type (8 -> yes) is bogus
        Failed to obtain authorization for org.libvirt.unix.manage.
        

        which is harmless.

  1. Firewall rules must permit the Eucalyptus components to communicate with one another, and clients to communicate with Eucalyptus.
    • NOTE: on the front-end, ports 8443, 8773, 8774 and 9001 must be open. On the node, port 8775 must be open
    • If you are planning on using Elastic IPs and/or Security Groups, you may want to consider disabling the firewall and use Eucalyptus facilities for enabling custom firewall rules (see Network configuration for more information).
      • yast2 firewall startup manual
      • /etc/init.d/SuSEfirewall2_init stop
      • reboot

Download and Install RPMs

Eucalyptus binary installation is broken up into several packages: one for each of the components (CLC, Walrus, CC, etc.), as well as a couple of common packages. There are two options for obtaining the packages:

  1. Zypper option: packages are available from our repository. To use it:
    zypper ar --refresh http://www.eucalyptussoftware.com/downloads/repo/eucalyptus/$VERSION/yum/opensuse Eucalyptus
    
    answer question about trusting packages from this repository then refresh it
    zypper refresh Eucalyptus
    
    and now install eucalyptus on the front-end
    zypper install eucalyptus-cloud eucalyptus-cc eucalyptus-walrus eucalyptus-sc 
    
    or the node
    zypper install eucalyptus-nc 
    
  2. Tarball option: the packages are available in a single tarball, wherein we also include copies of third-party openSUSE packages that Eucalyptus depends on (Rampart, Axis2C, many Java libraries), at http://open.eucalyptus.com/downloads (look for a openSUSE tarball of the right Eucalyptus version and architecture). Untar the bundle in a temporary location:
    tar zxvf eucalyptus-$VERSION-*.tar.gz
    cd eucalyptus-$VERSION-*
    
  3. In the examples below we use x86_64, which should be replaced with i386 or i586 on 32-bit architectures. Install the third-party dependency RPMs on the front end:

    cd eucalyptus-$VERSION*-rpm-deps-x86_64
    rpm -Uvh aoetools-21-1.el4.x86_64.rpm \
             euca-axis2c-1.6.0-1.x86_64.rpm \
             euca-rampartc-1.3.0-1.x86_64.rpm \
             vblade-14-1mdv2008.1.x86_64.rpm \
             groovy-1.6.5-1.noarch.rpm \
             vtun-3.0.1-1.x86_64.rpm
    cd ..
    

    Install the -cloud, -walrus, -cc and -sc RPMs on the front end:

    rpm -Uvh eucalyptus-$VERSION-*.x86_64.rpm \
             eucalyptus-common-java-$VERSION-*.x86_64.rpm \
             eucalyptus-cloud-$VERSION-*.x86_64.rpm \
             eucalyptus-sc-$VERSION-*.x86_64.rpm \
             eucalyptus-walrus-$VERSION-*.x86_64.rpm \
             eucalyptus-cc-$VERSION-*.x86_64.rpm \
             eucalyptus-gl-$VERSION-*.x86_64.rpm
    

    Install RPMs on the nodes

    Install the dependency packages on each node:

    cd eucalyptus-$VERSION*-rpm-deps-x86_64
    rpm -Uvh aoetools-25-2.49.x86_64.rpm \
             euca-axis2c-1.6.0-1.x86_64.rpm \
             euca-rampartc-1.3.0-1.x86_64.rpm \
             vblade-15-2.49.x86_64.rpm
    cd ..
    

    On the compute nodes, install the node controller RPM with dependencies:

    rpm -Uvh eucalyptus-$VERSION-*.x86_64.rpm \
             eucalyptus-gl-$VERSION-*.x86_64.rpm \
             eucalyptus-nc-$VERSION-*.x86_64.rpm
    

    Post-Install Steps

    Now start up your Eucalyptus services. On the front-end:

    /etc/init.d/eucalyptus-cloud start
    /etc/init.d/eucalyptus-cc start
    

    On the node:

    /etc/init.d/eucalyptus-nc start