update priority range in htb qos (#1688)

kubeovn · Jul 14, 2022 · 8bc1b16 · 8bc1b16
1 parent ef4673d
commit 8bc1b16
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 7 deletions.
diff --git a/docs/qos.md b/docs/qos.md
@@ -38,7 +38,7 @@ spec:
               type: object
               properties:
                 priority:
-                  type: string					# Value in range 0 to 4,294,967,295.
+                  type: string					# Value in range 0 to 7.
   scope: Cluster
   names:
     plural: htbqoses
@@ -52,9 +52,9 @@ The spec parameter has only one field, `htbqoses.spec.priority`, which value rep
 ```
 mac@bogon kube-ovn % kubectl get htbqos
 NAME            PRIORITY
-htbqos-high     100
-htbqos-low      300
-htbqos-medium   200
+htbqos-high     1
+htbqos-low      5
+htbqos-medium   3
 ```
 Specific priority values are unimportant, only relative ordering matters. The smaller the priority value, the higher the QoS priority.
 

diff --git a/pkg/controller/init.go b/pkg/controller/init.go
@@ -703,11 +703,11 @@ func (c *Controller) initHtbQos() error {
 
 		switch qosName {
 		case util.HtbQosHigh:
-			priority = "100"
+			priority = "1"
 		case util.HtbQosMedium:
-			priority = "200"
+			priority = "3"
 		case util.HtbQosLow:
-			priority = "300"
+			priority = "5"
 		default:
 			klog.Errorf("qos %s is not default defined", qosName)
 		}