Subject: Re: [openstack-dev] [tripleo] Mistral Workflow for
deriving THT parameters
On 01/04/2017 09:13 AM, Saravanan KR wrote:
The aim of this mail is to ease the DPDK deployment with TripleO. I
would like to see if the approach of deriving THT parameter based on
introspection data, with a high level input would be feasible.
Let me brief on the complexity of certain parameters, which are
related to DPDK. Following parameters should be configured for a good
performing DPDK cluster:
* NeutronDpdkCoreList (puppet-vswitch)
* ComputeHostCpusList (PreNetworkConfig , puppet-vswitch) (under review)
* NovaVcpuPinset (puppet-nova)
* NeutronDpdkSocketMemory (puppet-vswitch)
* NeutronDpdkMemoryChannels (puppet-vswitch)
* ComputeKernelArgs (PreNetworkConfig ) (under review)
* Interface to bind DPDK driver (network config templates)
The complexity of deciding some of these parameters is explained in
the blog , where the CPUs has to be chosen in accordance with the
NUMA node associated with the interface. We are working a spec , to
collect the required details from the baremetal via the introspection.
The proposal is to create mistral workbook and actions
(tripleo-common), which will take minimal inputs and decide the actual
value of parameters based on the introspection data. I have created
simple workbook  with what I have in mind (not final, only
wireframe). The expected output of this workflow is to return the list
of inputs for "parameter_defaults", which will be used for the
deployment. I would like to hear from the experts, if there is any
drawbacks with this approach or any other better approach.
hi, I am not an expert, I think John (on CC) knows more but this looks
like a good initial step to me.
once we have the workbook in good shape, we could probably integrate it
in the tripleo client/common to (optionally) trigger it before every
would you be able to join the PTG to help us with the session on the
overcloud settings optimization?
GPG KEY: 08D733BA
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]