Make Garage more operator friendly #69
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#69
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The aim of this issue is to make Garage's development more open and more transparent by clearly recording our early thinking.
Currently, Garage is a bit rough around the edges for operators.
First, I would start with some concrete propositions to make it more operator friendly:
--ca-cert
,--client-cert
and--client-key
to be able to operate garage without requiring to define an alias. I propose/etc/garage/{garage-ca.crt,garage.crt,garage.key}
, the Dockerfile should reflect this changegarage status
that would indicate the health of the cluster. The value could be OK (green), Node missing (orange), Restoring data (orange), Data unavailable (red). We could maybe add colors to node in the following and suggest an action to do (put the node back online, make it join the cluster, rebuild, etc.)For now, the only prospective feature I think of is:
These things are proposals, feel free to discuss them including why they could be bad ideas ^^. Also once a feature starts to be well defined, it might be better to create an independent issue to track it. See this issue as a place for idea incubation around operator friendliness of Garage.
Closing as this issue is too generic and too old.