-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Comments
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. |
Great news! Thanks! On Fri, 15 Jan 2016 1:17 am Joe Topjian [email protected] wrote:
-Aun |
Hi Joe, when do you think we will be able to get this feature into terraform? |
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? |
Thanks Joe! Definitely can test it out. |
Joe, it works! 👍 |
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. |
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. |
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:
Thanks.
The text was updated successfully, but these errors were encountered: