-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add possibility to create a VM in bridged network mode #81
base: master
Are you sure you want to change the base?
Conversation
aa18381
to
e909673
Compare
16b4e7e
to
a5551b3
Compare
a5551b3
to
5869172
Compare
Thanks for the request, will review soon (hopefully). |
in our case we need to ensure to first start libvirtd and then nftables only than the firewall rules are present. if nftables is restarted the firewallrules will be dropped and the vm network is down it's only happening if libvirtd manages the network with this PR i can manage the network on my own and the rules are working now |
I have another case for bridged ndework mode.
And i want that start my domins (VMs) will be attachet to exist bridge, and works on host network
|
Co-authored-by: Kenyon Ralph <[email protected]>
@@ -1,7 +1,11 @@ | |||
<%- | Libvirt::Domain::Interface $iface, | |||
String $boot, | |||
| -%> | |||
<%- if $iface['bridge_network'] and $iface['bridge_network'] == true { -%> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think if $iface['bridge_network']
is enough.
@@ -22,7 +26,11 @@ | |||
</filterref> | |||
<%- } -%> | |||
<%- } -%> | |||
<%- if $iface['bridge_network'] and $iface['bridge_network'] == true { -%> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think if $iface['bridge_network'] is enough.
This is based on the idea of @sebastianrakel and @bastelfreak in pull request #81. Besides adding bridges this also adds additional network types. This deprecates the 'network' and 'portgroup' parameters in favor of the more flexible 'source' parameter in the network interface hash. The deprecated parameters will remain functional until next major release.
@sebastianrakel, @rayderua, @kenyon Just an additional hint, the bridge configuration is already possible without this merge request, just use one of $devices or $additionaldevices parameter with the following setting:
|
After problems with nftables and libvirtd, i talked with @bastelfreak and we talked about managing the network with systemd-networkd and bridge VMs directly to the systemd-networkd managed bridge.
It was not possible with the current state of this module, so i added an optional setting to create a bridged interface