> It is also possible to have a external=true network that isn't a floating IP network.
> We have a provider network that is external and users can attach a port from this network directly to their instance.
> They can't however use this network as a floating IP network.
I think there is some confusion on the usage of "router:external" and "shared" attributes.
- shared=True means users can attach a port from this network directly to their instance
- router:external=True means this network can be used as a floating IP network.
In addition, if you have two network as floating IP pools and expose one of them to a specific set of users and the other of them to another set of users, you can use "access_as_external" of network RBAC feature.
I would like to clarify whether you have use cases more than above.
> It is also possible to have a external=true network that isn't a floating IP network.
> We have a provider network that is external and users can attach a port from this network directly to their instance.
> They can't however use this network as a floating IP network.
I think there is some confusion on the usage of "router:external" and "shared" attributes.
- shared=True means users can attach a port from this network directly to their instance external= True means this network can be used as a floating IP network.
- router:
Looking at comment #11 (https:/ /bugs.launchpad .net/neutron/ +bug/1743480/ comments/ 11), you set both shared=True and router: external= True for both networks.
In addition, if you have two network as floating IP pools and expose one of them to a specific set of users and the other of them to another set of users, you can use "access_ as_external" of network RBAC feature.
I would like to clarify whether you have use cases more than above.