Re: Stratos 4.1.0 - tracebacks seen when issuing application undeploy/remove

On Mon, Mar 30, 2015 at 7:18 PM, Vanson Lim wrote: > On 3/30/15, 9:18 AM, Lakmal Warusawithana wrote: > > IMO forceful un deploy is enough no need to have forceful delete. If un > deployment success delete should work without any issues > > > I agree, forceful undeploy should be enough. I ass

Re: Issue (?): Stratos 4.1.0 - Cartridges in a group are not going active ... was RE: Stratos 4.1.0 : Issue when deploying application with single group and 3 cartridges, no dependencies ...

Hi Martin, On Tue, Mar 31, 2015 at 5:41 AM, Martin Eppel (meppel) wrote: > Hi Lahiru, > > > > I tested a new scenario, where I have 2 groups with cartridges and no > start up dependencies and I see again the issue with cartridge instances > being stuck in “started” state. I also noticed the fol

Jenkins build is back to stable : Stratos-Master-Nightly-Build #455

See

Jenkins build is back to stable : Stratos-Master-Nightly-Build » jclouds Google Compute Engine provider #455

See

[jira] [Commented] (STRATOS-1292) Stratos 4.1.0 : Issue when deploying application with single group and 3 cartridges, no dependencies ...

[ https://issues.apache.org/jira/browse/STRATOS-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387456#comment-14387456 ] Martin Eppel commented on STRATOS-1292: --- tested the provided fix and it worked, al

RE: Issue (?): Stratos 4.1.0 - Cartridges in a group are not going active ... was RE: Stratos 4.1.0 : Issue when deploying application with single group and 3 cartridges, no dependencies ...

Thanks Lahiru, Will do and let you know Martin From: Lahiru Sandaruwan [mailto:lahi...@wso2.com] Sent: Monday, March 30, 2015 3:32 AM To: dev Subject: Re: Issue (?): Stratos 4.1.0 - Cartridges in a group are not going active ... was RE: Stratos 4.1.0 : Issue when deploying application with sing

Re: Stratos 4.1.0 - tracebacks seen when issuing application undeploy/remove

On 3/30/15, 9:18 AM, Lakmal Warusawithana wrote: IMO forceful un deploy is enough no need to have forceful delete. If un deployment success delete should work without any issues I agree, forceful undeploy should be enough. I assume this means that if I call undeploy (force=false) the first

Re: Stratos 4.1.0 - tracebacks seen when issuing application undeploy/remove

+1 Yes Lakmal, a good point! We might not need a forceful application delete, a forceful application un-deployment would be sufficient. Thanks On Mon, Mar 30, 2015 at 6:48 PM, Lakmal Warusawithana wrote: > IMO forceful un deploy is enough no need to have forceful delete. If un > deployment succ

Re: Stratos 4.1.0 - tracebacks seen when issuing application undeploy/remove

IMO forceful un deploy is enough no need to have forceful delete. If un deployment success delete should work without any issues On Monday, March 30, 2015, Imesh Gunaratne wrote: > Thanks Vanson for pointing this scenario! Yes we would need to forcefully > delete an application in certain scenar

Re: Is there a special reason to persist Deployment policies in Cloud Controller

On Monday, March 30, 2015, Lahiru Sandaruwan wrote: > When the deployment policy is deployed in cloud controller, it is > difficult to update it at runtime and propagate the update to Cluster > monitors(actual runtime). > > Therefore i will be moving it back to Autoscaler. > > +1IMO It should be

[jira] [Updated] (STRATOS-1302) Wrong HTTP status code and message - DELETE /applicationPolicies/{applicationPolicyId}

[ https://issues.apache.org/jira/browse/STRATOS-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1302: -- Priority: Major (was: Minor) > Wrong HTTP status code and message - DELETE > /applic

[jira] [Updated] (STRATOS-1302) Wrong HTTP status code and message - DELETE /applicationPolicies/{applicationPolicyId}

[ https://issues.apache.org/jira/browse/STRATOS-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1302: -- Description: 1) Normally the 204 HTTP status code should be returned when deleting. Ho

[jira] [Updated] (STRATOS-1302) Wrong HTTP status code and message - DELETE /applicationPolicies/{applicationPolicyId}

[ https://issues.apache.org/jira/browse/STRATOS-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1302: -- Assignee: (was: Dinithi De SIlva) > Wrong HTTP status code and message - DELETE >

[jira] [Updated] (STRATOS-1302) Wrong HTTP status code and message - DELETE /applicationPolicies/{applicationPolicyId}

[ https://issues.apache.org/jira/browse/STRATOS-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1302: -- Priority: Minor (was: Major) > Wrong HTTP status code and message - DELETE > /applic

[jira] [Updated] (STRATOS-1302) Wrong HTTP status code and message - DELETE /applicationPolicies/{applicationPolicyId}

[ https://issues.apache.org/jira/browse/STRATOS-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1302: -- Description: 1) Normally the 204 HTTP status code should be returned when deleting. Ho

[jira] [Created] (STRATOS-1302) Wrong HTTP status code and message - DELETE /applicationPolicies/{applicationPolicyId}

Mariangela Hills created STRATOS-1302: - Summary: Wrong HTTP status code and message - DELETE /applicationPolicies/{applicationPolicyId} Key: STRATOS-1302 URL: https://issues.apache.org/jira/browse/STRATOS-1302

Re: Is there a special reason to persist Deployment policies in Cloud Controller

When the deployment policy is deployed in cloud controller, it is difficult to update it at runtime and propagate the update to Cluster monitors(actual runtime). Therefore i will be moving it back to Autoscaler. Thanks. On Mon, Mar 30, 2015 at 4:17 PM, Lahiru Sandaruwan wrote: > Hi, > > $subje

Is there a special reason to persist Deployment policies in Cloud Controller

Hi, $subject. AFAIR we had this in Autoscaler earlier. Thanks. -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +94773325954 email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ l

Re: Issue (?): Stratos 4.1.0 - Cartridges in a group are not going active ... was RE: Stratos 4.1.0 : Issue when deploying application with single group and 3 cartridges, no dependencies ...

Hi Martin, I was able to reproduce the issue and committed a fix. Could you please verify? Thanks. On Sun, Mar 29, 2015 at 5:43 PM, Lahiru Sandaruwan wrote: > Hi Martin, > > According to the logs attached, it seems the cartridge agent waits for the > artifact updated event, and somehow it is n

[jira] [Updated] (STRATOS-1300) Mock IaaS sends the instance activated for member eventhough the ArtifactUpdatedEvent is not received

[ https://issues.apache.org/jira/browse/STRATOS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandaruwan updated STRATOS-1300: --- Description: This affects when the artifact repo is available. > Mock IaaS sends the

[jira] [Updated] (STRATOS-1300) Mock IaaS sends the instance activated for member eventhough the ArtifactUpdatedEvent is not received

[ https://issues.apache.org/jira/browse/STRATOS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandaruwan updated STRATOS-1300: --- Description: Due to this, it will send the instance activated event (was: Due to th

[jira] [Deleted] (STRATOS-1301) Mock IaaS send the instanceActivatedEvent eventhough the artifactUpdatedEvent is not received

[ https://issues.apache.org/jira/browse/STRATOS-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandaruwan deleted STRATOS-1301: --- > Mock IaaS send the instanceActivatedEvent eventhough the artifactUpdatedEvent > is n

[jira] [Updated] (STRATOS-1300) Mock IaaS sends the instance activated for member eventhough the ArtifactUpdatedEvent is not received

[ https://issues.apache.org/jira/browse/STRATOS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandaruwan updated STRATOS-1300: --- Description: (was: Due to this, it will send the instance activated event) > Mo

[jira] [Created] (STRATOS-1301) Mock IaaS send the instanceActivatedEvent eventhough the artifactUpdatedEvent is not received

Lahiru Sandaruwan created STRATOS-1301: -- Summary: Mock IaaS send the instanceActivatedEvent eventhough the artifactUpdatedEvent is not received Key: STRATOS-1301 URL: https://issues.apache.org/jira/browse/STR

[jira] [Created] (STRATOS-1300) Mock IaaS sends the instance activated for member eventhough the ArtifactUpdatedEvent is not received

Lahiru Sandaruwan created STRATOS-1300: -- Summary: Mock IaaS sends the instance activated for member eventhough the ArtifactUpdatedEvent is not received Key: STRATOS-1300 URL: https://issues.apache.org/jira/br

Re: Acessing cartridge through Load Balancer public IP returns "Unknown host name"

Did you map LB-Public IP to Cartridge Host Name in /etc/hosts file? On Monday, March 30, 2015, Ricardo Carvalho wrote: > Hi everyone > > > I'm using Apache Stratos 4.0.0 with two cartridge instances, one load > balancer and one php cartridge. I defined the http and https ports as 8280 > and 82