fix build error

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

Branch: refs/heads/vmware-storage-motion
Commit: 9f9333b36374a3924fedddd93b41b6005c5ea818
Parents: e3ff2b3
Author: radhikap <[email protected]>
Authored: Tue May 14 07:37:07 2013 +0530
Committer: radhikap <[email protected]>
Committed: Tue May 14 07:37:07 2013 +0530

----------------------------------------------------------------------
 docs/en-US/gslb.xml |   26 +-------------------------
 1 files changed, 1 insertions(+), 25 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cloudstack/blob/9f9333b3/docs/en-US/gslb.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/gslb.xml b/docs/en-US/gslb.xml
index 3f6a494..d5d2d20 100644
--- a/docs/en-US/gslb.xml
+++ b/docs/en-US/gslb.xml
@@ -157,29 +157,6 @@
   </section>
   <section id="gslb-workflow">
     <title>Configuring GSLB</title>
-    <para>A GSLB deployment is the logical collection of GSLB virtual server, 
GSLB service, LB
-      virtual server, service, domain, and ADNS service. To create a GSLB 
site, you must configure
-      load balancing in the zone. You must create GSLB vservers and GSLB 
services for each site. You
-      must bind GSLB services to GSLB vservers. You must then create an ADNS 
service that provides
-      the IP address of the best performing site to the client's request. A 
GSLB vserver is an
-      entity that performs load balancing for the domains bound to it by 
returning the IP address of
-      the best GSLB service. A GSLB service is a representation of the load 
balancing/content
-      switching vserver. An LB vserver load balances incoming traffic by 
identifying the best
-      server, then directs traffic to the corresponding service. It can also 
load-balance external
-      DNS name servers. Services are entities that represent the servers. The 
domain is the domain
-      name for which the system is the authoritative DNS server. By creating 
an ADNS service, the
-      system can be configured as an authoritative DNS server.</para>
-    <para>To configure GSLB in your cloud environment, as a cloud 
administrator you must perform the
-      following.</para>
-    <para>To configure such a GSLB setup, you must first configure a standard 
load balancing setup
-      for each zone. This enables you to balance load across the different 
servers in each zone in
-      the region. Then, configure both NetScaler appliances that you plan to 
add to each zone as
-      authoritative DNS (ADNS) servers. Next, create a GSLB site for each 
zone, configure GSLB
-      virtual servers for each site, create GLSB services, and bind the GSLB 
services to the GSLB
-      virtual servers. Finally, bind the domain to the GSLB virtual servers. 
The GSLB configurations
-      on the two appliances at the two different sites are identical, although 
each sites
-      load-balancing configuration is specific to that site.</para>
-    <para>Perform the following as a cloud administrator. As per the above 
example, the
     <para>To configure a GSLB deployment, you must first configure a standard 
load balancing setup
       for each zone. This enables you to balance load across the different 
servers in each zone in
       the region. Then on the NetScaler side, configure both NetScaler 
appliances that you plan to
@@ -471,7 +448,6 @@
     </section>
     <section id="assign-lb-gslb">
       <title>Assigning Load Balancing Rules to GSLB</title>
-      <para/>
       <orderedlist>
         <listitem>
           <para>Log in to the &PRODUCT; UI as a domain administrator or 
user.</para>
@@ -503,7 +479,7 @@
       </orderedlist>
     </section>
   </section>
-  <section id="limit-gslb">
+  <section>
     <title>Known Limitation</title>
     <para>Currently, &PRODUCT; does not support orchestration of services 
across the zones. The
       notion of services and service providers in region are to be 
introduced.</para>

Reply via email to