You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by bf...@apache.org on 2013/05/02 19:31:42 UTC
[36/50] git commit: updated refs/heads/ui-cisco-asa1000v-support to
ac07a54
CLOUDSTACK-2301
Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/101d89c3
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/101d89c3
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/101d89c3
Branch: refs/heads/ui-cisco-asa1000v-support
Commit: 101d89c3a351c85c8f76bf7b1a723a1153a7be70
Parents: 1686501
Author: Radhika PC <ra...@citrix.com>
Authored: Thu May 2 11:43:02 2013 +0530
Committer: Radhika PC <ra...@citrix.com>
Committed: Thu May 2 11:43:35 2013 +0530
----------------------------------------------------------------------
docs/en-US/elastic-ip.xml | 47 +++++++++++++++++----------
docs/en-US/images/eip-ns-basiczone.png | Bin 55568 -> 63227 bytes
2 files changed, 30 insertions(+), 17 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cloudstack/blob/101d89c3/docs/en-US/elastic-ip.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/elastic-ip.xml b/docs/en-US/elastic-ip.xml
index b09d37d..8ecbd75 100644
--- a/docs/en-US/elastic-ip.xml
+++ b/docs/en-US/elastic-ip.xml
@@ -21,16 +21,31 @@
<section id="elastic-ip">
<title>About Elastic IP</title>
<para>Elastic IP (EIP) addresses are the IP addresses that are associated with an account, and act
- as static IP addresses. The account owner has complete control over the Elastic IP addresses
- that belong to the account. You can allocate an Elastic IP to a VM of your choice from the EIP
- pool of your account. Later if required you can reassign the IP address to a different VM. This
- feature is extremely helpful during VM failure. Instead of replacing the VM which is down, the
- IP address can be reassigned to a new VM in your account. Elastic IP service provides Static NAT
- (1:1) service in an EIP-enabled basic zone. The default network offering,
+ as static IP addresses. The account owner has the complete control over the Elastic IP addresses
+ that belong to the account. As an account owner, you can allocate an Elastic IP to a VM of your
+ choice from the EIP pool of your account. Later if required you can reassign the IP address to a
+ different VM. This feature is extremely helpful during VM failure. Instead of replacing the VM
+ which is down, the IP address can be reassigned to a new VM in your account. </para>
+ <para>Similar to the public IP address, Elastic IP addresses are mapped to their associated
+ private IP addresses by using StaticNAT. The EIP service is equipped with StaticNAT (1:1)
+ service in an EIP-enabled basic zone. The default network offering,
DefaultSharedNetscalerEIPandELBNetworkOffering, provides your network with EIP and ELB network
- services if a NetScaler device is deployed in your zone. Similar to the public IP address,
- Elastic IP addresses are also mapped to their associated private IP addresses by using Stactic
- NAT.</para>
+ services if a NetScaler device is deployed in your zone. Consider the following illustration for
+ more details.</para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./images/eip-ns-basiczone.png"/>
+ </imageobject>
+ <textobject>
+ <phrase>eip-ns-basiczone.png: Elastic IP in a NetScaler-enabled Basic Zone.</phrase>
+ </textobject>
+ </mediaobject>
+ <para>In the illustration, a NetScaler appliance is the default entry or exit point for the
+ &PRODUCT; instances, and firewall is the default entry or exit point for the rest of the data
+ center. Netscaler provides LB services and staticNAT service to the guest networks. The guest
+ traffic in the pods and the Management Server are on different subnets / VLANs. The policy-based
+ routing in the data center core switch sends the public traffic through the NetScaler, whereas
+ the rest of the data center goes through the firewall. </para>
<para>The EIP work flow is as follows:</para>
<itemizedlist>
<listitem>
@@ -48,7 +63,6 @@
supported by NetScaler, in which the source IP address is replaced in the packets
generated by a VM in the private network with the public IP address.</para>
</note>
- <para/>
</listitem>
<listitem>
<para>This default public IP will be released in two cases:</para>
@@ -68,12 +82,12 @@
</itemizedlist>
</listitem>
</itemizedlist>
- <para>However, for the deployments where public IPs are limited resources, you have the
- flexibility to choose not to allocate a public IP by default. You can use the Associate Public
- IP option to turn on or off the automatic public IP assignment in the EIP-enabled Basic zones.
- If you turn off the automatic public IP assignment while creating a network offering, only a
- private IP is assigned to a VM when the VM is deployed with that network offering. Later, the
- user can acquire an IP for the VM and enable static NAT.</para>
+ <para>For the deployments where public IPs are limited resources, you have the flexibility to
+ choose not to allocate a public IP by default. You can use the Associate Public IP option to
+ turn on or off the automatic public IP assignment in the EIP-enabled Basic zones. If you turn
+ off the automatic public IP assignment while creating a network offering, only a private IP is
+ assigned to a VM when the VM is deployed with that network offering. Later, the user can acquire
+ an IP for the VM and enable static NAT.</para>
<para condition="admin">For more information on the Associate Public IP option, see <xref
linkend="creating-network-offerings"/>.</para>
<para condition="install">For more information on the Associate Public IP option, see the
@@ -83,7 +97,6 @@
continue to get both public IP and private by default, irrespective of the network offering
configuration.</para>
</note>
- <para/>
<para>New deployments which use the default shared network offering with EIP and ELB services to
create a shared network in the Basic zone will continue allocating public IPs to each user
VM.</para>
http://git-wip-us.apache.org/repos/asf/cloudstack/blob/101d89c3/docs/en-US/images/eip-ns-basiczone.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/eip-ns-basiczone.png b/docs/en-US/images/eip-ns-basiczone.png
index 315ff55..bc88570 100644
Binary files a/docs/en-US/images/eip-ns-basiczone.png and b/docs/en-US/images/eip-ns-basiczone.png differ