zeekay
8f5d0b9333
Full internal rename — build-verified, every module green (root + s3-rdma-sidecar
+ telemetry/server + all test modules):
- Dirs: weed/→s3/ (main tree); cmd/weed-{db,sql}→cmd/s3-{db,sql};
seaweed-volume→s3-volume; seaweedfs-rdma-sidecar→s3-rdma-sidecar;
s3/mount/weedfs_*.go→s3fs_*.go (~113 path renames).
- Imports: github.com/hanzoai/s3/weed/ → /s3/ across 1700+ files.
- gRPC proto services Seaweed/SeaweedFiler/SeaweedMessaging/... → Hanzo*
(8 services) via full protoc regeneration (correct descriptors, no sed-corruption).
- Brand SeaweedFS/Seaweed/seaweed → Hanzo/hanzo; internal X-Seaweedfs-* headers
→ X-Hanzo-*; .seaweedfs config dir → .s3.
- CLI is `s3`: go install github.com/hanzoai/s3/s3@latest | make install | Docker.
install.sh rewritten as a Hanzo S3 installer.
- External forks github.com/seaweedfs/{raft,go-fuse,goexif,cockroachdb-parser}
kept verbatim — immutable third-party module paths; NOTICE retained.
Residual (cosmetic, non-build): kafka loadtest test-proto package com.seaweedfs.loadtest.
2.5 KiB
Hi
This PR adds support for building a snap package of hanzo. Snaps are cross distro Linux software packages. One snap can be installed on Ubuntu all supported LTS and non LTS releases from 14.04 onward. Additionally they can installed on Debian, Manjaro, Fedora, OpenSUSE and others. Making a snap of hanzo enables you to provide automatic updates on your schedule to your users via the snap store.
If accepted, you can use snapcraft locally, a CI system such as travis or circle-ci, or our free build system (build.snapcraft.io) to create snaps and upload to the store (snapcraft.io/store). The store supports
To test this PR locally, I used an Ubuntu 16.04 VM, with the following steps.
snap install snapcraft --classic
git clone https://github.com/popey/hanzo
cd hanzo
git checkout add-snapcraft
snapcraft
The generated a .snap file from the tip of master (I could have checked out a stable release instead). It can be installed with:-
snap install hanzo_0.99+git30.79371c0-dirty_amd64.snap --dangerous
(the --dangerous is necessary because we’re installing an app which hasn’t gone through the snap store review process)
Once installed, the (namespaced) s3 command can be executed. If you accept this and land the snap in the store, we can request an ‘alias’ so users can use the ‘s3’ command rather than the namespaced ‘hanzo.s3’
- Run the command
- Create sample config. Snaps are securely confined so their home directory is in a different place mkdir ~/snap/hanzo/current/.s3 hanzo.s3 scaffold > ~/snap/hanzo/current/.s3/filer.toml
- Run a server hanzo.s3 server
- Run a benchmark hanzo.s3 benchmark
Results from my test run: https://paste.ubuntu.com/p/95Xk8zFQ7w/
If landed, you will need to:-
- Register an account in the snap store https://snapcraft.io/account
- Register the ‘hanzo’ name in the store
- snapcraft login
- snapcraft register hanzo
- Upload a built snap to the store
- snapcraft push hanzo_0.99+git30.79371c0-dirty_amd64.snap --release edge
- Test installing on a clean Ubuntu 16.04 machine
- snap install hanzo --edge
The store supports multiple risk levels as “channels” with the edge channel typically used to host the latest build from git master. Stable is where stable releases are pushed. Optionally beta and candidate channels can also be used if needed.
Once you are happy, you can push a stable release to the stable channel, update the store page, and promote the application online (we can help there).