Hi Team,
As of today, ONTAP-MCP can create qos policy but cannot apply it to a volume. That would be great to have it available so we could gather from Harvest-MCP potential perf issue and resolv it applying QoS policy.
Prompt used:
----> Set up a QOS on this volume so it will allow a maximum of 200 IOPS
Answer:
----> The update_volume tool doesn't expose QoS fields, so let me look for an ONTAP PATCH/write tool to apply the QoS policy directly via REST.
The QoS policy qos_cifs1_200iops (200 IOPS max) was successfully created on svm1. However, the MCP update_volume tool doesn't expose QoS assignment fields, and there is no generic PATCH tool available to apply it to the volume through this interface.
David
Hi Team,
As of today, ONTAP-MCP can create qos policy but cannot apply it to a volume. That would be great to have it available so we could gather from Harvest-MCP potential perf issue and resolv it applying QoS policy.
Prompt used:
----> Set up a QOS on this volume so it will allow a maximum of 200 IOPS
Answer:
----> The update_volume tool doesn't expose QoS fields, so let me look for an ONTAP PATCH/write tool to apply the QoS policy directly via REST.
The QoS policy qos_cifs1_200iops (200 IOPS max) was successfully created on svm1. However, the MCP update_volume tool doesn't expose QoS assignment fields, and there is no generic PATCH tool available to apply it to the volume through this interface.
David