Steve Baker <sba...@redhat.com> wrote on 10/15/2013 06:48:53 PM: > From: Steve Baker <sba...@redhat.com> > To: openstack-dev@lists.openstack.org, > Date: 10/15/2013 06:51 PM > Subject: [openstack-dev] [Heat] HOT Software configuration proposal > > I've just written some proposals to address Heat's HOT software > configuration needs, and I'd like to use this thread to get some feedback: > https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config
In that proposal, each component can use a different configuration management tool. > https://wiki.openstack.org/wiki/Heat/Blueprints/native-tools-bootstrap-config In this proposal, I get the idea that it is intended that each Compute instance run only one configuration management tool. At least, most of the text discusses the support (e.g., the idea that each CM tool supplies userdata to bootstrap itself) in terms appropriate for a single CM tool per instance; also, there is no discussion of combining userdata from several CM tools. I agree with the separation of concerns issues that have been raised. I think all this software config stuff can be handled by a pre-processor that takes an extended template in and outputs a plain template that can be consumed by today's heat engine (no extension to the heat engine necessary). Regards, Mike
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
