19:01:03 #startmeeting infra 19:01:03 Meeting started Tue Jan 11 19:01:03 2022 UTC and is due to finish in 60 minutes. The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:01:03 The meeting name has been set to 'infra' 19:01:23 #link https://lists.opendev.org/pipermail/service-discuss/2022-January/000311.html Our Agenda 19:01:45 one thing that occured to me as I prepared for this meeting is that we have https on our list servers now but don't redirect http to https 19:01:57 fungi: ^ should we do redirects on all of the vhosts now that https is working happily? 19:02:46 the link to the agenda works via http 19:02:47 that isn't urgent so I'll continue on, but wanted to call it out 19:02:59 jentoio: yup it works via both. I think we should force http to redirect https though 19:03:04 *to redirect to 19:03:16 right 19:03:19 #topic Announcements 19:03:31 i can try setting up https redirects for that, it's worth noting that http is hard-coded into a lot of the urls though so it may end up with more browser warnings 19:03:39 fungi: ah that is too bad. 19:03:46 unless we configure it to also rewrite page content 19:03:59 i think it's configurable though 19:04:14 we'd just need to update the mailman configs to use https urls everywhere 19:04:20 The OpenInfra Foundation board election is happening right now. If you are an individual member for long enough (I forget the exact period of time) you should have received a ballot in your email inbox. Please don't forget to vote 19:04:31 six months 19:04:56 also the ballot includes a measure to update the wording for the bylaws 19:05:16 so you'll be prompted to vote for that as well on the same ballot 19:05:22 well, for or against 19:05:38 yup and you'll get separate email receipts for your votes against the bylaw update and the membership vote 19:06:09 Also this is your reminder that OpenDev Service coordinator nominations run January 25, 2022 - February 8, 2022. I'm more than happy for someone else to give it a go :) 19:06:36 If you are interested feel free to reach out with questions. And I'll definitely be around to help assist should someone else take it on 19:06:58 #topic Actions from last meeting 19:07:02 #link http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-12-14-19.01.txt minutes from last meeting 19:07:19 There were no actions recorded. Not surprising as we were already slowing down for the year at that point. But we are back now :) 19:07:32 Let's dive into the topic list now 19:07:36 #topic Ansible lint failures 19:08:00 I had this on the agenda to make sure we didn't let these issues linger longer than necessary. But ya'll are on top of it and the fixes I pushed appear to have all merged overnight 19:08:11 This means we can land zuul ansible updates again 19:08:43 Thank you to everyone who jumped on that 19:08:56 #topic Improving OpenDev's CD Throughput 19:09:25 ianw is still out for the holidays. I believe the spec outlining the next step here still needs review though 19:09:27 #link https://review.opendev.org/c/opendev/infra-specs/+/821645 -- spec outlining some of the issues with secrets 19:09:38 infra-root ^ if you have time to review that it would be appreciated (I need to review it myself) 19:10:02 #topic Container Maintenance 19:10:12 #link https://etherpad.opendev.org/p/opendev-container-maintenance 19:10:25 This is something that I'm starting to pick up now that I'm back. 19:10:55 kopecmartin will test the refstack bullseye image update and if that doesn't look problematic I'll go ahead and approve it in the next day or two hopefully 19:11:09 We've also got lodgeit bullseye updates sitting behind the uwsgi image update. 19:11:14 #link https://review.opendev.org/c/opendev/system-config/+/821339 to update uwsgi for lodgeit 19:11:41 If we can go ahead and land the uwsgi image update for bullseye then we can land the lodgeit update (they are separate chagnes) when we are able to monitor. I probably have time for that this week as well 19:12:09 I'd prefer to not single core approve uwsgi updates since it is sort of a hack around a problem. But that reminds me that maybe upstream fixed the problem and we can check that directly first and maybe avoid the hack 19:12:58 The other big thing I've started to look at is updating some of our containers to run with dedicated users. Sounds like jentoio is willing to help me with that (thanks!). I'll try to set up time this week with jentoio to go over what is needed and propose more changes 19:13:36 That etherpad has a few other things we should look into but I think they are all good followups for once the above set of updates are completed (bullseye updates and better user management specifically) 19:14:20 I'm just going to keep running through the agenda. I think we've got low attendance today as people aren't all quite back from holidays and there isn't a ton to cover yet as we paused work for a bit too 19:14:28 #topic Nodepool image cleanups 19:14:46 We now have volunteers to maintain OpenSUSE Leap 15 and Gentoo. 19:15:11 That leaves us with CentOS 8, Fedora 34, and Tumbleweed needing cleanup. The tumbleweed removal actually happened overnight. 19:15:36 I believe ianw was looking at Fedora 34 so we can probably wait for ianw to return to finish that up 19:15:44 F34 still has a couple of months unless I'm mistaken 19:15:58 frickler: it does, but we cannot boot it reliably because they broke their initramfs generation 19:16:01 also devstack+neutron still depend on it 19:16:08 our f34 images only boot in like 2 clouds right now 19:16:27 oh, I thought that that issue was with F35 19:16:33 so the plan ianw proposed was to switch to f35 whcih doesn't have initramfs problems 19:16:43 frickler: they both had it but they fixed f35 and not f34 19:17:06 right, they ended up not backporting the fix 19:17:08 It seems that the problem didn't meet the level of urgency to fix on f34 at least not urgently 19:17:17 they simply left 34 broken 19:17:33 so maybe some of the RH neutron folks can help with getting F35 to run for them 19:17:46 that only seems fair ;) 19:17:48 Its not a perfect solution but one that is in line with our previous treatment of fedora (basically move everything to latest fedora when available and drop old) 19:17:51 ++ 19:18:19 FWIW I expect CentOS 8 removal to be similarly painful but at larger scale because lots of things use it 19:18:28 I guess I should send a reminder and maybe an email to opensatck specifically 19:18:41 though folks are already noticing things breaking on centos-8 images 19:18:47 some people have already started converting to stream which is good but I doubt all have. 19:19:44 I'll make a note to send the reminder that CentOS 8 is EOL and opendev will be working to remove the image today 19:20:13 But then I think we start pushing up changes and force merging updates if we have to after people have a chance to do it more gracefully 19:21:30 sounds good to me 19:21:54 #topic Scheduling Gerrit Project Renames 19:22:26 We have project rename requests. I think we'll want to be careful to do this in a way that doesn't interfere with the openstack release schedule or Zuuls as zuul approachs zuulv5 19:23:11 Anytime in january is probably fine https://releases.openstack.org/yoga/schedule.html does anyone have opinions on this? 19:23:26 normally I'd suggest the 21st but I think I have a doctors appointment that day 19:23:37 i'm available any time, but yeah i agree on the timing suggestions 19:23:40 perhaps do it on a Monday the 23th? 19:23:45 er 24th 19:23:48 (I cannot type) 19:23:56 wfm 19:24:18 ok lets pencil that in and can start proper planning on the 18th 19:24:35 and preferably not at peak activity that day 19:25:03 ya yseterday was super quiet activity wise, but I wonder if that will hold up through january. Today is much busier in zuul 19:25:54 separately I've been looking at using the gerrit rename-project plugin to do renames. This plugin can do renames without a downtime. but introduces races replicating projects. I've got a change up that doesn't pass currently trying to test this. I don't think we should block on itand instead use our established process. This will come up again and we can make use of no 19:25:55 downtime renames then 19:26:39 that was all I had on the agenda 19:26:41 #topic Open Discussion 19:26:55 I'm sure I've missed stuff with the holidays and all that. Feel free to call out anything else now 19:27:35 I believe CFP for summit is open (reminder) 19:28:46 also worth mentioning, openstackid.org is becoming id.openinfra.dev, and i've got a few changes up to work through impact on systems we manage under topic:openinfraid 19:29:35 specifically i'll need to make database edits to zanata and refstack for the new ids 19:30:10 looks like you were going to do translate -dev first and then when that is happy do the others? 19:30:28 correct. i'll use translate-dev to test the transition 19:30:49 a date for the PTG was also announced (2022-04-04 - 08), at least that was news to me 19:31:13 basically i need to figure out if zanata supports multiple openids in its database, or if i need to replace existing openids directly 19:31:30 so translate-dev gives me an opportunity to experiment 19:32:17 we'll probably also want to update the keycloak poc for that transition 19:32:53 I feel like other people are more clued in on the events than I am. Not necessarily a bad thing but I work with the organizers :) 19:33:23 fungi: did keycloak get configured to talk to the old name? 19:33:31 yes 19:33:32 or is it just a matter of using the correct new name now when it gets configured 19:33:33 ah ok 19:33:45 we tested it with openstackid.org 19:33:54 and also google, i think 19:35:01 I'll give it a few more minutes for anything else then call it and we can all go find lunch/dinner/$MEAL 19:38:39 Sounds like that may be it. Thank you everyone and welcome back, happy new year :) 19:38:48 thanks! 19:38:50 thanks clarkb! 19:38:53 #endmeeting