VPP folks, Currently, CSIT is 'pegging' to a particular DPDK version.
https://git.fd.io/csit/tree/DPDK_STABLE_VER This is fragile and bit us this week. Its been recognized that such pegging is undesirable, and should be removed, but it was done to solve a problem for which an alternate solution needs to be found. CSIT builds all the vpp packages and then scp copies them to the boxes where the tests are run. The problem is, for reasons of efficiency, vpp typically *doesn't* build dpdk packages unless there is a change in version, and so generally doesn't build those packages. To work around that, CSIT uses DPDK_STABLE_VER to peg a version of the dpdk packages and fetches them from nexus. It's been agreed in CSIT that we should be taking our queues from the vpp repo on these matters, so we wanted to see how the vpp-dev folks would like it to be solved. Possibilities that come immediately to mind: 1) Point CSIT to (or create and point CSIT to) a simple clean way to get the DPDK version from the vpp/ tree. It would be good for this to be some kind of clean contract with low probability of simply changing unexpectedly. 2) Point CSIT to (or create and point CSIT to) a simple clean way to force DPDK build (this has a cost for verify times, so I suspect will not be the desired outcome). Ed
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
