nspcc-dev/neofs-dev-env

Fork 0

mirror of https://github.com/nspcc-dev/neofs-dev-env.git synced 2026-03-01 04:29:00 +00:00

Number of CNs and IR nodes should be configurable #18

New issue

Closed

opened 2025-12-28 18:08:07 +00:00 by sami · 8 comments

sami commented

2025-12-28 18:08:07 +00:00

Owner

Originally created by @realloc on GitHub (May 7, 2021).

Originally assigned to: @End-rey on GitHub.

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.

Originally created by @realloc on GitHub (May 7, 2021). Originally assigned to: @End-rey on GitHub. 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.

sami

2025-12-28 18:08:07 +00:00

closed this issue
added the
U4

S2

I2

feature
labels

sami commented

2025-12-28 18:08:08 +00:00

Author

Owner

@alexvanin commented on GitHub (May 7, 2021):

Configurations with different number of IR/CN nodes require different blockchain dumps and different neo-go configuration files for each case. I am not sure it is possible to do without in-place chain dump / config generators, that may be hard to integrate with neofs-dev-env repo.

@alexvanin commented on GitHub (May 7, 2021): Configurations with different number of IR/CN nodes require different blockchain dumps and different neo-go configuration files for each case. I am not sure it is possible to do without in-place chain dump / config generators, that may be hard to integrate with neofs-dev-env repo.

sami commented

2025-12-28 18:08:08 +00:00

Author

Owner

@roman-khimov commented on GitHub (May 7, 2021):

It's not that difficult to generate a small chain dump (and I don't think you have a lot to put into it), neo-bench does that for example.

@roman-khimov commented on GitHub (May 7, 2021): It's not that difficult to generate a small chain dump (and I don't think you have a lot to put into it), neo-bench does that for example.

sami commented

2025-12-28 18:08:08 +00:00

Author

Owner

@realloc commented on GitHub (May 7, 2021):

In the most simple case this can be implemented as additional separate services, like chain-single and ir-single. Depending on the most popular configurations, they may be disabled or enabled by default. Chain dump urls could be pre-set in those services.

@realloc commented on GitHub (May 7, 2021): In the most simple case this can be implemented as additional separate services, like `chain-single` and `ir-single`. Depending on the most popular configurations, they may be disabled or enabled by default. Chain dump urls could be pre-set in those services.

sami commented

2025-12-28 18:08:08 +00:00

Author

Owner

@alexvanin commented on GitHub (May 13, 2021):

Let's start with polishing and publishing our chain generation tools first.

@alexvanin commented on GitHub (May 13, 2021): Let's start with polishing and publishing our chain generation tools first.

sami commented

2025-12-28 18:08:08 +00:00

Author

Owner

@aprasolova commented on GitHub (Jun 10, 2021):

As I understood from the discussion, the task is about creating exact neofs-dev-env configurations with predefined number of nodes and corresponding blockchain dumps. If it is so, I only need to know, how many nodes must be in these configurations.
@realloc @alexvanin ?

@aprasolova commented on GitHub (Jun 10, 2021): As I understood from the discussion, the task is about creating exact neofs-dev-env configurations with predefined number of nodes and corresponding blockchain dumps. If it is so, I only need to know, how many nodes must be in these configurations. @realloc @alexvanin ?

sami commented

2025-12-28 18:08:08 +00:00

Author

Owner

@alexvanin commented on GitHub (Jun 11, 2021):

As I understood from the discussion, the task is about creating exact neofs-dev-env configurations with predefined number of nodes and corresponding blockchain dumps. If it is so, I only need to know, how many nodes must be in these configurations.
@realloc @alexvanin ?

I think we want to target one and seven alphabet node configurations. First for debug and latter to model real network setup. However I wonder how we gonna do it. It requires different side chain dumps and we wanted to have some sort of side chain dump generator right in neofs-dev-env, if I understood correctly.

Can you elaborate your thoughts on how this should be done?

@alexvanin commented on GitHub (Jun 11, 2021): > As I understood from the discussion, the task is about creating exact neofs-dev-env configurations with predefined number of nodes and corresponding blockchain dumps. If it is so, I only need to know, how many nodes must be in these configurations. > @realloc @alexvanin ? I think we want to target **one** and **seven** alphabet node configurations. First for debug and latter to model real network setup. However I wonder how we gonna do it. It requires different side chain dumps and we wanted to have some sort of side chain dump generator right in neofs-dev-env, if I understood correctly. Can you elaborate your thoughts on how this should be done?

sami commented

2025-12-28 18:08:08 +00:00

Author

Owner

@realloc commented on GitHub (Aug 29, 2022):

Related: #208

@realloc commented on GitHub (Aug 29, 2022): Related: #208

sami commented

2025-12-28 18:08:08 +00:00

Author

Owner

@cthulhu-rider commented on GitHub (Dec 9, 2024):

CN∈IR now nspcc-dev/neofs-node@35def8436a/config/example/ir.yaml (L23)

@cthulhu-rider commented on GitHub (Dec 9, 2024): CN∈IR now https://github.com/nspcc-dev/neofs-node/blob/35def8436a7316db4511845b6ac2020c2ed6f313/config/example/ir.yaml#L23