Open Stack

On 25 June 2013 23:17, Sean Dague <sean at dague.net> wrote:
> Cool proposed change coming in from the Heat folks -
> https://review.openstack.org/#/c/34278/ to use dib to build their base
> images in devstack. From a development perspective, will make experimenting
> with Heat a lot easier.
>
> However, this raises an issue as we look towards using this in the gate,
> because diskimage-builder isn't currently gated by devstack-gate. But if
> Heat wants to use it we're talking about pulling upstream master as part of
> the build. Which opens us up to an asymmetric gate where a dib change can
> land which breaks the gate, then all nova changes are blocked from merging
> until it gets in.

Right - this is the larger version of the issue that prompted me to
send http://lists.openstack.org/pipermail/openstack-dev/2013-May/009539.html.

> I think we need to be really explicit that on the gate, every git tree we
> pull in is also gated, to ensure nothing breaks other projects ability to
> merge code. Asymmetric gating is no fun.
>
> This gets a little odder in that dib is out on stackforge and not as part of
> an openstack* github tree. Which on the one hand is just naming, on the
> other hand if heat's going to need that to get through the gate, maybe we
> should rethink it being on stackforge vs. openstack-dev?

diskimage-builder isn't a dev tool. The next step for it in terms of
moving from one place to another IMNSHO, is the openstack org. Unless
we end up with per-program orgs, in which case it probably moves back
from stackforge to 'tripleo' or to 'openstack-tripleo' or whatever.

But the main thing needed is for diskimage-builder changes to be gated
well enough to make accidental breakage that can affect tempest runs a
very low probability, Steve Baker was talking about doing that on IRC
yesterday, so we should have something in place soon.

-Rob

-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Cloud Services