netapp.ontap.na_ontap_service_policy module – NetApp ONTAP service policy configuration
Note
This module is part of the netapp.ontap collection (version 22.13.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_service_policy
.
New in netapp.ontap 21.7.0
Synopsis
Add, modify, or remove service policies.
This module requires ONTAP 9.8 or later, and only supports REST.
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 |
---|---|
As an alternative to updating the |
|
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. |
|
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:
|
|
Name of the ipspace. Required for cluster-scoped service policies. Optional for SVM-scoped service policies. |
|
path to SSL client key file. |
|
List of known services in 9.12.1 An error is raised if any service in Modify this list to restrict the services you want to support if needed. Default: |
|
The name of the service policy. |
|
Password for the specified user. |
|
Set to “svm” for interfaces owned by an SVM. Otherwise, set to “cluster”. svm is assumed if vserver is set. cluster is assumed is vserver is not set. Choices:
|
|
List of services to associate to this service policy. To remove all services, use “no_service”. No other value is allowed when no_service is present. Note - not all versions of ONTAP support all values, and new ones may be added. See |
|
Whether the specified service policy should exist or not. Choices:
|
|
This module only supports REST. always – will always use the REST API. A warning is issued if the module does not support REST. 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://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:
|
|
The name of the vserver to use. Omit this option for cluster scoped user accounts. |
Notes
Note
This module supports check_mode.
This module does not support ‘allowed-addresses’ as REST does not support it. It defaults to 0.0.0.0/0.
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 service policy
netapp.ontap.na_ontap_service_policy:
state: present
name: "{{ service_policy_name }}"
services:
- data_core
- data_nfs
vserver: ansibleVServer
hostname: "{{ netapp_hostname }}"
username: "{{ netapp_username }}"
password: "{{ netapp_password }}"
- name: Delete single service policy
netapp.ontap.na_ontap_service_policy:
state: absent
name: "{{ service_policy_name }}"
vserver: ansibleVServer
hostname: "{{ netapp_hostname }}"
username: "{{ netapp_username }}"
password: "{{ netapp_password }}"
- name: Modify single service policy
netapp.ontap.na_ontap_service_policy:
state: present
name: "{{ service_policy_name }}"
services:
- data_core
- data_nfs
- data_cifs
vserver: ansibleVServer
hostname: "{{ netapp_hostname }}"
username: "{{ netapp_username }}"
password: "{{ netapp_password }}"
- name: Modify service policy, remove services
netapp.ontap.na_ontap_service_policy:
state: present
name: "{{ service_policy_name }}"
services:
- no_service
vserver: "{{ vserver }}"
- name: Modify service policy at cluster level
netapp.ontap.na_ontap_service_policy:
state: present
name: "{{ service_policy_name }}"
ipspace: ansibleIpspace
scope: cluster
services:
- management_core
- management_autosupport
- management_ems
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
whether a public key is created or deleted. Returned: success |
|
attributes that were modified if the key already exists. Returned: success |