From 7b4b3aa65052b4459d6b35549b06351c55f47062 Mon Sep 17 00:00:00 2001 From: Matei Valeanu Date: Thu, 16 Apr 2020 17:46:19 +0200 Subject: doc: getting-started - updates Change-Id: Ifaf560f414173c59c9c765972ed8ef7d1a971da8 Signed-off-by: Matei Valeanu --- .../doc/advanced_configurations.xml | 43 --------- .../doc/getting_started_nfv_access.xml | 8 +- .../doc/getting_started_ucpe_manager.xml | 103 +++++++++++---------- 3 files changed, 56 insertions(+), 98 deletions(-) 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 160190f..afcdec6 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 @@ -346,33 +346,11 @@ node0.1048576kB = 3 - Optional parameters for sending status notifications to a - server. All three must be provided if used: - - - - notify_user. Server SSH username. - - - - notify_pass. Server SSH password. - - - - notify_path. Location where notification - files will be placed, specified in Server - IP:directory format. - - - Installation Configuration File Example: image_url = http://192.168.1.100/enea-nfv-access-xeon-d.hddimg.gz install_drive = /dev/sda - notify_user = username - notify_pass = password - notify_path = 192.168.1.100:/home/user/status_notifications @@ -415,27 +393,6 @@ node0.1048576kB = 3 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. - -
- Server Notifications - - Optionally, the uCPE devices can send a notification file to a - server once the installation is complete and Enea NFV Access Run Time - Platform has successfully booted. Notifications are enabled by - providing the notify_* parameters in the - installation configuration file. - - Each uCPE device will push a file to the server location - specified in the installation configuration file. The file name will - be the MAC address of the PXE boot network interface in order to - uniquely identify the device. - - - Note that the status notification will only be sent on the - first boot after installation is done, subsequent reboots of the - uCPE device will not cause any new notifications to be sent. - -
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 796c386..bb488a1 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 @@ -256,7 +256,7 @@ of=/dev/sdb bs=4M conv=fsync Once the USB stick is properly booted, the Web-installer application starts - automatically and can be accessed in a web browser at http://192.168.1.1 (port 80). + automatically and can be accessed in a web browser at http://172.16.1.1 (port 80). On the first page of the Web-installer, the user should fill in: @@ -332,12 +332,12 @@ of=/dev/sdb bs=4M conv=fsync If NFV Access was installed by Bare Metal Provisioning, the Web-installer will launch at start-up expecting the user to provide the post-installation configuration. The Web-installer will - be launched on port 82 for post-installation configuration: - http://192.168.1.1:82. + be launched on port 80 for post-installation configuration: + http://172.168.1.1. In case of failure, the user should remove all WAN cables, re-attach the laptop, reboot - the device and then access the Web-installer on http://192.168.1.1:82. + the device and then access the Web-installer on http://172.16.1.1. 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 733f61e..1940eb1 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 @@ -546,7 +546,7 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar - IP Address. IP address of the ucPE device. + IP Address. IP address of the uCPE device. @@ -580,10 +580,7 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar - Device ID. The unique identifier of the uCPE device. This - links a device to its Day-0 configuration (stored in the offline - configuration system). It is a required field if you want to - perform Zero-Touch Provisioning. + Device ID. The unique identifier of the uCPE device. @@ -593,12 +590,12 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar Follow the same steps as described in the previous section, making sure that the Device Calls Home checkbox is - selected this time. + selected this time. The IP Address of the uCPE device + is not required. 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. Make sure the uCPE Manager IP - address has been configured on the device. For more information please + Manager waits for a device connection. For more information please see section Installing Enea NFV Access for more details. @@ -612,22 +609,6 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar networking infrastructure can be configured either manually or by using Zero Touch Provisioning. - The uCPE Manager can list network interfaces found on a device by - selecting the uCPE device first and then selecting - Configuration -> OpenVSwitch - -> Host Interface Caps: - -
- Host Interface Caps - - - - - - -
- Available network interfaces can be added to the management system, for use by the networking virtualization infrastructure. @@ -636,17 +617,15 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar For Manual Configuration of uCPE networking, select the uCPE device first and then Configuration -> - OpenVSwitch. In Host Interfaces - Caps, one can find a list of available network interfaces - and their capabilities. + External Interfaces, where one can find a list of + available network interfaces and their capabilities.
Configuring Interfaces After networking interfaces have been added to the uCPE Manager, the user can change the interface type (DPDK, SR-IOV, - Standard) and the address assignment of the network interfaces - (DHCP, Static). + Standard, wan). How to Edit the Configuration of an Interface @@ -860,13 +839,6 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar - Create an OpenVSwitch bridge (ovsbr0) on - the device that uses a DPDK interface type, by selecting the uCPE - device, then from the top toolbar selecting - Configuration -> - OpenVSwitch -> Bridges - -> Add. - SR-IOV Interface Type SR-IOV technology allows for the creation of a number of @@ -1141,13 +1113,34 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar To create an offline configuration, from the top toolbar menu select Applications -> Offline - Config -> Add. Specify the value of - the Device ID in the required field or wildcard - if appropriate. Choose Merge as the "Default - Upload Method" if you do not want any boot configuration set on the - device, to be wiped out. Selecting Replace will - set the entire device configuration to match values in the offline - configuration. + Config -> Add. The following fields + are available: + + + + Name: name of the device. + + + + Device type: Enea universal CPE. + + + + Device version: 2.2.2 + + + + Config Set: uCPE Config + + + + Device ID: device ID or a wildcard(*). + + + + Device Grouping Tags: a tag to group devices. + + When a device connects to the uCPE Manager for the first time, it checks the device to see if it has been Zero Touch Provisioned @@ -1420,9 +1413,9 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar Click on Choose File to provide the path - to the image file. Select the target hardware platform - corresponding to the image being uploaded (xeon-d or - atomc-3000). + to the image file (must be of type rootfs.ostree.tar.bz2). + Select the target hardware platform corresponding to the image + being uploaded (xeon-d or atomc-3000). @@ -1488,8 +1481,7 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar minute for when to run the upgrade. - The time zone is set to Eastern Standard Time - (EST). The hour represents the local uCPE Manager server hour. + The hour represents the local uCPE Manager server hour. @@ -1895,6 +1887,11 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar name, and optionally a description, used only by the uCPE Manager. + + CAUTION: The user MUST conserve the same order for the + virtual interfaces during both onboarding and instantiation phases. + + Cloud Init Tab Click the Clout Init tab to provide the @@ -2045,7 +2042,11 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar - Device: the uCPE device to instantiate the VNF on. + VNF Type: a list of onboarded VNFs. + + + + uCPE Device: the uCPE device to instantiate the VNF on. @@ -2101,8 +2102,8 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar SSH to the uCPE device from the Enea uCPE Manager - (Device->SSH) with default user and password: - root. + (Device->SSH) using user: + root and no password. -- cgit v1.2.3-54-g00ecf