Apparently in 4.2.0 https://github.com/apache/cloudstack/blob/f0dd5994b447a6097c52f405c7c7c54c76da9c16/setup/db/db/schema-410to420.sql
On Wed, Sep 6, 2017 at 9:42 AM, Jochim, Ingo <ingo.joc...@bitgroup.de> wrote: > Hello Marc-Aurèle, > > great. Didn't know that this parameter exists. > Do you know in which ACS version this got introduced? > > Many thanks. > Ingo > > -----Ursprüngliche Nachricht----- > Von: Marc-Aurèle Brothier [mailto:ma...@exoscale.ch] > Gesendet: Mittwoch, 6. September 2017 09:15 > An: users@cloudstack.apache.org > Betreff: Re: Free capacity calculation within ACS > > Hi Ingo, > > You might want to look at the release period set in your installation: > host.reservation.release.period. This release window time is there to > keep the capacity of stopped machines on a host for a certain time, before > releasing it, in case the machine has to start again soon after. And most > likely for other reason maybe in the advance networking mode. So try to > decrease this time window and check your capacity after that. > > Marc-Aurèle > > On Tue, Sep 5, 2017 at 9:48 AM, Jochim, Ingo <ingo.joc...@bitgroup.de> > wrote: > > > Hello all, > > > > within our CloudStack environment we like to park a couple of large > > machines in powered off state. > > Those machines are demo machines which are needed only sometimes. > > Those machines will get included in the capacity. That means we cannot > > build new machines even if there are free ressources on the hypervisors. > > We don't want to solve it with overcommitment. > > Is there a possibility to calculate free capacity without all powered > > off machines? > > > > Currently we have a dirty workaround. We created an offering with 1 > > core and 1MB RAM and used that for all parked machines. > > But this is not very nice. > > > > Any ideas or comments are welcome. > > Thank you. > > Ingo > > >
