Thursday, 2021-01-21

*** jamesmcarthur has joined #openstack-tc00:11
*** jamesmcarthur has quit IRC00:40
*** ricolin_ has joined #openstack-tc02:14
*** lbragstad_ is now known as lbragstad02:15
*** pojadhav|away is now known as pojadhav03:47
*** ricolin_ has quit IRC04:20
*** ricolin has joined #openstack-tc04:24
*** ricolin has quit IRC05:11
*** ricolin has joined #openstack-tc05:24
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-tc05:33
*** lpetrut has joined #openstack-tc07:10
*** tkajinam_ has joined #openstack-tc07:19
*** jaosorior has quit IRC07:19
*** tkajinam has quit IRC07:20
*** ralonsoh has joined #openstack-tc07:41
*** slaweq has joined #openstack-tc07:58
*** e0ne has joined #openstack-tc07:58
*** rpittau|afk is now known as rpittau08:11
*** tosky has joined #openstack-tc08:16
*** andrewbonney has joined #openstack-tc08:24
*** lpetrut_ has joined #openstack-tc09:34
*** tosky has quit IRC09:36
*** tosky_ has joined #openstack-tc09:36
*** lpetrut has quit IRC09:37
*** tosky_ is now known as tosky09:43
openstackgerritHervĂ© Beraud proposed openstack/governance master: monasca-log-api & monasca-ceilometer does not make releases  https://review.opendev.org/c/openstack/governance/+/77178510:37
openstackgerritHervĂ© Beraud proposed openstack/governance master: js-openstack-lib does not make releases  https://review.opendev.org/c/openstack/governance/+/77178910:50
*** e0ne has quit IRC11:28
*** jaosorior has joined #openstack-tc11:45
*** ricolin has quit IRC12:06
*** tosky has quit IRC13:06
*** tosky has joined #openstack-tc13:06
*** ricolin has joined #openstack-tc13:08
*** rosmaita has joined #openstack-tc14:14
mnaser#startmeeting tc15:00
openstackMeeting started Thu Jan 21 15:00:24 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
mnaser#topic rollcall15: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
mnasero/15:00
jungleboyjo/15:00
*** openstack changes topic to "rollcall (Meeting topic: tc)"15:00
mnasertoo fast?15:00
dansmitho/15:00
mnaseropenstack is having a slow morning i guess15:00
gmanno/15:00
mnaserwell, we can get started15: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-01-14-15.00.html15:02
fungiirc is not 100% synchronous, so if messages lag between the server to which you're connected and the server to which the bot is connected, you'll see a delay in its responding15:02
*** rosmaita has left #openstack-tc15:02
mnaserfungi: so i guess i can add irc to 'asynchronous collaboration tools' :P15:02
mnaserok, so we have15:02
mnaserdiablo_rojo complete retirement of karbor15:02
mnaseri know there was a few patches left15:03
mnaser#link https://review.opendev.org/c/openstack/governance/+/76705615:03
mnaser#link https://review.opendev.org/c/openstack/project-config/+/76705715:04
mnaserlooks like we had a mishap with the rebase :) i'll keep it on the list15:04
mnaser#action diablo_rojo complete retirement of karbor15:04
mnasermnaser to remove proposed goal topic from agenda << gone15:04
mnaserdiablo_rojo reach out to SIGs/ML and start auditing states of SIGs << neither ricolin or diablo_rojo seem to be around right now, so i think we can follow up on this later15:05
mnaser#action diablo_rojo/ricolin reach out to SIGs/ML and start auditing states of SIGs15:05
mnasermnaser remove annual report suggestions from agenda << that's done15:05
mnaserdansmith update osc change to include ci/docs commentary < thats in https://review.opendev.org/c/openstack/governance/+/75990415:05
mnaserthanks dansmith for revising that, and it looks like we're on the right track, tc-members, please review ^15:06
mnasermnaser add openstack/infra-core as discussion topic in opendev meeting << done, will discuss later15:06
mnasergmann follow-up with zigo if debian uses l-c15:06
dansmithI just +1d, I was waiting until others had since I revised it latest15:06
gmannl-c thing we can discuss later, we have more response in ML15:07
mnaserok cool, perfect15:07
gmannlater in topic section15:07
*** rosmaita has joined #openstack-tc15:07
mnasergmann update supported distros to drop opensuse < has a discussion topic too, so perhaps we can keep it for that?15:07
gmannhttps://review.opendev.org/c/openstack/devstack/+/76988415:07
gmannsure15:07
mnasercool, tryingh to get through those so we can get to the discussions15:08
mnaser#topic Audit SIG list and chairs (diablo_rojo / ricolin)15:08
*** openstack changes topic to "Audit SIG list and chairs (diablo_rojo / ricolin) (Meeting topic: tc)"15:08
mnaserno updates that i've seen on this, unless i missed something on the ML, we can probably keep that for next time?15:08
gmann+115:09
mnaser#topic Add Resolution of TC stance on the OpenStackClient (diablo_rojo / dansmith)15:09
*** openstack changes topic to "Add Resolution of TC stance on the OpenStackClient (diablo_rojo / dansmith) (Meeting topic: tc)"15:09
mnasernot much to do about this anymore at this point I think, just need to get tc members to review the patch and land it15:09
mnaserso i think we can remove this topic for the future perhaps and keep it under the open reviews?15:10
gmannyeah15:10
mnaser#action mnaser drop "Add Resolution of TC stance on the OpenStackClient" from agenda15:10
mnaser#topic Gate performance and heavy job configs (dansmith)15:10
*** openstack changes topic to "Gate performance and heavy job configs (dansmith) (Meeting topic: tc)"15:10
mnaser#link http://paste.openstack.org/show/jD6kAP9tHk7PZr2nhv8h/15:11
dansmithSo,15:11
dansmithI'm concerned about the gate lately15:11
dansmithlast week, we had a 24+ hour turnaround literally all week,15:11
dansmiththis week it's been 8+ hours15:11
dansmithfor someone in the last timezone (i.e me), that means it is impossible to submit a job and get a result in the same working day15:11
dansmiththat is super frustrating15:11
gmanntriploe, neutron is more than 50% consumption15:11
gmanntripleo15:11
dansmithright, that's the takeaway there15:11
jungleboyj:-(15:12
mnaseryeah, that is really rough15:12
dansmithneutron is going to remove some of their tripleo jobs, but it's going to take a while to land that,15:12
dansmithand even still, they have several 2+ hour jobs in their large list15:12
dansmithnote that nova is 5% of the total.. NOVA15:12
mnaserdansmith: question, is this a lack of resources (compute power) or is this unreliable jobs (so causing large number of resets)15:12
gmannit definitely slow down the development15:12
dansmithI've already identified some fat we should cut from the nova list15:12
mnaser(spontaneously pinging clarkb / fungi if they have thoughts on all of this too)15:13
dansmithmnaser: it's always lack of resources, but in this case, it's waaaaay too many jobs that are multi-hour jobs15:13
dansmithmnaser: we could be in a lot better place if tripleo wasn't taking a quarter of the gate on super long multinode jobs,15:13
gmannI see more time in queue to get the node for run so lack of resources ?15:13
dansmithand definitely bad to drag those into neutron15:13
dansmithI've been talking to clarkb and fungi .. they're tired of me already :)15:13
dansmithI'm trying to point us (the TC) at maybe some people engineering to work on,15:14
gmanntempest-slow job also take much time 2 hrs or so which I have in list to optimize15:14
dansmithspecifically trying to ask projects to cut their jobs down to more reasonable sizes,15:14
dansmithand push things into periodic15:14
fungidansmith: oh i could never get tired of you ;)15:14
* dansmith makes eyes at fungi 15:14
fungithanks for trying to improve devstack/tempest performance!15:15
mnaserhmm15:15
gmannperiodic and experimental is good idea so that they can be run on demand too15:15
dansmithI've also been working on optimizing devstack itself, and we could use some general job perf optimizations I think, which nobody ever wants to work on15:15
dansmithbut we can't keep going like this15:15
dansmitha day turnaround is going to discourage people from testing things15:15
mnaserhave we lost any nodepool providers lately that might have contributed to worsening this?15:15
gmannfor devstack main challenge is to maintain the new framework/things if we change15:15
dansmithmnaser: I really don't think it's a recent abrupt loss of resources, I think it's jobs growth15:16
fungimnaser: not particularly recently, it seems projects are just adding an ever increasing amount of jobs and not necessarily looking at which ones they can safely stop running15:16
dansmiththat ^15:16
dansmithand hopefully that's where the TC can put some pressure on people15:16
mnaseri _hate_ to say it but does uh, a quota be something we might look into adding?15:16
fungithough also there has been a significant post-holiday rush leading into milestone 215:16
dansmithbecause the health of these systems impacts the health of the contributor community15:17
gmanntrue, thats good point15:17
mnaserit also changes our 'gate everything' mentality15:17
mnaserwhere we just want to slip things across because its such a pita to land things15:17
mnaserbecause 5 revisions of a patch = 5 business days15:18
dansmithat least15:18
fungii was surprised to find out that neutron had started running (multi-stage, multi-node) tripleo jobs in check and gate15:18
dansmithI literally submitted something the other day,15:18
dansmithand waited until the NEXT DAY to realize I had forgotten to git-add a file15:18
dansmiththat sucked15:18
fungithree-hour multi-node jobs and other jobs which pause waiting on those to finish consume rather a lot of our available quota15:18
dansmithfungi: right, that's the thing I'm hoping we can put some pressure on15:18
slaweqdansmith: patch for that is here: https://review.opendev.org/c/openstack/neutron/+/771486 and just needs approval15:18
slaweqand we already merged https://review.opendev.org/c/openstack/neutron/+/77083215:19
gmannneutron has optimized it a lot in past but with tripelo jobs it is back to more worst15:19
dansmithslaweq: yes, and thank you VERY much for proposing it :)15:19
slaweqyw :)15:19
*** JanZerebecki[m] has quit IRC15:19
dansmithanyway, I want to bring it up15:19
mnaseri think cross gating is a really neat thing, but we might not have the necessary r sources to drive it15:19
gmannbut another point we need to consider is 'does this narrow down our upstream testing quality' ?15:20
dansmithand maybe we can periodically revisit this and/or figure out some guidelines, and some requests to the projects15:20
fungicross-gating could still be done with a less heavy-weight approach, i expect15:20
dansmithI dunno what we can ask of tripleo, but even if neutron went to 5% like nova, I think tripleo would probably swell to more than its current 25%15:20
dansmithand I dunno what to do about that15:20
gmanndoes 3rd party CI/CD causing more load? I have not checked yet15:20
mnaser3rd party ci doesn't really affect it that much15:21
gmannok15:21
fungithe script clarkb's been using to provide node-hour breakdowns by project and job can help highlight opportunities to normalize utilization15:21
*** irclogbot_2 has quit IRC15:21
gmanndansmith: +1, we need to get tripleo with 10% somehow15:21
dansmithgmann: ++15:22
mnasermaybe we can find a way to work with the tripleo team to find a way to off-load many of their jobs15:22
fungiand yeah, just to put it in perspective, all the non-openstack projects (everything in x/, but also zuul, opendev, airship, starlingx, et cetera) account for <5% of our available quota utilization at peak15:22
dansmithgmann: I'm tempted to say that tripleo is special enough in how heavy it is that they really need to have their own resources, but I know that's a hard line to take15:22
mnaseri know all of these jobs and that doesnt include a bunch that run inside the rdo cloud15:22
jungleboyjThe 3rd party shouldn't be making a big difference.15:22
gmannyeah15:22
*** irclogbot_0 has joined #openstack-tc15:23
mnaserWhat about volume of developer changes to CI usage15:23
gmannfungi: mnaser not sure if we can add cap for node utilization per project even some node are free15:23
dansmithfungi: has a script for the review load, but it crashed for me15:23
dansmithand I've been busy with other stuff,15:24
dansmithbut that would be a good metric, mnaser15:24
gmannso that there is always nodepool for other patches whenever they are in gate15:24
gmannso say if nova want more jobs and load then it effect nova gate run time only15:24
mnaserCan we look at that metric before we start asking projects to lower their CI usage15:24
gmannand then project will automatically narrow down their jobs15:25
fungiyeah, for opendev as a whole we have an "engagement" reporting tool i've been working on which includes a breakdown of review activity by git namespace, it also shards the gerrit queries by repository so could probably be extended/modified to do stats based on deliverable aggregation to teams from the governance projects data15:25
dansmithgmann: well, that means work for zuul people, and while technical solutions are nice, we can chase the people ones first I think15:25
dansmithfungi:  do you have a paste of that? I couldn't get it to run15:25
dansmithmnaser: not all projects are going to be the same review-to-cpu-cycles ratio of course15:26
dansmithmnaser: but if it's like 10x for one project over another similar one that'd be useful15:26
fungi#link http://paste.openstack.org/show/801829 preliminary OpenDev 2020 Engagement Report15:26
mnaserdansmith: right yes, so we can approach a specific team and point out these 'fair-use' ratios15:26
mnaserok so maybe lets come up with some actionable things we can try doing and following up on15:27
dansmithfungi: ah okay that's not quite granular enough for projects yet15:27
dansmithwell, one is the neutron paring down, which is in progress15:27
fungiright, that's what i was saying, it would need modifying to report by repo, but the querying is already sharded by repo to stabilize the pagination from the rest api15:27
mnaseri think one action is maybe first approach teams with high usage (say tripleo) and ask what can be done about it?15:28
gmann+115:28
dansmithyeah15:28
fungi#link https://review.opendev.org/729293 OpenDev Engagament Reporting Tool15:28
fungiis where i've been working on the script itself15:28
dansmithfungi: ah, gotcha15:28
fungi(that's what produced that 2020 report)15:29
mnasercan anyone reach out to perhaps the PTL of these high use projects with a tc hat on and ask what we can do to improve the situation?15:29
mnaseri'm also happy to volunteer too15:29
fungipretty sure tripleo and neutron are already aware as they've been in prior discussions with opendev/tact sig representatives about disproportionate resource consumption15:29
dansmithI don't have a relationship with any of the tripleo people, but I have already been pushing on neutron15:29
gmannmay be TC liaison for tripleo ?15:30
mnaserfungi: i think we've historically had those discussions for months and years but i think we've reached a point where the discussion needs to transition to "what can you do about this?"15:30
mnasergmann: i think i don't mind picking it up and reaching out to them and seeing what we can do15:30
gmannsure15:30
fungiwell, to be fair, tripleo has been working on slimming it down. there was a point where they were consistently >50% of our overall consumption, then it was 40%, now it's down around 30%15:31
mnaser#action mnaser reach out to tripleo + other high usage job teams re: usage15:31
gmannthanks15:31
dansmithI forgot about the liaisons.. who is the tripleo one?15:31
mnaserfungi: ah yes that's good too15:31
dansmithfungi: ack, maybe neutron's adoption of that has regressed us then15:31
mnaserthat'll be on the project teams page15:31
dansmithperhaps we can wait and see how things are once the neutron patch to drop those goes15:31
mnaserhttps://governance.openstack.org/tc/reference/projects/tripleo.html15:31
gmanndansmith: it was me and ricolin :)15:31
*** JanZerebecki[m] has joined #openstack-tc15:32
ricolino/15:32
dansmithaight15:32
mnasercool, i say we should move on the next topics to make sure we can hit all topics15:32
mnaserand we can follow up on this next week15:32
gmannyeah15:32
mnaserthanks for bringing it up dansmith :>15:32
fungitripleo has been working on ways to avoid redundancy between their jobs, run fewer jobs, make their frameworks more efficient, et cetera and it's had an impact, but they're still by far the highest resource consumer when measured on a per-team basis15:32
dansmithyeah sorry, but thanks for humoring me :)15:32
gmann+1, thanks dansmith15:32
mnaser#topic Audit and clean-up tags (gmann)15:33
*** openstack changes topic to "Audit and clean-up tags (gmann) (Meeting topic: tc)"15:33
gmannwe have manila application for API tag15:33
gmannhttps://review.opendev.org/c/openstack/governance/+/77085915:33
gmannneed more review15:33
* gouthamr sneaks in15:33
gmannwe can do in gerrit, nothing much to discuss here unless any question15:33
ricolingmann, one question15:34
gmannalso I am thinking to remove this from agenda as such and add when there is progress or things to discuss ?15:34
gmannricolin: sure15:34
ricolinif a project didnot impl micro version, is that mean it should not apply for that tag?15:34
ricolinas the docs looks like so15:35
gmannricolin: microversion is not mandatory, if project does any versioing for API to discover the changes/features then it satisfy the rquiremnet15:35
gmannricolin: we changed that doc to clarify that but let me check15:35
ricolinit does tell about that15:35
gmannhttps://governance.openstack.org/tc/reference/tags/assert_supports-api-interoperability.html15:35
gmannpoint 2, say aor a discoverablity mechanism15:36
gmanni think i clarified it in ML also15:36
gmannbut do we need to add more clarification in doc ?15:36
ricolinokay make sense to me15:36
ricolingmann, I think current docs is fine15:36
gmannok, ricolin feel free to propose some change id doc is not so clear that can help other projects too15:37
gmannok15:37
gmannid/if15:37
ricolinsure:)15:37
gmannthanks15:37
gmannmnaser: reposting if you missed it. 'also I am thinking to remove this from agenda as such and add when there is progress or things to discuss ?'15:37
mnasergmann: yeah, that's fair with me too15:38
mnaserdoesn't seem to need that much so we can add it ad-hoc15:38
gmannyeah15:38
mnaser#action mnaser drop API tags topic from weekly agenda15:38
mnaserfor the rest, we just continue to follow up on reviews15:39
mnaser#topic infra-core updates (mnaser)15:39
*** openstack changes topic to "infra-core updates (mnaser) (Meeting topic: tc)"15:39
mnaseri brought up the topic on tuesday's opendev meeting which made for some interesting discussion15:39
mnaser#link http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-01-19-19.01.html15:40
mnasersee "Discuss infra-core (on behalf of OpenStack)"15:40
mnaser#link http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-01-19-19.01.log.html#l-1915:40
mnaserthe summary and actionable thing at the end of the discussion was that fungi was going to draft up an email to reach out to the community if anyone is looking to volunteer, and perhaps we can take an opportunity to improve the processes and tools to simplify the work of any reviewers15:41
fungiyeah, i'm hoping to get a tact sig request for help e-mail out to openstack-discuss by the weekend15:41
mnaseri don't think there's anything actionable from a tc's pov at the moment, so i'm afraid maybe we can put the topic aside and if we don't gather any attention for volunteers we can bring that up?15:41
gmannI think doc are really in good shape but yeah we can simplify if needed15:41
fungialso big thanks to mnaser and gmann for pitching in there so far15:42
*** lpetrut_ has quit IRC15:42
fungithe tl;dr though is that we need people invested in openstack to review configuration chages on behalf of openstack. if your config changes aren't getting reviewed fast enough for your liking, that's on you (at least in part)15:42
mnaserseems fair.  i'll drop this topic for now and we can bring it up if it's an issue15:43
gmann+115:43
jungleboyj++15:43
mnaser#action mnaser remove infra-core discussion from agenda15:43
mnaser#topic Dropping lower-constraints testing from all projects (gmann)15:43
*** openstack changes topic to "Dropping lower-constraints testing from all projects (gmann) (Meeting topic: tc)"15:43
gmannwe have responses in ML and few suggestion also15:44
gmannand its going on15:44
fungiyeah, discussion has been lively15:44
mnaserthat's kinda good i guess :)15:44
mnaserdo we have anything to update/discuss on that or shall we leave the discussion to continue and go back to follow up on it next week?15:45
gmannso should we continue discussion for some more and then finalize anything in TC or now?15:45
ricolinFYI I will start the SIG update thing these two days15:45
mnasercool ricolin.  i think i like leaving the discussion run while it's active and we can follow up on it again next week if we seem to be getting to a consensus next week15:46
fungiit seems like a popular compromise might be to limit lower-constraints.txt files to just what's listed in requirements.txt for a project in master, and drop the lower bounds checking as soon as stable is branched (i really don't see it being a viable approach in stable branches)15:46
gmanncurrent suggestion from stephen and what  os-win and networking-hyperv tried is 1. 'remove the indirect deps form l-c file' which can  ease the maintenance 2. remove the job form stable branches15:46
jungleboyjThe discussion has been good.  Let's see where it goes.15:46
gmannyeah what fungi wrote15:47
gmannfungi: for stable branch, we should remove it.15:47
mnaseri think for today and for time purposes, maybe we should let the conversation keep going and see where we are next week15:48
fungibut not just existing stable branches, future stable branches are going to hit the same problems as they age15:48
mnaserso we can have a solid reliable recommendation15:48
gmannmake sense,15:48
fungiyeah, i agree the discussion hasn't played out yet15:48
jungleboyjMakes sense.15:48
mnaserokey cool15:48
mnaser#topic Decide on OpenSUSE in testing runtime (gmann)15:48
*** openstack changes topic to "Decide on OpenSUSE in testing runtime (gmann) (Meeting topic: tc)"15:48
gmannreally do  not want us to interrupt the ongoing discussion and conclude in half way15:48
mnaser#link https://review.opendev.org/c/openstack/devstack/+/76988415:49
mnaser#link https://review.opendev.org/c/openstack/governance/+/77085515:49
gmannyeah patches are up for this, need more review15:49
mnasertc-members: ^ lets get reviews on the governance change so we can let the qa team do their cleanups15:49
mnaserits a trival review15:49
gmannand I think nothing else needed on this so we can remove from agenda too ?15:50
mnaseryeah i think its just mostly a review15:50
gmannyeah15:50
* dansmith hath blessed it with his +115:50
mnaser#action mnaser remove "Decide on OpenSUSE in testing runtime (gmann)" from agenda15:50
mnaser#topic Define 2021 upstream investment opportunities15:50
*** openstack changes topic to "Define 2021 upstream investment opportunities (Meeting topic: tc)"15:50
dansmithI'm starting a hedge fund, looking for investors15:50
gmannwe have not got any help on this yet for many years but in case we want to continue it for 2021.15:51
mnaserdansmith: waited all meeting long to drop this15:51
dansmithhah15:51
gmanni have pushed to continue the 2020 one which are goal, qa, rbac15:51
mnaseri'm ok with just copying them over and merging them, but perhaps there will be a time to evaluate if there's just any point in doing all of this15:51
mnaseryear after year we've put in effort into writing all this stuff up but it kinda sadly just ends up sitting15:52
mnaserand when these things do get help or traction, it's probably rarely been someone who read this document and decided to put resources on it15:52
*** rosmaita has quit IRC15:52
gmannyeah, at some point we have to stop this if it does not help15:52
gmannbut not fair to drop due to COVID situation where we should not expect more unpaid volunteer. if company invest then good15:53
fungiprior expectation was that we would direct board members to that list, pick a different one to highlight in each foundation monthly newsletter, et cetera15:54
*** rosmaita has joined #openstack-tc15:54
fungii get that there's not a lot of attention on it, but i suspect we've been forgetting to bring anyone's attention to it as well15:54
mnaser#link Define 2021 upstream investment opportunities15:54
gmannyeah but I do not think board has been any help till now15:54
mnaser#undo15:54
openstackRemoving item from minutes: #link Define15:54
mnaser#link https://review.opendev.org/c/openstack/governance/+/77170715:54
mnasergmann: ok great, thank you for bringing this up, i think we can drop this as it's just an open review now?15:55
gmannyup15:55
mnaser#action mnaser drop "Define 2021 upstream investment opportunities" from agenda15:56
mnaser#topic open discussion / open reviews15:56
*** openstack changes topic to "open discussion / open reviews (Meeting topic: tc)"15:56
mnaseri'll do a run over the open things soon, this past week has been pretty hectic with a personal move so15:56
dansmithare we done?15:59
gmannseems so, we can end15:59
gmannmnaser: ?16:00
dansmithmnaser: I bill overtime by the minute16:00
gmann:)16:01
mnaserSorry, had to step out for a sec. Let me end it before I go in deep debt16:01
mnaser#endmeeting16:01
*** 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:01
openstackMeeting ended Thu Jan 21 16:01:26 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-01-21-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-01-21-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-01-21-15.00.log.html16:01
mnaserThank you everyone.16:01
gmannthanks16:01
jungleboyjThank you!16:02
*** dklyle has joined #openstack-tc16:08
*** pojadhav is now known as pojadhav|away16:23
*** e0ne has joined #openstack-tc16:29
*** lpetrut has joined #openstack-tc16:42
*** lpetrut has quit IRC16:50
*** jamesmcarthur has joined #openstack-tc16:51
*** njohnston is now known as njohnston|lunch17:01
*** pojadhav|away is now known as pojadhav17:08
*** lpetrut has joined #openstack-tc17:40
*** diablo_rojo has quit IRC17:41
*** rpittau is now known as rpittau|afk17:42
*** ralonsoh has quit IRC17:52
*** lpetrut has quit IRC17:55
*** e0ne has quit IRC18:33
jungleboyjdiablo_rojo_phon:  spotz  I guess I may not making it to the video planning session today.  Going to have to take Logan for anti-body testing.18:37
*** diablo_rojo has joined #openstack-tc18:37
diablo_rojojungleboyj, uh oh! Hope everything is alright. No worries about the meeting.18:37
*** rosmaita has left #openstack-tc18:44
*** andrewbonney has quit IRC18:55
diablo_rojotc-members: If you have ideas for the monthly newsletter, please add them ASAP(by Tuesday at the latest)! The Newsletter goes out a week from today: https://etherpad.opendev.org/p/newsletter-openstack-news18:57
TheJulianot presently on the TC so hesitant to add this, but maybe something retrospectivy wise to try and identify positives and opportunities in the project removals19:00
gmanndiablo_rojo: may be we can keep it one of the meeting agenda. it is bi weekly publish right?19:01
TheJuliagmann: says monthly on the etherpad19:02
fungiyeah, foundation newsletter is ~monthly but sometimes goes longer between issues19:02
gmannah yeah, so we can discuss 1 week prior to publication19:02
*** njohnston|lunch is now known as njohnston19:02
fungiit used to be more frequent but we worked out that was a little too often19:03
diablo_rojoTheJulia, your opinions are always welcome!19:04
diablo_rojoWe didn't do one in December because holidays, but we are back on ~monthly now19:05
diablo_rojogmann, ^19:05
diablo_rojoSo yeah it can be in the agenda. I should have added it today, but I didn't make the meeting.19:05
gmannmay be every 2nd meeting of month can be good time.19:06
diablo_rojoYeah that works. Now we just have to remember lol19:07
* TheJulia whispers "standing agendas..."19:07
diablo_rojoPsssshhhh making it all easy and stuff.19:08
TheJulialol19:08
diablo_rojoMy brain buffer is constantly full though, so yeah, standing agenda is a good idea.19:08
gmannadded comment in etherpad. nothing else i can think of for this month19:09
jungleboyj:-)19:11
jungleboyjdiablo_rojo:  Thanks.  Kids already had Covid but we had another exposure over the weekend.  Getting the antibody levels checked for peace of mind.19:12
spotzjungleboyj: Oh no!!!!!19:17
jungleboyjYeah.  One weekend of hockey and we are back in quarantine.19:17
gmannjungleboyj: ah, take care.19:18
spotzSee at least dog and pony stuff have built in social distancing19:18
*** ShadowJonathan has quit IRC19:27
*** ShadowJonathan has joined #openstack-tc19:28
jungleboyjspotz:  :-)  Yeah.  We all had masks on, so I am sure we will be fine but need to be careful ...19:43
jungleboyjThis is all getting old though.19:43
spotzYeah:( I missed seeing everyone this year19:44
diablo_rojoI'm surprised MN even allows that stuff atm with how full your ICUs are.19:45
*** jamesmcarthur has quit IRC19:52
*** slaweq has quit IRC19:55
*** jamesmcarthur has joined #openstack-tc20:03
spotzdiablo_rojo: wake up;)20:05
*** irclogbot_0 has quit IRC20:14
*** tosky has quit IRC20:14
*** tosky has joined #openstack-tc20:15
*** irclogbot_2 has joined #openstack-tc20:17
diablo_rojospotz, I am awake, the calendar says we don't meet for another hour and a half lol.20:26
spotzdiablo_rojo: You said 2 my time:)20:27
fungimaybe she timezone mathed backwards20:28
spotzmaybe but 2 I could do, 4 I can't do a whole hour20:33
diablo_rojospotz, oh, maybe I did do that wrong- but I think you accepted the calendar invite lol20:35
spotzdiablo_rojo: Ha I just grabbed the link out of it and put it in the work calendar to block off the time20:36
diablo_rojoHahahaha20:46
diablo_rojoCalendars are hard.20:46
jungleboyjdiablo_rojo:  I know.  The schools and sports people pushed really hard for it.  Our numbers have improved a lot.20:47
jungleboyjGo figure.  This will be my 4th time being exposed I think.20:47
jungleboyjThat I know of.20:47
spotzdiablo_rojo jungleboyj - Would meeting at like 4 PST 6 CST work instead of meeting in 45?21:13
jungleboyjI could attend for part of it.21:15
spotzWell while we decide I'm starting dinner21:25
*** jamesmcarthur_ has joined #openstack-tc21:45
*** jamesmcarthur has quit IRC21:49
*** jamesmcarthur has joined #openstack-tc22:02
*** jamesmcarthur_ has quit IRC22:05
*** jamesmcarthur_ has joined #openstack-tc22:51
*** jamesmcarthur has quit IRC22:55
*** jamesmcarthur has joined #openstack-tc23:02
*** jamesmcarthur_ has quit IRC23:05
*** jamesmcarthur has quit IRC23:12
*** jamesmcarthur has joined #openstack-tc23:16
*** jamesmcarthur has quit IRC23:16
*** jamesmcarthur has joined #openstack-tc23:16
*** jamesmcarthur has quit IRC23:55
*** jamesmcarthur has joined #openstack-tc23:59

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