17:00:26 <cmurphy> #startmeeting keystone
17:00:26 <openstack> Meeting started Tue Jan 21 17:00:26 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:27 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:29 <openstack> The meeting name has been set to 'keystone'
17:00:39 <cmurphy> #link https://etherpad.openstack.org/p/keystone-weekly-meeting agenda
17:00:42 <cmurphy> o/
17:01:01 <gagehugo> o/
17:01:04 <cmurphy> i'm finishing up in another meeting, might be slightly distracted
17:01:26 <vishakha> o/
17:02:48 * knikolla running a few mins late
17:03:51 <lbragstad> o/
17:05:33 <cmurphy> #topic Ussuri specs
17:06:06 <cmurphy> the spec freeze duedate is in three weeks, we have three specs proposed and not yet merged
17:06:26 <cmurphy> #link https://review.opendev.org/698951 expiring group membership
17:06:43 <cmurphy> #link https://review.opendev.org/698950 federated user attributes
17:06:58 <cmurphy> i think those are uncontroversial, they just need reviews
17:07:18 <cmurphy> #link https://review.opendev.org/698279 alembic migration
17:08:04 <cmurphy> I'm a little concerned about that one as it seems like the migration might be a bit complicated and we don't have proper rolling upgrade CI any more
17:08:25 <lbragstad> the alembic one?
17:08:28 <cmurphy> yes
17:08:33 * lbragstad nods
17:09:16 <cmurphy> does anyone have an idea how hard it would be to get rolling upgrade jobs up and running?
17:09:24 <cmurphy> we've been meaning to do it for a while and it never quite happened
17:09:59 <lbragstad> we had it working at one point, but it's been so long since i've looked at it
17:10:03 <lbragstad> i'm not sure what's changed
17:10:59 <cmurphy> we had the OSA upgrade job working but jesse disabled it because it was broken, and according to jrosser they've changed how their upgrade jobs work now
17:12:12 <lbragstad> aha
17:12:25 <cmurphy> i think ideally we should be doing it with grenade and a multinode job but i'm not sure how that works
17:12:33 <lbragstad> yeah - me either...
17:12:46 <lbragstad> originally, i wanted to use osa since we could theoretically do all the testing on a single host
17:12:59 <vishakha> I pushed a patch to check the experimental jobs
17:13:05 <cmurphy> http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2020-01-20.log.html#t2020-01-20T18:20:05
17:13:29 <lbragstad> at the time, i was more concerned about gate resources and i didn't want to put more strain on infra because we decided to use multiple nodes to test upgrade scenarios
17:13:58 <vishakha> https://review.opendev.org/#/c/703541/
17:14:04 <lbragstad> maybe that's not a concern anymore
17:14:52 <cmurphy> lbragstad: i think that shouldn't be our top concern, if we're really causing a problem they'll tell us and we can work with them to fix it
17:15:07 <cmurphy> vishakha: is that running rolling upgrades? ie with expand, migrate, and contract?
17:15:44 <lbragstad> yeah - that's fair, at the time there was a whole bunch of profiling going on with gate resources
17:16:54 <cmurphy> vishakha: also, what upgrade is it testing? is it going from stable/train to master?
17:17:33 <vishakha> It upgrades from stable/train to master
17:19:58 <cmurphy> vishakha: okay, can you check if it's doing rolling upgrades and if it's not see what it will take to have it do that?
17:21:03 <vishakha> cmurphy: I think it does. But i will provide some more details regarding it to you
17:21:14 <cmurphy> thanks vishakha
17:21:28 <cmurphy> does anyone else have questions about this spec?
17:23:53 <gyee> do we run the federation function tests during rolling upgrade?
17:24:19 <gyee> those may break if we are not using source LB at the proxy
17:24:24 <cmurphy> gyee: not currently afaik
17:24:37 <cmurphy> just regular tempest
17:24:59 <gyee> does tempest using LB for multi-node deployment?
17:25:31 <cmurphy> i'm not actually sure
17:26:05 <gyee> round robin LB is not good for federation because of the state rely
17:26:53 <cmurphy> it's something we could look into, right now i just want any kind of rolling upgrade testing just so we don't break the migrations :)
17:29:22 <cmurphy> moving on, please review all three proposed ussuri specs
17:29:35 <cmurphy> #topic Ussuri roadmap checkin
17:29:46 <cmurphy> #link https://tree.taiga.io/project/keystone-ussuri-roadmap/kanban roadmap
17:30:39 <cmurphy> I am not really planning on organizing a midcycle or milestone-ly meetings so I'm hoping we can make due with using the meeting time for some development coordination
17:31:30 <cmurphy> I'd like to go through the In Progress column and get an update from the card owners on how it's going and whether help is needed
17:31:30 <gagehugo> I got a wip for removing ksc from ksm: https://review.opendev.org/#/c/702278/
17:31:38 <gagehugo> but haven't made too much progress yet
17:31:54 <cmurphy> awesome
17:32:09 <cmurphy> #link https://tree.taiga.io/project/keystone-ussuri-roadmap/us/42
17:33:02 <cmurphy> gagehugo: anything you need help on? or anything need discussion?
17:33:16 <gagehugo> not yet, was just giving a status about it
17:33:23 <gagehugo> I'll say something if I get stuck
17:33:26 <cmurphy> cool
17:34:34 <cmurphy> #link https://tree.taiga.io/project/keystone-ussuri-roadmap/us/2 Work with nova to implement scope_types
17:35:06 <cmurphy> this one goes a little farther than just nova, we created an RBAC popup team with a few different projects as members
17:35:21 <cmurphy> #link https://governance.openstack.org/tc/reference/popup-teams.html#secure-default-policies
17:36:01 <cmurphy> i met with each project except nova before christmas to kick things off, planning on circling up with gmann and the other projects this week to figure out next steps
17:36:12 <gagehugo> nice
17:36:33 <cmurphy> will try to have a regular email update once i figure out how to track everybody's work
17:36:44 <vishakha> Should I move 52 and 53 from ready to ready for review?
17:37:20 <cmurphy> vishakha: you could update the subtasks
17:37:38 <vishakha> thanks cmurphy
17:38:44 <vishakha> #link https://tree.taiga.io/project/keystone-ussuri-roadmap/us/33?kanban-status=2035081
17:38:51 <vishakha> ready for review now https://review.opendev.org/#/c/588211/
17:39:07 <vishakha> Thanks cmurphy for giving time to this
17:39:14 <cmurphy> the federation job is green! :D
17:39:21 <vishakha> :)
17:39:29 <cmurphy> vishakha: please move that one to ready for review too
17:39:37 <vishakha> sure
17:40:46 <cmurphy> knikolla: any update on https://tree.taiga.io/project/keystone-ussuri-roadmap/us/31?kanban-status=2035081 https://tree.taiga.io/project/keystone-ussuri-roadmap/us/32?kanban-status=2035081 https://tree.taiga.io/project/keystone-ussuri-roadmap/us/45?kanban-status=2035081 ? besides the specs needing to be merged
17:41:00 <knikolla> no updates besides that.
17:41:29 <cmurphy> knikolla: need any help on any of them?
17:41:55 <knikolla> reviews on the specs :)
17:42:07 <cmurphy> ++
17:43:08 <cmurphy> hmm i guess subtasks don't appear on the board on their own
17:44:11 <cmurphy> for https://tree.taiga.io/project/keystone-ussuri-roadmap/us/3?kanban-status=2035081 and https://tree.taiga.io/project/keystone-ussuri-roadmap/us/49?kanban-status=2035081 - those are in progress, need reviews from the tempest team and am slowing replicating all our flask protection tests in keystone-tempest-plugin
17:44:42 <cmurphy> i think i need to fix the tempest changes, my last update broke something
17:45:06 <cmurphy> lbragstad: are you still working on https://tree.taiga.io/project/keystone-ussuri-roadmap/us/7?kanban-status=2035081 ?
17:48:34 <cmurphy> re https://tree.taiga.io/project/keystone-ussuri-roadmap/us/10?kanban-status=2035081 we merged a bunch of work in oslo.limit to implement an initial interface, the hierarchical interface is still a wip but there's at least enough in there that other projects can start working with it and building on it
17:49:53 <cmurphy> anyone have questions or things to discuss about the tasks in progress or the tasks not yet started?
17:50:02 <lbragstad> i haven't working on it for a while
17:50:12 <lbragstad> it's on my list, but i don't have cycles immediately
17:51:24 <cmurphy> lbragstad: okay, should we leave the story as-is for now?
17:51:36 <lbragstad> sure
17:51:45 <cmurphy> okay
17:52:21 <cmurphy> thanks for the updates everyone
17:52:36 <cmurphy> #topic review requests
17:53:10 <cmurphy> #link https://review.opendev.org/#/c/699013/
17:53:19 <cmurphy> gagehugo still seeking reviews on ^
17:53:36 <cmurphy> #link https://review.opendev.org/700826
17:53:44 <vishakha> #link https://review.opendev.org/#/c/697444/
17:53:53 <cmurphy> and i'm still needing reviews on 700826
17:54:05 <vishakha> #link https://review.opendev.org/#/c/703578/
17:54:20 <vishakha> #link https://review.opendev.org/#/c/588211/
17:54:57 <cmurphy> vishakha: i will take another look at 697444 and 588211
17:55:11 <cmurphy> vishakha: can you explain more about 703578?
17:55:40 <vishakha> thanks cmurphy
17:56:22 <vishakha> all-plugin command used to run keystone_tempest_plugin is goin to be removed soon. We can only use all instead of it
17:57:24 <cmurphy> okay
17:57:40 <cmurphy> #topic L1 duty rotation
17:57:50 <cmurphy> really quickly since we're almost at time
17:58:01 <vishakha> This week I am on duty
17:58:12 <cmurphy> knikolla: was on duty this past week, anything worthwhile to mention about recent bugs?
17:58:20 <cmurphy> thanks vishakha
17:58:37 <knikolla> It was a quiet week.
17:58:59 <cmurphy> any volunteers for the week after vishakha ?
17:59:29 <gagehugo> I can do next week
17:59:38 <cmurphy> thanks gagehugo
17:59:58 <cmurphy> with that we're about at time
18:00:02 <cmurphy> thanks everyone
18:00:04 <lbragstad> thanks all
18:00:05 <cmurphy> #endmeeting