Tuesday, 2023-08-01

kargozariHey there04:27
kargozari`git clone -b stable/antelope https://opendev.org/openstack/openstack-ansible /opt/openstack-ansible`04:27
kargozariFatal: Remote branch stable/antelope not found in upstream origin04:27
kargozariIsn't there an Antelope branche?04:28
derekokeeffeMorning all, it's been a while, hope all is well. I have enabled cinder backups and it's working fine as expected from the cli. What I'd like to know is if it's possible to have an option in the dropdown for the volume in horizon to allow users to backup volumes and if so a link to where I can find how to do it would be great :)08:08
derekokeeffePlease ofc08:08
derekokeeffeIt's ok I got it :) thanks08:26
damiandabrowskiderekokeeffe: you can enable `horizon_enable_cinder_backup` and reexecute os-horizon-install.yml playbook09:09
damiandabrowskihttps://opendev.org/openstack/openstack-ansible-os_horizon/src/branch/master/templates/horizon_local_settings.py.j2#L30709:09
damiandabrowskithen you'll see something like this:09:09
damiandabrowskihttps://i.imgur.com/H3LiZXS.png09:09
derekokeeffe Thanks damiandabrowski09:11
hamidlotfi_do you create veth_cleanup.sh script in lxc_creete?10:35
hamidlotfi_Hi there.10:35
hamidlotfi_@noonedeadpunk 10:36
jrosserhamidlotfi_: the codesearch tool is very useful to find things like that https://codesearch.opendev.org/?q=veth-cleanup10:37
hamidlotfi_Thank you10:37
hamidlotfi_This script is wrong and does not work properly.10:38
hamidlotfi_this code must change to `ovs-vsctl del-port bridge_name port_name`10:39
jrosseryou are using OVS bridges for the LXC containers?10:42
hamidlotfi_in this code check `type=openvswicth` but doesn't work for me and just put `ip link del`10:42
hamidlotfi_yes10:42
hamidlotfi_i don't know why?10:42
jrosserhmm that is kind of unusual10:42
hamidlotfi_maybe10:43
jrosserthe way that the LXC bridges work is completely decoupled from choosing OVS for neutron10:43
hamidlotfi_Now, I corrected this manually.10:44
jrosserwell like i say, LXC bridges using OVS is not the same as neutron using OVS10:45
hamidlotfi_do you want see my config in `openstack_user_config.yml`10:45
jrossercan you explain a bit how you want it to work?10:45
hamidlotfi_I used OVN and Stable/ZED ver.10:46
hamidlotfi_when I reboot or shut down my infra server, after starting all LXC is in the stopped state.10:47
hamidlotfi_and I see this error on the run `ovs-vsctl show`10:48
hamidlotfi_`error: "could not open network device 5b47160e_eth7 (No such device)"`10:48
hamidlotfi_and this device is a lxc's network interface10:49
hamidlotfi_I must delete this and then start lxc.10:50
hamidlotfi_ok?10:51
jrosserthe default configuration for OVN or any other neutron networking is to use regular linux bridges, *not* OVS ones, for the LXC containers10:54
jrosseryou can choose if you want to to also have the LXC containers connect to OVS bridges, thats up to you, but it's not the default, and it's not what most people do10:55
jrosserhamidlotfi_: what i am trying to find out is if you specifically want to use OVS bridges for the LXC containers, or not?11:01
hamidlotfi_I had a problem with my network configuration (netplan) and I asked a question here and @admin1 answered to me 11:46
hamidlotfi_https://www.irccloud.com/pastebin/Sa3yUL0m/11:46
hamidlotfi_And then I changed all bridge to OVS bridge.11:47
mgariepywow. https://github.com/ansible/ansible/issues/7834412:02
jrosserhamidlotfi_: br-provider and br-vlan are to do with neutron networking so it is expected that you want those to be done with OVS12:29
jrosserhamidlotfi_: things like br-storage and br-mgmt are not to do with neutron so the default would be to use regualt linux bridges for those12:29
jrossermgariepy: what a great outcome12:34
jrossersoo many hours of debug :/12:34
jrosseri remember you spent *loads* of time looking at that12:34
opendevreviewKatarina Strenkova proposed openstack/openstack-ansible-os_manila master: Replacedeprecated terms  https://review.opendev.org/c/openstack/openstack-ansible-os_manila/+/89020212:37
hamidlotfi_jrosser:  This means that not all interfaces need to be OVS.12:41
jrosserhamidlotfi_: correct - you can set it up however you prefer12:41
hamidlotfi_jrosser: Thank you for your guidance.12:42
jrosserit's worth reviewing how the all-in-one works for this configuration12:42
jrosserthat should be your "reference" implementation12:43
mgariepyreminds me of the race condition i found in ceph-volume a couple years ago.12:44
mgariepyif i hadn't took the time to fix it i guess it would still be an issue.12:44
admin1hamidlotfi_, i meant type ovs for provider network bridges .. and not for others .. mgmt and storage .. but br-vlan and br-vxlan .. sorry i was not more clear 15:02
noonedeadpunkSorry folks, I'm not around today, can't participate in a meeting 15:03
mgariepyspatel, i use ovs fw without any issue.18:09
spatelmgariepy are you using openvswitch firewall?18:09
spatelIn production?18:09
mgariepyyes18:09
spatelhmm! Good to know.. 18:10
mgariepywith victoria at the start there were some flickering when ovs was restarting. without the neutron part.18:10
mgariepybut it's now fixed 18:10
mgariepyold arch without dvr18:11
spatelYou are saying its more stable now correct no glitch or surprises :)18:11
mgariepywent with that to save some hop in user/kernel space and to be more ready for the ovn switch at some point.18:11
mgariepyyep works quite well.18:12
spatel+1 perfect! then i will use OVS  firewall 18:13
spatelTrying to reduce complexity in path of the packet flow 18:13
mgariepyi do use the vlan directly via ovs, no lx bridge on top to bind to it.18:18
tuggernutsHey all, I'm working on deploying an opestack environment with the antelope openstack ansible and I'm having issues with gnocchi. I applied the change recommend form https://bugs.launchpad.net/openstack-ansible/+bug/2026828 by putting `gnocchi_git_install_branch: 6f35ea5413a9f78551d8193b8d2a6d77c49b6372` is user_variables but now I'm getting a new error. https://pastebin.com/gSAnCTBQ19:47
tuggernutsnot really sure where to go from here it seems to pretty consistenly fail on this step19:49
spatelmgariepy I am trying to configure magnum with Xena release but having strange issue with fedora-coreos-35.20220116 image. 20:07
spatelDoes that image works with Xena? 20:08
tuggernuts1I ran setup-openstack again without changing anything and now it's this error: https://pastebin.com/hHEzgaAT20:22

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