| Summary: | [RFE][heat]: Implement support for scaling-out multiple engines | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> |
| Component: | openstack-heat | Assignee: | RHOS Maint <rhos-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | unspecified | CC: | ajeain, augol, ddomingo, markmc, sbaker, sdake, shardy, yeylon |
| Target Milestone: | Upstream M2 | Keywords: | FutureFeature |
| Target Release: | 5.0 (RHEL 7) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://blueprints.launchpad.net/heat/+spec/multiple-engines | ||
| Whiteboard: | upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_approved | ||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-08 15:32:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
RHOS Integration
2013-12-12 21:13:08 UTC
Moving to POST based on upstream status (Implemented). I am working with multiple engines for a while on 5.0. Only paths not tested here were multiple engines on distributed machines and esoteric settings. Default settings and several engines on the same machine works rather well. There is still some work to be done as to how its all being logged and monitored. Setting this to modified as the original thought behind multiple engines is supported. Next versions will need a 'child' RFE for things not yet done here. 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. http://rhn.redhat.com/errata/RHEA-2014-0849.html |