Re: [openstack-dev] [qa][cinder] critical fix for ceph job

On Tue, Apr 11, 2017 at 4:05 AM, Jon Bernard wrote: > * Matt Riedemann wrote: >> On 4/7/2017 9:43 AM, Jordan Pittier wrote: >> > >> > >> > On Fri, Apr 7, 2017 at 4:15 PM, Ghanshyam Mann > > > wrote: >> > >> > Thanks. I am not sure these kind of driver specific

Re: [openstack-dev] [qa][cinder] critical fix for ceph job

* Matt Riedemann wrote: > On 4/7/2017 9:43 AM, Jordan Pittier wrote: > > > > > > On Fri, Apr 7, 2017 at 4:15 PM, Ghanshyam Mann > > wrote: > > > > Thanks. I am not sure these kind of driver specific behavior on APIs > > side. This bring up question that

Re: [openstack-dev] [qa][cinder] critical fix for ceph job

On 4/7/2017 9:43 AM, Jordan Pittier wrote: On Fri, Apr 7, 2017 at 4:15 PM, Ghanshyam Mann mailto:ghanshyamm...@gmail.com>> wrote: Thanks. I am not sure these kind of driver specific behavior on APIs side. This bring up question that should not cinder APIs be consistent from usage p

Re: [openstack-dev] [qa][cinder] critical fix for ceph job

On Fri, Apr 7, 2017 at 4:15 PM, Ghanshyam Mann wrote: > Thanks. I am not sure these kind of driver specific behavior on APIs > side. This bring up question that should not cinder APIs be consistent > from usage point. In this case[1], create backup API can accept > 'container' param and do/don't

Re: [openstack-dev] [qa][cinder] critical fix for ceph job

Thanks. I am not sure these kind of driver specific behavior on APIs side. This bring up question that should not cinder APIs be consistent from usage point. In this case[1], create backup API can accept 'container' param and do/don't create pool as per configured driver? Then have better documenta

[openstack-dev] [qa][cinder] critical fix for ceph job

I just posted a critical fix the ceph job [1]. I'm anxious to get this landed so I can start working on the other intermittent failures in the gate. Any feedback is much appreciated. [1] https://review.openstack.org/#/c/454321/ -- Jon __