15:01:03 #startmeeting openstack_ansible_meeting 15:01:03 Meeting started Tue Apr 23 15:01:03 2024 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:03 The meeting name has been set to 'openstack_ansible_meeting' 15:01:07 #topic rollcall 15:01:09 o/ 15:01:26 o/ hello 15:02:49 so, I failed quite a bit to send out PTG results :( 15:02:58 though there were not much things 15:03:19 mainly moved things from the past one to the new cycle 15:06:54 #topic office hours 15:08:14 so, there was a ML thread abour cluster-api deployment with osa: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/27R2UOTCIHNAAGFFCG36KWHDPFLD3TZ4/ 15:08:31 I was mainly guessing there as never checked it/played enough myself 15:08:45 no idea if folk gave up or made it working though 15:09:30 hiya folks 15:11:37 o/ 15:12:12 I'm actually planning to keep pushing patches this week for quorum queues improvements 15:12:32 as this needs to be done across all services - would be good to know a health state overall 15:12:39 until it's not _too_ late 15:12:43 i think that the cluster api guy from the ML showed up in the cluster-api slack channel and i helped out there 15:12:50 ah 15:13:10 ok, good to know there's some slack channel :D 15:13:13 that was the push i needed to get it fixed up last weekend 15:14:59 Also, if anybody missed, I've opened Answers section in launchpad, where almost instantly landed question around OVN docs: https://answers.launchpad.net/openstack-ansible/+question/709484 15:18:40 this is kind of a big problem 15:22:22 that I've opened it?:) 15:22:53 or that we're bad in documentation? 15:26:25 also as an update - frrouting role has been moved under our governance. it's needed for ovn-bgp-agent implementation 15:26:35 i think the trouble is that OVN is so hard 15:26:35 nice :D 15:26:44 I really need to look into OVN 15:26:55 Actually, I don't find it _that_ hard today 15:27:05 sorry i'm distracted today... covering for a few people 15:27:07 like it's mainly just very different 15:27:08 and simultaneously the docs do not show a newcomer what all the moving parts are 15:27:25 and how to translate what you want into working config 15:27:38 i think the problem is that OVN is itself a huge beast, and so a newcomer to OpenStack **and** OVN will be like "WTF!" 15:27:47 right 15:27:49 yeah, and I think we lack of examples. Or better say - they're hidden in os_neutron docs 15:28:08 also OpenStack Networking in general is pretty counter to what a "Network Engineer" would expect 15:28:10 yeah, I think you might be into smth NeilHanlon 15:28:33 like I still have to reprogram my brain to think about what OpenStack does with provider/external nets :) 15:30:28 it was always left to the deployer for the network configuration 15:30:50 stuff can work quite differently with ovn tho. 15:38:08 i think it is pretty difficult on top to understand what to put in openstack_user_config 15:38:17 yeah 15:38:21 there are too many wierdly named fields 15:39:17 there are many ways to do stuff also. 15:39:51 so primarily this is a documentation issue then 15:40:20 yeah, maybe we should somehow promote neutron_provider_networks which is way more obvious.... 15:41:09 but then when I tried to - it was even more confusing on what to add where 15:46:08 surely the AI can do it for us 15:46:09 * NeilHanlon ducks 15:47:14 this is also not a case of making some quick fix to the docs for some error 15:47:31 it needs time/concentration to make a coherent set of stuff for how things actually are with OVN 15:47:43 yeah 15:48:38 * NeilHanlon will ask in his circles if anyone might be interested in some OSA+OVN documentation 15:48:49 work* 15:50:10 well, I partially did some 15:50:20 but apparently we have more places to fix 15:50:26 like deployment guide at least 15:51:21 maybe we have to start from what got put in the launchpad answers section 15:53:16 yeah 15:54:05 that sounds as a good start 15:58:00 #endmeeting