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
[70/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/about-clusters.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/about-clusters.html b/docs/tmp/en-US/html/about-clusters.html
deleted file mode 100644
index d5f58cc..0000000
--- a/docs/tmp/en-US/html/about-clusters.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>2.3. About Clusters</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="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-pods.html" title="2.2. About Pods" /><link rel="next" href="about-hosts.html" title="2.4. About 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="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="about-pods.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="about-hosts.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-clusters" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-clusters">2.3. About Clusters</h2></div></div></div><div class="para">
- A cluster provides a way to group hosts. To be precise, a cluster is a XenServer server pool, a set of KVM servers, , or a VMware cluster preconfigured in vCenter. The hosts in a cluster all have identical hardware, run the same hypervisor, are on the same subnet, and access the same shared primary storage. Virtual machine instances (VMs) can be live-migrated from one host to another within the same cluster, without interrupting service to the user.
- </div><div class="para">
- A cluster is the third-largest organizational unit within a CloudStack deployment. Clusters are contained within pods, and pods are contained within zones. Size of the cluster is limited by the underlying hypervisor, although the CloudStack recommends less in most cases; see Best Practices.
- </div><div class="para">
- A cluster consists of one or more hosts and one or more primary storage servers.
- </div><div class="mediaobject"><img src="./images/cluster-overview.png" alt="cluster-overview.png: Structure of a simple cluster" /></div><div class="para">
- CloudStack allows multiple clusters in a cloud deployment.
- </div><div class="para">
- Even when local storage is used exclusively, clusters are still required organizationally, even if there is just one host per cluster.
- </div><div class="para">
- When VMware is used, every VMware cluster is managed by a vCenter server. Administrator must register the vCenter server with CloudStack. There may be multiple vCenter servers per zone. Each vCenter server may manage multiple VMware clusters.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-pods.html"><strong>Prev</strong>2.2. About Pods</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="about-hosts.html"><strong>Next</strong>2.4. About Hosts</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/about-hosts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/about-hosts.html b/docs/tmp/en-US/html/about-hosts.html
deleted file mode 100644
index f0cb0df..0000000
--- a/docs/tmp/en-US/html/about-hosts.html
+++ /dev/null
@@ -1,31 +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.4. About 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="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-clusters.html" title="2.3. About Clusters" /><link rel="next" href="about-primary-storage.html" title="2.5. About Primary 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.cloudsta
ck.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-clusters.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="about-primary-storage.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-hosts" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-hosts">2.4. About Hosts</h2></div></div></div><div class="para">
- A host is a single computer. Hosts provide the computing resources that run the guest virtual machines. Each host has hypervisor software installed on it to manage the guest VMs. For example, a Linux KVM-enabled server, a Citrix XenServer server, and an ESXi server are hosts.
- </div><div class="para">
- The host is the smallest organizational unit within a CloudStack deployment. Hosts are contained within clusters, clusters are contained within pods, and pods are contained within zones.
- </div><div class="para">
- Hosts in a CloudStack deployment:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Provide the CPU, memory, storage, and networking resources needed to host the virtual machines
- </div></li><li class="listitem"><div class="para">
- Interconnect using a high bandwidth TCP/IP network and connect to the Internet
- </div></li><li class="listitem"><div class="para">
- May reside in multiple data centers across different geographic locations
- </div></li><li class="listitem"><div class="para">
- May have different capacities (different CPU speeds, different amounts of RAM, etc.), although the hosts within a cluster must all be homogeneous
- </div></li></ul></div><div class="para">
- Additional hosts can be added at any time to provide more capacity for guest VMs.
- </div><div class="para">
- CloudStack automatically detects the amount of CPU and memory resources provided by the Hosts.
- </div><div class="para">
- Hosts are not visible to the end user. An end user cannot determine which host their guest has been assigned to.
- </div><div class="para">
- For a host to function in CloudStack, you must do the following:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Install hypervisor software on the host
- </div></li><li class="listitem"><div class="para">
- Assign an IP address to the host
- </div></li><li class="listitem"><div class="para">
- Ensure the host is connected to the CloudStack Management Server
- </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-clusters.html"><strong>Prev</strong>2.3. About Clusters</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="about-primary-storage.html"><strong>Next</strong>2.5. About Primary Storage</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/about-physical-networks.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/about-physical-networks.html b/docs/tmp/en-US/html/about-physical-networks.html
deleted file mode 100644
index dbc7cbb..0000000
--- a/docs/tmp/en-US/html/about-physical-networks.html
+++ /dev/null
@@ -1,93 +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.7. About Physical Networks</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="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-secondary-storage.html" title="2.6. About Secondary Storage" /><link rel="next" href="accounts.html" title="Chapter 3. Accounts" /></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://do
cs.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="about-secondary-storage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="accounts.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-physical-networks" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-physical-networks">2.7. About Physical Networks</h2></div></div></div><div class="para">
- Part of adding a zone is setting up the physical network. One or (in an advanced zone) more physical networks can be associated with each zone. The network corresponds to a NIC on the hypervisor host. Each physical network can carry one or more types of network traffic. The choices of traffic type for each network vary depending on whether you are creating a zone with basic networking or advanced networking.
- </div><div class="para">
- A physical network is the actual network hardware and wiring in a zone. A zone can have multiple physical networks. An administrator can:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Add/Remove/Update physical networks in a zone
- </div></li><li class="listitem"><div class="para">
- Configure VLANs on the physical network
- </div></li><li class="listitem"><div class="para">
- Configure a name so the network can be recognized by hypervisors
- </div></li><li class="listitem"><div class="para">
- Configure the service providers (firewalls, load balancers, etc.) available on a physical network
- </div></li><li class="listitem"><div class="para">
- Configure the IP addresses trunked to a physical network
- </div></li><li class="listitem"><div class="para">
- Specify what type of traffic is carried on the physical network, as well as other properties like network speed
- </div></li></ul></div><div xml:lang="en-US" class="section" id="physical-network-configuration-settings" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="physical-network-configuration-settings">2.7.1. Configurable Characteristics of Physical Networks</h3></div></div></div><div class="para">
- CloudStack provides configuration settings you can use to set up a physical network in a zone, including:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- What type of network traffic it carries (guest, public, management, storage)
- </div></li><li class="listitem"><div class="para">
- VLANs
- </div></li><li class="listitem"><div class="para">
- Unique name that the hypervisor can use to find that particular network
- </div></li><li class="listitem"><div class="para">
- Enabled or disabled. When a network is first set up, it is disabled – not in use yet. The administrator sets the physical network to enabled, and it begins to be used. The administrator can later disable the network again, which prevents any new virtual networks from being created on that physical network; the existing network traffic continues even though the state is disabled.
- </div></li><li class="listitem"><div class="para">
- Speed
- </div></li><li class="listitem"><div class="para">
- Tags, so network offerings can be matched to physical networks
- </div></li><li class="listitem"><div class="para">
- Isolation method
- </div></li></ul></div></div><div xml:lang="en-US" class="section" id="basic-zone-network-traffic-types" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="basic-zone-network-traffic-types">2.7.2. Basic Zone Network Traffic Types</h3></div></div></div><div class="para">
- When basic networking is used, there can be only one physical network in the zone. That physical network carries the following traffic types:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Guest. When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. Each pod in a basic zone is a broadcast domain, and therefore each pod has a different IP range for the guest network. The administrator must configure the IP range for each pod.
- </div></li><li class="listitem"><div class="para">
- Management. When CloudStack’s internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- We strongly recommend the use of separate NICs for management traffic and guest traffic.
- </div></div></div></li><li class="listitem"><div class="para">
- Public. Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in Acquiring a New IP Address.
- </div></li><li class="listitem"><div class="para">
- Storage. Traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudStack uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network.
- </div></li></ul></div><div class="para">
- In a basic network, configuring the physical network is fairly straightforward. In most cases, you only need to configure one guest network to carry traffic that is generated by guest VMs. If you use a NetScaler load balancer and enable its elastic IP and elastic load balancing (EIP and ELB) features, you must also configure a network to carry public traffic. CloudStack takes care of presenting the necessary network configuration steps to you in the UI when you add a new zone.
- </div></div><div xml:lang="en-US" class="section" id="basic-zone-guest-ip-addresses" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="basic-zone-guest-ip-addresses">2.7.3. Basic Zone Guest IP Addresses</h3></div></div></div><div class="para">
- When basic networking is used, CloudPlatform will assign IP addresses in the CIDR of the pod to the guests in that pod. The administrator must add a Direct IP range on the pod for this purpose. These IPs are in the same VLAN as the hosts.
- </div></div><div xml:lang="en-US" class="section" id="advanced-zone-network-traffic-types" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="advanced-zone-network-traffic-types">2.7.4. Advanced Zone Network Traffic Types</h3></div></div></div><div class="para">
- When advanced networking is used, there can be multiple physical networks in the zone. Each physical network can carry one or more traffic types, and you need to let CloudStack know which type of network traffic you want each network to carry. The traffic types in an advanced zone are:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Guest. When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. This network can be isolated or shared. In an isolated guest network, the administrator needs to reserve VLAN ranges to provide isolation for each CloudStack account’s network (potentially a large number of VLANs). In a shared guest network, all guest VMs share a single network.
- </div></li><li class="listitem"><div class="para">
- Management. When CloudStack’s internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use.
- </div></li><li class="listitem"><div class="para">
- Public. Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in “Acquiring a New IP Address” in the Administration Guide.
- </div></li><li class="listitem"><div class="para">
- Storage. Traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudStack uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network.
- </div></li></ul></div><div class="para">
- These traffic types can each be on a separate physical network, or they can be combined with certain restrictions. When you use the Add Zone wizard in the UI to create a new zone, you are guided into making only valid choices.
- </div></div><div xml:lang="en-US" class="section" id="advanced-zone-guest-ip-addresses" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="advanced-zone-guest-ip-addresses">2.7.5. Advanced Zone Guest IP Addresses</h3></div></div></div><div class="para">
- When advanced networking is used, the administrator can create additional networks for use by the guests. These networks can span the zone and be available to all accounts, or they can be scoped to a single account, in which case only the named account may create guests that attach to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The administrator may provision thousands of these networks if desired.
- </div></div><div xml:lang="en-US" class="section" id="advanced-zone-public-ip-addresses" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="advanced-zone-public-ip-addresses">2.7.6. Advanced Zone Public IP Addresses</h3></div></div></div><div class="para">
- When advanced networking is used, the administrator can create additional networks for use by the guests. These networks can span the zone and be available to all accounts, or they can be scoped to a single account, in which case only the named account may create guests that attach to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The administrator may provision thousands of these networks if desired.
- </div></div><div xml:lang="en-US" class="section" id="system-reserved-ip-addresses" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="system-reserved-ip-addresses">2.7.7. System Reserved IP Addresses</h3></div></div></div><div class="para">
- In each zone, you need to configure a range of reserved IP addresses for the management network. This network carries communication between the CloudStack Management Server and various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP.
- </div><div class="para">
- The reserved IP addresses must be unique across the cloud. You cannot, for example, have a host in one zone which has the same private IP address as a host in another zone.
- </div><div class="para">
- The hosts in a pod are assigned private IP addresses. These are typically RFC1918 addresses. The Console Proxy and Secondary Storage system VMs are also allocated private IP addresses in the CIDR of the pod that they are created in.
- </div><div class="para">
- Make sure computing servers and Management Servers use IP addresses outside of the System Reserved IP range. For example, suppose the System Reserved IP range starts at 192.168.154.2 and ends at 192.168.154.7. CloudStack can use .2 to .7 for System VMs. This leaves the rest of the pod CIDR, from .8 to .254, for the Management Server and hypervisor hosts.
- </div><div class="para">
- <span class="bold bold"><strong>In all zones:</strong></span>
- </div><div class="para">
- Provide private IPs for the system in each pod and provision them in CloudStack.
- </div><div class="para">
- For KVM and XenServer, the recommended number of private IPs per pod is one per host. If you expect a pod to grow, add enough private IPs now to accommodate the growth.
- </div><div class="para">
- <span class="bold bold"><strong>In a zone that uses advanced networking:</strong></span>
- </div><div class="para">
- For zones with advanced networking, we recommend provisioning enough private IPs for your total number of customers, plus enough for the required CloudStack System VMs. Typically, about 10 additional IPs are required for the System VMs. For more information about System VMs, see Working with System Virtual Machines in the Administrator's Guide.
- </div><div class="para">
- When advanced networking is being used, the number of private IP addresses available in each pod varies depending on which hypervisor is running on the nodes in that pod. Citrix XenServer and KVM use link-local addresses, which in theory provide more than 65,000 private IP addresses within the address block. As the pod grows over time, this should be more than enough for any reasonable number of hosts as well as IP addresses for guest virtual routers. VMWare ESXi, by contrast uses any administrator-specified subnetting scheme, and the typical administrator provides only 255 IPs per pod. Since these are shared by physical machines, the guest virtual router, and other entities, it is possible to run out of private IPs when scaling up a pod whose nodes are running ESXi.
- </div><div class="para">
- To ensure adequate headroom to scale private IP space in an ESXi pod that uses advanced networking, use one or both of the following techniques:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Specify a larger CIDR block for the subnet. A subnet mask with a /20 suffix will provide more than 4,000 IP addresses.
- </div></li><li class="listitem"><div class="para">
- Create multiple pods, each with its own subnet. For example, if you create 10 pods and each pod has 255 IPs, this will provide 2,550 IP addresses.
- </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-secondary-storage.html"><strong>Prev</strong>2.6. About Secondary 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="accounts.html"><strong>Next</strong>Chapter 3. Accounts</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/about-pods.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/about-pods.html b/docs/tmp/en-US/html/about-pods.html
deleted file mode 100644
index 57142fa..0000000
--- a/docs/tmp/en-US/html/about-pods.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.2. About Pods</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="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-zones.html" title="2.1. About Zones" /><link rel="next" href="about-clusters.html" title="2.3. About Clusters" /></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="Com
mon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="about-zones.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="about-clusters.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-pods" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-pods">2.2. About Pods</h2></div></div></div><div class="para">
- A pod often represents a single rack. Hosts in the same pod are in the same subnet.
- </div><div class="para">
- A pod is the second-largest organizational unit within a CloudStack deployment. Pods are contained within zones. Each zone can contain one or more pods.
- </div><div class="para">
- Pods are not visible to the end user.
- </div><div class="para">
- A pod consists of one or more clusters of hosts and one or more primary storage servers.
- </div><div class="mediaobject"><img src="./images/pod-overview.png" alt="pod-overview.png: Nested structure of a simple pod" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-zones.html"><strong>Prev</strong>2.1. About Zones</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="about-clusters.html"><strong>Next</strong>2.3. About Clusters</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/about-primary-storage.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/about-primary-storage.html b/docs/tmp/en-US/html/about-primary-storage.html
deleted file mode 100644
index 4289e73..0000000
--- a/docs/tmp/en-US/html/about-primary-storage.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>2.5. About Primary 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="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-hosts.html" title="2.4. About Hosts" /><link rel="next" href="about-secondary-storage.html" title="2.6. About 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="about-hosts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="about-secondary-storage.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-primary-storage" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-primary-storage">2.5. About Primary Storage</h2></div></div></div><div class="para">
- Primary storage is associated with a cluster, and it stores the disk volumes for all the VMs running on hosts in that cluster. You can add multiple primary storage servers to a cluster. At least one is required. It is typically located close to the hosts for increased performance.
- </div><div class="para">
- CloudStack is designed to work with all standards-compliant iSCSI and NFS servers that are supported by the underlying hypervisor, including, for example:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Dell EqualLogic™ for iSCSI
- </div></li><li class="listitem"><div class="para">
- Network Appliances filers for NFS and iSCSI
- </div></li><li class="listitem"><div class="para">
- Scale Computing for NFS
- </div></li></ul></div><div class="para">
- If you intend to use only local disk for your installation, you can skip to Add Secondary Storage.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-hosts.html"><strong>Prev</strong>2.4. About 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="about-secondary-storage.html"><strong>Next</strong>2.6. About Secondary Storage</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/about-secondary-storage.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/about-secondary-storage.html b/docs/tmp/en-US/html/about-secondary-storage.html
deleted file mode 100644
index 5e34db8..0000000
--- a/docs/tmp/en-US/html/about-secondary-storage.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>2.6. About 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="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-primary-storage.html" title="2.5. About Primary Storage" /><link rel="next" href="about-physical-networks.html" title="2.7. About Physical Networks" /></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="rig
ht" 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="about-primary-storage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="about-physical-networks.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-secondary-storage" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-secondary-storage">2.6. About Secondary Storage</h2></div></div></div><div class="para">
- Secondary storage is associated with a zone, and it stores the following:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Templates — OS images that can be used to boot VMs and can include additional configuration information, such as installed applications
- </div></li><li class="listitem"><div class="para">
- ISO images — disc images containing data or bootable media for operating systems
- </div></li><li class="listitem"><div class="para">
- Disk volume snapshots — saved copies of VM data which can be used for data recovery or to create new templates
- </div></li></ul></div><div class="para">
- The items in zone-based NFS secondary storage are available to all hosts in the zone. CloudStack manages the allocation of guest virtual disks to particular primary storage devices.
- </div><div class="para">
- To make items in secondary storage available to all hosts throughout the cloud, you can add OpenStack Object Storage (Swift, <a href="http://swift.openstack.org">swift.openstack.org</a>) in addition to the zone-based NFS secondary storage. When using Swift, you configure Swift storage for the entire CloudStack, then set up NFS secondary storage for each zone as usual. The NFS storage in each zone acts as a staging area through which all templates and other secondary storage data pass before being forwarded to Swift. The Swift storage acts as a cloud-wide resource, making templates and other data available to any zone in the cloud. There is no hierarchy in the Swift storage, just one Swift container per storage object. Any secondary storage in the whole cloud can pull a container from Swift at need. It is not necessary to copy templates and snapshots from one zone to another, as would be required when using zone NFS alone. Everything is available everywhere.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-primary-storage.html"><strong>Prev</strong>2.5. About 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="about-physical-networks.html"><strong>Next</strong>2.7. About Physical Networks</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/about-virtual-networks.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/about-virtual-networks.html b/docs/tmp/en-US/html/about-virtual-networks.html
deleted file mode 100644
index efb0289..0000000
--- a/docs/tmp/en-US/html/about-virtual-networks.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>9.2. About Virtual Networks</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="set-up-network-for-users.html" title="Chapter 9. Setting Up Networking for Users" /><link rel="prev" href="networks-for-users-overview.html" title="9.1. Overview of Setting Up Networking for Users" /><link rel="next" href="network-service-providers.html" title="9.3. Network Service Providers" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Produ
ct 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="networks-for-users-overview.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="network-service-providers.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-virtual-networks" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-virtual-networks">9.2. About Virtual Networks</h2></div></div></div><div class="para">
- A virtual network is a logical construct that enables multi-tenancy on a single physical network. In CloudStack a virtual network can be shared or isolated.
- </div><div xml:lang="en-US" class="section" id="isolated-networks" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="isolated-networks">9.2.1. Isolated Networks</h3></div></div></div><div class="para">
- An isolated network can be accessed only by virtual machines of a single account. Isolated networks have the following properties.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Resources such as VLAN are allocated and garbage collected dynamically
- </div></li><li class="listitem"><div class="para">
- There is one network offering for the entire network
- </div></li><li class="listitem"><div class="para">
- The network offering can be upgraded or downgraded but it is for the entire network
- </div></li></ul></div></div><div xml:lang="en-US" class="section" id="shared-networks" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="shared-networks">9.2.2. Shared Networks</h3></div></div></div><div class="para">
- A shared network can be accessed by virtual machines that belong to many different accounts. Network Isolation on shared networks is accomplished using techniques such as security groups (supported only in basic zones in CloudStack 3.0.3).
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Shared Networks are created by the administrator
- </div></li><li class="listitem"><div class="para">
- Shared Networks can be designated to a certain domain
- </div></li><li class="listitem"><div class="para">
- Shared Network resources such as VLAN and physical network that it maps to are designated by the administrator
- </div></li><li class="listitem"><div class="para">
- Shared Networks are isolated by security groups
- </div></li><li class="listitem"><div class="para">
- Public Network is a shared network that is not shown to the end users
- </div></li></ul></div></div><div xml:lang="en-US" class="section" id="runtime-allocation-virtual-network-resources" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="runtime-allocation-virtual-network-resources">9.2.3. Runtime Allocation of Virtual Network Resources</h3></div></div></div><div class="para">
- When you define a new virtual network, all your settings for that network are stored in CloudStack. The actual network resources are activated only when the first virtual machine starts in the network. When all virtual machines have left the virtual network, the network resources are garbage collected so they can be allocated again. This helps to conserve network resources..
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="networks-for-users-overview.html"><strong>Prev</strong>9.1. Overview of Setting Up Networking for Users</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="network-service-providers.html"><strong>Next</strong>9.3. Network Service Providers</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/about-working-with-vms.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/about-working-with-vms.html b/docs/tmp/en-US/html/about-working-with-vms.html
deleted file mode 100644
index c068ac6..0000000
--- a/docs/tmp/en-US/html/about-working-with-vms.html
+++ /dev/null
@@ -1,21 +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.1. About Working with Virtual Machines</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="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /><link rel="prev" href="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /><link rel="next" href="best-practices-vm.html" title="10.2. Best Practices for Virtual Machines" /></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-machines.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="best-practices-vm.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-working-with-vms" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-working-with-vms">10.1. About Working with Virtual Machines</h2></div></div></div><div class="para">
- CloudStack provides administrators with complete control over the lifecycle of all guest VMs executing in the cloud. CloudStack provides several guest management operations for end users and administrators. VMs may be stopped, started, rebooted, and destroyed.
- </div><div class="para">
- Guest VMs have a name and group. VM names and groups are opaque to CloudStack and are available for end users to organize their VMs. Each VM can have three names for use in different contexts. Only two of these names can be controlled by the user:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Instance name – a unique, immutable ID that is generated by CloudStack and can not be modified by the user. This name conforms to the requirements in IETF RFC 1123.
- </div></li><li class="listitem"><div class="para">
- Display name – the name displayed in the CloudStack web UI. Can be set by the user. Defaults to instance name.
- </div></li><li class="listitem"><div class="para">
- Name – host name that the DHCP server assigns to the VM. Can be set by the user. Defaults to instance name
- </div></li></ul></div><div class="para">
- Guest VMs can be configured to be Highly Available (HA). An HA-enabled VM is monitored by the system. If the system detects that the VM is down, it will attempt to restart the VM, possibly on a different host. For more information, see HA-Enabled Virtual Machines on
- </div><div class="para">
- Each new VM is allocated one public IP address. When the VM is started, CloudStack automatically creates a static NAT between this public IP address and the private IP address of the VM.
- </div><div class="para">
- If elastic IP is in use (with the NetScaler load balancer), the IP address initially allocated to the new VM is not marked as elastic. The user must replace the automatically configured IP with a specifically acquired elastic IP, and set up the static NAT mapping between this new IP and the guest VM’s private IP. The VM’s original IP address is then released and returned to the pool of available public IPs.
- </div><div class="para">
- CloudStack cannot distinguish a guest VM that was shut down by the user (such as with the “shutdown” command in Linux) from a VM that shut down unexpectedly. If an HA-enabled VM is shut down from inside the VM, CloudStack will restart it. To shut down an HA-enabled VM, you must go through the CloudStack UI or API.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="virtual-machines.html"><strong>Prev</strong>Chapter 10. Working With Virtual Machines</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-vm.html"><strong>Next</strong>10.2. Best Practices for Virtual Machines</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/about-zones.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/about-zones.html b/docs/tmp/en-US/html/about-zones.html
deleted file mode 100644
index 0b1570e..0000000
--- a/docs/tmp/en-US/html/about-zones.html
+++ /dev/null
@@ -1,31 +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. About 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="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="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="next" href="about-pods.html" title="2.2. About Pods" /></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="cloud-infrastructure-concepts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="about-pods.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-zones" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-zones">2.1. About Zones</h2></div></div></div><div class="para">
- A zone is the largest organizational unit within a CloudStack deployment. A zone typically corresponds to a single datacenter, although it is permissible to have multiple zones in a datacenter. The benefit of organizing infrastructure into zones is to provide physical isolation and redundancy. For example, each zone can have its own power supply and network uplink, and the zones can be widely separated geographically (though this is not required).
- </div><div class="para">
- A zone consists of:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- One or more pods. Each pod contains one or more clusters of hosts and one or more primary storage servers.
- </div></li><li class="listitem"><div class="para">
- Secondary storage, which is shared by all the pods in the zone.
- </div></li></ul></div><div class="mediaobject"><img src="./images/zone-overview.png" width="444" alt="zone-overview.png: Nested structure of a simple zone" /></div><div class="para">
- Zones are visible to the end user. When a user starts a guest VM, the user must select a zone for their guest. Users might also be required to copy their private templates to additional zones to enable creation of guest VMs using their templates in those zones.
- </div><div class="para">
- Zones can be public or private. Public zones are visible to all users. This means that any user may create a guest in that zone. Private zones are reserved for a specific domain. Only users in that domain or its subdomains may create guests in that zone.
- </div><div class="para">
- Hosts in the same zone are directly accessible to each other without having to go through a firewall. Hosts in different zones can access each other through statically configured VPN tunnels.
- </div><div class="para">
- For each zone, the administrator must decide the following.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- How many pods to place in a zone.
- </div></li><li class="listitem"><div class="para">
- How many clusters to place in each pod.
- </div></li><li class="listitem"><div class="para">
- How many hosts to place in each cluster.
- </div></li><li class="listitem"><div class="para">
- How many primary storage servers to place in each cluster and total capacity for the storage servers.
- </div></li><li class="listitem"><div class="para">
- How much secondary storage to deploy in a zone.
- </div></li></ul></div><div class="para">
- When you add a new zone, you will be prompted to configure the zone’s physical network and add the first pod, cluster, host, primary storage, and secondary storage.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="cloud-infrastructure-concepts.html"><strong>Prev</strong>Chapter 2. Cloud Infrastructure Concepts</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="about-pods.html"><strong>Next</strong>2.2. About Pods</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/accept-membership-invite.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/accept-membership-invite.html b/docs/tmp/en-US/html/accept-membership-invite.html
deleted file mode 100644
index 4e3cb52..0000000
--- a/docs/tmp/en-US/html/accept-membership-invite.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>6.5. Accepting a Membership Invitation</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="projects.html" title="Chapter 6. Using Projects to Organize Users and Resources" /><link rel="prev" href="add-members-to-projects.html" title="6.4. Adding Members to a Project" /><link rel="next" href="suspend-project.html" title="6.6. Suspending or Deleting a Project" /></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="add-members-to-projects.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="suspend-project.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="accept-membership-invite" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="accept-membership-invite">6.5. Accepting a Membership Invitation</h2></div></div></div><div class="para">
- If you have received an invitation to join a CloudStack project, and you want to accept the invitation, follow these steps:
- </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 Invitations.
- </div></li><li class="listitem"><div class="para">
- If you see the invitation listed onscreen, click the Accept button.
- </div><div class="para">
- Invitations listed on screen were sent to you using your CloudStack account name.
- </div></li><li class="listitem"><div class="para">
- If you received an email invitation, click the Enter Token button, and provide the project ID and unique ID code (token) from the email.
- </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="add-members-to-projects.html"><strong>Prev</strong>6.4. Adding Members to a Project</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="suspend-project.html"><strong>Next</strong>6.6. Suspending or Deleting a Project</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/accessing-vms.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/accessing-vms.html b/docs/tmp/en-US/html/accessing-vms.html
deleted file mode 100644
index db5390d..0000000
--- a/docs/tmp/en-US/html/accessing-vms.html
+++ /dev/null
@@ -1,21 +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.5. Accessing 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="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="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /><link rel="prev" href="creating-vms.html" title="10.4. Creating VMs" /><link rel="next" href="stopping-and-starting-vms.html" title="10.6. Stopping and Starting VMs" /></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="creating-vms.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="stopping-and-starting-vms.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="accessing-vms" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="accessing-vms">10.5. Accessing VMs</h2></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 class="para">
- To access a VM through the CloudStack UI:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to the CloudStack UI as a user or admin.
- </div></li><li class="listitem"><div class="para">
- Click Instances, then click the name of a running VM.
- </div></li><li class="listitem"><div class="para">
- Click the View Console button <img src="images/icon.png" />.
- </div></li></ol></div><div class="para">
- To access a VM directly over the network:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- The VM must have some port open to incoming traffic. For example, in a basic zone, a new VM might be assigned to a security group which allows incoming traffic. This depends on what security group you picked when creating the VM. In other cases, you can open a port by setting up a port forwarding policy. See IP Forwarding and Firewalling.
- </div></li><li class="listitem"><div class="para">
- If a port is open but you can not access the VM using ssh, it’s possible that ssh is not already enabled on the VM. This will depend on whether ssh is enabled in the template you picked when creating the VM. Access the VM through the CloudStack UI and enable ssh on the machine using the commands for the VM’s operating system.
- </div></li><li class="listitem"><div class="para">
- If the network has an external firewall device, you will need to create a firewall rule to allow access. See IP Forwarding and Firewalling.
- </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="creating-vms.html"><strong>Prev</strong>10.4. Creating VMs</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="stopping-and-starting-vms.html"><strong>Next</strong>10.6. Stopping and Starting VMs</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/accounts-users-domains.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/accounts-users-domains.html b/docs/tmp/en-US/html/accounts-users-domains.html
deleted file mode 100644
index 19b5e83..0000000
--- a/docs/tmp/en-US/html/accounts-users-domains.html
+++ /dev/null
@@ -1,21 +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. Accounts, Users, and Domains</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="accounts.html" title="Chapter 3. Accounts" /><link rel="prev" href="accounts.html" title="Chapter 3. Accounts" /><link rel="next" href="LDAPserver-for-user-authentication.html" title="3.2. Using an LDAP Server for User Authentication" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cl
oudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="accounts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="LDAPserver-for-user-authentication.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="accounts-users-domains" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="accounts-users-domains">3.1. Accounts, Users, and Domains</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idp24194632">Accounts</h5>
- An account typically represents a customer of the service provider or a department in a large organization. Multiple users can exist in an account.
- </div><div class="formalpara"><h5 class="formalpara" id="idp12742856">Domains</h5>
- Accounts are grouped by domains. Domains usually contain multiple accounts that have some logical relationship to each other and a set of delegated administrators with some authority over the domain and its subdomains. For example, a service provider with several resellers could create a domain for each reseller.
- </div><div class="para">
- For each account created, the Cloud installation creates three different types of user accounts: root administrator, domain administrator, and user.
- </div><div class="formalpara"><h5 class="formalpara" id="idp33273016">Users</h5>
- Users are like aliases in the account. Users in the same account are not isolated from each other, but they are isolated from users in other accounts. Most installations need not surface the notion of users; they just have one user per account. The same user cannot belong to multiple accounts.
- </div><div class="para">
- Username is unique in a domain across accounts in that domain. The same username can exist in other domains, including sub-domains. Domain name can repeat only if the full pathname from root is unique. For example, you can create root/d1, as well as root/foo/d1, and root/sales/d1.
- </div><div class="para">
- Administrators are accounts with special privileges in the system. There may be multiple administrators in the system. Administrators can create or delete other administrators, and change the password for any user in the system.
- </div><div class="formalpara"><h5 class="formalpara" id="idp11323152">Domain Administrators</h5>
- Domain administrators can perform administrative operations for users who belong to that domain. Domain administrators do not have visibility into physical servers or other domains.
- </div><div class="formalpara"><h5 class="formalpara" id="idp31236600">Root Administrator</h5>
- Root administrators have complete access to the system, including managing templates, service offerings, customer care administrators, and domains
- </div><div class="para">
- The resources belong to the account, not individual users in that account. For example, billing, resource limits, and so on are maintained by the account, not the users. A user can operate on any resource in the account provided the user has privileges for that operation. The privileges are determined by the role.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="accounts.html"><strong>Prev</strong>Chapter 3. Accounts</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="LDAPserver-for-user-authentication.html"><strong>Next</strong>3.2. Using an LDAP Server for User Authentication</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/accounts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/accounts.html b/docs/tmp/en-US/html/accounts.html
deleted file mode 100644
index 44845b6..0000000
--- a/docs/tmp/en-US/html/accounts.html
+++ /dev/null
@@ -1,3 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 3. Accounts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="index.html" title="CloudStack Administrator's Guide" /><link rel="prev" href="about-physical-networks.html" title="2.7. About Physical Networks" /><link rel="next" href="accounts-users-domains.html" title="3.1. Accounts, Users, and Domains" /></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="about-physical-networks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="accounts-users-domains.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="accounts" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. Accounts</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="accounts-users-domains.html">3.1. Accounts, Users, and Domains</a></span></dt><dt><span class="section"><a href="LDAPserver-for-user-authentication.html">3.2. Using an LDAP Server for User Authentication</a></span></dt><dd><dl><dt><span class="section"><a href="LDAPserver-for-user-authentication.html#example-LDAP-configuration-commands">3.2.1. Example LDAP Configuration Commands</a></span></dt><dt><span class="section"><a href="LDAPserver-for-user-authentication
.html#search-base">3.2.2. Search Base</a></span></dt><dt><span class="section"><a href="LDAPserver-for-user-authentication.html#query-filter">3.2.3. Query Filter</a></span></dt><dt><span class="section"><a href="LDAPserver-for-user-authentication.html#search-user-bind-dn">3.2.4. Search User Bind DN</a></span></dt><dt><span class="section"><a href="LDAPserver-for-user-authentication.html#SSL-keystore-path-and-password">3.2.5. SSL Keystore Path and Password</a></span></dt></dl></dd></dl></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="accounts-users-domains.html"><strong>Next</strong>3.1. Accounts, Users, and Domains</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/acquire-new-ip-address.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/acquire-new-ip-address.html b/docs/tmp/en-US/html/acquire-new-ip-address.html
deleted file mode 100644
index 09a082e..0000000
--- a/docs/tmp/en-US/html/acquire-new-ip-address.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>15.11. Acquiring a New 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="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="guest-ip-ranges.html" title="15.10. Guest IP Ranges" /><link rel="next" href="release-ip-address.html" title="15.12. Releasing an IP Address" /></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.clouds
tack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="guest-ip-ranges.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="release-ip-address.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="acquire-new-ip-address" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="acquire-new-ip-address">15.11. Acquiring a New IP Address</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">
- 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 Acquire New IP, and click Yes in the confirmation dialog.
- </div><div class="para">
- You are prompted for confirmation because, typically, IP addresses are a limited resource. Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding or static NAT rules.
- </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="guest-ip-ranges.html"><strong>Prev</strong>15.10. Guest IP Ranges</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="release-ip-address.html"><strong>Next</strong>15.12. Releasing an IP Address</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/add-members-to-projects.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/add-members-to-projects.html b/docs/tmp/en-US/html/add-members-to-projects.html
deleted file mode 100644
index 09f5192..0000000
--- a/docs/tmp/en-US/html/add-members-to-projects.html
+++ /dev/null
@@ -1,45 +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.4. Adding Members to 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="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="projects.html" title="Chapter 6. Using Projects to Organize Users and Resources" /><link rel="prev" href="create-new-projects.html" title="6.3. Creating a New Project" /><link rel="next" href="accept-membership-invite.html" title="6.5. Accepting a Membership Invitation" /></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-new-projects.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="accept-membership-invite.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="add-members-to-projects" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="add-members-to-projects">6.4. Adding Members to a Project</h2></div></div></div><div class="para">
- New members can be added to a project by the project’s administrator, the domain administrator of the domain where the project resides or any parent domain, or the CloudStack root administrator. There are two ways to add members in CloudStack, but only one way is enabled at a time:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- If invitations have been enabled, you can send invitations to new members.
- </div></li><li class="listitem"><div class="para">
- If invitations are not enabled, you can add members directly through the UI.
- </div></li></ul></div><div xml:lang="en-US" class="section" id="send-projects-membership-invitation" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="send-projects-membership-invitation">6.4.1. Sending Project Membership Invitations</h3></div></div></div><div class="para">
- Use these steps to add a new member to a project if the invitations feature is enabled in the cloud as described in <a class="xref" href="configuring-projects.html#set-up-invitations">Section 6.2.1, “Setting Up Invitations”</a>. If the invitations feature is not turned on, use the procedure in Adding Project Members From the UI.
- </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 you want to work with.
- </div></li><li class="listitem"><div class="para">
- Click the Invitations tab.
- </div></li><li class="listitem"><div class="para">
- In Add by, select one of the following:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Account – The invitation will appear in the user’s Invitations tab in the Project View. See Using the Project View.
- </div></li><li class="listitem"><div class="para">
- Email – The invitation will be sent to the user’s email address. Each emailed invitation includes a unique code called a token which the recipient will provide back to CloudStack when accepting the invitation. Email invitations will work only if the global parameters related to the SMTP server have been set. See <a class="xref" href="configuring-projects.html#set-up-invitations">Section 6.2.1, “Setting Up Invitations”</a>.
- </div></li></ol></div></li><li class="listitem"><div class="para">
- Type the user name or email address of the new member you want to add, and click Invite. Type the CloudStack user name if you chose Account in the previous step. If you chose Email, type the email address. You can invite only people who have an account in this cloud within the same domain as the project. However, you can send the invitation to any email address.
- </div></li><li class="listitem"><div class="para">
- To view and manage the invitations you have sent, return to this tab. When an invitation is accepted, the new member will appear in the project’s Accounts tab.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="add-projects-members-from-ui" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="add-projects-members-from-ui">6.4.2. Adding Project Members From the UI</h3></div></div></div><div class="para">
- The steps below tell how to add a new member to a project if the invitations feature is not enabled in the cloud. If the invitations feature is enabled cloud,as described in <a class="xref" href="configuring-projects.html#set-up-invitations">Section 6.2.1, “Setting Up Invitations”</a>, use the procedure in <a class="xref" href="add-members-to-projects.html#send-projects-membership-invitation">Section 6.4.1, “Sending Project Membership Invitations”</a>.
- </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 you want to work with.
- </div></li><li class="listitem"><div class="para">
- Click the Accounts tab. The current members of the project are listed.
- </div></li><li class="listitem"><div class="para">
- Type the account name of the new member you want to add, and click Add Account. You can add only people who have an account in this cloud and within the same domain as the project.
- </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="create-new-projects.html"><strong>Prev</strong>6.3. Creating a New Project</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="accept-membership-invite.html"><strong>Next</strong>6.5. Accepting a Membership Invitation</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/add-password-management-to-templates.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/add-password-management-to-templates.html b/docs/tmp/en-US/html/add-password-management-to-templates.html
deleted file mode 100644
index 6dec996..0000000
--- a/docs/tmp/en-US/html/add-password-management-to-templates.html
+++ /dev/null
@@ -1,31 +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.13. Adding Password Management to Your 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="convert-hyperv-vm-to-template.html" title="12.12. Converting a Hyper-V VM to a Template" /><link rel="next" href="delete-templates.html" title="12.14. Deleting 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="convert-hyperv-vm-to-template.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="delete-templates.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="add-password-management-to-templates" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="add-password-management-to-templates">12.13. Adding Password Management to Your Templates</h2></div></div></div><div class="para">
- CloudStack provides an optional password reset feature that allows users to set a temporary admin or root password as well as reset the existing admin or root password from the CloudStack UI.
- </div><div class="para">
- To enable the Reset Password feature, you will need to download an additional script to patch your template. When you later upload the template into CloudStack, you can specify whether reset admin/root password feature should be enabled for this template.
- </div><div class="para">
- The password management feature works always resets the account password on instance boot. The script does an HTTP call to the virtual router to retrieve the account password that should be set. As long as the virtual router is accessible the guest will have access to the account password that should be used. When the user requests a password reset the management server generates and sends a new password to the virtual router for the account. Thus an instance reboot is necessary to effect any password changes.
- </div><div class="para">
- If the script is unable to contact the virtual router during instance boot it will not set the password but boot will continue normally.
- </div><div xml:lang="en-US" class="section" id="linux-installation" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="linux-installation">12.13.1. Linux OS Installation</h3></div></div></div><div class="para">
- Use the following steps to begin the Linux OS installation:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Download the script file cloud-set-guest-password:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Linux: <a href="http://cloudstack.org/dl/cloud-set-guest-password">http://cloudstack.org/dl/cloud-set-guest-password</a>
- </div></li><li class="listitem"><div class="para">
- Windows: <a href="http://sourceforge.net/projects/cloudstack/files/Password%20Management%20Scripts/CloudInstanceManager.msi/download">http://sourceforge.net/projects/cloudstack/files/Password%20Management%20Scripts/CloudInstanceManager.msi/download</a>
- </div></li></ul></div></li><li class="listitem"><div class="para">
- Copy this file to /etc/init.d.
- </div><div class="para">
- On some Linux distributions, copy the file to /etc/rc.d/init.d.
- </div></li><li class="listitem"><div class="para">
- Run the following command to make the script executable:
- </div><pre class="programlisting">chmod +x /etc/init.d/cloud-set-guest-password</pre></li><li class="listitem"><div class="para">
- Depending on the Linux distribution, continue with the appropriate step.
- </div><div class="para">
- On Fedora, CentOS/RHEL, and Debian, run:
- </div><pre class="programlisting">chkconfig --add cloud-set-guest-password</pre></li></ol></div></div><div xml:lang="en-US" class="section" id="windows-installation" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="windows-installation">12.13.2. Windows OS Installation</h3></div></div></div><div class="para">
- Download the installer, CloudInstanceManager.msi, from <a href="http://cloudstack.org/download.html">Download page</a> and run the installer in the newly created Windows VM.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="convert-hyperv-vm-to-template.html"><strong>Prev</strong>12.12. Converting a Hyper-V VM to a Template</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="delete-templates.html"><strong>Next</strong>12.14. Deleting Templates</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/adding-hosts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/adding-hosts.html b/docs/tmp/en-US/html/adding-hosts.html
deleted file mode 100644
index bc40eeb..0000000
--- a/docs/tmp/en-US/html/adding-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.1. Adding 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="working-with-hosts.html" title="Chapter 11. Working With Hosts" /><link rel="next" href="scheduled-maintenance-maintenance-mode-hosts.html" title="11.2. Scheduled Maintenance and Maintenance Mode for Hosts" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Sit
e" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="working-with-hosts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="scheduled-maintenance-maintenance-mode-hosts.html"><strong>Next</strong></a></li></ul><div class="section" id="adding-hosts"><div class="titlepage"><div><div><h2 class="title" id="adding-hosts">11.1. Adding Hosts</h2></div></div></div><div class="para">
- Additional hosts can be added at any time to provide more capacity for guest VMs. For requirements and instructions, see <a class="xref" href="host-add.html">Section 7.5, “Adding a Host”</a>.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="working-with-hosts.html"><strong>Prev</strong>Chapter 11. Working With 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="scheduled-maintenance-maintenance-mode-hosts.html"><strong>Next</strong>11.2. Scheduled Maintenance and Maintenance Mode ...</a></li></ul></body></html>