Hi Nirmal,
Here are the docs [1]. The docs need to be updated. I have created a JIRA
[2] to track this task.
[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=46632980
[2] https://issues.apache.org/jira/browse/STRATOS-821
Regards,
Mariangela
*--*
Mariangela Hills
Senior Te
On Tue, Sep 23, 2014 at 9:25 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Hi Chamila,
>
> +1 for test cases. Are you going to test auto-scaling as well ? What I
> mean here is publishing summarize health stats from python cartridge agent
> and according to those health stats we
Mariangela Hills created STRATOS-821:
Summary: [Wiki] Update CC documentation
Key: STRATOS-821
URL: https://issues.apache.org/jira/browse/STRATOS-821
Project: Stratos
Issue Type: Bug
On Tue, Sep 23, 2014 at 9:25 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Hi Chamila,
>
> +1 for test cases. Are you going to test auto-scaling as well ? What I
> mean here is publishing summarize health stats from python cartridge agent
> and according to those health stats we
Nicely articulated Chamila! What's your plan to implement these tests?
On Tue, Sep 23, 2014 at 8:34 PM, Chamila De Alwis wrote:
> Hi,
>
> For $subject, we decided to implement the following steps.
>
> Following aspects need to be tested from agent's point of view.
>
> 1) Listening to and publish
[
https://issues.apache.org/jira/browse/STRATOS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills resolved STRATOS-672.
--
Resolution: Duplicate
Fix Version/s: 4.1.0 M1
Hi Martin,
This has been discusse
Hi Martin,
Seems this model might not work if there are only cartridges at the
application without Groups. We can specify an application without Groups,
but with multiple single cartridge subscriptions. In that case also, we may
need to share some information.
For now, I will revert the commit. P
Github user nirmal070125 commented on the pull request:
https://github.com/apache/stratos/pull/38#issuecomment-56629499
Hi Lasindu,
There's a merge conflict at ADCManagementServerComponent class. Please
rebase and update the PR. Thanks.
---
If your project is set up for it,
Hi All,
Now I can access it.
On Wed, Sep 24, 2014 at 11:36 AM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> $subject. It is down today ?
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> email
Hi Manula,
It works for me [1].
[1] https://cwiki.apache.org/confluence/display/STRATOS/4.0.0
On Wed, Sep 24, 2014 at 11:36 AM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> $subject. It is down today ?
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2
Works for me. Are you having a host entry ?
On Wed, Sep 24, 2014 at 11:36 AM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> $subject. It is down today ?
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middlew
Sure. I will send the pull request for this.
On Wed, Sep 24, 2014 at 10:49 AM, nirmal070125 wrote:
> Github user nirmal070125 commented on the pull request:
>
> https://github.com/apache/stratos/pull/50#issuecomment-56625991
>
> I solved merge conflicts and integrated this PR. Thanks Gay
$subject. It is down today ?
--
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware
email : manu...@wso2.com / man...@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/
[
https://issues.apache.org/jira/browse/STRATOS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills reassigned STRATOS-672:
Assignee: Mariangela Hills
> Define convention wrt tabs/spaces
> -
[
https://issues.apache.org/jira/browse/STRATOS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills closed STRATOS-804.
> [Wiki] Coding Standards & Best Practices Guidelines
> ---
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/57
---
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
[
https://issues.apache.org/jira/browse/STRATOS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145949#comment-14145949
]
ASF GitHub Bot commented on STRATOS-818:
Github user asfgit closed the pull reque
Github user nirmal070125 commented on the pull request:
https://github.com/apache/stratos/pull/57#issuecomment-56628130
Rebased and merged. Thanks Lasindu.
---
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
Github user lasinducharith closed the pull request at:
https://github.com/apache/stratos/pull/55
---
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
[
https://issues.apache.org/jira/browse/STRATOS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145937#comment-14145937
]
ASF GitHub Bot commented on STRATOS-818:
GitHub user lasinducharith opened a pull
[
https://issues.apache.org/jira/browse/STRATOS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145938#comment-14145938
]
ASF GitHub Bot commented on STRATOS-818:
Github user lasinducharith closed the pu
Github user lasinducharith commented on the pull request:
https://github.com/apache/stratos/pull/55#issuecomment-56627306
Sending the PR https://github.com/apache/stratos/pull/57 to
docker-integration branch. Hence closing this PR.
---
If your project is set up for it, you can reply
GitHub user lasinducharith opened a pull request:
https://github.com/apache/stratos/pull/57
Fixing Stratos-818 - Error log getting printed during the server start-up
Removing org.wso2.stratos.identity.saml2.sso.mgt references and removing
org.wso2.stratos references.
JIRA: https
Github user thushara35 commented on the pull request:
https://github.com/apache/stratos/pull/54#issuecomment-56626661
Yes, Tested in Linux(ubuntu) done!
---
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
Github user nirmal070125 commented on the pull request:
https://github.com/apache/stratos/pull/54#issuecomment-56626278
Hi Thushara,
thanks for the PR, did you get a chance to test this in Ubuntu (Linux)?
---
If your project is set up for it, you can reply to this email and
Sure will do, I’ll check if we have any requirements like this
Btw, I haven’t added the new fields to the schema yet,
Regards
Martin
From: isu...@wso2.com [mailto:isu...@wso2.com] On Behalf Of Isuru Haththotuwa
Sent: Tuesday, September 23, 2014 10:09 PM
To: dev
Subject: Re: [Discuss] [Grouping]
Logged a jira https://issues.apache.org/jira/browse/STRATOS-820
On Wed, Sep 24, 2014 at 10:28 AM, Nirmal Fernando
wrote:
> Hi Gayan,
>
> With this PR, I am seen following error at Stratos back-end. I am running
> locally built stratos with an activemq. What am I missing?
>
> [2014-09-24 10:23:56
[
https://issues.apache.org/jira/browse/STRATOS-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145912#comment-14145912
]
ASF GitHub Bot commented on STRATOS-820:
Github user nirmal070125 commented on th
Github user nirmal070125 commented on the pull request:
https://github.com/apache/stratos/pull/50#issuecomment-56625991
I solved merge conflicts and integrated this PR. Thanks Gayan.
However, later found that this PR has introduced a regression
https://issues.apache.org/jira/b
Nirmal Fernando created STRATOS-820:
---
Summary: Error when publishing tenant subscribed event
Key: STRATOS-820
URL: https://issues.apache.org/jira/browse/STRATOS-820
Project: Stratos
Issue T
That is totally fine. Please do share if you have any ideas for improving
it so that we can work on them. The main requirement is to expose some
information from one Group/leaf level subscription so that any depending
instances can use them to form the connections within the application.
On Wed, S
Hi Gayan,
With this PR, I am seen following error at Stratos back-end. I am running
locally built stratos with an activemq. What am I missing?
[2014-09-24 10:23:56,924] INFO
{org.apache.stratos.manager.publisher.InstanceNotificationPublisher} -
Publishing Instance Cleanup Event: [cluster] test2.
Mmmh, I already added it …
From: isu...@wso2.com [mailto:isu...@wso2.com] On Behalf Of Isuru Haththotuwa
Sent: Tuesday, September 23, 2014 7:58 PM
To: dev
Subject: Re: [Discuss] [Grouping] Specifying Dependency Information in Group
Definition
Hi Martin,
On Wed, Sep 24, 2014 at 4:44 AM, Martin E
Hi Martin,
On Wed, Sep 24, 2014 at 4:44 AM, Martin Eppel (meppel)
wrote:
> Hi Isuru,
>
>
>
> What kind of properties are you referring to where this would be the case
> ? Is there an actual use case for this ? Which code in stratos would
> actually take these properties into account and apply t
Hi Martin,
I think this is due to some recent changes. Could you please build the
org.apache.stratos.metadata.client component, and add it to the
/repository/component/dropins as a temporaray workaround for
this?
On Wed, Sep 24, 2014 at 1:58 AM, Martin Eppel (meppel)
wrote:
>
>
>
>
> I updated
Hi Isuru,
What kind of properties are you referring to where this would be the case ? Is
there an actual use case for this ? Which code in stratos would actually take
these properties into account and apply them ?
Thanks
Martin
From: isu...@wso2.com [mailto:isu...@wso2.com] On Behalf Of Isuru
Hi Isuru,
I was going over the application structure once more and wanted to confirm my
complete understanding of some of the application specific objects and fields
(based on the reference json structure below):
·"components":
o is split in sections to assign the deployment, autos
Martin Eppel created STRATOS-819:
Summary: java.lang.NoClassDefFoundError:
org/apache/stratos/metadata/client/config/MetaDataClientConfig
Key: STRATOS-819
URL: https://issues.apache.org/jira/browse/STRATOS-819
I updated the 4.0.0-grouping branch today morning (09/23 PST) and run into the
exception below when I try to deploy an application:
I opened a JIRA for this issue
https://issues.apache.org/jira/browse/STRATOS-819
TID: [0] [STRATOS] [2014-09-23 20:17:33,080] DEBUG
{org.apache.stratos.cloud.co
On Tue, Sep 23, 2014 at 11:54 PM, Akila Ravihansa Perera wrote:
> Hi Manula,
>
>
>> CEP will receive the health stats once the agent will published them.
>> Suppose the instance didn't activate due to some configuration problem. So
>> how to handle this kind of scenario. Are we use the same time
Hi Manula,
> CEP will receive the health stats once the agent will published them.
> Suppose the instance didn't activate due to some configuration problem. So
> how to handle this kind of scenario. Are we use the same time threshold
> mechanism to handle that ?
>
That's a good point!
I think w
[
https://issues.apache.org/jira/browse/STRATOS-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Perera reassigned STRATOS-812:
Assignee: Isuru Perera
> Longetivity test issue: VMs spawned and Stratos threw OutOfMemory
Hi,
If we need to retrieve a Member object from the topology for a given
member id, we need to perform a 3 level iteration to look it up. This
is a limitation of current topology data structure. Following is a
sample code I had to use for this.
for (Service service : topology.getServices())
Hi,
*Review notes*
- use the word kubernetes instead of docker when naming classes
- arguments should be less than or equal to 4 (we need to add it to
coding practices!?)
- add licence header
- map variables names should have a clue about the map (say,
clusterIdToClusterMonitorM
GitHub user swgkg opened a pull request:
https://github.com/apache/stratos/pull/56
Modify configuration name conventions
Please review and merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gayangunarathne/stratos 4.0.0-groupi
[
https://issues.apache.org/jira/browse/STRATOS-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145076#comment-14145076
]
Manula Chathurika Thantriwatte commented on STRATOS-300:
Hi Akila
[
https://issues.apache.org/jira/browse/STRATOS-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145075#comment-14145075
]
Manula Chathurika Thantriwatte commented on STRATOS-300:
Hi Akila
Hi Akila,
Once the instance is activated agent doesn't need to check the
ports_not_open message logic again and again. Before sending the member
activated event agent will check whether the relevant ports are activated
or not. That's why we have comment out in cartridge agent.
Thanks !
On Tue,
Hi Rekha,
·conceptually we are suggesting to have 3 different types of
autoscaling policies,
o scaling by statistics,
o scaling by group member and
o scaling by group.
Based on this, the general algorithm would be like this (in order):
1. Scale VMs until the cluster maxi
[
https://issues.apache.org/jira/browse/STRATOS-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145054#comment-14145054
]
Akila commented on STRATOS-300:
---
Currently ports_not_open messages logic is commented out
Hi Gayan,
+1 for re-format code with new coding standards. I think you can use
IntelliJ IDEA reformat code option format the code.
On Tue, Sep 23, 2014 at 12:43 PM, Gayan Gunarathne wrote:
> Hi Chamila,
>
> Thanks for sharing this.But this is not resolve the current code
> formatting issue as t
Hi Manula,
Currently there's no plan to test auto scaling. The method, as we've
planned, is to test the publishing side of the health topic. Autoscaling as
an end to end test case will not be included in our scope.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.cham
[
https://issues.apache.org/jira/browse/STRATOS-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akila resolved STRATOS-689.
---
Resolution: Fixed
> CEP binds to private interface so agents can't talk with public IP
>
[
https://issues.apache.org/jira/browse/STRATOS-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144948#comment-14144948
]
Akila commented on STRATOS-689:
---
You can have the CEP bind to any interface by putting 0.0.
Hi Chamila,
+1 for test cases. Are you going to test auto-scaling as well ? What I mean
here is publishing summarize health stats from python cartridge agent and
according to those health stats we have to check whether the auto-scaling
is functioning as expected.
Thanks !
On Tue, Sep 23, 2014 at
Hi,
For $subject, we decided to implement the following steps.
Following aspects need to be tested from agent's point of view.
1) Listening to and publishing instance related events
2) Managing artifacts
3) Managing tenants based on tenant related events
4) Managing log publishing
We chose the
[
https://issues.apache.org/jira/browse/STRATOS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lasindu Charith resolved STRATOS-818.
-
Resolution: Fixed
Fixed in PR : https://github.com/apache/stratos/pull/55/
> Error log g
[
https://issues.apache.org/jira/browse/STRATOS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144785#comment-14144785
]
ASF GitHub Bot commented on STRATOS-818:
GitHub user lasinducharith opened a pull
Since hangout email didn't reach dev@.
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Hi,
Please join the hangout here
https://plus.google.com/hangouts/_/hoaevent/AP36tYfCemYdNWEw38lnSZqhRCIA8rqA-FTHXaP0zw9juKeBvPIxiQ?authuser=0&hl=en
Thanks.
On Tue, Sep 23, 2014 at 11:15 AM, Rajkumar Rajaratnam
wrote:
> Hi Imesh,
>
> You can find more information on the mail thread "Stratos Cl
GitHub user lasinducharith opened a pull request:
https://github.com/apache/stratos/pull/55
Fixing Stratos-818 - Error log getting printed during the server start-up
Removing org.wso2.stratos.identity.saml2.sso.mgt references and removing
any org.wso2.apache calls. Fixing
https://i
Hi,
Please find the hangout at
https://plus.google.com/hangouts/_/hoaevent/AP36tYfCemYdNWEw38lnSZqhRCIA8rqA-FTHXaP0zw9juKeBvPIxiQ?authuser=0&hl=en
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Tue, Sep 23, 2014 at 11:15 AM, Rajkumar Rajarat
Hi,
Please join the hangout on [1]
[1]
https://plus.google.com/hangouts/_/hoaevent/AP36tYfCemYdNWEw38lnSZqhRCIA8rqA-FTHXaP0zw9juKeBvPIxiQ?authuser=0&hl=en
On Tue, Sep 23, 2014 at 11:15 AM, Rajkumar Rajaratnam
wrote:
> Hi Imesh,
>
> You can find more information on the mail thread "Stratos Clus
Please join the hangout
https://plus.google.com/hangouts/_/hoaevent/AP36tYfCemYdNWEw38lnSZqhRCIA8rqA-FTHXaP0zw9juKeBvPIxiQ?pqs=1&authuser=0&hl=en
On Tue, Sep 23, 2014 at 11:15 AM, Rajkumar Rajaratnam
wrote:
> Hi Imesh,
>
> You can find more information on the mail thread "Stratos Cluster
> Monit
[
https://issues.apache.org/jira/browse/STRATOS-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144748#comment-14144748
]
ASF GitHub Bot commented on STRATOS-816:
Github user thushara35 closed the pull r
[
https://issues.apache.org/jira/browse/STRATOS-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144728#comment-14144728
]
Thushara Kasun Ranawaka edited comment on STRATOS-816 at 9/23/14 12:55 PM:
[
https://issues.apache.org/jira/browse/STRATOS-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144747#comment-14144747
]
ASF GitHub Bot commented on STRATOS-816:
GitHub user thushara35 opened a pull req
Github user thushara35 closed the pull request at:
https://github.com/apache/stratos/pull/53
---
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
Github user thushara35 commented on the pull request:
https://github.com/apache/stratos/pull/53#issuecomment-56514854
Sending a new PR https://github.com/apache/stratos/pull/54, hence closing
this
---
If your project is set up for it, you can reply to this email and have your
reply a
GitHub user thushara35 opened a pull request:
https://github.com/apache/stratos/pull/54
Adding changes related to sed -i for mac osx
This change is mainly due to incompatibility issues occurred in stratos
when user run it on a mac os x.
A work around solution is to use gsed inst
Nirmal Fernando created STRATOS-818:
---
Summary: Error log getting printed during the server start-up
Key: STRATOS-818
URL: https://issues.apache.org/jira/browse/STRATOS-818
Project: Stratos
[
https://issues.apache.org/jira/browse/STRATOS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nirmal Fernando updated STRATOS-818:
Assignee: Lasindu Charith (was: Nirmal Fernando)
> Error log getting printed during the se
Hi All,
Please find the above meta data service review on
https://www.youtube.com/watch?v=zb12aYLzjBM
Following are the major discussion points in the above review.
1. REST URL modifications - It is better to have shorter URL
2. Contents which are posted with the meta data service.
3. Configurat
Gayan Gunarathne created STRATOS-817:
Summary: Stratos meta data service config naming conventions
Key: STRATOS-817
URL: https://issues.apache.org/jira/browse/STRATOS-817
Project: Stratos
Thushara Kasun Ranawaka created STRATOS-816:
---
Summary: sed -i command does not work in mac osx
Key: STRATOS-816
URL: https://issues.apache.org/jira/browse/STRATOS-816
Project: Stratos
[
https://issues.apache.org/jira/browse/STRATOS-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144728#comment-14144728
]
Thushara Kasun Ranawaka commented on STRATOS-816:
-
Sent a PR : https://gi
GitHub user shirolk opened a pull request:
https://github.com/apache/stratos/pull/52
Adding in isPublic property to beans for tenant isolation requirements -
for STRATOS-761
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shiro
[
https://issues.apache.org/jira/browse/STRATOS-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144726#comment-14144726
]
ASF GitHub Bot commented on STRATOS-816:
GitHub user thushara35 opened a pull req
GitHub user thushara35 opened a pull request:
https://github.com/apache/stratos/pull/53
Adding changes related to sed -i for mac osx
This change is mainly due to incompatibility issues occurred in stratos
when user run it on a mac os x.
A work around solution is to use gsed inst
[
https://issues.apache.org/jira/browse/STRATOS-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144721#comment-14144721
]
ASF GitHub Bot commented on STRATOS-761:
GitHub user shirolk opened a pull reques
Github user shirolk closed the pull request at:
https://github.com/apache/stratos/pull/44
---
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 ena
[
https://issues.apache.org/jira/browse/STRATOS-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144722#comment-14144722
]
ASF GitHub Bot commented on STRATOS-761:
Github user shirolk closed the pull requ
Github user chamilad closed the pull request at:
https://github.com/apache/stratos/pull/49
---
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 en
Github user R-Rajkumar closed the pull request at:
https://github.com/apache/stratos/pull/28
---
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
Github user R-Rajkumar closed the pull request at:
https://github.com/apache/stratos/pull/51
---
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
Github user R-Rajkumar commented on the pull request:
https://github.com/apache/stratos/pull/28#issuecomment-56495427
committed in 5e41897eb730b941f2d2521f15dd6378eada
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user R-Rajkumar commented on the pull request:
https://github.com/apache/stratos/pull/51#issuecomment-56495388
commited in a93781038c38e86dc7f263cec69373d4541b73d1 and
d6f49d37095d0c6d20cf799f6e9a0e47932608ca
---
If your project is set up for it, you can reply to this email an
GitHub user swgkg opened a pull request:
https://github.com/apache/stratos/pull/50
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
GitHub user R-Rajkumar opened a pull request:
https://github.com/apache/stratos/pull/51
STRATOS-807 - cluster monitors re-arranged
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/R-Rajkumar/stratos
docker-integration-new-cluster
Github user R-Rajkumar closed the pull request at:
https://github.com/apache/stratos/pull/46
---
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
Manula Chathurika Thantriwatte created STRATOS-815:
--
Summary: Support HAProxy extension to default and service aware
load balancer
Key: STRATOS-815
URL: https://issues.apache.org/jira/browse/STRA
[
https://issues.apache.org/jira/browse/STRATOS-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144610#comment-14144610
]
ASF GitHub Bot commented on STRATOS-779:
Github user R-Rajkumar closed the pull r
[
https://issues.apache.org/jira/browse/STRATOS-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144609#comment-14144609
]
ASF GitHub Bot commented on STRATOS-779:
Github user R-Rajkumar commented on the
[
https://issues.apache.org/jira/browse/STRATOS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144607#comment-14144607
]
ASF GitHub Bot commented on STRATOS-807:
Github user R-Rajkumar commented on the
[
https://issues.apache.org/jira/browse/STRATOS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144608#comment-14144608
]
ASF GitHub Bot commented on STRATOS-807:
Github user R-Rajkumar closed the pull r
[
https://issues.apache.org/jira/browse/STRATOS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144605#comment-14144605
]
ASF GitHub Bot commented on STRATOS-807:
Github user R-Rajkumar closed the pull r
[
https://issues.apache.org/jira/browse/STRATOS-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144595#comment-14144595
]
chris snow commented on STRATOS-797:
It is still [failing|https://travis-ci.org/snowc
[
https://issues.apache.org/jira/browse/STRATOS-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chris snow updated STRATOS-797:
---
Comment: was deleted
(was: I just kicked off a fresh build and it failed:
https://travis-ci.org/snow
[
https://issues.apache.org/jira/browse/STRATOS-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144581#comment-14144581
]
chris snow commented on STRATOS-797:
I just kicked off a fresh build and it failed:
[
https://issues.apache.org/jira/browse/STRATOS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144578#comment-14144578
]
ASF GitHub Bot commented on STRATOS-807:
GitHub user R-Rajkumar opened a pull req
1 - 100 of 109 matches
Mail list logo
