Livepatch on-prem patch storage

Security Livepatch
1

Livepatch server supports several different drivers for storing patch files downloaded from livepatch.canonical.com:

  1. Local filesystem
  2. Swift
  3. S3 (and compatible implementations, e.g. minio)
  4. Postgresql

The filesystem patch store is easiest to deploy and suits most configurations. However, if there is a need to scale out the livepatch server such as have multiple livepatch servers running to handle the load, the filesystem patch store should not be used.

In case there is a need to scale out livepatch on-prem, use the s3, postgresql or swift patch stores. Any patch store should have enough space for storing livepatches - currently at least 45GB for all patches, see this guide to filter patches sent to your on-prem instance to specific kernel variants/architectures and lower this requirement.

See the patch storage config for all available parameters.

1 Like
4

The current 15GB size requirement is misleading.

I deployed a livepatch on-prem server yesterday and it currently stands at 37GB:

$ du -sh /livepatch/
37G /livepatch/

Let’s update that.

Thanks,
Alan

1 Like
5

@alanbach Thanks for the note. I’ve updated it to 45GB and included a link to another page we have on how to setup patch sync filters to reduce this requirement.

1 Like
6

Thank you so much for making the update and linking the guide.