hitachivantara.vspone_block.sds_block.hv_sds_block_storage_pool module – Manages storage pool on Hitachi SDS Block storage systems.
Note
This module is part of the hitachivantara.vspone_block collection (version 4.2.0).
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 hitachivantara.vspone_block
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: hitachivantara.vspone_block.sds_block.hv_sds_block_storage_pool
.
New in hitachivantara.vspone_block 4.1.0
Synopsis
This module allows the expansion of the storage pool on Hitachi SDS Block storage systems.
For examples, go to URL https://github.com/hitachi-vantara/vspone-block-ansible/blob/main/playbooks/sds_block_direct/storage_pool.yml
Requirements
The below requirements are needed on the host that executes this module.
python >= 3.9
Parameters
Parameter |
Comments |
---|---|
Information required to establish a connection to the storage system. |
|
IP address or hostname of the storage system. |
|
Type of connection to the storage system. Choices:
|
|
Password for authentication. This is a required field. |
|
Username for authentication. This is a required field. |
|
Specification for the storage pool. |
|
The drive ids to be added to the pool. |
|
The ID of the storage pool. |
|
The name of the storage pool. |
|
The number of drive failures that can be tolerated. Must be in the range 0 to 23. |
|
Rebuild capacity policy. Fixed means secures capacity required for Rebuild as a fixed Rebuild-dedicated capacity. Variable means secures a part of user data capacity as rebuild capacity when the storage pool usage is low, and uses the capacity entirely as user data capacity when the storage pool usage increases. Choices:
|
|
The desired state of the storage pool. Choices:
|
Attributes
Attribute |
Support |
Description |
---|---|---|
Support: none |
Determines if the module should run in check mode. |
Examples
- name: Expand storage pool by pool name
hitachivantara.vspone_block.sds_block.hv_sds_block_storage_pool:
connection_info:
address: storage1.company.com
username: "admin"
password: "secret"
state: "expand"
spec:
name: "SP01"
drive_ids: ["6a14d3cb-264f-41b1-81c0-cdbfab73d358"]
- name: Expand storage pool by pool ID
hitachivantara.vspone_block.sds_block.hv_sds_block_storage_pool:
connection_info:
address: storage1.company.com
username: "admin"
password: "secret"
state: "expand"
spec:
id: "3f9bcecc-9ac5-4c21-abed-5b03e682e7b4"
drive_ids: ["6a14d3cb-264f-41b1-81c0-cdbfab73d358"]
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
A list of storage pools. Returned: always |
|
Information about the storage pool. Returned: success |
|
The blocked capacity in the effective physical capacity of the storage pool in MiB. Returned: success Sample: |
|
Capacity management. Returned: success |
|
Maximum reserve rate (unit -%). -1 indicates the capacity is unlimited. Returned: success Sample: |
|
The Depletion threshold (unit - %). Returned: success Sample: |
|
The depletion threshold of the storage controller managing the storage pool (unit - %) Returned: success Sample: |
|
The warning threshold (unit - %). Returned: success Sample: |
|
Usage rate (unit - %). Returned: success Sample: |
|
Redundancy of user data. Value of 0 means no redundancy, and -1 means that the user data has been lost. Returned: success Sample: |
|
The state of storage pool data encryption. Returned: success Sample: |
|
The available capacity of the storage pool in MiB. Returned: success Sample: |
|
The ID of the storage pool. Returned: success Sample: |
|
The capacity for control information in the total physical capacity of the storage pool in MiB. Returned: success Sample: |
|
The name of the storage pool. Returned: success Sample: |
|
The number of volumes belonging to the storage pool. Returned: success Sample: |
|
The total capacity of other volumes that have been created on this storage controller in MiB. Returned: success Sample: |
|
The ID of the protection domain to which the volume is belonging. Returned: success Sample: |
|
The total capacity of provisioned volumes that have been created on this storage controller in MiB. Returned: success Sample: |
|
Rebuild capacity policy. Returned: success Sample: |
|
Resource type and the number of resources of rebuild capacity. Returned: success |
|
The number of drive failures that can be tolerated. Returned: success Sample: |
|
The status of securing rebuild capacity. Returned: success Sample: |
|
Resource for which Rebuild is possible. Returned: success |
|
The number of drives for which Rebuild is possible. Returned: success Sample: |
|
User data protection method. Returned: success Sample: |
|
User data protection type. Returned: success Sample: |
|
The internally reserved area in the effective physical capacity of the storage pool in MiB. This area cannot be configured redundantly. Returned: success Sample: |
|
Effect of the data reduction function on the storage pool. Returned: success |
|
Date and time the calculation ended. Returned: success Sample: |
|
Date and time the calculation started. Returned: success Sample: |
|
Status of the reduction effect of the data reduction function. Returned: success Sample: |
|
Status of total efficiency. Returned: success Sample: |
|
The storage pool status. Returned: success Sample: |
|
The summary of the storage pool status. Returned: success Sample: |
|
Summary information about the capacity status of all the storage controllers managing the storage pool. Returned: success Sample: |
|
The total capacity of temporary volumes that have been created on this storage controller in MiB. Returned: success Sample: |
|
The logical capacity of the storage pool in MiB. Returned: success Sample: |
|
The total physical capacity of the storage pool in MiB. Returned: success Sample: |
|
The effective physical capacity in the total physical capacity of the storage pool in MiB. Returned: success Sample: |
|
The total capacity of volumes that have been created on this storage controller in MiB. Returned: success Sample: |
|
The capacity which can be used as the logical capacity in the effective physical capacity of the storage pool in MiB. Returned: success Sample: |
|
The used capacity of the storage pool in MiB. Returned: success Sample: |