- name: Create volume on source cluster na_ontap_volume: state: present name: "{{ src_vol_fg }}" aggr_list: "{{ src_aggr_list }}" aggr_list_multiplier: 2 type: RW size: 2 encrypt: true size_unit: tb space_guarantee: none wait_for_completion: false vserver: "{{ src_vserver }}" junction_path: /local/{{ src_vol_fg }} hostname: "{{ src_hostname }}" username: "{{ username }}" password: "{{ password }}"
#Hello, I am told that ansible modules originally using ZAPI can easily be converted to REST. How?
1 messages · Page 1 of 1 (latest)
We have the documentation for Ontapi to REST mapping
https://docs.netapp.com/us-en/ontap-automation/migrate/mapping.html
System Manager also allows you to download common workflows
This is not a 'raw API' question. This question belongs in the #1062048885847117935 channel.
More than likely, it's an upgrade the netapp.ontap collections to a certain version and do not explicitly define ZAPI. That's how most the various NetApp.ONTAP packages are transitioning.
https://galaxy.ansible.com/ui/repo/published/netapp/ontap/docs/
Deprecation warning
The ONTAP 9.12.1 release will be the last ONTAP version to support ONTAPI (ZAPI). Future versions of ONTAP will only support REST. This change will effect the modules listed below.
Based on that, I'd say be on a version of the collection that supports 9.12.1 and later to get mostly REST APIs. Then it depends on your ONTAP version you're running against.
Oh, I see you did post this question over in the Ansible channel and got a good response there. 🙂
that info is quite outdated, ZAPI is still supported in 9.14 and will be supported (I think) at least until 9.17 or something? Can't find the doc at the moment that has the updated info