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.
19 lines
884 B
Go
19 lines
884 B
Go
// Package jsoniter implements encoding and decoding of JSON as defined in
|
|
// RFC 4627 and provides interfaces with identical syntax of standard lib encoding/json.
|
|
// Converting from encoding/json to jsoniter is no more than replacing the package with jsoniter
|
|
// and variable type declarations (if any).
|
|
// jsoniter interfaces gives 100% compatibility with code using standard lib.
|
|
//
|
|
// "JSON and Go"
|
|
// (https://golang.org/doc/articles/json_and_go.html)
|
|
// gives a description of how Marshal/Unmarshal operate
|
|
// between arbitrary or predefined json objects and bytes,
|
|
// and it applies to jsoniter.Marshal/Unmarshal as well.
|
|
//
|
|
// Besides, jsoniter.Iterator provides a different set of interfaces
|
|
// iterating given bytes/string/reader
|
|
// and yielding parsed elements one by one.
|
|
// This set of interfaces reads input as required and gives
|
|
// better performance.
|
|
package jsoniter
|