Standardized Error Codes for Nova
Top level exceptions should include a standardized set of error codes in addition to the normal exception data (stack trace, exception type, etc.) This is to ease customer support by permitting the customer to state "I'm getting a X1234 error when I try to start my server".
We need to grab all the Exxx codes from Slicehost as a starting place.
We need to catch all top-level exceptions and write them to a rabbit queue with these new codes (and the logger).
Blueprint information
- Status:
- Complete
- Approver:
- Rick Clark
- Priority:
- Low
- Drafter:
- Sandy Walsh
- Direction:
- Approved
- Assignee:
- Titan
- Definition:
- Approved
- Series goal:
- Accepted for diablo
- Implementation:
- Implemented
- Milestone target:
- 2011.3
- Started by
- Vish Ishaya
- Completed by
- Thierry Carrez
Related branches
- lp://staging/~cerberus/nova/nova_notifications
- lp://staging/~rackspace-titan/nova/publish_errors
- lp://staging/~rackspace-titan/nova/exceptions-refactor-invalid
- lp://staging/~rackspace-titan/nova/exceptions-refactor-duplicate
- lp://staging/~rackspace-titan/nova/exceptions-refactor-notfound
- lp://staging/~rackspace-titan/nova/exception-cleanup
- lp://staging/~rackspace-titan/nova/publish_errors2
Related bugs
Sprints
Whiteboard
First appeared in diablo-2
Reassigning this to titan team since they have been doing a lot of this.
Tasks:
1) Collect all current error codes from existing RS cloud API.
2) Define uniform approach to error codes across Nova project.
3) Add error codes to correct places throughtout Nova code base.
Work Items
Dependency tree
* Blueprints in grey have been implemented.