17:00:13 #startmeeting keystone 17:00:14 Meeting started Tue Feb 4 17:00:13 2020 UTC and is due to finish in 60 minutes. The chair is cmurphy. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:18 The meeting name has been set to 'keystone' 17:00:20 o/ 17:00:24 #link https://etherpad.openstack.org/p/keystone-weekly-meeting agenda 17:00:26 o/ 17:00:26 o/ 17:00:31 o/ 17:01:38 o/ 17:02:19 hey everyone 17:02:22 #topic Rocky EM 17:02:43 Won’t be able to attend meeting, but I can take on the next bug duty slot. 17:02:51 wanted to raise awareness that the rocky branch is going into Extended Maintenance around the end of the month which means no more releases will be made 17:03:06 knikolla: okay thanks 17:03:54 for rocky - if you see bugfix patches that should be backported please help cherrypick them as far back as they need to go 17:04:38 devstack is broken for rocky atm but the qa team is on top of it 17:05:02 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012207.html Rocky EM 17:05:13 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012241.html Rocky CI status 17:06:06 any questions or comments on that topic? 17:07:07 #topic L1 duty rotation 17:07:19 gagehugo was on last week, any interesting bugs to discuss? 17:07:31 just one doc bug I think 17:07:35 from rocky 17:07:43 about apache missing as an item to install 17:07:58 otherwise nothing really that I remember 17:08:49 okay 17:08:56 I updated the tracker 17:09:04 #topic review requests 17:10:01 #link https://review.opendev.org/#/c/704736/ 17:10:57 Also I wanted to discuss over https://review.opendev.org/#/c/697444/. Should I change the implementation as per the comments? 17:10:57 the day has finally come 17:10:58 vishakha thanks for working on that but i will not review a change that touches over 100 files, my personal feeling is that this is unnecessary code churn and it is not a critical part of the py2 non-support goal, happy for other reviewers to take care of it if it is important to them 17:12:12 vishakha: i like the suggestions made by lbragstad amotoki and knikolla on 697444 i think those are more friendly than the json blob 17:13:27 cmurphy: Thanks. I will update according this approach. 17:14:32 i have an easy review https://review.opendev.org/704707 17:16:14 any other review requests? or any other feelings about https://review.opendev.org/#/c/704736/ ? i gave my opinion but i don't want to stifle others 17:16:52 I'd rather it be a series of smaller changes, but I'm fine with removing six 17:17:11 was the plan to just leave six in place? 17:17:17 since it works with py3? 17:17:34 i'm not sure we made a plan 17:17:41 i know morgan wanted it gone 17:19:02 i would prefer an incremental approach or cleaning it up little by little 17:19:27 but if a big bang approach is fine with you guys i won't block it 17:20:19 tbh i just think there are more important things to spend time on 17:20:30 I could convert it into series of patches 17:20:35 i'm indifferent - i certainly prefer smaller patch sizes, but i already reviewed it, if it is broken up i'm happy to re-review 17:22:31 we might as well keep it as one big patch since it's already gotten one +2, i don't want vishakha to have to spend a ton of time breaking it up :) 17:23:08 thanks :) 17:24:21 I noticed that stackalytics isn't showing any count of keystone commits. Can anybody help me over that? I added ussuri for keystone project https://review.opendev.org/#/c/698418/ 17:25:39 i know people have reported inconsistencies with stackalytics in the past, from my experience it usually needs to be resolved by mirantis 17:26:32 #topic open floor 17:26:44 it looks to me like it's working https://www.stackalytics.com/?module=keystone-group&release=ussuri&metric=commits i see commits from the last few days 17:27:10 but it's not a service that the opendev team runs, i wouldn't puch much stock in it 17:27:18 put* much 17:28:30 i hope nobody's employers are relying on stackalytics metrics as an accurate measure of community engagement 17:30:48 anything else to bring up? 17:30:55 I Was just curious to know the reason. 17:31:26 vishakha: i'm curious what isn't working for you? it looks like it's working to me 17:32:42 cmurphy: Sorry checked few days ago, that time it wasn't showing. Now it is updated and I can see too. 17:33:11 vishakha: ah yeah i think it works in batches and sometimes takes a while to catch up 17:33:58 okay. Thanks 17:34:55 oh one more thing, if you have spare cycles please help the nova team review their policy changes https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh 17:35:27 ++ 17:36:18 i'll close it with that, have a great day everyone 17:36:21 #endmeeting