Add minpoll/maxpoll for ntp client

[mattiaswal]

Also make the local timeserver more robust, changing from busybox ntpd to chronyd.
This for now only effects one test: client_stratum_selection

Description

Checklist

Tick relevant boxes, this PR is-a or has-a:

• Bugfix
  • Regression tests
  • ChangeLog updates (for next release)
• Feature
  • YANG model change => revision updated?
  • Regression tests added?
  • ChangeLog updates (for next release)
  • Documentation added?
• Test changes
  • Checked in changed Readme.adoc (make test-spec)
  • Added new test to group Readme.adoc and yaml file
• Code style update (formatting, renaming)
• Refactoring (please detail in commit messages)
• Build related changes
• Documentation content changes
  • ChangeLog updated (for major changes)
• Other (please describe):

[troglobit]

Simply adopting the Chrony naming somehow feels wrong. Can't put my finger on it but I was sort of expecting a CLI syntax more like:

set poll min A max B

We also need to gate these settings to client mode with a must or when expression.

[mattiaswal]

Simply adopting the Chrony naming somehow feels wrong. Can't put my finger on it but I was sort of expecting a CLI syntax more like:

set poll min A max B

We also need to gate these settings to client mode with a must or when expression.

Simply adopting the Chrony naming somehow feels wrong. Can't put my finger on it but I was sort of expecting a CLI syntax more like:

set poll min A max B

We also need to gate these settings to client mode with a must or when expression.

It is already limited to client since it is in ietf-system.

[mattiaswal]

Simply adopting the Chrony naming somehow feels wrong. Can't put my finger on it but I was sort of expecting a CLI syntax more like:

set poll min A max B

We also need to gate these settings to client mode with a must or when expression.

And changing from maxpoll/minpoll diverge from how ietf-ntp implements it:

 grouping common-attributes {
    description
      "NTP common attributes for configuration";
    leaf minpoll {
      type log2seconds;
      default "6";
      description
        "The minimum poll interval used in this association";
      reference
        "RFC 5905: Network Time Protocol Version 4: Protocol and
         Algorithms Specification, Section 7.2";
    }
    leaf maxpoll {
      type log2seconds;
      default "10";
      description
        "The maximum poll interval used in this association";
      reference
        "RFC 5905: Network Time Protocol Version 4: Protocol and
         Algorithms Specification, Section 7.2";
    }
    leaf port {
      if-feature "ntp-port";
      type inet:port-number {
        range "123 | 1024..max";
      }
      default "123";
      description

[troglobit]

Ah, ietf-system, I missed that tiny detail, thanks! And if the standard model has minpoll/maxpoll that's fine too, always better to optimize for consistency over perfection.