** Description changed: [ Impact ] * I'm part of Canonical's HPC team, and we're currently working on the lustre-server charm (https://charmhub.io/lustre-server). However, the charm currently uses a PPA to install and serve the Lustre packages required for the client and the server, which is not enough to offer - LTS guarantees for our product. Backporting the Lustre packages - into Resolute offers such guarantee. + LTS guarantees for our product, and requires building the Lustre modules + using DKMS, which takes a significant amount of deployment time. + Backporting the Lustre package into Resolute offers the LTS guarantees + we want and unblocks publishing the Lustre kernel modules as part of + the `linux-main-modules` interlock package. [ Test Plan ] * The package includes an autopkgtest that verifies the DKMS compilation process is successful. - * A PPA verifies the backport builds on Resolute systems - Build logs: - https://launchpad.net/~jedel/+archive/ubuntu/lustre-resolute/+build/33823814/+files/buildlog_ubuntu-resolute-amd64.lustre_2.17.58+dfsg-0ubuntu2~bpo26.04.1~ppa1_BUILDING.txt.gz + * A PPA verifies the backport builds on Resolute systems + Build logs: + https://launchpad.net/~jedel/+archive/ubuntu/lustre-resolute/+build/33823814/+files/buildlog_ubuntu-resolute-amd64.lustre_2.17.58+dfsg-0ubuntu2~bpo26.04.1~ppa1_BUILDING.txt.gz * The attached script can be used to deploy a 3 node cluster using LXD, verifying the package end-to-end. A typical run of the test would be `./test.sh --debs-dir=build-area --image=ubuntu:resolute --pkg-version=2.17.58+dfsg-0ubuntu2` script: https://bugs.launchpad.net/ubuntu/+source/lustre/+bug/2169885/+attachment/6006954/+files/test.sh - Execution logs: - https://bugs.launchpad.net/ubuntu/+source/lustre/+bug/2169885/+attachment/6007266/+files/test.log + Execution logs: + https://bugs.launchpad.net/ubuntu/+source/lustre/+bug/2169885/+attachment/6007266/+files/test.log [ Where problems could occur ] * No existing users in resolute can regress since nothing is published there today; the real risks are: * The DKMS package failing to compile against an older kernel. * Build/NEW-queue issues. * The ongoing maintenance commitment for the release's lifetime. [ Other Info ] * This is a new package for the release, with support for amd64+arm64 only. The reason for using an SRU instead of the "backport" pocket is because we plan on compiling and signing the kernel modules compiled - by the `lustre-dkms` package, and bundle those with the kernel-shipped modules. + by the `lustre-dkms` package, and bundle those with `linux-main-modules`.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2169885 Title: Please backport lustre 2.17.58+dfsg-0ubuntu2 from stonking to resolute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lustre/+bug/2169885/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
