943c9fd988
data_platform_libs.v0.database_requires was deprecated on January 4th, 2023 and has not received updates since then. This change migrates to data_platform_libs.v0.data_interfaces which the preferred way to interact with MySQL. Most notable changes: - User/password in a secret - Keystone test 'test_on_peer_data_changed_with_fernet_keys_and_fernet_secret_different' is no longer mocking secrets to make sure it's using database secrets. Change-Id: Ia1908c0828689458c6ff3fa8d9640c8debfc0a73
placement-k8s
Description
placement-k8s is an operator to manage the OpenStack Placement service on a Kubernetes based environment.
Usage
Deployment
placement-k8s is deployed using below command:
juju deploy placement-k8s placement --trust
Now connect the placement operator to an existing database and keystone identity operators.
juju relate mysql:database placement:database
juju relate keystone:identity-service placement:identity-service
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 placement. If the charm is not
deployed then see file actions.yaml.
Relations
placement-k8s requires the following relations:
database: To connect to the database
identity-service: To register endpoints 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/placement-api:2023.2 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.