<div dir="ltr"><div>I've tested exabgp against a v6 peer, and it's an independent feature, so I added that as a row separately from whether v6 advertisements work. Might be worth making the page general and adding in the vpn feature set too.<br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 30 May 2014 16:50, Nachi Ueno <span dir="ltr"><<a href="mailto:nachi@ntti3.com" target="_blank">nachi@ntti3.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi folks<br>
<br>
ExaBGP won't suit for BGPVPN implementation because it isn't support vpnv4.<br>
Ryu is supporting it, however they have no internal api to binding<br>
neutron network & route target.<br>
so I think contrail is a only solution for BGPVPN implementation now.<br>
<br>
<br>
<br>
2014-05-30 2:22 GMT-07:00 Mathieu Rohon <<a href="mailto:mathieu.rohon@gmail.com">mathieu.rohon@gmail.com</a>>:<br>
<div class="HOEnZb"><div class="h5">> Hi,<br>
><br>
> I was about mentionning ExaBGP too! can we also consider using those<br>
> BGP speakers for BGPVPN implementation [1].<br>
> This would be consistent to have the same BGP speaker used for every<br>
> BGP needs inside Neutron.<br>
><br>
> [1]<a href="https://review.openstack.org/#/c/93329/" target="_blank">https://review.openstack.org/#/c/93329/</a><br>
><br>
><br>
> On Fri, May 30, 2014 at 10:54 AM, Jaume Devesa <<a href="mailto:devvesa@gmail.com">devvesa@gmail.com</a>> wrote:<br>
>> Hello Takashi,<br>
>><br>
>> thanks for doing this! As we have proposed ExaBgp[1] in the Dynamic Routing<br>
>> blueprint[2], I've added a new column for this speaker in the wiki page. I<br>
>> plan to fill it soon.<br>
>><br>
>> ExaBgp was our first choice because we thought that run something in library<br>
>> mode would be much more easy to deal with (especially the exceptions and<br>
>> corner cases) and the code would be much cleaner. But seems that Ryu BGP<br>
>> also can fit in this requirement. And having the help from a Ryu developer<br>
>> like you turns it into a promising candidate!<br>
>><br>
>> I'll start working now in a proof of concept to run the agent with these<br>
>> implementations and see if we need more requirements to compare between the<br>
>> speakers.<br>
>><br>
>> [1]: <a href="https://wiki.openstack.org/wiki/Neutron/BGPSpeakersComparison" target="_blank">https://wiki.openstack.org/wiki/Neutron/BGPSpeakersComparison</a><br>
>> [2]: <a href="https://review.openstack.org/#/c/90833/" target="_blank">https://review.openstack.org/#/c/90833/</a><br>
>><br>
>> Regards,<br>
>><br>
>><br>
>> On 29 May 2014 18:42, YAMAMOTO Takashi <<a href="mailto:yamamoto@valinux.co.jp">yamamoto@valinux.co.jp</a>> wrote:<br>
>>><br>
>>> as per discussions on l3 subteem meeting today, i started<br>
>>> a bgp speakers comparison wiki page for this bp.<br>
>>><br>
>>> <a href="https://wiki.openstack.org/wiki/Neutron/BGPSpeakersComparison" target="_blank">https://wiki.openstack.org/wiki/Neutron/BGPSpeakersComparison</a><br>
>>><br>
>>> Artem, can you add other requirements as columns?<br>
>>><br>
>>> as one of ryu developers, i'm naturally biased to ryu bgp.<br>
>>> i appreciate if someone provides more info for other bgp speakers.<br>
>>><br>
>>> YAMAMOTO Takashi<br>
>>><br>
>>> > Good afternoon Neutron developers!<br>
>>> ><br>
>>> > There has been a discussion about dynamic routing in Neutron for the<br>
>>> > past few weeks in the L3 subteam weekly meetings. I've submitted a review<br>
>>> > request of the blueprint documenting the proposal of this feature:<br>
>>> > <a href="https://review.openstack.org/#/c/90833/" target="_blank">https://review.openstack.org/#/c/90833/</a>. If you have any feedback or<br>
>>> > suggestions for improvement, I would love to hear your comments and include<br>
>>> > your thoughts in the document.<br>
>>> ><br>
>>> > Thank you.<br>
>>> ><br>
>>> > Sincerely,<br>
>>> > Artem Dmytrenko<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>
>><br>
>><br>
>> --<br>
>> Jaume Devesa<br>
>> Software Engineer at Midokura<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>
> _______________________________________________<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></div>