openconfig
add gnmirpc to oc paths
The intent is to be able to allow both requirements to be made clearer by attaching the required RPC level of support (get, set, subscribe), as well as more detailed information about the current level of support.
Just because a path is supported under gnmi.Get doesn't mean it's supported ON_CHANGE in a gnmi.Subscribe!
The messages can be used to either list requirements or, if describing a particular target, it can be used to describe the level of support a target provides.
For read paths, we allow specification of desired (or implemented) support level: streaming, subscribe once, or polling.
Additionally, for paths requiring streaming support, we add specifications for the subscription type: target defined, on change, or sampled.
Finally, we add a sample_interval_nanoseconds, which can be used as a 'maximum desired cadence', if specified as a requirement or the 'minimum recommended cadence' if describing a target's capabilities.
For a target, a cadence of 0 (when the SubscriptionMode includes ON_CHANGE as supported) describes ON_CHANGE as the recommended frequency of subscription.
Pull Request Functional Test Report for #3463 / 00a9419733ea42a5b1be6d61a089853c5bdfe998
No tests identified for validation.
Pull Request Test Coverage Report for Build 11133359002
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 55.268%
| Totals | |
|---|---|
| Change from base Build 11130047378: | 0.0% |
| Covered Lines: | 1983 |
| Relevant Lines: | 3588 |
