[riot-notifications] [RIOT-OS/RIOT] doc/memos: RDM Runtime Configuration Architecture (#10622)

Leandro Lanzieri notifications at github.com
Tue Jan 29 19:17:31 CET 2019

leandrolanzieri commented on this pull request.

> +<img src="./files/rdm-draft-alamos-lanzieri-runtime-configuration-architecture/registry-storage.svg" />
+# 4. Configuration managers
+Configuration managers are modules that allow a RIOT node to be
+configured from one or more communication interfaces. Examples of these
+communication interfaces could be UART, SPI or higher layers like PPP, IPv6,
+UDP, CoAP, etc.
+These are some examples of Configuration Managers:
+- [OMA LWM2M](https://www.omaspecworks.org/what-is-oma-specworks/iot/lightweight-m2m-lwm2m/)
+- [Newt Manager](https://mynewt.apache.org/master/os/modules/devmgmt/newtmgr.html)
+  via interfaces like NFC, BLE, Serial, etc.
+- A UART shell with special commands for interacting with configurations (CLI)
+A Configuration Manager may interact with the RIOT Registry to access Runtime

> Is this really a "MAY" here? According to the first architecture graph, the Configuration Manager accesses the RIOT Registry.

You are right, the Configuration Managers should only access the parameters via the Registry.

> It would be IMO helpful to clarify
> * which is the interface or surface the Configuration Manager sees and interacts with
> * which (southbound) API(s) does it need to implement towards RIOT

Each implemented Configuration Manager will interact directly with the RIOT Registry API.

Regarding the API of the Configuration Managers towards RIOT, I'm not sure if we extract a common interface it at the moment, as all of them are really different  (IMO Configuration Managers could even require an RDM on their own). We can though define some responsibilities they have (e.g. access control mechanisms, enable/disable of interfaces). Maybe that can be rephrased in the document.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190129/54115b9c/attachment-0001.html>

More information about the notifications mailing list