Return-Path: X-Original-To: apmail-incubator-cloudstack-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C4C11DC34 for ; Mon, 22 Oct 2012 13:24:08 +0000 (UTC) Received: (qmail 99848 invoked by uid 500); 22 Oct 2012 13:24:08 -0000 Delivered-To: apmail-incubator-cloudstack-commits-archive@incubator.apache.org Received: (qmail 99679 invoked by uid 500); 22 Oct 2012 13:24:08 -0000 Mailing-List: contact cloudstack-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-commits@incubator.apache.org Received: (qmail 99605 invoked by uid 99); 22 Oct 2012 13:24:05 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Oct 2012 13:24:05 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id 81B9845AF8; Mon, 22 Oct 2012 13:24:05 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: chipchilders@apache.org To: cloudstack-commits@incubator.apache.org X-Mailer: ASF-Git Admin Mailer Subject: [2/2] git commit: partial-fix-for-376 Message-Id: <20121022132405.81B9845AF8@tyr.zones.apache.org> Date: Mon, 22 Oct 2012 13:24:05 +0000 (UTC) partial-fix-for-376 Signed-off-by: Radhika PC Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/76478d96 Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/76478d96 Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/76478d96 Branch: refs/heads/master Commit: 76478d963bbdfe48e4c83abc0cf8d3c97c499e2c Parents: 947d8cc Author: Radhika PC Authored: Fri Oct 19 13:29:03 2012 +0530 Committer: Chip Childers Committed: Mon Oct 22 09:16:28 2012 -0400 ---------------------------------------------------------------------- docs/en-US/about-hosts.xml | 3 +- docs/en-US/management-server-install-client.xml | 42 +++++--- .../en-US/management-server-install-multi-node.xml | 82 ++++++++------- docs/en-US/management-server-install-overview.xml | 7 +- docs/en-US/prepare-system-vm-template.xml | 78 ++++++++------ 5 files changed, 123 insertions(+), 89 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/76478d96/docs/en-US/about-hosts.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/about-hosts.xml b/docs/en-US/about-hosts.xml index 956c695..49694b2 100644 --- a/docs/en-US/about-hosts.xml +++ b/docs/en-US/about-hosts.xml @@ -28,7 +28,8 @@ The host is the smallest organizational unit within a &PRODUCT; deployment. Hosts are contained within clusters, clusters are contained within pods, and pods are contained within zones. Hosts in a &PRODUCT; deployment: - Provde the CPU, memory, storage, and networking resources needed to host the virtual machines + Provide the CPU, memory, storage, and networking resources needed to host the virtual + machines Interconnect using a high bandwidth TCP/IP network and connect to the Internet May reside in multiple data centers across different geographic locations May have different capacities (different CPU speeds, different amounts of RAM, etc.), although the hosts within a cluster must all be homogeneous http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/76478d96/docs/en-US/management-server-install-client.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/management-server-install-client.xml b/docs/en-US/management-server-install-client.xml index 93273ce..7d219ac 100644 --- a/docs/en-US/management-server-install-client.xml +++ b/docs/en-US/management-server-install-client.xml @@ -21,20 +21,32 @@ specific language governing permissions and limitations under the License. --> -
- Install the Management Server on the First Host - 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. - - 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. - 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. -
- Install on CentOS/RHEL - We start by installing the required packages: - yum install cloud-client -
-
- Install on Ubuntu - apt-get install cloud-client -
+ Install the Management Server on the First Host + 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. + + 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. + + 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. +
+ Downloading vhd-util + Before setting up the Management Server, download vhd-util from vhd-util + If the Management Server is RHEL or CentOS, copy vhd-util to + /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver. + If the Management Server is Ubuntu, copy vhd-util to + /usr/lib/cloud/common/scripts/vm/hypervisor/xenserver/vhd-util. +
+
+ Install on CentOS/RHEL + We start by installing the required packages: + yum install cloud-client +
+
+ Install on Ubuntu + apt-get install cloud-client +
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/76478d96/docs/en-US/management-server-install-multi-node.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/management-server-install-multi-node.xml b/docs/en-US/management-server-install-multi-node.xml index 8ac70ac..1764fa9 100644 --- a/docs/en-US/management-server-install-multi-node.xml +++ b/docs/en-US/management-server-install-multi-node.xml @@ -21,47 +21,49 @@ specific language governing permissions and limitations under the License. --> -
- Prepare and Start Additional Management Servers - For your second and subsequent Management Servers, you will install the Management Server software, connect it to the database, and set up the OS for the Management Server. - - - - - Perform the steps in and - or - as appropriate. - - - - - Ensure that necessary services are started and set to start - on boot. - -# service rpcbind start + Prepare and Start Additional Management Servers + For your second and subsequent Management Servers, you will install the Management Server + software, connect it to the database, and set up the OS for the Management Server. + + + Perform the steps in and or as + appropriate. + + + Download vhd-util from vhd-util + If the Management Server is RHEL or CentOS, copy vhd-util to + /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver. + If the Management Server is Ubuntu, copy vhd-util to + /usr/lib/cloud/common/scripts/vm/hypervisor/xenserver/vhd-util. + + + Ensure that necessary services are started and set to start on boot. + # service rpcbind start # service nfs start # chkconfig nfs on -# chkconfig rpcbind on - - - - - - Configure the database client. Note the absence of the - --deploy-as argument in this case. - (For more details about the arguments to this command, see - .) - - - # cloud-setup-databases cloud:dbpassword@dbhost -e encryption_type -m management_server_key -k database_key - - - Configure the OS and start the Management Server: - # cloud-setup-management - The Management Server on this node should now be running. - - Repeat these steps on each additional Management Server. - Be sure to configure a load balancer for the Management Servers. See Management Server Load Balancing. - +# chkconfig rpcbind on + + + + Configure the database client. Note the absence of the --deploy-as argument in this + case. (For more details about the arguments to this command, see .) + # cloud-setup-databases cloud:dbpassword@dbhost -e encryption_type -m management_server_key -k database_key + + + Configure the OS and start the Management Server: + # cloud-setup-management + The Management Server on this node should now be running. + + + Repeat these steps on each additional Management Server. + + + Be sure to configure a load balancer for the Management Servers. See Management Server + Load Balancing. + +
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/76478d96/docs/en-US/management-server-install-overview.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/management-server-install-overview.xml b/docs/en-US/management-server-install-overview.xml index 5bc6f1b..ba4c8f6 100644 --- a/docs/en-US/management-server-install-overview.xml +++ b/docs/en-US/management-server-install-overview.xml @@ -35,7 +35,12 @@ The procedure for installing the Management Server is: - Prepare the Operating System + + Prepare the Operating System + + + Download and install vhd-util. + Install the First Management Server Install and Configure the MySQL database Prepare NFS Shares http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/76478d96/docs/en-US/prepare-system-vm-template.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/prepare-system-vm-template.xml b/docs/en-US/prepare-system-vm-template.xml index caca4e7..5ed78f7 100644 --- a/docs/en-US/prepare-system-vm-template.xml +++ b/docs/en-US/prepare-system-vm-template.xml @@ -21,37 +21,51 @@ specific language governing permissions and limitations under the License. --> -
- Prepare the System VM Template - Secondary storage must be seeded with a template that is used for &PRODUCT; system VMs. - When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text. - - On the Management Server, run one or more of the following cloud-install-sys-tmplt commands to retrieve and decompress the system VM template. Run the command for each hypervisor type that you expect end users to run in this Zone. - If your secondary storage mount point is not named /mnt/secondary, substitute your own mount point name. - If you set the &PRODUCT; database encryption type to "web" when you set up the database, you must now add the parameter -s <management-server-secret-key>. See About Password and Key Encryption. - This process will require approximately 5 GB of free space on the local file system and up to 30 minutes each time it runs. - - For XenServer: - # /usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2 -h xenserver -s <optional-management-server-secret-key> -F - - For vSphere: - # /usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.ova -h vmware -s <optional-management-server-secret-key> -F - - For KVM: - # /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 -s <optional-management-server-secret-key> -F - - - - If you are using a separate NFS server, perform this step. If you are using the Management - Server as the NFS server, you MUST NOT perform this step. - When the script has finished, unmount secondary storage and remove the created directory. - -# umount /mnt/secondary -# rmdir /mnt/secondary - - - Repeat these steps for each secondary storage server. - - + Prepare the System VM Template + Secondary storage must be seeded with a template that is used for &PRODUCT; system + VMs. + + When copying and pasting a command, be sure the command has pasted as a single line before + executing. Some document viewers may introduce unwanted line breaks in copied text. + + + + On the Management Server, run one or more of the following cloud-install-sys-tmplt + commands to retrieve and decompress the system VM template. Run the command for each + hypervisor type that you expect end users to run in this Zone. + If your secondary storage mount point is not named /mnt/secondary, substitute your own + mount point name. + If you set the &PRODUCT; database encryption type to "web" when you set up the database, + you must now add the parameter -s <management-server-secret-key>. See About Password + and Key Encryption. + This process will require approximately 5 GB of free space on the local file system and + up to 30 minutes each time it runs. + + + For XenServer: + # /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2 -h xenserver -s <optional-management-server-secret-key> -F + + + For vSphere: + # /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.ova -h vmware -s <optional-management-server-secret-key> -F + + + For KVM: + # /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -s <optional-management-server-secret-key> -F + + + + + If you are using a separate NFS server, perform this step. If you are using the + Management Server as the NFS server, you MUST NOT perform this step. + When the script has finished, unmount secondary storage and remove the created + directory. + # umount /mnt/secondary +# rmdir /mnt/secondary + + + Repeat these steps for each secondary storage server. + +