>> From our studios, in the heart of Silicon Valley, Palo Alto, California, this is a CUBE Conversation. >> Welcome to this CUBE Conversation here in Palo Alto, California. I'm John Furrier, host of theCUBE. We are here with Arpit Joshipura, GM of Networking, Edge, IoT for the Linux Foundation. Arpit, great to see you again, welcome back to theCUBE, thanks for joining us. >> Thank you, thank you. Happy to be here. >> So obviously, we love the Linux Foundation. We've been following all the events; we've chatted in the past about networking. Computer storage and networking just doesn't seem to go away with cloud and on-premise hybrid cloud, multicloud, but open-source software continues to surpass expectations, growth, geographies outside the United States and North America, just overall, just greatness in software. Everything's an abstraction layer now; you've got Kubernetes, Cloud Native- so many good things going on with software, so congratulations. >> Well thank you. No, I think we're excited too. >> So you guys got a big event coming up in China: OSS, Open Source Summit, plus KubeCon. >> Yep. >> A lot of exciting things, I want to talk about that in a second. But I want to get your take on a couple key things. Edge and IoT, deep learning and AI, and networking. I want to kind of drill down with you. Tell us what's the updates on the projects around Linux Foundation. >> Okay. >> The exciting ones. I mean, we know Cloud Native CNCF is going to take up more logos, more members, keeps growing. >> Yep. >> Cloud Native clearly has a lot of opportunity. But the classic in the set, certainly, networking and computer storage is still kicking butt. >> Yeah. So, let me start off by Edge. And the fundamental assumption here is that what happened in the cloud and core is going to move to the Edge. And it's going to be 50, 100, 200 times larger in terms of opportunity, applications, spending, et cetera. And so what LF did was we announced a very exciting project called Linux Foundation Edge, as an umbrella, earlier in January. And it was announced with over 60 founding members, right. It's the largest founding member announcement we've had in quite some time. And the reason for that is very simple- the project aims at unifying the fragmented edge in IoT markets. So today, edge is completely fragmented. If you talk to clouds, they have a view of edge. Azure, Amazon, Baidu, Tencent, you name it. If you talk to the enterprise, they have a view of what edge needs to be. If you talk to the telcos, they are bringing the telecom stack close to the edge. And then if you talk to the IoT vendors, they have a perception of edge. So each of them are solving the edge problems differently. What LF Edge is doing, is it is unifying a framework and set of frameworks, that allow you to create a common life cycle management framework for edge computing. >> Yeah. >> Now the best part of it is, it's built on five exciting technologies. So people ask, "You know, why now?" So, there are five technologies that are converging at the same time. 5G, low latency. NFV, network function virtualization, so on demand. AI, so predictive analytics for machine learning. Container and microservices app development, so you can really write apps really fast. And then, hardware development: TPU, GPU, NPU. Lots of exciting different size and shapes. All five converging; put it close to the apps, and you have a whole new market. >> This is, first of all, complicated in the sense of... cluttered, fragmented, shifting grounds, so it's an opportunity. >> It's an opportunity. >> So, I get that- fragmented, you've got the clouds, you've got the enterprises, and you've got the telcos all doing their own thing. >> Yep. >> So, multiple technologies exploding. 5G, Wi-Fi 6, a bunch of other things you laid out, >> Mhmm. >> all happening. But also, you have all those suppliers, right? >> Yes. >> And, so you have different manufacturers-- >> And different layers. >> So it's multiple dimensions to the complexity. >> Correct, correct. >> What are you guys seeing, in terms of, as a solution, what's motivating the founding members; when you say unifying, what specifically does that mean? >> What that means is, the entire ecosystem from those markets are coming together to solve common problems. And I always sort of joke around, but it's true- the common problems are really the plumbing, right? It's the common life cycle management, how do you start, stop, boot, load, log, you know, things like that. How do you abstract? Now in the Edge, you've 400, 500 interfaces that comes into an IoT or an edge device. You know, Zigbee, Bluetooth, you've got protocols like M2T; things that are legacy and new. Then you have connectivity to the clouds. Devices of various forms and shapes. So there's a lot of end by end problems, as we call it. So, the cloud players. So for LF Edge for example, Tencent and Baidu and the cloud leaders are coming together and saying, "Let's solve it once." The industrial IoT player, like Dynamic, OSIsoft, they're coming in saying, "Let's solve it once." The telcos- AT&T, NTT, they're saying "Let's solve it once. And let's solve this problem in open-source. Because we all don't need to do it, and we'll differentiate on top." And then of course, the classic system vendors that support these markets are all joining hands. >> Talk about the business pressure real quick. I know, you look at, say, Alibaba for instance, and the folks you mentioned, Tencent, in China. They're perfecting the edge. You've got videos at the edge; all kinds of edge devices; people. >> Correct. >> So there's business pressures, as well. >> The business pressure is very simple. The innovation has to speed up. The cost has to go down. And new apps are coming up, so extra revenue, right? So because of these five technologies I mentioned, you've got the top killer apps in edge are anything that is, kind of, video but not YouTube. So, anything that the video comes from 360 venues, or drones, things like that. Plus, anything that moves, but that's not a phone. So things like connected cars, vehicles. All of those are edge applications. So in LF Edge, we are defining edge as an application that requires 20 milliseconds or less latency. >> I can't wait for someone to define- software define- "edge". Or, it probably is defined. A great example- I interviewed an R&D engineer at VMware yesterday in San Francisco, it was at the RADIO event- and we were just riffing on 5G, and talking about software at the edge. And one of the advances >> Yes. >> that's coming is splicing the frequency so that you can put software in the radios at the antennas, >> Correct. Yeah. >> so you can essentially provision, in real time. >> Correct, and that's a telco use case, >> Yeah. >> so our projects at the LF Edge are EdgeX Foundry, Akraino, Edge Virtualization Engine, Open Glossary, Home Edge. There's five and growing. And all of these software projects can allow you to put edge blueprints. And blueprints are really reference solutions for smart cities, manufacturing, telcos, industrial gateways, et cetera et cetera. So, lots of-- >> It's kind of your fertile ground for entrepreneurship, too, if you think about it, >> Correct; startups are huge. >> because, just the radio software that splices the radio spectrum is going to potentially maybe enable a service provider market, and towers, right? >> Correct, correct. >> Own my own land, I can own the tower and rent it out, one radio. >> Yep. >> So, business model innovations also an opportunity, >> It's a huge-- >> not just the business pressure to have an edge, but-- >> Correct. So technology, business, and market pressures. All three are colliding. >> Yeah, perfect storm. >> So edge is very exciting for us, and we had some new announcements come out in May, and more exciting news to come out in June, as well. >> And so, going back to Linux Foundation. If I want to learn more. >> LFEdge.org. >> That's kind of the CNCF of edge, if you will, right? Kind of thing. >> Yeah. It's an umbrella with all the projects, and that's equivalent to the CNCF, right. >> Yeah. >> And of course it's a huge group. >> So it's kind of momentum. 64 founding members-- >> Huge momentum. Yeah, now we are at 70 founding members, and growing. >> And how long has it been around? >> The umbrella has been around for about five months; some of the projects have been around for a couple of years, as they incubate. >> Well let us know when the events start kicking in. We'll get theCUBE down there to cover it. >> Absolutely. >> Super exciting. Again, multiple dimensions of innovation. Alright, next topic, one of my favorites, is AI and deep learning. AI's great. If you don't have data you can't really make AI work; deep learning requires data. So this is a data conversation. What's going on in the Linux Foundation around AI and deep learning? >> Yeah. So we have a foundation called LF Deep Learning, as you know. It was launched last year, and since then we have significantly moved it forward by adding more members, and obviously the key here is adding more projects, right. So our goal in the LF Deep Learning Foundation is to bring the community of data scientists, researchers, entrepreneurs, academia, and users to collaborate. And create frameworks and platforms that don't require a PhD to use. >> So a lot of data ingestion, managing data, so not a lot of coding, >> Platforms. >> more data analyst, and/or applications? >> It's more, I would say, platforms for use, right? >> Yeah. >> So frameworks that you can actually use to get business outcomes. So projects include Acumos, which is a machine learning framework and a marketplace which allows you to, sort of, use a lot of use cases that can be commonly put. And this is across all verticals. But I'll give you a telecom example. For example, there is a use case, which is drones inspecting base stations-- >> Yeah. >> And doing analytics for maintenance. That can be fed into a marketplace, used by other operators worldwide. You don't have to repeat that. And you don't need to understand the details of machine learning algorithms. >> Yeah. >> So we are trying to do that. There are projects that have been contributed from Tencent, Baidu, Uber, et cetera. Angel, Elastic Deep Learning, Pyro. >> Yeah. >> It's a huge investment for us. >> And everybody wins when there's contribution, because data's one of those things where if there's available, it just gets smarter. >> Correct. And if you look at deep learning, and machine learning, right. I mean obviously there's the classic definition; I won't go into that. But from our perspective, we look at data and how you can share the data, and so from an LF perspective, we have something called a CDLA license. So, think of an Apache for data. How do you share data? Because it's a big issue. >> Big deal. >> And we have solved that problem. Then you can say, "Hey, there's all these machine learning algorithms," you know, TensorFlow, and others, right. How can you use it? And have plugins to this framework? Then there's the infrastructure. Where do you run these machine learning? Like if you run it on edge, you can run predictive maintenance before a machine breaks down. If you run it in the core, you can do a lot more, right? So we've done that level of integration. >> So you're treating data like code. You can bring data to the table-- >> And then-- >> Apply some licensing best practices like Apache. >> Yes, and then integrate it with the machine learning, deep learning models, and create platforms and frameworks. Whether it's for cloud services, for sharing across clouds, elastic searching-- >> And Amazon does that in terms of they vertically integrate SageMaker, for instance. >> That's exactly right. >> So it's a similar-- >> And this is the open-source version of it. >> Got it- oh, that's awesome. So, how does someone get involved here, obviously developers are going to love this, but-- >> LF Deep Learning is the place to go, under Linux Foundation, similar to LF Edge, and CNCF. >> So it's not just developers. It's also people who have data, who might want to expose it in. >> Data scientists, databases, algorithmists, machine learning, and obviously, a whole bunch of startups. >> A new kind of developer, data developer. >> Right. Exactly. And a lot of verticals, like the security vertical, telecom vertical, enterprise verticals, finance, et cetera. >> You know, I've always said- you and I talked about this before, and I always rant on theCUBE about this- I believe that there's going to be a data development environment where data is code, kind of like what DevOps did with-- >> It's the new currency, yeah. >> It's the new currency. >> Yeah. Alright, so final area I want to chat with you before we get into the OSS China thing: networking. >> Yeah. >> Near and dear to your heart. >> Near and dear to my-- >> Networking's hot now, because if you bring IoT, edge, AI, networking, you've got to move things around-- >> Move things around, (laughs) right, so-- >> And you still need networking. >> So we're in the second year of the LF Networking journey, and we are really excited at the progress that has happened. So, projects like ONAP, OpenDaylight, Tungsten Fabric, OPNFV, FDio, I mean these are now, I wouldn't say household names, but business enterprise names. And if you've seen, pretty much all the telecom providers- almost 70% of the subscribers covered, enabled by the service providers, are now participating. Vendors are completely behind it. So we are moving into a phase which is really the deployment phase. And we are starting to see, not just PoCs [Proofs of Concept], but real deployments happening, some of the major carriers now. Very excited, you know, Dublin, ONAP's Dublin release is coming up, OPNFV just released the Hunter release. Lots of exciting work in Fido, to sort of connect-- >> Yeah. >> multiple projects together. So, we're looking at it, the big news there is the launch of what's called OVP. It's a compliance and verification program that cuts down the deployment time of a VNF by half. >> You know, it's interesting, Stu and I always talk about this- Stu Miniman, CUBE cohost with me- about networking, you know, virtualization came out and it was like, "Oh networking is going to change." It's actually helped networking. >> It helped networking. >> Now you're seeing programmable networks come out, you see Cisco >> And it's helped. >> doing a lot of things, Juniper as well, and you've got containers in Kubernetes right around the corner, so again, this is not going to change the need, it's going to- It's not going to change >> It's just a-- >> the desire and need of networking, it's going to change what networking is. How do you describe that to people? Someone saying, "Yeah, but tell me what's going on in networking? Virtualization, we got through that wave, now I've got the container, Kubernetes, service mesh wave, how does networking change? >> Yeah, so it's a four step process, right? The first step, as you rightly said, virtualization, moved into VMs. Then came disaggregation, which was enabled by the technology SDN, as we all know. Then came orchestration, which was last year. And that was enabled by projects like ONAP and automation. So now, all of the networks are automated, fully running, self healing, feedback closed control, all that stuff. And networks have to be automated before 5G and IoT and all of these things hit, because you're no longer talking about phones. You're talking about things that get connected, right. So that's where we are today. And that journey continues for another two years, and beyond. But very heavy focused on deployment. And while that's happening, we're looking at the hybrid version of VMs and containers running in the network. How do you make that happen? How do you translate one from the other? So, you know, VNFs, CNFs, everything going at the same time in your network. >> You know what's exciting is with the software abstractions emerging, the hard problems are starting to emerge because as it gets more complicated, end by end problems, as you said, there's a lot of new costs and complexities, for instance, the big conversation at the Edge is, you don't want to move data around. >> No, no. >> So you want to move compute to the edge, >> You can, yeah-- >> But it's still a networking problem, you've still got edge, so edge, AI, deep learning, networking all tied together-- >> They're all tied together, right, and this is where Linux Foundation, by developing these projects, in umbrellas, but then allowing working groups to collaborate between these projects, is a very simple governance mechanism we use. So for example, we have edge working groups in Kubernetes that work with LF Edge. We have Hyperledger syncs that work for telecoms. So LFN and Hyperledger, right? Then we have automotive-grade Linux, that have connected cars working on the edge. Massive collaboration. But, that's how it is. >> Yeah, you connect the dots but you don't, kind of, force any kind of semantic, or syntax >> No. >> into what people can build. >> Each project is autonomous, >> Yeah. >> and independent, but related. >> Yeah, it's smart. You guys have a good view, I'm a big fan of what you guys are doing. Okay, let's talk about the Open Source Summit and KubeCon, happening in China, the week of the 24th of June. >> Correct. >> What's going on, there's a lot of stuff going on beyond Cloud Native and Linux, what are some of the hot areas in China that you guys are going to be talking about? I know you're going over. >> Yeah, so, we're really excited to be there, and this is, again, life beyond Linux and Cloud Native; there's a whole dimension of projects there. Everything from the edge, and the excitement of Iot, cloud edge. We have keynotes from Tencent, and VMware, and all the Chinese- China Mobile and others, that are all focusing on the explosive growth of open-source in China, right. >> Yeah, and they have a lot of use cases; they've been very aggressive on mobility, Netdata, >> Very aggressive on mobility, data, right, and they have been a big contributor to open-source. >> Yeah. >> So all of that is going to happen there. A lot of tracks on AI and deep learning, as a lot more algorithms come out of the Tencents and the Baidus and the Alibabas of the world. So we have tracks there. We have huge tracks on networking, because 5G and implementation of ONAP and network automation is all part of the umbrella. So we're looking at a cross-section of projects in Open Source Summit and KubeCon, all integrated in Shanghai. >> And a lot of use cases are developing, certainly on the edge, in China. >> Correct. >> A lot of cross pollination-- >> Cross pollination. >> A lot of fragmentation has been addressed in China, so they've kind of solved some of those problems. >> Yeah, and I think the good news is, as a global community, which is open-source, whether it's Europe, Asia, China, India, Japan, the developers are coming together very nicely, through a common governance which crosses boundaries. >> Yeah. >> And building on use cases that are relevant to their community. >> And what's great about what you guys have done with Linux Foundation is that you're not taking positions on geographies, because let the clouds do that, because clouds have-- >> Clouds have geographies, >> Clouds, yeah they have agents-- >> Edge may have geography, they have regions. >> But software's software. (laughs) >> Software's software, yeah. (laughs) >> Arpit, thanks for coming in. Great insight, loved talking about networking, the deep learning- congratulations- and obviously the IoT Edge is hot, and-- >> Thank you very much, excited to be here. >> Have a good trip to China. Thanks for coming in. >> Thank you, thank you. >> I'm John Furrier here for CUBE Conversation with the Linux Foundation; big event in China, Open Source Summit, and KubeCon in Shanghai, week of June 24th. It's a CUBE Conversation, thanks for watching.

>> Narrator: Live from Vancouver, Canada it's theCUBE covering OpenStack Summit North America 2018. Brought to you by Red Hat, the OpenStack Foundation, and its ecosystem partners. >> Welcome back to theCUBE. I'm Stu Miniman here with my cohost here John Troyer. And we're at the OpenStack Summit 2018, here in Vancouver. One of the key topics we've been discussing, actually for a few years but under new branding, and it's really matured a bit is Edge Computing. So, we're really happy to welcome to the program two first time guests. We have Arturo Suarez, who's a program director with Canonical. We also have first time Kontron employee on, Eric Sarault, who's a product manager of software and services with, I believe Montreal based, is the headquarters. >> That's correct. >> Stu: So, thank you for allowing all of us to come up to Canada and have some fun. >> It's a pleasure. >> But we were all working during Victoria Day, right? >> Yeah. >> All right. Arturo, we know Canonical. So, we're going to talk about where you fit in. But, Eric, let's start with Kontron. I've got a little bit of background with them. I worked in really kind of the TelCo space back in the 90s. But for people that don't know Kontron maybe give us some background. So, basically, the entity here today is representing the communications business unit. So, what we do on that front is mostly TelCo's service providers. We also have strong customer base in the media vertical. But right now the OpenStack, what we're focusing on, is really on the Edge, mixed messages as well. So, we're really getting about delivering the true story about Edge because everybody has their own version of Edge. Everybody has their own little precisions about it. But down the road, it's making sure that we align everyone towards the same messaging so that we deliver a unified solution so that everybody understands what it is. >> Yeah. So, my filter on this has been Edge depends who you are. If you're a telecommunications vendor, when we've talked about the Cohen, it's the Edge of where they sit. If I'm an enterprise, it's the Edge is more like the IOT devices and sometimes there's an aggregation box in between. So, there's somewhere between two and four Edges out there. It's like cloud. We spent a bunch of years discussing it and then we just put the term to the side and go things. When you're talking Edge at Kontron, what does that mean? You actually have devices. >> We do. >> So, who's your customer? What does the Edge look like? >> So, we do have customers on that front. Right now we're working with some big names out there. Basically delivering solutions for 12 inch depth racks at the bottom of radio towers or near cell sites. And ultimately working our way up closer to what would look like, what I like to call a "closet" data center, if you will. Where we also have a platform with multiple systems that's able to be hosted in the environment. So, that's really about not only having one piece of the equation but really being able to get closer to the data center. >> All right. And Arturo, help bring us in because we know Canonical's a software company. What's the Edge mean to your customers and where does Canonical fit? >> So, Canonical, we take pride of being an ubiquitous platform, right? So, it doesn't matter where the Edge, or what the Edge is, right? There is an Ubuntu platform. There is an Ubuntu operating system for every single domain of compute, going from the very end of the Edge. That device that sits on your house or that drone that is flying around. And you need to do some application businesses, or to post on application businesses with, all the way to the core rank. Our OpenStack story starts at the core. But it's interesting as it goes farther from that core, how the density, it's an important factor in how you do things, so. We are able, with Kontron, to provide an operating system and tooling to tackle several of those compute domains that are part of the cloud where real estate is really expensive, right. >> Eric, so you all are a systems developer? Is that a fair two-word phrase? It's hardware and software? >> Basically, we do our original design. >> Okay. I know where I am. >> Manufacturing. >> So, I'm two steps away from hardware. So, I think of those as all systems. But you build things? >> Eric: Correct. >> And you work with software. I think for folks that have been a little more abstract, you tend to think, "Well, in those towers, there must be some bespoke chips and some other stuff but nothing very sophisticated." At this point we're running, or that your customers are running, full OpenStack installations on your system hardware. >> Eric: Correct. >> That's in there and it's rugged and it's upgradable. Can you talk a little bit about the business impact, of that sort of thing, as you go out and work with your customers? >> Certainly. So, one of the challenges that we saw there was really that, from a hardware perspective, people didn't really think about making sure that, once the box is shipped, how do you get the software on it, right. Typically, it's a push and forget approach. And this is where we saw a big gap, that it doesn't make any sense for folks to figure that on their own. A lot of those people out there are actually application developers. They don't have the networking background. They don't have a hardware engineering background. And the last thing they want to be doing is spending weeks, if not months, figuring out how to deploy OpenStack, or Kubernetes, or other solutions out there. So, that's where we leverage Canonical's tools, including MAAS and Juju, to really deploy that easily, at scale, and automated. Along with packaging some documentation, some proper steps on how to deploy the environment quickly in a few hours instead of just sitting there scratching your head and trying to figure it out, right. Because that's the last thing they want. The minute they have the box in their hand they already want to consume the resources and get up and running, so. That's really the mission we want to tackle that you're not going to see from most hardware vendors out there. >> Yeah, it's interesting. We often talk about scale, and our term, it's a very different scale when you talk about how fast it's deployed. We're not talking about tens or hundreds of thousands of cores for one environment. It's way more distributed. >> Yeah. It's a different type of scale. It's still a scale but the building block is different, right. So, we take the orders of magnitude more of points of presence than there are data centers, right. At that scale, and the farther you go again from the core, the larger the scale it is. But the building block is different. And the ability to play, the price of the compute is different. It goes much higher, right? So, going back again, that ability to condense in OpenStack, the ability to deliver a Kubernetes within that little space, is pretty unique, right? And while we're still figuring out what technology goes on the Edge, we still need to account for, as Eric said, the economics of that Edge play a big, big part of that gain, right. So, there is a scale, it's in the thousands of points of presence, in the hundreds of thousands of points of presence, or different buildings where you can put an Edge cloud, or the use-case are still being defined, but it's scaled on a different building block. >> Well, Arturo, just to clarify for myself, sometimes when you're looking at an OpenStack component diagram, there's a lot of components and I don't know how many nodes I'm going to have to run. And they're all talking to each other. But at the Edge, even though there's powerful hardware there, there's an overhead consideration, right? >> Yes. Absolutely and that's going to be there. And OpenStack might evolve but might not evolve. But this is something we are tackling today, right. That's why I love the fact that Kontron has also a Kubernetes cluster, right. That multi-technology, the real multi-cloud is a multi-technology approach to the Edge, right. There are all the things that we can put in the Edge and the access is set. It's not defined. We need to know exactly how much room you have, how you make the most out of each of your cores or each of the gigs of RAM out there. So, OpenStack obviously is heavy for some parts of the Edge. Kontron, with our help, has pushed that to the minimum Openstack viable that allows you not to roll a track when you need to do something on that location, right. As that is as effective as it can get today. >> Eric, can you help put this in a framework of cloud, in general. When I think of Edge, a lot of it data's going to need to go back to data centers or a public cloud, multiple public cloud providers. How do your customers deal with that? Are you using Kubernetes to help them span between public cloud and the Edge? >> So, it's a mix of both. Right now we're doing some work to see how you can utilize idle processing time, along with Kubernetes scheduling and orchestration capabilities. But also OpenStack really caters to the more traditional SDNN of the use-case out there to run your traditional applications. So, that's two things that we get out of the platform. But it's also understanding how much data do you want to go back to the data center and making sure that most of the processing is as close as possible. That goes along with 5G, of course. You literally don't have the time to go back to the data centers. So, it's really about putting those capabilities, whether it's FPGAs, GPUs, and those platform, and really enabling that as close as possible to the Edge, or the end user, should I say. >> Eric, I know you're in the carrier space. Can you talk a little, maybe Kontron in general? And maybe how you, in your career as you go the next decades looking at imbed-able technology everywhere, and what do you all see as the vision of where we're headed? >> Oh, wow. That's a hell of a question. >> That's a big question to throw on you. >> I think it's very interesting to see where things are going. There's a lot of consolidation. And you have all these opensource project that needs to work together. The fact that OpenStack is embracing the reality that Kubernetes is going to be there to drive workloads. And they're not stepping on each others' throat, not even near. So, this is where the collaboration, between what we're seeing from the OpenStack Foundation along with the projects from the Linux Foundation, this is really, really interesting to see this moving forward. Other projects upcoming, like ONAP and Akraino, it's going to be very interesting for the next 24 months, to see what it's going to shape into. >> One of the near things, you mentioned 5G and we've been watching, what's available, how that roll-out's going to go into the various pieces. Is this ecosystem ready for that? Going to take advantage of it? And how soon until it is real for customers? >> The hardware is ready. That's for sure. It's really going to be about making sure if you have a split environment that's based on X86, or a split with ARM, it's going to be about making sure that these environments can interact with each other. The service chaining is probably the most complicated aspect there is to what people want to be doing there. And there's a bit of a tie, rope-pulling, from one side to another still but it's finally starting to put in to play. So, I think that the fact that Akraino, which is going to bring a version of OpenStack within the Linux Foundation, this is going to be really unlocking the capabilities that are out there to deploy the solution. And tying along with that, with hardware that has a single purpose, that's able to cater all the use-cases, and not just think about one vertical. "And then this box does this and this other box does another use-case." I think that's the pitfall that a lot of vendors fallen into. Instead of just, "Okay, for a second think outside the box. How many applications could you fit in this footprint?" And there probably going to be big data and multiple use-cases, that are nowhere near each other. So, don't try to do this very specific platform and just make sure that you're able to cater pretty much everyone. It's probably going to do the job, right, so. >> There's over 40 sessions on Edge Computing here. Why don't we just give both of you the opportunity to give us a closing remarks on the importance of Edge, what you're seeing here at the show, and final takeaways. >> From our side, from the Canonical side again, the Edge is whatever is not core. That really has different domains of compute. There is an Ubuntu for each of one of those domains. As Eric mentioned, this is important because you have a common platform, not only in the hardware perspective or the orchestrating technologies and their needs, which are evolving fast. And we have the ability, because how we are built, to accommodate or to build on all of those technologies. And be able to allow developers to choose what they want to do or how they want to do it. Try and try again, in different types of technologies and finally get to that interesting thing, right. There is that application layer that still needs to be developed to make the best use out of the existing technologies. So, it's going to be interesting to see how applications and the technologies evolve together. And we are in a great position as a common platform to all of those compute domains on all of those technologies from the economical perspective. >> On our side, what we see, it's really about making sure it's a density play. At the Edge, and the closer you go to these more wild environments, it's not data centers with 30 kilowatts per rack. You don't have the luxury of putting in, what I like to call whiteboards, 36 inch servers or open-compute systems. So, we really want to make sure that we're able to cater to that. We do have the products for it along with the technologies that Canonical are bringing in on that front. We're able to easily roll-out multiple types of application for those different use-cases. And, ultimately, it's all going to be about density, power efficiency, and making sure that your time to production with the environment is as short as possible. Because the minute they'll want access to that platform, you need to be ready to roll it out. Otherwise, you're going to be lagging behind. >> Eric and Arturo, thanks so much for coming on the program and giving us all the updates on Edge Computing here. For John Troyer, I'm Stu Miniman. Back with lots more coverage here from OpenStack Summit 2018 in Vancouver. Thanks for watching theCUBE. (exciting music)