Re: [openstack-dev] [cinder] [Sahara] Block Device Driver updates
Hi Zhidong, Unfortunately stable/kilo branch is opened only for security fixes now. So we can't backport this fix. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Mon, Nov 23, 2015 at 4:43 AM, Zhidong Yuwrote: > It seems there was a bug introduced in Kilo and then fixed in Liberty [6]. > However, since there are more users of Kilo than of Liberty, I am wondering > if the fix has been back ported to Kilo. I could not find it except for > this one [7] which seems to be a different issue. > > [6] https://review.openstack.org/#/c/200039/ > [7] https://bugs.launchpad.net/cinder/+bug/1465819 > > On Thu, Oct 1, 2015 at 3:00 AM, Ivan Kolodyazhny wrote: > >> Hi team, >> >> I know that Block Device Driver (BDD) is not popular in Cinder community. >> The main issues were: >> >> * driver is not good maintained >> * it doesn't feet minimum features set >> * there is no CI for it >> * it's not a Cinder way/it works only when instance and volume are >> created on the same host >> * etc >> >> AFAK, it's widely used in Sahara & Hadoop communities because it works >> fast. I won't discuss driver's performance in this thread. I share my >> performance tests results once I'll finish it. >> >> I'm going to share drive updates with you about issues above. >> >> 1) driver is not good maintained - we are working on it right now and >> will fix any found issues. We've got devstack plugin [1] for this driver. >> >> 2) it doesn't feet minimum features set - I've filed a blueprint [2] for >> it. There are patches that implement needed features in the gerrit [3]. >> >> 3) there is no CI for it - In Cinder community, we've got strong >> requirement that each driver must has CI. I've absolutely agree with that. >> That's why new infra job is proposed [4]. >> >> 4) it works only when instance and volume are created on the same host - >> I've filed a blueprint [5] but after testing I've found that it's already >> implemented by [6]. >> >> >> I hope, I've answered all questions that were asked in IRC and in >> comments for [6]. I will do my best to support this driver and propose fix >> to delete if community decide to delete it from the cinder tree >> >> >> [1] https://github.com/openstack/devstack-plugin-bdd >> [2] >> https://blueprints.launchpad.net/cinder/+spec/block-device-driver-minimum-features-set >> [3] >> https://review.openstack.org/#/q/status:open+project:openstack/cinder+branch:master+topic:bp/block-device-driver-minimum-features-set,n,z >> [4] https://review.openstack.org/228857 >> [5] >> https://blueprints.launchpad.net/cinder/+spec/block-device-driver-via-iscsi >> [6] https://review.openstack.org/#/c/200039/ >> >> >> Regards, >> Ivan Kolodyazhny >> >> __ >> 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
Re: [openstack-dev] [cinder] [Sahara] Block Device Driver updates
It seems there was a bug introduced in Kilo and then fixed in Liberty [6]. However, since there are more users of Kilo than of Liberty, I am wondering if the fix has been back ported to Kilo. I could not find it except for this one [7] which seems to be a different issue. [6] https://review.openstack.org/#/c/200039/ [7] https://bugs.launchpad.net/cinder/+bug/1465819 On Thu, Oct 1, 2015 at 3:00 AM, Ivan Kolodyazhnywrote: > Hi team, > > I know that Block Device Driver (BDD) is not popular in Cinder community. > The main issues were: > > * driver is not good maintained > * it doesn't feet minimum features set > * there is no CI for it > * it's not a Cinder way/it works only when instance and volume are created > on the same host > * etc > > AFAK, it's widely used in Sahara & Hadoop communities because it works > fast. I won't discuss driver's performance in this thread. I share my > performance tests results once I'll finish it. > > I'm going to share drive updates with you about issues above. > > 1) driver is not good maintained - we are working on it right now and will > fix any found issues. We've got devstack plugin [1] for this driver. > > 2) it doesn't feet minimum features set - I've filed a blueprint [2] for > it. There are patches that implement needed features in the gerrit [3]. > > 3) there is no CI for it - In Cinder community, we've got strong > requirement that each driver must has CI. I've absolutely agree with that. > That's why new infra job is proposed [4]. > > 4) it works only when instance and volume are created on the same host - > I've filed a blueprint [5] but after testing I've found that it's already > implemented by [6]. > > > I hope, I've answered all questions that were asked in IRC and in comments > for [6]. I will do my best to support this driver and propose fix to delete > if community decide to delete it from the cinder tree > > > [1] https://github.com/openstack/devstack-plugin-bdd > [2] > https://blueprints.launchpad.net/cinder/+spec/block-device-driver-minimum-features-set > [3] > https://review.openstack.org/#/q/status:open+project:openstack/cinder+branch:master+topic:bp/block-device-driver-minimum-features-set,n,z > [4] https://review.openstack.org/228857 > [5] > https://blueprints.launchpad.net/cinder/+spec/block-device-driver-via-iscsi > [6] https://review.openstack.org/#/c/200039/ > > > Regards, > Ivan Kolodyazhny > > __ > 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
[openstack-dev] [cinder] [Sahara] Block Device Driver updates
Hi team, I know that Block Device Driver (BDD) is not popular in Cinder community. The main issues were: * driver is not good maintained * it doesn't feet minimum features set * there is no CI for it * it's not a Cinder way/it works only when instance and volume are created on the same host * etc AFAK, it's widely used in Sahara & Hadoop communities because it works fast. I won't discuss driver's performance in this thread. I share my performance tests results once I'll finish it. I'm going to share drive updates with you about issues above. 1) driver is not good maintained - we are working on it right now and will fix any found issues. We've got devstack plugin [1] for this driver. 2) it doesn't feet minimum features set - I've filed a blueprint [2] for it. There are patches that implement needed features in the gerrit [3]. 3) there is no CI for it - In Cinder community, we've got strong requirement that each driver must has CI. I've absolutely agree with that. That's why new infra job is proposed [4]. 4) it works only when instance and volume are created on the same host - I've filed a blueprint [5] but after testing I've found that it's already implemented by [6]. I hope, I've answered all questions that were asked in IRC and in comments for [6]. I will do my best to support this driver and propose fix to delete if community decide to delete it from the cinder tree [1] https://github.com/openstack/devstack-plugin-bdd [2] https://blueprints.launchpad.net/cinder/+spec/block-device-driver-minimum-features-set [3] https://review.openstack.org/#/q/status:open+project:openstack/cinder+branch:master+topic:bp/block-device-driver-minimum-features-set,n,z [4] https://review.openstack.org/228857 [5] https://blueprints.launchpad.net/cinder/+spec/block-device-driver-via-iscsi [6] https://review.openstack.org/#/c/200039/ Regards, Ivan Kolodyazhny __ 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