Hi Mari,

I will start removing this in code.

Thanks.

On Tue, Mar 17, 2015 at 10:37 AM, Mariangela Hills <[email protected]>
wrote:

> Hi Lahiru,
>
> Will you be able to remove the lbClusterId property or shall we create a
> JIRA to track this task, so that no one forgets it in the future?
>
> Regards,
> Mariangela
>
>
>
>
> *--*
> Mariangela Hills
> Senior Technical Writer
>
> *WSO2, Inc.*lean.enterprise.middleware.
> m: +94 773 500185
> w: http://wso2.com
> <http://wso2.com/events/>
>
> On Tue, Mar 17, 2015 at 9:49 AM, Imesh Gunaratne <[email protected]> wrote:
>
>> Hi Lahiru,
>>
>> Yes we need to remove lbClusterId property from the member definition.
>>
>> Now each load balancer instance will get a list of dependent cluster ids
>> via the payload which the load balancer should serve specifically.
>> Therefore lbClusterId property is not used anymore.
>>
>> Thanks
>>
>> On Mon, Mar 16, 2015 at 3:33 PM, Lahiru Sandaruwan <[email protected]>
>> wrote:
>>
>>> Hi devs,
>>>
>>> I have seen there are few places that we still have "lbClusterId" in
>>> Member and MemberContext classes.
>>>
>>> Since we have removed the LB type from the list of cartridge types, we
>>> would not recognize LB Id from Stratos POV.
>>>
>>> Do we use that for load balancing functionality?
>>>
>>> Thanks.
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Committer and PMC member, Apache Stratos,
>>> Senior Software Engineer,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> phone: +94773325954
>>> email: [email protected] blog: http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>


-- 
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

phone: +94773325954
email: [email protected] blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146

Reply via email to