Bug 1281569 - [RFE][nova]: Versioned notification api
Summary: [RFE][nova]: Versioned notification api
Keywords:
Status: CLOSED DUPLICATE of bug 1281570
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M3
: 9.0 (Mitaka)
Assignee: Eoghan Glynn
QA Contact: nlevinki
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_mitaka-3 upstream_...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-12 20:02 UTC by Stephen Gordon
Modified: 2019-09-09 13:07 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-14 19:20:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Stephen Gordon 2015-11-12 20:02:33 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/versioned-notification-api.

Description:

Versioned notification API

Notification interface of nova is not well defined and the current
notifications define a very inconsistent interface. There is no easy
way to see from the notification consumer point of view what is the format
and the content of the notification nova sends.

Nova developers can add new notifications to the system without specifying
the format and the content of the notification.

Moreover developers can change existing notifications without considering
backward compatibility towards the notification consumers.

Due to this situation maintaining a consumer for nova notifications is really
hard.

Specification URL (additional information):

http://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/versioned-notification-api.html

Comment 2 Jon Schlueter 2016-02-04 14:18:59 UTC
This was a Mitaka RFE moving to OSP 9

Comment 3 Mike McCune 2016-03-28 22:33:16 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 4 Stephen Gordon 2016-06-14 19:20:26 UTC

*** This bug has been marked as a duplicate of bug 1281570 ***


Note You need to log in before you can comment on or make changes to this bug.