mirror of
https://github.com/hanzoai/s3.git
synced 2026-11-03 03:07:41 +00:00
zooqueen
dd74d3e6d6
hanzoai/s3 was an AGPL-3.0 MinIO fork whose network-copyleft blocks embedding
and reselling as a managed service. Replace it wholesale with a fork of
SeaweedFS (github.com/seaweedfs/seaweedfs, Apache-2.0, Go) which ships a
built-in S3 gateway + Filer.
- License: AGPL-3.0 -> Apache-2.0 (upstream LICENSE kept verbatim, incl.
"Copyright 2025 Chris Lu"); NOTICE added crediting SeaweedFS. No AGPL/BUSL/
SSPL/GPL or enterprise ("ee") files remain.
- Module: go.mod path set to github.com/hanzoai/s3 with a self-replace
(replace github.com/seaweedfs/seaweedfs => ./) so the ~1800 internal Go files
keep their upstream import paths with zero churn. Internal identifiers and
import paths are intentionally NOT renamed.
- CLI rebrand: the binary is built as `s3` (was `weed`); root usage, per-command
help/usage/flag strings, shell autocomplete program name, and the product name
in CLI output now read "Hanzo S3" / `s3`. Users never see `weed`.
(e.g. `s3 server`, `s3 filer`, `s3 master`, `s3 volume`, `s3 s3`, `s3 mount`.)
- Build: `make` (or `go build -o s3 ./weed`) builds the `s3` binary green;
`cmd/weed-db` and `cmd/weed-sql` also build; `go vet ./weed/command/` clean.
- README/LLM.md rewritten for Hanzo S3; AGENTS.md/CLAUDE.md symlinks preserved.
- Dropped a 33MB prebuilt Mach-O `stress` binary upstream had committed; `.gitignore`
updated to ignore the `s3` build output.
56 lines
2.8 KiB
Go
56 lines
2.8 KiB
Go
package topology
|
|
|
|
import (
|
|
"github.com/seaweedfs/seaweedfs/weed/glog"
|
|
"github.com/seaweedfs/seaweedfs/weed/storage/erasure_coding"
|
|
)
|
|
|
|
// CalculateTaskStorageImpact calculates storage impact for different task types
|
|
func CalculateTaskStorageImpact(taskType TaskType, volumeSize int64) (sourceChange, targetChange StorageSlotChange) {
|
|
switch taskType {
|
|
case TaskTypeErasureCoding:
|
|
// EC task: distributes shards to MULTIPLE targets, source reserves with zero impact
|
|
// Source reserves capacity but with zero StorageSlotChange (no actual capacity consumption during planning)
|
|
// WARNING: EC has multiple targets! Use AddPendingTask with multiple destinations for proper multi-target handling
|
|
// This simplified function returns zero impact; real EC requires specialized multi-destination calculation
|
|
return StorageSlotChange{VolumeSlots: 0, ShardSlots: 0}, StorageSlotChange{VolumeSlots: 0, ShardSlots: 0}
|
|
|
|
case TaskTypeBalance:
|
|
// Balance task: moves volume from source to target
|
|
// Source loses 1 volume, target gains 1 volume
|
|
return StorageSlotChange{VolumeSlots: -1, ShardSlots: 0}, StorageSlotChange{VolumeSlots: 1, ShardSlots: 0}
|
|
|
|
case TaskTypeVacuum:
|
|
// Vacuum task: frees space by removing deleted entries, no slot change
|
|
return StorageSlotChange{VolumeSlots: 0, ShardSlots: 0}, StorageSlotChange{VolumeSlots: 0, ShardSlots: 0}
|
|
|
|
case TaskTypeReplication:
|
|
// Replication task: creates new replica on target
|
|
return StorageSlotChange{VolumeSlots: 0, ShardSlots: 0}, StorageSlotChange{VolumeSlots: 1, ShardSlots: 0}
|
|
|
|
case TaskTypeECBalance:
|
|
// EC balance task: moves individual shard from source to target
|
|
// Source frees 1 shard slot, target gains 1 shard slot
|
|
return StorageSlotChange{VolumeSlots: 0, ShardSlots: -1}, StorageSlotChange{VolumeSlots: 0, ShardSlots: 1}
|
|
|
|
default:
|
|
// Unknown task type, assume minimal impact
|
|
glog.Warningf("unhandled task type %s in CalculateTaskStorageImpact, assuming default impact", taskType)
|
|
return StorageSlotChange{VolumeSlots: 0, ShardSlots: 0}, StorageSlotChange{VolumeSlots: 1, ShardSlots: 0}
|
|
}
|
|
}
|
|
|
|
// CalculateECShardStorageImpact calculates storage impact for EC shards specifically
|
|
func CalculateECShardStorageImpact(shardCount int32, expectedShardSize int64) StorageSlotChange {
|
|
// EC shards are typically much smaller than full volumes
|
|
// Use shard-level tracking for granular capacity planning
|
|
return StorageSlotChange{VolumeSlots: 0, ShardSlots: shardCount}
|
|
}
|
|
|
|
// CalculateECShardCleanupImpact calculates storage impact for cleaning up existing EC shards
|
|
func CalculateECShardCleanupImpact(originalVolumeSize int64) StorageSlotChange {
|
|
// Cleaning up existing EC shards frees shard slots
|
|
// Use the actual EC configuration constants for accurate shard count
|
|
return StorageSlotChange{VolumeSlots: 0, ShardSlots: -int32(erasure_coding.TotalShardsCount)} // Negative = freed capacity
|
|
}
|