Thursday, 2014-10-16

*** ivar-laz_ has quit IRC00:04
*** SumitNaiksatam has quit IRC00:13
*** ivar-lazzaro has joined #openstack-meeting-300:14
*** ivar-laz_ has joined #openstack-meeting-300:16
*** ivar-lazzaro has quit IRC00:16
*** ivar-laz_ has quit IRC00:17
*** ivar-lazzaro has joined #openstack-meeting-300:18
*** safchain has quit IRC00:30
*** otherwiseguy has quit IRC00:50
*** SumitNaiksatam has joined #openstack-meeting-300:57
*** ivar-laz_ has joined #openstack-meeting-301:08
*** sunrenjie6 has joined #openstack-meeting-301:09
*** ivar-lazzaro has quit IRC01:11
*** ivar-laz_ has quit IRC01:13
*** sankarshan is now known as sankarshan_away01:17
*** Longgeek has joined #openstack-meeting-301:19
*** alexsyip has quit IRC01:21
*** Longgeek has quit IRC01:25
*** bpokorny has quit IRC01:28
*** vkmc has joined #openstack-meeting-301:33
*** stanzgy has joined #openstack-meeting-301:43
*** shakamunyi has joined #openstack-meeting-301:54
*** Longgeek has joined #openstack-meeting-302:04
*** yamamoto_ has joined #openstack-meeting-302:05
*** salv-orlando has quit IRC02:05
*** sunrenjie6 has quit IRC02:05
*** jacalcat has joined #openstack-meeting-302:25
*** jacalcat has left #openstack-meeting-302:26
*** lhcheng has quit IRC02:31
*** armax has joined #openstack-meeting-302:39
*** lhcheng has joined #openstack-meeting-302:40
*** mfer has quit IRC03:05
*** armax has quit IRC03:10
*** armax has joined #openstack-meeting-303:12
*** otherwiseguy has joined #openstack-meeting-303:15
*** otherwiseguy has quit IRC03:21
*** otherwiseguy has joined #openstack-meeting-303:21
*** vkmc has quit IRC03:30
*** yamahata has quit IRC03:48
*** otherwiseguy has quit IRC03:51
*** otherwiseguy has joined #openstack-meeting-303:51
*** amotoki__zzz has quit IRC04:00
*** glebo has joined #openstack-meeting-304:06
*** nelsnelson has quit IRC04:06
*** armax has quit IRC04:07
*** otherwiseguy has quit IRC04:08
*** otherwiseguy has joined #openstack-meeting-304:09
*** otherwiseguy has quit IRC04:14
*** otherwiseguy has joined #openstack-meeting-304:14
*** enikanorov has joined #openstack-meeting-304:17
*** lhcheng has quit IRC04:19
*** lhcheng has joined #openstack-meeting-304:19
*** otherwiseguy has quit IRC04:20
*** otherwiseguy has joined #openstack-meeting-304:20
*** lhcheng has quit IRC04:24
*** otherwiseguy has quit IRC04:33
*** yamahata has joined #openstack-meeting-304:40
*** otherwiseguy has joined #openstack-meeting-304:43
*** jaypipes has joined #openstack-meeting-304:53
*** otherwiseguy has quit IRC04:55
*** enikanorov has quit IRC04:55
*** lhcheng has joined #openstack-meeting-305:05
*** otherwiseguy has joined #openstack-meeting-305:07
*** lhcheng has quit IRC05:08
*** lhcheng has joined #openstack-meeting-305:09
*** otherwiseguy has quit IRC05:12
*** glebo has quit IRC05:15
*** armax has joined #openstack-meeting-305:20
*** k4n0 has joined #openstack-meeting-305:29
*** glebo has joined #openstack-meeting-305:30
*** armax has quit IRC05:33
*** Longgeek has quit IRC05:35
*** HenryG has quit IRC05:36
*** armax has joined #openstack-meeting-305:53
*** tomoe has quit IRC05:53
*** tomoe has joined #openstack-meeting-305:54
*** amotoki has joined #openstack-meeting-305:56
*** coolsvap|afk is now known as coolsvap05:56
*** SumitNaiksatam has quit IRC06:00
*** SumitNaiksatam has joined #openstack-meeting-306:02
*** Longgeek has joined #openstack-meeting-306:03
*** armax has quit IRC06:03
*** mrunge has joined #openstack-meeting-306:08
*** lhcheng has quit IRC06:29
*** lhcheng has joined #openstack-meeting-306:45
*** shakamunyi has quit IRC06:46
*** shakamunyi has joined #openstack-meeting-306:49
*** matrohon has joined #openstack-meeting-306:55
*** shakamunyi has quit IRC06:56
*** jtomasek has joined #openstack-meeting-307:03
*** jamiehannaford has joined #openstack-meeting-307:15
*** jcoufal has joined #openstack-meeting-307:16
*** flaper87|afk is now known as flaper8707:16
*** lhcheng has quit IRC07:20
*** HenryG has joined #openstack-meeting-307:20
*** lhcheng has joined #openstack-meeting-307:21
*** zz_ttrifonov is now known as ttrifonov07:23
*** lhcheng has quit IRC07:26
*** flaper87 is now known as flaper87|afk07:41
*** MaxV has joined #openstack-meeting-308:17
*** salv-orlando has joined #openstack-meeting-308:23
*** safchain has joined #openstack-meeting-308:28
*** yamahata has quit IRC08:36
*** igordcard has joined #openstack-meeting-308:42
*** glebo has quit IRC08:45
*** zz_johnthetubagu is now known as johnthetubaguy09:04
*** yamamoto_ has quit IRC09:05
*** armax has joined #openstack-meeting-309:17
*** yamamoto_ has joined #openstack-meeting-310:25
*** armax has quit IRC10:29
*** yamahata has joined #openstack-meeting-310:36
*** flaper87|afk is now known as flaper8710:46
*** salv-orlando has quit IRC10:48
*** yamamoto_ has quit IRC10:51
*** stanzgy has quit IRC10:53
*** armax has joined #openstack-meeting-311:03
*** flaper87 is now known as flaper87|afk11:04
*** armax has quit IRC11:13
*** armax has joined #openstack-meeting-311:18
*** armax has quit IRC11:25
*** MaxV has quit IRC11:27
*** MaxV has joined #openstack-meeting-311:28
*** MaxV has quit IRC11:32
*** MaxV has joined #openstack-meeting-311:43
*** julim has quit IRC11:46
*** armax has joined #openstack-meeting-311:56
*** armax has quit IRC11:58
*** armax has joined #openstack-meeting-312:09
*** matrohon has quit IRC12:10
*** sankarshan_away is now known as sankarshan12:16
*** tomoe_ has joined #openstack-meeting-312:17
*** tomoe_ has quit IRC12:17
*** tomoe has quit IRC12:17
*** tomoe has joined #openstack-meeting-312:17
*** vkmc has joined #openstack-meeting-312:21
*** vkmc has quit IRC12:21
*** vkmc has joined #openstack-meeting-312:21
*** tomoe_ has joined #openstack-meeting-312:33
*** tomoe has quit IRC12:36
*** armax has quit IRC12:51
*** armax has joined #openstack-meeting-312:53
*** armax has quit IRC12:59
*** armax has joined #openstack-meeting-313:00
*** armax has quit IRC13:04
*** armax has joined #openstack-meeting-313:11
*** armax has quit IRC13:11
*** armax has joined #openstack-meeting-313:12
*** armax has quit IRC13:12
*** zz_jgrimm is now known as jgrimm13:13
*** gholler has joined #openstack-meeting-313:18
*** julim has joined #openstack-meeting-313:21
*** peristeri has joined #openstack-meeting-313:28
*** jacalcat has joined #openstack-meeting-313:31
*** mfer has joined #openstack-meeting-313:39
*** ozamiatin_ has quit IRC13:46
*** tomoe_ has quit IRC13:46
*** tomoe has joined #openstack-meeting-313:46
*** armax has joined #openstack-meeting-313:48
*** matrohon has joined #openstack-meeting-313:48
*** tomoe has quit IRC13:51
*** tomoe has joined #openstack-meeting-313:52
*** sigmavirus24_awa is now known as sigmavirus2413:56
*** thangp has joined #openstack-meeting-314:05
*** ryu25 has joined #openstack-meeting-314:09
*** nelsnelson has joined #openstack-meeting-314:11
*** amotoki_ has joined #openstack-meeting-314:14
*** david-lyle has joined #openstack-meeting-314:16
*** otherwiseguy has joined #openstack-meeting-314:23
*** marun has joined #openstack-meeting-314:27
*** jacalcat has left #openstack-meeting-314:33
*** coolsvap is now known as coolsvap|afk14:36
*** jacalcat1 has joined #openstack-meeting-314:37
*** k4n0 has quit IRC14:40
*** tomoe has quit IRC14:55
*** tomoe has joined #openstack-meeting-314:56
*** carl_baldwin has joined #openstack-meeting-314:58
carl_baldwinhi15:00
*** mrsmith has joined #openstack-meeting-315:00
*** pc_m has joined #openstack-meeting-315:00
*** tomoe has quit IRC15:00
carl_baldwinmrsmith: pc_m: hi15:01
*** Rajeev has joined #openstack-meeting-315:01
pc_mcarl_baldwin: hi. Only able to be on for 30 min :(15:01
ChuckCo/15:01
*** devvesa has joined #openstack-meeting-315:01
carl_baldwinpc_m: my time is limited today too.15:01
devvesahi15:01
carl_baldwinChuckC: hi15:01
carl_baldwindevvesa: hi15:01
*** seizadi has joined #openstack-meeting-315:01
carl_baldwinseizadi: it has been a while15:02
Rajeevcarl_baldwin: Hi15:02
carl_baldwin#startmeeting neutron_l315:02
openstackMeeting started Thu Oct 16 15:02:31 2014 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
seizadiHi15:02
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:02
openstackThe meeting name has been set to 'neutron_l3'15:02
carl_baldwinRajeev: hi15:02
carl_baldwin#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:02
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:03
carl_baldwinI don’t think I have any announcements.  Anyone else?15:03
*** MaxV has quit IRC15:03
carl_baldwin#topic l3-high-availability15:04
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:04
carl_baldwinsafchain: hi.  Anything new?15:04
carl_baldwin#undo15:05
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x3188550>15:05
carl_baldwinActually, I thought of an announcement.  It just hit me that Juno final should be today.15:05
carl_baldwin#topic bgp-dynamic-routing15:05
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:05
carl_baldwindevvesa: hi15:05
devvesahi15:06
carl_baldwinI think we’re almost there with the blueprint.15:07
carl_baldwinThe question remaining is whether the dr agent is associated with a network or a router.  I’m still thinking about it.15:08
devvesame too. I understand you point, it can become annoying to add all the routers15:09
matrohonme too :) an alternative could be to associate it to a l3 agent?15:09
devvesabut... it can be the use case where you don't want to advertise all?15:09
carl_baldwinI can see advantages and disadvantages to both strategies.  I’m wondering if we need to hear some more opinions.15:09
devvesamatrohon: the alternative is associate the router to the dr_agent15:09
devvesaso: a network with all his routers or a single router one by one?15:10
carl_baldwinmatrohon: I’m not sure an l3 agent fits.  they can be associated with many routers.  There can be many l3 agents associated with an external network.  In some cases, there can be more than one external network associated to an l3 agent.15:11
*** tomoe has joined #openstack-meeting-315:11
ryu25i see attaching to a router as more intuitive to the users, but providing a way to do 'bulk attach' by specifying external network sounds useful.  Perhaps allow both?15:11
carl_baldwinryu25: I was just going to suggest maybe both too.  We could start with routers initially maybe.15:11
carl_baldwinThat complicates the db model a little bit…  It is something to think about.15:12
carl_baldwinWould we model that with two types of associations (two tables) or one table that can handle different types of association?15:13
carl_baldwindevvesa: ^15:13
devvesayes, why not?15:14
devvesaanother think to talk about is if we forget the discovery or not15:14
*** haleyb has joined #openstack-meeting-315:14
devvesaI removed any discover reference in the spec, but you seemed concerned about it15:14
carl_baldwinhaleyb: hi15:14
ryu25right...  the db model also feels more natural if the router and dynamic routing are directly attached.  If the only reason for going with external network is to provide a way to associate it with multiple routers, then it sounds like it should be a thought of as an API level enhancement15:14
haleybcarl_baldwin: hi15:14
*** rcleere is now known as rcleere_away15:15
carl_baldwindevvesa: Are you thinking of putting that off to another blueprint?  How important is the discover to your use case?15:15
devvesait is not important, we just need to advertise a full range15:15
devvesalet's avoid the discovery but trying to do things in a way that won't be difficult to add it in a future15:16
ryu25agreed that advertisement is more useful than discovery15:16
devvesawhat do you think?15:16
carl_baldwinThen I think leaving it out of this blueprint is fine.  I’d like to leave the door open to addressing it later.15:16
devvesaok15:17
carl_baldwinIt does make sense to address advertisement first and discovery later if there is demand for it.15:17
carl_baldwinSo, have we decided to implement an associated with a router now and follow-on later with an association to a network?  I’m happy with that.15:18
devvesaI'm happy too15:18
carl_baldwinI’m think I’m leaning toward adding a property to the association to indicate if it is a router or a network.  What do you think?15:19
ryu25sounds good to me.  In the future, tenants will want to add BGP to their own routers to advertise routes over VPN too15:19
carl_baldwinryu25: Yes, I think so.  I still see an admin involved in that.15:20
carl_baldwindevvesa: okay.  Anything else?  I hope we can get this blueprint in soon.15:21
devvesaOk, I'll take that into account in the next spec review15:21
carl_baldwindevvesa: great.  Thanks for your work and patience.15:21
devvesame too! thanks carl!15:21
carl_baldwinthanks ryu25 and matrohon for your input too.15:21
carl_baldwin#topic L3 Agent Refactoring15:22
*** openstack changes topic to "L3 Agent Refactoring (Meeting topic: neutron_l3)"15:22
ryu25carl_baldwin:  anytime!15:22
*** Swami has joined #openstack-meeting-315:22
devvesaplease matrohon, review the spec, we want to do something useful for VPN guys15:22
*** pc_m has quit IRC15:22
carl_baldwindevvesa: matrohon: +115:22
matrohondevvesa : I'll send a potential design for IPVPN attachment15:23
devvesalooking forward to see it15:23
matrohonyou can have a first look here :  https://docs.google.com/drawings/d/1NN4tDgnZlBRr8ZUf5-6zzUcnDOUkWSnSiPm8LuuAkoQ/edit15:23
carl_baldwinI have to apologize that I have not posted the spec for the refactoring of the L3 agent.  I wrote it as promised but I need a sign off from our legal team to post it.  I’m still trying to get that.15:23
yamahatahi, I have uploaded WIP patch for l3 agent.15:24
yamahatahttps://review.openstack.org/#/c/128846/15:24
yamahataThat's quite incompleted, but enough to show the idea/direction15:25
SwamiWill this be part of the L3 agent refactoring effort or will this be a separate patch15:25
carl_baldwinyamahata: do you have a blueprint?  This is a pretty big change and looks like it has a big chance of conflicting with other efforts.15:25
yamahataI expect it will be a part of l3 agent refactoring.15:25
matrohonyamahata : this leads to modula l3 agent?15:26
Swamiyamahata: then you may need to add in your idea to the same blueprint that carl was mentioning15:26
yamahatacarl_baldwin: no blueprint.15:26
yamahatacarl_baldwin: so I'd like to discuss before going further.15:27
matrohonis modular l3 agent the overall direction? (sorry for the newby question:)15:27
carl_baldwinyamahata: I see value in this.  Could you hold off on it for just a bit while we try to bring our efforts together?15:27
yamahatacarl_baldwin: Sure.15:27
carl_baldwinmatrohon: We would like to get closer to a modular agent.  But that is a bit longer term.15:27
matrohoncarl_baldwin : thanks15:28
carl_baldwinyamahata: I like the enthusiasm.  I don’t want to squash it.  I will have a look at what you have proposed and try to work it in to the overall effort.15:28
carl_baldwinmatrohon: We won’t get there in one step.  However, the L3 should get more modular as the work progresses.15:29
yamahatacarl_baldwin: so far I heard just refactor of l3 agent. Can you please elaborate what kind of refactoring?15:29
yamahataMy motivation is routervm.15:29
*** armax has quit IRC15:29
matrohoncarl_baldwin : fine : will try to help since I think i'll need it for BGPVPN15:30
carl_baldwinyamahata: I was hoping to have the blueprint up to answer these questions.  Sigh.  Let me try to give you the gist of it.15:30
yamahataSo I'd like to split out device specific logic and the logic of polling/syncing15:30
carl_baldwinI’d like to start by adding an encapsulation for a router to remove all of the router stuff from l3_agent.py.  This will leave the agent class to handle RPC updates and queuing them to workers.15:31
carl_baldwinThis sounds similar to your goal.15:31
yamahatacarl_baldwin: yes, sound similar.15:31
carl_baldwinAnother early step will be to encapsulate a namespace and create a manager that will handle the clean up of stale ones.15:32
SwamiI like the idea. +115:33
carl_baldwinThen, I’d like to encapsulate plugging ports, especially the external gateway port since there is so much logic around that for DVR vs legacy routers.  All of the floating ip namespace handling would go under this encapsulation.15:33
mrsmithgreat ideas carl_baldwin15:33
carl_baldwinI’m thinking of maybe a driver model to handle the differences between  DVR and legacy connection to the external network.15:34
carl_baldwinI think with those initial steps, the L3 agent will be significantly less tangled up in itself than it is now.15:35
carl_baldwinIt should enable further work to clean it up even more.15:35
carl_baldwinI’ll try to get the sign-off to post the blueprint and will add you all as reviewers.15:36
*** rcleere_away is now known as rcleere15:36
carl_baldwin#topic neutron-ovs-dvr15:37
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:37
Swamicarl_baldwin: hi15:37
carl_baldwinSwami: mrsmith: Rajeev: anything since yesterday?15:37
SwamiWe got another bug filed regarding the floating IP status update15:37
carl_baldwinSwami: I did not get a chance yesterday to look at the locking issues much.  I have that on my plan for today.15:37
SwamiWe are looking into it right now.15:37
carl_baldwinSwami: Ah yes, the new tempest test was added for that.15:38
Swami#link https://bugs.launchpad.net/neutron/+bug/138161715:38
*** shakamunyi has joined #openstack-meeting-315:38
SwamiIt seems to be like a timing issue, but we are looking into it to confirm.15:38
SwamiWe had some headway on the lockwait issue.15:38
carl_baldwinSwami: headway since yesterday?15:39
carl_baldwinWhat have you found?15:39
SwamiOn the lockwait it seems that a port is deleted by "gateway_clear".15:39
SwamiThe router_interface_delete is trying to delete the same port.15:39
SwamiWhen it goes to the delete_port, it calls "db.get_locked_port_and_binding".15:40
SwamiIn a  normal scenario, this function returns the port that was deleted and then it logs a message and quits.15:40
SwamiBut in this case this function does not return.15:41
Swamithe query to find out the ports that are locked fails.15:41
RajeevOn another note: Saw the re-occurrence of the race condition in l_3 processing floating ips.15:42
Rajeevfiled defect 138123815:43
Rajeev#link https://bugs.launchpad.net/neutron/+bug/138123815:43
carl_baldwinSwami: So, let me see if I have this right...15:43
SwamiThis is query that fails: port = (session.query(models_v2.Port). enable_eagerloads(False). filter_by(id=port_id). with_lockmode('update'). one())15:43
carl_baldwindelete_port tries to get_locked_port_and_binding and it cannot because gateway_clear has already obtained the lock to delete the port?15:44
carl_baldwinRajeev: Thanks for the link.15:44
SwamiYes in this case the gateway_clear has already deleted the port, it is not clear after deleting the port if it had released the lock or not.15:44
SwamiThe log message shows that the port has already been deleted.15:45
SwamiI have updated the launchpad bug with the neutron-server log and I have mentioned the port-id that was causing this problem. Take a look at it.15:45
carl_baldwinSwami: okay.  I couldn’t yesterday but will probably have some time today.15:46
Swamicarl_baldwin: thanks15:46
*** pc_m has joined #openstack-meeting-315:46
*** pc_m has left #openstack-meeting-315:46
carl_baldwinSwami: thank you15:46
* carl_baldwin goes to look at bug 138123815:47
carl_baldwinRajeev: How is this bug going?15:48
Rajeevcarl_baldwin: have a review up with possible fix15:49
Rajeev#link https://review.openstack.org/#/c/128131/15:49
carl_baldwinRajeev: Could you link the review to the bug?  Somehow it did not get linked.15:50
Rajeevsure, didn't realize that.15:50
carl_baldwin^ It did not get linked because the first PS didn’t mention the bug in the commit msg.  I’ve had that happen.15:50
carl_baldwinSwami: mrsmith: Rajeev:  Anything else?15:51
RajeevI see, how do I link it now ?15:51
Swamicarl_baldwin: I don't think I have anything more to add. We are still focussed on bugs and backlog items.15:51
carl_baldwinSwami: Thanks.15:51
RajeevOn bug #138161715:52
carl_baldwinRajeev, just paste a link in a comment.15:52
Rajeevfrom the logs it appears the test is checking the status of the floating ips too quick.15:53
RajeevIt would be a timing issue with the test as Swami mentioned earlier.15:53
mrsmithdvr takes a little longer to setup FIPs since we have extra ns, port, etc15:53
Rajeev#link https://bugs.launchpad.net/neutron/+bug/138161715:54
Rajeevmrsmith: yes15:54
*** david-lyle has quit IRC15:54
Rajeevno more updates from me except , take a look at review https://review.openstack.org/#/c/128131/15:55
carl_baldwinThanks all.  We’re about out of time.15:57
carl_baldwinKeep up the good work.15:57
carl_baldwin#endmeeting15:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:57
openstackMeeting ended Thu Oct 16 15:57:43 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-10-16-15.02.html15:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-10-16-15.02.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-10-16-15.02.log.html15:57
*** mrsmith has quit IRC15:57
*** jacalcat1 has left #openstack-meeting-315:59
*** seizadi has quit IRC16:00
*** armax has joined #openstack-meeting-316:01
*** lhcheng has joined #openstack-meeting-316:10
*** Longgeek has quit IRC16:12
*** tomoe has quit IRC16:13
*** openstackstatus has joined #openstack-meeting-316:14
*** ChanServ sets mode: +v openstackstatus16:14
*** tomoe has joined #openstack-meeting-316:14
*** devvesa has quit IRC16:17
*** tomoe has quit IRC16:19
-openstackstatus- NOTICE: An error in a configuration change to mitigate the poodle vulnerability caused a brief outage of git.openstack.org from 16:06-16:12. The problem has been corrected and git.openstack.org is working again.16:19
*** david-lyle has joined #openstack-meeting-316:21
*** sarob has joined #openstack-meeting-316:23
*** jcoufal has quit IRC16:26
*** sarob has quit IRC16:28
*** lsmola has quit IRC16:29
*** shakamunyi has quit IRC16:30
*** ryu25 has quit IRC16:31
*** dmahony has quit IRC16:39
*** lsmola has joined #openstack-meeting-316:44
*** armax has left #openstack-meeting-316:50
*** yamahata has quit IRC16:52
*** matrohon has quit IRC16:53
*** otherwiseguy has quit IRC16:55
*** rcleere is now known as rcleere_away16:55
*** coolsvap|afk is now known as coolsvap16:55
*** s3wong has joined #openstack-meeting-316:58
*** rcleere_away is now known as rcleere16:59
*** rcleere is now known as rcleere_away17:00
*** rcleere_away is now known as rcleere17:00
*** Rajeev has quit IRC17:02
*** seizadi has joined #openstack-meeting-317:06
*** yamahata has joined #openstack-meeting-317:08
*** rcleere is now known as rcleere_away17:10
*** rcleere_away is now known as rcleere17:14
*** rcleere is now known as rcleere_away17:14
*** rcleere_away is now known as rcleere17:15
*** johnthetubaguy is now known as zz_johnthetubagu17:17
*** dboik has joined #openstack-meeting-317:18
*** rudrarugge has joined #openstack-meeting-317:24
*** SumitNaiksatam has quit IRC17:27
*** yamahata has quit IRC17:27
*** safchain has quit IRC17:31
*** rcleere is now known as rcleere_away17:31
*** gholler has quit IRC17:42
*** gholler has joined #openstack-meeting-317:42
*** ivar-lazzaro has joined #openstack-meeting-317:43
*** ivar-lazzaro has quit IRC17:43
*** ivar-lazzaro has joined #openstack-meeting-317:44
*** rms_13 has joined #openstack-meeting-317:47
*** SumitNaiksatam has joined #openstack-meeting-317:48
*** wuhg has quit IRC17:53
*** rkukura has joined #openstack-meeting-317:58
*** nbouthors has joined #openstack-meeting-317:59
SumitNaiksatamhi18:00
nbouthorshi18:00
rkukurahi18:00
*** glebo has joined #openstack-meeting-318:00
s3wonghello18:01
SumitNaiksatamrkukura: s3wong ivar-lazzaro18:01
ivar-lazzarohi!18:01
SumitNaiksatamrudrarugge: good to see you! :-)18:01
rkukurahi again18:01
*** haleyb has quit IRC18:01
SumitNaiksatamokay lets get started18:01
rudraruggeSumitNaiksatam: :)18:01
SumitNaiksatam#startmeeting networking_policy18:01
*** hemanthravi has joined #openstack-meeting-318:01
openstackMeeting started Thu Oct 16 18:01:32 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
*** glebo has quit IRC18:01
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy18:01
s3wongglebo is gone...18:01
*** LouisF has joined #openstack-meeting-318:02
SumitNaiksatamany big announcements or info that anyone would like to share upfront?18:02
SumitNaiksatams3wong: he will back soon :-)18:02
SumitNaiksatamone piece of information i wanted to share was the GBP design summit session18:02
SumitNaiksatam#link http://kilodesignsummit.sched.org/event/98dc4255384e340682137c8a7ee7e60d#.VD_6XIt4r4w18:02
SumitNaiksatamthis is a separate session in the “other projects” track (in the design summit)18:03
SumitNaiksatami am of course talking in the context of the upcoming Paris summit (should have mentioned that before) ;-)18:03
s3wongcool18:03
SumitNaiksatams3wong: yeah :-)18:03
s3wongSumitNaiksatam: do we know if we are getting Neutron design summit slots?18:04
*** seizadi has quit IRC18:04
SumitNaiksatams3wong: not sure18:04
*** thangp has quit IRC18:04
SumitNaiksatams3wong: we will leave that to community to decide the neutron priority18:04
SumitNaiksatamokay we can discuss the details of the session in a separate agenda topic18:04
s3wongSumitNaiksatam: sure18:04
SumitNaiksatamany other info/announcements?18:05
*** marun has quit IRC18:05
SumitNaiksatam#topic Specs in review18:05
*** openstack changes topic to "Specs in review (Meeting topic: networking_policy)"18:05
SumitNaiksatam#link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy-specs+branch:master,n,z18:05
SumitNaiksatamsome of the ones mentioned above already have implementation patches posted against them18:06
SumitNaiksatamwe are little behind on the reviews18:06
rkukuraSumitNaiksatam: I should be able to make some progress on these today.18:06
rms_13It took time for jenkins to be happy... Glad he is smiling now :)18:07
SumitNaiksatamrkukura: thanks18:07
*** marun has joined #openstack-meeting-318:07
rkukuraSumitNaiksatam: Sorry, I actually meant the code reviews, but I need to review the specs as well.18:07
SumitNaiksatamrms_13: yes, but we are currently discussing the specs, implementation patches are next :-)18:07
SumitNaiksatamrkukura: yeah, this is the specs review18:07
SumitNaiksatamLouisF: good to see your specs, thanks for posting promptly!18:08
hemanthravineed review of the gbp chaining spec https://review.openstack.org/#/c/125876/18:08
SumitNaiksatamhemanthravi: sorry i am behind on that18:08
hemanthraviSumitNaiksatam, when you get some time18:08
SumitNaiksatami see that only kevinbenton has reviewed18:09
SumitNaiksatamthe ones that were assigned to him18:09
SumitNaiksatamivar-lazzaro: rkukura do you have issues with kevinbenton’s comments?18:09
LouisFSumitNaiksatam: thanks18:09
*** dboik_ has joined #openstack-meeting-318:10
SumitNaiksatamLouisF: you want to update the commite message title to reflect the name of the spec18:10
ivar-lazzaroSumitNaiksatam: nope, I'm going to push the new version of the patch in seconds :)18:10
SumitNaiksatamivar-lazzaro: sweet18:10
LouisFSumitNaiksatam: i will be updating them18:10
rkukuraSumitNaiksatam: I think I clarified kevinbenton’s concern about L2P, and am updaing the extension driver spec.18:10
SumitNaiksatamLouisF: great, thanks18:10
SumitNaiksatamrkukura: ok great18:10
*** glebo has joined #openstack-meeting-318:10
SumitNaiksatamrkukura: sorry i was not following the discussion thread18:11
SumitNaiksatamglebo: welcome back!18:11
*** glebo is now known as Guest9635018:11
Guest96350*sorry he's late, irc client connectivity issues, dkw*18:11
Guest96350#nick glebo18:12
SumitNaiksatamcan i also plug a request to review the spec update that i put: #link https://review.openstack.org/12791318:12
SumitNaiksatami am happy to spend a few minutes here if someone wants to dig deeper on the specs that are in review currently18:12
SumitNaiksatamon -> into18:13
SumitNaiksatamif not we will move to the implementation patches18:13
*** dboik has quit IRC18:13
SumitNaiksatamok moving on18:14
SumitNaiksatam#topic Implementation patches in review18:14
*** openstack changes topic to "Implementation patches in review (Meeting topic: networking_policy)"18:14
SumitNaiksatamwait18:14
SumitNaiksatam#undo18:14
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x3399490>18:14
*** otherwiseguy has joined #openstack-meeting-318:14
SumitNaiksatam#topic Current DB approach: SSDC18:14
*** openstack changes topic to "Current DB approach: SSDC (Meeting topic: networking_policy)"18:14
SumitNaiksatamwant to bring this to everyone’s notice since this patch was already approved18:15
*** salv-orlando has joined #openstack-meeting-318:15
s3wongSumitNaiksatam: so no problem with the release folks?18:15
SumitNaiksatamper discussion in the last meeting (and on friday in the review meeting), ivar-lazzaro posted a new patch for the single schema different series approach (SSDS)18:16
SumitNaiksatams3wong: i am not sure18:16
SumitNaiksatamivar-lazzaro: rkukura: s3wong’s question ^^^18:16
ivar-lazzaros3wong: we don't know yet, but we needed this to be in place to fix dependency issues18:16
rkukuraivar-lazzaro: +118:16
SumitNaiksatamyes, installation was broken without a fix18:17
SumitNaiksatamso in the interest of expediency, i approved this patch18:17
ivar-lazzaros3wong: we can always go back to the DSDC approach if the problem arises18:17
*** emagana has joined #openstack-meeting-318:17
SumitNaiksatami believe at least rkukura approves of this18:17
SumitNaiksatamplease let us know if there are concerns18:17
s3wongivar-lazzaro: sure18:17
ivar-lazzaroBut in general I would suggest to start investigating the issue with the packagers before it's too late :)18:17
SumitNaiksatami have tested that devstack install now works with the fix in place18:17
SumitNaiksatamivar-lazzaro: can you quickly summarize for the benefit of everyone what the current approach is?18:18
ivar-lazzaroSumitNaiksatam: sure18:18
SumitNaiksatamivar-lazzaro: sorry to put you on the spot18:18
ivar-lazzaroThe current approach is to use a different "version table" in the same database/schema Neutron is using18:19
*** jamiehannaford has quit IRC18:19
ivar-lazzaroso we are basically still tied to the Neutron's database, but we run a completely different migration chain18:19
SumitNaiksatamivar-lazzaro: good summary18:19
ivar-lazzarowhich means that Neutron can upgrade just fine as long as table names are unique18:20
ivar-lazzaro(same goes for gbp ofc)18:20
SumitNaiksatamivar-lazzaro: and thanks so much for working on this so expeditiously, it was a blocking issue18:20
SumitNaiksatamokay any more questions on the current approach?18:20
SumitNaiksatamso for anyone posting a new migration, nothing changes18:20
ivar-lazzaroNope18:21
SumitNaiksatamjust change the HEAD in the gbp repo, and point to the right down migration18:21
ivar-lazzarothis approach is much cleaner than DSDC18:21
SumitNaiksatamivar-lazzaro: did I summarize it correctly?18:21
ivar-lazzarobut less safe packaging wise18:21
ivar-lazzaroSumitNaiksatam: that's perfect :)18:21
rkukuraWhy less safe?18:21
SumitNaiksatamcertainly simpler!18:22
ivar-lazzarorkukura: because we don't know if using the same database is acceptable overall18:22
*** carl_baldwin has quit IRC18:22
ivar-lazzarorkukura: once we know that for sure I'll be happier :-)18:22
rkukuraI think that is more of an architectural issue than a packaging issue18:22
rkukuraBut we can ask around18:22
SumitNaiksatamrkukura: sure18:22
SumitNaiksatamok moving on18:22
rkukuraFor Juno, this is a service plugin within neutron-server, after all18:23
SumitNaiksatamivar-lazzaro: thanks again!18:23
SumitNaiksatamrkukura: agreed!18:23
ivar-lazzaroSumitNaiksatam: np! :-)18:23
SumitNaiksatam#topic Implementation patches in review18:23
*** openstack changes topic to "Implementation patches in review (Meeting topic: networking_policy)"18:23
SumitNaiksatamso we had a long review meeting (i believe it was Oct 14th)18:23
Guest96350nick/ glebo_18:23
SumitNaiksatamthis was an IRC meeting, you can find the logs here: #link https://wiki.openstack.org/w/images/7/7f/Gbp-patch-reviews-10142014.pdf18:23
SumitNaiksatamwe got out of the meeting with some AI and review owners18:24
SumitNaiksatamthis has been captured here: #link https://docs.google.com/spreadsheets/d/1VAcYODD5fA_t2yleb95pTlIxD-btnUllZTN-uhNrsh4/edit#gid=018:24
*** mestery has quit IRC18:24
*** mestery has joined #openstack-meeting-318:25
Guest96350lo mestery18:25
SumitNaiksatamso we are still a bit behind on the reviews here18:25
SumitNaiksatamwe merged GPM-RMD-1, did we?18:26
Guest96350all: having serious irc issues this morning, so Guest96350 = glebo18:26
Guest96350*hope y'all can live w/ it*18:26
SumitNaiksatamGuest96350: np18:26
SumitNaiksatamok we did18:26
SumitNaiksatamon GP-API-2, rms_13 you have a -118:27
Guest96350*will repost the mapping once in a while to help any new-comers*18:27
SumitNaiksatami believe i have addressed your comments18:27
rkukuraI just updated the gpm-rmd-1 review with links to the LP bugs I filed.18:27
rms_13Ok. Will take a look18:27
SumitNaiksatamrkukura: thanks18:27
SumitNaiksatamrms_13: i addressed them yesterday evening :-P18:28
s3wongrkukura: gpm-rmd-1 is already merged, right?18:28
SumitNaiksatams3wong: yes18:28
hemanthraviivar-lazzaro, does hierachical contracts patch need a rebase18:28
rkukuras3wong: yes, just wanted to record that the bugs were filed18:28
SumitNaiksatams3wong: i think rkukura added as record18:28
s3wongrkukura: sure18:28
hemanthraviivar-lazzaro, service-chain patches dependent on this are failing too18:28
ivar-lazzarohemanthravi: yep18:28
SumitNaiksatamhemanthravi: i believe it does, i did not rebase it yesterday when i was rebasing others18:28
SumitNaiksatamhemanthravi: okay i did not realize that18:29
ivar-lazzarohemanthravi: there are merge conflicts, will address right after the meeting18:29
SumitNaiksatami can do it later in the day if ivar-lazzaro doesnt get to it18:29
hemanthraviivar-lazzaro, thanks18:29
SumitNaiksatamfor GP-DB-218:29
SumitNaiksatamhemanthravi: and ivar-lazzaro you +2’ed18:30
SumitNaiksatamif no one has objections, can someone +A this?18:30
ivar-lazzaroSumitNaiksatam: there's still a dict/set issue (just like the contract patch) but didn't want to block it18:30
*** cathy_ has joined #openstack-meeting-318:30
SumitNaiksatamsorry to get into the weeds here with the specific patches18:30
ivar-lazzaroSumitNaiksatam: I can approve it18:31
SumitNaiksatamivar-lazzaro: ah okay, i believe you added that comment a couple of mins back :-)18:31
ivar-lazzaroSumitNaiksatam: yes :)18:31
SumitNaiksatamivar-lazzaro: but my bad, i should have checked for it when i was fixing the other stuff18:31
SumitNaiksatamivar-lazzaro: you can file a bug18:31
Guest96350reminder: Guest96350 = glebo *suffering from irc client disfunction syndrome this morning*18:31
SumitNaiksatamGuest96350: ;-)18:32
*** seizadi has joined #openstack-meeting-318:32
SumitNaiksatamGuest96350: we at least know you are not masquerading! ;-)18:32
ivar-lazzaro\ME starts doubting that Guest96350 really is glebo :-)18:32
SumitNaiksatamivar-lazzaro: i can assure you he is18:32
SumitNaiksatamGP-PLG-318:32
ivar-lazzaroSumitNaiksatam: j/k :)18:32
Guest96350SumitNaiksatam: well, reverse masquerading, aka parading18:32
SumitNaiksatamwho is the second core on this?18:33
SumitNaiksatamsorri, i meant GP-PLG-218:33
SumitNaiksatamrkukura: that would be you ;-)18:33
Guest96350ivar-lazzaro: who is glebo anyway, really?18:33
rkukurayep18:33
SumitNaiksatamhopefully you can take a quick look at it18:34
ivar-lazzaroGuest96350: maybe we all are!18:34
SumitNaiksatamGP-API-318:34
rkukuraSumitNaiksatam: Yes, I hope to make some progress on the code reviews today18:34
SumitNaiksatamrms_13: you are guilty again ;-P18:34
rms_13what did I do now?18:34
rms_13:)18:35
SumitNaiksatamrms_13: just pulling your leg18:35
SumitNaiksatamrms_13: you put the -1 saying that jenkins was not happy, except that jenkins had not voted18:35
SumitNaiksatamrms_13: but it has now and its happy :-)18:36
Guest96350ivar-lazzaro: *hears familiar tune, then lyrics, "your own... personal... glebo"18:36
SumitNaiksatamrkukura: i believe you will be looking at GP-API-3 as well18:36
rms_13May be the session was not upto date... Ya its passing so I will do +2.18:37
rkukuraSumitNaiksatam: yes18:37
SumitNaiksatamfor GP-DB-3 i believe i have addressed the comments, ivar-lazzaro and rms_13 can you take a look?18:37
ivar-lazzaroSumitNaiksatam: sure18:37
rms_13Rebase after Rebase and that after +2 ... :)18:37
rms_13Sure I will18:37
SumitNaiksatamrms_13: great, thanks!18:37
SumitNaiksatamGP-PLG-318:38
SumitNaiksatami think this is good to go, we can wait for the preceeding patches to merge and then +A this18:38
SumitNaiksatambtw, lets merge the patches in order (when we come to it) ;-)18:39
SumitNaiksatami am not sure Jenkins will allow a merge otherwise18:39
SumitNaiksatamthat brings us to GPM-RMD-SG18:39
rms_13Ya that is the reason I did not +A after Hemanth did another +2 on one of them.18:39
SumitNaiksatamso myself and rkukura are on the hook, we will get to it once the backlog clears18:39
SumitNaiksatamrms_13: sure18:40
SumitNaiksatamand we also have the hierarchical contracts patch18:40
SumitNaiksatamthats Hemanth and me18:40
SumitNaiksatami think hemanth has reviewed to some extent18:40
SumitNaiksatami havent18:40
SumitNaiksatamwill get to that18:40
SumitNaiksatamso once we are done with these foundation patches, we have a bunch of service chain patches to get to18:41
SumitNaiksatamperhaps doesnt make sense to spend time on discussing those right now18:41
SumitNaiksatambut please keep those patches in mind as well18:41
ivar-lazzaroSumitNaiksatam: there's another one18:42
ivar-lazzaroSumitNaiksatam: lost in the bunch18:42
SumitNaiksatamivar-lazzaro: ah sorry, did i miss something18:42
ivar-lazzaroSumitNaiksatam: which rkukura will certainly appreciate :)18:42
ivar-lazzaro#link https://review.openstack.org/#/c/128148/18:42
ivar-lazzarosince we are now depending from Neutron only for UTs, we can forget about pypi and directly pull from their repo18:42
SumitNaiksatamivar-lazzaro: oh my bad, yeah that is critical bug fic18:42
ivar-lazzarothe official one18:42
SumitNaiksatam*fix18:42
rkukuraivar-lazzaro: So it does work?18:43
ivar-lazzarorkukura: yeah now it does, because we don't need to pull the repo anymore when running the installation script18:43
ivar-lazzarorkukura: it's only needed for UTs which have always worked18:44
ivar-lazzarorkukura: need to point to stable/juno though18:44
SumitNaiksatamivar-lazzaro: oh sorry, i mixed up18:44
rkukuraivar-lazzaro: was just going to mention stable-juno18:44
SumitNaiksatamivar-lazzaro: i thought you were referring to the delete object chain bug18:44
ivar-lazzaroSumitNaiksatam: that's another one, I didn't have the chance to test it yet18:44
SumitNaiksatam#link https://review.openstack.org/#/c/12674018:44
SumitNaiksatamyes, we have lots of things in flight, if you are still wondering! :-)18:45
SumitNaiksatamokay, so moving on18:45
SumitNaiksatam#topic GBP Design Summit session18:45
*** openstack changes topic to "GBP Design Summit session (Meeting topic: networking_policy)"18:45
SumitNaiksatamas i mentioned earlier - #link http://kilodesignsummit.sched.org/event/98dc4255384e340682137c8a7ee7e60d#.VD_6XIt4r4w18:45
SumitNaiksatamwe need to plan for this18:46
SumitNaiksatamnot sure that we need to discuss this today18:46
SumitNaiksatamwe have time until the summit18:46
SumitNaiksatams3wong: you were mentioning something about this earlier?18:46
Guest96350SumitNaiksatam: 2 wks away now, not too much time, really18:47
SumitNaiksatamfyi, the GBP conference track session is #link https://openstacksummitnovember2014paris.sched.org/popular#.VD5YAYvF_3B18:47
SumitNaiksatamGuest96350: true18:47
SumitNaiksatamGuest96350: we just got notification that we have been allocated this slot18:47
*** terryw has joined #openstack-meeting-318:48
SumitNaiksatamGuest96350: so in the process of planning, and the rest of the team just got to know about it as well18:48
SumitNaiksatamGuest96350: but point well taken18:48
SumitNaiksatamGuest96350: in general, this will be a “design” discussion18:48
SumitNaiksatamGuest96350: i will get the etherpad started for it18:48
SumitNaiksatamGuest96350: so that we can start adding the topics that we want to discuss18:48
SumitNaiksatamand over time we can add structure18:49
SumitNaiksatamdoes that sound good to everyone? :-)18:49
rkukuraSumitNaiksatam: +118:49
SumitNaiksatammy earlier comments not specifically targeted at Guest96350 :-)18:49
s3wongSumitNaiksatam: sorry, was out for a moment18:49
* Guest96350 sees SumitNaiksatam take his 842nd action item of the mtg ;-)18:49
SumitNaiksatamGuest96350: :-)18:49
s3wongSumitNaiksatam: we should plan for the conference presentation, as it happens on the first day of the summit :-)18:50
SumitNaiksatams3wong: no worries18:50
SumitNaiksatams3wong: ah on that18:50
SumitNaiksatams3wong: i was planning to bring that up in the open discussion18:50
SumitNaiksatams3wong: i did update the slides18:50
SumitNaiksatams3wong:  at least with those from the policy summit18:50
SumitNaiksatams3wong: i will send them out18:50
s3wongSumitNaiksatam: and of course the "other project" design summit also :-)18:50
s3wongSumitNaiksatam: OK18:50
SumitNaiksatams3wong: i believe others are working on the slides as well18:50
*** otherwiseguy has quit IRC18:50
SumitNaiksatams3wong: so will send it as soon as i get that input18:51
s3wongSumitNaiksatam: others? I am not :-)18:51
SumitNaiksatams3wong: mandeep and mikeC18:51
SumitNaiksatamok thats a good way to segue to the open discussion18:51
SumitNaiksatam#topic Open Discussion18:51
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:51
Guest96350SumitNaiksatam: so those will be sent to ML?18:51
Guest96350SumitNaiksatam: slides, I meant18:52
SumitNaiksatamGuest96350: perhaps not the ML right away, they will posted on the openstack site after the presentation18:52
SumitNaiksatamGuest96350: we expect to iterate until the presentation day, so might not be worthwhile sending the draft versions to the ML in advance18:52
SumitNaiksatamGuest96350: can certainly share within the team for feedback and review18:53
Guest96350SumitNaiksatam: so, sent unicast to "interested parties for reivew"?18:53
SumitNaiksatamGuest96350: yes, absolutely18:53
SumitNaiksatamok we are in open discussion18:53
Guest96350SumitNaiksatam: cross-talk; ack18:53
SumitNaiksatamLouisF: i noticed you and cathy_ were following up on the Congress integration?18:53
SumitNaiksatamLouisF: thanks for following up on that thread18:53
SumitNaiksatamLouisF: any update you would like to give to the rest of the team18:54
SumitNaiksatamor perhaps on the blueprints you posted?18:54
SumitNaiksatamperhaps LouisF is away18:55
*** emagana has quit IRC18:55
*** emagana has joined #openstack-meeting-318:56
SumitNaiksatams3wong: you have any updates on that front?18:56
SumitNaiksatams3wong: you mentioned the operators track as well for socializing GBP?18:56
*** emagana has quit IRC18:56
*** emagana has joined #openstack-meeting-318:57
SumitNaiksatami think we lost a few people since we are getting close to lunch time here on the west coast :-)18:57
nbouthorsWe are dividing the propose BluePrint in 3 parts.18:57
ivar-lazzaroSumitNaiksatam: ahah18:57
SumitNaiksatamnbouthors: nice to know, and good to see you here :-)18:57
nbouthorshi18:58
nbouthorsI work with Louis on the BP18:59
SumitNaiksatamnbouthors: yes of course, sorry i did not realize you were in the meeting today18:59
nbouthorsAlso, it is nice to see that OVS is starting to implement L7 classification.18:59
SumitNaiksatamso the blueprint which LouisF posted is a joint work between nbouthors LouisF and cathy_18:59
SumitNaiksatamnbouthors: right?18:59
nbouthorsSumitNaiksatam: yes19:00
SumitNaiksatamnbouthors: yes, noticed your pointer earlier today regarding the OVS work19:00
SumitNaiksatamnbouthors: will follow up19:00
nbouthorsTHought it could be of interest19:00
SumitNaiksatamnbouthors: i think the team will be happy to get some pointers to docs or references if you have any19:00
SumitNaiksatamnbouthors: we can take it offline19:01
SumitNaiksatamokay we are over time19:01
nbouthorsSumitNaiksatam:  Wil do19:01
SumitNaiksatamthanks everyone19:01
SumitNaiksatamnbouthors: thanks19:01
nbouthorsBye19:01
s3wongSumitNaiksatam: sorry, again stepping out19:01
SumitNaiksatamuntil next week (we might have another review meeting if we dont make enough progress)19:01
SumitNaiksatambye all19:01
rkukurabye19:01
SumitNaiksatam#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
openstackMeeting ended Thu Oct 16 19:01:45 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-10-16-18.01.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-10-16-18.01.txt19:01
Guest96350by19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-10-16-18.01.log.html19:01
*** nbouthors has quit IRC19:01
*** hemanthravi has quit IRC19:02
*** rkukura has left #openstack-meeting-319:02
*** boris-42 has quit IRC19:02
ivar-lazzarobye!19:02
*** boris-42 has joined #openstack-meeting-319:04
*** Guest96350 is now known as glebo19:06
*** glebo is now known as Guest7967519:06
*** Guest79675 is now known as grommbit19:09
*** grommbit is now known as grombit19:10
*** grombit is now known as gregorylebo19:11
*** gregorylebo is now known as Guest8562819:11
*** Guest85628 has left #openstack-meeting-319:13
*** rudrarugge has quit IRC19:16
*** Youcef has quit IRC19:17
*** david-lyle_ has joined #openstack-meeting-319:20
*** david-lyle has quit IRC19:20
*** terryw has quit IRC19:20
*** mrunge has quit IRC19:23
*** david-lyle_ is now known as david-lyle19:27
*** mfer has quit IRC19:29
*** stanzgy has joined #openstack-meeting-319:30
*** cathy_ has quit IRC19:32
*** s3wong has quit IRC19:47
*** sarob has joined #openstack-meeting-319:48
*** seizadi has quit IRC19:57
*** seizadi has joined #openstack-meeting-320:01
*** david-lyle_ has joined #openstack-meeting-320:04
*** david-lyle has quit IRC20:06
*** seizadi has quit IRC20:16
*** dboik_ has quit IRC20:21
*** dboik has joined #openstack-meeting-320:22
*** otherwiseguy has joined #openstack-meeting-320:23
*** woodm1979 has joined #openstack-meeting-320:24
*** LouisF has quit IRC20:32
*** seizadi has joined #openstack-meeting-320:37
*** gholler has quit IRC20:40
*** emagana has quit IRC20:40
*** emagana has joined #openstack-meeting-320:41
*** emagana has quit IRC20:41
*** emagana has joined #openstack-meeting-320:41
*** ChuckC has quit IRC20:42
*** david-lyle_ is now known as david-lyle20:48
*** cbader has joined #openstack-meeting-321:00
*** seizadi has quit IRC21:06
*** seizadi has joined #openstack-meeting-321:06
*** ChuckC has joined #openstack-meeting-321:13
*** emagana has quit IRC21:28
*** emagana has joined #openstack-meeting-321:28
*** emagana has quit IRC21:33
*** emagana has joined #openstack-meeting-321:33
*** gholler has joined #openstack-meeting-321:35
*** MaxV has joined #openstack-meeting-321:36
*** MaxV has quit IRC21:41
*** alexpilotti has joined #openstack-meeting-321:41
*** MaxV has joined #openstack-meeting-321:45
*** julim has quit IRC21:47
*** MaxV_ has joined #openstack-meeting-321:48
*** david-lyle has quit IRC21:49
*** MaxV has quit IRC21:49
*** igordcard has quit IRC21:52
*** tomoe has joined #openstack-meeting-321:53
*** dboik has quit IRC21:57
*** MaxV has joined #openstack-meeting-321:59
*** MaxV_ has quit IRC22:02
*** david-lyle has joined #openstack-meeting-322:05
*** stanzgy has quit IRC22:15
*** mestery_ has joined #openstack-meeting-322:21
*** mestery has quit IRC22:23
*** david-lyle has quit IRC22:24
*** woodm1979 has left #openstack-meeting-322:24
*** otherwiseguy has quit IRC22:24
*** edhall_ has quit IRC22:24
*** tomoe has quit IRC22:26
*** otherwiseguy has joined #openstack-meeting-322:26
*** peristeri has quit IRC22:27
*** sigmavirus24 is now known as sigmavirus24_awa22:28
*** MaxV has quit IRC22:28
*** edhall_ has joined #openstack-meeting-322:29
*** sigmavirus24_awa is now known as sigmavirus2422:37
*** reed has joined #openstack-meeting-322:50
*** emagana has quit IRC22:57
*** HenryG_ has joined #openstack-meeting-323:01
*** HenryG_ has left #openstack-meeting-323:01
*** HenryG_ has joined #openstack-meeting-323:02
*** yamahata has joined #openstack-meeting-323:10
*** stanzgy has joined #openstack-meeting-323:12
*** cbader has quit IRC23:15
*** seizadi has quit IRC23:15
*** tomoe has joined #openstack-meeting-323:19
*** marun has quit IRC23:26
*** marun has joined #openstack-meeting-323:36
*** edhall_ has quit IRC23:47
*** tomoe has quit IRC23:51
*** tomoe has joined #openstack-meeting-323:52
*** otherwiseguy has quit IRC23:52
*** sigmavirus24 is now known as sigmavirus24_awa23:52
*** yamahata has quit IRC23:53
*** edhall_ has joined #openstack-meeting-323:54

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