ngine_io.vultr.vultr_server_baremetal module – Manages baremetal servers on Vultr.
Note
This module is part of the ngine_io.vultr collection (version 1.1.2).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install ngine_io.vultr
.
To use it in a playbook, specify: ngine_io.vultr.vultr_server_baremetal
.
New in version 0.3.0: of ngine_io.vultr
Requirements
The below requirements are needed on the host that executes this module.
python >= 2.6
Parameters
Parameter |
Comments |
---|---|
Name of the ini section in the The ENV variable Default: “default” |
|
URL to API endpint (without trailing slash). The ENV variable Fallback value is https://api.vultr.com if not specified. |
|
API key of the Vultr API. The ENV variable |
|
Amount of retries in case of the Vultr API retuns an HTTP 503 code. The ENV variable Fallback value is 5 retries if not specified. |
|
Retry backoff delay in seconds is exponential up to this max. value, in seconds. The ENV variable Fallback value is 12 seconds. |
|
HTTP timeout to Vultr API. The ENV variable Fallback value is 60 seconds if not specified. |
|
The hostname to assign to this server. |
|
Whether to enable IPv6 or not. Choices:
|
|
Name of the server. |
|
Whether to send an activation email when the server is ready or not. Only considered on creation. Choices:
|
|
The operating system name or ID. Required if the server does not yet exist and is not restoring from a snapshot. |
|
Plan name or ID to use for the server. Required if the server does not yet exist. |
|
Region name or ID the server is deployed into. Required if the server does not yet exist. |
|
IP address of the floating IP to use as the main IP of this server. Only considered on creation. |
|
List of SSH key names or IDs passed to the server on creation. |
|
Name or ID of the startup script to execute on boot. Only considered while creating the server. |
|
State of the server. Choices:
|
|
Tag for the server. |
|
User data to be passed to the server. |
|
Validate SSL certs of the Vultr API. Choices:
|
Notes
Note
Also see the API documentation on https://www.vultr.com/api/.
Examples
- name: create server
ngine_io.vultr.vultr_server_baremetal:
name: "{{ vultr_server_baremetal_name }}"
os: Debian 9 x64 (stretch)
plan: 32768 MB RAM,2x 240 GB SSD,5.00 TB BW
region: Amsterdam
- name: ensure a server is absent
ngine_io.vultr.vultr_server_baremetal:
name: "{{ vultr_server_baremetal_name }}"
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Response from Vultr API with a few additions/modification Returned: success |
|
Account used in the ini file to select the key Returned: success Sample: “default” |
|
Amount of max retries for the API requests Returned: success Sample: 5 |
|
Timeout used for the API requests Returned: success Sample: 60 |
|
Response from Vultr API with a few additions/modification Returned: success |
|
Allowed bandwidth to use in GB Returned: success Sample: 1000 |
|
Cost per month for the server Returned: success Sample: 120.0 |
|
Current bandwidth used for the server Returned: success Sample: 0 |
|
Date when the server was created Returned: success Sample: “2017-04-12 18:45:41” |
|
Password to login as root into the server Returned: success Sample: “ab81u!ryranq” |
|
Information about the disk Returned: success Sample: “SSD 250 GB” |
|
ID of the server Returned: success Sample: 900000 |
|
Internal IP Returned: success Sample: “” |
|
Name (label) of the server Returned: success Sample: “ansible-test-baremetal” |
|
Operating system used for the server Returned: success Sample: “Debian 9 x64” |
|
Pending charges Returned: success Sample: 0.18 |
|
Plan used for the server Returned: success Sample: “32768 MB RAM,2x 240 GB SSD,5.00 TB BW” |
|
Information about the RAM size Returned: success Sample: “32768 MB” |
|
Region the server was deployed into Returned: success Sample: “Amsterdam” |
|
Status about the deployment of the server Returned: success Sample: “active” |
|
Server tag Returned: success Sample: “my tag” |
|
IPv4 gateway Returned: success Sample: “203.0.113.1” |
|
Main IPv4 Returned: success Sample: “203.0.113.10” |
|
Netmask IPv4 Returned: success Sample: “255.255.255.0” |
|
Main IPv6 Returned: success Sample: “2001:DB8:9000::100” |
|
Network IPv6 Returned: success Sample: “2001:DB8:9000::” |
|
Network size IPv6 Returned: success Sample: 64 |
|
Networks IPv6 Returned: success Sample: [] |
Authors
Nate River (@vitikc)
Simon Baerlocher (@sbaerlocher)