>>Ly from San Diego, California. It's the cube covering to clock in cloud native con brought to you by red hat, the cloud native computing foundation and its ecosystem Marsh. >>Welcome back to San Diego. It's CubeCon cloud native con 2019. You're watching the cube. I'm streaming in my cohost for three days of live coverage is John Troyer and happened at welcome fresh off the keynote stage to my right is as hers as har who's the chief architect for telco at red hat and the man that was behind the scenes for a lot of it, hunting Garcia, telco solutions manager at red hat. A gentlemen, thanks so much for joining us and a very interesting keynote. So you know 5g uh, you know, my background's networking, we all watch it. Um, uh, let's say my telco provider already says that I have something related to five G on my phone that we grumble a little bit about, but we're not going to talk about that where we are going to talk about his keynote. Uh, we had a China mobile up on stage. Uh, maybe a, I love a little bit behind the scenes as you were saying. Uh, you know, the cloud native enabled not just uh, you know, the keynote and what it's living, but it gets a little bit of what >>well, sure. Um, look, when we took on this particular project to build a cloud native environment, uh, for five genes, we spent a lot of time planning and in fact this is a guy who actually did, you know, most of that work, um, to do a lot of planning in terms of picking different components and getting that together. Um, one of the things that cloud native environment allows us to do is bring things up quickly. The resilience part of it and the scale bar, right? Those are the two important components and attributes of cloud native. In fact, what happened last night was obviously one of the circuit breakers trapped and we actually lost power to that particular entire part that is onstage. I mean, nobody knows about this. I didn't talk about it as part of the keynote, but guess what? Through because it was cloud native because it was built in an automated fashion. People were able to work. Yes, they spent about three hours or so to actually get that back up. But we got it back up and running and we showed it live today. But what, I'm not trying to stress on how it failed a white fail. I'm trying to stress on how quickly things came back up and more important. The only cloud native way of doing things could have done that. Otherwise it wouldn't have been possible. All right. >>as, as the man behind the scenes there. Uh, it's great when we have, you know, here's actually the largest telco provider in the world. Uh, you know, showing what it, it's happened. So the title Kubernetes everywhere that telco edge gets a little bit of a hind, the scenes as to kind of the, the, the mission of building the solution and how you got it, you know, your, your, your customers, your partners, uh, engaged and excited to participate in. >> This is what's that very thirsting enterprise through realize. Actually, we took four months around, uh, 15 partners. And, uh, I would say partners >>because in that case, I'm taking, uh, uh, bell Canada and China mobile is a partners. They are part of the project. They were giving us a requirement, helping us all the way to it and together other, uh, more, uh, commercial partners. And of course, uh, as whatsover Allianz, like the team in the and the open interface, Allianz is, we're working with us is, was about 8,200 people working behind the scenes to get this work, uh, to have a lab, uh, directly, completely set up with a full, uh, Fuji containerized MoMA and network in France, uh, have the same in Montreal. Fuji and fogey called directly Montiel as well, uh, in one of our partners, uh, Calum labs and then bringing here the fudgey pop, uh, and have everything connected to the public cloud. So we have everything in there. So all the technology, all the mobile technology was there. >>We have enterprise technology that we're using to connect all the, all the labs and the, and the pop here with the public cloud to. Uh, um, technology and we have of course deployed as, as a, as our, uh, was mentioning. We deployed Kubernete is on the public cloud and we have as well Kubernete is open, rehabbed, open stack, uh, sorry. They had OpenShift container platform running on the, on all the premise in the lab in France and Davi, Marcia and they pop here. Uh, as I say, it was kind of an interesting enterprise. We have some hiccups last night, but uh, we were able to put that out the world telco, >>very specialized, very high service level agreements. I always want by phone to work and so a little bit, uh, uses different terminology than the rest of it sometimes. Right. And MP and VNF and VCO. But so maybe let's real to tell people a little bit like what are we actually talking about here? I mean, people also may not be following edge and, and teleco and what's actually sitting in their home town or, or it used to be embedded chips and none, it was a like Linux, but we're actually talking about installing Kubernetes clusters in a lot of different, really interesting typologies. That's absolutely true actually with the way how, and described it as perfect in the sense that we actually had Kubernetes clusters sitting in a data center environment in France, in Montreal and a remote pop that's sitting here on stage. So it was not just independent clusters but also stretch clusters where we actually had some worker nodes here that will attach back to the Montreal cluster. >>So the flexibility that it gave us was just awesome. We can't achieve that. Uh, you know, in general. But you brought up an interesting topic around, uh, you know, Getty or, uh, or, or the Teleco's operating environment, which is different and cloud native principles has, are a little bit different where they weren't very high availability, they weren't very high reliability with good amount of redundancy. Well, cloud native and actually those attributes to you. But the operational model is very different. You have to almost use codas throwaway hardware as throwaway and do a horizontal scale model to be able to build that. Whereas in the older environment, hardware was a premium switches and routers with a premium and you couldn't have a failure. So you needed all of those, you know, compliance of high availability and upgradability and so on. Here I'm upgrading processes in Linux, I'm upgrading applications. I can go deploy anytime, tear them down. Anytime I'm monitoring the infrastructure, using metrics, using telemetry. That wasn't the case before. So a different operating environment, but it provides actually better residency models than what telcos are actually yesterday. Yeah. >>Um, it's a complicated ecosystem to put all these pieces together. Uh, it gives, gives a little insight as to, uh, you know, red hats, leadership and uh, the, the, the partners that help you put it in. >>I will let him answer that. >>Um, is another, our first rodeo. We have been working on the vitro central office project with the, with the leaner foundation, uh, networking and Hopi NFV community for three last years. Uh, let's say, and the interesting part of this one is that even though we typically get with working with what the technology that they are using now, uh, we decided it's time to go with the technologies that we'll be using from now on. Um, but of course, uh, there is a set of partners that we need. We need to build the infrastructure from scratch. So for example, we have a Lenovo that was bringing all the, all the servers, uh, for the, for the set up in, uh, and here in San Diego, which actually the San Diego pub was built originally in Raleigh, Illinois, facilities and cheap all over the country to here for the show. Uh, and uh, then we have the fabric part. >>So the networking part, that's his cologne. Uh, this was working and bringing us the software defined fabric, uh, to connect all the different future. And then, then we start building this over layers on top. So we have, they had OpenShift container platform for the to completely deploy over metal servers. And then we start adding all the rest of the components, like the four G core fundamental Tran, like dividing for GFG radio from Altron, uh, together with Intel come Scott. That's his building. He started building the mobile part of it in Montreal, a San Diego. And then we add on top of that. Then we start adding the IMS core in the public cloud and then we connect everything through the by tuning. >>So a couple of things that I'd like to highlight in terms of coordinating partners, getting to know when they're ready, figuring out an onboarding process that gives them a sandbox to play with their configurations first before you connect them back into the main environment. Partitioning that working simultaneously with Malden, we had a Slack board that was full of messages every day. We had a nonstop, you know, every morning we had a scam call, right then it's like a scrum meeting every morning, just a daily stand up from eight 30 to nine 30. And we continue that all over the day. >>So as her, one of the things I really like to China mobile, uh, when they talked about in the keynote, first of all they said, you know, the problem is, you know, 20 by 2026, you know, it's, it's rainbows and unicorns and you know, 5g, uh, you know, will help enable so much around the planet. Seriously. Um, but you know, today she, she talked about major challenge in the rollout and infrastructure and service and capability. So, you know, help us understand a little bit the hype from reality of where we are with five G what we could expect. >>Absolutely. We are going through the hype phase right now, right? We are absolutely all the operators want FFG service to be delivered for sure. The reason why they want it to be delivered as they don't want to be left behind. Now there are some operators when we in more opportunistic and looking at 5g as a way to insert themselves into different conversations, IOT conversation, um, smart city conversation, right? Um, edge compute conversation. So they're being very strategic about how the big, the set of technologies, how they go deploy in that particular infrastructure and strategically offer capabilities and build partnerships. Nobody's going to rip out their existing three G four G network and replace that with 5g by 2026. It's not gonna happen, but what will happen by 2026 is an incremental phase of services that will be continued to offer. As an example, I'll give you, um, cable providers are looking at 5g as a way to get into homes because they can deploy in millimeter wave band a radio closer to the house and get a very high speed multi-gigabit high speed connection into the home without having to worry about what's your copper look like? >>Do I have fiber to the home? Do I have fiber to the business and so on. And so. So that's actually an interesting, >>okay, so you're saying solving the last mile issue in a very targeted use. >>Absolutely. So that's one. The other area might be running a partnership with BMW Toyota in, you know, some of these car companies to provide telemetry back from cars into their own, you know, operating environment so that they know what's going on, what's being used, how is it being used, how can we, how can we do provide diagnosis before the car actually begins to fail? Uh, big, you know, private environments like oil and gas mining, they are going to deploy public safety and security where all of these, you know, policemen on and safety personnel are required to now use body cams. Now you have video feeds coming from hundreds of people. There are deployment and incidents. Now you can take that information you need high speed broadband, you need the ability to analyze data and do analytics and provide feedback immediately so that they can actually act. So do three, this specific targeted use case, even a country like India where they're talking about using 5g for very specific use cases, not replacing your phone calling. >>I love that point. And it kind of ties back into some of the other things you were saying about the a agility and the operational model. And I relate it back to it. You know, my, again, my perception of some telco maybe 20 years old and that they had a tendency to do very monolithic projects. And you know, when you're out, when you're rolling out a infrastructure across the country, there's a certain, uh, monolithic nature to it. But you're talking about rolling out one, rolling out individual projects rolling out. That's also the advice we give to it. Try it with one thing, you know, try open shift with that one application and then also though, but it takes uh, the upskilling and the cultural model. So true with your telco petitioners who are, we're on Slack, they're with you and I, you know, I don't, I don't know if there's any relation, any other kinds of things to pull out about the mirror of, of the it transformation with telco transformation and colon Turner. That's actually a good point that you bring up, >>right? Look, the costs of building, if I have infrastructure from ground up is extremely high. If they want to completely revamp that. You're talking about replacing every single radio, you're talking about adding capacity more adding, you know, backhaul capacity and so on. So that isn't going to happen overnight. It's going to happen. It may take even more 10 years. Right. I mean in the most interesting thing, that stat stack that I saw was even LTE is going to grow. LTE subscriber count is going to grow for the next two years before it flatmates. So we're not going to LTE four G that's been around for a decade almost. Right. And it's going to still grow for the next two years, then it's going to flatten and then you'll start to see more 5g subscribers. Now back to the point that you were bringing up in terms of operational model change and in terms of how things will be I D principles applying it principles to telco. >>Um, there are still some challenges that we need to solve in Coobernetti's environment in particular, uh, to address the teleco side of the house. And in fact through this particular proof of concept, that was one of the things we were really attempting to highlight and shine a light on. Um, but in terms of operational models, what use applicable and it will now be totally applicable on the telco network, the CIC pipeline. There's delivery of applications and software that testing and integration, the, you know, um, operational models. Absolutely. Those, in fact, I actually have a number of service providers and telcos that I talked to who are actually thinking about a common platform for it end telco network. And they are now saying, okay, red hat, can you help us in terms of designing this type of a system. So I think what could speak to you a little bit about, uh, in this context is how the same infrastructure can be used for any kind of application. So you want to talk about how the community's platform can be used to deploy CNS and then to deploy applications and how you've shown that. Yeah. Well this is what, >>what we have been doing, right. So we have, uh, the coordinators platform does, is actually deploy and the services we have, all these partners are bringing their Cloudnative uh, function, uh, applications on top of that, that what we are calling the CNF the quantities and network functions. And basically what we were doing as well during the whole process is that we have, those partners are still developing, still finishing the software. So we were building and deploying at the same time and testing on the same time. So during the last four months, and even I can tell you even just to deny >>even last night, so the full CACD pipeline that we deploy in ID side, here it is in operation on the network side. >>Well yeah. So, so I, I want to give you the final word cause you know, John was talking about it cycles, you know, if you think about enterprises, how long they used to take to deploy things, uh, and what cloud data is doing for them. Uh, it sounds like we're going through a similar trends. >>Absolutely big in a big way. Um, telcos are actually deploying a private cloud environment and they're also leveraging public cloud in mind. In fact, sometimes they using public cloud as sandbox for their development to be completed until they get deployed and private. Claremont, they still need the private time enrollment for their own purposes, like security, data sovereignty and uh, you know, their own operational needs. So, but they want to make it as transparent as possible. And in fact, that was one of the things we want to also attempted to show, which is a public cloud today, a private cloud and bare metal, a private cloud on OpenStack. And it was like, and you know, it came together, it worked, but it is real. That's more important. And, uh, for enterprise and for telcos to be literally going down the same path with respect to their applications, their services and their operational models. I think this is really a dream come true. >>Well, congratulations on the demo. Uh, but even more importantly, congratulations on the progress. Great to see, uh, you know, the global impact that's going to have in the telecommunications market. Definitely look forward to hearing more than. >>Thank you very much. Thank you. The opportunity to >>actually be here. All right. For John Troyer, I'm Stu Miniman back with lots more here from CubeCon Claude, date of con 2019 in San Diego, California. Thanks for watching the queue.