The EPIC https://issues.redhat.com/browse/OSPRH-2273 already covers the required PR details, so this story is for testing and verification only.

os-net-config supports VLAN interfaces. VLANs are used to separate network traffic by function and to separate control plane traffic (provisioning network, Internal API, storage management) from data plane traffic (tenant traffic, provider VLANs, storage, etc.) and keep those separate from external (North-South) traffic. When migrating from ifcfg to nmstate it is important that the VLANs are preserved, and that the VLAN IDs are applied to the correct interfaces that match switchport configuration, and that MTUs are configured correctly to allow for VLAN tags. VLANs are especially important when there are limited NIC ports and/or NIC ports are bonded and multiple or all networks are carried across one physical or logical interface.

A sample template is given below:

network_config:
- type: interface
  name: nic1
- type: vlan
  device: nic1
  mtu: 9000
  vlan_id: 10
  dns_servers: ['10.48.242.30', '10.41.248.15']
  addresses:
  - ip_netmask: 198.51.200.2/24
  routes:
  - default: true
    next_hop: 192.51.200.1

- type: vlan
  device: nic1
  mtu: 9000
  vlan_id: 20
  addresses:
  - ip_netmask: 198.51.100.2/24