You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by jz...@apache.org on 2012/11/07 19:01:12 UTC
[30/52] [abbrv] [partial] CLOUDSTACK-444 Fix from Radhika PC against
docs, adds network setup in the install guide.
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-templates.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-templates.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-templates.html
new file mode 100644
index 0000000..6dd7a84
--- /dev/null
+++ b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-templates.html
@@ -0,0 +1,16 @@
+<?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 12. Working with Templates</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-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Apache_CloudStack');
+
+ addID('Apache_CloudStack.4.0.0-incubating');
+
+ addID('Apache_CloudStack.4.0.0-incubating.books');
+ addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
+ </script><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="vlan-provisioning.html" title="11.9. VLAN Provisioning" /><link rel="next" href="create-templates-overview.html" title="12.1. Creating Templates: Overview" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="vlan-provisioning.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href
="create-templates-overview.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="working-with-templates" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 12. Working with Templates</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="create-templates-overview.html">12.1. Creating Templates: Overview</a></span></dt><dt><span class="section"><a href="requirements-templates.html">12.2. Requirements for Templates</a></span></dt><dt><span class="section"><a href="best-practices-templates.html">12.3. Best Practices for Templates</a></span></dt><dt><span class="section"><a href="default-template.html">12.4. The Default Template</a></span></dt><dt><span class="section"><a href="private-public-template.html">12.5. Private and Public Templates</a></span></dt><dt><span class="section"><a href="create-template-from-existing-vm.html">12.6. Creating a Template from an Existing Virtual Machine</a></span></dt><dt><span
class="section"><a href="create-template-from-snapshot.html">12.7. Creating a Template from a Snapshot</a></span></dt><dt><span class="section"><a href="upload-template.html">12.8. Uploading Templates</a></span></dt><dt><span class="section"><a href="export-template.html">12.9. Exporting Templates</a></span></dt><dt><span class="section"><a href="create-windows-template.html">12.10. Creating a Windows Template</a></span></dt><dd><dl><dt><span class="section"><a href="create-windows-template.html#sysprep-windows-server-2008R2">12.10.1. System Preparation for Windows Server 2008 R2</a></span></dt><dt><span class="section"><a href="create-windows-template.html#sysprep-for-windows-server-2003R2">12.10.2. Sysprep for Windows Server 2003 R2</a></span></dt></dl></dd><dt><span class="section"><a href="import-ami.html">12.11. Importing Amazon Machine Images</a></span></dt><dt><span class="section"><a href="convert-hyperv-vm-to-template.html">12.12. Converting a Hyper-V VM to a Template</a></
span></dt><dt><span class="section"><a href="add-password-management-to-templates.html">12.13. Adding Password Management to Your Templates</a></span></dt><dd><dl><dt><span class="section"><a href="add-password-management-to-templates.html#linux-installation">12.13.1. Linux OS Installation</a></span></dt><dt><span class="section"><a href="add-password-management-to-templates.html#windows-installation">12.13.2. Windows OS Installation</a></span></dt></dl></dd><dt><span class="section"><a href="delete-templates.html">12.14. Deleting Templates</a></span></dt></dl></div><div class="para">
+ A template is a reusable configuration for virtual machines. When users launch VMs, they can choose from a list of templates in CloudStack.
+ </div><div class="para">
+ Specifically, a template is a virtual disk image that includes one of a variety of operating systems, optional additional software such as office applications, and settings such as access control to determine who can use the template. Each template is associated with a particular type of hypervisor, which is specified when the template is added to CloudStack.
+ </div><div class="para">
+ CloudStack ships with a default template. In order to present more choices to users, CloudStack administrators and users can create templates and add them to CloudStack.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="vlan-provisioning.html"><strong>Prev</strong>11.9. VLAN Provisioning</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="create-templates-overview.html"><strong>Next</strong>12.1. Creating Templates: Overview</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-usage-data.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-usage-data.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-usage-data.html
new file mode 100644
index 0000000..f034909
--- /dev/null
+++ b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-usage-data.html
@@ -0,0 +1,9 @@
+<?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 5. Working With Usage Data</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="asynchronous-commands.html" title="4.5. Asynchronous Commands" /><link rel="next" href="usage-record-format.html" title="5.1. Usage Record Format" /></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.clou
dstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="asynchronous-commands.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="usage-record-format.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="working-with-usage-data" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Working With Usage Data</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="usage-record-format.html">5.1. Usage Record Format</a></span></dt><dd><dl><dt><span class="section"><a href="usage-record-format.html#virtual-machine-usage-record-format">5.1.1. Virtual Machine Usage Record Format</a></span></dt><dt><span class="section"><a href="usage-record-format.html#network-usage-record-format">5.1.2. Network Usage Record Format</a></span></dt><dt><span class="section"><a href="usage-record-format.html#ipadd
ress-usage-record-format">5.1.3. IP Address Usage Record Format</a></span></dt><dt><span class="section"><a href="usage-record-format.html#disk-volume-usage-record-format">5.1.4. Disk Volume Usage Record Format</a></span></dt><dt><span class="section"><a href="usage-record-format.html#template-iso-snapshot-usage-record-format">5.1.5. Template, ISO, and Snapshot Usage Record Format</a></span></dt><dt><span class="section"><a href="usage-record-format.html#loadbalancer-policy-port-forwarding-rule-usage-record-format">5.1.6. Load Balancer Policy or Port Forwarding Rule Usage Record Format</a></span></dt><dt><span class="section"><a href="usage-record-format.html#network-offering-usage-record-format">5.1.7. Network Offering Usage Record Format</a></span></dt><dt><span class="section"><a href="usage-record-format.html#VPN-user-usage-record-format">5.1.8. VPN User Usage Record Format</a></span></dt></dl></dd><dt><span class="section"><a href="usage-types.html">5.2. Usage Types</a></span><
/dt><dt><span class="section"><a href="example-response-from-listUsageRecords.html">5.3. Example response from listUsageRecords</a></span></dt><dt><span class="section"><a href="dates-in-usage-record.html">5.4. Dates in the Usage Record</a></span></dt></dl></div><div class="para">
+ The Usage Server provides aggregated usage records which you can use to create billing integration for the CloudStack platform. The Usage Server works by taking data from the events log and creating summary usage records that you can access using the listUsageRecords API call.
+ </div><div class="para">
+ The usage records show the amount of resources, such as VM run time or template storage space, consumed by guest instances. In the special case of bare metal instances, no template storage resources are consumed, but records showing zero usage are still included in the Usage Server's output.
+ </div><div class="para">
+ The Usage Server runs at least once per day. It can be configured to run multiple times per day. Its behavior is controlled by configuration settings as described in the CloudStack Administration Guide.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="asynchronous-commands.html"><strong>Prev</strong>4.5. Asynchronous Commands</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="usage-record-format.html"><strong>Next</strong>5.1. Usage Record Format</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-volumes.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-volumes.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-volumes.html
new file mode 100644
index 0000000..3d956d6
--- /dev/null
+++ b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/working-with-volumes.html
@@ -0,0 +1,16 @@
+<?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>13.4. Using Swift for Secondary Storage</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-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Apache_CloudStack');
+
+ addID('Apache_CloudStack.4.0.0-incubating');
+
+ addID('Apache_CloudStack.4.0.0-incubating.books');
+ addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
+ </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="storage.html" title="Chapter 13. Working With Storage" /><link rel="prev" href="secondary-storage.html" title="13.3. Secondary Storage" /><link rel="next" href="working-with-snapshots.html" title="13.5. Working with Snapshots" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="secondary-storage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="wor
king-with-snapshots.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="working-with-volumes" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="working-with-volumes">13.4. Using Swift for Secondary Storage</h2></div></div></div><div class="para">
+ A volume provides storage to a guest VM. The volume can provide for a root disk or an additional data disk. CloudStack supports additional volumes for guest VMs.
+ </div><div class="para">
+ Volumes are created for a specific hypervisor type. A volume that has been attached to guest using one hypervisor type (e.g, XenServer) may not be attached to a guest that is using another hypervisor type (e.g. vSphere, KVM). This is because the different hypervisors use different disk image formats.
+ </div><div class="para">
+ CloudStack defines a volume as a unit of storage available to a guest VM. Volumes are either root disks or data disks. The root disk has "/" in the file system and is usually the boot device. Data disks provide for additional storage (e.g. As "/opt" or "D:"). Every guest VM has a root disk, and VMs can also optionally have a data disk. End users can mount multiple data disks to guest VMs. Users choose data disks from the disk offerings created by administrators. The user can create a template from a volume as well; this is the standard procedure for private template creation. Volumes are hypervisor-specific: a volume from one hypervisor type may not be used on a guest of another hypervisor type.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="secondary-storage.html"><strong>Prev</strong>13.3. Secondary Storage</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="working-with-snapshots.html"><strong>Next</strong>13.5. Working with Snapshots</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/zone-add.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/zone-add.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/zone-add.html
new file mode 100644
index 0000000..48f9255
--- /dev/null
+++ b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/zone-add.html
@@ -0,0 +1,386 @@
+<?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.2. Adding a Zone</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-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Apache_CloudStack');
+
+ addID('Apache_CloudStack.4.0.0-incubating');
+
+ addID('Apache_CloudStack.4.0.0-incubating.books');
+ addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
+ </script><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="provisioning-steps-overview.html" title="7.1. Overview of Provisioning Steps" /><link rel="next" href="pod-add.html" title="7.3. Adding a Pod" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="provisioning-steps-overview.html"><strong>Prev</strong></a></li>
<li class="next"><a accesskey="n" href="pod-add.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="zone-add" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="zone-add">7.2. Adding a Zone</h2></div></div></div><div class="para">
+ These steps assume you have already logged in to the CloudStack UI. See <a class="xref" href="log-in.html">Section 5.1, “Log In to the UI”</a>.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ (Optional) If you are going to use Swift for cloud-wide secondary storage, you need to add it before you add zones.
+ </div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
+ Log in to the CloudStack UI as administrator.
+ </div></li><li class="listitem"><div class="para">
+ If this is your first time visiting the UI, you will see the guided tour splash screen. Choose “Experienced user.” The Dashboard appears.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation bar, click Global Settings.
+ </div></li><li class="listitem"><div class="para">
+ In the search box, type swift.enable and click the search button.
+ </div></li><li class="listitem"><div class="para">
+ Click the edit button and set swift.enable to true.
+ <span class="inlinemediaobject"><img src="./images/edit-icon.png" alt="edit-icon.png: button to modify data" /></span>
+
+ </div></li><li class="listitem"><div class="para">
+ Restart the Management Server.
+ </div><pre class="programlisting"># service cloud-management restart</pre></li><li class="listitem"><div class="para">
+ Refresh the CloudStack UI browser tab and log back in.
+ </div></li></ol></div></li><li class="listitem"><div class="para">
+ In the left navigation, choose Infrastructure.
+ </div></li><li class="listitem"><div class="para">
+ On Zones, click View More.
+ </div></li><li class="listitem"><div class="para">
+ (Optional) If you are using Swift storage, click Enable Swift. Provide the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>URL.</strong></span> The Swift URL.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Account.</strong></span> The Swift account.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Username.</strong></span> The Swift account’s username.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Key.</strong></span> The Swift key.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Click Add Zone. The zone creation wizard will appear.
+ </div></li><li class="listitem"><div class="para">
+ Choose one of the following network types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Basic.</strong></span> For AWS-style networking. Provides a single network where each VM instance is assigned an IP directly from the network. Guest isolation can be provided through layer-3 means such as security groups (IP address source filtering).
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Advanced.</strong></span> For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks and providing custom network offerings such as firewall, VPN, or load balancer support.
+ </div></li></ul></div><div class="para">
+ For more information about the network types, see Network Setup.
+ </div></li><li class="listitem"><div class="para">
+ The rest of the steps differ depending on whether you chose Basic or Advanced. Continue with the steps that apply to you:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a class="xref" href="zone-add.html#basic-zone-configuration">Section 7.2.1, “Basic Zone Configuration”</a>
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="zone-add.html#advanced-zone-configuration">Section 7.2.2, “Advanced Zone Configuration”</a>
+ </div></li></ul></div></li></ol></div><div xml:lang="en-US" class="section" id="basic-zone-configuration" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="basic-zone-configuration">7.2.1. Basic Zone Configuration</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ After you select Basic in the Add Zone wizard and click Next, you will be asked to enter the following details. Then click Next.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Name.</strong></span> A name for the zone.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>DNS 1 and 2.</strong></span> These are DNS servers for use by guest VMs in the zone. These DNS servers will be accessed via the public network you will add later. The public IP addresses for the zone must have a route to the DNS server named here.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Internal DNS 1 and Internal DNS 2.</strong></span> These are DNS servers for use by system VMs in the zone (these are VMs used by CloudStack itself, such as virtual routers, console proxies, and Secondary Storage VMs.) These DNS servers will be accessed via the management traffic network interface of the System VMs. The private IP address you provide for the pods must have a route to the internal DNS server named here.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Hypervisor.</strong></span> (Introduced in version 3.0.1) Choose the hypervisor for the first cluster in the zone. You can add clusters with different hypervisors later, after you finish adding the zone.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Network Offering.</strong></span> Your choice here determines what network services will be available on the network for guest VMs.
+ </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">
+ Network Offering
+ </div>
+ </th><th align="left">
+ <div class="para">
+ Description
+ </div>
+ </th></tr></thead><tbody><tr><td align="left">
+ <div class="para">
+ DefaultSharedNetworkOfferingWithSGService
+ </div>
+ </td><td align="left">
+ <div class="para">
+ If you want to enable security groups for guest traffic isolation, choose this. (See Using Security Groups to Control Traffic to VMs.)
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ DefaultSharedNetworkOffering
+ </div>
+ </td><td align="left">
+ <div class="para">
+ If you do not need security groups, choose this.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ DefaultSharedNetscalerEIPandELBNetworkOffering
+ </div>
+ </td><td align="left">
+ <div class="para">
+ If you have installed a Citrix NetScaler appliance as part of your zone network, and you will be using its Elastic IP and Elastic Load Balancing features, choose this. With the EIP and ELB features, a basic zone with security groups enabled can offer 1:1 static NAT and load balancing.
+ </div>
+ </td></tr></tbody></table></div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Network Domain.</strong></span> (Optional) If you want to assign a special domain name to the guest VM network, specify the DNS suffix.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Public.</strong></span> A public zone is available to all users. A zone that is not public will be assigned to a particular domain. Only users in that domain will be allowed to create guest VMs in this zone.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Choose which traffic types will be carried by the physical network.
+ </div><div class="para">
+ The traffic types are management, public, guest, and storage traffic. For more information about the types, roll over the icons to display their tool tips, or see Basic Zone Network Traffic Types. This screen starts out with some traffic types already assigned. To add more, drag and drop traffic types onto the network. You can also change the network name if desired.
+ </div></li><li class="listitem"><div class="para">
+ (Introduced in version 3.0.1) Assign a network traffic label to each traffic type on the physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon. A popup dialog appears where you can type the label, then click OK.
+ </div><div class="para">
+ These traffic labels will be defined only for the hypervisor selected for the first cluster. For all other hypervisors, the labels can be configured after the zone is created.
+ </div></li><li class="listitem"><div class="para">
+ Click Next.
+ </div></li><li class="listitem"><div class="para">
+ (NetScaler only) If you chose the network offering for NetScaler, you have an additional screen to fill out. Provide the requested details to set up the NetScaler, then click Next.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>IP address.</strong></span> The NSIP (NetScaler IP) address of the NetScaler device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Username/Password.</strong></span> The authentication credentials to access the device. CloudStack uses these credentials to access the device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Type.</strong></span> NetScaler device type that is being added. It could be NetScaler VPX, NetScaler MPX, or NetScaler SDX. For a comparison of the types, see About Using a NetScaler Load Balancer.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Public interface.</strong></span> Interface of NetScaler that is configured to be part of the public network.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Private interface.</strong></span> Interface of NetScaler that is configured to be part of the private network.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Number of retries.</strong></span> Number of times to attempt a command on the device before considering the operation failed. Default is 2.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Capacity.</strong></span> Number of guest networks/accounts that will share this NetScaler device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Dedicated.</strong></span> When marked as dedicated, this device will be dedicated to a single account. When Dedicated is checked, the value in the Capacity field has no significance – implicitly, its value is 1.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ (NetScaler only) Configure the IP range for public traffic. The IPs in this range will be used for the static NAT capability which you enabled by selecting the network offering for NetScaler with EIP and ELB. Enter the following details, then click Add. If desired, you can repeat this step to add more IP ranges. When done, click Next.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Gateway.</strong></span> The gateway in use for these IP addresses.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Netmask.</strong></span> The netmask associated with this IP range.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>VLAN.</strong></span> The VLAN that will be used for public traffic.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Start IP/End IP.</strong></span> A range of IP addresses that are assumed to be accessible from the Internet and will be allocated for access to guest VMs.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new zone, CloudStack adds the first pod for you. You can always add more pods later. For an overview of what a pod is, see <a class="xref" href="about-pods.html">Section 2.2, “About Pods”</a>.
+ </div><div class="para">
+ To configure the first pod, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Pod Name.</strong></span> A name for the pod.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Reserved system gateway.</strong></span> The gateway for the hosts in that pod.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Reserved system netmask.</strong></span> The network prefix that defines the pod's subnet. Use CIDR notation.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Start/End Reserved System IP.</strong></span> The IP range in the management network that CloudStack uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see System Reserved IP Addresses.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Configure the network for guest traffic. Provide the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Guest gateway.</strong></span> The gateway that the guests should use.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Guest netmask.</strong></span> The netmask in use on the subnet the guests will use.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Guest start IP/End IP.</strong></span> Enter the first and last IP addresses that define a range that CloudStack can assign to guests.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ We strongly recommend the use of multiple NICs. If multiple NICs are used, they may be in a different subnet.
+ </div></li><li class="listitem"><div class="para">
+ If one NIC is used, these IPs should be in the same CIDR as the pod CIDR.
+ </div></li></ul></div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new pod, CloudStack adds the first cluster for you. You can always add more clusters later. For an overview of what a cluster is, see About Clusters.
+ </div><div class="para">
+ To configure the first cluster, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Hypervisor.</strong></span> (Version 3.0.0 only; in 3.0.1, this field is read only) Choose the type of hypervisor software that all hosts in this cluster will run. If you choose VMware, additional fields appear so you can give information about a vSphere cluster. For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Cluster name.</strong></span> Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new cluster, CloudStack adds the first host for you. You can always add more hosts later. For an overview of what a host is, see About Hosts.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When you add a hypervisor host to CloudStack, the host must not have any VMs already running.
+ </div></div></div><div class="para">
+ Before you can configure the host, you need to install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by CloudStack and what additional configuration is required to ensure the host will work with CloudStack. To find these installation details, see:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Citrix XenServer Installation and Configuration
+ </div></li><li class="listitem"><div class="para">
+ VMware vSphere Installation and Configuration
+ </div></li><li class="listitem"><div class="para">
+ KVM vSphere Installation and Configuration
+ </div></li></ul></div><div class="para">
+ To configure the first host, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Host Name.</strong></span> The DNS name or IP address of the host.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Username.</strong></span> The username is root.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Password.</strong></span> This is the password for the user named above (from your XenServer or KVM install).
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Host Tags.</strong></span> (Optional) Any labels that you use to categorize hosts for ease of maintenance. For example, you can set this to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the "high availability" feature enabled. For more information, see HA-Enabled Virtual Machines as well as HA for Hosts.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new cluster, CloudPlatform adds the first primary storage server for you. You can always add more servers later. For an overview of what primary storage is, see About Primary Storage.
+ </div><div class="para">
+ To configure the first primary storage server, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Name.</strong></span> The name of the storage device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Protocol.</strong></span> For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS, SharedMountPoint,CLVM, or RBD. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary depending on what you choose here.
+ </div></li></ul></div></li></ol></div></div><div xml:lang="en-US" class="section" id="advanced-zone-configuration" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="advanced-zone-configuration">7.2.2. Advanced Zone Configuration</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ After you select Advanced in the Add Zone wizard and click Next, you will be asked to enter the following details. Then click Next.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Name.</strong></span> A name for the zone.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>DNS 1 and 2.</strong></span> These are DNS servers for use by guest VMs in the zone. These DNS servers will be accessed via the public network you will add later. The public IP addresses for the zone must have a route to the DNS server named here.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Internal DNS 1 and Internal DNS 2.</strong></span> These are DNS servers for use by system VMs in the zone(these are VMs used by CloudStack itself, such as virtual routers, console proxies,and Secondary Storage VMs.) These DNS servers will be accessed via the management traffic network interface of the System VMs. The private IP address you provide for the pods must have a route to the internal DNS server named here.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Network Domain.</strong></span> (Optional) If you want to assign a special domain name to the guest VM network, specify the DNS suffix.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Guest CIDR.</strong></span> This is the CIDR that describes the IP addresses in use in the guest virtual networks in this zone. For example, 10.1.1.0/24. As a matter of good practice you should set different CIDRs for different zones. This will make it easier to set up VPNs between networks in different zones.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Hypervisor.</strong></span> (Introduced in version 3.0.1) Choose the hypervisor for the first cluster in the zone. You can add clusters with different hypervisors later, after you finish adding the zone.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Public.</strong></span> A public zone is available to all users. A zone that is not public will be assigned to a particular domain. Only users in that domain will be allowed to create guest VMs in this zone.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Choose which traffic types will be carried by the physical network.
+ </div><div class="para">
+ The traffic types are management, public, guest, and storage traffic. For more information about the types, roll over the icons to display their tool tips, or see <a class="xref" href="about-physical-networks.html#advanced-zone-network-traffic-types">Section 2.7.4, “Advanced Zone Network Traffic Types”</a>. This screen starts out with one network already configured. If you have multiple physical networks, you need to add more. Drag and drop traffic types onto a greyed-out network and it will become active. You can move the traffic icons from one network to another; for example, if the default traffic types shown for Network 1 do not match your actual setup, you can move them down. You can also change the network names if desired.
+ </div></li><li class="listitem"><div class="para">
+ (Introduced in version 3.0.1) Assign a network traffic label to each traffic type on each physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon within each physical network. A popup dialog appears where you can type the label, then click OK.
+ </div><div class="para">
+ These traffic labels will be defined only for the hypervisor selected for the first cluster. For all other hypervisors, the labels can be configured after the zone is created.
+ </div></li><li class="listitem"><div class="para">
+ Click Next.
+ </div></li><li class="listitem"><div class="para">
+ Configure the IP range for public Internet traffic. Enter the following details, then click Add. If desired, you can repeat this step to add more public Internet IP ranges. When done, click Next.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Gateway.</strong></span> The gateway in use for these IP addresses.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Netmask.</strong></span> The netmask associated with this IP range.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>VLAN.</strong></span> The VLAN that will be used for public traffic.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Start IP/End IP.</strong></span> A range of IP addresses that are assumed to be accessible from the Internet and will be allocated for access to guest networks.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new zone, CloudStack adds the first pod for you. You can always add more pods later. For an overview of what a pod is, see <a class="xref" href="about-pods.html">Section 2.2, “About Pods”</a>.
+ </div><div class="para">
+ To configure the first pod, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Pod Name.</strong></span> A name for the pod.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Reserved system gateway.</strong></span> The gateway for the hosts in that pod.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Reserved system netmask.</strong></span> The network prefix that defines the pod's subnet. Use CIDR notation.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Start/End Reserved System IP.</strong></span> The IP range in the management network that CloudStack uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see <a class="xref" href="about-physical-networks.html#system-reserved-ip-addresses">Section 2.7.7, “System Reserved IP Addresses”</a>.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Specify a range of VLAN IDs to carry guest traffic for each physical network (see VLAN Allocation Example ), then click Next.
+ </div></li><li class="listitem"><div class="para">
+ In a new pod, CloudStack adds the first cluster for you. You can always add more clusters later. For an overview of what a cluster is, see <a class="xref" href="about-clusters.html">Section 2.3, “About Clusters”</a>.
+ </div><div class="para">
+ To configure the first cluster, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Hypervisor.</strong></span> (Version 3.0.0 only; in 3.0.1, this field is read only) Choose the type of hypervisor software that all hosts in this cluster will run. If you choose VMware, additional fields appear so you can give information about a vSphere cluster. For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere .
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Cluster name.</strong></span> Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new cluster, CloudStack adds the first host for you. You can always add more hosts later. For an overview of what a host is, see <a class="xref" href="about-hosts.html">Section 2.4, “About Hosts”</a>.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When you deploy CloudStack, the hypervisor host must not have any VMs already running.
+ </div></div></div><div class="para">
+ Before you can configure the host, you need to install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by CloudStack and what additional configuration is required to ensure the host will work with CloudStack. To find these installation details, see:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Citrix XenServer Installation for CloudStack
+ </div></li><li class="listitem"><div class="para">
+ VMware vSphere Installation and Configuration
+ </div></li><li class="listitem"><div class="para">
+ KVM Installation and Configuration
+ </div></li></ul></div><div class="para">
+ To configure the first host, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Host Name.</strong></span> The DNS name or IP address of the host.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Username.</strong></span> Usually root.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Password.</strong></span> This is the password for the user named above (from your XenServer or KVM install).
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Host Tags.</strong></span> (Optional) Any labels that you use to categorize hosts for ease of maintenance. For example, you can set to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the "high availability" feature enabled. For more information, see HA-Enabled Virtual Machines as well as HA for Hosts, both in the Administration Guide.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new cluster, CloudStack adds the first primary storage server for you. You can always add more servers later. For an overview of what primary storage is, see <a class="xref" href="about-primary-storage.html">Section 2.5, “About Primary Storage”</a>.
+ </div><div class="para">
+ To configure the first primary storage server, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Name.</strong></span> The name of the storage device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Protocol.</strong></span> For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS, SharedMountPoint, CLVM, and RBD. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary depending on what you choose here.
+ </div><div class="informaltable"><table border="1"><colgroup><col align="left" class="c1" width="50%" /><col align="left" class="c2" width="50%" /></colgroup><tbody><tr><td align="left">
+ <div class="para">
+ NFS
+ </div>
+ </td><td align="left">
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Server.</strong></span> The IP address or DNS name of the storage device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Path.</strong></span> The exported path from the server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Tags (optional).</strong></span> The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.
+ </div></li></ul></div>
+ <div class="para">
+ The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2.
+ </div>
+
+ </td></tr><tr><td align="left">
+ <div class="para">
+ iSCSI
+ </div>
+ </td><td align="left">
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Server.</strong></span> The IP address or DNS name of the storage device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Target IQN.</strong></span> The IQN of the target. For example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Lun.</strong></span> The LUN number. For example, 3.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Tags (optional).</strong></span> The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.
+ </div></li></ul></div>
+ <div class="para">
+ The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2.
+ </div>
+
+ </td></tr><tr><td align="left">
+ <div class="para">
+ preSetup
+ </div>
+ </td><td align="left">
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Server.</strong></span> The IP address or DNS name of the storage device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>SR Name-Label.</strong></span> Enter the name-label of the SR that has been set up outside CloudStack.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Tags (optional).</strong></span> The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.
+ </div></li></ul></div>
+ <div class="para">
+ The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2.
+ </div>
+
+ </td></tr><tr><td align="left">
+ <div class="para">
+ SharedMountPoint
+ </div>
+ </td><td align="left">
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Path.</strong></span> The path on each host that is where this primary storage is mounted. For example, "/mnt/primary".
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Tags (optional).</strong></span> The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.
+ </div></li></ul></div>
+ <div class="para">
+ The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2.
+ </div>
+
+ </td></tr><tr><td align="left">
+ <div class="para">
+ VMFS
+ </div>
+ </td><td align="left">
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Server.</strong></span> The IP address or DNS name of the vCenter server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Path.</strong></span> A combination of the datacenter name and the datastore name. The format is "/" datacenter name "/" datastore name. For example, "/cloud.dc.VM/cluster1datastore".
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Tags (optional).</strong></span> The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.
+ </div></li></ul></div>
+ <div class="para">
+ The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2.
+ </div>
+
+ </td></tr></tbody></table></div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new zone, CloudStack adds the first secondary storage server for you. For an overview of what secondary storage is, see <a class="xref" href="about-secondary-storage.html">Section 2.6, “About Secondary Storage”</a>.
+ </div><div class="para">
+ Before you can fill out this screen, you need to prepare the secondary storage by setting up NFS shares and installing the latest CloudStack System VM template. See Adding Secondary Storage :
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>NFS Server.</strong></span> The IP address of the server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Path.</strong></span> The exported path from the server.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Click Launch.
+ </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="provisioning-steps-overview.html"><strong>Prev</strong>7.1. Overview of Provisioning Steps</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="pod-add.html"><strong>Next</strong>7.3. Adding a Pod</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-API_Developers_Guide-en-US.pdf
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-API_Developers_Guide-en-US.pdf b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-API_Developers_Guide-en-US.pdf
new file mode 100644
index 0000000..0b3e60f
Binary files /dev/null and b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-API_Developers_Guide-en-US.pdf differ
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-Admin_Guide-en-US.pdf
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-Admin_Guide-en-US.pdf b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-Admin_Guide-en-US.pdf
new file mode 100644
index 0000000..2cebce1
Binary files /dev/null and b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-Admin_Guide-en-US.pdf differ
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-Installation_Guide-en-US.pdf
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-Installation_Guide-en-US.pdf b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-Installation_Guide-en-US.pdf
new file mode 100644
index 0000000..a0f762b
Binary files /dev/null and b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-Installation_Guide-en-US.pdf differ
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-release-notes-en-US.pdf
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-release-notes-en-US.pdf b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-release-notes-en-US.pdf
new file mode 100644
index 0000000..87edf84
Binary files /dev/null and b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Admin_Guide/Apache_CloudStack-4.0.0-incubating-release-notes-en-US.pdf differ
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/runbook/tmp/en-US/pdf/Apache_CloudStack-3.0.2-Runbook-en-US.pdf
----------------------------------------------------------------------
diff --git a/docs/runbook/tmp/en-US/pdf/Apache_CloudStack-3.0.2-Runbook-en-US.pdf b/docs/runbook/tmp/en-US/pdf/Apache_CloudStack-3.0.2-Runbook-en-US.pdf
new file mode 100644
index 0000000..d3b6ba0
Binary files /dev/null and b/docs/runbook/tmp/en-US/pdf/Apache_CloudStack-3.0.2-Runbook-en-US.pdf differ
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/runbook/tmp/en-US/xml/Author_Group.xml
----------------------------------------------------------------------
diff --git a/docs/runbook/tmp/en-US/xml/Author_Group.xml b/docs/runbook/tmp/en-US/xml/Author_Group.xml
new file mode 100644
index 0000000..c0e946a
--- /dev/null
+++ b/docs/runbook/tmp/en-US/xml/Author_Group.xml
@@ -0,0 +1,29 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Runbook.ent">
+%BOOK_ENTITIES;
+]>
+<authorgroup lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <author>
+ <firstname>Apache</firstname>
+ <surname>CloudStack</surname>
+
+ </author>
+</authorgroup>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/runbook/tmp/en-US/xml/Book_Info.xml
----------------------------------------------------------------------
diff --git a/docs/runbook/tmp/en-US/xml/Book_Info.xml b/docs/runbook/tmp/en-US/xml/Book_Info.xml
new file mode 100644
index 0000000..4d32f7e
--- /dev/null
+++ b/docs/runbook/tmp/en-US/xml/Book_Info.xml
@@ -0,0 +1,47 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Runbook.ent">
+%BOOK_ENTITIES;
+]>
+<bookinfo id="book-Runbook-Runbook" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Runbook</title>
+ <subtitle>Prescriptive instructions for deploying Apache CloudStack</subtitle>
+ <productname>Apache CloudStack</productname>
+ <productnumber>3.0.2</productnumber>
+ <edition>0</edition>
+ <pubsnumber>0</pubsnumber>
+ <abstract>
+ <para>
+ These runbooks are designed to provide a strict environment to guarantee a higher degree of success in initial deployments of Apache CloudStack. All of the elements of the environment will be provided to you. Apache CloudStack is capable of much more complex configurations, but they are beyond the scope of this document.
+ </para>
+
+ </abstract>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" />
+ </imageobject>
+
+ </inlinemediaobject>
+
+ </corpauthor>
+ <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</bookinfo>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/runbook/tmp/en-US/xml/Chapter.xml
----------------------------------------------------------------------
diff --git a/docs/runbook/tmp/en-US/xml/Chapter.xml b/docs/runbook/tmp/en-US/xml/Chapter.xml
new file mode 100644
index 0000000..d760ed8
--- /dev/null
+++ b/docs/runbook/tmp/en-US/xml/Chapter.xml
@@ -0,0 +1,55 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Runbook.ent">
+%BOOK_ENTITIES;
+]>
+<chapter id="chap-Runbook-Test_Chapter" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Test Chapter</title>
+ <para>
+ This is a test paragraph
+ </para>
+ <section id="sect-Runbook-Test_Chapter-Test_Section_1">
+ <title>Test Section 1</title>
+ <para>
+ This is a test paragraph in a section
+ </para>
+
+ </section>
+
+ <section id="sect-Runbook-Test_Chapter-Test_Section_2">
+ <title>Test Section 2</title>
+ <para>
+ This is a test paragraph in Section 2
+ <orderedlist>
+ <listitem>
+ <para>
+ listitem text
+ </para>
+
+ </listitem>
+
+ </orderedlist>
+
+ </para>
+
+ </section>
+
+
+</chapter>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/runbook/tmp/en-US/xml/Common_Content/Conventions.xml
----------------------------------------------------------------------
diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/Conventions.xml b/docs/runbook/tmp/en-US/xml/Common_Content/Conventions.xml
new file mode 100644
index 0000000..cd7e8d4
--- /dev/null
+++ b/docs/runbook/tmp/en-US/xml/Common_Content/Conventions.xml
@@ -0,0 +1,178 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "../Runbook.ent">
+%BOOK_ENTITIES;
+]>
+<section lang="en-US">
+ <title>Document Conventions</title>
+ <para>
+ This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
+ </para>
+ <para>
+ In PDF and paper editions, this manual uses typefaces drawn from the <ulink url="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</ulink> set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
+ </para>
+ <section>
+ <title>Typographic Conventions</title>
+ <para>
+ Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
+ </para>
+ <para>
+ <literal>Mono-spaced Bold</literal>
+ </para>
+ <para>
+ Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example:
+ </para>
+ <blockquote>
+ <para>
+ To see the contents of the file <filename>my_next_bestselling_novel</filename> in your current working directory, enter the <command>cat my_next_bestselling_novel</command> command at the shell prompt and press <keycap>Enter</keycap> to execute the command.
+ </para>
+
+ </blockquote>
+ <para>
+ The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
+ </para>
+ <para>
+ Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example:
+ </para>
+ <blockquote>
+ <para>
+ Press <keycap>Enter</keycap> to execute the command.
+ </para>
+ <para>
+ Press <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap></keycombo> to switch to the first virtual terminal. Press <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo> to return to your X-Windows session.
+ </para>
+
+ </blockquote>
+ <para>
+ The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously).
+ </para>
+ <para>
+ If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in <literal>mono-spaced bold</literal>. For example:
+ </para>
+ <blockquote>
+ <para>
+ File-related classes include <classname>filesystem</classname> for file systems, <classname>file</classname> for files, and <classname>dir</classname> for directories. Each class has its own associated set of permissions.
+ </para>
+
+ </blockquote>
+ <para>
+ <application>Proportional Bold</application>
+ </para>
+ <para>
+ This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
+ </para>
+ <blockquote>
+ <para>
+ Choose <menuchoice><guimenu>System</guimenu><guisubmenu>Preferences</guisubmenu><guimenuitem>Mouse</guimenuitem></menuchoice> from the main menu bar to launch <application>Mouse Preferences</application>. In the <guilabel>Buttons</guilabel> tab, click the <guilabel>Left-handed mouse</guilabel> check box and click <guibutton>Close</guibutton> to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
+ </para>
+ <para>
+ To insert a special character into a <application>gedit</application> file, choose <menuchoice><guimenu>Applications</guimenu><guisubmenu>Accessories</guisubmenu><guimenuitem>Character Map</guimenuitem></menuchoice> from the main menu bar. Next, choose <menuchoice><guimenu>Search</guimenu><guimenuitem>Find…</guimenuitem></menuchoice> from the <application>Character Map</application> menu bar, type the name of the character in the <guilabel>Search</guilabel> field and click <guibutton>Next</guibutton>. The character you sought will be highlighted in the <guilabel>Character Table</guilabel>. Double-click this highlighted character to place it in the <guilabel>Text to copy</guilabel> field and then click the <guibutton>Copy</guibutton> button. Now switch back to your document and choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Paste</guimenuitem></menuchoice> from the <application>gedit</application> menu bar.
+ </para>
+
+ </blockquote>
+ <para>
+ The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.
+ </para>
+ <para>
+ <command><replaceable>Mono-spaced Bold Italic</replaceable></command> or <application><replaceable>Proportional Bold Italic</replaceable></application>
+ </para>
+ <para>
+ Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
+ </para>
+ <blockquote>
+ <para>
+ To connect to a remote machine using ssh, type <command>ssh <replaceable>username</replaceable>@<replaceable>domain.name</replaceable></command> at a shell prompt. If the remote machine is <filename>example.com</filename> and your username on that machine is john, type <command>ssh john@example.com</command>.
+ </para>
+ <para>
+ The <command>mount -o remount <replaceable>file-system</replaceable></command> command remounts the named file system. For example, to remount the <filename>/home</filename> file system, the command is <command>mount -o remount /home</command>.
+ </para>
+ <para>
+ To see the version of a currently installed package, use the <command>rpm -q <replaceable>package</replaceable></command> command. It will return a result as follows: <command><replaceable>package-version-release</replaceable></command>.
+ </para>
+
+ </blockquote>
+ <para>
+ Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
+ </para>
+ <para>
+ Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
+ </para>
+ <blockquote>
+ <para>
+ Publican is a <firstterm>DocBook</firstterm> publishing system.
+ </para>
+
+ </blockquote>
+
+ </section>
+
+ <section>
+ <title>Pull-quote Conventions</title>
+ <para>
+ Terminal output and source code listings are set off visually from the surrounding text.
+ </para>
+ <para>
+ Output sent to a terminal is set in <computeroutput>mono-spaced roman</computeroutput> and presented thus:
+ </para>
+
+<screen>books Desktop documentation drafts mss photos stuff svn
+books_tests Desktop1 downloads images notes scripts svgs</screen>
+ <para>
+ Source-code listings are also set in <computeroutput>mono-spaced roman</computeroutput> but add syntax highlighting as follows:
+ </para>
+
+<programlisting language="Java">package org.jboss.book.jca.ex1;
+
+import javax.naming.InitialContext;
+
+public class ExClient
+{
+ public static void main(String args[])
+ throws Exception
+ {
+ InitialContext iniCtx = new InitialContext();
+ Object ref = iniCtx.lookup("EchoBean");
+ EchoHome home = (EchoHome) ref;
+ Echo echo = home.create();
+
+ System.out.println("Created Echo");
+
+ System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
+ }
+}</programlisting>
+
+ </section>
+
+ <section>
+ <title>Notes and Warnings</title>
+ <para>
+ Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
+ </para>
+ <note>
+ <title>Note</title>
+ <para>
+ Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
+ </para>
+
+ </note>
+ <important>
+ <title>Important</title>
+ <para>
+ Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
+ </para>
+
+ </important>
+ <warning>
+ <title>Warning</title>
+ <para>
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </para>
+
+ </warning>
+
+ </section>
+
+
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/runbook/tmp/en-US/xml/Common_Content/Feedback.xml
----------------------------------------------------------------------
diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/Feedback.xml b/docs/runbook/tmp/en-US/xml/Common_Content/Feedback.xml
new file mode 100644
index 0000000..0f8803b
--- /dev/null
+++ b/docs/runbook/tmp/en-US/xml/Common_Content/Feedback.xml
@@ -0,0 +1,22 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "../Runbook.ent">
+%BOOK_ENTITIES;
+]>
+<section lang="en-US">
+ <title>We Need Feedback!</title>
+ <indexterm>
+ <primary>feedback1</primary>
+ <secondary>contact information for this brand</secondary>
+
+ </indexterm>
+ <para>
+ If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a bug: <ulink url="http://bugs.cloudstack.org">http://bugs.cloudstack.org</ulink> against the component <application>Doc</application>
+ </para>
+ <para>
+ If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
+ </para>
+
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/runbook/tmp/en-US/xml/Common_Content/Legal_Notice.xml
----------------------------------------------------------------------
diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/Legal_Notice.xml b/docs/runbook/tmp/en-US/xml/Common_Content/Legal_Notice.xml
new file mode 100644
index 0000000..c193284
--- /dev/null
+++ b/docs/runbook/tmp/en-US/xml/Common_Content/Legal_Notice.xml
@@ -0,0 +1,23 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "../Runbook.ent">
+%BOOK_ENTITIES;
+]>
+<legalnotice lang="en-US">
+ <para>
+ Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
+ </para>
+ <para>
+ http://www.apache.org/licenses/LICENSE-2.0
+ </para>
+ <para>
+ Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
+ </para>
+ <para>
+ Apache CloudStack is an effort undergoing incubation at The Apache Software Foundation (ASF).
+ </para>
+ <para>
+ Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
+ </para>
+</legalnotice>
+