You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/pvcscale.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -117,7 +117,7 @@ The storageclass which will be used to allocated PVCs. It has to be present on c
117
117
118
118
### ACCESS_MODES
119
119
Default: `ReadWriteOnce`
120
-
`ACCESS_MODES` is access_mode for PVC inside Pod. This field does not affect the test itself and might be removed in the future.
120
+
`ACCESS_MODES` is access_mode for PVC inside Pod. This field does not affect the test itself and might be removed in the future.
121
121
122
122
### Smoke test variables
123
123
@@ -141,10 +141,11 @@ PVCSCALE_PAUSE=0
141
141
PVCSCALE_STORAGE_SIZE="1Gi"
142
142
PVCSCALE_STORAGECLASS="storgage_class_name"
143
143
ACCESS_MODES="ReadWriteOnce"
144
-
# adapt PUBLIC_KEY and PRIVATE_KEY to your needs
144
+
# adapt PUBLIC_KEY and PRIVATE_KEY to your needs
145
145
PUBLIC_KEY=~/.ssh/id_rsa.pub
146
146
PRIVATE_KEY=~/.ssh/id_rsa
147
147
echo "[orchestration]" > inventory
148
+
echo "${ORCHESTRATION_HOST}" >> inventory
148
149
```
149
150
150
151
After exporting above variables, execute test:
@@ -153,7 +154,7 @@ After exporting above variables, execute test:
153
154
time ansible-playbook -v -i inventory workloads/workloads/pvcscale.yml
154
155
```
155
156
156
-
### Test results
157
+
### Test results
157
158
158
159
PVCScale test creates first the number of Pods specified in `PVCSCALE_MAXPODS` variable. Once all Pods are in `READY` state with PVC in `Bound` status, PVCScale test collects data for all Pods when they are started, and from this information we can then see how long it takes to start Pods from Pod1..PodN.
0 commit comments