-
Notifications
You must be signed in to change notification settings - Fork 21
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
Document current HA model (Epic) #361
Comments
Is there an idea/expectation when to allocate this activity in the context of LH integration? |
Yes, @giubacc this is planned for Milestone 4 of the Experimental Schedule, which is our v0.22.0 milestone. |
@giubacc will be doing some initial research into what we can get out of the underlying system, and its limitations, before we evaluate what are our options to move this forward. |
- add research/ha/RATIONALE.md Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
regular-localhost-incremental-fill-5k regular_localhost_load_fio_64_write regular_localhost_zeroload_400_800Kdb regular_localhost_zeroload_emptydb segfault_localhost_zeroload_emptydb Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
what still needs to be done:
other? |
- scale_deployment_0_1-k3s3nodes-zeroload-emptydb - s3wl-putobj-100ms-clusterip - s3wl-putobj-100ms-ingress Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
- add research/ha/RATIONALE.md Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
regular-localhost-incremental-fill-5k regular_localhost_load_fio_64_write regular_localhost_zeroload_400_800Kdb regular_localhost_zeroload_emptydb segfault_localhost_zeroload_emptydb Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
- scale_deployment_0_1-k3s3nodes-zeroload-emptydb - s3wl-putobj-100ms-clusterip - s3wl-putobj-100ms-ingress Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
@giubacc if there are pending tasks in this Epic (which I'm sure there are, at least with regard to documentation), please add them as tasks to this issue. |
Related to: https://github.com/aquarist-labs/s3gw/issues/361 Signed-off-by: Giuseppe Baccini <[email protected]>
There is a on-going task (medik8s research) regarding the HA, I think we will have to wait until the definitive path for HA will be set, I'd keep this opened because we will have to write something in the documentation at some point, but now we still don't know exactly what |
@giubacc please file an issue for the documentation, and whatever you think may be needed to track the effort, and add it to this epic. |
What needs to be done
Document the high-availability guarantees of s3gw on top of Longhorn.
Why it needs to be done
Users of storage solutions expect to understand the HA model of their solutions to gauge whether it's an appropriate choice for their workloads.
This is a first step in identifying what s3gw has as-is. What's the reasonable/best thing we can do today?
Once we have that, we should have follow ups on how to improve it (based on user/PM requirements) to enable further use cases. We should, once we have this documented, also consider if we can test/validate these claims.
Acceptance Criteria
Blog post, possibly part of the project's official documentation.
This could initially be implemented similarly to Longhorn or Rancher Telemetry. Perhaps there is an opportunity for code sharing.
Tasks
The text was updated successfully, but these errors were encountered: