Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable spinning additional nodes #88

Open
norswap opened this issue Dec 23, 2023 · 1 comment
Open

Enable spinning additional nodes #88

norswap opened this issue Dec 23, 2023 · 1 comment
Labels

Comments

@norswap
Copy link
Member

norswap commented Dec 23, 2023

I think we should have additional configuration options for spinning additional "regular" nodes besides the sequencers.

These options should generally follow that of the sequencer, but be arrays instead. These arrays must be checked to have the same size. If they are empty, no additional node will be spun.

Each of these nodes also needs an execution engine, so a similar setup should exist for the engines. Here there is a question of whether to separate the execution engine that will be used by the sequencer, and those that will be used by the extra nodes. It seems not separating them out reduce code duplication.

Maybe that should be the case for nodes too? With an option to designate if a node (if any) should be the sequencer? Maybe simply a boolean flag that says whether the first item in the array should be the sequencer.

This blocks #68

@GrapeBaBa
Copy link
Contributor

@thinkAfCod Can you have a look?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants