The Ansible Modules for Dell Technologies (Dell) Unity allow Data Center and IT administrators to use RedHat Ansible to automate and orchestrate the configuration and management of Dell Unity arrays.
The capabilities of the Ansible modules are managing consistency groups, filesystem, filesystem snapshots, NAS server, NFS export, SMB share, hosts, snapshots, snapshot schedules, storage pools, user quotas, quota trees and volumes; and to gather facts from the array. The options available for each are list, show, create, modify and delete. These tasks can be executed by running simple playbooks written in yaml syntax. The modules are written so that all the operations are idempotent, so making multiple identical requests has the same effect as making a single request.
The Ansible collection for Unity is released and licensed under the GPL-3.0 license. See LICENSE for the full terms. Ansible modules and modules utilities that are part of the Ansible collection for Unity are released and licensed under the Apache 2.0 license. See MODULE-LICENSE for the full terms.
The Ansible collection for Unity are supported by Dell and are provided under the terms of the license attached to the collection. Please see the LICENSE section for the full terms. Dell does not provide any support for the source code modifications. For any Ansible modules issues, questions or feedback, join the Dell Automation Community.
- Dell Unity Arrays version 5.0, 5.1.2
This table provides information about the software prerequisites for the Ansible Modules for Dell Unity.
| Ansible Modules | Red Hat Enterprise Linux | Python version | Python library version | Ansible |
|---|---|---|---|---|
| v1.3.0 | 8.4 8.5 |
3.7 3.8 3.9 |
1.2.10 | 2.10 2.11 2.12 |
The modules are written in such a way that all requests are idempotent and hence fault-tolerant. It essentially means that the result of a successfully performed request is independent of the number of times it is executed.
- Consistency group module
- Filesystem module
- Filesystem snapshot module
- Info module
- Host module
- NAS server module
- NFS export module
- SMB share module
- Snapshot module
- Snapshot schedule module
- Storage pool module
- User quota module
- Quota tree module
- Volume module
Install python sdk named 'storops'. It can be installed using pip, based on appropriate python version.
pip install storops
- Use the following command to build the collection from source code:
ansible-galaxy collection build
For more details on how to build a tar ball, refer: Building the collection
- Use the following command to install the latest collection hosted in galaxy:
ansible-galaxy collection install dellemc.unity -p <install_path>
- Download the latest tar build from any of the available distribution channel Ansible Galaxy /Automation Hub and use the following command to install the collection anywhere in your system:
ansible-galaxy collection install dellemc-unity-1.3.0.tar.gz -p <install_path>
- Set the environment variable:
export ANSIBLE_COLLECTIONS_PATHS=$ANSIBLE_COLLECTIONS_PATHS:<install_path>
- In order to use any Ansible module, ensure that the importing of a proper FQCN (Fully Qualified Collection Name) must be embedded in the playbook. Refer to the following example:
collections:
- dellemc.unity
- In order to use an installed collection specific to the task use a proper FQCN (Fully Qualified Collection Name). Refer to the following example:
tasks:
- name: Get Volume details
dellemc.unity.volume
- For generating Ansible documentation for a specific module, embed the FQCN before the module name. Refer to the following example:
ansible-doc dellemc.unity.info
The Ansible server must be configured with Python library for Unity to run the Ansible playbooks. The Documents provide information on different Ansible modules along with their functions and syntax. The parameters table in the Product Guide provides information on various parameters which need to be configured before running the modules.
NOTE: These modules are supported through CA certified certificate only, however a self-signed certificate is not supported.
- Copy the CA certificate to this "/etc/pki/ca-trust/source/anchors" path of the host by any external means.
- Set the "REQUESTS_CA_BUNDLE" environment variable to the path of the SSL certificate using the command "export REQUESTS_CA_BUNDLE=/etc/pki/ca-trust/source/anchors/<<Certificate_Name>>"
- Import the SSL certificate to host using the command "update-ca-trust".
Each module returns the updated state and details of the entity, For example, if you are using the Volume module, all calls will return the updated details of the volume. Sample result is shown in each module's documentation.