Red Hat Bugzilla – Bug 910816
[RFE] node upgrade command-line interface
Last modified: 2014-01-21 14:25:05 EST
+++ This bug was initially created as a clone of Bug #858596 +++ Following discussion, was asked to open RFE, did not find RFE category, please feel free to label this correctly. Will be glad to discuss this. --- MISSION Providing component independent node upgrade command-line interface. REASON Node base should provide life cycle management: - install - provided. - reinstall - provided. - upgrade via boot - provided. - upgrade via command-line - provided indirectly as an API. Node upgrade is not related to any hosted components, for example VDSM. Node infrastructure is the one that knows the filesystem structure, where to put large images, what is the image format etc... No reason to expose these to hosted components. USAGE ovirt-node-upgrade [--reboot[=NN]] [-f|--image image|-] --reboot perform reboot after installation, defer to NN seconds, default=10. -f, --image read node image from this file, '-' is stdin. HOOKS In order to allow hosted components to take action during upgrade, hooks mechanism is suggested. A directory for each state, each directory contains files/symlinks, which will be executed alphabetical sorted. /usr/libexec/ovirt-node/hooks/ pre-upgrade 000-vdsm post-upgrade rollback 900-vdsm At the above example, VDSM will be stopped before upgrade, and started if rollbacked. LOGIC At least: 1. If image is read from stdin, read image and store it on the filesystem within temporary location. 2. Verify image integrity, using md5sum of the iso. 3. Execute pre-upgrade hooks. 4. Mount^^3 the image, execute image upgrade. 5. Delete the image from temporary location if read from stdin. 6. Execute post-upgrade or rollback hooks. 7. Optionally async reboot. SIMPLE TEST CASE $ cat ovirt-node.iso | ssh root@node "ovirt-node-upgrade --reboot -f -" --- Additional comment from Alon Bar-Lev on 2012-09-19 05:29:43 EDT --- I forgot two more hooks I would like to have... On the image it-self, pre-image-upgrade, post-image-upgrade, so that the new component on the image can execute some logic during upgrade.
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0033.html