Bug 976456
| Summary: | [RFE] Allow floating IP to be assigned to a specific fixed address | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Russell Bryant <rbryant> |
| Component: | openstack-nova | Assignee: | Brent Eagles <beagles> |
| Status: | CLOSED ERRATA | QA Contact: | David Ripton <dripton> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | beagles, dallan, jkt, mlopes, ndipanov, nobody, oblaut, sclewis |
| Target Milestone: | Upstream M1 | Keywords: | FutureFeature, OtherQA |
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://blueprints.launchpad.net/nova/+spec/multi-nic-floating-ip-assignment | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-nova-2013.2-0.8.b2.el6ost | Doc Type: | Enhancement |
| Doc Text: |
Previously, it was not possible to specify which address should be associated with the instance's floating IP address.
With this enhancement, users are able to specify the fixed IP address that a floating IP should be mapped to.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-20 00:07:31 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: | 988939 | ||
| Bug Blocks: | 975499 | ||
|
Description
Russell Bryant
2013-06-20 15:29:21 UTC
Matched Priority to upstream Code matching patch is in current build (2013-12-16.1).
Feature appears to work. Test procedure followed:
- created two private networks as non-admin tenant
- ensure both are added to the router (neutron router-interface-add)
- booted a vm with the two networks, e.g.:
nova boot vm2 --flavor 1 --image cirros \
--nic net-id=83c72e42-50fd-4e9e-89fd-b55b05c93520 \
--nic net-id=03c99ed8-d91e-47e9-a971-5e23f50aadda \
--key-name labkey
- waited for VM to enter ACTIVE state and verify that both private IPs were allocated.
eef17d12-ca58-48bb-adf1-731d043679ef | vm1 | ACTIVE | None | Running | labnet=192.168.90.2; mechnet=192.168.100.2 |
- allocated floating IP to default interface:
nova add-floating-ip vm1 192.168.2.52
- ran nova list to verify assignment to first network listed, as expected for default behavior:
eef17d12-ca58-48bb-adf1-731d043679ef | vm1 | ACTIVE | None | Running | labnet=192.168.90.2, 192.168.2.52; mechnet=192.168.100.2
- removed floating ip
nova remove-floating-ip vm1 192.168.2.52
- ran nova list to verify floating IP is removed:
eef17d12-ca58-48bb-adf1-731d043679ef | vm1 | ACTIVE | None | Running | labnet=192.168.90.2; mechnet=192.168.100.2 |
- ran nova add-floating-ip with "--fixed-address" option:
nova add-floating-ip --fixed-address 192.168.100.2 vm1 192.168.2.52
- ran nova list to verify floating IP is attached to proper interface (the second):
eef17d12-ca58-48bb-adf1-731d043679ef | vm1 | ACTIVE | None | Running | labnet=192.168.90.2; mechnet=192.168.100.2, 192.168.2.52 |
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html |