[openstack-dev] [all] Treating notifications as a contract
Sandy Walsh
sandy.walsh at RACKSPACE.COM
Fri Jul 11 13:05:33 UTC 2014
On 7/11/2014 6:04 AM, Chris Dent wrote:
> On Fri, 11 Jul 2014, Eoghan Glynn wrote:
>
>> But I guess you're suggesting not only that we version/schematize
>> individual notification payloads, but that we do so in a way that's
>> global across event types and emitters?
> That's partially correct. I'm suggesting the we consider standardizing a
> general format for notification payloads across emitters. _Not_
> individual notification payloads.
>
> Schematizing individual payloads strikes me as heavyweight[1] when it
> _might_[2] be easier to declare that "a list of dicts with certain
> required fields" is sufficient to represent a multiplicity of value-
> oriented events which are consumed as any of metric, event,
> visualization data-point, etc.
This is the model of notifications [1] (see elsewhere in this thread)
The payload is the wild-west and loosely spec'ed on the wiki. Above the
payload we have strict fields.
[1] https://wiki.openstack.org/wiki/NotificationSystem
More information about the OpenStack-dev
mailing list