--- old+++ new@@ -1 +1,3 @@
As a continuation of ticket [#1235], the N+M redundancy model could also be supported for the shutdown admin-op on AMF node groups.
++Note: SI deps will not be honored, within SU, while giving quiesced/quiescing assigments.
--- old+++ new@@ -1,3 +1,8 @@-As a continuation of ticket [#1235], the N+M redundancy model could also be supported for the shutdown admin-op on AMF node groups.+This ticket aims to support N+M model for:+1)shutdown,+2) lock, +3) lock-in and+4) unlock-in +operations on nodegroup.
Note: SI deps will not be honored, within SU, while giving quiesced/quiescing assigments.
High Level Changes at AMFD:
-Currently nodegroup.cc contains all checks related to validityof admin operation on NG hosting SU of a given red model. These checks are applicable to sg of N+M model also. There is almost no change in this file except the removal of check on red model.
-After checking validity of lock and shutdown operation, AMFD calls SG FSM function for assignment handling for each SU hosted on a given node from NG's node list. Thus a new function ng_admin() is added in sg_npm_fsm.cc. This new function works at su level. Depending upon the HA state of SU, assignment message is sent to the Node director that hosts this SU. If SU has active state then quiescing or quiesced HA state is sent respectively for shutdown and lock operation. If SU has standby HA state then removal is sent for both shutdown and lock operations. SG is moved to REALIGN state. Upon receiving successful response for quiescing or quiesced assignements, AMFD tries to switchover this SU by making its peer SU active if SU is not assigned on nodes of this nodegroup. If switchover of whole SU is not possbile then AMFD tries to make as many SUSI active as possible and removing other SUSI from the peer SU. In case of successful removal o assignments, SUSIs are deleted at AMFD. In case of shutdown admin op, initial admin state of NG and Node will be SHUTTING_DOWN. When all the SUs of a node moves to quiesced state then Node transitions to LOCKED state. A NG transitions to LOCKED state when all its nodes transitions to LOCKED state. Admin operation finishes when all assignments gets removed in each SU hosted on nodes of NG. Since SG is moved to REALIGN state, any faults occured during assignment is handled by re-using red-model specific fault related code functions.
-For lock-in and unlock-in admin operations, there are no new changes execpt the removal of check on red models. In case of unlock-in operation, SUs are instantiated honoring PrefInserviceSU criteria.
-For unlock operations, SUs are assigned based on their ranks in SG on the nodes of NG. This is currenlty done by calling su_insvc() function from nodegroup.cc. There are also no new changes in this area execpt removal of red model check.
Note: There are no changes at AMFND and AMFA.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
changeset: 7964:321aa331e5b5
user: praveen.malviya@oracle.com
date: Mon Aug 29 14:27:10 2016 +0530
summary: amfd: support NplusM model for supported admin ops on NG [#1454]
Diff:
Related
Tickets:
#1235Test configurations.
Diff:
Related
Tickets:
#1235High Level Changes at AMFD:
-Currently nodegroup.cc contains all checks related to validityof admin operation on NG hosting SU of a given red model. These checks are applicable to sg of N+M model also. There is almost no change in this file except the removal of check on red model.
-After checking validity of lock and shutdown operation, AMFD calls SG FSM function for assignment handling for each SU hosted on a given node from NG's node list. Thus a new function ng_admin() is added in sg_npm_fsm.cc. This new function works at su level. Depending upon the HA state of SU, assignment message is sent to the Node director that hosts this SU. If SU has active state then quiescing or quiesced HA state is sent respectively for shutdown and lock operation. If SU has standby HA state then removal is sent for both shutdown and lock operations. SG is moved to REALIGN state. Upon receiving successful response for quiescing or quiesced assignements, AMFD tries to switchover this SU by making its peer SU active if SU is not assigned on nodes of this nodegroup. If switchover of whole SU is not possbile then AMFD tries to make as many SUSI active as possible and removing other SUSI from the peer SU. In case of successful removal o assignments, SUSIs are deleted at AMFD. In case of shutdown admin op, initial admin state of NG and Node will be SHUTTING_DOWN. When all the SUs of a node moves to quiesced state then Node transitions to LOCKED state. A NG transitions to LOCKED state when all its nodes transitions to LOCKED state. Admin operation finishes when all assignments gets removed in each SU hosted on nodes of NG. Since SG is moved to REALIGN state, any faults occured during assignment is handled by re-using red-model specific fault related code functions.
-For lock-in and unlock-in admin operations, there are no new changes execpt the removal of check on red models. In case of unlock-in operation, SUs are instantiated honoring PrefInserviceSU criteria.
-For unlock operations, SUs are assigned based on their ranks in SG on the nodes of NG. This is currenlty done by calling su_insvc() function from nodegroup.cc. There are also no new changes in this area execpt removal of red model check.
Note: There are no changes at AMFND and AMFA.
Patches for #1454 and #1608. rebased on long dn changes.
changeset: 7964:321aa331e5b5
user: praveen.malviya@oracle.com
date: Mon Aug 29 14:27:10 2016 +0530
summary: amfd: support NplusM model for supported admin ops on NG [#1454]
Related
Tickets:
#1454Added Readme based on Minh's comment in changeset:
changeset: 7970:4bbc1bd1ef8d
user: praveen.malviya@oracle.com
date: Mon Aug 29 17:40:56 2016 +0530
summary: amfd: add README_NODEGROUP for nodegroup implementation [#1454, #1608]