Tuesday, 2024-05-07

clarkbhello it is meeting time19:00
clarkb#startmeeting infra19:00
opendevmeetMeeting started Tue May  7 19:00:33 2024 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
opendevmeetThe meeting name has been set to 'infra'19:00
clarkb#link https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/thread/HDXZPH7XJI5O5SDOCC35RGUALV7SUDZS/ Our Agenda19:00
clarkbWe have an agenda but I half expect this to go quickly as I believe attendance may be light19:00
clarkb#topic Announcements19:02
clarkbI don't have anythign to announce other than that I expect this to go quickly and attendance to be light19:02
clarkb#topic Upgrading old servers19:02
clarkbWith the release of Noble the year long countdown to getting off of focal has started19:03
clarkb#link https://etherpad.opendev.org/p/opendev-focal-server-upgrades19:03
clarkbtonyb has started putting notes together for the needs there. I added some annotations and flavor to try and categorize things19:03
clarkbtonyb: would it be preferable for me to just go ahead and rearrange or do you like having the notes?19:03
tonybWhatever works for you.19:04
tonybI certainly have no objection to you moving things around19:04
tonybI just did the bit I knew and figured I'd slowly figure the rest out19:04
clarkbsounds good19:05
clarkbThe other idea I had here was to maybe try and consolidate the various server upgrade todo lists into one big list?19:06
clarkbthen we don't need new documents over time as we have different upgrades to do19:06
clarkbI guess one reason not to do that is things might get too cluttered. I'm open to feedback on that19:07
tonybYup we can do that.   Should be easy enough.   I'm happy to give it a try and see what it looks like.19:07
clarkbthanks!19:07
clarkbI did also want to note that your changes to prep meetpad upgrades to jammy have landed and the changes to add the new servers are up19:08
tonybYup.19:08
clarkbas mentioned in review on the inventory update I think we want to do that with the old servers in the emergency file so that we don't end up with a weird cluster state but otherwise I think this should be straightforward19:08
tonybAs you pointed out we probably need a little care before takign the next step.19:08
tonybI'll double check, but I think we're good to go. perhaps Thursday sometime?19:09
clarkbthat should work for me19:10
tonybcool beans19:10
clarkbmornings are generally better simply because then I feel more confident we'll have time to work through any issues over the day19:10
clarkb#topic MariaDB Upgrades19:11
tonybYup.   We can figure out a time that works with TZ, and real world commitments in #opendev19:11
clarkb++19:12
clarkb#link https://review.opendev.org/c/opendev/system-config/+/916848 Update Gerrit's Mariadb19:12
clarkbthis is still lacking reviews. I'm happy to approve this change if others review it and give it +2s19:12
tonybI thought I had.19:12
tonybI have now19:12
clarkbspecifically I think we should plan to do a short gerrit downtime after the change merges to ensure we've got the upgrade in place after merging it as this won't happen automatically19:12
clarkbthanks!19:12
clarkbbut other than that change and the manual tasks to deploy it all mariadb upgrades are complete19:13
clarkb#topic AFS Mirror Cleanups19:13
clarkbtopic:drop-ubuntu-xenial has changes up for rewiew.19:13
clarkbI think this is largely where we're at now. I'm hoping to avoid a large backlog of changes like this sitting in my open queue. Ideally I write a few and we merge a few and slowly chip away19:14
clarkbLooks like a number of them have reviews and I just need to approve them when I can monitor. I think I'll try to do some of that today/tomorrow. We'll see how the days go19:14
tonybSounds good to me.19:14
clarkb#topic Building Ubuntu Noble Images and Test Nodes19:15
clarkbAs mentioned last week the next step here is adding Noble to our mirror content and babysitting what is likely to be a large set of data that needs to be downloaded and released in afs19:16
clarkbin particular i Know we'll need a quota bump on the volume at least.19:16
clarkbI don't thik anyone has volunteered for that yet and I'm trying to focus on the cleanups until that is more fully done before I take on adding stuff. But if anyone else has time for this I think we can add content19:16
tonybI doubt I'll have time before this meeting next week but I can probably do it after that.19:17
tonybI have spent some time reading and learning more about AFS so I can try to pick up work items in that area.19:17
clarkbcool we can resync at the next meeting then19:19
clarkb#topic Gerrit 3.9 Upgrade Planning19:19
clarkb#link https://etherpad.opendev.org/p/gerrit-upgrade-3.9 Upgrade prep and process notes19:19
clarkbI spent a bit of yesterday doing some testing of this and I have learned new things19:19
clarkb#link https://review.opendev.org/c/opendev/system-config/+/918333 Need updated and promoted 3.9 image before doing more testing.19:19
clarkbFirst up is that when I thought I had updated the 3.9 image previously I didn ot because the promote job didn't run. Pretty sure this happend for the same reason it didn't run against an etherpad change recently: I only modified the job definitions and not the dockerfile19:20
clarkbthis will also update our 3.8 image so we should plan a restart for that. Maybe combine the 3.8 update and the mariadb upgrade after merging both of those changes?19:20
clarkbOnce that is done I can resume testing particularly of the downgrade using images that are likely to end up in production rather than old buggy images19:21
clarkbOne of the questions from last week is whether or not hte change topic limit limitation of 5k changes per topic by default would be a problem for us19:21
tonybYeah I agree WRT combining the timing for MariaDB and the new 3.8 container restart19:21
clarkbthrough testing I am confident that the limit only applies to open changes and not the total of open and closed changes. This means we're fine for the new-release topic which is known to have more than 5k total but never near that many open19:22
clarkbI also tested an upgrade from 3.8 to 3.9 with the limit being exceeded and that did not seem to impact the upgrade process at all19:22
tonybwhich is all goodness19:23
clarkbThe only thing the limit seems to affect is when at or over the limit and you try to add a chagne to the topic you get an error. But even that is pretty forgiving. If you restore an abandoned change with a topic that would be over the limit the restore works just fine19:23
clarkbyup I'm fairly confident now that we can do the upgrade and not worry about the topic limit. Then if we ever find a reason to have more than 5k open changes in a topic we can revisit and adjust the config. But for now we're good as is19:24
clarkbThe other thing I've tested and tried to improve upstream is building the Gerrit docs without webfonts19:24
tonybThanks Clark19:24
clarkbTesting shows some slight rendering differences but they are all minor and I think I'd rather have small rendering differences than load a bunch of fonts from google19:24
tonybon gerrit tangent did our without-webfonts patch get any feedback?19:25
clarkbBy default the gerrit release war does not know how to remove the webfont though so I wrote a change that I pushed upstream to do that19:25
clarkb#link https://gerrit-review.googlesource.com/c/gerrit/+/424404 Upstream change to have release war build target without webfonts19:25
clarkbtonyb: not yet the last time I checked19:25
corvusi wonder if we should start considering discouraging topics for things like that and encourage tags instead19:25
corvussince topics do have a use in gerrit for submitwholetopic.  i don't have any expectation we would ever turn that on for openstack, however, it's starting to feel like the wrong tool for the job now that it has that additional functionality in gerrit19:26
corvus("things like that" == release process)19:26
clarkbcorvus: ya I think that gerrit diverged on how topics are used and never really communicated that explicitly19:27
clarkbit just happened naturally due to the same topic merge functionality I think19:27
corvusexactly19:27
corvusanyway, no need to discuss further or decide now; just throwing out a brainstorm :)19:27
tonybcorvus: We could probably do that.  We'd just need to ensure that the tags stuff is as easy to use as the topics stuff ATM19:27
tonybI've never really looked a tags19:28
clarkbtonyb: ya thats an acl update. But also I think we can address that separately to the upgrade19:28
tonybYup19:28
corvustonyb: yeah, and i think that means really doing that acl update.  which would be a good side effect of the process. because tags rock.19:28
clarkbbasically we just need to allow registered users or whatever to globally set hashtags then let projects limit that if they wish19:28
clarkbThat was the end of what I learned about the upgrade process. The good news is everything I was concerned about so far has been a non issue19:29
clarkbI'll resume testing once we have new images and make sure the revert process is viable for us19:29
clarkb#topic Wiki ssl cert renewal19:30
clarkbThis is on my todo list to do friday ish. Just a few more days then the notifications should go away19:30
clarkbas before noting it in the meeting to make sure it isn't overlooked and everyone knows that it will be dealt with before it expires19:30
clarkb#topic Open Discussion19:30
clarkbI maybe should've considered this an announcement but I've been asked to let people know the CFP for the openinfra summit in korea is open until may2919:31
tonybOh and git-review does hashtags already19:31
clarkb#link https://openinfrafoundation.formstack.com/forms/openinfra_asia_summit_2024 OpenInfra Summit CFP is open19:31
tonybThanks.19:32
clarkbThe event happens at the beginning of September in a city outside of Seoul (I think within metro service distance)19:32
tonybI've been asked by dpawlik to see if there are objecstions to enbing the elasticsearch reporter in the opendev zuul?19:33
tonybI'm guessing it's report to the existing opensearch site19:33
* tonyb would really like to go to Korea for the summit19:33
clarkbit would probably be good to describe what the use case is. My initial reponse having run a large elasticsearch cluster for years is that I want nothing to do with that19:34
tonybLOL19:34
clarkbI'm also not sure we should have reporters to sinks that we don't run (smtp is a weird one we report to the local smtp server iirc but then normal smtp happens to deliver elsewhere)19:35
clarkbbut understanding the use case would be helpful before saying anythign definitive19:35
tonybI think it is about consistency with other elasticserach site used by some team members19:35
tonybso the same data is available for opendev as is for rdoproject19:36
tonybbut yes I'll get more details19:36
clarkbI think the answer to reporting to a third party elasticsearch is no. Reporting to an elasticsearhc/opensearch we run is a maybe with the side note that in theory the data reported is far less of a deluge than the log data was and it might be easier to maintain19:36
tonybOkay.19:37
tonyband opensearch.logs.openstack.org would be considered 3rd party?19:37
clarkbyes, opendev doesn't run it19:37
tonybCool.  Just checking.19:38
clarkband to justify running something like that ourslves we'd need to understand what it enabels that existing zuul apis do not19:38
clarkbwhich goes back to use cases19:39
tonybMakes sense19:39
tonybI think that's all I had19:40
clarkbfor me as well19:41
clarkbI'll give it another minute before calling it a meeting19:41
* tonyb twiddles thumbs19:42
clarkband time!19:43
clarkb#endmeeting19:43
opendevmeetMeeting ended Tue May  7 19:43:39 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:43
opendevmeetMinutes:        https://meetings.opendev.org/meetings/infra/2024/infra.2024-05-07-19.00.html19:43
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/infra/2024/infra.2024-05-07-19.00.txt19:43
opendevmeetLog:            https://meetings.opendev.org/meetings/infra/2024/infra.2024-05-07-19.00.log.html19:43
clarkbThank you tonyb for joining me today :)19:43
clarkboh and corvus 19:43
clarkbI'm going to go eat lunch now19:43
tonybNice19:44
corvusyay!19:44
corvusi'm going to sleep!19:44
clarkbgood night!19:44
corvusgood lunch!19:44

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