config: Refactor exception handling and reporting
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R1.1 |
Won't Fix
|
Medium
|
Hampapur Ajay | |||
R2.20 |
Won't Fix
|
Medium
|
Hampapur Ajay | |||
Trunk |
Fix Committed
|
Medium
|
Hampapur Ajay |
Bug Description
There is scope for improvements in exception handling in api-server and vnc-openstack extension in following areas:
1. Raise exceptions but defer handling(abort etc.) from bottom of call stacks to upper-layers giving them a chance to handle gracefully if possible. (e.g. vnc_cfg_
2. There are patterns of
ok, result = <some-callable>()
if not ok:
<error handling>
This should be enhanced to also catch exceptions that can be handled gracefully vs not with appropriate error message in latter case.
3. Currently api-server returns human-readable strings on exceptions. Enhance to also append a json part that can be used in machine invocation contexts to generate exceptions on the remote end.
4. It would be good to send exception information (gracefully handled or otherwise) to collector.
5. Chained exception reporting (not losing information if there is an exception in any complex handling itself) would be good too.
Changed in juniperopenstack: | |
assignee: | nobody → Hampapur Ajay (hajay) |
description: | updated |
Changed in juniperopenstack: | |
importance: | Undecided → Medium |
tags: | added: config |
information type: | Proprietary → Public |
Review in progress for https:/ /review. opencontrail. org/11812
Submitter: Hampapur Ajay (<email address hidden>)