From 9b3b1c6358b64a81726bfa23c5f16007859dcf75 Mon Sep 17 00:00:00 2001 From: Jaganathan Palanisamy Date: Wed, 5 Jul 2017 06:57:46 -0400 Subject: Workflow input parameter update in plan-environment derive_parameters workflow input parameter needs to be changed as num_phy_cores_per_numa_node_for_pmd instead of number_of_pmd_cpu_threads_per_numa_node. The performance varies based on the physical core rather than the logical CPUs. Which means, user should be able to decide the number of physical cores, which is proportional to data rate. Implements: blueprint tripleo-derive-parameters Change-Id: I056fb330a17e647ab527e8bccd52bdf5e77067b6 --- plan-samples/README.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'plan-samples/README.rst') diff --git a/plan-samples/README.rst b/plan-samples/README.rst index 44b9d0cd..b3c2d1df 100644 --- a/plan-samples/README.rst +++ b/plan-samples/README.rst @@ -15,8 +15,8 @@ commands. The sample format to provide the workflow specific parameters:: workflow_parameters: tripleo.derive_params.v1.derive_parameters: # DPDK Parameters - number_of_pmd_cpu_threads_per_numa_node: 2 + num_phy_cores_per_numa_node_for_pmd: 2 All the parameters specified under the workflow name will be passed as -``user_input`` to the workflow, while invoking from the tripleoclient. \ No newline at end of file +``user_input`` to the workflow, while invoking from the tripleoclient. -- cgit 1.2.3-korg