DescriptionGoutham Pacha Ravi
2022-08-25 19:12:18 UTC
Description of problem:
NetApp ONTAP storage systems are integrated into OpenStack Manila with the help of XML-based "ONTAPI"s called ZAPIs. In the 9.6 release of ONTAP, NetApp added a RESTful API that is meant to replace these ZAPIs. [1] Starting with ONTAP 9.7, new features and enhancements are available only through the ONTAP REST API for automation. ZAPIs are also deprecated and are slated for end-of-support and eventual removal from the product. Per [2], ZAPI will reach end of availability (EOA) in January 2023. (CPC-00410: EOA- ONTAPI [3]). ONTAP release in FY22-Q4 (expected to be ONTAP 9.12.1), will be the final ONTAP version to include ONTAPI.
So, The NetApp manila driver needs to add support to REST APIs in place of all the ZAPIs it is using. The upstream community is supportive of backporting this to Zed as long as it doesn't introduce any backwards incompatible change - i.e., ZAPIs must not be removed prematurely from code as deployers may continue to use older/supported versions of ONTAP storage with RHOSP.
Version-Release number of selected component (if applicable): 17
Affects future OSP 18, and OSP 16.2 as well.
Additional info:
[1] https://www.netapp.com/blog/restful-apis-now-natively-available-with-netapp-ontap-9-6-software/
[2] https://www.netapp.com/blog/transform-automation-ontap-rest-api/
[3] https://mysupport.netapp.com/info/communications/ECMLP2880232.html - Requires NetApp login
Removing target milestone. Netapp plans have changed and this RFE is not required for 17.1GA anymore. They are extending the ZAPI support and we are dependent on them to do the backports.
Removing PM ack. At the moment netapp does not plan to support this feature in wallaby (17.x) and do any backport. We're planning to build an OSP/ONTAP versions compatibility matrix.