Livepatch latest kernel support is for
Ubuntu 22.04 LTS 64-bit x86 6.5 (HWE)
I am using
Ubuntu Noble Numbat (development branch) Linux 6.8.0-11-generic
When will 24.04 LTS get Livepatch support?
Most likely when it turns into an actual LTS with its .1 release…
But also surely not before the actual release date.
Thank you Lech! One more if I may, if I have 10 vsphere hosts running say like 200 ubuntu vm’s of compatible versions. Then the 10 physical licenses cover all of those?
I encountered an issue recently where we purchased what I thought was 10 vmhost/physical licenses which actually turned out to be 10 individual vm licenses. It’s a very long and drawn out ordeal. Suffice to say the waters being so murky with what exactly to buy and then exactly how to employ licenses to cover my situation. I felt it best to shotgun the question out (so to speak).
Is there any documentation and information how Ubuntu Pro works with selfhosted Landscape server? We have both servers that have internet access and those that does not. Our goal is to have our selfhosted landscape server to handle all the ubuntu repos, pro repos and the pro licens reporting, so we dont need any proxy/internet access for the servers, only access to our selfhosted landscape server that have internet access, is this a possible senario?
Hi,
what if I need to enable Ubuntu Pro on multiple VMs with Ubuntu Server on an IaaS environment (VMware based, but not a Public Cloud) where I don’t have any control on the nodes (and there are a lot)?
I cannot for sure buy a node license for each node managed by my cloud provider…
And I only have visibility of my VMs and I cannot specify any rule to bind those VMs to a bunch of specific nodes.
Is it possible to buy licenses per single VMs?
Thanks
yes, that’s correct. 10 physical licenses would cover your 200 vms. Just remember to cover all physical machines in your environment, to be compliant. so if you have 10 vsphere hosts you need 10 Ubuntu Pro subscriptions. If you have 20, then you need 20, etc.
yes, pls contact our sales team, and they will be able to help you out.
https://ubuntu.com/contact-us/form?product=pro
Livepatch security coverage is available as soon as an Ubuntu LTS is generally available, so that includes day 1 of the Ubuntu LTS release, until the LTS goes end-of-life (EOL). Livepatch will cover the machine for the 5 years of standard support, and also through the expanded security maintenance (ESM) window which is 12 years, or more.
Any nuance around Livepatch coverage revolves around ensuring kernel updates are applied every 9 (for HWE kernels) to 13 months (for GA kernels), because Livepatch doesn’t allow you to defer rebooting for 12 years. Applying a kernel update means upgrading the kernel package, and rebooting the machine.
Lech, Continued thanks. One more if I may; “All physical machines in your environment”
Logically this should mean only those that either, you wish to manage with Ubuntu Pro, or in a virtualized environment only those hypervisor hosts that contains vm’s you want to manage with Ubuntu Pro.
Can you help me understand which is correct?
hi @benh - according to the Ubuntu Pro Service Terms you should cover “all Ubuntu systems within an environment”. So, for example, if your service on production is using 3 physical servers, then you need 3 licenses, not 1. Otherwise you would not be covering the whole environment
Hope this clarifies?
Continued thanks Lech. So it really doesn’t help, unless I’m being incredibly dense. So I’m wanting to purchase U Pro coverage for all Ubuntu VM’s hosted on 10 vsphere hosts. Now is this every Ubuntu system in our environment? Nope, but it is all of them on 10 of our 20 hypervisor hosts. I get the feeling that this is not a supported scenario? Also it’s SUPER hard to get any information (other than thru you) when all mention of ‘supported-hypervisors’ was removed from the related U Pro docs back in Dec 2023. In additions we’ve been ghosted by both an assigned account rep as well as a sales guy I tried contacting via the Ubuntu Pro website.
There’s more to this story than just that, but suffice to say we’ve been trying to buy the correct license since Nov 2023.
uh, I am really sorry to hear that, @benh .
if you have 20 hosts running Ubuntu VMs in your environment then, indeed, 10 Ubuntu Pro physical subscriptions won’t cover that. but with 20 Ubuntu Pro subscriptions you cover the whole environment including all Ubuntu VMs running on top. If you have 10 physical hosts with Ubuntu VMs, and the other 10 hosts are not running any Ubuntu -then you would be fully covered with 10 subscriptions.
I would love to listen to the full story and I am happy to grant you 1 month free access to Ubuntu Pro. to get you started. Could you please reach out to me directly over email at lech.sandecki[at]canonical.com
Hi,
I am using Ubuntu Pro in my homelab using the “personal” license, which covers five “machines”. Now my question is, does this mean 5 Servers, each with unlimited VMs, or does this mean five VMs?
We are looking into running postgres databases with patroni and on unmanaged bare metal servers provided by dell or hpe for an in-house usecase. The combination of easily available mirrored ZFS + LXD with system container snapshots and support from a single vendor for the entire stack on a very mainstream distro would be a significant competitive advantage of ubuntu pro over other distros with enterprise support.
The main issue is that LXD relicensed to AGPL, which is prohibited by company policy (GPL or LGPL would have been far less of an issue), and makes it substantially harder to push for this stack to the point where pushing for it requires a lengthy explanation about licenses and forks instead of “this is a very mature open source tool with permissive licensing and first-class vendor support” much like when pushing for podman on red hat machines. So my question is:
- Does purchasing ubuntu pro include a permissive license for LXD?
- Alternatively, can we expect proper support for a stack that uses Incus instead of LXD if we have support for open source applications? Since it is a fork of a canonical project we’d expect institutional knowledge about it to be available.
- Also, is using the version of postgres from the official postgres repo and extensions from the timescaledb repo supported? Most likely we would do that in an LXD/Incus ubuntu container to facilitate testing before major version upgrades.
Hi @saolof,
On the LXD licencing question - we did not select AGPL to create fear and drive people to commercial licensing, we selected it to avoid fragmentation of the network API and protocol. So dual-licensing isn’t our goal or something we do regularly. At the same time, for companies that are partners or customers, we often give people a royalty-free source license if that makes their internal conversations easier (we understand some orgs have a historical aversion to AGPL). So yes, if you were embedding all of this into a product and using Ubuntu Pro we would do the same for you. That’s not a traditional permissive open source license, just a non-AGPL source available license for you, it wouldn’t allow your customers to treat the code as if it were theirs, only you. And our goal, again, would be to make sure that your API was the same as the standard API for LXD even if you modified it. Does that help?
On the timescaledb question, I believe we do support that scenario, please do reach out to me if you want to discuss it and I can connect you with the right people working with Postgres on our side.
3 Likes
If dual booting Ubuntu on two different SSDs on one PC count as one or two machines?
please note that I added a clarification
Ubuntu Pro is free for personal use. It offers the full suite of Ubuntu Pro capabilities for you – and any business you own – on up to 5 physical machines with unlimited VMs and/or containers you can run on top.
Hello
Sorry if this is the wrong place and to show my noobness
I had thought updates were automatic but logged in and seen some needed to be done,
incorrect assumption.
Is there something I can do to not have to keep an eye on the need for updates?
Thank you