You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by mu...@apache.org on 2012/12/06 09:09:12 UTC
[79/100] [abbrv] [partial] Revised en-US/network-setup.xml to include
the correct file.
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/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 374a39c..0000000
--- a/docs/tmp/en-US/html/management-server-install-flow.html
+++ /dev/null
@@ -1,329 +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.0-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="para">
- For primary storage, you can use iSCSI instead.
- </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">
- About Primary Storage
- </div></li><li class="listitem"><div class="para">
- About Secondary Storage
- </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 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/d8e31c7a/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 2853833..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 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><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/d8e31c7a/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 161269c..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.0-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>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/multi_node_management_server.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/multi_node_management_server.html b/docs/tmp/en-US/html/multi_node_management_server.html
deleted file mode 100644
index c0ea97a..0000000
--- a/docs/tmp/en-US/html/multi_node_management_server.html
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.4. Multi-Node Management Server</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="choosing-a-deployment_architecture.html" title="Chapter 9. Choosing a Deployment Architecture" /><link rel="prev" href="separate_storage_network.html" title="9.3. Separate Storage Network" /><link rel="next" href="multi_site_deployment.html" title="9.5. Multi-Site Deployment" /></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="separate_storage_network.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="multi_site_deployment.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="multi_node_management_server" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="multi_node_management_server">9.4. Multi-Node Management Server</h2></div></div></div><div class="para">
- The CloudStack Management Server is deployed on one or more front-end servers connected to a single MySQL database. Optionally a pair of hardware load balancers distributes requests from the web. A backup management server set may be deployed using MySQL replication at a remote site to add DR capabilities.
- </div><div class="mediaobject"><img src="./images/multi-node-management-server.png" width="444" alt="Multi-Node Management Server" /></div><div class="para">
- The administrator must decide the following.
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Whether or not load balancers will be used.
- </div></li><li class="listitem"><div class="para">
- How many Management Servers will be deployed.
- </div></li><li class="listitem"><div class="para">
- Whether MySQL replication will be deployed to enable disaster recovery.
- </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="separate_storage_network.html"><strong>Prev</strong>9.3. Separate Storage Network</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="multi_site_deployment.html"><strong>Next</strong>9.5. Multi-Site Deployment</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/multi_site_deployment.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/multi_site_deployment.html b/docs/tmp/en-US/html/multi_site_deployment.html
deleted file mode 100644
index d05e9ac..0000000
--- a/docs/tmp/en-US/html/multi_site_deployment.html
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5. Multi-Site Deployment</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Installation_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="choosing-a-deployment_architecture.html" title="Chapter 9. Choosing a Deployment Architecture" /><link rel="prev" href="multi_node_management_server.html" title="9.4. Multi-Node Management Server" /><link rel="next" href="aws-interface-compatibility.html" title="Chapter 10. Amazon Web Service Interface Compatibility" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/imag
es/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="multi_node_management_server.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="aws-interface-compatibility.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="multi_site_deployment" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="multi_site_deployment">9.5. Multi-Site Deployment</h2></div></div></div><div class="para">
- The CloudStack platform scales well into multiple sites through the use of zones. The following diagram shows an example of a multi-site deployment.
- </div><div class="mediaobject"><img src="./images/multi-site-deployment.png" width="444" alt="Example Of A Multi-Site Deployment" /></div><div class="para">
- Data Center 1 houses the primary Management Server as well as zone 1. The MySQL database is replicated in real time to the secondary Management Server installation in Data Center 2.
- </div><div class="mediaobject"><img src="./images/separate-storage-network.png" width="444" alt="Separate Storage Network" /></div><div class="para">
- This diagram illustrates a setup with a separate storage network. Each server has four NICs, two connected to pod-level network switches and two connected to storage network switches.
- </div><div class="para">
- There are two ways to configure the storage network:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Bonded NIC and redundant switches can be deployed for NFS. In NFS deployments, redundant switches and bonded NICs still result in one network (one CIDR block+ default gateway address).
- </div></li><li class="listitem"><div class="para">
- iSCSI can take advantage of two separate storage networks (two CIDR blocks each with its own default gateway). Multipath iSCSI client can failover and load balance between separate storage networks.
- </div></li></ul></div><div class="mediaobject"><img src="./images/nic-bonding-and-multipath-io.png" width="444" alt="NIC Bonding And Multipath I/O" /></div><div class="para">
- This diagram illustrates the differences between NIC bonding and Multipath I/O (MPIO). NIC bonding configuration involves only one network. MPIO involves two separate networks.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="multi_node_management_server.html"><strong>Prev</strong>9.4. Multi-Node Management Server</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="aws-interface-compatibility.html"><strong>Next</strong>Chapter 10. Amazon Web Service Interface Compatib...</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/multiple-system-vm-vmware.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/multiple-system-vm-vmware.html b/docs/tmp/en-US/html/multiple-system-vm-vmware.html
deleted file mode 100644
index 90e2609..0000000
--- a/docs/tmp/en-US/html/multiple-system-vm-vmware.html
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="working-with-system-vm.html" title="Chapter 16. Working with System Virtual Machines" /><link rel="prev" href="system-vm-template.html" title="16.1. The System VM Template" /><link rel="next" href="console-proxy.html" title="16.3. Console Proxy" /></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="system-vm-template.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="console-proxy.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="multiple-system-vm-vmware" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="multiple-system-vm-vmware">16.2. Multiple System VM Support for VMware</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="system-vm-template.html"><strong>Prev</strong>16.1. The System VM Template</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="console-proxy.html"><strong>Next</strong>16.3. Console Proxy</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/network-offerings.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/network-offerings.html b/docs/tmp/en-US/html/network-offerings.html
deleted file mode 100644
index 9c08a92..0000000
--- a/docs/tmp/en-US/html/network-offerings.html
+++ /dev/null
@@ -1,37 +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.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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="set-up-network-for-users.html" title="Chapter 9. Setting Up Networking for Users" /><link rel="prev" href="network-service-providers.html" title="9.3. Network Service Providers" /><link rel="next" href="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a clas
s="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="network-service-providers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="virtual-machines.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="network-offerings" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="network-offerings">9.4. Network Offerings</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="network-service-providers.html"><strong>Prev</strong>9.3. Network Service Providers</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="virtual-machines.html"><strong>Next</strong>Chapter 10. Working With Virtual Machines</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/network-service-providers.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/network-service-providers.html b/docs/tmp/en-US/html/network-service-providers.html
deleted file mode 100644
index 48b4b54..0000000
--- a/docs/tmp/en-US/html/network-service-providers.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>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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="set-up-network-for-users.html" title="Chapter 9. Setting Up Networking for Users" /><link rel="prev" href="about-virtual-networks.html" title="9.2. About Virtual Networks" /><link rel="next" href="network-offerings.html" title="9.4. Network Offerings" /></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="h
ttp://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="about-virtual-networks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="network-offerings.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="network-service-providers" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="network-service-providers">9.3. Network Service Providers</h2></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="idp21852344">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><ul class="docnav"><li class="previous"><a accesskey="p" href="about-virtual-networks.html"><strong>Prev</strong>9.2. About Virtual Networks</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="network-offerings.html"><strong>Next</strong>9.4. Network Offerings</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/networking-in-a-pod.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/networking-in-a-pod.html b/docs/tmp/en-US/html/networking-in-a-pod.html
deleted file mode 100644
index 726d5ba..0000000
--- a/docs/tmp/en-US/html/networking-in-a-pod.html
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="networks.html" title="Chapter 15. Managing Networks and Traffic" /><link rel="prev" href="guest-traffic.html" title="15.1. Guest Traffic" /><link rel="next" href="networking-in-a-zone.html" title="15.3. Networking in a Zone" /></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="guest-traffic.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="networking-in-a-zone.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="networking-in-a-pod" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="networking-in-a-pod">15.2. Networking in a Pod</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="guest-traffic.html"><strong>Prev</strong>15.1. Guest Traffic</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="networking-in-a-zone.html"><strong>Next</strong>15.3. Networking in a Zone</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/networking-in-a-zone.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/networking-in-a-zone.html b/docs/tmp/en-US/html/networking-in-a-zone.html
deleted file mode 100644
index cf10850..0000000
--- a/docs/tmp/en-US/html/networking-in-a-zone.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>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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="networks.html" title="Chapter 15. Managing Networks and Traffic" /><link rel="prev" href="networking-in-a-pod.html" title="15.2. Networking in a Pod" /><link rel="next" href="basic-zone-physical-network-configuration.html" title="15.4. Basic Zone Physical Network Configuration" /></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="networking-in-a-pod.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="basic-zone-physical-network-configuration.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="networking-in-a-zone" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="networking-in-a-zone">15.3. Networking in a Zone</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="networking-in-a-pod.html"><strong>Prev</strong>15.2. Networking in a Pod</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="basic-zone-physical-network-configuration.html"><strong>Next</strong>15.4. Basic Zone Physical Network Configuration</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/networks-for-users-overview.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/networks-for-users-overview.html b/docs/tmp/en-US/html/networks-for-users-overview.html
deleted file mode 100644
index 91cb3f1..0000000
--- a/docs/tmp/en-US/html/networks-for-users-overview.html
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.1. Overview of Setting Up Networking for Users</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="set-up-network-for-users.html" title="Chapter 9. Setting Up Networking for Users" /><link rel="prev" href="set-up-network-for-users.html" title="Chapter 9. Setting Up Networking for Users" /><link rel="next" href="about-virtual-networks.html" title="9.2. About Virtual Networks" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt
="Product Site" /></a><a class="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="set-up-network-for-users.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="about-virtual-networks.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="networks-for-users-overview" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="networks-for-users-overview">9.1. Overview of Setting Up Networking for Users</h2></div></div></div><div class="para">
- People using cloud infrastructure have a variety of needs and preferences when it comes to the networking services provided by the cloud. As a CloudStack administrator, you can do the following things to set up networking for your users:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- Set up physical networks in zones
- </div></li><li class="listitem"><div class="para">
- Set up several different providers for the same service on a single physical network (for example, both Cisco and Juniper firewalls)
- </div></li><li class="listitem"><div class="para">
- Bundle different types of network services into network offerings, so users can choose the desired network services for any given virtual machine
- </div></li><li class="listitem"><div class="para">
- Add new network offerings as time goes on so end users can upgrade to a better class of service on their network
- </div></li><li class="listitem"><div class="para">
- Provide more ways for a network to be accessed by a user, such as through a project of which the user is a member
- </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="set-up-network-for-users.html"><strong>Prev</strong>Chapter 9. Setting Up Networking for Users</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="about-virtual-networks.html"><strong>Next</strong>9.2. About Virtual Networks</a></li></ul></body></html>