Page History
Add_workflow_for_techpubs | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
This Method of Procedure (MOP) describes the steps Use this procedure to downgrade the OAM and its managed VMs in an OpenStack Environment environment from the upgraded version to the desired base version.
Prerequisites
This section lists the prerequisites for performing the OAM downgrade:
- Ensure the OAM and managed nodes are up and running.
- Ensure the EMS
node is accessible.Spacevars 0 model3 - Ensure the EMS
includes a lower version of the config with it. Ensure the version is the same as the version in which the OAM will be downgraded.Spacevars 0 model3 - Ensure the SBC image is glanced.
Procedure
Log on to the EMS GUI
UI.Spacevars 0 model3 Navigate to Network → Cluster Management.
Caption 0 Table 1 Cluster Management - Select the cluster that contains the nodes which you need to downgrade.
Navigate to Configuration History.
From the table, select the revision that contains the same version as the software version to which the node will be downgraded.
Click Restore. See the example below, which shows the cluster configuration history of upgrading from 08.02.02R000 to 10.00.00R000, and then downgrading back to 08.02.02R000.
caption0 Figure 1 Configuration History Example
Perform downgrade of OAM and nodes by stack delete and create method.Info title Note With SBC 10.00.00R00, select any 8.02.02R000 revision (In this scenario, there are three revisions available as 1,2, and 3).
Consider revision 3 is restored. The OAM will download this revision and push back a new revision (revision 7 in the scenario of version 08.02.02R000).Auto-reboot of nodes does not work. The user after validating that the active revision in the cluster is the same as the lower version in which the downgrade is expected to perform.
- Once the new nodes are up, log on to the EMS
and validate a new revision contains a version of the new SBC image.Spacevars 0 model3