Thursday, 2020-12-17

*** tosky has quit IRC00:01
*** ricolin_ has joined #openstack-tc00:44
*** evrardjp has quit IRC01:24
*** knikolla has quit IRC01:24
*** mnasiadka has quit IRC01:24
*** diablo_rojo_phon has quit IRC01:24
*** jbryce has quit IRC01:24
*** jroll has quit IRC01:24
*** evrardjp has joined #openstack-tc01:30
*** knikolla has joined #openstack-tc01:30
*** diablo_rojo_phon has joined #openstack-tc01:30
*** mnasiadka has joined #openstack-tc01:30
*** jbryce has joined #openstack-tc01:30
*** jroll has joined #openstack-tc01:30
*** timburke has joined #openstack-tc01:48
*** timburke has quit IRC01:56
*** abhishekk has quit IRC02:03
*** pojadhav has quit IRC02:04
*** pojadhav has joined #openstack-tc02:06
*** ricolin_ has quit IRC02:35
*** abhishekk has joined #openstack-tc05:05
*** timburke has joined #openstack-tc05:29
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-tc05:33
*** ralonsoh has joined #openstack-tc07:14
*** slaweq has joined #openstack-tc07:34
*** slaweq has quit IRC07:38
*** belmoreira has joined #openstack-tc07:46
*** slaweq has joined #openstack-tc07:50
*** slaweq has quit IRC08:01
*** slaweq has joined #openstack-tc08:08
*** andrewbonney has joined #openstack-tc08:11
*** tosky has joined #openstack-tc09:12
*** tosky has quit IRC10:47
*** tosky has joined #openstack-tc10:47
*** lbragstad has quit IRC10:52
*** lbragstad has joined #openstack-tc10:55
*** rpittau|afk is now known as rpittau10:59
*** ricolin has quit IRC11:00
*** e0ne has joined #openstack-tc11:02
*** lbragstad has quit IRC11:38
*** lbragstad has joined #openstack-tc11:42
*** e0ne has quit IRC13:16
*** e0ne has joined #openstack-tc13:22
*** dklyle has quit IRC14:19
*** lbragstad has quit IRC14:21
*** lbragstad has joined #openstack-tc14:23
*** diablo_rojo has joined #openstack-tc14:57
mnaser#startmeeting tc15:00
openstackMeeting started Thu Dec 17 15:00:00 2020 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 rollcall15:00
*** openstack changes topic to "rollcall (Meeting topic: tc)"15:00
mnasero/15:00
belmoreirao/15:00
gmanno/15:00
diablo_rojoo/15:00
mnaser#topic skipping next meetings15:01
*** openstack changes topic to "skipping next meetings (Meeting topic: tc)"15:01
mnaseri forgot to update the wiki on this, but i assume we're all okay with skipping the 2 upcoming meetings?15:02
belmoreira+115:02
mnaseri'll gladly run it on the 24th and 31st if anyone really wants to be there ;)15:02
mnaserso i guess in that case, we're probably going to skip those and meet again on january 7th15:03
gmannI can but as most of us will not be available so I think skip is fine.15:03
gmann+115:03
mnasercool cool cool15:03
mnaser#action mnaser send out email about skipping both upcoming meetings15:03
jungleboyj+115:04
mnaser#topic Follow up on past action items15:04
*** openstack changes topic to "Follow up on past action items (Meeting topic: tc)"15:04
mnaser#link http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-12-10-15.01.html15:04
mnasermnaser send email to ML to find volunteers to help drive goal selection15:04
mnaserso i sent that email out15:05
mnaserabotu the idea of a stabilization cycle15:05
mnaserno one seems to be strongly opposing it :)15:05
jungleboyj:-)15:05
mnaser#action mnaser write a proposed goal for X about stabilization/cooldown15:06
mnaseri'll push up something about that15:06
gmann+115:06
diablo_rojoWhy would people oppose stabilization? :)15:06
mnaserdiablo_rojo: mOvE fAsT aNd BrEaK tHiNgS15:06
jungleboyjI think we all need a bit of stability right now.15:06
mnaser:P15:06
mnasernext up, we had: gmann complete retirement of searchlight & qinling15:06
diablo_rojojungleboyj, lol +215:06
gmannboth are done, repo cleanup, project-config and  governance patches are merged. few usage patches on kolla side etc are left because their CI is broken currently. they can be merged as soon as their CI is green.15:07
mnaserok that's cool, so shall we keep this as an action item to keep following up or just consider it done?15:07
mnaseryour call gmann :)15:07
gmannwe can consider as done, I will follow on recheck those once CI is back15:08
mnasercool cool, ty15:09
mnasernext up, diablo_rojo complete retirement of karbor15:09
diablo_rojoGetting there. I have the bulk of things done - just a couple kolla and kayobe patches left I think.15:09
diablo_rojoThings are starting to merge.15:09
diablo_rojoDefinitely want to keep this action item lol15:10
mnaserhaha, got it, sounds good15:10
mnaser#action diablo_rojo complete retirement of karbor15:10
diablo_rojoBut waaaaay more progress than our last time touching base15:10
mnaser\o/ awesome, ping me if you need any project-config patches to land15:10
mnaserand finally, mnaser work to find time for community deployment projects + centos/rdo team15:10
mnaseri reached out to apevec and working on setting that up though most likely it'll be happening next year cause its too close to holidays now15:11
diablo_rojomnaser, I think there are a couple.15:11
mnaserdiablo_rojo: send em my way whenever :)15:11
diablo_rojoSounds good.15:11
diablo_rojowill do.15:11
mnaserok cool, so next up15:11
mnaser#topic Audit SIG list and chairs (diablo_rojo)15:11
*** openstack changes topic to "Audit SIG list and chairs (diablo_rojo) (Meeting topic: tc)"15:11
mnaser#link https://governance.openstack.org/sigs/15:11
diablo_rojoOh yeah. So, this list is suuuuuper out of date so I was going to go and email the discuss list about each of them encouraging them to update details- specifically chairs.15:12
diablo_rojoI know a lot of these people aren't active anymore and so we should get new chairs in place or look at retiring the sig15:12
diablo_rojoor hibernating it or whatever15:12
diablo_rojoSo I guess thats another action item for me15:13
mnaseri think that'll be really useful15:13
jungleboyjThat is a good idea.15:13
gmannwhat all SIG ?15:13
jungleboyjThis does look really old.15:13
mnasergmann: a lot of sigs seem to not be so active and/or chairs arent around15:13
gmannif any SIG are complete their purpose then  we move them to advisory state15:14
gmannotherwise close15:14
diablo_rojogmann, most of them aside from like.. a handful- scientific, first cotnact, TaCT, Large Scale are all probably fine.15:14
diablo_rojogmann, yeah I plan to start those conversations15:14
gmann+1, we can check and then move their state15:15
mnaser#action diablo_rojo reach out to SIGs/ML and start auditing states of SIGs15:15
gmannI think even we close them we keep them in doc for refence15:15
diablo_rojogmann, I would agree15:15
diablo_rojoin case someone wants to revive it down the road15:15
gmannyeah15:15
jungleboyjThat sounds good.15:15
mnasercools15:16
gmannI cannot find such example in site now but I am sure we have in SIG repo code somewhere15:16
mnaseri think once we start hitting that problem, we can discuss on the best way of moving it/archiving it15:16
diablo_rojo+215:16
mnasercool, next up15:17
mnaser#topic Annual report suggestions (diablo_rojo)15:17
*** openstack changes topic to "Annual report suggestions (diablo_rojo) (Meeting topic: tc)"15:17
diablo_rojoAlso me lol15:17
diablo_rojoits the diablo_rojo show today15:17
diablo_rojoSo mnaser and I are working on the annual report for openstack.15:18
diablo_rojoIf there are any specific ideas you think we should include, please send them our way15:18
diablo_rojoonce its mostly written we will send around a draft before submitting it15:18
gmanndiablo_rojo: mnaser this is process on retiring the SIG https://governance.openstack.org/sigs/reference/sig-guideline.html#retiring-a-sig15:19
gmann#link https://governance.openstack.org/sigs/reference/sig-guideline.html#retiring-a-sig15:19
diablo_rojogmann, oh cool! thanks :)15:19
mnaseroh that's neat to add later15:19
mnaseralso wrt to the annual report stuff, yeah, appreciate any info to tack onto it15:20
mnaserok cool15:21
mnaserthats fiar15:21
mnaserwell next15:21
mnaser#topic X cycle goal selection start15:21
*** openstack changes topic to "X cycle goal selection start (Meeting topic: tc)"15:21
* jungleboyj stabilized15:21
mnaseri think that has to go with the action item that i had above15:21
gmannyeah this can be removed now15:21
mnasercool, we can keep track of it in the AI15:21
gmann+1 that's better15:22
mnaser#action mnaser drop X cycle goal selection start from agenda15:22
mnaser#topic Audit and clean-up tags (gmann)15:22
*** openstack changes topic to "Audit and clean-up tags (gmann) (Meeting topic: tc)"15:22
gmannI started ML on API tag15:22
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019505.html15:22
gmannlet's see how many projects start that but it might be after holiday15:22
gmannI will continue on other tag audit in parallel15:23
mnaserok cool, that seems reasonable15:23
mnasershould we remove those sub items in there in the meantime too?15:23
gmannyes those can be removed and I will update next tag for next meeting15:24
mnasergmann: mind doing that when you update for next tag for next meeting?15:24
gmannsure15:24
mnaser#action gmann continue to audit tags + outreach to community to apply for them15:25
mnaser#topic X cycle release name vote recording (gmann)15:25
*** openstack changes topic to "X cycle release name vote recording (gmann) (Meeting topic: tc)"15:25
gmannshould we close this as votes are recorded in ML but only 4 out of 6.15:26
mnaseryeah, i guess that's ok at this point15:26
mnaser#action mnaser drop X cycle release name vote recording15:26
mnaser#link http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019337.html15:27
gmannI thinks getting votes from all community members is easy process than getting from TC15:27
jungleboyj:-(15:27
mnaseri agree15:27
mnaser*shrug*15:27
gmannanyways something we can discuss later in next meeting or so when all members are here15:28
mnaseryeah15:28
mnaser#topic CentOS 8 releases are discontinued / switch to CentOS 8 Stream (gmann/yoctozepto)15:28
*** openstack changes topic to "CentOS 8 releases are discontinued / switch to CentOS 8 Stream (gmann/yoctozepto) (Meeting topic: tc)"15:28
mnaseris there anything to discuss on this at this point from a tc level?15:28
mnaserwe have an action item to get the community to get together and i trust that the QA team is donig the right hing15:29
jungleboyjMan, this has caused a lot of frustration in general.15:29
gmannI do not think so, in devstack we are trying to get centos stream job working15:29
gmannjungleboyj: yeah I agree15:29
mnaseryeah i think that's a whole another discussion we can have15:30
mnaseri dont particularly agree with the source of the frustration15:30
mnaserbut that's another discussion to have :P15:30
mnaserwe can probably drop this from our list?15:30
jungleboyjmnaser:  Agree.15:30
gmannyeah. +1 on dropping from our list15:30
*** ricolin has joined #openstack-tc15:31
mnasercoools15:31
mnaser#action mnaser remove centos 8 topic from upcoming agenda15:31
mnaser#topic open reviews15:31
*** openstack changes topic to "open reviews (Meeting topic: tc)"15:31
mnaserhttps://review.opendev.org/q/projects:openstack/governance+is:open15:31
mnaser#link https://review.opendev.org/q/projects:openstack/governance+is:open15:31
mnaseronly main thing is15:33
mnaser#link https://review.opendev.org/c/openstack/governance/+/75990415:33
mnaserwhat can we do to help merge this?  or maybe get it in a minimal merge state and then allowing us to amend thing to it later?15:33
gmannmy -1 is mainly on python-*client stands where we create again confusion on what direction we should do15:33
gmannfor OSC, projects side point sicne starting was what to do with existing python-*client which is still unclear in this resolution15:34
gmannthat is why i think we should have some technical debt first and get agreement on that.15:35
mnaseri think the main point of the change at the time that projects SHOULDNT do things like remove osc usage and replace it by python-*client15:35
mnaserand more in general try to aim to make osc to have feature parity if not .. better?15:36
gmannyeah that we can make resolution saying these ^^ and leave technical details like 'remove the python-*client'15:37
gmannif resolution talk about these two part then I am good15:37
gmann* technical details like 'remove the python-*client which lead the discussion on how sdk python binding should be done15:38
jungleboyjI am ok with that.15:38
fungithis discussion also conflates openstackclient with openstacksdk, fwiw15:38
gmannbecause Tom raised good point on standalone service client15:39
mnaserstandalone service clients can make sense if they somehow find a way to be 100% feature parity (i think ironic does something like this)15:40
mnaserbut tbh when you enter the domain of two different implementations, that's just doing our users a disservice15:40
jungleboyjDual maintenance.15:41
jungleboyjIf there is parity then we don't have to have them removed but it leave room for confusion/mistakes.15:42
belmoreirawhat's the advantage to not remove them?15:43
belmoreirafor a simple user that would be very confusing15:44
belmoreiralike today15:44
fungione advantage is stand-alone projects may not want to force users to install a heavyweight client/sdk to interact with just their service15:44
gmannstandalone is one oint15:44
gmannpoint15:44
gmann#link https://review.opendev.org/c/openstack/governance/+/759904/7/resolutions/20201028-openstackclient-tc-policy.rst#1115:44
belmoreirafungi gmann true15:45
fungibut that's ultimately a tension between the view that openstack should be one big consistent system vs a federation of compatible but separate solutions15:45
fungiit's tough to reconcile those with a single approach to interfaces (for example would you use horizon as a webui for standalone swift?)15:46
gmannwe also provide the standalone tag for services and operator to choose those #link https://governance.openstack.org/tc/reference/tags/assert_supports-standalone.html15:46
gmannso that point we should consider on removing the python-*client15:46
fungione (very labor intensive so unlikely) solution could be to reimplement te individual clients on top of openstacksdk15:48
fungiat least the command-line part of them (so basically a compatibility shim to the standalone client syntax where possible)15:51
ricolindo we have stand along service who already said they prefer not doing anything to force users to install a heavyweight (which I don't think it's heavy:) ) client/sdk?15:52
gmannricolin: that is the point from manila team  #link https://review.opendev.org/c/openstack/governance/+/759904/7/resolutions/20201028-openstackclient-tc-policy.rst#1115:53
gmannand other projects like ironic,  have not opinioned on this yet15:54
fungiagain, the situations with openstackclient and openstacksdk, while related, are a little different at the moment15:55
ricolinright, from gouthamr15:55
*** dklyle has joined #openstack-tc15:56
fungiremember that for now openstackclient still relies on (almost?) all of the individual service client libraries along with depending on openstacksdk15:56
fungithat's not the end goal, but it's a present reality15:57
jungleboyjReading over those comments it seems that the main concern is with us making a stance on removal.  I am ok with softening out stance in the interest of making progress.15:57
jungleboyjRemoval of the python-*client15:57
fungiso openstacksdk is remarkably lightweight, openstackclient is a massive grab-bag of dependencies15:58
ricolinjungleboyj, +1 as the first step in road to push/encourage projects start this task15:58
jungleboyj:-)15:59
gmannyeah, if we talk on moving to osc and not updating doc etc not to use osc, basically two point mnaser mentioned above then it is ok.15:59
jungleboyj++16:00
ricolin++16:00
gmannand leave the implementation detail on python binding and removal or python-*client for sdk and projects team side16:01
gmannat least before TC decide any resolution on that part.16:02
mnaseri think we'll keep the discussion going....16:02
mnaser#endmeeting16:02
*** 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:02
openstackMeeting ended Thu Dec 17 16:02:32 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-12-17-15.00.html16:02
mnaserbut will end for now16:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-12-17-15.00.txt16:02
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-12-17-15.00.log.html16:02
fungion the earlier topic of sig health, the security sig is probably also fine by the tc's definition. the chair is still around and engaged in the community and holds irc meetings almost weekly, though these days it's almost exclusively vmt-related discussion16:05
ricolinfungi, that's good to know16:06
fungiwe've also fairly consistently had at least one security sig block at every ptg16:07
fungiand some activity in the #openstack-security irc channel (though again it's mostly public vulnerability management discussions)16:08
gmannI think we should re-iterate the active criteria for SIG current it is regular meeting etc16:08
gmannlike some ML update or PTG gathering should be enough and as along as chair and co-chair is reachable16:08
gmannricolin ^^ you are the right person on this16:09
fungiwell, we previously said there just needed to be some regular activity reporting from each sig. that could be periodic irc meeting minutes, or quarterly summaries posted to the ml, ot update presentations at summit, et cetera16:09
gmannfungi: +1, much active than most of other SIG16:09
fungiyeah, so anyway i agree that the activity reporting expectations are sufficiently loose already16:10
fungibasically the tc should be able to look in a few places and quickly determine that the sig is alive16:10
ricolinfungi, we have work on renew the SIG status base on SIG's suggestion an year ago16:11
ricolinmaybe we can do it again16:11
fungiare there recent meeting minutes on eavesdrop? alive. did someone post a summary to the ml in the past few months? alive. was there a presentaiton at the summit? alive...16:12
gmannyeah16:12
fungiricolin: totally, it's good to look through the list and determine which ones have ceased to gather and collaborate on anything, and clean them from the list of sigs or at least update their status column to something like "defunct"16:14
ricolinI can help to reach out to SIGs on ML/private mail to check their current status, or are you suggest TC should step in and make the call?16:14
ricolinfungi, ^^^16:14
fungialso some of the nascent sigs which were added to the list don't appear to have materialized16:14
gmannwe can choose one of the defined status - https://governance.openstack.org/sigs/reference/sig-guideline.html#keeping-sig-status-up-to-date16:15
fungiricolin: well, sigs are under the governance of the tc now (since absorbing the uc), so it's up to the tc or their delegates in the meta sig to decide which sigs are listed16:16
fungipresumably the tc would rely on the meta sig to take care of it16:16
ricolinfungi, there's no meta sig anymore FYI16:17
fungibut at this point the role of the meta sig is itself a little redundant because it's no longer a proxy for shared tc/uc oversight16:17
gmannwe can consider the SIG status check or retirement same way as prjojects16:17
fungiaha, then yes the tc16:17
ricolineverything point to tc now16:17
gmannyeah16:18
ricolingmann, +116:18
ricolinI probably to it tomorrow or early next week16:23
ricolins/to/do/16:24
*** belmoreira has quit IRC17:10
*** ralonsoh has quit IRC17:23
*** e0ne has quit IRC17:39
smcginnistc-members: I have gotten word back from the Foundation on the vetting for the X release name.18:01
fungi*drumroll*18:02
smcginnisAs brought up here, it did turn out there were issues with the top pick of Xanadu.18:02
smcginnisThe second place name of Xena was good though.18:02
smcginnisSorry Olivia Newton John.18:02
fungioh, cool, for some reason i misheard wes and thought he was saying the first five or so selections all had problems18:02
smcginnisBefore I sent any kind of announcement on this, since there were some... issues... with the polling, I wanted to get the OK from the TC before announcing anything.18:03
smcginnisfungi: This is what I received: "We've run the checks on our end and it looks like "Xena" is the best bet for this release."18:03
fungicool, thanks for distilling it!18:11
gmannsounds good. +118:17
*** rpittau is now known as rpittau|afk18:20
jungleboyjsmcginnis:  THanks for the update!  Sounds good to me.18:29
jungleboyjThank goodness I don't have to have Xanadu going through my head for the next 6 months.18:30
fungii can totally still make that happen you know18:30
jungleboyjPlease sir. No.18:30
fungigranted it might contravene some international treaties18:31
jungleboyj:-)18:31
fungisounds like a challenge to up my rickrolling game18:32
*** andrewbonney has quit IRC19:11
*** timburke has quit IRC19:55
*** e0ne has joined #openstack-tc20:05
*** slaweq has quit IRC20:59
*** e0ne has quit IRC21:09
*** e0ne has joined #openstack-tc21:11
*** e0ne has quit IRC21:11
*** slaweq has joined #openstack-tc22:20
*** slaweq has quit IRC22:33
*** lbragstad has quit IRC23:18
*** timburke has joined #openstack-tc23:38
*** tosky has quit IRC23:43

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