lbaas health monitors checkport and patterns
Modify the lbaas health monitor model: offer the possibility to have a chk port different from the member listen port
Use case:
A pool member is defined as listening on port 80. The backend server also has a
service listening on port 8080 and returning its general health condition formatted with status codes or patterns
With the current db model/api, there is no way to define a health monitor with a check port different from the member port
And there is no way, when you create a simple tcp monitor, to provide an expected response pattern.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- raphael.glon
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Armando Migliaccio
Related branches
Related bugs
Sprints
Whiteboard
Nov-13-2015(armax): If someone is interested in pursuing it, this must be re-submitted according to guidelines defined in [1].
[1] http://
-----------------