You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by wi...@apache.org on 2013/01/15 10:36:31 UTC
[39/52] [partial] Remove docs/tmp (partial revert)
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/ip-load-balancing.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/ip-load-balancing.html b/docs/tmp/en-US/html/ip-load-balancing.html
deleted file mode 100644
index 4c6e100..0000000
--- a/docs/tmp/en-US/html/ip-load-balancing.html
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.15. IP Load Balancing</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.1-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="networks.html" title="Chapter 11. Managing Networks and Traffic" /><link rel="prev" href="ip-forwarding-firewalling.html" title="11.14. IP Forwarding and Firewalling" /><link rel="next" href="dns-dhcp.html" title="11.16. DNS and DHCP" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.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="ip-forwarding-firewalling.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="dns-dhcp.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="ip-load-balancing" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ip-load-balancing">11.15. IP Load Balancing</h2></div></div></div><div class="para">
- The user may choose to associate the same public IP for multiple guests. CloudStack implements a TCP-level load balancer with the following policies.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Round-robin
- </div></li><li class="listitem"><div class="para">
- Least connection
- </div></li><li class="listitem"><div class="para">
- Source IP
- </div></li></ul></div><div class="para">
- This is similar to port forwarding but the destination may be multiple IP addresses.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ip-forwarding-firewalling.html"><strong>Prev</strong>11.14. IP Forwarding and Firewalling</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="dns-dhcp.html"><strong>Next</strong>11.16. DNS and DHCP</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/large_scale_redundant_setup.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/large_scale_redundant_setup.html b/docs/tmp/en-US/html/large_scale_redundant_setup.html
deleted file mode 100644
index 75625f8..0000000
--- a/docs/tmp/en-US/html/large_scale_redundant_setup.html
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2. Large-Scale Redundant Setup</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.1-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="choosing-a-deployment_architecture.html" title="Chapter 9. Choosing a Deployment Architecture" /><link rel="prev" href="small_scale_deployment.html" title="9.1. Small-Scale Deployment" /><link rel="next" href="separate_storage_network.html" title="9.3. Separate Storage Network" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Sit
e" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="small_scale_deployment.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="separate_storage_network.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="large_scale_redundant_setup" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="large_scale_redundant_setup">9.2. Large-Scale Redundant Setup</h2></div></div></div><div class="mediaobject"><img src="./images/large-scale-redundant-setup.png" width="444" alt="Large-Scale Redundant Setup" /></div><div class="para">
- This diagram illustrates the network architecture of a large-scale CloudStack deployment.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- A layer-3 switching layer is at the core of the data center. A router redundancy protocol like VRRP should be deployed. Typically high-end core switches also include firewall modules. Separate firewall appliances may also be used if the layer-3 switch does not have integrated firewall capabilities. The firewalls are configured in NAT mode. The firewalls provide the following functions:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Forwards HTTP requests and API calls from the Internet to the Management Server. The Management Server resides on the management network.
- </div></li><li class="listitem"><div class="para">
- When the cloud spans multiple zones, the firewalls should enable site-to-site VPN such that servers in different zones can directly reach each other.
- </div></li></ul></div></li><li class="listitem"><div class="para">
- A layer-2 access switch layer is established for each pod. Multiple switches can be stacked to increase port count. In either case, redundant pairs of layer-2 switches should be deployed.
- </div></li><li class="listitem"><div class="para">
- The Management Server cluster (including front-end load balancers, Management Server nodes, and the MySQL database) is connected to the management network through a pair of load balancers.
- </div></li><li class="listitem"><div class="para">
- Secondary storage servers are connected to the management network.
- </div></li><li class="listitem"><div class="para">
- Each pod contains storage and computing servers. Each storage and computing server should have redundant NICs connected to separate layer-2 access switches.
- </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="small_scale_deployment.html"><strong>Prev</strong>9.1. Small-Scale Deployment</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="separate_storage_network.html"><strong>Next</strong>9.3. Separate Storage Network</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/layer2-switch.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/layer2-switch.html b/docs/tmp/en-US/html/layer2-switch.html
deleted file mode 100644
index b44cda2..0000000
--- a/docs/tmp/en-US/html/layer2-switch.html
+++ /dev/null
@@ -1,42 +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.4. Layer-2 Switch</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="network-setup.html" title="Chapter 12. Network Setup" /><link rel="prev" href="hardware-config-eg.html" title="12.3. Example Hardware Configuration" /><link rel="next" href="hardware-firewall.html" title="12.5. Hardware Firewall" /></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="hardware-config-eg.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="hardware-firewall.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="layer2-switch" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="layer2-switch">12.4. Layer-2 Switch</h2></div></div></div><div class="para">
- The layer-2 switch is the access switching layer inside the pod.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- It should trunk all VLANs into every computing host.
- </div></li><li class="listitem"><div class="para">
- It should switch traffic for the management network containing computing and storage hosts. The layer-3 switch will serve as the gateway for the management network.
- </div></li></ul></div><div class="formalpara"><h5 class="formalpara" id="idp22191000">Example Configurations</h5>
- This section contains example configurations for specific switch models for pod-level layer-2 switching. It assumes VLAN management protocols such as VTP or GVRP have been disabled. The scripts must be changed appropriately if you choose to use VTP or GVRP.
- </div><div xml:lang="en-US" class="section" id="dell62xx-layer2" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="dell62xx-layer2">12.4.1. Dell 62xx</h3></div></div></div><div class="para">
- The following steps show how a Dell 62xx is configured for pod-level layer-2 switching.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Configure all the VLANs in the database.
- </div><pre class="programlisting">vlan database
-vlan 300-999
-exit</pre></li><li class="listitem"><div class="para">
- VLAN 201 is used to route untagged private IP addresses for pod 1, and pod 1 is connected to this layer-2 switch.
- </div><pre class="programlisting">interface range ethernet all
-switchport mode general
-switchport general allowed vlan add 300-999 tagged
-exit</pre></li></ol></div><div class="para">
- The statements configure all Ethernet ports to function as follows:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- All ports are configured the same way.
- </div></li><li class="listitem"><div class="para">
- All VLANs (300-999) are passed through all the ports of the layer-2 switch.
- </div></li></ul></div></div><div xml:lang="en-US" class="section" id="cisco3750-layer2" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="cisco3750-layer2">12.4.2. Cisco 3750</h3></div></div></div><div class="para">
- The following steps show how a Cisco 3750 is configured for pod-level layer-2 switching.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Setting VTP mode to transparent allows us to utilize VLAN IDs above 1000. Since we only use VLANs up to 999, vtp transparent mode is not strictly required.
- </div><pre class="programlisting">vtp mode transparent
-vlan 300-999
-exit</pre></li><li class="listitem"><div class="para">
- Configure all ports to dot1q and set 201 as the native VLAN.
- </div><pre class="programlisting">interface range GigabitEthernet 1/0/1-24
-switchport trunk encapsulation dot1q
-switchport mode trunk
-switchport trunk native vlan 201
-exit</pre></li></ol></div><div class="para">
- By default, Cisco passes all VLANs. Cisco switches complain of the native VLAN IDs are different when 2 ports are connected together. That’s why you must specify VLAN 201 as the native VLAN on the layer-2 switch.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="hardware-config-eg.html"><strong>Prev</strong>12.3. Example Hardware Configuration</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="hardware-firewall.html"><strong>Next</strong>12.5. Hardware Firewall</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/load-balancer-rules.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/load-balancer-rules.html b/docs/tmp/en-US/html/load-balancer-rules.html
deleted file mode 100644
index 4e65a4e..0000000
--- a/docs/tmp/en-US/html/load-balancer-rules.html
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.9. Load Balancer Rules</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.1-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="networks.html" title="Chapter 11. Managing Networks and Traffic" /><link rel="prev" href="external-firewalls-and-load-balancers.html" title="11.8. External Firewalls and Load Balancers" /><link rel="next" href="guest-ip-ranges.html" title="11.10. Guest IP Ranges" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="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="external-firewalls-and-load-balancers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="guest-ip-ranges.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="load-balancer-rules" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="load-balancer-rules">11.9. Load Balancer Rules</h2></div></div></div><div class="para">
- A CloudStack user or administrator may create load balancing rules that balance traffic received at a public IP to one or more VMs. A user creates a rule, specifies an algorithm, and assigns the rule to a set of VMs.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- If you create load balancing rules while using a network service offering that includes an external load balancer device such as NetScaler, and later change the network service offering to one that uses the CloudStack virtual router, you must create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function.
- </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="external-firewalls-and-load-balancers.html"><strong>Prev</strong>11.8. External Firewalls and Load Balancers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="guest-ip-ranges.html"><strong>Next</strong>11.10. Guest IP Ranges</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/log-in.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/log-in.html b/docs/tmp/en-US/html/log-in.html
deleted file mode 100644
index c7f52c0..0000000
--- a/docs/tmp/en-US/html/log-in.html
+++ /dev/null
@@ -1,62 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.1. Log In to the UI</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.1-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="ui.html" title="Chapter 5. User Interface" /><link rel="prev" href="ui.html" title="Chapter 5. User Interface" /><link rel="next" href="using-sshkeys.html" title="5.2. Using SSH Keys for Authentication" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/i
mages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ui.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="using-sshkeys.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="log-in" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="log-in">5.1. Log In to the UI</h2></div></div></div><div class="para">
- CloudStack provides a web-based UI that can be used by both administrators and end users. The appropriate version of the UI is displayed depending on the credentials used to log in. The UI is available in popular browsers including IE7, IE8, IE9, Firefox 3.5+, Firefox 4, Safari 4, and Safari 5. The URL is: (substitute your own management server IP address)
- </div><pre class="programlisting">http://<management-server-ip-address>:8080/client</pre><div class="para">
- On a fresh Management Server installation, a guided tour splash screen appears. On later visits, you’ll see a login screen where you specify the following to proceed to your Dashboard:
- </div><div class="formalpara"><h5 class="formalpara" id="idp12673936">Username</h5>
- The user ID of your account. The default username is admin.
- </div><div class="formalpara"><h5 class="formalpara" id="idp40894472">Password</h5>
- The password associated with the user ID. The password for the default username is password.
- </div><div class="formalpara"><h5 class="formalpara" id="idp23329384">Domain</h5>
- If you are a root user, leave this field blank.
- </div><div class="para">
- If you are a user in the sub-domains, enter the full path to the domain, excluding the root domain.
- </div><div class="para">
- For example, suppose multiple levels are created under the root domain, such as Comp1/hr. The users in the Comp1 domain should enter Comp1 in the Domain field, whereas the users in the Comp1/sales domain should enter Comp1/sales.
- </div><div class="para">
- For more guidance about the choices that appear when you log in to this UI, see Logging In as the Root Administrator.
- </div><div xml:lang="en-US" class="section" id="end-user-ui-overview" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="end-user-ui-overview">5.1.1. End User's UI Overview</h3></div></div></div><div class="para">
- The CloudStack UI helps users of cloud infrastructure to view and use their cloud resources, including virtual machines, templates and ISOs, data volumes and snapshots, guest networks, and IP addresses. If the user is a member or administrator of one or more CloudStack projects, the UI can provide a project-oriented view.
- </div></div><div xml:lang="en-US" class="section" id="root-admin-ui-overview" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="root-admin-ui-overview">5.1.2. Root Administrator's UI Overview</h3></div></div></div><div class="para">
- The CloudStack UI helps the CloudStack administrator provision, view, and manage the cloud infrastructure, domains, user accounts, projects, and configuration settings. The first time you start the UI after a fresh Management Server installation, you can choose to follow a guided tour to provision your cloud infrastructure. On subsequent logins, the dashboard of the logged-in user appears. The various links in this screen and the navigation bar on the left provide access to a variety of administrative functions. The root administrator can also use the UI to perform all the same tasks that are present in the end-user’s UI.
- </div></div><div xml:lang="en-US" class="section" id="log-in-root-admin" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="log-in-root-admin">5.1.3. Logging In as the Root Administrator</h3></div></div></div><div class="para">
- After the Management Server software is installed and running, you can run the CloudStack user interface. This UI is there to help you provision, view, and manage your cloud infrastructure.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Open your favorite Web browser and go to this URL. Substitute the IP address of your own Management Server:
- </div><pre class="programlisting">http://<management-server-ip-address>:8080/client</pre><div class="para">
- On a fresh Management Server installation, a guided tour splash screen appears. On later visits, you’ll see a login screen where you can enter a user ID and password and proceed to your Dashboard.
- </div></li><li class="listitem"><div class="para">
- If you see the first-time splash screen, choose one of the following.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="bold bold"><strong>Continue with basic setup.</strong></span> Choose this if you're just trying CloudStack, and you want a guided walkthrough of the simplest possible configuration so that you can get started right away. We'll help you set up a cloud with the following features: a single machine that runs CloudStack software and uses NFS to provide storage; a single machine running VMs under the XenServer or KVM hypervisor; and a shared public network.
- </div><div class="para">
- The prompts in this guided tour should give you all the information you need, but if you want just a bit more detail, you can follow along in the Trial Installation Guide.
- </div></li><li class="listitem"><div class="para">
- <span class="bold bold"><strong>I have used CloudStack before.</strong></span> Choose this if you have already gone through a design phase and planned a more sophisticated deployment, or you are ready to start scaling up a trial cloud that you set up earlier with the basic setup screens. In the Administrator UI, you can start using the more powerful features of CloudStack, such as advanced VLAN networking, high availability, additional network elements such as load balancers and firewalls, and support for multiple hypervisors including Citrix XenServer, KVM, and VMware vSphere.
- </div><div class="para">
- The root administrator Dashboard appears.
- </div></li></ul></div></li><li class="listitem"><div class="para">
- You should set a new root administrator password. If you chose basic setup, you’ll be prompted to create a new password right away. If you chose experienced user, use the steps in <a class="xref" href="log-in.html#changing-root-password">Section 5.1.4, “Changing the Root Password”</a>.
- </div></li></ol></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
- You are logging in as the root administrator. This account manages the CloudStack deployment, including physical infrastructure. The root administrator can modify configuration settings to change basic functionality, create or delete user accounts, and take many actions that should be performed only by an authorized person. Please change the default password to a new, unique password.
- </div></div></div></div><div xml:lang="en-US" class="section" id="changing-root-password" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="changing-root-password">5.1.4. Changing the Root Password</h3></div></div></div><div class="para">
- During installation and ongoing cloud administration, you will need to log in to the UI as the root administrator. The root administrator account manages the CloudStack deployment, including physical infrastructure. The root administrator can modify configuration settings to change basic functionality, create or delete user accounts, and take many actions that should be performed only by an authorized person. When first installing CloudStack, be sure to change the default password to a new, unique value.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Open your favorite Web browser and go to this URL. Substitute the IP address of your own Management Server:
- </div><pre class="programlisting">http://<management-server-ip-address>:8080/client</pre></li><li class="listitem"><div class="para">
- Log in to the UI using the current root user ID and password. The default is admin, password.
- </div></li><li class="listitem"><div class="para">
- Click Accounts.
- </div></li><li class="listitem"><div class="para">
- Click the admin account name.
- </div></li><li class="listitem"><div class="para">
- Click View Users.
- </div></li><li class="listitem"><div class="para">
- Click the admin user name.
- </div></li><li class="listitem"><div class="para">
- Click the Change Password button.
- <span class="inlinemediaobject"><img src="./images/change-password.png" alt="change-password.png: button to change a user's password" /></span>
- </div></li><li class="listitem"><div class="para">
- Type the new password, and click OK.
- </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ui.html"><strong>Prev</strong>Chapter 5. User Interface</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="using-sshkeys.html"><strong>Next</strong>5.2. Using SSH Keys for Authentication</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/maintain-hypervisors-on-hosts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/maintain-hypervisors-on-hosts.html b/docs/tmp/en-US/html/maintain-hypervisors-on-hosts.html
deleted file mode 100644
index c3d403d..0000000
--- a/docs/tmp/en-US/html/maintain-hypervisors-on-hosts.html
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.6. Maintaining Hypervisors on Hosts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="working-with-hosts.html" title="Chapter 11. Working With Hosts" /><link rel="prev" href="re-install-hosts.html" title="11.5. Re-Installing Hosts" /><link rel="next" href="change-host-password.html" title="11.7. Changing Host Password" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://doc
s.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="re-install-hosts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="change-host-password.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="maintain-hypervisors-on-hosts" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="maintain-hypervisors-on-hosts">11.6. Maintaining Hypervisors on Hosts</h2></div></div></div><div class="para">
- When running hypervisor software on hosts, be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. CloudStack will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- The lack of up-do-date hotfixes can lead to data corruption and lost VMs.
- </div></div></div><div class="para">
- (XenServer) For more information, see <a href="http://docs.cloudstack.org/Knowledge_Base/Possible_VM_corruption_if_XenServer_Hotfix_is_not_Applied/Highly_Recommended_Hotfixes_for_XenServer_5.6_SP2">Highly Recommended Hotfixes for XenServer in the CloudStack Knowledge Base</a>
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="re-install-hosts.html"><strong>Prev</strong>11.5. Re-Installing Hosts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="change-host-password.html"><strong>Next</strong>11.7. Changing Host Password</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/manage-cloud.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/manage-cloud.html b/docs/tmp/en-US/html/manage-cloud.html
deleted file mode 100644
index f2ba053..0000000
--- a/docs/tmp/en-US/html/manage-cloud.html
+++ /dev/null
@@ -1,3 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 18. Managing the Cloud</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="index.html" title="CloudStack Administrator's Guide" /><link rel="prev" href="secondary-storage-outage-and-data-loss.html" title="17.5. Secondary Storage Outage and Data Loss" /><link rel="next" href="tagging-resources.html" title="18.1. Using Tags to Organize Resources in the Cloud" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site
" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="secondary-storage-outage-and-data-loss.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="tagging-resources.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="manage-cloud" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 18. Managing the Cloud</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="tagging-resources.html">18.1. Using Tags to Organize Resources in the Cloud</a></span></dt><dt><span class="section"><a href="change-database-config.html">18.2. Changing the Database Configuration</a></span></dt><dt><span class="section"><a href="change-database-password.html">18.3. Changing the Database Password</a></span></dt><dt><span class="section"><a href="admin-alerts.html">18
.4. Administrator Alerts</a></span></dt><dt><span class="section"><a href="customizing-dns.html">18.5. Customizing the Network Domain Name</a></span></dt><dt><span class="section"><a href="stop-restart-management-server.html">18.6. Stopping and Restarting the Management Server</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="secondary-storage-outage-and-data-loss.html"><strong>Prev</strong>17.5. Secondary Storage Outage and Data Loss</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="tagging-resources.html"><strong>Next</strong>18.1. Using Tags to Organize Resources in the Clo...</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/management-server-install-flow.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/management-server-install-flow.html b/docs/tmp/en-US/html/management-server-install-flow.html
deleted file mode 100644
index 1db5af0..0000000
--- a/docs/tmp/en-US/html/management-server-install-flow.html
+++ /dev/null
@@ -1,333 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.5. Management Server Installation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.1-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="installation.html" title="Chapter 4. Installation" /><link rel="prev" href="configure-package-repository.html" title="4.4. Configure package repository" /><link rel="next" href="ui.html" title="Chapter 5. User Interface" /></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="configure-package-repository.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ui.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="management-server-install-flow" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="management-server-install-flow">4.5. Management Server Installation</h2></div></div></div><div xml:lang="en-US" class="section" id="management-server-installation-overview" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="management-server-installation-overview">4.5.1. Management Server Installation Overview</h3></div></div></div><div class="para">
- This section describes installing the Management Server. There are two slightly different installation flows, depending on how many Management Server nodes will be in your cloud:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- A single Management Server node, with MySQL on the same node.
- </div></li><li class="listitem"><div class="para">
- Multiple Management Server nodes, with MySQL on a node separate from the Management Servers.
- </div></li></ul></div><div class="para">
- In either case, each machine must meet the system requirements described in System Requirements.
- </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
- For the sake of security, be sure the public Internet can not access port 8096 or port 8250 on the Management Server.
- </div></div></div><div class="para">
- The procedure for installing the Management Server is:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Prepare the Operating System
- </div></li><li class="listitem"><div class="para">
- Download and install vhd-util.
- </div></li><li class="listitem"><div class="para">
- Install the First Management Server
- </div></li><li class="listitem"><div class="para">
- Install and Configure the MySQL database
- </div></li><li class="listitem"><div class="para">
- Prepare NFS Shares
- </div></li><li class="listitem"><div class="para">
- Prepare and Start Additional Management Servers (optional)
- </div></li><li class="listitem"><div class="para">
- Prepare the System VM Template
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="prepare-os" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="prepare-os">4.5.2. Prepare the Operating System</h3></div></div></div><div class="para">
- The OS must be prepared to host the Management Server using the following steps. These steps must be performed on each Management Server node.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Log in to your OS as root.
- </div></li><li class="listitem"><div class="para">
- Check for a fully qualified hostname.
- </div><pre class="programlisting"><span class="perl_BString">hostname</span> --fqdn</pre><div class="para">
- This should return a fully qualified hostname such as "managament1.lab.example.org". If it does not, edit /etc/hosts so that it does.
- </div></li><li class="listitem"><div class="para">
- Make sure that the machine can reach the Internet.
- </div><pre class="programlisting"><span class="perl_BString">ping</span> www.cloudstack.org</pre></li><li class="listitem"><div class="para">
- Turn on NTP for time synchronization.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- NTP is required to synchronize the clocks of the servers in your cloud.
- </div></div></div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
- Install NTP.
- </div><pre class="programlisting">yum <span class="perl_BString">install</span> ntp</pre><pre class="programlisting">apt-get <span class="perl_BString">install</span> openntpd</pre></li></ol></div></li><li class="listitem"><div class="para">
- Repeat all of these steps on every host where the Management Server will be installed.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="management-server-install" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="management-server-install">4.5.3. Install the Management Server on the First Host</h3></div></div></div><div class="para">
- The first step in installation, whether you are installing the Management Server on one host or many, is to install the software on a single node.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- If you are planning to install the Management Server on multiple nodes for high availability, do not proceed to the additional nodes yet. That step will come later.
- </div></div></div><div class="para">
- The CloudStack Management server can be installed using either RPM or DEB packages. These packages will depend on everything you need to run the Management server.
- </div><div class="section" id="vhd-util"><div class="titlepage"><div><div><h4 class="title" id="vhd-util">4.5.3.1. Downloading vhd-util</h4></div></div></div><div class="para">
- Before setting up the Management Server, download vhd-util from <a href="http://download.cloud.com.s3.amazonaws.com/tools/vhd-util">vhd-util</a>
- </div><div class="para">
- If the Management Server is RHEL or CentOS, copy vhd-util to /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver.
- </div><div class="para">
- If the Management Server is Ubuntu, copy vhd-util to /usr/lib/cloud/common/scripts/vm/hypervisor/xenserver/vhd-util.
- </div></div><div class="section" id="management-server-install-rhel"><div class="titlepage"><div><div><h4 class="title" id="management-server-install-rhel">4.5.3.2. Install on CentOS/RHEL</h4></div></div></div><div class="para">
- We start by installing the required packages:
- </div><pre class="programlisting">yum <span class="perl_BString">install</span> cloud-client</pre></div><div class="section" id="management-server-install-ubuntu"><div class="titlepage"><div><div><h4 class="title" id="management-server-install-ubuntu">4.5.3.3. Install on Ubuntu</h4></div></div></div><pre class="programlisting">apt-get <span class="perl_BString">install</span> cloud-client</pre></div></div><div xml:lang="en-US" class="section" id="management-server-install-db" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="management-server-install-db">4.5.4. Install the database server</h3></div></div></div><div class="para">
- The CloudStack management server uses a MySQL database server to store it's data. When you are installing the management server on a single node you can install the MySQL server locally. When using a multi-node installation the MySQL database has to run on an external node.
- </div><div class="para">
- CloudStack has been tested with MySQL 5.1 and 5.5, both should work fine. These versions are included in RHEL/CentOS and Ubuntu.
- </div><div xml:lang="en-US" class="section" id="management-server-install-db-local" lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="management-server-install-db-local">4.5.4.1. Install the Database on the Management Server Node</h4></div></div></div><div class="para">
- This section describes how to install MySQL on the same machine with the Management Server. This technique is intended for a simple deployment that has a single Management Server node. If you have a multi-node Management Server deployment, you will typically use a separate node for MySQL. See <a class="xref" href="management-server-install-flow.html#management-server-install-db-external">Section 4.5.4.2, “Install the Database on a Separate Node”</a>.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Install MySQL from the package repository from your distribution:
- </div><pre class="programlisting">yum <span class="perl_BString">install</span> mysql-server</pre><pre class="programlisting">apt-get <span class="perl_BString">install</span> mysql-server</pre></li><li class="listitem"><div class="para">
- Edit the MySQL configuration (/etc/my.cnf or /etc/mysql/my.cnf, depending on your OS) and insert the following lines in the [mysqld] section. You can put these lines below the datadir line. The max_connections parameter should be set to 350 multiplied by the number of Management Servers you are deploying. This example assumes one Management Server.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- On Ubuntu you can also create a file /etc/mysql/conf.d/cloudstack.cnf and add these directives there. Don't forget to add [mysqld] on the first line of the file.
- </div></div></div><pre class="programlisting">
-innodb_rollback_on_timeout=1
-innodb_lock_wait_timeout=600
-max_connections=350
-log-bin=mysql-bin
-binlog-format = 'ROW'
-</pre></li><li class="listitem"><div class="para">
- On RHEL/CentOS MySQL doesn't start after installation, start it manually.
- </div><pre class="programlisting">service mysqld start</pre></li><li class="listitem"><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
- On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly recommended that you set a root password as a security precaution. Run the following commands, and substitute your own desired root password. This step is not required on Ubuntu as it asks for a root password during installation.
- </div></div></div><div class="para">
- Run this command to secure your installation. Since we are running MySQL locally you can answer "Y" to all questions.
- </div><pre class="programlisting">mysql_secure_installation</pre></li><li class="listitem"><div class="para">
- Set up the database. The following command creates the "cloud" user on the database.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- In dbpassword, specify the password to be assigned to the "cloud" user. You can choose to provide no password although that is not recommended.
- </div></li><li class="listitem"><div class="para">
- In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the "cloud" user.
- </div></li><li class="listitem"><div class="para">
- (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption.
- </div></li><li class="listitem"><div class="para">
- (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption.
- </div></li><li class="listitem"><div class="para">
- (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption.
- </div></li></ul></div><pre class="programlisting">cloud-setup-databases cloud:<span class="perl_Operator"><</span>dbpassword<span class="perl_Operator">></span>@localhost \
- --deploy-as=root:<span class="perl_Operator"><</span>password<span class="perl_Operator">></span> \
- -e <span class="perl_Operator"><</span>encryption_type<span class="perl_Operator">></span> \
- -m <span class="perl_Operator"><</span>management_server_key<span class="perl_Operator">></span> \
- -k <span class="perl_Operator"><</span>database_key<span class="perl_Operator">></span></pre><div class="para">
- When this script is finished, you should see a message like “Successfully initialized the database.”
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="management-server-install-db-external" lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="management-server-install-db-external">4.5.4.2. Install the Database on a Separate Node</h4></div></div></div><div class="para">
- This section describes how to install MySQL on a standalone machine, separate from the Management Server. This technique is intended for a deployment that includes several Management Server nodes. If you have a single-node Management Server deployment, you will typically use the same node for MySQL. See <a class="xref" href="management-server-install-flow.html#management-server-install-db-local">Section 4.5.4.1, “Install the Database on the Management Server Node”</a>.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- The management server doesn't require a specific distribution for the MySQL node. You can use a distribution or Operating System of your choice. Using the same distribution as the management server is recommended, but not required. See <a class="xref" href="minimum-system-requirements.html#management-server-system-requirements">Section 4.3.1, “Management Server, Database, and Storage System Requirements”</a>.
- </div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Install MySQL from the package repository from your distribution:
- </div><pre class="programlisting">yum <span class="perl_BString">install</span> mysql-server</pre><pre class="programlisting">apt-get <span class="perl_BString">install</span> mysql-server</pre></li><li class="listitem"><div class="para">
- Edit the MySQL configuration (/etc/my.cnf or /etc/mysql/my.cnf, depending on your OS) and insert the following lines in the [mysqld] section. You can put these lines below the datadir line. The max_connections parameter should be set to 350 multiplied by the number of Management Servers you are deploying. This example assumes two Management Servers.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- On Ubuntu you can also create a file /etc/mysql/conf.d/cloudstack.cnf and add these directives there. Don't forget to add [mysqld] on the first line of the file.
- </div></div></div><pre class="programlisting">
-innodb_rollback_on_timeout=1
-innodb_lock_wait_timeout=600
-max_connections=700
-log-bin=mysql-bin
-binlog-format = 'ROW'
-bind-address = 0.0.0.0
-</pre></li><li class="listitem"><div class="para">
- On RHEL/CentOS MySQL doesn't start after installation, start it manually.
- </div><pre class="programlisting">service mysqld start</pre></li><li class="listitem"><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
- On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly recommended that you set a root password as a security precaution. Run the following commands, and substitute your own desired root password. This step is not required on Ubuntu as it asks for a root password during installation.
- </div></div></div><div class="para">
- Run this command to secure your installation. You can answer "Y" to all questions except to "Disallow root login remotely?". This is required to set up the databases.
- </div><pre class="programlisting">mysql_secure_installation</pre></li><li class="listitem"><div class="para">
- If a firewall is present on the system, open TCP port 3306 so external MySQL connections can be established.
- </div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
- On RHEL/CentOS:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Edit the /etc/sysconfig/iptables file and add the following line at the beginning of the INPUT chain.
- </div><pre class="programlisting">-A INPUT -p tcp --dport 3306 -j ACCEPT</pre></li><li class="listitem"><div class="para">
- Now reload the iptables rules.
- </div><pre class="programlisting">service iptables restart</pre></li></ol></div></li><li class="listitem"><div class="para">
- On Ubuntu:
- </div><div class="para">
- UFW is the default firewall on Ubuntu, open the port with this command:
- </div><pre class="programlisting">ufw allow mysql</pre></li></ol></div></li><li class="listitem"><div class="para">
- Set up the database. The following command creates the cloud user on the database.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- This command should be run on the first Management server node!
- </div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
- </div></li><li class="listitem"><div class="para">
- In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
- </div></li><li class="listitem"><div class="para">
- (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption.
- </div></li><li class="listitem"><div class="para">
- (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption.
- </div></li><li class="listitem"><div class="para">
- (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption.
- </div></li></ul></div><pre class="programlisting">cloud-setup-databases cloud:<span class="perl_Operator"><</span>dbpassword<span class="perl_Operator">></span>@<span class="perl_Operator"><</span>ip address mysql server<span class="perl_Operator">></span> \
- --deploy-as=root:<span class="perl_Operator"><</span>password<span class="perl_Operator">></span> \
- -e <span class="perl_Operator"><</span>encryption_type<span class="perl_Operator">></span> \
- -m <span class="perl_Operator"><</span>management_server_key<span class="perl_Operator">></span> \
- -k <span class="perl_Operator"><</span>database_key<span class="perl_Operator">></span></pre><div class="para">
- When this script is finished, you should see a message like “Successfully initialized the database.”
- </div></li></ol></div></div></div><div xml:lang="en-US" class="section" id="prepare-nfs-shares" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="prepare-nfs-shares">4.5.5. Prepare NFS Shares</h3></div></div></div><div class="para">
- CloudStack needs a place to keep primary and secondary storage (see Cloud Infrastructure Overview). Both of these can be NFS shares. This section tells how to set up the NFS shares before adding the storage to CloudStack.
- </div><div class="note"><div class="admonition_header"><h2>Alternative Storage</h2></div><div class="admonition"><div class="para">
- NFS is not the only option for primary or secondary storage. For example, you may use a Ceph RDB cluster, GlusterFS, iSCSI, and otthers.
- </div></div></div><div class="para">
- The requirements for primary and secondary storage are described in:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <a class="xref" href="about-primary-storage.html">Section 2.5, “About Primary Storage”</a>
- </div></li><li class="listitem"><div class="para">
- <a class="xref" href="about-secondary-storage.html">Section 2.6, “About Secondary Storage”</a>
- </div></li></ul></div><div class="para">
- A production installation typically uses a separate NFS server. See <a class="xref" href="management-server-install-flow.html#nfs-shares-on-separate-server">Section 4.5.5.1, “Using a Separate NFS Server”</a>.
- </div><div class="para">
- You can also use the Management Server node as the NFS server. This is more typical of a trial installation, but is technically possible in a larger deployment. See <a class="xref" href="management-server-install-flow.html#nfs-shares-on-management-server">Section 4.5.5.2, “Using the Management Server as the NFS Server”</a>.
- </div><div xml:lang="en-US" class="section" id="nfs-shares-on-separate-server" lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="nfs-shares-on-separate-server">4.5.5.1. Using a Separate NFS Server</h4></div></div></div><div class="para">
- This section tells how to set up NFS shares for secondary and (optionally) primary storage on an NFS server running on a separate node from the Management Server.
- </div><div class="para">
- The exact commands for the following steps may vary depending on your operating system version.
- </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
- (KVM only) Ensure that no volume is already mounted at your NFS mount point.
- </div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- On the storage server, create an NFS share for secondary storage and, if you are using NFS for primary storage as well, create a second NFS share. For example:
- </div><pre class="programlisting">
-# mkdir -p /export/primary
-# mkdir -p /export/secondary
-</pre></li><li class="listitem"><div class="para">
- To configure the new directories as NFS exports, edit /etc/exports. Export the NFS share(s) with rw,async,no_root_squash. For example:
- </div><pre class="programlisting"># vi /etc/exports</pre><div class="para">
- Insert the following line.
- </div><pre class="programlisting">/export *(rw,async,no_root_squash)</pre></li><li class="listitem"><div class="para">
- Export the /export directory.
- </div><pre class="programlisting"># exportfs -a</pre></li><li class="listitem"><div class="para">
- On the management server, create a mount point for secondary storage. For example:
- </div><pre class="programlisting"># mkdir -p /mnt/secondary</pre></li><li class="listitem"><div class="para">
- Mount the secondary storage on your Management Server. Replace the example NFS server name and NFS share paths below with your own.
- </div><pre class="programlisting"># mount -t nfs nfsservername:/nfs/share/secondary /mnt/secondary</pre></li></ol></div></div><div xml:lang="en-US" class="section" id="nfs-shares-on-management-server" lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="nfs-shares-on-management-server">4.5.5.2. Using the Management Server as the NFS Server</h4></div></div></div><div class="para">
- This section tells how to set up NFS shares for primary and secondary storage on the same node with the Management Server. This is more typical of a trial installation, but is technically possible in a larger deployment. It is assumed that you will have less than 16TB of storage on the host.
- </div><div class="para">
- The exact commands for the following steps may vary depending on your operating system version.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- On Ubuntu/Debian systems, you'll need to install the nfs-kernel-server package:
- </div><pre class="programlisting">
-$ sudo apt-get install nfs-kernel-server
-</pre></li><li class="listitem"><div class="para">
- On the Management Server host, create two directories that you will use for primary and secondary storage. For example:
- </div><pre class="programlisting">
-# mkdir -p /export/primary
-# mkdir -p /export/secondary
-</pre></li><li class="listitem"><div class="para">
- To configure the new directories as NFS exports, edit /etc/exports. Export the NFS share(s) with rw,async,no_root_squash. For example:
- </div><pre class="programlisting"># vi /etc/exports</pre><div class="para">
- Insert the following line.
- </div><pre class="programlisting">/export *(rw,async,no_root_squash)</pre></li><li class="listitem"><div class="para">
- Export the /export directory.
- </div><pre class="programlisting"># exportfs -a</pre></li><li class="listitem"><div class="para">
- Edit the /etc/sysconfig/nfs file.
- </div><pre class="programlisting"># vi /etc/sysconfig/nfs</pre><div class="para">
- Uncomment the following lines:
- </div><pre class="programlisting">
-LOCKD_TCPPORT=32803
-LOCKD_UDPPORT=32769
-MOUNTD_PORT=892
-RQUOTAD_PORT=875
-STATD_PORT=662
-STATD_OUTGOING_PORT=2020
-</pre></li><li class="listitem"><div class="para">
- Edit the /etc/sysconfig/iptables file.
- </div><pre class="programlisting"># vi /etc/sysconfig/iptables</pre><div class="para">
- Add the following lines at the beginning of the INPUT chain where <NETWORK> is the network that you'll be using:
- </div><pre class="programlisting">
--A INPUT -s <NETWORK> -m state --state NEW -p udp --dport 111 -j ACCEPT
--A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 111 -j ACCEPT
--A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 2049 -j ACCEPT
--A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 32803 -j ACCEPT
--A INPUT -s <NETWORK> -m state --state NEW -p udp --dport 32769 -j ACCEPT
--A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 892 -j ACCEPT
--A INPUT -s <NETWORK> -m state --state NEW -p udp --dport 892 -j ACCEPT
--A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 875 -j ACCEPT
--A INPUT -s <NETWORK> -m state --state NEW -p udp --dport 875 -j ACCEPT
--A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 662 -j ACCEPT
--A INPUT -s <NETWORK> -m state --state NEW -p udp --dport 662 -j ACCEPT
-</pre></li><li class="listitem"><div class="para">
- Run the following commands:
- </div><pre class="programlisting">
-# service iptables restart
-# service iptables save
-</pre></li><li class="listitem"><div class="para">
- If NFS v4 communication is used between client and server, add your domain to /etc/idmapd.conf on both the hypervisor host and Management Server.
- </div><pre class="programlisting"># vi /etc/idmapd.conf</pre><div class="para">
- Remove the character # from the beginning of the Domain line in idmapd.conf and replace the value in the file with your own domain. In the example below, the domain is company.com.
- </div><pre class="programlisting">Domain = company.com</pre></li><li class="listitem"><div class="para">
- Reboot the Management Server host.
- </div><div class="para">
- Two NFS shares called /export/primary and /export/secondary are now set up.
- </div></li><li class="listitem"><div class="para">
- It is recommended that you test to be sure the previous steps have been successful.
- </div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
- Log in to the hypervisor host.
- </div></li><li class="listitem"><div class="para">
- Be sure NFS and rpcbind are running. The commands might be different depending on your OS. For example:
- </div><pre class="programlisting">
-# service rpcbind start
-# service nfs start
-# chkconfig nfs on
-# chkconfig rpcbind on
-# reboot
-</pre></li><li class="listitem"><div class="para">
- Log back in to the hypervisor host and try to mount the /export directories. For example (substitute your own management server name):
- </div><pre class="programlisting">
-# mkdir /primarymount
-# mount -t nfs <management-server-name>:/export/primary /primarymount
-# umount /primarymount
-# mkdir /secondarymount
-# mount -t nfs <management-server-name>:/export/secondary /secondarymount
-# umount /secondarymount
-</pre></li></ol></div></li></ol></div></div></div><div xml:lang="en-US" class="section" id="install-management-server-multi-nodes" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="install-management-server-multi-nodes">4.5.6. Prepare and Start Additional Management Servers</h3></div></div></div><div class="para">
- For your second and subsequent Management Servers, you will install the Management Server software, connect it to the database, and set up the OS for the Management Server.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Perform the steps in <a class="xref" href="management-server-install-flow.html#prepare-os">Section 4.5.2, “Prepare the Operating System”</a> and <a class="xref" href="sect-source-buildrpm.html">Section 3.6, “Building RPMs”</a> or <a class="xref" href="sect-source-builddebs.html">Section 3.5, “Building DEB packages”</a> as appropriate.
- </div></li><li class="listitem"><div class="para">
- Download vhd-util from <a href="http://download.cloud.com.s3.amazonaws.com/tools/vhd-util">vhd-util</a>
- </div><div class="para">
- If the Management Server is RHEL or CentOS, copy vhd-util to /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver.
- </div><div class="para">
- If the Management Server is Ubuntu, copy vhd-util to /usr/lib/cloud/common/scripts/vm/hypervisor/xenserver/vhd-util.
- </div></li><li class="listitem"><div class="para">
- Ensure that necessary services are started and set to start on boot.
-<pre class="programlisting"><code class="prompt">#</code> <code class="command">service</code> rpcbind start
-<code class="prompt">#</code> <code class="command">service</code> nfs start
-<code class="prompt">#</code> <code class="command">chkconfig</code> nfs on
-<code class="prompt">#</code> <code class="command">chkconfig</code> rpcbind on</pre>
-
- </div></li><li class="listitem"><div class="para">
- Configure the database client. Note the absence of the --deploy-as argument in this case. (For more details about the arguments to this command, see <a class="xref" href="management-server-install-flow.html#management-server-install-db-external">Section 4.5.4.2, “Install the Database on a Separate Node”</a>.)
- </div><pre class="programlisting"><code class="prompt">#</code> <code class="command">cloud-setup-databases</code> cloud:<em class="replaceable"><code>dbpassword</code></em>@<em class="replaceable"><code>dbhost</code></em> -e <em class="replaceable"><code>encryption_type</code></em> -m <em class="replaceable"><code>management_server_key</code></em> -k <em class="replaceable"><code>database_key</code></em></pre></li><li class="listitem"><div class="para">
- Configure the OS and start the Management Server:
- </div><pre class="programlisting"><code class="prompt">#</code> <code class="command">cloud-setup-management</code></pre><div class="para">
- The Management Server on this node should now be running.
- </div></li><li class="listitem"><div class="para">
- Repeat these steps on each additional Management Server.
- </div></li><li class="listitem"><div class="para">
- Be sure to configure a load balancer for the Management Servers. See Management Server Load Balancing.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="prepare-system-vm-template" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="prepare-system-vm-template">4.5.7. Prepare the System VM Template</h3></div></div></div><div class="para">
- Secondary storage must be seeded with a template that is used for CloudStack system VMs.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text.
- </div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- On the Management Server, run one or more of the following cloud-install-sys-tmplt commands to retrieve and decompress the system VM template. Run the command for each hypervisor type that you expect end users to run in this Zone.
- </div><div class="para">
- If your secondary storage mount point is not named /mnt/secondary, substitute your own mount point name.
- </div><div class="para">
- If you set the CloudStack database encryption type to "web" when you set up the database, you must now add the parameter -s <management-server-secret-key>. See About Password and Key Encryption.
- </div><div class="para">
- This process will require approximately 5 GB of free space on the local file system and up to 30 minutes each time it runs.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- For XenServer:
- </div><pre class="programlisting"># /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2 -h xenserver -s <optional-management-server-secret-key> -F</pre></li><li class="listitem"><div class="para">
- For vSphere:
- </div><pre class="programlisting"># /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova -h vmware -s <optional-management-server-secret-key> -F</pre></li><li class="listitem"><div class="para">
- For KVM:
- </div><pre class="programlisting"># /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -s <optional-management-server-secret-key> -F</pre></li></ul></div></li><li class="listitem"><div class="para">
- If you are using a separate NFS server, perform this step. If you are using the Management Server as the NFS server, you MUST NOT perform this step.
- </div><div class="para">
- When the script has finished, unmount secondary storage and remove the created directory.
- </div><pre class="programlisting"># umount /mnt/secondary
-# rmdir /mnt/secondary</pre></li><li class="listitem"><div class="para">
- Repeat these steps for each secondary storage server.
- </div></li></ol></div></div><div xml:lang="en-US" class="section" id="installation-complete" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="installation-complete">4.5.8. Installation Complete! Next Steps</h3></div></div></div><div class="para">
- Congratulations! You have now installed CloudStack Management Server and the database it uses to persist system data.
- </div><div class="mediaobject"><img src="./images/installation-complete.png" width="444" alt="installation-complete.png: Finished installs with single Management Server and multiple Management Servers" /></div><div class="para">
- What should you do next?
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Even without adding any cloud infrastructure, you can run the UI to get a feel for what's offered and how you will interact with CloudStack on an ongoing basis. See Log In to the UI.
- </div></li><li class="listitem"><div class="para">
- When you're ready, add the cloud infrastructure and try running some virtual machines on it, so you can watch how CloudStack manages the infrastructure. See Provision Your Cloud Infrastructure.
- </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="configure-package-repository.html"><strong>Prev</strong>4.4. Configure package repository</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="ui.html"><strong>Next</strong>Chapter 5. User Interface</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/management-server-lb.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/management-server-lb.html b/docs/tmp/en-US/html/management-server-lb.html
deleted file mode 100644
index 53d4554..0000000
--- a/docs/tmp/en-US/html/management-server-lb.html
+++ /dev/null
@@ -1,71 +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.6. Setting Zone VLAN and Running VM Maximums</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="network-setup.html" title="Chapter 12. Network Setup" /><link rel="prev" href="hardware-firewall.html" title="12.5. Hardware Firewall" /><link rel="next" href="topology-req.html" title="12.7. Topology Requirements" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloud
stack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="hardware-firewall.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="topology-req.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="management-server-lb" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="management-server-lb">12.6. Setting Zone VLAN and Running VM Maximums</h2></div></div></div><div class="para">
- CloudStack can use a load balancer to provide a virtual IP for multiple Management Servers. The administrator is responsible for creating the load balancer rules for the Management Servers. The application requires persistence or stickiness across multiple sessions. The following chart lists the ports that should be load balanced and whether or not persistence is required.
- </div><div class="para">
- Even if persistence is not required, enabling it is permitted.
- </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><thead><tr><th align="left">
- <div class="para">
- Source Port
- </div>
- </th><th align="left">
- <div class="para">
- Destination Port
- </div>
- </th><th align="left">
- <div class="para">
- Protocol
- </div>
- </th><th align="left">
- <div class="para">
- Persistence Required?
- </div>
- </th></tr></thead><tbody><tr><td align="left">
- <div class="para">
- 80 or 443
- </div>
- </td><td align="left">
- <div class="para">
- 8080 (or 20400 with AJP)
- </div>
- </td><td align="left">
- <div class="para">
- HTTP (or AJP)
- </div>
- </td><td align="left">
- <div class="para">
- Yes
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- 8250
- </div>
- </td><td align="left">
- <div class="para">
- 8250
- </div>
- </td><td align="left">
- <div class="para">
- TCP
- </div>
- </td><td align="left">
- <div class="para">
- Yes
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- 8096
- </div>
- </td><td align="left">
- <div class="para">
- 8096
- </div>
- </td><td align="left">
- <div class="para">
- HTTP
- </div>
- </td><td align="left">
- <div class="para">
- No
- </div>
- </td></tr></tbody></table></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="hardware-firewall.html"><strong>Prev</strong>12.5. Hardware Firewall</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="topology-req.html"><strong>Next</strong>12.7. Topology Requirements</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/manual-live-migration.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/manual-live-migration.html b/docs/tmp/en-US/html/manual-live-migration.html
deleted file mode 100644
index 770659f..0000000
--- a/docs/tmp/en-US/html/manual-live-migration.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>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="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="changing-service-offering-for-vm.html" title="10.8. Changing the Service Offering for a VM" /><link rel="next" href="deleting-vms.html" title="10.10. Deleting VMs" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Si
te" /></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="changing-service-offering-for-vm.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="deleting-vms.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="manual-live-migration" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="manual-live-migration">10.9. Moving VMs Between Hosts (Manual Live Migration)</h2></div></div></div><div class="para">
- The CloudStack 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 CloudStack 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><ul class="docnav"><li class="previous"><a accesskey="p" href="changing-service-offering-for-vm.html"><strong>Prev</strong>10.8. Changing the Service Offering for a VM</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="deleting-vms.html"><strong>Next</strong>10.10. Deleting VMs</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/html/minimum-system-requirements.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/minimum-system-requirements.html b/docs/tmp/en-US/html/minimum-system-requirements.html
deleted file mode 100644
index 13a784e..0000000
--- a/docs/tmp/en-US/html/minimum-system-requirements.html
+++ /dev/null
@@ -1,53 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3. Minimum System Requirements</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.1-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="installation.html" title="Chapter 4. Installation" /><link rel="prev" href="installation-steps-overview.html" title="4.2. Overview of Installation Steps" /><link rel="next" href="configure-package-repository.html" title="4.4. Configure package repository" /></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="righ
t" 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="installation-steps-overview.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="configure-package-repository.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="minimum-system-requirements" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="minimum-system-requirements">4.3. Minimum System Requirements</h2></div></div></div><div class="section" id="management-server-system-requirements"><div class="titlepage"><div><div><h3 class="title" id="management-server-system-requirements">4.3.1. Management Server, Database, and Storage System Requirements</h3></div></div></div><div class="para">
- The machines that will run the Management Server and MySQL database must meet the following requirements. The same machines can also be used to provide primary and secondary storage, such as via localdisk or NFS. The Management Server may be placed on a virtual machine.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Operating system:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Preferred: CentOS/RHEL 6.3+ or Ubuntu 12.04(.1)
- </div></li></ul></div></li><li class="listitem"><div class="para">
- 64-bit x86 CPU (more cores results in better performance)
- </div></li><li class="listitem"><div class="para">
- 4 GB of memory
- </div></li><li class="listitem"><div class="para">
- 50 GB of local disk (When running secondary storage on the management server 500GB is recommended)
- </div></li><li class="listitem"><div class="para">
- At least 1 NIC
- </div></li><li class="listitem"><div class="para">
- Statically allocated IP address
- </div></li><li class="listitem"><div class="para">
- Fully qualified domain name as returned by the hostname command
- </div></li></ul></div></div><div class="section" id="hypervisor-system-requirements"><div class="titlepage"><div><div><h3 class="title" id="hypervisor-system-requirements">4.3.2. Host/Hypervisor System Requirements</h3></div></div></div><div class="para">
- The host is where the cloud services run in the form of guest virtual machines. Each host is one machine that meets the following requirements:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Must support HVM (Intel-VT or AMD-V enabled).
- </div></li><li class="listitem"><div class="para">
- 64-bit x86 CPU (more cores results in better performance)
- </div></li><li class="listitem"><div class="para">
- Hardware virtualization support required
- </div></li><li class="listitem"><div class="para">
- 4 GB of memory
- </div></li><li class="listitem"><div class="para">
- 36 GB of local disk
- </div></li><li class="listitem"><div class="para">
- At least 1 NIC
- </div></li><li class="listitem"><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
- If DHCP is used for hosts, ensure that no conflict occurs between DHCP server used for these hosts and the DHCP router created by CloudStack.
- </div></div></div></li><li class="listitem"><div class="para">
- Latest hotfixes applied to hypervisor software
- </div></li><li class="listitem"><div class="para">
- When you deploy CloudStack, the hypervisor host must not have any VMs already running
- </div></li><li class="listitem"><div class="para">
- All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags.
- </div></li></ul></div><div class="para">
- Hosts have additional requirements depending on the hypervisor. See the requirements listed at the top of the Installation section for your chosen hypervisor:
- </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
- Be sure you fulfill the additional hypervisor requirements and installation steps provided in this Guide. Hypervisor hosts must be properly prepared to work with CloudStack. For example, the requirements for XenServer are listed under Citrix XenServer Installation.
- </div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <a class="xref" href="hypervisor-kvm-install-flow.html#hypervisor-kvm-requirements">Section 8.1.1, “System Requirements for KVM Hypervisor Hosts”</a>
- </div></li><li class="listitem"><div class="para">
- <a class="xref" href="citrix-xenserver-installation.html#system-requirements-xenserver-hosts">Section 8.2.1, “System Requirements for XenServer Hosts”</a>
- </div></li><li class="listitem"><div class="para">
- <a class="xref" href="vmware-install.html#vmware-requirements">Section 8.3.1, “System Requirements for vSphere Hosts”</a>
- </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="installation-steps-overview.html"><strong>Prev</strong>4.2. Overview of Installation Steps</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="configure-package-repository.html"><strong>Next</strong>4.4. Configure package repository</a></li></ul></body></html>