> This is not the right model IMO. We should follow a consistent pattern
> throughout. I'm going to fix this.
>

+1 for fixing to follow up a right model.

>
> +1.  Let's fix this for M4. We can add a rule in autoscaler which runs
> when a “cluster removed” event is received. It will find all the member IDs
> and call CC for terminating.
>
> Thanks.
>
>>
>>
>>
>>
>> On Wed, Nov 20, 2013 at 3:39 AM, reka thirunavukkarasu (JIRA) <
>> [email protected]> wrote:
>>
>>>
>>>      [
>>> https://issues.apache.org/jira/browse/STRATOS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>>
>>> reka thirunavukkarasu resolved STRATOS-204.
>>> -------------------------------------------
>>>
>>>     Resolution: Fixed
>>>
>>> > Unsubscription didn't terminate the instance
>>> > --------------------------------------------
>>> >
>>> >                 Key: STRATOS-204
>>> >                 URL: https://issues.apache.org/jira/browse/STRATOS-204
>>> >             Project: Stratos
>>> >          Issue Type: Bug
>>> >    Affects Versions: 4.0.0 M2
>>> >            Reporter: Nirmal Fernando
>>> >            Assignee: reka thirunavukkarasu
>>> >            Priority: Blocker
>>> >             Fix For: 4.0.0 M3
>>> >
>>> >
>>>
>>>
>>>
>>>
>>> --
>>> This message was sent by Atlassian JIRA
>>> (v6.1#6144)
>>>
>>
>>
>>
>> --
>> 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: [email protected] 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
>
>


-- 
Reka Thirunavukkarasu
Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007

Reply via email to