20.08 (Draft version in progress)


The 20.08 OpenStack Charms project release includes updates for the following charms. Additional charm support status information is published in the OpenStack Charm Guide which ultimately supersedes Release Notes contents.

Always use the latest stable charm revision before proceeding with topological changes, application migrations, workload upgrades, series upgrades, or bug reports.

Other supporting charms (Stable)

These charms have stable releases with ongoing maintenance and testing. They are classified differently because the payload of each is not technically an OpenStack project.

Tech-preview charms (Beta)

These charms do not have stable releases, even though they may technically have “stable/yy.mm” branches. Regardless of any maintenance and testing that these charms may receive, some work (major bugs, payload packaging issues, project issues, general QA) is still required before the charms are ready for production use (promoted to Stable).

Alpha charms (Edge)

This classification of charms includes those which may be a proof-of-concept, a test fixture, or one which is in active development. They are not intended to be used in production. Supportability, upgradability, testability may be lacking, either from a charm perspective, or from the workload package perspective.

Maintenance-mode charms

These charms are in maintenance mode, meaning that new features and new releases are not actively being added or tested with them. Generally, these were produced for a demo, PoC, or as an example.

  • None at this time.

Removed charms


New charm features

With each new feature, there is a corresponding example bundle in the form of a test bundle, and/or a OpenStack Charms Deployment Guide section which details the use of the feature. For example test bundles, see the src/tests/bundles directory within the relevant charm repository.

Charm cinder-ceph now requires ‘ceph-access’ relation to Charm nova-compute

In order to ensure a functional nova-compute application, the ‘ceph-access’ relation is now required between the cinder-ceph charm and the nova-compute charm when cinder-ceph is related to the cinder charm. Otherwise, the charm will go into the blocked state.

This is due to this change:

Without a relation to at least one nova-compute application a cinder-ceph backend will not be functional as the libvirt secrets will not have been created to allow access to the ceph cluster from libvirt/qemu.

Require relation to nova-compute application

This probably won’t affect most existing, deployed, clouds, but may affect test bundles that now won’t complete deployment.

To add the relation:

juju add-relation nova-compute:ceph-access cinder-ceph:ceph-access

All bundles that use cinder-ceph should be checked and the relation added.

New charms

Preview charm features

Upgrading charms

Always use the latest stable charm revision before proceeding with topological changes, charm application migrations, workload upgrades, series upgrades, or bug reports.

Please ensure that the keystone charm is upgraded first.

To upgrade an existing deployment to the latest charm version simply use the upgrade-charm command. For example:

juju upgrade-charm keystone

Charm upgrades and OpenStack upgrades are functionally different. Charm upgrades ensure that the deployment has the latest charm revision, containing the latest charm fixes and features, whereas OpenStack upgrades influence the software package versions of OpenStack itself.

A charm upgrade does not trigger an OpenStack upgrade. An OpenStack upgrade is a separate process. However, an OpenStack upgrade does require the latest charm revision. Please refer to OpenStack upgrades in the OpenStack Charms Deployment Guide for more details.

Deprecation notices

Removed features

Known issues

Glance Simplestreams Sync

When deploying the glance-simplestreams-sync charm on Bionic a more recent version of the simplestreams package must be installed by configuring a PPA:

juju config glance-simplestreams-sync source=ppa:simplestreams-dev/trunk

See bug LP #1790904 for details.

Designate and Vault at Ocata and earlier

The designate charm for OpenStack releases Pike and earlier does not yet support SSL via Vault and the certificates relation. See bug LP #1839019.

Current versions of OpenStack with Vault and the certificates relation are supported by the Designate charm.

Restart Nova services after adding certificates relation

A race condition exists with the use of the ‘certificates’ relation. When SSL certificates are issued Nova services may attempt to talk to the placement API over HTTP while the API has already changed to HTTPS. See bug LP #1826382.

To mitigate against this, restart the nova-compute and nova-scheduler services once certificates have been issued:

juju run --application nova-compute "systemctl restart nova-compute"
juju run --application nova-cloud-controller "systemctl restart nova-scheduler"

TrilioVault Data Mover charm upgrade

For deployments using prior versions of the trilio-data-mover charm (as provided by Trilio) the relation between the trilio-data-mover charm and rabbitmq-server must be removed and re-added to ensure that specific access for the data-mover service is provided for RabbitMQ.

juju remove-relation trilio-data-mover rabbitmq-server
juju add-relation trilio-data-mover rabbitmq-server

TrilioVault package upgrades

Changing the value of the ‘triliovault-pkg-source’ option does not currently trigger a package upgrade although the apt sources for the unit are updated.

Packages can be manually upgraded after changing this option - for example:

juju run --application trilio-dm-api "sudo apt -y dist-upgrade"

See bug LP #1879904 for more details.

Designate upgrades to Train

When upgrading Designate to OpenStack Train, there is an encoding issue between the designate-producer and memcached that causes the designate-producer to crash. See bug LP #1828534. This can be resolved by restarting the memcached service.

juju run --application=memcached 'sudo systemctl restart memcached'

Octavia and neutron-openvswitch in LXD

The octavia charm requires a neutron-openvswitch subordinate which means that if it runs in a container, the openvswitch kernel module must be loaded before the container starts. Module loading is done by LXD based on the profile applied by Juju and taken from the neutron-openvswitch charm. However, due to LP #1876849 in Juju, there is no guarantee that the profile will be applied before neutron-openvswitch execution starts in a container.

The issue is more likely to happen on disaggregated deployments where octavia units run in LXD containers on machines that do not have any units of neutron-openvswitch running on bare metal.

In order to work around the error an operator needs to make sure the openswitch module is loaded on the host and then restart the openvswitch-switch.service service inside the LXD container where the respective neutron-openvswitch unit is present. After that the unit error can be resolved.

Ceph RBD Mirror and Ceph Octopus

Due to an unresolved permission issue the ceph-rbd-mirror charm will stay in a blocked state after configuring mirroring for pools when connected to a Ceph Octopus cluster. See bug LP #1879749 for details.

Minimum Juju version for deploying Octavia

Juju 2.7 and above should be used for deployments with the octavia charm since it has dependencies that require the LANG environment variable to be set during package installation. Juju versions prior to 2.7 do not set the LANG variable in hook executions which leads to the default python decoder being set to ASCII - this results in decoding issues when one of the dependent package’s setup.py script gets executed and reads a source file containing UTF-8 code units. As a result, the following error can be seen in a hook error:

UnicodeDecodeError: 'ascii' codec can't decode byte 0xc8 in position 129: ordinal not in range(128)

See bug LP #1879184 for more information.

This issue affects existing Juju 2.6 environments as well if a charm upgrade is performed. It will be addressed by fixing GH #173.

Bugs fixed

The 20.08 OpenStack Charms release includes XX bug fixes. Refer to the 20.08 milestone in Launchpad for the list of resolved bugs.

Next release info

Please see the OpenStack Charm Guide for current information.