Bug 42171 - Make ntp peer configurable via UCR
Make ntp peer configurable via UCR
Status: NEW
Product: UCS
Classification: Unclassified
Component: NTP
UCS 4.4
Other Linux
: P5 enhancement with 2 votes (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks: 51498
  Show dependency treegraph
 
Reported: 2016-08-29 16:58 CEST by Michael Grandjean
Modified: 2020-07-03 20:23 CEST (History)
6 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2016-08-29 16:58:35 CEST
It should be possible to specify NTP peers via UCR. Configuring peers is often a compliance requirement to achieve a setup similiar to this:


   1a  1b     1c  1d     1e  1f      outside
... \ / ...... \ / ...... \ / ..............
     2a ---p--- 2b ---p--- 2c        inside


Where: 1 = stratum-1, 2 = stratum-2, p = peer
Comment 1 Philipp Hahn univentionstaff 2016-08-30 08:48:30 CEST
see `man 5 ntp.conf` -> "peer" in addition to "server" to allow bi-directional sync between servers of same stratum inside a corporate network for redundancy.

see <http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm#AEN3101> for a description of the idea.
Comment 2 Florian Best univentionstaff 2017-06-28 14:52:44 CEST
There is a Customer ID set so I set the flag "Enterprise Customer affected".