From 030fe5b6624bf4e22e02306cea0982c310566acf Mon Sep 17 00:00:00 2001
From: radhikap <radhika.puthiyetath@citrix.com>
Date: Tue, 27 Aug 2013 11:31:45 +0530
Subject: [PATCH] review comments for CLOUDSTACK-2808, CLOUDSTACK-769

---
 docs/en-US/add-loadbalancer-rule-vpc.xml | 33 +++++++++++++++++-------
 1 file changed, 24 insertions(+), 9 deletions(-)

diff --git a/docs/en-US/add-loadbalancer-rule-vpc.xml b/docs/en-US/add-loadbalancer-rule-vpc.xml
index 71fc51c1f8f..90247b0a6f9 100644
--- a/docs/en-US/add-loadbalancer-rule-vpc.xml
+++ b/docs/en-US/add-loadbalancer-rule-vpc.xml
@@ -278,6 +278,19 @@
         </textobject>
       </mediaobject>
     </section>
+    <section id="internallb-notes">
+      <title>Guidelines</title>
+      <itemizedlist>
+        <listitem><para>Internal LB and Public LB are mutually exclusive on a tier. If the tier has LB on the public
+            side, then it can't have the Internal LB.</para></listitem>
+        <listitem><para>Internal LB is supported just on VPC networks in &PRODUCT; 4.2 release.</para></listitem>
+        <listitem><para>Only Internal LB VM can act as the Internal LB provider in &PRODUCT; 4.2 release.</para></listitem>
+        <listitem><para>Network upgrade is not supported from the network offering with Internal LB to the network
+            offering with Public LB.</para></listitem>
+        <listitem><para>Multiple tiers can have internal LB support in a VPC.</para></listitem>
+        <listitem><para>Only one tier can have Public LB support in a VPC.</para></listitem>
+      </itemizedlist>
+    </section>
     <section id="enable-vpc-lb">
       <title>Enabling Internal LB on a VPC Tier</title>
       <orderedlist>
@@ -371,12 +384,13 @@
     <section id="int-lb-vpc">
       <title>Creating an Internal LB Rule</title>
       <para>When you create the Internal LB rule and applies to a VM, an Internal LB VM, which is
-        responsible for load balancing, is created. You can view the created Internal LB VM in the
-        Instances page if you navigate to <emphasis role="bold">Infrastructure</emphasis> >
-          <emphasis role="bold">Zones</emphasis> > &lt;<emphasis role="italic">zone_
-        name</emphasis>&gt; > &lt;<emphasis role="italic">physical_network_name</emphasis>&gt; >
-          <emphasis role="bold">Network Service Providers</emphasis> > <emphasis role="bold"
-          >Internal LB VM</emphasis>. </para>
+        responsible for load balancing, is created. </para>
+      <para>You can view the created Internal LB VM in the Instances page if you navigate to
+          <emphasis role="bold">Infrastructure</emphasis> > <emphasis role="bold">Zones</emphasis> >
+          &lt;<emphasis role="italic">zone_ name</emphasis>&gt; > &lt;<emphasis role="italic"
+          >physical_network_name</emphasis>&gt; > <emphasis role="bold">Network Service
+          Providers</emphasis> > <emphasis role="bold">Internal LB VM</emphasis>. You can manage the
+        Internal LB VMs as and when required from the location.</para>
       <orderedlist>
         <listitem>
           <para>Log in to the &PRODUCT; UI as an administrator or end user.</para>
@@ -410,9 +424,10 @@
                 that can be displayed to users.</para>
             </listitem>
             <listitem>
-              <para><emphasis role="bold">Source IP Address</emphasis>: The source IP from which
-                traffic originates. The IP is acquired from the CIDR of that particular tier on
-                which you want to create the Internal LB rule. </para>
+              <para><emphasis role="bold">Source IP Address</emphasis>: (Optional) The source IP
+                from which traffic originates. The IP is acquired from the CIDR of that particular
+                tier on which you want to create the Internal LB rule. If not specified, the IP
+                address is automatically allocated from the network CIDR.</para>
               <para>For every Source IP, a new Internal LB VM is created for load balancing.</para>
             </listitem>
             <listitem>