cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chipchild...@apache.org
Subject [19/49] git commit: Added short section that addresses the TODO for the system reserved IP addresses. Copied over from original 3.x documentation.
Date Mon, 22 Oct 2012 15:20:28 GMT
Added short section that addresses the TODO for the system reserved IP addresses. Copied over
from original 3.x documentation.


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

Branch: refs/heads/4.0
Commit: 51653af056d23f603374591ce7783cc6feb620b1
Parents: 536fa68
Author: Joe Brockmeier <jzb@zonker.net>
Authored: Sat Oct 20 14:42:59 2012 -0500
Committer: Chip Childers <chip.childers@gmail.com>
Committed: Mon Oct 22 10:59:32 2012 -0400

----------------------------------------------------------------------
 docs/en-US/configure-package-repository.xml |    2 +-
 docs/en-US/system-reserved-ip-addresses.xml |    9 ++++++---
 2 files changed, 7 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/51653af0/docs/en-US/configure-package-repository.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/configure-package-repository.xml b/docs/en-US/configure-package-repository.xml
index 996b936..6e5f349 100644
--- a/docs/en-US/configure-package-repository.xml
+++ b/docs/en-US/configure-package-repository.xml
@@ -39,7 +39,7 @@
     </note>
     <section id="configure-package-repository-deb">
         <title>DEB package repository</title>
-        <para>You can add a DEB package repository to your apt sources with the following
commands. Please note that currently only packages for Ubuntu 12.04 (precise) are being build.</para>
+        <para>You can add a DEB package repository to your apt sources with the following
commands. Please note that currently only packages for Ubuntu 12.04.1 LTS (precise) are being
build.</para>
         <para>Use your preferred editor and open (or create) <filename>/etc/apt/sources.list.d/cloudstack</filename>.
Add the community provided repository to the file:</para>
 <programlisting>deb http://cloudstack.apt-get.eu/ubuntu precise 4.0</programlisting>
         <para>We now have to add the public key to the trusted keys.</para>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/51653af0/docs/en-US/system-reserved-ip-addresses.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/system-reserved-ip-addresses.xml b/docs/en-US/system-reserved-ip-addresses.xml
index 2f49225..1270378 100644
--- a/docs/en-US/system-reserved-ip-addresses.xml
+++ b/docs/en-US/system-reserved-ip-addresses.xml
@@ -32,8 +32,11 @@
     <para>Provide private IPs for the system in each pod and provision them in &PRODUCT;.</para>
     <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.</para>
     <para><emphasis role="bold">In a zone that uses advanced networking:</emphasis></para>
-    <para>For vSphere with advanced networking, we recommend provisioning enough private
IPs for your total number of customers, plus enough for the required &PRODUCT; 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.</para>
+    <para>For zones with advanced networking, we recommend provisioning enough private
IPs for your total number of customers, plus enough for the required &PRODUCT; 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.</para>
     <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.</para>
-    <para>To ensure adequate headroom to scale private IP space in an ESXi pod that
uses advanced networking, use one or more of the following techniques:</para>
-    <para>TODO</para>
+    <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:</para>
+    <itemizedlist>
+        <listitem><para>Specify a larger CIDR block for the subnet. A subnet
mask with a /20 suffix will provide more than 4,000 IP addresses.</para></listitem>
+        <listitem><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.</para></listitem>
+    </itemizedlist>
 </section>


Mime
View raw message