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 0EB6B9284 for ; Wed, 6 Mar 2013 00:41:40 +0000 (UTC) Received: (qmail 44552 invoked by uid 500); 6 Mar 2013 00:41:39 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 44515 invoked by uid 500); 6 Mar 2013 00:41:39 -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 44506 invoked by uid 99); 6 Mar 2013 00:41:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 00:41:39 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Chiradeep.Vittal@citrix.com designates 66.165.176.89 as permitted sender) Received: from [66.165.176.89] (HELO SMTP.CITRIX.COM) (66.165.176.89) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 00:41:35 +0000 X-IronPort-AV: E=Sophos;i="4.84,791,1355097600"; d="scan'208";a="11371262" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Mar 2013 00:41:14 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Tue, 5 Mar 2013 16:41:13 -0800 From: Chiradeep Vittal To: "cloudstack-dev@incubator.apache.org" Date: Tue, 5 Mar 2013 16:41:10 -0800 Subject: Re: [Discuss] Support for non-contiguous vlan ranges. Thread-Topic: [Discuss] Support for non-contiguous vlan ranges. Thread-Index: Ac4aA03dDJDefU2uSX+5tGMX7Zzv/w== Message-ID: In-Reply-To: <1938106D-029E-4021-B51B-53E20C9D1DD4@citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.1.130117 acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Will the changes be atomic? All or nothing? Existing range E=3D 100-200, in use U=3D101,121,131 New request: add=3D201-301, remove=3D100-201 Or E =3D 100-200, U=3D110-120 A =3D 150-250, R=3D100-149 etc On 1/24/13 10:13 PM, "Bharat Kumar" wrote: > Thank you Manan for pointing this out i intended to say multiple Vlans >not IPs.=20 >I corrected it in the FS. > >Bharat >On Jan 25, 2013, at 4:25 AM, Manan Shah wrote: > >> Bharat, I reviewed the FS and I have the following question. It states >> that=A9 >>=20 >> Admin can update the vlan range after creation or can add multiple non >> contiguous vlan ranges while creating a zone. This can be done by >> changing the UpdatephysicalNetwork api. It allows only extending of the >> vlan. we plan to extend the api to update the vlan with multiple ip >> Ranges. >>=20 >> What does it mean by "we plan to extend the API to update the VLAN with >> multiple IP Ranges". Specifically the "Multiple IP Ranges" part. >>=20 >> Can you clarify? >>=20 >>=20 >> Regards, >> Manan Shah >>=20 >>=20 >>=20 >>=20 >> On 1/4/13 8:49 AM, "Manan Shah" wrote: >>=20 >>> Bharat, I have created a JIRA ticket as well as requirements page for >>>this >>> requirement. Please leverage that. >>>=20 >>> Regards, >>> Manan Shah >>>=20 >>>=20 >>>=20 >>>=20 >>> On 1/3/13 10:33 PM, "Prasanna Santhanam" wrote: >>>=20 >>>> On Fri, Jan 04, 2013 at 11:37:28AM +0530, Bharat Kumar wrote: >>>>> Hi all, >>>>>=20 >>>>> In cloudstack we specify the vlan ranges in advanced zone. These >>>>> vlans are used while creating the guest networks. Presently we can >>>>> add only one continuos vlan range. There is no way to add non >>>>> contiguous vlan ranges. >>>>>=20 >>>>> So we propose to add a feature to support adding multiple vlan >>>>> ranges. >>>>>=20 >>>>> This feature will enable adding non contiguous vlan ranges. >>>>>=20 >>>>=20 >>>> Will it support extending the ranges in non-contiguous increments >>>> after the zone has been created? >>>>=20 >>>> So I start with 100-200 and then later extend my switch and cloudstack >>>> to do 300-400, 492 and 50-80 say? >>>>=20 >>>> --=20 >>>> Prasanna., >>>=20 >>=20 >