On Sat, Jan 30, 2021 at 2:49 PM Gena Makhomed <gmm at csdoc.com> wrote: > On 29.01.2021 21:06, redbaronbrowser via CentOS-devel wrote: > >> Developer Subscriptions allowed to use for production workloads > >> only by individuals, and totally forbidden to use by companies? > > Listen to the Ask Noah show interview with Bex because that explains things better. > Sorry, but I can't. Because English is not my native language. > Written English I can read, but spoken English is just > a bunch of sounds for me - I can't understand it. > >> 350 USD/year RHEL is forbidden to use for virtual machines. > > If you are using something else as the hypervisor then you can use the RHEL license > > My understanding is if you purchased only a single $350 license you can use it for being a HV or a VM but not both. > Look at the page > https://www.redhat.com/en/store/red-hat-enterprise-linux-server > 350 USD/year Red Hat subscription described as: > "Can only be deployed on physical systems". > I understand these words as "forbidden to use inside virtual machines". The $800 "Standard Server" license - I believe this is the one that supports either 1 physical, or 2 VM... which helps a bit if you are calculating cost. It brings down the per-VM cost to $400, and at scale a small discount might apply... perhaps $350 USD/year after discount. But, if you need EUS - then it increases again as an optional add-on cost, so back up to $475+ USD/year per VM. You may be able to negotiate for the $2500 "Red Hat Enterprise Linux for Virtual Datacenters" license to cover your whole physical host, whether or not you are running a certified hypervisor or container technology. Lots of fine print around what support would look like in such a scenario, but you may be able to pitch it. Once you add it all up, it still ends up being a problem at scale. For smaller deployments - it's fine. It is the break-even point where you have to have your own support + development stuff anyways, that the proposition really starts to break down. -- Mark Mielke <mark.mielke at gmail.com>