Update documentation for YangLib feature

[netconf.git] / docs / user-guide.rst

.. _netconf-user-guide:

.. |ss| raw:: html

   <strike>

.. |se| raw:: html

   </strike>

NETCONF User Guide
==================

Overview
--------

NETCONF is an XML-based protocol used for configuration and monitoring
devices in the network. The base NETCONF protocol is described in
`RFC-6241 <http://tools.ietf.org/html/rfc6241>`__.

**NETCONF in OpenDaylight:.**

OpenDaylight supports the NETCONF protocol as a northbound server as
well as a southbound plugin. It also includes a set of test tools for
simulating NETCONF devices and clients.

Southbound (netconf-connector)
------------------------------

The NETCONF southbound plugin is capable of connecting to remote NETCONF
devices and exposing their configuration/operational datastores, RPCs
and notifications as MD-SAL mount points. These mount points allow
applications and remote users (over RESTCONF) to interact with the
mounted devices.

In terms of RFCs, the connector supports:

-  `RFC-6241 <http://tools.ietf.org/html/rfc6241>`__

-  `RFC-5277 <https://tools.ietf.org/html/rfc5277>`__

-  `RFC-6022 <https://tools.ietf.org/html/rfc6022>`__

-  `draft-ietf-netconf-yang-library-06 <https://tools.ietf.org/html/draft-ietf-netconf-yang-library-06>`__

**Netconf-connector is fully model-driven (utilizing the YANG modeling
language) so in addition to the above RFCs, it supports any
data/RPC/notifications described by a YANG model that is implemented by
the device.**

.. tip::

    NETCONF southbound can be activated by installing
    ``odl-netconf-connector-all`` Karaf feature.

Netconf-connector configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

NETCONF connectors are configured directly through the usage of the
network-topology model. You can configure new NETCONF connectors both
through the NETCONF server for MD-SAL (port 2830) or RESTCONF. This guide
focuses on RESTCONF.

.. important::

    There are 2 different endpoints related to RESTCONF protocols:

    - | ``http://localhost:8181/restconf`` is related to `draft-bierman-netconf-restconf-02 <https://tools.ietf.org/html/draft-bierman-netconf-restconf-02>`__,
      | can be activated by installing ``odl-restconf-nb-bierman02``
       Karaf feature.
      | This user guide uses this approach.

    - | ``http://localhost:8181/rests`` is related to `RFC-8040 <https://tools.ietf.org/html/rfc8040>`__,
      | can be activated by installing ``odl-restconf-nb-rfc8040``
       Karaf feature.

    | In case of `RFC-8040 <https://tools.ietf.org/html/rfc8040>`__
     resources for configuration and operational datastores start
     ``/rests/data/``,
    | e. g. GET
     http://localhost:8181/rests/data/network-topology:network-topology
     with response of both datastores. It's allowed to use query
     parameters to distinguish between them.
    | e. g. GET
     http://localhost:8181/rests/data/network-topology:network-topology?content=config
     for configuration datastore
    | and GET
     http://localhost:8181/rests/data/network-topology:network-topology?content=nonconfig
     for operational datastore.

    | Also in case of `RFC-8040 <https://tools.ietf.org/html/rfc8040>`__,
     if a data node in the path expression is a YANG leaf-list or list
     node, the path segment has to be constructed by having leaf-list or
     list node name, followed by an "=" character, then followed by the
     leaf-list or list value. Any reserved characters must be
     percent-encoded.
    | e. g. GET
     http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf?content=config
     for retrieving data from configuration datastore for
     topology-netconf value of topology list is equivalent to the deprecated request
    | |ss| GET |se|
     http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf,
     which is related to `draft-bierman-netconf-restconf-02
     <https://tools.ietf.org/html/draft-bierman-netconf-restconf-02>`__.

    Examples in the `Spawning new NETCONF connectors`_ section include both bierman02 and rfc8040
    formats

Preconditions
^^^^^^^^^^^^^

1. OpenDaylight is running

2. In Karaf, you must have the ``odl-netconf-topology`` or
   ``odl-netconf-clustered-topology`` feature installed.

3. Feature ``odl-restconf`` must be installed

Spawning new NETCONF connectors
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

To create a new NETCONF connector you need to send the following PUT request
to RESTCONF:

.. list-table::
   :widths: 1 5

   * - bierman02
     - http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/new-netconf-device
   * - rfc8040
     - http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=new-netconf-device

You could use the same body to create the new  NETCONF connector with a POST
without specifying the node in the URL:

.. list-table::
   :widths: 1 5

   * - bierman02
     - http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf
   * - rfc8040
     - http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf

Payload:

.. tabs::

   .. tab:: XML

      **Content-type:** ``application/xml``

      **Accept:** ``application/xml``

      **Authentication:** ``admin:admin``

      .. code-block:: xml

         <node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
           <node-id>new-netconf-device</node-id>
           <host xmlns="urn:opendaylight:netconf-node-topology">127.0.0.1</host>
           <port xmlns="urn:opendaylight:netconf-node-topology">17830</port>
           <username xmlns="urn:opendaylight:netconf-node-topology">admin</username>
           <password xmlns="urn:opendaylight:netconf-node-topology">admin</password>
           <tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>
           <!-- non-mandatory fields with default values, you can safely remove these if you do not wish to override any of these values-->
           <reconnect-on-changed-schema xmlns="urn:opendaylight:netconf-node-topology">false</reconnect-on-changed-schema>
           <connection-timeout-millis xmlns="urn:opendaylight:netconf-node-topology">20000</connection-timeout-millis>
           <max-connection-attempts xmlns="urn:opendaylight:netconf-node-topology">0</max-connection-attempts>
           <between-attempts-timeout-millis xmlns="urn:opendaylight:netconf-node-topology">2000</between-attempts-timeout-millis>
           <sleep-factor xmlns="urn:opendaylight:netconf-node-topology">1.5</sleep-factor>
           <!-- keepalive-delay set to 0 turns off keepalives-->
           <keepalive-delay xmlns="urn:opendaylight:netconf-node-topology">120</keepalive-delay>
         </node>

   .. tab:: JSON

      **Content-type:** ``application/json``

      **Accept:** ``application/json``

      **Authentication:** ``admin:admin``

      .. code-block:: json

         {
             "node": [
                 {
                     "node-id": "new-netconf-device",
                     "netconf-node-topology:port": 17830,
                     "netconf-node-topology:reconnect-on-changed-schema": false,
                     "netconf-node-topology:connection-timeout-millis": 20000,
                     "netconf-node-topology:tcp-only": false,
                     "netconf-node-topology:max-connection-attempts": 0,
                     "netconf-node-topology:username": "admin",
                     "netconf-node-topology:password": "admin",
                     "netconf-node-topology:sleep-factor": 1.5,
                     "netconf-node-topology:host": "127.0.0.1",
                     "netconf-node-topology:between-attempts-timeout-millis": 2000,
                     "netconf-node-topology:keepalive-delay": 120
                 }
             ]
         }

Note that the device name in <node-id> element must match the last
element of the restconf URL.

Reconfiguring an existing connector
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The steps to reconfigure an existing connector are exactly the same as
when spawning a new connector. The old connection will be disconnected
and a new connector with the new configuration will be created. This needs
to be done with a PUT request because the node already exists. A POST
request will fail for that reason.

Additionally, a PATCH request can be used to modify an existing
configuration. Currently, only yang-patch (`RFC-8072 <https://tools.ietf.org/html/rfc8072>`__)
is supported. The URL would be the same as the above PUT examples.
Using JSON for the body, the headers needed for the request would
be:

Headers:

-  Accept: application/yang.patch-status+json

-  Content-Type: application/yang.patch+json

Example JSON payload to modify the password entry:

::

    {
      "ietf-restconf:yang-patch" : {
        "patch-id" : "0",
        "edit" : [
          {
            "edit-id" : "edit1",
            "operation" : "merge",
            "target" : "",
            "value" : {
             "node": [
                {
                 "node-id": "new-netconf-device",
                 "netconf-node-topology:password" : "newpassword"
                }
             ]
            }
         }
        ]
      }
    }

Deleting an existing connector
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

To remove an already configured NETCONF connector you need to send a
DELETE request to the same PUT request URL that was used to create the
device:

.. list-table::
   :widths: 1 5

   * - bierman02
     - http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/new-netconf-device
   * - rfc8040
     - http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=new-netconf-device

.. note::

    No body is needed to delete the node/device

Connecting to a device not supporting NETCONF monitoring
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The netconf-connector in OpenDaylight relies on ietf-netconf-monitoring
support when connecting to remote NETCONF device. The
ietf-netconf-monitoring support allows netconf-connector to list and
download all YANG schemas that are used by the device. NETCONF connector
can only communicate with a device if it knows the set of used schemas
(or at least a subset). However, some devices use YANG models internally
but do not support NETCONF monitoring. Netconf-connector can also
communicate with these devices, but you have to side load the necessary
yang models into OpenDaylight’s YANG model cache for netconf-connector.
In general there are 2 situations you might encounter:

**1. NETCONF device does not support ietf-netconf-monitoring but it does
list all its YANG models as capabilities in HELLO message**

This could be a device that internally uses only ietf-inet-types YANG
model with revision 2010-09-24. In the HELLO message that is sent from
this device there is this capability reported:

::

    urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&revision=2010-09-24

**For such devices you only need to put the schema into folder
cache/schema inside your Karaf distribution.**

.. important::

    The file with YANG schema for ietf-inet-types has to be called
    ietf-inet-types@2010-09-24.yang. It is the required naming format of
    the cache.

**2. NETCONF device does not support ietf-netconf-monitoring and it does
NOT list its YANG models as capabilities in HELLO message**

Compared to device that lists its YANG models in HELLO message, in this
case there would be no capability with ietf-inet-types in the HELLO
message. This type of device basically provides no information about the
YANG schemas it uses so its up to the user of OpenDaylight to properly
configure netconf-connector for this device.

Netconf-connector has an optional configuration attribute called
yang-module-capabilities and this attribute can contain a list of "YANG
module based" capabilities. So by setting this configuration attribute,
it is possible to override the "yang-module-based" capabilities reported
in HELLO message of the device. To do this, we need to modify the
configuration of netconf-connector like in the example below:

.. tabs::

   .. tab:: XML

      **Content-type:** ``application/xml``

      **Accept:** ``application/xml``

      **Authentication:** ``admin:admin``

      .. code-block:: xml

         <node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
           <node-id>r5</node-id>
           <host xmlns="urn:opendaylight:netconf-node-topology">127.0.0.1</host>
           <port xmlns="urn:opendaylight:netconf-node-topology">8305</port>
           <username xmlns="urn:opendaylight:netconf-node-topology">root</username>
           <password xmlns="urn:opendaylight:netconf-node-topology">root</password>
           <tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>
           <keepalive-delay xmlns="urn:opendaylight:netconf-node-topology">30</keepalive-delay>
           <yang-module-capabilities xmlns="urn:opendaylight:netconf-node-topology">
             <override>true</override>
             <capability xmlns="urn:opendaylight:netconf-node-topology">
               urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&amp;revision=2013-07-15
             </capability>
           </yang-module-capabilities>
         </node>

   .. tab:: JSON

      **Content-type:** ``application/json``

      **Accept:** ``application/json``

      **Authentication:** ``admin:admin``

      .. code-block:: json

         {
             "node": [
                 {
                     "node-id": "device",
                     "netconf-node-topology:host": "127.0.0.1",
                     "netconf-node-topology:password": "root",
                     "netconf-node-topology:username": "root",
                     "netconf-node-topology:yang-module-capabilities": {
                         "override": true,
                         "capability": [
                             "urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&revision=2013-07-15"
                         ]
                     },
                     "netconf-node-topology:port": 8305,
                     "netconf-node-topology:tcp-only": false,
                     "netconf-node-topology:keepalive-delay": 30
                 }
             ]
         }

**Remember to also put the YANG schemas into the cache folder.**

.. note::

    For putting multiple capabilities, you just need to replicate the
    capability element inside yang-module-capability element.
    Capability element is modeled as a leaf-list. With this
    configuration, we would make the remote device report usage of
    ietf-inet-types in the eyes of netconf-connector.

Connecting to a device supporting only NETCONF 1.0
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

OpenDaylight is schema-based distribution and heavily depends on YANG
models. However some legacy NETCONF devices are not schema-based and
implement just RFC 4741. This type of device does not utilize YANG
models internally and OpenDaylight does not know how to communicate
with such devices, how to validate data, or what the semantics of data
are.

NETCONF connector can communicate also with these devices, but the
trade-offs are worsened possibilities in utilization of NETCONF
mountpoints. Using RESTCONF with such devices is not suported. Also
communicating with schemaless devices from application code is slightly
different.

To connect to schemaless device, there is a optional configuration option
in netconf-node-topology model called schemaless. You have to set this
option to true.

Clustered NETCONF connector
~~~~~~~~~~~~~~~~~~~~~~~~~~~

To spawn NETCONF connectors that are cluster-aware you need to install
the ``odl-netconf-clustered-topology`` karaf feature.

.. warning::

    The ``odl-netconf-topology`` and ``odl-netconf-clustered-topology``
    features are considered **INCOMPATIBLE**. They both manage the same
    space in the datastore and would issue conflicting writes if
    installed together.

Configuration of clustered NETCONF connectors works the same as the
configuration through the topology model in the previous section.

When a new clustered connector is configured the configuration gets
distributed among the member nodes and a NETCONF connector is spawned on
each node. From these nodes a master is chosen which handles the schema
download from the device and all the communication with the device. You
will be able to read/write to/from the device from all slave nodes due
to the proxy data brokers implemented.

You can use the ``odl-netconf-clustered-topology`` feature in a single
node scenario as well but the code that uses akka will be used, so for a
scenario where only a single node is used, ``odl-netconf-topology``
might be preferred.

Netconf-connector utilization
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Once the connector is up and running, users can utilize the new mount
point instance. By using RESTCONF or from their application code. This
chapter deals with using RESTCONF and more information for app
developers can be found in the developers guide or in the official
tutorial application **ncmount** that can be found in the coretutorials
project:

-  https://github.com/opendaylight/coretutorials/tree/master/ncmount

Reading data from the device
^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Just invoke (no body needed):

GET
http://localhost:8080/restconf/operational/network-topology:network-topology/topology/topology-netconf/node/new-netconf-device/yang-ext:mount/

This will return the entire content of operation datastore from the
device. To view just the configuration datastore, change **operational**
in this URL to **config**.

Writing configuration data to the device
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

In general, you cannot simply write any data you want to the device. The
data have to conform to the YANG models implemented by the device. In
this example we are adding a new interface-configuration to the mounted
device (assuming the device supports Cisco-IOS-XR-ifmgr-cfg YANG model).
In fact this request comes from the tutorial dedicated to the
**ncmount** tutorial app.

POST
http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/new-netconf-device/yang-ext:mount/Cisco-IOS-XR-ifmgr-cfg:interface-configurations

::

    <interface-configuration xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-ifmgr-cfg">
        <active>act</active>
        <interface-name>mpls</interface-name>
        <description>Interface description</description>
        <bandwidth>32</bandwidth>
        <link-status></link-status>
    </interface-configuration>

Should return 200 response code with no body.

.. tip::

    This call is transformed into a couple of NETCONF RPCs. Resulting
    NETCONF RPCs that go directly to the device can be found in the
    OpenDaylight logs after invoking ``log:set TRACE
    org.opendaylight.controller.sal.connect.netconf`` in the Karaf
    shell. Seeing the NETCONF RPCs might help with debugging.

This request is very similar to the one where we spawned a new netconf
device. That’s because we used the loopback netconf-connector to write
configuration data into config-subsystem datastore and config-subsystem
picked it up from there.

Invoking custom RPC
^^^^^^^^^^^^^^^^^^^

Devices can implement any additional RPC and as long as it provides YANG
models for it, it can be invoked from OpenDaylight. Following example
shows how to invoke the get-schema RPC (get-schema is quite common among
netconf devices). Invoke:

POST
http://localhost:8181/restconf/operations/network-topology:network-topology/topology/topology-netconf/node/new-netconf-device/yang-ext:mount/ietf-netconf-monitoring:get-schema

::

    <input xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
      <identifier>ietf-yang-types</identifier>
      <version>2013-07-15</version>
    </input>

This call should fetch the source for ietf-yang-types YANG model from
the mounted device.

Netconf-connector + Netopeer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

`Netopeer <https://github.com/cesnet/netopeer>`__ (an open-source
NETCONF server) can be used for testing/exploring NETCONF southbound in
OpenDaylight.

Netopeer installation
^^^^^^^^^^^^^^^^^^^^^

A `Docker <https://www.docker.com/>`__ container with netopeer will be
used in this guide. To install Docker and start the `netopeer
image <https://index.docker.io/u/dockeruser/netopeer/>`__ perform
following steps:

1. Install docker http://docs.docker.com/linux/step_one/

2. Start the netopeer image:

   ::

       docker run --rm -t -p 1831:830 dockeruser/netopeer

3. Verify netopeer is running by invoking (netopeer should send its
   HELLO message right away:

   ::

       ssh root@localhost -p 1831 -s netconf
       (password root)

Mounting netopeer NETCONF server
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Preconditions:

-  OpenDaylight is started with features ``odl-restconf-all`` and
   ``odl-netconf-connector-all``.

-  Netopeer is up and running in docker

Now just follow the section: `Spawning new NETCONF connectors`_.
In the payload change the:

-  name, e.g., to netopeer

-  username/password to your system credentials

-  ip to localhost

-  port to 1831.

After netopeer is mounted successfully, its configuration can be read
using RESTCONF by invoking:

GET
http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/netopeer/yang-ext:mount/

Northbound (NETCONF servers)
----------------------------

OpenDaylight provides 2 types of NETCONF servers:

-  **NETCONF server for config-subsystem (listening by default on port
   1830)**

   -  Serves as a default interface for config-subsystem and allows
      users to spawn/reconfigure/destroy modules (or applications) in
      OpenDaylight

-  **NETCONF server for MD-SAL (listening by default on port 2830)**

   -  Serves as an alternative interface for MD-SAL (besides RESTCONF)
      and allows users to read/write data from MD-SAL’s datastore and to
      invoke its rpcs (NETCONF notifications are not available in the
      Boron release of OpenDaylight)

.. note::

    The reason for having 2 NETCONF servers is that config-subsystem and
    MD-SAL are 2 different components of OpenDaylight and require
    different approach for NETCONF message handling and data
    translation. These 2 components will probably merge in the future.

.. note::

    Since Nitrogen release, there is performance regression in NETCONF
    servers accepting SSH connections. While opening a connection takes
    less than 10 seconds on Carbon, on Nitrogen time can increase up to
    60 seconds. Please see https://bugs.opendaylight.org/show_bug.cgi?id=9020

NETCONF server for config-subsystem
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This NETCONF server is the primary interface for config-subsystem. It
allows the users to interact with config-subsystem in a standardized
NETCONF manner.

In terms of RFCs, these are supported:

-  `RFC-6241 <http://tools.ietf.org/html/rfc6241>`__

-  `RFC-5277 <https://tools.ietf.org/html/rfc5277>`__

-  `RFC-6470 <https://tools.ietf.org/html/rfc6470>`__

   -  (partially, only the schema-change notification is available in
      Boron release)

-  `RFC-6022 <https://tools.ietf.org/html/rfc6022>`__

For regular users it is recommended to use RESTCONF + the
controller-config loopback mountpoint instead of using pure NETCONF. How
to do that is spesific for each component/module/application in
OpenDaylight and can be found in their dedicated user guides.

NETCONF server for MD-SAL
~~~~~~~~~~~~~~~~~~~~~~~~~

This NETCONF server is just a generic interface to MD-SAL in
OpenDaylight. It uses the stadard MD-SAL APIs and serves as an
alternative to RESTCONF. It is fully model driven and supports any data
and rpcs that are supported by MD-SAL.

In terms of RFCs, these are supported:

-  `RFC-6241 <http://tools.ietf.org/html/rfc6241>`__

-  `RFC-6022 <https://tools.ietf.org/html/rfc6022>`__

-  `draft-ietf-netconf-yang-library-06 <https://tools.ietf.org/html/draft-ietf-netconf-yang-library-06>`__

Notifications over NETCONF are not supported in the Boron release.

.. tip::

    Install NETCONF northbound for MD-SAL by installing feature:
    ``odl-netconf-mdsal`` in karaf. Default binding port is **2830**.

Configuration
^^^^^^^^^^^^^

The default configuration can be found in file: *08-netconf-mdsal.xml*.
The file contains the configuration for all necessary dependencies and a
single SSH endpoint starting on port 2830. There is also a (by default
disabled) TCP endpoint. It is possible to start multiple endpoints at
the same time either in the initial configuration file or while
OpenDaylight is running.

The credentials for SSH endpoint can also be configured here, the
defaults are admin/admin. Credentials in the SSH endpoint are not yet
managed by the centralized AAA component and have to be configured
separately.

Verifying MD-SAL’s NETCONF server
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

After the NETCONF server is available it can be examined by a command
line ssh tool:

::

    ssh admin@localhost -p 2830 -s netconf

The server will respond by sending its HELLO message and can be used as
a regular NETCONF server from then on.

Mounting the MD-SAL’s NETCONF server
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

To perform this operation, just spawn a new netconf-connector as
described in `Spawning new NETCONF connectors`_. Just change the ip to
"127.0.0.1" port to "2830" and its name to "controller-mdsal".

Now the MD-SAL’s datastore can be read over RESTCONF via NETCONF by
invoking:

GET
http://localhost:8181/restconf/operational/network-topology:network-topology/topology/topology-netconf/node/controller-mdsal/yang-ext:mount

.. note::

    This might not seem very useful, since MD-SAL can be accessed
    directly from RESTCONF or from Application code, but the same method
    can be used to mount and control other OpenDaylight instances by the
    "master OpenDaylight".

NETCONF stress/performance measuring tool
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This is basically a NETCONF client that puts NETCONF servers under heavy
load of NETCONF RPCs and measures the time until a configurable amount
of them is processed.

RESTCONF stress-performance measuring tool
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Very similar to NETCONF stress tool with the difference of using
RESTCONF protocol instead of NETCONF.

YANGLIB remote repository
-------------------------

There are scenarios in NETCONF deployment, that require for a centralized
YANG models repository. YANGLIB plugin provides such remote repository.

To start this plugin, you have to install odl-yanglib feature. Then you
have to configure YANGLIB either through RESTCONF or NETCONF. We will
show how to configure YANGLIB through RESTCONF.

YANGLIB configuration through RESTCONF
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You have to specify what local YANG modules directory you want to provide.
Then you have to specify address and port whre you want to provide YANG
sources. For example, we want to serve yang sources from folder /sources
on localhost:8181 adress. The configuration for this scenario will be
as follows:

::

    PUT  http://localhost:8181/rests/data/yanglib:yanglib-config

Headers:

-  Accept: application/xml

-  Content-Type: application/xml

Payload:

::

    <yanglib-config xmlns="urn:opendaylight:params:xml:ns:yang:controller:yanglib:impl">
        <cache-folder>cache/newSchema</cache-folder>
        <binding-addr>localhost</binding-addr>
        <binding-port>8181</binding-port>
    </yanglib-config>

This should result in a 2xx response and new YANGLIB instance should be
created. This YANGLIB takes all YANG sources from /sources folder and
for each generates URL in form:

::

    http://localhost:8181/yanglib/schemas/{modelName}/{revision}

On this URL will be hosted YANG source for particular module.

YANGLIB instance also write this URL along with source identifier to
ietf-netconf-yang-library/modules-state/module list.

Netconf-connector with YANG library as fallback
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

There is an optional configuration in netconf-connector called
yang-library. You can specify YANG library to be plugged as additional
source provider into the mount's schema repository. Since YANGLIB
plugin is advertising provided modules through yang-library model, we
can use it in mount point's configuration as YANG library.  To do this,
we need to modify the configuration of netconf-connector by adding this
XML

::

    <yang-library xmlns="urn:opendaylight:netconf-node-topology">
      <yang-library-url xmlns="urn:opendaylight:netconf-node-topology">http://localhost:8181/restconf/operational/ietf-yang-library:modules-state</yang-library-url>
      <username xmlns="urn:opendaylight:netconf-node-topology">admin</username>
      <password xmlns="urn:opendaylight:netconf-node-topology">admin</password>
    </yang-library>

This will register YANGLIB provided sources as a fallback schemas for
particular mount point.

NETCONF Call Home
-----------------

Call Home Installation
~~~~~~~~~~~~~~~~~~~~~~

ODL Call-Home server is installed in Karaf by installing karaf feature
``odl-netconf-callhome-ssh``. RESTCONF feature is recommended for
configuring Call Home & testing its functionality.

::

  feature:install odl-netconf-callhome-ssh


.. note::

    In order to test Call Home functionality we recommend Netopeer or
    Netopeer2. See `Netopeer Call Home <https://github.com/CESNET/netopeer/wiki/CallHome>`__
    or `Netopeer2 <https://github.com/CESNET/netopeer2>`__ to learn how to
    enable call-home on Netopeer.

Northbound Call-Home API
~~~~~~~~~~~~~~~~~~~~~~~~

The northbound Call Home API is used for administering the Call-Home Server. The
following describes this configuration.

Global Configuration
^^^^^^^^^^^^^^^^^^^^

.. important::
  The global configuration is not a part of the `RFC 8071
  <https://tools.ietf.org/html/rfc8071>`__ and, therefore, subject to change.

Configuring global credentials
''''''''''''''''''''''''''''''

ODL Call-Home server allows user to configure global credentials, which will be
used for connected over SSH transport protocol devices which does not have
device-specific credentials configured.

This is done by creating
``/odl-netconf-callhome-server:netconf-callhome-server/global/credentials``
with username and passwords specified.

*Configuring global username & passwords to try*

.. code-block::

    PUT
    /restconf/config/odl-netconf-callhome-server:netconf-callhome-server/global/credentials HTTP/1.1
    Content-Type: application/json
    Accept: application/json

.. code-block:: json

    {
      "credentials":
      {
        "username": "example",
        "passwords": [ "first-password-to-try", "second-password-to-try" ]
      }
    }

Configuring to accept any ssh server key using global credentials
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

By default Netconf Call-Home Server accepts only incoming connections
from allowed devices
``/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices``,
if user desire to allow all incoming connections, it is possible to set
``accept-all-ssh-keys`` to ``true`` in
``/odl-netconf-callhome-server:netconf-callhome-server/global``.

The name of this devices in ``netconf-topology`` will be in format
``ip-address:port``. For naming devices see Device-Specific
Configuration.

*Allowing unknown devices to connect*

This is a debug feature and should not be used in production. Besides being an obvious
security issue, this also causes the Call-Home Server to drastically increase its output
to the log.

.. code-block::

    POST
    /restconf/config/odl-netconf-callhome-server:netconf-callhome-server/global HTTP/1.1
    Content-Type: application/json
    Accept: application/json

.. code-block:: json

    {
      "global": {
        "accept-all-ssh-keys": "true"
      }
    }

Device-Specific Configuration
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Netconf Call Home server supports both of the secure transports used
by the Network Configuration Protocol (NETCONF) - Secure Shell (SSH),
and Transport Layer Security (TLS).

Configure device to connect over SSH protocol
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Netconf Call Home Server uses device provided SSH server key (host key)
to identify device. The pairing of name and server key is configured in
``/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices``.
This list is colloquially called a whitelist.

If the Call-Home Server finds the SSH host key in the whitelist, it continues
to negotiate a NETCONF connection over an SSH session. If the SSH host key is
not found, the connection between the Call Home server and the device is dropped
immediately. In either case, the device that connects to the Call home server
leaves a record of its presence in the operational store.

Configuring Device with Device-specific Credentials
'''''''''''''''''''''''''''''''''''''''''''''''''''

Adding specific device to the allowed list is done by creating
``/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device/{device}``
with device-id and connection parameters inside the ssh-client-params container.

*Configuring Device with Credentials*

.. code-block::

    PUT
    /restconf/config/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device/example HTTP/1.1
    Content-Type: application/json
    Accept: application/json

.. code-block:: json

    {
      "device": {
        "unique-id": "example",
        "ssh-client-params": {
          "credentials": {
            "username": "example",
            "passwords": [ "password" ]
          },
          "ssh-host-key": "AAAAB3NzaC1yc2EAAAADAQABAAABAQDHoH1jMjltOJnCt999uaSfc48ySutaD3ISJ9fSECe1Spdq9o9mxj0kBTTTq+2V8hPspuW75DNgN+V/rgJeoUewWwCAasRx9X4eTcRrJrwOQKzb5Fk+UKgQmenZ5uhLAefi2qXX/agFCtZi99vw+jHXZStfHm9TZCAf2zi+HIBzoVksSNJD0VvPo66EAvLn5qKWQD4AdpQQbKqXRf5/W8diPySbYdvOP2/7HFhDukW8yV/7ZtcywFUIu3gdXsrzwMnTqnATSLPPuckoi0V2jd8dQvEcu1DY+rRqmqu0tEkFBurlRZDf1yhNzq5xWY3OXcjgDGN+RxwuWQK3cRimcosH"
        }
      }
    }

Configuring Device with Global Credentials
'''''''''''''''''''''''''''''''''''''''''''''''''''

It is possible to omit 'username' and 'password' for ssh-client-params,
in such case values from global credentials will be used.

*Example of configuring device*

.. code-block::

    PUT
    /restconf/config/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device/example HTTP/1.1
    Content-Type: application/json
    Accept: application/json

.. code-block:: json

    {
      "device": {
        "unique-id": "example",
        "ssh-client-params": {
          "host-key": "AAAAB3NzaC1yc2EAAAADAQABAAABAQDHoH1jMjltOJnCt999uaSfc48ySutaD3ISJ9fSECe1Spdq9o9mxj0kBTTTq+2V8hPspuW75DNgN+V/rgJeoUewWwCAasRx9X4eTcRrJrwOQKzb5Fk+UKgQmenZ5uhLAefi2qXX/agFCtZi99vw+jHXZStfHm9TZCAf2zi+HIBzoVksSNJD0VvPo66EAvLn5qKWQD4AdpQQbKqXRf5/W8diPySbYdvOP2/7HFhDukW8yV/7ZtcywFUIu3gdXsrzwMnTqnATSLPPuckoi0V2jd8dQvEcu1DY+rRqmqu0tEkFBurlRZDf1yhNzq5xWY3OXcjgDGN+RxwuWQK3cRimcosH"
        }
      }
    }

Deprecated configuration models for devices accessed with SSH protocol
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

With `RFC 8071 <https://tools.ietf.org/html/rfc8071>`__ alignment and adding
support for TLS transport following configuration models has been marked
deprecated.

Configuring Device with Global Credentials
'''''''''''''''''''''''''''''''''''''''''''''''''''

*Example of configuring device*

.. code-block::

    PUT
    /restconf/config/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device/example HTTP/1.1
    Content-Type: application/json
    Accept: application/json

.. code-block:: json

    {
      "device": {
        "unique-id": "example",
        "ssh-host-key": "AAAAB3NzaC1yc2EAAAADAQABAAABAQDHoH1jMjltOJnCt999uaSfc48ySutaD3ISJ9fSECe1Spdq9o9mxj0kBTTTq+2V8hPspuW75DNgN+V/rgJeoUewWwCAasRx9X4eTcRrJrwOQKzb5Fk+UKgQmenZ5uhLAefi2qXX/agFCtZi99vw+jHXZStfHm9TZCAf2zi+HIBzoVksSNJD0VvPo66EAvLn5qKWQD4AdpQQbKqXRf5/W8diPySbYdvOP2/7HFhDukW8yV/7ZtcywFUIu3gdXsrzwMnTqnATSLPPuckoi0V2jd8dQvEcu1DY+rRqmqu0tEkFBurlRZDf1yhNzq5xWY3OXcjgDGN+RxwuWQK3cRimcosH"
      }
    }

Configuring Device with Device-specific Credentials
'''''''''''''''''''''''''''''''''''''''''''''''''''

Call Home Server also allows to configure credentials per device basis,
this is done by introducing ``credentials`` container into
device-specific configuration. Format is same as in global credentials.

*Configuring Device with Credentials*

.. code-block::

    PUT
    /restconf/config/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device/example HTTP/1.1
    Content-Type: application/json
    Accept: application/json

.. code-block:: json

    {
      "device": {
        "unique-id": "example",
        "credentials": {
          "username": "example",
          "passwords": [ "password" ]
        },
        "ssh-host-key": "AAAAB3NzaC1yc2EAAAADAQABAAABAQDHoH1jMjltOJnCt999uaSfc48ySutaD3ISJ9fSECe1Spdq9o9mxj0kBTTTq+2V8hPspuW75DNgN+V/rgJeoUewWwCAasRx9X4eTcRrJrwOQKzb5Fk+UKgQmenZ5uhLAefi2qXX/agFCtZi99vw+jHXZStfHm9TZCAf2zi+HIBzoVksSNJD0VvPo66EAvLn5qKWQD4AdpQQbKqXRf5/W8diPySbYdvOP2/7HFhDukW8yV/7ZtcywFUIu3gdXsrzwMnTqnATSLPPuckoi0V2jd8dQvEcu1DY+rRqmqu0tEkFBurlRZDf1yhNzq5xWY3OXcjgDGN+RxwuWQK3cRimcosH"
      }
    }

Configure device to connect over TLS protocol
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Netconf Call Home Server allows devices to use TLS transport protocol to
establish a connection towards the NETCONF device. This communication
requires proper setup to make two-way TLS authentication possible for client
and server.

The initial step is to configure certificates and keys for two-way TLS by
storing them within the netconf-keystore.

*Adding a client private key credential to the netconf-keystore*

.. code-block::

    POST
    /rests/operations/netconf-keystore:add-keystore-entry HTTP/1.1
    Content-Type: application/json
    Accept: application/json

.. code-block:: json

  {
    "input": {
      "key-credential": [
        {
          "key-id": "example-client-key-id",
          "private-key": "base64encoded-private-key",
          "passphrase": "passphrase"
        }
      ]
    }
  }

*Associate a private key with a client and CA certificates chain*

.. code-block::

    POST
    /rests/operations/netconf-keystore:add-private-key HTTP/1.1
    Content-Type: application/json
    Accept: application/json

.. code-block:: json

  {
    "input": {
      "private-key": [
        {
          "name": "example-client-key-id",
          "data": "key-data",
          "certificate-chain": [
            "certificate-data"
          ]
        }
      ]
    }
  }

*Add a list of trusted CA and server certificates*

.. code-block::

    POST
    /rests/operations/netconf-keystore:add-trusted-certificate HTTP/1.1
    Content-Type: application/json
    Accept: application/json

.. code-block:: json

  {
    "input": {
      "trusted-certificate": [
        {
          "name": "example-ca-certificate",
          "certificate": "ca-certificate-data"
        },
        {
          "name": "example-server-certificate",
          "certificate": "server-certificate-data"
        }
      ]
    }
  }

In a second step, it is required to create an allowed device associated with
a server certificate and client key. The server certificate will be used to
identify and pin the NETCONF device during SSL handshake and should be unique
among the allowed devices.

*Add device configuration for TLS protocol to allowed devices list*

.. code-block::

    PUT
    /restconf/config/odl-netconf-callhome-server:netconf-callhome-server/allowed-devices/device/example-device HTTP/1.1
    Content-Type: application/json
    Accept: application/json

.. code-block:: json

  {
    "device": {
      "unique-id": "example-device",
      "tls-client-params": {
        "key-id": "example-client-key-id",
        "certificate-id": "example-server-certificate"
      }
    }
  }

Operational Status
^^^^^^^^^^^^^^^^^^

Once an entry is made into the config side of "allowed-devices", the Call-Home Server will
populate an corresponding operational device that is the same as the config device but
has an additional status. By default, this status is *DISCONNECTED*. Once a device calls
home, this status will change to one of:

*CONNECTED* — The device is currently connected and the NETCONF mount is available for network
management.

*FAILED_AUTH_FAILURE* — The last attempted connection was unsuccessful because the Call-Home
Server was unable to provide the acceptable credentials of the device. The device is also
disconnected and not available for network management.

*FAILED_NOT_ALLOWED* — The last attempted connection was unsuccessful because the device was
not recognized as an acceptable device. The device is also disconnected and not available for
network management.

*FAILED* — The last attempted connection was unsuccessful for a reason other than not
allowed to connect or incorrect client credentials. The device is also disconnected and not
available for network management.

*DISCONNECTED* — The device is currently disconnected.

Rogue Devices
'''''''''''''

Devices which are not on the whitelist might try to connect to the Call-Home Server. In
these cases, the server will keep a record by instantiating an operational device. There
will be no corresponding config device for these rogues. They can be identified readily
because their device id, rather than being user-supplied, will be of the form
"address:port". Note that if a device calls back multiple times, there will only be
a single operatinal entry (even if the port changes); these devices are recognized by
their unique host key.

Southbound Call-Home API
~~~~~~~~~~~~~~~~~~~~~~~~

The Call-Home Server listens for incoming TCP connections and assumes that the other side of
the connection is a device calling home via a NETCONF connection with SSH for
management. The server uses port 6666 by default and this can be configured via a
blueprint configuration file.

The device **must** initiate the connection and the server will not try to re-establish the
connection in case of a drop. By requirement, the server cannot assume it has connectivity
to the device due to NAT or firewalls among others.

Reading data with selected fields
---------------------------------

Overview
~~~~~~~~

If user would like to read only selected fields from NETCONF device, it is possible to use
fields query parameter that is described by RFC-8040. RESTCONF parses content of query
parameter into format that is accepted by NETCONF subtree filtering - filtering of data is done
on NETCONF server, not on NETCONF client side. This approach optimizes network traffic load,
because data in which user doesn't have interest, is not transferred over network.

Next advantages:

* using single RESTCONF request and single NETCONF RPC for reading multiple subtrees
* possibility to read only selected fields under list node across multiple hierarchies
  (it cannot be done without proper selection API)

.. note::

  More information about fields query parameter: `RFC 8071 <https://tools.ietf.org/html/rfc8040#section-4.8.3>`__

Preparation of data
~~~~~~~~~~~~~~~~~~~

Mounting NETCONF device that runs on NETCONF testtool:

.. code-block:: bash

  curl --location --request PUT 'http://127.0.0.1:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=testtool' \
  --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
  --header 'Content-Type: application/json' \
  --data-raw '{
      "node": [
          {
              "node-id": "testtool",
              "netconf-node-topology:host": "127.0.0.1",
              "netconf-node-topology:port": 36000,
              "netconf-node-topology:keepalive-delay": 100,
              "netconf-node-topology:tcp-only": false,
              "netconf-node-topology:username": "admin",
              "netconf-node-topology:password": "admin"
          }
      ]
  }'

Setting initial configuration on NETCONF device:

.. code-block:: bash

  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' \
  --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
  --header 'Content-Type: application/json' \
  --data-raw '{
      "root": {
          "simple-root": {
              "leaf-a": "asddhg",
              "leaf-b": "ffffff",
              "ll": [
                  "str1",
                  "str2",
                  "str3"
              ],
              "nested": {
                  "sample-x": true,
                  "sample-y": false
              }
          },
          "list-root": {
              "branch-ab": 5,
              "top-list": [
                  {
                      "key-1": "ka",
                      "key-2": "kb",
                      "next-data": {
                          "switch-1": [
                              null
                          ],
                          "switch-2": [
                              null
                          ]
                      },
                      "nested-list": [
                          {
                              "identifier": "f1",
                              "foo": 1
                          },
                          {
                              "identifier": "f2",
                              "foo": 10
                          },
                          {
                              "identifier": "f3",
                              "foo": 20
                          }
                      ]
                  },
                  {
                      "key-1": "kb",
                      "key-2": "ka",
                      "next-data": {
                          "switch-1": [
                              null
                          ]
                      },
                      "nested-list": [
                          {
                              "identifier": "e1",
                              "foo": 1
                          },
                          {
                              "identifier": "e2",
                              "foo": 2
                          },
                          {
                              "identifier": "e3",
                              "foo": 3
                          }
                      ]
                  },
                  {
                      "key-1": "kc",
                      "key-2": "ke",
                      "next-data": {
                          "switch-2": [
                              null
                          ]
                      },
                      "nested-list": [
                          {
                              "identifier": "q1",
                              "foo": 13
                          },
                          {
                              "identifier": "q2",
                              "foo": 14
                          },
                          {
                              "identifier": "q3",
                              "foo": 15
                          }
                      ]
                  }
              ]
          }
      }
  }'

Examples
--------

1. Reading whole leaf-list 'll' and leaf 'nested/sample-x' under 'simple-root' container.

RESTCONF request:

.. code-block:: bash

    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' \
    --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
    --header 'Cookie: JSESSIONID=node01h4w82eorc1k61866b71qjgj503.node0'

Generated NETCONF RPC request:

.. code-block:: xml

    <rpc message-id="m-18" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
        <get-config>
            <source>
                <running/>
            </source>
            <filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree">
                <root xmlns="urn:ietf:params:xml:ns:yang:test-model">
                    <simple-root>
                        <ll/>
                        <nested>
                            <sample-x/>
                        </nested>
                    </simple-root>
                </root>
            </filter>
        </get-config>
    </rpc>

.. note::

    Using fields query parameter it is also possible to read whole leaf-list or list without
    necessity to specify value / key predicate (without reading parent entity). Such scenario
    is not permitted in RFC-8040 paths alone - fields query parameter can be used as
    workaround for this case.

RESTCONF response:

.. code-block:: json

    {
        "test-module:simple-root": {
            "ll": [
                "str3",
                "str1",
                "str2"
            ],
            "nested": {
                "sample-x": true
            }
        }
    }

2. Reading all identifiers of 'nested-list' under all elements of 'top-list'.

RESTCONF request:

.. code-block:: bash

    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)' \
    --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
    --header 'Cookie: JSESSIONID=node01h4w82eorc1k61866b71qjgj503.node0'

Generated NETCONF RPC request:

.. code-block:: xml

    <rpc message-id="m-27" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
        <get-config>
            <source>
                <running/>
            </source>
            <filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree">
                <root xmlns="urn:ietf:params:xml:ns:yang:test-model">
                    <list-root>
                        <top-list>
                            <nested-list>
                                <identifier/>
                            </nested-list>
                            <key-1/>
                            <key-2/>
                        </top-list>
                    </list-root>
                </root>
            </filter>
        </get-config>
    </rpc>

.. note::

    NETCONF client automatically fetches values of list keys since they are required for correct
    deserialization of NETCONF response and at the end serialization of response to RESTCONF
    response (JSON/XML).

RESTCONF response:

.. code-block:: json

    {
        "test-module:list-root": {
            "top-list": [
                {
                    "key-1": "ka",
                    "key-2": "kb",
                    "nested-list": [
                        {
                            "identifier": "f3"
                        },
                        {
                            "identifier": "f2"
                        },
                        {
                            "identifier": "f1"
                        }
                    ]
                },
                {
                    "key-1": "kb",
                    "key-2": "ka",
                    "nested-list": [
                        {
                            "identifier": "e3"
                        },
                        {
                            "identifier": "e2"
                        },
                        {
                            "identifier": "e1"
                        }
                    ]
                },
                {
                    "key-1": "kc",
                    "key-2": "ke",
                    "nested-list": [
                        {
                            "identifier": "q3"
                        },
                        {
                            "identifier": "q2"
                        },
                        {
                            "identifier": "q1"
                        }
                    ]
                }
            ]
        }
    }

3. Reading value of leaf 'branch-ab' and all values of leaves 'switch-1' that are placed
   under 'top-list' list elements.

RESTCONF request:

.. code-block:: bash

    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' \
    --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
    --header 'Cookie: JSESSIONID=node01jx6o5thwae9t1ft7c2zau5zbz4.node0'

Generated NETCONF RPC request:

.. code-block:: xml

    <rpc message-id="m-42" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
        <get-config>
            <source>
                <running/>
            </source>
            <filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree">
                <root xmlns="urn:ietf:params:xml:ns:yang:test-model">
                    <list-root>
                        <branch-ab/>
                        <top-list>
                            <next-data>
                                <switch-1/>
                            </next-data>
                            <key-1/>
                            <key-2/>
                        </top-list>
                    </list-root>
                </root>
            </filter>
        </get-config>
    </rpc>

RESTCONF response:

.. code-block:: json

    {
        "test-module:list-root": {
            "branch-ab": 5,
            "top-list": [
                {
                    "key-1": "ka",
                    "key-2": "kb",
                    "next-data": {
                        "switch-1": [
                            null
                        ]
                    }
                },
                {
                    "key-1": "kb",
                    "key-2": "ka",
                    "next-data": {
                        "switch-1": [
                            null
                        ]
                    }
                },
                {
                    "key-1": "kc",
                    "key-2": "ke"
                }
            ]
        }
    }