Return-Path: X-Original-To: apmail-cloudstack-commits-archive@www.apache.org Delivered-To: apmail-cloudstack-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D318CF2D9 for ; Mon, 13 May 2013 04:36:36 +0000 (UTC) Received: (qmail 1732 invoked by uid 500); 13 May 2013 04:36:35 -0000 Delivered-To: apmail-cloudstack-commits-archive@cloudstack.apache.org Received: (qmail 1451 invoked by uid 500); 13 May 2013 04:36:32 -0000 Mailing-List: contact commits-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list commits@cloudstack.apache.org Received: (qmail 1388 invoked by uid 99); 13 May 2013 04:36:30 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 May 2013 04:36:30 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id C827C88F13C; Mon, 13 May 2013 04:36:29 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: radhika@apache.org To: commits@cloudstack.apache.org Message-Id: <5d3464c85ab645738092684d0fcc0261@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: git commit: updated refs/heads/master to 6df3d83 Date: Mon, 13 May 2013 04:36:29 +0000 (UTC) Updated Branches: refs/heads/master 225a46746 -> 6df3d8318 CLOUDSTACK-893 conceptual info around gslb Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/6df3d831 Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/6df3d831 Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/6df3d831 Branch: refs/heads/master Commit: 6df3d83183d33876c37ea51cd0ffcb8836fa8d26 Parents: 225a467 Author: unknown Authored: Fri May 10 19:43:29 2013 +0530 Committer: radhikap Committed: Mon May 13 10:05:54 2013 +0530 ---------------------------------------------------------------------- docs/en-US/gslb.xml | 35 +++++++++++------------------------ 1 files changed, 11 insertions(+), 24 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/6df3d831/docs/en-US/gslb.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/gslb.xml b/docs/en-US/gslb.xml index 2303331..8070e30 100644 --- a/docs/en-US/gslb.xml +++ b/docs/en-US/gslb.xml @@ -157,29 +157,15 @@
Configuring GSLB - 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. - To configure GSLB in your cloud environment, as a cloud administrator you must perform the - following. - To configure such a GSLB setup, you must first configure a standard load balancing setup + 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, 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. - Perform the following as a cloud administrator. As per the above example, the + the region. Then on the NetScaler side, 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 zones are identical, although each + sites load-balancing configuration is specific to that site. + Perform the following as a cloud administrator. As per the example given above, the administrator of xyztelco is the one who sets up GSLB: @@ -200,7 +186,9 @@ >Configuring an Authoritative DNS Service. - Configure a GSLB site with site name formed from the domain name details. + Configure a GSLB site with the site name formed from the domain name. + As per the example given above, the site names are A.xyztelco.com and + B.xyztelco.com. For more information, see Configuring a Basic GSLB Site. @@ -459,7 +447,6 @@
Assigning Load Balancing Rules to GSLB - Log in to the &PRODUCT; UI as a domain administrator or user.