<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Ian,<br>
<br>
Ian Wells :<br>
</div>
<blockquote
cite="mid:CAPoubz5e6brBamF-5f0VOvZWCRH1aaP2Lg088JfjRwoJzoBYrg@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr"><br>
<div class="gmail_extra">
<div class="gmail_quote">
<div>When you say things like 'tenant = VRF' (and, in fact,
I presume you mean 'network = VRF', since networks and
tenants are two different things) then that's actually
more to do with how you implement the networking overlay
layer in Neutron. While interesting, and while it could
potentially use a BGP speaker and VRFs to do it, it's not
the same use case as advertising routes externally, or
terminating an external MPLS VPN in Openstack. I could do
either of those things independently of the other.
Terminating VPNs requires an extension API and could
potentially glue on to a current plugin (much like
VPNaaS). Writing overlays is a new plugin entirely.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Indeed.<br>
<br>
<blockquote
cite="mid:CAPoubz5e6brBamF-5f0VOvZWCRH1aaP2Lg088JfjRwoJzoBYrg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>
<br>
There's a use for BGP speakers in both arenas (and
additionally within the distributed virtual router, which
is a third case) so perhaps we could address who's using
which speaker for precisely what?<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
We plan to propose an implementation of the BGP VPN interconnection
API ( <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/93329/1">https://review.openstack.org/#/c/93329/1</a> ) that will use
BaGPipe BGP for IP VPN VRF.<br>
And we are also working on a mechanism driver that will use BaGPipe
BGP and E-VPN/VXLAN.<br>
<br>
Best,<br>
<br>
-Thomas<br>
</body>
</html>