<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Inquiry Regarding Planned API Enhancements for Storage and Network Endpoints in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Inquiry-Regarding-Planned-API-Enhancements-for-Storage-and-Network-Endpoints/m-p/457457#M44424</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Dear NetApp Team,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I am reaching out to inquire whether there are any plans to introduce additional fields in NetApp's REST API for storage and network resources. Specifically, I am interested in knowing if the following enhancements are on the roadmap:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;STRONG&gt;RAID status&lt;/STRONG&gt; for the GET /api/storage/aggregates endpoint.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Position&lt;/STRONG&gt; for the GET /api/storage/disks endpoint.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Share-state&lt;/STRONG&gt; for the GET /api/storage/luns endpoint.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Operational duplex&lt;/STRONG&gt; for the GET /api/network/ethernet/ports endpoint.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Oplocks&lt;/STRONG&gt; for the GET /api/storage/qtrees endpoint.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;These fields would greatly enhance automation and monitoring capabilities, and I would appreciate any insights you can provide on the potential timeline for these additions or if they are currently under consideration.&lt;/P&gt;&lt;P&gt;Thank you for your assistance, and I look forward to your response.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Best regards,&lt;/STRONG&gt;&lt;BR /&gt;Oleksandr Dubrovyk&lt;BR /&gt;Software Engineer&lt;BR /&gt;Zenoss&lt;BR /&gt;odubrovyk@zenoss.com&lt;/P&gt;</description>
    <pubDate>Wed, 18 Dec 2024 09:12:52 GMT</pubDate>
    <dc:creator>odubrovyk</dc:creator>
    <dc:date>2024-12-18T09:12:52Z</dc:date>
    <item>
      <title>Inquiry Regarding Planned API Enhancements for Storage and Network Endpoints</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Inquiry-Regarding-Planned-API-Enhancements-for-Storage-and-Network-Endpoints/m-p/457457#M44424</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Dear NetApp Team,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I am reaching out to inquire whether there are any plans to introduce additional fields in NetApp's REST API for storage and network resources. Specifically, I am interested in knowing if the following enhancements are on the roadmap:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;STRONG&gt;RAID status&lt;/STRONG&gt; for the GET /api/storage/aggregates endpoint.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Position&lt;/STRONG&gt; for the GET /api/storage/disks endpoint.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Share-state&lt;/STRONG&gt; for the GET /api/storage/luns endpoint.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Operational duplex&lt;/STRONG&gt; for the GET /api/network/ethernet/ports endpoint.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Oplocks&lt;/STRONG&gt; for the GET /api/storage/qtrees endpoint.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;These fields would greatly enhance automation and monitoring capabilities, and I would appreciate any insights you can provide on the potential timeline for these additions or if they are currently under consideration.&lt;/P&gt;&lt;P&gt;Thank you for your assistance, and I look forward to your response.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Best regards,&lt;/STRONG&gt;&lt;BR /&gt;Oleksandr Dubrovyk&lt;BR /&gt;Software Engineer&lt;BR /&gt;Zenoss&lt;BR /&gt;odubrovyk@zenoss.com&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 09:12:52 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Inquiry-Regarding-Planned-API-Enhancements-for-Storage-and-Network-Endpoints/m-p/457457#M44424</guid>
      <dc:creator>odubrovyk</dc:creator>
      <dc:date>2024-12-18T09:12:52Z</dc:date>
    </item>
  </channel>
</rss>

