Re: [Discuss] Executing rolling update on a service cluster

Hi Sajith, On Tue, Dec 15, 2015 at 5:41 PM, Sajith Kariyawasam wrote: > Hi Devs, > > At the moment in a Stratos deployment there is no easy way to do a rolling > update on a service cluster. One has to manually terminate all the running > instances of the cluster, after updating images / puppet

[Discuss] Executing rolling update on a service cluster

Hi Devs, At the moment in a Stratos deployment there is no easy way to do a rolling update on a service cluster. One has to manually terminate all the running instances of the cluster, after updating images / puppet master with relevant fixes, and then autoscaler will spawn new instances with the

Removing application signups if (!applicationSignUpExists) ?

Hi Devs, Can someone clarify this code? In AutoscalerServiceImpl undeployApplication method I can see following logic if (!applicationSignUpExists) { ... --> undeployApplicationGracefully () } Inside undeployApplicationGracefully method I can see removeApplicationSignUp is invoked. But why its

[jira] [Created] (STRATOS-1645) PCA message broker HA support has broken backward compatibility of cartridges

Imesh Gunaratne created STRATOS-1645: Summary: PCA message broker HA support has broken backward compatibility of cartridges Key: STRATOS-1645 URL: https://issues.apache.org/jira/browse/STRATOS-1645