You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Shaheedur Haque (shahhaqu)" <sh...@cisco.com> on 2015/04/10 06:27:12 UTC
Quotas and Stratos
Hi all,
The IaaS will typically have a quota mechanism, e.g. for virtual CPUs. What does Stratos do to enforce this, e.g. what happens when the autoscaler would like to push beyond the configured limit?
Thanks, Shaheed
P.S. Apologies if this has been asked before, but I cannot find a searchable archive for this mailer...or a newsgroup.
Re: Quotas and Stratos
Posted by Imesh Gunaratne <im...@apache.org>.
A good point Shaheed! I think we could use quota information if the quota
is reached before reaching the configured maximum. May be not the other way
around.
On Fri, Apr 10, 2015 at 10:41 PM, Shaheedur Haque (shahhaqu) <
shahhaqu@cisco.com> wrote:
> I see that jclouds seems to expose the quota information, so I do agree
> this would be good to have. Initially, it could be based on say #CPUs and
> then maybe additional checks on memory and disk and so on…
>
>
>
> WDYT?
>
>
>
> *From:* Reka Thirunavukkarasu [mailto:reka@wso2.com]
> *Sent:* 10 April 2015 06:37
> *To:* dev
> *Subject:* Re: Quotas and Stratos
>
>
>
> Hi Shaheed,
>
> AFAIK, autoscaler will strict to the min/max specified. We don't currently
> have the way of identifying whether actual IaaS has enough quota. If one
> partition failed as it is exhausted with the resources, then autoscaler can
> try to switch to next partition. However, I'm not sure whether we support
> this now. But this would be a nice to have feature. So that autoscaler
> won't blindly create instances in the exhausted partition all the time.
>
> As a workaround, we can configure the min/max to satisfy the actual IaaS
> level resources. So that we can assume that the autoscaler will not create
> the instances beyond the limit.
>
> FYI: If the autoscaler move an instance to terminating list, then the
> member which is being terminated will not be counted into the currently
> available instances. So, whenever autoscaler failed terminate an instance,
> then autoscaler can keep on creating new instances in order to satisfy the
> min/max as the terminating instance will not be counted.
>
>
>
> Thanks,
>
> Reka
>
>
>
> On Fri, Apr 10, 2015 at 9:57 AM, Shaheedur Haque (shahhaqu) <
> shahhaqu@cisco.com> wrote:
>
> Hi all,
>
>
>
> The IaaS will typically have a quota mechanism, e.g. for virtual CPUs.
> What does Stratos do to enforce this, e.g. what happens when the autoscaler
> would like to push beyond the configured limit?
>
>
>
> Thanks, Shaheed
>
>
>
> P.S. Apologies if this has been asked before, but I cannot find a
> searchable archive for this mailer…or a newsgroup.
>
>
>
>
> --
>
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
>
> Mobile: +94776442007
>
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
RE: Quotas and Stratos
Posted by "Shaheedur Haque (shahhaqu)" <sh...@cisco.com>.
I see that jclouds seems to expose the quota information, so I do agree this would be good to have. Initially, it could be based on say #CPUs and then maybe additional checks on memory and disk and so on…
WDYT?
From: Reka Thirunavukkarasu [mailto:reka@wso2.com]
Sent: 10 April 2015 06:37
To: dev
Subject: Re: Quotas and Stratos
Hi Shaheed,
AFAIK, autoscaler will strict to the min/max specified. We don't currently have the way of identifying whether actual IaaS has enough quota. If one partition failed as it is exhausted with the resources, then autoscaler can try to switch to next partition. However, I'm not sure whether we support this now. But this would be a nice to have feature. So that autoscaler won't blindly create instances in the exhausted partition all the time.
As a workaround, we can configure the min/max to satisfy the actual IaaS level resources. So that we can assume that the autoscaler will not create the instances beyond the limit.
FYI: If the autoscaler move an instance to terminating list, then the member which is being terminated will not be counted into the currently available instances. So, whenever autoscaler failed terminate an instance, then autoscaler can keep on creating new instances in order to satisfy the min/max as the terminating instance will not be counted.
Thanks,
Reka
On Fri, Apr 10, 2015 at 9:57 AM, Shaheedur Haque (shahhaqu) <sh...@cisco.com>> wrote:
Hi all,
The IaaS will typically have a quota mechanism, e.g. for virtual CPUs. What does Stratos do to enforce this, e.g. what happens when the autoscaler would like to push beyond the configured limit?
Thanks, Shaheed
P.S. Apologies if this has been asked before, but I cannot find a searchable archive for this mailer…or a newsgroup.
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: Quotas and Stratos
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi Shaheed,
AFAIK, autoscaler will strict to the min/max specified. We don't currently
have the way of identifying whether actual IaaS has enough quota. If one
partition failed as it is exhausted with the resources, then autoscaler can
try to switch to next partition. However, I'm not sure whether we support
this now. But this would be a nice to have feature. So that autoscaler
won't blindly create instances in the exhausted partition all the time.
As a workaround, we can configure the min/max to satisfy the actual IaaS
level resources. So that we can assume that the autoscaler will not create
the instances beyond the limit.
FYI: If the autoscaler move an instance to terminating list, then the
member which is being terminated will not be counted into the currently
available instances. So, whenever autoscaler failed terminate an instance,
then autoscaler can keep on creating new instances in order to satisfy the
min/max as the terminating instance will not be counted.
Thanks,
Reka
On Fri, Apr 10, 2015 at 9:57 AM, Shaheedur Haque (shahhaqu) <
shahhaqu@cisco.com> wrote:
> Hi all,
>
>
>
> The IaaS will typically have a quota mechanism, e.g. for virtual CPUs.
> What does Stratos do to enforce this, e.g. what happens when the autoscaler
> would like to push beyond the configured limit?
>
>
>
> Thanks, Shaheed
>
>
>
> P.S. Apologies if this has been asked before, but I cannot find a
> searchable archive for this mailer…or a newsgroup.
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007