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

José Alamos notifications at github.com
Thu Jan 10 14:44:44 CET 2019


jia200x commented on this pull request.



> +
+A runtime configuration system is in charge of providing a mechanism to set and
+get the values of configuration parameters that are used during the execution
+of the firmware, as well as a way to persist these values. Runtime
+configurations are deployment-specific and can be changed on a per node basis.
+Appropriate management tools could also enable the configuration of node
+groups.
+
+Examples of runtime configurations are:
+- Transmission duty cycles
+- Sensor thresholds
+- Security credentials
+- System state variables
+
+These parameters might have constraints, like a specific order to be applied
+(due to interdependencies) or value boundaries.

> Are non-static configuration parameters possible/likely?

It's always possible, but I think defining how the configurations should be implemented is out of the scope of this document. We don't have any mechanism in RIOT to protect modules (we have no users, groups, etc). So, it will be always possible to mess with other components (not only in the RCS scope)



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/10622#discussion_r246762252
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190110/ce87cf14/attachment-0001.html>


More information about the notifications mailing list