On Wed, Aug 08, 2018 at 05:15:26PM +, Sean McGinnis wrote:
> On Tue, Aug 07, 2018 at 05:27:06PM -0500, Monty Taylor 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
> >
On Tue, Aug 07, 2018 at 05:27:06PM -0500, Monty Taylor 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 cr
> > >
> > > 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 ke
On Wed, 08 Aug 2018 07:27:06 +0900 Monty Taylor
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 sch
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 versio
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 l
