Hi Eddie,

If I define them in the hostname it works perfectly fine. I cannot use the globals.yml because there are different bridges per group (ex. control plane servers do not the provide network bridges).

The problem with the host approach is that it makes the inventory file very difficult to parse with external scripts. If the typical ansible :vars section worked as expected it would make any parsing much easier with crudini :)

a.

Hi Alexandros,

In the [compute] area, it's correct.

But for define what physical interface should be use for each 

nodes, you should set like below:

[compute]

comp[1:5] neutron_external_interface=bond0.100,bond.101

And I'm not sure if "neutron_bridge_name" can be set behind 

hostname. For me I usually put into globals.yml.

Alexandros Soumplis <soumplis@admin.grnet.gr> 於 2021年3月27日 週六 上午1:49寫道：

Hi all,

I am trying to define a couple of variables in the inventory file for a
specific group and I do something like the following in the inventory:

(...)
[compute]
comp[1:5]

[compute:vars]
neutron_external_interface=bond0.100, bond0.101
neutron_bridge_name=br-ex,br-ex2

(...)

This is a valid ansible setup, however with kolla-ansible these
variables are totally ignored. Any suggestion ?


a.