You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by ke...@apache.org on 2013/10/10 21:49:47 UTC
git commit: Removing a link, section is not in the Installation guide
Updated Branches:
refs/heads/master 5483aed28 -> 35bf5941a
Removing a link, section is not in the Installation guide
Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/commit/35bf5941
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/tree/35bf5941
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/diff/35bf5941
Branch: refs/heads/master
Commit: 35bf5941a690eb2faf9a2dc335cb1a7671f08402
Parents: 5483aed
Author: David Nalley <da...@gnsa.us>
Authored: Thu Oct 10 15:49:28 2013 -0400
Committer: David Nalley <da...@gnsa.us>
Committed: Thu Oct 10 15:49:28 2013 -0400
----------------------------------------------------------------------
en-US/system-reserved-ip-addresses.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/35bf5941/en-US/system-reserved-ip-addresses.xml
----------------------------------------------------------------------
diff --git a/en-US/system-reserved-ip-addresses.xml b/en-US/system-reserved-ip-addresses.xml
index c3078a2..e2588ed 100644
--- a/en-US/system-reserved-ip-addresses.xml
+++ b/en-US/system-reserved-ip-addresses.xml
@@ -31,7 +31,7 @@
<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 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 <xref linkend="working-with-system-vm"/> 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 the section on working with SystemVMs 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 both of the following techniques:</para>
<itemizedlist>