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 2012/07/24 23:20:37 UTC
[48/50] [abbrv] adding docs
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/remove-member-from-project.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/remove-member-from-project.xml b/docs/en-US/remove-member-from-project.xml
new file mode 100644
index 0000000..18e2f65
--- /dev/null
+++ b/docs/en-US/remove-member-from-project.xml
@@ -0,0 +1,25 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="remove-member-from-project">
+ <title>Removing a Member From a Project</title>
+ <para>When a member is removed from a project, the member’s resources continue to be owned by the project. The former project member cannot create any new resources within the project or use any of the project’s existing resources.</para>
+ <para>A member of a project can be removed by the project administrator, the domain administrator of the domain the project belongs to or of its parent domain, or the CloudPlatform root administrator.</para>
+ <orderedlist>
+ <listitem><para>Log in to the CloudPlatform UI.</para></listitem>
+ <listitem><para>In the left navigation, click Projects.</para></listitem>
+ <listitem><para>In Select View, choose Projects.</para></listitem>
+ <listitem><para>Click the name of the project.</para></listitem>
+ <listitem><para>Click the Accounts tab.</para></listitem>
+ <listitem><para>Click the name of the member.</para></listitem>
+ <listitem><para>Click the Delete button.<inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./images/delete-button.png" />
+ </imageobject>
+ <textobject><phrase>deletebutton.png: Removes a member</phrase></textobject>
+ </inlinemediaobject></para></listitem>
+ </orderedlist>
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/removed-API-commands.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/removed-API-commands.xml b/docs/en-US/removed-API-commands.xml
new file mode 100644
index 0000000..1c08717
--- /dev/null
+++ b/docs/en-US/removed-API-commands.xml
@@ -0,0 +1,8 @@
+ <section id="removed-API-commands">
+ <title>Removed API commands</title>
+ <itemizedlist>
+ <listitem><para>createConfiguration (Adds configuration value)</para></listitem>
+ <listitem><para>configureSimulator (Configures simulator)</para></listitem>
+ </itemizedlist>
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/removing-vsphere-hosts.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/removing-vsphere-hosts.xml b/docs/en-US/removing-vsphere-hosts.xml
new file mode 100644
index 0000000..9366d56
--- /dev/null
+++ b/docs/en-US/removing-vsphere-hosts.xml
@@ -0,0 +1,9 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="removing-vsphere-hosts">
+ <title>Removing vSphere Hosts</title>
+ <para>To remove this type of host, first place it in maintenance mode, as described in <xref linkend="scheduled-maintenance-maintenance-mode-hosts"/>. Then use CloudPlatform to remove the host. CloudPlatform will not direct commands to a host that has been removed using CloudPlatform. However, the host may still exist in the vCenter cluster.</para>
+ </section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/removing-xenserver-kvm-hosts.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/removing-xenserver-kvm-hosts.xml b/docs/en-US/removing-xenserver-kvm-hosts.xml
new file mode 100644
index 0000000..9d39e89
--- /dev/null
+++ b/docs/en-US/removing-xenserver-kvm-hosts.xml
@@ -0,0 +1,15 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="removing-xenserver-kvm-hosts">
+ <title>Removing XenServer and KVM Hosts</title>
+ <para>A node cannot be removed from a cluster until it has been placed in maintenance mode. This will ensure that all of the VMs on it have been migrated to other Hosts. To remove a Host from the cloud:</para>
+ <orderedlist>
+ <listitem><para>Place the node in maintenance mode.</para><para> See <xref linkend="scheduled-maintenance-maintenance-mode-hosts"/>.</para></listitem>
+ <listitem><para>For KVM, stop the cloud-agent service.</para></listitem>
+ <listitem><para>Use the UI option to remove the node.</para><para>Then you may power down the Host, re-use its IP address, re-install it, etc</para></listitem>
+ </orderedlist>
+
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/requirements-templates.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/requirements-templates.xml b/docs/en-US/requirements-templates.xml
new file mode 100644
index 0000000..5ea0943
--- /dev/null
+++ b/docs/en-US/requirements-templates.xml
@@ -0,0 +1,12 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="requirements-templates">
+ <title>Requirements for Templates</title>
+ <itemizedlist>
+ <listitem><para>For XenServer, install PV drivers / Xen tools on each template that you create. This will enable live migration and clean guest shutdown.</para></listitem>
+ <listitem><para>For vSphere, install VMware Tools on each template that you create. This will enable console view to work properly.</para></listitem>
+</itemizedlist>
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/resizing-volumes.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/resizing-volumes.xml b/docs/en-US/resizing-volumes.xml
new file mode 100644
index 0000000..d3cf314
--- /dev/null
+++ b/docs/en-US/resizing-volumes.xml
@@ -0,0 +1,19 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="resizing-volumes">
+ <title>Resizing Volumes</title>
+ <para>CloudPlatform does not provide the ability to resize root disks or data disks; the disk size is fixed based on the template used to create the VM. However, the tool <ulink url="http://vmtoolkit.com/files/folders/converters/entry87.aspx/"> VHD Resizer</ulink>), while not officially supported by Cloud.com or Citrix, might provide a workaround. To increase disk size with VHD Resizer:</para>
+ <orderedlist>
+ <listitem><para>Get the VHD from the secondary storage.</para></listitem>
+ <listitem><para>Import it into VHD Resizer.</para></listitem>
+ <listitem><para>Resize the VHD.</para></listitem>
+ <listitem><para>Upload the new VHD.</para></listitem>
+ <listitem><para>Create a new VM.</para></listitem>
+ <listitem><para>Take a snapshot, then create a new template from that snapshot.</para>
+ <para>For more information, see <ulink url="http://support.citrix.com/article/CTX118608/"> How to Resize a Provisioning Server 5 Virtual Disk </ulink> at the Citrix Knowledge Center </para></listitem>
+ </orderedlist>
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/response-formats.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/response-formats.xml b/docs/en-US/response-formats.xml
new file mode 100644
index 0000000..171c409
--- /dev/null
+++ b/docs/en-US/response-formats.xml
@@ -0,0 +1,32 @@
+ <section id="response-formats">
+ <title>Response Formats: XML and JSON</title>
+ <para>CloudStack supports two formats as the response to an API call. The default response is XML. If you would like the response to be in JSON, add &response=json to the Command String.</para>
+ <para>Sample XML Response:</para>
+ <programlisting>
+ <listipaddressesresponse>
+ <allocatedipaddress>
+ <ipaddress>192.168.10.141</ipaddress>
+ <allocated>2009-09-18T13:16:10-0700</allocated>
+ <zoneid>4</zoneid>
+ <zonename>WC</zonename>
+ <issourcenat>true</issourcenat>
+ </allocatedipaddress>
+ </listipaddressesresponse>
+ </programlisting>
+ <para>Sample JSON Response:</para>
+ <programlisting>
+ { "listipaddressesresponse" :
+ { "allocatedipaddress" :
+ [
+ {
+ "ipaddress" : "192.168.10.141",
+ "allocated" : "2009-09-18T13:16:10-0700",
+ "zoneid" : "4",
+ "zonename" : "WC",
+ "issourcenat" : "true"
+ }
+ ]
+ }
+ }
+ </programlisting>
+ </section>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/responses.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/responses.xml b/docs/en-US/responses.xml
new file mode 100644
index 0000000..7c70570
--- /dev/null
+++ b/docs/en-US/responses.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="responses">
+ <title>Responses</title>
+ <xi:include href="response-formats.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="max-result-page-returned.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="error-handling.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/roles.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/roles.xml b/docs/en-US/roles.xml
new file mode 100644
index 0000000..8e02727
--- /dev/null
+++ b/docs/en-US/roles.xml
@@ -0,0 +1,16 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="roles">
+ <title>Roles</title>
+ <para>
+ The CloudPlatform API supports three access roles:</para>
+ <orderedlist>
+ <listitem><para>Root Admin. Access to all features of the cloud, including both virtual and physical resource management.</para></listitem>
+ <listitem><para>Domain Admin. Access to only the virtual resources of the clouds that belong to the administrator’s domain.</para></listitem>
+ <listitem><para>User. Access to only the features that allow management of the user’s virtual instances, storage, and network.</para></listitem>
+ </orderedlist>
+</section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/root-admin-ui-overview.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/root-admin-ui-overview.xml b/docs/en-US/root-admin-ui-overview.xml
new file mode 100644
index 0000000..5477266
--- /dev/null
+++ b/docs/en-US/root-admin-ui-overview.xml
@@ -0,0 +1,9 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="root-admin-ui-overview">
+ <title>Root Administrator's UI Overview</title>
+ <para>The &PRODUCT; UI helps the &PRODUCT; administrator provision, view, and manage the cloud infrastructure, domains, user accounts, projects, and configuration settings. The first time you start the UI after a fresh Management Server installation, you can choose to follow a guided tour to provision your cloud infrastructure. On subsequent logins, the dashboard of the logged-in user appears. The various links in this screen and the navigation bar on the left provide access to a variety of administrative functions. The root administrator can also use the UI to perform all the same tasks that are present in the end-user’s UI.</para>
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/runtime-allocation-virtual-network-resources.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/runtime-allocation-virtual-network-resources.xml b/docs/en-US/runtime-allocation-virtual-network-resources.xml
new file mode 100644
index 0000000..2541574
--- /dev/null
+++ b/docs/en-US/runtime-allocation-virtual-network-resources.xml
@@ -0,0 +1,9 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="runtime-allocation-virtual-network-resources">
+ <title>Runtime Allocation of Virtual Network Resources</title>
+ <para>When you define a new virtual network, all your settings for that network are stored in CloudPlatform. The actual network resources are activated only when the first virtual machine starts in the network. When all virtual machines have left the virtual network, the network resources are garbage collected so they can be allocated again. This helps to conserve network resources..</para>
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/runtime-behavior-of-primary-storage.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/runtime-behavior-of-primary-storage.xml b/docs/en-US/runtime-behavior-of-primary-storage.xml
new file mode 100644
index 0000000..a3740db
--- /dev/null
+++ b/docs/en-US/runtime-behavior-of-primary-storage.xml
@@ -0,0 +1,12 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="runtime-behavior-of-primary-storage">
+ <title>Runtime Behavior of Primary Storage</title>
+ <para>Root volumes are created automatically when a virtual machine is created. Root volumes are deleted when the VM is destroyed. Data volumes can be created and dynamically attached to VMs (although, when the Oracle VM hypervisor is used, the VM must be stopped before an additional volume can be attached). Data volumes are not deleted when VMs are destroyed.</para>
+ <para>Administrators should monitor the capacity of primary storage devices and add additional primary storage as needed. See the Advanced Installation Guide.</para>
+ <para>Administrators add primary storage to the system by creating a CloudPlatform storage pool. Each storage pool is associated with a cluster.</para>
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/scheduled-maintenance-maintenance-mode-hosts.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/scheduled-maintenance-maintenance-mode-hosts.xml b/docs/en-US/scheduled-maintenance-maintenance-mode-hosts.xml
new file mode 100644
index 0000000..28769c7
--- /dev/null
+++ b/docs/en-US/scheduled-maintenance-maintenance-mode-hosts.xml
@@ -0,0 +1,9 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="scheduled-maintenance-maintenance-mode-hosts">
+ <title>Scheduled Maintenance and Maintenance Mode for Hosts</title>
+ <para>You can place a host into maintenance mode. When maintenance mode is activated, the host becomes unavailable to receive new guest VMs, and the guest VMs already running on the host are seamlessly migrated to another host not in maintenance mode. This migration uses live migration technology and does not interrupt the execution of the guest.</para>
+ </section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/scratch.txt
----------------------------------------------------------------------
diff --git a/docs/en-US/scratch.txt b/docs/en-US/scratch.txt
new file mode 100644
index 0000000..e69de29
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/search-base.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/search-base.xml b/docs/en-US/search-base.xml
new file mode 100644
index 0000000..3c0d1ef
--- /dev/null
+++ b/docs/en-US/search-base.xml
@@ -0,0 +1,32 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="search-base">
+ <title>Search Base</title>
+ <para>An LDAP query is relative to a given node of the LDAP directory tree, called the search base. The search base is the distinguished name (DN) of a level of the directory tree below which all users can be found. The users can be in the immediate base directory or in some subdirectory. The search base may be equivalent to the organization, group, or domain name. The syntax for writing a DN varies depending on which LDAP server you are using. A full discussion of distinguished names is outside the scope of our documentation. The following table shows some examples of search bases to find users in the testing department..</para>
+
+ <informaltable>
+ <tgroup cols="2" align="left" colsep="1" rowsep="1">
+ <thead>
+ <row>
+ <entry><para>LDAP Server</para></entry>
+ <entry><para>Example Search Base DN</para></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><para>ApacheDS</para></entry>
+ <entry><para>ou=testing,o=project</para></entry>
+ </row>
+ <row>
+ <entry><para>Active Directory</para></entry>
+ <entry><para>OU=testing, DC=company</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+
+
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/search-user-bind-dn.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/search-user-bind-dn.xml b/docs/en-US/search-user-bind-dn.xml
new file mode 100644
index 0000000..a4c9d4b
--- /dev/null
+++ b/docs/en-US/search-user-bind-dn.xml
@@ -0,0 +1,28 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="search-user-bind-dn">
+ <title>Search User Bind DN</title>
+ <para>The bind DN is the user on the external LDAP server permitted to search the LDAP directory within the defined search base. When the DN is returned, the DN and passed password are used to authenticate the CloudPlatform user with an LDAP bind. A full discussion of bind DNs is outside the scope of our documentation. The following table shows some examples of bind DNs.</para>
+ <informaltable>
+ <tgroup cols="2" align="left" colsep="1" rowsep="1">
+ <thead>
+ <row>
+ <entry><para>LDAP Server</para></entry>
+ <entry><para>Example Bind DN</para></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><para>ApacheDS</para></entry>
+ <entry><para>cn=Administrator,dc=testing,ou=project,ou=org</para></entry>
+ </row>
+ <row>
+ <entry><para>Active Directory</para></entry>
+ <entry><para>CN=Administrator, OU=testing, DC=company, DC=com</para></entry></row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/secondary-storage-add.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/secondary-storage-add.xml b/docs/en-US/secondary-storage-add.xml
new file mode 100644
index 0000000..b17b998
--- /dev/null
+++ b/docs/en-US/secondary-storage-add.xml
@@ -0,0 +1,9 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="secondary-storage-add">
+ <title>Adding Secondary Storage</title>
+ <para>TODO</para>
+</section>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/secondary-storage-outage-and-data-loss.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/secondary-storage-outage-and-data-loss.xml b/docs/en-US/secondary-storage-outage-and-data-loss.xml
new file mode 100644
index 0000000..f651310
--- /dev/null
+++ b/docs/en-US/secondary-storage-outage-and-data-loss.xml
@@ -0,0 +1,10 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="secondary-storage-outage-and-data-loss">
+ <title>Secondary Storage Outage and Data Loss</title>
+ <para>For a Zone that has only one secondary storage server, a secondary storage outage will have feature level impact to the system but will not impact running guest VMs. It may become impossible to create a VM with the selected template for a user. A user may also not be able to save snapshots or examine/restore saved snapshots. These features will automatically be available when the secondary storage comes back online.</para>
+ <para>Secondary storage data loss will impact recently added user data including templates, snapshots, and ISO images. Secondary storage should be backed up periodically.Multiple secondary storage servers can be provisioned within each zone to increase the scalability of the system.</para>
+ </section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/secondary-storage-vm.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/secondary-storage-vm.xml b/docs/en-US/secondary-storage-vm.xml
new file mode 100644
index 0000000..40c8a27
--- /dev/null
+++ b/docs/en-US/secondary-storage-vm.xml
@@ -0,0 +1,14 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="secondary-storage-vm">
+ <title>Secondary Storage VM</title>
+ <para>In addition to the hosts, CloudPlatform’s Secondary Storage VM mounts and writes to secondary storage.</para>
+ <para>Submissions to secondary storage go through the Secondary Storage VM. The Secondary Storage VM can retrieve templates and ISO images from URLs using a variety of protocols.</para>
+ <para> The secondary storage VM provides a background task that takes care of a variety of secondary storage activities: downloading a new template to a Zone, copying templates between Zones, and snapshot backups.</para>
+ <para>The administrator can log in to the secondary storage VM if needed. </para>
+
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/secondary-storage.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/secondary-storage.xml b/docs/en-US/secondary-storage.xml
new file mode 100644
index 0000000..4d6191e
--- /dev/null
+++ b/docs/en-US/secondary-storage.xml
@@ -0,0 +1,10 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="secondary-storage">
+ <title>Secondary Storage</title>
+ <para>This section gives concepts and technical details about CloudPlatform secondary storage. For information about how to install and configure secondary storage through the CloudPlatform UI, see the Advanced Installation Guide.</para>
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/security-groups.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/security-groups.xml b/docs/en-US/security-groups.xml
new file mode 100644
index 0000000..3c1ae91
--- /dev/null
+++ b/docs/en-US/security-groups.xml
@@ -0,0 +1,10 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="security-groups">
+ <xi:include href="add-security-group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="enable-security-groups.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="add-ingress-egress-rules.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/send-projects-membership-invitation.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/send-projects-membership-invitation.xml b/docs/en-US/send-projects-membership-invitation.xml
new file mode 100644
index 0000000..67abf33
--- /dev/null
+++ b/docs/en-US/send-projects-membership-invitation.xml
@@ -0,0 +1,24 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="send-projects-membership-invitation">
+ <title>Sending Project Membership Invitations</title>
+ <para>Use these steps to add a new member to a project if the invitations feature is enabled in the cloud as described in <xref linkend="set-up-invitations"/>. If the invitations feature is not turned on, use the procedure in Adding Project Members From the UI.</para>
+ <orderedlist>
+ <listitem><para>Log in to the CloudPlatform UI.</para></listitem>
+ <listitem><para>In the left navigation, click Projects.</para></listitem>
+ <listitem><para>In Select View, choose Projects.</para></listitem>
+ <listitem><para>Click the name of the project you want to work with.</para></listitem>
+ <listitem><para>Click the Invitations tab.</para></listitem>
+ <listitem><para>In Add by, select one of the following:</para>
+ <orderedlist>
+ <listitem><para>Account – The invitation will appear in the user’s Invitations tab in the Project View. See Using the Project View.</para></listitem>
+ <listitem><para>Email – The invitation will be sent to the user’s email address. Each emailed invitation includes a unique code called a token which the recipient will provide back to CloudPlatform when accepting the invitation. Email invitations will work only if the global parameters related to the SMTP server have been set. See <xref linkend="set-up-invitations"/>.</para></listitem>
+ </orderedlist></listitem>
+ <listitem><para>Type the user name or email address of the new member you want to add, and click Invite. Type the CloudPlatform user name if you chose Account in the previous step. If you chose Email, type the email address. You can invite only people who have an account in this cloud within the same domain as the project. However, you can send the invitation to any email address.</para></listitem>
+ <listitem><para>To view and manage the invitations you have sent, return to this tab. When an invitation is accepted, the new member will appear in the project’s Accounts tab.</para></listitem>
+ </orderedlist>
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/service-offerings.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/service-offerings.xml b/docs/en-US/service-offerings.xml
new file mode 100644
index 0000000..8af653b
--- /dev/null
+++ b/docs/en-US/service-offerings.xml
@@ -0,0 +1,12 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="service-offerings">
+ <title>Service Offerings</title>
+ <para><xref linkend="set-up-network-for-users" />vCenter Maintenance Mode</para>
+ <para><xref linkend="about-virtual-networks" />XenServer and Maintenance Mode</para>
+ <para><xref linkend="customizing-dns" />vCenter Maintenance Mode</para>
+ <para><xref linkend="stop-start-management-server" />XenServer and Maintenance Mode</para>
+ </section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/set-database-buffer-pool-size.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/set-database-buffer-pool-size.xml b/docs/en-US/set-database-buffer-pool-size.xml
new file mode 100644
index 0000000..3fc439b
--- /dev/null
+++ b/docs/en-US/set-database-buffer-pool-size.xml
@@ -0,0 +1,17 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="set-database-buffer-pool-size">
+ <title>Set Database Buffer Pool Size</title>
+ <para>It is important to provide enough memory space for the MySQL database to cache data and indexes:</para>
+ <orderedlist>
+ <listitem><para>Edit the Tomcat configuration file:</para><programlisting>/etc/my.cnf</programlisting></listitem>
+ <listitem><para>2. Insert the following line in the [mysqld] section, below the datadir line. Use a value that is appropriate for your situation. We recommend setting the buffer pool at 40% of RAM if MySQL is on the same server as the management server or 70% of RAM if MySQL has a dedicated server. The following example assumes a dedicated server with 1024M of RAM.</para>
+ <programlisting>innodb_buffer_pool_size=700M</programlisting></listitem>
+ <listitem><para>Restart the MySQL service.</para><programlisting># service mysqld restart</programlisting></listitem>
+ </orderedlist>
+ <para>For more information about the buffer pool, see "The InnoDB Buffer Pool" at <ulink url="http://dev.mysql.com/doc/refman/5.5/en/innodb-buffer-pool.html">MySQL Reference Manual</ulink>.</para>
+</section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/set-monitor-total-vm-limits-per-host.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/set-monitor-total-vm-limits-per-host.xml b/docs/en-US/set-monitor-total-vm-limits-per-host.xml
new file mode 100644
index 0000000..806ba33
--- /dev/null
+++ b/docs/en-US/set-monitor-total-vm-limits-per-host.xml
@@ -0,0 +1,10 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="set-monitor-total-vm-limits-per-host">
+ <title>Set and Monitor Total VM Limits per Host</title>
+ <para>The CloudPlatform administrator should monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are automatically redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudPlatform global configuration settings to set this as the default limit. Monitor the VM activity in each cluster at all times. Keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) * (per-host-limit). Once a cluster reaches t
his number of VMs, use the CloudPlatform UI to disable allocation of more VMs to the cluster.</para>
+</section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/set-projects-creator-permissions.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/set-projects-creator-permissions.xml b/docs/en-US/set-projects-creator-permissions.xml
new file mode 100644
index 0000000..bc00802
--- /dev/null
+++ b/docs/en-US/set-projects-creator-permissions.xml
@@ -0,0 +1,30 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="set-projects-creator-permissions">
+ <title>Setting Project Creator Permissions</title>
+ <para>You can configure CloudPlatform to allow any user to create a new project, or you can restrict that ability to just CloudPlatform administrators.</para>
+ <orderedlist>
+ <listitem><para>Log in as administrator to the CloudPlatform UI.</para></listitem>
+ <listitem><para>In the left navigation, click Global Settings.</para></listitem>
+ <listitem><para>In the search box, type allow.user.create.projects.</para></listitem>
+ <listitem><para>Click the edit button to set the parameter. <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./images/edit-icon.png" />
+ </imageobject>
+ <textobject><phrase>editbutton.png: Edits parameters</phrase></textobject>
+ </inlinemediaobject></para><informaltable>
+ <tgroup cols="2" align="left" colsep="1" rowsep="1">
+ <tbody>
+ <row>
+ <entry><para>allow.user.create.projects</para></entry>
+ <entry><para>Set to true to allow end users to create projects. Set to false if you want only the CloudPlatform root administrator and domain administrators to create projects.</para></entry>
+
+ </row>
+ </tbody></tgroup></informaltable></listitem>
+ <listitem><para>Restart the Management Server.</para><programlisting># service cloud-management restart</programlisting></listitem>
+ </orderedlist>
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/set-resource-limits-for-projects.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/set-resource-limits-for-projects.xml b/docs/en-US/set-resource-limits-for-projects.xml
new file mode 100644
index 0000000..f9b57a8
--- /dev/null
+++ b/docs/en-US/set-resource-limits-for-projects.xml
@@ -0,0 +1,10 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="set-resource-limits-for-projects">
+ <title>Setting Resource Limits for Projects</title>
+ <para>The CloudPlatform administrator can set global default limits to control the amount of resources that can be owned by each project in the cloud. This serves to prevent uncontrolled usage of resources such as snapshots, IP addresses, and virtual machine instances. Domain administrators can override these resource limits for individual projects with their domains, as long as the new limits are below the global defaults set by the CloudPlatform root administrator. The root administrator can also set lower resource limits for any project in the cloud</para>
+</section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/set-up-invitations.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/set-up-invitations.xml b/docs/en-US/set-up-invitations.xml
new file mode 100644
index 0000000..bc7b21a
--- /dev/null
+++ b/docs/en-US/set-up-invitations.xml
@@ -0,0 +1,79 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="set-up-invitations">
+ <title>Setting Up Invitations</title>
+ <para>CloudPlatform can be set up either so that project administrators can add people directly to a project, or so that it is necessary to send an invitation which the recipient must accept. The invitation can be sent by email or through the user’s CloudPlatform account. If you want administrators to use invitations to add members to projects, turn on and set up the invitations feature in CloudPlatform..</para>
+ <itemizedlist>
+ <listitem><para>Log in as administrator to the CloudPlatform UI.</para></listitem>
+ <listitem><para>In the left navigation, click Global Settings.</para></listitem>
+ <listitem><para>In the search box, type project and click the search button.</para></listitem>
+ <listitem><para>In the search box, type project and click the search button.<inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./images/search-button.png" />
+ </imageobject>
+ <textobject><phrase>searchbutton.png: Searches projects</phrase></textobject>
+ </inlinemediaobject></para></listitem>
+ <listitem><para>5. In the search results, you will see a few other parameters you need to set to control how invitations behave. The table below shows global configuration parameters related to project invitations. Click the edit button to set each parameter</para>
+ <informaltable>
+ <tgroup cols="2" align="left" colsep="1" rowsep="1">
+ <thead>
+ <row>
+ <entry><para>Configuration Parameters</para></entry>
+ <entry><para>Description</para></entry>
+
+
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><para>project.invite.required</para></entry>
+ <entry><para>Set to true to turn on the invitations feature.</para></entry>
+
+
+ </row>
+ <row>
+ <entry><para>project.email.sender</para></entry>
+ <entry><para>The email address to show in the From field of invitation emails.</para></entry>
+
+ </row>
+ <row>
+ <entry><para>project.invite.timeout</para></entry>
+ <entry><para>Amount of time to allow for a new member to respond to the invitation.</para></entry>
+
+ </row>
+ <row>
+ <entry><para>project.smtp.host</para></entry>
+ <entry><para>Name of the host that acts as an email server to handle invitations.</para></entry>
+
+ </row>
+ <row>
+ <entry><para>project.smtp.password</para></entry>
+ <entry><para>(Optional) Password required by the SMTP server. You must also set project.smtp.username and set project.smtp.useAuth to true.</para></entry>
+
+ </row>
+ <row>
+ <entry><para>project.smtp.port</para></entry>
+ <entry><para>SMTP server’s listening port.</para></entry>
+
+ </row>
+ <row>
+ <entry><para>project.smtp.useAuth</para></entry>
+ <entry><para>Set to true if the SMTP server requires a username and password.</para></entry>
+ </row>
+ <row>
+ <entry><para>project.smtp.username</para></entry>
+ <entry><para>(Optional) User name required by the SMTP server for authentication. You must also set project.smtp.password and set project.smtp.useAuth to true..</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </listitem>
+ <listitem><para>Restart the Management Server</para>
+ <programlisting>service cloud-management restart</programlisting></listitem>
+ </itemizedlist>
+
+</section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/set-up-network-for-users.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/set-up-network-for-users.xml b/docs/en-US/set-up-network-for-users.xml
new file mode 100644
index 0000000..bc8902f
--- /dev/null
+++ b/docs/en-US/set-up-network-for-users.xml
@@ -0,0 +1,17 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="set-up-network-for-users">
+ <title>Setting Up Networking for Users</title>
+ <para>People using cloud infrastructure have a variety of needs and preferences when it comes to the networking services provided by the cloud. As a CloudPlatform administrator, you can do the following things to set up networking for your users:</para>
+ <itemizedlist>
+ <listitem><para>Set up physical networks in zones</para></listitem>
+ <listitem><para>Set up several different providers for the same service on a single physical network (for example, both Cisco and Juniper firewalls)</para></listitem>
+ <listitem><para>Bundle different types of network services into network offerings, so users can choose the desired network services for any given virtual machine </para></listitem>
+ <listitem><para>Add new network offerings as time goes on so end users can upgrade to a better class of service on their network</para></listitem>
+ <listitem><para>Provide more ways for a network to be accessed by a user, such as through a project of which the user is a member </para></listitem>
+ </itemizedlist>
+
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/set-usage-limit.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/set-usage-limit.xml b/docs/en-US/set-usage-limit.xml
new file mode 100644
index 0000000..350d5c4
--- /dev/null
+++ b/docs/en-US/set-usage-limit.xml
@@ -0,0 +1,14 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="set-usage-limit">
+ <title>Setting Usage Limits</title>
+ <para>CloudPlatform provides several administrator control points for capping resource usage by users. Some of these limits are global configuration parameters. Others are applied at the ROOT domain and may be overridden on a per-account basis.</para>
+ <para>Aggregate limits may be set on a per-domain basis. For example, you may limit a domain and all subdomains to the creation of 100 VMs.</para>
+ <para>This section covers the following topics:</para>
+ <para><xref linkend="globally-configured-limit" />Globally Configured Limits</para>
+ <para><xref linkend="default-account-resource-limit" />Default Account Resource Limits</para>
+ <para><xref linkend="per-domain-limits" />Per Domain Limits</para>
+ </section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/shared-networks.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/shared-networks.xml b/docs/en-US/shared-networks.xml
new file mode 100644
index 0000000..24e0252
--- /dev/null
+++ b/docs/en-US/shared-networks.xml
@@ -0,0 +1,18 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="shared-networks">
+ <title>Shared Networks</title>
+ <para>A shared network can be accessed by virtual machines that belong to many different accounts. Network Isolation on shared networks is accomplished using techniques such as security groups (supported only in basic zones in CloudPlatform 3.0.3).</para>
+ <itemizedlist>
+ <listitem><para>Shared Networks are created by the administrator</para></listitem>
+ <listitem><para>Shared Networks can be designated to a certain domain</para></listitem>
+ <listitem><para>Shared Network resources such as VLAN and physical network that it maps to are designated by the administrator</para></listitem>
+ <listitem><para>Shared Networks are isolated by security groups</para></listitem>
+ <listitem><para>Public Network is a shared network that is not shown to the end users</para></listitem>
+ </itemizedlist>
+
+
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/signing-api-requests.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/signing-api-requests.xml b/docs/en-US/signing-api-requests.xml
new file mode 100644
index 0000000..b71cd42
--- /dev/null
+++ b/docs/en-US/signing-api-requests.xml
@@ -0,0 +1,36 @@
+ <section id="signing-api-requests">
+ <title>Signing API Requests</title>
+ <para>Whether you access the CloudStack API with HTTP or HTTPS, it must still be signed so that CloudStack can verify the caller has been authenticated and authorized to execute the command. Make sure that you have both the API Key and Secret Key provided by the CloudStack administrator for your account before proceeding with the signing process.</para>
+ <para>To show how to sign a request, we will re-use the previous example.</para>
+ <programlisting>http://http://localhost:8080/client/api?command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D</programlisting>
+ <para>Breaking this down, we have several distinct parts to this URL.</para>
+ <itemizedlist>
+ <listitem><para>Base URL: This is the base URL to the CloudStack Management Server.</para>
+ <programlisting>http://localhost:8080</programlisting>
+ </listitem>
+ <listitem><para>API Path: This is the path to the API Servlet that processes the incoming requests.</para>
+ <programlisting>/client/api?</programlisting>
+ </listitem>
+ <listitem><para>Command String: This part of the query string comprises of the command, its parameters, and the API Key that identifies the account.</para>
+ <note><para>As with all query string parameters of field-value pairs, the “field” component is case insensitive while all “value” values are case sensitive.</para></note>
+ <programlisting>command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ</programlisting>
+ </listitem>
+ <listitem><para>Signature: This is the hashed signature of the Base URL that is generated using a combination of the user’s Secret Key and the HMAC SHA-1 hashing algorithm.</para>
+ <para>&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D</para>
+ </listitem>
+ </itemizedlist>
+ <para>Every API request has the format Base URL+API Path+Command String+Signature.</para>
+ <para>To generate the signature.</para>
+ <orderedlist>
+ <listitem><para>For each field-value pair (as separated by a ‘&’) in the Command String, URL encode each value so that it can be safely sent via HTTP GET.</para>
+ <note><para>Make sure all spaces are encoded as “%20” rather than “+”.</para></note>
+ </listitem>
+ <listitem><para>Lower case the entire Command String and sort it alphabetically via the field for each field-value pair. The result of this step would look like the following.</para>
+ <programlisting>apikey=mivr6x7u6bn_sdahobpjnejpgest35exq-jb8cg20yi3yaxxcgpyuairmfi_ejtvwz0nukkjbpmy3y2bcikwfq&command=deployvirtualmachine&diskofferingid=1&serviceofferingid=1&templateid=2&zoneid=4</programlisting>
+ </listitem>
+ <listitem><para>Take the sorted Command String and run it through the HMAC SHA-1 hashing algorithm (most programming languages offer a utility method to do this) with the user’s Secret Key. Base64 encode the resulting byte array in UTF-8 so that it can be safely transmitted via HTTP. The final string produced after Base64 encoding should be “Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D”.</para>
+ <para>By reconstructing the final URL in the format Base URL+API Path+Command String+Signature, the final URL should look like:</para>
+ <programlisting>http://localhost:8080/client/api?command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D</programlisting>
+ </listitem>
+ </orderedlist>
+ </section>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/site-to-site-vpn.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/site-to-site-vpn.xml b/docs/en-US/site-to-site-vpn.xml
new file mode 100644
index 0000000..2e29909
--- /dev/null
+++ b/docs/en-US/site-to-site-vpn.xml
@@ -0,0 +1,27 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="site-to-site-vpn">
+ <title>Site-to-Site VPN</title>
+ <para></para>
+ <para>To add a Virtual Private Cloud (VPC):</para>
+ <orderedlist>
+ <listitem><para>Log in to the CloudPlatform UI as an administrator or end user. </para></listitem>
+ <listitem><para>In the left navigation, choose Network</para></listitem>
+ <listitem><para>In the Select view, select site-to-site VPN.</para></listitem>
+ <listitem><para>Click Add site-to-site VPN. Provide the following information:</para>
+ <itemizedlist>
+ <listitem><para><emphasis role="bold">IP Address</emphasis>:.</para></listitem>
+ <listitem><para><emphasis role="bold">Gateway</emphasis>: The IP address of the remote gateway.</para></listitem>
+ <listitem><para><emphasis role="bold">CIDR list</emphasis>: The guest CIDR list of the remote subnets. Enter a CIDR or a comma-separated list of CIDRs. </para></listitem>
+ <listitem><para><emphasis role="bold">IPsec Preshared Key</emphasis>: The preshared key of the remote gateway.</para></listitem>
+ <listitem><para><emphasis role="bold">IKE Policy</emphasis>: Internet Key Exchange (IKE) policy for phase 1. Specify it as a combination of the encryption algorithm(aes,3des,des) and hash algorithm(sha1,md5). For example: aes-sha1, 3des-sha1.</para></listitem>
+ <listitem><para><emphasis role="bold">ESP Policy</emphasis>: Encapsulating Security Payload (ESP) policy for phase 2. Specify it as a combination of the encryption algorithm(aes,3des,des) and hash algorithm(sha1,md5). For example: aes-sha1, 3des-sha1.</para></listitem>
+ <listitem><para><emphasis role="bold">Lifetime (seconds)</emphasis>: Lifetime of SA in seconds. Default is 86400 seconds(1day).</para></listitem>
+ </itemizedlist></listitem>
+ <listitem><para>Click OK.</para></listitem>
+ </orderedlist>
+
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/snapshot-restore.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/snapshot-restore.xml b/docs/en-US/snapshot-restore.xml
new file mode 100644
index 0000000..2a63f1f
--- /dev/null
+++ b/docs/en-US/snapshot-restore.xml
@@ -0,0 +1,9 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="snapshot-restore">
+ <title>Snapshot Restore</title>
+ <para>There are two paths to restoring snapshots. Users can create a volume from the snapshot. The volume can then be mounted to a VM and files recovered as needed. Alternatively, a template may be created from the snapshot of a root disk. The user can then boot a VM from this template to effect recovery of the root disk.</para>
+ </section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/standard-events.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/standard-events.xml b/docs/en-US/standard-events.xml
new file mode 100644
index 0000000..290b8bc
--- /dev/null
+++ b/docs/en-US/standard-events.xml
@@ -0,0 +1,22 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="standard-events">
+ <title>Standard Events</title>
+ <para>The events log records three types of standard events.</para>
+ <itemizedlist>
+ <listitem><para>INFO. This event is generated when an operation has been successfully performed.</para></listitem>
+ <listitem><para>WARN. This event is generated in the following circumstances.</para>
+ <itemizedlist>
+ <listitem><para>When a network is disconnected while monitoring a template download.</para></listitem>
+ <listitem><para>When a template download is abandoned.</para></listitem>
+ <listitem><para>When an issue on the storage server causes the volumes to fail over to the mirror storage server.</para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para>ERROR. This event is generated when an operation has not been successfully performed</para></listitem>
+ </itemizedlist>
+
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/static-nat.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/static-nat.xml b/docs/en-US/static-nat.xml
new file mode 100644
index 0000000..ea7c7d8
--- /dev/null
+++ b/docs/en-US/static-nat.xml
@@ -0,0 +1,9 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="static-nat">
+ <title>Static NAT</title>
+ <para>A static NAT rule maps a public IP address to the private IP address of a VM in order to allow Internet traffic into the VM. The public IP address always remains the same, which is why it is called “static” NAT. This section tells how to enable or disable static NAT for a particular IP address.</para>
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/sticky-session-policies-for-lb-rules.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/sticky-session-policies-for-lb-rules.xml b/docs/en-US/sticky-session-policies-for-lb-rules.xml
new file mode 100644
index 0000000..a8c11c9
--- /dev/null
+++ b/docs/en-US/sticky-session-policies-for-lb-rules.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sticky-session-policies-for-lb-rules">
+ <title>Sticky Session Policies for Load Balancer Rules</title>
+ <para>Sticky sessions are used in Web-based applications to ensure continued availability of information across the multiple requests in a user's session. For example, if a shopper is filling a cart, you need to remember what has been purchased so far. The concept of “stickiness” is also referred to as persistence or maintaining state.</para>
+ <para>Any load balancer rule defined in CloudPlatform can have a stickiness policy. The policy consists of a name, stickiness method, and parameters. The parameters are name-value pairs or flags, which are defined by the load balancer vendor. The stickiness method could be load balancer-generated cookie, application-generated cookie, or source-based. In the source-based method, the source IP address is used to identify the user and locate the user’s stored data. In the other methods, cookies are used. The cookie generated by the load balancer or application is included in request and response URLs to create persistence. The cookie name can be specified by the administrator or automatically generated. A variety of options are provided to control the exact behavior of cookies, such as how they are generated and whether they are cached.</para>
+ <para>For the most up to date list of available stickiness methods, see the CloudPlatform UI or call listNetworks and check the SupportedStickinessMethods capability.</para>
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/stop-restart-management-server.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/stop-restart-management-server.xml b/docs/en-US/stop-restart-management-server.xml
new file mode 100644
index 0000000..26d30ea
--- /dev/null
+++ b/docs/en-US/stop-restart-management-server.xml
@@ -0,0 +1,16 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="stop-restart-management-server">
+ <title>Stopping and Restarting the Management Server</title>
+ <para>The root administrator will need to stop and restart the Management Server from time to time.</para>
+ <para>For example, after changing a global configuration parameter, a restart is required. If you have multiple Management Server nodes, restart all of them to put the new parameter value into effect consistently throughout the cloud..</para>
+ <para>To stop the Management Server, issue the following command at the operating system prompt on the Management Server node:</para>
+ <programlisting># service cloud-management stop</programlisting>
+ <para>To start the Management Server:</para>
+ <programlisting># service cloud-management start</programlisting>
+ <para>To stop the Management Server:</para>
+ <programlisting># service cloud-management stop</programlisting>
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/stopped-vm.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/stopped-vm.xml b/docs/en-US/stopped-vm.xml
new file mode 100644
index 0000000..e6b8400
--- /dev/null
+++ b/docs/en-US/stopped-vm.xml
@@ -0,0 +1,12 @@
+ <section id="stopped-vm">
+ <title>Stopped VM</title>
+ <para>CloudPlatform now supports creating a VM without starting it. You can determine whether the VM needs to be started as part of the VM deployment. A VM can now be deployed in two ways: create and start a VM (the default method); or create a VM and leave it in the stopped state.</para>
+ <para>A new request parameter, startVM, is introduced in the deployVm API to support the stopped VM feature.</para>
+ <para>The possible values are:</para>
+ <itemizedlist>
+ <listitem><para>true - The VM starts as a part of the VM deployment.</para></listitem>
+ <listitem><para>false - The VM is left in the stopped state at the end of the VM deployment.</para></listitem>
+ </itemizedlist>
+ <para>The default value is true.</para>
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/stopping-and-starting-vms.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/stopping-and-starting-vms.xml b/docs/en-US/stopping-and-starting-vms.xml
new file mode 100644
index 0000000..20d0d95
--- /dev/null
+++ b/docs/en-US/stopping-and-starting-vms.xml
@@ -0,0 +1,5 @@
+<section id="stopping-and-starting-vms">
+ <title>Stopping and Starting VMs</title>
+ <para>Any user can access their own virtual machines. The administrator can access all VMs running in the cloud.</para>
+</section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/storage-tags.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/storage-tags.xml b/docs/en-US/storage-tags.xml
new file mode 100644
index 0000000..3297c8d
--- /dev/null
+++ b/docs/en-US/storage-tags.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="storage-tags">
+ <title>Storage Tags</title>
+ <para>Storage may be "tagged". A tag is a text string attribute associated with primary storage, a Disk Offering, or a Service Offering. Tags allow administrators to provide additional information about the storage. For example, that is a "SSD" or it is "slow". Tags are not interpreted by CloudPlatform. They are matched against tags placed on service and disk offerings. CloudPlatform requires all tags on service and disk offerings to exist on the primary storage before it allocates root or data disks on the primary storage. Service and disk offering tags are used to identify the requirements of the storage that those offerings have. For example, the high end service offering may require "fast" for its root disk volume.</para>
+ <para>The interaction between tags, allocation, and volume copying across clusters and pods can be complex. To simplify the situation, use the same set of tags on the primary storage for all clusters in a pod. Even if different devices are used to present those tags, the set of exposed tags can be the same.</para>
+
+ </section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/storage.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/storage.xml b/docs/en-US/storage.xml
new file mode 100644
index 0000000..45fa648
--- /dev/null
+++ b/docs/en-US/storage.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="storage">
+ <title>Deleting VMs</title>
+ <para>CloudPlatform defines two types of storage: primary and secondary. Primary storage can be accessed by either iSCSI or NFS. Additionally, direct attached storage may be used for primary storage. Secondary storage is always accessed using NFS.</para>
+ <para>There is no ephemeral storage in CloudPlatform. All volumes on all nodes are persistent</para>
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/suspend-project.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/suspend-project.xml b/docs/en-US/suspend-project.xml
new file mode 100644
index 0000000..9ad1e62
--- /dev/null
+++ b/docs/en-US/suspend-project.xml
@@ -0,0 +1,30 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="suspend-project">
+ <title>Suspending or Deleting a Project</title>
+ <para>When a project is suspended, it retains the resources it owns, but they can no longer be used. No new resources or members can be added to a suspended project.</para>
+ <para>When a project is deleted, its resources are destroyed, and member accounts are removed from the project. The project’s status is shown as Disabled pending final deletion.</para>
+ <para>A project can be suspended or deleted by the project administrator, the domain administrator of the domain the project belongs to or of its parent domain, or the CloudPlatform root administrator.</para>
+ <orderedlist>
+ <listitem><para>Log in to the CloudPlatform UI.</para></listitem>
+ <listitem><para>In the left navigation, click Projects.</para></listitem>
+ <listitem><para>In Select View, choose Projects.</para></listitem>
+ <listitem><para>Click the name of the project.</para></listitem>
+ <listitem><para>Click one of the buttons:<inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./images/delete-button.png" />
+ </imageobject>
+ <textobject><phrase>deletebutton.png: Removes a member</phrase></textobject>
+ </inlinemediaobject></para>
+ <para><inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./images/suspend-icon.png" />
+ </imageobject>
+ <textobject><phrase>deletebutton.png: Removes a member</phrase></textobject>
+ </inlinemediaobject></para></listitem>
+ </orderedlist>
+ </section>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/sys-reliability-and-ha.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/sys-reliability-and-ha.xml b/docs/en-US/sys-reliability-and-ha.xml
new file mode 100644
index 0000000..d8c4bbd
--- /dev/null
+++ b/docs/en-US/sys-reliability-and-ha.xml
@@ -0,0 +1,12 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sys-reliability-and-ha">
+ <title>System Reliability and High Availability</title>
+ <para><xref linkend="ha-management-server" />vCenter Maintenance Mode</para>
+ <para><xref linkend="ha-enabled-vm" />XenServer and Maintenance Mode</para>
+ <para><xref linkend="ha-for-hosts" />vCenter Maintenance Mode</para>
+ <para><xref linkend="dedicated-ha-hosts" />XenServer and Maintenance Mode</para>
+ </section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/sysprep-for-windows-server-2003R2.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/sysprep-for-windows-server-2003R2.xml b/docs/en-US/sysprep-for-windows-server-2003R2.xml
new file mode 100644
index 0000000..bdde68e
--- /dev/null
+++ b/docs/en-US/sysprep-for-windows-server-2003R2.xml
@@ -0,0 +1,39 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sysprep-for-windows-server-2003R2">
+ <title>Sysprep for Windows Server 2003 R2</title>
+ <para>Earlier versions of Windows have a different sysprep tool. Follow these steps for Windows Server 2003 R2.</para>
+ <orderedlist>
+ <listitem><para>Extract the content of \support\tools\deploy.cab on the Windows installation CD into a directory called c:\sysprep on the Windows 2003 R2 VM.</para></listitem>
+ <listitem><para>Run c:\sysprep\setupmgr.exe to create the sysprep.inf file.</para>
+ <orderedlist numeration="loweralpha">
+ <listitem><para>Select Create New to create a new Answer File.</para></listitem>
+ <listitem><para>Enter “Sysprep setup” for the Type of Setup.</para></listitem>
+ <listitem><para>Select the appropriate OS version and edition.</para></listitem>
+ <listitem><para>On the License Agreement screen, select “Yes fully automate the installation”.</para></listitem>
+ <listitem><para>Provide your name and organization.</para></listitem>
+ <listitem><para>Leave display settings at default.</para></listitem>
+ <listitem><para>Set the appropriate time zone.</para></listitem>
+ <listitem><para>Provide your product key.</para></listitem>
+ <listitem><para>Select an appropriate license mode for your deployment</para></listitem>
+ <listitem><para>Select “Automatically generate computer name”.</para></listitem>
+ <listitem><para>Type a default administrator password. If you enable the password reset feature, the users will not actually use this password. This password will be reset by the instance manager after the guest boots up.</para></listitem>
+ <listitem><para>Leave Network Components at “Typical Settings”.</para></listitem>
+ <listitem><para>Select the “WORKGROUP” option.</para></listitem>
+ <listitem><para>Leave Telephony options at default.</para></listitem>
+ <listitem><para>Select appropriate Regional Settings.</para></listitem>
+ <listitem><para>Select appropriate language settings.</para></listitem>
+ <listitem><para>Do not install printers.</para></listitem>
+ <listitem><para>Do not specify “Run Once commands”.</para></listitem>
+ <listitem><para>You need not specify an identification string.</para></listitem>
+ <listitem><para>Save the Answer File as c:\sysprep\sysprep.inf.</para></listitem>
+
+ </orderedlist>
+ </listitem>
+ <listitem><para>Run the following command to sysprep the image:</para><programlisting>c:\sysprep\sysprep.exe -reseal -mini -activated</programlisting>
+ <para>After this step the machine will automatically shut down</para></listitem>
+ </orderedlist>
+ </section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/sysprep-windows-server-2008R2.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/sysprep-windows-server-2008R2.xml b/docs/en-US/sysprep-windows-server-2008R2.xml
new file mode 100644
index 0000000..37a2e1c
--- /dev/null
+++ b/docs/en-US/sysprep-windows-server-2008R2.xml
@@ -0,0 +1,51 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sysprep-windows-server-2008R2">
+ <title>System Preparation for Windows Server 2008 R2</title>
+ <para>For Windows 2008 R2, you run Windows System Image Manager to create a custom sysprep response XML file. Windows System Image Manager is installed as part of the Windows Automated Installation Kit (AIK). Windows AIK can be downloaded from the Microsoft Download Center at the following location:</para>
+ <para><ulink url="http://www.microsoft.com/en-us/download/details.aspx?id=9085"></ulink>Microsoft Download Center.</para>
+ <para>Use the following steps to run sysprep for Windows 2008 R2:</para><note><para>The steps outlined here are derived from the excellent guide by Charity Shelbourne, originally published at <ulink url="http://blogs.technet.com/askcore/archive/2008/10/31/automating-the-oobe-process-during-windows-server-2008-sysprep-mini-setup.aspx"></ulink>Windows Server 2008 Sysprep Mini-Setup</para></note>
+ <orderedlist>
+ <listitem><para>Download and install the Windows AIK</para><note><para>Windows AIK should not be installed on the Windows 2008 R2 VM you just created. Windows AIK should not be part of the template you create. It is only used to create the sysprep answer file.</para></note></listitem>
+ <listitem><para>Copy the install.wim file in the \sources directory of the Windows 2008 R2 installation DVD to the hard disk. This is a very large file and may take a long time to copy. Windows AIK requires the WIM file to be writable.</para></listitem>
+ <listitem><para>Start the Windows System Image Manager, which is part of the Windows AIK.</para></listitem>
+ <listitem><para>In the Windows Image pane, right click “Select a Windows image or catalog file” to load the install.wim file you just copied.</para></listitem>
+ <listitem><para>Select the Windows 2008 R2 Edition</para><para>You may be prompted with a warning that the catalog file cannot be opened. Click Yes to create a new catalog file.</para></listitem>
+ <listitem><para>In the Answer File pane, right click to create a new answer file.</para></listitem>
+ <listitem><para>Generate the answer file from the Windows System Image Manager using the following steps:</para>
+ <orderedlist numeration="loweralpha">
+ <listitem><para>The first page you need to automate is the Language and Country or Region Selection page. To automate this, expand Components in your Windows Image pane, right-click and add the Microsoft-Windows-International-Core setting to Pass 7 oobeSystem. In your Answer File pane, configure the InputLocale, SystemLocale, UILanguage, and UserLocale with the appropriate settings for your language and country or region. Should you have a question about any of these settings, you can right-click on the specific setting and select Help. This will open the appropriate CHM help file with more information, including examples on the setting you are attempting to configure.</para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./images/sysmanager.png" />
+ </imageobject>
+ <textobject><phrase>sysmanager.png: System Image Manager</phrase></textobject>
+ </mediaobject></listitem>
+ <listitem><para>You need to automate the Software License Terms Selection page, otherwise known as the End-User License Agreement (EULA). To do this, expand the Microsoft-Windows-Shell-Setup component. High-light the OOBE setting, and add the setting to the Pass 7 oobeSystem. In Settings, set HideEULAPage true.</para> <mediaobject>
+ <imageobject>
+ <imagedata fileref="./images/software-license.png" />
+ </imageobject>
+ <textobject><phrase>software-license.png: Depicts hiding the EULA page.</phrase></textobject>
+ </mediaobject></listitem>
+ <listitem><para>Make sure the license key is properly set. If you use MAK key, you can just enter the MAK key on the Windows 2008 R2 VM. You need not input the MAK into the Windows System Image Manager. If you use KMS host for activation you need not enter the Product Key. Details of Windows Volume Activation can be found at <ulink url="http://technet.microsoft.com/en-us/library/bb892849.aspx"></ulink></para></listitem>
+ <listitem><para>You need to automate is the Change Administrator Password page. Expand the Microsoft-Windows-Shell-Setup component (if it is not still expanded), expand UserAccounts, right-click on AdministratorPassword, and add the setting to the Pass 7 oobeSystem configuration pass of your answer file. Under Settings, specify a password next to Value.</para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./images/change-admin-password.png" />
+ </imageobject>
+ <textobject><phrase>change-admin-password.png: Depicts changing the administrator password</phrase></textobject>
+ </mediaobject><para>You may read the AIK documentation and set many more options that suit your deployment. The steps above are the minimum needed to make Windows unattended setup work.</para></listitem></orderedlist></listitem>
+ <listitem><para>Save the answer file as unattend.xml. You can ignore the warning messages that appear in the validation window.</para></listitem>
+ <listitem><para>Copy the unattend.xml file into the c:\windows\system32\sysprep directory of the Windows 2008 R2 Virtual Machine</para></listitem>
+ <listitem><para>Once you place the unattend.xml file in c:\windows\system32\sysprep directory, you run the sysprep tool as follows:</para>
+ <programlisting>cd c:\Windows\System32\sysprep
+sysprep.exe /oobe /generalize /shutdown
+</programlisting><para>The Windows 2008 R2 VM will automatically shut down after sysprep is complete.</para></listitem>
+
+
+ </orderedlist>
+
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/system-service-offerings.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/system-service-offerings.xml b/docs/en-US/system-service-offerings.xml
new file mode 100644
index 0000000..92aff73
--- /dev/null
+++ b/docs/en-US/system-service-offerings.xml
@@ -0,0 +1,10 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="system-service-offerings">
+ <title>System Service Offerings</title>
+ <para>System service offerings provide a choice of CPU speed, number of CPUs, tags, and RAM size, just as other service offerings do. But rather than being used for virtual machine instances and exposed to users, system service offerings are used to change the default properties of virtual routers, console proxies, and other system VMs. System service offerings are visible only to the CloudPlatform root administrator. CloudPlatform provides default system service offerings. The CloudPlatform root administrator can create additional custom system service offerings.</para>
+ <para>When CloudPlatform creates a virtual router for a guest network, it uses default settings which are defined in the system service offering associated with the network offering. You can upgrade the capabilities of the virtual router by applying a new network offering that contains a different system service offering. All virtual routers in that network will begin using the settings from the new service offering.</para>
+ </section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/system-vm-template.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/system-vm-template.xml b/docs/en-US/system-vm-template.xml
new file mode 100644
index 0000000..e873ee1
--- /dev/null
+++ b/docs/en-US/system-vm-template.xml
@@ -0,0 +1,19 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="system-vm-template">
+ <title>The System VM Template</title>
+ <para>The System VMs come from a single template. The System VM has the following characteristics:</para>
+ <itemizedlist>
+ <listitem><para>Debian 6.0 ("Squeeze"), 2.6.32 kernel with the latest security patches from the Debian security APT repository</para></listitem>
+ <listitem><para>Has a minimal set of packages installed thereby reducing the attack surface</para></listitem>
+ <listitem><para>32-bit for enhanced performance on Xen/VMWare</para></listitem>
+ <listitem><para>pvops kernel with Xen PV drivers, KVM virtio drivers, and VMware tools for optimum performance on all hypervisors</para></listitem>
+ <listitem><para>Xen tools inclusion allows performance monitoring</para></listitem>
+ <listitem><para>Latest versions of HAProxy, iptables, IPsec, and Apache from debian repository ensures improved security and speed</para></listitem>
+ <listitem><para>Latest version of JRE from Sun/Oracle ensures improved security and speed</para></listitem>
+ </itemizedlist>
+
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/template-iso-snapshot-usage-record-format.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/template-iso-snapshot-usage-record-format.xml b/docs/en-US/template-iso-snapshot-usage-record-format.xml
new file mode 100644
index 0000000..d3ae8e1
--- /dev/null
+++ b/docs/en-US/template-iso-snapshot-usage-record-format.xml
@@ -0,0 +1,18 @@
+<section id="template-iso-snapshot-usage-record-format">
+ <title>Template, ISO, and Snapshot Usage Record Format</title>
+ <itemizedlist>
+ <listitem><para>account – name of the account</para></listitem>
+ <listitem><para>accountid – ID of the account</para></listitem>
+ <listitem><para>domainid – ID of the domain in which this account resides</para></listitem>
+ <listitem><para>zoneid – Zone where the usage occurred</para></listitem>
+ <listitem><para>description – A string describing what the usage record is tracking</para></listitem>
+ <listitem><para>usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for hours)</para></listitem>
+ <listitem><para>usagetype – A number representing the usage type (see Usage Types)</para></listitem>
+ <listitem><para>rawusage – A number representing the actual usage in hours</para></listitem>
+ <listitem><para>usageid – The ID of the the template, ISO, or snapshot</para></listitem>
+ <listitem><para>offeringid – The ID of the disk offering</para></listitem>
+ <listitem><para>templateid – – Included only for templates (usage type 7). Source template ID.</para></listitem>
+ <listitem><para>size – Size of the template, ISO, or snapshot</para></listitem>
+ <listitem><para>startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record</para></listitem>
+ </itemizedlist>
+</section>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/templates.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/templates.xml b/docs/en-US/templates.xml
new file mode 100644
index 0000000..a249ded
--- /dev/null
+++ b/docs/en-US/templates.xml
@@ -0,0 +1,10 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
+%BOOK_ENTITIES;
+]>
+<section id="templates">
+ <title>Templates</title>
+ <xi:include href="working-with-iso.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="working-with-templates.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ </section>