This repository has been archived by the owner on Oct 23, 2021. It is now read-only.
Releases: smart-edge-open/common
Releases · smart-edge-open/common
OpenNESS 20.12.02 Release
Merge pull request #9 from open-ness/openness_release_2009 Openness release 2009
OpenNESS 20.12.01 Release
Merge pull request #9 from open-ness/openness_release_2009 Openness release 2009
OpenNESS 20.12 Release
OpenNESS - 20.12
- Reference Converged Edge Reference Architecture (CERA) On-Premises Edge and Private Wireless deployment focusing on On-Premises, Private Wireless and Ruggedized Outdoor deployments, presenting a scalable solution across the On-Premises edge.
- Reference deployment with Kubernetes enhancements for High performance compute and networking for an SD-WAN node (Edge) that runs Applications, Services, and SD-WAN CNF. AI/ML applications and services are targeted in this flavor with support for Hardware offload for inferencing.
- Reference deployment with Kubernetes enhancements for high-performance compute and networking for an SD-WAN node (Hub) that runs SD-WAN CNF.
- Reference deployment for high-performance Computing and Networking using SR-IOV for reference Untrusted Non-3GPP Access as defined by 3GPP Release 15.
- Reference implementation of the offline installation package for the CERA Access Edge flavor enabling installation of Kubernetes and related enhancements for Access edge deployments.
- Early access release of Edge Multi-Cluster Orchestration(EMCO), a Geo-distributed application orchestrator for Kubernetes. This release supports EMCO deploying and managing the life cycle of the Smart City Application pipeline on the edge cluster. More details in the EMCO Release Notes.
- Azure Development kit (Devkit) supporting the installation of an OpenNESS Kubernetes cluster on the Microsoft* Azure* cloud. This is typically used by a customer who wants to develop applications and services for the edge using OpenNESS building blocks.
- Support Intel® vRAN Dedicated Accelerator ACC100, Kubernetes Cloud-native deployment supporting higher capacity 4G/LTE and 5G vRANs cells/carriers for FEC offload.
- Major system Upgrades: Kubernetes 1.19.3, CentOS 7.8, Calico 3.16, and Kube-OVN 1.5.2.
OpenNESS 20.09.01 Release
Merge pull request #9 from open-ness/openness_release_2009 Openness release 2009
OpenNESS 20.09 Release
OpenNESS – 20.09
- Service Mesh support
- Basic support for Service Mesh using istio within an OpenNESS cluster
- Application of Service Mesh openness 5G and Media analytics - A dedicated network for service to service communications
- EAA Update
- EAA microservices has been updated to be more cloud-native friendly
- 5G Core AF and NEF
- User-Plane Path Change event notifications from AF received over N33 I/f [Traffic Influence updates from SMF received through NEF]
- AF/NEF/OAM Configuration and Certificate updates through Configmaps.
- AF and OAM API’s access authorization through Istio Gateway.
- Envoy Sidecar Proxy for all the 5G microservices(AF/NEF/OAM/CNTF) which enables support for telemetry(Request/Response Statistics), certificates management, http 2.0 protocol configuration(with/without TLS)
- Core-cplane flavor is enabled with Istio
- Edge Insights Application (update)
- Industrial Edge Insights Software update to version 2.3.
- Experience Kit now supports multiple detection video’s – Safety equipment detection, PCB default detection and also supports external video streams.
- CERA Near Edge
- Core network and Application reference architecture
- CERA provides reference integration of OpenNESS, Network function 5G UPF (Not part of the release), OpenVINO with EIS application.
- Native On-premises mode
- Following from the previous release decision of pausing Native on-premises Development the code has been move to a dedicated repository “native-on-prem”
- Kubernetes based solution will now support both Network and on-premises Edge
OpenNESS 20.06.01 Release
Merge pull request #7 from open-ness/openness_release_2006 Openness release 2006
OpenNESS 20.06 OVN Fix
Merge pull request #7 from open-ness/openness_release_2006 Openness release 2006
OpenNESS 20.06 Release
OpenNESS – 20.06
- OpenNESS is now available in two distributions
- Open source (Apache 2.0 license)
- Intel Distribution of OpenNESS (Intel Proprietary License)
- Includes all the code from the open source distribution plus additional features and enhancements to improve the user experience
- Access requires a signed license. A request for access can be made at openness.org by navigating to the “Products” section and selecting “Intel Distribution of OpenNESS”
- Both distributions are hosted at github.com/open-ness
- On premises configuration now optionally supports Kubernetes
- Core Network Feature (5G)
- Policy Authorization Service support in AF and CNCA over the N5 Interface(3GPP 29.514 - Chapter 5 Npcf_PolicyAuthorization Service API).
- Core Network Notifications for User Plane Path Change event received through Policy Authorization support in AF.
- NEF South Bound Interfaces support to communicate with the Core Network Functions for Traffic Influence and PFD.
- Core Network Test Function (CNTF) microservice added for validating the AF & NEF South Bound Interface communication.
- Flavors added for Core Network control-plane and user-plane.
- OpenNESS assisted Edge cloud deployment in 5G Non Stand Alone mode whitepaper.
- OpenNESS 20.06 5G features enablement through the enhanced-OpenNESS release(IDO).
- Dataplane
- Support for Calico eBPF as CNI
- Performance baselining of the CNIs
- Visual Compute and Media Analytics
- Intel Visual Cloud Accelerator Card - Analytics (VCAC-A) Kubernetes deployment support (CPU, GPU and VPU)
- Node feature discovery of VCAC-A
- Telemetry support for VCAC-A
- Provide ansible and Helm -playbook support for OVC codecs Intel Xeon CPU mode - video analytics service (REST API) for developers
- Edge Applications
- Smart City Application Pipeline supporting CPU or VCAC-A mode with Helm chart
- CDN Content Delivery using NGINX with SR-IOV capability for higher performance with Helm chart
- CDN transcode sample application using Intel Xeon CPU optimized media SDK with Helm Chart
- Support for Transcoding Service using Intel Xeon CPU optimized media SDK with Helm chart
- Intel Edge Insights application support with Helm chart
- Edge Network Functions
- FlexRAN DU with Helm Chart (FlexRAN not part of the release)
- xRAN Fronthaul with Helm CHart (xRAN app not part of the release)
- Core Network Function - Application Function with Helm Chart
- Core Network Function - Network Exposure Function With Helm Chart
- Core Network Function - UPF (UPF app not part of the release)
- Core network Support functions - OAM and CNTF
- Helm Chart for Kubernetes enhancements
- NFD, CMK, SRIOV-Device plugin and Multus
- Support for local Docker registry setup
- Support for deployment specific Flavors
- Minimal
- RAN - 4G and 5G
- Core - User plane and Control Plane
- Media Analytics with VCAC-A and with CPU only mode
- CDN - Transcode
- CDN - Content Delivery
- Azure - Deployment of OpenNESS cluster on Microsoft Azure cloud
- Support for OpenNESS on CSP Cloud
- Azure - Deployment of OpenNESS cluster on Microsoft Azure cloud
- Telemetry Support
- Support for Collectd backend with Intel hardware and custom metrics
- Cpu, cpufreq, load, hugepages, intel_pmu, intel_rdt, ipmi, ovs_stats, ovs_pmd_stats
- FPGA – PACN3000 (collectd) - Temp, Power draw
- VPU Device memory, VPU device thermal, VPU Device utilization
- Open Telemetry - Support for collector and exporter for metrics ( e.g. heartbeat from app)
- Support for PCM counter for Prometheus and Grafana
- Telemetry Aware Scheduler
- Early Access support for Resource Management Daemon (RMD)
- RMD for cache allocation to the application Pods
- Ability to deploy OpenNESS Master and Node on same platform
Changes to Existing Features
- OpenNESS 20.06
- Offline install for Native mode OnPremises has be deprecated
Fixed Issues
- OpenNESS 20.06
- Optimized the Kubernetes based deployment by supporting multiple Flavors
Known Issues and Limitations
- OpenNESS 20.06
- On-Premises edge installation takes 1.5hrs because of docker image build for OVS-DPDK
- Network edge installation takes 1.5hrs because of docker image build for OVS-DPDK
- OpenNESS controller allows management NICs to be in the pool of configuration which might allow configuration by mistake there by disconnecting the node from master
- When using the SRIOV EPA feature added in 20.03 with OVNCNI, the container cannot access the CNI port. This is due to the SRIOV port being set by changing the network used by the container from default to a custom network, This overwrites the OVNCNI network setting configured prior to this to enable the container to work with OVNCNI. Another issue with the SRIOV, is that this also overwrites the network configuration with the EAA and edgedns, agents, which prevents the SRIOV enabled container from communicating with the agents.
- Cannot remove Edge Node from Controller when its offline and traffic policy is configured or app is deployed.
- Legacy OnPremises - Traffic rule creation: cannot parse filled and cleared field
- There is an issue with using CDI when uploading VM images when CMK is enabled due to missing CMK taint toleration. The CDI upload pod does not get deployed and the
virtctlplugin command times out waiting for the action to complete. A workaround for the issue is to invoke the CDI upload command, edit the taint toleration for the CDI upload to tolerate CMK, update the pod, create the PV and let the pod run to completion. - There is a known issue with cAdvisor which in certain scenarios occasionally fails to expose the metrics for Prometheus endpoint, see Git Hub: google/cadvisor#2537
Release Content
- OpenNESS 20.06
- Open Source: Edge node, Controller, Epcforedge, Common, Spec, Applications and Experience kit.
- IDO: IDO Edge node, IDO Controller, IDO Epcforedge, IDO Spec and IDO Experience kit.
Note: Application repo common to Open Source and IDO
Hardware and Software Compatibility
OpenNESS Edge Node has been tested using the following hardware specification:
Intel® Xeon® D Processor
- Super Micro 3U form factor chasis server, product SKU code: 835TQ-R920B
- Motherboard type: X11SDV-16C-TP8F
- Intel® Xeon® Processor D-2183IT
2nd Generation Intel® Xeon® Scalable Processors
| CLX-SP | Compute Node based on CLX-SP(6252N) |
| Board | S2600WFT server board |
| 2 x Intel(R) Xeon(R) Gold 6252N CPU @ 2.30GHz | |
| 2 x associated Heatsink | |
| Memory | 12x Micron 16GB DDR4 2400MHz DIMMS * [2666 for PnP] |
| Chassis | 2U Rackmount Server Enclosure |
| Storage | Intel M.2 SSDSCKJW360H6 360G |
| NIC | 1x Intel Fortville NIC X710DA4 SFP+ ( PCIe card to CPU-0) |
| QAT | Intel Quick Assist Adapter Device 37c8 |
| (Symmetrical design) LBG integrated | |
| NIC on board | Intel-Ethernet-Controller-I210 (for management) |
| Other card | 2x PCIe Riser cards |
Intel® Xeon® Scalable Processors
| SKX-SP | Compute Node based on SKX-SP(6148) |
| Board | WolfPass S2600WFQ server board(symmetrical QAT)CPU |
| 2 x Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz | |
| 2 x associated Heatsink | |
| Memory | 12x Micron 16GB DDR4 2400MHz DIMMS * [2666 for PnP] |
| Chassis | 2U Rackmount Server Enclosure |
| Storage | Intel M.2 SSDSCKJW360H6 360G |
| NIC | 1x Intel Fortville NIC X710DA4 SFP+ ( PCIe card to CPU-0) |
| QAT | Intel Quick Assist Adapter Device 37c8 |
| (Symmetrical design) LBG integrated | |
| NIC on board | Intel-Ethernet-Controller-I210 (for management) |
| Other card | 2x PCIe Riser cards |
| HDDL-R | Mouser Mustang-V100 |
| VCAC-A | VCAC-A Accelerator for Media Analytics |
Supported Operating Systems
OpenNESS was tested on CentOS Linux release 7.6.1810 (Core) : Note: OpenNESS is tested with CentOS 7.6 Pre-empt RT kernel to ensure VNFs and Applications can co-exist. There is not a requirement from OpenNESS software...
OpenNESS 20.03 Release
Merge pull request #6 from open-ness/openness_rel_2003 Openness rel 2003
OpenNESS 19.12.01 Release
Merge pull request #5 from open-ness/rel_1912 Rel 1912