Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for static storage container name #107

Merged
merged 2 commits into from
Mar 26, 2024
Merged

Add support for static storage container name #107

merged 2 commits into from
Mar 26, 2024

Conversation

Jonher937
Copy link
Contributor

When using a storage backend such as ceph block, the container corresponds to a ceph pool and is not managed by the user, but rather by the storage/Openstack operator.

In a S3 deployment it's fine for this to be dynamic as it's managed by the user, but in some cases (such as ceph block) the user needs to be able to override this container value.

With this change I was able to point to our backups pools, same pool as what Openstack Cinder Backup is using.

Depending on the backend used, we might need a static container name.
In a scenario of ceph-driver this corresponds to a ceph pool that holds the backups, which is not something the user can create themselves thru Openstack Cinder.
@Lirt
Copy link
Owner

Lirt commented Mar 25, 2024

Hello @Jonher937,

That sounds good. Give me some time to run quick test and reach back to you.

@Lirt
Copy link
Owner

Lirt commented Mar 25, 2024

Hey, I had to release a fix for CI and synced this branch.

If the CI runs fine I can merge the PR.

@Lirt Lirt merged commit a665700 into Lirt:master Mar 26, 2024
3 checks passed
@Jonher937
Copy link
Contributor Author

Thanks for the quick merge and maintaining this plugin ⭐

@Lirt
Copy link
Owner

Lirt commented Mar 26, 2024

Thank you for contribution.

New tag was published successfully.

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.

2 participants