Thursday, 2014-05-22

*** chuckC has joined #openstack-meeting-300:01
*** ttrifonov is now known as ttrifonov_zZzz00:01
*** markmcclain has quit IRC00:05
*** chuckC has quit IRC00:14
*** lcheng_ has quit IRC00:22
*** sarob has joined #openstack-meeting-300:22
*** sarob has quit IRC00:27
*** chuckC has joined #openstack-meeting-300:28
*** devlaps has quit IRC00:38
*** cjellick has quit IRC00:47
*** nati_ueno has quit IRC00:50
*** nati_ueno has joined #openstack-meeting-300:59
*** nati_ueno has quit IRC01:01
*** rgbkrk_ has joined #openstack-meeting-301:16
*** SridarK has quit IRC01:18
*** rgbkrk has quit IRC01:18
*** mrunge_away has quit IRC01:28
*** lcheng_ has joined #openstack-meeting-301:34
*** mrunge has joined #openstack-meeting-301:44
*** lcheng_ has quit IRC01:49
*** banix has joined #openstack-meeting-301:57
*** rgbkrk_ has quit IRC02:05
*** mrunge has quit IRC02:08
*** rgbkrk has joined #openstack-meeting-302:09
*** rgbkrk has quit IRC02:11
*** mrunge has joined #openstack-meeting-302:11
*** rgbkrk has joined #openstack-meeting-302:12
*** rgbkrk has quit IRC02:16
*** lcheng_ has joined #openstack-meeting-302:18
*** rgbkrk has joined #openstack-meeting-302:19
*** sankarshan is now known as sankarshan_away02:32
*** kenhui has joined #openstack-meeting-302:43
*** kenhui has quit IRC02:46
*** Youcef_ has quit IRC02:54
*** jpomero_ has joined #openstack-meeting-302:54
*** banix_ has joined #openstack-meeting-303:00
*** sankarshan_away is now known as sankarshan03:01
*** anteaya has quit IRC03:03
*** edhall has quit IRC03:03
*** dansmith has quit IRC03:03
*** jpomero has quit IRC03:03
*** dansmith has joined #openstack-meeting-303:03
*** edhall has joined #openstack-meeting-303:03
*** anteaya has joined #openstack-meeting-303:04
*** otherwiseguy has joined #openstack-meeting-303:05
*** yamamoto has quit IRC03:05
*** ttrifonov_zZzz is now known as ttrifonov03:06
*** yamahata__ has joined #openstack-meeting-303:07
*** yamahata_ has quit IRC03:07
*** banix has quit IRC03:09
*** banix_ is now known as banix03:09
*** yamamoto has joined #openstack-meeting-303:11
*** nelsnelson has quit IRC03:15
*** boris-42 has quit IRC03:23
*** banix has quit IRC03:27
*** boris-42 has joined #openstack-meeting-303:29
*** eghobo has joined #openstack-meeting-303:35
*** lcheng_ has quit IRC03:36
*** TravT has quit IRC03:39
*** coolsvap|afk is now known as coolsvap03:49
*** nelsnelson has joined #openstack-meeting-303:57
*** beyounn_1 has quit IRC03:59
*** rgbkrk has quit IRC04:05
*** rgbkrk has joined #openstack-meeting-304:10
*** eghobo has quit IRC04:25
*** yamamoto has quit IRC04:29
*** eghobo has joined #openstack-meeting-304:31
*** yisun has joined #openstack-meeting-304:32
*** rgbkrk has quit IRC04:38
*** yisun has left #openstack-meeting-304:50
*** terryw has joined #openstack-meeting-304:53
*** otherwiseguy has quit IRC04:56
*** nelsnelson has quit IRC05:05
*** gcb has joined #openstack-meeting-305:16
*** ttrifonov is now known as ttrifonov_zZzz05:34
*** gcb has quit IRC05:51
*** sankarshan has quit IRC05:59
*** sankarshan has joined #openstack-meeting-305:59
*** gcb has joined #openstack-meeting-306:04
*** terryw has quit IRC06:06
*** sankarshan is now known as sankarshan_away06:06
*** eghobo has quit IRC06:06
*** sankarshan_away is now known as sankarshan06:10
*** sankarshan is now known as sankarshan_away06:24
*** sankarshan_away is now known as sankarshan06:25
*** rkukura has joined #openstack-meeting-306:28
*** beyounn has joined #openstack-meeting-306:34
*** yamahata has joined #openstack-meeting-306:36
*** jpomero_ has quit IRC06:46
*** jpomero_ has joined #openstack-meeting-306:46
*** yamahata has quit IRC06:48
*** jcoufal has joined #openstack-meeting-306:53
*** jpomero has joined #openstack-meeting-307:01
*** gcb has quit IRC07:02
*** jpomero_ has quit IRC07:03
*** beyounn has quit IRC07:12
*** samchoi has quit IRC07:36
*** nelsnelson has joined #openstack-meeting-307:45
*** nacim has joined #openstack-meeting-307:50
*** safchain has joined #openstack-meeting-308:14
*** jamie_h has joined #openstack-meeting-308:26
*** d0ugal_ has joined #openstack-meeting-308:29
*** jamielennox is now known as jamielennox|away08:37
*** d0ugal_ has quit IRC08:39
*** sankarshan is now known as sankarshan_away08:44
*** d0ugal_ has joined #openstack-meeting-308:46
*** jtomasek has quit IRC08:56
*** jtomasek has joined #openstack-meeting-308:58
*** d0ugal_ has quit IRC09:05
*** mrunge is now known as mrunge_afk09:13
*** d0ugal_ has joined #openstack-meeting-309:14
*** d0ugal_ has quit IRC09:17
*** d0ugal_ has joined #openstack-meeting-309:22
*** d0ugal has quit IRC09:22
*** d0ugal_ is now known as d0ugal09:22
*** d0ugal has quit IRC09:25
*** d0ugal has joined #openstack-meeting-309:25
*** mrunge_afk is now known as mrunge10:44
*** coolsvap is now known as coolsvap|afk10:51
*** sankarshan_away is now known as sankarshan11:08
*** mwagner_lap has quit IRC11:54
*** jpomero has quit IRC12:06
*** mrunge has quit IRC12:06
*** nacim has quit IRC12:07
*** jpomero has joined #openstack-meeting-312:09
*** thomasem has joined #openstack-meeting-312:14
*** thomasem has quit IRC12:19
*** thomasem has joined #openstack-meeting-312:19
*** nacim has joined #openstack-meeting-312:23
*** cgoncalv1s is now known as cgoncalves12:28
*** cgoncalves has joined #openstack-meeting-312:28
*** markmcclain has joined #openstack-meeting-312:32
*** dkorn has joined #openstack-meeting-312:33
*** julim has joined #openstack-meeting-312:54
*** jpomero has quit IRC13:05
*** nacim has quit IRC13:11
*** rgbkrk has joined #openstack-meeting-313:21
*** mfer has joined #openstack-meeting-313:25
*** jpomero has joined #openstack-meeting-313:27
*** peristeri has joined #openstack-meeting-313:28
*** lblanchard has joined #openstack-meeting-313:29
*** markmcclain1 has joined #openstack-meeting-313:32
*** markmcclain2 has joined #openstack-meeting-313:33
*** markmcclain2 has quit IRC13:33
*** markmcclain has quit IRC13:33
*** markmcclain has joined #openstack-meeting-313:33
*** markmcclain1 has quit IRC13:38
*** banix has joined #openstack-meeting-313:41
*** nacim has joined #openstack-meeting-313:41
*** otherwiseguy has joined #openstack-meeting-313:58
*** TravT has joined #openstack-meeting-314:01
*** nextone92 has joined #openstack-meeting-314:01
*** MaxV_ has joined #openstack-meeting-314:02
*** nextone92 has quit IRC14:02
*** MaxV_ has quit IRC14:06
*** jamie_h has quit IRC14:11
*** jamie_h has joined #openstack-meeting-314:12
*** tomoe_ has joined #openstack-meeting-314:13
*** otherwiseguy has quit IRC14:17
*** tomoe_ has quit IRC14:21
*** lcheng_ has joined #openstack-meeting-314:24
*** david-lyle has joined #openstack-meeting-314:26
*** devlaps has joined #openstack-meeting-314:38
*** roaet has joined #openstack-meeting-314:46
*** yamahata has joined #openstack-meeting-314:46
*** otherwiseguy has joined #openstack-meeting-314:55
*** rudrarugge has joined #openstack-meeting-314:56
*** otherwiseguy has quit IRC14:58
*** terryw has joined #openstack-meeting-314:58
*** carl_baldwin has joined #openstack-meeting-314:58
*** amuller has joined #openstack-meeting-314:59
carl_baldwinhi all14:59
*** rkukura has left #openstack-meeting-315:00
carl_baldwinLet’s get started.15:00
carl_baldwin#startmeeting neutron_l315:00
openstackMeeting started Thu May 22 15:00:48 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:00
*** armax has joined #openstack-meeting-315:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
*** pcm__ has joined #openstack-meeting-315:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
*** lcheng_ has quit IRC15:01
carl_baldwinSummit was great! Lot's of energy and a lot of good work to come.15:01
*** xuhanp has joined #openstack-meeting-315:01
*** nextone92 has joined #openstack-meeting-315:01
armaxyup!15:01
carl_baldwinNeutron mid-cycle meeting for Juno is set for July 9-11. I've got my travel arrangements already. Do you?15:02
carl_baldwin#link https://etherpad.openstack.org/p/neutron-juno-mid-cycle-meeting15:02
roaetpresents15:02
armaxnot yet ony my end15:02
roaetI do not have plans set up either.15:02
carl_baldwinI hope to see many of you there.15:03
carl_baldwin#topic Bugs15:03
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:03
carl_baldwin#link https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-ipam-dhcp15:03
carl_baldwinI’ll be adding this section to the meeting each week as I’ll be working more on bug triage, especially where this tag is applied.15:03
*** xuhanp has quit IRC15:04
carl_baldwinNone of the bugs stick out to me today as urgent but I haven’t been through them all.15:04
*** xuhanp has joined #openstack-meeting-315:04
carl_baldwin#topic l3-svcs-vendor-*15:04
*** openstack changes topic to "l3-svcs-vendor-* (Meeting topic: neutron_l3)"15:04
carl_baldwinpcm__: ping15:04
carl_baldwinYour session at the summit was very informative.  It got me up to speed.15:05
pcm__thanks!15:05
amullerHave to get going guys, just stopped by to say hi and that it was great meeting everyone at the summit15:05
* pcm__ trying to engage in two meetings at once :(15:05
carl_baldwinamuller: Thanks.  We’ll be in touch.15:05
roaetI'm not sure who I met, but whoever I did it was nice to meet you.15:06
carl_baldwinpcm__: I know the feeling.  Have you filed a bug for that third item?15:06
*** amuller has quit IRC15:06
pcm__carl_baldwin: sorry, which item?15:07
carl_baldwinWe could use reviews on the spec here:  https://review.openstack.org/8840615:07
carl_baldwinpcm__: There was the problem where the client validates over aggressively.15:07
pcm__ah, that one. No. Not yet. Plan to do that.15:07
*** rudrarugge has quit IRC15:07
pcm__Thought is to remove validation of enum fields from client (already no validation of integer fields)15:08
carl_baldwin#action pcm__ will file a bug for client validation problem.15:08
carl_baldwin#action carl_baldwin will review https://review.openstack.org/8840615:08
carl_baldwin^ I encourage others to review the blueprints as well.15:08
carl_baldwinpcm__: Anything else?15:09
pcm__For validation... I was thinking about separating the validation from the persistence.15:09
carl_baldwinThat sounds like a good thing.15:09
pcm__This way, if/when we go to TaskFlow, we'll have discrete tasks. In the meantime, I can try to15:09
carl_baldwinIs that spelled out in your blueprint?15:10
pcm__allow provider to override the validation (since it will be separate)15:10
pcm__BP needs to be updated to reflect summit items.15:10
pcm__will work that too.15:10
carl_baldwin#action pcm__ To update blueprint from summit discussion.15:10
carl_baldwinpcm__: Thanks.  Keep up the good work.15:11
pcm__sure. np.15:11
carl_baldwin#topic bgp-dynamic-routing15:11
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:11
roaetcarl_baldwin: btw grats on the nomination for core, quite deserved15:11
carl_baldwinnextone92: I thought the session went well.  I heard a lot of support in the room.15:11
carl_baldwinroaet: Thanks.15:11
nextone92Thank you15:11
nextone92It was a great opportunity to learn requirements and use cases for dynamic routing :)15:12
carl_baldwinI’ve heard good things since summit as well from a few people who did not speak up in the room.15:12
* pcm__ clapping15:12
carl_baldwinDo you have any action items out of it?15:12
nextone92Jaume and I are working to incorporate the comments and to work through the use cases of the new agent15:12
nextone92We have collected feedback from the in-person discussion, the session, and over the email15:13
carl_baldwinGreat, ping the ML when you’ve posted a new draft of the blueprint.  I’d like to see the improved blueprint.15:13
nextone92Great! Looking forward to more feedback after that15:14
carl_baldwinDo you have any idea what milestone you are looking to target with the implementation?15:14
nextone92I will take an action item to create the schedule estimate for next meeting15:14
*** mestery has quit IRC15:14
carl_baldwinnextone92: Great.15:15
nextone92#action nextone92 Provide BGP dynamic routing schedule15:15
carl_baldwin#topic *-dns-resolution15:15
*** openstack changes topic to "*-dns-resolution (Meeting topic: neutron_l3)"15:15
carl_baldwinI’m still working on the blueprints for this.  There are a few points to work out.  I’ll be addressing feedback but otherwise this topic is going to have to wait until DVR is merged.15:16
*** nati_ueno has joined #openstack-meeting-315:16
carl_baldwin#topic IPAM15:17
*** openstack changes topic to "IPAM (Meeting topic: neutron_l3)"15:17
* roaet salutes15:17
carl_baldwinroaet: hi15:17
roaetI have put up a very simple implementation that I believe most people can agree with on https://etherpad.openstack.org/p/ipam_pod in the Implementation Details15:17
carl_baldwinI was pleased to see the grass roots energy around this topic at the summit and recently in IRC and on ML.15:17
roaetIndeed, a lot of people showed up to the pod15:18
roaetI'm wondering any of those people are here so they can comment on the implementation.15:18
*** rgbkrk has quit IRC15:18
*** tomoe_ has joined #openstack-meeting-315:19
roaetcarl_baldwin: did you find any blueprints that you wished to use as the spearhead of this, or are we just going to use them all?15:19
carl_baldwinI took a look through them.  They were varied.15:19
carl_baldwinWe should try to consolidate.15:20
roaetagree.15:20
carl_baldwinI think that Sumit’s blueprint is the closest to where we want to start.  But, it doesn’t have much detail.15:20
roaetAs far as direction goes henceforth, I guess it's a matter of gathering more input on that very simple implementation and reviewing people's current implementation proposals?15:20
carl_baldwinYes.  We should probably submit a design specification to Neutron specs.15:21
*** salv-orlando has joined #openstack-meeting-315:22
carl_baldwinI’ll work on consolidating the existing blueprints.15:22
roaetI am not familiar with that step.15:22
roaetI assume it's documented somewhere, I"ll look around, but if you have it avail...15:22
*** Dseven has joined #openstack-meeting-315:22
carl_baldwin#action carl_baldwin to work with blueprint owners to consolidate.15:22
carl_baldwinThere is a wiki page.  Does anyone have the neutron-specs wiki page link on hand?15:23
salv-orlandocar;_baldwin: happy to help in defining design and or reviewing it15:23
carl_baldwinroaet: The whole process is very new.15:23
salv-orlandocarl_baldwin: ^^15:23
roaetsalv-orlando: i'd appreciate your input15:23
salv-orlandoAs with anything, two core-devs is better than one ;)15:23
carl_baldwinsalv-orlando: Great15:23
carl_baldwin#link https://wiki.openstack.org/wiki/Blueprints#Neutron15:24
roaeti found https://github.com/openstack/neutron-specs15:24
roaetoh, this is that thing voss was talking about. I'll need to ping people on the right way to do this.15:25
carl_baldwinroaet: Admittedly, there is a learning curve if you haven’t written RST but the whole process is a huge improvement over what we had before.15:25
carl_baldwinroaet: There is a very good sample document to start with.15:25
roaetI am a fan of rst, so I'll have that going for me.15:25
*** nati_ueno has quit IRC15:25
roaetcarl_baldwin: ok. I'll work on making that so it can be reviewed properly.15:26
carl_baldwin#action roaet to propose specification.15:26
carl_baldwinAnything else?15:26
roaetthat is it, thank you.15:26
carl_baldwinroaet: thank you.15:27
*** markmcclain has quit IRC15:27
carl_baldwin#topic rootwrap15:28
*** openstack changes topic to "rootwrap (Meeting topic: neutron_l3)"15:28
carl_baldwinI’ll give a quick update on this.15:28
carl_baldwinThere was a meeting in the oslo track about the rootwrap daemon mode.15:28
carl_baldwinThey did not have any reason not to go forward with the daemon mode implementation by YorikSar.15:29
carl_baldwinA few of them will review the blueprints and provide feedback on the implementation.15:29
carl_baldwinI probably won’t have this subject on the agenda past today.  Bookmark the topic in gerrit and review it.15:31
carl_baldwin#link https://review.openstack.org/#/q/topic:bp/rootwrap-daemon-mode,n,z15:31
salv-orlandocan we then integrate it smoothly in neutron or do you think we will need to adapt some modules?15:31
carl_baldwinsalv-orlando: Good question.  That was a point of discussion at the summit.15:32
carl_baldwinYuriy has proposed some code that integrates it.15:32
carl_baldwinsalv-orlando: You’ll find the proposal in the topic linked ^15:32
salv-orlandook great. thatconcludes the discussion then, I think15:33
*** mdorman has joined #openstack-meeting-315:33
carl_baldwinsalv-orlando: It may be a little behind the discussion.15:34
salv-orlandocarl_baldwin: that's ok, I meant the discussion here, in this meeting15:34
carl_baldwinThe general sentiment was that probably more of the integration could be implemented in oslo than neutron.15:34
carl_baldwinOh, I see.15:34
salv-orlandobeing the point of contact between oslo and neutron I should probably look at that :/15:35
carl_baldwinPlease do.  It will be greatly appreciated.15:35
carl_baldwinSwami: ping15:36
carl_baldwin#topic neutron-ovs-dvr15:36
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:36
carl_baldwinI don’t see Swami around.15:36
carl_baldwinI do know that work on DVR is moving along and picking up.  I grabbed a few nodes in our development environment and I’m currently in the process of building up my own little DVR deployment.15:37
nextone92Is there a way to run DVR on devstack?15:38
carl_baldwinnextone92: I plan to start with devstack.15:38
*** jamie_h has quit IRC15:38
carl_baldwinI don’t see any reason why it shouldn’t and it needs to.15:39
carl_baldwinI’ll admit I haven’t run a multi-node devstack yet.15:39
*** Swami has joined #openstack-meeting-315:40
nextone92Great!15:40
carl_baldwinA colleague sitting next to me has and is willing to share his experience with me.15:40
carl_baldwinThe setup will help with DVR and with VRRP which I’ve been meaning to test out as well.15:40
carl_baldwinI will document what I learn through the process for the next meeting.15:41
carl_baldwinSwami: hi15:41
Swamihi15:42
Swamicarl: Am I too late for the dvr update15:42
carl_baldwinWe were just discussing running DVR in devstack.15:42
Swamigood topic15:43
carl_baldwinYou’re not too late.  I’ve been saving DVR until the end because I know you can’t join early.15:43
Swamiwe need to have a multinode setup to run the DVR in devstack15:43
*** jamie_h has joined #openstack-meeting-315:43
carl_baldwinSwami: I have carved out time to try this out and document it for the community.15:43
SwamiI am planning to put together a Wiki to run multinode setup with the DVR15:43
carl_baldwin#action carl_baldwin to document experience getting DVR going with devstack in a multi-node configuration.15:44
Swamicarl: Do you have a workable config that runs devstack in multinode setup right now.15:44
carl_baldwinSwami: I will be glad to help out.15:44
Swamicarl: thanks15:44
carl_baldwinSwami: I’m part way through.  I’ve just identified some nodes in our dev environment to do it on and I’ve installed the base OS.15:44
Swamiwho ever first attempts it can provide information15:45
carl_baldwinSwami: Will you create a wiki page stub so that we can have a URL to collaborate on?15:45
SwamiI got a config file from Kyle for mulitnode setup I will forward it to you15:45
SwamiYes I do have a Wiki already. I will post the link15:45
carl_baldwinGreat.15:46
Swami#link https://wiki.openstack.org/wiki/Neutron/DVR/HowTo15:46
SwamiYou can use this place to update your findings15:46
carl_baldwinI will, thanks.15:46
carl_baldwinSwami: How was the DVR meeting yesterday?15:47
*** beyounn_1 has joined #openstack-meeting-315:47
Swamiit went well.15:48
SwamiI think you left during the services discussion15:48
*** rgbkrk has joined #openstack-meeting-315:48
SwamiWe had some discussion about where to handle the FWaaS for the DVR scenario.15:48
carl_baldwinYes.  Sorry to bug out.15:48
SwamiI have asked Yiun to come up with his ideas to apply the FWaaS for the DVR. Vivek and Rajeev also provided some ideas.15:49
SwamiWe will be capturing those ideas in the coming week and will probably walk through.15:49
SwamiWe also discussed about the VPNaaS and its impact.15:49
SwamiRight now there might not be too much impact for the VPN, just some code refactoring to schedule the VPN Service in the Service Node when associated with the DVR router.15:50
SwamiThis week our main focus is to fix all the broken Unit tests by the introduction of the DVR15:50
Swamiit affects many plugins out there and we are cherry picking and fixing it.15:51
carl_baldwinSwami: I did get your email about that.15:51
carl_baldwinIt can be labor intensive to fix unit tests.15:51
SwamiYes, you are right.15:52
SumitNaiksatamSwami: regarding fwaas, we also have DVR as a standing item on our FWaaS meeting15:52
SwamiSumitNaiksatam: Yes Yiun mentioned that he will take it up to the FWaaS team.15:52
carl_baldwinSumitNaiksatam: what are your thoughts overall?15:52
SumitNaiksatamSwami: if you get a chance, you can chime in that discussion as well, just to reinforce the discussion here15:52
SwamiSumitNaiksatam: Sorry I missed yesterday's meeting since I was busy with other work. I will chime in15:53
SumitNaiksatamcarl_baldwin: we dont have a clear solution yet15:53
SumitNaiksatamcarl_baldwin: we are sifting through the options15:53
SumitNaiksatamSwami: no worries at all, just a suggestion15:53
SwamiSumitNaiksatam: Thanks for accomodating the DVR/FWaaS requirements15:54
carl_baldwinSumitNaiksatam: Is the major concern that routing for each direction of east/west traffic is done on a different node and therefore cannot share state?15:54
SumitNaiksatamcarl_baldwin: yes15:54
carl_baldwinAre there other concerns?15:55
SumitNaiksatamnot that i am aware of at this point15:55
carl_baldwinSumitNaiksatam: Thank you.15:55
*** mestery has joined #openstack-meeting-315:55
SumitNaiksatami have also requested Yi to start an email thread on this15:55
SumitNaiksatamon the dev mailer15:55
*** mestery has quit IRC15:56
carl_baldwinSumitNaiksatam: Great.15:56
SumitNaiksatamcarl_baldwin: sure15:56
SwamiSumitNaiksatam: Thanks sumit15:56
*** mestery has joined #openstack-meeting-315:56
SumitNaiksatamSwami: np15:56
carl_baldwinFYI, FWaaS meetings are on Wednesdays at 1830 UTC in this meeting room.15:56
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/FWaaS15:56
carl_baldwinI will put it on my calendar.15:56
*** garyduan has joined #openstack-meeting-315:57
carl_baldwinSwami: anything else?15:57
*** gduan has quit IRC15:57
SwamiThat's all I had carl.15:57
*** xuhanp has quit IRC15:57
carl_baldwinSwami: thanks15:58
carl_baldwin#topic General Discussion15:58
*** openstack changes topic to "General Discussion (Meeting topic: neutron_l3)"15:58
carl_baldwinOne minute left.  ;)15:59
*** lcheng_ has joined #openstack-meeting-315:59
*** rgbkrk has quit IRC15:59
carl_baldwinThanks everyone!  Have a great week.16:00
carl_baldwin#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu May 22 16:00:10 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-05-22-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-05-22-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-05-22-15.00.log.html16:00
*** gduan has joined #openstack-meeting-316:00
Swamibye16:00
*** Swami has left #openstack-meeting-316:00
pcm__bye16:01
*** pcm__ has left #openstack-meeting-316:01
*** garyduan has quit IRC16:02
*** rockyg has joined #openstack-meeting-316:02
*** samchoi has joined #openstack-meeting-316:02
*** mdorman has left #openstack-meeting-316:04
*** rockyg has left #openstack-meeting-316:06
*** busterswt has joined #openstack-meeting-316:07
*** rgbkrk has joined #openstack-meeting-316:07
*** nextone92 has quit IRC16:10
*** eghobo has joined #openstack-meeting-316:13
*** nati_ueno has joined #openstack-meeting-316:14
*** mwagner_lap has joined #openstack-meeting-316:19
*** mestery has quit IRC16:27
*** kenhui has joined #openstack-meeting-316:28
*** mestery has joined #openstack-meeting-316:30
*** rgbkrk has quit IRC16:32
*** nacim has quit IRC16:39
*** garyduan has joined #openstack-meeting-316:43
*** gduan has quit IRC16:44
*** rudrarugge has joined #openstack-meeting-316:44
*** mestery has quit IRC16:45
*** coolsvap|afk is now known as coolsvap16:45
*** lcheng_ has quit IRC16:46
*** safchain has quit IRC16:48
*** gduan has joined #openstack-meeting-316:50
*** garyduan has quit IRC16:50
*** markmcclain has joined #openstack-meeting-316:52
*** markmcclain1 has joined #openstack-meeting-316:54
*** markmcclain1 has quit IRC16:54
*** markmcclain1 has joined #openstack-meeting-316:54
*** markmcclain has quit IRC16:57
*** ewindisch has joined #openstack-meeting-316:57
*** sarob has joined #openstack-meeting-316:58
*** nati_ueno has quit IRC16:59
*** rudrarug_ has joined #openstack-meeting-316:59
*** rgbkrk has joined #openstack-meeting-316:59
*** praveen_dell has joined #openstack-meeting-317:00
*** sarob_ has joined #openstack-meeting-317:00
*** rudrarugge has quit IRC17:01
*** nati_ueno has joined #openstack-meeting-317:01
*** sarob has quit IRC17:02
*** sarob_ has quit IRC17:03
*** sarob has joined #openstack-meeting-317:03
*** nati_ueno has quit IRC17:04
*** nati_ueno has joined #openstack-meeting-317:05
*** rudrarug_ has quit IRC17:06
*** nati_ueno has quit IRC17:06
*** dkorn has quit IRC17:06
*** nati_ueno has joined #openstack-meeting-317:06
*** rockyg has joined #openstack-meeting-317:08
*** catherine|2 has joined #openstack-meeting-317:08
rockygo/17:08
catherine|2Hello17:09
ewindischo/17:09
ewindischI’m presuming the meeting isn’t happening at 9 after17:09
praveen_dellHello all17:10
*** catherine|3 has joined #openstack-meeting-317:10
*** jcoufal has quit IRC17:11
rockygI think I was on at 9, but nobody else was.  My calendar alerted at 1017:12
catherine|3so we change the time?17:12
*** rgbkrk has quit IRC17:12
*** waiman has joined #openstack-meeting-317:13
*** catherine|2 has quit IRC17:14
*** rgbkrk has joined #openstack-meeting-317:14
rockygdon't know ping some folks on refstack channel17:15
davidlenwellhey .. we have room cross over17:15
davidlenwellsorry17:15
davidlenwellmy fault17:15
davidlenwellI started things in alt17:16
rockygoh.17:16
*** waiman has quit IRC17:17
davidlenwelllets all migrate there I guess17:17
praveen_dellwhere?17:17
praveen_dellmigrate to refstack?17:17
davidlenwell#openstack-meeting-alt17:17
praveen_dellokay,thanks17:17
rockygi'm there17:17
*** rockyg has left #openstack-meeting-317:19
*** kenhui has quit IRC17:19
*** rgbkrk has quit IRC17:24
*** yamahata has quit IRC17:24
*** yamahata has joined #openstack-meeting-317:25
*** rgbkrk has joined #openstack-meeting-317:29
*** catherine|3 has left #openstack-meeting-317:30
*** nati_ueno has quit IRC17:30
*** nati_ueno has joined #openstack-meeting-317:30
*** chuckC has quit IRC17:31
*** tedchang has joined #openstack-meeting-317:35
*** tedchang has quit IRC17:37
*** lcheng_ has joined #openstack-meeting-317:38
*** igordcard has joined #openstack-meeting-317:38
*** SumitNaiksatam has quit IRC17:39
*** anil_rao has joined #openstack-meeting-317:40
*** anil_rao has quit IRC17:40
*** praveen_dell has quit IRC17:48
*** chuckC has joined #openstack-meeting-317:48
*** regXboi has joined #openstack-meeting-317:50
*** SumitNaiksatam has joined #openstack-meeting-317:51
*** rkukura has joined #openstack-meeting-317:53
*** rgbkrk has quit IRC17:53
*** rudrarugge has joined #openstack-meeting-317:54
*** mandeep has joined #openstack-meeting-317:55
*** lcheng_ has quit IRC17:57
*** prasadv has joined #openstack-meeting-318:00
SumitNaiksatamhello Neutron folks!18:00
*** tomoe_ has quit IRC18:00
prasadvSumitNaiksatam: hello18:00
banixhi SumitNaiksatam prasadv18:00
*** s3wong has joined #openstack-meeting-318:00
*** marun has joined #openstack-meeting-318:00
SumitNaiksatamprasadv banix: hi18:00
banixhi everybody18:00
marunhi18:00
regXboione time I'm not actually pre-empted18:01
s3wonghello18:01
banixhi regXboi18:01
SumitNaiksatamgive another minute and we can get rolling18:01
banixhi mandeep18:01
banixhi marun s3wong18:01
*** hemanthravi has joined #openstack-meeting-318:01
*** thinrichs has joined #openstack-meeting-318:01
SumitNaiksatamok lets get started18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu May 22 18:01:59 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: networking_policy)"18:02
openstackThe meeting name has been set to 'networking_policy'18:02
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy18:02
*** ewindisch has left #openstack-meeting-318:02
*** OSM has joined #openstack-meeting-318:02
mandeepbanix: Hi18:02
SumitNaiksatamfirstly, thanks to everyone for the participation in the during the summit18:02
SumitNaiksatammore so to the team which actually worked on the PoC, great effort in pulling it together across projects in record time18:03
rkukurahi18:03
SumitNaiksatamneedless to say, it was very well received18:03
*** sarob has quit IRC18:04
marunuh18:04
mandeepGreat work by SumitNaiksatam rkukura hemanthravi prasadv ronak rudrarugge18:04
s3wongyes, it was. banix, SumitNaiksatam, and me were mobbed after the presentation18:04
SumitNaiksatams3wong: true18:04
banixi think it is fair to say the public at large was very supportive of the direction18:04
mandeepbanix: Yes, I was viewing the presentation - very well done banix s3wong and SumitNaiksatam18:05
banixthat is the need for policy abstractions18:05
marunI've sent an email to os-dev that paints a somewhat contradictory viewpoint.18:05
SumitNaiksatamokay to the first topic on the agenda18:05
mandeep(and I should have added banix and s3wong to my last list ;-)18:05
mandeepWhen did you send it marun18:05
marunjust now I'm afraid.18:05
mandeepI did not see that18:05
mandeepOK18:05
SumitNaiksatamok lets follow the agenda items18:06
*** roaet has left #openstack-meeting-318:06
s3wongmarun: really?18:06
SumitNaiksatamso that we can get all items covered18:06
marunI've added an item to the end of the agenda to discuss.18:06
banixmarun: we are mainly referring to the need for policy abstractions and not specifically a particular model and approach etc18:06
marunso yes, let's move on.18:06
SumitNaiksatammarun: good18:06
mandeepAs it is just seconds before the meeting, we can not discuss to that I guess.18:06
SumitNaiksatami will just go based on the order currently in the agenda18:06
SumitNaiksatam#topic Change of weekly meeting time18:06
*** openstack changes topic to "Change of weekly meeting time (Meeting topic: networking_policy)"18:07
regXboibanix added that at my request18:07
SumitNaiksatami thought we had good consensus on this time/day?18:07
mandeepYes18:07
SumitNaiksatamregXboi: ah ok18:07
*** mickey_spiegel has joined #openstack-meeting-318:07
mandeepWe finally got the meeting slot!18:07
regXboiproblem is that this overlaps with the ODL TSC which is 2 hours18:07
banixconflicting with TCM at ODL18:07
SumitNaiksatamregXboi: actually we bounced off a few meetings times in the past18:07
banixTSC18:07
regXboiand several of the TSC members (myself included) are obligated to that18:07
regXboiand can't participate in this18:08
SumitNaiksatamand it was difficult to find an open openstack channel18:08
mandeepregXboi: We have tried quite a few slots and this is already the 3rd or 4th attempt18:08
mandeepI would rather not chnage it again, if possible18:08
s3wongSumitNaiksatam: perhaps pushing it earlier? I have a three hours slot between LBaaS and GP18:08
regXboimandeep: you are basically saying to TSC folks that are also working ODL GBP "go away"18:08
regXboibut, I understand the problem with finding a good time18:09
banixregXboi: Starting one hour later would work?18:09
SumitNaiksatamregXboi: we should definitely try to accomodate every one to the extent possible18:09
regXboistarting one hour later would work18:09
mandeepMy morniong is also filled up, then I guess I will go away?18:09
s3wongregXboi: I simply stopped attending the TSC meeting - but I can see you wouldn't be able to do that, as a TSC member :-)18:09
banixSumitNaiksatam: any chance we switch fwaas and this one?18:09
prasadvone hour later will not work for ODL GBP folks18:09
banixif others are ok with it that is18:10
regXboium18:10
regXboiyes it will18:10
s3wongprasadv: correct, I suggested earlier18:10
*** nati_ueno has quit IRC18:10
prasadvs3wong: earlier works18:10
regXboiis this a 60 minute or a longer irc?18:10
SumitNaiksatambanix: if we replace with fwaas, we will have two back-to-back heavy meetings (the former one is advanced services)18:11
SumitNaiksatamregXboi: this meeting is 60 min18:11
regXboiif it's 60 minutes, there is a window between the end of this slot and the GBP ODL18:11
regXboier ODL GBP18:11
banixSumitNaiksatam: yeah confused the dates18:11
regXboiand to mandeep's point - I can't go earlier in the day18:11
regXboiI'm blocked solid until when this slot ends18:11
mandeepAnd I know that prasadv and hemanthravi travel after this call to the ODL call18:12
regXboiah18:12
regXboitravel is an issue18:12
prasadvwe travel to the meeting most of the time18:12
regXboiI'm remote to all of them...18:12
s3wongregXboi: travel as in 10 minutes drive :-)18:12
banixprasadv: you are very dedicated :)18:12
regXboilonger than sub-minute irc->hangout/webex flip18:12
*** jamie_h has quit IRC18:12
SumitNaiksatamokay, so lets bounce off some times off line18:12
SumitNaiksatamregXboi: any chance the ODL meeting can be moved?18:13
regXboisure... in the meantime, I can load up banix18:13
*** LouisF has joined #openstack-meeting-318:13
regXboiSumitNaiksatam: no18:13
SumitNaiksatamregXboi: being optimistic :-)18:13
regXboiit's a 2-hour slot18:13
*** nbouthors has joined #openstack-meeting-318:13
banixregXboi: np; will try to find a better time.18:13
regXboithanks all18:13
SumitNaiksatam#topic PoC status update18:13
*** openstack changes topic to "PoC status update (Meeting topic: networking_policy)"18:13
SumitNaiksatamso while we achieved most of what we set out to do for the PoC, there were a few loose ends18:14
SumitNaiksatamour patches are in review in gerrit, but some people in the team will continue to focus on tying those loose ends18:15
SumitNaiksatamrkukura s3wong you want to fill on that?18:15
regXboithose loose ends being?18:15
SumitNaiksatamregXboi: on cue ^^^ :-18:15
s3wongrkukura: want to go first?18:15
* regXboi can play the straight person18:15
rkukurasure18:15
rkukuraWe had hoped to get the PoC to the point where the mapping driver was setting up neutron security groups to actually enforce some policy rules, but did not get that far.18:16
LouisFany work planned for redirect action?18:17
rkukuraRight now, the mapping driver manages the neutron networks, subnets, port, and routers, with all access allowed. The security groups would let us deny traffic that is not explciity allowed.18:17
s3wongLouisF: that's me. It will be next after ruukura :-)18:17
*** terryw has quit IRC18:17
banixLouisF: hi Louis, good to see you here18:18
rkukuraThere are also some issues with allocating subnets from withint the RD’s supernet that need fixing.18:18
LouisFgood to meet at summit18:18
rkukuraSo I thinkk it makes sense to continue to work towards these goals in the PoC/github code base in parallel with the work to merge lower layers to neutron’s repository.18:19
*** jcoufal has joined #openstack-meeting-318:19
s3wongrkukura: my turn?18:19
SumitNaiksatamrkukura: thanks18:19
rkukuraSumitNaiksatam: Did you want me to mention some of the design changes we’ve been thinking about for the driver and driver API?18:20
rkukuraor is that later?18:20
*** sarob has joined #openstack-meeting-318:20
s3wongOK - for the PoC, due to ease of unit testing and several pieces absence during my time of integration test, the redirect action takes place upon policy-action creation18:20
SumitNaiksatamrkukura: thats a different agenda item18:21
s3wongwhich isn't the right place, so the first thing I will do for post-PoC is to move it to contract creation, where it belongs18:21
s3wongSecond, to properly do redirect to a service (UUID), we need ServiceBase Object support, whose bp is already in gerrit18:21
s3wongand coincidently, I (along with kanzhe) will be working on that18:22
s3wongso to implement 'redirect' action properly on the mapping driver, that ServiceBase effort is a bit of a dependency18:22
LouisFwill ServiceBase be added to the POC branch?18:22
*** OSM is now known as songole18:23
SumitNaiksatamLouisF: service base is intended to get the adavanced services framework going18:23
SumitNaiksatamLouisF: so it has applicability beyond group policy18:23
s3wongLouisF: good question. In terms of checking in, the 'redirect' mapping driver part will obviously be after the ServiceBase work18:23
SumitNaiksatamLouisF: hopefully that will go in soon18:23
s3wongin terms of PoC branch, I think porting it there for unit testing purpose makes sense18:23
songoles3wong: is the redirect action specified on a rule or inside contract?18:24
s3wongbut won't be part of the check-in, of course18:24
s3wongsongole: redirect action, like all actions, is part of policy-rule18:24
banixsongole: rule18:24
*** rudrarugge has quit IRC18:24
s3wongthat's it for me18:24
SumitNaiksatams3wong: ok thanks18:25
SumitNaiksatamany questions for rkukura or s3wong in terms of the above update?18:25
songoles3wong: got it. thanks18:25
SumitNaiksatam$topic Gerrit reviews18:26
LouisFwhat branch is ServiceBase work on?18:26
rkukuraSumitNaiksatam: use #topic18:26
SumitNaiksatamPolicy Model: #link  https://review.openstack.org/#/c/9385318:26
s3wongLouisF: kanzhe and I will fork from Neutron to work on it - we are working on that now18:26
SumitNaiksatamMapping Driver #link https://review.openstack.org/#/c/9393518:26
SumitNaiksatam#topic  Gerrit reviews18:27
*** openstack changes topic to "Gerrit reviews (Meeting topic: networking_policy)"18:27
SumitNaiksatamrkukura: thanks :-)18:27
SumitNaiksatamabove links dont change18:27
s3wongLouisF: if you are interested, please join us at the advanced service IRC meeting Wed 17:30 UTC on #openstack-meeting-318:27
SumitNaiksatamso the first patch only has two resources now, and is the first in a series18:28
SumitNaiksatamthe second patch is WIP, and is waiting for a few more patches to land on the model side18:28
LouisFhmm nobody on channel yesterday18:28
SumitNaiksatambut the second patch should give a good idea about the mapping driver implementation18:28
*** sarob has quit IRC18:28
SumitNaiksatamhopefully you all can review and provide constructive feedback18:29
rkukuraThe 2nd will also be broken up into smaller patches when its dependencies are ready18:29
s3wongLouisF: really? I was there yesterday, as were SumitNaiksatam, banix, kanzhe, rkukura, and many others...18:29
SumitNaiksatamrkukura: thanks18:29
*** jcoufal has quit IRC18:29
SumitNaiksatamLouisF: yes, we had the meeting yesterday (was a full house)18:29
*** jcoufal has joined #openstack-meeting-318:30
SumitNaiksatamany thoughts questions on the gerrit patches in review?18:30
banixwe are trying to breakdown the patches to smaller pieces so the review process is easier; is this being helpful?18:31
regXboiI'll admit that I'm late to the party18:31
SumitNaiksatambanix: yeah good point18:31
*** rudrarugge has joined #openstack-meeting-318:32
SumitNaiksatamok perhaps it is helpful, since no counter opinions18:32
SumitNaiksatam#topic Mapping driver18:32
*** openstack changes topic to "Mapping driver (Meeting topic: networking_policy)"18:32
*** lcheng_ has joined #openstack-meeting-318:32
*** sarob has joined #openstack-meeting-318:32
SumitNaiksatamso rkukura wanted to spend a little bit of time on some the discussions around this topic18:33
rkukuraok18:33
SumitNaiksatamrkukura: i believe you had a few items on the agenda18:33
markmcclain1SumitNaiksatam: had to step away for sec, but do have questions on the reviews18:34
SumitNaiksatam#undo18:34
rkukuraOne question that came up during PoC implementation was whether the code that implicitly creates BDs and RDs when they are not passed in explicitly might not really be specific to the mapping driver, so maybe it should go in the plugin itself.18:34
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x380fe90>18:34
SumitNaiksatamrkukura: one sec18:34
SumitNaiksatammarkmcclain1: go ahead18:34
markmcclain1SumitNaiksatam: even with the smaller patches it is impossible to review because the code series doesn't actually work18:35
SumitNaiksatammarkmcclain1: not quite sure, what you mean by code series doesnt actually work?18:35
mandeepmarkmcclain1: Please explain.18:35
rkukuraSumitNaiksatam, markmcclain1: Unit tests should pass, right?18:36
SumitNaiksatamrkukura: yes they do18:36
markmcclain1functionally it should work18:36
markmcclain1UT should pass per chunk18:36
SumitNaiksatammarkmcclain1: there is only patch in the series right now18:36
mandeepAnd the entire policy can not be made to work with out all the policy objects being in place18:36
SumitNaiksatammarkmcclain1: not sure what your expectation is18:36
mandeepAs requested by marun the patches are being split by resources18:36
SumitNaiksatammarkmcclain1: an entire functional patch was posted18:36
SumitNaiksatammarkmcclain1: you refused to review it18:37
SumitNaiksatammarkmcclain1: becuause you wanted it broken down18:37
marunSumitNaiksatam: I pointed out why it was a problem weeks ago.18:37
SumitNaiksatammarkmcclain1: you got that18:37
mandeepSo the patches are now split18:37
markmcclain1but I should be able to grab the last in a series and actually run the extension and see changes to datapath18:37
SumitNaiksatammarkmcclain1: there is only in the series18:37
rkukuraWe’re breaking it up both by layers and by resources18:37
SumitNaiksatammarkmcclain1: the others are coming18:37
markmcclain1right the nice thing about breaking into patches is that code can be reviewed in chunks18:37
markmcclain1but for functional testing the end result can be run18:38
SumitNaiksatammarkmcclain1: sure, so you want that all patches be posted before you start reviewing?18:38
mandeepAnd we do not expect you to approve the patches until they fit together in a function chunk18:38
markmcclain1yes otherwise we're just looking at one tree at a time to figure out what the forrest looks like18:38
rkukuraThat sounds nice in theory, but would basically force doing all the development outside the OpenStack gerrit environment, wouldn’t it?18:39
marunrkukura: Quite the opposite18:39
mandeepBut the "tree" can be inspected for code issues and UTs etc18:39
SumitNaiksatammarkmcclain1: yes, exactly for that reason there is also a PoC branch that be pulled and tested in entirety18:40
*** chuckC has quit IRC18:40
mandeepSumitNaiksatam: exactly18:40
*** rgbkrk has joined #openstack-meeting-318:40
markmcclain1gerrit will sequence the commits correctly18:40
*** chuckC has joined #openstack-meeting-318:40
banixso i think we agree that the code will be rather large. So the question is how best we go about doing this in steps so the review can be done effectively.18:41
SumitNaiksatammarkmcclain1: absolutely18:41
mandeepmarkmcclain1: Can I request that we chnage the discussion on - how can we make progress on it vs. why it can not work the way it is?18:41
marunAs per my email, there is some question as to whether the proposed approach is actually the way forward in the short term.18:41
rkukuraThere is a lot of boilerplate and common patterns involved. We’ve been hoping to get closure on these on a small subset of resources, before putting all the othe resources into review. This seems to be a lot more efficient use of reviewers’ time.18:41
mandeepmarun: I can not discuss that without having read it.18:42
marunthen go read it.18:42
SumitNaiksatamrkukura: thats a good point18:42
mandeepI will. After this IRC18:42
*** lcheng_ has quit IRC18:42
marunsure.  then you won't be able to actually speak to my points.18:42
marunI started participating late in the game, and if i had known there was a simple approach, I would have pushed for it.18:42
mandeepI will respond on the ML18:42
markmcclain1rkukura: you're right there is boilerplate18:42
banixmarun: yes, just read your email: #link http://lists.openstack.org/pipermail/openstack-dev/2014-May/035666.html18:42
*** alexpilotti has joined #openstack-meeting-318:42
marun'the simplest thing that can possibly work' is generally the best thing.18:42
prasadvmarun: can we discuss one topic at a time.. first can we resolve checkin and resolution process18:43
SumitNaiksatamfor anyone who actually read through the patch, it is indeed very boilerplate18:43
marunespecially when pushing new initiatives.18:43
markmcclain1but the whole reason we started requiring implementations with APIs was because the lbaas API was so terrible18:43
markmcclain1nobody really noticed until they tried to use it18:43
mandeepYes, I want to avoid religious discussions as well.18:43
mandeepLet us focus on how to structure the checkin18:43
SumitNaiksatamokay, so let me stop this topic here18:44
SumitNaiksatami think the expectation for some of the reviewers is that more patches land18:44
marunmandeep: To be blunt, the question that needs to be answered is 'are we solving the right problem'18:44
SumitNaiksatambefore they get a better feel18:44
marunRather than 'are we solving the problem right'18:44
mandeepmarun: We can discuss that independly of what the questions are on the current check-in18:44
SumitNaiksatamso lets do that (which I believe was the plan any way)18:44
SumitNaiksatammarkmcclain1: does the address your concern as well?18:44
mandeepmarun: So that later if you undertsand that what we are doing is correct we would not have wasted time18:45
*** chuckC has quit IRC18:45
SumitNaiksatammarun mandeep: can i request you to hold your horses a bit18:45
mandeepSumitNaiksatam: OK18:45
SumitNaiksatamthere is a topic in the agena, we can take it up at that time18:45
banixare there horses here?18:45
banix:)18:45
mandeepSumitNaiksatam: But I would prefer to get an answer on how to strcutre the patches18:46
SumitNaiksatammandeep: i think we have agreement that patches are structured in the right way18:46
mandeepSumitNaiksatam: Do we have agreement on what would be acceptable18:46
SumitNaiksatammandeep: just that more patches need to land18:46
mandeepSumitNaiksatam: Cool18:46
markmcclain1SumitNaiksatam: yes ideally more functional units and if there is a logical way to separate them so that we don't get a series that's 20 deep that would be nice18:46
mandeepSumitNaiksatam: In that case, I am Ok to move on to the next phase18:46
SumitNaiksatammarkmcclain1: you can either have smaller chunks, and but more patches, or bigger chunks with less patches :-)18:47
SumitNaiksatammarkmcclain1: i believe you wanted smaller chunks, in a series18:47
markmcclain1I want both :)18:47
mandeepmarkmcclain1: Policy is a big item, you can not just solve a part of it18:47
SumitNaiksatammarkmcclain1: well you will need to teach us to bend the laws of physics then18:48
marunmandeep: no comment18:48
markmcclain1mandeep: fully aware.. just making sure that we have good items to test18:48
mandeepmarkmcclain1: Either that, or as a community we are not going to sign up to solving big problems18:48
markmcclain1the lbaas experience from 2 yrs ago still haunts18:48
rkukuramarkmcclain1: Would building things up like we did in the PoC effort help - getting first the to where the Endpoint and EndpointGroup resources can be used as an alternative to directly using neutron resources first, the adding policy/contract/enforcement to this, help?18:48
marunmandeep: there are more than 1 ways to skin a cat18:48
markmcclain1rkukura: that does seem like something that could prove workable18:49
markmcclain1ie a series that gets us to Endpoints/Groups18:49
mandeepmarun: I challenge you to show ONE real life policy based service deployment system that is "small"18:49
SumitNaiksatammarkmcclain1: ok we should be able to endpoints and groups in less than 20 patches :-)18:49
markmcclain1SumitNaiksatam: cool18:50
marunmandeep: I challenge you to find a single workable system that wasn't developed incrementally.18:50
marun(in open source)18:50
mandeepmarun: This has been developed incrementally - week after week - you joined the party late18:50
marunmandeep: incrementally outside of oversight18:50
SumitNaiksatamok good, i think we have good agreement on the current approach, we need to get to the point where we have the EP and EPG in review soon18:51
mandeepmarun: There was oversight18:51
marunmandeep: not from the wider neutron community18:51
SumitNaiksatamso we wil get to taht18:51
SumitNaiksatammarkmcclain1: sound okay?18:51
mandeepmarun:  the whole team worked on an open repo tigether18:51
rkukuramarun: There has been an official neutron subteam working on this during the entire icehouse cycle, reporting at the neutron IRC meetings18:51
markmcclain1SumitNaiksatam: from a review perspective yes18:51
marunmandeep: the fact that we're dealing with things like patch structure point to a failure to understand how to contribute to neutron18:51
mandeepmarun: With oversignt from multiple neutron cores18:51
SumitNaiksatamok moving back to the earlier topic18:51
SumitNaiksatam#topic Mapping driver18:52
*** openstack changes topic to "Mapping driver (Meeting topic: networking_policy)"18:52
marunnothing that can't be remedied, but pretending it's not a problem seems pretty silly18:52
mandeepmarun: You know better than other cores, obviously18:52
marunmandeep: really?18:52
markmcclain1SumitNaiksatam: thanks for indulging my review process questions18:52
rkukurathe PoC is just that, trying to prove some concepts before submitting code for formal review18:52
mandeepmarkmcclain1: Thanks for the clarification18:52
SumitNaiksatammarkmcclain1: always18:52
*** peristeri has quit IRC18:53
rkukuraback to the current topic…18:53
SumitNaiksatamrkukura: please18:53
rkukuraOne question that came up during PoC implementation was whether the code that implicitly creates BDs and RDs when they are not passed in explicitly might not really be specific to the mapping driver, so maybe it should go in the plugin itself.18:54
SumitNaiksatamrkukura: maybe a short summary, so that we can to get the other items as well18:54
*** rgbkrk_ has joined #openstack-meeting-318:54
rkukuraSo I’m looking into putting that into a separate driver that runs before the mapping driver.18:54
SumitNaiksatamrkukura: i like that idea18:55
s3wongrkukura: +118:55
regXboiso um hold18:55
SumitNaiksatamrkukura: will this be in the PoC branch?18:55
rkukuraWill also make a meaningful chunk for review ;)18:55
*** jcoufal has quit IRC18:55
regXboiI'm still a little unclear how bridge and router domains come into this discussion?18:56
s3wongrkukura: :-)18:56
*** rgbkrk has quit IRC18:56
SumitNaiksatamregXboi: that was the next topic on the agenda18:56
SumitNaiksatam#topic Resource name changes18:56
* regXboi plays straight man again18:56
*** openstack changes topic to "Resource name changes (Meeting topic: networking_policy)"18:56
regXboiok I can wait :)18:56
SumitNaiksatamregXboi: it seems that BD and RD names are causing a lot of confusion18:56
SumitNaiksatamand are being interpreted for what they are not18:57
rkukuraregXboi: These need to be their for the mapping driver to do its thing, but the APIs would used more from an application network admin role than an application deployer role.18:57
mandeepSumitNaiksatam: Propose change names to L3-policy-context and L2-policy-context18:57
regXboimandeep: +118:57
prasadvmandeep: +118:58
s3wongmandeep: +118:58
SumitNaiksatammandeep: yeah something like that will be good18:58
rkukuraSome risk of confusion around the work “context” since its used in the driver API (based on ML2’s similar pattern)18:58
SumitNaiksatamlets think a little more on this (since these are just meant to hold context attributes)18:58
SumitNaiksatamok moving on18:58
rkukuraBut L?PolicyContext is fine with me18:58
SumitNaiksatamwant to make sure give time for marun’s agenda item18:58
SumitNaiksatam#topic Summit session post-mortem18:59
*** openstack changes topic to "Summit session post-mortem (Meeting topic: networking_policy)"18:59
s3wong2 minutes? :-)18:59
SumitNaiksatamwe can go a little over unless we get kicked out18:59
marunarmax: has suggested on the ml thread to schedule an ad-hoc meeting to discuss18:59
SumitNaiksatam(but hopefully not a neverending debate)18:59
mandeeps3wong: I can sacrifice my luch to hear this18:59
*** rgbkrk_ has quit IRC18:59
armaxyeah just a minute is not gonna cut it18:59
armax:)18:59
marunAnd that would give folks a chance to read it.18:59
regXboiI'm in for the long haul18:59
banixsounds reasonable19:00
marunSo, no need to extend, we can schedule something later.19:00
mandeepSumitNaiksatam: Will you be scheduling this ad-hoc meeting?19:00
*** thinrichs has quit IRC19:00
SumitNaiksatamsure,19:00
regXboiand more to the point: "how" will the meeting get scheduled?19:00
SumitNaiksatamwe can have another meeting :-)19:00
marunI'm off tomorrow and all next week, but I'd suggest collecting participants from the ml thread and discussing the issues raised.19:00
regXboimarun: in that case, may I ask a q?19:01
marunshoot19:01
banixhow about continuing now?19:01
mandeepmarun: We need to resolve this issue ASAP, we can not put this off by a few weeks19:01
*** rgbkrk has joined #openstack-meeting-319:01
*** garyduan has joined #openstack-meeting-319:01
marunmandeep: completely agree.19:01
regXboiif the patches are restructured to build up to EP/EPG first (as discussed earlier)19:01
*** mestery has joined #openstack-meeting-319:01
banixif we have the room and the audiance, shall we proceed?19:01
marunmandeep: I'm raising issues, but I don't have to be involved.19:01
SumitNaiksatamwe are not getting kicked out yet19:02
*** gduan has quit IRC19:02
regXboidoes this meet your concern by providing a natural point to implement the simple model?19:02
marunmandeep: it's not my intention to hold anything up.19:02
*** beyounn has joined #openstack-meeting-319:02
SumitNaiksatamso i think we can hang in here for a little longer19:02
regXboier simple implementation I mean?19:02
*** beyounn_1 has quit IRC19:02
regXboisorry about the interleave :(19:02
SumitNaiksatamregXboi: yes, so will discussed that we will get to EP and EPG at the earliest19:02
s3wongso, I guess we should read marun 's email and armax 's response first?19:02
marunregXboi: can the simple implementation be done without the complex model?19:02
SumitNaiksatamregXboi: but again it need not be a suspense19:03
regXboimarun: I have to go back and look, but I believe so, banix?19:03
SumitNaiksatamregXboi: the PoC branch already has all of this19:03
mandeepI was not in the summit, but I guess this is rehash of the original discussion on link based vs. contract based policy from early this year19:03
marunyes19:03
banixregXboi: yes it can19:03
mandeepAnd that was discussed over at least 6 weeks in this forum before the current model was choosen19:03
SumitNaiksatamok let me level set here a little -19:03
regXboiI think it also involves the process point of deviating from the BP, no?19:04
mandeepThe blueprint has the current model in it.19:04
SumitNaiksatamlots of people are mistaking the optional parts of the model with what is required19:04
marunUh19:04
regXboimarun: Uh to whom?19:04
marunSumit: Do these optional parts have corresponding implementation?19:04
SumitNaiksatamwithout the optional parts it is indeed simple19:04
mandeepmarun: Yes19:05
SumitNaiksatammarun: to your earlier point, this is a phased/iterative implementation19:05
marunSumitNaiksatam: So would it be possible to propose _just_ the simple model as a starting point?19:05
marunSumitNaiksatam: rather than trying to do it all at once?19:05
SumitNaiksatammarun: that is what the current PoC implementation is19:05
mandeepmarun: We had a discussion on that as well19:05
marunmandeep: and we're discussing it again.19:05
marunSumitNaiksatam: I guess I find that surprising given the level of concern in the summit session at the complexity.19:06
mandeepmarun: And as long as people do not read those minutes, we will discuss it again19:06
SumitNaiksatammarun: that is the problem, i believe people are misunderstanding19:06
SumitNaiksatammarun: for instance you made claims about lack of simplicity, but i dont think you have read the docs or the code19:06
marunSumitNaiksatam: So the complexity of the proposed implementation doesn't reflect the complexity of the logical model involved?19:07
marunSumitNaiksatam: Maybe your definition of 'complexity' differ from mine.19:07
banixSo i think the question is if having an implementation based on the simpler model would be helpful as a first step19:07
banixis that fair to say?19:07
SumitNaiksatammarun: the team would hope that people make informed comments19:07
marunbanix: agreed.19:07
marunSumitNaiksatam: That cuts both ways, I'm afraid.19:07
mandeepSumitNaiksatam: What is robust is also fragile to a different set of constraints. Similarly what is simple is also complex for a different context.19:08
SumitNaiksatammarun: well you cant accuse those implementing, to be not informed about the code they write, right?19:08
s3wongbanix: but the problem we already have some level of implementation of the model, so it is basically changing the code to "simpler" model?19:08
marunmandeep: There is a need to socialize the concepts behind group policy to an audience of developers beyond this subteam.19:08
banixjust want to get an agreement as how we can move forward19:08
*** sarob has quit IRC19:08
marunmandeep: The way to do that is to implement something small and simple so that people can start to appreciate what you're trying to do.19:09
*** sarob has joined #openstack-meeting-319:09
marunmandeep: Front-ending the complexity is not a very good way to do this, imho.19:09
hemanthravii think the required subset of the contract model provides the simplicity of the other model19:09
SumitNaiksatammarun: plenty of that has happened, it is not constructive if you choose to focus only on the people who choose to be not in the loop19:09
SumitNaiksatammarun: by “that” i mean socialization19:09
LouisFthe "scoping" parts of the model do add complexity19:09
mandeepmarun: But if every change required a DB chnage and you deal with upgarde and back ward compatibility issues, you have just traded one complexity for anothert19:09
SumitNaiksatamLouisF: scopes are optional19:10
marunSumitNaiksatam: If you want to justify decisions made without consultation, that's certainly your choice.19:10
hemanthraviand it's better to model all the resources, else it will be harder to add these in later19:10
SumitNaiksatammarun: in fact quite the contrary19:10
banixi am wondering if we leave out the optionals, moving to simpler model would be much of coding. I am underestimating the work? or shall we have a complete functional system wih the current model without the optionals. that is another way forward.19:10
hemanthraviwe are already seeing this wrt to lbaas and the adv services efforts19:10
marunSumitNaiksatam: But I've yelled 'iterate in the open' so often it's getting boring, and I still don't think some of the folks in this room have heard me.19:10
SumitNaiksatammarun: the effort and work has been no secret, so there is no need to justify anything19:11
mandeepmarun: Incrementally chnaging resources happens when there is no architecture to put things together to begin with19:11
s3wongAgreed with hemanthravi here - the contract model with what we done in PoC so far is far from "complex" - it would be as "simple" as the link-based model19:11
LouisFSumitNaiksatam: agree19:11
marunmandeep: I call bs19:11
mandeepAnd it has all been open and with team participation19:11
prasadvmarun: the iteration was done in open19:11
marunno, it hasn't19:11
SumitNaiksatamok so let me level set again -19:11
mandeepmarun: I can call your feedback bs as well, but that is not the question here, is it?19:11
maruniterate would be - simplest thing that could possibly work.19:12
marunput it in gerrit and get it merged19:12
SumitNaiksatamthe spec captures the braoder model (including optional parts)19:12
marunthen start on the next piece19:12
s3wongmarun: IRC meeting, branch is public, link to branch on ML, what else can we do to make it more open?19:12
marunand make sure it's architecturally coherent at every step19:12
SumitNaiksatamthe simplest part is what we are implementing now and is a subset of the model19:12
SumitNaiksatamperhaps the optional pieces did not come out as clearly19:12
maruns3wong: ^^ iterate in the open -> propose patches, merge them, repeat19:12
maruns3wong: NOT iterate monolithically and then try to break things down19:13
mandeepThis was all done in open. It was all done iteratively19:13
*** sarob has quit IRC19:13
marunmandeep: ^^ uh, read what I just wrote19:13
banixlet’s focus on the way forward19:13
marunmandeep: _merge_ patches and then iterate19:13
mandeepThe repo used was in the minutes.19:13
mandeepThe team was comfortable using github as that is faster19:13
hemanthravithe current patch was needed to make it a functional block19:13
marunmandeep: merge -> gerrit.  not external repo19:14
banixwhat is the simplest yet meaningful set of patches we can have out for review19:14
mandeepmarun: Now were are discussing tools19:14
mandeepmarun: vs vs emacs?19:14
mandeepmarun: vi vs emacs?19:14
SumitNaiksatambanix: i think we have have already discussed that19:14
marunmandeep: nope.  I'm telling you what it takes to merge code to Neutron.  You're getting lost in the details .19:14
rkukuramarun: The PoC in github was intended as a learning exercise, and only lasted a couple weeks.19:14
banixemacs is the best!19:14
rkukurabanix: +119:14
*** rgbkrk has quit IRC19:14
*** rgbkrk has joined #openstack-meeting-319:15
mandeepAnd I use both. YMMV19:15
marunrkukura: fair enough.  so consider the poc as a prototype.  and then start iterating on doing it for real.19:15
marunrkukura: (in gerrit)19:15
mandeepmarun: That is precisely what we are doing19:15
rkukuramarun: That is exactly what we are trying to do19:15
marunmandeep: no, you're not.  you're breaking down the poc into chunks in the hopes of achieving a similar result19:15
marunmandeep: but there is likely to be commentary that will require changes.  I'm just setting your expectations so it's not 'i'm done, merge'19:16
mandeepmarun: I was involved in PoC, I am doing the reviews. When I say, that is what I was doing, I know it as I was doing it19:16
marunmandeep: I'm also pointing out that the review effort required is non-trivial, and Neutron has lots of other priorities.19:16
s3wongmanrun: OK - that's fair. We will revisit the PoC and start to iterate, instead of just breaking things in chunks19:16
SumitNaiksatams3wong: yes, that is what we are doing, hence the earlier items in the agenda today19:17
maruns3wong: +119:17
SumitNaiksatamgood so we have some level of agreement19:17
rkukuraI think we need to put some thought into how to build this thing up over a series of iterations in gerrit, not through continuing in the PoC codebase.19:17
s3wongmarun: but do keep in mind that there are workable code in the PoC also, and we will iterate those first19:17
marunrkukura: +119:17
banixrkukura: +119:18
SumitNaiksatameverybody happy calling it a wrap for today? :-)19:18
s3wongrkukura: yes, I think that is a good approach to get started19:18
banixso it looks like we are getting somewhwere :)19:18
marunSumitNaiksatam: +119:18
s3wongSumitNaiksatam: please :-)19:19
rkukuraWe can continue to use the PoC codebase to prototype, but the real code gets developed in step-by-step in gerrit19:19
regXboiSumit: I'll get with banix if the time slot doesn't move19:19
mandeepSumitNaiksatam: Good to see that we all agree on the process now19:19
SumitNaiksatamregXboi: sure19:19
*** igordcard has quit IRC19:19
SumitNaiksatamalrighty, thanks everyone19:19
marunYour collective participation in the ml thread is appreciated.19:19
s3wongmarun: sure19:19
*** prasadv has quit IRC19:19
marunAnd hopefully armax can help you organize any follow-up discussion.19:19
marunAs I said, I'll be off next week and I don't want to hold things up.19:20
mandeepSumitNaiksatam will organize it (it was above)19:20
SumitNaiksatammarun: so armax is your proxy? ;-)19:20
SumitNaiksatamand again, thanks for all the work, this is indeed very good progress19:20
armaxI'll be more involved, I hope markmcclain1 can be too19:20
marunFrom his reply on the ml I think he shares my concerns, so if you can satisfy him that should be fine.19:20
SumitNaiksatamgot it19:21
SumitNaiksatam#endmeeting19:21
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:21
openstackMeeting ended Thu May 22 19:21:11 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-22-18.01.html19:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-22-18.01.txt19:21
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-22-18.01.log.html19:21
armaxmarun: yes, even though my concerns were slightly on different notes19:21
*** songole has left #openstack-meeting-319:21
*** hemanthravi has quit IRC19:21
banixi actually think the concerns from marun markmcclain1 and armax were all a bit different19:22
marunarmax: I think the goal of high quality with as little effort as possible is the goal regardless, so I'll trust you to ensure that.19:22
armaxbanix: they are, but as marun said, we all share a common goal of doing what's right19:23
banixarmax: agree. the same here. Hopefully we’ll get there :)19:23
armaxbanix: I have no doubts we will19:23
*** alexpilotti has quit IRC19:27
*** LouisF has quit IRC19:28
*** regXboi has left #openstack-meeting-319:30
*** s3wong has quit IRC19:31
*** mandeep has quit IRC19:31
*** lenrow has joined #openstack-meeting-319:33
*** sarob has joined #openstack-meeting-319:33
*** TravT has quit IRC19:36
*** gduan has joined #openstack-meeting-319:39
*** garyduan has quit IRC19:41
*** gduan has quit IRC19:42
*** beyounn has quit IRC19:42
*** garyduan has joined #openstack-meeting-319:43
*** beyounn has joined #openstack-meeting-319:43
*** thomasem_ has joined #openstack-meeting-319:43
*** thomasem has quit IRC19:44
*** lblanchard has quit IRC19:45
*** lblanchard has joined #openstack-meeting-319:46
*** beyounn_1 has joined #openstack-meeting-319:47
*** gduan has joined #openstack-meeting-319:48
*** garyduan has quit IRC19:49
*** beyounn has quit IRC19:50
*** rgbkrk has quit IRC19:51
*** mickey_spiegel has quit IRC19:51
*** beyounn has joined #openstack-meeting-319:53
*** garyduan has joined #openstack-meeting-319:53
*** TravT has joined #openstack-meeting-319:53
*** beyounn_1 has quit IRC19:54
*** gduan has quit IRC19:54
*** rgbkrk has joined #openstack-meeting-319:59
*** mickey_spiegel has joined #openstack-meeting-320:00
*** mspiegel has joined #openstack-meeting-320:02
*** mickey_spiegel has quit IRC20:05
*** SumitNaiksatam has quit IRC20:06
*** SumitNaiksatam has joined #openstack-meeting-320:08
*** rkukura has left #openstack-meeting-320:11
*** jtomasek has quit IRC20:11
*** jtomasek has joined #openstack-meeting-320:13
*** gduan has joined #openstack-meeting-320:16
*** beyounn_2 has joined #openstack-meeting-320:16
*** garyduan has quit IRC20:18
*** beyounn has quit IRC20:19
*** kenhui has joined #openstack-meeting-320:28
*** sarob has quit IRC20:32
*** mwagner_lap has quit IRC20:33
*** lcheng_ has joined #openstack-meeting-320:34
*** sarob has joined #openstack-meeting-320:41
*** rgbkrk has quit IRC20:49
*** mspiegel has quit IRC20:56
*** alexpilotti has joined #openstack-meeting-320:59
*** sarob has quit IRC21:01
*** jtomasek has quit IRC21:01
*** yamahata has quit IRC21:02
*** boris-42 has quit IRC21:06
*** coolsvap is now known as coolsvap|afk21:08
*** boris-42 has joined #openstack-meeting-321:08
*** rudrarugge has quit IRC21:10
*** lcheng_ has quit IRC21:10
*** kenhui has quit IRC21:10
*** lcheng_ has joined #openstack-meeting-321:10
*** rgbkrk has joined #openstack-meeting-321:12
*** lcheng_ has quit IRC21:17
*** jpomero has quit IRC21:28
*** sarob has joined #openstack-meeting-321:29
*** Sukhdev has joined #openstack-meeting-321:32
*** sarob has quit IRC21:34
*** armax has left #openstack-meeting-321:38
*** nati_ueno has joined #openstack-meeting-321:40
*** mfer has quit IRC21:44
*** devlaps has quit IRC21:53
*** devlaps has joined #openstack-meeting-321:55
*** rgbkrk has quit IRC21:57
*** chuckC has joined #openstack-meeting-322:00
*** devlaps1 has joined #openstack-meeting-322:00
*** devlaps has quit IRC22:01
*** devlaps1 has quit IRC22:02
*** sarob has joined #openstack-meeting-322:02
*** sarob has quit IRC22:03
*** sarob has joined #openstack-meeting-322:03
*** sarob_ has joined #openstack-meeting-322:04
*** sarob_ has quit IRC22:04
*** sarob has quit IRC22:08
*** sarob_ has joined #openstack-meeting-322:08
*** nelsnelson has quit IRC22:08
*** rgbkrk has joined #openstack-meeting-322:10
*** jamielennox|away is now known as jamielennox22:11
*** boris-42 has quit IRC22:17
*** gduan has quit IRC22:18
*** david-lyle has quit IRC22:18
*** david-lyle has joined #openstack-meeting-322:18
*** david-lyle has quit IRC22:19
*** boris-42 has joined #openstack-meeting-322:20
*** garyduan has joined #openstack-meeting-322:21
*** nati_ueno has quit IRC22:25
*** nati_ueno has joined #openstack-meeting-322:25
*** chuckC has quit IRC22:27
*** mwagner_lap has joined #openstack-meeting-322:42
*** salv-orlando has quit IRC22:48
*** devlaps has joined #openstack-meeting-322:55
*** Youcef has joined #openstack-meeting-322:56
*** rgbkrk has quit IRC23:01
*** SumitNaiksatam has quit IRC23:04
*** chuckC has joined #openstack-meeting-323:06
*** rgbkrk has joined #openstack-meeting-323:19
*** rgbkrk has quit IRC23:19
*** SumitNaiksatam has joined #openstack-meeting-323:20
*** eguz has joined #openstack-meeting-323:20
*** rgbkrk has joined #openstack-meeting-323:20
*** eguz has quit IRC23:20
*** banix has quit IRC23:21
*** nati_ueno has quit IRC23:23
*** eghobo has quit IRC23:24
*** rgbkrk has quit IRC23:28
*** markmcclain1 has quit IRC23:29
*** markmcclain has joined #openstack-meeting-323:29
*** sarob_ has quit IRC23:29
*** Sukhdev has quit IRC23:32
*** sarob has joined #openstack-meeting-323:32
*** lcheng_ has joined #openstack-meeting-323:33
*** Youcef has quit IRC23:34
*** thomasem_ has quit IRC23:42
*** lcheng_ has quit IRC23:46
*** devlaps has quit IRC23:48
*** sarob has quit IRC23:59

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