[Bug 2045708] Please test proposed package

Robie Basak 2045708 at bugs.launchpad.net
Wed Feb 14 14:39:03 UTC 2024


Hello Chloé, or anyone else affected,

Accepted gce-compute-image-packages into mantic-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/gce-compute-image-
packages/20230808.00-0ubuntu2~23.10.0 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gce-compute-image-packages in
Ubuntu.
https://bugs.launchpad.net/bugs/2045708

Title:
  [SRU] Improve debian/99-gce.rules to set schedulers based on disk

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Focal:
  Fix Committed
Status in gce-compute-image-packages source package in Jammy:
  Fix Committed
Status in gce-compute-image-packages source package in Mantic:
  Fix Committed

Bug 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.

  [ 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2045708/+subscriptions




More information about the foundations-bugs mailing list