I second this. In a typical virtualization environment, you have a server with several real network cards. These are typically combined in a bond device. On top of these you have bridges, and on top of those you have vlans. Virtual servers may exist in different networks, so you need this stacked solution of vlan, bridge, bond, nics.
Also bonding should work with different lacp modes such as those available in CISCO switches, or others. It is totally unclear from the documentation how to do this. There should be tested, failsave documentation for the /etc/network/interfaces file. Right now it is nearly impossible to get exactly right. And even when I get it to work, the network does Ideally you should be able to do all this from within a GUI, but at the very least the documentation for the interfaces file should radically improve. I hope Canonical realizes this is CRITICAL for a virtualization server product. A single gigabit line is not enough, so you MUST be able to configure bonding, bridging and vlans easily. As long as this does not work reliably, you can just forget about ubuntu server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881380 Title: bonding and vlan configuration options should really be available during ubuntu-server installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/881380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
