Difference between revisions of "Sweetcomb/RPCop"

Openconfig style: 'config' and 'state' containers
IETF withtout NMDA: 'config' and 'state' top level trees
IETF with NMDA:

Revision as of 10:44, 26 March 2019

This page aims at describing which data should be read when a user uses a RPC method on sweetcomb control agent.

First, there are two types of data:

Configuration data/desired state: data that is read from an intermediate database (ex: data fetched by sr_get_item)
Operational data: "Operational state data is a set of data that has been obtained by the system at runtime and influences the system's behavior similar to configuration data. In contrast to configuration data, operational state is transient and modified by interactions with internal components or other systems via specialized protocols." RFC6244

Second, there are three types of organization of YANG trees:

Third, as sweetcomb only supports NETCONF and gNMI, there are 5 RPCs supported:

In order to know if your IETF support NMDA, please use YangCatalog.

@@ Line 5: / Line 5: @@
 First, there are two types of data:
 * '''Configuration data/desired state''': data that is read from an intermediate database  (ex: data fetched by sr_get_item)
-* '''Operational data''': fresh data directly read from the networking devices (ex: telemetry data, all data fetched with VAPI)
+* '''Operational data''':  "Operational state data is a set of data that has been obtained by the system at runtime and influences the system's behavior similar to configuration data. In contrast to configuration data, operational state is transient and modified by interactions with internal components or other systems via specialized protocols." [https://tools.ietf.org/html/rfc6244 RFC6244]
 Second, there are [https://www.ietf.org/proceedings/99/slides/slides-99-rtgwg-sessa-guidelines-for-yang-module-authors-on-using-nmda-00.pdf three types of organization] of YANG trees: