You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Lahiru Sandaruwan <la...@wso2.com> on 2014/01/04 16:27:39 UTC

Re: [Autoscaler] HealthEventMessageDelegator doesn't follow the correct message processor pattern

Final bit of the fix is added with
commit 253bbb08a9fab307570a2832cc965757384e0422.

Now all the message receivers in Autoscaler follow chain of responsibility
pattern. Also I have added all the required bits in messaging components
such that if any other party wants Health stat messages.

Example message that would required from CEP side would be,

{"org.apache.stratos.messaging.event.health.stat.MemberAverageLoadAverageEvent":{"message":{"memberId":"member_id","value":3.3}}}}

Manula will do necessary changes in CEP side to send events this way.


On Fri, Dec 20, 2013 at 2:02 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:

> I'm working on adding message events and processors in messaging component
> for health stat events.
>
> Thanks.
>
>
> On Fri, Dec 6, 2013 at 11:35 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>
>> I'm starting with Scale up/ down algorithms etc. So i'll look into this
>> as well..
>>
>> Thanks.
>>
>>
>> On Fri, Dec 6, 2013 at 11:32 AM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>> All,
>>>
>>> Just noticed that $subject. Idea of introducing message processor chain
>>> [1] is to avoid if-else statements and follow a proper OOP design pattern.
>>>
>>> Can anyone volunteer to fix this bit of code?
>>>
>>> [1] dev@ thread: Topology Event Message Processors follow 'chain of
>>> responsibility' design pattern
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>


-- 
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146

Re: [Autoscaler] HealthEventMessageDelegator doesn't follow the correct message processor pattern

Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Done the changes and commit to git.

Thanks !


On Mon, Jan 6, 2014 at 9:22 AM, Lahiru Sandaruwan <la...@wso2.com> wrote:

>
>
>
> On Mon, Jan 6, 2014 at 9:05 AM, Manula Chathurika Thantriwatte <
> manulac@wso2.com> wrote:
>
>> Hi,
>>
>> I'll do the necessary changes in CEP side.
>>
>
> Thanks Manula.
>
>>
>>
>> On Sat, Jan 4, 2014 at 10:42 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>> Great. :)
>>>
>>>
>>> On Saturday, January 4, 2014, Lahiru Sandaruwan wrote:
>>>
>>>> Final bit of the fix is added with
>>>> commit 253bbb08a9fab307570a2832cc965757384e0422.
>>>>
>>>> Now all the message receivers in Autoscaler follow chain of
>>>> responsibility pattern. Also I have added all the required bits in
>>>> messaging components such that if any other party wants Health stat
>>>> messages.
>>>>
>>>> Example message that would required from CEP side would be,
>>>>
>>>>
>>>> {"org.apache.stratos.messaging.event.health.stat.MemberAverageLoadAverageEvent":{"message":{"memberId":"member_id","value":3.3}}}}
>>>>
>>>> Manula will do necessary changes in CEP side to send events this way.
>>>>
>>>>
>>>> On Fri, Dec 20, 2013 at 2:02 PM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>>
>>>>> I'm working on adding message events and processors in messaging
>>>>> component for health stat events.
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
>>>>> On Fri, Dec 6, 2013 at 11:35 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>>>
>>>>>> I'm starting with Scale up/ down algorithms etc. So i'll look into
>>>>>> this as well..
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>>
>>>>>> On Fri, Dec 6, 2013 at 11:32 AM, Nirmal Fernando <
>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>
>>>>>>> All,
>>>>>>>
>>>>>>> Just noticed that $subject. Idea of introducing message processor
>>>>>>> chain [1] is to avoid if-else statements and follow a proper OOP design
>>>>>>> pattern.
>>>>>>>
>>>>>>> Can anyone volunteer to fix this bit of code?
>>>>>>>
>>>>>>> [1] dev@ thread: Topology Event Message Processors follow 'chain of
>>>>>>> responsibility' design pattern
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Nirmal
>>>>>>>
>>>>>>> Nirmal Fernando.
>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>
>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> Lahiru Sandaruwan
>>>>>> Software Engineer,
>>>>>> Platform Technologies,
>>>>>> WSO2 Inc., http://wso2.com
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>>>> blog: http://lahiruwrites.blogspot.com/
>>>>>> twitter: http://twitter.com/lahirus
>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> Lahiru Sandaruwan
>>>>> Software Engineer,
>>>>> Platform Technologies,
>>>>> WSO2 Inc., http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>>> blog: http://lahiruwrites.blogspot.com/
>>>>> twitter: http://twitter.com/lahirus
>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Software Engineer,
>>>> Platform Technologies,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>> blog: http://lahiruwrites.blogspot.com/
>>>> twitter: http://twitter.com/lahirus
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>
>>
>> --
>> Regards,
>> Manula Chathurika Thantriwatte
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>> lean . enterprise . middleware
>>
>> email : manulac@wso2.com / manula@apache.org
>> phone : +94 772492511
>> blog : http://manulachathurika.blogspot.com/
>>
>>
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>


-- 
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware

email : manulac@wso2.com / manula@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/

Re: [Autoscaler] HealthEventMessageDelegator doesn't follow the correct message processor pattern

Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Mon, Jan 6, 2014 at 9:05 AM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:

> Hi,
>
> I'll do the necessary changes in CEP side.
>

Thanks Manula.

>
>
> On Sat, Jan 4, 2014 at 10:42 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> Great. :)
>>
>>
>> On Saturday, January 4, 2014, Lahiru Sandaruwan wrote:
>>
>>> Final bit of the fix is added with
>>> commit 253bbb08a9fab307570a2832cc965757384e0422.
>>>
>>> Now all the message receivers in Autoscaler follow chain of
>>> responsibility pattern. Also I have added all the required bits in
>>> messaging components such that if any other party wants Health stat
>>> messages.
>>>
>>> Example message that would required from CEP side would be,
>>>
>>>
>>> {"org.apache.stratos.messaging.event.health.stat.MemberAverageLoadAverageEvent":{"message":{"memberId":"member_id","value":3.3}}}}
>>>
>>> Manula will do necessary changes in CEP side to send events this way.
>>>
>>>
>>> On Fri, Dec 20, 2013 at 2:02 PM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>
>>>> I'm working on adding message events and processors in messaging
>>>> component for health stat events.
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> On Fri, Dec 6, 2013 at 11:35 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>>
>>>>> I'm starting with Scale up/ down algorithms etc. So i'll look into
>>>>> this as well..
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
>>>>> On Fri, Dec 6, 2013 at 11:32 AM, Nirmal Fernando <
>>>>> nirmal070125@gmail.com> wrote:
>>>>>
>>>>>> All,
>>>>>>
>>>>>> Just noticed that $subject. Idea of introducing message processor
>>>>>> chain [1] is to avoid if-else statements and follow a proper OOP design
>>>>>> pattern.
>>>>>>
>>>>>> Can anyone volunteer to fix this bit of code?
>>>>>>
>>>>>> [1] dev@ thread: Topology Event Message Processors follow 'chain of
>>>>>> responsibility' design pattern
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Nirmal Fernando.
>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> Lahiru Sandaruwan
>>>>> Software Engineer,
>>>>> Platform Technologies,
>>>>> WSO2 Inc., http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>>> blog: http://lahiruwrites.blogspot.com/
>>>>> twitter: http://twitter.com/lahirus
>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Software Engineer,
>>>> Platform Technologies,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>> blog: http://lahiruwrites.blogspot.com/
>>>> twitter: http://twitter.com/lahirus
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Software Engineer,
>>> Platform Technologies,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>> blog: http://lahiruwrites.blogspot.com/
>>> twitter: http://twitter.com/lahirus
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> email : manulac@wso2.com / manula@apache.org
> phone : +94 772492511
> blog : http://manulachathurika.blogspot.com/
>
>
>
>


-- 
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146

Re: [Autoscaler] HealthEventMessageDelegator doesn't follow the correct message processor pattern

Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi,

I'll do the necessary changes in CEP side.


On Sat, Jan 4, 2014 at 10:42 PM, Nirmal Fernando <ni...@gmail.com>wrote:

> Great. :)
>
>
> On Saturday, January 4, 2014, Lahiru Sandaruwan wrote:
>
>> Final bit of the fix is added with
>> commit 253bbb08a9fab307570a2832cc965757384e0422.
>>
>> Now all the message receivers in Autoscaler follow chain of
>> responsibility pattern. Also I have added all the required bits in
>> messaging components such that if any other party wants Health stat
>> messages.
>>
>> Example message that would required from CEP side would be,
>>
>>
>> {"org.apache.stratos.messaging.event.health.stat.MemberAverageLoadAverageEvent":{"message":{"memberId":"member_id","value":3.3}}}}
>>
>> Manula will do necessary changes in CEP side to send events this way.
>>
>>
>> On Fri, Dec 20, 2013 at 2:02 PM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>
>>> I'm working on adding message events and processors in messaging
>>> component for health stat events.
>>>
>>> Thanks.
>>>
>>>
>>> On Fri, Dec 6, 2013 at 11:35 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>
>>>> I'm starting with Scale up/ down algorithms etc. So i'll look into this
>>>> as well..
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> On Fri, Dec 6, 2013 at 11:32 AM, Nirmal Fernando <
>>>> nirmal070125@gmail.com> wrote:
>>>>
>>>>> All,
>>>>>
>>>>> Just noticed that $subject. Idea of introducing message processor
>>>>> chain [1] is to avoid if-else statements and follow a proper OOP design
>>>>> pattern.
>>>>>
>>>>> Can anyone volunteer to fix this bit of code?
>>>>>
>>>>> [1] dev@ thread: Topology Event Message Processors follow 'chain of
>>>>> responsibility' design pattern
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Software Engineer,
>>>> Platform Technologies,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>> blog: http://lahiruwrites.blogspot.com/
>>>> twitter: http://twitter.com/lahirus
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Software Engineer,
>>> Platform Technologies,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>> blog: http://lahiruwrites.blogspot.com/
>>> twitter: http://twitter.com/lahirus
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
>


-- 
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware

email : manulac@wso2.com / manula@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/

Re: [Autoscaler] HealthEventMessageDelegator doesn't follow the correct message processor pattern

Posted by Nirmal Fernando <ni...@gmail.com>.
Great. :)

On Saturday, January 4, 2014, Lahiru Sandaruwan wrote:

> Final bit of the fix is added with
> commit 253bbb08a9fab307570a2832cc965757384e0422.
>
> Now all the message receivers in Autoscaler follow chain of responsibility
> pattern. Also I have added all the required bits in messaging components
> such that if any other party wants Health stat messages.
>
> Example message that would required from CEP side would be,
>
>
> {"org.apache.stratos.messaging.event.health.stat.MemberAverageLoadAverageEvent":{"message":{"memberId":"member_id","value":3.3}}}}
>
> Manula will do necessary changes in CEP side to send events this way.
>
>
> On Fri, Dec 20, 2013 at 2:02 PM, Lahiru Sandaruwan <lahirus@wso2.com<javascript:_e({}, 'cvml', 'lahirus@wso2.com');>
> > wrote:
>
>> I'm working on adding message events and processors in messaging
>> component for health stat events.
>>
>> Thanks.
>>
>>
>> On Fri, Dec 6, 2013 at 11:35 AM, Lahiru Sandaruwan <lahirus@wso2.com<javascript:_e({}, 'cvml', 'lahirus@wso2.com');>
>> > wrote:
>>
>>> I'm starting with Scale up/ down algorithms etc. So i'll look into this
>>> as well..
>>>
>>> Thanks.
>>>
>>>
>>> On Fri, Dec 6, 2013 at 11:32 AM, Nirmal Fernando <nirmal070125@gmail.com<javascript:_e({}, 'cvml', 'nirmal070125@gmail.com');>
>>> > wrote:
>>>
>>>> All,
>>>>
>>>> Just noticed that $subject. Idea of introducing message processor chain
>>>> [1] is to avoid if-else statements and follow a proper OOP design pattern.
>>>>
>>>> Can anyone volunteer to fix this bit of code?
>>>>
>>>> [1] dev@ thread: Topology Event Message Processors follow 'chain of
>>>> responsibility' design pattern
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Software Engineer,
>>> Platform Technologies,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com <javascript:_e({}, 'cvml', 'lahirus@wso2.com');>cell: (+94)
>>> 773 325 954
>>> blog: http://lahiruwrites.blogspot.com/
>>> twitter: http://twitter.com/lahirus
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com <javascript:_e({}, 'cvml', 'lahirus@wso2.com');>cell: (+94)
>> 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com <javascript:_e({}, 'cvml', 'lahirus@wso2.com');>cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>

-- 
Best Regards,
Nirmal

Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.

Blog: http://nirmalfdo.blogspot.com/