Browse code
XenAPI: Don't assume specific network interfaces
The default for GUEST_INTERFACE_DEFAULT now uses the ip command
to find an interface; so it will work on multiple distributions.
XenAPI should not be setting a specific interface here, as it will
almost always be wrong. In most cases, the calculated value for
GUEST_INTERFACE_DEFAULT will be a better default.
PUBLIC_INTERFACE_DEFAULT makes even less sense as it's often an
internal bridge for devstack scenarios.
In both cases, the right way to override these is to set
GUEST_INTERFACE / PUBLIC_INTERFACE in the localrc rather than
changing the _DEFAULT values.
Change-Id: I0cf84438d778bf1a2481328165513c59167490e2
Bob Ball authored on 2016/08/01 20:52:44Showing 1 changed files
| ... | ... |
@@ -24,8 +24,6 @@ set +o xtrace |
| 24 | 24 |
# Defaults |
| 25 | 25 |
# -------- |
| 26 | 26 |
|
| 27 |
-PUBLIC_INTERFACE_DEFAULT=eth2 |
|
| 28 |
-GUEST_INTERFACE_DEFAULT=eth1 |
|
| 29 | 27 |
# Allow ``build_domU.sh`` to specify the flat network bridge via kernel args |
| 30 | 28 |
FLAT_NETWORK_BRIDGE_DEFAULT=$(sed -e 's/.* flat_network_bridge=\([[:alnum:]]*\).*$/\1/g' /proc/cmdline) |
| 31 | 29 |
if is_service_enabled neutron; then |