oops, sorry, the correct link is https://review.openstack.org/#/c/384261/,
I must remove last number accidently
2017-03-30 14:34 GMT+08:00 Kevin Benton :
> Not sure what you meant to link to, but that's not a spec. :)
>
> On Wed, Mar 29, 2017 at 11:21 PM, Alex Xu
Not sure what you meant to link to, but that's not a spec. :)
On Wed, Mar 29, 2017 at 11:21 PM, Alex Xu wrote:
> I just move the spec into Pike release https://review.
> openstack.org/#/c/38426.
>
> The problem description section describes the strange API behaviour, and
>
I just move the spec into Pike release
https://review.openstack.org/#/c/38426.
The problem description section describes the strange API behaviour, and
proposal to deprecate the API since there isn't a clear use-case for this
API.
2017-03-29 8:59 GMT+08:00 Kevin Benton :
> +1.
+1. If there is a use case missing from the neutron API that this allows,
we can also expand the API to address it.
On Mar 28, 2017 07:16, "Matt Riedemann" wrote:
> On 3/27/2017 11:42 PM, Rui Chen wrote:
>
>> Thank you Matt, the background information is important. Seems
On 3/27/2017 11:42 PM, Rui Chen wrote:
Thank you Matt, the background information is important. Seems all the
peoples don't know how the add-fixed-ip API works,
and there is no exact use case about it. Now neutron port-update API
also support to set multiple fixed ip for a port, and
the fixed-ip
Thank you Matt, the background information is important. Seems all the
peoples don't know how the add-fixed-ip API works,
and there is no exact use case about it. Now neutron port-update API also
support to set multiple fixed ip for a port, and
the fixed-ip updating will sync to nova side
On 3/27/2017 7:23 AM, Rui Chen wrote:
Hi:
A question about nova AddFixedIp API, nova api-ref[1] describe the
API as "Adds a fixed IP address to a server instance, which associates
that address with the server.", the argument of API is network id, so if
there are two or more subnets in a