Hi Imesh,
On Sat, Oct 18, 2014 at 10:40 AM, Imesh Gunaratne 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
On Sat, Oct 18, 2014 at 12:29 PM, Imesh Gunaratne 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.
+1
On Sat, Oct 18, 2014 at 11:07 PM, Isuru Haththotuwa
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
>
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
On Sat, Oct 18, 2014 at 10:43 AM, Udara Liyanage 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 G
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 wrote:
> Hi Isuru,
>
> I have done some changes to the Member Lifecycle and also added events:
>
>
> Things changed:
> - I have introduced a new state ca
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 the
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 wrote:
> Hi,
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 D
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 <
manu...@ws
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
wrote:
> Hi Devs,
>
> The purpo
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 t
12 matches
Mail list logo
