incubator-cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ke4...@apache.org
Subject [5/11] adding docs
Date Mon, 16 Jul 2012 19:44:04 GMT
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/ha-enabled-vm.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/ha-enabled-vm.xml b/docs/en-US/ha-enabled-vm.xml
new file mode 100644
index 0000000..63faa82
--- /dev/null
+++ b/docs/en-US/ha-enabled-vm.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="ha-enabled-vm">
+    <title>HA-Enabled Virtual Machines</title>
+    <para>The user can specify a virtual machine as HA-enabled. By default, all virtual router VMs and Elastic Load Balancing VMs are automatically configured as HA-enabled. When an HA-enabled VM crashes, CloudPlatform detects the crash and restarts the VM automatically within the same Availability Zone. HA is never performed across different Availability Zones. CloudPlatform has a conservative policy towards restarting VMs and ensures that there will never be two instances of the same VM running at the same time. The Management Server attempts to start the VM on another Host in the same cluster.</para>
+    <para>HA features work with iSCSI or NFS primary storage.  HA with local storage is not supported.</para>
+    </section>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/ha-for-hosts.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/ha-for-hosts.xml b/docs/en-US/ha-for-hosts.xml
new file mode 100644
index 0000000..f555c3e
--- /dev/null
+++ b/docs/en-US/ha-for-hosts.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="ha-for-hosts">
+    <title>HA for Hosts</title>
+    <para>The user can specify a virtual machine as HA-enabled. By default, all virtual router VMs and Elastic Load Balancing VMs are automatically configured as HA-enabled. When an HA-enabled VM crashes, CloudPlatform detects the crash and restarts the VM automatically within the same Availability Zone. HA is never performed across different Availability Zones. CloudPlatform has a conservative policy towards restarting VMs and ensures that there will never be two instances of the same VM running at the same time. The Management Server attempts to start the VM on another Host in the same cluster.</para>
+    <para>HA features work with iSCSI or NFS primary storage.  HA with local storage is not supported.</para>
+    </section>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/ha-management-server.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/ha-management-server.xml b/docs/en-US/ha-management-server.xml
new file mode 100644
index 0000000..27019cc
--- /dev/null
+++ b/docs/en-US/ha-management-server.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="ha-management-server">
+    <title>HA for Management Server</title>
+    <para>The CloudPlatform Management Server should be deployed in a multi-node configuration such that it is not susceptible to individual server failures. The Management Server itself (as distinct from the MySQL database) is stateless and may be placed behind a load balancer.</para>
+    <para>Normal operation of Hosts is not impacted by an outage of all Management Serves. All guest VMs will continue to work.</para>
+    <para>When the Management Server is down, no new VMs can be created, and the end user and admin UI, API, dynamic load distribution, and HA will cease to work.</para>
+   </section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/host-add.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/host-add.xml b/docs/en-US/host-add.xml
new file mode 100644
index 0000000..7591ee5
--- /dev/null
+++ b/docs/en-US/host-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="host-add">
+	<title>Adding a Host</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/host-allocation.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/host-allocation.xml b/docs/en-US/host-allocation.xml
new file mode 100644
index 0000000..8a56322
--- /dev/null
+++ b/docs/en-US/host-allocation.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="host-allocation">
+    <title>Host Allocation</title>
+    <para>The system automatically picks the most appropriate host to run each virtual machine. End users may specify the zone in which the virtual machine will be created. End users do not have control over which host will run the virtual machine instance.</para>
+    <para>CloudPlatform administrators can specify that certain hosts should have a preference for particular types of guest instances. For example, an administrator could state that a host should have a preference to run Windows guests. The default host allocator will attempt to place guests of that OS type on such hosts first. If no such host is available, the allocator will place the instance wherever there is sufficient physical capacity.</para>
+    <para>Both vertical and horizontal allocation is allowed. Vertical allocation consumes all the resources of a given host before allocating any guests on a second host. This reduces power consumption in the cloud. Horizontal allocation places a guest on each host in a round-robin fashion. This may yield better performance to the guests in some cases. CloudPlatform also allows an element of CPU over-provisioning as configured by the administrator. Over-provisioning allows the administrator to commit more CPU cycles to the allocated guests than are actually available from the hardware.</para>
+    <para>CloudPlatform also provides a pluggable interface for adding new allocators. These custom allocators can provide any policy the administrator desires.</para>
+</section>    
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/hypervisor-support-for-primarystorage.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/hypervisor-support-for-primarystorage.xml b/docs/en-US/hypervisor-support-for-primarystorage.xml
new file mode 100644
index 0000000..e0fa56b
--- /dev/null
+++ b/docs/en-US/hypervisor-support-for-primarystorage.xml
@@ -0,0 +1,83 @@
+<?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="hypervisor-support-for-primarystorage">
+	<title>Hypervisor Support for Primary Storage</title>
+	<para>The following table shows storage options and parameters for different hypervisors.</para>
+	<informaltable>
+		<tgroup cols="5">
+			<colspec colname="c1" colnum="1" colwidth="4.0cm"/>
+			<colspec colname="c2" colnum="2" colwidth="4cm" />
+			<colspec colname="c3" colnum="3" colwidth="5cm" />
+			<colspec colname="c4" colnum="2" colwidth="5.9cm"/>
+			<colspec colname="c5" colnum="3" colwidth="5.0cm"/>
+			<colspec colnum="4" colname="c4" colwidth="120.75pt"/>
+			<colspec colnum="5" colname="c5" colwidth="80.25pt"/>
+			<thead>
+				<row>
+					<entry></entry>
+					<entry><para>VMware vSphere</para></entry>
+					<entry><para>Citrix XenServer</para></entry>
+					<entry><para>KVM</para></entry>
+					<entry><para>Oracle VM</para></entry>
+				</row>
+			</thead>
+			<tbody>
+				<row>
+					<entry><para><emphasis role="bold"><emphasis role="bold">Format for Disks, Templates, and
+									Snapshots</emphasis></emphasis></para></entry>
+					<entry><para>VMDK</para></entry>
+					<entry><para>VHD</para></entry>
+					<entry><para>QCOW2</para></entry>
+					<entry><para>RAW</para></entry>
+				</row>
+				<row>
+					<entry><para><emphasis role="bold">iSCSI support</emphasis></para></entry>
+					<entry><para>VMFS</para></entry>
+					<entry><para>Clustered LVM</para></entry>
+					<entry><para>Yes, via Shared Mountpoint</para></entry>
+					<entry><para>Yes, via OCFS2M</para></entry>
+				</row>
+				<row>
+					<entry><para><emphasis role="bold">Fiber Channel support</emphasis></para></entry>
+					<entry><para>VMFS</para></entry>
+					<entry><para>Yes, via Existing SR</para></entry>
+					<entry><para>Yes, via Shared Mountpoint</para></entry>
+					<entry><para>No</para></entry>
+				</row>
+				<row>
+					<entry><para><emphasis role="bold">NFS support</emphasis></para></entry>
+					<entry><para>Y</para></entry>
+					<entry><para>Y</para></entry>
+					<entry><para>Y</para></entry>
+					<entry><para>Y</para></entry>
+				</row>
+				
+				<row>
+					<entry><para><emphasis role="bold">Local storage support</emphasis></para></entry>
+					<entry><para>Y</para></entry>
+					<entry><para>Y</para></entry>
+					<entry><para>Y</para></entry>
+					<entry><para>Y</para></entry>
+				</row>
+				
+				<row>
+					<entry><para><emphasis role="bold">Storage over-provisioning</emphasis></para></entry>
+					<entry><para>NFS and iSCSI</para></entry>
+					<entry><para>NFS</para></entry>
+					<entry><para>NFS</para></entry>
+					<entry><para>No</para></entry>
+				</row>
+					
+			</tbody>
+		</tgroup>
+	</informaltable>
+	<para>XenServer uses a clustered LVM system to store VM images on iSCSI and Fiber Channel volumes and does not support over-provisioning in the hypervisor. The storage server itself, however, can support thin-provisioning.  As a result the CloudPlatform can still support storage over-provisioning by running on thin-provisioned storage volumes.</para>
+	<para>KVM supports "Shared Mountpoint" storage.  A shared mountpoint is a file system path local to each server in a given cluster.  The path must be the same across all Hosts in the cluster, for example /mnt/primary1.  This shared mountpoint is assumed to be a clustered filesystem such as OCFS2.  In this case the CloudPlatform does not attempt to mount or unmount the storage as is done with NFS.  The CloudPlatform requires that the administrator insure that the storage is available</para>
+	<para>Oracle VM supports both iSCSI and NFS storage. When iSCSI is used with OVM, the CloudPlatform administrator is responsible for setting up iSCSI on the host, including re-mounting the storage after the host recovers from a failure such as a network outage. With other hypervisors, CloudPlatform takes care of mounting the iSCSI target on the host whenever it discovers a connection with an iSCSI server and unmounting the target when it discovers the connection is down.</para>
+	<para>With NFS storage, CloudPlatform manages the overprovisioning. In this case the global configuration parameter storage.overprovisioning.factor controls the degree of overprovisioning. This is independent of hypervisor type.</para>
+	<para>Local storage is an option for primary storage for vSphere, XenServer, Oracle VM, and KVM. When the local disk option is enabled, a local disk storage pool is automatically created on each host. To use local storage for the System Virtual Machines (such as the Virtual Router), set system.vm.use.local.storage to true in global configuration.</para>
+	<para>CloudPlatform supports multiple primary storage pools in a Cluster. For example, you could provision 2 NFS servers in primary storage. Or you could provision 1 iSCSI LUN initially and then add a second iSCSI LUN when the first approaches capacity.</para>
+	</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/1000-foot-view.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/1000-foot-view.png b/docs/en-US/images/1000-foot-view.png
new file mode 100644
index 0000000..2fe3c16
Binary files /dev/null and b/docs/en-US/images/1000-foot-view.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/attach-disk-icon.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/attach-disk-icon.png b/docs/en-US/images/attach-disk-icon.png
new file mode 100644
index 0000000..5e81d04
Binary files /dev/null and b/docs/en-US/images/attach-disk-icon.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/basic-deployment.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/basic-deployment.png b/docs/en-US/images/basic-deployment.png
new file mode 100644
index 0000000..894a053
Binary files /dev/null and b/docs/en-US/images/basic-deployment.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/change-password.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/change-password.png b/docs/en-US/images/change-password.png
new file mode 100644
index 0000000..fbb203a
Binary files /dev/null and b/docs/en-US/images/change-password.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/change-service-icon.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/change-service-icon.png b/docs/en-US/images/change-service-icon.png
new file mode 100644
index 0000000..780e235
Binary files /dev/null and b/docs/en-US/images/change-service-icon.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/destroy-instance.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/destroy-instance.png b/docs/en-US/images/destroy-instance.png
new file mode 100644
index 0000000..aa9846c
Binary files /dev/null and b/docs/en-US/images/destroy-instance.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/detach-disk-icon.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/detach-disk-icon.png b/docs/en-US/images/detach-disk-icon.png
new file mode 100644
index 0000000..536a4f8
Binary files /dev/null and b/docs/en-US/images/detach-disk-icon.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/edit-icon.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/edit-icon.png b/docs/en-US/images/edit-icon.png
new file mode 100644
index 0000000..42417e2
Binary files /dev/null and b/docs/en-US/images/edit-icon.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/http-access.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/http-access.png b/docs/en-US/images/http-access.png
new file mode 100644
index 0000000..817f197
Binary files /dev/null and b/docs/en-US/images/http-access.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/infrastructure-overview.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/infrastructure-overview.png b/docs/en-US/images/infrastructure-overview.png
new file mode 100644
index 0000000..24aeecf
Binary files /dev/null and b/docs/en-US/images/infrastructure-overview.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/installation-complete.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/installation-complete.png b/docs/en-US/images/installation-complete.png
new file mode 100644
index 0000000..4626f86
Binary files /dev/null and b/docs/en-US/images/installation-complete.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/migrate-instance.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/migrate-instance.png b/docs/en-US/images/migrate-instance.png
new file mode 100644
index 0000000..25ff572
Binary files /dev/null and b/docs/en-US/images/migrate-instance.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/provisioning-overview.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/provisioning-overview.png b/docs/en-US/images/provisioning-overview.png
new file mode 100644
index 0000000..25cc97e
Binary files /dev/null and b/docs/en-US/images/provisioning-overview.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/release-ip-icon.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/release-ip-icon.png b/docs/en-US/images/release-ip-icon.png
new file mode 100644
index 0000000..aa9846c
Binary files /dev/null and b/docs/en-US/images/release-ip-icon.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/images/stop-instance-icon.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/stop-instance-icon.png b/docs/en-US/images/stop-instance-icon.png
new file mode 100644
index 0000000..209afce
Binary files /dev/null and b/docs/en-US/images/stop-instance-icon.png differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/import-ami.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/import-ami.xml b/docs/en-US/import-ami.xml
new file mode 100644
index 0000000..ad3a74e
--- /dev/null
+++ b/docs/en-US/import-ami.xml
@@ -0,0 +1,93 @@
+<?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="import-ami">
+	<title>Importing Amazon Machine Images</title>
+	<para>The following procedures describe how to import an Amazon Machine Image (AMI) into CloudPlatform when using the XenServer hypervisor.</para>
+	<para>Assume you have an AMI file and this file is called CentOS_6.2_x64. Assume further that you are working on a CentOS host. If the AMI is a Fedora image, you need to be working on a Fedora host initially.</para>
+	<para>You need to have a XenServer host with a file-based storage repository (either a local ext3 SR or an NFS SR) to convert to a VHD once the image file has been customized on the Centos/Fedora host.</para>
+	<note><para>When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text.</para></note>
+	<orderedlist>
+		<listitem><para>Set up loopback on image file:</para><programlisting># mkdir -p /mnt/loop/centos62
+# mount -o loop  CentOS_6.2_x64 /mnt/loop/centos54
+</programlisting></listitem>
+		<listitem><para>Install the kernel-xen package into the image. This downloads the PV kernel and ramdisk to the image.</para><programlisting># yum -c /mnt/loop/centos54/etc/yum.conf --installroot=/mnt/loop/centos62/ -y install kernel-xen</programlisting></listitem>
+		<listitem><para>Create a grub entry in /boot/grub/grub.conf.</para><programlisting># mkdir -p /mnt/loop/centos62/boot/grub
+# touch /mnt/loop/centos62/boot/grub/grub.conf
+# echo "" > /mnt/loop/centos62/boot/grub/grub.conf
+</programlisting></listitem>
+		<listitem><para>Determine the name of the PV kernel that has been installed into the image.</para>
+			<programlisting># cd /mnt/loop/centos62
+# ls lib/modules/
+2.6.16.33-xenU  2.6.16-xenU  2.6.18-164.15.1.el5xen  2.6.18-164.6.1.el5.centos.plus  2.6.18-xenU-ec2-v1.0  2.6.21.7-2.fc8xen  2.6.31-302-ec2
+# ls boot/initrd*
+boot/initrd-2.6.18-164.6.1.el5.centos.plus.img boot/initrd-2.6.18-164.15.1.el5xen.img
+# ls boot/vmlinuz*
+boot/vmlinuz-2.6.18-164.15.1.el5xen  boot/vmlinuz-2.6.18-164.6.1.el5.centos.plus  boot/vmlinuz-2.6.18-xenU-ec2-v1.0  boot/vmlinuz-2.6.21-2952.fc8xen
+			</programlisting>
+			<para>Xen kernels/ramdisk always end with "xen". For the kernel version you choose, there has to be an entry for that version under lib/modules, there has to be an initrd and vmlinuz corresponding to that. Above, the only kernel that satisfies this condition is 2.6.18-164.15.1.el5xen.</para></listitem>
+		<listitem><para>Based on your findings, create an entry in the grub.conf file. Below is an example entry.</para><programlisting>default=0
+timeout=5
+hiddenmenu
+title CentOS (2.6.18-164.15.1.el5xen)
+        root (hd0,0)
+        kernel /boot/vmlinuz-2.6.18-164.15.1.el5xen ro root=/dev/xvda 
+        initrd /boot/initrd-2.6.18-164.15.1.el5xen.img
+</programlisting></listitem>
+		<listitem><para>Edit etc/fstab, changing “sda1” to “xvda” and changing “sdb” to “xvdb”.</para>
+		<programlisting># cat etc/fstab
+/dev/xvda  /         ext3    defaults        1 1
+/dev/xvdb  /mnt      ext3    defaults        0 0
+none       /dev/pts  devpts  gid=5,mode=620  0 0
+none       /proc     proc    defaults        0 0
+none       /sys      sysfs   defaults        0 0
+</programlisting></listitem>
+		<listitem><para>Enable login via the console. The default console device in a XenServer system is xvc0.  Ensure that etc/inittab and etc/securetty have the following lines respectively:</para>
+		<programlisting># grep xvc0 etc/inittab 
+co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav
+# grep xvc0 etc/securetty 
+xvc0
+</programlisting></listitem>
+		<listitem><para>Ensure the ramdisk supports PV disk and PV network. Customize this for the kernel version you have determined above.</para>
+		<programlisting># chroot /mnt/loop/centos54
+# cd /boot/
+# mv initrd-2.6.18-164.15.1.el5xen.img initrd-2.6.18-164.15.1.el5xen.img.bak
+# mkinitrd -f /boot/initrd-2.6.18-164.15.1.el5xen.img --with=xennet --preload=xenblk --omit-scsi-modules 2.6.18-164.15.1.el5xen
+</programlisting></listitem>
+		<listitem><para>Change the password.</para>
+			<programlisting># passwd
+Changing password for user root.
+New UNIX password: 
+Retype new UNIX password: 
+passwd: all authentication tokens updated successfully.
+</programlisting></listitem>
+		<listitem><para>Exit out of chroot.</para><programlisting># exit</programlisting></listitem>
+		<listitem><para>Check etc/ssh/sshd_config for lines allowing ssh login using a password.</para>
+		<programlisting># egrep "PermitRootLogin|PasswordAuthentication" /mnt/loop/centos54/etc/ssh/sshd_config  
+PermitRootLogin yes
+PasswordAuthentication yes
+</programlisting></listitem>
+		<listitem><para>If you need the template to be enabled to reset passwords from the CloudPlatform UI or API,
+                                install the password change script into the image at this point. See
+		        <xref linkend="add-password-management-to-templates"/>.</para></listitem>
+		<listitem><para>Unmount and delete loopback mount.</para><programlisting># umount /mnt/loop/centos54
+# losetup -d /dev/loop0
+</programlisting></listitem>
+		<listitem><para>Copy the image file to your XenServer host's file-based storage repository. In the example below, the Xenserver is "xenhost". This XenServer has an NFS repository whose uuid is a9c5b8c8-536b-a193-a6dc-51af3e5ff799.</para>
+		<programlisting># scp CentOS_6.2_x64 xenhost:/var/run/sr-mount/a9c5b8c8-536b-a193-a6dc-51af3e5ff799/</programlisting></listitem>
+		<listitem><para>Log in to the Xenserver and create a VDI the same size as the image.</para>
+		<programlisting>[root@xenhost ~]# cd /var/run/sr-mount/a9c5b8c8-536b-a193-a6dc-51af3e5ff799
+[root@xenhost a9c5b8c8-536b-a193-a6dc-51af3e5ff799]#  ls -lh CentOS_6.2_x64
+-rw-r--r-- 1 root root 10G Mar 16 16:49 CentOS_6.2_x64
+[root@xenhost a9c5b8c8-536b-a193-a6dc-51af3e5ff799]# xe vdi-create virtual-size=10GiB sr-uuid=a9c5b8c8-536b-a193-a6dc-51af3e5ff799 type=user name-label="Centos 6.2 x86_64"
+cad7317c-258b-4ef7-b207-cdf0283a7923
+</programlisting></listitem>
+		<listitem><para>Import the image file into the VDI. This may take 10–20 minutes.</para><programlisting>[root@xenhost a9c5b8c8-536b-a193-a6dc-51af3e5ff799]# xe vdi-import filename=CentOS_6.2_x64 uuid=cad7317c-258b-4ef7-b207-cdf0283a7923</programlisting></listitem>
+		<listitem><para>Locate a the VHD file.  This is the file with the VDI’s UUID as its name. Compress it and upload it to your web server.</para>
+		<programlisting>[root@xenhost a9c5b8c8-536b-a193-a6dc-51af3e5ff799]# bzip2 -c cad7317c-258b-4ef7-b207-cdf0283a7923.vhd > CentOS_6.2_x64.vhd.bz2
+[root@xenhost a9c5b8c8-536b-a193-a6dc-51af3e5ff799]# scp CentOS_6.2_x64.vhd.bz2 webserver:/var/www/html/templates/
+</programlisting></listitem>
+	</orderedlist>
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/increase-management-server-max-memory.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/increase-management-server-max-memory.xml b/docs/en-US/increase-management-server-max-memory.xml
new file mode 100644
index 0000000..d4ac196
--- /dev/null
+++ b/docs/en-US/increase-management-server-max-memory.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="increase-management-server-max-memory">
+    <title>Increase Management Server Maximum Memory</title>
+    <para>If the Management Server is subject to high demand, the default maximum JVM memory allocation can be insufficient. To increase the memory:</para>
+    <orderedlist>
+        <listitem><para>Edit the Tomcat configuration file:</para><programlisting>/etc/cloud/management/tomcat6.conf</programlisting></listitem>
+        <listitem><para>Change the command-line parameter -XmxNNNm to a higher value of N.</para><para>For example, if the current value is -Xmx128m, change it to -Xmx1024m or higher.</para></listitem>
+        <listitem><para>To put the new setting into effect, restart the Management Server.</para><programlisting># service cloud-management restart</programlisting></listitem>
+      </orderedlist>
+    <para>For more information about memory issues, see "FAQ: Memory" at <ulink url="http://wiki.apache.org/tomcat/FAQ/Memory">Tomcat Wiki.</ulink></para>
+</section>
+      

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/incremental-snapshots-backup.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/incremental-snapshots-backup.xml b/docs/en-US/incremental-snapshots-backup.xml
new file mode 100644
index 0000000..db6de2f
--- /dev/null
+++ b/docs/en-US/incremental-snapshots-backup.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="incremental-snapshots-backup">
+	<title>Incremental Snapshots and Backup </title>
+	<para>Snapshots are created on primary storage where a disk resides. After a snapshot is created, it is immediately backed up to secondary storage and removed from primary storage for optimal utilization of space on primary storage.</para>
+	<para>CloudPlatform does incremental backups for some hypervisors. When incremental backups are supported, every N backup is a full backup.</para>
+	<informaltable>
+		<tgroup cols="4" align="left" colsep="1" rowsep="1">
+			
+			<thead>
+				<row>
+					<entry></entry>
+					<entry><para>VMware vSphere</para></entry>
+					<entry><para>Citrix XenServer</para></entry>
+					<entry><para>KVM</para></entry>
+				</row>									
+			</thead>
+			<tbody>
+				<row>
+					<entry><para>Support incremental backup</para></entry>
+					<entry><para>N</para></entry>
+					<entry><para>Y</para></entry>
+					<entry><para>N</para></entry>
+				</row>
+			</tbody>
+		</tgroup>
+	</informaltable>
+	
+	</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/initial-setup-of-external-firewalls-loadbalancers.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/initial-setup-of-external-firewalls-loadbalancers.xml b/docs/en-US/initial-setup-of-external-firewalls-loadbalancers.xml
new file mode 100644
index 0000000..8cfdb6a
--- /dev/null
+++ b/docs/en-US/initial-setup-of-external-firewalls-loadbalancers.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="initial-setup-of-external-firewalls-loadbalancer">
+    <title>Initial Setup of External Firewalls and Load Balancers</title>
+    <para>When the first VM is created for a new account, CloudPlatform programs the external firewall and load balancer to work with the VM. The following objects are created on the firewall:</para>
+    <itemizedlist>
+        <listitem><para>A new logical interface to connect to the account's private VLAN. The interface IP is always the first IP of the account's private subnet (e.g. 10.1.1.1). </para></listitem>
+        <listitem><para>A source NAT rule that forwards all outgoing traffic from the account's private VLAN to the public Internet, using the account's public IP address as the source address</para></listitem>
+        <listitem><para>A firewall filter counter that measures the number of bytes of outgoing traffic for the account</para></listitem>
+    </itemizedlist>
+    <para>The following objects are created on the load balancer:</para>
+    <itemizedlist>        
+        <listitem><para>A new VLAN that matches the account's provisioned Zone VLAN</para></listitem>
+        <listitem><para>A self IP for the VLAN. This is always the second IP of the account's private subnet (e.g. 10.1.1.2).</para></listitem>
+      </itemizedlist>   				
+	</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/initialize-and-test.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/initialize-and-test.xml b/docs/en-US/initialize-and-test.xml
new file mode 100644
index 0000000..ed251a7
--- /dev/null
+++ b/docs/en-US/initialize-and-test.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="initialize-and-test">
+	<title>Initialize and Test</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/install-database-on-management-server-node.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/install-database-on-management-server-node.xml b/docs/en-US/install-database-on-management-server-node.xml
new file mode 100644
index 0000000..e80f09c
--- /dev/null
+++ b/docs/en-US/install-database-on-management-server-node.xml
@@ -0,0 +1,82 @@
+<?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="install-database-on-management-server-node">
+	<title>Install the Database on the Management Server Node</title>
+	<para>This section describes how to install MySQL on the same machine with the Management Server.
+		This technique is intended for a simple deployment that has a single Management Server node.
+		If you have a multi-node Management Server deployment, you will typically use a separate node for MySQL.
+		See <xref linkend="install-database-on-separate-node" />.
+	</para>
+	<orderedlist>
+		<listitem><para>If you already have a version of MySQL installed on the Management Server node, make one of the following choices, depending on what version of MySQL it is. The most recent version tested is 5.1.58.</para>
+			<itemizedlist>
+				<listitem><para>If you already have installed MySQL version 5.1.58 or later, skip to step 4.</para>
+				</listitem>
+				<listitem><para>If you have installed a version of MySQL earlier than 5.1.58, you can either skip to step 4 or uninstall MySQL and proceed to step 2 to install a more recent version.</para></listitem>
+			</itemizedlist>
+			<warning><para>It is important that you choose the right database version. Never downgrade a MySQL installation.</para></warning>
+		</listitem>
+		<listitem><para>On the same computer where you installed the Management Server, re-run install.sh.</para>
+			<programlisting># ./install.sh</programlisting>
+			<para>You should see a few messages as the installer prepares, followed by a list of choices.</para>
+		</listitem>
+		<listitem><para>Choose D to install the MySQL server from the distribution’s repo.</para>
+			<programlisting>  > D</programlisting>
+			<para>Troubleshooting: If you do not see the D option, you already have MySQL installed. Please go back to step 1.</para>
+		</listitem>
+		<listitem><para>Edit the MySQL configuration (/etc/my.cnf or /etc/mysql/my.cnf, depending on your OS) and insert the following lines in the [mysqld] section. You can put these lines below the datadir line. The max_connections parameter should be set to 350 multiplied by the number of Management Servers you are deploying. This example assumes one Management Server.</para>
+			<programlisting>
+innodb_rollback_on_timeout=1
+innodb_lock_wait_timeout=600
+max_connections=350
+log-bin=mysql-bin
+binlog-format = 'ROW'
+			</programlisting>
+			<note><para>The binlog-format variable is supported in MySQL versions 5.1 and greater. It is not supported in MySQL 5.0. In some versions of MySQL, an underscore character is used in place of the hyphen in the variable name. For the exact syntax and spelling of each variable, consult the documentation for your version of MySQL.</para></note>
+		</listitem>
+		<listitem><para>Restart the MySQL service, then invoke MySQL as the root user.</para>
+			<programlisting>
+# service mysqld restart
+# mysql -u root
+			</programlisting>
+		</listitem>
+		<listitem><para>Best Practice: On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly recommended that you set a root password as a security precaution. Run the following commands, and substitute your own desired root password.</para>
+		<programlisting>mysql> SET PASSWORD = PASSWORD('password');</programlisting>
+			<para>From now on, start MySQL with mysql -p so it will prompt you for the password.</para>
+		</listitem>
+		<listitem><para>To grant access privileges to remote users, perform the following steps.</para>
+			<orderedlist numeration="loweralpha">
+				<listitem><para>Run the following commands from the mysql prompt:</para>
+					<programlisting>
+mysql> GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' WITH GRANT OPTION; 
+mysql> exit
+					</programlisting>
+				</listitem>
+				<listitem><para>Restart the MySQL service.</para>
+					<programlisting># service mysqld restart</programlisting></listitem>
+				<listitem><para>Open the MySQL server port (3306) in the firewall to allow remote clients to connect.</para>
+					<programlisting># iptables -I INPUT -p tcp --dport 3306 -j ACCEPT</programlisting></listitem>
+				<listitem><para>Edit the /etc/sysconfig/iptables file and add the following line at the beginning of the INPUT chain.</para>
+					<programlisting> -A INPUT -p tcp --dport 3306 -j ACCEPT</programlisting></listitem>
+			</orderedlist>
+		</listitem>
+		<listitem><para>Set up the database. The following command creates the cloud user on the database.</para>
+			<itemizedlist>
+				<listitem><para>In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.</para></listitem>
+				<listitem><para>In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.</para></listitem>
+				<listitem><para>(Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption.</para></listitem>
+				<listitem><para>(Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the &PRODUCT; properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption.</para></listitem>
+				<listitem><para>(Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the &PRODUCT; database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption.</para></listitem>
+			</itemizedlist>
+			<programlisting># cloud-setup-databases cloud:&lt;dbpassword&gt;@localhost --deploy-as=root:&lt;password&gt; -e &lt;encryption_type&gt; -m &lt;management_server_key&gt; -k &lt;database_key&gt;</programlisting>
+			<para>When this script is finished, you should see a message like “Successfully initialized the database.”</para>
+		</listitem>
+		<listitem><para>Now that the database is set up, you can finish configuring the OS for the Management Server. This command will set up iptables, sudoers, and start the Management Server.</para>
+			<programlisting># cloud-setup-management</programlisting>
+			<para>You should see the message “Management Server setup is done.”</para>
+		</listitem>
+	</orderedlist>
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/install-database-on-separate-node.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/install-database-on-separate-node.xml b/docs/en-US/install-database-on-separate-node.xml
new file mode 100644
index 0000000..4dc10ba
--- /dev/null
+++ b/docs/en-US/install-database-on-separate-node.xml
@@ -0,0 +1,86 @@
+<?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="install-database-on-separate-node">
+	<title>Install the Database on a Separate Node</title>
+	<para>This section describes how to install MySQL on a standalone machine, separate from the Management Server.
+		This technique is intended for a deployment that includes several Management Server nodes.
+		If you have a single-node Management Server deployment, you will typically use the same node for MySQL.
+		See <xref linkend="install-database-on-management-server-node"/>.
+	</para>
+	<orderedlist>
+		<listitem><para>If you already have a version of MySQL installed on the Management Server node, make one of the following choices, depending on what version of MySQL it is. The most recent version tested is 5.1.58.</para>
+			<itemizedlist>
+				<listitem><para>If you already have installed MySQL version 5.1.58 or later, skip to step 3.</para>
+				</listitem>
+				<listitem><para>If you have installed a version of MySQL earlier than 5.1.58, you can either skip to step 3 or uninstall MySQL and proceed to step 2 to install a more recent version.</para></listitem>
+			</itemizedlist>
+			<warning><para>It is important that you choose the right database version. Never downgrade a MySQL installation.</para></warning>
+		</listitem>
+		<listitem><para>Log in as root to your Database Node and run the following commands. If you are going to install a replica database, then log in to the master.</para>
+			<programlisting>
+# yum install mysql-server   
+# chkconfig --level 35 mysqld on
+			</programlisting>
+		</listitem>
+		<listitem><para>Edit the MySQL configuration (/etc/my.cnf or /etc/mysql/my.cnf, depending on your OS) 
+			and insert the following lines in the [mysqld] section. You can put these lines below the datadir 
+			line. The max_connections parameter should be set to 350 multiplied by the number of Management 
+			Servers you are deploying. This example assumes two Management Servers.</para>
+			<programlisting>
+innodb_rollback_on_timeout=1
+innodb_lock_wait_timeout=600
+max_connections=700
+log-bin=mysql-bin
+binlog-format = 'ROW'
+			</programlisting>
+			<note><para>The binlog-format variable is supported in MySQL versions 5.1 and greater. It is not supported in MySQL 5.0. In some versions of MySQL, an underscore character is used in place of the hyphen in the variable name. For the exact syntax and spelling of each variable, consult the documentation for your version of MySQL.</para></note>
+		</listitem>
+		<listitem><para>Restart the MySQL service, then invoke MySQL as the root user.</para>
+			<programlisting>
+# service mysqld restart
+# mysql -u root
+			</programlisting>
+		</listitem>
+		<listitem><para>Best Practice: On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly recommended that you set a root password as a security precaution. Run the following commands, and substitute your own desired root password.</para>
+			<programlisting>mysql> SET PASSWORD = PASSWORD('password');</programlisting>
+			<para>From now on, start MySQL with mysql -p so it will prompt you for the password.</para>
+		</listitem>
+		<listitem><para>To grant access privileges to remote users, perform the following steps.</para>
+			<orderedlist numeration="loweralpha">
+				<listitem><para>Run the following commands from the mysql prompt:</para>
+					<programlisting>
+mysql> GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' WITH GRANT OPTION; 
+mysql> exit
+					</programlisting>
+				</listitem>
+				<listitem><para>Restart the MySQL service.</para>
+					<programlisting># service mysqld restart</programlisting>
+				</listitem>
+				<listitem><para>Open the MySQL server port (3306) in the firewall to allow remote clients to connect.</para>
+					<programlisting># iptables -I INPUT -p tcp --dport 3306 -j ACCEPT</programlisting>
+				</listitem>
+				<listitem><para>Edit the /etc/sysconfig/iptables file and add the following line at the beginning of the INPUT chain.</para>
+					<programlisting> -A INPUT -p tcp --dport 3306 -j ACCEPT</programlisting>
+				</listitem>
+			</orderedlist>
+		</listitem>
+		<listitem><para>Set up the database. The following command creates the cloud user on the database.</para>
+			<itemizedlist>
+				<listitem><para>In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.</para></listitem>
+				<listitem><para>In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.</para></listitem>
+				<listitem><para>(Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption.</para></listitem>
+				<listitem><para>(Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the &PRODUCT; properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption.</para></listitem>
+				<listitem><para>(Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the &PRODUCT; database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption.</para></listitem>
+			</itemizedlist>
+			<programlisting># cloud-setup-databases cloud:&lt;dbpassword&gt;@localhost --deploy-as=root:&lt;password&gt; -e &lt;encryption_type&gt; -m &lt;management_server_key&gt; -k &lt;database_key&gt;</programlisting>
+			<para>When this script is finished, you should see a message like “Successfully initialized the database.”</para>
+		</listitem>
+		<listitem><para>Now that the database is set up, you can finish configuring the OS for the Management Server. This command will set up iptables, sudoers, and start the Management Server.</para>
+			<programlisting># cloud-setup-management</programlisting>
+			<para>You should see the message “Management Server setup is done.”</para>
+		</listitem>
+	</orderedlist>
+</section>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/install-management-server-multi-nodes.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/install-management-server-multi-nodes.xml b/docs/en-US/install-management-server-multi-nodes.xml
new file mode 100644
index 0000000..3efa4f6
--- /dev/null
+++ b/docs/en-US/install-management-server-multi-nodes.xml
@@ -0,0 +1,54 @@
+<?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="install-management-server-multi-nodes">
+	<title>Prepare and Start Additional Management Servers</title>
+	<para>For your second and subsequent Management Servers, you will install the Management Server software, connect it to the database, and set up the OS for the Management Server. 
+	</para>
+	<orderedlist>
+		<listitem><para>Perform the steps in <xref linkend="prepare-os"/>.</para>
+		</listitem>
+		<listitem><para>Download the Management Server onto the additional host where it will run. Get the software from the following link.</para>
+				<para><ulink url="https://www.citrix.com/English/ss/downloads/">https://www.citrix.com/English/ss/downloads/</ulink></para>
+				<para>You will need a <ulink url="http://www.citrix.com/lang/English/publicindex.asp?destURL=%2FEnglish%2FmyCitrix%2Findex.asp%3F">MyCitrix account</ulink>.</para>		
+		</listitem>
+		<listitem><para>Install the  packages. You should have a file in the form of “&PRODUCT;-VERSION-N-OSVERSION.tar.gz”. Untar the file and then run the install.sh script inside it. Replace the file and directory names below with those you are using:</para>
+			<programlisting>
+# tar xzf &PRODUCT;-VERSION-N-OSVERSION.tar.gz
+# cd &PRODUCT;-VERSION-N-OSVERSION
+# ./install.sh
+			</programlisting>
+			<para>You should see a few messages as the installer prepares, followed by a list of choices.</para>
+		</listitem>
+		<listitem><para>Choose M to install the Management Server software.</para>
+			<programlisting>  > M</programlisting>
+		</listitem>
+		<listitem><para>Wait for a message like “Complete! Done,” which indicates that the software was installed successfully.</para>
+		</listitem>
+		<listitem><para>(RHEL or CentOS) When the installation is finished, run the following commands to start essential services  (the commands might be different depending on your OS):</para>
+			<programlisting>
+# service rpcbind start
+# service nfs start
+# chkconfig nfs on
+# chkconfig rpcbind on
+			</programlisting>
+		</listitem>
+		<listitem><para>Configure the database client. Note the absence of the --deploy-as argument in this case.
+			(For more details about the arguments to this command, see <xref linkend="install-database-on-separate-node"/>.)
+		</para>
+			<programlisting># cloud-setup-databases cloud:&lt;dbpassword&gt;@&lt;dbhost&gt; -e &lt;encryption_type&gt; -m &lt;management_server_key&gt; -k &lt;database_key&gt;
+			</programlisting>
+		</listitem>
+		<listitem><para>(Trial installations only) If you are running the hypervisor on the same machine with the Management Server, edit /etc/sudoers and add the following line:</para>
+			<programlisting>Defaults:cloud !requiretty</programlisting>
+		</listitem>
+		<listitem><para>Configure the OS and start the Management Server:</para>
+			<programlisting># cloud-setup-management</programlisting>
+			<para>The Management Server on this node should now be running.</para>
+		</listitem>
+		<listitem><para>Repeat these steps on each additional Management Server. </para></listitem>
+		<listitem><para>Be sure to configure a load balancer for the Management Servers. See Management Server Load Balancing.</para></listitem>
+	</orderedlist>
+</section>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/install-management-server.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/install-management-server.xml b/docs/en-US/install-management-server.xml
new file mode 100644
index 0000000..bfe1283
--- /dev/null
+++ b/docs/en-US/install-management-server.xml
@@ -0,0 +1,41 @@
+<?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="install-management-server">
+	<title>Install the Management Server on the First Host</title>
+	<para>The first step in installation, whether you are installing the Management Server on one host or many, is to
+		install the software on a single node.
+	</para>
+	<note><para>If you are planning to install the Management Server on multiple nodes
+		for high availability, do not proceed to the additional nodes yet. That step will come later.</para></note>
+	<orderedlist>
+		<listitem><para>Download the Management Server onto the host where it will run.
+			Get the software from the following link.</para>
+			<para><ulink url="https://www.citrix.com/English/ss/downloads/">https://www.citrix.com/English/ss/downloads/</ulink></para>
+			<para>You will need a <ulink url="http://www.citrix.com/lang/English/publicindex.asp?destURL=%2FEnglish%2FmyCitrix%2Findex.asp%3F">MyCitrix account</ulink>.</para>
+		</listitem>
+		<listitem><para>Install the  packages. You should have a file in the form of “&PRODUCT;-VERSION-N-OSVERSION.tar.gz”. Untar the file and then run the install.sh script inside it. Replace the file and directory names below with those you are using:</para>
+			<programlisting>
+# tar xzf &PRODUCT;-VERSION-N-OSVERSION.tar.gz
+# cd &PRODUCT;-VERSION-N-OSVERSION
+# ./install.sh
+			</programlisting>
+			<para>You should see a few messages as the installer prepares, followed by a list of choices.</para>
+		</listitem>
+		<listitem><para>Choose M to install the Management Server software.</para>
+			<programlisting>  > M</programlisting>
+		</listitem>
+		<listitem><para>Wait for a message like “Complete! Done,” which indicates that the software was installed successfully.</para>
+		</listitem>
+		<listitem><para>(RHEL or CentOS) When the installation is finished, run the following commands to start essential services  (the commands might be different depending on your OS):</para>
+			<programlisting>
+# service rpcbind start
+# service nfs start
+# chkconfig nfs on
+# chkconfig rpcbind on
+			</programlisting>
+		</listitem>
+	</orderedlist>
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/installation-complete.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/installation-complete.xml b/docs/en-US/installation-complete.xml
new file mode 100644
index 0000000..62a069a
--- /dev/null
+++ b/docs/en-US/installation-complete.xml
@@ -0,0 +1,20 @@
+<?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="installation-complete">
+	<title>Installation Complete! Next Steps</title>
+	<para>Congratulations! You have now installed &PRODUCT; Management Server and the database it uses to persist system data.</para>
+	<mediaobject>
+		<imageobject>
+			<imagedata fileref="./images/installation-complete.png" />
+		</imageobject>
+		<textobject><phrase>installation-complete.png: Finished installs with single Management Server and multiple Management Servers</phrase></textobject>
+	</mediaobject>
+	<para>What should you do next?</para>
+	<itemizedlist>
+		<listitem><para>Even without adding any cloud infrastructure, you can run the UI to get a feel for what's offered and how you will interact with &PRODUCT; on an ongoing basis. See Log In to the UI.</para></listitem>
+		<listitem><para>When you're ready, add the cloud infrastructure and try running some virtual machines on it, so you can watch how &PRODUCT; manages the infrastructure. See Provision Your Cloud Infrastructure.</para></listitem>
+	</itemizedlist>
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/installation-steps-overview.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/installation-steps-overview.xml b/docs/en-US/installation-steps-overview.xml
new file mode 100644
index 0000000..9a95bfb
--- /dev/null
+++ b/docs/en-US/installation-steps-overview.xml
@@ -0,0 +1,64 @@
+<?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="installation-steps-overview">
+	<title>Overview of Installation Steps</title>
+	<para>
+		For anything more than a simple trial installation, you will need guidance for a variety of configuration choices. It is strongly recommended that you read the following:
+	</para>
+	<itemizedlist>
+		<listitem><para>Choosing a Deployment Architecture</para></listitem>
+		<listitem><para>Choosing a Hypervisor: Supported Features</para></listitem>
+		<listitem><para>Network Setup</para></listitem>
+		<listitem><para>Storage Setup</para></listitem>
+		<listitem><para>Best Practices</para></listitem>
+	</itemizedlist>
+	<para>
+		<emphasis role="bold">Prepare</emphasis>
+	</para>
+	<para>
+		1.	Make sure you have the required hardware ready
+	</para>
+	<para>
+		2.	(Optional) Fill out the preparation checklists
+	</para>
+	<para>
+		<emphasis role="bold">Install the &PRODUCT; software</emphasis>
+	</para>
+	<para>
+		3.	Install the Management Server (choose single-node or multi-node)
+	</para>
+	<para>
+		4.	Log in to the UI
+	</para>
+	<para>
+		<emphasis role="bold">Provision your cloud infrastructure</emphasis>
+	</para>
+	<para>
+		5.	Add a zone. Includes the first pod, cluster, and host
+	</para>
+	<para>
+		6.	Add more pods
+	</para>
+	<para>
+		7.	Add more clusters
+	</para>
+	<para>
+		8.	Add more hosts
+	</para>
+	<para>
+		9.	Add more primary storage
+	</para>
+	<para>
+		10.	Add more secondary storage
+	</para>
+	<para>
+		<emphasis role="bold">Try using the cloud</emphasis>
+	</para>
+	<para>
+		11.	Initialization and testing
+	</para>
+	
+</section>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/installation.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/installation.xml b/docs/en-US/installation.xml
new file mode 100644
index 0000000..6a003fe
--- /dev/null
+++ b/docs/en-US/installation.xml
@@ -0,0 +1,12 @@
+<?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="installation">
+	<title>Installation</title>
+	<xi:include href="who-should-read-installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+	<xi:include href="installation-steps-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+	<xi:include href="minimum-system-requirements.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+	<xi:include href="management-server-install-flow.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/installation_overview.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/installation_overview.xml b/docs/en-US/installation_overview.xml
new file mode 100644
index 0000000..6b743d2
--- /dev/null
+++ b/docs/en-US/installation_overview.xml
@@ -0,0 +1,14 @@
+<?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="installation_overview">
+	<title>Installation Overview</title>
+		<xi:include href="cloudstack_whatis.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+		<xi:include href="cloudstack_features.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+		<xi:include href="deployment_architecture_overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+		<xi:include href="installation_steps_overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+		<xi:include href="cloudstack_system_requirements.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/installation_steps_overview.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/installation_steps_overview.xml b/docs/en-US/installation_steps_overview.xml
new file mode 100644
index 0000000..a48cf51
--- /dev/null
+++ b/docs/en-US/installation_steps_overview.xml
@@ -0,0 +1,60 @@
+	<section id="installation_steps_overview">
+		<title>Overview of Installation Steps</title>
+		<para>
+			For anything more than a simple trial installation, you will need guidance for a variety of configuration choices. It is strongly recommended that you read the following:
+		</para>
+		<itemizedlist>
+			<listitem><para>Choosing a Deployment Architecture</para></listitem>
+			<listitem><para>Choosing a Hypervisor: Supported Features</para></listitem>
+			<listitem><para>Network Setup</para></listitem>
+			<listitem><para>Storage Setup</para></listitem>
+			<listitem><para>Best Practices</para></listitem>
+		</itemizedlist>
+		<para>
+			<emphasis role="bold">Prepare</emphasis>
+		</para>
+		<para>
+			1.	Make sure you have the required hardware ready
+		</para>
+		<para>
+			2.	(Optional) Fill out the preparation checklists
+		</para>
+		<para>
+			<emphasis role="bold">Install the CloudStack software</emphasis>
+		</para>
+		<para>
+			3.	Install the CloudStack Management Server (single-node, or multi-node)
+		</para>
+		<para>
+			4.	Log in to the CloudStack UI
+		</para>
+		<para>
+			<emphasis role="bold">Provision your cloud infrastructure</emphasis>
+		</para>
+		<para>
+			5.	Add a zone. Includes the first pod, cluster, and host
+		</para>
+		<para>
+			6.	Add more pods
+		</para>
+		<para>
+			7.	Add more clusters
+		</para>
+		<para>
+			8.	Add more hosts
+		</para>
+		<para>
+			9.	Add more primary storage
+		</para>
+		<para>
+			10.	Add more secondary storage
+		</para>
+		<para>
+			<emphasis role="bold">Try using the cloud</emphasis>
+		</para>
+		<para>
+			11.	Initialization and testing
+		</para>
+		
+	</section>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/introduction.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/introduction.xml b/docs/en-US/introduction.xml
new file mode 100644
index 0000000..9865360
--- /dev/null
+++ b/docs/en-US/introduction.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="introduction">
+	<title>Introduction</title>
+	<xi:include href="roles.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="api-reference.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+    <xi:include href="developer-getting-started.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/ip-forwarding-firewalling.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/ip-forwarding-firewalling.xml b/docs/en-US/ip-forwarding-firewalling.xml
new file mode 100644
index 0000000..6873fcb
--- /dev/null
+++ b/docs/en-US/ip-forwarding-firewalling.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="ip-forwarding-firewalling">
+    <title>IP Forwarding and Firewalling</title>
+    <para>By default, all incoming traffic to the public IP address is rejected. All outgoing traffic from the guests is translated via NAT to the public IP address and is allowed.</para>
+    <para>To allow incoming traffic, users may set up firewall rules and/or port forwarding rules. For example, you can use a firewall rule to open a range of ports on the public IP address, such as 33 through 44. Then use port forwarding rules to direct traffic from individual ports within that range to specific ports on user VMs. For example, one port forwarding rule could route incoming traffic on the public IP's port 33 to port 100 on one user VM's private IP.</para>
+    <para>For the steps to implement these rules, see Firewall Rules and Port Forwarding.</para>
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/ip-load-balancing.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/ip-load-balancing.xml b/docs/en-US/ip-load-balancing.xml
new file mode 100644
index 0000000..638e935
--- /dev/null
+++ b/docs/en-US/ip-load-balancing.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="ip-load-balancing">
+	<title>IP Load Balancing</title>
+	<para>The user may choose to associate the same public IP for multiple guests. CloudPlatform implements a TCP-level load balancer with the following policies.</para>
+	<itemizedlist>
+		<listitem><para>Round-robin</para></listitem>
+		<listitem><para>Least connection</para></listitem>
+		<listitem><para>Source IP</para></listitem>
+	</itemizedlist>
+	<para>This is similar to port forwarding but the destination may be multiple IP addresses.</para>
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/ipaddress-usage-record-format.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/ipaddress-usage-record-format.xml b/docs/en-US/ipaddress-usage-record-format.xml
new file mode 100644
index 0000000..609fbd6
--- /dev/null
+++ b/docs/en-US/ipaddress-usage-record-format.xml
@@ -0,0 +1,19 @@
+<section id="ipaddress-usage-record-format">
+	<title>IP Address Usage Record Format</title>
+	<para>For IP address usage the following fields exist in a usage record.</para>
+	<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</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 – IP address ID</para></listitem>
+			<listitem><para>startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record</para></listitem>
+			<listitem><para>issourcenat – Whether source NAT is enabled for the IP address</para></listitem>
+			<listitem><para>iselastic - True if the IP address is elastic.</para></listitem>
+		</itemizedlist>
+	</section>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/isolated-networks.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/isolated-networks.xml b/docs/en-US/isolated-networks.xml
new file mode 100644
index 0000000..a2e27ab
--- /dev/null
+++ b/docs/en-US/isolated-networks.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="isolated-networks">
+    <title>Isolated Networks</title>
+    <para>An isolated network can be accessed only by virtual machines of a single account. Isolated networks have the following properties.</para>
+    <itemizedlist>
+        <listitem><para>Resources such as VLAN are allocated and garbage collected dynamically</para></listitem>
+        <listitem><para>There is one network offering for the entire network</para></listitem>
+        <listitem><para>The network offering can be upgraded or downgraded but it is for the entire network</para></listitem>
+        </itemizedlist>
+    
+    
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/job-status.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/job-status.xml b/docs/en-US/job-status.xml
new file mode 100644
index 0000000..17d602e
--- /dev/null
+++ b/docs/en-US/job-status.xml
@@ -0,0 +1,10 @@
+<section id="job-status">
+		<title>Job Status</title>
+	<para>The key to using an asynchronous command is the job ID that is returned immediately once the command has been executed. With the job ID, you can periodically check the job status by making calls to queryAsyncJobResult command. The command will return three possible job status integer values:</para>
+		<itemizedlist>
+			<listitem><para>0 - Job is still in progress. Continue to periodically poll for any status changes.</para></listitem>
+			<listitem><para>1 - Job has successfully completed. The job will return any successful response values associated with command that was originally executed.</para></listitem>
+			<listitem><para>2 - Job has failed to complete.  Please check the "jobresultcode" tag for failure reason code and "jobresult" for the failure reason.</para></listitem>
+		</itemizedlist>
+	</section>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/linux-installation.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/linux-installation.xml b/docs/en-US/linux-installation.xml
new file mode 100644
index 0000000..5168d66
--- /dev/null
+++ b/docs/en-US/linux-installation.xml
@@ -0,0 +1,35 @@
+<?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="linux-installation">
+	<title>Linux OS Installation</title>
+	<para>Use the following steps to begin the Linux OS installation:</para>
+	<orderedlist>
+		<listitem><para>Download the script file cloud-set-guest-password:</para>
+		<itemizedlist>
+			<listitem><para>Linux: <ulink url="
+				http://cloudstack.org/dl/cloud-set-guest-password
+				"></ulink>				
+			</para></listitem>
+			<listitem><para>Windows: <ulink url="
+				http://sourceforge.net/projects/cloudstack/files/Password%20Management%20Scripts/CloudInstanceManager.msi/download
+				"></ulink>		
+			</para></listitem>
+		</itemizedlist>
+		</listitem>
+		<listitem><para>Copy this file to /etc/init.d.</para><para>On some Linux distributions, copy the file to /etc/rc.d/init.d.</para>
+			</listitem>
+		<listitem><para>Run the following command to make the script executable:</para><programlisting>chmod +x /etc/init.d/cloud-set-guest-password</programlisting>
+			</listitem>
+		<listitem><para>Depending on the Linux distribution, continue with the appropriate step.</para><para>On Fedora, CentOS/RHEL, and Debian, run:</para><programlisting>chkconfig --add cloud-set-guest-password</programlisting>
+			<para condition="community">On Ubuntu with VMware tools, link the script file to the /etc/network/if-up and
+				/etc/network/if-down folders, and run the script:</para>
+			<programlisting condition="community">#ln -s /etc/init.d/cloud-set-guest-password /etc/network/if-up/cloud-set-guest-password
+			#ln -s /etc/init.d/cloud-set-guest-password /etc/network/if-down/cloud-set-guest-password</programlisting>
+			<para condition="community">If you are using Ubuntu 11.04, start by creating a directory called /var/lib/dhcp3 on your Ubuntu machine (works around a known issue with this version of Ubuntu). On all Ubuntu versions: Run “sudo update-rc.d cloud-set-guest-password defaults 98”. To test, run "mkpasswd" and check that it is generating a new password. If the “mkpasswd” command does not exist, run "sudo apt-get install whois"  (or sudo apt-get install mkpasswd, depending on your Ubuntu version) and repeat.</para>
+			</listitem>
+	</orderedlist>
+	
+	</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/load-balancer-rules.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/load-balancer-rules.xml b/docs/en-US/load-balancer-rules.xml
new file mode 100644
index 0000000..6eb323a
--- /dev/null
+++ b/docs/en-US/load-balancer-rules.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="load-balancer-rules">
+    <title>Load Balancer Rules</title>
+    <para>A CloudPlatform user or administrator may create load balancing rules that balance traffic received at a public IP to one or more VMs. A user creates a rule, specifies an algorithm, and assigns the rule to a set of VMs.</para>
+    <note><para>If you create load balancing rules while using a network service offering that includes an external load balancer device such as NetScaler, and later change the network service offering to one that uses the CloudPlatform virtual router, you must create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function.</para></note>
+	</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/loadbalancer-policy-port-forwarding-rule-usage-record-format.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/loadbalancer-policy-port-forwarding-rule-usage-record-format.xml b/docs/en-US/loadbalancer-policy-port-forwarding-rule-usage-record-format.xml
new file mode 100644
index 0000000..1e724fd
--- /dev/null
+++ b/docs/en-US/loadbalancer-policy-port-forwarding-rule-usage-record-format.xml
@@ -0,0 +1,17 @@
+<section id="loadbalancer-policy-port-forwarding-rule-usage-record-format">
+	<title>Load Balancer Policy or Port Forwarding Rule 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 – ID of the load balancer policy or port forwarding rule</para></listitem>
+			<listitem><para>usagetype – A number representing the usage type (see Usage Types)</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>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/log-in-root-admin.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/log-in-root-admin.xml b/docs/en-US/log-in-root-admin.xml
new file mode 100644
index 0000000..f57e264
--- /dev/null
+++ b/docs/en-US/log-in-root-admin.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="log-in-root-admin">
+    <title>Logging In as the Root Administrator</title>
+    <para>After the Management Server software is installed and running, you can run the &PRODUCT; user interface. This UI is there to help you provision, view, and manage your cloud infrastructure.</para>
+    <orderedlist>
+        <listitem><para>Open your favorite Web browser and go to this URL. Substitute the IP address of your own Management Server:</para>
+            <programlisting>http://&lt;management-server-ip-address&gt;:8080/client</programlisting>
+            <para>On a fresh Management Server installation, a guided tour splash screen appears. On later visits, you’ll see a login screen where you can enter a user ID and password and proceed to your Dashboard.</para>
+        </listitem>
+        <listitem><para>If you see the first-time splash screen, choose one of the following.</para>
+            <itemizedlist>
+                <listitem><para><emphasis role="bold">Continue with basic setup.</emphasis> Choose this if you're just trying &PRODUCT;, and you want a guided walkthrough of the simplest possible configuration so that you can get started right away. We'll help you set up a cloud with the following features: a single machine that runs &PRODUCT; software and uses NFS to provide storage; a single machine running VMs under the XenServer or KVM hypervisor; and a shared public network.</para>
+                    <para>The prompts in this guided tour should give you all the information you need, but if you want just a bit more detail, you can follow along in the Trial Installation Guide.</para>
+                </listitem>
+                <listitem><para><emphasis role="bold">I have used &PRODUCT; before.</emphasis> Choose this if you have already gone through a design phase and planned a more sophisticated deployment, or you are ready to start scaling up a trial cloud that you set up earlier with the basic setup screens. In the Administrator UI, you can start using the more powerful features of CloudPlatform, such as advanced VLAN networking, high availability, additional network elements such as load balancers and firewalls, and support for multiple hypervisors including Citrix XenServer, KVM, and VMware vSphere.</para> 
+                    <para>The root administrator Dashboard appears.</para>
+                </listitem>
+            </itemizedlist>
+        </listitem>
+        <listitem><para>You should set a new root administrator password. If you chose basic setup, you’ll be prompted to create a new password right away. If you chose experienced user, use the steps in <xref linkend="changing-root-password" />.</para></listitem>
+    </orderedlist>
+    <warning><para>You are logging in as the root administrator. This account manages the &PRODUCT; deployment, including physical infrastructure. The root administrator can modify configuration settings to change basic functionality, create or delete user accounts, and take many actions that should be performed only by an authorized person. Please change the default password to a new, unique password.</para></warning>
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/log-in.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/log-in.xml b/docs/en-US/log-in.xml
new file mode 100644
index 0000000..385dedd
--- /dev/null
+++ b/docs/en-US/log-in.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="log-in">
+	<title>Log In to the UI</title>
+	<para>&PRODUCT; provides a web-based UI that can be used by both administrators and end users. The appropriate version of the UI is displayed depending on the credentials used to log in. The UI is available in popular browsers including IE7, IE8, IE9, Firefox 3.5+, Firefox 4, Safari 4, and Safari 5. The URL is: (substitute your own management server IP address)</para>
+	<programlisting>http://&lt;management-server-ip-address&gt;:8080/client</programlisting>
+    <para>On a fresh Management Server installation, a guided tour splash screen appears. On later visits, you’ll see a login screen where you specify the following to proceed to your Dashboard:</para>
+    <formalpara>
+        <title>Username</title>
+        <para>The user ID of your account. The default username is admin.</para>
+    </formalpara>
+    <formalpara>
+        <title>Password</title>
+        <para>The password associated with the user ID. The password for the default username is password.</para>
+    </formalpara>
+    <formalpara>
+        <title>Domain</title>
+        <para>If you are a root user, leave this field blank.</para>
+    </formalpara>
+    <para>If you are a user in the sub-domains, enter the full path to the domain, excluding the root domain.</para>
+    <para>For example, suppose multiple levels are created under the root domain, such as Comp1/hr. The users in the Comp1 domain should enter Comp1 in the Domain field, whereas the users in the Comp1/sales domain should enter Comp1/sales.</para>    
+    <para>For more guidance about the choices that appear when you log in to this UI, see Logging In as the Root Administrator.</para>
+	<xi:include href="end-user-ui-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="root-admin-ui-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="log-in-root-admin.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/long-running-job-events.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/long-running-job-events.xml b/docs/en-US/long-running-job-events.xml
new file mode 100644
index 0000000..577e1c2
--- /dev/null
+++ b/docs/en-US/long-running-job-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="long-running-job-events">
+    <title>Long Running Job 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/maintain-hypervisors-on-hosts.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/maintain-hypervisors-on-hosts.xml b/docs/en-US/maintain-hypervisors-on-hosts.xml
new file mode 100644
index 0000000..7d6bb0e
--- /dev/null
+++ b/docs/en-US/maintain-hypervisors-on-hosts.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="maintain-hypervisors-on-hosts">
+    <title>Maintaining Hypervisors on Hosts</title>
+    <para>When running hypervisor software on hosts, be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. CloudPlatform will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches.</para>
+    <note><para>The lack of up-do-date hotfixes can lead to data corruption and lost VMs.</para></note>
+    <para>(XenServer) For more information, see <ulink url="http://docs.cloudstack.org/Knowledge_Base/Possible_VM_corruption_if_XenServer_Hotfix_is_not_Applied/Highly_Recommended_Hotfixes_for_XenServer_5.6_SP2">Highly Recommended Hotfixes for XenServer in the CloudPlatform Knowledge Base</ulink></para>    
+</section>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/maintenance-mode-for-primary-storage.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/maintenance-mode-for-primary-storage.xml b/docs/en-US/maintenance-mode-for-primary-storage.xml
new file mode 100644
index 0000000..83cc245
--- /dev/null
+++ b/docs/en-US/maintenance-mode-for-primary-storage.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="maintenance-mode-for-primary-storage.xml">
+		<title>Maintenance Mode for Primary Storage</title>
+			<para>Primary storage may be placed into maintenance mode.  This is useful, for example, to replace faulty RAM in a storage device.  Maintenance mode for a storage device will first stop any new guests from being provisioned on the storage device.  Then it will stop all guests that have any volume on that storage device.  When all such guests are stopped the storage device is in maintenance mode and may be shut down.  When the storage device is online again you may cancel maintenance mode for the device.  The CloudPlatform will bring the device back online and attempt to start all guests that were running at the time of the entry into maintenance mode.</para>
+	</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/e874fdb2/docs/en-US/making-api-request.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/making-api-request.xml b/docs/en-US/making-api-request.xml
new file mode 100644
index 0000000..35ba460
--- /dev/null
+++ b/docs/en-US/making-api-request.xml
@@ -0,0 +1,36 @@
+<?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="making-api-request">
+		<title>Making API Requests</title>
+		<para>
+			All CloudStack API requests are submitted in the form of a HTTP GET/POST with an associated command and any parameters.  A request is composed of the following whether in HTTP or HTTPS:
+		</para>
+		<itemizedlist>
+			<listitem><para>CloudStack API URL: This is the web services API entry point(for example, http://www.cloud.com:8080/client/api)</para></listitem> 
+			<listitem><para>Command: The web services command you wish to execute, such as start a virtual machine or create a disk volume</para></listitem>
+			<listitem><para>Parameters: Any additional required or optional parameters for the command</para></listitem>
+		</itemizedlist>
+		<para>A sample API GET request looks like the following:</para>
+		<programlisting>http://localhost:8080/client/api?command=deployVirtualMachine&amp;serviceOfferingId=1&amp;diskOfferingId=1&amp;templateId=2&amp;zoneId=4&amp;apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&amp;signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D
+		</programlisting>
+		<para>Or in a more readable format:</para>
+		<programlisting>
+1. http://localhost:8080/client/api
+2. ?command=deployVirtualMachine
+3. &amp;serviceOfferingId=1
+4. &amp;diskOfferingId=1
+5. &amp;templateId=2
+6. &amp;zoneId=4
+7. &amp;apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXqjB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ
+8. &amp;signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D
+		</programlisting>
+		<para>The first line is the CloudStack API URL. This is the Cloud instance you wish to interact with.</para>
+		<para>The second line refers to the command you wish to execute.  In our example, we are attempting to deploy a fresh new virtual machine.  It is preceded by a (?) to separate itself from the CloudStack API URL.</para>
+		<para>Lines 3-6 are the parameters for this given command.  To see the command and its request parameters, please refer to the appropriate section in the CloudStack API documentation.  Each parameter field-value pair (field=value) is preceded by an ampersand character (&amp;).</para>
+		<para>Line 7 is the user API Key that uniquely identifies the account.  See Signing API Requests on page 7.</para>
+		<para>Line 8 is the signature hash created to authenticate the user account executing the API command.  See Signing API Requests on page 7.</para>			
+	</section>
+


Mime
View raw message