>From bertils powerpoint
Proposed solution
-----------------
Use existing rolling procedures but add new IMM configuration object that tells
SMF how to execute the upgrade (one node at the time, all at once, several
nodes at the same time). The information describing how to upgrade is given in
IMM objects. This means we use the existing campaign schema.
Add possibility to configure a reboot upgrade (all nodes at the same time) as
first priority. Then add rolling upgrade (one node at the time) as second
priority.
As third priority add the possibility to configure upgrade of several nodes at
the same time. This step requires more work to define exactly how you describe
how many and what nodes should be upgraded at the same time.
This solution implies that applications can reuse their existing campaign files
and does not need to adapt to this new feature (however testing is needed).
Issues to be considered during implementation
---------------------------------------------
1) How to handle callbacks?
Callbacks is a mechanism in SMF where a campaign can specify that a certain
callback should be sent out at a certain time during the upgrade. Any SW can
subscribe to these callbacks and do something when they arrive. The callbacks
is sometimes related to the steps in a procedure (first, every, halfway or last
step).
2) How will the alternatives work with parallel node lock support in AMF. (e.g.
lock/unlock on Node group)
If the procedures specifies nodes as activation unit SMF will lock the nodes
one by one i.e. not in parallel (AMF can today only do one lock at the time).
So SMF has to create temporary node group and do lock etc on that object. The
new procedure type can specify node groups directly but someone still need to
create them.
3) How to handle single step procedures?
If a campaign also includes single step procedures, what to do? Could be
installation procedure for new CBA component.
---
** [tickets:#1401] smf: upgrade time improvement**
**Status:** assigned
**Milestone:** future
**Created:** Mon Jul 06, 2015 08:58 AM UTC by Rafael
**Last Updated:** Thu Jul 09, 2015 09:00 AM UTC
**Owner:** Rafael
Decrease the execution time for campaigns by merging parallel procedures.
Parallel procedures are procedures that have saSmfExecLevel set to the same
value. When procedures are merged they will be executed in one thread. Today
procedures are executed in separate threads with possible cluster/node reboots
in each procedure. When procedures are merged they would install multiple
software packages on a node with one reboot at the end.
There are three use cases
* Upgrade one node at the time in the cluster
* Upgrade all nodes at once using cluster reboot
* Upgrade several nodes at once
There will be an IMM attribute that decides if procedures are to be merged to
maintain backward compatibility.
---
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.
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
