You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by jz...@apache.org on 2013/01/11 22:02:58 UTC

[16/52] [partial] CLOUDSTACK-961: Added dependencies for building RPMs.

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/globally-configured-limits.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/globally-configured-limits.xml b/docs/tmp/en-US/xml/globally-configured-limits.xml
new file mode 100644
index 0000000..9efde22
--- /dev/null
+++ b/docs/tmp/en-US/xml/globally-configured-limits.xml
@@ -0,0 +1,216 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="globally-configured-limit" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Globally Configured Limits</title>
+	 <para>
+		In a zone, the guest virtual network has a 24 bit CIDR by default. This limits the guest virtual network to 254 running instances. It can be adjusted as needed, but this must be done before any instances are created in the zone. For example, 10.1.1.0/22 would provide for ~1000 addresses.
+	</para>
+	 <para>
+		The following table lists limits set in the Global Configuration:
+	</para>
+	 <informaltable>
+		<tgroup cols="2">
+			<thead>
+				<row>
+					<entry>
+						<para>
+							Parameter Name
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Definition
+						</para>
+					</entry>
+
+				</row>
+
+			</thead>
+			 <tbody>
+				<row>
+					<entry>
+						<para>
+							max.account.public.ips
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Number of public IP addresses that can be owned by an account
+						</para>
+					</entry>
+
+				</row>
+				 <row>
+					<entry>
+						<para>
+							max.account.snapshots
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Number of snapshots that can exist for an account
+						</para>
+					</entry>
+
+				</row>
+				 <row>
+					<entry>
+						<para>
+							max.account.templates
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Number of templates that can exist for an account
+						</para>
+					</entry>
+
+				</row>
+				 <row>
+					<entry>
+						<para>
+							max.account.user.vms
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Number of virtual machine instances that can exist for an account
+						</para>
+					</entry>
+
+				</row>
+				 <row>
+					<entry>
+						<para>
+							max.account.volumes
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Number of disk volumes that can exist for an account
+						</para>
+					</entry>
+
+				</row>
+				 <row>
+					<entry>
+						<para>
+							max.template.iso.size
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Maximum size for a downloaded template or ISO in GB
+						</para>
+					</entry>
+
+				</row>
+				 <row>
+					<entry>
+						<para>
+							max.volume.size.gb
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Maximum size for a volume in GB
+						</para>
+					</entry>
+
+				</row>
+				 <row>
+					<entry>
+						<para>
+							network.throttling.rate
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Default data transfer rate in megabits per second allowed per user (supported on XenServer)
+						</para>
+					</entry>
+
+				</row>
+				 <row>
+					<entry>
+						<para>
+							snapshot.max.hourly
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Maximum recurring hourly snapshots to be retained for a volume. If the limit is reached, early snapshots from the start of the hour are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring hourly snapshots can not be scheduled
+						</para>
+					</entry>
+
+				</row>
+				 <row>
+					<entry>
+						<para>
+							snapshot.max.daily
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Maximum recurring daily snapshots to be retained for a volume. If the limit is reached, snapshots from the start of the day are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring daily snapshots can not be scheduled
+						</para>
+					</entry>
+
+				</row>
+				 <row>
+					<entry>
+						<para>
+							snapshot.max.weekly
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Maximum recurring weekly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the week are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring weekly snapshots can not be scheduled
+						</para>
+					</entry>
+
+				</row>
+				 <row>
+					<entry>
+						<para>
+							snapshot.max.monthly
+						</para>
+					</entry>
+					 <entry>
+						<para>
+							Maximum recurring monthly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the month are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring monthly snapshots can not be scheduled.
+						</para>
+					</entry>
+
+				</row>
+
+			</tbody>
+
+		</tgroup>
+
+	</informaltable>
+	 <para>
+		To modify global configuration parameters, use the global configuration screen in the &PRODUCT; UI. See Setting Global Configuration Parameters
+	</para>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/guest-ip-ranges.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/guest-ip-ranges.xml b/docs/tmp/en-US/xml/guest-ip-ranges.xml
new file mode 100644
index 0000000..9be25cb
--- /dev/null
+++ b/docs/tmp/en-US/xml/guest-ip-ranges.xml
@@ -0,0 +1,29 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="guest-ip-ranges" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Guest IP Ranges</title>
+	 <para>
+		The IP ranges for guest network traffic are set on a per-account basis by the user. This allows the users to configure their network in a fashion that will enable VPN linking between their guest network and their clients.
+	</para>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/guest-network.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/guest-network.xml b/docs/tmp/en-US/xml/guest-network.xml
new file mode 100644
index 0000000..6779b18
--- /dev/null
+++ b/docs/tmp/en-US/xml/guest-network.xml
@@ -0,0 +1,32 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="guest-network" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Guest Network</title>
+	 <para>
+		In a &PRODUCT; cloud, guest VMs can communicate with each other using shared infrastructure with the security and user perception that the guests have a private LAN.
+	</para>
+	 <para>
+		The &PRODUCT; virtual router is the main component providing networking features for guest traffic.
+	</para>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/guest-nw-usage-with-traffic-sentinel.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/guest-nw-usage-with-traffic-sentinel.xml b/docs/tmp/en-US/xml/guest-nw-usage-with-traffic-sentinel.xml
new file mode 100644
index 0000000..7f3003f
--- /dev/null
+++ b/docs/tmp/en-US/xml/guest-nw-usage-with-traffic-sentinel.xml
@@ -0,0 +1,78 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="guest-nw-usage-with-traffic-sentinel" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+  or more contributor license agreements.  See the NOTICE file
+  distributed with this work for additional information
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+  http://www.apache.org/licenses/LICENSE-2.0
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+ --> <title>Guest Network Usage Integration for Traffic Sentinel</title>
+	 <para>
+		To collect usage data for a guest network, &PRODUCT; needs to pull the data from an external network statistics collector installed on the network. Metering statistics for guest networks are available through &PRODUCT;’s integration with inMon Traffic Sentinel.
+	</para>
+	 <para>
+		Traffic Sentinel is a network traffic usage data collection package. &PRODUCT; can feed statistics from Traffic Sentinel into its own usage records, providing a basis for billing users of cloud infrastructure. Traffic Sentinel uses the traffic monitoring protocol sFlow. Routers and switches generate sFlow records and provide them for collection by Traffic Sentinel, then &PRODUCT; queries the Traffic Sentinel database to obtain this information
+	</para>
+	 <para>
+		To construct the query, &PRODUCT; determines what guest IPs were in use during the current query interval. This includes both newly assigned IPs and IPs that were assigned in a previous time period and continued to be in use. &PRODUCT; queries Traffic Sentinel for network statistics that apply to these IPs during the time period they remained allocated in &PRODUCT;. The returned data is correlated with the customer account that owned each IP and the timestamps when IPs were assigned and released in order to create billable metering records in &PRODUCT;. When the Usage Server runs, it collects this data.
+	</para>
+	 <para>
+		To set up the integration between &PRODUCT; and Traffic Sentinel:
+	</para>
+	 <orderedlist>
+		<listitem>
+			<para>
+				On your network infrastructure, install Traffic Sentinel and configure it to gather traffic data. For installation and configuration steps, see inMon documentation at <ulink url="http://inmon.com.">Traffic Sentinel Documentation</ulink>.
+			</para>
+
+		</listitem>
+		 <listitem>
+			<para>
+				In the Traffic Sentinel UI, configure Traffic Sentinel to accept script querying from guest users. &PRODUCT; will be the guest user performing the remote queries to gather network usage for one or more IP addresses.
+			</para>
+			 <para>
+				Click File &gt; Users &gt; Access Control &gt; Reports Query, then select Guest from the drop-down list.
+			</para>
+
+		</listitem>
+		 <listitem>
+			<para>
+				On &PRODUCT;, add the Traffic Sentinel host by calling the &PRODUCT; API command addTrafficMonitor. Pass in the URL of the Traffic Sentinel as protocol + host + port (optional); for example, http://10.147.28.100:8080. For the addTrafficMonitor command syntax, see the API Reference at <ulink url="http://incubator.apache.org/cloudstack/docs/api/index.html">API Documentation</ulink>.
+			</para>
+			 <para>
+				For information about how to call the &PRODUCT; API, see the Developer’s Guide at <ulink url="http://incubator.apache.org/cloudstack/docs/en-US/Apache_CloudStack/4.0.0-incubating/html/API_Developers_Guide/index.html">CloudStack API Developer's Guide</ulink>.
+			</para>
+
+		</listitem>
+		 <listitem>
+			<para>
+				Log in to the &PRODUCT; UI as administrator.
+			</para>
+
+		</listitem>
+		 <listitem>
+			<para>
+				Select Configuration from the Global Settings page, and set the following:
+			</para>
+			 <para>
+				direct.network.stats.interval: How often you want &PRODUCT; to query Traffic Sentinel.
+			</para>
+
+		</listitem>
+
+	</orderedlist>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/guest-traffic.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/guest-traffic.xml b/docs/tmp/en-US/xml/guest-traffic.xml
new file mode 100644
index 0000000..090e044
--- /dev/null
+++ b/docs/tmp/en-US/xml/guest-traffic.xml
@@ -0,0 +1,50 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="guest-traffic" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Guest Traffic</title>
+	 <para>
+		A network can carry guest traffic only between VMs within one zone. Virtual machines in different zones cannot communicate with each other using their IP addresses; they must communicate with each other by routing through a public IP address.
+	</para>
+	 <para>
+		Figure 1 illustrates a typical guest traffic setup:
+	</para>
+	 <mediaobject>
+		<imageobject>
+			<imagedata fileref="./images/basic-deployment.png" />
+		</imageobject>
+		 <textobject>
+			<phrase>guesttraffic.png: Depicts a guest traffic setup</phrase>
+		</textobject>
+
+	</mediaobject>
+	 <para>
+		The Management Server automatically creates a virtual router for each network. A virtual router is a special virtual machine that runs on the hosts. Each virtual router has three network interfaces. Its eth0 interface serves as the gateway for the guest traffic and has the IP address of 10.1.1.1. Its eth1 interface is used by the system to configure the virtual router. Its eth2 interface is assigned a public IP address for public traffic.
+	</para>
+	 <para>
+		The virtual router provides DHCP and will automatically assign an IP address for each guest VM within the IP range assigned for the network. The user can manually reconfigure guest VMs to assume different IP addresses.
+	</para>
+	 <para>
+		Source NAT is automatically configured in the virtual router to forward outbound traffic for all guest VMs
+	</para>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/ha-enabled-vm.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/ha-enabled-vm.xml b/docs/tmp/en-US/xml/ha-enabled-vm.xml
new file mode 100644
index 0000000..62463b5
--- /dev/null
+++ b/docs/tmp/en-US/xml/ha-enabled-vm.xml
@@ -0,0 +1,33 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="ha-enabled-vm" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>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, &PRODUCT; detects the crash and restarts the VM automatically within the same Availability Zone. HA is never performed across different Availability Zones. &PRODUCT; 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>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/ha-for-hosts.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/ha-for-hosts.xml b/docs/tmp/en-US/xml/ha-for-hosts.xml
new file mode 100644
index 0000000..1ef035f
--- /dev/null
+++ b/docs/tmp/en-US/xml/ha-for-hosts.xml
@@ -0,0 +1,33 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="ha-for-hosts" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>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, &PRODUCT; detects the crash and restarts the VM automatically within the same Availability Zone. HA is never performed across different Availability Zones. &PRODUCT; 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>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/ha-management-server.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/ha-management-server.xml b/docs/tmp/en-US/xml/ha-management-server.xml
new file mode 100644
index 0000000..d467555
--- /dev/null
+++ b/docs/tmp/en-US/xml/ha-management-server.xml
@@ -0,0 +1,36 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="ha-management-server" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>HA for Management Server</title>
+	 <para>
+		The &PRODUCT; 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/92d4b214/docs/tmp/en-US/xml/hardware-config-eg.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hardware-config-eg.xml b/docs/tmp/en-US/xml/hardware-config-eg.xml
new file mode 100644
index 0000000..dcdf2e6
--- /dev/null
+++ b/docs/tmp/en-US/xml/hardware-config-eg.xml
@@ -0,0 +1,29 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hardware-config-eg" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+  or more contributor license agreements.  See the NOTICE file
+  distributed with this work for additional information
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+  http://www.apache.org/licenses/LICENSE-2.0
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+ --> <title>Example Hardware Configuration</title>
+	 <para>
+		This section contains an example configuration of specific switch models for zone-level layer-3 switching. It assumes VLAN management protocols, such as VTP or GVRP, have been disabled. The example scripts must be changed appropriately if you choose to use VTP or GVRP.
+	</para>
+	 <xi:include href="dell62xx-hardware.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="cisco3750-hardware.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hardware-firewall.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hardware-firewall.xml b/docs/tmp/en-US/xml/hardware-firewall.xml
new file mode 100644
index 0000000..f89859b
--- /dev/null
+++ b/docs/tmp/en-US/xml/hardware-firewall.xml
@@ -0,0 +1,30 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hardware-firewall" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+  or more contributor license agreements.  See the NOTICE file
+  distributed with this work for additional information
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+  http://www.apache.org/licenses/LICENSE-2.0
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+ --> <title>Hardware Firewall</title>
+	 <para>
+		All deployments should have a firewall protecting the management server; see Generic Firewall Provisions. Optionally, some deployments may also have a Juniper SRX firewall that will be the default gateway for the guest networks; see <xref linkend="external-guest-firewall-integration" />.
+	</para>
+	 <xi:include href="generic-firewall-provisions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="external-guest-firewall-integration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="external-guest-lb-integration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/host-add-vsphere.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/host-add-vsphere.xml b/docs/tmp/en-US/xml/host-add-vsphere.xml
new file mode 100644
index 0000000..3e1183e
--- /dev/null
+++ b/docs/tmp/en-US/xml/host-add-vsphere.xml
@@ -0,0 +1,29 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="host-add-vsphere" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+    
+    http://www.apache.org/licenses/LICENSE-2.0
+    
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+ --> <title>Adding a Host (vSphere)</title>
+	 <para>
+		For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to &PRODUCT;. See Add Cluster: vSphere.
+	</para>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/host-add-xenserver-kvm-ovm.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/host-add-xenserver-kvm-ovm.xml b/docs/tmp/en-US/xml/host-add-xenserver-kvm-ovm.xml
new file mode 100644
index 0000000..3a73396
--- /dev/null
+++ b/docs/tmp/en-US/xml/host-add-xenserver-kvm-ovm.xml
@@ -0,0 +1,222 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="host-add-xenserver-kvm-ovm" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+    
+    http://www.apache.org/licenses/LICENSE-2.0
+    
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+ --> <title>Adding a Host (XenServer or KVM)</title>
+	 <para>
+		XenServer and KVM hosts can be added to a cluster at any time.
+	</para>
+	 <section>
+		<title>Requirements for XenServer and KVM Hosts</title>
+		 <warning>
+			<para>
+				Make sure the hypervisor host does not have any VMs already running before you add it to &PRODUCT;.
+			</para>
+
+		</warning>
+		 <para>
+			Configuration requirements:
+		</para>
+		 <itemizedlist>
+			<listitem>
+				<para>
+					Each cluster must contain only hosts with the identical hypervisor.
+				</para>
+
+			</listitem>
+			 <listitem>
+				<para>
+					For XenServer, do not put more than 8 hosts in a cluster.
+				</para>
+
+			</listitem>
+			 <listitem>
+				<para>
+					For KVM, do not put more than 16 hosts in a cluster.
+				</para>
+
+			</listitem>
+
+		</itemizedlist>
+		 <para>
+			For hardware requirements, see the installation section for your hypervisor in the &PRODUCT; Installation Guide.
+		</para>
+		 <section>
+			<title>XenServer Host Additional Requirements</title>
+			 <para>
+				If network bonding is in use, the administrator must cable the new host identically to other hosts in the cluster.
+			</para>
+			 <para>
+				For all additional hosts to be added to the cluster, run the following command. This will cause the host to join the master in a XenServer pool.
+			</para>
+			 
+<programlisting># xe pool-join master-address=[master IP] master-username=root master-password=[your password]</programlisting>
+			 <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>
+			 <para>
+				With all hosts added to the XenServer pool, run the cloud-setup-bond script. This script will complete the configuration and setup of the bonds on the new hosts in the cluster.
+			</para>
+			 <orderedlist>
+				<listitem>
+					<para>
+						Copy the script from the Management Server in /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master host and ensure it is executable.
+					</para>
+
+				</listitem>
+				 <listitem>
+					<para>
+						Run the script:
+					</para>
+					 
+<programlisting># ./cloud-setup-bonding.sh</programlisting>
+
+				</listitem>
+
+			</orderedlist>
+
+		</section>
+		
+		 <section>
+			<title>KVM Host Additional Requirements</title>
+			 <itemizedlist>
+				<listitem>
+					<para>
+						If shared mountpoint storage is in use, the administrator should ensure that the new host has all the same mountpoints (with storage mounted) as the other hosts in the cluster.
+					</para>
+
+				</listitem>
+				 <listitem>
+					<para>
+						Make sure the new host has the same network configuration (guest, private, and public network) as other hosts in the cluster.
+					</para>
+
+				</listitem>
+
+			</itemizedlist>
+
+		</section>
+		
+		 <!--  <section>
+    <title>OVM Host Additional Requirements</title>
+      <para>Before adding a used host in &PRODUCT;, as part of the cleanup procedure on the host, be
+          sure to remove /etc/ovs-agent/db/.</para> 
+    </section>  -->
+	</section>
+	
+	 <section>
+		<title>Adding a XenServer or KVM Host</title>
+		 <itemizedlist>
+			<listitem>
+				<para>
+					If you have not already done so, install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by &PRODUCT; and what additional configuration is required to ensure the host will work with &PRODUCT;. To find these installation details, see the appropriate section for your hypervisor in the &PRODUCT; Installation Guide.
+				</para>
+
+			</listitem>
+			 <listitem>
+				<para>
+					Log in to the &PRODUCT; UI as administrator.
+				</para>
+
+			</listitem>
+			 <listitem>
+				<para>
+					In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the host.
+				</para>
+
+			</listitem>
+			 <listitem>
+				<para>
+					Click the Compute tab. In the Clusters node, click View All.
+				</para>
+
+			</listitem>
+			 <listitem>
+				<para>
+					Click the cluster where you want to add the host.
+				</para>
+
+			</listitem>
+			 <listitem>
+				<para>
+					Click View Hosts.
+				</para>
+
+			</listitem>
+			 <listitem>
+				<para>
+					Click Add Host.
+				</para>
+
+			</listitem>
+			 <listitem>
+				<para>
+					Provide the following information.
+				</para>
+				 <itemizedlist>
+					<listitem>
+						<para>
+							Host Name. The DNS name or IP address of the host.
+						</para>
+
+					</listitem>
+					 <listitem>
+						<para>
+							Username. Usually root.
+						</para>
+
+					</listitem>
+					 <listitem>
+						<para>
+							Password. This is the password for the user from your XenServer or KVM install).
+						</para>
+
+					</listitem>
+					 <listitem>
+						<para>
+							Host Tags (Optional). Any labels that you use to categorize hosts for ease of maintenance. For example, you can set to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the "high availability" feature enabled. For more information, see HA-Enabled Virtual Machines as well as HA for Hosts.
+						</para>
+
+					</listitem>
+
+				</itemizedlist>
+				 <para>
+					There may be a slight delay while the host is provisioned. It should automatically display in the UI.
+				</para>
+
+			</listitem>
+			 <listitem>
+				<para>
+					Repeat for additional hosts.
+				</para>
+
+			</listitem>
+
+		</itemizedlist>
+
+	</section>
+
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/host-add.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/host-add.xml b/docs/tmp/en-US/xml/host-add.xml
new file mode 100644
index 0000000..10845bf
--- /dev/null
+++ b/docs/tmp/en-US/xml/host-add.xml
@@ -0,0 +1,64 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="host-add" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+    
+    http://www.apache.org/licenses/LICENSE-2.0
+    
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+ --> <title>Adding a Host</title>
+	 <orderedlist>
+		<listitem>
+			<para>
+				Before adding a host to the &PRODUCT; configuration, you must first install your chosen hypervisor on the host. &PRODUCT; can manage hosts running VMs under a variety of hypervisors.
+			</para>
+			 <para>
+				The &PRODUCT; Installation Guide provides instructions on how to install each supported hypervisor and configure it for use with &PRODUCT;. See the appropriate section in the Installation Guide for information about which version of your chosen hypervisor is supported, as well as crucial additional steps to configure the hypervisor hosts for use with &PRODUCT;.
+			</para>
+			 <warning>
+				<para>
+					Be sure you have performed the additional &PRODUCT;-specific configuration steps described in the hypervisor installation section for your particular hypervisor.
+				</para>
+			</warning>
+
+		</listitem>
+		 <listitem>
+			<para>
+				Now add the hypervisor host to &PRODUCT;. The technique to use varies depending on the hypervisor.
+			</para>
+			 <itemizedlist>
+				<listitem>
+					<para>
+						<xref linkend="host-add-xenserver-kvm-ovm" />
+					</para>
+				</listitem>
+				 <listitem>
+					<para>
+						<xref linkend="host-add-vsphere" />
+					</para>
+				</listitem>
+
+			</itemizedlist>
+
+		</listitem>
+
+	</orderedlist>
+	 <xi:include href="host-add-xenserver-kvm-ovm.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="host-add-vsphere.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/host-allocation.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/host-allocation.xml b/docs/tmp/en-US/xml/host-allocation.xml
new file mode 100644
index 0000000..a29931d
--- /dev/null
+++ b/docs/tmp/en-US/xml/host-allocation.xml
@@ -0,0 +1,38 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="host-allocation" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>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>
+		&PRODUCT; 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. &PRODUCT; 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>
+		&PRODUCT; also provides a pluggable interface for adding new allocators. These custom allocators can provide any policy the administrator desires.
+	</para>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-host-install-agent.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-host-install-agent.xml b/docs/tmp/en-US/xml/hypervisor-host-install-agent.xml
new file mode 100644
index 0000000..fbc7187
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-host-install-agent.xml
@@ -0,0 +1,45 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hypervisor-host-install-agent" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Install and configure the Agent</title>
+	 <para>
+		To manage KVM instances on the host &PRODUCT; uses a Agent. This Agent communicates with the Management server and controls all the instances on the host.
+	</para>
+	 <para>
+		First we start by installing the agent:
+	</para>
+	 <para>
+		In RHEL or CentOS:
+	</para>
+	 
+<programlisting language="Bash"><command>$ yum install cloud-agent</command></programlisting>
+	 <para>
+		In Ubuntu:
+	</para>
+	 
+<programlisting language="Bash"><command>$ apt-get install cloud-agent</command></programlisting>
+	 <para>
+		The host is now ready to be added to a cluster. This is covered in a later section, see <xref linkend="host-add" />. It is recommended that you continue to read the documentation before adding the host!
+	</para>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-host-install-finish.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-host-install-finish.xml b/docs/tmp/en-US/xml/hypervisor-host-install-finish.xml
new file mode 100644
index 0000000..fbfbd5b
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-host-install-finish.xml
@@ -0,0 +1,29 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hypervisor-host-install-finish" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Add the host to CloudStack</title>
+	 <para>
+		The host is now ready to be added to a cluster. This is covered in a later section, see <xref linkend="host-add" />. It is recommended that you continue to read the documentation before adding the host!
+	</para>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-host-install-firewall.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-host-install-firewall.xml b/docs/tmp/en-US/xml/hypervisor-host-install-firewall.xml
new file mode 100644
index 0000000..68d24af
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-host-install-firewall.xml
@@ -0,0 +1,112 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hypervisor-host-install-firewall" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Configuring the firewall</title>
+	 <para>
+		The hypervisor needs to be able to communicate with other hypervisors and the management server needs to be able to reach the hypervisor.
+	</para>
+	 <para>
+		In order to do so we have to open the following TCP ports (if you are using a firewall):
+	</para>
+	 <orderedlist>
+		<listitem>
+			<para>
+				22 (SSH)
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				1798
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				16509 (libvirt)
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				5900 - 6100 (VNC consoles)
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				49152 - 49216 (libvirt live migration)
+			</para>
+		</listitem>
+
+	</orderedlist>
+	 <para>
+		It depends on the firewall you are using how to open these ports. Below you'll find examples how to open these ports in RHEL/CentOS and Ubuntu.
+	</para>
+	 <section id="hypervisor-host-install-firewall-rhel">
+		<title>Open ports in RHEL/CentOS</title>
+		 <para>
+			RHEL and CentOS use iptables for firewalling the system, you can open extra ports by executing the following iptable commands:
+		</para>
+		 
+<programlisting language="Bash"><command>$ iptables -I INPUT -p tcp -m tcp --dport 22 -j ACCEPT</command></programlisting>
+		 
+<programlisting language="Bash"><command>$ iptables -I INPUT -p tcp -m tcp --dport 1798 -j ACCEPT</command></programlisting>
+		 
+<programlisting language="Bash"><command>$ iptables -I INPUT -p tcp -m tcp --dport 16509 -j ACCEPT</command></programlisting>
+		 
+<programlisting language="Bash"><command>$ iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT</command></programlisting>
+		 
+<programlisting language="Bash"><command>$ iptables -I INPUT -p tcp -m tcp --dport 49152:49216 -j ACCEPT</command></programlisting>
+		 <para>
+			These iptable settings are not persistent accross reboots, we have to save them first.
+		</para>
+		 
+<programlisting language="Bash"><command>$ iptables-save &gt; /etc/sysconfig/iptables</command></programlisting>
+
+	</section>
+	
+	 <section id="hypervisor-host-install-firewall-ubuntu">
+		<title>Open ports in Ubuntu</title>
+		 <para>
+			The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is a Python wrapper around iptables.
+		</para>
+		 <para>
+			To open the required ports, execute the following commands:
+		</para>
+		 
+<programlisting language="Bash"><command>$ ufw allow proto tcp from any to any port 22</command></programlisting>
+		 
+<programlisting language="Bash"><command>$ ufw allow proto tcp from any to any port 1798</command></programlisting>
+		 
+<programlisting language="Bash"><command>$ ufw allow proto tcp from any to any port 16509</command></programlisting>
+		 
+<programlisting language="Bash"><command>$ ufw allow proto tcp from any to any port 5900:6100</command></programlisting>
+		 
+<programlisting language="Bash"><command>$ ufw allow proto tcp from any to any port 49152:49216</command></programlisting>
+		 <note>
+			<para>
+				By default UFW is not enabled on Ubuntu. Executing these commands with the firewall disabled does not enable the firewall.
+			</para>
+		</note>
+
+	</section>
+
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-host-install-libvirt.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-host-install-libvirt.xml b/docs/tmp/en-US/xml/hypervisor-host-install-libvirt.xml
new file mode 100644
index 0000000..4c4f2b6
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-host-install-libvirt.xml
@@ -0,0 +1,97 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hypervisor-host-install-libvirt" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Install and Configure libvirt</title>
+	 <para>
+		&PRODUCT; uses libvirt for managing virtual machines. Therefore it is vital that libvirt is configured correctly. Libvirt is a dependency of cloud-agent and should already be installed.
+	</para>
+	 <orderedlist>
+		<listitem>
+			<para>
+				In order to have live migration working libvirt has to listen for unsecured TCP connections. We also need to turn off libvirts attempt to use Multicast DNS advertising. Both of these settings are in <filename>/etc/libvirt/libvirtd.conf</filename>
+			</para>
+			 <para>
+				Set the following paramaters:
+			</para>
+			 
+<programlisting>listen_tls = 0</programlisting>
+			 
+<programlisting>listen_tcp = 1</programlisting>
+			 
+<programlisting>tcp_port = 16059</programlisting>
+			 
+<programlisting>auth_tcp = "none"</programlisting>
+			 
+<programlisting>mdns_adv = 0</programlisting>
+
+		</listitem>
+		 <listitem>
+			<para>
+				Turning on "listen_tcp" in libvirtd.conf is not enough, we have to change the parameters as well:
+			</para>
+			 <para>
+				On RHEL or CentOS modify <filename>/etc/sysconfig/libvirtd</filename>:
+			</para>
+			 <para>
+				Uncomment the following line:
+			</para>
+			 
+<programlisting>#LIBVIRTD_ARGS="--listen"</programlisting>
+			 <para>
+				On Ubuntu: modify <filename>/etc/init/libvirt-bin.conf</filename>
+			</para>
+			 <para>
+				Change the following line (at the end of the file):
+			</para>
+			 
+<programlisting>exec /usr/sbin/libvirtd -d</programlisting>
+			 <para>
+				to (just add -l)
+			</para>
+			 
+<programlisting>exec /usr/sbin/libvirtd -d -l</programlisting>
+			 <para>
+				You will also want to edit <filename>/etc/libvirt/qemu.conf</filename> and make sure that "vnc_listen = 0.0.0.0" is uncommented.
+			</para>
+
+		</listitem>
+		 <listitem>
+			<para>
+				Restart libvirt
+			</para>
+			 <para>
+				In RHEL or CentOS:
+			</para>
+			 
+<programlisting><command>$ service libvirtd restart</command></programlisting>
+			 <para>
+				In Ubuntu:
+			</para>
+			 
+<programlisting><command>$ service libvirt-bin restart</command></programlisting>
+
+		</listitem>
+
+	</orderedlist>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-host-install-network.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-host-install-network.xml b/docs/tmp/en-US/xml/hypervisor-host-install-network.xml
new file mode 100644
index 0000000..6e2a4a8
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-host-install-network.xml
@@ -0,0 +1,239 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hypervisor-host-install-network" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Configure the network bridges</title>
+	 <warning>
+		<para>
+			This is a very important section, please make sure you read this thoroughly.
+		</para>
+	</warning>
+	 <para>
+		In order to forward traffic to your instances you will need at least two bridges: <emphasis>public</emphasis> and <emphasis>private</emphasis>.
+	</para>
+	 <para>
+		By default these bridges are called <emphasis>cloudbr0</emphasis> and <emphasis>cloudbr1</emphasis>, but you do have to make sure they are available on each hypervisor.
+	</para>
+	 <para>
+		The most important factor is that you keep the configuration consistent on all your hypervisors.
+	</para>
+	 <section id="hypervisor-host-install-network-vlan">
+		<title>Network example</title>
+		 <para>
+			There are many ways to configure your network. In the Basic networking mode you should have two (V)LAN's, one for your private network and one for the public network.
+		</para>
+		 <para>
+			We assume that the hypervisor has one NIC (eth0) with three tagged VLAN's:
+		</para>
+		 <orderedlist>
+			<listitem>
+				<para>
+					VLAN 100 for management of the hypervisor
+				</para>
+			</listitem>
+			 <listitem>
+				<para>
+					VLAN 200 for public network of the instances (cloudbr0)
+				</para>
+			</listitem>
+			 <listitem>
+				<para>
+					VLAN 300 for private network of the instances (cloudbr1)
+				</para>
+			</listitem>
+
+		</orderedlist>
+		 <para>
+			On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with the gateway 192.168.42.1
+		</para>
+		 <note>
+			<para>
+				The Hypervisor and Management server don't have to be in the same subnet!
+			</para>
+		</note>
+
+	</section>
+	
+	 <section id="hypervisor-host-install-network-configure">
+		<title>Configuring the network bridges</title>
+		 <para>
+			It depends on the distribution you are using how to configure these, below you'll find examples for RHEL/CentOS and Ubuntu.
+		</para>
+		 <note>
+			<para>
+				The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this section. This should be used as a guideline only. The exact configuration will depend on your network layout.
+			</para>
+		</note>
+		 <section id="hypervisor-host-install-network-configure-rhel">
+			<title>Configure in RHEL or CentOS</title>
+			 <para>
+				The required packages were installed when libvirt was installed, we can proceed to configuring the network.
+			</para>
+			 <para>
+				First we configure eth0
+			</para>
+			 
+<programlisting language="Bash">vi /etc/sysconfig/network-scripts/ifcfg-eth0</programlisting>
+			 <para>
+				Make sure it looks similair to:
+			</para>
+			 
+<programlisting>DEVICE=eth0
+HWADDR=00:04:xx:xx:xx:xx
+ONBOOT=yes
+HOTPLUG=no
+BOOTPROTO=none
+TYPE=Ethernet</programlisting>
+			 <para>
+				We now have to configure the three VLAN interfaces:
+			</para>
+			 
+<programlisting language="Bash">vi /etc/sysconfig/network-scripts/ifcfg-eth0.100</programlisting>
+			 
+<programlisting>DEVICE=eth0.100
+HWADDR=00:04:xx:xx:xx:xx
+ONBOOT=yes
+HOTPLUG=no
+BOOTPROTO=none
+TYPE=Ethernet
+VLAN=yes
+IPADDR=192.168.42.11
+GATEWAY=192.168.42.1
+NETMASK=255.255.255.0</programlisting>
+			 
+<programlisting language="Bash">vi /etc/sysconfig/network-scripts/ifcfg-eth0.200</programlisting>
+			 
+<programlisting>DEVICE=eth0.200
+HWADDR=00:04:xx:xx:xx:xx
+ONBOOT=yes
+HOTPLUG=no
+BOOTPROTO=none
+TYPE=Ethernet
+VLAN=yes
+BRIDGE=cloudbr0</programlisting>
+			 
+<programlisting language="Bash">vi /etc/sysconfig/network-scripts/ifcfg-eth0.300</programlisting>
+			 
+<programlisting>DEVICE=eth0.300
+HWADDR=00:04:xx:xx:xx:xx
+ONBOOT=yes
+HOTPLUG=no
+BOOTPROTO=none
+TYPE=Ethernet
+VLAN=yes
+BRIDGE=cloudbr1</programlisting>
+			 <para>
+				Now we have the VLAN interfaces configured we can add the bridges on top of them.
+			</para>
+			 
+<programlisting language="Bash">vi /etc/sysconfig/network-scripts/ifcfg-cloudbr0</programlisting>
+			 <para>
+				Now we just configure it is a plain bridge without an IP-Adress
+			</para>
+			 
+<programlisting>DEVICE=cloudbr0
+TYPE=Bridge
+ONBOOT=yes
+BOOTPROTO=none
+IPV6INIT=no
+IPV6_AUTOCONF=no
+DELAY=5
+STP=yes</programlisting>
+			 <para>
+				We do the same for cloudbr1
+			</para>
+			 
+<programlisting language="Bash">vi /etc/sysconfig/network-scripts/ifcfg-cloudbr1</programlisting>
+			 
+<programlisting>DEVICE=cloudbr1
+TYPE=Bridge
+ONBOOT=yes
+BOOTPROTO=none
+IPV6INIT=no
+IPV6_AUTOCONF=no
+DELAY=5
+STP=yes</programlisting>
+			 <para>
+				With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly.
+			</para>
+			 <warning>
+				<para>
+					Make sure you have an alternative way like IPMI or ILO to reach the machine in case you made a configuration error and the network stops functioning!
+				</para>
+			</warning>
+
+		</section>
+		
+		 <section id="hypervisor-host-install-network-configure-ubuntu">
+			<title>Configure in Ubuntu</title>
+			 <para>
+				All the required packages were installed when you installed libvirt, so we only have to configure the network.
+			</para>
+			 
+<programlisting language="Bash">vi /etc/network/interfaces</programlisting>
+			 <para>
+				Modify the interfaces file to look like this:
+			</para>
+			 
+<programlisting>auto lo
+iface lo inet loopback
+
+# The primary network interface
+auto eth0.100
+iface eth0.100 inet static
+    address 192.168.42.11
+    netmask 255.255.255.240
+    gateway 192.168.42.1
+    dns-nameservers 8.8.8.8 8.8.4.4
+    dns-domain lab.example.org
+
+# Public network
+auto cloudbr0
+iface cloudbr0 inet manual
+    bridge_ports eth0.200
+    bridge_fd 5
+    bridge_stp off
+    bridge_maxwait 1
+
+# Private network
+auto cloudbr1
+iface cloudbr1 inet manual
+    bridge_ports eth0.300
+    bridge_fd 5
+    bridge_stp off
+    bridge_maxwait 1</programlisting>
+			 <para>
+				With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly.
+			</para>
+			 <warning>
+				<para>
+					Make sure you have an alternative way like IPMI or ILO to reach the machine in case you made a configuration error and the network stops functioning!
+				</para>
+			</warning>
+
+		</section>
+		
+
+	</section>
+
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-host-install-overview.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-host-install-overview.xml b/docs/tmp/en-US/xml/hypervisor-host-install-overview.xml
new file mode 100644
index 0000000..19e89d2
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-host-install-overview.xml
@@ -0,0 +1,65 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hypervisor-host-install-overview" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>KVM Installation Overview</title>
+	 <para>
+		If you want to use the Linux Kernel Virtual Machine (KVM) hypervisor to run guest virtual machines, install KVM on the host(s) in your cloud. The material in this section doesn't duplicate KVM installation docs. It provides the &PRODUCT;-specific steps that are needed to prepare a KVM host to work with &PRODUCT;.
+	</para>
+	 <warning>
+		<para>
+			Before continuing, make sure that you have applied the latest updates to your host.
+		</para>
+	</warning>
+	 <warning>
+		<para>
+			It is NOT recommended to run services on this host not controlled by &PRODUCT;.
+		</para>
+	</warning>
+	 <para>
+		The procedure for installing a KVM Hypervisor Host is:
+	</para>
+	 <orderedlist>
+		<listitem>
+			<para>
+				Prepare the Operating System
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				Install and configure libvirt
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				Configure Security Policies (AppArmor and SELinux)
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				Install and configure the Agent
+			</para>
+		</listitem>
+
+	</orderedlist>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-host-install-prepare-os.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-host-install-prepare-os.xml b/docs/tmp/en-US/xml/hypervisor-host-install-prepare-os.xml
new file mode 100644
index 0000000..2e15106
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-host-install-prepare-os.xml
@@ -0,0 +1,85 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hypervisor-host-install-prepare-os" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Prepare the Operating System</title>
+	 <para>
+		The OS of the Host must be prepared to host the &PRODUCT; Agent and run KVM instances.
+	</para>
+	 <orderedlist>
+		<listitem>
+			<para>
+				Log in to your OS as root.
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				Check for a fully qualified hostname.
+			</para>
+			 
+<programlisting language="Bash"><command>$ hostname --fqdn</command></programlisting>
+			 <para>
+				This should return a fully qualified hostname such as "kvm1.lab.example.org". If it does not, edit /etc/hosts so that it does.
+			</para>
+
+		</listitem>
+		 <listitem>
+			<para>
+				Make sure that the machine can reach the Internet.
+			</para>
+			 
+<programlisting language="Bash"><command>$ ping www.cloudstack.org</command></programlisting>
+
+		</listitem>
+		 <listitem>
+			<para>
+				Turn on NTP for time synchronization.
+			</para>
+			 <note>
+				<para>
+					NTP is required to synchronize the clocks of the servers in your cloud. Unsynchronized clocks can cause unexpected problems.
+				</para>
+			</note>
+			 <orderedlist numeration="loweralpha">
+				<listitem>
+					<para>
+						Install NTP
+					</para>
+					  
+<programlisting language="Bash"><command>$ yum install ntp</command></programlisting>
+					  
+<programlisting language="Bash"><command>$ apt-get install openntpd</command></programlisting>
+
+				</listitem>
+
+			</orderedlist>
+
+		</listitem>
+		 <listitem>
+			<para>
+				Repeat all of these steps on every hypervisor host.
+			</para>
+		</listitem>
+
+	</orderedlist>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-host-install-security-policies.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-host-install-security-policies.xml b/docs/tmp/en-US/xml/hypervisor-host-install-security-policies.xml
new file mode 100644
index 0000000..a591a04
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-host-install-security-policies.xml
@@ -0,0 +1,115 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hypervisor-host-install-security-policies" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Configure the Security Policies</title>
+	 <para>
+		&PRODUCT; does various things which can be blocked by security mechanisms like AppArmor and SELinux. These have to be disabled to ensure the Agent has all the required permissions.
+	</para>
+	 <orderedlist>
+		<listitem>
+			<para>
+				Configure SELinux (RHEL and CentOS)
+			</para>
+			 <orderedlist numeration="loweralpha">
+				<listitem>
+					<para>
+						Check to see whether SELinux is installed on your machine. If not, you can skip this section.
+					</para>
+					 <para>
+						In RHEL or CentOS, SELinux is installed and enabled by default. You can verify this with:
+					</para>
+					 
+<programlisting language="Bash"><command>$ rpm -qa | grep selinux</command></programlisting>
+
+				</listitem>
+				 <listitem>
+					<para>
+						Set the SELINUX variable in <filename>/etc/selinux/config</filename> to "permissive". This ensures that the permissive setting will be maintained after a system reboot.
+					</para>
+					 <para>
+						In RHEL or CentOS:
+					</para>
+					 
+<programlisting language="Bash">vi /etc/selinux/config</programlisting>
+					 <para>
+						Change the following line
+					</para>
+					 
+<programlisting>SELINUX=enforcing</programlisting>
+					 <para>
+						to this
+					</para>
+					 
+<programlisting>SELINUX=permissive</programlisting>
+
+				</listitem>
+				 <listitem>
+					<para>
+						Then set SELinux to permissive starting immediately, without requiring a system reboot.
+					</para>
+					 
+<programlisting language="Bash"><command>$ setenforce permissive</command></programlisting>
+
+				</listitem>
+
+			</orderedlist>
+
+		</listitem>
+		 <listitem>
+			<para>
+				Configure Apparmor (Ubuntu)
+			</para>
+			 <orderedlist numeration="loweralpha">
+				<listitem>
+					<para>
+						Check to see whether AppArmor is installed on your machine. If not, you can skip this section.
+					</para>
+					 <para>
+						In Ubuntu AppArmor is installed and enabled by default. You can verify this with:
+					</para>
+					 
+<programlisting language="Bash"><command>$ dpkg --list 'apparmor'</command></programlisting>
+
+				</listitem>
+				 <listitem>
+					<para>
+						Disable the AppArmor profiles for libvirt
+					</para>
+					 
+<programlisting language="Bash"><command>$ ln -s /etc/apparmor.d/usr.sbin.libvirtd /etc/apparmor.d/disable/</command></programlisting>
+					 
+<programlisting language="Bash"><command>$ ln -s /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper /etc/apparmor.d/disable/</command></programlisting>
+					 
+<programlisting language="Bash"><command>$ apparmor_parser -R /etc/apparmor.d/usr.sbin.libvirtd</command></programlisting>
+					 
+<programlisting language="Bash"><command>$ apparmor_parser -R /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper</command></programlisting>
+
+				</listitem>
+
+			</orderedlist>
+
+		</listitem>
+
+	</orderedlist>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-installation.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-installation.xml b/docs/tmp/en-US/xml/hypervisor-installation.xml
new file mode 100644
index 0000000..d98cdd8
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-installation.xml
@@ -0,0 +1,29 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<chapter id="hypervisor-installation" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Hypervisor Installation</title>
+	 <xi:include href="hypervisor-kvm-install-flow.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="citrix-xenserver-installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="vmware-install.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <!--     <xi:include href="ovm-install.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>  -->
+</chapter>
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-kvm-install-flow.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-kvm-install-flow.xml b/docs/tmp/en-US/xml/hypervisor-kvm-install-flow.xml
new file mode 100644
index 0000000..e3a2cc0
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-kvm-install-flow.xml
@@ -0,0 +1,35 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hypervisor-kvm-install-flow" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>KVM Hypervisor Host Installation</title>
+	 <xi:include href="hypervisor-kvm-requirements.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="hypervisor-host-install-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="hypervisor-host-install-prepare-os.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="hypervisor-host-install-agent.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="hypervisor-host-install-libvirt.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="hypervisor-host-install-security-policies.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="hypervisor-host-install-network.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="hypervisor-host-install-firewall.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	 <xi:include href="hypervisor-host-install-finish.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-kvm-requirements.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-kvm-requirements.xml b/docs/tmp/en-US/xml/hypervisor-kvm-requirements.xml
new file mode 100644
index 0000000..0e6c95c
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-kvm-requirements.xml
@@ -0,0 +1,99 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hypervisor-kvm-requirements" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>System Requirements for KVM Hypervisor Hosts</title>
+	 <para>
+		KVM is included with a variety of Linux-based operating systems. Although you are not required to run these distributions, the following are recommended:
+	</para>
+	 <itemizedlist>
+		<listitem>
+			<para>
+				CentOS / RHEL: 6.3
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				Ubuntu: 12.04(.1)
+			</para>
+		</listitem>
+
+	</itemizedlist>
+	 <para>
+		The main requirement for KVM hypervisors is the libvirt and Qemu version. No matter what Linux distribution you are using, make sure the following requirements are met:
+	</para>
+	 <itemizedlist>
+		<listitem>
+			<para>
+				libvirt: 0.9.4 or higher
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				Qemu/KVM: 1.0 or higher
+			</para>
+		</listitem>
+
+	</itemizedlist>
+	 <para>
+		In addition, the following hardware requirements apply:
+	</para>
+	 <itemizedlist>
+		<listitem>
+			<para>
+				Within a single cluster, the hosts must be of the same distribution version.
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags.
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				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>
+				4 GB of memory
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				At least 1 NIC
+			</para>
+		</listitem>
+		 <listitem>
+			<para>
+				When you deploy &PRODUCT;, the hypervisor host must not have any VMs already running
+			</para>
+		</listitem>
+
+	</itemizedlist>
+</section>
+
+

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/hypervisor-support-for-primarystorage.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/hypervisor-support-for-primarystorage.xml b/docs/tmp/en-US/xml/hypervisor-support-for-primarystorage.xml
new file mode 100644
index 0000000..59e78fc
--- /dev/null
+++ b/docs/tmp/en-US/xml/hypervisor-support-for-primarystorage.xml
@@ -0,0 +1,222 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="hypervisor-support-for-primarystorage" lang="en-US">
+	<!--  Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>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>
+			 <colspec colname="c2" colnum="2" colwidth="4cm"></colspec>
+			 <colspec colname="c3" colnum="3" colwidth="5cm"></colspec>
+			 <colspec colname="c4" colnum="2" colwidth="5.9cm"></colspec>
+			 <colspec colname="c5" colnum="3" colwidth="5.0cm"></colspec>
+			 <colspec colname="c4" colnum="4" colwidth="120.75pt"></colspec>
+			 <colspec colname="c5" colnum="5" colwidth="80.25pt"></colspec>
+			 <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>
+							<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>
+
+				</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>
+
+				</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>
+
+				</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>
+
+				</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>
+
+				</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>
+
+				</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 &PRODUCT; 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 &PRODUCT; does not attempt to mount or unmount the storage as is done with NFS. The &PRODUCT; 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 &PRODUCT; 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, &PRODUCT; 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, &PRODUCT; 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, 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>
+		&PRODUCT; 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>
+
+