Difference between revisions of "Sweetcomb/RPCop"
From fd.io
m (→RPC Operations) |
m (→RPC Operations) |
||
| Line 4: | Line 4: | ||
First, there are two types of data: | First, there are two types of data: | ||
| − | * '''Configuration data/desired state''': data that is | + | * '''Configuration data/desired state''': "Configuration data is the set of writable data that is required to transform a system from its initial default state into its current state." [https://tools.ietf.org/html/rfc6241 RFC6241] |
* '''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] | * '''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] | ||
Revision as of 10:53, 26 March 2019
RPC Operations
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: "Configuration data is the set of writable data that is required to transform a system from its initial default state into its current state." RFC6241
- 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:
- Openconfig style: 'config' and 'state' containers
- IETF withtout NMDA: 'config' and 'state' top level trees
- IETF with NMDA:
Third, as sweetcomb only supports NETCONF and gNMI, there are 5 RPCs supported:
- gNMI get
- gNMI set
- NETCONF get
- NETCONF get-config
- NETCONF edit-config
In order to know if your IETF support NMDA, please use YangCatalog.
Openconfig style
