Hide Forgot
Created attachment 1208885 [details] dpdk-first-boot.yaml file Description of problem: RHOS 10 deployment missing post configuration heat yaml scripts for DPDK configuration. The deployment of DPDK feature supported by RHOS 10, should execute PostDeploySteps in additional to the heat templates in order to properly configure the DPDK feature. Version-Release number of selected component (if applicable): RHOS 10 Product version: 10 Product core version: 10 Product core build: 2016-10-06.1 rpm -qa |grep tripleo openstack-tripleo-0.0.1-0.20160916135259.4de13b3.el7ost.noarch openstack-tripleo-common-5.2.1-0.20160930181658.40ad7e5.el7ost.noarch puppet-tripleo-5.2.0-1.el7ost.noarch openstack-tripleo-puppet-elements-5.0.0-0.20160929220627.200d011.el7ost.noarch openstack-tripleo-heat-templates-5.0.0-0.20161003064637.d636e3a.1.1.el7ost.noarch openstack-tripleo-image-elements-5.0.0-0.20161002235922.14e1f41.el7ost.noarch python-tripleoclient-5.2.0-1.el7ost.noarch openstack-tripleo-ui-1.0.3-0.20160930145215.f7297c3.el7ost.noarch Actual results: The heat yaml post config scripts should exists within the /usr/share/openstack-tripleo-heat-templates/extraconfig directory. Expected results: The heat yaml post config scripts are missing Additional info: dpdk-fist-boot.yaml and dpdk-post-install.yaml files are attached.
Created attachment 1208886 [details] dpdk-post-install.yaml file
Correct.
Is this planned to land in upstream tripleo-heat-templates? I don't see a reason for including this as a downstream only patch.
(In reply to Mike Burns from comment #5) > Is this planned to land in upstream tripleo-heat-templates? I don't see a > reason for including this as a downstream only patch.
(In reply to Yariv from comment #6) > (In reply to Mike Burns from comment #5) > > Is this planned to land in upstream tripleo-heat-templates? I don't see a > > reason for including this as a downstream only patch. We planned to do post-install.yaml in documentation.
The templates are being modified for OSP11 to simplify, progress in BZ - https://bugzilla.redhat.com/show_bug.cgi?id=1384845.
This bug cannot be fixed for Ocata (upstream), as the first boot for configuring kernel args are will be removed and added as PreNetworkConfig, which cannot be backported as it has dependency on os-net-config flow change.