Open Stack

Hi All,

On Mon, Apr 15, 2019 at 8:08 PM Zane Bitter <zbitter at redhat.com> wrote:
> On 15/04/19 1:23 PM, Slawomir Kaplonski wrote:
> > IMO option 2 provided by Bence is the best one here. This should be fixed in neutron API by making extra routes first class API objects and treat them as router interfaces. DB layer is „ready” for that IMO so it should be handled easy.
> > All other ways it will just be kind of workaround of the issue. Even if we will fix it in OpenStack SDK and/or neutron client there may be someone who is using API in some other way and will still hit the same issue.
>
> Oh, for sure. If Neutron is willing to do that then that is definitely
> the best solution.

I'm inclined to take that as a shared agreement to prefer way #2 over
the other alternatives brought up in this thread. That is first class
extra routes in neutron and adapt the heat resource to that.

I am willing to take up both the Neutron and Heat sides of this work
in the Train cycle if the projects agree this is a good idea to work
on and it is worth the review cycles. As a next step I'll write up a
Neutron RFE. And at least open a placeholder Heat blueprint - which
I'll be able to specify better when the first class extraroute Neutron
API is agreed on. Please expect these coming still before the PTG.
I'll be attending the Summit and the PTG in Denver so we can discuss
these in person if we feel that's needed at that time.

Thanks,
Bence