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.
14 lines
375 B
Go
14 lines
375 B
Go
// This file is included to the build if any of the buildtags below
|
|
// are defined. Refer to README notes for more details.
|
|
|
|
//+build easyjson_nounsafe appengine
|
|
|
|
package jlexer
|
|
|
|
// bytesToStr creates a string normally from []byte
|
|
//
|
|
// Note that this method is roughly 1.5x slower than using the 'unsafe' method.
|
|
func bytesToStr(data []byte) string {
|
|
return string(data)
|
|
}
|