netapp_eseries.santricity.netapp_e_flashcache module – NetApp E-Series manage SSD caches
Note
This module is part of the netapp_eseries.santricity collection (version 1.3.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 netapp_eseries.santricity
.
To use it in a playbook, specify: netapp_eseries.santricity.netapp_e_flashcache
.
New in version 2.2: of netapp_eseries.santricity
Parameters
Parameter |
Comments |
---|---|
The password to authenticate with the SANtricity WebServices Proxy or embedded REST API. |
|
The url to the SANtricity WebServices Proxy or embedded REST API. |
|
The username to authenticate with the SANtricity WebServices Proxy or embedded REST API. |
|
The minimum size (in size_units) of the ssd cache. The cache will be expanded if this exceeds the current size of the cache. |
|
Type of physical disk Choices:
|
|
The minimum number of disks to use for building the cache. The cache will be expanded if this number exceeds the number of disks already in place |
|
List of disk references |
|
The type of workload to optimize the cache for. Choices:
|
|
Log mode |
|
Log path |
|
The name of the SSD cache to manage |
|
The unit to be applied to size arguments Choices:
|
|
The ID of the array to manage (as configured on the web services proxy). |
|
Whether the specified SSD cache should exist or not. Choices:
|
|
Should https certificates be validated? Choices:
|
Examples
- name: Flash Cache
netapp_e_flashcache:
ssid: "{{ ssid }}"
api_url: "{{ netapp_api_url }}"
api_username: "{{ netapp_api_username }}"
api_password: "{{ netapp_api_password }}"
validate_certs: "{{ netapp_api_validate_certs }}"
name: SSDCacheBuiltByAnsible
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Success message Returned: success Sample: “json for newly created flash cache” |
Authors
Kevin Hulquest (@hulquest)