<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div><font>Agreed. The way I'm thinking about this is that tenants shouldn't care what the underlying implementation is - L2 or L3. As long as the connectivity requirements are met using the model/API, end users should be fine. </font></div>
<div><font>The data center network design should be an administrators decision based on the implementation mechanism that has been configured for OpenStack. </font></div>
<div><br>
</div>
<div>Thanks</div>
<div>Rohit</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Kevin Benton <<a href="mailto:blak111@gmail.com">blak111@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, October 28, 2014 1:01 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [neutron][nova] New specs on routed networking<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">><span style="font-family: arial, sans-serif; font-size: 13.3333339691162px; ">1. Every packet L3 FIB Lookup : Radix Tree Search, instead of current L2 Hash/Index Lookup ?</span><br style="font-family:arial,sans-serif;font-size:13.3333339691162px">
<span style="font-family: arial, sans-serif; font-size: 13.3333339691162px; ">>2. Will there be Hierarchical network ? How much of the Routes will be imported from external world ?</span>
<div><span style="font-family: arial, sans-serif; font-size: 13.3333339691162px; ">></span><span style="font-family: arial, sans-serif; font-size: 13.3333339691162px; ">3. Will there be Separate routing domain for overlay network ? Or it will be mixed with
external/underlay network ?</span></div>
<br style="font-family:arial,sans-serif;font-size:13.3333339691162px">
<div>These are all implementation specific details. Different deployments and network backends can implement them however they want. What we need to discuss now is how this model will look to the end-user and API.</div>
<div><br>
</div>
<div>><span style="font-family: arial, sans-serif; font-size: 13.3333339691162px; ">4. What will be the basic use case of this ? Thinking of L3 switching to support BGP-MPLS L3 VPN Scenario right from compute node ?</span></div>
<div><br>
</div>
<div>I think the simplest use case is just that a provider doesn't want to deal with extending L2 domains all over their datacenter. </div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Oct 28, 2014 at 12:39 PM, A, Keshava <span dir="ltr">
<<a href="mailto:keshava.a@hp.com" target="_blank">keshava.a@hp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Cory,<br>
<br>
Yes that is the basic question I have.<br>
<br>
OpenStack cloud is ready to move away from Flat L2 network ?<br>
<br>
1. Every packet L3 FIB Lookup : Radix Tree Search, instead of current L2 Hash/Index Lookup ?<br>
2. Will there be Hierarchical network ? How much of the Routes will be imported from external world ?<br>
3. Will there be Separate routing domain for overlay network ? Or it will be mixed with external/underlay network ?<br>
4. What will be the basic use case of this ? Thinking of L3 switching to support BGP-MPLS L3 VPN Scenario right from compute node ?<br>
<br>
Others can give their opinion also.<br>
<br>
Thanks & Regards,<br>
keshava<br>
<span class="im HOEnZb"><br>
-----Original Message-----<br>
From: Cory Benfield [mailto:<a href="mailto:Cory.Benfield@metaswitch.com">Cory.Benfield@metaswitch.com</a>]<br>
Sent: Tuesday, October 28, 2014 10:35 PM<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
</span><span class="im HOEnZb">Subject: Re: [openstack-dev] [neutron][nova] New specs on routed networking<br>
<br>
</span>
<div class="HOEnZb">
<div class="h5">On Tue, Oct 28, 2014 at 07:44:48, A, Keshava wrote:<br>
> Hi,<br>
><br>
> Current Open-stack was built as flat network.<br>
><br>
> With the introduction of the L3 lookup (by inserting the routing table<br>
> in forwarding path) and separate 'VIF Route Type' interface:<br>
><br>
> At what point of time in the packet processing decision will be made<br>
> to lookup FIB during ? For each packet there will additional FIB<br>
> lookup ?<br>
><br>
> How about the impact on 'inter compute traffic', processed by DVR ?<br>
> Here thinking OpenStack cloud as hierarchical network instead of Flat<br>
> network ?<br>
<br>
Keshava,<br>
<br>
It's difficult for me to answer in general terms: the proposed specs are general enough to allow multiple approaches to building purely-routed networks in OpenStack, and they may all have slightly different answers to some of these questions. I can, however,
speak about how Project Calico intends to apply them.<br>
<br>
For Project Calico, the FIB lookup is performed for every packet emitted by a VM and destined for a VM. Each compute host routes all the traffic to/from its guests. The DVR approach isn't necessary in this kind of network because it essentially already implements
one: all packets are always routed, and no network node is ever required in the network.<br>
<br>
The routed network approach doesn't add any hierarchical nature to an OpenStack cloud. The difference between the routed approach and the standard OVS approach is that packet processing happens entirely at layer 3. Put another way, in Project Calico-based networks
a Neutron subnet no longer maps to a layer 2 broadcast domain.<br>
<br>
I hope that clarifies: please shout if you'd like more detail.<br>
<br>
Cory<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>Kevin Benton</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>