On Thu, Jul 10 2014, Eoghan Glynn wrote: Hi Eoghan,
> So the purpose of this thread is simply to get a read on the appetite > in the community for such an effort. At the least it would require: > > * trashing out the details in say a cross-project-track session at > the K* summit > > * buy-in from the producer-side projects (nova, glance, cinder etc.) > in terms of stepping up to make the changes > > * acquiescence from non-integrated projects that currently consume > these notifications > > (we shouldn't, as good citizens, simply pull the rug out from under > projects such as StackTach without discussion upfront) > > * dunno if the TC would need to give their imprimatur to such an > approach, or whether we could simply self-organize and get it done > without the need for governance resolutions etc. > > Any opinions on how desirable or necessary this is, and how the > detailed mechanics might work, would be welcome. Glad to see this coming up again. I've been pushing that since the Icehouse summit in Hong-Kong, where we had a Oslo session about that subject and where everybody nod about my initial plan. :) I've created a blueprint and started a very primitive implementation back then: https://blueprints.launchpad.net/oslo.messaging/+spec/notification-structured but had to stop by lacking time to push that effort further. My initial plan was to leverage a library like voluptuous to do schema based validation on the sender side. That would allow for receiver to introspect schema and know the data structure to expect. I didn't think deeply on how to handle versioning, but that should be doable too. To summarize, I got the feeling that there's more a need of resources to work on that than any problem. Same old, same old. Cheers, -- Julien Danjou /* Free Software hacker http://julien.danjou.info */
signature.asc
Description: PGP signature
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
