I wanted to raise the question of whether to develop BGP dynamic routing in the Neutron repo or spin it out to as a stadium project. This question has been raised recently on reviews and in offline discussions. For those unfamiliar with this work, BGP efforts in Neutron entail admin-only API's for configuring and propagating BGP announcements of next-hops for floating IP's, tenant networks, and host routes for each compute port when using DVR. As we are getting late in the Mitaka cycle, I would like to be sure there is consensus on the approach for Mitaka. As I see it, we have 3 courses of action:
1. Continue with development in the main repo without any intention of spinning out to a stadium project 2. Continue on the current development course for Mitaka while targeting a spin-out to a stadium project during the N cycle 3. Spin out to a stadium project immediately Each has pros and cons. This question seems to have arisen while looking at the sheer amount code being proposed, its place in the Neutron model, and questioning whether we really want to bring that code into Neutron. As such, continuing with option 1 definitely requires us to come to some consensus. Let me be clear that I'm not opposed to any of these options, I'm simply looking for some guidance. With that said, if the end game is a stadium project I do question whether #2 makes sense. -Ryan https://review.openstack.org/#/c/201621/ https://review.openstack.org/#/q/topic:bp/bgp-dynamic-routing
__________________________________________________________________________ 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
