We’re using a combination of cASO (https://caso.readthedocs.io/en/stable/) and
some low level libvirt fabric monitoring. The showback accounting reports are
generated with merging with other compute/storage usage across various systems
(HTCondor, SLURM, ...)
It would seem that those who needed solutions in the past found they had to do
them themselves. It would be interesting if there are references of usage
data/accounting/chargeback at scale with the current project set but doing the
re-evaluation would be an effort which would need to be balanced versus just
keeping the local solution working.
Tim
-----Original Message-----
From: Lars Kellogg-Stedman <l...@redhat.com>
Date: Wednesday, 14 March 2018 at 17:15
To: openstack-operators <openstack-operators@lists.openstack.org>
Subject: Re: [Openstack-operators] How are you handling billing/chargeback?
On Mon, Mar 12, 2018 at 03:21:13PM -0400, Lars Kellogg-Stedman wrote:
> I'm curious what folks out there are using for chargeback/billing in
> your OpenStack environment.
So far it looks like everyone is using a homegrown solution. Is
anyone using an existing product/project?
--
Lars Kellogg-Stedman <l...@redhat.com> | larsks @ {irc,twitter,github}
http://blog.oddbit.com/ |
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
