Re: [Discuss] Apache Stratos 4.1.2 Release Plan

Hi, I've tested all supported IaaS types and verified the functionality. Pushed jclouds 1.9.1 upgrade + GCE fix to master branch. I've also added Carbon kernel patches up to patch0012 to Stratos. Marked relevant JIRAs as resolved. Thanks. On Fri, Aug 21, 2015 at 11:35 AM, Imesh Gunaratne wrote:

[jira] [Resolved] (STRATOS-1435) Upgrade carbon 4.2.0 to new kernel patches

[ https://issues.apache.org/jira/browse/STRATOS-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila resolved STRATOS-1435. Resolution: Fixed Fixed in commit: bef7f66df80eb2ff6f89dfb3c8230b64f8711998 > Upgrade carbon 4.2.0 to new

[jira] [Resolved] (STRATOS-1516) Error when deploying an application on Google Compute Engine

[ https://issues.apache.org/jira/browse/STRATOS-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila resolved STRATOS-1516. Resolution: Fixed Fix Version/s: (was: FUTURE) 4.1.2 Issue analysis: All the

Jenkins build is still unstable: Stratos-Master-Commit-Build #801

See

Jenkins build is still unstable: Stratos-Master-Commit-Build » Apache Stratos - Integration Tests #801

See

Re: Jenkins build is unstable: Stratos-Master-Commit-Build #800

Hi I went though the error log and found that NPE has been thrown while deploying the applicaiton in ApplicationInstanceCreatedProcessor. But couldn't find out the root cause of it. I have fixed a particular code which caused NPE as that code segment had the possibility to cause NPE. I will test t

Jenkins build is unstable: Stratos-Master-Commit-Build #800

See

Jenkins build became unstable: Stratos-Master-Commit-Build » Apache Stratos - Integration Tests #800

See

Jenkins build is back to normal : Stratos-Master-Nightly-Build #599

See

Jenkins build is back to normal : Stratos-Master-Nightly-Build » Apache Stratos - Load Balancer - Distribution #599

See

Re: [Code Quality] Sonar profile shows 261 critical issues

Hi Devs, +1, I have already started to clean code in master branch according to SonarQube and FindBugs. These are the P/R for that: [1]. https://github.com/apache/stratos/pull/420 [2]. https://github.com/apache/stratos/pull/444 I'm currently cleaning code in cloud-controller component. PR [1] is

[GitHub] stratos pull request: Modifying thrift-client-config file.

GitHub user Thanu opened a pull request: https://github.com/apache/stratos/pull/449 Modifying thrift-client-config file. This P/R includes following: 1. Deleting artifacts used to publish health stats from cep to das. 2. Enable Thrift Stats Publisher using thrift-client-confi

[GitHub] stratos pull request: Fixing the issue when adding a cartridgeGrou...

Github user asfgit closed the pull request at: https://github.com/apache/stratos/pull/448 --- 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 ena

[GitHub] stratos pull request: Fixing the issue when adding a cartridgeGrou...

GitHub user dinithis opened a pull request: https://github.com/apache/stratos/pull/448 Fixing the issue when adding a cartridgeGroup with a name of a subgroup in another cartridge group Fixing the issue when adding a cartridgeGroup with a name of a subgroup in another cartridge gro

[jira] [Created] (STRATOS-1523) Stop Monitors thread when application is undeploying

Reka Thirunavukkarasu created STRATOS-1523: -- Summary: Stop Monitors thread when application is undeploying Key: STRATOS-1523 URL: https://issues.apache.org/jira/browse/STRATOS-1523 Project: St

[jira] [Resolved] (STRATOS-1523) Stop Monitors thread when application is undeploying

[ https://issues.apache.org/jira/browse/STRATOS-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reka Thirunavukkarasu resolved STRATOS-1523. Resolution: Fixed Assignee: Reka Thirunavukkarasu Fixed in Commit:

[jira] [Resolved] (STRATOS-1489) Faulty behavior in application monitor creation logic

[ https://issues.apache.org/jira/browse/STRATOS-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reka Thirunavukkarasu resolved STRATOS-1489. Resolution: Fixed Fix Version/s: 4.1.2 > Faulty behavior in applica

[jira] [Assigned] (STRATOS-1489) Faulty behavior in application monitor creation logic

[ https://issues.apache.org/jira/browse/STRATOS-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reka Thirunavukkarasu reassigned STRATOS-1489: -- Assignee: Reka Thirunavukkarasu > Faulty behavior in application moni

[jira] [Commented] (STRATOS-1489) Faulty behavior in application monitor creation logic

[ https://issues.apache.org/jira/browse/STRATOS-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706684#comment-14706684 ] Reka Thirunavukkarasu commented on STRATOS-1489: This is fixed in Commi

[jira] [Created] (STRATOS-1522) Single cluster autoscaling support in Integration Framework

Reka Thirunavukkarasu created STRATOS-1522: -- Summary: Single cluster autoscaling support in Integration Framework Key: STRATOS-1522 URL: https://issues.apache.org/jira/browse/STRATOS-1522 Pro

[jira] [Resolved] (STRATOS-1522) Single cluster autoscaling support in Integration Framework

[ https://issues.apache.org/jira/browse/STRATOS-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reka Thirunavukkarasu resolved STRATOS-1522. Resolution: Fixed This is added to Integration Framework. > Single cluste

[jira] [Resolved] (STRATOS-1518) Integration test to cover listing of all the artifacts

[ https://issues.apache.org/jira/browse/STRATOS-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reka Thirunavukkarasu resolved STRATOS-1518. Resolution: Done This is added to integration framework. > Integration te

[jira] [Resolved] (STRATOS-1517) Integration test to cover termination behavior and startup order of Composite application

[ https://issues.apache.org/jira/browse/STRATOS-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reka Thirunavukkarasu resolved STRATOS-1517. Resolution: Done > Integration test to cover termination behavior and star

[jira] [Resolved] (STRATOS-1521) Scale-down not working when partitionMax hits

[ https://issues.apache.org/jira/browse/STRATOS-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reka Thirunavukkarasu resolved STRATOS-1521. Resolution: Fixed > Scale-down not working when partitionMax hits > --

[jira] [Commented] (STRATOS-1517) Integration test to cover termination behavior and startup order of Composite application

[ https://issues.apache.org/jira/browse/STRATOS-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706673#comment-14706673 ] Reka Thirunavukkarasu commented on STRATOS-1517: These tests have been a

[jira] [Commented] (STRATOS-1521) Scale-down not working when partitionMax hits

[ https://issues.apache.org/jira/browse/STRATOS-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706671#comment-14706671 ] Reka Thirunavukkarasu commented on STRATOS-1521: It is fixed in Commit:

[GitHub] stratos pull request: Thrift Client Configuration Modification

Github user asfgit closed the pull request at: https://github.com/apache/stratos/pull/447 --- 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 ena

Re: [Improvement] Single tenant application deletion via single method call

Hi Reka, Yes at least getting a certain undeployment time would satisfy our requirement. I had an offline chat with Akila and got to know that previously undeployment call was synchronous, where we are getting a response if the undeployment is success or not, which solves the issue. On Fri, Aug

[GitHub] stratos pull request: Adding missing changes for monitoring servic...

Github user asfgit closed the pull request at: https://github.com/apache/stratos/pull/446 --- 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 ena

Re: [Improvement] Single tenant application deletion via single method call

Hi Anuruddha, Our purpose was to differentiate application undeployment and deletion as we have treated application run time and the application definition separately. IMO, it is not good to merge undeployment and deletion to one call. In some other scenarios, users can undeploy an application, th

[GitHub] stratos pull request: Thrift Client Configuration Modification

GitHub user Thanu opened a pull request: https://github.com/apache/stratos/pull/447 Thrift Client Configuration Modification This P/R includes Stratos thrift-client-config.xml file change to read DAS thrift client configuration from the same file and thrift config parser and publis

[GitHub] stratos pull request: Adding missing changes for monitoring servic...

GitHub user Thanu opened a pull request: https://github.com/apache/stratos/pull/446 Adding missing changes for monitoring service This P/R is to add missing part for monitoring service commit 'Refactoring Monitoring Service Classes'. You can merge this pull request into a Git repos

[Improvement] Single tenant application deletion via single method call

Hi Devs, When we want to delete a single tenant application user have to first undeploy the application and then delete it. If a user wants to do it programatically, one way is to undepoy and wait for a certain period and then delete this is not reliable since the waiting time is uncertain. Other

[jira] [Created] (STRATOS-1521) Scale-down not working when partitionMax hits

Reka Thirunavukkarasu created STRATOS-1521: -- Summary: Scale-down not working when partitionMax hits Key: STRATOS-1521 URL: https://issues.apache.org/jira/browse/STRATOS-1521 Project: Stratos

[GitHub] stratos pull request: Thrift Client Configuration Modification

Github user Thanu closed the pull request at: https://github.com/apache/stratos/pull/443 --- 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 enab