Nokia’s core business is building telecom networks end-to-end; its main products are related to the infrastructure, such as antennas, switching equipment, and routing equipment. “As telecom vendors, we have to deliver our software to several telecom operators and put the software into their infrastructure, and each of the operators have a bit different infrastructure,” says Gergely Csatari, Senior Open Source Engineer. “We want to run the same product on all of these different infrastructures without changing the product itself.”
The company decided that moving to cloud native technologies would allow teams to have infrastructure-agnostic behavior in their products. Teams at Nokia began experimenting with Kubernetes in pre-1.0 versions. The first Kubernetes-based product, the Nokia Telephony Application Server, went live in early 2018.
“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. And 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,” he adds. As a result, “we save several hundred hours in every release.”
By the numbers…
“five nines” (99.999%)
Hundreds of hours every release
Enabled Nokia’s foray into 5G
Nokia was the first name in mobile phones when they were becoming ubiquitous in the late 1990s and early 2000s.
But by 2014, the company had sold off its mobile device division and was focusing its core business not on the handhelds used for calls, but on the networks.
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, we have to deliver our software to several telecom operators and put the software into their infrastructure, and each of the operators have a bit different infrastructure,” says Gergely Csatari, Senior Open Source Engineer at Nokia. “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. Since early 2018, “when people are picking up their phones and making a call on Nokia networks, they are creating containers in the background with Kubernetes,” says Csatari. “Now, all the products are doing some kind of re-architecture work, and they’re moving to Kubernetes.”
Nokia’s cloud native journey began about two years ago, when Csatari’s team was building the company’s Telephony Application Server (TAS). “We wanted to have a service execution engine in the product, which was a totally separate function from all other parts,” he says. “There, we had the possibility to think about new architectures and new tools that we could use. We created this particular product based on Kubernetes, and we liked the work, so we started to talk about cloud native and containers and all of these things. We did a very extensive research of different container orchestration tools. We knew that we have some, let’s say, strange or different requirements because of the special environment that our software is running on.”
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,” says Csatari. “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 our 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,” Csatari explains. “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.”
“When people are picking up their phones and making a call on Nokia networks, they are creating containers in the background with Kubernetes.”— GERGELY CSATARI, SENIOR OPEN SOURCE ENGINEER AT 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.”
Moving from Nokia’s legacy cluster management system, which had been built in-house more than thirty years ago, to a Kubernetes platform also meant that “we started using Linux as a base operating system, so we just opened the window to all of these open source projects instead of implementing everything in house,” says Csatari. (From CNCF’s ecosystem, the team is already using Helm, gRPC, CNI, Prometheus, and Envoy, and plans to implement CoreDNS.) “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.”
“Kubernetes opened the window to all of these open source projects instead of implementing everything in house. 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 AT NOKIA
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.
And the CNCF community is proving to be a great forum for that collaboration. “I had some discussions at KubeCon with people from the networking SIG and the resource management working group, to work together on our requirements, and that’s very exciting for me and my colleagues,” says Csatari. “Previously, everybody had the same problem, but everybody just did it in his own, and now we are trying to solve the same problem together.”
Perhaps the biggest impact that Kubernetes is having on Nokia, Csatari 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.”