Hi Isuru/Imesh,
This particular processor chain implemented in order to calculate the
status of the application/group/cluster. When an status change occurred in
member, cluster processor chain will get executed to calculate the current
status of the cluster in which that member is being part of. W
Great! Thanks Akila!
On Thursday, November 19, 2015, Akila Ravihansa Perera
wrote:
> Hi Imesh,
>
> Yes, I tested scaling, min check, fault detection features in ec2,
> openstack, gce and Kubernetes iaas's. We have integration tests for
> metadata service and group scaling features. According to
Hi Imesh,
Yes, I tested scaling, min check, fault detection features in ec2,
openstack, gce and Kubernetes iaas's. We have integration tests for
metadata service and group scaling features. According to Jenkins all tests
passed successfully.
Thanks.
On Thursday, 19 November 2015, Imesh Gunaratn
Great work Chamila!!
May be you could try to contribute this back to the Paho-MQTT python
library.
Thanks
On Mon, Nov 16, 2015 at 11:38 PM, Chamila De Alwis
wrote:
> Hi Devs,
>
> I've implemented the $subject, since Paho-MQTT Python library doesn't seem
> to support a broker URL list out of the
I'm +1 for displaying a grey colour icon when DAS/monitoring is not
configured. Because it would give an indication for a first time user that
monitoring features are there but they are not configured.
Thanks
On Tue, Nov 17, 2015 at 9:07 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrot
Great work Akila!
We might need to verify all the features after doing this modification.
Were you able to run any tests after doing this?
Thanks
On Tue, Nov 17, 2015 at 10:02 PM, Akila Ravihansa Perera wrote:
> Hi,
>
> Currently Stratos components do not properly import/export packages
> to/fr
I'm sorry Isuru I'm not so sure how this logic works, @Reka: Do you have
any thoughts?
Thanks
On Wed, Nov 18, 2015 at 6:52 PM, Isuru Haththotuwa
wrote:
> Hi,
>
> In ClusterMonitor [1] and AutoscalerTopologyEventReceiver [2] classes,
> there are two occasions where we are sending a message throu
Also in the cluster monitor we are getting status change from[1]. AFAIU
that process logic is not execute ever and stateChanged will be always
false.Is n't?
// Checking the current status of the cluster instance
boolean stateChanged =
ServiceReferenceHolder.getInstance().getCluste
On Wed, Nov 18, 2015 at 5:11 PM, Isuru Haththotuwa
wrote:
>
>
> On Wed, Nov 18, 2015 at 9:50 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Thanks Isuru. Will test this again. Doea that mean we are changing the
>> network partition artifact structure in 4.1.5 release?
>
> No, ther
Hi All,
If we summarize issues mention in this thread,
Issue 1 - This is happen if Stratos is restarting before application get
activated.(If application is in the initiate state). If anyone experience
this issue after the application activation?
Issue 2 - Regarding the Axis2 exception, seems it
In the rest API, there is profile called api-test. Seems it is not up to
date with the latest rest API. What is the usage about this profile?
[1]
https://github.com/apache/stratos/tree/stratos-4.1.x/components/org.apache.stratos.rest.endpoint/src/main/webapp/api-test
Thanks,
Gayan
--
Gayan Gu
Hi,
In ClusterMonitor [1] and AutoscalerTopologyEventReceiver [2] classes,
there are two occasions where we are sending a message through the
ClusterStatusProcessorChain with type set to an empty String [3, 4]. AFAIK
the processor chain will determine which processor to use based on this
type, and
On Wed, Nov 18, 2015 at 9:50 AM, Akila Ravihansa Perera
wrote:
> Thanks Isuru. Will test this again. Doea that mean we are changing the
> network partition artifact structure in 4.1.5 release?
No, there is no change to NW partition definitions. It will first check if
zone (partition property) is
[
https://issues.apache.org/jira/browse/STRATOS-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa resolved STRATOS-1620.
Resolution: Fixed
> Stratos is not Picking up Updated IaasProvider properties in C
[
https://issues.apache.org/jira/browse/STRATOS-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa resolved STRATOS-1613.
Resolution: Fixed
> The Image Id defined in the Cartridge Defintion Does not get p
[
https://issues.apache.org/jira/browse/STRATOS-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010709#comment-15010709
]
Isuru Haththotuwa commented on STRATOS-1620:
Fixed in Fixed in caa3ab27229cd
[
https://issues.apache.org/jira/browse/STRATOS-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa updated STRATOS-1613:
---
Fix Version/s: (was: FUTURE)
4.1.5
> The Image Id defined in
[
https://issues.apache.org/jira/browse/STRATOS-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010708#comment-15010708
]
Isuru Haththotuwa commented on STRATOS-1613:
Fixed in caa3ab27229cd042730ed2
Hi Zhang,
Welcome to the Stratos community!
There are several tasks (based on Drools rules engine) that run in the
background to take scaling decisions. You can find those Drools files at
[1].
mincheck.drl - is responsible for spawning minimum number of instances
defined in the cartridge definit
Hi Akila,
Yes, I am aware of component synchronization. But the logs suggests that
there is a communication issue between AS & CC while AS tries to validate
deployment policy as part of cluster monitor creation. It doesn't
necessarily mean that CC was not started before AS (as per the logs, we can
Hi Raj,
There is a component startup order which will make sure CC, AS and SM are
ready before accepting any request from Stratos API.
On Wed, Nov 18, 2015 at 12:52 PM, Rajkumar Rajaratnam
>> wrote:
>>
>>> Hi Pubudu,
>>>
>>> In your case, the monitors are not started/scheduled after server
>>> r
[
https://issues.apache.org/jira/browse/STRATOS-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thanuja Uruththirakodeeswaran resolved STRATOS-1624.
Resolution: Fixed
> Updating metering and monitoring dashb
[
https://issues.apache.org/jira/browse/STRATOS-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010480#comment-15010480
]
Thanuja Uruththirakodeeswaran commented on STRATOS-1624:
Fixed i
[
https://issues.apache.org/jira/browse/STRATOS-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gayan Gunarathne updated STRATOS-1624:
--
Assignee: Thanuja Uruththirakodeeswaran
> Updating metering and monitoring dashboard a
Thanuja Uruththirakodeeswaran created STRATOS-1624:
--
Summary: Updating metering and monitoring dashboard artifacts to
support carbon-dashboard version 1.0.7
Key: STRATOS-1624
URL: https://issues.a
25 matches
Mail list logo
