Docs: clarify network config (globals.yml confusing text)

[zhangss]

Can I configure vxlan/tunnel network and API network respectively?
I can't see the options according to globales.yml
##############################
# Neutron - Networking Options
##############################
# This interface is what all your api services will be bound to by default.
# Additionally, all vxlan/tunnel and storage network traffic will go over this
# interface by default. This interface must contain an IPv4 address.
# It is possible for hosts to have non-matching names of interfaces - these can
# be set in an inventory file per host or per group or stored separately, see
# http://docs.ansible.com/ansible/intro_inventory.html
# Yet another way to workaround the naming problem is to create a bond for the
# interface on all hosts and give the bond name here. Similar strategy can be
# followed for other types of interfaces.
network_interface: "eth0"

[Radosław Piliszek (yoctozepto)]

This help text is wrong. You can use the respective variables below this one to override the interface per function (and use them in your inventory to override per host/hostgroup).

[zhangss (intentc)]

Where can I find documents or help that describe these variables in detail? Could You give me a link or screenshot, thk

[Radosław Piliszek (yoctozepto)]

https://docs.openstack.org/kolla-ansible/train/admin/production-architecture-guide.html

[Andrei Nistor (codertux)]

I've hit this same issue when adding a few new compute servers to my deployment. The old servers use team interfaces and the new ones use bonds.

I've tried setting network_interface and neutron_external_interface using hostvars, but they were overridden by the values in globals.yaml.

I've then tried removing the variables from globals and set the old values using group vars on the `all` group, and tried to override them for the new servers using hostvars. Still no luck, they were overridden by the playbook group vars defined in https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml (values were eth0 and eth1 respectively, although I specified team0/bond0 and vlan2119/bond2119 in inventory)

Ansible docs confirm the behavior i saw: https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable

I think this actually is a bug, not just a documentation error.