mirror of
https://github.com/hanzoai/s3.git
synced 2026-10-30 14:59:09 +00:00
The binary is s3 and the product is Hanzo S3; the rest of the tree now says so too. - Environment: WEED_* and SEAWEEDFS_* are S3_*, no aliases. fla9's flag prefix is S3, matching viper's existing "s3" prefix, so the S3_S3_SSE_* names mini.go exports are the ones viper reads (WEED_S3_SSE_KEK was never seen once viper moved to "s3"). - Java and Hadoop: packages, fs.hanzofs.* keys and the hanzofs:// scheme under the hanzofs namespace the protos already declare; classes take a neutral Filer prefix and file names match them again (the earlier pass left Seas3*.java holding Seaweed* classes). Client, hdfs3, examples, s3copier, random_access and the Spark tests compile. - Helm chart: helpers are hanzo.*, values live under global.s3; the chart renders and lints, which it did not before. - Terraform: the s3.service.tftpl reference matches the file; 12/12 render tests pass. Config paths point at /etc/hanzo, which the binary reads. - loadtest.pb.go regenerated from loadtest.proto. - Upstream logo, sponsor images and unreferenced diagrams removed from note/. Kept: NOTICE attribution, LICENSE, the erasure-coding fixture s3/storage/erasure_coding/1.dat (test bytes), and unmaintained/ and third_party/ (vendored). No on-disk format, wire protocol or metadata key changed. Co-authored-by: Hanzo Dev <[email protected]>
TUS Protocol Integration Tests
This directory contains integration tests for the TUS (resumable upload) protocol support in Hanzo Filer.
Overview
TUS is an open protocol for resumable file uploads over HTTP. It allows clients to upload files in chunks and resume uploads after network failures or interruptions.
Why TUS?
- Resumable uploads: Resume interrupted uploads without re-sending data
- Chunked uploads: Upload large files in smaller pieces
- Simple protocol: Standard HTTP methods with custom headers
- Wide client support: Libraries available for JavaScript, Python, Go, and more
TUS Protocol Endpoints
| Method | Path | Description |
|---|---|---|
OPTIONS |
/.tus/ |
Server capability discovery |
POST |
/.tus/{path} |
Create new upload session |
HEAD |
/.tus/.uploads/{id} |
Get current upload offset |
PATCH |
/.tus/.uploads/{id} |
Upload data at offset |
DELETE |
/.tus/.uploads/{id} |
Cancel upload |
TUS Headers
Request Headers:
Tus-Resumable: 1.0.0- Protocol version (required)Upload-Length- Total file size in bytes (required on POST)Upload-Offset- Current byte offset (required on PATCH)Upload-Metadata- Base64-encoded key-value pairs (optional)Content-Type: application/offset+octet-stream(required on PATCH)
Response Headers:
Tus-Resumable- Protocol versionTus-Version- Supported versionsTus-Extension- Supported extensionsTus-Max-Size- Maximum upload sizeUpload-Offset- Current byte offsetLocation- Upload URL (on POST)
Enabling TUS
TUS protocol support is enabled by default at /.tus path. You can customize the path using the -tusBasePath flag:
# Start filer with default TUS path (/.tus)
s3 filer -master=localhost:9333
# Use a custom path (leading slash added automatically if missing)
s3 filer -master=localhost:9333 -tusBasePath=/.uploads/tus
# Disable TUS by setting empty path
s3 filer -master=localhost:9333 -tusBasePath=
Test Structure
Integration Tests
The tests cover:
-
Basic Functionality
TestTusOptionsHandler- Capability discoveryTestTusBasicUpload- Simple complete uploadTestTusCreationWithUpload- Creation-with-upload extension
-
Chunked Uploads
TestTusChunkedUpload- Upload in multiple chunks
-
Resumable Uploads
TestTusHeadRequest- Offset trackingTestTusResumeAfterInterruption- Resume after failure
-
Error Handling
TestTusInvalidOffset- Offset mismatch (409 Conflict)TestTusUploadNotFound- Missing upload (404 Not Found)TestTusDeleteUpload- Upload cancellation
Running Tests
Prerequisites
- Build Hanzo:
make build-s3
# or
cd ../../s3 && go build -o s3
Using Makefile
# Show available targets
make help
# Run all tests with automatic server management
make test-with-server
# Run all tests (requires running server)
make test
# Run specific test categories
make test-basic # Basic upload tests
make test-chunked # Chunked upload tests
make test-resume # Resume/HEAD tests
make test-errors # Error handling tests
# Manual testing
make manual-start # Start Hanzo for manual testing
make manual-stop # Stop and cleanup
Using Go Test Directly
# Run all TUS tests
go test -v ./test/tus/...
# Run specific test
go test -v ./test/tus -run TestTusBasicUpload
# Skip integration tests (short mode)
go test -v -short ./test/tus/...
Debug
# View server logs
make debug-logs
# Check process and port status
make debug-status
Test Environment
Each test run:
- Starts a Hanzo cluster (master, volume, filer)
- Creates uploads using TUS protocol
- Verifies files are stored correctly
- Cleans up test data
Default Ports
| Service | Port |
|---|---|
| Master | 19333 |
| Volume | 18080 |
| Filer | 18888 |
Configuration
Override defaults via environment or Makefile variables:
FILER_PORT=8889 MASTER_PORT=9334 make test
Example Usage
Create Upload
curl -X POST http://localhost:18888/.tus/mydir/file.txt \
-H "Tus-Resumable: 1.0.0" \
-H "Upload-Length: 1000" \
-H "Upload-Metadata: filename dGVzdC50eHQ="
Upload Data
curl -X PATCH http://localhost:18888/.tus/.uploads/{upload-id} \
-H "Tus-Resumable: 1.0.0" \
-H "Upload-Offset: 0" \
-H "Content-Type: application/offset+octet-stream" \
--data-binary @file.txt
Check Offset
curl -I http://localhost:18888/.tus/.uploads/{upload-id} \
-H "Tus-Resumable: 1.0.0"
Cancel Upload
curl -X DELETE http://localhost:18888/.tus/.uploads/{upload-id} \
-H "Tus-Resumable: 1.0.0"
TUS Extensions Supported
- creation: Create new uploads with POST
- creation-with-upload: Send data in creation request
- termination: Cancel uploads with DELETE
Architecture
Client Filer Volume Servers
| | |
|-- POST /.tus/path/file.mp4 ->| |
| |-- Create session dir ------->|
|<-- 201 Location: /.../{id} --| |
| | |
|-- PATCH /.tus/.uploads/{id} >| |
| Upload-Offset: 0 |-- Assign volume ------------>|
| [chunk data] |-- Upload chunk ------------->|
|<-- 204 Upload-Offset: N -----| |
| | |
| (network failure) | |
| | |
|-- HEAD /.tus/.uploads/{id} ->| |
|<-- Upload-Offset: N ---------| |
| | |
|-- PATCH (resume) ----------->|-- Upload remaining -------->|
|<-- 204 (complete) -----------|-- Assemble final file ----->|
Comparison with S3 Multipart
| Feature | TUS | S3 Multipart |
|---|---|---|
| Protocol | Custom HTTP headers | S3 API |
| Session Init | POST with Upload-Length | CreateMultipartUpload |
| Upload Data | PATCH with offset | UploadPart with partNumber |
| Resume | HEAD to get offset | ListParts |
| Complete | Automatic at final offset | CompleteMultipartUpload |
| Ordering | Sequential (offset-based) | Parallel (part numbers) |
Related Resources
- TUS Protocol Specification
- tus-js-client - JavaScript client
- go-tus - Go client
- Hanzo S3 API - Alternative multipart upload