shift-week: add topolvm upstream manifests

Signed-off-by: Evgeny Slutsky <[email protected]>

Author: eslutsky

okd/storage/README.md

@@ -1,4 +1,57 @@
 ## examples for using with storage
+
+### run Microshift with upsteam topolvm
+
+1. prepare the LVM backend on the host (example only)
+  ```bash
+  truncate --size=20G /tmp/lvmdisk
+	losetup -f /tmp/lvmdisk
+	device_name=$(losetup -j /tmp/lvmdisk | cut -d: -f1)
+	vgcreate -f -y myvg1 /dev/${device_name}
+	lvcreate -T myvg1/thinpool -L 6G
+  ```
+
+
+1. run microshift in OKD and wait for its to be ready
+  ```bash
+      export kustomize_dir=/usr/lib/microshift/manifests.d/001-topolvm
+      sudo podman run --privileged --rm --name microshift-okd \
+        -v $(pwd)/okd/storage/topolvm/manifests:${kustomize_dir}:z \
+        --hostname 127.0.0.1.nip.io \
+        -p 5432:5432 -p 6443:6443 \
+        -d localhost/microshift-okd-4.19
+  ```
+
+1. wait for all the components to come up 
+    ```bash
+    sudo podman exec  microshift-okd bash -c "microshift healthcheck "
+    ```
+1. apply the manifests:
+   `sudo podman exec  microshift-okd bash -c "oc apply -f /usr/lib/microshift/manifests.d/001-topolvm/"`
+
+   TODO: embed manifests so it will be performed automaticly
+
+### load some example data into the psql
+
+1. copy kubeconfig from the container
+    ```bash
+        sudo podman cp microshift-okd:/var/lib/microshift/resources/kubeadmin/127.0.0.1.nip.io/kubeconfig .
+        sudo chown ${USERNAME}:${USERNAME} kubeconfig
+    ```
+
+
+1. applying manifests
+```bash
+ # install cert-manager
+ oc apply -f manifests/namespace.yaml
+ oc apply -f manifests/cert-manager.yaml
+ oc apply -f manifests/topolvm.yaml
+```
+
+
+1. oc ally 
+
+
 ###  run Microshift with hostpath volume
 A hostPath volume mounts a file or directory from the host node’s file system into your pod. 
 Most pods do not need a hostPath volume, but it does offer a quick option for testing should an application require it (some requires persistent storage - DBs).
@@ -12,7 +65,7 @@ Most pods do not need a hostPath volume, but it does offer a quick option for te
 
     sudo podman run --privileged --rm --name microshift-okd \
       -v ${data_dir}:/var/lib/pvdata:z \
-      -v $(pwd)/okd/examples/hostpath:${kustomize_dir}:z \
+      -v $(pwd)/okd/storage/hostpath:${kustomize_dir}:z \
       --hostname 127.0.0.1.nip.io \
       -p 5432:5432 -p 6443:6443 \
       -d localhost/microshift-okd 
@@ -46,3 +99,4 @@ Most pods do not need a hostPath volume, but it does offer a quick option for te
 
 1. stop the container `sudo podman stop microshift-okd`
 1. start a new container instance and verify data is still exists.
+