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 53D8AE38C for ; Thu, 24 Jan 2013 23:53:51 +0000 (UTC) Received: (qmail 13991 invoked by uid 500); 24 Jan 2013 23:53:50 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 13933 invoked by uid 500); 24 Jan 2013 23:53:50 -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 13923 invoked by uid 99); 24 Jan 2013 23:53:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jan 2013 23:53:50 +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 manan.shah@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; Thu, 24 Jan 2013 23:53:45 +0000 X-IronPort-AV: E=Sophos;i="4.84,532,1355097600"; d="scan'208";a="4762871" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Jan 2013 23:53:23 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.73]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Thu, 24 Jan 2013 15:52:50 -0800 From: Manan Shah To: "cloudstack-dev@incubator.apache.org" Date: Thu, 24 Jan 2013 15:52:49 -0800 Subject: Re: [Discuss] Support for multiple ip ranges. Thread-Topic: [Discuss] Support for multiple ip ranges. Thread-Index: Ac36jesEqzBJsVy2T8KB398KPGKvvA== 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.2.5.121010 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 Hi Bharat Kumar, I have some additional questions regarding this spec. 1. Can you specify the scope of your feature? Assuming you are only addressing the Guest IP part and not Management IP part, correct? 2. For the Advanced Shared, I realized after writing these requirements that adding more ranges to the existing subnet for a Shared Network is already possible today. For different subnets, I believe Anthony has taken a different approach which is contradictory to yours. Are you suggesting that we will support both ways? 3. For Basic Zone, it also seems that this is already possible to extend an existing subnet for the POD. For an additional subnet on the same POD, would this new API work and how different/similar are the approaches going to be compared to Advanced Shared network? Regards, Manan Shah On 1/19/13 3:08 AM, "Bharat Kumar" wrote: >Hi Sanjeev,=20 >find my comments inline. >=20 >On Jan 17, 2013, at 4:31 PM, Sanjeev Neelarapu > wrote: > >> Hi, >>=20 >> I have reviews Multiple IP Ranges FS available @ >>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Multiple+Ip+ranges >>+FS and below are my review comments: >>=20 >> 1.Is there any limit on no.of subnets/IP ranges that can be added for >>guest?(since a new nic is added on router vm for every different subnet) > There is a limit on the number of nics a VM can have depending on the >hypervisor. So if we go ahead with the present idea there will be a >limit on the number of subnets. I also came to know alternative method, >we can add multiple ips to the same nic of a VM. I still need to see if >there are any downsides to this. >=20 >>=20 >> 2.Do we support adding multiple subnets in the same vlan incase of >>Shared guest network in Advanced zone? > I think this can be done as an enhancement once we are done with the >basic implementation. >>=20 >> 3.Can we shrink the existing IP ranges(Guest/Management)? > Shrinking an ip range is possible as long as none of the ips which >are being removed due to shrinkage are in use. We still need to discuss >if this functionality is required. >>=20 >> 4.Can we add non-contiguos guest ip ranges for Basic zone? > yes. >>=20 >> 5.Do we support tagged IP Network for management traffic? > I don't understand this question can you please elaborate it. >>=20 >> 6.Is not-contiguous management IP ranges supported? > yes.=20 >>=20 >> 7. Is this supported in upgraded environment? >The upgrade will not modify the existing ip ranges. we can just add new >ip ranges after the upgrade. > >>=20 >> Thanks, >> Sanjeev >>=20 >> -----Original Message----- >> From: Bharat Kumar [mailto:bharat.kumar@citrix.com] >> Sent: Tuesday, January 08, 2013 5:27 PM >> To: cloudstack-users@incubator.apache.org; >>cloudstack-dev@incubator.apache.org >> Subject: [Discuss] Support for multiple ip ranges. >>=20 >> Hi all, >>=20 >> Currently in cloudstack we can add multiple public ip ranges. we want >>to provide similar flexibility for management and guest ip ranges. >>=20 >> Motivation: There may be cases where some part of the subnet is >>allocated for some other purpose and the admin wants to use the rest of >>the ip range or admin may want to add more ip address once the old ones >>are exhausted. Admin may want to add the ip ranges form the same subnet >>or from different one. Currently in cloudstack there is no flexibility >>to do this for management and guest ip ranges (ip ranges from different >>subnets).=20 >>=20 >> This feature allows adding multiple management ip ranges in advanced >>and basic zones, and guest ip ranges in basic zones. >>=20 >> Regards, >> Bharat Kumar. >>=20 >>=20 >>=20 >>=20 >>=20 >>=20 >>=20 >