[openstack-dev] os-*-config in tripleo repositories

Robert Collins robertc at robertcollins.net
Fri Jan 10 02:38:22 UTC 2014

On 10 January 2014 02:13, Derek Higgins <derekh at redhat.com> wrote:
> It looks like we have some duplication and inconsistencies on the 3
> os-*-config elements in the tripleo repositories
> os-apply-config (duplication) :
>    We have two elements that install this
>      diskimage-builder/elements/config-applier/
>      tripleo-image-elements/elements/os-apply-config/
>    As far as I can tell the version in diskimage-builder isn't used by
> tripleo and the upstart file is broke
> ./dmesg:[   13.336184] init: Failed to spawn config-applier main
> process: unable to execute: No such file or directory
>    To avoid confusion I propose we remove
> diskimage-builder/elements/config-applier/ (or deprecated if we have a
> suitable process) but would like to call it out here first to see if
> anybody is using it or thinks its a bad idea?
> inconsistencies
>   os-collect-config, os-refresh-config : these are both installed from
> git into the global site-packages
>   os-apply-config : installed from a released tarball into its own venv
>   To be consistent with the other elements all 3 I think should be
> installed from git into its own venv, thoughts?

We deliberately moved to using releases to match the whole
production-ready concept. So +1 on the other bits, but -2 on using

We should use the git version when landing a change to the package,
the released version otherwise.


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

More information about the OpenStack-dev mailing list