On Wed, May 29, 2013 at 06:02:59AM +, Murali Reddy wrote:
> On 28/05/13 11:42 PM, "Chip Childers" wrote:
> >
> >+1 to this proposal (with one concern noted below).
> >
> >>
> >> Effort I am proposing is to get API semantics right with minimal
> >>changes.
> >> I am not proposing to enable por
On 28/05/13 11:42 PM, "Chip Childers" wrote:
>
>+1 to this proposal (with one concern noted below).
>
>>
>> Effort I am proposing is to get API semantics right with minimal
>>changes.
>> I am not proposing to enable portability for zone level public Ip's for
>> 4.2 but can be done for later relea
On Tue, May 28, 2013 at 01:56:21PM +, Murali Reddy wrote:
> In CloudStack, currently there are four distinct operations available with
> public IP's at network service and manager layers.
>
> 1. Acquiring a public IP from zone level public IP pool
> 2. Associate acquired public IP with
Hi Murali,
I have an internal issue, 'Cannot add additional network range to NVP
isolated network', meaning the user wants to expand a guest network. Is it
an idea to integrate this question into your design? I realize that you are
adressing the API mainly but the relation seems so close that I am
In CloudStack, currently there are four distinct operations available with
public IP's at network service and manager layers.
1. Acquiring a public IP from zone level public IP pool
2. Associate acquired public IP with a guest network/VPC
3. Disassociate an associated public IP with a
