...
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
The purpose of this spike is to be able to identify the APIs we need in order to talk to SDNC for doing CRUD operations on the models that are mounted as nodes on a particular installation.
Decisions
Description | Decision | Notes | |
---|---|---|---|
1 | Bundle to use | "rests" bundle supports MIME type "application/yang-data+json" and is chosen as the bundle to use. Supports parameters like fields and depth (details below) | It also supports actions. |
Assumptions
Assumption | Note | |
---|---|---|
1 | rests budle is predeployed |
...
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
module gnodeb { yang-version 1.1; namespace "urn:gnodeb:test"; prefix gnb; description "Yang model for gnodeb"; revision "2019-12-03" { description "initial version"; } container cells { list cellinfolist { key cell-id; leaf cell-id { type uint16; } leaf cell-uuid { type uint32; } leaf cell-description { type string; description "Possible name or description"; } } } } |
...
Query Config date
The "content" query parameter controls how descendant nodes of the requested data nodes will be processed in the reply of a GET request.
Possible values are config, nonconfig and all, with all being the default.
Code Block | ||||
---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc message-id="m-130" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get>
<filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree">
<cells xmlns="urn:gnodeb:test"/>
</filter>
</get>
</rpc> |
Code Block | ||||
---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <rpc message-id="m-131" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get-config> <source> <running/> </source> <filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree"> <cells xmlns="urn:gnodeb:test"/> </filter> </get-config> </rpc> |
The equivalent Netconf requests are
Other available params :
Recording :
...