You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by jz...@apache.org on 2012/11/08 07:13:09 UTC
[11/52] [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/epub/OEBPS/provisioning-steps.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/provisioning-steps.html b/docs/tmp/en-US/epub/OEBPS/provisioning-steps.html
deleted file mode 100644
index 63ab64b..0000000
--- a/docs/tmp/en-US/epub/OEBPS/provisioning-steps.html
+++ /dev/null
@@ -1,27 +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 7. Steps to Provisioning Your Cloud Infrastructure</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="" /></head><body><div class="chapter" id="provisioning-steps"><div class="titlepage"><div><div><h1 class="title">Chapter 7. Steps to Provisioning Your Cloud Infrastructure</h1></div></div></div><div class="para">
- This section tells how to add zones, pods, clusters, hosts, storage, and networks to your cloud. If you are unfamiliar with these entities, please begin by looking through <a class="xref" href="cloud-infrastructure-concepts.html">Chapter 2, <em>Cloud Infrastructure Concepts</em></a>.
- </div><div class="section" id="provisioning-steps-overview"><div class="titlepage"><div><div><h1 class="title" id="provisioning-steps-overview">7.1. Overview of Provisioning Steps</h1></div></div></div><div class="para">
- After the Management Server is installed and running, you can add the compute resources for it to manage. For an overview of how a CloudStack cloud infrastructure is organized, see <a class="xref" href="deployment-architecture-overview.html#cloud-infrastructure-overview">Section 1.3.2, “Cloud Infrastructure Overview”</a>.
- </div><div class="para">
- To provision the cloud infrastructure, or to scale it up at any time, follow these procedures:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Change the root password. See <a class="xref" href="ui.html#changing-root-password">Section 5.1.4, “Changing the Root Password”</a>.
- </div></li><li class="listitem"><div class="para">
- Add a zone. See <a class="xref" href="zone-add.html">Section 7.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 7.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 7.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 7.5, “Adding a Host”</a>.
- </div></li><li class="listitem"><div class="para">
- Add primary storage. See <a class="xref" href="primary-storage-add.html">Section 7.6, “Add Primary Storage”</a>.
- </div></li><li class="listitem"><div class="para">
- Add secondary storage. See <a class="xref" href="secondary-storage-add.html">Section 7.7, “Add Secondary Storage”</a>.
- </div></li><li class="listitem"><div class="para">
- Initialize and test the new cloud. See <a class="xref" href="initialize-and-test.html">Section 7.8, “Initialize and Test”</a>.
- </div></li></ol></div><div class="para">
- When you have finished these steps, you will have a deployment with the following basic structure:
- </div><div class="mediaobject"><img src="./images/provisioning-overview.png" width="444" alt="provisioning-overview.png: Conceptual overview of a basic deployment" /></div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/re-install-hosts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/re-install-hosts.html b/docs/tmp/en-US/epub/OEBPS/re-install-hosts.html
deleted file mode 100644
index 3e02be2..0000000
--- a/docs/tmp/en-US/epub/OEBPS/re-install-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.5. Re-Installing 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="" /></head><body><div class="section" id="re-install-hosts"><div class="titlepage"><div><div><h1 class="title" id="re-install-hosts">11.5. Re-Installing Hosts</h1></div></div></div><div class="para">
- You can re-install a host after placing it in maintenance mode and then removing it. If a host is down and cannot be placed in maintenance mode, it should still be removed before the re-install.
- </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/release-ip-address.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/release-ip-address.html b/docs/tmp/en-US/epub/OEBPS/release-ip-address.html
deleted file mode 100644
index 68cdb14..0000000
--- a/docs/tmp/en-US/epub/OEBPS/release-ip-address.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>15.12. Releasing an IP Address</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="" /></head><body><div class="section" id="release-ip-address"><div class="titlepage"><div><div><h1 class="title" id="release-ip-address">15.12. Releasing an IP Address</h1></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudPlatform 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">
- Click the name of the network where you want to work with.
- </div></li><li class="listitem"><div class="para">
- Click View IP Addresses.
- </div></li><li class="listitem"><div class="para">
- Click the IP address you want to release.
- </div></li><li class="listitem"><div class="para">
- Click the Release IP button
- <span class="inlinemediaobject"><img src="./images/release-ip-icon.png" alt="ReleaseIPButton.png: button to release an IP" /></span>
- .
- </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/removing-hosts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/removing-hosts.html b/docs/tmp/en-US/epub/OEBPS/removing-hosts.html
deleted file mode 100644
index 1e37947..0000000
--- a/docs/tmp/en-US/epub/OEBPS/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="" /></head><body><div class="section" id="removing-hosts"><div class="titlepage"><div><div><h1 class="title" id="removing-hosts">11.4. Removing Hosts</h1></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 class="section" id="removing-xenserver-kvm-hosts"><div class="titlepage"><div><div><h2 class="title" id="removing-xenserver-kvm-hosts">11.4.1. Removing XenServer and KVM Hosts</h2></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 class="section" id="removing-vsphere-hosts"><div class="titlepage"><div><div><h2 class="title" id="removing-vsphere-hosts">11.4.2. Removing vSphere Hosts</h2></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></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/requirements-templates.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/requirements-templates.html b/docs/tmp/en-US/epub/OEBPS/requirements-templates.html
deleted file mode 100644
index fdc7a02..0000000
--- a/docs/tmp/en-US/epub/OEBPS/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="" /></head><body><div class="section" id="requirements-templates"><div class="titlepage"><div><div><h1 class="title" id="requirements-templates">12.2. Requirements for Templates</h1></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></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/scheduled-maintenance-maintenance-mode-hosts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/scheduled-maintenance-maintenance-mode-hosts.html b/docs/tmp/en-US/epub/OEBPS/scheduled-maintenance-maintenance-mode-hosts.html
deleted file mode 100644
index 3d3cffd..0000000
--- a/docs/tmp/en-US/epub/OEBPS/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="" /></head><body><div class="section" id="scheduled-maintenance-maintenance-mode-hosts"><div class="titlepage"><div><div><h1 class="title" id="scheduled-maintenance-maintenance-mode-hosts">11.2. Scheduled Maintenance and Maintenance Mode for Hosts</h1></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></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/secondary-storage-add.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/secondary-storage-add.html b/docs/tmp/en-US/epub/OEBPS/secondary-storage-add.html
deleted file mode 100644
index ff4a8be..0000000
--- a/docs/tmp/en-US/epub/OEBPS/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="" /></head><body><div class="section" id="secondary-storage-add"><div class="titlepage"><div><div><h1 class="title" id="secondary-storage-add">7.7. Add Secondary Storage</h1></div></div></div><div class="section" id="sys-require-secondary-storage"><div class="titlepage"><div><div><h2 class="title" id="sys-require-secondary-storage">7.7.1. System Requirements for Secondary Storage</h2></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><h2 class="title" id="adding-secondary-storage">7.7.2. Adding Secondary Storage</h2></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></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/secondary-storage-outage-and-data-loss.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/secondary-storage-outage-and-data-loss.html b/docs/tmp/en-US/epub/OEBPS/secondary-storage-outage-and-data-loss.html
deleted file mode 100644
index c1f93cb..0000000
--- a/docs/tmp/en-US/epub/OEBPS/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="" /></head><body><div class="section" id="secondary-storage-outage-and-data-loss"><div class="titlepage"><div><div><h1 class="title" id="secondary-storage-outage-and-data-loss">17.5. Secondary Storage Outage and Data Loss</h1></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></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/secondary-storage-vm.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/secondary-storage-vm.html b/docs/tmp/en-US/epub/OEBPS/secondary-storage-vm.html
deleted file mode 100644
index 71d0dc9..0000000
--- a/docs/tmp/en-US/epub/OEBPS/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="" /></head><body><div class="section" id="secondary-storage-vm"><div class="titlepage"><div><div><h1 class="title" id="secondary-storage-vm">16.5. Secondary Storage VM</h1></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></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/secondary-storage.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/secondary-storage.html b/docs/tmp/en-US/epub/OEBPS/secondary-storage.html
deleted file mode 100644
index 3de485e..0000000
--- a/docs/tmp/en-US/epub/OEBPS/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="" /></head><body><div class="section" id="secondary-storage"><div class="titlepage"><div><div><h1 class="title" id="secondary-storage">13.3. Secondary Storage</h1></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></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/security-groups.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/security-groups.html b/docs/tmp/en-US/epub/OEBPS/security-groups.html
deleted file mode 100644
index 5dbe6c1..0000000
--- a/docs/tmp/en-US/epub/OEBPS/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="" /></head><body><div class="section" id="security-groups"><div class="titlepage"><div><div><h1 class="title" id="security-groups">15.7. Security Groups</h1></div></div></div><div class="section" id="about-security-groups"><div class="titlepage"><div><div><h2 class="title" id="about-security-groups">15.7.1. About Security Groups</h2></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 class="section" id="add-security-group"><div class="titlepage"><div><div><h2 class="title" id="add-security-group">15.7.2. Adding a Security Group</h2></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 class="section" id="enable-security-groups"><div class="titlepage"><div><div><h2 class="title" id="enable-security-groups">15.7.3. Enabling Security Groups</h2></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 class="section" id="add-ingress-egress-rules"><div class="titlepage"><div><div><h2 class="title" id="add-ingress-egress-rules">15.7.4. Adding Ingress and Egress Rules to a Security Group</h2></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></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/set-database-buffer-pool-size.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/set-database-buffer-pool-size.html b/docs/tmp/en-US/epub/OEBPS/set-database-buffer-pool-size.html
deleted file mode 100644
index 3f654ed..0000000
--- a/docs/tmp/en-US/epub/OEBPS/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="" /></head><body><div class="section" id="set-database-buffer-pool-size"><div class="titlepage"><div><div><h1 class="title" id="set-database-buffer-pool-size">21.3. Set Database Buffer Pool Size</h1></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></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/set-monitor-total-vm-limits-per-host.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/set-monitor-total-vm-limits-per-host.html b/docs/tmp/en-US/epub/OEBPS/set-monitor-total-vm-limits-per-host.html
deleted file mode 100644
index 2d8a593..0000000
--- a/docs/tmp/en-US/epub/OEBPS/set-monitor-total-vm-limits-per-host.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>21.4. Set and Monitor Total VM Limits per Host</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="" /></head><body><div class="section" id="set-monitor-total-vm-limits-per-host"><div class="titlepage"><div><div><h1 class="title" id="set-monitor-total-vm-limits-per-host">21.4. Set and Monitor Total VM Limits per Host</h1></div></div></div><div class="para">
- The CloudStack administrator should monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are automatically redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudStack global configuration settings to set this as the default limit. Monitor the VM activity in each cluster at all times. Keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) * (per-host-limit). Once a cluster reaches this number of
VMs, use the CloudStack UI to disable allocation of more VMs to the cluster.
- </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/set-up-network-for-users.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/set-up-network-for-users.html b/docs/tmp/en-US/epub/OEBPS/set-up-network-for-users.html
deleted file mode 100644
index 2cd0455..0000000
--- a/docs/tmp/en-US/epub/OEBPS/set-up-network-for-users.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>Chapter 9. Setting Up Networking for Users</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="" /></head><body><div class="chapter" id="set-up-network-for-users"><div class="titlepage"><div><div><h1 class="title">Chapter 9. Setting Up Networking for Users</h1></div></div></div><div class="section" id="networks-for-users-overview"><div class="titlepage"><div><div><h1 class="title" id="networks-for-users-overview">9.1. Overview of Setting Up Networking for Users</h1></div></div></div><div class="para">
- People using cloud infrastructure have a variety of needs and preferences when it comes to the networking services provided by the cloud. As a CloudStack administrator, you can do the following things to set up networking for your users:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Set up physical networks in zones
- </div></li><li class="listitem"><div class="para">
- Set up several different providers for the same service on a single physical network (for example, both Cisco and Juniper firewalls)
- </div></li><li class="listitem"><div class="para">
- Bundle different types of network services into network offerings, so users can choose the desired network services for any given virtual machine
- </div></li><li class="listitem"><div class="para">
- Add new network offerings as time goes on so end users can upgrade to a better class of service on their network
- </div></li><li class="listitem"><div class="para">
- Provide more ways for a network to be accessed by a user, such as through a project of which the user is a member
- </div></li></ul></div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/set-usage-limit.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/set-usage-limit.html b/docs/tmp/en-US/epub/OEBPS/set-usage-limit.html
deleted file mode 100644
index e3c9cb5..0000000
--- a/docs/tmp/en-US/epub/OEBPS/set-usage-limit.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>14.2. Setting Usage Limits</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="" /></head><body><div class="section" id="set-usage-limit"><div class="titlepage"><div><div><h1 class="title" id="set-usage-limit">14.2. Setting Usage Limits</h1></div></div></div><div class="para">
- CloudStack provides several administrator control points for capping resource usage by users. Some of these limits are global configuration parameters. Others are applied at the ROOT domain and may be overridden on a per-account basis.
- </div><div class="para">
- Aggregate limits may be set on a per-domain basis. For example, you may limit a domain and all subdomains to the creation of 100 VMs.
- </div><div class="para">
- This section covers the following topics:
- </div><div class="para">
- <a class="xref" href="globally-configured-limit.html">Section 14.3, “Globally Configured Limits”</a>Globally Configured Limits
- </div><div class="para">
- <a class="xref" href="default-account-resource-limit.html">Section 14.4, “Default Account Resource Limits”</a>Default Account Resource Limits
- </div><div class="para">
- <a class="xref" href="per-domain-limits.html">Section 14.5, “Per-Domain Limits”</a>Per Domain Limits
- </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/static-nat.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/static-nat.html b/docs/tmp/en-US/epub/OEBPS/static-nat.html
deleted file mode 100644
index fff8a55..0000000
--- a/docs/tmp/en-US/epub/OEBPS/static-nat.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>15.13. Static NAT</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="" /></head><body><div class="section" id="static-nat"><div class="titlepage"><div><div><h1 class="title" id="static-nat">15.13. Static NAT</h1></div></div></div><div class="para">
- A static NAT rule maps a public IP address to the private IP address of a VM in order to allow Internet traffic into the VM. The public IP address always remains the same, which is why it is called "static" NAT. This section tells how to enable or disable static NAT for a particular IP address.
- </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/stop-restart-management-server.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/stop-restart-management-server.html b/docs/tmp/en-US/epub/OEBPS/stop-restart-management-server.html
deleted file mode 100644
index 80fe280..0000000
--- a/docs/tmp/en-US/epub/OEBPS/stop-restart-management-server.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>18.5. Stopping and Restarting the Management Server</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="" /></head><body><div class="section" id="stop-restart-management-server"><div class="titlepage"><div><div><h1 class="title" id="stop-restart-management-server">18.5. Stopping and Restarting the Management Server</h1></div></div></div><div class="para">
- The root administrator will need to stop and restart the Management Server from time to time.
- </div><div class="para">
- For example, after changing a global configuration parameter, a restart is required. If you have multiple Management Server nodes, restart all of them to put the new parameter value into effect consistently throughout the cloud.
- </div><div class="para">
- To stop the Management Server, issue the following command at the operating system prompt on the Management Server node:
- </div><pre class="programlisting"># service cloud-management stop</pre><div class="para">
- To start the Management Server:
- </div><pre class="programlisting"># service cloud-management start</pre><div class="para">
- To stop the Management Server:
- </div><pre class="programlisting"># service cloud-management stop</pre></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/stopping-and-starting-vms.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/stopping-and-starting-vms.html b/docs/tmp/en-US/epub/OEBPS/stopping-and-starting-vms.html
deleted file mode 100644
index 1db4d64..0000000
--- a/docs/tmp/en-US/epub/OEBPS/stopping-and-starting-vms.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>10.6. Stopping and Starting VMs</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="" /></head><body><div class="section" id="stopping-and-starting-vms"><div class="titlepage"><div><div><h1 class="title" id="stopping-and-starting-vms">10.6. Stopping and Starting VMs</h1></div></div></div><div class="para">
- Any user can access their own virtual machines. The administrator can access all VMs running in the cloud.
- </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/storage.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/storage.html b/docs/tmp/en-US/epub/OEBPS/storage.html
deleted file mode 100644
index 2062b4a..0000000
--- a/docs/tmp/en-US/epub/OEBPS/storage.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>Chapter 13. Working With 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="" /></head><body><div class="chapter" id="storage"><div class="titlepage"><div><div><h1 class="title">Chapter 13. Working With Storage</h1></div></div></div><div class="section" id="storage-overview"><div class="titlepage"><div><div><h1 class="title" id="storage-overview">13.1. Storage Overview</h1></div></div></div><div class="para">
- CloudStack defines two types of storage: primary and secondary. Primary storage can be accessed by either iSCSI or NFS. Additionally, direct attached storage may be used for primary storage. Secondary storage is always accessed using NFS.
- </div><div class="para">
- There is no ephemeral storage in CloudStack. All volumes on all nodes are persistent.
- </div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/suspend-project.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/suspend-project.html b/docs/tmp/en-US/epub/OEBPS/suspend-project.html
deleted file mode 100644
index 3671c3e..0000000
--- a/docs/tmp/en-US/epub/OEBPS/suspend-project.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>6.6. Suspending or Deleting a Project</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="" /></head><body><div class="section" id="suspend-project"><div class="titlepage"><div><div><h1 class="title" id="suspend-project">6.6. Suspending or Deleting a Project</h1></div></div></div><div class="para">
- When a project is suspended, it retains the resources it owns, but they can no longer be used. No new resources or members can be added to a suspended project.
- </div><div class="para">
- When a project is deleted, its resources are destroyed, and member accounts are removed from the project. The project’s status is shown as Disabled pending final deletion.
- </div><div class="para">
- A project can be suspended or deleted by the project administrator, the domain administrator of the domain the project belongs to or of its parent domain, or the CloudStack root administrator.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI.
- </div></li><li class="listitem"><div class="para">
- In the left navigation, click Projects.
- </div></li><li class="listitem"><div class="para">
- In Select View, choose Projects.
- </div></li><li class="listitem"><div class="para">
- Click the name of the project.
- </div></li><li class="listitem"><div class="para">
- Click one of the buttons:
- </div><div class="para">
- To delete, use
- <span class="inlinemediaobject"><img src="./images/delete-button.png" alt="deletebutton.png: Removes a project" /></span>
- </div><div class="para">
- To suspend, use
- <span class="inlinemediaobject"><img src="./images/suspend-icon.png" alt="deletebutton.png: suspends a project" /></span>
- </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/sys-reliability-and-ha.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/sys-reliability-and-ha.html b/docs/tmp/en-US/epub/OEBPS/sys-reliability-and-ha.html
deleted file mode 100644
index 2929d70..0000000
--- a/docs/tmp/en-US/epub/OEBPS/sys-reliability-and-ha.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 17. System Reliability and High Availability</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="" /></head><body><div class="chapter" id="sys-reliability-and-ha"><div class="titlepage"><div><div><h1 class="title">Chapter 17. System Reliability and High Availability</h1></div></div></div><div class="section" id="ha-management-server"><div class="titlepage"><div><div><h1 class="title" id="ha-management-server">17.1. HA for Management Server</h1></div></div></div><div class="para">
- The CloudStack Management Server should be deployed in a multi-node configuration such that it is not susceptible to individual server failures. The Management Server itself (as distinct from the MySQL database) is stateless and may be placed behind a load balancer.
- </div><div class="para">
- Normal operation of Hosts is not impacted by an outage of all Management Serves. All guest VMs will continue to work.
- </div><div class="para">
- When the Management Server is down, no new VMs can be created, and the end user and admin UI, API, dynamic load distribution, and HA will cease to work.
- </div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/system-service-offerings.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/system-service-offerings.html b/docs/tmp/en-US/epub/OEBPS/system-service-offerings.html
deleted file mode 100644
index 61b830a..0000000
--- a/docs/tmp/en-US/epub/OEBPS/system-service-offerings.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>8.2. System Service Offerings</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="" /></head><body><div class="section" id="system-service-offerings"><div class="titlepage"><div><div><h1 class="title" id="system-service-offerings">8.2. System Service Offerings</h1></div></div></div><div class="para">
- System service offerings provide a choice of CPU speed, number of CPUs, tags, and RAM size, just as other service offerings do. But rather than being used for virtual machine instances and exposed to users, system service offerings are used to change the default properties of virtual routers, console proxies, and other system VMs. System service offerings are visible only to the CloudStack root administrator. CloudStack provides default system service offerings. The CloudStack root administrator can create additional custom system service offerings.
- </div><div class="para">
- When CloudStack creates a virtual router for a guest network, it uses default settings which are defined in the system service offering associated with the network offering. You can upgrade the capabilities of the virtual router by applying a new network offering that contains a different system service offering. All virtual routers in that network will begin using the settings from the new service offering.
- </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/epub/OEBPS/time-zones.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/time-zones.html b/docs/tmp/en-US/epub/OEBPS/time-zones.html
deleted file mode 100644
index a862914..0000000
--- a/docs/tmp/en-US/epub/OEBPS/time-zones.html
+++ /dev/null
@@ -1,244 +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>Appendix A. Time Zones</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="" /></head><body><div class="appendix" id="time-zones"><div class="titlepage"><div><div><h1 class="title">Time Zones</h1></div></div></div><div class="para">
- The following time zone identifiers are accepted by CloudStack. There are several places that have a time zone as a required or optional parameter. These include scheduling recurring snapshots, creating a user, and specifying the usage time zone in the Configuration table.
- </div><div class="informaltable"><table border="1"><colgroup><col style="text-align: left" class="c1" width="33%" /><col style="text-align: left" class="c2" width="33%" /><col style="text-align: left" class="c3" width="33%" /></colgroup><tbody><tr><td style="text-align: left">
- <div class="para">
- Etc/GMT+12
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Etc/GMT+11
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Pacific/Samoa
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Pacific/Honolulu
- </div>
- </td><td style="text-align: left">
- <div class="para">
- US/Alaska
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/Los_Angeles
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Mexico/BajaNorte
- </div>
- </td><td style="text-align: left">
- <div class="para">
- US/Arizona
- </div>
- </td><td style="text-align: left">
- <div class="para">
- US/Mountain
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- America/Chihuahua
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/Chicago
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/Costa_Rica
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- America/Mexico_City
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Canada/Saskatchewan
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/Bogota
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- America/New_York
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/Caracas
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/Asuncion
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- America/Cuiaba
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/Halifax
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/La_Paz
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- America/Santiago
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/St_Johns
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/Araguaina
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- America/Argentina/Buenos_Aires
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/Cayenne
- </div>
- </td><td style="text-align: left">
- <div class="para">
- America/Godthab
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- America/Montevideo
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Etc/GMT+2
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Atlantic/Azores
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Atlantic/Cape_Verde
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Africa/Casablanca
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Etc/UTC
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Atlantic/Reykjavik
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Europe/London
- </div>
- </td><td style="text-align: left">
- <div class="para">
- CET
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Europe/Bucharest
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Africa/Johannesburg
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Asia/Beirut
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Africa/Cairo
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Asia/Jerusalem
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Europe/Minsk
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Europe/Moscow
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Africa/Nairobi
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Asia/Karachi
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Asia/Kolkata
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Asia/Bangkok
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Asia/Shanghai
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Asia/Kuala_Lumpur
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Australia/Perth
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Asia/Taipei
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Asia/Tokyo
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Asia/Seoul
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Australia/Adelaide
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Australia/Darwin
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Australia/Brisbane
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Australia/Canberra
- </div>
- </td></tr><tr><td style="text-align: left">
- <div class="para">
- Pacific/Guam
- </div>
- </td><td style="text-align: left">
- <div class="para">
- Pacific/Auckland
- </div>
- </td><td style="text-align: left">
- <div class="para">
- </div>
- </td></tr></tbody></table></div></div></body></html>