| 2018-01-18 13:51:25 |
Christian Ehrhardt |
bug |
|
|
added bug |
| 2018-01-18 13:56:10 |
Christian Ehrhardt |
description |
Note: I know it is the template so far, but after the discussions at the sprint I want something we can start working on together.
Background: after evaluation it was considered easier to maintain to provide a good and secure ntp experience as well as some people asking me if it could be preferred.
--- MIR ---
TBD
Thoroughly go through UbuntuMainInclusionRequirements, check that the package meets all the points there. Write down issues that violate the requirements. If this package has nontrivial problems, it is not eligible for main inclusion, and needs to be fixed first.
File a bug report about the package, titled "[MIR] sourcepackagename". Include the rationale and description of the violations of UbuntuMainInclusionRequirements, and a confirmation that you checked the requirements carefully.
Subscribe ubuntu-mir to the bug report (do not assign it to anyone), so that it appears in the MIR bug list.
The MIR team reviews the reports, and sets acceptable ones to In Progress or Fix Committed. They might also delegate portions of the review to other teams, assign it to them, and set it to Incomplete; common cases are getting a thorough security review from the security team (please see SecurityTeam/Auditing for details on requesting an audit), or getting a sign-off from particular team leads about maintenance commitments.
Add the package to a seed, or as a (build-)dependency of a package in main. The package will not be moved to main automatically, but will show up in the component-mismatches list, or if the dependency is only in proposed, the component-mismatches-proposed list.
Archive administrators will review the component-mismatches output, and for each package waiting to move into main, look for a corresponding bug.
The submitter should then take responsibility for adding the package to the seeds as per SeedManagement or adding a dependency to it.
The archive administrators will promote approved packages to main if some other package or the seeds want it (see component-mismatches output).
--- Affected Packages ---
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time, so that should be ok) |
Note: I know it is the template so far, but after the discussions at the sprint I want something we can start working on together.
Background: after evaluation it was considered easier to maintain to provide a good and secure ntp experience as well as some people asking me if it could be preferred.
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale: NTP in general is needed quite a lot, but we want to exchange ntpd which is the current implementation in main with chrony for 18.04.
3. Security: In fact the request came in by security Team, so I guess I call this section done
-- EVERYTHING BELOW TBD FOR NOW --
Quality assurance:
After installing the package it must be possible to make it working with a reasonable effort of configuration and documentation reading.
The package must not ask debconf questions higher than medium if it is going to be installed by default. The debconf questions must have reasonable defaults.
There are no long-term outstanding bugs which affect the usability of the program to a major degree. To support a package, we must be reasonably convinced that upstream supports and cares for the package.
The status of important bugs in Debian's, Ubuntu's, and upstream's bug tracking systems must be evaluated. Important bugs must be pointed out and discussed in the MIR report.
The package is maintained well in Debian/Ubuntu (check out the Debian PTS)
The package should not deal with exotic hardware which we cannot support.
If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build.
The package uses a debian/watch file whenever possible. In cases where this is not possible (e. g. native packages), the package should either provide a debian/README.source file or a debian/watch file (with comments only) providing clear instructions on how to generate the source tar file.
The package should not rely on obsolete or about to be demoted packages. That currently includes package dependencies on Python2 (without providing Python3 packages), and packages depending on GTK2.
UI standards: (generally only for user-facing applications)
End-user applications must be internationalized (translatable), using the standard intltool/gettext build and runtime system and produce a proper PO template during build.
End-user applications must ship a standard conformant desktop file.
Dependencies:
All binary dependencies (including Recommends:) must be satisfiable in main (i. e. the preferred alternative must be in main). If not, these dependencies need a separate MIR report (this can be a separate bug or another task on the main MIR bug)
Standards compliance: The package should meet the FHS and Debian Policy standards. Major violations should be documented and justified. Also, the source packaging should be reasonably easy to understand and maintain.
Maintenance: The package must have an acceptable level of maintenance corresponding to its complexity:
All packages must have a designated "owning" team, regardless of complexity, which is set as a package bug contact.
Simple packages (e.g. language bindings, simple Perl modules, small command-line programs, etc.) might not need very much maintenance effort, and if they are maintained well in Debian we can just keep them synced
More complex packages will usually need a developer or team of developers paying attention to their bugs, whether that be in Ubuntu or elsewhere (often Debian). Packages that deliver major new headline features in Ubuntu need to have commitment from Ubuntu developers willing to spend substantial time on them.
Background information:
The package descriptions should explain the general purpose and context of the package. Additional explanations/justifications should be done in the MIR report.
If the package was renamed recently, or has a different upstream name, this needs to be explained in the MIR report.
--- Affected Packages ---
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time, so that should be ok)
seeds - remove seeding of ntp
chrony - MIR itself (seeding)
chrony - add default enabled apparmor profile |
|
| 2018-01-18 14:29:50 |
Christian Ehrhardt |
description |
Note: I know it is the template so far, but after the discussions at the sprint I want something we can start working on together.
Background: after evaluation it was considered easier to maintain to provide a good and secure ntp experience as well as some people asking me if it could be preferred.
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale: NTP in general is needed quite a lot, but we want to exchange ntpd which is the current implementation in main with chrony for 18.04.
3. Security: In fact the request came in by security Team, so I guess I call this section done
-- EVERYTHING BELOW TBD FOR NOW --
Quality assurance:
After installing the package it must be possible to make it working with a reasonable effort of configuration and documentation reading.
The package must not ask debconf questions higher than medium if it is going to be installed by default. The debconf questions must have reasonable defaults.
There are no long-term outstanding bugs which affect the usability of the program to a major degree. To support a package, we must be reasonably convinced that upstream supports and cares for the package.
The status of important bugs in Debian's, Ubuntu's, and upstream's bug tracking systems must be evaluated. Important bugs must be pointed out and discussed in the MIR report.
The package is maintained well in Debian/Ubuntu (check out the Debian PTS)
The package should not deal with exotic hardware which we cannot support.
If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build.
The package uses a debian/watch file whenever possible. In cases where this is not possible (e. g. native packages), the package should either provide a debian/README.source file or a debian/watch file (with comments only) providing clear instructions on how to generate the source tar file.
The package should not rely on obsolete or about to be demoted packages. That currently includes package dependencies on Python2 (without providing Python3 packages), and packages depending on GTK2.
UI standards: (generally only for user-facing applications)
End-user applications must be internationalized (translatable), using the standard intltool/gettext build and runtime system and produce a proper PO template during build.
End-user applications must ship a standard conformant desktop file.
Dependencies:
All binary dependencies (including Recommends:) must be satisfiable in main (i. e. the preferred alternative must be in main). If not, these dependencies need a separate MIR report (this can be a separate bug or another task on the main MIR bug)
Standards compliance: The package should meet the FHS and Debian Policy standards. Major violations should be documented and justified. Also, the source packaging should be reasonably easy to understand and maintain.
Maintenance: The package must have an acceptable level of maintenance corresponding to its complexity:
All packages must have a designated "owning" team, regardless of complexity, which is set as a package bug contact.
Simple packages (e.g. language bindings, simple Perl modules, small command-line programs, etc.) might not need very much maintenance effort, and if they are maintained well in Debian we can just keep them synced
More complex packages will usually need a developer or team of developers paying attention to their bugs, whether that be in Ubuntu or elsewhere (often Debian). Packages that deliver major new headline features in Ubuntu need to have commitment from Ubuntu developers willing to spend substantial time on them.
Background information:
The package descriptions should explain the general purpose and context of the package. Additional explanations/justifications should be done in the MIR report.
If the package was renamed recently, or has a different upstream name, this needs to be explained in the MIR report.
--- Affected Packages ---
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time, so that should be ok)
seeds - remove seeding of ntp
chrony - MIR itself (seeding)
chrony - add default enabled apparmor profile |
Note: I know it is the template so far, but after the discussions at the sprint I want something we can start working on together.
Background: after evaluation it was considered easier to maintain to provide a good and secure ntp experience as well as some people asking me if it could be preferred.
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale: NTP in general is needed quite a lot, but we want to exchange ntpd which is the current implementation in main with chrony for 18.04.
3. Security: In fact the request came in by security Team, so I guess I call this section done
-- EVERYTHING BELOW TBD FOR NOW --
Quality assurance:
After installing the package it must be possible to make it working with a reasonable effort of configuration and documentation reading.
The package must not ask debconf questions higher than medium if it is going to be installed by default. The debconf questions must have reasonable defaults.
There are no long-term outstanding bugs which affect the usability of the program to a major degree. To support a package, we must be reasonably convinced that upstream supports and cares for the package.
The status of important bugs in Debian's, Ubuntu's, and upstream's bug tracking systems must be evaluated. Important bugs must be pointed out and discussed in the MIR report.
The package is maintained well in Debian/Ubuntu (check out the Debian PTS)
The package should not deal with exotic hardware which we cannot support.
If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build.
The package uses a debian/watch file whenever possible. In cases where this is not possible (e. g. native packages), the package should either provide a debian/README.source file or a debian/watch file (with comments only) providing clear instructions on how to generate the source tar file.
The package should not rely on obsolete or about to be demoted packages. That currently includes package dependencies on Python2 (without providing Python3 packages), and packages depending on GTK2.
UI standards: (generally only for user-facing applications)
End-user applications must be internationalized (translatable), using the standard intltool/gettext build and runtime system and produce a proper PO template during build.
End-user applications must ship a standard conformant desktop file.
Dependencies:
All binary dependencies (including Recommends:) must be satisfiable in main (i. e. the preferred alternative must be in main). If not, these dependencies need a separate MIR report (this can be a separate bug or another task on the main MIR bug)
Standards compliance: The package should meet the FHS and Debian Policy standards. Major violations should be documented and justified. Also, the source packaging should be reasonably easy to understand and maintain.
Maintenance: The package must have an acceptable level of maintenance corresponding to its complexity:
All packages must have a designated "owning" team, regardless of complexity, which is set as a package bug contact.
Simple packages (e.g. language bindings, simple Perl modules, small command-line programs, etc.) might not need very much maintenance effort, and if they are maintained well in Debian we can just keep them synced
More complex packages will usually need a developer or team of developers paying attention to their bugs, whether that be in Ubuntu or elsewhere (often Debian). Packages that deliver major new headline features in Ubuntu need to have commitment from Ubuntu developers willing to spend substantial time on them.
Background information:
The package descriptions should explain the general purpose and context of the package. Additional explanations/justifications should be done in the MIR report.
If the package was renamed recently, or has a different upstream name, this needs to be explained in the MIR report.
--- Affected Packages ---
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time, so that should be ok)
seeds - remove seeding of ntp
chrony - MIR itself (not pre-install, but pull it into supported)
chrony - add default enabled apparmor profile |
|
| 2018-01-22 07:24:22 |
Christian Ehrhardt |
bug |
|
|
added subscriber Paul Gear |
| 2018-01-22 07:27:48 |
Christian Ehrhardt |
bug |
|
|
added subscriber Tyler Hicks |
| 2018-01-22 08:23:13 |
Christian Ehrhardt |
description |
Note: I know it is the template so far, but after the discussions at the sprint I want something we can start working on together.
Background: after evaluation it was considered easier to maintain to provide a good and secure ntp experience as well as some people asking me if it could be preferred.
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale: NTP in general is needed quite a lot, but we want to exchange ntpd which is the current implementation in main with chrony for 18.04.
3. Security: In fact the request came in by security Team, so I guess I call this section done
-- EVERYTHING BELOW TBD FOR NOW --
Quality assurance:
After installing the package it must be possible to make it working with a reasonable effort of configuration and documentation reading.
The package must not ask debconf questions higher than medium if it is going to be installed by default. The debconf questions must have reasonable defaults.
There are no long-term outstanding bugs which affect the usability of the program to a major degree. To support a package, we must be reasonably convinced that upstream supports and cares for the package.
The status of important bugs in Debian's, Ubuntu's, and upstream's bug tracking systems must be evaluated. Important bugs must be pointed out and discussed in the MIR report.
The package is maintained well in Debian/Ubuntu (check out the Debian PTS)
The package should not deal with exotic hardware which we cannot support.
If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build.
The package uses a debian/watch file whenever possible. In cases where this is not possible (e. g. native packages), the package should either provide a debian/README.source file or a debian/watch file (with comments only) providing clear instructions on how to generate the source tar file.
The package should not rely on obsolete or about to be demoted packages. That currently includes package dependencies on Python2 (without providing Python3 packages), and packages depending on GTK2.
UI standards: (generally only for user-facing applications)
End-user applications must be internationalized (translatable), using the standard intltool/gettext build and runtime system and produce a proper PO template during build.
End-user applications must ship a standard conformant desktop file.
Dependencies:
All binary dependencies (including Recommends:) must be satisfiable in main (i. e. the preferred alternative must be in main). If not, these dependencies need a separate MIR report (this can be a separate bug or another task on the main MIR bug)
Standards compliance: The package should meet the FHS and Debian Policy standards. Major violations should be documented and justified. Also, the source packaging should be reasonably easy to understand and maintain.
Maintenance: The package must have an acceptable level of maintenance corresponding to its complexity:
All packages must have a designated "owning" team, regardless of complexity, which is set as a package bug contact.
Simple packages (e.g. language bindings, simple Perl modules, small command-line programs, etc.) might not need very much maintenance effort, and if they are maintained well in Debian we can just keep them synced
More complex packages will usually need a developer or team of developers paying attention to their bugs, whether that be in Ubuntu or elsewhere (often Debian). Packages that deliver major new headline features in Ubuntu need to have commitment from Ubuntu developers willing to spend substantial time on them.
Background information:
The package descriptions should explain the general purpose and context of the package. Additional explanations/justifications should be done in the MIR report.
If the package was renamed recently, or has a different upstream name, this needs to be explained in the MIR report.
--- Affected Packages ---
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time, so that should be ok)
seeds - remove seeding of ntp
chrony - MIR itself (not pre-install, but pull it into supported)
chrony - add default enabled apparmor profile |
Note: I know it is the template so far, but after the discussions at the sprint I want something we can start working on together.
Background: after evaluation it was considered easier to maintain to provide a good and secure ntp experience as well as some people asking me if it could be preferred.
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale: NTP in general is needed quite a lot, but we want to exchange ntpd which is the current implementation in main with chrony for 18.04.
3. Security: In fact the request came in by security Team, so I guess I call this section done
-- EVERYTHING BELOW TBD FOR NOW --
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
OPEN - bug 1718227 - convert ifup hooks to networkd compatible hooks
OPEN - bug 1744662 - add chrony apparmor profile
OPEN - bug 1744328 - make src:libnss libfreebl3 usable by other programs
OPEN - bug 1744664 - use Ubuntu time servers |
|
| 2018-01-22 08:30:37 |
Christian Ehrhardt |
description |
Note: I know it is the template so far, but after the discussions at the sprint I want something we can start working on together.
Background: after evaluation it was considered easier to maintain to provide a good and secure ntp experience as well as some people asking me if it could be preferred.
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale: NTP in general is needed quite a lot, but we want to exchange ntpd which is the current implementation in main with chrony for 18.04.
3. Security: In fact the request came in by security Team, so I guess I call this section done
-- EVERYTHING BELOW TBD FOR NOW --
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
OPEN - bug 1718227 - convert ifup hooks to networkd compatible hooks
OPEN - bug 1744662 - add chrony apparmor profile
OPEN - bug 1744328 - make src:libnss libfreebl3 usable by other programs
OPEN - bug 1744664 - use Ubuntu time servers |
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main with chrony for 18.04.
2.2 Security: chrony was considered easier to be maintained easier in
terms of security and provide a more modern ntp experience as well.
2.3 Efficiency: Furthermore several cloud people seem to be interested to
change to chrony in the guests for its lower memoy/cpu footprint
(efficiency I guess).
2.4 related to this MIR 6 years ago this is the same but for Fedora.
See: https://fedoraproject.org/wiki/Features/ChronyDefaultNTP
IIRC some limitations that were present have been eliminated since, so
it is even better than it was back then.
2.5 In general one has to realize that in a systemd-timesync world
ntp/chrony are mostly for the "serving" portion of an ntp service, and
not so much about the client (unless you the better accuracy vs
timesyncd is needed).
3. Security: In fact the request came in by security Team, so I guess I call this section done
-- EVERYTHING BELOW TBD FOR NOW --
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
OPEN - bug 1718227 - convert ifup hooks to networkd compatible hooks
OPEN - bug 1744662 - add chrony apparmor profile
OPEN - bug 1744328 - make src:libnss libfreebl3 usable by other programs
OPEN - bug 1744664 - use Ubuntu time servers |
|
| 2018-01-22 08:30:57 |
Christian Ehrhardt |
bug task added |
|
maas (Ubuntu) |
|
| 2018-01-22 08:31:18 |
Christian Ehrhardt |
bug task added |
|
cloud-init (Ubuntu) |
|
| 2018-01-22 08:31:32 |
Christian Ehrhardt |
bug task added |
|
ceph (Ubuntu) |
|
| 2018-01-22 08:32:48 |
Christian Ehrhardt |
bug task added |
|
ntp-charm |
|
| 2018-01-22 08:33:43 |
Christian Ehrhardt |
bug |
|
|
added subscriber MIR approval team |
| 2018-01-22 17:27:15 |
Launchpad Janitor |
ceph (Ubuntu): status |
New |
Confirmed |
|
| 2018-01-22 17:27:15 |
Launchpad Janitor |
chrony (Ubuntu): status |
New |
Confirmed |
|
| 2018-01-22 17:27:15 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
New |
Confirmed |
|
| 2018-01-22 17:27:15 |
Launchpad Janitor |
maas (Ubuntu): status |
New |
Confirmed |
|
| 2018-01-22 17:27:18 |
Simon Déziel |
bug |
|
|
added subscriber Simon Déziel |
| 2018-01-23 06:46:59 |
Christian Ehrhardt |
description |
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main with chrony for 18.04.
2.2 Security: chrony was considered easier to be maintained easier in
terms of security and provide a more modern ntp experience as well.
2.3 Efficiency: Furthermore several cloud people seem to be interested to
change to chrony in the guests for its lower memoy/cpu footprint
(efficiency I guess).
2.4 related to this MIR 6 years ago this is the same but for Fedora.
See: https://fedoraproject.org/wiki/Features/ChronyDefaultNTP
IIRC some limitations that were present have been eliminated since, so
it is even better than it was back then.
2.5 In general one has to realize that in a systemd-timesync world
ntp/chrony are mostly for the "serving" portion of an ntp service, and
not so much about the client (unless you the better accuracy vs
timesyncd is needed).
3. Security: In fact the request came in by security Team, so I guess I call this section done
-- EVERYTHING BELOW TBD FOR NOW --
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
OPEN - bug 1718227 - convert ifup hooks to networkd compatible hooks
OPEN - bug 1744662 - add chrony apparmor profile
OPEN - bug 1744328 - make src:libnss libfreebl3 usable by other programs
OPEN - bug 1744664 - use Ubuntu time servers |
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main with chrony for 18.04.
2.2 Security: chrony was considered easier to be maintained easier in
terms of security and provide a more modern ntp experience as well.
2.3 Efficiency: Furthermore several cloud people seem to be interested to
change to chrony in the guests for its lower memoy/cpu footprint
(efficiency I guess).
2.4 related to this MIR 6 years ago this is the same but for Fedora.
See: https://fedoraproject.org/wiki/Features/ChronyDefaultNTP
IIRC some limitations that were present have been eliminated since, so
it is even better than it was back then.
2.5 In general one has to realize that in a systemd-timesync world
ntp/chrony are mostly for the "serving" portion of an ntp service, and
not so much about the client (unless you the better accuracy vs
timesyncd is needed).
3. Security: In fact the request came in by security Team, so I guess I call this section done
-- EVERYTHING BELOW TBD FOR NOW --
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
OPEN - bug 1718227 - convert ifup hooks to networkd compatible hooks
DONE - bug 1744662 - add chrony apparmor profile
OPEN - bug 1744328 - make src:libnss libfreebl3 usable by other programs
OPEN - bug 1744664 - use Ubuntu time servers |
|
| 2018-01-25 17:16:15 |
Christian Ehrhardt |
bug task added |
|
serverguide |
|
| 2018-01-26 20:23:36 |
David Britton |
bug |
|
|
added subscriber David Britton |
| 2018-01-29 16:28:21 |
Christian Ehrhardt |
description |
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main with chrony for 18.04.
2.2 Security: chrony was considered easier to be maintained easier in
terms of security and provide a more modern ntp experience as well.
2.3 Efficiency: Furthermore several cloud people seem to be interested to
change to chrony in the guests for its lower memoy/cpu footprint
(efficiency I guess).
2.4 related to this MIR 6 years ago this is the same but for Fedora.
See: https://fedoraproject.org/wiki/Features/ChronyDefaultNTP
IIRC some limitations that were present have been eliminated since, so
it is even better than it was back then.
2.5 In general one has to realize that in a systemd-timesync world
ntp/chrony are mostly for the "serving" portion of an ntp service, and
not so much about the client (unless you the better accuracy vs
timesyncd is needed).
3. Security: In fact the request came in by security Team, so I guess I call this section done
-- EVERYTHING BELOW TBD FOR NOW --
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
OPEN - bug 1718227 - convert ifup hooks to networkd compatible hooks
DONE - bug 1744662 - add chrony apparmor profile
OPEN - bug 1744328 - make src:libnss libfreebl3 usable by other programs
OPEN - bug 1744664 - use Ubuntu time servers |
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main with chrony for 18.04.
2.2 Security: chrony was considered easier to be maintained easier in
terms of security and provide a more modern ntp experience as well.
2.3 Efficiency: Furthermore several cloud people seem to be interested to
change to chrony in the guests for its lower memoy/cpu footprint
(efficiency I guess).
2.4 related to this MIR 6 years ago this is the same but for Fedora.
See: https://fedoraproject.org/wiki/Features/ChronyDefaultNTP
IIRC some limitations that were present have been eliminated since, so
it is even better than it was back then.
2.5 In general one has to realize that in a systemd-timesync world
ntp/chrony are mostly for the "serving" portion of an ntp service, and
not so much about the client (unless you the better accuracy vs
timesyncd is needed).
3. Security: In fact the request came in by security Team, so I guess I call this section done
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
OPEN - bug 1718227 - convert ifup hooks to networkd compatible hooks
DONE - bug 1744662 - add chrony apparmor profile
OPEN - bug 1744328 - make src:libnss libfreebl3 usable by other programs
OPEN - bug 1744664 - use Ubuntu time servers |
|
| 2018-01-30 03:56:04 |
Seth Arnold |
bug |
|
|
added subscriber Seth Arnold |
| 2018-01-30 13:47:02 |
Christian Ehrhardt |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/336844 |
|
| 2018-01-31 06:55:56 |
Christian Ehrhardt |
description |
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main with chrony for 18.04.
2.2 Security: chrony was considered easier to be maintained easier in
terms of security and provide a more modern ntp experience as well.
2.3 Efficiency: Furthermore several cloud people seem to be interested to
change to chrony in the guests for its lower memoy/cpu footprint
(efficiency I guess).
2.4 related to this MIR 6 years ago this is the same but for Fedora.
See: https://fedoraproject.org/wiki/Features/ChronyDefaultNTP
IIRC some limitations that were present have been eliminated since, so
it is even better than it was back then.
2.5 In general one has to realize that in a systemd-timesync world
ntp/chrony are mostly for the "serving" portion of an ntp service, and
not so much about the client (unless you the better accuracy vs
timesyncd is needed).
3. Security: In fact the request came in by security Team, so I guess I call this section done
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
OPEN - bug 1718227 - convert ifup hooks to networkd compatible hooks
DONE - bug 1744662 - add chrony apparmor profile
OPEN - bug 1744328 - make src:libnss libfreebl3 usable by other programs
OPEN - bug 1744664 - use Ubuntu time servers |
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main with chrony for 18.04.
2.2 Security: chrony was considered easier to be maintained easier in
terms of security and provide a more modern ntp experience as well.
2.3 Efficiency: Furthermore several cloud people seem to be interested to
change to chrony in the guests for its lower memoy/cpu footprint
(efficiency I guess).
2.4 related to this MIR 6 years ago this is the same but for Fedora.
See: https://fedoraproject.org/wiki/Features/ChronyDefaultNTP
IIRC some limitations that were present have been eliminated since, so
it is even better than it was back then.
2.5 In general one has to realize that in a systemd-timesync world
ntp/chrony are mostly for the "serving" portion of an ntp service, and
not so much about the client (unless you the better accuracy vs
timesyncd is needed).
3. Security: In fact the request came in by security Team, so I guess I call this section done
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
DONE - bug 1744662 - add chrony apparmor profile
COMMITTED - bug 1744328 - make src:libnss libfreebl3 usable by other programs
COMMITTED - bug 1744664 - use Ubuntu time servers |
|
| 2018-02-06 08:52:38 |
Christian Ehrhardt |
description |
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main with chrony for 18.04.
2.2 Security: chrony was considered easier to be maintained easier in
terms of security and provide a more modern ntp experience as well.
2.3 Efficiency: Furthermore several cloud people seem to be interested to
change to chrony in the guests for its lower memoy/cpu footprint
(efficiency I guess).
2.4 related to this MIR 6 years ago this is the same but for Fedora.
See: https://fedoraproject.org/wiki/Features/ChronyDefaultNTP
IIRC some limitations that were present have been eliminated since, so
it is even better than it was back then.
2.5 In general one has to realize that in a systemd-timesync world
ntp/chrony are mostly for the "serving" portion of an ntp service, and
not so much about the client (unless you the better accuracy vs
timesyncd is needed).
3. Security: In fact the request came in by security Team, so I guess I call this section done
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
DONE - bug 1744662 - add chrony apparmor profile
COMMITTED - bug 1744328 - make src:libnss libfreebl3 usable by other programs
COMMITTED - bug 1744664 - use Ubuntu time servers |
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main with chrony for 18.04.
2.2 Security: chrony was considered easier to be maintained easier in
terms of security and provide a more modern ntp experience as well.
2.3 Efficiency: Furthermore several cloud people seem to be interested to
change to chrony in the guests for its lower memoy/cpu footprint
(efficiency I guess).
2.4 related to this MIR 6 years ago this is the same but for Fedora.
See: https://fedoraproject.org/wiki/Features/ChronyDefaultNTP
IIRC some limitations that were present have been eliminated since, so
it is even better than it was back then.
2.5 In general one has to realize that in a systemd-timesync world
ntp/chrony are mostly for the "serving" portion of an ntp service, and
not so much about the client (unless you the better accuracy vs
timesyncd is needed).
3. Security: In fact the request came in by security Team, so I guess I call this section done
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
DONE - bug 1744662 - add chrony apparmor profile
DONE - bug 1744328 - make src:libnss libfreebl3 usable by other programs
COMMITTED - bug 1744664 - use Ubuntu time servers
COMMITTED - bug 1744072 - d/control: use to nss instead of tomcrypt
Some more cleanups in Chrony are optional but useful. |
|
| 2018-02-06 22:55:42 |
Haw Loeung |
bug |
|
|
added subscriber Haw Loeung |
| 2018-02-07 08:16:38 |
Launchpad Janitor |
chrony (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2018-02-07 09:54:54 |
Christian Ehrhardt |
chrony (Ubuntu): status |
Fix Released |
New |
|
| 2018-02-07 09:55:02 |
Christian Ehrhardt |
summary |
MIR Chrony in 18.04 |
[MIR] Chrony in 18.04 |
|
| 2018-02-07 10:13:33 |
Christian Ehrhardt |
branch linked |
|
lp:~paelzer/ubuntu-seeds/18.04-ntp-to-chrony-platform |
|
| 2018-02-07 10:13:43 |
Christian Ehrhardt |
branch linked |
|
lp:~paelzer/ubuntu-seeds/18.04-ntp-to-chrony-ubuntu |
|
| 2018-02-08 23:42:53 |
David Britton |
description |
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main with chrony for 18.04.
2.2 Security: chrony was considered easier to be maintained easier in
terms of security and provide a more modern ntp experience as well.
2.3 Efficiency: Furthermore several cloud people seem to be interested to
change to chrony in the guests for its lower memoy/cpu footprint
(efficiency I guess).
2.4 related to this MIR 6 years ago this is the same but for Fedora.
See: https://fedoraproject.org/wiki/Features/ChronyDefaultNTP
IIRC some limitations that were present have been eliminated since, so
it is even better than it was back then.
2.5 In general one has to realize that in a systemd-timesync world
ntp/chrony are mostly for the "serving" portion of an ntp service, and
not so much about the client (unless you the better accuracy vs
timesyncd is needed).
3. Security: In fact the request came in by security Team, so I guess I call this section done
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
DONE - bug 1744662 - add chrony apparmor profile
DONE - bug 1744328 - make src:libnss libfreebl3 usable by other programs
COMMITTED - bug 1744664 - use Ubuntu time servers
COMMITTED - bug 1744072 - d/control: use to nss instead of tomcrypt
Some more cleanups in Chrony are optional but useful. |
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main with chrony for 18.04.
2.2 Security: chrony was considered easier to be maintained easier in
terms of security and provide a more modern ntp experience as well.
2.3 Efficiency: Furthermore several cloud people seem to be interested to
change to chrony in the guests for its lower memoy/cpu footprint
(efficiency I guess).
2.4 related to this MIR 6 years ago this is the same but for Fedora.
See: https://fedoraproject.org/wiki/Features/ChronyDefaultNTP
IIRC some limitations that were present have been eliminated since, so
it is even better than it was back then.
2.5 In general one has to realize that in a systemd-timesync world
ntp/chrony are mostly for the "serving" portion of an ntp service, and
not so much about the client (unless you the better accuracy vs
timesyncd is needed).
3. Security: In fact the request came in by security Team, so I guess I call this section done
3. Quality assurance
3.1 configuration ease - works after installation
3.2 no high prio debconf
3.3 usability (no major issues in Debian nor Ubuntu)
asked Paul in regard to the ntp charm in comment #5
3.4 long-term >=high bugs (none in Debian nor Ubuntu)
3.5 Debian/Ubuntu bugs look reasonable maintained
3.6 does not deal with hard to support exotic hardware (other than ntpd
btw). If used this can be done through universe package GPSD (no
dependency)
3.7 Test suite runs on build (some skipped if not env applicable)
3.8 debian/watch exists
3.9 not depending on obsoleted packages
4.1 It does not face graphical UI
4.2 It is unfortunately not internationalized as far as I could see in the source
5. Dependencies - there is one not in main libtomcrypt
We don't want it in main either, instead we want to fix bug 1744328 and then use libnss which is in main already.
6. Not found major Policy or FSH violations that would have to be fixed.
7. Maintenance
7.1 Upstream - is maintained well (and better than ntpd it seems
according to some discussisons)
7.2 Ubuntu - Owning Team would be Ubuntu (in exchange to drop ntp)
8. Background information:
Fulfills the same role as ntp, yet according to the security Team would
be preferred for them.
--- Affected Packages ---
I'll add all those as bug tasks.
Once the MIR has passed the state of uncertainty (e.g. would it be blocked by one of the dependent bug being not doable at all) then please work on these into 18.04. Here a list what is affected in the listed packages:
Maas - needs to change dependencies and maybe template
cloud-init - needs to support writing ntp config to chrony instead of ntpd
ceph-base - change recommends from ntpd to chrony (it only intends to get good time and doesn't care via which dameon that is, so that should be ok to be change)
ntp charm - switch to chrony for >=18.04
chrony - MIR itself (discussion here and eventually seeding)
--- Depending on further Bugs ---
In my initial evaluation I uncovered (and filed) a set of bugs that I consider requirement to make it fully ready:
Reminder - tracking state here might be out of sync, I'll only change them to Done once complete and not care about interim status changes.
DONE - bug 1744662 - add chrony apparmor profile
DONE - bug 1744328 - make src:libnss libfreebl3 usable by other programs
COMMITTED - bug 1744664 - use Ubuntu time servers
COMMITTED - bug 1744072 - d/control: use to nss instead of tomcrypt
Some more cleanups in Chrony are optional but useful.
Other Related Bugs
* https://bugs.launchpad.net/cloud-init/+bug/1731619 (cloud-init) |
|
| 2018-02-12 22:06:06 |
Steve Langasek |
bug |
|
|
added subscriber Steve Langasek |
| 2018-02-13 03:42:25 |
Paul Gear |
ntp-charm: status |
New |
Triaged |
|
| 2018-02-13 03:42:31 |
Paul Gear |
ntp-charm: importance |
Undecided |
Medium |
|
| 2018-02-14 16:17:56 |
Nish Aravamudan |
chrony (Ubuntu): assignee |
|
Nish Aravamudan (nacc) |
|
| 2018-02-14 16:18:01 |
Nish Aravamudan |
chrony (Ubuntu): status |
New |
In Progress |
|
| 2018-02-15 22:39:30 |
Nish Aravamudan |
chrony (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2018-02-16 21:13:57 |
Steve Langasek |
chrony (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2018-02-19 07:47:14 |
Christian Ehrhardt |
maas (Ubuntu): importance |
Undecided |
Critical |
|
| 2018-02-19 07:47:16 |
Christian Ehrhardt |
ceph (Ubuntu): status |
Confirmed |
In Progress |
|
| 2018-02-19 07:52:36 |
Christian Ehrhardt |
chrony (Ubuntu): assignee |
Nish Aravamudan (nacc) |
|
|
| 2018-02-20 02:42:02 |
Launchpad Janitor |
ceph (Ubuntu): status |
In Progress |
Fix Released |
|
| 2018-02-23 10:56:10 |
Christian Ehrhardt |
branch linked |
|
lp:~paelzer/serverguide/serverguide-chrony-18.04 |
|
| 2018-02-23 16:21:37 |
Launchpad Janitor |
branch linked |
|
lp:serverguide |
|
| 2018-02-23 16:22:57 |
Doug Smythies |
serverguide: status |
New |
Fix Committed |
|
| 2018-02-23 19:55:56 |
Andres Rodriguez |
merge proposal linked |
|
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/336685 |
|
| 2018-02-23 19:56:02 |
Andres Rodriguez |
maas (Ubuntu): assignee |
|
Andres Rodriguez (andreserl) |
|
| 2018-02-23 19:56:04 |
Andres Rodriguez |
maas (Ubuntu): status |
Confirmed |
In Progress |
|
| 2018-02-26 17:40:37 |
Andres Rodriguez |
merge proposal linked |
|
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/339706 |
|
| 2018-02-26 17:41:39 |
Andres Rodriguez |
merge proposal linked |
|
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/339707 |
|
| 2018-02-27 00:00:44 |
Andres Rodriguez |
maas (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2018-02-27 00:00:56 |
Andres Rodriguez |
maas (Ubuntu): status |
Fix Committed |
In Progress |
|
| 2018-03-06 04:55:14 |
Paul Gear |
merge proposal linked |
|
https://code.launchpad.net/~paulgear/ntp-charm/+git/ntp-charm/+merge/340780 |
|
| 2018-03-06 04:55:30 |
Paul Gear |
ntp-charm: assignee |
|
Paul Gear (paulgear) |
|
| 2018-03-06 04:55:34 |
Paul Gear |
ntp-charm: status |
Triaged |
In Progress |
|
| 2018-04-26 14:55:26 |
Doug Smythies |
serverguide: status |
Fix Committed |
Fix Released |
|
| 2018-06-07 18:57:25 |
Christian Ehrhardt |
cloud-init (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2018-06-07 18:57:27 |
Christian Ehrhardt |
maas (Ubuntu): status |
In Progress |
Fix Released |
|
| 2018-06-13 21:22:01 |
Mathieu Trudel-Lapierre |
removed subscriber MIR approval team |
|
|
|
| 2018-09-17 04:45:39 |
Paul Gear |
ntp-charm: status |
In Progress |
Fix Committed |
|
| 2018-11-30 03:12:03 |
Paul Gear |
ntp-charm: status |
Fix Committed |
Fix Released |
|
