netapp.ontap.na_ontap_quota_policy – NetApp Ontap create, assign, rename or delete quota policy
Note
This plugin is part of the netapp.ontap collection (version 21.14.1).
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
.
To use it in a playbook, specify: netapp.ontap.na_ontap_quota_policy
.
New in version 19.11.0: of netapp.ontap
Requirements
The below requirements are needed on the host that executes this module.
Ansible 2.9
Python3 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.
To enable http on the cluster you must run the following commands ‘set -privilege advanced;’ ‘system services web modify -http-enabled true;’
Parameters
Parameter |
Comments |
---|---|
when true, assign the policy to the vserver, whether it is newly created, renamed, or already exists. when true, the policy identified by name replaces the already assigned policy. when false, the policy is created if it does not already exist but is not assigned. Choices:
|
|
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. |
|
Name of the existing quota policy to be renamed to name. |
|
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. |
|
Specifies the quota policy name to create or rename to. |
|
The ontap api version to use |
|
Password for the specified user. |
|
Whether the specified quota policy should exist or not. Choices:
|
|
REST API if supported by the target system for all the resources and attributes the module requires. Otherwise will revert to ZAPI. always – will always use the REST API never – will always use the ZAPI auto – will try to use the REST Api Default: “auto” |
|
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://mysupport.netapp.com/NOW/download/software/nmsdk/9.4/. 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:
|
|
Specifies the vserver for the quota policy. |
Examples
- name: Create quota policy
na_ontap_quota_policy:
state: present
vserver: SVM1
name: ansible_policy
hostname: "{{ hostname }}"
username: "{{ username }}"
password: "{{ password }}"
- name: Rename quota policy
na_ontap_quota_policy:
state: present
vserver: SVM1
name: new_ansible
from_name: ansible
hostname: "{{ hostname }}"
username: "{{ username }}"
password: "{{ password }}"
- name: Delete quota policy
na_ontap_quota_policy:
state: absent
vserver: SVM1
name: ansible_policy
hostname: "{{ hostname }}"
username: "{{ username }}"
password: "{{ password }}"
Authors
NetApp Ansible Team (@carchi8py) <ng-ansibleteam@netapp.com>