From 61dbe22ebb42279e388f53c557c267d43a774ed2 Mon Sep 17 00:00:00 2001 From: Todd Malsbary Date: Thu, 1 Oct 2020 14:17:59 -0700 Subject: Build and deploy sriov module only on supported hosts. Building on the target host fixes a couple issues: - In the containerized installer, the container image does not include the necessary kernel headers to build the module. - The build and target host must have the same kernel version. There is no guarantee of this. The deploy uses NFD, similar to the QAT playbook. Issue-ID: MULTICLOUD-1228 Signed-off-by: Todd Malsbary Change-Id: I58705b73b8ce6d381b4649d5a20b8644e51e1b13 --- kud/hosting_providers/containerized/installer.sh | 2 ++ 1 file changed, 2 insertions(+) (limited to 'kud/hosting_providers/containerized') diff --git a/kud/hosting_providers/containerized/installer.sh b/kud/hosting_providers/containerized/installer.sh index ae16b1dd..c18829a5 100755 --- a/kud/hosting_providers/containerized/installer.sh +++ b/kud/hosting_providers/containerized/installer.sh @@ -119,6 +119,8 @@ function install_addons { ansible-playbook $verbose -i \ $kud_inventory $kud_playbooks/configure-kud.yml | \ tee $cluster_log/setup-kud.log + # The order of KUD_ADDONS is important: some plugins (sriov, qat) + # require nfd to be enabled. for addon in ${KUD_ADDONS:-virtlet ovn4nfv nfd sriov cmk $plugins_name}; do echo "Deploying $addon using configure-$addon.yml playbook.." ansible-playbook $verbose -i \ -- cgit 1.2.3-korg