Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

Thanks Amit, I'll do this as well. Eduard On Thu, Oct 30, 2014 at 3:09 PM, Amit Das wrote: > Hey Eduard, > > We posted our driver cert result by creating a new bugzilla ticket & > tagging that as driver-cert. > > https://bugs.launchpad.net/cinder/+bug/1380126 > > > > Regards, > Amit > *CloudBy

Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

Hey Eduard, We posted our driver cert result by creating a new bugzilla ticket & tagging that as driver-cert. https://bugs.launchpad.net/cinder/+bug/1380126 Regards, Amit *CloudByte Inc.* On Thu, Oct 30, 2014 at 5:55 PM, Eduard Matei < eduard.ma...@cloudfounders.co

Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

Hi Mike, I saw your comment on my review, but i need some more info regarding "Your driver passes the cert test and the results are posted." I assume you mean running cinder_driver_cert.sh - this is already passing - but how do i get the results posted, and where? I've been looking through some doc

Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

On 19:41 Thu 04 Sep , Duncan Thomas wrote: > Hi > > during this week's cinder weekly meeting [1], we discussed plans for > Kilo, a discussion that started at the mid-cycle meetup [2]. The > outcome is that we (the cinder core team and extended community) want > to focus on stability and code c

Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

Thanks. I have done that. Regards, Amit *CloudByte Inc.* On Mon, Sep 8, 2014 at 9:37 AM, Mike Perez wrote: > On 17:18 Sun 07 Sep , Amit Das wrote: > > I had submitted the "CloudByte" driver code during juno and currently > > grappling with various aspects of sett

Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

On 17:18 Sun 07 Sep , Amit Das wrote: > I had submitted the "CloudByte" driver code during juno and currently > grappling with various aspects of setting up the CI for the same. It also > requires a copy of tempest logs which also is a in progress item. > > Will above be automatically eligible

Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

Hi, Thanks for clarification w.r.t cinder drivers. I had submitted the "CloudByte" driver code during juno and currently grappling with various aspects of setting up the CI for the same. It also requires a copy of tempest logs which also is a in progress item. Will above be automatically eligible