Skip to content

Commit 490551e

Browse files
authored
Merge pull request #18 from vbedida79/patch-130323-4
tests_l1: Update readme
2 parents 50dbd4a + 26dea37 commit 490551e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

tests/l1/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
### L1 tests overview
2-
Layer 1 tests are used to check for the Intel hardware featurs's devices and drivers (in-tree or out-of-tree) along with setting up the [machine configuration](https://github.com/intel/intel-technology-enabling-for-openshift/blob/main/machine_configuration/README.md) through MCO and OOT drivers through [KMMO](https://github.com/intel/intel-technology-enabling-for-openshift/blob/main/kmmo/README.md) and preparing for (before) the deployment of device plugins through [Intel-device-plugins operator](https://github.com/intel/intel-technology-enabling-for-openshift/blob/main/idpo/README.md). This gives user the information on whether Intel Hardware features are well supported in the OS running on the nodes. Currently, these tests are initial and will be refined in the future releases.
2+
Layer 1 tests are used to check for the Intel hardware feature's devices and drivers (in-tree or out-of-tree) along with setting up the [machine configuration](https://github.com/intel/intel-technology-enabling-for-openshift/blob/main/machine_configuration/README.md) through MCO and OOT drivers through [KMMO](https://github.com/intel/intel-technology-enabling-for-openshift/blob/main/kmmo/README.md) and preparing for (before) the deployment of device plugins through [Intel-device-plugins operator](https://github.com/intel/intel-technology-enabling-for-openshift/blob/main/idpo/README.md). This gives user the information on whether Intel Hardware features are well supported in the OS running on the nodes. Currently, these tests are initial and will be refined in the future releases.
33

44
#### Deployment steps
55
The OCP buildconfig is leveraged to build the source code's container image and push it to the embedded repository through OCP imagestream. It is deployed as a daemonset with an initcontainer for pod completion. Information about Intel hardware features supported on every node in the cluster is the result.
@@ -14,7 +14,7 @@ The following deployment steps have been verified on OCP 4.12 baremetal cluster.
1414
`oc apply -f l1_deploy.yaml`
1515
* To check the results on a chosen node:
1616
`oc logs <l1-test-pod>`
17-
* Sample result on node with dGPU support only:
17+
* Sample result on node with Intel® Data Center GPU Flex Series card:
1818
`E0223 20:04:11.864401 1 sgx.go:22] SGX enclave file not present: stat /dev/sgx_enclave: no such file or directory`
1919
`E0223 20:04:11.864438 1 sgx.go:24] SGX provision file not present: stat /dev/sgx_provision: no such file or directory`
2020
`I0223 20:04:11.864504 1 dgpu.go:44] Card and device nodes present for dGPU`

0 commit comments

Comments
 (0)