Difference between revisions of "Doc:Sdk 4.1/awdguide/upgrade"

 
m (1 revision)

Revision as of 19:07, 24 October 2011

Application Upgrade

After an application deployment is scheduled for an upgrade (by selecting it and clicking on the "upgrade" button in various places in the GUI). It appears in this upgrade page. Multiple upgradeable deployments can appear here simultaneously and you may run the upgrades simultaneously or sequentially as you wish.

Select the application deployments to be upgraded by clicking on the left checkbox. Next choose "rolling" or "single-step" upgrade on the right. "Rolling" upgrade executes an in-service algorithm in which the application is upgraded on each node sequentially ensuring that some nodes always remain to provide the application service. To use this method, applications must be capable of having different versions run simultaneously on the cluster. "Single-step" upgrade upgrades the application on every node simultaneously, causing a short interruption in service. However, this method does not require that application versions interoperate. These upgrade algorithms are explained in detail in the SAF SMF (Software Manageability Framework) specification.

Leave "automatic" as "yes" since manual upgrades are not yet supported.

When ready, click "Start". This page will be updated dynamically so you will see the upgrade's progress.

OpenClovis SAFplus Platform Web Director Upgrade Page

This is a view of an in-progress rolling upgrade. Note that the payloadI0 node is no longer running the application (its status is "down") and that it is being upgraded. Also note that the "payloadI1" node is up, and active -- it is providing the service during the upgrade of the "payloadI0" node.

OpenClovis SAFplus Platform Web Director Mid-Upgrade Page

When the upgrade is complete and you are satisfied with the correct operation, click "Commit" to remove it from the upgrade page.