Add Ingress and Storage test slides with Vagrant instructions

pages/run-slide.md

@@ -2,9 +2,10 @@
 level: 2
 ---
 
-# RUN
+# Getting Started
+
+... with Vagrant
 
-So what does `infctl` look like then ...
 
 ````md magic-move {lines: true}
 
@@ -57,7 +58,7 @@ infctl -f pipelines/dev/vagrant-k3s.json
 ````
 <div v-click>
 
-Here is a [Demo](http://ascii.headshed.dev/a/ISIOKVA1AmckG2muwOMUOG4z5)
+Lets see what this looks like for real in a [Demo](http://ascii.headshed.dev/a/ISIOKVA1AmckG2muwOMUOG4z5)
 
 </div>
 
@@ -66,3 +67,32 @@ Here is a [Demo](http://ascii.headshed.dev/a/ISIOKVA1AmckG2muwOMUOG4z5)
 Lets  [try again](http://ascii.headshed.dev/a/bUzNNojNjkxytfDT6cRqhSVwN)
 
 </div>
+
+
+<!--
+
+Let's see how to get started with vagrant
+
+We use Vagrant to stand up a cluster of 3 nodes and a workstation locally
+
+Vagrant by default uses Virtualbox which works across Windows, Linux and Mac
+
+Git cloning the `infctl-cli` repository gets us the starter files
+
+changing to the vagrant folder we can use `vagrant up` to see what would happen **without** `infctl`
+
+we see the first gotcha in any automation process - where the tooling does not know what to do and asks the user for input
+
+This in IaC is an epic fail and we need to copy the name of the interface we want to use for the external network in our test case and export it as an environment variable
+
+export VAGRANT_BRIDGE=wlp0s20f3
+
+sets to a device on the example system
+
+which allows us now to run `infctl` with a deployment file 
+
+lets see what this looks like for real
+
+....
+
+-->