You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by "Jochim, Ingo" <In...@bitgroup.de> on 2017/09/05 07:48:10 UTC
Free capacity calculation within ACS
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
Re: Free capacity calculation within ACS
Posted by Rafael Weingärtner <ra...@gmail.com>.
If you are an enthusiast of ACS, you can take a look at:
> com.cloud.deploy.DeploymentPlanningManagerImpl.start()
>
and also at
> com.cloud.deploy.DeploymentPlanningManagerImpl.checkHostReservations()
>
to debug/understand the problem and the code that is supposed to remove the
"old" reservations.
On Tue, Sep 26, 2017 at 5:49 PM, Rafael Weingärtner <
rafaelweingartner@gmail.com> wrote:
> What version of ACS are you using?
>
> On Tue, Sep 26, 2017 at 5:44 PM, Jochim, Ingo <In...@bitgroup.de>
> wrote:
>
>> Hello Marc-Aurèle,
>>
>> we tested with the parameter host.reservation.release.period.
>> We didn't see any change in the free capacity after shutdown of machines.
>> Not even after this period.
>> Any idea why?
>>
>> Regards,
>> Ingo
>>
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Jochim, Ingo [mailto:Ingo.Jochim@bitgroup.de]
>> Gesendet: Mittwoch, 6. September 2017 09:56
>> An: 'users@cloudstack.apache.org' <us...@cloudstack.apache.org>
>> Betreff: AW: Free capacity calculation within ACS
>>
>> Many thanks. We will check.
>>
>> Regards,
>> Ingo
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Marc-Aurèle Brothier [mailto:marco@exoscale.ch]
>> Gesendet: Mittwoch, 6. September 2017 09:51
>> An: users@cloudstack.apache.org
>> Betreff: Re: Free capacity calculation within ACS
>>
>> Apparently in 4.2.0
>> https://github.com/apache/cloudstack/blob/f0dd5994b447a6097c
>> 52f405c7c7c54c76da9c16/setup/db/db/schema-410to420.sql
>>
>> On Wed, Sep 6, 2017 at 9:42 AM, Jochim, Ingo <In...@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:marco@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 <In...@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
>> > >
>> >
>>
>
>
>
> --
> Rafael Weingärtner
>
--
Rafael Weingärtner
Re: Free capacity calculation within ACS
Posted by Rafael Weingärtner <ra...@gmail.com>.
Ingo, I checked the code, and at first sight I did not see any bug or
problem that would cause this feature not to work.
Can you describe what you are doing, the configurations/settings, wht you
expect and what is happening.
On Tue, Sep 26, 2017 at 6:05 PM, Jochim, Ingo <In...@bitgroup.de>
wrote:
> Hello Rafael,
>
> we are running 4.10.
>
> Regards,
> Ingo
>
> -----Ursprüngliche Nachricht-----
> Von: Rafael Weingärtner [mailto:rafaelweingartner@gmail.com]
> Gesendet: Dienstag, 26. September 2017 22:49
> An: users@cloudstack.apache.org
> Betreff: Re: Free capacity calculation within ACS
>
> What version of ACS are you using?
>
> On Tue, Sep 26, 2017 at 5:44 PM, Jochim, Ingo <In...@bitgroup.de>
> wrote:
>
> > Hello Marc-Aurèle,
> >
> > we tested with the parameter host.reservation.release.period.
> > We didn't see any change in the free capacity after shutdown of machines.
> > Not even after this period.
> > Any idea why?
> >
> > Regards,
> > Ingo
> >
> >
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Jochim, Ingo [mailto:Ingo.Jochim@bitgroup.de]
> > Gesendet: Mittwoch, 6. September 2017 09:56
> > An: 'users@cloudstack.apache.org' <us...@cloudstack.apache.org>
> > Betreff: AW: Free capacity calculation within ACS
> >
> > Many thanks. We will check.
> >
> > Regards,
> > Ingo
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Marc-Aurèle Brothier [mailto:marco@exoscale.ch]
> > Gesendet: Mittwoch, 6. September 2017 09:51
> > An: users@cloudstack.apache.org
> > Betreff: Re: Free capacity calculation within ACS
> >
> > Apparently in 4.2.0
> > https://github.com/apache/cloudstack/blob/f0dd5994b447a6097c52f405c7c7
> > c5 4c76da9c16/setup/db/db/schema-410to420.sql
> >
> > On Wed, Sep 6, 2017 at 9:42 AM, Jochim, Ingo <In...@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:marco@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
> > > <In...@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
> > > >
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>
--
Rafael Weingärtner
AW: Free capacity calculation within ACS
Posted by "Jochim, Ingo" <In...@bitgroup.de>.
Hello Rafael,
we are running 4.10.
Regards,
Ingo
-----Ursprüngliche Nachricht-----
Von: Rafael Weingärtner [mailto:rafaelweingartner@gmail.com]
Gesendet: Dienstag, 26. September 2017 22:49
An: users@cloudstack.apache.org
Betreff: Re: Free capacity calculation within ACS
What version of ACS are you using?
On Tue, Sep 26, 2017 at 5:44 PM, Jochim, Ingo <In...@bitgroup.de>
wrote:
> Hello Marc-Aurèle,
>
> we tested with the parameter host.reservation.release.period.
> We didn't see any change in the free capacity after shutdown of machines.
> Not even after this period.
> Any idea why?
>
> Regards,
> Ingo
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Jochim, Ingo [mailto:Ingo.Jochim@bitgroup.de]
> Gesendet: Mittwoch, 6. September 2017 09:56
> An: 'users@cloudstack.apache.org' <us...@cloudstack.apache.org>
> Betreff: AW: Free capacity calculation within ACS
>
> Many thanks. We will check.
>
> Regards,
> Ingo
>
> -----Ursprüngliche Nachricht-----
> Von: Marc-Aurèle Brothier [mailto:marco@exoscale.ch]
> Gesendet: Mittwoch, 6. September 2017 09:51
> An: users@cloudstack.apache.org
> Betreff: Re: Free capacity calculation within ACS
>
> Apparently in 4.2.0
> https://github.com/apache/cloudstack/blob/f0dd5994b447a6097c52f405c7c7
> c5 4c76da9c16/setup/db/db/schema-410to420.sql
>
> On Wed, Sep 6, 2017 at 9:42 AM, Jochim, Ingo <In...@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:marco@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
> > <In...@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
> > >
> >
>
--
Rafael Weingärtner
Re: Free capacity calculation within ACS
Posted by Rafael Weingärtner <ra...@gmail.com>.
What version of ACS are you using?
On Tue, Sep 26, 2017 at 5:44 PM, Jochim, Ingo <In...@bitgroup.de>
wrote:
> Hello Marc-Aurèle,
>
> we tested with the parameter host.reservation.release.period.
> We didn't see any change in the free capacity after shutdown of machines.
> Not even after this period.
> Any idea why?
>
> Regards,
> Ingo
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Jochim, Ingo [mailto:Ingo.Jochim@bitgroup.de]
> Gesendet: Mittwoch, 6. September 2017 09:56
> An: 'users@cloudstack.apache.org' <us...@cloudstack.apache.org>
> Betreff: AW: Free capacity calculation within ACS
>
> Many thanks. We will check.
>
> Regards,
> Ingo
>
> -----Ursprüngliche Nachricht-----
> Von: Marc-Aurèle Brothier [mailto:marco@exoscale.ch]
> Gesendet: Mittwoch, 6. September 2017 09:51
> An: users@cloudstack.apache.org
> Betreff: Re: Free capacity calculation within ACS
>
> Apparently in 4.2.0
> https://github.com/apache/cloudstack/blob/f0dd5994b447a6097c52f405c7c7c5
> 4c76da9c16/setup/db/db/schema-410to420.sql
>
> On Wed, Sep 6, 2017 at 9:42 AM, Jochim, Ingo <In...@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:marco@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 <In...@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
> > >
> >
>
--
Rafael Weingärtner
Re: Free capacity calculation within ACS
Posted by Marc-Aurèle Brothier <ma...@exoscale.ch>.
What was the value you had for host.reservation.release.period before
changing? Did you restart the management server after changing the value?
I can only see this option to create an issue. Check in the logs when you
tried to create a new VM the capacity values that the mgmt server holds, or
the value stored in the DB in "op_host_capacity".
On Wed, Sep 27, 2017 at 11:34 PM, Jochim, Ingo <In...@bitgroup.de>
wrote:
> It's not about deleted VM's. It's about VM's in shutdown mode.
> We do have customers which keep some demo or testing machines in off mode
> over a long period.
> Off machines will not free up capacity. In the end I cannot build new
> machines even if there is enough space on the hypervisors.
>
> Regards,
> Ingo
> ________________________________________
> Von: Marc-Aurèle Brothier [marco@exoscale.ch]
> Gesendet: Mittwoch, 27. September 2017 14:22
> An: users@cloudstack.apache.org
> Betreff: Re: Free capacity calculation within ACS
>
> What do you see in the table vm_instance for the VMs you were expecting a
> release? Do they stay in Destroyed state only and are not moving to
> "Expunging" state? What do you see in the logs related to the thread named
> "UserVm-Scavenger". This is the one which should do the VM cleanup. What do
> you have in the logs related to CapacityManagerImpl class?
>
> Kind regards,
> Marc-Aurèle
>
>
>
> > On 26 Sep 2017, at 22:44, Jochim, Ingo <In...@bitgroup.de> wrote:
> >
> > Hello Marc-Aurèle,
> >
> > we tested with the parameter host.reservation.release.period.
> > We didn't see any change in the free capacity after shutdown of
> machines. Not even after this period.
> > Any idea why?
> >
> > Regards,
> > Ingo
> >
> >
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Jochim, Ingo [mailto:Ingo.Jochim@bitgroup.de]
> > Gesendet: Mittwoch, 6. September 2017 09:56
> > An: 'users@cloudstack.apache.org' <us...@cloudstack.apache.org>
> > Betreff: AW: Free capacity calculation within ACS
> >
> > Many thanks. We will check.
> >
> > Regards,
> > Ingo
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Marc-Aurèle Brothier [mailto:marco@exoscale.ch]
> > Gesendet: Mittwoch, 6. September 2017 09:51
> > An: users@cloudstack.apache.org
> > Betreff: Re: Free capacity calculation within ACS
> >
> > Apparently in 4.2.0
> > https://github.com/apache/cloudstack/blob/f0dd5994b447a6097c52f405c7c7c5
> 4c76da9c16/setup/db/db/schema-410to420.sql
> >
> > On Wed, Sep 6, 2017 at 9:42 AM, Jochim, Ingo <In...@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:marco@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 <In...@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
> >>>
> >>
>
>
AW: Free capacity calculation within ACS
Posted by "Jochim, Ingo" <In...@bitgroup.de>.
It's not about deleted VM's. It's about VM's in shutdown mode.
We do have customers which keep some demo or testing machines in off mode over a long period.
Off machines will not free up capacity. In the end I cannot build new machines even if there is enough space on the hypervisors.
Regards,
Ingo
________________________________________
Von: Marc-Aurèle Brothier [marco@exoscale.ch]
Gesendet: Mittwoch, 27. September 2017 14:22
An: users@cloudstack.apache.org
Betreff: Re: Free capacity calculation within ACS
What do you see in the table vm_instance for the VMs you were expecting a release? Do they stay in Destroyed state only and are not moving to "Expunging" state? What do you see in the logs related to the thread named "UserVm-Scavenger". This is the one which should do the VM cleanup. What do you have in the logs related to CapacityManagerImpl class?
Kind regards,
Marc-Aurèle
> On 26 Sep 2017, at 22:44, Jochim, Ingo <In...@bitgroup.de> wrote:
>
> Hello Marc-Aurèle,
>
> we tested with the parameter host.reservation.release.period.
> We didn't see any change in the free capacity after shutdown of machines. Not even after this period.
> Any idea why?
>
> Regards,
> Ingo
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Jochim, Ingo [mailto:Ingo.Jochim@bitgroup.de]
> Gesendet: Mittwoch, 6. September 2017 09:56
> An: 'users@cloudstack.apache.org' <us...@cloudstack.apache.org>
> Betreff: AW: Free capacity calculation within ACS
>
> Many thanks. We will check.
>
> Regards,
> Ingo
>
> -----Ursprüngliche Nachricht-----
> Von: Marc-Aurèle Brothier [mailto:marco@exoscale.ch]
> Gesendet: Mittwoch, 6. September 2017 09:51
> An: users@cloudstack.apache.org
> Betreff: Re: Free capacity calculation within ACS
>
> 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 <In...@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:marco@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 <In...@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
>>>
>>
Re: Free capacity calculation within ACS
Posted by Marc-Aurèle Brothier <ma...@exoscale.ch>.
What do you see in the table vm_instance for the VMs you were expecting a release? Do they stay in Destroyed state only and are not moving to "Expunging" state? What do you see in the logs related to the thread named "UserVm-Scavenger". This is the one which should do the VM cleanup. What do you have in the logs related to CapacityManagerImpl class?
Kind regards,
Marc-Aurèle
> On 26 Sep 2017, at 22:44, Jochim, Ingo <In...@bitgroup.de> wrote:
>
> Hello Marc-Aurèle,
>
> we tested with the parameter host.reservation.release.period.
> We didn't see any change in the free capacity after shutdown of machines. Not even after this period.
> Any idea why?
>
> Regards,
> Ingo
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Jochim, Ingo [mailto:Ingo.Jochim@bitgroup.de]
> Gesendet: Mittwoch, 6. September 2017 09:56
> An: 'users@cloudstack.apache.org' <us...@cloudstack.apache.org>
> Betreff: AW: Free capacity calculation within ACS
>
> Many thanks. We will check.
>
> Regards,
> Ingo
>
> -----Ursprüngliche Nachricht-----
> Von: Marc-Aurèle Brothier [mailto:marco@exoscale.ch]
> Gesendet: Mittwoch, 6. September 2017 09:51
> An: users@cloudstack.apache.org
> Betreff: Re: Free capacity calculation within ACS
>
> 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 <In...@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:marco@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 <In...@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
>>>
>>
AW: Free capacity calculation within ACS
Posted by "Jochim, Ingo" <In...@bitgroup.de>.
Hello Marc-Aurèle,
we tested with the parameter host.reservation.release.period.
We didn't see any change in the free capacity after shutdown of machines. Not even after this period.
Any idea why?
Regards,
Ingo
-----Ursprüngliche Nachricht-----
Von: Jochim, Ingo [mailto:Ingo.Jochim@bitgroup.de]
Gesendet: Mittwoch, 6. September 2017 09:56
An: 'users@cloudstack.apache.org' <us...@cloudstack.apache.org>
Betreff: AW: Free capacity calculation within ACS
Many thanks. We will check.
Regards,
Ingo
-----Ursprüngliche Nachricht-----
Von: Marc-Aurèle Brothier [mailto:marco@exoscale.ch]
Gesendet: Mittwoch, 6. September 2017 09:51
An: users@cloudstack.apache.org
Betreff: Re: Free capacity calculation within ACS
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 <In...@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:marco@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 <In...@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
> >
>
AW: Free capacity calculation within ACS
Posted by "Jochim, Ingo" <In...@bitgroup.de>.
Many thanks. We will check.
Regards,
Ingo
-----Ursprüngliche Nachricht-----
Von: Marc-Aurèle Brothier [mailto:marco@exoscale.ch]
Gesendet: Mittwoch, 6. September 2017 09:51
An: users@cloudstack.apache.org
Betreff: Re: Free capacity calculation within ACS
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 <In...@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:marco@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 <In...@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
> >
>
Re: Free capacity calculation within ACS
Posted by Marc-Aurèle Brothier <ma...@exoscale.ch>.
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 <In...@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:marco@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 <In...@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
> >
>
AW: Free capacity calculation within ACS
Posted by "Jochim, Ingo" <In...@bitgroup.de>.
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:marco@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 <In...@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
>
Re: Free capacity calculation within ACS
Posted by Marc-Aurèle Brothier <ma...@exoscale.ch>.
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 <In...@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
>
AW: Free capacity calculation within ACS
Posted by "Jochim, Ingo" <In...@bitgroup.de>.
Hello Swen,
so you mean changing/removing the host tag for the unused machines?
That might be a good idea since with our workaround with offering zero we have to remember the original size.
I thought there might be a parameter (ideally global settings or so) to change the behavior of the capacity calculation.
Thanks.
Ingo
-----Ursprüngliche Nachricht-----
Von: S. Brüseke - proIO GmbH [mailto:s.brueseke@proio.com]
Gesendet: Dienstag, 5. September 2017 10:03
An: users@cloudstack.apache.org
Cc: Jochim, Ingo <In...@bitgroup.de>
Betreff: AW: Free capacity calculation within ACS
Hi Ingo,
did you try to work with host tags? I am not sure if this will solve it, but it is worth a try.
Mit freundlichen Grüßen / With kind regards,
Swen
-----Ursprüngliche Nachricht-----
Von: Jochim, Ingo [mailto:Ingo.Jochim@bitgroup.de]
Gesendet: Dienstag, 5. September 2017 09:48
An: users@cloudstack.apache.org
Betreff: Free capacity calculation within ACS
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
- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main
USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
AW: Free capacity calculation within ACS
Posted by "S. Brüseke - proIO GmbH" <s....@proio.com>.
Hi Ingo,
did you try to work with host tags? I am not sure if this will solve it, but it is worth a try.
Mit freundlichen Grüßen / With kind regards,
Swen
-----Ursprüngliche Nachricht-----
Von: Jochim, Ingo [mailto:Ingo.Jochim@bitgroup.de]
Gesendet: Dienstag, 5. September 2017 09:48
An: users@cloudstack.apache.org
Betreff: Free capacity calculation within ACS
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
- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main
USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error) please notify
the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.