Open Stack

With OVS driver, how can you even get a VM up and running in Openstack


without the risk of melting the entire network down ?

Both the interfaces of the BITW VM are sitting on br-int.The risk of BUM packets looping between the two interfaces is very high.   Even if the BITW VM does not forward broadcast and multicast packetsacross the two interfaces, chances are it would forward "Unknown unicasts"resulting in looping of these packets between the two interfaces.

Consider a BITW BM with OF ports 1 and 2.  When "br-int"  floodsan "Unknown unicast packet" to ports 1 and 2, you essentially have a loop situation.


With OVN driver, this is no longer an issue since OVN knows where each and every unicast MAC address needs to be forwarded.  FLooding of "unknown unicasts" is not an issue with OVN.

Farhad.
 

----------------------------------------------------------------------

Message: 1
Date: Tue, 10 Jan 2017 20:43:50 +0530
From: Vikash Kumar <vikash.kumar at oneconvergence.com>
To: Vikram Choudhary <vikschw at gmail.com>
Cc: Openstack Milis <openstack at lists.openstack.org>
Subject: Re: [Openstack] [networking-sfc] SFC in BITW or L2 mode
Message-ID:
    <CAPHM3WbcG7kp+KYTDFT8SKeoY6s7N1G7dGr8hTVT2CDOG=JzrA at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

If thats the case then does it only support L3 mode as of now? My
experiment suggest same. With this limitation, it won't be possible to any
L2/BITW network functions.

On Tue, Jan 10, 2017 at 12:59 PM, Vikram Choudhary <vikschw at gmail.com>
wrote:

> networking-sfc doesn't care about the VNF deployment mode. If you see the
> API's, it's all about chaining neutron ports..
>
> On Tue, Jan 10, 2017 at 12:26 PM, Vikash Kumar <
> vikash.kumar at oneconvergence.com> wrote:
>
>> Which API specifies the mode of VNF (L3/L2/BITW) ? I need to insert a
>> Firewall in L2 mode.
>>
>> --
>> Regards,
>> Vikash
>>
>

   

   

   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20170112/d49e55e5/attachment.html>