Skip to content

Commit 4edde59

Browse files
authored
Merge pull request #276 from chaitanya1731/release-v1.3.0
Updated release version v1.3.0
2 parents fd472a1 + 4e0bcd6 commit 4edde59

File tree

11 files changed

+23
-23
lines changed

11 files changed

+23
-23
lines changed

device_plugins/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Follow the steps below to install Intel Device Plugins Operator using OpenShift
2323
### Installation via command line interface (CLI)
2424
Apply the [install_operator.yaml](/device_plugins/install_operator.yaml) file:
2525
```
26-
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/device_plugins/install_operator.yaml
26+
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/device_plugins/install_operator.yaml
2727
```
2828

2929
### Verify Installation via CLI

device_plugins/deploy_gpu.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
## Create CR via CLI
1515
Apply the CR yaml file:
1616
```
17-
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/device_plugins/gpu_device_plugin.yaml
17+
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/device_plugins/gpu_device_plugin.yaml
1818
```
1919

2020
## Verify via CLI

device_plugins/deploy_qat.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
## Create CR via CLI
1515
Apply the CR yaml file:
1616
```
17-
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/device_plugins/qat_device_plugin.yaml
17+
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/device_plugins/qat_device_plugin.yaml
1818
```
1919

2020
## Verify via CLI

device_plugins/deploy_sgx.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
## Create CR via CLI
1515
Apply the CR yaml file:
1616
```
17-
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/device_plugins/sgx_device_plugin.yaml
17+
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/device_plugins/sgx_device_plugin.yaml
1818
```
1919

2020
## Verify via CLI

e2e/inference/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ To enable the interactive mode, the OpenVINO notebook CR needs to be created and
3636

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

4242
1. Navigate to `openvino-notebooks` ImageStream and add the above created `AcceleratorProfile` key to the annotation field, as shown in the image below:

kmmo/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ $ oc label node <node_name> intel.feature.node.kubernetes.io/dgpu-canary=true
5757

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

6363
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.

machine_configuration/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Any contribution in this area is welcome.
2424
* Turn on `intel_iommu` kernel parameter and load `vfio_pci` at boot for QAT provisioning
2525

2626
```
27-
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/machine_configuration/100-intel-qat-intel-iommu-on.yaml
27+
$ 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
2828
```
2929

3030
Note: This will reboot the worker nodes when changing the kernel parameter through MCO.

nfd/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -14,12 +14,12 @@ Note: As RHOCP cluster administrator, you might need to merge the NFD operator c
1414

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

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

2525
## Verification

tests/l2/dgpu/README.md

+8-8
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ This workload runs [clinfo](https://github.com/Oblomov/clinfo) utilizing the i91
66
* Build the workload container image.
77

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

1212
* Deploy and execute the workload.
1313

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

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

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

5353
* Deploy and execute the workload.
5454

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

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

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

102102
* Deploy and execute the workload.
103103

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

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

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

169169
* Deploy and execute the workload.
170170

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

175175
* Check the results.

tests/l2/qat/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -6,25 +6,25 @@ This workload runs [qatlib](https://github.com/intel/qatlib) sample tests using
66
Please replace the credentials in buildconfig yaml with your RedHat account login credentials.
77

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

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

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

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

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

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

3030
* Check the results.

tests/l2/sgx/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,13 @@
22
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.
33
* Build the container image.
44
```
5-
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/tests/l2/sgx/sgx_build.yaml
5+
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/v1.3.0/tests/l2/sgx/sgx_build.yaml
66
```
77

88
* Deploy and run the workload.
99

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

1414
* Check the results.

0 commit comments

Comments
 (0)