Open Stack

On 03/06/2014 05:37 PM, Andrew Woodward wrote:
> Matt,
>
> I'd love to see this too, however I'm not seasoned enough to even know
> much about how to start implementing that. I'd love some direction,
> and maybe some support after you guys are done with the pending
> release.

We're working on setting up CI with Ceph starting with Cinder.
Jay Pipes' recent blog posts explaining this process are great:

http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/

Josh

> As others have illustrated here, the current RBD support in nova is
> effectively useless and I'd love to see that second sponsor so us Ceph
> users don't have to use hand patched nova for another release.
>
> On Thu, Mar 6, 2014 at 3:30 PM, Matt Riedemann
> <mriedem at linux.vnet.ibm.com> wrote:
>>
>>
>> On 3/6/2014 2:20 AM, Andrew Woodward wrote:
>>>
>>> I'd Like to request A FFE for the remaining patches in the Ephemeral
>>> RBD image support chain
>>>
>>> https://review.openstack.org/#/c/59148/
>>> https://review.openstack.org/#/c/59149/
>>>
>>> are still open after their dependency
>>> https://review.openstack.org/#/c/33409/ was merged.
>>>
>>> These should be low risk as:
>>> 1. We have been testing with this code in place.
>>> 2. It's nearly all contained within the RBD driver.
>>>
>>> This is needed as it implements an essential functionality that has
>>> been missing in the RBD driver and this will become the second release
>>> it's been attempted to be merged into.
>>>
>>> Andrew
>>> Mirantis
>>> Ceph Community
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>> What would be awesome in Juno is some CI around RBD/Ceph.  I'd feel a lot
>> more comfortable with this code if we had CI running Tempest against that
>> type of configuration, just like how we are now requiring 3rd party CI for
>> virt drivers.
>>
>> I realize this is tangential but it would make moving these blueprints
>> through faster so you're not working on it over multiple releases.
>>
>> Having said that, I'm not signing up for sponsoring this, sorry. :)
>>
>> --
>>
>> Thanks,
>>
>> Matt Riedemann