[
https://issues.apache.org/jira/browse/STRATOS-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057192#comment-14057192
]
Manula Chathurika Thantriwatte commented on STRATOS-697:
Stratos
[
https://issues.apache.org/jira/browse/STRATOS-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manula Chathurika Thantriwatte resolved STRATOS-697.
Resolution: Fixed
Fix Version/s: 4.0.1
> Improvemen
Hi Isuru, did my previous email make sense?
On Wed, Jul 9, 2014 at 8:51 AM, chris snow wrote:
> Hi Isuru,
>
> Separating the repository will just move the problem (of having to
> manually update these files) rather than fix it? I think we could fix
> this problem as we are implement STRATOS-680.
[
https://issues.apache.org/jira/browse/STRATOS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057134#comment-14057134
]
Dinesh Bandara commented on STRATOS-703:
4.0.0 : f2e2c9621e1fb9913b4d256b7d8167a4
Hi Manula,
Looks like you're currently working on this JIRA. Wanted to check with you if
you're going to fix the issue of topology events supporting only one private IP
and one public IP. I think this issue is related to the floating IP issue
described in this JIRA. Are you going to addre
Hi,
We want to upstream support for cartridge agent health statistics plugins.
The attached patch (for 4.0.0) doesn’t change the cartridge agents’
functionality. What it does do, is allow a single plugin jar, to ‘override’ the
original health statistics functionality, if it is passed in as part
Hi Udara,
On Wed, Jul 9, 2014 at 5:43 PM, Udara Liyanage wrote:
> Hi Reka,
>
> Currently in AS we have a cluster moniter which act on ClusterCreated
> events when a subscription happens. Are we going to use the same
> ClusterMoniter for compositeApp deployment or adding another moniter like
> Ap
Hi Reka,
Currently in AS we have a cluster moniter which act on ClusterCreated
events when a subscription happens. Are we going to use the same
ClusterMoniter for compositeApp deployment or adding another moniter like
ApplicationMoniter.
On Wed, Jul 9, 2014 at 4:33 PM, Reka Thirunavukkarasu wro
Hi all,
These are the break down that we may need to consider when deploying
Composite Application and when starting an ApplicationMonitor. I have
integrated the earlier subscription model with Composite Application.
Please see below and provide you thoughts on this. So that we can finalize
the th
Thanks Martin..
On Wed, Jul 9, 2014 at 1:34 PM, Martin Eppel (meppel)
wrote:
> Hi Reka,
>
>
>
> Actually I just copied the example from one of the previous emails (Imesh
> and Isuru’s emails) as examples.
>
>
>
> But I think you are right, the composite application defines these
> parameters (
Hi Isuru,
Separating the repository will just move the problem (of having to
manually update these files) rather than fix it? I think we could fix
this problem as we are implement STRATOS-680.
The purpose of STRATOS-680 is to create zip archives of files in the
tool directory. If we had a @VERS
Dinesh Bandara created STRATOS-703:
--
Summary: HAProxy Extension with multiple clusters, it will route
to the same server
Key: STRATOS-703
URL: https://issues.apache.org/jira/browse/STRATOS-703
Projec
Hi Martin,
Thanks for the summary...I have a small doubt with Composite Application
Model. It is mentioned as below..
On Tue, Jul 8, 2014 at 8:07 PM, Martin Eppel (meppel)
wrote:
> I browsed over the previously exchanged emails, compiled and summarized
> it below (please correct me when my un
[
https://issues.apache.org/jira/browse/STRATOS-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Bandara resolved STRATOS-702.
Resolution: Fixed
> HAProxy Extension won't update it's member list
>
14 matches
Mail list logo
