Latest revision as of 16:47, 1 April 2019

RPC Operations

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

Context

Types of data

There are three types of data:

• Configuration data, intented config, (config=true): "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 state data, (config=false): "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
  • Applied configuration, (oc:operational=false) : "Reflection of configuration parameters" OpenConfig OpState
  • Derived state, (oc:operational=true): "Counters, Statistics, protocol-parameters" OpenConfig OpState

NB: oc:operational is openconfig specific, IETF models do not make this difference.

"[Operational state data and configuration data] may be different for a number of reasons, e.g., system internal interactions with hardware, interaction with protocols or other devices, or simply the time it takes to propagate a configuration change to the software and hardware components of a system." RFC8342

Datastore

First, NETCONF and RESTCONF protocol have been defined to use datastores [RFC 6241] & [RFC 8040] but not gNMI. Though, gNMI support a datatype field in GetRequest which defines properties similar to a datastore.

• NETCONF works with several datastores defined after.
• RESTCONF "provides only a writable unified datastore". (similar to NETCONF running datastore)
• gNMI communicate with a YANG speaking network device containing configuration and operational data. No notion of datastore exists.

In NETCONF environment, there are several datastores:

• startup - RFC6241: Automatically handled by sysrepo and netopeer
• candidate - RFC6241: Automatically handled by sysrepo and netopeer
• running - RFC6241 : This is when changes are commited to running that VPP is configured
• intended - RFC8342: Not supported by sysrepo yet
• operational - RFC8342: Not supported by sysrepo yet

Architectures of datastores

+-------------+                 +-----------+
| <candidate> |                 | <startup> |
|  (ct, rw)   |<---+       +--->| (ct, rw)  |
+-------------+    |       |    +-----------+
       |           |       |           |
       |         +-----------+         |
       +-------->| <running> |<--------+
                 | (ct, rw)  |
                 +-----------+
                       |
                       v
                operational state  <--- control plane
                    (cf, ro)
ct = config true; cf = config false
rw = read-write; ro = read-only
boxes denote datastores

+-------------+                 +-----------+
| <candidate> |                 | <startup> |
|  (ct, rw)   |<---+       +--->| (ct, rw)  |
+-------------+    |       |    +-----------+
       |           |       |           |
       |         +-----------+         |
       +-------->| <running> |<--------+
                 | (ct, rw)  |
                 +-----------+
                       |
                       |        // configuration transformations,
                       |        // e.g., removal of nodes marked as
                       |        // "inactive", expansion of
                       |        // templates
                       v
                 +------------+
                 | <intended> | // subject to validation
                 | (ct, ro)   |
                 +------------+
                       |        // changes applied, subject to
                       |        // local factors, e.g., missing
                       |        // resources, delays
                       |
  dynamic              |   +-------- learned configuration
  configuration        |   +-------- system configuration
  datastores -----+    |   +-------- default configuration
                  |    |   |
                  v    v   v
               +---------------+
               | <operational> | <-- system state
               | (ct + cf, ro) |
               +---------------+

Source: RFC8342

YANG tree architectures

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

• Openconfig style: 'config' and 'state' containers
• IETF withtout NMDA: two separate branches rooted at the root of the data tree: one branch for configuration data objects and one branch for operational state data objects.
• IETF with NMDA: leverage the targetted datastore to know if it is operational or configuration (running) data.

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

RPC types

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

• gNMI subscribe
• gNMI get
• gNMI set
• NETCONF get
• NETCONF get-config
• NETCONF edit-config

Requirements

Requirements for sweetcomb current datastore architecture (RFC 6241)

draw.io source can be found here

Future work: Requirements for sweetcomb support for NMDA

For the moment, sweetcomb does not support NMDA. YANG models with an NMDA tree type MUST NOT be used with sweetcomb.

• Help link: https://github.com/netmod-wg/FAQ/wiki/FAQ-related-to-NMDA-implementations#Q7

Source for requirements

• gNMI errors: https://github.com/openconfig/reference/blob/master/rpc/gnmi/gnmi-specification.md#347-error-handling
• gNMI proto get data types: https://github.com/openconfig/gnmi/blob/master/proto/gnmi/gnmi.proto#L397
• gNMI spec get datatypes: https://github.com/openconfig/reference/blob/master/rpc/gnmi/gnmi-specification.md#331-the-getrequest-message
• NETCONF errors: https://tools.ietf.org/html/rfc6241#appendix-A