Hi Matt, Jaume did an awesome work at proposing and implementing a framework for announcing public IP with a BGP speaker [1]. Unfortunately, the spec hasn't been merged in kilo. Hope it will be resubmitted in L. Your proposal seems to be a mix of Jaume proposal and HA router design?
We also play with a BGP speaker (BagPipe[3], derived from ExaBGP, written in python) for IPVPN attachment [2]. [1]https://blueprints.launchpad.net/neutron/+spec/bgp-dynamic-routing [2]https://launchpad.net/bgpvpn [3]https://github.com/Orange-OpenSource/bagpipe-bgp On Thu, Apr 9, 2015 at 3:54 PM, Kyle Mestery <mest...@mestery.com> wrote: > On Thu, Apr 9, 2015 at 2:13 AM, Matt Grant <m...@mattgrant.net.nz> wrote: > >> Hi! >> >> I am just wondering what the story is about joining the neutron team. >> Could you tell me if you are looking for new contributors? >> >> We're always looking for someone new to participate! Thanks for reaching > out! > > >> Previously I have programmed OSPFv2 in Zebra/Quagga, and worked as a >> router developer for Allied Telesyn. I also have extensive Python >> programming experience, having worked on the DNS Management System. >> >> Sounds like you have extensive experience programming network elements. :) > > >> I have been experimenting with IPv6 since 2008 on my own home network, >> and I am currently installing a Juno Openstack cluster to learn ho >> things tick. >> >> Great, this will give you an overview of things. > > >> Have you guys ever figured out how to do a hybrid L3 North/South Neutron >> router that propagates tenant routes and networks into OSPF/BGP via a >> routing daemon, and uses floating MAC addresses/costed flow rules via >> OVS to fail over to a hot standby router? There are practical use cases >> for such a thing in smaller deployments. >> >> BGP integration with L3 is something we'll look at again for Liberty. > Carl Baldwin leads the L3 work in Neutron, and would be a good person to > sync with on this work item. I suspect he may be looking for people to help > integrate the BGP work in Liberty, this may be a good place for you to jump > in. > > I have a single stand alone example working by turning off >> neutron-l3-agent network name space support, and importing the connected >> interface and static routes into Bird and Birdv6. The AMPQ connection >> back to the neutron-server is via the upstream interface and is secured >> via transport mode IPSEC (just easier than bothering with https/SSL). >> Bird looks easier to run from neutron as they are single process than a >> multi process Quagga implementation. Incidentally, I am running this in >> an LXC container. >> >> Nice! > > >> Could some one please point me in the right direction. I would love to >> be in Vancouver :-) >> >> If you're not already on #openstack-neutron on Freenode, jump in there. > Plenty of helpful people abound. Since you're in New Zealand, I would > suggest reaching out to Akihiro Motoki (amotoki) on IRC, as he's in Japan > and closer to your timezone. > > Thanks! > Kyle > > Best Regards, >> >> -- >> Matt Grant, Debian and Linux Systems Administration and Consulting >> Mobile: 021 0267 0578 >> Email: m...@mattgrant.net.nz >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev