VMware Telco Cloud PlatformTM – 5G Edition | 13 OCT 2020
NOTE: This Release Notes does not provide the terms applicable to your license. Consult the VMware Product Guide and VMware End User License Agreement for the license metrics and other license terms applicable to your use of VMware Telco Cloud Platform.
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- Overview of VMware Telco Cloud Platform 5G Edition
- New Features
- Components of Telco Cloud Platform 5G Edition 1.0
- Validated Patches
- Release Notes Change Log
- Support Resources
- Known Issues
VMware Telco Cloud Platform™ — 5G Edition is a cloud-native platform powered by field-proven VMware Telco Cloud Infrastructure™ coupled with automation, providing a cloud-first approach that delivers operational agility for virtual, cloud-native 5G, and Edge network functions. Using Telco Cloud Platform, Communication Service Providers (CSPs) and Mobile Virtual Network Operators (MVNOs) can modernize their clouds to gain web-scale speed and agility, and bring innovative services to the market faster than competitors while maintaining carrier-grade performance, resiliency, and quality.
Telco Cloud Platform helps CSPs expedite the innovation cycle to deliver new applications and services, reduce operational complexities, and achieve substantial Total Cost of Ownership (TCO) savings over other approaches, further accelerating CSPs’ cloud modernization journey to 5G.
VMware Telco Cloud Automation
- CaaS Management
- Automated discovery, registration, and creation of Kubernetes clusters.
- Continuous synchronization between the CaaS layer and VMware Telco Cloud Automation.
- Automated and On-demand optimization of existing clusters to match a network function’s requirements.
- Support for VMware Tanzu Kubernetes Grid 1.1.3.
VMware NSX-T Data Center
- NSX-T 3.0 introduces support for multicast using Protocol Independent Multicast - Sparse Mode (PIM-SM) and IGMPv2.
- Enhanced Data Path
- Performance optimizations: Data plane forwarding has been further improved.
- Additional Controller Support: Intel(R) Ethernet Controller E810 family
- L3 Networking
- VRF Lite: Provides multi-tenant data plane isolation through Virtual Routing Forwarding (VRF) in Tier-0 gateway. VRF has its own isolated routing table, uplinks, NAT, and gateway firewall services. Check the maximums for the number of VRFs and sizing using the VMware Configuration Maximums tool.
- L3 Ethernet VPN (EVPN): Provides the northbound connectivity option to advertise all VRFs on an NSX Tier-0 gateway through MP-BGP EVPN AFI (Route Type 5) to a Provider Edge and maintain the isolation on the data plane using VXLAN encapsulation by using one Virtual Network Identifier (VNI) per VRF.
VMware Tanzu Standard for Telco
- Updated Kubernetes Version: Kubernetes version included in this release is 1.18.6.
- Better support for Huge pages (with Kubernetes 1.18): Allowing for huge pages of multiple sizes, setting the huge page limit during container creation.
- VMware ESXi 6.7 U3b. See VMware ESXi 6.7, Patch Release ESXi670-201912001.
- VMware vRealize Orchestrator Appliance 8.1. See the VMware vRealize Orchestrator 8.1 Release Notes.
- VMware NSX-T Data Center Advanced Edition 3.0.2. See the VMware NSX-T Data Center 3.0.2 Release Notes.
- VMware Telco Cloud Automation 1.7. See the VMware Telco Cloud Automation 1.7 Release Notes.
- VMware Tanzu Kubernetes Grid 1.1.3. See the VMware Tanzu Kubernetes Grid 1.1.3 Release Notes.
Mandatory Add-On Components
Note: Additional license is required.
- VMware vCenter Server 6.7 U3j. See the VMware vCenter Server 6.7 Update 3j Release Notes.
- VMware ESXi 6.7 EP15. See VMware ESXi 6.7, Patch Release ESXi670-202006001.
|21 OCT 2020||Added VMware ESXi 6.7 EP15 to the Validated Patches section.|
For additional support resources, see the VMware Telco Cloud Platform documentation page.
- Both Kubernetes and Tanzu Icons Appear When Adding a Cloud-Native Virtual Infrastructure from TCA UI
When adding a new cloud-native virtual infrastructure from the Telco Cloud Automation (TCA) UI, the UI shows both Kubernetes and Tanzu icons. Tanzu relates to Kubernetes add-on for vSphere, which is targeted for support in an upcoming release.
Workaround: Use the Kubernetes icon when adding a new cloud-native virtual infrastructure from the TCA UI.
- Association of Harbor Registry with Kubernetes Cluster Not Recorded Properly in Telco Cloud Automation
When you deploy CNFs on a Kubernetes cluster, the Harbor registry associated with the cluster does not appear for selection in the Telco Cloud Automation UI. In this issue, the Harbor registry is associated with the Kubernetes cluster properly but is not recorded in the Telco Cloud Automation database.
Workaround: Navigate to the Partner Systems UI, modify the Harbor registry, and add the VIM association.
- NUMA Config Customization Not Applied to CNF When SR-IOV is Already Customized
If you instantiate a CNF with SR-IOV NICs and NUMA config set to false in a node pool, delete the CNF, and then instantiate another CNF with NUMA config set to true in the same node pool, the NUMA config customization is not applied to that node pool.
Workaround: Create a new node pool for the CNFs that require NUMA config.
- VM-level Huge Page Support Not Enabled Though Huge Page is Enabled in Guest OS Kernel
When NUMA config is set to false in CNF’s Cloud Service Archive (CSAR), the VM-level huge page support is not enabled even if huge page is enabled in the guest OS kernel.
- Node Pool VMs Exist in vSphere Even After Successful Deletion of Node Pool in Telco Cloud Automation
The node pool VMs exist in vSphere even though the node pool is deleted successfully in Telco Cloud Automation.
- Scale-out Operation Failed During SR-IOV Customization on New Node
If a node pool is customized with a kernel version that is different from the default version, the scale-out operation fails during SR-IOV customization on a new node.
Workaround: Create a new node pool with the required replicas.
- Deletion of Kubernetes Management Cluster Failed
When you delete the Kubernetes management cluster in Telco Cloud Automation, it fails with the following error:
Unable to connect to Bootstrapper. Error: ‘SocketTimeoutException’