summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authormrpa <mrpa@enea.se>2020-01-09 15:57:11 +0100
committermrpa <mrpa@enea.se>2020-01-09 16:04:11 +0100
commitc2982cf02c1c2b4fbcadce673c1f5deffcbe4417 (patch)
treec46c402dd8f9f3f97496b1e5c3ad15e20255bfec
parent1af63679f4360f1301efcc28e540005227821f81 (diff)
downloadel_releases-nfv-access-c2982cf02c1c2b4fbcadce673c1f5deffcbe4417.tar.gz
Added 3.1.9 Network Config DPDK.
Change-Id: I0bc55993e6c84ccba17a530f00502b9949831649
-rw-r--r--doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml36
1 files changed, 36 insertions, 0 deletions
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml b/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml
index cac0e8a..eecd3b4 100644
--- a/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml
+++ b/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml
@@ -333,6 +333,42 @@ bridge=&lt;Bridge-name&gt;"</programlisting></para>
333 not exist: <programlisting># debug 333 not exist: <programlisting># debug
334&lt;Bridge-name&gt; bridge not found!</programlisting></para> 334&lt;Bridge-name&gt; bridge not found!</programlisting></para>
335 </section> 335 </section>
336
337 <section id="config_dpdk">
338 <title>Network - Configure_DPDK</title>
339
340 <para><emphasis role="bold">Description:</emphasis> Enabling or
341 Disabling the DPDK to a device. For details please refer to:</para>
342
343 <itemizedlist>
344 <listitem>
345 <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/network/configDPDK.yml</filename>.</para>
346 </listitem>
347
348 <listitem>
349 <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/network/configDPDK.py</filename>.</para>
350 </listitem>
351 </itemizedlist>
352
353 <para><emphasis role="bold">Precondition: </emphasis></para>
354
355 <para>A device must have been previously added to the uCPE Manager
356 instance.</para>
357
358 <para><emphasis role="bold">Action:</emphasis> Run the
359 <filename>configDPDK.yml</filename> Ansible Playbook with the
360 <literal>&lt;Device-name&gt;</literal> and
361 <literal>&lt;enable/disable&gt;</literal> as extra-vars:<programlisting>ansible-playbook playbooks/configDPDK.yml -e "device=&lt;Device-name&gt; \
362state=&lt;enable/disable&gt;"</programlisting></para>
363
364 <para><emphasis role="bold">Result:</emphasis> Output of the test case
365 run using the Test Harness:</para>
366
367 <para><programlisting># Configure DPDK task result
368DEBUG: Set DPDK state to &lt;enable/disable&gt;</programlisting><emphasis
369 role="bold">Note:</emphasis> DPDK use cannot be disabled if DPDK
370 interfaces are configured. The task will fail in this case.</para>
371 </section>
336 </section> 372 </section>
337 373
338 <section id="vnf_deploy_lifecycle"> 374 <section id="vnf_deploy_lifecycle">