Wednesday, 2014-10-22

*** bpokorny has joined #openstack-meeting-300:04
*** bpokorny has quit IRC00:20
*** vkmc has quit IRC00:20
*** yamahata has quit IRC00:20
*** garyduan has quit IRC00:20
*** seizadi has quit IRC00:20
*** reed has quit IRC00:20
*** kashyap has quit IRC00:20
*** marun has quit IRC00:20
*** ChuckC has quit IRC00:20
*** mtreinish has quit IRC00:20
*** fungi has quit IRC00:20
*** vishy has quit IRC00:20
*** troytoman_ has quit IRC00:20
*** ctracey has quit IRC00:20
*** jraim has quit IRC00:20
*** mordred has quit IRC00:20
*** zigo has quit IRC00:20
*** Adri2000 has quit IRC00:20
*** HenryG has quit IRC00:20
*** ttx has quit IRC00:20
*** jaypipes has quit IRC00:20
*** mestery has quit IRC00:20
*** wendar has quit IRC00:20
*** rossella_s has quit IRC00:20
*** zhiyan has quit IRC00:20
*** zz_johnthetubagu has quit IRC00:20
*** Basil_Saito has quit IRC00:20
*** asahlin has quit IRC00:20
*** boris-42 has quit IRC00:20
*** cjellick has quit IRC00:20
*** armax has quit IRC00:20
*** rhagarty has quit IRC00:20
*** jeblair has quit IRC00:20
*** dosaboy has quit IRC00:20
*** alaski has quit IRC00:20
*** jgrimm has quit IRC00:20
*** leifz has quit IRC00:20
*** mhagedorn has quit IRC00:20
*** miguelgrinberg has quit IRC00:20
*** dansmith has quit IRC00:20
*** anteaya has quit IRC00:20
*** dhellmann has quit IRC00:20
*** pettori has quit IRC00:20
*** haleyb has quit IRC00:20
*** d0ugal has quit IRC00:20
*** jrist has quit IRC00:20
*** emagana has quit IRC00:20
*** s3wong has quit IRC00:20
*** ivar-lazzaro has quit IRC00:20
*** gugl3 has quit IRC00:20
*** abramley has quit IRC00:20
*** sandr8 has quit IRC00:20
*** ekarlso has quit IRC00:20
*** rharwood has quit IRC00:20
*** sc68cal has quit IRC00:20
*** sdad has quit IRC00:20
*** vitorc has quit IRC00:20
*** alexsyip has quit IRC00:20
*** davidlenwell has quit IRC00:20
*** mwagner_lap has quit IRC00:20
*** pballand has quit IRC00:20
*** dkehn has quit IRC00:20
*** bauzas has quit IRC00:20
*** lifeless has quit IRC00:20
*** dougwig has quit IRC00:20
*** kevinbenton has quit IRC00:20
*** burgobianco has quit IRC00:20
*** flwang has quit IRC00:20
*** edleafe has quit IRC00:20
*** flaper87 has quit IRC00:20
*** sigmavirus24_awa has quit IRC00:20
*** persia has quit IRC00:20
*** s1rp has quit IRC00:20
*** redrobot has quit IRC00:20
*** sankarshan_away has quit IRC00:20
*** maurosr has quit IRC00:20
*** russellb has quit IRC00:20
*** erw has quit IRC00:20
*** SergeyLukjanov has quit IRC00:20
*** aleksandr_null has quit IRC00:20
*** DinaBelova has quit IRC00:20
*** tidwellr has quit IRC00:20
*** yamahata_ has quit IRC00:20
*** jomara has quit IRC00:20
*** notmyname has quit IRC00:20
*** dobson has quit IRC00:20
*** pcarver_ has quit IRC00:20
*** boltR has quit IRC00:20
*** NikitaKonovalov has quit IRC00:20
*** dboik has quit IRC00:20
*** obondarev has quit IRC00:20
*** ozamiatin has quit IRC00:20
*** chuckC_ has quit IRC00:20
*** edhall_ has quit IRC00:20
*** marios_ has quit IRC00:20
*** krotscheck has quit IRC00:20
*** tteggel has quit IRC00:20
*** rcleere_away has quit IRC00:20
*** pleia2 has quit IRC00:20
*** blogan has quit IRC00:20
*** munish_ has quit IRC00:20
*** mikal has quit IRC00:20
*** _crobertsrh has quit IRC00:20
*** dstanek has quit IRC00:20
*** beagles has quit IRC00:20
*** cgoncalves has quit IRC00:20
*** kgriffs|afk has quit IRC00:20
*** kevinbenton has joined #openstack-meeting-300:27
*** dougwig has joined #openstack-meeting-300:27
*** lifeless has joined #openstack-meeting-300:27
*** bauzas has joined #openstack-meeting-300:27
*** dkehn has joined #openstack-meeting-300:27
*** pballand has joined #openstack-meeting-300:27
*** mwagner_lap has joined #openstack-meeting-300:27
*** bpokorny has joined #openstack-meeting-300:27
*** dboik has joined #openstack-meeting-300:27
*** pettori has joined #openstack-meeting-300:27
*** marun has joined #openstack-meeting-300:27
*** yamahata has joined #openstack-meeting-300:27
*** asahlin has joined #openstack-meeting-300:27
*** s3wong has joined #openstack-meeting-300:27
*** ChuckC has joined #openstack-meeting-300:27
*** boris-42 has joined #openstack-meeting-300:27
*** flwang has joined #openstack-meeting-300:27
*** garyduan has joined #openstack-meeting-300:27
*** vitorc has joined #openstack-meeting-300:27
*** sigmavirus24_awa has joined #openstack-meeting-300:27
*** ivar-lazzaro has joined #openstack-meeting-300:27
*** zigo has joined #openstack-meeting-300:27
*** mhagedorn has joined #openstack-meeting-300:27
*** cjellick has joined #openstack-meeting-300:27
*** Basil_Saito has joined #openstack-meeting-300:27
*** alexsyip has joined #openstack-meeting-300:27
*** _crobertsrh has joined #openstack-meeting-300:27
*** reed has joined #openstack-meeting-300:27
*** armax has joined #openstack-meeting-300:27
*** munish_ has joined #openstack-meeting-300:27
*** obondarev has joined #openstack-meeting-300:27
*** ozamiatin has joined #openstack-meeting-300:27
*** Adri2000 has joined #openstack-meeting-300:27
*** HenryG has joined #openstack-meeting-300:27
*** kgriffs|afk has joined #openstack-meeting-300:27
*** ttx has joined #openstack-meeting-300:27
*** haleyb has joined #openstack-meeting-300:27
*** jaypipes has joined #openstack-meeting-300:27
*** burgobianco has joined #openstack-meeting-300:27
*** chuckC_ has joined #openstack-meeting-300:27
*** kashyap has joined #openstack-meeting-300:27
*** edleafe has joined #openstack-meeting-300:27
*** mtreinish has joined #openstack-meeting-300:27
*** miguelgrinberg has joined #openstack-meeting-300:27
*** davidlenwell has joined #openstack-meeting-300:27
*** mestery has joined #openstack-meeting-300:27
*** edhall_ has joined #openstack-meeting-300:27
*** wendar has joined #openstack-meeting-300:27
*** rhagarty has joined #openstack-meeting-300:27
*** dansmith has joined #openstack-meeting-300:27
*** jeblair has joined #openstack-meeting-300:27
*** rossella_s has joined #openstack-meeting-300:27
*** anteaya has joined #openstack-meeting-300:27
*** gugl3 has joined #openstack-meeting-300:27
*** marios_ has joined #openstack-meeting-300:27
*** fungi has joined #openstack-meeting-300:27
*** vishy has joined #openstack-meeting-300:27
*** zhiyan has joined #openstack-meeting-300:27
*** d0ugal has joined #openstack-meeting-300:27
*** flaper87 has joined #openstack-meeting-300:27
*** zz_johnthetubagu has joined #openstack-meeting-300:27
*** leifz has joined #openstack-meeting-300:27
*** jgrimm has joined #openstack-meeting-300:27
*** alaski has joined #openstack-meeting-300:27
*** dosaboy has joined #openstack-meeting-300:27
*** jrist has joined #openstack-meeting-300:27
*** DinaBelova has joined #openstack-meeting-300:27
*** troytoman_ has joined #openstack-meeting-300:27
*** abramley has joined #openstack-meeting-300:27
*** ctracey has joined #openstack-meeting-300:27
*** persia has joined #openstack-meeting-300:27
*** jraim has joined #openstack-meeting-300:27
*** s1rp has joined #openstack-meeting-300:27
*** redrobot has joined #openstack-meeting-300:27
*** dhellmann has joined #openstack-meeting-300:27
*** krotscheck has joined #openstack-meeting-300:27
*** tidwellr has joined #openstack-meeting-300:27
*** mikal has joined #openstack-meeting-300:27
*** sankarshan_away has joined #openstack-meeting-300:27
*** sandr8 has joined #openstack-meeting-300:27
*** beagles has joined #openstack-meeting-300:27
*** mordred has joined #openstack-meeting-300:27
*** yamahata_ has joined #openstack-meeting-300:27
*** ekarlso has joined #openstack-meeting-300:27
*** maurosr has joined #openstack-meeting-300:27
*** tteggel has joined #openstack-meeting-300:27
*** rharwood has joined #openstack-meeting-300:27
*** jomara has joined #openstack-meeting-300:27
*** sc68cal has joined #openstack-meeting-300:27
*** dstanek has joined #openstack-meeting-300:27
*** cgoncalves has joined #openstack-meeting-300:27
*** russellb has joined #openstack-meeting-300:27
*** erw has joined #openstack-meeting-300:27
*** SergeyLukjanov has joined #openstack-meeting-300:27
*** blogan has joined #openstack-meeting-300:27
*** pleia2 has joined #openstack-meeting-300:27
*** rcleere_away has joined #openstack-meeting-300:27
*** aleksandr_null has joined #openstack-meeting-300:27
*** sdad has joined #openstack-meeting-300:27
*** notmyname has joined #openstack-meeting-300:27
*** dobson has joined #openstack-meeting-300:27
*** pcarver_ has joined #openstack-meeting-300:27
*** boltR has joined #openstack-meeting-300:27
*** NikitaKonovalov has joined #openstack-meeting-300:27
*** s3wong_ has joined #openstack-meeting-300:27
*** s3wong_ has quit IRC00:28
*** ChuckC has quit IRC00:28
*** s3wong has quit IRC00:28
*** yamamoto has joined #openstack-meeting-300:28
*** yamamoto has quit IRC00:33
*** seizadi has joined #openstack-meeting-300:33
*** marun has quit IRC00:33
*** pettori has quit IRC00:37
*** pettori has joined #openstack-meeting-300:40
*** yamamoto has joined #openstack-meeting-300:42
*** shakamunyi has joined #openstack-meeting-300:42
*** shakamunyi has quit IRC00:42
*** pettori has quit IRC00:44
*** pettori has joined #openstack-meeting-300:45
*** pettori has joined #openstack-meeting-300:47
*** pettori has quit IRC00:48
*** cjellick has quit IRC00:55
*** alexsyip has quit IRC00:57
*** yamamoto has quit IRC01:00
*** dboik has quit IRC01:06
*** jgrimm is now known as zz_jgrimm01:10
*** david-lyle has joined #openstack-meeting-301:11
*** Germy has joined #openstack-meeting-301:12
*** amotoki has joined #openstack-meeting-301:14
*** dboik has joined #openstack-meeting-301:15
*** bpokorny has quit IRC01:25
*** sarob has joined #openstack-meeting-301:27
*** sarob has quit IRC01:31
*** stanzgy has joined #openstack-meeting-301:36
*** david-lyle has quit IRC01:39
*** seizadi has quit IRC01:41
*** esp has joined #openstack-meeting-301:43
*** tomoe has joined #openstack-meeting-301:47
*** jacalcat has joined #openstack-meeting-301:48
*** jacalcat has left #openstack-meeting-301:49
*** munish_ has quit IRC01:53
*** shakamunyi has joined #openstack-meeting-301:55
*** shakamunyi has quit IRC01:55
*** topol has joined #openstack-meeting-302:06
*** clu_ has quit IRC02:10
*** SumitNaiksatam has joined #openstack-meeting-302:29
*** esp has left #openstack-meeting-302:55
*** marun has joined #openstack-meeting-302:59
*** dboik has quit IRC03:05
*** ivar-laz_ has joined #openstack-meeting-303:20
*** ivar-laz_ has quit IRC03:20
*** ivar-lazzaro has quit IRC03:23
*** yamahata has quit IRC03:25
*** sarob has joined #openstack-meeting-303:30
*** sarob has quit IRC03:35
*** lhcheng has joined #openstack-meeting-303:38
*** Longgeek has joined #openstack-meeting-303:45
*** reed has quit IRC03:45
*** Longgeek has quit IRC03:51
*** lhcheng has quit IRC04:03
*** yamahata has joined #openstack-meeting-304:08
*** lhcheng has joined #openstack-meeting-304:40
*** marun has quit IRC04:42
*** lhcheng has quit IRC04:44
*** lhcheng has joined #openstack-meeting-304:45
*** lhcheng has left #openstack-meeting-304:46
*** Longgeek has joined #openstack-meeting-304:47
*** marun has joined #openstack-meeting-304:49
*** armax has quit IRC04:51
*** Longgeek has quit IRC04:52
*** marun has quit IRC04:54
*** marun has joined #openstack-meeting-304:59
*** marun has quit IRC05:04
*** topol has quit IRC05:25
*** sarob has joined #openstack-meeting-305:28
*** sarob has quit IRC05:32
*** k4n0 has joined #openstack-meeting-305:36
*** yamamoto_ has joined #openstack-meeting-305:38
*** emagana has joined #openstack-meeting-305:39
*** jtomasek has joined #openstack-meeting-305:44
*** Longgeek has joined #openstack-meeting-305:48
*** Longgeek has quit IRC05:52
*** jtomasek has quit IRC06:03
*** sc68cal has quit IRC06:10
*** jtomasek has joined #openstack-meeting-306:26
*** emagana has quit IRC06:27
*** emagana has joined #openstack-meeting-306:28
*** zz_ttrifonov is now known as ttrifonov06:28
*** mrunge has joined #openstack-meeting-306:29
*** ttrifonov is now known as zz_ttrifonov06:29
*** zz_ttrifonov is now known as ttrifonov06:30
*** emagana_ has joined #openstack-meeting-306:31
*** jtomasek has quit IRC06:32
*** emagana has quit IRC06:32
*** sc68cal has joined #openstack-meeting-307:04
*** jcoufal has joined #openstack-meeting-307:11
*** MaxV has joined #openstack-meeting-307:21
*** Longgeek has joined #openstack-meeting-307:28
*** vitorc has quit IRC07:33
*** iovadia has joined #openstack-meeting-307:53
*** safchain has joined #openstack-meeting-308:00
*** alexpilotti has joined #openstack-meeting-308:11
*** yamamoto_ has quit IRC08:16
*** emagana_ has quit IRC08:19
*** emagana has joined #openstack-meeting-308:20
*** yamahata has quit IRC08:20
*** vitorc has joined #openstack-meeting-308:21
*** emagana has quit IRC08:24
*** SumitNaiksatam has quit IRC08:25
*** SumitNaiksatam has joined #openstack-meeting-308:29
*** igordcard has joined #openstack-meeting-308:44
*** Longgeek has quit IRC08:45
*** emagana has joined #openstack-meeting-308:51
*** Longgeek has joined #openstack-meeting-308:55
*** emagana has quit IRC08:57
*** jcoufal has quit IRC09:06
*** zz_johnthetubagu is now known as johnthetubaguy09:09
*** ttrifonov is now known as zz_ttrifonov09:13
*** jtomasek has joined #openstack-meeting-309:27
*** yamamoto_ has joined #openstack-meeting-309:30
*** Longgeek has quit IRC09:34
*** Longgeek has joined #openstack-meeting-309:36
*** ozamiatin has quit IRC09:41
*** alexpilotti has quit IRC09:43
*** emagana has joined #openstack-meeting-309:46
*** alexpilotti has joined #openstack-meeting-309:48
*** emagana has quit IRC09:51
*** bradjones has joined #openstack-meeting-309:58
*** bradjones has quit IRC10:08
*** bradjones has joined #openstack-meeting-310:09
*** jcoufal has joined #openstack-meeting-310:14
*** yamahata has joined #openstack-meeting-310:22
*** igordcard has quit IRC10:23
*** emagana has joined #openstack-meeting-310:40
*** emagana has quit IRC10:44
*** mwagner_lap has quit IRC10:57
*** amotoki has quit IRC10:59
*** bradjones has quit IRC11:30
*** bradjones has joined #openstack-meeting-311:33
*** emagana has joined #openstack-meeting-311:34
*** mwagner_lap has joined #openstack-meeting-311:38
*** emagana has quit IRC11:39
*** yamamoto_ has quit IRC11:47
*** Germy has left #openstack-meeting-311:51
*** jcoufal has quit IRC11:57
*** jcoufal has joined #openstack-meeting-312:05
*** Germy has joined #openstack-meeting-312:05
*** asahlin has quit IRC12:12
*** MarkAtwood has joined #openstack-meeting-312:22
*** igordcard has joined #openstack-meeting-312:27
*** amotoki has joined #openstack-meeting-312:27
*** emagana has joined #openstack-meeting-312:28
*** vkmc has joined #openstack-meeting-312:32
*** emagana has quit IRC12:33
*** MarkAtwood has quit IRC12:45
*** tidwellr has quit IRC12:46
*** stanzgy has quit IRC12:55
*** tidwellr has joined #openstack-meeting-313:00
*** _crobertsrh is now known as crobertsrh13:04
*** Adri2000 has quit IRC13:11
*** sigmavirus24_awa is now known as sigmavirus2413:16
*** Adri2000 has joined #openstack-meeting-313:17
*** Adri2000 has quit IRC13:17
*** Adri2000 has joined #openstack-meeting-313:17
*** dboik has joined #openstack-meeting-313:17
*** MarkAtwood has joined #openstack-meeting-313:18
*** mfer has joined #openstack-meeting-313:22
*** emagana has joined #openstack-meeting-313:22
*** emagana has quit IRC13:27
*** marun has joined #openstack-meeting-313:27
*** julim has joined #openstack-meeting-313:28
*** dboik has quit IRC13:28
*** lblanchard has joined #openstack-meeting-313:33
*** pino has joined #openstack-meeting-313:37
*** pino has quit IRC13:38
*** pino has joined #openstack-meeting-313:38
*** asahlin has joined #openstack-meeting-313:42
*** mfer has quit IRC13:43
*** asahlin has quit IRC13:43
*** zz_jgrimm is now known as jgrimm13:44
*** mfer has joined #openstack-meeting-313:47
*** armax has joined #openstack-meeting-313:47
*** dboik has joined #openstack-meeting-313:50
*** thangp has joined #openstack-meeting-313:50
*** jcoufal_ has joined #openstack-meeting-313:52
*** amotoki has quit IRC13:52
*** jcoufal has quit IRC13:53
*** jcoufal_ is now known as jcoufal13:54
*** yamahata has quit IRC13:55
*** yamahata has joined #openstack-meeting-313:55
*** mfer has quit IRC13:58
*** marun has quit IRC13:58
*** julim has quit IRC13:58
*** mfer has joined #openstack-meeting-314:00
*** mfer has quit IRC14:00
*** julim has joined #openstack-meeting-314:00
*** mfer has joined #openstack-meeting-314:01
*** jschwarz has joined #openstack-meeting-314:02
*** ihrachyshka has joined #openstack-meeting-314:02
*** ajo has joined #openstack-meeting-314:06
*** marun has joined #openstack-meeting-314:11
*** salv-orlando has joined #openstack-meeting-314:13
*** vkmc has quit IRC14:13
*** nelsnelson has joined #openstack-meeting-314:15
*** emagana has joined #openstack-meeting-314:16
*** k4n0 has quit IRC14:17
*** emagana has quit IRC14:21
*** emagana has joined #openstack-meeting-314:24
*** dboik has quit IRC14:27
*** jacalcat has joined #openstack-meeting-314:28
*** dboik has joined #openstack-meeting-314:28
*** vkmc has joined #openstack-meeting-314:31
*** lblanchard has quit IRC14:31
*** ChuckC has joined #openstack-meeting-314:33
*** emagana has quit IRC14:34
*** hurgleburgler has joined #openstack-meeting-314:35
*** emagana has joined #openstack-meeting-314:35
*** markmcclain has joined #openstack-meeting-314:35
*** mrunge has quit IRC14:36
*** emagana has quit IRC14:40
*** emagana has joined #openstack-meeting-314:43
*** igordcard has quit IRC14:45
*** regXboi has joined #openstack-meeting-314:45
*** SumitNaiksatam has quit IRC14:46
*** mhagedorn is now known as mwhagedorn14:47
*** SumitNaiksatam has joined #openstack-meeting-314:47
*** asahlin has joined #openstack-meeting-314:53
*** s3wong has joined #openstack-meeting-314:58
* regXboi pads in14:59
mesteryHi folks, we'll start the neutron-drivers meeting soon and discuss summit schedules14:59
*** sweston has joined #openstack-meeting-315:00
* regXboi wonders what the definition of "soon" is :)15:00
*** pc_m has joined #openstack-meeting-315:00
jschwarzsoon (tm)15:00
*** amotoki has joined #openstack-meeting-315:00
regXboijschwartz: nice :)15:00
*** dboik has quit IRC15:01
regXboier - fingers aren't working this morning15:01
*** dboik has joined #openstack-meeting-315:01
jschwarzI'm here to please :>15:01
* regXboi goes to look for more caffeine15:01
*** dboik has quit IRC15:01
salv-orlandoaloha15:01
*** jlibosva has joined #openstack-meeting-315:01
marunhi15:01
amotokihi15:01
mestery#startmeeting neutron-drivers15:02
openstackMeeting started Wed Oct 22 15:02:00 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
regXboimoo15:02
*** carl_baldwin has joined #openstack-meeting-315:02
*** openstack changes topic to " (Meeting topic: neutron-drivers)"15:02
openstackThe meeting name has been set to 'neutron_drivers'15:02
swestonIs Salvatore in Hawaii? :-)15:02
mestery#topic Kilo Summit Schedule15:02
*** openstack changes topic to "Kilo Summit Schedule (Meeting topic: neutron-drivers)"15:02
markmcclainhi15:02
*** dboik has joined #openstack-meeting-315:02
mesteryWe'll discuss this today, and that's about it since I estimate it will take the full hour15:02
regXboimestery: etherpad link?15:02
*** eglynn has joined #openstack-meeting-315:04
amotoki#link https://etherpad.openstack.org/p/kilo-neutron-summit-topics-distilled15:04
mestery#link https://etherpad.openstack.org/p/kilo-neutron-summit-topics-distilled15:04
mesteryamotoki: You beat me :)15:04
mesteryWe have 4 slots on Wed, and 7 slots Thur15:04
* regXboi wonders if #undo works15:05
mesterySo very limited compared to Atlanta15:05
regXboi#undo15:05
*** otherwiseguy has joined #openstack-meeting-315:05
* regXboi guesses not for non chairs15:05
mesteryThe drivers team has taken all the feedback from the original etherpad and condensed it into what is on the distilled page15:05
*** ilyashakhat has joined #openstack-meeting-315:05
markmcclainregXboi: yeah non chairs don't get many commands15:05
*** emagana has quit IRC15:05
mesteryIn an attempt to get something manageable15:05
mesteryThe goal with Kilo is paying down technical debt, per my email to the list.15:06
mesteryAnd we're trying to focus on things which require F2F time in Paris, not things which can be done on ML or IRC15:06
*** emagana has joined #openstack-meeting-315:06
*** tomoe_ has joined #openstack-meeting-315:06
mesterySo, that's the back story.15:06
markmcclainalso we've got the tables on Friday15:06
mesterymarkmcclain: Good point, thanks for reminding me of that.15:07
markmcclainso topics of interest to sub groups within the community fit better there15:07
mesteryAny questions so far from people?15:07
marunyes15:07
marunI've requested a number of times that we include time for lightning talks in the schedule.15:08
mesteryYou mean like taking one 40 minute slot for 5 minute lightning talks?15:08
marunTo ensure that those that don't get summit time do get to present to the community briefly about what they want to meet about in the unscheduled times.15:08
marunYes15:08
* mestery thinks on this for a minute15:08
marunI think that's only fair given how many people won't be getting time due to the focus on community stuff.15:09
*** jpomero has joined #openstack-meeting-315:09
maruntime -> time in the regular sessions15:09
* regXboi notes: marun: +115:09
*** seizadi has joined #openstack-meeting-315:09
amotokiit is useful to form some small groups or BoF.15:09
*** tomoe has quit IRC15:09
markmcclainso we're very limited on slots15:09
marunThat's a poor excuse.15:10
markmcclainwhat if we kept a backlog of lightning talk requests15:10
marunI think we can spare a single slot.15:10
*** reed has joined #openstack-meeting-315:10
markmcclainand if any sessions run short of their allocation we pull from backlog?15:10
markmcclainmarun: if the nova/neutron session gets pushed back into our track we'll be in a big time crunch15:10
mesteryI don't think it's a poor excuse, rather the realities of the situation, but I understand your point of view as well marun.15:10
marunWhile that seems reasonable on its face, I don't think it's wise.15:10
marunmarkmcclain: ^^15:10
salv-orlandolet’s just look at cost/benefits15:11
marunThe whole point of lightning talks is that they are scheduled.15:11
salv-orlandothe cost is 1 slot = 9% of neutron summit time15:11
marunThose that are giving them and those that want to attend have a time to be in the same room.15:11
salv-orlandowhat about the benefit?15:11
*** emagana has quit IRC15:11
salv-orlandoI mean my concernis what benefit there will be in talking 5 minutes about something? Merely community exposure?15:11
marun9% seems a pretty tiny amount to allow the community to focus on what they want to focus on in addition to everything that we consider core.15:11
marunExposure, yes.15:12
markmcclainmarun: what do you propose we cut?15:12
marunmarkmcclain: good question15:12
marunmarkmcclain: Do you have a priority listing of the sessions scheduled thus far?15:12
mesterymarun: It's on the etherpad we linked15:13
marunmarkmcclain: Such that you know what would be worth giving up?15:13
mesteryWe've allocated the slots.15:13
mesteryAs best as we could so far.15:13
marunYou all have been thinking about this an awful lot more than any of us.15:13
mesteryThus, something from there needs to go if we were to do this.15:13
marunI think my point is that community focus doesn't just include the technical.15:13
marunIt includes giving people the opportunity to participate.15:13
*** kgriffs|afk is now known as kgriffs15:13
mesteryFair point15:14
markmcclainmarun: I agree with that sentiment15:14
marunSo, olive branch.15:14
*** david-lyle has joined #openstack-meeting-315:14
marunThere are many that are going to be upset that they don't get time in from of everyone they way they have in the past.15:14
mesteryWell, no matter what we do, there will be many people who are upset.15:15
marunI think most would agree that it's a positive change, because we have lots we have to talk about to ensure our continued success.15:15
marunBut I don't think it's unreasonable that people still get a limited forum to present why their ideas are important.15:15
salv-orlandomarun: I think there will be many people wishing to argue on the “continued success” statement ;)15:15
marunAnyway, I've spoken my piece.15:16
mesterymarun: I'm thinking of what we can cut out out now to give a lightning talk slot.15:16
* regXboi notes looking at the list of slots, the only one that might make sense to give up is the last one on the list...15:16
* regXboi notes *MIGHT* not does15:17
*** vkmc has quit IRC15:17
amotokia question is how many folks would like lighting talks. Does 8 LT slots fit? who can present?15:17
marunI'm not sure why we need a whole session on rpc, frankly15:17
marunamotoki: lottery?15:17
marunamotoki: the logistics are less important than getting the slot.15:17
mestery6 is more reaslistic15:17
mestery8 is too manyu for 40 mionutes15:17
marunmestery: we could do 815:17
mesterymarun: Do you agree?15:17
mesterymarun: How?15:17
mestery40 minutes, time for swapping, 8 is tight, right?15:17
* mestery rhymes his way to reason15:17
markmcclainhaha15:18
amotokiFrom the driver discussion last week, slots with a bit weeker need is "Plugin/RPC API" (a partof API sessions).15:18
marunagain, the logistics could be resolved if the commitment is made15:18
*** Sukhdev has joined #openstack-meeting-315:18
marunit could be put to a vote, frankly.15:18
dougwig8 only works if you assume no teardown/setup time.  which is unrealistic.15:18
amotokiCLI slot might not need a full slot.15:18
marunbut let's not focus on that.15:18
mesteryAgreed.15:18
markmcclainmarun: so folks want exposure for stuff right?15:18
markmcclainwhat if had slides or page of links to ideas and contacts?15:19
marundougwig: they do it at pycon :)15:19
*** david-lyle has quit IRC15:19
s3wongdoing 8 means there is absolutely no time for Q&A --- so it is really just getting the 5 minutes exposure (5 minutes pitch)15:19
marunmarkmcclain: There is something special about lightning talks for galvanizing interest in your ideas.15:19
maruns3wong: q&a can come after, informally15:20
markmcclainmarun: that I agree with15:20
markmcclainbut given time constraints15:20
mesterylightning talks have no Q&A15:20
markmcclainjust concerned15:20
marunmarkmcclain: I think it's better than nothing.15:20
markmcclainalternatively we could steal 5 mins of some slots15:20
marunbut why don't we take this to the list?15:20
salv-orlandoshould we allocate a lightning talk on the tail of each session?15:20
salv-orlandoor some?15:20
marunAsk if people think it's a good idea, and how to do it?15:21
marunI mean, the value is really up to the community at large.15:21
mesteryOK, I think we'll need to allow for some time for lightning talks15:21
*** MarkAtwood has quit IRC15:21
mesteryLogistically, I'll figure out how to make it work.15:21
mesterymarun: Sound fair?15:21
s3wongactually doing 5 minutes on tail end of each session is a good idea, instead of bombarding community with 8 non-stop talks15:21
-amotoki- am afraid allocating the last 5min of each session does not work..15:22
maruns3wong: it's not so bad, ask anyone who's been to pycon15:22
maruns3wong: the energy around lightning talks means that they fly by15:22
maruns3wong: no chance to get bored15:22
marunanyway, mestery has agreed to make it work (thank you!) so we can probably move on.15:23
s3wongmarun: not bored for sure. wonder if the presentations would stick into people's mind --- but agree we can try15:23
*** crobertsrh has left #openstack-meeting-315:23
armaxmarun: +115:23
dougwigs3wong: from my experience at atlanta, 40 minutes was either dreadfully too short, or the session in question could've been 15 minutes.  and with some of the contentious slots on the schedule...15:23
mesteryLets move on, as marun indicated, we'll slot this in somehow.15:23
*** pballand has quit IRC15:23
amotoki+115:23
mesteryOK, getting back to what is on the agenda, lets look at Day 1 now.15:24
*** vkmc has joined #openstack-meeting-315:24
*** pballand has joined #openstack-meeting-315:24
mesteryDay has: Dev Process and Procedures, Neutron split, and CLI/Client lib.15:24
mesteryNothing contentious in there at least ;)15:24
regXboimestery: well15:24
mesterySeems like a solid first day to move forward with. Comments from people?15:25
regXboiI *could* argue that CLI/Client Lib goes along with the whole REST/RPC/Plugin API discussion15:25
mesteryregXboi: You could, sounds like you may? ;)15:25
regXboino, just wondering if I can create a slot15:26
mesteryregXboi: Heh :)15:26
regXboibut otherwise day 1 looks solid15:26
marunI'm not sure what we'll have to discuss around client/cli, honestly.15:26
marunIt's a serious problem, no question.15:27
markmcclainmarun: imploding them :)15:27
marunBut most seem to accept its deficiencies and may not have much to say about what needs to be done.15:27
salv-orlandothe client side discussion is more about reconsidering our approach to what we call client now and discussiing hot it could be reworked15:27
salv-orlandoregardless of the shape of the API15:27
marunIt may be worth floating a proposal for refactor on the ML and see if there are any detractors that suggest a session is necessary.15:27
*** pballand has quit IRC15:27
markmcclainalso we need folks to help align our efforts with the openstack sdk work15:27
marunsalv-orlando: fair enough.15:27
*** seizadi has quit IRC15:28
markmcclainthe client lib is a consistent complaint we get from users15:28
salv-orlandowe probably won’t have even time to talk about usability of the CLI15:28
marunI guess my point is that the point of the summit sessions now is discussion.15:28
markmcclainmany still use nova as a proxy because of our client is bad15:28
marunThat would imply we need a critical mass of interested parties to participate.15:28
marunAnd even though I am one of them, I'm not sure we have that critical mass.15:28
mesteryThat's what summits are for?15:28
marunBut if you are sure, please ignore me. :)15:28
* marun is sorry for nitpicking15:29
marunplease continue with day 215:30
mesterymarun: Not nit-picking, I appreciate your input here for sure.15:30
mesteryOK15:30
mesteryDay 2 (unless there are more comments on Day 1) ...15:30
amotokiat least we need to decide the direction of our cli. it may not need a full slot.15:30
markmcclainamotoki: the cli is one side of it.. we also have the lib side of it15:30
mesteryDay 2 starts with a doozie: REST/RPC/Plugin/API15:30
mesteryLots to discuss there.15:30
amotokimarkmcclain: yes.15:31
salv-orlandomestery: the last separator should not be a / but a space15:31
salv-orlandoREST/RPC/Plugin API ;)15:31
marunI'm sure of the need for REST and Plugin API.15:31
mesterysalv-orlando: Ack15:31
marunNot so sure about RPC - what exactly is contentious here?15:31
mesteryNothing contentious about RPC15:31
*** kgriffs has left #openstack-meeting-315:32
markmcclainwe have design issues to work through15:32
* regXboi wonders if he should ask the async/sync question15:32
* mestery hopes regXboi has had his coffee this morning15:32
regXboiso... i'll ask - in this block is there any intent to start looking at async operations or is that already in scope and I've missed it?15:33
* regXboi is thinking towards multi-region support15:33
markmcclainregXboi: yes!15:33
regXboimarkmcclain: :)15:33
marunmarkmcclain: Don't those issues more properly belong in the agent refactor discussion?15:33
markmcclainthat flows into part of the REST API and the behavioral semantics of the what happens15:33
markmcclainmarun: that too15:33
marunmarkmcclain: We need a common framework designed around distributed system principles.15:33
markmcclainit overlaps with both15:34
marunmarkmcclain: I'd rather see the agent refactor get more time and include discussion around rpc.15:34
salv-orlandothe funny fact is that most neutron operations are already async. Problem is that we’ve got no indication of that anywhere.15:34
marunmarkmcclain: Or is the goal to provide slack time for rest and plugin api?15:34
markmcclainsalv-orlando: right15:34
marunmarkmcclain: I think I'd rather see those 2 just get 3 slots rather that pretending that RPC needs our full attention there.15:35
markmcclainmarun: yes… rpc is fills in a portion of that block15:35
*** cjellick has joined #openstack-meeting-315:35
marunsalv-orlando: async, but not eventually consistent :/15:35
markmcclainI would not look at that block as 3 items needing equal time allocation in the 3 slot block… it's really a weighted15:35
marunmarkmcclain: fair enough15:36
regXboihonestly, I read it the same way as markmcclain: it's a 120 minute block that can be used as needed15:36
markmcclaindistribution and we wanted the ability to flow and 3 slots felt like a natural allocation for all 3 items but 1 slot was not enough for some15:36
mesterySee? Nothing contentious about the first slot on day 2. :)15:36
* mestery ducks15:36
* regXboi hopes mestery was joking :)15:36
salv-orlandomarun: no need to disturb eventual consistency… suffice to say that there’s no tracking of the operation, expect for what the agent decides to tell us indirectly about it15:37
marunsalv-orlando: magic? ;)15:37
* regXboi wonders - do we need a slot for adv svc spin out?15:37
amotokii think the slots are to dicsuss what behaviors are expected and visible to REST API, so there are many potential topics including tasks.15:37
* regXboi is reading ahead15:37
salv-orlandomarun: it is correct to say that we currently rely on the agents being nice and merciful15:37
markmcclainregXboi: we have to walk through the mechanics15:37
mesteryregXboi: Surely you jest?15:37
markmcclainand timing15:37
-amotoki- wonder where the item on taks is gone15:37
markmcclainamotoki: tasks is part L2 agent refactor and part plugin API15:38
salv-orlandoregXboi: the adv svc spin out poses challenges regarding API design and db management that we need to achieve consensus on.15:38
regXboimarkmcclain, mestery: wondering what the end result is supposed to be - but I'll ask that when we get there15:38
mesteryNote that IPAM now has it's own cozy slot in Paris.15:38
armaxamotoki: what do you mean?15:39
s3wongsalv-orlando: agreed, I think adv. service spin out is an important item to discuss with some f2f time15:39
regXboimestery: yeah, that one still doesn't quite grok15:39
carl_baldwinDid I hear IPAM?15:39
amotokiarmax: "task" related topic is related to API.15:39
markmcclaincarl_baldwin: yep.. we're actually going to talk about it15:39
mesterycarl_baldwin: You did, and pluggable IPAM even15:39
armaxamotoki: currently it’s being captured in the etherpad for ‘Resource lifecycle and status representation'15:40
armaxamotoki: but that can be moved15:40
carl_baldwinI’ve had IPAM on my mind for a while.15:40
markmcclaininstead of kick can down the road15:40
amotokiit is a topic how we manage states of operations.15:40
amotokiarmax: thanks15:40
regXboiso... I'll come back and ask on the adv svc spin out (since that's the next slot) - the etherpad doesn't reveal what the expected outcomes might be15:40
mesteryregXboi: I think markmcclain indicated what we expect, to work out some details and finalize a roadmap for this in Kilo.15:41
regXboia roadmap for Kilo or a roadmap for future releases starting with Kilo?15:41
armaxregXboi: I guess the outcome is to be determined at the session15:41
s3wongmestery: regXboi made a great point --- for all these selected design sessions, do we have designated people to prepare for presentation?15:42
* regXboi is trying to nail down the ambiguity15:42
armaxregXboi: we can start brainstorm on the etherpad for sure15:42
* regXboi wonders where he made the point ascribed to him15:43
mesterys3wong: Yes for most, for others we're working on this.15:43
*** david-lyle has joined #openstack-meeting-315:43
salv-orlandos3wong: we might designate session chairs but I don’t think we need presentations or slides15:43
mesteryregXboi: Me too actually, I don't know how s3wong made that correlation :)15:43
* mestery thinks we should ban slides again15:43
mesteryBecause ... PPT15:43
salv-orlandoor keynote for that matter, or even openoffice15:44
regXboiso... I'm still trying to nail down an ambiguity - a roadmap for Kilo or a roadmap for future releases starting with Kilo?15:44
salv-orlandoit’s just the idea of the “talk” that should be banned15:44
mesteryregXboi: Roadmpa for adv svcs spinout?15:44
mesterysalv-orlando: +100015:44
regXboimestery: yes15:44
markmcclainmestery: +100000000000 for banning PPT15:44
anteayas3wong: I think what neutron is trying to do is move away from presentation format, which other programs don't use, and move to discussion format, which is rather the point of the summit15:44
mesteryanteaya: +100000000015:44
mesteryregXboi: The roadmap for both, kilo and the spinout15:45
s3wongregXboi: when you said you didn't know what to discuss in adv. service spinout session --- it implies there has to be people responsible for the actual discussion point --- that's how I perceive it :-)15:45
markmcclainright… we'll someone to facilitate discussion15:45
salv-orlandos3wong: that would setup in an etherpad collaboratively compiled before the summit15:45
markmcclainand probably have a strawman proposal to work from15:45
s3wongsalv-orlando: sounds good15:45
* regXboi hopes rooms have whiteboards or easels for unconference type things15:45
salv-orlandoI think we already did is for Atlanta, didn’t we15:45
mesteryLess leaders, more collaboration?15:45
markmcclainit should be noted that the spinout depends on the results of the discussion from day 115:46
* salv-orlando is a follower looking for a leader15:46
markmcclainso would expect changes15:46
mesteryYes, some of this is dynamic, as these types of things tend to be15:46
regXboihmm, ok I see my confusion... in my head, I'm already thinking of adv svcs as described in the etherpad as an 'M" thing15:47
dougwigM?  as in release M?15:48
mesteryregXboi: Moar coffee15:48
* regXboi doesn't drink coffee15:48
s3wongsalv-orlando: in design summit session? no --- we didn't use whiteboard (just etherpad); in pod area, yes15:48
* regXboi notes nobody wants to see him hopped up on caffeine15:48
mesteryLets not confuse adv. svcs (LBaaS, VPNaaS, and FWaaS) with service chaining here, which is I think what regXboi was doing.15:49
regXboimestery: not precisely15:49
s3wongparticularly when we talk about "spinning out" --- clearly it is in context of the existing advanced services (LB/FW/VPN)15:49
mesterys3wong: Yes15:49
regXboium15:50
regXboimestery: that etherpad needs updating because that context is *NOT* clear15:50
mesteryregXboi: Please feel free to update. :)15:50
mesteryTime to move on: Eveyrone is ok talking IPAM? /cc carl_baldwin15:50
mestery???15:50
carl_baldwinI am15:51
salv-orlandoOr anybody NOT OK talking about IPAM?15:51
mesterysalv-orlando: That's a beter way to discuss this I think.15:51
mesteryOr frame it, rather15:51
* salv-orlando if you’re one of those I’ll assign you all the deadlock and lock wait timeout bugs that come out from ipam15:51
mesteryOK, IPAM it is. Moving on.15:51
mesteryRefactoring in agents and paying down technical debt there.15:52
mesteryThis is an area which overlaps a few things.15:52
mesteryAnd finally, we have a slot for retrospective.15:53
mesteryI'm personally of the opinion that this is ok, but that it would be better to do this post-Summit once people ahve recovered from partying (and design summit sessions).15:54
regXboimestery: that was the slot I was thinking of suggesting for LTs15:54
s3wongmestery: that is a prime candidate to be replaced by lighting talks?15:54
mesteryregXboi: Me as well to be honest15:54
mesteryI think the first Neutron meeting post-Summit could be used entirally for priorities and we could nail them down there.15:55
* mestery notes 5 minutes left ...15:55
*** mwagner_lap has quit IRC15:55
*** gholler has joined #openstack-meeting-315:55
amotokidon't we need to discuss about Friday?15:55
mesteryamotoki: Yes, but really we can allow signups there as we have 2 3.5 hour blocks15:56
mesteryAt a round table in a room with other round tables and discussions going on15:56
mesterySo for that, we can push things which require a smaller # of people or things which overflow.15:56
mesteryJust my current thinking15:56
markmcclainthere will also be the pods as in past years too15:57
mesteryOK, since we're almost out of time, I think we can wind this down now.15:57
markmcclainso I think that can help folks advertise when pods sessions are occuring too15:57
mesteryI will finalize the schedule and upload to sched.org by Friday.15:57
mesterySo please reach out to me if you have questions or concerns before then.15:57
markmcclainsince in many instances lightning talks are really just open to recruit more for wider discussion15:58
mesteryAnd thanks for attending this week everyone!15:58
mestery#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Wed Oct 22 15:58:23 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-10-22-15.02.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-10-22-15.02.txt15:58
salv-orlandoadieuuuuu15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-10-22-15.02.log.html15:58
s3wongbye15:58
armaxbye15:58
amotokigood night15:58
markmcclainbye15:58
regXboioom15:58
*** jlibosva has left #openstack-meeting-315:58
*** s3wong has quit IRC15:58
*** pc_m has left #openstack-meeting-315:58
*** mestery has quit IRC15:59
*** ihrachyshka has left #openstack-meeting-316:00
*** lhcheng has joined #openstack-meeting-316:00
*** lhcheng has left #openstack-meeting-316:01
*** regXboi has left #openstack-meeting-316:03
*** mestery has joined #openstack-meeting-316:04
*** jcoufal has quit IRC16:05
*** bpokorny has joined #openstack-meeting-316:06
*** dboik has quit IRC16:06
*** shakamunyi has joined #openstack-meeting-316:08
*** shakamunyi has quit IRC16:08
*** mitarun has joined #openstack-meeting-316:13
*** emagana has joined #openstack-meeting-316:17
*** jschwarz has quit IRC16:17
*** Longgeek has quit IRC16:20
*** jacalcat1 has joined #openstack-meeting-316:20
*** jacalcat has quit IRC16:21
*** jtomasek has quit IRC16:25
*** MaxV has quit IRC16:28
*** markmcclain has quit IRC16:31
*** alexsyip has joined #openstack-meeting-316:33
*** seizadi has joined #openstack-meeting-316:35
*** bradjones has quit IRC16:43
*** hinnant_ has joined #openstack-meeting-316:43
*** dboik has joined #openstack-meeting-316:45
*** mrunge has joined #openstack-meeting-316:48
*** dboik has quit IRC16:49
*** s3wong has joined #openstack-meeting-316:54
*** mwagner_lap has joined #openstack-meeting-316:56
*** gholler has quit IRC16:59
*** dboik has joined #openstack-meeting-317:03
*** pettori has joined #openstack-meeting-317:04
*** pettori has quit IRC17:05
*** markmcclain has joined #openstack-meeting-317:07
*** amotoki has quit IRC17:07
*** mitarun has quit IRC17:13
*** yamahata has quit IRC17:15
*** pritesh has joined #openstack-meeting-317:16
*** pino has quit IRC17:17
*** pino has joined #openstack-meeting-317:17
*** Sukhdev has quit IRC17:18
*** eglynn is now known as eglynn-afk17:21
*** pino has quit IRC17:22
*** safchain has quit IRC17:23
*** sarob has joined #openstack-meeting-317:23
*** bpokorny has quit IRC17:24
*** ivar-lazzaro has joined #openstack-meeting-317:25
*** lblanchard has joined #openstack-meeting-317:26
*** pettori has joined #openstack-meeting-317:26
*** lblanchard has quit IRC17:27
*** sarob has quit IRC17:28
*** sarob_ has joined #openstack-meeting-317:28
*** pc_m has joined #openstack-meeting-317:29
*** hemanthravi has joined #openstack-meeting-317:32
*** bpokorny has joined #openstack-meeting-317:33
*** lblanchard has joined #openstack-meeting-317:33
*** lblanchard has quit IRC17:34
*** bpokorny_ has joined #openstack-meeting-317:35
*** eglynn-afk is now known as eglynn17:35
*** bpokorny has quit IRC17:37
*** julim has quit IRC17:39
*** pc_m has left #openstack-meeting-317:39
*** bpokorny has joined #openstack-meeting-317:46
*** dboik has quit IRC17:47
*** bpokorny_ has quit IRC17:49
*** hemanthravi has quit IRC17:50
*** johnthetubaguy is now known as zz_johnthetubagu17:52
*** pballand has joined #openstack-meeting-317:52
*** markmcclain has quit IRC17:58
*** iovadia has quit IRC17:58
*** pballand has quit IRC18:00
*** dboik has joined #openstack-meeting-318:01
*** otherwiseguy has quit IRC18:02
*** jacalcat1 has left #openstack-meeting-318:03
*** pballand has joined #openstack-meeting-318:11
*** marun has quit IRC18:14
*** pballand has quit IRC18:19
*** jgrimm is now known as zz_jgrimm18:26
*** pballand has joined #openstack-meeting-318:27
*** carl_baldwin has quit IRC18:28
*** SridarK has joined #openstack-meeting-318:30
*** natarajk has joined #openstack-meeting-318:30
SumitNaiksatamSridarK: natarajk: hi18:30
SridarKSumitNaiksatam: hi18:31
natarajkhi18:31
SridarKnatarajk: k18:31
SumitNaiksatam#startmeeting Networking FWaaS18:31
openstackMeeting started Wed Oct 22 18:31:43 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:31
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:31
openstackThe meeting name has been set to 'networking_fwaas'18:31
SumitNaiksatamseems like everyone is busy preparing for the summit ;-)18:32
*** pballand has quit IRC18:32
*** markmcclain has joined #openstack-meeting-318:32
SumitNaiksatam#info kilo design summit etherpad: https://etherpad.openstack.org/p/neutron-fwaas18:32
SumitNaiksatam#info neurtron kilo design summit topics: #link https://etherpad.openstack.org/p/kilo-neutron-summit-topics-distilled18:33
SumitNaiksatamlets get started with the standing items on the agenda18:33
SumitNaiksatam#topic Bugs18:33
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:33
SumitNaiksatamI dont see anything new popping up18:33
SumitNaiksatamSridarK: ?18:33
*** pballand has joined #openstack-meeting-318:33
SridarKSumitNaiksatam: not much to report18:33
SumitNaiksatami know badveli was going to do some additional testing18:34
SumitNaiksatambut he doesnt seem to be here18:34
*** julim has joined #openstack-meeting-318:34
SumitNaiksatamlets check back with him offline18:34
SridarKSumitNaiksatam: will do18:34
*** zz_jgrimm is now known as jgrimm18:35
SumitNaiksatami dont think any of the untriaged bugs are critical18:35
*** pballand has quit IRC18:36
*** carl_baldwin has joined #openstack-meeting-318:36
*** pritesh has quit IRC18:36
SridarKSumitNaiksatam: i will also take  a look18:36
SumitNaiksatamSridarK: thanks18:36
SumitNaiksatam#topic Docs18:36
*** openstack changes topic to "Docs (Meeting topic: Networking FWaaS)"18:36
SumitNaiksatamSridarK: any updates?18:36
SridarKSumitNaiksatam: not much on this18:36
SumitNaiksatamSridarK: let me know if you need anything from me, happy to jump in…18:37
*** glebo has joined #openstack-meeting-318:37
SridarKSumitNaiksatam: will do18:37
SumitNaiksatamok moving on18:37
SumitNaiksatam#topic Kilo blueprints18:38
*** openstack changes topic to "Kilo blueprints (Meeting topic: Networking FWaaS)"18:38
SumitNaiksatamSridarK: i noticed that you added a vendor blueprint for the CSR18:38
SumitNaiksatamglebo: hi there!18:38
*** pettori has quit IRC18:38
*** pettori has joined #openstack-meeting-318:39
SridarKSumitNaiksatam: yes resubmitted what we had for Juno18:39
SumitNaiksatamSridarK: thats a good thing18:39
SumitNaiksatamSridarK: we need to start refocussing on getting the process going18:39
gleboSumitNaiksatam: lo!18:39
SridarKSumitNaiksatam: now our dependencies are in18:39
SridarKglebo: hi18:39
SumitNaiksatamSridarK: agreed18:39
SumitNaiksatamglebo: is vishnu planning to repost the service groups blueprint?18:40
SumitNaiksatamnatarajk: what about your vendor spec?18:40
natarajki was planning to submit it after the design summit18:40
gleboSumitNaiksatam: absolutely18:40
SumitNaiksatamnatarajk: ok sure18:40
gleboI'll ping him on it18:40
glebosuprised he didn't do it already18:40
SumitNaiksatamglebo: yes, i think better to put it in at earliest18:40
SumitNaiksatamglebo: he might have had, and i might have missed it18:41
gleboSumitNaiksatam: ack18:41
SumitNaiksatamglebo: apologies in advance if i missed it18:41
*** pc_m has joined #openstack-meeting-318:41
glebo#action: glebo to encourage vishnu to submit service groups BP asap18:41
*** marun has joined #openstack-meeting-318:42
* glebo surprised vishnu not on the chat here himself18:42
SumitNaiksatamglebo: thanks for adding the AI18:42
SumitNaiksatam#action: glebo to encourage vishnu to submit service groups BP asap18:42
SumitNaiksatam#chairs SridarK natarajk glebo18:43
*** emagana has quit IRC18:43
SumitNaiksatam#chair SridarK natarajk glebo18:43
openstackCurrent chairs: SridarK SumitNaiksatam glebo natarajk18:43
SumitNaiksatamglebo: i checked, i dont think its in18:43
*** pettori has quit IRC18:43
SumitNaiksatamglebo: but its perfectly understandable if badveli is a bit confused and frustrated here18:44
gleboSumitNaiksatam: ya, me too. Already pinged him on it18:44
gleboSumitNaiksatam:  LOL!!18:44
*** carl_baldwin has quit IRC18:44
gleboSumitNaiksatam:  honestly, if he wasn't, I wouldn't be here18:44
SumitNaiksatamglebo: :-)18:44
SumitNaiksatami think we all are!18:44
SumitNaiksatamanyway18:45
gleboSumitNaiksatam:  moving on18:45
SumitNaiksatamso in terms any additional blueprints to be posted18:45
*** badveli has joined #openstack-meeting-318:45
SumitNaiksatami think we need the design summit discussion to go through18:45
glebobadveli joining any second now18:45
badvelithanks glebo18:45
badvelisorry18:45
SumitNaiksatamah badveli just joined18:45
SumitNaiksatambadveli: not worries18:46
SumitNaiksatam*no18:46
glebobadveli: good to see someone is still able to get emersed in coding18:46
glebobadveli:  ah… the good ol days…18:46
badvelithanks glebo, sorry today being diwali18:46
SumitNaiksatambadveli: we handed you an AI while you were busy actually working! ;-)18:46
badvelisorry sumit, did not see it18:47
glebobadveli:  let's go ahead and have u resubmit the BP for service groups18:47
glebobadveli: ack?18:47
badvelithe blue print?18:47
SumitNaiksatambadveli: yeah, the service groups18:47
badvelithe blue print is already approved18:47
glebobadveli: and do so asap, yeah, BP, spec and code, all in kilo18:47
*** bpokorny has quit IRC18:47
gleboSumitNaiksatam: that's the proper process?18:48
SumitNaiksatamglebo: yeah, we have to go by that, until we decide or are told to do something else18:48
badvelisumit, do we submit the bp and code by branch names?18:49
SridarKbadveli: u need to resubmit spec18:49
badvelithanks sridark, i will try to do that18:49
SumitNaiksatambadveli: resubmit the blueprint (you will have to make minor modifications since the template has changed slightly)18:49
SumitNaiksatambadveli: code can just be rebased18:49
badvelishould we get the approvals again?18:49
SumitNaiksatambadveli: yes, we need the approvals again on the spec18:50
badvelifor the blue print?18:50
* glebo here it comes, ducking18:50
SumitNaiksatambadveli: yes18:50
SumitNaiksatamglebo: :-)18:50
* glebo feels deja vu for badveli, and for all here, really18:50
SumitNaiksatambadveli: so things are clear on the process?18:50
* glebo lavers, rinses, repeats18:50
SumitNaiksatamglebo: deja vu for the nth time!18:50
gleboSumitNaiksatam:  so, is that deja vu vu vu vu vu vu vu18:51
SumitNaiksatamglebo: :-)18:51
gleboSumitNaiksatam:  or just more simply deja vu^918:51
SumitNaiksatambadveli: is the process clear?18:51
glebomaybe we ought to get shirts printed up for sumit, just for FWaaS team to wear, "deja vu^9"18:52
badveliyes, but this will still delay and not able to get why we are doing this again18:52
gleboand maybe we'll bring enough for the LBaaS and VPNaaS teams too18:52
badveliand getting the approvals18:52
badveliagain???18:52
SumitNaiksatamglebo: :-)18:52
glebosince u know they are having the exact same tongue n cheek exchange in their mtgs this week too18:52
SumitNaiksatambadveli: i share your frustration, and we are trying to find a solution18:52
gleboSumitNaiksatam:  badveli: +100018:53
SumitNaiksatambadveli: but until then we have to stay the course18:53
glebobadveli: Let's u and I take it offline. I can coach u thru it tomorrow, k?18:53
badvelifine with me, thanks glebo18:54
SumitNaiksatambadveli: open to your suggestions as well, if you think a different approach might be helpful18:54
badveliSumit, as you know how hard it is getting the approvals18:54
badveliand going through it again18:54
glebo*badveli pictures blow torches*18:54
*** bpokorny has joined #openstack-meeting-318:55
glebobadveli:  time check. Let's take it offline18:55
SumitNaiksatambadveli: agree, and hence we had team discussions to explore options18:55
SumitNaiksatamok moving on18:55
*** armax has quit IRC18:55
SumitNaiksatam#topic Kilo design summit discussion18:56
*** openstack changes topic to "Kilo design summit discussion (Meeting topic: Networking FWaaS)"18:56
s3wongbadveli: it is probably going to be worse this time. only five selected cores can give your spec a +A in Kilo cycle :-)18:56
SumitNaiksatams3wong: now you are really rubbing it in!18:56
s3wongSumitNaiksatam: :-)18:56
glebos3wong:  at least now we know which core's reviews really matter18:56
SumitNaiksatams3wong: yeah sad but (absolutely) true18:56
badvelithanks s3wong18:57
glebos3wong: that's a step in the right direction, or bright side18:57
SumitNaiksatams3wong: btw, welcome to fwaas!18:57
s3wongglebo: well, you still need the 2 +2's , but you need an extra step to get the +A in case the two cores that gave you +2's aren't one of the five18:57
* glebo snaps for s3wong18:57
glebos3wong: ack. Exactly18:58
s3wongSumitNaiksatam: just happened to be on #openstack-meeting-3; sorry for the interruption, please move on18:58
*** sarob_ has quit IRC18:58
glebos3wong:  but at least now we KNOW that18:58
*** markmcclain has quit IRC18:58
SumitNaiksatamok Kilo design summit discussion18:58
glebos3wong:  Which, you know, is nice18:58
*** sarob has joined #openstack-meeting-318:58
s3wongglebo: :-)18:58
*** pettori has joined #openstack-meeting-318:58
SumitNaiksatami provided link to the etherpad earlier #link https://etherpad.openstack.org/p/neutron-fwaas18:59
glebos3wong: actually, very helpful "interruption". Everyone needs to be clear on that process step18:59
SumitNaiksatamplease enter your input18:59
SumitNaiksatams3wong: right, you are welcome to stick around18:59
* glebo scanning epad18:59
SridarKSumitNaiksatam: the entries in the kilo epad have been preserved here19:00
glebobrb19:00
s3wongBTW, guys, in this morning's neutron-drivers meeting, a new "lighting talks" session is suggested and probably will replace the "retrospective" session19:00
SumitNaiksatamso as we had discussed within the team earlier, the following seem to be community priorities for FWaaS:19:00
SridarKi think that does reflect our priorities for kilo19:00
SumitNaiksatam1. Get FWaaS out of experimental status (address router insertion)19:01
SumitNaiksatam2. Support FWaaS for E-W scenario in DVR.19:01
SumitNaiksatam3. Service Groups (since this code is posted and in review)19:01
SumitNaiksatam4. Metering capabilities (Ceilometer dependency)19:01
SumitNaiksatam5. Flavors - we might need to support if this gets implemented19:01
*** bpokorny_ has joined #openstack-meeting-319:01
s3wongso don't be discouraged if your proposal didn't make the initial cut of design summit, you may still get to do a 5 minutes lighting talk19:01
*** carl_baldwin has joined #openstack-meeting-319:01
SridarKSumitNaiksatam: +119:01
*** sarob_ has joined #openstack-meeting-319:02
SumitNaiksatami would propose that we keep our focus on the above during the discussions19:02
SridarKSumitNaiksatam: +119:02
*** sarob has quit IRC19:02
SumitNaiksatamon point 1, i myself am not clear as to why FWaaS is qailified as “experimental”19:02
SumitNaiksatami was consulted on this point in the first release of fwaas, and my feedback was based on the insertion issue19:03
SridarKSumitNaiksatam: i think this is probab only open issue19:03
*** otherwiseguy has joined #openstack-meeting-319:04
SumitNaiksatamSridarK: yeah19:04
*** jtomasek has joined #openstack-meeting-319:04
* glebo back19:04
SumitNaiksatamare there any disagreements within the team on the above priorities?19:04
*** bpokorny has quit IRC19:04
SumitNaiksatamthe above obviously does not include vendor specific stuff19:05
*** eglynn has quit IRC19:05
SridarKSumitNaiksatam: agree, i guess we also have to see how this "services coming out of neutron" story plays out19:05
SumitNaiksatamthe above also in the context of Kilo19:05
SumitNaiksatamSridarK: agreed19:05
SridarKand how that impacts our list19:05
gleboon the above priorites,19:06
gleboI think we will gain a lot of cred in the community at large if19:06
SumitNaiksatamthe key to any “coming out” discussion is who are the cores19:06
glebowe are shown to be talking about pulling out vendor plugins from main19:06
gleboand creating an interface for them to easily be loaded as plugg-able modules19:07
SumitNaiksatamglebo: as i mentioned before pulling out vendor plugins is not a discussion just in the context of FWaaS19:07
gleboas I've mentioned before, it's a huge sticking point for several of the TC,19:07
gleboSumitNaiksatam:  understood19:07
glebobut19:07
*** david-lyle_ has joined #openstack-meeting-319:07
*** SridarK has quit IRC19:07
SumitNaiksatamglebo: this has been on the table for a long time, and i believe it will happen in Kilo19:07
gleboeach service element will need to address it for themselves,19:07
gleboso, if we show we are doing our part, it will earn us some cred19:08
*** markmcclain has joined #openstack-meeting-319:08
*** SridarK has joined #openstack-meeting-319:08
gleboSumitNaiksatam: exactly why we need to have it on our list,19:08
gleboso that we are being good citizens to the deeper architectural direction19:08
SumitNaiksatamglebo: yeah, sure we can put it on the list, but we will just be following what the rest of neutron is doing19:08
gleboSumitNaiksatam: make sense?19:08
gleboSumitNaiksatam:  sure, and19:09
gleboit indicates are are "cheefully complying" and19:09
*** david-lyle has quit IRC19:09
gleboif we can add some value there, the community will like that too, and19:09
glebowe need to ensure that the hooks, plugs, interfaces, structures, etc. that we need in order to succeed in such an extraction are present19:10
SumitNaiksatamglebo: yes we will definitely comply, i dont think we will have a choice, and we definitely prefer that option19:10
gleboSumitNaiksatam: so, it becomes a pretty big work item for us in kilo,19:10
gleboI'll add it to the epad19:10
SumitNaiksatamglebo: “interfaces” for plugging into neutron is not a FWaaS-specific topic19:11
SumitNaiksatamglebo: that becomes a general services’ discussion19:11
gleboSumitNaiksatam:  agreed, and19:11
*** marun has quit IRC19:11
SumitNaiksatamglebo: feel free to add to the etherpad, since it reinforces the discussion19:11
gleboFWaaS has it's side of it19:11
gleboit's our part of the service insertion model, our domain-specific elements19:12
SumitNaiksatamglebo: but i wanted to make sure that we dont get lost in that disucssion and hence stall on the features for FWaaS that are sort of independent of that aspect19:12
SumitNaiksatamby “that” i mean the “service insertion” related conversation19:13
gleboSumitNaiksatam:  not to be sarcastic, but to then go ahead and be sarcastic… those features aren't really "getting in" right now anyway19:13
SumitNaiksatamsince this has happened in the past two cycles19:13
gleboSumitNaiksatam: job 1: unstick the system, whatever it takes. Job 2: make FWaaS feature rich19:14
gleboSumitNaiksatam: doing 1 w/o 2 is wheel spinning, no?19:14
SumitNaiksatamalso, in the past we have tried justify the value/need of the service insertion framework using FWaaS as an exmaple/case study19:14
SumitNaiksatamhowever the net result of that was that we could neither get the service framework in, and we couldn’t solve the problem for fwaas either (and thus continue to be branded experimental)19:15
SumitNaiksatamglebo: so most of what you are saying is deja vu to me ;-) (and not trying to be sarcy there)19:16
gleboSumitNaiksatam: totally empathetic19:16
SumitNaiksatamokay so the meta point was, please put your comments on the etherpad :-)19:16
gleboSumitNaiksatam: right. Will do19:16
glebo;-)19:17
SumitNaiksatamglebo: ;-) but could be :-( just as well!19:17
glebo(some of my points are already there, prepended with [glebo])19:17
SumitNaiksatamglebo: nice19:17
SumitNaiksatamso what the above list means is that we miss out very critical features like zones and address groups19:17
SumitNaiksatamand logging and hit counts19:18
*** david-lyle_ is now known as david-lyle19:18
SumitNaiksatamthe fact that none of features were allowed to go through in the last two cycles has created a huge backlog of items19:19
SumitNaiksatamand that will take a long time to clear up in the current process/system  (if at all)19:19
glebo(hit counts is a very cool feature. We have them in our product, and customers LOVE them)19:19
SumitNaiksatamglebo: absolutely agree19:20
*** pballand has joined #openstack-meeting-319:20
SumitNaiksatamglebo: its critical for firewalls19:20
SumitNaiksatamso any way the point i wanted to make is that we havent lost track of these features19:20
SumitNaiksatambut we will unlikely have time for them with the current constraints19:21
SumitNaiksatamsince we are veering more into open discussion territory19:21
SumitNaiksatam#topic Open Discussion19:21
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:21
gleboSumitNaiksatam:  re: backlog, that's sort of ok, for the short term, because we aren't trying to build an open source FW here, just trying to define policy blobs. In reality, all the products can define their own policy blobs in their config / mgmt systems, so there is a work around in the short run, for operators, automatable through vendor API19:21
*** markmcclain has quit IRC19:22
SumitNaiksatamglebo: people prefer a single pane of glass19:22
*** markmcclain has joined #openstack-meeting-319:23
gleboSumitNaiksatam: any update from the service teams strategy session last week. As you know I left early. Saw the write up. Commented. But not sure if any response came back after that. ?19:23
*** natarajk has left #openstack-meeting-319:23
SumitNaiksatamglebo: i responded to your emails19:23
*** dboik has left #openstack-meeting-319:23
SumitNaiksatamglebo: i did not notice your emails until yesterday19:23
gleboSumitNaiksatam:  ok, must have missed it19:23
gleboSumitNaiksatam:  will check19:24
SumitNaiksatamglebo: for some reason the thread got buried and popped only because of s3wong’s email yesterday19:24
gleboSumitNaiksatam:  re: 1 glass: for sure. Wouldn't be here otherwise.19:24
SumitNaiksatamglebo: :-)19:24
SumitNaiksatamok if nothing else to discuss we can get 5 mins of our time back19:24
SridarKSumitNaiksatam: perhaps we can all start thinking about the priority list19:25
SumitNaiksatamSridarK: sure19:25
SridarKSumitNaiksatam: so in terms of spec etc we can get some early discussion at the summit19:25
SumitNaiksatami would also propose that we popularize this etherpad and make sure that we get a good critical mass of folks for the F2F discussions in the summit19:26
SumitNaiksatamok thanks folks for attending today19:27
SumitNaiksatambye!19:27
SridarKbye all19:27
SumitNaiksatam#endmeeting19:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:27
openstackMeeting ended Wed Oct 22 19:27:41 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:27
glebocheers19:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-10-22-18.31.html19:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-10-22-18.31.txt19:27
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-10-22-18.31.log.html19:27
badveli    bye19:28
*** pritesh has joined #openstack-meeting-319:28
*** jtomasek has quit IRC19:31
*** pc_m has left #openstack-meeting-319:33
*** seizadi has quit IRC19:36
*** mrunge has quit IRC19:37
*** seizadi has joined #openstack-meeting-319:37
*** seizadi has quit IRC19:47
*** gduan has joined #openstack-meeting-319:47
*** seizadi has joined #openstack-meeting-319:48
*** gduan has quit IRC19:48
*** ChuckC has quit IRC19:50
*** SridarK has quit IRC19:56
*** markmcclain has quit IRC19:58
*** MaxV has joined #openstack-meeting-319:58
*** sarob_ has quit IRC20:00
*** hinnant_ has quit IRC20:01
*** sarob has joined #openstack-meeting-320:01
*** sarob has quit IRC20:03
*** sarob has joined #openstack-meeting-320:03
*** pettori has quit IRC20:04
*** pettori has joined #openstack-meeting-320:05
*** otherwiseguy has quit IRC20:06
*** pettori has quit IRC20:11
*** otherwiseguy has joined #openstack-meeting-320:13
*** hinnant has joined #openstack-meeting-320:13
*** pritesh has quit IRC20:13
*** jtomasek has joined #openstack-meeting-320:18
*** MarkAtwood has joined #openstack-meeting-320:19
*** glebo1 has joined #openstack-meeting-320:19
*** igordcard has joined #openstack-meeting-320:20
*** ChuckC has joined #openstack-meeting-320:20
*** bpokorny has joined #openstack-meeting-320:20
*** glebo has quit IRC20:22
*** hurgleburgler has quit IRC20:23
*** bpokorny_ has quit IRC20:23
*** seizadi has quit IRC20:27
*** sarob has quit IRC20:28
*** sarob has joined #openstack-meeting-320:28
*** sarob has quit IRC20:30
*** sarob has joined #openstack-meeting-320:31
*** pballand has quit IRC20:35
*** pballand has joined #openstack-meeting-320:36
*** pballand has quit IRC20:43
*** pballand has joined #openstack-meeting-320:46
*** pballand has quit IRC20:49
*** sarob has quit IRC20:49
*** sarob has joined #openstack-meeting-320:49
*** vkmc has quit IRC20:53
*** sarob has quit IRC20:54
*** pballand has joined #openstack-meeting-320:54
*** tomoe_ has quit IRC20:54
*** jacalcat has joined #openstack-meeting-320:55
*** sarob has joined #openstack-meeting-320:56
*** carl_baldwin has quit IRC20:58
*** cgoncalves has quit IRC21:00
*** boris-42 has quit IRC21:00
*** sarob has quit IRC21:01
*** seizadi has joined #openstack-meeting-321:01
*** cgoncalves has joined #openstack-meeting-321:01
*** otherwiseguy has quit IRC21:02
*** seizadi1 has joined #openstack-meeting-321:03
*** seizadi has quit IRC21:03
*** MaxV has quit IRC21:03
*** igordcard has quit IRC21:05
*** boris-42 has joined #openstack-meeting-321:06
*** vkmc has joined #openstack-meeting-321:07
*** david-lyle_ has joined #openstack-meeting-321:10
*** bpokorny_ has joined #openstack-meeting-321:10
*** david-lyle has quit IRC21:11
*** vkmc has quit IRC21:12
*** bpokorny has quit IRC21:14
*** bradjones has joined #openstack-meeting-321:16
*** glebo1 has left #openstack-meeting-321:19
*** asahlin has quit IRC21:19
*** thangp has quit IRC21:28
*** david-lyle_ is now known as david-lyle21:31
*** bpokorny_ has quit IRC21:37
*** seizadi1 has quit IRC21:41
*** seizadi has joined #openstack-meeting-321:41
*** MarkAtwood has quit IRC21:41
*** dboik has joined #openstack-meeting-321:42
*** bpokorny has joined #openstack-meeting-321:45
*** markmcclain has joined #openstack-meeting-321:50
*** MarkAtwood has joined #openstack-meeting-321:50
*** vkmc has joined #openstack-meeting-321:57
*** carl_baldwin has joined #openstack-meeting-322:12
*** tgraf has quit IRC22:13
*** sigmavirus24 is now known as sigmavirus24_awa22:13
*** vkmc has quit IRC22:15
*** carl_baldwin has quit IRC22:20
*** ivar-lazzaro has quit IRC22:22
*** jtomasek has quit IRC22:23
*** ivar-lazzaro has joined #openstack-meeting-322:23
*** dboik has quit IRC22:23
*** asahlin has joined #openstack-meeting-322:24
*** bpokorny has quit IRC22:28
*** david-lyle_ has joined #openstack-meeting-322:30
*** david-lyle has quit IRC22:30
*** mfer has quit IRC22:35
*** jpomero has quit IRC22:37
*** peristeri has joined #openstack-meeting-322:39
*** seizadi has quit IRC22:40
*** nelsnelson has quit IRC22:42
*** markmcclain has quit IRC22:51
*** armax has joined #openstack-meeting-322:53
*** peristeri has quit IRC22:53
*** dboik has joined #openstack-meeting-322:57
*** bpokorny has joined #openstack-meeting-323:00
*** pballand has quit IRC23:00
*** tidwellr has left #openstack-meeting-323:03
*** alexpilotti has quit IRC23:19
*** pballand has joined #openstack-meeting-323:21
*** MarkAtwood has quit IRC23:25
*** s3wong has quit IRC23:27
*** marun has joined #openstack-meeting-323:28
*** pballand has quit IRC23:36
*** pballand has joined #openstack-meeting-323:36
*** pballand has quit IRC23:46
*** sarob has joined #openstack-meeting-323:50
*** sarob has quit IRC23:54

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!