Thursday, 2021-07-01

*** diablo_rojo is now known as Guest107202:58
*** pojadhav- is now known as pojadhav04:41
*** gthiemon1e is now known as gthiemonge06:31
*** akekane_ is now known as abhishekk06:32
*** gthiemon1e is now known as gthiemonge07:18
*** slaweq_ is now known as slaweq08:29
*** pojadhav- is now known as pojadhav10:40
*** pojadhav- is now known as pojadhav12:54
*** yoctozepto[m] is now known as Guest116713:05
*** diablo_rojo__ is now known as diablo_rojo14:10
* mnaser half around today, it's a national holiday14:59
jungleboyj:-)14:59
gmanntc-members: meeting time14:59
* jungleboyj starts singing "Oh Canada ..."14:59
gmann#startmeeting tc15:00
opendevmeetMeeting started Thu Jul  1 15:00:04 2021 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
jungleboyjo/15:00
gmanno/15:00
mnaser(kinda here :])15:00
ricolino/15:00
yoctozeptoo/15:00
belmoreirao/15:00
* dansmith is here but not really15:00
* gmann ah remember now its holiday today here :)15:00
gmann#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions15:01
gmannthis ^^ is today agenda15:01
gmannlet's start15:01
gmann#topic Follow up on past action items15:01
gmannno action item from previous meeting15:02
gmann#topic Gate health check (dansmith/yoctozepto)15:02
gmannany news on gate health 15:02
spotzo/15:02
jungleboyjThe Cinder team has a couple of patches for the LVM crashes that are up and have been merged.15:03
jungleboyjContinue to work those.15:03
mnasersweet15:03
gmannnice15:03
yoctozeptoI haven't heard complaints recently15:03
gmannone I remember is live migration tempest test failure which is fixed now.15:03
jungleboyj:-)15:04
gmannthanks jungleboyj for updates15:04
jungleboyjgmann:  Welcome.15:04
gmannanything else on Gate status side?15:04
gmann#topic Migration from 'Freenode' to 'OFTC' (gmann)15:05
diablo_rojoo/15:05
gmann#link https://etherpad.opendev.org/p/openstack-irc-migration-to-oftc15:05
jungleboyjNothing from me.15:05
gmanni do not have any progress in this week. I will do next week for remaining project side doc update15:06
gmann#topic Governance non-active repos retirement & cleanup15:06
gmann#link https://etherpad.opendev.org/p/governance-repos-cleanup15:06
gmannall the patches are merged now in this and cleanup is completed 15:06
gmannI will remove this from next meeting agenda15:06
jungleboyj\o/15:07
gmann#action gmann to remove Governance non-active repos cleanup topic from agenda15:07
gmannif we find any other repo which needs to be merged/cleanup then we can do that later15:08
gmann#topic Election official assignments15:08
gmannwe have three proposed election official now15:08
gmann1. Belmiro: https://review.opendev.org/c/openstack/election/+/79882215:08
gmann2. Amy: https://review.opendev.org/c/openstack/election/+/79890715:08
gmann3. Helena: https://review.opendev.org/c/openstack/election/+/79872915:08
fungihuge thanks to the three of you for stepping up!15:08
gmannyeah, thanks belmoreira spotz helena15:08
gmannto merge these patches we need to merge this gate fix #link https://review.opendev.org/c/openstack/election/+/79891615:09
spotzMy pleasure:)15:09
gmanndiablo_rojo: ^^ can you check 798916 ?15:10
gmannwho is 2nd reviewer in elections repo? I think Ian ?15:11
gmannwe have spotz belmoreira also added 15:12
gmanncan you check this #link https://review.opendev.org/c/openstack/election/+/79891615:12
gmannor fungi ^^ 15:12
gmannhttps://review.opendev.org/admin/groups/208108b62745877449d8e6fce45f44e3cc013e8b,members15:12
belmoreirasure15:13
gmannthanks 15:13
spotzreviewed15:13
gmannonce this merge then we can recheck on other patches15:13
spotzwasn't suree if I should +w yet though15:13
gmannand on next election dates #link https://review.opendev.org/c/openstack/election/+/79871915:13
gmannyeah me too, may be diablo_rojo added you15:13
gmannI thought it will be after election official patch merge, but anyways.15:14
spotzShe did, but I tend to like 2 +2 if the repo is active15:14
gmannyeah15:14
gmannI commented on dates for next electrion to macth with our charter15:14
gmannand we need to wait until we have Y release name which might be next week as I received information from foundation on trademark check15:15
diablo_rojoDouble meetings, sorry. 15:16
jungleboyjgmann:  Any news on the naming? 15:16
diablo_rojoYeah I will take a look at the gate fix. 15:16
spotzI so want to call RC1 Baby Yoda:(15:16
gmannjungleboyj: yeah, next week we will get the trademanrk check by foundation 15:16
jungleboyjgmann:  Ok.  people have been asking.15:17
gmanndiablo_rojo: fungi belmoreira spotz just a question do we keep only current election official in core goups or is it fine to have previous ofificial also ?15:17
jungleboyjspotz:  I think that is unlikely.  :-(15:17
gmannjungleboyj: yeah, I am hoping by next week we should be ready15:17
diablo_rojogmann, I have periodically culled the group15:17
diablo_rojoI am not aggressive about removing people though15:18
spotzjungleboyj: hence the :( I'd be really surprised if we get to use Yoda. I think it'll be Yeti15:18
spotzYezh like Andy was still in there but I had only heard Ian mentioned15:18
fungiyeah, i have no need to be in the election officials team in gerrit, as i'm no longer an official15:18
diablo_rojofungi, I can remove you right now. 15:18
fungiespecially if we have several people in it now who can approve any tooling fixes i end up proposing15:18
gmannack, may be we can do once we merge the new election offiicals patches15:19
fungithanks diablo_rojo!15:19
diablo_rojo'free' you from the bonds of election officiating15:19
gmannthanks 15:19
gmannI will remove this topic from agenda for next meeting. 15:19
gmannanything else on this topic?15:19
diablo_rojofungi is freeeeeeeeeeee15:20
gmann#action gmann to remove election assignments topic form agenda15:20
gmanndiablo_rojo: hehe he never :) free form elections things may be15:20
diablo_rojoCurrent list- spotz andymccr, belmoreira, hspease, ianychoi and myself15:20
jungleboyj#freeFungi15:20
gmannone more things about election 15:20
diablo_rojojungleboyj, LOLOLOLOL15:20
gmannL65 in https://etherpad.opendev.org/p/tc-xena-tracker15:21
spotzBut then I'll be lonely!15:21
gmannspotz: belmoreira this is extra step for this election "One extra step here:  CIVS changed its policy on email communication in April 2021. To vote in private CIVS polls, Authorized voters must opt in to email communication from the service via https://civs1.civs.us/cgi-bin/opt_in.pl. We need to add this as a pre-step for the election once electorate are finalized. "15:21
gmannthat is what I did for TC votes on Y release name15:21
spotzYeah I rermember that from the naming election15:21
diablo_rojoOh nooooo15:21
fungiit took effect *immediately* (like a day or two) after we created the last tc/ptl polls15:22
diablo_rojothat is lucky. 15:22
gmannyeah15:22
fungii think it was right after the special tc election actually15:22
diablo_rojoYeah that sounds right15:23
diablo_rojoI don't recall doing extra stuff for that special election15:23
fungibecause i remember running into it when trying to resend a ballot to one voter while the poll was open15:23
spotzSo can we send a pre-voting opt-in like a week before?15:23
fungibut regardless, it means we need to talk about our options yeah15:23
gmannspotz: may be15:23
gmannk, may be you all can disucss it in election channel on how to do that but this is somehting we should figure out before we send the poll link15:23
gmannfungi: +115:24
belmoreirathanks gmann for the heads up15:24
fungilike announcing in various places that people who want to vote need to allow civs to e-mail them first15:24
fungior running our own copy of civs somewhere instead15:24
spotzI heard civs wasn't supported anymore?15:25
gmannyeah, let's discussed on detail after meeting or on election channel ?15:25
gmannnext topic is15:25
gmann#topic let's move to next topic15:25
gmannohh15:25
ricolinhaha:)15:25
gmann#topic Items for next Newsletter15:26
gmannwe have next month newsletter and need to put 2-3 items for news15:26
gmannricolin: Y release goal is added i previous newsletter right?15:26
ricolingmann, I don't think we do15:27
gmannits there15:27
gmann#link https://superuser.openstack.org/articles/inside-open-infrastructure-the-latest-from-the-openinfra-foundation-4/15:27
ricolinokay15:27
gmannwhat all items we can add ?15:27
opendevreviewMerged openstack/election master: Add election_results to cycle data  https://review.opendev.org/c/openstack/election/+/79891615:28
diablo_rojoWe can add the discussion of y goals to the newsletter again15:28
diablo_rojoeven if it was there before15:28
ricolinEOL ocata?15:28
spotzYeah cause the more ideas the better. I like the pain points one alot15:29
gmannsure, that will help +115:29
gmannocata EOl is good info,15:29
jungleboyjWould say add news about the naming but sounds like we won't have that in time?15:29
spotzI just EOLed Stein in some docs yesterday. 15:29
gmannjungleboyj: yeah15:29
gmannone item I think is adding pre-step for CIVS poll? we should wait until election officials finalize the mechanish of that.15:29
spotzOh good call gmann!15:29
gmannso that people can start it early15:30
spotzI would say give folks a heads up on the opt-in now and as many times as we can15:30
gmannyeah15:30
spotzJust a please be aware you willreceive an email in the coming weeks to opt-in15:30
gmannspotz: can you add some word and link in etherpad about it ?15:30
gmannand  we can also ask 'you can do it in advance also'15:31
gmannok so, 1. ocata EOl ricolin can you add15:31
ricolinyes15:31
gmannI will add Y goal again15:31
spotzyep15:31
gmanngreat thanks15:32
gmann#topic Open Reviews15:32
spotzthe tracker ether?15:32
gmannthis one https://etherpad.opendev.org/p/newsletter-openstack-news15:32
spotzthanks15:33
gmann#link https://review.opendev.org/q/projects:openstack/governance+is:open15:33
gmannthese are open reviews15:33
gmannI think all review has erquired vote but please review those if you have not15:34
gmannricolin: thanks for headup for js-openstack-lib retirement15:34
gmannthere are some comment on governance and project-config patches to address first 15:35
ricolingmann, NP, we still need ML from PTL15:35
gmannricolin: +1, thanks. 15:35
ricolinbut everything is there15:35
gmannthat's all I have for today, anything else we need to discuss ?15:36
ricolinyes15:36
ricolinJulia have an idea about to allow projects to have a community goal like aiming their/ops most painful issues15:37
ricolin#link http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023352.html15:38
ricolinwould like to hear from all of you15:38
jungleboyjSeems like a decent idea.15:38
gmannXena cycle also we had kind of similar? about stability of existing things.15:38
yoctozeptoI am also in favour15:39
spotzI like the pain pooints goal as already mentioned. I added the Inclusive Naming stuff so we can at least officially be planning on what next15:39
gmannwe have I think two more candidate for Y, tls and RBAC15:39
ricolinAs pre-selecting step, we might be able to make actions like- ask projects to provide information on what's ops's most painful part15:39
ricolingmann, yes15:40
gmannRBAC is also very imoportant for operator point of view15:40
gmannricolin: +115:40
gmannand we can collect the pain points in goal proposal first15:40
ricolingmann, but we said we gonna have 2 Y goals15:40
ricolinbut right now we're working on is to pre-selecting15:40
gmannricolin: it depends on what all goals and how much work needed15:40
spotzI'd second RBAC, we also need to help folks understand why it's important as I bet most folks don't even know about policy.yaml/jsoon15:40
*** pojadhav- is now known as pojadhav15:41
ricolingmann, that's the part I'm wondering15:41
gmannso we get the goals proposed in proposed dir and then we can weight on each goal while selecting 15:41
jungleboyjMakes sense.15:42
ricolin+115:42
gmannso let's start proposing/asking to propose as first step15:42
gmannI will do for RBAC before next meeting15:42
fungiprogress on rbac would be nice from the vmt's perspective. we keep getting vulnerability reports opened from people who have created "project admin" roles and don't realize that users in it are full admins of a lot of services15:42
ricolinSo maybe we make actions like "collect the pain points"?15:42
gmannfungi: yeah, good point. 15:42
gmannricolin: +1, to projects right?15:43
fungiright now the existing rbac half-implementation is an attractive nuisance15:43
ricolingmann, yes15:43
belmoreiraI like the idea about ops pain points, just wondering if devs have the same perception of pain points as ops. Who will provide the pain points?15:43
gmannyes and system admin has its own chanlange on project mapped resources15:43
jungleboyjbelmoreira:  Probably not, but that is why it would be good to get that feedback.15:43
gmannand especially for cross servier dependent resources, like system admin cannot create VM from nova but can create network from neutron15:44
gmannmaye be we can ask to add pain points in our goal backlog? there we have other pain points also which we plan to make goal15:45
gmann#link https://etherpad.opendev.org/p/community-goals15:46
dansmithdefinitely ++ from me for rbac15:46
* dansmith catches up15:46
ricolinbelmoreira, do raise a good question: where we can ask for feedback first?15:46
spotzbelmoreira: That might be a good initiative for thhe ops meetuo folks or atleast the channel, a livestream, the user serrver?15:46
spotzSorry if I type fast I don't fix the typos:)15:46
ricolinwe can ask project teams, and where else?15:46
spotzuser vervey..15:46
spotzgrr15:46
ricolingmann, +115:47
fungiuser oy vey15:47
jungleboyjspotz:  is typing like she just left the dentist.15:47
yoctozeptoI like verveys15:48
belmoreiraspotz yes, I think user survey is good 15:48
jungleboyjbelmoreira:  ++15:48
TheJuliaThe verveys feedback has never proven really useful, at least for ironic. Most comments have tended to not be constructive, and the overall process means that that the actual feedback is only after translation and review from the foundation which means we're talking next year if we want to use that as imput15:48
spotzI need a new keyboard, thhe Mac keybooards go weird on me after a yearr. This time quicker15:48
TheJuliaverveys++15:48
gmannok let's collect those pain points from all those channels/projects and add it in https://etherpad.opendev.org/p/community-goals15:49
fungiyes, the survey is great for making demographic profiles and statistics, less for identifying what bugs to fix15:49
gmannricolin: can you ask it on ML from projects/ops side ?15:49
ricolinyes15:49
jungleboyjIf nothing else, having a list of perceived pain points is useful.15:49
gmanngreat thanks15:49
fungithe ops sig should ideally be a great source of pain points15:50
gmann#action ricolin to ask for collecting the ops pain points on openstack-discuss ML15:50
gmannyeah, who is chair there?15:50
gmannah15:50
gmannlet's see if we have anyone coming up with help and then we can form15:51
belmoreirafungi the problem is that the participation is not that much15:51
gmann#action gmann to propose the RBAC goal 15:51
fungibelmoreira: yep, a separate problem also worth solving i suppose15:52
gmannanything on this topic or any other topic to discuss today?15:52
TheJuliaI wonder if openinfra.live would be willing to do an general operator roundtable, or maybe join the operators for an hour?15:53
spotzThat's what I was thinking above, the AMA15:53
belmoreiraand I'm sure mine pain points will be different from most operators15:53
gmann+115:53
fungiTheJulia: add it to https://ideas.openinfra.live/ !15:53
jungleboyj++15:54
gmann#link https://openinfrafoundation.formstack.com/forms/openinfralive15:54
belmoreiraTheJulia ++15:54
TheJuliafungi: that url is not accepting connections at this time15:55
ricolinbelmoreira, what potentially can do is collect pain points and allow project teams to select from15:55
gmannTheJulia: #link https://openinfrafoundation.formstack.com/forms/openinfralive15:55
fungiTheJulia: i just noticed, bringing it to the attention of the folks who run it15:56
spotzWe break all the things!15:57
gmann:)15:57
gmannthanks for all great discusison today and let's work on respective action items for various topic. 15:58
gmannif nothing else let's close the meeting15:58
fungiTheJulia: it's http sorry, https is apparently not implemented there15:58
gmannthanks all for joining15:58
spotzThanks gmann!15:58
gmann#endmeeting15:58
opendevmeetMeeting ended Thu Jul  1 15:58:29 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-01-15.00.html15:58
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-01-15.00.txt15:58
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-01-15.00.log.html15:58
TheJuliabelmoreira: would you be willing to join a round table?15:58
yoctozeptothanks gmann15:59
TheJuliaany other operators watching willing to join a round table?15:59
belmoreirasure, that would be great15:59
yoctozeptogmann: also, I will be on PTO the next two weeks, just so you know :-)15:59
jungleboyjThanks. 15:59
gmannyoctozepto: ack. thanks for update and enjoy the PTO. 16:00
spotzIf you want an ex-operator to help lead I can join Julia. We can use the ops meetup twitter to get the word out once scheduled16:00
spotzHave fun yoctozepto16:00
yoctozeptothanks gmann and spotz16:01
belmoreirathe Large Scale SIG can also be a good channel to make ops aware16:02
TheJuliaspotz: ack, /msg me your preferred email address16:02
fungibelmoreira: great idea, yep. sigs in general make good conduits since they're at least assumed to involve users/operators in many cases16:03
belmoreiraI can do mention it in the Large Scale and Scientific SIG16:05
gmannI think we need to make SIG more conencting to developers for such ops pain point/feedback from ops and community or vice versa 16:06
gmannso that it will continously help us on any improvement in software16:07
TheJuliabelmoreira: I'm going to submit it was is with a couple names, and note we're going to try and find some more people16:09
TheJuliaSome folks do need to get permission before speaking in the public view on their environment or issues encountered.16:10
spotzok opt-in blurb ccreated if anyone wants to chheck it out on the etherpad. I think it's typo free:)16:50
gmannspotz: thanks lgtm, how about adding link also there in case people can do this step in advance.17:42
spotzLet me look, I was on the site to get the wording17:43
gmannhttps://civs1.civs.us/cgi-bin/opt_in.pl17:44
spotzOh cool I didn't see that17:44
gmannthanks17:49
gmanndiablo_rojo: we are ready on newsletter content, in case you would like to inform foundation staff early than Monday https://etherpad.opendev.org/p/newsletter-openstack-news17:51
diablo_rojogmann, oh cool. 18:01
*** gthiemon1e is now known as gthiemonge19:05
clarkbgmann: Now that the ELK stuff has been brought up with the board I was thinking it would be a good time to think about checkpoints on that from the infra side. Is that something that I should add to next week's TC agenda?20:22
clarkbso far we've said that we aren't in a rush to turn it off (which is still the case) but yesterday we discovered the elasticsearch cluster had largely crashed and we weren't indexing anything.20:23
clarkbI don't think that means we're in a rush yet, but thinking about reasonable timelines to expect help and what to do if we don't etc is probably a good idea20:23
clarkbrelated to that I've disabled the indexer processes on 50% of our worker nodes to see if we can narrow down how many of them we need for our current workloads (since one of the concerns is resource consumption)20:24
clarkbso far the metrics we are gathering indicate turning off 50% might be too much but we need to get more data before we decide that20:25
clarkb(and they can be turned back on if necessary since I haven't deleted anything, just stopped processes)20:25
gmannyeah, I added that topic in morning - https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting20:25
clarkbthat was for today to give an update on what you talked to the board about right?20:26
gmannclarkb: we did not discussed it today as I was waiting from Board if any updates they have from their organizayion check. 20:26
gmannnext meeting is best time for that and we can discuss all the pointed you mentione also20:27
clarkbgot it. Do you mind if I add an item or two under that topic for next week?20:27
gmannpointy20:27
gmannclarkb: yes that will be great.20:27
clarkbcool I'll do that20:27
gmannthanks 20:27
gmannclarkb: having timeline is something we need at some point as Board asked about any deadline for shutdown. may be we can define something like next Y release or so if that is fine from infra/opendev team side 20:29
gmannotherwise without deadline, many people can interpret it as same as we are asking infra help since 3 years20:30
clarkbgmann: I mean we are asking for help because they dno't help :P20:30
clarkbbut I agree a timeline would be a good thing20:30
gmannyeah, let's discuss all those points in next meeting20:32
clarkbgmann: ok I posted some updates, feel free to edit or add to that20:33
gmannclarkb: looks good, updated the topic name to 'ELK services plan and help status'20:34
gmannclarkb: and i hope you will attend the meeting to decide timeline or so or fungi ?20:35
gmannas current maintainer input is needed20:35
clarkbyes, I'll plan to be there next week (Thursday at 15:00 UTC right?)20:36
gmannyeah 20:36
gmannI will ping also in case.20:36
clarkbthat would be great, thanks20:37
gmannthanks. 20:37
fungii'm also basically always around for the tc meeting20:38
gmann+120:39
fungiwhen i resolved not to run for a seat on the tc again, i made it a point to still stick around and participate as if i were still on the tc, at least as much as my available time allows20:47
fungiall of the opinions with none of the added responsibility ;)20:48
gmann'23:39

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