extern/zrepl
1
0
Fork 0
mirror of https://github.com/zrepl/zrepl.git synced 2024-11-22 00:13:52 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
stable
zrepl/go.mod

52 lines
2.1 KiB
Modula-2
Raw Permalink Normal View History

build: drop go Dep, switch to modules, support Go 1.13 bump enumer to v1.1.1 bump golangci-lint to v1.17.1 no `go mod tidy` because 1.13 and 1.12 seem to alter each other's output fixes #112
2019-09-03 14:45:18 +02:00
module github.com/zrepl/zrepl
go 1.12
require (
github.com/fatih/color v1.7.0
github.com/gdamore/tcell v1.2.0
implement new 'zrepl status' Primary goals: - Scrollable output ( fixes #245 ) - Sending job signals from status view - Filtering of output by filesystem Implementation: - original TUI framework: github.com/rivo/tview - but: tview is quasi-unmaintained, didn't support some features - => use fork https://gitlab.com/tslocum/cview - however, don't buy into either too much to avoid lock-in - instead: **port over the existing status UI drawing code and adjust it to produce strings instead of directly drawing into the termbox buffer** Co-authored-by: Calistoc <calistoc@protonmail.com> Co-authored-by: InsanePrawn <insane.prawny@gmail.com> fixes #245 fixes #220
2020-03-27 20:37:17 +01:00
github.com/gdamore/tcell/v2 v2.2.0
[#307] add package trace, integrate it with logging, and adopt it throughout zrepl package trace: - introduce the concept of tasks and spans, tracked as linked list within ctx - see package-level docs for an overview of the concepts - **main feature 1**: unique stack of task and span IDs - makes it easy to follow a series of log entries in concurrent code - **main feature 2**: ability to produce a chrome://tracing-compatible trace file - either via an env variable or a `zrepl pprof` subcommand - this is not a CPU profile, we already have go pprof for that - but it is very useful to visually inspect where the replication / snapshotter / pruner spends its time ( fixes #307 ) usage in package daemon/logging: - goal: every log entry should have a trace field with the ID stack from package trace - make `logging.GetLogger(ctx, Subsys)` the authoritative `logger.Logger` factory function - the context carries a linked list of injected fields which `logging.GetLogger` adds to the logger it returns - `logging.GetLogger` also uses package `trace` to get the task-and-span-stack and injects it into the returned logger's fields
2020-04-11 15:49:41 +02:00
github.com/gitchander/permutation v0.0.0-20181107151852-9e56b92e9909
build: go mods: split build deps into subgomod, bump prometheus to 1.2.1, tweaked go mod tidy tweaked go mod tidy: see comment in go.mod
2019-10-26 13:55:03 +02:00
github.com/go-logfmt/logfmt v0.4.0
replication: simplify parallel replication variables & expose them in config closes #140
2021-02-28 23:33:28 +01:00
github.com/go-playground/validator v9.31.0+incompatible
implement new 'zrepl status' Primary goals: - Scrollable output ( fixes #245 ) - Sending job signals from status view - Filtering of output by filesystem Implementation: - original TUI framework: github.com/rivo/tview - but: tview is quasi-unmaintained, didn't support some features - => use fork https://gitlab.com/tslocum/cview - however, don't buy into either too much to avoid lock-in - instead: **port over the existing status UI drawing code and adjust it to produce strings instead of directly drawing into the termbox buffer** Co-authored-by: Calistoc <calistoc@protonmail.com> Co-authored-by: InsanePrawn <insane.prawny@gmail.com> fixes #245 fixes #220
2020-03-27 20:37:17 +01:00
github.com/go-playground/validator/v10 v10.4.1
pre- and post-snapshot hooks * stack-based execution model, documented in documentation * circbuf for capturing hook output * built-in hooks for postgres and mysql * refactor docs, too much info on the jobs page, too difficult to discover snapshotting & hooks Co-authored-by: Ross Williams <ross@ross-williams.net> Co-authored-by: Christian Schwarz <me@cschwarz.com> fixes #74
2019-07-26 21:12:21 +02:00
github.com/go-sql-driver/mysql v1.4.1-0.20190907122137-b2c03bcae3d4
Update to protobuf v1.25 and grpc 1.35; bump CI to go1.12 From: github.com/golang/protobuf v1.3.2 google.golang.org/grpc v1.17.0 To: github.com/golang/protobuf v1.4.3 google.golang.org/grpc v1.35.0 google.golang.org/protobuf v1.25.0 About the two protobuf packages: https://developers.google.com/protocol-buffers/docs/reference/go/faq > Version v1.4.0 and higher of github.com/golang/protobuf wrap the new implementation and permit programs to adopt the new API incrementally. For example, the well-known types defined in github.com/golang/protobuf/ptypes are simply aliases of those defined in the newer module. Thus, google.golang.org/protobuf/types/known/emptypb and github.com/golang/protobuf/ptypes/empty may be used interchangeably. Notable Code Changes in zrepl: - generate protobufs now contain a mutex so we can't copy them by value anymore - grpc.WithDialer is deprecated => use grpc.WithContextDialer instead Go1.12 is now actually required by some of the dependencies.
2021-01-24 23:31:45 +01:00
github.com/golang/protobuf v1.4.3
github.com/google/uuid v1.1.2
build: drop go Dep, switch to modules, support Go 1.13 bump enumer to v1.1.1 bump golangci-lint to v1.17.1 no `go mod tidy` because 1.13 and 1.12 seem to alter each other's output fixes #112
2019-09-03 14:45:18 +02:00
github.com/jinzhu/copier v0.0.0-20170922082739-db4671f3a9b8
send/recv: job-level bandwidth limiting Sponsored-by: Prominic.NET, Inc. fixes #339
2021-07-09 16:30:44 +02:00
github.com/juju/ratelimit v1.0.1
run go mod tidy; go version go1.17.2 linux/amd64 Juding from the (now deleted) comments in go.mod, this might break 1.12 build. If it does, the CI will catch it as it currently build using 1.17 and 1.12. fixes https://github.com/zrepl/zrepl/issues/586
2022-05-07 21:58:17 +02:00
github.com/k0kubun/colorstring v0.0.0-20150214042306-9440f1994b88 // indirect
build: drop go Dep, switch to modules, support Go 1.13 bump enumer to v1.1.1 bump golangci-lint to v1.17.1 no `go mod tidy` because 1.13 and 1.12 seem to alter each other's output fixes #112
2019-09-03 14:45:18 +02:00
github.com/kr/pretty v0.1.0
replication: simplify parallel replication variables & expose them in config closes #140
2021-02-28 23:33:28 +01:00
github.com/leodido/go-urn v1.2.1 // indirect
pre- and post-snapshot hooks * stack-based execution model, documented in documentation * circbuf for capturing hook output * built-in hooks for postgres and mysql * refactor docs, too much info on the jobs page, too difficult to discover snapshotting & hooks Co-authored-by: Ross Williams <ross@ross-williams.net> Co-authored-by: Christian Schwarz <me@cschwarz.com> fixes #74
2019-07-26 21:12:21 +02:00
github.com/lib/pq v1.2.0
transports/ssh: bump go-netssh to improve dial errors from go-netssh changelog: dial: better error handling if ssh command exits with non-zero exit status SSHError.Error() relied on go-rwccmd behavior of returning io.EOF if the ssh binary exited with status code 0. We no longe ruse go-rwccmd => capture Stderr ourselves using zrepl's circlog (depending on zrepl is not pretty, but since this package is supposedly only used by zrepl ATM, this is fine) refs https://github.com/zrepl/zrepl/issues/237
2019-10-26 14:32:07 +02:00
github.com/mattn/go-colorable v0.1.4 // indirect
github.com/mattn/go-isatty v0.0.8
build: drop go Dep, switch to modules, support Go 1.13 bump enumer to v1.1.1 bump golangci-lint to v1.17.1 no `go mod tidy` because 1.13 and 1.12 seem to alter each other's output fixes #112
2019-09-03 14:45:18 +02:00
github.com/montanaflynn/stats v0.5.0
transports/ssh: bump go-netssh to improve dial errors from go-netssh changelog: dial: better error handling if ssh command exits with non-zero exit status SSHError.Error() relied on go-rwccmd behavior of returning io.EOF if the ssh binary exited with status code 0. We no longe ruse go-rwccmd => capture Stderr ourselves using zrepl's circlog (depending on zrepl is not pretty, but since this package is supposedly only used by zrepl ATM, this is fine) refs https://github.com/zrepl/zrepl/issues/237
2019-10-26 14:32:07 +02:00
github.com/onsi/ginkgo v1.10.2 // indirect
github.com/onsi/gomega v1.7.0 // indirect
build: go mods: split build deps into subgomod, bump prometheus to 1.2.1, tweaked go mod tidy tweaked go mod tidy: see comment in go.mod
2019-10-26 13:55:03 +02:00
github.com/pkg/errors v0.8.1
build: drop go Dep, switch to modules, support Go 1.13 bump enumer to v1.1.1 bump golangci-lint to v1.17.1 no `go mod tidy` because 1.13 and 1.12 seem to alter each other's output fixes #112
2019-09-03 14:45:18 +02:00
github.com/pkg/profile v1.2.1
transport/ssh: bump go-netssh version to fix ssh client process leaks fixes #322
2020-06-01 13:49:56 +02:00
github.com/problame/go-netssh v0.0.0-20200601114649-26439f9f0dc5
build: go mods: split build deps into subgomod, bump prometheus to 1.2.1, tweaked go mod tidy tweaked go mod tidy: see comment in go.mod
2019-10-26 13:55:03 +02:00
github.com/prometheus/client_golang v1.2.1
[#307] add package trace, integrate it with logging, and adopt it throughout zrepl package trace: - introduce the concept of tasks and spans, tracked as linked list within ctx - see package-level docs for an overview of the concepts - **main feature 1**: unique stack of task and span IDs - makes it easy to follow a series of log entries in concurrent code - **main feature 2**: ability to produce a chrome://tracing-compatible trace file - either via an env variable or a `zrepl pprof` subcommand - this is not a CPU profile, we already have go pprof for that - but it is very useful to visually inspect where the replication / snapshotter / pruner spends its time ( fixes #307 ) usage in package daemon/logging: - goal: every log entry should have a trace field with the ID stack from package trace - make `logging.GetLogger(ctx, Subsys)` the authoritative `logger.Logger` factory function - the context carries a linked list of injected fields which `logging.GetLogger` adds to the logger it returns - `logging.GetLogger` also uses package `trace` to get the task-and-span-stack and injects it into the returned logger's fields
2020-04-11 15:49:41 +02:00
github.com/prometheus/common v0.7.0
refactor snapper & support cron-based snapshotting fixes https://github.com/zrepl/zrepl/issues/554 refs https://github.com/zrepl/zrepl/discussions/547#discussioncomment-1936126
2022-04-12 01:26:41 +02:00
github.com/robfig/cron/v3 v3.0.1
run go mod tidy; go version go1.17.2 linux/amd64 Juding from the (now deleted) comments in go.mod, this might break 1.12 build. If it does, the CI will catch it as it currently build using 1.17 and 1.12. fixes https://github.com/zrepl/zrepl/issues/586
2022-05-07 21:58:17 +02:00
github.com/sergi/go-diff v1.0.1-0.20180205163309-da645544ed44 // indirect; go1.12 thinks it needs this
build: drop go Dep, switch to modules, support Go 1.13 bump enumer to v1.1.1 bump golangci-lint to v1.17.1 no `go mod tidy` because 1.13 and 1.12 seem to alter each other's output fixes #112
2019-09-03 14:45:18 +02:00
github.com/spf13/cobra v0.0.2
build: go.mod: bump go-netssh and drop go-critic replaces (go-netssh vendored util/circlog, so the circular dep is gone) fixes build failure reported by @poetterl-ric ``` make ZREPL_VERSION=0.2.1 zrepl-bin GO111MODULE=on go build -mod=readonly -ldflags "-X github.com/zrepl/zrepl/version.zreplVersion=0.2.1" -o "artifacts/zrepl-linux-amd64" go: github.com/problame/go-netssh@v0.0.0-20191026123024-f34099f4f6b1 requires github.com/zrepl/zrepl@v0.2.0 requires github.com/golangci/lint-1@v0.0.0-20181222135242-d2cdd8c08219: invalid version: git fetch --unshallow -f origin in /builddir/go/pkg/mod/cache/vcs/ca789ff49d608cda239a48837cfeea6e9dcdb2bce20051383910eef46b623a33: exit status 128: fatal: git fetch-pack: expected shallow list ```
2019-12-09 13:37:19 +01:00
github.com/spf13/pflag v1.0.5
replication: simplify parallel replication variables & expose them in config closes #140
2021-02-28 23:33:28 +01:00
github.com/stretchr/testify v1.6.1
[#307] add package trace, integrate it with logging, and adopt it throughout zrepl package trace: - introduce the concept of tasks and spans, tracked as linked list within ctx - see package-level docs for an overview of the concepts - **main feature 1**: unique stack of task and span IDs - makes it easy to follow a series of log entries in concurrent code - **main feature 2**: ability to produce a chrome://tracing-compatible trace file - either via an env variable or a `zrepl pprof` subcommand - this is not a CPU profile, we already have go pprof for that - but it is very useful to visually inspect where the replication / snapshotter / pruner spends its time ( fixes #307 ) usage in package daemon/logging: - goal: every log entry should have a trace field with the ID stack from package trace - make `logging.GetLogger(ctx, Subsys)` the authoritative `logger.Logger` factory function - the context carries a linked list of injected fields which `logging.GetLogger` adds to the logger it returns - `logging.GetLogger` also uses package `trace` to get the task-and-span-stack and injects it into the returned logger's fields
2020-04-11 15:49:41 +02:00
github.com/willf/bitset v1.1.10
build: drop go Dep, switch to modules, support Go 1.13 bump enumer to v1.1.1 bump golangci-lint to v1.17.1 no `go mod tidy` because 1.13 and 1.12 seem to alter each other's output fixes #112
2019-09-03 14:45:18 +02:00
github.com/yudai/gojsondiff v0.0.0-20170107030110-7b1b7adf999d
run go mod tidy; go version go1.17.2 linux/amd64 Juding from the (now deleted) comments in go.mod, this might break 1.12 build. If it does, the CI will catch it as it currently build using 1.17 and 1.12. fixes https://github.com/zrepl/zrepl/issues/586
2022-05-07 21:58:17 +02:00
github.com/yudai/golcs v0.0.0-20170316035057-ecda9a501e82 // indirect; go1.12 thinks it needs this
github.com/yudai/pp v2.0.1+incompatible // indirect
new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold - **Resumable Send & Recv Support** No knobs required, automatically used where supported. - **Hold-Protected Send & Recv** Automatic ZFS holds to ensure that we can always resume a replication step. - **Encrypted Send & Recv Support** for OpenZFS native encryption. Configurable at the job level, i.e., for all filesystems a job is responsible for. - **Receive-side hold on last received dataset** The counterpart to the replication cursor bookmark on the send-side. Ensures that incremental replication will always be possible between a sender and receiver. Design Doc ---------- `replication/design.md` doc describes how we use ZFS holds and bookmarks to ensure that a single replication step is always resumable. The replication algorithm described in the design doc introduces the notion of job IDs (please read the details on this design doc). We reuse the job names for job IDs and use `JobID` type to ensure that a job name can be embedded into hold tags, bookmark names, etc. This might BREAK CONFIG on upgrade. Protocol Version Bump --------------------- This commit makes backwards-incompatible changes to the replication/pdu protobufs. Thus, bump the version number used in the protocol handshake. Replication Cursor Format Change -------------------------------- The new replication cursor bookmark format is: `#zrepl_CURSOR_G_${this.GUID}_J_${jobid}` Including the GUID enables transaction-safe moving-forward of the cursor. Including the job id enables that multiple sending jobs can send the same filesystem without interfering. The `zrepl migrate replication-cursor:v1-v2` subcommand can be used to safely destroy old-format cursors once zrepl has created new-format cursors. Changes in This Commit ---------------------- - package zfs - infrastructure for holds - infrastructure for resume token decoding - implement a variant of OpenZFS's `entity_namecheck` and use it for validation in new code - ZFSSendArgs to specify a ZFS send operation - validation code protects against malicious resume tokens by checking that the token encodes the same send parameters that the send-side would use if no resume token were available (i.e. same filesystem, `fromguid`, `toguid`) - RecvOptions support for `recv -s` flag - convert a bunch of ZFS operations to be idempotent - achieved through more differentiated error message scraping / additional pre-/post-checks - package replication/pdu - add field for encryption to send request messages - add fields for resume handling to send & recv request messages - receive requests now contain `FilesystemVersion To` in addition to the filesystem into which the stream should be `recv`d into - can use `zfs recv $root_fs/$client_id/path/to/dataset@${To.Name}`, which enables additional validation after recv (i.e. whether `To.Guid` matched what we received in the stream) - used to set `last-received-hold` - package replication/logic - introduce `PlannerPolicy` struct, currently only used to configure whether encrypted sends should be requested from the sender - integrate encryption and resume token support into `Step` struct - package endpoint - move the concepts that endpoint builds on top of ZFS to a single file `endpoint/endpoint_zfs.go` - step-holds + step-bookmarks - last-received-hold - new replication cursor + old replication cursor compat code - adjust `endpoint/endpoint.go` handlers for - encryption - resumability - new replication cursor - last-received-hold - client subcommand `zrepl holds list`: list all holds and hold-like bookmarks that zrepl thinks belong to it - client subcommand `zrepl migrate replication-cursor:v1-v2`
2019-09-11 17:19:17 +02:00
github.com/zrepl/yaml-config v0.0.0-20191220194647-cbb6b0cf4bdd
implement new 'zrepl status' Primary goals: - Scrollable output ( fixes #245 ) - Sending job signals from status view - Filtering of output by filesystem Implementation: - original TUI framework: github.com/rivo/tview - but: tview is quasi-unmaintained, didn't support some features - => use fork https://gitlab.com/tslocum/cview - however, don't buy into either too much to avoid lock-in - instead: **port over the existing status UI drawing code and adjust it to produce strings instead of directly drawing into the termbox buffer** Co-authored-by: Calistoc <calistoc@protonmail.com> Co-authored-by: InsanePrawn <insane.prawny@gmail.com> fixes #245 fixes #220
2020-03-27 20:37:17 +01:00
gitlab.com/tslocum/cview v1.5.3
Update to protobuf v1.25 and grpc 1.35; bump CI to go1.12 From: github.com/golang/protobuf v1.3.2 google.golang.org/grpc v1.17.0 To: github.com/golang/protobuf v1.4.3 google.golang.org/grpc v1.35.0 google.golang.org/protobuf v1.25.0 About the two protobuf packages: https://developers.google.com/protocol-buffers/docs/reference/go/faq > Version v1.4.0 and higher of github.com/golang/protobuf wrap the new implementation and permit programs to adopt the new API incrementally. For example, the well-known types defined in github.com/golang/protobuf/ptypes are simply aliases of those defined in the newer module. Thus, google.golang.org/protobuf/types/known/emptypb and github.com/golang/protobuf/ptypes/empty may be used interchangeably. Notable Code Changes in zrepl: - generate protobufs now contain a mutex so we can't copy them by value anymore - grpc.WithDialer is deprecated => use grpc.WithContextDialer instead Go1.12 is now actually required by some of the dependencies.
2021-01-24 23:31:45 +01:00
golang.org/x/net v0.0.0-20210119194325-5f4716e94777
build: drop go Dep, switch to modules, support Go 1.13 bump enumer to v1.1.1 bump golangci-lint to v1.17.1 no `go mod tidy` because 1.13 and 1.12 seem to alter each other's output fixes #112
2019-09-03 14:45:18 +02:00
golang.org/x/sync v0.0.0-20190423024810-112230192c58
Update to protobuf v1.25 and grpc 1.35; bump CI to go1.12 From: github.com/golang/protobuf v1.3.2 google.golang.org/grpc v1.17.0 To: github.com/golang/protobuf v1.4.3 google.golang.org/grpc v1.35.0 google.golang.org/protobuf v1.25.0 About the two protobuf packages: https://developers.google.com/protocol-buffers/docs/reference/go/faq > Version v1.4.0 and higher of github.com/golang/protobuf wrap the new implementation and permit programs to adopt the new API incrementally. For example, the well-known types defined in github.com/golang/protobuf/ptypes are simply aliases of those defined in the newer module. Thus, google.golang.org/protobuf/types/known/emptypb and github.com/golang/protobuf/ptypes/empty may be used interchangeably. Notable Code Changes in zrepl: - generate protobufs now contain a mutex so we can't copy them by value anymore - grpc.WithDialer is deprecated => use grpc.WithContextDialer instead Go1.12 is now actually required by some of the dependencies.
2021-01-24 23:31:45 +01:00
golang.org/x/sys v0.0.0-20210124154548-22da62e12c0c
golang.org/x/tools v0.0.0-20190524140312-2c0ae7006135
google.golang.org/genproto v0.0.0-20210122163508-8081c04a3579 // indirect
google.golang.org/grpc v1.35.0
google.golang.org/protobuf v1.25.0
run go mod tidy; go version go1.17.2 linux/amd64 Juding from the (now deleted) comments in go.mod, this might break 1.12 build. If it does, the CI will catch it as it currently build using 1.17 and 1.12. fixes https://github.com/zrepl/zrepl/issues/586
2022-05-07 21:58:17 +02:00
gopkg.in/go-playground/assert.v1 v1.2.1 // indirect
build: drop go Dep, switch to modules, support Go 1.13 bump enumer to v1.1.1 bump golangci-lint to v1.17.1 no `go mod tidy` because 1.13 and 1.12 seem to alter each other's output fixes #112
2019-09-03 14:45:18 +02:00
)
Reference in New Issue Copy Permalink