cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject git commit: refs/heads/4.0 - CLOUDSTACK-1110: Adding missing load balancing docs.
Date Thu, 07 Mar 2013 03:06:49 GMT
Updated Branches:
  refs/heads/4.0 a02844b20 -> 5f6cffc60


CLOUDSTACK-1110: Adding missing load balancing docs.


Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/5f6cffc6
Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/5f6cffc6
Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/5f6cffc6

Branch: refs/heads/4.0
Commit: 5f6cffc60b8855d8b0fc1bb0be50ffdc995304c6
Parents: a02844b
Author: Joe Brockmeier <jzb@zonker.net>
Authored: Wed Mar 6 21:06:29 2013 -0600
Committer: Joe Brockmeier <jzb@zonker.net>
Committed: Wed Mar 6 21:06:29 2013 -0600

----------------------------------------------------------------------
 .../en-US/management-server-install-multi-node.xml |    3 +-
 docs/en-US/management-server-lb.xml                |   47 ++++++++++++++-
 docs/en-US/networks.xml                            |    3 +-
 3 files changed, 48 insertions(+), 5 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/5f6cffc6/docs/en-US/management-server-install-multi-node.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/management-server-install-multi-node.xml b/docs/en-US/management-server-install-multi-node.xml
index 1764fa9..6e2d920 100644
--- a/docs/en-US/management-server-install-multi-node.xml
+++ b/docs/en-US/management-server-install-multi-node.xml
@@ -62,8 +62,7 @@ linkend="sect-source-buildrpm"/> or <xref linkend="sect-source-builddebs"/>
as
       <para>Repeat these steps on each additional Management Server. </para>
     </listitem>
     <listitem>
-      <para>Be sure to configure a load balancer for the Management Servers. See Management
Server
-        Load Balancing.</para>
+        <para>Be sure to configure a load balancer for the Management Servers. See
<xref linkend="management-server-lb" /></para>
     </listitem>
   </orderedlist>
 </section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/5f6cffc6/docs/en-US/management-server-lb.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/management-server-lb.xml b/docs/en-US/management-server-lb.xml
index 85a8622..f651f92 100644
--- a/docs/en-US/management-server-lb.xml
+++ b/docs/en-US/management-server-lb.xml
@@ -19,7 +19,7 @@
   under the License.
 -->
 <section id="management-server-lb">
-  <title>Setting Zone VLAN and Running VM Maximums</title>
+  <title>Management Server Load Balancing</title>
   <para>&PRODUCT; can use a load balancer to provide a virtual IP for multiple
Management
     Servers. The administrator is responsible for creating the load balancer rules for the
     Management Servers. The application requires persistence or stickiness across multiple
sessions.
@@ -57,5 +57,48 @@
         </row>
       </tbody>
     </tgroup>
-  </informaltable>
+</informaltable>
+    <section id="toplogy-requirements">
+        <title>Topology Requirements</title>
+        <section id="security-req">
+            <title>Security Requirements</title>
+            <para>The public Internet must not be able to access port 8096 or port
8250 on the Management Server.</para>
+        </section>
+        <section id="runtime-req">
+            <title>Internal Communication Requirements</title>
+            <itemizedlist>
+                <listitem><para>The Management Servers communicate with each
other to coordinate tasks. This communication uses TCP on ports 8250 and 9090.</para></listitem>
+                <listitem><para>The console proxy VMs connect to all hosts in
the zone over the management traffic network. Therefore the management traffic network of
any given pod in the zone must have connectivity to the management traffic network of all
other pods in the zone.</para></listitem>
+                <listitem><para>The secondary storage VMs and console proxy VMs
connect to the Management Server on port 8250. If you are using multiple Management Servers,
the load balanced IP address of the Management Servers on port 8250 must be reachable.</para></listitem>
+            </itemizedlist>
+        </section>
+        <section id="storage-network-topology-req">
+            <title>Storage Network Topology Requirements</title>
+            <para>The secondary storage NFS export is mounted by the secondary storage
VM. Secondary storage traffic goes over the management traffic network, even if there is a
separate storage network. Primary storage traffic goes over the storage network, if available.
If you choose to place secondary storage NFS servers on the storage network, you must make
sure there is a route from the management traffic network to the storage network.</para>
+        </section>
+        <section id="external-firewall-topology-req">
+            <title>External Firewall Topology Requirements</title>
+            <para>When external firewall integration is in place, the public IP VLAN
must still be trunked to the Hosts. This is required to support the Secondary Storage VM and
Console Proxy VM.</para>
+        </section>
+        <section id="advanced-zone-topology-req">
+            <title>Advanced Zone Topology Requirements</title>
+            <para>With Advanced Networking, separate subnets must be used for private
and public networks.</para>
+        </section>
+        <section id="xenserver-topology-req">
+            <title>XenServer Topology Requirements</title>
+            <para>The Management Servers communicate with XenServer hosts on ports
22 (ssh), 80 (HTTP), and 443 (HTTPs).</para>
+        </section>
+        <section id="vmware-topology-req">
+            <title>VMware Topology Requirements</title>
+            <itemizedlist>
+                <listitem><para>The Management Server and secondary storage VMs
must be able to access vCenter and all ESXi hosts in the zone.  To allow the necessary access
through the firewall, keep port 443 open.</para></listitem>
+                <listitem><para>The Management Servers communicate with VMware
vCenter servers on port 443 (HTTPs).</para></listitem>
+                <listitem><para>The Management Servers communicate with the System
VMs on port 3922 (ssh) on the management traffic network.</para></listitem>
+            </itemizedlist>
+        </section>
+        <section id="kvm-topology-req">
+            <title>KVM Topology Requirements</title>
+            <para>The Management Servers communicate with KVM hosts on port 22 (ssh).</para>
+        </section>
+    </section>
 </section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/5f6cffc6/docs/en-US/networks.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/networks.xml b/docs/en-US/networks.xml
index a7b9ea1..23a9488 100644
--- a/docs/en-US/networks.xml
+++ b/docs/en-US/networks.xml
@@ -45,4 +45,5 @@
   <xi:include href="vpn.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
   <xi:include href="inter-vlan-routing.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
   <xi:include href="configure-vpc.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-</chapter>
\ No newline at end of file
+  <xi:include href="management-server-lb.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+</chapter>


Mime
View raw message