You are viewing an old version of this page. View the current version .
Compare with Current
View Page History
« Previous
Version 14
Next »
Commands to SDN-R to get yang modules
Environment Variables
@ protocol = https @ host = odlux.oam.smo.indigo.cosmos-lab.org ### @host = 10.41.1.2 @ port = 443 @ sdnrUsername = admin @ sdnrPassword = Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U
@ baseUrl = {{protocol}}://{{host}}:{{port}}
#### Step #1 ### @name getAllNodeIds GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?content=nonconfig&fields=node(node-id) Authorization: Basic {{sdnrUsername}} {{sdnrPassword}} Accept: application/yang-data+json
HTTP/1.1 200 OK
Content-Length: 166
Content-Type: application/yang-data+json
Date: Wed, 09 Aug 2023 16:47:56 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Server: nginx
Set-Cookie: JSESSIONID=node01ea9dc8np27jcw3vocehlwcwo90929.node0; Path=/,rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Tue, 08-Aug-2023 16:47:56 GMT; SameSite=lax
X-Frame-Options: SAMEORIGIN
Connection: close
{
"network-topology:topology": [
{
"node": [
{
"node-id": "O-RU-11222"
},
{
"node-id": "O-DU-1122"
},
#### Step #2 itter over the node-ids ### @name getConnectionStatus @ node-id = O-RU-11222 GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf/node={{node-id}}?content=nonconfig&fields=netconf-node-topology:available-capabilities/available-capability/capability Authorization: Basic {{sdnrUsername}} {{sdnrPassword}} Accept: application/yang-data+json
HTTP/1.1 200 OK
Content-Type: application/yang-data+json
Date: Wed, 09 Aug 2023 16:56:05 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Server: nginx
Set-Cookie: JSESSIONID=node0zsfdafr3nv0m1bi3uymdui3uw90955.node0; Path=/,rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Tue, 08-Aug-2023 16:56:05 GMT; SameSite=lax
X-Frame-Options: SAMEORIGIN
Connection: close
Transfer-Encoding: chunked
{
"network-topology:node": [
{
"netconf-node-topology:available-capabilities": {
"available-capability": [
{
"capability": "urn:ietf:params:netconf:capability:with-defaults:1.0?basic-mode=explicit&also-supported=report-all,report-all-tagged,trim,explicit"
},
{
"capability": "urn:ietf:params:netconf:capability:notification:1.0"
},
#### Step #3 itter over the capabilities #### If no revision date is psecified you will get the latest avaialble. ### @name getASingleYangModuleNoRevision @ yangModuleNoRevision = o-ran-hardware #### from "capability": "(urn:o-ran:hardware:1.0?revision=2022-12-05)o-ran-hardware" #### .split(')')[1] GET {{baseUrl}}/yang-schema/{{yangModuleNoRevision}} Authorization: Basic {{sdnrUsername}} {{sdnrPassword}} Accept: application/yang-data+json
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Type: text/plain
Date: Wed, 09 Aug 2023 16:56:36 GMT
Server: nginx
X-Frame-Options: SAMEORIGIN
Connection: close
Transfer-Encoding: chunked
module o-ran-hardware {
yang-version 1.1;
namespace "urn:o-ran:hardware:1.0";
prefix o-ran-hw;
import ietf-hardware {
prefix hw;
}
import iana-hardware {
prefix ianahw;
}
import ietf-yang-types {
### @name getASingleYangModule @ yangModule = o-ran-sync @ revision = 2022-08-15 #### from "capability": "(urn:o-ran:sync:1.0?revision=2022-08-15)o-ran-sync" GET {{baseUrl}}/yang-schema/{{yangModule}}/ Authorization: Basic {{sdnrUsername}} {{sdnrPassword}} Accept: application/yang-data+json
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Type: text/plain
Date: Wed, 09 Aug 2023 16:57:08 GMT
Server: nginx
X-Frame-Options: SAMEORIGIN
Connection: close
Transfer-Encoding: chunked
module o-ran-sync {
yang-version 1.1;
namespace "urn:o-ran:sync:1.0";
prefix o-ran-sync;
import ietf-interfaces {
prefix if;
}
import o-ran-interfaces {
prefix o-ran-int;
ONAP internal data vs. Network Function specific data For backup or Initial (startup) configuration CPS could store the configuration data according to the Network Function (VNP, PNF) specific data models.
Such data is most likely not abstracted to be used for multi-vendor, multi-layer, multi-technology use cases and should/could not be used by µServices addressing such use cases.
Multi-vendor, multi-layer, multi-technology µServices require an abstract view of the network. Therefore a translation service is required to translate between ONAP internal data models and Network Function specific data models.
The database technology for the ONAP internal data must be well defined and so that model-translation-functions can be implemented accordingly. SQL based on in the MariaDB implementation seems to be the right choice.
The database technology for Network Function specific data depends on the data and the Network Function specific data schema. If the data model schema bases on YANG, which usually describes a data tree, then a non-SQL database, could be the right choice.
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6Ik1hcnRpbiBTa29ydXBza2kiLCJvdXRwdXRUeXBlIjoiYmxvY2siLCJsYXN0TW9kaWZpZXJOYW1lIjoiTWFydGluIFNrb3J1cHNraSIsImxhbmd1YWdlIjoiZW4iLCJkaWFncmFtRGlzcGxheU5hbWUiOiIiLCJzRmlsZUlkIjoiIiwiYXR0SWQiOiI4NDY1MDM0NiIsImRpYWdyYW1OYW1lIjoiZGF0YSBtb2RlbHMiLCJhc3BlY3QiOiIiLCJsaW5rcyI6ImF1dG8iLCJjZW9OYW1lIjoiU0ROLVIgaW50ZXJmYWNpbmcgd2l0aCBDb25maWd1cmF0aW9uIFx1MDAyNiBQZXJzaXN0ZW5jeSBTZXJ2aWNlIiwidGJzdHlsZSI6InRvcCIsImNhbkNvbW1lbnQiOmZhbHNlLCJkaWFncmFtVXJsIjoiIiwiY3N2RmlsZVVybCI6IiIsImJvcmRlciI6dHJ1ZSwibWF4U2NhbGUiOiIxIiwib3duaW5nUGFnZUlkIjo4MTM5NjU0NCwiZWRpdGFibGUiOmZhbHNlLCJjZW9JZCI6MTc3MDgwODAxLCJwYWdlSWQiOiIiLCJsYm94Ijp0cnVlLCJzZXJ2ZXJDb25maWciOnsiZW1haWxwcmV2aWV3IjoiMSJ9LCJvZHJpdmVJZCI6IiIsInJldmlzaW9uIjoxLCJtYWNyb0lkIjoiZDYzYTIzNTAtYzExZS00ODMxLWE5ZmYtNDkyM2Y0ZDc2M2YzIiwicHJldmlld05hbWUiOiJkYXRhIG1vZGVscy5wbmciLCJsaWNlbnNlU3RhdHVzIjoiT0siLCJzZXJ2aWNlIjoiIiwiaXNUZW1wbGF0ZSI6IiIsIndpZHRoIjoiNTIyIiwic2ltcGxlVmlld2VyIjpmYWxzZSwibGFzdE1vZGlmaWVkIjoxNTkxMDEwMTQxMDAwLCJleGNlZWRQYWdlV2lkdGgiOmZhbHNlLCJvQ2xpZW50SWQiOiIifQ==
Sequence Diagram
Status: under discussion 2020-03-01 ONAP SDN-R Interfacing with Configuration & Persistency Service (CPS) ONAP CCSDK/SDNC/SDN-R cluster ONAP CCSDK/SDNC/SDN-R cluster Configuration & Persistency Service (CPS) NetConf Provider NetConf Provider ODL NetConf Client ODL NetConf Client md-sal file-system md-sal file-system RestConf Server RestConf Server DMaaP Consumer DMaaP Consumer DMaaP Provider DMaaP Provider DMaaP DMaaP DMaaP Consumer DMaaP Consumer YANG-to-SQL YANG-to-SQL A1-REST-to-SQL (?) A1-REST-to-SQL (?) SQL SQL start, idling [010] subscribe for topic(s) - topic-names? [020] synch-request [030] synch-response (MountPoints, ConnectionStatus,YANG-Capabilities) [040] download of new intersting YANG modules [050] YANG modules [060] process YANG modules [070] Create INDEX, TABLE, ASSOCCIATION [080] subscribe for topic(s) - topic-names? loop [every 5s] [090] poll for updates [100] response (empty or new message) loop [every 5s] [110] poll for updates [120] response (empty or new message) New YANG revision (e.g. atfer xNF Software upgrade) [130] Establish NetConf session [140] Hello Message [150] Capabilites (yang modules) [160] download new YANG revision [170] new YANG module [180] new YANG module [190] mountpoint operation update [200] mountpoint operation update [210] mountpoint operation update [220] mountpoint operation update [230] mountpoint operation update [240] analyse new YANG capabilities [250] download new YANG revision [260] read new YANG revision [270] YANG module [280] YANG module [290] process YANG modules [300] Create INDEX, TABLE, ASSOCCIATION READ data from network (proposed, to be discussed) [310] RESTCONF HTTP-GET data from network (pnf-id; filter) [320] trigger <get> ro <get-config> [330] NetConf <get> ro <get-config> [340] NetConf <response> [350] forward data [360] RESTCONF response [370] forward data [380] strore data SET data on network (???) [390] TO BE DEFINED License Apache 2.0 Thanks to plantUml! 2020-03-01 | wiki.onap.org
ONAP internal data vs. Network Function specific data For backup or Initial (startup) configuration CPS could store the configuration data according to the Network Function (VNP, PNF) specific data models.
Such data is most likely not abstracted to be used for multi-vendor, multi-layer, multi-technology use cases and should/could not be used by µServices addressing such use cases.
Multi-vendor, multi-layer, multi-technology µServices require an abstract view of the network. Therefore a translation service is required to translate between ONAP internal data models and Network Function specific data models.
The database technology for the ONAP internal data must be well defined and so that model-translation-functions can be implemented accordingly. SQL based on in the MariaDB implementation seems to be the right choice.
The database technology for Network Function specific data depends on the data and the Network Function specific data schema. If the data model schema bases on YANG, which usually describes a data tree, then a non-SQL database, could be the right choice.
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6Ik1hcnRpbiBTa29ydXBza2kiLCJvdXRwdXRUeXBlIjoiYmxvY2siLCJsYXN0TW9kaWZpZXJOYW1lIjoiTWFydGluIFNrb3J1cHNraSIsImxhbmd1YWdlIjoiZW4iLCJkaWFncmFtRGlzcGxheU5hbWUiOiIiLCJzRmlsZUlkIjoiIiwiYXR0SWQiOiI4NDY1MDM0NiIsImRpYWdyYW1OYW1lIjoiZGF0YSBtb2RlbHMiLCJhc3BlY3QiOiIiLCJsaW5rcyI6ImF1dG8iLCJjZW9OYW1lIjoiU0ROLVIgaW50ZXJmYWNpbmcgd2l0aCBDb25maWd1cmF0aW9uIFx1MDAyNiBQZXJzaXN0ZW5jeSBTZXJ2aWNlIiwidGJzdHlsZSI6InRvcCIsImNhbkNvbW1lbnQiOmZhbHNlLCJkaWFncmFtVXJsIjoiIiwiY3N2RmlsZVVybCI6IiIsImJvcmRlciI6dHJ1ZSwibWF4U2NhbGUiOiIxIiwib3duaW5nUGFnZUlkIjo4MTM5NjU0NCwiZWRpdGFibGUiOmZhbHNlLCJjZW9JZCI6MTc3MDgwODAxLCJwYWdlSWQiOiIiLCJsYm94Ijp0cnVlLCJzZXJ2ZXJDb25maWciOnsiZW1haWxwcmV2aWV3IjoiMSJ9LCJvZHJpdmVJZCI6IiIsInJldmlzaW9uIjoxLCJtYWNyb0lkIjoiMTE5ODcwYmItMjVhNi00ZmNlLTg0MjAtZTdlZTI3YTc5NzFhIiwicHJldmlld05hbWUiOiJkYXRhIG1vZGVscy5wbmciLCJsaWNlbnNlU3RhdHVzIjoiT0siLCJzZXJ2aWNlIjoiIiwiaXNUZW1wbGF0ZSI6IiIsIndpZHRoIjoiNTIyIiwic2ltcGxlVmlld2VyIjpmYWxzZSwibGFzdE1vZGlmaWVkIjoxNTkxMDEwMTQxMDAwLCJleGNlZWRQYWdlV2lkdGgiOmZhbHNlLCJvQ2xpZW50SWQiOiIifQ==
Sequence Diagram
Status: under discussion 2020-03-01 ONAP SDN-R Interfacing with Configuration & Persistency Service (CPS) ONAP CCSDK/SDNC/SDN-R cluster ONAP CCSDK/SDNC/SDN-R cluster Configuration & Persistency Service (CPS) NetConf Provider NetConf Provider ODL NetConf Client ODL NetConf Client md-sal file-system md-sal file-system RestConf Server RestConf Server DMaaP Consumer DMaaP Consumer DMaaP Provider DMaaP Provider DMaaP DMaaP DMaaP Consumer DMaaP Consumer YANG-to-SQL YANG-to-SQL A1-REST-to-SQL (?) A1-REST-to-SQL (?) SQL SQL start, idling [010] subscribe for topic(s) - topic-names? [020] synch-request [030] synch-response (MountPoints, ConnectionStatus,YANG-Capabilities) [040] download of new intersting YANG modules [050] YANG modules [060] process YANG modules [070] Create INDEX, TABLE, ASSOCCIATION [080] subscribe for topic(s) - topic-names? loop [every 5s] [090] poll for updates [100] response (empty or new message) loop [every 5s] [110] poll for updates [120] response (empty or new message) New YANG revision (e.g. atfer xNF Software upgrade) [130] Establish NetConf session [140] Hello Message [150] Capabilites (yang modules) [160] download new YANG revision [170] new YANG module [180] new YANG module [190] mountpoint operation update [200] mountpoint operation update [210] mountpoint operation update [220] mountpoint operation update [230] mountpoint operation update [240] analyse new YANG capabilities [250] download new YANG revision [260] read new YANG revision [270] YANG module [280] YANG module [290] process YANG modules [300] Create INDEX, TABLE, ASSOCCIATION READ data from network (proposed, to be discussed) [310] RESTCONF HTTP-GET data from network (pnf-id; filter) [320] trigger <get> ro <get-config> [330] NetConf <get> ro <get-config> [340] NetConf <response> [350] forward data [360] RESTCONF response [370] forward data [380] strore data SET data on network (???) [390] TO BE DEFINED License Apache 2.0 Thanks to plantUml! 2020-03-01 | wiki.onap.org