dedicated public ip range for VPC

[Brandon Arms <BA...@dsscorp.com>]

Is anyone familiar with dedicating a specific ip range to an account that needs a VPC setup?  when I added a new public range and associated it with the account, there was an isolated network automatically created under the account and all the public ip addresses specified were allocated correctly.  Problem is, the customer needs a vpc for tiering, S2S vpn etc.  When I deleted the automatically generated isolated network, and created a VPC, the dedicated public ip's were not allocated to the vpc router.  When acquiring new public ip addresses, some were being pulled from the system public ip range.

Brandon Arms
DSS

RE: dedicated public ip range for VPC

[Brandon Arms <BA...@dsscorp.com>]

Thank you.  We are running 4.2.1 in our DEV and I have confirmed this works for multi-tier VPC.

Brandon Arms
DSS


-----Original Message-----
From: Likitha Shetty [mailto:likitha.shetty@citrix.com] 
Sent: Thursday, December 12, 2013 11:20 PM
To: users@cloudstack.apache.org; Brandon Arms
Subject: RE: dedicated public ip range for VPC

Brandon,

In 4.2 release this feature was enhanced to support VPC setups too.
Refer - https://cwiki.apache.org/confluence/display/CLOUDSTACK/FS-+Dedicate+Public+IP+Addresses+per+tenant for the Functional spec.

Thanks,
Likitha

>-----Original Message-----
>From: Alena Prokharchyk [mailto:Alena.Prokharchyk@citrix.com]
>Sent: Thursday, December 12, 2013 11:41 PM
>To: users@cloudstack.apache.org; BArms@dsscorp.com
>Subject: Re: dedicated public ip range for VPC
>
>Brandon, dedicated ip range feature has a limitation in the cloudStack 
>- it can be used only for the case when customer (account) owns only one Isolated network.
>As by initial design, the newly created ip range gets programmed 
>automatically on the Isolated network¹s VR right after the range is 
>created (so the code tries to locate the only one network for the 
>account; if there are more than one - it would fail)
>
>I believe there was an enhancement request filed for support dedicated 
>ip range for multiple isolated networks case. If you can¹t find it, please file a new one.
>
>-Alena.
>
>On 12/12/13, 9:14 AM, "Brandon Arms" <BA...@dsscorp.com> wrote:
>
>>Is anyone familiar with dedicating a specific ip range to an account 
>>that needs a VPC setup?  when I added a new public range and 
>>associated it with the account, there was an isolated network 
>>automatically created under the account and all the public ip 
>>addresses specified were allocated correctly.  Problem is, the 
>>customer needs a vpc for tiering, S2S vpn etc.  When I deleted the 
>>automatically generated isolated network, and created a VPC, the 
>>dedicated public ip's were not allocated to the vpc router.  When 
>>acquiring new public ip addresses, some were being pulled from the system public ip range.
>>
>>Brandon Arms
>>DSS

RE: dedicated public ip range for VPC

[Likitha Shetty <li...@citrix.com>]

Brandon,

In 4.2 release this feature was enhanced to support VPC setups too.
Refer - https://cwiki.apache.org/confluence/display/CLOUDSTACK/FS-+Dedicate+Public+IP+Addresses+per+tenant for the Functional spec.

Thanks,
Likitha

>-----Original Message-----
>From: Alena Prokharchyk [mailto:Alena.Prokharchyk@citrix.com]
>Sent: Thursday, December 12, 2013 11:41 PM
>To: users@cloudstack.apache.org; BArms@dsscorp.com
>Subject: Re: dedicated public ip range for VPC
>
>Brandon, dedicated ip range feature has a limitation in the cloudStack - it can be
>used only for the case when customer (account) owns only one Isolated network.
>As by initial design, the newly created ip range gets programmed automatically
>on the Isolated network¹s VR right after the range is created (so the code tries to
>locate the only one network for the account; if there are more than one - it
>would fail)
>
>I believe there was an enhancement request filed for support dedicated ip range
>for multiple isolated networks case. If you can¹t find it, please file a new one.
>
>-Alena.
>
>On 12/12/13, 9:14 AM, "Brandon Arms" <BA...@dsscorp.com> wrote:
>
>>Is anyone familiar with dedicating a specific ip range to an account
>>that needs a VPC setup?  when I added a new public range and associated
>>it with the account, there was an isolated network automatically
>>created under the account and all the public ip addresses specified
>>were allocated correctly.  Problem is, the customer needs a vpc for
>>tiering, S2S vpn etc.  When I deleted the automatically generated
>>isolated network, and created a VPC, the dedicated public ip's were not
>>allocated to the vpc router.  When acquiring new public ip addresses,
>>some were being pulled from the system public ip range.
>>
>>Brandon Arms
>>DSS

Re: dedicated public ip range for VPC

[Alena Prokharchyk <Al...@citrix.com>]

Brandon, dedicated ip range feature has a limitation in the cloudStack -
it can be used only for the case when customer (account) owns only one
Isolated network. As by initial design, the newly created ip range gets
programmed automatically on the Isolated network¹s VR right after the
range is created (so the code tries to locate the only one network for the
account; if there are more than one - it would fail)

I believe there was an enhancement request filed for support dedicated ip
range for multiple isolated networks case. If you can¹t find it, please
file a new one.

-Alena.

On 12/12/13, 9:14 AM, "Brandon Arms" <BA...@dsscorp.com> wrote:

>Is anyone familiar with dedicating a specific ip range to an account that
>needs a VPC setup?  when I added a new public range and associated it
>with the account, there was an isolated network automatically created
>under the account and all the public ip addresses specified were
>allocated correctly.  Problem is, the customer needs a vpc for tiering,
>S2S vpn etc.  When I deleted the automatically generated isolated
>network, and created a VPC, the dedicated public ip's were not allocated
>to the vpc router.  When acquiring new public ip addresses, some were
>being pulled from the system public ip range.
>
>Brandon Arms
>DSS