[openstack-dev] incubating diskimage-builder?

Mark Washenberger mark.washenberger at markwash.net
Sun May 26 07:11:31 UTC 2013

On Sat, May 25, 2013 at 12:21 PM, Robert Collins
<robertc at robertcollins.net>wrote:

> Seeking opinions - should I put forward diskimage-builder for
> incubation. Reddwarf, which is incubated, depends on diskimage-builder
> for it's tests, and thats great - but at the same time I feel a little
> odd about having an integrated project depend on a stackforge project.
> Diskimage-builder isn't a whole lot of code, but thats deliberate ;).
> It is however something I suspect will end up in the inner loop of a
> bunch of projects as people get familiar with it's utility. Maybe it
> should be an oslo component  [though its 95% shell], or maybe it
> should be 'part of' glance in the same way python-glanceclient is
> 'part of' glance.
>  I'd be delighted to collaborate with any of the PTL's in OpenStack
> today - but fFor all that it's small, it has it's own unique
> challenges in keeping it flexible, fast and safe, so I feel hesitant
> about simply handing guidance of it over to PTL control in the context
> of a project which is API focused : this is low level OS plumbing
> which it's own problem domain.

Ahem. . . I'm guessing you're talking about Glance here?
No worries, though. I think we can all agree there is a huge difference
between an API that publishes images and a tool for building images.

My question is, are you trying to begin handing off diskimage-builder? Or
are you just figuring that joining another project would necessarily mean
you have to lose a certain level of control? Just trying to get a sense of
your motivations and how they inform your (very much appreciated) concerns.

FWIW, if diskimage-builder joined Glance during my tenure, I'd think it
best for me to be pretty hands off--in part because you clearly know what
you're doing with the project--in part because I clearly would not know
what I was doing with it :-).

But that's not to say that a future Glance PTL wouldn't be well positioned
to appreciate and manage the different focuses of each project. I'm very
eager to hear other folk's opinions. In an ideal world, would these two
projects have a strong reason to share technical leadership?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130526/f092320c/attachment.html>

More information about the OpenStack-dev mailing list