Re: Merged the AWS load balancer to Stratos 4.1.x branch

It was in a load balancer parant folder.Now I have moved it to the modules folder and remove the aws lb in parent folder. Thanks, Gayan On Mon, Oct 12, 2015 at 2:18 AM, Akila Ravihansa Perera wrote: > Hi Gayan, > > There was a build break caused by this merge because the parent > relativePath

[GitHub] stratos pull request: Fixed issue with logging in pca

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

Re: Improvements for Python cartridge agent

Noted, will do! Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 On Sun, Oct 11, 2015 at 10:16 PM, Akila Ravihansa Perera wrote: > Hi Mari, > > Will you be a

Re: Refining Python Cartridge Agent log levels

Hi All, This issue has been resolved now. Thanks. On Thu, Oct 8, 2015 at 12:01 PM, Thanuja Uruththirakodeeswaran < thanu...@wso2.com> wrote: > Hi All, > > I have started on $subject because logs we get in PCA is like bit > cumbersome and this issue is tracked in a jira [1]. We have to refine th

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

See

Jenkins build is unstable: Stratos-41x-Commit-Build #84

See

Build failed in Jenkins: Stratos-41x-Nightly-Build #34

See Changes: [ravihansa3000] Fix STRATOS-1572: Network partition availability zone setting has no [gayang] Added instanceId field to Member class and exposed it through topology. [ravihansa3000] Fix STRATOS-1578: Handle regis

Build failed in Jenkins: Stratos-41x-Nightly-Build » Apache Stratos - Common #34

See -- [INFO] [INFO]

Re: Merged the AWS load balancer to Stratos 4.1.x branch

Hi Gayan, There was a build break caused by this merge because the parent relativePath in aws-lb-extension was not correct. I've fixed it now. I think we should run a complete build in a clean m2 repo before merging these PRs. Thanks. On Sun, Oct 11, 2015 at 4:28 PM, Gayan Gunarathne wrote: >

Build failed in Jenkins: Stratos-41x-Commit-Build #83

See Changes: [ravihansa3000] Fix STRATOS-1578: Handle registry exceptions in higher levels to avoid [ravihansa3000] Rename startup test case artifacts -- Started by user ravihansa [EnvIn

[jira] [Resolved] (STRATOS-1578) Removing a member from CloudControllerContext and Topology should be executed atomically

[ https://issues.apache.org/jira/browse/STRATOS-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila resolved STRATOS-1578. Resolution: Fixed Fix Version/s: (was: FUTURE) 4.1.4 Fixed in 8d46fab0f921e3

Re: Make CRUD operations executed on Topology and CloudControllerContext as atomic

Hi, I've fixed most of these cases we discussed here. To summarize; - Registry exceptions should always be thrown from persist() method and should be handled by the methods that are calling it - If service name, cluster id or member id is not found in the Topology, a RuntimeException should be

Re: Improvements for Python cartridge agent

Hi Mari, Will you be able to add this information to a relevant Wiki page? Basically this is a new feature which allows users to plugin their own custom logic to artifact sync task. I've added a summary of this in JIRA at [1]. A sample can be found at [2]. [1] https://issues.apache.org/jira/brows

[jira] [Commented] (STRATOS-1549) Move PCA artifact distribution coordinator logic to a separate plugin

[ https://issues.apache.org/jira/browse/STRATOS-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952332#comment-14952332 ] Akila commented on STRATOS-1549: Introduced two new extension points for PCA as follows.

Jenkins build is still unstable: Stratos-41x-Commit-Build #82

See

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

See

[GitHub] stratos pull request: Google compute engine load balancing support

Github user asankasanjaya commented on the pull request: https://github.com/apache/stratos/pull/433#issuecomment-147193032 I have changed the logic for health check creation. So health checks are created using the port map configuration related to the application instead of using the

Re: NPE while executing Drool methods - Integration tests are failing

Seems even application is terminated, some of the group monitors are still running. Mostly in the nested group scenario. Those group monitors looking for the application monitor that didn't exist at that time.So I think we need to recheck the logic of group monitor termination logic in the applicat

Merged the AWS load balancer to Stratos 4.1.x branch

Now I have merged the AWS LB extension[1] to the gsoc-projects-2015 and added the same thing to the Stratos-4.1.x branch.Will merge other projects one by one. Thanks Swapnil for your contribution. [1] https://github.com/apache/stratos/pull/438 Thanks, Gayan -- Gayan Gunarathne Technical Lead,

Jenkins build is unstable: Stratos-41x-Commit-Build #81

See

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

See

Re: Openstack Availability zone settings in partition definition not working

Hi, This is now fixed in stratos-4.1.x branch. I've tested and verified in ec2, openstack, GCE. I fixed another minor issue in GCE IaaS which caused partition validation exception to be thrown when availabilityZone is defined in network partition. This is becuase GCE validator checks for region st

[jira] [Commented] (STRATOS-1572) Network partition availability zone setting has no affect on VMs launched by CC

[ https://issues.apache.org/jira/browse/STRATOS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952226#comment-14952226 ] Akila commented on STRATOS-1572: Fixed in 02d01071c77b50be246c49d0841e4a1f8b8e2b02 > Ne

[jira] [Resolved] (STRATOS-1572) Network partition availability zone setting has no affect on VMs launched by CC

[ https://issues.apache.org/jira/browse/STRATOS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila resolved STRATOS-1572. Resolution: Fixed Assignee: Akila Fix Version/s: (was: FUTURE) 4.1.4