Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 145D4E50D for ; Mon, 17 Dec 2012 20:05:39 +0000 (UTC) Received: (qmail 48084 invoked by uid 500); 17 Dec 2012 20:05:38 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 48025 invoked by uid 500); 17 Dec 2012 20:05:38 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 48016 invoked by uid 99); 17 Dec 2012 20:05:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2012 20:05:38 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Chiradeep.Vittal@citrix.com designates 66.165.176.63 as permitted sender) Received: from [66.165.176.63] (HELO SMTP02.CITRIX.COM) (66.165.176.63) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2012 20:05:33 +0000 X-IronPort-AV: E=Sophos;i="4.84,304,1355097600"; d="scan'208";a="948331" Received: from sjcpmailmx02.citrite.net ([10.216.14.75]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/RC4-MD5; 17 Dec 2012 20:05:11 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX02.citrite.net ([10.216.14.75]) with mapi; Mon, 17 Dec 2012 12:05:10 -0800 From: Chiradeep Vittal To: CloudStack DeveloperList Date: Mon, 17 Dec 2012 12:05:08 -0800 Subject: Re: [Discuss] EIP and ELB enhancements for HA & Failover application architecture Thread-Topic: [Discuss] EIP and ELB enhancements for HA & Failover application architecture Thread-Index: Ac3ckdDmhq9ghj6QTjS+IffxIaImuA== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: 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 X-Virus-Checked: Checked by ClamAV on apache.org Thanks, Murali These are a few big features in the same email. Can we split them up to be discussed independently? 1. EIP across zones 2. ELB across zones 3. ELB scaling parity 4. Network appliance orchestration framework On 12/17/12 11:58 AM, "Murali Reddy" wrote: >I would like to work on enhancing EIP/ELB functionality present in >CloudStack, so that highly available and fault-tolerant application can be >architected using CloudStack deployments at a region level. EIP and ELB >are both AWS networking features that help building fault-tolerant, highly >available application architectures on top of AWS [1],[2],[3]. Idea of >this enhancement is to leverage the RHI (Route Health Injection) and GSLB >functionalities available in application delivery controllers that provide >HA/DR solutions in Active-Active data centre configuration to provide AWS >style EIP and ELB functionality in CloudStack. I opened enhancement >requests 652, 653 for tracking. > >CLOUDSTACK-652: High Availability: EIP enhancements >CLOUDSTACK-653: High Availability: implement GSLB (Global Server Load >Balancing) capability for ELB service > >Also another complementery effort I would like to work on is close the gap >between CloudStack implementation of ELB with that of AWS w.r.t to >CloudStack ability to auto-scale up/down request handling capacity. This >would require CloudStack to orchestrate provisioning load balancer >appliances. I opened enhancement requests 654, 655 for tracking. 655 is >pre-requisite for 654. > >CLOUDSTACK-654: ELB: auto-scale request handling capacity by >provisioningLB appliances >CLOUDSTACK-655: framework for CloudStack to orchestrate virtual network >appliances to provide network services > >This effort in general would involve two parts. First, coming up with >framework/abstraction/generic configuration etc with out any particular >assumption of ADC or network appliance. Second, ADC/appliance specific >implementation that would realise the functionality. For the second part, >I would be primarily working on NetScaler ADC. If any one interested in >contributing support for other appliances/ADC I would be happy to work >toward integration. > >I would be starting POC to uncover the issue in supporting cross zone >operation with CloudStack. I hope to come with up a functional >requirements spec by early next week. > >[1] http://media.amazonwebservices.com/AWS_Disaster_Recovery.pdf >[2]=20 >http://media.amazonwebservices.com/AWS_Building_Fault_Tolerant_Application >s >.pdf >[3]=20 >http://support.rightscale.com/09-Clouds/AWS/02-Amazon_EC2/Designing_Failov >e >r_Architectures_on_EC2/00-Best_Practices_for_using_Elastic_IPs_(EIP)_and_A >v >ailability_Zones >=20 > >-Murali >