Skip to content

Conversation

zhmarvi
Copy link
Contributor

@zhmarvi zhmarvi commented Sep 4, 2025

Adding the rating service for Chargeback, recently added to openstack-helm. tested the deployment and api calls work. At this time there is no Skyline module for cloudkitty but there is a horizon dashboard module that should work.

Copy link
Contributor

@cloudnull cloudnull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

functionally, this looks fine, however we need the boilerplate github actions added to validate the helm, kustomize, and potentially add it to the smoke tests

@rackerchris
Copy link
Contributor

This PR pulls in multiple changes not related to the pr. please rebase.

Copy link
Contributor

@rackerchris rackerchris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensure that rabbitmq resources are managed by helm so the "helm.sh/resource-policy" can be enforced properly.

metadata:
name: cloudkitty
namespace: openstack
annotations:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are missing the managed by helm-label here. similiar to this:
labels:
app.kubernetes.io/managed-by: "Helm"
annotations:
helm.sh/resource-policy: keep
meta.helm.sh/release-name: "cloudkitty"
meta.helm.sh/release-namespace: "openstack"

metadata:
name: cloudkitty-vhost
namespace: openstack
annotations:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above here.

metadata:
name: cloudkitty-queue
namespace: openstack
annotations:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above here.

metadata:
name: cloudkitty-permission
namespace: openstack
annotations:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above here.

@rackerchris
Copy link
Contributor

One more change, please take a look at an install script from another service to see the format and make sure to add the helm version of your servce in the helm-chart-versions.yaml.

SERVICE_CONFIG_DIR="/etc/genestack/helm-configs/cloudkitty"
BASE_OVERRIDES="/opt/genestack/base-helm-configs/cloudkitty/cloudkitty-helm-overrides.yaml"

HELM_CMD="helm upgrade --install cloudkitty openstack-helm/cloudkitty --version 2025.1.1+64dfa3fe4 \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The helm version has been moved to genestack/helm-chart-versions.yaml. Please update this install script to conform with the standard (the other services).

@rackerchris
Copy link
Contributor

and finally, the upstream helm chart starts only one cloudkitty process.
https://opendev.org/openstack/openstack-helm/src/branch/master/cloudkitty/values.yaml#L563
Is this the intended number or processes to run by default?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants