From 32c519a8ae376cc860a8f65e0c15fa4b4ef24cf2 Mon Sep 17 00:00:00 2001 From: David Nalley Date: Tue, 29 Jan 2013 00:17:06 -0500 Subject: [PATCH] first pass at fixing runbook for ACS4.0.x --- docs/runbook/en-US/Book_Info.xml | 2 +- docs/runbook/en-US/Environment.xml | 36 +++++++-- docs/runbook/en-US/Management.xml | 37 ++------- docs/runbook/en-US/Overview.xml | 17 ++-- docs/runbook/en-US/Revision_History.xml | 9 +++ docs/runbook/en-US/config.xml | 2 +- docs/runbook/en-US/kvm.xml | 103 +++++++++++++++++------- 7 files changed, 127 insertions(+), 79 deletions(-) diff --git a/docs/runbook/en-US/Book_Info.xml b/docs/runbook/en-US/Book_Info.xml index ec591446856..5d2014beb9a 100644 --- a/docs/runbook/en-US/Book_Info.xml +++ b/docs/runbook/en-US/Book_Info.xml @@ -27,7 +27,7 @@ Runbook Prescriptive instructions for deploying Apache CloudStack Apache CloudStack - 3.0.2 + 4.0.1 0 0 diff --git a/docs/runbook/en-US/Environment.xml b/docs/runbook/en-US/Environment.xml index 781e05de182..4172e031e98 100644 --- a/docs/runbook/en-US/Environment.xml +++ b/docs/runbook/en-US/Environment.xml @@ -32,7 +32,7 @@
Operating System - Using the CentOS 6.2 x86_64 minimal install ISO, you'll need to install CentOS + Using the CentOS 6.3 x86_64 minimal install ISO, you'll need to install CentOS on your hardware. The defaults will generally be acceptable for this installation. @@ -163,6 +163,30 @@ SELINUXTYPE=targeted # chkconfig ntpd on # service ntpd start
+
+ Configuring the CloudStack Package Repository + + We need to configure the machine to use a CloudStack package repository. + + The below repository is not an official Apache CloudStack project repository + + The Apache CloudStack official releases are source code. As such there are no + 'official' binaries available. The full installation guide describes how to take + the source release and generate RPMs and and yum repository. This guide attempts + to keep things as simple as possible, and thus we are using one of the + community-provided yum repositories. + + + + To add the CloudStack repository, create /etc/yum.repos.d/cloudstack.repo and insert the following information. + +[cloudstack] +name=cloudstack +baseurl=http://cloudstack.apt-get.eu/rhel/4.0/ +enabled=1 +gpgcheck=0 + +
NFS @@ -224,12 +248,10 @@ STATD_OUTGOING_PORT=2020 We now need to configure nfs service to start on boot and actually start it on the host by executing the following commands: - # service rpcbind start - # service nfs start - # chkconfig rpcbind on - # chkconfig nfs on +# service rpcbind start +# service nfs start +# chkconfig rpcbind on +# chkconfig nfs on
- - diff --git a/docs/runbook/en-US/Management.xml b/docs/runbook/en-US/Management.xml index 0df2bf118f9..f954561c9a4 100644 --- a/docs/runbook/en-US/Management.xml +++ b/docs/runbook/en-US/Management.xml @@ -54,45 +54,26 @@ binlog-format = 'ROW' Now that MySQL is properly configured we can start it and configure it to start on boot as follows: - # service mysqld start - # chkconfig mysqld on +# service mysqld start +# chkconfig mysqld on -
- Extraction - - The next step is to extract the contents of the CloudStack tarball - (mentioned in ) you - downloaded previously. To extract the contents of this tarball use - the following command: - - - # tar -xzvf CloudStack-oss-3.0.2-1-rhel6.2.tar.gz - - For the next few sections you'll need to cd into the first level that was just created. - -
Installation - Now that you are in the directory created by extracting the tarball, it's now time to install. We'll run - ./install.sh and choose option . This will install the management server - and necessary dependencies. + We are now going to install the management server. We do that by executing the following command: + # yum -y install cloud-client With the application itself installed we can now setup the database, we'll do that with the following command and options: - - # cloud-setup-databases cloud:password@localhost --deploy-as=root - + # cloud-setup-databases cloud:password@localhost --deploy-as=root When this process is finished, you should see a message like "CloudStack has successfully initialized the database." Now that the database has been created, we can take the final step in setting up the management server by issuing the following command: - - # cloud-setup-mangament - + # cloud-setup-mangament
System Template Setup @@ -107,16 +88,14 @@ binlog-format = 'ROW' storage share that we setup earlier, so we'll need to mount that share with the mount command run on the management server: - - # mount -t nfs 172.16.10.2:/secondary /mnt/secondary + # mount -t nfs 172.16.10.2:/secondary /mnt/secondary Now we need to download the system VM template and deploy that to the share we just mounted. The management server includes a script to properly manipulate the system VMs images. - - # /usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -F + # /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -F That concludes our setup of the management server. We still need to diff --git a/docs/runbook/en-US/Overview.xml b/docs/runbook/en-US/Overview.xml index f69798fdb67..d686bf4aef6 100644 --- a/docs/runbook/en-US/Overview.xml +++ b/docs/runbook/en-US/Overview.xml @@ -36,7 +36,7 @@ What exactly are we building? This runbook will focus on building a CloudStack cloud using KVM with - CentOS 6.2 with NFS storage on a flat layer-2 network utilizing + CentOS 6.3 with NFS storage on a flat layer-2 network utilizing layer-3 network isolation (aka Security Groups), and doing it all on a single piece of hardware. @@ -74,23 +74,16 @@ The - - CentOS 6.2 x86_64 minimal install CD + + CentOS 6.3 x86_64 minimal install CD A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP should be on this network and - none of the computers running CloudStack may have a dynamic address. - - - - - Copy of - - CloudStack 3.0.2 for RHEL and CentOS 6.2 - + none of the computers running CloudStack will have a dynamic address. Again this is done for + the sake of simplicity. diff --git a/docs/runbook/en-US/Revision_History.xml b/docs/runbook/en-US/Revision_History.xml index 4aecafd1d66..78340ea2a1e 100644 --- a/docs/runbook/en-US/Revision_History.xml +++ b/docs/runbook/en-US/Revision_History.xml @@ -27,6 +27,15 @@ Revision History + + 1 + Fri Feb 1 2013 + + + Updating for Apache CloudStack 4.0.1 + + + 0-0 Mon Jun 25 2012 diff --git a/docs/runbook/en-US/config.xml b/docs/runbook/en-US/config.xml index 90c34957fb1..da9b1ca35cd 100644 --- a/docs/runbook/en-US/config.xml +++ b/docs/runbook/en-US/config.xml @@ -142,7 +142,7 @@
Primary Storage - With you cluster now setup - you should be prompted for primary storage information. Choose NFS as the storage type and then enter the following values in the fields: + With your cluster now setup - you should be prompted for primary storage information. Choose NFS as the storage type and then enter the following values in the fields: Name - We'll use 'Primary1' diff --git a/docs/runbook/en-US/kvm.xml b/docs/runbook/en-US/kvm.xml index 03119496a2c..f6b61c25ac9 100644 --- a/docs/runbook/en-US/kvm.xml +++ b/docs/runbook/en-US/kvm.xml @@ -59,6 +59,11 @@ + + + + + @@ -66,37 +71,77 @@ any additional hosts will need for you to complete the above steps.
- +
Installation - - You'll need to ensure that you are in the directory that was created when - we extracted the the tarball. - - - - You'll be running ./install.sh again and this time - choosing which will install the software necessary for - managing a KVM node. - -
-
- KVM Configuration - - KVM configuration is relatively simple at only a single item. We need to - edit the QEMU VNC configuration. This is done by editing - /etc/libvirt/qemu.conf and ensuring the following - line is present and uncommented. - vnc_listen=0.0.0.0 - - - You can now just restart the libvirt daemon by issuing the following command: - # service libvirt restart - - - That concludes our installation and configuration of KVM, and we'll now move to using the CloudStack UI - for the actual configuration of our cloud. - + Installation of the KVM agent is trivial with just a single command, but afterwards we'll need to configure a few things. + # yum -y install cloud-agent +
+ KVM Configuration + We have two different parts of KVM to configure, libvirt, and QEMU. +
+ QEMU Configuration + + KVM configuration is relatively simple at only a single item. We need to + edit the QEMU VNC configuration. This is done by editing + /etc/libvirt/qemu.conf and ensuring the following + line is present and uncommented. + vnc_listen=0.0.0.0 + + + You can now just restart the libvirt daemon by issuing the following command: + # service libvirt restart + +
+
+ Libvirt Configuration + + CloudStack uses libvirt for managing virtual machines. Therefore it + is vital that libvirt is configured correctly. Libvirt is a dependency + of cloud-agent and should already be installed. + + + + In order to have live migration working libvirt has to listen + for unsecured TCP connections. We also need to turn off libvirts + attempt to use Multicast DNS advertising. Both of these settings + are in /etc/libvirt/libvirtd.conf + + Set the following paramaters: + listen_tls = 0 + listen_tcp = 1 + tcp_port = 16059 + auth_tcp = "none" + mdns_adv = 0 + + + Turning on "listen_tcp" in libvirtd.conf is not enough, we have to change the parameters as well: + On RHEL or CentOS modify /etc/sysconfig/libvirtd: + Uncomment the following line: + #LIBVIRTD_ARGS="--listen" + On Ubuntu: modify /etc/init/libvirt-bin.conf + Change the following line (at the end of the file): + exec /usr/sbin/libvirtd -d + to (just add -l) + exec /usr/sbin/libvirtd -d -l + + + Restart libvirt + In RHEL or CentOS: + $ service libvirtd restart + In Ubuntu: + $ service libvirt-bin restart + + +
+
+ KVM configuration complete + + That concludes our installation and configuration of KVM, and we'll now move to using the CloudStack UI + for the actual configuration of our cloud. + +
+