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

José Alamos notifications at github.com
Wed Jan 9 11:54:05 CET 2019


jia200x commented on this pull request.



> +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.
+
+The main advantages of having such a system are:
+- Easy to apply per-node configuration during deployment
+- No need to implement a special mechanism for per-node configurations during
+  firmware updates (only in the case of migration)

Not exactly what we intended to show. This was more in the direction e.g "move all configuration parameters from EEPROM to a SD Card". Anyway, we should state that configuration parameters can persist between firmware updates

-- 
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_r246338657
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190109/91440c30/attachment-0001.html>


More information about the notifications mailing list