In the case of yum or apt package installation, I would recommend to give OS::Heat::CloudConfig a try, instead of sticking to cfn-init.
The function you proposed (Fn::MemberListToMap) actually brings us back to the previous discussion whether a mapping section is really needed in the native HOT template. My understanding was that people are more inclined to use provider templates for this kind of varieties or flexibilities. I am still feeling that we need a simple, intuitive, declarative way to specify maps/dicts for convenience. Provider templates, IMHO, are too heavy-weight for this. However, for keys, I don't know whether it is a good idea to make it a variable. Regards, Qiming On Tue, Apr 15, 2014 at 06:15:36PM -0400, Mike Spreitzer wrote: > Mike Spreitzer/Watson/IBM@IBMUS wrote on 04/15/2014 05:59:50 PM: > > > Yes, I can see how OS::Heat::Init makes sense. But is this just the > > first thing on a long list? Would it be better to have a static > > intrinsic that is like Python's dict(iterable of > > iterable)->dictionary function? > > .. and I see now that we do: Fn::MemberListToMap > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
