-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Add a Scaleway IP module #45121
Add a Scaleway IP module #45121
Conversation
@g1franc I started working on your dynamic IP management module. I will let you know once it is ready for review. |
The test
|
5625678
to
6834ee1
Compare
5e2f654
to
ac52b03
Compare
The test
|
ac52b03
to
2a1e798
Compare
2a1e798
to
21e3d73
Compare
The test
The test
The test
The test
The test
The test
The test
The test
|
21e3d73
to
9bd3288
Compare
Tested and working |
@Spredzy @maxamillion Could you merge it? |
@@ -29,6 +29,13 @@ | |||
|
|||
options: | |||
|
|||
dynamic_ip_required: | |||
description: | |||
- Enable a public IP at server creation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I propose to use:
- an hardcoded IP, for example:
163.172.152.10
(or scaleway address ID?) (IP must exist and be available in the pool of reserved IPs) - attached (create an IP which will be destroyed when the node will be destroyed)
- absent (don't use any public IP)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also think this would be advantageous.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Started working on it there: https://github.com/ansible/ansible/pull/44826/files
Could you review and merge it?
description: | ||
- id of the IP | ||
|
||
server: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should not that be handled by the scaleway_compute
module ?
argument_spec.update(dict( | ||
state=dict(default='present', choices=['absent', 'present']), | ||
organization=dict(), | ||
server=dict(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would let the scaleway_compute
handles IP assignation to server.
|
||
id: | ||
description: | ||
- id of the IP |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't make sense to use id
parameter with state=present
. Currently when state=present
is used and id
is specified, a new IP with another id
is created.
56fb225
to
f21ffde
Compare
@sieben a rebase is required for this one |
f21ffde
to
e73db82
Compare
Rebase done. I'm going to add additional tests for assigning ip to scaleway_compute |
The test
|
- Add an option to enable public ip at server creation
e73db82
to
2373ab1
Compare
rebuild_merge |
description: | ||
- id of the Scaleway IP (UUID) | ||
|
||
server: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't we agree that:
- this module should not handle that
- scaleway_compute should be used instead
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed but I guess we can fix it in another PR.
SUMMARY
This PR adds a management module for Scaleway reserved IP.
Here is the list of targeted features:
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION