Thursday, 2021-03-11

*** jamesmcarthur has quit IRC00:17
*** tosky has quit IRC00:26
*** jamesmcarthur has joined #openstack-tc01:19
*** jamesmcarthur has quit IRC02:32
*** jamesmcarthur has joined #openstack-tc02:39
*** jamesmcarthur has quit IRC03:19
*** jamesmcarthur has joined #openstack-tc03:21
*** jamesmcarthur has quit IRC03:23
*** jamesmcarthur has joined #openstack-tc03:23
*** openstackgerrit has quit IRC03:25
*** openstackgerrit has joined #openstack-tc03:47
openstackgerritGhanshyam proposed openstack/governance master: Close Xena Elections  https://review.opendev.org/c/openstack/governance/+/77984603:47
gmanndiablo_rojo: ^^ fixed the TC term date which is published as "Elected On" (we changed this in last cycle i think). your original date March,2021 was correct.03:48
*** diablo_rojo has quit IRC03:48
gmannother part lgtm, thanks for fixing03:48
gmannZun also have PTL candidacy now, we left with 5 project as PTL-less (out of which Cyborg might have PTL candidate during China day time)04:00
*** e0ne has joined #openstack-tc04:12
*** e0ne has quit IRC04:12
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-tc05:33
*** jamesmcarthur has quit IRC05:47
*** e0ne has joined #openstack-tc06:24
*** e0ne has quit IRC06:24
* ricolin rif06:25
* ricolin Rico is asking if WangXinRan will volunteer for Cyborg PTL role again06:26
ricolinWang XinRan will propose patch for volunteer for Cyborg PTL today06:41
*** ralonsoh has joined #openstack-tc06:51
openstackgerritXinran WANG proposed openstack/election master: Add Xinran Wang candidacy for Cyborg PTL in Xena  https://review.opendev.org/c/openstack/election/+/77991106:52
yoctozeptowhiteboard updated07:05
yoctozepto4 projects indeed07:05
ricolinyoctozepto, thx07:12
*** slaweq has joined #openstack-tc07:13
openstackgerritXinran WANG proposed openstack/election master: Add Xinran Wang candidacy for Cyborg PTL in Xena  https://review.opendev.org/c/openstack/election/+/77991107:26
*** lpetrut has joined #openstack-tc07:41
openstackgerritXinran WANG proposed openstack/election master: Add Xinran Wang candidacy for Cyborg PTL in Xena  https://review.opendev.org/c/openstack/election/+/77991107:43
*** david-lyle has joined #openstack-tc07:47
*** jamesmcarthur has joined #openstack-tc07:47
*** dklyle has quit IRC07:49
*** jamesmcarthur has quit IRC07:52
*** belmoreira has joined #openstack-tc08:04
*** dklyle_ has joined #openstack-tc08:08
*** david-lyle has quit IRC08:10
*** andrewbonney has joined #openstack-tc08:24
*** tosky has joined #openstack-tc08:33
*** tosky_ has joined #openstack-tc08:52
*** tosky is now known as Guest8681408:53
*** tosky_ is now known as tosky08:53
*** Guest86814 has quit IRC08:55
*** e0ne has joined #openstack-tc10:30
*** e0ne has quit IRC11:03
*** openstack has joined #openstack-tc13:17
*** ChanServ sets mode: +o openstack13:17
*** dklyle_ has quit IRC13:43
openstackgerritAurelien Lourot proposed openstack/governance master: Add Manila-NetApp backend charm to OpenStack charms  https://review.opendev.org/c/openstack/governance/+/78000713:58
gmannyeah 4 project left out of which Mistral can try DPL as discussed previously, we left with 3 projects to discuss for leader assignments.14:44
mnaser#startmeeting tc15:00
openstackMeeting started Thu Mar 11 15:00:48 2021 UTC and is due to finish in 60 minutes.  The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: tc)"15:00
openstackThe meeting name has been set to 'tc'15:00
jungleboyjo/15:00
mnaser#topic roll call15:00
mnasero/15:00
*** openstack changes topic to "roll call (Meeting topic: tc)"15:00
ricolino/15:00
gmanno/15:00
belmoreirao/15:01
redrobot15:01
yoctozepto\o/15:02
mnaser#topic Follow up on past action items15:02
*** openstack changes topic to "Follow up on past action items (Meeting topic: tc)"15:02
mnaser#link http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-03-04-15.03.html15:03
mnaserwe don't have anything listed, so we can skip that for today15:03
mnaser#topic Audit SIG list and chairs (diablo_rojo)15:03
*** openstack changes topic to "Audit SIG list and chairs (diablo_rojo) (Meeting topic: tc)"15:03
mnasercc ricolin on this one too15:03
yoctozeptoping diablo_rojo_phon15:03
ricolinwe only got one patch in review now https://review.opendev.org/c/openstack/governance-sigs/+/77830415:04
mnaserright, i think gmann brings up a good point about archiving things15:05
ricolinyes15:05
ricolinI through we have ways to retire a SIG15:06
gmannshould we add sig also in TC-liaison list so that we periodically checks the status/health ?15:06
ricolingmann, +115:06
jungleboyjgmann:  ++15:07
fungiwe had them in there originally15:07
gmannricolin: yeah we have for moving to 'completed' state but not for 'un finished ' or so15:07
fungithe first cycle or two that we did liaisons, we had an optional section for sigs and board-appointed committees/working groups15:07
gmannricolin: i mean if any SIG is retired from 'forming' state only15:07
gmannfungi: i see.15:08
gmannwhile reiterating the liaison for Xena cycle we can add SIG also in our automatic assignment script15:08
fungiat the time people felt just keeping up with all the project teams was more work than we were able to get done in the cycle, but we also had much loftier goals for health measurement back then15:08
gmannyeah15:08
ricolinI guess this is currently all we have for retire process https://governance.openstack.org/sigs/reference/sig-guideline.html#retiring-a-sig15:09
mnaserit's pretty hard to keep up with all the teams with all the things we have to deal with, that's what i found anyways15:09
gmannricolin: yeah, may be we can add 'forming' -> 'retire' also there15:09
belmoreira+115:10
mnasermaybe add a reason15:10
gmannmnaser: true, at least we know if any SIG is not active then who from TC can follow up quickly15:10
mnaserand say 'folded into XYZ'15:10
jungleboyjmnaser:  ++15:10
ricolinwe should also ask to retire or migrate SIG repo too in doc I assume15:10
*** spotz has joined #openstack-tc15:10
gmannmnaser: +1 for reason, nice idea15:11
ricolina reason will definitely something good for reactive15:11
ricolinI will update the doc to reflect on these suggestion15:11
gmannthanks.15:12
ricolinWill also update the container SIG patch too15:12
ricolindiablo_rojo_phon, ^^^15:12
mnasercool15:12
gmannand should I add SIG in TC liaison list if all ok?15:12
openstackgerritMerged openstack/election master: Close Xena Elections  https://review.opendev.org/c/openstack/election/+/77984515:12
mnaseri guess we could15:12
gmannok,15:13
ricolinI think we should15:13
ricolinbut on the other hand15:13
ricolinpopup tema15:13
ricolinwhat about popup team15:14
gmannpopup team has TC liaison/volunteer already.15:14
ricolinoh, than we're all good:)15:14
gmann#link https://governance.openstack.org/tc/reference/popup-teams.html15:14
gmann'TC Liaison'15:14
ricolinthe TC liaison for image encryption should update15:15
ricolinor we're fine to have non-TC for TC liaison for popup team?15:16
mnaseri think its ok for it to just be a liasion and not necessary a tc member15:16
mnaserbut maybe that's another discussion topic15:16
mnaser:p15:16
gmannyeah15:17
jungleboyj:-)  I mean, he is an honorary member.  :-)15:17
mnaserricolin: wanna add that to next weeks agenda?15:17
ricolinI think no need to make more discussion as I believe on fungi for it:)15:17
jungleboyjPoor guy will never be able to get away.15:17
ricolinmnaser, I think we're good on this15:17
gmann:) we will not let him to go away15:17
jungleboyj:-)15:17
fungiheh, yeah i was a tc member when i originally served as the sponsor for that pop-up15:17
ricolinyep!15:17
fungii still attend their weekly meetings15:18
gmann+115:18
mnaser#topic Gate performance and heavy job configs (dansmith).15:18
*** openstack changes topic to "Gate performance and heavy job configs (dansmith). (Meeting topic: tc)"15:18
jungleboyjhttps://media1.giphy.com/media/KczBU4M2IEdClprXaq/giphy.gif?cid=ecf05e4772p0dj0zuysiay11z145hvnovyiqbthd0thwb6nx&rid=giphy.gif15:18
fungii want to say we originally decided that tc liaisons for pop-up teams didn't need to be tc members, i just happened to be in that case15:18
dansmithoof, sorry15:18
mnaseri think this one has been a rotating topic without that much progress15:18
mnaserits been a busy week for all of us i think15:18
dansmithyeah, so,15:19
fungii saw we finally caught up with our node request backlog around 02:00 utc today15:19
dansmiththe gate has been crazy busy15:19
gmannyeah15:19
dansmithI've seen a lot of cinder fail,15:19
jungleboyjmnaser:  It has at least gotten some visibility in Cinder and we are working on cleaning up failures that are slowing the checks.15:19
dansmithand the tempest queue has been somewhat problematic15:19
dansmithwe're definitely doing a lot of work, which is great15:19
gmannyeah yesterday we finally got many of them merged in tempest but it was issue there15:20
dansmithgiven the last couple weeks have been atyipcal (for normal, not for this part of the cycle), it's hard to tell how good we are or aren'tm15:20
dansmithbut some things have taken millions of rechecks to get landed15:20
gmannand obviously it start happen during release time15:20
fungitoday is not so bad, i guess because we're at/past the freeze deadline now?15:20
dansmithfungi: the major rush was yesterday for sure15:20
funginode backlog reached nominal levels around 13:00 utc15:20
fungithere's a little bump at the moment, but there were brief periods in the past two hours where we weren't even using all of our quota15:21
dansmithmnaser: personally I think this is a good thing for us to keep eyes on.. doesn't have to be every week, but I think keeping it on the radar has yielded good stuff, IMHO15:21
mnaseryeah i think lets keep it on the radar15:21
mnaseri agree15:21
gmannagree15:21
jungleboyj++15:22
fungialso the additional quota from inap has really helped in the past few weeks15:22
dansmithfungi: yeah, really seems like it15:22
fungithings would have been much worse without it15:22
dansmithyesterday it was almost eight hours to get jobs running for a while,15:22
dansmithbut with a huuuge queue15:22
dansmithso it felt like things were doing pretty well considering all the fail15:23
*** dirk2 is now known as dirk15:23
fungithere's been some push on the ml to solve some cinder-related failures by switching the iscsi signalling is it?15:23
fungisomething which was causing a lot of job failures anyway15:24
jungleboyjYes.15:24
jungleboyjI am not sure where that landed after discussion yesterday though.15:24
dansmithswitching to or from iscsi,15:24
dansmithor switching something about how we use it?15:25
jungleboyjSwitching how we use it.15:25
fungilio vs tgt i think?15:25
jungleboyjFrom tgt to lio15:25
dansmithah15:25
fungianyway, would be good not to lose sight of it with the change volume dropping as the cycle goes through its post-freeze state change15:25
mnaserthis sounds all good so we'll keep watching over things :)15:26
mnaseri think we can move on to the next item15:26
dansmithyup15:26
mnaser#topic Consensus on lower constraints testing (gmann)15:26
*** openstack changes topic to "Consensus on lower constraints testing (gmann) (Meeting topic: tc)"15:26
gmannit seems no objection on the proposed plan on ML #link http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020556.html15:26
gmannwhich is basically 1. Only keep direct deps in lower-constraints.txt 2. Remove the lower constraints testing from all stable branches.15:27
gmannand it will be easy to maintain15:27
gmannlike for nova 77 deps can be removed from l-c #link https://review.opendev.org/c/openstack/nova/+/77278015:28
fungi#2 includes removing it from new stable branches when they get created15:28
gmann+115:28
fungistable branches need stable jobs, and those won't be stable over time15:28
gmannas next step, i feel we should document it somewhere, in project guide or PTI or resolution ?15:28
*** lpetrut has quit IRC15:29
yoctozeptoI agree, it makes most sense to have some stub for it and fix when needed15:29
gmannI feel PTI is better place?15:29
ricolingmann, do you think a goal is too strong/enforcing for this?15:30
gmannor resolution and then update PTI15:30
gmannricolin: it is not strong, i think just removing the indirect one which would not cause much work15:30
fungiwe haven't previously required the use of lower-constraints jobs, so it seems weird to have a policy requiring something about a non-required job15:30
yoctozeptoindeed15:31
fungii think so far the pti only lists necessary policy, so this would be a shift to also including guidance i guess15:31
yoctozeptoI am with fungi on this15:32
yoctozeptobetter not15:32
jungleboyjAgreed.15:32
* mnaser personally defers to the others on thisd15:32
gmanntrue for projects clarity we can add somewhere at least when project asked TC to have some guidelines on this15:32
fungii agree with the guidance, just seems like maybe not something that needs to be enshrined in openstack's governance15:32
yoctozeptoagreed15:33
fungidoes the qa team maintain content in the project teams guide?15:33
gmanni do not think so15:33
fungii wonder if a section in there on testing recommendations (not policy) would fit15:34
gmanni think pti is the place where we all look on testing guidelines15:34
fungiwell, we certainly look there for policies that the tc has officially voted on15:34
yoctozeptopti does not mention l-c at all15:35
gmannyeah that's what projects were looking for, TC decide on l-c testing15:35
yoctozeptoin fact, the only place is pt guide15:35
gmannyoctozepto: yes that was the confusion i think when this bring up on ML15:35
fungijust remember the pti is part of openstack's governing documents (it's in the governance repository along with things like tc resolutions)15:35
yoctozeptoyes15:35
gmannand it was hard to maintain and we did not find pti does not talk about it so remove it?15:35
gmannremove the testing job?15:35
* yoctozepto with his masakari ptl and kolla cores hats on admits to removing all l-c jobs15:36
gmannI feel having all testing policy in single place will be more clear15:36
yoctozeptonot a single tear was shed15:36
fungipolicy yes, but is this policy when it's about something not required?15:36
gmannand 'do not test l-c on stable and direct deps on master' s policy for testing15:37
yoctozeptofeels too brute15:37
gmannat least like 'only requirement is to test direct deps on master'15:37
yoctozeptoso we are then adding one now, aren't we?15:37
gmanni will say adding the one we were testing without any clearity15:38
gmannif we end up removing the l-c testing then I would agree15:38
yoctozeptowould make sense to query projects; perhaps some do not test l-c at all15:38
yoctozeptofwiw, masakari had broken jobs which ran noop with l-c so :-)15:39
yoctozeptojust saying :D15:39
gmannyeah because there was no clarity on whether to test or not15:39
yoctozeptoindeed15:39
yoctozeptoso do we want to test l-c? we know the shortcomings of the newly proposed approach15:40
gmannand after checking 'who need these'  and 'whether it is worth to test or not' we end up like yes we can at least test direct deps in consistent way15:40
yoctozeptoit makes sense obviously15:40
yoctozepto"accidental version bump, you shall not pass!"15:41
spotzHehe15:41
yoctozeptoI would vote on making this a policy then15:42
gmannin PTG, many project will be discussing on these like nova will so I think we should be ready with TC guidelines by then.15:42
fungiso far, openstack has not mandated lower bounds testing, but many projects used lower-constraints jobs as an ad hoc standard. recent changes in pip made it apparent they could not be easily maintained on stable branches. some projects were cool with removing their l-c jobs entirely (they're not required after all), others wanted to keep the jobs but were looking for a compromise and so we've suggested15:42
fungithat compromise is to just take them out of stable branches. none of that is policy15:42
yoctozeptoyes, none *is* at the moment15:43
mnaserso maybe this is something we can leave up to the projects to decide but list the different options?15:43
fungiit's all up to individual teams if they want to run l-c jobs at all, and they can also *try* to run them in stable branches if they like tilting at windmills, but it's inadvisable15:43
gmannmnaser: project wanted TC to decide15:43
gmannthat was the original discussion started when neutron asked on ML15:44
funginova wants the tc to tell them whether and how to run lower-constraints jobs?15:44
gmannafter oslo started the thread on dropping those.15:44
mnaserso if projects want the tc to decide, then it sounds like policy15:44
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019660.html15:45
gmannfrom here it was started to have some common guidelines15:45
fungia tc policy of "you can do this if you want" isn't a policy, so if some projects want the tc to make a policy about lower-constraints jobs then it sounds like they're asking the tc to require these jobs when they were not previously required. that's a lot different from mere guidelines15:46
mnaserok, so a guideline sounds like a list of approaches to take15:46
gmannwell it can be "l-c testing can be done with direct deps only for master and not needed for stable as mandatory"15:46
*** jamesmcarthur has joined #openstack-tc15:46
fungiis nova asking the tc to decide how all projects will do lower bounds testing, or is nova asking the tc to provide them with some suggestions? the first is policy, the second is not15:47
*** dklyle has joined #openstack-tc15:47
gmannits not nova, its from all other projects like neutron was seeing for some common strategy on this.15:47
gmannwhere come project were dropping it and some not15:47
fungiand i anticipate at least some projects to object to being required to add lower bounds testing they don't feel they have the capacity to stay on top of15:48
gmannwe have job testing it and it run on  all project/stable also so why not to make it in pti on what we expect on that.15:48
fungiand you'll need to decide how to determine what kinds of deliverables are required to have/add lower bounds testing, vs how to identify deliverables where it doesn't make sense15:49
*** timburke_ has quit IRC15:49
gmannthat is true in many other testing also, not all  projects test also defined pti15:49
yoctozeptolet's recap what we know15:49
yoctozepto1) l-c testing was largely broken15:49
yoctozepto2) we survived15:49
yoctozeptoso?15:49
yoctozeptono need to policy if not required :D15:50
mnaseri think we should revisit this next week15:50
mnaseri'd like sometime to chat over the next topic.15:50
fungiit's not like upper-constraints which is centrally maintained, lower bounds are different for every project and not always trivial to identify, i'm unconvinced that it makes sense to start forcing it on project teams who don't see value in it15:50
*** timburke_ has joined #openstack-tc15:50
mnaseror we keep discussing this15:50
mnaserand move the rest of topics next week15:50
mnaserbut yeah15:50
gmannok for next week as next topic is more important15:50
yoctozeptoperhaps it's good to vocalize on ptg15:50
jungleboyjyoctozepto:  ++15:51
mnaser#topic PTL assignment for Xena cycle leaderless projects (gmann)15:51
*** openstack changes topic to "PTL assignment for Xena cycle leaderless projects (gmann) (Meeting topic: tc)"15:51
mnaser#link https://etherpad.opendev.org/p/xena-leaderless15:51
gmannWe have 4 project left as leader-less and 4 project as late candidacy15:52
gmannbetter than last cycle i think15:52
yoctozepto(let's keep retiring and it will get better and better, yes)15:53
jungleboyjThat is better.15:53
ricolinIt is15:53
gmannout of first 4, Mistral might go with DPL as discussed preciously15:53
yoctozeptovery well15:53
redrobotI volunteer as tribute for Barbican.15:53
yoctozeptoyou are too kind15:53
spotz:)15:53
jungleboyj:-)15:53
gmannnice15:53
ricolin:)15:53
* redrobot was not paying attention to PTL nomination deadline.15:53
fungiredrobot: i your defense, we didn't provide as many warnings it was coming up as we have in past cycles15:54
gmannI can reach out to Mistral team for DPL model15:55
yoctozeptogmann: should we then move mistral to dpl in the whiteboard?15:55
fungiwe actually ended up with a lot fewer "leaderless" results than in past cycles15:55
yoctozeptogmann: ack15:55
gmannyoctozepto: let's check with them on required liaison list or so15:55
redrobotfungi 😅15:55
yoctozeptogmann: yeah, I figured from your subsequent message15:55
gmannbasically we need to decide on Keystone and Zaqar15:56
jungleboyjWow.  Keystone ...15:56
gmannZaqar seems not active in last cycle15:56
spotzYeah my feelings too jungleboyj15:56
gmannmay be we can get release team input also if they are doing wallaby release or not15:56
fungiknikolla was suggesting dpl for keystone15:57
yoctozeptozaqar is not deployable by kolla nor charms15:57
yoctozeptoI think tripleo and osa do deploy it though15:57
jungleboyjOk.  I assume there is still enough activty there to spread out the responsibility?15:58
jungleboyjSomeone go find Brant Knudson15:58
yoctozeptoI agree with gmann that Zaqar is likely 5 - bye-bye for now15:58
fungifor keystone? i don't get the impression keystone is dead, at least, they're on top of vulnerability reports from my vmt perspective15:58
gmannyeah, I will ping release team on Zaqar release status15:59
gmannagree on keystone, it is active project just no PTL15:59
jungleboyjfungi:  Yeah.  If knikolla is recommending depl, that seems fine.15:59
yoctozeptohttps://review.opendev.org/q/project:openstack/releases+zaqar15:59
gmannyoctozepto: thanks15:59
yoctozeptonothing in wallaby whatsoever16:00
gmannyeah16:01
belmoreiraanother important data point is also to understand if the project is actually used16:02
gmannyeah, good point16:03
gmannmay be we can check latest user survey data16:04
jungleboyjMakes sense.16:04
yoctozeptoyeah, on that note I already wrote regarding deployment tools16:05
gmannwe are out of time anyways. we can keep discussing it on etherpad or after meeting16:06
yoctozeptothere was not enough steam to even add it in kolla and charms :/16:06
ricolinProject like Heat use Zaqar to impl. singal, will be great to send them some notify if we gonna remove Zaqar16:06
yoctozeptoricolin: that's interesting16:06
knikollao/ sorry i'm late16:07
ricolinyoctozepto, not hard dependency, just provide it as one of singal backend16:07
ricolinI mean from heat side16:07
ricolinknikolla, o/16:07
yoctozeptoricolin: yeah, I've done a quick read16:07
yoctozeptothey should be happy to maintain less code :-)16:07
yoctozeptohi knikolla16:08
yoctozeptooh, we are past time indeed16:08
spotzNot too badly16:08
yoctozeptoif knikolla could say a word about keystone governance model16:09
yoctozeptowe would have a (almost) complete set of information16:09
jungleboyj\o/16:09
knikollaNone of the cores has reached out to me showing interest in taking over as PTL16:10
knikollaAnd pretty much everyone has cycled through the role (or is ptl of some other project)16:10
yoctozeptoduh16:10
spotzMaybe ping them? They might be too shy to step up?16:11
gmannohk, how about DPL model? anyone interested in that or something you have discussed in keystone meeitng or so16:11
fungispeaking from experience, it takes a lot of convincing for a former ptl to come out of retirement16:12
spotzI was thinking more the cores16:12
knikollaI don’t think it’s a question of shyness16:12
yoctozeptogmann: hberaud said mistral is not releasing either16:12
fungispotz: he was saying basically all the keystone cores are also former keystone ptls16:12
yoctozepto++16:13
gmannyoctozepto: yeah but as per Renat (former PTL) he is ok to help on that16:13
spotzAhhh16:13
yoctozeptogmann: ahh, ack!16:13
bnemecI get the impression that everyone is being pulled in other directions and doesn't feel like they have the time to commit to being PTL.16:13
* bnemec sympathizes16:13
jungleboyjbnemec:  ++16:13
yoctozeptoI could not agree more16:14
knikollaI’ll ping the cores privately before Tuesday’s meeting, for a final attempt16:14
knikollaOthwerise, I guess DPL will be it.16:14
gmann+116:15
gmannthanks knikolla16:15
yoctozepto++16:15
gmannmay be we should end meeting16:15
yoctozeptoall right, I think we have gathered all we could16:15
gmannmnaser: ?16:15
yoctozeptomy thoughts exactly16:16
mnasersorry, yes16:16
mnaser#endmeeting16:16
*** openstack changes topic to "OpenStack Technical Committee office hours: Tuesdays at 09:00 UTC, Wednesdays at 01:00 UTC, and Thursdays at 15:00 UTC | https://governance.openstack.org/tc/ | channel logs http://eavesdrop.openstack.org/irclogs/%23openstack-tc/"16:16
openstackMeeting ended Thu Mar 11 16:16:05 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-03-11-15.00.html16:16
jungleboyj:-)16:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-03-11-15.00.txt16:16
gmannyoctozepto: +1, good progress and discussion16:16
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-03-11-15.00.log.html16:16
fungiat some point the tc needs to come to a decision on what to do about the vacant seat16:16
yoctozeptogmann: :-)16:16
* fungi waves his election official hat around one more time16:16
yoctozeptofungi: spotz nominated herself late iirc16:17
fungiyep16:17
yoctozeptook16:17
fungiclosest thing in the tc charter which addresses it says that if all else fails, a special election is conducted to fill a vacancy16:17
yoctozeptohmm16:18
yoctozeptoI guess this is the first time such a thing happened16:18
jungleboyjCan we take a poll on spotz  ?16:18
fungiit may make sense to apply that rule, and then once there's a full compliment of tc members, start talking about shrinking the number of seats further16:18
jungleboyjThat is special.16:18
jungleboyjfungi:  ++16:18
spotzI was just an airhead and forgot to coo it16:19
yoctozeptofungi: tbh, 9 sounds like a decent number to have lively discussions16:19
fungihardly an airhead, you were busy. i think everyone here is familiar with that16:19
yoctozeptoyeas, I sympathise as well16:20
*** jamesmcarthur has quit IRC16:28
*** jamesmcarthur has joined #openstack-tc16:30
*** belmoreira has quit IRC16:53
*** belmoreira has joined #openstack-tc17:06
*** diablo_rojo has joined #openstack-tc17:20
lbragstadsomeone pinged me here a few days about the keystone PTL thing and i'm just getting around to following up,17:35
fungilbragstad: tl;dr is if you want it, it's probably yours! ;)17:36
lbragstadmost of my focus is on getting other openstack projects to retrofit their policy to work with newer keystone constructs, and it takes up most of my time17:36
lbragstadeven with the lower bandwidth keystone requires, i don't think i'd have the ability to step into the role again and give it the attention it deserves :(17:36
fungiyeah, i think the main question now is does keystone want to pivot to distributed leadership, and if so does it have volunteers for the various roles defined in the dpl resolution17:37
* lbragstad nods17:37
gmannyeah at least three liaison DPL model need17:38
jungleboyjlbragstad:  Thanks for the input.17:43
*** andrewbonney has quit IRC18:12
*** ralonsoh has quit IRC18:48
*** jamesmcarthur has quit IRC18:52
*** jamesmcarthur has joined #openstack-tc18:55
openstackgerritGhanshyam proposed openstack/governance master: Appoint Shengqin Feng as Zun PTL  https://review.opendev.org/c/openstack/governance/+/78006719:13
openstackgerritGhanshyam proposed openstack/governance master: Appoint XueFeng Liu as Senlin PTL  https://review.opendev.org/c/openstack/governance/+/78006819:17
openstackgerritGhanshyam proposed openstack/governance master: Appoint Martin Chacon Piza as Monasca PTL  https://review.opendev.org/c/openstack/governance/+/78007019:20
openstackgerritGhanshyam proposed openstack/governance master: Appoint Xinran Wang as Cyborg PTL  https://review.opendev.org/c/openstack/governance/+/78007119:25
openstackgerritGhanshyam proposed openstack/governance master: Appoint Douglas Mendizábal as Barbican PTL  https://review.opendev.org/c/openstack/governance/+/78007219:29
*** belmoreira has quit IRC19:31
*** belmoreira has joined #openstack-tc19:31
*** e0ne has joined #openstack-tc19:45
*** jamesmcarthur has quit IRC19:47
*** jamesmcarthur has joined #openstack-tc19:48
*** jamesmcarthur has quit IRC19:53
*** e0ne has quit IRC20:36
*** slaweq has quit IRC20:56
*** e0ne has joined #openstack-tc21:06
*** belmoreira has quit IRC21:23
*** smcginnis has quit IRC23:04
*** smcginnis has joined #openstack-tc23:15
*** jamesmcarthur has joined #openstack-tc23:16
*** e0ne has quit IRC23:16
*** diablo_rojo has quit IRC23:16
*** smcginnis has quit IRC23:28
*** diablo_rojo has joined #openstack-tc23:32
*** jamesmcarthur has quit IRC23:41
*** timburke_ has quit IRC23:45
*** jamesmcarthur has joined #openstack-tc23:52
*** jamesmcarthur has quit IRC23:57

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