Return-Path: X-Original-To: apmail-cloudstack-commits-archive@www.apache.org Delivered-To: apmail-cloudstack-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 28C3EFE8E for ; Sat, 30 Mar 2013 09:58:49 +0000 (UTC) Received: (qmail 68170 invoked by uid 500); 30 Mar 2013 09:58:45 -0000 Delivered-To: apmail-cloudstack-commits-archive@cloudstack.apache.org Received: (qmail 67724 invoked by uid 500); 30 Mar 2013 09:58:44 -0000 Mailing-List: contact commits-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list commits@cloudstack.apache.org Received: (qmail 62461 invoked by uid 99); 30 Mar 2013 09:58:31 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Mar 2013 09:58:31 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id 176D3834561; Sat, 30 Mar 2013 09:58:31 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: widodh@apache.org To: commits@cloudstack.apache.org Date: Sat, 30 Mar 2013 09:58:39 -0000 Message-Id: In-Reply-To: <4247a17f41bc48deb8f48309d3d6aadf@git.apache.org> References: <4247a17f41bc48deb8f48309d3d6aadf@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [10/52] [abbrv] git commit: updated refs/heads/qemu-img to 44197a0 CLOUDSTACK-772 Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/d437cb6d Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/d437cb6d Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/d437cb6d Branch: refs/heads/qemu-img Commit: d437cb6dacd9614b293089fbd070af180ba3daa7 Parents: e8a144a Author: Radhika PC Authored: Thu Mar 28 10:53:05 2013 +0530 Committer: Radhika PC Committed: Thu Mar 28 10:53:52 2013 +0530 ---------------------------------------------------------------------- docs/en-US/Book_Info.xml | 39 +- docs/en-US/Installation_Guide.xml | 74 ++-- docs/en-US/add-clusters-vsphere.xml | 103 ++++- docs/en-US/images/add-cluster.png | Bin 46302 -> 35697 bytes docs/en-US/images/dvswitch-config.png | Bin 0 -> 41955 bytes docs/en-US/images/dvswitchconfig.png | Bin 0 -> 38642 bytes docs/en-US/vmware-cluster-config-dvswitch.xml | 192 ++++++++ docs/en-US/vmware-install.xml | 515 +++++++++++++------- 8 files changed, 666 insertions(+), 257 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d437cb6d/docs/en-US/Book_Info.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/Book_Info.xml b/docs/en-US/Book_Info.xml index c125ab8..be8bcdd 100644 --- a/docs/en-US/Book_Info.xml +++ b/docs/en-US/Book_Info.xml @@ -22,26 +22,23 @@ specific language governing permissions and limitations under the License. --> - - &PRODUCT; Guide - Revised August 9, 2012 10:48 pm Pacific - Apache CloudStack - 4.0.0-incubating - 1 - - - - Complete technical documentation of &PRODUCT;. - - - - - - - - - - - + &PRODUCT; Guide + Revised August 9, 2012 10:48 pm Pacific + Apache CloudStack + 4.0.0 + 1 + + + Complete technical documentation of &PRODUCT;. + + + + + + + + + + http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d437cb6d/docs/en-US/Installation_Guide.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/Installation_Guide.xml b/docs/en-US/Installation_Guide.xml index f2f27ad..fed53fc 100644 --- a/docs/en-US/Installation_Guide.xml +++ b/docs/en-US/Installation_Guide.xml @@ -11,9 +11,7 @@ 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 @@ -21,42 +19,40 @@ specific language governing permissions and limitations under the License. --> - - - &PRODUCT; Installation Guide - Apache CloudStack - 4.0.0-incubating - 1 - - - - Installation Guide for &PRODUCT;. - - - - - - - - - - - - - - - - - - - - - - - - - - - + + &PRODUCT; Installation Guide + Apache CloudStack + 4.0.0 + 1 + + + Installation Guide for &PRODUCT;. + + + + + + + + + + + + + + + + + + + + + + + + + + http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d437cb6d/docs/en-US/add-clusters-vsphere.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/add-clusters-vsphere.xml b/docs/en-US/add-clusters-vsphere.xml index 6b2dff2..ca36ee1 100644 --- a/docs/en-US/add-clusters-vsphere.xml +++ b/docs/en-US/add-clusters-vsphere.xml @@ -73,36 +73,105 @@ Provide the following information in the dialog. The fields below make reference to values from vCenter. + + + + + + addcluster.png: add a cluster + + + There might be a slight delay while the cluster is provisioned. It will automatically + display in the UI. - Cluster Name. Enter the name of the cluster you created in vCenter. For example, - "cloud.cluster.2.2.1" + Cluster Name: Enter the name of the cluster you + created in vCenter. For example, "cloud.cluster.2.2.1" + + + vCenter Username: Enter the username that &PRODUCT; + should use to connect to vCenter. This user must have all the administrative + privileges. + + + CPU overcommit ratio: Enter the CPU overcommit + ratio for the cluster. The value you enter determines the CPU consumption of each VM in + the selected cluster. By increasing the over-provisioning ratio, more resource capacity + will be used. If no value is specified, the value is defaulted to 1, which implies no + over-provisioning is done. + + + RAM overcommit ratio: Enter the RAM overcommit + ratio for the cluster. The value you enter determines the memory consumption of each VM + in the selected cluster. By increasing the over-provisioning ratio, more resource + capacity will be used. If no value is specified, the value is defaulted to 1, which + implies no over-provisioning is done. + + + vCenter Host: Enter the hostname or IP address of + the vCenter server. + + + vCenter Password: Enter the password for the user + named above. + + + vCenter Datacenter: Enter the vCenter datacenter + that the cluster is in. For example, "cloud.dc.VM". - vCenter Host. Enter the hostname or IP address of the vCenter server. + Override Public Traffic: Enable this option to + override the zone-wide public traffic for the cluster you are creating. - vCenter Username. Enter the username that &PRODUCT; should use to connect to - vCenter. This user must have all administrative privileges. + Public Traffic vSwitch Type: This option is + displayed only if you enable the Override Public Traffic option. Select a desirable + switch. If the vmware.use.dvswitch global parameter is true, the default option will be + VMware vNetwork Distributed Virtual Switch. + If you have enabled Nexus dvSwitch in the environment, the following parameters for + dvSwitch configuration are displayed: + + + Nexus dvSwitch IP Address: The IP address of the Nexus VSM appliance. + + + Nexus dvSwitch Username: The username required to access the Nexus VSM + applicance. + + + Nexus dvSwitch Password: The password associated with the username specified + above. + + - vCenter Password. Enter the password for the user named above + Override Guest Traffic: Enable this option to + override the zone-wide guest traffic for the cluster you are creating. - vCenter Datacenter. Enter the vCenter datacenter that the cluster is in. For - example, "cloud.dc.VM". + Guest Traffic vSwitch Type: This option is + displayed only if you enable the Override Guest Traffic option. Select a desirable + switch. If the vmware.use.dvswitch global parameter is true, the default option will be + VMware vNetwork Distributed Virtual Switch. + If you have enabled Nexus dvSwitch in the environment, the following parameters for + dvSwitch configuration are displayed: + + + Nexus dvSwitch IP Address: The IP address of the Nexus VSM appliance. + + + Nexus dvSwitch Username: The username required to access the Nexus VSM + applicance. + + + Nexus dvSwitch Password: The password associated with the username specified + above. + + - - - - - - addcluster.png: add cluster - - There might be a slight delay while the cluster is provisioned. It will - automatically display in the UI + automatically display in the UI. http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d437cb6d/docs/en-US/images/add-cluster.png ---------------------------------------------------------------------- diff --git a/docs/en-US/images/add-cluster.png b/docs/en-US/images/add-cluster.png index 383f375..4b24ec7 100644 Binary files a/docs/en-US/images/add-cluster.png and b/docs/en-US/images/add-cluster.png differ http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d437cb6d/docs/en-US/images/dvswitch-config.png ---------------------------------------------------------------------- diff --git a/docs/en-US/images/dvswitch-config.png b/docs/en-US/images/dvswitch-config.png new file mode 100644 index 0000000..edce6e8 Binary files /dev/null and b/docs/en-US/images/dvswitch-config.png differ http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d437cb6d/docs/en-US/images/dvswitchconfig.png ---------------------------------------------------------------------- diff --git a/docs/en-US/images/dvswitchconfig.png b/docs/en-US/images/dvswitchconfig.png new file mode 100644 index 0000000..55b1ef7 Binary files /dev/null and b/docs/en-US/images/dvswitchconfig.png differ http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d437cb6d/docs/en-US/vmware-cluster-config-dvswitch.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/vmware-cluster-config-dvswitch.xml b/docs/en-US/vmware-cluster-config-dvswitch.xml new file mode 100644 index 0000000..3e1e37c --- /dev/null +++ b/docs/en-US/vmware-cluster-config-dvswitch.xml @@ -0,0 +1,192 @@ + + +%BOOK_ENTITIES; +]> + + +
+ Configuring a vSphere Cluster with VMware Distributed Virtual Switch + &PRODUCT;supports VMware vNetwork Distributed Switch (VDS) for virtual network configuration + in a VMware vSphere environment. This section helps you configure VMware VDS in a &PRODUCT; + deployment. Each vCenter server instance can support up to 128 VDS instances and each VDS + instance can manage up to 500 VMware hosts. +
+ About VMware Distributed Virtual Switch + VMware VDS is an aggregation of host-level virtual switches on a VMware vCenter server. + VDS abstracts the configuration of individual virtual switches that span across a large number + of hosts, and enables centralized provisioning, administration, and monitoring for your entire + datacenter from a centralized interface. In effect, a VDS acts as a single virtual switch at + the datacenter level and manages networking for a number of hosts in a datacenter from a + centralized VMware vCenter server. Each VDS maintains network runtime state for VMs as they + move across multiple hosts, enabling inline monitoring and centralized firewall services. A + VDS can be deployed with or without Virtual Standard Switch and a Nexus 1000V virtual + switch. +
+
+ Prerequisites and Guidelines + + + Do not attempt to configure VDS by altering VMware traffic label when configuring + physical networks. This will only work for Standard Virtual Switch and should not be + distributed. + + + VMware VDS does not support multiple VDS per traffic type. If a user has many VDS + switches, only one can be used for Guest traffic and one for Public traffic. + + + Management and Storage network does not support VDS and use Standard Switch for these + networks. + + +
+
+ Enabling Virtual Distributed Switch in &PRODUCT; + To make a &PRODUCT; deployment VDS enabled, set the vmware.use.dvswitch parameter to true + by using the Global Settings page in the &PRODUCT; UI and restart the Management Server. + Unless you enable the vmware.use.dvswitch parameter, you cannot see any UI options specific to + VDS, and &PRODUCT; ignores the VDS-specific parameters given in the AddClusterCmd API call. + Additionally, &PRODUCT; uses VDS for virtual network infrastructure if the value of + vmware.use.dvswitch parameter is true and the value of vmware.use.nexus.dvswitch parameter is + false. + &PRODUCT; supports configuring virtual networks in a deployment with a mix of Virtual + Distributed Switch, Standard Virtual Switch and Nexus 1000v Virtual Switch. +
+
+ Configuring Distributed Virtual Switch in &PRODUCT; + You can configure VDS by adding the necessary resources while a zone is created. + + + + + + dvSwitchConfig.png: Configuring dvSwitch + + + Alternatively, you can create an additional cluster with VDS enabled in the existing zone. + Use the Add Cluster option. For information as given in . + In both these cases, you must specify the following parameters to configure VDS: + + + + + + + Parameters + Description + + + + + Cluster Name + Enter the name of the cluster you created in vCenter. For example, + "cloud.cluster". + + + vCenter Host + Enter the host name or the IP address of the vCenter host where you have + deployed the Nexus virtual switch. + + + vCenter User name + Enter the username that &PRODUCT; should use to connect to vCenter. This + user must have all administrative privileges. + + + vCenter Password + Enter the password for the user named above. + + + vCenter Datacenter + Enter the vCenter datacenter that the cluster is in. For example, + "cloud.dc.VM". + + + Override Public Traffic + Enable this option to override the zone-wide public traffic for the cluster + you are creating. + + + Public Traffic vSwitch Type + This option is displayed only if you enable the Override Public Traffic + option. Select VMware vNetwork Distributed Virtual Switch. If the + vmware.use.dvswitch global parameter is true, the default option will be VMware + vNetwork Distributed Virtual Switch. + + + Public Traffic vSwitch Name + Specify a name to identify the switch. + + + Override Guest Traffic + Enable the option to override the zone-wide guest traffic for the cluster + you are creating. + + + Guest Traffic vSwitch Type + This option is displayed only if you enable the Override Guest Traffic + option. Select VMware vNetwork Distributed Virtual Switch. If the + vmware.use.dvswitch global parameter is true, the default option will be VMware + vNetwork Distributed Virtual Switch. + + + Guest Traffic vSwitch Name + Specify a name to identify the switch. + + + + +
+
+ Removing Nexus Virtual Switch + + + In the vCenter datacenter that is served by the VMware dvSwitch, ensure that you + delete all the hosts in the corresponding cluster. + + + Log in with Admin permissions to the &PRODUCT; administrator UI. + + + In the left navigation bar, select Infrastructure. + + + In the Infrastructure page, click View all under Clusters. + + + Select the cluster where you want to remove the virtual switch. + + + In the VMware dvSwitch tab, click the name of the virtual switch. + + + In the Details page, click Delete VMware dvSwitch icon. + + + + + DeleteButton.png: button to delete dvSwitch + + + + Click Yes in the confirmation dialog box. + + +
+
http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d437cb6d/docs/en-US/vmware-install.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/vmware-install.xml b/docs/en-US/vmware-install.xml index 467e135..81c9a49 100644 --- a/docs/en-US/vmware-install.xml +++ b/docs/en-US/vmware-install.xml @@ -1,5 +1,5 @@ - %BOOK_ENTITIES; ]> @@ -11,9 +11,7 @@ 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 @@ -327,282 +325,439 @@ esxcfg-firewall -o 59000-60000,tcp,out,vncextras guide. - + + + +
Storage Preparation for vSphere (iSCSI only) Use of iSCSI requires preparatory work in vCenter. You must add an iSCSI target and create