Re: [openstack-dev] disabling deprecated APIs by config?

On 05/18/2016 11:56 AM, Dean Troyer wrote: > On Wed, May 18, 2016 at 10:20 AM, Sean Dague > wrote: > > nova-net is now deprecated - https://review.openstack.org/#/c/310539/ > > > Woot! Now to make it not-the-default in DevStack... Sean Collins is

Re: [openstack-dev] disabling deprecated APIs by config?

On Wed, May 18, 2016 at 9:20 AM, Sean Dague wrote: > nova-net is now deprecated - https://review.openstack.org/#/c/310539/ > > And we're in the process in Nova of doing some spring cleaning and > deprecating the proxies to other services - >

Re: [openstack-dev] disabling deprecated APIs by config?

On Wed, May 18, 2016 at 10:20 AM, Sean Dague wrote: > nova-net is now deprecated - https://review.openstack.org/#/c/310539/ > > And we're in the process in Nova of doing some spring cleaning and > deprecating the proxies to other services - >

Re: [openstack-dev] disabling deprecated APIs by config?

On Wed, 2016-05-18 at 10:56 -0500, Dean Troyer wrote: > With my OSC hat on, I need to still support those APIs for a couple of > years at least, so I would love to have a way to discover that those > APIs have been disabled without requiring a round trip to get a 404. > This seems like a useful

Re: [openstack-dev] disabling deprecated APIs by config?

On Wed, May 18, 2016 at 10:20 AM, Sean Dague wrote: > nova-net is now deprecated - https://review.openstack.org/#/c/310539/ Woot! Now to make it not-the-default in DevStack... > One idea was a "big red switch" in the format of a config option >

[openstack-dev] disabling deprecated APIs by config?

nova-net is now deprecated - https://review.openstack.org/#/c/310539/ And we're in the process in Nova of doing some spring cleaning and deprecating the proxies to other services - https://review.openstack.org/#/c/312209/ At some point in the future after deprecation the proxy code is going to