license@jndata.dk asked a question.
Is there any who can advise on this topic. Red hat Openshift License count in Flexera One
The Red Hat policy surrounding OpenShift subscriptions is somewhat ambiguous, particularly in the Self-managed Red Hat OpenShift subscription guide. It mentions two licensing options: pairing physical cores as the license unit or using 4 vCPUs as the license unit. My primary concern lies in understanding if there is a specified overallocation ratio between physical cores and vCPUs. Specifically, can the overallocation ratio exceed 2:1, meaning for every 4 vCPUs, should there be 2 physical cores secured? Alternatively, is it permissible that the number of VMs and vCPUs on a host be unlimited?
It would be incredibly helpful to know how Flexera recommends calculating licensing counts for their customers in such scenarios”
@license@jndata.dk
I agree that the Self‑managed Red Hat OpenShift Subscription Guide can feel ambiguous if you read it through a traditional virtualization‑licensing lens. To my knowledge there's no required overallocation ratio in Red Hat OpenShift licensing, i.e., my interpretation is that:
I think that there's a need for a combination of intelligent allocation rules, point rule sets, etc. to enable Flexera One ITAM to facilitate the Red Hat OpenShift use cases. Do you have SKUs to enter, and do they properly represent your product use rights after having been processed? And then, it's a matter of getting this reconciled properly against the technical inventory?
Thanks,
John Sorensen