eucalyptus

5.1   Introduction to Eucalyptus:

Eucalyptus is a Linux-based software architecture that implements scalable private and hybrid clouds within your existing IT infrastructure. Eucalyptus allows you to provision your own collections of resources (hardware, storage, and network) using a self-service interface on an as-needed basis.

You can install Eucalyptus on the following Linux distributions:

·         CentOS 5.6 and above

·         Red Hat Enterprise Linux 5.6 and above

·         Red Hat Enterprise Linux 6

·         Ubuntu 10.04 LTS

The software framework is modular, with industry-standard, language-agnostic communication. Eucalyptus provides a virtual network overlay that both isolates network traffic of different users and allows two or more clusters to appear to belong to the same Local Area Network (LAN). Also, Eucalyptus offers API compatability with Amazon’s EC2, S3, and IAM services. This offers you the capability of a hybrid cloud.

Eucalyptus Components :

·         Cloud Controllers

·         Node Controler

·         Cluster Controller

·         Storage Controllers

·         Walurus

·         System Requirements :

To install Eucalyptus, your system must meet the following baseline requirements.

Note: The specific requirements of your Eucalyptus deployment, including the number of physical machines, structure of the physical network, storage requirements, and access to software are ultimately determined by the features you choose for your cloud and the availability of infrastructure required to support those features.

·         Hypervisor: CentOS 5 and RHEL 5 installations must have Xen installed and configured on NC host.

·         RHEL 6 and Ubuntu 10.04 LTS installations must have KVM installed and configured  on host.

·         VMware-based installations do not include NCs, but must have a VMware hypervisor pool installed and configured.

·         Machine Access: Verify that all machines in your network allow SSH login, and that root or sudo access is available

·         Compute Requirements

•    Physical Machines: All Eucalyptus components must be installed on physical machines, not virtual machines.

•    Central Processing Units (CPUs): We recommend that each machine in your Eucalyptus cloud contain either an Intel or AMD processor with a minimum of two, 2GHz cores.

·         Operating Systems: Eucalyptus supports the following Linux distributions: CentOS 5, RHEL 5, RHEL 6, and Ubuntu 10.04 LTS.

·         Machine Clocks: Each Eucalyptus component machine and any client machine clocks must be synchronized (for example, using NTP). These clocks must be synchronized all the time, not just at installation.

·         Storage and Memory Requirements

1.       Each machine in your network needs a minimum of 30 GB of storage.

2.       We recommend at least 100GB for Walrus and SC hosts running Linux VMs. We recommend at least 250GB for Walrus and SC hosts running Windows VMs.

3.       We recommend a range of 50-100GB per NC host running Linux VMs, and at least 250GB per NC host for running Windows VMs. Note that larger available disk space enables greater number of Vms.

·         Network Configuration

·         All NCs must have access to a minimum of 1Gb Ethernet network connectivity.

·         All Eucalyptus components must have at least one Network Interface Card (NIC) for a base-line deployment. For better network isolation and scale, the CC should have two NICS (one facing the CLC/user network and one facing the NC/VM network). For HA configurations that include network failure resilience, each machine should have one extra NIC for each functional NIC (they will be bonded and connected to separate physical network hardware components).

·          Some configurations require that machines hosting a CC have two network interfaces, each with a minimum of 1Gb Ethernet.

Depending on the feature set that is to be deployed, the network ports connecting the Ethernet interfaces may need to allow VLAN trunking.

·         In order to enable all of the networking features, Eucalyptus requires that you make available two sets of IP addresses. The first range is private, to be used only within the Eucalyptus system itself. The second range is public, to be routable to and from end-users and VM instances. Both sets must be unique to Eucalyptus, not in use by other components or applications within your network.

·         The network interconnecting physical servers hosting Eucalyptus components must support UDP multicast for IP address 228.7.7.3. Note that UDP multicast is not used over the network that interconnects the CC to the NCs.Once you are satisfied that  your  systems requirements  are   met,  you  are ready to  plan  your Eucalyptus installation.

To successfully plan for your Eucalyptus installation, you must determine two things:

·        The infrastructure you plan to install Eucalyptus on: Think about the application workload performance and resource utilization tuning. Think about how many machines you want on your system.

·        The amount of control you plan to give Eucalyptus on your network: Use your existing architecture and policies to determine the Eucalyptus networking features you want to enable: elastic IPs, security groups, DHCP server, and Layer 2 VM isolation.

·        Install on Ubuntu 10.04 LTS

If you plan to install Eucalyptus HA, we recommend that you install each Eucalyptus component on a separate host.

For example, if you are installing CLC, Walrus, CC, and SC, you will install each of these components on a separate ost. You will also install each secondary component (the secondary CLC, Walrus, CC, and SC) on a separate host. In his case, you will need eight machines. Each additional cluster needs four more machines for its CCs and SCs. This oes not account for NCs, which are not redundant.

To install Eucalyptus on servers running Ubuntu 10.04 LTS:

1. Copy the entitlement certificate to the /etc/ssl/certs directory on each server that you want to install Eucalyptus n.

mv <license_name>-1.3.0.crt /etc/ssl/certs/<license_name>-1.3.0.crt

2. Copy the private key file to the /etc/ssl/private directory on each server that you want to install Eucalyptus on.

mv <license_name>.key /etc/ssl/private/<license_name>.key

Important: Make sure that the private key's file permissions are restricted to only the root user and ssl-certs group.

  Add the public key to the list of trusted keys:

apt-key add c1240596-eucalyptus-release-key.pub

4. On each server that you want to install Eucalyptus on, go to /etc/apt/apt.conf.d and create a new file (forexample, eucarepo) with the following content:

Acquire {

https {

VerifyPeer "true";

SslCert "/etc/ssl/certs/<license_name>-1.3.0.crt";

2012, Eucalyptus Systems, Inc.

Eucalyptus | Installing Eucalyptus | 44

SslKey "/etc/ssl/private/<license_name>.key";

};

};

5. Create a file in /etc/apt/sources.list.d called eucalyptus-enterprise.list with the following content:

deb https://downloads.eucalyptus.com/software/enterprise/3.0/ubuntu luciduniverse

6. On all machines that will run either Eucalyptus or Euca2ools, create a file in /etc/apt/sources.list.d called euca2ools.listwith the following content:

deb http://downloads.eucalyptus.com/software/euca2ools/2.0/ubuntu lucid

universe

7. Enter the following command on all machines:

apt-get update

8. Install Eucalyptus packages and dependencies. The following example shows a package install all on the same server.

You can install each component on a different server.

apt-get install eucalyptus-cloud eucalyptus-cc eucalyptus-sc eucalyptus-walrus

For HA: If you are deploying HA, you must install these packages on pairs of systems. For instance,

“eucalyptus-cloud” is installed on the primary CLC and the secondary CLC.

9. On each planned NC server, install the NC package:

apt-get install eucalyptus-nc

Important: If you are using VMware, you can skip this step. Eucalyptus software is not installed on the ode machines. The nodes are running VMware.

10. If you plan to use VMware, install the subscription only VMware Broker package on each CC server:

apt-get install eucalyptus-broker

11. After you have installed Eucalyptus, test multicast connectivity between the CLC and Walrus, SC, and the Vmware Broker.

a) Run the following receiver command on the CLC:

java -classpath /usr/share/eucalyptus/jgroups-2.11.1.Final.jar

org.jgroups.tests.McastReceiverTest -mcast_addr 224.10.10.10 -port 5555

b) Run the following sender command on Walrus:

java -classpath /usr/share/eucalyptus/jgroups-2.11.1.Final.jar

org.jgroups.tests.McastSenderTest -mcast_addr 224.10.10.10 -port 5555

c) Repeat the previous step on the SC and then on the VMware Broker.

Managed Mode

In Managed mode, Eucalyptus manages the local network of VM instances and provides all networking features Eucalyptus Currently supports, including VM network isolation, security groups, elastic IPs, and metadata service. Configure each

CC to use an Ethernet device that lies within the same broadcast domain as all of its NCs.

CLC Configuration

no configuration.

CC Configuration

1. Log in to the CC and open the /etc/eucalyptus/eucalyptus.conf file.

2. Go to the Network Configuration section, uncomment

3  If your NCs are not reachable from end-users directly and the CC has two (or more) Ethernet devices of which one

connects to the client/public network and one connects to the NC network, or the single Ethernet device that the CC                        uses to connect to both clients and NCs is NOT ‘eth0’, then you must also uncomment and set.

4. Save the file.

5. Repeat on each CC in your system.

NC Configuration

1. Log into an NC machine and open the /etc/eucalyptus/eucalyptus.conf file.

2. Go to the Network Configuration section, uncomment and set the following:

3. Save the file.

4. Repeat on each NC.

System Mode

In System mode, Eucalyptus mostly stays out of the way in terms of VM networking, relying on your local DHCP service to configure VM networks. The NC has to specify a bridge, and that it is the bridge that is connected to an Ethernet network that has a reachable DHCP server running elsewhere that is configured to hand out IP addresses dynamically.

To configure for System mode:

CLC Configuration

No network configuration required.

CC Configuration

1. Log in to the CC and open the /etc/eucalyptus/eucalyptus.conf file.

2. Go to the Network Configuration section, uncomment and set the following:

3. Save the file.

4. Repeat on each CC in your system.