---- On Wed, 08 Aug 2018 07:27:06 +0900 Monty Taylor <mord...@inaugust.com>
wrote ----
> On 08/07/2018 05:03 PM, Akihiro Motoki wrote:
> > Hi Cinder and API-SIG folks,
> >
> > During reviewing a horizon bug [0], I noticed the behavior of Cinder API
> > 3.0 was changed.
> > Cinder introduced more strict schema validation for creating/updating
> > volume encryption type
> > during Rocky and a new micro version 3.53 was introduced[1].
> >
> > Previously, Cinder API like 3.0 accepts unused fields in POST requests
> > but after [1] landed unused fields are now rejected even when Cinder API
> > 3.0 is used.
> > In my understanding on the microversioning, the existing behavior for
> > older versions should be kept.
> > Is it correct?
>
> I agree with your assessment that 3.0 was used there - and also that I
> would expect the api validation to only change if 3.53 microversion was
> used.
+1. As you know, neutron also implemented strict validation in Rocky but with
discovery via config option and extensions mechanism. Same way Cinder should
make it with backward compatible way till 3.53 version.
-gmann
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
