Add support for static storage container name #107
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using a storage backend such as ceph block, the
container
corresponds to aceph 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.