Hi all, Lately I've been spending more time looking at tripleo and doing some reviews. I'm particularly interested in helping the no-mergepy and subsequent puppet-software-config implementations mature (as well as improving overcloud updates via heat).
Since Tomas's patch landed to enable --no-mergepy in tripleo-heat-templates, it's become apparent that frequently patches are submitted which only update overcloud-source.yaml, so I've been trying to catch these and ask for a corresponding change to e.g controller.yaml. This raises the following questions: 1. Is it reasonable to -1 a patch and ask folks to update in both places? 2. How are we going to handle this duplication and divergence? 3. What's the status of getting gating CI on the --no-mergepy templates? 4. What barriers exist (now that I've implemented the eliding functionality requested for ResourceGroup) to moving to the --no-mergepy implementation by default? Thanks for any clarification you can provide! :) Steve  https://review.openstack.org/#/c/123100/  https://review.openstack.org/#/c/128365/  https://review.openstack.org/#/c/123713/ _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev