Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of Chiradeep.Vittal@citrix.com
 designates 66.165.176.89 as permitted sender)
From: Chiradeep Vittal <Chiradeep.Vittal@citrix.com>
To: CloudStack DeveloperList <cloudstack-dev@incubator.apache.org>
Date: Thu, 10 Jan 2013 13:25:28 -0800
Subject: Re: [DISCUSS] Global Server Load Balancing (GSLB) FS & Design
 Document
Thread-Topic: [DISCUSS] Global Server Load Balancing (GSLB) FS & Design
 Document
Thread-Index: Ac3veQQYM/AUsg9JQHCcBMPA1Ump/g==
Message-ID: <CD146FA5.40264%chiradeep.vittal@citrix.com>
In-Reply-To: <CD1281EE.2B118%murali.reddy@citrix.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.13.0.110805
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Thanks for the detailed and enlightening write-up*.

I feel that the GSLB service is not a NetworkElement.
NetworkElements are those that participate in the L2/L3 orchestration of
VMs.
GSLB providers do not do this.

It does not even participate in the existing Loadbalancer workflow.

In fact I would assert that this is a completely different higher-level
orchestration workflow that should not need to touch network elements or
the network manager.
You could even write this feature by orchestrating it using the end-user
APIs.


*A lot of folks strive to format the document according to the template
but the template is just to make sure that vital information is not
missed. What ends up happening is that there's a lot of information, but
incoherently organized. Nice job.


On 1/8/13 12:52 PM, "Murali Reddy" <Murali.Reddy@citrix.com> wrote:

>In continuation to my proposal [1], I am brining GSLB support
>separately for discussion. I have put up functional specification and
>design documentation at [2]. Please provide feedback, comments.
>
>Quick abstract of the feature:
>
>Today CloudStack supports load balancing traffic across the VM instances
>with in a zone. In case of multi-zone clouds, users can launch service
>across one or more zones for high availability and disaster recovery. GSLB
>is set of technologies that are used to load balance traffic across
>multiple location and also provides disaster recovery. With this feature
>CloudStack would be able to orchestrate setting up load balancing across
>multiple zones and also provide disaster recovery solution in case of
>multiple zone clouds.
>
>
>[1] http://markmail.org/message/lx6tyikvmvd6wix4
>
>[2]https://cwiki.apache.org/confluence/display/CLOUDSTACK/GSLB+%28Global+S
>e
>rver+Load+Balancing%29+Functional+specification+and+Design+Document
>