| EugenMayer | hello- does those docs apply to kolla https://docs.openstack.org/project-deploy-guide/openstack-ansible/ocata/overview-network-arch.html - or in other words, is openstack-ansible "kolla" or not? | 13:05 |
|---|---|---|
| EugenMayer | I assume openstack-ansible might be similar, but in the end kolla runs in containers, openstack-ansible us a direct installation. But both provision via ansible (that is the similarity, but different projects?) | 13:06 |
| EugenMayer | Maybe the docs for networking overview i look for are rahter https://docs.openstack.org/neutron/latest/admin/intro-os-networking.html | 13:29 |
| EugenMayer | when intially deploying kolla on my prodcution environment, i'am no longer sure hot to understand "network_interface". With my lab, all nodes had the same interface names, this is no longer true for my production setup. While i have a managment network and "provider lan network", the inteface name per node vary from "ens9s0, en8s0, ens18" - how is that setting in globals.yaml is to be understood - should i insert the | 14:23 |
| EugenMayer | inteface name on the deployer and it will then be auto-detected per controller/compute node, which inteface offers the same network? | 14:23 |
| EugenMayer | i guess to redefine the interface names for each compute / controll node i use "Host and group variables" as described in https://docs.openstack.org/kolla-ansible/latest/user/multinode.html. I use this for network_interface, and also the neutron_external_interface: "eth2,eth3" map and all this, right? | 15:54 |
| jingvar | usually controllers have the same hardware configuration | 16:39 |
| jingvar | I use 2 compute node types with interface naming like enp197s0f1 and eth5 | 16:43 |
| jingvar | ayobe-config/etc/kayobe/inventory/group_vars/compute_ucs_gold/network-interfaces:external_interface: enp3s0 | 16:46 |
| jingvar | kayobe-config/etc/kayobe/inventory/group_vars/controllers/network-interfaces:external_interface: bond0 | 16:46 |
| jingvar | kayobe-config/etc/kayobe/inventory/group_vars/compute_ucs/network-interfaces:external_interface: eth2 | 16:46 |
| EugenMayer | yeah i finally understood this from the docs | 17:06 |
| EugenMayer | controllers and computes are equal, but not always equal with the predictable network names | 17:07 |
| EugenMayer | how do you store group vars within the installed kolla-ansible installation? | 17:10 |
| EugenMayer | i sse you are using group_vars/controllers/ format | 17:10 |
| EugenMayer | is there any way to see what the applied configuration for each host ist? | 17:10 |
| EugenMayer | i installed kolla under /opt/kolla and not sure where the inventory actually is | 17:15 |
| EugenMayer | i found /opt/kolla/share/kolla-ansible/ansible/inventory but that is just the template i guess | 17:16 |
| kevko | kolla-ansible -i /whatever/path/you/have/inventory/located | 17:16 |
| EugenMayer | then i have my own "/opt/kolla/multinode" but where to create my custom inventory for varas? | 17:16 |
| kevko | EugenMayer: ./ansible/inventory/multinode < | 17:17 |
| EugenMayer | ok so the entire "inventory" in my case is /opt/kolla/multinode | 17:18 |
| EugenMayer | so to add the folder like inventory i just add more -i /custom/path/inventory to the calls? | 17:18 |
| kevko | well kolla-ansible is standard ansible | 17:18 |
| kevko | so if you are not defining inventory, ansible by default is looking it in /home/ ...etc.. | 17:19 |
| EugenMayer | well i'am rather the chef-guy, using ansible for laptop/desktop deployments only, so not as bullet proof, esp. for those big deployments with kolla | 17:19 |
| EugenMayer | ok i read the ansible docs then | 17:19 |
| kevko | https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html | 17:19 |
| kevko | ciao | 17:19 |
| EugenMayer | have a nice evening | 17:20 |
| EugenMayer | kevko, thanks for the other day with the finding about the ip/interface, it really helped me finding the cause and getting the stack up. I was not able to thank you prior, i was MIA that evening and you were not online a couple of days | 17:20 |
| jingvar | kayobe-config/etc/kolla/inventory/overcloud/host_vars/gold-ucs.dev.dataline.cloud:neutron_external_interface: "enp3s0" | 18:16 |
| jingvar | kayobe-config/etc/kolla/inventory/overcloud/host_vars/cmp01-ucs.dev.dataline.cloud:neutron_external_interface: "eth2" | 18:16 |
| jingvar | kayobe render it's config and place rendered files for kolla-ansible | 18:17 |
| EugenMayer | jingvar, it seems, somehow that e.g. [control:vars] are not picked up when defined in `multinode` is interestingly not picked up. When using folder based group_vars it is working, but only if i pick the entire folder as the inventory, so `kollab-ansible -i /mnt/config` (here i have multinode and group_vars/ located). If i use -i /mnt/config -i /opt/kollab/multinode i will not picked up either | 18:32 |
| EugenMayer | thats how that config folder looks like https://github.com/EugenMayer/openstack-lab/tree/master/config | 18:37 |
| EugenMayer | i see that my bridges configureed in https://github.com/EugenMayer/openstack-lab/blob/master/config/group_vars/compute/compute.yml#L5 are not part of the controller / compute nodes. How do i check that br-kwlan is actually bridged to eth1 e.g.? | 18:58 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!