Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Openstack: Ability to assign floating IP to specific network interface #4677

Closed
aunraza opened this issue Jan 14, 2016 · 8 comments · Fixed by #4812
Closed

Openstack: Ability to assign floating IP to specific network interface #4677

aunraza opened this issue Jan 14, 2016 · 8 comments · Fixed by #4812

Comments

@aunraza
Copy link

aunraza commented Jan 14, 2016

Hi, when trying to associate a floating IP to a compute instance with multiple networks, it is only possible to assign it to the first interface. Is it possible to change the functionality where it can be used to assign it to a specific fixed IP, similar to how it's mentioned in the Openstack docs:

If an instance is connected to multiple networks, you can associate a floating IP address with a specific fixed IP address using the optional --fixed-address parameter:

$ nova floating-ip-associate --fixed-address FIXED_IP_ADDRESS \
INSTANCE_NAME_OR_ID FLOATING_IP_ADDRESS

Thanks.

@jtopjian
Copy link
Contributor

Soon!

Thank you for the reminder. Support for this was just recently merged into Gophercloud, so now I can work on getting it done in Terraform.

@aunraza
Copy link
Author

aunraza commented Jan 15, 2016

Great news! Thanks!

On Fri, 15 Jan 2016 1:17 am Joe Topjian notifications@github.com wrote:

Soon!

Thank you for the reminder. Support for this was just recently merged
rackspace/gophercloud#403 into Gophercloud, so
now I can work on getting it done in Terraform.


Reply to this email directly or view it on GitHub
#4677 (comment)
.

-Aun

@aunraza
Copy link
Author

aunraza commented Jan 24, 2016

Hi Joe, when do you think we will be able to get this feature into terraform?

@jtopjian
Copy link
Contributor

Sorry for the delay -- although it sounds like a simple change, it required a significant reconfiguration.

#4812 has the proposed change. Would you be able to test it out similar to testing the Personalities feature?

@aunraza
Copy link
Author

aunraza commented Jan 25, 2016

Thanks Joe! Definitely can test it out.

@aunraza
Copy link
Author

aunraza commented Jan 25, 2016

Joe, it works! 👍

@jtopjian
Copy link
Contributor

Awesome, thank you very much for testing!

I'll leave this open for a few days to give other people a chance to comment. Although this patch doesn't break backwards compatibility, there are a lot of changes.

@ghost
Copy link

ghost commented Apr 28, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants