[RFE] Per-server port for LBaaS Health Monitoring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
[Use-cases]
- Hierarchical health monitoring
The operator wants to monitor member health for the pool separately from application health.
- Micro-service deployment
An application is deployed as docker containers, which consume an ephemeral port.
[Limitations]
LBaaSv2 health monitor is attached to the pool, but will use the protocol-port set in the member object. Certain operators wish to monitor the health of the member (a.k.a member) separately, but in addition to the health of the service/
[Enhancement]
Add an optional application port field in the member object. Default is <None>. Enhance health monitor creation with an optional parameter to use the service or application port. Default is <service port>.
summary: |
- [RFE] Per-server port for Health Monitoring + [RFE] Per-server port for LBaaS Health Monitoring |
description: | updated |
Changed in neutron: | |
importance: | Undecided → Wishlist |
We're in the process of winding down lbaas efforts into Neutron [1]. I think we're at a cut off point where new LBaaS requests should target Octavia. Let's raise this for discussion so that the drivers team can reach an agreement on the strategy on how to deal with these types of RFEs going forward.
[1] http:// specs.openstack .org/openstack/ neutron- specs/specs/ newton/ kill-neutron- lbaas.html