You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to write zombienet tests for the bridges project. Since a bridge connects 2 networks we would need the ability to start multiple networks as part of zndsl test.
If I understand correctly, right now a zndsl test definition supports only one network. I was wondering if it would be possible to add support for multiple networks.
If the proposal makes sense and if it's ok for you, I would be happy to implement this feature myself. I was thinking of the following very high-level approach:
Allowing multiple Network: network_def.json lines in the .zndsl file and building a vector of networks when parsing it instead of a single network.
I think we should assume that each network uses different node names. This would help preserve the current syntax and keep the code changes minimal.
In the orchestrator iterating through the vector of networks and starting each one.
I see that for the moment there is only one Client per zndsl run. We would probably need one per network. I'm not completely sure about this, but I guess there must be a solution.
The text was updated successfully, but these errors were encountered:
Hi @serban300, thanks for the feedback, open this issue and the draft PR :) 🙌 .
We will open this new feature as discussion with the team and get back to you asap. I like the idea of running multiple-networks what I wonder what is the best api/config for users take advantage of this.
We would like to write zombienet tests for the bridges project. Since a bridge connects 2 networks we would need the ability to start multiple networks as part of
zndsl
test.If I understand correctly, right now a
zndsl
test definition supports only one network. I was wondering if it would be possible to add support for multiple networks.If the proposal makes sense and if it's ok for you, I would be happy to implement this feature myself. I was thinking of the following very high-level approach:
Network: network_def.json
lines in the.zndsl
file and building a vector of networks when parsing it instead of a single network.Client
perzndsl
run. We would probably need one per network. I'm not completely sure about this, but I guess there must be a solution.The text was updated successfully, but these errors were encountered: