Thursday, 2014-04-17

*** lblanchard has joined #openstack-meeting-300:00
*** mwagner_lap has joined #openstack-meeting-300:02
*** amrith is now known as amrith-gonzo00:04
*** sarob has quit IRC00:05
*** lblanchard1 has joined #openstack-meeting-300:05
*** sarob has joined #openstack-meeting-300:05
*** lblanchard has quit IRC00:08
*** cjellick has quit IRC00:08
*** sarob has quit IRC00:10
*** lblanchard has joined #openstack-meeting-300:49
*** lblanchard1 has quit IRC00:49
*** dstanek has joined #openstack-meeting-301:01
*** markmcclain1 has quit IRC01:11
*** eguz has quit IRC01:17
*** cgoncalv1s has joined #openstack-meeting-301:21
*** cgoncalves has quit IRC01:22
*** dstanek has quit IRC01:25
*** dstanek has joined #openstack-meeting-301:30
*** dstanek has quit IRC01:55
*** dstanek has joined #openstack-meeting-302:05
*** _sweston_ has quit IRC02:15
*** david-lyle has joined #openstack-meeting-302:17
*** dstanek has quit IRC02:19
*** dstanek has joined #openstack-meeting-302:23
*** lblanchard has quit IRC02:24
*** dstanek has quit IRC02:38
*** sweston has joined #openstack-meeting-302:56
*** beyounn has quit IRC03:05
*** lcheng has joined #openstack-meeting-303:11
*** dstanek has joined #openstack-meeting-303:27
*** dstanek has quit IRC03:33
*** lcheng has quit IRC03:44
*** banix has joined #openstack-meeting-303:59
*** banix has quit IRC04:05
*** lcheng has joined #openstack-meeting-304:05
*** lcheng has quit IRC04:27
*** banix has joined #openstack-meeting-304:32
*** eghobo has joined #openstack-meeting-304:32
*** eghobo has quit IRC05:00
*** eghobo has joined #openstack-meeting-305:00
*** lcheng has joined #openstack-meeting-305:09
*** baojg has joined #openstack-meeting-305:23
*** baojg has quit IRC05:23
*** boris-42 has quit IRC05:24
*** baojg has joined #openstack-meeting-305:24
*** lcheng has quit IRC05:26
*** dstanek has joined #openstack-meeting-305:29
*** lblanchard has joined #openstack-meeting-305:34
*** dstanek has quit IRC05:34
*** lblanchard has quit IRC05:35
*** banix has quit IRC05:40
*** boris-42 has joined #openstack-meeting-305:44
*** jtomasek has joined #openstack-meeting-305:49
*** jcoufal has joined #openstack-meeting-305:52
*** baojg_ has joined #openstack-meeting-305:54
*** jcoufal has quit IRC05:56
*** baojg has quit IRC05:56
*** baojg_ has quit IRC05:57
*** baojg has joined #openstack-meeting-305:58
*** baojg has quit IRC06:09
*** baojg has joined #openstack-meeting-306:09
*** baojg has quit IRC06:11
*** baojg has joined #openstack-meeting-306:11
*** eghobo has quit IRC06:11
*** nacim has joined #openstack-meeting-306:20
*** baojg has quit IRC06:29
*** baojg has joined #openstack-meeting-306:30
*** baojg_ has joined #openstack-meeting-306:39
*** baojg has quit IRC06:42
*** nacim has quit IRC07:05
*** ttrifonov_zZzz is now known as ttrifonov07:17
*** lsmola has quit IRC07:34
*** MaxV has joined #openstack-meeting-307:36
*** mestery_ has joined #openstack-meeting-307:43
*** mestery has quit IRC07:45
*** enikanorov_ has quit IRC07:51
*** lpetrut has joined #openstack-meeting-307:54
*** amotoki has joined #openstack-meeting-307:56
*** lsmola has joined #openstack-meeting-307:58
*** lpetrut has quit IRC07:59
*** safchain has joined #openstack-meeting-308:03
*** nacim has joined #openstack-meeting-308:07
*** amotoki has quit IRC08:08
*** jcoufal has joined #openstack-meeting-308:20
*** enikanorov has joined #openstack-meeting-308:25
*** yamahata has joined #openstack-meeting-308:29
*** baojg_ has quit IRC08:40
*** baojg has joined #openstack-meeting-308:40
*** nacim has quit IRC08:48
*** nacim has joined #openstack-meeting-309:06
*** alexpilotti has joined #openstack-meeting-309:22
*** enikanorov has quit IRC09:29
*** enikanorov has joined #openstack-meeting-309:30
*** enikanorov has quit IRC09:41
*** enikanorov has joined #openstack-meeting-309:43
*** enikanorov has quit IRC09:48
*** enikanorov has joined #openstack-meeting-309:51
*** yamahata has quit IRC10:10
*** baojg_ has joined #openstack-meeting-310:12
*** baojg has quit IRC10:16
*** amotoki has joined #openstack-meeting-310:16
*** david-lyle has quit IRC10:35
*** enikanorov has quit IRC10:47
*** MaxV has quit IRC11:00
*** baojg_ has quit IRC11:01
*** mwagner_lap has quit IRC11:47
*** MaxV has joined #openstack-meeting-311:51
*** MaxV has quit IRC11:56
*** safchain has quit IRC11:58
*** MaxV has joined #openstack-meeting-312:09
*** safchain has joined #openstack-meeting-312:17
*** dstanek has joined #openstack-meeting-312:20
*** MaxV has quit IRC12:44
*** MaxV has joined #openstack-meeting-312:44
*** mestery_ is now known as mestery13:00
*** overlayer has joined #openstack-meeting-313:05
*** fungi has quit IRC13:20
*** xuhanp has joined #openstack-meeting-313:23
*** jpomero has joined #openstack-meeting-313:23
*** baojg has joined #openstack-meeting-313:27
*** peristeri has joined #openstack-meeting-313:32
*** mwagner_lap has joined #openstack-meeting-313:33
*** mfer has joined #openstack-meeting-313:33
*** fungi has joined #openstack-meeting-313:34
*** amrith-gonzo is now known as amrith13:44
*** banix has joined #openstack-meeting-313:46
*** banix has quit IRC13:51
*** banix has joined #openstack-meeting-313:55
*** mwagner_lap has quit IRC14:04
*** banix has quit IRC14:06
*** banix has joined #openstack-meeting-314:07
*** markmcclain has joined #openstack-meeting-314:08
*** yamahata has joined #openstack-meeting-314:08
*** markmcclain1 has joined #openstack-meeting-314:08
*** markmcclain1 has quit IRC14:09
*** markmcclain1 has joined #openstack-meeting-314:10
*** markmcclain1 has quit IRC14:10
*** markmcclain1 has joined #openstack-meeting-314:11
*** markmcclain has quit IRC14:12
*** markmcclain1 has quit IRC14:13
*** markmcclain has joined #openstack-meeting-314:14
*** jcoufal has quit IRC14:25
*** jcoufal has joined #openstack-meeting-314:25
*** jcoufal has quit IRC14:25
*** jcoufal has joined #openstack-meeting-314:25
*** banix_ has joined #openstack-meeting-314:27
*** banix has quit IRC14:28
*** banix_ is now known as banix14:28
*** mwagner_lap has joined #openstack-meeting-314:30
*** banix has quit IRC14:32
*** baojg has quit IRC14:32
*** baojg has joined #openstack-meeting-314:33
*** david-lyle has joined #openstack-meeting-314:37
*** carl_baldwin has joined #openstack-meeting-314:50
*** baojg has quit IRC14:50
*** baojg has joined #openstack-meeting-314:51
*** AndChat|112404 has joined #openstack-meeting-314:52
*** baojg has quit IRC14:55
*** otherwiseguy has joined #openstack-meeting-314:55
*** pcm__ has joined #openstack-meeting-315:00
carl_baldwinHi all.15:00
pcm__hi15:00
mesteryo/15:00
carl_baldwinAnother week has gone by...15:00
carl_baldwinHi mestery, pcm__15:00
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Apr 17 15:01:09 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
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
*** AndChat|112404 has quit IRC15:01
xuhanphello15:01
carl_baldwinThis week-end is the deadline to submit topics for the summit.15:01
*** AndChat|112404 has joined #openstack-meeting-315:01
carl_baldwin#link http://summit.openstack.org/15:02
*** nextone92 has joined #openstack-meeting-315:02
carl_baldwinI will submit a couple of topics as soon as I get approval to do so.  ;)15:02
carl_baldwinAny other announcements?15:03
carl_baldwin#topic ML3 / L3 Vendor plugins15:03
*** openstack changes topic to "ML3 / L3 Vendor plugins (Meeting topic: neutron_l3)"15:03
carl_baldwinAs discussed in the Neutron meeting on Monday, this is added to today's agenda.15:03
carl_baldwinI'm sure there are many thinking about this from different angles.15:04
carl_baldwinI'd like to start by asking you all what you hope to get out of this discussion.15:04
carl_baldwinFor me, I would like to hear some concrete use cases for this feature.  To get my gears turning.15:05
carl_baldwinI'd also like to know how we can use the time leading to the summit to prepare for a productive conversation.15:05
pcm__I have some w/what I see with VPN15:05
*** Hao has joined #openstack-meeting-315:06
pcm__Big one is that currently, a vendor (or alternate service driver) has no way to do validation before info is persisted.15:06
pcm__As a result, all that can be done is placing the resource in error state.15:07
carl_baldwinI see that you've started a blueprint on that.15:07
pcm__yes: https://blueprints.launchpad.net/neutron/+spec/l3-svcs-vendor-validation15:07
carl_baldwinAre you planning to submit a blueprint specification to gerrit?15:08
pcm__Yeah, just need to learn about what I need to do for that15:08
carl_baldwinBTW, the summit discussion topic is here:15:08
carl_baldwin#link http://summit.openstack.org/cfp/details/8115:08
carl_baldwinpcm__: Yes, there is a new learning curve with the new process.  I know from experience.  ;)15:09
carl_baldwinIt is worth learning though.  I think the new process is a big improvement.15:10
pcm__mestery: Will probably need some pointers on what to do there.15:10
*** peristeri has quit IRC15:10
mesterypcm__: Sure! Look here for starters: https://wiki.openstack.org/wiki/Blueprints#Neutron15:10
pcm__mestery: thanks15:10
mesterypcm__: If you have questions, please reach out. This is new for all of us. :)15:10
pcm__roger that15:10
carl_baldwinpcm__: I also found that checking out the new repository and making sure that tox runs in the directory is a good start.  There is a nice read me and a template.15:11
*** Swami has joined #openstack-meeting-315:11
pcm__carl_baldwin: cool. I'll have to do that next.15:11
carl_baldwinpcm__: cool.  Back to the blueprints.  I think I'd like to see a few concrete examples, like your VPN example, that lay down some motivation for the features.15:12
pcm__So, in general, just trying to think of ways to fit vendor plugins in, as things are very centric to reference implementation.15:13
overlayerI'm interested in the L3 vendor plugins,  could it be explored in such a way as to enable distant, legacy routers to act as a normal neutron router for virtual networks? For instance, this blueprint expands on that idea: https://blueprints.launchpad.net/neutron/+spec/provider-router15:13
*** otherwiseguy has quit IRC15:14
carl_baldwinUltimately, we'll want a general framework that supports it but I always like to start with the concrete examples.15:14
overlayerif that router could somehow be used as a vendor plugin, it would be awesome and better align with neutron's architecture15:14
mesteryoverlayer: That's a very interesting use case, and I think it maps into what pcm__ is thinking here as well.15:14
*** MaxV has quit IRC15:15
SwamiHow will this architecture fit into the distributed model.15:15
carl_baldwinpcm__: overlayer:  That is the kind of content I would like to see in the blueprint.  A paragraph about how these blueprints fit together would be great.15:15
overlayerthe idea is that a (usually) physical router (at the other side of the internet) be used to route traffic from a virtual network to other networks (that may be physical), encapsulating the traffic that goes through the internet (as if the virtual network was directly connected)15:16
*** wchrisj_ has joined #openstack-meeting-315:16
*** ttrifonov is now known as ttrifonov_zZzz15:16
carl_baldwinSwami: That is a great point as well.  We will soon have the distinction between services that can be distributed and those that cannot.15:17
Swamicarl: yes that would give a clear idea.15:17
carl_baldwinoverlayer: sounds like a vpn use case.  Is it different?15:18
*** otherwiseguy has joined #openstack-meeting-315:19
overlayerpcm__: carl_baldwin mestery, Yes, the provider-router BP has some similarities to VPN so some ideas could be discussed...15:19
overlayercarl_baldwin: It is similar but aims at making legacy router connectivity to virtual networks as straightfoward as possible15:20
overlayerin such a way that companies can migrate their legacy networks to the cloud as painlessly as possible15:21
AndChat|112404Is it basically a way to integrate a physical router in the virtual topology?15:21
carl_baldwinoverlayer: What sort of encapsulation do you imagine between the cloud network and the "distant" router.  Are you thinking of connecting L2 segments between the two networks?  Or is this just L3 routing to the new cloud networks?15:22
overlayerI have a feeling it doesn't fit very well in neutron's path right now, and some use cases or concepts are overlapping or at the wrong place... but if the end result could be made possible, it would be awesome15:22
mesteryAndChat|112404: That's what I was thinking this was. overlayer, is this correct?15:23
carl_baldwinpcm__: overlayer:  Could you take action items to document the use cases that you have in mind?  Either wiki or blueprint is fine but please link to them from the L3 sub team wiki page.15:24
overlayercarl_baldwin: as of now, I'm thinking of the distant router establishing a tunnel to neutron (to each of the VMs) by automatic configuration made by neutron15:24
*** amrith is now known as amrith-gonzo15:25
pcm__carl_baldwin: Sure. I have some use case info, but will add more.15:25
overlayercarl_baldwin: the rest is routing (between virtual networks), made by that same distant router15:25
carl_baldwinoverlayer: A simple diagram might help to communicate it clearly.15:25
carl_baldwin#action pcm__ document known use cases.15:26
*** cjellick has joined #openstack-meeting-315:26
overlayerI have one in google docs15:26
overlayerpage 415:26
carl_baldwinoverlayer: is that linked from the blueprint?15:26
*** Rajeev has joined #openstack-meeting-315:26
overlayerI have proposed a DPR agent, which is basically the same as the L3 agent but encapsulates a distant router instead of a virtual one15:26
overlayercarl_baldwin: yes15:27
pcm__mestery: Should I put the use cases in the BP spec?15:27
pcm__(in gerrit)15:28
carl_baldwinoverlayer: Thanks.15:28
mesterypcm__: I think that's the best place for them.15:29
carl_baldwinLet's move on.  I need to review these blueprints further and I'm sure others do as well.  pcm__ I'm looking forward to seeing the specifications even if it is just a rough start.15:29
carl_baldwin#topic l3-high-availability15:30
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:30
pcm__carl_baldwin: yeah, me too :)15:30
carl_baldwinpcm__: I think that having them in place will make for a better discussion at summit.15:30
carl_baldwinsafchain: Any updates?15:30
safchainsafchain, Hi all15:31
safchainsubmitted a new patch set of the DB side in order to address some comments15:31
safchainreviewed the l3 BP part of DVR to understand how the central agent will work15:32
carl_baldwinI will add that to my review cue.  I think that many of us may be able to find some time to review again now that Icehouse is released and summit topics are almost submitted.15:32
safchainmade some comment/question on the gdoc15:32
safchaincarl_baldwin, great15:32
carl_baldwinsafchain: Thanks for reviewing DVR.  That is a pretty hot item for Juno.15:33
safchaincarl_baldwin, yes sure15:33
safchaincarl_baldwin, that's all for mr15:34
safchainme15:34
carl_baldwinI'll encourage others to review l3-high-availability and neutron-ovs-dvr now that we're in to Juno.  We would like both to land early in the cycle.15:34
carl_baldwinThanks, safchain15:34
Swamisafchain: one other thing that we wanted to make sure, is that the vrrp code can be utilized for the Service node in dvr.15:34
carl_baldwin#topic bgp-dynamic-routing15:34
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:34
carl_baldwinnextone92: hi15:34
nextone92Hi Carl!15:34
safchainSwami, yes sure, let's talk about that after15:34
carl_baldwinI see that you've submitted a summit topic.15:34
nextone92Yes: http://summit.openstack.org/cfp/details/28315:35
nextone92The blueprint is a gdoc at the moment15:35
carl_baldwinNo worries.  It will take us all a little time to convert to restructured text and merge with the template.15:36
carl_baldwinnextone92: Anything to highlight?15:36
nextone92Not at the moment, I didn't see any feedback from the document or on the mailing list15:36
*** peristeri has joined #openstack-meeting-315:36
overlayerI have read the blueprint, and have some feedback15:37
*** otherwiseguy has quit IRC15:37
*** markmcclain has quit IRC15:37
*** otherwiseguy has joined #openstack-meeting-315:37
nextone92Great! Thank you overlayer15:37
carl_baldwinoverlayer: Feel free to provide that feedback on the blueprint or ask on the ML.15:37
carl_baldwin#topic rootwrap-daemon-mode15:38
*** openstack changes topic to "rootwrap-daemon-mode (Meeting topic: neutron_l3)"15:38
overlayerwhy only BGP? did you think of a more generic way that can encompass different protocols while keeping the use cases intact?15:38
carl_baldwin#undo15:38
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x389cd50>15:38
overlayercarl_baldwin: on the blueprint, the doc? or here too?15:38
*** otherwiseguy has quit IRC15:38
overlayercarl_baldwin: got it15:39
carl_baldwinoverlayer: It is intended that this be done with a generic interface.  However, BGP is the implementation that seems to have the most interest for a first implementation.15:39
carl_baldwinoverlayer: In the doc would be great.15:39
overlayercarl_baldwin: thank you15:39
carl_baldwinoverlayer: yw15:40
carl_baldwin#topic rootwrap-daemon-mode15:40
*** openstack changes topic to "rootwrap-daemon-mode (Meeting topic: neutron_l3)"15:40
*** AndChat|112404 has quit IRC15:40
carl_baldwinago, YorikSar: Are you around?15:40
*** lsmola has quit IRC15:41
carl_baldwinWe'll continue discussion in the reviews.15:41
carl_baldwin#link https://review.openstack.org/#/q/status:open+branch:master+topic:bp/rootwrap-daemon-mode,n,z15:41
*** eghobo has joined #openstack-meeting-315:41
*** AndChat|112404 has joined #openstack-meeting-315:41
carl_baldwin#topic neutron-ovs-dvr15:41
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:41
Swamicarl: hi15:41
carl_baldwinSwami: hi.  I wanted to make sure that you had some meeting time left to discuss.15:41
SwamiDVR Progress update.15:42
SwamiEast-West completed.15:42
carl_baldwinExcellent!15:42
SwamiFIPs completed for the North-South and working on the Service node right now.15:42
carl_baldwinI have started my review.  I encourage all to review.15:42
SwamiL2 Agent code was posted for review.15:42
carl_baldwin#link https://review.openstack.org/#/q/topic:bp/neutron-ovs-dvr,n,z15:42
SwamiIt is good that we are getting early review.15:42
carl_baldwin^ This is a great link to track DVR review progress.  Bookmark it!  :)15:43
SwamiWe are trying to address the reviews while we are working on the other aspects of the DVR.15:43
mestery+1 to the link carl_baldwin!15:43
SwamiIn the coming week we will be posting the remaining code patches for L3 Agent and for the Scheduler.15:43
carl_baldwinSwami: I hope that the feedback has been constructive.15:43
*** otherwiseguy has joined #openstack-meeting-315:43
Swamicarl: Sure it is of great use for us.15:44
mesterySwami carl_baldwin: Per the new BP process, it would be great to get BPs into neutron-specs for review as well!15:44
SwamiEspecially since we are targeting the DVR for the Juno milestone 1 it would be of great help if we have early feedback.15:44
carl_baldwinA word to reviewers.  In order to not bog down the development process.  While the patches are WIP maybe we can stay away from nits and focus on the high level implementation details.15:44
mesteryI expect those to pass pretty quickly, but it's the new process and all, so I encourage that too.15:44
mesterySwami: Are the patches in a state where people can test them out? I'd like to try them soon.15:45
Swamimestery: Thanks for reminding me. I was about to ask, since we have already reviewed the blueprint should be again follow the new model to push our blueprint15:45
Swamimestery: Yes it should be in a state to test. These are internal working code.15:45
mesterySwami: Yes, the new BP process works such that features which miss a release need to re-propose at the start of the next cycle. Nova is doing the same, so we're consistent there.15:45
mesterySwami: Great! I will go ahead and try them out, thanks!15:45
*** otherwiseguy has quit IRC15:45
Swamimestery: Thanks for confirmation. I will do it asap.15:46
mesterySwami: Thanks!15:46
Swamimestery: You may have to wait for the other patches that are requirement for the complete flow.15:46
*** yamahata has quit IRC15:46
mesterySwami: OK, got it, I'll keep on the lookout on gerrit. ;)15:46
SwamiThat's all I have from the DVR side.15:47
carl_baldwinSwami: Thanks for the update.  Great progress.15:47
*** otherwiseguy has joined #openstack-meeting-315:47
carl_baldwin#topic Multiple Subnets on External Network15:47
*** openstack changes topic to "Multiple Subnets on External Network (Meeting topic: neutron_l3)"15:47
carl_baldwinI introduced this topic last week because I was unable to get multiple floating ip subnets to work on an external network.15:48
Swamicarl: For the multiple subnets on External network, also we had an issue with the DVR with the latest code.15:49
SwamiSince there was a change in the bridge mapping behaviour for the multiple subnets for Extenal network.15:49
carl_baldwinI played with it a bit and found that it actually isn't as broken as I thought.15:49
carl_baldwinSwami: I know that you were playing around with multiple external networks.  I want to make sure that we're talking about the same thing.15:50
SwamiWe are still looking into it to see how the DVR rules can work in a multiple subnet scenario.15:50
*** baojg has joined #openstack-meeting-315:50
carl_baldwinThere are multiple external networks, supported by provider networks.  Then, there are multiple subnets on a single external network.15:50
carl_baldwinSwami: Can you confirm which one specifically you are talking about just to be clear?15:51
Swamicarl: You are right, I am talking about the multiple external networks and you are talking about the multiple subnets on single network.15:51
carl_baldwinI had a feeling.  ;)15:52
carl_baldwinI actually was able to get multiple floating ip subnets to work on a single external network in devstack with only a couple of little hacks.  I plan to file a bug and post a patch soon.15:52
carl_baldwinI was actually very pleased.  I was worried it was going to be a lot of work and require a new blueprint and all that.  But I found that the code is pretty much all there, it just needs a couple of little fixes.15:53
carl_baldwinAnyway, that is my report an that.15:54
carl_baldwin#topic Open Discussion15:54
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:54
pcm__carl_baldwin:  Can you post link for L3 team sub page?15:55
carl_baldwinpcm__: Sure thing15:55
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:55
pcm__carl_baldwin: thanks!15:55
*** jcoufal has quit IRC15:55
*** nextone92 has quit IRC15:56
carl_baldwinThank you all for your great work.  I look forward to seeing progress in all of these areas.15:57
*** dstanek is now known as dstanek_lunch15:57
carl_baldwinUntil next week.15:58
safchaincarl_baldwin, thx15:58
carl_baldwin#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Thu Apr 17 15:58:36 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-04-17-15.01.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-04-17-15.01.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-04-17-15.01.log.html15:58
*** pcm__ has left #openstack-meeting-315:59
*** Swami has quit IRC16:04
*** carl_baldwin has quit IRC16:07
*** safchain has quit IRC16:09
*** SumitNaiksatam has quit IRC16:22
*** xuhanp has quit IRC16:24
*** jcoufal has joined #openstack-meeting-316:35
*** SumitNaiksatam has joined #openstack-meeting-316:36
*** dstanek_lunch has quit IRC16:37
*** otherwiseguy has quit IRC16:37
*** markmcclain has joined #openstack-meeting-316:38
*** markmcclain1 has joined #openstack-meeting-316:40
*** markmcclain has quit IRC16:42
*** markmcclain1 has quit IRC16:52
*** markmcclain has joined #openstack-meeting-316:52
*** catherineD has joined #openstack-meeting-316:53
*** praveen_dell has joined #openstack-meeting-316:59
davidlenwellzehicle_at_dell, catherineD  time for a refstack meeting ?17:00
*** fcarpenter has joined #openstack-meeting-317:01
*** eghobo has quit IRC17:02
*** dstanek_lunch has joined #openstack-meeting-317:04
*** eghobo has joined #openstack-meeting-317:07
catherineDHello17:09
*** nacim has quit IRC17:09
*** dstanek_lunch has quit IRC17:10
fcarpenterhi17:10
praveen_dellhello17:11
*** tedchang has joined #openstack-meeting-317:12
davidlenwell#startmeeting17:12
openstackdavidlenwell: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'17:12
davidlenwell#startmeeting refstack17:12
openstackMeeting started Thu Apr 17 17:12:24 2014 UTC and is due to finish in 60 minutes.  The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot.17:12
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:12
*** openstack changes topic to " (Meeting topic: refstack)"17:12
openstackThe meeting name has been set to 'refstack'17:12
davidlenwellroll call?17:12
catherineDHere17:12
tedchanghere17:12
fcarpentermorning17:12
davidlenwellmorning everyone17:13
praveen_dellgood evening17:13
davidlenwell#topic summit session17:13
*** openstack changes topic to "summit session (Meeting topic: refstack)"17:13
davidlenwellcatherineD: will you be able to attend the openstack summit?17:13
catherineDLast I check the session is pre-accepted?17:14
davidlenwellyes .. I think it will go through17:14
catherineDwe can only travel if it is accepted ..17:14
davidlenwellokay .. so we'll know soon enough17:14
catherineDyes .. only then we can make travel request17:15
davidlenwellcosts more that way.. I personally live in hope that it will be ..17:16
davidlenwellbut I was going to the summit anyways17:16
catherineDgood good, I think Rocky is too ..17:16
davidlenwellokay moving right along17:16
praveen_delli would like to attend the summit17:16
davidlenwellpraveen_dell: tell rob you must attend ;)17:17
davidlenwell#topic execute_test madness17:17
*** openstack changes topic to "execute_test madness (Meeting topic: refstack)"17:17
davidlenwellSo I was hoping for either more pushback on what I did in execute_test or a working tcup build from rob.. I guess he's going to work on it tomorrow17:18
catherineDLast status is Ted waits waiting for davidlenwell: before making more change to execute_test?17:19
davidlenwellcatherineD: I posted a review of it and asked you gusy to review it durring the last meeitng17:19
catherineDyou understand what I mean :-)17:19
davidlenwellsince it was blocking rob from his work I merged the code17:20
davidlenwelltedchang: did you get a chance to review it .. it was your code I started off with17:20
*** Hao has quit IRC17:20
catherineDThey did17:21
davidlenwellhe didn't17:21
tedchangboth me and ray left comments on it17:21
davidlenwellonly on docker_buildfile.template  not in the execute_test code it self17:22
davidlenwellthat actually is a good point ..17:22
davidlenwellthe docker_buildfile.template pulls the script from refstack .. that is one thing i want to change ..17:22
catherineDok so the code is merged ..17:22
tedchangexecute_test I looked but I have to try to really make sure it will work17:23
davidlenwellI'd like for it to get the script from git rather than from an http call .. for one .. an http call is very insecure17:23
davidlenwellto wget a file from a url then execute it leaves us open for man in the middle attacks17:23
davidlenwellI don't forsee execute_test changing much in the future once its working .. so I don't want to keep this model ..17:24
*** zehicle_at_dell has joined #openstack-meeting-317:24
davidlenwellif you look at what I did I started to make execute_test an installable package with tempest as a dependancy17:25
davidlenwellwhat I would love to do is get it into its own repo called "refstack-tester" or something and get it into pypy so that it can just be pip installed on testing nodes17:25
davidlenwellwhat do you guys think about that ?17:26
catherineDHere is Raymond last comment "The main purpose of using the get-script api is to make sure the script and the dockerfile are of the same version. Getting the script from github cannot guarantee they are of the same release."17:27
davidlenwellthat is a valid argument17:28
davidlenwellbut the api needs to be version locked moving forward anyways17:28
davidlenwellso that the live copy of refstack.org gets api/v1 api/v2 and so forth ..17:29
davidlenwellbecause refstack.org's api needs to be able to accept data from any version of the tester17:29
davidlenwellI understand thats hard to do when things are changing rapidly .. but things can't keep shifting as much as they will int he beginings of a project17:30
*** s3wong has joined #openstack-meeting-317:30
catherineDI have no problem with that ..... We need to focus ... at this point the most important thing is to collect data .. agree?17:31
davidlenwellagreed17:31
*** banix has joined #openstack-meeting-317:31
catherineDso what we have so far .. we are able to collect some data ... how do we enable others to collect data?  are they willing to just run what we have that is working ?17:32
s3wongIs this the Neutron group-policy meeting?17:32
banixs3wong: no17:32
davidlenwells3wong: no this is refstack17:32
banixalt17:32
banixs3wong: we are at the meeting-alt channel17:33
s3wongbanix: Thanks17:33
davidlenwellcatherineD: so what we have so far doesn't allow that currently .. if rob can finish what he is working on we'll be able to collect data from anyone17:33
catherineDWe have been collecting data via Refstack path ..17:34
davidlenwellcatherineD: but that data is not going back to refstack.org's central database17:34
catherineDthe that is what we need to work on ...17:34
davidlenwellwe're missing the publish results part of the story17:34
catherineDmake sure that data can be sent back to centrol Refstack17:35
catherineDshould we concentrated on the send back center Refstack ?17:35
davidlenwellpossibly ..17:35
catherineDRaymond had a TCUP version that is working ...17:36
*** overlayer has quit IRC17:36
catherineDit may not be the final version .. we all understand that ...17:36
davidlenwellare you reffering to the shell scripts ?17:36
catherineDI refer to this one https://review.openstack.org/#/c/84320/17:37
davidlenwellyeah .. that one17:37
catherineDthis is a very quick thing that we put together just for data collection ... understand that it may no be final ..17:37
praveen_delli have tested existing tcup,it only builds the docker container and exports openstack properties on to docker container17:38
catherineDI really want to see some other data ...17:38
davidlenwellcatherineD: so do I ..17:38
catherineDwe can focus on the send back data ... I have  data that I collect from Havana (all in one) env that I can pulbish17:39
davidlenwellso rob tells me he'll have time tomorrow to finish what he was working on .. the tcup.py aproach17:39
davidlenwellthat is .. sourcing an openstack.rc file that a user gets from the cloud they want tested17:40
catherineDnp .. just that we need data ... I found that there are more configuration in tempest.config that we need to consider ... that is why I would like to see more data from other env17:40
davidlenwellthen kicking off a script that grabs the already built container and runs it with the env variables17:40
catherineDsource openstack.rc is definitetly not enough ..17:40
davidlenwellit should be able to auto discover the rest17:41
*** AndChat|112404 has quit IRC17:41
catherineDone example ... network ..17:41
*** jcoufal has quit IRC17:41
*** jcoufal has joined #openstack-meeting-317:41
davidlenwellupstream tempest is close to having the networking auto discovery built ..17:41
catherineDif you env has more than one network and your network name is not named "private" or "public"  so need to confgure those parameters ...17:42
davidlenwellnot sure how long it will take for that code to make it into havana stable17:42
catherineDdiscovery is also a problem .. let say I discover 10 networks then which one should I use?17:42
davidlenwellthat is going to require some thought ..17:42
davidlenwelllets get back to a network / config discussion offline17:43
davidlenwellwe're low on time17:43
catherineDyes .. a lot more configuration needed as I start to collect data17:43
davidlenwellokay . we're running low on time so I am going to move to another topic17:43
catherineDsure17:43
davidlenwell#topic #infra testing17:43
*** openstack changes topic to "#infra testing (Meeting topic: refstack)"17:43
davidlenwellSo while at pycon over the weekend I had a chance to chat face to face with jim blair17:44
*** sarob has joined #openstack-meeting-317:44
davidlenwellhe's ptl of infra .. the group we want to host this thing long term17:44
davidlenwelland he sorta shattered some of my dreams about how I wanted to trigger tests using pure openstack things..17:44
catherineDpraveen_dell: may be take a look at this one for some idea https://review.openstack.org/#/c/84320/ of how we run test ... Let's move to the next subject17:45
*** jaypipes has joined #openstack-meeting-317:45
davidlenwellbut then explained a workable solution that might be a better idea anyways17:45
praveen_dell@catherineD sure17:45
davidlenwellthat is essentially to just use the infra system to run tests17:45
catherineDdavidlenwell: that is refstack will be hosted on infra system?17:46
davidlenwellwithout explaining in detail how infra works ..17:46
davidlenwellcatherineD: yes .. it will17:47
davidlenwellbut even before it is .. they can host the testing env17:47
davidlenwellthey have a thing called nodepool17:47
davidlenwelland another thing called zuul17:47
davidlenwellnodepool just makes a bunch of ready to run .. one time use vm's for running tests .. their config is passed to them with a yaml file17:47
davidlenwellwhen they boot up they ask zuul for jobs.. zuul gives them a job and then keeps track of its progress17:48
davidlenwellSo we can piggy back on that17:48
davidlenwellcreate our own node type for nodepool17:48
davidlenwelland im paraphrasing here .. but essentially it will keep an army of ready to run single use vm's at our disposal17:49
davidlenwellthat we can then trigger and let run and report home with results17:49
*** beyounn has joined #openstack-meeting-317:52
davidlenwellanyways .. long story short .. my original gearman spec is close to what we'll end up with but not exactly .. and I'll amend the spec to more closely match that17:52
catherineDcool17:52
davidlenwell#topic open discussion17:53
*** openstack changes topic to "open discussion (Meeting topic: refstack)"17:53
*** praveen_dell has quit IRC17:53
davidlenwellis there anything anyone needs to talk about ?17:54
catherineDso we will work on the send data back to code  so we can collect data ....  agree?17:54
davidlenwellcatherineD: I feel like the networking discussion isn't going to be an easy solution .. perhaps we'll need to make this user entered feilds to start with17:54
catherineDyes exactly ...17:55
catherineDthat is why it is important to have more people test to discover more ...17:55
davidlenwellcatherineD: since refstack.org already has a public method for accepting data .. we just need to make a call out to api thing on the local refstack that can send things to it17:55
catherineDi have the same thinking as yours that we may need more user data enter than we would like to ...17:55
*** jpomero has quit IRC17:55
catherineDok will do that to call the pulbikc methoid ....17:56
davidlenwellcatherineD: can you write a spec before writing any code please ?17:56
catherineDAt this time data is what we need ...17:56
davidlenwellthe public method might have to be change .. the database might need some alteration17:57
davidlenwelland I just want it to be thought through17:57
catherineDwe will but we do not see writing any more code before discussion with the team ...17:57
*** punal has joined #openstack-meeting-317:57
davidlenwellthe questions in the spec template are designed to take out the guessing on the impact of changes17:57
catherineDic17:58
catherineDwill do17:58
*** dstanek has joined #openstack-meeting-317:58
davidlenwellokay .. I look forward to seeing that .. I'll be back at piston hq full time next week .. So my hours will be more regular and we'll see more commits out of me17:59
catherineDgreat! maybe we need an other f-2-r18:00
catherineDf2f18:00
davidlenwellyeah .. im open to that18:00
davidlenwellwe should plan for after the 1st of the month tho .. piston is moving offices right now18:00
davidlenwell#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Thu Apr 17 18:00:51 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-04-17-17.12.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-04-17-17.12.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-04-17-17.12.log.html18:00
*** jpomero has joined #openstack-meeting-318:01
*** rockyg has joined #openstack-meeting-318:02
*** s3wong has quit IRC18:04
*** nbouthors has joined #openstack-meeting-318:06
*** s3wong has joined #openstack-meeting-318:06
*** mandeep has joined #openstack-meeting-318:06
*** rkukura has joined #openstack-meeting-318:06
*** hemanthravi has joined #openstack-meeting-318:06
SumitNaiksatam#startmeeting networking_policy18:07
openstackMeeting started Thu Apr 17 18:07:01 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:07
mandeepHi Group policy folks?18:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:07
*** openstack changes topic to " (Meeting topic: networking_policy)"18:07
openstackThe meeting name has been set to 'networking_policy'18:07
rkukurahi18:07
s3wonghello18:07
banixhi18:07
s3wongclearly the channel wasn't booked fully18:07
banixs3wong: you knew something about this channel :)18:07
*** thinrichs has joined #openstack-meeting-318:07
s3wongbut is it available from 17:00 onward?18:07
SumitNaiksatam#topic Policy plugin driver update18:07
*** openstack changes topic to "Policy plugin driver update (Meeting topic: networking_policy)"18:07
s3wongbanix: yeah - but I didn't stay on :-)18:07
rkukuraI’m working towards a short term goal:18:08
SumitNaiksatamrkukura: sorry for cutting your update18:08
*** lblanchard has joined #openstack-meeting-318:08
SumitNaiksatamrkukura: please go ahead18:08
rockygUh, Refstack has it 1700-180018:08
rkukurao drive creation of the neutron network, subnet, and port resources via the group API, with all traffic allowed18:08
s3wongrockyg: I was thinking of doing #openstack-meeting-alt from 1700-180018:09
rkukuraThen s3wong and I can work in parallel from that on mapping the policies18:09
SumitNaiksatamrkukura: that sounds like a good plan to me18:09
rkukuraDoes this approach make sense?18:09
banixrkukura: thanks yes. is this already in your branch?18:09
*** jtomasek has quit IRC18:10
s3wongrkukura: sounds good. The service stuff would need more clarity before I can do into full-mode coding anyway :-)18:10
rockygs3wong:  Ah.  That would work.  Also an fyi for the RefStack: we stay PST/PDT, so the UTC time shifts with daylight savings time.  But that's our problem.18:10
rkukurabanix: not yes - I’m building the unit tests on top of what SumitNaiksatam has done, and needed to complete some of that first18:10
rkukuras/not yes/not yet/18:10
thinrichsrkukura: so are we assuming no one has already created their own networks/ports/etc.?18:10
banixrkukura: ok. thanks.18:10
rkukurathinrichs: I don’t think we need to assume that, but maybe we can defer handling it18:11
thinrichsI was just anticipating objections from the people who like the non-policy API.18:11
thinrichsIf our first use case demonstrates that the two APIs can be used together, it will squash their objections.18:11
SumitNaiksatamthinrichs: yes, thats the goal18:12
banixi think that will be the case18:12
rkukurathinrichs: Fair enough, but making this really work might require the plugin intercept stuff that we are deferring for a bit18:12
*** fcarpenter has left #openstack-meeting-318:12
SumitNaiksatamrkukura: that’s correc18:12
SumitNaiksatam*correct18:12
SumitNaiksatamthinrichs: we are iterating towards that goal in terms of implementation18:13
SumitNaiksatamthinrichs: hopefully the patch we push upstream will have this from the get go18:13
rkukuraI’m trying to do as little as possible in the 1st iteration so we can get people working in parallel ASAP18:13
thinrichsUnderstood--I was just thinking about making the demo something that helps everyone understand where we are and where we're headed.18:13
SumitNaiksatamthinrichs: absolutely, good to have that thought processing going18:14
rkukurathinrichs: I’ll at least include TODO comments for this18:14
thinrichsrkukura: good plan.18:14
rkukuras3wong: Are you on board with the approach I described?18:15
*** lblanchard has quit IRC18:15
s3wongrkukura: yes (as mentioned above :-) )18:15
rkukuras3wong: Sorry, see it now18:15
rkukuraAnything else on the mapping driver for now?18:16
s3wongrkukura: thanks for setting the groundwork18:16
s3wongrkukura: seems like it's just you and me :-)18:16
*** ttrifonov_zZzz is now known as ttrifonov18:17
*** sarob has quit IRC18:17
rkukuraSumitNaiksatam: What’s next on the agenda?18:17
*** markmcclain has quit IRC18:18
SumitNaiksatamrkukura: yeah, are you dont with your update?18:18
*** sarob has joined #openstack-meeting-318:18
SumitNaiksatamany questions for rkukura s3wong?18:18
SumitNaiksatamok moving on18:18
SumitNaiksatam#topic Python Client and CLI18:18
*** openstack changes topic to "Python Client and CLI (Meeting topic: networking_policy)"18:18
SumitNaiksatamhemanthravi: there?18:19
hemanthraviSumitNaiksatam: delayed on this, have CLI for end-poing and epg18:19
rkukuraSumitNaiksatam: Is it advizable to keep pushing updates to my github branch without squashing?18:19
hemanthraviwill complete the rest next week18:19
SumitNaiksatamhemanthravi: nice, i guess delayed is good, since we are evolving the api18:19
hemanthravicaught up with a few thins this week18:19
SumitNaiksatamhemanthravi: thanks, end of this week is good18:20
hemanthravimight be wed of next week, is that ok18:20
SumitNaiksatamrkukura: yeah, we need to sort out the branching18:20
SumitNaiksatamrkukura: lets talk about it18:20
SumitNaiksatamhemanthravi: strech goal, this weekend? just kidding :-)18:21
mandeeprkukura: I am deliquent in sending my update on branch usage, I will do so today18:21
rkukuramandeep: OK18:21
SumitNaiksatamhemanthravi: perhaps just getting one single resource working wil be good for now18:21
SumitNaiksatamhemanthravi: after that it will be mechanical18:21
hemanthraviSumitNaiksatam: ok will push that out18:22
SumitNaiksatamwell hopefully18:22
SumitNaiksatamhemanthravi: thanks18:22
SumitNaiksatamrkukura: btw, thanks for the earlier update, forgot to mention ;-P18:22
banixhemanthravi: thanks18:22
*** sarob has quit IRC18:22
SumitNaiksatam#topic Horizon integration18:22
*** openstack changes topic to "Horizon integration (Meeting topic: networking_policy)"18:22
s3wongSumitNaiksatam: oh? someone is working on Horizon?18:23
SumitNaiksatamhemanthravi: did prasad offer to pursue this? or was it Subra?18:23
SumitNaiksatamor neither?18:23
*** tedchang has quit IRC18:23
SumitNaiksatamokay may be we need to check who the owner for this is18:24
hemanthraviSumitNaiksatam: need to check on this, haven't started on it for sure18:24
SumitNaiksatamhemanthravi: okay, understand18:24
SumitNaiksatamanyone else want to jump in, please feel free18:24
SumitNaiksatam#topic Design summit session18:24
*** openstack changes topic to "Design summit session (Meeting topic: networking_policy)"18:24
SumitNaiksatamwe have requested a session for this18:24
SumitNaiksatamnot sure that we will get a time slot, we will know soon18:25
SumitNaiksatamif we get it, we will be presenting as a team18:25
s3wongSumitNaiksatam: hopefully we will be enable to get a design session ;-)18:25
SumitNaiksatams3wong banix i think you commented on the session18:25
SumitNaiksatamthanks! need more of those :-P18:25
s3wongSumitNaiksatam: also you, banix, and I will have to prep for the general presentation18:25
*** Sukhdev has joined #openstack-meeting-318:26
SumitNaiksatams3wong: yes, thats the next topic18:26
SumitNaiksatam#topic Conference Session18:26
*** openstack changes topic to "Conference Session (Meeting topic: networking_policy)"18:26
banixShall we try to meet on Monday of the sumit week? just us? may be?18:26
SumitNaiksatambanix s3wong and mestery got a conference slot to present this18:26
SumitNaiksatammestery wont be able to do it now, since he is swamped18:26
SumitNaiksatamhe asked me to step in18:26
SumitNaiksatambanix: great idea18:27
s3wongbanix: will there be slides (I would think so) - so we would have to work on that prior to arriving at the Sumit (at least I hope we do) :-)18:27
SumitNaiksatambanix: lets do that18:27
SumitNaiksatams3wong: slides for the conference, yes18:27
banixmeeting on monday will be for design session and discussions18:27
SumitNaiksatams3wong: most probably not for the design session18:27
banixfor the general conference talk yes we have to have slides ready before getting there :)18:27
SumitNaiksatamfor the conference session, yes lets all collaborate as a team again to put a coherent message out there, in terms of what we are trying to do here18:28
s3wongSumitNaiksatam: Oh - I was confused, I thought banix was talking about the conference presentation18:28
SumitNaiksatams3wong: yes sure18:28
SumitNaiksatami think the meeting will be good in general, not just for preparing for the conf presentation18:28
*** zehicle_at_dell has quit IRC18:28
banixs3wong: yeah that comment was for the earlier topic… too slow :)18:29
SumitNaiksatam#topic Open Discussion18:29
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:29
SumitNaiksatamwe have a min18:29
SumitNaiksatamanything we missed out?18:29
s3wongSumitNaiksatam: meeting time18:29
SumitNaiksatams3wong: nice, thats a pain18:29
SumitNaiksatamyeah we will have to change again18:30
s3wongclearly #openstack-meeting-alt isn't working for 17:3018:30
SumitNaiksatam-meeting-3 is also not available at 17.3018:30
s3wongit seems like we may want to do 17:00 on #openstack-meeting-alt18:30
SumitNaiksatamor 18.00 on -meeting-318:30
banixor 18:00?18:30
*** Rajeev has quit IRC18:30
SumitNaiksatambanix: yeah ^^^18:30
s3wongthough 1700 may eat into banix's lunch time :-)18:30
* mestery peeks back in for a bit.18:30
mesteryI can help review slides as well if you guys want! :)18:30
s3wongmestery: great18:31
banixyeah i prefer 18:00 but 17:00 is ok if we have to18:31
mandeepI vote for 18:00 as well18:31
SumitNaiksatammestery: absolutely, thats a given :-)18:31
banixmestery: great; will have to start working on them soon. will keep you updated18:31
SumitNaiksatams3wong, others, 18.00 okay?18:31
s3wongseems like 1800 it is then18:31
rkukuraeither should be OK for me18:31
SumitNaiksatamrkukura: nice, thanks for being flexible18:32
hemanthravi11 pdt?18:32
banixyes for me18:32
SumitNaiksatamok done, thursdays 1800 UTC18:32
s3wonghemanthravi: yes, that would be 11am pdt18:32
SumitNaiksatamhemanthravi: yes, 11 PDT18:32
SumitNaiksatamok lets call it a wrap18:32
hemanthraviyes for me18:32
SumitNaiksatamthanks all for attending18:32
SumitNaiksatamhemanthravi: great18:32
banixthanks everybody18:32
mandeepthanks18:32
SumitNaiksatam#endmeeting18:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:32
banixbye18:32
openstackMeeting ended Thu Apr 17 18:32:50 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-04-17-18.07.html18:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-04-17-18.07.txt18:32
rkukurabye18:32
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-04-17-18.07.log.html18:32
s3wongbye18:33
*** mandeep has quit IRC18:33
rkukuraSumitNaiksatam: Which channel?18:33
s3wong#openstack-meeting-318:33
s3wongrkukura: the current channel18:33
rkukurathx18:34
*** sarob has joined #openstack-meeting-318:34
*** rkukura has left #openstack-meeting-318:34
*** s3wong has left #openstack-meeting-318:34
*** enikanorov_ has joined #openstack-meeting-318:36
*** Sukhdev has quit IRC18:36
*** Sukhdev has joined #openstack-meeting-318:37
*** hemanthravi has quit IRC18:39
*** nbouthors has quit IRC18:40
*** markmcclain has joined #openstack-meeting-318:41
*** overlayer has joined #openstack-meeting-318:45
*** tedchang has joined #openstack-meeting-318:50
*** banix has quit IRC18:55
*** banix has joined #openstack-meeting-318:56
*** sarob has quit IRC18:56
*** jtomasek has joined #openstack-meeting-318:57
*** sarob has joined #openstack-meeting-318:57
*** dstanek has quit IRC18:57
*** sarob has quit IRC19:01
*** jpomero_ has joined #openstack-meeting-319:02
*** jpomero has quit IRC19:04
*** rockyg has quit IRC19:06
*** banix has quit IRC19:23
*** banix has joined #openstack-meeting-319:25
*** baojg has quit IRC19:27
*** baojg has joined #openstack-meeting-319:27
*** dstanek has joined #openstack-meeting-319:28
*** sarob has joined #openstack-meeting-319:31
*** baojg has quit IRC19:32
*** glenc has quit IRC19:32
*** annegentle has quit IRC19:33
*** ycombinator has quit IRC19:33
*** glenc has joined #openstack-meeting-319:33
*** sarob has quit IRC19:35
*** amrith-gonzo is now known as amrith19:36
*** sarob has joined #openstack-meeting-319:44
*** sarob has quit IRC19:49
*** otherwiseguy has joined #openstack-meeting-320:02
*** annegentle has joined #openstack-meeting-320:04
*** sarob has joined #openstack-meeting-320:09
*** sarob_ has joined #openstack-meeting-320:13
*** sarob has quit IRC20:13
*** mwagner_lap has quit IRC20:14
*** thinrichs has quit IRC20:16
*** punal has quit IRC20:17
*** Sukhdev has quit IRC20:28
*** Sukhdev has joined #openstack-meeting-320:29
*** banix has quit IRC20:31
*** banix has joined #openstack-meeting-320:38
*** alexpilotti has quit IRC20:40
*** dstanek has quit IRC20:41
*** dstanek has joined #openstack-meeting-320:41
*** sarob_ has quit IRC20:43
*** sarob has joined #openstack-meeting-320:44
*** alexpilotti has joined #openstack-meeting-320:47
*** sarob has quit IRC20:48
*** eguz has joined #openstack-meeting-320:49
*** nacim has joined #openstack-meeting-320:50
*** eghobo has quit IRC20:53
*** david-lyle has quit IRC21:04
*** chuckC has joined #openstack-meeting-321:05
*** sarob has joined #openstack-meeting-321:06
*** tedchang has quit IRC21:06
*** sarob has quit IRC21:10
*** eguz has quit IRC21:12
*** eghobo has joined #openstack-meeting-321:13
*** eguz has joined #openstack-meeting-321:16
*** peristeri has quit IRC21:17
*** markmcclain has quit IRC21:18
*** eghobo has quit IRC21:21
*** banix has quit IRC21:21
*** eguz has quit IRC21:21
*** tedchang has joined #openstack-meeting-321:21
*** eghobo has joined #openstack-meeting-321:22
*** mwagner_lap has joined #openstack-meeting-321:23
*** banix has joined #openstack-meeting-321:30
*** nacim has quit IRC21:33
*** jrist has quit IRC21:36
*** jrist has joined #openstack-meeting-321:36
*** markmcclain has joined #openstack-meeting-321:42
*** jpomero_ has quit IRC21:42
*** banix has quit IRC21:44
*** chuckC has quit IRC21:44
*** tedchang has quit IRC21:49
*** jtomasek has quit IRC21:50
*** rockyg has joined #openstack-meeting-321:59
*** TravT has joined #openstack-meeting-322:03
*** TravT has quit IRC22:04
*** TravT has joined #openstack-meeting-322:04
*** TravT has quit IRC22:05
*** TravT has joined #openstack-meeting-322:05
*** ttrifonov is now known as ttrifonov_zZzz22:12
*** chuckC has joined #openstack-meeting-322:17
*** mfer has quit IRC22:19
*** overlayer has quit IRC22:20
*** jcoufal has quit IRC22:21
*** david-lyle has joined #openstack-meeting-322:23
*** david-lyle has quit IRC22:29
*** Sukhdev has quit IRC22:29
*** otherwiseguy has quit IRC22:32
*** otherwiseguy has joined #openstack-meeting-322:33
*** catherineD has left #openstack-meeting-322:40
*** chuckC has quit IRC22:42
*** sweston has quit IRC22:44
*** sweston has joined #openstack-meeting-322:50
*** wchrisj_ has quit IRC23:02
*** sarob has joined #openstack-meeting-323:09
*** sarob has quit IRC23:13
*** rockyg has quit IRC23:14
*** wchrisj has joined #openstack-meeting-323:18
*** mfer has joined #openstack-meeting-323:22
*** mfer has quit IRC23:24
*** eghobo has quit IRC23:25
*** wchrisj has quit IRC23:28
*** wchrisj has joined #openstack-meeting-323:35
*** Sukhdev has joined #openstack-meeting-323:35
*** wchrisj has quit IRC23:38
*** wchrisj has joined #openstack-meeting-323:41
*** wchrisj has quit IRC23:44
*** TravT has quit IRC23:58
*** TravT has joined #openstack-meeting-323:59
*** TravT has quit IRC23:59

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