This message was deleted.

Hi Maxime, we don’t have anything for this yet. We’re starting to discuss how we can build out a model for the community to write their own providers for different cloud vendors, so OpenStack could be done in this way.

Since pricing with openstack is provider dependent and to avoid cumbersome integration, would we consider integration with pricing provided via a CSV or similar?

This is interesting. Do you have any thoughts of how the pricing would be listed in the CSV?

From what I know about the openstack implementation used in my company, billing is done in flavour, with obviously different names, and depending on whether the host is dedicated or not, same thing for reservation. We also have network costs billed in a particular way, and specific billing for managed Kubernetes. So the user could provide a json to parse (I didn't realize how complex it was, so I double-checked the rates used internally, and it seems easier to parse than a csv):, which would be taken in parameters like that: Storage ( Price per Go) SFS: (price) S3:: (the price) Compute: Reserved instances: Flavor 1: : (price) Flavor xxxxx: : (price) Normal instances: Flavor 1: : (price) Flavor xxxxx: : (price) Database: PostgreSQL: Flavor 1: : (price) Flavor xxxxx: : (price) mysql/MariaDB: Flavor 1: : (price) Flavor xxxxx: : (price) Network: (price per go) Input (price) Output (price)

That’s cool! Thanks for the details. Would you be okay to add this example to the https://github.com/infracost/infracost/issues/616 issue (so we don’t lose track of it)? For k8s, do you bill per GB and CPU each pod uses?

yes, of course ! for k8s, it is charged by the number of clusters managed, and then by flavors as normal ecs

Ah okay, do you charge for network in k8s as well?

The billing for the network for kubernetes is done the same way as for the instances (so price per Go for outgoing traffic)

Great, thanks that’s useful to know 🙏