apache/cloudstack
1
0
Fork 0
mirror of https://github.com/apache/cloudstack.git synced 2025-11-02 20:02:29 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: Add more Hypervisor and Management installation

Browse Source 
This commit also renames a lot of Management Server installation files to try to get
consistency in the naming of files.

It should make it easier to identify which files are for which section.
This commit is contained in:
Wido den Hollander 2012-08-21 16:48:39 +02:00
parent b1d52c4404
commit 342481e603
21 changed files with 142 additions and 257 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/en-US/management_server_multi_node_install.xml → docs/en-US/hypervisor-host-install-agent.xml
View File

@ -1,5 +1,5 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
%BOOK_ENTITIES;
]>
@ -11,9 +11,9 @@
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
@ -22,9 +22,13 @@
under the License.
-->
<chapter id="management_server_multi_node_install">
<title>Management Server Multi-Node Installation</title>
<xi:include href="multi_node_overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="prepare_os.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="first_ms_node_install.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</chapter>
<section id="hypervisor-host-install-agent">
<title>Install and configure the Agent</title>
<para>To manage KVM instances on the host &PRODUCT; uses a Agent. This Agent communicates with the Management server and controls all the instances on the host.</para>
<para>First we start by installing the agent:</para>
<para>In RHEL or CentOS:</para>
<programlisting language="Bash">yum install cloud-agent</programlisting>
<para>In Ubuntu:</para>
<programlisting language="Bash">apt-get install cloud-agent</programlisting>
<para>The host is now ready to be added to a cluster. This is covered in a later section, see <xref linkend="host-add" />. It is recommended that you continue to read the documentation before adding the host!</para>
</section>

11
docs/en-US/hypervisor-host-install-firewall.xml
View File

@ -36,11 +36,18 @@
<para>It depends on the firewall you are using how to open these ports. Below you'll find examples how to open these ports in RHEL/CentOS and Ubuntu.</para>
<section id="hypervisor-host-install-firewall-rhel">
<title>Open ports in RHEL/CentOS</title>
<para>TODO: How to open ports</para>
<para>RHEL and CentOS use iptables for firewalling the system, you can open extra ports by executing the following iptable commands:</para>
<programlisting language="Bash">iptables -I INPUT -p tcp -m tcp --dport 22 -j ACCEPT</programlisting>
<programlisting language="Bash">iptables -I INPUT -p tcp -m tcp --dport 1798 -j ACCEPT</programlisting>
<programlisting language="Bash">iptables -I INPUT -p tcp -m tcp --dport 16509 -j ACCEPT</programlisting>
<programlisting language="Bash">iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT</programlisting>
<programlisting language="Bash">iptables -I INPUT -p tcp -m tcp --dport 49152:492160 -j ACCEPT</programlisting>
<para>These iptable settings are not persistent accross reboots, we have to save them first.</para>
<programlisting language="Bash">iptables-save > /etc/sysconfig/iptables</programlisting>
</section>
<section id="hypervisor-host-install-firewall-ubuntu">
<title>Open ports in Ubuntu</title>
<para>The default firewall under Ubuntu is UFW (Uncomplicated FireWall), although not enabled.</para>
<para>The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is a Python wrapper around iptables.</para>
<para>To open the required ports, execute the following commands:</para>
<programlisting language="Bash">ufw allow proto tcp from any to any port 22</programlisting>
<programlisting language="Bash">ufw allow proto tcp from any to any port 1798</programlisting>

1
docs/en-US/hypervisor-host-install-flow.xml
View File

@ -30,4 +30,5 @@
<xi:include href="hypervisor-host-install-security-policies.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="hypervisor-host-install-network.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="hypervisor-host-install-firewall.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="hypervisor-host-install-agent.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</section>

6
docs/en-US/hypervisor-host-install-libvirt.xml
View File

@ -35,15 +35,15 @@
</listitem>
<listitem>
<para>In order to have live migration working libvirt has to listen for unsecured TCP connections.</para>
<programlisting># vi /etc/libvirt/libvirtd.conf</programlisting>
<programlisting language="Bash">vi /etc/libvirt/libvirtd.conf</programlisting>
<para>Set the following paramaters:</para>
<programlisting>listen_tls = 0</programlisting>
<programlisting>listen_tcp = 1</programlisting>
<programlisting>tcp_port = 16059</programlisting>
<programlisting>auth_tcp none</programlisting>
<programlisting>auth_tcp = "none"</programlisting>
</listitem>
<listitem>
<para>In order to have libvirt listening on TCP we have to change the execution arguments.</para>
<para>Turning on "listen_tcp" in libvirtd.conf is not enough, we have to change the parameters as well:</para>
<para>On RHEL or CentOS:</para>
<programlisting language="Bash">vi /etc/sysconfig/libvirtd</programlisting>
<para>Uncomment the following line:</para>

16
docs/en-US/hypervisor-host-install-network.xml
View File

@ -25,18 +25,20 @@
<section id="hypervisor-host-install-network">
<title>Configure the network bridges</title>
<warning><para>This is a very important section, please make sure you read this thoroughly.</para></warning>
<para>In order to forward traffic to your instances you will need at least two bridges: public and private.</para>
<para>By default these bridges are called cloudbr0 and cloudbr1, but you do have to make sure they are available on each hypervisor.</para>
<para>In order to forward traffic to your instances you will need at least two bridges: <emphasis>public</emphasis> and <emphasis>private</emphasis>.</para>
<para>By default these bridges are called <emphasis>cloudbr0</emphasis> and <emphasis>cloudbr1</emphasis>, but you do have to make sure they are available on each hypervisor.</para>
<para>The most important factor is that you keep the configuration consistent on all your hypervisors.</para>
<section id="hypervisor-host-install-network-vlan">
<title>Network example</title>
<para>There are many ways to configure your network. In the Basic networking mode you should have two (V)LAN's, one for your private network and one for the public network.</para>
<para>The hypervisor has one NIC (eth0) with three VLAN's:</para>
<para>We assume that the hypervisor has one NIC (eth0) with three tagged VLAN's:</para>
<orderedlist>
<listitem><para>VLAN 100 for management of the hypervisor</para></listitem>
<listitem><para>VLAN 200 for public network of the instances (cloudbr0)</para></listitem>
<listitem><para>VLAN 300 for private network of the instances (cloudbr1)</para></listitem>
</orderedlist>
<para>On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with the gateway 192.168.42.1</para>
<note><para>The Hypervisor and Management server don't have to be in the same subnet!</para></note>
</section>
<section id="hypervisor-host-install-network-configure">
<title>Configuring the network bridges</title>
@ -116,18 +118,14 @@ STP=yes]]></programlisting>
<programlisting><![CDATA[auto lo
iface lo inet loopback
auto eth0.200
iface eth0.200 inet manual
auto eth0.300
iface eth0.300 inet manual
# The primary network interface
auto eth0.100
iface eth0.100 inet static
address 192.168.42.11
netmask 255.255.255.240
gateway 192.168.42.1
dns-nameservers 8.8.8.8 8.8.4.4
dns-domain lab.example.org
# Public network
auto cloudbr0

1
docs/en-US/hypervisor-host-install-overview.xml
View File

@ -26,6 +26,7 @@
<title>Hypervisor Host Installation Overview</title>
<para>This section describes installing a Hypervisor host. This is targeted towards hosts running Linux Kernel Virtual Machine (KVM)</para>
<warning><para>Before continuing, make sure that you have applied the latest updates to your host.</para></warning>
<warning><para>It is NOT recommended to run services on this host not controlled by &PRODUCT;.</para></warning>
<para>The procedure for installing the Hypervisor Host is:</para>
<orderedlist>
<listitem><para>Prepare the Operating System</para></listitem>

6
docs/en-US/hypervisor-host-install-prepare-os.xml
View File

@ -29,16 +29,16 @@
<listitem><para>Log in to your OS as root.</para></listitem>
<listitem>
<para>Check for a fully qualified hostname.</para>
<programlisting># hostname --fqdn</programlisting>
<programlisting language="Bash">hostname --fqdn</programlisting>
<para>This should return a fully qualified hostname such as "kvm1.lab.example.org". If it does not, edit /etc/hosts so that it does.</para>
</listitem>
<listitem>
<para>Make sure that the machine can reach the Internet.</para>
<programlisting># ping www.cloudstack.org</programlisting>
<programlisting language="Bash">ping www.cloudstack.org</programlisting>
</listitem>
<listitem>
<para>Turn on NTP for time synchronization.</para>
<note><para>NTP is required to synchronize the clocks of the servers in your cloud.</para></note>
<note><para>NTP is required to synchronize the clocks of the servers in your cloud. Unsynchronized clocks can cause unexpected problems.</para></note>
<orderedlist numeration="loweralpha">
<listitem><para>Install NTP</para>
<para condition="community">On RHEL or CentOS:</para>

1
docs/en-US/hypervisor-host-install-security-policies.xml
View File

@ -24,6 +24,7 @@
<section id="hypervisor-host-install-security-policies">
<title>Configure the Security Policies</title>
<para>&PRODUCT; does various things which can be blocked by security mechanisms like AppArmor and SELinux. These have to be disabled to ensure the Agent has all the required permissions.</para>
<orderedlist>
<listitem>
<para>Configure SELinux (RHEL and CentOS)</para>

58
docs/en-US/install-management-server.xml
View File

@ -1,58 +0,0 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
%BOOK_ENTITIES;
]>
<!-- Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<section id="install-management-server">
<title>Install the Management Server on the First Host</title>
<para>The first step in installation, whether you are installing the Management Server on one host or many, is to install the software on a single node.
</para>
<note><para>If you are planning to install the Management Server on multiple nodes for high availability, do not proceed to the additional nodes yet. That step will come later.</para></note>
<orderedlist>
<listitem><para>Download the Management Server onto the host where it will run. Get the software from the following link.</para>
<para condition="cloudplatform"><ulink url="https://www.citrix.com/English/ss/downloads/">https://www.citrix.com/English/ss/downloads/</ulink></para>
<para condition="cloudstack"><ulink url="FIXME">FIXME</ulink></para>
<para condition="cloudplatform">You will need a <ulink url="http://www.citrix.com/lang/English/publicindex.asp?destURL=%2FEnglish%2FmyCitrix%2Findex.asp%3F">MyCitrix account</ulink>.</para>
</listitem>
<listitem><para>Install the packages. You should have a file in the form of “&PRODUCT;-VERSION-N-OSVERSION.tar.gz”. Untar the file and then run the install.sh script inside it. Replace the file and directory names below with those you are using:</para>
<programlisting>
# tar xzf &PRODUCT;-VERSION-N-OSVERSION.tar.gz
# cd &PRODUCT;-VERSION-N-OSVERSION
# ./install.sh
</programlisting>
<para>You should see a few messages as the installer prepares, followed by a list of choices.</para>
</listitem>
<listitem><para>Choose M to install the Management Server software.</para>
<programlisting> > M</programlisting>
</listitem>
<listitem><para>Wait for a message like “Complete! Done,” which indicates that the software was installed successfully.</para>
</listitem>
<listitem><para>(RHEL or CentOS) When the installation is finished, run the following commands to start essential services (the commands might be different depending on your OS):</para>
<programlisting>
# service rpcbind start
# service nfs start
# chkconfig nfs on
# chkconfig rpcbind on
</programlisting>
</listitem>
</orderedlist>
</section>

40
docs/en-US/management-server-install-client.xml Normal file
View File

@ -0,0 +1,40 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
%BOOK_ENTITIES;
]>
<!-- Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<section id="management-server-install">
<title>Install the Management Server on the First Host</title>
<para>The first step in installation, whether you are installing the Management Server on one host or many, is to install the software on a single node.
</para>
<note><para>If you are planning to install the Management Server on multiple nodes for high availability, do not proceed to the additional nodes yet. That step will come later.</para></note>
<para>The &PRODUCT; Management server can be installed using either RPM or DEB packages. These packages will depend on everything you need to run the Management server.</para>
<section id="management-server-install-rhel">
<title>Install on CentOS/RHEL</title>
<para>We start by installing the required packages:</para>
<programlisting language="Bash">yum install cloud-client</programlisting>
</section>
<section id="management-server-install-ubuntu">
<title>Install on Ubuntu</title>
<programlisting language="Bash">apt-get install cloud-client</programlisting>
</section>
</section>

0
docs/en-US/installation-complete.xml → docs/en-US/management-server-install-complete.xml
View File

0
docs/en-US/install-database-on-separate-node.xml → docs/en-US/management-server-install-db-external.xml
View File

0
docs/en-US/install-database-on-management-server-node.xml → docs/en-US/management-server-install-db-local.xml
View File

18
docs/en-US/management-server-install-flow.xml
View File

@ -24,13 +24,13 @@
<section id="management-server-install-flow">
<title>Management Server Installation</title>
<xi:include href="management-server-installation-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="prepare-os.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="install-management-server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="install-database-on-management-server-node.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="install-database-on-separate-node.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="prepare-nfs-shares.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="install-management-server-multi-nodes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="prepare-system-vm-template.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="installation-complete.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
<xi:include href="management-server-install-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="management-server-install-prepare-os.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="management-server-install-client.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="management-server-install-db-local.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="management-server-install-db-external.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="management-server-install-nfs-shares.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="management-server-install-multi-node.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="management-server-install-systemvm.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="management-server-install-complete.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
</section>

0
docs/en-US/install-management-server-multi-nodes.xml → docs/en-US/management-server-install-multi-node.xml
View File

0
docs/en-US/prepare-nfs-shares.xml → docs/en-US/management-server-install-nfs-shares.xml
View File

2
docs/en-US/management-server-installation-overview.xml → docs/en-US/management-server-install-overview.xml
View File

@ -37,7 +37,7 @@
<orderedlist>
<listitem><para>Prepare the Operating System</para></listitem>
<listitem><para>Install the First Management Server</para></listitem>
<listitem><para>Install and Configure the Database</para></listitem>
<listitem><para>Install and Configure the MySQL database</para></listitem>
<listitem><para>Prepare NFS Shares</para></listitem>
<listitem><para>Prepare and Start Additional Management Servers (optional)</para></listitem>
<listitem><para>Prepare the System VM Template</para></listitem>

54
docs/en-US/management-server-install-prepare-os.xml Normal file
View File

@ -0,0 +1,54 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
%BOOK_ENTITIES;
]>
<!-- Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<section id="prepare-os">
<title>Prepare the Operating System</title>
<para>The OS must be prepared to host the Management Server using the following steps. These steps must be performed on each Management Server node.</para>
<orderedlist>
<listitem><para>Log in to your OS as root.</para></listitem>
<listitem>
<para>Check for a fully qualified hostname.</para>
<programlisting language="Bash">hostname --fqdn</programlisting>
<para>This should return a fully qualified hostname such as "managament1.lab.example.org". If it does not, edit /etc/hosts so that it does.</para>
</listitem>
<listitem>
<para>Make sure that the machine can reach the Internet.</para>
<programlisting language="Bash">ping www.google.com</programlisting>
</listitem>
<listitem>
<para>Turn on NTP for time synchronization.</para>
<note><para>NTP is required to synchronize the clocks of the servers in your cloud.</para></note>
<orderedlist numeration="loweralpha">
<listitem>
<para>Install NTP.</para>
<para condition="community">On RHEL or CentOS:</para>
<programlisting language="Bash">yum install ntp</programlisting>
<para condition="community">On Ubuntu:</para>
<programlisting language="Bash">apt-get install openntpd</programlisting>
</listitem>
</orderedlist>
</listitem>
<listitem><para>Repeat all of these steps on every host where the Management Server will be installed.</para></listitem>
</orderedlist>
</section>

0
docs/en-US/prepare-system-vm-template.xml → docs/en-US/management-server-install-systemvm.xml
View File

53
docs/en-US/management_server_overview.xml
View File

@ -1,53 +0,0 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
%BOOK_ENTITIES;
]>
<!-- Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<section id="management_server_overview">
<title>Management Server Overview</title>
<para>The Management Server is the &PRODUCT; software that manages cloud resources. By interacting with the Management Server through its UI or API, you can configure and manage your cloud infrastructure.</para>
<para>The Management Server runs on a dedicated server or VM. It controls allocation of virtual machines to hosts and assigns storage and IP addresses to the virtual machine instances. The &PRODUCT; Management Server runs in a Tomcat container and requires a MySQL database for persistence.</para>
<para>The machine must meet the system requirements described in System Requirements.</para>
<para>The Management Server:</para>
<itemizedlist>
<listitem>
<para>Provides the web user interface for the administrator and a reference user interface for end users.</para>
</listitem>
<listitem>
<para>Provides the APIs for the &PRODUCT; platform.</para>
</listitem>
<listitem>
<para>Manages the assignment of guest VMs to particular hosts.</para>
</listitem>
<listitem>
<para>Manages the assignment of public and private IP addresses to particular accounts.</para>
</listitem>
<listitem>
<para>Manages the allocation of storage to guests as virtual disks.</para>
</listitem>
<listitem>
<para>Manages snapshots, templates, and ISO images, possibly replicating them across data centers.</para>
</listitem>
<listitem>
<para>Provides a single point of configuration for the cloud.</para>
</listitem>
</itemizedlist>
</section>

110
docs/en-US/prepare-os.xml
View File

@ -1,110 +0,0 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
%BOOK_ENTITIES;
]>
<!-- Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<section id="prepare-os">
<title>Prepare the Operating System</title>
<para>
The OS must be prepared to host the Management Server using the following steps. These steps must be performed on each Management Server node.
</para>
<orderedlist>
<listitem><para>Log in to your OS as root.</para></listitem>
<listitem><para>Check for a fully qualified hostname.</para>
<programlisting># hostname --fqdn</programlisting>
<para>This should return a fully qualified hostname such as "kvm1.lab.example.org". If it does not, edit /etc/hosts so that it does.</para>
</listitem>
<listitem><para>Set SELinux to be permissive by default.</para>
<orderedlist numeration="loweralpha">
<listitem><para>Check to see whether SELinux is installed on your machine. If not, you can skip to step 4.</para>
<para>In RHEL or CentOS, SELinux is installed and enabled by default. You can verify this with:</para>
<programlisting># rpm -qa | grep selinux</programlisting>
<para condition="community">In Ubuntu, SELinux is not installed by default. You can verify this with:</para>
<programlisting condition="community"># dpkg --list 'selinux'</programlisting>
</listitem>
<listitem><para>Set the SELINUX variable in /etc/selinux/config to “permissive”. This ensures that the permissive setting will be maintained after a system reboot.</para>
<para condition="community">In RHEL or CentOS:</para>
<programlisting># vi /etc/selinux/config</programlisting>
<para condition="community">In Ubuntu (do this step only if SELinux was found on the machine in the previous step):</para>
<programlisting condition="community"># selinux-config-enforcing permissive</programlisting>
</listitem>
<listitem><para>Then set SELinux to permissive starting immediately, without requiring a system reboot.</para>
<para>In CentOS:</para>
<programlisting># setenforce permissive</programlisting>
<para>In RHEL:</para>
<programlisting># setenforce 0</programlisting>
<para condition="community">In Ubuntu (do this step only if SELinux was found on the machine):</para>
<programlisting condition="community"># setenforce permissive</programlisting>
</listitem>
</orderedlist>
</listitem>
<listitem><para>Make sure that the machine can reach the Internet.</para>
<programlisting># ping www.google.com</programlisting>
</listitem>
<listitem><para>(RHEL 6.2) If you do not have a Red Hat Network account, you need to prepare a local Yum repository.</para>
<orderedlist numeration="loweralpha">
<listitem><para>If you are working with a physical host, insert the RHEL 6.2 installation CD. If you are using a VM, attach the RHEL6 ISO.</para></listitem>
<listitem><para>Mount the CDROM to /media.</para></listitem>
<listitem><para>Create a repo file at /etc/yum.repos.d/rhel6.repo. In the file, insert the following lines:</para>
<programlisting>
[rhel]
name=rhel6
baseurl=file:///media
enabled=1
gpgcheck=0
</programlisting>
</listitem>
</orderedlist>
</listitem>
<listitem><para>Turn on NTP for time synchronization.</para>
<note><para>NTP is required to synchronize the clocks of the servers in your cloud.</para></note>
<orderedlist numeration="loweralpha">
<listitem><para>Install NTP.</para>
<para condition="community">On RHEL or CentOS:</para>
<programlisting># yum install ntp</programlisting>
<para condition="community">On Ubuntu:</para>
<programlisting condition="community"># apt-get install ntp</programlisting>
</listitem>
<listitem><para>Edit the NTP configuration file to point to your NTP server.</para>
<programlisting># vi /etc/ntp.conf</programlisting>
<para>Add one or more server lines in this file with the names of the NTP servers
you want to use. For example:</para>
<programlisting>server 0.xenserver.pool.ntp.org
server 1.xenserver.pool.ntp.org
server 2.xenserver.pool.ntp.org
server 3.xenserver.pool.ntp.org
</programlisting>
</listitem>
<listitem><para>Restart the NTP client.</para>
<programlisting># service ntpd restart</programlisting>
</listitem>
<listitem><para>Make sure NTP will start again upon reboot.</para>
<para condition="community">On RHEL or CentOS:</para>
<programlisting># chkconfig ntpd on</programlisting>
<para condition="community">On Ubuntu:</para>
<programlisting># chkconfig ntp on</programlisting>
</listitem>
</orderedlist>
</listitem>
<listitem><para>Repeat all of these steps on every host where the Management Server will be installed.</para></listitem>
</orderedlist>
</section>