19:00:29 <notmyname> #startmeeting swift
19:00:30 <openstack> Meeting started Wed May 13 19:00:29 2015 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:31 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:34 <openstack> The meeting name has been set to 'swift'
19:00:40 <notmyname> who's here for the swift team meeting?
19:00:46 <aerwin> o/
19:00:47 <mahatic> me
19:00:47 <mattoliverau> o/
19:00:47 <gvernik> hello
19:00:47 <tdasilva> hello
19:00:47 <jrichli> o/
19:00:49 <cutforth> o/
19:00:49 <ho> o/
19:00:53 <imkarrer> o/
19:00:57 <acoles> here
19:01:00 <wbhuber> o/
19:01:00 <hurricanerix_> hi
19:01:03 <nadeem> hi
19:01:05 <mattoliverau> tdasilva: yay, your back!
19:01:23 <ho> tdasilva: welcome back!
19:01:35 <notmyname> tdasilva: I hope the family is doing well :-)
19:01:45 <mattoliverau> +10000
19:01:45 <tdasilva> thanks!!!
19:01:50 <tdasilva> family is great
19:01:55 <notmyname> good to hear
19:02:00 <tdasilva> everyone is doing well..baby is growing and healthy
19:02:14 <notmyname> we'll miss you next week, but I suppose "new baby" is an acceptable excuse ;-)
19:02:22 <tdasilva> :)
19:02:36 <torgomatic> 🙋
19:02:42 <notmyname> speaking of next week, that's the main thing to talk about today
19:02:43 <mattoliverau> lol, but by next summit, baby must be a swift contributor :P
19:02:49 <notmyname> #link https://wiki.openstack.org/wiki/Meetings/Swift
19:02:55 <kota_> hi, sorry be late a bit
19:02:56 <tdasilva> mattoliverau: lol
19:03:09 <notmyname> #topic summit prep
19:03:20 <notmyname> so, scheduling first
19:03:33 <notmyname> #link http://libertydesignsummit.sched.org/type/design+summit/Swift#.VVOgAGDFrxJ
19:03:41 <notmyname> that's the swift design summit stuff
19:03:53 <notmyname> and this is the full summit schedule
19:03:55 <notmyname> #link http://libertydesignsummit.sched.org
19:04:12 <notmyname> it has conference and design stuff on it, so it's your one place to look next week
19:04:40 <notmyname> that being said, there's actually one slot left over for Swift right now!
19:05:03 <notmyname> not that we dont' have stuff to talk about, but it seems I didn't take good enough notes for the last work session talk
19:05:04 <minwoob_> o/
19:05:13 <notmyname> so this is for the 4:30 slot on wednesday
19:05:30 <notmyname> #link https://etherpad.openstack.org/p/liberty-swift-summit-topics
19:05:36 <notmyname> there's the etherpad
19:05:51 <notmyname> so what's the topic that needs to be discussed in the last work session on wednesday?
19:06:22 <notmyname> fast post? undelete? sysmeta? ec test results?
19:06:42 <notmyname> I'm not sure what to put there. please help :-)
19:07:03 <gvernik> ec test results?
19:07:35 <acoles> notmyname: we have time on friday for 'leftovers' correct?
19:07:46 <notmyname> gvernik: we already have a fishbowl and a work session for EC stuff (overview and follow-on work). but several of us have been doing some tests locally and could share
19:07:48 <notmyname> acoles: yes
19:08:10 <notmyname> gvernik: ie instead of on friday or during hallway conversations
19:09:00 <gvernik> i would love to hear test results on ec...don't care on which slot or day :)
19:09:23 <notmyname> :-)
19:09:26 <acoles> notmyname: i'd be happy to lead a working session on fast post but feel i have talked a lot about it at hackathon
19:09:56 <notmyname> acoles: IIRC the summary was that there isn't a ton to talk about. more just need to actually type it in and review the code
19:10:45 <acoles> notmyname: its typed - modulo post EC conflicts, so yeah review would be great
19:11:05 <notmyname> yeah, we could do that. fast-post code review
19:11:06 <acoles> i hope to get the reviews back in shape before next week
19:11:22 <acoles> notmyname: so i am wondering if friday is best for that?
19:11:27 <notmyname> what do the rest of you think?
19:11:51 <acoles> do we have symlinks scheduled in a session?
19:12:00 <notmyname> no
19:12:33 <notmyname> https://review.openstack.org/#/c/173609/
19:12:47 <ho> I think "Sync up on related policy change working sessionsType" is a good candidate.
19:12:52 <notmyname> good grief. 5 +1s on there and nothing has landed?! ;-)
19:14:06 <notmyname> ho: that's not a bad idea. and it includes symlink talk
19:14:27 <notmyname> (peluse is not here right now)
19:14:42 <notmyname> acoles: what do you think?
19:15:06 <notmyname> and since acoles and ho are the only one's talking, then it looks like they get to set the topic ;-)
19:15:31 <mattoliverau> yeah, start with symlink and can push what we don't get to into friday
19:15:33 <acoles> yea, agree,
19:15:59 <jrichli> so, I am just gonna through this out there.  I was wondering if you all were interested in talking about what had to be changed to fix SL issues https://www.reddit.com/r/IBM/comments/31e3rh/ibm_gets_called_out_for_massive_system_failure_by/
19:16:02 <ho> agree
19:16:35 <notmyname> ok "Sync up on related policy changes" is a good one
19:16:54 <notmyname> jrichli: you should probably ask someone at IBM what they want to share :-)
19:17:10 <jrichli> Alan would like to share, i think
19:17:22 <jrichli> I talked with him yesterday.  but he thought all the schedule had been set.
19:17:23 <notmyname> ah? well that could be interesting then
19:17:33 <notmyname> acoles: mattoliverau: ho: what do you think?
19:17:39 <notmyname> an "ops war story"
19:17:58 * torgomatic likes war stories
19:18:11 <acoles> notmyname: agree, sync on policy changes for working session, fast-post for enthusiasts on friday
19:18:37 <notmyname> acoles: instead of the softlayer ops story?
19:18:52 <acoles> ah, i answered the wrong question :)
19:18:54 <notmyname> I'd prefer to hear from softlayer if they are willing to share. if not then do the other one
19:19:10 <jrichli> ajiang will be on in a min if you wanna chat with him about a work session
19:19:12 <notmyname> the other one == Sync up on related policy changes
19:19:14 <acoles> could the SL story be shared during the ops session, will it need its won session?
19:19:36 <notmyname> and there is ajiang :-)
19:19:46 <ajiang> Hey
19:20:05 <jrichli> you had told me that you might have some info to share on the SL issues, right?
19:20:06 <notmyname> ajiang: current topic being discussed is if softlayer shares about their recent swift issues and solutions, and if that should be a whole session or not
19:20:34 <ajiang> Janie told me there may be a chance for me to talk about the experience of SL swift cluster latency issue.
19:20:51 <notmyname> ajiang: we've got one currently unscheduled working session
19:21:34 <jrichli> ajiang: it would be wed at 4:30 for 40 mins
19:21:56 <notmyname> ajiang: so first question for you: are you willing/able to share?
19:22:11 <ajiang> @notmyname, that sounds good. The topic I would like to cover will be the analysis work I have done with Replicator/object server load and latency
19:22:17 <notmyname> acoles: do you not think it should be its own thing?
19:22:44 <ajiang> I think there are rooms for improvement on the object server/replicator i/o subsystem.
19:22:48 <notmyname> that sounds interesting to me
19:22:49 <acoles> i just wasn't sure how much content there would be but its sounding like there's plenty
19:22:55 <notmyname> ajiang: to put it mildly ;-)
19:23:10 <notmyname> cool. anyone opposed to that topic?
19:23:27 <mattoliverau> sounds like SL will be our last working session :)
19:23:31 <acoles> notmyname: +1 at summit i would favor things that are hard to do on gerrit ;)
19:23:38 <notmyname> :-)
19:23:38 <ho> sounds good
19:23:50 <ajiang> Based on the data I have, i can cover that 40 minutes with this one topic
19:24:45 <notmyname> ok. http://libertydesignsummit.sched.org/event/51d22ad3da43db0607e05a6c58cd1c14#.VVOk-GDFrxI
19:24:47 <notmyname> ajiang: thanks
19:24:53 <ajiang> thank you guys
19:24:57 <jrichli> +1
19:25:00 <notmyname> ajiang: please find me online or email me@not.mn for a more complete description
19:25:12 <notmyname> ok, let's move on in the meeting then
19:25:38 <notmyname> is there anything that anyone needs to get ready for the summit?
19:25:47 <notmyname> please don't hesitate to ask
19:26:02 <notmyname> I know for some it's your first OpenStack Summit. for others it's your 12th
19:26:29 <scotticus> my 4th. :)
19:26:34 <notmyname> any logisitics issues, any scheduling, any "I'm giving a talk and don't know what to do". please feel free to ask
19:27:13 <scotticus> when presenting...what hookups should we anticipate there being?
19:27:21 <scotticus> HDMI? DVI? VGA?
19:27:26 <scotticus> :)
19:27:31 <scotticus> asking the hard questions
19:27:38 <notmyname> scotticus: generally VGA and maybe HDMI. normally I either use HDMI or a VGA adaptor
19:28:00 <notmyname> scotticus: also, the screens are normally 16:9 aspect ratio
19:28:28 <scotticus> k, trying to think if i should leave my laptop at home :)
19:28:28 <notmyname> here's a fun trivia fact: this coming Sunday, May 17, is Swift's 5th birthday!
19:28:37 <mattoliverau> yay
19:28:42 <notmyname> 5 years ago Swift first went into prod at rackspace
19:29:25 <notmyname> on sunday night in vancouver, we (swiftstack) are hosting a small get-together of swift contributors and operators.
19:29:26 <notmyname> https://www.eventbrite.com/e/swift-birthday-bash-tickets-16964790144
19:29:42 <notmyname> I set up 40 tickets yesterday, and it looks like there are 8 left now :-)
19:30:06 <notmyname> so feel free to come. should be small and casual and fun seeing other swift people
19:30:31 <notmyname> (but please rsvp if you are coming. I want the right amount of food, and the venue isn't terribly big)
19:30:38 <kota_> great :)
19:30:52 <mahatic> nice!
19:30:58 <notmyname> anything else from anyone on the summit next week?
19:31:05 <mattoliverau> Got my ticket, I'll be the jetlagged Aussie in the corner :P
19:31:12 <mahatic> :D
19:31:31 <notmyname> this is a nice summit because it's in my same timezone!
19:31:58 <notmyname> ok, if nothing else on the summit...
19:32:01 <mattoliverau> Next one (japan) would be better for me :)
19:32:08 <notmyname> #topic open discussion
19:32:43 <notmyname> one thing I want to start being better about (after summit/summit prep) is how many specs we have
19:32:50 <kota_> mattoliverau: exactly
19:32:53 <notmyname> seems that we've got a lot out there, some with a lot of reviews
19:33:15 <notmyname> remember that specs are living documents. if you agree on something, land it! then edit it later as needed
19:33:32 <notmyname> specs are not documentation
19:34:19 <notmyname> I'll get back on the starred/priority reviews again after the summit, and I have some ideas on how to tackle some of the bug triage
19:34:27 <notmyname> also, because of the summit, no meeting next week
19:34:29 <clayg> "TBD" and "This should work" and "Also need to consider XYZ" are better than to much design up front
19:34:39 <notmyname> clayg: +1
19:35:03 <notmyname> so what else is on your mind? what else do you want to bring up this week?
19:35:31 <mattoliverau> I think we need to make the landed specs more visible, as atm the specs in review stand out. once that have landed aren't.. but that might just be me, and always having the dash boards up.
19:35:53 <notmyname> http://specs.openstack.org/openstack/swift-specs/
19:36:07 <notmyname> there's only 2 there (at the top)
19:36:22 <notmyname> 12 on the dashboard
19:36:30 <notmyname> (that should be reversed IMO)
19:36:33 <acoles> is there any way to auto link to a spec from a code review (like Reletaed-Spec) - i haven't found it? that would be useful
19:36:44 <notmyname> acoles: good question. I don't know
19:36:46 <acoles> Related-Spec would be even better ;)
19:37:01 <notmyname> I'll ask the gerrit experts (ie -infra)
19:37:45 <acoles> and then - if the dashboard could group code reviews with related specs, that would be cool
19:37:57 <acoles> notmyname: thx
19:38:04 <notmyname> acoles: and also make me lunch. and a pony!
19:38:07 <mattoliverau> want to add the specs link to the swift topic, or would that make it too long.
19:38:23 <notmyname> mattoliverau: I can do that. (also you can too, actually)
19:38:30 <acoles> notmyname: awww, we should have used the last working session for that ;)
19:38:40 * mattoliverau needs to learn this irc thing :P
19:39:06 <notmyname> acoles: I've wanted a unified code review + ideas + bug tool. haven't found one
19:39:19 <notmyname> anything else to bring up?
19:39:24 <acoles> notmyname: post-its?
19:40:44 <notmyname> ok, if nothing else, then let's call it
19:40:59 <notmyname> thanks for coming this week. I'm looking forward to seeing you in Canada!
19:41:04 <notmyname> #endmeeting