From c5c565a4f5c10104844e0dbf8419a73622103457 Mon Sep 17 00:00:00 2001 From: "A. Wilcox" Date: Wed, 16 Sep 2020 15:46:18 -0500 Subject: Update roadmap with current progress and TBD resos --- doc/roadmap.rst | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/doc/roadmap.rst b/doc/roadmap.rst index 7f9ce7e..b011ab8 100644 --- a/doc/roadmap.rst +++ b/doc/roadmap.rst @@ -70,9 +70,9 @@ This feature will require in-depth discussion. * [/] Configuration nodes - * [/] Retrieve and set admin contact and system location information. + * [X] Retrieve and set admin contact and system location information. - * [/] Retrieve and set hostname. + * [X] Retrieve and set hostname. * [ ] Clock: @@ -80,11 +80,11 @@ This feature will require in-depth discussion. * [ ] Determine ``timezone-utc-offset`` from current localtime. - * [/] DNS configuration + * [X] DNS configuration - * [ ] Local user administration: + * [ ] NTP configuration - * [ ] Password support (if in spec). + * [ ] Local user administration: * [ ] SSH key administration (``$HOME/.ssh/authorized_keys``). @@ -113,12 +113,8 @@ Outstanding TBDs * When the admin tries to set ``timezone-utc-offset``, do we make a custom zoneinfo file or do we try to match? -* How do we support ``name`` of DNS resolvers? It is mandatory. - * Should there be a group for NETCONF-allowed users? -* Do we support RADIUS? - Resolved TBDs ````````````` * Do we support NTP? If so, which implementation? Prefer chrony because it's @@ -153,6 +149,15 @@ Resolved TBDs **Resolution**: Not applicable; we do not support password-based authentication. +* How do we support ``name`` of DNS resolvers? It is mandatory. + + **Resolution**: Well-defined comment above each nameserver line. Default + to 'Resolver' if not specified. + +* Do we support RADIUS? + + **Resolution**: No. + [ ] Interfaces module -- cgit v1.2.3-60-g2f50