[New Resource]: SVM QoS Policy Activation

[acch]

Description

Ability to activate (existing) QoS policy for (existing) SVM

Requested Resource(s) and/or Data Source(s)

• netapp-ontap_svm_qos_policy_activation

Potential Terraform Configuration

// example SVM
resource "netapp-ontap_svm" "svm1" {
  name = "svm1"
}

// example policy
resource "netapp-ontap_qos_policies" "policy1" {
  name     = "policy1"
  svm_name = netapp-ontap_svm.svm1.name
}

// activate example policy for example SVM
resource "netapp-ontap_svm_qos_policy_activation" "svm1_policy1" { 
  svm_name        = netapp_ontap_svm.svm1.name
  qos_policy_name = netapp_ontap_qos_policies.policy1.name
}

References

• https://docs.netapp.com/us-en/ontap-restapi-9131/ontap/patch-svm-svms-.html

  # Updates the QoS policy for the SVM
  PATCH "/api/svm/svms/f16f0935-5281-11e8-b94d-005056b46485" '{"qos_policy_group":{"name":"qpolicy1"}}'
  

Would you like to implement a fix?

Yes

[carchi8py]

hmmmm we'll need to look at how we are going to do this. I don't think we need a specific resource for this and should be able to do it in SVM, but let me see how that would work.

[acch]

@carchi8py Thanks for looking into this!

My understanding is that QoS policy activation is a multi-step process (taken from here):

1. Create SVM: vserver create -vserver svm1
2. Create QoS policy: qos policy-group create -policy-group policy1 -vserver svm1
3. Apply policy group to SVM: vserver modify -vserver svm1 -qos-policy-group policy1

Creating the policy group is only possible after the SVM / vserver exists. Hence, activating it is a separate step - it can't be activated upon initial creation... but I might be missing something here!

That's why I've opted for a separate resource to model the association of SVM <-> policy. Again, this might be due to my limited understanding - let me know if there's a more elegant way to do it.

Thanks again, and all the best!
Achim