@@ -76,45 +76,45 @@ node1
7676
7777## Testing and Demos
7878
79- We can test the plugin is working by deploying the provided example iaa-qpl -demo test image.
79+ We can test the plugin is working by deploying the provided example accel-config -demo test image.
8080
81811 . Build a Docker image with an accel-config tests:
8282
8383 ``` bash
84- $ make iaa-qpl -demo
84+ $ make accel-config -demo
8585 ...
86- Successfully tagged intel/iaa-qpl -demo:devel
86+ Successfully tagged intel/accel-config -demo:devel
8787 ```
8888
89891. Create a pod running unit tests off the local Docker image:
9090
9191 ` ` ` bash
92- $ kubectl apply -f ./demo/iaa-qpl -demo-pod.yaml
93- pod/iaa-qpl -demo created
92+ $ kubectl apply -f ./demo/iaa-accel-config -demo-pod.yaml
93+ pod/iaa-accel-config -demo created
9494 ` ` `
9595
96961. Wait until pod is completed:
9797
9898 ` ` ` bash
99- $ kubectl get pods | grep iaa-qpl -demo
100- iaa-qpl -demo 0/1 Completed 0 31m
99+ $ kubectl get pods | grep iaa-accel-config -demo
100+ iaa-accel-config -demo 0/1 Completed 0 31m
101101
102102 If the pod did not successfully launch, possibly because it could not obtain the IAA
103103 resource, it will be stuck in the ` Pending` status:
104104
105105 ` ` ` bash
106106 $ kubectl get pods
107107 NAME READY STATUS RESTARTS AGE
108- iaa-qpl- demo 0/1 Pending 0 7s
108+ iaa-accel-config- demo 0/1 Pending 0 7s
109109 ` ` `
110110
111111 This can be verified by checking the Events of the pod:
112112
113113 ` ` ` bash
114114
115- $ kubectl describe pod iaa-qpl -demo | grep -A3 Events:
115+ $ kubectl describe pod iaa-accel-config -demo | grep -A3 Events:
116116 Events:
117117 Type Reason Age From Message
118118 ---- ------ ---- ---- -------
119- Warning FailedScheduling 2m26s default-scheduler 0/1 nodes are available: 1 Insufficient iaa.intel.com/wq-user-dedicated, 1 Insufficient iaa.intel.com/wq-user-shared .
119+ Warning FailedScheduling 2m26s default-scheduler 0/1 nodes are available: 1 Insufficient iaa.intel.com/wq-user-dedicated.
120120 ` ` `
0 commit comments