[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[rdo-list] python-heat-agent subpackage from openstack-heat-templates

Hi All

I would like to get some feedback on this packaging change:

This change creates a new subpackage python-heat-agent out of

Currently image building or boot configuration has to do a number of
non-obvious steps to end up with a server ready to perform heat-driven
software deployments.

The package python-heat-agent installs all dependencies and files
required to do this, resulting in a boot config on a pristine image
being as simple as:

        yum -y install https://www.rdoproject.org/repos/rdo-release.rpm
        yum -y install python-heat-agent
        systemctl enable os-collect-config
        systemctl start --no-block os-collect-config

python-heat-agent installs one hook which allows configuration via
heat templates. The aim is to create another subpackage per
configuration tool hook in heat-templates. So python-heat-agent-puppet
will install the puppet hook and depend on python-heat-agent and
puppet packages.

This depends on some upstream heat-templates changes:

As far as TripleO goes, this packaging approach has the potential to eliminate the need for diskimage-builder invoking heat-templates elements, and further reducing the use of tripleo-image-elements - I'd like to have a discussion on openstack-dev around whether there should be a push to remove tripleo-image-elements entirely.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]