18:02:39 #startmeeting keystone 18:02:40 Meeting started Tue Sep 15 18:02:39 2015 UTC and is due to finish in 60 minutes. The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:02:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:02:43 o/ 18:02:44 The meeting name has been set to 'keystone' 18:02:49 bknudson is not allowed to lurk! 18:03:02 busted... 18:03:05 o/ 18:03:05 gotta see if i know all the irc meeting commands 18:03:06 morgan: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 18:03:08 no litterin, no divin, no lurkin 18:03:13 #link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting 18:03:15 #link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting 18:03:16 can you tell the difference between me lurking and not lurking? 18:03:21 damn it slow 18:03:29 wow short agenda 18:03:30 too many ptls 18:03:40 missing #endmeeting ? :p 18:03:40 hey o/ 18:03:45 anyway 18:03:49 it's turning into the republican presidential contest 18:03:55 lol 18:03:57 lol 18:03:58 stevemar: Liberty Release Management Housekeeping 18:04:00 #topic Liberty Release Management Housekeeping 18:04:00 whoever started the previous meeting needs to end it 18:04:02 o/ 18:04:07 ahhh no 18:04:10 ah, nvm 18:04:11 dolphm both steve and I started the meeting at the same time 18:04:17 my client was slow 18:04:21 i missed steve's :) 18:04:22 bah - agenda was full when i looked last night and decided to get up 18:04:25 you can #chair 18:04:27 I think 18:04:33 * morgan shrugs 18:04:40 anyway so this will be stupidly short 18:04:44 #chair morgan 18:04:54 tomorrow is the cut off for library releases 18:05:15 if we are doing more releases of the libraries tomorrow is when they go out before we have a stable/liberty branch 18:05:37 this means keystoneclient, middleware, keystoneauth, and pycadf will be released. land anything that needs to land today 18:06:06 once this revision of keystoneclient is released, session and anything that is moving to keystoneauth is frozen 18:06:15 we'll probably wind up backporting a fix for https://bugs.launchpad.net/keystonemiddleware/+bug/1494327 to ksm stable 18:06:17 Launchpad bug 1494327 in keystonemiddleware "DuplicateOptError intermittently breaks UT" [High,In progress] - Assigned to Dave Chen (wei-d-chen) 18:06:18 no more code unless it is a security flaw will be landed 18:06:21 \o 18:06:48 keystoneauth will likewise be in a holding pattern until we see some adoption (unless there is a bug) - no new features 18:06:53 there is a bug in auth_token tests that i don't think has been sorted out 18:06:54 bknudson: that would be nice 18:07:10 jamielennox: that is why bug fixes will be landed. 18:07:26 that specifically is something I wna tbefore we cut 1.0.1 if possible 18:07:38 erm. crud ksa vs auth_token 18:07:40 you know what i mean. 18:07:57 so lets resolve the bug in keystonemiddlewae.auth_token 18:08:13 there's a couple of proposed fixes, one from dave chen and one from me 18:08:20 lets see if they are landable 18:08:30 if we can get them in pre-stable cut, it would be easier 18:09:20 stevemar: #topic Keystone RC1 tracking 18:09:30 thx morgan 18:09:32 #topic Keystone RC1 tracking 18:09:45 when is rc1? 18:09:48 didn't know if you were done 18:09:49 Liberty RC1 is around the corner.. as in... next week 18:09:57 keystone seems pretty stable... let's rc1 now 18:10:06 what’s the status of any FFEs? 18:10:06 I'm going to drop open BPs from RC1 18:10:07 sooner we rc sooner we can work on M 18:10:11 #link https://wiki.openstack.org/wiki/Liberty_Release_Schedule 18:10:26 since I don't think we have any FFEs 18:10:32 (please correct me if I'm wrong) 18:10:38 approved FFEs 18:10:39 week of the 21st if the RC period bknudson 18:10:39 that is 18:10:40 Here's an easy fix: https://review.openstack.org/#/c/203047/ (has 2 +2) 18:11:15 bugs taged to RC1 need to be gating by thursday this week *or* will be dropped unless they are legitimately RC blockers 18:11:33 morgan: not arguing with the answer, but had not heard we had decided against all of the proposed FFes 18:11:33 please tag any new bugs that are potential rc blockers as the appropriate rc-potential 18:12:00 bknudson: tagging your bug for rc1 18:12:01 henrynash: i'm find if we have open FFEs just point them out. but they need to land this week 18:12:09 or be dropped 18:12:20 stevemar: we can always backport the fix, so shouldn't be an rc blocker 18:12:30 (Unrelated to FFEs) I’d like to push the last of the data driver testing in: https://review.openstack.org/#/c/154485/ 18:12:36 bknudson: if it's high/critical I'd like to land pre-RC 18:12:38 just needs another +2 18:12:47 bknudson: if it's lower than high prio we can backport if needed 18:12:57 has everything feature-y in review been -2'd? 18:13:07 dolphm: the ones I saw should be -2'd 18:13:16 please feel free to -2 if I missed one 18:13:22 or flag me down 18:13:41 morgan: alrighty, i definitely ran into one last night linked to a bp 18:14:27 morgan: https://review.openstack.org/#/c/210581/ 18:14:32 * morgan nods. 18:14:54 dolphm -2 applied 18:15:31 so, find me if we have any approved FFEs and they can land this week, i can unblock 18:15:33 aww i liked that one 18:15:45 otherwise defer until mitaka 18:16:05 I'd like to be RC-ready on friday 18:16:08 if at all possible 18:16:29 stevemar: #topic Next PTL and Summit Planning 18:16:39 * stevemar just realizes he's been calling it Mikata and not Mitaka 18:16:45 #topic Next PTL and Summit Planning 18:16:48 Mumble* 18:16:54 So as you know.. I wont be PTL next cycle 18:16:59 soon there will be a new PTL. 18:17:28 thanks for your service morgan :) 18:17:31 Once the election is finalized I am going to delegate the last of the release responsibilities to the new PTL. I'll be around to unblock things i've -2'd but I have some stuff that I need to take care of 18:17:34 ++ 18:17:47 hear, hear+++ 18:17:49 ++ 18:17:57 ++ 18:18:03 ++ 18:18:06 so it'll be on the new PTL to cover the last of the RC responisbilities and write up releasenotes. (and/or pull people in) 18:18:10 thanks morgan ++ 18:18:12 thanks for having me as the PTL for 2 cycles :) 18:18:45 morgan, those ++ are convertible to beers I think 18:18:46 and I will be taking a step back from keystone (not 100%) for a bit, just need some space to reset after the long haul 18:19:03 the post PTL black hole Say HI to Joew Heck for me 18:19:10 and Ziad 18:19:11 ayoung: hehe 18:19:20 ayoung: c'mon dolphm escaped 18:19:32 as for the summit planning, I am going to delegate all forward looking planning to stevemar, dstanek, and ayoung as they are running for PTL. We have our spaces lined up. 18:19:45 Please collaborate and start appropriate steps to plan the sessions. 18:19:47 dstanek's running? 18:19:55 and anyone else that still wants to throw their hat into the ring 18:19:55 gyee: he put is name into the repo 18:19:59 please do so. 18:20:07 ah, I missed the email then 18:20:10 yes, dstanek is running, too 18:20:12 no email yet afaik 18:20:15 gyee: yessir, going to send out an email to the list later, but i'm in the repo! 18:20:22 do you have to send an email? 18:20:27 bknudson: not technically 18:20:35 bknudson, no, but probably a good idea if you want a chance to win ;) 18:20:37 bknudson: new process only dictates a git review 18:20:38 dstanek: is trying to be sneaky! 18:20:39 unless running unapposed 18:20:46 morgan: ++ 18:20:50 looking forward to the big debate 18:21:06 its gonna be televised 18:21:07 so you three are on the hook to plan the summit sessions since that needs to start before the election is finalized 18:21:14 henrynash, gyee you guys should run, too 18:21:18 gyee: who will moderate? 18:21:24 as in.. sending the email to the ML, start getting feedback 18:21:25 etc 18:21:30 first question, what's your view on pagination? :) 18:21:43 i'll moderate... 18:21:43 gyee: ain't gonna happen! 18:21:45 I trust the eventual winner will finalize all the things 18:21:52 gyee: hey no starting the debate here 18:21:57 k, k 18:21:59 gyee: can't read a book without it 18:21:59 * morgan is still PTL and says "NO" 18:22:01 :P 18:22:06 morgan: yes yes, we'll play nice :) 18:22:16 ok 18:22:21 that is most of everything I had 18:22:34 summary: land things for libraries today, releases tomorrow 18:22:46 gyee, horizon guys are begging for pagination here 18:22:51 RC1 next week of keystone, any FFEs outstanding need to be in this week or punted 18:22:55 there's probably some other lib fixes we should get in. 18:23:15 amakarov: and we have addressed most of that on the ML. 18:23:25 amakarov: and the stance is fairly universal within the core team afaict 18:23:27 morgan, ++ 18:23:43 so. 18:23:48 23 minutes of meeting 18:23:58 stevemar: #topic open discussion (make it quick) 18:24:07 #topic open discussion 18:24:15 anything else? 18:24:18 is there a list of the most important things to get in for the libs? 18:24:19 I was expecting some Donald Trump-ism in the PTL emails, like I will find anyone one karma point per day till the bug is fixed! 18:24:31 s/find/fine/ 18:24:31 dstanek: no specific list atm. 18:24:37 I don’t understand the problem with pagination, with vitual screens, surely you can just have 100 screens displayes and see all teh users….then you can page youself! 18:24:40 dstanek: but please look over open bugs. 18:25:04 dstanek: do you want to generate the report for all bugs since Liberty has opened? 18:25:07 henrynash: it's implementation of pagination for users. the rest of the backends don't matter and we can do pagination 18:25:12 bknudson: anything? you normally have something :P 18:25:13 https://review.openstack.org/#/c/155758/ -- client but fix 18:25:22 I don't have anything in flight 18:25:30 morgan: twas a joke (!) 18:25:30 lies 18:25:33 browsers have builtin pagination and support for the PageUp and PageDown keys 18:25:37 henrynash: ah anyway 18:25:50 * morgan is losing ability to see sarcasm in irc ;) 18:26:00 morgan: :-) 18:26:13 oh - we had someone setup translation jobs for python-keystoneclient, should we be setting up translation jobs for all the libraries? 18:26:16 ookay please take bug discussions to -keystone and land the final bits so i can generate release reviews tonight/tomorrow 18:26:23 stevemar: there was a fix in flight to set that up 18:26:27 stevemar: not sure the status 18:26:45 stevemar: i'm going to let i18n team drive those 18:26:53 morgan: who’s running teh RC1 bug list? 18:26:58 if we ever do get translations we'll need another release. 18:27:09 well the way it was setup in ksc was broken. we fixed it there, and are adding the infra job now 18:27:11 henrynash: until next week, me, after PTL election the next PTL 18:27:12 so something isn't lining up. 18:27:18 ok, thx 18:27:21 bknudson: we wont get i18n stuff this cycle 18:27:29 ++ 18:27:35 it doesn't matter what cycle... 18:27:39 bknudson: the jobs may land but we probably wont get anything in liberty 18:27:42 we haven't gotten translations for keytsone either 18:27:59 should we fully support Fernet in Liberty..not make it default, but say it is out of incubation? 18:28:02 bknudson: translation work is on the way and usually land right around RC is cut 18:28:19 ayoung: I'm open to calling fernet stable 18:28:34 anyone for/against stable fernet in liberty? 18:28:48 before we call the meeting and return 30mins of everyone's time :) 18:29:06 lets all get time back 18:29:15 fernet is still not passing tempest 18:29:25 bknudson: ok that is enough we don't call it stable 18:29:29 so I am against saying fernet is stable 18:29:31 lets aim for first thing in mitaka 18:29:45 ++ 18:29:46 as well as making fernet default in devstack around the same time 18:29:51 ++ if we can't fix it sooner 18:29:55 I agree with that 18:30:02 good enough rationale here. but what if we do pass by release? 18:30:16 ayoung: if it is post RC answer is the same 18:30:18 because fixing those tempest test will require removal of sub-second precision in revocation events 18:30:18 unfortunately 18:30:25 which will be an api change 18:30:27 K 18:30:50 actually, we can't remove those, it will break other htings 18:31:00 ayoung: we can remove that but it's a bit more work 18:31:01 subsecond was in there due to the speed the tests run 18:31:15 so we need to fix our testing 18:31:20 which is fine 18:31:50 mock out time.utcnow etc, but it's something to aim for next cycle 18:32:15 anyway so fernet stable in mitaka, and default in devstack around then too 18:32:22 anything else before we're done? 18:32:33 3. 18:32:40 2. 18:32:44 1. 18:32:47 stevemar: #endmeeting 18:32:48 lots of plans for M 18:32:55 #endmeeting