| em_ | I'am not sure this is a neutron questions, or yet a kolla. I have 3 ethernet devices, 1 for management [eth1], 1 for provider network 'self service'[eth2] and one for provider network (wan/floating ips) [eth3] - thus during the deployment i use https://github.com/EugenMayer/openstack-lab/blob/master/config/group_vars/compute/compute.yml#L4 to assign eth2 to br-lan and eth3 to br-wan, which then creates physnet1 and physnet2. When i | 05:45 |
|---|---|---|
| em_ | then create a network in openstack (flat) mappigng on physnet1, the network of the VM never comes up. Is there anything inproper configured? | 05:45 |
| em_ | currently trying to use ovs-vsctl show to understand if the acual bridges have been created correctly (on controller/compute), but i'am not an OVS guy yet, rather used to linux bridge. hard to understand what i'am looking a there | 05:55 |
| jingvar | I 'm not having an env with ovs | 06:00 |
| em_ | looking at that output, it seems like it is configured correctly https://gist.github.com/EugenMayer/2a8329361fb2638203fc36561b665459 | 06:00 |
| em_ | jingvar, are you using OVN already? | 06:00 |
| jingvar | yep | 06:01 |
| *** amoralej|off is now known as amoralej | 06:06 | |
| eugenmayer | does it actually make any sense to use OVS with a new stack at all? OVN is the successor of OVS AFAIU, right? | 06:07 |
| jingvar | it depends on usecase - for example ovs+dvr=+1additional float IP per compute node | 06:18 |
| jingvar | if cloud is private - in makes no sense | 06:19 |
| jingvar | OVN does'nt have VPNaaS (only dev in Xena) | 06:19 |
| eugenmayer | i do not need vpnaas | 06:20 |
| jingvar | RabbitMQ sometimes painfull, OVN don't use Rabbit | 06:21 |
| eugenmayer | additional float IP .. i get that, would be an issue for me too. I would rather avoid that. So you use a network node for all floating ips (1) and then route all the traffic to the actual instances, right | 06:21 |
| jingvar | OVN uses direct links(datapaths) between instances and network node for external | 06:23 |
| jingvar | as OVN+DVR without additional FIP per compute node | 06:23 |
| eugenmayer | but OVN still uses OVS under the hood, right? | 06:25 |
| jingvar | yes but defferean approach | 06:26 |
| jingvar | like Docker - Kubernetes | 06:27 |
| eugenmayer | what guide/docs did you follow during the setup? there are the main docs https://docs.openstack.org/neutron/latest/admin/ovn/index.html , then a setup guide https://docs.ovn.org/en/stable/tutorials/ovn-openstack.html and somewhat short section in kolla https://docs.ovn.org/en/stable/tutorials/ovn-openstack.html on how to enable ovn | 06:30 |
| eugenmayer | anything in particular you would guide to use here? | 06:30 |
| eugenmayer | interesting, when setting up (for xena) with kolla, when using debian as a target for the docker images, i get https://gist.github.com/EugenMayer/d9b717e66b8424bf8953ea9ca7d744bc | 06:32 |
| eugenmayer | trying to switch to ubuntu then | 06:32 |
| jingvar | I use Centos/Rocky | 06:32 |
| jingvar | RedHat has an tutorial of OVN | 06:33 |
| eugenmayer | i see. Are you avoiding enable_neutron_provider_networks: yes with OVN setups? The point is (as in my lab) i already have setup a vswitch provider based network in my DC to create a shared 'self service' network between my computes. Does this contradicts how ovn wants to operate? | 06:34 |
| eugenmayer | i will have 3 vswitches in the DC: management network (that seems just fine), self-service (vm lan) and WAN (floating ips). all 3 are based on the main nic of the bare bone, vlan based | 06:35 |
| jingvar | You can't use flat network on common interface | 06:43 |
| eugenmayer | jingvar, not sure what you mean. You mean instead of pre-creating my interface for compute/controll | 06:44 |
| jingvar | kayobe-config/etc/kayobe/kolla.yml:kolla_enable_neutron_provider_networks: yes | 06:45 |
| eugenmayer | i rather do this inside ovn? | 06:45 |
| jingvar | Time to draw a schema | 06:46 |
| eugenmayer | should i draw one - i surely can. I try right now to simulate the DC setup i have (even though dc is with vswitches / vlans) in the home lab using vbox interfaces | 06:47 |
| jingvar | I think we have an miscommunication,I think we have an miscommunication, probably my English is not good enough :) | 06:55 |
| mnasiadka | morning | 06:57 |
| eugenmayer | no worries | 06:57 |
| jingvar | morning | 06:59 |
| mnasiadka | jingvar: you're using Rocky with Kayobe? | 07:06 |
| jingvar | yep | 07:10 |
| mnasiadka | with centos stream Kolla containers? | 07:12 |
| eugenmayer | mnasiadka, morning | 07:13 |
| jingvar | aaa, I use victoria/stable - Rocky just host OS | 07:22 |
| *** MikeCTZA_ is now known as MikeCTZA | 07:23 | |
| jingvar | Rocky on Kayobe control host and seed ( in my case seed and kayobe the same host) | 07:24 |
| jingvar | few dirty hack around ansible and it works | 07:24 |
| eugenmayer | jingvar, could you explain why flat will not work with OVN? | 07:53 |
| eugenmayer | i deployed the stack with OVN now with the same result. All instances i start on the flat provider network i created, cannot access the network (stuck on network up) | 07:53 |
| jingvar | what the interfaces you have on computes | 08:03 |
| *** mazzy5096 is now known as mazzy509 | 08:10 | |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: Revert "Do not load br_netfilter" https://review.opendev.org/c/openstack/kolla-ansible/+/814949 | 08:16 |
| opendevreview | Mark Goddard proposed openstack/kayobe stable/wallaby: Remove stale config dump from seed hypervisor host configure https://review.opendev.org/c/openstack/kayobe/+/815230 | 08:17 |
| opendevreview | Mark Goddard proposed openstack/kayobe stable/victoria: Remove stale config dump from seed hypervisor host configure https://review.opendev.org/c/openstack/kayobe/+/815231 | 08:18 |
| mnasiadka | mgoddard: you made my day with "reason for revert" ;-) | 08:18 |
| opendevreview | Mark Goddard proposed openstack/kayobe stable/ussuri: Remove stale config dump from seed hypervisor host configure https://review.opendev.org/c/openstack/kayobe/+/815232 | 08:18 |
| *** mazzy5098 is now known as mazzy509 | 08:23 | |
| eugenmayer | jingvar, eth2 for 'self service' and eth3 for 'wan', see https://github.com/EugenMayer/openstack-lab/blob/master/config/group_vars/compute/compute.yml#L4 | 08:25 |
| eugenmayer | i can see those br-wan / br-lan bridges online on the computes / controller | 08:25 |
| eugenmayer | on compute1: https://gist.github.com/EugenMayer/81747df977e15f2d7dd284af75fb4747 | 08:26 |
| jingvar | kayobe-config/etc/kolla/inventory/overcloud/host_vars/cmp01:neutron_bridge_name: "bond0-ovs" | 08:27 |
| jingvar | neutron_external_interface: "bond0" | 08:28 |
| mgoddard | mnasiadka: I aim to please | 08:31 |
| opendevreview | Merged openstack/kayobe stable/wallaby: Add the missing documentation for mariadb recovery https://review.opendev.org/c/openstack/kayobe/+/815074 | 08:37 |
| opendevreview | Merged openstack/kayobe stable/victoria: Add the missing documentation for mariadb recovery https://review.opendev.org/c/openstack/kayobe/+/815075 | 08:37 |
| eugenmayer | jingvar, what does that mean? | 08:37 |
| eugenmayer | i mean yes, that is similar, but how did you create the network in openstack? | 08:38 |
| kevko | \o/ morning | 08:39 |
| opendevreview | Merged openstack/kayobe stable/ussuri: Add the missing documentation for mariadb recovery https://review.opendev.org/c/openstack/kayobe/+/815076 | 08:39 |
| eugenmayer | good morning kevko | 08:41 |
| eugenmayer | jingvar, https://ibb.co/bFFhJBR that is the point, so after having configured physnet1/physnet2 how to create an openstack networking utilizing those | 08:41 |
| eugenmayer | AFAIU the type i'am looking for is flat, i properly configured the subnet, but when spawning an instance, it has no connectivity at all | 08:42 |
| jingvar | ohh - web UI | 08:46 |
| jingvar | Have you created a Router? | 08:47 |
| jingvar | openstack network create --external --provider-physical-network physnet1 --provider-network-type flat public1 | 08:47 |
| eugenmayer | no - no router. It is a flat network and i wanted to test network inter communication | 08:48 |
| eugenmayer | your cli variant is basically the same, isnt it? | 08:48 |
| jingvar | it was about external | 08:49 |
| jingvar | openstack network create demo-net | 08:49 |
| jingvar | openstack subnet create --subnet-range 10.0.0.0/24 --network demo-net --gateway 10.0.0.1 --dns-nameserver 8.8.8.8 demo-subnet | 08:49 |
| jingvar | for local-self network | 08:49 |
| kevko | eugenmayer: it's simple - if you want to have IP on external network, you have to create network as jingvar adviced, then run instance and wuala - it's working | 08:51 |
| kevko | eugenmayer: if it is not working , you should check ovs-vsctl show - and check if port providing external l2 connection is added to openvswitch bridge providing physnet for openstacj | 08:52 |
| jingvar | and default network type - I think | 08:52 |
| kevko | default network type ? | 08:53 |
| eugenmayer | kevko, i did use ovs-vsctl: https://gist.github.com/EugenMayer/81747df977e15f2d7dd284af75fb4747 | 08:58 |
| eugenmayer | jingvar, i cannot see any difference to my setup in yours right now | 08:59 |
| kevko | eugenmayer: hmm, i'm not using ovn ..but ovs ..my setup | 09:02 |
| eugenmayer | did not work with ovs either, same setup kevko | 09:03 |
| kevko | eugenmayer: https://paste.opendev.org/show/810190/ | 09:03 |
| eugenmayer | kevko, looked the same for me with ovs https://gist.github.com/EugenMayer/2a8329361fb2638203fc36561b665459 | 09:12 |
| eugenmayer | so i think both should work - and do not | 09:12 |
| kevko | kolla in default is operating with br-int, br-tun etc.. how you changed the names ? | 09:13 |
| opendevreview | Will Szumski proposed openstack/kayobe master: Do not fail when admin openrc file does not exist https://review.opendev.org/c/openstack/kayobe/+/815259 | 09:15 |
| eugenmayer | https://github.com/EugenMayer/openstack-lab/blob/master/config/group_vars/control/control.yml#L4 | 09:24 |
| eugenmayer | kevko, ^^ | 09:24 |
| opendevreview | Verification of a change to openstack/kolla stable/xena failed: openstack-base: drop anyjson https://review.opendev.org/c/openstack/kolla/+/814936 | 09:49 |
| opendevreview | OpenStack Release Bot proposed openstack/kayobe stable/xena: Update .gitreview for stable/xena https://review.opendev.org/c/openstack/kayobe/+/815267 | 10:02 |
| opendevreview | OpenStack Release Bot proposed openstack/kayobe master: Update master for stable/xena https://review.opendev.org/c/openstack/kayobe/+/815268 | 10:02 |
| opendevreview | OpenStack Release Bot proposed openstack/kayobe master: Add Python3 yoga unit tests https://review.opendev.org/c/openstack/kayobe/+/815269 | 10:02 |
| opendevreview | OpenStack Release Bot proposed openstack/kayobe-config stable/xena: Update .gitreview for stable/xena https://review.opendev.org/c/openstack/kayobe-config/+/815270 | 10:02 |
| opendevreview | OpenStack Release Bot proposed openstack/kayobe-config stable/xena: Update TOX_CONSTRAINTS_FILE for stable/xena https://review.opendev.org/c/openstack/kayobe-config/+/815271 | 10:02 |
| opendevreview | OpenStack Release Bot proposed openstack/kayobe-config-dev stable/xena: Update .gitreview for stable/xena https://review.opendev.org/c/openstack/kayobe-config-dev/+/815272 | 10:02 |
| opendevreview | OpenStack Release Bot proposed openstack/kayobe-config-dev stable/xena: Update TOX_CONSTRAINTS_FILE for stable/xena https://review.opendev.org/c/openstack/kayobe-config-dev/+/815273 | 10:02 |
| eugenmayer | jingvar, using your cli commands the type is not flat but geneve, that is the main difference here. User your setup but the box still cannot brin up the network | 10:03 |
| eugenmayer | ok it works vm to vm now | 10:03 |
| eugenmayer | so now i need to ensure the connectivity for the internet (yet not floating ip). I guess that is what the router are for | 10:12 |
| kevko | eugenmayer: how many physnets do you have ? | 10:17 |
| eugenmayer | right now, i have two. One for the self-service(1), one for wan (2). I could get self-service work, so spawning 2 VMs in the same project, the VMs can talk | 10:20 |
| eugenmayer | though, other non-openstack boxes, e.g. from the compute box itself, cannot talk to the VMs (so it is not really flat, its geneve, thus an isolated lan | 10:21 |
| kevko | hmm, it looks like you have two external networks | 10:39 |
| kevko | eugenmayer: if you want to use self-service networks, you don't need to add second bridge and interface to it | 10:40 |
| eugenmayer | consulting the actual OVN provider network docs, it seems to be the case, isn't it? : https://docs.openstack.org/networking-ovn/latest/admin/refarch/provider-networks.html | 10:44 |
| opendevreview | Merged openstack/kolla stable/xena: centos: switch to RDO final release of Xena https://review.opendev.org/c/openstack/kolla/+/814857 | 11:06 |
| opendevreview | Merged openstack/kolla stable/xena: update information about unbuildable images https://review.opendev.org/c/openstack/kolla/+/814944 | 11:06 |
| eugenmayer | net network group in kolla, when using OVN - what will it stand for, for the gateway nodes or where the neutron-server is deployed to? | 11:51 |
| jingvar | in my case controllers and network nodes it the same group | 12:09 |
| *** amoralej is now known as amoralej|lunch | 12:12 | |
| eugenmayer | jingvar, network nodes - with OVN, are those the gateway-nodes? | 12:49 |
| *** amoralej|lunch is now known as amoralej | 12:54 | |
| opendevreview | Egon Rijpkema proposed openstack/kolla-ansible master: keep X-Forwarded-Proto of exterbal ssl termination. https://review.opendev.org/c/openstack/kolla-ansible/+/758361 | 13:05 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: nova: don't fail all hosts on service registration failures https://review.opendev.org/c/openstack/kolla-ansible/+/805599 | 13:15 |
| jingvar | eugenmayer: I have 3 controller and fwe computes nodes | 13:50 |
| opendevreview | Merged openstack/kolla stable/xena: openstack-base: drop anyjson https://review.opendev.org/c/openstack/kolla/+/814936 | 14:00 |
| *** amoralej is now known as amoralej|off | 15:09 | |
| eugenmayer | jingvar, i dropped the idea of using a provider network for self-service when using OVN. i use one for the cluster/managemeent network and then create a vlan based self-service network with OVN - it jsut makes more sense and simplifies what OVN should have simplified in the first place | 15:27 |
| jingvar | eugenmayer: I think being near to real network topology is good idea | 15:29 |
| eugenmayer | jingvar, IMHO using OVN does exactly the opposite, don't you htink? | 15:31 |
| eugenmayer | it abstracts from the physical topology (for the cost of performance) | 15:31 |
| jingvar | I'm not sure than understood | 16:00 |
| jingvar | ovn and ovs as ml2 plugin have similar functionality | 16:01 |
| jingvar | there is defferenet approcach how traffic should be switched | 16:03 |
| jingvar | from my perspective OVN looks like OpenContrail | 16:04 |
| eugenmayer | jingvar, OVN tries to tunnel nearly all networks (i guess as OVS does), so it nests any network inside any other network - by design. This means (for me, IMHO) that the physical network / topology is just a the base network to offer the transport layer for any other nested network (l3 and even l2, if i understood it right). | 16:21 |
| eugenmayer | jingvar, OVN (and ovs) are build to not expose or limit by physical topology to offer way more flexebility and encapsulation. If find it similar to LVM somehow - abstracting away and encapsulating boundaries of physical drives | 16:22 |
| eugenmayer | But honestly, i'am new to all this. At least what i can see, the OVN deployment ref does use VXLAN or geneve for the self-service network, while OVS/Linux bridge use provider networks for the same int the ref. | 16:23 |
| eugenmayer | So there is, at least for the openstack guys, a difference in the 'strategy' | 16:24 |
| eugenmayer | big fat huge IMHO :) | 16:24 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: nova: don't fail all hosts on service registration failures https://review.opendev.org/c/openstack/kolla-ansible/+/805599 | 16:25 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: nova: use any_errors_fatal for once-per-cell tasks https://review.opendev.org/c/openstack/kolla-ansible/+/815335 | 16:25 |
| opendevreview | Mark Goddard proposed openstack/kayobe master: infra VMs: use wait_for rather than wait_for_connection https://review.opendev.org/c/openstack/kayobe/+/813212 | 16:33 |
| opendevreview | Mark Goddard proposed openstack/kayobe-config-dev master: Define infra VMs for testing https://review.opendev.org/c/openstack/kayobe-config-dev/+/805239 | 16:42 |
| opendevreview | Mark Goddard proposed openstack/kayobe master: CI: add Infra VM jobs https://review.opendev.org/c/openstack/kayobe/+/813048 | 19:12 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!