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

Use Amazon Time Sync Service on AWS as default #2275

Closed
johanneswuerbach opened this Issue Nov 30, 2017 · 6 comments

Comments

Projects
None yet
5 participants
@johanneswuerbach

johanneswuerbach commented Nov 30, 2017

In line with the advice in https://coreos.com/os/docs/latest/configuring-date-and-timezone.html#recommended-ntp-sources

use your cloud provider's NTP source

I would be great if CoreOS on AWS would use the Amazon Time Sync Service https://aws.amazon.com/about-aws/whats-new/2017/11/introducing-the-amazon-time-sync-service by default as it requires no outgoing connections to the public internet and smooths leap seconds.

When using Amazon Linux, this is already done by default http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html#configure-amazon-time-service, but currently requires additional steps on CoreOS.

@crawford

This comment has been minimized.

Show comment
Hide comment
@crawford

crawford Nov 30, 2017

Member

@johanneswuerbach Do you know if AWS advertises these time servers via DHCP? If so, Container Linux should pick them up by default. If not, we'd have to document how the VPC's DHCP options can be modified.

Member

crawford commented Nov 30, 2017

@johanneswuerbach Do you know if AWS advertises these time servers via DHCP? If so, Container Linux should pick them up by default. If not, we'd have to document how the VPC's DHCP options can be modified.

@johanneswuerbach

This comment has been minimized.

Show comment
Hide comment
@johanneswuerbach

johanneswuerbach Dec 1, 2017

Not yet as far as I can tell, nodes started after the announcement still point to ntp.org

Nov 30 14:29:25 localhost systemd-timesyncd[701]: Network configuration changed, trying to establish connection.
Nov 30 14:29:39 ip-xxx.ec2.internal systemd-timesyncd[701]: Network configuration changed, trying to establish connection.
Nov 30 14:29:40 ip-xxx.ec2.internal systemd-timesyncd[701]: Synchronized to time server 162.210.111.4:123 (2.coreos.pool.ntp.org).

So I guess you would need to override ntp-servers http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_DHCP_Options.html manually for now or via https://coreos.com/os/docs/latest/configuring-date-and-timezone.html#changing-ntp-time-sources

johanneswuerbach commented Dec 1, 2017

Not yet as far as I can tell, nodes started after the announcement still point to ntp.org

Nov 30 14:29:25 localhost systemd-timesyncd[701]: Network configuration changed, trying to establish connection.
Nov 30 14:29:39 ip-xxx.ec2.internal systemd-timesyncd[701]: Network configuration changed, trying to establish connection.
Nov 30 14:29:40 ip-xxx.ec2.internal systemd-timesyncd[701]: Synchronized to time server 162.210.111.4:123 (2.coreos.pool.ntp.org).

So I guess you would need to override ntp-servers http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_DHCP_Options.html manually for now or via https://coreos.com/os/docs/latest/configuring-date-and-timezone.html#changing-ntp-time-sources

@Sodki

This comment has been minimized.

Show comment
Hide comment
@Sodki

Sodki Feb 7, 2018

Also please note the following:

Support for the Amazon Time Sync Service on C5 and M5 instances is coming soon.

Source: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html#configure-amazon-time-service

I would wait until all instances are supported before any attempts of making it the default choice.

Sodki commented Feb 7, 2018

Also please note the following:

Support for the Amazon Time Sync Service on C5 and M5 instances is coming soon.

Source: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html#configure-amazon-time-service

I would wait until all instances are supported before any attempts of making it the default choice.

@mindw

This comment has been minimized.

Show comment
Hide comment
@mindw

mindw Mar 21, 2018

@Sodki the above comment is no longer present in the above link.

mindw commented Mar 21, 2018

@Sodki the above comment is no longer present in the above link.

@Sodki

This comment has been minimized.

Show comment
Hide comment
@Sodki

Sodki Mar 21, 2018

@mindw Correct, I've tested with an M5 instance and it's working.

Sodki commented Mar 21, 2018

@mindw Correct, I've tested with an M5 instance and it's working.

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Sep 26, 2018

Member

Thank you for reporting this issue. Unfortunately, we don't think we'll end up addressing it in Container Linux.

We're now working on Fedora CoreOS, the successor to Container Linux, and we expect most major development to occur there instead. Meanwhile, Container Linux will be fully maintained into 2020 but won't see many new features. We appreciate your taking the time to report this issue and we're sorry that we won't be able to address it.

Member

bgilbert commented Sep 26, 2018

Thank you for reporting this issue. Unfortunately, we don't think we'll end up addressing it in Container Linux.

We're now working on Fedora CoreOS, the successor to Container Linux, and we expect most major development to occur there instead. Meanwhile, Container Linux will be fully maintained into 2020 but won't see many new features. We appreciate your taking the time to report this issue and we're sorry that we won't be able to address it.

@bgilbert bgilbert closed this Sep 26, 2018

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