Open Stack

On Sat, 27 Mar 2021 at 06:50, Alexandros Soumplis
<soumplis at admin.grnet.gr> wrote:
>
> 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 :)

Hi Alexandros,

There's some kolla-specific info here:
https://docs.openstack.org/kolla-ansible/latest/user/multinode.html#host-and-group-variables

Essentially, the problem is that we define various default values in a
group_vars/all.yml file next to our playbooks, and this has a higher
precedence than an inventory file:
https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#understanding-variable-precedence.

Try using a group_vars/compute file, next to your inventory file.

Mark

>
>
> a.
>
>
>
> On 27/3/21 1:11 π.μ., Eddie Yen wrote:
>
> 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 at 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.
>>
>>
>>