Re: Stratos and Kuburnetes and docker support.

Regarding health monitoring in containers, as discussed the best approach would be to use a well-known docker container monitoring tool such as cAdvisor coupled with a cartridge agent instance per controller node. Why do we use the term "replicas" for the Kubernetes control node instances? Are we

Re: [Discuss] Coding Standards & Best Practices Guidelines

Thanks for the reminder Imesh. I've created a Jira for this https://issues.apache.org/jira/browse/STRATOS-813 On Tue, Sep 23, 2014 at 10:31 AM, Imesh Gunaratne wrote: > It's nice to see everyone is focusing on $subject. I just went through the > latest Sonar findings and seems like there are nea

[jira] [Created] (STRATOS-813) Fix critical issues reported by Sonar

Nirmal Fernando created STRATOS-813: --- Summary: Fix critical issues reported by Sonar Key: STRATOS-813 URL: https://issues.apache.org/jira/browse/STRATOS-813 Project: Stratos Issue Type: Imp

Re: [Discuss] Coding Standards & Best Practices Guidelines

+1 on 4 spaces. Since there is python code in the project, 4 spaces is the better option in terms of consistency. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Mon, Sep 22, 2014 at 4:39 PM, Isuru Perera wrote: > Hi everyone, > > I think w

Re: subscribe

Ack On Tue, Sep 23, 2014 at 11:22 AM, Thushara Ranawaka wrote: > > > -- > Thushara Kasun Ranawaka > Software Engineer > WSO2 Inc.; > lean.enterprise.middleware > Mobile : *+94 (0) 773438949 <%2B94%20%280%29%20773438949>* > *thusha...@wso2.com * > -- Regards, Manula Chat

subscribe

-- Thushara Kasun Ranawaka Software Engineer WSO2 Inc.; lean.enterprise.middleware Mobile : *+94 (0) 773438949* *thusha...@wso2.com *

Re: [Hangout] Stratos Cluster Monitoring Improvement - Design and Code review

Hi Imesh, You can find more information on the mail thread "Stratos Cluster Monitoring" Thanks. On Tue, Sep 23, 2014 at 10:38 AM, Imesh Gunaratne wrote: > Hi Rajkumar, > > Can you please point me to a mail thread/wiki page where we have more > information on this improvement? > > Thanks > > On

Re: Messaging Component Architecture

We have some information here, but not on implementation details: https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Stratos+Pub-Sub+Communication On Thu, Sep 18, 2014 at 1:09 AM, Isuru Haththotuwa wrote: > Hi Devs, > > Do we have information/documents about $subject? > > -- > Thanks and

[GitHub] stratos pull request: Removed mistakenly added Tenant event listen...

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

Re: [Hangout] Stratos Cluster Monitoring Improvement - Design and Code review

Hi Rajkumar, Can you please point me to a mail thread/wiki page where we have more information on this improvement? Thanks On Mon, Sep 22, 2014 at 11:00 AM, Lakmal Warusawithana wrote: > +1 > > On Mon, Sep 22, 2014 at 4:51 PM, Rajkumar Rajaratnam > wrote: > >> Hi all, >> >> Can we have $Subje

Re: [Discuss] Coding Standards & Best Practices Guidelines

It's nice to see everyone is focusing on $subject. I just went through the latest Sonar findings and seems like there are nearly 270 critical issues: https://analysis.apache.org/drilldown/issues/org.apache.stratos:stratos-parent?severity=CRITICAL We can go through the list and fix these issues, o

Cloud Controller Architecture Docs are missing!

Hi Mari, I cannot find the CC architecture docs we had. Do you have any idea what happened to them? -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/

Avoid Git merge commits - keep the history clean

Hi Devs, I think it's better if we can keep the commit history clean in our repo. It will allow us to clearly see the dev work going on. Here are some articles [1, 2] that explains how to get rid of merge commits and also ways to keep history clean. Basically we can use rebase option in Git to get

Re: MQTT client library for Stratos messaging component.

Hi Gayan, May be following tips would help to separate your existing changes in to formatting and business logic without reformatting. [1] deals with removing white space from the changes, but additionally [2], git add -p, allows selecting the sections that need to be staged for a particular commi

[jira] [Updated] (STRATOS-812) Longetivity test issue: VMs spawned and Stratos threw OutOfMemoryError

[ https://issues.apache.org/jira/browse/STRATOS-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Nguyen updated STRATOS-812: --- Description: We have observed this issue on multiple testbeds where we observed VMs were bei

[jira] [Created] (STRATOS-812) Longetivity test issue: VMs spawned and Stratos threw OutOfMemoryError

Jeffrey Nguyen created STRATOS-812: -- Summary: Longetivity test issue: VMs spawned and Stratos threw OutOfMemoryError Key: STRATOS-812 URL: https://issues.apache.org/jira/browse/STRATOS-812 Project: S

[jira] [Updated] (STRATOS-812) Longetivity test issue: VMs spawned and Stratos threw OutOfMemoryError

[ https://issues.apache.org/jira/browse/STRATOS-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Nguyen updated STRATOS-812: --- Attachment: debug_info_20140922.tar.gz > Longetivity test issue: VMs spawned and Stratos thre

[GitHub] stratos pull request: Fixed hard coded strings in stratos-installe...

GitHub user chamilad opened a pull request: https://github.com/apache/stratos/pull/49 Fixed hard coded strings in stratos-installer setup.sh script You can merge this pull request into a Git repository by running: $ git pull https://github.com/chamilad/stratos hardcoded-string

Re: [Hangout] Stratos Cluster Monitoring Improvement - Design and Code review

+1 On Mon, Sep 22, 2014 at 4:51 PM, Rajkumar Rajaratnam wrote: > Hi all, > > Can we have $Subject tomorrow (Tue, September 23) at 7:30 PM GMT+5:30 ? > > We will be reviewing about the changes done to existing cluster > monitor hierarchy to allow any 'entity' cluster monitors to be plugged in > a

Rajkumar Rajaratnam canceled Stratos Cluster Monitoring Improvement - Design and Code review

Rajkumar Rajaratnam canceled the event Tue, September 23, 7:30 PM GMT+5:30 Be thoughtful about who you share this email with; anyone can reshare it. This notification was sent to dev@stratos.apache.org; Go to your notification delivery settings to update your address: https://plus.google.com/

Invitation: Stratos Cluster Monitoring Improvement @ Tue Sep 23, 2014 7:30pm - 8:30pm (Rajkumar Rajaratnam)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20140923T14Z DTEND:20140923T15Z DTSTAMP:20140922T105057Z ORGANIZER;CN=Rajkumar Rajaratnam:mailto:rajkum...@wso2.com UID:pvo9telmv79t5b4c504km0t...@google.com

[GitHub] stratos pull request: Removed mistakenly added Tenant event listen...

GitHub user chamilad opened a pull request: https://github.com/apache/stratos/pull/48 Removed mistakenly added Tenant event listeners Removed mistakenly added Tenant event listeners Removed unused extension util methods Removed unused methods and imports in CartridgeAgent Yo

Use of hard coded strings in setup.sh

Hi, The setup.sh script in stratos-installer uses a couple of hard coded strings in its operations. These strings are set in setup.conf, but not used. I opened a jira issue at [1] and submitted a PR[2]. [1] - https://issues.apache.org/jira/browse/STRATOS-811 [2] - https://github.com/apache/strat

[jira] [Created] (STRATOS-811) Hard coded strings in setup.sh

Chamila de Alwis created STRATOS-811: Summary: Hard coded strings in setup.sh Key: STRATOS-811 URL: https://issues.apache.org/jira/browse/STRATOS-811 Project: Stratos Issue Type: Improvem

[jira] [Created] (STRATOS-810) Improve User Experience on Stratos managment console

Dakshika Jayathilaka created STRATOS-810: Summary: Improve User Experience on Stratos managment console Key: STRATOS-810 URL: https://issues.apache.org/jira/browse/STRATOS-810 Project: Stratos

Re: MQTT client library for Stratos messaging component.

What is the code format template are we following previously? This is to revert the code with the previous code format. Thanks, Gayan On Mon, Sep 22, 2014 at 5:03 PM, Isuru Haththotuwa wrote: > > > On Mon, Sep 22, 2014 at 4:45 PM, Isuru Perera wrote: > >> Hi Gayan, >> >> IMHO, the formatting s

Re: Meta Data Service Client as a Separate Component

Hi Lahiru, We faced some issues with RestEasy library and JAX-RS based libraries. We couldn't get them to work within the Carbon platform because of some ClassDef not found issue. So I guess we will have to stick with Apache HTTP library and write a wrapper. On Mon, Sep 22, 2014 at 5:32 PM, Lahir

Re: Meta Data Service Client as a Separate Component

+1 for a generic client as code would be easy to manage if so. Nirmal has suggested "RestEasy" at the thread "Java client for Kubernetes REST API". It seems that is a good library. Shall we stick to that? Thanks. On Fri, Sep 19, 2014 at 1:12 PM, Sajith Kariyawasam wrote: > > On Thu, Sep 18, 20

Re: Accessing Tenant information in Cartridge Agent

On Mon, Sep 22, 2014 at 3:28 PM, Akila Ravihansa Perera wrote: > Best approach would be to blockingly wait until > CompleteTopologyEvent and CompleteTenantEvent are received > This seems to be the best option for now. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code

[Hangout] Stratos Cluster Monitoring Improvement - Design and Code review

Hi all, Can we have $Subject tomorrow (Tue, September 23) at 7:30 PM GMT+5:30 ? We will be reviewing about the changes done to existing cluster monitor hierarchy to allow any 'entity' cluster monitors to be plugged in and the initial version of docker cluster monitoring. Thanks. -- Rajkumar Ra

Re: Tenant listeners added twice in the Cartridge Agent

Hi Akila, I made the changes and created a PR [1]. Please review and merge. 1 - https://github.com/apache/stratos/pull/48 Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Mon, Sep 22, 2014 at 2:33 PM, Akila Ravihansa Perera wrote: > Hi Cha

Re: [Discuss] Coding Standards & Best Practices Guidelines

On Mon, Sep 22, 2014 at 4:39 PM, Isuru Perera wrote: > Hi everyone, > > I think we should agree on whether we should use tabs or spaces for the > indentation. > > I'm suggesting that we should use 4 spaces for the indentation and > completely avoid tabs in our code. +1 Tabs can mess up the code

Re: MQTT client library for Stratos messaging component.

On Mon, Sep 22, 2014 at 4:45 PM, Isuru Perera wrote: > Hi Gayan, > > IMHO, the formatting should be done with a different commit. > +1 > The problem is that you have done logic changes along with formatting. I > can't figure out what you changed in the code to support MQTT. > > As a practice, I

Re: MQTT client library for Stratos messaging component.

Hi Gayan, IMHO, the formatting should be done with a different commit. The problem is that you have done logic changes along with formatting. I can't figure out what you changed in the code to support MQTT. As a practice, I usually try to keep the diff minimum when doing code changes and do forma

Re: [Discuss] Coding Standards & Best Practices Guidelines

Hi everyone, I think we should agree on whether we should use tabs or spaces for the indentation. I'm suggesting that we should use 4 spaces for the indentation and completely avoid tabs in our code. I can help to come up with an Eclipse Formatter profile. We should also format the entire code b

Re: MQTT client library for Stratos messaging component.

Hi Isuru, Yeah.It is formatted according to the discussion[1].In the GIT source comparing window it may show white spaces due to this.Is n't? Please find the following code as it is formatted as the discussion[1]. https://github.com/gayangunarathne/stratos/blob/msgtopichierachchy-1/components/or

Re: [Discuss] [Grouping] Specifying Dependency Information in Group Definition

Hi Gayan, Thanks for the input. On Mon, Sep 22, 2014 at 10:36 AM, Gayan Gunarathne wrote: > > Hi Isuru, > > On Sun, Sep 21, 2014 at 1:34 PM, Isuru Haththotuwa > wrote: > >> Hi Devs, >> >> In Service Grouping, a cartridge that is depending on another might need >> some information (endpoint, et

Rajkumar Rajaratnam invited you to Stratos Cluster Monitoring Improvement - Design and Code review

Rajkumar Rajaratnam invited you to Stratos Cluster Monitoring Improvement - Design and Code review Tue, September 23, 7:30 PM GMT+5:30 2 people invited View Invitation: https://plus.google.com/_/notifications/ngemlink?&emid=CMCGkZ7N9MACFauzQgod4GAAbw&path=%2Fevents%2Fcmtg4pgccfrr9aujat2s6d07e

Re: MQTT client library for Stratos messaging component.

Your PR seems to be messed up due to white space changes :( Did you format classes? On Mon, Sep 22, 2014 at 2:39 PM, Gayan Gunarathne wrote: > Hi All, > > I have changed the Stratos messaging model to support MQTT. > > Please find the pull request for this. > > https://github.com/apache/stratos

Re: Accessing Tenant information in Cartridge Agent

Hi Chamila, Complete events are meant to be used in a recovery or initialization process. It should build up the information model using the CompleteTopologyEvent or CompleteTenantEvent and then only listen to individual events. Best approach would be to blockingly wait until CompleteTopologyEvent

[jira] [Resolved] (STRATOS-809) Removing unncessray logs in apache:4.0.0-grouping

[ https://issues.apache.org/jira/browse/STRATOS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gayan Gunarathne resolved STRATOS-809. -- Resolution: Fixed Pull request - https://github.com/apache/stratos/pull/41 Commit ID -

Re: Accessing Tenant information in Cartridge Agent

CompleteTenantEvent has the list of tenants, however is the order in which the events are fired reliable? As I understand from the code, a CompleteTenantEvent is scheduled to fire with a delay, when any one of the other tenant events could be received before a CompleteTenantEvent. Regards, Chamil

[jira] [Created] (STRATOS-809) Removing unncessray logs in apache:4.0.0-grouping

Gayan Gunarathne created STRATOS-809: Summary: Removing unncessray logs in apache:4.0.0-grouping Key: STRATOS-809 URL: https://issues.apache.org/jira/browse/STRATOS-809 Project: Stratos I

Re: Tenant listeners added twice in the Cartridge Agent

Hi Chamila, Yes, my bad. Tenant listeners in subscribeToTopicsAndRegisterListeners() should be removed. Great work in finding these flaws. Appreciate if you could send a PR with fixes. Thanks On Mon, Sep 22, 2014 at 1:08 PM, Chamila De Alwis wrote: > Hi Akila, > > The listeners in registerTena

[jira] [Commented] (STRATOS-791) MQTT protocol support for the messaging module

[ https://issues.apache.org/jira/browse/STRATOS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143042#comment-14143042 ] Gayan Gunarathne commented on STRATOS-791: -- Pull request - https://github.com/ap

Re: MQTT client library for Stratos messaging component.

Hi All, I have changed the Stratos messaging model to support MQTT. Please find the pull request for this. https://github.com/apache/stratos/pull/47 Also I have updated the relevant JIRA(STRATOS-791) as well. Thanks, Gayan On Thu, Sep 11, 2014 at 12:58 PM, Gayan Gunarathne wrote: > Hi All

[jira] [Commented] (STRATOS-790) Messaging module refactoring to remove header based message distingushment

[ https://issues.apache.org/jira/browse/STRATOS-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143040#comment-14143040 ] Gayan Gunarathne commented on STRATOS-790: -- Pull request - https://github.com/ap

[GitHub] stratos pull request: Messaging model changes and MQTT integration

GitHub user swgkg opened a pull request: https://github.com/apache/stratos/pull/47 Messaging model changes and MQTT integration Please review and merge You can merge this pull request into a Git repository by running: $ git pull https://github.com/gayangunarathne/stratos msgtop

[jira] [Commented] (STRATOS-807) Re-designing cluster monitor hierarchy to support any 'entity' monitors to be plugged in

[ https://issues.apache.org/jira/browse/STRATOS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143018#comment-14143018 ] Lakmal Warusawithana commented on STRATOS-807: -- On Mon, Sep 22, 2014 at 12:2

[GitHub] stratos pull request: STRATOS-807

GitHub user R-Rajkumar opened a pull request: https://github.com/apache/stratos/pull/46 STRATOS-807 You can merge this pull request into a Git repository by running: $ git pull https://github.com/R-Rajkumar/stratos master-cluster-monitors Alternatively you can review and appl

[GitHub] stratos pull request: Msgtopichierachchy

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

Re: [jira] [Created] (STRATOS-807) Re-designing cluster monitor hierarchy to support any 'entity' monitors to be plugged in

On Mon, Sep 22, 2014 at 12:23 PM, Rajkumar Rajaratnam (JIRA) < j...@apache.org> wrote: > Rajkumar Rajaratnam created STRATOS-807: > --- > > Summary: Re-designing cluster monitor hierarchy to support > any 'entity' monitors to be plugged in >

[GitHub] stratos pull request: Msgtopichierachchy

GitHub user swgkg opened a pull request: https://github.com/apache/stratos/pull/45 Msgtopichierachchy Pull request You can merge this pull request into a Git repository by running: $ git pull https://github.com/gayangunarathne/stratos msgtopichierachchy Alternatively you

[jira] [Commented] (STRATOS-807) Re-designing cluster monitor hierarchy to support any 'entity' monitors to be plugged in

[ https://issues.apache.org/jira/browse/STRATOS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143012#comment-14143012 ] ASF GitHub Bot commented on STRATOS-807: GitHub user R-Rajkumar opened a pull req

Re: Tenant listeners added twice in the Cartridge Agent

>From Git blame annotations, it looks like the additional paths for these two event listeners are added possibly by merging by accident. Because one path passes variables that are not picked up by the shell script extensions, no visible errors are occurring. Regards, Chamila de Alwis Software Eng

Re: Tenant listeners added twice in the Cartridge Agent

Hi Akila, The listeners in registerTenantEventListeners() are invoking extension handling through the DefaultExtensionHandler. The tenant event listeners added in subscribeToTopicsAndRegisterListeners() are not, so they must be removed, along with the additional methods in ExtensionUtils. Regard

Re: Tenant listeners added twice in the Cartridge Agent

Hi Chamila, On Mon, Sep 22, 2014 at 1:03 PM, Chamila De Alwis wrote: > From Git blame annotations, it looks like the additional paths for these > two event listeners are added possibly by merging by accident. Because one > path passes variables that are not picked up by the shell script > extens

Re: Tenant listeners added twice in the Cartridge Agent

Hi Chamila, Looks like there is a flaw in the logic. The extension should be invoked via DefaultExtensionHandler. This could be a merge conflict. Also we should refactor cartridge agent to support customizable extension handlers. I've created a JIRA to track this task [1]. Tenant listeners under

[jira] [Created] (STRATOS-808) Re-factor Cartridge Agent Extension Handling

Akila created STRATOS-808: - Summary: Re-factor Cartridge Agent Extension Handling Key: STRATOS-808 URL: https://issues.apache.org/jira/browse/STRATOS-808 Project: Stratos Issue Type: Improvement