19:01:01 #startmeeting swift 19:01:02 Meeting started Wed Jan 28 19:01:01 2015 UTC and is due to finish in 60 minutes. The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:01:06 The meeting name has been set to 'swift' 19:01:08 who's here for the swift meeting? 19:01:11 o/ 19:01:11 yo 19:01:13 o/ 19:01:13 o/ 19:01:15 hello 19:01:40 clayg: torgomatic: ping 19:01:43 hi 19:01:49 wat 19:01:51 #link https://wiki.openstack.org/wiki/Meetings/Swift 19:01:54 hello 19:02:14 not a ton to cover today 19:02:24 oh. hackathon isn't on there. that too 19:02:31 first up: swift 2.2.2 release 19:02:37 #topic swift 2.2.2 release 19:03:01 I'd like to see patches land today and tag an rc. then final release next week (on 2/2) 19:03:30 https://review.openstack.org/#/c/145970/ is the last substantive patch 19:03:39 zaitcev just added some comments 19:03:54 oh this is today? 19:03:56 zaitcev: looks like minor stuff, right? 19:04:00 yes 19:04:28 Like, one place adds '%' to end of output and the other does not. 19:04:33 the most important question is if this is the last one related to data placement that needs to land in this release 19:05:09 well - i mean... that's just like your *opinion* man 19:05:13 or are there other outstanding patches that need to land too 19:05:31 notmyname: did you already merge the one about... missing zero tier something 19:05:38 clayg: yup 19:05:45 then i'm good 19:05:58 great 19:06:26 I just proposed https://review.openstack.org/#/c/150909/ with the changelog updates 19:06:31 zaitcev is the main with making output/format on command line utilities better - if he has opinions on set_overload I'm happy to hand that off and take on the reviewer role 19:07:03 the data placement stuff is tricky, so please take a loot and make sure I said things clearly and correctly. I'd appreciate any help on it 19:08:06 notmyname: reads well to me 19:08:08 notmyname: changelog looks good to me, but then i’m biased because there are no real news for me ;) 19:08:36 me too 19:08:40 thanks 19:09:10 cschwede: heh. some of that data placement stuff is from you too. the first one about dancing partitions was something you saw, right? 19:09:35 ditto 19:10:16 zaitcev: on clayg's patch, are you ok with everything if the percent signs get consistent? 19:10:17 notmyname: hmm, or clayg or torgomatic - i think one of us saw this. not sure who was the first 19:10:28 notmyname: yes, +2 19:10:36 cschwede: I thought we both had customers with it (well, we did) 19:10:56 notmyname: yes, and we still have ;) 19:11:20 cschwede: so go +2 https://review.openstack.org/#/c/145970/ and we can get a release for you! ;-) 19:11:28 (after fixing % signs, of course) 19:12:03 clayg: will you have a change to push another patch set right after this, or would you like someone else to? 19:12:34 notmyname: i'm not entirely sure how zaitcev would like it to look and I *am* in the middle of something 19:12:53 zaitcev: can you push a new patchset there? 19:12:57 zaitcev: I'd just love you forever if you wanna go ahead and fix it for me 19:13:00 sure 19:13:04 thanks 19:13:05 woo hoo! thanks! 19:13:18 anything else on this release? questions or concerns? 19:13:40 change log looks good 19:13:49 tdasilva: thanks 19:13:50 not that i can think of.. but I'm not really that awake :P 19:14:00 zaitcev: can you keep a 0.6f output *somewhere* though? 19:14:35 clayg: I'll just keep it where you left it in parenthesis 19:14:47 notmyname: just a quick question on change log. do we ever add a note like: "for more info, read this: _link_" ? 19:14:57 i think that's it maybe for the the ring release (took us long enough) - but there's still tones of outstanding reviews that we need to keep on 19:15:01 tdasilva: yes. I've done that before 19:15:07 ^ i.e. no rest for anyone 19:15:10 clayg: yes absolutely 19:16:01 tdasilva: ya maybe a link to http://docs.openstack.org/developer/swift/overview_ring.html#overload is good 19:16:22 notmyname: yeah, that's what i was thinking 19:16:28 thanks. I'll add that 19:16:49 moving on 19:16:53 #topic hackathon 19:17:01 #link https://www.eventbrite.com/e/openstack-swift-hack-a-thon-sponsored-by-swiftstack-tickets-15226147818 19:17:24 it's just 2 weeks (1.5 weeks) away 19:17:31 I'm looking forward to seeing you here 19:17:41 if there are other people that need to come, please let me know. 19:17:52 * peluse start shining his shoes 19:18:10 I'm currently going through the registration list, and there is still some space if someone else needs to come 19:19:06 beyond the normal "here's some patches we should look at", I expect us to spend a lot of time on EC, some on encryption, and maybe a couple of other big things (sharded containers, fast-POST, ??) 19:19:31 please let me know asap if you have any concerns 19:19:41 notmyname: service tokens?? ;) 19:19:49 acoles: ah! that's the other one! 19:19:51 yes that 19:20:48 I expect EC to dominate. It was difficult for me to grasp. 19:20:50 maybe I'll get up to speed on EC on the flight over, it'll be long enough :P 19:21:10 #topic priority reviews 19:21:11 mattoliverau, don't count on it being long enough :) 19:21:17 heh 19:21:18 lol 19:21:36 so I'm working on https://wiki.openstack.org/wiki/Swift/PriorityReviews and there are a few good things listed there 19:21:47 but... 19:22:06 I need to update it. I expect to later this week. 19:22:18 that being said, what patches are on your mind that we need to look at? 19:23:00 I had a couple that _I_ needed to examine 19:23:35 oh, some are merged already (135102) 19:24:02 it would be great if people could start looking at object versioning, but not sure how "priority" it is... 19:24:29 tdasilva: link? 19:24:39 tdasilva: you're coming to the hackathon, right? 19:25:02 notmyname: yes 19:25:13 tdasilva: I think it would be great to look at it before and discuss it there :-) 19:25:23 #link: https://review.openstack.org/#/c/134347/ 19:25:36 thanks 19:26:33 tdasilva: why'd you move the doc? ...maybe we can address that later... 19:27:24 notmyname: ok 19:28:15 there's quite a few patches outstanding. whew. I'll go through them asap and get them sorted 19:28:42 tdasilva: do you have any specific questions to bring up in here about versioning? 19:29:31 notmyname: no, don't think so. clayg helped out a lot, so I think it is ready now 19:29:37 great! 19:29:46 any other patches to bring up in here with the group? 19:30:26 just fyi for anyone interested, I was posted the first "sinlge process" patch, and I expect Ignacio and I will be working on that during hackathon 19:30:46 it would be great to get other people looking at it.. 19:30:50 tdasilva, yes, I saw that! I am very intersted in that and will try to look before the SanFran party 19:30:56 https://review.openstack.org/#/c/149329/ 19:31:49 peluse: cool, thanks! 19:32:32 tdasilva: ok, I'll make a note of that too 19:32:39 #topic open discussion 19:32:43 anything else from anyone? 19:33:08 nothing important comes to mind 19:33:16 lunch comes to mind 19:33:19 FYI I'll have another ver of the EC reconstructor up soon and will the get the spec up to date with the current implementation 19:33:25 peluse: thanks 19:33:40 so that mattoliverau has something good to read on the way over :) 19:33:53 peluse: thanks ;) 19:33:56 peluse: a sleep aid? 19:34:37 what??? its like crack cocaine baby 19:34:43 lol 19:35:03 ok. let's call it 19:35:09 thanks for coming 19:35:12 #endmeeting