18:00:02 #startmeeting keystone 18:00:03 Meeting started Tue Mar 6 18:00:02 2018 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 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:04 ping ayoung, breton, cmurphy, dstanek, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, lwanderley, kmalloc, rderose, rodrigods, samueldmq, spilla, aselius, dpar, jdennis, ruan_he 18:00:06 The meeting name has been set to 'keystone' 18:00:14 #link https://etherpad.openstack.org/p/keystone-weekly-meeting 18:00:17 agenda ^ 18:00:18 o/ 18:00:53 o/ 18:00:54 Hello 18:01:34 o/ 18:02:22 we have a pretty light agenda today - so we'll give it a minute or two for folks to show up[ 18:02:40 i also expect people to be recovering from travel or even still dealing with it 18:03:14 hey 18:03:53 we'll get started at 5 after 18:05:02 #topic trello board/rocky roadmap 18:05:08 just a heads up for everyone 18:05:23 i've spent the last few days in trello attempting to capture context from last week 18:05:30 #link https://trello.com/b/wmyzbFq5/keystone-rocky-roadmap 18:05:52 most of the larger initiatives should be captured accordingly 18:05:59 along with some of the one-off action items 18:06:28 hrybacki: and i will being going through it early next week, so there might be some changes between now and next weeks meeting 18:06:43 feel free to poke around and let me know if there is anything i missed 18:07:13 next week we'll focus on setting more realistic timelines and finding/updating ownership 18:07:18 #topic new meeting time 18:07:26 per the retrospective 18:07:35 we're going to move the keystone weekly meeting time 18:07:46 i plan to propose that change today 18:08:05 which might result in a different meeting room depending on availability 18:08:26 next week we'll plan to at least have the meeting 2 hours earlier 18:09:04 i'll send a note to the mailing list once the change is proposed 18:09:17 #info no policy meeting tomorrow 18:09:35 just a heads up here - but we're going to cut down on the frequency of the policy meetings on wednesday 18:09:56 we *might* just call for them on an as-needed basis 18:10:07 but - don't expect to have one tomorrow 18:10:16 #action lbragstad to propose new meeting time for keystone meeting 18:10:26 #action lbragstad to send note to mailing list about new meeting time 18:10:38 #action lbragstad to send reminder about policy meeting tomorrow 18:10:41 that's about all i had 18:10:45 #topic open discussion 18:10:52 floor is open if anyone has comments or questions 18:11:27 just FYI - it's WIP, but i plan to have a full summary of the PTG ready by the eod 18:12:24 lbragstad: how was the PTG overall? 18:12:32 i thought it went really well 18:13:04 imo - the big theme was integrating the stuff we did in Queens with other projects 18:13:18 cool. integrating is always great 18:13:32 and i thought we got plenty of feedback that push things forward from a cross-project perspective 18:13:39 o/ i'm sort of here via phone 18:13:52 cmurphy: tapping really fast, ahn? 18:13:53 :) 18:14:24 typing********8 18:14:51 is anyone else working on PTG summaries? or is there something you'd specifically like me to reference in mine? 18:15:07 i'm eorking on one 18:15:09 same 18:15:16 lots of ntes to go through 18:15:19 notes 18:15:30 cmurphy: knikolla awesome - i was hoping other would do one 18:15:33 others* 18:15:57 there is so much cross project context to go through 18:16:56 yep. writing is the best way to consolidate that info in a way that flows. 18:17:03 One thing I was going to ask about (and maybe this is related to the meeting time change for you all) is someone mentioned lsat week tht in your retrospective certain tools (infra hosted and otherwise) have been problematic for some devs? I'd be curious to hear more about that to make sure there isn't something more infra could be doing to help there 18:17:47 * lbragstad finds a link to the retro 18:17:55 #link v 18:17:59 #link https://trello.com/b/Vo6dRALh/keystone-queens-retrospective 18:18:02 dims had insights into that for huawei devs 18:18:34 that board is apparently not visible? 18:18:53 ah - hrybacki is the only admin 18:18:59 and it's only team visible 18:19:28 should probably make that open 18:19:29 irc is cmmonly blocked and there was some problrm (technical?) with responding to mailing lists 18:20:03 #action lbragstad to check with hrybacki on making the retro public 18:20:08 wxy could also speak about it but hes probably asleep 18:20:25 cmurphy: yeah - IRC was one of the big problems 18:20:33 iirc 18:20:47 trello was good because apparently they have access to that 18:21:03 i'm not sure what other dev tools there were 18:21:20 lbragstad: but no one else has access to trello :/ 18:21:45 i think email was one but i dont remember if it was a technical reason or a social one 18:22:10 cmurphy: i think it was social - they can get access to mailing list, but they don't always feel comfortable responding 18:22:18 clarkb: yeah :( 18:22:27 cmurphy: i think it was this one - v 18:22:37 #link https://trello.com/c/QldE5koC/40-is-there-another-type-of-asynch-communication-method-we-can-use-to-communicate-with-apac-contributors 18:23:18 lbragstad: yes. 18:23:24 discussion was both on technical and social barriers. 18:23:37 with irc being blocked, and mailing lists being a social barrier. 18:24:03 did we get info on where/how irc was being blocked? 18:24:05 how to encourage discussion with apac contributors, like etherpads wheere they can easily ++, or write a comment without committing to a full mail post. 18:24:23 (we don't have to solve all this now, but do want to help if infra can help) 18:24:35 clarkb: irc was blocked at work, and they don't always have computer access at home. (have to leave laptop at work) 18:24:58 yeah - most of the might be trying to follow discussions (in another language) on their phone 18:25:28 s/the/them/ 18:29:13 clarkb: in general infra hosted tools like gerrit and etherpad were said to be fine 18:29:26 gotcha. Let me know when that trello is opened up and I'll take a look at it in more detail 18:29:37 clarkb: ++ will do 18:29:42 thanks for checking in 18:30:01 clarkb: actually - do you know if you plan to follow up on the performance stuff we talked about last week/ 18:30:22 when we were talking about perf testing and dedicated hardware with mtreinish? 18:31:16 i remember the discussion wrapping up with talk about an email thread? 18:32:16 ya I actually ended up briefly talking about it with mnaser at the ptg 18:32:27 He had some ideas on the hosting side that I hadn't considered 18:32:39 (mostly how to orgnize that sort of thing) 18:32:53 oh - nice 18:33:32 lbragstad: maybe you can start a thread with some of your needs so they are written down and I can recap current infra abilities then we go get mnaser/mtreinish to chime in too 18:33:39 ^ :) 18:33:44 ++ 18:33:51 just to openstack-dev? 18:33:56 ya I think thats fine 18:34:01 ok - cool 18:34:18 #action lbragstad to write down performance testing needs in a note to the dev mailing list 18:35:50 anything else we want to cover today? 18:37:48 cool - well thanks for coming all 18:38:00 reminder office hours will be starting in about 20 minutes 18:38:05 #endmeeting