initcontainer enables vfs and configures vfs
- only first pf is used to configure a vf
- only one vf is configured from the pf
add dlb-initcontainer kustomize overlay
update CRD to have initImage
implment operator to run initcontainer
update e2e test to run initcontainer overlay
update envtest to test initimage
Signed-off-by: Hyeongju Johannes Lee <hyeongju.lee@intel.com>
We had to switch to debian unstable earlier due to a
mismatch in glibc versions in the debian-unstrable-slim and
debian-testing-slim images and Debian package repositories.
This issue has been fixed:
https://github.com/debuerreotype/docker-debian-artifacts/issues/168
so we can switch back.
Due to a glibc version mismatch in the debian repos and the
unstable-slim and testing-slim docker image 3 CI jobs have been failing
for some time. The issue was fixed by switching to testing-slim base image
and started again when the bug was introduced to the image.
Using testing-slim image as a base should fix the issue.
Signed-off-by: Ed Bartosh <eduard.bartosh@intel.com>
Due to a glibc version mismatch in the debian repos and the
unstable-slim docker image 3 CI jobs have been failing last several days.
Using testing-slim image as a base should fix the issue.
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>
Run only one test command for VF setup as the second one
usually fails with Error: DLB2_ST_DOMAIN_RESET_FAILED.
This issue has been reported to DLB developers.
Signed-off-by: Ed Bartosh <eduard.bartosh@intel.com>
- used different pods for PF and VF workloads
- increased waiting timeout to 200s
- used 'epoll' waiting mode for test apps
- decreased amount of packets from 128 to 8 for test apps
- output pod logs
- done small code optimisations
Signed-off-by: Ed Bartosh <eduard.bartosh@intel.com>
QAT_401xx is a derivative of 4xxx. Add support for that device
by including the device IDs (both PF and VF).
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
Start using the newly created NodeFeatureRule configs with SGX.
This allows to drop the custom worker config.
Additionally, split the example NFD deployment into two steps
1) plain NFD (+SGX json patches)
2) NodeFeatureRule creation
NodeFeatureRule creation is not guaranteed to succeed when it's
part of the same kustomization with the CRD creation. Users may
also have NFD already running so allowing 2) alone works better
in that scenario.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
In Debian, uuid and uuid-dev are totally different things.
accel-config build depends on uuid-dev headers but the runtime
library is libuuid1. This is part of debian:sid-slim so we can
just drop installing uuid. Moreover, it's sufficient that we
only ship accel-config source.
Also, correctly ship OPAE SDK COPYING in the final image.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
