-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On-Premises Pricing - Further clarifications would be really nice #90
Comments
I'm traveling this week but I'll get some docs cleaned up around this when I have access to my home cluster. Related issues and examples: |
#93 updated the website at https://www.opencost.io/docs/on-prem#custom-pricing-using-the-opencost-helm-chart I was able to update my aws.json and my default.json, I'll think about refactoring this page to make it a bit clearer what our options are. @daniwk What would you like to see? |
opencost/opencost#1756 is related. I was able to override my AWS spot pricing |
Sorry, for getting back to you so late. After some work with OpenCost I was finally able to load our pricing model to OpenCost and tag nodes with different price SKUs. This required a bit investigation in the source code, OpenCost docs and KubeCost docs. In retrospect, I think it would be helpful for new users if the docs outline, as you say, what the different options are:
I'd be happy to contribute here. |
@daniwk we'd love to have additional documentation on this. Please let me know how I can help you out! |
Hi @daniwk, thanks for the sharing on this. I do have a quick question on CPU and RAM cost section. From what I read in the code, the ratio could only be derived through CPU and RAM section in the |
That's correct, @lordofire. Or to be more precise: I arrived at the same conclusion after searching through the code and docs. I haven't found a way to adjust this ratio on a per SKU basis though. We are mostly concerned with the total node cost, and not the specific CPU and RAM costs, but I guess you could look at your procurement data and infer the CPU and RAM ratio from that. |
Hi @daniwk , thanks for sharing! Could you please help explain how do you derive the ratio of cpu/memory unit price in your situation? In our on-prem DC, we do have some memory optimized instances (which means bigger memory, and less unit cost for per GB memory), so how to determine that will be a problem for us to proceed further. Also, it would be great if you could explain how do you only measure the total node cost without the specific CPU/RAM cost. In my situation, my goal of using opencost is to have a single metric to evaluate our usage cost vs TCO. |
Sorry for getting back to you so late. In short, we skipped the entire "try to find the ratio of cpu/memory unit price" because we have a lot of different SKUs and the ratio will depend on what SKU you choose. AFAIK, OpenCost doesn't support SKU specific cpu/memory ratio. When it comes to assigning total node cost it seems we're in a different situation. I work in a cloud company offering compute and managed services. We therefore have a price sheet containing what each compute specification will cost so we're simply assigning these prices to the different nodes (through the Custom CSV provider). |
I'm marking this as complete with #159 |
The guide for providing pricing for on-promises pricing is unclear for newcomers to OpenCost. It would be really helpful and a timesaver if the guide contained a section where it's stated and shown how the custom pricing (
default.json
) is mounted to theopencost
container in the deployment config.Let me know you'd like me to create a PR where I give it go.
The text was updated successfully, but these errors were encountered: