| 2016-07-27 20:17:37 |
Matt Greene |
description |
[Use-cases]
- Hierarchical health monitoring
The operator wants to monitor server 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, so is restricted to monitoring the single port set for the pool. Certain operators wish to monitor the health of the server instance separately, but in addition to the health of the service/application. This model also does not support deployment of a service via docker container, in which each container will use an ephemeral port.
[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> in the pool object. |
[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/application. This model limits the granularity at which the operator can gauge the health of their cloud.
[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>. |
|
