crypto-perf: add kustomization and move to deployments

We plan to use crypto-perf for simple QAT testing. This commit adds
kustomization to make the deployment easier. The original .yaml is
also moved to deployments/ with some changes.

For instance, it turns out also vfio-pci mode with DPDK needs CAP_SYS_ADMIN
(See PR: #187 which states that only igb_uio would need it).

kustomize is available part of kubectl since kubernetes v1.14.

Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>

Author: mythi

cmd/qat_plugin/README.md

@@ -105,20 +105,20 @@ $ kubectl describe node <node name> | grep qat.intel.com/generic
       For a DPDK-based workload, you may need to add hugepage request and limit.
 
      ```
-     $ kubectl create -f demo/crypto-perf-dpdk-pod-requesting-qat.yaml
+     $ kubectl apply -k deployments/qat_dpdk_app/base/
      $ kubectl get pods
        NAME                     READY     STATUS    RESTARTS   AGE
-       dpdkqatuio               1/1       Running   0          27m
+       qat-dpdk                 1/1       Running   0          27m
        intel-qat-plugin-5zgvb   1/1       Running   0          3h
 
      ```
 
-    **Note**: If the `igb_uio` VF driver is used with the QAT device plugin,
-    the workload be deployed with `SYS_ADMIN` capabilities added.
+    **Note**: The deployment example above uses kustomize that is available in
+    kubectl since kubernetes v1.14 release.
 
 3. Manually execute the `dpdk-test-crypto-perf` application to review the logs:
    ```
-   $ kubectl exec -it dpdkqatuio bash
+   $ kubectl exec -it qat-dpdk bash
 
    $ ./dpdk-test-crypto-perf -l 6-7 -w $QAT1 -- --ptest throughput --\
 	devtype crypto_qat --optype cipher-only --cipher-algo aes-cbc --cipher-op \

demo/screencast-qat-dpdk.sh

@@ -35,7 +35,7 @@
   out "This video demonstrates the Intel(R) QuickAssist Technology device Plugin for Kubernetes"
   out "Prerequisites:"
   out "* Intel(R) QuickAssist Technology (Intel(R) QAT) DH895xcc Chipset with SR-IOV enabled"
-  out "* Kubernetes v1.12 cluster"
+  out "* Kubernetes v1.14 cluster"
   out "* Data Plane Development Kit (DPDK) drivers configured"
   out "Let's get started!"
 }
@@ -80,10 +80,10 @@
 {
   clear
   out "7. View pod specification file for pod requesting QAT Virtual Functions:"
-  command "cat crypto-perf-dpdk-pod-requesting-qat.yaml"
+  command "kubectl apply --dry-run -o yaml -k ../deployments/qat_dpdk_app/base"
   sleep 5 
   out "8. Create Pod requesting QAT Virtual Functions:"
-  command "kubectl create -f crypto-perf-dpdk-pod-requesting-qat.yaml"
+  command "kubectl apply -k ../deployments/qat_dpdk_app/base"
   sleep 2
   command "kubectl get pods"
   sleep 2
@@ -94,7 +94,7 @@
   out "9. Get a shell to the running container and run a DPDK application using QAT device"
   out "* \"export\": Lists environment variables - note QAT0, QAT1, QAT2... etc"
   out "* \"./dpdk-test-crypto-perf -l 6-7 -w \$QAT0 -- --ptest throughput --devtype crypto_qat --optype cipher-only --cipher-algo aes-cbc --cipher-op encrypt --cipher-key-sz 16 --total-ops 10000000 --burst-sz 32 --buffer-sz 64\" : Manually executes the dpdk-test-crypto-perf application to review the logs"
-   command "kubectl exec -it dpdkqatuio bash"
+   command "kubectl exec -it qat-dpdk bash"
   sleep 10
 }
  if [ "$1" == 'play' ] ; then

…crypto-perf-dpdk-pod-requesting-qat.yaml …crypto-perf-dpdk-pod-requesting-qat.yamldemo/crypto-perf-dpdk-pod-requesting-qat.yaml renamed to deployments/qat_dpdk_app/base/crypto-perf-dpdk-pod-requesting-qat.yaml demo/crypto-perf-dpdk-pod-requesting-qat.yaml renamed to deployments/qat_dpdk_app/base/crypto-perf-dpdk-pod-requesting-qat.yaml

@@ -1,10 +1,10 @@
 kind: Pod
 apiVersion: v1
 metadata:
-  name: dpdkqatuio
+  name: qat-dpdk
 spec:
   containers:
-  - name: dpdkcontainer
+  - name: crypto-perf
     image: crypto-perf:devel
     imagePullPolicy: IfNotPresent
     command: [ "/bin/bash", "-c", "--" ]
@@ -17,16 +17,17 @@ spec:
         cpu: "3"
         memory: "128Mi"
         qat.intel.com/generic: '4'
-        hugepages-2Mi: "1Gi"
+        hugepages-2Mi: "128Mi"
       limits:
         cpu: "3"
         memory: "128Mi"
         qat.intel.com/generic: '4'
-        hugepages-2Mi: "1Gi"
+        hugepages-2Mi: "128Mi"
     securityContext:
       capabilities:
         add:
-          ["IPC_LOCK"]
+          ["IPC_LOCK", "SYS_ADMIN"]
+  restartPolicy: Never
   volumes:
   - name: hugepage
     emptyDir:

deployments/qat_dpdk_app/base/kustomization.yaml

@@ -0,0 +1,2 @@
+resources:
+- crypto-perf-dpdk-pod-requesting-qat.yaml