In this blog guys, I am presenting you a case study that how Nokia (A previous market leader in mobile industry) is using Kubernetes to deliver 5G network.
Nokia was a first choice amongst people in the late 1990s and early 2000s. But in 2014 Nokia had sold its mobile unit division to Microsoft and was focusing on it’s main business not cellphones used for calling, but on the Network.
Today, Nokia is building telecom networks end-to-end — from antennas to switching and routing equipment — serving operators in more than 120 countries. As telecom vendors, They have to deliver their software to several telecom operators and put the software into their infrastructure, and each of the operators have a bit different infrastructure, “There are operators who are running on bare metal. There are operators who are running on virtual machines. There are operators who are running on VMware Cloud and OpenStack Cloud. We want to run the same product on all of these different infrastructures without changing the product itself.”
Looking for a way to allow its teams to build products with infrastructure-agnostic behavior, the company decided to embrace containerization, Kubernetes, and other cloud native technologies, a move that is being made across the telecom industry.
“when people are picking up their phones and making a call on Nokia networks, they are creating containers in the background with Kubernetes”
Nokia’s cloud native journey began two years ago, when its one of team was building company’s Telephony Application Server(TAS). “They wanted to have a service execution engine in the product, which was a totally separate function from all other parts.” So they think about the possibility of creating new architecture and tools that they could use.
For one thing, Nokia’s software serves millions of people, and is required to have the carrier-grade “five nines” availability: to be up 99.999% of the time. If you turn it to minutes, this means we’re allowed to have only 10 minutes of downtime in a whole year, “Downtime here means that you are not able to serve the person to full capacity, which means that we cannot fail. This includes software upgrades, everything, because when you call 911, you’re using Nokia’s software, and you expect that it will work.”
That meant that they needed to be able to set affinity and anti-affinity rules in their orchestration tools. “You cannot put all of the functions to the same physical host because physical hosts are failing. If you fail with one physical host, then you lose all of the core processing processes. Then there are no calls going through. So we have to divide them among the different physical hosts. At that time, only Kubernetes was able to provide these features. The simplicity of the label-based scheduling of Kubernetes was a sign that showed us this architecture will scale, will be stable, and will be good for our purposes.
“Kubernetes opened the window to all of these open source projects instead of implementing everything in house. Our engineers can focus more on the application level, which is actually the thing what we are selling, and not on the infrastructure level. For us, the most important thing about Kubernetes is it allows us to focus on value creation of our business.”
— GERGELY CSATARI, SENIOR OPEN SOURCE ENGINEER, NOKIA
The TAS went live in early 2018, and now Kubernetes is also enabling Nokia’s foray into 5G. The company is introducing microservices architecture and Kubernetes while adding 5G features to existing products. And all new 5G product development will be on top of Kubernetes. “When you develop something that is part of the operator’s infrastructure, you have to develop it for the future, and Kubernetes and containers are the forward-looking technologies,” says Csatari.
There have been real time savings thanks to Kubernetes. “By separating the infrastructure and the application layer, we have less dependencies in the system, which means that it’s easier to implement features in the application layer,” says Csatari. Because teams can test the exact same binary artifact independently of the target execution environment, “we find more errors in early phases of the testing, and we do not need to run the same tests on different target environments, like VMware, OpenStack or bare metal,” he adds. As a result, “we save several hundred hours in every release.”
The company has a long-term goal of moving the entire product portfolio into the Kubernetes platform. To that end, Nokia teams are working together with other companies to add the features needed to use Kubernetes with the real-time, nanosecond-sensitive applications close to the edge of the radio network.
Perhaps the biggest impact that Kubernetes is having on Nokia, Nokia believes, is that people are starting to think about how a telecom company can do DevOps. “We are building a DevOps pipeline, which reaches from the actual developer to the customers, and thinking about new ways how can we digitally deliver our software to our customers and get feedback from the customers right to the engineers,” he says. “This is something that will fundamentally change how telecom companies are delivering software, and how quickly can we develop new features. This is because of the usage of containers and, of course, the usage of Kubernetes.”