Hello, Murilo
There were several improvements on the Quota plugin in 4.18 (and there
are some more to come). One of them was enabling operators to write
rules to determine in which context the tariff will be applied; along
with that, the vCPU, CPU_SPEED, and MEMORY tariffs were converted to
RUNNING_VM tariffs with respective activation rules (it supports ES 5.1
on the JavaSript scripts). You can check issue #5891 [1] and PR #5909
[2] for more information. You can also check this video [3] on YouTube
to get an overview of the new features yet to be ported to the community
(though you probably will need to use the automatic subtitles generator).
Unfortunately, we did not have time to put effort into the official
documentation adjustments, but it is in the roadmap.
If you have any doubt about how it works or any improvement suggestion,
just let us know.
Best regards,
Daniel Salvador (gutoveronezi)
[1] https://github.com/apache/cloudstack/issues/5891
[2] https://github.com/apache/cloudstack/pull/5909
[3]
https://www.youtube.com/watch?v=3tGhrzuxaOw&pp=ygUQcXVvdGEgY2xvdWRzdGFjaw%3D%3D
On 11/3/23 02:16, Murilo Moura wrote:
Guys, is the quota tariff plugin still in development?
I ask because in version 4.18 I've noticed that the memory tariff, for
example, isn't being calculated or saved in the cloud_usage table, in
addition to the error that appears when trying to update a tariff (Unable
to execute API command quotatariffupdate due to missing parameter name).
