Summary
Add VPP coredumps.
In order to debug a crash of VPP, it is required to provide a coredump file, which allows backtracing of the VPP issue.
Add this option configurable.
Use case
Collect debug information
Additional information
https://fdio-vpp.readthedocs.io/en/latest/usecases/contiv/CORE_FILES.html
Proposed CLI
set vpp settings unix coredump directory /vyos/world
Additional packages: gdb, vpp-dbg
Care to elaborate on why this was denied?
Or is the reason to not wanting gdb and vpp-dbg to be part of the image?
Because my take from https://fdio-vpp.readthedocs.io/en/latest/usecases/contiv/CORE_FILES.html is that these packages are not needed to perform the dump.
And I agree, packages who arent strictly necessary shouldnt be installed. If an admin want to perform gdb etc then make a custom image or analyze the dump on a different box.
It seems that the needed config changes to enable coredump should be doable through set vpp settings unix coredump directory /vyos/world or similar as VyOS config option.
My proposed CLI was in https://github.com/vyos/vyos-vpp/pull/20
The question to @zsdc is why he doesn't like it...
I don't want to waste any more time on a feature that won't be accepted.