implementation

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 supporting 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.           

·         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.