> We don't have to add a new notification, but we have to add some > new datas in the nova notifications. At least for the delete > instance notification to remove the ceilometer nova notifier. > > A while ago, I have registered a blueprint that explains which > datas are missing in the current nova notifications: > > https://blueprints.launchpad.net/nova/+spec/usage-data-in-notification > > https://wiki.openstack.org/wiki/Ceilometer/blueprints/remove-ceilometer-nova-notifier
This seems like a much better way to do this. I'm not opposed to a nova plugin, but if it's something that lives outside the nova tree, I think there's going to be a problem of constantly chasing internal API changes. IMHO, a plugin should live (and be tested) in the nova tree and provide/consume a stableish API to/from Ceilometer. So, it seems like we've got the following options: 1. Provide the required additional data in our notifications to avoid the need for a plugin to hook into nova internals. 2. Continue to use a plugin in nova to scrape the additional data needed during certain events, but hopefully in a way that ties the plugin to the internal APIs in a maintainable way. Is that right? Personally, I think #1 is far superior to #2. --Dan _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
