mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-30 14:55:30 +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.
40 lines
1.4 KiB
Go
40 lines
1.4 KiB
Go
// Copyright 2012 The Go Authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style
|
|
// license that can be found in the LICENSE file.
|
|
|
|
//go:build !aix && !darwin && !dragonfly && !freebsd && !linux && !netbsd && !openbsd && !solaris && !zos
|
|
|
|
package ipv4
|
|
|
|
import "net"
|
|
|
|
// ReadFrom reads a payload of the received IPv4 datagram, from the
|
|
// endpoint c, copying the payload into b. It returns the number of
|
|
// bytes copied into b, the control message cm and the source address
|
|
// src of the received datagram.
|
|
func (c *payloadHandler) ReadFrom(b []byte) (n int, cm *ControlMessage, src net.Addr, err error) {
|
|
if !c.ok() {
|
|
return 0, nil, nil, errInvalidConn
|
|
}
|
|
if n, src, err = c.PacketConn.ReadFrom(b); err != nil {
|
|
return 0, nil, nil, err
|
|
}
|
|
return
|
|
}
|
|
|
|
// WriteTo writes a payload of the IPv4 datagram, to the destination
|
|
// address dst through the endpoint c, copying the payload from b. It
|
|
// returns the number of bytes written. The control message cm allows
|
|
// the datagram path and the outgoing interface to be specified.
|
|
// Currently only Darwin and Linux support this. The cm may be nil if
|
|
// control of the outgoing datagram is not required.
|
|
func (c *payloadHandler) WriteTo(b []byte, cm *ControlMessage, dst net.Addr) (n int, err error) {
|
|
if !c.ok() {
|
|
return 0, errInvalidConn
|
|
}
|
|
if dst == nil {
|
|
return 0, errMissingAddress
|
|
}
|
|
return c.PacketConn.WriteTo(b, dst)
|
|
}
|