The create command via cidr is just a convienience to create a bunch of floating ips at once, floating ips are actually individual entries in the db. It should skip the network and gateway addressses by default, but it is perfectly acceptable to delete individual addresses with
nova-manage floating delete 10.243.30.17 (for example) You need to leave off the /XX to specify a single address. Vish On Aug 2, 2012, at 10:59 AM, Lars Kellogg-Stedman <l...@seas.harvard.edu> wrote: > If I create a floating address range like this: > > nova-manage floating create --ip_range=10.243.30.0/24 > > Is there any way to "block out" specific addresses in that range? For > example, the .1 address is the network gateway, and everything will > fall apart if that address is accidentally allocated to an instance. > > Similarly, our host needs an address in that range in order to route > traffic to the gateway. > > Is there any way to exempt specific addresses? I realize that instead > of allocating a /24 I could allocate a series of, say, /28 networks, > but that seems a little clumsy. > > Thanks, > > -- > Lars Kellogg-Stedman <l...@seas.harvard.edu> | > Senior Technologist | > http://ac.seas.harvard.edu/ > Academic Computing | > http://code.seas.harvard.edu/ > Harvard School of Engineering and Applied Sciences | > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
