[openstack-dev] [nova] Next steps for proxy API deprecation

Matt Riedemann mriedem at linux.vnet.ibm.com
Tue Jul 26 16:59:03 UTC 2016

Now that the 2.36 microversion change has merged [1], we can work on the 
python-novaclient changes for this microversion.

At the midcycle we agreed [2] to also return a 404 for network APIs, 
including nova-network (which isn't a proxy), for consistency and 
further signaling that nova-network is going away.

In the client, we agreed to soften the impact for network CLIs by 
determining if the latest microversion supported will fail (so will we 
send >=2.36) and rather than fail, send 2.35 instead (if the user didn't 
specifically specify a different version). However, we'd emit a warning 
saying this is deprecated and will go away in the first major client 
release (in Ocata? after nova-network is removed? after Ocata is released?).

We should probably just deprecate any CLIs/APIs in python-novaclient 
today that are part of this server side API change, including network 
CLIs/APIs in novaclient. The baremetal and image proxies in the client 
are already deprecated, and the volume proxies were already removed. 
That leaves the network proxies in the client.

 From my notes, Dan Smith was going to work on the novaclient changes 
for 2.36 to not fail and use 2.35 - unless anyone else wants to 
volunteer to do that work (please speak up).

We can probably do the network CLI/API deprecations in the client in 
parallel to the 2.36 support, but need someone to step up for that. I'll 
try to get it started this week if no one else does.

[1] https://review.openstack.org/#/c/337005/
[2] https://etherpad.openstack.org/p/nova-newton-midcycle



Matt Riedemann

More information about the OpenStack-dev mailing list