From 8a9a64151ad1710a3a90ad4ded465cb79401a5af Mon Sep 17 00:00:00 2001 From: mrpa Date: Tue, 20 Oct 2020 10:09:28 +0200 Subject: Synced branch feature_CPDX-3385 (the new parts) into the develop branch. Change-Id: I38493572937c6e96bf329e1590b7184e561c72e5 Signed-off-by: mrpa --- .../doc/automation_framework_test_harness.xml | 4 +-- .../doc/components.xml | 12 ++++--- .../doc/getting_started.xml | 10 +++--- .../doc/getting_started_ucpe_manager.xml | 42 ++++++++++++++++++---- .../doc/introduction.xml | 10 ------ .../doc/known_bugs_and_limitations.xml | 37 +++++++++---------- .../doc/configuration.xml | 8 ++--- .../doc/sample_test_cases.xml | 17 +++++---- 8 files changed, 81 insertions(+), 59 deletions(-) diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml index 35cac8c..2cf02b6 100644 --- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml +++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml @@ -802,13 +802,13 @@ Mandatory options: Sample intelc3850-2.json configuration file: - + { "name": "intelc3850-2", "deviceId": "intelc3850-2", "deviceGroupingTags": " ", "description": "", - "address": "192.168.1.100", +"address": "172.24.12.114", "port": "22", "username": "root", "password": "root", 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 3439a64..b408041 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 @@ -34,10 +34,11 @@ For more on Enea uCPE Manager installation instructions, please refer to the section on how to Install the Enea uCPE Manager in + targetptr="install_ucpe_manager">Install the Enea uCPE Manager in the . + xpointer="element(book_enea_nfv_access_getting_started/1)" /> + Manual.
@@ -71,10 +72,11 @@ For more on Enea NFV Access installation instructions, please refer to chapter Getting Started with Enea NFV Access in + targetptr="access_installer">Getting Started with Enea NFV Access in the . + xpointer="element(book_enea_nfv_access_getting_started/1)" /> + Manual.
@@ -126,7 +128,7 @@ For details about the test suites or test cases please refer to chapter Sample Test Cases in theSample Test Cases in the 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 8a62b3b..dbb19c4 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 @@ -88,9 +88,10 @@ For details on how to install the uCPE Manager, see Install the Enea uCPE Manager in - . + xpointer="element(book_enea_nfv_access_getting_started/1)" /> + Manual. @@ -116,10 +117,11 @@ For information on how to install Enea NFV Access refer to Getting Started with Enea NFV - Access in . + xpointer="element(book_enea_nfv_access_getting_started/1)" /> + Manual.
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 a732129..e2a8a97 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 @@ -277,11 +277,11 @@ userdel postgres The service will be automatically started when the computer boots up. The user may enable the firewall in order to allow access to - these specific ports: 80 (TCP), 443 (TCP), 54327 (UDP) and 5701:5708 - (TCP). If callhome is used access to the following ports must also be - allowed: 4334 (TCP) and 2021:2040 (TCP). Otherwise, the user should - check that the CentOS machine where the uCPE Manager is installed has - the firewall disabled. + these specific ports: 80 (TCP), 443 (TCP), 54327 (UDP), 5701:5708 + (TCP) and 7000:7009 (TCP). If callhome is used, access to the + following ports must also be allowed: 4334 (TCP) and 2021:2040 (TCP). + Otherwise, the user should check that the CentOS machine where the + uCPE Manager is installed has the firewall disabled. Verify that the installation has succeeded by: @@ -2034,8 +2034,36 @@ userdel postgres SSH to the uCPE device from the Enea uCPE Manager - (Device->SSH) using user: - root and no password. + (Device->SSH) using: + + + + For normal connections: the Username + (default: root), the Password (default: no + password), the Port (default: 22) and the + Reverse ssh checkbox: unchecked. + + + + For reverse ssh connections: the + Username (default: root) and the + Reverse ssh checkbox checked. The port will + be automatically choosen by the uCPE Manager in the range + defined in the System -> Configuration -> Reverse + SSH configuration panel. By default, the start port + will be 7000 and the maximum number of ports + allocated to all devices is 10. Only one port per device is + allowed. + + A SSH Tunnel between the uCPE Manager and the device will be created: + ssh -f -N -T -R < Port > :localhost:22 <uCPE Mgr user>@<uCPE MgrIP> + The device must be connected to the uCPE Manager for the tunnel to be created. + On connection, a normal ssh connection will be made: + ssh -p <Port> <Username>@localhost + + + + diff --git a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml index 96c3172..2009672 100644 --- a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml +++ b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml @@ -4,16 +4,6 @@ Introduction - INFO eltf_params_updated.xml - contains many parameters in the book, also in the open source books, and - MUST be created FROM eltf_params_template.xml. The parameters are - automatically used in the books, via xi:include statements, similar to how - parameters from pardoc-distro.xml are included in the book. Read the file - eltf_params_updated_template_how_to_use.txt - for important details about formats and how to do! The idea is that ELTF - will auto-create/update it. - Enea NFV Access for universal Customer Premise Equipment (uCPE) is a virtualization and management platform, which allows end-users to introduce, instantiate, and run third-party VNFs onto their systems. It is comprised of 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 9b1c740..636af3f 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 @@ -16,7 +16,7 @@ ELCCR-319After a successful installation or upgrade, the uCPE Manager will reboot. The time required for restarting - all its services is influenced by hardware configuration of the host + all its services is influenced by the hardware configuration of the host platform. @@ -60,7 +60,7 @@ ELCCR-577If a uCPEM is restored from a backup - made on an older release version than 2.2.3, VNFs cannot be instantiated + made on a release version older than 2.2.3, VNFs cannot be instantiated from the GUI. @@ -89,8 +89,8 @@ ELCCR-847The Juniper VNF cannot be instantiated 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. + domain XML. This impacts all example use cases and AF&TH tests where + the Juniper VNF is used. @@ -100,7 +100,7 @@ - LXCR-9853The WAN interface of uCPE device needs + LXCR-9853The WAN interface of a uCPE device needs to be connected to a network with at least a router/gateway installed for next-hop communication. @@ -120,28 +120,29 @@ 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 shall be used - instead for the entire IOMMU group. + drivers. The igb_uio driver must be used instead for + the entire IOMMU group. Driver selection for DPDK-assigned interfaces is a system-wide - configuration, therefore selecting igb_uio - or vfio-pci when adding a DPDK interface will not + configuration, therefore selecting igb_uio or + vfio-pci when adding a DPDK interface will not influence the actual driver used. In this release, NFV Access runtime - software is using vfio-pci driver by default, but + software uses the vfio-pci driver by default, but igb_uio can be used instead by providing custom scripting. Please contact Enea for further details. - Using both igb_uio driver for DPDK interfaces - and vfio-pci for SR-IOV/PCI-Passthrough is possible, - but not recomended, as it might not be supported by some hardware - configurations. + + Using both the igb_uio driver for DPDK + interfaces and the vfio-pci driver for + SR-IOV/PCI-Passthrough is possible, but not recomended, as these actions + might not be supported by some hardware configurations. When an in-band management bridge uses the igb_uio driver and the VM connected to the bridge has other interfaces that use the vfio-pci driver (e.g. SR-IOV/PCI-Passthrough), then the VM must be stopped before restarting - the vCPE service on the device - (systemctl restart vcpe). Rebooting the device does - not have this restriction. + the vCPE service on the device (systemctl restart + vcpe). Rebooting the device does not have this + restriction. @@ -151,7 +152,7 @@ - STCR-6292Management of WAN Interface is not + STCR-6292Management of WAN Interfaces is not implemented in the Automation Framework and Test Harness. diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/configuration.xml b/doc/book-enea-nfv-access-system-test-specification/doc/configuration.xml index 94bd4d9..4345326 100644 --- a/doc/book-enea-nfv-access-system-test-specification/doc/configuration.xml +++ b/doc/book-enea-nfv-access-system-test-specification/doc/configuration.xml @@ -8,7 +8,7 @@ The test objects for the Test Harness are the Enea NFV Access and Enea uCPE Manager installations performed as indicated in the Components chapter of Components chapter of the . @@ -18,7 +18,7 @@ Test Environment To set up the required Test Harness environment please refer to - chapter Getting Started with the Automation Framework and Test Harness in the and section Installation and Initial Setup in the Installation and Initial Setup in the + for more details. 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 6e54bd4..f4b2fc7 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 @@ -1498,23 +1498,22 @@ FortigateFWInstance tested successfully! - Section FortiGate VNF as a - Firewall in the + xpointer="element(book_enea_nfv_access_example_usecases/1)" + xmlns:ns="http://www.w3.org/2001/XInclude" /> Manual. - Section Python Unit-Test Suite in - . + . -- cgit v1.2.3-54-g00ecf