Chris Dent wrote:
On Tue, 11 Oct 2016, Joshua Harlow wrote:
Damn, that's crazy that the projects emitting events don't want to own
the formats and versions (and schemas) that they emit. That is ummm,
like ummm, what the, ha, words can't describe... And the fact that
nothing much has changed since kilo, ya, also a what the...
Nova started with versioning and schematizing notifications with
this blueprint:
https://blueprints.launchpad.net/nova/+spec/versioned-notification-api
That's sort of in the realm of what's being discussed here, but
centralized in nova for now.
I agree that siloing the stuff in the code is bad in the long term,
but I guess it is good that it has started somewhere.
Thanks for sharing, didn't recall that work being done.
From glancing at it, it seems to be nova versioning its notifications
(which is good) but I'm unclear what the objectification of those
notifications means to the outside world (the actual consumers of
notifications). Said outside world uses more than just python so it
feels like some other intermediary format should be exposed to consumers
as the schema that various python and non-python languages can consume
(either via auto-generation of code or other).
Perhaps just jsonschema is enough (though it doesn't feel like it)? Has
anyone tried 'to_json_schema' on those objects and outputting that
schema into a nova/schema/notifications folder (or equivalent)?
-Josh
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
