From 729309c771f257bf768260609d7c917417497658 Mon Sep 17 00:00:00 2001 From: mrpa Date: Tue, 20 Jul 2021 19:48:13 +0200 Subject: Updated the release notes main changes file and edited a path in the known issues and limitations. Change-Id: I920e4d8d042b00906471ca843c9b43b269ef9235 Signed-off-by: mrpa --- .../doc/installation_guide.xml | 2 +- .../doc/known_bugs_and_limitations.xml | 49 +++---- .../doc/main_changes.xml | 155 ++++++++++++++------- 3 files changed, 132 insertions(+), 74 deletions(-) diff --git a/doc/book-enea-edge-getting-started/doc/installation_guide.xml b/doc/book-enea-edge-getting-started/doc/installation_guide.xml index 2e1fe7e..53d883f 100644 --- a/doc/book-enea-edge-getting-started/doc/installation_guide.xml +++ b/doc/book-enea-edge-getting-started/doc/installation_guide.xml @@ -1188,7 +1188,7 @@ of=/dev/sdb bs=4M conv=fsync
- Basic operations for uCPE device Managememt + Basic operations for uCPE device Management When the uCPE device is connected to the Enea Edge Management application, it can be rebooted, the factory settings can be restored or diff --git a/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml index d6e04ce..08e3e0d 100644 --- a/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml +++ b/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml @@ -19,9 +19,9 @@ - ELCCR-527Canceling a file upload in the Enea - Edge Management will require the user to close and reopen the upload - window for the next upload to work. + ELCCR-527Canceling a file upload in the Enea Edge + Management will require the user to close and reopen the upload window + for the next upload to work. @@ -29,11 +29,11 @@ is restored from a backup made on a release version older than Enea NFV Access 2.2.3, VNFs cannot be instantiated from the GUI. - + - ELCCR-1134In order to avoid an incorrect boot - order after a failed upgrade, the user should remove the upgrade - image before attempting again. + ELCCR-1134In order to avoid an incorrect boot + order after a failed upgrade, the user should remove the upgrade image + before attempting again. @@ -67,11 +67,11 @@ to be connected to a network with at least a router/gateway installed for next-hop communication. - + - ELCCR-1504To change the type of an interface - from DPDK to SR-IOV, first delete the existing interface, then - recreate it with the desired type. + ELCCR-1504To change the type of an interface from + DPDK to SR-IOV, first delete the existing interface, then recreate it + with the desired type. @@ -85,9 +85,9 @@ - STCR-6224The Enea Edge Automation Framework and - Test Harness do not support multiple custom scripts uploaded to a uCPE - device at the same time. + STCR-6224The Enea Edge Automation Framework and + Test Harness do not support multiple custom scripts uploaded to a uCPE + device at the same time. @@ -124,9 +124,10 @@ - ELCCR-1561Before starting an Enea Edge Management - upgrade, any owned Tomcat certificates should be manually copied into the - /opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/config/certificates + ELCCR-1565Before starting an Enea Edge Management + upgrade, any owned Tomcat certificates should be manually copied into + the + /opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/certificates folder. @@ -136,14 +137,14 @@ to delete the old interfaces and recreate them with the desired type. - + - ELCCR-1497If the Enea Edge Management application - has an incorrect database configuration, when performing an uninstallation, - the Tomcat instance and Watchdog service will not be stopped automatically. - Instead, they must be killed explicitly. + ELCCR-1497If the Enea Edge Management application + has an incorrect database configuration, when performing an + uninstallation, the Tomcat instance and Watchdog service will not be + stopped automatically. Instead, they must be killed explicitly. - + ELCCR-1468When using the Enea Edge Management application in HTTPS mode, upgrading a device from NFV Access 2.3.0 is @@ -171,4 +172,4 @@ - + \ No newline at end of file diff --git a/doc/book-enea-edge-release-info/doc/main_changes.xml b/doc/book-enea-edge-release-info/doc/main_changes.xml index 63e2c47..c686278 100644 --- a/doc/book-enea-edge-release-info/doc/main_changes.xml +++ b/doc/book-enea-edge-release-info/doc/main_changes.xml @@ -15,60 +15,58 @@ - CPDX-3496Embedded Wi-Fi support for all-in-one - store/home office deployment. For more details please see the Wap Interface Type in the - Manual. + Support for Fully Qualified Domain Names (FQDN) for the Enea Edge + Management application address. For more details + please see Preparing the Deployment in the + Manual. - CPDX-3499Expanded hardware, OS and network - monitoring capability with Grafana integration. For more details - please see Using Grafana and InfluxDB in the - Manual. + Support for a DNS servers list in the case of + static WAN interfaces, to resolve the FQDN used by the Enea Edge Management + application. For more details please + see Installing Enea Edge - uCPE Device Installation + in the + Manual. - CPDX-3407HTTPS based downloads of VNFs for - simplified deployment of the Enea Edge Management application in cloud - environments. For more details please see Fresh Installation of the Enea Edge - Management application in the + Support for NFV Infrastructure backup and restore to allow for recovery + to a previously known state. For more details please see NFV Infrastructure Backup Operations + in the Manual. - CPDX-3500Enea Edge Automation, a tool for - automatic system configuration based on Python scripting that will - replace the existing Enea Edge Automation Framework and Test Harness - in the next major release. For more details please see the . + Support for VNF snapshotting to allow for storing, managing and + restoring snapshots of VNFs deployed on Enea Edge Runtime. For more details + please see VNF Snapshots + in the Manual. + + - - The Enea Edge Automation Framework and Test Harness, and its - related documentation the and - the - are deprecated starting with Enea Edge 2.4.0. - + + Support for a Factory Reset to allow reverting of the Enea Edge Runtime + to its initial state. For more details please see Basic operations for uCPE device Management + in the Manual. @@ -76,18 +74,77 @@ - A new Requirements page has - been added to the Web-installer, displaying device characteristics and - checking minimal hardware requirements. + Added support for uploading multiple custom scripts on a uCPE Device + in the Enea Edge Automation framework. + + + + Python APIs from the Enea Edge Automation framework can now be run + with a limited set of optional parameters. + + + + Configuration files from the Enea Edge Automation framework can now + be generated in a non-interactive way with a limited set of optional + parameters. + + + + The Enea Edge Management application represents the new name for + the uCPE Manager component. + + + + Improved support for large deployments of Enea Edge: addressed + possible connectivity issues, added call-home tuning + parameters. + + + + Increased the wait time from 5 minutes to 10 minutes after an + Enea Edge Runtime upgrade. + + + + Improved the upgrade and uninstall processes of the Enea Edge + Management component: the database information is no longer requested + during an upgrade or an uninstall. + + + + Improved the Events feature by discarding logging of the + NetconfSessionStart and the + NetconfSessionEnd notifications. - A Web-installer's log is displayed on the last page in case the - installation process has failed. + Enea Edge Runtime key component upgrades include: + + + Linux kernel 5.10 + + + + Open vSwitch 2.15 + + + + QEMU 5.2.0 + + + + libvirt 6.3.0 + + + + DPDK 2.11.0 + + - Extended Web-installer support for NVME disks. + Python3 (v3.9.4) replaced Python2 support in Enea Edge + Runtime. -- cgit v1.2.3-54-g00ecf