GitHub user swgkg opened a pull request:
https://github.com/apache/stratos/pull/145
Update the categary of cartridge as a mandatory value
This pr will Update the categary of cartridge as a mandatory value
Please review and merge
You can merge this pull request into a Git re
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/143
---
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-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240670#comment-14240670
]
ASF GitHub Bot commented on STRATOS-857:
Github user asfgit closed the pull reque
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/144
---
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
Shiroshica Kulatilake created STRATOS-1028:
--
Summary: Refactor REST API responsees
Key: STRATOS-1028
URL: https://issues.apache.org/jira/browse/STRATOS-1028
Project: Stratos
Issue T
Hi Martin,
>From 4.1.0 onwards, we recommend to use python agent as discussed in
stratos-dev [1]. We have added the puppet modules for it as well. If you
pull our latest puppet module, it has puppet agent stuffs and it is already
configured to use python agent. So, by just updating the mb and cep
[
https://issues.apache.org/jira/browse/STRATOS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240648#comment-14240648
]
ASF GitHub Bot commented on STRATOS-857:
GitHub user shirolk opened a pull reques
GitHub user shirolk opened a pull request:
https://github.com/apache/stratos/pull/144
Refactoring the REST API
For STRATOS-857
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shirolk/stratos api_test
Alternatively you can review
Github user shirolk closed the pull request at:
https://github.com/apache/stratos/pull/138
---
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
Hi Martin,
Yah. It is like that..We refer the child policy of group/cluster using the
alias of corresponding group/cluster in application.
Thanks,
Reka
On Tue, Dec 9, 2014 at 11:27 PM, Martin Eppel (meppel)
wrote:
> Ok,
>
>
>
> Quick question on the deployment policy:
>
> Does a deployment po
Hi Martin,
Can you pull master and start the initial testing? We were working on
4.1.0-test throughout the day today for several other testing. So i'm not
sure how far it is stable now. We thought of merging 4.1.0-test to master
by tomorrow after make sure that the flow is working fine.
You can
Reka,
Should I pull the master or temporary branch (4.1.0-test) ?
Thanks
Martin
From: Reka Thirunavukkarasu [mailto:r...@wso2.com]
Sent: Monday, December 08, 2014 11:19 PM
To: dev
Subject: Re: [Testing] Stratos 4.1.0 Alpha
Hi Martin,
I saw a log saying the unable to retrieve registry data. Ca
Hi Imesh,
I guess, it is better have it as an INFO level log.
Thanks.
On Tue, Dec 9, 2014 at 6:20 PM, Rajkumar Rajaratnam
wrote:
> It should be INFO/DEBUG log.
>
> And log message should be changed something like "Member is terminated.
> Hence removing from active member list".
>
> Thanks.
>
>
It should be INFO/DEBUG log.
And log message should be changed something like "Member is terminated.
Hence removing from active member list".
Thanks.
On Tue, Dec 9, 2014 at 6:14 PM, Imesh Gunaratne wrote:
> Hi,
>
> Why do we have the following warning message? Isn't it possible for us to
> avo
Hi,
Why do we have the following warning message? Isn't it possible for us to
avoid this scenario being happening?
public class VMClusterMonitor {
public void handleMemberTerminatedEvent(
MemberTerminatedEvent memberTerminatedEvent) {
...
} else if
(clusterMonitorPartitio
GitHub user swgkg opened a pull request:
https://github.com/apache/stratos/pull/143
Update cleanup clustor with the instance id
Added the instance id condition for the clean up cluster
Please review and merge
You can merge this pull request into a Git repository by running:
Github user swgkg commented on the pull request:
https://github.com/apache/stratos/pull/140#issuecomment-66277245
This is already merge , hence closing the pull request
commit ID :adf60a8608d27879ce9630cc8531bfc953f21bc9
---
If your project is set up for it, you can reply to
Github user swgkg closed the pull request at:
https://github.com/apache/stratos/pull/140
---
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
GitHub user Vishanth opened a pull request:
https://github.com/apache/stratos/pull/142
Rename security-sql.mysql to security-mysql.sql
incorrect file name
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Vishanth/stratos patch-2
A
GitHub user Vishanth opened a pull request:
https://github.com/apache/stratos/pull/141
Rename application-sql.mysql to application-mysql.sql
incorrect file name
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Vishanth/stratos patc
Yes i did and it worked. Just pointed out to correct them.
Thank you
On Tue, Dec 9, 2014 at 4:41 PM, Udara Liyanage wrote:
> Hi Vishanth,
>
> Please rename them so they match.
>
> On Tue, Dec 9, 2014 at 4:39 PM, Gayan Gunarathne wrote:
>
>> Seems we need to rename file name as security-mysql.s
Hi Vishanth,
Please rename them so they match.
On Tue, Dec 9, 2014 at 4:39 PM, Gayan Gunarathne wrote:
> Seems we need to rename file name as security-mysql.sql and
> application-mysql.sql.
>
> Thanks,
> Gayan
>
> On Tue, Dec 9, 2014 at 3:54 PM, Vishanth Balasubramaniam <
> vishan...@wso2.com>
Seems we need to rename file name as security-mysql.sql and
application-mysql.sql.
Thanks,
Gayan
On Tue, Dec 9, 2014 at 3:54 PM, Vishanth Balasubramaniam wrote:
> Hi Devs,
>
> In the latest stratos-installer setup.sh file, the 2 files to be amended
> are security-mysql.sql and application-mysql
Hi Devs,
In the latest stratos-installer setup.sh file, the 2 files to be amended
are security-mysql.sql and application-mysql.sql in the following lines of
code.
# Database Configuration
# ---
echo "Create and configure MySql Databases" >> $
Thanks Lahiru!
On Tue, Dec 9, 2014 at 2:35 PM, Lahiru Sandaruwan wrote:
> I will fix it to use this method when scaling down. Earlier we used SM
> service call.
>
> Thanks.
>
> On Tue, Dec 9, 2014 at 2:12 PM, Imesh Gunaratne wrote:
>
>> I fixed the above issue and pushed it to 4.1.0-test branch
I will fix it to use this method when scaling down. Earlier we used SM
service call.
Thanks.
On Tue, Dec 9, 2014 at 2:12 PM, Imesh Gunaratne wrote:
> I fixed the above issue and pushed it to 4.1.0-test branch.
>
> Now I see another problem: Instance clean up event is not published to
> member.
I fixed the above issue and pushed it to 4.1.0-test branch.
Now I see another problem: Instance clean up event is not published to
member. Seems
like InstanceNotificationPublisher.sendInstanceCleanupEventForMember()
method in Autoscaler is not used.
Thanks
On Tue, Dec 9, 2014 at 1:34 PM, Imesh
Found the problem, InstanceSpawnedMessageProcessor has not added instance
id to the member object.
On Tue, Dec 9, 2014 at 1:07 PM, Imesh Gunaratne wrote:
> Now I can see another problem in autoscaler in member fault handling
> scenario:
>
> [2014-12-09 13:04:03,795] ERROR
> {org.apache.stratos.m
28 matches
Mail list logo
