Installing Eucalyptus (2.0) On Centos 5.5 Author: Saravanan

Installing Eucalyptus (2.0) on Centos 5.
5 Author : saravanan This document details the steps required to install Eucalyptus from RPMs. Note: Before you begin, please ensure that you have an up-to-date CentOS installation on your target machine(s). Prerequisites: If you start with a standard CentOS installation, you will satisfy all prerequisites with the following steps: 1) Front-end, node(s), and client machine system clocks are synchronized (e.g., using NTP). 2) Front end needs java, command to manipulate a bridge, and the binaries for dhcp server (do not configure or run dhcp server on the CC): 3) Node has a fully installed and configured installation of Xen that allows controlling the hypervisor via HTTP from localhost. 4) Firewall rules must permit the Eucalyptus components to communicate with one another, and clients to communicate with Eucalyptus. 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, consider disabling the firewall and use Eucalyptus facilities for enabling custom firewall rules. RPM Installation: The packages are available in a single tarball, wherein we also include copies of thirdparty CentOS packages that Eucalyptus depends on (Rampart, Axis2C, many Java libraries), at http://open.eucalyptus.com/downloads (look for a CentOS tarball of the right Eucalyptus version and architecture). Untar the bundle in a temporary location: tar zxvf eucalyptus-2.0.0-centos-i386.tar.gz cd eucalyptus-2.0.0-centos-i386/ Install RPMs on the front end First, on the front end, install third-party dependency RPMs: cd eucalyptus-2.0.0-centos-i386/eucalyptus-2.0.0-rpm-deps-i386/ [email protected]
rpm -Uvh aoetools-21-1.el4.i386.rpm rpm -Uvh euca-axis2c-1.6.0-1.i386.rpm rpm -Uvh euca-rampartc-1.3.0-1.i386.rpm rpm -Uvh vblade-14-1mdv2008.1.i586.rpm rpm -ivh lzo2-2.02-3.el5.rf.i386.rpm rpm -Uvh vtun-3.0.2-1.el5.rf.i386.rpm rpm Uvh perl-Crypt-OpenSSL-Random-0.04-1.el5.rf.i386.rpm rpm Uvh perl-Crypt-OpenSSL-RSA-0.25-1.el5.rf.i386.rpm rpm Uvh perl-Crypt-X509-0.32-1.el5.rf.noarch.rpm rpm Uvh python25-libs-2.5.1-bashton1.i386.rpm rpm Uvh python25-2.5.1-bashton1.i386.rpm rpm Uvh python25-devel-2.5.1-bashton1.i386.rpm then install the -cloud, -walrus, -cc and -sc RPMs: rpm -Uvh eucalyptus-2.0.0-1.i386.rpm rpm Uvh eucalyptus-common-java-2.0.0-1.i386.rpm rpm Uvh eucalyptus-cloud-2.0.0-1.i386.rpm rpm Uvh eucalyptus-walrus-2.0.0-1.i386.rpm rpm Uvh eucalyptus-sc-2.0.0-1.i386.rpm rpm Uvh eucalyptus-cc-2.0.0-1.i386.rpm Install RPMs on the nodes Next, on each node install the dependency packages: cd eucalyptus-2.0.0-centos-i386/eucalyptus-2.0.0-rpm-deps-i386 rpm Uvh aoetools-21-1.el4.i386.rpm rpm Uvh euca-axis2c-1.6.0-1.i386.rpm rpm Uvh euca-rampartc-1.3.0-1.i386.rpm rpm Uvh vblade-14-1mdv2008.1.i586.rpm rpm -Uvh lzo2-2.02-3.el5.rf.i386.rpm rpm -Uvh vtun-3.0.2-1.el5.rf.i386.rpm rpm -Uvh perl-Crypt-OpenSSL-Random-0.04-1.el5.rf.i386.rpm rpm -Uvh perl-Crypt-OpenSSL-RSA-0.25-1.el5.rf.i386.rpm rpm -Uvh perl-Crypt-X509-0.32-1.el5.rf.noarch.rpm rpm Uvh python25-libs-2.5.1-bashton1.i386.rpm rpm Uvh python25-2.5.1-bashton1.i386.rpm rpm Uvh python25-devel-2.5.1-bashton1.i386.rpm then install the node controller RPM with dependencies: rpm Uvh eucalyptus-2.0.0-1.i386.rpm rpm Uvh eucalyptus-gl-2.0.0-1.i386.rpm
rpm Uvh eucalyptus-nc-2.0.0-1.i386.rpm Post-Install Steps The last step in the installation is to make sure that the user 'eucalyptus', which is created at RPM installation time, is configured to interact with the hypervisor through libvirt on all of your compute nodes. The easiest way to check this is to run the following command on each node: su eucalyptus -c "virsh list" The output of that command may include error messages (failed to connect to xend), but as long as it includes a listing of all domains (at least Domain-0), the configuration is in order. 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 Configuration: This section of Guide describes how to configure Eucalyptus, both during installation and after a decision to reconfigure parts of the system. After you've started all components, you will need to perform registration so that they can communicate with each other. Registering Eucalyptus Components This section will assume that you have installed all Eucalyptus components and they are up and running. We will assume that your Eucalyptus setup consists of one front end and one or more nodes. First, you will need to register various front end components. To do this, run the following commands on the front end. euca_conf --register-walrus <front end IP address> euca_conf --register-cluster <clustername> <front end IP address> euca_conf --register-sc <clustername> <front end IP address> Finally, you need to register nodes with the front end. To do so, run the following command on the front end, euca_conf --register-nodes "<Node 0 IP address> <Node 1 IP address> ... <Node N IP address>"
where "<Node X IP address>" is the IP address of host X that is running the Node Controller (NC). At this point, you have successfully registered Eucalyptus components and are ready to begin your initial configuration. Initial Configuration Point your browser to, https://front-end-ip:8443 Since Eucalyptus is using a self-signed certificate, your browser is likely to prompt you to accept the certificate. On some machines it may take few minutes after the starting of the Cloud Controller for the URL to be responsive the first time you run Eucalyptus. You will be prompted for a user and password both of which are set to admin initially. Upon logging in the first time you will be asked to change the admin password, set the admin's email address, and confirm the IP of the Cloud Controller host. After clicking 'Submit', you will see the 'Configuration' tab. Since you've used euca_conf to register Walrus and a cluster, they will be listed along with a few configurable parameters. Look over the parameters to see if any need adjustment. For more information, see the Management section. To use the system with client tools, you must obtain user credentials. From the 'Credentials' tab, Eucalyptus users can obtain two types of credentials: x509 certificates and query interface credentials. Use the 'Download Credentials' button to download a zipfile with both or click on the 'Show Keys' to see the query interface credentials. You will be able to use your credentials with Euca2ools, Amazon EC2 tools and third-party tools like rightscale.com. Create a directory to store your credentials, unpack the zip-file into it, and source the included 'eucarc': mkdir $HOME/.euca unzip euca2-admin-x509.zip -d $HOME/.euca . $HOME/.euca/eucarc Note that you will have to source this file every time you intend to use the command-line tools, or you may add it to your local default environment.

Installing Eucalyptus (2.0) On Centos 5.5 Author: Saravanan

Uploaded by

Copyright:

Available Formats

Installing Eucalyptus (2.0) On Centos 5.5 Author: Saravanan

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installing Eucalyptus (2.0) On Centos 5.5 Author: Saravanan

Uploaded by

Copyright:

Available Formats

Installing Eucalyptus (2.0) on Centos 5.

You might also like