Open Stack

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.


On 30 May 2014 16:50, Nachi Ueno <nachi at ntti3.com> wrote:

> Hi folks
>
> ExaBGP won't suit for BGPVPN implementation because it isn't support vpnv4.
> Ryu is supporting it, however they have no internal api to binding
> neutron network & route target.
> so I think contrail is a only solution for  BGPVPN implementation now.
>
>
>
> 2014-05-30 2:22 GMT-07:00 Mathieu Rohon <mathieu.rohon at gmail.com>:
> > Hi,
> >
> > I was about mentionning ExaBGP too! can we also consider using those
> > BGP speakers for BGPVPN implementation [1].
> > This would be consistent to have the same BGP speaker used for every
> > BGP needs inside Neutron.
> >
> > [1]https://review.openstack.org/#/c/93329/
> >
> >
> > On Fri, May 30, 2014 at 10:54 AM, Jaume Devesa <devvesa at gmail.com>
> wrote:
> >> Hello Takashi,
> >>
> >> thanks for doing this! As we have proposed ExaBgp[1] in the Dynamic
> Routing
> >> blueprint[2], I've added a new column for this speaker in the wiki
> page. I
> >> plan to fill it soon.
> >>
> >> ExaBgp was our first choice because we thought that run something in
> library
> >> mode would be much more easy to deal with (especially the exceptions and
> >> corner cases) and the code would be much cleaner. But seems that Ryu BGP
> >> also can fit in this requirement. And having the help from a Ryu
> developer
> >> like you turns it into a promising candidate!
> >>
> >> I'll start working now in a proof of concept to run the agent with these
> >> implementations and see if we need more requirements to compare between
> the
> >> speakers.
> >>
> >> [1]: https://wiki.openstack.org/wiki/Neutron/BGPSpeakersComparison
> >> [2]: https://review.openstack.org/#/c/90833/
> >>
> >> Regards,
> >>
> >>
> >> On 29 May 2014 18:42, YAMAMOTO Takashi <yamamoto at valinux.co.jp> wrote:
> >>>
> >>> as per discussions on l3 subteem meeting today, i started
> >>> a bgp speakers comparison wiki page for this bp.
> >>>
> >>> https://wiki.openstack.org/wiki/Neutron/BGPSpeakersComparison
> >>>
> >>> Artem, can you add other requirements as columns?
> >>>
> >>> as one of ryu developers, i'm naturally biased to ryu bgp.
> >>> i appreciate if someone provides more info for other bgp speakers.
> >>>
> >>> YAMAMOTO Takashi
> >>>
> >>> > Good afternoon Neutron developers!
> >>> >
> >>> > There has been a discussion about dynamic routing in Neutron for the
> >>> > past few weeks in the L3 subteam weekly meetings. I've submitted a
> review
> >>> > request of the blueprint documenting the proposal of this feature:
> >>> > https://review.openstack.org/#/c/90833/. If you have any feedback or
> >>> > suggestions for improvement, I would love to hear your comments and
> include
> >>> > your thoughts in the document.
> >>> >
> >>> > Thank you.
> >>> >
> >>> > Sincerely,
> >>> > Artem Dmytrenko
> >>>
> >>> _______________________________________________
> >>> OpenStack-dev mailing list
> >>> OpenStack-dev at lists.openstack.org
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >>
> >>
> >>
> >> --
> >> Jaume Devesa
> >> Software Engineer at Midokura
> >>
> >> _______________________________________________
> >> OpenStack-dev mailing list
> >> OpenStack-dev at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140531/7ec7ebc3/attachment.html>