19:01:08 <notmyname> #startmeeting swift
19:01:09 <openstack> Meeting started Wed Mar 26 19:01:08 2014 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:01:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:01:12 <openstack> The meeting name has been set to 'swift'
19:01:31 <notmyname> #link https://wiki.openstack.org/wiki/Meetings/Swift
19:01:40 <notmyname> not a ton on the agenda today
19:01:57 <notmyname> first up, OpenStack Icehouse
19:02:02 <notmyname> #topic Icehouse
19:02:05 <torgomatic> Igloo?
19:02:15 <clayg> are we still doing that?
19:02:34 * peluse thinks of a cooler and then drifts to thiking of beer
19:02:51 <notmyname> we need to offer our sacrifice^Wrelease next week
19:03:09 <notmyname> ie our RC for the Icehouse integrated release
19:03:24 <peluse> what needs to get done?
19:03:50 <notmyname> looking at what's in master since 1.13.0 and what's proposed right now in gerrit, there isn't a lot of major stuff (yay frequent releases)
19:03:54 <zaitcev> I like the containeralias, but account ACLs are nice too.
19:04:06 <notmyname> therefore I'm leaning towards a 1.13.1 release, rather than 1.14.0
19:04:14 <notmyname> but if I've missed something, please let me know
19:04:15 <torgomatic> I'd like cross-account copy, but I think I saw there was some security problem...?
19:04:27 <notmyname> I updated the priority reviews wiki page https://wiki.openstack.org/wiki/Swift/PriorityReviews
19:04:40 <clayg> torgomatic: psssththt "security"
19:04:41 <notmyname> and there is a set of things that should be looked at with icehosue
19:05:02 <creiht> torgomatic: yeah I could copy an object from an account that I didn't have access to
19:05:05 <notmyname> the logging and range and md5 patches should go in pre-icehouse
19:05:37 <torgomatic> creiht: yeah, that seems bad... is that something we can fix in Swift, or does the auth system have to do it?
19:05:39 <creiht> unless I was doing something wrong (which wouldn't be the first time :))
19:05:46 <clayg> creiht: did you write a failing functests!  (dfg is all about the functests)
19:05:48 <creiht> torgomatic: not sure, haven't heard back from them yet
19:05:58 <creiht> clayg: dfg volunteered to work on that
19:06:10 * clayg hugs dfg
19:06:35 <creiht> clayg: still no guarantee... creating a reasonable test is a bit problematic for that one
19:06:45 <clayg> oh
19:07:29 <portante> 891883
19:07:32 <portante> 356902
19:07:33 <portante> 902626
19:07:34 <portante> 896105
19:07:43 <notmyname> that's numberwang
19:07:50 <portante> ah yeah, sorry
19:08:10 <portante> some one was talking about security? ;)
19:08:13 <notmyname> portante: are those the functest patches you've got WIP?
19:08:22 <portante> ;)
19:08:26 <zaitcev> no
19:08:56 <portante> working on the unit tests for the proxy logging fix
19:09:06 <notmyname> ah, cool. good.
19:09:29 <torgomatic> any thoughts on tests for the slo-range patch?
19:09:43 <notmyname> https://review.openstack.org/#/c/82895/
19:09:59 <portante> if I understood what that fix was about, ... sorry
19:10:03 <creiht> torgomatic: dfg is working on that
19:10:08 <portante> can somebody explain that offline?
19:10:08 <torgomatic> creiht: ok cool
19:10:38 <notmyname> ok, cool
19:10:55 <notmyname> so it looks like the manifest bugs (including logging) are being actively worked on, including tests
19:11:01 <notmyname> other stuff is being reviewed
19:11:05 <creiht> torgomatic: but like I told clayg, it is a bit tricky :)
19:11:10 <notmyname> and peluse clayg and torgomatic are busy with storage policies
19:11:38 <torgomatic> creiht: yeah, I could have sworn we had a functional test for that stuff already
19:11:44 <torgomatic> at least for the simple case
19:12:10 <notmyname> also, if you are going to atlanta and haven't registered yet with your ATC discount code, you should do that before friday. (do it now!)
19:12:50 <portante> and get your plane tickets before they go up!
19:12:57 * notmyname needs to do that today
19:13:06 <torgomatic> well yeah, after they go up it's a bit late to buy a ticket ;)
19:13:19 <notmyname> lol
19:13:25 * peluse gets it
19:13:28 <portante> nice
19:13:36 <zaitcev> wait, what
19:13:38 <notmyname> what other patches need to be in for icehouse?
19:13:45 <zaitcev> I thought discount expired on 3/22
19:13:56 <notmyname> zaitcev: they extended it to the 28th
19:14:03 <zaitcev> yay!!
19:14:13 <zaitcev> I just got budget today
19:14:17 <notmyname> awesome
19:15:43 <notmyname> it looks likely that we'll only have 8 sessions for swift at the summit. 15 have been proposed already
19:16:09 <notmyname> so I propose a cage match to the death
19:16:13 <peluse> better than having 15 slots and only 8 submissions
19:16:18 <notmyname> yes, true :-)
19:16:28 <peluse> I'm in on the cage match!
19:16:41 <notmyname> peluse: yeah, but you're bigger than anyone else ;-)
19:16:41 <cschwede_> notmyname: is this a fixed number?
19:16:54 <cschwede_> notmyname: or adopting to the number of submissions?
19:17:32 <clayg> notmyname: that's no joke peluse has guns
19:17:32 <notmyname> cschwede_: final schedules have yet to be approved, but it looks like we'll likely have 8 time slots, 40 minutes each
19:17:53 <peluse> heh
19:18:16 <notmyname> and please don't stop submitting session proposals.
19:18:18 <creiht> notmyname: :/
19:18:25 <creiht> about session slots
19:18:28 <notmyname> but don't assume every one will be accepted :-)
19:18:34 <notmyname> creiht: my thoughts exactly
19:18:39 <peluse> notmyname:  maybe we can collapse a few related ones into single sessions w/shorter summaries to at least socialize some ideas?
19:18:40 <cschwede_> hmm, too many interesting Swift summit proposals. Maybe do some of them outside the regular slots?
19:18:46 <notmyname> peluse: ya
19:18:51 <notmyname> cschwede_: possibly
19:18:57 <creiht> notmyname: is there a count for all the projects?
19:19:02 <notmyname> I think we may also have a designated unconference area
19:19:24 <peluse> there's always the local pub too
19:19:24 <notmyname> creiht: why would you ask questions you know that will make you sad?
19:19:31 <cschwede_> peluse: +1
19:19:33 <creiht> heh
19:20:08 <notmyname> ok, anything else for "The Road to Icehouse" (tm)?
19:20:40 <notmyname> ok
19:20:51 <creiht> notmyname: I wonder how that number gets calculated
19:20:55 <notmyname> I had py3 support in swiftlcient on the agenda, but I can't remember why I added that
19:21:14 <torgomatic> looks like people are working on it, which seems fine
19:21:21 <notmyname> ya
19:21:23 <notmyname> #topic open discussion
19:21:31 <peluse> Stop your grinnin' and drop your linen... acct head policy rollup has been approved (much thanks clayg and torgomatic!)
19:21:33 <creiht> notmyname: maybe about tests with py3 merge props?
19:21:58 <notmyname> creiht: ya, maybe. but that seems like a thing we shoudl do regardless
19:22:20 <creiht> yeah agreed, but just remember someone asking about that in channel
19:22:30 <creiht> so I was thinking maybe that's why you put it on there
19:22:34 <notmyname> any patch reviews or other issues that need to be brought up in today's meeting?
19:22:52 <peluse> just one I can catch up w/clayg about on the other channel
19:23:43 <notmyname> last call...
19:24:15 <notmyname> thanks for attending this week. keep up the good work!
19:24:17 <notmyname> #endmeeting