You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by wi...@apache.org on 2013/01/15 10:36:31 UTC
[44/52] [partial] Remove docs/tmp (partial revert)
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/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/9b4ee042/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 4f5a60c..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-Installation_Guide-4.0.1-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="index.html" title="CloudStack Installation Guide" /><link rel="prev" href="index.html" title="CloudStack Installation 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/images/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-infrastructure-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 Installation 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/9b4ee042/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 81c6205..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.1-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/9b4ee042/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>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/configure-vpc.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/configure-vpc.html b/docs/tmp/en-US/html/configure-vpc.html
deleted file mode 100644
index 3779fa8..0000000
--- a/docs/tmp/en-US/html/configure-vpc.html
+++ /dev/null
@@ -1,519 +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>11.19. Configuring a Virtual Private Cloud</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.1-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="networks.html" title="Chapter 11. Managing Networks and Traffic" /><link rel="prev" href="inter-vlan-routing.html" title="11.18. About Inter-VLAN Routing" /><link rel="next" href="appe-cloudstack-Revision_History.html" title="Appendix A. Revision History" /></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="inter-vlan-routing.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="appe-cloudstack-Revision_History.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="configure-vpc" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="configure-vpc">11.19. Configuring a Virtual Private Cloud</h2></div></div></div><div xml:lang="en-US" class="section" id="vpc" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="vpc">11.19.1. About Virtual Private Clouds</h3></div></div></div><div class="para">
- CloudStack Virtual Private Cloud is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. You can launch VMs in the virtual network that can have private addresses in the range of your choice, for example: 10.0.0.0/16. You can define network tiers within your VPC network range, which in turn enables you to group similar kinds of instances based on IP address range.
- </div><div class="para">
- For example, if a VPC has the private range 10.0.0.0/16, its guest networks can have the network ranges 10.0.1.0/24, 10.0.2.0/24, 10.0.3.0/24, and so on.
- </div><div class="formalpara"><h5 class="formalpara" id="idp25470656">Major Components of a VPC:</h5>
- A VPC is comprised of the following network components:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>VPC</strong></span>: A VPC acts as a container for multiple isolated networks that can communicate with each other via its virtual router.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Network Tiers</strong></span>: Each tier acts as an isolated network with its own VLANs and CIDR list, where you can place groups of resources, such as VMs. The tiers are segmented by means of VLANs. The NIC of each tier acts as its gateway.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Virtual Router</strong></span>: A virtual router is automatically created and started when you create a VPC. The virtual router connect the tiers and direct traffic among the public gateway, the VPN gateways, and the NAT instances. For each tier, a corresponding NIC and IP exist in the virtual router. The virtual router provides DNS and DHCP services through its IP.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Public Gateway</strong></span>: The traffic to and from the Internet routed to the VPC through the public gateway. In a VPC, the public gateway is not exposed to the end user; therefore, static routes are not support for the public gateway.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Private Gateway</strong></span>: All the traffic to and from a private network routed to the VPC through the private gateway. For more information, see <a class="xref" href="configure-vpc.html#add-gateway-vpc">Section 11.19.5, “Adding a Private Gateway to a VPC”</a>.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>VPN Gateway</strong></span>: The VPC side of a VPN connection.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Site-to-Site VPN Connection</strong></span>: A hardware-based VPN connection between your VPC and your datacenter, home network, or co-location facility. For more information, see <a class="xref" href="vpn.html#site-to-site-vpn">Section 11.17.4, “Setting Up a Site-to-Site VPN Connection”</a>.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Customer Gateway</strong></span>: The customer side of a VPN Connection. For more information, see <a class="xref" href="vpn.html#create-vpn-customer-gateway">Section 11.17.4.1, “Creating and Updating a VPN Customer Gateway”</a>.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>NAT Instance</strong></span>: An instance that provides Port Address Translation for instances to access the Internet via the public gateway. For more information, see <a class="xref" href="configure-vpc.html#enable-disable-static-nat-vpc">Section 11.19.9, “Enabling or Disabling Static NAT on a VPC”</a>.
- </div></li></ul></div><div class="formalpara"><h5 class="formalpara" id="idp16110800">Network Architecture in a VPC</h5>
- In a VPC, the following four basic options of network architectures are present:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- VPC with a public gateway only
- </div></li><li class="listitem"><div class="para">
- VPC with public and private gateways
- </div></li><li class="listitem"><div class="para">
- VPC with public and private gateways and site-to-site VPN access
- </div></li><li class="listitem"><div class="para">
- VPC with a private gateway only and site-to-site VPN access
- </div></li></ul></div><div class="formalpara"><h5 class="formalpara" id="idp18471560">Connectivity Options for a VPC</h5>
- You can connect your VPC to:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- The Internet through the public gateway.
- </div></li><li class="listitem"><div class="para">
- The corporate datacenter by using a site-to-site VPN connection through the VPN gateway.
- </div></li><li class="listitem"><div class="para">
- Both the Internet and your corporate datacenter by using both the public gateway and a VPN gateway.
- </div></li></ul></div><div class="formalpara"><h5 class="formalpara" id="idp14345584">VPC Network Considerations</h5>
- Consider the following before you create a VPC:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- A VPC, by default, is created in the enabled state.
- </div></li><li class="listitem"><div class="para">
- A VPC can be created in Advance zone only, and can't belong to more than one zone at a time.
- </div></li><li class="listitem"><div class="para">
- The default number of VPCs an account can create is 20. However, you can change it by using the max.account.vpcs global parameter, which controls the maximum number of VPCs an account is allowed to create.
- </div></li><li class="listitem"><div class="para">
- The default number of tiers an account can create within a VPC is 3. You can configure this number by using the vpc.max.networks parameter.
- </div></li><li class="listitem"><div class="para">
- Each tier should have an unique CIDR in the VPC. Ensure that the tier's CIDR should be within the VPC CIDR range.
- </div></li><li class="listitem"><div class="para">
- A tier belongs to only one VPC.
- </div></li><li class="listitem"><div class="para">
- All network tiers inside the VPC should belong to the same account.
- </div></li><li class="listitem"><div class="para">
- When a VPC is created, by default, a SourceNAT IP is allocated to it. The Source NAT IP is released only when the VPC is removed.
- </div></li><li class="listitem"><div class="para">
- A public IP can be used for only one purpose at a time. If the IP is a sourceNAT, it cannot be used for StaticNAT or port forwarding.
- </div></li><li class="listitem"><div class="para">
- The instances only have a private IP address that you provision. To communicate with the Internet, enable NAT to an instance that you launch in your VPC.
- </div></li><li class="listitem"><div class="para">
- Only new networks can be added to a VPC. The maximum number of networks per VPC is limited by the value you specify in the vpc.max.networks parameter. The default value is three.
- </div></li><li class="listitem"><div class="para">
- The load balancing service can be supported by only one tier inside the VPC.
- </div></li><li class="listitem"><div class="para">
- If an IP address is assigned to a tier:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- That IP can't be used by more than one tier at a time in the VPC. For example, if you have tiers A and B, and a public IP1, you can create a port forwarding rule by using the IP either for A or B, but not for both.
- </div></li><li class="listitem"><div class="para">
- That IP can't be used for StaticNAT, load balancing, or port forwarding rules for another guest network inside the VPC.
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Remote access VPN is not supported in VPC networks.
- </div></li></ul></div></div><div xml:lang="en-US" class="section" id="add-vpc" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="add-vpc">11.19.2. Adding a Virtual Private Cloud</h3></div></div></div><div class="para">
- When creating the VPC, you simply provide the zone and a set of IP addresses for the VPC network address space. You specify this set of addresses in the form of a Classless Inter-Domain Routing (CIDR) block.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div></li><li class="listitem"><div class="para">
- Click Add VPC. The Add VPC page is displayed as follows:
- </div><div class="mediaobject"><img src="./images/add-vpc.png" alt="add-vpc.png: adding a vpc." /></div><div class="para">
- Provide the following information:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Name</strong></span>: A short name for the VPC that you are creating.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Description</strong></span>: A brief description of the VPC.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Zone</strong></span>: Choose the zone where you want the VPC to be available.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Super CIDR for Guest Networks</strong></span>: Defines the CIDR range for all the tiers (guest networks) within a VPC. When you create a tier, ensure that its CIDR is within the Super CIDR value you enter. The CIDR must be RFC1918 compliant.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>DNS domain for Guest Networks</strong></span>: If you want to assign a special domain name, specify the DNS suffix. This parameter is applied to all the tiers within the VPC. That implies, all the tiers you create in the VPC belong to the same DNS domain. If the parameter is not specified, a DNS domain name is generated automatically.
- </div></li></ul></div></li></ol></div></div><div xml:lang="en-US" class="section" id="add-tier" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="add-tier">11.19.3. Adding Tiers</h3></div></div></div><div class="para">
- Tiers are distinct locations within a VPC that act as isolated networks, which do not have access to other tiers by default. Tiers are set up on different VLANs that can communicate with each other by using a virtual router. Tiers provide inexpensive, low latency network connectivity to other tiers within the VPC.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div><div class="para">
- All the VPC that you have created for the account is listed in the page.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- The end users can see their own VPCs, while root and domain admin can see any VPC they are authorized to see.
- </div></div></div></li><li class="listitem"><div class="para">
- Click the Configure button of the VPC for which you want to set up tiers.
- </div><div class="para">
- The Add new tier dialog is displayed, as follows:
- </div><div class="mediaobject"><img src="./images/add-tier.png" alt="add-tier.png: adding a tier to a vpc." /></div><div class="para">
- If you have already created tiers, the VPC diagram is displayed. Click Create Tier to add a new tier.
- </div></li><li class="listitem"><div class="para">
- Specify the following:
- </div><div class="para">
- All the fields are mandatory.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Name</strong></span>: A unique name for the tier you create.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Network Offering</strong></span>: The following default network offerings are listed: DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, DefaultIsolatedNetworkOfferingForVpcNetworks
- </div><div class="para">
- In a VPC, only one tier can be created by using LB-enabled network offering.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Gateway</strong></span>: The gateway for the tier you create. Ensure that the gateway is within the Super CIDR range that you specified while creating the VPC, and is not overlapped with the CIDR of any existing tier within the VPC.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Netmask</strong></span>: The netmask for the tier you create.
- </div><div class="para">
- For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is 10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the tier is 255.255.255.0.
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Click OK.
- </div></li><li class="listitem"><div class="para">
- Continue with configuring access control list for the tier.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="configure-acl" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="configure-acl">11.19.4. Configuring Access Control List</h3></div></div></div><div class="para">
- Define Network Access Control List (ACL) on the VPC virtual router to control incoming (ingress) and outgoing (egress) traffic between the VPC tiers, and the tiers and Internet. By default, all incoming and outgoing traffic to the guest networks is blocked. To open the ports, you must create a new network ACL. The network ACLs can be created for the tiers only if the NetworkACL service is supported.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div><div class="para">
- All the VPCs that you have created for the account is listed in the page.
- </div></li><li class="listitem"><div class="para">
- Click the Settings icon.
- </div><div class="para">
- The following options are displayed.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- IP Addresses
- </div></li><li class="listitem"><div class="para">
- Gateways
- </div></li><li class="listitem"><div class="para">
- Site-to-Site VPN
- </div></li><li class="listitem"><div class="para">
- Network ACLs
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Select Network ACLs.
- </div><div class="para">
- The Network ACLs page is displayed.
- </div></li><li class="listitem"><div class="para">
- Click Add Network ACLs.
- </div><div class="para">
- To add an ACL rule, fill in the following fields to specify what kind of network traffic is allowed in this tier.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>CIDR</strong></span>: The CIDR acts as the Source CIDR for the Ingress rules, and Destination CIDR for the Egress rules. To accept traffic only from or to the IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is the base IP address of the incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Protocol</strong></span>: The networking protocol that sources use to send traffic to the tier. The TCP and UDP protocols are typically used for data exchange and end-user communications. The ICMP protocol is typically used to send error messages or network monitoring data.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Start Port</strong></span>, <span class="bold bold"><strong>End Port</strong></span> (TCP, UDP only): A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Select Tier</strong></span>: Select the tier for which you want to add this ACL rule.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>ICMP Type</strong></span>, <span class="bold bold"><strong>ICMP Code</strong></span> (ICMP only): The type of message and error code that will be sent.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Traffic Type</strong></span>: Select the traffic type you want to apply.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Egress</strong></span>: To add an egress rule, select Egress from the Traffic type drop-down box and click Add. This specifies what type of traffic is allowed to be sent out of VM instances in this tier. If no egress rules are specified, all traffic from the tier is allowed out at the VPC virtual router. Once egress rules are specified, only the traffic specified in egress rules and the responses to any traffic that has been allowed in through an ingress rule are allowed out. No egress rule is required for the VMs in a tier to communicate with each other.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Ingress</strong></span>: To add an ingress rule, select Ingress from the Traffic type drop-down box and click Add. This specifies what network traffic is allowed into the VM instances in this tier. If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule.
- </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- By default, all incoming and outgoing traffic to the guest networks is blocked. To open the ports, create a new network ACL.
- </div></div></div></li></ul></div></li><li class="listitem"><div class="para">
- Click Add. The ACL rule is added.
- </div><div class="para">
- To view the list of ACL rules you have added, click the desired tier from the Network ACLs page, then select the Network ACL tab.
- </div><div class="mediaobject"><img src="./images/network-acl.png" width="444" alt="network-acl.png: adding, editing, deleting an ACL rule." /></div><div class="para">
- You can edit the tags assigned to the ACL rules and delete the ACL rules you have created. Click the appropriate button in the Actions column.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="add-gateway-vpc" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="add-gateway-vpc">11.19.5. Adding a Private Gateway to a VPC</h3></div></div></div><div class="para">
- A private gateway can be added by the root admin only. The VPC private network has 1:1 relationship with the NIC of the physical network. No gateways with duplicated VLAN and IP are allowed in the same data center.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div><div class="para">
- All the VPCs that you have created for the account is listed in the page.
- </div></li><li class="listitem"><div class="para">
- Click the Configure button of the VPC to which you want to configure load balancing rules.
- </div><div class="para">
- The VPC page is displayed where all the tiers you created are listed in a diagram.
- </div></li><li class="listitem"><div class="para">
- Click the Settings icon.
- </div><div class="para">
- The following options are displayed.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- IP Addresses
- </div></li><li class="listitem"><div class="para">
- Private Gateways
- </div></li><li class="listitem"><div class="para">
- Site-to-Site VPN
- </div></li><li class="listitem"><div class="para">
- Network ACLs
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Select Private Gateways.
- </div><div class="para">
- The Gateways page is displayed.
- </div></li><li class="listitem"><div class="para">
- Click Add new gateway:
- </div><div class="mediaobject"><img src="./images/add-new-gateway-vpc.png" alt="add-new-gateway-vpc.png: adding a private gateway for the VPC." /></div></li><li class="listitem"><div class="para">
- Specify the following:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Physical Network</strong></span>: The physical network you have created in the zone.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>IP Address</strong></span>: The IP address associated with the VPC gateway.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Gateway</strong></span>: The gateway through which the traffic is routed to and from the VPC.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Netmask</strong></span>: The netmask associated with the VPC gateway.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>VLAN</strong></span>: The VLAN associated with the VPC gateway.
- </div></li></ul></div><div class="para">
- The new gateway appears in the list. You can repeat these steps to add more gateway for this VPC.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="add-vm-to-tier" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="add-vm-to-tier">11.19.6. Deploying VMs to the Tier</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div><div class="para">
- All the VPCs that you have created for the account is listed in the page.
- </div></li><li class="listitem"><div class="para">
- Click the Configure button of the VPC to which you want to deploy the VMs.
- </div><div class="para">
- The VPC page is displayed where all the tiers you created are listed.
- </div></li><li class="listitem"><div class="para">
- Click the Add VM button of the tier for which you want to add a VM.
- </div><div class="para">
- The Add Instance page is displayed.
- </div><div class="para">
- Follow the on-screen instruction to add an instance. For information on adding an instance, see Adding Instances section in the Installation Guide.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="acquire-new-ip-for-vpc" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="acquire-new-ip-for-vpc">11.19.7. Acquiring a New IP Address for a VPC</h3></div></div></div><div class="para">
- When you acquire an IP address, all IP addresses are allocated to VPC, not to the guest networks within the VPC. The IPs are associated to the guest network only when the first port-forwarding, load balancing, or Static NAT rule is created for the IP or the network. IP can't be associated to more than one network at a time.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div><div class="para">
- All the VPCs that you have created for the account is listed in the page.
- </div></li><li class="listitem"><div class="para">
- Click the Configure button of the VPC to which you want to deploy the VMs.
- </div><div class="para">
- The VPC page is displayed where all the tiers you created are listed in a diagram.
- </div></li><li class="listitem"><div class="para">
- Click the Settings icon.
- </div><div class="para">
- The following options are displayed.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- IP Addresses
- </div></li><li class="listitem"><div class="para">
- Gateways
- </div></li><li class="listitem"><div class="para">
- Site-to-Site VPN
- </div></li><li class="listitem"><div class="para">
- Network ACLs
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Select IP Addresses.
- </div><div class="para">
- The IP Addresses page is displayed.
- </div></li><li class="listitem"><div class="para">
- Click Acquire New IP, and click Yes in the confirmation dialog.
- </div><div class="para">
- You are prompted for confirmation because, typically, IP addresses are a limited resource. Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding, load balancing, and static NAT rules.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="release-ip-for-vpc" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="release-ip-for-vpc">11.19.8. Releasing an IP Address Alloted to a VPC</h3></div></div></div><div class="para">
- The IP address is a limited resource. If you no longer need a particular IP, you can disassociate it from its VPC and return it to the pool of available addresses. An IP address can be released from its tier, only when all the networking ( port forwarding, load balancing, or StaticNAT ) rules are removed for this IP address. The released IP address will still belongs to the same VPC.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div><div class="para">
- All the VPCs that you have created for the account is listed in the page.
- </div></li><li class="listitem"><div class="para">
- Click the Configure button of the VPC whose IP you want to release.
- </div><div class="para">
- The VPC page is displayed where all the tiers you created are listed in a diagram.
- </div></li><li class="listitem"><div class="para">
- Click the Settings icon.
- </div><div class="para">
- The following options are displayed.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- IP Addresses
- </div></li><li class="listitem"><div class="para">
- Gateways
- </div></li><li class="listitem"><div class="para">
- Site-to-Site VPN
- </div></li><li class="listitem"><div class="para">
- Network ACLs
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Select IP Addresses.
- </div><div class="para">
- The IP Addresses page is displayed.
- </div></li><li class="listitem"><div class="para">
- Click the IP you want to release.
- </div></li><li class="listitem"><div class="para">
- In the Details tab, click the Release IP button
- <span class="inlinemediaobject"><img src="./images/release-ip-icon.png" alt="release-ip-icon.png: button to release an IP." /></span>
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="enable-disable-static-nat-vpc" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="enable-disable-static-nat-vpc">11.19.9. Enabling or Disabling Static NAT on a VPC</h3></div></div></div><div class="para">
- A static NAT rule maps a public IP address to the private IP address of a VM in a VPC to allow Internet traffic to it. This section tells how to enable or disable static NAT for a particular IP address in a VPC.
- </div><div class="para">
- If port forwarding rules are already in effect for an IP address, you cannot enable static NAT to that IP.
- </div><div class="para">
- If a guest VM is part of more than one network, static NAT rules will function only if they are defined on the default network.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div><div class="para">
- All the VPCs that you have created for the account is listed in the page.
- </div></li><li class="listitem"><div class="para">
- Click the Configure button of the VPC to which you want to deploy the VMs.
- </div><div class="para">
- The VPC page is displayed where all the tiers you created are listed in a diagram.
- </div></li><li class="listitem"><div class="para">
- Click the Settings icon.
- </div><div class="para">
- The following options are displayed.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- IP Addresses
- </div></li><li class="listitem"><div class="para">
- Gateways
- </div></li><li class="listitem"><div class="para">
- Site-to-Site VPN
- </div></li><li class="listitem"><div class="para">
- Network ACLs
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Select IP Addresses.
- </div><div class="para">
- The IP Addresses page is displayed.
- </div></li><li class="listitem"><div class="para">
- Click the IP you want to work with.
- </div></li><li class="listitem"><div class="para">
- In the Details tab,click the Static NAT button.
- <span class="inlinemediaobject"><img src="./images/enable-disable.png" alt="enable-disable.png: button to enable Statid NAT." /></span>
- The button toggles between Enable and Disable, depending on whether static NAT is currently enabled for the IP address.
- </div></li><li class="listitem"><div class="para">
- If you are enabling static NAT, a dialog appears as follows:
- </div><div class="mediaobject"><img src="./images/select-vm-staticnat-vpc.png" width="444" alt="select-vmstatic-nat.png: selecting a tier to apply staticNAT." /></div></li><li class="listitem"><div class="para">
- Select the tier and the destination VM, then click Apply.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="add-loadbalancer-rule-vpc" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="add-loadbalancer-rule-vpc">11.19.10. Adding Load Balancing Rules on a VPC</h3></div></div></div><div class="para">
- A CloudStack user or administrator may create load balancing rules that balance traffic received at a public IP to one or more VMs that belong to a network tier that provides load balancing service in a VPC. A user creates a rule, specifies an algorithm, and assigns the rule to a set of VMs within a VPC.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div><div class="para">
- All the VPCs that you have created for the account is listed in the page.
- </div></li><li class="listitem"><div class="para">
- Click the Configure button of the VPC to which you want to configure load balancing rules.
- </div><div class="para">
- The VPC page is displayed where all the tiers you created are listed in a diagram.
- </div></li><li class="listitem"><div class="para">
- Click the Settings icon.
- </div><div class="para">
- The following options are displayed.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- IP Addresses
- </div></li><li class="listitem"><div class="para">
- Gateways
- </div></li><li class="listitem"><div class="para">
- Site-to-Site VPN
- </div></li><li class="listitem"><div class="para">
- Network ACLs
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Select IP Addresses.
- </div><div class="para">
- The IP Addresses page is displayed.
- </div></li><li class="listitem"><div class="para">
- Click the IP address for which you want to create the rule, then click the Configuration tab.
- </div></li><li class="listitem"><div class="para">
- In the Load Balancing node of the diagram, click View All.
- </div></li><li class="listitem"><div class="para">
- Select the tier to which you want to apply the rule.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- In a VPC, the load balancing service is supported only on a single tier.
- </div></div></div></li><li class="listitem"><div class="para">
- Specify the following:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Name</strong></span>: A name for the load balancer rule.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Public Port</strong></span>: The port that receives the incoming traffic to be balanced.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Private Port</strong></span>: The port that the VMs will use to receive the traffic.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Algorithm</strong></span>. Choose the load balancing algorithm you want CloudStack to use. CloudStack supports the following well-known algorithms:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Round-robin
- </div></li><li class="listitem"><div class="para">
- Least connections
- </div></li><li class="listitem"><div class="para">
- Source
- </div></li></ul></div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Stickiness</strong></span>. (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Add VMs</strong></span>: Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply.
- </div></li></ul></div></li></ol></div><div class="para">
- The new load balancing rule appears in the list. You can repeat these steps to add more load balancing rules for this IP address.
- </div></div><div xml:lang="en-US" class="section" id="add-portforward-vpc" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="add-portforward-vpc">11.19.11. Adding a Port Forwarding Rule on a VPC</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div><div class="para">
- All the VPCs that you have created for the account is listed in the page.
- </div></li><li class="listitem"><div class="para">
- Click the Configure button of the VPC to which you want to deploy the VMs.
- </div><div class="para">
- The VPC page is displayed where all the tiers you created are listed in a diagram.
- </div></li><li class="listitem"><div class="para">
- Click the Settings icon.
- </div><div class="para">
- The following options are displayed.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- IP Addresses
- </div></li><li class="listitem"><div class="para">
- Gateways
- </div></li><li class="listitem"><div class="para">
- Site-to-Site VPN
- </div></li><li class="listitem"><div class="para">
- Network ACLs
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Choose an existing IP address or acquire a new IP address. Click the name of the IP address in the list.
- </div><div class="para">
- The IP Addresses page is displayed.
- </div></li><li class="listitem"><div class="para">
- Click the IP address for which you want to create the rule, then click the Configuration tab.
- </div></li><li class="listitem"><div class="para">
- In the Port Forwarding node of the diagram, click View All.
- </div></li><li class="listitem"><div class="para">
- Select the tier to which you want to apply the rule.
- </div></li><li class="listitem"><div class="para">
- Specify the following:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Public Port</strong></span>: The port to which public traffic will be addressed on the IP address you acquired in the previous step.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Private Port</strong></span>: The port on which the instance is listening for forwarded public traffic.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Protocol</strong></span>: The communication protocol in use between the two ports.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- TCP
- </div></li><li class="listitem"><div class="para">
- UDP
- </div></li></ul></div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Add VM</strong></span>: Click Add VM. Select the name of the instance to which this rule applies, and click Apply.
- </div><div class="para">
- You can test the rule by opening an ssh session to the instance.
- </div></li></ul></div></li></ol></div></div><div xml:lang="en-US" class="section" id="remove-tier" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="remove-tier">11.19.12. Removing Tiers</h3></div></div></div><div class="para">
- You can remove a tier from a VPC. A removed tier cannot be revoked. When a tier is removed, only the resources of the tier are expunged. All the network rules (port forwarding, load balancing and staticNAT) and the IP addresses associated to the tier are removed. The IP address still be belonging to the same VPC.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div><div class="para">
- All the VPC that you have created for the account is listed in the page.
- </div></li><li class="listitem"><div class="para">
- Click the Configure button of the VPC for which you want to set up tiers.
- </div><div class="para">
- The Configure VPC page is displayed. Locate the tier you want to work with.
- </div></li><li class="listitem"><div class="para">
- Click the Remove VPC button:
- </div><div class="mediaobject"><img src="./images/remove-tier.png" alt="remove-tier.png: removing a tier from a vpc." /></div><div class="para">
- Wait for some time for the tier to be removed.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="remove-vpc" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="remove-vpc">11.19.13. Editing, Restarting, and Removing a Virtual Private Cloud</h3></div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- Ensure that all the tiers are removed before you remove a VPC.
- </div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network.
- </div></li><li class="listitem"><div class="para">
- In the Select view, select VPC.
- </div><div class="para">
- All the VPCs that you have created for the account is listed in the page.
- </div></li><li class="listitem"><div class="para">
- Select the VPC you want to work with.
- </div></li><li class="listitem"><div class="para">
- To remove, click the Remove VPC button
- <span class="inlinemediaobject"><img src="./images/remove-vpc.png" alt="remove-vpc.png: button to remove a VPC" /></span>
- </div><div class="para">
- You can edit the name and description of a VPC. To do that, select the VPC, then click the Edit button.
- <span class="inlinemediaobject"><img src="./images/edit-icon.png" alt="edit-icon.png: button to edit a VPC" /></span>
- </div><div class="para">
- To restart a VPC, select the VPC, then click the Restart button.
- <span class="inlinemediaobject"><img src="./images/restart-vpc.png" alt="restart-vpc.png: button to restart a VPC" /></span>
- </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="inter-vlan-routing.html"><strong>Prev</strong>11.18. About Inter-VLAN Routing</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="appe-cloudstack-Revision_History.html"><strong>Next</strong>Appendix A. Revision History</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/configure-xenserver-dom0-memory.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/configure-xenserver-dom0-memory.html b/docs/tmp/en-US/html/configure-xenserver-dom0-memory.html
deleted file mode 100644
index 7e15229..0000000
--- a/docs/tmp/en-US/html/configure-xenserver-dom0-memory.html
+++ /dev/null
@@ -1,5 +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>21.5. Configure XenServer dom0 Memory</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="tuning.html" title="Chapter 21. Tuning" /><link rel="prev" href="set-monitor-total-vm-limits-per-host.html" title="21.4. Set and Monitor Total VM Limits per Host" /><link rel="next" href="troubleshooting.html" title="Chapter 22. Troubleshooting" /></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="set-monitor-total-vm-limits-per-host.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="troubleshooting.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="configure-xenserver-dom0-memory" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="configure-xenserver-dom0-memory">21.5. Configure XenServer dom0 Memory</h2></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">Citrix Knowledgebase Article</a>.The article refers to XenServer 5.6, but the same information applies to XenServer 6
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="set-monitor-total-vm-limits-per-host.html"><strong>Prev</strong>21.4. Set and Monitor Total VM Limits per Host</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="troubleshooting.html"><strong>Next</strong>Chapter 22. Troubleshooting</a></li></ul></body></html>