ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
2
3
4
5
ISO TESTED
6
Test IDTest NameTest ObjectiveExpected behaviorTest StepsCommentsStatus
7
1QAT_StarlingX_001Verify that QAT driver / service is up and running Driver / Service is up and running after install the controller-0controller-0:~$ lsmod | grep "qa"
qat_dh895xcc 13581 0
intel_qat 141557 2 usdm_drv,qat_dh895xcc
authenc 17776 1 intel_qat
uio 19259 1 intel_qat


controller-0:~$ service qat_service status
Checking status of all devices.
There is 3 QAT acceleration device(s) in the system:
qat_dev0 - type: c6xx, inst_id: 0, bsf: 88:00.0, #accel: 5 #engines: 10 state: up
qat_dev1 - type: c6xx, inst_id: 1, bsf: 8a:00.0, #accel: 5 #engines: 10 state: up
qat_dev2 - type: c6xx, inst_id: 2, bsf: 8c:00.0, #accel: 5 #engines: 10 state: up		PASSED
8
2QAT_StarlingX_002Verify newly added system inventory commands to support crypto deviceSystem should show the QAT device listedsystem host-device-list compute-0

+-------+----------+--------+--------+--------+-----------------------+-------------------------+------------------------+-----------+---------+
| name | address | class | vendor | device | class name | vendor name | device name | numa_node | enabled |
| | | id | id | id | | | | | |
+-------+----------+--------+--------+--------+-----------------------+-------------------------+------------------------+-----------+---------+
| pci_0 | 0000:02: | 030000 | 1a03 | 2000 | VGA compatible | ASPEED Technology, Inc. | ASPEED Graphics Family | 0 | True |
| 000_0 | 00.0 | | | | controller | | | | |
| 2_00_ | | | | | | | | | |
| 0 | | | | | | | | | |
| | | | | | | | | | |
+-------+----------+--------+--------+--------+-----------------------+-------------------------+------------------------+-----------+---------+
| pci_0 | 0000:03: | 040000 | 1a03 | 3000 | QAT compatible | Intel Corporation, Inc. | QAT DH859xcc | 0 | True |
| 000_0 | 00.0 | | | | controller | | | | |
| 3_00_ | | | | | | | | | |
| 0 | | | | | | | | | |
| | | | | | | | | | |
+-------+----------+--------+--------+--------+-----------------------+-------------------------+------------------------+-----------+---------+		PASSED
9
3QAT_StarlingX_003Verify that GUI can be used to configure crypto deviceHorizon shoudl shown this device ? (This test case can be changed / dropped, depending on the current StarlingX support)Verify that the GUI displays the device info properly, disable / enable the device from GUI
10
4QAT_StarlingX_004Verify QAT support for guest with VF bound in a flavorVerify that a flavor is created successfullyCrate a new flavor from GUI an add an extra spec for Coleto Creek (PCI Alias) (TBD if this is supported already in StarlingX

Verify that the flavor is created successfully

Verify the guest is launched successfully and in ACTIVE state

Launch a guest with the above created flavor an SRIOV interfaces. (This might be dependant on HW / BIOS settings, and StarlingX current support)

Verify the guest is launched succesfully in ACTIVE state


11
5QAT_StarlingX_005Verify that QAT support isn't disabled while device is in use by the guestVerify that if QAT support is disabled while device is in use by the guest an error message is throw (TBD if StarlingX support this )Create a new flavor from GUI and add an extra-spec for Coleto Creek (PCI Alias)

Verify that the flavor is created successfully

Launch a guest with the above created flavor

Verify the guest is launched successfully and in ACTIVE state

Force lock the compute and disable the device on the host where the guest is hosted

Verify that the disable command is rejected and proper error message displayed
12
6QAT_StarlingX_006Verify that a guest can be launched with multiple crypto VFs (VIrtual Functions), verify the max number of crypto VFs, verify beyond the limit (max is 32, To be confirmed), and VM maintenance activity.Verify that using all valid options, the flavor / guest is created successfully, when this condition isn't meet, a rejection (or error message) will be shown.1: Create a new flavor from GUI and add extra-spec for Coletro Creek (PCI Alias, input 32 for the number of devices)
Expected Result: Verify that the flavor is created successfully
2: Launch a guest with the above created flavor and SRIOV interfaces.
Expected Result: Verify the guest is launched successfully and in ACTIVE state.
3: cold migrate the guest created in step-2.
Expected Result: Verify the guest is migrated successfully.
4: suspend/resume the guest created in step-2.
Expected Result: Verify the guest is suspend/resume successfully.
5: resize (cpu and memory) the guest created in step-2.
Expected Result: Verify the guest is resized successfully.
6: Create a new flavor from GUI and add extra-spec for Coletro Creek (PCI Alias, input 45 for the number of devices)
Expected Result: Verify that the flavor creation is rejected
13
7QAT_StarlingX_007Verify the co-existance between guests with crypto VFs and guests without VFsVerify the co-existance between guests with crypto VFs and guests without VFs1: Launch multiple guests with crypto VFs.
Expected Result: Verify all guest are launched and ACTIVE
2: Launch, DPDK guests (This can be tested until post-merge OVS/DPDK feature), instead launch no VFs guests.
Expected Result: Verify tall guests are launched successfully and in ACTIVE state.
3: cold/live migrate the guest created in step-2.
Expected Result: Verify the guest is migrated successfully.
4: suspend/resume the guest created in step-2.
Expected Result: Verify the guest is suspend/resume successfully.
5: resize (cpu and memory) the guest created in step-2.
Expected Result: Verify the guest is resized successfully.
6: Run sample app to exercise crypto in the guset
Expected Result: Verify no issues are reported by the sample app.
7: Evacuate the guest by rebooting the compute
Expected Result: Verify the guest is evacuated succ essfully.
8: Run sample app to exercise crypto in the guset
Expected Result: Verify no issues are reported by the sample app.
14
8QAT_StarlingX_008Verify the co-existance between crypto VFs and various type of interface atttachmentVerify that guests with crypto VFs and SRIOV interfaces can be launched and execute VM maintenance basic commands.1: Launch a guest with crypto VFs, and SRIOV network attachments.
Expected Result: Verify all guests are launched and ACTIVE
2: cold/live migrate the guest created in step-2.
Expected Result: Verify the guest is migrated successfully.
3: suspend/resume the guest created in step-2.
Expected Result: Verify the guest is suspend/resume successfully.
4: resize (cpu and memory) the guest created in step-2.
Expected Result: Verify the guest is resized successfully.
5: Run sample app to exercise crypto in the guset
Expected Result: Verify no issues are reported by the sample app.
6: Evacuate the guest by rebooting the compute
Expected Result: Verify the guest is evacuated successfully.
7: Run sample app to exercise crypto in the guset
Expected Result: Verify no issues are reported by the sample app.
15
9QAT_StarlingX_009Verify QATZip library functionalityVerify that QATzip is setup correctly for compressing or decompressing files under StarlingX environment + QAT PCIe HardwareDownload QATZip library https://github.com/intel/QATzip
Install QATZip library
qzip -k $your_input_file (use a file equals or bigger than 2GB)
Perform for different compression levels / chunk size
More specific details about test steps TBD.
16
10QAT_StarlingX_010REST API ?TBDTBD
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100