[openstack-dev] [TripleO] [CI] Cinder/Ceph CI setup
duncan.thomas at gmail.com
Thu Nov 27 10:21:29 UTC 2014
I'd suggest starting by making it an extra job, so that it can be monitored
for a while for stability without affecting what is there.
I'd be supportive of making it the default HA job in the longer term as
long as the LVM code is still getting tested somewhere - LVM is still the
reference implementation in cinder and after discussion there was strong
resistance to changing that.
I've no strong opinions on the node layout, I'll leave that to more
knowledgable people to discuss.
Is the ceph/tripleO code in a working state yet? Is there a guide to using
On 26 November 2014 at 13:10, Giulio Fidente <gfidente at redhat.com> wrote:
> hi there,
> while working on the TripleO cinder-ha spec meant to provide HA for Cinder
> via Ceph , we wondered how to (if at all) test this in CI, so we're
> looking for some feedback
> first of all, shall we make Cinder/Ceph the default for our (currently
> non-voting) HA job? (check-tripleo-ironic-overcloud-precise-ha)
> current implementation (under review) should permit for the deployment of
> both the Ceph monitors and Ceph OSDs on either controllers, dedicated
> nodes, or to split them up so that only OSDs are on dedicated nodes
> what would be the best scenario for CI?
> * a single additional node hosting a Ceph OSD with the Ceph monitors
> deployed on all controllers (my preference is for this one)
> * a single additional node hosting a Ceph OSD and a Ceph monitor
> * no additional nodes with controllers also service as Ceph monitor and
> Ceph OSD
> more scenarios? comments? Thanks for helping
> 1. https://blueprints.launchpad.net/tripleo/+spec/tripleo-kilo-cinder-ha
> Giulio Fidente
> GPG KEY: 08D733BA
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev