netapp.ontap.na_ontap_kerberos_realm – NetApp ONTAP vserver nfs kerberos realm
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_kerberos_realm
.
New in version 2.9.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 |
---|---|
IP Address of the Active Directory Domain Controller (DC). This is a mandatory parameter if the kdc-vendor is ‘microsoft’. |
|
Host name of the Active Directory Domain Controller (DC). This is a mandatory parameter if the kdc-vendor is ‘microsoft’. |
|
IP address of the host where the Kerberos administration daemon is running. This is usually the master KDC. If this parameter is omitted, the address specified in kdc_ip is used. |
|
The TCP port on the Kerberos administration server where the Kerberos administration service is running. The default for this parmater is ‘749’ |
|
path to SSL client cert file (.pem). not supported with python 2.6. |
|
The clock skew in minutes is the tolerance for accepting tickets with time stamps that do not exactly match the host’s system clock. The default for this parameter is ‘5’ minutes. |
|
Optional comment |
|
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:
|
|
IP address of the Key Distribution Centre (KDC) server Required if state=present |
|
TCP port on the KDC to be used for Kerberos communication. The default for this parameter is ‘88’. |
|
The vendor of the Key Distribution Centre (KDC) server Required if state=present Choices:
|
|
path to SSL client key file. |
|
The ontap api version to use |
|
Password for the specified user. |
|
IP address of the host where the Kerberos password-changing server is running. Typically, this is the same as the host indicated in the adminserver-ip. If this parameter is omitted, the IP address in kdc-ip is used. |
|
The TCP port on the Kerberos password-changing server where the Kerberos password-changing service is running. The default for this parameter is ‘464’. |
|
Kerberos realm name |
|
Whether the Kerberos realm is present or absent. 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:
|
|
vserver/svm with kerberos realm configured |
Examples
- name: Create kerberos realm other kdc vendor
na_ontap_kerberos_realm:
state: present
realm: 'EXAMPLE.COM'
vserver: 'vserver1'
kdc_ip: '1.2.3.4'
kdc_vendor: 'other'
hostname: "{{ netapp_hostname }}"
username: "{{ netapp_username }}"
password: "{{ netapp_password }}"
- name: Create kerberos realm Microsoft kdc vendor
na_ontap_kerberos_realm:
state: present
realm: 'EXAMPLE.COM'
vserver: 'vserver1'
kdc_ip: '1.2.3.4'
kdc_vendor: 'microsoft'
ad_server_ip: '0.0.0.0'
ad_server_name: 'server'
hostname: "{{ netapp_hostname }}"
username: "{{ netapp_username }}"
password: "{{ netapp_password }}"
Authors
Milan Zink (@zeten30) <zeten30@gmail.com>,<mzink@redhat.com>