[Yahoo-eng-team] [Bug 1711466] Re: No way to configure timesyncd specifically

2023-05-05 Thread James Falcon
cc_ntp.py allows for configuring timesyncd and provides defaults for
each distro. This was addressed in https://bugs.launchpad.net/cloud-
init/+bug/1749722

** Changed in: cloud-init
   Status: Confirmed => Fix Released

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1711466

Title:
  No way to configure timesyncd specifically

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu (starting from Xenial), uses timesyncd by default as a NTP
  client.

  When configuring NTP, instead of configuring Ubuntu's default NTP
  client, it installs and configures 'ntp' daemon. In Ubuntu Core,
  however, it configures 'timesyncd' (obviously) because Ubuntu Core
  doesn't support 'ntp'.

  First, it would be nice to have consistency between both Ubuntu and
  Ubuntu Core and configure timesyncd (as it is the default anyway).

  Second, lets imagine the use case scenario where a image is configured
  with NTP and you have an NTP snap or a snap that also needs to run
  NTP.

  In Ubuntu core this works nicely because the OS' uses timesyncd as
  time source while the snap would provided NTP services from the snap
  itself to its client.

  However, in Ubuntu this doesn't work nicely because 'ntp' is running
  in the host as an NTP client, however, the snap having NTP inside
  needs to provide NTP services, but it won't be able to provided that
  the host OS *also* has 'ntp' installed.

  As such, it would be nice to either keep consistency (and configure
  timesyncd for both Ubuntu Core and Ubuntu), or have the ability to
  specifically configure 'timesyncd' instead of 'ntpd'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1711466/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1711466] Re: No way to configure timesyncd specifically

2017-09-26 Thread Scott Moser
** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init
   Status: New => Confirmed

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1711466

Title:
  No way to configure timesyncd specifically

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu (starting from Xenial), uses timesyncd by default as a NTP
  client.

  When configuring NTP, instead of configuring Ubuntu's default NTP
  client, it installs and configures 'ntp' daemon. In Ubuntu Core,
  however, it configures 'timesyncd' (obviously) because Ubuntu Core
  doesn't support 'ntp'.

  First, it would be nice to have consistency between both Ubuntu and
  Ubuntu Core and configure timesyncd (as it is the default anyway).

  Second, lets imagine the use case scenario where a image is configured
  with NTP and you have an NTP snap or a snap that also needs to run
  NTP.

  In Ubuntu core this works nicely because the OS' uses timesyncd as
  time source while the snap would provided NTP services from the snap
  itself to its client.

  However, in Ubuntu this doesn't work nicely because 'ntp' is running
  in the host as an NTP client, however, the snap having NTP inside
  needs to provide NTP services, but it won't be able to provided that
  the host OS *also* has 'ntp' installed.

  As such, it would be nice to either keep consistency (and configure
  timesyncd for both Ubuntu Core and Ubuntu), or have the ability to
  specifically configure 'timesyncd' instead of 'ntpd'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1711466/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp