Thank you Yuya!!

On Wed, Mar 4, 2020 at 11:58 AM Yuya KAWAKAMI <[email protected]> wrote:

> Hi Gyan and Robert,
>
>  > This could eliminate use of MLAG on the leaf switches
>
> Contrail/Tungsten just provide L2/L3 overlay routes to Compute via
> XMPP(MP-BGP), not support underlay multipath.
> At this time, vRouter of Contrail/Tungsten does not follow changes in the
> routing table of host OS.
> So there are still MLAG or Virtual-Chassis or VRRP and I'm struggling with
> them.
> This is just implementation issue and will be resolved in the future.
>
> Just for your information,
> Yuya
> SDN Tech Lead, NTT
>
> On 2020/03/03 9:07, Robert Raszuk wrote:
> > Hi Gyan,
> >
> > You are touching subject close to me so let me share my perspective on
> your doubts below ;)
> >
> >  > maybe some advantages of elimination of L2 to the host
> >
> > Not some but huge !
> >
> >  >  BGP multipath provides flow based uneven load balancing
> >
> > First Contrail/Tungsten does not use BGP to the hypervisor but XMPP. But
> this is opaque to your concern.
> >
> > Load balancing and hashing construction is your choice, BGP or XMPP only
> deliver you next hops .. how you spread traffic to them is 100% up to your
> choice. That is the same on hypervisor or on any decent router. LAGs also
> build hash in the way you configure them to do so..
> >
> >  >  hypervisor managed by server admins
> >
> > In any decent network or for that matter even in my lab this is all 100%
> automated. You run one template and execute it. Ansible works pretty well,
> but there are other choices too.
> >
> > Many thx,
> > R.
> >
> >
> > On Tue, Mar 3, 2020 at 1:00 AM Gyan Mishra <[email protected]
> <mailto:[email protected]>> wrote:
> >
> >
> >     Thanks Robert for the quick response
> >
> >     Just thinking out loud -  I can see there maybe some advantages of
> elimination of L2 to the host but the one major disadvantage is that BGP
> multipath provides flow based uneven load balancing so not as desirable
> from that standpoint compare to L3 MLAG bundle XOR Src/Dest/Port hash..
> >
> >     Other big down side is most enterprises have the hypervisor managed
> by server admins but if you run BGP now that ends up shifting to network.
> More complicated.
> >
> >     Kind regards
> >
> >     Gyan
> >
> >     On Mon, Mar 2, 2020 at 6:39 PM Robert Raszuk <[email protected]
> <mailto:[email protected]>> wrote:
> >
> >         Hi Gyan,
> >
> >         Similar architecture has been invented and shipped by Contrail
> team. Now that project after they got acquired by Juniper has been renamed
> to Tungsten Fabric https://tungsten..io/ <https://tungsten.io/> while
> Juniper continued to keep the original project's name and commercial flavor
> of it. No guarantees of any product quality at this point.
> >
> >         Btw ,,, no need for VXLAN nor BGP to the host. The proposed
> above alternative were well thought out and turned to work ways far more
> efficient and practical if you zoom into details.
> >
> >         Best,
> >         Robert.
> >
> >
> >         On Tue, Mar 3, 2020 at 12:26 AM Gyan Mishra <
> [email protected] <mailto:[email protected]>> wrote:
> >
> >
> >             Dear BESS WG
> >
> >             Is anyone aware of any IETF BGP development in the Data
> Center arena to extend BGP VXLAN EVPN to a blade server Hypervisor making
> the Hypervisor part of the  vxlan fabric.  This could eliminate use of MLAG
> on the leaf switches and eliminate L2 completely from the vxlan fabric
> thereby maximizing  stability.
> >
> >             Kind regards,
> >
> >             Gyan
> >             --
> >
> >             Gyan  Mishra
> >
> >             Network Engineering & Technology
> >
> >             Verizon
> >
> >             Silver Spring, MD 20904
> >
> >             Phone: 301 502-1347
> >
> >             Email: [email protected] <mailto:
> [email protected]>
> >
> >
> >
> >             _______________________________________________
> >             BESS mailing list
> >             [email protected] <mailto:[email protected]>
> >             https://www.ietf.org/mailman/listinfo/bess
> >
> >     --
> >
> >     Gyan  Mishra
> >
> >     Network Engineering & Technology
> >
> >     Verizon
> >
> >     Silver Spring, MD 20904
> >
> >     Phone: 301 502-1347
> >
> >     Email: [email protected] <mailto:[email protected]>
> >
> >
> >
> >
> > _______________________________________________
> > BESS mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/bess
> >
>
> _______________________________________________
> BESS mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/bess
>
-- 

Gyan  Mishra

Network Engineering & Technology

Verizon

Silver Spring, MD 20904

Phone: 301 502-1347

Email: [email protected]
_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess

Reply via email to