intel-device-plugins-for-ku.../cmd/fpga_crihook
2020-01-29 17:17:06 +02:00
..
testdata fpga_plugin: support in-tree kernel driver 2019-08-24 18:27:15 +03:00
main_test.go crihook: simplified NewHookEnv signature 2019-09-16 12:56:35 +03:00
main.go fpga: rename files to make them linux-only 2020-01-29 17:17:06 +02:00
README.md fpga: fixed documentation and demo 2019-09-10 19:30:20 -05:00

Build and set up Intel FPGA prestart CRI-O hook

Dependencies

You must install and set up the following FPGA plugin modules for correct operation:

Get source code:

    $ mkdir -p $GOPATH/src/github.com/intel/
    $ cd $GOPATH/src/github.com/intel/
    $ git clone https://github.com/intel/intel-device-plugins-for-kubernetes.git

Build CRI-O hook:

    $ cd $GOPATH/src/github.com/intel/intel-device-plugins-for-kubernetes
    $ make intel-fpga-initcontainer
    $ docker images
    REPOSITORY                      TAG                                        IMAGE ID            CREATED          SIZE
    intel/intel-fpga-initcontainer  01b11d9d6d18bbe7df987a738efb20ae22ce795e   2e7586fe0fa6        0 sec ago        57.6MB
    intel/intel-fpga-initcontainer  devel                                      2e7586fe0fa6        0 sec ago        57.6MB
    ...

Ensure that CRI-O is configured to allow OCI hooks

Recent versions of CRI-O are shipped with default configuration file that prevents CRI-O to discover and configure hooks automatically. For FPGA orchestration programmed mode, the OCI hooks are the key component. Thus, please make sure that in your /etc/crio/crio.conf parameter hooks_dir is either unset (to enable default search paths for OCI hooks configuration) or contains directory /etc/containers/oci/hooks.d