Hi,
The group-scaling-v1 can not be un-deployed, after failed undeployed, can
not re-active again.
Also after this failed, the single-cartridge-app can not active.
David
On Sun, Feb 8, 2015 at 1:54 PM, Reka Thirunavukkarasu wrote:
> Hi
>
> After i have removed this particular check to start
According to my understanding, startup order is broken due to we start all
the adder at once..Could you please check on this?
Thanks,
Reka
On Sun, Feb 8, 2015 at 1:51 PM, Reka Thirunavukkarasu wrote:
> Hi Gayan,
>
> I found below segment has been added when starting the monitor adder.
> Could y
Hi Gayan,
I found below segment has been added when starting the monitor adder. Could
you please explain Why it has been added? We used to start the adder
whenever needed as per earlier implementation by referring to dependency
tree. Won't this break the dependency order of the Clusters? I found t
Thanks Imesh for fixing the issues..I will continue testing with the other
samples..
Thanks,
Reka
On Sun, Feb 8, 2015 at 10:59 AM, Imesh Gunaratne wrote:
> May be this message processor is receiving an invalid message. Will debug
> and see.
>
> On Sun, Feb 8, 2015 at 11:09 PM, Gayan Gunarathne
May be this message processor is receiving an invalid message. Will debug
and see.
On Sun, Feb 8, 2015 at 11:09 PM, Gayan Gunarathne wrote:
> Hi Imesh,
>
> Seems "GroupStatusInactiveProcessor" is the last processor in the
> "GroupStatusProcessorChain".We are printing the above warn message if th
Hi Imesh,
Seems "GroupStatusInactiveProcessor" is the last processor in the
"GroupStatusProcessorChain".We are printing the above warn message if the
next processor is null.
if (nextProcessor != null) {
// ask the next processor to take care of the message.
return n
I tested both group-scaling and group-scaling-v1 applications but they did
not activate:
I can see the following warning in the log:
WARN
{org.apache.stratos.autoscaler.status.processor.group.GroupStatusInactiveProcessor}
- No possible state change found for [component] mygroup2 [instance]
Than
Great work Reka! Thanks for looking into this!
On Sun, Feb 8, 2015 at 3:27 AM, Reka Thirunavukkarasu wrote:
> Hi
>
> I have fixed one issue that i found when using more than one
> groupInstances in the application. Now that, i could get all the
> single-group-* samples became active without any
Hi
I have fixed one issue that i found when using more than one groupInstances
in the application. Now that, i could get all the single-group-* samples
became active without any issue.
Thanks,
Reka
On Sat, Feb 7, 2015 at 12:08 PM, Reka Thirunavukkarasu
wrote:
> Hi
>
> Do we have the current st
Hi Reka,
I fixed subscribable information finding logic in default application
parser, not sure about others (cannot see any other commits except for one
from you). Moreover I found several problems in the samples and fixes those
today.
Did the group samples stay in Active state constantly?
Than
Hi
Do we have the current state of the samples and application state? When i
tried group samples in mock and it has become active..Did we fix this
recently?
Thanks,
Reka
On Sat, Feb 7, 2015 at 11:54 AM, Reka Thirunavukkarasu
wrote:
> Great job in organizing this samples..I just tried the simpl
Great job in organizing this samples..I just tried the simple sample. It
saves lot of time in the testing phase..
On Fri, Feb 6, 2015 at 7:08 PM, Imesh Gunaratne wrote:
> Hi Chamila,
>
> Now we have a common set of artifacts and deployment scripts for all the
> IaaSes except for deployment pol
Hi Chamila,
Now we have a common set of artifacts and deployment scripts for all the
IaaSes except for deployment policies. We have verified this with Mock IaaS.
Thanks
On Fri, Feb 6, 2015 at 11:47 PM, Chamila De Alwis wrote:
> Hi Imesh,
>
> Is this on a particular one IaaS or on mock IaaS?
>
Hi Imesh,
Is this on a particular one IaaS or on mock IaaS?
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Fri, Feb 6, 2015 at 9:18 PM, Imesh Gunaratne wrote:
> Thanks Dinithi, Manula and Vishanth for contributing to fix sample
> applicati
Thanks Dinithi, Manula and Vishanth for contributing to fix sample
applications! I'm now looking into issues we have in grouping logic.
Thanks
On Fri, Feb 6, 2015 at 8:59 PM, Dinithi De Silva wrote:
> Hi Imesh,
>
> Both group-scaling and group-scaling-v1 also become inactive after few
> seconds
Hi Imesh,
Both group-scaling and group-scaling-v1 also become inactive after few
seconds.
Thanks
On Fri, Feb 6, 2015 at 7:18 PM, Imesh Gunaratne wrote:
> Hi Devs,
>
> Please find the current state of the sample applications below:
>
> complex-appApplication does not Activatecomplex-app-with-lb
Hi Devs,
Please find the current state of the sample applications below:
complex-appApplication does not Activatecomplex-app-with-lbApplication does
not Activatedependent-scaling/sample-cartridgesApplication Activates but
becomes Inactive after few secondsdependent-scaling/sample-groupsApplicatio
17 matches
Mail list logo
