15:04:44 <Swami> #startmeeting Distributed virtual router
15:04:45 <openstack> Meeting started Wed Jan  8 15:04:44 2014 UTC and is due to finish in 60 minutes.  The chair is Swami. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:04:46 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:04:49 <openstack> The meeting name has been set to 'distributed_virtual_router'
15:05:07 <enikanorov> good. I don't have to say much this time, so I'll be a silent listener. unless something related to lbaas arises
15:05:09 <safchain> Swami, hi
15:05:20 <Swami> safchain: hi
15:05:45 <Swami> safchain: I missed you in the conference call last week. Where you not able to dial.
15:06:17 <safchain> unfortunately yes
15:06:44 <Swami> safchain: did you get a chance to go over the google doc
15:07:21 <safchain> Swami, not since two weeks
15:07:28 <Swami> enikanorov: did you get a chance to go through the google doc.
15:07:42 <enikanorov> Swami: not yet
15:07:52 <Swami> safchain: ok, thanks, if you have any questions please let me know.
15:08:11 <safchain> Swami, sure
15:08:55 <safchain> Swami, great to see call flows
15:09:04 <Swami> enikanorov: Since you are here, I have a basic question related to services such as Lbaas. On how it should operate in a distributed Router mode.
15:09:08 <Swami> safchain: thanks
15:09:50 <safchain> Swami, have you change something in the global design ?
15:09:55 <Swami> enikanorov: What is your thought on centralizing the services versus distributed.
15:10:10 <enikanorov> Swami: that's a good question. Currently we don't have loadbalancers that operate as routers themselves, so vip is always on the tenant network
15:10:21 <Swami> safchain: what do you mean by global design. I don't think we have changed anything .
15:10:41 <enikanorov> so if i understand correctly, virtual router stuff would affect association of the floating ip and the vip port
15:11:07 <Swami> enikanorov: Yes you are right, I am not familiar with the LBass as you are.
15:11:18 <safchain> safchain, I mean the design of the solution, type of routers, routing, etc
15:11:24 <safchain> Swami, ^
15:11:43 <enikanorov> if talking about routed-mode loadbalancers things could be different, but we have not analyzed it yet, since we doesn't have such solution.
15:11:51 <Swami> safchain: nothing has changed from our original design, but we have added more content and description.
15:12:36 <enikanorov> in fact we have one (which is nicira's or VMWare NSX), but it relies on the nicira edge router, so I'm not sure distributed routers are applicable there
15:13:23 <Swami> enikanorov: in the current LBaas service model, will the lbaas service be affected when we distribute the routers, because in this case each compute node will be having an external gateway and a related floating ip., where do you intend to have the lbaas service.
15:13:48 <Swami> safchain: Did you have any details on your proposal for the north-south.
15:14:46 <enikanorov> floating ip is a nat from gateway to the port on tenant network, in fact lbaas is even unaware of that
15:14:51 <Swami> enikanorov: Yes in our design we don't have a concept of edge router, yes it makes our life easier when we a tenant has an edge router.
15:15:21 <safchain> Swami, no, only the document linked on the bottom of yours
15:15:22 <enikanorov> so for existing lbaas providers it doesn't matter how floating ips are maintained, because it is out of lbaas control
15:15:49 <Swami> safchain: Yes it only had the picture but no other information, that's why I was curious to know if you had any other solution.
15:16:43 <Swami> enikanorov: When we have external network connectivity from each and every compute node in a multihost scenario, where will the lbaas run
15:17:20 <safchain> Swami, other than yours and mine, no, I could had some details to my document
15:17:31 <enikanorov> that totally depends on lbaas provider. existing haproxy lbaas provider choses one of the hosts where lbaas agent runs
15:17:37 <enikanorov> and starts haproxy there
15:18:07 <enikanorov> Swami: another providers may use VMs to bring up the balancer
15:19:44 <Swami> enikanorov: In the google doc, I have a picture at the end describing the services, you can take a look at it.
15:19:56 <enikanorov> let me do it right now
15:20:10 <Swami> link https://docs.google.com/document/d/1iXMAyVMf42FTahExmGdYNGOBFyeA4e74sAO3pvr_RjA/edit
15:20:59 <safchain> Swami, I think one difference between the two designs is the API/CLI changes and of course  all the routing things
15:22:54 <Swami> safchain: Yes I since we are also considering the east-west we have that in place. the reason for adding the new EGA command is to utilize only single ip address in the compute nodes, otherwise each EGA will consume one IP address. How are you handling it?
15:23:29 <shivh> can one maintain a single routed ip address for the distributed virtual router? Do we have to have one IP address per host?
15:24:48 <Swami> shivh: hi
15:25:25 <shivh> hi, interesting work you are doing. I was trying to see if we can use vip concepts here as well.
15:25:26 <safchain> Swami, for north-south, the traffic goes through the "classical"  l3 agent, only compute node having floating ip are directly connected to external network
15:25:47 <Swami> shivh: We do have only one single routed ip address for all the routers that we have for distributed routers. But for external connectivity, if you enable a Gateway on each and every node, then each node will have a public ip address.
15:26:47 <shivh> got it. my question is answered. thx.
15:28:42 <Swami> safchain: When you say it uses the classical l3 agent, for normal external connectivity to the public network, does the tenat still use the gateway in the network node.
15:29:26 <safchain> Swami, only if the tenant doesn't use any floating ip
15:30:05 <Swami> safchain: ok, if the tenant uses floating ip for a particular VM, then how do you route the traffic.
15:30:11 <safchain> Swami, if the tenant use one floating ip, the floating ip is scheduled on the compute node
15:31:00 <safchain> Swami, what do you mean by "route the traffic"  ? north-south or east-west ?
15:31:18 <Swami> safchain: I meant north-south.
15:32:52 <Swami> safchain: for the floating ip case, the traffic will get out from the compute node and all other VM traffic will then move through the network node external net. ( am I right).
15:33:13 <safchain> Swami, no only this vm will use the floating ip
15:33:28 <safchain> Swami, all others will use the current l3
15:33:33 <Swami> safchain: ok thanks.
15:33:56 <Swami> enikanorov: did you get a chance to look at the doc.
15:34:05 <enikanorov> looking at it right now.
15:34:13 <Swami> enikanorov; thanks.
15:35:17 <Swami> safchain: The only issue that we see in our current model is how to tie the services network with the distributed network?
15:36:48 <safchain> Swami, which services, fwaas, lbaas ?
15:36:56 <enikanorov> Swami: i need to think about the scheme. at first glance it doesn't seem different from single router at which loadbalancer works (if we had such insertion mode for lb)
15:37:28 <Swami> safchain: I was talking about the VPNaaS and LbaaS
15:38:02 <Swami> enikanorov: thanks, think through that and I will chat with this week.
15:38:41 <enikanorov> Swami: we'll have an lbaas meeting tomorrow at 14 utc on #openstack-meeting
15:38:52 <enikanorov> i'll try to raise the discussion on this
15:39:01 <Swami> enikanorov: Ok I will try to join, it is too early, but will try.
15:39:40 <enikanorov> ok. i don't think it's required, probably such discussion is a bit premature since there are no plans to introduce routed lb for icehouse
15:40:03 <enikanorov> but I'll let folks know about the bp and your design doc
15:40:08 <Swami> safchain: I need to discuss the next steps. So if you have any concerns or questions on the doc, please send me your thoughts or ideas or proposals.
15:40:31 <safchain> Swami, yes of course and I will update my doc
15:40:54 <Swami> safchain: Also if you want to talk to me and understand more on the design we can have a session.
15:41:18 <Swami> enikanorov: Thanks for your help.
15:41:32 <safchain> Swami, sure, I will update the doc, I after I will ping you to discuss about it
15:41:34 <enikanorov> no prob
15:41:40 <Swami> ok, thanks
15:41:52 <Swami> folks I need to drop off early today.
15:42:22 <safchain> Swami, ok no prob
15:42:30 <Swami> So I will end the discussion and if anything is required please, send me an email. Folks also don't wait for the meeting and if you have any questions feel free to send me.
15:42:42 <Swami> Thanks for joining.
15:42:53 <shivh> Thanks for organizing.
15:43:04 <Swami> #info Next week I am planning to have a global design discussion.
15:43:19 <safchain> Swami, thanks for the meeting
15:43:27 <Swami> Thank you all.
15:43:41 <Swami> #endmeeting