Re: Container-autoscaling branch created [Fwd: Git Push Summary]

+1 On Sat, Oct 11, 2014 at 11:20 AM, Nirmal Fernando wrote: > Guys, > > I think it's time to move to master? Wdyt? If you all agree, let's commit > only to master. > > On Sat, Oct 11, 2014 at 9:48 AM, Nirmal Fernando > wrote: > >> Merged to the master. Please double commit hereafter. >> >> On M

Re: Error in Python Agent

Hi Sajith, Can you start the container again, this time with LOG_LEVEL=DEBUG env var? I started a container manually with the following launch params and it goes as far as connecting to the message broker. Here are the env vars I used. sudo docker run -d -P --name php-cartridge-20 --env SERVICE_

Re: Container-autoscaling branch created [Fwd: Git Push Summary]

Guys, I think it's time to move to master? Wdyt? If you all agree, let's commit only to master. On Sat, Oct 11, 2014 at 9:48 AM, Nirmal Fernando wrote: > Merged to the master. Please double commit hereafter. > > On Mon, Oct 6, 2014 at 10:03 AM, Nirmal Fernando > wrote: > >> FYI $Subject, to ca

Re: Error while CEP publish member fault event

Hi Raj, Is message broker up and running. On Sat, Oct 11, 2014 at 9:26 AM, Rajkumar Rajaratnam wrote: > Hi, > > TID: [0] [STRATOS] [2014-10-11 09:23:01,002] DEBUG > {org.apache.stratos.manager.publisher.TenantSynzhronizerTask} - Publishing > complete tenant event > {org.apache.stratos.manager.

Error in Python Agent

Hi Chamila, I got a container started with Python Agent in it, but didn't get any member activated event.. I had a look at few logs, agent.log has only one line as follows.. root@ab654326-5104-11e4-bd2b-0800271054f4:/mnt/cartridge-agent# cat agent.log 2014-10-11 05:09:37,617:INFO:

Re: How we can change the logging format in Stratos?

committed to both container-autoscaling and master branches On Sat, Oct 11, 2014 at 8:06 AM, Rajkumar Rajaratnam wrote: > > > On Sat, Oct 11, 2014 at 7:59 AM, Sajith Kariyawasam > wrote: > >> Hi, >> >> Haven't noticed this until now :) >> >> in og4j.appender.CARBON_LOGFILE.layout.ConversionPatt

Re: git commit: Fixing layout.ConversionPattern to remove class name duplicates in the log

committed in 2d9895fdd4ed98fae5b79f21489bc6fae1884d66 On Sat, Oct 11, 2014 at 10:02 AM, Sajith Kariyawasam wrote: > sure > > On Sat, Oct 11, 2014 at 9:55 AM, Nirmal Fernando > wrote: > >> Sajith, please double commit to master as well. >> >> On Sat, Oct 11, 2014 at 9:53 AM, wrote: >> >>> Repos

Re: git commit: Fixing layout.ConversionPattern to remove class name duplicates in the log

sure On Sat, Oct 11, 2014 at 9:55 AM, Nirmal Fernando wrote: > Sajith, please double commit to master as well. > > On Sat, Oct 11, 2014 at 9:53 AM, wrote: > >> Repository: stratos >> Updated Branches: >> refs/heads/container-autoscaling d16d37eac -> 70a9cca24 >> >> >> Fixing layout.Conversion

Re: git commit: Fixing layout.ConversionPattern to remove class name duplicates in the log

Sajith, please double commit to master as well. On Sat, Oct 11, 2014 at 9:53 AM, wrote: > Repository: stratos > Updated Branches: > refs/heads/container-autoscaling d16d37eac -> 70a9cca24 > > > Fixing layout.ConversionPattern to remove class name duplicates in the log > > > Project: http://git

Re: Container-autoscaling branch created [Fwd: Git Push Summary]

Merged to the master. Please double commit hereafter. On Mon, Oct 6, 2014 at 10:03 AM, Nirmal Fernando wrote: > FYI $Subject, to carry out auto-scaling feature implementation for > container scenario. > > > -- Forwarded message -- > From: > Date: Mon, Oct 6, 2014 at 10:01 AM > S

Re: Build failed in Jenkins: Stratos-Master-Nightly-Build » Apache Stratos - CLI #284

I've fixed this build failure. On Sat, Oct 11, 2014 at 8:05 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < > https://builds.apache.org/job/Stratos-Master-Nightly-Build/org.apache.stratos$org.apache.stratos.cli/284/changes > > > > Changes: > > [imesh] Fixing login error hand

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Hi Raj, Yes your observation is correct. But in the CEP extension it expect stats within one minute. So it send member faulty event after one minute. Thanks ! On Fri, Oct 10, 2014 at 11:14 PM, Akila Ravihansa Perera wrote: > On Fri, Oct 10, 2014 at 11:09 PM, Rajkumar Rajaratnam > wrote: > > H

Error while CEP publish member fault event

Hi, TID: [0] [STRATOS] [2014-10-11 09:23:01,002] DEBUG {org.apache.stratos.manager.publisher.TenantSynzhronizerTask} - Publishing complete tenant event {org.apache.stratos.manager.publisher.TenantSynzhronizerTask} TID: [0] [STRATOS] [2014-10-11 09:23:01,003] DEBUG {org.apache.stratos.cloud.contro

Build failed in Jenkins: Stratos-Master-Nightly-Build » Apache Stratos - CLI #284

See Changes: [imesh] Fixing login error handling logic in CLI [imesh] Adding kubernetes group and host deploy and undeploy commands to cli [imesh] Adding kubernetes group and host

Build failed in Jenkins: Stratos-Master-Nightly-Build #284

See Changes: [lasinducharith] User Management Exception handling improvements and changes to REST API methods [imesh] Fixing login error handling logic in CLI [imesh] Adding kubernetes group and host deploy and undeploy c

Re: How we can change the logging format in Stratos?

On Sat, Oct 11, 2014 at 7:59 AM, Sajith Kariyawasam wrote: > Hi, > > Haven't noticed this until now :) > > in og4j.appender.CARBON_LOGFILE.layout.ConversionPattern=TID: [%T] [%S] > [%d] %P%5p *{%c}* - %x %m* {%c}*%n > %c appears twice, which lets the class name to logged twice > I think we should

Re: How we can change the logging format in Stratos?

Hi, Haven't noticed this until now :) in og4j.appender.CARBON_LOGFILE.layout.ConversionPattern=TID: [%T] [%S] [%d] %P%5p *{%c}* - %x %m* {%c}*%n %c appears twice, which lets the class name to logged twice I think we should remove that, thanks Raj or pointing out! Thanks, Sajith On Sat, Oct 11,

Re: Cannot subscribe to Docker based cartridge through Kubernetes

In up.sh, try commenting out the following line.. ssh -f -nNT -L 8080:127.0.0.1:8080 -F ssh.config master On Sat, Oct 11, 2014 at 6:47 AM, Nirmal Fernando wrote: > Kubernetes API server is getting bound to port 8080. If it's not correctly > open up, Stratos can't connect to the Kubernet

Re: Cannot subscribe to Docker based cartridge through Kubernetes

Thanks Sajith for confirming. I've pushed the changes here: https://github.com/nirmal070125/vagrant-kubernetes-setup In OS X- this worked without any issue and in Mint too. On Sat, Oct 11, 2014 at 7:23 AM, Sajith Kariyawasam wrote: > In up.sh, try commenting out the following line.. >

Re: How we can change the logging format in Stratos?

Hi, On Sat, Oct 11, 2014 at 6:44 AM, Nirmal Fernando wrote: > Why do you want to remove TID part? It stands for Tenant ID. > I didn't meant to remove it from code base. I wanted to do it locally in my running setup so that I can clearly observe the scaling logs. It is very lengthy now. And the

Re: Cannot subscribe to Docker based cartridge through Kubernetes

Kubernetes API server is getting bound to port 8080. If it's not correctly open up, Stratos can't connect to the Kubernetes cluster. This is an issue with the Kubernetes setup. On Sat, Oct 11, 2014 at 3:20 AM, Chamila De Alwis wrote: > Hi, > > I'm following the m1-guide to setup a Kubernetes Hos

Re: How we can change the logging format in Stratos?

Why do you want to remove TID part? It stands for Tenant ID. All these can be configured via log4j.properties files corresponding Appenders. On Sat, Oct 11, 2014 at 6:41 AM, Rajkumar Rajaratnam wrote: > Hi, > > Can we configure the logging format? > > Currently we are logging in the format like

Re: CEP in 4.0.0 stratos all-in-one

It's bundled up for the default profile. If you use any other profile, you have to start it separately. On Sat, Oct 11, 2014 at 3:12 AM, Martin Eppel (meppel) wrote: > Hi, > > > > is the Complex Event Processor (CEP) bundled up in the all-in-one jvm in > stratos 4.0.0 (and runs in the same jvm

How we can change the logging format in Stratos?

Hi, Can we configure the logging format? Currently we are logging in the format like below; TID: [0] [STRATOS] [2014-10-11 06:39:05,722] INFO {org.apache.stratos.autoscaler.rule.RuleLog} - Running minimum rule: [kub-cluster] KubGrp1 [cluster] myphp.php.domain {org.apache.stratos.autoscaler.rul

CEP in 4.0.0 stratos all-in-one

Hi, is the Complex Event Processor (CEP) bundled up in the all-in-one jvm in stratos 4.0.0 (and runs in the same jvm as apache stratos) or does it require a separate install ? Thanks Martin

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

On Fri, Oct 10, 2014 at 11:09 PM, Rajkumar Rajaratnam wrote: > Hi > > On Fri, Oct 10, 2014 at 10:42 PM, Akila Ravihansa Perera > wrote: >> >> Hi Raj, >> >> What you provide in GradientOfHealthRequest.xml execution plan is the >> time period that CEP waits to execute the Siddhi Window Processor. >

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Hi On Fri, Oct 10, 2014 at 10:42 PM, Akila Ravihansa Perera wrote: > Hi Raj, > > What you provide in GradientOfHealthRequest.xml execution plan is the > time period that CEP waits to execute the Siddhi Window Processor. > This is not exactly the time period Stratos will wait to detect faulty > i

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Also I don't think you can change the time out period on the fly. You have to restart the server to make changes take effect. Have you succeeded in changing this value on the fly? This value is read once and kept in memory according to the logic in Window processor init method. I think there is mo

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Hi Raj, What you provide in GradientOfHealthRequest.xml execution plan is the time period that CEP waits to execute the Siddhi Window Processor. This is not exactly the time period Stratos will wait to detect faulty instances. It is defined by TIME_OUT variable in FaultHandlingWindowProcessor.java

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

On Fri, Oct 10, 2014 at 10:34 PM, Manula Chathurika Thantriwatte < manu...@wso2.com> wrote: > Hi Raj, > > I don't think this is configurable. Timeout period is hard coded in the > fault handling window processor at the movement [1]. > Even though it is hard coded there, if we run the fault handli

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Hi Raj, I don't think this is configurable. Timeout period is hard coded in the fault handling window processor at the movement [1]. [1] https://github.com/apache/stratos/blob/master/extensions/cep/stratos-cep-extension/src/main/java/org/apache/stratos/cep/extension/FaultHandlingWindowProcessor.j

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Hi Manas, Seems it is configurable. We do not need to build the stratos again. We don't need to even restart the stratos. You can edit the following file in your running stratos setup. Please edit the following file; /apache-stratos-default/repository/deployment/server/executionplans/GradientOf

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Hi Manas, Ones CEP received stats from VM, it periodically checks for statics from that VM. Once it didn't received stats from that VM within one minute CEP figure it out as a faulty member and it send member faulty event. Thanks ! On Fri, Oct 10, 2014 at 7:31 PM, Rajkumar Rajaratnam wrote: >

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Hi, Forgot to mention that CEP will decide the faulty members based on one minute window. That is, if an active cartridge is not sending any health stats events to CEP in any one minute period, it will be identified as a faulty member. I guess, we can't tell the time stratos will take to terminat

RE: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Thanks Rajkumar, Does it means CEP won’t wait for specific defined time & declare that cartridge as faulty-vm?? Regards Manas. From: Rajkumar Rajaratnam [mailto:rajkum...@wso2.com] Sent: Friday, October 10, 2014 7:14 PM To: dev@stratos.apache.org Subject: Re: Which Timer in Stratos Triggers Car

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Hi Manas, If the cartridge-vm becomes unreachable, CEP will not get any events from cartridge agent (which is running inside cartridge-vm). Then CEP will identify it as a faulty member and publish member fault event. Autoscaler will listen to this event and terminate the cartridge-vm as soon as it

RE: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Hi Lasindu, The timer you mentioned is for the cartridge to come active after it got subscribed 90 Lets take an example, I subscribed to cartridge & it comes Active within the expiry-timeout mentioned above. Now, after sometime the cartridge vm becomes unreachable or

Re: Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Hi Manas, You should change the member 'expiryTimeout' property in /repository/conf/autoscaler.xml in order to adjust the timeout value. Thanks, On Fri, Oct 10, 2014 at 6:18 PM, Manas Padegaonkar -T (mpadegao - ARICENT TECHNOLOGIES HOLDINGS LIMITED at Cisco) wrote: > Hi, > > > > Wanted to kno

[jira] [Commented] (STRATOS-882) [CLI] Invalid Error Handling at Login

[ https://issues.apache.org/jira/browse/STRATOS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166753#comment-14166753 ] Imesh Gunaratne commented on STRATOS-882: - Fixed with commit revision: 8550d58de4

Which Timer in Stratos Triggers Cartridge Deletion When its Unreachable

Hi, Wanted to know which timer in stratos will trigger the deletion of existing Active Cartridge when it becomes unreachable. Regards Manas

[jira] [Resolved] (STRATOS-882) [CLI] Invalid Error Handling at Login

[ https://issues.apache.org/jira/browse/STRATOS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne resolved STRATOS-882. - Resolution: Fixed > [CLI] Invalid Error Handling at Login > -

[jira] [Updated] (STRATOS-882) [CLI] Invalid Error Handling at Login

[ https://issues.apache.org/jira/browse/STRATOS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-882: Affects Version/s: 4.1.0 M1 > [CLI] Invalid Error Handling at Login > -

[jira] [Updated] (STRATOS-882) [CLI] Invalid Error Handling at Login

[ https://issues.apache.org/jira/browse/STRATOS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-882: Fix Version/s: 4.1.0 M2 > [CLI] Invalid Error Handling at Login > -

[jira] [Updated] (STRATOS-882) [CLI] Invalid Error Handling at Login

[ https://issues.apache.org/jira/browse/STRATOS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-882: Description: Seems like in CLI even when the user is not authenticated it says "Successfull

[jira] [Created] (STRATOS-882) [CLI] Invalid Error Handling at Login

Imesh Gunaratne created STRATOS-882: --- Summary: [CLI] Invalid Error Handling at Login Key: STRATOS-882 URL: https://issues.apache.org/jira/browse/STRATOS-882 Project: Stratos Issue Type: Bug

[jira] [Commented] (STRATOS-791) MQTT protocol support for the messaging module

[ https://issues.apache.org/jira/browse/STRATOS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166624#comment-14166624 ] ASF GitHub Bot commented on STRATOS-791: GitHub user swgkg opened a pull request:

[GitHub] stratos pull request: Fixes for error in publishing artifact updat...

GitHub user swgkg opened a pull request: https://github.com/apache/stratos/pull/87 Fixes for error in publishing artifact updated event - STRATOS-791 This pull image contains the fixes for : Error in publishing artifact updated event - STRATOS-858 Re factoring the code - STRA

[jira] [Created] (STRATOS-881) Get the Cluster Read Lock before creating a Cluster Monitor

Isuru Haththotuwa created STRATOS-881: - Summary: Get the Cluster Read Lock before creating a Cluster Monitor Key: STRATOS-881 URL: https://issues.apache.org/jira/browse/STRATOS-881 Project: Strato

Re: [Wiki] Stratos HA Image Source file needed to correct typos

Thank you, Lakmal! Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com On Fri, Oct 10, 2014 at 11:44 AM, Lakmal Warusawithana wrote: > Hi Mari, > > Send the invite email for

[GitHub] stratos pull request: Python implementation of the Cartridge Agent

Github user chamilad commented on the pull request: https://github.com/apache/stratos/pull/85#issuecomment-58621287 Resubmit to container-autoscaling --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does no

[GitHub] stratos pull request: Python implementation of the Cartridge Agent

Github user chamilad closed the pull request at: https://github.com/apache/stratos/pull/85 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is en

[jira] [Resolved] (STRATOS-872) New User update issue

[ https://issues.apache.org/jira/browse/STRATOS-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith resolved STRATOS-872. - Resolution: Fixed Fix Version/s: 4.2.0 M2 > New User update issue > --

[jira] [Commented] (STRATOS-872) New User update issue

[ https://issues.apache.org/jira/browse/STRATOS-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166502#comment-14166502 ] Lasindu Charith commented on STRATOS-872: - This issue was due to REST Endpoint no

Re: Dockerfile for PHP image with Python Cartridge Agent

Hi Nirmal, I'm in the process of testing this now. I couldn't do so earlier because of the low memory resources on my laptop. I'm working with Sajith to get this tested. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Fri, Oct 10, 2014 at 8:0