Last autumn, the OpenStack Foundation’s executive director, Jonathan Bryce, said edge computing had emerged as a “surprise” use case for the open source platform. Enterprises which are using OpenStack as the basis of their private clouds are starting to consider how to distribute those cloud platforms to support services close to the user.
This opens up a new opportunity for OpenStack in telecoms, where operators are increasingly using the technology for NFVi (infrastructure), and are also increasingly interested in integrating their connectivity with edge compute capabilities to enable new services. However, OpenStack’s acceptance in telco’s virtualization projects has been hard-won, and challenges remain with deploying it at the heart of such a demanding environment.
So will it succeed in becoming a significant enabler of telecoms edge programs, and how will it work with platforms that have emerged from the mobile operator world, such as ETSI MEC (Multi-access Edge Computing)?
In October, Bryce told a meeting in Australia: “Heading into the beginning of this year, edge computing was something I had heard about and was kind of aware of, but I hadn’t really spent a lot time thinking about it or talking to users about it.” But enterprise interest was rising, and in the first quarter of 2018, the Foundation’s Edge Computing Group released a white paper, Cloud Edge Computing: Beyond the Data Center, which looks at the specific requirements of edge computing and its requirements for OpenStack.
There was also a clear focus on edge in the latest release of OpenStack, called Queens.
Queens included the work of several edge-focused projects, such as OpenStack LOCI (Lightweight Open Container Initiative) and OpenStack-Helm. Both these simplify the deployment of OpenStack services at the edge. The former provides LOCI-compatible images of OpenStack services, allowing them to be deployed by a container orchestration tool such as Kubernetes.
The latter is the result of a project led by AT&T, SK Telecom and SAP. It uses the Helm packaging system, which is a way to map a complex Kubernetes application, and define the interaction of containers. That enables a small footprint OpenStack deployment, with Kubernetes controlling it in an automated way. The project had its first full release in February and AT&T has been trialing it.
Now the Foundation needs to convince a wider group of telcos that it has the right platform to support their significant and complex edge cloud deployments. The US is leading the way, as in many areas of virtualization and cloud. Bryce said: “What AT&T and Verizon are working on with OpenStack is all of the computing and networking infrastructure that sits between a smartphone or smart car or some kind of IoT device in a house and whatever data center that data is going back to. It’s a very big opportunity and footprint these guys are working on. It has different characteristics, and these are some of the things we’re a little bit behind on the OpenStack technology front.”
Some of the groundwork has been laid, especially in relation to ETSI MEC. In another critical area of telco virtualization, management and orchestration (MANO), there is something of a stand-off between open source technologies from the Linux Foundation ecosystem, and those of ETSI. Both ETSI and OpenStack say they are keen to avoid something similar in edge compute. ETSI’s MEC group says there is no official agreement with OpenStack because they are working on complementary, not overlapping, issues. And some open source players have worked hard to cooperate with MEC.
For instance, Red Hat joined the ETSI MEC group in 2016 to help define use cases and architectures and ensure these remained complementary with open cloud platforms. There will also be an interest in trying to limit the influence of Amazon AWS, which has its own close alliance with MEC focused on its Greengrass edge-based IoT platform.
Red Hat and its fellow OpenStack supporters believe this is the natural platform to provide one of ETSI MEC’s three management layers – hosting infrastructure. The others are the applications platform (where Red Hat pushes its Jboss offering) and the actual services, and much work has gone into defining open northbound APIs to interface with the individual apps and services. In MEC, the hosting infrastructure and apps platform are distributed across servers which are integrated with the RAN, at the base station, radio network controller or cell aggregation site.
Despite the logic that, with OpenStack becoming almost a default option for NFVi, it should be the same for MEC infrastructure, there is still a high level of operator suspicion of the platform (and of open source in general).
Even OpenStack enthusiast BT has spoken out before about the high cost of implementing solutions even on well-established open source platforms with multiple vendors supporting them, such as OpenStack. Open platforms with their roots in the data center entail compromises for the telco, unless significant inhouse effort is made to optimize the solution for a carrier-grade network – which negates the cost advantages, so other business cases need to be made.
And despite the protestations of harmony between the OpenStack Foundation and ETSI MEC, not all the open source edge compute efforts are as friendly. The Linux Foundation is hosting two projects focused on the telco edge, which could sideline MEC. One of them, the ONF’s (Open Network Foundation’s) CORD (Central Office Re-architected as a Datacenter) claims it is now the “de facto choice for edge compute” among operators, but says it is not working with ETSI because, as Timon Sloane, the ONF’s VP of marketing, put it: “CORD gives you all that natively; you’re going to get the equivalent of edge computing. We believe open source is moving at a pace unlike anything seen. Open source is having a dominant impact.”
Another Linux Foundation project is Akraino, which aims to define an open source software stack to support carrier-class, high availability cloud services optimized for edge computing. Its first code will be released in the second quarter this year. “Akraino Edge Stack, coupled with ONAP and OpenStack, will help to accelerate progress towards development of next generation, network-based edge services, fueling a new ecosystem of applications for 5G and IoT,” said Mazin Gilbert, VP of advanced technology at AT&T Labs, which contributed some of the code.. The affordability of white box routers will also make edge compute deployments more flexible and practical, says the operator.
OpenStack does not have to worry about the edge compute architecture which prevails with operators, since it is a strong candidate to provide the infrastructure for any of them – though too much fragmentation could slow the whole market down. But it does have to build operator confidence in its capabilities, compared with inhouse infrastructure, or AWS.
Bryce told LightReading in an interview last week that the Foundation is now working hard to tailor OpenStack work to specific use cases, one of the areas being edge computing and NFV. This reflects work that has been done by various members of the community to take the technology well beyond its original remit, into areas like edge. The focus areas are data center/cloud, container infrastructure, edge computing and NFV, and CI/CD (continuous integration, continuous development). In the case of edge compute, this was what the telcos said they needed the most. “We didn’t choose edge computing, it chose us,” Bryce said in the interview.
All of these use cases have generic needs for automated compute, storage and networking, but there are differences of implementation. For instance, edge compute needs self-service capabilities, automation and APIs, and has to take into account large numbers of server deployments, some of which may be in difficult environments.
“One of the big issues at the edge is that you don’t have one environment, you have a lot of different environments, so that automation, that zero-touch management is very critical so this is being built directly off of AT&T and SK Telecom requirements and both of them are trialing it,” Bryce said.