Below you'll find information about the new features and updates made in this release, as well as details on the provided packages and the backwards compatibility with previous versions of Enea NFV Access if applicable.

Use of OpenJDK as the Java Engine in the uCPE Manager. USB Installer Web User Interface. Support of ZTP extensions through custom scripting. Support for uCPE device software management from the Enea uCPE Manager. Support for Layer 3 networking configuration from the Enea uCPE Manager.

For more information about the Open Source packages included, please refer to the Enea NFV Access Open Source Reports provided with this release.

In the development of any complex software platform, there is a need to strike a balance between backwards compatibility and new development. In most cases, compatibility will be maintained as long as reasonably possible. Necessary compatibility breaks will be done only as needed and in major releases. LXCR-9773The following REST API changes have been made: The uploadCustomScript() method included in the CustomScripts module takes in an additional argument (device module name). A new -- upload() -- method has been added to the Device Upgrade module to allow for uploads of NFV Access software images to the uCPE Manager. A new -- upload() -- method has been added to the VnfManager module to allow uploads of VNF images to the uCPE Manager as part of the onboarding process. The VcpeAgent (i.e. the NFV Access device module) was redesigned: The system-attributes config table was split into system-attributes-state (operational data) and system-attributes (configuration data). The configuration data still contains the attributes: device-name, device-description and initial-configuration-complete. The fields device-type, device-version, device-id, device-latitude, and device-longitude are now operational data. device-ip-address has been added as oper data. The customer-tag in release version 2.2.1 was a config leaf-list, it is now a leaf called device-customer-tags (comma-separated). The mgmt-ip-address has been added as oper data. This attribute was configured within an ovs-bridge of type inband-mgmt. The external-interface-capabilities operational table now has wan and mgmt Booleans. The external-interface configuration table now has a choice of wan. New fields for this type are mgmt-interface, address-assignment, ip-address, gateway, and netmask (only considered if static). In an ovs-bridge, for the choice of inband-mgmt, the mgmt-address and mgmt-port fields have been removed (there are no fields left in this choice). In the Host operational table, there are a couple of changes: The name field has been removed, however, there is still a host-name field. A machine-type field has been added. REST clients should see only some minor changes when upgrading from NFV Access 2.2.1 to NFV Access 2.2.2. Code that deals with the system-attributes table, in-band management OVS bridges, or the host operational data may need to be modified. The new WAN interface type needs a wan-mgmt interface configured to create the in-band mgmt bridge. This should typically happen automatically as part of initial installation or upgrade and should not affect the REST clients.