yahoo-eng-team team mailing list archive

[OpenStack Infra <1226003@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/516417
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=dd0eba2128a892bddef563b09e4a28122c50f458
Submitter: Zuul
Branch:    master

commit dd0eba2128a892bddef563b09e4a28122c50f458
Author: Akihiro Motoki <amotoki@xxxxxxxxx>
Date:   Mon Oct 30 18:09:44 2017 +0000

    Support simple FIP disassociation (with FIP release)
    
    We previously supported so-called "Simple FIP disassociation"
    which allows users to disassociate and release a FIP in a single action.
    We no longer support nova-network based features, but I believe it is worth
    implemented even in a neutron-only era. This patch introduces a checkbox
    "Release floating IP" to support this with neutron.
    
    At the same time, this patch also fixes a bug that the existing FIP
    disassociation action disassociates and releases a first FIP of
    a requested server. Even though it is a rare case where a single
    server has multiple FIPs, this is a bug. After this patch, FIPs
    associated with the requested server are listed in the form and
    a user can select an FIP to be disassociated.
    
    This patch drops a setting parameter 'simple_ip_management' without
    deprecation notice. This is actually no side effect because this setting
    just toggled the FIP disassociate action in the instance table and
    it provides nothing more than that. We can do the same thing by
    the policy file.
    
    Change-Id: Ie8053bdd3a3e4c7897c7c906788d40c2a1d3f708
    Closes-Bug: #1226003


** Changed in: horizon
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1226003

Title:
  Inconsistent simple_ip_management behavior with Neutron

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Neutron does not (yet?) support the mechanism behind
  simple_ip_management (see e.g.
  https://bugs.launchpad.net/horizon/+bug/1196541). But it seems Horizon
  is only checking for support when associating a floating IP, but not
  when disassociating it. Association will show the non-simple behavior
  ("pick your IP") but Disassociation will show simple behavior
  ("disassociate and release immediately").

  Thus, the behavior is highly inconsistent, if Neutron is used for
  Networking and simple_ip_management is on (default).

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1226003/+subscriptions