Friday, 2025-03-28

f0o_noonedeadpunk: that's not something I tried, only tried disassociating and reassociating06:48
*** f0o_ is now known as f0o06:48
f0oI guess the correct way of migrating this would be to recreate the networks entirely along with all fips etc? :/06:49
noonedeadpunkf0o: well, I'm still somehow thinking about running neutron-ovn-db-sync-util once you make changes in mappings/enable distributed fips07:56
noonedeadpunkas that will sync state of ovn dbs  with intended states from neutron mysql db  07:56
noonedeadpunkand ovn should rebuild flows and all required stuff once proper data is put to nb/sb dbs07:57
f0ook07:57
f0ohave no issue with trying it07:58
f0oI'd run this on the northd container?07:58
f0oor where?07:58
noonedeadpunkon neutron-server07:58
f0ookidoki07:58
noonedeadpunkbut don't forget to pass it config files explicitly07:59
noonedeadpunkml2_conf.ini and neutron.conf are of main interest to the tool07:59
f0oneutron-ovn-db-sync-util --help is a wall of text of parameters wow08:00
f0oneutron-ovn-db-sync-util --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini08:02
f0othis should be it right?08:02
noonedeadpunkwe have example here :https://docs.openstack.org/openstack-ansible-os_neutron/latest/app-ovn.html#ovn-database-population08:05
f0oand here I want repair or migrate?08:08
f0oor both? :D08:09
f0osince I know that I'll lose connectivity on this shell I rather ask all the stupid Qs now\08:09
noonedeadpunkum, don't know really... I guess I'd do migrate?08:11
noonedeadpunkjust to rebuild them from scratch...08:11
f0oalrighty08:11
noonedeadpunksec08:12
noonedeadpunkdo you do ocvtavia ovn lb?08:12
f0onop08:12
noonedeadpunkas these are not populted with this command08:12
noonedeadpunkok08:12
f0oso my plan now: Set network_geneve_ranges to vlan:100:3000; network_mappings becomes a host_var, being vlan:br-ext for compute and vlan:br-fip for gateway nodes; network_interface_mappings becomes a hostvar for gateway nodes which set br-fip:mlag123 instead of the previous br-ext:mlag123; update the networksegments table in neutron to make the networks 'vlan' where they08:14
f0owere 'fip'; run ansible & get downtime; run neutron-ovn-db-sync-util with migrate; hopes&payers08:14
f0oam I missing anything?08:14
noonedeadpunkeh, probably not... mpore hopes...08:20
noonedeadpunksry, I need to run away now so will likely be afk for the day...08:20
f0ono worries I really appreciate all the pointers and worst case I just do a full revert like yesterday haha08:22
f0ogonna make another coffee and then just yolo this08:22
noonedeadpunkkeep us updated about theresult)08:41
f0onoonedeadpunk: no change10:09
f0oI tried just doing the mapping change and not going full distributed fip yet; that also didnt work10:10
f0omigrate didnt seem to do anything at all10:10
f0oit flagged the same ports/networks as needing update no matter how often I ran it10:10
f0o(I also ran repair, same no-change)10:15
f0odoes distributed fip require all compute nodes to become gateway nodes?10:37
f0oI'm just trying to understand whether I'm barking at the wrong tree here or not10:38
f0obut I think the main issue is that I cant seem to be able to move the networksegments from fip->vlan provider10:40
f0othe values in networksegments db seem to be entirely ignored even with the migrate config10:41
f0owhich leads me to belive that I will have to change the SB DB manually10:41
f0obut that really sounds like HereBeDragons10:41
f0oI know I can do a backup of the SB DB, sed s/fip/vlan/g the json dump and restore it... but I've no idea what harm that would o10:44
noonedeadpunk> does distributed fip require all compute nodes to become gateway nodes?15:29
noonedeadpunkno, they do not afaik15:29
mgariepyno17:45
mgariepyyou need to add ovn_gateway group to the nodes you want to be serving gw 17:46
mgariepyneutron_ovn_gateway group.17:46

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!