'capacity.skipcounting.hours' is used to determine how low after a VM is
stopped its resources are released, i.e. not counted to its host's used
capacity. This is not directly related to 'capacity.check.period' afaict.
On Wed, Oct 4, 2023 at 9:28 AM Loth wrote:
> Hello,
>
> Thanks for the quick
Hello,
Thanks for the quick response. according to
https://bitworks.software/2018-08-23-cloudstack-global-variables-atlas-system.html
(not sure if accurate) capacity.check.period is interlinked with
capacity.skipcounting.hours. If I disable capacity.skipcounting.hours
(set to 0) does it not matter
Loth,
reading the code and simplifying it in my head;
- the 'capacity.check.period' is the interval between capacity checks (from
an operator perspective) and
- the 'resourcecount.check.interval' is the interval to check for usage
from a project/account/domain perspective.
On Tue, Oct 3, 2023 at 1
Hello Users,
What is the difference between 'capacity.check.period' and
'resourcecount.check.interval'? I've read that capacity.check.period
is somehow related to capacity.skipcounting.hours but not sure how up
to date my source is.
Thanks!
