Re: [openstack-dev] [heat] Making stack outputs static

2017-06-13 Thread Ben Nemec
On 06/12/2017 03:53 PM, Zane Bitter wrote: On 12/06/17 16:21, Steven Hardy wrote: I think we wanted to move to convergence anyway so I don't see a problem with this. I know there was some discussion about starting to test with convergence in tripleo-ci, does anyone know what, if anything,

Re: [openstack-dev] [heat] Making stack outputs static

2017-06-12 Thread Zane Bitter
On 12/06/17 16:21, Steven Hardy wrote: I think we wanted to move to convergence anyway so I don't see a problem with this. I know there was some discussion about starting to test with convergence in tripleo-ci, does anyone know what, if anything, happened with that? There's an experimental job

Re: [openstack-dev] [heat] Making stack outputs static

2017-06-12 Thread Steven Hardy
On Mon, Jun 12, 2017 at 6:18 PM, Ben Nemec wrote: > > > On 06/09/2017 03:10 PM, Zane Bitter wrote: >> >> History lesson: a long, long time ago we made a very big mistake. We >> treated stack outputs as things that would be resolved dynamically when >> you requested them,

Re: [openstack-dev] [heat] Making stack outputs static

2017-06-12 Thread Ben Nemec
On 06/09/2017 03:10 PM, Zane Bitter wrote: History lesson: a long, long time ago we made a very big mistake. We treated stack outputs as things that would be resolved dynamically when you requested them, instead of having values fixed at the time the template was created or updated. This makes

[openstack-dev] [heat] Making stack outputs static

2017-06-09 Thread Zane Bitter
History lesson: a long, long time ago we made a very big mistake. We treated stack outputs as things that would be resolved dynamically when you requested them, instead of having values fixed at the time the template was created or updated. This makes performance of reading outputs slow,