18:00:02 <lbragstad> #startmeeting keystone 18:00:03 <openstack> Meeting started Tue May 2 18:00:02 2017 UTC and is due to finish in 60 minutes. The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:07 <openstack> The meeting name has been set to 'keystone' 18:00:09 <lbragstad> ping antwash, ayoung, breton, cmurphy, dstanek, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, notmorgan, ravelar, rderose, rodrigods, samueldmq, spilla 18:00:12 <breton> yey 18:00:17 <lbragstad> #link https://etherpad.openstack.org/p/keystone-weekly-meeting 18:00:17 <cmurphy> o/ 18:00:20 <lbragstad> agenda ^ 18:00:21 <lbragstad> o/ 18:00:29 <gagehugo> o/ 18:00:35 <rodrigods> o/ 18:01:26 <lamt> o/ 18:01:42 <lbragstad> we have a pretty light agenda today - so we'll give it a minute 18:01:45 <dstanek> o/ 18:02:06 <dstanek> that's my favorite kind of agenda 18:02:21 <lbragstad> :) 18:03:28 <edmondsw> what did I miss... no agenda for today? 18:03:35 <lbragstad> #topic announcements 18:03:44 <lbragstad> edmondsw https://etherpad.openstack.org/p/keystone-weekly-meeting 18:03:48 <lbragstad> edmondsw a very light one :) 18:04:04 <lbragstad> first up - I've made an addition to our core team 18:04:08 <breton> yey! 18:04:19 <rodrigods> \o/ 18:04:22 <edmondsw> :) 18:04:26 <lbragstad> #info cmurphy is now keystone-core 18:04:29 <lbragstad> :) 18:04:30 <breton> cmurphy: congrats 18:04:39 <rodrigods> congrats cmurphy 18:04:42 <edmondsw> +1 18:04:44 <cmurphy> :) yay 18:04:57 <lbragstad> i feel that has been long over due - regardless 18:05:13 <gagehugo> grats! 18:05:14 <lbragstad> cmurphy thanks for all the quality code reviews and hard work 18:05:22 <cmurphy> i will try not to break keystone too badly 18:05:45 <lbragstad> :) 18:05:57 <lbragstad> also 18:06:03 <lbragstad> we won't be having a meeting next week 18:06:22 <lbragstad> since some will be at the forum 18:06:34 <lbragstad> I'll send a reminder after the meeting today 18:07:04 <lbragstad> which brings us to our next topic 18:07:11 <lbragstad> #topic forum 18:07:23 <lbragstad> is there anything folks need for the forum next week? 18:07:37 <lbragstad> i'll be getting into boston sunday night and leaving on friday 18:07:50 <gagehugo> lbragstad good suggestions for food? 18:08:02 <lbragstad> gagehugo clam chowder and lobster rolls 18:08:07 <gagehugo> +1 18:08:11 <edmondsw> I assume we hit up ayoung for food suggestions 18:08:20 <lbragstad> edmondsw ++ 18:08:34 <lbragstad> ayoung took us to a few awesome places when we had the midcycle there a couple years ago 18:08:44 <gagehugo> oh nice 18:08:58 <dstanek> congrats cmurphy! you earned it 18:09:08 <cmurphy> ty dstanek 18:09:27 <breton> ask dims, he knows things around there 18:09:44 <dims> vegetarian? :) 18:10:06 <lbragstad> dims I'm down ;) 18:10:37 <lbragstad> if anyone needs anything prior to the forum, don't hesitate to ping me 18:10:53 <lbragstad> #topic open discussion 18:11:26 <lbragstad> does anyone have anything they'd like to talk about? 18:11:48 <breton> which specs are affected by recent layoffs? 18:12:19 <lbragstad> well - most of the policy in code and policy docs works was done 18:12:39 <lbragstad> i think there are only a few patches left to implement both of those 18:12:48 <lbragstad> quota limits is still in the pipe 18:13:06 <lbragstad> not sure if anyone is able to pick that up though 18:13:24 <lbragstad> the api keys spec is probably going to be affected 18:13:32 <lbragstad> #link https://review.openstack.org/#/c/450415/ 18:13:42 <lbragstad> #link https://review.openstack.org/#/c/363765/ 18:13:46 <lbragstad> quotas ^ 18:13:49 <lbragstad> and limits^ 18:14:10 <lbragstad> actually, that's the wrong link 18:14:14 <lbragstad> #link https://review.openstack.org/#/c/455709/ 18:14:19 <lbragstad> quotas and limits ^ 18:16:08 <lbragstad> i think project tags is still on the roadmap 18:16:17 * lbragstad #link https://review.openstack.org/#/c/431785/ 18:16:35 <gagehugo> yeah ^ 18:17:10 <gagehugo> I can take a look at api keys as well, I think I understand it from what was discussed at the PTG 18:17:21 <gagehugo> It's definitely a useful feature 18:17:55 <lbragstad> gagehugo cool - the limits stuff is also going to be a big one since i know nova was staging work for Queens based on us getting limits implemented in Pike 18:18:15 <gagehugo> lbragstad yeah limits is a hot topic 18:18:36 <lbragstad> sdague has an initial interface defined for that work 18:18:55 <lbragstad> but we really need to review it 18:19:50 <lbragstad> i don't think the implementation should be too hard, its mostly designing the interface 18:20:14 <samueldmq> hi, sorry I am late 18:21:03 <samueldmq> cmurphy: congrats! 18:21:40 <cmurphy> :) 18:21:59 <lbragstad> am i missing anything specs wise? 18:23:57 <lbragstad> this is probably a loaded question - but is anyone looking to pick up any of the affected specs (outside of gagehugo looking into api-keys)? 18:25:15 <lbragstad> I can make a point to refactor or update the affected specs in review after the Forum 18:25:44 <lbragstad> i'm sure there is going to be talk about policy and limits at the Forum, and if that's an opportunity for us to get help then I'll leave it open 18:26:04 <lbragstad> otherwise, our priorities will rescope a bit for Pike given the circumstances 18:27:11 <lbragstad> #action lbragstad to update all specs after the forum with relevant discussions regarding updated Pike roadmap 18:27:23 <lbragstad> anyone have anything else? 18:28:34 <lbragstad> cool - looks like we'll get some time back today 18:28:39 <lbragstad> thanks for coming 18:28:42 <lbragstad> #endmeeting