[openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo
Bhandaru, Malini K
malini.k.bhandaru at intel.com
Tue Mar 17 03:06:52 UTC 2015
+1 Rob. Warning could carry/indicate all the attributes ignored.
From: Robert Collins [mailto:robertc at robertcollins.net]
Sent: Monday, March 16, 2015 7:56 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo
On 17 March 2015 at 14:27, Ken'ichi Ohmichi <ken1ohmichi at gmail.com> wrote:
>> I am worried about SDKs making requests that have additional JSON
>> attributes that were previously ignored by v2, but will be considered
>> invalid by the v2.1 validation code. If we were to just strip out the
>> extra items, rather than error out the request (when you don't
>> specify a microversion), I would be less worried about the
>> transition. Maybe that what we do?
> Nice point.
> That is a main difference in API behaviors between v2 and v2.1 APIs.
> If SDKs pass additional JSON attributes to Nova API now, developers
> need to fix/remove these attributes because that is a bug on SDKs
> These attributes are unused and meaningless, so some APIs of SDKs
> would contain problems if passing this kind of attributes.
> Sometime it was difficult to know what are available attributes before
> v2.1 API, so "The full monty approach" will clarify problems of SDKs
> and make SDKs' quality better.
> Ken Ohmichi
Better at the cost of forcing all existing users to upgrade just to keep using code of their own that already worked.
Not really 'better' IMO. Different surely.
We could (should) add Warning: headers to inform about this, but breaking isn't healthy IMO.
Robert Collins <rbtcollins at hp.com>
HP Converged Cloud
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev