943c06f75a
This reverts commit ddd397bdc0.
Reason for revert: To avoid regression https://bugs.launchpad.net/snap-openstack/+bug/2126612
Additional change:
Install ops<3.x in test-requirements. This is a workaround and
will be fixed in subsequent PR to move test-requirements
to pyproject.toml so that charms as well as test environment
will use same tox version from uv.lock
Change-Id: I6f1e517e89de16908c876955a880c05581900366
Signed-off-by: Hemanth Nakkina <hemanth.nakkina@canonical.com>
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:2025.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.