Event Cycle

When charming with the reactive framework, it’s possible to use developer-created states and boolean logic to run code when the states represent something meaningful to your deployment, such as when a database is connected, and when it is available, or when the primary workload becomes available for use. These are additional “events” that are abstracted from the hook event cycle outlined later in this page.

Handling reactive states

Many states can be performed during a single hook execution, as these abstracted states are run through a dispatcher, and ordering is not guaranteed. All state based events, like hook events, are required to be idempotent.

Let’s assume we have an install hook that looks similar to the following:

def install():
    # Do work to install the Apache web server...

We can continue to “react” to this event with an event subscription using the “@when” decorator. Note: that we are still in the Install hook context.

def do_something():
   # Install a webapp on top of the Apache Web server...

Handling relations with reactive states

When building a charm using layers -- implementing an interface layer -- these layers set states for the code to react to. This allows the charm author to focus solely on the states rather than the traditional method of putting all the code in the relationship hook sequence.

Relation states by example

In the vanilla layer.yaml file, we include “interface:mysql". This relates directly to the “database” relation defined in metadata.yaml; with this inclusion in layer.yaml, your charm will pick up the mysql interface layer from the layers webservice. The vanilla code can then react to the “database.connected” state and/or the “database.available” state.

This is illustrated by the following block which handles messaging to the user that the code is waiting for MySQL to send the connection details:

def waiting_mysql(mysql):
    status_set('waiting', 'Waiting for MySQL')

Note: It is important to note that the instructions for this particular interface are only applicable to this particular interface. Interfaces are unique to the author’s implementation, and any states set will vary from interface to interface. These states are documented in the interface layer repository README.md file.

Hook event cycle

Taking a broad look at multiple applications, there are several common events that each application goes through: install, configure, start, upgrade, and stop. To model applications, Juju drives these events that a charm can respond to with executable files called hooks. Juju executes the specific hook for the appropriate event.

There are several core lifecycle hooks that can be implemented by any charm:

For every relation defined by a charm, an additional four "relation hooks" can be implemented, named after the charm relation:

For every storage pool created a charm can implement two additional storage hooks:

There is more information on Charm Hooks in the Reference section of the Juju documentation.

Deployment Events by example

When deploying a charm, there is a guaranteed set lifecycle events that every charm will run - this is the basic series of hooks executed in the initial deployment cycle.

  1. install
  2. leader-elected (leader-settings-changed respectively)
  3. config-changed
  4. start
  5. update-status

Configuration Events by example

Other event chains can be initiated by Juju commands or actions in the GUI. These chains follow a few different paths depending on which event is triggered against the unit. For example, if we were to change the configuration of the vanilla charm, Juju would then call the config-changed hook, and nothing else.

  1. config-changed

Relation Events by example

When a relation is added from the vanilla charm to a database charm, the first event is database-relation-joined the two units know about each other and the code should prepare communication between the two. After the join a database-relation-changed state is set, the two units have peer to peer communication.

  1. database-relation-joined
  2. database-relation-changed

When the relation is removed, either by removing the relation or deleting the related node, two additional events will be triggered. The first event [name]-relation-departed is run while there is still a relationship with the other unit, to allow operations such as backup, or to allow graceful terminations of connections. The second event [name]-relation-broken is run when the relation no longer exists, where a charm might remove a system from a configuration and restart a process if necessary.

  1. database-relation-departed
  2. database-relation-broken

Leader Events by example

Software with many distributed nodes may require a notion of a “leader”, or a single node as the organizer of the other nodes. Such applications often have “leader elections” or come to a “quorum” to determine the leader among themselves. The leadership hooks allow Juju to determine one leader and creates an event if the leader is ever destroyed or otherwise displaced.

  1. leader-elected
  2. leader-settings-changed

There is more detailed information about Charm Leadership in the Juju documentation.

Storage Events by example

Many applications require access to storage resources. Juju has events related to storage for the charm to respond to. There are two events related to storage, so the charm can react storage is attached and when it is detached.

  1. [name]-storage-attached
  2. [name]-storage-detached

There is more information about the storage feature in the Juju documentation.

While these concepts are important to understand how Juju works, creating a charm in the reactive framework reduces the need to interact directly with the event model. We will preserve the install and config-changed hook(s) in most layers. The relation hooks are generated when using an interface layer, during the charm build process. The remainder of actions taken will be directed with artificial states, set by the layer's author.

© 2018 Canonical Ltd. Ubuntu and Canonical are registered trademarks of Canonical Ltd.