Thursday, 2014-06-12

*** julim has quit IRC00:05
*** seizadi has quit IRC00:08
*** nedbat has joined #openstack-meeting-300:08
*** yamahata has joined #openstack-meeting-300:33
*** cjellick has quit IRC00:34
*** cjellick has joined #openstack-meeting-300:35
*** cjellick_ has joined #openstack-meeting-300:36
*** cjellick has quit IRC00:37
*** mfer has joined #openstack-meeting-300:52
*** seizadi has joined #openstack-meeting-300:59
*** pballand has quit IRC01:20
*** sarob has quit IRC01:25
*** sarob has joined #openstack-meeting-301:26
*** igordcard has quit IRC01:28
*** nati_ueno has quit IRC01:30
*** sarob_ has joined #openstack-meeting-301:30
*** sarob has quit IRC01:30
*** nlahouti has joined #openstack-meeting-301:34
*** seizadi has quit IRC01:37
*** nlahouti has quit IRC01:39
*** badveli has quit IRC01:44
*** cjellick_ has quit IRC01:55
*** cjellick has joined #openstack-meeting-301:56
*** thomasem has joined #openstack-meeting-301:59
*** thomasem has quit IRC01:59
*** cjellick has quit IRC02:00
*** sarob_ has quit IRC02:02
*** sarob has joined #openstack-meeting-302:03
*** sarob has quit IRC02:07
*** sarob has joined #openstack-meeting-302:25
*** markmcclain has quit IRC02:31
*** eghobo has quit IRC02:36
*** mfer has quit IRC02:40
*** nedbat has quit IRC02:49
*** sarob has quit IRC02:57
*** sarob has joined #openstack-meeting-303:02
*** coolsvap|afk is now known as coolsvap03:04
*** sankarshan_away is now known as sankarshan03:18
*** nlahouti has joined #openstack-meeting-303:21
*** nlahouti has quit IRC03:23
*** nlahouti has joined #openstack-meeting-303:23
*** sarob has quit IRC03:26
*** sarob has joined #openstack-meeting-303:26
*** tomoe_ has joined #openstack-meeting-303:26
*** sarob has quit IRC03:30
*** eghobo has joined #openstack-meeting-303:47
*** samchoi has quit IRC03:59
*** coolsvap is now known as coolsvap|afk04:01
*** seizadi has joined #openstack-meeting-304:07
*** seizadi has quit IRC04:17
*** banix has quit IRC04:24
*** sarob has joined #openstack-meeting-304:27
*** sarob has quit IRC04:31
*** SumitNaiksatam has quit IRC04:35
*** SumitNaiksatam has joined #openstack-meeting-304:36
*** sarob has joined #openstack-meeting-304:39
*** sarob has quit IRC04:43
*** markmcclain has joined #openstack-meeting-304:50
*** lcheng has joined #openstack-meeting-304:57
*** seizadi has joined #openstack-meeting-305:01
*** coolsvap|afk is now known as coolsvap05:02
*** eghobo has quit IRC05:08
*** eghobo has joined #openstack-meeting-305:09
*** lcheng has quit IRC05:11
*** nelsnelson has quit IRC05:16
*** nlahouti_ has joined #openstack-meeting-305:25
*** nlahouti_ has quit IRC05:25
*** nlahouti_ has joined #openstack-meeting-305:26
*** nlahouti has quit IRC05:26
*** nelsnelson has joined #openstack-meeting-305:36
*** sarob has joined #openstack-meeting-305:39
*** seizadi has quit IRC05:41
*** sarob has quit IRC05:43
*** lsmola has joined #openstack-meeting-305:53
*** enikanorov has joined #openstack-meeting-305:58
*** markmcclain has quit IRC06:15
*** markmcclain has joined #openstack-meeting-306:18
*** lcheng has joined #openstack-meeting-306:34
*** sarob has joined #openstack-meeting-306:39
*** sarob_ has joined #openstack-meeting-306:41
*** sarob has quit IRC06:43
*** sarob_ has quit IRC06:45
*** jamiehannaford has joined #openstack-meeting-306:46
*** jtomasek has joined #openstack-meeting-306:51
*** sarob has joined #openstack-meeting-306:53
*** sarob has quit IRC06:57
*** nlahouti_ has quit IRC07:05
*** safchain has joined #openstack-meeting-307:08
*** eguz has joined #openstack-meeting-307:11
*** markmcclain has quit IRC07:11
*** eguz has quit IRC07:11
*** ttrifonov is now known as ttrifonov_zZzz07:13
*** jcoufal has joined #openstack-meeting-307:13
*** eghobo has quit IRC07:15
*** sarob has joined #openstack-meeting-307:29
*** ttrifonov_zZzz is now known as ttrifonov07:30
*** jcoufal has quit IRC07:33
*** nlahouti has joined #openstack-meeting-307:34
*** sarob has quit IRC07:34
*** MaxV has joined #openstack-meeting-307:36
*** nlahouti has quit IRC07:38
*** sarob has joined #openstack-meeting-307:39
*** jcoufal has joined #openstack-meeting-307:43
*** sarob has quit IRC07:44
*** jcoufal has quit IRC07:51
*** mrunge has joined #openstack-meeting-307:59
*** jcoufal has joined #openstack-meeting-308:00
*** jcoufal has quit IRC08:14
*** tomoe_ has quit IRC08:33
*** nlahouti has joined #openstack-meeting-308:34
*** sankarshan is now known as sankarshan_away08:35
*** nlahouti has quit IRC08:39
*** sarob has joined #openstack-meeting-308:39
*** igordcard has joined #openstack-meeting-308:43
*** jcoufal has joined #openstack-meeting-308:43
*** sarob has quit IRC08:43
*** coolsvap is now known as coolsvap|afk08:55
*** nlahouti has joined #openstack-meeting-309:05
*** coolsvap|afk is now known as coolsvap09:06
*** nlahouti has quit IRC09:10
*** nlahouti has joined #openstack-meeting-309:36
*** sarob has joined #openstack-meeting-309:38
*** sarob_ has joined #openstack-meeting-309:39
*** nlahouti has quit IRC09:40
*** sarob has quit IRC09:43
*** MaxV has quit IRC09:43
*** sarob_ has quit IRC09:44
*** MaxV has joined #openstack-meeting-309:51
*** nlahouti has joined #openstack-meeting-310:07
*** nlahouti has quit IRC10:11
*** yamahata has quit IRC10:21
*** MaxV has quit IRC10:31
*** nlahouti has joined #openstack-meeting-310:38
*** sarob has joined #openstack-meeting-310:39
*** nlahouti has quit IRC10:42
*** sarob has quit IRC10:43
*** nedbat has joined #openstack-meeting-310:55
*** MaxV has joined #openstack-meeting-311:01
*** MaxV has quit IRC11:06
*** nlahouti has joined #openstack-meeting-311:09
*** nlahouti has quit IRC11:13
*** rm_work is now known as rm_work|away11:16
*** MaxV has joined #openstack-meeting-311:29
*** coolsvap is now known as coolsvap|afk11:36
*** jamiehan_ has joined #openstack-meeting-311:39
*** sarob has joined #openstack-meeting-311:39
*** nlahouti has joined #openstack-meeting-311:39
*** jamiehannaford has quit IRC11:41
*** sarob has quit IRC11:43
*** lcheng has quit IRC11:44
*** nlahouti has quit IRC11:44
*** jamiehan_ is now known as jamiehannaford11:45
*** mrunge has quit IRC11:55
*** nedbat has quit IRC11:59
*** nlahouti has joined #openstack-meeting-312:10
*** yamahata has joined #openstack-meeting-312:11
*** jamiehannaford has quit IRC12:14
*** jamiehannaford has joined #openstack-meeting-312:15
*** nlahouti has quit IRC12:15
*** jamiehan_ has joined #openstack-meeting-312:23
*** jamiehannaford has quit IRC12:24
*** amotoki has quit IRC12:31
*** sarob has joined #openstack-meeting-312:39
*** nlahouti has joined #openstack-meeting-312:41
*** sarob has quit IRC12:44
*** Youcef_ has quit IRC12:46
*** coolsvap|afk has quit IRC12:46
*** coolsvap|afk has joined #openstack-meeting-312:46
*** nlahouti has quit IRC12:46
*** Youcef has joined #openstack-meeting-312:47
*** sankarshan_away is now known as sankarshan12:59
*** julim has joined #openstack-meeting-313:01
*** yamahata has quit IRC13:03
*** jamiehannaford has joined #openstack-meeting-313:03
*** yamahata has joined #openstack-meeting-313:03
*** jamiehan_ has quit IRC13:06
*** lblanchard has joined #openstack-meeting-313:07
*** thomasem has joined #openstack-meeting-313:08
*** nlahouti has joined #openstack-meeting-313:12
*** thomasem has quit IRC13:12
*** thomasem has joined #openstack-meeting-313:13
*** nlahouti has quit IRC13:16
*** peristeri has joined #openstack-meeting-313:25
*** andymaier has joined #openstack-meeting-313:30
*** mwagner_lap has quit IRC13:36
*** sarob has joined #openstack-meeting-313:39
*** nlahouti has joined #openstack-meeting-313:43
*** sarob has quit IRC13:43
*** nedbat has joined #openstack-meeting-313:47
*** nlahouti has quit IRC13:47
*** mfer has joined #openstack-meeting-313:47
*** seizadi has joined #openstack-meeting-313:49
*** mrunge has joined #openstack-meeting-313:55
*** jackib has joined #openstack-meeting-313:55
*** jackib has quit IRC14:01
*** rm_work|away is now known as rm_work14:03
*** banix has joined #openstack-meeting-314:09
*** nlahouti has joined #openstack-meeting-314:14
*** nlahouti has quit IRC14:18
*** seizadi has quit IRC14:19
*** otherwiseguy has joined #openstack-meeting-314:19
*** mrunge has quit IRC14:22
*** davlaps has joined #openstack-meeting-314:24
*** jcoufal has quit IRC14:27
*** otherwiseguy has quit IRC14:31
*** jackib has joined #openstack-meeting-314:31
*** jackib has quit IRC14:32
*** jackib has joined #openstack-meeting-314:32
*** coolsvap|afk is now known as coolsvap14:33
*** otherwiseguy has joined #openstack-meeting-314:35
*** sarob has joined #openstack-meeting-314:39
*** yamahata has quit IRC14:41
*** sarob has quit IRC14:43
*** devvesa has joined #openstack-meeting-314:47
*** coolsvap is now known as coolsvap|afk14:49
*** seizadi has joined #openstack-meeting-314:52
*** awang has joined #openstack-meeting-314:52
*** prad has joined #openstack-meeting-314:52
*** yamamoto has joined #openstack-meeting-314:54
*** xuhanp has joined #openstack-meeting-314:55
*** awang is now known as alicewang14:55
*** sarob has joined #openstack-meeting-314:57
*** pcm_ has joined #openstack-meeting-315:00
*** carl_baldwin has joined #openstack-meeting-315:00
pcm_carl_baldwin: hi15:00
carl_baldwinpcm_: hi15:01
carl_baldwinhi all15:01
*** sarob has quit IRC15:01
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Jun 12 15:01:32 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:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
*** andymaier has quit IRC15:01
yamamotohi15:01
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
carl_baldwinJuno-1 is today.15:02
chuckChi15:02
*** andymaier has joined #openstack-meeting-315:02
devvesahi15:02
*** sarob has joined #openstack-meeting-315:03
carl_baldwinIf you’re going to the mid-cycle sprint for nova/neutron parity, you’ll want to have booked your travel.  Kyle sent an email about the hotel block.15:03
carl_baldwin#link https://etherpad.openstack.org/p/neutron-juno-mid-cycle-meeting15:03
carl_baldwin#topic Bugs15:04
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:04
carl_baldwin#link https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-ipam-dhcp15:04
carl_baldwinI haven’t seen any new bugs of High Importance or higher.15:04
carl_baldwinI don’t see Swami here.  We’ll leave DVR for last.15:06
*** jackib has quit IRC15:06
carl_baldwin#topic l3-high-availability15:06
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:06
carl_baldwinsafchain: hi15:06
safchaincarl_baldwin, hi15:06
carl_baldwinAnything new this week?  Looks like there were a few questions on the blueprint.15:06
safchaincarl_baldwin, started to discuss with the dvr team, trying to address some comments15:07
safchaincarl_baldwin, feel free to add yours15:07
*** sarob has quit IRC15:07
carl_baldwinI have not revisited the bp this week.  I will do so today.15:08
safchaincarl_baldwin, seems there is a lot of dependencies with the dvr, I will have to rebase my proposal on it15:08
carl_baldwin#action carl_baldwin will revisit l3-high-availability bp15:08
*** coolsvap|afk is now known as coolsvap15:08
carl_baldwinsafchain: anything else?15:08
safchaincarl_baldwin, ok for me15:08
carl_baldwinsafchain: thanks15:09
carl_baldwin#topic neutron-ipam15:09
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:09
*** nlahouti has joined #openstack-meeting-315:09
seizadiHi15:09
carl_baldwinseizadi: hi15:09
carl_baldwinroaet_: ping15:09
seizadiWe have a few reviewers of the bp but no comments.15:10
carl_baldwinseizadi: I did an initial read through of your blueprint but have not finished my comments.15:10
carl_baldwinI added a handful of reviewers to it as well.15:10
seizadiGreat, we are trying to meet the Juno2 date but need the comments to scope the effort15:10
carl_baldwinI think Juno-1 may have taken reviewers’ energies this week.15:10
seizadiOK15:11
seizadiThat15:11
*** ttrifonov is now known as ttrifonov_zZzz15:11
seizadiis it for this week.15:11
carl_baldwinseizadi: One thought that I had when I read through it is that I think I’d like to see IPAM decoupled from the DHCP implementation.15:11
carl_baldwinI realize that they may be coupled in some external implementations but decoupling them wont’ prevent an implementation from implementing both.15:12
carl_baldwinAny thoughts?15:12
seizadiYes, we wanted to decouple DHCP and DNS from bp. If there is anything like that point it out. We might have missed something. I will look at it again.15:12
carl_baldwinI will read through it again and add my comments soon.15:13
carl_baldwin#action carl_baldwin will also review neutron-ipam bp.15:14
carl_baldwinseizadi: anything else?15:14
seizadiThe IPAM driver is abstract class, we will have couple implements one that does what the current functionality and one that will talk to our Infoblox solution.15:14
seizadiNo other update.15:14
carl_baldwinseizadi: thanks15:14
carl_baldwin#topic bgp-dynamic-routing15:15
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:15
*** andymaier has quit IRC15:15
carl_baldwinnextone92: devvesa: ping15:15
devvesahi15:15
devvesanextone92 is not available today15:16
carl_baldwinokay.  Updates?15:16
yamamotohi15:16
devvesaI summited a new patch based on the conversation we had after the meeting15:16
carl_baldwinyamamoto: hi15:16
devvesaabout the use cases15:16
devvesabut i've been busy in other stuff this week and I haven't played with the Ryu bgp speaker15:17
carl_baldwindevvesa: Yes, I need to review that update as well.  I’ve had juno-1 blinders on for a week or so.15:17
*** otherwiseguy has quit IRC15:17
yamamotoryu team is working on new api which is hopefully easier to use than the current one15:17
yamamotohttp://sourceforge.net/p/ryu/mailman/message/32434586/15:18
devvesabut I understand the current bgp speaker is part of the whole ryu library15:18
devvesaare you planning to update the neutron dependency?15:19
yamamoto?15:19
devvesai mean, ryu is a dependency of neutron, right?15:19
yamamotoryu plugin and ofagent depends on ryu15:20
*** tomoe_ has joined #openstack-meeting-315:20
yamamotoneutron’s requirement.txt doesn’t have ryu15:21
*** otherwiseguy has joined #openstack-meeting-315:21
yamamotodo you mean this?15:21
devvesayes15:21
devvesaok, then forget it15:21
carl_baldwinyamamoto:  Do you need input from us for this work?15:21
yamamotothe current practice is install ryu with pip when using ofagent or ryu plugin15:21
yamamotoyes we love to hear opinions from neutron folks15:22
*** markmcclain has joined #openstack-meeting-315:22
carl_baldwinyamamoto: Could the speaker be broken out into a library?15:23
yamamotowhat do you mean?  packaging?15:23
carl_baldwinMore or less, yes.15:23
yamamotobgp-only library is preferable?15:24
carl_baldwinWe’ll have a core piece of neutron depending on ryu so I think it would be added as a formal dependency.  I’m just wondering if that would be easier with a bpg-only library.15:24
carl_baldwinI’m not really stating any requirements yet.  Just thinking out loud to get your thoughts.15:25
devvesayamamoto: that would be great for me15:25
yamamotook, i’ll discuss the possibility with the rest of ryu folks15:25
carl_baldwinyamamoto: Thanks.15:25
yamamotobut installing the whole ryu and just using only bgp part should be fine15:25
devvesabtw, yamamoto: do you think is better that i use the current development branch with the new API15:25
yamamotounless you concern disk space :-)15:25
carl_baldwindevvesa: Will you be able to review their new API?15:26
yamamotodevvesa yes15:26
*** cjellick has joined #openstack-meeting-315:26
yamamotobut the patch i mentioned with the above url has not been merged yet15:26
*** alexpilotti has joined #openstack-meeting-315:26
yamamotoi’ll tell you when it’s merged15:27
*** emagana has joined #openstack-meeting-315:27
devvesagreat15:27
devvesawhen do you estimate it will be?15:27
yamamotohopefully by early next week15:28
carl_baldwindevvesa: A review of the unmerged code would be good.  If we have any feedback, it could be worked in before merge.15:28
devvesaok!15:28
yamamotoyea, the patch above have a comment which has a usage example15:28
devvesa#link http://sourceforge.net/p/ryu/mailman/message/32434586/15:29
devvesa(better to come back later)15:29
yamamotowe want to hear on which event you want callbacks15:29
carl_baldwin#action devvesa will review BGP speaker API.15:29
carl_baldwindevvesa: Feel free to pull me in for discussion.  I’ll be a bit scarce over the next week but I’ll check in on email.15:30
carl_baldwinAnything else on this topic?15:30
yamamotonothing from me15:30
devvesanothing from me neither15:30
carl_baldwinyamamoto: devvesa: thank you.15:31
devvesathanks to you15:31
carl_baldwin#topic neutron-ovs-dvr15:32
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:32
*** emagana has quit IRC15:32
yamamotothank you15:32
carl_baldwinA lot of the DVR team are on vacation this week.15:32
carl_baldwinIs anyone here to represent the DVR team?15:32
*** emagana has joined #openstack-meeting-315:33
carl_baldwinI can give a report.15:33
carl_baldwinA few patches on the dvr topic merged for juno-1.  However, the bulk of the work is still under review.15:33
*** alicewang has quit IRC15:34
carl_baldwinThe team has completed all of the features internally and are busy pushing patches up now.15:35
carl_baldwinThis is a top priority for the Neutron team.15:36
carl_baldwin#link https://review.openstack.org/#/q/topic:bp/neutron-ovs-dvr,n,z15:36
*** jamiehannaford has quit IRC15:36
carl_baldwinI put some notes for reviewers on the this link:15:36
carl_baldwin#link https://wiki.openstack.org/wiki/Neutron/DVR/HowTo15:37
*** jamiehannaford has joined #openstack-meeting-315:37
carl_baldwinI’ve started adding notes about the deployment of DVR as well to this page.15:37
carl_baldwinI’m building a reference two-node devstack system.  If anyone would like help building a system of their own, I can give you access to mine to use as reference.15:38
carl_baldwinContact me out of band for details.15:38
*** jamiehannaford has quit IRC15:38
carl_baldwinchuckC: Related to this topic, is there anything that you have to discuss?15:39
*** sarob has joined #openstack-meeting-315:39
chuckCnot much, still getting my 2-node devstack system going15:39
chuckCI'll be helping out with system testing15:39
carl_baldwinchuckC: That will be great.15:40
*** jamiehannaford has joined #openstack-meeting-315:40
carl_baldwinAre there others with interest in testing the DVR code?15:41
*** Rajeev has joined #openstack-meeting-315:41
carl_baldwinchuckC: I can work with you on this a bit.  I’ll be continuing to work on my reference system.15:42
chuckCWe need help from folks with related experience15:42
chuckCcarl_baldwin: thanks15:42
carl_baldwinchuckC: noted, I will engage a few cores with testing skills for discussion.15:42
*** sarob has quit IRC15:43
carl_baldwin#topic Open Discussion15:44
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:44
pcm_carl_baldwin: For client validation removal. See you signed up for that. Thanks!15:45
pcm_carl_baldwin: Should the resolution be to convert the enum attributes to strings?15:45
*** eghobo has joined #openstack-meeting-315:45
carl_baldwinpcm_: Did I miss your topic?15:45
pcm_Sure, but np15:45
carl_baldwin#topic l3-svcs-vendor-*15:46
*** openstack changes topic to "l3-svcs-vendor-* (Meeting topic: neutron_l3)"15:46
carl_baldwinSorry for the oversight.15:46
pcm_np15:46
pcm_BP for vendor validation was approved. Appreciated the reviews.15:46
carl_baldwinpcm_: Great.15:47
pcm_Having a bit of problem with UT for VPN code for this. Making changes now. Hope to push out Fri or Mon15:47
carl_baldwinpcm_: I might have missed something in my patch.15:47
pcm_(side tracked by other items)15:47
pcm_For the client side validation removal, I saw you sign up for it. Thanks! Is there a patch out?15:48
*** xuhanp has quit IRC15:48
carl_baldwinpcm_: Did you see the patch I put up?  I think what I did was to effectively remove the enum and accept any string.15:48
carl_baldwin#link https://review.openstack.org/#/c/99437/15:49
pcm_carl_baldwin: Not yet. Will look for it. Cool I was wondering if that would be the right thing to do (enum->string)15:49
pcm_Will review today.15:50
pcm_Appreciate you grabbing that. I've been swamped. :(15:50
pcm_That's all I have.15:50
carl_baldwinIt was a really easy change.  That’s why I took it on.  I needed something easy to get through because I was stuck on everything else I was trying to do yesterday.  :)15:50
pcm_:)15:51
carl_baldwinpcm_: Let me know if you want to discuss about the unit tests.  I’ll be around today but not tomorrow.15:51
* pcm_ knows exactly what you mean from this week15:51
pcm_carl_baldwin: Will do. I think I have it sorted out. Purely an issue with mocking.15:52
carl_baldwinCool.  Let me know.15:52
pcm_Will certainly seek you and others out!15:52
carl_baldwinpcm_: Thanks for your report.  I won’t leave you out next time.15:53
pcm_no problemo15:53
carl_baldwin#topic Open Discussion15:53
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:53
carl_baldwinThanks everyone.15:55
carl_baldwin#endmeeting15:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:55
openstackMeeting ended Thu Jun 12 15:55:44 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-06-12-15.01.html15:55
yamamotothanks15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-06-12-15.01.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-06-12-15.01.log.html15:55
pcm_bye15:55
*** pcm_ has left #openstack-meeting-315:55
*** markmcclain has quit IRC15:57
*** markmcclain has joined #openstack-meeting-315:57
*** markmcclain has quit IRC15:57
*** markmcclain has joined #openstack-meeting-315:58
*** mestery has quit IRC16:03
*** mestery has joined #openstack-meeting-316:04
*** alicewang has joined #openstack-meeting-316:06
*** mwagner_lap has joined #openstack-meeting-316:07
*** yamamoto has quit IRC16:07
*** devvesa has left #openstack-meeting-316:09
*** chuckC has quit IRC16:11
*** emagana has quit IRC16:12
*** D7 has joined #openstack-meeting-316:13
*** Dseven has quit IRC16:13
*** chuckC has joined #openstack-meeting-316:13
*** alicewang has quit IRC16:16
*** seizadi has quit IRC16:17
*** markmcclain has quit IRC16:23
*** davlaps is now known as devlaps16:25
*** cgoncalves has quit IRC16:27
*** cgoncalves has joined #openstack-meeting-316:27
*** MaxV has quit IRC16:30
*** safchain has quit IRC16:32
*** sarob has joined #openstack-meeting-316:39
*** nedbat has quit IRC16:41
*** nedbat has joined #openstack-meeting-316:42
*** sarob has quit IRC16:43
*** markmcclain has joined #openstack-meeting-316:44
*** pballand has joined #openstack-meeting-316:45
*** jcoufal has joined #openstack-meeting-316:58
*** rockyg has joined #openstack-meeting-316:59
*** sarob has joined #openstack-meeting-316:59
*** MaxV has joined #openstack-meeting-317:00
*** catherine_d has joined #openstack-meeting-317:02
*** flaviof_zzz is now known as flaviof17:03
*** eghobo has quit IRC17:04
*** eghobo has joined #openstack-meeting-317:04
*** MaxV has quit IRC17:05
*** nati_ueno has joined #openstack-meeting-317:06
*** nedbat_ has joined #openstack-meeting-317:08
*** rockyg has left #openstack-meeting-317:09
*** nedbat_ has quit IRC17:09
*** nedbat_ has joined #openstack-meeting-317:09
*** erw has joined #openstack-meeting-317:12
*** nedbat has quit IRC17:12
*** LouisF has joined #openstack-meeting-317:18
*** tomoe_ has quit IRC17:21
*** markmcclain has quit IRC17:25
*** MarkAtwood has joined #openstack-meeting-317:28
*** markmcclain has joined #openstack-meeting-317:33
*** markmcclain has quit IRC17:33
*** markmcclain has joined #openstack-meeting-317:35
*** SumitNaiksatam has left #openstack-meeting-317:35
*** SumitNaiksatam has joined #openstack-meeting-317:36
*** ivar-lazzaro has joined #openstack-meeting-317:50
*** nedbat_ has quit IRC17:56
*** emagana has joined #openstack-meeting-317:57
*** rkukura has joined #openstack-meeting-317:57
*** mandeep has joined #openstack-meeting-317:59
*** s3wong has joined #openstack-meeting-318:00
*** marun has joined #openstack-meeting-318:00
banixHi everybody18:01
SumitNaiksatamhi all18:01
s3wongHello18:01
SumitNaiksatamlets get started18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Jun 12 18:01:40 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
rkukurahi18:01
*** markmcclain has quit IRC18:01
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Grou18:01
mandeepbanix: SumitNaiksatam: Hi18:01
*** markmcclain has joined #openstack-meeting-318:01
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy18:02
*** markmcclain has quit IRC18:02
mandeeps3wong: rkukura: hi18:02
banixmandeep: hi18:02
s3wongmandeep: hi18:02
*** thinrichs has joined #openstack-meeting-318:02
*** nedbat has joined #openstack-meeting-318:02
SumitNaiksatam#topic Gerrit Reviews18:02
*** openstack changes topic to "Gerrit Reviews (Meeting topic: networking_policy)"18:02
SumitNaiksatamPatches with EP, EPG, L2/3 Policy are in review:18:02
SumitNaiksatam#link https://review.openstack.org/#/c/9590018:03
SumitNaiksatam#link https://review.openstack.org/#/c/9605018:03
SumitNaiksatam#link https://review.openstack.org/#/c/9639318:03
SumitNaiksatamgetting good review coverage on the first two patches18:03
SumitNaiksatamall the review comments on the first (API) patch have been addressed18:03
*** cathy_ has joined #openstack-meeting-318:03
SumitNaiksatamthe comments on the second patch have been partially addressed18:03
rkukuraSumitNaiksatam: Noticed you recently posted updates!18:03
SumitNaiksatamrkukura: yeah, early morning todya18:04
SumitNaiksatamall patches have been rebased to current18:04
SumitNaiksatamwill try to wrap the review comments on the second patch shortly18:04
*** nbouthors has joined #openstack-meeting-318:04
SumitNaiksatamanyone want to discuss anything specific with respect to the above here?18:05
*** markmcclain has joined #openstack-meeting-318:05
rkukuraOne note is that I’m trying to make sure all the same unit tests from the non-mapping DB and plugin layers run against the mapping versions of these.18:05
SumitNaiksatamrkukura: yes18:06
SumitNaiksatamrkukura: did you see any issues?18:06
rkukuraSo some of my comments were around generaling the support functions a bit so they don’t have to be copied and extended.18:06
SumitNaiksatamrkukura: yeah, got that18:06
SumitNaiksatamrkukura: will have that in the upcoming patch set18:07
rkukuraWould be nice if I could just pass the mapping attributes to the version of endpoint(), endpoint_group(), … from the base.18:07
rkukuracool18:07
SumitNaiksatamrkukura: yep18:07
SumitNaiksatambtw, i noticed that i skipped the first item in the agenda, will circle back to it towards the end18:07
*** Baba_O_Riley has joined #openstack-meeting-318:08
Baba_O_Rileyhi everyone18:08
SumitNaiksatamBaba_O_Riley: hi18:08
Baba_O_Rileyhello sumit18:08
SumitNaiksatamok if nothing else, lets move to the next topic18:09
SumitNaiksatamthanks for the reviews btw!18:09
SumitNaiksatam#topic Mapping driver/data path patches update18:09
*** openstack changes topic to "Mapping driver/data path patches update (Meeting topic: networking_policy)"18:09
SumitNaiksatamrkukura: ?18:09
rkukuraI’ve been spending way more time on the mapping DB layer patch than I thought would be necessary, so its all pushed back about a week18:10
SumitNaiksatamrkukura: ok18:10
SumitNaiksatamrkukura: any blockers?18:10
*** catherine_d has left #openstack-meeting-318:10
rkukuraThe API layer could have been pushed, but I’ll need to sync that with SumitNaiksatam’s latest18:10
SumitNaiksatamrkukura: ok18:11
rkukuraIt took me a while to figure out how to reuse the SumitNaiksatam’s DB layer UTs, but I’ve got those working, and am adding the additional UTs fot the mapping attributes18:11
SumitNaiksatamrkukura: ok great18:11
*** absubram_ has joined #openstack-meeting-318:11
SumitNaiksatami guess the other folks have to see the patches to have more input18:11
rkukuraThis led to the comments on Sumit’s patches, and I think all should come together nicely18:11
SumitNaiksatambut happy to spend time discussing anything else that anyone wants to bring up on the mapping18:12
rkukuraI will definitely be posting the API, DB and plugin layer patches this week18:12
SumitNaiksatamrkukura: thanks for the review18:12
s3wongrkukura: cool18:12
rkukuraand the two driver patches will be next week18:12
*** sadasu has joined #openstack-meeting-318:12
*** samchoi has joined #openstack-meeting-318:12
SumitNaiksatamrkukura: are we all set on the current design decisions, or is there something pending that still needs to be discussed here?18:13
rkukuraI think its worth the effort to get the UT approaches, patterns, re-use strategies, etc. right on these before we add the next sets of resources18:13
SumitNaiksatamrkukura: okay, we will bring that up in the UT part of the agenda18:13
s3wongrkukura: will you be adding mapping policy-rules to security groups in these patches? or is that coming up after?18:13
rkukuraLast week we decided to drop the “neutron_” prefixes from the mapping attribute names, but that’s about it18:13
SumitNaiksatamrkukura: ok18:14
rkukuraThe first version of the mapping patch will just establish connectivity, like in the PoC18:14
s3wongrkukura: OK18:14
rkukuraA followon patch after the additional resources are ready will deal with enforcing policy18:14
rkukuraSo we will need to make progress in parallel next week on getting the next sets of resources into review18:15
SumitNaiksatamrkukura: yes, that is the plan18:15
banixrkukura: you mean policies other than “allow”. right?18:16
rkukuraThat’s all I have on the mappong patches18:16
rkukurabanix: right18:16
SumitNaiksatamrkukura: i thought you meant including ‘allow'18:16
SumitNaiksatamrkukura: not other than ‘allow'18:16
rkukuraI meant that the first mapping patch will allow all traffic18:17
SumitNaiksatamrkukura: yes18:17
SumitNaiksatamrkukura: i think banix is asking about the allow action18:17
rkukuraIf two EPGs use the same L3P, they’ll be able to talk18:17
banixand deal with enforcing “other” policies later18:17
*** jcoufal has quit IRC18:17
SumitNaiksatamor may be not18:17
rkukuraWe won’t have any actions until the PolicyRule, … resources are there18:17
s3wongbanix: well, we aren't doing any processing of the policy-rules, so "allow" action is given to all traffic between EPGs18:17
SumitNaiksatamrkukura: yeah18:18
banixSumitNaiksatam: rkukura got it18:18
LouisFhow will the redirect action to a service chain relate to the service chains defined in the adv-services traffic steering BP?18:18
SumitNaiksatambanix: ok good18:18
banixs3wong: thanks got it18:18
SumitNaiksatamLouisF: we have an agenda item to discuss that18:18
LouisFthx18:18
SumitNaiksatamrkukura: thanks18:18
SumitNaiksatamfor the update18:19
SumitNaiksatam#topic Services’ integration update18:19
*** openstack changes topic to "Services’ integration update (Meeting topic: networking_policy)"18:19
SumitNaiksatamLouisF: your question :-)18:19
LouisFnp18:19
SumitNaiksatams3wong: any progress (i know you are blocked on the dependencies)18:19
s3wongSumitNaiksatam: not much (sorry), still working with Kanzhe on service insertion and service base18:20
SumitNaiksatams3wong: ok18:20
s3wonguntil that is done, the official work can't be done18:20
SumitNaiksatams3wong:  you want to take LouisF’s question?18:20
s3wongfor LouisF 's question:18:20
s3wongthe service chain would actually be service chain in mandeep 's bp18:21
banixi think the traffic steering spec (and design) need a bit more work but that is not perhaps what is being referred to here?18:21
s3wongand traffic steering bp (which is not the service chaining bp) should be one of the enabling bp for service chaining18:22
SumitNaiksatams3wong: right18:22
LouisFthe traffic steering bp defines a classifer for a chain18:22
s3wongLouisF: the traffic steering bp defines classifier for a chain to redirect traffic18:23
s3wongon various discussion with cgoncalves, these details may be too deep / complicated to expect tenants to perform18:24
SumitNaiksatams3wong: i agree18:24
LouisFs3wong: right, but can the traffic steering chains be referenced from a GBP redirect action?18:24
mandeepLouisF: Service chain defined in the advanced services will be used to "render" the service chain as needed in GBP18:24
*** lsmola has quit IRC18:25
s3wongLouisF: certainly traffic steering constructs are out of scope for GBP - we don't expect app-owners to start steering traffic18:25
LouisFok, I would agree the traffic steering bp being a bit complicated18:25
banixIt would be really good if the traffic sterring spec gets reviewed more thoroughly but that is for another meeting18:25
s3wongLouisF: we can redirect to a service chain18:25
s3wongLouisF: but a service chain needs to be defined outside of GBP when you use 'redirect' action18:26
mandeeps3wong: Correct18:26
LouisFmandeep: ok18:26
SumitNaiksatamLouisF: is your question that we would need the classifier to be able to redirect to a chain?18:26
banixmandeep: does the service chain plan to use the traffic steering for the ref implementation?18:26
mandeepLouisF: Yes, but a service needs to be defined outside GBP as well ... we do not want to recreate parallel funbctionality, just a common place to define the policy that ties up all these pieces.18:26
s3wongSumitNaiksatam: LouisF: so there are two classifiers here: (a) classifier for policy-rules in contract for GBP, and (b) classifier used for traffic steering18:27
LouisFno, GBP has a classifier, I was concerned about having two different classifiers: one in GBP and one in traffic steering18:27
*** samchoi has quit IRC18:27
cathy_I assume that "redirect to a service chain" action has been supported in the GBP, right? The real chaining will be done in "service chaining" or "service steering" BP, right?18:27
s3wongcathy_: that's right18:27
SumitNaiksatamcathy_: correct18:27
SumitNaiksatamLouisF: good point18:28
mandeepbanix: From a GBP point of view, i recomnd that we chaining construct in advanced services and leave the implementation to service - it coukld as today or using steering.18:28
SumitNaiksatamLouisF: however, the scope of those classifiers is different18:28
s3wongLouisF: think of them different. The classifier in policy-rule is for app-owners to set rules upon which a policy is applied18:28
s3wongLouisF: the classifier in traffic steering is for traffic flow between network services18:28
cathy_When we specify "redirect", should user specify a chain-ID or should user specify an ordered sequence of service instances or we allow both?18:28
banixmandeep: agree; since we were discussing here thought i get your take on it18:28
mandeepbanix: Ok18:29
s3wongLouisF: when we 'redirect', it is because we want access to an EPG to be subjected to a network service - most likely defined by admin18:29
LouisFs3wong: agree18:30
SumitNaiksatammandeep: cathy_’s question ^^^18:30
banixmandeep: main point being that if the plan is to use traffic steering we need to focus on getting that right in a timely fashion as everything will be built on top of that; which in my opinion is not necessary but lets talk during the advanced services call.18:30
*** pballand has quit IRC18:30
s3wongLouisF: when we classify traffic on traffic steering, the intent is for traffic within a chain to flow to the next service to complete the definition of the chain18:30
*** markmcclain has quit IRC18:31
*** markmcclain has joined #openstack-meeting-318:31
SumitNaiksatamcathy_: its a reference to the service chain object18:31
mandeepbanix: I would prefer to keep the two not depend on each other strongly - and the keep that integration easier. But let us discuss that in the adv services issues18:31
s3wongLouisF: it is likely that the consumer of these two sets of APIs to be different people (app-owner defining app's behavior on the network; admin defining how the traffic flows through the chain)18:31
SumitNaiksatamcathy_: i dont think we have considered allowing both18:31
*** pballand has joined #openstack-meeting-318:32
cathy_What information is defined in the service chain object?18:32
mandeepcathy_: For now. we assume that the redirect action is always the last actoion of the chain.18:32
banixcathy_: a reference to a service or service chain18:32
*** pballand has quit IRC18:32
mandeepbanix: agreed18:32
SumitNaiksatamcathy_: more info here: https://review.openstack.org/#/c/9352418:33
banixcathy_: being discussed in the advanced services subgroup18:33
cathy_when you say a reference to a service chain, how you specify the service chain? an ID or a sequence of sevice instances?18:33
SumitNaiksatamcathy_: and i know you agreed to review :-P18:33
*** Rajeev has quit IRC18:33
s3wongcathy_: just an ID18:33
cathy_Ok, I will give my comments.18:33
banixan ID as s3wong says18:33
SumitNaiksatamLouisF: good questions, tells me that you are reviewing the BPs as promised, thanks :-)18:34
cathy_OK, thanks.18:34
SumitNaiksatamok lets move on, unless there is something more18:34
s3wongcathy_: a service chain needs to be defined by someone (admin or tenant) by putting together the sequence of service instances18:34
cathy_Any the sequence information should be passed down to driver to set up the service chain18:35
s3wongcathy_: that's the intent18:35
mandeepcathy_: That is correct18:35
cathy_OK18:35
SumitNaiksatam#topic Client, CLI, Horizon update18:35
*** openstack changes topic to "Client, CLI, Horizon update (Meeting topic: networking_policy)"18:35
SumitNaiksatamhemanth ronak here?18:36
SumitNaiksatamperhaps hemanth is travelling18:36
SumitNaiksatami wanted to check if there are any blockers18:36
SumitNaiksatamok they are not here18:36
SumitNaiksatammoving on18:36
LouisFwhere is the horizon work?18:36
SumitNaiksatamLouisF: #link https://review.openstack.org/#/c/93590/18:37
LouisFthx18:37
mandeepnati_ueno was looking into helping us make improvements on that.18:37
nati_uenohi18:38
SumitNaiksatamnati_ueno: hi, do you have the link to your horizon document?18:38
LouisFwill review18:38
SumitNaiksatamnati_ueno: i cant seem to find it18:38
s3wongmandeep: nati_ueno 's proposal seems more like the next step, right?18:38
SumitNaiksatamLouisF: thanks18:38
*** shivharis has joined #openstack-meeting-318:38
SumitNaiksatams3wong: yes18:38
nati_uenolet mee see18:38
SumitNaiksatamnati_ueno: thanks18:39
mandeeps3wong: Correct18:39
*** markmcclain has quit IRC18:39
*** Baba_O_Riley has quit IRC18:39
*** Baba_O_Riley has joined #openstack-meeting-318:39
nati_uenohttps://docs.google.com/presentation/d/1SmbhY5GTBKFV0U6XmAlaWn2nm-biV5bFVZDURZslNrg/edit?usp=drive_web18:39
nati_uenohere18:39
SumitNaiksatamnati_ueno: great thanks18:39
SumitNaiksatamLouisF: ^^^18:39
SumitNaiksatamok next topic18:39
SumitNaiksatam#topic Unit tests18:39
*** openstack changes topic to "Unit tests (Meeting topic: networking_policy)"18:40
SumitNaiksatamrkukura: we discussed some of this, you want to weigh in?18:40
rkukuraWe already talked about reusing the base UTs in the mappings, and I’ll work with SumitNaiksatam to make that as simple as possible18:40
rkukuraThe UTs at the DB and plugin layer are currently written using the REST API18:41
rkukuraThere have been some discussions that these kinds of tests should avoid the REST API so they run more efficiently, etc.18:42
*** armax has joined #openstack-meeting-318:42
SumitNaiksatamrkukura: yeah, agree18:42
rkukuraIdeally, UTs would test just the code under test, in isolation18:42
SumitNaiksatamrkukura: is there any place in the Neutron code that we do this already?18:42
rkukuraSo I’m wondering if we want to try to switch to having the DB and plugin UTs just call the DB and plugin class methods directly rather than via the REST APIU18:43
rkukuraI think most exisitng neutron code has been using the REST APIs, but I’m sure we can find some examples where DB or plugin classes are tested directly.18:44
SumitNaiksatamrkukura: i agree with that approach, and i wanted to do that when we started these patches as well, however I did not see any precedence for that18:44
rkukuraDoes anyone see any reason not to switch to calling these classes directly?18:44
*** ivar-lazzaro has quit IRC18:44
rkukuraI was hoping marun would be here to comment on this, since he has raised this issue before with the existing tests18:45
marunhere18:45
*** banix has left #openstack-meeting-318:46
rkukuramarun: great - didn’t see you before18:46
*** banix has joined #openstack-meeting-318:46
marunI agree there is no precedence, and that's a blocker.18:46
SumitNaiksatammarun: yeah, happy to try out any suggestions that you or anyone else has18:46
marunI'm happy to work with someone to create a useful example, but I don't think it should preclude merging what you already have.18:47
rkukuraIt would be easier to switch now with only 4 resources than later with many more18:47
marunI would suggest it as an evolution.18:47
*** pballand has joined #openstack-meeting-318:47
marunOr are the tests no written yet?18:47
SumitNaiksatammarun: tests are written18:47
rkukuraThe tests in https://review.openstack.org/#/c/96050/ would be the place to start18:47
marunIs there anyone that wants to work with me to use the new approach?18:48
SumitNaiksatammarun: so your suggestion is to do the new approach as a separate enhancement patch?18:48
rkukuramarun: Is this just a matter of instantiating the DB or plugin class, initializing the DB, and calling methods to test?18:48
marunSumitNaiksatam: yes18:49
mandeepmarun: agreed that we should do this as an enhancement/evolutioon18:49
SumitNaiksatammarun: okay, both rkukura and I will be happy to work with you on that18:49
mandeepSumitNaiksatam: I can help as well18:50
SumitNaiksatammandeep: okay thanks18:50
rkukuraIf its not trivial, I agree we can’t take too much time to work this out before proceeding18:50
rkukuracool, I’ll continue with the current approach in the mapping UTs for now then18:50
SumitNaiksatamrkukura: okay18:50
mandeeprkukura: I agree with marun, that we need to try this as an enhancement18:50
rkukuraAt least for the DB and plugin layers, will probably try to test driver classes directly18:51
SumitNaiksatammarun rkukura mandeep (anyone else): lets synch offline on this18:51
rkukuraOK18:51
mandeepOK18:51
rkukuralast testing question I had was around functional tests18:51
SumitNaiksatam#action marun rkukura SumitNaiksatam mandeep to discuss how to structure UTs to make direct calls to the DB/Plugin layer (as enhancement patches)18:51
SumitNaiksatamrkukura: yes please go ahead18:52
rkukuraseems that if we do isolated UTs of the drivers, and maybe other layers, we really need some functional tests that ensure it all works together18:52
SumitNaiksatamrkukura: there functional tests will be different from those used in tempest?18:52
SumitNaiksatamrkukura: i mean scenario tests18:53
rkukuraI’m thinking of tests that don’t depend on anything outside neutron-server18:53
*** absubram_ has quit IRC18:53
rkukurabasically, fire up neutron-server with the GP service and mapping drivers, and test that neutron resources (networks, ports, routers, …) get managed properly.18:54
SumitNaiksatamrkukura: ok18:54
SumitNaiksatamrkukura: i guess tempest tests do the same?18:55
rkukuraThis is basically what the mapping driver UTs in the PoC were doing, but I really don’t think those are UTs18:55
rkukuratempest would do the same, but with nova and VMs and all that18:55
*** nedbat has left #openstack-meeting-318:55
rkukuraThese functional tests would run with just a neutron repo, without needing devstack18:56
SumitNaiksatamrkukura: ok18:56
SumitNaiksatamrkukura: so we could start adding those even now, right?18:56
rkukuramarun: Does this sound at all like your vision of functional tests for neutron?18:56
*** Baba_O_Riley has quit IRC18:56
*** Baba_O_Riley has joined #openstack-meeting-318:56
*** Youcef has quit IRC18:57
SumitNaiksatamwe do have some functional tests defined here: #link https://github.com/openstack/neutron/tree/master/neutron/tests/functional18:57
*** devlaps has quit IRC18:58
SumitNaiksatamrkukura: perhaps move those mapping driver UTs to ^^^ to begin with?18:58
marunrkukura: yes18:58
*** SumitNaiksatam has quit IRC18:58
rkukuraSumitNaiksatam: I’m aware of those, but they are very low level tests of interaction with the system, and probably should not run by default18:58
marunrkukura: they are optional, they'll skip if they don't have the necessary dependencies18:59
*** markmcclain has joined #openstack-meeting-318:59
*** jackib has joined #openstack-meeting-318:59
*** SumitNaiksatam has joined #openstack-meeting-318:59
marunrkukura: the functional suite will run in the gate in an environment configured by devstack (for dependencies) but without the services running18:59
rkukuramarun: Would it make more sense to do these tests via the REST API like the current UTs, or using python-neutronclient?18:59
*** ivar-lazzaro has joined #openstack-meeting-318:59
marunrkukura: but it's still the right place to put non-unit tests.18:59
marunrkukura: definitely with the rest api19:00
rkukuramarun: OK19:00
marunrkukura: having a dependency on the native client would require too much coordination between the two repos19:00
SumitNaiksatamok we are out of time19:00
SumitNaiksatamthanks all!19:00
SumitNaiksatamsee you next week19:00
SumitNaiksatambye19:01
rkukuraI’d have said the same thing, but we already do depend on python-neutronclient, and the mapping driver will be using it19:01
SumitNaiksatam#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
banixbye19:01
openstackMeeting ended Thu Jun 12 19:01:04 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-06-12-18.01.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-06-12-18.01.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-06-12-18.01.log.html19:01
rkukurabye19:01
Baba_O_Rileybye19:01
SumitNaiksatamrkukura: sorry to cut you19:01
rkukuraSumitNaiksatam: NP19:01
marunrkukura: let's talk offline19:01
s3wongthanks all, bye!19:01
SumitNaiksatamrkukura: did not realize that we were still discussing19:01
rkukuramarun: sure, ping me on IRC or hangout19:01
*** MaxV has joined #openstack-meeting-319:02
*** sadasu has quit IRC19:02
marunrkukura: will do.  I'll review https://review.openstack.org/#/c/96050/ first19:02
rkukuramarun: makes sense - thanks19:02
*** rkukura has left #openstack-meeting-319:03
*** cathy_ has quit IRC19:04
*** eguz has joined #openstack-meeting-319:05
*** mandeep has quit IRC19:05
*** eguz has quit IRC19:06
*** jackib has quit IRC19:06
*** MaxV has quit IRC19:07
*** eghobo has quit IRC19:08
*** nlahouti has quit IRC19:08
*** shivharis has left #openstack-meeting-319:10
*** Youcef has joined #openstack-meeting-319:13
*** Baba_O_Riley has quit IRC19:13
*** markmcclain has quit IRC19:25
*** nbouthors has quit IRC19:36
*** s3wong has quit IRC19:37
*** nlahouti has joined #openstack-meeting-319:39
*** devlaps has joined #openstack-meeting-319:41
*** emagana has quit IRC19:43
*** emagana has joined #openstack-meeting-319:45
*** markmcclain has joined #openstack-meeting-319:45
*** nati_ueno has quit IRC19:47
*** markmcclain has quit IRC19:51
*** nati_ueno has joined #openstack-meeting-319:56
*** gduan has joined #openstack-meeting-320:03
*** lblanchard has quit IRC20:03
*** garyduan has quit IRC20:03
*** Youcef_ has joined #openstack-meeting-320:09
*** Youcef has quit IRC20:12
*** MaxV has joined #openstack-meeting-320:13
*** emaganap has joined #openstack-meeting-320:16
*** garyduan has joined #openstack-meeting-320:16
*** boris-42 has quit IRC20:18
*** emagana has quit IRC20:18
*** boris-42 has joined #openstack-meeting-320:18
*** gduan has quit IRC20:19
*** MaxV has quit IRC20:20
*** MaxV has joined #openstack-meeting-320:21
*** thinrichs has quit IRC20:22
*** nati_ueno has quit IRC20:28
*** TravT has joined #openstack-meeting-320:29
*** julim has quit IRC20:35
*** markmcclain has joined #openstack-meeting-320:36
*** Youcef_ has quit IRC20:38
*** banix has quit IRC20:39
*** otherwiseguy has quit IRC20:41
*** emaganap has quit IRC20:41
*** banix has joined #openstack-meeting-320:43
*** nati_ueno has joined #openstack-meeting-320:44
*** emagana has joined #openstack-meeting-320:46
*** jamiehannaford has quit IRC20:53
*** jtomasek has quit IRC20:55
*** LouisF has quit IRC20:58
*** nati_ueno has quit IRC21:07
*** armax has left #openstack-meeting-321:10
*** markmcclain has quit IRC21:12
*** markmcclain1 has joined #openstack-meeting-321:12
*** eghobo has joined #openstack-meeting-321:14
*** banix has quit IRC21:15
*** TravT has quit IRC21:31
*** thomasem has quit IRC21:35
*** thomasem_ has joined #openstack-meeting-321:35
*** pballand has quit IRC21:37
*** thomasem_ has quit IRC21:39
*** mfer has quit IRC21:39
*** HenryG has quit IRC21:45
*** jamiehannaford has joined #openstack-meeting-321:46
*** markmcclain1 has quit IRC21:56
*** markmcclain has joined #openstack-meeting-321:56
*** jamielennox is now known as jamielennox|away21:58
*** MarkAtwood has quit IRC22:00
*** nati_ueno has joined #openstack-meeting-322:03
*** pballand has joined #openstack-meeting-322:12
*** mfer has joined #openstack-meeting-322:15
*** mfer has quit IRC22:19
*** SumitNaiksatam has quit IRC22:24
*** markmcclain has quit IRC22:27
*** peristeri has quit IRC22:40
*** lblanchard has joined #openstack-meeting-322:41
*** HenryG has joined #openstack-meeting-322:42
*** Deight has joined #openstack-meeting-322:47
*** carl_baldwin has quit IRC22:49
*** D7 has quit IRC22:50
*** sarob has quit IRC22:52
*** ivar-lazzaro has quit IRC22:53
*** sarob has joined #openstack-meeting-322:53
*** jamielennox|away is now known as jamielennox23:05
*** sarob has quit IRC23:09
*** sarob has joined #openstack-meeting-323:10
*** jamielennox has left #openstack-meeting-323:16
*** markmcclain has joined #openstack-meeting-323:18
*** Dseven has joined #openstack-meeting-323:22
*** Deight has quit IRC23:25
*** MaxV has quit IRC23:29
*** MaxV has joined #openstack-meeting-323:29
*** jamiehannaford has quit IRC23:35
*** emagana has quit IRC23:40
*** sarob has quit IRC23:41
*** sarob_ has joined #openstack-meeting-323:41
*** nlahouti_ has joined #openstack-meeting-323:49
*** nlahouti has quit IRC23:52
*** igordcard has quit IRC23:58

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