Install Intel FPGA device plugin

[dell]

Install Intel FPGA device plugin

[lwilson]

Looks like we can avoid CRI-O if we are willing to not have Kubernetes automatically program the FPGAs (https://github.com/intel/intel-device-plugins-for-kubernetes#fpga-device-plugin).

[lwilson]

The RPM for the Intel OPAE driver is on GitHub. Version 1.4.0 here: https://github.com/OPAE/opae-sdk/releases/download/1.4.0-1/opae-intel-fpga-driver-2.0.4-2.x86_64.rpm

It appears that the driver has now been upstreamed into the Linux kernel v5.6 (see https://github.com/OPAE/opae-sdk/releases/tag/1.4.1-1).

[lwilson]

It appears that the OPAE drivers on GitHub are not Intel's supported software -- that has to be downloaded from behind Intel's firewall.

At this point I do not see automated installation for Intel FPGAs as something we can plan for or pursue.

I will close this ticket.

[lwilson]

I'm re-opening this issue. I think the right approach here would be to allow the playbooks to install from a local path - this way we can install the Intel FPGA drivers and device plugin in a mostly automated fashion.

Moving from Docker to CRI-O (#76) will also allow us to take full advantage of the Intel FPGA device plugins capabilities.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[lwilson]

Keeping this one alive - I'm working with Intel to make the deployment process smoother.

I think for the moment the plan will have to be:

1. Have the user download the FPGA drivers (in order to accept the click-through license)
2. Provide a variable with the path to the driver tarball
3. Have Omnia deploy from tarball

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.