Cleanup and finalize the Multi-VRF with Hosts example

VRF/vrf-lite-hosts/README.md

@@ -32,15 +32,20 @@ The `multi-vrf.yml` topology contains two isolated VRFs:
 * VRF *red* containing Linux hosts h1 and h2
 * VRF *blue* containing Linux hosts h3 and h4
 
+![Isolated VRFs topology](vrf-lite-simple.png)
+
 After starting the lab, h1 should be able to ping h2 but not h3 or h4, and h3 should be able to ping h4 but not h1 or h2.
 
 ## Inter-VRF Route Leaking
 
-The `vrf-route-leaking.yml` topology contains two VRFs:
+The `vrf-route-leaking.yml` topology contains three VRFs:
 
-* VRF *red* containing Linux hosts h1 and h2
-* VRF *blue* containing Linux hosts h3 and h4
+* VRF *red* containing Linux host h1
+* VRF *blue* containing Linux host h2
+* VRF *common* contains Linux host srv
+
+A simple common services VPN topology is set up to enable h1 and h2 to communicate with srv, but not with each other:
 
-Routes from *red* VRF are imported into *red* and *blue* VRF. Likewise, the routes from *blue* VRF are imported into both VRFs.
+![Common services VRFs](vrf-lite-common.png)
 
-After starting the lab, all hosts (h1..h4) should be able to ping all other hosts.
+After starting the lab, h1 and h2 should be able to ping srv but not each other.

VRF/vrf-lite-hosts/multi-vrf.yml

@@ -7,6 +7,7 @@ vrfs:
 nodes:
   rtr:
     module: [ vrf ]
+    device: eos
   h1:
   h2:
   h3:

VRF/vrf-lite-hosts/vrf-route-leaking.yml

@@ -2,25 +2,24 @@ defaults.device: linux
 
 vrfs:
   red:
-    import: [ red, blue ]
+    import: [ red, common ]
   blue:
-    import: [ red, blue ]
+    import: [ blue, common ]
+  common:
+    import: [ red, blue, common ]
 
 nodes:
   rtr:
     module: [ vrf ]
-    bgp.as: 65000
+    device: eos
   h1:
   h2:
-  h3:
-  h4:
+  srv:
 
 links:
 - rtr: { vrf: red }
   h1:
-- rtr: { vrf: red } 
+- rtr: { vrf: blue } 
   h2:
-- rtr: { vrf: blue }
-  h3:
-- rtr: { vrf: blue }
-  h4:
+- rtr: { vrf: common }
+  srv: