802.1Q VLAN Networks

This guide describes how to enable Network isolation provided through host-managed VLANs. This driver will create a bridge for each OpenNebula Virtual Network and attach an VLAN tagged network interface to the bridge. This mechanism is compliant with IEEE 802.1Q.

The VLAN id will be the same for every interface in a given network, automatically computed by OpenNebula. It may also be forced by specifying an VLAN_ID parameter in the Virtual Network template.

OpenNebula Configuration

The VLAN_ID is calculated according to this configuration option of oned.conf:

#  VLAN_IDS: VLAN ID pool for the automatic VLAN_ID assigment. This pool
#  is for 802.1Q networks (Open vSwitch and 802.1Q drivers). The driver
#  will try first to allocate VLAN_IDS[START] + VNET_ID
#     start: First VLAN_ID to use
#     reserved: Comma separated list of VLAN_IDs or ranges. Two numbers
#     separated by a colon indicate a range.

    START    = "2",
    RESERVED = "0, 1, 4095"

By modifying that parameter you can reserve some VLANs so they aren’t assigned to a Virtual Network. You can also define the first VLAN_ID. When a new isolated network is created, OpenNebula will find a free VLAN_ID from the VLAN pool. This pool is global, and it’s also shared with the Open vSwitch network mode.

The following configuration attributes can be adjusted in /var/lib/one/remotes/etc/vnm/OpenNebulaNetwork.conf:

Parameter Description
validate_vlan_id Set to true to check that no other vlans are connected to the bridge
keep_empty_bridge Set to true to preserve bridges with no virtual interfaces left.
bridge_conf Hash Options for brctl (deprecated, will be translated to ip-route2 options)
ip_bridge_conf Hash Options for ip-route2 ip link add <bridge> type bridge ...
ip_link_conf Hash Arguments passed to ip link add


# Following options will be added when creating bridge. For example:
#     ip link add name <bridge name> type bridge stp_state 1
# :ip_bridge_conf:
#     :stp_state: on

    # These options will be added to the ip link add command. For example:
    #     sudo ip link add lxcbr0.260  type vxlan id 260 group \
    #       ttl 16 dev lxcbr0 udp6zerocsumrx  tos 3
        :tos: 3

Defining a 802.1Q Network

To create a 802.1Q network include the following information:

Attribute Value Mandatory
PHYDEV Name of the physical network device that will be attached to the bridge. YES
BRIDGE Name of the linux bridge, defaults to onebr<net_id> or onebr.<vlan_id> NO
VLAN_ID The VLAN ID, will be generated if not defined and AUTOMATIC_VLAN_ID is set to YES YES (unless AUTOMATIC_VLAN_ID)
AUTOMATIC_VLAN_ID Mandatory and must be set to YES if VLAN_ID hasn’t been defined YES (unless VLAN_ID)
MTU The MTU for the tagged interface and bridge NO

The following example defines a 802.1Q network

NAME    = "hmnet"
VN_MAD  = "802.1Q"
PHYDEV  = "eth0"
VLAN_ID = 50        # optional. If not setting VLAN_ID set AUTOMATIC_VLAN_ID = "YES"
BRIDGE  = "brhm"    # optional

In this scenario, the driver will check for the existence of the brhm bridge. If it doesn’t exist it will be created. eth0 will be tagged (eth0.50) and attached to brhm (unless it’s already attached).