ngine_io.vultr.vultr_block_storage module – Manages block storage volumes 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_block_storage
.
New in version 0.1.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 ID of the server the volume is attached to. Required if state is attached. |
|
Whether the volume should be attached/detached, even if the server not stopped. Choices:
|
|
Name of the block storage volume. |
|
Region the block storage volume is deployed into. Required if state is present. |
|
Size of the block storage volume in GB. Required if state is present. If it’s larger than the volume’s current size, the volume will be resized. |
|
State of the block storage volume. Choices:
|
|
Validate SSL certs of the Vultr API. Choices:
|
Notes
Note
Also see the API documentation on https://www.vultr.com/api/.
Examples
- name: Ensure a block storage volume is present
ngine_io.vultr.vultr_block_storage:
name: myvolume
size: 10
region: Amsterdam
- name: Ensure a block storage volume is absent
ngine_io.vultr.vultr_block_storage:
name: myvolume
state: absent
- name: Ensure a block storage volume exists and is attached to server 114
ngine_io.vultr.vultr_block_storage:
name: myvolume
state: attached
attached_to_id: 114
size: 10
- name: Ensure a block storage volume exists and is not attached to any server
ngine_io.vultr.vultr_block_storage:
name: myvolume
state: detached
size: 10
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 |
|
Exponential backoff delay in seconds between retries up to this max delay value. Returned: success Sample: 12 |
|
Timeout used for the API requests Returned: success Sample: 60 |
|
Response from Vultr API Returned: success |
|
The ID of the server the volume is attached to Returned: success Sample: “10194376” |
|
Cost per month for the volume Returned: success Sample: 1.0 |
|
Date when the volume was created Returned: success Sample: “2017-08-26 12:47:48” |
|
ID of the block storage volume Returned: success Sample: “1234abcd” |
|
Name of the volume Returned: success Sample: “ansible-test-volume” |
|
Region the volume was deployed into Returned: success Sample: “New Jersey” |
|
Information about the volume size in GB Returned: success Sample: 10 |
|
Status about the deployment of the volume Returned: success Sample: “active” |
Authors
Yanis Guenane (@Spredzy)