On 01/30/2013 08:03 AM, Jaroslav Reznik wrote: > = Features/NetworkManagerBridging = > https://fedoraproject.org/wiki/Features/NetworkManagerBridging > > Feature owner(s): Pavel Šimerda <psimerda at redhat.com>, Dan Williams <dcbw > at redhat dot com> > > NetworkManager should be able to configure bridge interfaces with commonly used > options and recognize their existing configuration on startup without > disrupting their operation. Is the scope of this feature intended to cover both traditional (brctl) bridges and Open vSwitch (i.e. ovs-vsctl, ...) bridges? Both types of bridging are supported by plugins for openstack-quantum, and it would be great to make sure this feature works nicely with quantum. -Bob > > == Detailed description == > A bridge connects two or more physical or virtual network interfaces to allow > network traffic to flow between the two interfaces at a low level. Bridging is > commonly used to connect Virtual Machines to the outside world; a bridge > interface is created, to which a physical interface (typically ethernet) is > assigned as a slave, and a virtual interface (typically TAP) is created and > also assigned to the bridge as a slave, and then given to the Virtual Machine. > Thus traffic from one or more VMs can be combined and sent out of the machine > via the physical interface. > > This setup is currently done either manually using ifcfg files and ifup/ifdown, > or by a tool like libvirt/netcf. NetworkManager should be able to configure > bridge interfaces and their slaves with the same functionality as provided by > libvirt, and should recognize and not disrupt existing bridge connections when > it starts up. > _______________________________________________ > devel-announce mailing list > devel-announce@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel-announce > -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
