21:04:29 #startmeeting swift 21:04:30 Meeting started Wed Mar 9 21:04:29 2016 UTC and is due to finish in 60 minutes. The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:04:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:04:33 The meeting name has been set to 'swift' 21:04:37 swift team meeting time. who's here? 21:04:39 o/ 21:04:41 o/ 21:04:44 o/ 21:04:46 o/ 21:04:47 o/ 21:04:47 o/ 21:04:48 o/ 21:04:48 helo! 21:04:51 o/ 21:04:54 \o/ 21:04:56 o/ 21:05:01 hi 21:05:13 o/ 21:05:14 hi 21:05:24 great to see everyone 21:05:41 I want to keep this week's meeting fairly short 21:05:54 #topic hackathon summary 21:06:00 last week was the hackathon in bristol 21:06:13 acoles: thank you, again, for hosting and all the work you put in 21:06:17 it was a fantastic week 21:06:24 +1 21:06:32 +1 21:06:41 so great 21:06:49 It was nice to see you guys 21:06:57 thanks, we were glad to host you all 21:06:58 awesome work acoles! 21:07:07 o/ 21:07:15 I'd like to spend most of the meeting tim on this topic to hear from everyone (and share with those who weren't there) 21:07:29 what did you like? what can we improve? what are you happy got done? etc 21:07:33 o/ 21:08:19 personally, I found huge benefit in the conversations about the community itself. I've got several things to work on about how to track things, what to track, what *not* to track, etc. thank you for all your input 21:08:33 I'm also really happy that fast-post and the ops runbook docs landed 21:08:45 free baby sitting or birthing facilities for those of us who were home-ridden just in case :P 21:08:58 +1-- 21:09:00 +100 21:09:02 mattoliverau: we'll work on that for next time :-) 21:09:10 we missed mattoliverau 21:09:27 :-D 21:09:50 \o/ 21:09:58 notmyname: agree, discussions about community and process were good 21:10:03 what was another thing that happened last week that you enjoyed or found benefit in? 21:10:38 also good to get consensus on container sync patches 21:10:59 yep 21:11:12 as newcomer to community, insight/learning that's not possible via irc 21:11:25 I'll be bugging people about those in the days to come to see if we can get the container stuff into the next release 21:11:30 and meeting people in person! 21:11:38 seems like we planned out the topics pretty well. maybe the last couple days were harder to know what was being discussed when 21:11:58 * mattoliverau is looking forward to some summaries cause it sounds like he missed alot. 21:12:11 jirichli: exactly 21:12:30 yeah, it did feel like a bunch of topics got piled intot he last day 21:13:14 mattoliverau: mostly we were in a room and talked. then we all went to a different room and talked and ate. then we went to a different room and talked and had beer 21:13:29 dont forget the bus rides! 21:13:35 good conversations there 21:13:41 right 21:13:46 mattoliverau: and rarely we went to individual rooms and slept :) 21:14:00 notmyname: thanks :P Now I'm up to speed :P 21:14:10 oh yeah, the bus could have been better :/ 21:14:24 acoles: lol 21:14:28 so acoles provided us a bus to and from the HPE office. and we all rode it together instead of everyone coming and going at different times 21:14:48 the bus had the unintentional side effect of fostering a lot of good conversations it seems 21:14:50 acoles got a scare one day - was gonna order a bunch of taxis 21:15:10 single replica bus is not robust 21:15:17 lol 21:15:30 here's one summary thing that happend 21:15:35 multiple taxis are eventually consistant :P 21:15:37 we spent a lot of time talking about long review times 21:15:42 mattoliverau: lol 21:16:16 and the result is (1) prioritization of reviews is very imported instead of just number of patches reviewed. and (2) *good* reviews are very important to encourage 21:16:16 notmyname: so a long review on long reviews? 21:17:18 did clayg write something up about good reviews? i saw something, on github maybe, is it on gerrit? 21:17:27 also another think I'll try to facilitate going forward are some different ways to communicate with each other like voice and/or video chat. probably around a specific topic 21:17:30 acoles: yep 21:17:35 yeah, the reviewer guidelines 21:17:41 it looked great 21:17:42 sounded like we are gonna accept any form of communicating a design for now : you dont *have* to write a spec, right? 21:17:48 still in progress, but definitely a good idea to have 21:18:05 https://review.openstack.org/#/c/287616/ 21:18:05 notmyname: patch 287616 - swift - Adding review guidelines 21:19:10 so, other things talked about include global cluster improvements (including container sync). we made good progress there I hear 21:19:17 anyone want to give a better summary on that? 21:19:59 not everyone at once ;-) 21:20:32 ah yeah 21:20:33 I can give it a try 21:20:35 basically what I got from that is that we will continue to spend time improving obth 21:20:43 ah, good. go kota_ and tdasilva :-) 21:20:43 we reviewed use cases, pros/cons of container sync and global clusters, and agreed both were valuable features 21:20:47 as they help with different use cases 21:21:03 and both have some deficiencies which people are working on fixing 21:21:13 cool, +1 to that 21:21:17 yup, and i think we need something like table for users which staff is suitable for you use case in upstream docs. 21:21:19 understanding the pros/cons was very valuable to me 21:21:32 kota_: +1 21:22:07 i have a picture for the white board and am willing to write down in docs in the future. 21:22:15 yeah andy was really excited after that topic and started getting container sync into openstack-ansible 21:22:16 kota_: great :-) 21:22:25 we also talked about notifications, and that quickly went into the metadata search use case 21:22:35 and we talked with the searchlight team 21:23:11 the idea we came up with is something like container sync (its mechanisms to poll the container DBs) to directly feed the indexer instead of a message bus 21:23:14 great, seems to be hugh community interest in that one and I wasn't even there 21:23:16 (like rabbit) 21:23:49 joel and tim worked with alex on client docs and have some stuff in progress there 21:23:56 anything else to bring up? 21:24:06 there was a session on RBAC and policy which I missed 21:24:18 right. me too :-( 21:24:22 anyone here attend that? 21:24:27 ho_away: ? 21:24:40 acoles: we had a great explanation from donagh for it :-) 21:24:56 ho_away: oic. i must ask him for a replay! 21:25:02 thanks to jrichli and acoles on the the crypto status update 21:25:24 I think we also got a good plan on how we see it landing on master 21:25:26 yeah! the goal for crypto is to have a reasonably good feature branch by the summit 21:25:37 (and merging shortly thereafter) 21:25:47 jrichli: acoles: do I remember correctly? 21:25:57 notmyname: yes! and review the COPY as mw patches 21:25:58 notmyname: yes 21:26:16 lol 21:26:20 oh yeah, tdasilva gave great overview of whats happening with COPY moving to middleware 21:26:30 that hasn't landed yet? ;-) 21:26:43 lol, I was going to make the same joke :P 21:26:55 i saw some more +1 on one patch, thanks reviewers! 21:27:05 tdasilva: typey typey 21:27:12 :-) 21:27:19 mattoliverau: I think it's on us reviewers now! 21:27:21 mattoliverau: it's done...i'm just waiting for reviews :( 21:27:23 acoles: yeah, he gave us a good explanation why it is important (i also learned from it) 21:27:35 damn.. thats on me then :P 21:27:40 lol 21:27:52 mattoliverau: and clayg was badgering to get concurrent gets landed 21:27:59 what's typey typey for "go review" 21:28:17 starey starey 21:28:21 overall, to say again, it was a great week and very productive 21:28:34 just in general...I liked the way we chose the topics to discuss in Austin better than this time...just my 2 cents... 21:28:38 thank you to everyone who attended, and I hope everyone else will be at the next one :-) 21:28:54 tdasilva: that's good to know. I'll have to buy some more dot stickers ;-) 21:29:19 notmyname: hehehe...i think letting people rank what's important and focusing on that was nice 21:29:30 i guess it goes with the whole rocks and sands anology 21:29:44 yeah, I think I liked that better too. 21:30:00 ok, in the interest of time, I want to move on to some general stuff 21:30:11 #topic general summary of things 21:30:19 (how's that for a generic topic) 21:30:30 nice 21:30:40 I dont' want to discuss the per-release vs per-commit docs for swiftclient this week 21:30:51 we just cut a release last week, so frankly it doesn't matter too much now 21:31:09 I'm learning some about how they are built, so I think we may be able to have the best of both 21:31:18 speaking of releases... 21:31:36 we just did swiftclient 3.0.0, and that will be the final one (baring any security issues) for mitaka 21:31:51 and for swift itself, we'll have one more release scheduled for mitaka 21:32:01 our final date for that is the week of march 28 21:32:17 but I'll likely try to do it sooner than later 21:32:33 ie next week or the week after 21:33:06 later this week i'll start to organize the starred patches for what we should try to get in 21:33:14 speaking of starred patches... 21:33:33 community dashboard seems to be doing one of it's jobs... 21:33:33 http://not.mn/swift/swift_community_dashboard.html 21:33:41 only 8 unreviewed patches right now! 21:34:26 you all gave me a lot of feedback last week, so I'll be updating this page in the future 21:34:39 (specifically about measuring review vs owner timings 21:34:53 maybe a bunch of unreviewd patches got conflicted with current master :/ 21:35:17 and finally, (at least in the US) the daylight saving time starts this weekend, but we still will meet next week at 2100UTC 21:35:45 so for some of you, the meeting time will change. pay attention :-=) 21:36:04 and that's all I have for this week 21:36:14 anything else (please keep patch begging in -swift) 21:36:24 lol 21:36:54 3... 21:37:04 2... 21:37:22 1... 21:37:30 wait 21:37:32 jk 21:37:34 tdasilva: go 21:37:37 ok, fine 21:37:39 done 21:37:50 thanks for coming. thank you for your work on swift 21:37:53 #endmeeting