ECOPROJECT-3416 | feat: Baremetal cost prediction #251
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR add a cost estimation for baremetal self managed OCP/OVE.
The user can see the estimation when he click the
cost estimationbutton on the overview of report page.The calculation is based on:
https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide
We predefine vCPU for calc based on vCenter VMs. We let user define the Node HW, we can pre-define it, but it's hard as each node could be different.
We also offer user to define OCP/OVE or SLA.
Example calculation:
A user has 4000vCPU on vCenter with ratio 1:4, it’s 1000cores. Bare metal node has 2sockets with 32cores. 1000cores/64cores=16 servers. We would suggest 16*1.25=20 nodes. We would calculate the price for 20 OpenShift Virtualization Engine bare metal socket-pair subscriptions.This calculation takes into account
Bare metal socket-pair subscription.More info: https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide#section-4
Current solution don't take into account
core-pair subscription model. We may provide it as an option in future.