Comment 6 for bug 1959699

Revision history for this message
Sebastian Lohff (sebageek) wrote :

What I want is that the user is unable to allocate the gateway IP as a floating IP.

> " If allocation_pools are not specified, OpenStack Networking automatically allocates pools for covering all IP addresses in the CIDR, excluding the address reserved for the subnet gateway by default."

This describes what I want, but does not work if the user specifies an IP address. The problem is that the user can specify (and therefore allocate) the gateway IP of the CIDR. The gateway IP is excluded in the allocation pool of my subnet, but the user is _still able to allocate IPs outside the allocation pool_. So what I'm proposing is to not allow the user to allocate floating IPs outside of the allocation pool of a subnet (desired state) instead of allowing them to allocate everything in the CIDR including the gateway IP even if outside of the allocation pool (current state).

The test attached in the original post should illustrate that behavior. Gateway IP is outside of allocation pool, but the test is still able to allocate it as a floating IP.

I hope that clears my intentions up a bit, but if not I'm happy to clarify further and discuss my assumptions about OpenStack's floating IP allocation approach.