summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat
-rw-r--r--doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml18
-rw-r--r--doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml17
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml69
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml238
-rw-r--r--doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml44
-rw-r--r--doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml19
-rw-r--r--doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml39
-rw-r--r--doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml31
8 files changed, 288 insertions, 187 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 2917b1a..3439a64 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
@@ -46,10 +46,12 @@
46 <para>One or more uCPE devices running the Enea NFV Access Run Time 46 <para>One or more uCPE devices running the Enea NFV Access Run Time
47 Platform are required as hosts to run the VNF(s). The uCPE device is 47 Platform are required as hosts to run the VNF(s). The uCPE device is
48 known to the uCPE Manager as the "VcpeAgent" device module.</para> 48 known to the uCPE Manager as the "VcpeAgent" device module.</para>
49 49
50 <note><para>Before running any use case with the Automation Framework or 50 <note>
51 the Test Harness, make sure the uCPE device(s) have been added to 51 <para>Before running any use case with the Automation Framework or the
52 the uCPE Manager.</para></note> 52 Test Harness, make sure the uCPE device(s) have been added to the uCPE
53 Manager.</para>
54 </note>
53 55
54 <para>Adding a VcpeAgent device can be done via two methods:</para> 56 <para>Adding a VcpeAgent device can be done via two methods:</para>
55 57
@@ -124,12 +126,10 @@
124 126
125 <para>For details about the test suites or test cases please refer to 127 <para>For details about the test suites or test cases please refer to
126 chapter <olink targetdoc="book_enea_nfv_access_system_test_specification" 128 chapter <olink targetdoc="book_enea_nfv_access_system_test_specification"
127 targetptr="sample_testcases">Sample Test Cases in <xi:include 129 targetptr="sample_testcases">Sample Test Cases in the<xi:include
128 href="../../s_docbuild/olinkdb/pardoc-names.xml" 130 href="../../s_docbuild/olinkdb/pardoc-names.xml"
129 xmlns:xi="http://www.w3.org/2001/XInclude" 131 xmlns:xi="http://www.w3.org/2001/XInclude"
130 xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>.</para> 132 xpointer="element(book_enea_nfv_access_system_test_specification/1)" /></olink>
131 133 Manual.</para>
132 <remark>this olink needs to be fixed it points to getting started not the
133 test spec manual, an olinkdb update is needed to know why.</remark>
134 </section> 134 </section>
135</chapter> \ No newline at end of file 135</chapter> \ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml
index 68e6f12..8a62b3b 100644
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml
@@ -30,9 +30,12 @@
30 <note> 30 <note>
31 <para>The Automation Framework and Test Harness installation may be done 31 <para>The Automation Framework and Test Harness installation may be done
32 on the same machine used for uCPE Manager installation, although this is 32 on the same machine used for uCPE Manager installation, although this is
33 not encouraged. For more details see <link linkend="automation">chapter 33 not encouraged. For more details see section <olink
34 3.2</link>.<remark>what chapter of what book is this link refering 34 targetdoc="book_enea_nfv_access_auto_fw_th_user_guide"
35 to?</remark></para> 35 targetptr="automation">Automation Framework in the <xi:include
36 href="../../s_docbuild/olinkdb/pardoc-names.xml"
37 xmlns:xi="http://www.w3.org/2001/XInclude"
38 xpointer="element(book_enea_nfv_access_auto_fw_th_user_guide/1)" /></olink>.</para>
36 </note> 39 </note>
37 </section> 40 </section>
38 41
@@ -49,9 +52,11 @@
49 </imageobject> 52 </imageobject>
50 </mediaobject> 53 </mediaobject>
51 </figure>The following enviroment setup is needed for running all tests 54 </figure>The following enviroment setup is needed for running all tests
52 defined in the Enea NFV Access System Test Specification manual:</para> 55 defined in the <xi:include
53 56 href="../../s_docbuild/olinkdb/pardoc-common.xml"
54 <remark>olink to the book needed here.</remark> 57 xmlns:xi="http://www.w3.org/2001/XInclude"
58 xpointer="element(book_enea_nfv_access_system_test_specification/1)" />
59 manual:</para>
55 60
56 <para><emphasis role="bold">Lab Network 61 <para><emphasis role="bold">Lab Network
57 Requirements</emphasis><itemizedlist spacing="compact"> 62 Requirements</emphasis><itemizedlist spacing="compact">
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml
index 42e6a5e..9fe1b2b 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml
@@ -2,8 +2,14 @@
2<appendix id="appendix_four_cust"> 2<appendix id="appendix_four_cust">
3 <title>Running Enea Automation Framework tests</title> 3 <title>Running Enea Automation Framework tests</title>
4 4
5 <para>For more detailed information regarding the Automation Framework and
6 Test Harness please see the <xi:include
7 href="../../s_docbuild/olinkdb/pardoc-common.xml"
8 xmlns:xi="http://www.w3.org/2001/XInclude"
9 xpointer="element(book_enea_nfv_access_auto_fw_th_user_guide/1)" />.</para>
10
5 <para>The most relevant information from the Automation Framework and Test 11 <para>The most relevant information from the Automation Framework and Test
6 Harness structure:</para> 12 Harness structure is presented below:</para>
7 13
8 <programlisting>|---automation_framework 14 <programlisting>|---automation_framework
9| |---unittestSuite 15| |---unittestSuite
@@ -18,14 +24,14 @@
18| | |---unittestSuite.py 24| | |---unittestSuite.py
19|---lab_config 25|---lab_config
20| |---trgt-1 26| |---trgt-1
21| | |---enp4s0f0_0000_04_00_0.json
22| | |---enp4s0f1_0000_04_00_1.json
23| | |---ibm_br.json - In-band management definition. 27| | |---ibm_br.json - In-band management definition.
24| | |---lan_br_enp4s0f1.json - Lan bridge definition. 28| | |---lan_br.json - Lan bridge definition.
25| | |---trgt-1.json 29| | |---target.json
26 - Target definition - make sure to update the "address". 30 - Target definition - the "address", "deviceId", "name" and \
31 "version" must be updated.
27| | |---sfc_br.json - Service chain bridge definition. 32| | |---sfc_br.json - Service chain bridge definition.
28| | |---vnf_mgmt_br.json - VNF management bridge definition. 33| | |---vnf_mgmt_br.json - VNF management bridge definition.
34| | |---lan_nic.json - NIC definition.
29|---vnf_config 35|---vnf_config
30| |---128t 36| |---128t
31| | |---128tInstance.json - 128T instantiation - used in use case 1. 37| | |---128tInstance.json - 128T instantiation - used in use case 1.
@@ -37,16 +43,53 @@
37| | |---fortigateInstance.json - Fortigate instantiantion. 43| | |---fortigateInstance.json - Fortigate instantiantion.
38| | |---fortigate.json - Fortigate onboarding. 44| | |---fortigate.json - Fortigate onboarding.
39| | |---fortigateLicense.lic 45| | |---fortigateLicense.lic
40 - Fortigate license - replace it with a valid License file. 46 - Fortigate license - contact Fortinet to get a VNF image and license file.
41|---vnf_image 47|---vnf_image
42| |---centos_128t_with_ci.qcow2 - 128T qcow2 image. 48| |---centos_128t_with_ci.qcow2 - Contact 128 Technology to get a \
43| |---fortios.qcow2 - Fortigate qcow2 image.</programlisting> 49 VNF image and its license file.
50| |---fortios.qcow2 - Contact Fortinet to get a VNF image \
51 and its license file.</programlisting>
44 52
45 <para>Make sure to update the relevant configuration file for your setup. 53 <para>Make sure to update the relevant configuration file for your setup.
46 The essential files to consider are the target configuration 54 The essential files to consider are the uCPE Device configuration
47 (<filename>trgt-1.json</filename>), the license for the Fortigate VNF, and 55 (<filename>target.json</filename>), the license for the Fortigate VNF, and
48 the 128T cloud-init iso image matching your network.</para> 56 the 128T cloud-init iso image matching your network.</para>
49 57
50 <para>To run a test:<programlisting>&gt; cd automation_and_systemtest/automation_framework/unittestSuite 58 <para>For uCPE Device configuration (<filename>target.json</filename>)
51&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 -s</programlisting></para> 59 please change the following information, if needed, in the JSON file:</para>
60
61 <itemizedlist spacing="compact">
62 <listitem>
63 <para><literal>address</literal> - The IP address of uCPE Device.</para>
64 </listitem>
65
66 <listitem>
67 <para><literal>version</literal> - The NFVA version.</para>
68 </listitem>
69
70 <listitem>
71 <para><literal>deviceId</literal> - The device ID of uCPE Device.</para>
72 </listitem>
73
74 <listitem>
75 <para><literal>name</literal> - The name of uCPE Device.</para>
76 </listitem>
77 </itemizedlist>
78
79 <note>
80 <para>Before starting the two usecases detailed in the following appendix,
81 the uCPE Device needs to be added into the uCPE Manager.</para>
82 </note>
83
84 <para>To run a test:</para>
85
86 <programlisting>&gt; cd automation_framework/unittestSuite/
87&gt; python unittestSuite.py -u admin -p admin -H &lt;uCPEManager IP address&gt; -n \
88&lt;uCPE Device name&gt; -s &lt;Test suite&gt; -d &lt;description&gt;</programlisting>
89
90 <para>The <literal>Test suite</literal> must be one from any of the
91 following: <filename>128tDeploy.json</filename>,
92 <filename>128tCleanup.json</filename>,
93 <filename>128t_FG_SFCDeploy.json</filename>, or
94 <filename>128t_FG_SFCCleanup.json</filename>.</para>
52</appendix> \ No newline at end of file 95</appendix> \ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
index bdffa2f..2097435 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
@@ -2,200 +2,240 @@
2<appendix id="appendix_five_cust"> 2<appendix id="appendix_five_cust">
3 <title>Example Tests Results using the Automation Framework</title> 3 <title>Example Tests Results using the Automation Framework</title>
4 4
5 <programlisting>Test Host: 5 <para>In order to run the following example usecases, certain configuration
6Use Case1 - 128T 6 file entries need to be modified according to the network setup that it will
7&gt; cd automation_and_systemtest/automation_framework/unittestSuite 7 be used, for more details see the previous appendix:</para>
8&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \ 8
9 <itemizedlist spacing="compact">
10 <listitem>
11 <para>uCPE Device name: inteld1521-17</para>
12 </listitem>
13
14 <listitem>
15 <para>address: 172.24.8.62</para>
16 </listitem>
17
18 <listitem>
19 <para>version: 2.2.3</para>
20 </listitem>
21
22 <listitem>
23 <para>deviceId: inteld1521-17</para>
24 </listitem>
25 </itemizedlist>
26
27 <para><programlisting>&gt; cat lab_config/trgt-1/target.json
28{
29 "name": "inteld1521-17",
30 "description": "trgt",
31 "address": "172.24.8.62",
32 "port": "830",
33 "username": "root",
34 "password": "",
35 "certificate": null,
36 "passphrase": null,
37 "maintMode": "false",
38 "version": "2.2.3",
39 "deviceId": "inteld1521-17"
40}</programlisting>The IP address of the uCPE Manager that will be used in
41 these examples is <literal>172.24.3.92</literal>.</para>
42
43 <para>The FortiGate and 128T VNF images need to be copied into the
44 <literal>vnf_image</literal> directory. The names should be the same as
45 those described in Appendix D.</para>
46
47 <para>The FortiGate valid license file needs to be copied into the
48 <literal>vnf_config/fortigate/</literal> directory. The name should be the
49 same as that described in Appendix D.</para>
50
51 <para>The cloud init files that match the network, need to be copied into
52 the <literal>vnf_config/fortigate/</literal> and the
53 <literal>vnf_config/128t/</literal> directories respectively. The names
54 should be the same as those described in Appendix D.</para>
55
56 <section id="ap_d_uc1">
57 <title>Use-case 1: 128T VNF Router Example Use-case</title>
58
59 <programlisting>&gt; cd automation_framework/unittestSuite/
60&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
9-s 128tDeploy.json -d "128T Deployment" 61-s 128tDeploy.json -d "128T Deployment"
10 62
11Running 128T Deployment... 63Running 128T Deployment...
12 64
13test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ... 65test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ...
142020-04-15 19:04:58,037 - INFO: Wait uCPE device 662020-08-26 10:10:05,517 - INFO: Wait uCPE device
152020-04-15 19:05:29,128 - INFO: Status: Connected 672020-08-26 10:10:36,650 - INFO: Status: Connected
162020-04-15 19:05:29,128 - INFO: Done 682020-08-26 10:10:36,651 - INFO: Done
17ok 69ok
18test 002: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ... 70test 002: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ...
192020-04-15 19:05:29,154 - INFO: Bind NIC 712020-08-26 10:10:36,686 - INFO: Bind NIC
202020-04-15 19:05:30,280 - INFO: Done 722020-08-26 10:10:37,788 - INFO: Done
21ok 73ok
22test 003: Creating ibm bridge (__main__.UnittestSuite) ... 74test 003: Creating ibm bridge (__main__.UnittestSuite) ...
232020-04-15 19:05:30,302 - INFO: New OVS network bridge 752020-08-26 10:10:37,818 - INFO: New OVS network bridge
242020-04-15 19:05:50,687 - INFO: Done 762020-08-26 10:10:58,762 - INFO: Done
25ok 77ok
26test 004: Creating VNF Management bridge (__main__.UnittestSuite) ... 78test 004: Creating VNF Management bridge (__main__.UnittestSuite) ...
272020-04-15 19:05:50,706 - INFO: New OVS network bridge 792020-08-26 10:10:58,794 - INFO: New OVS network bridge
282020-04-15 19:05:50,982 - INFO: Done 802020-08-26 10:10:58,977 - INFO: Done
29ok 81ok
30test 005: Creating LAN bridge and attaching lan interface to the bridge \ 82test 005: Creating LAN bridge and attaching lan interface to the bridge \
31(__main__.UnittestSuite) ... 83(__main__.UnittestSuite) ...
322020-04-15 19:05:51,001 - INFO: New OVS network bridge 842020-08-26 10:10:59,003 - INFO: New OVS network bridge
332020-04-15 19:05:51,682 - INFO: Done 852020-08-26 10:10:59,334 - INFO: Done
34ok 86ok
35test 006: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ... 87test 006: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ...
362020-04-15 19:05:51,704 - INFO: Onboard wizard 882020-08-26 10:10:59,370 - INFO: Onboard wizard
372020-04-15 19:08:43,978 - INFO: Done 892020-08-26 10:13:55,775 - INFO: Done
38ok 90ok
39test 007: Instantiate 128T VNF (__main__.UnittestSuite) ... 91test 007: Instantiate 128T VNF (__main__.UnittestSuite) ...
402020-04-15 19:08:44,000 - INFO: Instantiate VNF 922020-08-26 10:13:55,813 - INFO: Instantiate VNF
412020-04-15 19:09:37,385 - INFO: Done 932020-08-26 10:14:56,583 - INFO: Done
42ok 94ok
43 95
44---------------------------------------------------------------------- 96----------------------------------------------------------------------
45Ran 7 tests in 279.366s 97Ran 7 tests in 291.103s
46 98
47OK 99OK
48 100
101&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
102-s 128tCleanup.json -d "128T Cleanup"
49 103
50Clean-up use-case1 104Running 128T Cleanup...
51&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \
52-s 128tCleanup.json -d "128T Clean-up"
53
54Running 128T Clean-up...
55 105
56test 001: Destroying 128T VNF (__main__.UnittestSuite) ... 106test 001: Destroying 128T VNF (__main__.UnittestSuite) ...
572020-04-15 19:10:41,926 - INFO: Destroy VNF 1072020-08-26 10:15:28,395 - INFO: Destroy VNF
582020-04-15 19:10:42,813 - INFO: Done 1082020-08-26 10:15:29,452 - INFO: Done
59ok 109ok
60test 002: Deleting network bridge LAN (__main__.UnittestSuite) ... 110test 002: Deleting network bridge LAN (__main__.UnittestSuite) ...
612020-04-15 19:10:42,831 - INFO: Delete OVS network bridge 1112020-08-26 10:15:29,493 - INFO: Delete OVS network bridge
622020-04-15 19:10:43,231 - INFO: Done 1122020-08-26 10:15:29,734 - INFO: Done
63ok 113ok
64test 003: Deleting VNF management bridge (__main__.UnittestSuite) ... 114test 003: Deleting VNF management bridge (__main__.UnittestSuite) ...
652020-04-15 19:10:43,248 - INFO: Delete OVS network bridge 1152020-08-26 10:15:29,765 - INFO: Delete OVS network bridge
662020-04-15 19:10:43,366 - INFO: Done 1162020-08-26 10:15:30,080 - INFO: Done
67ok 117ok
68test 004: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ... 118test 004: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ...
692020-04-15 19:10:43,383 - INFO: Delete OVS network bridge 1192020-08-26 10:15:30,110 - INFO: Delete OVS network bridge
702020-04-15 19:10:58,638 - INFO: Done 1202020-08-26 10:15:46,907 - INFO: Done
71ok 121ok
72test 005: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ... 122test 005: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ...
732020-04-15 19:10:58,687 - INFO: Unbind NIC 1232020-08-26 10:15:46,967 - INFO: Unbind NIC
742020-04-15 19:11:00,490 - INFO: Done 1242020-08-26 10:15:48,489 - INFO: Done
75ok 125ok
76test 006: Offboarding 128t VNF (__main__.UnittestSuite) ... 126test 006: Offboarding 128t VNF (__main__.UnittestSuite) ...
772020-04-15 19:11:00,509 - INFO: Offboard VNF 1272020-08-26 10:15:48,531 - INFO: Offboard VNF
782020-04-15 19:11:01,416 - INFO: Done 1282020-08-26 10:15:49,171 - INFO: Done
79ok 129ok
80 130
81---------------------------------------------------------------------- 131----------------------------------------------------------------------
82Ran 6 tests in 19.507s 132Ran 6 tests in 20.808s
83 133
84OK 134OK</programlisting>
135 </section>
85 136
137 <section id="ap_d_uc2">
138 <title>Use-case 2: Service Chaining 128T - Fortigate Example
139 Usecase</title>
86 140
87Use-case2 141 <programlisting>&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
88&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \
89-s 128t_FG_SFCDeploy.json -d "128T - Fortigate SFC Deployment" 142-s 128t_FG_SFCDeploy.json -d "128T - Fortigate SFC Deployment"
90 143
91Running 128T - Fortigate SFC Deployment... 144Running 128T - Fortigate SFC Deployment...
92 145
93test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ... 146test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ...
942020-04-15 19:12:31,906 - INFO: Wait uCPE device 1472020-08-26 10:17:29,361 - INFO: Wait uCPE device
952020-04-15 19:13:02,972 - INFO: Status: Connected 1482020-08-26 10:18:00,473 - INFO: Status: Connected
962020-04-15 19:13:02,973 - INFO: Done 1492020-08-26 10:18:00,474 - INFO: Done
97ok 150ok
98test 002: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ... 151test 002: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ...
992020-04-15 19:13:02,994 - INFO: Bind NIC 1522020-08-26 10:18:00,634 - INFO: Bind NIC
1002020-04-15 19:13:04,105 - INFO: Done 1532020-08-26 10:18:01,805 - INFO: Done
101ok 154ok
102test 003: Creating ibm bridge (__main__.UnittestSuite) ... 155test 003: Creating ibm bridge (__main__.UnittestSuite) ...
1032020-04-15 19:13:04,122 - INFO: New OVS network bridge 1562020-08-26 10:18:01,863 - INFO: New OVS network bridge
1042020-04-15 19:13:10,939 - INFO: Done 1572020-08-26 10:18:30,640 - INFO: Done
105ok 158ok
106test 004: Creating VNF Management bridge (__main__.UnittestSuite) ... 159test 004: Creating VNF Management bridge (__main__.UnittestSuite) ...
1072020-04-15 19:13:10,957 - INFO: New OVS network bridge 1602020-08-26 10:18:30,670 - INFO: New OVS network bridge
1082020-04-15 19:13:11,246 - INFO: Done 1612020-08-26 10:18:30,876 - INFO: Done
109ok 162ok
110test 005: Creating LAN bridge and attaching lan interface to the bridge \ 163test 005: Creating LAN bridge and attaching lan interface to the bridge \
111(__main__.UnittestSuite) ... 164(__main__.UnittestSuite) ...
1122020-04-15 19:13:11,264 - INFO: New OVS network bridge 1652020-08-26 10:18:30,908 - INFO: New OVS network bridge
1132020-04-15 19:13:12,010 - INFO: Done 1662020-08-26 10:18:31,243 - INFO: Done
114ok 167ok
115test 006: Creating SFC(service function chaining) bridge (__main__.UnittestSuite) ... 168test 006: Creating SFC(service function chaining) bridge (__main__.UnittestSuite) ...
1162020-04-15 19:13:12,026 - INFO: New OVS network bridge 1692020-08-26 10:18:31,273 - INFO: New OVS network bridge
1172020-04-15 19:13:12,104 - INFO: Done 1702020-08-26 10:18:31,416 - INFO: Done
118ok 171ok
119test 007: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ... 172test 007: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ...
1202020-04-15 19:13:12,118 - INFO: Onboard wizard 1732020-08-26 10:18:31,448 - INFO: Onboard wizard
1212020-04-15 19:15:48,993 - INFO: Done 1742020-08-26 10:21:21,569 - INFO: Done
122ok 175ok
123test 008: Onboarding Fortigate VNF (wizard API) (__main__.UnittestSuite) ... 176test 008: Onboarding Fortigate VNF (wizard API) (__main__.UnittestSuite) ...
1242020-04-15 19:15:49,012 - INFO: Onboard wizard 1772020-08-26 10:21:21,608 - INFO: Onboard wizard
1252020-04-15 19:15:53,805 - INFO: Done 1782020-08-26 10:21:27,199 - INFO: Done
126ok 179ok
127test 009: Instantiate 128T VNF (__main__.UnittestSuite) ... 180test 009: Instantiate 128T VNF (__main__.UnittestSuite) ...
1282020-04-15 19:15:53,880 - INFO: Instantiate VNF 1812020-08-26 10:21:27,226 - INFO: Instantiate VNF
1292020-04-15 19:16:53,272 - INFO: Done 1822020-08-26 10:22:27,067 - INFO: Done
130ok 183ok
131test 010: Instantiate Fortigate VNF (__main__.UnittestSuite) ... 184test 010: Instantiate Fortigate VNF (__main__.UnittestSuite) ...
1322020-04-15 19:16:53,289 - INFO: Instantiate VNF 1852020-08-26 10:22:27,121 - INFO: Instantiate VNF
1332020-04-15 19:16:57,428 - INFO: Done 1862020-08-26 10:22:31,310 - INFO: Done
134ok 187ok
135 188
136---------------------------------------------------------------------- 189----------------------------------------------------------------------
137Ran 10 tests in 265.536s 190Ran 10 tests in 301.989s
138 191
139OK 192OK
140 193
194&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
195-s 128t_FG_SFCCleanup.json -d "128T - Fortigate SFC Cleanup"
141 196
142# Access 128T management interface 197Running 128T - Fortigate SFC Cleanup...
143https://172.24.12.154:60001
144user: admin
145password: 128Tadmin
146
147# Access Fortigate management interface
148https://172.24.12.154:60002
149user: admin
150password:
151
152
153
154Use case2 clean-up
155&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \
156-s 128t_FG_SFCCleanup.json -d "128T - Fortigate SFC CleanUp"
157
158Running 128T - Fortigate SFC CleanUp...
159 198
160test 001: Destroying Fortigate VNF (__main__.UnittestSuite) ... 199test 001: Destroying Fortigate VNF (__main__.UnittestSuite) ...
1612020-04-15 19:31:37,255 - INFO: Destroy VNF 2002020-08-26 10:23:29,308 - INFO: Destroy VNF
1622020-04-15 19:31:38,941 - INFO: Done 2012020-08-26 10:23:30,026 - INFO: Done
163ok 202ok
164test 002: Destroying 128T VNF (__main__.UnittestSuite) ... 203test 002: Destroying 128T VNF (__main__.UnittestSuite) ...
1652020-04-15 19:31:38,960 - INFO: Destroy VNF 2042020-08-26 10:23:30,065 - INFO: Destroy VNF
1662020-04-15 19:31:39,878 - INFO: Done 2052020-08-26 10:23:30,917 - INFO: Done
167ok 206ok
168test 003: Deleting network bridge SFC (__main__.UnittestSuite) ... 207test 003: Deleting network bridge SFC (__main__.UnittestSuite) ...
1692020-04-15 19:31:39,908 - INFO: Delete OVS network bridge 2082020-08-26 10:23:30,960 - INFO: Delete OVS network bridge
1702020-04-15 19:31:40,086 - INFO: Done 2092020-08-26 10:23:31,123 - INFO: Done
171ok 210ok
172test 004: Deleting network bridge LAN (__main__.UnittestSuite) ... 211test 004: Deleting network bridge LAN (__main__.UnittestSuite) ...
1732020-04-15 19:31:40,102 - INFO: Delete OVS network bridge 2122020-08-26 10:23:31,156 - INFO: Delete OVS network bridge
1742020-04-15 19:31:40,388 - INFO: Done 2132020-08-26 10:23:31,381 - INFO: Done
175ok 214ok
176test 005: Deleting VNF management bridge (__main__.UnittestSuite) ... 215test 005: Deleting VNF management bridge (__main__.UnittestSuite) ...
1772020-04-15 19:31:40,427 - INFO: Delete OVS network bridge 2162020-08-26 10:23:31,412 - INFO: Delete OVS network bridge
1782020-04-15 19:31:40,678 - INFO: Done 2172020-08-26 10:23:31,596 - INFO: Done
179ok 218ok
180test 006: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ... 219test 006: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ...
1812020-04-15 19:31:40,701 - INFO: Delete OVS network bridge 2202020-08-26 10:23:31,621 - INFO: Delete OVS network bridge
1822020-04-15 19:31:46,894 - INFO: Done 2212020-08-26 10:23:47,980 - INFO: Done
183ok 222ok
184test 007: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ... 223test 007: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ...
1852020-04-15 19:31:46,945 - INFO: Unbind NIC 2242020-08-26 10:23:48,019 - INFO: Unbind NIC
1862020-04-15 19:31:48,792 - INFO: Done 2252020-08-26 10:23:49,547 - INFO: Done
187ok 226ok
188test 008: Offboarding 128t VNF (__main__.UnittestSuite) ... 227test 008: Offboarding 128t VNF (__main__.UnittestSuite) ...
1892020-04-15 19:31:48,808 - INFO: Offboard VNF 2282020-08-26 10:23:49,575 - INFO: Offboard VNF
1902020-04-15 19:31:49,554 - INFO: Done 2292020-08-26 10:23:50,252 - INFO: Done
191ok 230ok
192test 009: Offboarding Fortigate VNF (__main__.UnittestSuite) ... 231test 009: Offboarding Fortigate VNF (__main__.UnittestSuite) ...
1932020-04-15 19:31:49,572 - INFO: Offboard VNF 2322020-08-26 10:23:50,295 - INFO: Offboard VNF
1942020-04-15 19:31:49,837 - INFO: Done 2332020-08-26 10:23:50,589 - INFO: Done
195ok 234ok
196 235
197---------------------------------------------------------------------- 236----------------------------------------------------------------------
198Ran 9 tests in 12.600s 237Ran 9 tests in 21.326s
199 238
200OK</programlisting> 239OK</programlisting>
240 </section>
201</appendix> \ No newline at end of file 241</appendix> \ No newline at end of file
diff --git a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml b/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
index 649a80d..9c60ebb 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
@@ -146,9 +146,9 @@
146node0.1048576kB = 3 </programlisting> 146node0.1048576kB = 3 </programlisting>
147 147
148 <note> 148 <note>
149 <para>Make sure there are no hugepages reserved in the kernel boot 149 <para>Make sure there are no hugepages reserved in the kernel boot
150 command line, these will override any manual configuration done 150 command line, these will override any manual configuration done in the
151 in the service.</para> 151 service.</para>
152 </note> 152 </note>
153 </section> 153 </section>
154 </section> 154 </section>
@@ -221,8 +221,8 @@ node0.1048576kB = 3 </programlisting>
221 drive) under <literal>/uefi_sb_keys</literal>.</para> 221 drive) under <literal>/uefi_sb_keys</literal>.</para>
222 222
223 <para>These certificates need to be manually enrolled in BIOS. The 223 <para>These certificates need to be manually enrolled in BIOS. The
224 exact details on how to proceed may vary depending the version of the 224 exact details on how to proceed may vary depending the version of the
225 UEFI firmware.</para> 225 UEFI firmware.</para>
226 </section> 226 </section>
227 227
228 <section id="enable_secure_boot"> 228 <section id="enable_secure_boot">
@@ -311,10 +311,9 @@ node0.1048576kB = 3 </programlisting>
311 311
312 <listitem> 312 <listitem>
313 <para>Compress the Enea NFV Access Run Time Platform 313 <para>Compress the Enea NFV Access Run Time Platform
314 <literal>.hddimg</literal> image for the uCPE 314 <literal>.hddimg</literal> image for the uCPE device architecture
315 device architecture using <literal>gzip</literal> and copy the 315 using <literal>gzip</literal> and copy the resulting
316 resulting <literal>hddimg.gz</literal> file to the HTTP 316 <literal>hddimg.gz</literal> file to the HTTP server.</para>
317 server.</para>
318 </listitem> 317 </listitem>
319 </orderedlist> 318 </orderedlist>
320 319
@@ -363,7 +362,7 @@ install_drive = /dev/sda</programlisting>
363 <note> 362 <note>
364 <para>The installation configuration file needs to use the Linux 363 <para>The installation configuration file needs to use the Linux
365 end-of-line format (\n), not the Windows format (\r\n).</para> 364 end-of-line format (\n), not the Windows format (\r\n).</para>
366 </note> 365 </note>
367 </section> 366 </section>
368 367
369 <section id="bare_meta_prov_pxe"> 368 <section id="bare_meta_prov_pxe">
@@ -374,15 +373,14 @@ install_drive = /dev/sda</programlisting>
374 (e.g <literal>/var/lib/tftpboot/pxelinux.cfg/default</literal>). The 373 (e.g <literal>/var/lib/tftpboot/pxelinux.cfg/default</literal>). The
375 PXE entry should have the following settings:</para> 374 PXE entry should have the following settings:</para>
376 375
377 <programlisting> 376 <programlisting>default nfv_access
378 default nfv_access 377label nfv_access
379 label nfv_access 378menu label ^NFV_ACCESS_INSTALLER
380 menu label ^NFV_ACCESS_INSTALLER 379kernel &lt;Path to kernel&gt;
381 kernel &lt;Path to kernel&gt; 380append root=/dev/ram0 initrd=&lt;Path to initramfs&gt; LABEL=pxe-installer \
382 append root=/dev/ram0 initrd=&lt;Path to initramfs&gt; LABEL=pxe-installer \ 381 INSTALL_CFG=http://&lt;Server IP&gt;/&lt;Path to install config file&gt; \
383 INSTALL_CFG=http://&lt;Server IP&gt;/&lt;Path to install config file&gt; \ 382 console=ttyS0,115200 earlyprintk=ttyS0,115200
384 console=ttyS0,115200 earlyprintk=ttyS0,115200 383ipappend 2
385 ipappend 2
386 </programlisting> 384 </programlisting>
387 </section> 385 </section>
388 </section> 386 </section>
@@ -397,14 +395,12 @@ install_drive = /dev/sda</programlisting>
397 395
398 <para>Example initiation using <literal>ipmitool</literal>:</para> 396 <para>Example initiation using <literal>ipmitool</literal>:</para>
399 397
400 <programlisting> 398 <programlisting>ipmitool -U &lt;user&gt; -P &lt;password&gt; -H &lt;uCPE device IPMI IP address&gt; chassis bootdev pxe
401 ipmitool -U &lt;user&gt; -P &lt;password&gt; -H &lt;uCPE device IPMI IP address&gt; chassis bootdev pxe 399ipmitool -U &lt;user&gt; -P &lt;password&gt; -H &lt;uCPE device IPMI IP address&gt; power reset </programlisting>
402 ipmitool -U &lt;user&gt; -P &lt;password&gt; -H &lt;uCPE device IPMI IP address&gt; power reset
403 </programlisting>
404 400
405 <para>The uCPE devices should be configured in BIOS to boot from the 401 <para>The uCPE devices should be configured in BIOS to boot from the
406 installation drive first in order to automatically start the Enea NFV 402 installation drive first in order to automatically start the Enea NFV
407 Access Run Time Platform when the installation is finished.</para> 403 Access Run Time Platform when the installation is finished.</para>
408 </section> 404 </section>
409 </section> 405 </section>
410</chapter> 406</chapter> \ No newline at end of file
diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
index d46b4c7..932f0cc 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
@@ -23,9 +23,12 @@
23 </itemizedlist> 23 </itemizedlist>
24 24
25 <para>For more information about Bare Metal Provisioning please refer to 25 <para>For more information about Bare Metal Provisioning please refer to
26 <xref linkend="bare_meta_prov"> 26 section <olink targetdoc="book_enea_nfv_access_getting_started"
27 5.3, Bare Metal Provisioning" 27 targetptr="bare_meta_prov">Bare Metal Provisioning in <xi:include
28 </xref>.</para> 28 href="../../s_docbuild/olinkdb/pardoc-names.xml"
29 xmlns:xi="http://www.w3.org/2001/XInclude"
30 xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
31 Manual.</para>
29 32
30 <section id="prereq"> 33 <section id="prereq">
31 <title>Prerequisites</title> 34 <title>Prerequisites</title>
@@ -110,10 +113,8 @@ q or quit - exits the script</programlisting></para>
110 113
111 <note> 114 <note>
112 <para>When using the installer for the first time, make sure to 115 <para>When using the installer for the first time, make sure to
113 set ALL parameters in order to be able to run all steps. See <xref 116 set ALL parameters in order to be able to run all steps. See
114 linkend="examples"> 117 Example 2 for details.</para>
115 Example 2
116 </xref> for details.</para>
117 </note> 118 </note>
118 119
119 <para><programlisting># set &lt;parameter_name&gt;=&lt;parameter_value&gt;</programlisting></para> 120 <para><programlisting># set &lt;parameter_name&gt;=&lt;parameter_value&gt;</programlisting></para>
@@ -217,8 +218,8 @@ rootfs_destination=</programlisting></para>
217 <note> 218 <note>
218 <para>The <literal>.hddimg</literal> image is available in the 219 <para>The <literal>.hddimg</literal> image is available in the
219 Enea_NFV_Access_Run_Time_Platform_ 220 Enea_NFV_Access_Run_Time_Platform_
220 &lt;processor&gt;_&lt;version&gt;-build&lt;build_number&gt;.tar.gz file you 221 &lt;processor&gt;_&lt;version&gt;-build&lt;build_number&gt;.tar.gz
221 downloaded with your release.</para> 222 file you downloaded with your release.</para>
222 </note> 223 </note>
223 224
224 <para><emphasis role="bold">Create a bootable USB stick 225 <para><emphasis role="bold">Create a bootable USB stick
diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
index dda71bb..2acc009 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
@@ -136,23 +136,25 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar</p
136 </listitem> 136 </listitem>
137 137
138 <listitem> 138 <listitem>
139 <para>If you plan to use the PostgreSQL server bundled with the 139 <para>If you plan to use the PostgreSQL server bundled with the uCPE
140 uCPE Manager, verify that there is no existing installation of the 140 Manager, verify that there is no existing installation of the
141 Postgres database. Execute the following command to check if you 141 Postgres database. Execute the following command to check if you
142 have a currently running PostgreSQL database server:</para> 142 have a currently running PostgreSQL database server:</para>
143 143
144 <programlisting>ps -ef | grep post</programlisting> 144 <programlisting>ps -ef | grep post</programlisting>
145 145
146 <para>To remove a currently installed PostgreSQL server (including the 146 <para>To remove a currently installed PostgreSQL server (including
147 existing postgres user), run the following commands:</para> 147 the existing postgres user), run the following commands:</para>
148 148
149 <programlisting>yum remove postgres\* 149 <programlisting>yum remove postgres\*
150rm -f /var/lib/pgsql 150rm -f /var/lib/pgsql
151rm -f /etc/postgres-reg.ini 151rm -f /etc/postgres-reg.ini
152userdel postgres</programlisting> 152userdel postgres</programlisting>
153 153
154 <note><para>This step is not necessary if the uCPE Manager 154 <note>
155 will be using an external database (like MariaDB).</para></note> 155 <para>This step is not necessary if the uCPE Manager will be using
156 an external database (like MariaDB).</para>
157 </note>
156 </listitem> 158 </listitem>
157 159
158 <listitem> 160 <listitem>
@@ -598,8 +600,12 @@ userdel postgres</programlisting>
598 <para>When using this mechanism, the device will initiate a connection 600 <para>When using this mechanism, the device will initiate a connection
599 to the uCPE Manager for NETCONF traffic (over SSH), while the uCPE 601 to the uCPE Manager for NETCONF traffic (over SSH), while the uCPE
600 Manager waits for a device connection. For more information please see 602 Manager waits for a device connection. For more information please see
601 section <link linkend="install_ena_stick">Installing Enea NFV 603 section <olink targetdoc="book_enea_nfv_access_getting_started"
602 Access</link> for more details.</para> 604 targetptr="auto_installer">Creating a bootable USB stick in the
605 <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
606 xmlns:xi="http://www.w3.org/2001/XInclude"
607 xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
608 Manual for more details.</para>
603 </section> 609 </section>
604 </section> 610 </section>
605 611
@@ -938,8 +944,13 @@ userdel postgres</programlisting>
938 <note> 944 <note>
939 <para>VNF management interfaces must be configured in same 945 <para>VNF management interfaces must be configured in same
940 network as the <literal>vnf-mgmt-address</literal> of the 946 network as the <literal>vnf-mgmt-address</literal> of the
941 bridge. For more information, please see 4.4 <link 947 bridge. For more information, please see section <olink
942 linkend="vnf_management">VNF Management</link>.</para> 948 targetdoc="book_enea_nfv_access_getting_started"
949 targetptr="vnf_management">VNF Management in the <xi:include
950 href="../../s_docbuild/olinkdb/pardoc-names.xml"
951 xmlns:xi="http://www.w3.org/2001/XInclude"
952 xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
953 Manual.</para>
943 </note> 954 </note>
944 </section> 955 </section>
945 956
@@ -2041,4 +2052,4 @@ userdel postgres</programlisting>
2041 </orderedlist> 2052 </orderedlist>
2042 </section> 2053 </section>
2043 </section> 2054 </section>
2044</chapter> 2055</chapter> \ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
index c1d7de5..cdea2be 100644
--- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
@@ -88,9 +88,9 @@
88 88
89 <listitem> 89 <listitem>
90 <para><remark>ELCCR-847</remark>The Juniper VNF cannot be instantiated 90 <para><remark>ELCCR-847</remark>The Juniper VNF cannot be instantiated
91 on the XeonD architecture because the domain XML file cannot be modified 91 on the Xeon-D architectures due to missing CPU features in the VNF's
92 prior to creating a Virtual Machine. This impacts all Examples Use Cases 92 domain XML. This impacts all Examples Use Cases and AF&amp;TH Tests
93 and AF&amp;TH Tests where Juniper VNF is used.</para> 93 where Juniper VNF is used.</para>
94 </listitem> 94 </listitem>
95 95
96 <listitem> 96 <listitem>
@@ -113,17 +113,22 @@
113 </listitem> 113 </listitem>
114 114
115 <listitem> 115 <listitem>
116 <para><remark>LXCR-9992</remark>Due to the way VFIO works, there are 116 <para><remark>LXCR-9992</remark>Depending on how PCI devices are split
117 certain limitations regarding which devices can be used with VFIO. 117 among IOMMU groups, there are certain limitations regarding how the
118 Mainly, it comes down to how IOMMU groups work. Any Virtual Function 118 <literal>vfio-pci</literal> driver can be used. For PCI devices
119 device can be used with VFIO on its own, however, physical devices will 119 belonging to the same IOMMU group, it is required that all are managed
120 require either all ports to be bound to VFIO, or only some of them bound 120 within same security domain (e.g. host system or VNF). Therefore it is
121 while others not bound to anything at all.</para> 121 not possible to bind only some of them to the
122 <literal>vfio-pci</literal> driver, while the rest are managed by other
123 drivers. In this case the <literal>igb_uio</literal> driver will be used
124 instead for the entire IOMMU group.</para>
122 125
123 <para>If UEFI secure boot is enabled, the Linux kernel may disallow the 126 <para>If UEFI Secure Boot is enabled, the Linux kernel disallows the use
124 use of UIO on the system. Therefore, devices intended for use by the 127 of the UIO framework, therefore network devices intended for use by DPDK
125 DPDK should be bound to the <literal>vfio-pci</literal> kernel module 128 must be bound to the <literal>vfio-pci</literal> driver rather than the
126 rather than the <literal>igb_uio</literal>.</para> 129 <literal>igb_uio</literal>. However, the limitation stated above still
130 applies so all the interfaces must be assigned to
131 <literal>vfio-pci</literal>.</para>
127 </listitem> 132 </listitem>
128 133
129 <listitem> 134 <listitem>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-05-14 17:12:17 +0000