Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update telemetry-atomic description #1238

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 15 additions & 3 deletions release/models/openconfig-extensions.yang
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,13 @@ module openconfig-extensions {
"This module provides extensions to the YANG language to allow
OpenConfig specific functionality and meta-data to be defined.";

oc-ext:openconfig-version "0.6.0";
oc-ext:openconfig-version "0.7.0";

revision "2025-01-02" {
description
"Update telemetry-atomic description.";
reference "0.7.0";
}

revision "2024-09-19" {
description
Expand Down Expand Up @@ -160,11 +166,17 @@ module openconfig-extensions {
extension telemetry-atomic {
description
"The telemetry-atomic annotation is specified in the context of
a subtree (container, or list), and indicates that all nodes
a subtree (container, or leaf-list), and indicates that all nodes
within the subtree are always updated together within the data
model. For example, all elements under the subtree may be updated
as a result of a new alarm being raised, or the arrival of a new
protocol message.
protocol message. When the annotation is specified in the context
of a list of containers, the atomic property applies to the
contents of each individual keyed entry in the list. For example,
say ipv4-entry list has two elements, prefix1 and prefix2, all
the elements under the prefix1 subtree may be updated as a
result of a next-hop group change while prefix2 subtree is not
updated.

Transport protocols may use the atomic specification to determine
optimisations for sending or storing the corresponding data.";
Expand Down
Loading