octavia/elements/amphora-agent
Gregory Thiemonge b9f622b335 Disable auto configuration of new interfaces in NetworkManager
NetworkManager in Centos images configures new network devices as soon
as they appear in the default namespace, it means that we might have
conflicts between the management interface's routes and address and the
new VIP or member interfaces' routes and addresses during a small period
of time before they are moved to the amphora-haproxy namespace.

Now, the "no-auto-default=*" option is enabled in NetworkManager, it
disables the configuration of new interfaces, while the management
interface is still enabled/configured through cloud-init.

Story 2008599
Task 41773

Change-Id: I6dd8e99b07ff557674871cb503dece96a9df3ada
(cherry picked from commit a518cefda1)
2021-02-22 09:18:11 +01:00
..
install.d/amphora-agent-source-install Fix building Ubuntu 20.04 focal amphorae 2020-09-23 14:14:25 -07:00
post-install.d Fix building Ubuntu 20.04 focal amphorae 2020-09-23 14:14:25 -07:00
static Disable auto configuration of new interfaces in NetworkManager 2021-02-22 09:18:11 +01:00
README.rst Rework amphora agent installation element 2018-01-22 18:04:41 -08:00
element-deps Change amphora logging to dedicated socket 2019-08-07 09:02:22 -07:00
package-installs.yaml Fix building Ubuntu 20.04 focal amphorae 2020-09-23 14:14:25 -07:00
pkg-map Fix missing cronie package in RHEL-based image builds 2021-01-11 06:20:27 +00:00
source-repository-amphora-agent Update TOX_CONSTRAINTS_FILE for stable/victoria 2020-09-25 08:38:13 +00:00
svc-map Rework amphora agent installation element 2018-01-22 18:04:41 -08:00

README.rst

Element to install an Octavia Amphora agent.

By default, it installs the agent from source. To enable installation from distribution repositories, define the following: export DIB_INSTALLTYPE_amphora_agent=package

Note: this requires a system base image modified to include OpenStack repositories