Comment:
Code blocks removed from expand sections, expand sections removed
...
This section describes how to upgrade from Abiquo 5.2.0 or above to an Abiquo 5.4.x version. Please contact Abiquo Support for further information.
Table of Contents
Numberedheadings
start-numbering-at
h2
This is a non-official upgrade document from which you can easily cut and paste the commands for each to prepare your own upgrade document.
The official upgrade document, that you must read and refer to for your upgrade is still
Abiquo YUM repositories are no longer open, please contact Abiquo Support to obtain your credentials
This upgrade process starts from Abiquo 5.4.0 or above. To upgrade from earlier versions, please see
false
The upgrade will overwrite lang_en_US.json. If you have customized labels or translations, back them up before the upgrade and restore them afterwards accordingly.
The upgrade will overwrite the SAML login configuration for multiple IdPs. If you use SAML with multiple IdPs, back up the configuration files before the upgrade and add the multiple IdPs afterwards accordingly. See
The upgrade to Abiquo 5.3 includes a migration to provider ID as the identifier of a deployed VM.
See
Prepare the provider ID migration before your upgrade. See
Prevent cloud users from performing VM operations
In the UI in the Infrastructure view, select each physical machine and click Disable
Using the API, set the state of each physical machine to DISABLED
API Servers
On each API Server do these steps. If you have a separate DB server, do the DB upgrade steps on that server.
API Server upgrade procedure
Additional API and UI upgrade steps
Add translations for new to lang_xx_XX_custom.json. See
Optionally add new configuration to client-config-custom.json. See Configure Abiquo UI
In your UI configuration, check that the API endpoint is pointing to your Abiquo API server: