-
-
Notifications
You must be signed in to change notification settings - Fork 32
Picking a particular IP address for a Network #30
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
mmmm, now it seems to be working. |
it should but I have just verified that we don't have an integration test for that particular example. |
I verified in code and I confirm, this isn't implemented, it seems https://cloudstack.apache.org/api/apidocs-4.9/apis/associateIpAddress.html |
I think it is at least partially implemented. Because when it happens to give the right IP will not try to assign another IP on subsequent calls. I can implement the test case and fix it, if u want. |
When my testing failed a new IP got acquired on each call. Now there is idempotency in the calls. |
When using the UI it is possible to select a particular IP to acquire for a Virtual Network.
I have tried to replicate the same functionality with the cs_ip_address module, but it does not work. The documentation states that the IP address is required for the release functionality, and I guess that it is being ignored on acquisition.
For example, consider 123.123.123.123 a public IP address associated with our ACS account.
The following call:
Will assign a random IP form the public pull, but not the requested one.
The text was updated successfully, but these errors were encountered: