summaryrefslogtreecommitdiffstats
path: root/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml
diff options
context:
space:
mode:
authorMiruna Paun <Miruna.Paun@enea.com>2019-05-15 17:27:34 +0200
committerMartin Borg <martin.borg@enea.com>2019-05-16 11:16:48 +0200
commitcdfd320516250acdc5d3a9b11b07a066262ad849 (patch)
tree89a984f48fdb0cd72c23017a02919d2596a84742 /doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml
parente0e4fa4f73db0fbd803b60b4368adbcb3667912e (diff)
downloadel_releases-nfv-access-cdfd320516250acdc5d3a9b11b07a066262ad849.tar.gz
Add Content in all remaining chapters + basic formatting.
Content proofing to follow in new patches. Change-Id: I3439ad81e05eef5b77fbd437e0aba635db7923c9
Diffstat (limited to 'doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml')
-rw-r--r--doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml112
1 files changed, 98 insertions, 14 deletions
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml
index 0f72709..8b98ca2 100644
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml
@@ -2,33 +2,117 @@
2<chapter id="components"> 2<chapter id="components">
3 <title>Components</title> 3 <title>Components</title>
4 4
5 <para>An overview of the Enea NFV Access solution and the uCPE Manager in
6 cooperation with the Automation Framework and Test Harness, will be
7 presented in detail.</para>
8
9 <figure>
10 <title>Component Overview</title>
11
12 <mediaobject>
13 <imageobject>
14 <imagedata align="center" fileref="images/autofw_testh_overview.png"
15 scale="40" />
16 </imageobject>
17 </mediaobject>
18 </figure>
19
5 <section id="enfva_solution"> 20 <section id="enfva_solution">
6 <title>Enea NFV Access Solution</title> 21 <title>Enea NFV Access Solution</title>
7 22
8 <para></para> 23 <para>The Enea NFV Access Solution is comprised of the Enea NFV Access
9 24 Runtime Platform and the Enea uCPE Manager.</para>
10 <section id="eucpe_manager"> 25
11 <title>Enea uCPE Manager</title> 26 <section id="eucpe_manager">
27 <title>Enea uCPE Manager</title>
28
29 <para>The Enea uCPE Manager application needs to be installed on a
30 supported platform. Upon installation, the system will be set up to
31 manage Enea NFV Access "devices", these are the virtualized CPE devices
32 used in testing.</para>
33
34 <para>For more on Enea uCPE Manager installation instructions, please
35 refer to chapter "Getting Started with Enea uCPE Manager" from the Enea
36 NFV Access Getting Started manual.</para>
37 </section>
38
39 <section id="ena_plat">
40 <title>Enea NFV Access</title>
41
42 <para>One or more NFV Access devices are required as target hosts
43 running the VNF(s). The NFV Access device is known to the uCPE Manager
44 as the "VcpeAgent" device module.</para>
45
46 <para>Adding a VcpeAgent device can be done via one of two
47 methods:</para>
12 48
13 <para></para> 49 <itemizedlist>
14 </section> 50 <listitem>
15 51 <para>Through the uCPE Manager GUI. Add the device using the
16 <section id="ena_plat"> 52 appropriate parameters by launching the UI under Devices -&gt;
17 <title>Enea NFV Access</title> 53 Manage in the main screen.</para>
54 </listitem>
18 55
19 <para></para> 56 <listitem>
20 </section> 57 <para>REST API. Invoke the uCPE Manager REST API to add a
58 device.</para>
59 </listitem>
60 </itemizedlist>
61
62 <para>For more on Enea NFV Access installation instructions, please
63 refer to chapter "Getting Started with Enea NFV Access" from the Enea
64 NFV Access Getting Started manual.</para>
65 </section>
21 </section> 66 </section>
22 67
23 <section id="automation"> 68 <section id="automation">
24 <title>Automation Framework</title> 69 <title>Automation Framework</title>
25 70
26 <para></para> 71 <para>Testing can be performed by running the available Python scripts
72 against the uCPE Manager REST API (Python samples supplied). This can be
73 done by using the Python scripts individually or by using the Python
74 unit-test suite that is able to automatically run test-cases defined for
75 each available Python script.</para>
76
77 <para>In either case, it is desirable to use a third system (instead of
78 running the tests on the same system as the uCPE Manager) in order to
79 ensure that uCPE Manager is setup and installed correctly in terms of
80 allowing external users to access it and use it effectively.</para>
27 </section> 81 </section>
28 82
29 <section id="harness"> 83 <section id="harness">
30 <title>Test Harness</title> 84 <title>Test Harness</title>
31 85
32 <para></para> 86 <para>The Test Harness (TH) provides a way for driving configuration with
87 Ansible Playbooks, by running the python modules from the Automation
88 Framework (AF) and by direct connection over SSH to the boards that run
89 the Enea NFV Access solution.</para>
90
91 <para>The Test Harness includes an automated test suite that
92 contains:</para>
93
94 <itemizedlist>
95 <listitem>
96 <para>VNF, Device and Network Smoke Test Cases. A sample test suite
97 that acts as basic smoke tests for the Enea NFV Access Solution and
98 also as a sanity-check test suite for the AF and TH.</para>
99 </listitem>
100
101 <listitem>
102 <para>VNF Deployment and Lifecycle. A sample test suite that verifies
103 the instantiation, lifecycle control and destruction of a VNF for the
104 Enea NFV Access Solution.</para>
105 </listitem>
106
107 <listitem>
108 <para>Service Creation and Lifecycle: A sample test suite that
109 contains complex test cases showcasing service creation and lifecycle
110 management.</para>
111 </listitem>
112 </itemizedlist>
113
114 <para>For details about the test suites or test cases please refer to the
115 chapter "Sample Test Cases" from the Enea NFV Access System Test
116 Specification document.</para>
33 </section> 117 </section>
34</chapter> \ No newline at end of file 118</chapter> \ No newline at end of file