Skip to content

feat: support multiple-network deployments#152

Open
KatyaRyazantseva wants to merge 2 commits intoblockblaz:mainfrom
KatyaRyazantseva:network-label
Open

feat: support multiple-network deployments#152
KatyaRyazantseva wants to merge 2 commits intoblockblaz:mainfrom
KatyaRyazantseva:network-label

Conversation

@KatyaRyazantseva
Copy link
Copy Markdown
Contributor

This PR provides the following updates and fixes:

  • Support multiple-network and multiple nodes per server ansible deployments with separate network configs per run.
  • Fix --validatorConfig flag and NETWORK_DIR absolute path resolution.
  • Support external network directories outside the repo.
  • Add client_type and network labels to Prometheus metrics for per-network and per-client filtering in Grafana.

Copy link
Copy Markdown
Contributor

@ch4r10t33r ch4r10t33r left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't there a possibility of validator-config file changing between runs? Should we add some validation or checks to ensure, the rsync doesn't produce incorrect copies on the server?

node_id: '{{ node_name }}'
instance: '{{ ansible_host }}'
network: '{{ network_name }}'
client_type: '{{ node.name.split("_")[0] }}'
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should always ensure that client names have just one "_" in them. Maybe add this to readme and integration.md?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants