nova-manage floating create interprets /32 range as being wider than the /31 range

[Eoghan Glynn]

The implementation of 'nova-manage floating create' special-cases the /32 address range, so that:

   a.b.c.d/32 => [a.b.c.d]

However the logic of netaddr.IPNetwork.iter_hosts() is such that:

   a.b.c.d/31 => []

So effectively the /32 range is wider than the /31 range, whereas intuitively the opposite should be the case.

[Eoghan Glynn (eglynn)]

The special-casing of /32 was introduced in:

  https://github.com/openstack/nova/commit/e430c842

as a work-around for the lack of ability to create a floating IP for a specific individual address.

This would be better achieved by just dropping the range altogether, such that:

  nova-manage floating create 192.168.1.150

creates a single flotaing IP address for that specific address.

This would avoid the contradictions inherent in how the /32 versus /31 ranges are currently handled.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/5227

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/5227
Committed: http://github.com/openstack/nova/commit/c5e51415282330030385304c5af8216e47b84991
Submitter: Jenkins
Branch: master

commit c5e51415282330030385304c5af8216e47b84991
Author: Eoghan Glynn <email address hidden>
Date: Mon Mar 12 10:27:24 2012 +0000

    Avoid nova-manage floating create <IP addr>/32

    Fixes bug 951161

    Avoid the counter-intuitive use of the /32 range to indicate a specific
    individial IP address.

    Instead a floating IP for a specific individual address is created by
    dropping the range specifier altogether, e.g.:

      nova-manage floating create 192.168.1.150

    Change-Id: I54b124e961accefa47f6faa7f201809c545c3fa5