cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From seb...@apache.org
Subject [32/51] [partial] cloudstack-docs git commit: Remove all old docbook files
Date Thu, 01 Oct 2015 14:04:42 GMT
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/host-allocation.xml
----------------------------------------------------------------------
diff --git a/en-US/host-allocation.xml b/en-US/host-allocation.xml
deleted file mode 100644
index dddffd5..0000000
--- a/en-US/host-allocation.xml
+++ /dev/null
@@ -1,123 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="host-allocation">
-    <title>Assigning VMs to Hosts</title>
-    <para>At any point in time, each virtual machine instance is running on a single host.
-        How does &PRODUCT; determine which host to place a VM on? There are several ways:</para>
-    <itemizedlist>
-        <listitem><para>Automatic default host allocation. &PRODUCT; can automatically pick
-            the most appropriate host to run each virtual machine.</para></listitem>
-        <listitem><para>Instance type preferences. &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></listitem>
-        <listitem><para>Vertical and horizontal allocation.
-            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.</para></listitem>
-        <listitem><para>End user preferences.
-            Users can not control exactly which host will run a given VM instance,
-            but they can specify a zone for the VM.
-            &PRODUCT; is then restricted to allocating the VM only to one of the hosts in that zone.</para></listitem>
-        <listitem><para>Host tags. The administrator can assign tags to hosts. These tags can be used to
-            specify which host a VM should use.
-            The &PRODUCT; administrator decides whether to define host tags, then create a service offering using those tags and offer it to the user.
-        </para></listitem>
-        <listitem><para>Affinity groups.
-            By defining affinity groups and assigning VMs to them, the user or administrator can
-            influence (but not dictate) which VMs should run on separate hosts.
-            This feature is to let users specify that certain VMs won't be on the same host.</para></listitem>
-        <listitem><para>&PRODUCT; also provides a pluggable interface for adding new allocators.
-            These custom allocators can provide any policy the administrator desires.</para></listitem>
-    </itemizedlist>
-    <section id="affinity-groups">
-        <title>Affinity Groups</title>
-        <para>By defining affinity groups and assigning VMs to them, the user or administrator can
-            influence (but not dictate) which VMs should run on separate hosts.
-            This feature is to let users specify that VMs with the same “host anti-affinity” type won’t be on the same host.
-            This serves to increase fault tolerance.
-            If a host fails, another VM offering the same service (for example, hosting the user's website) is still up and running on another host.</para>
-        <para>The scope of an affinity group is per user account.</para>
-        <formalpara><title>Creating a New Affinity Group</title>
-            <para>To add an affinity group:</para></formalpara>
-        <orderedlist>
-            <listitem><para>Log in to the &PRODUCT; UI as an administrator or user.</para></listitem>
-            <listitem><para>In the left navigation bar, click Affinity Groups.</para></listitem>
-            <listitem><para>Click Add affinity group. In the dialog box, fill in the following fields:</para>
-                <itemizedlist>
-                    <listitem><para>Name. Give the group a name.</para></listitem>
-                    <listitem><para>Description. Any desired text to tell more about the purpose of the group.</para></listitem>
-                    <listitem><para>Type. The only supported type shipped with &PRODUCT; is Host Anti-Affinity.
-                        This indicates that the VMs in this group should avoid being placed on the same VM with each other.
-                        If you see other types in this list, it means that your installation of &PRODUCT; has been extended
-                        with customized affinity group plugins.</para></listitem>
-                </itemizedlist>
-            </listitem>
-        </orderedlist>
-        <formalpara><title>Assign a New VM to an Affinity Group</title>
-            <para>To assign a new VM to an affinity group:</para></formalpara>
-        <itemizedlist>
-            <listitem><para>Create the VM as usual, as described in <xref linkend="creating-vms"/>.
-                In the Add Instance wizard, there is a new Affinity tab where you can select the affinity group.</para></listitem>
-        </itemizedlist>
-        <formalpara><title>Change Affinity Group for an Existing VM</title>
-            <para>To assign an existing VM to an affinity group:</para></formalpara>
-        <orderedlist>
-            <listitem><para>Log in to the &PRODUCT; UI as an administrator or user.</para></listitem>
-            <listitem><para>In the left navigation bar, click Instances.</para></listitem>
-            <listitem><para>Click the name of the VM you want to work with.</para></listitem>
-            <listitem><para>Stop the VM by clicking the Stop button.</para></listitem>
-            <listitem><para>Click the Change Affinity button. <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="./images/change-affinity-button.png"/>
-                </imageobject>
-                <textobject>
-                    <phrase>change-affinity-button.png: button to assign an affinity group
-                        to a virtual machine</phrase>
-                </textobject>
-            </inlinemediaobject>
-            </para></listitem>
-        </orderedlist>
-        <formalpara><title>View Members of an Affinity Group</title>
-            <para>To see which VMs are currently assigned to a particular affinity group:</para></formalpara>
-        <orderedlist>
-            <listitem><para>In the left navigation bar, click Affinity Groups.</para></listitem>
-            <listitem><para>Click the name of the group you are interested in.</para></listitem>
-            <listitem><para>Click View Instances. The members of the group are listed.</para>
-                <para>From here, you can click the name of any VM in the list to access all its details and controls.</para></listitem>
-        </orderedlist>
-        <formalpara><title>Delete an Affinity Group</title>
-            <para>To delete an affinity group:</para></formalpara>
-        <orderedlist>
-            <listitem><para>In the left navigation bar, click Affinity Groups.</para></listitem>
-            <listitem><para>Click the name of the group you are interested in.</para></listitem>
-            <listitem><para>Click Delete.</para>
-                <para>Any VM that is a member of the affinity group will be disassociated from the group.
-                    The former group members will continue to run normally on the current hosts, but if the
-                    VM is restarted, it will no longer follow the host allocation rules from its former
-                    affinity group.</para></listitem>
-        </orderedlist>
-    </section>
-</section>    

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hyperv-agent-install.xml
----------------------------------------------------------------------
diff --git a/en-US/hyperv-agent-install.xml b/en-US/hyperv-agent-install.xml
deleted file mode 100644
index 1bec8ed..0000000
--- a/en-US/hyperv-agent-install.xml
+++ /dev/null
@@ -1,70 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="hyperv-agent-install">
-  <title>Installing the &PRODUCT; Agent on a Hyper-V Host</title>
-  <para>The Hyper-V Agent helps &PRODUCT; perform operations on the Hyper-V hosts. This Agent
-    communicates with the Management Server and controls all the instances on the host. Each Hyper-V
-    host must have the Hyper-V Agent installed on it for successful interaction between the host and
-    &PRODUCT;. The Hyper-V Agent runs as a Windows service. Install the Agent on each host using the
-    following steps.</para>
-  <para>&PRODUCT; Management Server communicates with Hyper-V Agent by using HTTPS. For secure
-    communication between the Management Server and the host, install a self-signed certificate on
-    port 8250.</para>
-  <note>
-    <para>The Agent installer automatically perform this operation. You have not selected this
-      option during the Agent installation, it can also be done manually as given in step 1.</para>
-  </note>
-  <para/>
-  <orderedlist>
-    <listitem>
-      <para>Create and add a self-signed SSL certificate on port 8250:</para>
-      <orderedlist numeration="loweralpha" id="ssl-agent">
-        <listitem>
-          <para>Create A self-signed SSL certificate:</para>
-          <programlisting>#  New-SelfSignedCertificate -DnsName apachecloudstack -CertStoreLocation Cert:\LocalMachine\My</programlisting>
-          <para>This command creates the self-signed certificate and add that to the certificate
-            store <filename>LocalMachine\My</filename>.</para>
-        </listitem>
-        <listitem>
-          <para>Add the created certificate to port 8250 for https communication:</para>
-          <programlisting>netsh http add sslcert ipport=0.0.0.0:8250 certhash=&lt;thumbprint&gt; appid="{727beb1c-6e7c-49b2-8fbd-f03dbe481b08}"</programlisting>
-          <para>Thumbprint is the thumbprint of the certificate you created.</para>
-        </listitem>
-      </orderedlist>
-    </listitem>
-    <listitem>
-      <para>Build the CloudStack Agent for Hyper-V as given in <ulink
-          url="https://cwiki.apache.org/confluence/display/CLOUDSTACK/Creating+Hyperv+Agent+Installer"
-          >Building CloudStack Hyper-V Agent</ulink>.</para>
-    </listitem>
-    <listitem>
-      <para>As an administrator, run the installer.</para>
-    </listitem>
-    <listitem>
-      <para>Provide the Hyper-V admin credentials when prompted.</para>
-      <para>When the agent installation is finished, the agent runs as a service on the host
-        machine.</para>
-    </listitem>
-  </orderedlist>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hyperv-checklist.xml
----------------------------------------------------------------------
diff --git a/en-US/hyperv-checklist.xml b/en-US/hyperv-checklist.xml
deleted file mode 100644
index 4873736..0000000
--- a/en-US/hyperv-checklist.xml
+++ /dev/null
@@ -1,145 +0,0 @@
-<?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;
-]>
-
-<!-- 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.
--->
-<section id="hyperv-checklist">
-  <title>Preparation Checklist for Hyper-V</title>
-  <para>For a smoother installation, gather the following information before you start:</para>
-  <informaltable frame="all">
-    <tgroup cols="3" align="left" colsep="1" rowsep="1">
-      <colspec colname="c1" colwidth="1.22*"/>
-      <colspec colname="c2" colwidth="1.0*"/>
-      <colspec colname="c3" colwidth="6.05*"/>
-      <thead>
-        <row>
-          <entry><para>Hyper-V Requirements</para></entry>
-          <entry><para>Value</para></entry>
-          <entry><para>Description</para></entry>
-        </row>
-      </thead>
-      <tbody>
-        <row>
-          <entry><para>Server Roles</para></entry>
-          <entry><para>Hyper-V</para></entry>
-          <entry><para>After the Windows Server 2012 R2 installation, ensure that Hyper-V is
-              selected from Server Roles. For more information, see <ulink
-                url="http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step2">Installing
-                Hyper-V</ulink>.</para></entry>
-        </row>
-        <row>
-          <entry><para>Share Location</para></entry>
-          <entry><para>New folders in the /Share directory</para></entry>
-          <entry><para>Ensure that folders are created for Primary and Secondary storage. The SMB
-              share and the hosts should be part of the same domain.</para>
-            <para>If you are using Windows SMB share, the location of the file share for the Hyper-V
-              deployment will be the new folder created in the \Shares on the selected volume. You
-              can create sub-folders for both &PRODUCT; Primary and Secondary storage within the
-              share location. When you select the profile for the file shares, ensure that you
-              select SMB Share -Applications. This creates the file shares with settings appropriate
-              for Hyper-V.</para></entry>
-        </row>
-        <row>
-          <entry><para>Domain and Hosts</para></entry>
-          <entry><para/></entry>
-          <entry><para>Hosts should be part of the same Active Directory domain.</para></entry>
-        </row>
-        <row>
-          <entry><para>Hyper-V Users</para></entry>
-          <entry><para>Full control</para></entry>
-          <entry><para>Full control on the SMB file share.</para></entry>
-        </row>
-        <row>
-          <entry><para>Virtual Switch</para></entry>
-          <entry><para/></entry>
-          <entry><para>If you are using Hyper-V 2012 R2, manually create an external virtual switch
-              before adding the host to &PRODUCT;. If the Hyper-V host is added to the Hyper-V
-              manager, select the host, then click Virtual Switch Manager, then New Virtual Switch.
-              In the External Network, select the desired NIC adapter and click Apply. </para>
-            <para>If you are using Windows 2012 R2, virtual switch is created
-            automatically.</para></entry>
-        </row>
-        <row>
-          <entry><para>Virtual Switch Name</para></entry>
-          <entry><para/></entry>
-          <entry><para>Take a note of the name of the virtual switch. You need to specify that when
-              configuring &PRODUCT; physical network labels.</para></entry>
-        </row>
-        <row>
-          <entry><para>Hyper-V Domain Users</para></entry>
-          <entry><para/></entry>
-          <entry>
-            <itemizedlist>
-              <listitem>
-                <para>Add the Hyper-V domain users to the Hyper-V Administrators group.</para>
-              </listitem>
-              <listitem>
-                <para>A domain user should have full control on the SMB share that is exported for
-                  primary and secondary storage. </para>
-              </listitem>
-              <listitem>
-                <para>This domain user should be part of the Hyper-V Administrators and Local
-                  Administrators group on the Hyper-V hosts that are to be managed by
-                  &PRODUCT;.</para>
-              </listitem>
-              <listitem>
-                <para>The Hyper-V Agent service runs with the credentials of this domain user
-                  account.</para>
-              </listitem>
-              <listitem>
-                <para>Specify the credential of the domain user while adding a host to &PRODUCT; so
-                  that it can manage it.</para>
-              </listitem>
-              <listitem>
-                <para>Specify the credential of the domain user while adding a shared SMB primary or
-                  secondary storage.</para>
-              </listitem>
-            </itemizedlist>
-          </entry>
-        </row>
-        <row>
-          <entry><para>Migration</para></entry>
-          <entry><para>Migration</para></entry>
-          <entry><para>Enable Migration.</para>
-          </entry>
-        </row>
-        <row>
-          <entry><para>Migration</para></entry>
-          <entry><para>Delegation</para></entry>
-          <entry><para>If you want to use Live Migration, enable Delegation. Enable the following services of other
-              hosts participating in Live Migration: CIFS and Microsoft Virtual System Migration
-              Service.</para>
-          </entry>
-        </row>
-        <row>
-          <entry><para>Migration</para></entry>
-          <entry><para>Kerberos</para></entry>
-          <entry><para>Enable Kerberos for Live Migration.</para></entry>
-        </row>
-        <row>
-          <entry><para>Network Access Permission for Dial-in</para></entry>
-          <entry><para>Allow access</para></entry>
-          <entry><para>Allow access for Dial-in connections.</para></entry>
-        </row>
-      </tbody>
-    </tgroup>
-  </informaltable>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hyperv-host-add.xml
----------------------------------------------------------------------
diff --git a/en-US/hyperv-host-add.xml b/en-US/hyperv-host-add.xml
deleted file mode 100644
index 738515e..0000000
--- a/en-US/hyperv-host-add.xml
+++ /dev/null
@@ -1,91 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="hyperv-host-add">
-  <title>Adding a Hyper-V Host</title>
-  <orderedlist>
-    <listitem>
-      <para>Before adding a host to the &PRODUCT; configuration, ensure that you install Hyper-V on
-        the host.</para>
-      <warning>
-        <para>Be sure you have performed the additional &PRODUCT;-specific configuration steps
-          described in the Hyper-V installation section.</para>
-      </warning>
-      <para/>
-    </listitem>
-    <listitem>
-      <para>If you have not already done so, install Hyper-V 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;. For more
-        information, see the Prerequisites section in the 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><emphasis role="bold">Host Name</emphasis>: The DNS name or IP address of the host.
-          </para>
-        </listitem>
-        <listitem>
-          <para><emphasis role="bold">Username</emphasis>: Username of the domain user you created.
-            Specify domain name in the path. For example, domain 1\ admin.</para>
-        </listitem>
-        <listitem>
-          <para><emphasis role="bold">Password</emphasis>: This is the password for the user named
-            above.</para>
-        </listitem>
-        <listitem>
-          <para><emphasis role="bold">Host Tags</emphasis> (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>
-  </orderedlist>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hyperv-install-network.xml
----------------------------------------------------------------------
diff --git a/en-US/hyperv-install-network.xml b/en-US/hyperv-install-network.xml
deleted file mode 100644
index 1ea2b40..0000000
--- a/en-US/hyperv-install-network.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="hyperv-install-network">
-  <title>Physical Network Configuration for Hyper-V</title>
-  <para>You should have a plan for how the hosts will be cabled and which physical NICs will carry
-    what types of traffic. By default, &PRODUCT; will use the device that is used for the default
-    route.</para>
-  <para>If you are using Hyper-V 2012 R2, manually create an external virtual switch before adding
-    the host to &PRODUCT;. If the Hyper-V host is added to the Hyper-V manager, select the host,
-    then click Virtual Switch Manager, then New Virtual Switch. In the External Network, select the
-    desired NIC adapter and click Apply. </para>
-  <para>If you are using Windows 2012 R2, virtual switch is created automatically.</para>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hyperv-install-steps.xml
----------------------------------------------------------------------
diff --git a/en-US/hyperv-install-steps.xml b/en-US/hyperv-install-steps.xml
deleted file mode 100644
index a981862..0000000
--- a/en-US/hyperv-install-steps.xml
+++ /dev/null
@@ -1,79 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="hyperv-install-steps">
-  <title>Hyper-V Installation Steps</title>
-  <orderedlist>
-    <listitem>
-      <para>Download the operating system from <ulink
-          url="http://technet.microsoft.com/en-us/windowsserver/hh534429">Windows Server 2012
-          R2</ulink> .</para>
-    </listitem>
-    <listitem>
-      <para>Install it on the host as given in <ulink
-          url="http://technet.microsoft.com/library/hh831620">Install and Deploy Windows Server 2012
-          R2</ulink>.</para>
-    </listitem>
-    <listitem>
-      <para>Post installation, ensure that you enable Hyper-V role in the server.</para>
-    </listitem>
-    <listitem>
-      <para>If no Active Directory domain exists in your deployment, create one and add users to the
-        domain.</para>
-    </listitem>
-    <listitem>
-      <para>In the Active Directory domain, ensure that all the Hyper-v hosts are added so that all
-        the hosts are part of the domain.</para>
-    </listitem>
-    <listitem>
-      <para>Add the domain user to the following groups on the Hyper-V host: Hyper-V Administrators
-        and Local Administrators.</para>
-    </listitem>
-    <listitem>
-      <para>After installation, perform the following configuration tasks, which are described in
-        the next few sections.</para>
-    </listitem>
-  </orderedlist>
-  <informaltable>
-    <tgroup cols="2" align="left" colsep="1" rowsep="1">
-      <colspec colwidth="1.0*" colname="1" colnum="1"/>
-      <colspec colwidth="3.76*" colname="2" colnum="2"/>
-      <thead>
-        <row>
-          <entry><para>Required</para></entry>
-          <entry><para>Optional</para></entry>
-        </row>
-      </thead>
-      <tbody>
-        <row>
-          <entry><para><xref linkend="hyperv-agent-install"/></para></entry>
-          <entry><para><xref linkend="hyperv-install-storage"/></para></entry>
-        </row>
-        <row>
-          <entry><para><xref linkend="hyperv-install-network"/></para></entry>
-          <entry><para/></entry>
-        </row>
-      </tbody>
-    </tgroup>
-  </informaltable>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hyperv-install-storage.xml
----------------------------------------------------------------------
diff --git a/en-US/hyperv-install-storage.xml b/en-US/hyperv-install-storage.xml
deleted file mode 100644
index d49f285..0000000
--- a/en-US/hyperv-install-storage.xml
+++ /dev/null
@@ -1,51 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="hyperv-install-storage">
-  <title>Storage Preparation for Hyper-V (Optional)</title>
-  <para>&PRODUCT; allows administrators to set up shared Primary Storage and Secondary Storage that
-    uses SMB.</para>
-  <orderedlist>
-    <listitem>
-      <para>Create a SMB storage and expose it over SMB Version 3.</para>
-      <para>For more information, see <ulink
-          url="http://technet.microsoft.com/en-us/library/jj134187.aspx">Deploying Hyper-V over
-          SMB</ulink>.</para>
-      <para>You can also create and export SMB share using Windows. After the Windows Server 2012 R2
-        installation, select File and Storage Services from Server Roles to create an SMB file
-        share. For more information, see <ulink
-          url="http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step3">Creating an SMB
-          File Share Using Server Manager</ulink>.</para>
-    </listitem>
-    <listitem>
-      <para>Add the SMB share to the Active Directory domain.</para>
-      <para>The SMB share and the hosts managed by &PRODUCT; need to be in the same domain. However,
-        the storage should be accessible from the Management Server with the domain user privileges.
-      </para>
-    </listitem>
-    <listitem>
-      <para>While adding storage to &PRODUCT;, ensure that the correct domain, and credentials are
-        supplied. This user should be able to access the storage from the Management Server.</para>
-    </listitem>
-  </orderedlist>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hyperv-install.xml
----------------------------------------------------------------------
diff --git a/en-US/hyperv-install.xml b/en-US/hyperv-install.xml
deleted file mode 100644
index 384c026..0000000
--- a/en-US/hyperv-install.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<chapter id="hyperv-install">
-  <title>Installing Hyper-V for &PRODUCT;</title>
-  <para>If you want to use Hyper-V hypervisor to run guest virtual machines, install Hyper-V on the
-    hosts in your cloud. The instructions in this section doesn't duplicate Hyper-V Installation
-    documentation. It provides the &PRODUCT;-specific steps that are needed to prepare a Hyper-V
-    host to work with &PRODUCT;.</para>
-  <xi:include href="hyperv-requirements.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="hyperv-checklist.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="hyperv-install-steps.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="hyperv-agent-install.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="hyperv-install-network.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="hyperv-install-storage.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-</chapter>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hyperv-maintenance-mode.xml
----------------------------------------------------------------------
diff --git a/en-US/hyperv-maintenance-mode.xml b/en-US/hyperv-maintenance-mode.xml
deleted file mode 100644
index 75e4d42..0000000
--- a/en-US/hyperv-maintenance-mode.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="hyperv-maintenance-mode.xml">
-  <title>Hyper-V Maintenance Mode</title>
-  <para>For &PRODUCT; 4.3, the Hyper-V version certified is the latest: Windows Server 2012 R2 (with
-    Hyper-V Role enabled) and Hyper-V Server 2012 R2. For subsequent releases or upgrades from
-    Microsoft, you can perform the similar maintenance procedure for Hyper-V hosts: place a host to
-    maintenance mode, perform necessary upgrades and then add the host back.</para>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hyperv-migration-req.xml
----------------------------------------------------------------------
diff --git a/en-US/hyperv-migration-req.xml b/en-US/hyperv-migration-req.xml
deleted file mode 100644
index c589b7e..0000000
--- a/en-US/hyperv-migration-req.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-<!-- 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.
--->
-<section id="hyperv-migration-req">
-  <title>Hyper-V Migration Requirements</title>
-  <itemizedlist>
-    <listitem>
-      <para>If you want to use Live Migration, enable Delegation. For example, if you have two
-        hosts, perform the following: Come to the domain controller, go to each host and perform: 1
-        Properties > Delegation > add the following Services running on host 2: cifs Microsoft
-        Virtual System Migration Service Select Microsoft Virtual System Migration service.</para>
-    </listitem>
-    <listitem>
-      <para/>
-    </listitem>
-    <listitem>
-      <para/>
-    </listitem>
-    <listitem>
-      <para/>
-    </listitem>
-    <listitem>
-      <para/>
-    </listitem>
-  </itemizedlist>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hyperv-requirements.xml
----------------------------------------------------------------------
diff --git a/en-US/hyperv-requirements.xml b/en-US/hyperv-requirements.xml
deleted file mode 100644
index 312708d..0000000
--- a/en-US/hyperv-requirements.xml
+++ /dev/null
@@ -1,69 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="hyperv-requirements">
-  <title>System Requirements for Hyper-V Hypervisor Hosts</title>
-  <para/>
-  <section id="hyperv-supported-os">
-    <title>Supported Operating Systems for Hyper-V Hosts</title>
-    <itemizedlist>
-      <listitem>
-        <para>Windows Server 2012 R2 Standard</para>
-      </listitem>
-      <listitem>
-        <para>Windows Server 2012 R2 Datacenter</para>
-      </listitem>
-      <listitem>
-        <para>Hyper-V 2012 R2</para>
-      </listitem>
-    </itemizedlist>
-  </section>
-  <section id="hyperv-hardware-req">
-    <title>Minimum System Requirements for Hyper-V Hosts</title>
-    <itemizedlist>
-      <listitem>
-        <para>1.4 GHz 64-bit processor with hardware-assisted virtualization.</para>
-      </listitem>
-      <listitem>
-        <para>800 MB of RAM</para>
-      </listitem>
-      <listitem>
-        <para>32 GB of disk space</para>
-      </listitem>
-      <listitem>
-        <para>Gigabit (10/100/1000baseT) Ethernet adapter</para>
-      </listitem>
-    </itemizedlist>
-  </section>
-  <section id="storage">
-    <title>Supported Storage</title>
-    <itemizedlist>
-      <listitem>
-        <para>Primary Storage: Server Message Block (SMB) Version 3, Local</para>
-      </listitem>
-      <listitem>
-        <para>Secondary Storage: SMB</para>
-      </listitem>
-    </itemizedlist>
-  </section>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hyperv-topology-req.xml
----------------------------------------------------------------------
diff --git a/en-US/hyperv-topology-req.xml b/en-US/hyperv-topology-req.xml
deleted file mode 100644
index d97dc6e..0000000
--- a/en-US/hyperv-topology-req.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-<!-- 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.
--->
-<section id="hyperv-topology-req">
-  <title>Hyper-V Topology Requirements</title>
-  <para>&PRODUCT; Management Server communicates with Hyper-V Agent by using HTTPS. For secure
-    communication between the Management Server and the Hyper-V host, open port 8250.</para>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hypervisor-host-install-agent.xml
----------------------------------------------------------------------
diff --git a/en-US/hypervisor-host-install-agent.xml b/en-US/hypervisor-host-install-agent.xml
deleted file mode 100644
index e339165..0000000
--- a/en-US/hypervisor-host-install-agent.xml
+++ /dev/null
@@ -1,79 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="hypervisor-host-install-agent">
-    <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 cloudstack-agent</command></programlisting>
-    <para>In Ubuntu:</para>
-    <programlisting language="Bash"><command>$ apt-get install cloudstack-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 id="config-cpu-model">
-        <title>Configure CPU model for KVM guest (Optional) </title>
-    <para>In additional,the &PRODUCT; Agent allows host administrator to control the guest CPU model which is exposed to KVM instances. By default, the CPU model of KVM instance is likely <emphasis role="italic"> QEMU Virtual CPU version x.x.x</emphasis> with least CPU features exposed. There are a couple of reasons to specify the CPU model:</para>
-    <itemizedlist>
-        <listitem><para>To maximise performance of instances by exposing new host CPU features to the KVM instances;</para>    </listitem>
-        <listitem><para>To ensure a consistent default CPU across all machines,removing reliance of variable QEMU defaults;    </para> </listitem>
-    </itemizedlist>
-    <para> For the most part it will be sufficient for the host administrator to specify the guest CPU config in the per-host configuration file (/etc/cloudstack/agent/agent.properties). This will be achieved by introducing two new configuration parameters: </para>
-    <programlisting language="Bash">guest.cpu.mode=custom|host-model|host-passthrough
-guest.cpu.model=from /usr/share/libvirt/cpu_map.xml(only valid when guest.cpu.mode=custom)
-    </programlisting>
-    <para>There are three choices to fulfill the cpu model changes:</para>
-    <orderedlist>
-        <listitem>
-            <para><emphasis role="bold">custom: </emphasis> you can explicitly specify one of the supported named model in /usr/share/libvirt/cpu_map.xml</para>
-        </listitem>
-        <listitem>
-            <para><emphasis role="bold">host-model: </emphasis> libvirt will identify the CPU model in /usr/share/libvirt/cpu_map.xml which most closely matches the host, and then request additional CPU flags to complete the match. This should give close to maximum functionality/performance, which maintaining good reliability/compatibility if the guest is migrated to another host with slightly different host CPUs.  </para>
-        </listitem>
-        <listitem>
-            <para><emphasis role="bold">host-passthrough: </emphasis> libvirt will tell KVM to passthrough the host CPU with no modifications. The difference to host-model, instead of just matching feature flags, every last detail of the host CPU is matched. This gives absolutely best performance, and can be important to some apps which check low level CPU details, but it comes at a cost with respect to migration: the guest can only be migrated to an exactly matching host CPU.  </para>
-        </listitem>
-    </orderedlist>
-    <para>Here are some examples:</para>
-    <itemizedlist>
-        <listitem>
-            <para>custom</para>
-            <programlisting>guest.cpu.mode=custom
-guest.cpu.model=SandyBridge
-            </programlisting>
-        </listitem>
-        <listitem>
-            <para>host-model</para>
-            <programlisting>guest.cpu.mode=host-model </programlisting>
-        </listitem>
-        <listitem>
-            <para>host-passthrough</para>
-            <programlisting>guest.cpu.mode=host-passthrough </programlisting>
-        </listitem>
-    </itemizedlist>
-    <note>
-        <para>host-passthrough may lead to migration failure,if you have this problem,you should use host-model or custom </para>
-    </note>
-</section>
-
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hypervisor-host-install-finish.xml
----------------------------------------------------------------------
diff --git a/en-US/hypervisor-host-install-finish.xml b/en-US/hypervisor-host-install-finish.xml
deleted file mode 100644
index ff530c7..0000000
--- a/en-US/hypervisor-host-install-finish.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="hypervisor-host-install-finish">
-    <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/cloudstack-docs/blob/f42520a5/en-US/hypervisor-host-install-firewall.xml
----------------------------------------------------------------------
diff --git a/en-US/hypervisor-host-install-firewall.xml b/en-US/hypervisor-host-install-firewall.xml
deleted file mode 100644
index c665873..0000000
--- a/en-US/hypervisor-host-install-firewall.xml
+++ /dev/null
@@ -1,59 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="hypervisor-host-install-firewall">
-    <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>
-        <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 > /etc/sysconfig/iptables</command></programlisting>
-    </section>
-    <section>
-        <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/cloudstack-docs/blob/f42520a5/en-US/hypervisor-host-install-libvirt.xml
----------------------------------------------------------------------
diff --git a/en-US/hypervisor-host-install-libvirt.xml b/en-US/hypervisor-host-install-libvirt.xml
deleted file mode 100644
index d3d6b9b..0000000
--- a/en-US/hypervisor-host-install-libvirt.xml
+++ /dev/null
@@ -1,57 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="hypervisor-host-install-libvirt">
-    <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 cloudstack-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 parameters:</para>
-            <programlisting>listen_tls = 0</programlisting>
-            <programlisting>listen_tcp = 1</programlisting>
-            <programlisting>tcp_port = "16509"</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/default/libvirt-bin</filename></para>
-            <para>Add "-l" to the following line::</para>
-            <programlisting>libvirtd_opts="-d"</programlisting>
-            <para>so it looks like:</para>
-            <programlisting>libvirtd_opts="-d -l"</programlisting>
-        </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/cloudstack-docs/blob/f42520a5/en-US/hypervisor-host-install-network-openvswitch.xml
----------------------------------------------------------------------
diff --git a/en-US/hypervisor-host-install-network-openvswitch.xml b/en-US/hypervisor-host-install-network-openvswitch.xml
deleted file mode 100644
index a16dc8e..0000000
--- a/en-US/hypervisor-host-install-network-openvswitch.xml
+++ /dev/null
@@ -1,116 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="hypervisor-host-install-network-openvswitch">
-    <title>Configure the network using OpenVswitch</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-openvswitch-prepare">
-        <title>Preparing</title>
-        <para>To make sure that the native bridge module will not interfere with openvswitch the bridge module should be added to the blacklist. See the modprobe documentation for your distribution on where to find the blacklist. Make sure the module is not loaded either by rebooting or executing rmmod bridge before executing next steps.</para>
-        <para>The network configurations below depend on the ifup-ovs and ifdown-ovs scripts which are part of the openvswitch installation. They should be installed in /etc/sysconfig/network-scripts/</para>
-    </section>        
-    <section id="hypervisor-host-install-network-openvswitch-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-openvswitch-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.</para>
-        <note><para>The goal is to have three bridges called 'mgmt0', '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-openvswitch-configure-ovs">
-            <title>Configure OpenVswitch</title>
-            <para>The network interfaces using OpenVswitch are created using the ovs-vsctl command. This command will configure the interfaces and persist them to the OpenVswitch database.</para>
-            <para>First we create a main bridge connected to the eth0 interface. Next we create three fake bridges, each connected to a specific vlan tag.</para>
-            <programlisting><![CDATA[# ovs-vsctl add-br cloudbr
-# ovs-vsctl add-port cloudbr eth0 
-# ovs-vsctl set port cloudbr trunks=100,200,300
-# ovs-vsctl add-br mgmt0 cloudbr 100
-# ovs-vsctl add-br cloudbr0 cloudbr 200
-# ovs-vsctl add-br cloudbr1 cloudbr 300]]></programlisting>
-        </section>
-        <section id="hypervisor-host-install-network-openvswitch-configure-rhel">
-            <title>Configure in RHEL or CentOS</title>
-            <para>The required packages were installed when openvswitch and libvirt were 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 similar to:</para>
-            <programlisting><![CDATA[DEVICE=eth0
-HWADDR=00:04:xx:xx:xx:xx
-ONBOOT=yes
-HOTPLUG=no
-BOOTPROTO=none
-TYPE=Ethernet]]></programlisting>
-            <para>We have to configure the base bridge with the trunk.</para>
-            <programlisting language="Bash">vi /etc/sysconfig/network-scripts/ifcfg-cloudbr</programlisting>
-            <programlisting><![CDATA[DEVICE=cloudbr
-ONBOOT=yes
-HOTPLUG=no
-BOOTPROTO=none
-DEVICETYPE=ovs
-TYPE=OVSBridge]]></programlisting>
-            <para>We now have to configure the three VLAN bridges:</para>
-            <programlisting language="Bash">vi /etc/sysconfig/network-scripts/ifcfg-mgmt0</programlisting>
-            <programlisting><![CDATA[DEVICE=mgmt0
-ONBOOT=yes
-HOTPLUG=no
-BOOTPROTO=static
-DEVICETYPE=ovs
-TYPE=OVSBridge
-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-cloudbr0</programlisting>
-            <programlisting><![CDATA[DEVICE=cloudbr0
-ONBOOT=yes
-HOTPLUG=no
-BOOTPROTO=none
-DEVICETYPE=ovs
-TYPE=OVSBridge]]></programlisting>
-            <programlisting language="Bash">vi /etc/sysconfig/network-scripts/ifcfg-cloudbr1</programlisting>
-            <programlisting><![CDATA[DEVICE=cloudbr1
-ONBOOT=yes
-HOTPLUG=no
-BOOTPROTO=none
-TYPE=OVSBridge
-DEVICETYPE=ovs]]></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/cloudstack-docs/blob/f42520a5/en-US/hypervisor-host-install-network.xml
----------------------------------------------------------------------
diff --git a/en-US/hypervisor-host-install-network.xml b/en-US/hypervisor-host-install-network.xml
deleted file mode 100644
index 80156d9..0000000
--- a/en-US/hypervisor-host-install-network.xml
+++ /dev/null
@@ -1,150 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="hypervisor-host-install-network">
-    <title>Configure the network bridges</title>
-    <warning><para>This is a very important section, please make sure you read this thoroughly.</para></warning>
-    <note><para>This section details how to configure bridges using the native implementation in Linux. Please refer to the next section if you intend to use OpenVswitch</para></note>
-    <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>
-        <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>
-        <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>
-            <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 similar to:</para>
-            <programlisting><![CDATA[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><![CDATA[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><![CDATA[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><![CDATA[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-Address</para>
-            <programlisting><![CDATA[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><![CDATA[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>
-            <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><![CDATA[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/cloudstack-docs/blob/f42520a5/en-US/hypervisor-host-install-overview.xml
----------------------------------------------------------------------
diff --git a/en-US/hypervisor-host-install-overview.xml b/en-US/hypervisor-host-install-overview.xml
deleted file mode 100644
index 716b43d..0000000
--- a/en-US/hypervisor-host-install-overview.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="hypervisor-host-install-overview">
-    <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>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hypervisor-host-install-prepare-os.xml
----------------------------------------------------------------------
diff --git a/en-US/hypervisor-host-install-prepare-os.xml b/en-US/hypervisor-host-install-prepare-os.xml
deleted file mode 100644
index 44852f2..0000000
--- a/en-US/hypervisor-host-install-prepare-os.xml
+++ /dev/null
@@ -1,53 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="hypervisor-host-install-prepare-os">
-    <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>
-                        <para condition="community">On RHEL or CentOS:</para>
-                        <programlisting language="Bash"><command>$ yum install ntp</command></programlisting>
-                        <para condition="community">On Ubuntu:</para>
-                        <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>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hypervisor-host-install-security-policies.xml
----------------------------------------------------------------------
diff --git a/en-US/hypervisor-host-install-security-policies.xml b/en-US/hypervisor-host-install-security-policies.xml
deleted file mode 100644
index 03da04b..0000000
--- a/en-US/hypervisor-host-install-security-policies.xml
+++ /dev/null
@@ -1,70 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="hypervisor-host-install-security-policies">
-    <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>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hypervisor-installation.xml
----------------------------------------------------------------------
diff --git a/en-US/hypervisor-installation.xml b/en-US/hypervisor-installation.xml
deleted file mode 100644
index 341322c..0000000
--- a/en-US/hypervisor-installation.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-<?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 "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<chapter id="hypervisor-installation">
-  <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="hyperv-install.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"/> -->
-  <xi:include href="lxc-install.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-</chapter>


Mime
View raw message