commit 4b98876ad3da3d45af204a4d0bca06c59d8231b2
author Tomáš Pecka <tomas.pecka@fit.cvut.cz> Thu Dec 03 08:38:49 2020 +0100
committer Tomáš Pecka <tomas.pecka@fit.cvut.cz> Thu Dec 17 12:19:24 2020 +0100
tree 0fdbf0f41a5f26fbed76e1b82ccc5cb658d0d8f2
parent d03044fca2bcdee1b72ee1823cd82f70cf3a3529

HardwareState: Cooperation and compatibility with cla-sysrepo

IETF Hardware model exports only some components to Sysrepo. Some of
them are handled by cla-sysrepo daemon. In order for things to cooperate
smoothly, the following must be taken in mind:

1. Sysrepo does not allow two subscriptions to the same XPath. Velia
   therefore subscribes to "/ietf-hardware-state:hardware/*", which is
   a different path (but effectively the same). This is a workaround for
   Sysrepo described in [1].

2. ietf-hardware-state stores all the components in a tree (which is
   represented by a list with links to parents). Sysrepo does not (as of
   now) check whether the parent is present in the tree but this can of
   course change.
   cla-sysrepo, which starts first, handles some of the components whose
   parent is the topmost element. Therefore it must also handle the
   topmost element. It indeed initialises it (it creates the component
   and sets 'name', 'model' and 'class' leafs in the component -- see
   ietf-hardware-state YANG model [2]).
   However, velia will handle setting of some other properties (like
   reading and setting of serial numbers, manufacturer,...).

[1] https://github.com/sysrepo/sysrepo/issues/2191
[2] https://tools.ietf.org/html/rfc8348#appendix-A

Change-Id: Ia790a07a830334f8fd541bae9d770faf930a40fe