Question/clarification about qos-queue-config

The qos-queue-config grouping in openconfig-qos-elements is a template which needs to be applied to interface?
If so shouldn't we have the queue name under openconfig-qos-interface refer to qos-queue-config?

If it is different, why do we have queue name configurable under openconfig-qos-interface ?

Hi there, Can you be more specific? Are you referring to /qos/interfaces/interface/input/queues/queue/config/name?

public/release/models/qos/openconfig-qos-interfaces.yang

Lines 286 to 300 in aec94a1

    
               leaf name { 
        
                 // TODO(robjs): Previously we proposed that the queue name here is 
        
                 // only a queue that has been configured. However, in some cases we 
        
                 // may want to have queues that have not been configured exist. 
        
                 //type leafref { 
        
                 //  path "../../../../../../queues/queue/config/name"; 
        
                 //} 
        
                 type string; 
        
                 description 
        
                   "Reference to the queue associated with this interface. 
        
                   A queue may be explicitly configured, or implicitly created 
        
                   by the system based on default queues that are instantiated 
        
                   by a hardware component, or are assumed to be default on 
        
                   the system."; 
        
               }

The purpose of this leaf is to associate a named queue with the interface. ref: openconfig qos overview

Hi, yes, i am refering /qos/interfaces/interface/input/queues/queue/config/name

I hope named queue is created at /qos/queues/queue/config/name in which case, we need to have this path mentioned under /qos/interfaces/interface/input/queues/queue/config/name as like it is done under /qos/forwarding-groups/forwarding-group/config/output-queue

or both are different?

Hi, yes, i am refering /qos/interfaces/interface/input/queues/queue/config/name

I hope named queue is created at /qos/queues/queue/config/name in which case, we need to have this path mentioned under /qos/interfaces/interface/input/queues/queue/config/name as like it is done under /qos/forwarding-groups/forwarding-group/config/output-queue

or both are different?

See example QoS config for details on the configuration and how interfaces are included.

Queues are associated with a list of interfaces by setting this leaf-ref to the /qos/interfaces/interface/config/interface-id

Hi, yes, i am refering /qos/interfaces/interface/input/queues/queue/config/name
I hope named queue is created at /qos/queues/queue/config/name in which case, we need to have this path mentioned under /qos/interfaces/interface/input/queues/queue/config/name as like it is done under /qos/forwarding-groups/forwarding-group/config/output-queue
or both are different?

See example QoS config for details on the configuration and how interfaces are included.

Queues are associated with a list of interfaces by setting this leaf-ref to the /qos/interfaces/interface/config/interface-id

in the example QoS config there is no reference for /qos/interfaces/interface/input/queues/queue/config/name

Can we have the leaf /qos/interfaces/interface/input/queues/queue/config/name as leaf-reference to /qos/queues/queue/config/name

	leaf name {
	// TODO(robjs): Previously we proposed that the queue name here is
	// only a queue that has been configured. However, in some cases we
	// may want to have queues that have not been configured exist.
	//type leafref {
	// path "../../../../../../queues/queue/config/name";
	//}
	type string;
	description
	"Reference to the queue associated with this interface.
	A queue may be explicitly configured, or implicitly created
	by the system based on default queues that are instantiated
	by a hardware component, or are assumed to be default on
	the system.";
	}