You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Isuru Haththotuwa <is...@apache.org> on 2014/10/17 09:16:48 UTC

[Discuss] Validating Life Cycle Transitions for Topology Elements

Hi Devs,

The purpose of this thread is to discuss $subject.

Currently, even though the topology elements (Members, Clusters, etc) go
through a life cycle, we do not validate the transitions. For an example, a
Member can have the following life cycle:

[image: Inline image 1]

IMHO its important to keep track of the transitions and see if the change
of state is valid as well.
Ex. A member can't go from Created state to Activated state without passing
through the Started state. If there is such a thing, it might mean that the
member is in an inconsistent state. Therefore, we need to validate this
transitions.

Thoughts?


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* <http://wso2.com/>*

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

Posted by Imesh Gunaratne <im...@apache.org>.
A good suggestion Chamila, I have now updated the diagram:



@Isuru: Great, yes will start from here and improve it as we go on.

Thanks
​

On Tue, Oct 21, 2014 at 10:50 AM, Isuru Haththotuwa <is...@apache.org>
wrote:

> Hi Imesh,
>
> On Sat, Oct 18, 2014 at 10:40 AM, Imesh Gunaratne <im...@apache.org>
> wrote:
>
>> Hi Isuru,
>>
>> I have done some changes to the Member Lifecycle and also added events:
>>
>>
>> Things changed:
>> - I have introduced a new state called Inactive. Currently we detect
>> members as Inactive but it is not reflected in topology, rather we
>> straightway consider those as Faulty members and terminate them. May be we
>> can split the member faulty timeout into two parts and first detect them as
>> Inactive and then after the second timeout consider them as Faulty and
>> terminate. In this way there is a buffer time for the members to come back
>> to Active state. WDYT?
>>
>> - I have renamed "Activated" to "Active" since we introduced Inactive
>> state.
>>
>> - I have renamed "In Maintenance" to "Pre Terminate" because "In
>> Maintenance" would not mean that the member is about to be terminated.
>>
>> Please add your thoughts.
>>
> Sorry for the delayed response. +1 for this. I believe we use this as a
> starting point, and improve as we go on.
>
>>
>> Thanks
>> ​
>>
>> On Fri, Oct 17, 2014 at 5:38 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>> Hi all,
>>>
>>> I do agree that there might be many changes that we need for this state
>>> diagram. That will need to be developed as we go on. The idea is to discuss
>>> the use of validating state changes, for any state diagram that we come
>>> upon.
>>>
>>> On Fri, Oct 17, 2014 at 3:09 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Could you mention what events/actions causes the state transition from
>>>> Activate to Terminate?
>>>>
>>>> My next question is what happens when member diapered when it is in
>>>> In-Maintaince mode?  Does this state transition is applicable to obsolete
>>>> members also.
>>>>
>>>> On Fri, Oct 17, 2014 at 2:55 PM, Chamila De Alwis <ch...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> In the container based scenario, aren't the members immediately
>>>>> terminated without going in to the maintenance mode?
>>>>>
>>>>>
>>>>> Regards,
>>>>> Chamila de Alwis
>>>>> Software Engineer | WSO2 | +94772207163
>>>>> Blog: code.chamiladealwis.com
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Oct 17, 2014 at 1:11 PM, Manula Chathurika Thantriwatte <
>>>>> manulac@wso2.com> wrote:
>>>>>
>>>>>> Hi Isuru,
>>>>>>
>>>>>> IMO is we need to verify the life cycle in between Activated and
>>>>>> Terminated modes. We not need to verify the created and started, because
>>>>>> without started members want come to activated state.
>>>>>>
>>>>>> Thanks !
>>>>>>
>>>>>> On Fri, Oct 17, 2014 at 12:46 PM, Isuru Haththotuwa <
>>>>>> isuruh@apache.org> wrote:
>>>>>>
>>>>>>> Hi Devs,
>>>>>>>
>>>>>>> The purpose of this thread is to discuss $subject.
>>>>>>>
>>>>>>> Currently, even though the topology elements (Members, Clusters,
>>>>>>> etc) go through a life cycle, we do not validate the transitions. For an
>>>>>>> example, a Member can have the following life cycle:
>>>>>>>
>>>>>>> [image: Inline image 1]
>>>>>>>
>>>>>>> IMHO its important to keep track of the transitions and see if the
>>>>>>> change of state is valid as well.
>>>>>>> Ex. A member can't go from Created state to Activated state without
>>>>>>> passing through the Started state. If there is such a thing, it might mean
>>>>>>> that the member is in an inconsistent state. Therefore, we need to validate
>>>>>>> this transitions.
>>>>>>>
>>>>>>> Thoughts?
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> +94 716 358 048* <http://wso2.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/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Udara Liyanage
>>>> Software Engineer
>>>> WSO2, Inc.: http://wso2.com
>>>> lean. enterprise. middleware
>>>>
>>>> web: http://udaraliyanage.wordpress.com
>>>> phone: +94 71 443 6897
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> +94 716 358 048* <http://wso2.com/>*
>>>>
>>>>
>>>> * <http://wso2.com/>*
>>>>
>>>>
>>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>


-- 
Imesh Gunaratne

Technical Lead, WSO2
Committer & PMC Member, Apache Stratos

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

Posted by Isuru Haththotuwa <is...@apache.org>.
Hi Imesh,

On Sat, Oct 18, 2014 at 10:40 AM, Imesh Gunaratne <im...@apache.org> wrote:

> Hi Isuru,
>
> I have done some changes to the Member Lifecycle and also added events:
>
>
> Things changed:
> - I have introduced a new state called Inactive. Currently we detect
> members as Inactive but it is not reflected in topology, rather we
> straightway consider those as Faulty members and terminate them. May be we
> can split the member faulty timeout into two parts and first detect them as
> Inactive and then after the second timeout consider them as Faulty and
> terminate. In this way there is a buffer time for the members to come back
> to Active state. WDYT?
>
> - I have renamed "Activated" to "Active" since we introduced Inactive
> state.
>
> - I have renamed "In Maintenance" to "Pre Terminate" because "In
> Maintenance" would not mean that the member is about to be terminated.
>
> Please add your thoughts.
>
Sorry for the delayed response. +1 for this. I believe we use this as a
starting point, and improve as we go on.

>
> Thanks
> ​
>
> On Fri, Oct 17, 2014 at 5:38 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>> Hi all,
>>
>> I do agree that there might be many changes that we need for this state
>> diagram. That will need to be developed as we go on. The idea is to discuss
>> the use of validating state changes, for any state diagram that we come
>> upon.
>>
>> On Fri, Oct 17, 2014 at 3:09 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Could you mention what events/actions causes the state transition from
>>> Activate to Terminate?
>>>
>>> My next question is what happens when member diapered when it is in
>>> In-Maintaince mode?  Does this state transition is applicable to obsolete
>>> members also.
>>>
>>> On Fri, Oct 17, 2014 at 2:55 PM, Chamila De Alwis <ch...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> In the container based scenario, aren't the members immediately
>>>> terminated without going in to the maintenance mode?
>>>>
>>>>
>>>> Regards,
>>>> Chamila de Alwis
>>>> Software Engineer | WSO2 | +94772207163
>>>> Blog: code.chamiladealwis.com
>>>>
>>>>
>>>>
>>>> On Fri, Oct 17, 2014 at 1:11 PM, Manula Chathurika Thantriwatte <
>>>> manulac@wso2.com> wrote:
>>>>
>>>>> Hi Isuru,
>>>>>
>>>>> IMO is we need to verify the life cycle in between Activated and
>>>>> Terminated modes. We not need to verify the created and started, because
>>>>> without started members want come to activated state.
>>>>>
>>>>> Thanks !
>>>>>
>>>>> On Fri, Oct 17, 2014 at 12:46 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>> > wrote:
>>>>>
>>>>>> Hi Devs,
>>>>>>
>>>>>> The purpose of this thread is to discuss $subject.
>>>>>>
>>>>>> Currently, even though the topology elements (Members, Clusters, etc)
>>>>>> go through a life cycle, we do not validate the transitions. For an
>>>>>> example, a Member can have the following life cycle:
>>>>>>
>>>>>> [image: Inline image 1]
>>>>>>
>>>>>> IMHO its important to keep track of the transitions and see if the
>>>>>> change of state is valid as well.
>>>>>> Ex. A member can't go from Created state to Activated state without
>>>>>> passing through the Started state. If there is such a thing, it might mean
>>>>>> that the member is in an inconsistent state. Therefore, we need to validate
>>>>>> this transitions.
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> +94 716 358 048* <http://wso2.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/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> web: http://udaraliyanage.wordpress.com
>>> phone: +94 71 443 6897
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* <http://wso2.com/>*
>>>
>>>
>>> * <http://wso2.com/>*
>>>
>>>
>>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

Posted by Imesh Gunaratne <im...@apache.org>.
+1

On Sat, Oct 18, 2014 at 11:07 PM, Isuru Haththotuwa <is...@apache.org>
wrote:

> The initial API for validating and changing states will support the
> following methods:
>
>
>    /**
>      * Checks if the state transition is valid
>      *
>      * @param nextState Next state that for the topology element
>      * @return true if transitioning for nextState from current state is
> valid, else false
>      */
>     public boolean isStateTransitionValid (State nextState) ;
>
>     /**
>      * Changes the current state to nextState
>      *
>      * @param nextState next state for the element
>      */
>     public void changeState (State nextState) ;
>
>     /**
>      * Get all the states this element has gone through
>      *
>      * @return stack of states
>      */
>     public Stack<State> getStateStack () ;
>
>     /**
>      * Get the current state
>      *
>      * @return the current state
>      */
>     public State getCurrentState ();
>
> On Sat, Oct 18, 2014 at 12:29 PM, Imesh Gunaratne <im...@apache.org>
> wrote:
>
>>
>> On Sat, Oct 18, 2014 at 10:43 AM, Udara Liyanage <ud...@wso2.com> wrote:
>>
>>> Hi Imesh,
>>>
>>> 'Pre Terminate" and "Ready to terminate" seems confusing for a user,
>>> isn't it so?
>>>
>>> True, may be we can try to find a better term for this. I was thinking
>> to call it "Terminating" but again it's not correct.
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>


-- 
Imesh Gunaratne

Technical Lead, WSO2
Committer & PMC Member, Apache Stratos

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

Posted by Isuru Haththotuwa <is...@apache.org>.
The initial API for validating and changing states will support the
following methods:


   /**
     * Checks if the state transition is valid
     *
     * @param nextState Next state that for the topology element
     * @return true if transitioning for nextState from current state is
valid, else false
     */
    public boolean isStateTransitionValid (State nextState) ;

    /**
     * Changes the current state to nextState
     *
     * @param nextState next state for the element
     */
    public void changeState (State nextState) ;

    /**
     * Get all the states this element has gone through
     *
     * @return stack of states
     */
    public Stack<State> getStateStack () ;

    /**
     * Get the current state
     *
     * @return the current state
     */
    public State getCurrentState ();

On Sat, Oct 18, 2014 at 12:29 PM, Imesh Gunaratne <im...@apache.org> wrote:

>
> On Sat, Oct 18, 2014 at 10:43 AM, Udara Liyanage <ud...@wso2.com> wrote:
>
>> Hi Imesh,
>>
>> 'Pre Terminate" and "Ready to terminate" seems confusing for a user,
>> isn't it so?
>>
>> True, may be we can try to find a better term for this. I was thinking to
> call it "Terminating" but again it's not correct.
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

Posted by Chamila De Alwis <ch...@wso2.com>.
On Sat, Oct 18, 2014 at 12:29 PM, Imesh Gunaratne <im...@apache.org> wrote:

> True, may be we can try to find a better term for this. I was thinking to
> call it "Terminating" but again it's not correct.


May be "PendingTermination"?




Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

Posted by Imesh Gunaratne <im...@apache.org>.
On Sat, Oct 18, 2014 at 10:43 AM, Udara Liyanage <ud...@wso2.com> wrote:

> Hi Imesh,
>
> 'Pre Terminate" and "Ready to terminate" seems confusing for a user, isn't
> it so?
>
> True, may be we can try to find a better term for this. I was thinking to
call it "Terminating" but again it's not correct.


-- 
Imesh Gunaratne

Technical Lead, WSO2
Committer & PMC Member, Apache Stratos

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

Posted by Udara Liyanage <ud...@wso2.com>.
Hi Imesh,

'Pre Terminate" and "Ready to terminate" seems confusing for a user, isn't
it so?

On Sat, Oct 18, 2014 at 10:40 AM, Imesh Gunaratne <im...@apache.org> wrote:

> Hi Isuru,
>
> I have done some changes to the Member Lifecycle and also added events:
>
>
> Things changed:
> - I have introduced a new state called Inactive. Currently we detect
> members as Inactive but it is not reflected in topology, rather we
> straightway consider those as Faulty members and terminate them. May be we
> can split the member faulty timeout into two parts and first detect them as
> Inactive and then after the second timeout consider them as Faulty and
> terminate. In this way there is a buffer time for the members to come back
> to Active state. WDYT?
>
> - I have renamed "Activated" to "Active" since we introduced Inactive
> state.
>
> - I have renamed "In Maintenance" to "Pre Terminate" because "In
> Maintenance" would not mean that the member is about to be terminated.
>
> Please add your thoughts.
>
> Thanks
> ​
>
> On Fri, Oct 17, 2014 at 5:38 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>> Hi all,
>>
>> I do agree that there might be many changes that we need for this state
>> diagram. That will need to be developed as we go on. The idea is to discuss
>> the use of validating state changes, for any state diagram that we come
>> upon.
>>
>> On Fri, Oct 17, 2014 at 3:09 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Could you mention what events/actions causes the state transition from
>>> Activate to Terminate?
>>>
>>> My next question is what happens when member diapered when it is in
>>> In-Maintaince mode?  Does this state transition is applicable to obsolete
>>> members also.
>>>
>>> On Fri, Oct 17, 2014 at 2:55 PM, Chamila De Alwis <ch...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> In the container based scenario, aren't the members immediately
>>>> terminated without going in to the maintenance mode?
>>>>
>>>>
>>>> Regards,
>>>> Chamila de Alwis
>>>> Software Engineer | WSO2 | +94772207163
>>>> Blog: code.chamiladealwis.com
>>>>
>>>>
>>>>
>>>> On Fri, Oct 17, 2014 at 1:11 PM, Manula Chathurika Thantriwatte <
>>>> manulac@wso2.com> wrote:
>>>>
>>>>> Hi Isuru,
>>>>>
>>>>> IMO is we need to verify the life cycle in between Activated and
>>>>> Terminated modes. We not need to verify the created and started, because
>>>>> without started members want come to activated state.
>>>>>
>>>>> Thanks !
>>>>>
>>>>> On Fri, Oct 17, 2014 at 12:46 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>> > wrote:
>>>>>
>>>>>> Hi Devs,
>>>>>>
>>>>>> The purpose of this thread is to discuss $subject.
>>>>>>
>>>>>> Currently, even though the topology elements (Members, Clusters, etc)
>>>>>> go through a life cycle, we do not validate the transitions. For an
>>>>>> example, a Member can have the following life cycle:
>>>>>>
>>>>>> [image: Inline image 1]
>>>>>>
>>>>>> IMHO its important to keep track of the transitions and see if the
>>>>>> change of state is valid as well.
>>>>>> Ex. A member can't go from Created state to Activated state without
>>>>>> passing through the Started state. If there is such a thing, it might mean
>>>>>> that the member is in an inconsistent state. Therefore, we need to validate
>>>>>> this transitions.
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> +94 716 358 048* <http://wso2.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/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> web: http://udaraliyanage.wordpress.com
>>> phone: +94 71 443 6897
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* <http://wso2.com/>*
>>>
>>>
>>> * <http://wso2.com/>*
>>>
>>>
>>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>



-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

Posted by Imesh Gunaratne <im...@apache.org>.
Hi Isuru,

I have done some changes to the Member Lifecycle and also added events:


Things changed:
- I have introduced a new state called Inactive. Currently we detect
members as Inactive but it is not reflected in topology, rather we
straightway consider those as Faulty members and terminate them. May be we
can split the member faulty timeout into two parts and first detect them as
Inactive and then after the second timeout consider them as Faulty and
terminate. In this way there is a buffer time for the members to come back
to Active state. WDYT?

- I have renamed "Activated" to "Active" since we introduced Inactive state.

- I have renamed "In Maintenance" to "Pre Terminate" because "In
Maintenance" would not mean that the member is about to be terminated.

Please add your thoughts.

Thanks
​

On Fri, Oct 17, 2014 at 5:38 PM, Isuru Haththotuwa <is...@apache.org>
wrote:

> Hi all,
>
> I do agree that there might be many changes that we need for this state
> diagram. That will need to be developed as we go on. The idea is to discuss
> the use of validating state changes, for any state diagram that we come
> upon.
>
> On Fri, Oct 17, 2014 at 3:09 PM, Udara Liyanage <ud...@wso2.com> wrote:
>
>> Hi,
>>
>> Could you mention what events/actions causes the state transition from
>> Activate to Terminate?
>>
>> My next question is what happens when member diapered when it is in
>> In-Maintaince mode?  Does this state transition is applicable to obsolete
>> members also.
>>
>> On Fri, Oct 17, 2014 at 2:55 PM, Chamila De Alwis <ch...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> In the container based scenario, aren't the members immediately
>>> terminated without going in to the maintenance mode?
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>> On Fri, Oct 17, 2014 at 1:11 PM, Manula Chathurika Thantriwatte <
>>> manulac@wso2.com> wrote:
>>>
>>>> Hi Isuru,
>>>>
>>>> IMO is we need to verify the life cycle in between Activated and
>>>> Terminated modes. We not need to verify the created and started, because
>>>> without started members want come to activated state.
>>>>
>>>> Thanks !
>>>>
>>>> On Fri, Oct 17, 2014 at 12:46 PM, Isuru Haththotuwa <is...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> The purpose of this thread is to discuss $subject.
>>>>>
>>>>> Currently, even though the topology elements (Members, Clusters, etc)
>>>>> go through a life cycle, we do not validate the transitions. For an
>>>>> example, a Member can have the following life cycle:
>>>>>
>>>>> [image: Inline image 1]
>>>>>
>>>>> IMHO its important to keep track of the transitions and see if the
>>>>> change of state is valid as well.
>>>>> Ex. A member can't go from Created state to Activated state without
>>>>> passing through the Started state. If there is such a thing, it might mean
>>>>> that the member is in an inconsistent state. Therefore, we need to validate
>>>>> this transitions.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>>
>>>>> --
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> +94 716 358 048* <http://wso2.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/
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>


-- 
Imesh Gunaratne

Technical Lead, WSO2
Committer & PMC Member, Apache Stratos

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

Posted by Isuru Haththotuwa <is...@apache.org>.
Hi all,

I do agree that there might be many changes that we need for this state
diagram. That will need to be developed as we go on. The idea is to discuss
the use of validating state changes, for any state diagram that we come
upon.

On Fri, Oct 17, 2014 at 3:09 PM, Udara Liyanage <ud...@wso2.com> wrote:

> Hi,
>
> Could you mention what events/actions causes the state transition from
> Activate to Terminate?
>
> My next question is what happens when member diapered when it is in
> In-Maintaince mode?  Does this state transition is applicable to obsolete
> members also.
>
> On Fri, Oct 17, 2014 at 2:55 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> Hi,
>>
>> In the container based scenario, aren't the members immediately
>> terminated without going in to the maintenance mode?
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Fri, Oct 17, 2014 at 1:11 PM, Manula Chathurika Thantriwatte <
>> manulac@wso2.com> wrote:
>>
>>> Hi Isuru,
>>>
>>> IMO is we need to verify the life cycle in between Activated and
>>> Terminated modes. We not need to verify the created and started, because
>>> without started members want come to activated state.
>>>
>>> Thanks !
>>>
>>> On Fri, Oct 17, 2014 at 12:46 PM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> The purpose of this thread is to discuss $subject.
>>>>
>>>> Currently, even though the topology elements (Members, Clusters, etc)
>>>> go through a life cycle, we do not validate the transitions. For an
>>>> example, a Member can have the following life cycle:
>>>>
>>>> [image: Inline image 1]
>>>>
>>>> IMHO its important to keep track of the transitions and see if the
>>>> change of state is valid as well.
>>>> Ex. A member can't go from Created state to Activated state without
>>>> passing through the Started state. If there is such a thing, it might mean
>>>> that the member is in an inconsistent state. Therefore, we need to validate
>>>> this transitions.
>>>>
>>>> Thoughts?
>>>>
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> +94 716 358 048* <http://wso2.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/
>>>
>>>
>>>
>>>
>>
>
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

Posted by Udara Liyanage <ud...@wso2.com>.
Hi,

Could you mention what events/actions causes the state transition from
Activate to Terminate?

My next question is what happens when member diapered when it is in
In-Maintaince mode?  Does this state transition is applicable to obsolete
members also.

On Fri, Oct 17, 2014 at 2:55 PM, Chamila De Alwis <ch...@wso2.com> wrote:

> Hi,
>
> In the container based scenario, aren't the members immediately terminated
> without going in to the maintenance mode?
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Fri, Oct 17, 2014 at 1:11 PM, Manula Chathurika Thantriwatte <
> manulac@wso2.com> wrote:
>
>> Hi Isuru,
>>
>> IMO is we need to verify the life cycle in between Activated and
>> Terminated modes. We not need to verify the created and started, because
>> without started members want come to activated state.
>>
>> Thanks !
>>
>> On Fri, Oct 17, 2014 at 12:46 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> The purpose of this thread is to discuss $subject.
>>>
>>> Currently, even though the topology elements (Members, Clusters, etc) go
>>> through a life cycle, we do not validate the transitions. For an example, a
>>> Member can have the following life cycle:
>>>
>>> [image: Inline image 1]
>>>
>>> IMHO its important to keep track of the transitions and see if the
>>> change of state is valid as well.
>>> Ex. A member can't go from Created state to Activated state without
>>> passing through the Started state. If there is such a thing, it might mean
>>> that the member is in an inconsistent state. Therefore, we need to validate
>>> this transitions.
>>>
>>> Thoughts?
>>>
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* <http://wso2.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/
>>
>>
>>
>>
>


-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897

Re: [Discuss] Validating Life Cycle Transitions for Topology Elements

Posted by Chamila De Alwis <ch...@wso2.com>.
Hi,

In the container based scenario, aren't the members immediately terminated
without going in to the maintenance mode?


Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com



On Fri, Oct 17, 2014 at 1:11 PM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:

> Hi Isuru,
>
> IMO is we need to verify the life cycle in between Activated and
> Terminated modes. We not need to verify the created and started, because
> without started members want come to activated state.
>
> Thanks !
>
> On Fri, Oct 17, 2014 at 12:46 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>> Hi Devs,
>>
>> The purpose of this thread is to discuss $subject.
>>
>> Currently, even though the topology elements (Members, Clusters, etc) go
>> through a life cycle, we do not validate the transitions. For an example, a
>> Member can have the following life cycle:
>>
>> [image: Inline image 1]
>>
>> IMHO its important to keep track of the transitions and see if the change
>> of state is valid as well.
>> Ex. A member can't go from Created state to Activated state without
>> passing through the Started state. If there is such a thing, it might mean
>> that the member is in an inconsistent state. Therefore, we need to validate
>> this transitions.
>>
>> Thoughts?
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.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: [Discuss] Validating Life Cycle Transitions for Topology Elements

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

IMO is we need to verify the life cycle in between Activated and Terminated
modes. We not need to verify the created and started, because without
started members want come to activated state.

Thanks !

On Fri, Oct 17, 2014 at 12:46 PM, Isuru Haththotuwa <is...@apache.org>
wrote:

> Hi Devs,
>
> The purpose of this thread is to discuss $subject.
>
> Currently, even though the topology elements (Members, Clusters, etc) go
> through a life cycle, we do not validate the transitions. For an example, a
> Member can have the following life cycle:
>
> [image: Inline image 1]
>
> IMHO its important to keep track of the transitions and see if the change
> of state is valid as well.
> Ex. A member can't go from Created state to Activated state without
> passing through the Started state. If there is such a thing, it might mean
> that the member is in an inconsistent state. Therefore, we need to validate
> this transitions.
>
> Thoughts?
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.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/