Re: [Hangout] Discussion and Review on Hierarchical Topology Locking

2014-10-19 Thread Isuru Haththotuwa
Please find the link to the hangout at [1]. Will start in 15 minutes. [1]. https://plus.google.com/hangouts/_/hoaevent/AP36tYdSfm6LfEP4266FVE8qz2XxjnWFTyb9yNsY6cSfT3q_TY7_Sg?pqs=1&authuser=0&hl=en On Fri, Oct 17, 2014 at 10:31 AM, Dinesh Bandara wrote: > +1 > > On Thu, Oct 16, 2014 at 5:28 PM,

Re: Commits enabled payload parameter

2014-10-19 Thread Mariangela Hills
Hi Akila, Page [1] discusses auto commit. While, [2] and [3] mention how it can be used. Please let me know whether any more information needs to be added to these pages. [1] https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Artifact+Distribution+Coordinator#id-4.0.0ArtifactDistributionC

Re: [Grouping] Shall we clean unused code block

2014-10-19 Thread Reka Thirunavukkarasu
Hi On Mon, Oct 20, 2014 at 6:54 AM, Martin Eppel (meppel) wrote: > If you guys are ok I can start cleaning up this code (since most of it > comes from the POC anyway), WDYT ? > +1 Martin. We will also clean the code from our end which added by us. Thanks, Reka > > > Regards > > > > Martin > >

[jira] [Created] (STRATOS-898) Add information on Messaging Component Architecture

2014-10-19 Thread Mariangela Hills (JIRA)
Mariangela Hills created STRATOS-898: Summary: Add information on Messaging Component Architecture Key: STRATOS-898 URL: https://issues.apache.org/jira/browse/STRATOS-898 Project: Stratos

Re: Messaging Component Architecture

2014-10-19 Thread Mariangela Hills
I will add this blogpost to wiki. I have created a JIRA [1] to track this task. [1] https://issues.apache.org/jira/browse/STRATOS-898 Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com

RE: [Grouping] Shall we clean unused code block

2014-10-19 Thread Martin Eppel (meppel)
If you guys are ok I can start cleaning up this code (since most of it comes from the POC anyway), WDYT ? Regards Martin From: Imesh Gunaratne [mailto:im...@apache.org] Sent: Friday, October 17, 2014 10:30 PM To: dev Cc: Udara Liyanage; Isuru Haththotuwa; Reka Thirunavukkarasu Subject: Re: [Gro

Re: [GitHub] stratos pull request: Initial GCE commit

2014-10-19 Thread Nirmal Fernando
Please close the PR. On Sun, Oct 19, 2014 at 6:09 PM, nirmal070125 wrote: > Github user nirmal070125 commented on the pull request: > > https://github.com/apache/stratos/pull/92#issuecomment-59654601 > > Thanks Suriya for the PR. I've merged it! Great work ! > > > --- > If your project i

[GitHub] stratos pull request: Initial GCE commit

2014-10-19 Thread nirmal070125
Github user nirmal070125 commented on the pull request: https://github.com/apache/stratos/pull/92#issuecomment-59654601 Thanks Suriya for the PR. I've merged it! Great work ! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well

Re: [DISCUSS] Achieving HA or 100% (99.999%) uptime for apache stratos

2014-10-19 Thread Imesh Gunaratne
On Sun, Oct 19, 2014 at 9:26 PM, Lakmal Warusawithana wrote: > > Imesh is working on how you can achieved active/passive with Stratos > 4.0.0. But we are working on active/active for all stratos core with > clustering support which going to address both high availability and > scalability. IMO we

Re: [DISCUSS] Achieving HA or 100% (99.999%) uptime for apache stratos

2014-10-19 Thread Lakmal Warusawithana
On Sat, Oct 18, 2014 at 12:19 PM, Imesh Gunaratne wrote: > Hi Martin, > > Please find my comments inline: > > On Fri, Oct 17, 2014 at 11:38 PM, Martin Eppel (meppel) > wrote: > >> I would like to discuss what it would take to achieve 100% uptime for >> stratos in a production environment (aimin

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

2014-10-19 Thread Imesh Gunaratne
+1 On Sat, Oct 18, 2014 at 11:07 PM, Isuru Haththotuwa wrote: > The initial API for validating and changing states will support the > following methods: > > >/** > * Checks if the state transition is valid > * > * @param nextState Next state that for the topology element >