You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by mu...@apache.org on 2012/12/06 09:09:12 UTC
[73/100] [abbrv] [partial] Revised en-US/network-setup.xml to include
the correct file.
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/citrix-xenserver-installation.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/citrix-xenserver-installation.html b/docs/tmp/en-US/html/citrix-xenserver-installation.html
deleted file mode 100644
index d584b65..0000000
--- a/docs/tmp/en-US/html/citrix-xenserver-installation.html
+++ /dev/null
@@ -1,414 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2. Citrix XenServer Installation for CloudStack</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="hypervisor-installation.html" title="Chapter 8. Hypervisor Installation" /><link rel="prev" href="hypervisor-kvm-install-flow.html" title="8.1. KVM Hypervisor Host Installation" /><link rel="next" href="vmware-install.html" title="8.3. VMware vSphere Installation and Configuration" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.
png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="hypervisor-kvm-install-flow.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="vmware-install.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="citrix-xenserver-installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="citrix-xenserver-installation">8.2. Citrix XenServer Installation for CloudStack</h2></div></div></div><div class="para">
- 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 <a class="xref" href="citrix-xenserver-installation.html#xenserver-version-upgrading">Section 8.2.11, “Upgrading XenServer Versions”</a>.
- </div><div class="section" id="system-requirements-xenserver-hosts"><div class="titlepage"><div><div><h3 class="title" id="system-requirements-xenserver-hosts">8.2.1. System Requirements for XenServer Hosts</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- The host must be certified as compatible with one of the following. See the Citrix Hardware Compatibility Guide: <a href="http://hcl.xensource.com">http://hcl.xensource.com</a>
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- XenServer 5.6 SP2
- </div></li><li class="listitem"><div class="para">
- XenServer 6.0
- </div></li><li class="listitem"><div class="para">
- XenServer 6.0.2
- </div></li></ul></div></li><li class="listitem"><div class="para">
- You must re-install Citrix XenServer if you are going to re-use a host from a previous install.
- </div></li><li class="listitem"><div class="para">
- Must support HVM (Intel-VT or AMD-V enabled)
- </div></li><li class="listitem"><div class="para">
- Be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. CloudStack will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches.
- </div></li><li class="listitem"><div class="para">
- All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags.
- </div></li><li class="listitem"><div class="para">
- Must support HVM (Intel-VT or AMD-V enabled in BIOS)
- </div></li><li class="listitem"><div class="para">
- 64-bit x86 CPU (more cores results in better performance)
- </div></li><li class="listitem"><div class="para">
- Hardware virtualization support required
- </div></li><li class="listitem"><div class="para">
- 4 GB of memory
- </div></li><li class="listitem"><div class="para">
- 36 GB of local disk
- </div></li><li class="listitem"><div class="para">
- At least 1 NIC
- </div></li><li class="listitem"><div class="para">
- Statically allocated IP Address
- </div></li><li class="listitem"><div class="para">
- When you deploy CloudStack, the hypervisor host must not have any VMs already running
- </div></li></ul></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
- The lack of up-do-date hotfixes can lead to data corruption and lost VMs.
- </div></div></div></div><div class="section" id="xenserver-installation-steps"><div class="titlepage"><div><div><h3 class="title" id="xenserver-installation-steps">8.2.2. XenServer Installation Steps</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- From <a href="https://www.citrix.com/English/ss/downloads/">https://www.citrix.com/English/ss/downloads/</a>, download the appropriate version of XenServer for your CloudStack version (see <a class="xref" href="citrix-xenserver-installation.html#system-requirements-xenserver-hosts">Section 8.2.1, “System Requirements for XenServer Hosts”</a>). Install it using the Citrix XenServer Installation Guide.
- </div></li><li class="listitem"><div class="para">
- After installation, perform the following configuration steps, which are described in the next few sections:
- </div><div class="informaltable"><table border="1"><colgroup><col align="left" class="c1" width="50%" /><col align="left" class="c2" width="50%" /></colgroup><thead><tr><th align="left">
- <div class="para">
- Required
- </div>
- </th><th align="left">
- <div class="para">
- Optional
- </div>
- </th></tr></thead><tbody><tr><td align="left">
- <div class="para">
- <a class="xref" href="citrix-xenserver-installation.html#config-xenserver-dom0-memory">Section 8.2.3, “Configure XenServer dom0 Memory”</a>
- </div>
- </td><td align="left">
- <div class="para">
- <a class="xref" href="citrix-xenserver-installation.html#xenserver-support-pkg-installation">Section 8.2.7, “Install CloudStack XenServer Support Package (CSP)”</a>
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- <a class="xref" href="citrix-xenserver-installation.html#xenserver-username-password">Section 8.2.4, “Username and Password”</a>
- </div>
- </td><td align="left">
- <div class="para">
- Set up SR if not using NFS, iSCSI, or local disk; see <a class="xref" href="citrix-xenserver-installation.html#xenserver-primary-storage-setup">Section 8.2.8, “Primary Storage Setup for XenServer”</a>
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- <a class="xref" href="citrix-xenserver-installation.html#xenserver-time-sync">Section 8.2.5, “Time Synchronization”</a>
- </div>
- </td><td align="left">
- <div class="para">
- <a class="xref" href="citrix-xenserver-installation.html#xenserver-iscsi-multipath-setup">Section 8.2.9, “iSCSI Multipath Setup for XenServer (Optional)”</a>
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- <a class="xref" href="citrix-xenserver-installation.html#xenserver-get-deploy-license">Section 8.2.6.1, “Getting and Deploying a License”</a>
- </div>
- </td><td align="left">
- <div class="para">
- <a class="xref" href="citrix-xenserver-installation.html#xenserver-physical-network-setup">Section 8.2.10, “Physical Networking Setup for XenServer”</a>
- </div>
- </td></tr></tbody></table></div></li></ol></div></div><div class="section" id="config-xenserver-dom0-memory"><div class="titlepage"><div><div><h3 class="title" id="config-xenserver-dom0-memory">8.2.3. Configure XenServer dom0 Memory</h3></div></div></div><div class="para">
- 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 <a href="http://support.citrix.com/article/CTX126531">http://support.citrix.com/article/CTX126531</a>. The article refers to XenServer 5.6, but the same information applies to XenServer 6.0.
- </div></div><div class="section" id="xenserver-username-password"><div class="titlepage"><div><div><h3 class="title" id="xenserver-username-password">8.2.4. Username and Password</h3></div></div></div><div class="para">
- All XenServers in a cluster must have the same username and password as configured in CloudStack.
- </div></div><div class="section" id="xenserver-time-sync"><div class="titlepage"><div><div><h3 class="title" id="xenserver-time-sync">8.2.5. Time Synchronization</h3></div></div></div><div class="para">
- The host must be set to use NTP. All hosts in a pod must have the same time.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Install NTP.
- </div><pre class="programlisting"># yum install ntp</pre></li><li class="listitem"><div class="para">
- Edit the NTP configuration file to point to your NTP server.
- </div><pre class="programlisting"># vi /etc/ntp.conf</pre><div class="para">
- Add one or more server lines in this file with the names of the NTP servers you want to use. For example:
- </div><pre class="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
-</pre></li><li class="listitem"><div class="para">
- Restart the NTP client.
- </div><pre class="programlisting"># service ntpd restart</pre></li><li class="listitem"><div class="para">
- Make sure NTP will start again upon reboot.
- </div><pre class="programlisting"># chkconfig ntpd on</pre></li></ol></div></div><div class="section" id="xenserver-licensing"><div class="titlepage"><div><div><h3 class="title" id="xenserver-licensing">8.2.6. Licensing</h3></div></div></div><div class="para">
- Citrix XenServer Free version provides 30 days usage without a license. Following the 30 day trial, XenServer requires a free activation and license. You can choose to install a license now or skip this step. If you skip this step, you will need to install a license when you activate and license the XenServer.
- </div><div class="section" id="xenserver-get-deploy-license"><div class="titlepage"><div><div><h4 class="title" id="xenserver-get-deploy-license">8.2.6.1. Getting and Deploying a License</h4></div></div></div><div class="para">
- If you choose to install a license now you will need to use the XenCenter to activate and get a license.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- In XenCenter, click Tools > License manager.
- </div></li><li class="listitem"><div class="para">
- Select your XenServer and select Activate Free XenServer.
- </div></li><li class="listitem"><div class="para">
- Request a license.
- </div></li></ol></div><div class="para">
- You can install the license with XenCenter or using the xe command line tool.
- </div></div></div><div class="section" id="xenserver-support-pkg-installation"><div class="titlepage"><div><div><h3 class="title" id="xenserver-support-pkg-installation">8.2.7. Install CloudStack XenServer Support Package (CSP)</h3></div></div></div><div class="para">
- (Optional)
- </div><div class="para">
- To enable security groups, elastic load balancing, and elastic IP on XenServer, download and install the CloudStack XenServer Support Package (CSP). After installing XenServer, perform the following additional steps on each XenServer host.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Download the CSP software onto the XenServer host from one of the following links:
- </div><div class="para">
- For XenServer 6.0.2:
- </div><div class="para">
- <a href="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</a>
- </div><div class="para">
- For XenServer 5.6 SP2:
- </div><div class="para">
- <a href="http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz">http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz</a>
- </div><div class="para">
- For XenServer 6.0:
- </div><div class="para">
- <a href="http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz">http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz</a>
- </div></li><li class="listitem"><div class="para">
- Extract the file:
- </div><pre class="programlisting"># tar xf xenserver-cloud-supp.tgz</pre></li><li class="listitem"><div class="para">
- Run the following script:
- </div><pre class="programlisting"># xe-install-supplemental-pack xenserver-cloud-supp.iso</pre></li><li class="listitem"><div class="para">
- If the XenServer host is part of a zone that uses basic networking, disable Open vSwitch (OVS):
- </div><pre class="programlisting"># xe-switch-network-backend bridge</pre><div class="para">
- Restart the host machine when prompted.
- </div></li></ol></div><div class="para">
- The XenServer host is now ready to be added to CloudStack.
- </div></div><div class="section" id="xenserver-primary-storage-setup"><div class="titlepage"><div><div><h3 class="title" id="xenserver-primary-storage-setup">8.2.8. Primary Storage Setup for XenServer</h3></div></div></div><div class="para">
- CloudStack natively supports NFS, iSCSI and local storage. If you are using one of these storage types, there is no need to create the XenServer Storage Repository ("SR").
- </div><div class="para">
- If, however, you would like to use storage connected via some other technology, such as FiberChannel, you must set up the SR yourself. To do so, perform the following steps. If you have your hosts in a XenServer pool, perform the steps on the master node. If you are working with a single XenServer which is not part of a cluster, perform the steps on that XenServer.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Connect FiberChannel cable to all hosts in the cluster and to the FiberChannel storage host.
- </div></li><li class="listitem"><div class="para">
- Rescan the SCSI bus. Either use the following command or use XenCenter to perform an HBA rescan.
- </div><pre class="programlisting"># scsi-rescan</pre></li><li class="listitem"><div class="para">
- Repeat step 2 on every host.
- </div></li><li class="listitem"><div class="para">
- Check to be sure you see the new SCSI disk.
- </div><pre class="programlisting"># ls /dev/disk/by-id/scsi-360a98000503365344e6f6177615a516b -l</pre><div class="para">
- The output should look like this, although the specific file name will be different (scsi-<scsiID>):
- </div><pre class="programlisting">lrwxrwxrwx 1 root root 9 Mar 16 13:47
-/dev/disk/by-id/scsi-360a98000503365344e6f6177615a516b -> ../../sdc
-</pre></li><li class="listitem"><div class="para">
- Repeat step 4 on every host.
- </div></li><li class="listitem"><div class="para">
- On the storage server, run this command to get a unique ID for the new SR.
- </div><pre class="programlisting"># uuidgen</pre><div class="para">
- The output should look like this, although the specific ID will be different:
- </div><pre class="programlisting">e6849e96-86c3-4f2c-8fcc-350cc711be3d</pre></li><li class="listitem"><div class="para">
- Create the FiberChannel SR. In name-label, use the unique ID you just generated.
- </div><pre class="programlisting">
-# xe sr-create type=lvmohba shared=true
-device-config:SCSIid=360a98000503365344e6f6177615a516b
-name-label="e6849e96-86c3-4f2c-8fcc-350cc711be3d"
-</pre><div class="para">
- This command returns a unique ID for the SR, like the following example (your ID will be different):
- </div><pre class="programlisting">7a143820-e893-6c6a-236e-472da6ee66bf</pre></li><li class="listitem"><div class="para">
- To create a human-readable description for the SR, use the following command. In uuid, use the SR ID returned by the previous command. In name-description, set whatever friendly text you prefer.
- </div><pre class="programlisting"># xe sr-param-set uuid=7a143820-e893-6c6a-236e-472da6ee66bf name-description="Fiber Channel storage repository"</pre><div class="para">
- Make note of the values you will need when you add this storage to CloudStack later (see <a class="xref" href="primary-storage-add.html">Section 6.6, “Add Primary Storage”</a>). 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).
- </div></li><li class="listitem"><div class="para">
- (Optional) If you want to enable multipath I/O on a FiberChannel SAN, refer to the documentation provided by the SAN vendor.
- </div></li></ol></div></div><div class="section" id="xenserver-iscsi-multipath-setup"><div class="titlepage"><div><div><h3 class="title" id="xenserver-iscsi-multipath-setup">8.2.9. iSCSI Multipath Setup for XenServer (Optional)</h3></div></div></div><div class="para">
- When setting up the storage repository on a Citrix XenServer, you can enable multipath I/O, which uses redundant physical components to provide greater reliability in the connection between the server and the SAN. To enable multipathing, use a SAN solution that is supported for Citrix servers and follow the procedures in Citrix documentation. The following links provide a starting point:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <a href="http://support.citrix.com/article/CTX118791">http://support.citrix.com/article/CTX118791</a>
- </div></li><li class="listitem"><div class="para">
- <a href="http://support.citrix.com/article/CTX125403">http://support.citrix.com/article/CTX125403</a>
- </div></li></ul></div><div class="para">
- You can also ask your SAN vendor for advice about setting up your Citrix repository for multipathing.
- </div><div class="para">
- Make note of the values you will need when you add this storage to the CloudStack later (see <a class="xref" href="primary-storage-add.html">Section 6.6, “Add Primary Storage”</a>). 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.
- </div><div class="para">
- If you encounter difficulty, address the support team for the SAN provided by your vendor. If they are not able to solve your issue, see Contacting Support.
- </div></div><div class="section" id="xenserver-physical-network-setup"><div class="titlepage"><div><div><h3 class="title" id="xenserver-physical-network-setup">8.2.10. Physical Networking Setup for XenServer</h3></div></div></div><div class="para">
- Once XenServer has been installed, you may need to do some additional network configuration. At this point in the installation, you should have a plan for what NICs the host will have and what traffic each NIC will carry. The NICs should be cabled as necessary to implement your plan.
- </div><div class="para">
- If you plan on using NIC bonding, the NICs on all hosts in the cluster must be cabled exactly the same. For example, if eth0 is in the private bond on one host in a cluster, then eth0 must be in the private bond on all hosts in the cluster.
- </div><div class="para">
- The IP address assigned for the management network interface must be static. It can be set on the host itself or obtained via static DHCP.
- </div><div class="para">
- CloudStack configures network traffic of various types to use different NICs or bonds on the XenServer host. You can control this process and provide input to the Management Server through the use of XenServer network name labels. The name labels are placed on physical interfaces or bonds and configured in CloudStack. In some simple cases the name labels are not required.
- </div><div class="section" id="xenserver-public-network-config"><div class="titlepage"><div><div><h4 class="title" id="xenserver-public-network-config">8.2.10.1. Configuring Public Network with a Dedicated NIC for XenServer (Optional)</h4></div></div></div><div class="para">
- CloudStack supports the use of a second NIC (or bonded pair of NICs, described in <a class="xref" href="citrix-xenserver-installation.html#xenserver-nic-bonding">Section 8.2.10.4, “NIC Bonding for XenServer (Optional)”</a>) 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 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 <a class="xref" href="management-server-install-flow.html">Section 4.5, “Management Server Installation”</a>.
- </div><div class="para">
- If you are using two NICs bonded together to create a public network, see <a class="xref" href="citrix-xenserver-installation.html#xenserver-nic-bonding">Section 8.2.10.4, “NIC Bonding for XenServer (Optional)”</a>.
- </div><div class="para">
- If you are using a single dedicated NIC to provide public network access, follow this procedure on each new host that is added to CloudStack before adding the host.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Run xe network-list and find the public network. This is usually attached to the NIC that is public. Once you find the network make note of its UUID. Call this <UUID-Public>.
- </div></li><li class="listitem"><div class="para">
- Run the following command.
- </div><pre class="programlisting"># xe network-param-set name-label=cloud-public uuid=<UUID-Public></pre></li></ol></div></div><div class="section" id="xenserver-multi-guest-network-config"><div class="titlepage"><div><div><h4 class="title" id="xenserver-multi-guest-network-config">8.2.10.2. Configuring Multiple Guest Networks for XenServer (Optional)</h4></div></div></div><div class="para">
- CloudStack supports the use of multiple guest networks with the XenServer hypervisor. Each network is assigned a name-label in XenServer. For example, you might have two networks with the labels "cloud-guest" and "cloud-guest2". After the management server is installed and running, you must add the networks and use these labels so that CloudStack is aware of the networks.
- </div><div class="para">
- Follow this procedure on each new host before adding the host to CloudStack:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Run xe network-list and find one of the guest networks. Once you find the network make note of its UUID. Call this <UUID-Guest>.
- </div></li><li class="listitem"><div class="para">
- Run the following command, substituting your own name-label and uuid values.
- </div><pre class="programlisting"># xe network-param-set name-label=<cloud-guestN> uuid=<UUID-Guest></pre></li><li class="listitem"><div class="para">
- Repeat these steps for each additional guest network, using a different name-label and uuid each time.
- </div></li></ol></div></div><div class="section" id="xenserver-separate-storage-network"><div class="titlepage"><div><div><h4 class="title" id="xenserver-separate-storage-network">8.2.10.3. Separate Storage Network for XenServer (Optional)</h4></div></div></div><div class="para">
- You can optionally set up a separate storage network. This should be done first on the host, before implementing the bonding steps below. This can be done using one or two available NICs. With two NICs bonding may be done as above. It is the administrator's responsibility to set up a separate storage network.
- </div><div class="para">
- Give the storage network a different name-label than what will be given for other networks.
- </div><div class="para">
- For the separate storage network to work correctly, it must be the only interface that can ping the primary storage device's IP address. For example, if eth0 is the management network NIC, ping -I eth0 <primary storage device IP> must fail. In all deployments, secondary storage devices must be pingable from the management network NIC or bond. If a secondary storage device has been placed on the storage network, it must also be pingable via the storage network NIC or bond on the hosts as well.
- </div><div class="para">
- You can set up two separate storage networks as well. For example, if you intend to implement iSCSI multipath, dedicate two non-bonded NICs to multipath. Each of the two networks needs a unique name-label.
- </div><div class="para">
- If no bonding is done, the administrator must set up and name-label the separate storage network on all hosts (masters and slaves).
- </div><div class="para">
- Here is an example to set up eth5 to access a storage network on 172.16.0.0/24.
- </div><pre class="programlisting">
-# xe pif-list host-name-label='hostname' device=eth5
-uuid(RO): ab0d3dd4-5744-8fae-9693-a022c7a3471d
-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</pre></div><div class="section" id="xenserver-nic-bonding"><div class="titlepage"><div><div><h4 class="title" id="xenserver-nic-bonding">8.2.10.4. NIC Bonding for XenServer (Optional)</h4></div></div></div><div class="para">
- XenServer supports Source Level Balancing (SLB) NIC bonding. Two NICs can be bonded together to carry public, private, and guest traffic, or some combination of these. Separate storage networks are also possible. Here are some example supported configurations:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- 2 NICs on private, 2 NICs on public, 2 NICs on storage
- </div></li><li class="listitem"><div class="para">
- 2 NICs on private, 1 NIC on public, storage uses management network
- </div></li><li class="listitem"><div class="para">
- 2 NICs on private, 2 NICs on public, storage uses management network
- </div></li><li class="listitem"><div class="para">
- 1 NIC for private, public, and storage
- </div></li></ul></div><div class="para">
- All NIC bonding is optional.
- </div><div class="para">
- XenServer expects all nodes in a cluster will have the same network cabling and same bonds implemented. In an installation the master will be the first host that was added to the cluster and the slave hosts will be all subsequent hosts added to the cluster. The bonds present on the master set the expectation for hosts added to the cluster later. The procedure to set up bonds on the master and slaves are different, and are described below. There are several important implications of this:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- You must set bonds on the first host added to a cluster. Then you must use xe commands as below to establish the same bonds in the second and subsequent hosts added to a cluster.
- </div></li><li class="listitem"><div class="para">
- Slave hosts in a cluster must be cabled exactly the same as the master. For example, if eth0 is in the private bond on the master, it must be in the management network for added slave hosts.
- </div></li></ul></div><div class="section" id="management-network-bonding"><div class="titlepage"><div><div><h5 class="title" id="management-network-bonding">8.2.10.4.1. Management Network Bonding</h5></div></div></div><div class="para">
- The administrator must bond the management network NICs prior to adding the host to CloudStack.
- </div></div><div class="section" id="first-host-private-bond"><div class="titlepage"><div><div><h5 class="title" id="first-host-private-bond">8.2.10.4.2. Creating a Private Bond on the First Host in the Cluster</h5></div></div></div><div class="para">
- Use the following steps to create a bond in XenServer. These steps should be run on only the first host in a cluster. This example creates the cloud-private network with two physical NICs (eth0 and eth1) bonded into it.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Find the physical NICs that you want to bond together.
- </div><pre class="programlisting"># xe pif-list host-name-label='hostname' device=eth0
-# xe pif-list host-name-label='hostname' device=eth1</pre><div class="para">
- These command shows the eth0 and eth1 NICs and their UUIDs. Substitute the ethX devices of your choice. Call the UUID's returned by the above command slave1-UUID and slave2-UUID.
- </div></li><li class="listitem"><div class="para">
- Create a new network for the bond. For example, a new network with name "cloud-private".
- </div><div class="para">
- <span class="bold bold"><strong>This label is important. CloudStack looks for a network by a name you configure. You must use the same name-label for all hosts in the cloud for the management network.</strong></span>
- </div><pre class="programlisting"># xe network-create name-label=cloud-private
-# xe bond-create network-uuid=[uuid of cloud-private created above]
-pif-uuids=[slave1-uuid],[slave2-uuid]</pre></li></ol></div><div class="para">
- Now you have a bonded pair that can be recognized by CloudStack as the management network.
- </div></div><div class="section" id="public-network-bonding"><div class="titlepage"><div><div><h5 class="title" id="public-network-bonding">8.2.10.4.3. Public Network Bonding</h5></div></div></div><div class="para">
- Bonding can be implemented on a separate, public network. The administrator is responsible for creating a bond for the public network if that network will be bonded and will be separate from the management network.
- </div></div><div class="section" id="first-host-public-network-bond"><div class="titlepage"><div><div><h5 class="title" id="first-host-public-network-bond">8.2.10.4.4. Creating a Public Bond on the First Host in the Cluster</h5></div></div></div><div class="para">
- These steps should be run on only the first host in a cluster. This example creates the cloud-public network with two physical NICs (eth2 and eth3) bonded into it.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Find the physical NICs that you want to bond together.
- </div><pre class="programlisting">#xe pif-list host-name-label='hostname' device=eth2
-# xe pif-list host-name-label='hostname' device=eth3</pre><div class="para">
- These command shows the eth2 and eth3 NICs and their UUIDs. Substitute the ethX devices of your choice. Call the UUID's returned by the above command slave1-UUID and slave2-UUID.
- </div></li><li class="listitem"><div class="para">
- Create a new network for the bond. For example, a new network with name "cloud-public".
- </div><div class="para">
- <span class="bold bold"><strong>This label is important. CloudStack looks for a network by a name you configure. You must use the same name-label for all hosts in the cloud for the public network.</strong></span>
- </div><pre class="programlisting"># xe network-create name-label=cloud-public
-# xe bond-create network-uuid=[uuid of cloud-public created above]
-pif-uuids=[slave1-uuid],[slave2-uuid]</pre></li></ol></div><div class="para">
- Now you have a bonded pair that can be recognized by CloudStack as the public network.
- </div></div><div class="section" id="adding-more-hosts"><div class="titlepage"><div><div><h5 class="title" id="adding-more-hosts">8.2.10.4.5. Adding More Hosts to the Cluster</h5></div></div></div><div class="para">
- With the bonds (if any) established on the master, you should add additional, slave hosts. Run the following command for all additional hosts to be added to the cluster. This will cause the host to join the master in a single XenServer pool.
- </div><pre class="programlisting"># xe pool-join master-address=[master IP] master-username=root
-master-password=[your password]</pre></div><div class="section" id="complete-bonding-setup"><div class="titlepage"><div><div><h5 class="title" id="complete-bonding-setup">8.2.10.4.6. Complete the Bonding Setup Across the Cluster</h5></div></div></div><div class="para">
- With all hosts added to the pool, run the cloud-setup-bond script. This script will complete the configuration and set up of the bonds across all hosts in the cluster.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Copy the script from the Management Server in /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master host and ensure it is executable.
- </div></li><li class="listitem"><div class="para">
- Run the script:
- </div><pre class="programlisting"># ./cloud-setup-bonding.sh</pre></li></ol></div><div class="para">
- Now the bonds are set up and configured properly across the cluster.
- </div></div></div></div><div class="section" id="xenserver-version-upgrading"><div class="titlepage"><div><div><h3 class="title" id="xenserver-version-upgrading">8.2.11. Upgrading XenServer Versions</h3></div></div></div><div class="para">
- This section tells how to upgrade XenServer software on CloudStack hosts. The actual upgrade is described in XenServer documentation, but there are some additional steps you must perform before and after the upgrade.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- Be sure the hardware is certified compatible with the new version of XenServer.
- </div></div></div><div class="para">
- To upgrade XenServer:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Upgrade the database. On the Management Server node:
- </div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
- Back up the database:
- </div><pre class="programlisting"># mysqldump --user=root --databases cloud > cloud.backup.sql
-# mysqldump --user=root --databases cloud_usage > cloud_usage.backup.sql</pre></li><li class="listitem"><div class="para">
- You might need to change the OS type settings for VMs running on the upgraded hosts.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- If you upgraded from XenServer 5.6 GA to XenServer 5.6 SP2, change any VMs that have the OS type CentOS 5.5 (32-bit), Oracle Enterprise Linux 5.5 (32-bit), or Red Hat Enterprise Linux 5.5 (32-bit) to Other Linux (32-bit). Change any VMs that have the 64-bit versions of these same OS types to Other Linux (64-bit).
- </div></li><li class="listitem"><div class="para">
- If you upgraded from XenServer 5.6 SP2 to XenServer 6.0.2, change any VMs that have the OS type CentOS 5.6 (32-bit), CentOS 5.7 (32-bit), Oracle Enterprise Linux 5.6 (32-bit), Oracle Enterprise Linux 5.7 (32-bit), Red Hat Enterprise Linux 5.6 (32-bit) , or Red Hat Enterprise Linux 5.7 (32-bit) to Other Linux (32-bit). Change any VMs that have the 64-bit versions of these same OS types to Other Linux (64-bit).
- </div></li><li class="listitem"><div class="para">
- If you upgraded from XenServer 5.6 to XenServer 6.0.2, do all of the above.
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Restart the Management Server and Usage Server. You only need to do this once for all clusters.
- </div><pre class="programlisting"># service cloud-management start
-# service cloud-usage start</pre></li></ol></div></li><li class="listitem"><div class="para">
- Disconnect the XenServer cluster from CloudStack.
- </div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
- Log in to the CloudStack UI as root.
- </div></li><li class="listitem"><div class="para">
- Navigate to the XenServer cluster, and click Actions – Unmanage.
- </div></li><li class="listitem"><div class="para">
- Watch the cluster status until it shows Unmanaged.
- </div></li></ol></div></li><li class="listitem"><div class="para">
- Log in to one of the hosts in the cluster, and run this command to clean up the VLAN:
- </div><pre class="programlisting"># . /opt/xensource/bin/cloud-clean-vlan.sh</pre></li><li class="listitem"><div class="para">
- Still logged in to the host, run the upgrade preparation script:
- </div><pre class="programlisting"># /opt/xensource/bin/cloud-prepare-upgrade.sh</pre><div class="para">
- Troubleshooting: If you see the error "can't eject CD," log in to the VM and umount the CD, then run the script again.
- </div></li><li class="listitem"><div class="para">
- Upgrade the XenServer software on all hosts in the cluster. Upgrade the master first.
- </div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
- Live migrate all VMs on this host to other hosts. See the instructions for live migration in the Administrator's Guide.
- </div><div class="para">
- Troubleshooting: You might see the following error when you migrate a VM:
- </div><pre class="programlisting">[root@xenserver-qa-2-49-4 ~]# xe vm-migrate live=true host=xenserver-qa-2-49-5 vm=i-2-8-VM
-You attempted an operation on a VM which requires PV drivers to be installed but the drivers were not detected.
-vm: b6cf79c8-02ee-050b-922f-49583d9f1a14 (i-2-8-VM)</pre><div class="para">
- To solve this issue, run the following:
- </div><pre class="programlisting"># /opt/xensource/bin/make_migratable.sh b6cf79c8-02ee-050b-922f-49583d9f1a14</pre></li><li class="listitem"><div class="para">
- Reboot the host.
- </div></li><li class="listitem"><div class="para">
- Upgrade to the newer version of XenServer. Use the steps in XenServer documentation.
- </div></li><li class="listitem"><div class="para">
- After the upgrade is complete, copy the following files from the management server to this host, in the directory locations shown below:
- </div><div class="informaltable"><table border="1"><colgroup><col align="left" class="c1" width="50%" /><col align="left" class="c2" width="50%" /></colgroup><thead><tr><th align="left">
- <div class="para">
- Copy this Management Server file...
- </div>
- </th><th align="left">
- <div class="para">
- ...to this location on the XenServer host
- </div>
- </th></tr></thead><tbody><tr><td align="left">
- <div class="para">
- /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py
- </div>
- </td><td align="left">
- <div class="para">
- /opt/xensource/sm/NFSSR.py
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/setupxenserver.sh
- </div>
- </td><td align="left">
- <div class="para">
- /opt/xensource/bin/setupxenserver.sh
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/make_migratable.sh
- </div>
- </td><td align="left">
- <div class="para">
- /opt/xensource/bin/make_migratable.sh
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/cloud-clean-vlan.sh
- </div>
- </td><td align="left">
- <div class="para">
- /opt/xensource/bin/cloud-clean-vlan.sh
- </div>
- </td></tr></tbody></table></div></li><li class="listitem"><div class="para">
- Run the following script:
- </div><pre class="programlisting"># /opt/xensource/bin/setupxenserver.sh</pre><div class="para">
- Troubleshooting: If you see the following error message, you can safely ignore it.
- </div><pre class="programlisting">mv: cannot stat `/etc/cron.daily/logrotate': No such file or directory</pre></li><li class="listitem"><div class="para">
- Plug in the storage repositories (physical block devices) to the XenServer host:
- </div><pre class="programlisting"># for pbd in `xe pbd-list currently-attached=false| grep ^uuid | awk '{print $NF}'`; do xe pbd-plug uuid=$pbd ; done</pre><div class="para">
- Note: If you add a host to this XenServer pool, you need to migrate all VMs on this host to other hosts, and eject this host from XenServer pool.
- </div></li></ol></div></li><li class="listitem"><div class="para">
- Repeat these steps to upgrade every host in the cluster to the same version of XenServer.
- </div></li><li class="listitem"><div class="para">
- Run the following command on one host in the XenServer cluster to clean up the host tags:
- </div><pre class="programlisting"># for host in $(xe host-list | grep ^uuid | awk '{print $NF}') ; do xe host-param-clear uuid=$host param-name=tags; done;</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- 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.
- </div></div></div></li><li class="listitem"><div class="para">
- Reconnect the XenServer cluster to CloudStack.
- </div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
- Log in to the CloudStack UI as root.
- </div></li><li class="listitem"><div class="para">
- Navigate to the XenServer cluster, and click Actions – Manage.
- </div></li><li class="listitem"><div class="para">
- Watch the status to see that all the hosts come up.
- </div></li></ol></div></li><li class="listitem"><div class="para">
- After all hosts are up, run the following on one host in the cluster:
- </div><pre class="programlisting"># /opt/xensource/bin/cloud-clean-vlan.sh</pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="hypervisor-kvm-install-flow.html"><strong>Prev</strong>8.1. KVM Hypervisor Host Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="vmware-install.html"><strong>Next</strong>8.3. VMware vSphere Installation and Configuration</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/cloud-infrastructure-concepts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/cloud-infrastructure-concepts.html b/docs/tmp/en-US/html/cloud-infrastructure-concepts.html
deleted file mode 100644
index a4914fb..0000000
--- a/docs/tmp/en-US/html/cloud-infrastructure-concepts.html
+++ /dev/null
@@ -1,3 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. Cloud Infrastructure Concepts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="index.html" title="CloudStack Administrator's Guide" /><link rel="prev" href="deployment-architecture-overview.html" title="1.3. Deployment Architecture Overview" /><link rel="next" href="about-zones.html" title="2.1. About Zones" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.c
loudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="deployment-architecture-overview.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="about-zones.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="cloud-infrastructure-concepts" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. Cloud Infrastructure Concepts</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="about-zones.html">2.1. About Zones</a></span></dt><dt><span class="section"><a href="about-pods.html">2.2. About Pods</a></span></dt><dt><span class="section"><a href="about-clusters.html">2.3. About Clusters</a></span></dt><dt><span class="section"><a href="about-hosts.html">2.4. About Hosts</a></span></dt><dt><span class="section"><a href="about-primary-storage.html">2.5. About Primary Storage</a></span></dt><
dt><span class="section"><a href="about-secondary-storage.html">2.6. About Secondary Storage</a></span></dt><dt><span class="section"><a href="about-physical-networks.html">2.7. About Physical Networks</a></span></dt><dd><dl><dt><span class="section"><a href="about-physical-networks.html#physical-network-configuration-settings">2.7.1. Configurable Characteristics of Physical Networks</a></span></dt><dt><span class="section"><a href="about-physical-networks.html#basic-zone-network-traffic-types">2.7.2. Basic Zone Network Traffic Types</a></span></dt><dt><span class="section"><a href="about-physical-networks.html#basic-zone-guest-ip-addresses">2.7.3. Basic Zone Guest IP Addresses</a></span></dt><dt><span class="section"><a href="about-physical-networks.html#advanced-zone-network-traffic-types">2.7.4. Advanced Zone Network Traffic Types</a></span></dt><dt><span class="section"><a href="about-physical-networks.html#advanced-zone-guest-ip-addresses">2.7.5. Advanced Zone Guest IP Addresse
s</a></span></dt><dt><span class="section"><a href="about-physical-networks.html#advanced-zone-public-ip-addresses">2.7.6. Advanced Zone Public IP Addresses</a></span></dt><dt><span class="section"><a href="about-physical-networks.html#system-reserved-ip-addresses">2.7.7. System Reserved IP Addresses</a></span></dt></dl></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="deployment-architecture-overview.html"><strong>Prev</strong>1.3. Deployment Architecture Overview</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="about-zones.html"><strong>Next</strong>2.1. About Zones</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/cluster-add.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/cluster-add.html b/docs/tmp/en-US/html/cluster-add.html
deleted file mode 100644
index 9127787..0000000
--- a/docs/tmp/en-US/html/cluster-add.html
+++ /dev/null
@@ -1,61 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.4. Adding a Cluster</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="provisioning-steps.html" title="Chapter 7. Steps to Provisioning Your Cloud Infrastructure" /><link rel="prev" href="pod-add.html" title="7.3. Adding a Pod" /><link rel="next" href="host-add.html" title="7.5. Adding a Host" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="
Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pod-add.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="host-add.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="cluster-add" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="cluster-add">7.4. Adding a Cluster</h2></div></div></div><div class="para">
- You need to tell CloudStack about the hosts that it will manage. Hosts exist inside clusters, so before you begin adding hosts to the cloud, you must add at least one cluster.
- </div><div xml:lang="en-US" class="section" id="add-clusters-kvm-xenserver" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="add-clusters-kvm-xenserver">7.4.1. Add Cluster: KVM or XenServer</h3></div></div></div><div class="para">
- These steps assume you have already installed the hypervisor on the hosts and logged in to the CloudStack UI.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the cluster.
- </div></li><li class="listitem"><div class="para">
- Click the Compute tab.
- </div></li><li class="listitem"><div class="para">
- In the Clusters node of the diagram, click View All.
- </div></li><li class="listitem"><div class="para">
- Click Add Cluster.
- </div></li><li class="listitem"><div class="para">
- Choose the hypervisor type for this cluster.
- </div></li><li class="listitem"><div class="para">
- Choose the pod in which you want to create the cluster.
- </div></li><li class="listitem"><div class="para">
- Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack.
- </div></li><li class="listitem"><div class="para">
- Click OK.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="add-clusters-vsphere" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="add-clusters-vsphere">7.4.2. Add Cluster: vSphere</h3></div></div></div><div class="para">
- Host management for vSphere is done through a combination of vCenter and the CloudStack admin UI. CloudStack requires that all hosts be in a CloudStack cluster, but the cluster may consist of a single host. As an administrator you must decide if you would like to use clusters of one host or of multiple hosts. Clusters of multiple hosts allow for features like live migration. Clusters also require shared storage such as NFS or iSCSI.
- </div><div class="para">
- For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. Follow these requirements:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Do not put more than 8 hosts in a vSphere cluster
- </div></li><li class="listitem"><div class="para">
- Make sure the hypervisor hosts do not have any VMs already running before you add them to CloudStack.
- </div></li></ul></div><div class="para">
- To add a vSphere cluster to CloudStack:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Create the cluster of hosts in vCenter. Follow the vCenter instructions to do this. You will create a cluster that looks something like this in vCenter.
- </div><div class="mediaobject"><img src="./images/vsphere-client.png" width="444" alt="vsphereclient.png: vSphere client" /></div></li><li class="listitem"><div class="para">
- Log in to the UI.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the cluster.
- </div></li><li class="listitem"><div class="para">
- Click the Compute tab, and click View All on Pods. Choose the pod to which you want to add the cluster.
- </div></li><li class="listitem"><div class="para">
- Click View Clusters.
- </div></li><li class="listitem"><div class="para">
- Click Add Cluster.
- </div></li><li class="listitem"><div class="para">
- In Hypervisor, choose VMware.
- </div></li><li class="listitem"><div class="para">
- Provide the following information in the dialog. The fields below make reference to values from vCenter.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Cluster Name. Enter the name of the cluster you created in vCenter. For example, "cloud.cluster.2.2.1"
- </div></li><li class="listitem"><div class="para">
- vCenter Host. Enter the hostname or IP address of the vCenter server.
- </div></li><li class="listitem"><div class="para">
- vCenter Username. Enter the username that CloudStack should use to connect to vCenter. This user must have all administrative privileges.
- </div></li><li class="listitem"><div class="para">
- vCenter Password. Enter the password for the user named above
- </div></li><li class="listitem"><div class="para">
- vCenter Datacenter. Enter the vCenter datacenter that the cluster is in. For example, "cloud.dc.VM".
- </div></li><li class="listitem"><div class="mediaobject"><img src="./images/add-cluster.png" alt="addcluster.png: add cluster" /></div><div class="para">
- There might be a slight delay while the cluster is provisioned. It will automatically display in the UI
- </div></li></ul></div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pod-add.html"><strong>Prev</strong>7.3. Adding a Pod</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="host-add.html"><strong>Next</strong>7.5. Adding a Host</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/compute-disk-service-offerings.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/compute-disk-service-offerings.html b/docs/tmp/en-US/html/compute-disk-service-offerings.html
deleted file mode 100644
index 37dea64..0000000
--- a/docs/tmp/en-US/html/compute-disk-service-offerings.html
+++ /dev/null
@@ -1,97 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.1. Compute and Disk Service Offerings</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="offerings.html" title="Chapter 8. Service Offerings" /><link rel="prev" href="offerings.html" title="Chapter 8. Service Offerings" /><link rel="next" href="system-service-offerings.html" title="8.2. System Service Offerings" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.clouds
tack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="offerings.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="system-service-offerings.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="compute-disk-service-offerings" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="compute-disk-service-offerings">8.1. Compute and Disk Service Offerings</h2></div></div></div><div class="para">
- A service offering is a set of virtual hardware features such as CPU core count and speed, memory, and disk size. The CloudStack administrator can set up various offerings, and then end users choose from the available offerings when they create a new VM. A service offering includes the following elements:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- CPU, memory, and network resource guarantees
- </div></li><li class="listitem"><div class="para">
- How resources are metered
- </div></li><li class="listitem"><div class="para">
- How the resource usage is charged
- </div></li><li class="listitem"><div class="para">
- How often the charges are generated
- </div></li></ul></div><div class="para">
- For example, one service offering might allow users to create a virtual machine instance that is equivalent to a 1 GHz Intel® Core™ 2 CPU, with 1 GB memory at $0.20/hour, with network traffic metered at $0.10/GB. Based on the user’s selected offering, CloudStack emits usage records that can be integrated with billing systems. CloudStack separates service offerings into compute offerings and disk offerings. The computing service offering specifies:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Guest CPU
- </div></li><li class="listitem"><div class="para">
- Guest RAM
- </div></li><li class="listitem"><div class="para">
- Guest Networking type (virtual or direct)
- </div></li><li class="listitem"><div class="para">
- Tags on the root disk
- </div></li></ul></div><div class="para">
- The disk offering specifies:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Disk size (optional). An offering without a disk size will allow users to pick their own
- </div></li><li class="listitem"><div class="para">
- Tags on the data disk
- </div></li></ul></div><div xml:lang="en-US" class="section" id="creating-compute-offerings" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="creating-compute-offerings">8.1.1. Creating a New Compute Offering</h3></div></div></div><div class="para">
- To create a new compute offering:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in with admin privileges to the CloudStack UI.
- </div></li><li class="listitem"><div class="para">
- In the left navigation bar, click Service Offerings.
- </div></li><li class="listitem"><div class="para">
- In Select Offering, choose Compute Offering.
- </div></li><li class="listitem"><div class="para">
- Click Add Compute Offering.
- </div></li><li class="listitem"><div class="para">
- In the dialog, make the following choices:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Name</strong></span>: Any desired name for the service offering.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Description</strong></span>: A short description of the offering that can be displayed to users
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Storage type</strong></span>: The type of disk that should be allocated. Local allocates from storage attached directly to the host where the system VM is running. Shared allocates from storage accessible via NFS.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong># of CPU cores</strong></span>: The number of cores which should be allocated to a system VM with this offering
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>CPU (in MHz)</strong></span>: The CPU speed of the cores that the system VM is allocated. For example, “2000” would provide for a 2 GHz clock.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Memory (in MB)</strong></span>: The amount of memory in megabytes that the system VM should be allocated. For example, “2048” would provide for a 2 GB RAM allocation.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Network Rate</strong></span>: Allowed data transfer rate in MB per second.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Offer HA</strong></span>: If yes, the administrator can choose to have the system VM be monitored and as highly available as possible.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Storage Tags</strong></span>: The tags that should be associated with the primary storage used by the system VM.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Host Tags</strong></span>: (Optional) Any tags that you use to organize your hosts
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>CPU cap</strong></span>: Whether to limit the level of CPU usage even if spare capacity is available.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Public</strong></span>: Indicate whether the service offering should be available all domains or only some domains. Choose Yes to make it available to all domains. Choose No to limit the scope to a subdomain; CloudStack will then prompt for the subdomain's name.
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Click Add.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="creating-disk-offerings" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="creating-disk-offerings">8.1.2. Creating a New Disk Offering</h3></div></div></div><div class="para">
- To create a system service offering:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in with admin privileges to the CloudStack UI.
- </div></li><li class="listitem"><div class="para">
- In the left navigation bar, click Service Offerings.
- </div></li><li class="listitem"><div class="para">
- In Select Offering, choose Disk Offering.
- </div></li><li class="listitem"><div class="para">
- Click Add Disk Offering.
- </div></li><li class="listitem"><div class="para">
- In the dialog, make the following choices:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Name. Any desired name for the system offering.
- </div></li><li class="listitem"><div class="para">
- Description. A short description of the offering that can be displayed to users
- </div></li><li class="listitem"><div class="para">
- Custom Disk Size. If checked, the user can set their own disk size. If not checked, the root administrator must define a value in Disk Size.
- </div></li><li class="listitem"><div class="para">
- Disk Size. Appears only if Custom Disk Size is not selected. Define the volume size in GB.
- </div></li><li class="listitem"><div class="para">
- (Optional)Storage Tags. The tags that should be associated with the primary storage for this disk. Tags are a comma separated list of attributes of the storage. For example "ssd,blue". Tags are also added on Primary Storage. CloudStack matches tags on a disk offering to tags on the storage. If a tag is present on a disk offering that tag (or tags) must also be present on Primary Storage for the volume to be provisioned. If no such primary storage exists, allocation from the disk offering will fail..
- </div></li><li class="listitem"><div class="para">
- Public. Indicate whether the service offering should be available all domains or only some domains. Choose Yes to make it available to all domains. Choose No to limit the scope to a subdomain; CloudStack will then prompt for the subdomain's name.
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Click Add.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="modify-delete-service-offerings" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="modify-delete-service-offerings">8.1.3. Modifying or Deleting a Service Offering</h3></div></div></div><div class="para">
- Service offerings cannot be changed once created. This applies to both compute offerings and disk offerings.
- </div><div class="para">
- A service offering can be deleted. If it is no longer in use, it is deleted immediately and permanently. If the service offering is still in use, it will remain in the database until all the virtual machines referencing it have been deleted. After deletion by the administrator, a service offering will not be available to end users that are creating new instances.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="offerings.html"><strong>Prev</strong>Chapter 8. Service Offerings</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="system-service-offerings.html"><strong>Next</strong>8.2. System Service Offerings</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/concepts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/concepts.html b/docs/tmp/en-US/html/concepts.html
deleted file mode 100644
index 0fd5d86..0000000
--- a/docs/tmp/en-US/html/concepts.html
+++ /dev/null
@@ -1,3 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 1. Concepts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-API_Developers_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack API Developer's Guide" /><link rel="up" href="index.html" title="CloudStack API Developer's Guide" /><link rel="prev" href="index.html" title="CloudStack API Developer's Guide" /><link rel="next" href="whatis.html" title="1.1. What Is CloudStack?" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/im
ages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="whatis.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="concepts" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Concepts</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="whatis.html">1.1. What Is CloudStack?</a></span></dt><dt><span class="section"><a href="feature-overview.html">1.2. What Can CloudStack Do?</a></span></dt><dt><span class="section"><a href="deployment-architecture-overview.html">1.3. Deployment Architecture Overview</a></span></dt><dd><dl><dt><span class="section"><a href="deployment-architecture-overview.html#management-server-overview">1.3.1. Management Server Overview</a></span></dt><dt><span class="section"><a href="deployment-architecture-overview.html#cloud-infrastructu
re-overview">1.3.2. Cloud Infrastructure Overview</a></span></dt><dt><span class="section"><a href="deployment-architecture-overview.html#networking-overview">1.3.3. Networking Overview</a></span></dt></dl></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong>CloudStack API Developer's Guide</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="whatis.html"><strong>Next</strong>1.1. What Is CloudStack?</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/configure-package-repository.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/configure-package-repository.html b/docs/tmp/en-US/html/configure-package-repository.html
deleted file mode 100644
index 64e8dbd..0000000
--- a/docs/tmp/en-US/html/configure-package-repository.html
+++ /dev/null
@@ -1,36 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.4. Configure package repository</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="installation.html" title="Chapter 4. Installation" /><link rel="prev" href="minimum-system-requirements.html" title="4.3. Minimum System Requirements" /><link rel="next" href="management-server-install-flow.html" title="4.5. Management Server Installation" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="ri
ght" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="minimum-system-requirements.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="management-server-install-flow.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="configure-package-repository" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="configure-package-repository">4.4. Configure package repository</h2></div></div></div><div class="para">
- CloudStack is only distributed from source from the official mirrors. However, members of the CloudStack community may build convenience binaries so that users can install Apache CloudStack without needing to build from source.
- </div><div class="para">
- If you didn't follow the steps to build your own packages from source in the sections for <a class="xref" href="sect-source-buildrpm.html">Section 3.6, “Building RPMs”</a> or <a class="xref" href="sect-source-builddebs.html">Section 3.5, “Building DEB packages”</a> you may find pre-built DEB and RPM packages for your convience linked from the <a href="http://incubator.apache.org/cloudstack/downloads.html">downloads</a> page.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- These repositories contain both the Management Server and KVM Hypervisor packages.
- </div></div></div><div class="section" id="configure-package-repository-deb"><div class="titlepage"><div><div><h3 class="title" id="configure-package-repository-deb">4.4.1. DEB package repository</h3></div></div></div><div class="para">
- You can add a DEB package repository to your apt sources with the following commands. Please note that currently only packages for Ubuntu 12.04 LTS (precise) are being build.
- </div><div class="para">
- Use your preferred editor and open (or create) <code class="filename">/etc/apt/sources.list.d/cloudstack</code>. Add the community provided repository to the file:
- </div><pre class="programlisting">deb http://cloudstack.apt-get.eu/ubuntu precise 4.0</pre><div class="para">
- We now have to add the public key to the trusted keys.
- </div><pre class="programlisting">$ <span class="perl_BString">wget</span> -O - http://cloudstack.apt-get.eu/release.asc<span class="perl_Keyword">|</span>apt-key add -</pre><div class="para">
- Now update your local apt cache.
- </div><pre class="programlisting">$ apt-get update</pre><div class="para">
- Your DEB package repository should now be configured and ready for use.
- </div></div><div class="section" id="configure-package-repository-rpm"><div class="titlepage"><div><div><h3 class="title" id="configure-package-repository-rpm">4.4.2. RPM package repository</h3></div></div></div><div class="para">
- If you're using an RPM-based system, you'll want to add the Yum repository so that you can install CloudStack with Yum.
- </div><div class="para">
- Yum repository information is found under <code class="filename">/etc/yum.repos.d</code>. You'll see several <code class="filename">.repo</code> files in this directory, each one denoting a specific repository.
- </div><div class="para">
- To add the CloudStack repository, visit the <a href="http://incubator.apache.org/cloudstack/downloads.html">downloads page</a> for the repository information. It will look something like this:
- </div><pre class="programlisting">
-[cloudstack]
-name=cloudstack
-baseurl=<em class="replaceable"><code>http://server.url/downloads/rpm/stable/</code></em>
-enabled=1
-gpgcheck=1
-</pre><div class="para">
- Next you'll want to add the GPG key:
- </div><pre class="screen">
-<code class="command">$ rpm --import http://server.url/downloads/RPM-GPG-KEY.txt</code></pre><div class="para">
- Now you should be able to install CloudStack using Yum.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="minimum-system-requirements.html"><strong>Prev</strong>4.3. Minimum System Requirements</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="management-server-install-flow.html"><strong>Next</strong>4.5. Management Server Installation</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/configure-usage-server.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/configure-usage-server.html b/docs/tmp/en-US/html/configure-usage-server.html
deleted file mode 100644
index b9a7432..0000000
--- a/docs/tmp/en-US/html/configure-usage-server.html
+++ /dev/null
@@ -1,123 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.1. Configuring the Usage Server</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="work-with-usage.html" title="Chapter 14. Working with Usage" /><link rel="prev" href="work-with-usage.html" title="Chapter 14. Working with Usage" /><link rel="next" href="set-usage-limit.html" title="14.2. Setting Usage Limits" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudst
ack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="work-with-usage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="set-usage-limit.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="configure-usage-server" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="configure-usage-server">14.1. Configuring the Usage Server</h2></div></div></div><div class="para">
- To configure the usage server:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Be sure the Usage Server has been installed. This requires extra steps beyond just installing the CloudStack software. See Installing the Usage Server (Optional) in the Advanced Installation Guide.
- </div></li><li class="listitem"><div class="para">
- Log in to the CloudStack UI as administrator.
- </div></li><li class="listitem"><div class="para">
- Click Global Settings.
- </div></li><li class="listitem"><div class="para">
- In Search, type usage. Find the configuration parameter that controls the behavior you want to set. See the table below for a description of the available parameters.
- </div></li><li class="listitem"><div class="para">
- In Actions, click the Edit icon.
- </div></li><li class="listitem"><div class="para">
- Type the desired value and click the Save icon.
- </div></li><li class="listitem"><div class="para">
- Restart the Management Server (as usual with any global configuration change) and also the Usage Server:
- </div><pre class="programlisting"># service cloud-management restart
-# service cloud-usage restart
-</pre></li></ol></div><div class="para">
- The following table shows the global configuration settings that control the behavior of the Usage Server.
- </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th align="left">
- <div class="para">
- Parameter Name
- </div>
- </th><th align="left">
- <div class="para">
- Description
- </div>
- </th></tr></thead><tbody><tr><td align="left">
- <div class="para">
- enable.usage.server
- </div>
- </td><td align="left">
- <div class="para">
- Whether the Usage Server is active.
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- usage.aggregation.timezone
- </div>
- </td><td align="left">
- <div class="para">
- Time zone of usage records. Set this if the usage records and daily job execution are in different time zones. For example, with the following settings, the usage job will run at PST 00:15 and generate usage records for the 24 hours from 00:00:00 GMT to 23:59:59 GMT:
- </div>
-
-<pre class="programlisting">usage.stats.job.exec.time = 00:15
-usage.execution.timezone = PST
-usage.aggregation.timezone = GMT
-</pre>
- <div class="para">
- Valid values for the time zone are specified in <a class="xref" href="time-zones.html">Appendix A, <em>Time Zones</em></a>
- </div>
- <div class="para">
- Default: GMT
- </div>
-
- </td></tr><tr><td align="left">
- <div class="para">
- usage.execution.timezone
- </div>
- </td><td align="left">
- <div class="para">
- The time zone of usage.stats.job.exec.time. Valid values for the time zone are specified in <a class="xref" href="time-zones.html">Appendix A, <em>Time Zones</em></a>
- </div>
- <div class="para">
- Default: The time zone of the management server.
- </div>
-
- </td></tr><tr><td align="left">
- <div class="para">
- usage.sanity.check.interval
- </div>
- </td><td align="left">
- <div class="para">
- The number of days between sanity checks. Set this in order to periodically search for records with erroneous data before issuing customer invoices. For example, this checks for VM usage records created after the VM was destroyed, and similar checks for templates, volumes, and so on. It also checks for usage times longer than the aggregation range. If any issue is found, the alert ALERT_TYPE_USAGE_SANITY_RESULT = 21 is sent.
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- usage.stats.job.aggregation.range
- </div>
- </td><td align="left">
- <div class="para">
- The time period in minutes between Usage Server processing jobs. For example, if you set it to 1440, the Usage Server will run once per day. If you set it to 600, it will run every ten hours. In general, when a Usage Server job runs, it processes all events generated since usage was last run.
- </div>
- <div class="para">
- There is special handling for the case of 1440 (once per day). In this case the Usage Server does not necessarily process all records since Usage was last run. CloudStack assumes that you require processing once per day for the previous, complete day’s records. For example, if the current day is October 7, then it is assumed you would like to process records for October 6, from midnight to midnight. CloudStack assumes this "midnight to midnight" is relative to the usage.execution.timezone.
- </div>
- <div class="para">
- Default: 1440
- </div>
-
- </td></tr><tr><td align="left">
- <div class="para">
- usage.stats.job.exec.time
- </div>
- </td><td align="left">
- <div class="para">
- The time when the Usage Server processing will start. It is specified in 24-hour format (HH:MM) in the time zone of the server, which should be GMT. For example, to start the Usage job at 10:30 GMT, enter "10:30".
- </div>
- <div class="para">
- If usage.stats.job.aggregation.range is also set, and its value is not 1440, then its value will be added to usage.stats.job.exec.time to get the time to run the Usage Server job again. This is repeated until 24 hours have elapsed, and the next day's processing begins again at usage.stats.job.exec.time.
- </div>
- <div class="para">
- Default: 00:15.
- </div>
-
- </td></tr></tbody></table></div><div class="para">
- For example, suppose that your server is in GMT, your user population is predominantly in the East Coast of the United States, and you would like to process usage records every night at 2 AM local (EST) time. Choose these settings:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- enable.usage.server = true
- </div></li><li class="listitem"><div class="para">
- usage.execution.timezone = America/New_York
- </div></li><li class="listitem"><div class="para">
- usage.stats.job.exec.time = 07:00. This will run the Usage job at 2:00 AM EST. Note that this will shift by an hour as the East Coast of the U.S. enters and exits Daylight Savings Time.
- </div></li><li class="listitem"><div class="para">
- usage.stats.job.aggregation.range = 1440
- </div></li></ul></div><div class="para">
- With this configuration, the Usage job will run every night at 2 AM EST and will process records for the previous day’s midnight-midnight as defined by the EST (America/New_York) time zone.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- Because the special value 1440 has been used for usage.stats.job.aggregation.range, the Usage Server will ignore the data between midnight and 2 AM. That data will be included in the next day's run
- </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="work-with-usage.html"><strong>Prev</strong>Chapter 14. Working with Usage</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="set-usage-limit.html"><strong>Next</strong>14.2. Setting Usage Limits</a></li></ul></body></html>