Jenkins build became unstable: Stratos-41x-Nightly-Build » Apache Stratos - Messaging #47

See

Jenkins build became unstable: Stratos-41x-Nightly-Build #47

See

Re: PCA live test is failing

Thanks Pubudu! Yes, I think it's better to use IOUtils.toString(classLoader.getResourceAsStream(fileName)) to read the config files here. I'm seeing lot of code duplication warnings in all test cases. We might have to refactor the agent test cases. Thanks. On Wed, Nov 11, 2015 at 11:47 PM, Pubud

Re: PCA live test is failing

Hi, I will look into this. We may have to change [1] as well. [1] - https://github.com/apache/stratos/blob/stratos-4.1.x/products/python-cartridge-agent/modules/integration/test-integration/src/test/java/org/apache/stratos/python/cartridge/agent/integration/tests/PythonAgentIntegrationTest.java#L

AutoscalerHealthStatEventReceiver is sleeping for 15s at startup?

Hi devs, I noticed $subject in [1]. Is there any reason for this? As per a comment it is waiting for Autoscaler deployer to be activated. Anyone has an idea what this is about? 15s delay at the server startup is a significant amount of delay. If this is actually needed we need to fix this properl

Jenkins build is back to stable : Stratos-41x-Commit-Build » Apache Stratos - Integration Tests #139

See

Jenkins build is back to stable : Stratos-41x-Commit-Build #139

See

Jenkins build became unstable: Stratos-41x-Commit-Build #138

See

Jenkins build became unstable: Stratos-41x-Commit-Build » Apache Stratos - Integration Tests #138

See

PCA live test is failing

Hi, Looks like PCA live test case for CEPHAModeTestCase is failing. Noticed few issues in this test case. - Calling read() method in FIS does not guarantee that complete file is loaded [1] - cepPort + 1 is confusing. Use a public const with the actual value [2] - Method name should be fixed to

[jira] [Updated] (STRATOS-1613) The Image Id defined in the Cartridge Defintion Does not get picked in Building the JClouds Template

[ https://issues.apache.org/jira/browse/STRATOS-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa updated STRATOS-1613: --- Fix Version/s: FUTURE > The Image Id defined in the Cartridge Defintion Does not get

[EC2] Removing the Image Id from CC Results in instances Spinning in Wrong Zones

Hi Devs, Noted $subject. When there is no image id in the cloud-controller.xml, the JClouds template which is build will of default type, which does not have any zone information. Therefore it will spin the instance in the default zone, without using the zone selected by partition algorithm. I wil

[jira] [Created] (STRATOS-1613) The Image Id defined in the Cartridge Defintion Does not get picked in Building the JClouds Template

Isuru Haththotuwa created STRATOS-1613: -- Summary: The Image Id defined in the Cartridge Defintion Does not get picked in Building the JClouds Template Key: STRATOS-1613 URL: https://issues.apache.org/jira/br

Re: [Discuss] Suggesting a patching model for PCA

On Wed, Nov 11, 2015 at 6:07 PM, Sajith Kariyawasam wrote: > Hi Devs, > > At the moment Python Cartridge Agent (PCA) doesn't have a convenient way > of applying patches. > If there is an issue identified and fixed, in order to apply the fix to a > running system that particular file(s) has to be

[Discuss] Suggesting a patching model for PCA

Hi Devs, At the moment Python Cartridge Agent (PCA) doesn't have a convenient way of applying patches. If there is an issue identified and fixed, in order to apply the fix to a running system that particular file(s) has to be replaced in the running system, and there is no easy way to revert the p

Re: ComponentStartUpSynchronizer: CC and AS components are waiting for SM to be activated?

Hi Imesh, Thanks for the clarification. I've removed this logic that forced CC and AS to wait for SM to be activated to schedule sync tasks. This is not needed since SM can initialize the topology and application models on-demand. Thanks. On Tue, Nov 10, 2015 at 4:12 AM, Imesh Gunaratne wrote:

Re: Error while undeploying an app on Kubernetes

I've fixed this and also added error logs if K8s cluster couldn't be removed. On Wed, Nov 11, 2015 at 3:25 PM, Gayan Gunarathne wrote: > > > On Wed, Nov 11, 2015 at 3:06 PM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Hi, >> >> I've created a JIRA to track this task [1]. It seems

[GitHub] stratos pull request: Renaming dashboards and updating ues-patch t...

GitHub user Thanu opened a pull request: https://github.com/apache/stratos/pull/490 Renaming dashboards and updating ues-patch to get rid of timeout This p/r includes following changes: 1. Updating ues-patch and member-details-filter.js to get rid of timeout. 2. Renaming mete

Re: [Dev] Publishing Complete Topology event on Demand

Hi, I've implemented the following improvements and merged in [1]. JIRAs created [2, 3, 4] to track these tasks. - On-demand initialization of complete topology - On-demand initialization of complete application topology - On-demand initialization of complete tenant model - On-demand initiali

Re: Error while undeploying an app on Kubernetes

On Wed, Nov 11, 2015 at 3:06 PM, Akila Ravihansa Perera wrote: > Hi, > > I've created a JIRA to track this task [1]. It seems a fix has been done > in [2] to resolve this. But I'm not sure why we have to iterate through all > the properties in [3]. Why not just do; > > partition.getProperties().g

[jira] [Resolved] (STRATOS-1544) Topology Initialization Optimization

[ https://issues.apache.org/jira/browse/STRATOS-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila resolved STRATOS-1544. Resolution: Fixed Implemented in 60b801144dcb05e3664353c412bc1c3fffd7c55c > Topology Initialization Optim

[jira] [Resolved] (STRATOS-1611) Application model initialization optimization

[ https://issues.apache.org/jira/browse/STRATOS-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila resolved STRATOS-1611. Resolution: Fixed Implemented in 60b801144dcb05e3664353c412bc1c3fffd7c55c > Application model initializat

[jira] [Resolved] (STRATOS-1612) Tenant Model and Complete Application SignUps Initialization Optimization

[ https://issues.apache.org/jira/browse/STRATOS-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila resolved STRATOS-1612. Resolution: Fixed Implemented in 60b801144dcb05e3664353c412bc1c3fffd7c55c > Tenant Model and Complete App

[jira] [Created] (STRATOS-1612) Tenant Model and Complete Application SignUps Initialization Optimization

Akila created STRATOS-1612: -- Summary: Tenant Model and Complete Application SignUps Initialization Optimization Key: STRATOS-1612 URL: https://issues.apache.org/jira/browse/STRATOS-1612 Project: Stratos

[jira] [Updated] (STRATOS-1544) Topology Initialization Optimization

[ https://issues.apache.org/jira/browse/STRATOS-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila updated STRATOS-1544: --- Component/s: Messaging Cloud Controller > Topology Initialization Optimization > --

[jira] [Created] (STRATOS-1611) Application model initialization optimization

Akila created STRATOS-1611: -- Summary: Application model initialization optimization Key: STRATOS-1611 URL: https://issues.apache.org/jira/browse/STRATOS-1611 Project: Stratos Issue Type: Improvement

Re: Error while undeploying an app on Kubernetes

Hi, I've created a JIRA to track this task [1]. It seems a fix has been done in [2] to resolve this. But I'm not sure why we have to iterate through all the properties in [3]. Why not just do; partition.getProperties().getProperty(KUBERNETES_CLUSTER) [1] https://issues.apache.org/jira/browse/STR

[jira] [Resolved] (STRATOS-1610) Stratos does not validate for currently in-use Kubernetes clusters when removing a Kubernetes cluster

[ https://issues.apache.org/jira/browse/STRATOS-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila resolved STRATOS-1610. Resolution: Fixed Assignee: Chamila de Alwis Fixed in b9ff2b10fa743c2eebca8468c99a9ef7ac528f42 > St

[jira] [Created] (STRATOS-1610) Stratos does not validate for currently in-use Kubernetes clusters when removing a Kubernetes cluster

Akila created STRATOS-1610: -- Summary: Stratos does not validate for currently in-use Kubernetes clusters when removing a Kubernetes cluster Key: STRATOS-1610 URL: https://issues.apache.org/jira/browse/STRATOS-1610

[jira] [Resolved] (STRATOS-1545) Startup order not getting validated when it is defined in the application

[ https://issues.apache.org/jira/browse/STRATOS-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam resolved STRATOS-1545. - Resolution: Fixed Added validation logic and integration test. Fixed in commit

[jira] [Updated] (STRATOS-1602) Reading dasStatsPublisherEabled value and metering and monitoring dashboard Urls at web application startup time and set those as application variables.

[ https://issues.apache.org/jira/browse/STRATOS-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanuja Uruththirakodeeswaran updated STRATOS-1602: --- Summary: Reading dasStatsPublisherEabled value and metering a

[jira] [Updated] (STRATOS-1602) Reading dasStatsPublisherEabled value and metering and monitoring dashboard Urls at web application startup time and set those as application variables and

[ https://issues.apache.org/jira/browse/STRATOS-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanuja Uruththirakodeeswaran updated STRATOS-1602: --- Description: In the current implementation, we are reading d

[jira] [Resolved] (STRATOS-1500) DAS Integration for Monitoring Service

[ https://issues.apache.org/jira/browse/STRATOS-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanuja Uruththirakodeeswaran resolved STRATOS-1500. Resolution: Fixed > DAS Integration for Monitoring Service