Skip to content

Latest commit

 

History

History
312 lines (196 loc) · 8.51 KB

upgrade-4.13.rst

File metadata and controls

312 lines (196 loc) · 8.51 KB
Raw

Upgrade Instruction from 4.13.x

This section will show you how to upgrade from CloudStack 4.13.x to latest CloudStack .

Any steps that are hypervisor-specific will be called out with a note.

We recommend reading through this section once or twice before beginning your upgrade procedure, and working through it on a test system before working on a production system.

Note

The following upgrade instructions should be performed regardless of hypervisor type.

Overview of Upgrade Steps:

  1. Check any customisations and integrations
  2. Upload the System VM template if not already using it.
  3. Confirm Java 11 is the default Java version
  4. Stop all running management servers
  5. Backup CloudStack database (MySQL)
  6. Add "serverTimezone=UTC" to your "db.properties"
  7. Upgrade 1st CloudStack management server
  8. Update hypervisors specific dependencies
  9. Restart 1st management server
  10. Check that your upgraded environment works as expected
  11. Upgrade and restart the remaining management servers

Warning

If you are not already using the System VM template you will need to upgrade your System VM template prior to performing the upgrade of the CloudStack packages.

Packages repository

Most users of CloudStack manage the installation and upgrades of CloudStack with one of Linux's predominant package systems, RPM or APT. This guide assumes you'll be using RPM and Yum (for Red Hat Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).

Create RPM or Debian packages (as appropriate) and a repository from the source, or check the Apache CloudStack downloads page at http://cloudstack.apache.org/downloads.html for package repositories supplied by community members. You will need them for ubuntu413 or kvm413 hosts upgrade.

Instructions for creating packages from the CloudStack source are in the CloudStack Installation Guide.

Database Preparation

Backup current database

  1. Stop your management server or servers. Run this on all management server hosts:

    $ sudo service cloudstack-management stop

  2. If you are running a usage server or usage servers, stop those as well:

    $ sudo service cloudstack-usage stop

  3. Make a backup of your MySQL database. If you run into any issues or need to roll back the upgrade, this will assist in debugging or restoring your existing environment. You'll be prompted for your password.

    $ mysqldump -u root -p -R cloud > cloud-backup$(date +%Y-%m-%d-%H%M%S) $ mysqldump -u root -p cloud_usage > cloud_usage-backup$(date +%Y-%m-%d-%H%M%S)

Management Server

Ubuntu

If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step rhel413.

Note

Community Packages: This section assumes you're using the community supplied packages for CloudStack. If you've created your own packages and APT repository, substitute your own URL for the ones used in these examples.

The first order of business will be to change the sources list for each system with CloudStack packages. This means all management servers, and any hosts that have the KVM agent (no changes should be necessary for hosts that are running VMware or Xen.)

Edit your /etc/apt/sources.list.d/cloudstack.list file on any systems that have CloudStack packages installed to points to version

This file should have one line, which contains:

Setup the public key for the above repository:

wget -qO - http://download.cloudstack.org/release.asc | sudo apt-key add -

  1. Now update your apt package list:

    $ sudo apt-get update

  2. Now that you have the repository configured, it's time to upgrade the cloudstack-management package.

    $ sudo apt-get upgrade cloudstack-management

  3. If you use CloudStack usage server

    $ sudo apt-get upgrade cloudstack-usage

CentOS/RHEL

If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to hypervisors section upg_hyp_413.

Note

Community Packages: This section assumes you're using the community supplied packages for CloudStack. If you've created your own packages and yum repository, substitute your own URL for the ones used in these examples.

The first order of business will be to change the yum repository for each system with CloudStack packages. This means all management servers, and any hosts that have the KVM agent (no changes should be necessary for hosts that are running VMware or Xen.)

Change your /etc/yum.repos.d/cloudstack.repo file on any systems that have CloudStack packages installed to points to version .

This file should have content similar to the following:

[apache-cloudstack] name=Apache CloudStack baseurl=http://download.cloudstack.org/centos/$releasever// enabled=1 gpgcheck=0

Setup the GPG public key if you wish to enable gpgcheck=1:

  1. Now that you have the repository configured, it's time to upgrade the cloudstack-management.

    $ sudo yum upgrade cloudstack-management

  2. If you use CloudStack usage server

    $ sudo yum upgrade cloudstack-usage

Upgrade Hypervisors

Hypervisor: XenServer

No additional steps are required for XenServer Hypervisor for this upgrade.

Hypervisor: VMware

Warning

For VMware hypervisor, CloudStack management server packages must be built using "noredist". Refer to building-noredist.

No additional steps are requried for the VMware Hypervisor for this upgrade.

Hypervisor: KVM

KVM on Ubuntu

(KVM only) Additional steps are required for each KVM host. These steps will not affect running guests in the cloud. These steps are required only for clouds using KVM as hosts and only on the KVM hosts.

  1. Configure the APT repo <apt-repo413> as detailed above.

  2. Stop the running agent.

    $ sudo service cloudstack-agent stop

  3. Update the agent software.

    $ sudo apt-get upgrade cloudstack-agent

  4. Start the agent.

    $ sudo service cloudstack-agent start

KVM on CentOS/RHEL

For KVM hosts, upgrade the cloudstack-agent package

  1. Configure the rpm-repo413 as detailed above.

    $ sudo yum install -y epel-release $ sudo yum install -y python36-libvirt $ sudo yum upgrade cloudstack-agent

  2. Restart the agent:

    $ sudo service cloudstack-agent stop $ sudo service cloudstack-agent start

Restart management services

  1. Now it's time to start the management server

    $ sudo service cloudstack-management start

  2. If you use it, start the usage server

    $ sudo service cloudstack-usage start