Ansible managed NTP config
Bug #1413018 reported by
Kevin Stevens
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Won't Fix
|
Wishlist
|
Major Hayden |
Bug Description
This is a feature request.
Sometimes our servers' times will drift apart enough to cause Neutron agents/Nova services to flap up and down. It would probably be a good idea to have the entire environment agree on time similar to the guidelines presented in the Openstack deployment guide.
Proposal: It would be nice if the Infra nodes had a configurable list of hosts to use as NTP servers, defaulting to the pool.ntp.org servers. By default, the infra nodes would be peers of each other. Any physical host *not* Infra would be clients of the Infra nodes.
Changed in openstack-ansible: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in openstack-ansible: | |
milestone: | none → next |
Changed in openstack-ansible: | |
milestone: | next → none |
Changed in openstack-ansible: | |
milestone: | none → 11.1.1 |
Changed in openstack-ansible: | |
status: | Triaged → In Progress |
To post a comment you must log in.
I have suffered from this as well when trying to correlate log files for containers hosted on different infra nodes.