Licencing RHEL in Azure
Has anyone got any first hand experience here they can share as we here begin our journey to the cloud?
I am looking at flexible ways to licence RHEL for instances in Azure. I have two options available to me at present
1. Add RHEL to my Azure subscription - the costs here vary depending on the VM Instance type but I have the flexibility to switch the VM off when not in use, to fire up additional VMs during increased demands on capacity. However, for stable workloads this can prove rather costly
2. BYOL. I can buy RHEL Server (Physical and Virtual nodes) which entitles me to licence two VMs. I cannot find anything that limits the size of the VM or suggests whether the VMs have to reside on premises or can be on public cloud infrastructure.
What I am after is a simple to measure, cost-effective purchasing model that allows for both the stable server environment plus allows for periods where capcity needs to be increased, generally for short periods. The only option that appears to fit this mold would be to use both models, using BYOL for long term Azure infrastucture and RHEL under subscription to cover addtional capacity demands. It's all a bit messy.
Has anyone else looked into this and come up with a simple model to determine the tipping point between each licence model and be able to track usage and compliance. Or perhaps you have negotiated a flexible licence midel with Red Hat, or with Microsoft, or with both?
Open Apr 24, 2017 - 03:40 AM
Red Hat, RHEL, Linux, Azure, cloud, BYOL