Table of Contents |
---|
...
URI | Mandatory or Optional | Description |
---|---|---|
<OP> | mandatory | the HTTP method |
dmi | mandatory | the dmi root resource |
<v{vNumber}> | mandatory | version of the dmi interface is the target resource URI is the query parameter list |
<cmHandle> | mandatory | unique (string) identifier of a yang tree instance. |
<data|operations|dmiAction> | mandatory | yang data, rpc operation or a (non-modeled) dmi action |
{datastore} | mandatory | mandatory datastore |
<resourcePath> | optional | the path expression identifying the resource that is being accessed by the operation. If this field is not present, then the target resource is the API itself. |
<query> | optional | the set of parameters associated with the RESTCONF message; see Section 3.4 of [RFC3986]. RESTCONF parameters have the familiar form of "name=value" pairs. Most query parameters are optional to implement by the server and optional to use by the client. Each optional query parameter is identified by a URI |
NCPS-NCMP - DMI Plugin Write Request Flow
See CPS-577: Prepare the request from client and send write request to dmi-plugin
Datastore
If the cmhandle metadata indicates that data is not synched in CPS then the request is forwarded to the dmiPlugin
...
Expand | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
Below table shows the proposed interface, actual implementation might deviate from this but can be accessed from
*For response output, where applicable the yang-library format and conventions are used 'as is' or extended
|
...