Thursday, 2022-02-17

*** pojadhav|out is now known as pojadhav03:50
*** pojadhav is now known as pojadhav|lunch09:27
*** pojadhav|lunch is now known as pojadhav10:13
opendevreviewAlex Kavanagh proposed openstack/election master: Add Alex Kavanagh as Candidate for OpenStack Charms project  https://review.opendev.org/c/openstack/election/+/82967611:23
*** pojadhav is now known as pojadhav|afk12:53
gmanntc-memebrs: TC meeting in an 8 min from now14:52
gmann#startmeeting tc15:00
opendevmeetMeeting started Thu Feb 17 15:00:06 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
dansmitho/15:00
gmann/15:00
gmanno15:00
yoctozeptoo/15:00
dansmithgmann: what happened to your arm (and/or head)?15:00
belmoreirao/15:00
jungleboyjo/15:00
gmanndansmith: its my bad keyboard :)15:01
dansmithheh15:01
ricolino/15:01
yoctozeptoseems gmann is losing his mind because of his bad keyboard15:01
spotz__o/15:01
* jungleboyj is laughing15:01
dmendiza[m]🙋‍♂️15:01
gmann:)15:01
gmanndmendiza[m]: hi15:02
gmannlet's start15:02
gmann#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions15:02
gmanntoday agenda ^^15:02
slaweqhi15:03
gmann#topic Follow up on past action items15:03
gmannslaweq: hi15:03
* slaweq will be just lurking for now :)15:03
gmannbelmoreira to propose the next release naming ideas15:03
gmannand belmoreira proposed it #link https://review.opendev.org/c/openstack/governance/+/82956315:03
gmannbelmoreira: would you like to discuss anything here or continue on gerrit ?15:04
belmoreirawe discussed the main idea during the last meeting. Map the release name with the year15:04
belmoreiraplease have a look to the proposal15:05
gmann+1, there are discussion going on in gerrit, please review and add feedback if you have any15:05
jungleboyjHaven't looked at the patch yet, so would like to do that and then go from there.15:05
gmannthanks 15:06
dansmithyep, I'll hit it right after this15:06
gmann+115:06
gmannmoving next15:06
gmann#topic Gate health check15:07
gmannany news on gate15:07
dansmithI haven't been pushing as many patches the last week, except for non-code things,15:07
dansmithso I'm not really sure how things are15:07
dansmithI know there were a number of repeat failures last week, but I never really checked into them since they didn't block me (because I suck)15:07
gmannvolume detach on centos9 stream issue will be fixed by this tempest series #link https://review.opendev.org/q/topic:wait_until_sshable_pingable15:08
dansmiththe gate is not very full right now so I tend to assume that means we're not seeing high failure rate in the gate queue15:08
dansmithalso, not really gate related but:15:08
gmannI will rebase/update it sometime next week early 15:08
dansmithglance had to de-vote our fips jobs because just running them on centos was introducing all kinds of failures15:08
dansmithseemingly libvirt and/or qemu crashes15:09
gmannin nvoa they are non voting and tempest they are in experimental queue15:09
dansmithyeah, but isn't the community goal to have them voting?15:09
gmannI think there is time to make them voting and run in check but not sure about other project.15:10
dansmithat this point I kinda worry about being able to do that15:10
gmanndansmith: goal is proposed not selected yet15:10
dansmithwell, right, but...15:10
slaweqin neutron we also have them in experimental queue for now15:10
slaweqI want to move them to periodic probably15:11
gmannwe can progress on that but as per my understanding from tempest patches that we are still not in state of making them voting15:11
dansmithmakes me concerned about accepting the goal if that brings "have to run centos jobs voting" which aren't going to be stable15:11
gmanndansmith: exactly, trying the jobs as n-v / experimental give us good input for goal selection 15:12
* dansmith nods15:12
spotz__I like the nv for seeing if it'll work, plus allows us to possibly bug things we find in stream15:12
fungiis anyone maintaining a list of the errors they've been seeing in failed fips jobs?15:12
dansmithno, the one I dug into was pretty obscure,15:13
dansmithbut the end result was qemu crashes,15:13
dansmithbut those aren't always actually qemu (although sometimes they are)15:14
fungiare these running in parallel with non-fips centos jobs?15:14
dansmithbut it manifested at the higher layer as like timeouts waiting for device attachments and things15:14
dansmithnot in the places I'm looking, but I can't imagine what the fips-ness would have in the way of impact on things likethat15:14
fungijust curious if the failires can be attributed to running in fips mode specifically, or if they're the background noise of bugs from running tests on centos when we don't normally test on centos15:15
gmannone i know encrypted cinder volume does not work in fips15:15
dansmithI think it's centos15:15
fungigot it, so suspecting that the problem isn't testing fips mode, but testing on centos15:15
dansmithright15:16
spotz__Yeah it'd be interesting to see if fips vs no-fips results in same or different errors15:16
fungiso the "we're going to have voting fips jobs" had hidden in it "we're going to have voting centos jobs"15:16
fungiwhich, i agree, is a much bigger lift15:17
dansmithfungi: right15:17
gmannyeah15:17
gmannlet's continue them non voting until they are ported on other distro or with centos job voting. and when this goal is proposed for selection then this is one input we need to check15:18
jungleboyj++15:19
gmannthis is ongoing work for fips #link https://review.opendev.org/q/topic:fips-compatibility15:19
fungiworth keeping in mind, just minutes ago we added rocky linux (a rhel derivative) images to our nodepool in opendev15:20
fungiso that might be a viable alternative too15:20
gmannnice, any initial job trying that?15:20
yoctozeptokolla is working on one15:20
fungithere were at least a couple teams interested in having it15:20
fungimore like what centos was before stream15:20
yoctozeptohttps://review.opendev.org/c/openstack/kolla-ansible/+/81510415:21
jungleboyjfungi:  ++15:21
fungiso it's closer to what's in rhel rather than what's going to eventually end up in rhel15:21
gmannok. sounds interesting to see the jobs and result 15:21
gmann#link https://review.opendev.org/c/openstack/kolla-ansible/+/81510415:21
gmannthanks yoctozepto fungi 15:21
gmannanything else on gate?15:22
gmann#topic Z Release Cycle Name15:22
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027242.html15:22
gmannZ name is final as 'Zed' ^^15:23
gmannthere is one objection but we cannot do about it at this point15:23
jungleboyjI think there are objections, but there isn't much we can do.15:23
gmannyeah. those should have brought when we asked on ML before election and trademark checks15:24
fungiobjections are fine, as long as the tc doesn't feel those objections are serious enough to redo the process15:24
yoctozeptowell, fwiw, the pronunciation of the letter Z should not raise too many concerns - should it? :D15:24
spotz__Is it worth reaching out to the foundation to see if they want to send it to legal for another name?15:24
* dansmith shakes his head15:24
gmannyoctozepto: agree :)15:24
jungleboyjspotz__:  I don't think it is worth making a fuss over.15:25
gmannspotz__: is it worth? and when we will stop it if there is objection on other name too. 15:25
dansmithseriously15:25
gmannyeah, there is nothing where we have everyone agree :)15:25
spotz__Just askig, hence not saying we should15:25
dansmithI'm going to start objecting to specific version numbers that I don't like15:25
* yoctozepto is just glad it was not zombie that won15:25
jungleboyjAnd the person that was worried about Pulp Fiction, I think in that case it was spelled 'Zedd' but I could be wrong.15:25
yoctozeptodansmith: yeah, we don't like 2022 because of zomicron15:26
spotz__Zombie was growing on me. I should have spammed you all with Ziggy the dog pictures before voting:)15:26
fungiwe'll skip any version numbers that have 4 or 13 in them, right? ;)15:26
dansmithyoctozepto: wfm :)15:26
jungleboyjfungi:  ++15:26
yoctozeptofungi: why 4?15:26
jungleboyjyoctozepto: That is considered bad luck in Asia, like 13.15:26
spotz__I liked CLark's idea where D would have ended up Dabomb:)15:26
fungi4 is pronounced the same as "death" in some languages15:26
yoctozeptojungleboyj, fungi: thanks15:27
jungleboyjspotz__:  ++15:27
gmannok, let's move on ?15:27
yoctozeptospotz__: Darude - Sandstorm15:27
dansmithyes please15:27
belmoreira:)15:27
gmannwe will continue discussion on future names but for Zed let's make it final15:27
jungleboyjThat is a good one too.15:27
gmannI will remove the topic from next week agenda15:27
jungleboyjZed it is.15:27
gmann#topic Z cycle Technical Elections15:27
gmannnomination are closed and we are : 17 projects without PTL, TC: all 5 seat nomination so no runoffs 15:28
jungleboyj:-(  To the 17 projects without PTL.15:28
spotz__I saw another late one come in this morning, didn't update the etherpad yet thpigh15:28
yoctozeptojungleboyj ++15:29
gmannthough there is no voting needed for PTL or TC, we thought of having Campaigning for tc 15:29
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027311.html15:29
gmannafter that on Feb 22 we will close the election15:29
gmannmeanwhile I have created the etherpad for leaserless projetcs to discuss #link https://etherpad.opendev.org/p/zed-leaderless15:30
gmannwith late candidacy we are left with 11 projects to look solution for15:30
jungleboyjWell, that is a little better.15:30
spotz__While everyone should be aware I don't think we spammed enough15:31
fungithere were, what, 4 reminders? 5?15:31
spotz__I was happy to see we had 5 for TC15:31
gmannnot sure, it is happening in every election that lot of late candidacy 15:31
jungleboyjNo e-mails with flashing red text were sent.15:31
gmannalso not sure how to improve it :) 15:31
spotz__Yeah I didn't think to tweet, we could have done that from Openstack and ops meetup15:32
gmannsending personal email to current PTLs? 15:32
jungleboyjspotz__:  ++15:32
gmannspotz__: yeah may be15:32
fungiit might be nice to separate some of that from the election officials' responsibilities though15:32
spotz__I know with OPS meetup we get better covereage and response tweeting vs ML. But yes the PTLs should have known it was coming except maybe the new projects15:33
gmannanyways something to discuss as retrospectively in PTG or in next election 15:33
fungithe tc reaching out to current ptls, for example, would be cool. expecting the eleciton officials to do even more work is not great15:33
gmannfungi: yeah. 15:33
slaweqmaybe send announcement to the irc team channels too?15:33
fungiwe need scalable solutions that don't make more work for volunteer officials15:33
gmannor extend the nomination period to 2 weeks15:34
spotz__Yeah and I don't think the election officials should, to some degree that could be construed as bias15:34
fungithat too, i agree15:34
gmannyeah, I will add those points in PTG discussion 15:34
belmoreirafor me it's really sad if current PTLs are not aware of the process... or not follow the mailing list15:34
gmannbelmoreira: unfortunately it is true 15:34
gmannlet's keep finding the leaders or add your opinion in the etherpad for those 11 projects15:35
belmoreiramaybe the elections should be more close with the release. Like we have the release event and as consequence new PTL elections15:35
yoctozeptobelmoreira: we have to beg for candidates for non-really-healthy projects so it's no wonder15:36
spotz__I kinda like that as the PTL would finish the release and before more work got deeply underway new leadership comes in15:36
fungithat could create timing issues, as teams begin work on the next release during the rc period, and possibly release planning even earlier15:36
yoctozepto++ fungi15:36
spotz__ok NM!15:36
fungiat least that's why we traditionally scheduled ptl elections ahead of the end of the cycle15:37
gmannyoctozepto: more than not-relaly-healthy there are many cases healthy projects also miss the nomination 15:37
fungiwe also tried to get the elections to happen prior to in-person gatherings where planning for the next cycle would take place15:37
belmoreiratrue... but the result is that we don't have a clear boundary and can lead to some miss comunication 15:37
gmannagree, it might be worst doing it more later during release time15:37
yoctozeptogmann: I meant begging, not the late/initially-invalid submissions :-)15:37
spotz__Some I think is loss of concept of time, which is why I wonder if we spammed enough. Folks wait until the last minute15:37
jungleboyjspotz__:  True.  Time doesn't seem to pass the way it used to.15:38
gmannyoctozepto: ok :). +1. 15:38
fungiyeah, going back to the early days of the project we've always gotten the majority of nominations on the last day of the nominations period15:38
gmannanyways time running, let's move to next topic and I will add this topic for PTG and for PTL+TC sessions in PTG15:39
spotz__+115:39
gmannbut let's check and add feedback in etherpad15:39
gmannone more update is keystone moving from DPL to PTL model and thanks to dmendiza[m] for heling to lead it.15:39
jungleboyj++15:39
gmannI will merge governance patch once it ready to merge as per formal-vote15:39
gmann#topic Dropping tags framework - next steps (yoctozepto)15:40
gmannyoctozepto: ^^ anything to update15:40
fungii'm hoping to move the vulnerability:managed tag info into the openstack/ossa repo in the next few days, sorry i haven't gotten to it yet15:40
gmannor elodilles if you would like to discuss any concern you raised in ML form release team perspective15:41
gmannfungi: +1, thanks15:41
gmannfungi: ping me once you do that, and then we can ask foundation to update the openstack navigation site to link to that page15:42
gmannjust to remind tc-members that part-1 of tag removal is ready to review #link https://review.opendev.org/c/openstack/governance/+/82290015:43
fungigmann: which page of the site specifically?15:43
fungii can also work with them on getting it updated15:44
yoctozeptosorry, I was away15:44
gmannfungi: nice, this one https://www.openstack.org/software/releases/xena/components/nova15:44
yoctozeptofungi: thanks, that's ok15:44
gmannfungi: for all projects where VMT is mentioned under 'Project details' section15:45
fungiahh, got it, we may want to drop that from those pages yes15:45
fungisince we won't have the tag any more15:45
yoctozeptoregarding releases repo - we need to drop more15:45
yoctozeptoI did not have time to drive this15:45
yoctozeptobut I'm glad the release team does not oppose it15:45
gmannlike stable policy is linked to table policy page we can update VMT also to new VMT page15:45
gmannyoctozepto: yeah, 15:46
yoctozeptois not the foundation page using tags directly?15:46
gmannfungi: dropping also fine or just update link to new page if anyone relying on the info from website15:46
yoctozeptoas I see the list has shrunk15:46
fungiyeah, since the vmt will consult with and help any team with reported vulnerabilities if they want, the list of which ones we're the first line of triage on is probably less relevant these days15:46
yoctozeptoso from our actions likely15:46
yoctozeptoso the decision is to drop15:47
yoctozeptook15:47
gmannok15:47
yoctozeptowhere is the source code for that site?15:47
fungithat content may not be in a git repository, some of the stuff there is in a cms15:47
yoctozeptomeh15:47
gmannyeah15:48
fungi(a database-backed cms)15:48
fungiit's handled by a contract web developer company the foundation uses15:48
yoctozeptoI wonder if it will simply display no list if we drop all tags15:48
yoctozeptoor break15:48
gmannlink will be broken for sure. 15:48
yoctozeptogmann: I think it will be gone15:48
yoctozeptoas the others are15:48
gmannohk15:48
fungiyeah, what i don't know is if there's some automated scraping of the reference/projects.yaml to auto-build that content. but i can ask15:49
yoctozeptobut obviously not sure15:49
yoctozeptofungi: thanks!15:49
gmannfungi: thanks, we will discuss about it in next week meeting accordingly. 15:49
yoctozeptoonce we fix releases, we can always merge governance change and undo if it breaks the pages15:49
gmannyoctozepto: part-1 does not break anything right?15:50
yoctozeptogmann: right15:50
gmannyou mean for next patch for removal completely ?15:50
yoctozeptogmann: yeah15:50
gmanngot it. +115:50
gmannmoving next if nothing else on this topic? 10 min left15:50
yoctozeptoforgot the part 1 is not merged yet I thought it was15:51
yoctozeptoso no idea how the website will behave15:51
yoctozeptosorry for confusing15:51
gmannyeah, it is still waiting for more vote15:51
yoctozepto(though I remember seeing more characteristics)15:51
yoctozeptolet's move on15:51
gmann#topic Progress check on Yoga tracker15:51
gmann#link https://etherpad.opendev.org/p/tc-yoga-tracker15:51
gmannwe are close to Yoga release and still pending few items15:52
gmannmost of them are in progress like tag, release name etc15:52
gmannplease update the etherpad if any updates on those not started yet. 15:53
jungleboyjI know I haven't gotten to my item.  :-(  15:53
spotz__I'm considering abandoning my patch until we decide what we really want15:54
jungleboyjI will be able to get that done before the PTG though which I think is when we want work on that done.15:54
gmannspotz__: ok, I think we can add on first guidelines unless you want to refactor the existing one i commented for15:54
gmannjungleboyj: +1, that will be nice. 15:54
gmannricolin: any chance you found the goal checklist? that is only pending item for community-wide goal?15:55
spotz__gmann: I'll take a look15:55
gmann* goal checklist etherpad15:55
gmannspotz__: thanks 15:55
gmannlet's move, I will catch with ricolin later15:56
gmann#topic Open Reviews15:56
gmann6 open review #link https://review.opendev.org/q/projects:openstack/governance+is:open15:56
gmann3 review ready and need more feedback are15:57
gmann#link https://review.opendev.org/c/openstack/governance/+/82290015:57
gmann#link https://review.opendev.org/c/openstack/governance/+/82956315:57
gmannthese two we already discussed15:57
gmann#link https://review.opendev.org/c/openstack/governance/+/82877715:57
gmanndansmith proposal for release cadence adjustment resolution15:58
gmanndansmith: we are just 2 min left but in case you would like to say/discuss on this ^^15:58
dansmithyeah, there's been some review already,15:58
dansmithand some adjustments,15:58
dansmithI think the feedback has all been positive and looking for clarifications,15:58
dansmithso would appreciate comments even if it's just "sounds good, let's try this"15:59
gmannnice. I will check sometime soon may be tomorrow 15:59
dansmithit's very flexible in what it commits us to, so I'd really like to not drag out approval on this for too long unless there are real objections15:59
dansmithbecause getting ready for the A release will be better if we know it's coming15:59
gmann+116:00
gmanntc-members ^^ let's review and add feedback. 16:00
gmannthat is all from my side today16:00
gmannthanks everyone for joining 16:00
gmann#endmeeting16:00
opendevmeetMeeting ended Thu Feb 17 16:00:39 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-17-15.00.html16:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-17-15.00.txt16:00
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-17-15.00.log.html16:00
yoctozeptothanks gmann16:00
* yoctozepto off16:01
jungleboyjThanks gmann !16:01
spotz__Thanks all!16:02
elodillesgmann: well, no other concerns than what i mentioned on ML. And I think we can live without the tags. Anyway, I'll ask the release team on the tomorrow meeting maybe16:41
gmannelodilles: thanks. 16:44
gmannelodilles: do let us know if any other way we can provide that info to help release team if it is mandatory.16:44
elodillesgmann: sure, thanks16:45
*** kopecmartin_ is now known as kopecmartin19:11
opendevreviewLance Albertson proposed openstack/election master: Add Lance Albertson candidancy for Openstack Chef PTL  https://review.opendev.org/c/openstack/election/+/82976519:36

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