From 9217ccdf15ee0920c183b5e3e68c6dc7aca2734b Mon Sep 17 00:00:00 2001 From: Miruna Paun Date: Wed, 26 Jun 2019 12:02:07 +0200 Subject: Removed references to Portal and Solution in ENA docs where appropriate. Change-Id: Idcc466e9c2f4faaeaa5696cb4c24f595b87cab98 --- .../doc/book.xml | 2 +- .../doc/components.xml | 24 ++-- .../doc/getting_started.xml | 39 ++++--- .../doc/overview.xml | 7 -- .../doc/book.xml | 10 +- .../doc/clav_vnf_examples.xml | 121 +++++++++++---------- .../doc/enea_vnf_examples.xml | 102 ++++++++--------- .../doc/forti_vnf_examples.xml | 103 +++++++++--------- .../doc/inband_management.xml | 4 +- .../doc/introduction.xml | 14 +-- .../doc/vnf_chaining.xml | 23 ++-- .../doc/getting_started_nfv_access.xml | 2 +- .../doc/introduction.xml | 8 +- .../doc/about_release.xml | 21 ++-- .../doc/getting_enea_nfv_access.xml | 5 +- .../doc/overview.xml | 29 ++--- .../doc/sample_test_cases.xml | 43 ++++---- 17 files changed, 274 insertions(+), 283 deletions(-) diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml index c2b86f4..58b4650 100644 --- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml +++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml @@ -26,7 +26,7 @@ - + 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 bbfccd7..2fecf5b 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,9 +2,9 @@ Components - An overview of the Enea NFV Access Run Time Platform and the uCPE Manager in - cooperation with the Automation Framework and Test Harness, will be - presented in detail. + An overview of the Enea NFV Access Run Time Platform and the uCPE + Manager in cooperation with the Automation Framework and Test Harness, will + be presented in detail.
Component Overview @@ -20,8 +20,8 @@
Enea NFV Access - The Enea NFV Access is comprised of the Enea NFV Access - Run time Platform and the Enea uCPE Manager. + The Enea NFV Access is comprised of the Enea NFV Access Run time + Platform and the Enea uCPE Manager.
Enea uCPE Manager @@ -39,9 +39,9 @@
Enea NFV Access Run time Platform - One or more uCPE devices running the NFV Access Run Time Platform are - required as hosts running the VNF(s). The uCPE device is known to the uCPE Manager - as the "VcpeAgent" device module. + One or more uCPE devices running the NFV Access Run Time Platform + are required as hosts running the VNF(s). The uCPE device is known to + the uCPE Manager as the "VcpeAgent" device module. Adding a VcpeAgent device can be done via one of two methods: @@ -86,7 +86,7 @@ The Test Harness (TH) provides a way for driving configuration with Ansible Playbooks, by running the python modules from the Automation Framework (AF) and by direct connection over SSH to the boards that run - the Enea NFV Access solution. + Enea NFV Access. The Test Harness includes an automated test suite that contains: @@ -94,8 +94,8 @@ VNF, Device and Network Smoke Test Cases. A sample test suite - that acts as basic smoke tests for the Enea NFV Access and - also as a sanity-check test suite for the AF and TH. + that acts as basic smoke tests for the Enea NFV Access and also as a + sanity-check test suite for the AF and TH. @@ -115,4 +115,4 @@ chapter "Sample Test Cases" from the Enea NFV Access System Test Specification document.
- + \ 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 b3386b8..34c9308 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 @@ -101,9 +101,12 @@ Enea NFV Access Run Time Platform installed. - For information on how to install Enea NFV Access - refer to "Getting Started with Enea NFV Access" from the - Enea NFV Access Getting Started manual. + For information on how to install Enea NFV Access refer to + Getting Started with Enea NFV Access + in .
@@ -118,8 +121,8 @@
- Changes to 1st - uCPE device + Changes to 1st uCPE + device @@ -127,8 +130,8 @@ - 1 Physical connection back to back with the - 2nd uCPE device. + 1 Physical connection back to back with the + 2nd uCPE device. @@ -155,10 +158,12 @@ Enea NFV Access installed. - For information on how to install Enea NFV Accessthe - solution or the platform?, refer to "Getting Started with - Enea NFV Access" from the Enea NFV Access Getting Started - manual. + For information on how to install Enea NFV Access, refer to + Getting Started with Enea NFV + Access. @@ -167,9 +172,9 @@
Installation and Initial Setup - Download nfvaccess22_af-th.zip from the Enea - Portal and unzip it on the a supported host machine. Henceforth, the - directory in which the ZIP archive has been unpacked will be denoted as + Unzip the nfvaccess22_af-th.zip archive file, + provided by Enea, on a supported host machine. The directory in which the + archive has been unpacked will be denoted as <AF-TH-installdir>. Enter the <AF-TH-install-dir> directory and @@ -197,10 +202,10 @@ Run the setupuCPEManager.yml Ansible - Playbook with the JSON config path as parameter: ansible-playbook playbooks/setupuCPEManager.yml -e\ + Playbook with the JSON config path as parameter: ansible-playbook playbooks/setupuCPEManager.yml -e\ "@uCPEM_config/<config_name>.json" - Example ansible-playbook playbooks/setupuCPEManager.yml -e\ + Example ansible-playbook playbooks/setupuCPEManager.yml -e\ "@uCPEM_config/ucpem01.json" @@ -219,4 +224,4 @@ setupuCPEManager.yml playbook with the corresponding JSON config for the new uCPE Manager instance.
- + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml index 045ceef..1c85cfc 100644 --- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml +++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml @@ -44,13 +44,6 @@ Enea NFV Access (with ODM) Runtime Platform and Enea uCPE Manager. - - - Enea Portal - - https://portal.enea.com - diff --git a/doc/book-enea-nfv-access-example-usecases/doc/book.xml b/doc/book-enea-nfv-access-example-usecases/doc/book.xml index 0f69570..5071e01 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/book.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/book.xml @@ -17,19 +17,19 @@ - + - + - + - + - + diff --git a/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml index a73c5e8..570ea7a 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml @@ -19,8 +19,9 @@ - License for the Clavister VNF (needed as Cloud-Init content in the Cloud-Init tab). - This file is available through the VNF provider. + License for the Clavister VNF (needed as Cloud-Init content in + the Cloud-Init tab). This file is available through the VNF + provider.
@@ -45,19 +46,22 @@
uCPE device Setup - Configure Network interfaces on the uCPE devices: + Configure Network interfaces on the uCPE + devices: - From the uCPE Manager select uCPE device 1, then access Configuration - -> OpenVSwitch -> Host Interfaces -> - Add. + From the uCPE Manager select uCPE device 1, then access + Configuration -> + OpenVSwitch -> Host + Interfaces -> Add. - Select the network interface that will be used to connect to uCPE device 2. - Configure it for DPDK, and click Create to send the configuration - to that uCPE device. + Select the network interface that will be used to connect to + uCPE device 2. Configure it for DPDK, and click + Create to send the configuration to that uCPE + device. @@ -67,13 +71,13 @@ - Once the bridge creation popup appears, fill-in the required fields and add the - physical interface. + Once the bridge creation popup appears, fill-in the required + fields and add the physical interface. - Repeat the steps above on uCPE device 2, using one DPDK interface and creating - another OVS bridge. + Repeat the steps above on uCPE device 2, using one DPDK + interface and creating another OVS bridge.
@@ -83,8 +87,9 @@ - Select VNF -> Descriptor -> - On-board. + Select VNF -> + Descriptor -> + On-board. @@ -92,12 +97,14 @@ - Provide the path to the qcow image by selecting Browse - from VM image file option. + Provide the path to the qcow image by selecting + Browse from VM image file + option. - Fill the required fields below and press Onboard: + Fill the required fields below and press + Onboard: @@ -119,56 +126,61 @@
Instantiate the VNFs - A) Instantiate the Clavister VNF on uCPE device 1: + A) Instantiate the Clavister VNF on uCPE + device 1: - Select uCPE device 1, then from the top toolbar: VNF -> - Instances -> Add. + Select uCPE device 1, then from the top toolbar: + VNF -> Instances -> + Add. - Fill in the required information about the Clavister VNF, (the default network - configuration can be used) and select Create. + Fill in the required information about the Clavister VNF, (the + default network configuration can be used) and select + Create. - - B) Instantiate two Enea VNFs (one as the client and one as the - server) on uCPE device 2: - + + B) Instantiate two Enea VNFs (one as the + client and one as the server) on uCPE device 2: + - Select uCPE device 2, then from the top toolbar: VNF -> - Instances -> Add. + Select uCPE device 2, then from the top toolbar: + VNF -> Instances -> + Add. - In the new VNF Instance window, select the Enea VNF from the - dropdown menu, configure it to act as a server by unchecking the Client mode - IPerf box, and then click Create. + In the new VNF Instance window, select the + Enea VNF from the dropdown menu, configure it to act as a server by + unchecking the Client mode IPerf box, and then + click Create. - Select Add once more, enable the Client mode - IPerf checkbox this time, and click Create to instantiate - the second iPerf VNF as a client, and to run it in client mode. + Select Add once more, enable the + Client mode IPerf checkbox this time, and click + Create to instantiate the second iPerf + VNF as a client, and to run it in client mode. - In order to check that traffic is forwarded between the two VNFs, connect to the - iPerf VNF client console: SSH -> user (root) - -> Connect and run the following: - - - virsh list - virsh console - root@qemux86-64:~# iperf3 -c 192.168.10.10 - + In order to check that traffic is forwarded between the two + VNFs, connect to the iPerf VNF client console: + SSH -> user (root) -> + Connect and run the following: + + virsh list +virsh console +root@qemux86-64:~# iperf3 -c 192.168.10.10
- +
Clavister VNF using SR-IOV @@ -210,8 +222,9 @@ - Instantiate the Clavister VNF on uCPE device 2: VNF - -> Instances -> Add. + Instantiate the Clavister VNF on uCPE device 2: + VNF -> Instances -> + Add. @@ -251,16 +264,12 @@ In order to check that traffic is forwarded between the VNFs, connect to the iPerf VNF client console by using: SSH -> user (root) - ->Connect and run the following - commands: - - virsh list - virsh console - root@qemux86-64:~# iperf3 -c 192.168.10.10 - - + ->Connect and run the following commands: + virsh list +virsh console +root@qemux86-64:~# iperf3 -c 192.168.10.10
- + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-example-usecases/doc/enea_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/enea_vnf_examples.xml index f2d7910..ac4347c 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/enea_vnf_examples.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/enea_vnf_examples.xml @@ -5,19 +5,19 @@
Prerequisites - The following file(s) are needed for this example use-case: - enea-nfv-access-vnf-qemux86-64.qcow2. This image is - provided with your release. + The following file(s) are needed for this example use-case: + enea-nfv-access-vnf-qemux86-64.qcow2. This image is + provided with your release.
TestPMD VNF - In this use-case, uCPE device 1 will run pktgen - (the DPDK application) and uCPE device 2 will onboard - and instantiate two VNFs. One VNF will run testpmd_fwd, - forwarding traffic, and the other will run testpmd_term - which will terminate traffic. + In this use-case, uCPE device 1 will run pktgen + (the DPDK application) and uCPE device 2 will onboard + and instantiate two VNFs. One VNF will run testpmd_fwd, + forwarding traffic, and the other will run testpmd_term + which will terminate traffic.
Enea VNF Example Overview @@ -33,13 +33,13 @@
Example Setup - Configure the Network interface on uCPE - devices 1 and 2: + Configure the Network interface on uCPE + devices 1 and 2: - Bind the host interfaces to the DPDK by selecting uCPE device 1 - first, then accessing Configuration -> + Bind the host interfaces to the DPDK by selecting uCPE device + 1 first, then accessing Configuration -> OpenVSwitch -> Host Interfaces -> Add. @@ -62,26 +62,29 @@ Create an Open vSwitch bridge on uCPE device 1: - Create an Open vSwitch bridge (ovsbr0) on uCPE - device 1, that uses one DPDK interface: - - - Click the Add button from the - Bridges tab. - - - Select uCPE device 1, then access - Configuration ->OpenVSwitch - ->Bridges. - - + Create an Open vSwitch bridge (ovsbr0) on uCPE + device 1, that uses one DPDK interface: + + + + Click the Add button from the Bridges + tab. + + + + Select uCPE device 1, then access + Configuration ->OpenVSwitch + ->Bridges. + + Onboard the Enea VNF: - Select VNF ->Descriptor - -> On-board. + Select VNF + ->Descriptor -> + On-board. @@ -89,13 +92,14 @@ - Provide the path to the qcow image by selecting Browse - from the VM image file option. + Provide the path to the qcow image by selecting + Browse from the VM image file + option. - Fill the required fields below and press Onboard: - + Fill the required fields below and press + Onboard: @@ -113,16 +117,18 @@ - Instantiate two VNFs on uCPE device 2: + Instantiate two VNFs on uCPE device + 2: - Select uCPE device 2, then access VNF -> - Instances -> Add. + Select uCPE device 2, then access VNF -> + Instances -> Add. - Fill-in the required fields and click Create. + Fill-in the required fields and click + Create. @@ -160,15 +166,14 @@ - Start pktgen on uCPE device 1. Connect to the device by selecting - it first, then access SSH -> user - (root) and perform the following: + Start pktgen on uCPE device 1. Connect to the device by + selecting it first, then access SSH -> + user (root) and perform the following: - - cd /usr/share/apps/pktgen/ - ./pktgen -c 0x7 -n 4 --proc-type auto --socket-mem 256 -w 0000:05:00.3 -- \ - -P -m "[1:2].0" - Pktgen:/> start 0 + cd /usr/share/apps/pktgen/ +./pktgen -c 0x7 -n 4 --proc-type auto --socket-mem 256 -w 0000:05:00.3 -- \ +-P -m "[1:2].0" +Pktgen:/> start 0 The PCI address <0000:05:00.3> used in this example @@ -183,11 +188,10 @@ statistics, by selecting the uCPE device first, then accessing SSH -> user (root): - - Virsh list - Virsh console 1 - # Qemux86-64 login: root - tail -f /var/log/testpmd-out + Virsh list +Virsh console 1 +# Qemux86-64 login: root +tail -f /var/log/testpmd-out
Traffic Statistics @@ -280,4 +284,4 @@ Run: tail -f /opt/testpmd-out
- + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml index cc158fe..8174aa1 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml @@ -7,11 +7,14 @@ appliances. The virtual appliances can be integrated in Firewall or SD-WAN solution development. - Enea provides a prepared VNF bundle for download from the Enea Portal, - for usage with the Enea NFV Access product. The prepared VNF bundle includes - the FortiGate VNF image as well as a VNF Descriptor and other onboarding - related configuration files. The VNF Descriptor provided configures a setup, - which requires the following resources: +
+ Prerequisites + + Enea provides a prepared VNF bundle for usage with the Enea + NFV Access product. The bundle includes the FortiGate VNF image as well + as a VNF Descriptor and other onboarding related configuration files. + The VNF Descriptor provided configures a setup, which requires the + following resources: @@ -29,19 +32,20 @@ The VNF Descriptor represents one specific setup, suitable for usage with the Firewall and SD-WAN VPN instructions in this guide. Alternative VNF - Descriptor configurations may be needed to support other configurations - required by the customer. + Descriptor configurations may be needed to support other setups + desired by the customer. Enea can offer assistance and provide alternative VNF Descriptor configurations. - While the prepared FortiGate bundle is available through the Enea Portal, - additional content needs to be received from Fortinet directly. The - FortiGate VNF license as well as any FortiGate specific documentation - shall be requested from the local Fortinet sales representatives in your - region, before FortiGate can be used. + While the prepared FortiGate bundle is available from Enea, + additional content needs to acquired directly from Fortinet. The + FortiGate VNF license file as well as any FortiGate specific documentation + is available from the local Fortinet sales representatives in your + region, and must be requested before FortiGate can be used. +
FortiGate VNF as a Firewall @@ -53,8 +57,7 @@ networks, and provides security ratings to adopt security best practices. - An example firewall configuration for the FortiGate VNF is provided - in the Enea Portal. It is a simple firewall base configuration. + Enea provides an example of a simple base firewall configuration for the FortiGate VNF. FortiGate VNF Example Configuration @@ -227,16 +230,12 @@ - Download the FortiGate VNF Bundle from the Enea Portal - to the Lab Machine file system. Please see the Download - Chapter for more details. + Copy the FortiGate VNF Bundle provided by Enea to the Lab Machine file system. - Download FortiGate configuration examples from the - Enea Portal to the Lab Machine file system. Please check the - Download Chapter for more details. Unpack the configuration - examples on the Lab Machine. + Copy the FortiGate configuration examples from Enea to the Lab Machine file system. Unpack the configuration + examples onto the Lab Machine. @@ -337,7 +336,7 @@ Create one Open vSwitch bridge for each firewall network connection (WAN, LAN1 and LAN2), by selecting: Configuration -> - OpenVSwitch -> Bridges -> Add. + OpenVSwitch -> Bridges -> Add. A popup like the following should appear:
@@ -381,7 +380,7 @@ - Click Browse to view selections, and choose the + Click Browse to view selections, and choose the Fortigate.zip file, before clicking Send. @@ -464,7 +463,7 @@ Configuration file - Firewall example configuration file provided by Enea + Firewall example configuration file provided by Enea (FGVM080000136187_20180828_0353_basic_fw.conf ). @@ -472,7 +471,7 @@ Port1 - WAN - Set the External Interface type to Dpdk and connect it to the + Set the External Interface type to Dpdk and connect it to the wanmgrbr ovs bridge. @@ -497,12 +496,12 @@ Testing the FortiGate Firewall - Connect the Test Machine on the LAN interfacewhich lan interface? + Connect the Test Machine on the LAN interfacewhich lan interface? and access the internet from the Test Machine to use the firewall on the uCPE device. - The connected Test Machine can be a laptop or a uCPE device. It must have one - interface configured to get a dynamic IP from a DHCP server. The + The connected Test Machine can be a laptop or a uCPE device. It must have one + interface configured to get a dynamic IP from a DHCP server. The dhclient <interface> command can be used to request an IP address. The received IP must be in the 172.16.1.2 - 172.16.1.255 range. @@ -519,25 +518,25 @@
- In the example abovewhat example exactly, in the overview picture or?, - the FortiGate VNF management interface is accessible through the WAN interface. The - WAN IP address can be used from a web browser on the Lab Machine to access the - Fortigate VNF Management Web UI. Please check the Fortigate VNF web management section + In the example abovewhat example exactly, in the overview picture or?, + the FortiGate VNF management interface is accessible through the WAN interface. The + WAN IP address can be used from a web browser on the Lab Machine to access the + Fortigate VNF Management Web UI. Please check the Fortigate VNF web management section for more information.Note to self: An olink is needed to this section in this book, use fortigate_webmg as the ID. In another example, the firewall can be setup to use bridges as - connection points for the Fortigate VNF. It is possible to replace these + connection points for the Fortigate VNF. It is possible to replace these OVS-DPDK bridges with SR-IOV connection points. Please check the network - configuration chapter on how to configure an interface for SR-IOV.An olink + configuration chapter on how to configure an interface for SR-IOV.An olink is needed but I can't add it without clarifying which chapter do you refer to? It was previously assumed that three physical interfaces are - available for VNF connection. In the case of a firewall setup only two physical interfaces - are needed for the data path (one for WAN and one for LAN).Is this the meaning you + available for VNF connection. In the case of a firewall setup only two physical interfaces + are needed for the data path (one for WAN and one for LAN).Is this the meaning you intented to convey in this sentence? - - In the example below only two interfaces will be configured as DPDK, with two + + In the example below only two interfaces will be configured as DPDK, with two bridges created, one for each type of connection. Please note that at VNF instantiation instead of assigning distinct bridges for each @@ -585,7 +584,7 @@ - To access Fortigate CLI, use admin as the user, + To access Fortigate CLI, use admin as the user, leaving the password blank/empty, and press enter. Use the CLI command get system interface to @@ -679,7 +678,7 @@ applied to WAN connections. It connects enterprise networks, including branch offices and data centers, over large geographic distances. - SD-WAN decouples the network from the management plane, detaching + SD-WAN decouples the network from the management plane, detaching traffic management and monitoring functions from hardware. Most forms of SD-WAN technology create a virtual overlay that is transport-agnostic, i.e. it abstracts underlying private or public WAN connections. With an @@ -694,7 +693,7 @@ Example SD-WAN configurations for the FortiGate VNF are provided - in the Enea Portal. + by Enea.
@@ -928,14 +927,12 @@ - FortiGate VNF Bundle downloaded from the Enea Portal - to the Lab Machine file system. + FortiGate VNF Bundle copied from Enea to the Lab Machine file system. - FortiGate configuration examples downloaded from the Enea - Portal to the Lab Machine file system. Unpack the configuration - examples specific for SD-WAN on the Lab Machine. + FortiGate configuration examples from Enea, copied to the Lab Machine file system. Unpack the configuration + examples specific for SD-WAN onto the Lab Machine. @@ -1009,7 +1006,7 @@ - Repeat this step for the other two interfaces. The result of a successful binding + Repeat this step for the other two interfaces. The result of a successful binding should look like the following:
@@ -1026,8 +1023,8 @@ Create an Open vSwitch bridge for each SD-WAN network connection - (VNF management, WAN and LAN) by selecting the uCPE device then: - Configuration -> OpenvSwitch -> + (VNF management, WAN and LAN) by selecting the uCPE device then: + Configuration -> OpenvSwitch -> Bridges -> Add. A popup will appear:
@@ -1106,14 +1103,14 @@ Instantiating the FortiGate VNF - - Download locally the valid license files for the Fortigate VNF from + + Download locally the valid license files for the Fortigate VNF from Fortinet and the configuration file provided by Enea as examples. - Select a uCPE device on the map, then from the top toolbar click + Select a uCPE device on the map, then from the top toolbar click VNF -> Instances -> Add:
@@ -1192,7 +1189,7 @@ Configuration file(s) - SD-WAN example configuration files provided by Enea: + SD-WAN example configuration files provided by Enea: FGVM080000136187_20180215_0708_sdwan1.conf FGVM080000136188_20180215_0708_sdwan2.conf diff --git a/doc/book-enea-nfv-access-example-usecases/doc/inband_management.xml b/doc/book-enea-nfv-access-example-usecases/doc/inband_management.xml index 3aea4f5..a15b7d5 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/inband_management.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/inband_management.xml @@ -31,7 +31,7 @@ - For prerequisites and further details, please see + For prerequisites and further details, please see and Are these references still valid?.
@@ -261,7 +261,7 @@ - If you have access from the uCPE Manager to the device as shown above, this + If you have access from the uCPE Manager to the device as shown above, this demonstrates that device management traffic passes through the In-band management WAN bridge successfully. diff --git a/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml b/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml index 208cd0e..91e15aa 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml @@ -2,16 +2,16 @@ Introduction - This document describes several example use-cases concerning uCPE device - network interface configuration, onboarding and instantiation of certain VNFs, + This document describes several example use-cases concerning uCPE device + network interface configuration, onboarding and instantiation of certain VNFs, VNF chaining, and In-band management. - - Before running any example make sure the uCPE device(s) have been + + Before running any example make sure the uCPE device(s) have been added to the uCPE Manager and placed on the map. - - For detailed information on how to add a device to the uCPE Manager, how - to configure the network interfaces to use DPDK, PCI-passthrough or SR-IOV drivers, + + For detailed information on how to add a device to the uCPE Manager, how + to configure the network interfaces to use DPDK, PCI-passthrough or SR-IOV drivers, or VNF configuration, please refer to the Manual. diff --git a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml index 412af4a..90bf566 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml @@ -28,7 +28,7 @@ + scale="88" />
@@ -52,19 +52,16 @@
- Fortigate VNF image. This VNF can be downloaded from Enea portal. + Fortigate VNF image. This image is provided by Enea. - vSRX-domain-update-script. This file can be downloaded from - Enea portal. + vSRX-domain-update-script. This file is provided by Enea. - FortiFW-Site<x>.conf as Cloud-Init files. This file can be - downloaded from Enea - portal. + FortiFW-Site<x>.conf as the Cloud-Init file(s). This file + is provided by Enea. @@ -292,8 +289,10 @@ Before testing LAN to LAN connectivity, preliminary tests of service can be run to ensure everything was set up properly. - Before testing LAN to LAN connectivity, one can run preliminary tests of service to ensure everything was -set-up properly. For instance, by connecting to vSRX CLI (any site), one can test IKE security associations: + Before testing LAN to LAN connectivity, one can run preliminary + tests of service to ensure everything was set-up properly. For instance, + by connecting to vSRX CLI (any site), one can test IKE security + associations: root@Atom-C3000:~ # cli @@ -373,7 +372,7 @@ disable type: physical netflow-sampler: disable sflow-sampler: disable be checked (from Site1) as such:
root@atom-c3000:~# ping 172.10.10.2 -PING 172.10.10.1 (172.10.10.2): 56 data bytes +PING 172.10.10.1 (172.10.10.2): 56 data bytes ... @@ -397,4 +396,4 @@ PING 172.10.10.1 (172.10.10.2): 56 data bytes - + \ 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 9b28c88..7a30f28 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 @@ -207,7 +207,7 @@ rootfs_destination= - Download the HDDIMG file from the download portal onto a + Copy the HDDIMG image file provided by Enea, onto a development machine (Linux or Windows with Cygwin support). 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 e2e9802..c6a4f04 100644 --- a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml +++ b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml @@ -16,12 +16,12 @@ 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. The solution is - comprised of two major components working in close cooperation: + instantiate, and run third-party VNFs onto their systems. It is comprised of + two major components working in close cooperation: - The Enea NFV Access Run Time Platform, which acts as the host for + The Enea NFV Access Run-Time Platform, which acts as the host for Virtualized Network Functions (VNFs) and provides management over NETCONF. @@ -92,4 +92,4 @@ - + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-release-info/doc/about_release.xml b/doc/book-enea-nfv-access-release-info/doc/about_release.xml index e24ae38..d179765 100644 --- a/doc/book-enea-nfv-access-release-info/doc/about_release.xml +++ b/doc/book-enea-nfv-access-release-info/doc/about_release.xml @@ -142,7 +142,7 @@ Access release content. - + . @@ -153,8 +153,8 @@ . - Describes how to install the uCPE Manager, the NFV Access platform and - Device Management. + Describes how to install the uCPE Manager, the NFV Access Run-Time + platform and Device Management. @@ -165,7 +165,7 @@ various VNFs. - + Enea NFV Access VNF Onboarding Guide. Describes the process of onboarding a new VNF onto the uCPE Manager. @@ -186,14 +186,15 @@ Enea NFV Access Automation Framework and Test Harness User - Guide. Describes the Automation Framework and Test Harness for the - Enea NFV Access Solution and provides instructions regarding the - necessary steps to run these software tools. + Guide. Describes the Automation Framework and Test Harness for Enea + NFV Access and provides instructions regarding the necessary steps to + run these software tools. - - Enea NFV Access System Test Specification. + + Enea NFV Access System Test Specification. Describes a sample + Test Suite for System Testing of Enea NFV Access. - + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml b/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml index 4975ca3..9eecd3c 100644 --- a/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml +++ b/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml @@ -5,11 +5,10 @@ Getting Enea NFV Access Enea NFV Access releases and updates are available as binaries ready - for download from the Enea Download - Portal. + for download. Downloading Enea NFV Access - +Does the content below need to be revised to no longer make reference or mention to Enea Portal? Log in to the link above using the credentials provided by diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml b/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml index 7df9acc..f89f8bd 100644 --- a/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml +++ b/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml @@ -2,18 +2,10 @@ Overview - This document specifies a Sample Test Suite for System Testing of the - Enea NFV Access Solution. It also provides information regarding the - necessary steps to run these tests. - -
- Scope - - The scope of this document is to describe the Test Harness (TH) - sample test cases for System Testing of the Enea NFV Access Solution. - Furthermore, this document shall also describe the necessary environment - setup to run these tests successfully. -
+ The scope of this document is to describe the Test Harness (TH) sample + test cases for System Testing of Enea NFV Access. Furthermore, this document + shall also describe the necessary environment setup to run these tests + successfully.
Definitions and Acronyms @@ -34,17 +26,10 @@
- Enea NFV Access Solution - - Enea NFV Access (with ODM) Runtime Platform and Enea uCPE - Manager. - - - - Enea Portal + Enea NFV Access - https://portal.enea.com + The Enea NFV Access (with ODM) Run-time Platform and the + Enea uCPE Manager. 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 50907ca..ec2e592 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 @@ -9,8 +9,8 @@ VNF, Device and Network Smoke Test CasesThe following is an automated test suite that acts as basic smoke - tests for the Enea NFV Access Solution and as a sanity-check test suite - for the AF and TH. + tests for Enea NFV Access, and as a sanity-check test suite for the AF and + TH.
VNF - Onboard_VNF_Image @@ -322,8 +322,8 @@ bridge=<Bridge-name>" VNF Deployment and Lifecycle The following details the automated suite that handles the testing - of the instantiation, lifecycle and destruction of a VNF for the Enea NFV - Access Solution. + of the instantiation, lifecycle and destruction of a VNF for Enea NFV + Access.
Instantiate_VNFI @@ -467,10 +467,9 @@ Invalid VNF Instance control command specified - <Command> For more information please refer to "FortiGate VNF as a Firewall" - chapter from the "Enea NFV Access Example Use-cases" manual. + chapter from the "Enea NFV Access Example Use-cases" manual. The license and configuration files for the FortiGate VNF are - not included in the TH and should be obtained from the user's Enea - Portal account. + not included in the TH and should be obtained from Enea.
@@ -542,15 +541,15 @@ ansible_user=root ansible_pass=root Download the FortiGate VNF Firewall basic configuration from - the Enea Portal, copy it into the + Enea, copy it into the <AF-TH-install-dir>/vnf_config/fortigateImage directory and rename it to fortigateFW.conf. - Retrieve the FortiGate VNF license from Fortinet or the Enea - Portal, copy it into the + Retrieve the FortiGate VNF license from Fortinet or Enea, + copy it into the <AF-TH-install-dir>/vnf_config/fortigateImage directory and rename it to fortigateLicense.lic. @@ -636,15 +635,15 @@ FortigateFWInstance tested successfully! Download the FortiGate VNF Firewall basic configuration from - the Enea Portal, copy it into the + Enea, copy it into the <AF-TH-install-dir>/vnf_config/fortigateImage directory and rename it to fortigateFW.conf. - Retrieve the FortiGate VNF license file from Fortinet or the - Enea Portal, copy it into the + Retrieve the FortiGate VNF license file from Fortinet or + Enea, copy it into the <AF-TH-install-dir>/vnf_config/fortigateImage directory and rename it to fortigateLicense.lic. @@ -796,33 +795,33 @@ ansible_pass=root - Download the FortiGate VNF Firewall basic configuration files - from the Enea Portal (FortiFW-Site1.conf and + Retrieve the FortiGate VNF Firewall basic configuration files + from Enea (FortiFW-Site1.conf and FortiFW-Site2.conf), and copy them into the <AF-TH-install-dir>/vnf_config/fortigateFWImage directory. - Retrieve the FortiGate VNF license from Fortinet or the Enea - Portal, copy it into the + Retrieve the FortiGate VNF license from Fortinet or Enea, copy + it into the <AF-TH-install-dir>/vnf_config/fortigateFWImage directory and rename it to fortigateLicense.lic. - Download the Juniper vSRX basic configuration files from the - Enea Portal (vSRX-Site1.iso and + Retrieve the Juniper vSRX basic configuration files from Enea + (vSRX-Site1.iso and vSRX-Site2.iso), and copy them into the <AF-TH-install-dir>/vnf_config/junipervSRXImage directory. - Download vSRX-domain-update-script from - the Enea Portal and copy it into the - junipervSRXImage directory. + Retrieve vSRX-domain-update-script from + Enea and copy it into the junipervSRXImage + directory. Please refer to the "VNF Chaining Example Use-case" chapter from the Enea NFV Access Example Use-cases manual for additional -- cgit v1.2.3-54-g00ecf