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

Remove bridge br0 from virtual machines #586

Open
eroussy opened this issue Aug 20, 2024 · 0 comments
Open

Remove bridge br0 from virtual machines #586

eroussy opened this issue Aug 20, 2024 · 0 comments
Labels
Debian enhancement New feature or request Yocto

Comments

@eroussy
Copy link
Member

eroussy commented Aug 20, 2024

Abstract
By default, a Linux bridge br0 is created on the administration interface in the hypervisor. This is useful to access all the VMs and the hypervisor with the same physical interface.
This bridge is also created inside the VM, but has no use. It should be removed.

Technical implementation
This bridge is applied in the cluster_setup_network playbook by the systemd_networkd role and the vars/network_vars.yml file. One simple solution could be to not apply this role inside the virtual machines, but in that case, the IP address of the VM will never be set.

In my opinion, we should provide a default network for the VM (just applying the admin IP address) and allow the user to modify it at will. This could be done, for example by creating two variables seapath_network and seapath_netdev that can be fully customized.
This is already the behavior if you use netplan. But the combined use of both netplan and systemd-netword is not clear now.

NB: This subject was already discussed in #565 (comment)

@eroussy eroussy added enhancement New feature or request Yocto Debian labels Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Debian enhancement New feature or request Yocto
Projects
None yet
Development

No branches or pull requests

1 participant