On 09/04/14 10:09, Robert Collins wrote: > We had a long chat about this in the meeting today. > > we had rough consensus on the following path of action > > - we'll put together a quick-but-effective config passthrough > mechanism, with a goal of landing it in the next few days > - it needs to handle tie and tht - we need a pass through vector for heat too > - the huge swath of 'and we need to configure X' patches can then be > taken off the table and instead be worked through much more gracefully > as either > - a) bugs where defaults are inappropriate (and this is known to > often be contentious) > - b) changes to tripleo to model and expose frequently used knobs > - we'll later review the passthrough and decide on an ideal > implementation and migration plan to such implementation - the folk > who have all these config changes cascading into TripleO will be able > to drive such implementation down the track. > > I'm making an etherpad now - > https://etherpad.openstack.org/p/tripleo-config-passthrough > > I've put a couple of options in the etherpad, one which assumes the merging of the software-config changes[1] and another which also assumes a port to HOT templates.
[1] https://review.openstack.org/#/c/81666/12 _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
