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 |
||
|---|---|---|
| .. | ||
| finalise.d | ||
| README.rst | ||
This element clears out /etc/resolv.conf and prevents dhclient from populating it with data from DHCP. This means that DNS resolution will not work from the amphora. This is OK because all outbound connections from the amphora will be based using raw IP addresses.
In addition we remove dns from the nsswitch.conf hosts setting.
This has the real benefit of speeding up host boot and configutation times. This is especially helpful when running tempest tests in a devstack environment where DNS resolution from the amphora usually doesn't work anyway: This means that the amphora never waits for DNS timeouts to occur.