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>
gnocchi-k8s
Description
gnocchi-k8s is an operator to manage the gnocchi services gnocchi api, and gnocchi metricd on a Kubernetes based environment.
Usage
Deployment
gnocchi-k8s is deployed using below command:
juju deploy gnocchi-k8s gnocchi --trust
Now connect the gnocchi operator to existing database, keystone identity, and rabbitmq operators:
juju relate mysql:database gnocchi:database
juju relate keystone:identity-service gnocchi: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 gnocchi. If the charm is not
deployed then see file actions.yaml.
Relations
gnocchi-k8s requires the following relations:
database: To connect to MySQL
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 following images:
ghcr.io/canonical/gnocchi-consolidated:2025.1
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.