On 2016-04-19 15:34:16 -0400 (-0400), James Slagle wrote: > A fork would be unfortunate. What about a new repo that's just for > the elements used heavily by infra, e.g., > openstack-infra-elements. [...]
We do already have a bunch of elements in openstack-infra/project-config, so most of the velocity concerns have been around "upstream" elements (lately a number of the -minimal distro variants as we've been migrating our nodepool deployment to rely heavily on dib). Decoupling the elements in diskimage-builder from the framework and maintaining them in separately-versioned repositories might help, but regardless Infra team consensus has been primarily to just keep collaborating on those common elements and find downstream workarounds while we wait for bug fixing iteration to take place and releases to be tagged. > I definitely think dib is part of "OpenStack the Product" given it > has to be used by users and operators of TripleO. Makes sense! It's also possible some of the elements bundled in diskimage-builder aren't actually used in "OpenStack the Product" and are just along for the ride, but I don't really know enough about the other consuming projects to be able to say either way. -- Jeremy Stanley __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
