Ntp
- NTP charm developers
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 50 | 29 Aug 2022 | |
latest/stable | 49 | 15 Aug 2022 | |
latest/stable | 47 | 09 Feb 2022 | |
latest/stable | 37 | 11 Nov 2020 | |
latest/stable | 27 | 11 Nov 2020 | |
latest/candidate | 50 | 29 Aug 2022 | |
latest/candidate | 45 | 09 Feb 2022 | |
latest/candidate | 34 | 11 Nov 2020 | |
latest/candidate | 28 | 11 Nov 2020 |
juju deploy ntp
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
auto_peers | boolean
DEPRECATED - please DO NOT use if you have more than approximately 20 units in this service. Automatically select the most appropriate units in the service to be a service stratum connecting with upstream NTP servers, and use those units as time sources for the remaining units.
-
auto_peers_upstream | int
Default: 6
DEPRECATED - please DO NOT use if you have more than approximately 20 units in this service. How many units should attempt to connect with upstream NTP servers?
-
max_check_attempts | string
The maxiumum number of attempts to check the ntpmon service before switching an alert to HARD status rather than SOFT. Default for Nagios is 4, if this is set, the default will be overwritten for the ntpmon check only.
-
nagios_context | string
Default: juju
Used by the nrpe subordinate charms. A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-myservice-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.
-
nagios_ntpmon_checks | string
Default: offset peers reach sync proc vars
A space-separated list of nagios ntpmon checks to enable. Default is to enable all checks except trace; leave empty for no checks.
-
nagios_servicegroups | string
A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup
-
ntp_package | string
If set to "ntp" the ntp package will be installed and configured, or if set to "chrony" the chrony package will be installed and configured. If unspecified the appropriate package will be selected based on the operating system. Please note that the use of ntp on Ubuntu bionic or later is not recommended as it does not receive security updates.
-
orphan_stratum | int
The stratum at which NTP must lose connectivity to before it considers itself orphaned, and starts determining the reference time with local peers. A typical value is 6, which will enable orphaned operation when there are no stratum 6 servers or servers of a higher stratum available, which is two strata below most Internet NTP hosts. Set to 0 to disable orphan mode entirely. You must enable at least one peer in order to use orphan mode, but four or more is recommended for best results.
-
peers | string
Space-separated list of NTP servers to use as peers. Under ntpd, peers are allowed to query the local NTP server via ntpq.
-
pools | string
Default: 0.ubuntu.pool.ntp.org 1.ubuntu.pool.ntp.org 2.ubuntu.pool.ntp.org 3.ubuntu.pool.ntp.org ntp.ubuntu.com
Space-separated list of NTP servers to use as pool sources. These are recommended over normal sources for their self-healing capabilities. Leave empty to disable pool sources.
-
restrict_allow | string
Space-separated list of CIDR subnets for which we will allow queries via chrony.conf's "allow x.x.x.x/x" directive. Default is a bare "allow" to accept traffic from all networks.
-
restrict_deny | string
Space-separated list of subnets for which we will deny queries via chrony.conf's "deny" directive. Default is no "deny" directive.
-
source | string
Space-separated list of NTP servers to use as time sources.
-
unlimited_clients | string
Comma-separated list of IPs or networks for which requests will not be rate-limited. Example value "1.2.3.4,16.0.0.0 mask 255.0.0.0" This is implemented for ntpd only - chrony doesn't do rate limiting by default.
-
use_iburst | boolean
Default: True
Use iburst for all peers/sources, not just those received via the master relation.
-
verify_ntp_servers | boolean
If configured to True, charm will automatically try to verify that given NTP servers are accessible and raise an error, if they aren't.