I've been running Ceph-backed Cinder since, I think, Icehouse. It's really more of a function of your backend or the hypervisor than Cinder itself. That being said, it's been probabky mt smallest Openstack pain point iver the years.
I can't imagine what sort of concurrency issues you'd run into short of a large public cloud given that it really doesn't do much once provisioning a volume is complete. Maybe if you've got people taking a ton of snapshots? What sort of specific issues are you concerned about? -Erik On May 31, 2017 8:30 PM, "Mike Lowe" <joml...@iu.edu> wrote: > We have run ceph backed cinder from Liberty through Newton, with the > exception of a libvirt 2.x bug that should now be fixed, cinder really > hasn't caused us any problems. > > Sent from my iPad > > > On May 31, 2017, at 6:12 PM, Joshua Harlow <harlo...@fastmail.com> > wrote: > > > > Hi folks, > > > > So I was having some back and forth internally about is cinder ready for > usage and wanted to get other operators thoughts on how there cinder > experiences have been going, any trials and tribulations. > > > > For context, we are running on liberty (yes I know, working on getting > that to newer versions) and folks in godaddy are starting to use more and > more cinder (backed by ceph) and that got me thinking about asking the > question from operators (and devs) on what kind of readiness 'rating' (or > whatever you would want to call it) would people give cinder in liberty. > > > > Some things that I was thinking was around concurrency rates, because I > know that's be a common issue that the cinder developers have been working > through (using tooz, and various other lock mechanisms and such). > > > > Have other cinder operators seen concurrent operations (or conflicting > operations or ...) work better in newer releases (is there any metric/s > anyone has gathered about how things have gotten worse/better under scale > for cinder in various releases? partically with regard to using ceph). > > > > Thoughts? > > > > It'd be interesting to capture (not just for my own usage) I think > because such info helps the overall user and operator and dev community > (and yes I would expect various etherpads to have parts of this > information, but it'd be nice to have like a single place where other > operators can specify how ready they believe a project is for a given > release and for a given configuration; and ideally provide details/comments > as to why they believe this). > > > > -Josh > > > > > > > > > > _______________________________________________ > > OpenStack-operators mailing list > > OpenStack-operators@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
