19:01:53 <notmyname> #startmeeting swift
19:01:53 <openstack> Meeting started Wed Aug 13 19:01:53 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:54 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:01:57 <openstack> The meeting name has been set to 'swift'
19:02:10 <notmyname> hello, everyone. who's here for the Swift team meeting?
19:02:15 <cschwede_> o/
19:02:16 <mattoliverau> o/
19:02:18 <cutforth> o/
19:02:19 <kota_> o/
19:02:24 <tdasilva> hello
19:02:26 <hurricanerix> hi
19:02:32 <acoles> here
19:02:42 <gvernik> hello
19:02:53 <torgomatic> hi
19:02:57 <notmyname> agenda for today is at https://wiki.openstack.org/wiki/Meetings/Swift
19:03:12 <notmyname> "normal" stuff :-)
19:03:24 <notmyname> first up, hackathon
19:03:35 * notmyname notes "hackathon", not "hackathong"
19:03:41 <notmyname> #topic hackathon
19:03:53 <notmyname> tdasilva: hello
19:04:01 <tdasilva> no speedos please
19:04:05 <tdasilva> hello
19:04:11 <mattoliverau> lol
19:04:21 <notmyname> the fall hackathon will be during the bridge week between september and october
19:04:27 <notmyname> before the paris summit
19:04:44 <notmyname> in general, there are a couple of primary reasons that we do these
19:05:29 <notmyname> first, it's a good chance to see each other in person and talk face-to-face. this becomes terribly useful, especially when discussing designs and future plans
19:05:42 <notmyname> it's also nice for doing in-person code reviews for big stuff
19:06:27 <notmyname> second, the summits are hard to get stuff done, and not everyone can get their company to pay to go to the summits, so the hackathons are a place where we can focus on the code, rather than the social part of openstack
19:06:59 <notmyname> I've had some people express concern that it seems like there are now requirements to travel around the world 4 times a year (2 summits, 2 hackathons)
19:07:35 <notmyname> although it's nice to go to all of them, certainly don't consider it a requirement. the hackathons are great for code progress. the summits are great for community progress
19:07:43 <notmyname> so, that all being said...
19:08:02 <notmyname> Red Hat is hosting the fall hackathon, and tdasilva is coordinating logistics form their side
19:08:07 <notmyname> thanks tdasilva!
19:08:22 <notmyname> tdasilva: I believe the invites are publicly open now?
19:08:27 <tdasilva> ur welcome :)
19:08:29 <tdasilva> yes
19:08:32 <tdasilva> https://swift-hackathon.eventbrite.com/
19:08:57 <notmyname> #link https://swift-hackathon.eventbrite.com/
19:09:10 <tdasilva> I tried to add info there regarding airports, hotels, etc
19:09:21 <tdasilva> if people have questions feel free to reach out to me
19:09:39 <mattoliverau> Is easier to get to for some :P Seeing as it's so close to the summit (for traveeling 1/2 round the world) it may or maynot be possible to trick work into sending me to both the hackathon and summit (but I'll ask) ;P
19:10:43 <notmyname> mattoliverau: I'd love to see you there if you can make it
19:11:12 <cutforth> notmyname: how far in advance are hackathon dates scheduled?  I ask cuz I will miss out on this one due to a conflict.  I'd like to plan to make the next one.
19:11:26 <notmyname> so, to everyone, sign up ASAP if you are able to go. there are a limited number of places
19:11:48 <notmyname> cutforth: mostly it's "hey we want to sponsor, when do you want it?" in an email to me :-)
19:12:19 <notmyname> cutforth: that being said, I'd like to have the one after before the "L" summit in the spring. I've already got a volunteer to host it on the US West coast
19:12:46 <cutforth> ok, if there were a general time frame, that could help with planning
19:13:01 <tdasilva> notmyname: is the location for the "L" summit already defined too?
19:13:11 <tdasilva> and date?
19:13:24 <notmyname> cutforth: there isn't yet. I'd guess likely in the march(ish) timeframe
19:13:44 <notmyname> tdasilva: no, not that I know of. dates will be in May (it's always May and November)
19:13:58 <tdasilva> ok, thanks
19:14:05 <notmyname> any questions around the fall hackathon?
19:14:13 <cutforth> notmyname: thank you, no more questions
19:14:51 <notmyname> ok, moving on
19:15:04 <notmyname> #topic swift gap analysis follow-up
19:15:10 <notmyname> now for the "fun" topic
19:15:59 <notmyname> as I mentioned last week, the TC has done a "gap analysis" of Swift wrt its integration with the rest of OpenStack (all currently-integrated projects have gone through this--we aren't singled out)
19:16:52 <notmyname> https://etherpad.openstack.org/p/swift_gap_analysis is a high-level summary, but the real juicy details are in the meeting logs from the TC meeting last week. if you're curious, then go read those
19:17:00 <notmyname> but, here's the summary (again)
19:17:08 <notmyname> there are 2 "gaps" identified
19:17:23 <notmyname> quotation marks are intentional, because these may not in fact be gaps
19:17:31 <notmyname> but they are points of investigation
19:17:40 <notmyname> the first is about the use of oslo libraries
19:17:53 <notmyname> the second is about releases and versioning
19:18:37 <notmyname> I've talked with various people about all this, including emaisl with swift-core.
19:18:50 <notmyname> importantly, I don't want to characterize this as a "fight"
19:19:37 <notmyname> but it is important to realize that this is unresolved differences that have existed for the past 4+ years. so there is, unfortunately, baggage on each side of the debate
19:19:55 <mattoliverau> What do the *'s mean in the etherpad next to a few of the oslo libraries?
19:20:02 <notmyname> mattoliverau: I'll get there :-)
19:20:08 <mattoliverau> sorry :)
19:20:32 <notmyname> basically, the situation is that we should either adopt more of the oslo libraries and the common release cycles or convice the TC that it's ok that Swift not do this
19:21:04 <notmyname> so, as mattoliverau referred to, there is an entherpad where we can collect our thoughts and use as a common scratchpad
19:21:09 <notmyname> #link https://etherpad.openstack.org/p/swift_gap_scratchpad
19:21:28 <notmyname> I've started it with the 2 issues bolded and then some subpoints under each
19:21:45 <notmyname> today in this meeting I want to focus a little on the oslo usage
19:22:14 <notmyname> I've listed what I think are the 3 big questions that need to be answered for each oslo library
19:22:28 <notmyname> (I found the list of oslo libraries by searching pypi for "oslo"
19:22:59 <notmyname> so for each, I'd like to answer what the library is doing, what are we doing (ie what would it replace in swift), and what's the impact of using it
19:23:17 <notmyname> some of them (oslo.vmware being the simplest) are just silly to consider for swift
19:23:29 <notmyname> that's why I put a strikethrough on oslo.vmware
19:23:43 <notmyname> the ones I put a * on are the Big Ones (tm).
19:23:52 <notmyname> ie those are the ones that people have specifically called out
19:24:06 <notmyname> config, messaging, and logging
19:24:34 <notmyname> logging is sorta special because it's not a separate library at this time, but I still want to see an analysis of it
19:24:46 <notmyname> here's what I would like to see
19:25:07 <notmyname> I'd like us, as a group, to each take one or two of these oslo libraries and answer the questions for them
19:25:48 <notmyname> eg with oslo config, figure out what it would look like to use it, what the impact to swift deployers is, migration paths, gaps in the oslo library, etc
19:26:19 <notmyname> the ones with a * are bigger, and therefore I think that if one person takes it, that's the only one they should take
19:26:24 <notmyname> make sense?
19:26:31 <notmyname> (I'm about to ask for volunteers)
19:26:39 <notmyname> any questions so far?
19:27:06 <cschwede_> makes sense to me. should we add ourselves to the etherpad to the libs we are going to investigating?
19:27:19 <cschwede_> s/investigating/investigate
19:27:43 <notmyname> cschwede_: yes, feel free to add yourself to the etherpad. also, say somethere in here now when you do :-)
19:28:16 <notmyname> that's my call for volunteers. who wants to look at what oslo libraries
19:28:44 <mattoliverau> re: logging, it seems a bit dirty to me as its still incubated but is suppose to be treated as released. But incubated means no pip.. so does that mean a copy and paste job?
19:29:11 <cschwede_> notmyname: k. i’ll have a look at oslo.serialization first
19:29:19 <acoles> i'll look at oslo.config
19:29:38 <acoles> made a start already on that
19:29:49 <notmyname> mattoliverau: we're not going to use copy/paste code that is externally managed in swift. so that's a non-starter. but assuming that it will be released, the common perspective will be that we should use it until we convince the TC it's ok that we don't
19:29:54 <notmyname> acoles: thansk
19:29:58 <notmyname> cschwede_: thanks
19:30:17 <torgomatic> let's put our names by our comments; I also have stuff to say about oslo.config, and I don't want to put words in acoles's mouth
19:30:31 <notmyname> yes, good point
19:30:48 <notmyname> it's hard to track who said what on an etherpad.
19:31:11 <notmyname> torgomatic:  what about simply writing your name at the top so there is a color match to your name?
19:31:34 <acoles> isn't there an oslo.nametracker?
19:31:38 <torgomatic> lol
19:31:41 <notmyname> heh
19:32:12 <notmyname> yes, please put your name next to your comments in the etherpad
19:32:43 <notmyname> cschwede_: can you take another one too? I think i18n is small. also rootwrap
19:32:58 <cschwede_> notmyname: yes, i was thinking about i18n
19:33:15 <notmyname> mattoliverau: hurricanerix: gvernik: cutforth: any you can look in to?
19:33:30 <notmyname> and kota_ :-)
19:33:53 <notmyname> oh, now maybe we can volunteer zaitcev for one :-)
19:34:08 <portante_> oslo.db
19:34:15 <gvernik> i will look over it also
19:34:18 <notmyname> portante_: is that for you?
19:34:19 <mattoliverau> I'm happy to look at any, I guess I'll start with logging as it's highlighted then maybe using oslo.db and see how it could connect to sqllite etc
19:34:30 <portante> for zaitcev ... :)
19:34:36 <portante> happy to volunteer others ...
19:34:36 <cschwede_> heh!
19:34:39 <notmyname> hurricanerix: thanks for taking logging. I think there's a lot to consider there. let me know if you have any questions
19:34:45 <notmyname> portante: heh
19:34:48 <zaitcev> That "db" thing sounds like a database.
19:34:59 <zaitcev> Are we importing a database from Oslo now?
19:35:00 <notmyname> mattoliverau: hurricanerix got logging. can you take messaging?
19:35:12 <mattoliverau> sure
19:35:27 <torgomatic> zaitcev: how else will we store all our container listings in Mongo? /s
19:35:29 <notmyname> mattoliverau: thanks. also, I think that one is kinda big, so please talk to me at any time about it
19:35:57 <notmyname> mattoliverau: specifically, the point made by the TC is that we aren't using oslo.messaging and are instead using statsd
19:36:27 <kota_> I'll take oslo.rootwrap
19:36:28 <notmyname> torgomatic: can you take 3 small ones? db, rootwrap, and oslotest
19:36:43 <notmyname> kota_: ok. can you also look at middleware?
19:36:44 <mattoliverau> notmyname: k, may need to talk to you about it then.. when I'm more awake :P
19:36:50 <notmyname> mattoliverau: no worries :-)
19:36:58 <kota_> notmyname: k
19:37:06 <torgomatic> notmyname: sure, I can look at those... I think portante is taking db though
19:37:08 <notmyname> mattoliverau: or maybe you can ask torgomatic nicely and he can do messaging and you can take a few smaller one s: -)
19:37:17 <torgomatic> unless I misunderstood what he said
19:37:27 <torgomatic> (which is entirely possible)
19:37:30 <notmyname> I think portante has only volunteered others
19:37:45 <torgomatic> nobody told me he got promoted to management! congratulations! ;)
19:37:49 <notmyname> lol
19:37:58 <mattoliverau> lol
19:38:39 <notmyname> torgomatic: db and oslotest are all that's left
19:38:48 <mattoliverau> torgomatic: if you want messaging it's yours, but happy to give it a whirl. If you do take it I'll take the smaller ones that are left :)
19:38:49 <torgomatic> notmyname: I can take a look at those two, sure
19:38:55 <portante> torgomatic: yes, thanks, it is great feeling ...
19:39:05 <notmyname> torgomatic: thanks
19:39:11 <mattoliverau> cool, done then
19:39:21 <notmyname> thanks, everyone
19:39:25 * portante would like to take a minute at the end of the meeting to esplain ...
19:39:53 <notmyname> I'm going to the openstack ops meetup in san antonio in a few weeks. I'm specifically going to bring up some of these things to get feedback there
19:40:18 <notmyname> dhellmann: you're editing stuff now?
19:40:33 <notmyname> dhellmann: we already use pbr, that's why it's not on the list (like oslosphinx)
19:40:56 <zaitcev> we aren't going to use stevedore and taskflow, are we
19:41:23 <dhellmann> notmyname: ah, sorry, I was filling out your list when I saw you said you'd only searched for "oslo" on pypi
19:42:00 <notmyname> I'll look at stevedore and taskflow
19:42:01 <dhellmann> zaitcev: stevedore would be used if you're loading driver code, but I don't know if swift does that
19:42:02 <notmyname> zaitcev: I have no diea
19:42:41 <notmyname> I've talked to clayg briefly about stevedore. I'll ping him again about it
19:42:59 <notmyname> dhellmann: what is taskflow?
19:43:20 <dhellmann> it manages multi-step processes in a way that lets  you pause, restart, and roll them back
19:43:38 <dhellmann> josh harlow can fill in more details, he manages that
19:43:50 <notmyname> dhellmann: ok, thanks
19:43:54 <dhellmann> np
19:44:03 <notmyname> ok, let's move on
19:44:28 <notmyname> thanks everyone for taking these. please try to have some information for next week's meeting (some, not all)
19:44:45 <notmyname> peluse: around?
19:44:51 <notmyname> I don't think he's here today
19:45:01 <notmyname> #topic reviews
19:45:15 <notmyname> #link https://wiki.openstack.org/wiki/Swift/PriorityReviews
19:45:40 <notmyname> thanks for working on the migration middleware and the keystone reviews. I've seen a bit of back and forth on those this week
19:46:02 <notmyname> mattoliverau: you assigned the affinity+DELETEs bug to yourself on LP. are you working on that?
19:46:06 <notmyname> mattoliverau: if so, what's the status?
19:46:15 <notmyname> #link https://bugs.launchpad.net/swift/+bug/1318375
19:46:19 <uvirtbot> Launchpad bug 1318375 in swift "DELETE operation not write affinity aware" [High,New]
19:47:45 <zaitcev> maybe he stepped off to get a sandwich
19:47:52 <notmyname> or went back to sleep :-)
19:47:59 <mattoliverau> lol i'm here
19:48:08 <notmyname> heh, ok
19:48:16 <kota_> lol
19:48:26 <notmyname> mattoliverau: are you working on that bug?
19:48:33 <notmyname> ie a patch
19:48:53 <mattoliverau> yup, I've just thrown together a swift multi region SAIO for testing it. Will get a version 0.1 up today for a flaming
19:49:02 <notmyname> mattoliverau: awesome. thanks
19:49:17 <mattoliverau> sorry, irc decided to hang
19:49:25 <notmyname> I understand. been there :-)
19:50:23 <notmyname> the other bug that was reraised this week is addressed by https://review.openstack.org/#/c/113180/. several people have looked at it
19:50:46 <notmyname> I think the only outstanding question there is to prove one way or another if a circular logging reference is properly GC'd or not
19:50:54 <notmyname> which seems like a big deal :-)
19:51:14 <notmyname> so if you like such things, I'd appreciate your comments on the patch :-)
19:51:28 <torgomatic> not for a logger whose lifetime virtually matches the process's lifetime
19:51:30 <torgomatic> IMO
19:52:33 <notmyname> as to other patches, the migration middleware has had some back and forth from acoles and torgomatic with gvernik
19:52:44 <notmyname> is there anything on that to bring up in the meeting?
19:53:08 <portante> can somebody dump the gerrit link here for convenience?
19:53:13 <notmyname> yes, sorry
19:53:24 <portante> thanks
19:53:24 <notmyname> https://review.openstack.org/#/c/64430/
19:53:49 <kota_> Hi, I would like to get core review about EfficientReplication
19:53:54 <kota_> https://review.openstack.org/#/c/99824/
19:54:27 <notmyname> kota_: yes, me too :-)
19:54:27 <kota_> It's writtend down in PriorityReviews on wiki
19:54:33 <notmyname> (Hi, pot. I'm kettle)
19:55:50 <kota_> mattoliverau: thanks for a review!
19:56:22 <notmyname> kota_: I think that one is pretty important. I like the ideas, and I'm sorry I haven't had a chance to look at it personally yet
19:56:44 <kota_> notmyname: ok,
19:56:47 <mattoliverau> kota_: of course, we've had some back and forths on it, but looks good to me now :)
19:56:51 <notmyname> to all, please keep looking at the priority reviews page, and work your way down it
19:56:54 <kota_> notmyname: no worries
19:57:04 <notmyname> just a few minutes left...
19:57:10 <notmyname> #topic open discussion
19:57:19 <notmyname> anything else to bring up in the meeting this week?
19:57:35 <torgomatic> the SwiftService patch for python-swiftclient could still use another set of eyes
19:58:00 <notmyname> torgomatic: can you add that to the priority reviews page, please?
19:58:00 <portante> notmyname: working on keystone V3 review for python swift client
19:58:06 <notmyname> portante: thanks
19:58:06 <torgomatic> notmyname: will do
19:58:19 <acoles> just fyi, i will be away 8/15 - 9/1
19:58:29 <notmyname> acoles: ah, ok. thanks for the head's up
19:58:40 <notmyname> acoles: vacation?
19:58:50 <portante> it will be one of my last reviews for a while, as my role going forward on the performance team is changing to more consulting and less development work on swift
19:58:59 <acoles> notmyname: yep, italy
19:59:03 <notmyname> acoles: enjoy!
19:59:06 <cschwede_> acoles: enjoy your vacation!
19:59:17 <notmyname> portante: we'll try to keep finding ways to pull you back!
19:59:20 <acoles> thanks
19:59:21 <mattoliverau> portante: :( that's a shame
19:59:24 <portante> notmyname: thanks
19:59:37 <acoles> portante: appreciate your efforts on that review
19:59:44 <portante> acoles: welcome
20:00:01 <notmyname> last 30 seconds for comments in the meeting....
20:00:07 <portante> and for others, if I have dropped the ball on anything, please let me know so that I can wind that down properly ...
20:00:36 <notmyname> time's up
20:00:45 <notmyname> thanks, everyone, for coming today
20:00:45 <notmyname> #endmeeting