> >
> >
> Regards.> >
> >
> > >
> From: David Jumani > >
> Sent: Monday, April 5, 2021 09:08> >
> To: dev@cloudstack.apache.org ;
us...@cloudstack.apache.org > >
> Subject: Re: Overprovisioning consideration in
umani
Sent: Monday, April 5, 2021 09:08
To: dev@cloudstack.apache.org ;
us...@cloudstack.apache.org
Subject: Re: Overprovisioning consideration in metrics API response
+1 on this. Allocated should consider overprovisioning!
From: Rohit Yadav
Sent: Wednesday, March 31
+1 on this. Allocated should consider overprovisioning!
From: Rohit Yadav
Sent: Wednesday, March 31, 2021 3:30 PM
To: dev@cloudstack.apache.org ;
us...@cloudstack.apache.org
Subject: Re: Overprovisioning consideration in metrics API response
Thanks for starting
Thanks for starting this thread Abhishek. I think all 'allocated' API response
keys (irrespective of type such as CPU, RAM, storage/disk etc) across all
list/metrics APIs should consider overprovisioning factor.
For example, if the total resource value/limit is 100 and overprovisioning
factor i
