Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
K
Kolla Ansible
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Very Demiurge Very Mindful
Kolla Ansible
Commits
285d2db3
Commit
285d2db3
authored
9 years ago
by
Jenkins
Committed by
Gerrit Code Review
9 years ago
Browse files
Options
Downloads
Plain Diff
Merge "Add additional ntp information around ceph"
parents
74d8c2d8
fdb010e5
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/quickstart.rst
+16
-9
16 additions, 9 deletions
doc/quickstart.rst
with
16 additions
and
9 deletions
doc/quickstart.rst
+
16
−
9
View file @
285d2db3
...
@@ -126,13 +126,17 @@ To install these clients use:
...
@@ -126,13 +126,17 @@ To install these clients use:
pip install -U python-openstackclient
pip install -U python-openstackclient
OpenStack uses healthcheck timers which run off wall-clock time rather then
OpenStack, RabbitMQ, and Ceph require all hosts to have matching times to ensure
starting a timer and expiring the timer, encoding the expiration in the message
proper message delivery. In the case of Ceph, it will complain if the hosts
contents. In some cases, this timer interval can be on the order of 60
differ by more than 0.05 seconds. Some OpenStack services have timers as low as
seconds. For OpenStack to operate correctly with these tight health-check
2 seconds by default. For these reasons it is highly recommended to setup an NTP
timer intervals, the Kolla community highly recommends running the ntpd
service of some kind. While `ntpd` will achieve more accurate time for the
service on all deployment targets. To install, start, and enable ntp
deployment if the NTP servers are running in the local deployment environment,
execute the following:
`chrony <http://chrony.tuxfamily.org>`_ is more accurate when syncing the time
across a WAN connection. When running Ceph it is recommended to setup `ntpd` to
sync time locally due to the tight time constraints.
To install, start, and enable ntp on CentOS execute the following:
::
::
...
@@ -141,8 +145,11 @@ execute the following:
...
@@ -141,8 +145,11 @@ execute the following:
systemctl enable ntpd
systemctl enable ntpd
systemctl start ntpd
systemctl start ntpd
# Ubuntu
To install and start on Debian based systems execute the following:
sudo apt-get install ntp
::
apt-get install ntp
Libvirt is started by default on many operating systems. Please disable libvirt
Libvirt is started by default on many operating systems. Please disable libvirt
on any machines that will be deployment targets. Only one copy of libvirt may
on any machines that will be deployment targets. Only one copy of libvirt may
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment