Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: error (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <CE4E0CD0.1E448%venkataswamybabu.budumuru@citrix.com>
References: <B549DFEF-FCBF-4335-8B1D-E69E153C4E8F@clogeny.com>
 <CE4E0CD0.1E448%venkataswamybabu.budumuru@citrix.com>
From: Gaurav Aradhye <gaurav.aradhye@clogeny.com>
Date: Thu, 5 Sep 2013 12:24:07 +0530
Message-ID: 
 <CAFU5GBSa77M-aTkabvP49THCPeJ=F83nq-d_NzOAaeJtHPjRgw@mail.gmail.com>
Subject: Re: Passing vlan parameter to "createPortableIpRange"
To: Venkata SwamyBabu Budumuru <venkataswamybabu.budumuru@citrix.com>
Cc: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>,
	Sudha Ponnaganti <sudha.ponnaganti@citrix.com>
Content-Type: multipart/alternative; boundary=001a11c352949a9aea04e59d64b8

--001a11c352949a9aea04e59d64b8
Content-Type: text/plain; charset=ISO-8859-1

Ok that means in any case public or portable ip ranges should not overlap
and right now this is not handled for public ranges.
That removes my confusion.

Thanks swamy

Regards,
Gaurav


On Thu, Sep 5, 2013 at 10:27 AM, Venkata SwamyBabu Budumuru <
venkataswamybabu.budumuru@citrix.com> wrote:

> Passing a vlan id or not doesn't matter as long as your infra is
> configured accordingly. The only thing that user should not do and CS is
> allowing is  passing the same public ip range in different vlans.
>
> On 05/09/13 9:52 AM, "Girish Shilamkar" <girish@clogeny.com> wrote:
>
> >Hi Swamy,
> >
> >Thanks for setting up a call, the other day, we were able resolve this
> >issue quickly.
> >In what scenario would  vlan id be passed? How does passing vlan id
> >change/affect Portable IP range to be created ?
> >I am guessing that Portable IP range created would be within IP range
> >assigned for the vlan. (which as of now does not work)
> >
> >Regards,
> >Girish
> >
> >On 05-Sep-2013, at 9:41 AM, Venkata SwamyBabu Budumuru
> ><venkataswamybabu.budumuru@citrix.com> wrote:
> >
> >> Hi Gaurav,
> >>
> >> The VLAN parameter is not mandatory. Depending on your environment you
> >>can
> >> either pass a VLAN tag / untagged one.
> >> We have updated our documents about the issue with adding same ip range
> >> across portable and public VLANs. This is punted for 4.2.1.
> >>
> >> Thanks,
> >> SWAMY
> >>
> >> On 04/09/13 8:26 PM, "Gaurav Aradhye" <gaurav.aradhye@clogeny.com>
> >>wrote:
> >>
> >>> Hi Swamy,
> >>>
> >>> As observed, if portable ip range is created with IPs overlapping with
> >>>any
> >>> of the existing public ip ranges, then it gives "Entity already exists"
> >>> error while associating any portable ip from the created range. (But it
> >>> doesn't give any error while creating portable ip range in this case)
> >>>
> >>> The question is if we can't use IPs from existing VLANs, why to pass
> >>>vlan
> >>> parameter while creating portable ip range? Keeping the default value
> >>> "untagged" serves the purpose and works well. I didn't get this well.
> >>>
> >>> Can you please explain me the how we can use vlan ids to while creating
> >>> portable range and still get it work correctly?
> >>>
> >>> Regards,
> >>> Gaurav
> >>
> >
>
>

--001a11c352949a9aea04e59d64b8--