[cloudkitty] Instances billing based on tags
Folks, We have an AWS project and in a single project we run multiple customers so for billing we use tags. In short every vm instance has a tag (customer name) and that way we can produce bills for each customer. Recently I am playing with openstack cloudkitty and it works with standard cases like project based billing. But does it support tags based billing just similar to what i have explained in the above aws example?
You can do that. Basically, you can start collecting those attributes you want for billing (e.g. tags) via Ceilometer dynamic pollster (that is the easiest way to achieve this). Then, you need to configure the resource type in Gnocchi to store this extra attribute, and of course, configure CloudKitty to collect/use it. Both in the metrics.yml and then in the hashmap or Pyscript rules. On Mon, Jan 2, 2023 at 11:01 PM Satish Patel <satish.txt@gmail.com> wrote:
Folks,
We have an AWS project and in a single project we run multiple customers so for billing we use tags. In short every vm instance has a tag (customer name) and that way we can produce bills for each customer.
Recently I am playing with openstack cloudkitty and it works with standard cases like project based billing. But does it support tags based billing just similar to what i have explained in the above aws example?
-- Rafael Weingärtner
Wow! very interesting, I will poke around and see how it's feasible. Very curious how it will represent that data in horizon UI. Currently I am seeing rates based on project_id so assuming it will show based on customer_id. correct? On Tue, Jan 3, 2023 at 8:13 AM Rafael Weingärtner < rafaelweingartner@gmail.com> wrote:
You can do that. Basically, you can start collecting those attributes you want for billing (e.g. tags) via Ceilometer dynamic pollster (that is the easiest way to achieve this). Then, you need to configure the resource type in Gnocchi to store this extra attribute, and of course, configure CloudKitty to collect/use it. Both in the metrics.yml and then in the hashmap or Pyscript rules.
On Mon, Jan 2, 2023 at 11:01 PM Satish Patel <satish.txt@gmail.com> wrote:
Folks,
We have an AWS project and in a single project we run multiple customers so for billing we use tags. In short every vm instance has a tag (customer name) and that way we can produce bills for each customer.
Recently I am playing with openstack cloudkitty and it works with standard cases like project based billing. But does it support tags based billing just similar to what i have explained in the above aws example?
-- Rafael Weingärtner
It is showing metrics based on the scope configured. I guess you have set the scopes to be mapped as project IDs. If you want other attribute to represent the scope, you need to change that in CloudKitty. On Tue, Jan 3, 2023 at 5:23 PM Satish Patel <satish.txt@gmail.com> wrote:
Wow! very interesting, I will poke around and see how it's feasible. Very curious how it will represent that data in horizon UI. Currently I am seeing rates based on project_id so assuming it will show based on customer_id. correct?
On Tue, Jan 3, 2023 at 8:13 AM Rafael Weingärtner < rafaelweingartner@gmail.com> wrote:
You can do that. Basically, you can start collecting those attributes you want for billing (e.g. tags) via Ceilometer dynamic pollster (that is the easiest way to achieve this). Then, you need to configure the resource type in Gnocchi to store this extra attribute, and of course, configure CloudKitty to collect/use it. Both in the metrics.yml and then in the hashmap or Pyscript rules.
On Mon, Jan 2, 2023 at 11:01 PM Satish Patel <satish.txt@gmail.com> wrote:
Folks,
We have an AWS project and in a single project we run multiple customers so for billing we use tags. In short every vm instance has a tag (customer name) and that way we can produce bills for each customer.
Recently I am playing with openstack cloudkitty and it works with standard cases like project based billing. But does it support tags based billing just similar to what i have explained in the above aws example?
-- Rafael Weingärtner
-- Rafael Weingärtner
participants (2)
-
Rafael Weingärtner
-
Satish Patel