Upgrading Standalone ESC Instance
To upgrade standalone ESC instance, perform the following tasks:
Back up the ESC database. For more information, see Backup the Database for ESC Standalone Instance.
To backup any custom scripts used by the deployments, and for restoring them before restoring the database, you must re-install the scripts on the backup as well.
Redeploy the ESC instance. For more information, see the below section, Deploy the ESC for Upgrade.
Restore the ESC database on the new ESC instance. For more information, see the below section, Restoring the ESC Database.
Deploy the ESC for Upgrade
- For OpenStack, you need to
register the new ESC qcow2 image using the Glance command with a new image name
and then use new bootvm.py script and new image name to install ESC VM.
In OpenStack, if an old ESC VM was assigned with floating IP, the new ESC VM should be associated with the same floating IP after the installation.
- For VMWare, you need to use the new ESC OVA file to install ESC VM. All other configurations and property values should be the same as the old VM.
Restoring the ESC Database
Restore the ESC database on the new ESC instance , using the following procedure:
Connect to the new ESC instance using SSH.
Switch to the root user.
Stop the ESC service.
Check ESC service status to make sure all the services are stopped.
Restore the database files.
Restart the ESC service:
After ESC service is started, the standalone ESC upgrade is complete. You can check the health of the new ESC service by running
In Openstack, after restoring the database successfully, delete the old ESC instance: