-
Notifications
You must be signed in to change notification settings - Fork 479
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
Epic: [Azure] production ready Azure blob storage support #5567
Comments
@arpad-m , does this replace https://github.com/neondatabase/cloud/issues/7204 ? |
@stepashka there is also #5562 which is soon to be closed. I think with that in combination with this issue, we can say https://github.com/neondatabase/cloud/issues/7204 is replaced. Sorry I've not seen it! |
Adds prototype-level support for [Azure blob storage](https://azure.microsoft.com/en-us/products/storage/blobs). Some corners were cut, see the TODOs and the followup issue #5567 for details. Steps to try it out: * Create a storage account with block blobs (this is a per-storage account setting). * Create a container inside that storage account. * Set the appropriate env vars: `AZURE_STORAGE_ACCOUNT, AZURE_STORAGE_ACCESS_KEY, REMOTE_STORAGE_AZURE_CONTAINER, REMOTE_STORAGE_AZURE_REGION` * Set the env var `ENABLE_REAL_AZURE_REMOTE_STORAGE=y` and run `cargo test -p remote_storage azure` Fixes #5562
* Update `azure-*` crates to 0.18 * Use new open ranges support added by upstream in Azure/azure-sdk-for-rust#1482 Part of #5567. Prior update PR: #6081
closing in favour of the follow-up in https://github.com/neondatabase/cloud/issues/12627 . The existing azure blob implementation is production-ready, the missing parts are in maintenance tooling outside of the main pageserver binary. |
PR #5546 has added a preview-level azure blob storage support but left some key areas in a state that could see improvements.
This epic tracks the follow-up work needed to make azure blob storage support production ready.
Tasks
The text was updated successfully, but these errors were encountered: