Nova currently ships error messages and notifications outside the system via a message queue. This has the downside that those errors are not available for diagnostics, and storing those errors breaks the simple model of Nova's architecture. The 1.1 API specification uses asynchronous notifications to access this data, but it is at best a mediocre solution. This session would be to brainstorm on various proposals for the 2.0 API and understand the best way to ensure that Nova users can track errors.
Wednesday October 5, 2011 3:00pm - 3:55pm