| 2023-12-06 01:13:36 |
Chloé Smith |
bug |
|
|
added bug |
| 2023-12-06 01:15:43 |
Chloé Smith |
description |
We should reduce the `udev` rule scope here and change I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yeilded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Test Plan ]
* I Built test GCP images with this file changed as proposed [0]
* This can be done with a PPA hooked into CPC bootstrap scripts (kajiya's here: [1])
[ Where problems could occur ]
* I can't see any regressions happening as we're moving _from_ `noop` _to_ not using a scheduler at all
(`none`), which was the original behaviour before this file was introduced.
SRU
====
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no scheduler will be used
natively.
* This package is provided upstream by Google themselves, and is part of a collection of tools and that
ensure that the Ubuntu images published to GCE run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and published in the `ubuntu-os-
cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes will be handed to the Google
team to perform their own verification.
If all the testing indicates that the image containing the new package is good, verification is considered finished. |
We should reduce the `udev` rule scope here and change I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yielded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Test Plan ]
* I Built test GCP images with this file changed as proposed [0]
* This can be done with a PPA hooked into CPC bootstrap scripts (kajiya's here: [1])
[ Where problems could occur ]
* I can't see any regressions happening as we're moving _from_ `noop` _to_ not using a scheduler at all
(`none`), which was the original behaviour before this file was introduced.
SRU
====
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no
scheduler will be used natively.
* This package is provided upstream by Google themselves, and is part of a
collection of tools and that ensures that the Ubuntu images published to GCE
run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and
published in the `ubuntu-os-cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes
will be handed to the Google team to perform their own verification.
If all the testing indicates that the image containing the new package is good, verification is considered finished.
[0]: https://code.launchpad.net/~kajiya/ubuntu/+source/gce-compute-image-packages/+git/gce-compute-image-packages/+merge/455766
[1]: https://launchpad.net/~kajiya/+archive/ubuntu/gce-compute-image-packages |
|
| 2023-12-06 01:16:20 |
Chloé Smith |
description |
We should reduce the `udev` rule scope here and change I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yielded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Test Plan ]
* I Built test GCP images with this file changed as proposed [0]
* This can be done with a PPA hooked into CPC bootstrap scripts (kajiya's here: [1])
[ Where problems could occur ]
* I can't see any regressions happening as we're moving _from_ `noop` _to_ not using a scheduler at all
(`none`), which was the original behaviour before this file was introduced.
SRU
====
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no
scheduler will be used natively.
* This package is provided upstream by Google themselves, and is part of a
collection of tools and that ensures that the Ubuntu images published to GCE
run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and
published in the `ubuntu-os-cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes
will be handed to the Google team to perform their own verification.
If all the testing indicates that the image containing the new package is good, verification is considered finished.
[0]: https://code.launchpad.net/~kajiya/ubuntu/+source/gce-compute-image-packages/+git/gce-compute-image-packages/+merge/455766
[1]: https://launchpad.net/~kajiya/+archive/ubuntu/gce-compute-image-packages |
We should reduce the `udev` rule scope here and change I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yielded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Test Plan ]
* I built test GCP images with this file changed as proposed [0]
* This can be done with a PPA hooked into CPC bootstrap scripts (kajiya's here: [1])
[ Where problems could occur ]
* I can't see any regressions happening as we're moving _from_ `noop` _to_ not using a scheduler at all
(`none`), which was the original behaviour before this file was introduced.
SRU
====
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no
scheduler will be used natively.
* This package is provided upstream by Google themselves, and is part of a
collection of tools and that ensures that the Ubuntu images published to GCE
run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and
published in the `ubuntu-os-cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes
will be handed to the Google team to perform their own verification.
If all the testing indicates that the image containing the new package is good, verification is considered finished.
[0]: https://code.launchpad.net/~kajiya/ubuntu/+source/gce-compute-image-packages/+git/gce-compute-image-packages/+merge/455766
[1]: https://launchpad.net/~kajiya/+archive/ubuntu/gce-compute-image-packages |
|
| 2023-12-06 06:54:12 |
Andrew Cloke |
bug |
|
|
added subscriber Andrew Cloke |
| 2023-12-06 13:46:34 |
Launchpad Janitor |
gce-compute-image-packages (Ubuntu): status |
New |
Fix Released |
|
| 2024-01-11 02:23:32 |
Chloé Smith |
merge proposal linked |
|
https://code.launchpad.net/~kajiya/cloud-images/+git/gce-compute-image-packages/+merge/458395 |
|
| 2024-01-11 02:23:46 |
Chloé Smith |
merge proposal linked |
|
https://code.launchpad.net/~kajiya/cloud-images/+git/gce-compute-image-packages/+merge/458396 |
|
| 2024-01-11 02:23:57 |
Chloé Smith |
merge proposal linked |
|
https://code.launchpad.net/~kajiya/cloud-images/+git/gce-compute-image-packages/+merge/458397 |
|
| 2024-01-11 02:24:08 |
Chloé Smith |
merge proposal linked |
|
https://code.launchpad.net/~kajiya/cloud-images/+git/gce-compute-image-packages/+merge/458398 |
|
| 2024-01-11 02:29:26 |
Chloé Smith |
description |
We should reduce the `udev` rule scope here and change I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yielded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Test Plan ]
* I built test GCP images with this file changed as proposed [0]
* This can be done with a PPA hooked into CPC bootstrap scripts (kajiya's here: [1])
[ Where problems could occur ]
* I can't see any regressions happening as we're moving _from_ `noop` _to_ not using a scheduler at all
(`none`), which was the original behaviour before this file was introduced.
SRU
====
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no
scheduler will be used natively.
* This package is provided upstream by Google themselves, and is part of a
collection of tools and that ensures that the Ubuntu images published to GCE
run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and
published in the `ubuntu-os-cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes
will be handed to the Google team to perform their own verification.
If all the testing indicates that the image containing the new package is good, verification is considered finished.
[0]: https://code.launchpad.net/~kajiya/ubuntu/+source/gce-compute-image-packages/+git/gce-compute-image-packages/+merge/455766
[1]: https://launchpad.net/~kajiya/+archive/ubuntu/gce-compute-image-packages |
We should reduce the `udev` rule scope here and change I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yielded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no
scheduler will be used natively.
* This package is provided upstream by Google themselves, and is part of a
collection of tools and that ensures that the Ubuntu images published to GCE
run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and
published in the `ubuntu-os-cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes
will be handed to the Google team to perform their own verification.
* This can also be done independently with a PPA hooked into CPC's bootstrap
scripts (kajiya's PPA here: [0])
If all the testing indicates that the image containing the new package is good, verification is considered finished.
[0]: https://launchpad.net/~kajiya/+archive/ubuntu/gce-compute-image-packages |
|
| 2024-02-02 15:36:56 |
Philip Roche |
nominated for series |
|
Ubuntu Jammy |
|
| 2024-02-02 15:36:56 |
Philip Roche |
bug task added |
|
gce-compute-image-packages (Ubuntu Jammy) |
|
| 2024-02-02 15:36:56 |
Philip Roche |
nominated for series |
|
Ubuntu Mantic |
|
| 2024-02-02 15:36:56 |
Philip Roche |
bug task added |
|
gce-compute-image-packages (Ubuntu Mantic) |
|
| 2024-02-02 15:36:56 |
Philip Roche |
nominated for series |
|
Ubuntu Focal |
|
| 2024-02-02 15:36:56 |
Philip Roche |
bug task added |
|
gce-compute-image-packages (Ubuntu Focal) |
|
| 2024-02-02 16:09:50 |
Chloé Smith |
summary |
Improve debian/99-gce.rules to set schedulers based on disk |
[SRU] Improve debian/99-gce.rules to set schedulers based on disk |
|
| 2024-02-02 16:14:18 |
Chloé Smith |
description |
We should reduce the `udev` rule scope here and change I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yielded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no
scheduler will be used natively.
* This package is provided upstream by Google themselves, and is part of a
collection of tools and that ensures that the Ubuntu images published to GCE
run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and
published in the `ubuntu-os-cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes
will be handed to the Google team to perform their own verification.
* This can also be done independently with a PPA hooked into CPC's bootstrap
scripts (kajiya's PPA here: [0])
If all the testing indicates that the image containing the new package is good, verification is considered finished.
[0]: https://launchpad.net/~kajiya/+archive/ubuntu/gce-compute-image-packages |
[SRU]
=======
[Overview]
We should reduce the scope of the `udev` rules in d/99-gce.rules, and change the I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yielded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no
scheduler will be used natively.
* This package is provided upstream by Google themselves, and is part of a
collection of tools and that ensures that the Ubuntu images published to GCE
run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and
published in the `ubuntu-os-cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes
will be handed to the Google team to perform their own verification.
* This can also be done independently with a PPA hooked into CPC's bootstrap
scripts (kajiya's PPA here: [0])
If all the testing indicates that the image containing the new package is good, verification is considered finished. [Additional Information]
This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [1].
[0]: https://launchpad.net/~kajiya/+archive/ubuntu/gce-compute-image-packages
[1]: https://wiki.ubuntu.com/google-compute-engine-oslogin-Updates |
|
| 2024-02-02 16:15:58 |
Chloé Smith |
description |
[SRU]
=======
[Overview]
We should reduce the scope of the `udev` rules in d/99-gce.rules, and change the I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yielded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no
scheduler will be used natively.
* This package is provided upstream by Google themselves, and is part of a
collection of tools and that ensures that the Ubuntu images published to GCE
run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and
published in the `ubuntu-os-cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes
will be handed to the Google team to perform their own verification.
* This can also be done independently with a PPA hooked into CPC's bootstrap
scripts (kajiya's PPA here: [0])
If all the testing indicates that the image containing the new package is good, verification is considered finished. [Additional Information]
This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [1].
[0]: https://launchpad.net/~kajiya/+archive/ubuntu/gce-compute-image-packages
[1]: https://wiki.ubuntu.com/google-compute-engine-oslogin-Updates |
[SRU]
=======
[Overview]
We should reduce the scope of the `udev` rules in d/99-gce.rules, and change the I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yielded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no
scheduler will be used natively.
* This package is provided upstream by Google themselves, and is part of a
collection of tools and that ensures that the Ubuntu images published to GCE
run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and
published in the `ubuntu-os-cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes
will be handed to the Google team to perform their own verification.
* This can also be done independently with a PPA hooked into CPC's bootstrap
scripts (kajiya's PPA here: [0])
If all the testing indicates that the image containing the new package is good, verification is considered finished. [Additional Information]
This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [1].
[0]: https://launchpad.net/~kajiya/+archive/ubuntu/gce-compute-image-packages
[1]: https://wiki.ubuntu.com/google-compute-engine-oslogin-Updates |
|
| 2024-02-06 09:43:05 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Utkarsh Gupta |
| 2024-02-12 11:17:15 |
Łukasz Zemczak |
gce-compute-image-packages (Ubuntu Jammy): status |
New |
Fix Committed |
|
| 2024-02-12 11:17:16 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-02-12 11:17:17 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2024-02-12 11:17:19 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-jammy |
|
| 2024-02-12 11:17:42 |
Łukasz Zemczak |
gce-compute-image-packages (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2024-02-12 11:17:45 |
Łukasz Zemczak |
tags |
verification-needed verification-needed-jammy |
verification-needed verification-needed-focal verification-needed-jammy |
|
| 2024-02-13 12:45:44 |
Chloé Smith |
description |
[SRU]
=======
[Overview]
We should reduce the scope of the `udev` rules in d/99-gce.rules, and change the I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yielded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no
scheduler will be used natively.
* This package is provided upstream by Google themselves, and is part of a
collection of tools and that ensures that the Ubuntu images published to GCE
run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and
published in the `ubuntu-os-cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes
will be handed to the Google team to perform their own verification.
* This can also be done independently with a PPA hooked into CPC's bootstrap
scripts (kajiya's PPA here: [0])
If all the testing indicates that the image containing the new package is good, verification is considered finished. [Additional Information]
This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [1].
[0]: https://launchpad.net/~kajiya/+archive/ubuntu/gce-compute-image-packages
[1]: https://wiki.ubuntu.com/google-compute-engine-oslogin-Updates |
[SRU]
=======
[Overview]
We should reduce the scope of the `udev` rules in d/99-gce.rules, and change the I/O scheduler. The previous `udev` rule was drastically reducing the bootspeed on SSD backed instances, as the `noop` scheduler is pretty old school.
I did pretty extensive experimentation and found that swapping to "none" in this file yielded the best results on HDD instances (>10s improvement in boot time on average). Letting SSD's just roll independently also seemed to give the best speeds.
[ Impact ]
* If an end user launches an Ubuntu instance in GCE backed with a HDD, no
scheduler will be used natively.
* This package is provided upstream by Google themselves, and is part of a
collection of tools and that ensures that the Ubuntu images published to GCE
run properly on the platform.
[Test Case]
When this package lands in -proposed, the following will happen:
* an image built with this package from -proposed will be built for GCE and
published in the `ubuntu-os-cloud-image-proposed` project
* The image will go through CPC's own CTF framework, and assuming it passes
will be handed to the Google team to perform their own verification.
* This can also be done independently with a PPA hooked into CPC's bootstrap
scripts (kajiya's PPA here: [0])
If all the testing indicates that the image containing the new package is good, verification is considered finished.
[ Regression potential / Where problems could occur ]
* This may affect users who are already modifying the file (d/99-gce.rules) via
a startup script on boot [2]; there have been no edits since 2017 so it's a
pretty well established file.
* There could also be issues if a non-rotating disk is interpreted as a rotating
disk (and vice-versa). This shouldn't be a big problem in practice though, as
the named scheduler is "none" which works well on both types anyway.
[Additional Information]
This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [1].
[0]: https://launchpad.net/~kajiya/+archive/ubuntu/gce-compute-image-packages
[1]: https://wiki.ubuntu.com/google-compute-engine-oslogin-Updates
[2]: https://cloud.google.com/compute/docs/instances/startup-scripts/linux |
|
| 2024-02-13 21:45:54 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Simon Quigley |
| 2024-02-14 14:38:59 |
Robie Basak |
gce-compute-image-packages (Ubuntu Mantic): status |
New |
Fix Committed |
|
| 2024-02-14 14:39:02 |
Robie Basak |
tags |
verification-needed verification-needed-focal verification-needed-jammy |
verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic |
|
| 2024-04-12 16:57:38 |
Andrew Cloke |
tags |
verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic |
verification-done-jammy verification-done-mantic verification-needed verification-needed-focal |
|
| 2024-04-12 17:06:48 |
Andrew Cloke |
tags |
verification-done-jammy verification-done-mantic verification-needed verification-needed-focal |
verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic |
|
| 2024-04-15 11:56:56 |
Andrew Cloke |
tags |
verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic |
verification-done-jammy verification-done-mantic verification-needed verification-needed-focal |
|
| 2024-04-24 09:18:53 |
Andrew Cloke |
tags |
verification-done-jammy verification-done-mantic verification-needed verification-needed-focal |
verification-done verification-done-focal verification-done-jammy verification-done-mantic |
|
| 2024-04-25 20:48:46 |
Launchpad Janitor |
gce-compute-image-packages (Ubuntu Mantic): status |
Fix Committed |
Fix Released |
|
| 2024-04-25 20:48:49 |
Andreas Hasenack |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2024-04-25 20:49:13 |
Launchpad Janitor |
gce-compute-image-packages (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2024-04-25 20:49:25 |
Launchpad Janitor |
gce-compute-image-packages (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
