You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by mu...@apache.org on 2012/12/06 09:09:12 UTC
[81/100] [abbrv] [partial] Revised en-US/network-setup.xml to include
the correct file.
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/removing-hosts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/removing-hosts.html b/docs/tmp/en-US/html/removing-hosts.html
deleted file mode 100644
index 9121ef8..0000000
--- a/docs/tmp/en-US/html/removing-hosts.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>11.4. Removing 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="disable-enable-zones-pods-clusters.html" title="11.3. Disabling and Enabling Zones, Pods, and Clusters" /><link rel="next" href="re-install-hosts.html" title="11.5. Re-Installing Hosts" /></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="r
ight" 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="disable-enable-zones-pods-clusters.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="re-install-hosts.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="removing-hosts" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="removing-hosts">11.4. Removing Hosts</h2></div></div></div><div class="para">
- Hosts can be removed from the cloud as needed. The procedure to remove a host depends on the hypervisor type.
- </div><div xml:lang="en-US" class="section" id="removing-xenserver-kvm-hosts" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="removing-xenserver-kvm-hosts">11.4.1. Removing XenServer and KVM Hosts</h3></div></div></div><div class="para">
- A node cannot be removed from a cluster until it has been placed in maintenance mode. This will ensure that all of the VMs on it have been migrated to other Hosts. To remove a Host from the cloud:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Place the node in maintenance mode.
- </div><div class="para">
- See <a class="xref" href="scheduled-maintenance-maintenance-mode-hosts.html">Section 11.2, “Scheduled Maintenance and Maintenance Mode for Hosts”</a>.
- </div></li><li class="listitem"><div class="para">
- For KVM, stop the cloud-agent service.
- </div></li><li class="listitem"><div class="para">
- Use the UI option to remove the node.
- </div><div class="para">
- Then you may power down the Host, re-use its IP address, re-install it, etc
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="removing-vsphere-hosts" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="removing-vsphere-hosts">11.4.2. Removing vSphere Hosts</h3></div></div></div><div class="para">
- To remove this type of host, first place it in maintenance mode, as described in <a class="xref" href="scheduled-maintenance-maintenance-mode-hosts.html">Section 11.2, “Scheduled Maintenance and Maintenance Mode for Hosts”</a>. Then use CloudStack to remove the host. CloudStack will not direct commands to a host that has been removed using CloudStack. However, the host may still exist in the vCenter cluster.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="disable-enable-zones-pods-clusters.html"><strong>Prev</strong>11.3. Disabling and Enabling Zones, Pods, and Clu...</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="re-install-hosts.html"><strong>Next</strong>11.5. Re-Installing Hosts</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/requirements-templates.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/requirements-templates.html b/docs/tmp/en-US/html/requirements-templates.html
deleted file mode 100644
index 5b3e9e7..0000000
--- a/docs/tmp/en-US/html/requirements-templates.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>12.2. Requirements for Templates</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-templates.html" title="Chapter 12. Working with Templates" /><link rel="prev" href="create-templates-overview.html" title="12.1. Creating Templates: Overview" /><link rel="next" href="best-practices-templates.html" title="12.3. Best Practices for Templates" /></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="create-templates-overview.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="best-practices-templates.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="requirements-templates" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="requirements-templates">12.2. Requirements for Templates</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- For XenServer, install PV drivers / Xen tools on each template that you create. This will enable live migration and clean guest shutdown.
- </div></li><li class="listitem"><div class="para">
- For vSphere, install VMware Tools on each template that you create. This will enable console view to work properly.
- </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="create-templates-overview.html"><strong>Prev</strong>12.1. Creating Templates: Overview</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="best-practices-templates.html"><strong>Next</strong>12.3. Best Practices for Templates</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/responses.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/responses.html b/docs/tmp/en-US/html/responses.html
deleted file mode 100644
index a21f9a1..0000000
--- a/docs/tmp/en-US/html/responses.html
+++ /dev/null
@@ -1,49 +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.4. Responses</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="signing-api-requests.html" title="4.3. Signing API Requests" /><link rel="next" href="asynchronous-commands.html" title="4.5. Asynchronous Commands" /></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="signing-api-requests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="asynchronous-commands.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="responses" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="responses">4.4. Responses</h2></div></div></div><div xml:lang="en-US" class="section" id="response-formats" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="response-formats">4.4.1. Response Formats: XML and JSON</h3></div></div></div><div class="para">
- CloudStack supports two formats as the response to an API call. The default response is XML. If you would like the response to be in JSON, add &response=json to the Command String.
- </div><div class="para">
- Sample XML Response:
- </div><pre class="programlisting">
- <listipaddressesresponse>
- <allocatedipaddress>
- <ipaddress>192.168.10.141</ipaddress>
- <allocated>2009-09-18T13:16:10-0700</allocated>
- <zoneid>4</zoneid>
- <zonename>WC</zonename>
- <issourcenat>true</issourcenat>
- </allocatedipaddress>
- </listipaddressesresponse>
-</pre><div class="para">
- Sample JSON Response:
- </div><pre class="programlisting">
- { "listipaddressesresponse" :
- { "allocatedipaddress" :
- [
- {
- "ipaddress" : "192.168.10.141",
- "allocated" : "2009-09-18T13:16:10-0700",
- "zoneid" : "4",
- "zonename" : "WC",
- "issourcenat" : "true"
- }
- ]
- }
- }
-</pre></div><div xml:lang="en-US" class="section" id="max-result-page-returned" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="max-result-page-returned">4.4.2. Maximum Result Pages Returned</h3></div></div></div><div class="para">
- For each cloud, there is a default upper limit on the number of results that any API command will return in a single page. This is to help prevent overloading the cloud servers and prevent DOS attacks. For example, if the page size limit is 500 and a command returns 10,000 results, the command will return 20 pages.
- </div><div class="para">
- The default page size limit can be different for each cloud. It is set in the global configuration parameter default.page.size. If your cloud has many users with lots of VMs, you might need to increase the value of this parameter. At the same time, be careful not to set it so high that your site can be taken down by an enormous return from an API call. For more information about how to set global configuration parameters, see "Describe Your Deployment" in the Installation Guide.
- </div><div class="para">
- To decrease the page size limit for an individual API command, override the global setting with the page and pagesize parameters, which are available in any list* command (listCapabilities, listDiskOfferings, etc.).
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Both parameters must be specified together.
- </div></li><li class="listitem"><div class="para">
- The value of the pagesize parameter must be smaller than the value of default.page.size. That is, you can not increase the number of possible items in a result page, only decrease it.
- </div></li></ul></div><div class="para">
- For syntax information on the list* commands, see the API Reference.
- </div></div><div xml:lang="en-US" class="section" id="error-handling" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="error-handling">4.4.3. Error Handling</h3></div></div></div><div class="para">
- If an error occurs while processing an API request, the appropriate response in the format specified is returned. Each error response consists of an error code and an error text describing what possibly can go wrong. For an example error response, see page 12.
- </div><div class="para">
- An HTTP error code of 401 is always returned if API request was rejected due to bad signatures, missing API Keys, or the user simply did not have the permissions to execute the command.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="signing-api-requests.html"><strong>Prev</strong>4.3. Signing API Requests</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="asynchronous-commands.html"><strong>Next</strong>4.5. Asynchronous Commands</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/roles.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/roles.html b/docs/tmp/en-US/html/roles.html
deleted file mode 100644
index 18e91d1..0000000
--- a/docs/tmp/en-US/html/roles.html
+++ /dev/null
@@ -1,11 +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>2.1. Roles</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="developer-introduction.html" title="Chapter 2. Introduction for Developers" /><link rel="prev" href="developer-introduction.html" title="Chapter 2. Introduction for Developers" /><link rel="next" href="api-reference.html" title="2.2. API Reference Documentation" /></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="developer-introduction.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="api-reference.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="roles" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="roles">2.1. Roles</h2></div></div></div><div class="para">
- The CloudPlatform API supports three access roles:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Root Admin. Access to all features of the cloud, including both virtual and physical resource management.
- </div></li><li class="listitem"><div class="para">
- Domain Admin. Access to only the virtual resources of the clouds that belong to the administrator’s domain.
- </div></li><li class="listitem"><div class="para">
- User. Access to only the features that allow management of the user’s virtual instances, storage, and network.
- </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="developer-introduction.html"><strong>Prev</strong>Chapter 2. Introduction for Developers</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="api-reference.html"><strong>Next</strong>2.2. API Reference Documentation</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/scheduled-maintenance-maintenance-mode-hosts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/scheduled-maintenance-maintenance-mode-hosts.html b/docs/tmp/en-US/html/scheduled-maintenance-maintenance-mode-hosts.html
deleted file mode 100644
index 2881a3c..0000000
--- a/docs/tmp/en-US/html/scheduled-maintenance-maintenance-mode-hosts.html
+++ /dev/null
@@ -1,5 +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.2. Scheduled Maintenance and Maintenance Mode for 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="adding-hosts.html" title="11.1. Adding Hosts" /><link rel="next" href="disable-enable-zones-pods-clusters.html" title="11.3. Disabling and Enabling Zones, Pods, and Clusters" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Prod
uct 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="adding-hosts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="disable-enable-zones-pods-clusters.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="scheduled-maintenance-maintenance-mode-hosts" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="scheduled-maintenance-maintenance-mode-hosts">11.2. Scheduled Maintenance and Maintenance Mode for Hosts</h2></div></div></div><div class="para">
- You can place a host into maintenance mode. When maintenance mode is activated, the host becomes unavailable to receive new guest VMs, and the guest VMs already running on the host are seamlessly migrated to another host not in maintenance mode. This migration uses live migration technology and does not interrupt the execution of the guest.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="adding-hosts.html"><strong>Prev</strong>11.1. Adding 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="disable-enable-zones-pods-clusters.html"><strong>Next</strong>11.3. Disabling and Enabling Zones, Pods, and Clu...</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/secondary-storage-add.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/secondary-storage-add.html b/docs/tmp/en-US/html/secondary-storage-add.html
deleted file mode 100644
index c664203..0000000
--- a/docs/tmp/en-US/html/secondary-storage-add.html
+++ /dev/null
@@ -1,25 +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>7.7. Add Secondary Storage</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="provisioning-steps.html" title="Chapter 7. Steps to Provisioning Your Cloud Infrastructure" /><link rel="prev" href="primary-storage-add.html" title="7.6. Add Primary Storage" /><link rel="next" href="initialize-and-test.html" title="7.8. Initialize and Test" /></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" hre
f="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="primary-storage-add.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="initialize-and-test.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="secondary-storage-add" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="secondary-storage-add">7.7. Add Secondary Storage</h2></div></div></div><div class="section" id="sys-require-secondary-storage"><div class="titlepage"><div><div><h3 class="title" id="sys-require-secondary-storage">7.7.1. System Requirements for Secondary Storage</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- NFS storage appliance or Linux NFS server
- </div></li><li class="listitem"><div class="para">
- (Optional) OpenStack Object Storage (Swift) (see http://swift.openstack.org)
- </div></li><li class="listitem"><div class="para">
- 100GB minimum capacity
- </div></li><li class="listitem"><div class="para">
- A secondary storage device must be located in the same zone as the guest VMs it serves.
- </div></li><li class="listitem"><div class="para">
- Each Secondary Storage server must be available to all hosts in the zone.
- </div></li></ul></div></div><div class="section" id="adding-secondary-storage"><div class="titlepage"><div><div><h3 class="title" id="adding-secondary-storage">7.7.2. Adding Secondary Storage</h3></div></div></div><div class="para">
- When you create a new zone, the first secondary storage is added as part of that procedure. You can add secondary storage servers at any time to add more servers to an existing zone.
- </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
- Be sure there is nothing stored on the server. Adding the server to CloudStack will destroy any existing data.
- </div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- If you are going to use Swift for cloud-wide secondary storage, you must add the Swift storage to CloudStack before you add the local zone secondary storage servers. See <a class="xref" href="zone-add.html">Section 7.2, “Adding a Zone”</a>.
- </div></li><li class="listitem"><div class="para">
- To prepare for local zone secondary storage, you should have created and mounted an NFS share during Management Server installation. <span>See Preparing NFS Shares in the Installation Guide.</span>
- </div></li><li class="listitem"><div class="para">
- Make sure you prepared the system VM template during Management Server installation. <span>See Prepare the System VM Template in the Installation Guide.</span>
- </div></li><li class="listitem"><div class="para">
- Now that the secondary storage server for per-zone storage is prepared, add it to CloudStack. Secondary storage is added as part of the procedure for adding a new zone. See <a class="xref" href="zone-add.html">Section 7.2, “Adding a Zone”</a>.
- </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="primary-storage-add.html"><strong>Prev</strong>7.6. Add Primary Storage</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="initialize-and-test.html"><strong>Next</strong>7.8. Initialize and Test</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/secondary-storage-outage-and-data-loss.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/secondary-storage-outage-and-data-loss.html b/docs/tmp/en-US/html/secondary-storage-outage-and-data-loss.html
deleted file mode 100644
index 8744d41..0000000
--- a/docs/tmp/en-US/html/secondary-storage-outage-and-data-loss.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>17.5. Secondary Storage Outage and Data Loss</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="sys-reliability-and-ha.html" title="Chapter 17. System Reliability and High Availability" /><link rel="prev" href="primary-storage-outage-and-data-loss.html" title="17.4. Primary Storage Outage and Data Loss" /><link rel="next" href="manage-cloud.html" title="Chapter 18. Managing 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="primary-storage-outage-and-data-loss.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="manage-cloud.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="secondary-storage-outage-and-data-loss" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="secondary-storage-outage-and-data-loss">17.5. Secondary Storage Outage and Data Loss</h2></div></div></div><div class="para">
- For a Zone that has only one secondary storage server, a secondary storage outage will have feature level impact to the system but will not impact running guest VMs. It may become impossible to create a VM with the selected template for a user. A user may also not be able to save snapshots or examine/restore saved snapshots. These features will automatically be available when the secondary storage comes back online.
- </div><div class="para">
- Secondary storage data loss will impact recently added user data including templates, snapshots, and ISO images. Secondary storage should be backed up periodically. Multiple secondary storage servers can be provisioned within each zone to increase the scalability of the system.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="primary-storage-outage-and-data-loss.html"><strong>Prev</strong>17.4. Primary 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="manage-cloud.html"><strong>Next</strong>Chapter 18. Managing the Cloud</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/secondary-storage-vm.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/secondary-storage-vm.html b/docs/tmp/en-US/html/secondary-storage-vm.html
deleted file mode 100644
index 37c7fd7..0000000
--- a/docs/tmp/en-US/html/secondary-storage-vm.html
+++ /dev/null
@@ -1,11 +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>16.5. Secondary Storage VM</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-system-vm.html" title="Chapter 16. Working with System Virtual Machines" /><link rel="prev" href="virtual-router.html" title="16.4. Virtual Router" /><link rel="next" href="sys-reliability-and-ha.html" title="Chapter 17. System Reliability and High Availability" /></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="virtual-router.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sys-reliability-and-ha.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="secondary-storage-vm" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="secondary-storage-vm">16.5. Secondary Storage VM</h2></div></div></div><div class="para">
- In addition to the hosts, CloudStack’s Secondary Storage VM mounts and writes to secondary storage.
- </div><div class="para">
- Submissions to secondary storage go through the Secondary Storage VM. The Secondary Storage VM can retrieve templates and ISO images from URLs using a variety of protocols.
- </div><div class="para">
- The secondary storage VM provides a background task that takes care of a variety of secondary storage activities: downloading a new template to a Zone, copying templates between Zones, and snapshot backups.
- </div><div class="para">
- The administrator can log in to the secondary storage VM if needed.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="virtual-router.html"><strong>Prev</strong>16.4. Virtual Router</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="sys-reliability-and-ha.html"><strong>Next</strong>Chapter 17. System Reliability and High Availabil...</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/secondary-storage.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/secondary-storage.html b/docs/tmp/en-US/html/secondary-storage.html
deleted file mode 100644
index 234d0c7..0000000
--- a/docs/tmp/en-US/html/secondary-storage.html
+++ /dev/null
@@ -1,5 +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>13.3. Secondary Storage</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="storage.html" title="Chapter 13. Working With Storage" /><link rel="prev" href="primary-storage.html" title="13.2. Primary Storage" /><link rel="next" href="working-with-volumes.html" title="13.4. Using Swift for Secondary Storage" /></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="primary-storage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="working-with-volumes.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="secondary-storage" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="secondary-storage">13.3. Secondary Storage</h2></div></div></div><div class="para">
- This section gives concepts and technical details about CloudStack secondary storage. For information about how to install and configure secondary storage through the CloudStack UI, see the Advanced Installation Guide.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="primary-storage.html"><strong>Prev</strong>13.2. Primary Storage</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="working-with-volumes.html"><strong>Next</strong>13.4. Using Swift for Secondary Storage</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/sect-source-builddebs.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/sect-source-builddebs.html b/docs/tmp/en-US/html/sect-source-builddebs.html
deleted file mode 100644
index 5456d26..0000000
--- a/docs/tmp/en-US/html/sect-source-builddebs.html
+++ /dev/null
@@ -1,54 +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>3.5. Building DEB packages</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="sect-source.html" title="Chapter 3. Building from Source" /><link rel="prev" href="sect-source-extract.html" title="3.4. Extracting source" /><link rel="next" href="sect-source-buildrpm.html" title="3.6. Building RPMs" /></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-extract.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-source-buildrpm.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="sect-source-builddebs" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-source-builddebs">3.5. Building DEB packages</h2></div></div></div><div class="para">
- In addition to the bootstrap dependencies, you'll also need to install several other dependencies. Note that we recommend using Maven 3, which is not currently available in 12.04.1 LTS. So, you'll also need to add a PPA repository that includes Maven 3. After running the command <code class="command">add-apt-repository</code>, you will be prompted to continue and a GPG key will be added.
- </div><pre class="screen">
-<code class="command">$ sudo apt-get update</code>
-<code class="command">$ sudo apt-get install python-software-properties</code>
-<code class="command">$ sudo add-apt-repository ppa:natecarlson/maven3</code>
-<code class="command">$ sudo apt-get update</code>
-<code class="command">$ sudo apt-get install ant debhelper openjdk-6-jdk tomcat6 libws-commons-util-java genisoimage python-mysqldb libcommons-codec-java libcommons-httpclient-java liblog4j1.2-java maven3</code></pre><div class="para">
- While we have defined, and you have presumably already installed the bootstrap prerequisites, there are a number of build time prerequisites that need to be resolved. CloudStack uses maven for dependency resolution. You can resolve the buildtime depdencies for CloudStack by running:
- </div><pre class="screen"><code class="command">$ mvn3 -P deps</code></pre><div class="para">
- Now that we have resolved the dependencies we can move on to building CloudStack and packaging them into DEBs by issuing the following command.
- </div><pre class="screen">
-<code class="command">$ dpkg-buildpackge -uc -us</code></pre><div class="para">
- This command will build 16 Debian packages. You should have all of the following:
- </div><pre class="programlisting">
-cloud-agent_4.0.0-incubating_amd64.deb
-cloud-agent-deps_4.0.0-incubating_amd64.deb
-cloud-agent-libs_4.0.0-incubating_amd64.deb
-cloud-awsapi_4.0.0-incubating_amd64.deb
-cloud-cli_4.0.0-incubating_amd64.deb
-cloud-client_4.0.0-incubating_amd64.deb
-cloud-client-ui_4.0.0-incubating_amd64.deb
-cloud-core_4.0.0-incubating_amd64.deb
-cloud-deps_4.0.0-incubating_amd64.deb
-cloud-python_4.0.0-incubating_amd64.deb
-cloud-scripts_4.0.0-incubating_amd64.deb
-cloud-server_4.0.0-incubating_amd64.deb
-cloud-setup_4.0.0-incubating_amd64.deb
-cloud-system-iso_4.0.0-incubating_amd64.deb
-cloud-usage_4.0.0-incubating_amd64.deb
-cloud-utils_4.0.0-incubating_amd64.deb
-</pre><div class="section" id="sect-source-builddebs-repo"><div class="titlepage"><div><div><h3 class="title" id="sect-source-builddebs-repo">3.5.1. Setting up an APT repo</h3></div></div></div><div class="para">
- After you've created the packages, you'll want to copy them to a system where you can serve the packages over HTTP. You'll create a directory for the packages and then use <code class="code">dpkg-scanpackages</code> to create <code class="filename">Packages.gz</code>, which holds information about the archive structure. Finally, you'll add the repository to your system(s) so you can install the packages using APT.
- </div><div class="para">
- The first step is to make sure that you have the <span class="application"><strong>dpkg-dev</strong></span> package installed. This should have been installed when you pulled in the <span class="application"><strong>debhelper</strong></span> application previously, but if you're generating <code class="filename">Packages.gz</code> on a different system, be sure that it's installed there as well.
- </div><pre class="screen"><code class="command">$ sudo apt-get install dpkg-dev</code></pre><div class="para">
- The next step is to copy the DEBs to the directory where they can be served over HTTP. We'll use <code class="filename">/var/www/cloudstack/repo</code> in the examples, but change the directory to whatever works for you.
- </div><pre class="screen">
-<code class="command">sudo mkdir -p /var/www/cloudstack/repo/binary</code>
-<code class="command">sudo cp *.deb /var/www/cloudstack/repo/binary</code>
-<code class="command">sudo cd /var/www/cloudstack/repo/binary</code>
-<code class="command">sudo dpkg-scanpackages . /dev/null | tee Packages | gzip -9 > Packages.gz</code></pre><div class="note"><div class="admonition_header"><h2>Note: Override Files</h2></div><div class="admonition"><div class="para">
- You can safely ignore the warning about a missing override file.
- </div></div></div><div class="para">
- Now you should have all of the DEB packages and <code class="filename">Packages.gz</code> in the <code class="filename">binary</code> directory and available over HTTP. (You may want to use <code class="command">wget</code> or <code class="command">curl</code> to test this before moving on to the next step.)
- </div></div><div class="section" id="sect-source-builddebs-repo2"><div class="titlepage"><div><div><h3 class="title" id="sect-source-builddebs-repo2">3.5.2. Configuring your machines to use the APT repository</h3></div></div></div><div class="para">
- Now that we have created the repository, you need to configure your machine to make use of the APT repository. You can do this by adding a repository file under <code class="filename">/etc/apt/sources.list.d</code>. Use your preferred editor to create <code class="filename">/etc/apt/sources.list.d/cloudstack.list</code> with this line:
- </div><pre class="programlisting">deb http://<em class="replaceable"><code>server.url</code></em>/cloudstack/repo binary/</pre><div class="para">
- Now that you have the repository info in place, you'll want to run another update so that APT knows where to find the CloudStack packages.
- </div><pre class="screen"><code class="command">$ sudo apt-get update</code></pre><div class="para">
- You can now move on to the instructions under Install on Ubuntu.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-source-extract.html"><strong>Prev</strong>3.4. Extracting source</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="sect-source-buildrpm.html"><strong>Next</strong>3.6. Building RPMs</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/sect-source-buildrpm.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/sect-source-buildrpm.html b/docs/tmp/en-US/html/sect-source-buildrpm.html
deleted file mode 100644
index f4569f1..0000000
--- a/docs/tmp/en-US/html/sect-source-buildrpm.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>3.6. Building RPMs</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="sect-source.html" title="Chapter 3. Building from Source" /><link rel="prev" href="sect-source-builddebs.html" title="3.5. Building DEB packages" /><link rel="next" href="installation.html" title="Chapter 4. Installation" /></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="sect-source-builddebs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="installation.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="sect-source-buildrpm" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-source-buildrpm">3.6. Building RPMs</h2></div></div></div><div class="para">
- While we have defined, and you have presumably already installed the bootstrap prerequisites, there are a number of build time prerequisites that need to be resolved. CloudStack uses maven for dependency resolution. You can resolve the buildtime depdencies for CloudStack by running the following command:
-<pre class="programlisting"><code class="prompt">$</code> <code class="command">mvn</code> -P deps</pre>
-
- </div><div class="para">
- Now that we have resolved the dependencies we can move on to building CloudStack and packaging them into RPMs by issuing the following command.
-<pre class="programlisting"><code class="prompt">$</code> <code class="command">./waf</code> rpm</pre>
-
- </div><div class="para">
- Once this completes, you should find assembled RPMs in <code class="filename">artifacts/rpmbuild/RPMS/x86_64</code>
- </div><div class="section" id="sect-source-buildrpm-repo"><div class="titlepage"><div><div><h3 class="title" id="sect-source-buildrpm-repo">3.6.1. Creating a yum repo</h3></div></div></div><div class="para">
- While RPMs is an ideal packaging format - it's most easily consumed from yum repositories over a network. We'll move into the directory with the newly created RPMs by issuing the following command:
-<pre class="programlisting"><code class="prompt">$</code> <code class="command">cd</code> artifacts/rpmbuild/RPMS/x86_64</pre>
-
- </div><div class="para">
- Next we'll issue a command to create the repository metadata by issuing the following command:
-<pre class="programlisting"><code class="prompt">$</code> <code class="command">createrepo</code> ./</pre>
-
- </div><div class="para">
- The files and directories within our current working directory can now be uploaded to a web server and serve as a yum repository
- </div></div><div class="section" id="sect-source-buildrpm-repo2"><div class="titlepage"><div><div><h3 class="title" id="sect-source-buildrpm-repo2">3.6.2. Configuring your systems to use your new yum repository</h3></div></div></div><div class="para">
- Now that your yum repository is populated with RPMs and metadata we need to configure our machines that need to install CloudStack. We will create a file at <code class="filename">/etc/yum.repos.d/cloudstack.repo</code> with the following content:
-<pre class="programlisting">
-[apache-cloudstack]
-name=Apache CloudStack
-baseurl=http://<em class="replaceable"><code>webserver.tld/path/to/repo</code></em>
-enabled=1
-gpgcheck=0
-</pre>
-
- </div><div class="para">
- Completing this step will allow you to easily install CloudStack on a number of machines across the network.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-source-builddebs.html"><strong>Prev</strong>3.5. Building DEB packages</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="installation.html"><strong>Next</strong>Chapter 4. Installation</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/sect-source-extract.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/sect-source-extract.html b/docs/tmp/en-US/html/sect-source-extract.html
deleted file mode 100644
index ead718d..0000000
--- a/docs/tmp/en-US/html/sect-source-extract.html
+++ /dev/null
@@ -1,11 +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>3.4. Extracting source</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="sect-source.html" title="Chapter 3. Building from Source" /><link rel="prev" href="sect-source-prereq.html" title="3.3. Prerequisites for building Apache CloudStack" /><link rel="next" href="sect-source-builddebs.html" title="3.5. Building DEB packages" /></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="htt
p://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="sect-source-prereq.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-source-builddebs.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="sect-source-extract" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-source-extract">3.4. Extracting source</h2></div></div></div><div class="para">
- Extracting the CloudStack release is relatively simple and can be done with a single command as follows:
-<pre class="programlisting"><code class="prompt">$</code> <code class="command">tar</code> -jxvf apache-cloudstack-4.0.0-incubating-src.tar.bz2</pre>
-
- </div><div class="para">
- You can now move into the directory:
-<pre class="programlisting"><code class="prompt">$</code> <code class="command">cd</code> ./apache-cloudstack-4.0.0-incubating-src</pre>
-
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-source-prereq.html"><strong>Prev</strong>3.3. Prerequisites for building Apache CloudStack</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="sect-source-builddebs.html"><strong>Next</strong>3.5. Building DEB packages</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/sect-source-gettingrelease.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/sect-source-gettingrelease.html b/docs/tmp/en-US/html/sect-source-gettingrelease.html
deleted file mode 100644
index 71eb52b..0000000
--- a/docs/tmp/en-US/html/sect-source-gettingrelease.html
+++ /dev/null
@@ -1,15 +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>3.1. Getting the release</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="sect-source.html" title="Chapter 3. Building from Source" /><link rel="prev" href="sect-source.html" title="Chapter 3. Building from Source" /><link rel="next" href="sect-source-verify.html" title="3.2. Verifying the downloaded release" /></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.cloud
stack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-source.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-source-verify.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="sect-source-gettingrelease" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-source-gettingrelease">3.1. Getting the release</h2></div></div></div><div class="para">
- You can download the latest CloudStack release from the <a href="http://incubator.apache.org/cloudstack/downloads.html"> Apache CloudStack project download page</a>.
- </div><div class="para">
- You'll notice several links under the 'Latest release' section.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- <a href="http://www.apache.org/dyn/closer.cgi/dist/incubator/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2"> apache-cloudstack-4.0.0-incubating-src.tar.bz2</a> - This is the link to the release itself.
- </div></li><li class="listitem"><div class="para">
- <a href="http://www.apache.org/dist/incubator/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc">PGP</a> - This is a detached cryptographic signature that can be used to help verify the authenticity of the release.
- </div></li><li class="listitem"><div class="para">
- <a href="http://www.apache.org/dist/incubator/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5">MD5</a> - An MD5 hash of the release to aid in verify the validity of the release download.
- </div></li><li class="listitem"><div class="para">
- <a href="http://www.apache.org/dist/incubator/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.sha">SHA512</a> - A SHA512 hash of the release to aid in verify the validity of the release download.
- </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-source.html"><strong>Prev</strong>Chapter 3. Building from Source</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="sect-source-verify.html"><strong>Next</strong>3.2. Verifying the downloaded release</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/sect-source-prereq.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/sect-source-prereq.html b/docs/tmp/en-US/html/sect-source-prereq.html
deleted file mode 100644
index 5bfa990..0000000
--- a/docs/tmp/en-US/html/sect-source-prereq.html
+++ /dev/null
@@ -1,17 +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>3.3. Prerequisites for building Apache CloudStack</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="sect-source.html" title="Chapter 3. Building from Source" /><link rel="prev" href="sect-source-verify.html" title="3.2. Verifying the downloaded release" /><link rel="next" href="sect-source-extract.html" title="3.4. Extracting source" /></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="sect-source-verify.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-source-extract.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="sect-source-prereq" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-source-prereq">3.3. Prerequisites for building Apache CloudStack</h2></div></div></div><div class="para">
- There are a number of prerequisites needed to build CloudStack. This document assumes compilation on a Linux system that uses RPMs or DEBs for package management.
- </div><div class="para">
- The minimum bootstrapped prerequisites for building CloudStack includes the following:
- <div class="orderedlist"><ol><li class="listitem"><div class="para">
- ant
- </div></li><li class="listitem"><div class="para">
- maven (version 3)
- </div></li><li class="listitem"><div class="para">
- Java (Java 6/OpenJDK 1.6)
- </div></li><li class="listitem"><div class="para">
- rpmbuild or dpkg-dev
- </div></li></ol></div>
-
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-source-verify.html"><strong>Prev</strong>3.2. Verifying the downloaded release</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="sect-source-extract.html"><strong>Next</strong>3.4. Extracting source</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/sect-source-verify.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/sect-source-verify.html b/docs/tmp/en-US/html/sect-source-verify.html
deleted file mode 100644
index 0d02a4c..0000000
--- a/docs/tmp/en-US/html/sect-source-verify.html
+++ /dev/null
@@ -1,29 +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>3.2. Verifying the downloaded release</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="sect-source.html" title="Chapter 3. Building from Source" /><link rel="prev" href="sect-source-gettingrelease.html" title="3.1. Getting the release" /><link rel="next" href="sect-source-prereq.html" title="3.3. Prerequisites for building Apache CloudStack" /></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="sect-source-gettingrelease.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-source-prereq.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="sect-source-verify" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sect-source-verify">3.2. Verifying the downloaded release</h2></div></div></div><div class="para">
- There are a number of mechanisms to check the authenticity and validity of a downloaded release.
- </div><div class="section" id="sect-source-verify-keys"><div class="titlepage"><div><div><h3 class="title" id="sect-source-verify-keys">3.2.1. Getting the KEYS</h3></div></div></div><div class="para">
- To enable you to verify the GPG signature, you will need to download the <a href="http://www.apache.org/dist/dev/incubator/cloudstack/KEYS">KEYS</a> file.
- </div><div class="para">
- You next need to import those keys, which you can do by running the following command:
-<pre class="programlisting"><code class="prompt">#</code> <code class="command">gpg</code> --import KEYS</pre>
-
- </div></div><div class="section" id="sect-source-verify-gpg"><div class="titlepage"><div><div><h3 class="title" id="sect-source-verify-gpg">3.2.2. GPG</h3></div></div></div><div class="para">
- The CloudStack project provides a detached GPG signature of the release. To check the signature, run the following command:
-<pre class="programlisting"><code class="prompt">$</code> <code class="command">gpg</code> --verify apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc</pre>
-
- </div><div class="para">
- If the signature is valid you will see a line of output that contains 'Good signature'.
- </div></div><div class="section" id="sect-source-verify-md5"><div class="titlepage"><div><div><h3 class="title" id="sect-source-verify-md5">3.2.3. MD5</h3></div></div></div><div class="para">
- In addition to the cryptographic signature, the CloudStack provides a number of cryptographic hashes to aid in assurance of validity of the downloaded release. You can verify this hash by executing the following command:
-<pre class="programlisting"><code class="prompt">$</code> <code class="command">gpg</code> --print-md MD5 apache-cloudstack-4.0.0-incubating-src.tar.bz2 | <code class="command">diff</code> - apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5</pre>
-
- </div><div class="para">
- If this successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server.
- </div></div><div class="section" id="sect-source-verify-sha512"><div class="titlepage"><div><div><h3 class="title" id="sect-source-verify-sha512">3.2.4. SHA512</h3></div></div></div><div class="para">
- In addition to the MD5 hash, the CloudStack project provides a SHA512 cryptographic hash to aid in assurance of the validity of the downloaded release. You can verify this hash by executing the following command:
-<pre class="programlisting"><code class="prompt">$</code> <code class="command">gpg</code> --print-md SHA512 apache-cloudstack-4.0.0-incubating-src.tar.bz2 | <code class="command">diff</code> - apache-cloudstack-4.0.0-incubating-src.tar.bz2.sha</pre>
-
- </div><div class="para">
- If this command successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-source-gettingrelease.html"><strong>Prev</strong>3.1. Getting the release</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="sect-source-prereq.html"><strong>Next</strong>3.3. Prerequisites for building Apache CloudStack</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/sect-source.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/sect-source.html b/docs/tmp/en-US/html/sect-source.html
deleted file mode 100644
index 29408ac..0000000
--- a/docs/tmp/en-US/html/sect-source.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>Chapter 3. Building from Source</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="about-physical-networks.html" title="2.7. About Physical Networks" /><link rel="next" href="sect-source-gettingrelease.html" title="3.1. Getting the release" /></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.clou
dstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="about-physical-networks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-source-gettingrelease.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="sect-source" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. Building from Source</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="sect-source-gettingrelease.html">3.1. Getting the release</a></span></dt><dt><span class="section"><a href="sect-source-verify.html">3.2. Verifying the downloaded release</a></span></dt><dd><dl><dt><span class="section"><a href="sect-source-verify.html#sect-source-verify-keys">3.2.1. Getting the KEYS</a></span></dt><dt><span class="section"><a href="sect-source-verify.html#sect-source-verify-gpg">3.2.2. GPG</a></span></dt><dt><span cla
ss="section"><a href="sect-source-verify.html#sect-source-verify-md5">3.2.3. MD5</a></span></dt><dt><span class="section"><a href="sect-source-verify.html#sect-source-verify-sha512">3.2.4. SHA512</a></span></dt></dl></dd><dt><span class="section"><a href="sect-source-prereq.html">3.3. Prerequisites for building Apache CloudStack</a></span></dt><dt><span class="section"><a href="sect-source-extract.html">3.4. Extracting source</a></span></dt><dt><span class="section"><a href="sect-source-builddebs.html">3.5. Building DEB packages</a></span></dt><dd><dl><dt><span class="section"><a href="sect-source-builddebs.html#sect-source-builddebs-repo">3.5.1. Setting up an APT repo</a></span></dt><dt><span class="section"><a href="sect-source-builddebs.html#sect-source-builddebs-repo2">3.5.2. Configuring your machines to use the APT repository</a></span></dt></dl></dd><dt><span class="section"><a href="sect-source-buildrpm.html">3.6. Building RPMs</a></span></dt><dd><dl><dt><span class="section"
><a href="sect-source-buildrpm.html#sect-source-buildrpm-repo">3.6.1. Creating a yum repo</a></span></dt><dt><span class="section"><a href="sect-source-buildrpm.html#sect-source-buildrpm-repo2">3.6.2. Configuring your systems to use your new yum repository</a></span></dt></dl></dd></dl></div><div class="para">
- The official CloudStack release is always in source code form. While there may exist convenience binaries in various forms from a number of places, the source is the canonical release will be source. In this document we'll cover acquiring the source release, building that into binary, deployable packages.
- </div><div class="para">
- While building and deploying directly from source is certainly possible, the reality of Infrastructure-as-a-Service cloud computing implies a need to deploy packages on a potentially large number of systems, which RPMs and DEBs fill nicely.
- </div><div class="para">
- Building and deploying directly from source is thus outside the scope of this document, but is documented in the INSTALL.md file in the release.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-physical-networks.html"><strong>Prev</strong>2.7. About Physical Networks</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="sect-source-gettingrelease.html"><strong>Next</strong>3.1. Getting the release</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/security-groups.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/security-groups.html b/docs/tmp/en-US/html/security-groups.html
deleted file mode 100644
index b709b33..0000000
--- a/docs/tmp/en-US/html/security-groups.html
+++ /dev/null
@@ -1,74 +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.7. Security Groups</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="using-multiple-guest-networks.html" title="15.6. Using Multiple Guest Networks" /><link rel="next" href="external-firewalls-and-load-balancers.html" title="15.8. External Firewalls and Load Balancers" /></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="using-multiple-guest-networks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="external-firewalls-and-load-balancers.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="security-groups" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="security-groups">15.7. Security Groups</h2></div></div></div><div xml:lang="en-US" class="section" id="about-security-groups" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="about-security-groups">15.7.1. About Security Groups</h3></div></div></div><div class="para">
- Security groups provide a way to isolate traffic to VMs. A security group is a group of VMs that filter their incoming and outgoing traffic according to a set of rules, called ingress and egress rules. These rules filter network traffic according to the IP address that is attempting to communicate with the VM. Security groups are particularly useful in zones that use basic networking, because there is a single guest network for all guest VMs. In CloudStack 3.0.3 - 3.0.5, security groups are supported only in zones that use basic networking.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- In a zone that uses advanced networking, you can instead define multiple guest networks to isolate traffic to VMs.
- </div></div></div><div class="para">
- </div><div class="para">
- Each CloudStack account comes with a default security group that denies all inbound traffic and allows all outbound traffic. The default security group can be modified so that all new VMs inherit some other desired set of rules.
- </div><div class="para">
- Any CloudStack user can set up any number of additional security groups. When a new VM is launched, it is assigned to the default security group unless another user-defined security group is specified. A VM can be a member of any number of security groups. Once a VM is assigned to a security group, it remains in that group for its entire lifetime; you can not move a running VM from one security group to another.
- </div><div class="para">
- You can modify a security group by deleting or adding any number of ingress and egress rules. When you do, the new rules apply to all VMs in the group, whether running or stopped.
- </div><div class="para">
- If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule.
- </div></div><div xml:lang="en-US" class="section" id="add-security-group" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="add-security-group">15.7.2. Adding a Security Group</h3></div></div></div><div class="para">
- A user or administrator can define a new security group.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network
- </div></li><li class="listitem"><div class="para">
- In Select view, choose Security Groups.
- </div></li><li class="listitem"><div class="para">
- Click Add Security Group.
- </div></li><li class="listitem"><div class="para">
- Provide a name and description.
- </div></li><li class="listitem"><div class="para">
- Click OK.
- </div><div class="para">
- The new security group appears in the Security Groups Details tab.
- </div></li><li class="listitem"><div class="para">
- To make the security group useful, continue to Adding Ingress and Egress Rules to a Security Group.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="enable-security-groups" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="enable-security-groups">15.7.3. Enabling Security Groups</h3></div></div></div><div class="para">
- In order for security groups to function in a zone, the security groups feature must first be enabled for the zone. The administrator can do this when creating a new zone, by selecting a network offering that includes security groups. The procedure is described in Basic Zone Configuration in the Advanced Installation Guide.
- </div></div><div xml:lang="en-US" class="section" id="add-ingress-egress-rules" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="add-ingress-egress-rules">15.7.4. Adding Ingress and Egress Rules to a Security Group</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as an administrator or end user.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, choose Network
- </div></li><li class="listitem"><div class="para">
- In Select view, choose Security Groups, then click the security group you want .
- </div></li><li class="listitem"><div class="para">
- To add an ingress rule, click the Ingress Rules tab and fill out the following fields to specify what network traffic is allowed into VM instances in this security group. If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Add by CIDR/Account</strong></span>. Indicate whether the source of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow incoming traffic from all VMs in another security group
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Protocol</strong></span>. The networking protocol that sources will use to send traffic to the security group. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Start Port, End Port</strong></span>. (TCP, UDP only) A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>ICMP Type, ICMP Code</strong></span>. (ICMP only) The type of message and error code that will be accepted.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>CIDR</strong></span>. (Add by CIDR only) To accept only traffic from IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is the base IP address of the incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Account, Security Group</strong></span>. (Add by Account only) To accept only traffic from another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter the same name you used in step 7.
- </div></li></ul></div><div class="para">
- The following example allows inbound HTTP access from anywhere:
- </div><div class="mediaobject"><img src="./images/http-access.png" width="444" alt="httpaccess.png: allows inbound HTTP access from anywhere" /></div></li><li class="listitem"><div class="para">
- To add an egress rule, click the Egress Rules tab and fill out the following fields to specify what type of traffic is allowed to be sent out of VM instances in this security group. If no egress rules are specified, then all traffic will be allowed out. Once egress rules are specified, the following types of traffic are allowed out: traffic specified in egress rules; queries to DNS and DHCP servers; and responses to any traffic that has been allowed in through an ingress rule
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Add by CIDR/Account</strong></span>. Indicate whether the destination of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow outgoing traffic to all VMs in another security group.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Protocol</strong></span>. The networking protocol that VMs will use to send outgoing traffic. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Start Port, End Port</strong></span>. (TCP, UDP only) A range of listening ports that are the destination for the outgoing traffic. If you are opening a single port, use the same number in both fields.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>ICMP Type, ICMP Code</strong></span>. (ICMP only) The type of message and error code that will be sent
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>CIDR</strong></span>. (Add by CIDR only) To send traffic only to IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is the base IP address of the destination. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Account, Security Group</strong></span>. (Add by Account only) To allow traffic to be sent to another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter its name.
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Click Add.
- </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="using-multiple-guest-networks.html"><strong>Prev</strong>15.6. Using Multiple Guest Networks</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="external-firewalls-and-load-balancers.html"><strong>Next</strong>15.8. External Firewalls and Load Balancers</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/separate_storage_network.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/separate_storage_network.html b/docs/tmp/en-US/html/separate_storage_network.html
deleted file mode 100644
index 6b0ac60..0000000
--- a/docs/tmp/en-US/html/separate_storage_network.html
+++ /dev/null
@@ -1,5 +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.3. Separate Storage Network</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="large_scale_redundant_setup.html" title="9.2. Large-Scale Redundant Setup" /><link rel="next" href="multi_node_management_server.html" title="9.4. Multi-Node Management Server" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" a
lt="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="large_scale_redundant_setup.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="multi_node_management_server.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="separate_storage_network" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="separate_storage_network">9.3. Separate Storage Network</h2></div></div></div><div class="para">
- In the large-scale redundant setup described in the previous section, storage traffic can overload the management network. A separate storage network is optional for deployments. Storage protocols such as iSCSI are sensitive to network delays. A separate storage network ensures guest network traffic contention does not impact storage performance.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="large_scale_redundant_setup.html"><strong>Prev</strong>9.2. Large-Scale Redundant Setup</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="multi_node_management_server.html"><strong>Next</strong>9.4. Multi-Node Management Server</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/set-database-buffer-pool-size.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/set-database-buffer-pool-size.html b/docs/tmp/en-US/html/set-database-buffer-pool-size.html
deleted file mode 100644
index f716235..0000000
--- a/docs/tmp/en-US/html/set-database-buffer-pool-size.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>21.3. Set Database Buffer Pool Size</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="tuning.html" title="Chapter 21. Tuning" /><link rel="prev" href="increase-management-server-max-memory.html" title="21.2. Increase Management Server Maximum Memory" /><link rel="next" href="set-monitor-total-vm-limits-per-host.html" title="21.4. Set and Monitor Total VM Limits per Host" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Pro
duct 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="increase-management-server-max-memory.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="set-monitor-total-vm-limits-per-host.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="set-database-buffer-pool-size" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="set-database-buffer-pool-size">21.3. Set Database Buffer Pool Size</h2></div></div></div><div class="para">
- It is important to provide enough memory space for the MySQL database to cache data and indexes:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Edit the Tomcat configuration file:
- </div><pre class="programlisting">/etc/my.cnf</pre></li><li class="listitem"><div class="para">
- Insert the following line in the [mysqld] section, below the datadir line. Use a value that is appropriate for your situation. We recommend setting the buffer pool at 40% of RAM if MySQL is on the same server as the management server or 70% of RAM if MySQL has a dedicated server. The following example assumes a dedicated server with 1024M of RAM.
- </div><pre class="programlisting">innodb_buffer_pool_size=700M</pre></li><li class="listitem"><div class="para">
- Restart the MySQL service.
- </div><pre class="programlisting"># service mysqld restart</pre></li></ol></div><div class="para">
- For more information about the buffer pool, see "The InnoDB Buffer Pool" at <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-buffer-pool.html">MySQL Reference Manual</a>.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="increase-management-server-max-memory.html"><strong>Prev</strong>21.2. Increase Management Server Maximum Memory</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="set-monitor-total-vm-limits-per-host.html"><strong>Next</strong>21.4. Set and Monitor Total VM Limits per Host</a></li></ul></body></html>