Saturday, 2025-04-26

f0ohttps://paste.opendev.org/show/bni0NTj441e5DrO1vP8k/ << pretty sure this is not supposed to look like this05:40
f0oI got all exchanges in all vhosts and things go bonkers05:40
f0ofor i in aodh ceilometer cinder dns glance heat ironic keystone magnum neutron nova sahara zaqar; do echo $i; /rabbitmqadmin delete exchange --vhost=swift name=${i} -H 10.20.1.114 -P 15671 -s -k -u x -p x; done # this worked to clean up swift at least. The rest doesnt seem to be hurting05:54
f0ohttps://paste.opendev.org/show/bIhFtyEk83w4XxscjawM/05:55
f0oceilometer-notif agent will simply recreate those whenever its started05:55
f0oand it will then crash with the same errors and ddos gnocchi in the process05:55
f0o*_ceilometer_enabled all set to False apart from swift_ceilometer_enabled also keeps recreating those exchanges and crashing on them with the same error; but at least it doesnt ddos gnocchi so hard it crashes06:26
f0oso seems like ceilometer is nonfunctional for our usecase. Guess i'll write some binary myself that gathers usage statistics instead06:27
SeiloHi Community06:51
SeiloIs OVN the default scenario in OSA?06:52
f0oMore or less yes; it will still need manual configuration to work properly (such as defining northd and gateway hosts etc)06:52
f0ohttps://docs.openstack.org/openstack-ansible-os_neutron/latest/app-ovn.html06:53
Seilof0o: When I installed AIO, I saw that OVN was brought up. So in general, for production installations, OVS is not the default, and according to what you said, only some points need to be defined in the configuration for OVN to work properly. I am asking for this confirmation because I want to mention a comparison with Kolla (where OVN is not the default).07:35
noonedeadpunkOVN is the default assumption, yes07:36
noonedeadpunkYou still can do OVS setup with couple of variables07:36
noonedeadpunk(and slightly different inventory)07:36
noonedeadpunkSeilo: that is the default: https://opendev.org/openstack/openstack-ansible-os_neutron/src/branch/master/defaults/main.yml#L399-L40107:37
jrossercomparing defaults imho is not very insightful with OSA07:37
noonedeadpunk(nor with kolla I believe)07:37
jrosserbecause you can choose/configure almost everything in any way you wish07:37
noonedeadpunkbut you better draw a design/architecture first to know/understand the state you need to reach07:38
jrosserthat really is the point of these kind of tools compared to the ones from big vendors that tend to be more rigid and opinionated07:38
Seilonoonedeadpunk: Kolla explicitly states that OVS is the default: https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutron.html#openvswitch-ml2-ovs  The same link further explains how to configure OVN.07:41
noonedeadpunkSeilo: I am not sure we do document defaults in docs07:46
noonedeadpunkI think we mostly oriented on describing typical scenarios overall07:47
noonedeadpunkFor isntance, networking scenarios can be seen here: https://docs.openstack.org/openstack-ansible-os_neutron/latest/07:47
noonedeadpunkso it is more of a path you choose in a way07:49
noonedeadpunkeven in AIO you can supply ovs scenario and it will be deployed with OVS over OVN07:49
SeiloThe link you shared is great. Thanks07:53
noonedeadpunkWe probably need to re-arrange and highlight that OVN is "default" in there...07:57
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Add CI jobs for Ceph on Ubuntu 24.04  https://review.opendev.org/c/openstack/openstack-ansible/+/94825508:17
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Add CI jobs for Ceph on Ubuntu 24.04  https://review.opendev.org/c/openstack/openstack-ansible/+/94825512:38

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