#QoS Policy Cluster Scoped

1 messages · Page 1 of 1 (latest)

dim cosmos
#

I am trying to create new policies in OnTap 9.11 and trying to scope them to cluster.
error i m getting
"error_message": "Field "scope" cannot be set in this operation",
"msg": "Error when calling '/storage/qos/policies': {'target': 'scope'}",

based on https://library.netapp.com/ecmdocs/ECMLP2882307/html/#/storage/qos_policy_create
"scope": "cluster" is a valid option.
I am using ansible Module ' netapp.ontap.na_ontap_restit:' and body looks like this
body:
name: abhiClusterFixedQosTest
fixed:
max_throughput_iops: 0
capacity_shared: true
max_throughput_mbps: 0
min_throughput_iops: 0
min_throughput_mbps: 0
svm:
name: "abhitest001"
scope: 'svm' # or scope: 'cluster' but neither works

Code works if i am not using scope as an option but then the policy is created for SVM,

more details here #1082967001770774538 message
this is error code 262196 Field cannot be set in this operation.
This was added in 9.11
Scope (9.11) string
Scope of the entity. Set to "cluster" for cluster owned objects and to "svm" for SVM owned objects.

Enum:
[ cluster, svm ]

Thanks for any inputs.
Abhi

barren flax
#

AFAIK, cluster is only allowed for some preset policies, and not for user defined ones. The user can only use scope : "svm". That is because users can only create QoS policies which belong/owned by a SVM (vserver).

dim cosmos
#

Thanks @barren flax , seems this was changed in Ontap 9.11. Netapp added Scope and that can be (in theory) set to Cluster or SVM. This was informed by Netapp to my manager and now we are trying to figure out how to apply it. you can check the docs link i have mentioned in the original post.

barren flax
#

hi @dim cosmos , It seems like a bug to me, the intention of that was to only apply for GET requests and not for POST/PATCH. The swagger docs need to be fixed.

dim cosmos
#

I found it in documentation later, first someone from Netapp informed my manager, as this will avoid creating hundreds of QoS Policies in our case. So not sure if its just bug in documentation.

ruby nebula
#

we've observed that while the user-defined scope is related to an svm, it appears to implement at the cluster level

For example, a qos policy is created on an svm, it is also consumable by other svms.
if you try to use the same qos policy name on different svms, it will not allow it (duplicate entry)
and if you go to delete it, it does not allow the vserver to be specified

barren flax
#

For example, a qos policy is created on an svm, it is also consumable by other svms.
=> AFAIK That should not be possible, there should be an ownership check while assigning the qos policy.