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>
This change:
* adds cloning and building of QAT-enabled DPDK to the Dockerfile
* disables unnecessary compilation of DPDK kernel modules which depend on the host kernel version
* fixes issue with missing ./resolv.conf file and dpdk directory
* removes installation of unnecessary yum packages
Added alternative builder for project images: buildah
https://github.com/containers/buildah
Considering that some of our plugins use CRI-O runtime it could be
a good idea to get rid of docker as a builder. It should allow us
not to run docker daemon at all, even for build purposes.
Kubernetes also goes this way encouraging users to switch to CRI
runtimes (CRI-O and containerd), so having non-docker builds supported
looks good from this perspective too.
Added screencast.sh script that generates asciinema screencast
for the FPGA demo "Intel FPGA Plugin for Kubernetes".
The screencast demonstrates build and deployment of the
FPGA plugin in orchestration programmed mode.
- To ensure that the device plugin continues to run in case a certain QAT device family is not detected on the node
- Updated the extended resource name to qat/generic in demo/crypto-perf-dpdk-pod-requesting-qat.yaml file
- Added explicit check for QAT device ID to avoid counting other DPDK bound devices as QAT devices
Docker documentation recommends configuring proxy in
a Docker client configuration file ~/.docker/config.json for Docker
version >= 17.07: https://docs.docker.com/network/proxy/
Using --build-arg for this purpose is not recommended, hence
removing.
