Re: Apache Stratos not works as expected

Hi Iago, Can you please attach the complete server side error log, wso2carbon.log, which is at /repository/logs/ directory. On Tue, Jul 19, 2016 at 7:30 PM, Iago Alonso Alonso wrote: > I'm trying to send orders to Apache Stratos via API REST but I'm unnable > to make it works. > > According to

[jira] [Resolved] (STRATOS-1662) Make CEP User Credentials Configurable

[ https://issues.apache.org/jira/browse/STRATOS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa resolved STRATOS-1662. Resolution: Implemented > Make CEP User Credentials Configura

[jira] [Commented] (STRATOS-1662) Make CEP User Credentials Configurable

[ https://issues.apache.org/jira/browse/STRATOS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356320#comment-15356320 ] Isuru Haththotuwa commented on STRATOS-1662: This is already fixed in

[jira] [Updated] (STRATOS-1662) Make CEP User Credentials Configurable

[ https://issues.apache.org/jira/browse/STRATOS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa updated STRATOS-1662: --- Fix Version/s: 4.1.0 > Make CEP User Credentials Configura

[jira] [Updated] (STRATOS-1662) Make CEP User Credentials Configurable

[ https://issues.apache.org/jira/browse/STRATOS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa updated STRATOS-1662: --- Description: Currently CEP user credentials are hard coded in the publishing

[jira] [Created] (STRATOS-1662) Make CEP User Credentials Configurable

Isuru Haththotuwa created STRATOS-1662: -- Summary: Make CEP User Credentials Configurable Key: STRATOS-1662 URL: https://issues.apache.org/jira/browse/STRATOS-1662 Project: Stratos Issue

Re: Stratos master branch is unstable

Hi Akila, On Thu, Jun 16, 2016 at 9:31 PM, Akila Ravihansa Perera < raviha...@apache.org> wrote: > Hi, > > It seems integration tests have not been running due to a change made in > [1] since 2015 Dec 8. Only tests under "policies" group have been running > since then. When I enabled all integrat

Re: Build failed in Jenkins: stratos » Apache Stratos - Integration Tests #436

Seems a issue with some dependency archives being corrupted. Will check locally. On Thu, May 12, 2016 at 4:05 AM, wrote: > See < > https://analysis.apache.org/jenkins/job/stratos/org.apache.stratos$stratos-test-integration/436/ > > > > -- > [INFO] > [INFO]

Re: Problem in deploying single cartridge app

Anand, CEP_HOME refers to the location in the file system where you have the CEP installed. If you are not using an external CEP, the Stratos can act as a CEP server as well. In this case, the jndi properties file is at apache-stratos-4.1.5/repository/conf/jndi.properties location. On Sat, Apr 9,

[jira] [Updated] (STRATOS-1656) AWS LB Extension Tries to Create Already Existing LBs and Fails

[ https://issues.apache.org/jira/browse/STRATOS-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa updated STRATOS-1656: --- Fix Version/s: FUTURE > AWS LB Extension Tries to Create Already Existing LBs

[jira] [Commented] (STRATOS-1656) AWS LB Extension Tries to Create Already Existing LBs and Fails

[ https://issues.apache.org/jira/browse/STRATOS-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173250#comment-15173250 ] Isuru Haththotuwa commented on STRATOS-1656: Removed redundant

[jira] [Resolved] (STRATOS-1656) AWS LB Extension Tries to Create Already Existing LBs and Fails

[ https://issues.apache.org/jira/browse/STRATOS-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa resolved STRATOS-1656. Resolution: Fixed > AWS LB Extension Tries to Create Already Existing LBs

[jira] [Updated] (STRATOS-1656) AWS LB Extension Tries to Create Already Existing LBs and Fails

[ https://issues.apache.org/jira/browse/STRATOS-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa updated STRATOS-1656: --- Affects Version/s: 4.1.5 > AWS LB Extension Tries to Create Already Existing

[jira] [Created] (STRATOS-1656) AWS LB Extension Tries to Create Already Existing LBs and Fails

Isuru Haththotuwa created STRATOS-1656: -- Summary: AWS LB Extension Tries to Create Already Existing LBs and Fails Key: STRATOS-1656 URL: https://issues.apache.org/jira/browse/STRATOS-1656

[jira] [Resolved] (STRATOS-1655) Proxy Support for AWS LB Extension

[ https://issues.apache.org/jira/browse/STRATOS-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa resolved STRATOS-1655. Resolution: Fixed > Proxy Support for AWS LB Extens

[jira] [Commented] (STRATOS-1655) Proxy Support for AWS LB Extension

[ https://issues.apache.org/jira/browse/STRATOS-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162748#comment-15162748 ] Isuru Haththotuwa commented on STRATOS-1655: Committed the changes

[jira] [Updated] (STRATOS-1655) Proxy Support for AWS LB Extension

[ https://issues.apache.org/jira/browse/STRATOS-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa updated STRATOS-1655: --- Affects Version/s: 4.1.5 > Proxy Support for AWS LB Extens

[jira] [Created] (STRATOS-1655) Proxy Support for AWS LB Extension

Isuru Haththotuwa created STRATOS-1655: -- Summary: Proxy Support for AWS LB Extension Key: STRATOS-1655 URL: https://issues.apache.org/jira/browse/STRATOS-1655 Project: Stratos Issue

Re: Build failed in Jenkins: stratos » Apache Stratos - Integration Tests #435

Although this is mentioned as a compilation issue, the error seems to be coming because of [1]. Maybe caused by be a corrupted archive. Will check locally. [1]. error: error reading /x1/jenkins/jenkins-master/jenkins-home/maven-repositories/0/org/apache/xerces/xml-apis/2.9.1/xml-apis-2.9.1.jar; er

Re: Stratos creating thread pools per application?

to document the list of thread > pools, their usage and how to tune them. > > Thanks > > > On Tuesday, January 5, 2016, Isuru Haththotuwa wrote: > >> The following are the list of improvements done: >> >>- make the threads pools dynamic by a

Re: Stratos creating thread pools per application?

using a static scheduled thread pool for all monitors Will commit the changes. On Thu, Dec 3, 2015 at 5:41 PM, Imesh Gunaratne wrote: > > > On Thu, Dec 3, 2015 at 10:20 AM, Isuru Haththotuwa > wrote: >> >> This is in addition to the scheduled executor services w

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

Ran a clean build on the 4.1.x branch locally, could not reproduce the test failures. On Sat, Dec 26, 2015 at 6:31 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > -- Thanks and Regards, Isuru H. +94 7

Re: Refactoring Event Receivers in Messaging Component

gt; > Thanks > > On Fri, Dec 4, 2015 at 5:19 AM, Isuru Haththotuwa > wrote: > >> Hi Devs, >> >> Started doing $subject. The Event Receiver model was designed when >> Stratos cannot be run on a single JVM, and it was not properly re-factored >> once the

Re: [Discuss] Executing rolling update on a service cluster

Hi Sajith, On Tue, Dec 15, 2015 at 5:41 PM, Sajith Kariyawasam wrote: > Hi Devs, > > At the moment in a Stratos deployment there is no easy way to do a rolling > update on a service cluster. One has to manually terminate all the running > instances of the cluster, after updating images / puppet

Re: Cleaning up User Artifacts at Signup Removal

h API changes, IMO can go for a major release from master branch after 4.1.5 is done, with all bug fixes + new features. > > Thanks. > > > On Thursday, 10 December 2015, Isuru Haththotuwa > wrote: > >> +1, will cherry pick the commits to master. >> >>

Re: Cleaning up User Artifacts at Signup Removal

-4.1.x branch by cherry-picking bug fixes/critical improvements. > > I think it's best if noone commits to stratos-4.1.x branch except for the > release manager. > > > > >> Thanks, >> Raj. >> >> On Wed, Dec 9, 2015 at 10:39 PM, Isuru Haththot

Re: [Discuss] Release Apache Stratos 4.1.5-RC3

Observed the stacktrace [1] at application undeployment in EC2. However the no impact on functionality, hence not a blocker for the release. Related jira [2]. [1]. [2015-12-09 17:15:38,789] INFO {org.apache.stratos.cloud.controller.iaases.JcloudsIaas} - Member terminated: [member-id] wso2as-521-

Re: [Vote] Release Apache Stratos 4.1.5-RC3.

+1. Verified: 1. Application deployment, signup addition/removal, and application undeployment on EC2 2. Application deployment/undeployment on Kubernetes. On Mon, Dec 7, 2015 at 4:52 PM, Gayan Gunarathne wrote: > > Hi All, > > This is the third release candidate of Apache Stratos 4.1

[jira] [Updated] (STRATOS-1637) Restore Initial Artifacts after a Signup is Removed for a Tenant

[ https://issues.apache.org/jira/browse/STRATOS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa updated STRATOS-1637: --- Fix Version/s: (was: FUTURE) 4.2.0 > Restore Init

[jira] [Commented] (STRATOS-1637) Restore Initial Artifacts after a Signup is Removed for a Tenant

[ https://issues.apache.org/jira/browse/STRATOS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048985#comment-15048985 ] Isuru Haththotuwa commented on STRATOS-1637: Fixed with com

[jira] [Resolved] (STRATOS-1637) Restore Initial Artifacts after a Signup is Removed for a Tenant

[ https://issues.apache.org/jira/browse/STRATOS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa resolved STRATOS-1637. Resolution: Fixed > Restore Initial Artifacts after a Signup is Removed fo

Re: Cleaning up User Artifacts at Signup Removal

On Wed, Dec 9, 2015 at 10:38 PM, Isuru Haththotuwa wrote: > This is not committed to stratos-4.1.x branch. > Correction: This is now committed to stratos-4.1.x branch. > > On Tue, Dec 1, 2015 at 7:34 PM, Isuru Haththotuwa > wrote: > >> Sent a PR [1] with the fix. >&

Re: Cleaning up User Artifacts at Signup Removal

This is not committed to stratos-4.1.x branch. On Tue, Dec 1, 2015 at 7:34 PM, Isuru Haththotuwa wrote: > Sent a PR [1] with the fix. > > [1]. https://github.com/apache/stratos/pull/498/ > > On Sun, Nov 29, 2015 at 9:18 PM, Isuru Haththotuwa > wrote: > >> >> &g

Re: [Discuss] Release Apache Stratos 4.1.5-RC2

ermination logic when the given >>member has not initiatlized >>- doap_Stratos.rdf file was not up to date with release versions >> >> Considering all of the above +1 to cancel this vote and go for 4.1.5-rc3. >> >> Thanks >> >> On Sun, Dec

Re: [Discuss] Release Apache Stratos 4.1.5-RC2

On Sun, Dec 6, 2015 at 12:37 AM, Akila Ravihansa Perera wrote: > I tried to deploy an application on EC2 and immediately undeployed it > which caused the following exception. Also the EC2 instance did not get > terminated. Noticed the following warning in the log; > > [2015-12-06 00:29:51,337] W

Re: [Vote] Release Apache Stratos 4.1.5-RC2

+1 Verified application life cycle in Amazon EC2 and mock IaaS. On Fri, Dec 4, 2015 at 10:20 PM, Dinithi De Silva wrote: > +1 for the release. > > Verified the Licence headers. > Built from source with integration tests. > Verified the application activation through the UI in mock IaaS. > Verif

Refactoring Event Receivers in Messaging Component

Hi Devs, Started doing $subject. The Event Receiver model was designed when Stratos cannot be run on a single JVM, and it was not properly re-factored once the Stratos single JVM distribution came up. So, all the main components (Stratos Manager, Cloud Controller, Autoscaler) has their own Message

Re: Stratos creating thread pools per application?

tos/blob/stratos-4.1.x/components/org.apache.stratos.autoscaler/src/main/java/org/apache/stratos/autoscaler/context/partition/ClusterLevelPartitionContext.java#L116-L121 >> >> [2] >> https://github.com/apache/stratos/blob/stratos-4.1.x/components/org.apache.stratos.autoscaler/src/main/java/o

Re: Stratos creating thread pools per application?

Hi Devs, Currently what we have is a static set of thread pools: 1. monitor thread pool 2. autoscaler thread pool 3. cartridge agent event listener thread pool 4. cloud controller context thread pool 5. cloud controller thread pool 6. cloud controller instance manager thread poo

Re: Refactoring Mock IaaS, Metadata API, Messaging Processor Chain, Integration Utils

Superb work Akila! Integration test are about three times faster now. Earlier it used to take ~45 mins, now run in ~15 mins. On Wed, Dec 2, 2015 at 6:48 PM, Imesh Gunaratne wrote: > Fabulous work Akila!! :-) > > On Mon, Nov 30, 2015 at 12:55 AM, Akila Ravihansa Perera < > raviha...@wso2.com> wro

[jira] [Created] (STRATOS-1639) Dynamic Thread Pool Implementation for StratosThreadPool

Isuru Haththotuwa created STRATOS-1639: -- Summary: Dynamic Thread Pool Implementation for StratosThreadPool Key: STRATOS-1639 URL: https://issues.apache.org/jira/browse/STRATOS-1639 Project

[jira] [Created] (STRATOS-1637) Restore Initial Artifacts after a Signup is Removed for a Tenant

Isuru Haththotuwa created STRATOS-1637: -- Summary: Restore Initial Artifacts after a Signup is Removed for a Tenant Key: STRATOS-1637 URL: https://issues.apache.org/jira/browse/STRATOS-1637

Re: Cleaning up User Artifacts at Signup Removal

Sent a PR [1] with the fix. [1]. https://github.com/apache/stratos/pull/498/ On Sun, Nov 29, 2015 at 9:18 PM, Isuru Haththotuwa wrote: > > > On Fri, Nov 27, 2015 at 11:51 AM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Hi Isuru, >> >>

Re: Jenkins build is still unstable: Stratos-41x-Commit-Build » Apache Stratos - Integration Tests #195

If the problem is due to too many logs getting accumulated, we might face this issue again. For the moment lets try to fix the test failure by fixing the connection issue to the Thrift server; that is the cause why lot of logs are there. I will check whether there is a known limitation in the Admin

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

I'm looking in to this. On Tue, Dec 1, 2015 at 11:02 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* * > > > *

Re: PCA Not Sending Complete Topology Request

; property (instead of MB_IP and MB_PORT). > Yes, I defined the MB_URL with IP:PORT, and left the username and password empty. There are no logs in the Agent side as well. Will check further on this. > > Thanks. > > On Mon, Nov 30, 2015 at 11:39 PM, Isuru Haththotuwa > wrote

PCA Not Sending Complete Topology Request

Hi Devs, In a EC2 instance, the PCA log does not show anything after [1]. Seems its not sending the complete topology event request. This might be a configuration issue, any idea what can be the issue? Packs are built from 4.1.x branch. [1]. ubuntu@138930111537:~$ tailf /tmp/agent.screen.log 2015

Re: Customizing serialization in Stratos to maintain backward compatibility of serialized data

option is to move the registry based data store to a >> database due to many reasons. Jane started this effort sometime back but it >> was halted. >> >> Thanks >> >> On Tue, Nov 24, 2015 at 3:35 PM, Isuru Haththotuwa >> wrote: >> >>> Hi D

[jira] [Created] (STRATOS-1635) Cartridge Agent Does not Check if the Local Git Repo Path is Valid

Isuru Haththotuwa created STRATOS-1635: -- Summary: Cartridge Agent Does not Check if the Local Git Repo Path is Valid Key: STRATOS-1635 URL: https://issues.apache.org/jira/browse/STRATOS-1635

[jira] [Created] (STRATOS-1634) Git Repo Password is Displayed in Plaintext in agent.screen.log

Isuru Haththotuwa created STRATOS-1634: -- Summary: Git Repo Password is Displayed in Plaintext in agent.screen.log Key: STRATOS-1634 URL: https://issues.apache.org/jira/browse/STRATOS-1634

Re: Cleaning up User Artifacts at Signup Removal

the suffix). Let's keep things simple as > possible :) > +1, maybe using a different suffix :) > > Thanks. > > On Fri, Nov 27, 2015 at 11:35 AM, Isuru Haththotuwa > wrote: > >> Hi, >> >> On Fri, Nov 27, 2015 at 11:13 AM, Gayan Gunarathne >> wrot

Re: Server Log Client for Stratos Integration Tests

Hi, On Sat, Nov 28, 2015 at 11:41 PM, Imesh Gunaratne wrote: > > > On Tue, Nov 24, 2015 at 5:45 PM, Isuru Haththotuwa > wrote: > >> Added a new API method to obtain logs in a incremental manner [1]. >> >> [1]. >> /** >> * Return all lo

Re: Cleaning up User Artifacts at Signup Removal

Thanks for all the responses. On Sat, Nov 28, 2015 at 11:26 PM, Imesh Gunaratne wrote: > > > On Fri, Nov 27, 2015 at 6:34 AM, Isuru Haththotuwa > wrote: >> >> >>1. Prior to the first clone, take a backup of the artifacts in the >>local repository

Re: [Vote] Release Apache Stratos 4.1.5-RC1

+1, Tested the basic application deployment flow in EC2 and in Mock Iaas. On Sat, Nov 28, 2015 at 10:06 PM, Gayan Gunarathne wrote: > Hi All, > > Please download, test and vote. The vote runs for 72 hours, until Sunday, > November 29, 2015, 08:30:00 AM PST,Sunday, November 29, 2015, 09:00:00 PM

Re: Cleaning up User Artifacts at Signup Removal

Hi, On Fri, Nov 27, 2015 at 11:13 AM, Gayan Gunarathne wrote: > Hi, > > On Fri, Nov 27, 2015 at 6:34 AM, Isuru Haththotuwa > wrote: > >> Hi Devs, >> >> Currently for a multiTenant Application (multiTenant=true), when a >> signup is removed, all artifacts

Cleaning up User Artifacts at Signup Removal

Hi Devs, Currently for a multiTenant Application (multiTenant=true), when a signup is removed, all artifacts which are in the local repository path will be deleted from the file system. But there are some cases where the runtime of the cartridge instance depends on some of the artifacts which were

Re: Integration test timeout issue

I see that we have upgraded TestNG version [1]. Do we still have the issue where the tests are run in parallel, even if we specify not to? [1]. https://issues.apache.org/jira/browse/STRATOS-1627 On Wed, Nov 25, 2015 at 4:23 PM, Akila Ravihansa Perera wrote: > Hi Gayan, > > I don't think timeout

Re: Server Log Client for Stratos Integration Tests

. * * @return all log lines, starting from the last log line returned * @throws AutomationUtilException */ public String[] getLogLines () throws AutomationUtilException On Sun, Nov 22, 2015 at 7:53 AM, Isuru Haththotuwa wrote: > Hi Devs, > > Added a $subje

Customizing serialization in Stratos to maintain backward compatibility of serialized data

Hi Devs, We are heavily using serialization to store context/runtime data throughout Stratos, and we depend on the default serialization mechanism provided by Java. The downside of this is if a Serialized class is changed (adding/removing a non-transient and non-static class variables), we cannot

[jira] [Resolved] (STRATOS-1631) Server Log Client to Retrieve Logs from Remote Carbon Servers

[ https://issues.apache.org/jira/browse/STRATOS-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa resolved STRATOS-1631. Resolution: Fixed > Server Log Client to Retrieve Logs from Remote Carbon Serv

[jira] [Commented] (STRATOS-1631) Server Log Client to Retrieve Logs from Remote Carbon Servers

[ https://issues.apache.org/jira/browse/STRATOS-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023876#comment-15023876 ] Isuru Haththotuwa commented on STRATOS-1631: Implemented in co

[jira] [Created] (STRATOS-1631) Server Log Client to Retrieve Logs from Remote Carbon Servers

Isuru Haththotuwa created STRATOS-1631: -- Summary: Server Log Client to Retrieve Logs from Remote Carbon Servers Key: STRATOS-1631 URL: https://issues.apache.org/jira/browse/STRATOS-1631 Project

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

Ran a clean build, did not get this. On Tue, Nov 24, 2015 at 11:01 AM, Gayan Gunarathne wrote: > Anyone experience this with local build? I am not experience this with > local build.Anyway I have triggered a new build in jenkins server. > > Thanks, > Gayan > > On Tue, Nov 24, 2015 at 8:34 AM, Ra

Re: File handle leak in Thrift

Shaheed, I could not find the jar with the mentioned version hosted in the relevant nexus repository [1]. Can you please double check if the version is correct? [1]. http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.databridge.agent.thrift/ On Mon, Nov 23, 2

Server Log Client for Stratos Integration Tests

Hi Devs, Added a $subject, class 'ServerLogClient'. This allows to monitor the back end logs of the Stratos server or any Carbon Server against which the integration tests are run, by providing the server URL. For an example, in a setup with multiple CEP nodes, we can use this to read the BE logs

Re: Updates done to CC configuration does not get reflected in spinning new instances

Committed an integration test to verify the scenario of IaaS properties getting properly picked and overridden when spawning instances. Commit ids: 28e65f2bf9c9b2f8f62173160b773368ac3b88f1 and 516609907b76b0078c0b0eef0c768793a8239720. On Wed, Nov 18, 2015 at 9:27 AM, Isuru Haththotuwa wrote

Re: Stratos creating thread pools per application?

Hi, +1 for a common Thread pool. On Sat, Nov 21, 2015 at 8:08 PM, Reka Thirunavukkarasu wrote: > Hi Akila, > > Yah..I think that we can share a common thread pool per monitor. AFAIK, > there was no specific reason to maintain thread pool per monitor object. > > @Gayan, Do you aware of any parti

Integration Test Failure in Branch 4.1.x

Hi Devs, Seeing $subject atm [1]. Will look in to this. [1]. Tests run: 28, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1,474.178 sec <<< FAILURE! - in TestSuite testApplicationStartupOrder(org.apache.stratos.integration.tests.application.ApplicationStartupOrderTestCase) Time elapsed: 0.03

Re: I want to join you to develop the Apache Stratos,to make it better,but still need some help from you all in this community

Hi Hank, Welcome to the Apache Stratos community! You are very welcome to contribute to Apache Stratos. The latest released version is 4.1.4, and you can refer the wiki [1] as a starting point. You can either try out Stratos using VM IaaSes like OpenStack/EC2, or using Containers with Kubernetes

Re: Initialized or Suspended state members are not tracked by stratos on restart

Good work Raj! On Thu, Nov 19, 2015 at 5:11 PM, Rajkumar Rajaratnam wrote: > This is fixed and available in 4.1.x branch. Relevant JIRA is STRATOS-1625. > > Thanks, > Raj. > > On Thu, Nov 19, 2015 at 5:01 PM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Nice catch Raj! >> >> Strato

[Stratos] [4.1.5] Message Type is Set to an Empty String when Using ClusterStatusProcessorChain

Hi, In ClusterMonitor [1] and AutoscalerTopologyEventReceiver [2] classes, there are two occasions where we are sending a message through the ClusterStatusProcessorChain with type set to an empty String [3, 4]. AFAIK the processor chain will determine which processor to use based on this type, and

Re: Stratos still trying to spawn members in wrong availability zone

operty) is set, else will check if the availabilityZone is set. > > > On Wednesday, 18 November 2015, Isuru Haththotuwa > wrote: > >> Did a quick fix to give priority to 'zone' over 'availabilityZone' when >> spinning instances. >> >

[jira] [Resolved] (STRATOS-1620) Stratos is not Picking up Updated IaasProvider properties in Cartridge

[ https://issues.apache.org/jira/browse/STRATOS-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa resolved STRATOS-1620. Resolution: Fixed > Stratos is not Picking up Updated IaasProvider properties

[jira] [Resolved] (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 resolved STRATOS-1613. Resolution: Fixed > The Image Id defined in the Cartridge Defintion Does not

[jira] [Commented] (STRATOS-1620) Stratos is not Picking up Updated IaasProvider properties in Cartridge

[ https://issues.apache.org/jira/browse/STRATOS-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010709#comment-15010709 ] Isuru Haththotuwa commented on STRATOS-1620: Fixed in Fixe

[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: (was: FUTURE) 4.1.5 > The Image Id defined

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15010708#comment-15010708 ] Isuru Haththotuwa commented on STRATOS-1613: Fixe

Re: Updates done to CC configuration does not get reflected in spinning new instances

lding. I have changed log level of the above message to debug. > > Thanks. > > On Mon, Nov 16, 2015 at 11:51 AM, Isuru Haththotuwa > wrote: > >> Hi Akila, >> >> On Mon, Nov 16, 2015 at 11:41 AM, Akila Ravihansa Perera < >> raviha...@wso2.com> wrote

Re: Stratos still trying to spawn members in wrong availability zone

Did a quick fix to give priority to 'zone' over 'availabilityZone' when spinning instances. On Wed, Nov 18, 2015 at 6:06 AM, Isuru Haththotuwa wrote: > AFAIU the reason for Stratos not picking the correct availability zone > from the NW partition is because we

Re: Stratos still trying to spawn members in wrong availability zone

AFAIU the reason for Stratos not picking the correct availability zone from the NW partition is because we have the property name as *availabilityZone *in the cloud-controller.xml and *zone *in the cartridge definition. So, it will not be overridden. On Wed, Nov 18, 2015 at 5:55 AM, Isuru

Re: Stratos still trying to spawn members in wrong availability zone

Hi Akila, Can you attach the complete log here? If you enable DEBUG logs for [1], we can get more information on what is the exact zone selected by Stratos prior to starting the instance. [1]. org.apache.stratos.cloud.controller.util.CloudControllerUtil On Wed, Nov 18, 2015 at 12:46 AM, Akila Ra

[jira] [Created] (STRATOS-1622) Runtime Error in Undeploying Application (Member does not Exist)

Isuru Haththotuwa created STRATOS-1622: -- Summary: Runtime Error in Undeploying Application (Member does not Exist) Key: STRATOS-1622 URL: https://issues.apache.org/jira/browse/STRATOS-1622

[jira] [Updated] (STRATOS-1621) NPE Application Undeployment

[ https://issues.apache.org/jira/browse/STRATOS-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa updated STRATOS-1621: --- Priority: Minor (was: Major) > NPE Application Undeploym

[jira] [Created] (STRATOS-1621) NPE Application Undeployment

Isuru Haththotuwa created STRATOS-1621: -- Summary: NPE Application Undeployment Key: STRATOS-1621 URL: https://issues.apache.org/jira/browse/STRATOS-1621 Project: Stratos Issue Type: Bug

[jira] [Updated] (STRATOS-1620) Stratos is not Picking up Updated IaasProvider properties in Cartridge

[ https://issues.apache.org/jira/browse/STRATOS-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa updated STRATOS-1620: --- Description: Steps to re-produce: 1. Update IaaS properties cartridge, delete the

[jira] [Created] (STRATOS-1620) Stratos is not Picking up Updated IaasProvider properties in Cartridge

Isuru Haththotuwa created STRATOS-1620: -- Summary: Stratos is not Picking up Updated IaasProvider properties in Cartridge Key: STRATOS-1620 URL: https://issues.apache.org/jira/browse/STRATOS-1620

Re: Updates done to CC configuration does not get reflected in spinning new instances

en if there are no changes to the object, we do not have to build again. > > Thanks. > > On Mon, Nov 16, 2015 at 10:40 AM, Isuru Haththotuwa > wrote: > >> One limitation of this approach is that JClouds will do a API call to >> validate the information that is provid

Re: Updates done to CC configuration does not get reflected in spinning new instances

cloud-controller.xml, policies and cartridgde >> definitions. WDYT? > > > +1. > This will also resolve the issue; having to delete and recreate > application, each time cartridge is updated. > > On Fri, Nov 13, 2015 at 4:44 PM, Isuru Haththotuwa > wrote: > >>

Re: Updates done to CC configuration does not get reflected in spinning new instances

aasProvider before starting an instance, we can use all the updates available from cloud-controller.xml, policies and cartridgde definitions. WDYT? Thanks. On Fri, Nov 13, 2015 at 2:03 PM, Isuru Haththotuwa wrote: > Hi Devs, > > $subject. > > This is happening because after initial i

Updates done to CC configuration does not get reflected in spinning new instances

Hi Devs, $subject. This is happening because after initial information model is built (IaasProvider object), it does not get re-built to detect any changes. The mail thread [1] also describes a similar issue, where if we do not specify image id in cloud-controller.xml, the instance not spawning i

Re: [Stratos 4.1.5] [Blocker] Issues with cartridge-config.properties file

Additionally, IMO we can rename this configuration file to have a generic name (stratos.xml/stratos.properties). wdyt? On Fri, Nov 13, 2015 at 12:53 PM, Gayan Gunarathne wrote: > Hi, > > On Fri, Nov 13, 2015 at 12:42 PM, Rajkumar Rajaratnam > wrote: > >> Hi Devs, >> >> This file content is as b

Re: AutoscalerHealthStatEventReceiver is sleeping for 15s at startup?

This can be similar to the issue Raj has explained in thread [1]. The HealthStat receiver is started before the information is loaded from the registry. We should start the HealthStat and Topology threads after loading the information from the registry. That might be the reason why we are waiting 1

Re: [Stratos 4.1.5] [Blocker] Monitors are not created on Stratos restart

On Fri, Nov 13, 2015 at 10:46 AM, Akila Ravihansa Perera wrote: > Nice catch Raj! > > I think better to wait until contexts/policies are loaded from registry > before starting AutoscalerTopologyReceiver. We're seeing this issue now > because topology is initialized immediately after starting the

Re: [Dev] Publishing Complete Topology event on Demand

models are initialized properly. > > [1] > https://github.com/apache/stratos/commit/60b801144dcb05e3664353c412bc1c3fffd7c55c > [2] https://issues.apache.org/jira/browse/STRATOS-1544 > [3] https://issues.apache.org/jira/browse/STRATOS-1612 > [4] https://issues.apache.org/jira/browse/STRATOS-1611 > > Thanks.

Re: PCA live test is failing

On Thu, Nov 12, 2015 at 3:54 PM, Pubudu Gunatilaka wrote: > PCA live tests were failing due to not having enough threads in the thread > pool. It is not the CEP HA mode test case but the agent startup test case > which was failing as it was waiting for the complete topology event to > receive. Th

[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

[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

[jira] [Resolved] (STRATOS-1603) NPE in re-deploying the Cartridges

[ https://issues.apache.org/jira/browse/STRATOS-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa resolved STRATOS-1603. Resolution: Fixed > NPE in re-deploying the Cartrid

[jira] [Comment Edited] (STRATOS-1603) NPE in re-deploying the Cartridges

[ https://issues.apache.org/jira/browse/STRATOS-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996317#comment-14996317 ] Isuru Haththotuwa edited comment on STRATOS-1603 at 11/10/15 10:0

  1   2   3   4   5   6   >