diff options
| author |   Zane Bitter <zbitter@redhat.com> | 2017-02-03 17:52:10 -0500 |
|---|---|---|
| committer |   Emilien Macchi <emilien@redhat.com> | 2017-02-27 12:18:40 +0000 |
| commit | 94e27e64d469d6a25c9e7b5dca2f06a5479268a7 (patch) | |
| tree | 834c36acc06da9a089fefb8c383d653e970d78a5 /network/ports/storage_mgmt_from_pool_v6.yaml | |
| parent | 8c9cef20efb663983e45f6234c211b7443423804 (diff) | |
Don't recalculate EndpointMap to get outputs
As of Ocata, whenever Heat needs to get the value of an output from a
nested Stack it will still load the Stack in memory and re-resolve the
output value. This means that the EndpointMap's endpoint_map output, which
is huge, gets loaded and recalculated whenever showing the EndpointMap or
KeystoneUrl outputs of the main (overcloud) stack. To avoid this, store the
value locally in an OS::Heat::Value resource. This means that the
EndpointMap will only be resolved once, during the stack create/update, and
the outputs can refer to that value.
Related-Bug: #1661728
Change-Id: Ia79eceeea309f5508713a310849f5d366a035430
Depends-On: If0f80cab94c28514d1569b1025362ab9d9d31512
(cherry picked from commit b2ee58c7f6883011b4ba8b387eedc63d3600aea0)
Diffstat (limited to 'network/ports/storage_mgmt_from_pool_v6.yaml')
0 files changed, 0 insertions, 0 deletions