Thursday, 2022-10-27

opendevreviewGhanshyam proposed openstack/governance master: Adding TC chair election process  https://review.opendev.org/c/openstack/governance/+/86277203:46
opendevreviewGhanshyam proposed openstack/governance master: Adding TC chair election process  https://review.opendev.org/c/openstack/governance/+/86277203:47
*** dasm|rover is now known as dasm|off03:50
opendevreviewGhanshyam proposed openstack/governance master: Adding TC chair election process  https://review.opendev.org/c/openstack/governance/+/86277204:03
opendevreviewGhanshyam proposed openstack/governance master: Adding TC chair election process: nomination in TC meeting  https://review.opendev.org/c/openstack/governance/+/86277404:07
opendevreviewGhanshyam proposed openstack/governance master: Adding TC chair election process: nomination in governance repo  https://review.opendev.org/c/openstack/governance/+/86277204:07
gmanntc-members: ^^ added both options for TC chair election we discussed in PTG, you can vote on those and based on the agreement with majority positive vote, we will merge one and abandon other. We will discuss the same in tomorrow meeting also. 04:10
*** diablo_rojo is now known as Guest414206:49
*** dasm|off is now known as dasm|rover13:10
*** knikolla[m] is now known as knikolla14:38
gmann#startmeeting tc15:00
opendevmeetMeeting started Thu Oct 27 15:00:04 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
noonedeadpunko/15:00
gmanntc-members: meeting time15:00
gmanno/15:00
slaweqo/15:00
JayFo/15:00
knikollao/15:00
dansmitho/15:00
gmannfrom absence section: arne_wiebalck will miss the meeting on Oct 27 (PTO)15:02
rosmaitao/15:02
gmann#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee15:02
gmann^^ today agenda. let's start15:02
gmann#topic Follow up on past action items15:02
gmannnone from previous meeting15:02
gmann#topic Gate health check15:03
gmannany news on gate 15:03
gmannI have not observed any frequent failure. 15:03
slaweqnothing from me15:04
gmannok15:04
rosmaitathis is not quite related, but any word about the ceph job failures on Jammy?15:04
gmannI did not follow up on that discussion, noonedeadpunk did you get chance to talk to ceph plugin team in qa team?15:05
gmanngouthamr ^^15:05
dansmithno big failures on my radar either15:07
gmannI think gouthamr had some discussion last week, anyways will check with them laster15:07
gmannk15:07
noonedeadpunkup, no, I have not I guess15:07
noonedeadpunkIn osa we have just overriden couple of variables for ceph-ansible15:08
noonedeadpunkEventually, infra mirrors regarding EPEL are broken now15:08
noonedeadpunkSo projects relying on centos/rocky jobs are likely affected15:09
noonedeadpunkAt very least kolla and osa are affected15:09
noonedeadpunkI'm trying to reach fedora ppl who are mentioned as point of contact15:10
gmannok15:10
noonedeadpunkIf not - patch proposed to switch mirror15:10
gmannnoonedeadpunk: will be good to send it on ML also if any other projects affected in case they are running centos in gate15:11
noonedeadpunk+115:11
noonedeadpunkwill do15:12
gmannthanks 15:12
gmannnext is Bare 'recheck' state15:12
gmann#link https://etherpad.opendev.org/p/recheck-weekly-summary15:12
gmannslaweq: please go ahead15:12
slaweqall is good there15:12
slaweqI will contact few teams this or next week but overall it's good15:13
slaweqnothing more to say really15:13
gmanncool15:13
gmannnext is Zuul config error15:13
JayFIs the bare recheck still enough of an ongoing issue to be worth a dedicated TC agenda item at this point?15:14
gmann#link https://etherpad.opendev.org/p/zuul-config-error-openstack15:14
gmannJayF: we would like to spread the message and monitor to help gate health 15:14
gmannslaweq doing good job keeping stats for every week and reaching out to project team15:14
dansmithyeah, I think these recurring items have been successful in keeping tabs on stuff like this15:15
gmannI think keep checking the stats and status in our weekly report does not take much time15:15
gmannyeah15:15
JayFFair enough; if I'm the minority opinion that's that :)15:15
dansmithused to be more issues with the gate, but lately it's mostly "everything is cool" .. but if we stop monitoring, it slips easily15:15
gmannagree15:15
slaweq+115:15
slaweqlets just keep an eye on it15:16
slaweqand hopefully all will still be like "all is good" :)15:16
knikollawe could perhaps move it to the end of the meeting though? 15:17
gmanndoing it under Gate health as it is related15:17
gmannor you mean to move gate health at the end of meeting?15:17
dansmithI think they mean move recurring things to the end15:17
knikollacorrect dansmith 15:18
fungioh, per the opendev meeting this week, we are losing the iweb cloud at the end of the year. it currently accounts for ~20-25% of our total quota for job resources15:18
slaweqthat's bad15:18
dansmithtbh, I think the recurring stuff is some of the more useful things we've done lately, and since we can get caught up in other discussions and run out of time, I'd prefer to keep it up front15:18
fungi(we were originally losing it at the beginning of this year, but they generously pulled a lot of strings to keep it running for us)15:18
dansmithwe can try to hit it quicker and move on though, but.. fungi's thing just now is a good example of it being important :)15:19
gmannknikolla: dansmith: that is reason I keep them at start so that we finish them quickly and spend more time on other things15:19
dansmith++15:19
fungisince we don't seem to spend a lot of time at max capacity these days, openstack probably won't feel that capacity reduction too badly, but it's worth keeping in the back of your mind15:20
fungialso, as always, we're in talks with other openstack providers about possibly becoming resource donors15:20
gmannfungi: seems like 20-25% of quota can impact the testing right?15:20
dansmithfungi: iweb is internap/15:20
fungigmann: it may mean waiting longer for test results when there's a lot of concurrent activity, yes15:20
gmannyeah15:20
slaweqso it's second provider which we are loosing this year, do I remember correctly?15:21
knikollaI agree that it is useful, it's just a huge chunk of not-usually actionable back and forth. When there is a pressing issue that needs to be presented, we can add it to the front and discuss it. 15:21
fungibut as i said, we don't run maxxed out nearly as much as we used to, so it may go unnoticed much of the time15:21
JayFknikolla: that's essentially why I asked if we should keep doing it; because it's been non-actionable the last several times15:21
fungislaweq: it's the same one, they just extended the time we could keep using it15:21
fungiby a lot15:21
slaweqahh, ok, then it's not that bad :)15:21
slaweqthx fungi15:21
knikollaI feel the flow of the meeting should be sorted by importance. 15:21
knikollaand actionability (or necessity for a discussion). 15:22
gmannfungi: ok, let's keep eyes on it and thanks for update on checking with another provider 15:22
dansmithknikolla: IMHO, keeping the developer resources healthy is one of the more important things we discuss.. even when they're non-actionable immediately, because sometimes it's a "we need to thin jobs" or "we need to drive some different behavior"15:22
dansmithlonger-term actions, not immediate "take action in this meeting" but... it's important to me15:23
gmannGate health checks are important activity TC is doing even at least monitoring and keep eyes on it15:23
gmannI can move recheck and zuul config errors at the end but let's keep gate health at the start15:24
knikollafair point dansmith. 15:24
gmannknikolla: JayF ^^ ok for you?15:24
knikollaworks for me. 15:24
JayFThe status quo is OK for me too; I asked a question and didn't expect to spawn this much discussion. That seems like a sane middle ground though.15:25
gmannok, let's move to zuul config error15:25
gmannknikolla anything from your side to bring on zuul error?15:25
knikollanothing new from what i reported last week at the PTG. 15:26
gmannok15:26
gmann#topic 2023.1 cycle PTG15:26
gmannfirst is Discussion summary sent on ML:15:26
gmann#link https://lists.openstack.org/pipermail/openstack-discuss/2022-October/030954.html15:26
gmann#link https://lists.openstack.org/pipermail/openstack-discuss/2022-October/030953.html15:26
gmannI sent the summary of PTG discussion over email15:27
gmann2023.1 TC tracker15:27
gmann#link https://etherpad.opendev.org/p/tc-2023.1-tracker15:27
gmann^^ as discussed in PTG, this is our tracker for this cycle, feel free to add the working item you are or would like to work in this cycle15:27
gmannand there are few items need assignee, please write your name in etherpad if you would like to help15:28
gmannthat is all on post PTG things. and from next meeting we can discuss more in tracker side if needed15:29
gmann#topic TC questions for the 2023 user survey15:29
gmann#link https://etherpad.opendev.org/p/tc-2023-user-survey-questions15:29
gmannI added the questions we want to remove/add in this etherpad15:29
gmannhope everyone got chance to review it15:29
gmannIf not please do, I will send these to aprice after the meeting15:30
gmannI will update here if we hit the limit on number of question by a group15:31
noonedeadpunkbtw I'm not sure about how correct is question `How users are consuming OpenStack`15:31
noonedeadpunkBecause it's not users, but operators I guess?15:31
noonedeadpunkor how are you consuming openstack?15:31
gmannsounds good even for next question also?15:32
noonedeadpunkThough I can imagine oeprators not always know how their deployment tool does install 15:32
noonedeadpunkWell, next depends15:32
noonedeadpunkAs I think that next is indeed about users15:32
gmannsure, done15:33
gmannif any more updates, feel free to edit in etherpad15:33
noonedeadpunkyeah, was not just sure how to phrase better at first :D15:34
gmann+1, thanks15:34
gmann#topic TC chair election process15:35
gmannseems we did not have conclusion in PTG so I proposed both the option we discussed in PTG15:35
gmann#link https://review.opendev.org/c/openstack/governance/+/86277215:35
gmann#link https://review.opendev.org/c/openstack/governance/+/86277415:35
gmannplease vote on those and at the end we will merge one with majority positive votes15:36
gmannor even feel free to add comments/improvement if needed in current proposal15:36
gmannany discussion needed on this or we just review in gerrit? 15:37
slaweqI will review in gerrit but tomorrow morning15:37
knikollai haven't had a chance to look at them yet. Discussion on Gerrit sounds good to me.15:38
gmanncool15:38
gmannmoving next15:38
gmann#topic TC weekly meeting time15:38
gmann#link https://framadate.org/xR6HoeDpdXXfiueb15:38
gmannas discussed in PTG, I started the poll to select the new time for our weekly meeting15:38
gmannseems arne_wiebalck and spotz not yet voted and both are not here15:39
gmannI will ping them and if they can vote before our next week and we can do next meeting on new time15:39
gmannanything else to discuss for this? 15:40
gmann#topic Open Reviews15:41
gmann#link https://review.opendev.org/q/projects:openstack/governance+is:open15:41
gmanncurrent open reviews ^^ 15:41
gmann2021 user survey is ready to vote #link https://review.opendev.org/c/openstack/governance/+/83688815:42
gmannupgrade testing things I need to update as per discussion happened in PTG15:42
gmannI am updating few things in CHAIR.rst so this is also good to vote - #link https://review.opendev.org/c/openstack/governance/+/86263715:43
gmannand rest other we already discussed in meeting15:43
gmannthat is all from today meeting agenda, we have ~15 min left if anyone would like to discuss anything else? 15:44
clarkbFallout from the jammy default base node switch seems to be minimal  (as expected openstack is pretty good about being specific about needed nodes)15:45
gmannyeah15:45
clarkbZuul will drop ansible 5 support in opendev this weekend when our automated upgrade process runs15:46
clarkbwe've been default to ansible 6 for a bit now and I don't think we had ansible 5 long enough for anyone to override to it, but heads up anyway15:46
gmannack thanks for updates15:47
gmannok, if nothing else..15:48
gmannour next week meeting will be on Nov 3 and video call15:48
gmannlet's close today meeting. thanks everyone for joining15:49
gmann#endmeeting15:49
opendevmeetMeeting ended Thu Oct 27 15:49:06 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:49
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2022/tc.2022-10-27-15.00.html15:49
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2022/tc.2022-10-27-15.00.txt15:49
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2022/tc.2022-10-27-15.00.log.html15:49
slaweqo/15:50
opendevreviewGhanshyam proposed openstack/governance master: Update CHAIR.rst for few updates  https://review.opendev.org/c/openstack/governance/+/86263715:57
*** dasm|rover is now known as dasm|off19:21

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