16:00:16 #startmeeting keystone 16:00:16 Meeting started Tue Aug 28 16:00:16 2018 UTC and is due to finish in 60 minutes. The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:20 The meeting name has been set to 'keystone' 16:00:45 #link https://etherpad.openstack.org/p/keystone-weekly-meeting 16:00:48 agenda ^ 16:01:23 o/ 16:01:28 o/ 16:01:28 o/ 16:01:37 lbragstad I fixed the ping list 16:01:39 i think there might be a couple people out 16:01:43 gagehugo: tanks 16:01:46 thanks* 16:02:11 tanks sound fun 16:02:42 o/ 16:02:43 I suppose that depends on you frame of reference with respect to the tank gagehugo ;) 16:03:13 #topic release status 16:03:20 #info rc2 cut 16:03:38 we ended up cutting rc2 last week to make sure we had backport migrations 16:03:47 (thanks wxy| for catching that) 16:03:54 with that 16:03:56 #info Stein is open for development 16:04:13 o/ 16:04:26 hrybacki I was thinking more of a scorched earth clone I played in grade school lab 16:04:26 just a reminder that now is a great time to work on PoCs before the PTG 16:05:01 I may have played the same thing come to think of it :) 16:05:11 lbragstad: I added two new oslo.limit patches. 16:05:23 wxy|: oh - nice. i'll be sure to take a look 16:05:31 lbragstad: cool 16:05:35 #topic Stein PTG Details 16:05:51 we're 13 days from the PTG 16:06:04 and i've updated the etherpad to include a schedule 16:06:06 #link https://etherpad.openstack.org/p/keystone-stein-ptg 16:06:13 o/ 16:06:16 please give it a look and let me know if you see any issues or conflicts 16:06:47 tl;dr is that we have monday for cross-project stuff, thursday and friday will be dedicated to keystone-specific topics 16:07:00 tuesday and wednesday we won't have a room 16:07:22 but we will likely be doing follow up discussions for federation + edge and cross-project discussions from monday 16:08:09 and for the most part, friday is going to be reserved to getting everything we've talked about throughout the week in trello 16:08:13 and merging specs 16:08:33 i'm really hoping we don't have much to "follow up on" when we leave denver 16:09:10 any questions on the schedule so far? 16:09:53 looks great! 16:10:31 hrybacki: think we'll be good to do all the trello/roadmap work on that friday? 16:10:49 Looks pretty good 16:11:00 lbragstad: I believe so, yes 16:11:06 cool 16:11:11 we do also have a few open sessions 16:11:26 wednesday afternoon for example 16:11:57 usually something always comes up, but in the event things go smoothly we can use that as hack time 16:12:21 lbragstad: is there any thorny bugs that we could pair on during that time? 16:12:30 if people want to sit down in a corner and work through review or pair-programming (flask stuff or protection patches) 16:12:36 assuming the block doesn't get filled up with something else 16:12:41 right 16:12:47 ++ /me steps back 16:13:12 hrybacki: by all means, if you have suggestions for things to tackle during that time, please feel free to suggest them :) 16:13:22 i was thinking the flask stuff 16:13:25 I think we are on the same tracks 16:13:36 or policy protection 16:13:47 we could spend a whole day on microversions like last year 16:13:49 but we could hammer through the doc changes we wanted to do in rocky 16:13:50 * gagehugo ducks 16:13:55 gagehugo: go away :P 16:14:03 lbragstad: that's not a bad idea 16:14:08 'get it done' 16:14:25 I'd like to see a roadmap for the rest of the flask stuff (honest answer) 16:14:29 right - something we can iterate on quickly 16:14:32 never will there be a more rich library of knowledge than in that room 16:15:26 kmalloc: do you think it would be possible to get an idea of what's left to help you with before the PTG? 16:16:36 mostly review eyes. 16:17:00 if someone else wants to take on domains, projects, users, that would be awesome. 16:17:04 afaik just a few APIs are left to be moved 16:17:04 but they are burly changes. 16:17:20 i am blocked on groups waiting for your opinon lbragstad 16:17:31 which is why the rebase/refactor hasn't happened. 16:17:38 ack - sorry about that 16:17:42 i will look today 16:17:58 i'm just about to finish up the failures on #link https://review.openstack.org/#/c/594547/ 16:18:01 lbragstad: will send DM. can't talk more in public forums. 16:18:37 sounds good 16:18:52 is there anything else specific to the PTG people want to discuss? 16:18:56 kmalloc I wouldn't mind trying one of those resources, if I get some capacity on my end 16:18:58 anything not on the schedule that should be? 16:19:08 OS-FEDERATION needs review eyes, it's the next to land: https://review.openstack.org/#/c/591082/ 16:19:21 and should be ready for review and passing tests. 16:19:39 gagehugo: i warn you, domains is the easiest, and it isn't easy. 16:19:48 :( 16:20:01 ok 16:20:15 gagehugo: i will happily take help. 16:20:38 but i want to level set that it isn't straight forward. 16:20:48 I will take a swing at it 16:20:53 it's mostly hard because we are duplicating functionality. 16:21:11 gagehugo: you'll need to move all dispatched URLs that start with /domains in one swoop. 16:21:15 (one patch) 16:21:31 /auth may not be moved by PTG. 16:21:45 is that one going to be the last one we move? 16:21:46 it is very involved and will probably take ~3-5 days to unwind. 16:21:48 yes. 16:21:59 i expect auth to move around S2, to be honest. 16:22:08 mmmm 16:22:11 unless i get a lot of time this weekend or move through /users and/or projects 16:22:12 ok 16:22:15 fast. 16:22:43 auth is involved because of how the plugins interact and how things directly access auth controllers 16:23:00 some of the cleanup is done already, some is on hold because federation, projects, users should move first 16:23:13 ok 16:23:42 and auth may *still* require webob for a bit after it is moved. 16:23:49 just for request/response handling 16:24:16 i've got a translation from flask req -> webob req that makes it a bit easier. 16:24:49 once the APIs are moved, we will need to compress our middleware (mostly) to before_request functions 16:25:02 i have it down for wednesday in the event we don't have cross-project things to go through 16:25:22 i can cover the indepth bits of how flask works for us 16:25:31 and what we are doing to fill in gaps at the PTF 16:25:33 PTG* 16:25:55 i hope the flask APIs are easier to read 16:26:12 i think long term it will be easier to maintain, but it has been a big shift. 16:26:37 in S, i would also like to see us do the move of keystone.XXX to keystone.subsystem.XXX (for non-api code) 16:26:40 if we can. 16:27:06 just so we clearly outline what is api code, what is business logic code, and what is common/shared/etc code 16:27:44 sounds good 16:28:03 i'd like to start stacking changes like https://review.openstack.org/#/c/594547/ up after the flask migrations 16:28:15 ++ 16:28:36 i'll bug you today re: groups, get the current stack rebased and start in on users and/or projects 16:29:13 ok 16:29:17 anything else PTG related? 16:29:22 otherwise we can move to open discussion 16:31:32 #topic open discussion 16:34:02 if there isn't anything specific to bring up, looks like we can get some time back 16:34:18 ++ thanks lbragstad ! 16:34:26 thanks for coming, all 16:34:38 thanks! 16:34:41 reminder we can office hours in 26 minutes 16:34:47 s/can/have/ 16:34:53 #endmeeting