[Openstack-operators] [Neutron] Floating IPs / Router Gateways

Jacob Godin jacobgodin at gmail.com
Tue Apr 14 21:12:35 UTC 2015

Thanks Kevin. That might work in some instances, however our tenants have
the ability to create their own routers and allocate their gateway. I
suppose we could hack some code in to restrict what networks are usable for
routers vs floating IPs.

On Tue, Apr 14, 2015 at 6:08 PM, Kevin Benton <blak111 at gmail.com> wrote:

> Probably not in the way you want.
> You can have two subnets on the external network. Then you would set the
> allocation pool to be nothing for the subnet that you want the router
> interfaces to be attached to to make sure floating IPs aren't allocated
> from it. Then whenever you attach a router interface you would need to
> explicitly set the IP address to something from the first subnet.
> This obviously won't work well if you want it to automatically happen for
> tenants, but it might work if you are setting up the infrastructure
> yourself.
> On Tue, Apr 14, 2015 at 10:56 AM, Jacob Godin <jacobgodin at gmail.com>
> wrote:
>> Hi folks,
>> Looking for a bit of advice on how to accomplish something with Neutron.
>> Our setup uses OVS+GRE with isolated tenant networks. Currently, we have
>> one large network servicing our Floating IPs as well as our external router
>> interfaces.
>> What we're looking to do is actually have two distinct networks handle
>> these tasks. One for FIPs and another for routers.
>> Is this possible?
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> --
> Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150414/b08b622a/attachment.html>

More information about the OpenStack-operators mailing list