Repository: cloudstack-docs-install Updated Branches: refs/heads/master 5447dae06 -> b1f7a0f01
fixed links in hypervisor_installation, installation, network_setup: Closes #7 Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/commit/b1f7a0f0 Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/tree/b1f7a0f0 Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/diff/b1f7a0f0 Branch: refs/heads/master Commit: b1f7a0f01b40a34fd803a93cb248b3ba19333111 Parents: 5447dae Author: Pierre-Luc Dion <[email protected]> Authored: Thu Mar 27 21:32:02 2014 -0400 Committer: Sebastien Goasguen <[email protected]> Committed: Fri Mar 28 06:46:06 2014 -0400 ---------------------------------------------------------------------- .gitignore | 13 +++ source/_static/images/acslogo.png | Bin 0 -> 135394 bytes source/_static/images/monkey.png | Bin 0 -> 30274 bytes source/hypervisor_installation.rst | 180 +++++++++++++++----------------- source/index.rst | 11 ++ source/installation.rst | 126 +++++++++------------- source/network_setup.rst | 45 +++----- 7 files changed, 178 insertions(+), 197 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/b1f7a0f0/.gitignore ---------------------------------------------------------------------- diff --git a/.gitignore b/.gitignore index b885e35..9029067 100644 --- a/.gitignore +++ b/.gitignore @@ -15,3 +15,16 @@ # under the License. /build + +# OS generated files # +###################### +*/.DS_Store +.DS_Store +.DS_Store? +._* +.Spotlight-V100 +.Trashes +Icon? +ehthumbs.db +Thumbs.db + http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/b1f7a0f0/source/_static/images/acslogo.png ---------------------------------------------------------------------- diff --git a/source/_static/images/acslogo.png b/source/_static/images/acslogo.png new file mode 100644 index 0000000..a938231 Binary files /dev/null and b/source/_static/images/acslogo.png differ http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/b1f7a0f0/source/_static/images/monkey.png ---------------------------------------------------------------------- diff --git a/source/_static/images/monkey.png b/source/_static/images/monkey.png new file mode 100644 index 0000000..37928d5 Binary files /dev/null and b/source/_static/images/monkey.png differ http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/b1f7a0f0/source/hypervisor_installation.rst ---------------------------------------------------------------------- diff --git a/source/hypervisor_installation.rst b/source/hypervisor_installation.rst index 70b0df2..91a4c9f 100644 --- a/source/hypervisor_installation.rst +++ b/source/hypervisor_installation.rst @@ -203,7 +203,7 @@ In Ubuntu: $ apt-get install cloudstack-agent The host is now ready to be added to a cluster. This is covered in a -later section, see `Section 6.6, âAdding a Hostâ <#host-add>`__. It is +later section, see :ref:`adding-a-host`. It is recommended that you continue to read the documentation before adding the host! @@ -941,7 +941,7 @@ Add the host to CloudStack ~~~~~~~~~~~~~~~~~~~~~~~~~~ The host is now ready to be added to a cluster. This is covered in a -later section, see `Section 6.6, âAdding a Hostâ <#host-add>`__. It is +later section, see :ref:`adding-a-host`. It is recommended that you continue to read the documentation before adding the host! @@ -1000,8 +1000,7 @@ If you want to use the Citrix XenServer hypervisor to run guest virtual machines, install XenServer 6.0 or XenServer 6.0.2 on the host(s) in your cloud. For an initial installation, follow the steps below. If you have previously installed XenServer and want to upgrade to another -version, see `Section 8.2.11, âUpgrading XenServer -Versionsâ <#xenserver-version-upgrading>`__. +version, see :ref:`upgrading-xenserver-version`. System Requirements for XenServer Hosts ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -1010,19 +1009,13 @@ System Requirements for XenServer Hosts The host must be certified as compatible with one of the following. See the Citrix Hardware Compatibility Guide: - `http://hcl.xensource.com <http://hcl.xensource.com>`__ + `http://hcl.xensource.com <http://hcl.xensource.com>`_ - - - - XenServer 5.6 SP2 - - - - - XenServer 6.0 - - - - - XenServer 6.0.2 + - XenServer 5.6 SP2 + - XenServer 6.0 + - XenServer 6.0.2 + - XenServer 6.1.0 + - XenServer 6.2.0 - @@ -1090,10 +1083,9 @@ XenServer Installation Steps #. From - `https://www.citrix.com/English/ss/downloads/ <https://www.citrix.com/English/ss/downloads/>`__, + `https://www.citrix.com/English/ss/downloads/ <https://www.citrix.com/English/ss/downloads/>`_, download the appropriate version of XenServer for your CloudStack - version (see `Section 8.2.1, âSystem Requirements for XenServer - Hostsâ <#system-requirements-xenserver-hosts>`__). Install it using + version (see `"System Requirements for XenServer Hosts" <#system-requirements-for-xenserver-hosts>`_). Install it using the Citrix XenServer Installation Guide. Older Versions of XenServer: @@ -1110,7 +1102,7 @@ Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see -`http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`__. +`http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`_. The article refers to XenServer 5.6, but the same information applies to XenServer 6.0. @@ -1186,15 +1178,15 @@ steps on each XenServer host. For XenServer 6.0.2: - `http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz>`__ + `http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz>`_ For XenServer 5.6 SP2: - `http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz>`__ + `http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz>`_ For XenServer 6.0: - `http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz>`__ + `http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz>`_ #. @@ -1255,7 +1247,7 @@ that XenServer. #. - Repeat step `2 <#rescan-scsi>`__ on every host. + Repeat step 2 on every host. #. @@ -1275,7 +1267,7 @@ that XenServer. #. - Repeat step `4 <#verify-scsi>`__ on every host. + Repeat step 4 on every host. #. @@ -1322,8 +1314,7 @@ that XenServer. # xe sr-param-set uuid=7a143820-e893-6c6a-236e-472da6ee66bf name-description="Fiber Channel storage repository" Make note of the values you will need when you add this storage to - CloudStack later (see `Section 6.7, âAdd Primary - Storageâ <#primary-storage-add>`__). In the Add Primary Storage + CloudStack later (see `"Add Primary Storage" <configuration.html#add-primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you will choose PreSetup. In SR Name-Label, you will enter the name-label you set earlier (in this example, e6849e96-86c3-4f2c-8fcc-350cc711be3d). @@ -1345,18 +1336,17 @@ following links provide a starting point: - - `http://support.citrix.com/article/CTX118791 <http://support.citrix.com/article/CTX118791>`__ + `http://support.citrix.com/article/CTX118791 <http://support.citrix.com/article/CTX118791>`_ - - `http://support.citrix.com/article/CTX125403 <http://support.citrix.com/article/CTX125403>`__ + `http://support.citrix.com/article/CTX125403 <http://support.citrix.com/article/CTX125403>`_ You can also ask your SAN vendor for advice about setting up your Citrix repository for multipathing. Make note of the values you will need when you add this storage to the -CloudStack later (see `Section 6.7, âAdd Primary -Storageâ <#primary-storage-add>`__). In the Add Primary Storage dialog, +CloudStack later (see `"Add Primary Storage" <configuration.html#add-primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you will choose PreSetup. In SR Name-Label, you will enter the same name used to create the SR. @@ -1403,8 +1393,7 @@ Configuring Public Network with a Dedicated NIC for XenServer (Optional) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ CloudStack supports the use of a second NIC (or bonded pair of NICs, -described in `Section 8.2.10.4, âNIC Bonding for XenServer -(Optional)â <#xenserver-nic-bonding>`__) for the public network. If +described in :ref:`nic-bonding-for-xenserver`) for the public network. If bonding is not used, the public network can be on any NIC and can be on different NICs on the hosts in a cluster. For example, the public network can be on eth0 on node A and eth1 on node B. However, the @@ -1412,12 +1401,10 @@ XenServer name-label for the public network must be identical across all hosts. The following examples set the network label to "cloud-public". After the management server is installed and running you must configure it with the name of the chosen network label (e.g. "cloud-public"); this -is discussed in `Section 4.5, âManagement Server -Installationâ <#management-server-install-flow>`__. +is discussed in `"Management Server Installation" <installation.html#management-server-installation>`_. If you are using two NICs bonded together to create a public network, -see `Section 8.2.10.4, âNIC Bonding for XenServer -(Optional)â <#xenserver-nic-bonding>`__. +see :ref:`nic-bonding-for-xenserver`. If you are using a single dedicated NIC to provide public network access, follow this procedure on each new host that is added to @@ -1507,6 +1494,8 @@ Here is an example to set up eth5 to access a storage network on device ( RO): eth5 #xe pif-reconfigure-ip DNS=172.16.3.3 gateway=172.16.0.1 IP=172.16.0.55 mode=static netmask=255.255.255.0 uuid=ab0d3dd4-5744-8fae-9693-a022c7a3471d +.. _nic-bonding-for-xenserver: + NIC Bonding for XenServer (Optional) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -1680,6 +1669,8 @@ all hosts in the cluster. Now the bonds are set up and configured properly across the cluster. +.. _upgrading-xenserver-version: + Upgrading XenServer Versions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -1869,9 +1860,10 @@ To upgrade XenServer: # for host in $(xe host-list | grep ^uuid | awk '{print $NF}') ; do xe host-param-clear uuid=$host param-name=tags; done; - .. note:: 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. + .. note:: + 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. #. @@ -1960,9 +1952,9 @@ Preparation Checklist for Hyper-V For a smoother installation, gather the following information before you start: -Hyper-V Requirements +Hyper-V Requirements -Value +Value Description @@ -1971,8 +1963,7 @@ Server Roles Hyper-V After the Windows Server 2012 R2 installation, ensure that Hyper-V is -selected from Server Roles. For more information, see `Installing -Hyper-V <http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step2>`__. +selected from Server Roles. For more information, see `Installing Hyper-V <http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step2>`_. Share Location @@ -2053,8 +2044,7 @@ Migration Enable Migration. -For more information, see `Configuring Live -Migration <http://technet.microsoft.com/en-us/library/jj134199.aspx%20>`__. +For more information, see `Configuring Live Migration <http://technet.microsoft.com/en-us/library/jj134199.aspx>`_. Migration @@ -2081,13 +2071,11 @@ Hyper-V Installation Steps #. - Download the operating system from `Windows Server 2012 - R2 <http://technet.microsoft.com/en-us/windowsserver/hh534429>`__ . + Download the operating system from `Windows Server 2012 R2 <http://technet.microsoft.com/en-us/windowsserver/hh534429>`_. #. - Install it on the host as given in `Install and Deploy Windows Server - 2012 R2 <http://technet.microsoft.com/library/hh831620>`__. + Install it on the host as given in `Install and Deploy Windows Server 2012 R2 <http://technet.microsoft.com/library/hh831620>`_. #. @@ -2123,7 +2111,8 @@ CloudStack Management Server communicates with Hyper-V Agent by using HTTPS. For secure communication between the Management Server and the host, install a self-signed certificate on port 8250. -.. note:: The Agent installer automatically perform this operation. You have not selected this option during the Agent installation, it can also be done manually as given in step 1. +.. note:: + The Agent installer automatically perform this operation. You have not selected this option during the Agent installation, it can also be done manually as given in step 1. #. @@ -2193,14 +2182,12 @@ Secondary Storage that uses SMB. Create a SMB storage and expose it over SMB Version 3. - For more information, see `Deploying Hyper-V over - SMB <http://technet.microsoft.com/en-us/library/jj134187.aspx>`__. + For more information, see `Deploying Hyper-V over SMB <http://technet.microsoft.com/en-us/library/jj134187.aspx>`_. You can also create and export SMB share using Windows. After the Windows Server 2012 R2 installation, select File and Storage Services from Server Roles to create an SMB file share. For more information, - see `Creating an SMB File Share Using Server - Manager <http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step3>`__. + see `Creating an SMB File Share Using Server Manager <http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step3>`_. #. @@ -2234,7 +2221,7 @@ Software requirements: vSphere Standard is recommended. Note however that customers need to consider the CPU constraints in place with vSphere licensing. See - `http://www.vmware.com/files/pdf/vsphere\_pricing.pdf <http://www.vmware.com/files/pdf/vsphere_pricing.pdf>`__ + `http://www.vmware.com/files/pdf/vsphere\_pricing.pdf <http://www.vmware.com/files/pdf/vsphere_pricing.pdf>`_ and discuss with your VMware sales representative. vCenter Server Standard is recommended. @@ -2259,7 +2246,7 @@ Hardware requirements: The host must be certified as compatible with vSphere. See the VMware Hardware Compatibility Guide at - `http://www.vmware.com/resources/compatibility/search.php <http://www.vmware.com/resources/compatibility/search.php>`__. + `http://www.vmware.com/resources/compatibility/search.php <http://www.vmware.com/resources/compatibility/search.php>`_. - @@ -2324,9 +2311,7 @@ vCenter Server requirements: Networking - 1Gbit or 10Gbit. -For more information, see "vCenter Server and the vSphere Client -Hardware Requirements" at -`http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c\_vc\_hw.html <http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_vc_hw.html>`__. +For more information, see `"vCenter Server and the vSphere Client Hardware Requirements" <http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_vc_hw.html>`_. Other requirements: ^^^^^^^^^^^^^^^^^^^ @@ -2362,8 +2347,7 @@ Other requirements: The CloudStack management network must not be configured as a separate virtual network. The CloudStack management network is the same as the vCenter management network, and will inherit its - configuration. See `Section 8.4.5.2, âConfigure vCenter Management - Networkâ <#vmware-physical-host-networking-config-vcenter-mgt>`__. + configuration. See :ref:`configure-vcenter-management-network`. - @@ -2406,13 +2390,13 @@ start: - - Information listed in `Section 8.4.2.1, âvCenter - Checklistâ <#vmware-vcenter-checklist>`__ + Information listed in :ref:`vcenter-checklist` - - Information listed in `Section 8.4.2.2, âNetworking Checklist for - VMwareâ <#vmware-network-checklist>`__ + Information listed in :ref:`networking-checklist-for-vmware` + +.. _vcenter-checklist: vCenter Checklist ^^^^^^^^^^^^^^^^^ @@ -2428,6 +2412,8 @@ vCenter Datacenter Name Name of the datacenter. vCenter Cluster Name Name of the cluster. ======================== ===================================== +.. _networking-checklist-for-vmware: + Networking Checklist for VMware ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -2459,7 +2445,7 @@ vSphere Installation Steps If you haven't already, you'll need to download and purchase vSphere from the VMware Website - (`https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1 <https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1>`__) + (`https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1 <https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1>`_) and install it by following the VMware vSphere Installation Guide. #. @@ -2541,6 +2527,8 @@ In this dialog, you can change the number of switch ports. After you've done that, ESXi hosts are required to reboot in order for the setting to take effect. +.. _configure-vcenter-management-network: + Configure vCenter Management Network ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -2610,8 +2598,8 @@ CloudStack supports Cisco Nexus 1000v dvSwitch (Distributed Virtual Switch) for virtual network configuration in a VMware vSphere environment. This section helps you configure a vSphere cluster with Nexus 1000v virtual switch in a VMware vCenter environment. For -information on creating a vSphere cluster, see `Section 8.4, âVMware -vSphere Installation and Configurationâ <#vmware-install>`__ +information on creating a vSphere cluster, see +`"VMware vSphere Installation and Configuration" <#vmware-vsphere-installation-and-configuration>`_ About Cisco Nexus 1000v Distributed Virtual Switch ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -2665,7 +2653,7 @@ ensure that your system meets the following requirements: CloudStack doesn't have to deal with dynamic migration of virtual adapters or networks across other existing virtual switches. See `Cisco Nexus 1000V Installation and Upgrade - Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/install_upgrade/vsm_vem/guide/n1000v_installupgrade.html>`__ + Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/install_upgrade/vsm_vem/guide/n1000v_installupgrade.html>`_ for guidelines on how to install the Nexus 1000v VSM and VEM modules. - @@ -2689,9 +2677,9 @@ ensure that your system meets the following requirements: - - All information given in `Section 8.4.6.3, âNexus 1000v Virtual - Switch - Preconfigurationâ <#vmware-vsphere-cluster-config-nexus-vswitch-preconfig>`__ + All information given in :ref:`nexus-vswift-preconf` + +.. _nexus-vswift-preconf: Nexus 1000v Virtual Switch Preconfiguration ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -2753,8 +2741,7 @@ CloudStack UI: .. note:: The VLANs used for control, packet, and management port groups can be the same. -For more information, see `Cisco Nexus 1000V Getting Started -Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_b/getting_started/configuration/guide/n1000v_gsg.pdf>`__. +For more information, see `Cisco Nexus 1000V Getting Started Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_b/getting_started/configuration/guide/n1000v_gsg.pdf>`_. VSM Configuration Checklist ''''''''''''''''''''''''''' @@ -2767,8 +2754,8 @@ You will need the following VSM configuration parameters: This is the IP address of the VSM appliance. This is the IP address you specify in the virtual switch IP Address field while configuting Nexus virtual switch. **SSL** Should be set to Enable.Always enable SSL. SSH is usually enabled by default during the VSM -installation. However, check whether the SSH connection to the VSM is -working, without which CloudStack failes to connect to the VSM. + installation. However, check whether the SSH connection to the VSM is + working, without which CloudStack failes to connect to the VSM. Creating a Port Profile ''''''''''''''''''''''' @@ -2818,7 +2805,7 @@ Creating a Port Profile For information on creating a port profile, see `Cisco Nexus 1000V Port Profile Configuration -Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_a/port_profile/configuration/guide/n1000v_port_profile.html>`__. +Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_a/port_profile/configuration/guide/n1000v_port_profile.html>`_. Assigning Physical NIC Adapters ''''''''''''''''''''''''''''''' @@ -2832,8 +2819,7 @@ during the zone configuration on CloudStack. These Ethernet port profile names are later specified as VMware Traffic Labels for different traffic types when configuring physical networks during the zone configuration. For more information on configuring physical networks, see -`Section 8.4.6, âConfiguring a vSphere Cluster with Nexus 1000v Virtual -Switchâ <#vmware-vsphere-cluster-config-nexus-vswitch>`__. +`"Configuring a vSphere Cluster with Nexus 1000v Virtual Switch" <#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_. Adding VLAN Ranges '''''''''''''''''' @@ -2905,7 +2891,7 @@ the zone is being created. After the zone is created, if you want to create an additional cluster along with Nexus 1000v virtual switch in the existing zone, use the Add Cluster option. For information on creating a cluster, see -`Section 6.5.2, âAdd Cluster: vSphereâ <#add-clusters-vsphere>`__. +`"Add Cluster: vSphere" <configuration.html#add-cluster-vsphere>`_. In both these cases, you must specify the following parameters to configure Nexus virtual switch: @@ -3033,7 +3019,7 @@ Use this VDS name in the following: Distributed Virtual Switch when you configure guest and public traffic type. - |traffic-type.png: virtual switch type| + |traffic-type.png| - @@ -3045,8 +3031,7 @@ Use this VDS name in the following: The switch name in the traffic label while updating the switch type in a zone. -Traffic label format in the last case is [["Name of -vSwitch/dvSwitch/EthernetPortProfile"][,"VLAN ID"[,"vSwitch Type"]]] +Traffic label format in the last case is [["Name of vSwitch/dvSwitch/EthernetPortProfile"][,"VLAN ID"[,"vSwitch Type"]]] The possible values for traffic labels are: @@ -3144,8 +3129,7 @@ created. Alternatively, at the cluster level, you can create an additional cluster with VDS enabled in the existing zone. Use the Add Cluster -option. For information as given in `Section 6.5.2, âAdd Cluster: -vSphereâ <#add-clusters-vsphere>`__. +option. For information as given in `âAdd Cluster: vSphereâ <configuration.html#add-cluster-vsphere>`_. In both these cases, you must specify the following parameters to configure VDS: @@ -3253,7 +3237,7 @@ Add Hosts or Configure Clusters (vSphere) Use vCenter to create a vCenter cluster and add your desired hosts to the cluster. You will later add the entire cluster to CloudStack. (see -`Section 6.5.2, âAdd Cluster: vSphereâ <#add-clusters-vsphere>`__). +`âAdd Cluster: vSphereâ <configuration.html#add-cluster-vsphere>`_). Applying Hotfixes to a VMware vSphere Host ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -3267,7 +3251,7 @@ Applying Hotfixes to a VMware vSphere Host Log in to the CloudStack UI as root. - See `Section 5.1, âLog In to the UIâ <#log-in>`__. + See `âLog In to the UIâ <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_. #. @@ -3469,8 +3453,9 @@ KVM instances. Turn on NTP for time synchronization. - .. note:: NTP is required to synchronize the clocks of the servers in your - cloud. Unsynchronized clocks can cause unexpected problems. + .. note:: + NTP is required to synchronize the clocks of the servers in your + cloud. Unsynchronized clocks can cause unexpected problems. #. @@ -3538,7 +3523,7 @@ are in ``/etc/cloudstack/agent/agent.properties`` network.direct.device=eth0 The host is now ready to be added to a cluster. This is covered in a -later section, see `Section 6.6, âAdding a Hostâ <#host-add>`__. It is +later section, see :ref:`adding-a-host`. It is recommended that you continue to read the documentation before adding the host! @@ -3729,7 +3714,8 @@ Configure the network bridges .. warning:: This is a very important section, please make sure you read this thoroughly. -.. note:: This section details how to configure bridges using the native implementation in Linux. Please refer to the next section if you intend to use OpenVswitch +.. note:: + This section details how to configure bridges using the native implementation in Linux. Please refer to the next section if you intend to use OpenVswitch In order to forward traffic to your instances you will need at least two bridges: *public* and *private*. @@ -4029,17 +4015,21 @@ To open the required ports, execute the following commands: $ ufw allow proto tcp from any to any port 49152:49216 -.. note:: By default UFW is not enabled on Ubuntu. Executing these commands with -the firewall disabled does not enable the firewall. +.. note:: + By default UFW is not enabled on Ubuntu. Executing these commands with the firewall disabled does not enable the firewall. Add the host to CloudStack ~~~~~~~~~~~~~~~~~~~~~~~~~~ The host is now ready to be added to a cluster. This is covered in a -later section, see `Section 6.6, âAdding a Hostâ <#host-add>`__. It is +later section, see :ref:`adding-a-host`. It is recommended that you continue to read the documentation before adding the host! +.. |DeleteButton.png: button to delete dvSwitch| image:: ./_static/images/delete-button.png +.. |vds-name.png: Name of the dvSwitch as specified in the vCenter.| image:: ./_static/images/vds-name.png +.. |traffic-type.png| image:: ./_static/images/traffic-type.png +.. |dvSwitchConfig.png: Configuring dvSwitch| image:: ./_static/images/dvswitchconfig.png .. |vsphereclient.png: vSphere client| image:: ./_static/images/vsphere-client.png .. |vspherephysicalnetwork.png: vSphere client| image:: ./_static/images/vmware-physical-network.png .. |vsphereincreaseports.png: vSphere client| image:: ./_static/images/vmware-increase-ports.png http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/b1f7a0f0/source/index.rst ---------------------------------------------------------------------- diff --git a/source/index.rst b/source/index.rst index 292d4d0..9abd163 100644 --- a/source/index.rst +++ b/source/index.rst @@ -18,6 +18,17 @@ You can adapt this file completely to your liking, but it should at least contain the root `toctree` directive. +.. figure:: /_static/images/acslogo.png + :align: center + +Quicklinks to CloudStack documentations: + + * `Documentation home <http://docs.cloudstack.apache.org>`_ + * `Administration Guide <http://docs.cloudstack.apache.org/projects/cloudstack-administration>`_ + * `Release Notes <http://docs.cloudstack.apache.org/projects/cloudstack-release-notes>`_ + + + Welcome to CloudStack Installation Documentation ================================================ http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/b1f7a0f0/source/installation.rst ---------------------------------------------------------------------- diff --git a/source/installation.rst b/source/installation.rst index 2678c9e..600a836 100644 --- a/source/installation.rst +++ b/source/installation.rst @@ -56,53 +56,46 @@ recommended that you read the following: #. - Make sure you have the required hardware ready. See `Section 4.3, - âMinimum System Requirementsâ <#minimum-system-requirements>`__ + Make sure you have the required hardware ready. See :ref:`minimum-system-requirements` #. Install the Management Server (choose single-node or multi-node). See - `Section 4.5, âManagement Server - Installationâ <#management-server-install-flow>`__ + :ref:`adding-a-zone` #. - Log in to the UI. See `Chapter 5, *User Interface* <#ui>`__ + Log in to the UI. See `*User Interface* <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_ #. - Add a zone. Includes the first pod, cluster, and host. See - `Section 6.3, âAdding a Zoneâ <#zone-add>`__ + Add a zone. Includes the first pod, cluster, and host. See :ref:`adding-a-host` #. - Add more pods (optional). See `Section 6.4, âAdding a - Podâ <#pod-add>`__ + Add more pods (optional). See :ref:`adding-a-pod` #. - Add more clusters (optional). See `Section 6.5, âAdding a - Clusterâ <#cluster-add>`__ + Add more clusters (optional). See :ref:`adding-a-cluster` #. - Add more hosts (optional). See `Section 6.6, âAdding a - Hostâ <#host-add>`__ + Add more hosts (optional). See :ref:`adding-a-host` #. - Add more primary storage (optional). See `Section 6.7, âAdd Primary - Storageâ <#primary-storage-add>`__ + Add more primary storage (optional). See :ref:`add-primary-storage` #. - Add more secondary storage (optional). See `Section 6.8, âAdd - Secondary Storageâ <#secondary-storage-add>`__ + Add more secondary storage (optional). See :ref:`add-secondary-storage` #. - Try using the cloud. See `Section 6.9, âInitialize and - Testâ <#initialize-and-test>`__ + Try using the cloud. See :ref:`initialize-and-test` + +.. _minimum-system-requirements: Minimum System Requirements --------------------------- @@ -180,7 +173,6 @@ requirements: At least 1 NIC .. note:: - If DHCP is used for hosts, ensure that no conflict occurs between DHCP server used for these hosts and the DHCP router created by CloudStack. - @@ -202,8 +194,7 @@ requirements listed at the top of the Installation section for your chosen hypervisor: .. warning:: - - Be sure you fulfill the additional hypervisor requirements and installation steps provided in this Guide. Hypervisor hosts must be properly prepared to work with CloudStack. For example, the requirements for XenServer are listed under Citrix XenServer Installation. + Be sure you fulfill the additional hypervisor requirements and installation steps provided in this Guide. Hypervisor hosts must be properly prepared to work with CloudStack. For example, the requirements for XenServer are listed under Citrix XenServer Installation. Configure package repository ---------------------------- @@ -214,14 +205,11 @@ binaries so that users can install Apache CloudStack without needing to build from source. If you didn't follow the steps to build your own packages from source in -the sections for `Section 3.6, âBuilding RPMs from -Sourceâ <#sect-source-buildrpm>`__ or `Section 3.5, âBuilding DEB -packagesâ <#sect-source-builddebs>`__ you may find pre-built DEB and RPM -packages for your convenience linked from the -`downloads <http://cloudstack.apache.org/downloads.html>`__ page. +the sections for `âBuilding RPMs from Sourceâ <building_from_source.html#building-rpms-from-source>`_ +or `âBuilding DEB packagesâ <building_from_source.html#building-deb-packages>`_ you may find pre-built DEB and RPM +packages for your convenience linked from the `downloads <http://cloudstack.apache.org/downloads.html>`_ page. .. note:: - These repositories contain both the Management Server and KVM Hypervisor packages. DEB package repository @@ -303,7 +291,6 @@ In either case, each machine must meet the system requirements described in System Requirements. .. warning:: - For the sake of security, be sure the public Internet can not access port 8096 or port 8250 on the Management Server. The procedure for installing the Management Server is: @@ -372,8 +359,7 @@ node. Turn on NTP for time synchronization. .. note:: - - NTP is required to synchronize the clocks of the servers in your cloud. + NTP is required to synchronize the clocks of the servers in your cloud. Install NTP. @@ -398,7 +384,6 @@ Management Server on one host or many, is to install the software on a single node. .. note:: - 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 CloudStack Management server can be installed using either RPM or @@ -428,7 +413,7 @@ This procedure is required only for installations where XenServer is installed on the hypervisor hosts. Before setting up the Management Server, download vhd-util from -`vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`__. +`vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_. If the Management Server is RHEL or CentOS, copy vhd-util to `/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver` @@ -453,8 +438,7 @@ This section describes how to install MySQL on the same machine with the Management Server. This technique is intended for a simple deployment that has a single Management Server node. If you have a multi-node Management Server deployment, you will typically use a separate node for -MySQL. See `Section 4.5.4.2, âInstall the Database on a Separate -Nodeâ <#management-server-install-db-external>`__. +MySQL. See :ref:`install-database-on-separate-node`. #. @@ -482,7 +466,8 @@ Nodeâ <#management-server-install-db-external>`__. Servers you are deploying. This example assumes one Management Server. - .. note:: On Ubuntu, you can also create a file `/etc/mysql/conf.d/cloudstack.cnf` and add these directives there. Don't forget to add [mysqld] on the first line of the file. + .. note:: + On Ubuntu, you can also create a file `/etc/mysql/conf.d/cloudstack.cnf` and add these directives there. Don't forget to add [mysqld] on the first line of the file. .. sourcecode:: bash @@ -514,7 +499,6 @@ Nodeâ <#management-server-install-db-external>`__. (CentOS and RHEL only; not required on Ubuntu) .. warning:: - On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly recommended that you set a root password as a security precaution. Run the following command to secure your installation. You can answer "Y" to all questions. @@ -598,25 +582,23 @@ Nodeâ <#management-server-install-db-external>`__. (Optional) For encryption\_type, use file or web to indicate the technique used to pass in the database encryption password. - Default: file. See `Section 4.5.5, âAbout Password and Key - Encryptionâ <#about-password-encryption>`__. + Default: file. See :ref:`about-password-key-encryption`. - (Optional) For management\_server\_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that - you replace this with a more secure value. See `Section 4.5.5, - âAbout Password and Key - Encryptionâ <#about-password-encryption>`__. + you replace this with a more secure value. See + :ref:`about-password-key-encryption`. - (Optional) For database\_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you - replace this with a more secure value. See `Section 4.5.5, âAbout - Password and Key Encryptionâ <#about-password-encryption>`__. + replace this with a more secure value. See + :ref:`about-password-key-encryption`. - @@ -637,7 +619,6 @@ Nodeâ <#management-server-install-db-external>`__. âSuccessfully initialized the database.â .. note:: - If the script is unable to connect to the MySQL database, check the "localhost" loopback address in ``/etc/hosts``. It should be pointing to the IPv4 loopback address "127.0.0.1" and not the IPv6 loopback address ::1. Alternatively, reconfigure MySQL to bind to the IPv6 loopback interface. #. @@ -662,6 +643,8 @@ Nodeâ <#management-server-install-db-external>`__. You should see the message âCloudStack Management Server setup is done.â +.. _install-database-on-separate-node: + Install the Database on a Separate Node ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -669,10 +652,11 @@ This section describes how to install MySQL on a standalone machine, separate from the Management Server. This technique is intended for a deployment that includes several Management Server nodes. If you have a single-node Management Server deployment, you will typically use the -same node for MySQL. See `Section 4.5.4.1, âInstall the Database on the -Management Server Nodeâ <#management-server-install-db-local>`__. +same node for MySQL. See ` +âInstall the Database on the Management Server Nodeâ <#install-the-database-on-the-management-server-node>`_. -.. note:: The management server doesn't require a specific distribution for the MySQL node. You can use a distribution or Operating System of your choice. Using the same distribution as the management server is recommended, but not required. See `Section 4.3.1, âManagement Server, Database, and Storage System Requirementsâ <#management-server-system-requirements>`__. +.. note:: + The management server doesn't require a specific distribution for the MySQL node. You can use a distribution or Operating System of your choice. Using the same distribution as the management server is recommended, but not required. See `âManagement Server, Database, and Storage System Requirementsâ <#management-server-database-and-storage-system-requirements>`_. #. @@ -696,7 +680,6 @@ Management Server Nodeâ <#management-server-install-db-local>`__. two Management Servers. .. note:: - On Ubuntu, you can also create /etc/mysql/conf.d/cloudstack.cnf file and add these directives there. Don't forget to add [mysqld] on the first line of the file. .. sourcecode:: bash @@ -730,7 +713,6 @@ Management Server Nodeâ <#management-server-install-db-local>`__. (CentOS and RHEL only; not required on Ubuntu) .. warning:: - On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly recommended that you set a root password as a security precaution. Run the following command to secure your installation. You can answer "Y" to all questions except "Disallow root login remotely?". Remote root login is required to set up the databases. .. sourcecode:: bash @@ -793,8 +775,7 @@ Management Server Nodeâ <#management-server-install-db-local>`__. (Optional) For encryption\_type, use file or web to indicate the technique used to pass in the database encryption password. - Default: file. See `Section 4.5.5, âAbout Password and Key - Encryptionâ <#about-password-encryption>`__. + Default: file. See :ref:`about-password-key-encryption`. - @@ -809,8 +790,8 @@ Management Server Nodeâ <#management-server-install-db-local>`__. (Optional) For database\_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you - replace this with a more secure value. See `Section 4.5.5, âAbout - Password and Key Encryptionâ <#about-password-encryption>`__. + replace this with a more secure value. See + :ref:`about-password-key-encryption`. - @@ -829,6 +810,8 @@ Management Server Nodeâ <#management-server-install-db-local>`__. When this script is finished, you should see a message like âSuccessfully initialized the database.â +.. _about-password-key-encryption: + About Password and Key Encryption ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -972,20 +955,19 @@ The requirements for primary and secondary storage are described in: - - `Section 2.6, âAbout Primary Storageâ <#about-primary-storage>`__ + `âAbout Primary Storageâ <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-primary-storage>`_ - - `Section 2.7, âAbout Secondary Storageâ <#about-secondary-storage>`__ + `âAbout Secondary Storageâ <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-secondary-storage>`_ -A production installation typically uses a separate NFS server. See -`Section 4.5.7.1, âUsing a Separate NFS -Serverâ <#nfs-shares-on-separate-server>`__. +A production installation typically uses a separate NFS server. See :ref:`using-a-separage-nfs-server`. You can also use the Management Server node as the NFS server. This is more typical of a trial installation, but is technically possible in a -larger deployment. See `Section 4.5.7.2, âUsing the Management Server as -the NFS Serverâ <#nfs-shares-on-management-server>`__. +larger deployment. See :ref:`using-the-management-server-as-the-nfs-server`. + +.. _using-a-separage-nfs-server: Using a Separate NFS Server ^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -998,7 +980,6 @@ The exact commands for the following steps may vary depending on your operating system version. .. warning:: - (KVM only) Ensure that no volume is already mounted at your NFS mount point. #. @@ -1054,6 +1035,8 @@ operating system version. # mount -t nfs nfsservername:/nfs/share/secondary /mnt/secondary +.. _using-the-management-server-as-the-nfs-server: + Using the Management Server as the NFS Server ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -1232,10 +1215,9 @@ OS for the Management Server. #. - Perform the steps in `Section 4.5.2, âPrepare the Operating - Systemâ <#prepare-os>`__ and `Section 3.6, âBuilding RPMs from - Sourceâ <#sect-source-buildrpm>`__ or `Section 3.5, âBuilding DEB - packagesâ <#sect-source-builddebs>`__ as appropriate. + Perform the steps in `âPrepare the Operating Systemâ <#prepare-the-operating-system>`_ and + `âBuilding RPMs from Sourceâ <building_from_source.html#building-rpms-from-source>`_ or + `âBuilding DEB packagesâ <building_from_source.html#building-deb-packages>`_ as appropriate. #. @@ -1243,7 +1225,7 @@ OS for the Management Server. installed on the hypervisor hosts. Download vhd-util from - `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`__ + `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_ Copy vhd-util to /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver. @@ -1263,8 +1245,7 @@ OS for the Management Server. 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 `Section 4.5.4.2, âInstall the Database on a Separate - Nodeâ <#management-server-install-db-external>`__.) + command, see :ref:`install-database-on-separate-node`.) .. sourcecode:: bash @@ -1287,8 +1268,7 @@ OS for the Management Server. #. Be sure to configure a load balancer for the Management Servers. See - `Section 13.6, âManagement Server Load - Balancingâ <#management-server-lb>`__. + `âManagement Server Load Balancingâ <http://docs.cloudstack.apache.org/en/latest/administration_guide.html?highlight=management%20server%20load#management-server-load-balancing>`_. Prepare the System VM Template ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -1297,7 +1277,6 @@ Secondary storage must be seeded with a template that is used for CloudStack system VMs. .. note:: - 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. #. @@ -1312,8 +1291,7 @@ CloudStack system VMs. If you set the CloudStack database encryption type to "web" when you set up the database, you must now add the parameter -s - <management-server-secret-key>. See `Section 4.5.5, âAbout Password - and Key Encryptionâ <#about-password-encryption>`__. + <management-server-secret-key>. See :ref:`about-password-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. http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/b1f7a0f0/source/network_setup.rst ---------------------------------------------------------------------- diff --git a/source/network_setup.rst b/source/network_setup.rst index 2c46513..e85ba46 100644 --- a/source/network_setup.rst +++ b/source/network_setup.rst @@ -275,9 +275,7 @@ Hardware Firewall All deployments should have a firewall protecting the management server; see Generic Firewall Provisions. Optionally, some deployments may also have a Juniper SRX firewall that will be the default gateway for the -guest networks; see `Section 13.5.2, âExternal Guest Firewall -Integration for Juniper SRX -(Optional)â <#external-guest-firewall-integration>`__. +guest networks; see `âExternal Guest Firewall Integration for Juniper SRX (Optional)â <#external-guest-firewall-integration-for-juniper-srx-optional>`_. Generic Firewall Provisions ~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -628,40 +626,35 @@ Prerequisites profile, which needs to be provided while adding the ASA appliance to CloudStack. - For information on configuration, see `Section 8.4.6, âConfiguring a - vSphere Cluster with Nexus 1000v Virtual - Switchâ <#vmware-vsphere-cluster-config-nexus-vswitch>`__. + For information on configuration, see + `âConfiguring a vSphere Cluster with Nexus 1000v Virtual Switchâ <hypervisor_installation.html#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_. #. Deploy and configure Cisco VNMC. - For more information, see `Installing Cisco Virtual Network Management Center <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_2_1_1/install_upgrade/guide/b_Cisco_VSG_for_VMware_vSphere_Rel_4_2_1_VSG_2_1_1_and_Cisco_VNMC_Rel_2_1_Installation_and_Upgrade_Guide_chapter_011.html>`__ - and `Configuring Cisco Virtual Network Management - Center <http://www.cisco.com/en/US/docs/unified_computing/vnmc/sw/1.2/VNMC_GUI_Configuration/b_VNMC_GUI_Configuration_Guide_1_2_chapter_010.html>`__. + For more information, see `Installing Cisco Virtual Network Management Center <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_2_1_1/install_upgrade/guide/b_Cisco_VSG_for_VMware_vSphere_Rel_4_2_1_VSG_2_1_1_and_Cisco_VNMC_Rel_2_1_Installation_and_Upgrade_Guide_chapter_011.html>`_ + and `Configuring Cisco Virtual Network Management Center <http://www.cisco.com/en/US/docs/unified_computing/vnmc/sw/1.2/VNMC_GUI_Configuration/b_VNMC_GUI_Configuration_Guide_1_2_chapter_010.html>`_. #. Register Cisco Nexus 1000v dvSwitch with Cisco VNMC. For more information, see `Registering a Cisco Nexus 1000V with Cisco - VNMC <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_1_2/vnmc_and_vsg_qi/guide/vnmc_vsg_install_5register.html#wp1064301>`__. + VNMC <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_1_2/vnmc_and_vsg_qi/guide/vnmc_vsg_install_5register.html#wp1064301>`_. #. Create Inside and Outside port profiles in Cisco Nexus 1000v dvSwitch. - For more information, see `Section 8.4.6, âConfiguring a vSphere - Cluster with Nexus 1000v Virtual - Switchâ <#vmware-vsphere-cluster-config-nexus-vswitch>`__. + For more information, see `âConfiguring a vSphere Cluster with Nexus 1000v Virtual Switchâ <hypervisor_installation.html#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_. #. Deploy and Cisco ASA 1000v appliance. - For more information, see `Setting Up the ASA 1000V Using - VNMC <http://www.cisco.com/en/US/docs/security/asa/quick_start/asa1000V/setup_vnmc.html>`__. + For more information, see `Setting Up the ASA 1000V Using VNMC <http://www.cisco.com/en/US/docs/security/asa/quick_start/asa1000V/setup_vnmc.html>`_. Typically, you create a pool of ASA 1000v appliances and register them with CloudStack. @@ -712,27 +705,26 @@ Using Cisco ASA 1000v Services Ensure that all the prerequisites are met. - See `Section 13.5.3.1.2, âPrerequisitesâ <#prereq-asa>`__. + See `âPrerequisitesâ <#prerequisites>`_. #. Add a VNMC instance. - See `Section 13.5.3.2, âAdding a VNMC Instanceâ <#add-vnmc>`__. + See `âAdding a VNMC Instanceâ <#adding-a-vnmc-instance>`_. #. Add a ASA 1000v instance. - See `Section 13.5.3.3, âAdding an ASA 1000v Instanceâ <#add-asa>`__. + See `âAdding an ASA 1000v Instanceâ <#adding-an-asa-1000v-instance>`_. #. Create a Network Offering and use Cisco VNMC as the service provider for desired services. - See `Section 13.5.3.4, âCreating a Network Offering Using Cisco ASA - 1000vâ <#asa-offering>`__. + See `âCreating a Network Offering Using Cisco ASA 1000vâ <#creating-a-network-offering-using-cisco-asa-1000v>`_. #. @@ -918,8 +910,7 @@ offering as follows: Private Cloud-enabled. A Virtual Private Cloud (VPC) is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. - For more information on VPCs, see `Section 15.27.1, âAbout Virtual - Private Cloudsâ <#vpc>`__. + For more information on VPCs, see `âAbout Virtual Private Cloudsâ <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/networking2.html#about-virtual-private-clouds>`_. - @@ -1271,8 +1262,8 @@ To set up the integration between CloudStack and Traffic Sentinel: On your network infrastructure, install Traffic Sentinel and configure it to gather traffic data. For installation and - configuration steps, see inMon documentation at `Traffic Sentinel - Documentation <http://inmon.com.>`__. + configuration steps, see inMon documentation at + `Traffic Sentinel Documentation <http://inmon.com.>`_. #. @@ -1290,12 +1281,10 @@ To set up the integration between CloudStack and Traffic Sentinel: CloudStack API command addTrafficMonitor. Pass in the URL of the Traffic Sentinel as protocol + host + port (optional); for example, http://10.147.28.100:8080. For the addTrafficMonitor command syntax, - see the API Reference at `API - Documentation <http://cloudstack.apache.org/docs/api/index.html>`__. + see the API Reference at `API Documentation <http://cloudstack.apache.org/docs/api/index.html>`_. For information about how to call the CloudStack API, see the - Developerâs Guide at `CloudStack API Developer's - Guide <http://cloudstack.apache.org/docs/en-US/index.html>`__. + Developerâs Guide at `CloudStack API Developer's Guide <http://docs.cloudstack.apache.org/en/latest/index.html#developers>`_. #.
