Bug 1281569

Summary:	[RFE][nova]: Versioned notification api
Product:	Red Hat OpenStack	Reporter:	Stephen Gordon <sgordon>
Component:	openstack-nova	Assignee:	Eoghan Glynn <eglynn>
Status:	CLOSED DUPLICATE	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0 (Kilo)	CC:	berrange, dasmith, eglynn, jschluet, kchamart, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone:	Upstream M3	Keywords:	FutureFeature
Target Release:	9.0 (Mitaka)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/versioned-notification-api
Whiteboard:	upstream_milestone_mitaka-3 upstream_definition_approved upstream_status_implemented
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-14 19:20:26 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:

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 ***