Saravanan KR f9e099f218 Ensure node is rebooted before enabling DPDK ... In the PreNetworkConfig, the order of resources sent to os-collect-config changed after introducing vhost user resource. The current order is 1. HostParametersDeployment 2. DpdkVhostGroupDeployment 3. RebootDeployment and EnableDpdkDeployment Here the expectation is that RebootDeployment should be completed before enabling DPDK, but since both are provided at the same time to os-collect-config, DPDK is enabled first. The reson is RebootDepolyment is having signal transport as NONE and EnableDpdkDeployment is moved after reboot because of ovs2.7 change of restart vswitchd, when DPDK is enabled. This is causing the a failure. This patch modifies the order as below: 1. HostParametersDeployment and DpdkVhostGroupDeployment 2. RebootDeployment and RebootEnsureDeployment 3. EnableDpdkDeployment Change-Id: I5db52d5dd833833c989532931baea8fac03f9cb7		2018-02-13 11:26:39 +05:30
..
ansible_host_config.yaml	Replace hardcoded profile name with _TUNED_PROFILE_NAME_	2018-01-16 16:20:18 +01:00
config_then_reboot.yaml	Change template names to queens	2017-11-23 10:15:32 +01:00
host_config_and_reboot.yaml	Ensure node is rebooted before enabling DPDK	2018-02-13 11:26:39 +05:30