You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by jz...@apache.org on 2013/01/11 22:02:58 UTC
[18/52] [partial] CLOUDSTACK-961: Added dependencies for building
RPMs.
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/creating-network-offerings.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/creating-network-offerings.xml b/docs/tmp/en-US/xml/creating-network-offerings.xml
new file mode 100644
index 0000000..3887557
--- /dev/null
+++ b/docs/tmp/en-US/xml/creating-network-offerings.xml
@@ -0,0 +1,362 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="creating-network-offerings" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Creating a New Network Offering</title>
+ <para>
+ To create a network offering:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Log in with admin privileges to the &PRODUCT; UI.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In the left navigation bar, click Service Offerings.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In Select Offering, choose Network Offering.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Click Add Network Offering.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In the dialog, make the following choices:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Name. Any desired name for the network offering
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Description. A short description of the offering that can be displayed to users
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Network Rate. Allowed data transfer rate in MB per second
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Traffic Type. The type of network traffic that will be carried on the network
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Guest Type. Choose whether the guest network is isolated or shared. For a description of these terms, see <xref linkend="about-virtual-networks" />
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Specify VLAN. (Isolated guest networks only) Indicate whether a VLAN should be specified when this offering is used
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Supported Services. Select one or more of the possible network services. For some services, you must also choose the service provider; for example, if you select Load Balancer, you can choose the &PRODUCT; virtual router or any other load balancers that have been configured in the cloud. Depending on which services you choose, additional fields may appear in the rest of the dialog box.
+ </para>
+ <para>
+ Based on the guest network type selected, you can see the following supported services:
+ </para>
+ <informaltable>
+ <tgroup align="left" cols="4" colsep="1" rowsep="1">
+ <thead>
+ <row>
+ <entry>
+ <para>
+ Supported Services
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Description
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Isolated
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Shared
+ </para>
+ </entry>
+
+ </row>
+
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>
+ DHCP
+ </para>
+ </entry>
+ <entry>
+ <para>
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+
+ </row>
+ <row>
+ <entry>
+ <para>
+ DNS
+ </para>
+ </entry>
+ <entry>
+ <para>
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+
+ </row>
+ <row>
+ <entry>
+ <para>
+ Load Balancer
+ </para>
+ </entry>
+ <entry>
+ <para>
+ If you select Load Balancer, you can choose the &PRODUCT; virtual router or any other load balancers that have been configured in the cloud.
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+
+ </row>
+ <row>
+ <entry>
+ <para>
+ Source NAT
+ </para>
+ </entry>
+ <entry>
+ <para>
+ If you select Source NAT, you can choose the &PRODUCT; virtual router or any other Source NAT providers that have been configured in the cloud.
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+
+ </row>
+ <row>
+ <entry>
+ <para>
+ Static NAT
+ </para>
+ </entry>
+ <entry>
+ <para>
+ If you select Static NAT, you can choose the &PRODUCT; virtual router or any other Static NAT providers that have been configured in the cloud.
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+
+ </row>
+ <row>
+ <entry>
+ <para>
+ Port Forwarding
+ </para>
+ </entry>
+ <entry>
+ <para>
+ If you select Port Forwarding, you can choose the &PRODUCT; virtual router or any other Port Forwarding providers that have been configured in the cloud.
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Not Supported
+ </para>
+ </entry>
+
+ </row>
+ <row>
+ <entry>
+ <para>
+ VPN
+ </para>
+ </entry>
+ <entry>
+ <para>
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Not Supported
+ </para>
+ </entry>
+
+ </row>
+ <row>
+ <entry>
+ <para>
+ User Data
+ </para>
+ </entry>
+ <entry>
+ <para>
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Not Supported
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+
+ </row>
+ <row>
+ <entry>
+ <para>
+ Security Groups
+ </para>
+ </entry>
+ <entry>
+ <para>
+ See <xref linkend="add-security-group" />.
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Not Supported
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Supported
+ </para>
+ </entry>
+
+ </row>
+
+ </tbody>
+
+ </tgroup>
+
+ </informaltable>
+
+ </listitem>
+ <listitem>
+ <para>
+ System Offering. If the service provider for any of the services selected in Supported Services is a virtual router, the System Offering field appears. Choose the system service offering that you want virtual routers to use in this network. For example, if you selected Load Balancer in Supported Services and selected a virtual router to provide load balancing, the System Offering field appears so you can choose between the &PRODUCT; default system service offering and any custom system service offerings that have been defined by the &PRODUCT; root administrator. For more information, see System Service Offerings.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Redundant router capability. (v3.0.3 and greater) Available only when Virtual Router is selected as the Source NAT provider. Select this option if you want to use two virtual routers in the network for uninterrupted connection: one operating as the master virtual router and the other as the backup. The master virtual router receives requests from and sends responses to the user’s VM. The backup virtual router is activated only when the master is down. After the failover, the backup becomes the master virtual router. &PRODUCT; deploys the routers on different hosts to ensure reliability if one host is down.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Conserve mode. Indicate whether to use conserve mode. In this mode, network resources are allocated only when the first virtual machine starts in the network
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Tags. Network tag to specify which physical network to use
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ Click Add.
+ </para>
+ </listitem>
+
+ </orderedlist>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/creating-new-volumes.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/creating-new-volumes.xml b/docs/tmp/en-US/xml/creating-new-volumes.xml
new file mode 100644
index 0000000..f767439
--- /dev/null
+++ b/docs/tmp/en-US/xml/creating-new-volumes.xml
@@ -0,0 +1,79 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="creating-new-volumes" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Creating a New Volume</title>
+ <para>
+ You can add more data disk volumes to a guest VM at any time, up to the limits of your storage capacity. Both &PRODUCT; administrators and users can add volumes to VM instances. When you create a new volume, it is stored as an entity in &PRODUCT;, but the actual storage resources are not allocated on the physical storage device until you attach the volume. This optimization allows the &PRODUCT; to provision the volume nearest to the guest that will use it when the first attachment is made.
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Log in to the &PRODUCT; UI as a user or admin.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In the left navigation bar, click Storage.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In Select View, choose Volumes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To create a new volume, click Add Volume, provide the following details, and click OK.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Name. Give the volume a unique name so you can find it later.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Availability Zone. Where do you want the storage to reside? This should be close to the VM that will use the volume.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Disk Offering. Choose the characteristics of the storage.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ The new volume appears in the list of volumes with the state “Allocated.” The volume data is stored in &PRODUCT;, but the volume is not yet ready for use
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To start using the volume, continue to Attaching a Volume
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/creating-system-service-offerings.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/creating-system-service-offerings.xml b/docs/tmp/en-US/xml/creating-system-service-offerings.xml
new file mode 100644
index 0000000..b6abdb6
--- /dev/null
+++ b/docs/tmp/en-US/xml/creating-system-service-offerings.xml
@@ -0,0 +1,131 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="creating-system-service-offerings" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Creating a New System Service Offering</title>
+ <para>
+ To create a system service offering:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Log in with admin privileges to the &PRODUCT; UI.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In the left navigation bar, click Service Offerings.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In Select Offering, choose System Offering.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Click Add System Service Offering.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In the dialog, make the following choices:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Name. Any desired name for the system offering.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Description. A short description of the offering that can be displayed to users
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ System VM Type. Select the type of system virtual machine that this offering is intended to support.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Storage type. The type of disk that should be allocated. Local allocates from storage attached directly to the host where the system VM is running. Shared allocates from storage accessible via NFS.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ # of CPU cores. The number of cores which should be allocated to a system VM with this offering
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ CPU (in MHz). The CPU speed of the cores that the system VM is allocated. For example, "2000" would provide for a 2 GHz clock.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Memory (in MB). The amount of memory in megabytes that the system VM should be allocated. For example, "2048" would provide for a 2 GB RAM allocation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Network Rate. Allowed data transfer rate in MB per second.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Offer HA. If yes, the administrator can choose to have the system VM be monitored and as highly available as possible.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Storage Tags. The tags that should be associated with the primary storage used by the system VM.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Host Tags. (Optional) Any tags that you use to organize your hosts
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ CPU cap. Whether to limit the level of CPU usage even if spare capacity is available.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Public. Indicate whether the service offering should be available all domains or only some domains. Choose Yes to make it available to all domains. Choose No to limit the scope to a subdomain; &PRODUCT; will then prompt for the subdomain's name.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ Click Add.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/creating-vms.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/creating-vms.xml b/docs/tmp/en-US/xml/creating-vms.xml
new file mode 100644
index 0000000..289d213
--- /dev/null
+++ b/docs/tmp/en-US/xml/creating-vms.xml
@@ -0,0 +1,111 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="creating-vms" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Creating VMs</title>
+ <para>
+ Virtual machines are usually created from a template. Users can also create blank virtual machines. A blank virtual machine is a virtual machine without an OS template. Users can attach an ISO file and install the OS from the CD/DVD-ROM.
+ </para>
+ <para>
+ To create a VM from a template:
+ </para>
+ <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 Add Instance.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Select a template, then follow the steps in the wizard. (For more information about how the templates came to be in this list, see Working with Templates.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Be sure that the hardware you have allows starting the selected service offering.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Click Submit and your VM will be created and started.
+ </para>
+ <note>
+ <para>
+ For security reason, the internal name of the VM is visible only to the root admin.
+ </para>
+ </note>
+ </listitem>
+
+ </orderedlist>
+ <note>
+ <para>
+ Starting with v3.0.3, you can create a VM without starting it. You can determine whether the VM needs to be started as part of the VM deployment. A new request parameter, startVM, is introduced in the deployVm API to support this feature. For more information, see the Developer's Guide
+ </para>
+ </note>
+ <para>
+ To create a VM from an ISO:
+ </para>
+ <note>
+ <para>
+ (XenServer) Windows VMs running on XenServer require PV drivers, which may be provided in the template or added after the VM is created. The PV drivers are necessary for essential management functions such as mounting additional volumes and ISO images, live migration, and graceful shutdown.
+ </para>
+ </note>
+ <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 Add Instance.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Select ISO Boot, and follow the steps in the wizard.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Click Submit and your VM will be created and started.
+ </para>
+ </listitem>
+ <!-- <listitem><para>(Oracle VM only) After ISO installation, the installer reboots into the operating system. Due to a known issue in OVM, the reboot will place the VM in the Stopped state. In the &PRODUCT; UI, detach the ISO from the VM (so that the VM will not boot from the ISO again), then click the Start button to restart the VM.</para></listitem> -->
+ </orderedlist>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/customizing-dns.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/customizing-dns.xml b/docs/tmp/en-US/xml/customizing-dns.xml
new file mode 100644
index 0000000..b33d27d
--- /dev/null
+++ b/docs/tmp/en-US/xml/customizing-dns.xml
@@ -0,0 +1,86 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="customizing-dns" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Customizing the Network Domain Name</title>
+ <para>
+ The root administrator can optionally assign a custom DNS suffix at the level of a network, account, domain, zone, or entire &PRODUCT; installation, and a domain administrator can do so within their own domain. To specify a custom domain name and put it into effect, follow these steps.
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Set the DNS suffix at the desired scope
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ At the network level, the DNS suffix can be assigned through the UI when creating a new network, as described in <xref linkend="add-additional-guest-network" /> or with the updateNetwork command in the &PRODUCT; API.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ At the account, domain, or zone level, the DNS suffix can be assigned with the appropriate &PRODUCT; API commands: createAccount, editAccount, createDomain, editDomain, createZone, or editZone.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ At the global level, use the configuration parameter guest.domain.suffix. You can also use the &PRODUCT; API command updateConfiguration. After modifying this global configuration, restart the Management Server to put the new setting into effect.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ To make the new DNS suffix take effect for an existing network, call the &PRODUCT; API command updateNetwork. This step is not necessary when the DNS suffix was specified while creating a new network.
+ </para>
+ </listitem>
+
+ </orderedlist>
+ <para>
+ The source of the network domain that is used depends on the following rules.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ For all networks, if a network domain is specified as part of a network's own configuration, that value is used.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ For an account-specific network, the network domain specified for the account is used. If none is specified, the system looks for a value in the domain, zone, and global configuration, in that order.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ For a domain-specific network, the network domain specified for the domain is used. If none is specified, the system looks for a value in the zone and global configuration, in that order.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ For a zone-specific network, the network domain specified for the zone is used. If none is specified, the system looks for a value in the global configuration.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/database-replication.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/database-replication.xml b/docs/tmp/en-US/xml/database-replication.xml
new file mode 100644
index 0000000..558032c
--- /dev/null
+++ b/docs/tmp/en-US/xml/database-replication.xml
@@ -0,0 +1,234 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="database-replication" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Database Replication (Optional)</title>
+ <para>
+ &PRODUCT; supports database replication from one MySQL node to another. This is achieved using standard MySQL replication. You may want to do this as insurance against MySQL server or storage loss. MySQL replication is implemented using a master/slave model. The master is the node that the Management Servers are configured to use. The slave is a standby node that receives all write operations from the master and applies them to a local, redundant copy of the database. The following steps are a guide to implementing MySQL replication.
+ </para>
+ <note>
+ <para>
+ Creating a replica is not a backup solution. You should develop a backup procedure for the MySQL data that is distinct from replication.
+ </para>
+ </note>
+ <orderedlist>
+ <listitem>
+ <para>
+ Ensure that this is a fresh install with no data in the master.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Edit my.cnf on the master and add the following in the [mysqld] section below datadir.
+ </para>
+
+<programlisting>
+log_bin=mysql-bin
+server_id=1
+</programlisting>
+ <para>
+ The server_id must be unique with respect to other servers. The recommended way to achieve this is to give the master an ID of 1 and each slave a sequential number greater than 1, so that the servers are numbered 1, 2, 3, etc.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Restart the MySQL service:
+ </para>
+
+<programlisting>
+# service mysqld restart
+</programlisting>
+
+ </listitem>
+ <listitem>
+ <para>
+ Create a replication account on the master and give it privileges. We will use the "cloud-repl" user with the password "password". This assumes that master and slave run on the 172.16.1.0/24 network.
+ </para>
+
+<programlisting>
+# mysql -u root
+mysql> create user 'cloud-repl'@'172.16.1.%' identified by 'password';
+mysql> grant replication slave on *.* TO 'cloud-repl'@'172.16.1.%';
+mysql> flush privileges;
+mysql> flush tables with read lock;
+</programlisting>
+
+ </listitem>
+ <listitem>
+ <para>
+ Leave the current MySQL session running.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In a new shell start a second MySQL session.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Retrieve the current position of the database.
+ </para>
+
+<programlisting>
+# mysql -u root
+mysql> show master status;
++------------------+----------+--------------+------------------+
+| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
++------------------+----------+--------------+------------------+
+| mysql-bin.000001 | 412 | | |
++------------------+----------+--------------+------------------+
+</programlisting>
+
+ </listitem>
+ <listitem>
+ <para>
+ Note the file and the position that are returned by your instance.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Exit from this session.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Complete the master setup. Returning to your first session on the master, release the locks and exit MySQL.
+ </para>
+
+<programlisting>
+mysql> unlock tables;
+</programlisting>
+
+ </listitem>
+ <listitem>
+ <para>
+ Install and configure the slave. On the slave server, run the following commands.
+ </para>
+
+<programlisting>
+# yum install mysql-server
+# chkconfig mysqld on
+</programlisting>
+
+ </listitem>
+ <listitem>
+ <para>
+ Edit my.cnf and add the following lines in the [mysqld] section below datadir.
+ </para>
+
+<programlisting>
+server_id=2
+innodb_rollback_on_timeout=1
+innodb_lock_wait_timeout=600
+</programlisting>
+
+ </listitem>
+ <listitem>
+ <para>
+ Restart MySQL.
+ </para>
+
+<programlisting>
+# service mysqld restart
+</programlisting>
+
+ </listitem>
+ <listitem>
+ <para>
+ Instruct the slave to connect to and replicate from the master. Replace the IP address, password, log file, and position with the values you have used in the previous steps.
+ </para>
+
+<programlisting>
+mysql> change master to
+ -> master_host='172.16.1.217',
+ -> master_user='cloud-repl',
+ -> master_password='password',
+ -> master_log_file='mysql-bin.000001',
+ -> master_log_pos=412;
+</programlisting>
+
+ </listitem>
+ <listitem>
+ <para>
+ Then start replication on the slave.
+ </para>
+
+<programlisting>
+mysql> start slave;
+</programlisting>
+
+ </listitem>
+ <listitem>
+ <para>
+ Optionally, open port 3306 on the slave as was done on the master earlier.
+ </para>
+ <para>
+ This is not required for replication to work. But if you choose not to do this, you will need to do it when failover to the replica occurs.
+ </para>
+
+ </listitem>
+
+ </orderedlist>
+ <section id="database-failover">
+ <title>Failover</title>
+ <para>
+ This will provide for a replicated database that can be used to implement manual failover for the Management Servers. &PRODUCT; failover from one MySQL instance to another is performed by the administrator. In the event of a database failure you should:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Stop the Management Servers (via service cloud-management stop).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Change the replica's configuration to be a master and restart it.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Ensure that the replica's port 3306 is open to the Management Servers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Make a change so that the Management Server uses the new database. The simplest process here is to put the IP address of the new database server into each Management Server's /etc/cloud/management/db.properties.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Restart the Management Servers:
+ </para>
+
+<programlisting>
+# service cloud-management start
+</programlisting>
+
+ </listitem>
+
+ </orderedlist>
+
+ </section>
+
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/dates-in-usage-record.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/dates-in-usage-record.xml b/docs/tmp/en-US/xml/dates-in-usage-record.xml
new file mode 100644
index 0000000..dab16bf
--- /dev/null
+++ b/docs/tmp/en-US/xml/dates-in-usage-record.xml
@@ -0,0 +1,39 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="dates-in-usage-record" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Dates in the Usage Record</title>
+ <para>
+ Usage records include a start date and an end date. These dates define the period of time for which the raw usage number was calculated. If daily aggregation is used, the start date is midnight on the day in question and the end date is 23:59:59 on the day in question (with one exception; see below). A virtual machine could have been deployed at noon on that day, stopped at 6pm on that day, then started up again at 11pm. When usage is calculated on that day, there will be 7 hours of running VM usage (usage type 1) and 12 hours of allocated VM usage (usage type 2). If the same virtual machine runs for the entire next day, there will 24 hours of both running VM usage (type 1) and allocated VM usage (type 2).
+ </para>
+ <para>
+ Note: The start date is not the time a virtual machine was started, and the end date is not the time when a virtual machine was stopped. The start and end dates give the time range within which usage was calculated.
+ </para>
+ <para>
+ For network usage, the start date and end date again define the range in which the number of bytes transferred was calculated. If a user downloads 10 MB and uploads 1 MB in one day, there will be two records, one showing the 10 megabytes received and one showing the 1 megabyte sent.
+ </para>
+ <para>
+ There is one case where the start date and end date do not correspond to midnight and 11:59:59pm when daily aggregation is used. This occurs only for network usage records. When the usage server has more than one day's worth of unprocessed data, the old data will be included in the aggregation period. The start date in the usage record will show the date and time of the earliest event. For other types of usage, such as IP addresses and VMs, the old unprocessed data is not included in daily aggregation.
+ </para>
+
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/dedicated-ha-hosts.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/dedicated-ha-hosts.xml b/docs/tmp/en-US/xml/dedicated-ha-hosts.xml
new file mode 100644
index 0000000..a1381e2
--- /dev/null
+++ b/docs/tmp/en-US/xml/dedicated-ha-hosts.xml
@@ -0,0 +1,50 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="dedicated-ha-hosts" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Dedicated HA Hosts</title>
+ <para>
+ (v3.0.3 and greater) One or more hosts can be designated for use only by HA-enabled VMs that are restarting due to a host failure. Setting up a pool of such dedicated HA hosts as the recovery destination for all HA-enabled VMs is useful to:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Make it easier to determine which VMs have been restarted as part of the &PRODUCT; high-availability function. If a VM is running on a dedicated HA host, then it must be an HA-enabled VM whose original host failed. (With one exception: It is possible for an administrator to manually migrate any VM to a dedicated HA host.).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Keep HA-enabled VMs from restarting on hosts which may be reserved for other purposes.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ The dedicated HA option is set through a special host tag when the host is created. To allow the administrator to dedicate hosts to only HA-enabled VMs, set the global configuration variable ha.tag to the desired tag (for example, "ha_host"), and restart the Management Server. Enter the value in the Host Tags field when adding the host(s) that you want to dedicate to HA-enabled VMs.
+ </para>
+ <note>
+ <para>
+ If you set ha.tag, be sure to actually use that tag on at least one host in your cloud. If the tag specified in ha.tag is not set for any host in the cloud, the HA-enabled VMs will fail to restart after a crash.
+ </para>
+ </note>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/default-account-resource-limit.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/default-account-resource-limit.xml b/docs/tmp/en-US/xml/default-account-resource-limit.xml
new file mode 100644
index 0000000..2d523b7
--- /dev/null
+++ b/docs/tmp/en-US/xml/default-account-resource-limit.xml
@@ -0,0 +1,64 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="default-account-resource-limit" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Default Account Resource Limits</title>
+ <para>
+ You can limit resource use by accounts. The default limits are set using global configuration parameters, and they affect all accounts within a cloud. The relevant parameters are those beginning with max.account (max.account.snapshots, etc.)..
+ </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. 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>
+
+ </orderedlist>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/default-template.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/default-template.xml b/docs/tmp/en-US/xml/default-template.xml
new file mode 100644
index 0000000..7b15d02
--- /dev/null
+++ b/docs/tmp/en-US/xml/default-template.xml
@@ -0,0 +1,64 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="default-template" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>The Default Template</title>
+ <para>
+ &PRODUCT; includes a CentOS template. This template is downloaded by the Secondary Storage VM after the primary and secondary storage are configured. You can use this template in your production deployment or you can delete it and use custom templates.
+ </para>
+ <para>
+ The root password for the default template is "password".
+ </para>
+ <para>
+ A default template is provided for each of XenServer, KVM, and vSphere. The templates that are downloaded depend on the hypervisor type that is available in your cloud. Each template is approximately 2.5 GB physical size.
+ </para>
+ <para>
+ The default template includes the standard iptables rules, which will block most access to the template excluding ssh.
+ </para>
+
+<programlisting># iptables --list
+Chain INPUT (policy ACCEPT)
+target prot opt source destination
+RH-Firewall-1-INPUT all -- anywhere anywhere
+
+Chain FORWARD (policy ACCEPT)
+target prot opt source destination
+RH-Firewall-1-INPUT all -- anywhere anywhere
+
+Chain OUTPUT (policy ACCEPT)
+target prot opt source destination
+
+Chain RH-Firewall-1-INPUT (2 references)
+target prot opt source destination
+ACCEPT all -- anywhere anywhere
+ACCEPT icmp -- anywhere anywhere icmp any
+ACCEPT esp -- anywhere anywhere
+ACCEPT ah -- anywhere anywhere
+ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
+ACCEPT udp -- anywhere anywhere udp dpt:ipp
+ACCEPT tcp -- anywhere anywhere tcp dpt:ipp
+ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
+ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
+REJECT all -- anywhere anywhere reject-with icmp-host-
+</programlisting>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/delete-reset-vpn.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/delete-reset-vpn.xml b/docs/tmp/en-US/xml/delete-reset-vpn.xml
new file mode 100644
index 0000000..b0ab1ca
--- /dev/null
+++ b/docs/tmp/en-US/xml/delete-reset-vpn.xml
@@ -0,0 +1,147 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="delete-reset-vpn" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+ http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Restarting and Removing a VPN Connection</title>
+ <orderedlist>
+ <listitem>
+ <para>
+ Log in to the &PRODUCT; UI as an administrator or end user.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ In the left navigation, choose Network.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ In the Select view, select VPC.
+ </para>
+ <para>
+ All the VPCs that you have created for the account is listed in the page.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Click the Configure button of the VPC to which you want to deploy the VMs.
+ </para>
+ <para>
+ The VPC page is displayed where all the tiers you created are listed in a diagram.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Click the Settings icon.
+ </para>
+ <para>
+ The following options are displayed.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ IP Addresses
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Gateways
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Site-to-Site VPN
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Network ASLs
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </listitem>
+ <listitem>
+ <para>
+ Select Site-to-Site VPN.
+ </para>
+ <para>
+ The Site-to-Site VPN page is displayed.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ From the Select View drop-down, ensure that VPN Connection is selected.
+ </para>
+ <para>
+ All the VPN connections you created are displayed.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Select the VPN connection you want to work with.
+ </para>
+ <para>
+ The Details tab is displayed.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ To remove a VPN connection, click the Delete VPN connection button
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./images/remove-vpn.png" />
+ </imageobject>
+ <textobject>
+ <phrase>remove-vpn.png: button to remove a VPN connection</phrase>
+ </textobject>
+
+ </inlinemediaobject>
+ </para>
+ <para>
+ To restart a VPN connection, click the Reset VPN connection button present in the Details tab.
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./images/reset-vpn.png" />
+ </imageobject>
+ <textobject>
+ <phrase>reset-vpn.png: button to reset a VPN connection</phrase>
+ </textobject>
+
+ </inlinemediaobject>
+ </para>
+
+ </listitem>
+
+ </orderedlist>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/delete-templates.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/delete-templates.xml b/docs/tmp/en-US/xml/delete-templates.xml
new file mode 100644
index 0000000..80486ed
--- /dev/null
+++ b/docs/tmp/en-US/xml/delete-templates.xml
@@ -0,0 +1,32 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="delete-templates" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Deleting Templates</title>
+ <para>
+ Templates may be deleted. In general, when a template spans multiple Zones, only the copy that is selected for deletion will be deleted; the same template in other Zones will not be deleted. The provided CentOS template is an exception to this. If the provided CentOS template is deleted, it will be deleted from all Zones.
+ </para>
+ <para>
+ When templates are deleted, the VMs instantiated from them will continue to run. However, new VMs cannot be created based on the deleted template.
+ </para>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/deleting-vms.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/deleting-vms.xml b/docs/tmp/en-US/xml/deleting-vms.xml
new file mode 100644
index 0000000..642a24b
--- /dev/null
+++ b/docs/tmp/en-US/xml/deleting-vms.xml
@@ -0,0 +1,66 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="deleting-vms" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Deleting VMs</title>
+ <para>
+ Users can delete their own virtual machines. A running virtual machine will be abruptly stopped before it is deleted. Administrators can delete any virtual machines.
+ </para>
+ <para>
+ To delete a virtual machine:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Log in to the &PRODUCT; UI as a user or admin.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In the left navigation, click Instances.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Choose the VM that you want to delete.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Click the Destroy Instance button
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./images/destroy-instance.png" />
+ </imageobject>
+ <textobject>
+ <phrase>Destroyinstance.png: button to destroy an instance</phrase>
+ </textobject>
+
+ </inlinemediaobject>
+
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/dell62xx-hardware.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/dell62xx-hardware.xml b/docs/tmp/en-US/xml/dell62xx-hardware.xml
new file mode 100644
index 0000000..cbd07d8
--- /dev/null
+++ b/docs/tmp/en-US/xml/dell62xx-hardware.xml
@@ -0,0 +1,74 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="dell62xx-hardware" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+ http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Dell 62xx</title>
+ <para>
+ The following steps show how a Dell 62xx is configured for zone-level layer-3 switching. These steps assume VLAN 201 is used to route untagged private IPs for pod 1, and pod 1’s layer-2 switch is connected to Ethernet port 1/g1.
+ </para>
+ <para>
+ The Dell 62xx Series switch supports up to 1024 VLANs.
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Configure all the VLANs in the database.
+ </para>
+
+<programlisting>vlan database
+vlan 200-999
+exit</programlisting>
+
+ </listitem>
+ <listitem>
+ <para>
+ Configure Ethernet port 1/g1.
+ </para>
+
+<programlisting>interface ethernet 1/g1
+switchport mode general
+switchport general pvid 201
+switchport general allowed vlan add 201 untagged
+switchport general allowed vlan add 300-999 tagged
+exit</programlisting>
+
+ </listitem>
+
+ </orderedlist>
+ <para>
+ The statements configure Ethernet port 1/g1 as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ VLAN 201 is the native untagged VLAN for port 1/g1.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ All VLANs (300-999) are passed to all the pod-level layer-2 switches.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/dell62xx-layer2.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/dell62xx-layer2.xml b/docs/tmp/en-US/xml/dell62xx-layer2.xml
new file mode 100644
index 0000000..d2618a9
--- /dev/null
+++ b/docs/tmp/en-US/xml/dell62xx-layer2.xml
@@ -0,0 +1,69 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="dell62xx-layer2" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+ http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Dell 62xx</title>
+ <para>
+ The following steps show how a Dell 62xx is configured for pod-level layer-2 switching.
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Configure all the VLANs in the database.
+ </para>
+
+<programlisting>vlan database
+vlan 300-999
+exit</programlisting>
+
+ </listitem>
+ <listitem>
+ <para>
+ VLAN 201 is used to route untagged private IP addresses for pod 1, and pod 1 is connected to this layer-2 switch.
+ </para>
+
+<programlisting>interface range ethernet all
+switchport mode general
+switchport general allowed vlan add 300-999 tagged
+exit</programlisting>
+
+ </listitem>
+
+ </orderedlist>
+ <para>
+ The statements configure all Ethernet ports to function as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ All ports are configured the same way.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ All VLANs (300-999) are passed through all the ports of the layer-2 switch.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/deployment-architecture-overview.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/deployment-architecture-overview.xml b/docs/tmp/en-US/xml/deployment-architecture-overview.xml
new file mode 100644
index 0000000..bbae7a1
--- /dev/null
+++ b/docs/tmp/en-US/xml/deployment-architecture-overview.xml
@@ -0,0 +1,47 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="deployment-architecture-overview" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Deployment Architecture Overview</title>
+ <para>
+ A &PRODUCT; installation consists of two parts: the Management Server and the cloud infrastructure that it manages. When you set up and manage a &PRODUCT; cloud, you provision resources such as hosts, storage devices, and IP addresses into the Management Server, and the Management Server manages those resources.
+ </para>
+ <para>
+ The minimum production installation consists of one machine running the &PRODUCT; Management Server and another machine to act as the cloud infrastructure (in this case, a very simple infrastructure consisting of one host running hypervisor software). In its smallest deployment, a single machine can act as both the Management Server and the hypervisor host (using the KVM hypervisor).
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./images/basic-deployment.png" />
+ </imageobject>
+ <textobject>
+ <phrase>basic-deployment.png: Basic two-machine deployment</phrase>
+ </textobject>
+
+ </mediaobject>
+ <para>
+ A more full-featured installation consists of a highly-available multi-node Management Server installation and up to tens of thousands of hosts using any of several advanced networking setups. For information about deployment options, see Choosing a Deployment Architecture.
+ </para>
+ <xi:include href="management-server-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="cloud-infrastructure-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="networking-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/detach-move-volumes.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/detach-move-volumes.xml b/docs/tmp/en-US/xml/detach-move-volumes.xml
new file mode 100644
index 0000000..9728d1d
--- /dev/null
+++ b/docs/tmp/en-US/xml/detach-move-volumes.xml
@@ -0,0 +1,71 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="detach-move-volumes" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Attaching a Volume</title>
+ <note>
+ <para>
+ This procedure is different from moving disk volumes from one storage pool to another. See VM Storage Migration
+ </para>
+ </note>
+ <para>
+ A volume can be detached from a guest VM and attached to another guest. Both &PRODUCT; administrators and users can detach volumes from VMs and move them to other VMs.
+ </para>
+ <para>
+ If the two VMs are in different clusters, and the volume is large, it may take several minutes for the volume to be moved to the new VM.
+ </para>
+ <!-- <para>If the destination VM is running in the OVM hypervisor, the VM must be stopped before a new volume can be attached to it.</para> --> <orderedlist>
+ <listitem>
+ <para>
+ Log in to the &PRODUCT; UI as a user or admin.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In the left navigation bar, click Storage, and choose Volumes in Select View. Alternatively, if you know which VM the volume is attached to, you can click Instances, click the VM name, and click View Volumes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Click the name of the volume you want to detach, then click the Detach Disk button
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./images/detach-disk-icon.png" />
+ </imageobject>
+ <textobject>
+ <phrase>DetachDiskButton.png: button to detach a volume</phrase>
+ </textobject>
+
+ </inlinemediaobject>
+
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To move the volume to another VM, follow the steps in Attaching a Volume <xref linkend="attaching-volume" />.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/devcloud-usage-mode.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/devcloud-usage-mode.xml b/docs/tmp/en-US/xml/devcloud-usage-mode.xml
new file mode 100644
index 0000000..45d00a9
--- /dev/null
+++ b/docs/tmp/en-US/xml/devcloud-usage-mode.xml
@@ -0,0 +1,83 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="devcloud-usage-mode" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>DevCloud Usage Mode</title>
+ <para>
+ DevCloud can be used in several different ways:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Full sandbox. Where &PRODUCT; is run within the DevCloud instance started in Virtual Box.
+ </para>
+ <para>
+ In this mode, the &PRODUCT; management server runs within the instance and nested virtualization allows instantiation of tiny VMs within DevCloud itself. &PRODUCT; code modifications are done within DevCloud.
+ </para>
+ <para>
+ The following diagram shows the architecture of the SandBox mode.
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./images/DevCloud.png" width="444" />
+ </imageobject>
+ <textobject>
+ <phrase>DevCloud.png: Schematic of the DevCloud SandBox architecture</phrase>
+ </textobject>
+
+ </mediaobject>
+
+ </listitem>
+ <listitem>
+ <para>
+ A deployment environment. Where &PRODUCT; code is developed in the localhost of the developer and the resulting build is deployed within DevCloud
+ </para>
+ <para>
+ This mode was used in the testing procedure of &PRODUCT; 4.0.0 incubating release. See the following screencast to see how: <ulink url="http://vimeo.com/54621457">http://vimeo.com/54621457</ulink>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ A host-only mode. Where DevCloud is used only as a host. &PRODUCT; management server is run in the localhost of the developer
+ </para>
+ <para>
+ This mode makes use of a host-only interface defined in the Virtual Box preferences. Check the following screencast to see how: <ulink url="http://vimeo.com/54610161">http://vimeo.com/54610161</ulink>
+ </para>
+ <para>
+ The following schematic shows the architecture of the Host-Only mode.
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./images/DevCloud-hostonly.png" width="444" />
+ </imageobject>
+ <textobject>
+ <phrase>DevCloud-hostonly.png: Schematic of the DevCloud host-only architecture </phrase>
+ </textobject>
+
+ </mediaobject>
+
+ </listitem>
+
+ </orderedlist>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/devcloud.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/devcloud.xml b/docs/tmp/en-US/xml/devcloud.xml
new file mode 100644
index 0000000..cab23cf
--- /dev/null
+++ b/docs/tmp/en-US/xml/devcloud.xml
@@ -0,0 +1,49 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="devcloud" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>DevCloud</title>
+ <para>
+ DevCloud is the &PRODUCT; sandbox. It is provided as a Virtual Box appliance. It is meant to be used as a development environment to easily test new &PRODUCT; development. It has also been used for training and &PRODUCT; demos since it provides a <emphasis>Cloud in a box</emphasis>.
+ </para>
+ <note>
+ <para>
+ DevCloud is provided as a convenience by community members. It is not an official &PRODUCT; release artifact.
+ </para>
+ <para>
+ The &PRODUCT; source code however, contains tools to build your own DevCloud.
+ </para>
+
+ </note>
+ <warning>
+ <para>
+ DevCloud is under development and should be considered a Work In Progress (WIP), the wiki is the most up to date documentation:
+ </para>
+ <para>
+ <ulink url="https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud" />
+ </para>
+
+ </warning>
+ <xi:include href="devcloud-usage-mode.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="building-devcloud.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/developer-getting-started.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/developer-getting-started.xml b/docs/tmp/en-US/xml/developer-getting-started.xml
new file mode 100644
index 0000000..bd765e4
--- /dev/null
+++ b/docs/tmp/en-US/xml/developer-getting-started.xml
@@ -0,0 +1,58 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="getting-started" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Getting Started</title>
+ <para>
+ To get started using the &PRODUCT; API, you should have the following:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ URL of the &PRODUCT; server you wish to integrate with.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Both the API Key and Secret Key for an account. This should have been generated by the administrator of the cloud instance and given to you.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Familiarity with HTTP GET/POST and query strings.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Knowledge of either XML or JSON.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Knowledge of a programming language that can generate HTTP requests; for example, Java or PHP.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/developer-introduction.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/developer-introduction.xml b/docs/tmp/en-US/xml/developer-introduction.xml
new file mode 100644
index 0000000..c636d97
--- /dev/null
+++ b/docs/tmp/en-US/xml/developer-introduction.xml
@@ -0,0 +1,28 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<chapter id="developer-introduction" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Introduction for Developers</title>
+ <xi:include href="roles.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="api-reference.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="developer-getting-started.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/disable-enable-zones-pods-clusters.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/disable-enable-zones-pods-clusters.xml b/docs/tmp/en-US/xml/disable-enable-zones-pods-clusters.xml
new file mode 100644
index 0000000..7cfca37
--- /dev/null
+++ b/docs/tmp/en-US/xml/disable-enable-zones-pods-clusters.xml
@@ -0,0 +1,100 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="disable-enable-zones-pods-clusters" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Disabling and Enabling Zones, Pods, and Clusters</title>
+ <para>
+ You can enable or disable a zone, pod, or cluster without permanently removing it from the cloud. This is useful for maintenance or when there are problems that make a portion of the cloud infrastructure unreliable. No new allocations will be made to a disabled zone, pod, or cluster until its state is returned to Enabled. When a zone, pod, or cluster is first added to the cloud, it is Disabled by default.
+ </para>
+ <para>
+ To disable and enable a zone, pod, or cluster:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Log in to the &PRODUCT; UI as administrator
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In the left navigation bar, click Infrastructure.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ In Zones, click View More.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ If you are disabling or enabling a zone, find the name of the zone in the list, and click the Enable/Disable button.
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./images/enable-disable.png" />
+ </imageobject>
+ <textobject>
+ <phrase>enable-disable.png: button to enable or disable zone, pod, or cluster.</phrase>
+ </textobject>
+
+ </inlinemediaobject>
+
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you are disabling or enabling a pod or cluster, click the name of the zone that contains the pod or cluster.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Click the Compute tab.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ In the Pods or Clusters node of the diagram, click View All.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Click the pod or cluster name in the list.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Click the Enable/Disable button.
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./images/enable-disable.png" />
+ </imageobject>
+ </inlinemediaobject>
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/disk-volume-usage-record-format.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/disk-volume-usage-record-format.xml b/docs/tmp/en-US/xml/disk-volume-usage-record-format.xml
new file mode 100644
index 0000000..d9902d1
--- /dev/null
+++ b/docs/tmp/en-US/xml/disk-volume-usage-record-format.xml
@@ -0,0 +1,103 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="disk-volume-usage-record-format" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Disk Volume Usage Record Format</title>
+ <para>
+ For disk volumes, the following fields exist in a usage record.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ account – name of the account
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ accountid – ID of the account
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ domainid – ID of the domain in which this account resides
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ zoneid – Zone where the usage occurred
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ description – A string describing what the usage record is tracking
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for hours)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ usagetype – A number representing the usage type (see Usage Types)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ rawusage – A number representing the actual usage in hours
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ usageid – The volume ID
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ offeringid – The ID of the disk offering
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ type – Hypervisor
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ templateid – ROOT template ID
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ size – The amount of storage allocated
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/dns-dhcp.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/dns-dhcp.xml b/docs/tmp/en-US/xml/dns-dhcp.xml
new file mode 100644
index 0000000..4da4a18
--- /dev/null
+++ b/docs/tmp/en-US/xml/dns-dhcp.xml
@@ -0,0 +1,29 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="dns-dhcp" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>DNS and DHCP</title>
+ <para>
+ The Virtual Router provides DNS and DHCP services to the guests. It proxies DNS requests to the DNS server configured on the Availability Zone.
+ </para>
+</section>
+
+
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/xml/domains.xml
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/xml/domains.xml b/docs/tmp/en-US/xml/domains.xml
new file mode 100644
index 0000000..5f463e0
--- /dev/null
+++ b/docs/tmp/en-US/xml/domains.xml
@@ -0,0 +1,30 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="domains" lang="en-US">
+ <!-- Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ --> <title>Domains</title>
+ <para>
+ If the LDAP server requires SSL, you need to enable it in the ldapConfig command by setting the parameters ssl, truststore, and truststorepass. Before enabling SSL for ldapConfig, you need to get the certificate which the LDAP server is using and add it to a trusted keystore. You will need to know the path to the keystore and the password.
+ </para>
+
+</section>
+
+