http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/installation-steps-overview.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/installation-steps-overview.html 
b/docs/tmp/en-US/html/installation-steps-overview.html
deleted file mode 100644
index 74fa05e..0000000
--- a/docs/tmp/en-US/html/installation-steps-overview.html
+++ /dev/null
@@ -1,35 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta 
http-equiv="Content-Type" content="text/html; charset=UTF-8" 
/><title>4.2. Overview of Installation Steps</title><link rel="stylesheet" 
type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" 
media="print" href="Common_Content/css/print.css" type="text/css" /><meta 
name="generator" content="publican 2.8" /><meta name="package" 
content="Apache_CloudStack-Installation_Guide-4.0.0-incubating-en-US-1-" 
/><link rel="home" href="index.html" title="CloudStack Installation Guide" 
/><link rel="up" href="installation.html" title="Chapter 4. Installation" 
/><link rel="prev" href="who-should-read-installation.html" title="4.1. Who 
Should Read This" /><link rel="next" href="minimum-system-requirements.html" 
title="4.3. Minimum System Requirements" /></head><body><p id="title"><a 
class="left" href="http://cloudstack.org";><img 
src="Common_Content/images/image_left.png" alt="Product Site" /></a><a 
class="right" href=
 "http://docs.cloudstack.org";><img src="Common_Content/images/image_right.png" 
alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a 
accesskey="p" 
href="who-should-read-installation.html"><strong>Prev</strong></a></li><li 
class="next"><a accesskey="n" 
href="minimum-system-requirements.html"><strong>Next</strong></a></li></ul><div 
xml:lang="en-US" class="section" id="installation-steps-overview" 
lang="en-US"><div class="titlepage"><div><div><h2 class="title" 
id="installation-steps-overview">4.2. Overview of Installation 
Steps</h2></div></div></div><div class="para">
-               For anything more than a simple trial installation, you will 
need guidance for a variety of configuration choices. It is strongly 
recommended that you read the following:
-       </div><div class="itemizedlist"><ul><li class="listitem"><div 
class="para">
-                               Choosing a Deployment Architecture
-                       </div></li><li class="listitem"><div class="para">
-                               Choosing a Hypervisor: Supported Features
-                       </div></li><li class="listitem"><div class="para">
-                               Network Setup
-                       </div></li><li class="listitem"><div class="para">
-                               Storage Setup
-                       </div></li><li class="listitem"><div class="para">
-                               Best Practices
-                       </div></li></ul></div><div class="orderedlist"><ol><li 
class="listitem"><div class="para">
-                               Make sure you have the required hardware ready. 
See <a class="xref" href="minimum-system-requirements.html">Section 4.3, 
“Minimum System Requirements”</a>
-                       </div></li><li class="listitem"><div class="para">
-                               Install the Management Server (choose 
single-node or multi-node). See <a class="xref" 
href="management-server-install-flow.html">Section 4.5, “Management Server 
Installation”</a>
-                       </div></li><li class="listitem"><div class="para">
-                               Log in to the UI. See <a class="xref" 
href="ui.html">Chapter 5, <em>User Interface</em></a>
-                       </div></li><li class="listitem"><div class="para">
-                               Add a zone. Includes the first pod, cluster, 
and host. See <a class="xref" href="zone-add.html">Section 6.2, “Adding a 
Zone”</a>
-                       </div></li><li class="listitem"><div class="para">
-                               Add more pods (optional). See <a class="xref" 
href="pod-add.html">Section 6.3, “Adding a Pod”</a>
-                       </div></li><li class="listitem"><div class="para">
-                               Add more clusters (optional). See <a 
class="xref" href="cluster-add.html">Section 6.4, “Adding a Cluster”</a>
-                       </div></li><li class="listitem"><div class="para">
-                               Add more hosts (optional). See <a class="xref" 
href="host-add.html">Section 6.5, “Adding a Host”</a>
-                       </div></li><li class="listitem"><div class="para">
-                               Add more primary storage (optional). See <a 
class="xref" href="primary-storage-add.html">Section 6.6, “Add Primary 
Storage”</a>
-                       </div></li><li class="listitem"><div class="para">
-                               Add more secondary storage (optional). See <a 
class="xref" href="secondary-storage-add.html">Section 6.7, “Add Secondary 
Storage”</a>
-                       </div></li><li class="listitem"><div class="para">
-                               Try using the cloud. See <a class="xref" 
href="initialize-and-test.html">Section 6.8, “Initialize and Test”</a>
-                       </div></li></ol></div></div><ul class="docnav"><li 
class="previous"><a accesskey="p" 
href="who-should-read-installation.html"><strong>Prev</strong>4.1. Who Should 
Read This</a></li><li class="up"><a accesskey="u" 
href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" 
href="index.html"><strong>Home</strong></a></li><li class="next"><a 
accesskey="n" 
href="minimum-system-requirements.html"><strong>Next</strong>4.3. Minimum 
System Requirements</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/installation.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/installation.html 
b/docs/tmp/en-US/html/installation.html
deleted file mode 100644
index 0cb6da3..0000000
--- a/docs/tmp/en-US/html/installation.html
+++ /dev/null
@@ -1,3 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta 
http-equiv="Content-Type" content="text/html; charset=UTF-8" 
/><title>Chapter 4. Installation</title><link rel="stylesheet" 
type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" 
media="print" href="Common_Content/css/print.css" type="text/css" /><meta 
name="generator" content="publican 2.8" /><meta name="package" 
content="Apache_CloudStack-Installation_Guide-4.0.0-incubating-en-US-1-" 
/><link rel="home" href="index.html" title="CloudStack Installation Guide" 
/><link rel="up" href="index.html" title="CloudStack Installation Guide" 
/><link rel="prev" href="sect-source-buildrpm.html" title="3.6. Building RPMs" 
/><link rel="next" href="who-should-read-installation.html" title="4.1. Who 
Should Read This" /></head><body><p id="title"><a class="left" 
href="http://cloudstack.org";><img src="Common_Content/images/image_left.png" 
alt="Product Site" /></a><a class="right" 
href="http://docs.cloudstack.org";><img s
 rc="Common_Content/images/image_right.png" alt="Documentation Site" 
/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" 
href="sect-source-buildrpm.html"><strong>Prev</strong></a></li><li 
class="next"><a accesskey="n" 
href="who-should-read-installation.html"><strong>Next</strong></a></li></ul><div
 xml:lang="en-US" class="chapter" id="installation" lang="en-US"><div 
class="titlepage"><div><div><h2 
class="title">Chapter 4. Installation</h2></div></div></div><div 
class="toc"><dl><dt><span class="section"><a 
href="who-should-read-installation.html">4.1. Who Should Read 
This</a></span></dt><dt><span class="section"><a 
href="installation-steps-overview.html">4.2. Overview of Installation 
Steps</a></span></dt><dt><span class="section"><a 
href="minimum-system-requirements.html">4.3. Minimum System 
Requirements</a></span></dt><dd><dl><dt><span class="section"><a 
href="minimum-system-requirements.html#management-server-system-requirements">4.3.1.
 Management Server, Database, a
 nd Storage System Requirements</a></span></dt><dt><span class="section"><a 
href="minimum-system-requirements.html#hypervisor-system-requirements">4.3.2. 
Host/Hypervisor System Requirements</a></span></dt></dl></dd><dt><span 
class="section"><a href="configure-package-repository.html">4.4. Configure 
package repository</a></span></dt><dd><dl><dt><span class="section"><a 
href="configure-package-repository.html#configure-package-repository-deb">4.4.1.
 DEB package repository</a></span></dt><dt><span class="section"><a 
href="configure-package-repository.html#configure-package-repository-rpm">4.4.2.
 RPM package repository</a></span></dt></dl></dd><dt><span class="section"><a 
href="management-server-install-flow.html">4.5. Management Server 
Installation</a></span></dt><dd><dl><dt><span class="section"><a 
href="management-server-install-flow.html#management-server-installation-overview">4.5.1.
 Management Server Installation Overview</a></span></dt><dt><span 
class="section"><a href="management
 -server-install-flow.html#prepare-os">4.5.2. Prepare the Operating 
System</a></span></dt><dt><span class="section"><a 
href="management-server-install-flow.html#management-server-install">4.5.3. 
Install the Management Server on the First Host</a></span></dt><dt><span 
class="section"><a 
href="management-server-install-flow.html#management-server-install-db">4.5.4. 
Install the database server</a></span></dt><dt><span class="section"><a 
href="management-server-install-flow.html#prepare-nfs-shares">4.5.5. Prepare 
NFS Shares</a></span></dt><dt><span class="section"><a 
href="management-server-install-flow.html#install-management-server-multi-nodes">4.5.6.
 Prepare and Start Additional Management Servers</a></span></dt><dt><span 
class="section"><a 
href="management-server-install-flow.html#prepare-system-vm-template">4.5.7. 
Prepare the System VM Template</a></span></dt><dt><span class="section"><a 
href="management-server-install-flow.html#installation-complete">4.5.8. 
Installation Complete! N
 ext Steps</a></span></dt></dl></dd></dl></div></div><ul class="docnav"><li 
class="previous"><a accesskey="p" 
href="sect-source-buildrpm.html"><strong>Prev</strong>3.6. Building 
RPMs</a></li><li class="up"><a accesskey="u" 
href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" 
href="index.html"><strong>Home</strong></a></li><li class="next"><a 
accesskey="n" 
href="who-should-read-installation.html"><strong>Next</strong>4.1. Who Should 
Read This</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/inter-vlan-routing.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/inter-vlan-routing.html 
b/docs/tmp/en-US/html/inter-vlan-routing.html
deleted file mode 100644
index d54b278..0000000
--- a/docs/tmp/en-US/html/inter-vlan-routing.html
+++ /dev/null
@@ -1,39 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta 
http-equiv="Content-Type" content="text/html; charset=UTF-8" 
/><title>15.18. About Inter-VLAN Routing</title><link rel="stylesheet" 
type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" 
media="print" href="Common_Content/css/print.css" type="text/css" /><meta 
name="generator" content="publican 2.8" /><meta name="package" 
content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link 
rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link 
rel="up" href="networks.html" title="Chapter 15. Managing Networks and 
Traffic" /><link rel="prev" href="vpn.html" title="15.17. VPN" /><link 
rel="next" href="configure-vpc.html" title="15.19. Configuring a Virtual 
Private Cloud" /></head><body><p id="title"><a class="left" 
href="http://cloudstack.org";><img src="Common_Content/images/image_left.png" 
alt="Product Site" /></a><a class="right" 
href="http://docs.cloudstack.org";><img src=
 "Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul 
class="docnav"><li class="previous"><a accesskey="p" 
href="vpn.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" 
href="configure-vpc.html"><strong>Next</strong></a></li></ul><div 
xml:lang="en-US" class="section" id="inter-vlan-routing" lang="en-US"><div 
class="titlepage"><div><div><h2 class="title" 
id="inter-vlan-routing">15.18. About Inter-VLAN 
Routing</h2></div></div></div><div class="para">
-               Inter-VLAN Routing is the capability to route network traffic 
between VLANs. This feature enables you to build Virtual Private Clouds (VPC), 
an isolated segment of your cloud, that can hold multi-tier applications. These 
tiers are deployed on different VLANs that can communicate with each other. You 
provision VLANs to the tiers your create, and VMs can be deployed on different 
tiers. The VLANs are connected to a virtual router, which facilitates 
communication between the VMs. In effect, you can segment VMs by means of VLANs 
into different networks that can host multi-tier applications, such as Web, 
Application, or Database. Such segmentation by means of VLANs logically 
separate application VMs for higher security and lower broadcasts, while 
remaining physically connected to the same device.
-       </div><div class="para">
-               This feature is supported on XenServer and VMware hypervisors.
-       </div><div class="para">
-               The major advantages are:
-       </div><div class="itemizedlist"><ul><li class="listitem"><div 
class="para">
-                               The administrator can deploy a set of VLANs and 
allow users to deploy VMs on these VLANs. A guest VLAN is randomly alloted to 
an account from a pre-specified set of guest VLANs. All the VMs of a certain 
tier of an account reside on the guest VLAN allotted to that account.
-                       </div><div class="note"><div 
class="admonition_header"><h2>Note</h2></div><div class="admonition"><div 
class="para">
-                                       A VLAN allocated for an account cannot 
be shared between multiple accounts.
-                               </div></div></div></li><li 
class="listitem"><div class="para">
-                               The administrator can allow users create their 
own VPC and deploy the application. In this scenario, the VMs that belong to 
the account are deployed on the VLANs allotted to that account.
-                       </div></li><li class="listitem"><div class="para">
-                               Both administrators and users can create 
multiple VPCs. The guest network NIC is plugged to the VPC virtual router when 
the first VM is deployed in a tier.
-                       </div></li><li class="listitem"><div class="para">
-                               The administrator can create the following 
gateways to send to or receive traffic from the VMs:
-                       </div><div class="itemizedlist"><ul><li 
class="listitem"><div class="para">
-                                               <span class="bold 
bold"><strong>VPN Gateway</strong></span>: For more information, see <a 
class="xref" href="vpn.html#create-vpn-gateway-for-vpc">Section 15.17.4.2, 
“Creating a VPN gateway for the VPC”</a>.
-                                       </div></li><li class="listitem"><div 
class="para">
-                                               <span class="bold 
bold"><strong>Public Gateway</strong></span>: The public gateway for a VPC is 
added to the virtual router when the virtual router is created for VPC. The 
public gateway is not exposed to the end users. You are not allowed to list it, 
nor allowed to create any static routes.
-                                       </div></li><li class="listitem"><div 
class="para">
-                                               <span class="bold 
bold"><strong>Private Gateway</strong></span>: For more information, see <a 
class="xref" href="configure-vpc.html#add-gateway-vpc">Section 15.19.5, 
“Adding a Private Gateway to a VPC”</a>.
-                                       </div></li></ul></div></li><li 
class="listitem"><div class="para">
-                               Both administrators and users can create 
various possible destinations-gateway combinations. However, only one gateway 
of each type can be used in a deployment.
-                       </div><div class="para">
-                               For example:
-                       </div><div class="itemizedlist"><ul><li 
class="listitem"><div class="para">
-                                               <span class="bold 
bold"><strong>VLANs and Public Gateway</strong></span>: For example, an 
application is deployed in the cloud, and the Web application VMs communicate 
with the Internet.
-                                       </div></li><li class="listitem"><div 
class="para">
-                                               <span class="bold 
bold"><strong>VLANs, VPN Gateway, and Public Gateway</strong></span>: For 
example, an application is deployed in the cloud; the Web application VMs 
communicate with the Internet; and the database VMs communicate with the 
on-premise devices.
-                                       </div></li></ul></div></li><li 
class="listitem"><div class="para">
-                               The administrator can define Access Control 
List (ACL) on the virtual router to filter the traffic among the VLANs or 
between the Internet and a VLAN. You can define ACL based on CIDR, port range, 
protocol, type code (if ICMP protocol is selected) and Ingress/Egress type.
-                       </div></li></ul></div><div class="para">
-               The following figure shows the possible deployment scenarios of 
a Inter-VLAN setup:
-       </div><div class="mediaobject"><img src="./images/multi-tier-app.png" 
width="444" alt="mutltier.png: a multi-tier setup." /></div><div class="para">
-               To set up a multi-tier Inter-VLAN deployment, see <a 
class="xref" href="configure-vpc.html">Section 15.19, “Configuring a Virtual 
Private Cloud”</a>.
-       </div></div><ul class="docnav"><li class="previous"><a accesskey="p" 
href="vpn.html"><strong>Prev</strong>15.17. VPN</a></li><li class="up"><a 
accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a 
accesskey="h" href="index.html"><strong>Home</strong></a></li><li 
class="next"><a accesskey="n" 
href="configure-vpc.html"><strong>Next</strong>15.19. Configuring a Virtual 
Private Cloud</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/ip-forwarding-firewalling.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/ip-forwarding-firewalling.html 
b/docs/tmp/en-US/html/ip-forwarding-firewalling.html
deleted file mode 100644
index 26e5bf3..0000000
--- a/docs/tmp/en-US/html/ip-forwarding-firewalling.html
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta 
http-equiv="Content-Type" content="text/html; charset=UTF-8" 
/><title>15.14. IP Forwarding and Firewalling</title><link rel="stylesheet" 
type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" 
media="print" href="Common_Content/css/print.css" type="text/css" /><meta 
name="generator" content="publican 2.8" /><meta name="package" 
content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link 
rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link 
rel="up" href="networks.html" title="Chapter 15. Managing Networks and 
Traffic" /><link rel="prev" href="static-nat.html" title="15.13. Static NAT" 
/><link rel="next" href="ip-load-balancing.html" title="15.15. IP Load 
Balancing" /></head><body><p id="title"><a class="left" 
href="http://cloudstack.org";><img src="Common_Content/images/image_left.png" 
alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org";><img
  src="Common_Content/images/image_right.png" alt="Documentation Site" 
/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" 
href="static-nat.html"><strong>Prev</strong></a></li><li class="next"><a 
accesskey="n" 
href="ip-load-balancing.html"><strong>Next</strong></a></li></ul><div 
xml:lang="en-US" class="section" id="ip-forwarding-firewalling" 
lang="en-US"><div class="titlepage"><div><div><h2 class="title" 
id="ip-forwarding-firewalling">15.14. IP Forwarding and 
Firewalling</h2></div></div></div><div class="para">
-               By default, all incoming traffic to the public IP address is 
rejected. All outgoing traffic from the guests is translated via NAT to the 
public IP address and is allowed.
-       </div><div class="para">
-               To allow incoming traffic, users may set up firewall rules 
and/or port forwarding rules. For example, you can use a firewall rule to open 
a range of ports on the public IP address, such as 33 through 44. Then use port 
forwarding rules to direct traffic from individual ports within that range to 
specific ports on user VMs. For example, one port forwarding rule could route 
incoming traffic on the public IP's port 33 to port 100 on one user VM's 
private IP.
-       </div><div class="para">
-               For the steps to implement these rules, see Firewall Rules and 
Port Forwarding.
-       </div></div><ul class="docnav"><li class="previous"><a accesskey="p" 
href="static-nat.html"><strong>Prev</strong>15.13. Static NAT</a></li><li 
class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li 
class="home"><a accesskey="h" 
href="index.html"><strong>Home</strong></a></li><li class="next"><a 
accesskey="n" href="ip-load-balancing.html"><strong>Next</strong>15.15. IP 
Load Balancing</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/ip-load-balancing.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/ip-load-balancing.html 
b/docs/tmp/en-US/html/ip-load-balancing.html
deleted file mode 100644
index 2c50a67..0000000
--- a/docs/tmp/en-US/html/ip-load-balancing.html
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta 
http-equiv="Content-Type" content="text/html; charset=UTF-8" 
/><title>15.15. IP Load Balancing</title><link rel="stylesheet" 
type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" 
media="print" href="Common_Content/css/print.css" type="text/css" /><meta 
name="generator" content="publican 2.8" /><meta name="package" 
content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link 
rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link 
rel="up" href="networks.html" title="Chapter 15. Managing Networks and 
Traffic" /><link rel="prev" href="ip-forwarding-firewalling.html" 
title="15.14. IP Forwarding and Firewalling" /><link rel="next" 
href="dns-dhcp.html" title="15.16. DNS and DHCP" /></head><body><p 
id="title"><a class="left" href="http://cloudstack.org";><img 
src="Common_Content/images/image_left.png" alt="Product Site" /></a><a 
class="right" href="http://docs.cloudstack.o
 rg"><img src="Common_Content/images/image_right.png" alt="Documentation Site" 
/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" 
href="ip-forwarding-firewalling.html"><strong>Prev</strong></a></li><li 
class="next"><a accesskey="n" 
href="dns-dhcp.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" 
class="section" id="ip-load-balancing" lang="en-US"><div 
class="titlepage"><div><div><h2 class="title" id="ip-load-balancing">15.15. IP 
Load Balancing</h2></div></div></div><div class="para">
-               The user may choose to associate the same public IP for 
multiple guests. CloudStack implements a TCP-level load balancer with the 
following policies.
-       </div><div class="itemizedlist"><ul><li class="listitem"><div 
class="para">
-                               Round-robin
-                       </div></li><li class="listitem"><div class="para">
-                               Least connection
-                       </div></li><li class="listitem"><div class="para">
-                               Source IP
-                       </div></li></ul></div><div class="para">
-               This is similar to port forwarding but the destination may be 
multiple IP addresses.
-       </div></div><ul class="docnav"><li class="previous"><a accesskey="p" 
href="ip-forwarding-firewalling.html"><strong>Prev</strong>15.14. IP 
Forwarding and Firewalling</a></li><li class="up"><a accesskey="u" 
href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" 
href="index.html"><strong>Home</strong></a></li><li class="next"><a 
accesskey="n" href="dns-dhcp.html"><strong>Next</strong>15.16. DNS and 
DHCP</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/large_scale_redundant_setup.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/large_scale_redundant_setup.html 
b/docs/tmp/en-US/html/large_scale_redundant_setup.html
deleted file mode 100644
index 41a8c05..0000000
--- a/docs/tmp/en-US/html/large_scale_redundant_setup.html
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta 
http-equiv="Content-Type" content="text/html; charset=UTF-8" 
/><title>9.2. Large-Scale Redundant Setup</title><link rel="stylesheet" 
type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" 
media="print" href="Common_Content/css/print.css" type="text/css" /><meta 
name="generator" content="publican 2.8" /><meta name="package" 
content="Apache_CloudStack-Installation_Guide-4.0.0-incubating-en-US-1-" 
/><link rel="home" href="index.html" title="CloudStack Installation Guide" 
/><link rel="up" href="choosing-a-deployment_architecture.html" 
title="Chapter 9. Choosing a Deployment Architecture" /><link rel="prev" 
href="small_scale_deployment.html" title="9.1. Small-Scale Deployment" /><link 
rel="next" href="separate_storage_network.html" title="9.3. Separate Storage 
Network" /></head><body><p id="title"><a class="left" 
href="http://cloudstack.org";><img src="Common_Content/images/image_left.png" 
alt="Product Sit
 e" /></a><a class="right" href="http://docs.cloudstack.org";><img 
src="Common_Content/images/image_right.png" alt="Documentation Site" 
/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" 
href="small_scale_deployment.html"><strong>Prev</strong></a></li><li 
class="next"><a accesskey="n" 
href="separate_storage_network.html"><strong>Next</strong></a></li></ul><div 
xml:lang="en-US" class="section" id="large_scale_redundant_setup" 
lang="en-US"><div class="titlepage"><div><div><h2 class="title" 
id="large_scale_redundant_setup">9.2. Large-Scale Redundant 
Setup</h2></div></div></div><div class="mediaobject"><img 
src="./images/large-scale-redundant-setup.png" width="444" alt="Large-Scale 
Redundant Setup" /></div><div class="para">
-               This diagram illustrates the network architecture of a 
large-scale CloudStack deployment.
-       </div><div class="itemizedlist"><ul><li class="listitem"><div 
class="para">
-                               A layer-3 switching layer is at the core of the 
data center. A router redundancy protocol like VRRP should be deployed. 
Typically high-end core switches also include firewall modules. Separate 
firewall appliances may also be used if the layer-3 switch does not have 
integrated firewall capabilities. The firewalls are configured in NAT mode. The 
firewalls provide the following functions:
-                       </div><div class="itemizedlist"><ul><li 
class="listitem"><div class="para">
-                                               Forwards HTTP requests and API 
calls from the Internet to the Management Server. The Management Server resides 
on the management network.
-                                       </div></li><li class="listitem"><div 
class="para">
-                                               When the cloud spans multiple 
zones, the firewalls should enable site-to-site VPN such that servers in 
different zones can directly reach each other.
-                                       </div></li></ul></div></li><li 
class="listitem"><div class="para">
-                               A layer-2 access switch layer is established 
for each pod. Multiple switches can be stacked to increase port count. In 
either case, redundant pairs of layer-2 switches should be deployed.
-                       </div></li><li class="listitem"><div class="para">
-                               The Management Server cluster (including 
front-end load balancers, Management Server nodes, and the MySQL database) is 
connected to the management network through a pair of load balancers.
-                       </div></li><li class="listitem"><div class="para">
-                               Secondary storage servers are connected to the 
management network.
-                       </div></li><li class="listitem"><div class="para">
-                               Each pod contains storage and computing 
servers. Each storage and computing server should have redundant NICs connected 
to separate layer-2 access switches.
-                       </div></li></ul></div></div><ul class="docnav"><li 
class="previous"><a accesskey="p" 
href="small_scale_deployment.html"><strong>Prev</strong>9.1. Small-Scale 
Deployment</a></li><li class="up"><a accesskey="u" 
href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" 
href="index.html"><strong>Home</strong></a></li><li class="next"><a 
accesskey="n" 
href="separate_storage_network.html"><strong>Next</strong>9.3. Separate 
Storage Network</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/load-balancer-rules.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/load-balancer-rules.html 
b/docs/tmp/en-US/html/load-balancer-rules.html
deleted file mode 100644
index 2339b12..0000000
--- a/docs/tmp/en-US/html/load-balancer-rules.html
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta 
http-equiv="Content-Type" content="text/html; charset=UTF-8" 
/><title>15.9. Load Balancer Rules</title><link rel="stylesheet" 
type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" 
media="print" href="Common_Content/css/print.css" type="text/css" /><meta 
name="generator" content="publican 2.8" /><meta name="package" 
content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link 
rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link 
rel="up" href="networks.html" title="Chapter 15. Managing Networks and 
Traffic" /><link rel="prev" href="external-firewalls-and-load-balancers.html" 
title="15.8. External Firewalls and Load Balancers" /><link rel="next" 
href="guest-ip-ranges.html" title="15.10. Guest IP Ranges" /></head><body><p 
id="title"><a class="left" href="http://cloudstack.org";><img 
src="Common_Content/images/image_left.png" alt="Product Site" /></a><a 
class="right" 
 href="http://docs.cloudstack.org";><img 
src="Common_Content/images/image_right.png" alt="Documentation Site" 
/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" 
href="external-firewalls-and-load-balancers.html"><strong>Prev</strong></a></li><li
 class="next"><a accesskey="n" 
href="guest-ip-ranges.html"><strong>Next</strong></a></li></ul><div 
xml:lang="en-US" class="section" id="load-balancer-rules" lang="en-US"><div 
class="titlepage"><div><div><h2 class="title" 
id="load-balancer-rules">15.9. Load Balancer Rules</h2></div></div></div><div 
class="para">
-               A CloudStack 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.
-       </div><div class="note"><div 
class="admonition_header"><h2>Note</h2></div><div class="admonition"><div 
class="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 
CloudStack 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.
-               </div></div></div></div><ul class="docnav"><li 
class="previous"><a accesskey="p" 
href="external-firewalls-and-load-balancers.html"><strong>Prev</strong>15.8. External
 Firewalls and Load Balancers</a></li><li class="up"><a accesskey="u" 
href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" 
href="index.html"><strong>Home</strong></a></li><li class="next"><a 
accesskey="n" href="guest-ip-ranges.html"><strong>Next</strong>15.10. Guest IP 
Ranges</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/log-in.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/log-in.html b/docs/tmp/en-US/html/log-in.html
deleted file mode 100644
index 30f6307..0000000
--- a/docs/tmp/en-US/html/log-in.html
+++ /dev/null
@@ -1,62 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta 
http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.1. Log 
In to the UI</title><link rel="stylesheet" type="text/css" 
href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" 
href="Common_Content/css/print.css" type="text/css" /><meta name="generator" 
content="publican 2.8" /><meta name="package" 
content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link 
rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link 
rel="up" href="ui.html" title="Chapter 5. User Interface" /><link rel="prev" 
href="ui.html" title="Chapter 5. User Interface" /><link rel="next" 
href="using-sshkeys.html" title="5.2. Using SSH Keys for Authentication" 
/></head><body><p id="title"><a class="left" href="http://cloudstack.org";><img 
src="Common_Content/images/image_left.png" alt="Product Site" /></a><a 
class="right" href="http://docs.cloudstack.org";><img src="Common_Content/image
 s/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li 
class="previous"><a accesskey="p" 
href="ui.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" 
href="using-sshkeys.html"><strong>Next</strong></a></li></ul><div 
xml:lang="en-US" class="section" id="log-in" lang="en-US"><div 
class="titlepage"><div><div><h2 class="title" id="log-in">5.1. Log In to the 
UI</h2></div></div></div><div class="para">
-               CloudStack 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)
-       </div><pre 
class="programlisting">http://&lt;management-server-ip-address&gt;:8080/client</pre><div
 class="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:
-       </div><div class="formalpara"><h5 class="formalpara" 
id="idp26621976">Username</h5>
-                       The user ID of your account. The default username is 
admin.
-               </div><div class="formalpara"><h5 class="formalpara" 
id="idp44198600">Password</h5>
-                       The password associated with the user ID. The password 
for the default username is password.
-               </div><div class="formalpara"><h5 class="formalpara" 
id="idp19700448">Domain</h5>
-                       If you are a root user, leave this field blank.
-               </div><div class="para">
-               If you are a user in the sub-domains, enter the full path to 
the domain, excluding the root domain.
-       </div><div class="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.
-       </div><div class="para">
-               For more guidance about the choices that appear when you log in 
to this UI, see Logging In as the Root Administrator.
-       </div><div xml:lang="en-US" class="section" id="end-user-ui-overview" 
lang="en-US"><div class="titlepage"><div><div><h3 class="title" 
id="end-user-ui-overview">5.1.1. End User's UI 
Overview</h3></div></div></div><div class="para">
-               The CloudStack UI helps users of cloud infrastructure to view 
and use their cloud resources, including virtual machines, templates and ISOs, 
data volumes and snapshots, guest networks, and IP addresses. If the user is a 
member or administrator of one or more CloudStack projects, the UI can provide 
a project-oriented view.
-       </div></div><div xml:lang="en-US" class="section" 
id="root-admin-ui-overview" lang="en-US"><div class="titlepage"><div><div><h3 
class="title" id="root-admin-ui-overview">5.1.2. Root Administrator's UI 
Overview</h3></div></div></div><div class="para">
-               The CloudStack UI helps the CloudStack administrator provision, 
view, and manage the cloud infrastructure, domains, user accounts, projects, 
and configuration settings. The first time you start the UI after a fresh 
Management Server installation, you can choose to follow a guided tour to 
provision your cloud infrastructure. On subsequent logins, the dashboard of the 
logged-in user appears. The various links in this screen and the navigation bar 
on the left provide access to a variety of administrative functions. The root 
administrator can also use the UI to perform all the same tasks that are 
present in the end-user’s UI.
-       </div></div><div xml:lang="en-US" class="section" 
id="log-in-root-admin" lang="en-US"><div class="titlepage"><div><div><h3 
class="title" id="log-in-root-admin">5.1.3. Logging In as the Root 
Administrator</h3></div></div></div><div class="para">
-               After the Management Server software is installed and running, 
you can run the CloudStack user interface. This UI is there to help you 
provision, view, and manage your cloud infrastructure.
-       </div><div class="orderedlist"><ol><li class="listitem"><div 
class="para">
-                               Open your favorite Web browser and go to this 
URL. Substitute the IP address of your own Management Server:
-                       </div><pre 
class="programlisting">http://&lt;management-server-ip-address&gt;:8080/client</pre><div
 class="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.
-                       </div></li><li class="listitem"><div class="para">
-                               If you see the first-time splash screen, choose 
one of the following.
-                       </div><div class="itemizedlist"><ul><li 
class="listitem"><div class="para">
-                                               <span class="bold 
bold"><strong>Continue with basic setup.</strong></span> Choose this if you're 
just trying CloudStack, 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 
CloudStack software and uses NFS to provide storage; a single machine running 
VMs under the XenServer or KVM hypervisor; and a shared public network.
-                                       </div><div class="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.
-                                       </div></li><li class="listitem"><div 
class="para">
-                                               <span class="bold 
bold"><strong>I have used CloudStack before.</strong></span> Choose this if you 
have already gone through a design phase and planned a more sophisticated 
deployment, or you are ready to start scaling up a trial cloud that you set up 
earlier with the basic setup screens. In the Administrator UI, you can start 
using the more powerful features of CloudPlatform, such as advanced VLAN 
networking, high availability, additional network elements such as load 
balancers and firewalls, and support for multiple hypervisors including Citrix 
XenServer, KVM, and VMware vSphere.
-                                       </div><div class="para">
-                                               The root administrator 
Dashboard appears.
-                                       </div></li></ul></div></li><li 
class="listitem"><div class="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 <a 
class="xref" href="log-in.html#changing-root-password">Section 5.1.4, 
“Changing the Root Password”</a>.
-                       </div></li></ol></div><div class="warning"><div 
class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div 
class="para">
-                       You are logging in as the root administrator. This 
account manages the CloudStack 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.
-               </div></div></div></div><div xml:lang="en-US" class="section" 
id="changing-root-password" lang="en-US"><div class="titlepage"><div><div><h3 
class="title" id="changing-root-password">5.1.4. Changing the Root 
Password</h3></div></div></div><div class="para">
-               During installation and ongoing cloud administration, you will 
need to log in to the UI as the root administrator. The root administrator 
account manages the CloudStack 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. When first installing 
CloudStack, be sure to change the default password to a new, unique value.
-       </div><div class="orderedlist"><ol><li class="listitem"><div 
class="para">
-                               Open your favorite Web browser and go to this 
URL. Substitute the IP address of your own Management Server:
-                       </div><pre 
class="programlisting">http://&lt;management-server-ip-address&gt;:8080/client</pre></li><li
 class="listitem"><div class="para">
-                               Log in to the UI using the current root user ID 
and password. The default is admin, password.
-                       </div></li><li class="listitem"><div class="para">
-                               Click Accounts.
-                       </div></li><li class="listitem"><div class="para">
-                               Click the admin account name.
-                       </div></li><li class="listitem"><div class="para">
-                               Click View Users.
-                       </div></li><li class="listitem"><div class="para">
-                               Click the admin user name.
-                       </div></li><li class="listitem"><div class="para">
-                               Click the Change Password button. 
-                               <span class="inlinemediaobject"><img 
src="./images/change-password.png" alt="change-password.png: button to change a 
user's password" /></span>
-                       </div></li><li class="listitem"><div class="para">
-                               Type the new password, and click OK.
-                       </div></li></ol></div></div></div><ul 
class="docnav"><li class="previous"><a accesskey="p" 
href="ui.html"><strong>Prev</strong>Chapter 5. User Interface</a></li><li 
class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li 
class="home"><a accesskey="h" 
href="index.html"><strong>Home</strong></a></li><li class="next"><a 
accesskey="n" href="using-sshkeys.html"><strong>Next</strong>5.2. Using SSH 
Keys for Authentication</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/maintain-hypervisors-on-hosts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/maintain-hypervisors-on-hosts.html 
b/docs/tmp/en-US/html/maintain-hypervisors-on-hosts.html
deleted file mode 100644
index c3d403d..0000000
--- a/docs/tmp/en-US/html/maintain-hypervisors-on-hosts.html
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta 
http-equiv="Content-Type" content="text/html; charset=UTF-8" 
/><title>11.6. Maintaining Hypervisors on Hosts</title><link rel="stylesheet" 
type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" 
media="print" href="Common_Content/css/print.css" type="text/css" /><meta 
name="generator" content="publican 2.8" /><meta name="package" 
content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link 
rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link 
rel="up" href="working-with-hosts.html" title="Chapter 11. Working With 
Hosts" /><link rel="prev" href="re-install-hosts.html" 
title="11.5. Re-Installing Hosts" /><link rel="next" 
href="change-host-password.html" title="11.7. Changing Host Password" 
/></head><body><p id="title"><a class="left" href="http://cloudstack.org";><img 
src="Common_Content/images/image_left.png" alt="Product Site" /></a><a 
class="right" href="http://doc
 s.cloudstack.org"><img src="Common_Content/images/image_right.png" 
alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a 
accesskey="p" href="re-install-hosts.html"><strong>Prev</strong></a></li><li 
class="next"><a accesskey="n" 
href="change-host-password.html"><strong>Next</strong></a></li></ul><div 
xml:lang="en-US" class="section" id="maintain-hypervisors-on-hosts" 
lang="en-US"><div class="titlepage"><div><div><h2 class="title" 
id="maintain-hypervisors-on-hosts">11.6. Maintaining Hypervisors on 
Hosts</h2></div></div></div><div class="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. CloudStack 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.
-       </div><div class="note"><div 
class="admonition_header"><h2>Note</h2></div><div class="admonition"><div 
class="para">
-                       The lack of up-do-date hotfixes can lead to data 
corruption and lost VMs.
-               </div></div></div><div class="para">
-               (XenServer) For more information, see <a 
href="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 CloudStack Knowledge Base</a>
-       </div></div><ul class="docnav"><li class="previous"><a accesskey="p" 
href="re-install-hosts.html"><strong>Prev</strong>11.5. Re-Installing 
Hosts</a></li><li class="up"><a accesskey="u" 
href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" 
href="index.html"><strong>Home</strong></a></li><li class="next"><a 
accesskey="n" 
href="change-host-password.html"><strong>Next</strong>11.7. Changing Host 
Password</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/making-api-request.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/making-api-request.html 
b/docs/tmp/en-US/html/making-api-request.html
deleted file mode 100644
index 32240ee..0000000
--- a/docs/tmp/en-US/html/making-api-request.html
+++ /dev/null
@@ -1,35 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta 
http-equiv="Content-Type" content="text/html; charset=UTF-8" 
/><title>4.1. Making API Requests</title><link rel="stylesheet" 
type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" 
media="print" href="Common_Content/css/print.css" type="text/css" /><meta 
name="generator" content="publican 2.8" /><meta name="package" 
content="Apache_CloudStack-API_Developers_Guide-4.0.0-incubating-en-US-1-" 
/><link rel="home" href="index.html" title="CloudStack API Developer's Guide" 
/><link rel="up" href="api-calls.html" title="Chapter 4. Calling the 
CloudStack API" /><link rel="prev" href="api-calls.html" 
title="Chapter 4. Calling the CloudStack API" /><link rel="next" 
href="enabling-api-call-expiration.html" title="4.2. Enabling API Call 
Expiration" /></head><body><p id="title"><a class="left" 
href="http://cloudstack.org";><img src="Common_Content/images/image_left.png" 
alt="Product Site" /></a><a class="right" href
 ="http://docs.cloudstack.org";><img src="Common_Content/images/image_right.png" 
alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a 
accesskey="p" href="api-calls.html"><strong>Prev</strong></a></li><li 
class="next"><a accesskey="n" 
href="enabling-api-call-expiration.html"><strong>Next</strong></a></li></ul><div
 xml:lang="en-US" class="section" id="making-api-request" lang="en-US"><div 
class="titlepage"><div><div><h2 class="title" 
id="making-api-request">4.1. Making API Requests</h2></div></div></div><div 
class="para">
-               All CloudStack API requests are submitted in the form of a HTTP 
GET/POST with an associated command and any parameters. A request is composed 
of the following whether in HTTP or HTTPS:
-       </div><div class="itemizedlist"><ul><li class="listitem"><div 
class="para">
-                               CloudStack API URL: This is the web services 
API entry point(for example, http://www.cloud.com:8080/client/api)
-                       </div></li><li class="listitem"><div class="para">
-                               Command: The web services command you wish to 
execute, such as start a virtual machine or create a disk volume
-                       </div></li><li class="listitem"><div class="para">
-                               Parameters: Any additional required or optional 
parameters for the command
-                       </div></li></ul></div><div class="para">
-               A sample API GET request looks like the following:
-       </div><pre 
class="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
-</pre><div class="para">
-               Or in a more readable format:
-       </div><pre class="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
-</pre><div class="para">
-               The first line is the CloudStack API URL. This is the Cloud 
instance you wish to interact with.
-       </div><div class="para">
-               The second line refers to the command you wish to execute. In 
our example, we are attempting to deploy a fresh new virtual machine. It is 
preceded by a (?) to separate itself from the CloudStack API URL.
-       </div><div class="para">
-               Lines 3-6 are the parameters for this given command. To see the 
command and its request parameters, please refer to the appropriate section in 
the CloudStack API documentation. Each parameter field-value pair (field=value) 
is preceded by an ampersand character (&amp;).
-       </div><div class="para">
-               Line 7 is the user API Key that uniquely identifies the 
account. See Signing API Requests on page 7.
-       </div><div class="para">
-               Line 8 is the signature hash created to authenticate the user 
account executing the API command. See Signing API Requests on page 7.
-       </div></div><ul class="docnav"><li class="previous"><a accesskey="p" 
href="api-calls.html"><strong>Prev</strong>Chapter 4. Calling the CloudStack 
API</a></li><li class="up"><a accesskey="u" 
href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" 
href="index.html"><strong>Home</strong></a></li><li class="next"><a 
accesskey="n" 
href="enabling-api-call-expiration.html"><strong>Next</strong>4.2. Enabling 
API Call Expiration</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/manage-cloud.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/manage-cloud.html 
b/docs/tmp/en-US/html/manage-cloud.html
deleted file mode 100644
index 8b43353..0000000
--- a/docs/tmp/en-US/html/manage-cloud.html
+++ /dev/null
@@ -1,3 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta 
http-equiv="Content-Type" content="text/html; charset=UTF-8" 
/><title>Chapter 18. Managing the Cloud</title><link rel="stylesheet" 
type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" 
media="print" href="Common_Content/css/print.css" type="text/css" /><meta 
name="generator" content="publican 2.8" /><meta name="package" 
content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link 
rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link 
rel="up" href="index.html" title="CloudStack Administrator's Guide" /><link 
rel="prev" href="secondary-storage-outage-and-data-loss.html" 
title="17.5. Secondary Storage Outage and Data Loss" /><link rel="next" 
href="tagging-resources.html" title="18.1. Using Tags to Organize Resources in 
the Cloud" /></head><body><p id="title"><a class="left" 
href="http://cloudstack.org";><img src="Common_Content/images/image_left.png" 
alt="Product Site
 " /></a><a class="right" href="http://docs.cloudstack.org";><img 
src="Common_Content/images/image_right.png" alt="Documentation Site" 
/></a></p><ul class="docnav"><li class="previous"><a accesskey="p" 
href="secondary-storage-outage-and-data-loss.html"><strong>Prev</strong></a></li><li
 class="next"><a accesskey="n" 
href="tagging-resources.html"><strong>Next</strong></a></li></ul><div 
xml:lang="en-US" class="chapter" id="manage-cloud" lang="en-US"><div 
class="titlepage"><div><div><h2 class="title">Chapter 18. Managing the 
Cloud</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a 
href="tagging-resources.html">18.1. Using Tags to Organize Resources in the 
Cloud</a></span></dt><dt><span class="section"><a 
href="change-database-config.html">18.2. Changing the Database 
Configuration</a></span></dt><dt><span class="section"><a 
href="admin-alerts.html">18.3. Administrator Alerts</a></span></dt><dt><span 
class="section"><a href="customizing-dns.html">18.4. Customizing the
  Network Domain Name</a></span></dt><dt><span class="section"><a 
href="stop-restart-management-server.html">18.5. Stopping and Restarting the 
Management Server</a></span></dt></dl></div></div><ul class="docnav"><li 
class="previous"><a accesskey="p" 
href="secondary-storage-outage-and-data-loss.html"><strong>Prev</strong>17.5. Secondary
 Storage Outage and Data Loss</a></li><li class="up"><a accesskey="u" 
href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" 
href="index.html"><strong>Home</strong></a></li><li class="next"><a 
accesskey="n" href="tagging-resources.html"><strong>Next</strong>18.1. Using 
Tags to Organize Resources in the Clo...</a></li></ul></body></html>

Reply via email to