summaryrefslogtreecommitdiffstats
path: root/doc/book-enea-edge-automation-user-guide/doc/components.xml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/book-enea-edge-automation-user-guide/doc/components.xml')
-rw-r--r--doc/book-enea-edge-automation-user-guide/doc/components.xml11
1 files changed, 7 insertions, 4 deletions
diff --git a/doc/book-enea-edge-automation-user-guide/doc/components.xml b/doc/book-enea-edge-automation-user-guide/doc/components.xml
index d2538b8..613644a 100644
--- a/doc/book-enea-edge-automation-user-guide/doc/components.xml
+++ b/doc/book-enea-edge-automation-user-guide/doc/components.xml
@@ -24,7 +24,7 @@
24 24
25 <para>For more details about Enea Edge Management installation, see <olink 25 <para>For more details about Enea Edge Management installation, see <olink
26 targetdoc="book_enea_edge_getting_started" 26 targetdoc="book_enea_edge_getting_started"
27 targetptr="install_ucpe_mg">Installing the Enea Edge Management in the 27 targetptr="install_ucpe_mg">Installing the Enea Edge Management application in the
28 <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml" 28 <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
29 xmlns:xi="http://www.w3.org/2001/XInclude" 29 xmlns:xi="http://www.w3.org/2001/XInclude"
30 xpointer="element(book_enea_edge_getting_started/1)" /></olink> 30 xpointer="element(book_enea_edge_getting_started/1)" /></olink>
@@ -36,10 +36,10 @@
36 36
37 <para>One or more uCPE devices running the Enea Edge Runtime 37 <para>One or more uCPE devices running the Enea Edge Runtime
38 are required as hosts, to run the VNFs. The uCPE device is 38 are required as hosts, to run the VNFs. The uCPE device is
39 known to the Enea Edge Management as the <literal>VcpeAgent</literal> device 39 known to the Enea Edge Management application as the <literal>VcpeAgent</literal> device
40 module.</para> 40 module.</para>
41 41
42 <para>Before running any use case with the Enea Edge Automation, the uCPE devices have to be added to the Enea Edge Management.</para> 42 <para>Before running any use case with the Enea Edge Automation, the uCPE devices have to be added to the Enea Edge Management application.</para>
43 43
44 <para>Adding a <literal>VcpeAgent</literal> device can be done:</para> 44 <para>Adding a <literal>VcpeAgent</literal> device can be done:</para>
45 45
@@ -62,15 +62,18 @@
62 xpointer="element(book_enea_edge_getting_started/1)" /></olink> 62 xpointer="element(book_enea_edge_getting_started/1)" /></olink>
63 Manual.</para> 63 Manual.</para>
64 </section> 64 </section>
65
65 <section id="automation"> 66 <section id="automation">
66 <title>Enea Edge Automation</title> 67 <title>Enea Edge Automation</title>
68
67 <para>Enea Edge Automation has two compoments: Automation Framework and Test Harness. 69 <para>Enea Edge Automation has two compoments: Automation Framework and Test Harness.
68 It provides Python scripts using Enea Edge Management REST API and Ansible Playbooks.</para> 70 It provides Python scripts using Enea Edge Management REST API and Ansible Playbooks.</para>
71
69 <para>The Automation Framework component provides a Python unit-test suite that runs automatically the 72 <para>The Automation Framework component provides a Python unit-test suite that runs automatically the
70 test-cases defined for each Python script.</para> 73 test-cases defined for each Python script.</para>
71 74
72 <para>It is recommended to use a different host for running the tests, in 75 <para>It is recommended to use a different host for running the tests, in
73 order to allow external users to access and use the Enea Edge Management 76 order to allow external users to access and use the Enea Edge Management application
74 effectively.</para> 77 effectively.</para>
75 78
76 <para>The Test Harness component provides a way for driving configuration with 79 <para>The Test Harness component provides a way for driving configuration with