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/07 19:01:12 UTC

[44/52] [abbrv] [partial] CLOUDSTACK-444 Fix from Radhika PC against docs, adds network setup in the install guide.

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/manual-live-migration.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/manual-live-migration.html b/docs/tmp/en-US/epub/OEBPS/manual-live-migration.html
new file mode 100644
index 0000000..b0b4f5b
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/manual-live-migration.html
@@ -0,0 +1,31 @@
+<?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.9. Moving VMs Between Hosts (Manual Live Migration)</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="manual-live-migration"><div class="titlepage"><div><div><h1 class="title" id="manual-live-migration">10.9. Moving VMs Between Hosts (Manual Live Migration)</h1></div></div></div><div class="para">
+		The CloudPlatform administrator can move a running VM from one host to another without interrupting service to users or going into maintenance mode. This is called manual live migration, and can be done under the following conditions:
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				The root administrator is logged in. Domain admins and users can not perform manual live migration of VMs.
+			</div></li><li class="listitem"><div class="para">
+				The VM is running. Stopped VMs can not be live migrated.
+			</div></li><li class="listitem"><div class="para">
+				The destination host must be in the same cluster as the original host.
+			</div></li><li class="listitem"><div class="para">
+				The VM must not be using local disk storage.
+			</div></li><li class="listitem"><div class="para">
+				The destination host must have enough available capacity. If not, the VM will remain in the "migrating" state until memory becomes available.
+			</div></li></ul></div><div class="para">
+		To manually live migrate a virtual machine
+	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+				Log in to the CloudPlatform UI as a user or admin.
+			</div></li><li class="listitem"><div class="para">
+				In the left navigation, click Instances.
+			</div></li><li class="listitem"><div class="para">
+				Choose the VM that you want to migrate.
+			</div></li><li class="listitem"><div class="para">
+				Click the Migrate Instance button 
+				<span class="inlinemediaobject"><img src="./images/migrate-instance.png" alt="Migrateinstance.png: button to migrate an instance" /></span>
+
+			</div></li><li class="listitem"><div class="para">
+				From the list of hosts, choose the one to which you want to move the VM.
+			</div></li><li class="listitem"><div class="para">
+				Click OK.
+			</div></li></ol></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/multiple-system-vm-vmware.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/multiple-system-vm-vmware.html b/docs/tmp/en-US/epub/OEBPS/multiple-system-vm-vmware.html
new file mode 100644
index 0000000..3ee805b
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/multiple-system-vm-vmware.html
@@ -0,0 +1,5 @@
+<?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.2. Multiple System VM Support for VMware</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="multiple-system-vm-vmware"><div class="titlepage"><div><div><h1 class="title" id="multiple-system-vm-vmware">16.2. Multiple System VM Support for VMware</h1></div></div></div><div class="para">
+		Every CloudStack zone has single System VM for template processing tasks such as downloading templates, uploading templates, and uploading ISOs. In a zone where VMware is being used, additional System VMs can be launched to process VMware-specific tasks such as taking snapshots and creating private templates. The CloudStack management server launches additional System VMs for VMware-specific tasks as the load increases. The management server monitors and weights all commands sent to these System VMs and performs dynamic load balancing and scaling-up of more System VMs.
+	</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/network-offerings.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/network-offerings.html b/docs/tmp/en-US/epub/OEBPS/network-offerings.html
new file mode 100644
index 0000000..c8f88c0
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/network-offerings.html
@@ -0,0 +1,37 @@
+<?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.4. Network 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="network-offerings"><div class="titlepage"><div><div><h1 class="title" id="network-offerings">9.4. Network Offerings</h1></div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+			For the most up-to-date list of supported network services, see the CloudPlatform UI or call listNetworkServices.
+		</div></div></div><div class="para">
+		A network offering is a named set of network services, such as:
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				DHCP
+			</div></li><li class="listitem"><div class="para">
+				DNS
+			</div></li><li class="listitem"><div class="para">
+				Source NAT
+			</div></li><li class="listitem"><div class="para">
+				Static NAT
+			</div></li><li class="listitem"><div class="para">
+				Port Forwarding
+			</div></li><li class="listitem"><div class="para">
+				Load Balancing
+			</div></li><li class="listitem"><div class="para">
+				Firewall
+			</div></li><li class="listitem"><div class="para">
+				VPN
+			</div></li><li class="listitem"><div class="para">
+				Optional) Name one of several available providers to use for a given service, such as Juniper for the firewall
+			</div></li><li class="listitem"><div class="para">
+				(Optional) Network tag to specify which physical network to use
+			</div></li></ul></div><div class="para">
+		When creating a new VM, the user chooses one of the available network offerings, and that determines which network services the VM can use.
+	</div><div class="para">
+		The CloudPlatform administrator can create any number of custom network offerings, in addition to the default network offerings provided by CloudPlatform. By creating multiple custom network offerings, you can set up your cloud to offer different classes of service on a single multi-tenant physical network. For example, while the underlying physical wiring may be the same for two tenants, tenant A may only need simple firewall protection for their website, while tenant B may be running a web server farm and require a scalable firewall solution, load balancing solution, and alternate networks for accessing the database backend.
+	</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+			If you create load balancing rules while using a network service offering that includes an external load balancer device such as NetScaler, and later change the network service offering to one that uses the CloudPlatform virtual router, you must create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function.
+		</div></div></div><div class="para">
+		When creating a new virtual network, the CloudPlatform administrator chooses which network offering to enable for that network. Each virtual network is associated with one network offering. A virtual network can be upgraded or downgraded by changing its associated network offering. If you do this, be sure to reprogram the physical network to match.
+	</div><div class="para">
+		CloudPlatform also has internal network offerings for use by CloudPlatform system VMs. These network offerings are not visible to users but can be modified by administrators.
+	</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/network-service-providers.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/network-service-providers.html b/docs/tmp/en-US/epub/OEBPS/network-service-providers.html
new file mode 100644
index 0000000..a1cdbff
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/network-service-providers.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3. Network Service Providers</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="network-service-providers"><div class="titlepage"><div><div><h1 class="title" id="network-service-providers">9.3. Network Service Providers</h1></div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+			For the most up-to-date list of supported network service providers, see the CloudPlatform UI or call listNetworkServiceProviders.
+		</div></div></div><div class="para">
+		A service provider (also called a network element) is hardware or virtual appliance that makes a network service possible; for example, a firewall appliance can be installed in the cloud to provide firewall service. On a single network, multiple providers can provide the same network service. For example, a firewall service may be provided by Cisco or Juniper devices in the same physical network.
+	</div><div class="para">
+		You can have multiple instances of the same service provider in a network (say, more than one Juniper SRX device).
+	</div><div class="para">
+		If different providers are set up to provide the same service on the network, the administrator can create network offerings so users can specify which network service provider they prefer (along with the other choices offered in network offerings). Otherwise, CloudPlatform will choose which provider to use whenever the service is called for.
+	</div><div class="formalpara"><h5 class="formalpara" id="idm31301224">Supported Network Service Providers</h5>
+			CloudPlatform ships with an internal list of the supported service providers, and you can choose from this list when creating a network offering.
+		</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/networking-in-a-pod.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/networking-in-a-pod.html b/docs/tmp/en-US/epub/OEBPS/networking-in-a-pod.html
new file mode 100644
index 0000000..2e26c83
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/networking-in-a-pod.html
@@ -0,0 +1,15 @@
+<?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.2. Networking in a Pod</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="networking-in-a-pod"><div class="titlepage"><div><div><h1 class="title" id="networking-in-a-pod">15.2. Networking in a Pod</h1></div></div></div><div class="para">
+		Figure 2 illustrates network setup within a single pod. The hosts are connected to a pod-level switch. At a minimum, the hosts should have one physical uplink to each switch. Bonded NICs are supported as well. The pod-level switch is a pair of redundant gigabit switches with 10 G uplinks.
+	</div><div class="mediaobject"><img src="./images/networking-in-a-pod.png" width="444" alt="networking-in-a-pod.png: Network setup in a pod" /></div><div class="para">
+		Servers are connected as follows:
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				Storage devices are connected to only the network that carries management traffic.
+			</div></li><li class="listitem"><div class="para">
+				Hosts are connected to networks for both management traffic and public traffic.
+			</div></li><li class="listitem"><div class="para">
+				Hosts are also connected to one or more networks carrying guest traffic.
+			</div></li></ul></div><div class="para">
+		We recommend the use of multiple physical Ethernet cards to implement each network interface as well as redundant switch fabric in order to maximize throughput and improve reliability.
+	</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/networking-in-a-zone.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/networking-in-a-zone.html b/docs/tmp/en-US/epub/OEBPS/networking-in-a-zone.html
new file mode 100644
index 0000000..121f606
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/networking-in-a-zone.html
@@ -0,0 +1,9 @@
+<?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.3. Networking in a Zone</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="networking-in-a-zone"><div class="titlepage"><div><div><h1 class="title" id="networking-in-a-zone">15.3. Networking in a Zone</h1></div></div></div><div class="para">
+		Figure 3 illustrates the network setup within a single zone.
+	</div><div class="mediaobject"><img src="./images/networking-in-a-zone.png" width="444" alt="networking-in-a-zone.png: Network setup in a single zone" /></div><div class="para">
+		A firewall for management traffic operates in the NAT mode. The network typically is assigned IP addresses in the 192.168.0.0/16 Class B private address space. Each pod is assigned IP addresses in the 192.168.*.0/24 Class C private address space.
+	</div><div class="para">
+		Each zone has its own set of public IP addresses. Public IP addresses from different zones do not overlap.
+	</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/networks.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/networks.html b/docs/tmp/en-US/epub/OEBPS/networks.html
new file mode 100644
index 0000000..7e97caf
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/networks.html
@@ -0,0 +1,15 @@
+<?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 15. Managing Networks and Traffic</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="networks"><div class="titlepage"><div><div><h1 class="title">Chapter 15. Managing Networks and Traffic</h1></div></div></div><div class="para">
+		In a CloudStack, guest VMs can communicate with each other using shared infrastructure with the security and user perception that the guests have a private LAN. The CloudStack virtual router is the main component providing networking features for guest traffic.
+	</div><div class="section" id="guest-traffic"><div class="titlepage"><div><div><h1 class="title" id="guest-traffic">15.1. Guest Traffic</h1></div></div></div><div class="para">
+		A network can carry guest traffic only between VMs within one zone. Virtual machines in different zones cannot communicate with each other using their IP addresses; they must communicate with each other by routing through a public IP address.
+	</div><div class="para">
+		Figure 1 illustrates a typical guest traffic setup:
+	</div><div class="mediaobject"><img src="./images/basic-deployment.png" alt="guesttraffic.png: Depicts a guest traffic setup" /></div><div class="para">
+		The Management Server automatically creates a virtual router for each network. A virtual router is a special virtual machine that runs on the hosts. Each virtual router has three network interfaces. Its eth0 interface serves as the gateway for the guest traffic and has the IP address of 10.1.1.1. Its eth1 interface is used by the system to configure the virtual router. Its eth2 interface is assigned a public IP address for public traffic.
+	</div><div class="para">
+		The virtual router provides DHCP and will automatically assign an IP address for each guest VM within the IP range assigned for the network. The user can manually reconfigure guest VMs to assume different IP addresses.
+	</div><div class="para">
+		Source NAT is automatically configured in the virtual router to forward outbound traffic for all guest VMs
+	</div></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/offerings.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/offerings.html b/docs/tmp/en-US/epub/OEBPS/offerings.html
new file mode 100644
index 0000000..c1152bd
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/offerings.html
@@ -0,0 +1,99 @@
+<?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 8. 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="chapter" id="offerings"><div class="titlepage"><div><div><h1 class="title">Chapter 8. Service Offerings</h1></div></div></div><div class="para">
+		In this chapter we discuss compute, disk, and system service offerings. Network offerings are discussed in the section on setting up networking for users.
+	</div><div class="section" id="compute-disk-service-offerings"><div class="titlepage"><div><div><h1 class="title" id="compute-disk-service-offerings">8.1. Compute and Disk Service Offerings</h1></div></div></div><div class="para">
+		A service offering is a set of virtual hardware features such as CPU core count and speed, memory, and disk size. The CloudStack administrator can set up various offerings, and then end users choose from the available offerings when they create a new VM. A service offering includes the following elements:
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				CPU, memory, and network resource guarantees
+			</div></li><li class="listitem"><div class="para">
+				How resources are metered
+			</div></li><li class="listitem"><div class="para">
+				How the resource usage is charged
+			</div></li><li class="listitem"><div class="para">
+				How often the charges are generated
+			</div></li></ul></div><div class="para">
+		For example, one service offering might allow users to create a virtual machine instance that is equivalent to a 1 GHz Intel® Core™ 2 CPU, with 1 GB memory at $0.20/hour, with network traffic metered at $0.10/GB. Based on the user’s selected offering, CloudStack emits usage records that can be integrated with billing systems. CloudStack separates service offerings into compute offerings and disk offerings. The computing service offering specifies:
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				Guest CPU
+			</div></li><li class="listitem"><div class="para">
+				Guest RAM
+			</div></li><li class="listitem"><div class="para">
+				Guest Networking type (virtual or direct)
+			</div></li><li class="listitem"><div class="para">
+				Tags on the root disk
+			</div></li></ul></div><div class="para">
+		The disk offering specifies:
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				Disk size (optional). An offering without a disk size will allow users to pick their own
+			</div></li><li class="listitem"><div class="para">
+				Tags on the data disk
+			</div></li></ul></div><div class="section" id="creating-compute-offerings"><div class="titlepage"><div><div><h2 class="title" id="creating-compute-offerings">8.1.1. Creating a New Compute Offering</h2></div></div></div><div class="para">
+		To create a new compute offering:
+	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+				Log in with admin privileges to the CloudStack UI.
+			</div></li><li class="listitem"><div class="para">
+				In the left navigation bar, click Service Offerings.
+			</div></li><li class="listitem"><div class="para">
+				In Select Offering, choose Compute Offering.
+			</div></li><li class="listitem"><div class="para">
+				Click Add Compute Offering.
+			</div></li><li class="listitem"><div class="para">
+				In the dialog, make the following choices:
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Name</strong></span>: Any desired name for the service offering.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Description</strong></span>: A short description of the offering that can be displayed to users
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Storage type</strong></span>: The type of disk that should be allocated. Local allocates from storage attached directly to the host where the system VM is running. Shared allocates from storage accessible via NFS.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong># of CPU cores</strong></span>: The number of cores which should be allocated to a system VM with this offering
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>CPU (in MHz)</strong></span>: The CPU speed of the cores that the system VM is allocated. For example, “2000” would provide for a 2 GHz clock.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Memory (in MB)</strong></span>: The amount of memory in megabytes that the system VM should be allocated. For example, “2048” would provide for a 2 GB RAM allocation.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Network Rate</strong></span>: Allowed data transfer rate in MB per second.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Offer HA</strong></span>: If yes, the administrator can choose to have the system VM be monitored and as highly available as possible.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Storage Tags</strong></span>: The tags that should be associated with the primary storage used by the system VM.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Host Tags</strong></span>: (Optional) Any tags that you use to organize your hosts
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>CPU cap</strong></span>: Whether to limit the level of CPU usage even if spare capacity is available.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Public</strong></span>: Indicate whether the service offering should be available all domains or only some domains. Choose Yes to make it available to all domains. Choose No to limit the scope to a subdomain; CloudStack will then prompt for the subdomain's name.
+					</div></li></ul></div></li><li class="listitem"><div class="para">
+				Click Add.
+			</div></li></ol></div></div><div class="section" id="creating-disk-offerings"><div class="titlepage"><div><div><h2 class="title" id="creating-disk-offerings">8.1.2. Creating a New Disk Offering</h2></div></div></div><div class="para">
+		To create a system service offering:
+	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+				Log in with admin privileges to the CloudStack UI.
+			</div></li><li class="listitem"><div class="para">
+				In the left navigation bar, click Service Offerings.
+			</div></li><li class="listitem"><div class="para">
+				In Select Offering, choose Disk Offering.
+			</div></li><li class="listitem"><div class="para">
+				Click Add Disk Offering.
+			</div></li><li class="listitem"><div class="para">
+				In the dialog, make the following choices:
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						Name. Any desired name for the system offering.
+					</div></li><li class="listitem"><div class="para">
+						Description. A short description of the offering that can be displayed to users
+					</div></li><li class="listitem"><div class="para">
+						Custom Disk Size. If checked, the user can set their own disk size. If not checked, the root administrator must define a value in Disk Size.
+					</div></li><li class="listitem"><div class="para">
+						Disk Size. Appears only if Custom Disk Size is not selected. Define the volume size in GB.
+					</div></li><li class="listitem"><div class="para">
+						(Optional)Storage Tags. The tags that should be associated with the primary storage for this disk. Tags are a comma separated list of attributes of the storage. For example "ssd,blue". Tags are also added on Primary Storage. CloudStack matches tags on a disk offering to tags on the storage. If a tag is present on a disk offering that tag (or tags) must also be present on Primary Storage for the volume to be provisioned. If no such primary storage exists, allocation from the disk offering will fail..
+					</div></li><li class="listitem"><div class="para">
+						Public. Indicate whether the service offering should be available all domains or only some domains. Choose Yes to make it available to all domains. Choose No to limit the scope to a subdomain; CloudStack will then prompt for the subdomain's name.
+					</div></li></ul></div></li><li class="listitem"><div class="para">
+				Click Add.
+			</div></li></ol></div></div><div class="section" id="modify-delete-service-offerings"><div class="titlepage"><div><div><h2 class="title" id="modify-delete-service-offerings">8.1.3. Modifying or Deleting a Service Offering</h2></div></div></div><div class="para">
+		Service offerings cannot be changed once created. This applies to both compute offerings and disk offerings.
+	</div><div class="para">
+		A service offering can be deleted. If it is no longer in use, it is deleted immediately and permanently. If the service offering is still in use, it will remain in the database until all the virtual machines referencing it have been deleted. After deletion by the administrator, a service offering will not be available to end users that are creating new instances.
+	</div></div></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/per-domain-limits.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/per-domain-limits.html b/docs/tmp/en-US/epub/OEBPS/per-domain-limits.html
new file mode 100644
index 0000000..d79f019
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/per-domain-limits.html
@@ -0,0 +1,16 @@
+<?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.5. Per-Domain 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="per-domain-limits"><div class="titlepage"><div><div><h1 class="title" id="per-domain-limits">14.5. Per-Domain Limits</h1></div></div></div><div class="para">
+		CloudStack allows the configuration of limits on a domain basis. With a domain limit in place, all users still have their account limits. They are additionally limited, as a group, to not exceed the resource limits set on their domain. Domain limits aggregate the usage of all accounts in the domain as well as all accounts in all subdomains of that domain. Limits set at the root domain level apply to the sum of resource usage by the accounts in all domains and sub-domains below that root domain.
+	</div><div class="para">
+		To set a domain limit:
+	</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 tree, click Domains.
+			</div></li><li class="listitem"><div class="para">
+				Select the domain you want to modify. The current domain limits are displayed. A value of -1 shows that there is no limit in place.
+			</div></li><li class="listitem"><div class="para">
+				Click the Edit button
+				<span class="inlinemediaobject"><img src="./images/edit-icon.png" alt="editbutton.png: edits the settings." /></span>
+			</div></li></ol></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/pod-add.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/pod-add.html b/docs/tmp/en-US/epub/OEBPS/pod-add.html
new file mode 100644
index 0000000..3a8ab1e
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/pod-add.html
@@ -0,0 +1,25 @@
+<?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.3. Adding a Pod</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="pod-add"><div class="titlepage"><div><div><h1 class="title" id="pod-add">7.3. Adding a Pod</h1></div></div></div><div class="para">
+		When you created a new zone, CloudStack adds the first pod for you. You can add more pods at any time using the procedure in this section.
+	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+				Log in to the CloudStack UI. See <a class="xref" href="ui.html#log-in">Section 5.1, “Log In to the UI”</a>.
+			</div></li><li class="listitem"><div class="para">
+				In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone to which you want to add a pod.
+			</div></li><li class="listitem"><div class="para">
+				Click the Compute and Storage tab. In the Pods node of the diagram, click View All.
+			</div></li><li class="listitem"><div class="para">
+				Click Add Pod.
+			</div></li><li class="listitem"><div class="para">
+				Enter the following details in the dialog.
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Name.</strong></span> The name of the pod.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Gateway.</strong></span> The gateway for the hosts in that pod.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Netmask.</strong></span> The network prefix that defines the pod's subnet. Use CIDR notation.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Start/End Reserved System IP.</strong></span> The IP range in the management network that CloudStack uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see System Reserved IP Addresses.
+					</div></li></ul></div></li><li class="listitem"><div class="para">
+				Click OK.
+			</div></li></ol></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/primary-storage-add.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/primary-storage-add.html b/docs/tmp/en-US/epub/OEBPS/primary-storage-add.html
new file mode 100644
index 0000000..157f8d5
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/primary-storage-add.html
@@ -0,0 +1,63 @@
+<?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.6. Add 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="" /></head><body><div class="section" id="primary-storage-add"><div class="titlepage"><div><div><h1 class="title" id="primary-storage-add">7.6. Add Primary Storage</h1></div></div></div><div class="section" id="sys-require-primary-storage"><div class="titlepage"><div><div><h2 class="title" id="sys-require-primary-storage">7.6.1. System Requirements for Primary Storage</h2></div></div></div><div class="para">
+			Hardware requirements:
+		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+					Any standards-compliant iSCSI or NFS server that is supported by the underlying hypervisor.
+				</div></li><li class="listitem"><div class="para">
+					The storage server should be a machine with a large number of disks. The disks should ideally be managed by a hardware RAID controller.
+				</div></li><li class="listitem"><div class="para">
+					Minimum required capacity depends on your needs.
+				</div></li></ul></div><div class="para">
+			When setting up primary storage, follow these restrictions:
+		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+					Primary storage cannot be added until a host has been added to the cluster.
+				</div></li><li class="listitem"><div class="para">
+					If you do not provision shared primary storage, you must set the global configuration parameter system.vm.local.storage.required to true, or else you will not be able to start VMs.
+				</div></li></ul></div></div><div class="section" id="adding-primary-storage"><div class="titlepage"><div><div><h2 class="title" id="adding-primary-storage">7.6.2. Adding Primary Stroage</h2></div></div></div><div class="para">
+			When you create a new zone, the first primary storage is added as part of that procedure. You can add primary storage servers at any time, such as when adding a new cluster or adding more servers to an existing cluster.
+		</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">
+					Log in to the CloudStack UI (see <a class="xref" href="ui.html#log-in">Section 5.1, “Log In to the UI”</a>).
+				</div></li><li class="listitem"><div class="para">
+					In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the primary storage.
+				</div></li><li class="listitem"><div class="para">
+					Click the Compute tab.
+				</div></li><li class="listitem"><div class="para">
+					In the Primary Storage node of the diagram, click View All.
+				</div></li><li class="listitem"><div class="para">
+					Click Add Primary Storage.
+				</div></li><li class="listitem"><div class="para">
+					Provide the following information in the dialog. The information required varies depending on your choice in Protocol.
+				</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Pod.</strong></span> The pod for the storage device.
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Cluster.</strong></span> The cluster for the storage device.
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Name.</strong></span> The name of the storage device.
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Protocol.</strong></span> For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS or SharedMountPoint. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS.
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Server (for NFS, iSCSI, or PreSetup).</strong></span> The IP address or DNS name of the storage device.
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Server (for VMFS).</strong></span> The IP address or DNS name of the vCenter server.
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Path (for NFS).</strong></span> In NFS this is the exported path from the server.
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Path (for VMFS).</strong></span> In vSphere this is a combination of the datacenter name and the datastore name. The format is "/" datacenter name "/" datastore name. For example, "/cloud.dc.VM/cluster1datastore".
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Path (for SharedMountPoint).</strong></span> With KVM this is the path on each host that is where this primary storage is mounted. For example, "/mnt/primary".
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>SR Name-Label (for PreSetup).</strong></span> Enter the name-label of the SR that has been set up outside CloudStack.
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Target IQN (for iSCSI).</strong></span> In iSCSI this is the IQN of the target. For example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984.
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Lun # (for iSCSI).</strong></span> In iSCSI this is the LUN number. For example, 3.
+						</div></li><li class="listitem"><div class="para">
+							<span class="bold bold"><strong>Tags (optional).</strong></span> The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings..
+						</div></li></ul></div><div class="para">
+					The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2.
+				</div></li><li class="listitem"><div class="para">
+					Click OK.
+				</div></li></ol></div></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/primary-storage-outage-and-data-loss.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/primary-storage-outage-and-data-loss.html b/docs/tmp/en-US/epub/OEBPS/primary-storage-outage-and-data-loss.html
new file mode 100644
index 0000000..59ff847
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/primary-storage-outage-and-data-loss.html
@@ -0,0 +1,5 @@
+<?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.4. Primary 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="primary-storage-outage-and-data-loss"><div class="titlepage"><div><div><h1 class="title" id="primary-storage-outage-and-data-loss">17.4. Primary Storage Outage and Data Loss</h1></div></div></div><div class="para">
+		When a primary storage outage occurs the hypervisor immediately stops all VMs stored on that storage device. Guests that are marked for HA will be restarted as soon as practical when the primary storage comes back on line. With NFS, the hypervisor may allow the virtual machines to continue running depending on the nature of the issue. For example, an NFS hang will cause the guest VMs to be suspended until storage connectivity is restored.Primary storage is not designed to be backed up. Individual volumes in primary storage can be backed up using snapshots.
+	</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/primary-storage.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/primary-storage.html b/docs/tmp/en-US/epub/OEBPS/primary-storage.html
new file mode 100644
index 0000000..362302f
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/primary-storage.html
@@ -0,0 +1,5 @@
+<?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.2. 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="" /></head><body><div class="section" id="primary-storage"><div class="titlepage"><div><div><h1 class="title" id="primary-storage">13.2. Primary Storage</h1></div></div></div><div class="para">
+		This section gives concepts and technical details about CloudPlatform primary storage. For information about how to install and configure primary storage through the CloudPlatform UI, see the Advanced Installation Guide.
+	</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/private-public-template.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/private-public-template.html b/docs/tmp/en-US/epub/OEBPS/private-public-template.html
new file mode 100644
index 0000000..b62d475
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/private-public-template.html
@@ -0,0 +1,9 @@
+<?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.5. Private and Public 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="private-public-template"><div class="titlepage"><div><div><h1 class="title" id="private-public-template">12.5. Private and Public Templates</h1></div></div></div><div class="para">
+		When a user creates a template, it can be designated private or public.
+	</div><div class="para">
+		Private templates are only available to the user who created them. By default, an uploaded template is private.
+	</div><div class="para">
+		When a user marks a template as “public,” the template becomes available to all users in all accounts in the user's domain, as well as users in any other domains that have access to the Zone where the template is stored. This depends on whether the Zone, in turn, was defined as private or public. A private Zone is assigned to a single domain, and a public Zone is accessible to any domain. If a public template is created in a private Zone, it is available only to users in the domain assigned to that Zone. If a public template is created in a public Zone, it is available to all users in all domains.
+	</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/projects.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/projects.html b/docs/tmp/en-US/epub/OEBPS/projects.html
new file mode 100644
index 0000000..fa50e80
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/projects.html
@@ -0,0 +1,11 @@
+<?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 6. Using Projects to Organize Users and Resources</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="projects"><div class="titlepage"><div><div><h1 class="title">Chapter 6. Using Projects to Organize Users and Resources</h1></div></div></div><div class="section" id="projects-overview"><div class="titlepage"><div><div><h1 class="title" id="projects-overview">6.1. Overview of Projects</h1></div></div></div><div class="para">
+		Projects are used to organize people and resources. CloudStack users within a single domain can group themselves into project teams so they can collaborate and share virtual resources such as VMs, snapshots, templates, data disks, and IP addresses. CloudStack tracks resource usage per project as well as per user, so the usage can be billed to either a user account or a project. For example, a private cloud within a software company might have all members of the QA department assigned to one project, so the company can track the resources used in testing while the project members can more easily isolate their efforts from other users of the same cloud
+	</div><div class="para">
+		You can configure CloudStack to allow any user to create a new project, or you can restrict that ability to just CloudStack administrators. Once you have created a project, you become that project’s administrator, and you can add others within your domain to the project. CloudStack can be set up either so that you can add people directly to a project, or so that you have to send an invitation which the recipient must accept. Project members can view and manage all virtual resources created by anyone in the project (for example, share VMs). A user can be a member of any number of projects and can switch views in the CloudStack UI to show only project-related information, such as project VMs, fellow project members, project-related alerts, and so on.
+	</div><div class="para">
+		The project administrator can pass on the role to another project member. The project administrator can also add more members, remove members from the project, set new resource limits (as long as they are below the global defaults set by the CloudStack administrator), and delete the project. When the administrator removes a member from the project, resources created by that user, such as VM instances, remain with the project. This brings us to the subject of resource ownership and which resources can be used by a project.
+	</div><div class="para">
+		Resources created within a project are owned by the project, not by any particular CloudStack account, and they can be used only within the project. A user who belongs to one or more projects can still create resources outside of those projects, and those resources belong to the user’s account; they will not be counted against the project’s usage or resource limits. You can create project-level networks to isolate traffic within the project and provide network services such as port forwarding, load balancing, VPN, and static NAT. A project can also make use of certain types of resources from outside the project, if those resources are shared. For example, a shared network or public template is available to any project in the domain. A project can get access to a private template if the template’s owner will grant permission. A project can use any service offering or disk offering available in its domain; however, you can not create private service and disk offerings at the p
 roject level..
+	</div></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/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
new file mode 100644
index 0000000..63ab64b
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/provisioning-steps.html
@@ -0,0 +1,27 @@
+<?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/8e353282/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
new file mode 100644
index 0000000..3e02be2
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/re-install-hosts.html
@@ -0,0 +1,5 @@
+<?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/8e353282/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
new file mode 100644
index 0000000..68cdb14
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/release-ip-address.html
@@ -0,0 +1,17 @@
+<?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/8e353282/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
new file mode 100644
index 0000000..1e37947
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/removing-hosts.html
@@ -0,0 +1,19 @@
+<?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/8e353282/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
new file mode 100644
index 0000000..fdc7a02
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/requirements-templates.html
@@ -0,0 +1,7 @@
+<?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/8e353282/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
new file mode 100644
index 0000000..3d3cffd
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/scheduled-maintenance-maintenance-mode-hosts.html
@@ -0,0 +1,5 @@
+<?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/8e353282/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
new file mode 100644
index 0000000..ff4a8be
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/secondary-storage-add.html
@@ -0,0 +1,25 @@
+<?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/8e353282/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
new file mode 100644
index 0000000..c1f93cb
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/secondary-storage-outage-and-data-loss.html
@@ -0,0 +1,7 @@
+<?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/8e353282/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
new file mode 100644
index 0000000..71d0dc9
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/secondary-storage-vm.html
@@ -0,0 +1,11 @@
+<?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/8e353282/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
new file mode 100644
index 0000000..3de485e
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/secondary-storage.html
@@ -0,0 +1,5 @@
+<?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/8e353282/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
new file mode 100644
index 0000000..5dbe6c1
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/security-groups.html
@@ -0,0 +1,74 @@
+<?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/8e353282/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
new file mode 100644
index 0000000..3f654ed
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/set-database-buffer-pool-size.html
@@ -0,0 +1,13 @@
+<?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>