Openstack Mitaka

Automatic cloud image refresh

The Openstack Mitaka cloud deployed by the Autopilot includes two amd64 images by default: Ubuntu 14.04 LTS ("trusty") and Ubuntu 16.04 LTS ("xenial"). These images will be refreshed daily, so if new releases are available, they will be downloaded and made available in Openstack's Glance.

Upgrade notes

Landscape 16.06 supports Ubuntu 16.04 LTS ("xenial") and Ubuntu 14.04 LTS ("trusty"). It can only be upgraded from Landscape 16.03.

You can upgrade a Landscape 16.03 running on Ubuntu 14.04 LTS ("trusty") all the way up to Landscape 16.06 running on Ubuntu 16.04 LTS ("xenial").

Quickstart upgrade

If you used the landscape-server-quickstart package to install Landscape 16.03 then you can use this method to upgrade it.

When prompted, reply with N to any dpkg questions about configuration files so the existing files stay untouched. The quickstart package will make any needed modifications to your configuration files automatically.

Non-quickstart upgrade

Follow these steps to perform a non-quickstart upgrade, that is, you did not use the landscape-server-quickstart package when installing Landscape 16.03:

stop all landscape services on all machines that make up your non-quickstart deployment, except the database service: sudo lsctl stop

answer with N to any dpkg questions about Landscape configuration files

if you have UPGRADE_SCHEMA enabled in /etc/default/landscape-server, then the required schema upgrade will be performed as part of the package upgrade and all services will be running at the end. The upgrade is finished.

if UPGRADE_SCHEMA is disabled, then you will have failures when the services are restarted at the end of the upgrade. That's expected. You now have to perform the schema upgrade manually with this command:

sudo setup-landscape-server

After all these steps are completed, the Landscape services can be started:

sudo lsctl start

Charm upgrade

Starting with Landscape 15.10, juju deployed Landscape can be upgraded in place. If you have just one landscape server unit, please follow this procedure:

Also, you may want to keep this open in another window, to get an idea of when the system goes back to idle between each step:

juju status --format=tabular
# or
watch juju status --format=tabular

Ubuntu release upgrade

You can take advantage of the fact that Landscape 16.06 supports both Ubuntu 14.04 LTS ("trusty") and Ubuntu 16.04 LTS ("xenial") and upgrade your Landscape deployment from "trusty" to "xenial". This section details the upgrade procedure depending on how you deployed Landscape.

Release upgrade for quickstart deployments

Follow these steps in order:

Upgrade Landscape 16.03 to 16.06 while still on Ubuntu 14.04 LTS ("trusty") using the quickstart upgrade method.

If you get a warning about /etc/postgresql-common/createcluster.conf while configuring postgresql-common, select to keep the local version.

Drop the newly created 9.5 cluster:

sudo pg_dropcluster 9.5 main --stop

Upgrade the 9.3 cluster:

sudo pg_upgradecluster 9.3 main

Start Landscape services:

sudo lsctl start

Verify that Landscape is working correctly.

If you are happy with the upgrade results, the previous 9.3 cluster can be dropped:

sudo pg_dropcluster 9.3 main

Release upgrade for manual (non-quickstart) deployments

The release upgrade process for the manual non-quickstart deployment is a bit more complicated and needs to be done in steps. A summary is shown in the table below, in the order the steps should happen:

APP

DB

LDS

Ubuntu

Postgresql

Ubuntu

16.03 (1)

Trusty

9.3

Trusty

16.06 (2)

Trusty (3)

9.3

Trusty

16.06

Xenial (4)

9.3

Trusty (5)

16.06

Xenial

9.3 (7)

Xenial (6)

16.06

Xenial

9.5 (8)

Xenial

Upgrade the APP server first:

Upgrade Landscape 16.03 to 16.06 in the APP server, still on Ubuntu 14.04 LTS ("trusty"), following the steps outlined in the non-quickstart upgrade section.

If you get a warning about /etc/postgresql-common/createcluster.conf while configuring postgresql-common, select to keep the local version.

Drop the newly created 9.5 cluster:

sudo pg_dropcluster 9.5 main --stop

Upgrade the 9.3 cluster:

sudo pg_upgradecluster 9.3 main

Start the Landscape services:

sudo lsctl start

Verify that Landscape is working correctly.

If you are happy with the upgrade results, the previous 9.3 cluster can be dropped:

sudo pg_dropcluster 9.3 main

Release upgrade for juju deployments

Upgrading the Ubuntu release of servers within a juju deployment is not supported at this time.

Other changes of note

Storage devices referenced by IDs

Openstack Autopilot deployments will use disk IDs when referencing block devices for storage charms. This requires virtual machines to be configured to supply these IDs.

If using libvirt (or virt-manager) with KVM, for example, a simple way to accomplish this is to add a serial number to each disk:

Other virtualization technologies have similar concepts. Sometimes it's called a "disk UUID". Please consult the corresponding documentation.

Known issues

This section describes some relevant known issues that might affect your usage of Landscape 16.06.

Upgrading Landscape with existing clouds

Clouds deployed with a previous version of Landscape will remain working after Landscape is upgraded to 16.06, but add-hardware cannot be used until the cloud is redeployed with the upgraded Landscape.

package-search disabled after upgrade to xenial

If Landscape 16.06 on trusty is upgraded to xenial, the landscape-package-search service will be left disabled due to a bug in the transitioning from upstart to systemd. As a result, if the host where this service lives is rebooted, the service will not start on its own.