openstack team mailing list archive

[Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx>]

While I think the idea has merit, it's going to be a tough thing to version. (I'm neck deep in the notifications right now making a major revision to StackTach)

We'd have to version the context, the instance state dictionary, the cpu info and the related payloads for each type of message since each component comes from different, already-existing, systems.  (as opposed to the notification being responsible for the entire payload itself)

Lots of ramifications.

-S



From: openstack-bounces+sandy.walsh=rackspace.com@xxxxxxxxxxxxxxxxxxx [openstack-bounces+sandy.walsh=rackspace.com@xxxxxxxxxxxxxxxxxxx] on behalf of Day, Phil [philip.day@xxxxxx]

Sent: Tuesday, October 09, 2012 2:07 PM
To: openstack@xxxxxxxxxxxxxxxxxxx (openstack@xxxxxxxxxxxxxxxxxxx) (openstack@xxxxxxxxxxxxxxxxxxx)
Subject: [Openstack] Versioning for notification messages

Hi Folks,
 
What do people think about adding a version number to the notification systems, so that consumers of notification messages are protected to some extent from changes in the message contents ?
 
For example, would it be enough to add a version number to the messages – or should we have the version number as part of the topic itself (so that the notification system can provide both a 1.0 and 1.1 feed), etc ?
 
Phil