Ask Your Question
1

Cinder Local Storage Options on >=Mitaka

asked 2016-10-11 14:44:26 -0500

rfxnryan gravatar image

Looking for a strategy to have Cinder manage local storage on a per-compute node basis. Ideally, Cinder would not attach volumes over iSCSI since logical volumes would be local.

The current operating assumption is having each nova compute node tied to a matching configured cinder availability zone (volume_group). Volume creation then takes place on e.g availability zone cinder-compute01 where, as part of a host aggregate, compute01 node is a member of.

This works to the extent that volumes are being attached locally but over iSCSI on instance creation. This feels suboptimal and introduces a point of failure that simply is not needed.

End goal is to leverage SSD local storage on all compute nodes.

Running Mitaka on CentOS 7.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-10-14 12:41:18 -0500

I thought this was the goal and purpose of CEPH; Scale out with white box and local disks; No SAN no RAID, primarily local fast SSD to support scale out environments, like noSQL and Casandra.

https://www.openstack.org/summit/openstack-summit-hong-kong-2013/session-videos/presentation/ceph-the-de-facto-storage-backend-for-openstack (https://www.openstack.org/summit/open...)

http://docs.ceph.com/docs/jewel/start/hardware-recommendations/ (http://docs.ceph.com/docs/jewel/start...)

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-10-11 14:44:26 -0500

Seen: 561 times

Last updated: Oct 11 '16