Thursday, 2022-01-27

yoctozeptoclarkb, fungi, dansmith: I actually like the new behaviour, it helps weed out missed comments; I guess it all boils down to user preference; I am more in the gerrit upstream camp (based on their feedback) - be thorough with reviews09:13
dansmithyoctozepto: except if the person doesn't, either because they're a part-time contributor that doesn't know about the treadmill, or refuse to do the treadmill, or use gertty and don't see them, everyone else has the noise14:23
dansmithyesterday I looked at several patches where I was like "Jeez bob, we already saw that you wanted a variable name changed and decided not to, why bring it up again? oh wait, that's old.. not unresolved, just old."14:24
spotzI'll have to look at some older reviews, I mainly did newer stuff the last few days14:54
gmann#startmeeting tc15:00
opendevmeetMeeting started Thu Jan 27 15:00:13 2022 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'tc'15:00
gmann#topic Roll call15:00
gmanno/15:00
louroto/15:00
gmanntc-members meeting time15:00
dansmitho/15:00
Guest292O/15:00
jungleboyjo/15:00
*** Guest292 is now known as diablo_rojo_phone15:01
gmannnot present today: Radosław Piliszek (yoctozepto), Belmiro Moreira (belmoreira)15:01
ricolino/15:01
gmannlet's start15:01
gmann#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee15:01
gmann^^ today agenda15:01
gmann#topic Follow up on past action items15:02
gmannnothing from previous meeting15:02
gmann#topic Gate health check15:02
gmannany news on gate15:02
spotzoo/15:03
dansmithI have only had a few things through the gate this past week, but they all went quite smooth15:03
fungiactivity levels have been on the rise since we're aroubd feature freeze for some projects15:03
gmannyeah15:03
gmannstable/train cap with older tempest  is merged now. 15:04
diablo_rojo_phoneHopefully smooth continues to be the theme15:04
gmannI think centos8-stream issue still not resolved ?15:04
fungithe next few weeks will be our first real-world load test of zuul's persistent state and multi-scheduler capabilities15:04
fungiseeing how it handles the openstack rush15:04
fungiit's been doing well up to this point, but that was over the holiday lull15:05
fungiif something doesn't seem right, please don't hesitate to give folks a heads up in #opendev or #openstack-infra15:05
gmannseems passing but few retry failure #link https://zuul.openstack.org/builds?job_name=tempest+tempest-full-py3-centos-8-stream&job_name=tempest-integrated-compute-centos-8-stream&skip=015:06
fungialso we're on a new version of gerrit (3.4) since monday, so aside from already observed ui behavior and visual changes, there's the potential for uncovering regressions like the one we found with signed tags15:06
gmannI will monitor those15:06
gmannanything else on gate updates?15:08
jungleboyjSeems like it has been working ok for us.15:08
gmannok15:08
gmann#topic Z Release Cycle Name15:09
gmannnomination are closed for naming and election is started on 25th15:09
gmannI have started the poll and hope all tc-members received it, if not please let me know 15:09
gmann#link https://governance.openstack.org/tc/reference/release-naming.html#polls15:09
jungleboyj++15:09
gmannpoll will end on 1st feb or early if all TC members vote15:09
diablo_rojo_phoneReceived!15:10
spotzvoted!15:10
gmanntill now only 4 tc-members casted vote, 15:10
jungleboyjI will cast my vote in 23 hours after my Twitter poll closes.  :-)15:10
gmannjungleboyj: ack, what name people preferring in your poll?15:11
jungleboyjZenith right now.15:11
jungleboyjhttps://twitter.com/jungleboyj/status/148634491069344154115:11
gmanntc-members: please cast vote if not yet done. so that we can proceed for the next step of legal checks soon15:12
diablo_rojo_phoneI feel like that's a bad choice cause it implies we are at the top and going to head downward now?15:12
dansmithdiablo_rojo_phone: omicron and openstack have peaked15:12
dansmith:P15:12
diablo_rojo_phoneLol lol lol15:12
gmann:)15:13
jungleboyj*Sigh*  I hadn't thought of it that way.15:13
gmannI will vote this time and zombie is my fav :)15:13
diablo_rojo_phonejungleboyj: nor your Twitter voters lol :) 15:13
jungleboyjPeople are worried that that is going to bring the 'OpenStack is Dead' jokes.15:14
spotzI thought there were some good conversation on this channel a few days ago, like zombie15:14
jungleboyjdiablo_rojo_phone:  Right.15:14
jungleboyjI think of the old TVs that I used to love.15:14
gmannmore it bring, more it get clarity 15:14
diablo_rojo_phonePerhaps it's just dansmith and I, jungleboyj 15:14
diablo_rojo_phoneNever seen the show lol15:15
dansmithI'm not really worried, I think zombie has the same sort of "past its prime" connotation, even though I expect it to win15:15
diablo_rojo_phoneTechnically as a zombie it would make OpenStack 'living dead' or 'undead'15:15
dansmithnot worried about zenith I mean15:15
spotzYeah I doubt my cchoicce will win, even then legal..15:15
dansmithdiablo_rojo_phone: what zombies have you seen that don't smell like something past its prime in the fridge? :)15:16
gmanndiablo_rojo_phone: yeah15:16
jungleboyj*Sigh*15:16
gmannanything else on this topic?15:16
dansmithno :)15:17
spotzSure, constructive probably not:)15:17
gmann#topic Z cycle Technical Elections15:17
gmannIts time for the PTL and TC election15:17
gmannjungleboyj: and I had volunteer for election official along with existing one. if anyone would like to help please raise patch in election repo15:18
gmannI have also proposed the election dates #link https://review.opendev.org/c/openstack/election/+/82501715:18
spotzbelmeiro and I can't if re-running15:18
gmannPlease review and let me know your feedback. or if it looks ok then any election official can approve it15:18
gmannspotz: yeah15:18
diablo_rojo_phoneI can take a look today. 15:19
gmannspotz: diablo_rojo_phone can either of you add me in core list in gerrit group this is merged now https://review.opendev.org/c/openstack/election/+/82500915:19
gmanndiablo_rojo_phone: thanks 15:19
jungleboyjHave it open in a tab as well.15:20
gmannI think ianychoi[m], andymccr and hspease also around to help15:20
spotzI used to know where to do it:)15:20
gmannthis will be combined election again and for 5 TC seats 15:20
gmannspotz: https://review.opendev.org/admin/groups/208108b62745877449d8e6fce45f44e3cc013e8b,members15:21
spotzdone!15:21
gmannjungleboyj: if you can also raise patch for election official, we can start the process/meetings15:22
gmannspotz: thanks 15:22
gmannanything else on election?15:22
fungii'm always happy to answer process or tooling questions too, if the officials need to ask any15:22
jungleboyjgmann: Ok.  Will work on that.15:22
gmannthanks15:22
jungleboyjfungi:  Thanks!  I will try to not pester you too much.15:22
gmann#topic Adjutant need PTLs and maintainers15:23
gmannI think I was supposed to remove this from agenda. we will iterate it after election if no leader15:23
gmann#topic Open Reviews15:23
gmann#link https://review.opendev.org/q/projects:openstack/governance+is:open15:24
gmannthis need one more vote #link https://review.opendev.org/c/openstack/governance/+/82624315:24
gmannricolin: I replied on the project health tool patch 3link https://review.opendev.org/c/openstack/governance/+/810037/5..6/tools/project_health_check.py#b35115:25
gmann#link https://review.opendev.org/c/openstack/governance/+/810037/5..6/tools/project_health_check.py#b35115:25
ricolingmann, thanks will check15:25
gmannthanks15:25
gmannI think all other reviews are in good shape.  15:25
gmannI will check FIPs goal today15:26
ade_lee__gmann, thanks -- I think the fips goal is only missing reviews from you and ricolin 15:26
spotz7 votes on FIPs15:26
gmannade_lee__: ack. I opened it yesterday but missed it15:26
gmannI will do right after meeting15:27
ricolin+115:27
ade_lee__thanks - assuming this gets approved, what happens next?15:27
gmann#topic Renaming all `master` branches on all repos to `main`15:27
lourotHey o/ so at Canonical for example we have ~80 openstack repos (essentially charms). We could create a `main` branch ourselves, but we wouldn't have permissions to delete `master`. Also not sure how we would make `main` the default branch in Gitea. That's why we wanted to see if there were plans for a coordinated effort or something15:27
gmannade_lee__: you need to propose to goal selected in goal/selected folder and we will see the schedule based on current active goals or so15:28
gmannade_lee__: #link https://governance.openstack.org/tc/goals/#selecting-goals15:28
ade_lee__gmann, ok - thanks15:28
gmannlourot: if we do that, we need to do for all openstack repos15:29
gmannanyone remember what was discussed before when master/slave replacement happened in github15:29
fungilourot: the opendev sysadmins have been looking for projects interested in creating new repositories with a different default branch name so that we can make sure things are working as expected, renaming existing branches will be much more involved and premature if there's no confirmation that things actually work with a different default branch name to begin with15:30
dansmithis it already decided that we're making the switch?15:30
gmannI do not think so15:30
dansmithokay good :)15:31
fungii don't recall anyone deciding anything in that regard, no15:31
jungleboyjI don't remember discussing this.15:31
fungifrom opendev's perspective, we want to make sure the collaboratory is able to support projects who want different default branch names, and confirm our tooling supports that correctly15:31
spotzBesides what fungi mentiioned I think we've also been waiting for the git community to make their final decision15:31
gmannyeah, it is lot of work and lot of configuration/scripts/tooling updates not just repo rename15:31
dansmithyeah, allowing new projects to start with main if they want is fine15:31
dansmithmaking sure that's possible I mean15:32
fungispotz: well, opendev has been waiting for the git community to make a decision (or not) in order to inform any potential change in opendev's default for new repositories, that doesn't mean that it's necessarily the deciding factor for openstack's repositories15:32
spotzWe know changing OpenStack and all the projeccts would be an undertaking. So we need to be sure it will work in our systems and those we rely on before we can make a decision15:32
spotzAs much as I'd like us to change, the ops in me doesn't want us to break:)15:33
dansmithor we could decide not to even if it's possible, and then only worry about if new stuff will work with a different branch15:33
dansmithnot to change existing projects I mean15:33
lourotdo you know what would happen today if I created project-config/governance reviews for importing a new project from GitHub where the default and unique branch would be `main`. Would the import fail? 15:33
gmanneven before trying in new repo I think we still need updates and to know what all it can break like using master for all and main for new repo in automative scripts/tooling15:33
fungionly changing some repos in openstack could be challenging, particularly for integration testing where jobs assume branch names will match between different repositories15:34
gmannyeah15:34
fungilourot: that's what we want to test15:34
fungi(in opendev i mean)15:34
gmannis it final in git community that no once can use master ?15:34
gmann*no one15:35
fungilourot: currently the answer as to what will happen on import is unknown15:35
gmannand in integration testing/tooling too, it s unknown15:35
fungigmann: no, the git community has only so far made an effort to make sure that people can use any default branch name they want15:35
gmannknowing what all break and need change itself need more time to audit/try15:35
gmannfungi: ok15:35
fungithe most recent word i found on their mailing list was over a year ago indicating they had not themselves decided to change the built-in default for the default branch name15:36
fungi#link https://lore.kernel.org/git/xmqqv9d1yzta.fsf@gitster.c.googlers.com/15:36
lourotI think the default in GitHub now being `main`, the moment when someone will try to get that imported to Gitea/Gerrit will come sooner or later naturally15:36
fungilourot: github is a proprietary and predatory leech on open source, i wouldn't want to follow their lead just because15:37
fungibut i would like to test what an import does in that case, yes15:37
lourotit's not my point, just saying that someone will try soon to get a repo with `main` imported15:37
lourotbecause it's the default there15:38
lourotat least it's our workflow: we create a temp repo on github and we create then project-config/governance reviews to get that imported15:38
fungiwe have a configuration option where projects can indicate the default branch name they want, and have done some rudimentary testing, but nothing heavy with typical ci jobs et cetera15:38
gmannlourot: can please you try that and we can know what are things we need to change or need effort ?15:38
gmannand then we test the integration testing thing15:39
lourotgmann, yes, would you be OK if I do that with a dummy repo? I wouldn't want to slow down things on a project we'd need fast15:39
fungiyes, do keep in mind that renaming back from main to master if it doesn't work out for logistics/integration testing reasons could be even harder, so definitely don't try it with something you need working soon15:40
gmannlourot: I am ok for testing dummy15:40
fungithough odds are we could do it with a manual push --force from one of the gerrit sysadmins15:40
gmannfungi: I do not think we should try to move until we are very much sure15:40
lourotperfect, this looks like an action point for me then :)15:40
fungiright, i meant for whatever repo you were testing with15:41
gmannand more than that I am concerned about the effort it need vs how strongly we want/need to change it15:41
fungilourot: let's sync up in #opendev when you're ready and we'll work through it15:41
fungii'm happy to help15:41
lourotfungi, thanks!15:41
gmannopendevmeet: fungi thanks 15:42
opendevmeetgmann: Error: "fungi" is not a valid command.15:42
* fungi is so a valid command!15:42
gmannopendevmeet: fungi:  thanks 15:42
opendevmeetgmann: Error: "fungi:" is not a valid command.15:42
jungleboyjhe he.15:42
gmannlourot: fungi:  thanks 15:42
gmann:)15:42
lourotfungi is not a valid command!15:42
fungihah15:42
gmannand after that we will re-discuss on this15:42
gmannlourot: you want to keep it in agenda or add it back once we are ready with import experiment ?15:43
* spotz puts in a patch for a fungi command:)15:43
dansmithspotz: good luck, I expect that'll be a lot of code15:43
lourotgmann, I'll put things back on the agenda when we got some results with the experiment, thanks!15:44
spotzhehe15:44
jungleboyjdansmith:  Hmmm, I think you are going to need a Lenovo Supercomputer to run that AI.  15:44
gmannlourot: sure, thanks for brining it here.15:44
* jungleboyj goes to the configurator15:44
gmannlast thing 15:44
gmanndansmith: is ready with the ffu testing in grenade15:44
gmann#link https://review.opendev.org/c/openstack/grenade/+/82610115:45
dansmithyeah, although we need to stop calling it ffu I think.. I've been using that term, but it means something else15:45
gmann+115:45
dansmiththis is really guaranteeing that people can skip specific releases, so I think skip-level is a better term15:45
gmannyeah skip-level much better15:45
dansmithso yeah, I'd like to have a meeting with anyone interested in moving us forward with this tick-tock release model to address the cycle length concerns without slowing us down15:45
gmannyeah, this is good input for upgrade question we had in that discussion15:46
dansmithget a proposal together so we can try to get it in place with kinda smoke testing now (like this) and then hopefully make the AArdvark release where we start15:46
fungiright, in the old discussions where we were debating potential models, we did use "skip-level upgrades" to refer to this sort of solution (an alternative to the fast-forward upgrading model we settled on at the time)15:47
dansmithyeah, and we've always been anti-skip-level for good reason,15:47
dansmithand definitely skipping any random versions is not what we're talking about here,15:47
dansmithjust a specific "you can skip odd-lettered releases" (yeah I said it)15:48
gmannand for 'release cadence'  meeting will be video call (a separate call from TC meeting), what is best time for all interested in that topic to meet?15:48
dansmith++15:49
gmannremember our next TC meeting is on 3rd video call 15:49
gmannmay be right after that for an hr?15:49
dansmithsure wfm15:49
dansmithis nobody else interested in this?15:49
spotzI can definitelly leave the room open if y'all want it15:50
jungleboyj++15:50
gmannspotz: we can restart as separate meeting itself15:50
dansmithI think at least belmiro was, and he's not here15:50
spotzMaybe get reps of from the projects who aren't doing the normal release cadence?15:50
gmannor continue as we might finish TC meeting soon as per agenda 15:50
dansmithwell, I'm not sure this would really apply to them15:51
spotzOh I meant the video room next week15:51
dansmiththat's something we need to discuss I guess15:51
spotzdansmith: ok15:51
spotzJust trying to think of who might be interested15:52
gmannlet me propose the time on  ML for 3rd feb at 16UTC (right after TC meeting) 15:53
dansmithwe'll need to get buy-in from projects anyway,15:53
dansmithwe more need to make sure this is something the TC is going to push forward and what the plan is exactly, and then we can start asking projects to agree Ithink15:53
gmannyeah, hope we can conclude it as TC stand on it15:54
gmannand one more thing before we close.15:55
gmannwe will check yoga tracer progress in next meeting on 3rd Feb, please check your assigned item #link https://etherpad.opendev.org/p/tc-yoga-tracker15:55
gmannthat is all from me today, anything else to discuss ?15:55
spotzNot from me15:56
jungleboyjNot from me.15:56
gmannlet's close the meeting. thanks all for joining 15:56
gmann#endmeeting15:56
opendevmeetMeeting ended Thu Jan 27 15:56:45 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-27-15.00.html15:56
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-27-15.00.txt15:56
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-27-15.00.log.html15:56
diablo_rojo_phoneJust a heads up 15:56
spotzThanks gmann and everyone!15:56
diablo_rojo_phonethat the PTG signup for teams will go out next week15:56
gmanndiablo_rojo_phone: oh, please go ahead15:56
jungleboyjCool.15:57
gmanndiablo_rojo_phone: thanks and ack. 15:57
gmann will start TC PTG preparation15:58
jungleboyj++15:58
diablo_rojo_phoneOnce we get the list of teams set I will generate the etherpads 16:00
diablo_rojo_phoneso if we coordinate via email thread and poll that might be good enough for now?16:00
gmanndiablo_rojo_phone: ack. sounds good16:00
clarkbfungi: lourot: One point of clarification is that we added support for non master HEAD to jeepyb and our gitea management and the zuul config allows you to set it as well. This means we expect it to work but no one has done it in our system out side of testing16:15
clarkbfungi: lourot: you have to explicitly tell the import process that HEAD is not master too16:16
clarkbif will not infer this from the import process because git doesn't transfer that data on push16:16
fungiyep, i thought i covered all that but it's good to clarify16:17
clarkbya it was mentioned but I wanted to hammer that point home so it doesn't get missed and accidnetally imported as normal :)16:20
clarkbthen we'd have to start over :)16:20
fungiright16:28
opendevreviewMerged openstack/election master: Add CIVS opt in information in kickoff voting emails  https://review.opendev.org/c/openstack/election/+/80727116:40
opendevreviewMerged openstack/election master: remove unicode from code  https://review.opendev.org/c/openstack/election/+/76965316:42
lourotclarkb, ack, thanks!16:54
diablo_rojo_phoneSomething else I should have mentioned during the TC meeting- there is a newsletter going out next week. so if any wants to suggest things I need them here( https://etherpad.opendev.org/p/newsletter-openstack-news) by EOD Monday19:43
ade_lee__gmann, looks like somethings going on with the linters on https://zuul.opendev.org/t/openstack/build/0317357503424a68a141470cf77081b421:53
ade_lee__gmann, something about "Unknown repository skyline/skyline-apiserver as part of skyline-apiserver in skyline21:53
ade_lee__Unknown repository skyline/skyline-console as part of skyline-console in skyline"21:53
fungithat's almost certainly fallout from the skyline project rename into openstack21:55
fungii thought there was a corresponding change to update them in governance already21:56
fungiade_lee__: yep, either rebase on https://review.opendev.org/826243 or wait for it to merge21:56
fungiapparently it's stuck waiting for the skyline ptl to approve it. is that person aware?21:57
fungialso seems like a bit of unwarranted bureaucracy. that change is simply a reflection of the current state of the repositories, nothing that really demands acknowledgement21:58
gmannade_lee__: yeah, we need to wait fir this to merge https://review.opendev.org/c/openstack/governance/+/82624323:40
gmanntc-members: who ever 4 members have not voted on Z release name, please do. 5 members voted and 4 are not yet 23:46
dansmithnot me23:46
dansmithI mean, I have voted, it's not me in the "who ever 4" :)23:46
gmannack :)23:46
gmannI think mnaser or Belmiro might not seen the poll yet23:47
gmannand I think jungleboyj will vote soon after twitter poll23:47
gmanndiablo_rojo_phone: ricolin yoctozepto in case you have not voted ^^23:49

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