mirror of
https://github.com/hanzoai/volume.git
synced 2026-11-02 12:11:53 +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.
43 lines
657 B
Go
43 lines
657 B
Go
// Code generated by cmd/cgo -godefs; DO NOT EDIT.
|
|
// cgo -godefs defs_openbsd.go
|
|
|
|
package ipv6
|
|
|
|
const (
|
|
sizeofSockaddrInet6 = 0x1c
|
|
sizeofInet6Pktinfo = 0x14
|
|
sizeofIPv6Mtuinfo = 0x20
|
|
|
|
sizeofIPv6Mreq = 0x14
|
|
|
|
sizeofICMPv6Filter = 0x20
|
|
)
|
|
|
|
type sockaddrInet6 struct {
|
|
Len uint8
|
|
Family uint8
|
|
Port uint16
|
|
Flowinfo uint32
|
|
Addr [16]byte /* in6_addr */
|
|
Scope_id uint32
|
|
}
|
|
|
|
type inet6Pktinfo struct {
|
|
Addr [16]byte /* in6_addr */
|
|
Ifindex uint32
|
|
}
|
|
|
|
type ipv6Mtuinfo struct {
|
|
Addr sockaddrInet6
|
|
Mtu uint32
|
|
}
|
|
|
|
type ipv6Mreq struct {
|
|
Multiaddr [16]byte /* in6_addr */
|
|
Interface uint32
|
|
}
|
|
|
|
type icmpv6Filter struct {
|
|
Filt [8]uint32
|
|
}
|