DNM: CloudKitty for fresh OpenSearch deployments #699
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This container tag brings in the fixes from this PR: stackhpc/cloudkitty#57 which allows CloudKitty with the elasticsearch backend to be used with fresh OpenSearch. i.e for new deployments (Habrok, AZ Moldnal, etc.) This PR should not be merged until we are happy with using the same patch for existing deployments after an ES->OS migration. (Or ideally, never at all if we want to integrate the proper opensearch v2 storage driver)
|
Is this still required/working? |
|
The proper solutions to this are making their way through upstream. IMO we should keep this around until that's fully merged and backported, just in case someone needs this in the meantime. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This container tag brings in the fixes from this PR: stackhpc/cloudkitty#57 which allows CloudKitty with the elasticsearch backend to be used with fresh OpenSearch. i.e for new deployments (Habrok, AZ Moldnal, etc.)
This PR should not be merged until we are happy with using the same patch for existing deployments after an ES->OS migration. (Or ideally, never at all if we want to integrate the proper opensearch v2 storage driver)