reference
reference copied to clipboard
openconfig
gNMI subscription updates for leaf list and unkeyed list elements
From reading issues #66 and #76, I understand that leaf list and unkeyed list elements are unaddressable in gNMI. In particular, the response from issue #66 states that
... There is no way to delete an individual element and a delete or addition to the list would be achieved by replacing the value of the leaf-list with a new leaf-list. ...
I am wondering if the word "replacing" is meant to be take literally, as in gNMI spec section 3.5.2.3 which states
To replace the contents of an entire node within the tree, the target populates the delete field with the path of the node being removed, along with the new contents within the update field.
My current assumption is that for both leaf list and unkeyed list, if there is an addition or deletion to the list we will send out a gNMI replace subscription notification. Please let me know if that is correct.
On Wed, Dec 13, 2017 at 3:23 PM, Leon Wang [email protected] wrote:
From reading issues #66 https://github.com/openconfig/reference/issues/66 and #76 https://github.com/openconfig/reference/issues/76, I understand that leaf list and unkeyed list elements are unaddressable in gNMI. In particular, the response from issue #66 https://github.com/openconfig/reference/issues/66 states that
... There is no way to delete an individual element and a delete or addition to the list would be achieved by replacing the value of the leaf-list with a new leaf-list. ...
I am wondering if the word "replacing" is meant to be take literally, as in gNMI spec section 3.5.2.3 https://github.com/openconfig/reference/blob/master/rpc/gnmi/gnmi-specification.md#3523-sending-telemetry-updates which states
To replace the contents of an entire node within the tree, the target populates the delete field with the path of the node being removed, along with the new contents within the update field.
For a leaf-list, or unkeyed list, the whole list itself is simply sent as an Update.
My current assumption is that for both leaf list and unkeyed list, if there is an addition or deletion to the list we will send out a gNMI replace subscription notification. Please let me know if that is correct.
This text for removal refers to a container node that has multiple individually addressable elements within it. E.g. a config-replace operation might have a completely different set of aggregate interfaces configured. There are two options that are both valid in this case. First option, a notification containing all the interfaces that exist post config change as updates, and all the no longer existing interfaces in the list of deletes. Second option, a notification containing all the interfaces that exist post config change as updates, a single delete that specifies the interface container. The second option is a shorthand for bulk recursive removal of outdated contents.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/openconfig/reference/issues/81, or mute the thread https://github.com/notifications/unsubscribe-auth/ARfIL0RgFZAFsMeGDFczEfLRMKyef4dgks5tAFxsgaJpZM4RBU0V .
