18:00:02 #startmeeting keystone 18:00:02 Meeting started Tue Oct 17 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:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:06 The meeting name has been set to 'keystone' 18:00:11 #link https://etherpad.openstack.org/p/keystone-weekly-meeting 18:00:14 agenda ^ 18:00:22 ping ayoung, breton, cmurphy, dstanek, edmondsw, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, lwanderley, kmalloc, rderose, rodrigods, samueldmq, spilla, aselius, dpar, SamYaple 18:00:25 o/ 18:00:26 o/ 18:00:28 o/ 18:00:31 o/ 18:00:42 o/ 18:00:43 o/ 18:01:05 zzzzz 18:01:20 o/ 18:01:34 o/ 18:03:02 #topic announcements 18:03:08 #info queens-1 is this week 18:03:09 o/ 18:03:26 as a result - i'll be looking to schedule a retrospective within the next two weeks to recap queens-1 18:03:51 i'm thinking we'll just hold it during office hours since folks are used to that time 18:04:18 #info specification proposal freeze is this week 18:04:43 if there is a spec you're working on that hasn't made it to review yet, be sure to at least push it by the end of the week 18:04:50 remember this is only proposal freeze 18:04:51 o/ 18:05:12 specification freeze will be queens-2 18:05:32 we also have a bunch of trello cards coming due this week 18:05:33 lbragstad: do we have any proposals we are expecting that haven't appeared yet? 18:05:34 lbragstad: is ther eanything on the top of your head we had planned and did not propose a spec for yet? 18:05:41 hmm .. .maybe the flask stuff 18:05:42 samueldmq +1 18:05:56 hrybacki: samueldmq not that i know of 18:06:10 * samueldmq nods 18:06:14 as far as i know, everything we discussed at the ptg has been recorded in trello 18:06:17 but... 18:06:32 we do need to make those changes consistent with the keystone-specs repository 18:07:18 (there are things we've committed to in trello that don't reflect that status in our specs repo) 18:08:12 we have a bunch of things due this week, according to the dates we set in trello 18:08:18 #link https://trello.com/c/b5ovuvqG/1-project-tags 18:08:38 the project tags implementation is looking good, imo 18:09:02 i feel like we can get the server bits merged by queens-1, and all the client bits by queens-2 18:09:48 sure 18:09:53 if you have spare review cycles - reviewing the project tags work would be awesome 18:10:12 #link https://trello.com/c/25sBHXcM/14-write-up-a-specification-for-json-web-tokens 18:10:23 thanks cmurphy for writing up the spec for ^ 18:10:36 reviews appreciated for that too 18:10:37 i think that looks really good 18:11:12 it'd be awesome to get that targeted for this release, but bandwidth is going to be hard 18:11:12 yeah that's on my todo reading list 18:11:37 either way - the spec does a great job of capturing the information and it should be an easy reproposal 18:11:55 #link https://trello.com/c/XTkAiqaB/21-remove-v20-apis 18:12:04 the last thing needed for ^ is a patch to tempest 18:12:22 the v2.0 documentation removal is being tracked in #link https://trello.com/c/5WCMxrLg/12-docs-goals-organization 18:12:54 but the removal card should be in Done by EOW so long as #link https://review.openstack.org/#/c/506751/ merges 18:13:26 #link https://trello.com/c/Z6pUPEJu/3-oslopolicy-deprecation is getting close - i spent more time than i expected on that last week 18:13:49 i also noticed the keystoneclient tests need to be updated after the v2 removal https://review.openstack.org/#/c/512509/ 18:14:40 cmurphy: aha - i assume there is more cleanup in ksc, too? 18:14:49 (cleaning up v2.0 paths, etc...) 18:15:02 probably 18:15:41 when should we focus on removing those bits? 18:15:47 that would make removing keystoneclient.session easier 18:15:54 removing the v2 bits 18:16:02 immediately? or should we allow for a grace period? 18:16:15 (if someone still wants to use v2.0 should we force them to use an older client?) 18:17:07 actually i don't think it makes sense to remove that from ksc right away 18:17:16 people are more likely to update their clients than their services 18:17:24 ++ 18:17:26 yeah... 18:17:41 should we table v2.0 removal from ksc and ksa for Rocky then? 18:19:18 +1 18:19:28 ok - i'll create a card in backlog 18:19:58 #action lbragstad to create a trello card in backlog to slate v2.0 removal paths from ksa and ksc for Rocky 18:20:08 #link https://trello.com/c/ZjsNk84y/4-oslopolicy-scope 18:20:12 this one is iffy 18:20:25 i'm going to be working on it today/tonight 18:20:37 it's pretty straight forward - but it needs reviews 18:20:53 I'm hoping to get it landed in oslo by queens-1 or very shortly after 18:21:25 #link https://trello.com/c/XzM8IXy4/10-cross-project-policy-work 18:21:40 this isn't necessarily due this week - but using it as a check point 18:21:57 lots of patches are in review 18:22:01 #link https://www.lbragstad.com/policy-burndown/ 18:22:12 only a few projects haven't started 18:22:37 wonderful to see more repos in progress than not 18:22:51 yeah - i was pretty stoked to see us get through 50% 18:23:23 for folks interested in that - the reviews are super helpful 18:23:50 ok - that's all i had for trello status 18:23:58 is there anything i missed that folks want to mention? 18:24:09 (with regard to what you're working on?) 18:24:47 can you filter cards by due dates? 18:24:47 it's not committed to in the trello board but i reproposed the app creds spec to queens just to get it in the queue 18:25:09 cmurphy: nice - i'll put that in progress 18:25:13 gagehugo: you can filter by labels 18:25:49 so we could make milestone labels and that would allow you to filter properly 18:26:08 ah ok 18:26:12 was just curious 18:26:26 ohhh you can actually. on the Trello menu, click 'Filter cards' and on the bottom you can pick some premade filters for date ranges 18:26:33 nice! 18:26:46 that's a new feature to me :) 18:26:53 #link https://trello.com/b/5F0h9Hoe/keystone?menu=filter&filter=due:month 18:27:40 #topic IAM session scheduling 18:27:46 #https://beta.doodle.com/poll/ntkpzgmcv3k6v5qu 18:28:02 #link https://beta.doodle.com/poll/ntkpzgmcv3k6v5qu 18:28:10 besure to fill that out if you plan to attend 18:28:28 i'll propose the session soon - but it will be next week sometime 18:28:36 i still haven't heard from zaneb 18:28:52 * samueldmq will make sure to review project-tags again. and jwt 18:29:16 so - be on the lookout of that if that's something you want to participate in 18:29:26 #topic openstack/loci CI and images 18:29:32 SamYaple: o/ 18:29:36 o/ 18:30:04 hey all. so a few months back i popped in talking about possibly putting dockerfiles in project repos 18:30:15 we scraped that idea and went with a new project called LOCI 18:30:38 great success has been made there, and with zuulv3 we now push directly to dockerhub on each commit to openstack/loci 18:30:57 our next step is to push images when projects commit themselves 18:31:16 we have done this with cinder already 18:31:17 #link https://review.openstack.org/#/c/512398/ 18:31:24 SamYaple: so you'll bake a new image with each commit to keystone? 18:31:30 and push! 18:31:31 yes 18:31:50 #link https://github.com/openstack/loci 18:32:00 now, keystone doesnt actually need to do anything here, this is a request from infra that we talk with all the projects before we add a job to thier post pipeline 18:32:12 but because its in the post pipeline, it wont affect keystone gating in anyway 18:32:32 so this is more of a social question than a technical one, is keystone ok with a loci job in the post pipeline? 18:33:21 i don't have an issue with it - the post pipeline seems like the appropriate place for something like this 18:33:51 does anyone have any questions or concerns about this? 18:34:31 seems awesome 18:34:33 SamYaple: how is keystone setup in the container? 18:34:35 what's the ultimate goal of this? 18:34:53 samueldmq: better CICD 18:34:59 lbragstad: pip installed 18:35:05 run devstack in containers ? and then run the tests? 18:35:09 running with Apache? 18:35:19 lbragstad: you can optionally install apache2 18:35:26 we actually use bindep to select profiles 18:35:38 like, create an image of keystoen each time dependencies change. ci can be: install lastest image (with deps preinstalled), just put the code in 18:35:40 and run the tests 18:36:04 samueldmq: we were just talking about that in the channel. i would love to get devstack using loci images, optionally, 18:36:26 there is a time delay between merge and post job that might make it bad for gates, but it should be fine for general dev 18:37:45 sounds interesting 18:38:15 that sounds very cool 18:38:19 where does it publish to? tarballs.o.o? 18:38:29 lbragstad: we only install uwsgi by default, but `docker build https://github.com/openstack/loci.git --build-arg PROJECT=keystone --build-arg PROFILES="apache"` 18:38:32 cmurphy: dockerhub 18:38:46 SamYaple: aha - nice 18:38:54 SamYaple: so what if dockerhub is down? does that delay the gate job? 18:38:56 we actually had to get some new syntax into bindep to get this to work but https://review.openstack.org/#/c/512063/3/bindep.txt 18:39:05 cmurphy: not at all. this is post pipeline 18:39:27 okay, no objections from me :) 18:39:34 technically the post job can fail and we wont push for that commit, so there is a small risk of not pushing, same with not publishing tarballs 18:40:03 so you only push what you bless through testing 18:40:26 unfortunately, zuulv3 doesnt have that part figured out yet 18:40:36 so no matter what we test, what we push is "build only" 18:40:43 ah 18:40:50 once zuulv3 lets us share artifacts across jobs then testing and pushing can work 18:41:09 yeah - i'm good with this then 18:41:18 let us know if you need signoff on a commit 18:41:28 ok i will submit the patch to project-config and ask for a signoff in the channel 18:41:38 awesome - thanks SamYaple 18:41:39 thanks all! and if you ahve more questions, #openstack-loci 18:41:52 will do! 18:42:00 #topic open discussion 18:42:05 floor is open 18:42:26 gentle reminder that office hours will be happening today 18:43:12 we can focus on bugs or use the time to crush some spec reviews together 18:45:30 if there is nothing else - we can break for a bit before office-hours 18:46:11 thanks for coming! 18:46:15 #endmeeting