19:00:02 <notmyname> #startmeeting swift
19:00:03 <openstack> Meeting started Wed Apr 29 19:00:02 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:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:07 <openstack> The meeting name has been set to 'swift'
19:00:11 <notmyname> hello, everyone
19:00:15 <mattoliverau> o/
19:00:17 <ho> o/
19:00:18 <jrichli> here
19:00:18 <notmyname> who's here for the swift meeting?
19:00:19 <kota_> hello
19:00:24 <imkarrer> o/
19:00:27 <gvernik> hello
19:00:29 <minwoob_> o/
19:01:19 <torgomatic> 😹
19:01:21 <wbhuber_> o/
19:01:24 <cutforth> o/
19:01:26 <peluse> hola
19:01:37 <notmyname> welcome!
19:01:55 <notmyname> today's agenda has one item: summit session prep
19:02:01 <notmyname> #link https://wiki.openstack.org/wiki/Meetings/Swift
19:02:13 <dmorita> hi
19:02:18 <notmyname> so before we get into the sessions, general info and helpful links
19:02:31 <notmyname> room layout for the technical sessions:
19:02:33 <notmyname> #link https://docs.google.com/spreadsheets/d/1VsFdRYGbX5eCde81XDV7TrPBfEC7cgtOFikruYmqbPY/edit#gid=569963128
19:02:45 <notmyname> the overall schedule:
19:02:46 <notmyname> #link https://www.openstack.org/summit/vancouver-2015/schedule/
19:03:03 <notmyname> you should have your passport by now. and probably flights and hotels
19:03:44 <notmyname> if you have a sched.org account, you can select the thigns you want to go to and download a calendar for you r phone
19:03:55 <notmyname> makes it easier to know where to be when
19:04:21 <notmyname> looks like it will be a busy week, but I think this will be one of the more productive summits for us
19:04:32 <mattoliverau> +1
19:04:40 <notmyname> I'm especially looking forward to the new technical track layout
19:04:48 <notmyname> there are 3 kinds of sessions
19:05:18 <notmyname> 1) fishbowl: large rooms, similar to previous summits. facilitated discussions with a large audience. we have 6 of these
19:05:55 <notmyname> 2) working sessions: small rooms, similar to the hackathons, focused discussions on specific things, write/review code. we have 10 of these
19:06:37 <notmyname> 3) "meetup": we have a room all day friday for an open space meetup with no specific schedule in it. similar to friday in paris last november
19:07:18 <notmyname> if you have specific conflicts (eg I think I might be giving a talk during one of the swift sessions), please let me know asap
19:07:28 <notmyname> and we'll see if something can be worked out
19:07:46 <notmyname> so...where are we right now?
19:07:58 <mattoliverau> at home :P
19:08:09 <notmyname> we've got the RC2 tagged. that will be released tomorrow at around 1400UTC as swift 2.3.0 in openstack kilo
19:08:28 <notmyname> thank you, again, for all your work on it
19:08:37 <peluse> way cool
19:08:45 <mattoliverau> awesome
19:09:07 <kota_> great
19:09:23 <dionkalo> ]
19:09:26 <notmyname> which brings us to "what's next", which is a perfect segue to the summit sessions (where we talk abotu what's going on and what's next)
19:09:31 <notmyname> #topic summit sessions
19:09:39 <notmyname> #link https://etherpad.openstack.org/p/liberty-swift-summit-topics
19:09:57 <notmyname> since last week, I've reorganized that etherpad
19:10:04 <notmyname> at the top are the fishbowl sessions
19:10:09 <notmyname> next are the working sessions
19:10:16 <notmyname> and at the bottom are the "overflow" sessions
19:10:31 <notmyname> I've got 6 fishbowls listed and IIRC 7 working sessions
19:10:36 <notmyname> so 2 things:
19:11:14 <notmyname> first, if your name is on one of the sessions, this week (today even!) make a etherpad with a high-level description or outline of the session and add it to this document
19:11:28 <peluse> hmmm, all I see are blank sections for fish/working at the top and then a lundry list of ideas
19:11:57 <notmyname> peluse: have you tried turning it off and back on?
19:12:27 <jrichli> lol - love that show
19:12:27 <peluse> oh, never mind :)
19:12:35 <notmyname> the linked etherpads can either be a scratch pad for ideas and we'll work through them as a group in the room. or they can be more of a place to collect thoughts for what needs to be discussed
19:12:38 <peluse> stuff at the top are definitions and then I see 'type' with each idea
19:13:17 <notmyname> remember that while there is a small about of "presentation", especially for fishbowls, these sessions are more of a conversation or discussion, not a lecture with a huge slide deck
19:13:36 <notmyname> I will be very happy to help anyone with prep for a particular session
19:14:06 <dmorita> notmyname: ok, i will prepare it
19:14:23 <notmyname> ok, the second thing is that I'd like to go over the sessions in the bottom overflow sessions to fill out the working rooms and prioritize
19:14:39 <notmyname> dmorita: thanks!
19:15:12 <notmyname> ok, first one to look at is python-swiftclient status and next steps
19:15:35 <notmyname> I think this is important, but there isn't yet actually any specific thing around it other than "we should do something"
19:15:59 <notmyname> what do you think? should we make sure this gets specific time, or leave it to more informal conversations?
19:16:53 <notmyname> ...not everyone at once...
19:16:55 <peluse> no input from clayg on this one?
19:17:13 <notmyname> clayg doesn't seem to be here :-(
19:17:20 <torgomatic> it's a long way between "ugh" and "here's how to fix it"
19:17:23 <peluse> seems like there's always plenty to talk about wrt client - at least last time anyways
19:17:25 <mattoliverau> hmm, I'm on the fence.. it is important, but do we have 40 minutes of conversation about it.. but it does need time i guess
19:17:49 <peluse> maybe call it "a bitch session" :)
19:17:52 <notmyname> ok, in my arbitrary scale, let's put it at a 7
19:18:05 <notmyname> ok, fast-post spec
19:18:12 <notmyname> acoles isn't here (he had a work dinner)
19:18:37 <notmyname> do we need a full working session on this, or do we really just need to get the spec landed and work through it?
19:18:47 <notmyname> (same question for all of the spec ones, actually)
19:18:50 <peluse> I've talked with him about a few of the tiems there, think its al stuff we will do
19:18:57 <peluse> so probably land it and do it
19:19:13 <torgomatic> probably the latter for this one; seems like we know *what* we want, it's just a matter of *how*
19:19:26 <notmyname> ok. priority 4
19:19:33 <torgomatic> discussion is more valuable when there are differing opinions on what to do IMO
19:19:44 <peluse> agreed
19:19:46 <notmyname> global cluster improvements
19:20:06 <notmyname> I think this one is low priority (I added it)
19:20:24 <notmyname> this should be more a response to what we're all seeing in prod, not ideas we come up with
19:20:35 <notmyname> however, if there are some specific things to bring up, that's good
19:20:47 <notmyname> anyone feel strongly about including this one in a working session?
19:21:17 <mattoliverau> sounds like a beer session ;P
19:21:31 <kota_> lol
19:21:44 <notmyname> I can't see your face, so typing "no" helps ;-)
19:21:50 <torgomatic> when the only tool you have is getting hammered, everything looks like a beer session ;)
19:21:56 <notmyname> lol
19:22:08 <gvernik> mattoliverau,: it's 6 am for you...and you already speak about beer? :)
19:22:11 * torgomatic doesn't care about this one
19:22:19 <notmyname> gvernik: he's australian. it's different there
19:22:25 <mattoliverau> gvernik: lol, 5:22 actaully :P
19:22:27 <notmyname> priority 1
19:22:30 <peluse> not different than AZ!
19:22:34 <notmyname> next
19:22:36 * cschwede just arrived - hello!
19:22:37 <notmyname> symlink spec
19:22:53 <notmyname> torgomatic: do you want a working session on symlinks?
19:22:58 <notmyname> cschwede: welcome
19:23:04 <torgomatic> notmyname: if we don't get the spec more hashed out by then, yes
19:23:04 <peluse> I think we have 3 somewhat related sessions, that one, the policy changing and the netapp tier'ing
19:23:20 <torgomatic> I could see that one going with policy-change, but not the tiering thing
19:23:31 <peluse> do we hold all 3 and then spend some time Fri to sort out overlap (or not)?
19:24:01 <peluse> well, tiering could be the decision engine that then uses policy change...
19:24:03 <notmyname> I'll mark them as potential candidates to combine
19:24:09 <mattoliverau> not a bad idea
19:24:24 <peluse> yeah, just so everyone knows there's some potential relation there
19:24:46 <notmyname> ok
19:24:48 <torgomatic> well, the difference is that I like symlinks, could tolerate policy changing, and dislike auto-tiering :)
19:24:55 <notmyname> :-)
19:25:19 <peluse> nice
19:25:32 <notmyname> object undelete spec
19:25:49 <notmyname> cschwede: does this need a formal working session?
19:26:13 <cschwede> notmyname: no, not a formal one. discussion on friday is enough i think
19:26:18 <notmyname> ok
19:26:47 <notmyname> same question for container alias spec
19:26:57 <cschwede> same answer :)
19:27:19 <notmyname> updateable object sysmeta
19:27:27 <notmyname> isn't this related to fast post?
19:27:39 <torgomatic> they're certainly playing in the same sandbox
19:28:02 <mattoliverau> i think it is
19:28:27 <notmyname> ok, I'll propose combining them and bring it up with acoles
19:28:48 <notmyname> next
19:28:58 <notmyname> metadata search / notifications
19:29:19 <notmyname> this is interesting, since it makes me think of zaqar  and their recent call for adoption
19:29:33 <notmyname> cschwede: is there a spec yet?
19:29:42 <cschwede> no, no spec yet
19:30:32 <notmyname> would anyone rank it as more important than a swiftclient session? how about more important than the fastpost/sysmeta one?
19:30:35 <torgomatic> I wonder if the zaqar folks would be open to a cross-project working session here
19:31:01 <notmyname> if we schedule it, I'll tag it as part of their track too
19:31:12 <notmyname> like I'll tag the ops session for ops
19:31:19 <torgomatic> as it stands now, I believe that you have to get all kinds of keystoney to talk to a zaqar instance; there's no signature-based auth or something that'd be nice for use from within Swift
19:31:20 <notmyname> so it shows up in multiple tracks
19:32:03 <notmyname> ok, but where does this one rank? do we choose it over sysmeta/fastpost?
19:32:15 <torgomatic> depends?
19:32:25 <torgomatic> if zaqar folks are going to show up, yes. otherwise, no. IMO
19:32:57 <notmyname> that makes sense. the summit is a perfect place for cross-project discussions
19:33:15 <vkmc> hey hey o/
19:33:28 <vkmc> I, in behalf of Zaqar team, I can say yes :)
19:33:28 <notmyname> of next up is kota_'s updates to container listings
19:33:34 <notmyname> vkmc: :-)
19:34:09 <notmyname> vkmc: should I ping you when it comes to scheduling to check for any potential conflicts?
19:34:21 <vkmc> please, feel free to ping me or flaper87 after the meeting or when you schedule the sessions
19:34:22 <vkmc> sure
19:34:31 <notmyname> ok
19:34:43 <notmyname> I will later this week when I start to schedule them
19:34:49 <vkmc> cool
19:35:16 <notmyname> ok, back to container listing updates
19:35:33 <notmyname> kota_: you proposed this one and said a friday discussion might be sufficient
19:35:58 <kota_> ya, we don't need 40 minutes for this one, I think.
19:36:06 <notmyname> what do we all think? keep it on friday or have a working session?
19:36:25 <peluse> fri
19:36:50 <notmyname> anyone want to argue for a working session?
19:36:58 <torgomatic> not I
19:37:14 <notmyname> ok. let's bring it up on friday
19:37:37 <notmyname> weekly meeting time is already a friday discussion and we havent' seen any hummingbird code so there's nothing to talk about there yet
19:37:47 <notmyname> that's the end of the overflow list. thanks
19:37:56 <notmyname> now...
19:38:06 <ho> sorry. I would like to put https://review.openstack.org/#/c/149930/ on a friday discussion.
19:38:38 <notmyname> ho: ok. add it to the etherpad and mention it for a friday session there
19:38:46 <notmyname> of the ones I had higher in the working sessions
19:38:49 <notmyname> large contaienrs
19:38:53 <ho> notmyname: thanks!
19:38:54 <notmyname> ec follow-on work
19:38:58 <notmyname> tiering
19:39:00 <notmyname> change policies
19:39:09 <notmyname> encryption
19:39:14 <notmyname> increase part_power
19:39:15 <notmyname> docs
19:39:35 <notmyname> are there any there that should be dropped in favor of another?
19:39:39 <mattoliverau> So as it stands we have 7 working (what your going through now), plus swiftclient, symlink and messaging making 10.
19:40:03 <dmorita> mattoliverau: sounds good
19:40:05 <kota_> sounds good
19:40:06 <notmyname> mattoliverau: yeah. i want to make sure the 7 I had aren't taking the place of one that we should have
19:40:20 <notmyname> specifically, the one I'm thinking of is the tiering one
19:40:35 <mattoliverau> i agree its good to go through and make sure :)
19:41:19 <mattoliverau> tiering could be replaced with fast post
19:42:14 <peluse> yeah but fast post isn't very controversial
19:42:19 <notmyname> on the other hand, tiering is one of those things that I hear a lot from customers
19:42:29 <notmyname> yeah. fast post is like "yes, ok just do it"
19:42:38 <mattoliverau> however 40 minutes of torgomatic rage would be awesome :P
19:42:44 <notmyname> lol
19:42:56 <mattoliverau> lets leave it then
19:42:58 * peluse thinks he'll just say 'this is stupid' and leave after 5 minutes :)
19:42:58 <notmyname> just withhold coffee that mornign for extra torgomatic smash!
19:43:40 <mattoliverau> lol, awesome t-shrit idea
19:43:48 <mattoliverau> torgomatic SMASH!
19:43:57 <kota_> lol
19:44:18 <torgomatic> swift is many things, but it is not many more
19:44:19 <notmyname> ok, unless I hear differently soon (ping me in IRC) I'll keep it pretty much the way it is and how mattoliverau said it above
19:44:37 <notmyname> and I'll start scheduling those later this week
19:44:53 <notmyname> thanks for helping me go through them. I'm looking forward to it
19:44:57 <notmyname> #topic open discussion
19:45:05 <notmyname> anything else to bring up in the meeting this week?
19:45:13 <dmorita> one question about summit.
19:45:14 <torgomatic> I want to drop py2.6 support in Swift after the Kilo release
19:45:26 <notmyname> dmorita: you first
19:45:35 <dmorita> general quesion. do you know what equipments are prepared in the room of design summit?
19:46:02 <notmyname> dmorita: generally we'll have a projector and a table and microphones (if the fishbowls are like the previous ones)
19:46:19 <notmyname> but that's a good question
19:46:27 <dmorita> ok. no change from previous summits. thanks.
19:46:31 <notmyname> AFAIK
19:46:42 <notmyname> I'll check with ttx to see if there is anything changed
19:46:46 <notmyname> torgomatic: your turn
19:47:08 <torgomatic> basically, any objections to dropping 2.6 support after Kilo?
19:47:13 <torgomatic> 2.6 is dead, dead, dead
19:47:19 <torgomatic> python core team won't touch it
19:47:28 <notmyname> lucid expires tomorrow IIRC. it had py26
19:47:35 <notmyname> what about centos/RH?
19:47:41 <torgomatic> I'm not sure
19:47:52 <notmyname> where's the red hat people?
19:47:59 <torgomatic> I think the latest one (6?) has 2.7 available, though it's not the default
19:48:13 <notmyname> does anyone here run on py26?
19:48:58 <notmyname> I think it's perfectly reasonable to drop py26 at this point. all of the major distros have py27 or don't even ship py26 anymore
19:49:12 <notmyname> I think we can assume that all new deployers will have py27
19:49:28 <notmyname> this is something that definitely needs to be asked of the operators
19:49:39 <torgomatic> plus, writing code for 2.7 + 3.4 is annoying but reasonable
19:49:46 <notmyname> torgomatic: rather than waiting for the summit, can you send an email to the operators mailing list about this?
19:49:46 <torgomatic> (or 3.X)
19:49:46 <mattoliverau> shall we bring it up at the ops session?
19:49:47 <cschwede> rhel6 uses py2.6 by default
19:49:56 <notmyname> cschwede: ah thanks
19:50:01 <torgomatic> 2.6, 2.7, and 3.X together is awful
19:50:11 <notmyname> cschwede: and I'm guessing it has support until about 2056?
19:50:19 <mattoliverau> lol
19:50:29 <cschwede> notmyname: close
19:50:31 <torgomatic> and now that eventlet supports py3, it's probably getting towards time to get Swift working over there at some point
19:50:34 <cschwede> ;)
19:50:47 <cschwede> i’ll check that, get back to you later
19:50:51 <notmyname> ok, thanks
19:50:56 <notmyname> torgomatic: can you send that email?
19:51:07 <torgomatic> notmyname: I'm not on the -operators list
19:51:14 * torgomatic already gets too much email
19:51:16 <notmyname> that's not hard to change ;-)
19:51:27 <notmyname> ok ok. I'll do it
19:51:31 <torgomatic> thanks
19:51:50 <mattoliverau> that's called deligating up :P
19:52:08 <torgomatic> :D
19:52:17 <notmyname> ok, anything else to bring up this week?
19:52:27 * torgomatic has nothing
19:53:02 <notmyname> thank you for coming today, and thanks for working on swift!
19:53:05 <notmyname> #endmeeting