21:00:07 <notmyname> #startmeeting swift
21:00:08 <openstack> Meeting started Wed Apr 26 21:00:07 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:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:12 <openstack> The meeting name has been set to 'swift'
21:00:14 <notmyname> who's here for the swift team meeting?
21:00:17 <mattoliverau> o/
21:00:18 <joeljwright> o/
21:00:20 <m_kazuhiro> o/
21:00:20 <timburke> o/
21:00:22 <rledisez> o/
21:00:29 <patchbot> here
21:00:31 <mathiasb> o/
21:00:44 <acoles> hi
21:00:45 <pdardeau_> hi
21:00:46 <cschwede> o/
21:01:04 <kota_> hi
21:01:21 <notmyname> clayg_: clayg: ping
21:01:42 <notmyname> tdasilva: ping
21:01:48 <clayg_> ping 'em all
21:02:08 <notmyname> yeah, I've thought about a "meeting ping" function for patchbot
21:02:15 <clayg_> oh dar
21:02:18 <clayg_> *dear
21:02:20 <tdasilva> hi
21:02:26 <clayg_> tdasilva: HI!
21:02:33 <tdasilva> clayg_: !!!!
21:02:59 <notmyname> ok, let's get started
21:03:02 <notmyname> #link https://wiki.openstack.org/wiki/Meetings/Swift
21:03:06 <notmyname> rough agenda there
21:03:13 <notmyname> but summit stuff first
21:03:19 <notmyname> #topic summit update and FYIs
21:03:33 <notmyname> only a week and a half until the summit in boston
21:03:49 <notmyname> good news is that mattoliverau found sponsorship so will be able to make it
21:03:50 <clayg_> oh dear :'(
21:03:51 <mattoliverau> \o/
21:03:57 <clayg_> yay!
21:03:59 <cschwede> :D
21:04:10 <mattoliverau> thanks to the OpenStack foundation
21:04:11 <kota_> congrats
21:04:21 <notmyname> bad news is that some others ( jrichli, pdardeau_, others?) won't be there
21:04:36 <pdardeau_> notmyname: i'll be there (booth duty)
21:04:44 <notmyname> pdardeau_: awesome!
21:04:52 <kota_> nice!
21:04:55 <notmyname> that's new info!
21:05:07 * notmyname backspaces over american english idioms
21:06:04 <notmyname> so unfortunately there's been staffing changes at some of our employers (rackspace, intel). so (1) if someone unfirtunately has to leave our community because of a new job, let's make it easy and support them
21:06:28 <mattoliverau> Or just hire me to work on Swift ;)
21:06:31 <notmyname> and (2) if you know people who are hiring great openstack devs, people like mattoliverau will be at the summit and looking
21:07:29 <notmyname> pdardeau_: I'm not sure if you can or are ready to share anything about you and intel. last I heard your work with osic is over but there might be new opportunities elsewhere at intel
21:07:45 <notmyname> but ... i don't want to belabor the point or put people on the spot
21:08:18 <notmyname> the point is, as people go from time to time, let's recognize and thank them for their awesome work, and help them transitiona nd carry on their work in teh community
21:08:18 <pdardeau_> notmyname: it's complicated
21:08:42 <notmyname> pdardeau_: I'm sure. please let us know if there's anything the rest of us in teh community can do to help
21:08:51 <pdardeau_> thx
21:08:59 <clayg_> nice
21:09:18 <notmyname> and also, at the summit there will be some great opportunities to encourage new contributors to swift!
21:09:50 <notmyname> there's both the upstream institute training (on sunday? I think tdasilva is helping out there?) and there's a project onboarding later in the week
21:10:19 <notmyname> I was in the middle of getting the onboarding schedule squared away (ie finding where/when it is) as the meeting started
21:10:25 <diablo_rojo_phon> Half day Saturday and all of Sunday :)
21:10:37 <notmyname> diablo_rojo_phon: thanks (upstream institute)
21:10:51 <tdasilva> I'll be there Sunday
21:10:55 <notmyname> tdasilva: any more details on the upstream institute?
21:11:13 <tdasilva> I know it's at the Sheraton from 9am - 6pm
21:11:21 <tdasilva> but that's all i know
21:11:24 <notmyname> ok
21:11:39 <notmyname> oh! I wanted to say this too...
21:11:54 <timburke> onboarding is https://www.openstack.org/summit/boston-2017/summit-schedule/events/18714/swift-project-onboarding -- wed, 1:50-3:20pm
21:11:54 <tdasilva> hopefully there will be newcomers interested in swift and I won't scare them away ;)
21:12:02 <notmyname> timburke: thanks
21:12:27 <notmyname> clayg_: thanks for leading the meeting last week! when I got back online I had a message saying "clayg led the meeting and it was great!"
21:12:31 <notmyname> heard that from others too
21:12:37 <notmyname> clayg_: thank you. it was very helpful
21:12:42 <clayg_> np boss
21:12:46 <diablo_rojo_phon> notmyname: what details do you want about upstream institute? :)
21:13:18 <clayg_> I was really hoping to have something on the ML last week for me to digest async - so I could ask questions this week - i must have missed it tho :'(
21:13:22 <notmyname> diablo_rojo_phon: I had a follow-up from last week's meeting (led by clayg_; i was out) saying there was some question about interest and our team's participation
21:13:31 <notmyname> diablo_rojo_phon: and I think you and tdasilva have talked?
21:13:39 <acoles> the onboarding session clashes with the discussion about adding ids to logging
21:14:09 <diablo_rojo_phon> tdasilva maybe you talked to ildikov ? We just wanted some representation there in case people have swift questions.
21:14:09 <notmyname> acoles: ah. definitely will need to split up then
21:14:14 <tdasilva> I only talked to jungleboyj
21:14:23 <diablo_rojo_phon> Ah.
21:14:34 <jungleboyj> o/
21:14:40 <notmyname> acoles: I'm going through the summit schedule to look for those sorts of schedule conflicts now
21:14:47 <jungleboyj> Hey sorry, forgot to join up.
21:15:06 <notmyname> ok. upstream institute. jungleboyj diablo_rojo_phon: is there anything you need from us at this point?
21:15:32 <jungleboyj> diablo_rojo_phon:  Yeah, I had talked to tdasilva  .  He will join up.
21:15:34 <notmyname> jungleboyj: was there a ML thread this past week?
21:15:37 <diablo_rojo_phon> just someone to be around on Sunday :)
21:15:46 <diablo_rojo_phon> In case people have swift questions
21:16:01 <notmyname> tdasilva will be our (awesome as always) rep
21:16:03 <jungleboyj> notmyname:  Since tdasilva had volunteered and was in town I didn't go to the ML.
21:16:09 <notmyname> jungleboyj: ah ok
21:16:17 <jungleboyj> notmyname:  Hope that was ok.
21:16:26 <notmyname> great, then. I'm looking forward to meeting up sunday night to see how things went
21:16:27 <diablo_rojo_phon> Thank you in advance tdasilva :)
21:16:39 <jungleboyj> notmyname:  Sounds good!
21:16:45 <tdasilva> diablo_rojo_phon: yw
21:16:55 <tdasilva> looking forward to it
21:17:15 <notmyname> for everyone, the summit schedule is online at https://www.openstack.org/summit/boston-2017/summit-schedule/ so be sure to mark the stuff you want to be at
21:17:20 <notmyname> this includes all the forum tracks too
21:17:48 <notmyname> a brief work on the swift forum sessions
21:18:12 <notmyname> first, thank you to everyone who added those comments to the topics about "why this session needs to happen"
21:18:33 <notmyname> what that's resulted in is a large block of time on wednesday (IIRC) in one room for swift
21:18:58 <notmyname> there are format topics and time slots scheduled, but I want to do it similarly to some past summits
21:19:27 <notmyname> at the beginning of that time block, we'll write down the scheduled (and unscheduled) topics that need to be covered, and we'll have 4 hours or so to get through them
21:20:13 <notmyname> so they originally scheduled us for a few more time slots on different days, but they realized they gave swift a lot of time slots (this is because of the topic comments!)
21:20:40 <tdasilva> oohh..i did notice that some had disappeared
21:20:47 <notmyname> so they were going to take some away to give to other projects, and I was able to give up the "time islands" ones and ensure we got the large contiguous block of time
21:20:59 <tdasilva> nice!
21:21:04 <notmyname> ie instead of losing the big block of time
21:21:24 <kota_> make sense
21:21:24 <notmyname> so the unscheduled topics I mentioned earlier.. those are the things that got dropped
21:21:49 <notmyname> so I do definitely want to get through most of the stuff we had on the etherpad. it will be fast. it will be hard to do. but we can do it
21:22:11 <notmyname> I'll be working on that schedule before next week's meeting, and I plan to have more details then
21:22:17 * notmyname is just starting on it now
21:22:35 <notmyname> ok, so before we move on to other topics, are there any questions about the summit?
21:22:37 <mattoliverau> plus there will be the hallway and beer track right?
21:22:43 <notmyname> mattoliverau: of course!
21:22:51 <joeljwright> Mmmmm beer
21:23:01 <notmyname> mattoliverau: you can sleep on the plane ride home
21:23:06 <clayg_> i've heard about this hacking rooms?
21:23:08 <mattoliverau> after my last week, I'll need it ;)
21:23:14 <mattoliverau> notmyname: that is true
21:23:23 <notmyname> clayg_: ah right! I just saw something about that
21:23:40 <notmyname> AIUI the "hacking rooms" are like the reservable rooms at the PTG?
21:23:41 <clayg_> hacking on swift can be a somewhat raucous affair - hopefully we don't upset anyone
21:23:45 <notmyname> that's what it sounded like to me?
21:24:07 <notmyname> clayg_: but if you understood something different, do tell
21:24:16 <clayg_> well find out when we get there - i'm keeping an open mind
21:24:39 <notmyname> any other questions on the summit?
21:24:56 <clayg_> I'll try to make space for the work that we need to do within reason - if we really can't make it work w/o interrupting other people or the general flow - I'll give that feedback to the foundation folks
21:25:59 <notmyname> oh, maybe our time block is tuesday (like I said, I'm just now looking at it)
21:26:02 <notmyname> ok, moving on...
21:26:09 <notmyname> #topic swift 2.14.0 release
21:26:33 <notmyname> again, thanks for the prioritization and triage lists for the bugs and patches that were done last week
21:26:50 <notmyname> the big stuff landed, there's great stuff on master that's unreleased, let's release!
21:27:16 <notmyname> the authors/changelog update should be making its way through the gate right now
21:27:24 <notmyname> when that lands, i'll do the patch to request the release
21:27:33 <notmyname> thank you for your reviews and work on this release
21:27:43 <notmyname> #info swift 2.14.0: the best one yet!
21:28:02 <notmyname> but you know what's better than swift 2.14.0?
21:28:20 <notmyname> swift 2.15.0
21:28:22 <timburke> 2.14.1!
21:28:30 <joeljwright> :D
21:28:32 <notmyname> timburke: yep!
21:28:44 <clayg_> notmyname: is there an openstack release coming up?  or did the new scheduling fix it so the next openstack release isn't right on top of the forum?
21:28:53 <timburke> i'm just going to assume we'll need a minor bugfix ;-)
21:29:00 <notmyname> clayg_: the latter. no openstack release coming up
21:29:02 <clayg_> ... and it's Pike right?   we're working on Pike?
21:29:07 <timburke> yup
21:29:13 <mattoliverau> timburke: and taht would make it better :)
21:29:20 <notmyname> https://wiki.openstack.org/wiki/Swift/PriorityReviews has some high priority bugs on it
21:29:58 <notmyname> as a reminder, there's a ton of stuff people are interested in working on (in addition to the bugs)
21:30:09 <clayg_> some of them are more "improvements for existing stuff", dunno - i was hoping to get more feedback on that - but maybe I accidently picked the right stuff?
21:31:04 <notmyname> the two most important things in swift are container sharding and improving rebalance. if you're not looking at bugs listed on priority reviews, you can be most helpful by helping with these
21:31:39 <mattoliverau> oh yeah, I should give sharding some love before I loose my clouds.
21:31:50 <joeljwright> :'(
21:31:57 <notmyname> mattoliverau is obviously the world's leading expert on container sharding, but timburke and others have been learning in case we lose matt
21:32:30 <notmyname> if you want to help out on container sharding, the best way is to help improve test coverage. (1) it needs more tests (2) it will help you learn it
21:32:32 <mattoliverau> timburke and acoles are awesome, just saying
21:33:10 <timburke> one of the things i've been meaning to do for a while is to make a probe test harness...
21:33:30 <notmyname> if you want to help out with improving rebalance, clayg_ is your starting point. and https://etherpad.openstack.org/p/swift-rebalance is a rough guide of current thinking
21:33:40 <mattoliverau> and once you learn it you can make it better. fresh eyes and all that.
21:34:12 <clayg_> notmyname: there's also zaitcev's patch to fix PUTs - which is related to golang
21:34:40 <notmyname> ah, right. yeah, you and I need to write up a consolidated view of the different parts of that work
21:34:58 <mattoliverau> typey typey
21:35:02 <notmyname> yup
21:35:12 <notmyname> or in clayg_'s case, pencil and notepad ;-)
21:35:18 <clayg_> werd
21:35:28 <timburke> oh, and looking back at the priority reviews: should i go ahead and squash in my fixups for https://review.openstack.org/#/c/302494/ ? i think i'd be ready to +2 with that...
21:35:29 <patchbot> patch 302494 - swift - Sync metadata in 'rsync_then_merge' in db_replicator
21:35:38 <notmyname> ok, any questions on all that? the release, the big things being worked on?
21:35:46 <timburke> i feel bad that it had languished for like a year before i looked at it :-(
21:36:07 <notmyname> :-(
21:36:36 <notmyname> timburke: IMO, yes, squash changes
21:36:48 <notmyname> kota_: is daisuke still around to help out on that?
21:36:53 <notmyname> do you know?
21:37:08 <kota_> notmyname: i don't think so
21:37:11 <notmyname> ok
21:37:13 <acoles> mattoliverau: for the record, thank you so much for your incredible work on sharding, we are indebted to you
21:37:21 <notmyname> yeah, I only occasionally see him in irc any more
21:37:22 <timburke> indeed!
21:37:24 <joeljwright> acoles: +1
21:37:29 <notmyname> acoles: mattoliverau: +1
21:37:37 <kota_> notmyname: i just talked him yesterday but he said, not able to do it
21:37:40 <mattoliverau> says the people who are yet to run it :P
21:37:40 <pdardeau_> acoles: +1
21:37:44 <notmyname> timburke: so yeah, squash away
21:37:49 <mattoliverau> YW
21:37:50 <notmyname> kota_: ok
21:38:11 <kota_> notmyname, timburke: i'll try to look at the patch to help something
21:38:16 <notmyname> kota_: thanks
21:38:23 <timburke> thanks kota_
21:38:36 <notmyname> #topic follow-up: patch 456205
21:38:37 <patchbot> https://review.openstack.org/#/c/456205/ - python-swiftclient - WIP: Use keystone session when possible
21:38:53 <notmyname> it was on the agenda as a follow-up from last week
21:39:11 <notmyname> but the patch doesn't look like it's moved much/any and lots of tests fail and it's WIP
21:39:13 <notmyname> so....
21:39:14 <notmyname> ?
21:39:27 <joeljwright> yeah, so I've been looking at that patch… I think it highlights how big the change to generic keystone client would be…
21:39:45 <joeljwright> I don't think jaosorior has time to work on it
21:40:04 <clayg_> i lost track of the link to the related/earlier attempt/change
21:40:11 <notmyname> but my understanding is that this will be required to use keystone in the new devstack world order?
21:40:57 <clayg_> oh wow
21:41:03 <joeljwright> notmyname: keystone certainly want the generic stuff to be used and not the version specific clients
21:41:55 <notmyname> joeljwright: what do we need to do here, then?
21:42:31 <joeljwright> it's a big change
21:43:07 <joeljwright> the basic idea is in that patch, but it't a lot of work to move to keystone sessions
21:43:18 <joeljwright> and it changes some of the client behaviour
21:43:32 <joeljwright> we need to do it
21:43:37 <joeljwright> but it will take a while
21:43:40 <notmyname> ok
21:44:01 <notmyname> could you outline what's needed with any details you know and link to it on the ideas page?
21:44:16 <notmyname> I think that would help the rest of us keep track over the weeks as we go
21:44:25 <notmyname> or trello or whatever you like
21:45:01 <joeljwright> sure, I'll write down what I understand the situation to be
21:45:12 <notmyname> perfect. thanks
21:45:19 <notmyname> #topic open discussion
21:45:27 <notmyname> what else do we need to talk about this week in the meeting?
21:46:46 <mattoliverau> obviously not much :)
21:46:56 <notmyname> careful... we're in danger if ending 10 minutes before last week's meeting
21:47:08 <notmyname> might make clayg_ feel bad if we end so early ;-)
21:47:15 <clayg_> nah i'm good
21:47:20 <notmyname> heh, ok :-)
21:47:38 <notmyname> thank you everyone for your work on the code and on the community. you are why swift is great
21:47:46 <notmyname> I'm looking forward to seeing (most of) you in boston
21:47:50 <notmyname> until next week....
21:47:54 <joeljwright> have fun peeps
21:47:58 <mattoliverau> \o/ I can finish breakfast
21:47:59 <notmyname> ...or 30 seconds in #openstack-swift
21:48:03 <notmyname> #endmeeting