21:00:18 <notmyname> #startmeeting swift
21:00:19 <openstack> Meeting started Wed Mar  8 21:00:18 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:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:23 <openstack> The meeting name has been set to 'swift'
21:00:25 <jungleboyj> o/
21:00:27 <notmyname> who's here for the swift team meeting?
21:00:29 <mathiasb_> o/
21:00:32 <joeljwright> o/
21:00:37 <sgundur> hi
21:00:38 <jrichli> o/
21:00:43 <pdardeau_> hi
21:00:45 <rledisez> o/
21:00:48 <kota_> good morning
21:00:49 <tdasilva> hello
21:00:59 <mattoliverau> o/
21:01:04 <timburke> o/
21:01:25 <notmyname> welcome everyone
21:02:23 * notmyname is wondering if acoles or clayg are around
21:02:39 <acoles> just got here
21:02:57 <notmyname> all right, let's get started
21:03:01 <notmyname> agenda is at
21:03:02 <notmyname> #link https://wiki.openstack.org/wiki/Meetings/Swift
21:03:03 * joeljwright thinks clayg might **just might** be late ;)
21:03:13 <notmyname> joeljwright: shocking!
21:03:30 <notmyname> just a couple of things to go over, but i want to leave time for open discussion
21:03:32 <mattoliverau> well he was still online when I finished yesterday, so assume he has to sleep sometime ;P
21:03:40 <joeljwright> fair point
21:03:44 <notmyname> mattoliverau: I haven't seen evidence of that yet
21:03:53 <mattoliverau> lol, true me either
21:04:03 <notmyname> ok, first up is an FYI
21:04:12 <notmyname> #topic outreachy internships
21:04:34 <notmyname> as you've probably seen over the years, openstack participates in teh outreachy internship program
21:04:55 <notmyname> https://wiki.openstack.org/wiki/Internship_ideas is a place where internship ideas are collected
21:05:11 <notmyname> it's where prospective interns go look to see if there's something that sounds interesting to them
21:05:18 <notmyname> if you've got ideas, please let's put them there
21:05:28 <notmyname> and,better yet, if you're interested in mentoring, do it!
21:05:43 <notmyname> both timburke and myself have done it before
21:06:07 <notmyname> I'd definitely recommend it as somethign that helps the mentor grow/learn as much as the intern
21:06:28 <notmyname> so please look that over and consider if you'd be interested in being a mentor
21:06:39 <notmyname> and if you have ideas on projects, please write them down too
21:06:40 <timburke> agreed. i feel like i should have set more time aside to keep up on reviews though
21:07:05 <notmyname> if you have an idea, don't feel like you *must* be the mentor. or that you have to do it on your own
21:07:33 <notmyname> you've got the rest of the community to help
21:07:39 <mattoliverau> timburke: are you crazy man, even when mentoring your a reviewing machine ;)
21:08:07 <tdasilva> mattoliverau: those are not allowed anymore
21:08:08 <timburke> i meant keeping up on karenc's patches...
21:08:21 <jrichli> tdasilva: ha!
21:08:29 <jungleboyj> :-)
21:08:54 <notmyname> that's the FYI on internships/mentors. if there's no questions, we'll move on....
21:08:56 <timburke> you'll have to pry the keyboard out of clayg's cold, mechanical hands
21:09:11 <mattoliverau> tdasilva: lol
21:09:28 <joeljwright> :D
21:09:28 <notmyname> #topic updated foundation logo
21:09:32 <notmyname> breaking news here!
21:09:49 <notmyname> about 30 seconds ago I got the final logo in my inbox
21:09:53 <notmyname> perfect timing
21:09:55 <mattoliverau> what.. is it correct?
21:10:00 <notmyname> yep
21:10:02 <notmyname> https://www.dropbox.com/sh/7gcsuslg0qfjqe9/AAApjLrQpissqd5W6JsL3gOta?dl=0
21:10:04 <mattoliverau> \o/
21:10:05 <notmyname> there you go
21:10:06 <joeljwright> no, it's a bat now?!
21:10:09 <notmyname> lol
21:10:15 <notmyname> it's actually a swift now!
21:10:22 <joeljwright> oh wow! looks good!
21:10:25 <notmyname> not a swallow. not a martin
21:10:28 <notmyname> a swift!
21:10:58 <kota_> nice
21:11:04 <notmyname> yeah it does. it's very different than the hand-drawn one we've had (and we can still like that old one and use it). but I like this new one too
21:11:17 <sgundur> its good!
21:11:53 <notmyname> ok, next topic
21:11:56 <notmyname> a bigger one
21:12:05 <notmyname> #topic upcoming boston summit/forum
21:12:15 <jungleboyj> It looks good!
21:12:31 <notmyname> last week I promised to look in to the boston summit and report back to help answer questions about what it's going to be like, who needs to go, etc
21:12:40 <notmyname> there's good news and bad news on this front
21:12:56 <notmyname> but first let me dump some links in here so you can do further reading later
21:12:58 <joeljwright> :S
21:13:02 <notmyname> #link https://wiki.openstack.org/wiki/Forum
21:13:07 <notmyname> #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/113459.html
21:13:15 <notmyname> #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/113115.html
21:13:20 <notmyname> #link https://wiki.openstack.org/wiki/Forum/Boston2017
21:13:26 <notmyname> #link https://etherpad.openstack.org/p/BOS-Swift-brainstorming
21:13:31 <notmyname> /fin
21:13:35 <mattoliverau> just a few links then :P
21:13:50 <notmyname> ok, i'll try to summarize
21:14:13 <notmyname> the first 2 are more about what the summit will look like. the last 3 are related to planning it
21:14:23 <notmyname> here's what it will look like, as best I can make out
21:14:53 <notmyname> first, this is the event where there will be the formal talks/presentations, the expo hall, the marketing stuff, the big loud colorful parts
21:15:24 <notmyname> that much will be very familiar to anyone who's been to an openstack summit before
21:15:33 <notmyname> but here's the change
21:15:40 <notmyname> there's a new thing called "the forum"
21:15:55 <notmyname> this is the second part of the big summit/ptg split master plan
21:16:14 <notmyname> the ptg was what were called the design sessions at the summits previously
21:16:42 <notmyname> the forum is going to be, basicaly from what I can tell, the fishbowl sessions
21:17:03 <notmyname> these are time-limited 40 minute slots, scheduled, that are to discuss a particular topic
21:17:27 <notmyname> with a projector, and etherpad, and a room full of chairs arranged in circles
21:17:49 <notmyname> so all that sounds "normal", or close enough to what we've done in the past
21:18:12 <notmyname> the trick it, or where the difference comes in, is how these are scheduled and how they will be allocated
21:18:29 <notmyname> previously, each project got a few fishbowl slots and a bunch of design session slots
21:18:30 <mattoliverau> So they've taken the old design summits, split the meeting rooms and fish bowls and seperated them by about 3 months?
21:18:38 <notmyname> mattoliverau: yep
21:18:41 <joeljwright> :(
21:19:06 <mattoliverau> which I guess makes sense in some cases, ops can give feed back from the "last" OpenStack release mid way through etc
21:19:10 <notmyname> so this time, the whole set of fishbowl sessions will be scheduled across all projects instead of allocating a few per project
21:19:18 <notmyname> mattoliverau: that's the other part
21:19:31 <notmyname> in previous summits, there's been an "ops track", normally on the first day
21:19:38 <notmyname> that's rolled into the forum too
21:20:07 <notmyname> so instead of "swift ops feedback" in a swift track in a fishbowl room, there might be an "openstack ops feedback" for everyone
21:20:18 <notmyname> (note the "might". it's hard to predict)
21:20:52 <notmyname> the way these will be scheduled is interesting, and if we want the forum to be productive for swift, we need to get involved now
21:21:04 <notmyname> using the etherpad linked above..
21:21:08 <notmyname> https://etherpad.openstack.org/p/BOS-Swift-brainstorming
21:21:20 <notmyname> we need to collect fishbowl session topics
21:21:32 <notmyname> they need to have a clear scope and goal and, ideally, a designated moderator
21:22:04 <notmyname> so it might be something based on upgrades or hardware or replication cycle times or whatever we choose
21:22:31 <notmyname> then, the tc and the user committee will look at the topics that every project has chosen and select and schedule the forum sessions
21:22:57 <notmyname> from the email, it seems that the scheduling will likely start in the next few weeks
21:23:14 <notmyname> or the goal is to do scheduling about a month out from the forum
21:23:21 <notmyname> and the forum is about 9 weeks from now or so
21:23:25 <mattoliverau> right, yeah so we need to get in on the action there then.
21:23:31 <notmyname> so we need to be participating now
21:23:36 <notmyname> mattoliverau: exactly
21:23:56 <jungleboyj> notmyname: Did you also see the note about the onboarding meeting?
21:24:11 <notmyname> all this also brings up some more challenging questions. specifically, who should go
21:24:11 <mattoliverau> I remember them saying at some point that there might also be rooms available for projects to have a 'mid-cycle'. Would this be in addition (not formally organised of course) to these fish bowls?
21:24:50 <notmyname> jungleboyj: ah yes. a time for new contributors to get familiar with your project, btu I don't know full details of what that looks like
21:24:57 <mattoliverau> NOTE: remembering them saying.. was like 6 moths ago or something
21:25:07 <notmyname> mattoliverau: I haven't seen anything about that
21:25:11 <mattoliverau> kk
21:25:19 <notmyname> well, actually...
21:25:33 <jungleboyj> notmyname:  Right, I am trying to find out more about that.  It is supposed to be a logical extension of upstream university which I am also helping with.
21:25:35 <notmyname> it looks like there may be either some unscheduled space for ad-hoc stuff
21:25:49 <notmyname> or a room that's scheduled like the projector room at the PTG was
21:25:50 <mattoliverau> jungleboyj: nice
21:26:07 <jungleboyj> mattoliverau: I saw a note saying that they would also have tables set up for ad-hoc mid-cycle type stuff.
21:26:15 <notmyname> for those of you not familiar with how the ptg went, there was a room that could be reserved for a time slot
21:26:25 <notmyname> jungleboyj: mattoliverau: right
21:27:05 <notmyname> so who should go...
21:27:36 <mattoliverau> cool, so other then particaping in fish bowls that we important to us (as a project and cross openstack) we can also do some mid-cycling then.. albeit unstructured, but thats the way we roll ;)
21:27:43 <notmyname> I do know this: for any swift contributor who is there, we will definitely find a way to get together and talk about swift. that's just what we do when we're in the same city
21:28:03 <mattoliverau> :)
21:28:14 <jungleboyj> :-)
21:28:20 <notmyname> mattoliverau: yes, but probably in a limited sense. I'm not sure how much room we'll have. will it be like the lunch room with lots of space? something smaller? hard to know
21:28:55 <notmyname> I cannot promise that we'll have time to talk about stuff like we've done at previous summits
21:29:20 <mattoliverau> but worst case there is always the hallway track I assume
21:29:46 <notmyname> I do think the ops feedback will be great, but in my experience, when you've got 40 minutes to talk about some ops concern like "rolling upgrades" or "managing dependencies", swift hasn't gotten a lot of attention (it's just not the major pain point)
21:30:36 <notmyname> or said another way, I think it will look more similar to the first two days of the PTG than the last 3
21:30:37 <jungleboyj> On the bright side, the PTG was much better than expected.  Hoping the Summit/Forum goes the same way.
21:30:43 <notmyname> jungleboyj: :-)
21:30:55 <joeljwright> endless optimism :)
21:31:08 <mattoliverau> jungleboyj: +1
21:31:09 <jungleboyj> joeljwright:  I have gotten good at it.
21:31:25 <notmyname> I'm not trying to be gloomy about it. I think that there's some great potential for the forum. it's just very uncertain because it's new
21:31:41 <jungleboyj> notmyname:  ++
21:32:11 <joeljwright> notmyname: my positivity is just expressed differently :)
21:32:13 <notmyname> but *everything* I've heard about it has been much more "solve all-of-openstack problems" instead of "focus on your openstack project's problems"
21:32:44 <notmyname> so here's what we need to do:
21:32:57 <notmyname> first, add our topics that we're interested in to the etherpad
21:33:32 <notmyname> second, it would be good to figure out over the next few weeks who will be going and who won't (just to help inform what we'll be able to get done at the summit)
21:33:51 <notmyname> and finally, don't write it off before it actually happens :-)
21:34:26 <notmyname> so that's my report on the forum. I expect that there will be a lot of questions, if not now, then in the days to come. please feel free to ping me with them
21:34:28 <mattoliverau> sounds great. So we can use the etherpad for the first 2 things then?
21:34:48 <notmyname> mattoliverau: yes!
21:35:07 <mattoliverau> ie, ideas and a list of people, when they know they're coming can add their names
21:35:36 <notmyname> done. there's a section for that now
21:35:56 <notmyname> I'd encourage you to read over the info that's out there about the summit/forum. start with the links above
21:36:30 <notmyname> ok, next topic (and we can keep talking about this, too) is....
21:36:34 <notmyname> #topic open discussion
21:36:36 <notmyname> open!
21:36:58 <notmyname> what's on your mind that needs to be brought up in this meeting?
21:37:41 <clayg> i hate eventlet -> https://github.com/eventlet/eventlet/issues/210
21:37:50 <clayg> nothing is every simple
21:38:07 <joeljwright> :D
21:38:28 <notmyname> oh! I'll tell you my homework for the next meeting
21:39:07 <clayg> I say "hate" - I mean I mad at it right now
21:39:09 <notmyname> next week, I plan on having some words written down in a linkable place that talks about priorities in swift, current problems, and what to work on, specifically related to the whole golang/hummingbird thing
21:39:38 <mattoliverau> notmyname: nice
21:39:43 <mattoliverau> clayg: :(
21:41:42 <clayg> mattoliverau: I would have swore I'd done multiprocessing queues and eventlet green imports before - i'm not sure exactly what my problem is right now
21:41:46 <notmyname> not a lot of clamoring to bring up stuff...
21:42:14 <clayg> my symptoms are ust it locks up and doesn't do what I expect it to - more so than any mutliprocessing libariaries throwing stack on EAGAIN
21:42:36 <clayg> but like *generally* we don't do monkey patching in deamons - we just import green
21:43:33 <notmyname> clayg: you want someone else to jump into it with you?
21:44:36 <clayg> idk, I was hoping rledisez would tell me "no need to write a patch that adds multiple workers to the reconstrcutor i already did it -> linky"
21:45:26 <rledisez> clayg: sorry, i’m just starting multiple processes, concurrency the old way…
21:46:08 <mattoliverau> clayg: there you go, take eventlet out of the equation :P
21:47:14 <notmyname> not a lot of talking here, so continue converations in -swift and close the meeting
21:47:28 <notmyname> thank you everyone for coming. thanks for working on swift!
21:47:31 <notmyname> #endmeeting