More update on Implementation Scope:
1)When shutdown admin operation is in progress on a nodegroup, AMF will will
transition the nodes belonging to that nodegroup from SHUTTINGDOWN to LOCKED
admin state. So after completion of shutdown operation, nodegroup and nodes of
nodegroup will be in admin locked state.
2) Since individual nodes of nodegroup are also marked LOCKED as a part of
shutdown operation, user will be able to delete the node group after the
SHUTDOWN operation is complete.
3) After the nodegroup SHUTDOW, the user can unlock either the individual nodes
by performing unlock on that node OR by performing unlock operation on that
nodegorup.
If unlock admin op is targeted on nodegroup, all nodes of nodegroup will be
marked unlocked by AMF.
Note: When unlock admin op is targeted on nodegroup, SUs on individual nodes
will be assigned based on the overall status and redundancy model of the
containing service group and also on whether the redundancy requirements of the
service instance are being met.
4)Besides Nway_Active and NoRed models, 2N model will also be supported.
---
** [tickets:#1235] NodeGroup shutdown Admin op to support parallel admin
shutdown on multiple nodes**
**Status:** assigned
**Milestone:** 4.6.FC
**Created:** Wed Dec 10, 2014 12:25 PM UTC by Mathi Naickan
**Last Updated:** Mon Feb 02, 2015 10:01 AM UTC
**Owner:** Praveen
Today, it is not possible to initiate AMF node shutdown operation on multiple
nodes at the same time.
This ticket proposes (praveen's idea) to introduce a new AMF admin operation on
the nodegroup logical entity.
A cluter scale-down usecase might introduce limits on the total time spent in
down-sizing an AMF/application cluster. This enhancement shall look into
different ways by which atleast some amount of parallelism is induced/pushing
within AMF (wherever applicable) during the processing of this new 'node-group'
shutdown operation.
End of the day, the final timetake will be a mix of
1) amount of time spent in the checks inside AMF during processing of a
parallel admin_op.
+
2) how quicky applications respond to the csi callbacks.
Atleast to start with one redundancy model...
More later... Nagendra, Praveen would update on the details on the scenarios in
which AMF would still continue to do serial processing i.e. where existing
checks cannot be removed, etc....
(The bigger opportunity is also not to overlty complicate AMF by introducing
this adminop)
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
