- **status**: assigned --> accepted
- **Comment**:
This ticket represents the first of three development steps to minimize the
upgrade time.
This first step will allow the user to configure SMF to merge all procedures
(rolling and single step) in a campaign into a single step procedure.
A campaign is typically a result of merge of separate campaigns delivered with
different independent components. The drawback of this is that the campaign may
e.g. roll over the same node group several times. This will give major upgrade
time issues for operators having applications with problem to handle rolling
upgrades i.e. database applications may have to synch for each unlock in a
rolling upgrade. They sometime prefer system outage for a shorter time than
rolling upgrades going on for hours.
This patch will make it possible to write a campaign containing rolling
procedures (which most of the operators prefer) and in special cases order SMF
to run all the actions in a single step.
It will also help vendors which do not need to write specific campaigns for
these systems.
Campaign prerequisite: Procedures execution order must be independent.
-----------------------------
Coming steps are:
2) Merge campaign procedures into a rolling over nod procedure, which do all
actions from all procedures for the specific node within the same
lock/unlock/reboot sequence. This will prevent the campaign to run several
rolling procedures over the same nodes.
3) Not exactly decided, but will update sections of the cluster in a rolling
fashion.
E.g. SMF can be configured to update a 40 node cluster in chunks of 10 nodes
i.e. 10 nodes are upgraded single step. Four steps will be executed.
---
** [tickets:#1401] smf: upgrade time improvement**
**Status:** accepted
**Milestone:** 4.7.FC
**Created:** Mon Jul 06, 2015 08:58 AM UTC by Rafael
**Last Updated:** Tue Aug 25, 2015 04:08 PM 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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
