Page History

...

• Quality risks (test guidelines)
  • There is some question on how to handle MTU. See the chart included for the current solution.
  • No single system will scale to thousands of networks, regardless of technology. Therefore, we need to ensure that  CloudStack
    is properly tearing down networks that it no longer needs, and creating only networks necessary for the running instances
  • The current implementation relies on naming conventions to differentiate between a tagged interface that CloudStack should
    treat normally and an interface that CloudStack should treat as a physical interface. This works on KVM since linux provides
    two standard interface names for tagged vlan interfaces, and one is rarely used. However, there could be issue in the event
    that a customer is using the rare convention. We'd need to document this in the standard CloudStack network setup for KVM
    hosts.
• Supportability characteristics:
  • The implementation leverages CloudStack's existing network/bridging management code, so troubleshooting would be
    largely the same. The only caveat is in regards to the MTU as mentioned and covered later on.
• Configuration
  • To use the feature, one simply needs to create a new "vlan#" network device on each KVM host (being a tagged network interface on an existing physical network interface), then create a new physical network in CloudStack and attach the guest network traffic type as one would with any physical interface.
  • Jumbo frames should be enabled on any accompanying switch hardware that provides traffic between KVM hosts.

• deployment requirements (fresh install vs. upgrade) if any
  • Currently this will only work in the master branch, which has had a redesign of CloudStack bridge names for KVM. Previously the CloudStack created bridges were "cloudVirBr<vlan>", and now they're "br<physdev>-<vlan>" to avoid collisions when the same vlan is used on different physical devices.
  • Advanced networking is required
  • Ethernet switches that support 802.1q and variable MTU
  • To use the feature, one simply needs to create a new vlan# network device, then create a new physical network in CloudStack and attach the guest network traffic type as one would with any physical interface.
• interoperability and compatibility requirements:
  • OS
  • xenserver, hypervisros
  • storage, networks, otherKVM/Linux
• security
  • Security remains the same as with standard advanced networking and tagged networks. Anyone with privileges to listen on the unfiltered physical device can see all packets from all vlans.

...