Bug 1334463

Summary: [RFE] Multi-environment support in heat-engine
Product: Red Hat OpenStack Reporter: Jaromir Coufal <jcoufal>
Component: openstack-heatAssignee: Jay Dobies <jason.dobies>
Status: CLOSED ERRATA QA Contact: Amit Ugol <augol>
Severity: unspecified Docs Contact:
Priority: high    
Version: 9.0 (Mitaka)CC: ddomingo, jjoyce, mburns, nlevinki, rhel-osp-director-maint, sbaker, shardy, srevivo
Target Milestone: gaKeywords: FutureFeature
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-heat-6.0.0-1.el7ost Doc Type: Enhancement
Doc Text:
When multiple environment files are specified, they are combined in the engine instead of the client. This provides heat enough information to correctly orchestrate a stack.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-11 12:19:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1362719    

Description Jaromir Coufal 2016-05-09 16:49:10 UTC
When multiple environment files are specified, combine them in the engine instead of the client. This will give Heat enough information to do the Right Thing on PATCH updates.

Blueprint:
* https://blueprints.launchpad.net/heat/+spec/multi-environments

Comment 3 Amit Ugol 2016-07-24 01:57:29 UTC
I will be confident to mark this one as verified after successful upgrades and updates as well.

Comment 5 Amit Ugol 2016-08-04 16:30:50 UTC
Since this cannot be tested by a user, I had to wait until enough time and testing was done. regular testing on heat in osp9 and also upgrading from 8 to 9 and running tests post upgrades are enough to convince me that this new feature is working well.

Comment 7 errata-xmlrpc 2016-08-11 12:19:25 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-1597.html