Skip to content

Commit

Permalink
Merge pull request #276 from chaitanya1731/release-v1.3.0
Browse files Browse the repository at this point in the history
Updated release version v1.3.0
  • Loading branch information
uMartinXu authored Jun 21, 2024
2 parents fd472a1 + 4e0bcd6 commit 4edde59
Show file tree
Hide file tree
Showing 11 changed files with 23 additions and 23 deletions.
2 changes: 1 addition & 1 deletion device_plugins/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Follow the steps below to install Intel Device Plugins Operator using OpenShift
### Installation via command line interface (CLI)
Apply the [install_operator.yaml](/device_plugins/install_operator.yaml) file:
```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/device_plugins/install_operator.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/device_plugins/install_operator.yaml
```

### Verify Installation via CLI
Expand Down
2 changes: 1 addition & 1 deletion device_plugins/deploy_gpu.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
## Create CR via CLI
Apply the CR yaml file:
```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/device_plugins/gpu_device_plugin.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/device_plugins/gpu_device_plugin.yaml
```

## Verify via CLI
Expand Down
2 changes: 1 addition & 1 deletion device_plugins/deploy_qat.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
## Create CR via CLI
Apply the CR yaml file:
```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/device_plugins/qat_device_plugin.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/device_plugins/qat_device_plugin.yaml
```

## Verify via CLI
Expand Down
2 changes: 1 addition & 1 deletion device_plugins/deploy_sgx.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
## Create CR via CLI
Apply the CR yaml file:
```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/device_plugins/sgx_device_plugin.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/device_plugins/sgx_device_plugin.yaml
```

## Verify via CLI
Expand Down
2 changes: 1 addition & 1 deletion e2e/inference/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ To enable the interactive mode, the OpenVINO notebook CR needs to be created and

Create `AcceleratorProfile` in the `redhat-ods-applications` namespace
```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/e2e/inference/accelerator_profile.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/e2e/inference/accelerator_profile.yaml
```

1. Navigate to `openvino-notebooks` ImageStream and add the above created `AcceleratorProfile` key to the annotation field, as shown in the image below:
Expand Down
2 changes: 1 addition & 1 deletion kmmo/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ $ oc label node <node_name> intel.feature.node.kubernetes.io/dgpu-canary=true

3. Use pre-build mode to deploy the driver container.
```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/kmmo/intel-dgpu.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/kmmo/intel-dgpu.yaml
```

4. After the driver is verified on the cluster through the canary deployment, simply remove the line shown below from the [`intel-dgpu.yaml`](/kmmo/intel-dgpu.yaml) file and reapply the yaml file to deploy the driver to the entire cluster. As a cluster administrator, you can also select another deployment policy.
Expand Down
2 changes: 1 addition & 1 deletion machine_configuration/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Any contribution in this area is welcome.
* Turn on `intel_iommu` kernel parameter and load `vfio_pci` at boot for QAT provisioning

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/machine_configuration/100-intel-qat-intel-iommu-on.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/machine_configuration/100-intel-qat-intel-iommu-on.yaml
```

Note: This will reboot the worker nodes when changing the kernel parameter through MCO.
Expand Down
4 changes: 2 additions & 2 deletions nfd/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,12 +14,12 @@ Note: As RHOCP cluster administrator, you might need to merge the NFD operator c

1. Create `NodeFeatureDiscovery` CR instance.
```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/nfd/node-feature-discovery-openshift.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/nfd/node-feature-discovery-openshift.yaml
```

2. Create `NodeFeatureRule` CR instance.
```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/nfd/node-feature-rules-openshift.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/nfd/node-feature-rules-openshift.yaml
```

## Verification
Expand Down
16 changes: 8 additions & 8 deletions tests/l2/dgpu/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,13 @@ This workload runs [clinfo](https://github.com/Oblomov/clinfo) utilizing the i91
* Build the workload container image.

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/dgpu/clinfo_build.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/dgpu/clinfo_build.yaml
```

* Deploy and execute the workload.

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/dgpu/clinfo_job.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/dgpu/clinfo_job.yaml
```

* Check the results.
Expand Down Expand Up @@ -47,13 +47,13 @@ This workload runs ```hwinfo``` utilizing the i915 resource from GPU provisionin
* Build the workload container image.

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/dgpu/hwinfo_build.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/dgpu/hwinfo_build.yaml
```

* Deploy and execute the workload.

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/dgpu/hwinfo_job.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/dgpu/hwinfo_job.yaml
```

* Check the results
Expand Down Expand Up @@ -96,13 +96,13 @@ This workload runs [vainfo](https://github.com/intel/libva-utils) utilizing the
* Build the workload container image.

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/dgpu/vainfo_build.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/dgpu/vainfo_build.yaml
```

* Deploy and execute the workload.

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/dgpu/vainfo_job.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/dgpu/vainfo_job.yaml
```

* Check the results.
Expand Down Expand Up @@ -163,13 +163,13 @@ This workload runs various test programs from [libvpl](https://github.com/intel/
* Build the workload container image.

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/dgpu/intelvpl_build.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/dgpu/intelvpl_build.yaml
```

* Deploy and execute the workload.

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/dgpu/intelvpl_job.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/dgpu/intelvpl_job.yaml
```

* Check the results.
Expand Down
8 changes: 4 additions & 4 deletions tests/l2/qat/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,25 +6,25 @@ This workload runs [qatlib](https://github.com/intel/qatlib) sample tests using
Please replace the credentials in buildconfig yaml with your RedHat account login credentials.

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/qat/qatlib_build.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/qat/qatlib_build.yaml
```

* Create SCC intel-qat-scc for Intel QAT based workload, if this SCC is not created

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/security/qatlib_scc.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/security/qatlib_scc.yaml
```
* Create the intel-qat service account to use intel-qat-scc

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/security/qatlib_rbac.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/security/qatlib_rbac.yaml
```

* Deploy the qatlib workload job with intel-qat service account

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/qat/qatlib_job.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/qat/qatlib_job.yaml
```

* Check the results.
Expand Down
4 changes: 2 additions & 2 deletions tests/l2/sgx/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,13 +2,13 @@
This [SampleEnclave](https://github.com/intel/linux-sgx/tree/master/SampleCode/SampleEnclave) application workload from the Intel SGX SDK runs an Intel SGX enclave utilizing the EPC resource from the Intel SGX provisioning.
* Build the container image.
```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/sgx/sgx_build.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/sgx/sgx_build.yaml
```

* Deploy and run the workload.

```
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/sgx/sgx_job.yaml
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/sgx/sgx_job.yaml
```

* Check the results.
Expand Down

0 comments on commit 4edde59

Please sign in to comment.