netapp.ontap.na_ontap_zapit module – NetApp ONTAP Run any ZAPI on ONTAP
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_zapit.
New in netapp.ontap 20.4.0
Synopsis
- Call a ZAPI on ONTAP. 
- Cluster ZAPIs are run using a cluster admin account. 
- Vserver ZAPIs can be run using a vsadmin account or using vserver tunneling (cluster admin with vserver option). 
- In case of success, a json dictionary is returned as - response.
- In case of a ZAPI error, - status,- errno,- reasonare set to help with diagnosing the issue,
- and the call is reported as an error (‘failed’). 
- Other errors (eg connection issues) are reported as Ansible error. 
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. | |
| The hostname or IP address of the ONTAP instance. | |
| 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 | |
| Password for the specified user. | |
| This module only supports ZAPI and can not be swtiched to 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 always use ZAPI. 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: 
 | |
| if provided, forces vserver tunneling. username identifies a cluster admin account. | |
| A dictionary for the zapi and arguments. An XML tag <tag>value</tag> is a dictionary with tag as the key. Value can be another dictionary, a list of dictionaries, a string, or nothing. eg <tag/> is represented as tag: A single zapi can be called at a time. Ansible warns if duplicate keys are found and only uses the last entry. | 
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: Ontap ZAPI
  hosts: localhost
  gather_facts: false
  vars:
    login: &login
      hostname: "{{ netapp_hostname }}"
      username: "{{ netapp_username }}"
      password: "{{ netapp_password }}"
      https: true
      validate_certs: false
    svm_login: &svm_login
      hostname: "{{ svm_admin_ip }}"
      username: "{{ svm_admin_username }}"
      password: "{{ svm_admin_password }}"
      https: true
      validate_certs: false
  tasks:
    - name: Run ontap ZAPI command as cluster admin
      netapp.ontap.na_ontap_zapit:
        <<: *login
        zapi:
          system-get-version:
      register: output
    - name: Print info
      ansible.builtin.debug:
        var: output
    - name: Run ontap ZAPI command as cluster admin
      netapp.ontap.na_ontap_zapit:
        <<: *login
        zapi:
          vserver-get-iter:
      register: output
    - name: Run ontap ZAPI command as cluster admin
      netapp.ontap.na_ontap_zapit:
        <<: *login
        zapi:
          vserver-get-iter:
            desired-attributes:
              vserver-info:
                - aggr-list:
                    - aggr-name
                - allowed-protocols:
                    - protocols
                - vserver-aggr-info-list:
                    - vserser-aggr-info
                - uuid
            query:
              vserver-info:
                vserver-name: trident_svm
      register: output
    - name: Run ontap ZAPI command as vsadmin
      netapp.ontap.na_ontap_zapit:
        <<: *svm_login
        zapi:
          vserver-get-iter:
            desired-attributes:
              vserver-info:
                - uuid
      register: output
    - name: Run ontap ZAPI command as vserver tunneling
      netapp.ontap.na_ontap_zapit:
        <<: *login
        vserver: ansibleSVM
        zapi:
          vserver-get-iter:
            desired-attributes:
              vserver-info:
                - uuid
      register: output
    - name: Run ontap active-directory ZAPI command
      netapp.ontap.na_ontap_zapit:
        <<: *login
        vserver: ansibleSVM
        zapi:
          active-directory-account-create:
            account-name: testaccount
            admin-username: testuser
            admin-password: testpass
            domain: testdomain
            organizational-unit: testou
      register: output
      ignore_errors: true
Return Values
Common return values are documented here, the following are the fields unique to this module:
| Key | Description | 
|---|---|
| If the ZAPI was executed but failed, the error code set by the ZAPI. Not present if successful, or if the ZAPI call cannot be performed. Returned: On error | |
| If the ZAPI was executed but failed, the error reason set by the ZAPI. Not present if successful, or if the ZAPI call cannot be performed. Returned: On error | |
| If successful, a json dictionary representing the data returned by the ZAPI. If the ZAPI was executed but failed, an empty dictionary. Not present if the ZAPI call cannot be performed. Returned: On success | |
| If the ZAPI was executed but failed, the status set by the ZAPI. Not present if successful, or if the ZAPI call cannot be performed. Returned: On error | 
