On Tue, Nov 19, 2013 at 9:13 AM, Nirmal Fernando <[email protected]>wrote:

>
>
>
> On Tue, Nov 19, 2013 at 8:49 AM, Lahiru Sandaruwan <[email protected]>wrote:
>
>>
>>
>>
>> On Tue, Nov 19, 2013 at 8:43 AM, Nirmal Fernando 
>> <[email protected]>wrote:
>>
>>> Does CC has enough information to do that?
>>>
>> Yes. We followed that for M1 and M2.
>>
>
> I'm sorry, but what you mean? It doesn't work in M2, hence the jira.
>
I thought it's broken after M2...

>
>  I was expecting that CC would just change the state of the topology and
>>> that would trigger an event which auto-scaler pics up and do the instance
>>> termination.
>>>
>>
>>
>> We had it like that. And we changed it since this saves some overhead
>> request going around and this is not really a scaling decision but a
>> terminating a subscription.
>>
>> So, does CC also keeps the same information model as Autoscaler? IMO that
> is wrong, ideally CC should be state-less with the new architecture.
>

I think having topology is enough? We anyway have the topology. Reka can
add more insights..

Thanks.

>
> CC sends cluster removed event when unsubscription happened and Autoscaler
>> will act according tot hat.
>>
>> Thanks.
>>
>>>
>>>
>>>
>>> On Tue, Nov 19, 2013 at 8:31 AM, Lahiru Sandaruwan (JIRA) <
>>> [email protected]> wrote:
>>>
>>>>
>>>>     [
>>>> https://issues.apache.org/jira/browse/STRATOS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826105#comment-13826105]
>>>>
>>>> Lahiru Sandaruwan commented on STRATOS-204:
>>>> -------------------------------------------
>>>>
>>>> Nirmal,
>>>>
>>>> FYI.
>>>> Terminating instances when unsubscribed is done by Cloud controller.
>>>>
>>>> Thanks.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> 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://twitter.com/lahiruslinked-in>:
>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>> > 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: Lahiru Sandaruwan
>>>> >            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
>>
>>
>
>
> --
> 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

Reply via email to