Add support for floating IPs

[Nell Jerram]

Although networking-calico prefers the use of externally reachable fixed IPs, floating IPs are still useful for supporting IP mobility when the VM does not need or want to be aware of the mobile IP address. This bug tracks the work that is needed for networking-calico's plugin to honour Neutron floating IP requests, and pass those on to the Calico Felix agent for implementation.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/253634
Committed: https://git.openstack.org/cgit/openstack/networking-calico/commit/?id=2c302e6bafe5cfe564b9816aa2a67a3a65508807
Submitter: Jenkins
Branch: master

commit 2c302e6bafe5cfe564b9816aa2a67a3a65508807
Author: Nick Bartos <email address hidden>
Date: Thu Oct 22 14:01:39 2015 +0100

    Add floating IP support in OpenStack plugin.

    This patch requires a version of Calico with floating IP NAT support,
    as noted here: https://github.com/projectcalico/calico/pull/848

    Also in this commit, the Calico server-side code changes from being an
    ML2 mechanism driver to a Neutron core plugin. The Calico plugin
    inherits from ML2 and so can still in principle do everything that ML2
    can; but the move simplifies Calico configuration and also sidesteps
    the cognitive dissonance of 'How can Calico L3-only networking be
    implemented as a Modular Layer 2 driver?'

    To use it, users will need to define neutron routers. These routers
    will be ignored by Calico itself, they only serve to allow neutron to
    assign floating IPs at all.

    Change-Id: I1fa2f56a5ce5e34a8653a35d7ebb666c4a844b2f
    Closes-Bug: #1519840
    Sem-Ver: feature

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/networking-calico 1.2.0 release.