#1455 amf: support for RESTART admin operation on SU.

[Praveen]

Scope of implementation:
1)If su consists of all restartable components, then components in the SU will be terminated in reverse order of their instantiation level and instantiated honoring the instantiation level in the configured order. However Component of same instantiation level are not instantiated or terminated simultaneously. They are picked one by one as if they belong to different instantiation level.
2)If su consists of atleast one assigned non-restartable component then
SU will be marked OOS and there will be graceful reassignments of all SIs assigned to this SU to other SU. If no other SU is available to take the assignments then there will be graceful removal of assignments. This is applicable to SU of any redundancy model. In this way it becomes spec deviation for Nway and Nway Active redundancy models in which only assignments of non-restartable component should be reassigned to other SU.
3)Component presence state during surestart admin operation:
-presence state of a restartable component will remain in Restarting state when its termination and instantiaion is going on. After successful instantiation it will move from Restarting to Instantiated state. Thus its presence state will move from instantiated to restarting and from restarting to instantiated state.
-presence state of a non-restartable component will transition from instantiated to terminating state, then from terminating to uninstantiated, then from uninstantiated to instantiating and finally from instantiating to instantiated state.
4)For a NPI SU instantiation is done at the time of assignment. So for a NPI SU which is non restartable, operation will end when it moves to uninstantiated state.

[Praveen]

changeset: 6967:1e1d3d6fa606
tag: tip
user: praveen.malviya@oracle.com
date: Thu Oct 01 15:17:25 2015 +0530
summary: amf: support RESTART admin op on su [#1455]