Skip to content

Conversation

@hemna
Copy link
Contributor

@hemna hemna commented Oct 29, 2025

this separates the cinder db online migration out from the migrate-job in case the data migrations take a long time, it doesn't prevent the api from restarting.

@sapcc-bot
Copy link
Contributor

Failed to validate the helm chart. Details. Readme.

this separates the cinder db online migration out from the
migrate-job in case the data migrations take a long time, it
doesn't prevent the api from restarting.
@hemna hemna force-pushed the cinder-db-online-migration-job branch from adef138 to 32156ab Compare October 29, 2025 14:40
@sapcc-bot
Copy link
Contributor

Failed to validate the helm chart. Details. Readme.

# since this name changes with every image change, removal and creation of
# this Job happens on nearly every deployment. Check the helm-chart changes
# to see if this needs more review.
name: {{ tuple . "db-online-migrate" | include "job_name" }}
Copy link
Contributor

Choose a reason for hiding this comment

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

Nova has this, Cinder doesn't.

openstack/nova/templates/_helpers.tpl:{{- define "job_name" }}

You'd probably have to rewrite cinder.migration_job_name for that.

Comment on lines +46 to +53
- name: cinder-etc
mountPath: /etc/cinder/api-paste.ini
subPath: api-paste.ini
readOnly: true
- name: cinder-etc
mountPath: /etc/cinder/policy.yaml
subPath: policy.yaml
readOnly: true
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think the migration-job should need either of these configs. They are api-specific.

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.

4 participants