Hi everyone,
Sorry, I couldn't make it in time for the IRC meeting.
Just saw in the logs:
15:19:12 <yamamoto> are orange folks here? they might want to
introduce their bgp speaker.
The best intro to BaGPipe BGP is the README on github:
https://github.com/Orange-OpenSource/bagpipe-bgp/blob/master/README.md
Beyond just speaking the BGP protocol on the wire, BaGPipe is a an
implementation of BGP VPNs (IP VPNs and E-VPNs) including the forwarding
part. It can be run as a service exposing a REST API, or a library
inside an agent; it handles the lifecylcle of VRFs and port
attached/detached from them and appropriately circulates event to/from
BGP peers based on VRF import/export rules and RTC publish/subscribe
semantics. It's complete enough to let us build neutron virtual
networks with IP VPNs, and interconnect them with external VPNs; the
parts for Opentsack integration are not on this github, I'm just
mentioning this for the sake of illustrating the relative maturity.
Although it does not address plain IP, this would I believe by a really
easy addition to make.
I'll do my best to attend next week IRC meeting, but until this, feel
free to ask. We can also do a Q&A session on IRC if that sounds convenient.
Best,
-Thomas
2014-06-13, YAMAMOTO Takashi:
an update after today's l3 meeting:
here's a new version of ryu bgp api patch.
http://sourceforge.net/p/ryu/mailman/message/32453021/
it has been merged to the ryu master.
https://github.com/osrg/ryu.git
here's formatted documentation:
http://ryu.readthedocs.org/en/latest/library_bgp_speaker.html
http://ryu.readthedocs.org/en/latest/library_bgp_speaker_ref.html
YAMAMOTO Takashi
YAMAMOTO Takashi
I have seen the Ryu team is involved and responsive to the community.
That goes a long way to support it as the reference implementation for
BPG speaking in Neutron. Thank you for your support. I'll look
forward to the API and documentation refinement
Let's be sure to document any work that needs to be done so that it
will support the features we need. We can use the comparison page for
now [1] to gather that information (or links). If Ryu is lacking in
any area, it will be good to understand the timeline on which the
features can be delivered and stable before we make a formal decision
on the reference implementation.
Carl
[1] https://wiki.openstack.org/wiki/Neutron/BGPSpeakersComparison
On Thu, Jun 5, 2014 at 10:36 AM, Jaume Devesa <devv...@gmail.com> wrote:
After watch the documentation and the code of exabgp and Ryu, I find the Ryu
speaker much more easy to integrate and pythonic than exabgp. I will use it
as well as reference implementation in the Dynamic Routing bp.
Regards,
On 5 June 2014 18:23, Nachi Ueno <na...@ntti3.com> wrote:
Yamamoto
Cool! OK, I'll make ryu based bgpspeaker as ref impl for my bp.
Yong
Ya, we have already decided to have the driver architecture.
IMO, this discussion is for reference impl.
2014-06-05 0:24 GMT-07:00 Yongsheng Gong <gong...@unitedstack.com>:
I think maybe we can device a kind of framework so that we can plugin
different BGP speakers.
On Thu, Jun 5, 2014 at 2:59 PM, YAMAMOTO Takashi
<yamam...@valinux.co.jp>
wrote:
hi,
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.
we (ryu team) love to hear any suggestions and/or requests.
we are currently working on our bgp api refinement and documentation.
hopefully they will be available early next week.
for both of bgp blueprints, it would be possible, and might be
desirable,
to create reference implementations in python using ryu or exabgp.
(i prefer ryu. :-)
YAMAMOTO Takashi
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@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@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
