A role to manage chrony
Role Variables
Name |
Default Value |
Description |
|---|---|---|
chrony_debug |
False |
Enable debug option in chrony |
chrony_role_action |
all |
Ansible action when including the role. Should be one of: [all|install|config|upgrade|online] |
chrony_package_name |
chrony |
chrony system package name |
chrony_service_name |
chronyd |
chrony system service name |
chrony_manage_service |
True |
Flag used to specific if the ansible role should manage the service |
chrony_manage_package |
True |
Flag used to specific if the ansible role should manage the package |
chrony_service_state |
started |
Default service state to configure (started|stopped) |
chrony_config_file_location |
/etc/chrony.conf |
Chrony configuration file location. |
chrony_driftfile_path |
/var/lib/chrony/drift |
Chrony drift file location |
chrony_logdir_path |
/var/log/chrony |
Chrony log directory location |
chrony_ntp_servers |
[] |
List of NTP servers. This can be a list of hashes for advanced configuration. If using the hash format, a server_name and server_settings key should be populated with the appropriate data. If this is a list of hostnames, the chrony_global_server_settings will be appended to the configuration. |
chrony_global_server_settings |
<none> |
Default setting to apply to the servers configuration |
chrony_ntp_pools |
[] |
List of NTP pools. This can be a list of hashes for advanced configuration. If using the hash format, a pool_name and pool_settings key should be populated with the appropriate data. If this is a list of hostnames, the chrony_global_pool_settings will be appended to the configuration. |
chrony_global_pool_settings |
<none> |
Default setting to apply to the pools configuration |
chrony_ntp_peers |
[] |
List of NTP peers. This can be a list of hashes for advanced configuration. If using the hash format, a peer_name and peer_settings key should be populated with the appropriate data. If this is a list of hostnames, the chrony_global_peer_settings will be appended to the configuration. |
chrony_global_peer_settings |
<none> |
Default setting to apply to the peers configuration |
chrony_bind_addresses |
[‘127.0.0.1’, ‘::1’] |
List of addresses to bind to to listen for command packets |
chrony_acl_rules |
[] |
List of specific allow/deny commands for the configuration file |
chrony_rtc_settings |
[‘rtcsync’] |
List of specific real time lock settings |
chrony_makestep |
1.0 3 |
The chrony makestep configuration |
chrony_extra_options |
[] |
A list of extra option strings that is added to the end of the configuration file. This list is joined with new lines. |
Requirements
ansible >= 2.4
python >= 2.6
Dependencies
None
Example Playbooks
- hosts: localhost
become: true
roles:
- chrony
License
Apache 2.0
Metadata
Release files for ansible-role-chrony 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ansible-role-chrony-1.3.0.tar.gz | 12.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansible_role_chrony-1.3.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 29.4 kB
Release files / ansible-role-chrony-1.3.0.tar.gz
| Download URL | ansible-role-chrony-1.3.0.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8fdc6b9d971fb1057d5051313d3fb5fd6f4790ea5f607594551600ea180dad2e
|
|
BLAKE2b-256 checksum How to use checksums |
628a36917504bdc9f5148f9e436d44c06341fb0bc439302236abc0c16115e7fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Release files / ansible_role_chrony-1.3.0-py2.py3-none-any.whl
| Download URL | ansible_role_chrony-1.3.0-py2.py3-none-any.whl |
|---|---|
| Size | 17.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
865f0f34689b10497f7cd29c603dd6cd027f169c9a73dd1c8fe0b8b08cd513c7
|
|
BLAKE2b-256 checksum How to use checksums |
d318dfb80cd34628730b80a7fa0f4d7e4b21d4fdd1c32490468201d1e9e29cb7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Security for ansible-role-chrony 1.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.