Update the mechanism to determine the deployment type
Engine greps provided PDF for the word libvirt to determine the
type of the deployment which results in side effects. For example,
if we add a new baremetal POD with a VM based jumphost, the vendor
could be set to libvirt in jumphost section.
When we grep for vendor and look for the word libvirt, it will match
and cause engine to attempt to do virtual deployment which is not what
is intended. [0]
This change updates the existing PDF files for baremetal and virtual
PODs and uses details.type to specify the type of the POD.
Corresponding change is sent to hwconfig repository as well.
https: //gerrit.nordix.org/c/infra/hwconfig/+/4557
Change-Id: I3e6a26a42425cb5aabc7f3693fcbf72e952b4879
4 files changed