Why are the playbooks compiling DPDK rather than installing it with the packages?

smart-edge-open / converged-edge-experience-kits

Source code for experience kits with Ansible-based deployment.

Apache License 2.0

37 stars 40 forks source link

Why are the playbooks compiling DPDK rather than installing it with the packages? #11

Closed nicolacdnll closed 4 years ago

nicolacdnll commented 4 years ago

As the title says, why are the playbook compiling DPDK and not installing the packages?

Could that be changed or would it break something? FYI: I'm looking at an OnPrems deployment.

Thanks!

amr-mokhtar commented 4 years ago

Will it make any difference?

n-oliver commented 4 years ago

1) Compile times are probably inconveniently long. 2) Some users were running into build errors due to conflicts in library versions.

nicolacdnll commented 4 years ago

@amr-mokhtar If there is no difference in terms of results (e.g., extra features/performance benefit), I see no reason why one should compile DPDK rather than install the packages. That's why I'm asking.

amr-mokhtar commented 4 years ago

DPDK has a hard dependency on the kernel version, and accordingly when a user decides to change the kernel version, DPDK will break. Also, NTS requires DPDK source files to build and similarly for OVS-DPDK.

amr-mokhtar commented 4 years ago

Closing issue due to inactivity..