- add /usr/share/qat/calgary32 necessary for running dc test
to Dockerfile
- add e2e test for dc that runs cpa-sample with different
resource and command.
- remove openssl yaml file and use podSpec instead for cy test
- make a common func runCpaSampleCode for both cy and dc test
that have same process with a few differences
Signed-off-by: Hyeongju Johannes Lee <hyeongju.lee@intel.com>
build Intel's asynch_mode_nginx to demonstrate both HAproxy
and NGINX usage with QAT.
The expectation is both TLS keys and NGINX/HAproxy config are
provided via ConfigMaps.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
This updates the QAT driver to the latest, QAT engine to the latest,
IPSEC MB to the latest, and IPP CRYPTO to the latest. A basic test
was done in a Kata container and openssl was able to find the qat-hw
engine. I don't have a way to test if qat-sw works as the configure
parameters have changed.
Signed-off-by: Eric Adams <eric.adams@intel.com>
Add checksum checks for toybox and qat driver
Use toybox version 0.8.5 instead of 0.8.4
Update toybox-config
Signed-off-by: Hyeongju Johannes Lee <hyeongju.lee@intel.com>
This updates the QAT driver to the latest version
and updates the new driver download location on
downloadmirror. Also, this openssl container build
requires yasm so it was added as well.
Signed-off-by: Eric Adams <eric.adams@intel.com>
It was observed that qat-hw (when built right after qat-sw) is not built
correctly. Run make clean before the build (and back-up qat-sw since
clean removes it).
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
ipp-crypto repository did not provide a tag with the necessary changes
included until recently so we were using the master branch.
Now the tag was added (and master broke our build) so we move to use
it.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
Also, move from ENV to ARG to be able to override the versions
using --build-arg option.
Note: releases qat1.7.l.4.3.0-00033 and older do not have consistent
download URLs so wget'ing those will fail from this commit onwards.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
Add:
* Dockerfile that builds a container with OpenSSL 1.1.1 + QAT Engine
* Sample openssl-qat-engine-pod deployment yaml
The demo deployment yaml has the following dependencies:
* kata-runtime is installed and registered as the untrusted workload
handler
* QAT virtual function device configuration(s) (from QAT_Engine repo) are
available in /etc for the target hardware.
TODOs:
* readme.md
* move to RuntimeClass
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>