[openstack-dev] [TripleO] config options, defaults, oh my!
Miller, Mark M (EB SW Cloud - R&D - Corvallis)
mark.m.miller at hp.com
Wed Apr 9 22:30:26 UTC 2014
Does anyone have a flowchart of the cloud build/configure process including interactions between the various components/stages of TripleO and Heat?
-----Original Message-----
From: Robert Collins [mailto:robertc at robertcollins.net]
Sent: Wednesday, April 09, 2014 2:29 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [TripleO] config options, defaults, oh my!
On 10 April 2014 08:33, Clint Byrum <clint at fewbar.com> wrote:
>
> This is exactly what we're doing. We're just suggesting exposing
> variations in the Heat templates, rather than in the elements. It is
> worth noting that Heat has grown the ability to grab a local file and
> inject it into your template at runtime. I think it would actually
> make sense to have os-apply-config enhanced to be able to override
> whole template files based on something like this:
>
> resources:
> server1:
> metadata:
> template_overrides:
> "/etc/nova/nova.conf":
> get_file [ "my_special_nova.conf.template" ]
>
> In that, we achieve what you want, but we can do so without rebuilding
> the whole image.
This makes me a little nervous: its much easier to break os-collect-config by forcing os-apply-config to break hard this way, than through bad metadata. I think I'm ok with the sentiment, but nervous about impl.
-Rob
--
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
More information about the OpenStack-dev
mailing list