Re: [openstack-dev] [nova] Should we delete the (unexposed) os-pci API?

2017-04-18 Thread Matt Riedemann
On 3/17/2017 3:23 PM, Sean Dague wrote: Yes... with fire. Realistically this was about the pinnacle of the extensions on extensions API changes, which is why we didn't even let it into v2 in the first place. Here it is: https://review.openstack.org/457854 -- Thanks, Matt

Re: [openstack-dev] [nova] Should we delete the (unexposed) os-pci API?

2017-03-17 Thread Ed Leafe
On Mar 17, 2017, at 3:23 PM, Sean Dague wrote: >> So I move that we delete the (dead) code. Are there good reasons not to? > > Yes... with fire. > > Realistically this was about the pinnacle of the extensions on > extensions API changes, which is why we didn't even let it into

Re: [openstack-dev] [nova] Should we delete the (unexposed) os-pci API?

2017-03-17 Thread Jay Pipes
On 03/17/2017 04:23 PM, Sean Dague wrote: On 03/17/2017 04:19 PM, Matt Riedemann wrote: I was working on writing a spec for a blueprint [1] that would have touched on the os-pci API [2] and got to documenting about how it's not even documented [3] when Alex pointed out that the API is not even

Re: [openstack-dev] [nova] Should we delete the (unexposed) os-pci API?

2017-03-17 Thread Sean Dague
On 03/17/2017 04:19 PM, Matt Riedemann wrote: > I was working on writing a spec for a blueprint [1] that would have > touched on the os-pci API [2] and got to documenting about how it's not > even documented [3] when Alex pointed out that the API is not even > enabled [4][5]. > > It turns out

[openstack-dev] [nova] Should we delete the (unexposed) os-pci API?

2017-03-17 Thread Matt Riedemann
I was working on writing a spec for a blueprint [1] that would have touched on the os-pci API [2] and got to documenting about how it's not even documented [3] when Alex pointed out that the API is not even enabled [4][5]. It turns out that the os-pci API was added in the Nova V3 API and