Update notes after Fedora test.

cluster-v2-design.md

@@ -38,11 +38,10 @@ Fedora:
 - Really fast for something stable...
 - Cockpit is nice
 - Fedora minimal can't be installed on
-  cockpit.
+  cockpit without hitting tab alot.
 
-Decision: Stream
+Decision: Fedora Server
 
-Put var/rancher on a separate partition.
 
 ### K3S Distro
 
@@ -275,3 +274,55 @@ helm upgrade --install ingress-nginx ingress-nginx \
 ```
 
 ### k3s with nginx on fedora server
+```
+sudo systemctl disable firewalld --now
+export INSTALL_K3S_EXEC="server --disable traefik --selinux"
+curl -sfL https://get.k3s.io | sh -s -
+sudo chown jimmy:jimmy /etc/rancher/k3s/k3s.yaml
+sudo dnf install helm
+export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
+helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace
+```
+
+Import simple-ros2.
+Laptop:
+```
+podman save -o simple-ros2.tar simple-ros2:latest
+scp simple-ros2.tar 192.168.1.106:~/.
+```
+On server:
+```
+sudo ctr images import ./simple-ros2.tar
+# wait forever....
+```
+
+Test yaml:
+```
+---
+apiVersion: v1
+kind: Pod
+metadata:
+  name: test-pod
+spec:
+  containers:
+  - name: simple-ros2
+    image: localhost/simple-ros2:latest
+    imagePullPolicy: Never
+    args: [ros2, launch, j7s-simple, j7s_publisher_launch.py]
+```
+
+### VM Host set up
+
+I **think** I ran something like this when I set up the VM host.
+I don't remember exactly, and I didn't document it...
+
+This should be carefully looked at before running.
+
+```
+nmcli connection add ifname br0 type bridge con-name br0 connection.zone trusted
+nmcli connection add type bridge-slave ifname enp4s0 master br0
+nmcli connection modify br0 bridge.stp no
+nmcli connection modify enp4s0 autoconnect no
+nmcli connection down enp4s0
+nmcli connection up id br0
+```

notes.md

@@ -211,3 +211,8 @@ If we later want to do this on an overlay network:
    `INSTALL_K3S_EXEC="server --node-ip '10.100.100.5' --advertise-address '10.100.100.5' --flannel-iface 'wg0'" ./k3s.sh`
 4. For node:
    `INSTALL_K3S_EXEC="agent --server 'https://10.100.100.5:6443' --token 'K3S_TOKEN' --node-ip '10.100.100.?' --advertise-address '10.100.100.?' --flannel-iface 'wg0'" ./k3s.sh`
+
+# Bad Ideas
+
+1. Longhorn -> wonky performance issues on cluster after installing
+2. Multus -> CNI version does not seem compatible with k3s.