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 <sou...@gmail.com> 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 > 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 <ke...@benton.pub>: > >> +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" <mriede...@gmail.com> wrote: >> >>> 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 updating will sync to nova side automatically (I had >>>> verified it in my latest devstack). Updating fixed-ip for >>>> specified port is easier to understand for me in multiple nics case than >>>> nova add-fixed-ip API. >>>> >>>> So if others known the orignal API design or had used nova add/remove >>>> fixed-ip API and would like to show your use cases, >>>> it's nice for us to understand how the API works and when we should use >>>> it, we can update the api-ref and add exact usage, >>>> avoid users' confusion about it. Feel free to reply something, thank >>>> you. >>>> >>>> >>> If the functionality is available via Neutron APIs, we should just >>> deprecate the multinic API like we did for the other network API proxies in >>> microversion 2.36. This reminds me that Alex Xu had a blueprint for >>> deprecating the multinic API [1] but it needs to be updated for Pike. >>> >>> [1] https://review.openstack.org/#/c/384261/ >>> >>> -- >>> >>> Thanks, >>> >>> Matt >>> >>> ____________________________________________________________ >>> ______________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: openstack-dev-requ...@lists.op >>> enstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> ____________________________________________________________ >> ______________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev