Floating ips are always added to the host as a /32. You will need one ip on the
compute host from the floating range with the /16 prefix (which it will use for
natting instances without floating ips as well).
In other words you should manually assign an ip from 10.100.130.X/16 to each
compute
Thanks,
I managed to get it working by deleting the public pool (which was the
whole 10.100.X.X subnet) and creating a new pool 10.100.129.X.
This gives me control over which ips are assignable to the vms.
Eduard.
On Mon, Dec 22, 2014 at 7:30 PM, Vishvananda Ishaya vishvana...@gmail.com
wrote:
Hi,
I'm trying to create a vm and assign it an ip in range 10.100.130.0/16.
On the host, the ip is assigned to br100 as inet 10.100.0.3/32 scope
global br100
instead of 10.100.130.X/16, so it's not reachable from the outside.
The localrc.conf :
FLOATING_RANGE=10.100.130.0/16
Any idea what to
