Following discussion on IRC, a patch is now up to add this config option.
Reviews appreciated.
https://review.openstack.org/#/c/166973/
Cheers,
John
On 23/03/2015 18:11, "Carl Baldwin" wrote:
>On Mon, Mar 23, 2015 at 12:04 PM, John Davidge (jodavidg)
> wrote:
>> The above blueprint outlin
On Mon, Mar 23, 2015 at 12:04 PM, John Davidge (jodavidg)
wrote:
> The above blueprint outlines an admin-configurable global default pool to
> be used in the case of a user calling subnet-create without specifying a
> CIDR or subnet-pool ID. If the OpenStack environment has been made
> PD-capable
On Wed, Mar 18, 2015 at 8:15 AM, Sean M. Collins wrote:
> On Wed, Mar 18, 2015 at 06:45:59AM PDT, John Davidge (jodavidg) wrote:
>> In the IPv6 meeting yesterday you mentioned doing this
>> with an extension rather than modifying the core API. Could you go into
>> some detail about how you see thi
Going forward, I think the best approach for PD would be to align with the
subnet-pools being added by the subnet allocation BP work (thanks to Sean
for bringing this to our attention again).
http://specs.openstack.org/openstack/neutron-specs/specs/kilo/subnet-alloca
tion.html#rest-api-impact
Th
On 3/18/15, 9:12 PM, "Sean M. Collins" wrote:
> My hope is that either the new IPAM subsystem for subnet allocations
>would provide this, or that a small API extension could "paper over" some
>of the sharper edges.
In IPAM we have added this concept of a subnet request. The built-in
support w
On Wed, Mar 18, 2015 at 06:45:59AM PDT, John Davidge (jodavidg) wrote:
> In the IPv6 meeting yesterday you mentioned doing this
> with an extension rather than modifying the core API. Could you go into
> some detail about how you see this extension looking?
The easiest, is to evaluate the REST API
Copying my response on the review below:
Yes that completely makes sense Sean. In our original proposal we wanted
to allow the user to initiate a subnet-create without providing a CIDR,
and have an 'ipv6_pd_enabled' flag which could be set in the API call to
tell Neutron that this particular subne
Hi all,
I recently posted this comment in the review for
https://review.openstack.org/#/c/158697/,
and wanted to post it here so that people can respond. Basically, I have
concerns that I raised during the spec submission process
(https://review.openstack.org/#/c/93054/).
I'm still not totally o