b9f622b335
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
|
||
---|---|---|
.. | ||
install.d/amphora-agent-source-install | ||
post-install.d | ||
static | ||
README.rst | ||
element-deps | ||
package-installs.yaml | ||
pkg-map | ||
source-repository-amphora-agent | ||
svc-map |
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