15:00:07 <noonedeadpunk> #startmeeting openstack_ansible_meeting 15:00:07 <opendevmeet> Meeting started Tue Aug 24 15:00:07 2021 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:07 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:07 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting' 15:00:18 <noonedeadpunk> #topic rollcall 15:00:36 <noonedeadpunk> o/ I'm partially here from phone 15:06:03 <noonedeadpunk> #topic office hours 15:06:27 <noonedeadpunk> So, we are facing some new bug with mariadb 10.6.4 15:06:54 <noonedeadpunk> During mysql_upgrade things stuck and cause timeouts 15:07:14 <noonedeadpunk> Btw I noticed that only on focal, but not sure if it's limited to it 15:08:08 <noonedeadpunk> Anyway think we can rollback to 10.5.12 since we bumped only master. At least we will know if that helps or not. 15:08:26 <jrosser> i can make a patch for that 15:09:08 <noonedeadpunk> It would be simple revert I guess 15:09:41 <opendevreview> Merged openstack/openstack-ansible-os_neutron stable/wallaby: Add support of OVN for CentOS-8-Stream https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/804717 15:09:48 <noonedeadpunk> Oh, btw, on W I think there were no timeouts lately? 15:10:31 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-galera_server master: Revert "Update galera to 10.6.4" https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/805822 15:10:32 <noonedeadpunk> So that should help then 15:11:17 <noonedeadpunk> Another thing was haproxy role for managing endpoints vs included tasks 15:12:05 <noonedeadpunk> logan- aimed to make backend disablement smart, but I think it's too complicated and a bit risky 15:12:40 <noonedeadpunk> On terms that missing sudoers or invalid policy would make service unusable before any handlers 15:14:04 <noonedeadpunk> Also I pushed patch to add serial everywhere and wanted to do same with haproxy endpoints 15:14:20 <noonedeadpunk> But wasn't sure what way to choose 15:16:56 <noonedeadpunk> Also, I wonder if we should switch from depth to shallow_since for all repos in a-r-r as it feels like more reliable thing since some time from release 15:17:18 <noonedeadpunk> And we always pull only required history 15:23:28 <noonedeadpunk> I was supposed to call for a contributor with patches to our roles without using OSA overall to join our meeting but I didn't do that :( I will try to reach them tomorrow morning for the next meeting 15:23:44 <jrosser> looking at the existing code the strategy for serial/parallel installation is not totally clear 15:28:36 <noonedeadpunk> Um, what do you mean? 15:29:29 <noonedeadpunk> Meta handler "Manage LB"? 15:33:21 <noonedeadpunk> That is part of the logan- role that is used only for galera 15:33:46 <noonedeadpunk> For other roles it's was never fully implemented, but just started 15:34:05 <jrosser> there already seems provision for nova/neutron/cinder, but not anything else 15:34:40 <noonedeadpunk> Yeah, that's true 15:34:55 <noonedeadpunk> Also glance I guess and keystone 15:35:16 <noonedeadpunk> Well, and galera 15:37:15 <noonedeadpunk> But we indeed manage haproxy for super limited amount of roles 15:37:35 <noonedeadpunk> Which I guess high time to change 15:38:25 <noonedeadpunk> spatel are you around? 15:38:29 <spatel> yes 15:38:32 <spatel> always :) 15:39:25 <spatel> catching up this thread 15:39:32 <noonedeadpunk> Awesome. I had second thoughts about skyline:) well, I researched project a bit more 15:40:07 <spatel> noonedeadpunk nice! if we want then i am happy to work on it and integrate support with OSA 15:40:17 <noonedeadpunk> While it's still actively developing and afaik is not prod ready yet (because of missing ci and some things) 15:41:02 <noonedeadpunk> But once it will be released I think it would be great to have role for it 15:41:52 <spatel> noonedeadpunk totally it has lots of built in features and also high performance UI. 15:42:30 <noonedeadpunk> Maybe we can create repo even before that time but it will be incubated 15:42:44 <spatel> I have already started submitting bugs https://bugs.launchpad.net/skyline-apiserver 15:42:53 <noonedeadpunk> Until official first release of skyline 15:43:07 * jrosser looks for federated logins there..... 15:43:34 <spatel> I would say lets add support on OSA so more people will start using it and we will have more bugfix 15:44:23 <spatel> I am already talking to core developer of skyline team and they are super active in response. 15:44:35 <noonedeadpunk> Oh, that's nice 15:44:51 <noonedeadpunk> I hope they have irc channel:) 15:45:13 <spatel> They are in china so just talking to them on email. 15:45:24 <noonedeadpunk> Oh! Also, what do you think about adding freezer to OSA? 15:45:38 <spatel> I will ask them to create IRC so we have more better communication + more people will join 15:46:03 <noonedeadpunk> Yeah, email is... Meh 15:46:42 <noonedeadpunk> I kind of have role for freezer that I wrote on my free time 15:48:05 <spatel> noonedeadpunk does OSA has ironic support? i never heard from you guys so asking 15:48:28 <spatel> we don't have CI also for that role 15:49:38 <spatel> https://docs.openstack.org/openstack-ansible-os_ironic/latest/ not sure if anyone using it here. i am little interested to play 15:49:39 <noonedeadpunk> But project is a bit undrmaintained 15:50:01 <noonedeadpunk> Um, yes, I believe Ironic is used 15:50:20 <jrosser> kind of like os_octavia+++++ 15:50:43 <jrosser> that you need to understand the service itself and know what you're doing, before running the role and expect it to "just work" 15:51:14 <jrosser> theres some networking to do and interesting multitenancy 15:52:52 <noonedeadpunk> Btw, do you think we can merge that as initial commit and add encryption of keys with follow up? https://review.opendev.org/#/c/800792 15:53:59 <jrosser> sounds reasonable 15:54:13 <jrosser> something on my mind was if we want to use vault to manage user_secrets at all 15:54:43 <jrosser> which would get a bit circular with the galera credentials, if galera is the backend for vault 15:54:54 <noonedeadpunk> Well, yes 15:55:22 <noonedeadpunk> I guess we need to add native storage support there as well 15:55:46 <noonedeadpunk> To be able to use it as storage for user_secrets 15:56:45 <noonedeadpunk> I almost forgot! It's about due time for posting release highlights 15:56:54 <jrosser> maybe thats mixing up too many things though, dedicating a vault inside the deployment to barbican is very clean 15:57:10 <noonedeadpunk> And I'm not sure what we can post except ceph pacific there 15:57:28 <jrosser> somehow it feels like we don't yet start work on X :/ 15:57:44 <noonedeadpunk> Yeah:( 15:58:17 <noonedeadpunk> And it's already libraries fix time 16:00:27 <spatel> what is holding us to start X rc release? 16:00:40 <noonedeadpunk> Regarding vault - we can have multiple of them if needed and just make role usable on pre-osa step on standalone hardware 16:01:05 <jrosser> yes, thats a good idea 16:01:21 <noonedeadpunk> But that would still require either standalone galera or internal storage 16:01:32 <jrosser> spatel: it's more like needing effort to work on features, we really only just finished up W release for real 16:02:00 <jrosser> we run raft protocol local storage here, seems to be OK 16:02:02 <noonedeadpunk> Once neutron land I think I will do 23.1.0 release 16:02:23 <jrosser> yes, and the venv_build host permissions speed-ip 16:02:27 <jrosser> speed-up 16:02:33 <noonedeadpunk> And python_venv_buold optimization 16:02:34 <spatel> yeah! after 23.1.0 we can focus on X 16:02:35 <noonedeadpunk> Yeah 16:03:27 <noonedeadpunk> Ok, sounds like plan:) 16:03:35 <noonedeadpunk> #endmeeting