docs/user-guide.rst

   1 .. _netconf-user-guide:
   2
   3 .. |ss| raw:: html
   4
   5    <strike>
   6
   7 .. |se| raw:: html
   8
   9    </strike>
  10
  11 NETCONF User Guide
  12 ==================
  13
  14 Overview
  15 --------
  16
  17 NETCONF is an XML-based protocol used for configuration and monitoring
  18 devices in the network. The base NETCONF protocol is described in
  19 `RFC-6241 <https://www.rfc-editor.org/rfc/rfc6241>`__.
  20
  21 **NETCONF in OpenDaylight:.**
  22
  23 OpenDaylight supports the NETCONF protocol as a northbound server as
  24 well as a southbound plugin. It also includes a set of test tools for
  25 simulating NETCONF devices and clients.
  26
  27 Southbound (netconf-connector)
  28 ------------------------------
  29
  30 The NETCONF southbound plugin is capable of connecting to remote NETCONF
  31 devices and exposing their configuration/operational datastores, RPCs
  32 and notifications as MD-SAL mount points. These mount points allow
  33 applications and remote users (over RESTCONF) to interact with the
  34 mounted devices.
  35
  36 In terms of RFCs, the connector supports:
  37
  38 -  `RFC-6241 <https://www.rfc-editor.org/rfc/rfc6241>`__
  39
  40 -  `RFC-5277 <https://www.rfc-editor.org/rfc/rfc5277>`__
  41
  42 -  `RFC-6022 <https://www.rfc-editor.org/rfc/rfc6022>`__
  43
  44 -  `RFC-7895 <https://www.rfc-editor.org/rfc/rfc7895>`__
  45
  46 **Netconf-connector is fully model-driven (utilizing the YANG modeling
  47 language) so in addition to the above RFCs, it supports any
  48 data/RPC/notifications described by a YANG model that is implemented by
  49 the device.**
  50
  51 .. tip::
  52
  53     NETCONF southbound can be activated by installing
  54     ``odl-netconf-connector-all`` Karaf feature.
  55
  56 Netconf-connector configuration
  57 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  58
  59 NETCONF connectors are configured directly through the usage of the
  60 network-topology model. You can configure new NETCONF connectors both
  61 through the NETCONF server for MD-SAL (port 2830) or RESTCONF. This guide
  62 focuses on RESTCONF.
  63
  64 .. important::
  65
  66     Since 2022.09 Chlorine there is only one RESTCONF endpoint:
  67
  68     - | ``http://localhost:8181/rests`` is related to `RFC-8040 <https://www.rfc-editor.org/rfc/rfc8040>`__,
  69       | can be activated by installing ``odl-restconf-nb``
  70        Karaf feature.
  71
  72     | Resources for configuration and operational datastores start
  73      ``/rests/data/``,
  74     | e. g. GET
  75      http://localhost:8181/rests/data/network-topology:network-topology
  76      with response of both datastores. It's allowed to use query
  77      parameters to distinguish between them.
  78     | e. g. GET
  79      http://localhost:8181/rests/data/network-topology:network-topology?content=config
  80      for configuration datastore
  81     | and GET
  82      http://localhost:8181/rests/data/network-topology:network-topology?content=nonconfig
  83      for operational datastore.
  84
  85     | Also if a data node in the path expression is a YANG leaf-list or list
  86      node, the path segment has to be constructed by having leaf-list or
  87      list node name, followed by an "=" character, then followed by the
  88      leaf-list or list value. Any reserved characters must be
  89      percent-encoded.
  90     | e. g. GET
  91      http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf?content=config
  92      for retrieving data from configuration datastore for
  93      topology-netconf value of topology list.
  94
  95 Preconditions
  96 ^^^^^^^^^^^^^
  97
  98 1. OpenDaylight is running
  99
 100 2. In Karaf, you must have the ``odl-netconf-topology`` or
 101    ``odl-netconf-clustered-topology`` feature installed.
 102
 103 3. Feature ``odl-restconf-nb`` must be installed
 104
 105 Spawning new NETCONF connectors
 106 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 107
 108 To create a new NETCONF connector you need to send the following PUT request
 109 to RESTCONF:
 110
 111 .. list-table::
 112    :widths: 1 5
 113
 114    * - rfc8040
 115      - http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=new-netconf-device
 116
 117 You could use the same body to create the new  NETCONF connector with a POST
 118 without specifying the node in the URL:
 119
 120 .. list-table::
 121    :widths: 1 5
 122
 123    * - rfc8040
 124      - http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf
 125
 126 Payload:
 127
 128 .. tabs::
 129
 130    .. tab:: XML
 131
 132       **Content-type:** ``application/xml``
 133
 134       **Accept:** ``application/xml``
 135
 136       **Authentication:** ``admin:admin``
 137
 138       .. code-block:: xml
 139
 140          <node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
 141            <node-id>new-netconf-device</node-id>
 142            <host xmlns="urn:opendaylight:netconf-node-topology">127.0.0.1</host>
 143            <port xmlns="urn:opendaylight:netconf-node-topology">17830</port>
 144            <username xmlns="urn:opendaylight:netconf-node-topology">admin</username>
 145            <password xmlns="urn:opendaylight:netconf-node-topology">admin</password>
 146            <tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>
 147            <!-- non-mandatory fields with default values, you can safely remove these if you do not wish to override any of these values-->
 148            <reconnect-on-changed-schema xmlns="urn:opendaylight:netconf-node-topology">false</reconnect-on-changed-schema>
 149            <connection-timeout-millis xmlns="urn:opendaylight:netconf-node-topology">20000</connection-timeout-millis>
 150            <max-connection-attempts xmlns="urn:opendaylight:netconf-node-topology">0</max-connection-attempts>
 151            <between-attempts-timeout-millis xmlns="urn:opendaylight:netconf-node-topology">2000</between-attempts-timeout-millis>
 152            <sleep-factor xmlns="urn:opendaylight:netconf-node-topology">1.5</sleep-factor>
 153            <!-- keepalive-delay set to 0 turns off keepalives-->
 154            <keepalive-delay xmlns="urn:opendaylight:netconf-node-topology">120</keepalive-delay>
 155          </node>
 156
 157    .. tab:: JSON
 158
 159       **Content-type:** ``application/json``
 160
 161       **Accept:** ``application/json``
 162
 163       **Authentication:** ``admin:admin``
 164
 165       .. code-block:: json
 166
 167          {
 168              "node": [
 169                  {
 170                      "node-id": "new-netconf-device",
 171                      "netconf-node-topology:port": 17830,
 172                      "netconf-node-topology:reconnect-on-changed-schema": false,
 173                      "netconf-node-topology:connection-timeout-millis": 20000,
 174                      "netconf-node-topology:tcp-only": false,
 175                      "netconf-node-topology:max-connection-attempts": 0,
 176                      "netconf-node-topology:username": "admin",
 177                      "netconf-node-topology:password": "admin",
 178                      "netconf-node-topology:sleep-factor": 1.5,
 179                      "netconf-node-topology:host": "127.0.0.1",
 180                      "netconf-node-topology:between-attempts-timeout-millis": 2000,
 181                      "netconf-node-topology:keepalive-delay": 120
 182                  }
 183              ]
 184          }
 185
 186 Note that the device name in <node-id> element must match the last
 187 element of the restconf URL.
 188
 189 Reconfiguring an existing connector
 190 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 191
 192 The steps to reconfigure an existing connector are exactly the same as
 193 when spawning a new connector. The old connection will be disconnected
 194 and a new connector with the new configuration will be created. This needs
 195 to be done with a PUT request because the node already exists. A POST
 196 request will fail for that reason.
 197
 198 Additionally, a PATCH request can be used to modify an existing
 199 configuration. Currently, only yang-patch (`RFC-8072 <https://www.rfc-editor.org/rfc/rfc8072>`__)
 200 is supported. The URL would be the same as the above PUT examples.
 201 Using JSON for the body, the headers needed for the request would
 202 be:
 203
 204 Headers:
 205
 206 -  Accept: application/yang-data+json
 207
 208 -  Content-Type: application/yang-patch+json
 209
 210 Example JSON payload to modify the password entry:
 211
 212 ::
 213
 214     {
 215       "ietf-restconf:yang-patch" : {
 216         "patch-id" : "0",
 217         "edit" : [
 218           {
 219             "edit-id" : "edit1",
 220             "operation" : "merge",
 221             "target" : "",
 222             "value" : {
 223              "node": [
 224                 {
 225                  "node-id": "new-netconf-device",
 226                  "netconf-node-topology:password" : "newpassword"
 227                 }
 228              ]
 229             }
 230          }
 231         ]
 232       }
 233     }
 234
 235 Deleting an existing connector
 236 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 237
 238 To remove an already configured NETCONF connector you need to send a
 239 DELETE request to the same PUT request URL that was used to create the
 240 device:
 241
 242 .. list-table::
 243    :widths: 1 5
 244
 245    * - rfc8040
 246      - http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=new-netconf-device
 247
 248 .. note::
 249
 250     No body is needed to delete the node/device
 251
 252 Connecting to a device not supporting NETCONF monitoring
 253 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 254
 255 The netconf-connector in OpenDaylight relies on ietf-netconf-monitoring
 256 support when connecting to remote NETCONF device. The
 257 ietf-netconf-monitoring support allows netconf-connector to list and
 258 download all YANG schemas that are used by the device. NETCONF connector
 259 can only communicate with a device if it knows the set of used schemas
 260 (or at least a subset). However, some devices use YANG models internally
 261 but do not support NETCONF monitoring. Netconf-connector can also
 262 communicate with these devices, but you have to side load the necessary
 263 yang models into OpenDaylight’s YANG model cache for netconf-connector.
 264 In general there are 2 situations you might encounter:
 265
 266 **1. NETCONF device does not support ietf-netconf-monitoring but it does
 267 list all its YANG models as capabilities in HELLO message**
 268
 269 This could be a device that internally uses only ietf-inet-types YANG
 270 model with revision 2010-09-24. In the HELLO message that is sent from
 271 this device there is this capability reported:
 272
 273 ::
 274
 275     urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&revision=2010-09-24
 276
 277 **For such devices you only need to put the schema into folder
 278 cache/schema inside your Karaf distribution.**
 279
 280 .. important::
 281
 282     The file with YANG schema for ietf-inet-types has to be called
 283     ietf-inet-types@2010-09-24.yang. It is the required naming format of
 284     the cache.
 285
 286 **2. NETCONF device does not support ietf-netconf-monitoring and it does
 287 NOT list its YANG models as capabilities in HELLO message**
 288
 289 Compared to device that lists its YANG models in HELLO message, in this
 290 case there would be no capability with ietf-inet-types in the HELLO
 291 message. This type of device basically provides no information about the
 292 YANG schemas it uses so its up to the user of OpenDaylight to properly
 293 configure netconf-connector for this device.
 294
 295 Netconf-connector has an optional configuration attribute called
 296 yang-module-capabilities and this attribute can contain a list of "YANG
 297 module based" capabilities. So by setting this configuration attribute,
 298 it is possible to override the "yang-module-based" capabilities reported
 299 in HELLO message of the device. To do this, we need to modify the
 300 configuration of netconf-connector like in the example below:
 301
 302 .. tabs::
 303
 304    .. tab:: XML
 305
 306       **Content-type:** ``application/xml``
 307
 308       **Accept:** ``application/xml``
 309
 310       **Authentication:** ``admin:admin``
 311
 312       .. code-block:: xml
 313
 314          <node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
 315            <node-id>r5</node-id>
 316            <host xmlns="urn:opendaylight:netconf-node-topology">127.0.0.1</host>
 317            <port xmlns="urn:opendaylight:netconf-node-topology">8305</port>
 318            <username xmlns="urn:opendaylight:netconf-node-topology">root</username>
 319            <password xmlns="urn:opendaylight:netconf-node-topology">root</password>
 320            <tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>
 321            <keepalive-delay xmlns="urn:opendaylight:netconf-node-topology">30</keepalive-delay>
 322            <yang-module-capabilities xmlns="urn:opendaylight:netconf-node-topology">
 323              <override>true</override>
 324              <capability xmlns="urn:opendaylight:netconf-node-topology">
 325                urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&amp;revision=2013-07-15
 326              </capability>
 327            </yang-module-capabilities>
 328          </node>
 329
 330    .. tab:: JSON
 331
 332       **Content-type:** ``application/json``
 333
 334       **Accept:** ``application/json``
 335
 336       **Authentication:** ``admin:admin``
 337
 338       .. code-block:: json
 339
 340          {
 341              "node": [
 342                  {
 343                      "node-id": "device",
 344                      "netconf-node-topology:host": "127.0.0.1",
 345                      "netconf-node-topology:password": "root",
 346                      "netconf-node-topology:username": "root",
 347                      "netconf-node-topology:yang-module-capabilities": {
 348                          "override": true,
 349                          "capability": [
 350                              "urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&revision=2013-07-15"
 351                          ]
 352                      },
 353                      "netconf-node-topology:port": 8305,
 354                      "netconf-node-topology:tcp-only": false,
 355                      "netconf-node-topology:keepalive-delay": 30
 356                  }
 357              ]
 358          }
 359
 360 **Remember to also put the YANG schemas into the cache folder.**
 361
 362 .. note::
 363
 364     For putting multiple capabilities, you just need to replicate the
 365     capability element inside yang-module-capability element.
 366     Capability element is modeled as a leaf-list. With this
 367     configuration, we would make the remote device report usage of
 368     ietf-inet-types in the eyes of netconf-connector.
 369
 370 Connecting to a device supporting only NETCONF 1.0
 371 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 372
 373 OpenDaylight is schema-based distribution and heavily depends on YANG
 374 models. However some legacy NETCONF devices are not schema-based and
 375 implement just RFC 4741. This type of device does not utilize YANG
 376 models internally and OpenDaylight does not know how to communicate
 377 with such devices, how to validate data, or what the semantics of data
 378 are.
 379
 380 NETCONF connector can communicate also with these devices, but the
 381 trade-offs are worsened possibilities in utilization of NETCONF
 382 mountpoints. Using RESTCONF with such devices is not suported. Also
 383 communicating with schemaless devices from application code is slightly
 384 different.
 385
 386 To connect to schemaless device, there is a optional configuration option
 387 in netconf-node-topology model called schemaless. You have to set this
 388 option to true.
 389
 390 Clustered NETCONF connector
 391 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 392
 393 To spawn NETCONF connectors that are cluster-aware you need to install
 394 the ``odl-netconf-clustered-topology`` karaf feature.
 395
 396 .. warning::
 397
 398     The ``odl-netconf-topology`` and ``odl-netconf-clustered-topology``
 399     features are considered **INCOMPATIBLE**. They both manage the same
 400     space in the datastore and would issue conflicting writes if
 401     installed together.
 402
 403 Configuration of clustered NETCONF connectors works the same as the
 404 configuration through the topology model in the previous section.
 405
 406 When a new clustered connector is configured the configuration gets
 407 distributed among the member nodes and a NETCONF connector is spawned on
 408 each node. From these nodes a master is chosen which handles the schema
 409 download from the device and all the communication with the device. You
 410 will be able to read/write to/from the device from all slave nodes due
 411 to the proxy data brokers implemented.
 412
 413 You can use the ``odl-netconf-clustered-topology`` feature in a single
 414 node scenario as well but the code that uses akka will be used, so for a
 415 scenario where only a single node is used, ``odl-netconf-topology``
 416 might be preferred.
 417
 418 Netconf-connector utilization
 419 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 420
 421 Once the connector is up and running, users can utilize the new mount
 422 point instance. By using RESTCONF or from their application code. This
 423 chapter deals with using RESTCONF and more information for app
 424 developers can be found in the developers guide or in the official
 425 tutorial application **ncmount** that can be found in the coretutorials
 426 project:
 427
 428 -  https://github.com/opendaylight/coretutorials/tree/master/ncmount
 429
 430 Reading data from the device
 431 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 432
 433 Just invoke (no body needed):
 434
 435 GET
 436 http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=new-netconf-device/yang-ext:mount?content=nonconfig
 437
 438 This will return the entire content of operation datastore from the
 439 device. To view just the configuration datastore, change **nonconfig**
 440 in this URL to **config**.
 441
 442 Writing configuration data to the device
 443 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 444
 445 In general, you cannot simply write any data you want to the device. The
 446 data have to conform to the YANG models implemented by the device. In
 447 this example we are adding a new interface-configuration to the mounted
 448 device (assuming the device supports Cisco-IOS-XR-ifmgr-cfg YANG model).
 449 In fact this request comes from the tutorial dedicated to the
 450 **ncmount** tutorial app.
 451
 452 POST
 453 http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=new-netconf-device/yang-ext:mount/Cisco-IOS-XR-ifmgr-cfg:interface-configurations
 454
 455 ::
 456
 457     <interface-configuration xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-ifmgr-cfg">
 458         <active>act</active>
 459         <interface-name>mpls</interface-name>
 460         <description>Interface description</description>
 461         <bandwidth>32</bandwidth>
 462         <link-status></link-status>
 463     </interface-configuration>
 464
 465 Should return 200 response code with no body.
 466
 467 .. tip::
 468
 469     This call is transformed into a couple of NETCONF RPCs. Resulting
 470     NETCONF RPCs that go directly to the device can be found in the
 471     OpenDaylight logs after invoking ``log:set TRACE
 472     org.opendaylight.controller.sal.connect.netconf`` in the Karaf
 473     shell. Seeing the NETCONF RPCs might help with debugging.
 474
 475 This request is very similar to the one where we spawned a new netconf
 476 device. That’s because we used the loopback netconf-connector to write
 477 configuration data into config-subsystem datastore and config-subsystem
 478 picked it up from there.
 479
 480 Invoking custom RPC
 481 ^^^^^^^^^^^^^^^^^^^
 482
 483 Devices can implement any additional RPC and as long as it provides YANG
 484 models for it, it can be invoked from OpenDaylight. Following example
 485 shows how to invoke the get-schema RPC (get-schema is quite common among
 486 netconf devices). Invoke:
 487
 488 POST
 489 http://localhost:8181/rests/operations/network-topology:network-topology/topology=topology-netconf/node=new-netconf-device/yang-ext:mount/ietf-netconf-monitoring:get-schema
 490
 491 ::
 492
 493     <input xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
 494       <identifier>ietf-yang-types</identifier>
 495       <version>2013-07-15</version>
 496     </input>
 497
 498 This call should fetch the source for ietf-yang-types YANG model from
 499 the mounted device.
 500
 501 Receiving Netconf Device Notifications on a http client
 502 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 503
 504 Devices emit netconf alarms and notifictions on certain situtations, which can demand
 505 attention from Device Administration. The notifications are received as Netconf messages on an
 506 active Netconf session.
 507
 508 Opendaylight provides the way to stream the device notifications over a http session.
 509
 510 - Step 1: Mount the device (assume node name is test_device)
 511
 512 - Step 2: Wait for the device to be connected.
 513
 514 - Step 3: Create the Subscription for notification on the active session.
 515
 516  .. code-block::
 517
 518     POST
 519     http://localhost:8181/rests/operations/network-topology:network-topology/topology=topology-netconf/node=test_device/yang-ext:mount/notifications:create-subscription
 520     Content-Type: application/json
 521     Accept: application/json
 522
 523  .. code-block:: json
 524
 525     {
 526       "input": {
 527         "stream": "NETCONF"
 528        }
 529     }
 530
 531 - Step 4: Create the http Stream for the events.
 532
 533 .. code-block::
 534
 535     POST
 536     http://localhost:8181/rests/operations/odl-device-notification:subscribe-device-notification
 537     Content-Type: application/json
 538     Accept: application/json
 539
 540 .. code-block:: json
 541
 542     {
 543       "input": {
 544          "path":"/network-topology:network-topology/topology[topology-id='topology-netconf']/node[node-id='test_device']"
 545       }
 546     }
 547
 548 The response suggests the http url for reading the notifications.
 549
 550 .. code-block:: json
 551
 552     {
 553        "odl-device-notification:output": {
 554             "stream-path": "http://localhost:8181/rests/notif/test_device?notificationType=test_device"
 555         }
 556     }
 557
 558 - Step 5: User can access the url in the response and the notifications will be as follows.
 559
 560 .. code-block::
 561
 562     GET
 563     http://localhost:8181/rests/notif/test_device?notificationType=test_device
 564     Content-Type: application/xml
 565     Accept: application/xml
 566
 567
 568 .. code-block:: xml
 569
 570     : ping
 571
 572     : ping
 573
 574     : ping
 575
 576     : ping
 577
 578     : ping
 579
 580     data: <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"><eventTime>2022-06-17T07:01:08.60228Z</eventTime><netconf-session-start xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-notifications"><username>root</username><source-host>127.0.0.1</source-host><session-id>2</session-id></netconf-session-start></notification>
 581
 582     data: <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"><eventTime>2022-06-17T07:01:12.458258Z</eventTime><netconf-session-end xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-notifications"><username>root</username><source-host>127.0.0.1</source-host><termination-reason>closed</termination-reason><session-id>2</session-id></netconf-session-end></notification>
 583
 584 Change event notification subscription tutorial
 585 -----------------------------------------------
 586
 587 Subscribing to data change notifications makes it possible to obtain
 588 notifications about data manipulation (insert, change, delete) which are
 589 done on any specified **path** of any specified **datastore** with
 590 specific **scope**. In following examples *{odlAddress}* is address of
 591 server where ODL is running and *{odlPort}* is port on which
 592 OpenDaylight is running. OpenDaylight offers two methods for receiving notifications:
 593 Server-Sent Events (SSE) and WebSocket. SSE is the default notification mechanism used in OpenDaylight.
 594
 595 SSE notifications subscription process
 596 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 597
 598 In this section we will learn what steps need to be taken in order to
 599 successfully subscribe to data change event notifications.
 600
 601 Create stream
 602 ^^^^^^^^^^^^^
 603
 604 In order to use event notifications you first need to call RPC that
 605 creates notification stream that you can later listen to. You need to
 606 provide three parameters to this RPC:
 607
 608 -  **path**: data store path that you plan to listen to. You can
 609    register listener on containers, lists and leaves.
 610
 611 -  **datastore**: data store type. *OPERATIONAL* or *CONFIGURATION*.
 612
 613 -  **scope**: Represents scope of data change. Possible options are:
 614
 615    -  BASE: only changes directly to the data tree node specified in the
 616       path will be reported
 617
 618    -  ONE: changes to the node and to direct child nodes will be
 619       reported
 620
 621    -  SUBTREE: changes anywhere in the subtree starting at the node will
 622       be reported
 623
 624 The RPC to create the stream can be invoked via RESTCONF like this:
 625
 626 ::
 627
 628     OPERATION: POST
 629     URI:  http://{odlAddress}:{odlPort}/rests/operations/sal-remote:create-data-change-event-subscription
 630     HEADER: Content-Type=application/json
 631             Accept=application/json
 632
 633 .. code-block:: json
 634
 635        {
 636            "input": {
 637                "path": "/toaster:toaster/toaster:toasterStatus",
 638                "sal-remote-augment:datastore": "OPERATIONAL",
 639                "sal-remote-augment:scope": "ONE"
 640            }
 641        }
 642
 643 The response should look something like this:
 644
 645 .. code-block:: json
 646
 647     {
 648         "sal-remote:output": {
 649             "stream-name": "data-change-event-subscription/toaster:toaster/toaster:toasterStatus/datastore=CONFIGURATION/scope=SUBTREE"
 650         }
 651     }
 652
 653 **stream-name** is important because you will need to use it when you
 654 subscribe to the stream in the next step.
 655
 656 .. note::
 657
 658     Internally, this will create a new listener for *stream-name* if it
 659     did not already exist.
 660
 661 Subscribe to stream
 662 ^^^^^^^^^^^^^^^^^^^
 663
 664 In order to subscribe to stream and obtain SSE location you need
 665 to call *GET* on your stream path. The URI should generally be
 666 `http://{odlAddress}:{odlPort}/rests/data/ietf-restconf-monitoring:restconf-state/streams/stream/{streamName}`,
 667 where *{streamName}* is the *stream-name* parameter contained in
 668 response from *create-data-change-event-subscription* RPC from the
 669 previous step.
 670
 671 ::
 672
 673    OPERATION: GET
 674    URI: http://{odlAddress}:{odlPort}/rests/data/ietf-restconf-monitoring:restconf-state/streams/stream/data-change-event-subscription/toaster:toaster/datastore=CONFIGURATION/scope=SUBTREE
 675
 676 The subscription call may be modified with the following query parameters defined in the RESTCONF RFC:
 677
 678 -  `filter <https://www.rfc-editor.org/rfc/rfc8040#section-4.8.4>`__
 679
 680 -  `start-time <https://www.rfc-editor.org/rfc/rfc8040#section-4.8.7>`__
 681
 682 -  `end-time <https://www.rfc-editor.org/rfc/rfc8040#section-4.8.8>`__
 683
 684 In addition, the following ODL extension query parameter is supported:
 685
 686 :odl-leaf-nodes-only:
 687   If this parameter is set to "true", create and update notifications will only
 688   contain the leaf nodes modified instead of the entire subscription subtree.
 689   This can help in reducing the size of the notifications.
 690
 691 :odl-skip-notification-data:
 692   If this parameter is set to "true", create and update notifications will only
 693   contain modified leaf nodes without data.
 694   This can help in reducing the size of the notifications.
 695
 696 The response should look something like this:
 697
 698 .. code-block:: json
 699
 700     {
 701         "subscribe-to-notification:location": "http://localhost:8181/rests/notif/data-change-event-subscription/network-topology:network-topology/datastore=CONFIGURATION/scope=SUBTREE"
 702     }
 703
 704 .. note::
 705
 706     During this phase there is an internal check for to see if a
 707     listener for the *stream-name* from the URI exists. If not, new a
 708     new listener is registered with the DOM data broker.
 709
 710 Receive notifications
 711 ^^^^^^^^^^^^^^^^^^^^^
 712
 713 Once you got SSE location you can now connect to it and
 714 start receiving data change events. The request should look something like this:
 715
 716 ::
 717
 718     curl -v -X GET  http://localhost:8181/rests/notif/data-change-event-subscription/toaster:toaster/toasterStatus/datastore=OPERATIONAL/scope=ONE  -H "Content-Type: text/event-stream" -H "Authorization: Basic YWRtaW46YWRtaW4="
 719
 720
 721 WebSocket notifications subscription process
 722 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 723
 724 Enabling WebSocket notifications in OpenDaylight requires a manual setup before starting the application.
 725 The following steps can be followed to enable WebSocket notifications in OpenDaylight:
 726
 727 1. Open the file `restconf8040.cfg`, at `etc/` folder inside your Karaf distribution.
 728 2. Locate the `use-sse` configuration parameter and change its value from `true` to `false`.
 729 3. Uncomment the `use-sse` parameter if it is commented out.
 730 4. Save the changes made to the `restconf8040.cfg` file.
 731 5. Restart OpenDaylight if it is already running.
 732
 733 Once these steps are completed, WebSocket notifications will be enabled in OpenDaylight,
 734 and they can be used for receiving notifications instead of SSE.
 735
 736 WebSocket Notifications subscription process is the same as SSE until you receive a location of WebSocket.
 737 You can follow steps given above and after subscribing to a notification stream over WebSocket,
 738 you will receive a response indicating that the subscription was successful:
 739
 740 .. code-block:: json
 741
 742     {
 743         "subscribe-to-notification:location": "ws://localhost:8181/rests/notif/data-change-event-subscription/network-topology:network-topology/datastore=CONFIGURATION/scope=SUBTREE"
 744     }
 745
 746 You can use this WebSocket to listen to data
 747 change notifications. To listen to notifications you can use a
 748 JavaScript client or if you are using chrome browser you can use the
 749 `Simple WebSocket
 750 Client <https://chrome.google.com/webstore/detail/simple-websocket-client/pfdhoblngboilpfeibdedpjgfnlcodoo>`__.
 751
 752 Also, for testing purposes, there is simple Java application named
 753 WebSocketClient. The application is placed in the
 754 */restconf/websocket-client* project. It accepts a WebSocket URI
 755 as and input parameter. After starting the utility (WebSocketClient
 756 class directly in Eclipse/InteliJ Idea) received notifications should be
 757 displayed in console.
 758
 759 Notifications are always in XML format and look like this:
 760
 761 .. code-block:: xml
 762
 763     <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
 764         <eventTime>2014-09-11T09:58:23+02:00</eventTime>
 765         <data-changed-notification xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:remote">
 766             <data-change-event>
 767                 <path xmlns:meae="http://netconfcentral.org/ns/toaster">/meae:toaster</path>
 768                 <operation>updated</operation>
 769                 <data>
 770                    <!-- updated data -->
 771                 </data>
 772             </data-change-event>
 773         </data-changed-notification>
 774     </notification>
 775
 776 Example use case
 777 ~~~~~~~~~~~~~~~~
 778
 779 The typical use case is listening to data change events to update web
 780 page data in real-time. In this tutorial we will be using toaster as the
 781 base.
 782
 783 When you call *make-toast* RPC, it sets *toasterStatus* to "down" to
 784 reflect that the toaster is busy making toast. When it finishes,
 785 *toasterStatus* is set to "up" again. We will listen to this toaster
 786 status changes in data store and will reflect it on our web page in
 787 real-time thanks to WebSocket data change notification.
 788
 789 Simple javascript client implementation
 790 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 791
 792 We will create simple JavaScript web application that will listen
 793 updates on *toasterStatus* leaf and update some element of our web page
 794 according to new toaster status state.
 795
 796 Create stream
 797 ^^^^^^^^^^^^^
 798
 799 First you need to create stream that you are planing to subscribe to.
 800 This can be achieved by invoking "create-data-change-event-subscription"
 801 RPC on RESTCONF via AJAX request. You need to provide data store
 802 **path** that you plan to listen on, **data store type** and **scope**.
 803 If the request is successful you can extract the **stream-name** from
 804 the response and use that to subscribe to the newly created stream. The
 805 *{username}* and *{password}* fields represent your credentials that you
 806 use to connect to OpenDaylight via RESTCONF:
 807
 808 .. note::
 809
 810     The default user name and password are "admin".
 811
 812 .. code-block:: javascript
 813
 814     function createStream() {
 815         $.ajax(
 816             {
 817                 url: 'http://{odlAddress}:{odlPort}/rests/operations/sal-remote:create-data-change-event-subscription',
 818                 type: 'POST',
 819                 headers: {
 820                   'Authorization': 'Basic ' + btoa('{username}:{password}'),
 821                   'Content-Type': 'application/json'
 822                 },
 823                 data: JSON.stringify(
 824                     {
 825                         'input': {
 826                             'path': '/toaster:toaster/toaster:toasterStatus',
 827                             'sal-remote-augment:datastore': 'OPERATIONAL',
 828                             'sal-remote-augment:scope': 'ONE'
 829                         }
 830                     }
 831                 )
 832             }).done(function (data) {
 833                 // this function will be called when ajax call is executed successfully
 834                 subscribeToStream(data.output['stream-name']);
 835             }).fail(function (data) {
 836                 // this function will be called when ajax call fails
 837                 console.log("Create stream call unsuccessful");
 838             })
 839     }
 840
 841 Subscribe to stream
 842 ^^^^^^^^^^^^^^^^^^^
 843
 844 The Next step is to subscribe to the stream. To subscribe to the stream
 845 you need to call *GET* on
 846 *http://{odlAddress}:{odlPort}/rests/data/ietf-restconf-monitoring:restconf-state/streams/stream/{stream-name}*.
 847 If the call is successful, you get WebSocket address for this stream in
 848 **Location** parameter inside response header. You can get response
 849 header by calling *getResponseHeader(\ *Location*)* on HttpRequest
 850 object inside *done()* function call:
 851
 852 .. code-block:: javascript
 853
 854     function subscribeToStream(streamName) {
 855         $.ajax(
 856             {
 857                 url: 'http://{odlAddress}:{odlPort}/rests/data/ietf-restconf-monitoring:restconf-state/streams/stream/' + streamName;
 858                 type: 'GET',
 859                 headers: {
 860                   'Authorization': 'Basic ' + btoa('{username}:{password}'),
 861                 }
 862             }
 863         ).done(function (data, textStatus, httpReq) {
 864             // we need function that has http request object parameter in order to access response headers.
 865             listenToNotifications(httpReq.getResponseHeader('Location'));
 866         }).fail(function (data) {
 867             console.log("Subscribe to stream call unsuccessful");
 868         });
 869     }
 870
 871 Receive notifications
 872 ^^^^^^^^^^^^^^^^^^^^^
 873
 874 Once you got WebSocket server location you can now connect to it and
 875 start receiving data change events. You need to define functions that
 876 will handle events on WebSocket. In order to process incoming events
 877 from OpenDaylight you need to provide a function that will handle
 878 *onmessage* events. The function must have one parameter that represents
 879 the received event object. The event data will be stored in
 880 *event.data*. The data will be in an XML format that you can then easily
 881 parse using jQuery.
 882
 883 .. code-block:: javascript
 884
 885     function listenToNotifications(socketLocation) {
 886         try {
 887             var notificatinSocket = new WebSocket(socketLocation);
 888
 889             notificatinSocket.onmessage = function (event) {
 890                 // we process our received event here
 891                 console.log('Received toaster data change event.');
 892                 $($.parseXML(event.data)).find('data-change-event').each(
 893                     function (index) {
 894                         var operation = $(this).find('operation').text();
 895                         if (operation == 'updated') {
 896                             // toaster status was updated so we call function that gets the value of toasterStatus leaf
 897                             updateToasterStatus();
 898                             return false;
 899                         }
 900                     }
 901                 );
 902             }
 903             notificatinSocket.onerror = function (error) {
 904                 console.log("Socket error: " + error);
 905             }
 906             notificatinSocket.onopen = function (event) {
 907                 console.log("Socket connection opened.");
 908             }
 909             notificatinSocket.onclose = function (event) {
 910                 console.log("Socket connection closed.");
 911             }
 912             // if there is a problem on socket creation we get exception (i.e. when socket address is incorrect)
 913         } catch(e) {
 914             alert("Error when creating WebSocket" + e );
 915         }
 916     }
 917
 918 The *updateToasterStatus()* function represents function that calls
 919 *GET* on the path that was modified and sets toaster status in some web
 920 page element according to received data. After the WebSocket connection
 921 has been established you can test events by calling make-toast RPC via
 922 RESTCONF.
 923
 924 .. note::
 925
 926     for more information about WebSockets in JavaScript visit `Writing
 927     WebSocket client
 928     applications <https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API/Writing_WebSocket_client_applications>`__
 929
 930 Netconf-connector + Netopeer
 931 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 932
 933 `Netopeer <https://github.com/cesnet/netopeer>`__ (an open-source
 934 NETCONF server) can be used for testing/exploring NETCONF southbound in
 935 OpenDaylight.
 936
 937 Netopeer installation
 938 ^^^^^^^^^^^^^^^^^^^^^
 939
 940 A `Docker <https://www.docker.com/>`__ container with netopeer will be
 941 used in this guide. To install Docker and start the `netopeer
 942 image <https://hub.docker.com/r/sysrepo/sysrepo-netopeer2>`__ perform
 943 following steps:
 944
 945 1. Install docker https://docs.docker.com/get-started/
 946
 947 2. Start the netopeer image:
 948
 949    ::
 950
 951        docker run -it --name sysrepo -p 830:830 --rm sysrepo/sysrepo-netopeer2:latest
 952
 953 3. Verify netopeer is running by invoking (netopeer should send its
 954    HELLO message right away:
 955
 956    ::
 957
 958        ssh root@localhost -p 830 -s netconf
 959        (password root)
 960
 961 Mounting netopeer NETCONF server
 962 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 963
 964 Preconditions:
 965
 966 -  OpenDaylight is started with features ``odl-restconf-all`` and
 967    ``odl-netconf-connector-all``.
 968
 969 -  Netopeer is up and running in docker
 970
 971 Now just follow the section: `Spawning new NETCONF connectors`_.
 972 In the payload change the:
 973
 974 -  name, e.g., to netopeer
 975
 976 -  username/password to your system credentials
 977
 978 -  ip to localhost
 979
 980 -  port to 1831.
 981
 982 After netopeer is mounted successfully, its configuration can be read
 983 using RESTCONF by invoking:
 984
 985 GET
 986 http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netopeer/yang-ext:mount?content:config
 987
 988 Northbound (NETCONF servers)
 989 ----------------------------
 990
 991 OpenDaylight provides 2 types of NETCONF servers:
 992
 993 -  **NETCONF server for config-subsystem (listening by default on port
 994    1830)**
 995
 996    -  Serves as a default interface for config-subsystem and allows
 997       users to spawn/reconfigure/destroy modules (or applications) in
 998       OpenDaylight
 999
1000 -  **NETCONF server for MD-SAL (listening by default on port 2830)**
1001
1002    -  Serves as an alternative interface for MD-SAL (besides RESTCONF)
1003       and allows users to read/write data from MD-SAL’s datastore and to
1004       invoke its rpcs (NETCONF notifications are not available in the
1005       Boron release of OpenDaylight)
1006
1007 .. note::
1008
1009     The reason for having 2 NETCONF servers is that config-subsystem and
1010     MD-SAL are 2 different components of OpenDaylight and require
1011     different approach for NETCONF message handling and data
1012     translation. These 2 components will probably merge in the future.
1013
1014 .. note::
1015
1016     Since Nitrogen release, there is performance regression in NETCONF
1017     servers accepting SSH connections. While opening a connection takes
1018     less than 10 seconds on Carbon, on Nitrogen time can increase up to
1019     60 seconds. Please see https://jira.opendaylight.org/browse/ODLPARENT-112
1020
1021 NETCONF server for config-subsystem
1022 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1023
1024 This NETCONF server is the primary interface for config-subsystem. It
1025 allows the users to interact with config-subsystem in a standardized
1026 NETCONF manner.
1027
1028 In terms of RFCs, these are supported:
1029
1030 -  `RFC-6241 <https://www.rfc-editor.org/rfc/rfc6241>`__
1031
1032 -  `RFC-5277 <https://www.rfc-editor.org/rfc/rfc5277>`__
1033
1034 -  `RFC-6470 <https://www.rfc-editor.org/rfc/rfc6470>`__
1035
1036    -  (partially, only the schema-change notification is available in
1037       Boron release)
1038
1039 -  `RFC-6022 <https://www.rfc-editor.org/rfc/rfc6022>`__
1040
1041 For regular users it is recommended to use RESTCONF + the
1042 controller-config loopback mountpoint instead of using pure NETCONF. How
1043 to do that is spesific for each component/module/application in
1044 OpenDaylight and can be found in their dedicated user guides.
1045
1046 NETCONF server for MD-SAL
1047 ~~~~~~~~~~~~~~~~~~~~~~~~~
1048
1049 This NETCONF server is just a generic interface to MD-SAL in
1050 OpenDaylight. It uses the stadard MD-SAL APIs and serves as an
1051 alternative to RESTCONF. It is fully model driven and supports any data
1052 and rpcs that are supported by MD-SAL.
1053
1054 In terms of RFCs, these are supported:
1055
1056 -  `RFC-6241 <https://www.rfc-editor.org/rfc/rfc6241>`__
1057
1058 -  `RFC-6022 <https://www.rfc-editor.org/rfc/rfc6022>`__
1059
1060 -  `RFC-7895 <https://www.rfc-editor.org/rfc/rfc7895>`__
1061
1062 Notifications over NETCONF are not supported in the Boron release.
1063
1064 .. tip::
1065
1066     Install NETCONF northbound for MD-SAL by installing feature:
1067     ``odl-netconf-mdsal`` in karaf. Default binding port is **2830**.
1068
1069 Configuration
1070 ^^^^^^^^^^^^^
1071
1072 The default configuration can be found in file: *08-netconf-mdsal.xml*.
1073 The file contains the configuration for all necessary dependencies and a
1074 single SSH endpoint starting on port 2830. There is also a (by default
1075 disabled) TCP endpoint. It is possible to start multiple endpoints at
1076 the same time either in the initial configuration file or while
1077 OpenDaylight is running.
1078
1079 The credentials for SSH endpoint can also be configured here, the
1080 defaults are admin/admin. Credentials in the SSH endpoint are not yet
1081 managed by the centralized AAA component and have to be configured
1082 separately.
1083
1084 Verifying MD-SAL’s NETCONF server
1085 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1086
1087 After the NETCONF server is available it can be examined by a command
1088 line ssh tool:
1089
1090 ::
1091
1092     ssh admin@localhost -p 2830 -s netconf
1093
1094 The server will respond by sending its HELLO message and can be used as
1095 a regular NETCONF server from then on.
1096
1097 Mounting the MD-SAL’s NETCONF server
1098 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1099
1100 To perform this operation, just spawn a new netconf-connector as
1101 described in `Spawning new NETCONF connectors`_. Just change the ip to
1102 "127.0.0.1" port to "2830" and its name to "controller-mdsal".
1103
1104 Now the MD-SAL’s datastore can be read over RESTCONF via NETCONF by
1105 invoking:
1106
1107 GET
1108 http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=controller-mdsal/yang-ext:mount?content:nonconfig
1109
1110 .. note::
1111
1112     This might not seem very useful, since MD-SAL can be accessed
1113     directly from RESTCONF or from Application code, but the same method
1114     can be used to mount and control other OpenDaylight instances by the
1115     "master OpenDaylight".
1116
1117 NETCONF stress/performance measuring tool
1118 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1119
1120 This is basically a NETCONF client that puts NETCONF servers under heavy
1121 load of NETCONF RPCs and measures the time until a configurable amount
1122 of them is processed.
1123
1124 RESTCONF stress-performance measuring tool
1125 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1126
1127 Very similar to NETCONF stress tool with the difference of using
1128 RESTCONF protocol instead of NETCONF.
1129
1130 YANGLIB remote repository
1131 -------------------------
1132
1133 There are scenarios in NETCONF deployment, that require for a centralized
1134 YANG models repository. YANGLIB plugin provides such remote repository.
1135
1136 To start this plugin, you have to install odl-yanglib feature. Then you
1137 have to configure YANGLIB either through RESTCONF or NETCONF. We will
1138 show how to configure YANGLIB through RESTCONF.
1139
1140 YANGLIB configuration through RESTCONF
1141 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1142
1143 You have to specify what local YANG modules directory you want to provide.
1144 Then you have to specify address and port whre you want to provide YANG
1145 sources. For example, we want to serve yang sources from folder /sources
1146 on localhost:8181 adress. The configuration for this scenario will be
1147 as follows:
1148
1149 ::
1150
1151     PUT  http://localhost:8181/rests/data/yanglib:yanglib-config
1152
1153 Headers:
1154
1155 -  Accept: application/xml
1156
1157 -  Content-Type: application/xml
1158
1159 Payload:
1160
1161 ::
1162
1163     <yanglib-config xmlns="urn:opendaylight:params:xml:ns:yang:controller:yanglib:impl">
1164         <cache-folder>cache/newSchema</cache-folder>
1165         <binding-addr>localhost</binding-addr>
1166         <binding-port>8181</binding-port>
1167     </yanglib-config>
1168
1169 This should result in a 2xx response and new YANGLIB instance should be
1170 created. This YANGLIB takes all YANG sources from /sources folder and
1171 for each generates URL in form:
1172
1173 ::
1174
1175     http://localhost:8181/yanglib/schemas/{modelName}/{revision}
1176
1177 On this URL will be hosted YANG source for particular module.
1178
1179 YANGLIB instance also write this URL along with source identifier to
1180 ietf-netconf-yang-library/modules-state/module list.
1181
1182 Netconf-connector with YANG library as fallback
1183 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1184
1185 There is an optional configuration in netconf-connector called
1186 yang-library. You can specify YANG library to be plugged as additional
1187 source provider into the mount's schema repository. Since YANGLIB
1188 plugin is advertising provided modules through yang-library model, we
1189 can use it in mount point's configuration as YANG library.  To do this,
1190 we need to modify the configuration of netconf-connector by adding this
1191 XML
1192
1193 ::
1194
1195     <yang-library xmlns="urn:opendaylight:netconf-node-topology">
1196       <yang-library-url xmlns="urn:opendaylight:netconf-node-topology">http://localhost:8181/rests/data/ietf-yang-library:modules-state</yang-library-url>
1197       <username xmlns="urn:opendaylight:netconf-node-topology">admin</username>
1198       <password xmlns="urn:opendaylight:netconf-node-topology">admin</password>
1199     </yang-library>
1200
1201 This will register YANGLIB provided sources as a fallback schemas for
1202 particular mount point.
1203
1204 NETCONF Call Home
1205 -----------------
1206
1207 Call Home Installation
1208 ~~~~~~~~~~~~~~~~~~~~~~
1209
1210 ODL Call-Home server is installed in Karaf by installing karaf feature
1211 ``odl-netconf-callhome-ssh``. RESTCONF feature is recommended for
1212 configuring Call Home & testing its functionality.
1213
1214 ::
1215
1216   feature:install odl-netconf-callhome-ssh
1217
1218
1219 .. note::
1220
1221     In order to test Call Home functionality we recommend Netopeer or
1222     Netopeer2. See `Netopeer Call Home <https://github.com/CESNET/netopeer/wiki/CallHome>`__
1223     or `Netopeer2 <https://github.com/CESNET/netopeer2>`__ to learn how to
1224     enable call-home on Netopeer.
1225
1226 Northbound Call-Home API
1227 ~~~~~~~~~~~~~~~~~~~~~~~~
1228
1229 The northbound Call Home API is used for administering the Call-Home Server. The
1230 following describes this configuration.
1231
1232 Global Configuration
1233 ^^^^^^^^^^^^^^^^^^^^
1234
1235 .. important::
1236   The global configuration is not a part of the `RFC 8071
1237   <https://www.rfc-editor.org/rfc/rfc8071>`__ and, therefore, subject to change.
1238
1239 Configuring global credentials
1240 ''''''''''''''''''''''''''''''
1241
1242 ODL Call-Home server allows user to configure global credentials, which will be
1243 used for connected over SSH transport protocol devices which does not have
1244 device-specific credentials configured.
1245
1246 This is done by creating
1247 ``/odl-netconf-callhome-server:netconf-callhome-server/global/credentials``
1248 with username and passwords specified.
1249
1250 *Configuring global username & passwords to try*
1251
1252 .. code-block::
1253
1254     PUT HTTP/1.1
1255     /rests/data/odl-netconf-callhome-server:netconf-callhome-server/global/credentials
1256     Content-Type: application/json
1257     Accept: application/json
1258
1259 .. code-block:: json
1260
1261     {
1262       "credentials":
1263       {
1264         "username": "example",
1265         "passwords": [ "first-password-to-try", "second-password-to-try" ]
1266       }
1267     }
1268
1269 Configuring to accept any ssh server key using global credentials
1270 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
1271
1272 By default Netconf Call-Home Server accepts only incoming connections
1273 from allowed devices
1274 ``/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices``,
1275 if user desire to allow all incoming connections, it is possible to set
1276 ``accept-all-ssh-keys`` to ``true`` in
1277 ``/odl-netconf-callhome-server:netconf-callhome-server/global``.
1278
1279 The name of this devices in ``netconf-topology`` will be in format
1280 ``ip-address:port``. For naming devices see Device-Specific
1281 Configuration.
1282
1283 *Allowing unknown devices to connect*
1284
1285 This is a debug feature and should not be used in production. Besides being an obvious
1286 security issue, this also causes the Call-Home Server to drastically increase its output
1287 to the log.
1288
1289 .. code-block::
1290
1291     PUT HTTP/1.1
1292     /rests/data/odl-netconf-callhome-server:netconf-callhome-server/global/accept-all-ssh-keys
1293     Content-Type: application/json
1294     Accept: application/json
1295
1296 .. code-block:: json
1297
1298     {
1299         "accept-all-ssh-keys": "true"
1300     }
1301
1302 Device-Specific Configuration
1303 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1304
1305 Netconf Call Home server supports both of the secure transports used
1306 by the Network Configuration Protocol (NETCONF) - Secure Shell (SSH),
1307 and Transport Layer Security (TLS).
1308
1309 Configure device to connect over SSH protocol
1310 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1311
1312 Netconf Call Home Server uses device provided SSH server key (host key)
1313 to identify device. The pairing of name and server key is configured in
1314 ``/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices``.
1315 This list is colloquially called a whitelist.
1316
1317 If the Call-Home Server finds the SSH host key in the whitelist, it continues
1318 to negotiate a NETCONF connection over an SSH session. If the SSH host key is
1319 not found, the connection between the Call Home server and the device is dropped
1320 immediately. In either case, the device that connects to the Call home server
1321 leaves a record of its presence in the operational store.
1322
1323 Configuring Device with Device-specific Credentials
1324 '''''''''''''''''''''''''''''''''''''''''''''''''''
1325
1326 Adding specific device to the allowed list is done by creating
1327 ``/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device={device}``
1328 with device-id and connection parameters inside the ssh-client-params container.
1329
1330 *Configuring Device with Credentials*
1331
1332 .. code-block::
1333
1334     PUT HTTP/1.1
1335     /rests/data/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device=example
1336     Content-Type: application/json
1337     Accept: application/json
1338
1339 .. code-block:: json
1340
1341     {
1342       "device": {
1343         "unique-id": "example",
1344         "ssh-client-params": {
1345           "credentials": {
1346             "username": "example",
1347             "passwords": [ "password" ]
1348           },
1349           "host-key": "AAAAB3NzaC1yc2EAAAADAQABAAABAQDHoH1jMjltOJnCt999uaSfc48ySutaD3ISJ9fSECe1Spdq9o9mxj0kBTTTq+2V8hPspuW75DNgN+V/rgJeoUewWwCAasRx9X4eTcRrJrwOQKzb5Fk+UKgQmenZ5uhLAefi2qXX/agFCtZi99vw+jHXZStfHm9TZCAf2zi+HIBzoVksSNJD0VvPo66EAvLn5qKWQD4AdpQQbKqXRf5/W8diPySbYdvOP2/7HFhDukW8yV/7ZtcywFUIu3gdXsrzwMnTqnATSLPPuckoi0V2jd8dQvEcu1DY+rRqmqu0tEkFBurlRZDf1yhNzq5xWY3OXcjgDGN+RxwuWQK3cRimcosH"
1350         }
1351       }
1352     }
1353
1354 Configuring Device with Global Credentials
1355 '''''''''''''''''''''''''''''''''''''''''''''''''''
1356
1357 It is possible to omit ``username`` and ``password`` for ssh-client-params,
1358 in such case values from global credentials will be used.
1359
1360 *Example of configuring device*
1361
1362 .. code-block::
1363
1364     PUT HTTP/1.1
1365     /rests/data/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device=example
1366     Content-Type: application/json
1367     Accept: application/json
1368
1369 .. code-block:: json
1370
1371     {
1372       "device": {
1373         "unique-id": "example",
1374         "ssh-client-params": {
1375           "host-key": "AAAAB3NzaC1yc2EAAAADAQABAAABAQDHoH1jMjltOJnCt999uaSfc48ySutaD3ISJ9fSECe1Spdq9o9mxj0kBTTTq+2V8hPspuW75DNgN+V/rgJeoUewWwCAasRx9X4eTcRrJrwOQKzb5Fk+UKgQmenZ5uhLAefi2qXX/agFCtZi99vw+jHXZStfHm9TZCAf2zi+HIBzoVksSNJD0VvPo66EAvLn5qKWQD4AdpQQbKqXRf5/W8diPySbYdvOP2/7HFhDukW8yV/7ZtcywFUIu3gdXsrzwMnTqnATSLPPuckoi0V2jd8dQvEcu1DY+rRqmqu0tEkFBurlRZDf1yhNzq5xWY3OXcjgDGN+RxwuWQK3cRimcosH"
1376         }
1377       }
1378     }
1379
1380 Deprecated configuration models for devices accessed with SSH protocol
1381 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
1382
1383 With `RFC 8071 <https://www.rfc-editor.org/rfc/rfc8071>`__ alignment and adding
1384 support for TLS transport following configuration models has been marked
1385 deprecated.
1386
1387 Configuring Device with Global Credentials
1388 '''''''''''''''''''''''''''''''''''''''''''''''''''
1389
1390 *Example of configuring device*
1391
1392 .. code-block::
1393
1394     PUT HTTP/1.1
1395     /rests/data/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device=example
1396     Content-Type: application/json
1397     Accept: application/json
1398
1399 .. code-block:: json
1400
1401     {
1402       "device": {
1403         "unique-id": "example",
1404         "ssh-host-key": "AAAAB3NzaC1yc2EAAAADAQABAAABAQDHoH1jMjltOJnCt999uaSfc48ySutaD3ISJ9fSECe1Spdq9o9mxj0kBTTTq+2V8hPspuW75DNgN+V/rgJeoUewWwCAasRx9X4eTcRrJrwOQKzb5Fk+UKgQmenZ5uhLAefi2qXX/agFCtZi99vw+jHXZStfHm9TZCAf2zi+HIBzoVksSNJD0VvPo66EAvLn5qKWQD4AdpQQbKqXRf5/W8diPySbYdvOP2/7HFhDukW8yV/7ZtcywFUIu3gdXsrzwMnTqnATSLPPuckoi0V2jd8dQvEcu1DY+rRqmqu0tEkFBurlRZDf1yhNzq5xWY3OXcjgDGN+RxwuWQK3cRimcosH"
1405       }
1406     }
1407
1408 Configuring Device with Device-specific Credentials
1409 '''''''''''''''''''''''''''''''''''''''''''''''''''
1410
1411 Call Home Server also allows to configure credentials per device basis,
1412 this is done by introducing ``credentials`` container into
1413 device-specific configuration. Format is same as in global credentials.
1414
1415 *Configuring Device with Credentials*
1416
1417 .. code-block::
1418
1419     PUT HTTP/1.1
1420     /rests/data/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device=example
1421     Content-Type: application/json
1422     Accept: application/json
1423
1424 .. code-block:: json
1425
1426     {
1427       "device": {
1428         "unique-id": "example",
1429         "credentials": {
1430           "username": "example",
1431           "passwords": [ "password" ]
1432         },
1433         "ssh-host-key": "AAAAB3NzaC1yc2EAAAADAQABAAABAQDHoH1jMjltOJnCt999uaSfc48ySutaD3ISJ9fSECe1Spdq9o9mxj0kBTTTq+2V8hPspuW75DNgN+V/rgJeoUewWwCAasRx9X4eTcRrJrwOQKzb5Fk+UKgQmenZ5uhLAefi2qXX/agFCtZi99vw+jHXZStfHm9TZCAf2zi+HIBzoVksSNJD0VvPo66EAvLn5qKWQD4AdpQQbKqXRf5/W8diPySbYdvOP2/7HFhDukW8yV/7ZtcywFUIu3gdXsrzwMnTqnATSLPPuckoi0V2jd8dQvEcu1DY+rRqmqu0tEkFBurlRZDf1yhNzq5xWY3OXcjgDGN+RxwuWQK3cRimcosH"
1434       }
1435     }
1436
1437 Configure device to connect over TLS protocol
1438 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1439
1440 Netconf Call Home Server allows devices to use TLS transport protocol to
1441 establish a connection towards the NETCONF device. This communication
1442 requires proper setup to make two-way TLS authentication possible for client
1443 and server.
1444
1445 The initial step is to configure certificates and keys for two-way TLS by
1446 storing them within the netconf-keystore.
1447
1448 *Adding a client private key credential to the netconf-keystore*
1449
1450 .. code-block::
1451
1452     POST HTTP/1.1
1453     /rests/operations/netconf-keystore:add-keystore-entry
1454     Content-Type: application/json
1455     Accept: application/json
1456
1457 .. code-block:: json
1458
1459   {
1460     "input": {
1461       "key-credential": [
1462         {
1463           "key-id": "example-client-key-id",
1464           "private-key": "base64encoded-private-key",
1465           "passphrase": "passphrase"
1466         }
1467       ]
1468     }
1469   }
1470
1471 *Associate a private key with a client and CA certificates chain*
1472
1473 .. code-block::
1474
1475     POST HTTP/1.1
1476     /rests/operations/netconf-keystore:add-private-key
1477     Content-Type: application/json
1478     Accept: application/json
1479
1480 .. code-block:: json
1481
1482   {
1483     "input": {
1484       "private-key": [
1485         {
1486           "name": "example-client-key-id",
1487           "data": "key-data",
1488           "certificate-chain": [
1489             "certificate-data"
1490           ]
1491         }
1492       ]
1493     }
1494   }
1495
1496 *Add a list of trusted CA and server certificates*
1497
1498 .. code-block::
1499
1500     POST HTTP/1.1
1501     /rests/operations/netconf-keystore:add-trusted-certificate
1502     Content-Type: application/json
1503     Accept: application/json
1504
1505 .. code-block:: json
1506
1507   {
1508     "input": {
1509       "trusted-certificate": [
1510         {
1511           "name": "example-ca-certificate",
1512           "certificate": "ca-certificate-data"
1513         },
1514         {
1515           "name": "example-server-certificate",
1516           "certificate": "server-certificate-data"
1517         }
1518       ]
1519     }
1520   }
1521
1522 In a second step, it is required to create an allowed device associated with
1523 a server certificate and client key. The server certificate will be used to
1524 identify and pin the NETCONF device during SSL handshake and should be unique
1525 among the allowed devices.
1526
1527 *Add device configuration for TLS protocol to allowed devices list*
1528
1529 .. code-block::
1530
1531     PUT HTTP/1.1
1532     /rests/data/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device=example-device
1533     Content-Type: application/json
1534     Accept: application/json
1535
1536 .. code-block:: json
1537
1538   {
1539     "device": {
1540       "unique-id": "example-device",
1541       "tls-client-params": {
1542         "key-id": "example-client-key-id",
1543         "certificate-id": "example-server-certificate"
1544       }
1545     }
1546   }
1547
1548 Operational Status
1549 ^^^^^^^^^^^^^^^^^^
1550
1551 Once an entry is made into the config side of "allowed-devices", the Call-Home Server will
1552 populate an corresponding operational device that is the same as the config device but
1553 has an additional status. By default, this status is *DISCONNECTED*. Once a device calls
1554 home, this status will change to one of:
1555
1556 *CONNECTED* — The device is currently connected and the NETCONF mount is available for network
1557 management.
1558
1559 *FAILED_AUTH_FAILURE* — The last attempted connection was unsuccessful because the Call-Home
1560 Server was unable to provide the acceptable credentials of the device. The device is also
1561 disconnected and not available for network management.
1562
1563 *FAILED_NOT_ALLOWED* — The last attempted connection was unsuccessful because the device was
1564 not recognized as an acceptable device. The device is also disconnected and not available for
1565 network management.
1566
1567 *FAILED* — The last attempted connection was unsuccessful for a reason other than not
1568 allowed to connect or incorrect client credentials. The device is also disconnected and not
1569 available for network management.
1570
1571 *DISCONNECTED* — The device is currently disconnected.
1572
1573 Rogue Devices
1574 '''''''''''''
1575
1576 Devices which are not on the whitelist might try to connect to the Call-Home Server. In
1577 these cases, the server will keep a record by instantiating an operational device. There
1578 will be no corresponding config device for these rogues. They can be identified readily
1579 because their device id, rather than being user-supplied, will be of the form
1580 "address:port". Note that if a device calls back multiple times, there will only be
1581 a single operatinal entry (even if the port changes); these devices are recognized by
1582 their unique host key.
1583
1584 Southbound Call-Home API
1585 ~~~~~~~~~~~~~~~~~~~~~~~~
1586
1587 The Call-Home Server listens for incoming TCP connections and assumes that the other side of
1588 the connection is a device calling home via a NETCONF connection with SSH for
1589 management. The server uses port 6666 by default and this can be configured via a
1590 blueprint configuration file.
1591
1592 The device **must** initiate the connection and the server will not try to re-establish the
1593 connection in case of a drop. By requirement, the server cannot assume it has connectivity
1594 to the device due to NAT or firewalls among others.
1595
1596 Reading data with selected fields
1597 ---------------------------------
1598
1599 Overview
1600 ~~~~~~~~
1601
1602 If user would like to read only selected fields from NETCONF device, it is possible to use
1603 fields query parameter that is described by RFC-8040. RESTCONF parses content of query
1604 parameter into format that is accepted by NETCONF subtree filtering - filtering of data is done
1605 on NETCONF server, not on NETCONF client side. This approach optimizes network traffic load,
1606 because data in which user doesn't have interest, is not transferred over network.
1607
1608 Next advantages:
1609
1610 * using single RESTCONF request and single NETCONF RPC for reading multiple subtrees
1611 * possibility to read only selected fields under list node across multiple hierarchies
1612   (it cannot be done without proper selection API)
1613
1614 .. note::
1615
1616   More information about fields query parameter: `RFC 8071 <https://www.rfc-editor.org/rfc/rfc8040#section-4.8.3>`__
1617
1618 Preparation of data
1619 ~~~~~~~~~~~~~~~~~~~
1620
1621 For demonstration, we will define next YANG model:
1622
1623 ::
1624
1625     module test-module {
1626         yang-version 1.1;
1627         namespace "urn:opendaylight:test-module";
1628         prefix "tm";
1629         revision "2023-02-16";
1630
1631         container root {
1632             container simple-root {
1633                 leaf leaf-a {
1634                     type string;
1635                 }
1636                 leaf leaf-b {
1637                     type string;
1638                 }
1639                 leaf-list ll {
1640                     type string;
1641                 }
1642                 container nested {
1643                     leaf sample-x {
1644                         type boolean;
1645                     }
1646                     leaf sample-y {
1647                         type boolean;
1648                     }
1649                 }
1650             }
1651
1652             container list-root {
1653                 leaf branch-ab {
1654                     type int32;
1655                 }
1656                 list top-list {
1657                     key "key-1 key-2";
1658                     ordered-by user;
1659                     leaf key-1 {
1660                         type string;
1661                     }
1662                     leaf key-2 {
1663                         type string;
1664                     }
1665                     container next-data {
1666                         leaf switch-1 {
1667                             type empty;
1668                         }
1669                         leaf switch-2 {
1670                             type empty;
1671                         }
1672                     }
1673                     list nested-list {
1674                         key "identifier";
1675                         leaf identifier {
1676                             type string;
1677                         }
1678                         leaf foo {
1679                             type int32;
1680                         }
1681                     }
1682                 }
1683             }
1684         }
1685     }
1686
1687 Follow the :doc:`testtool` instructions to save this schema and run it with testtool.
1688
1689 Mounting NETCONF device that runs on NETCONF testtool:
1690
1691 .. code-block:: bash
1692
1693   curl --location --request PUT 'http://127.0.0.1:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=testtool' \
1694   --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
1695   --header 'Content-Type: application/json' \
1696   --data-raw '{
1697       "node": [
1698           {
1699               "node-id": "testtool",
1700               "netconf-node-topology:host": "127.0.0.1",
1701               "netconf-node-topology:port": 17830,
1702               "netconf-node-topology:keepalive-delay": 100,
1703               "netconf-node-topology:tcp-only": false,
1704               "netconf-node-topology:username": "admin",
1705               "netconf-node-topology:password": "admin"
1706           }
1707       ]
1708   }'
1709
1710 Setting initial configuration on NETCONF device:
1711
1712 .. code-block:: bash
1713
1714   curl --location --request PUT 'http://127.0.0.1:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=testtool/yang-ext:mount/test-module:root' \
1715   --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
1716   --header 'Content-Type: application/json' \
1717   --data-raw '{
1718       "root": {
1719           "simple-root": {
1720               "leaf-a": "asddhg",
1721               "leaf-b": "ffffff",
1722               "ll": [
1723                   "str1",
1724                   "str2",
1725                   "str3"
1726               ],
1727               "nested": {
1728                   "sample-x": true,
1729                   "sample-y": false
1730               }
1731           },
1732           "list-root": {
1733               "branch-ab": 5,
1734               "top-list": [
1735                   {
1736                       "key-1": "ka",
1737                       "key-2": "kb",
1738                       "next-data": {
1739                           "switch-1": [
1740                               null
1741                           ],
1742                           "switch-2": [
1743                               null
1744                           ]
1745                       },
1746                       "nested-list": [
1747                           {
1748                               "identifier": "f1",
1749                               "foo": 1
1750                           },
1751                           {
1752                               "identifier": "f2",
1753                               "foo": 10
1754                           },
1755                           {
1756                               "identifier": "f3",
1757                               "foo": 20
1758                           }
1759                       ]
1760                   },
1761                   {
1762                       "key-1": "kb",
1763                       "key-2": "ka",
1764                       "next-data": {
1765                           "switch-1": [
1766                               null
1767                           ]
1768                       },
1769                       "nested-list": [
1770                           {
1771                               "identifier": "e1",
1772                               "foo": 1
1773                           },
1774                           {
1775                               "identifier": "e2",
1776                               "foo": 2
1777                           },
1778                           {
1779                               "identifier": "e3",
1780                               "foo": 3
1781                           }
1782                       ]
1783                   },
1784                   {
1785                       "key-1": "kc",
1786                       "key-2": "ke",
1787                       "next-data": {
1788                           "switch-2": [
1789                               null
1790                           ]
1791                       },
1792                       "nested-list": [
1793                           {
1794                               "identifier": "q1",
1795                               "foo": 13
1796                           },
1797                           {
1798                               "identifier": "q2",
1799                               "foo": 14
1800                           },
1801                           {
1802                               "identifier": "q3",
1803                               "foo": 15
1804                           }
1805                       ]
1806                   }
1807               ]
1808           }
1809       }
1810   }'
1811
1812 Examples
1813 --------
1814
1815 1. Reading whole leaf-list 'll' and leaf 'nested/sample-x' under 'simple-root' container.
1816
1817 RESTCONF request:
1818
1819 .. code-block:: bash
1820
1821     curl --location --request GET 'http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=testtool/yang-ext:mount/test-module:root/simple-root?content=config&fields=ll;nested/sample-x' \
1822     --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
1823     --header 'Cookie: JSESSIONID=node01h4w82eorc1k61866b71qjgj503.node0'
1824
1825 Generated NETCONF RPC request:
1826
1827 .. code-block:: xml
1828
1829     <rpc message-id="m-18" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
1830         <get-config>
1831             <source>
1832                 <running/>
1833             </source>
1834             <filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree">
1835                 <root xmlns="urn:ietf:params:xml:ns:yang:test-model">
1836                     <simple-root>
1837                         <ll/>
1838                         <nested>
1839                             <sample-x/>
1840                         </nested>
1841                     </simple-root>
1842                 </root>
1843             </filter>
1844         </get-config>
1845     </rpc>
1846
1847 .. note::
1848
1849     Using fields query parameter it is also possible to read whole leaf-list or list without
1850     necessity to specify value / key predicate (without reading parent entity). Such scenario
1851     is not permitted in RFC-8040 paths alone - fields query parameter can be used as
1852     workaround for this case.
1853
1854 RESTCONF response:
1855
1856 .. code-block:: json
1857
1858     {
1859         "test-module:simple-root": {
1860             "ll": [
1861                 "str3",
1862                 "str1",
1863                 "str2"
1864             ],
1865             "nested": {
1866                 "sample-x": true
1867             }
1868         }
1869     }
1870
1871 2. Reading all identifiers of 'nested-list' under all elements of 'top-list'.
1872
1873 RESTCONF request:
1874
1875 .. code-block:: bash
1876
1877     curl --location --request GET 'http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=testtool/yang-ext:mount/test-module:root/list-root?content=config&fields=top-list(nested-list/identifier)' \
1878     --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
1879     --header 'Cookie: JSESSIONID=node01h4w82eorc1k61866b71qjgj503.node0'
1880
1881 Generated NETCONF RPC request:
1882
1883 .. code-block:: xml
1884
1885     <rpc message-id="m-27" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
1886         <get-config>
1887             <source>
1888                 <running/>
1889             </source>
1890             <filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree">
1891                 <root xmlns="urn:ietf:params:xml:ns:yang:test-model">
1892                     <list-root>
1893                         <top-list>
1894                             <nested-list>
1895                                 <identifier/>
1896                             </nested-list>
1897                             <key-1/>
1898                             <key-2/>
1899                         </top-list>
1900                     </list-root>
1901                 </root>
1902             </filter>
1903         </get-config>
1904     </rpc>
1905
1906 .. note::
1907
1908     NETCONF client automatically fetches values of list keys since they are required for correct
1909     deserialization of NETCONF response and at the end serialization of response to RESTCONF
1910     response (JSON/XML).
1911
1912 RESTCONF response:
1913
1914 .. code-block:: json
1915
1916     {
1917         "test-module:list-root": {
1918             "top-list": [
1919                 {
1920                     "key-1": "ka",
1921                     "key-2": "kb",
1922                     "nested-list": [
1923                         {
1924                             "identifier": "f3"
1925                         },
1926                         {
1927                             "identifier": "f2"
1928                         },
1929                         {
1930                             "identifier": "f1"
1931                         }
1932                     ]
1933                 },
1934                 {
1935                     "key-1": "kb",
1936                     "key-2": "ka",
1937                     "nested-list": [
1938                         {
1939                             "identifier": "e3"
1940                         },
1941                         {
1942                             "identifier": "e2"
1943                         },
1944                         {
1945                             "identifier": "e1"
1946                         }
1947                     ]
1948                 },
1949                 {
1950                     "key-1": "kc",
1951                     "key-2": "ke",
1952                     "nested-list": [
1953                         {
1954                             "identifier": "q3"
1955                         },
1956                         {
1957                             "identifier": "q2"
1958                         },
1959                         {
1960                             "identifier": "q1"
1961                         }
1962                     ]
1963                 }
1964             ]
1965         }
1966     }
1967
1968 3. Reading value of leaf 'branch-ab' and all values of leaves 'switch-1' that are placed
1969    under 'top-list' list elements.
1970
1971 RESTCONF request:
1972
1973 .. code-block:: bash
1974
1975     curl --location --request GET 'http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=testtool/yang-ext:mount/test-module:root/list-root?content=config&fields=branch-ab;top-list/next-data/switch-1' \
1976     --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
1977     --header 'Cookie: JSESSIONID=node01jx6o5thwae9t1ft7c2zau5zbz4.node0'
1978
1979 Generated NETCONF RPC request:
1980
1981 .. code-block:: xml
1982
1983     <rpc message-id="m-42" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
1984         <get-config>
1985             <source>
1986                 <running/>
1987             </source>
1988             <filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree">
1989                 <root xmlns="urn:ietf:params:xml:ns:yang:test-model">
1990                     <list-root>
1991                         <branch-ab/>
1992                         <top-list>
1993                             <next-data>
1994                                 <switch-1/>
1995                             </next-data>
1996                             <key-1/>
1997                             <key-2/>
1998                         </top-list>
1999                     </list-root>
2000                 </root>
2001             </filter>
2002         </get-config>
2003     </rpc>
2004
2005 RESTCONF response:
2006
2007 .. code-block:: json
2008
2009     {
2010         "test-module:list-root": {
2011             "branch-ab": 5,
2012             "top-list": [
2013                 {
2014                     "key-1": "ka",
2015                     "key-2": "kb",
2016                     "next-data": {
2017                         "switch-1": [
2018                             null
2019                         ]
2020                     }
2021                 },
2022                 {
2023                     "key-1": "kb",
2024                     "key-2": "ka",
2025                     "next-data": {
2026                         "switch-1": [
2027                             null
2028                         ]
2029                     }
2030                 },
2031                 {
2032                     "key-1": "kc",
2033                     "key-2": "ke"
2034                 }
2035             ]
2036         }
2037     }