c00488143d
Not all Linux flavors accept the same type of configuration to manage NICs. The amphora-agent must be able to distinguish between different Linux flavors and choose the appropriate type of jinja2 NIC configuration template for each one, respectively. Up until now, The amphora-agent had no notion of the operating system it is running on, therefore it used NIC configuration templates that only match Debian based Linux flavors (mostly Ubuntu). Making it unusable for flavors such as RHEL, Fedora and CentOS. This fix enhances how the amphora-agent is handling NIC hot plugs. It will use the appropriate jinja2 template by checking the Amphora distribution name when needed. Co-Authored-By: Michael Johnson <johnsomor@gmail.com> Closes-Bug #1548070 Change-Id: Id99948aec64656a0532afc68e146f0610bff1378
19 lines
866 B
YAML
19 lines
866 B
YAML
---
|
|
prelude: >
|
|
Amphora image support for RH Linux flavors.
|
|
features:
|
|
- The diskimage-create script supports different operating system flavors
|
|
such as Ubuntu (the default option), CentOS, Fedora and RHEL. Adaptations
|
|
were made to several elements to ensure all images are operational.
|
|
- The amphora-agent is now able to distinguish between operating systems and
|
|
choose the right course of action to manage files and networking on each
|
|
Linux flavor.
|
|
issues:
|
|
- To use CentOS, Fedora, or RHEL in your amphora image you must set
|
|
the user_group option, located in the [haproxy_amphora] section of the
|
|
octavia.conf file to "haproxy". This will be made automatic in a
|
|
future version.
|
|
upgrade:
|
|
- agent_server_network_dir is now auto-detected for Ubuntu, CentOS, Fedora
|
|
and RHEL if one is not specified in the configuration file.
|