@@ -949,6 +949,14 @@ The `vlan` sections contains two parameters:
949
949
* `id`: VLAN ID integer.
950
950
* `protocol`: `802.1q` (default) or `802.1ad`
951
951
952
+ With nmstate 2.2.1+, when using Nmstate with NetworkManager backend, nmstate
953
+ can creating VLAN over unmanaged interface, hence if you never mention VLAN
954
+ parent in `interfafaces` section of desired state, nmstate will not convert
955
+ VxLAN parent interface from unmanaged to managed.
956
+
957
+ For `generate configuration(gc)` mode, unmentioned VLAN parent will not
958
+ get automatically created interface profile.
959
+
952
960
# ## VxLAN Interface
953
961
954
962
The `vxlan` section of interface holds the parameters of VxLAN specific
@@ -982,6 +990,14 @@ The `vxlan` sections contains two parameters:
982
990
983
991
Currently, we only support VxLAN based on IEEE 802.1Q protocol.
984
992
993
+ With nmstate 2.2.1+, when using Nmstate with NetworkManager backend, nmstate
994
+ can creating VxLAN over unmanaged interface, if you never mention VxLAN parent
995
+ in `interfafaces` section of desired state, nmstate will not convert VxLAN
996
+ parent interface from unmanaged to managed.
997
+
998
+ For `generate configuration(gc)` mode, unmentioned VxLAN parent will not
999
+ get automatically created interface profile.
1000
+
985
1001
# ## Linux Bridge Interface
986
1002
987
1003
The `bridge` section of interface could hold parameters of Linux Bridge
0 commit comments