21:00:21 <notmyname> #startmeeting swift
21:00:22 <openstack> Meeting started Wed Feb 15 21:00:21 2017 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:24 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:26 <openstack> The meeting name has been set to 'swift'
21:00:29 <notmyname> who's here for the swift team meeting?
21:00:32 <mattoliverau> o/
21:00:32 <torgomatic> .
21:00:32 <jrichli> o/
21:00:34 <joeljwright> evenin
21:00:38 <jungleboyj> o/
21:00:41 <mmotiani_> o/
21:00:42 <cschwede_> o/
21:00:43 <mathiasb> o/
21:00:43 <sgundur> hi
21:00:45 <pdardeau_> hi
21:00:46 <kota_> hi
21:01:23 <notmyname> clayg_: timburke: ping
21:01:27 <acoles> hi
21:01:28 <notmyname> welcome, everyone
21:01:33 <notmyname> welcome back acoles
21:01:36 <timburke> i'm here, i'm here!
21:01:41 <acoles> thanks
21:01:50 <notmyname> agenda this week is at...
21:01:51 <notmyname> #link https://wiki.openstack.org/wiki/Meetings/Swift
21:02:01 <tdasilva> hi
21:02:02 <notmyname> I want to cover the release and the PTG
21:02:28 <notmyname> #topic ocata release
21:02:47 <notmyname> as you know, this week (ie tomorrow) is the release deadline for openstack ocata
21:03:02 <notmyname> we'll be releasing swift 2.13.0. spoiler: it's the best one yet
21:03:17 <notmyname> I've got an authors/changelog patch up at https://review.openstack.org/#/c/434081/
21:03:23 <jungleboyj> :-)
21:03:24 <notmyname> thanks for all the comments on it
21:04:09 <notmyname> I've addressed the open ones, and I'm currently translating the changelog to yaml for the reno dir tree. then I'll push that patch, and I expect it to be the one that lands (but i'll ask for a few extra eyes for quick checks)
21:04:26 <notmyname> and then when it lands we'll have the SHA for the release and I'll push that to the openstack-release repo
21:04:52 <notmyname> so we are or will be waiting on two things: me, to typey type and the gate queue
21:04:58 <timburke> are we finally going to get our linky? as i recall, we don't have that yet...
21:05:24 <notmyname> thank you to everything who contributed to swift in this release. there's a lot of good improvements
21:05:51 <notmyname> timburke: I don't think so. I think there's another repos somewhere where we need to set up a job or reference the right thing or something
21:05:58 <notmyname> timburke: would be great though
21:06:24 <notmyname> so two key points about the release
21:06:34 <notmyname> first, please don't land anything else right now :-)
21:06:52 <notmyname> second, note that neither part power increase nor replicated ec fragments will be in the release
21:07:21 <notmyname> ont eh second note, I would have loved to see them in teh release (especially part power increase), but the release is in no way "bad" without them
21:07:40 <notmyname> just means we'll land them soon and the next release will be that much better ;-)
21:08:00 <notmyname> I know there's been a lot of work put in to those, especially over the last couple of weeks. thank you for that
21:08:04 <mattoliverau> and we'll have a cycle to make them even betterer
21:08:14 <notmyname> yup :-)
21:08:24 <notmyname> and actually have full global ec suppprt?
21:08:30 <mattoliverau> \o/
21:08:35 <kota_> :-D
21:08:43 <joeljwright> :)
21:08:57 <notmyname> one interesting thing I noticed today about this release: I don't think there's a single CVE in it. I don't think that's good or bad, it's just interesting
21:09:26 <timburke> notmyname: i'll have to work on that for next time ;-)
21:09:30 <jungleboyj> We also go back to the normal release length now.  :-)
21:09:30 <notmyname> like not just 2.13.0, but all of ocata (anything after 2.10.0)
21:09:50 <notmyname> jungleboyj: yeah, but as cycle-with-intermediary, it's not a huge change either way
21:10:04 <notmyname> timburke: going to code up some buffer overflows?
21:10:12 <jungleboyj> Ahh, yeah ... sorry, Cinder head invading.  ;-)
21:10:13 <timburke> naturally
21:10:23 <notmyname> any questions from anyone about this release?
21:10:58 <notmyname> ok, let's move on
21:11:03 <notmyname> #topic PTG next week
21:11:06 <notmyname> #link https://etherpad.openstack.org/p/swift-ptg-pike
21:11:11 <notmyname> there's the scheduling etherpad
21:11:22 <notmyname> just for the record, there will be no weekly IRC meeting next week
21:11:29 <notmyname> in lieu of the ptg
21:12:21 <notmyname> after I get the release notes for 2.13 pushed, I'll be organizing the etherpad into blocks of topics so that there's as little overlap of interested people as possible
21:12:49 <notmyname> but remember that the three days we've got in our room will be lots of conversations at once
21:13:12 <notmyname> so that being said, come prepared to talk and to listen :-)
21:13:16 <mattoliverau> so use your inside voice? I don't have one of those :P
21:13:55 <notmyname> mattoliverau: I'm looking forward to your sharding topic. ready?
21:14:15 <mattoliverau> sure am.. ready as I'll ever be :)
21:14:26 <mattoliverau> there is some rough documentation up.
21:15:06 <notmyname> /going down the etherpad...
21:15:19 <notmyname> there's two topics related to golang object servers and another about the TC not-python rules
21:15:36 <notmyname> I'll be organizing some info on the TC rules so we can discuss that
21:16:02 <notmyname> I'm hoping that zaitcev, clayg_, and kota_ can help organize the golang stuff
21:16:04 <clayg_> was that today?
21:16:18 <notmyname> those names chosen because they're the 3 common names on those topics :-)
21:16:32 <clayg> i hate the reconstructor; i hate all rebalances
21:17:18 <notmyname> kota_: looks like good notes on the global ec topic. anything you need from the rest of us on that topic?
21:17:18 * cschwede_ nods in clayg's direction
21:17:33 <notmyname> global ec includes composite rings discussion
21:18:13 <kota_> notmyname: i think i added all i thought if i remember all things :P
21:18:20 <notmyname> heh, ok :-)
21:18:34 <notmyname> kota_: will kazuhiro be there?
21:18:41 <kota_> notmyname: sure
21:18:45 <notmyname> great
21:19:24 <notmyname> between kazuhiro, kota_, tdasilva, jrichli, we'll cover policy migration, auto tiering, and symlinks. anything you need from the rest of us before we all get togehter?
21:20:29 <notmyname> ...I'm going to assume that's a "no, you're all good" ;-)
21:20:40 <tdasilva> sorry, yeah, i'm all good
21:20:40 <clayg> notmyname: or a ring zipper!
21:20:45 <jrichli> +1
21:20:50 <notmyname> clayg: write it down! :-)
21:20:54 <tdasilva> hoping to have new version of symlink until then
21:20:57 <clayg> what are we doing?
21:21:19 <notmyname> tdasilva: high-latency middleware? do you know more about that or need anything? (you put your name down on it)
21:21:34 <tdasilva> there's a meeting tonight
21:21:37 <tdasilva> at 4am EST
21:21:38 <tdasilva> :D
21:21:41 <notmyname> tdasilva: sorry, media. not middleware
21:21:45 <notmyname> yikes!
21:21:54 <jrichli> lol
21:21:55 <notmyname> high latency middleware would be bad
21:22:01 <mattoliverau> lol
21:22:03 <kota_> lol
21:22:24 <tdasilva> what i know is that they have been meeting constantly and I'm guessing slavisa and others will be there at the PTG??
21:22:31 <notmyname> cool
21:22:39 <tdasilva> i'd like to follow up on how they are doing
21:22:40 <notmyname> on the sync to elasticsearch topic, I'll bug timur about it to make sure he's got what he needs
21:22:42 <jungleboyj> I think I have seen some high latency middleware before.
21:22:54 <notmyname> jungleboyj: I think I've written some! ;-)
21:23:01 <jungleboyj> :-)
21:23:25 <clayg> will the people driving that topic be there?
21:23:27 <timburke> fah. let's put it in the server itsefl! https://github.com/openstack/swift/blob/master/swift/obj/server.py#L132
21:23:33 <notmyname> cschwede_: are you good on part power increase topic? I'm assuming that the only "discussion" by next week is who buys the beers
21:23:35 <mattoliverau> there is the slowdown middleware thats great for testing, but hopefully noone is using in prod :P
21:23:42 <tdasilva> clayg: HLM? i believe slavisa will be there
21:24:07 <cschwede_> notmyname: well, that would be a great topic actually ;) i'm fine with partpower increasing
21:24:09 <clayg> mattoliverau: oh yeah i forgot about that guy!
21:25:00 <notmyname> ok, I've talked to romain about the small files storage topic. they've done some pretty cool investigation at OVH and are interested in working on that further
21:25:23 <notmyname> current OVH info on that is at https://wiki.openstack.org/wiki/Swift/ideas/small_files/experimentations
21:25:24 <kota_> cool
21:25:31 <notmyname> so read up on it so we can jump right in
21:25:40 <mattoliverau> nice
21:25:53 <notmyname> jrichli: notifications? good to go there? need anything from the rest of us before next week?
21:26:03 <jrichli> good to go
21:26:12 <notmyname> jrichli: and keymaster v2?
21:26:21 <jrichli> mathiasb would be the one to ask
21:26:37 <jrichli> but if he isn't here, i can ask him.
21:26:41 <mathiasb> I'll be there for keymaster v2
21:26:42 <notmyname> mathiasb: question to you. need anything for us before next week?
21:26:48 <notmyname> for that topic?
21:26:58 <mathiasb> no, I think we're good
21:27:00 <notmyname> kk
21:27:06 <notmyname> jrichli: and container sync?
21:27:28 <jrichli> good to go.  not sure if we will get to that, anyway.  so many topics!
21:27:52 <tdasilva> lol, hackaton was hard to cover everything in 5 days, now we only have 3
21:28:03 <tdasilva> actually it was 4 days
21:28:07 <notmyname> cschwede_: tdasilva: kota_: ring management topic. need anything from the group before next week? anything we can be reading over?
21:28:25 <jungleboyj> tdasilva: Cinder team has the same worry.  Will be interesting to see how this PTG thing works out.
21:28:37 <tdasilva> jungleboyj: yeah, agree
21:28:45 <clarkb> technically the full event is 5 days...
21:28:48 <cschwede_> notmyname: not yet, i might write something down during my flight in
21:28:53 <notmyname> cschwede_: ok, thanks
21:29:22 <notmyname> acoles: kota_: the topic of ec issues. good to go on that? anything the rest of us can do before next week?
21:29:57 <notmyname> clarkb: just talking about the stuff we need to cover that's swift-specific that we've got a room for. not knocking the other two days :-)
21:30:20 <kota_> that is a list we're currently tracking, if anyone else notice another issue, please feel free to add your issue over there.
21:30:26 <notmyname> ok
21:30:46 <notmyname> kota_: tdasilva: pyeclib/libec work? consolidation, etc?
21:31:04 <acoles> notmyname: yes, ok for the ec issues
21:31:11 <tdasilva> nothing from me atm, hoping we can discuss there what we would like it to be
21:31:16 <notmyname> ok
21:31:17 <tdasilva> and maybe we can even chat with infra guys
21:31:21 <kota_> tdasilva: true
21:31:23 <tdasilva> is onovy going to be there?
21:31:29 <notmyname> kota_: timburke: swift3 work? do we need a topic?
21:32:07 <kota_> notmyname: I don't have special for swift community but I think we still have some conversation while PTG
21:32:13 <notmyname> kota_: ok
21:32:19 <kota_> so adding for notifiycation we will have that
21:32:41 <kota_> and if anyone is interested in, welcome for joining that.
21:32:56 <kota_> for swift3
21:33:08 <notmyname> tdasilva: I don't know if onovy will be there.
21:33:15 <tdasilva> notmyname: ack
21:33:44 <notmyname> there's also a note from eranrom that there's some storlet topics and they've got a room too
21:33:45 <tdasilva> notmyname: i'll ping him tomorrow to check and try to get some input from him in case he is not making it
21:34:05 <notmyname> tdasilva: great. (would also be nice to check with him in light of zigo's email this morning re packaging)
21:34:19 <notmyname> ok, that's the topics we have on the etherpad
21:34:24 <tdasilva> yeah, i saw that...ok, i will ask him
21:34:52 <notmyname> since we've only got 3 days instead of the 4 we'd have at a hackathon, we WILL NOT be spending time at the front building a schedule and doing dots or anything
21:35:06 <clayg> notmyname: WATH!?
21:35:07 <notmyname> so if there's somethign you want to talk about, PUT IT ON THE ETHERPAD :-)
21:35:12 <clayg> how do you even hackathon without dots!?
21:35:17 <clayg> i'm so confused
21:35:19 <tdasilva> lol
21:35:28 * notmyname gives clayg a hug
21:35:37 * clayg deep breaths - i'm sure notmyname has got this
21:35:55 <notmyname> there will be a small amount of logistics just to see that we're getting stuff covered. and you know me. I like to talk ;-)
21:36:13 <clayg> that's true
21:36:19 <mattoliverau> and show graphs ;)
21:36:20 <notmyname> so first question: what's left off of the etherpad right now?
21:36:31 <tdasilva> notmyname: i do have a question. Do we know who is going to be there on Monday/Tuesday and assuming we might be able to find a corner somewhere are there any topics that could or could not be discussed in those two days?
21:36:36 <notmyname> mattoliverau: graphs are great. talking about graphs? just wonderful
21:36:50 <notmyname> tdasilva: I want to come back to mon/tues in just a bit
21:37:01 <tdasilva> ok
21:37:06 <notmyname> first, anything left off for wed-fri that we know of right now?
21:37:36 <clayg> basically this is last call for https://etherpad.openstack.org/p/swift-ptg-pike right?
21:37:54 <notmyname> sortof
21:38:03 <notmyname> we can add stuff as we go, of course
21:38:09 <mattoliverau> not that I can think of in my under caffenated state.
21:38:10 <clayg> we've had that link in the last three meetings and everytime I look it it has more good stuff - but my stuff is already on there - so ... if you haven't got your stuff on there?  WTF are you doing?
21:38:14 <clayg> :P
21:38:16 <notmyname> but we won't be "together" like this any more
21:38:32 <notmyname> ...before atlanta
21:38:43 <notmyname> sorry. kinda awkward return placement there
21:39:09 <notmyname> sounded like we were all dying or something. EVERYTHIGN IS FINE
21:39:18 <cschwede_> phew!
21:39:24 <notmyname> ok, let's talk mon/tues then
21:39:49 <notmyname> from what I've heard, i think most people will be there all week, but there's probablty about 1/3 of us who will only be there wed-fri
21:40:07 <notmyname> #link https://wiki.openstack.org/wiki/PTG/Pike/Etherpads
21:40:21 <notmyname> that's got the links for all the etherpads
21:40:31 <notmyname> AFAIK there is not an overall schedule
21:40:58 <notmyname> so I think we will need to look at each of those mon/tues ones and figure out where we need to be and when we need to be there
21:41:08 <kota_> why don't you add the list of names who's be in which day in the etherpad?
21:41:16 <clarkb> there is for the shared "projector/discussion/Iforgetwhatitscalled" rooms but otherwise I think the idea was to use #openstack-ptg to coordinate things
21:41:16 <notmyname> kota_: that's a great idea
21:41:40 <notmyname> clarkb: where's the schedule for that shared room?
21:42:02 <notmyname> I guess i missed the #openstack-ptg channel info
21:42:09 <clarkb> https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms (its on the wiki page you linked)
21:42:12 <notmyname> /join #openstack-ptg
21:42:21 <clarkb> right at the top above "only monday"
21:42:47 <notmyname> to be fair, it's very tiny words ;-)
21:43:31 <notmyname> does anyone think we'll need a projector for a particular topic?
21:43:35 <clayg> clarkb: I would like my monday and maybe tuesday to be sitting in a room of people who know enough stuff about devstack that when I say "I hate out devstack's swift support does xyz and I changed like this" they can say - "sure that's fine" - or "no you're stupid"
21:44:15 <notmyname> if so, we'll need to reserve the projector room and move over there. I'd suggest trying not to need a projector
21:44:16 <clayg> i may just wander around yelling devstack until someone stops me
21:44:27 <clarkb> clayg: you want to find the QA room
21:44:34 <clarkb> I think that would be a good place for doing such things
21:46:37 <notmyname> what are other cross-project stuff we need to be yelling about on mon-tues?
21:46:42 <notmyname> tdasilva: what'd you have in mind?
21:47:00 <notmyname> tdasilva: or are you just wanting to find other swift people on mon/tues? ;-)
21:47:36 <tdasilva> notmyname: i was just wondering if it does happen that a group of swift folks end up spending a couple hours together mon or tuesday if there was any topic that could be discussed
21:47:45 <tdasilva> as to make time for the wed-friday discussiosn
21:47:49 <notmyname> tdasilva: there always is :-)
21:47:57 <tdasilva> assuming there will probably not be enough time to discuss everything
21:48:16 <notmyname> as clayg said once, "I dare you to put two swift devs in teh same city any try not to do code/design work" ;-)
21:48:44 <notmyname> not enough time is probably a good assumption, unfortunately
21:49:00 <mattoliverau> I'll only really be there on Tuesday, but might need to go sit in Openstack Ansible so I can figure out if there is anything swift I can fix up for them. But that probably wont be the whole day. I just need to figure out if and when they talk about the os_swift role
21:50:00 <notmyname> does anyone else have anything else to bring up this week?
21:50:29 <cschwede_> mattoliverau: what? you're only there on Tuesday? Single day?
21:50:47 <mattoliverau> cschwede_: for the mon/tues part :)
21:51:19 <mattoliverau> I actually arrive monday arvo.. but I don't think anyone would want to see me then :P
21:51:27 <cschwede_> mattoliverau: ok, got it. it's late...
21:51:30 <clayg> notmyname: maybe we need to solicit some more feedback to for cross project work?
21:51:41 <notmyname> clayg: in what way?
21:51:48 <clayg> I've heard on numerous occasions that swift in devstack (and in particular logging) is not great - so that's what I want to work on
21:52:03 <mattoliverau> clayg: yeah, great
21:52:33 <clayg> we've been lambasted for not making cross-project work a prioirty - so ... i guess our self prioritziation is wrong?
21:53:00 <clayg> for folks that will be there Mon-Tues - we should probably be looking to get extrernal prioritization of how to spend that time? maybe?  idk?
21:53:29 <clayg> didn't someone write something something TC golang - shouldn't we talk to someone about that myabe?  no one on our eatherpad even signed up as *interested*
21:54:13 <kota_> ah, so a qustion come up in my mind
21:54:40 <kota_> for the cross-project, where we can catch up the topics and schedule?
21:54:59 <notmyname> kota_: the best I know of is to look at the individual etherpads
21:55:06 <kota_> ok
21:55:17 <kota_> it would be scheduled already
21:55:19 <notmyname> clayg: all I can come up with to answer is "yes" but I don't feel that's a very helpful answer
21:55:42 <notmyname> kota_: sortof. there's no global scheduling. different teams are each given a room, and they can do whatever they want in that room
21:55:43 <mattoliverau> cross project or inter-projects? really both I suspect
21:56:07 <notmyname> mattoliverau: the inter-project stuff would be wtih the other wed-fri rooms
21:56:20 <notmyname> (if my definitions are current)
21:56:29 <clayg> notmyname: that would make sense to me
21:56:34 <notmyname> the cross-project stuff is mon/tues
21:56:47 <mattoliverau> So going to help with say QA, infra or releases would be cross. I always though inter would be working with an other team on say swift stuff.
21:56:56 <notmyname> mattoliverau: right
21:57:24 <jrichli> i have to admit, i am not sure what to do monday.  i think i am just gonna find one of you and follow along.
21:57:54 <notmyname> best I can see for cross project stuff is to show up in one of those rooms and listen?
21:58:00 <notmyname> I'll admit that's not a great plan
21:58:30 <notmyname> one thing that will be good eg is the tc not-python rules
21:58:34 <clayg> there's been a bunch of chatter on the ML coming from osc's swift support - anyone going to be in https://etherpad.openstack.org/p/osc-ptg-pike
21:58:37 <jungleboyj> They have already gotten feedback that the cross-project needs to be better thought out.
21:58:48 <jrichli> i feel like an idiot: but i dont see anything on the room schedule for monday excpet for oslo at 11.  what am i missing?
21:58:50 <jungleboyj> Needs to be more focus on inter-project.
21:59:04 <clayg> clarkb: was QA - question/answer or quality assurance?
21:59:31 <mattoliverau> jrichli: are you just looking at the projector rooms sched?
21:59:34 <clayg> https://wiki.openstack.org/wiki/PTG/Pike/Etherpads <- jrichli maybe this one is better?
22:00:17 <mattoliverau> clayg: Quality assurance (devstack, granade, etc)
22:00:22 <clayg> storyboard?  do we need to know about storyboard?
22:00:27 <notmyname> I'll likely try to go by the docs room to talk about consolidating our docs trees. i'll likely try to go by the infra one to talk about golang stuff
22:00:27 <clayg> mattoliverau: I DID NOT KNOW THAT!?
22:00:36 <kota_> looks like we're running out of time
22:00:45 <notmyname> kota_: ah, you're right
22:01:01 <notmyname> I'm looking forward to seeing everyone next week
22:01:02 <clayg> notmyname: the WSGI thing?
22:01:17 <notmyname> clayg: yeah, the release goals are important for us to be present in
22:01:38 <notmyname> thanks everyone for coming. thanks for working on swift
22:01:42 <notmyname> #endmeeting