Bug 983577
Summary: | [RFE][neutron]: support automatic disassociation of floating IPs | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Brent Eagles <beagles> |
Component: | RFEs | Assignee: | RHOS Maint <rhos-maint> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 4.0 | CC: | chrisw, lpeer, markmc, nyechiel, srevivo, yeylon |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://blueprints.launchpad.net/neutron/+spec/auto-associate-floating-ip | ||
Whiteboard: | upstream_milestone_next upstream_status_not-started upstream_definition_obsolete | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-03-23 16:28:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 988874 | ||
Bug Blocks: |
Description
Brent Eagles
2013-07-11 13:52:34 UTC
The ability to "auto-associate" has been moved off of havana. The work on disassociate still seems to be in progress. While I had paired the two blueprints together as they are functionally complimentary, they are quite different with respect to complexity of implementation. Automatically diassociating an IP is relatively straightforward. The general step to testing this would be to associate an IP with a VM and then delete the vm. Running "quantum floatingip-list" should show that the floatingip is no longer associated with a fixed ip address. I'm altering the title of this bz to reflect the change in scope detail. Set to next upstream The feature is not targeted to Icehouse. updating the bug to reflect u/s status |