diff options
| -rw-r--r-- | doc/roadmap.rst | 31 |
1 files changed, 20 insertions, 11 deletions
diff --git a/doc/roadmap.rst b/doc/roadmap.rst index d78f36d..0a752ed 100644 --- a/doc/roadmap.rst +++ b/doc/roadmap.rst @@ -38,6 +38,10 @@ a specific YANG module, it can just be removed from the list to import. Outstanding TBDs ```````````````` +* None. + +Resolved TBDs +````````````` * The ``modules-state`` requires a ``module-set-id`` which represents the unique combination of YANG modules present and loaded in a NETCONF server. We have freedom to implement this however we like. One thought is to take @@ -46,9 +50,11 @@ Outstanding TBDs but this would also mean that tooling that caches modules would pull in all modules on every server restart. -Resolved TBDs -````````````` -* None. + **Resolution**: We went with sha256 of a comma-separated list of Python + module names. This is expected to be the cleanest way to do this; it allows + the implementation to provide the same ``module-set-id`` when modules stay + the same, but also changes ``module-set-id`` if a new module replaces an + existing one for the same namespace (which may require data to be reloaded). @@ -104,9 +110,6 @@ The system module allows basic administration of system configuration. Outstanding TBDs ```````````````` -* Do we support NTP? If so, which implementation? Prefer chrony because it's - available on Adélie (openntpd isn't available due to ppc/be issues) - * Where do we store the ``contact`` and ``location`` node information? * When the admin tries to set ``timezone-utf-offset``, do we make a custom @@ -128,7 +131,13 @@ Outstanding TBDs Resolved TBDs ````````````` -* None. +* Do we support NTP? If so, which implementation? Prefer chrony because it's + available on Adélie (openntpd isn't available due to ppc/be issues) + + **Resolution**: Yes, NTP support is desireable. THe implementation is + ``ntpsec``. It has been packaged and tested for Adélie/ppc64, so it appears + portable. + @@ -239,7 +248,7 @@ Resolved TBDs ========== [ ] Software module ------------------- +------------------- * [ ] Define model @@ -310,9 +319,9 @@ Outstanding TBDs ```````````````` * How do we determine when a RIB entry was modified? +Resolved TBDs +````````````` * Per kernel docs, the Linux kernel supports 242 user-defined RIBs in addition to default and main. Do we want to expose that (feature ``multiple-ribs``)? -Resolved TBDs -````````````` -* None. + **Resolution**: Yes, we expose feature ``multiple-ribs``. |