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>
accel-config v3.4.3 dropped libkmod, libudev dependencies, update
initcontainer to v3.4.3 and drop local customizations / workarounds.
Signed-off-by: Oleg Zhurakivskyy <oleg.zhurakivskyy@intel.com>
Remove libdlb-demo yaml that should have been dropped since dlb-libdlb-demo-pod yaml file replaced it
Signed-off-by: Hyeongju Johannes Lee <hyeongju.lee@intel.com>
The provisioning config can be optionally stored in the ProvisioningConfig
configMap which is then passed to initcontainer through the volume mount.
There's also a possibility for a node specific congfiguration through
passing a nodename via NODE_NAME into initcontainer's environment
and passing a node specific profile via configMap volume mount.
Signed-off-by: Oleg Zhurakivskyy <oleg.zhurakivskyy@intel.com>
