QAT testing/deployment updates

[mythi]

As we work to update the CI setup, I propose we make QAT Gen4 as the default and skip testing on older systems. With that, the following updates should be made:

• make deployments/qat_dpdk_app usable for Gen4 and drop all the testing kustomization
• update e2e/qat to work with previous
• enable all tests (dpdk compress/crypto + openssl + cpa_sample_code)
• move openssl-qat-engine image to Ubuntu 24.04 #1705

[hj-johannes-lee]

Maybe, then, we do not need the open pr.
Let me just change the pr to make this issue solved. Do you think it's ok?

[mythi]

that works OK to me

[mythi]

enable all tests (dpdk compress/crypto + openssl + cpa_sample_code)

@hj-johannes-lee I think we can now finish this final task and add test cases for QAT Engine. Fox example: a simple k8s Job with two containers each running different algo would be sufficient.

[hj-johannes-lee]

@hj-johannes-lee I think we can now finish this final task and add test cases for QAT Engine. Fox example: a simple k8s Job with two containers each running different algo would be sufficient.

I think I have actually not understood what we need to add until now.
We have now crypto-perf image that is used for dpdk crypto-perf and compress-perf
and the image openssl-qat-engine where we run cpa_sample_code.

What is missing among

dpdk compress/crypto + openssl + cpa_sample_code

?

[hj-johannes-lee]

I think what is missing is the openssl part?

I have no idea why we have used the image name openssl-qat-engine though the cpa-sample_code is a part of qatlib..?

[mythi]

why we have used the image name openssl-qat-engine though the cpa-sample_code is a part of qatlib..?

We have maintained a reference container image build for QAT Engine since day 0 but it wasn't possible to add it to the tests until e2e-spr. cpa_sample_code worked for basic tests even before e2e-spr so we just re-used the reference openssl-qat-engine build for it instead for creating a completely new image.