8bbd8f1b62
TCP and UDP Connect health monitors are now supported by the provider driver, when the underlying OVN version supports them. The health monitor uses the OVN distributed DHCP port as the source IP for messages, one must exist or the create or update operation will fail. The list of member ports to monitor is updated whenever one is created or deleted. Added support for SBDB notifications for Service Monitor events generated when the OVN health monitor code detects issues with connectivity. This will trigger updates to the Octavia objects as members go on/offline so that the Octavia API reflects the current running state of the load balancer. Added a lot of new unit and functional tests to cover all the new code, and enabled the tempest health monitor feature so those tests are run as well. Change-Id: I776a7a6b036ad72ce7eaa1ab39f448b344974be6
11 lines
487 B
YAML
11 lines
487 B
YAML
---
|
|
features:
|
|
- |
|
|
The OVN Octavia provider drvier now supports health monitoring.
|
|
TCP and UDP Connect health monitors are now supported by the
|
|
provider driver, when the underlying OVN version supports
|
|
them. The health monitor uses the OVN distributed DHCP port as the
|
|
source IP for messages by default, if one doesn't exist then
|
|
a port will be created on each given subnet. The list of member
|
|
ports to monitor is updated whenever one is created or deleted.
|