Zombienet Configuration Breakdown

Running the Zombienet requires a configuration file. This configuration file is downloaded during the third step of Linux/MacOS or can be copied from the first step of Running the parachain.

Similarities

The two files share most of the contents, so we'll start by covering their similarities. For more details refer to the zombienet documentation:

relaychain

NameDescription
chainThe relaychain name
default_argsThe default arguments passed to the command
default_commandThe default command to run the relaychain
nodesList of tables defining the nodes to run

nodes

NameDescription
nameThe node name
validatorWhether the node is a validator or not

parachains

A list of tables defining multiple parachains, in our case, we only care for our own parachain.

NameDescription
cumulus_basedWhether to use cumulus based generation
idThe parachain ID, we're using 1000 as a placeholder for now
collatorsList of tables defining the collators

collators

NameDescription
argsThe arguments passed to the command
commandThe command to run the collator
nameThe collator name
validatorWhether the collator is also a validator

Differences

The difference between them lies in the usage of container configurations:

NameDescription
image_pull_policyDefines when zombienet should pull an image; read more about it in the Kubernetes documentation
imageDefines which image to pull
ws_port/rpc_portDepending on the type of configuration (Native or Kubernetes), this variable sets the port for the collator RPC service