Wednesday, 2022-11-16

*** dasm|off is now known as Guest163403:20
opendevreviewMerged openstack/governance master: Adding TC chair election process: nomination in governance repo  https://review.opendev.org/c/openstack/governance/+/86277206:49
opendevreviewGhanshyam proposed openstack/governance master: Update CHAIR.rst for few updates  https://review.opendev.org/c/openstack/governance/+/86263706:57
*** akahat|ruck is now known as akahat|rover|lunch07:35
*** akahat|rover|lunch is now known as akahat|rover08:28
*** pojadhav is now known as pojadhav|afk08:47
*** pojadhav|afk is now known as pojadhav10:23
*** Guest1634 is now known as dasm13:48
slaweqhi gmann, I will not be able to attend today's tc meeting. I prepared new rechecks data in the etherpad, generally all looks good there, nothing to discuss really from my side13:53
*** akahat|rover is now known as akahat|ruck|afk14:03
*** akahat|ruck|afk is now known as akahat|ruck15:00
gmannslaweq: ack, thanks for update15:28
gmanntc-members: meeting time16:00
gmann#startmeeting tc16:00
opendevmeetMeeting started Wed Nov 16 16:00:14 2022 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'tc'16:00
gmann#topic Roll call16:00
gmanno/16:00
knikollao/16:00
JayFo/16:01
gmannlet's wait for couple of min for other members to join.16:02
arne_wiebalcko/16:02
gmanndansmith spotz noonedeadpunk rosmaita ping for meeting16:03
rosmaitao/16:03
gmannin Absence section, slaweq - 16.11.202216:03
gmannwe have 5 members so let's start16:04
gmann#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting16:04
gmann^^ today meeting agenda16:04
jungleboyjHowdy.16:05
noonedeadpunko/16:05
gmann#topic Follow up on past action items16:05
gmannwe have two action item from previous meeting16:05
gmanngmann to check with foundation about zoom pro account if any and can be shared with TC monthly video call16:05
gmannI sent email but did not get response yet so I will keep it open16:05
gmann#action gmann to check with foundation about zoom pro account if any and can be shared with TC monthly video call16:05
gmannrosmaita to continue his research/survey on translation things and update in TC meetings16:06
gmannrosmaita: any update on this?16:06
rosmaitayes16:06
rosmaitai put together a draft survey, could use some eyes/comments on it16:06
rosmaitahere comes a really long url16:06
rosmaita#link https://forms.zohopublic.com/rosmaitafossdev/form/OpenStacktranslationsusageandcontributionsurvey/formperma/9W0PYjoo61tAShU9B1GQj3m52K43uty-KtXDhIlOUe416:06
rosmaitabut that's what you get for free16:07
rosmaitawhile doing this, i learned that there has been a lot of consolidation in the free survey industry16:07
rosmaitaand most options have a free level that is practically useless16:07
fungii take it limesurvey didn't pan out16:07
gmannohk16:08
rosmaitano, limesurvey only allows 25 responses a month16:08
rosmaitawufoo only allows 100 "entries" a month (whch would be about 20 responses)16:08
rosmaitapabbly.com only allows 100 submissions on a form16:08
rosmaitatypeform only 10 responses16:09
rosmaitabut zoho.com allows 500 submissions/month16:09
fungiouch, yeah i guess i only lightly tested limesurvey's hosted version before i set up one to run in opendev (but then nobody used it, so we turned it off)16:09
rosmaitahence, that's what i picked16:09
rosmaitagoogle forms allow unlimited responses, but are not available worldwide16:09
rosmaita(just for the record)16:10
gmannthanks that is good info to consider in future.16:10
rosmaitafungi: would be good if you could review what i say there about opendev infra supporting an instance16:10
rosmaita(i took it from a clarkb email, so is probably correct)16:10
fungirosmaita: will check, thanks16:11
fungirosmaita: lgtm16:12
rosmaitagmann: do we have time to look it over now, or should i say please get me comments by <date>16:12
rosmaitafungi: ty16:12
fungieither way though, there's still work for someone to (re)implement the import/export automation, even for the hosted weblate16:12
gmannrosmaita: not now, you can continue and we can track it when ever you are ready via tracker16:12
rosmaitaok, everyone, please give me comments before Friday at 1700 UTC16:13
fungirosmaita: oh, zanata is the correct spelling, not zenata16:13
fungiminor nit16:13
rosmaitathanks, i must be confused with ZenDesk!16:13
gmann+1, let's get the response and once we have the data then we can discuss and decide 16:14
gmannanything else on this ?16:14
rosmaitanope16:14
gmannthanks 16:15
gmann#topic Gate health check16:15
gmannany news on gate?16:15
gmannI have not monitored gate this week much as working on RBAC/service role testing and also migration to jammy16:15
fungimoments ago we found out ovh is having an incident impacting some of their swift services, so we merged a change to temporarily stop uploading job logs there, but some builds in the past hour or so ended with post_failure16:16
gmannok16:16
fungiearly utc saturday we had a transient bug with our weekly rolling zuul upgrade which caused builds to end with retry_limit results, but by mit-saturday utc it was resolved (once the scheduelrs were running the same version as the executors). we merged a fix for that so other zuul deployments won't hit it16:17
noonedeadpunkWell, I found out that sahara if installed with Zed u-c (or with master) is not usable due to jsonschema version16:17
noonedeadpunkBut that;s  not gate specific thing, but more project health I guess16:18
gmannohk, not sure we have many active maintainer in sahara but we fixed jsonschema things in other repo during Zed i think16:18
fungithe recent round of branch eols also raised some new errors in projects which didn't eol those branches but were consuming branch-specific jobs from ones that did16:18
noonedeadpunkPatch exists but was -1 on CR16:18
fungiworth revisiting whether transition from em to eol is really something we can leave up to individual projects16:18
gmanndevstack is another example in that where we need to fix it to use the EOL tag for project moved to EOL16:19
noonedeadpunkwell at very least I think that projects with trailing releases must EOL after all other projects as well16:19
fungiyes, there is implied work for other teams when we do integration testing between projects but allow them to eol branches on different schedules16:19
noonedeadpunkYeah, for reason gmann said actually16:20
gmannnot sure how easy or difficult to have a coordinated transition to EOL but release team knows better16:20
JayFI'll note that forcing teams to remain in "EM" when they wish to EOL will still push back that job-fixing-work on other teams if they aren't maintaining CI for that EM release.16:20
fungiagreed, i feel like we leave em branches open far too long16:21
gmannI will say they are moving from EM to EOL so if EM is broken due to some project EOL then it is good indication to EM projects also to do16:21
JayFThere's no way to get around it: one project not-caring about an older release impacts any it cross-gates with; whether that's via EOL tag or just neglect16:21
gmannJayF: +1 yeah16:21
gmannin devstack also, we were discussing the same. let devstack EM branch broken and if anyone backporting and need devstack then they can fix it16:21
rosmaitawell, when a project goes EOL on a branch, in devstack you can tell it to check out the eol tag instead of the stable branch16:22
gmannthat is overall approach to EM anyays16:22
gmannrosmaita: yeah but that is extra work we need to do16:22
JayFand it leaves no path if that job starts failing due to bit rot or other reasons16:22
gmannI am not denying to do that but instead anyone maintaining the branches as EM can do16:23
JayFI actually think hard-failures might be preferable to testing against code you could never fix 16:23
JayFbut I'm not the one zuul is screaming at when the yaml doesn't parse :) 16:23
* dansmith stumbles in late16:23
gmannthis Friday (Nov 18) we will merge the base jobs moving to Jammy. and project can pin failing job to Focal nodeset for time being16:24
gmann#linkk https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031205.html16:24
gmannnoonedeadpunk i think let's stick to the deadline and not delay that.16:24
dansmithagree16:24
gmannceph and swift fixes are still not merged16:24
gmannand horizon nodejs also failing16:24
dansmithdo we need a patch to pin ceph stuff on focal ahead of friday?16:25
noonedeadpunkgmann: well, in OSA we also need to switch all projects to eol tag before marking osa as eol16:25
fungiyeah, the sooner that is switched the more time projects have to fix up problems they don't already know about. allowing projects which are aware of problems and haven't fixed them yet to delay that would be a poor prioritization, in my opinion16:25
gmannyeah to get devstack patch merge16:25
gmanndansmith: I will try to push one today16:25
noonedeadpunkotherwise, we will reference branches that does not exist16:26
dansmithgmann: okay16:26
noonedeadpunkah, you meant schedule about jammy transition16:26
gmannnoonedeadpunk: ok but you can just wait for all project to go EOL and keep OSA EM as broken ?16:26
noonedeadpunksorry16:26
noonedeadpunkyeah, I jsut haven't switched to the new topic yet :)16:27
gmannohk, sorry for jumping to next16:27
noonedeadpunknah, it's fine, sorry for being slow :)16:28
gmannnoonedeadpunk: for jammy migration, I know you fix is up for ceph job but it seems some other failure there. swift one is still not merged too16:28
noonedeadpunktbh I'm not sure what should be passing and what's not - jobs are marked as NV so hard to say kind of. I would expect NFS to pass though. I think it's a usecase with ganesha16:29
gmannthis is swift fix timburke mentioned in swift channel #link https://review.opendev.org/c/openstack/swift/+/86344116:29
noonedeadpunkCan look into that if it's supposed to work16:29
gmannsure16:29
noonedeadpunkoh no, "//" again16:30
gmannbut let's do the migration on Friday, I will keep pinning nodeset patches ready meanwhile16:30
gmannyeah16:30
gmannanything else on gate health?16:31
gmann#topic 2023.1 TC tracker checks16:31
gmann#link https://etherpad.opendev.org/p/tc-2023.1-tracker16:31
gmannrosmaita already provided updates on i18 SIG16:31
gmannone update form me on TC chair process which is merged now16:32
gmannand upgrade path patch is up for review #link https://review.opendev.org/c/openstack/governance/+/86059916:32
gmannnoonedeadpunk ^^ updated it as per your review comment, please have a look16:33
gmannany updates form anyone on their assigned items?16:33
gmannok, if nothing else let's move to next topic16:34
gmann#topic TC stop using storyboard?16:34
gmann#link https://storyboard.openstack.org/#!/project/92316:34
gmannwe discussed it in last week meeting, and many of us even were not aware that it exist16:35
gmannand defer this topic to this meeting as we were not having majority of TC in the meeting16:35
knikollaI remember that there was a push for everyone to use Storyboard many years ago16:35
gmannyeah16:35
knikollaAm I correct in assuming that push is not happening anymore and that Storyboard is not really seeing developmnet?16:36
gmannin TC we are using tracker in eytherpad which is much easy and also for many goal tracking also16:36
gmannwell, most of the projects decided to move to LP like ironic, placement. so not sure that it is good idea to move them back to SB again16:37
noonedeadpunkWell, during PTG there were couple of topics on different tracks to move out from storyboard as well16:37
gmannbut we are not deciding to shutdown SB for now16:37
gmannyeah16:37
fungiyes, this is less about whether projects are using storyboard and more that the process doug originally devised for goal tracking isn't being used and hasn't been for years16:37
gmannlet's see how project goes and prefer over time16:37
gmannfor TC SB, we can decide if we want to stop using SB or not16:38
knikolla++, just trying to get more context on where we stand as a community16:38
noonedeadpunkI personally find SB quite hard to use16:38
JayFI think it'd be a positive change to just remove this tracking of governance from storyboard, and migrate it to "nothing" (our etherpad?)16:38
gmannyeah16:38
dansmithyep, NFO, move on16:38
gmannI would like to have a vote here for the record, any more question/discussion before I start voting?16:39
fungithe vote is specifically about deactivating the openstack/governance repo in storyboard.openstack.org, right?16:39
gmannyes16:39
* dansmith readies his voting finger16:39
knikollaand not moving to launchpad16:39
knikolla?16:39
gmannyes 16:40
dansmithI think we identified that we don't need either because most of us didn't even know the SB stuff was a thing16:40
dansmithwhich I'm in favor of16:40
gmannok, let's start the voting, putting all together  16:40
gmann#startvote TC stop tracking things on storyboard, close the governance project in SB, and not moving to LP? Yes, No16:41
opendevmeetBegin voting on: TC stop tracking things on storyboard, close the governance project in SB, and not moving to LP? Valid vote options are Yes, No.16:41
opendevmeetVote using '#vote OPTION'. Only your last vote counts.16:41
knikolla#vote Yes16:41
gmann#vote Yes16:41
rosmaitai don't think we need the "not moving to LP" in there16:41
dansmith#vote Yes16:41
noonedeadpunk#vote Yes16:41
rosmaitaseems extraneous16:41
JayF#vote Yes16:41
noonedeadpunk+1 to that16:41
gmannrosmaita: just to make sure16:41
rosmaitamake sure of what, though?16:41
noonedeadpunkOr answers should be not boolean16:41
gmannrosmaita: usually closing SB means moving to LP16:42
knikollathere might be ambiguity in the need for an issue tracking mechanism for governance, and the SB/LP has been a binary usually. 16:42
rosmaitawell, i don't see any reason not to move to LP if it would be useful16:42
gmannfor now we do not need to move to LP16:42
rosmaitaright, but i don't see why that needs to be part of this vote16:42
gmannrosmaita: we do not have such requirement to move to LP right?16:42
fungifor the record, it wasn't really issue tracking that it was being used for anyway, it was task tracking16:42
rosmaitaright, there is no obligation to use LP16:43
fungi(back when it was used at all)16:43
rosmaitabut i don't see why we would want to say we are not going there as part of not using SB16:43
dansmithI think so many projects are "moving back to LP from SB", and knikolla asked about it,16:43
dansmithso the clarification seems to make sense to me16:43
gmannrosmaita: if we use then we need to open project there and tack it too right16:43
gmannyeah, stop SB should not mean we are moving to LP and for TC it is kind of different than other project16:44
dansmithrosmaita: you know we're just talking about the TC's task tracking and not anything binding for other projects right?16:44
gmannso it should not be read as TC is stopping SB and they will be on LP16:44
gmannyeah this is specific for TC only16:44
JayF"TC will stop formally tracking status in storyboard, leaving TC with no storyboard usage or migration to perform" <-- would this wording be more clear?16:45
knikollaif we make a songs album, it should be on LP16:45
JayFI think we all agree just confusion over the wording, yeah?16:45
fungithe tc hasn't really been doing goal task tracking in storyboard for years, so it already stopped long ago. this is about cleanup16:45
rosmaitai would be ok with "TC stop tracking things on storyboard and close the governance project in SB"16:46
JayF++16:46
gmannok let's do that way. and as we are not using LP, leave that separate 16:46
noonedeadpunkwell, for me if we're adding LP part it would make sense to ask if we're closing SB and migrating nowhere, not closing SB or moving to LP16:46
gmann"TC stop tracking things on storyboard and close the governance project in SB and not migrating to any other tracking tool for now" ?16:47
noonedeadpunkAs if it occurs that there're majority to use bug tracking system, but not SB, we're cutting these votes right now16:47
fungithe tc no longer has any process relying on the presence of the openstack/governance project in storyboard. it's probably not accurate to vote to stop doing something that already isn't being done16:48
gmanneveryone agree on "TC stop tracking things on storyboard and close the governance project in SB and not migrating to any other tracking tool for now" ?16:48
noonedeadpunkI'm fine with that16:48
dansmithsure?16:48
rosmaitaok16:48
knikollaalright16:48
gmannok let me end vote first and restart. I do not think we have command to cancel the vote, please let me know if we do/?16:48
JayF#vote invalid16:49
opendevmeetJayF: invalid is not a valid option. Valid options are Yes, No.16:49
JayFheh there's no way to abstain after the fact16:49
gmannthis poll/vote is abandon and we are restring the new vote16:50
rosmaitayeah, it enforces the options very strictly16:50
gmann#endvote16:50
opendevmeetVoted on "TC stop tracking things on storyboard, close the governance project in SB, and not moving to LP?" Results are16:50
opendevmeetYes (5): gmann, dansmith, JayF, knikolla, noonedeadpunk16:50
JayFCan you #note that the vote before was invalid?16:50
JayFsomethign that'll show up in the summarized-log16:50
fungithe meetbot manual seems to completely skip over voting commands16:50
gmann#note previous vote was abandon and we are restarting the new vote on SB.16:51
gmanndone 16:51
JayFThanks16:51
gmann#startvote TC stop tracking things on storyboard, close the governance project in SB, and not migrating to any other tracking tool for now? Yes, No16:51
opendevmeetBegin voting on: TC stop tracking things on storyboard, close the governance project in SB, and not migrating to any other tracking tool for now? Valid vote options are Yes, No.16:51
opendevmeetVote using '#vote OPTION'. Only your last vote counts.16:51
dansmith#vote Yes16:51
knikolla#vote Yes16:51
gmann#vote Yes16:51
rosmaita#vote Yes16:51
noonedeadpunk#vote Yes16:51
JayF#vote Yes16:51
arne_wiebalck#vote Yes16:52
gmannI think all tc-members present here voted. 16:52
gmann#endvote16:52
opendevmeetVoted on "TC stop tracking things on storyboard, close the governance project in SB, and not migrating to any other tracking tool for now?" Results are16:52
opendevmeetYes (7): gmann, rosmaita, arne_wiebalck, dansmith, JayF, knikolla, noonedeadpunk16:52
fungii'll take care of the steps for closing down the openstack/governance repository in sb later today16:53
gmanncool, I will start the cleanup work on SB16:53
gmannfrickler: let me close the open tasks there in case we have clear cleanup16:53
gmannfungi: ^^16:53
gmannfrickler: please ignore16:53
fungibut yes, you probably need to patch some governance documentation which refers to it16:53
gmannyeah, also some open story/tasks too16:54
gmannok, moving next16:54
gmann#topic Recurring tasks check16:54
gmannBare 'recheck' state16:54
gmann#link https://etherpad.opendev.org/p/recheck-weekly-summary16:54
gmannslaweq added this week summary in ^^ etherpad16:54
gmannwhich does not look bad. any discussion on this?16:55
gmann#topic Open Reviews16:55
gmann#link https://review.opendev.org/q/projects:openstack/governance+is:open16:55
gmannneed one more vote in this #link https://review.opendev.org/c/openstack/governance/+/86263716:56
gmannother open review are either waiting for deps or already talked about in meeting16:56
JayFFYI: I abandoned my proposal for video meetings; I appreciate everyone giving their feedback about the idea in writing but there was a clear consensus against it.16:56
rosmaitaoh, i was wondering what happened to that16:56
gmannack 16:56
gmannreminder that we have Board + OpenStack syncup call today at 20 UTC (i think 3 hr from now) #link https://etherpad.opendev.org/p/2022-11-board-openstack-sync16:57
knikollathanks for writing it JayF . It was really helpful to get additional points of view. I'll be doing some more research into how other communities do it.16:57
gmannplease plan to join16:57
gmann+116:58
gmannwe are on time, 2 min left. anything else?16:58
knikollaI'll be on vacation all of next week.16:58
gmannknikolla: ack. thanks for update16:59
gmannok, let's close then. thanks everyone for joining16:59
gmann#endmeeting16:59
opendevmeetMeeting ended Wed Nov 16 16:59:31 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.html16:59
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.txt16:59
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.log.html16:59
arne_wiebalckthanks gmann!17:00
JayFI will not be at next meeting as well; on vacation17:00
gmannJayF: ack. 17:00
JayFI mean, generally speaking, our next scheduled meeting is the Wednesday before thanksgiving in the US; we might want to check if we'll even be able to reach quorum17:01
fungii just looked through the meetbot source and confirmed there is no command to abandon a vote (though it would not be hard to add, basically just another class method in meeting.py)17:01
JayFthat way we can give non-US TC members their time back ahead of time if needed17:01
gmannfungi: yeah, i could not find either but will be good to have one17:01
fungialso a #undo after the #endvote would likely have stricken its result from the minutes, but i'm not sure without some testing17:02
fungias far as abstaining, the right way to allow that is to make abstain one of the vote options, then tc members present can explicitly abstain and would be able to change from a yes or no vote to abstain if they saw fit17:03
gmannJayF: I think having 5 members form USA but not sure if all are not available. dansmith rosmaita spotz ?17:03
gmannI am ok to cancel next week meeting if majority agree17:03
dansmithgmann: I haven't decided if I'm taking next weds off yet or not17:04
fungiwe use meetbot for the spi board of directors monthly meetings, and the chair always makes "abstain" one of the possible options you can vote with17:04
gmannI will be around so either is fine for me17:04
dansmithbut makes sense to cancel probably17:04
gmanntc-members: is it ok to cancel next week (Nov 23)meeting? 17:05
arne_wiebalckfine by me :)17:07
JayFI'm obviously OK with it, I won't be here :D17:08
gmannrosmaita slaweq spotz noonedeadpunk what is your preference for TC week meeting ^^?18:00
rosmaitagmann: i will be around, but have no objections to cancelling the meeting18:05
gmannack, thanks 18:06
fungitc-members: don't forget, our community round-table hour with foundation board members starts at 20:00 utc (roughly 50 minutes from now)19:10
fungiconnection info is on https://etherpad.opendev.org/p/2022-11-board-openstack-sync along with the tentative discussion topics19:11
opendevreviewMerged openstack/governance master: Update CHAIR.rst for few updates  https://review.opendev.org/c/openstack/governance/+/86263719:44
gmanntc-members: board syncup meeting started now 20:00
clarkbspotz: just a heads up that I got Gerrit 3.6 fixed for the ssh issue. We didn't backport to Gerrit 3.5 because that required a jgit update which is well beyond my abilities in that codebase. However, they eventually updated jgit for different reasons and I backported the ssh fix to 3.5 and we've been running it for a few weeks now20:19
spotzclarkb: Oh nice, I've run into it a few times helping folks to get set up including at Summit during Git and Gerrit20:20
clarkbdefinitely let us know if you see similar issues going forward, but we've tested this a bit and expect it is a non issue at this point20:21
spotzWill do, I still need to redo a few slides that were off in Berlin assuming we'll run the session again in Vancouver20:22
*** dasm is now known as dasm|off23:11

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