RFE: Introduce Error handling for ConnectionError
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-dpm |
New
|
High
|
Andreas Scheuring | ||
nova-dpm |
In Progress
|
High
|
Prabhat Ranjan | ||
os-dpm |
Invalid
|
Undecided
|
Unassigned |
Bug Description
A ConnectionError can occur every time when interacting with the HMC. A concept on how to deal with such errors is needed.
The following is thinkable
- Retry mechanism - retries a certain command up to x times. x is configurable via config option
- Timeout mechanism - during this time (configureable), the error will be caught
* The agent will be reported as down, but continues running until HMC is back or the timeout hit. Then it terminates
* resources will be reported as up until the timeout hits. After that the agent gets terminated
* resources will be reported as down until the timeout hits. After that the agent terminates
We need to carefully think which options make sense! Maybe all, maybe just one of them, maybe something totally different.
Changed in os-dpm: | |
status: | New → Invalid |
tags: | added: ocata-rc-potential |
tags: | added: rfe |
Changed in networking-dpm: | |
importance: | High → Wishlist |
Changed in nova-dpm: | |
assignee: | nobody → Prabhat Ranjan (pranjank) |
Changed in networking-dpm: | |
importance: | Wishlist → High |
Changed in networking-dpm: | |
assignee: | nobody → Andreas Scheuring (andreas-scheuring) |
milestone: | none → pike-1 |
Changed in nova-dpm: | |
milestone: | none → pike-1 |
Doesn't block the release, but we might want to backport it when it's done in Pike.