93b6184174
All services needing to run DB Sync actually need the database to be populated before they start. Starting the services before the database lead to a lot of error logs misleading on root case. Modify configure_unit lifecycle to make db sync run first. Change-Id: I6da0483aba0b0547c84946d540b362c3e5a46d82 Signed-off-by: Guillaume Boutry <guillaume.boutry@canonical.com>
horizon-k8s
Description
horizon-k8s is an operator to manage the OpenStack dashboard service on a Kubernetes based environment.
Usage
Deployment
horizon-k8s is deployed using below command:
juju deploy horizon-k8s horizon --trust
Now connect the horizon operator to existing database and Keystone operators:
juju relate mysql:database horizon:database
juju relate keystone:identity-credentials horizon:identity-credentials
Configuration
This section covers common and/or important configuration options. See file
config.yaml for the full list of options, along with their descriptions and
default values. See the Juju documentation for details
on configuring applications.
Actions
This section covers Juju actions supported by the charm.
Actions allow specific operations to be performed on a per-unit basis. To
display action descriptions run juju actions horizon. If the charm is not
deployed then see file actions.yaml.
Relations
horizon-k8s requires the following relations:
database: To connect to MySQL
identity-credentials: To register cloud users in Keystone
ingress-internal: To expose service on underlying internal network
ingress-public: To expose service on public network
OCI Images
The charm by default uses ghcr.io/canonical/horizon:2024.1 image.
Contributing
Please see the Juju SDK docs for guidelines on enhancements to this charm following best practice guidelines, and CONTRIBUTING.md for developer guidance.
Bugs
Please report bugs on Launchpad.