Subnet delete for IPv6 SLAAC should not require prior port disassoc

[Dane LeBlanc]

With the current Neutron implementation, a subnet cannot be deleted
until all associated IP addresses have been removed from ports (via
port update) or the associated ports/VMs have been deleted.

In the case of SLAAC-enabled subnets, however, it's not feasible to
require removal of SLAAC-generated addresses individually from each
associated port before deleting a subnet because of the multicast
nature of RA messages. For SLAAC-enabled subnets, the processing of
subnet delete requests needs to be changed so that these subnets will
be allowed to be deleted, and all ports get disassociated from their
corresponding SLAAC IP address, when there are ports existing
on the SLAAC subnet.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/134978
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ce5e95723925b0d7750bb3daa5be54765985cc30
Submitter: Jenkins
Branch: master

commit ce5e95723925b0d7750bb3daa5be54765985cc30
Author: Dane LeBlanc <email address hidden>
Date: Mon Nov 17 10:40:04 2014 -0500

    Subnet delete for IPv6 SLAAC should not require prior port disassoc

    With the current Neutron implementation, a subnet cannot be deleted
    until all associated IP addresses have been remove from ports (via
    port update) or the associated ports/VMs have been deleted.

    In the case of SLAAC-enabled subnets, however, it's not feasible to
    require removal of SLAAC-generated addresses individually from each
    associated port before deleting a subnet because of the multicast
    nature of RA messages. For SLAAC-enabled subnets, the processing of
    subnet delete requests needs to be changed so that these subnets will
    be allowed to be deleted, and all ports get disassociated from their
    corresponding SLAAC IP address, when there are ports existing on
    the SLAAC subnet.

    Change-Id: I281f5a1553248e09174dc49d0a42aef4b5c44bee
    Closes-Bug: 1393435

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/juno
Review: https://review.openstack.org/137030

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/137030
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=63b43376b3818a28af496d3a6f4e6957df9427f2
Submitter: Jenkins
Branch: stable/juno

commit 63b43376b3818a28af496d3a6f4e6957df9427f2
Author: Dane LeBlanc <email address hidden>
Date: Mon Nov 17 10:40:04 2014 -0500

    Subnet delete for IPv6 SLAAC should not require prior port disassoc

    With the current Neutron implementation, a subnet cannot be deleted
    until all associated IP addresses have been remove from ports (via
    port update) or the associated ports/VMs have been deleted.

    In the case of SLAAC-enabled subnets, however, it's not feasible to
    require removal of SLAAC-generated addresses individually from each
    associated port before deleting a subnet because of the multicast
    nature of RA messages. For SLAAC-enabled subnets, the processing of
    subnet delete requests needs to be changed so that these subnets will
    be allowed to be deleted, and all ports get disassociated from their
    corresponding SLAAC IP address, when there are ports existing on
    the SLAAC subnet.

    Change-Id: I281f5a1553248e09174dc49d0a42aef4b5c44bee
    Closes-Bug: 1393435
    (cherry picked from commit ce5e95723925b0d7750bb3daa5be54765985cc30)

[OpenStack Infra (hudson-openstack)]

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