The motivation for Ceph support in my case was for my company to work on nova/glance RBD support and horizon integration with Ceph storage. The nova support for RBD backing store is not currently mature, and subject to a great deal of debate. Also boot from volume support used by Cinder/Ceph in the openstack dashboard has a terrible workflow and needs serious attention. Having an environment to easily stand up a stack for development with Ceph already configured has been a large help. Most of our development team (and other openstack developers with which I've spoken) don't have time or want to be bothered with learning the complicated setup routine involved with Ceph. They would however happily develop support against the API if it was already there and waiting for them.
The plugin architecture of devstack felt like a nice place to add features and optional functionality that wouldn't impact users who didn't want or care about the extra features. I do understand your standpoint on the issue, and that you wouldn't want devstack to become a collection of broken un-maintained plugins for everything under the sun. But this was not intended for driver certification, rather to drive current active core feature development in openstack. Hope this at least gives everyone a better idea of my intent with the Blueprint. David Pippenger Sr. Devops Engineer Metacloud Inc. David Pippenger Sr. Devops Engineer Metacloud Inc. 1-213-253-8513 On Thu, Dec 26, 2013 at 9:16 AM, John Griffith <john.griff...@solidfire.com>wrote: > On Tue, Dec 24, 2013 at 4:49 AM, Sebastien Han > <sebastien....@enovance.com> wrote: > > Hello everyone, > > > > I’ve been working on a new feature for Devstack that includes a native > support for Ceph. > > The patch includes the following: > > > > * Ceph installation (using the ceph.com repo) > > * Glance integration > > * Cinder integration (+ nova virsh secret) > > * Cinder backup integration > > * Partial Nova integration since master is currently broken. Lines are > already there, the plan is to un-comment those lines later. > > * Everything works with Cephx (Ceph authentification system). > > > > Does anyone will be interested to see this going into Devstack > mainstream? > > > > I'm likely in the minority here, but personally I don't like the idea > of adding every driver/backend combination option directly in > devstack. The issue I think you're trying to solve here is exactly > what the driver_cert scripts and result submission are intended to > address. > > If there's interest in creating an additional gating job that uses RBD > as the backend that's in my mind a different discussion and definitely > worth having. > > > Cheers. > > > > –––– > > Sébastien Han > > Cloud Engineer > > > > "Always give 100%. Unless you're giving blood.” > > > > Phone: +33 (0)1 49 70 99 72 > > Mail: sebastien....@enovance.com > > Address : 10, rue de la Victoire - 75009 Paris > > Web : www.enovance.com - Twitter : @enovance > > > > > > _______________________________________________ > > OpenStack-dev mailing list > > OpenStack-dev@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
