EucalyptusInstallationCentos_v1.6 のバックアップ(No.2)

バックアップ一覧
差分を表示
現在との差分を表示
ソースを表示
EucalyptusInstallationCentos_v1.6 へ行く。
- 1 (2010-03-28 (日) 11:16:32)
- 2 (2010-03-28 (日) 15:34:18)
- 3 (2010-03-28 (日) 17:55:48)

Installing Eucalyptus (1.6) on CentOS 5 †

CentOS 5にEucalyptus（1.6）をインストールする †

Eucalyptus can be installed on CentOS 5 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:

Eucalyptus を CentOS 5 にインストールするには、ソースから行う方法と、バイナリの RPM パッケージを用いる方法があります。ここではRPMパッケージでインストールする手順について記述しています。以下の手順の中で記述されている$VERSIONはインストールするバージョンに置き換えてください。例えばbashの環境変数としてセットする場合には以下のようにします。

export VERSION=1.6.2

Notice: Before you begin, please ensure that you have an up-to-date CentOS installation on your target machine(s). In particular, CentOS 5.4, which was recentely released, carries libvirt 0.6.3 which is required to run Eucalyptus.

注意：以下の手順を行う前に、CentOSを最新の状態にアップデートしてください。特にCentOS5.4では、libvert 0.6.3以降が必要です。

↑

Prerequisites †

↑

前提条件 †

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

CentOS の標準的なインストールを行った後は、Eucalyptus の動作条件を満たすために、次の作業を行います。

Front-end, node and client machine system clocks are synchronized (e.g., using NTP).
```
yum install -y ntp
ntpdate pool.ntp.org
```
Front end needs java, command to manipulate a bridge and the binaries for dhcp server (do not configure it nor run it on the CC):
```
yum install -y java-1.6.0-openjdk ant ant-nodeps dhcp bridge-utils httpd
```

Node has a fully installed and configured installation of Xen that allows controlling the hypervisor via HTTP from localhost.

yum install -y xen
sed --in-place 's/#(xend-http-server no)/(xend-http-server yes)/' /etc/xen/xend-config.sxp 
sed --in-place 's/#(xend-address localhost)/(xend-address localhost)/' /etc/xen/xend-config.sxp
/etc/init.d/xend restart

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, you may want to consider disabling the firewall and use Eucalyptus facilities for enabling custom firewall rules (see Network configuration for more information). On both the front-end and the nodes:
- For example, from a text console:
  - run system-config-securitylevel
  - select Security Level: Disabled
  - select OK
- From an X terminal:
  - run system-config-security-level
  - select 'Disabled' for 'Firewall'
  - select the 'SELinux' tab
  - select either 'Permissive' or 'Disabled' for SELinux Setting

↑

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:

Yum option: Packages are available from our yum repository. To use it, create '/etc/yum.repos.d/euca.repo' file with the following four lines:
```
[euca]
name=Eucalyptus
baseurl=http://www.eucalyptussoftware.com/downloads/repo/eucalyptus/$VERSION/yum/centos/
enabled=1
```
where $VERSION is either 1.6.1 or 1.6.2. Now install eucalyptus on the front-end,
```
yum install eucalyptus-cloud.$ARCH eucalyptus-cc.$ARCH eucalyptus-walrus.$ARCH eucalyptus-sc.$ARCH --nogpgcheck
```
or the node
```
yum install eucalyptus-nc.$ARCH --nogpgcheck
```
where $ARCH is the architecture of your host (either 'i386' or 'x86_64').

Tarball option: The packages are available in a single tarball, wherein we also include copies of third-party 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-$VERSION-*.tar.gz
cd eucalyptus-$VERSION-*

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.2-1.el5.rf.x86_64.rpm \
        lzo2-2.02-3.el5.rf.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-walrus-$VERSION-*.x86_64.rpm \
        eucalyptus-sc-$VERSION-*.x86_64.rpm \
        eucalyptus-cc-$VERSION-*.x86_64.rpm \
        eucalyptus-gl-$VERSION-*.x86_64.rpm

Install the dependency packages on each compute node:

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

Install the node controller RPM with dependencies on each compute node:

rpm -Uvh eucalyptus-$VERSION-*.x86_64.rpm \
        eucalyptus-gl-$VERSION-*.x86_64.rpm \
        eucalyptus-nc-$VERSION-*.x86_64.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

At this point you should be ready to go through the first-time configuration.