apache/cloudstack
1
0
Fork 0
mirror of https://github.com/apache/cloudstack.git synced 2025-11-02 11:52:28 +01:00
Code Issues Packages Projects Releases Wiki Activity

fix build error

Browse Source
This commit is contained in:
radhikap 2013-05-14 07:37:07 +05:30
parent e3ff2b33ae
commit 9f9333b363
1 changed files with 1 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
docs/en-US/gslb.xml
View File

@ -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>