Number of CNs and IR nodes should be configurable #7
Labels
No Label
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-dev-env#7
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Original issue: https://github.com/nspcc-dev/neofs-dev-env/issues/73
In different development and testing scenarios we require different number of IR/CN/other nodes. It should be configurable and different setup scripts should be used depending on those settings.
We already do similar think for neo-bench https://github.com/nspcc-dev/neo-bench
Example config template for neo-go:
https://github.com/nspcc-dev/neo-bench/blob/master/.docker/ir/go.protocol.template.yml
I think we may adopt similar approach here.