netapp.ontap.na_ontap_nvme_subsystem module – NetApp ONTAP Manage NVME Subsystem
Note
This module is part of the netapp.ontap collection (version 22.14.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.ontap.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: netapp.ontap.na_ontap_nvme_subsystem.
New in netapp.ontap 2.8.0
Synopsis
Create/Delete NVME subsystem
Associate(modify) host/map to NVME subsystem
NVMe service should be existing in the data vserver with NVMe protocol as a pre-requisite
Requirements
The below requirements are needed on the host that executes this module.
Ansible 2.9 or later - 2.12 or later is recommended.
Python3 - 3.9 or later is recommended.
When using ZAPI, netapp-lib 2018.11.13 or later (install using ‘pip install netapp-lib’), netapp-lib 2020.3.12 is strongly recommended as it provides better error reporting for connection issues.
A physical or virtual clustered Data ONTAP system, the modules support Data ONTAP 9.1 and onward, REST support requires ONTAP 9.6 or later.
Parameters
Parameter |
Comments |
|---|---|
path to SSL client cert file (.pem). not supported with python 2.6. |
|
Enable or disable a new feature. This can be used to enable an experimental feature or disable a new feature that breaks backward compatibility. Supported keys and values are subject to change without notice. Unknown keys are ignored. |
|
Override the cluster ONTAP version when using REST. The behavior is undefined if the version does not match the target cluster. This is provided as a work-around when the cluster version cannot be read because of permission issues. See https://github.com/ansible-collections/netapp.ontap/wiki/Known-issues. This should be in the form 9.10 or 9.10.1 with each element being an integer number. When Ignored with ZAPI. |
|
The hostname or IP address of the ONTAP instance. |
|
List of host NQNs (NVMe Qualification Name) associated to the controller. |
|
Override the default port (80 or 443) with this port |
|
Enable and disable https. Ignored when using REST as only https is supported. Ignored when using SSL certificate authentication as it requires SSL. Choices:
|
|
path to SSL client key file. |
|
The ontap api version to use |
|
Specifies the ostype for initiators Choices:
|
|
Password for the specified user. |
|
List of Namespace paths to be associated with the subsystem. |
|
Skip host check Required to delete an NVMe Subsystem with attached NVMe namespaces Choices:
|
|
Skip mapped namespace check Required to delete an NVMe Subsystem with attached NVMe namespaces Choices:
|
|
Whether the specified subsystem should exist or not. Choices:
|
|
Specifies the subsystem |
|
Whether to use REST or ZAPI. always -- will always use the REST API if the module supports REST. A warning is issued if the module does not support REST. An error is issued if a module option is not supported in REST. never -- will always use ZAPI if the module supports ZAPI. An error may be issued if a REST option is not supported in ZAPI. auto -- will try to use the REST API if the module supports REST and modules options are supported. Reverts to ZAPI otherwise. Default: |
|
This can be a Cluster-scoped or SVM-scoped account, depending on whether a Cluster-level or SVM-level API is required. For more information, please read the documentation https://docs.netapp.com/us-en/ontap/authentication/create-svm-user-accounts-task.html. Two authentication methods are supported
To use a certificate, the certificate must have been installed in the ONTAP cluster, and cert authentication must have been enabled. |
|
If set to This should only set to Choices:
|
|
Name of the vserver to use. |
Notes
Note
The modules prefixed with na_ontap are built to support the ONTAP storage platform.
https is enabled by default and recommended. To enable http on the cluster you must run the following commands ‘set -privilege advanced;’ ‘system services web modify -http-enabled true;’
Examples
- name: Create NVME Subsystem
netapp.ontap.na_ontap_nvme_subsystem:
state: present
subsystem: test_sub
vserver: test_dest
ostype: linux
hostname: "{{ netapp_hostname }}"
username: "{{ netapp_username }}"
password: "{{ netapp_password }}"
- name: Delete NVME Subsystem
netapp.ontap.na_ontap_nvme_subsystem:
state: absent
subsystem: test_sub
vserver: test_dest
skip_host_check: true
skip_mapped_check: true
hostname: "{{ netapp_hostname }}"
username: "{{ netapp_username }}"
password: "{{ netapp_password }}"
- name: Associate NVME Subsystem host/map
netapp.ontap.na_ontap_nvme_subsystem:
state: present
subsystem: "{{ subsystem }}"
ostype: linux
hosts: nqn.1992-08.com.netapp:sn.3017cfc1e2ba11e89c55005056b36338:subsystem.ansible
paths: /vol/ansible/test,/vol/ansible/test1
vserver: "{{ vserver }}"
hostname: "{{ netapp_hostname }}"
username: "{{ netapp_username }}"
password: "{{ netapp_password }}"
- name: Modify NVME subsystem map
netapp.ontap.na_ontap_nvme_subsystem:
state: present
subsystem: test_sub
vserver: test_dest
skip_host_check: true
skip_mapped_check: true
paths: /vol/ansible/test
hostname: "{{ netapp_hostname }}"
username: "{{ netapp_username }}"
password: "{{ netapp_password }}"