mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-01 00:48:00 +00:00
zeekay
b61441f7d7
A fork of Rancher's local-path-provisioner at v0.0.36. The behaviour is unchanged and deliberately so — a directory on the node a pod lands on is the right thing for a disk. What changes is identity. The provisioner answers to hanzo.ai/volume rather than rancher.io/local-path. That is not branding: two provisioners sharing one name race for the same claims, and a stock k3s carries the upstream one, so a cluster running both would settle our storage by chance. Data lives at /var/lib/hanzo/volume, so reading a Hanzo cluster does not mean learning another vendor's directory. Apache-2.0 as published, unaltered, with Rancher's attribution in NOTICE. The README says what this is not: durability. A volume here dies with its node. That is hanzoai/replicate's question, one layer up, and keeping the two apart is what lets the disk stay this simple.
23 lines
699 B
Go
23 lines
699 B
Go
// Package cli provides a minimal framework for creating and organizing command line
|
|
// Go applications. cli is designed to be easy to understand and write, the most simple
|
|
// cli application can be written as follows:
|
|
// func main() {
|
|
// cli.NewApp().Run(os.Args)
|
|
// }
|
|
//
|
|
// Of course this application does not do much, so let's make this an actual application:
|
|
// func main() {
|
|
// app := cli.NewApp()
|
|
// app.Name = "greet"
|
|
// app.Usage = "say a greeting"
|
|
// app.Action = func(c *cli.Context) error {
|
|
// println("Greetings")
|
|
// return nil
|
|
// }
|
|
//
|
|
// app.Run(os.Args)
|
|
// }
|
|
package cli
|
|
|
|
//go:generate go run flag-gen/main.go flag-gen/assets_vfsdata.go
|