Bug 1125117

Summary: bind vnet devices on different namespaces
Product: [Community] Virtualization Tools Reporter: gustavo panizzo <gfa> <gfa>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: crobinso, rbalakri
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-10 19:18:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description gustavo panizzo <gfa> 2014-07-31 05:10:04 UTC
Description of problem:

i would like if libvirt could bind vnet devices on different namespaces

i would like to segment different bridges (linux bridges) on namespaces. so i can, for example, put all vm connected to certain vlan, and the bridge where them connect, on a specific namespace.
i would ideally create as many namespaces as vlans.

that should be a configuration option, off by default. 

    <interface type='bridge'>
      <mac address='52:54:00:10:e9:e3'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>

i would set this bug as wishlist item.


Comment 1 gustavo panizzo <gfa> 2014-07-31 05:15:07 UTC
in this example, libvirt should look for bridge br0 on namespace named foo, admin should take care of create bridge and namespace. i any of them does not exist virsh start should fail

Comment 2 gustavo panizzo <gfa> 2014-07-31 05:15:40 UTC
s/i any/if any/

Comment 3 Cole Robinson 2016-04-10 19:18:23 UTC
I think this would be solved/integrated as part of a larger effort to containerize VMs, which is a broader topic for which an RFE already exists

*** This bug has been marked as a duplicate of bug 636146 ***