Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

Juju

Juju is an open source orchestration engine for software operators that enables the deployment, integration and lifecycle management of applications at any scale, on any infrastructure using charms.

This charm is an operator - business logic encapsulated in reusable software packages that automate every aspect of an application’s life. Charms are shared via CharmHub.

See also:

This page aims to provide some context on some of the inner workings of Juju that affect this charm.

Summary


Breaking changes between Juju 2.9.x and 3.x

As this charm documentation is written for Juju 3.x, users of 2.9.x will encounter noteworthy changes when following the instructions. This section explains those changes.

Breaking changes have been introduced in the Juju client between versions 2.9.x and 3.x. These are caused by the renaming and re-purposing of several commands - functionality and command options remain unchanged.

In the context of this guide, the pertinent changes are shown here:

2.9.x 3.x
add-relation integrate
relate integrate
run exec
run-action --wait run

See the Juju 3.0 release notes for the comprehensive list of changes.

The response is to therefore substitute the documented command with the equivalent 2.9.x command. For example:

Juju 3.x:

juju integrate mysql-k8s:database mysql-test-app

juju run mysql-k8s/leader get-password 

Juju 2.9.x:

juju relate mysql-k8s:database mysql-test-app

juju run-action --wait mysql-k8s/leader get-password

This section is based on the OpenStack guide.

Juju upgrades

Newly released charm revisions might require a new Juju version. This is usually because the new revision requires new Juju features, e.g. Juju secrets.

Information about Juju requirements will be clearly indicated in the charm’s release notes and in the repository’s metadata.yaml file.

When upgrading your database charm with juju refresh, Juju checks that its version is compatible with the target revision. If not, it stops the upgrade and prevents further changes to keep the installation safe.

~$ juju refresh mysql

Added charm-hub charm "mysql", revision 42 in channel 8.0/stable, to the model
ERROR Charm feature requirements cannot be met:
    - charm requires all of the following:
      - charm requires feature "juju" (version >= 3.1.5) but model currently supports version 3.1.4

You must then upgrade to the required Juju version before proceeding with the charm upgrade.

Last updated 5 months ago. Help improve this document in the forum.