[openstack-dev] [TripleO] Strategy for testing and merging the merge.py-free templates

2014-10-14 Thread Tomas Sedovic
Hi everyone, As outlined in the Remove merge.py[1] spec, Peter Belanyi and I have built the templates for controller, nova compute, swift and cinder nodes that can be deploying directly to Heat (i.e. no merge.py pass is necessary). The patches: https://review.openstack.org/#/c/123100/

Re: [openstack-dev] [TripleO] Strategy for testing and merging the merge.py-free templates

2014-10-14 Thread Tomas Sedovic
On 10/14/2014 12:43 PM, Steven Hardy wrote: On Tue, Oct 14, 2014 at 10:55:30AM +0200, Tomas Sedovic wrote: Hi everyone, As outlined in the Remove merge.py[1] spec, Peter Belanyi and I have built the templates for controller, nova compute, swift and cinder nodes that can be deploying directly

Re: [openstack-dev] [TripleO] Strategy for testing and merging the merge.py-free templates

2014-10-14 Thread Steven Hardy
On Tue, Oct 14, 2014 at 01:27:20PM +0200, Tomas Sedovic wrote: On 10/14/2014 12:43 PM, Steven Hardy wrote: On Tue, Oct 14, 2014 at 10:55:30AM +0200, Tomas Sedovic wrote: Hi everyone, As outlined in the Remove merge.py[1] spec, Peter Belanyi and I have built the templates for controller,

Re: [openstack-dev] [TripleO] Strategy for testing and merging the merge.py-free templates

2014-10-14 Thread Gregory Haynes
Excerpts from Tomas Sedovic's message of 2014-10-14 08:55:30 +: James Slagle proposed something like this when I talked to him on IRC: 1. teach devtest about the new templates, driven by a OVERCLOUD_USE_MERGE_PY switch (defaulting to the merge.py-based templates) 2. Do a CI run of the