Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

amazon-image: use NTP provided by the hypervisor #32188

Merged
merged 1 commit into from Nov 30, 2017
Merged

Conversation

copumpkin
Copy link
Member

@copumpkin copumpkin commented Nov 30, 2017

See http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html for more information.

Fixes #32187

I don't feel strongly on whether to backport to 17.09. @globin @fpletz?

Motivation for this change

This allows our AWS AMI to work seamlessly with correct time even when started in a VPC with no internet connectivity.

@edolstra
Copy link
Member

Hm, I hit merge before seeing #32187 (comment). So maybe we need to revert this.

@copumpkin
Copy link
Member Author

If I just list the standard pool addresses after the 169.254 address, will it just fall back to those if the first is unreachable?

@copumpkin copumpkin deleted the copumpkin-aws-ntp branch November 30, 2017 14:00
@joelthompson
Copy link
Contributor

If I just list the standard pool addresses after the 169.254 address, will it just fall back to those if the first is unreachable?

It'll try to reach out to all servers listed regardless and use info from all reachable servers to pick the best time. Worst case, it would add noise to servers that can't reach one or the other time source.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants