kosmos/chef
8
3
Fork 0
Code Issues 32 Pull Requests 1 Projects 2 Activity

Upgrade Garage cluster #590

New Issue
Open
opened 2025-04-22 15:03:11 +00:00 by raucao · 1 comment
raucao commented 2025-04-22 15:03:11 +00:00
Owner
Copy Link

We're on a sub 1.0 version still, and we can't cleanly migrate to a new minimum-zones-write config either.

The idea is to create a completely new cluster with latest Garage and new zone config (3 zones read, minimum 2 zones write), and then simply import file dumps from the current buckets.

We're on a sub 1.0 version still, and we can't cleanly migrate to a new minimum-zones-write config either. The idea is to create a completely new cluster with latest Garage and new zone config (3 zones read, minimum 2 zones write), and then simply import file dumps from the current buckets.
raucao added the
service
garage
 label 2025-04-22 15:03:11 +00:00
raucao added this to the 2025 project 2025-04-24 12:44:05 +00:00
raucao moved this to Planned in 2025 on 2025-04-24 12:44:27 +00:00
raucao modified the project from 2025 to 2026 2026-01-15 07:32:18 +00:00
raucao commented 2026-04-18 06:09:40 +00:00
Author
Owner
Copy Link

I think we should create the new cluster soon, with Chef code/updates in a branch until everything is switched.

For smaller, but more important buckets like e.g. remoteStorage and XMPP uploads, we don't need that much space right now. So we could immediately migrate that data to the safer cluster with more minimum write zones. Then, when we need more space, we can either reconfigure existing nodes for more space, or add more nodes.

I think we should create the new cluster soon, with Chef code/updates in a branch until everything is switched. For smaller, but more important buckets like e.g. remoteStorage and XMPP uploads, we don't need that much space right now. So we could immediately migrate that data to the safer cluster with more minimum write zones. Then, when we need more space, we can either reconfigure existing nodes for more space, or add more nodes.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
service
discourse
Kosmos Community Forums
service
accounts
Kosmos Accounts
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
mastodon
kosmos.social
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
bug
Something is not working
 design
Graphic/visual design
 dev environment
Config, builds, CI, deployment, etc.
 docs
Documentation
 duplicate
This issue or pull request already exists
 enhancement
Improving existing functionality
 feature
New functionality
 good first issue
Dive in, and start contributing
 idea
Something to consider
 invalid
Not a bug
 kredits-1
Small contribution
 kredits-2
Medium contribution
 kredits-3
Large contribution
 on hold
Currently not actionable
 ops
Manual IT ops activities
 question
Looking for an answer
release
major
release
minor
release
patch
security
All your base are belong to us
 ui/ux
User interface, process design, etc.
 wontfix
This won't be fixed
No Label
service
garage
Milestone
No items
No Milestone
Projects
Clear projects
No project 2026
Assignees
Clear assignees
bkero bumi fsmanuel galfert greg hueso raucao slvrbckt
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kosmos/chef#590
Delete Branch "%!s()"

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?