docs(day2): Added first talk slides

content/day2/01_wasm-vm.md

@@ -0,0 +1,48 @@
+---
+title: "Beyond MicroserVices: Running VMS, WASM, and AI WOrkloads on Kubernetes"
+weight: 1
+tags:
+ - wasm
+ - vm
+---
+
+<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
+<!-- {{% button href="https://docs.google.com/presentation/d/1nEK0CVC_yQgIDqwsdh-PRihB6dc9RyT-" style="tip" icon="person-chalkboard" %}}Slides{{% /button %}} -->
+
+This is more of an "overview" talk and less actual new knowledge or specialized stuff.
+
+## Baseline
+
+We all know
+
+- Deployments
+- Statefulsets
+- Functions
+- and so on
+
+## Strange new World: VMs on Kubernetes
+
+- Why VM? Legacy! (and VDI and some testing envs)
+- The cool thing: VMs are basicly Pods with virtualization powered by kvm/qemu/libvirt
+- Demo: Kubernetes on GCP with KubeVirt installed and deployment of a vm with guest tool access
+- TL;DR: Kubevirt makes the vm management ux pretty good
+
+TODO: Steal vm vs container vs kubevirt layers illustration
+
+## Kind of a different universe: WASM
+
+- WASM: Low level typed intermediate machine code
+- WASI: System Interface for externel functions (fs, network, ...)
+- Pro: Secure, Portable and performant
+- Con: Bleeding-edge, complex, and not feature-complete
+
+### Now on kubernetes (with spinkube)
+
+- Still executed on a node with a pod, but this pod does not contain a container, but a Spin which contains the service as a wasm container (via the containerd-wasm shim)
+- Up to 10x faster spin up than a traditional container
+
+## And how about ai?
+
+- Goal: Host yourself or at least in the EU
+- Simple quickstart: Ollama
+- Challenge: Cost planning

content/day2/_index.md

@@ -4,3 +4,7 @@ title: Day 2
 weight: 2
 ---
 
+The schedule on day 2 was pretty ai platform focused.
+Sadly all of the ai focused talks were about building workflows and platforms with gitops and friends, not about actually building the base  (gpus scheduling and so on).
+We also had some "normal" work tasks resulting in less talks visited and more "normal" work + networking.
+

content/lessons_learned/_index.md

@@ -4,6 +4,7 @@ title: Lessons Learned
 weight: 3
 ---
 
-## Mal anschauen
+## Maybe look into
 
 - Otterize für Netzwrok policies
+- Spinkube/Wasm Cloud for optimized wasm on kubernetes