Implement NetApp ONTAP REST API Client
Currently, NetApp ONTAP Manila driver implements ZAPI client [0] to communicate with ONTAP back ends.
ZAPI client code sends HTTP(S) POST methods carrying XML data describing the operation to be issued, and receives responses containing XML data to be parsed.
ONTAP >= 9.6 provides a RESTful API [1] as an alternative to ZAPI. Also, the ZAPI will be deprecate soon.
This blueprint is to implement RESTful API client in the ONTAP NetApp driver to communicate with ONTAP back ends.
[0] https:/
[1] https:/
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Felipe Rodrigues
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
NetApp ONTAP: Implemented REST transition Client
Addressed by: https:/
NetApp ONTAP: REST transition - DHSS False Basic operations
Addressed by: https:/
NetApp ONTAP: REST transition - Data motion related functions
Addressed by: https:/
NetApp ONTAP: REST transition - DHSS True functions
Addressed by: https:/
WIP:NetApp: Improve REST API cover and fix internals
Addressed by: https:/
NetApp: Improve REST API cover and fix internals
