QoS "isRoot" rationale?

KRB <alagalah@...>

FYI, for those like me who were wondering why QoS is part of root set. Implementation decision for usability. 

Begin forwarded message:

From: Justin Pettit <jpettit@...>
Date: December 9, 2013 at 1:59:27 PM PST
To: alagalah <alagalah@...>
Cc: "discuss@..." <discuss@...>
Subject: Re: QoS "isRoot" rationale?

On Dec 9, 2013, at 1:16 PM, alagalah <alagalah@...> wrote:

I was wondering if someone could explain the rationale behind the QoS Table having "isRoot"=True?

I understand why Queues has it, but wasn't sure as to why QoS ?

Is this simply to preserve it from garbage collection so QoS configurations can be re-used without losing them if the last reference in Port is removed?

In short, yes.  Here's an explanation from when the code went in that goes into a bit more detail (in the first paragraph):



Join z.archive.ovsdb-dev@lists.opendaylight.org to automatically receive all group messages.