+1, the high-level code should deal with top-level exceptions and generate .error notifications (though it's a little spotty). Ideally we shouldn't need three events for simple operations.
The use of .start/.end vs. logging is a bit of a blurry line. At its heart a notification should provide context around an operation: What happened? Who did it? Who did they do it to? Where did it happen? Where is it going to? etc. Stuff that could be used for auditing/billing. That's their main purpose. But for mission critical operations (create instance, etc) notifications give us a hot-line to god. "Something is wrong!" vs. having to pour through log files looking for problems. Real-time. Low latency. I think it's a case-by-case judgement call which should be used. ________________________________________ From: Day, Phil [philip....@hp.com] I'm just a tad worried that this sounds like its starting to use notification as a replacement for logging. If we did this for every CRUD operation on an object don't we risk flooding the notification system. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
