[openstack-dev] Version header for OpenStack microversion support
D'Angelo, Scott
scott.dangelo at hpe.com
Mon Jun 20 22:24:08 UTC 2016
FYI, Cinder implemented using the style recommended by the API-wg:
https://review.openstack.org/#/c/224910
________________________________
From: Sean Dague <sean at dague.net>
Sent: Monday, June 20, 2016 6:32:10 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] Version header for OpenStack microversion support
On 06/18/2016 06:32 AM, Jamie Lennox wrote:
> Quick question: why do we need the service type or name in there? You
> really should know what API you're talking to already and it's just
> something that makes it more difficult to handle all the different APIs
> in a common way.
It is also extremely useful in wire interactions to be explicit so that
you know for sure you are interacting with the thing you think you are.
There was also the potential question of compound API operations (a Nova
call that calls other microversioned services that may impact
representation) and whether that may need to be surfaced to the user.
For instance network portions of the 'servers' object may get impacted
by Neutron.
With all those possibilities, putting in the extra ~8 bytes to handle
contingencies seemed prudent.
-Sean
--
Sean Dague
http://dague.net
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
More information about the OpenStack-dev
mailing list