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

feat(vm): setup network for a single VM and allow only one VM on a peer [BRND-60] #2352

Closed
wants to merge 10 commits into from

Conversation

kmd-fl
Copy link
Contributor

@kmd-fl kmd-fl commented Aug 21, 2024

Description

Setup networking for a single VM

Proposed Changes

  • Setup iptables rules when creating VM
  • Clear iptables rules when destroying VM
  • Allow to install only one VM
  • Modify Nox config

New configuration for VMs

[vm]
libvirt_uri = "qemu:///system"
[vm.network]
bridge_name = "br422442"
public_ip = "1.1.1.1"
vm_ip = "2.2.2.2"
host_ssh_port = 2222
vm_ssh_port = 22
port_range.start = 1000
port_range.end = 65535

Additional Notes

  1. Note that now THERE CAN BE ONLY ONE VM ON A PEER
  2. Couldn't test locally

What's with ports?
In Nox's config we're setting the following local ports:

tcp_port = 7771
websocket_port = 9991
http_port = 18080 # this port is used for an HTTP endpoints (prometheus metrics, etc)  
[chain_listener_config]
ccp_endpoint = "http://0.0.0.0:9389/"

Copy link

linear bot commented Aug 21, 2024

@kmd-fl kmd-fl added the e2e Run e2e workflow label Aug 21, 2024
@kmd-fl kmd-fl closed this Sep 2, 2024
@kmd-fl
Copy link
Contributor Author

kmd-fl commented Sep 2, 2024

Used the changes in another PR #2356

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

Successfully merging this pull request may close these issues.

2 participants