cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From seb...@apache.org
Subject [29/51] [partial] cloudstack-docs git commit: Remove all old docbook files
Date Thu, 01 Oct 2015 14:04:39 GMT
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/limit-accounts-domains.xml
----------------------------------------------------------------------
diff --git a/en-US/limit-accounts-domains.xml b/en-US/limit-accounts-domains.xml
deleted file mode 100644
index 78a642b..0000000
--- a/en-US/limit-accounts-domains.xml
+++ /dev/null
@@ -1,371 +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="limit-accounts-domains">
-  <title>Limiting Resource Usage</title>
-  <para>&PRODUCT; allows you to control resource usage based on the types of resources, such as CPU,
-    RAM, Primary storage, and Secondary storage.  A new set of resource types has been added to the
-    existing pool of resources to support the new customization model&mdash;need-basis usage, such
-    as large VM or small VM. The new resource types are now broadly classified as CPU, RAM, Primary
-    storage, and Secondary storage. The root administrator is able to impose resource usage limit by
-    the following resource types for Domain, Project, and Accounts. </para>
-  <itemizedlist>
-    <listitem>
-      <para>CPUs</para>
-    </listitem>
-    <listitem>
-      <para>Memory (RAM)</para>
-    </listitem>
-    <listitem>
-      <para>Primary Storage (Volumes)</para>
-    </listitem>
-    <listitem>
-      <para>Secondary Storage (Snapshots, Templates, ISOs)</para>
-    </listitem>
-  </itemizedlist>
-  <para>To control the behaviour of this feature, the following configuration parameters have been
-    added:</para>
-  <informaltable>
-    <tgroup cols="2" align="left" colsep="1" rowsep="1">
-      <thead>
-        <row>
-          <entry><para>Parameter Name</para></entry>
-          <entry><para>Description</para></entry>
-        </row>
-      </thead>
-      <tbody>
-        <row>
-          <entry><para>max.account.cpus</para></entry>
-          <entry><para>Maximum number of CPU cores that can be used for an account. </para>
-            <para>Default is 40.</para></entry>
-        </row>
-        <row>
-          <entry><para>max.account.ram (MB)</para></entry>
-          <entry><para>Maximum RAM that can be used for an account. </para>
-            <para>Default is 40960.</para></entry>
-        </row>
-        <row>
-          <entry><para>max.account.primary.storage (GB)</para></entry>
-          <entry><para>Maximum primary storage space that can be used for an account. </para>
-            <para>Default is 200.</para>
-          </entry>
-        </row>
-        <row>
-          <entry><para>max.account.secondary.storage (GB)</para></entry>
-          <entry><para>Maximum secondary storage space that can be used for an account. </para>
-            <para>Default is 400.</para></entry>
-        </row>
-        <row>
-          <entry><para>max.project.cpus</para></entry>
-          <entry>
-            <para>Maximum number of CPU cores that can be used for an account. </para>
-            <para>Default is 40.</para>
-          </entry>
-        </row>
-        <row>
-          <entry><para>max.project.ram (MB)</para></entry>
-          <entry>
-            <para>Maximum RAM that can be used for an account. </para>
-            <para>Default is 40960.</para>
-          </entry>
-        </row>
-        <row>
-          <entry><para>max.project.primary.storage (GB)</para></entry>
-          <entry>
-            <para>Maximum primary storage space that can be used for an account. </para>
-            <para>Default is 200.</para>
-          </entry>
-        </row>
-        <row>
-          <entry><para>max.project.secondary.storage (GB)</para></entry>
-          <entry>
-            <para>Maximum secondary storage space that can be used for an account. </para>
-            <para>Default is 400.</para>
-          </entry>
-        </row>
-      </tbody>
-    </tgroup>
-  </informaltable>
-  <section id="user-permission-rn">
-    <title>User Permission</title>
-    <para>The root administrator, domain administrators and users are able to list resources. Ensure
-      that proper logs are maintained in the <filename>vmops.log</filename> and
-        <filename>api.log</filename> files.</para>
-    <itemizedlist>
-      <listitem>
-        <para>The root admin will have the privilege to list and update resource limits.</para>
-      </listitem>
-      <listitem>
-        <para>The domain administrators are allowed to list and change these resource limits only
-          for the sub-domains and accounts under their own domain or the sub-domains. </para>
-      </listitem>
-      <listitem>
-        <para>The end users will the privilege to list resource limits. Use the listResourceLimits
-          API.</para>
-      </listitem>
-    </itemizedlist>
-  </section>
-  <section id="consideration-rn">
-    <title>Limit Usage Considerations</title>
-    <itemizedlist>
-      <listitem>
-        <para>Primary or Secondary storage space refers to the stated size of the volume and not the
-          physical size&mdash; the actual consumed size on disk in case of thin provisioning.</para>
-      </listitem>
-      <listitem>
-        <para>If the admin reduces the resource limit for an account and set it to less than the
-          resources that are currently being consumed, the existing VMs/templates/volumes are not
-          destroyed. Limits are imposed only if the user under that account tries to execute a new
-          operation using any of these resources. For example, the existing behavior in the case of
-          a VM are: </para>
-        <itemizedlist>
-          <listitem>
-            <para>migrateVirtualMachine: The users under that account will be able to migrate the
-              running VM into any other host without facing any limit issue.</para>
-          </listitem>
-          <listitem>
-            <para>recoverVirtualMachine: Destroyed VMs cannot be recovered.</para>
-          </listitem>
-        </itemizedlist>
-      </listitem>
-      <listitem>
-        <para>For any resource type, if a domain has limit X, sub-domains or accounts under that
-          domain can have there own limits. However, the sum of resource allocated to a sub-domain
-          or accounts under the domain at any point of time should not exceed the value X.</para>
-        <para>For example, if a domain has the CPU limit of 40 and the sub-domain D1 and account A1
-          can have limits of 30 each, but at any point of time the resource allocated to D1 and A1
-          should not exceed the limit of 40.</para>
-      </listitem>
-      <listitem>
-        <para>If any operation needs to pass through two of more resource limit check, then the
-          lower of 2 limits will be enforced, For example: if an account has the VM limit of 10 and
-          CPU limit of 20, and a user under that account requests 5 VMs of 4 CPUs each.  The user
-          can deploy 5 more VMs because VM limit is 10. However, the user cannot deploy any more
-          instances because the CPU limit has been exhausted.</para>
-      </listitem>
-    </itemizedlist>
-  </section>
-  <section id="per-domain-limits">
-    <title>Limiting Resource Usage in a Domain</title>
-    <para>&PRODUCT; allows the configuration of limits on a domain basis. With a domain limit in
-      place, all users still have their account limits. They are additionally limited, as a group,
-      to not exceed the resource limits set on their domain. Domain limits aggregate the usage of
-      all accounts in the domain as well as all the accounts in all the sub-domains of that domain.
-      Limits set at the root domain level apply to the sum of resource usage by the accounts in all
-      the domains and sub-domains below that root domain.</para>
-    <para>To set a domain limit:</para>
-    <orderedlist>
-      <listitem>
-        <para>Log in to the &PRODUCT; UI.</para>
-      </listitem>
-      <listitem>
-        <para>In the left navigation tree, click Domains.</para>
-      </listitem>
-      <listitem>
-        <para>Select the domain you want to modify. The current domain limits are displayed. </para>
-        <para>A value of -1 shows that there is no limit in place.</para>
-      </listitem>
-      <listitem>
-        <para>Click the Edit button<inlinemediaobject>
-            <imageobject>
-              <imagedata fileref="./images/edit-icon.png"/>
-            </imageobject>
-            <textobject>
-              <phrase>editbutton.png: edits the settings.</phrase>
-            </textobject>
-          </inlinemediaobject></para>
-      </listitem>
-      <listitem>
-        <para>Edit the following as per your requirement:</para>
-        <informaltable>
-          <tgroup cols="2" align="left" colsep="1" rowsep="1">
-            <thead>
-              <row>
-                <entry><para>Parameter Name</para></entry>
-                <entry><para>Description</para></entry>
-              </row>
-            </thead>
-            <tbody>
-              <row>
-                <entry><para>Instance Limits</para></entry>
-                <entry><para>The number of instances that can be used in a domain.</para></entry>
-              </row>
-              <row>
-                <entry><para>Public IP Limits</para></entry>
-                <entry>
-                  <para>The number of public IP addresses that can be used in a
-                  domain.</para></entry>
-              </row>
-              <row>
-                <entry><para>Volume Limits</para></entry>
-                <entry><para>The number of disk volumes that can be created in a domain. </para>
-                </entry>
-              </row>
-              <row>
-                <entry><para>Snapshot Limits</para></entry>
-                <entry>The number of snapshots that can be created in a domain.</entry>
-              </row>
-              <row>
-                <entry><para>Template Limits</para></entry>
-                <entry><para>The number of templates that can be registered in a
-                  domain.</para></entry>
-              </row>
-              <row>
-                <entry><para>VPC limits</para></entry>
-                <entry><para>The number of VPCs that can be created in a domain.</para></entry>
-              </row>
-              <row>
-                <entry><para>CPU limits</para></entry>
-                <entry>
-                  <para>The number of CPU cores that can be used for a domain.</para>
-                </entry>
-              </row>
-              <row>
-                <entry><para>Memory limits (MB)</para></entry>
-                <entry>
-                  <para>The number of RAM that can be used for a domain.</para>
-                </entry>
-              </row>
-              <row>
-                <entry><para>Primary Storage limits (GB)</para></entry>
-                <entry>
-                  <para>The primary storage space that can be used for a domain.</para>
-                </entry>
-              </row>
-              <row>
-                <entry><para>Secondary Storage limits (GB)</para></entry>
-                <entry>
-                  <para>The secondary storage space that can be used for a domain.</para>
-                </entry>
-              </row>
-            </tbody>
-          </tgroup>
-        </informaltable>
-      </listitem>
-      <listitem>
-        <para>Click Apply.</para>
-      </listitem>
-    </orderedlist>
-  </section>
-  <section id="default-account-resource-limit">
-    <title>Default Account Resource Limits</title>
-    <para>You can limit resource use by accounts. The default limits are set by using Global
-      configuration parameters, and they affect all accounts within a cloud. The relevant parameters
-      are those beginning with max.account, for example: max.account.snapshots.</para>
-    <para>To override a default limit for a particular account, set a per-account resource
-      limit.</para>
-    <orderedlist>
-      <listitem>
-        <para>Log in to the &PRODUCT; UI.</para>
-      </listitem>
-      <listitem>
-        <para>In the left navigation tree, click Accounts.</para>
-      </listitem>
-      <listitem>
-        <para>Select the account you want to modify. The current limits are displayed. </para>
-        <para>A value of -1 shows that there is no limit in place.</para>
-      </listitem>
-      <listitem>
-        <para>Click the Edit button.<inlinemediaobject>
-            <imageobject>
-              <imagedata fileref="./images/edit-icon.png"/>
-            </imageobject>
-            <textobject>
-              <phrase>editbutton.png: edits the settings</phrase>
-            </textobject>
-          </inlinemediaobject></para>
-      </listitem>
-      <listitem>
-        <para>Edit the following as per your requirement:</para>
-        <informaltable>
-          <tgroup cols="2" align="left" colsep="1" rowsep="1">
-            <thead>
-              <row>
-                <entry><para>Parameter Name</para></entry>
-                <entry><para>Description</para></entry>
-              </row>
-            </thead>
-            <tbody>
-              <row>
-                <entry><para>Instance Limits</para></entry>
-                <entry><para>The number of instances that can be used in an account.</para>
-                  <para>The default is 20.</para></entry>
-              </row>
-              <row>
-                <entry><para>Public IP Limits</para></entry>
-                <entry>
-                  <para>The number of public IP addresses that can be used in an account.</para>
-                  <para>The default is 20.</para></entry>
-              </row>
-              <row>
-                <entry><para>Volume Limits</para></entry>
-                <entry><para>The number of disk volumes that can be created in an account.</para>
-                  <para>The default is 20.</para></entry>
-              </row>
-              <row>
-                <entry><para>Snapshot Limits</para></entry>
-                <entry><para>The number of snapshots that can be created in an account.</para>
-                  <para>The default is 20.</para></entry>
-              </row>
-              <row>
-                <entry><para>Template Limits</para></entry>
-                <entry><para>The number of templates that can be registered in an account.</para>
-                  <para>The default is 20.</para></entry>
-              </row>
-              <row>
-                <entry><para>VPC limits</para></entry>
-                <entry><para>The number of VPCs that can be created in an account.</para>
-                  <para>The default is 20.</para></entry>
-              </row>
-              <row>
-                <entry><para>CPU limits</para></entry>
-                <entry>
-                  <para>The number of CPU cores that can be used for an account.</para>
-                  <para>The default is 40.</para></entry>
-              </row>
-              <row>
-                <entry><para>Memory limits (MB)</para></entry>
-                <entry>
-                  <para>The number of RAM that can be used for an account.</para>
-                  <para>The default is 40960.</para></entry>
-              </row>
-              <row>
-                <entry><para>Primary Storage limits (GB)</para></entry>
-                <entry>
-                  <para>The primary storage space that can be used for an account.</para>
-                  <para>The default is 200.</para></entry>
-              </row>
-              <row>
-                <entry><para>Secondary Storage limits (GB)</para></entry>
-                <entry>
-                  <para>The secondary storage space that can be used for an account.</para>
-                  <para>The default is 400.</para></entry>
-              </row>
-            </tbody>
-          </tgroup>
-        </informaltable>
-      </listitem>
-      <listitem>
-        <para>Click Apply.</para>
-      </listitem>
-    </orderedlist>
-  </section>
-</section>

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

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/load-balancer-rules.xml
----------------------------------------------------------------------
diff --git a/en-US/load-balancer-rules.xml b/en-US/load-balancer-rules.xml
deleted file mode 100644
index 884647c..0000000
--- a/en-US/load-balancer-rules.xml
+++ /dev/null
@@ -1,41 +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="load-balancer-rules">
-  <title>Load Balancer Rules</title>
-  <para>A &PRODUCT; user or administrator may create load balancing rules that balance traffic
-    received at a public IP to one or more VMs. A user creates a rule, specifies an algorithm, and
-    assigns the rule to a set of VMs.</para>
-  <note>
-    <para>If you create load balancing rules while using a network service offering that includes an
-      external load balancer device such as NetScaler, and later change the network service offering
-      to one that uses the &PRODUCT; virtual router, you must create a firewall rule on the virtual
-      router for each of your existing load balancing rules so that they continue to
-      function.</para>
-  </note>
-  <para/>
-  <xi:include href="add-load-balancer-rule.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="sticky-session-policies-for-lb-rules.xml"
-    xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="health-checks-for-lb-rules.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</section>

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

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/log-in.xml
----------------------------------------------------------------------
diff --git a/en-US/log-in.xml b/en-US/log-in.xml
deleted file mode 100644
index 84328ce..0000000
--- a/en-US/log-in.xml
+++ /dev/null
@@ -1,48 +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="log-in">
-	<title>Log In to the UI</title>
-	<para>&PRODUCT; provides a web-based UI that can be used by both administrators and end users. The appropriate version of the UI is displayed depending on the credentials used to log in. The UI is available in popular browsers including IE7, IE8, IE9, Firefox 3.5+, Firefox 4, Safari 4, and Safari 5. The URL is: (substitute your own management server IP address)</para>
-	<programlisting>http://&lt;management-server-ip-address&gt;:8080/client</programlisting>
-    <para>On a fresh Management Server installation, a guided tour splash screen appears. On later visits, you’ll see a login screen where you specify the following to proceed to your Dashboard:</para>
-    <formalpara>
-        <title>Username</title>
-        <para>The user ID of your account. The default username is admin.</para>
-    </formalpara>
-    <formalpara>
-        <title>Password</title>
-        <para>The password associated with the user ID. The password for the default username is password.</para>
-    </formalpara>
-    <formalpara>
-        <title>Domain</title>
-        <para>If you are a root user, leave this field blank.</para>
-    </formalpara>
-    <para>If you are a user in the sub-domains, enter the full path to the domain, excluding the root domain.</para>
-    <para>For example, suppose multiple levels are created under the root domain, such as Comp1/hr. The users in the Comp1 domain should enter Comp1 in the Domain field, whereas the users in the Comp1/sales domain should enter Comp1/sales.</para>    
-    <para>For more guidance about the choices that appear when you log in to this UI, see Logging In as the Root Administrator.</para>
-	<xi:include href="end-user-ui-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-	<xi:include href="root-admin-ui-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-	<xi:include href="log-in-root-admin.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-    <xi:include href="changing-root-password.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/long-running-job-events.xml
----------------------------------------------------------------------
diff --git a/en-US/long-running-job-events.xml b/en-US/long-running-job-events.xml
deleted file mode 100644
index cae2b74..0000000
--- a/en-US/long-running-job-events.xml
+++ /dev/null
@@ -1,41 +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="long-running-job-events">
-    <title>Long Running Job Events</title>
-    <para>The events log records three types of standard events.</para>
-    <itemizedlist>
-        <listitem><para>INFO. This event is generated when an operation has been successfully performed.</para></listitem>
-        <listitem><para>WARN. This event is generated in the following circumstances.</para>
-        <itemizedlist>
-            <listitem><para>When a network is disconnected while monitoring a template download.</para></listitem>
-            <listitem><para>When a template download is abandoned.</para></listitem>
-            <listitem><para>When an issue on the storage server causes the volumes to fail over to the mirror storage server.</para></listitem>
-        </itemizedlist>          
-        </listitem>
-        <listitem><para>ERROR. This event is generated when an operation has not been successfully performed</para></listitem>
-    </itemizedlist>
- 
-    </section>
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/lxc-install.xml
----------------------------------------------------------------------
diff --git a/en-US/lxc-install.xml b/en-US/lxc-install.xml
deleted file mode 100644
index 40f6a0a..0000000
--- a/en-US/lxc-install.xml
+++ /dev/null
@@ -1,110 +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="lxc-install">
-  <title>LXC Installation and Configuration</title>
-  <section id="lxc-requirements">
-    <title>System Requirements for LXC Hosts</title>
-    <para>LXC requires the Linux kernel cgroups functionality which is available starting 2.6.24. 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 LXC 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: 1.0.0 or higher</para></listitem>
-      <listitem><para>Qemu/KVM: 1.0 or higher</para></listitem>
-    </itemizedlist>
-    <para>The default bridge in &PRODUCT; is the Linux native bridge implementation (bridge module). &PRODUCT; includes an option to work with OpenVswitch, the requirements are listed below</para>
-    <itemizedlist>
-      <listitem><para>libvirt: 1.0.0 or higher</para></listitem>
-      <listitem><para>openvswitch: 1.7.1 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>
-  <section id="lxc-install-overview">
-    <title>LXC Installation Overview</title>
-    <para>LXC does not have any native system VMs, instead KVM will be used to run system VMs. This means that your host will need to support both LXC and KVM, thus most of the installation and configuration will be identical to the KVM installation. 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 an LXC 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>
-  <section id="lxc-install-prepare-os">
-    <xi:include href="hypervisor-host-install-prepare-os.xml#xpointer(/section/*)" xmlns:xi="http://www.w3.org/2001/XInclude" />
-  </section>
-  <section id="lxc-install-agent">
-    <title>Install and configure the Agent</title>
-    <para>To manage LXC 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>Next step is to update the Agent configuration setttings. The settings are in <filename>/etc/cloudstack/agent/agent.properties</filename></para>
-    <orderedlist>
-      <listitem>
-        <para>Set the Agent to run in LXC mode:</para>
-        <programlisting>hypervisor.type=lxc</programlisting>
-      </listitem>
-      <listitem>
-        <para>Optional: If you would like to use direct networking (instead of the default bridge networking), configure these lines:</para>
-        <programlisting>libvirt.vif.driver=com.cloud.hypervisor.kvm.resource.DirectVifDriver</programlisting>
-        <programlisting>network.direct.source.mode=private</programlisting>
-        <programlisting>network.direct.device=eth0</programlisting>
-      </listitem>
-    </orderedlist>
-    <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>
-  <section id="lxc-install-libvirt">
-    <xi:include href="hypervisor-host-install-libvirt.xml#xpointer(/section/*)" xmlns:xi="http://www.w3.org/2001/XInclude" />
-  </section>
-  <section id="lxc-install-security-policies">
-    <xi:include href="hypervisor-host-install-security-policies.xml#xpointer(/section/*)" xmlns:xi="http://www.w3.org/2001/XInclude" />
-  </section>
-  <section id="lxc-install-network">
-    <xi:include href="hypervisor-host-install-network.xml#xpointer(/section/*)" xmlns:xi="http://www.w3.org/2001/XInclude" />
-  </section>
-  <section id="lxc-install-firewall">
-    <xi:include href="hypervisor-host-install-firewall.xml#xpointer(/section/*)" xmlns:xi="http://www.w3.org/2001/XInclude" />
-  </section>
-  <section id="lxc-install-finish">
-    <xi:include href="hypervisor-host-install-finish.xml#xpointer(/section/*)" xmlns:xi="http://www.w3.org/2001/XInclude" />
-  </section>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/lxc-topology-req.xml
----------------------------------------------------------------------
diff --git a/en-US/lxc-topology-req.xml b/en-US/lxc-topology-req.xml
deleted file mode 100644
index 315863d..0000000
--- a/en-US/lxc-topology-req.xml
+++ /dev/null
@@ -1,24 +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="lxc-topology-req">
-  <title>LXC Topology Requirements</title>
-  <para>The Management Servers communicate with LXC hosts on port 22 (ssh).</para>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/maintain-hypervisors-on-hosts.xml
----------------------------------------------------------------------
diff --git a/en-US/maintain-hypervisors-on-hosts.xml b/en-US/maintain-hypervisors-on-hosts.xml
deleted file mode 100644
index 43f3f79..0000000
--- a/en-US/maintain-hypervisors-on-hosts.xml
+++ /dev/null
@@ -1,29 +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="maintain-hypervisors-on-hosts">
-    <title>Maintaining Hypervisors on Hosts</title>
-    <para>When running hypervisor software on hosts, be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. &PRODUCT; will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches.</para>
-    <note><para>The lack of up-do-date hotfixes can lead to data corruption and lost VMs.</para></note>
-    <para>(XenServer) For more information, see <ulink url="http://docs.cloudstack.org/Knowledge_Base/Possible_VM_corruption_if_XenServer_Hotfix_is_not_Applied/Highly_Recommended_Hotfixes_for_XenServer_5.6_SP2">Highly Recommended Hotfixes for XenServer in the &PRODUCT; Knowledge Base</ulink>.</para>    
-</section>

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

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

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/manage-cloud.xml
----------------------------------------------------------------------
diff --git a/en-US/manage-cloud.xml b/en-US/manage-cloud.xml
deleted file mode 100644
index 4cdc187..0000000
--- a/en-US/manage-cloud.xml
+++ /dev/null
@@ -1,33 +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="manage-cloud">
-  <title>Managing the Cloud</title>
-  <xi:include href="tagging-resources.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="cpu-sockets.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="change-database-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="change-database-password.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="admin-alerts.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="customizing-dns.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="stop-restart-management-server.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-</chapter>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-client.xml
----------------------------------------------------------------------
diff --git a/en-US/management-server-install-client.xml b/en-US/management-server-install-client.xml
deleted file mode 100644
index 62317cd..0000000
--- a/en-US/management-server-install-client.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="management-server-install">
-  <title>Install the Management Server on the First Host</title>
-  <para>The first step in installation, whether you are installing the Management Server on one host
-    or many, is to install the software on a single node. </para>
-  <note>
-    <para>If you are planning to install the Management Server on multiple nodes for high
-      availability, do not proceed to the additional nodes yet. That step will come later.</para>
-  </note>
-  <para>The &PRODUCT; Management server can be installed using either RPM or DEB packages. These
-    packages will depend on everything you need to run the Management server.</para>
-  <section id="management-server-install-rhel">
-    <title>Install on CentOS/RHEL</title>
-    <para>We start by installing the required packages:</para>
-    <programlisting language="Bash">yum install cloudstack-management</programlisting>
-  </section>
-  <section id="management-server-install-ubuntu">
-    <title>Install on Ubuntu</title>
-    <programlisting language="Bash">apt-get install cloudstack-management</programlisting>
-  </section>
-
-  <section id="vhd-util">
-    <title>Downloading vhd-util</title>
-    <para>This procedure is required only for installations where XenServer is installed on the
-      hypervisor hosts.</para>
-    <para>Before setting up the Management Server, download vhd-util from <ulink
-        url="http://download.cloud.com.s3.amazonaws.com/tools/vhd-util">vhd-util</ulink>.</para>
-    <para>If the Management Server is RHEL or CentOS, copy vhd-util to
-      /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver.</para>
-    <para>If the Management Server is Ubuntu, copy vhd-util to
-      /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver.</para>
-  </section>
-</section>

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

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-db-external.xml
----------------------------------------------------------------------
diff --git a/en-US/management-server-install-db-external.xml b/en-US/management-server-install-db-external.xml
deleted file mode 100644
index 2c6c8bc..0000000
--- a/en-US/management-server-install-db-external.xml
+++ /dev/null
@@ -1,145 +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="management-server-install-db-external">
-  <title>Install the Database on a Separate Node</title>
-  <para>This section describes how to install MySQL on a standalone machine, separate from the
-    Management Server. This technique is intended for a deployment that includes several Management
-    Server nodes. If you have a single-node Management Server deployment, you will typically use the
-    same node for MySQL. See <xref linkend="management-server-install-db-local"/>.</para>
-  <note>
-    <para>The management server doesn't require a specific distribution for the MySQL node. You can
-      use a distribution or Operating System of your choice. Using the same distribution as the
-      management server is recommended, but not required. See <xref
-        linkend="management-server-system-requirements"/>.</para>
-  </note>
-  <orderedlist>
-    <listitem>
-      <para>Install MySQL from the package repository from your distribution:</para>
-      <para condition="community">On RHEL or CentOS:</para>
-      <programlisting language="Bash">yum install mysql-server</programlisting>
-      <para condition="community">On Ubuntu:</para>
-      <programlisting language="Bash">apt-get install mysql-server</programlisting>
-    </listitem>
-    <listitem>
-      <para>Edit the MySQL configuration (/etc/my.cnf or /etc/mysql/my.cnf, depending on your OS)
-        and insert the following lines in the [mysqld] section. You can put these lines below the
-        datadir line. The max_connections parameter should be set to 350 multiplied by the number of
-        Management Servers you are deploying. This example assumes two Management Servers.</para>
-      <note>
-        <para>On Ubuntu, you can also create /etc/mysql/conf.d/cloudstack.cnf file and add these
-          directives there. Don't forget to add [mysqld] on the first line of the file.</para>
-      </note>
-      <programlisting language="Bash">innodb_rollback_on_timeout=1
-innodb_lock_wait_timeout=600
-max_connections=700
-log-bin=mysql-bin
-binlog-format = 'ROW'
-bind-address = 0.0.0.0</programlisting>
-    </listitem>
-    <listitem>
-      <para>Start or restart MySQL to put the new configuration into effect.</para>
-      <para>On RHEL/CentOS, MySQL doesn't automatically start after installation. Start it
-        manually.</para>
-      <programlisting language="Bash">service mysqld start</programlisting>
-      <para>On Ubuntu, restart MySQL.</para>
-      <programlisting language="Bash">service mysql restart</programlisting>
-    </listitem>
-    <listitem>
-      <para>(CentOS and RHEL only; not required on Ubuntu)</para>
-      <warning>
-        <para>On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly
-          recommended that you set a root password as a security precaution.</para>
-      </warning>
-      <para>Run the following command to secure your installation. You can answer "Y" to all
-        questions except "Disallow root login remotely?". Remote root login is required to set up
-        the databases.</para>
-      <programlisting language="Bash">mysql_secure_installation</programlisting>
-    </listitem>
-    <listitem>
-      <para>If a firewall is present on the system, open TCP port 3306 so external MySQL connections
-        can be established.</para>
-      <para>On Ubuntu, UFW is the default firewall. Open the port with this command:</para>
-      <programlisting language="Bash">ufw allow mysql</programlisting>
-      <para>On RHEL/CentOS:</para>
-      <orderedlist numeration="loweralpha">
-        <listitem>
-          <para>Edit the /etc/sysconfig/iptables file and add the following line at the beginning of
-            the INPUT chain.</para>
-          <programlisting language="Bash">-A INPUT -p tcp --dport 3306 -j ACCEPT</programlisting>
-        </listitem>
-        <listitem>
-          <para>Now reload the iptables rules.</para>
-          <programlisting language="Bash">service iptables restart</programlisting>
-        </listitem>
-      </orderedlist>
-    </listitem>
-    <listitem>
-      <para>Return to the root shell on your first Management Server.</para>
-    </listitem>
-    <listitem>
-      <para>Set up the database. The following command creates the cloud user on the
-        database.</para>
-      <itemizedlist>
-        <listitem>
-          <para>In dbpassword, specify the password to be assigned to the cloud user. You can choose
-            to provide no password.</para>
-        </listitem>
-        <listitem>
-          <para>In deploy-as, specify the username and password of the user deploying the database.
-            In the following command, it is assumed the root user is deploying the database and
-            creating the cloud user.</para>
-        </listitem>
-        <listitem>
-          <para>(Optional) For encryption_type, use file or web to indicate the technique used to
-            pass in the database encryption password. Default: file. See <xref
-              linkend="about-password-encryption"/>.</para>
-        </listitem>
-        <listitem>
-          <para>(Optional) For management_server_key, substitute the default key that is used to
-            encrypt confidential parameters in the &PRODUCT; properties file. Default: password. It
-            is highly recommended that you replace this with a more secure value. See About Password
-            and Key Encryption.</para>
-        </listitem>
-        <listitem>
-          <para>(Optional) For database_key, substitute the default key that is used to encrypt
-            confidential parameters in the &PRODUCT; database. Default: password. It is highly
-            recommended that you replace this with a more secure value. See <xref
-              linkend="about-password-encryption"/>.</para>
-        </listitem>
-        <listitem>
-          <para>(Optional) For management_server_ip, you may explicitly specify cluster management
-             server node IP. If not specified, the local IP address will be used.</para>
-        </listitem>
-      </itemizedlist>
-      <programlisting language="Bash">cloudstack-setup-databases cloud:&lt;dbpassword&gt;@&lt;ip address mysql server&gt; \
---deploy-as=root:&lt;password&gt; \
--e &lt;encryption_type&gt; \
--m &lt;management_server_key&gt; \
--k &lt;database_key&gt; \
--i &lt;management_server_ip&gt;</programlisting>
-      <para>When this script is finished, you should see a message like “Successfully initialized
-        the database.”</para>
-    </listitem>
-  </orderedlist>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-db-local.xml
----------------------------------------------------------------------
diff --git a/en-US/management-server-install-db-local.xml b/en-US/management-server-install-db-local.xml
deleted file mode 100644
index ebade57..0000000
--- a/en-US/management-server-install-db-local.xml
+++ /dev/null
@@ -1,167 +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="management-server-install-db-local">
-  <title>Install the Database on the Management Server Node</title>
-  <para>This section describes how to install MySQL on the same machine with the Management Server.
-    This technique is intended for a simple deployment that has a single Management Server node. If
-    you have a multi-node Management Server deployment, you will typically use a separate node for
-    MySQL. See <xref linkend="management-server-install-db-external"/>.</para>
-  <orderedlist>
-    <listitem>
-      <para>Install MySQL from the package repository of your distribution:</para>
-      <para condition="community">On RHEL or CentOS:</para>
-      <programlisting language="Bash">yum install mysql-server</programlisting>
-      <para condition="community">On Ubuntu:</para>
-      <programlisting language="Bash">apt-get install mysql-server</programlisting>
-    </listitem>
-    <listitem>
-      <para>Open the MySQL configuration file. The configuration file is <filename>/etc/my.cnf</filename> or
-        <filename>/etc/mysql/my.cnf</filename>, depending on your OS.</para>
-    </listitem>
-    <listitem>
-      <para>Insert the following lines in the [mysqld] section. </para>
-      <para>You can put these lines below the datadir line. The max_connections parameter should be
-        set to 350 multiplied by the number of Management Servers you are deploying. This example
-        assumes one Management Server.</para>
-      <note>
-        <para>On Ubuntu, you can also create a file <filename>/etc/mysql/conf.d/cloudstack.cnf</filename> and add these
-          directives there. Don't forget to add [mysqld] on the first line of the file.</para>
-      </note>
-      <programlisting language="Bash">innodb_rollback_on_timeout=1
-innodb_lock_wait_timeout=600
-max_connections=350
-log-bin=mysql-bin
-binlog-format = 'ROW'</programlisting>
-    </listitem>
-    <listitem>
-      <para>Start or restart MySQL to put the new configuration into effect.</para>
-      <para>On RHEL/CentOS, MySQL doesn't automatically start after installation. Start it
-        manually.</para>
-      <programlisting language="Bash">service mysqld start</programlisting>
-      <para>On Ubuntu, restart MySQL.</para>
-      <programlisting language="Bash">service mysql restart</programlisting>
-    </listitem>
-    <listitem>
-      <para>(CentOS and RHEL only; not required on Ubuntu)</para>
-      <warning>
-        <para>On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly
-          recommended that you set a root password as a security precaution. </para>
-      </warning>
-      <para>Run the following command to secure your installation. You can answer "Y" to all
-        questions.</para>
-      <programlisting language="Bash">mysql_secure_installation</programlisting>
-    </listitem>
-    <listitem>
-      <para>&PRODUCT; can be blocked by security mechanisms, such as SELinux. Disable SELinux to
-        ensure + that the Agent has all the required permissions.</para>
-      <para>Configure SELinux (RHEL and CentOS):</para>
-      <orderedlist numeration="loweralpha">
-        <listitem>
-          <para>Check 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>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>Set up the database. The following command creates the "cloud" user on the
-        database.</para>
-      <itemizedlist>
-        <listitem>
-          <para>In dbpassword, specify the password to be assigned to the "cloud" user. You can
-            choose to provide no password although that is not recommended.</para>
-        </listitem>
-        <listitem>
-          <para>In deploy-as, specify the username and password of the user deploying the database.
-            In the following command, it is assumed the root user is deploying the database and
-            creating the "cloud" user.</para>
-        </listitem>
-        <listitem>
-          <para>(Optional) For encryption_type, use file or web to indicate the technique used to
-            pass in the database encryption password. Default: file. See <xref
-              linkend="about-password-encryption"/>.</para>
-        </listitem>
-        <listitem>
-          <para>(Optional) For management_server_key, substitute the default key that is used to
-            encrypt confidential parameters in the &PRODUCT; properties file. Default: password. It
-            is highly recommended that you replace this with a more secure value. See <xref
-              linkend="about-password-encryption"/>.</para>
-        </listitem>
-        <listitem>
-          <para>(Optional) For database_key, substitute the default key that is used to encrypt
-            confidential parameters in the &PRODUCT; database. Default: password. It is highly
-            recommended that you replace this with a more secure value. See <xref
-              linkend="about-password-encryption"/>.</para>
-        </listitem>
-        <listitem>
-          <para>(Optional) For management_server_ip, you may explicitly specify cluster management
-            server node IP. If not specified, the local IP address will be used.</para>
-        </listitem>
-      </itemizedlist>
-      <programlisting language="Bash">cloudstack-setup-databases cloud:&lt;dbpassword&gt;@localhost \
---deploy-as=root:&lt;password&gt; \
--e &lt;encryption_type&gt; \
--m &lt;management_server_key&gt; \
--k &lt;database_key&gt; \
--i &lt;management_server_ip&gt;</programlisting>
-      <para>When this script is finished, you should see a message like “Successfully initialized
-        the database.”</para>
-      <note>
-	<para>If the script is unable to connect to the MySQL database, check
-          the "localhost" loopback address in <filename>/etc/hosts</filename>. It should
-          be pointing to the IPv4 loopback address "127.0.0.1" and not the IPv6 loopback
-          address ::1. Alternatively, reconfigure MySQL to bind to the IPv6 loopback
-          interface.
-        </para>
-      </note>
-    </listitem>
-    <listitem>
-      <para>If you are running the KVM hypervisor on the same machine with the Management Server,
-        edit /etc/sudoers and add the following line:</para>
-      <programlisting language="Bash">Defaults:cloud !requiretty</programlisting>
-    </listitem>
-    <listitem>
-      <para>Now that the database is set up, you can finish configuring the OS for the Management
-        Server. This command will set up iptables, sudoers, and start the Management Server.</para>
-      <programlisting><prompt>#</prompt> cloudstack-setup-management</programlisting>
-      <para>You should see the message “&PRODUCT; Management Server setup is done.”</para>
-    </listitem>
-  </orderedlist>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-db.xml
----------------------------------------------------------------------
diff --git a/en-US/management-server-install-db.xml b/en-US/management-server-install-db.xml
deleted file mode 100644
index 9d41af2..0000000
--- a/en-US/management-server-install-db.xml
+++ /dev/null
@@ -1,34 +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="management-server-install-db">
-    <title>Install the database server</title>
-    <para>The &PRODUCT; management server uses a MySQL database server to store its data.
-        When you are installing the management server on a single node, you can install the MySQL server locally.
-        For an installation that has multiple management server nodes, we assume the MySQL database also runs on a separate node.
-    </para>
-    <para>&PRODUCT; has been tested with MySQL 5.1 and 5.5. These versions are included in RHEL/CentOS and Ubuntu.</para>
-    <xi:include href="management-server-install-db-local.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-    <xi:include href="management-server-install-db-external.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-flow.xml
----------------------------------------------------------------------
diff --git a/en-US/management-server-install-flow.xml b/en-US/management-server-install-flow.xml
deleted file mode 100644
index cd73c69..0000000
--- a/en-US/management-server-install-flow.xml
+++ /dev/null
@@ -1,42 +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="management-server-install-flow">
-  <title>Management Server Installation</title>
-  <xi:include href="management-server-install-overview.xml"
-    xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="management-server-install-prepare-os.xml"
-    xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="management-server-install-client.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="management-server-install-db.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="about-password-encryption.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="password-storage-engine.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="management-server-install-nfs-shares.xml"
-    xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="management-server-install-multi-node.xml"
-    xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="management-server-install-systemvm.xml"
-    xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="management-server-install-complete.xml"
-    xmlns:xi="http://www.w3.org/2001/XInclude"/>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-multi-node.xml
----------------------------------------------------------------------
diff --git a/en-US/management-server-install-multi-node.xml b/en-US/management-server-install-multi-node.xml
deleted file mode 100644
index 480d84e..0000000
--- a/en-US/management-server-install-multi-node.xml
+++ /dev/null
@@ -1,69 +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="install-management-server-multi-nodes">
-  <title>Prepare and Start Additional Management Servers</title>
-  <para>For your second and subsequent Management Servers, you will install the Management Server
-    software, connect it to the database, and set up the OS for the Management Server. </para>
-  <orderedlist>
-    <listitem>
-      <para> Perform the steps in <xref linkend="prepare-os"/> and <xref
-linkend="sect-source-buildrpm"/> or <xref linkend="sect-source-builddebs"/> as
-        appropriate. </para>
-    </listitem>
-    <listitem>
-      <para>This step is required only for installations where XenServer is installed on the hypervisor hosts.</para>
-      <para>Download vhd-util from <ulink
-          url="http://download.cloud.com.s3.amazonaws.com/tools/vhd-util">vhd-util</ulink></para>
-      <para>Copy vhd-util to
-        /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver.</para>
-    </listitem>
-    <listitem>
-      <para> Ensure that necessary services are started and set to start on boot.
-        <programlisting><prompt>#</prompt> service rpcbind start
-<prompt>#</prompt> service nfs start
-<prompt>#</prompt> chkconfig nfs on
-<prompt>#</prompt> chkconfig rpcbind on
-</programlisting>
-      </para>
-    </listitem>
-    <listitem>
-      <para>Configure the database client. Note the absence of the --deploy-as argument in this
-        case. (For more details about the arguments to this command, see <xref
-          linkend="management-server-install-db-external"/>.) </para>
-      <programlisting><prompt>#</prompt> cloudstack-setup-databases cloud:<replaceable>dbpassword</replaceable>@<replaceable>dbhost</replaceable> -e <replaceable>encryption_type</replaceable> -m <replaceable>management_server_key</replaceable> -k <replaceable>database_key</replaceable> -i <replaceable>management_server_ip</replaceable>
-      </programlisting>
-    </listitem>
-    <listitem>
-      <para>Configure the OS and start the Management Server:</para>
-      <programlisting><prompt>#</prompt> cloudstack-setup-management</programlisting>
-      <para>The Management Server on this node should now be running.</para>
-    </listitem>
-    <listitem>
-      <para>Repeat these steps on each additional Management Server. </para>
-    </listitem>
-    <listitem>
-      <para>Be sure to configure a load balancer for the Management Servers. See <xref linkend="management-server-lb"/>.</para>
-    </listitem>
-  </orderedlist>
-</section>

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-nfs-shares.xml
----------------------------------------------------------------------
diff --git a/en-US/management-server-install-nfs-shares.xml b/en-US/management-server-install-nfs-shares.xml
deleted file mode 100644
index a12e09c..0000000
--- a/en-US/management-server-install-nfs-shares.xml
+++ /dev/null
@@ -1,40 +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="prepare-nfs-shares">
-    <title>Prepare NFS Shares</title>
-    <para>&PRODUCT; needs a place to keep primary and secondary storage (see Cloud Infrastructure Overview). Both of these can be NFS shares. This section tells how to set up the NFS shares before adding the storage to &PRODUCT;.</para>
-    <note><title>Alternative Storage</title>
-        <para>NFS is not the only option for primary or secondary storage. For example, you may use Ceph RBD, GlusterFS, iSCSI, and others. The choice of storage system will depend on the choice of hypervisor and whether you are dealing with primary or secondary storage.</para>
-    </note>
-    <para>The requirements for primary and secondary storage are described in:</para>
-    <itemizedlist>
-        <listitem><para><xref linkend="about-primary-storage"/></para></listitem>
-        <listitem><para><xref linkend="about-secondary-storage"/></para></listitem>
-    </itemizedlist>
-    <para>A production installation typically uses a separate NFS server. See <xref linkend="nfs-shares-on-separate-server"/>.</para>
-    <para>You can also use the Management Server node as the NFS server. This is more typical of a trial installation, but is technically possible in a larger deployment. See <xref linkend="nfs-shares-on-management-server"/>.</para>
-    <xi:include href="nfs-shares-on-separate-server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-    <xi:include href="nfs-shares-on-management-server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</section>


Mime
View raw message