New track request for canonical-livepatch

store-requests
1

Hi,

Please could a track “bare” be created for the canonical-livepatch Snap?

Existing tracks are core-core22 in what was an effort to provide targeted builds for various Ubuntu releases but we are looking to migrate to the bare base to simplify those efforts.

Thanks.

2

Hi, @review-team Can we get a look at this?

Thanks

3

Hi,

Can you explain a bit the rationale behind this change? How do you envision handling the cases where e.g. a different build of canonical-livepatch will be required for different bases? Also, could any of the @reviewers chime in here?

Thanks,

Odysseus

4

Hi @odysseus-k,

I’m not sure what you mean by your example. But to elaborate, there was a discussion a few years ago on the Livepatch client repo here about whether it was possible to build the Livepatch Client Snap on different bases to improve the boot time of cloud instances running Ubuntu Pro. In the ideal case the cloud image would install the Livepatch Snap using a base that was already pre-seeded in the image, in the worst case it would download a non-seeded base and increase the boot time.

To alleviate this problem the Snap can simply be built on the bare base (the build-base would still be the latest base i.e. core22 to get the latest snapcraft features). Now installation of the Snap will always be speedy because the bare base is a very minimal set of files and we don’t need to keep the overhead of maintaining multiple bases.

To add an extra caveat on the above, although the work was done to build the Snap on all the bases, it seems the Ubuntu Pro client defaults to installing from latest/stable making the benefit of multiple bases moot. But in any case, moving to the bare base has tangible benefits.

Hope that makes sense.

5

Hi,

Just bumping this @verterok @odysseus-k @review-team

Thank you.

6

Hi,

Thanks for the explanation. It makes sense to me. +1 from me as a reviewer and the bare track is now created.

Thanks,

Odysseus