On KVM, Cloudstack relies on the underlying Linux OS to do the base
network configuration. Linux "port groups" are called "bonds" and
virtual switches are called "bridges". In the Linux OS you set up the
bond0 for all of the ports that will be part of the port group, with
whatever parameters you wish to have for how the port balancing will
work, and then the bond0.X / brX VLAN and bridge for the management
network (where X is the vlan number of the management network). Then
Cloudstack will handle the rest, creating additional VLANs and bridges
on the base bond as needed. For directions on how to set up the bond0.X
/ brX pairs, consult your Linux distribution's documentation. (It is
*radically* different between CentOS and Ubuntu, with CentOS using
multiple configuration files under /etc/sysconfig/network-scripts and
Ubuntu using /etc/netplan/* YAML files).
Basically, a "bond" in Linux takes the place of an actual physical
network port in all of the configuration for the networking. VLANs work
the same with a "bond" in Linux as they work with actual physical
network ports in Linux. As with an actual physical network port in
Linux, the base bond is basically VLAN 0. All other VLANs must be
configured on top of it as a sub-interface e.g. bond0.100 is VLAN 100 on
the bond0 network interface.
Hi,
In vSphere it is possible to create port group with vlan range 1-4094, can
we done the same on kvm with L2 network (on openvswitch or bridge)?
Can we use in cloudstack vm with vlan trunk?
Regards,
Piotr
