[openstack-dev] [cinder] about block device driver

Rambo lijie at unitedstack.com
Tue Jul 17 09:24:00 UTC 2018


yes
 
 
------------------ Original ------------------
From:  "Ivan Kolodyazhny"<e0ne at e0ne.info>;
Date:  Tue, Jul 17, 2018 05:00 PM
To:  "OpenStack Developmen"<openstack-dev at lists.openstack.org>; 

Subject:  Re: [openstack-dev] [cinder] about block device driver

 
Do you use the volumes on the same nodes where instances are located?

Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/



 
On Tue, Jul 17, 2018 at 11:52 AM, Rambo <lijie at unitedstack.com> wrote:
yes,My cinder driver is  LVM+LIO.I have upload the test result in  appendix.Can you show me your test results?Thank you!



 
 
------------------ Original ------------------
From:  "Ivan Kolodyazhny"<e0ne at e0ne.info>;
Date:  Tue, Jul 17, 2018 04:09 PM
To:  "OpenStack Developmen"<openstack-dev at lists.openstack.org>; 

Subject:  Re: [openstack-dev] [cinder] about block device driver



 
Rambo,

Did you try to use LVM+LIO target driver? It shows pretty good performance comparing to BlockDeviceDriver,


Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/



 
On Tue, Jul 17, 2018 at 10:24 AM, Rambo <lijie at unitedstack.com> wrote:
Oh,the instances using Cinder perform intense I/O, thus iSCSI or LVM is not a viable option - benchmarked them several times, unsatisfactory results.Sometimes it's IOPS is twice as bad,could you show me your test data?Thank you!





Cheers,
Rambo
 
 
------------------ Original ------------------
From: "Sean McGinnis"; 
Date: 2018年7月16日(星期一) 晚上9:32
To: "OpenStack Developmen"; 
Subject: Re: [openstack-dev] [cinder] about block device driver

 
On Mon, Jul 16, 2018 at 01:32:26PM +0200, Gorka Eguileor wrote:
> On 16/07, Rambo wrote:
> > Well,in my opinion,the BlockDeviceDriver is more suitable than any other solution for data processing scenarios.Does the community will agree to merge the BlockDeviceDriver to the Cinder repository again if our company hold the maintainer and CI?
> >
> 
> Hi,
> 
> I'm sure the community will be happy to merge the driver back into the
> repository.
> 

The other reason for its removal was its inability to meet the minimum feature
set required for Cinder drivers along with benchmarks showing the LVM and iSCSI
driver could be tweaked to have similar or better performance.

The other option would be to not use Cinder volumes so you just use local
storage on your compute nodes.

Readding the block device driver is not likely an option.

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at 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-request at 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-request at lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180717/ea1a9fa7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D7C81B68 at 5B350B78.B0B54D5B
Type: application/octet-stream
Size: 22282 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180717/ea1a9fa7/attachment.obj>


More information about the OpenStack-dev mailing list