Back to bug 1042153

Who When What Removed Added
RHOS Integration 2013-12-12 21:13:14 UTC Keywords FutureFeature
Whiteboard upstream_milestone_icehouse-2 upstream_status_needs-code-review
Red Hat Bugzilla 2013-12-12 21:13:14 UTC Doc Type Bug Fix Enhancement
RHOS Integration 2013-12-17 00:44:35 UTC Whiteboard upstream_milestone_icehouse-2 upstream_status_needs-code-review upstream_milestone_icehouse-2 upstream_status_implemented
John Skeoch 2014-01-13 01:15:40 UTC CC hateya
Stephen Gordon 2014-01-23 20:50:56 UTC Status NEW POST
RHOS Integration 2014-02-19 22:24:12 UTC Whiteboard upstream_milestone_icehouse-2 upstream_status_implemented upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_approved
RHOS Integration 2014-02-20 16:01:34 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 17:22:28 UTC Target Release --- 5.0
RHOS Integration 2014-02-20 17:53:20 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 18:25:14 UTC Target Release --- 5.0
RHOS Integration 2014-02-20 21:47:19 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 22:18:32 UTC Target Release --- 5.0
Scott Lewis 2014-03-26 18:41:39 UTC CC sbaker, sdake, shardy
Component RFEs openstack-heat
Amit Ugol 2014-04-02 12:24:08 UTC CC augol
QA Contact augol
Steven Dake 2014-04-08 16:46:31 UTC Priority unspecified urgent
Doc Text Feature:
The ability to run multiple Heat engines simulatenously with one database backend is implemented.

Reason:
Support for horizontal scalability.

Result (if any):
Multiple heat engines can be run with multiple heat apis and correct results will occur.
Ami Jeain 2014-04-09 11:21:07 UTC CC ajeain
Amit Ugol 2014-06-06 10:23:04 UTC Status POST VERIFIED
Don Domingo 2014-06-25 02:54:33 UTC CC ddomingo
Doc Text Feature:
The ability to run multiple Heat engines simulatenously with one database backend is implemented.

Reason:
Support for horizontal scalability.

Result (if any):
Multiple heat engines can be run with multiple heat apis and correct results will occur.
With this release, you can now run multiple Orchestration engines simultaneously with just one database back-end. This feature adds horizontal scalability to the Orchestration service.
Flags needinfo?(sbaker)
errata-xmlrpc 2014-07-07 12:05:33 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2014-07-08 15:32:47 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2014-07-08 11:32:47 UTC
Steve Baker 2015-02-23 21:41:01 UTC Flags needinfo?(sbaker)

Back to bug 1042153