incubator-cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ke4...@apache.org
Subject [10/29] cleaning up docs temp, publish directories - adding gitignore entries for them for the future
Date Mon, 19 Nov 2012 14:11:28 GMT
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/warning.svg
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/warning.svg b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/warning.svg
deleted file mode 100644
index 4231e5a..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/warning.svg
+++ /dev/null
@@ -1,130 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
-   xmlns:dc="http://purl.org/dc/elements/1.1/"
-   xmlns:cc="http://creativecommons.org/ns#"
-   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-   xmlns:svg="http://www.w3.org/2000/svg"
-   xmlns="http://www.w3.org/2000/svg"
-   xmlns:xlink="http://www.w3.org/1999/xlink"
-   xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
-   xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
-   version="1.0"
-   width="48"
-   height="48"
-   id="svg5921"
-   sodipodi:version="0.32"
-   inkscape:version="0.46"
-   sodipodi:docname="warning.svg"
-   inkscape:output_extension="org.inkscape.output.svg.inkscape">
-  <metadata
-     id="metadata11">
-    <rdf:RDF>
-      <cc:Work
-         rdf:about="">
-        <dc:format>image/svg+xml</dc:format>
-        <dc:type
-           rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
-      </cc:Work>
-    </rdf:RDF>
-  </metadata>
-  <sodipodi:namedview
-     inkscape:window-height="975"
-     inkscape:window-width="1680"
-     inkscape:pageshadow="2"
-     inkscape:pageopacity="0.0"
-     guidetolerance="10.0"
-     gridtolerance="10.0"
-     objecttolerance="10.0"
-     borderopacity="1.0"
-     bordercolor="#666666"
-     pagecolor="#ffffff"
-     id="base"
-     showgrid="false"
-     inkscape:zoom="1"
-     inkscape:cx="49.390126"
-     inkscape:cy="6.0062258"
-     inkscape:window-x="0"
-     inkscape:window-y="25"
-     inkscape:current-layer="svg5921" />
-  <defs
-     id="defs5923">
-    <linearGradient
-       inkscape:collect="always"
-       id="linearGradient2400">
-      <stop
-         style="stop-color:#fac521;stop-opacity:1;"
-         offset="0"
-         id="stop2402" />
-      <stop
-         style="stop-color:#fde7a3;stop-opacity:1"
-         offset="1"
-         id="stop2404" />
-    </linearGradient>
-    <inkscape:perspective
-       sodipodi:type="inkscape:persp3d"
-       inkscape:vp_x="0 : 20 : 1"
-       inkscape:vp_y="0 : 1000 : 0"
-       inkscape:vp_z="40 : 20 : 1"
-       inkscape:persp3d-origin="20 : 13.333333 : 1"
-       id="perspective13" />
-    <inkscape:perspective
-       id="perspective2396"
-       inkscape:persp3d-origin="24 : 16 : 1"
-       inkscape:vp_z="48 : 24 : 1"
-       inkscape:vp_y="0 : 1000 : 0"
-       inkscape:vp_x="0 : 24 : 1"
-       sodipodi:type="inkscape:persp3d" />
-    <inkscape:perspective
-       id="perspective2394"
-       inkscape:persp3d-origin="372.04724 : 350.78739 : 1"
-       inkscape:vp_z="744.09448 : 526.18109 : 1"
-       inkscape:vp_y="0 : 1000 : 0"
-       inkscape:vp_x="0 : 526.18109 : 1"
-       sodipodi:type="inkscape:persp3d" />
-    <linearGradient
-       inkscape:collect="always"
-       xlink:href="#linearGradient2400"
-       id="linearGradient2406"
-       x1="-2684.8242"
-       y1="1639.8413"
-       x2="-2684.8242"
-       y2="1587.1559"
-       gradientUnits="userSpaceOnUse" />
-  </defs>
-  <g
-     transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
-     id="layer1">
-    <g
-       transform="translate(2745.6887,-1555.5977)"
-       id="g8304"
-       style="enable-background:new" />
-  </g>
-  <g
-     id="g3189"
-     transform="matrix(1.2987724,0,0,1.2987724,-1.4964485,-1.8271549)">
-    <path
-       style="opacity:1;fill:#2e3436;fill-opacity:1;stroke:none;stroke-opacity:1;enable-background:new"
-       id="path8034"
-       transform="matrix(0.3735251,4.0822414e-3,-4.0822414e-3,0.3735251,605.96125,-374.33682)"
-       d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z" />
-    <path
-       style="opacity:1;fill:url(#linearGradient2406);fill-opacity:1;stroke:none;stroke-width:0.72954363000000000;stroke-opacity:1;enable-background:new"
-       id="path8036"
-       d="M -2723.6739,1596.2775 L -2704.5623,1577.1175 L -2677.5001,1577.0833 L -2658.3401,1596.1949 L -2658.3059,1623.257 L -2677.4175,1642.417 L -2704.4797,1642.4513 L -2723.6396,1623.3396 L -2723.6739,1596.2775 z"
-       transform="matrix(0.4536635,0,0,0.4536635,1240.4351,-710.40684)" />
-    <path
-       transform="translate(6.7837002e-6,-8.8630501e-6)"
-       id="path3178"
-       d="M 13.46875,5.0625 L 4.8125,13.78125 L 4.8125,16.625 L 13.46875,7.9375 L 25.75,7.90625 L 34.4375,16.59375 L 34.4375,13.71875 L 25.75,5.0625 L 13.46875,5.0625 z"
-       style="opacity:1;fill:#fde8a6;fill-opacity:1;stroke:none;stroke-width:0.72954363;stroke-opacity:1;enable-background:new" />
-    <path
-       id="path4412"
-       style="fill:#fef2cb;fill-opacity:1;stroke:#fef2cb;stroke-width:0.9430126;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:1"
-       d="M 23.308501,28.806303 C 23.308501,30.239154 22.087319,31.313792 20.231121,31.313792 L 20.198559,31.313792 C 18.358657,31.313792 17.121188,30.239154 17.121188,28.806303 C 17.121188,27.308327 18.391219,26.282537 20.231121,26.282537 C 22.054757,26.282537 23.27593,27.308327 23.308501,28.806303 z M 22.982851,24.507759 L 24.057489,11.351592 L 16.355915,11.351592 L 17.430553,24.507759 L 22.982851,24.507759 z" />
-    <path
-       id="path4414"
-       style="fill:#2e3436"
-       d="M 22.732962,27.86025 C 22.732962,29.293101 21.51178,30.36774 19.655592,30.36774 L 19.623029,30.36774 C 17.783118,30.36774 16.545659,29.293101 16.545659,27.86025 C 16.545659,26.362275 17.81568,25.336485 19.655592,25.336485 C 21.479218,25.336485 22.7004,26.362275 22.732962,27.86025 z M 22.407312,23.561697 L 23.48195,10.40553 L 15.780385,10.40553 L 16.855023,23.561697 L 22.407312,23.561697 z" />
-  </g>
-</svg>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/watermark-draft.png
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/watermark-draft.png b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/watermark-draft.png
deleted file mode 100644
index 0ead5af..0000000
Binary files a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/watermark-draft.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/yellow.png
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/yellow.png b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/yellow.png
deleted file mode 100644
index 223865d..0000000
Binary files a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/Common_Content/images/yellow.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/LDAPserver-for-user-authentication.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/LDAPserver-for-user-authentication.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/LDAPserver-for-user-authentication.html
deleted file mode 100644
index ab8de27..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/LDAPserver-for-user-authentication.html
+++ /dev/null
@@ -1,142 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. Using an LDAP Server for User Authentication</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-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="accounts.html" title="Chapter 3. Accounts" /><link rel="prev" href="accounts-users-domains.html" title="3.1. Accounts, Users, and Domains" /><link rel="next" href="user-services-overview.html" title="Chapter 4. User Services Overview" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="accounts-users-domains.html"><strong>Prev</strong></a></li><li class="next"><a accesskey
 ="n" href="user-services-overview.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="LDAPserver-for-user-authentication" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="LDAPserver-for-user-authentication">3.2. Using an LDAP Server for User Authentication</h2></div></div></div><div class="para">
-		You can use an external LDAP server such as Microsoft Active Directory or ApacheDS to authenticate CloudStack end-users. Just map CloudStack accounts to the corresponding LDAP accounts using a query filter. The query filter is written using the query syntax of the particular LDAP server, and can include special wildcard characters provided by CloudStack for matching common values such as the user’s email address and name. CloudStack will search the external LDAP directory tree starting at a specified base directory and return the distinguished name (DN) and password of the matching user. This information along with the given password is used to authenticate the user..
-	</div><div class="para">
-		To set up LDAP authentication in CloudStack, call the CloudStack API command ldapConfig and provide the following:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Hostname or IP address and listening port of the LDAP server
-			</div></li><li class="listitem"><div class="para">
-				Base directory and query filter
-			</div></li><li class="listitem"><div class="para">
-				Search user DN credentials, which give CloudStack permission to search on the LDAP server
-			</div></li><li class="listitem"><div class="para">
-				SSL keystore and password, if SSL is used
-			</div></li></ul></div><div xml:lang="en-US" class="section" id="example-LDAP-configuration-commands" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="example-LDAP-configuration-commands">3.2.1. Example LDAP Configuration Commands</h3></div></div></div><div class="para">
-		To understand the examples in this section, you need to know the basic concepts behind calling the CloudStack API, which are explained in the Developer’s Guide.
-	</div><div class="para">
-		The following shows an example invocation of ldapConfig with an ApacheDS LDAP server
-	</div><pre class="programlisting">http://127.0.0.1:8080/client/api?command=ldapConfig&amp;hostname=127.0.0.1&amp;searchbase=ou%3Dtesting%2Co%3Dproject&amp;queryfilter=%28%26%28uid%3D%25u%29%29&amp;binddn=cn%3DJohn+Singh%2Cou%3Dtesting%2Co%project&amp;bindpass=secret&amp;port=10389&amp;ssl=true&amp;truststore=C%3A%2Fcompany%2Finfo%2Ftrusted.ks&amp;truststorepass=secret&amp;response=json&amp;apiKey=YourAPIKey&amp;signature=YourSignatureHash</pre><div class="para">
-		The command must be URL-encoded. Here is the same example without the URL encoding:
-	</div><pre class="programlisting">http://127.0.0.1:8080/client/api?command=ldapConfig
-&amp;hostname=127.0.0.1
-&amp;searchbase=ou=testing,o=project
-&amp;queryfilter=(&amp;(%uid=%u))
-&amp;binddn=cn=John+Singh,ou=testing,o=project
-&amp;bindpass=secret
-&amp;port=10389
-&amp;ssl=true
-&amp;truststore=C:/company/info/trusted.ks
-&amp;truststorepass=secret
-&amp;response=json
-&amp;apiKey=YourAPIKey&amp;signature=YourSignatureHash
-</pre><div class="para">
-		The following shows a similar command for Active Directory. Here, the search base is the testing group within a company, and the users are matched up based on email address.
-	</div><pre class="programlisting">http://10.147.29.101:8080/client/api?command=ldapConfig&amp;hostname=10.147.28.250&amp;searchbase=OU%3Dtesting%2CDC%3Dcompany&amp;queryfilter=%28%26%28mail%3D%25e%29%29 &amp;binddn=CN%3DAdministrator%2COU%3Dtesting%2CDC%3Dcompany&amp;bindpass=1111_aaaa&amp;port=389&amp;response=json&amp;apiKey=YourAPIKey&amp;signature=YourSignatureHash</pre><div class="para">
-		The next few sections explain some of the concepts you will need to know when filling out the ldapConfig parameters.
-	</div></div><div xml:lang="en-US" class="section" id="search-base" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="search-base">3.2.2. Search Base</h3></div></div></div><div class="para">
-		An LDAP query is relative to a given node of the LDAP directory tree, called the search base. The search base is the distinguished name (DN) of a level of the directory tree below which all users can be found. The users can be in the immediate base directory or in some subdirectory. The search base may be equivalent to the organization, group, or domain name. The syntax for writing a DN varies depending on which LDAP server you are using. A full discussion of distinguished names is outside the scope of our documentation. The following table shows some examples of search bases to find users in the testing department..
-	</div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th align="left">
-						<div class="para">
-							LDAP Server
-						</div>
-					</th><th align="left">
-						<div class="para">
-							Example Search Base DN
-						</div>
-					</th></tr></thead><tbody><tr><td align="left">
-						<div class="para">
-							ApacheDS
-						</div>
-					</td><td align="left">
-						<div class="para">
-							ou=testing,o=project
-						</div>
-					</td></tr><tr><td align="left">
-						<div class="para">
-							Active Directory
-						</div>
-					</td><td align="left">
-						<div class="para">
-							OU=testing, DC=company
-						</div>
-					</td></tr></tbody></table></div></div><div xml:lang="en-US" class="section" id="query-filter" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="query-filter">3.2.3. Query Filter</h3></div></div></div><div class="para">
-		The query filter is used to find a mapped user in the external LDAP server. The query filter should uniquely map the CloudPlatform user to LDAP user for a meaningful authentication. For more information about query filter syntax, consult the documentation for your LDAP server.
-	</div><div class="para">
-		The CloudPlatform query filter wildcards are:
-	</div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th align="left">
-						<div class="para">
-							Query Filter Wildcard
-						</div>
-					</th><th align="left">
-						<div class="para">
-							Description
-						</div>
-					</th></tr></thead><tbody><tr><td align="left">
-						<div class="para">
-							%u
-						</div>
-					</td><td align="left">
-						<div class="para">
-							User name
-						</div>
-					</td></tr><tr><td align="left">
-						<div class="para">
-							%e
-						</div>
-					</td><td align="left">
-						<div class="para">
-							Email address
-						</div>
-					</td></tr><tr><td align="left">
-						<div class="para">
-							%n
-						</div>
-					</td><td align="left">
-						<div class="para">
-							First and last name
-						</div>
-					</td></tr></tbody></table></div><div class="para">
-		The following examples assume you are using Active Directory, and refer to user attributes from the Active Directory schema.
-	</div><div class="para">
-		If the CloudPlatform user name is the same as the LDAP user ID:
-	</div><pre class="programlisting">(uid=%u)</pre><div class="para">
-		If the CloudPlatform user name is the LDAP display name:
-	</div><pre class="programlisting">(displayName=%u)</pre><div class="para">
-		To find a user by email address:
-	</div><pre class="programlisting">(mail=%e)</pre></div><div xml:lang="en-US" class="section" id="search-user-bind-dn" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="search-user-bind-dn">3.2.4. Search User Bind DN</h3></div></div></div><div class="para">
-		The bind DN is the user on the external LDAP server permitted to search the LDAP directory within the defined search base. When the DN is returned, the DN and passed password are used to authenticate the CloudStack user with an LDAP bind. A full discussion of bind DNs is outside the scope of our documentation. The following table shows some examples of bind DNs.
-	</div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th align="left">
-						<div class="para">
-							LDAP Server
-						</div>
-					</th><th align="left">
-						<div class="para">
-							Example Bind DN
-						</div>
-					</th></tr></thead><tbody><tr><td align="left">
-						<div class="para">
-							ApacheDS
-						</div>
-					</td><td align="left">
-						<div class="para">
-							cn=Administrator,dc=testing,ou=project,ou=org
-						</div>
-					</td></tr><tr><td align="left">
-						<div class="para">
-							Active Directory
-						</div>
-					</td><td align="left">
-						<div class="para">
-							CN=Administrator, OU=testing, DC=company, DC=com
-						</div>
-					</td></tr></tbody></table></div></div><div xml:lang="en-US" class="section" id="SSL-keystore-path-and-password" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="SSL-keystore-path-and-password">3.2.5. SSL Keystore Path and Password</h3></div></div></div><div class="para">
-		If the LDAP server requires SSL, you need to enable it in the ldapConfig command by setting the parameters ssl, truststore, and truststorepass. Before enabling SSL for ldapConfig, you need to get the certificate which the LDAP server is using and add it to a trusted keystore. You will need to know the path to the keystore and the password.
-	</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="accounts-users-domains.html"><strong>Prev</strong>3.1. Accounts, Users, and Domains</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="user-services-overview.html"><strong>Next</strong>Chapter 4. User Services Overview</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-clusters.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-clusters.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-clusters.html
deleted file mode 100644
index 7298002..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-clusters.html
+++ /dev/null
@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3. About Clusters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-pods.html" title="2.2. About Pods" /><link rel="next" href="about-hosts.html" title="2.4. About Hosts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="about-pods.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="about-hosts.html">
 <strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-clusters" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-clusters">2.3. About Clusters</h2></div></div></div><div class="para">
-		A cluster provides a way to group hosts. To be precise, a cluster is a XenServer server pool, a set of KVM servers, , or a VMware cluster preconfigured in vCenter. The hosts in a cluster all have identical hardware, run the same hypervisor, are on the same subnet, and access the same shared primary storage. Virtual machine instances (VMs) can be live-migrated from one host to another within the same cluster, without interrupting service to the user.
-	</div><div class="para">
-		A cluster is the third-largest organizational unit within a CloudStack deployment. Clusters are contained within pods, and pods are contained within zones. Size of the cluster is limited by the underlying hypervisor, although the CloudStack recommends less in most cases; see Best Practices.
-	</div><div class="para">
-		A cluster consists of one or more hosts and one or more primary storage servers.
-	</div><div class="mediaobject"><img src="./images/cluster-overview.png" alt="cluster-overview.png: Structure of a simple cluster" /></div><div class="para">
-		CloudStack allows multiple clusters in a cloud deployment.
-	</div><div class="para">
-		Even when local storage is used exclusively, clusters are still required organizationally, even if there is just one host per cluster.
-	</div><div class="para">
-		When VMware is used, every VMware cluster is managed by a vCenter server. Administrator must register the vCenter server with CloudStack. There may be multiple vCenter servers per zone. Each vCenter server may manage multiple VMware clusters.
-	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-pods.html"><strong>Prev</strong>2.2. About Pods</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="about-hosts.html"><strong>Next</strong>2.4. About Hosts</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-hosts.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-hosts.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-hosts.html
deleted file mode 100644
index 1877840..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-hosts.html
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4. About Hosts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-clusters.html" title="2.3. About Clusters" /><link rel="next" href="about-primary-storage.html" title="2.5. About Primary Storage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="about-clusters.html"><strong>Prev</strong></a></li><li class="next"><a access
 key="n" href="about-primary-storage.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-hosts" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-hosts">2.4. About Hosts</h2></div></div></div><div class="para">
-		A host is a single computer. Hosts provide the computing resources that run the guest virtual machines. Each host has hypervisor software installed on it to manage the guest VMs. For example, a Linux KVM-enabled server, a Citrix XenServer server, and an ESXi server are hosts.
-	</div><div class="para">
-		The host is the smallest organizational unit within a CloudStack deployment. Hosts are contained within clusters, clusters are contained within pods, and pods are contained within zones.
-	</div><div class="para">
-		Hosts in a CloudStack deployment:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Provide the CPU, memory, storage, and networking resources needed to host the virtual machines
-			</div></li><li class="listitem"><div class="para">
-				Interconnect using a high bandwidth TCP/IP network and connect to the Internet
-			</div></li><li class="listitem"><div class="para">
-				May reside in multiple data centers across different geographic locations
-			</div></li><li class="listitem"><div class="para">
-				May have different capacities (different CPU speeds, different amounts of RAM, etc.), although the hosts within a cluster must all be homogeneous
-			</div></li></ul></div><div class="para">
-		Additional hosts can be added at any time to provide more capacity for guest VMs.
-	</div><div class="para">
-		CloudStack automatically detects the amount of CPU and memory resources provided by the Hosts.
-	</div><div class="para">
-		Hosts are not visible to the end user. An end user cannot determine which host their guest has been assigned to.
-	</div><div class="para">
-		For a host to function in CloudStack, you must do the following:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Install hypervisor software on the host
-			</div></li><li class="listitem"><div class="para">
-				Assign an IP address to the host
-			</div></li><li class="listitem"><div class="para">
-				Ensure the host is connected to the CloudStack Management Server
-			</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-clusters.html"><strong>Prev</strong>2.3. About Clusters</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="about-primary-storage.html"><strong>Next</strong>2.5. About Primary Storage</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-physical-networks.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-physical-networks.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-physical-networks.html
deleted file mode 100644
index a9d3b41..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-physical-networks.html
+++ /dev/null
@@ -1,100 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7. About Physical Networks</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-secondary-storage.html" title="2.6. About Secondary Storage" /><link rel="next" href="accounts.html" title="Chapter 3. Accounts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="about-secondary-storage.html"><strong>Prev</strong></a></li><li class="next"><
 a accesskey="n" href="accounts.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-physical-networks" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-physical-networks">2.7. About Physical Networks</h2></div></div></div><div class="para">
-		Part of adding a zone is setting up the physical network. One or (in an advanced zone) more physical networks can be associated with each zone. The network corresponds to a NIC on the hypervisor host. Each physical network can carry one or more types of network traffic. The choices of traffic type for each network vary depending on whether you are creating a zone with basic networking or advanced networking.
-	</div><div class="para">
-		A physical network is the actual network hardware and wiring in a zone. A zone can have multiple physical networks. An administrator can:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Add/Remove/Update physical networks in a zone
-			</div></li><li class="listitem"><div class="para">
-				Configure VLANs on the physical network
-			</div></li><li class="listitem"><div class="para">
-				Configure a name so the network can be recognized by hypervisors
-			</div></li><li class="listitem"><div class="para">
-				Configure the service providers (firewalls, load balancers, etc.) available on a physical network
-			</div></li><li class="listitem"><div class="para">
-				Configure the IP addresses trunked to a physical network
-			</div></li><li class="listitem"><div class="para">
-				Specify what type of traffic is carried on the physical network, as well as other properties like network speed
-			</div></li></ul></div><div xml:lang="en-US" class="section" id="physical-network-configuration-settings" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="physical-network-configuration-settings">2.7.1. Configurable Characteristics of Physical Networks</h3></div></div></div><div class="para">
-		CloudStack provides configuration settings you can use to set up a physical network in a zone, including:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				What type of network traffic it carries (guest, public, management, storage)
-			</div></li><li class="listitem"><div class="para">
-				VLANs
-			</div></li><li class="listitem"><div class="para">
-				Unique name that the hypervisor can use to find that particular network
-			</div></li><li class="listitem"><div class="para">
-				Enabled or disabled. When a network is first set up, it is disabled – not in use yet. The administrator sets the physical network to enabled, and it begins to be used. The administrator can later disable the network again, which prevents any new virtual networks from being created on that physical network; the existing network traffic continues even though the state is disabled.
-			</div></li><li class="listitem"><div class="para">
-				Speed
-			</div></li><li class="listitem"><div class="para">
-				Tags, so network offerings can be matched to physical networks
-			</div></li><li class="listitem"><div class="para">
-				Isolation method
-			</div></li></ul></div></div><div xml:lang="en-US" class="section" id="basic-zone-network-traffic-types" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="basic-zone-network-traffic-types">2.7.2. Basic Zone Network Traffic Types</h3></div></div></div><div class="para">
-		When basic networking is used, there can be only one physical network in the zone. That physical network carries the following traffic types:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Guest. When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. Each pod in a basic zone is a broadcast domain, and therefore each pod has a different IP range for the guest network. The administrator must configure the IP range for each pod.
-			</div></li><li class="listitem"><div class="para">
-				Management. When CloudStack’s internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use.
-			</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
-					We strongly recommend the use of separate NICs for management traffic and guest traffic.
-				</div></div></div></li><li class="listitem"><div class="para">
-				Public. Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in Acquiring a New IP Address.
-			</div></li><li class="listitem"><div class="para">
-				Storage. Traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudStack uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network.
-			</div></li></ul></div><div class="para">
-		In a basic network, configuring the physical network is fairly straightforward. In most cases, you only need to configure one guest network to carry traffic that is generated by guest VMs. If you use a NetScaler load balancer and enable its elastic IP and elastic load balancing (EIP and ELB) features, you must also configure a network to carry public traffic. CloudStack takes care of presenting the necessary network configuration steps to you in the UI when you add a new zone.
-	</div></div><div xml:lang="en-US" class="section" id="basic-zone-guest-ip-addresses" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="basic-zone-guest-ip-addresses">2.7.3. Basic Zone Guest IP Addresses</h3></div></div></div><div class="para">
-		When basic networking is used, CloudPlatform will assign IP addresses in the CIDR of the pod to the guests in that pod. The administrator must add a Direct IP range on the pod for this purpose. These IPs are in the same VLAN as the hosts.
-	</div></div><div xml:lang="en-US" class="section" id="advanced-zone-network-traffic-types" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="advanced-zone-network-traffic-types">2.7.4. Advanced Zone Network Traffic Types</h3></div></div></div><div class="para">
-		When advanced networking is used, there can be multiple physical networks in the zone. Each physical network can carry one or more traffic types, and you need to let CloudStack know which type of network traffic you want each network to carry. The traffic types in an advanced zone are:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Guest. When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. This network can be isolated or shared. In an isolated guest network, the administrator needs to reserve VLAN ranges to provide isolation for each CloudStack account’s network (potentially a large number of VLANs). In a shared guest network, all guest VMs share a single network.
-			</div></li><li class="listitem"><div class="para">
-				Management. When CloudStack’s internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use.
-			</div></li><li class="listitem"><div class="para">
-				Public. Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in “Acquiring a New IP Address” in the Administration Guide.
-			</div></li><li class="listitem"><div class="para">
-				Storage. Traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudStack uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network.
-			</div></li></ul></div><div class="para">
-		These traffic types can each be on a separate physical network, or they can be combined with certain restrictions. When you use the Add Zone wizard in the UI to create a new zone, you are guided into making only valid choices.
-	</div></div><div xml:lang="en-US" class="section" id="advanced-zone-guest-ip-addresses" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="advanced-zone-guest-ip-addresses">2.7.5. Advanced Zone Guest IP Addresses</h3></div></div></div><div class="para">
-		When advanced networking is used, the administrator can create additional networks for use by the guests. These networks can span the zone and be available to all accounts, or they can be scoped to a single account, in which case only the named account may create guests that attach to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The administrator may provision thousands of these networks if desired.
-	</div></div><div xml:lang="en-US" class="section" id="advanced-zone-public-ip-addresses" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="advanced-zone-public-ip-addresses">2.7.6. Advanced Zone Public IP Addresses</h3></div></div></div><div class="para">
-		When advanced networking is used, the administrator can create additional networks for use by the guests. These networks can span the zone and be available to all accounts, or they can be scoped to a single account, in which case only the named account may create guests that attach to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The administrator may provision thousands of these networks if desired.
-	</div></div><div xml:lang="en-US" class="section" id="system-reserved-ip-addresses" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="system-reserved-ip-addresses">2.7.7. System Reserved IP Addresses</h3></div></div></div><div class="para">
-		In each zone, you need to configure a range of reserved IP addresses for the management network. This network carries communication between the CloudStack Management Server and various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP.
-	</div><div class="para">
-		The reserved IP addresses must be unique across the cloud. You cannot, for example, have a host in one zone which has the same private IP address as a host in another zone.
-	</div><div class="para">
-		The hosts in a pod are assigned private IP addresses. These are typically RFC1918 addresses. The Console Proxy and Secondary Storage system VMs are also allocated private IP addresses in the CIDR of the pod that they are created in.
-	</div><div class="para">
-		Make sure computing servers and Management Servers use IP addresses outside of the System Reserved IP range. For example, suppose the System Reserved IP range starts at 192.168.154.2 and ends at 192.168.154.7. CloudStack can use .2 to .7 for System VMs. This leaves the rest of the pod CIDR, from .8 to .254, for the Management Server and hypervisor hosts.
-	</div><div class="para">
-		<span class="bold bold"><strong>In all zones:</strong></span>
-	</div><div class="para">
-		Provide private IPs for the system in each pod and provision them in CloudStack.
-	</div><div class="para">
-		For KVM and XenServer, the recommended number of private IPs per pod is one per host. If you expect a pod to grow, add enough private IPs now to accommodate the growth.
-	</div><div class="para">
-		<span class="bold bold"><strong>In a zone that uses advanced networking:</strong></span>
-	</div><div class="para">
-		For zones with advanced networking, we recommend provisioning enough private IPs for your total number of customers, plus enough for the required CloudStack System VMs. Typically, about 10 additional IPs are required for the System VMs. For more information about System VMs, see Working with System Virtual Machines in the Administrator's Guide.
-	</div><div class="para">
-		When advanced networking is being used, the number of private IP addresses available in each pod varies depending on which hypervisor is running on the nodes in that pod. Citrix XenServer and KVM use link-local addresses, which in theory provide more than 65,000 private IP addresses within the address block. As the pod grows over time, this should be more than enough for any reasonable number of hosts as well as IP addresses for guest virtual routers. VMWare ESXi, by contrast uses any administrator-specified subnetting scheme, and the typical administrator provides only 255 IPs per pod. Since these are shared by physical machines, the guest virtual router, and other entities, it is possible to run out of private IPs when scaling up a pod whose nodes are running ESXi.
-	</div><div class="para">
-		To ensure adequate headroom to scale private IP space in an ESXi pod that uses advanced networking, use one or both of the following techniques:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Specify a larger CIDR block for the subnet. A subnet mask with a /20 suffix will provide more than 4,000 IP addresses.
-			</div></li><li class="listitem"><div class="para">
-				Create multiple pods, each with its own subnet. For example, if you create 10 pods and each pod has 255 IPs, this will provide 2,550 IP addresses.
-			</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-secondary-storage.html"><strong>Prev</strong>2.6. About Secondary Storage</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="accounts.html"><strong>Next</strong>Chapter 3. Accounts</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-pods.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-pods.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-pods.html
deleted file mode 100644
index 1bf6dcb..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-pods.html
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. About Pods</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-zones.html" title="2.1. About Zones" /><link rel="next" href="about-clusters.html" title="2.3. About Clusters" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="about-zones.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="about-clu
 sters.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-pods" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-pods">2.2. About Pods</h2></div></div></div><div class="para">
-		A pod often represents a single rack. Hosts in the same pod are in the same subnet.
-	</div><div class="para">
-		A pod is the second-largest organizational unit within a CloudStack deployment. Pods are contained within zones. Each zone can contain one or more pods.
-	</div><div class="para">
-		Pods are not visible to the end user.
-	</div><div class="para">
-		A pod consists of one or more clusters of hosts and one or more primary storage servers.
-	</div><div class="mediaobject"><img src="./images/pod-overview.png" alt="pod-overview.png: Nested structure of a simple pod" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-zones.html"><strong>Prev</strong>2.1. About Zones</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="about-clusters.html"><strong>Next</strong>2.3. About Clusters</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-primary-storage.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-primary-storage.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-primary-storage.html
deleted file mode 100644
index b18f6e7..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-primary-storage.html
+++ /dev/null
@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5. About Primary Storage</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-hosts.html" title="2.4. About Hosts" /><link rel="next" href="about-secondary-storage.html" title="2.6. About Secondary Storage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="about-hosts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="
 n" href="about-secondary-storage.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-primary-storage" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-primary-storage">2.5. About Primary Storage</h2></div></div></div><div class="para">
-		Primary storage is associated with a cluster, and it stores the disk volumes for all the VMs running on hosts in that cluster. You can add multiple primary storage servers to a cluster. At least one is required. It is typically located close to the hosts for increased performance.
-	</div><div class="para">
-		CloudStack is designed to work with all standards-compliant iSCSI and NFS servers that are supported by the underlying hypervisor, including, for example:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Dell EqualLogic™ for iSCSI
-			</div></li><li class="listitem"><div class="para">
-				Network Appliances filers for NFS and iSCSI
-			</div></li><li class="listitem"><div class="para">
-				Scale Computing for NFS
-			</div></li></ul></div><div class="para">
-		If you intend to use only local disk for your installation, you can skip to Add Secondary Storage.
-	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-hosts.html"><strong>Prev</strong>2.4. About Hosts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="about-secondary-storage.html"><strong>Next</strong>2.6. About Secondary Storage</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-secondary-storage.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-secondary-storage.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-secondary-storage.html
deleted file mode 100644
index edb4cc0..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-secondary-storage.html
+++ /dev/null
@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6. About Secondary Storage</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="about-primary-storage.html" title="2.5. About Primary Storage" /><link rel="next" href="about-physical-networks.html" title="2.7. About Physical Networks" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="about-primary-storage.html"><strong>Prev</strong></a></li><
 li class="next"><a accesskey="n" href="about-physical-networks.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-secondary-storage" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-secondary-storage">2.6. About Secondary Storage</h2></div></div></div><div class="para">
-		Secondary storage is associated with a zone, and it stores the following:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Templates — OS images that can be used to boot VMs and can include additional configuration information, such as installed applications
-			</div></li><li class="listitem"><div class="para">
-				ISO images — disc images containing data or bootable media for operating systems
-			</div></li><li class="listitem"><div class="para">
-				Disk volume snapshots — saved copies of VM data which can be used for data recovery or to create new templates
-			</div></li></ul></div><div class="para">
-		The items in zone-based NFS secondary storage are available to all hosts in the zone. CloudStack manages the allocation of guest virtual disks to particular primary storage devices.
-	</div><div class="para">
-		To make items in secondary storage available to all hosts throughout the cloud, you can add OpenStack Object Storage (Swift, <a href="http://swift.openstack.org">swift.openstack.org</a>) in addition to the zone-based NFS secondary storage. When using Swift, you configure Swift storage for the entire CloudStack, then set up NFS secondary storage for each zone as usual. The NFS storage in each zone acts as a staging area through which all templates and other secondary storage data pass before being forwarded to Swift. The Swift storage acts as a cloud-wide resource, making templates and other data available to any zone in the cloud. There is no hierarchy in the Swift storage, just one Swift container per storage object. Any secondary storage in the whole cloud can pull a container from Swift at need. It is not necessary to copy templates and snapshots from one zone to another, as would be required when using zone NFS alone. Everything is available everywhere.
-	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="about-primary-storage.html"><strong>Prev</strong>2.5. About Primary Storage</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="about-physical-networks.html"><strong>Next</strong>2.7. About Physical Networks</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-virtual-networks.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-virtual-networks.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-virtual-networks.html
deleted file mode 100644
index bc4be2b..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-virtual-networks.html
+++ /dev/null
@@ -1,34 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2. About Virtual Networks</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="set-up-network-for-users.html" title="Chapter 9. Setting Up Networking for Users" /><link rel="prev" href="networks-for-users-overview.html" title="9.1. Overview of Setting Up Networking for Users" /><link rel="next" href="network-service-providers.html" title="9.3. Network Service Providers" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="networks-for-users-overview.ht
 ml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="network-service-providers.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-virtual-networks" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-virtual-networks">9.2. About Virtual Networks</h2></div></div></div><div class="para">
-		A virtual network is a logical construct that enables multi-tenancy on a single physical network. In CloudStack a virtual network can be shared or isolated.
-	</div><div xml:lang="en-US" class="section" id="isolated-networks" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="isolated-networks">9.2.1. Isolated Networks</h3></div></div></div><div class="para">
-		An isolated network can be accessed only by virtual machines of a single account. Isolated networks have the following properties.
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Resources such as VLAN are allocated and garbage collected dynamically
-			</div></li><li class="listitem"><div class="para">
-				There is one network offering for the entire network
-			</div></li><li class="listitem"><div class="para">
-				The network offering can be upgraded or downgraded but it is for the entire network
-			</div></li></ul></div></div><div xml:lang="en-US" class="section" id="shared-networks" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="shared-networks">9.2.2. Shared Networks</h3></div></div></div><div class="para">
-		A shared network can be accessed by virtual machines that belong to many different accounts. Network Isolation on shared networks is accomplished using techniques such as security groups (supported only in basic zones in CloudStack 3.0.3).
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Shared Networks are created by the administrator
-			</div></li><li class="listitem"><div class="para">
-				Shared Networks can be designated to a certain domain
-			</div></li><li class="listitem"><div class="para">
-				Shared Network resources such as VLAN and physical network that it maps to are designated by the administrator
-			</div></li><li class="listitem"><div class="para">
-				Shared Networks are isolated by security groups
-			</div></li><li class="listitem"><div class="para">
-				Public Network is a shared network that is not shown to the end users
-			</div></li></ul></div></div><div xml:lang="en-US" class="section" id="runtime-allocation-virtual-network-resources" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="runtime-allocation-virtual-network-resources">9.2.3. Runtime Allocation of Virtual Network Resources</h3></div></div></div><div class="para">
-		When you define a new virtual network, all your settings for that network are stored in CloudStack. The actual network resources are activated only when the first virtual machine starts in the network. When all virtual machines have left the virtual network, the network resources are garbage collected so they can be allocated again. This helps to conserve network resources..
-	</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="networks-for-users-overview.html"><strong>Prev</strong>9.1. Overview of Setting Up Networking for Users</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="network-service-providers.html"><strong>Next</strong>9.3. Network Service Providers</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-working-with-vms.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-working-with-vms.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-working-with-vms.html
deleted file mode 100644
index 6e1a477..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-working-with-vms.html
+++ /dev/null
@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.1. About Working with Virtual Machines</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /><link rel="prev" href="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /><link rel="next" href="best-practices-vm.html" title="10.2. Best Practices for Virtual Machines" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="virtual-machines.html"><strong>Prev</strong></a></li>
 <li class="next"><a accesskey="n" href="best-practices-vm.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-working-with-vms" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-working-with-vms">10.1. About Working with Virtual Machines</h2></div></div></div><div class="para">
-		CloudStack provides administrators with complete control over the lifecycle of all guest VMs executing in the cloud. CloudStack provides several guest management operations for end users and administrators. VMs may be stopped, started, rebooted, and destroyed.
-	</div><div class="para">
-		Guest VMs have a name and group. VM names and groups are opaque to CloudStack and are available for end users to organize their VMs. Each VM can have three names for use in different contexts. Only two of these names can be controlled by the user:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Instance name – a unique, immutable ID that is generated by CloudStack and can not be modified by the user. This name conforms to the requirements in IETF RFC 1123.
-			</div></li><li class="listitem"><div class="para">
-				Display name – the name displayed in the CloudStack web UI. Can be set by the user. Defaults to instance name.
-			</div></li><li class="listitem"><div class="para">
-				Name – host name that the DHCP server assigns to the VM. Can be set by the user. Defaults to instance name
-			</div></li></ul></div><div class="para">
-		Guest VMs can be configured to be Highly Available (HA). An HA-enabled VM is monitored by the system. If the system detects that the VM is down, it will attempt to restart the VM, possibly on a different host. For more information, see HA-Enabled Virtual Machines on
-	</div><div class="para">
-		Each new VM is allocated one public IP address. When the VM is started, CloudStack automatically creates a static NAT between this public IP address and the private IP address of the VM.
-	</div><div class="para">
-		If elastic IP is in use (with the NetScaler load balancer), the IP address initially allocated to the new VM is not marked as elastic. The user must replace the automatically configured IP with a specifically acquired elastic IP, and set up the static NAT mapping between this new IP and the guest VM’s private IP. The VM’s original IP address is then released and returned to the pool of available public IPs.
-	</div><div class="para">
-		CloudStack cannot distinguish a guest VM that was shut down by the user (such as with the “shutdown” command in Linux) from a VM that shut down unexpectedly. If an HA-enabled VM is shut down from inside the VM, CloudStack will restart it. To shut down an HA-enabled VM, you must go through the CloudStack UI or API.
-	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="virtual-machines.html"><strong>Prev</strong>Chapter 10. Working With Virtual Machines</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="best-practices-vm.html"><strong>Next</strong>10.2. Best Practices for Virtual Machines</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-zones.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-zones.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-zones.html
deleted file mode 100644
index e26862e..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/about-zones.html
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.1. About Zones</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="next" href="about-pods.html" title="2.2. About Pods" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="cloud-infrastructure-concepts.html"><strong>Prev</strong></a><
 /li><li class="next"><a accesskey="n" href="about-pods.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-zones" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-zones">2.1. About Zones</h2></div></div></div><div class="para">
-		A zone is the largest organizational unit within a CloudStack deployment. A zone typically corresponds to a single datacenter, although it is permissible to have multiple zones in a datacenter. The benefit of organizing infrastructure into zones is to provide physical isolation and redundancy. For example, each zone can have its own power supply and network uplink, and the zones can be widely separated geographically (though this is not required).
-	</div><div class="para">
-		A zone consists of:
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				One or more pods. Each pod contains one or more clusters of hosts and one or more primary storage servers.
-			</div></li><li class="listitem"><div class="para">
-				Secondary storage, which is shared by all the pods in the zone.
-			</div></li></ul></div><div class="mediaobject"><img src="./images/zone-overview.png" width="444" alt="zone-overview.png: Nested structure of a simple zone" /></div><div class="para">
-		Zones are visible to the end user. When a user starts a guest VM, the user must select a zone for their guest. Users might also be required to copy their private templates to additional zones to enable creation of guest VMs using their templates in those zones.
-	</div><div class="para">
-		Zones can be public or private. Public zones are visible to all users. This means that any user may create a guest in that zone. Private zones are reserved for a specific domain. Only users in that domain or its subdomains may create guests in that zone.
-	</div><div class="para">
-		Hosts in the same zone are directly accessible to each other without having to go through a firewall. Hosts in different zones can access each other through statically configured VPN tunnels.
-	</div><div class="para">
-		For each zone, the administrator must decide the following.
-	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				How many pods to place in a zone.
-			</div></li><li class="listitem"><div class="para">
-				How many clusters to place in each pod.
-			</div></li><li class="listitem"><div class="para">
-				How many hosts to place in each cluster.
-			</div></li><li class="listitem"><div class="para">
-				How many primary storage servers to place in each cluster and total capacity for the storage servers.
-			</div></li><li class="listitem"><div class="para">
-				How much secondary storage to deploy in a zone.
-			</div></li></ul></div><div class="para">
-		When you add a new zone, you will be prompted to configure the zone’s physical network and add the first pod, cluster, host, primary storage, and secondary storage.
-	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="cloud-infrastructure-concepts.html"><strong>Prev</strong>Chapter 2. Cloud Infrastructure Concepts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="about-pods.html"><strong>Next</strong>2.2. About Pods</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/accept-membership-invite.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/accept-membership-invite.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/accept-membership-invite.html
deleted file mode 100644
index 2627d41..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/accept-membership-invite.html
+++ /dev/null
@@ -1,24 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.5. Accepting a Membership Invitation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="projects.html" title="Chapter 6. Using Projects to Organize Users and Resources" /><link rel="prev" href="add-members-to-projects.html" title="6.4. Adding Members to a Project" /><link rel="next" href="suspend-project.html" title="6.6. Suspending or Deleting a Project" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="add-members-to-projects.html"><strong>Prev</strong></a
 ></li><li class="next"><a accesskey="n" href="suspend-project.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="accept-membership-invite" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="accept-membership-invite">6.5. Accepting a Membership Invitation</h2></div></div></div><div class="para">
-		If you have received an invitation to join a CloudStack project, and you want to accept the invitation, follow these steps:
-	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-				Log in to the CloudStack UI.
-			</div></li><li class="listitem"><div class="para">
-				In the left navigation, click Projects.
-			</div></li><li class="listitem"><div class="para">
-				In Select View, choose Invitations.
-			</div></li><li class="listitem"><div class="para">
-				If you see the invitation listed onscreen, click the Accept button.
-			</div><div class="para">
-				Invitations listed on screen were sent to you using your CloudStack account name.
-			</div></li><li class="listitem"><div class="para">
-				If you received an email invitation, click the Enter Token button, and provide the project ID and unique ID code (token) from the email.
-			</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="add-members-to-projects.html"><strong>Prev</strong>6.4. Adding Members to a Project</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="suspend-project.html"><strong>Next</strong>6.6. Suspending or Deleting a Project</a></li></ul></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35666a52/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/accessing-vms.html
----------------------------------------------------------------------
diff --git a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/accessing-vms.html b/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/accessing-vms.html
deleted file mode 100644
index 97a3a10..0000000
--- a/docs/publish/en-US/Apache_CloudStack/4.0.0-incubating/html/Admin_Guide/accessing-vms.html
+++ /dev/null
@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.5. Accessing VMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
-              addID('Apache_CloudStack');
-              
-	      addID('Apache_CloudStack.4.0.0-incubating');
-              
-              addID('Apache_CloudStack.4.0.0-incubating.books');
-	      addID('Apache_CloudStack.4.0.0-incubating.Admin_Guide');
-              </script><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /><link rel="prev" href="creating-vms.html" title="10.4. Creating VMs" /><link rel="next" href="stopping-and-starting-vms.html" title="10.6. Stopping and Starting VMs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="creating-vms.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" 
 href="stopping-and-starting-vms.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="accessing-vms" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="accessing-vms">10.5. Accessing VMs</h2></div></div></div><div class="para">
-		Any user can access their own virtual machines. The administrator can access all VMs running in the cloud.
-	</div><div class="para">
-		To access a VM through the CloudStack UI:
-	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-				Log in to the CloudStack UI as a user or admin.
-			</div></li><li class="listitem"><div class="para">
-				Click Instances, then click the name of a running VM.
-			</div></li><li class="listitem"><div class="para">
-				Click the View Console button <img src="images/icon.png" />.
-			</div></li></ol></div><div class="para">
-		To access a VM directly over the network:
-	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-				The VM must have some port open to incoming traffic. For example, in a basic zone, a new VM might be assigned to a security group which allows incoming traffic. This depends on what security group you picked when creating the VM. In other cases, you can open a port by setting up a port forwarding policy. See IP Forwarding and Firewalling.
-			</div></li><li class="listitem"><div class="para">
-				If a port is open but you can not access the VM using ssh, it’s possible that ssh is not already enabled on the VM. This will depend on whether ssh is enabled in the template you picked when creating the VM. Access the VM through the CloudStack UI and enable ssh on the machine using the commands for the VM’s operating system.
-			</div></li><li class="listitem"><div class="para">
-				If the network has an external firewall device, you will need to create a firewall rule to allow access. See IP Forwarding and Firewalling.
-			</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="creating-vms.html"><strong>Prev</strong>10.4. Creating VMs</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="stopping-and-starting-vms.html"><strong>Next</strong>10.6. Stopping and Starting VMs</a></li></ul></body></html>


Mime
View raw message