New example: EVPN/VXLAN bridging

EVPN/vxlan-bridging/README.md

@@ -0,0 +1,16 @@
+# EVPN/VXLAN bridging
+
+This directory contains *netlab* topology file for a simple VXLAN bridging scenario with EVPN control plane -- two VLANs bridged across an IP underlay network.
+
+![EVPN/VXLAN bridging topology](topology.png)
+
+After starting the lab, h1 should be able to ping h2, and h3 should be able to ping h4, but there should be no traffic routed between the VLANs. Also, the VLAN hosts should not be able to access the switches.
+
+## Changing Device Types
+
+This topology can be used with all network devices supporting VLAN, VXLAN, EVPN, BGP, and OSPF configuration modules, and all virtualization providers supported by *netlab*.
+
+The easiest way to change the device types is to edit the topology file. You could also use the **netlab up** [CLI arguments](https://netsim-tools.readthedocs.io/en/latest/netlab/up.html#usage):
+
+* To change the node device type, use `-s nodes._name_..device=xxx` CLI argument
+* To change the virtualization provider, use `-p` CLI argument.

EVPN/vxlan-bridging/topology.yml

@@ -0,0 +1,50 @@
+message: |
+  The devices under test are VLAN-to-VXLAN bridges
+
+  * h1 and h2 should be able to ping each other
+  * h3 and h4 should be able to ping each other
+  * h1 should not be able to reach h3
+
+provider: clab
+
+groups:
+  hosts:
+    members: [ h1, h2, h3, h4 ]
+    device: linux
+  switches:
+    members: [ s1,s2 ]
+    module: [ vlan,vxlan,ospf,bgp,evpn ]
+
+bgp.as: 65000
+
+vlans:
+  red:
+    mode: bridge
+  blue:
+    mode: bridge
+
+nodes:
+  h1:
+  h2:
+  h3:
+  h4:
+  s1:
+    device: eos
+  s2:
+    device: cumulus
+
+links:
+- h1:
+  s1:
+    vlan.access: red
+- h2:
+  s2:
+    vlan.access: red
+- h3:
+  s1:
+    vlan.access: blue
+- h4:
+  s2:
+    vlan.access: blue
+- s1:
+  s2: