Re: Manual scaling effects are not persisted

2014-11-08 Thread Lahiru Sandaruwan
Hi, It seems we need to introduce cluster context(which will be persisted) for keeping these runtime changes to policies and also the run time data such as required count. I will work on this. Thanks. On Sat, Oct 18, 2014 at 10:58 AM, Imesh Gunaratne wrote: > Hi, > > @Raj: What I pointed out

Re: Manual scaling effects are not persisted

2014-10-17 Thread Imesh Gunaratne
Hi, @Raj: What I pointed out is a design issue. Each time we introduce a new feature we should not introduce new persistence logic unless unavoidable, rather persistence should happen centrally. In this scenario when we update the subscription it should go through a common flow and update the in

Re: Manual scaling effects are not persisted

2014-10-17 Thread Lakmal Warusawithana
This is not only related to manual scaling, we should have some mechanism to persist associate polices (and run time changes) with cartridge subscription. Currently it does not required because we did not allow to change policies (run time update for policies) per subscription. But since we are pla

Re: Manual scaling effects are not persisted

2014-10-15 Thread Rajkumar Rajaratnam
Hi Imesh, On Wed, Oct 15, 2014 at 4:26 PM, Imesh Gunaratne wrote: > I do not think we need to specifically handle this, manual scaling also > need to take the same path as the standard scaling decision. > Hmm.. In manual scaling what we are doing is increasing the min count right? Basically we

Re: Manual scaling effects are not persisted

2014-10-15 Thread Imesh Gunaratne
I do not think we need to specifically handle this, manual scaling also need to take the same path as the standard scaling decision. On Wed, Oct 15, 2014 at 10:03 AM, Rajkumar Rajaratnam wrote: > Or else, we can have an API at CC side to update clusters and let CC to > publish ClusterUpdated eve

Re: Manual scaling effects are not persisted

2014-10-14 Thread Rajkumar Rajaratnam
Or else, we can have an API at CC side to update clusters and let CC to publish ClusterUpdated event to topology topic. AS can simply listen to this event and update the cluster context accordingly. Then we don't need to introduce a new topic for AS to publish events and AS is already listening to

Manual scaling effects are not persisted

2014-10-14 Thread Rajkumar Rajaratnam
Hi, As you know, we are now supporting manual scaling for docker containers. Autoscaler has an API to update cluster properties like min replicas of a particular cluster. void updateClusterMonitor(String clusterId, Properties properties) throws InvalidArgumentException; We are not persisting any