First of all, I don't have a devstack deployed environment. I have a multinode setup with 3 controllers and 2 compute nodes, so I needed to change the commands provided.
10.0.0.0/24 is the external network configured in my deployment. The other resources are:
* router_ext:
** ext_gw: 10.0.0.221
** net_int2: 10.20.0.1
* router_int:
** net_int2: 10.20.0.100
** net_int1: 10.10.0.1
I tried with different routers:
* dvr: no ping
* ha: no ping
* legacy: I can ping
That could not be considered as a feature but as a bug or at least a side effect of how legacy router is implemented. In any case, I've contacted the core OVN developers to know if this functionality is possible and how should be implemented in Neutron.
Hello Brian:
First of all, I don't have a devstack deployed environment. I have a multinode setup with 3 controllers and 2 compute nodes, so I needed to change the commands provided.
10.0.0.0/24 is the external network configured in my deployment. The other resources are:
* router_ext:
** ext_gw: 10.0.0.221
** net_int2: 10.20.0.1
* router_int:
** net_int2: 10.20.0.100
** net_int1: 10.10.0.1
The routes added: 10.10.0. 0/24,gateway= 10.20.0. 100 (net_int1, router_int net_int2 interface) 0.0.0.0/ 0,gateway= 10.20.0. 1 (*all*, router_ext net_int2 interface)
* router_ext: destination=
* router_int: destination=
I tried with different routers:
* dvr: no ping
* ha: no ping
* legacy: I can ping
That could not be considered as a feature but as a bug or at least a side effect of how legacy router is implemented. In any case, I've contacted the core OVN developers to know if this functionality is possible and how should be implemented in Neutron.
Regards.