Support replay retry in Liberty so it works with multiprocesses
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-cisco |
Invalid
|
Medium
|
Carol Bouchard |
Bug Description
For the short-term, the retry capability was backed out or liberty and kilo since it will require data base changes to support multiprocesses(ref: 1469839). Due to planned movement on vendor data bases this capability will only be implemented in new releases.
This capability allows the user to configure in the cisco vendor ml2 ini file the number of replay attempts which can be performed. These attempts include any point of replay failure of which there are two points. The first failure point is attempt to contact the Nexus Switch. The second failure is when the switch was contacted but the ML2 Nexus Driver encountered errors trying to
configure the switch during replay. When the sum of these errors is reaches the max configured attempt, the ML2 Driver will stop attempting to contact the switch.
However, Once a new transaction is encountered, the stats kept for these two points of failure will be reset and Replay attempts will start over.
Changed in neutron: | |
assignee: | nobody → Carol Bouchard (caboucha) |
Changed in networking-cisco: | |
assignee: | nobody → Carol Bouchard (caboucha) |
no longer affects: | neutron |
Changed in networking-cisco: | |
importance: | Undecided → Medium |
status: | New → Triaged |
There is no desire to configure retry attempts for replay. The number of retries variable
has since been removed so there was a conscience decision by all to not perform
this any longer.