Propose a script to quickly spawn a cluster #14
No reviewers
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#14
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/cluster-example"
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?
Goal
Provide a no-brainer command line to start hacking on garage without having to reflect on how to deploy a local setup.
The script only requires standard GNU tools (bash, grep, cat, sleep).
Non-Goals
This script is not a generic wrapper to start or deploy a garage cluster (like bash scripts we often see in java projects. If you don't understand what I mean, go check Jitsi or Icescrum).
It is not a powerful development tool that you can dynamically tweak to set the right amount of verbosity, the right amount of nodes, etc.
If you have special needs, just use this script as a template and modify it locally to your needs.
Limitations
The script does not yet configure the nodes.
But I am not sure we want to do it yet: what do we do if two nodes are configured but not the last one.
I am note sure how I want to get node IDs as they are truncated in
garage status
.I think we could say it is out of scope, at least for this PR.