incubator-cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From alena1...@apache.org
Subject [9/22] adding docs
Date Mon, 16 Jul 2012 22:44:06 GMT
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloud-infrastructure-overview.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloud-infrastructure-overview.xml b/docs/en-US/cloud-infrastructure-overview.xml
new file mode 100644
index 0000000..9c10acf
--- /dev/null
+++ b/docs/en-US/cloud-infrastructure-overview.xml
@@ -0,0 +1,28 @@
+<?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="cloud-infrastructure-overview">
+	<title>Cloud Infrastructure Overview</title>
+	<para>
+		The Management Server manages one or more zones (typically, datacenters) containing host computers where guest virtual machines will run. The cloud infrastructure is organized as follows:
+	</para>
+	<itemizedlist>
+		<listitem><para>Zone: Typically, a zone is equivalent to a single datacenter. A zone consists of one or more pods and secondary storage.</para></listitem>
+		<listitem><para>Pod: A pod is usually one rack of hardware that includes a layer-2 switch and one or more clusters.</para></listitem>
+		<listitem><para>Cluster: A cluster consists of one or more hosts and primary storage.</para></listitem>
+		<listitem><para>Host: A single compute node within a cluster. The hosts are where the actual cloud services run in the form of guest virtual machines.</para></listitem>
+		<listitem><para>Primary storage is associated with a cluster, and it stores the disk volumes for all the VMs running on hosts in that cluster.</para></listitem>
+		<listitem><para>Secondary storage is associated with a zone, and it stores templates, ISO images, and disk volume snapshots.</para></listitem>
+	</itemizedlist>
+	<mediaobject>
+		<imageobject>
+			<imagedata fileref="./images/infrastructure_overview.png" />
+		</imageobject>
+		<textobject><phrase>infrastructure_overview.png: Nested organization of a zone</phrase></textobject>
+	</mediaobject>
+	<para><emphasis role="bold">More Information</emphasis></para>
+	<para>For more information, see <xref linkend="cloud-infrastructure-concepts" />.</para>
+</section>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloud_infrastructure_overview.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloud_infrastructure_overview.xml b/docs/en-US/cloud_infrastructure_overview.xml
new file mode 100644
index 0000000..89b8f63
--- /dev/null
+++ b/docs/en-US/cloud_infrastructure_overview.xml
@@ -0,0 +1,21 @@
+	<section id="cloud_infrastructure_overview">
+		<title>Cloud Infrastructure Overview</title>
+		<para>
+			The Management Server manages one or more zones (typically, datacenters) containing host computers where guest virtual machines will run. The cloud infrastructure is organized as follows:
+		</para>
+		<itemizedlist>
+			<listitem><para>Zone: Typically, a zone is equivalent to a single datacenter. A zone consists of one or more pods and secondary storage. See About Zones.</para></listitem>
+			<listitem><para>Pod: A pod is usually one rack of hardware that includes a layer-2 switch and one or more clusters. See About Pods.</para></listitem>
+			<listitem><para>Cluster: A cluster consists of one or more hosts and primary storage. See About Clusters.</para></listitem>
+			<listitem><para>Host: A single compute node within a cluster. The hosts are where the actual cloud services run in the form of guest virtual machines. See About Hosts.</para></listitem>
+			<listitem><para>Primary storage is associated with a cluster, and it stores the disk volumes for all the VMs running on hosts in that cluster. See About Primary Storage</para></listitem>
+			<listitem><para>Secondary storage is associated with a zone, and it stores templates, ISO images, and disk volume snapshots. See About Secondary Storage.</para></listitem>
+		</itemizedlist>
+		<mediaobject>
+			<imageobject>
+				<imagedata fileref="./images/infrastructure_overview.png" />
+			</imageobject>
+			<textobject><phrase>infrastructure_overview.png: Nested organization of a zone</phrase></textobject>
+		</mediaobject>
+	</section>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloudplatform-api.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloudplatform-api.xml b/docs/en-US/cloudplatform-api.xml
new file mode 100644
index 0000000..ac96b0c
--- /dev/null
+++ b/docs/en-US/cloudplatform-api.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="cloudplatform-api">
+    <title>CloudPlatform API</title>
+    <para>The CloudPlatform API is a low level API that has been used to implement the CloudPlatform web UIs. It is also a good basis for implementing other popular APIs such as EC2/S3 and emerging DMTF standards.</para>
+    <para>Many CloudPlatform API calls are asynchronous. These will return a Job ID immediately when called. This Job ID can be used to query the status of the job later. Also, status calls on impacted resources will provide some indication of their state.</para>
+    <para>The API has a REST-like query basis and returns results in XML or JSON.</para>
+    <para>See <ulink url="http://support.citrix.com/product/cs">the Developer’s Guide</ulink> and <ulink url="http://docs.cloudstack.org/CloudStack_Documentation/API_Reference%3A_CloudStack">the API Reference</ulink>.</para>
+   </section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloudstack-admin.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloudstack-admin.xml b/docs/en-US/cloudstack-admin.xml
new file mode 100644
index 0000000..8b1d0b2
--- /dev/null
+++ b/docs/en-US/cloudstack-admin.xml
@@ -0,0 +1,12 @@
+<?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;
+]>
+<book>
+	<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="admin-guide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloudstack.ent
----------------------------------------------------------------------
diff --git a/docs/en-US/cloudstack.ent b/docs/en-US/cloudstack.ent
new file mode 100644
index 0000000..4607134
--- /dev/null
+++ b/docs/en-US/cloudstack.ent
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "CloudStack">
+<!ENTITY BOOKID "Technical Documentation">
+<!ENTITY YEAR "2012">
+<!ENTITY HOLDER "CC-BY-SA">

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloudstack.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloudstack.xml b/docs/en-US/cloudstack.xml
new file mode 100644
index 0000000..143e0a6
--- /dev/null
+++ b/docs/en-US/cloudstack.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;
+]>
+<book>
+	<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="ui.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="provisioning.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="admin-guide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="developer-guide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="release-notes-3.0.4.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloudstack_admin.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloudstack_admin.xml b/docs/en-US/cloudstack_admin.xml
new file mode 100644
index 0000000..8b1d0b2
--- /dev/null
+++ b/docs/en-US/cloudstack_admin.xml
@@ -0,0 +1,12 @@
+<?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;
+]>
+<book>
+	<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="admin-guide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloudstack_developers.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloudstack_developers.xml b/docs/en-US/cloudstack_developers.xml
new file mode 100644
index 0000000..8fc5e2a
--- /dev/null
+++ b/docs/en-US/cloudstack_developers.xml
@@ -0,0 +1,12 @@
+<?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;
+]>
+<book>
+	<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="developer-guide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloudstack_features.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloudstack_features.xml b/docs/en-US/cloudstack_features.xml
new file mode 100644
index 0000000..5cf619e
--- /dev/null
+++ b/docs/en-US/cloudstack_features.xml
@@ -0,0 +1,42 @@
+	<section id="cloudstack_features">
+		<title>What Can CloudStack Do?</title>
+		
+		<para>
+			<emphasis role="bold">Multiple Hypervisor Support</emphasis>
+		</para>
+		<para>
+			CloudStack works with a variety of hypervisors. A single cloud deployment can contain multiple hypervisor implementations. You have the complete freedom to choose the right hypervisor for your workload. CloudStack is designed to work with open source Xen and KVM hypervisors as well as enterprise-grade hypervisors such as Citrix XenServer, VMware vSphere, and Oracle VM (OVM). You can also provision “bare metal” hosts with no hypervisor (Beta feature. Untested in CloudStack 3.0.x0.)
+		</para>
+		<para>
+			<emphasis role="bold">Massively Scalable Infrastructure Management</emphasis>
+		</para>
+		<para>
+			CloudStack can manage tens of thousands of servers installed in multiple geographically distributed datacenters. The centralized management server scales linearly, eliminating the need for intermediate cluster-level management servers. No single component failure can cause cloud-wide outage. Periodic maintenance of the management server can be performed without affecting the functioning of virtual machines running in the cloud.
+		</para>
+		<para>
+			<emphasis role="bold">Automatic Configuration Management</emphasis>
+		</para>
+		<para>CloudStack automatically configures each guest virtual machine’s networking and storage settings.
+		</para>
+		<para>CloudStack internally manages a pool of virtual appliances to support the cloud itself. These appliances offer services such as firewalling, routing, DHCP, VPN access, console proxy, storage access, and storage replication. The extensive use of virtual appliances simplifies the installation, configuration, and ongoing management of a cloud deployment.
+		</para>
+		<para>
+			<emphasis role="bold">Graphical User Interface</emphasis>
+		</para>
+		<para>CloudStack offers an administrator's Web interface, used for provisioning and managing the cloud, as well as an end-user's Web interface, used for running VMs and managing VM templates. The UI can be customized to reflect the desired service provider or enterprise look and feel.
+		</para>
+		<para>
+			<emphasis role="bold">API and Extensibility</emphasis>
+		</para>
+		<para>
+			CloudStack provides an API that gives programmatic access to all the management features available in the UI. The API is maintained and documented. This API enables the creation of command line tools and new user interfaces to suit particular needs. See the Developer’s Guide and API Reference, both available at http://docs.cloud.com/CloudStack_Documentation.
+		</para>
+		<para>
+			The CloudStack platform pluggable allocation architecture allows the creation of new types of allocators for the selection of storage and Hosts. See the Allocator Implementation Guide (http://docs.cloud.com/CloudStack_Documentation/Allocator_Implementation_Guide).
+		</para>
+		<para>
+			<emphasis role="bold">High Availability</emphasis>
+		</para>
+		<para>The CloudStack platform has a number of features to increase the availability of the system. The Management Server itself may be deployed in a multi-node installation where the servers are load balanced. MySQL may be configured to use replication to provide for a manual failover in the event of database loss. For the Hosts, the CloudStack platform supports NIC bonding and the use of separate networks for storage as well as iSCSI Multipath.
+		</para>
+	</section>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloudstack_installation.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloudstack_installation.xml b/docs/en-US/cloudstack_installation.xml
new file mode 100644
index 0000000..c57fc47
--- /dev/null
+++ b/docs/en-US/cloudstack_installation.xml
@@ -0,0 +1,12 @@
+<?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;
+]>
+<book>
+	<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloudstack_system_requirements.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloudstack_system_requirements.xml b/docs/en-US/cloudstack_system_requirements.xml
new file mode 100644
index 0000000..b8ce043
--- /dev/null
+++ b/docs/en-US/cloudstack_system_requirements.xml
@@ -0,0 +1,45 @@
+	<section id="cloudstack_system_requirements">
+		<title>Minimum System Requirements</title>
+		<para>
+			The machines that will run the Management Server and MySQL database must meet the following requirements. The same machines can also be used to provide primary and secondary storage, such as via localdisk or NFS. The Management Server may be placed on a virtual machine.
+		</para>
+		<itemizedlist>
+			<listitem><para>Operating system:</para>
+				<itemizedlist>
+					<listitem><para>Commercial users: Preferred: RHEL 6.2+ 64-bit (https://access.redhat.com/downloads) or CentOS 6.2+ 64-bit (http://isoredirect.centos.org/centos/6/isos/x86_64/). Also supported (v3.0.3 and greater): RHEL and CentOS 5.4-5.x 64-bit</para></listitem>
+					<listitem><para>Open-source community users: RHEL 5.4-5.x 64-bit or 6.2+ 64-bit; CentOS 5.4-5.x 64-bit or 6.2+ 64-bit; Ubuntu 10.04 LTS</para></listitem>
+				</itemizedlist>
+			</listitem>
+			<listitem><para>64-bit x86 CPU (more cores results in better performance)</para></listitem>
+			<listitem><para>4 GB of memory</para></listitem>
+			<listitem><para>250 GB of local disk (more results in better capability; 500 GB recommended)</para></listitem>
+			<listitem><para>At least 1 NIC</para></listitem>
+			<listitem><para>Statically allocated IP address</para></listitem>
+			<listitem><para>Fully qualified domain name as returned by the hostname command</para></listitem>
+		</itemizedlist>
+		<para>The host is where the cloud services run in the form of guest virtual machines. Each host is one machine that meets the following requirements:</para>
+		<itemizedlist>
+			<listitem><para>Must be 64-bit and must support HVM (Intel-VT or AMD-V enabled).</para></listitem> 
+			<listitem><para>64-bit x86 CPU (more cores results in better performance)</para></listitem>
+			<listitem><para>Hardware virtualization support required</para></listitem>
+			<listitem><para>4 GB of memory</para></listitem>
+			<listitem><para>36 GB of local disk</para></listitem>
+			<listitem><para>At least 1 NIC</para></listitem>
+			<listitem><para>Statically allocated IP Address</para></listitem>
+			<listitem><para>Latest hotfixes applied to hypervisor software</para></listitem>
+			<listitem><para>When you deploy CloudStack, the hypervisor host must not have any VMs already running</para></listitem>
+		</itemizedlist>
+		<para>Hosts have additional requirements depending on the hypervisor. See the requirements listed at the top of the Installation section for your chosen hypervisor:</para>
+		<itemizedlist>
+			<listitem><para>Citrix XenServer Installation for CloudStack</para></listitem>
+			<listitem><para>VMware vSphere Installation and Configuration</para></listitem>
+			<listitem><para>KVM Installation and Configuration</para></listitem>
+			<listitem><para>Oracle VM (OVM) Installation and Configuration</para></listitem>
+		</itemizedlist>
+		<warning>
+			<para>
+				Be sure you fulfill the additional hypervisor requirements and installation steps provided in this Guide. Hypervisor hosts must be properly prepared to work with CloudStack. For example, the requirements for XenServer are listed under Citrix XenServer Installation for CloudStack.
+			</para>
+		</warning>
+	</section>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloudstack_trial_installation.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloudstack_trial_installation.xml b/docs/en-US/cloudstack_trial_installation.xml
new file mode 100644
index 0000000..084c867
--- /dev/null
+++ b/docs/en-US/cloudstack_trial_installation.xml
@@ -0,0 +1,12 @@
+<?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;
+]>
+<book>
+	<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="trial-installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cloudstack_whatis.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloudstack_whatis.xml b/docs/en-US/cloudstack_whatis.xml
new file mode 100644
index 0000000..00f010a
--- /dev/null
+++ b/docs/en-US/cloudstack_whatis.xml
@@ -0,0 +1,25 @@
+	<section id="cloudstack_whatis">
+		<title>What Is CloudStack?</title>
+		<para>
+			Who Should Read This
+		</para>
+		<para>
+			If you are new to CloudStack or you want to learn more about concepts before installing and running CloudStack, read this overview. 
+			If you just want to get started, you can skip to Overview of Installation Steps.
+			
+		</para>
+		<para>
+			CloudStack is an open source software platform that pools computing resources to build public, private, and hybrid Infrastructure as a Service (IaaS) clouds. CloudStack manages the network, storage, and compute nodes that make up a cloud infrastructure. Use CloudStack to deploy, manage, and configure cloud computing environments.
+			Typical users are service providers and enterprises. With CloudStack, you can:
+			<itemizedlist>
+				<listitem>
+			<para>Set up an on-demand, elastic cloud computing service. Service providers can sell self service virtual machine instances, storage volumes, and networking configurations over the Internet.
+			</para></listitem>
+				<listitem>
+				<para>Set up an on-premise private cloud for use by employees. Rather than managing virtual machines in the same way as physical machines, with CloudStack an enterprise can offer self-service virtual machines to users without involving IT departments.
+				</para></listitem>
+			</itemizedlist>
+			
+		</para>
+	</section>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/cluster-add.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cluster-add.xml b/docs/en-US/cluster-add.xml
new file mode 100644
index 0000000..e269ab1
--- /dev/null
+++ b/docs/en-US/cluster-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="cluster-add">
+	<title>Adding a Cluster</title>
+	<para>TODO</para>
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/compatibility-matrix.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/compatibility-matrix.xml b/docs/en-US/compatibility-matrix.xml
new file mode 100644
index 0000000..e96be71
--- /dev/null
+++ b/docs/en-US/compatibility-matrix.xml
@@ -0,0 +1,97 @@
+<?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="compatibility-matrix">
+	<title>Compatibility Matrix</title>
+			<informaltable>
+					<tgroup cols="7" align="left" colsep="1" rowsep="1">
+						<thead>
+							<row>
+								<entry><para>Hypervisor</para></entry>
+								<entry><para>CloudStack 2.1.x</para></entry>
+								<entry><para>CloudStack 2.2.x</para></entry>
+								<entry><para>CloudStack 3.0.0</para></entry>
+								<entry><para>CloudStack 3.0.1</para></entry>
+								<entry><para>CloudStack 3.0.2</para></entry>
+								<entry><para>CloudStack 3.0.3</para></entry>
+							</row>
+						</thead>
+						<tbody>
+							<row>
+								<entry><para>XenServer 5.6</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>No</para></entry>
+								<entry><para>No</para></entry>
+								<entry><para>No</para></entry>
+								<entry><para>No</para></entry>
+							</row>
+							<row>
+								<entry><para>XenServer 5.6 FP1</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>No</para></entry>
+								<entry><para>No</para></entry>
+								<entry><para>No</para></entry>
+								<entry><para>No</para></entry>	
+							</row>
+							<row>
+										<entry><para>XenServer 5.6 SP2</para></entry>
+										<entry><para>Yes</para></entry>
+										<entry><para>Yes</para></entry>
+										<entry><para>No</para></entry>
+										<entry><para>No</para></entry>
+										<entry><para>Yes</para></entry>
+										<entry><para>Yes</para></entry>
+									</row>
+									<row>
+										<entry><para>XenServer 6.0.0</para></entry>
+										<entry><para>No</para></entry>
+										<entry><para>No</para></entry>
+										<entry><para>No</para></entry>
+										<entry><para>No</para></entry>
+										<entry><para>No</para></entry>
+										<entry><para>Yes</para></entry>
+									</row>
+								<row>
+									<entry><para>XenServer 6.0.2</para></entry>
+									<entry><para>No</para></entry>
+									<entry><para>No</para></entry>
+									<entry><para>Yes</para></entry>
+									<entry><para>Yes</para></entry>
+									<entry><para>Yes</para></entry>
+									<entry><para>Yes</para></entry>
+								</row>
+							<row>
+								<entry><para>XenServer 6.1</para></entry>
+								<entry><para>No</para></entry>
+								<entry><para>No</para></entry>
+								<entry><para>No</para></entry>
+								<entry><para>No</para></entry>
+								<entry><para>No</para></entry>
+								<entry><para>No</para></entry>
+							</row>
+							<row>
+								<entry><para>KVM (RHEL 6.0 or 6.1)</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+							</row>
+							<row>
+								<entry><para>VMware (vSphere and vCenter, both version 4.1)</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+								<entry><para>Yes</para></entry>
+							</row>
+								</tbody>
+							</tgroup>
+						</informaltable>
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/compute-disk-service-offerings.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/compute-disk-service-offerings.xml b/docs/en-US/compute-disk-service-offerings.xml
new file mode 100644
index 0000000..a5680e4
--- /dev/null
+++ b/docs/en-US/compute-disk-service-offerings.xml
@@ -0,0 +1,29 @@
+<?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="compute-disk-service-offerings">
+    <title>Compute and Disk Service Offerings</title>
+    <para>A service offering is a set of virtual hardware features such as CPU core count and speed, memory, and disk size. The CloudPlatform administrator can set up various offerings, and then end users choose from the available offerings when they create a new VM. A service offering includes the following elements:</para>
+     <itemizedlist>
+         <listitem><para>CPU, memory, and network resource guarantees</para></listitem>
+         <listitem><para>How resources are metered</para></listitem>
+         <listitem><para>How the resource usage is charged</para></listitem>
+         <listitem><para>How often the charges are generated</para></listitem>
+        </itemizedlist>
+    <para>For example,  one service offering might allow users to create a virtual machine instance that is equivalent to a 1 GHz Intel® Core™ 2 CPU, with 1 GB memory at $0.20/hour, with network traffic metered at $0.10/GB. Based on the user’s selected offering, CloudPlatform emits usage records that can be integrated with billing systems. CloudPlatform separates service offerings into compute offerings and disk offerings. The computing service offering specifies:</para>
+    <itemizedlist>
+        <listitem><para>Guest CPU</para></listitem>
+        <listitem><para>Guest RAM</para></listitem>
+        <listitem><para>Guest Networking type (virtual or direct)</para></listitem>
+        <listitem><para>Tags on the root disk</para></listitem>
+    </itemizedlist>
+    <para>The disk offering specifies:</para>
+    <itemizedlist>
+        <listitem><para>Disk size (optional).  An offering without a disk size will allow users to pick their own</para></listitem>
+        <listitem><para>Tags on the data disk</para></listitem>
+    </itemizedlist>
+</section>
+
+    

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/concepts.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/concepts.xml b/docs/en-US/concepts.xml
new file mode 100644
index 0000000..3cd3b72
--- /dev/null
+++ b/docs/en-US/concepts.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;
+]>
+<chapter id="concepts">
+	<title>Concepts</title>
+		<xi:include href="whatis.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+		<xi:include href="feature-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+		<xi:include href="deployment-architecture-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/configure-guest-traffic-in-advanced-zone.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/configure-guest-traffic-in-advanced-zone.xml b/docs/en-US/configure-guest-traffic-in-advanced-zone.xml
new file mode 100644
index 0000000..82204df
--- /dev/null
+++ b/docs/en-US/configure-guest-traffic-in-advanced-zone.xml
@@ -0,0 +1,31 @@
+<?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="configure-guest-traffic-in-advanced-zone">
+	<title>Configure Guest Traffic in an Advanced Zone</title>
+	<para>These steps assume you have already logged in to the CloudPlatform UI. To configure the base guest network:</para>
+	<orderedlist>
+		<listitem><para>In the left navigation, choose Infrastructure. On Zones, click View More, then click the zone to which you want to add a network.</para></listitem>
+		<listitem><para>Click the Network tab.</para></listitem>
+		<listitem><para>Click Add network.</para></listitem>
+		<listitem><para>Provide the following information:</para>
+		<itemizedlist>
+			<listitem><para>Name. The name of the network.  This will be user-visible</para></listitem>
+			<listitem><para>Description: The description of the network.  This will be user-visible</para></listitem>
+			<listitem><para>VLAN ID: Enter an administrator-configured VLAN ID so you can create different networks for use by different VM users in the zone</para></listitem>
+			<listitem><para>Scope: Choose account-specific or domain-specific if you would like to make the network accessible to only a single account or domain.  Choose zone-wide if all accounts with access to the zone should be able to access the network.</para></listitem>
+			<listitem><para>Domain/Account: If Scope is account-specific, enter the domain and account name for the account</para></listitem>
+			<listitem><para>Network offering: If the administrator has configured multiple network offerings, select the one you want to use for this network</para></listitem>
+			<listitem><para>Gateway: The gateway that the guests should use</para></listitem>
+			<listitem><para>Netmask: The netmask in use on the subnet the guests will use</para></listitem>
+			<listitem><para>Start IP/End IP: Enter the first and last IP addresses that define a range that CloudPlatform can assign to guests. If one NIC is used, these IPs should be in the same CIDR as the pod CIDR.  If multiple NICs are used, they may be in a different subnet.</para></listitem>
+			<listitem><para>Network Domain: (Optional) If you want to assign a special domain name to this network, specify the DNS suffix.</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/configure-public-traffic-in-an-advanced-zone.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/configure-public-traffic-in-an-advanced-zone.xml b/docs/en-US/configure-public-traffic-in-an-advanced-zone.xml
new file mode 100644
index 0000000..2420410
--- /dev/null
+++ b/docs/en-US/configure-public-traffic-in-an-advanced-zone.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="configure-public-traffic-in-an-advanced-zone">
+    <title>Configure Public Traffic in an Advanced Zone</title>
+    <para>In a zone that uses advanced networking, you need to configure at least one range of IP addresses for Internet traffic.</para>
+					
+	</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/configure-usage-server.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/configure-usage-server.xml b/docs/en-US/configure-usage-server.xml
new file mode 100644
index 0000000..6097361
--- /dev/null
+++ b/docs/en-US/configure-usage-server.xml
@@ -0,0 +1,82 @@
+<?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="configure-usage-server">
+    <title>Configuring the Usage Server</title>
+    <para>To configure the usage server:</para>
+    <orderedlist>
+        <listitem><para>Be sure the Usage Server has been installed. This requires extra steps beyond just installing the CloudPlatform software. See Installing the Usage Server (Optional) in the Advanced Installation Guide.</para></listitem>
+        <listitem><para>Log in to the CloudPlatform UI as administrator.</para></listitem>
+        <listitem><para>Click Global Settings.</para></listitem>
+        <listitem><para>In Search, type usage. Find the configuration parameter that controls the behavior you want to set. See the table below for a description of the available parameters.</para></listitem>
+        <listitem><para>In Actions, click the Edit icon.</para></listitem>
+        <listitem><para>Type the desired value and click the Save icon.</para></listitem>
+        <listitem><para>Restart the Management Server (as usual with any global configuration change) and also the Usage Server:</para>
+         <programlisting># service cloud-management restart
+# service cloud-usage restart 
+</programlisting></listitem>
+    </orderedlist>
+    <para>The following table shows the global configuration settings that control the behavior of the Usage Server.</para>
+    <informaltable>
+        <tgroup cols="2" align="left" colsep="1" rowsep="1">
+            <thead>
+                <row>
+                    <entry><para>Parameter Name</para></entry>
+                    <entry><para>Description</para></entry>                                     
+                </row>
+                </thead>
+                <tbody> 
+                <row>
+                    <entry><para>enable.usage.server</para></entry>
+                    <entry><para>Whether the Usage Server is active.</para></entry>                
+                </row>
+                <row>
+                    <entry><para>usage.aggregation.timezone</para></entry>
+                    <entry><para>Time zone of usage records. Set this if the usage records and daily job execution are in different time zones. For example, with the following settings, the usage job will run at PST 00:15 and generate usage records for the 24 hours from 00:00:00 GMT to 23:59:59 GMT:</para>
+                    <programlisting>usage.stats.job.exec.time = 00:15	
+usage.execution.timezone = PST
+usage.aggregation.timezone = GMT
+                        </programlisting>
+                        <para>Valid values for the time zone are specified in <xref linkend="appendix-a-time-zones"/></para>
+                        <para>Default: GMT</para>
+                    </entry>                    
+                </row>
+                <row>
+                    <entry><para>usage.execution.timezone</para></entry>
+                    <entry><para>The time zone of usage.stats.job.exec.time.  Valid values for the time zone are specified in <xref linkend="appendix-a-time-zones"/></para>
+                        <para>Default: The time zone of the management server.</para>
+                    </entry>                    
+                </row>
+                <row>
+                    <entry><para>usage.sanity.check.interval</para></entry>
+                    <entry><para>The number of days between sanity checks. Set this in order to periodically search for records with erroneous data before issuing customer invoices. For example, this checks for VM usage records created after the VM was destroyed, and similar checks for templates, volumes, and so on. It also checks for usage times longer than the aggregation range.  If any issue is found, the alert ALERT_TYPE_USAGE_SANITY_RESULT = 21 is sent.</para></entry>                    
+                </row>
+                <row>
+                    <entry><para>usage.stats.job.aggregation.range</para></entry>
+                    <entry><para>The time period in minutes between Usage Server processing jobs. For example, if you set it to 1440, the Usage Server will run once per day. If you set it to 600, it will run every ten hours. In general, when a Usage Server job runs, it processes all events generated since usage was last run.</para>
+                        <para>There is special handling for the case of 1440 (once per day). In this case the Usage Server does not necessarily process all records since Usage was last run. CloudPlatform assumes that you require processing once per day for the previous, complete day’s records. For example, if the current day is October 7, then it is assumed you would like to process records for October 6, from midnight to midnight. CloudPlatform assumes this “midnight to midnight” is relative to the usage.execution.timezone.</para>
+                        <para>Default: 1440</para>
+                    </entry>                    
+                </row>
+                <row>
+                    <entry><para>usage.stats.job.exec.time</para></entry>
+                    <entry><para>The time when the Usage Server processing will start. It is specified in 24-hour format (HH:MM) in the time zone of the server, which should be GMT. For example, to start the Usage job at 10:30 GMT, enter “10:30”.</para>
+                    <para>If usage.stats.job.aggregation.range is also set, and its value is not 1440, then its value will be added to usage.stats.job.exec.time to get the time to run the Usage Server job again. This is repeated until 24 hours have elapsed, and the next day's processing begins again at usage.stats.job.exec.time.</para>
+                        <para>Default: 00:15.</para>
+                    </entry>                    
+                </row>
+            </tbody>
+        </tgroup>
+    </informaltable>
+    <para>For example, suppose that your server is in GMT, your user population is predominantly in the East Coast of the United States, and you would like to process usage records every night at 2 AM local (EST) time. Choose these settings:</para>
+    <itemizedlist>
+        <listitem><para>enable.usage.server = true</para></listitem>
+        <listitem><para>usage.execution.timezone = America/New_York</para></listitem>
+        <listitem><para>usage.stats.job.exec.time = 07:00. This will run the Usage job at 2:00 AM EST. Note that this will shift by an hour as the East Coast of the U.S. enters and exits Daylight Savings Time.</para></listitem>
+        <listitem><para>usage.stats.job.aggregation.range = 1440</para></listitem>
+    </itemizedlist>
+    <para>With this configuration, the Usage job will run every night at 2 AM EST and will process records for the previous day’s midnight-midnight as defined by the EST (America/New_York) time zone.</para>
+    <note><para>Because the special value 1440 has been used for usage.stats.job.aggregation.range, the Usage Server will ignore the data between midnight and 2 AM. That data will be included in the next day's run</para></note>    
+</section>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/configure-virtual-router.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/configure-virtual-router.xml b/docs/en-US/configure-virtual-router.xml
new file mode 100644
index 0000000..7aab6b3
--- /dev/null
+++ b/docs/en-US/configure-virtual-router.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="configure-virtual-router">
+    <title>Configuring the Virtual Router</title>
+    <para>You can set the following:</para>
+    <itemizedlist>
+        <listitem><para>IP range</para></listitem>
+        <listitem><para>Supported network services</para></listitem>
+        <listitem><para>Default domain name for the network serviced by the virtual router</para></listitem>
+        <listitem><para>Gateway IP address</para></listitem>
+        <listitem><para>How often CloudPlatform fetches network usage statistics from CloudPlatform virtual routers. If you want to collect traffic metering data from the virtual router, set the global configuration parameter router.stats.interval. If you are not using the virtual router to gather network usage statistics, set it to 0.</para></listitem>
+    </itemizedlist>
+    
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/configure-vpn.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/configure-vpn.xml b/docs/en-US/configure-vpn.xml
new file mode 100644
index 0000000..cab25fd
--- /dev/null
+++ b/docs/en-US/configure-vpn.xml
@@ -0,0 +1,33 @@
+<?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="configure-vpn">
+	<title>Configuring VPN</title>
+	<para>To set up VPN for the cloud:</para>
+	<orderedlist>
+		<listitem><para>Log in to the CloudPlatform UI as an administrator or end user. </para></listitem>
+		<listitem><para>In the left navigation, click Global Settings.</para></listitem>
+		<listitem><para>Set the following global configuration parameters.</para>
+		<itemizedlist>
+			<listitem><para>remote.access.vpn.client.ip.range – The range of IP addressess to be allocated to remote access VPN clients. The first IP in the range is used by the VPN server.</para></listitem>
+			<listitem><para>remote.access.vpn.psk.length – Length of the IPSec key.</para></listitem>
+			<listitem><para>remote.access.vpn.user.limit – Maximum number of VPN users per account.</para></listitem>
+		</itemizedlist></listitem></orderedlist>
+		<para>To enable VPN for a particular network:</para>	
+		<orderedlist>
+			<listitem><para>Log in as a user or administrator to the CloudPlatform UI.</para></listitem>			
+			<listitem><para>In the left navigation, click Network.</para></listitem>
+			<listitem><para>Click the name of the network you want to work with.</para></listitem>
+			<listitem><para>Click View IP Addresses.</para></listitem>
+			<listitem><para>Click one of the displayed IP address names.</para></listitem>
+			<listitem><para>Click the Enable VPN button <inlinemediaobject>
+				<imageobject>
+					<imagedata fileref="./images/vpn-icon.png" />
+				</imageobject>
+				<textobject><phrase>AttachDiskButton.png: button to attach a volume</phrase></textobject>
+			</inlinemediaobject>.</para>
+				<para>The IPsec key is displayed in a popup window.</para></listitem>
+		</orderedlist>	
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/configure-xenserver-dom-memory.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/configure-xenserver-dom-memory.xml b/docs/en-US/configure-xenserver-dom-memory.xml
new file mode 100644
index 0000000..c647cd8
--- /dev/null
+++ b/docs/en-US/configure-xenserver-dom-memory.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="configure-xenserver-dom0-memory">
+    <title>Configure XenServer dom0 Memory</title>
+    <para>Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0.  For instructions on how to do this, see  <ulink url="http://support.citrix.com/article/CTX126531">Citrix Knowledgebase Article</ulink>.The article refers to XenServer 5.6, but the same information applies to XenServer 6</para>
+</section>
+      

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/configure-xenserver-dom0-memory.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/configure-xenserver-dom0-memory.xml b/docs/en-US/configure-xenserver-dom0-memory.xml
new file mode 100644
index 0000000..c647cd8
--- /dev/null
+++ b/docs/en-US/configure-xenserver-dom0-memory.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="configure-xenserver-dom0-memory">
+    <title>Configure XenServer dom0 Memory</title>
+    <para>Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0.  For instructions on how to do this, see  <ulink url="http://support.citrix.com/article/CTX126531">Citrix Knowledgebase Article</ulink>.The article refers to XenServer 5.6, but the same information applies to XenServer 6</para>
+</section>
+      

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/configuring-projects.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/configuring-projects.xml b/docs/en-US/configuring-projects.xml
new file mode 100644
index 0000000..925f360
--- /dev/null
+++ b/docs/en-US/configuring-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="configuring-projects">
+    <title>Configuring Projects</title>
+    <para>Before CloudPlatform users start using projects, the CloudPlatform administrator must set up various systems to support them, including membership invitations, limits on project resources, and controls on who can create projects</para>
+</section>
+      

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/console-proxy.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/console-proxy.xml b/docs/en-US/console-proxy.xml
new file mode 100644
index 0000000..bc14445
--- /dev/null
+++ b/docs/en-US/console-proxy.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="console-proxy">
+    <title>Console Proxy</title>
+    <para>The Console Proxy is a type of System Virtual Machine that has a role in presenting a console view via the web UI. It connects the user’s browser to the VNC port made available via the hypervisor for the console of the guest. Both the administrator and end user web UIs offer a console connection.</para>
+    <para>Clicking on a console icon brings up a new window. The AJAX code downloaded into that window refers to the public IP address of a console proxy VM. There is exactly one public IP address allocated per console proxy VM. The AJAX application connects to this IP. The console proxy then proxies the connection to the VNC port for the requested VM on the Host hosting the guest. .</para>
+    <note><para>The hypervisors will have many ports assigned to VNC usage so that multiple VNC sessions can occur simultaneously.</para></note>
+    <para>There is never any traffic to the guest virtual IP, and there is no need to enable VNC within the guest.</para>
+    <para>The console proxy VM will periodically report its active session count to the Management Server. The default reporting interval is five seconds. This can be changed through standard Management Server configuration with the parameter consoleproxy.loadscan.interval.</para>
+    <para>Assignment of guest VM to console proxy is determined by first determining if the guest VM has a previous session associated with a console proxy. If it does, the Management Server will assign the guest VM to the target Console Proxy VM regardless of the load on the proxy VM. Failing that, the first available running Console Proxy VM that has the capacity to handle new sessions is used.</para>
+    <para>Console proxies can be restarted by administrators but this will interrupt existing console sessions for users.</para>
+    <para>The console viewing functionality uses a dynamic DNS service under the domain name realhostip.com to assist in providing SSL security to console sessions.  The console proxy is assigned a public IP address.  In order to avoid browser warnings for mismatched SSL certificates, the URL for the new console window is set to the form of https://aaa-bbb-ccc-ddd.realhostip.com. Customers will see this URL during console session creation.  CloudPlatform includes the realhostip.com SSL certificate in the console proxy VM.  Of course, CloudPlatform cannot know about DNS A records for our customers' public IPs prior to shipping the software.  CloudPlatform therefore runs a dynamic DNS server that is authoritative for the realhostip.com domain.  It maps the aaa-bbb-ccc-ddd part of the DNS name to the IP address aaa.bbb.ccc.ddd on lookups.  This allows the browser to correctly connect to the console proxy's public IP, where it then expects and receives a SSL certificate for realhostip.c
 om, and SSL is set up without browser warnings.</para>
+   </section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/contacting-support.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/contacting-support.xml b/docs/en-US/contacting-support.xml
new file mode 100644
index 0000000..ef165b3
--- /dev/null
+++ b/docs/en-US/contacting-support.xml
@@ -0,0 +1,5 @@
+	<section id="contacting-support">
+		<title>Contacting Support</title>
+	    <para>The support team is available to help customers plan and execute their installations.  To contact the support team, log in to the support portal at <ulink url="support.citrix.com/cloudsupport">support.citrix.com/cloudsupport</ulink> by using the account credentials you received when you purchased your support contract.</para>
+	</section>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/convert-hyperv-vm-to-template.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/convert-hyperv-vm-to-template.xml b/docs/en-US/convert-hyperv-vm-to-template.xml
new file mode 100644
index 0000000..813112c
--- /dev/null
+++ b/docs/en-US/convert-hyperv-vm-to-template.xml
@@ -0,0 +1,50 @@
+<?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="convert-hyperv-vm-to-template">
+	<title>Converting a Hyper-V VM to a Template</title>
+	<para>To convert a Hyper-V VM to a XenServer-compatible CloudPlatform template, you will need a standalone XenServer host with an attached NFS VHD SR.  Use whatever XenServer version you are using with CloudPlatform, but use XenCenter 5.6 FP1 or SP2 (it is backwards compatible to 5.6).  Additionally, it may help to have an attached NFS ISO SR.</para>
+	<para>For Linux VMs, you may need to do some preparation in Hyper-V before trying to get the VM to work in XenServer.  Clone the VM and work on the clone if you still want to use the VM in Hyper-V.  Uninstall Hyper-V Integration Components and check for any references to device names in /etc/fstab:</para>
+	<orderedlist>
+		<listitem><para>From the linux_ic/drivers/dist directory, run make uninstall (where "linux_ic" is the path to the copied Hyper-V Integration Components files).</para></listitem>
+		<listitem><para>Restore the original initrd from backup in /boot/ (the backup is named *.backup0).</para></listitem>
+		<listitem><para>Remove the "hdX=noprobe" entries from /boot/grub/menu.lst.</para></listitem>
+		<listitem><para>Check /etc/fstab for any partitions mounted by device name.  Change those entries (if any) to mount by LABEL or UUID (get that information with the "blkid" command)..</para></listitem>
+	</orderedlist>
+	<para>The next step is make sure the VM is not running in Hyper-V, then get the VHD into XenServer.  There are two options for doing this.</para>
+	<para>Option one:</para>
+	<orderedlist>
+	<listitem><para>Import the VHD using XenCenter.  In XenCenter, go to Tools&gt;Virtual Appliance Tools&gt;Disk Image Import.</para></listitem>		
+		<listitem><para>Choose the VHD, then click Next.</para></listitem>
+		<listitem><para>Name the VM, choose the NFS VHD SR under Storage, enable "Run Operating System Fixups" and choose the NFS ISO SR.</para></listitem>
+		<listitem><para>Click Next, then Finish.  A VM should be created.</para></listitem>
+	</orderedlist>
+	<para>Option two</para>
+	<orderedlist>
+		<listitem><para>Run XenConvert, under From choose VHD, under To choose XenServer. Click Next.</para></listitem>
+		<listitem><para>Choose the VHD, then click Next.</para></listitem>		
+		<listitem><para>Input the XenServer host info, then click Next.</para></listitem>
+		<listitem><para>Name the VM, then click Next, then Convert.  A VM should be created</para></listitem>
+	</orderedlist>
+	<para>Once you have a VM created from the Hyper-V VHD, prepare it using the following steps:</para>
+	<orderedlist>
+		<listitem><para>Boot the VM, uninstall Hyper-V Integration Services, and reboot.</para></listitem>
+		<listitem><para>Install XenServer Tools, then reboot.</para></listitem>		
+		<listitem><para>Prepare the VM as desired. For example, run sysprep on Windows VMs. See <xref linkend="create-windows-template"/></para></listitem>
+	</orderedlist>
+	<para>Either option above will create a VM in HVM mode.  This is fine for Windows VMs, but Linux VMs may not perform optimally.  Converting a Linux VM to PV mode will require additional steps and will vary by distribution.</para>
+	<orderedlist>
+		<listitem><para>Shut down the VM and copy the VHD from the NFS storage to a web server; for example, mount the NFS share on the web server and copy it, or from the XenServer host use sftp or scp to upload it to the web server.</para></listitem>
+		<listitem><para>In CloudPlatform, create a new template using the following values:</para>
+		<itemizedlist>
+			<listitem><para>URL. Give the URL for the VHD</para></listitem>
+			<listitem><para>OS Type. Use the appropriate OS. For PV mode on CentOS, choose Other PV (32-bit) or Other PV (64-bit). This choice is available only for XenServer.</para></listitem>
+			<listitem><para>Hypervisor. XenServer</para></listitem>
+			<listitem><para>Format. VHD</para></listitem>
+		</itemizedlist></listitem>
+		
+	</orderedlist>
+	<para>The template will be created, and you can create instances from it.</para>
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/create-bare-metal-template.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/create-bare-metal-template.xml b/docs/en-US/create-bare-metal-template.xml
new file mode 100644
index 0000000..9effd86
--- /dev/null
+++ b/docs/en-US/create-bare-metal-template.xml
@@ -0,0 +1,31 @@
+<?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="create-bare-metal-template">
+	<title>Creating a Bare Metal Template</title>
+	<note><para><emphasis role="bold">Beta feature. Untested in	CloudPlatform 3.0.3. Provided without guarantee of performance</emphasis>.</para></note>
+	<para>Before you can create a bare metal template, you must have performed several other installation and setup steps to create a bare metal cluster and environment. See Bare Metal Installation in the Installation Guide. It is assumed you already have a directory named "win7_64bit" on your CIFS server, containing the image for the bare metal instance. This directory and image are set up as part of the Bare Metal Installation procedure.</para>
+	<orderedlist>
+		<listitem><para>Log in to the CloudPlatform UI as an administrator or end user.</para></listitem>
+		<listitem><para>In the left navigation bar, click Templates.</para></listitem>
+		<listitem><para>Click Create Template.</para></listitem>
+		<listitem><para>In the dialog box, enter the following values.</para>
+		<itemizedlist>
+			<listitem><para><emphasis role="bold">Name</emphasis>. Short name for the template.</para></listitem>
+			<listitem><para><emphasis role="bold">Display Text</emphasis>. Description of the template.</para></listitem>
+			<listitem><para><emphasis role="bold">URL</emphasis>. The directory name which contains image file on your
+						CIFS server. For example, win7_64bit.</para></listitem>
+			<listitem><para><emphasis role="bold">Zone</emphasis>. All Zones.</para></listitem>			
+			<listitem><para><emphasis role="bold">OS Type</emphasis>. Select the OS type of the ISO image. Choose other if
+						the OS Type of the ISO is not listed or if the ISO is not bootable.</para></listitem>
+			<listitem><para><emphasis role="bold">Hypervisor</emphasis>. BareMetal.</para></listitem>
+			<listitem><para><emphasis role="bold">Format</emphasis>. BareMetal.</para></listitem>
+			<listitem><para><emphasis role="bold">Password Enabled</emphasis>. No.</para></listitem>
+			<listitem><para><emphasis role="bold">Public</emphasis>. No.</para></listitem>
+			<listitem><para><emphasis role="bold">Featured</emphasis>. Choose Yes if you would like this template to be
+						more prominent for users to select. Only administrators may make templates
+						featured.</para></listitem>
+		</itemizedlist></listitem></orderedlist>
+	</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/create-new-projects.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/create-new-projects.xml b/docs/en-US/create-new-projects.xml
new file mode 100644
index 0000000..69e8360
--- /dev/null
+++ b/docs/en-US/create-new-projects.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="create-new-projects">
+    <title>Creating a New Project</title>
+    <para>CloudPlatform administrators and domain administrators can create projects. If the global configuration parameter allow.user.create.projects is set to true, end users can also create projects.</para>
+    <orderedlist>
+        <listitem><para>Log in as administrator to the CloudPlatform UI.</para></listitem>
+        <listitem><para>In the left navigation, click Projects.</para></listitem>
+        <listitem><para>In Select view, click Projects.</para></listitem>
+        <listitem><para>Click New Project.</para></listitem>
+        <listitem><para>Give the project a name and description for display to users, then click Create Project.</para></listitem>
+        <listitem><para>A screen appears where you can immediately add more members to the project. This is optional. Click Next when you are ready to move on.</para></listitem>
+        <listitem><para>Click Save.</para></listitem>
+    </orderedlist>
+   </section>
+      

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/create-template-from-existing-vm.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/create-template-from-existing-vm.xml b/docs/en-US/create-template-from-existing-vm.xml
new file mode 100644
index 0000000..b3b951f
--- /dev/null
+++ b/docs/en-US/create-template-from-existing-vm.xml
@@ -0,0 +1,38 @@
+<?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="create-template-from-existing-vm">
+	<title>Creating a Template from an Existing Virtual Machine</title>
+	<para>Once you have at least one VM set up in the way you want, you can use it as the prototype for other VMs.</para>
+	<orderedlist>
+		<listitem><para>Create and start a virtual machine using any of the techniques given in <xref linkend="creating-vms"/>.</para></listitem>
+		<listitem><para>Make any desired configuration changes on the running VM, then click Stop.</para></listitem>
+		<listitem><para>Wait for the VM to stop. When the status shows Stopped, go to the next step.</para></listitem>
+		<listitem><para>Click Create Template and provide the following:</para>
+		<itemizedlist>
+			<listitem><para><emphasis role="bold">Name and Display Text</emphasis>. These will be shown in the UI, so
+						choose something descriptive.</para></listitem>
+			<listitem><para><emphasis role="bold">OS Type</emphasis>. This helps CloudPlatform and the hypervisor perform
+						certain operations and make assumptions that improve the performance of the
+						guest. Select one of the following.</para>
+				<itemizedlist>
+					<listitem><para>If the operating system of the stopped VM is listed, choose it.</para></listitem>
+					<listitem><para>If the OS type of the stopped VM is not listed, choose Other.</para></listitem>
+					<listitem><para>If you want to boot from this template in PV mode, choose Other PV (32-bit) or Other PV (64-bit). This choice is available only for XenServere:</para>
+					<note><para>Note: Generally you should not choose an older version of the OS than the version in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image will in general not work. In those cases you should choose Other.</para></note></listitem>
+				</itemizedlist>			
+			</listitem>	
+			<listitem><para><emphasis role="bold">Public</emphasis>. Choose Yes to make this template accessible to all
+						users of this CloudPlatform installation. The template will appear in the
+						Community Templates list. See <xref linkend="private-public-template"
+						/>.</para></listitem>
+			<listitem><para><emphasis role="bold">Password Enabled</emphasis>. Choose Yes if your template has the
+						CloudPlatform password change script installed. See Adding Password
+						Management to Your Templates .</para></listitem>
+			</itemizedlist></listitem>
+		<listitem><para>Click Add.</para></listitem>		
+	</orderedlist>
+	<para>The new template will be visible in the Templates section when the template creation process has been completed. The template is then available when creating a new VM</para>
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/create-template-from-snapshot.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/create-template-from-snapshot.xml b/docs/en-US/create-template-from-snapshot.xml
new file mode 100644
index 0000000..23599da
--- /dev/null
+++ b/docs/en-US/create-template-from-snapshot.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="create-template-from-snapshot">
+    <title>Creating a Template from a Snapshot</title>
+    <note><para>Not supported by Oracle VM</para></note>
+    <para>If you do not want to stop the VM in order to use the Create Template menu item (as described in <xref linkend="create-template-from-existing-vm"/>), you can create a template directly from any snapshot through the CloudPlatform UI.</para>
+		
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/create-templates-overview.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/create-templates-overview.xml b/docs/en-US/create-templates-overview.xml
new file mode 100644
index 0000000..9c8bf37
--- /dev/null
+++ b/docs/en-US/create-templates-overview.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="create-templates-overview">
+	<title>Creating Templates: Overview</title>
+	<para>CloudPlatform ships with a default template for the CentOS operating system. There are a variety of ways to add more templates. Administrators and end users can add templates. The typical sequence of events is:</para>
+	<orderedlist>
+		<listitem><para>Launch a VM instance that has the operating system you want. Make any other desired configuration changes to the VM.</para></listitem>
+		<listitem><para>Stop the VM.</para></listitem>
+		<listitem><para>Convert the volume into a template.</para></listitem>
+	</orderedlist>
+	<para>There are other ways to add templates to CloudPlatform. For example, you can take a snapshot of the VM's volume and create a template from the snapshot, or import a VHD from another system into CloudPlatform</para>
+	<para>The various techniques for creating templates are described in the next few sections.</para>
+	
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/create-windows-template.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/create-windows-template.xml b/docs/en-US/create-windows-template.xml
new file mode 100644
index 0000000..70a71af
--- /dev/null
+++ b/docs/en-US/create-windows-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="create-windows-template">
+	<title>Creating a Windows Template</title>
+	<para>Windows templates must be prepared with Sysprep before they can be provisioned on multiple machines. Sysprep allows you to create a generic Windows template and avoid any possible SID conflicts.</para>
+	<note><para>(XenServer) Windows VMs running on XenServer require PV drivers, which may be provided in the template or added after the VM is created. The PV drivers are necessary for essential management functions such as mounting additional volumes and ISO images, live migration, and graceful shutdown.</para></note>
+	<para>An overview of the procedure is as follows:</para>
+	<orderedlist>
+	<listitem><para>Upload your Windows ISO.</para> <para>For more information, see <xref linkend="add-iso"/></para></listitem>
+	<listitem><para>Create a VM Instance with this ISO.</para><para> For more information, see <xref linkend="creating-vms"/></para></listitem>
+	<listitem><para>Follow the steps in Sysprep for Windows Server 2008 R2 (below) or Sysprep for Windows Server 2003 R2, depending on your version of Windows Server</para></listitem>		
+	<listitem><para>The preparation steps are complete. Now you can actually create the template as described in Creating the Windows Template.</para></listitem>
+	</orderedlist>
+	<xi:include href="sysprep-windows-server-2008R2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="sysprep-for-windows-server-2003R2.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/creating-compute-offerings.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/creating-compute-offerings.xml b/docs/en-US/creating-compute-offerings.xml
new file mode 100644
index 0000000..fc0b6a9
--- /dev/null
+++ b/docs/en-US/creating-compute-offerings.xml
@@ -0,0 +1,33 @@
+<?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="creating-compute-offerings">
+    <title>Creating a New Compute Offering</title>
+    <para>To create a new compute offering:</para>
+    <orderedlist>
+        <listitem><para>Log in with admin privileges to the CloudPlatform UI.</para></listitem>
+        <listitem><para>In the left navigation bar, click Service Offerings.</para></listitem>
+        <listitem><para>In Select Offering, choose Compute Offering.</para></listitem>
+        <listitem><para>Click Add Compute Offering.</para></listitem>
+        <listitem><para>In the dialog, make the following choices:</para>
+        <itemizedlist>
+            <listitem><para>Name. Any desired name for the service offering.</para></listitem>
+            <listitem><para>Description. A short description of the offering that can be displayed to users</para></listitem>
+            <listitem><para>Storage type. The type of disk that should be allocated. Local allocates from storage attached directly to the host where the system VM is running. Shared allocates from storage accessible via NFS.</para></listitem>
+            <listitem><para># of CPU cores. The number of cores which should be allocated to a system VM with this offering</para></listitem>
+            <listitem><para>CPU (in MHz). The CPU speed of the cores that the system VM is allocated. For example, “2000” would provide for a 2 GHz clock.</para></listitem>
+            <listitem><para>Memory (in MB). The amount of memory in megabytes that the system VM should be allocated. For example, “2048” would provide for a 2 GB RAM allocation.</para></listitem>
+            <listitem><para>Network Rate. Allowed data transfer rate in MB per second.</para></listitem>
+            <listitem><para>Offer HA. If yes, the administrator can choose to have the system VM be monitored and as highly available as possible.</para></listitem>
+            <listitem><para>Storage Tags.  The tags that should be associated with the primary storage used by the system VM.</para></listitem>
+            <listitem><para>Host Tags.  (Optional) Any tags that you use to organize your hosts</para></listitem>
+            <listitem><para>CPU cap. Whether to limit the level of CPU usage even if spare capacity is available.</para></listitem>
+            <listitem><para>Public.  Indicate whether the service offering should be available all domains or only some domains.  Choose Yes to make it available to all domains.  Choose No to limit the scope to a subdomain; CloudPlatform will then prompt for the subdomain's name.</para></listitem>
+        </itemizedlist></listitem> 
+        <listitem><para>Click Add.</para></listitem>        
+    </orderedlist>                
+    
+    
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/creating-disk-offerings.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/creating-disk-offerings.xml b/docs/en-US/creating-disk-offerings.xml
new file mode 100644
index 0000000..d455ecc
--- /dev/null
+++ b/docs/en-US/creating-disk-offerings.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="creating-disk-offerings">
+    <title>Creating a New Disk Offering</title>
+    <para>To create a system service offering:</para>
+    <orderedlist>
+        <listitem><para>Log in with admin privileges to the CloudPlatform UI.</para></listitem>
+        <listitem><para>In the left navigation bar, click Service Offerings.</para></listitem>
+        <listitem><para>In Select Offering, choose Disk Offering.</para></listitem>
+        <listitem><para>Click Add Disk Offering.</para></listitem>
+        <listitem><para>In the dialog, make the following choices:</para>
+        <itemizedlist>
+            <listitem><para>Name. Any desired name for the system offering.</para></listitem>
+            <listitem><para>Description. A short description of the offering that can be displayed to users</para></listitem>
+            <listitem><para>Custom Disk Size. If checked, the user can set their own disk size. If not checked, the root administrator must define a value in Disk Size.</para></listitem>
+            <listitem><para>Disk Size. Appears only if Custom Disk Size is not selected. Define the volume size in GB.</para></listitem>
+            <listitem><para>(Optional)Storage Tags.  The tags that should be associated with the primary storage for this disk. Tags are a comma separated list of attributes of the storage.  For example "ssd,blue".  Tags are also added on Primary Storage.  CloudPlatform matches tags on a disk offering to tags on the storage.  If a tag is present on a disk offering that tag (or tags) must also be present on Primary Storage for the volume to be provisioned.  If no such primary storage exists, allocation from the disk offering will fail..</para></listitem>
+            <listitem><para>Public.  Indicate whether the service offering should be available all domains or only some domains. Choose Yes to make it available to all domains. Choose No to limit the scope to a subdomain; CloudPlatform will then prompt for the subdomain's name.</para></listitem>
+        </itemizedlist></listitem> 
+        <listitem><para>Click Add.</para></listitem>        
+    </orderedlist>                
+    
+    
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/creating-network-offerings.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/creating-network-offerings.xml b/docs/en-US/creating-network-offerings.xml
new file mode 100644
index 0000000..5bf32be
--- /dev/null
+++ b/docs/en-US/creating-network-offerings.xml
@@ -0,0 +1,112 @@
+<?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="creating-network-offerings">
+    <title>Creating a New Network Offering</title>
+    <para>To create a network offering:</para>
+    <orderedlist>
+        <listitem><para>Log in with admin privileges to the CloudPlatform UI.</para></listitem>
+        <listitem><para>In the left navigation bar, click Service Offerings.</para></listitem>
+        <listitem><para>In Select Offering, choose Network Offering.</para></listitem>
+        <listitem><para>Click Add Network Offering.</para></listitem>
+        <listitem><para>In the dialog, make the following choices:</para>
+        <itemizedlist>
+            <listitem><para>Name. Any desired name for the network offering</para></listitem>
+            <listitem><para>Description. A short description of the offering that can be displayed to users</para></listitem>
+            <listitem><para>Network Rate. Allowed data transfer rate in MB per second</para></listitem>
+            <listitem><para>Traffic Type. The type of network traffic that will be carried on the network</para></listitem>
+            <listitem><para>Guest Type. Choose whether the guest network is isolated or shared. For a description of these terms, see <xref linkend="about-virtual-networks"/> </para></listitem>
+            <listitem><para>Specify VLAN. (Isolated guest networks only) Indicate whether a VLAN should be specified when this offering is used</para></listitem>
+            <listitem><para>Supported Services. Select one or more of the possible network services. For some services,
+                        you must also choose the service provider; for example, if you select Load
+                        Balancer, you can choose the CloudPlatform virtual router or any other load
+                        balancers that have been configured in the cloud. Depending on which
+                        services you choose, additional fields may appear in the rest of the dialog
+                        box.</para><para>Based on the guest network type selected, you can see the following supported services:</para><informaltable>
+                            <tgroup cols="4" align="left" colsep="1" rowsep="1">
+                                <thead>
+                                    <row>
+                                        <entry><para>Supported Services</para></entry>
+                                        <entry><para>Description</para></entry>
+                                        <entry><para>Isolated</para></entry>
+                                        <entry><para>Shared</para></entry>
+                                   </row>     
+                                </thead>
+                                <tbody>
+                                    <row>
+                                        <entry><para>DHCP</para></entry>
+                                        <entry><para></para></entry>
+                                        <entry><para>Supported</para></entry>
+                                        <entry><para>Supported</para></entry>
+                                    </row>
+                                    <row>
+                                        <entry><para>DNS</para></entry>
+                                        <entry><para></para></entry>
+                                        <entry><para>Supported</para></entry>
+                                        <entry><para>Supported</para></entry>
+                                    </row>
+                                    <row>
+                                        <entry><para>Load Balancer</para></entry>
+                                        <entry><para>If you select Load Balancer, you can choose the CloudPlatform virtual router or any other load
+                                            balancers that have been configured in the cloud.</para></entry>
+                                        <entry><para>Supported</para></entry>
+                                        <entry><para>Supported</para></entry>
+                                    </row>
+                                    <row>
+                                        <entry><para>Source NAT</para></entry>
+                                        <entry><para>If you select Source NAT, you can choose the CloudPlatform virtual router or any other Source
+                                            NAT providers that have been configured in the
+                                            cloud.</para></entry>
+                                        <entry><para>Supported</para></entry>
+                                        <entry><para>Supported</para></entry>
+                                    </row>
+                                    <row>
+                                       <entry><para>Static NAT</para></entry>
+                                        <entry><para>If you select Static NAT, you can choose the CloudPlatform virtual router or any other Static
+                                            NAT providers that have been configured in the
+                                            cloud.</para></entry>
+                                        <entry><para>Supported</para></entry>
+                                        <entry><para>Supported</para></entry>
+                                    </row>
+                                    <row>
+                                        <entry><para>Port Forwarding</para></entry>
+                                        <entry><para>If you select Port Forwarding, you can choose the CloudPlatform virtual router or any other
+                                            Port Forwarding providers that have been configured in
+                                            the cloud.</para></entry>
+                                        <entry><para>Supported</para></entry>
+                                        <entry><para>Not Supported</para></entry>
+                                    </row>
+                                    <row>
+                                       <entry><para>VPN</para></entry>
+                                        <entry><para></para></entry>
+                                        <entry><para>Supported</para></entry>
+                                        <entry><para>Not Supported</para></entry>                                        
+                                    </row>
+                                    <row>
+                                        <entry><para>User Data</para></entry>
+                                        <entry><para></para></entry>
+                                        <entry><para>Not Supported</para></entry>
+                                        <entry><para>Supported</para></entry>                                        
+                                    </row>
+                                    <row>
+                                        <entry><para>Security Groups</para></entry>
+                                        <entry><para>See <xref linkend="add-security-group"/>.</para></entry>
+                                        <entry><para>Not Supported</para></entry>
+                                        <entry><para>Supported</para></entry>                                        
+                                    </row>
+                                    </tbody>
+                                 </tgroup>
+                        </informaltable>
+            </listitem>
+            <listitem><para>System Offering. If the service provider for any of the services selected in Supported Services is a virtual router, the System Offering field appears. Choose the system service offering that you want virtual routers to use in this network. For example, if you selected Load Balancer in Supported Services and selected a virtual router to provide load balancing, the System Offering field appears so you can choose between the CloudPlatform default system service offering and any custom system service offerings that have been defined by the CloudPlatform root administrator. For more information, see System Service Offerings.</para></listitem>
+            <listitem><para>Redundant router capability. (v3.0.3 and greater) Available only when Virtual Router is selected as the Source NAT provider.  Select this option if you want to use two virtual routers in the network for uninterrupted connection: one operating as the master virtual router and the other as the backup. The master virtual router receives requests from and sends responses to the user’s VM. The backup virtual router is activated only when the master is down. After the failover, the backup becomes the master virtual router. CloudPlatform deploys the routers on different hosts to ensure reliability if one host is down.</para></listitem>
+            <listitem><para>Conserve mode.  Indicate whether to use conserve mode. In this mode, network resources are allocated only when the first virtual machine starts in the network</para></listitem>
+            <listitem><para>Tags.  Network tag to specify which physical network to use</para></listitem>
+        </itemizedlist></listitem> 
+        <listitem><para>Click Add.</para></listitem>        
+    </orderedlist>                
+    
+    
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/creating-new-volumes.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/creating-new-volumes.xml b/docs/en-US/creating-new-volumes.xml
new file mode 100644
index 0000000..71b4f9b
--- /dev/null
+++ b/docs/en-US/creating-new-volumes.xml
@@ -0,0 +1,23 @@
+<?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="creating-new-volumes">
+	<title>Creating a New Volume</title>
+	<para>You can add more data disk volumes to a guest VM at any time, up to the limits of your storage capacity. Both CloudPlatform administrators and users can add volumes to VM instances. When you create a new volume, it is stored as an entity in CloudPlatform, but the actual storage resources are not allocated on the physical storage device until you attach the volume. This optimization allows the CloudPlatform to provision the volume nearest to the guest that will use it when the first attachment is made.</para>
+				<orderedlist>
+				<listitem><para>Log in to the CloudPlatform UI as a user or admin.</para></listitem>
+				<listitem><para>In the left navigation bar, click Storage.</para></listitem>
+				<listitem><para>In Select View, choose Volumes.</para></listitem>
+				<listitem><para>To create a new volume, click Add Volume, provide the following details, and click OK.</para>
+				<itemizedlist>
+					<listitem><para>Name. Give the volume a unique name so you can find it later.</para></listitem>
+					<listitem><para>Availability Zone. Where do you want the storage to reside? This should be close to the VM that will use the volume.</para></listitem>
+					<listitem><para>Disk Offering. Choose the characteristics of the storage.</para></listitem>
+				</itemizedlist>
+				<para>The new volume appears in the list of volumes with the state “Allocated.” The volume data is stored in CloudPlatform, but the volume is not yet ready for use</para></listitem>
+				<listitem><para>To start using the volume, continue to Attaching a Volume </para></listitem>
+			</orderedlist>
+	</section>
+


Mime
View raw message