Bug 1059963
Summary: | [RFE][keystone]: Convert to oslo.messaging | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> | |
Component: | openstack-keystone | Assignee: | RHOS Maint <rhos-maint> | |
Status: | CLOSED ERRATA | QA Contact: | Udi Kalifon <ukalifon> | |
Severity: | low | Docs Contact: | ||
Priority: | high | |||
Version: | unspecified | CC: | aberezin, ayoung, breeler, markmc, nkinder, tross, ukalifon, yeylon | |
Target Milestone: | Upstream M3 | Keywords: | FutureFeature | |
Target Release: | 5.0 (RHEL 7) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
URL: | https://blueprints.launchpad.net/keystone/+spec/oslo-messaging | |||
Whiteboard: | upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_pending-approval | |||
Fixed In Version: | Doc Type: | Enhancement | ||
Doc Text: |
An enhancement has been made to use Oslo Messaging for notifications.
Previously, Identity used the incubated code, but messaging has graduated to a stand-alone library. Using the new library keeps Identity consistent with the rest of the OpenStack services in the way it handles notifications.
This ensures that Identity gets all bug fixes and feature enhancements.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1082397 (view as bug list) | Environment: | ||
Last Closed: | 2014-07-08 15:25:42 UTC | Type: | --- | |
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: | 1082397, 1115995, 1115996, 1115999, 1116002, 1116003 |
Description
RHOS Integration
2014-01-31 05:04:13 UTC
Updating based on BP milestone An enabler to move to Porton messaging and enable A/A messaging. Performed basic sanity. No test cases for this feature. openstack-keystone-2014.1-2.el7.noarch 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-0854.html *** Bug 1116005 has been marked as a duplicate of this bug. *** |