White Papers

Open Source Infrastructure Software for vRAN Deployment and Operation

Issue link: https://resources.windriver.com/i/1225317

Contents of this Issue

Navigation

Page 5 of 8

© HEAVY READING | WIND RIVER | OPEN SOURCE INFRASTRUCTURE SOFTWARE | AUGUST 2019 6 • Ability to scale across a range of hardware form factors. For example, scale from minimum footprint single servers (e.g., at a cell site) to two-server high availability solutions (e.g., at industrial sites) or multi-rack solutions at larger sites (e.g., at a central office). • Resilient operation. Critical edge services need to continue to operate autonomously – even if network connectivity is interrupted. StarlingX Services and Upstream Integration StarlingX provides complete Day 1 and Day 2 management of upstream Kubernetes and OpenStack clusters, including services such as install, configuration, monitoring, updates, and more. In this sense, StarlingX can be thought of as part development project for edge cloud management services and part integration project with upstream Kubernetes and OpenStack, as shown in Figure 3. This outcome is an integrated, ready-to-deploy solution that enables system-wide orchestration and monitoring with shared configurations across edge cloud locations/instances. Figure 3: StarlingX Edge Services Integration with Upstream Open Source Source: StarlingX The major differences between StarlingX releases are shown in Figure 4 below. Release 1.0 supported OpenStack deployed on dedicated physical servers. Release 2.0, due in Q3 2019, supports Kubernetes and OpenStack workloads deployed on dedicated physical servers. In this release, OpenStack services will be containerized and will run, optionally, on top of a Kubernetes cluster. This will mean operators can use StarlingX to run Kubernetes-only edge sites with support for Calico container networking and pass-through interfaces for higher networking performance. It will also add support for native Docker runtime, Ceph-backed persistent volume claims, a local Docker registry, and Helm and Armada package management. In a mobile network context, these Release 2.0 advances are important to support performance-intensive high throughput mobile network applications. Increasingly, network applications are now being written as cloud network functions (CNFs) to run containers. Where classic virtual network functions (VNFs), which run in virtual machines (VMs; e.g., in

Articles in this issue

view archives of White Papers - Open Source Infrastructure Software for vRAN Deployment and Operation