hmm... We use deployment policies to give an idea about order and limits of partitions.
How about giving freedom to change the min and max of deployment policy? Then the user can think and use deployment policies wisely. E.g. If he need to control min/max just for one cluster, he should give a particular policy for that cluster and only for that cluster. Or if he think it is fine to control min/max of two clusters from one policy, he can use one policy for both subscriptions. We face this problem when addressing seasonal patterns as well. E.g. Cluster A needs to handle higher load in first week of the year. So user decides to have minimum of 4 instances in that particular week, instead of the minimum of 2, that it normally has. We can handle both scenarios same way. Thanks. On Sat, Aug 23, 2014 at 9:31 PM, Nirmal Fernando <nirmal070...@gmail.com> wrote: > Lahiru, as you know currently we define min-max in a deployment policy and > per a partition. But AFAIU the objective of this feature is to provide > instant scaling for a service cluster without affecting other clusters. > > > On Sat, Aug 23, 2014 at 8:27 PM, Lahiru Sandaruwan <lahi...@wso2.com> > wrote: > >> Period here is one minute. I understand and agree the instant >> requirement. But I feel like introducing this much of complexity is not >> worth that one minute. >> >> Thanks. >> >> >> On Sat, Aug 23, 2014 at 12:39 PM, Nirmal Fernando <nirmal070...@gmail.com >> > wrote: >> >>> Hi Lahiru, >>> >>> AFAIU why manual scaling important is you can trigger a new instance >>> instantly instead of going through a periodical process. Same applies to >>> scaling down. Of course, it's important to avoid conflicts between auto and >>> manual scaling and that's part of the research. >>> >>> >>> On Sat, Aug 23, 2014 at 11:24 AM, Lahiru Sandaruwan <lahi...@wso2.com> >>> wrote: >>> >>>> Hi Nirmal, >>>> >>>> How about increasing/changing the min and max on the go, rather than >>>> manually adding nodes? >>>> >>>> Thanks. >>>> >>>> -- >>>> -- >>>> Lahiru Sandaruwan >>>> Committer and PMC member, Apache Stratos, >>>> Senior Software Engineer, >>>> WSO2 Inc., http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> email: lahi...@wso2.com cell: (+94) 773 325 954 >>>> blog: http://lahiruwrites.blogspot.com/ >>>> twitter: http://twitter.com/lahirus >>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>>> >>>> >>> >>> >>> -- >>> Best Regards, >>> Nirmal >>> >>> Nirmal Fernando. >>> PPMC Member & Committer of Apache Stratos, >>> >>> Senior Software Engineer, WSO2 Inc. >>> >>> Blog: http://nirmalfdo.blogspot.com/ >>> >> >> >> >> -- >> -- >> Lahiru Sandaruwan >> Committer and PMC member, Apache Stratos, >> Senior Software Engineer, >> WSO2 Inc., http://wso2.com >> lean.enterprise.middleware >> >> email: lahi...@wso2.com cell: (+94) 773 325 954 >> blog: http://lahiruwrites.blogspot.com/ >> twitter: http://twitter.com/lahirus >> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> >> > > > -- > Best Regards, > Nirmal > > Nirmal Fernando. > PPMC Member & Committer of Apache Stratos, > Senior Software Engineer, WSO2 Inc. > > Blog: http://nirmalfdo.blogspot.com/ > -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
