Tuesday, 2020-04-14

*** openstack has joined #opendev-meeting09:53
*** ChanServ sets mode: +o openstack09:53
*** tobiash has quit IRC18:16
*** tobiash has joined #opendev-meeting18:17
clarkbanyone else here for our weekly meeting?19:00
clarkbwe'll get started shortly19:00
mordredo/19:00
fungialoha y'all19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Apr 14 19:01:20 2020 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
clarkb#link http://lists.opendev.org/pipermail/service-discuss/2020-April/000002.html Our Agenda19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbJust a reminder that we are meeting here today and not in #openstack-meeting19:01
* clarkb goes over to the other channel to post that reminder19:02
clarkb#topic Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
fungido we have a change up to fix http://eavesdrop.openstack.org/#Project_Infrastructure_Team_Meeting yet?19:02
fungiit still lists the old location19:03
clarkbfungi: oh not yes though that was on my list19:03
clarkbI got distracted by container and zuul things19:03
fungii'll push one up while i'm thinking about it19:03
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-04-07-19.01.txt minutes from last meeting19:03
clarkbthere were no actions from last meeting19:04
clarkbThere are also no specs to discuss so we can dive straight into the things that had me distracted :)19:04
clarkb#topic Priority Efforts19:04
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:04
clarkb#topic Update Config Management19:04
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:04
clarkbwhy don't we start with gerrit?19:04
clarkbWe are now running gerrit from a docker image19:05
mordredBOOM19:05
clarkbthere were additional corner cases that we had to handle to make that happen19:05
mordredyeah - but it seems to mostly be working now19:05
clarkbmordred: maybe you want to summarize the relevant bits to help ensure we've written down the current status?19:05
mordreduhm19:05
mordredwe were missing a few bindmounts for the gerrit hook scripts19:05
mordredthere were also some places where jeepyb was hardcoding paths that are now different inside the container19:06
mordredso we fixed both of those19:06
mordredclarkb has a patch up to have docker-compose gracefully shutdown gerrit19:06
clarkb#link https://review.opendev.org/71905119:06
clarkbthat change requires us to use a newer version of docker-compose than is on ubuntu-xenial so we switch to installing it from pypi across the board19:07
clarkband I've tried to do extra validation of that in https://review.opendev.org/719682 to ensure the differences we've found don't create problems for us19:07
clarkband the testing seems to show docker-compose handles it just fine19:07
clarkbbut others should review that and check it for themselves :)19:08
clarkbmordred: we also still need to udpate gerritbot right?19:09
mordredyeah - gerritbot is oneof the next thigns on my list19:09
clarkbis that the last major outstanding item for gerrit?19:09
mordredI'm going to do it after projet-config19:09
mordredsince - you konw - it's driven by project-config :)19:09
mordredthat said - step one is here: https://review.opendev.org/#/c/715635/19:09
clarkbthat is probably a good lead into the zuul cd efforts?19:10
mordredsure!19:10
mordredso - we're now running all ansible from zuul and not from cron!19:11
mordredas a followup, there is a stack, ending at https://review.opendev.org/#/c/720029 - which is working on getting that to use the zuul checkout of system-config and project-config instead of independently cloned copies of those19:11
mordreddoing that will let us land stacks of changes and have each one run in prod with the actual state of the change19:11
clarkb#link https://review.opendev.org/#/c/720029 use Zuul provided system-config and project-config when Zuul runs our playbooks19:12
clarkbits on my list to rereview that all after the meeting19:12
clarkbI guess the big thing to be aware of here is that zuul is running the jobs and we may still need to tune when certain jobs run?19:13
clarkbthough I think we've fixed the majority of those problems19:13
mordredyeah - but it's definitely a thing to keep watching19:14
mordredalso - we should look at logs in /var/log/ansible, verify that various service logs are clean and set the flag in zuul.yaml to collect and publish the log files19:15
clarkboh and if you need logs the vast majority at at bridge:/var/log/ansible19:15
clarkband ya as we verify they are safe to publish we can flip that flag and have zuul collect the logs19:15
clarkbany questions on this? or anythign else to bring up?19:16
mordredthings run real quick now19:16
clarkbmordred: fungi should we talk about etherpad upgrades now or later (I have it later in the agenda but its somewhat relevant to the topic)19:18
*** diablo_rojo has joined #opendev-meeting19:18
mordredwe can do that now too19:18
mordred(agree, it seems of a piece)19:18
mordredwe are now running etherpad from docker too!19:18
clarkband in the process upgraded it to 1.8.0 release19:19
clarkbare we still on 1.8.0 now that we build our own images?19:19
mordredyup19:20
mordredour Dockerfile points to :1.8.0 - when they release 1.8.3 we can update that19:20
fungiyeah, "soon"19:21
fungialso something between what we were deploying on the old server and 1.8.0 seems to have fixed the line number misalignment bug19:21
clarkboh and we are hosting the db for etherpad on the server itself (no more trove db)19:22
fungioh, for 1.8.(1? 3?) we need to watch out for breaking plugins19:22
clarkbmordred: related to ^ the db thing did we confirm that backups are running properly now?19:22
fungithere's apparently a non-backward-compatible change coming which impacts the plugin interface19:22
mordredclarkb: yeah - they seem to be running well now19:22
mordredhowever ...19:22
mordredhttps://review.opendev.org/#/c/719192/ <-- we should land that for gerrit backups (they're working because we used to write that file out)19:23
mordredalso - stack ending here: https://review.opendev.org/#/c/719484/ has a few more backup updtes19:23
clarkboh good call (we haven't needed that in the other container/ansible things beacuse they use local dbs)19:24
mordredyeah19:24
clarkbwe should do similar with gitea0X fwiw19:24
mordredso - fwiw - I have confirmed that we're doing the mysqldump, and that we are backing up with bup19:24
clarkbI don't think we need to back them all up but should back up one of them19:24
mordredI have not confirmed that the db backup is making it in to bup19:24
mordredclarkb: it's in that stack19:24
mordred https://review.opendev.org/#/c/719484/19:25
clarkboh perfect19:25
clarkbI have lots of things to review this afternoon :)19:25
mordred(there's actually a bunch of things in system-config with 1 +2 from several days ago that could use a pass to pick up)19:25
fungishould we be looking to move the gerrit db into a local container anyway?19:25
clarkbfungi: gerrit uses a lot of memory and I expect its db does too19:26
clarkbit might be an exception to general cohabitation for our services19:26
clarkbbut I think we should consider not using trove as part of its upgrades19:27
mordredyeah. I think eventually having a dedicated galera cluster for gerrit might be nice19:27
fungiahh, yeah, maybe we'd deploy it in a container on a separate server in that case19:27
fungior serverS19:27
mordredoh - wait - duh19:27
mordredNEVERMIND19:27
mordredas part of gerrit ugprades we're getting rid of mysql19:27
clarkbmordred: not entirely19:27
mordredso - it stops being an issue19:27
clarkbbut I bet the db does use far less memroy in the new setup19:27
fungier, well, it's not so heavily used at least19:27
mordredmostly - I don't really care about the one remaining table19:27
mordredyeah19:27
fungiso maybe would fit on the same server19:27
mordredwe can switch to local for that19:27
clarkbgot it19:27
fungimakes sense19:27
mordredwe could probably just use h2 even19:28
fungii agree19:28
clarkbalright anything else on config management, docker, gerrit, backups?19:28
mordredonce the project-config stack and then gerritbot are done I'll start working on gerrit upgrade planning19:28
clarkbmordred: !19:29
clarkbmordred: I wonder if we can manipulate my ideas for testing of upgrades to do some of the work there19:29
mordred(general idea is probably going to be an upgrade event to get to 2.16, then pause there for a while letting it do online migration to notedb - then upgrade to 3.1)19:29
clarkbI think I'll have time tomorrow to really dig into that. We'll see :)19:29
mordredbut we'll do testing of that first and find out19:30
fungi2.16 has the new review screen and polygerrit both available, right?19:30
clarkbfungi: yes19:30
mordredyes19:30
mordred3.0 removes non-polygerrit19:30
fungithat does make it a good resting place briefly, for folks to get used to the newest interface design19:31
mordredme is hoping that subchecks are ready before we're ready to do the 2.16->3.1 bump19:31
fungithough i assume the polygerrit interface in 3.1 is way nicer than in 2.1619:31
mordredso much nicer19:31
mordredcurrent polygerrit is pretty awesome19:31
fungiso 2.16 may provide a poor impression of polygerrit19:31
fungiwe'll probably want to couch that announcement carefully with that in mind19:32
mordredmaybe - the biggest issue is going to be the ci summary table19:32
mordredfor the period between when we're on 2.16 and the time that subchecks is fully ready19:32
mordredbut we'll have to see how long it takes for us to be ready to upgrade in the first place - and then see where subchecks are19:33
fungieven after subchecks is fully ready, there's likely to be a ton of third-party ci systems who are not on a checks-api-capable platform19:33
mordredfungi: good reason for them to upgrade :)19:33
fungii concur19:33
mordredbut yeah - there's a pile of stuff to make a plan for19:33
fungibut we'll need to take the opportunity to make sure folks know that's coming19:33
clarkbseems like we may end up udpating our js too if that isn't too bad and we are expecting to be on 2.16 for a while19:34
fungii have a feeling "nobody sees your ci results" is going to be a major fulcrum to get 3pci operators to upgrade/rebuild19:34
clarkbtesting should help sort all of that out19:34
mordred++19:34
mordredfirst step is the biggy - getting to 2.16 and notedb is the big challenge19:35
mordredonce we're there - the subsequent steps are all much more managable19:35
clarkbok lets move on have a few more things to talk about19:35
clarkb#topic OpenDev19:36
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:36
clarkb#link http://lists.opendev.org/pipermail/service-discuss/2020-April/000001.html Email thread on next plans for governance19:36
clarkbI sent that email out. TLDR is I've opened nomination for those that want to do PTL duties until end of April. Which gives us plenty of time (I think) to account for pandemic and such19:37
mordred++19:37
clarkbAlso I was goign to kick start briging up the advisory board discussions with people that can facilitate that in their constituent communities19:37
clarkbI haven't done that yet, containers and zuul things were distracting, but its high on my list to get to19:37
clarkbif you are interested in the advisory board please reach out as well19:38
fungis/ptl/project coordinator/19:38
clarkbfungi: right19:38
fungier, "service coordinator"19:38
fungimy bad19:38
fungiwe'll get all this terminology figured out someday19:38
clarkbfungi: its difficult when you have to go from one set of terms to another :)19:38
clarkbfungi: on the authentication spec/summary/planning is there anything new to add?19:39
fungino, not yet19:39
fungioh, well, a little19:40
fungicorvus found some of mordred's prior draft plan from years ago, so i'll be using that as a sort of checklist to make sure i cover the use cases he identified19:40
clarkb#topic General Topics19:42
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:42
clarkbThe only item here is server upgrades and in particular the wiki19:42
clarkbfungi: anything new to add re the wiki19:42
fungizilch19:42
clarkbI also noticed that my refstack changes that were pushed to make it possible to build docker images for refstack seem to have landed19:43
clarkbthe board meeting today prompted me to take a look19:43
clarkbso I may pick that back up again if time permits19:43
clarkbI think the board wants to make that toolchain less openstack specific so maybe it is something that can fit in opendev but probably to start it will be a good test case for oepnstack-infra specific things19:44
clarkbwe'll see19:44
clarkb#topic Open Discussion19:45
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:45
clarkbAnything else?19:45
fungiyeah, i'm struggling to see how to make refstack non-openstack-centric19:45
clarkbfungi: what I took away from it was that the interop wg could use tools built for openstack to do validation and verification of other tools in a similar wy19:46
clarkbreally I doubt that will get much traction, but time will tell19:46
fungioh, i've pushed up the change i mentioned earlier to update our meeting info, and another to make the irc meetings index page less openstacky:19:46
ianwi'd appreciate it people could look over19:46
fungi#link https://review.opendev.org/720060 Update OpenDev meeting location and name19:46
ianw#link https://review.opendev.org/#/q/topic:ensure-pip+status:open19:46
fungi#link https://review.opendev.org/720063 Not all meetings are OpenStack19:47
ianwto get support for pip-and-virtualenv-less images in zuul-jobs19:47
clarkbianw: added to my list19:47
clarkbI've got kid school things at 2:30 but my rough plan is to review between now and then (and probably continue to reivew if they can do school things without too much help)19:47
clarkbbecause there are a lot of changes out there :)19:48
ianwalso, i'm not sure what people's thoughts on suse are, wrt to19:48
ianw#link https://review.opendev.org/71829919:48
ianwi would like to start building it without pip/virtualenv (like fedora is now) and push on that prior stack to get it back into shape19:48
clarkbianw: that makes sense given how things have changed upstream19:49
fungioh, for last week's maintenance we used this channel, and did an ad hoc meetbot meeting under the opendev-maint name19:49
mordred++19:49
fungiwhich might be a pattern we want to keep in mind for future scheduled maintenance activities19:50
clarkbmordred: not to add to your stack but I was thinkign we might want to consider a zuul.d for system-config19:50
clarkbmordred: then we can put docker image jobs in a file and prod jobs in a file and pre merge or shwatever19:50
fungi#link http://eavesdrop.openstack.org/meetings/opendev_maint/ maintenance meeting(s019:51
mordredclarkb: I had the same thought19:51
clarkbI'll call the meeting here. Thanks everyone!19:53
clarkbwe get a few minutes back to eat breakfast/lunch/dinner or do more reviews :)19:53
clarkb#endmeeting19:53
*** openstack changes topic to "Incident management and meetings for the OpenDev sysadmins; normal discussions are in #opendev"19:53
openstackMeeting ended Tue Apr 14 19:53:29 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-04-14-19.01.html19:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-04-14-19.01.txt19:53
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-04-14-19.01.log.html19:53
fungithanks clarkb!19:54
*** tobiash has quit IRC21:18
*** tobiash has joined #opendev-meeting21:20
*** diablo_rojo has quit IRC21:26

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!