From cbdca7c9b2ec9f0972dbf9c3d06c94bee9e86ee4 Mon Sep 17 00:00:00 2001 From: mrpa Date: Wed, 26 Aug 2020 14:01:14 +0200 Subject: Final 2.2.3 edits part 2. Change-Id: I9f959e6f6adb94a61dd2c26ce2c0468933596490 Signed-off-by: mrpa --- .../doc/components.xml | 18 +- .../doc/getting_started.xml | 17 +- .../doc/appendix_4.xml | 69 ++++-- .../doc/appendix_5.xml | 238 ++++++++++++--------- .../doc/advanced_configurations.xml | 44 ++-- .../doc/getting_started_nfv_access.xml | 19 +- .../doc/getting_started_ucpe_manager.xml | 39 ++-- .../doc/known_bugs_and_limitations.xml | 31 +-- 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 @@ One or more uCPE devices running the Enea NFV Access Run Time Platform are required as hosts to run the VNF(s). The uCPE device is known to the uCPE Manager as the "VcpeAgent" device module. - - Before running any use case with the Automation Framework or - the Test Harness, make sure the uCPE device(s) have been added to - the uCPE Manager. + + + Before running any use case with the Automation Framework or the + Test Harness, make sure the uCPE device(s) have been added to the uCPE + Manager. + Adding a VcpeAgent device can be done via two methods: @@ -124,12 +126,10 @@ For details about the test suites or test cases please refer to chapter Sample Test Cases in Sample Test Cases in the. - - this olink needs to be fixed it points to getting started not the - test spec manual, an olinkdb update is needed to know why. + xpointer="element(book_enea_nfv_access_system_test_specification/1)" /> + Manual. \ 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 @@ The Automation Framework and Test Harness installation may be done on the same machine used for uCPE Manager installation, although this is - not encouraged. For more details see chapter - 3.2.what chapter of what book is this link refering - to? + not encouraged. For more details see section Automation Framework in the . @@ -49,9 +52,11 @@ The following enviroment setup is needed for running all tests - defined in the Enea NFV Access System Test Specification manual: - - olink to the book needed here. + defined in the + manual: Lab Network Requirements 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 @@ Running Enea Automation Framework tests + For more detailed information regarding the Automation Framework and + Test Harness please see the . + The most relevant information from the Automation Framework and Test - Harness structure: + Harness structure is presented below: |---automation_framework | |---unittestSuite @@ -18,14 +24,14 @@ | | |---unittestSuite.py |---lab_config | |---trgt-1 -| | |---enp4s0f0_0000_04_00_0.json -| | |---enp4s0f1_0000_04_00_1.json | | |---ibm_br.json - In-band management definition. -| | |---lan_br_enp4s0f1.json - Lan bridge definition. -| | |---trgt-1.json - - Target definition - make sure to update the "address". +| | |---lan_br.json - Lan bridge definition. +| | |---target.json + - Target definition - the "address", "deviceId", "name" and \ + "version" must be updated. | | |---sfc_br.json - Service chain bridge definition. | | |---vnf_mgmt_br.json - VNF management bridge definition. +| | |---lan_nic.json - NIC definition. |---vnf_config | |---128t | | |---128tInstance.json - 128T instantiation - used in use case 1. @@ -37,16 +43,53 @@ | | |---fortigateInstance.json - Fortigate instantiantion. | | |---fortigate.json - Fortigate onboarding. | | |---fortigateLicense.lic - - Fortigate license - replace it with a valid License file. + - Fortigate license - contact Fortinet to get a VNF image and license file. |---vnf_image -| |---centos_128t_with_ci.qcow2 - 128T qcow2 image. -| |---fortios.qcow2 - Fortigate qcow2 image. +| |---centos_128t_with_ci.qcow2 - Contact 128 Technology to get a \ + VNF image and its license file. +| |---fortios.qcow2 - Contact Fortinet to get a VNF image \ + and its license file. Make sure to update the relevant configuration file for your setup. - The essential files to consider are the target configuration - (trgt-1.json), the license for the Fortigate VNF, and + The essential files to consider are the uCPE Device configuration + (target.json), the license for the Fortigate VNF, and the 128T cloud-init iso image matching your network. - To run a test:> cd automation_and_systemtest/automation_framework/unittestSuite -> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 -s + For uCPE Device configuration (target.json) + please change the following information, if needed, in the JSON file: + + + + address - The IP address of uCPE Device. + + + + version - The NFVA version. + + + + deviceId - The device ID of uCPE Device. + + + + name - The name of uCPE Device. + + + + + Before starting the two usecases detailed in the following appendix, + the uCPE Device needs to be added into the uCPE Manager. + + + To run a test: + + > cd automation_framework/unittestSuite/ +> python unittestSuite.py -u admin -p admin -H <uCPEManager IP address> -n \ +<uCPE Device name> -s <Test suite> -d <description> + + The Test suite must be one from any of the + following: 128tDeploy.json, + 128tCleanup.json, + 128t_FG_SFCDeploy.json, or + 128t_FG_SFCCleanup.json. \ 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 @@ Example Tests Results using the Automation Framework - Test Host: -Use Case1 - 128T -> cd automation_and_systemtest/automation_framework/unittestSuite -> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \ + In order to run the following example usecases, certain configuration + file entries need to be modified according to the network setup that it will + be used, for more details see the previous appendix: + + + + uCPE Device name: inteld1521-17 + + + + address: 172.24.8.62 + + + + version: 2.2.3 + + + + deviceId: inteld1521-17 + + + + > cat lab_config/trgt-1/target.json +{ + "name": "inteld1521-17", + "description": "trgt", + "address": "172.24.8.62", + "port": "830", + "username": "root", + "password": "", + "certificate": null, + "passphrase": null, + "maintMode": "false", + "version": "2.2.3", + "deviceId": "inteld1521-17" +}The IP address of the uCPE Manager that will be used in + these examples is 172.24.3.92. + + The FortiGate and 128T VNF images need to be copied into the + vnf_image directory. The names should be the same as + those described in Appendix D. + + The FortiGate valid license file needs to be copied into the + vnf_config/fortigate/ directory. The name should be the + same as that described in Appendix D. + + The cloud init files that match the network, need to be copied into + the vnf_config/fortigate/ and the + vnf_config/128t/ directories respectively. The names + should be the same as those described in Appendix D. + +
+ Use-case 1: 128T VNF Router Example Use-case + + > cd automation_framework/unittestSuite/ +> python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \ -s 128tDeploy.json -d "128T Deployment" Running 128T Deployment... test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ... -2020-04-15 19:04:58,037 - INFO: Wait uCPE device -2020-04-15 19:05:29,128 - INFO: Status: Connected -2020-04-15 19:05:29,128 - INFO: Done +2020-08-26 10:10:05,517 - INFO: Wait uCPE device +2020-08-26 10:10:36,650 - INFO: Status: Connected +2020-08-26 10:10:36,651 - INFO: Done ok test 002: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ... -2020-04-15 19:05:29,154 - INFO: Bind NIC -2020-04-15 19:05:30,280 - INFO: Done +2020-08-26 10:10:36,686 - INFO: Bind NIC +2020-08-26 10:10:37,788 - INFO: Done ok test 003: Creating ibm bridge (__main__.UnittestSuite) ... -2020-04-15 19:05:30,302 - INFO: New OVS network bridge -2020-04-15 19:05:50,687 - INFO: Done +2020-08-26 10:10:37,818 - INFO: New OVS network bridge +2020-08-26 10:10:58,762 - INFO: Done ok test 004: Creating VNF Management bridge (__main__.UnittestSuite) ... -2020-04-15 19:05:50,706 - INFO: New OVS network bridge -2020-04-15 19:05:50,982 - INFO: Done +2020-08-26 10:10:58,794 - INFO: New OVS network bridge +2020-08-26 10:10:58,977 - INFO: Done ok test 005: Creating LAN bridge and attaching lan interface to the bridge \ (__main__.UnittestSuite) ... -2020-04-15 19:05:51,001 - INFO: New OVS network bridge -2020-04-15 19:05:51,682 - INFO: Done +2020-08-26 10:10:59,003 - INFO: New OVS network bridge +2020-08-26 10:10:59,334 - INFO: Done ok test 006: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ... -2020-04-15 19:05:51,704 - INFO: Onboard wizard -2020-04-15 19:08:43,978 - INFO: Done +2020-08-26 10:10:59,370 - INFO: Onboard wizard +2020-08-26 10:13:55,775 - INFO: Done ok test 007: Instantiate 128T VNF (__main__.UnittestSuite) ... -2020-04-15 19:08:44,000 - INFO: Instantiate VNF -2020-04-15 19:09:37,385 - INFO: Done +2020-08-26 10:13:55,813 - INFO: Instantiate VNF +2020-08-26 10:14:56,583 - INFO: Done ok ---------------------------------------------------------------------- -Ran 7 tests in 279.366s +Ran 7 tests in 291.103s OK +> python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \ +-s 128tCleanup.json -d "128T Cleanup" -Clean-up use-case1 -> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \ --s 128tCleanup.json -d "128T Clean-up" - -Running 128T Clean-up... +Running 128T Cleanup... test 001: Destroying 128T VNF (__main__.UnittestSuite) ... -2020-04-15 19:10:41,926 - INFO: Destroy VNF -2020-04-15 19:10:42,813 - INFO: Done +2020-08-26 10:15:28,395 - INFO: Destroy VNF +2020-08-26 10:15:29,452 - INFO: Done ok test 002: Deleting network bridge LAN (__main__.UnittestSuite) ... -2020-04-15 19:10:42,831 - INFO: Delete OVS network bridge -2020-04-15 19:10:43,231 - INFO: Done +2020-08-26 10:15:29,493 - INFO: Delete OVS network bridge +2020-08-26 10:15:29,734 - INFO: Done ok test 003: Deleting VNF management bridge (__main__.UnittestSuite) ... -2020-04-15 19:10:43,248 - INFO: Delete OVS network bridge -2020-04-15 19:10:43,366 - INFO: Done +2020-08-26 10:15:29,765 - INFO: Delete OVS network bridge +2020-08-26 10:15:30,080 - INFO: Done ok test 004: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ... -2020-04-15 19:10:43,383 - INFO: Delete OVS network bridge -2020-04-15 19:10:58,638 - INFO: Done +2020-08-26 10:15:30,110 - INFO: Delete OVS network bridge +2020-08-26 10:15:46,907 - INFO: Done ok test 005: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ... -2020-04-15 19:10:58,687 - INFO: Unbind NIC -2020-04-15 19:11:00,490 - INFO: Done +2020-08-26 10:15:46,967 - INFO: Unbind NIC +2020-08-26 10:15:48,489 - INFO: Done ok test 006: Offboarding 128t VNF (__main__.UnittestSuite) ... -2020-04-15 19:11:00,509 - INFO: Offboard VNF -2020-04-15 19:11:01,416 - INFO: Done +2020-08-26 10:15:48,531 - INFO: Offboard VNF +2020-08-26 10:15:49,171 - INFO: Done ok ---------------------------------------------------------------------- -Ran 6 tests in 19.507s +Ran 6 tests in 20.808s -OK +OK +
+
+ Use-case 2: Service Chaining 128T - Fortigate Example + Usecase -Use-case2 -> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \ + > python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \ -s 128t_FG_SFCDeploy.json -d "128T - Fortigate SFC Deployment" Running 128T - Fortigate SFC Deployment... test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ... -2020-04-15 19:12:31,906 - INFO: Wait uCPE device -2020-04-15 19:13:02,972 - INFO: Status: Connected -2020-04-15 19:13:02,973 - INFO: Done +2020-08-26 10:17:29,361 - INFO: Wait uCPE device +2020-08-26 10:18:00,473 - INFO: Status: Connected +2020-08-26 10:18:00,474 - INFO: Done ok test 002: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ... -2020-04-15 19:13:02,994 - INFO: Bind NIC -2020-04-15 19:13:04,105 - INFO: Done +2020-08-26 10:18:00,634 - INFO: Bind NIC +2020-08-26 10:18:01,805 - INFO: Done ok test 003: Creating ibm bridge (__main__.UnittestSuite) ... -2020-04-15 19:13:04,122 - INFO: New OVS network bridge -2020-04-15 19:13:10,939 - INFO: Done +2020-08-26 10:18:01,863 - INFO: New OVS network bridge +2020-08-26 10:18:30,640 - INFO: Done ok test 004: Creating VNF Management bridge (__main__.UnittestSuite) ... -2020-04-15 19:13:10,957 - INFO: New OVS network bridge -2020-04-15 19:13:11,246 - INFO: Done +2020-08-26 10:18:30,670 - INFO: New OVS network bridge +2020-08-26 10:18:30,876 - INFO: Done ok test 005: Creating LAN bridge and attaching lan interface to the bridge \ (__main__.UnittestSuite) ... -2020-04-15 19:13:11,264 - INFO: New OVS network bridge -2020-04-15 19:13:12,010 - INFO: Done +2020-08-26 10:18:30,908 - INFO: New OVS network bridge +2020-08-26 10:18:31,243 - INFO: Done ok test 006: Creating SFC(service function chaining) bridge (__main__.UnittestSuite) ... -2020-04-15 19:13:12,026 - INFO: New OVS network bridge -2020-04-15 19:13:12,104 - INFO: Done +2020-08-26 10:18:31,273 - INFO: New OVS network bridge +2020-08-26 10:18:31,416 - INFO: Done ok test 007: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ... -2020-04-15 19:13:12,118 - INFO: Onboard wizard -2020-04-15 19:15:48,993 - INFO: Done +2020-08-26 10:18:31,448 - INFO: Onboard wizard +2020-08-26 10:21:21,569 - INFO: Done ok test 008: Onboarding Fortigate VNF (wizard API) (__main__.UnittestSuite) ... -2020-04-15 19:15:49,012 - INFO: Onboard wizard -2020-04-15 19:15:53,805 - INFO: Done +2020-08-26 10:21:21,608 - INFO: Onboard wizard +2020-08-26 10:21:27,199 - INFO: Done ok test 009: Instantiate 128T VNF (__main__.UnittestSuite) ... -2020-04-15 19:15:53,880 - INFO: Instantiate VNF -2020-04-15 19:16:53,272 - INFO: Done +2020-08-26 10:21:27,226 - INFO: Instantiate VNF +2020-08-26 10:22:27,067 - INFO: Done ok test 010: Instantiate Fortigate VNF (__main__.UnittestSuite) ... -2020-04-15 19:16:53,289 - INFO: Instantiate VNF -2020-04-15 19:16:57,428 - INFO: Done +2020-08-26 10:22:27,121 - INFO: Instantiate VNF +2020-08-26 10:22:31,310 - INFO: Done ok ---------------------------------------------------------------------- -Ran 10 tests in 265.536s +Ran 10 tests in 301.989s OK +> python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \ +-s 128t_FG_SFCCleanup.json -d "128T - Fortigate SFC Cleanup" -# Access 128T management interface -https://172.24.12.154:60001 -user: admin -password: 128Tadmin - -# Access Fortigate management interface -https://172.24.12.154:60002 -user: admin -password: - - - -Use case2 clean-up -> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \ --s 128t_FG_SFCCleanup.json -d "128T - Fortigate SFC CleanUp" - -Running 128T - Fortigate SFC CleanUp... +Running 128T - Fortigate SFC Cleanup... test 001: Destroying Fortigate VNF (__main__.UnittestSuite) ... -2020-04-15 19:31:37,255 - INFO: Destroy VNF -2020-04-15 19:31:38,941 - INFO: Done +2020-08-26 10:23:29,308 - INFO: Destroy VNF +2020-08-26 10:23:30,026 - INFO: Done ok test 002: Destroying 128T VNF (__main__.UnittestSuite) ... -2020-04-15 19:31:38,960 - INFO: Destroy VNF -2020-04-15 19:31:39,878 - INFO: Done +2020-08-26 10:23:30,065 - INFO: Destroy VNF +2020-08-26 10:23:30,917 - INFO: Done ok test 003: Deleting network bridge SFC (__main__.UnittestSuite) ... -2020-04-15 19:31:39,908 - INFO: Delete OVS network bridge -2020-04-15 19:31:40,086 - INFO: Done +2020-08-26 10:23:30,960 - INFO: Delete OVS network bridge +2020-08-26 10:23:31,123 - INFO: Done ok test 004: Deleting network bridge LAN (__main__.UnittestSuite) ... -2020-04-15 19:31:40,102 - INFO: Delete OVS network bridge -2020-04-15 19:31:40,388 - INFO: Done +2020-08-26 10:23:31,156 - INFO: Delete OVS network bridge +2020-08-26 10:23:31,381 - INFO: Done ok test 005: Deleting VNF management bridge (__main__.UnittestSuite) ... -2020-04-15 19:31:40,427 - INFO: Delete OVS network bridge -2020-04-15 19:31:40,678 - INFO: Done +2020-08-26 10:23:31,412 - INFO: Delete OVS network bridge +2020-08-26 10:23:31,596 - INFO: Done ok test 006: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ... -2020-04-15 19:31:40,701 - INFO: Delete OVS network bridge -2020-04-15 19:31:46,894 - INFO: Done +2020-08-26 10:23:31,621 - INFO: Delete OVS network bridge +2020-08-26 10:23:47,980 - INFO: Done ok test 007: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ... -2020-04-15 19:31:46,945 - INFO: Unbind NIC -2020-04-15 19:31:48,792 - INFO: Done +2020-08-26 10:23:48,019 - INFO: Unbind NIC +2020-08-26 10:23:49,547 - INFO: Done ok test 008: Offboarding 128t VNF (__main__.UnittestSuite) ... -2020-04-15 19:31:48,808 - INFO: Offboard VNF -2020-04-15 19:31:49,554 - INFO: Done +2020-08-26 10:23:49,575 - INFO: Offboard VNF +2020-08-26 10:23:50,252 - INFO: Done ok test 009: Offboarding Fortigate VNF (__main__.UnittestSuite) ... -2020-04-15 19:31:49,572 - INFO: Offboard VNF -2020-04-15 19:31:49,837 - INFO: Done +2020-08-26 10:23:50,295 - INFO: Offboard VNF +2020-08-26 10:23:50,589 - INFO: Done ok ---------------------------------------------------------------------- -Ran 9 tests in 12.600s +Ran 9 tests in 21.326s OK +
\ 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 @@ node0.1048576kB = 3 - Make sure there are no hugepages reserved in the kernel boot - command line, these will override any manual configuration done - in the service. + Make sure there are no hugepages reserved in the kernel boot + command line, these will override any manual configuration done in the + service. @@ -221,8 +221,8 @@ node0.1048576kB = 3 drive) under /uefi_sb_keys. These certificates need to be manually enrolled in BIOS. The - exact details on how to proceed may vary depending the version of the - UEFI firmware. + exact details on how to proceed may vary depending the version of the + UEFI firmware.
@@ -311,10 +311,9 @@ node0.1048576kB = 3 Compress the Enea NFV Access Run Time Platform - .hddimg image for the uCPE - device architecture using gzip and copy the - resulting hddimg.gz file to the HTTP - server. + .hddimg image for the uCPE device architecture + using gzip and copy the resulting + hddimg.gz file to the HTTP server. @@ -363,7 +362,7 @@ install_drive = /dev/sda The installation configuration file needs to use the Linux end-of-line format (\n), not the Windows format (\r\n). - +
@@ -374,15 +373,14 @@ install_drive = /dev/sda (e.g /var/lib/tftpboot/pxelinux.cfg/default). The PXE entry should have the following settings: - - default nfv_access - label nfv_access - menu label ^NFV_ACCESS_INSTALLER - kernel <Path to kernel> - append root=/dev/ram0 initrd=<Path to initramfs> LABEL=pxe-installer \ - INSTALL_CFG=http://<Server IP>/<Path to install config file> \ - console=ttyS0,115200 earlyprintk=ttyS0,115200 - ipappend 2 + default nfv_access +label nfv_access +menu label ^NFV_ACCESS_INSTALLER +kernel <Path to kernel> +append root=/dev/ram0 initrd=<Path to initramfs> LABEL=pxe-installer \ + INSTALL_CFG=http://<Server IP>/<Path to install config file> \ + console=ttyS0,115200 earlyprintk=ttyS0,115200 +ipappend 2
@@ -397,14 +395,12 @@ install_drive = /dev/sda Example initiation using ipmitool: - - ipmitool -U <user> -P <password> -H <uCPE device IPMI IP address> chassis bootdev pxe - ipmitool -U <user> -P <password> -H <uCPE device IPMI IP address> power reset - + ipmitool -U <user> -P <password> -H <uCPE device IPMI IP address> chassis bootdev pxe +ipmitool -U <user> -P <password> -H <uCPE device IPMI IP address> power reset The uCPE devices should be configured in BIOS to boot from the installation drive first in order to automatically start the Enea NFV Access Run Time Platform when the installation is finished. - + \ 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 @@ For more information about Bare Metal Provisioning please refer to - - 5.3, Bare Metal Provisioning" - . + section Bare Metal Provisioning in + Manual.
Prerequisites @@ -110,10 +113,8 @@ q or quit - exits the script When using the installer for the first time, make sure to - set ALL parameters in order to be able to run all steps. See - Example 2 - for details. + set ALL parameters in order to be able to run all steps. See + Example 2 for details. # set <parameter_name>=<parameter_value> @@ -217,8 +218,8 @@ rootfs_destination= The .hddimg image is available in the Enea_NFV_Access_Run_Time_Platform_ - <processor>_<version>-build<build_number>.tar.gz file you - downloaded with your release. + <processor>_<version>-build<build_number>.tar.gz + file you downloaded with your release. 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

- If you plan to use the PostgreSQL server bundled with the - uCPE Manager, verify that there is no existing installation of the + If you plan to use the PostgreSQL server bundled with the uCPE + Manager, verify that there is no existing installation of the Postgres database. Execute the following command to check if you have a currently running PostgreSQL database server: ps -ef | grep post - - To remove a currently installed PostgreSQL server (including the - existing postgres user), run the following commands: - + + To remove a currently installed PostgreSQL server (including + the existing postgres user), run the following commands: + yum remove postgres\* rm -f /var/lib/pgsql rm -f /etc/postgres-reg.ini userdel postgres - - This step is not necessary if the uCPE Manager - will be using an external database (like MariaDB). + + + This step is not necessary if the uCPE Manager will be using + an external database (like MariaDB). + @@ -598,8 +600,12 @@ userdel postgres When using this mechanism, the device will initiate a connection to the uCPE Manager for NETCONF traffic (over SSH), while the uCPE Manager waits for a device connection. For more information please see - section Installing Enea NFV - Access for more details. + section Creating a bootable USB stick in the + + Manual for more details.
@@ -938,8 +944,13 @@ userdel postgres VNF management interfaces must be configured in same network as the vnf-mgmt-address of the - bridge. For more information, please see 4.4 VNF Management. + bridge. For more information, please see section VNF Management in the + Manual. @@ -2041,4 +2052,4 @@ userdel postgres - + \ 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 @@ ELCCR-847The Juniper VNF cannot be instantiated - on the XeonD architecture because the domain XML file cannot be modified - prior to creating a Virtual Machine. This impacts all Examples Use Cases - and AF&TH Tests where Juniper VNF is used. + on the Xeon-D architectures due to missing CPU features in the VNF's + domain XML. This impacts all Examples Use Cases and AF&TH Tests + where Juniper VNF is used. @@ -113,17 +113,22 @@ - LXCR-9992Due to the way VFIO works, there are - certain limitations regarding which devices can be used with VFIO. - Mainly, it comes down to how IOMMU groups work. Any Virtual Function - device can be used with VFIO on its own, however, physical devices will - require either all ports to be bound to VFIO, or only some of them bound - while others not bound to anything at all. + LXCR-9992Depending on how PCI devices are split + among IOMMU groups, there are certain limitations regarding how the + vfio-pci driver can be used. For PCI devices + belonging to the same IOMMU group, it is required that all are managed + within same security domain (e.g. host system or VNF). Therefore it is + not possible to bind only some of them to the + vfio-pci driver, while the rest are managed by other + drivers. In this case the igb_uio driver will be used + instead for the entire IOMMU group. - If UEFI secure boot is enabled, the Linux kernel may disallow the - use of UIO on the system. Therefore, devices intended for use by the - DPDK should be bound to the vfio-pci kernel module - rather than the igb_uio. + If UEFI Secure Boot is enabled, the Linux kernel disallows the use + of the UIO framework, therefore network devices intended for use by DPDK + must be bound to the vfio-pci driver rather than the + igb_uio. However, the limitation stated above still + applies so all the interfaces must be assigned to + vfio-pci. -- cgit v1.2.3-54-g00ecf