>> From Seattle. Washington. It's the key you covering Goob Khan and Cloud Native Con North America. Twenty eighteen. Brought to you by Red Hat, the Cloud Native Computing Foundation and its ecosystem partner. >> Okay. Welcome back. It runs the cubes. Live coverage of three days Wall to wall here at Koop Khan and Cloud Native Khan, twenty eighteen in Seattle, where day three only actions happening. Mr Keep John for was to Minuteman where you have bread. French Compton, Tina. Director, Technical Market had read, had breaking down the container storage trends and directions. Costly containers are super important. That's happened. Communities has happened. Now. New things were happening around a lot of innovation. Thanks for coming on the Q. Appreciate it. >> Thanks for having me back. >> So what's the state of the art of containers of trends? Some of the market directions? What's going on around containers? >> Well, here at this show, of course, it's been all about service mesh. Right is Theo. Service mesh, dynamically dynamic discovery, dynamic invocation of services. But all of those things Well, a certain percentage of those things, according to Keynote, require some type of persistent so eso yet service message, service meshes and persistence. >> So storage is a big part of the networking and compute all working together. The cloud that's been a big part of it. What's what's important here in this show? What's going on this week. That's really impacting that piece of it. That container in storage you mentioned state versus stateless work area stateless is to find people from persistence in state become important and applications. How much conversation's been here this week on that piece >> we'll talk about this week, and then I'll talk about the last couple of weeks this week. There, there. Couple of significant thing is going on. They're going to sort of unleash innovation in persistence as it pertains to the coup bernetti subsystem. First, of course, is a container storage inter. See, you know, today, all the all of the volume plug ins have been entry. You want to change. You know, some vendor wants to change their their storage capabilities. They need to re compile the binaries. Very slow. Very, very non agile. Of course, with the advent of the container storage interface, it's okay. Here's the common interface. All the all the volume plugging providers right to that interface so they could. Then they Khun Iterated to their heart's content without having to change the the entry >> source. So the impact is what? Speed, agility, >> agility of innovation, allowing all those guys t innovate Kind of the second thing. That's so that's man of discussion this week. Another thing's been a discussion you've seen in the in some of the sessions and stuff is the operator framework, you know, coming a champion by the Coral West guys, of course. Now part of Red hat, the operator framework in terms of effectively automating things that human operators would do for complex subsystems. Such a CZ storage. Eso basic installation based basic upgrades, you know, monitoring those services. So when you know something falls over, what do you do with that type of stuff? So I'd say C s I container storage interface as well as operator from me. Those are some of the things have been talked about this week. I still want to go back. Talk about last week, but go ahead. >> I wonder if you could tease this out a little before. So, you know, lost five years. You know, container ization, Cooper Netease. You know, massive change the way we think about architectures. Things like networking in storage. I have often been the anchor to kind of hold us down to be ableto make changes faster. Virtual ization helped some, but you know, container ization. We're gonna have to fix some of these same things. What conversations you're having with customers, You know, give us the latest on the, you know, the state versus state falls we heard in the keynote. It was They said forty percent of deployments have, you know, st full applications out there spending on numbers. And, you know, it's definitely has been growing. And at least I can do it as opposed to, you know, two years ago, it was like, Okay, we're doing containers, but we're just going to stateless for now, and we'll try to figure out what architectures goingto work. Even a year ago at this show, I heard in the back rooms there were lots of arguments as to which one of the storage projects was going to lead and seems seems like we're getting some maturity. I hope we hope to give us some visibility is where we are, and you know what's working and what still needs to be done. >> So although the industry talks about serve earless there, not yet talking about data lists, the or storage lists. I mean, you know, if we threw out the basic principle of data gravity data is the sun around which applications services rotate And so even I mean, even stateless aps stateless app Still do I owe frequently? The io of stateless apse is, you know, be arrest Will puts and gets to an object store that actually brings me. So let's let's talk about let's unpack the stateless and then let's go to St ful. So I'm gonna come back. Tio some of the conversations. A couple of weeks ago, Red had announced the acquisition of Nuba and Israeli Company. So when you think about what new Bob Plus sef due to provide stateless aps with a common set of Davis, a common set of David data services across the hybrid and multi cloud so those stateless app saying, Okay, I'm going to do I'm going to rest well puts and gets. But, man, it's complicated. If I'm gonna have to develop to various proprietary protocols I've got, you know, the is your blob protocol. I've got a W. S s three. I'm talking Teo Google persistent disc. And then if I want to run hybrid, I'm also talking to SEF objects storage on premises. And if I'm a developer I'm thinking, man, Wouldn't it be nice if I had a common set of David data services, including common protocol to talkto all of those different cloud storage back end? So, Nuba some people kind of call it a cloud storage controller provides that kind of common data services. So things like common FBI protocol? Um, things like mirroring. So you you want to write, right Once you're uprights once and it smeared across the various cloud object storage back ends to facilitate easy migration. The second one I wanna uproot to move over here. Your data is already there. So that's, uh that's a couple of reasons. And some of the conversation from a couple weeks ago about how Nuba plus self are helping stateless aps get Teo hybrid and multi cloud >> this. I think that is a great point. You have a hybrid cloud and multi cloud coming around the corner, which is about choice, Right? But see, I CD pipe lining of having a consistent developer environment clearly is one of the main benefits we're seeing in this community here. Okay, I got some sulfur developers with crank teams move around that consistency, no matter where were the environment is just really good goodness. Their storage is interesting and data is that because you're right, the sun is the data and every is orbiting around it. That's the Holy Grail. This is what people want. They want addressable data. They wanted real time. They wanna have an access. They don't want to do all this code to configure manage data, and it's complicate. Got data warehouses? You got time. Siri's data so date is getting more complicated, but it needs to be simple. So this is kind of challenge of the industry. How are you guys seeing that with open ship? How is your container piece fit in? How do you guys make that easy for customers to say? Look, I want to have that data like I wanted intelligent, that brick of access to data. So my abs don't have to do all the heavy lifting almost like Dev ops for data. It's like day tops, like I need to have programmable data on the absolutely which, which have thoughts on that. >> So first I wanna I wanna address that in two ways. The first is about open shipped itself that what you described is in fact, the sweet spot of what open shift is providing a common set of Cooper Nettie Services. Plus. See, I see the pipeline services for developers and operation staff independent of your cloud infrastructures. So whether open shift is running on top of a heavy west, whether it's running on top of his your whether it's running on top of the G, C. P. Whether it's running on premises on bare metal, you know, common set of cou bernetti services and CD pipeline services. Okay, that so what you described there's wanted to just highlight that That is open ship hybrid multi >> valuable check. That's awesome data >> now coming down. Coming down to data. So, in fact, open shift container storage is the mirror analog to open shift for that, providing a common set of Cooper Netease volume services. Independent of what? The storage substrate. ID. So think about it. If you're If you're inside of eight of us, you've got CBS is what's you know? When in Rome, act as the Romans. You've got E. B s there when you're inside of eight of us. Well, the type of communities volumes service of the CBS provides natively differed them for instance, when you're on premises and it's surfacing via and NFS plug in, maybe different. Likewise. We're inside of a CZ. You're with your persistent disco, so open shift container storage device the same type of abstraction Lee are providing a common set of cou bernetti communities volumes services independent of what? The storage server layer is so >> cool you guys was tracked away the complexity. So the APP developer doesn't do anything about storage on those discreet platforms, >> doesn't know anything about storage and provides a common set of services instead of Well, let's see, this is running on this cloud. I don't have the have a different set of services, so common set of services. >> So one of things I love about talking right out of the shows is you actually have a lot of customers that are doing this way. Actually, we spoke to one of your customers yesterday. Talk about how you know communities is helping them create sustainable data centers over in Europe. In the Nordics, especially so communities is awesome. But what's really awesome is the things that we can do on top of it. I wonder if you've got, you know, help connect some of this toe. You know, your customers really things, you know? How does this, you know, change the game? How does it change their teams? You know, what can you share with us? >> One of things that I can't. What's what's top of mind. So what's not top of mind for me at the moment is you know what kind of knew how their reinventing the world what is top of mind with me right now? We've just been studying. Our our results is we look back and this is a little bit of a A Okay? It's a trend, but it's a different kind of friend you're talking about. In the last six quarters, we've had six hundred percent growth with open ship container storage. Um, so And now we send last six quarters were also at a point. Now we're seeing some of those same folks from the Nordics here. You're describing that are coming back now, you know, they have experimented on, So there are some There are Cem Cem cruise ship. There's a cruise ship company that is deployed this on on ships. What we're now seeing. What's very gratifying for us is they're coming back now for a second pass. Now, a year into it, it's okay. Clearly, it must be providing enough value that you come back. Okay. I want to buy this for another ship or more shifts. That's gratifying for us. The first year was, let's see. Let's try this uber Netease, this open ship container store stuff out. But, you know, coming back to the trough for another take, It's good for us. >> And what's going around the corner? He opens shifting, doing great. I love this abstraction layer we're seeing for the first time in the industry, clear visibility and a real value proposition. When I were joking yesterday, you know, we were at open stack years ago, or even Cube con three years ago. We would ask the question If you had a magic wand, what would you hope to have happened? It's actually some of the things that are actually happening. I mean, clean, heavy lifting is gone, and all the developer side consistency, productivity, better advantage on the application development side and then taking away all the hassles of having that she trained people on multiple clouds. So this is kind of happening. What's next? So what's the next next, uh, bowling pin to fall down? What's the, you know, Hit the front ten. What's next? What's going on? How do you guys see the next innovation around Open ship and storage containers, >> cloud independent data services and mobility. So independent of the clouds. And again, it's hybrid, too. So you don't want to be locked into your own cloud either. So cloud independent data services and mobility. So he said, Listen, I want to be I want to have a common de doop compression mirroring, but I want to sit in the layer above my clouds back to the data gravity thing. I want to ensure that my data is where I need it on different clouds. So I'm elevating to a new layer this this cloud storage controller, this this cloud independent set of data services way. Think that's where the pucks going? >> Yeah, I think the data date is critical, I think. Way said years ago. Data ops. There's a Dev ops model for data. You look at that way's not just putting into a data lake actually making it useful. Yeah, Thanks. Come on. Cuba. Here. Bringing all the data here. The Cube. We're sharing it here. Live in Seattle. Is our third year coop coming there from the beginning? That's the cubes coverage of Cloud Native Khan and Coop gone. Bring all the action here. Was red hot on the Cube. Back with more live coverage. Stay with us. Day three, three days ago off the wall. Coverage will be back after this short break.

>> Live from Seattle, Washington, it's theCUBE, covering KubeCon, and CloudNativeCon North America 2018. Brought to you by Red Hat, the CloudNative Computing Foundation, and the Antigo System Partners. >> Hey, welcome back everyone live here in Seattle for the theCUBE's coverage of KubeCon and CloundNativeCon 2018. I'm John Furrier, theCUBE with Stu Miniman, breaking down all the action. Three days of coverage, we're in day two. A lot of action at Open-source. 8,000 attendees, up from 4,000 North America, they were in China, they were all over Europe. The community's growing in a massive way. We had two great guests from Red Hat, all making it happen, part of the community. We've got Diane Mueller, whose theCUBE alumni director of community development, many times on theCUBE, good to see you, and Rob Szumski, principal product manager, both at Red Hat. Guys, thanks for coming on. Great to see you again. >> Yeah, glad to be here. - Great to be here. >> So the world's changing a lot, and there was some news recently around Red Hat. I can't remember what it was. Recently, something big news, but you guys have been big players in Open-source for years. We always cover it, we always wax on about the origination of it and how the evolution, but the CloudNative piece has gotten so real, and your role in it particularly, we've had many conversations, going maybe back to the OpenStack days of how OpenShift was developing, then the bet on Kubernetes that you made, Core OS acquisition, those two things I think, to me, at least from my perspective, really catalyzed a lot of things at the right time, right? So, from there, just a lot of things has just been happening really in a good way. Big tail wind for you guys, CloudNative app developers are using Open-source, CI/CD pipeline, and then also policy based up under the hood, completely big shift in moving the game down the field. So big congratulations first of all. But what's new? What's the update? >> The update is Operators. I think the next big thing that we are really focusing on, and that's a game changer for all the second day operations type things, and we'll make Rob talk about it in detail, is the rise of Kubernetes' Operators. It's not a scary thing, it's not like terminator day, or anything like that, but it is really the thing that helps us make the service catalogs, the Kubernetes marketplaces really accessible to all of the data bases as a service, and all of the other things, and takes out some of the complexity of delivering applications and database  as a Service to anybody running Kubernetes anywhere. >> Take a minute to explain Operator, real quick, and then we can jump into it, because I think this is a fundamental trend, that we're seeing. Developer trend is pretty obvious, it's been that word for awhile, CloudScale, ML, machine learning, and all the goodness around application development, but the Operator side of it has been an IT thing. But now you guys have a different, a new approach that's winning. What is it? What is Operator? >> Well, it's Kubernetes that has the approach, and I'll let you-- >> Yeah, so it's basically like the rise of containers was great, because you could take a single container and package an application and give to somebody, and know that they can run it successfully. And Operator does that for a distributed system in the exact same way. So you're using all the Kubernetes primitives, so you're not reinventing service discovery, and seeker management, and all that. And you can give somebody an entire Kafka stack, or a machine learning stack, or whatever it is, these very complex distributed systems, and have them run it without having to be an expert. They need to know Kafka at a high level, but not exactly all the underpinnings of it, because that's all baked in the software. >> And the benefit and the impact of the organization is what? >> And just to clarify, so this was added in, I believe Kubernetes is like 1.7, it's something that's in there, it's not something Red Hat specific- >> Yeah, it's like-- >> So you're extending Kubernetes so that you have a custom resource definition, which is an extensible mechanism for saying, hey, I've got a deployment or a staple set, but what if I want to have a new object called a MongoDB? That knows how to deploy, and manage, and upgrade MongoDB. So that's the extension mechanism that we're using. >> Yeah, so you got to think, there's certain applications that this is going to make, just a lot easier how I manage them, deploy them, things like that. Any specific examples you want to share as to-- >> All the clustered data bases. >> There's a lot of the application side in this model have been very excited about this. >> So its all the vendors and partners that want a hybrid Cloud story, just targeting Kubernetes, and we're using Kubernetes under the hood, and then everybody wants to run like a staple data base tier, whether that's Mongo and Couchbase, and Cassandra, whatever. And these are all distributed systems. >> Alright, so I want you to just perch, you said a hybrid Cloud. Explain that model, because there's just something in general discussion that is hybrid or multi means I'm running multiple places, I'm not necessarily stretching an application, but I have instances there, just want to make sure we're on the same page. >> So this would be more the compatibility that you're programming against when you're building an operator, is Kubernetes. It's not a Cloud offering, it's not OpenShift, so you're just targeting Kubernetes, and so you can run MongoDB on prem, in the Cloud, and have it function the exact same, by standing up one of these Operators. And then if that Operator has higher level constructs for how to do multi-cluster aware data rebalancing, you can take advantage of that too. >> And the Open-source status of this product is what? >> It's all Open-source, it's all in the github repos, there's a Google group for Operator framework, that anyone can come and participate in. We hold SIG meetings on the third Friday of every month, 9 a.m. Pacific Time, and it's a completely Open-source project. There's a whole framework around it, so there's the Operator SDK, the Operator Lifecycle Management, and Operator metering, all the tooling there to help people build and manage these Operators, and it's all being built out there in the open with the community's support and feedback loops. >> What's the feedback? What's the top feedback you guys are getting right now? Seeing right now? >> I have to say, this is really, like I've been hanging out with you guys like for the past three, four months on this topic, trying to get my head around it and everything, and we came here and we had two sessions, an intro session and a deep dive session, intro yesterday, deep dive today. Today's deep dive, the room was about 250 people, and they're were people outside of it-- >> Security guards blocking people from coming in. >> Nobody could come in and it's like, it's insane. It's like, everybody needs these things, and everybody wants to figure out that, and when you ask people in the room whose building one, half the room raises their hands. It's just crazy. This thing crept up on us really, maybe not on Core OS, okay, it crept up on me very quickly, and it's very rapid adoption. We have a Kubernetes Operators workshop on Friday, so not only do we have pre-conference days of like OpenShift Cons that are huge now, but now we're starting to book end, CNCF events and put on other things, just because, and that, we had 100 seats that we were hoping we would fill, and it sold out in like minutes once it got in there, and there's a waiting list of like 300 people. It is like one of, aside from Knative, and all the other wonderful hot things too, it is one of the most interesting developments I think right now. >> Thirst for the content. Would it impact? >> Yeah, and you can get all of the documentation is out there now, and people are already building them. We have a list of 50 community Operators. It's just, it's phenomenal how quickly it's growing. >> You know, Diane and Rob, it's funny because you know, we do so many of these theCUBE interviews, and this is our 10th year doing theCUBE coming up, and I remember the conversations going back in the OpenStack days, we would ask questions like, if you had a magic wand, what would you like, hope to have happened, right? And you know, those are parts of the evolution, where it's like, it's aspirational, things are being built. It seems now with Kubernetes, it's almost like, wait a minute, it's actually, this is like the goodness is so compelling, above and below Kubernetes that it's almost like uncomprehendible. You think about, oh this is actually happening. Finally the kinds of steady state kind of operational things that have been a pain in the butt for years-- >> Yeah, the toil, it's gone, for the most part. >> Yeah. >> So Rob, I've been having a lot of just thinking back to, you're employee number two at Core OS, when I first talked to Core OS, it was, we're going to build all of these individual tools, and we're going to Open-source them, and it's going to be good. We watched this just rising ecosystem and the CNCF, and it feels like what's nice and what's different that I see, compared to some previous things, is it's not one product or even a small group of companies. It's, I have this tool kit, and some of them work together, but many of them are independently used. We've talked to your peers earlier about it, etCD. etCD is totally stand alone, doesn't need to be Kubernetes. What have you seen, if you go back to that original vision, would Core OS just been, part of this whole ecosystem, and done it, if this was available, and has this delivering on a promise that your team had hoped to work on? >> Yeah, so we've always filled in where we see gaps, and so something like etCD, the concept is not new, and it comes from Google, and they have a system internally, and as Brandon got up on stage and said, we needed that coordinate, reboot, to grow out, to cluster of machines. It didn't exist so we had to build it. Same thing with how we wanted to manage Linux. There was no distro that even resembled what we were doing. Wanted to do automatic upgrades, people thought that was crazy, so we had to go build it. And so, but we always adopted the best of breed technology, when it existed. In our early bet Kubernetes, we just saw, this is the thing, and went for it. I don't even remember what version, but it was months and months before it was zero point oh, or one point oh, so it was, we've been doing it forever. And you just see the right thing, and it's the little nugget that you need, and if you don't see it, then you build it. >> What are you surprised about Rob, in terms of the ecosystem now, you mentioned some goodness is happening, still a lot more to do, visibility around value creation, you're starting to see spots where value can be created in the ecosystem, which is great. Still more work areas, but what's surprising you? What do you see as opportunities, challenges? Your thoughts, because this vision of ease of use and programmability, is happening, right? So there's still more work to do. What's your vision there? What's your thoughts? >> I mean, I think self service is key, so this is like the rise of the Cloud comes from self service for developers, and Kubernetes gives you the right abstraction, where self service for VM's, like OpenStack, which is not quite at the level of what you want. You don't want a VM, you actually wanted a place to deploy an application, you wanted load balancing, you wanted service discovery, you didn't want like a bare Ubuntu VM, and so Kubernetes raises you up to where you're productive, and then it's about building stuff on top. But what's interesting, in the space is, we're still kind of competing on Kubernetes installers, and stuff like that, so we're not even really into like the phase where people are being super productive on the platform, other than these leading companies. So I think we'll democratize that, and we'll have a whole new landscape. >> And so 2019 you see as what being a key theme for Kubernetes? >> I think it'll be Core stuff built on top, like all the serverless frameworks, a bunch of container natives storage solutions, solving some of these problems that folks are reaching out to external machine learning, but bringing that onto the cluster, GPU support, that type of stuff. It's all about the workloads. >> And tradition end users, you have a huge install base, with Red Hat, well documented, as the end users start coming in and looking at CloudNative, and doing a reimagine of their environment, whether it's IT span, IT investments, to have a run their coding and the deployments. It's going to change. 2019's going to have an impact on what I call mainstream enterprise, for lack of a better description. What's the impact of those guys, 'cause now, they now have head room, they can do more, what's the main stream enterprise look like right now with the impact of Kubernetes? >> I think they're going to start deploying applications and get like lower the time to business value, much, much lower. And I was just talking to a customer, and they ordered bare metal machines like a year ago, and they're still not racked and in the data center. And so people are still getting over that type of stuff, but once you have like a shared Kubernetes layer, you can onboard teams like crazy. I mean, name spaces are free, quote, unquote, and you can get 35 engineering teams on a Kubernetes cluster super easy. >> So they can ramp up in development teams basically, as they bring value in-house, versus outsourcing everything. They start getting development teams, this is where the action is. >> I think you're also going to see the rise of those end users contributing back things, to the Kubernetes community and as Lyft, and Uber, and everybody are great examples of that. Uber with Jaeger, and Lyft is, we were just in the Operators thing, and they raised their hand that they are about to Open-source it, a few Operators that they're building and stuff, and you're just going to see people that you didn't normally see. Often these large foundation driven things are vendor driven, but I think what you see here, is the end user community is now embracing the Open-source, is getting the legal teams there, allowing them to share their things, because one, they get more people to maintain them, and more people working on them, but it's really I think the rise of the end user we'll see, as they start participating more and more in here. And that's the promise of Open-source. >> And that's where CNCF really made it's bones. It wasn't really vendor led per se, it was really end users, the guys building out their stuff for the first time. You see Lyft for instance, great example, you guys did a Core OS, this is like the new generational model. Final question before we break. I want to get this out there. Get a plug in for Red Hat. What are you guys, what's the focus for the show? What's the news? What's the big story for Red Hat here at KubeCon this year? >> I think it's Operators, that's what we're here talking about. It's a really big push to once again get smarter workloads onto the cluster. We've got a really great hybrid story, we've got a really great over the air upgrade story that we're bringing from some of the Core OS technology, and then the next thing is, once it's easy to run 35 clusters, we need a bunch of workloads to put on there. And so we want to save folks from the toil of running all those workloads as well, just like we did at the cluster level. >> Awesome. >> Well put. I couldn't add more. One of the things that Core OS did, you hit the nail on the head earlier, is when there was something missing, they helped us build it, and with the Operator SDK, and the Lifecycle Management, and the metering, and whatever else the tooling is, they have really been inspirational inside of Red Hat. And so they filled a number of gaps, and it's just been all Operators all the time right now. >> It's great when a plan comes together. You guys got a great tail wind. Congratulations on all the success, and it's just the beginning of the wave. It's theCUBE, covering the wave of innovation here at KubeCon CloudNativeCon 2018, we'll be back with more live coverage. Day two of Three days of Kube Coverage. We'll be right back. (upbeat music)

>> Live from Seattle, Washington, it's the Cube, covering KubeCon andCloudNativeCon North America 2018. Brought to you buy Red Hat, the CloudNative computing foundation and it's ecosystem partners. (background crowd chatter) >> Okay welcome back everyone, live here in Seattle forKubeCon and CloudNativeCon. This is the Cube's coverage, I'm John Furrier with Stu Miniman. We've got two great guests, Chris Wright CTO of Red Hat, Scott Sneddon who's the senior director ofcloud at Juniper Networks, breaking down, windingdown day one of three days of coverage here. Rise of kubernetes, rise of cloudnatives, certainly impacting IT,open source communities, and developers. Guys, thanks for coming on the Cube. Appreciate it. It's good to see you. >> Yeah, good to see you. >> Welcome to the Cube. Okay, so, talk aboutthe relationship between Red Hat and Juniper. Why we're here, what are we talking about? >> Well, we're here to talkabout a combined solution. So, Red Hat's bringingkind of the software platform infrastructure piece and Juniper's bringinga networking component that ties it together.>> Yeah. >> So, we do have a fairly, well, in tech terms arelatively long history of working together. We've had a partnership for a little more than two years on sometelco Cloud initiatives around OpenStack, using the right OpenStackplatform with Contrail Juniper's contrail solutionas an SDN layer for these telco Cloud deployments. And have had a lot of successwith that partnership. A lot of large and smallto medium telco's around the world have deployed that. Earlier this year at theOpenStack summit in Vancouver, we announced an expandedpartnership to start to address some enterprise use cases. And, you know, naturallyopen shift is the lead technology that we wanted to tie in with around enterpriseadoption of cloud and some alternatives to someof the legacy platforms that are out there. >> And we were talkingearlier in the Cube here, we always get kind ofthe feel of the show, kubernetes maturing? But it kind of two worlds colliding and working together. A systems kind of view,almost like operating systems. The network systems, allkind of systems thinking. And then just apps. Okay, the old app thing. So these old legacy worldthat we all lived in kind of happening in really dynamic ways with the apps aren't thinkingabout what's below it. This is really kind of whereyou guys have a tailwind with Juniper.>> Yeah. Because you still gotto make things dynamic, you still got latency, onpremises not going away. You got IOT, so networkingplays a really big thing as software starts figuringthings out as kubernetes. Let's talk about that. Where is that value? How's it expanding? Cause clearly you stillneed to move packets from A to B.>> Yeah. Be more efficient with it. Apps going to have policy. >> The, well, I mean you've still got to, the network is always been the foundation of technology or at least for the last 20 plus years. And as cloud has been adopted, really we've seen network scale drive in different ways. The mega scalers thathave built infrastructure that we've been enabling for quite a while and have been working withthose customers as well. We've been developing a lot of simplified architecture just forthe physical plumbing to connect these things together. But what we've seen andis more and more important is, you know, it's all about the app, the app is the thing that'sgoing to consume these things. And the app developerdoesn't necessarily want to worry about IP addresses and port numbers and firewall rules and things like that, so how could we justmore simply extract that? And so, you know, we'vebeen developing automation and aimed at the networkfor quite a while, but I think more andmore it's becoming more important that theapplication can just consume that without having to directthe automation at the app. And so, you know, groupslike CloudNative foundation and a lot of the workwith kubernetes are on network policy, let's us use CloudNativeprivatives and then we can translate into the network primitives that we need to deploy to move packets, you know, IP addresses and subnets. >> And Chris, talk aboutthe multi cloud dynamic here because again, the dayof things are moving around the standardizationaround those core value propositions, youmentioned about networking and software networks, all kinds of software, you know, venations under the covers. I'm a customer, I havemultiple clouds now. This is going to be a core requirement. So you got to have a a clean integration between it. >> There's really two things. If you look at a modern application, you got your traditionalmonolithic application and as you tease itapart and into components and services, there's only one thingthat reconnects them and that's the network and so insuring that that's as easy to use as an applicationdevelopers focus is around the app and not aroundnetwork engineering is fundamental to a single cluster. And then if you have multiple clusters and you're trying to take advantage of different specialtiesin different clouds or geo replication or things like this that also require thenetwork to reconstitute those applications across thedifferent multiple clouds. If you expect your applicationengineers to become experts in networking, you're just sort ofsetting everybody up with misset expectations. >> It slows things down,requires all these other tasks you got to do. I mean it's like a rock fetch. You don't want to do it. Okay, stack a bunch of rocks, move them from there to there. I mean, this is whatthe holy grail of this infrastructure's code really is. >> Yeah.>> Yeah. I mean, that's the goal. >> Help connect the dots for us. When you look at multicloud networking obviously is a very critical component, what're your customers looking for? How does this solution goto market for your company? >> Absolute ease ofuse is top of the list. So, it can't be overly complicated. Because we're alreadybuilding complex systems, these are big distributive systems and you're adding multipleclusters and trying to connect them together. So ease of use is important. And then something that'sdynamic and reflects the current application requirements, I think is also really important. So that you don't over utilize resources in a cloud to maintainsort of a static connection that isn't actually needed at that moment. I'm sure you probably havea different perspective. >> Yeah, I mean, this isthe whole concept of SDN and network virtualization, a lot of the buzzwordsthat have been around for a few years now, is the ability to deliveron demand network services that are turned on whenthe application asks for it and are turned off when the application's done with it. We can create dynamic connectionsas applications scale. And then with a lot of thenewer things we've been doing around contrailand with Red Hat are the ability to extend thoseapplications environments with networking andsecurity into various cloud platforms. So, you know, if it's runningon top of an openstack environment or in a public cloud or, some other bare metal infrastructure, we're going to make surethat the network and security primitives are inplace when the application needs it and then get deepervisioned or pulled out when they go away. >> Being at a show like this, I don't think we need to talktoo much about open source, because that's reallycore and fundamental, but what we're doing here, but I guess, how doesthat play into customers? We've been watching the slow change in the networking world, you know, I'm a networking guy by background, used to measure changesin networks in decades and now it feels like we'removing a tiny bit faster, >> Little bit. >> What're we seeing is--? >> Well, I mean the historyof openness in networking was the ITF>> Standards. >> and IEEE and standards bodies, right? How do we interact? We're going to have ourlittle private playground and then we'll makesure to protocol layer, we can interact with each otherand we call that openness. But the new openness is open source and transparency into the platform and the ability tocontribute and participate. And so Juniper shifted a lot of our focus, I mean we still haveour own silicone and the operating system we built on our routers and switches, but we'vealso taken the contrail platform, open sourced it a few years ago, it's now called thetungsten fabric project under the Linux foundation. And we're activeparticipants in a community. And our customers really demand that. The telco's are drivingtowards an open source model, more and more enterpriseswant to be able to consume open source software with support, which is where we come in, but also be able to have an understanding of what's going on under the covers to participate if that's a possibility. But really drivinginteroperability through a different way then justa protocol interaction and a standards body. >> I can see how kubernetescan be a great fit for you guys at Juniper, clearly out of the boxyou have this kind of inter cloud, inter networking, paradigm that you're used to, right? How does the relationshipof Red Hat take it to the next level? What specifically areyou guys partnering on, where's that, what'sthat impact on customers? Can you just give a quick explanation, take a minute to explainthe Juniper Red Hat-- >> Well a lot of itcomes down to usability and ease of use, right? I mean what Red Hat's done with open shift is developed a platformleveraging kubernetes heavily, to make kubernetes easierto use with the great support model and a lot of tooling built on top of that to make thatmore easily deployable, more easily developersto develop on top of. What we're doing withcontrail is providing a supported version ofour open source project and then by tying thesethings together with some installation tools and packaging and most importantly a support model, that let's a customer have the proverbial single throat to choke. >> Have you ever hadcustomers that can run beautifully on your platform? >> Yeah yeah, and theinstallation process is seamless, it's a nob that installtime to consume contrail or some other networking stack and they can call Red Hat for support and they'll escalate toJuniper when appropriate and vice versa. And we've got all those things in place. >> I think one of the things that we have like shared vision on is, the ease of use andthen if you think about two separate systems with a plug in, there's going to be someintegration that needs to happen and we're lookingat how much automation can we do to keep thoseintegrations always functional so that ifwe need to do upgrades, we can do those together instead of abandoning one side or the other. And I think another areawhere we have shared vision is the multi cloud space where we really see the importance for our customer base toget applications deployed to the right locations. And that could be takingadvantage of different pricing structures in different clouds or it could be hardwarefeatures of functionality. Especially as we getinto edge computing and really creating a differentview of computing fabric, which isn't quite so, you know, client serveror cloud centralized, but much more distributed. >> I like how you said that Chris, earlier about how when you decomposethat monolithic app it connects with the network. That's also the other way around. Little pieces can cometogether and work with the network and then form in real time, whether it's an IOT datacoming into the data center, or pushing computdata to the edge, you got to have that network interaction. This is a real CloudNative evolution, this is the core. >> Yeah, and I think anotherpiece that we haven't touched on as much, Scott mentioned it, was the security component. >> Yeah, explain that. >> Again, with as youdecompose that application into components, you surface those components with APIs, those were internal APIswhen they're now exposed externally security really matters. And having simple policythat describes not just the connectivity topologybut who can speak to whom is pretty fundamentally important. So that you maintainsecurity posture and a risk profile that's acceptable. >> And then I think it'sreally important is, your traditionalenterprise starts to adopt these CloudNative models. You've got a securityteam there that might not necessarily be up to speed or on board. So you've got to havetooling and visualization and analytics to beable to present to them that policies are being enforced correctly and are compliant and all those things so. >> Yeah and they're tough customers too. They're not going to, they expectreally rock solid capability. >> They don't let youjust deploy a big flat network with no policy-- >> Hey what about the APIs? Service areas exposed in the IOT space. >> Yeah.>> Right. >> You got to nail it down. >> Yeah absolutely, sothat's a lot of what we're bringing to the table here, is a lot of Juniper'shistory around developing security products. >> Take a minute to explain,I want to give you some time to get a plug in for Juniper. I've been following youguys for a long time. Junos back on the old days, contrail. Juniper's has had a software, big time software view. >> Yeah. >> Explain the DNA of software at Juniper. >> You know the earlydays of Juniper were, we weren't the first networkvendor on the market. There was already somebodyon the market in the mid 90s that had a pretty solid stronghold on carrier and enterprise networking. We had to come in with a better model. Let's make the box easierto use and simpler. Let's make the interfacea little more structured and understandable. Let's make it programmable, right? I mean the first feature request for Junos was to have a CLI becausethe first interaction to it was just an API call. And that was out of the box from day one. We had to write a user interface to it just to fit in to theexisting network world in the mid 90s. And so we've alwaysbeen really proud of the Junos operating systemthat runs on our boxes. We've really been proudthat we've had this one Junos concept of a commonoperating system on every network device that we deliver. As we've started tovirtualize those network devices for NFE and things like that, it's again that same operatingsystem that we deliver. Contrail came to us through acquisition, so it's not Junos in and of itself, but still leveraging a lot of those same fundamentals around,model driven configuration management, understandableAPIs, and openness that we've always had. >> Cloud operating modelthat everyone's going to, the common operating modelfits in that unification vision that you guys have had. >> Yeah absolutely. >> And really early, by the way, was before SDN was SDN, I think that was SDN's kind of like-- >> I like to dry, I-- >> Should have called it SDN. >> Right, I described SDN as just a big distributed router andreally we've had big distributed routers for a long time. >> John, we are in Seattle, everything we're talkingabout in tech is hipster. >> Chris, great stuff. Great to have you on, Scott. Great smart commentary. CTO Red Hat, you guys are winning. Congratulations on the betsyou made at kubernetes early, >> Yeah. >> CoreOS great acquisition,great team there, and some news there aboutsome dealings out back into the C and CF, soI mean, you've got it-- >> A lot going on. >> A lot going on. And yeah, big news with that other things, I can't remember what it was, it was some big-->> Something in there. >> Something for a million dollars. >> Great news out there. Thanks for coming out, appreciate it. Good to see you.>> Good to see you. >> Alright, breakingdown day one coverage. I'm John Furrier, Stu Miniman. Day two starts tomorrow. Three days of wall towall coverage of KubeCon. And they're shutting down the hall. Be right back and see you tomorrow. Thanks for watching. (techy music)

>> Announcer: Live from Seattle Washington, it's the Cube covering KubeCon and CloudNativeCon, North America, 2018. Brought to you by Redhat, the CloudNative Computing Foundation, and it's ecosystem's partners. (techno music) >> Okay welcome back everyone. We are live in Seattle for KubeCon and CloudNativeCon 2018, Cube's live coverage three days. Day one of a full house event here, through 8,000 people, doubled from last year, I'm John Furrier for Stu Miniman. Our next two guests are from Red Hat. Great to have these guys as our guests, as also thank Red Hat for being great sponsors. Brian "Redbeard" Harrington, Cube Alumni Back Product Manager of Service Mesh at Red Hat, and William Oliveria, Product Manager Serverless at Red Hat, we'll hear a lot about that. You guys, first of all, thanks for coming on, and thanks to your company Red Hat, for being a great supporter of the Cube and the community, the contribution you guys have helped up make, we really appreciate that. Thank you. >> Absolutely delighted to be here. >> Happy to be here. >> John Furrier: Alright, so let's get into it. So service meshes are hot because now Kubernetes is kind of like, we're seeing that is totally stabilized, and now you start to see the engineering, and the value creation happening in layers. Shim layers they call here, I got state-full applications. So you're starting to see service meshes conceptually adopt. Give us a quick update on where that is, how real is it, what's the progress, and what's some of the state-of-the-art activities around it? >> [Brian "Redbeard" Harrington] Well the beautiful thing is, using a service mesh is not anything new at all. I mean, that was really built to top the Netflix OSS ideas. They've been around for seven, eight years now. It's really just kind of decomposing what were a bunch of individual libraries that you had to implement into more infrastructure services, so that you know that you just, regardless of the language, environment, etc., you've always got a certain base platform ready to go. >> John Furrier: Is Service Mesh going to be a standard thing? Is it going to be, service meshes of your flavor, is there going to be certain instances custom services? How do you see that coming out with CSDO, Knative? There's things evolving. >> [Brian "Redbeard" Harrington] Mmhm, yeah. >> What's the state there, is that going to be the new normal, or is it going to see settling? What's your view on that? >> [Brian "Redbeard" Harrington] I think to some extent, it depends on the scale that you're at. If you are at the scale of Yelp or Stripe, one of those, and using Envoy, you already have a good idea of what that mesh is going to look like, so you're building that control plain, in the way that you need it. Where Istio and Linker D and some of the other ones come in, is when you are a smaller scale and you need to figure out what you're control plane is going to look like, that's where it really shines, because it gives you something that you can just start using and has some training wheels on it to make sure that you've got a stable platform to use from day one. >> Stu Miniman: So one of the other news items today I wanted to get your opinion on is, EtsyD has been handed over to Linux Foundation and CNCF, so EtsyD came out of CoreOS of course, which was acquired by Red Hat. Give us a little bit of the update as to why that happened and why it's a good thing for the community. >> So I think for any stable platform, it's really been the theme of what I've been talking about, you've got to know that it's safe to use the software, that there's going to be a longer term vision, and a lot of community guidance around that, and that's why Red Hat made the contribution. When we were at CoreOS, we really wanted to, and it was something that was ultimately a goal, but it kind of became a little bit of a race condition. Do we go ahead and contribute it, and then hope that other folks will join us in building it? Just by open sourcing it, we saw some contributions from IBM around PowerPC architecture and Maso's, and other groups coming in, but putting it just full-bore in the CNCF really guarantees that there will be ongoing community collaboration. >> John Furrier: Just to give a shout out to you guys at CoreOS, you guys did an amazing job, and I think this is a benefit of the Red Hat relationship, because that's the start up dilemma you have, do we get it in there, how do we support it, how do we make it better, is it competitive, was our focus what we optimized it for? But now with the Red Hat piece you guys should lean back, and do the right thing and get it in there with the right resource push, is that kind of how it's evolving, because that seems like what's-- >> It absolutely is. This goes beyond just EtsyD. The really rad thing is that I think it's safe to say that there is no part of the CoreOS portfolio that really isn't getting open sourced. You can kind of read into that what you will but, it meant that there was no technology that was getting left behind, nad that our users who really felt passionately about pieces of software, again, we're going to be able to have that utility. >> Stu Miniman: I think it goes back, we've been at Red Hat summits for many years and Red Hat is a hundred percent open sourced, it must be, and even I go back to Polvey and yourself and Brandon, all of the tools at CoreOS were creating is, they were all going to be open sourced tools that you will be involved in. I guess William, a good point to bring you into the conversation, Serverless, and fully open source, if not been have you thought about it at least for the last couple of years so, before we get into the Knative, give us the Red Hat positioning, where does Serverless fit into the architecture? And then we'd love to tease out all of the Knative discussion. >> Absolutely. For us, Serverless then is a lot about the user experience, and how we can simplify how developers can leverage technology such as Itsiu and service meshes and everything around the developer experience on top of Kuberneties. Serverless can deliver that and a lot of what we believe is that, it should not be then tied too much to functions because we can do that for functions, but we can do that for any class of applications actually running on top of the platform, and that's a lot of why we believe that Knative is this powerful interesting project going on out there right now. We already have all these different players collaborating, which is fantastic for inter-oper ability, we make sure that we can leverage that implementation on different platforms, we can run that anywhere pretty much on top of Kuberneties, and that's a big goal, to make sure that you can plug all these different parts as part of a consistent user experience there. >> Stu Miniman: Okay so we had the cube at the Google event this summer when it was announced I was at Serverless conference this year and to be honest, a lot of people were kind of scratching their heads trying to understand. Okay, Serverless and Kuberneties are going together but I'm not sure I quite get it? Give us the update where are we, when does this get baked into platforms, what can I do today, where do I learn more? >> Today, what we are offering is the three big modules as part of Knative are built, events, and serving. So it's the basic capabilities for you to build a serverless platform that, can again, work on any kind of application, not only functions, and we are at that stage. The project is very new, we are still in 0.2 release, at this point, so there's a lot of missing parts around user experience and what-not, but we are getting there, and that's where most of the focus is going on right now. But with something like events, that's a perfect opportunity for example, to integrate with all the different services we have available, let's say on Service Catalog, or through the operator's framework, for example, to connect to the applications that you are building on top of Kuberneties. That was part of the things that was missing to connect the dots when your implementing those applications, how are you going to consume events, how are you going to consume services, how those applications are going to scale? That's a lot of what we're addressing with Knative right now. >> What's the big walk away around the current event here at KubeCon? We hear maturity, great, check. A lot of people are fine in their swim lanes or whatever, their value layer, check. Clear a lot more gaps things white space start to appear, when that visibility lifts. What do you guys see the opportunities for the community, and you guys, certainly one of the big players, Red Hat, leading the way, as this ecosystem is, I mean companies I've never heard of, coming out of the woodwork. This is vibrant! There are opportunities for people to kind of, play in these white spaces. Do you guys have any thoughts on where you could give guidance to where people could jump in and create value? >> Well, there's two areas that are really fascinating to me. One is the fact that now that Kuberneties has gotten to the level of boarding infrastructure, it means that there are a lot more companies that are really comfortable saying, "we're building a top that, we don't care about what the compute layer is, because we just know". So you see a lot of organizations that are coming in, because they want to collaborate with other organizations, and see how they're using it to cross pollinate and get new ideas. That's why you've got full retail companies like Nordstrom here, that are the local band in town, and they're happy to come and show off, and you've also got a lot of, to the second piece of that, emerging companies that are finding areas, white space that we didn't consider as the incumbance in the space, and they're providing direct value. I think that as we have seen a lot more acquisitions coming through the space, there is going to be a lot of opportunity for the organization that has that five, ten, fifty million dollar idea to come in, build it quickly, know that it works on top of Kuberneties, and then be able to port it to Enterprise software that runs on a local cluster or across clouds. >> John Furrier: So new business model innovations are coming out of it as well., hence opportunities. It's okay to have a fifty million dollar business. >> Yes. >> Not bad, and could be acquired as well, some other value there. Okay, Microservice is hard to manage. Guys, talk about this dynamic. This is one of the things you guys really work hard to address, I know. We hear a lot about it. Porting to Microservice, "Hey, I'm in Enterprise! We should move from our Red Hat Linux implementation, to full cloud, and then it's going to go all the way to Microservices." Well, what the hell is Microservices? So again, this is kind of like, well I'm not saying that they're thinking that way, but this is not that easy. How do you guys make it easier? What are some of the speed bumps that customers hit? And what are the things to overcome those? What's your view on that? >> [William Oliveria] I'll talk about, first of all, how Knative is contributing to that. Again, the whole thing that we're talking about, not being tied to functions is because again, I want to leverage the serverless capabilities available in the platform for Microservices as well. And whenever you're talking about monitoring, tracing, observe-abilities, Istio comes into play, and solved that problem and connect all those different Microservices in a very nice way. With Knative, things we can improve on the user experience, so you can do that in a very easy way, when you are coming from this brown field applications when you are migrating to the cloud, when you are trying to port those applications, it's a big learning curve. You got to learn about all these different technologies. So if you can improve that user experience, so you can do what you do best, which is focus on your code, and then we can take care of a lot the complexities of building and wiring together all these different parts on the platform. We'll do that. And that's a lot of what we are doing with serverless. >> That's where the manage piece comes in, right? >> [William Oliveria] Right. >> And then the monitoring, that part of it to? >> Yeaa, well to build on top of that, there is the organizations that want to still design things the way that they've been doing it. And we've had a big focus with a project called Red Hat OpenShift Application Runtimes, or RHOAR, which it goes more in the direction of the past concept, which is a big difference between OpenShift and TechTonic, for example, and through that, a lot of the RHOAR bundles for Python and Java and Node.js kind of integrate in the concepts of distributed tracing and permethius monitoring and things like that, to make sure that you focus, again, to William's point, on building the thing that brings yuour business value and standing on the shoulders of software at the infrastructure level. >> That's great stuff and it's a lot more work to do. >> Yeah, just the last thing, I know Red Hat's been working on trying to, I don't know if you call it "templatize", but how do I make it easier for people to, I'm trying to remember the name of the term for it. >> Yeah, so it's the OpenShift Application Runtime. Having what used to be the gear in the old OpenShift realm. Which is just here is a great template, a package to start from, so that you can go in and implement the things that you care about, and really step then into, the "Okay, we know that the code's going to work okay, because we built that, we know the application platform is going to be predictable, we know that we have all of these additional hooks to manage it." So hopefully, it lowers the bar, to make it trivial to get started. >> That's awesome. Well, Redbeard and William, thanks for coming on the Cube, really appreciate it. Just quick plug, what's up next for you guys? What's on the horizon? What itch are you scratching these days? What's getting you motivated? >> The big things that's exciting for me is the fourth coming release of OpenShift 4.0, which gives me the room to shine on the GA release of all the service mesh stuff. And then, kind of in parallel, just a lot of the vector packet processing, FITO, high scale networking stuff just sends a tingle up my spine. I love keeping an eye on that >> For me we just announced a review of Knative and OpenShift as an add-on. You can just install and run that when you're on OpenShift, and like what Redbeard said, I'm looking forward for 4.0 as well, to make sure that I could plug that user experience on top of 4.0 and we are already doing a lot for the ops side, and I'd like to do that also now for our developers as well. >> Well when you're ready, we'll pop a digital cork on Twitter, let us know, we'll certainly cover it. Thanks for coming out, appreciate the insight. >> We'll bring you the insights and all the data here at KubeCon CloudNative. Of course we're the Cube, don't be confused with KubeCon, on one of our conferences coming. But only kidding, we're not going to have that. Thanks for watching day one, live coverage. Stay with us for more coverage after this short break. (techno music)

>> Live from Seattle, Washington, it's the Cube, covering KubeCon and Cloud Native Con North America 2018. Brought to you by Red Hat, the Cloud Native Computing Foundation and its ecosystem partners. >> Welcome back everyone. We are live in Seattle for KubeCon 2018, Cloud Native Con. It's the Cube, I'm John Furrier, your host with Stu Miniman. Our next guest is Ashesh Badani, who is the Vice-President and General Manager of Cloud Platforms at Red Hat. Great to see you, welcome back to the Cube. >> Thanks for having me on. Always good to be back. >> So you guys, again, we talk every year with you. It's almost like a check-in. So what's new? You got some big, obviously, the news about the IBM. We don't really want to get into that detail. I know you just a stop on that because it's already out there. But you guys had great success with platformers of service. Now you got the growth of Kubecon and Cloud Native Con, 8000 attendees and users. There's uptake. What's the update on the Red Had side? >> Yeah, we're excited. Excited to be back at Kubecon. It's bigger and better than it's ever been, I think so. That's fantastic. We've been investing in this community for over four years now, since 2014. Really, from the earliest days. Based the entire platform on it. Continue growing that, adding lots of customers across the world. And I think what's really been gratifying for us to see is just the diversity of participants. Both in user perspective as well as the wider ecosystem. So whether you're a storage player, a networking player, management, marketing, what have you. Everything sort of building around this ecosystem. I think we're creating a great amount of value and we're seeing diverse applications being built. >> So you guys have been good then on (mumbles), good timing, a lot of things are going on. This show is an open-source community, right. And that's been a great thing. This is kind of where the end users come from. But two other personas come in that we're seeing participate heavily. The IT pro, the IT expert, and then the classic developer. So you have kind of a melting pot of how this is kind of horizontally connecting. You guys have been successful in the IT side. Where is this impacting the end users?6 How is this open-source movement impacting IT, specifically, and at the end of the day, the developers who are writing code? Have to get more stuff out. What's your thoughts? >> So, we hosted OpenShift Commons yesterday. OpenShift Commons, for the the folks who don't know, is our gathering of participants within the larger OpenShift community. We had lots of end users come and talk about the reason they're adopting a Kubernetes-based platform is to get greater productivity. So for example, if you're someone like Progressive Insurance, an established organization, how do you release applications quicker? How do you make your developers more productive? How do you enable them to have more languages, tools, frameworks at their disposal? To be able to compete in this world where you've got start-ups, you've got other companies trying to compete aggressively with you. I think it's a big dent here, right? It's not just for if you work traditional IT. But it's for if you were a company of all sizes. >> When you talk about customers, every customer is different. You've got, you look at IT, everything is additive, it tends to be a bit of a heterogeneous mess when you get there. Help connect for us what are you hearing from customers? How does, not just Kubernetes, but everything going on here in the Cloud Native environment? How is it helping them? How is it changing the way that they do their business and how's Red Hat involved? >> So one thing we've been noticing is that Hybrid Cloud is here and here to stay. So we've consistently been hearing this from customers. They've invested lots of money and time and energy, skills, in their existing environments. And they want to take advantage of public clouds. But they want to do that with flexibility, with portability, to bring to bear. What we've been trying to do is focus on exactly that. How do we help solve that problem and provide an abstraction. How do you provide primitives. So, for example, we announced our support of Knative, and how we'll make that available as part of OpenShift. Why's that? Well, how can we provide Serverless primitives within the platform so folks can have the flexibility to be able to adopt next-generation technologies. But to be able to do that consistently regardless of where they deploy. >> So, I love that. Talk about meeting the customers there. One of the things that really strikes me, there's so much change going on in the industry. And that's an area that Red Hat has a couple decades of experience. Maybe help explain how Red Hat in bringing some of that enterprise, oversight. Just like they've done for Linux for a long time. >> Yeah, yeah. Stu, you're following us very closely, as are you John, and the team at the Cube. We're trying to embrace that change as it comes upon us. So, I think the last time I was here, I was here with Alex Polvi of Core OS. Red Hat acquired Core OS in January. >> Big deal. >> Yeah, big acquisition for us. And now we're starting to see the fruits of some of that labor. In terms of integrating that technology. Why did we do that? We wanted to get more automation into the platform. So, customers have said, hey, look, I want these clusters to be more self-managing, self-healing. And so we've been really focused on saying how can we take those challenges the customers have, bring that directly into a platform so they're performing more and more like the expectations that they have in the public cloud, but in these diverse, introgenous, environments. >> That speaks to the operating model of cloud. You guys have a wholistic view because you're Red Hat. You got a lot of customers. You have the Dev House model, you got the Kubernetes container orchestration, micro-services. How does that all connect together for the customer? I mean, is it Turn Key and Open Shift? You guys had that nice bet with Core OS, pays big, huge dividends. What are some of those fruits in the operating model? So the customer has to think about the systems. It's a systems model, it's an operating system, so-to-speak. But they still got to develop and build apps. So you got to have a systems-wholistic view and be able to deliver the value. Where does it all connect? What's your explanation? >> So distributed systems are complex. And we're at the point where no individual can keep track of the hundreds, the thousands, the hundred-thousand containers that are running. So, the only way, then, to do it is to be able to say, how can the system be smart? So, at the Commons yesterday we had sort of a tongue-in-cheek slide that said, the factory of the future will only have two employees, a man and a dog. The man's there to feed the dog, and the dog's in place to ensure the man doesn't go off and actually touch the equipment. And the point really being, how can we bring technology that can bring that to bare. So, one example of that is actually through our Core OS acquisition. The Core OS team was working on a technology called, operators. Which is to say, how can we take the human knowledge that exists. To take complex software that's built by third parties and bring that natively into the platform and then have the platform go and manage them on behalf of the actual customer itself. Now we've got over 60 companies building operators. And we've, in fact, taken entire open-shift platforms, put operators to work. So it's completely automated and self-managed. >> The trend of hybrid is hot. You mentioned it's here to stay. We would argue that it's going to be a gateway to multi-cloud. And as you look at the stacks that are developing and the choices, the old concept of a stack-- and Chris was on earlier, the CTO of CNCF. And I kind of agree with him. The old notion of stack is changing because if you've got a horizontal, scale-able cloud framework, you got specialty with machine learning at the top, you got a whole new type of stack model. But, multi-cloud is what the customers want choice for. Red Hat's been around long enough to know what the multi-vendor word was years ago. Multi-vendor choice, multi-cloud choice. Similar paradigms happening now. Modern version of multi-vendor is multi-cloud. How do you guys see the multi-cloud evolution? >> So we keep investing and helping to make that a reality. So, last week, we made some announcements around Open Shift dedicators. Open Shift dedicators is the Open Shift manage service, or AWS. Open Shift is available in ways where it can be self-managed directly by customers in a variety of environments. Directly run around any public cloud or open stack, or what you'd like environment. We have third-party partners. For example, DXC D-systems providing managed versions of Open Shift. And then you can have Red Hat managed Open Shift for you. For example, on AWS, or coming next year, with Microsoft. Through our partnership for Open Shift on Azure. So you as a customer now have, I think, more choice than you ever had before. In terms of adopting Dev-Ops or dealings with micro-services. But then having flexibility with regard to taking advantage of tools, services, that are coming from, pretty much, every corner of IT industry. >> You guys have a huge install base. You've been servicing customers for many, many years, decades. Highest level support. Take us through what a customer, a traditional Red Hat customer that might not be fully embracing the cloud in the past, now is on-boarding to the cloud. What's the playbook? What do you guys offer them? How do you engage with them? What's the playbook? Is it, just buy Open Shift? Is there a series of-- how do you guys bring that Red Hat core Lenux customer that's been on Prim. Maybe a little bit out of shadow IT in the cloud, saying, hey, we're doing additional transformation. What's the playbook? >> So, great question, John. So, first fall into the transformation might be an over-hyped term. Might be a peak hype at this point in time. But I think that the bigger point from my perspective is how do you move more dollars, more euros, more spend towards innovation. That's what every company is sort of trying to do. So, our focus is, how can we build on the investments that they've made? At this point in time, (mumbles) Lenux probably has 50,000 customers. So, pretty much, every customer, any size, around the world, is some kind of Lenux user. How can we then say, how can we now provide you a platform to have greater agility and be able to develop these services quicker? But, at the same time, not forget the things that enterprises care about. So, last week we had our first big security issue released on Kubernetes. The privilege escalation flaw. And so, obviously, we participate in the community. We had a bunch of folks, along with others addressing that, and then we rolled our patches. Our patch roll-out went back all the way to version 3.2, 3.2 shipped in early 2016. Now, the one hand you say, hey, everyone has Dev-Ops, why do you need to have a patch for something that's from 2016? That's because customers still aren't moving as quickly as we'd like. So, I just want to temper, there's an enthusiasm with regard to, everyone's quick, everything's lightning fast. At the same time, we often find-- and so, going back to your question, we often find some enterprises will just take a little bit longer, in reality to kind of get-- (both speaking at once) >> Work loads, they're not going to be moving overnight. >> That's right. >> So there's some legacy from those workloads. >> Right, right. And so, what we want to do is ensure, for example, the platform. So we talked about the security and lifecycle. But, is supporting these Cloud Native, next generation, stateless applications, but also established legacy stateful applications all on the same platform. And so the work we're doing is ensure we don't-- you know, it's like, leave no application behind. So, either the work that we'll do, for example, with Red Hat Innovation Labs. We help sort of move that forward. Or with GSIs, global integrated, real integrators to bring those to bare. >> Ashesh, wonder if we could drill a little bit. There's a lot of re-training that needs to happen. I've been reading lots on there. It's not, oh, I bring in this new Cloud Native team that's just going to totally re-vamp it and take my old admins and fire them all. That's not the reality. There's not enough training people to do all of this wonderful stuff. We see how many people are at this show. Explain what Red Hat's doing. Some of the training maturation, education paths. >> So we do a lot of work on the just core training aspect, learning services, get folks up to speed. There's work that happens, for example, in CNCF. But we do the same thing around certifications, around administering the systems, developing applications, and so on. So that's one aspect that needs to be learned. But then there's another aspect with regard to how do we get the actual platform, itself, to be smart enough to do things, that in the past, individual people had to do? So, for example, if we were to sort of play out the operator vision fully and through execution. In the past, perhaps you needed several database admins. But, if you had operators built for databases, which, for example couch, base, and mongo, and others, have built out. You can now run those within the platform and then that goes and manages on behalf. Now you don't need as many database admins, you free those people up now to build actual business innovation value. So, I think what we're trying to do is increasingly think about how we sort of, if you will, move value up the stack to free up resources to kind of work on building the next generation of services. And I think that's our business transformation work. >> And I think, even though digital transformation is totally over-hyped, which I agree, it actually is really relevant. Because I think the cloud wave, right now, has been certainly validated. But what's recognized is that, people have to re-imagine how they do their infrastructure. And IT is programmable. You're seeing the network. The holy trinity of IT is storage, networking, and compute. So, when you start thinking about that in a way that's cloud-based, it's going to require them to, I don't want to say re-platform, but really move to an operating-environment that's different, that they used to have. And I think that is real. We're seeing evidence of that. With that in mind, what's next? What do you guys got on the horizon? What's the momentum here? What's the most important story that you guys are telling here at Red Hat? And what's around the corner? >> Yeah, so obviously, I talked about a few announcements that we made right around Open Shift Dedicated and the upgrades around that. And things like, for example, supporting bring-your-own-cloud. So, if you got your own Amazon security credentials, we help support that. And manage that on your behalf, as well. We've talked this week about our support native, trying to introduce more server-less technologies into Open Shift. We announced the contribution of SCD to the Cloud Native Computing Foundation. So, continuing re-affirming our commitment to the community I think looking ahead, going forward, our focus next year will be on Open Shift four, which will be the next release of the platform. And there, it's all about how do we give you a much better install than upgrade experience than you've had before? How do we give you these clusters that you can deploy in multiple different environments and manage that better for you? How do we introduce operators to bring more and more automation to the platform? So, for the next few months our focus is on creating greater automation in the platform and then enabling more and more services to be able to run on that. >> Pretty exciting for you guys riding the wave, the cloud wave. Pretty dynamic. A lot of action. You've guys have had great success, congratulations. >> Thank you very much. >> You're fun to watch. The Cube coverage here. We're in Seattle for KubeCon 2018 and Cloud Native Con. I'm John your host. Stay with us for more coverage of day one of three days of coverage after this short break. We'll be right back. (upbeat music)

>> Live, from Las Vegas, it's the Cube, covering AWS re:Invent 2018, brought to you by Amazon Web Services, Intel, and their ecosystem partners. >> Hey welcome back everyone, live here in Las Vegas for AWS re:Invent 2018, all the action is happening for Amazon Web Services. I'm John Furrier, Dave Vellante, Dave six years covering Amazon, great opportunity, a lot of news, Red Hat is a big part of it, Mike Ferris is here. Vice President, Technical Business Development for Red Hat, welcome back, good to see you. >> Likewise. >> A lot's going with you guys since our Red Hat Summit days in San Francisco just a few months ago. >> Yeah. >> Big news hit. >> Yeah. >> The bomb around the world, the rock that hit the ground really hard, shook everyone up, surprised everyone including me, I'm like "Wow, IBM and Red Hat". What an interesting relationship, obviously the history with IBM has been good. Talk about the announcement with IBM because this is huge. Of course, big numbers, but also impact wise pretty big. >> Yeah, it's exciting times right? And if you kind of look at, you know, from the perspective of Red Hat in this, this will allow us to really scale and accelerate what we've already been doing for the past, you know, since really the 1994 era when Red Hat was founded and, you know, it kind of validates a lot of what we've put into open source and enterprise customers since then. You know, we really see a couple of key outtakes from this, one of which is, certainly it's going to give us the resources to be able to really grow with the scale that we need to. It's also going to allow us to invest more in open source in emerging areas, bring the value of scale and certainly choice and flexibility to more customers, and then ultimately kind of the global advantage of hybrid and multi cloud, we'll be able to reach more partners and customers everywhere, and it puts us several years ahead of where we have been and where we would have been frankly, and ultimately our intent is that with IBM we'll become the leading hybrid and multi cloud provider overall. >> Yeah, Jimmy and Jim Whitehurst kind of ruined our Sunday, we were sitting down to watch football and he's like got the announcement. And then Jimmy kept saying "It's not backend loaded, it's not backend loaded" and then you start to realize, wow, IBM has an enormous business of managing applications that need to be modernized and OpenShift is obviously a great place to do that so, it's got to be super exciting for you guys to have that giant new opportunity to go after as well as global scale that you didn't have before. >> And, you know, this extends the stuff that we did, announced in May at Red Hat Summit with IBM where we really focused on how do we take WebSphere DB2MQ, running on IBM cloud private, running on OpenShift, and make that the hybrid choice. And so it's a natural extension of what we've already been doing and it gives us a lot more resources than we would have otherwise. >> This is good, coming into the next segment I want to chat about is RHEL, and what people might not understand from the announcment is the synergy you guys have with IBM because, being a student of Red Hat, being just in the industry when you guys were rebels, open source, second tier citizen, and the enterprise, the adoption then became tier one service. I mean you guys have, level of service, 17 years or something, huge numbers, but remember where it all started. And then you became a tier one supplier to almost all the enterprises, so you're actually a product company as well as a huge open source player. That's powerful and unique. >> Absolutely, even if you look at kind of what Amazon is doing this week and have been doing over the years, they're a huge value ad provider of open source technology as well, and one of the statements that we've always made is, the public cloud would not exist if not for Linux and open source, and so everything has been based upon that. There's one provider that doesn't use Linux as the base of their platform but certainly as we've taken the in roads into the enterprise, you know, I was there when it started with just turning Red Hat Enterprise Linux on and then bringing it from the edge of network into the data center and talking about major providers like Oracle, HP, Del, IBM as part of that. Now, we're looking at "Is it a de facto standard?", and everyone including Amazon and all of it's competitors are really invested heavily in the open source world. >> And so, let's talk about the impact to the products, okay so one of the things that has come up, at least on my Twitter feed and the conversations is, okay, it's going to take some time to close the deal, you're still Red Hat, you're still doing your things, what's the impact to the customers and to the ecosystem in your mind? How are you guys talking about that right now? Obviously, it's more of the same, keep the Red Hat same, unique, independent, what new thing is going to come out of it? >> So, to be clear, the deal has not closed, right, so there's not a lot we're going to say otherwise. >> A year away, you got a lot of work to do. >> Our focus is what it always has been. Let's build the best enterprise products using the open source development model and make those available across all public and hybrid cloud environments. >> At a certain level, that's enterprise, multi-year, old Red Hat, same Red Hat model, alright. >> But let me follow up on that, because you're a believer in multi cloud, we're a believer in, whatever you call it, multiple clouds, customers are going to use multiple clouds. We believe that, you believe that, it seems like Amazon has a slightly different perspective on that, >> Cause they're one cloud. >> in that this greater value, right cause they're one cloud, there's greater value, but it seems like the reality when you talk to customers is, we're not just one company, we've got different divisions, and eventually we've got to bring those together in some kind of extraction layer. That's what you guys want to be, right? So, your perspectives on multi cloud? >> Absolutely, so, each individual department, each project, each developer, in all of these major enterprises, you know, has a different vantage, and yes, there are corporate standards, golden masters of RHEL that get produced, everybody's supposed to be using, but you know, the practicalities of how you develop software, especially in the age of dev ops and containers and moving forward is actually, you have to have the choice necessary to meet your specific needs, and while we will absolutely do everything we can to make sure that things are consistent, I mean, we started this with RHEL consistency, on and off premise, when we did the original Amazon relationship. The point is, you need to be able to give people the flexibility and choice that they desire, regardless of what area of the company that they're in, and that's going to be the focus, regardless of whether it's Microsoft, Amazon, Google, IBM clouds, international clouds with Alibaba, it's all the same to us and we have to make sure it's there. >> What's always great about the cloud shows, especially this one, it's one of my favorites, because it really is dev ops deep in the mindset culture. As you see AI and machine learning start to get powered by all these great resources, computer, et cetera, the developer is going crazy, there's going to be another renaissance in software development, and then you got things like Kubernetes and containers now mainstream. Kubernetes almost, I say, de facto standard. >> Yeah. >> Absolutely happened, you guys had a big part of making that happen. People are now agreeing on things, so the formation's coming together pretty quickly, you're seeing the growth, we're hearing terms like "co-creation", "co-opetition", those are signals for a large rising tide, your thoughts? >> So, it's interesting, we were an early investor in Kubernetes, we actually launched OpenShift prior to Kubernetes, and then we adopted it and made a shift of our platform before it was too late. We did the same thing with hypervisors when we moved from Zen to KBM, but this overall approach is, once we see the energy happening both in the community and the early customers, then you see the partners start to come on board, it becomes the de facto standard, it's really crucial for us as an open source company to make sure we follow those trends, and then we help mature them across the business ecosystem, and that's something we've loved being able to engage with. I mean, Google certainly instigated the Kubernetes movement, but then it starts to propagate, just like on the open stack side, it came out of Rackspace and Nasa and then moved on to different areas and so, you know, our focus is, how do we continue that choice and that evolution overall? >> How would you talk about the impact of Kubernetes if someone says "Hey Mike, what's the real impact, what is it going to accomplish at the end of the day?" What's your view of that? >> It will have the same impact that the Linux current standardization has had, you know, but in this case for micro services and application packaging and being able to do dev ops much more efficiently across heterogeneous platforms. >> Does it make it easier or less painful or does it go away? Is it automated under the covers? I mean, this is a big, awesome opportunity. >> So the orchestration capabilities of Kubernetes combined with all the other tools that surround key container platforms like OpenShift, really give that developer the full life cycle environment to be able to take something from concept through deployment, and onto the maintenance phases, and you know, what we end up doing is we look at, okay the technologies are there, what value ads to we have around that to make sure that a customer and a developer cn actually maintain this thing long term and keep their enterprise applications up? >> So, security for example. >> Security is a great example, right? How do we make sure that every container that gets deployed on Kubernetes platforms or by Kubernetes platforms, that every container that's deployed which, keep in mind, is an operating system, it has an operating system in the container itself, how is that kept up to date? How do you make sure that when the next security errata is released, from us or a different vendor possibly, how do you make sure that that container is secure? And, you know, we've done a lot in our registry as well as our catalog to make sure that all of our partners and customers can see their containers, know what grade they have in a security context, and be able to grow that. That's one of the core things that we see adding into this Kubernetes value and authorization level. >> It's not a trivial technical problem either. >> No. >> Sometimes micro services aren't so micro. >> It's been part of what we've for RHEL from the start, it's been how do we bring that enterprise value into technology that is maturing out of the open source community and make that available to customers? >> Yeah, one of the key things you guys, first of all, OpenShift has been phenomenal, you guys did a great job with that, been watching that grow, but I think a real seminal moment was the CoreOS acquisition. >> Sure. >> That was a real turbo boost for you guys, great acquisition, fits in with the culture, and then Kubernetes just lifted from that, that was the point but, at the timing of all this, Kubernetes gets mainstream lift, people recognize that the standardization it is a good thing, and then, boom, developers are getting engaged. >> Yeah, and if you see what the CoreOS environment has brought us from over their updates for our platforms, to being able to talk about a registry in the environment. Being able to say that, is kind of additive to this overall messaging, it really rounds out the offering for us, and allows us to participate even more deeply in the communities as well. >> Well, we're looking forward to keeping you covered, we love Kubernetes, we've got a special report called "Kubernetes Special Report" on siliconangle.com, it's called "The Rise Of Kubernetes", it's a dedicated set of content, we're publishing a lot on Kubernetes. Final question I want to get to you because I think it's super important, what's the relationship you have with AWS? And take some time to explain the partnership, how many years, what you guys are doing together, I know you're actively involved, so take a minute. >> It is somewhat blurry, it's been a long time, so 2007 era is when we started in depth with them, and I can remember the early days, actually in the development of S3, prior to EC2, being able to say alright, what is this thing and how does Red Hat participate in this? And I think, yesterday Terry Wiese even mentioned that we were one of the first partners to actually engage in the consumption model and, you know, claiming partial credit for out 34 billion dollar valuation that we just got announced. But, you know, overall the relationship really spawned out of that, how do we help build a cloud and how do we help offer our products to our customers in a more flexible way? And so that snowballed over the years from just early adopters being able to play with it to now where you see it's many many millions of dollars that are being generated in customers and they think, in the hundreds of millions of hours of our products being consumed, at least within a month if not shorter timeframes, every time period we have. >> You know that's an unsung benefit that people might not know about with Red Hat is that, you guys are in early markets because, one, everyone uses Linux pretty much these days for anything core, meaningful. And you listen to community, and so you guys are always involved in big moving things, cloud, Amazon, 2007, it was command line back then. >> Yeah. >> It wasn't even, I think RightScale just came online that year, so you remember. You guys are always in all these markets so it's a good indicator, you guys are a bellwether, I think it's a good beacon to look at. >> And we do this, certainly on the container space, and the middleware space, and the storage space, you know, we replicate this model and, including in management, about how do we actually invest in the right places where we see the industry and communities going so we can actually help those? >> And you're very partner friendly, you bring a lot to the table, I love the open source ethos, I think that's the future. The future of that ethos of contributing to get value downstream is going to be a business practice, not just software, so you guys are a big part of the industry on that and I want to give you guys props for that. Okay, more Cube coverage here in Las Vegas, AWS Reinvent, after this short break, more live coverage, I'm John Furrier, Dave Vellante, we'll be right back. (electronic music)

(upbeat music) >> Live from Las Vegas, it's theCUBE, covering AWS re:Invent 2018, brought to you by Amazon Web Services, Intel, and their ecosystem partners. >> Well, welcome back here, as we continue our coverage at AWS re:Invent, along with Justin Warren, I'm John Walls, we are live in Las Vegas in the Sands. Day one of our coverage here, three days, with you all week. We're with Jon Masters now, who's the chief architect at Red Hat. Jon, good to see you this afternoon. >> Thank you, nice to be here. >> First off, give me your impression of what you've seen so far on the show floor, what's the feeling you've got as you come in this week? Well, it's been absolutely fabulous for me. It's my first time at re:Invent, so I've not had chance to witness firsthand the growth over the few years, but I've heard stories that we're up to 75,000 people, some very high number this year, and the growth is absolutely amazing. Very, very passionate people, it's very clear that the story of containerization and microservices is foremost this year, and yeah, it's just a fabulous experience to be here. >> Great, now yesterday, there was announcement from AWS about A1 instance, tell me a little bit about how that comes to play in a Red Hat and just your take on the release. >> Yeah, so Amazon did announce yesterday the new A1 instance type, and it's based on the Arm architecture, I think the interesting thing for me is that it's based on a processor that they themselves built called the Graviton. You know, this is really the culmination of what we've seen in the industry in the past few years. As the cloud vendors get bigger and have greater resources and greater capabilities, what they can do is they can take that self-determination aspect, and they can say, you know what, we're now big enough, and we now understand, and we're sophisticated enough that we can say we would like to deliver this to our customers, and we don't have to wait for someone to build it for us, we can just go and do it. And so what they did is they licensed an Arm design from Arm Holdings, the actual core inside the processor, and then they built the chip themselves, and contracted out to a foundry, manufactured and deployed these, and then, you know, they can snap their fingers and deploy these and, surprise, now we have Arm-based instances, so it's been very interesting. >> So I'm curious, 'cause we keep getting told that software is leading the world, and yet here we are, building hardware and customized hardware. So what is it about the Arm architecture in particular, but also the fact that you can build custom silicone, what is it that Amazon, or indeed any other cloud vendor, what benefit do they get from manufacturing their own silicone here? >> That's a very good question. Well, I think there's multiple aspects to it. At the end of the day, people tell me that the future is serverless, and I remind them that there's still servers somewhere, right? So we still need to have computers. Of course, we're going to have a smaller number of very big vendors on which we rely, I mean, we're seeing that with the adoption of public cloud, and as these vendors get bigger, they have that scale that they can invest what, for them, is a modest amount of money, for anybody else, it'd be a fortune, but a modest amount, and they can go and build a design. Now, with a traditional microprocessor design, you'd take a team of four people, and you would spend many hundreds of millions of dollars, maybe 300 million dollars over four years, to build a high-performance processor. What you can do with Arm is work with Arm Holdings, which is now a part of SoftBank, to license kind of cookie-cutter pre-made pieces, so you can license a processor core, and you can stamp it out and say, well, I'll have 16 of those in my chip. So you don't have to do the heavy lifting to design many of the building blocks, but you can integrate them together, so you get a lot of cost-efficiency there, you don't have to go and do all that design, but you can integrate building blocks. And the key piece there, I think, is the ability to choose how you want to integrate that and what you want to build. Right? And then, what we're seeing in the industry is that compute is becoming boring, right? I mean, everyone needs compute, but what are we talking about? We're talking about machine learning and GPUs and tensors and all kinds of other accelerators, right? So, the interesting thing for me is, once you've made the compute kind of so commodity that you can just license it from somebody and stamp out your own design, what opportunity does that bring later to maybe integrate various accelerators and other hardware goodies? I don't know what Amazon plan to do, but if I had a crystal ball, I would say this is probably not the end. This is kind of the beginning of a journey, and now they will have the ability to integrate some very interesting and novel hardware advances of their own as well. Okay, 'cause that does sort of lead into what my next question going to be. Which is, for a customer of Amazon, it's like, well, I don't know anything about the internals of chip design, why would I want to choose the A1 instance type over one of the other existing instance types? What's in it for me? >> Yeah, very good question. I think when Amazon announced it last night, the top line that the media picked up on first was the price benefit there, which was advertised as being 40% lower for certain workloads. Now the design that they've chosen today is not about having that top-shelf performance, that top-line performance. If you want that level of performance, clearly you're going to use one of the existing instance types. But if you want to have something that is more cost-effective for at-scale deployments, maybe where you're not using all the compute resources that you need, you're more memory-bound, or you're doing web app-serving, this kind of thing, in that case, you don't really need that level of compute. You still need the instances, and so this brings your cost down when you're doing that at-scale kind of deployment. And that seems to be where they're targeting. And in addition, they're targeting, I think, developers, and those that want to invest in the Arm ecosystem, because clearly this is the beginning of a journey, I don't know exactly where they'll go next, but one could imagine that it will continue from here. >> Okay, now you are an Arm fan. >> I am. >> But we don't actually work for Arm, you work for Red Hat, so what's the Red Hat angle here? >> Well, so I'll tell you a story. >> Okay, I like stories. (men laughing) >> Me too, so back at the end of-- >> I like stories too, Jon, go ahead. >> Well, I'll spare you the long form. The end of 2010, I was in one of my execs' offices, and I've been with Red Hat since 2006, and I had done a couple of things before that that kind of were very useful for the company but kind of dull, so they said, "All right, you choose something exciting to work on next," right? So I held up a BeagleBoard, which is a bit like a raspberry pie, and I told one of my execs, "This will be a server one day." And I walked through Moore's law and the pace of innovation and fast-forwarded and say, if these things were to happen, this technology would be in a server. Now why is that relevant to Red Hat? Well, if you look at it from Red Hat's point of view, we don't pick winners and losers, what we do is we work with customers and what they want to adopt, but we also need to be able to respond to our customers' needs, so kind of the concern was, this Arm thing looks like it could be interesting in a few years' time, what if it is? And if it is interesting, and it's kind of a zoo, as I used to call it, a free-for-all, you know, it's kind of an embedded mess, that works fine, well "fine" in quotes, if you're building cell phone widgets and so on, because it's kind of a different ecosystem there, but if you want to have a mainstream server play, we had to have a few of us in industry come in and say, all right, this looks interesting, but let's make sure that the level of standardization is there, so that if this does take off, standard operating systems and standard software can run on it, that's why we cared, was just in case it takes off. And then fans like me, of course, want to kind of promote it as well, but I think that's why Red Hat cared. >> You know, and this is kind of off-topic, but I'm just curious, because you've talked about the acceleration of change, you've talked about innovation, you've talked about new wrinkles, and Moore's law, is it possible, or do you see that the acceleration of change is so rapid that we're almost outpacing ourselves in a way? And that change is happening so dramatically and so quickly that to make a decision on a particular solution or service is difficult because you're afraid of missing the next flavor in eight months or nine months, instead of three or five years? >> That's right, and I think there's another piece there where the cloud makes even more sense, doesn't it? Because if you are a customer, or an end-user, and you're deploying an app, you could say, well, this Arm thing could be interesting, I don't know, I don't want to go and build out physical infrastructure and go and pay that tax to go and figure this out, what I want to do is I just want to try it out right now. And the fabulous thing that Amazon did yesterday, that no one had done, you know, there'd been some efforts out there to provide Arm to the mainstream, right? But Amazon put a giant rubber stamp on it and said, this is good enough for us, and it works. Now anyone who's used to a workflow in EC2, they can just use exactly the same flow to spin up one of these instances and try it out. It's a 30-second thing, just try it out, see what you think. If you like it, great, if you don't, then don't use it. And because you are able to just consume it, according to whatever you want, you don't have that commitment either, yeah. >> So a test drive? >> You can test drive it, if it works well, you can adopt it. There's no obligation, and that's, I think, key to exploring new technologies as well. >> Yeah, it does require you to have that software layer on top of it that runs, we were talking before, that Red Hat has invested a lot to actually get the Red Hat software suite to run on Arm. >> That's right. >> So I'm sure that with this announcement, there's going to be a whole lot of other people suddenly discovering how to compile to the Arm architecture. (Jon laughs) That'll be fun. >> That's right, we've invested for the last eight years in this, and what we have now is a strategy we call our multi-architecture strategy. So again, we don't pick winners and losers, we have all these different architectures that we support, obviously x86, also Power, and Mainframe, and now Arm, and all these architectures are treated equally going forward, so in RHEL 8, which we just announced the beta of RHEL 8, you'll see all these architectures treated just the same. And so the rule for our developers is, whenever they make a change, it has to run on all the architectures equally. >> Democratize it, and then make it so that it is standard across the board. >> That's right. >> Makes sense. Jon, thanks for the time. >> Oh, absolutely. >> Good to see you here at re:Invent, and wish you all the success down the road. >> Thank you very much. >> You bet. Jon Masters joining us from Red Hat. Back with more, we are here at AWS re:Invent, we're live in Las Vegas, and Justin and I'll be back in just a moment.

>> Live from New York, it's theCUBE, covering theCUBE New York City 2018. Brought to you by SiliconANGLE Media and its ecosystem partners. >> Hello, everyone, welcome back. This is theCUBE live in New York City for theCUBE NYC, #CUBENYC. This is our ninth year covering the big data ecosystem, which has now merged into cloud. All things coming together. It's really about AI, it's about developers, it's about operations, it's about data scientists. I'm John Furrier, my co-host Dave Vellante. Our next guest is Brent Compton, Technical Marketing Director for Storage Business at Red Hat. As you know, we cover Red Hat Summit and great to have the conversation. Open source, DevOps is the theme here. Brent, thanks for joining us, thanks for coming on. >> My pleasure, thank you. >> We've been talking about the role of AI and AI needs data and data needs storage, which is what you do, but if you look at what's going on in the marketplace, kind of an architectural shift. It's harder to find a cloud architect than it is to find diamonds these days. You can't find a good cloud architect. Cloud is driving a lot of the action. Data is a big part of that. What's Red Hat doing in this area and what's emerging for you guys in this data landscape? >> Really, the days of specialists are over. You mentioned it's more difficult to find a cloud architect than find diamonds. What we see is the infrastructure, it's become less about compute as storage and networking. It's the architect that can bring the confluence of those specialties together. One of the things that we see is people bringing their analytics workloads onto the common platforms where they've been running the rest of their enterprise applications. For instance, if they're running a lot of their enterprise applications on AWS, of course, they want to run their analytics workloads in AWS and that's EMRs long since in the history books. Likewise, if they're running a lot of their enterprise applications on OpenStack, it's natural that they want to run a lot of their analytics workloads on the same type of dynamically provisioned infrastructure. Emerging, of course, we just announced on Monday this week with Hortonworks and IBM, if they're running a lot of their enterprise applications on a Kubernetes substrate like OpenShift, they want to run their analytics workloads on that same kind of agile infrastructure. >> Talk about the private cloud impact and hybrid cloud because obviously we just talked to the CEO of Hortonworks. Normally it's about early days, about Hadoop, data legs and then data planes. They had a good vision. They're years into it, but I like what Hortonworks is doing. But he said Kubernetes, on a data show Kubernetes. Kubernetes is a multi-cloud, hybrid cloud concept, containers. This is really enabling a lot of value and you guys have OpenShift which became very successful over the past few years, the growth has been phenomenal. So congratulations, but it's pointing to a bigger trend and that is that the infrastructure software, the platform as a service is becoming the middleware, the glue, if you will, and Kubernetes and containers are facilitating a new architecture for developers and operators. How important is that with you guys, and what's the impact of the customer when they think, okay I'm going to have an agile DevOps environment, workload portability, but do I have to build that out? You mentioned people don't have to necessarily do that anymore. The trend has become on-premise. What's the impact of the customer as they hear Kubernetese and containers and the data conversation? >> You mentioned agile DevOps environment, workload portability so one of the things that customers come to us for is having that same thing, but infrastructure agnostic. They say, I don't want to be locked in. Love AWS, love Azure, but I don't want to be locked into those platforms. I want to have an abstraction layer for my Kubernetese layer that sits on top of those infrastructure platforms. As I bring my workloads, one-by-one, custom DevOps from a lift and shift of legacy apps onto that substrate, I want to have it be independent, private cloud or public cloud and, time permitting, we'll go into more details about what we've seen happening in the private cloud with analytics as well, which is effectively what brought us here today. The pattern that we've discovered with a lot of our large customers who are saying, hey, we're running OpenStack, they're large institutions that for lots of reasons they store a lot of their data on-premises saying, we want to use the utility compute model that OpenStack gives us as well as the shared data context that Ceph gives us. We want to use that same thing for our analytics workload. So effectively some of our large customers taught us this program. >> So they're building infrastructure for analytics essentially. >> That's what it is. >> One of the challenges with that is the data is everywhere. It's all in silos, it's locked in some server somewhere. First of all, am I overstating that problem and how are you seeing customers deal with that? What are some of the challenges that they're having and how are you guys helping? >> Perfect lead in, in fact, one of our large government customers, they recently sent us an unsolicited email after they deployed the first 10 petabytes in a deca petabyte solution. It's OpenStack based as well as Ceph based. Three taglines in their email. The first was releasing the lock on data. The second was releasing the lock on compute. And the third was releasing the lock on innovation. Now, that sounds a bit buzzword-y, but when it comes from a customer to you. >> That came from a customer? Sounds like a marketing department wrote that. >> In the details, as you know, traditional HDFS clusters, traditional Hadoop clusters, sparklers or whatever, HDFS is not shared between clusters. One of our large customers has 50 plus analytics clusters. Their data platforms team employ a maze of scripts to copy data from one cluster to the other. And if you are a scientist or an engineer, you'd say, I'm trying to obtain these types of answers, but I need access to data sets A, B, C, and D, but data sets A and B are only on this cluster. I've got to go contact the data platforms team and have them copy it over and ensure that it's up-to-date and in sync so it's messy. >> It's a nightmare. >> Messy. So that's why the one customer said releasing the lock on data because now it's in a shared. Similar paradigm as AWS with EMR. The data's in a shared context, an S3. You spin up your analytics workloads on AC2. Same paradigm discussion as with OpenStack. Your spinning up your analytics workloads via OpenStack virtualization and their sourcing is shared data context inside of Ceph, S3 compatible Ceph so same architecture. I love his last bit, the one that sounds the most buzzword-y which was releasing lock on innovation. And this individual, English was not this person's first language so love the word. He said, our developers no longer fear experimentation because it's so easy. In minutes they can spin up an analytics cluster with a shared data context, they get the wrong mix of things they shut it down and spin it up again. >> In previous example you used HDFS clusters. There's so many trip wires, right. You can break something. >> It's fragile. >> It's like scripts. You don't want to tinker with that. Developers don't want to get their hand slapped. >> The other thing is also the recognition that innovation comes from data. That's what my takeaway is. The customer saying, okay, now we can innovate because we have access to the data, we can apply intelligence to that data whether it's machine intelligence or analytics, et cetera. >> This the trend in infrastructure. You mentioned the shared context. What other observations and learnings have you guys come to as Red Hat starts to get more customer interactions around analytical infrastructure. Is it an IT problem? You mentioned abstracting the way different infrastructures, and that means multi-cloud's probably setup for you guys in a big way. But what does that mean for a customer? If you had to explain infrastructure analytics, what needs to get done, what does the customer need to do? How do you describe that? >> I love the term that industry uses of multi-tenant workload isolation with shared data context. That's such a concise term to describe what we talk to our customers about. And most of them, that's what they're looking for. They've got their data scientist teams that don't want their workloads mixed in with the long running batch workloads. They say, listen, I'm on deadline here. I've got an hour to get these answers. They're working with Impala. They're working with Presto. They iterate, they don't know exactly the pattern they're looking for. So having to take a long time because their jobs are mixed in with these long MapReduce jobs. They need to be able to spin up infrastructure, workload isolation meaning they have their own space, shared context, they don't want to be placing calls over to the platform team saying, I need data sets C, D, and E. Could you please send them over? I'm on deadline here. That phrase, I think, captures so nicely what customers are really looking to do with their analytics infrastructure. Analytics tools, they'll still do their thing, but the infrastructure underneath analytics delivering this new type of agility is giving that multi-tenant workload isolation with shared data context. >> You know what's funny is we were talking at the kickoff. We were looking back nine years. We've been at this event for nine years now. We made prediction there will be no Red Hat of big data. John, years ago said, unless it's Red Hat. You guys got dragged into this by your customers really is how it came about. >> Customers and partners, of course with your recent guest from Hortonworks, the announcement that Red Hat, Hortonworks, and IBM had on Monday of this week. Dialing up even further taking the agility, okay, OpenStack is great for agility, private cloud, utility based computing and storage with OpenStack and Ceph, great. OpenShift dials up that agility another notch. Of course, we heard from the CEO of Hortonworks how much they love the agility that a Kubernetes based substrate provides their analytics customers. >> That's essentially how you're creating that sort of same-same experience between on-prem and multi-cloud, is that right? >> Yeah, OpenShift is deployed pervasively on AWS, on-premises, on Azure, on GCE. >> It's a multi-cloud world, we see that for sure. Again, the validation was at VMworld. AWS CEO, Andy Jassy announced RDS which is their product on VMware on-premises which they've never done. Amazon's never done any product on-premises. We were speculating it would be a hardware device. We missed that one, but it's a software. But this is the validation, seamless cloud operations on-premise in the cloud really is what people want. They want one standard operating model and they want to abstract away the infrastructure, as you were saying, as the big trend. The question that we have is, okay, go to the next level. From a developer standpoint, what is this modern developer using for tools in the infrastructure? How can they get that agility and spinning up isolated, multi-tenant infrastructure concept all the time? This is the demand we're seeing, that's an evolution. Question for Red Hat is, how does that change your partnership strategy because you mentioned Rob Bearden. They've been hardcore enterprise and you guys are hardcore enterprise. You kind of know the little things that customers want that might not be obvious to people: compliance, certification, a decade of support. How is Red Hat's partnership model changing with this changing landscape, if you will? You mentioned IBM and Hortonworks release this week, but what in general, how does the partnership strategy look for you? >> The more it changes, the more it looks the same. When you go back 20 years ago, what Red Hat has always stood for is any application on any infrastructure. But back in the day it was we had n-thousand of applications that were certified on Red Hat Linux and we ran on anybody's server. >> Box. >> Running on a box, exactly. It's a similar play, just in 2018 in the world of hybrid, multi-cloud architectures. >> Well, you guys have done some serious heavy lifting. Don't hate me for saying this, but you're kind of like the mules of the industry. You do a lot of stuff that nobody either wants to do or knows how to do and it's really paid off. You just look at the ascendancy of the company, it's been amazing. >> Well, multi-cloud is hard. Look at what it takes to do multi-cloud in DevOps. It's not easy and a lot of pretenders will fall out of the way, you guys have done well. What's next for you guys? What's on the horizon? What's happening for you guys this next couple months for Red Hat and technology? Any new announcements coming? What's the vision, what's happening? >> One of the announcements that you saw last week, was Red Hat, Cloudera, and Eurotech as analytics in the data center is great. Increasingly, the world's businesses run on data-driven decisions. That's great, but analytics at the edge for more realtime industrial automation, et cetera. Per the announcements we did with Cloudera and Eurotech about the use of, we haven't even talked about Red Hat's middleware platforms, such as AMQ Streams now based on Kafka, a Kafka distribution, Fuze, an integration master effectively bringing Red Hat technology to the edge of analytics so that you have the ability to do some processing in realtime before back calling all the way back to the data center. That's an area that you'll also see is pushing some analytics to the edge through our partnerships such as announced with Cloudera and Eurotech. >> You guys got the Red Hat Summit coming up next year. theCUBE will be there, as usual. It's great to cover Red Hat. Thanks for coming on theCUBE, Brent. Appreciate it, thanks for spending the time. We're here in New York City live. I'm John Furrier, Dave Vallante, stay with us. All day coverage today and tomorrow in New York City. We'll be right back. (upbeat music)

>> Live, from Las Vegas! It's theCUBE! Covering the VMworld 2018. Brought to you by VMware and its ecosystem partners. >> Welcome back. We're in Las Vegas, and you're watching theCUBE's exclusive coverage of VMworld 2018. I'm Stu Miniman joined by my cohost Justin Warren, and happy to welcome to the program for the first time, James Labocki, who's a director of product management with Red Hat. And joining him is CUBE alum, Rob Young, who's the lead manager of virtualization product management strategy, also with Red Hat, wearing the shadow man logo. Rob, James, thank you so much for joining us. >> Great to be here >> Thanks for having us. >> Alright, so Rob, we touch base with Red Hat at a number of shows, you know, Red Hat Summit. We spoke with you last year at VMworld. Give us the update, Red Hat's got a nice booth here at the show, A lot of things going on, Red Hat plays in a lot of the multi-cloud environments that I hear VMware talking about, so, talk about your presence here. >> So, Red Hat has done quite a bit of growing over the course of the last year that we talked. We are focused on not only where our customers are today, but also on how our portfolio needs to evolve to where they aspire to be. And by that, I mean, RHEL is still the foundation of our business. We have Red Hat Virtualization, we have OpenStack Platform, we have the OpenShift, as you know, and what we're learning from our customers and the market, is that, on top of RHEL, customers have not only a footprint in the virtualization world, but they have an aspiration to evolve along with the market to more of a containerized world that is managed, orchestrated, delivered via Kubernetes, and we feel that our portfolio is well positioned with the pillars of our business from infrastructure to application middleware all the way through management, to allow them to act on those aspirations, not in the future but right now. So that's where we are. Our strategy is build around that vision and around that level of enablement and market dynamic, right now, so we're excited, would you agree? >> Yeah absolutely. A lot of interest in OpenShifted option, whether that's on the Vmware platform itself, out on the public clouds, and then on KVR, KVM based hypervisors with Red Hat Virtualization OpenStack Platform as well. >> Yeah it's interesting because, I've watched this adoption of containerization in the marketplace. What's the line I hear from Red Hat? It's like, Linux is containers, containers are Linux. >> Hey you got that good. >> Yeah I got the t shirt too. But, you know, here at VMworld, some people are still trying to understand that virtualization versus containers and, "How do I stack things?" "How do I do that?" What do you hear from customers? Where is their head at? Talk to us about, you know, it's pervasive in the product line so how do you think about it internally too? >> Yeah absolutely so, I think containers are absolutely Linux and Linux is fundamental to containers, so I think one of the most interesting paradigms that we're seeing, or one of the interesting trends we're seeing is that as people are beginning to adopt containers, they're also beginning to realize that they're looking to simplify their environments as they do that. And so it's presenting a lot of new opportunities and reinvigoration of other technologies. So things like traditional virtualization that they have in place today, they're looking at, maybe bringing along KVM and starting to orchestrate containers and virtual machines with Kubernetes in a consistent manner across both on-premise and public cloud providers. So, we're really excited to be involved in projects around that. We're helping drive the adoption of that. And with that reinvigoration of KVM as a hypervisor, based on that work, to bring a common orchestration layer we're seeing even reinvigoration of the ecosystem around KVM with partners of ours like Trilio, Maxta, Veeam, and so on and so forth, which have been kind of discussed in... >> Yeah, Sorry. >> Well I was just going to add to what Dave said. What we see also happening is that the Linux market 25 years ago was open-source, contributor laden. Red Hat was fully engaged there, we are seeing that very same dynamic happening in the Kubernetes environment. We actually see that as very much the equivalent of what Linux was 25 years ago, so we are contributing upstream to the Kubernetes project, but our goal really is not only to stabilize and build out Kubernetes, but also to bring the virtualization aspect that we had brought into KVM and to virtualization into the Kubernetes project and community so that we can get rid of an additional layer of complexity around the hypervisor allowing containers to be managed and deployed and to have the same isolation levels that you have with VMs now. So all that is in process now. We've got upstream work going on and we're leading a lot of those contributions in the Kubernetes community, specifically via the Kubert project so anyway... >> Leads nicely into what I wanted to ask about which was, Red Hat has a long history of open-source, and open-source is a really important part of containers in general. What are you seeing for enterprises in their adoption of open-source? I mean clearly you've watched it go from something which was once verboten, to now it's pretty much de facto. So what are you seeing customers using open-source for in this new cloud and container world? >> Yeah so I think, you know, the typical pattern we see is a lot of times previously people would look at open-source as a way to commoditize and reduce cost. That was the beginning of open-sources right, with the UNIX to Linux migrations and things of that nature. Now, open-source and really Linux is at the forefront of a lot of the innovation happening, so customers are using both those, basically, techniques inside of their environments to embrace open-source. So at one point, they're using their Linux skills to commoditize things inside their environment or reduce cost. They're also looking at it as the basis of containers, microservices, machine learning, so on and so forth, so really this common skillset of Linux is kind of on both sides, and it's really rooted in the open-source knowledge and methodologies that our customers need to be able to... >> You hit the nail right on the head when you mentioned that everything that has to do with the new modernization of the data center built on containers is open-source, and Red Hat's participation in the community is we already have credibility in the Linux world and the OpenStack world and the KVM world and the Kubernetes world as well, and what we're seeing on the customer side, specifically enterprise and public sector is, they are embracing open-source. They've actually got strategies that named open-source as part of the criteria for proof of concepts and things like that, and we believe we've been preparing for this moment for the last 25 years, for the market to really see this as an open opportunity, not only for open-source and communities, but also to enable their development staffs to extend and participate in those projects to their advantage, so it's a really good thing, for a Red Hat market. >> Yeah it's certainly encouraging to see it. Having watched it develop, it's been really nice seeing that actually get used with enterprises, and seeing that Red Hat is there, the whole way through that and as a trusted partner I'm sure gives them a lot of confidence. >> One thing I would add is just, it's not just about the ability to deliver open-source and to use it, although delivering that with along lifecycle is something that is a core competency of Red Hat as a company, but also the ability to actually affect change in those communities and get contributions back in is really key. And then, even advising customers on how to do that is something that we're, it's just to say, "Hey we do open-source," but actually providing that lifecycle around it is a whole nother story. >> Red Hat has a lot of experience living in a lot of different environments, just Linux is pervasive in the data center and in the cloud. When you talk about multi-cloud, customers need to figure out how to deal with these multi-could environments and you know, multi-cloud, multi-hypervisor, how does Red Hat help customers through this journey? >> So there's, we have a really good story there and really good enablement. There are basically four footprints that you can deploy an application on, physical, virtual; public, and private cloud, and red hat portfolio deploys nicely there, RHEL, VMs, OpenStack, OpenShift, containers, you name it. So our approach is, not only do we allow the deployment there, but also the management of it as well, and we agree with you wholeheartedly, workloads are portable, they're mobile, people are going to move them between clouds, on site, they're going to burst into clouds, so our solution to that is the management console that we provide with CloudForms, and our management vision going forward for software as a service and some other things that we're doing, is all about that heterogeneous environment. Multiple hypervisor, multiple cloud providers, multiple OSs as well, so, you know, we want people to see Red Hat as a platform to stabilize on, not a solution where they have to go out and cobble together a solution. They should be able to do everything with our product in a portfolio from a single management console, including that heterogeneous environment with multiple hypervisor, multiple cloud. So that's how we approach it and we're building on that concept, not only with CloudForms, but also with the new CoreOS Tectonic Platform that we just, acquired, that'll be part of OpenShift, and then going forward our management business unit is working on software as a service, consumption based model that allows customers to do the same thing from their phone as an example. It's that vision that we've already executed on, but it's only going to get bigger going forward. >> One thing I would add is, one thing that's fundamental to our vision is that we're actually delivering a consistency across all those footprints so, it's not one version of Kubernetes for public cloud, another version for on-premise, a different automation tool here and a different automation tool there, it's consistent right? Ansible automation across bare metal on-premise, virtualization, private, public cloud, OpenShift with the foundation of RHEL, consistent across all those for one version of Kubernetes across all of them. So I think that's a big key differentiator as opposed to some of the other visions where you have one version on public cloud, one version on private, different disparate tools tools for each of those. We really believe in simplifying that from a complexity standpoint. >> Well Rob and James, really appreciate you giving us the update on Red Hat. We'll be back with lots more coverage from VMworld 2018. For Justin Warren, I'm Stu Miniman, thanks for watching theCUBE.

>> Live from San Francisco, it's theCUBE, covering DockerCon 18. Brought to you by Docker and its ecosystem partners. >> Welcome back to theCUBE's continuing coverage of DockerCon 2018. I'm Lisa Martin with John Troyer. We are in San Francisco on a spectacularly sunny day. We're excited to welcome to theCUBE some guys from Red Hat. We've got Ben Breard, Senior Technical Products Manager, and Reza Shafii, VP of Platform Services. Guys, thanks so much for stopping by. >> Thanks for having us. >> Thank you. >> It's great. >> So, Reza, you come from the CoreOS acquisition, you've been with Red Hat for about five months, Ben, you've been there about eight years, but I did see online that it's Red Hat's 25th anniversary. You guys have been doing something right for 25 years. >> Open source, that's what we do. (laughs) >> Open source. So talk to us, what's going on at Red Hat, what's new, what's exciting? >> I mean, OpenShift is, I mean, that's the big thing, right? I mean, so, just, this is a humbling time to be in the industry, like with this container wave and to see the industry adoption that we've had with OpenShift and, like, how all the technology in Red Hat's portfolio is just pushing and driving that along, it's, I don't know. It's exciting to me. >> No, it's very exciting. For us I think that cultural compatibility between CoreOS and Red Hat has been just fabulous to see. And then seeing how Red Hat provides a platform to really extend that and enhance that is just great, yeah. >> Culture is key. We talk about culture a lot when, at every event we talk about digital transformation, right? And culture is key to that, so maybe, Reza, give us a little bit of perspective, it's been five months now. How has CoreOS been embraced by the Red Hat guys and how are you now living in harmony? >> Right, well, first of all, CoreOS had, we always believed in open source. We were behind many open source projects in the containerized infrastructure space. And in that space, especially there on Kubernetes, we worked very closely with Red Hat. So, we knew each other really well. So as the teams got together, it was very easy for us to really get together and brainstorm towards what are the possibilities. And that's what we've been working on and, you know, the shovel has been hitting the ground for a while now and we're working on a conversion platform that brings Tectonic's technology to OpenShift. That's been very exciting as well as bringing the container Linux technology together with Red Hat, so. >> Some of those announcements happened at Red Hat summit a few weeks back or a month or so back. Can you talk about have there been any other updates? And also like, okay, maybe go one level deeper, so Tectonic was CoreOS', Kubernetes', I don't know, I don't wanna call it, would you call it a distribution? But a lot of autonomic and automation technologies for the operator built into Tectonic which was part of CoreOS' core DNA, now being brought into, kind of, the Red Hat platforms. So maybe you can talk a little bit about some of the stats, some of the recent developments. >> Yeah, so where we're at, it's kind of a phased implementation of bringing those technologies in, right? And so our next quarterly release, right, is gonna start, that's where, you know, we start bringing in some of the components, right? And then the one after that, you know, it's more on the operator side and then, you know, end of the year is when it's fully converged and so that's the path we're on, yeah. >> In terms of Kubernetes in general, Red Hat made a really early bet on Kubernetes and a big shift, a big pivot for its OpenShift platform. Kind of really embracing, throwing out a lot of the internals and embracing Kubernetes. Here at DockerCon, Kubernetes was a big topic, Docker's doing a lot of integration with Kubernetes, I kind of think that maybe that is, one size doesn't fit all but certainly Kubernetes is becoming accepted a lot more places. Can you talk a little bit about, you know, the implications of that, this phenomenon? >> Yeah. >> Yeah, well I think it's, there's a recognition that Kubernetes is now the defacto standard for orchestration, right? I think even if you go back a year ago, that was probably not quite there but now I think that that sense is there, and I think you're right, like, Red Hat embraced that three or four years ago and so did CoreOS and we both had to do a big shift, right? CoreOs was using fleets before that and we made a shift to Kubernetes. That has paid dividends, I think, because now we're really focusing on many of the concerns above and beyond just operating Kubernetes itself. It's what do you do above the stack and how do you operate everything above the stack, and that's where all the operator framework and everything we've been working on comes in. >> Yeah, I mean, it's basically how you get value in a more applied technology and a more application centered way. And so it's just been great to see the whole industry really rally around those standards and API's and everything and, you know, all the cloud platforms, everything, and so it's, you know, it's where the ecosystem is. >> Let's talk about collaboration. When you're talking with customers, you know, we've talked a lot today and at other events too, our enterprises are spending a lot of money, a lot of their IT budgets, on just keeping the lights on on mission-critical applications that they have to have but there's very little budget for innovation. Which is key to an organization being competitive, being relevant and being a leader. What are some of the customer conversations that you guys are having and what are some of the common barriers to container adoption that you're helping, with open to public customers, to eliminate? >> Yeah. >> I can take a shot at it. So, essentially, now on Kubernetes running stateless work goal at Kubernetes, is something that most people can do, right? Once you get to stateful work mode, that starts getting tricky and what we're seeing is that people who have now adopted Kubernetes for a year plus, they're starting to think, how do I run my stateful work on the databases, backend storage, in a, you know, scalable fashion on top of Kubernetes. And that's where we're coming in ans trying to help people, help the community, deliver that, really. Through creation of operators, through creation of reusable business logic that can do that across any Kubernetes department. >> Yip, I was just gonna add on to that, it's, like, as far just keeping the lights on and freeing up resources, right? When you look at all of the path and the deployment models on the net and new stuff, right, we're able to take away a serious amount of, like, operational overhead and just everything to where people can scale and just move way faster, right, and so there's a certain amount of that value that carries over to the traditional stuff, right, and so, you know, I think the biggest thing on the customer side is just, like, a mindset and culture change and getting, getting people to, like, change the way they look at the problem, right? And so, you know, those things and just understanding security, those are the big topics. >> Nice. I was at some Red Hat summit and one of the things that really impressed me there was this promise that, you know, we've all been trying to promise the end customer a time to value that you can actually do things faster, that you actually can innovate, was actually starting to be real in the sense that all of the customer examples were in terms of weeks or months and not years. And the Apple's app and the Apple's multi-cloud and all those other, and, so, can you talk a little about maybe some customers that are doing that or some examples of that, of both time to value and then the fact that a very few number of people were controlling very large infrastructures and I think you were just touching on that in terms of the operators and just all the automation, the day two sort of things. It seems like, I kind of think we've turned a corner in terms of productivity and time to value and real-life, real production workloads. >> Yeah, absolutely, and when you look at, like, where we see adoption, be it the financial sector, or, I mean, it's all over the place, it's really encouraging. And so at summit we had, I don't know, I think, like, 300, or 200 customer talks, it was insane. Going through the use cases and everything. Some of the big ones we're seeing from Amadeus, Optum and it was great. >> I saw an IDC report, I think on the Red Hat website, that showed that customers that adopt OpenShift can see a massive ROI, I wanna say it was, like, over 500% ROI within a 5 year period. >> Well, I think, part of, there's multiple factors to that, right? Part of it comes out of, just the sheer power of containerized infrastructure. Instead of deploying applications on a per compute basis and having to map them to single compute nose, you have the orchestrator that plays that perfect Tetris game with all of your applications. The other part comes a bit out of simplified operations, right? And that's where I think we're just at the beginning of the road. There is plenty more work to do on simplifying operations of Kubernetes and that's what I'm most excited about on this. >> Nice. Let's talk about the future. We are, I don't know, at an inflection point of this container technology, it's becoming more mature, people are in production, multi-cloud is certainly an aspect of what's going on, but I'd love for you to kind of explore a little bit more about some of the tooling. Like, I don't know if you need to get down into the OCI and the runtime level but, you know, what do we see the tooling doing? So, Kubernetes is there, you know, that level is there, but, like, what about, you know, builder and other things like that, like, what other pieces of tooling and automation are being developed to help, again, help developer productivity? >> Yeah, that's a good one, so I'll take a shot. So, it's a couple of things, so Kubernetes itself is plugable on, like, every tier, right, so it's finding that balance of seeing defaults and guidance of what works but then being flexible to work in customer environments so we can lock into, whether we're in, kind of, build strategy pipelines and, you know, whatever works for the customer and their, frankly, different teams, right? Because they all have different levels of maturity and stuff, so that's one thing, is just providing that level of flexibility. And the other thing is, you know, you said multi-cloud, just the way OpenShift provides that, like, common platform across anything, right, it just abstracts away any of the, you know, differences and whatever. >> Yeah, and we're seeing multi-cloud more and more with our customer base. And having a consistent model to deal with every one of them, including your non-prep environment, is becoming a bigger deal. >> In terms of, so on prep, maybe, actually I think it'd be useful. We've been talking about Kubernetes and OpenShift a lot but maybe let's step up a level and say, okay, OpenShift, how do you decide, so OpenShift has Kubernetes in it, but it's much more, it's a services platform built up off of, you know, rail on the bottom all the way up to, kind of, operators now. Can you talk a little bit about what else, what is some of the special sauce of OpenShift? >> Yeah, so, kind of what I was saying earlier about just, like, kind of every layer. So, we start, you know, like you said, rail, right, so the supported bulletproof kernel right up to the runtime, to the, literally the enterprise cube distribution is OpenShift. And then what we bring to it is this, like, amazing developer experience, right? And, like, the secret sauce of where it's going is all of the beauty from the CoreOS side on top of that. So, we've had the developer story, right, so, really, prescriptive onboarding of applications is the power because an empty cluster is useless, right, so you've gotta have that easy path to onboard. And then when we marry that with the day two stuff and all of the, you know, the deployment, and say, operators, everything, I mean, that's the, those pieces coming together is what differentiates it. >> From just up in the air of, kind of, Kubernetes. >> Right. >> Gets you part of the way but there's certainly a lot more. >> Yeah, it doesn't have any of the developer experience, the web console, the admin console, none of that stuff exists, right? >> The way I look at it is that the value add comes from two perspectives, right? One is from the system administrators and the infrastructural owners. That certainly comes to day two operations and how much to simplify that. How do you get a consistent interface across different environments? And how do you do things like accountability? Converging everything on to the same cluster, which is really what Kubernetes does, also changes the focus from a cost perspective, for example. From different application owners to a single owner. How do you make sure that, like, that owner is able to say, well, these are the people that are using it. We have services on top of Kubernetes, in OpenShift, that provide you that capability, for example. Through metering and charge back. Sometimes people call it metering and shame back. (laughing) And then from the point of view of developers, you know, there is multiple opinionated ways of simplifying developers life, right? And any given large enterprise has many, many ways of doing that and we wanna just be ready to address all of them and by the way, we have our own opinions and we have built that on top of OpenShift as well. >> So, you guys work a lot with developers. We have about five or six thousand people that are here at this event. I'm curious, when you go to open source events, including your own, are you finding that same mix of developers, IT professionals, enterprise architects and execs? And if so, what is that conversation like at that higher level where there might be, you know, checkbooks and keys to the kingdom and a business saying, hey, we have to iterate quickly. What is, kind of, the mix of conversations that you guys find in these communities? >> Yeah, it's the difference between the strategy, right, versus, like, bits, right? So, the admin, developer, we wanna focus, we wanna get in the weeds, right, and then the higher levels it's all about strategy, direction and enablement and those types of, you know, higher level concepts, right? So, I mean, that's, I don't know, my perspective. >> Are you learning that your conversations and maybe education of developers helps them then go up the chain within their organizations to explain, this is why we need to do this? >> I think there's some of that, right? The other thing I left off the lift though, is the cultural piece, because traditional enterprises, there's something here that they want to glean and take home in the culture space, right? And so that's a, you know, that's the other big one. >> I find that the conversation varies widely, right? So, when you talk to the infrastructure administrators and developers, you gotta be able to talk very technical and explain to them exactly how all this is working. And they're interested in the feature and technology. But when you talk to the CIO's out there, and the CTO's out there, really they're in interested in the outcome. And when you talk about the outcome it's easy just to show just what everybody wants to get to a pure DevOps model, everybody wants to get to a microservices model. This is kind of like going to the gym and seeing the of really fit people and then saying, well, yeah, but how do I get there, right? And this is where I think a company like Red Hat can come in and say, well, we'll work with you to get you there, right? So that's, that's important. >> Well the other one is just the value of being there and talking to your peers in the industry too, right? I mean, yeah, it's us, we're facilitating, but it's peers too, right? >> But you're right, culture, we talked about that, John, a number of times today, how critical culture is to being able to move past inertia. You know, we mentioned when I kicked off the segment that Red Hat is just celebrating its 25th birthday, so I imagine, I know you've been there, Ben, for 8 years, that there's been a lot of change there and a lot of cultural, kind of, mindset shift. Obviously, Reza, coming on in the last 5 months. Give us a little bit of an insight into the Red Hat culture that's helping to drive the agility that you need to also give your customers. >> Yeah, this is something our CEO talks about all the time, right? He wrote a book on it, The Open Organization, and, you know, just, like, lays out clear values of transparency, doing things very visually. We go through these exercises all the time just for changing our slogans and brands and these types of things, and the way where everybody participates and everybody takes ownership in it, right, and is part of it. And so that's one thing, I mean, we've been going through crazy growth. When I joined it was 3,000 people, now it's, like, 12,000 or so. I don't know the exact number but, and so how we scale that culture has been, it's been interesting, but it's been really successful. I mean, it's a big part of it. Open was a really clear message from summit, you know, basically in the cloud, open has won, right? Open innovation, open source, open culture. That's what's driving all the things we see now, I'd say. >> Yes. >> Well guys, thanks so much, Ben and Reza for stopping by theCUBE and sharing with us what's new at Red Hat and what excites you guys and we look forward to having you back on. >> Thanks so much for having us. >> Thank you. >> We wanna thank you guys for watching theCUBE. Lisa Martin with John Troyer, from DockerCon 2018. Stick around, we'll be right back with our next guest. (upbeat music)

from San Francisco it's the queue covering Red Hat summit 2018 brought to you by Red Hat hey welcome back everyone here live in San Francisco at Moscone West of cubes exclusive coverage of Red Hat summit 2018 I'm John four with mykos John Troy a founder of tech reckoning advisory and on community services firm our next guest is Jason O'Connell openshift platform owner of mark mcquarrie group welcome to the cubes let's get it right that's right well the retail bank of Macquarie so thank you and financial services thanks for coming on so bossy begging is pretty hot big time early adopter of all things tech yes and you doing a lot of work at kubernetes tell us about what you're doing take a minute to explain your job what your focus is some of the some of the environment DevOps things you're doing it's a basically I'm head of the container platform team at Macquarie Bank so basically my team manages open shifts on AWS we do the architecture on there but we also focus a lot on the value add on top so we don't just give our our customers for my team are the developers and the development teams we don't just give them a blank platform we do a lot of automation a lot of work on top of that basically because we want to make sure that the idea of a platform as a service is that we do as much as possible to make developers lives easy talk about the journey when did you start on this effort Asli Amazon's great cloud we use it as well other clouds are coming on you had Google and Microsoft and others but when did the open shift conversations start happening where were you what year was it how long have you been using it it's gone through some great changes I want to get your experience on that open shifter journey I mean somewhat of an early adopter I mean we started looking at this two years ago so that was openshift 3.1 a lot of the basic features weren't even there and it took us a year to both build it out as well as migrate about 40 applications to production so it was only a year ago that we've been in production so it's evolved like so rapidly during that time so 40 applications migrating right that enough in and of itself in a year is is a pretty heavy lift can you talk a little bit about are you just re platforming the applications obviously probably not rewriting at this point the open shift has been a good home for the applications that you started out with it sounds like I mean one of the reasons to choose open shift was docker and it was about that migration path I mean part of the migration was ensuring that developers could get everything running locally get these legacy systems we did a lot of micro services running locally on docker containers on their laptop then the migration was was easy from there but we deliberately didn't want to do like a lift and shift we wanted to rethink how we delivered software as part of this project okay what's the biggest challenges you had in doing this I mean as you can open ships got some great movement Houston Cooper native good bet and kubernetes is looking like a really awesome way to move workloads around and manage containers and clusters so you know what's what are some of the things we've learned what are some of the complexities that you overcame can you share a little bit about some of the specifics I think I think the newness is is probably the biggest challenge I mean going back to two years ago there was some very basic components that weren't there at the time and we knew were coming and even now there are pieces of work which we just don't tackle and we do a very quick fix because we know it's coming later I mean it's just moving and evolving so quickly you know we're waiting a lot for sto which is coming in the future so we're holding back on investing in certain areas because of that so it's always a constant challenge yeah I still looking good and the service mesh is hot as well how has OpenShift helped you but what's the list if you had to kind of boil it down what's the bin the the impact to you guys where's the where's that coming from I mean before we even selected OpenShift we had we're looking at our objectives from a business perspective not a technology perspective I'm the biggest objective we had was speed to delivery you know how could you get a business idea a product idea into production as fast as possible or even if you look at a minor fix to something something that should be easier develop it takes a data ride why does it take a month to release the production so speed of delivery was one of the key objectives and I can tell you more about how we we delivered that in detail but just going back to the objectives we also looked at developer experience you know sometimes the developers are not spending enough time coding and doing it they want they get bogged down in a lot of other pieces of work that I I'm really delivering business value yeah so again we wanted the platform to handle that for them they could focus more on their work this is the promise of DevOps and the whole idea of DevOps is to automate away the hassles and I mean my partner Dave a lot that calls a rock fetches no one likes to do all that work it's like can someone else just handle it and then when you got now automation that frees it up but this brings up the thing that I would love to get your reaction to because one things we've been covering and talking a lot about in the cube is this isn't happening around us it's not just what we're doing but this new modern way to deploy software you'll get like some of the big things that are happening in with cloud native and you mission is do is to do this awesome dynamic things on the fly that are automated away so it changes the how software is being built how are you guys embracing that what's the thought obviously you've got a team that's got the mindset of dev yeah I'll see embracing this vision and if everything else is probably substandard she'll you look at you know waterfall or any kind of non agile what is the your view of this modern era of writing code and building applications what I mean for people who don't aren't getting it how are you how do you explain it you know I think it's I mean it's an unbelievable time that we're in at the moment I mean the amount of automation that we're doing is huge and part of our openshift is that it's an automated bull platform so I've got a few junior guys in my team they're like two graduates and in turn they do a lot of the automation yeah it's that easy if you look at interestingly in like security and risk teams and governance teams where we're finding look they can improve security risk and all this by automating you know they're the one set and now we've got SEC offs movements and things like that so speed of production is is does not prohibit better security and in fact with Sec ups the amount of automation we do you got a far greater amount of security because we now know everything that's deployed we can continually scanning for vulnerabilities yeah so Jason you talked about it being new we've talked a little bit about culture how much of this has been a training exercise how much is that it's been a cultural shift within your organization as one of the leaders of it how are you approaching I mean we're lucky there within Macquarie Bank there was a large scale culture shift towards agile where the whole bank runs in that gel manner so that's helped us then fill in our technology and automation it complements that way of delivering so we've got some very unique ways where we've done automation and delivery which completely rethinks how we used to deliver before so right example yeah for instance now if you think why were people scared of delivering something into production why was a small change scary change and a big part of it is the blast radius if something went wrong you know connecting through to our API is we've got our own channels mobile apps a website you've got a lot of partners there are the companies connecting through as well and so even if you did a small change if it costs an issue everyone's affected at once so a big piece of what we did to deliver faster is allowed targeted releases you know I could target a release and a change just to you we could target it to a percentage of customers monitor rolled out quickly if there's a problem dial it up if it's looking good good target to any channel it seems like there's a business benefit to that too right that's massive here because you also can promise stability on certain channels if you want you can have faster channels that are moving quickly and in an API driven world we've got external companies connecting through to these api's you want to be able to say that we've given you a stable offering and you can upgrade when you want and then our channels we cannot move more fast so we've got a minister no-brainer I mean really the old way is completely dead because of that because I think what the blast radius you're pointing about blast radius the risk is massive so everyone's kind of on edge all these tests have to go in redundancies as if the planning is ridiculous all for the risk all that energy you're optimizing for a potential non-event or event here with micro services and you an out can go down to the granular level the granularity is really amazing so when you go forward first of all it's a recruiting opportunity to get better engineers wait this is a way we work I'm going forward I want you to comment on your opinion as an industry participant and can clarify this because a lot of people get confused here Automation they think jobs are going away administration is getting automated system admin type roles where junior people can now do more operating things but the operating roles not going away so talk about that that ops side because now the ops are more efficient the right things are audited maybe but talk about that dynamic between the right things being automated and the right things that are gonna roll to operational service messages or whatnot yeah I mean basically it's about getting people to do these higher-order functions so the people who are doing things manually and operating things manually you look at our Ops teams now morphing into like the classic SRE team you know the side reliability engineering teams where they're spending a significant amount of that time automating things you know looking at alerting and monitoring and then Auto healing I mean it's actually more work to automate everything but with a far greater amount of quality and reliability and what we get and the benefits are long it's worth it basically you do the work upfront and you reap the benefits and then variety away it's like writing rolling out software managing workloads talk about multi class here on Amazon multi cloud is a big focus to your hybrid cloud multi-cloud obviously we're seeing that trend how do you look at multi cloud as a practitioner what are some of the things that check our check boxes for you in terms of okay as we start looking to the next level there might be a multiple cloud scenario how do you think about that and how do you put that into perspective that's worth noting even two years ago and we selected openshift it was with the idea that we could go multi cloud you know that for the users for the developers they're not going to know the difference where we run it on so we're not locked into any provider final question for you if you can boil down openshift into kind of like a soundbite for you what does it mean to you guys what's been the benefit what's been it it's been that what's been the role what's the benefit of OpenShift as you pour the cloud journey you know I could say speed I could say automation I mean that's huge but but really open shift and read how to pick the winner which is docker and kubernetes and a colleague of mine is in coop con in Copenhagen last week he's constantly messaging me saying there's new tooling you guys can use this you can use that and it means that rather than us doing the work we're just getting tooling from the community so it's the de facto standards so that's that's probably the biggest benefit all the goodness is just coming right to your front door luckily and I got to do my homework every night playing around with this technology so yeah gates success story and again the great community open-source projects out there you guys can bring that in and productize it for the retail bank congratulations love open-source stories like this tier one citizen and again continues to power the world open source softens the cube do our part bring and use all the data from Red Hat summit 2018 I'm John fryer with John Tory we'll be back with more after this short break

(upbeat music) >> 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's coverage of OpenStack Summit 2018, here in Vancouver. Three days wall-to-wall coverage. I'm Stu Miniman with my cohost, John Troyer. Happy to welcome back to the program, Radhesh Balakrishnan, who is the general manager of OpenStack with Red Hat. Radhesh, great to see you. It's been a week since John talked to you, and always good to have you on at the show. >> Great to be on. Good to be here talking about OpenStack at OpenStack Summit. >> Yeah so, look, OpenStack is in the title of your job. I believe, did we have a birthday cake and a party celebrating a certain milestone? >> That is indeed true; so it's the fifth anniversary of that fact that we've had a product, Red Hat OpenStack Platform, on the market. And so, we've been doing a little bit of a look back at how far we have come in the last five years as well as looking ahead at, you know, how does the next three to five years shape as well. >> Yeah, Radhesh, I'm going to date myself and when I think back to, gosh it was 18 years ago, I was working with Linux, and there were kernels all over the place and things like that. And then, I worked for an enterprise storage company and was like, ugh, like keeping up with Chrome.org was a pain in the neck. There came out this thing called Red Hat Advanced Server that was like, oh wait, we can glom onto this, we can support this with our customers, and that eventually turned into RHEL, which, of course, kind of becomes the main standard for how to do Linux. I feel like we have a lot of similarities. >> Radhesh: Absolutely, absolutely. >> In how we did. RHOSP, I believe, is the acronym, so. >> That's exactly right, and we like to have long names. >> Which are very descriptive, but Red Hat OpenStack Platform, fundamentally, to your point brings the same valid proposition that RHEL brought to Linux, to OpenStack, with the twist that, it's not just curated OpenStack, but it's a co-engineered solution of Linux and Cavium and OpenStack. And along the way we learned that, look, it's not just OpenStack and the infrastructure solution. It's done in conjunction with the software-defined storage solution or it's done in conjunction with software-defined networking. Or, fast-forward all the way now, it's being done in conjunction with cloud-native applications running on top of it, right? But regardless, in five years we've been able to grow to address these different demands being placed at infrastructure level, and at the same time evolved to address new-use cases as well; Telco is an example of that. >> Radhesh, let's spend a couple of minutes, though, on the OpenStack Platform itself from Red Hat. Some of the things, guys, that you were bringing to market, I know we talked about, here at the show, fast-forward upgrades, for instance were, they were just introducing, and maybe some other things in the Queens release that you all are bringing forward and have engineered. >> Yeah, thanks for that question, very topical, in the sense that yesterday we launched OSP 13, which is the latest and greatest version based on Queens release. If you look at the innovation packed in that it fundamentally falls in three buckets. One is the bread part that you talked about, whereby, anybody who is standing on OSP 10, which was the prior, long-release lifecycle product, over to 13, how do you kind of get over there in a graceful manner is the first area that we have addressed. The second area is around security, because how do you make sure that OpenStack-based clouds are secure by default, from the day you roll out all the way to until you retire it, right? I don't know if there's going to be a retirement, but that's the intent of all the security enablements that we have in the product as well. And the third one, how do we make sure that containers in OpenStack can come together in a nice manner. >> Yeah, the container piece is something else that, so a lot of effort, here at the show. They announced Kata containers, which, trying to give the security of a VM, lightweight VM. How does Red Hat look at Kata containers? I know Red Hat, you know Linux's containers, you know, very strong position, fill us in on that. >> Yeah, to maybe pull back a little bit and then look at the larger picture of there is the notion of infrastructure or the open infrastructure that you need and OpenStack is a good starting point for that. And then, you overlay on top of that an application deployment management configuration, lifecycle management solution that's the container platform called OpenShift, right. These are the two centers of gravity for the stack. Now, aspects such as Kata containers or Hubbard, which is for again, similar concept of addressing how do you use virtualization in addition to containers to bring some of the value around security et cetera, right? So we are continuing to engage in all these upstream projects, but we'll be careful and methodical in bringing those technologies into our products as we go along. >> Okay, how about Edge is the other kind of major topic that we're having here, I know I've interviewed some Red Hat customers looking at NFV solutions, so some of the big telcos you know specifically that use various pieces. What do you hear from your customers and help us kind of draw that line between the NFV to the Edge. Yeah, so Edge has become the center is kind of the new joke in the sense that, from an NFV perspective, customers have already effectively addressed the CORD errors and the challenges, now it's about how do you scale that and deploy that on a massive scale, right? That's a good problem to have. Now the goodness of virtualization can be brought all the way down to the radio Edge so that a programmable network becomes the reality that a telco or a carrier can get into. So in that context, Edge becomes a series of use cases. You know, it's not just one destination. Another way to say it is there is Edge an objective and there is Edge as a noun. Edge as the objective is a set of technologies that are enabling Edge, Edge networking, right. Edge management, for example, and then Edge as a destination where you have a series of Edge locations starting from CORD error center going all the way to radio. Now, the technology answers for all these are just being figured out right now. So you can say, you know, put crudely, KBM, OpenStack, containers, and Ansible will be all good elements that will come into the picture when it comes to a solution for all these footprints. >> Nice. Radhesh, maybe let's switch over to talk about the summit here, and the people here, filled with people being productive with OpenStack, right? Either looking at it, upgrading it, inheriting it. We talked to people in a bunch of different scenarios Red Hat, huge installed base, and you are good at helping and supporting, and uplifting, and upskilling a set of operators who started with Linux and now have to be responsible for an entire cloud infrastructure. Plus, now, at this conference, we've been talking about containers, we've been talking about open dev, right. That's again broadening the scope of what an operator might have to deal with. How does Red Hat look at that? How are you and your team helping upskill and enhance the role of the operator? >> Yeah, so I think it comes down to, how do we make sure that we are understanding the journey that the operator himself or herself is taking from a career perspective, right, the skill set of evolving from Linux and core automation-related skills to going to being able to understand what does it mean to live with cloud implementation on a day-to-day basis. What does it mean to live with network function virtualization as the way in which new services are going to be deployed. So, our course curriculum has evolved to be able to address all these needs today. That's one dimension, the other dimension is how do we make sure that the product itself is so easy that the journey is getting to a point where the infrastructure is invisible, and the focus is on the application platform on top. So I think we have multiple areas of focus to get to the point where it's so relevant that it's invisible, if that paradox makes sense. That's what we're trying to make happen with OpenStack. >> Radhesh, Red Hat has a very large presence at the show here; we were noting in the keynote the underlying infrastructure didn't get a lot of discussion because it is more mature, and therefore, we can talk about everything like VGPUs and containers, and everything like that. But Red Hat has a lot in the portfolio that helps in some of those underlying pieces. So maybe you can give us some of the highlights there. >> Absolutely, so we aren't looking at OpenStack as the be-all end-all destination for customers, but rather an essential ingredient in the journey to a hybrid cloud. So when you have that lens it becomes natural to you that a portfolio of our offerings, which are either first-party or in conjunction with our partners --we have over 400 partners with whom we have joint solutions as well -- so you naturally take a holistic view and then say, "How do you optimize the experience of ceph plus OpenStack for example." So we were talking about Edge recently, right, in the context of Edge we realize that there is a particular use-case for hyperconverged infrastructure whereby you need to collocate, compute, and store it in a way that the footprint is so small and easy to manage plus you want to have one life-cycle both for OpenStack and ceph right, so to address that we announced, right at hypercloud infrastructure for cloud, as an offering that is co-engineered between ceph team, or our storage team, and the OpenStack team. Right, that's just an example of how, by bringing the rest of the portfolio, we're able to address needs being expressed by our customers today. Or you look forward in terms of use-case, one thing that we are hearing from all our large customers, such as the Amadeus's of the world is, make the experience of OpenShift on OpenStack, easy to deploy and manage, as well as reduce the penalty of running containers on VMs. Because we understand the benefits of security and all of that, but we want to be able to get that without having any penalty of using a virtual infrastructure so that's why we're heavily focused on OpenShift, on OpenStack, as the form-factor for delivering that while continuing to work on things such as Kata containers as well as, you know, Kuryrs, as technology is evolving to make communities much richer as well as the infrastructure management at OpenStack level richer. >> You brought up an interesting point, we spoke a little bit yesterday with John Allessio and Margaret Dawson, about really that kind of multi-cloud world out there, because pieces like Kubernetes and Ansible, aren't just in the data center with this one stack, it's spanning across multiple environments and when we talk to customers, they do cloud, and cloud is multiple things in multiple places and changing all the time. So I'd love to get your viewpoint on what you hear from customers, how Red Hat's helping them across all those environments. >> Absolutely, so the key differentiation we see in being able to provide to our customers is that unlike some of the other providers out there, they're where they are stitching you with a particular private cloud, with the particular public cloud, and then saying, "Hey, this is sort of the equivalent of the AOL walled gardens, if you will, right, that's being created for a particular private and public cloud. What we're saying is fundamentally three things. First is, the foundation of Linux skills from RHEL that you have is going to be what you can build on to innovate for today and tomorrow, that's number one. Secondly, you can invest in infrastructure that is 100% open using OpenStack so that you can use commodity hardware, bring in multiple use-cases which are bleeding it, such as data lags, big data, Apache Spark, or going all the way to cloud-native application, development on top of OpenStack. And then last but not least, when you are embarking on a multi-cloud journey it is important that you're not tied to innovation speed of one particular public cloud provider, or even a private cloud provider, for that matter, so being able to get to a container platform, which is OpenShift, that can run pretty much everywhere, either on PREM or on a public cloud, and give you that single pane of consistency for your application, which is where business and IT alignment is the focus right now, then I think you've got the best of all the worlds. You know, freedom from vendor-lock in, and a future-proof infrastructure and application platform that can take you to where you need to go, right. So pretty excited to be able to deliver on that consistently as of today, as well as in the coming years. >> All right, we just want to give you the final word, for people out there that ... you know, often they get their opinion based on when they first heard of something. OpenStack's been around for a number of years, five years now, with your platform. Give us the takeaway for 2018 here from OpenStack Summit as to how they should be thinking about OpenStack, in that larger picture. >> The key takeaway is that OpenStack is rock-solid, that you can bring into your environment, not just to power your virtual machine infrastructure, but also baremetal infrastructure on which you can bring in containers as well. So if you're thinking about an infrastructure fabric, either to power your telco network or to power your private cloud in its entirety OpenStack is the only place that you need to be looking at and our OpenStack platform from end to end delivers that value proposition. Now the second aspect to think about is, OpenStack is a step in the journey of a hybrid future destination that you can get to. Red Hat not only has the set of surround products and technologies to round-up the solution, but also have the largest partner ecosystem to offer you choice. So what's your excuse from getting to a hybrid cloud today if not tomorrow? >> Well, Radhesh Balakrishnan, thank you for all the updates appreciate catching up with you once again. For John Troyer, I'm Stu Minimam, getting near the end of three days wall-to-wall coverage here in Vancouver, thank you so much for watching theCUBE. (upbeat music)

(ambient Music) >> Announcer: 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, this is theCUBE's coverage of OpenStack Summit 2018 in Vancouver. I'm Stu Miniman, my cohost for the week is John Troyer, happy to welcome back to the program two CUBE alumni, we have Margaret Dawson and John Alessio. Margaret is the vice-president of Portfolio Product Marketing and John is the vice-president of Global Services. Thanks so much for joining us. >> Thank you. >> Thanks for having us. >> Good to be here. >> Alright so, John has gotten the week and a half now of the red hat greatness of being at summit last week, I unfortunately missed Summit, first time in five years I hadn't been at the show, did watch some of the interviews, caught up on it, and of course we talked to a lot of your team but, Margaret, let's start with you >> Margaret: Okay. >> One of the things we were looking at was, really, it's not just a maturation of OpenStack, but it's beyond where we were, how it fits into the greater picture, something we've been observing is when you think about open sourced projects, it's not one massive stack that you just deploy, it's you take what you need, it kind of gets embedded all over the place, and help us frame for us where we are today. >> Wow, that's a big question. So I think there's a couple things, I mean, in talking to customers, I think there's a couple trends that are happening. One is one you've probably talked about a lot and we probably covered at the Red Hat Summit which is just this overall digital transformation, digital leadership, whatever you want to call it, digital disruption tends to be a thing, and open sources definitely playing, really, the critical role of that, right, you will not be able to innovate and disrupt or even manage a disruption if you're not able to get to those technologies and innovations quickly and be able to adapt to it and have it work with other things. So the need for openness, for open APIs, for open technologies, inner-operability allows us to move faster and have that innovation and agility that every enterprise and organization needs world wide. And tied to that is kind of this overall hybrid cloud, so it's not just, OpenStack is a part of a much bigger kind of solution or goal that enterprises have in order to win and transform and be a digital leader. >> Margaret, I love that. Digital transformation, absolutely something we hear time and again from customers. >> Margaret: Yup. >> John, I've got a confession to make. I'm an infrastructure person and sometimes we're always like, why, come on, we spend all our time talking about how all the widgets and doo-dads and things-- >> Margaret: Blinky lights. >> Blinky lights, up on stage we have the-- >> He missed the blinking lights >> He did miss the blinking light. >> They had a similar stack up on stage yesterday. >> Oh, that's right. >> Same fans you could hear in the back of the room. But the whole goal of infrastructure always, of course, is to run the application, the whole reason for applications is to run and transform and do-- >> John: Serve the business >> Yeah, so that's where I'm going with this is we're talking more about not only that foundational layer of OpenStack but everything that goes with it and on it so maybe you could talk about the services-- >> Sure. So I think, Stu, that's exactly what we're seeing. So if you think about the last year and what we're seeing with services and projects here on OpenStack, I think the first thing to talk about is the fact that it's been growing quite a bit, in fact, from a 2017 versus 2018 perspective, our number of OpenStack projects have increased 36% year on year globally. So we're seeing a lot of demand, but we're seeing the projects be a lot more comprehensive. So these are OpenStack projects, but they're OpenStack with Open Shift, with Cloud Form, with Suff, as an example, and this combination is, really, a very very powerful combination. In fact, it's been so powerful that we started to see some common patterns of customers building a hybrid cloud solution, using OpenStack as their kind of private cloud infrastructure, but then using Open Shift as their way to kind of deploy applications in containers in that hybrid way, that we created a whole solution, which we announced two weeks ago, when John was at our Red Hat Summit, called Containers on Cloud. And that's taking all of our best practices around combining these products together in a very comprehensive, programmatic approach to deploying those solutions together. >> And I think it's really important, I mean, as you know, I think you and I met when we were both in networking, so coming from that infrastructure background but we really all need to talk about the workload down, starting with the application, starting with the business goal, and then how the infrastructure is almost becoming a services-based abstraction layer where you just need it to be always there. >> John: Yup. >> And whether it's public cloud or private cloud or traditional infrastructure, what developers in the business want is that agility and flexibility and containers provide that. There's other kind of architectural fabrics that allow that consistency and that's when it gets really exciting. >> One thing that's really interesting to me this week at OpenStack, as we've drilled into different customers, and talking to different people, even at lunch, is one, it's real. Everyone I've talked to, stuff in deployment, it went quickly, it's rock solid, it's powering, as we know, actually a lot of that is technical infrastructure that's powering a lot of the world's infrastructure at this point. >> That's right. >> The other thing that was interesting to me is some folks I talked to were saying, "Well, actually we have enough knowledge "that we're actually doing a lot of it ourselves, "we're going upstream." However, so that's great, and that's right for some people, but what I'm kind of been interested in both just coming from Red Hat Summit is both the portfolio, the breadth of the stack, and then all the different offerings that Red Hat, you know, it's not Rel anymore, it's not just Linux anymore, there's everything that's been built up and around and on top for orchestration and management, and then also the training, the services, the support, and that sort of thing, and I was wondering, that's kind of a two-part question, but maybe you all could tackle that. What does Red Hat bring to the table then? >> So, let me just start with, again, just to kind of position what we do as global services, our number one priority is customer success with Red Hat technology, that's the first and foremost thing we do and second is really around building expertise in the ecosystem so our customers have choice and where to go to get that expertise. So, if you start to look at kind of what's been going on as it relates to OpenStack, and, again, many customers are using Upstream bits, but many customers are using Red Hat bits, we see that and we look at the number of people who are getting trained around our technology. So over the last three years, we've trained, through our fee-based programs, 55,000 people on our OpenStack portfolio and in fact from 2017 to 2018 that was up 50% year on year and so the momentum is super super strong. So, that's the first point. The second is it's not just our customers. So part of my remit is, yes, to run consulting and, yes, to drive customer enablement and training, but it's also to build an ecosystem through our business partners. Our business partners use a program we call OPEN, Online Partner Enablement Network, which actually will just be celebrating five years just like OpenStack will, we'll be celebrating five years for OPEN. And our business partner accreditations on OpenStack specifically are up 49% year on year. So we're seeing the momentum in our regional systems integrators, our global systems integrators, our partners at large, building their solutions and capabilities around OpenStack, which I think is fantastic. >> No and it helps a lot with the verticalization of that, right, 'cause every industry has slightly different things they need. The thing I that would add to that, in terms of do-it-yourself community versus a dis-ter that's supported from someone like Red Hat, is it really comes down to core competency. And so even though OpenStack has become vastly simplified from a day one, day two, ongoing management, it is still a complex project. I mean that's the power of it, it can be highly customizable, right, it is an incredibly powerful infrastructure capability and so for most people their core competency is not that, and they need that support at least initially to get it going. What we have done is a couple things. I've actually talked to customers a lot about doing that training earlier and it's for a couple reasons, one is so that they actually have the people in house that have that competency but, two, you're giving infrastructure folks a chance to be part of that future cool stuff, right? I mean, OpenStack's written in Python and there's other languages that are newer and sexier, I guess, but it's still kind of moving them towards that future and for a lot of guys that have been in the data center and the ops world for a long time, they're looking out there at developers and going, I'm not the cool kid anymore, right? So OpenStack actually is a little bit of a window, not just to help companies go through that digital transformation, but actually help your ops personnel get a taste of that future and be part of that transformation instead of being stuck in just mainframe land or whatever, so training them early in the process is a really powerful way to do a lot of things. You know, skillset, retention, as well as then you can manage more of that yourself. >> And then all the way up to Stack, right? I mean, we're talking about containers, and then there's containers but then there's container data storage, container data networking. I mean, you've got the rest of the pieces in that, in Open Shift, in the rest. >> Absolutely. >> That is correct. >> And I think, John, you were at Red Hat Summit, we had a number of different innovation award winners. So I think one good example of kind of this kind of transformation from a digital transformation perspective, but also kind of leveraging a lot of what our Stack has to offer is Cafe Pacific. And so we talked about Cafe, they were one of our innovation award winners and what their challenge really was is how do they create a new modern infrastructure that gave them more flexibility so they could be more responsive to their customers. >> Yeah. >> In the airline industry. And so what they were really looking for was really, truly a hybrid cloud solution. They wanted to be able to have some things run in their infrastructure, have some things run in the public cloud, and we worked with them over the last, little over a year now, Red Hat consulting, Red Hat training, the Red Hat engineering team, in really building a solution that leverage OpenStack, yes, but also a number of other capabilities in the Red Hat portfolio, Open Shift, so they can deploy these applications, containerized applications now both to the public cloud as well as to the private cloud, but also automation through Ansible, which we're hearing a lot about Ansible and products like Ansible here at the conference-- >> Well the Open Stock and Ansible communities are starting to really work well together, just like Kubernetes, you've got a lot of this collaboration happening at the project level not to mention when we actually productize it and take it to customers. >> Yeah, so it's been super super powerful and I think it's a good one where it really hit on what Margaret was saying, which was giving the guys in infrastructure an opportunity to be a part of this huge transformation that Cafe went through, 'cause they were a very very key part of it. >> Yeah. Well, I think we're seeing that also with the open innovation labs. So this is something, which is really an innovation incubation process, it's agile, scrum, whatever, and in those we're not just talking to the developers, we're actually combining developers, functional lines of business leaders, infrastructure, architects, who all come together in a very typical six week kind of agile methodology and what comes out of that, I don't know, I've seen it a couple times, it's magical is all I can say, but having those different perspectives and having those different people work together to innovate is so powerful and they all feel like they're moving that forward and you come out with pilots, and we've seen things where they come out with two apps at the end of six weeks or eight weeks, it's just incredible when they're all focused on that and you start to understand those different perspectives and to me that's open source culture, right? It's awesome. >> And, Margaret, I'd love to hear your perspective also on that hybrid cloud discussion because so many people look at OpenStack and be like, oh, that's private cloud. >> Margaret: Right. >> And, of course, every customer we talk to, they have a cloud strategy. And they're doing lots of SaaS, they've got public cloud, multiple, Red Hat, I know you play across all of them, big announcement with Microsoft last week, last year was Amazon big partnerships with, so is Kubernetes the story, or is Kubernetes a piece of the story, how do all these play together for customers? >> I think Kubernetes is one and so, especially when you look at the broader architectural level, OpenStack becomes obviously the private cloud and enables them to start to do things that are more cloud-native even in their own data center, or if it's hosted or management or more traditional infrastructure, but it really has to be fluid. And a lot of customers initially were saying that their strategy was cloud first, and they would say, "Oh, we're going to put "everything in the public cloud." And then you actually start going through the workloads, you start going through the cost, you start going through the data privacy, or whatever the criteria capabilities are, and that's just not practical, frankly. And so this hybrid reality with private cloud, traditional, and public is going to be the reality for a very very long time, if not forever. There's always going to be things that you want to have better control of. And so Kubernetes at the orchestration layer becomes really critical to be able to have that agility across all those environments, but you have other fabrics like that in your architecture too, we talked about Ansible, it allows you to have common automation and do those play books that you can use across all those different infrastructure, KVM, what's your virtualization fabric, and can KVM take you from traditional virtualization all through public cloud? The answer is yes. So we're going to see increasingly these kind of layers of the overall architecture that allows you to have that flexibility, that management that's still the consistency, which is what you need to keep your policies the same, your access controls, you security, your compliance, and your sanity, whereas before it was kind of Ad Hoc. People would be like, oh, we're just going to put this here, go to public cloud. We're going to do this here, and now people are finding standardizing on things like even Red Hat Enterprise Linux, that's my OS layer, and that allows me to easily do Linux containers in a secure way, et cetera, et cetera. So, doing hybrid cloud means both the agility but you got to have some consistency in order to have the security and control that you need. So it's a little bit different than what we were talking about a few years ago, even. >> And I think one of the things that we've learned in the services world is that we started this idea about 18 months ago, we called these journey adoption programs, which were really the fact that some of these transformations are big, they're not about a single project that's going to last four to six weeks, it's a journey that the customer's going to go on and so when we talk about hybrid cloud, we've actually created this adoption program which can really start with the customer in this whole discovery phase, really, what are you trying to accomplish from a business perspective then take them into a design phase, take them into a deployment phase, take them into an enablement phase, and then take them into a sustainment phase. And there's a number of different services that we'll do across consulting, training, even within Marco Bill Peters Organization, which is our customer experience and engagement organization, around what role a technical account manager can play and really help our customer in the operational phases. And so we've learned this from some of the very large deployments, like Verizon, where we've seen some very-- >> And it's cyclical, right? You can do that many times. >> We do. In fact, you absolutely do. And so we've created now a program, specifically, around hybrid clouded option to try and de-mistify it. >> Yeah. >> Because it is complex. >> Well, and the reality is, there's somewhere around 30% of organizations still do not actually have a clear cloud strategy. And we see that in our own research, our own experiences, but industry analysts come up with the exact same number. >> And Margaret, by the way, the other 70%, the ink still pretty-- >> Yeah. >> Still wet! (laughing) >> Yes, it is. I'll tell you, I love saying cloud first to people because they kind of giggle. It's like, yeah, that's our strategy but we know we don't really know what that means. >> Which cloud? >> Exactly. >> Exactly. >> All the clouds. >> Exactly. >> Alright, well Margaret and John, want to give you a final word, key takeaways you want to have or anything new to the show that you want to point out? >> I would just say we are still in early days. I think sometimes we forget that we, both in the open source communities, in the industry for a long time, tend to be 10 years ahead of where most people are and so when you hear jokes about, oh, is OpenStack still viable or is everything doing this, it's like right now we only have a very small percentage of actual enterprise workloads in the cloud and so we need to just now get to the point where we're all getting mature in this and really start to help our customers and our partners and our communities take this to the next level and work on inter-operability, and ease of use, and management. We're so mature now in technology, now let's put the polish on it, so that the consumption and the utilization can really go to the next level. >> Yeah, and I'll play off what Margaret said. I think it's very very key. When I look at where we've had the biggest success, as defined by, in that discovery phase, the customer lays out for us, here's what our business objectives were, did we achieve those business objectives, it's all about figuring out how we can create the solution and integrate into their environment today. So Margaret said I think very very well which is we have to integrate into these other solutions and every one of these big customer deployments has some Red Hat software, but it also has some other software that we're integrating into because customers have investments. So it's not about rip and replace, it's about integrate, it's about leverage, it's about time to market, and that's what most of the customers I've talked to, they're very worried about time to value, and so that's what we're trying to focus in, I think as a whole company, around Red Hat. >> Margaret: Agree. >> Absolutely. Summed it up very well. John Alessio, Margaret Dawson, thanks so much for joining us again. >> Thanks again. >> For John Troyer, I'm Stu Miniman, watch more coverage here from OpenStack Summit 2018 in Vancouver. Thanks for watching theCUBE.

(upbeat electronic music) >> Announcer: Live from San Francisco, it's theCUBE. Covering Red Hat Summit 2018. Brought to you by Red Hat. >> Hey, welcome back, everyone. This is theCUBE, we're live in San Francisco, California, here at Moscone West, Red Hat Summit 2018. I'm John Furrier, the co-host of theCUBE. We've got three great guests, exciting segment. Really looking at the future of computer programming, the youth in our generation, the young minds, and the award winners here at Red Hat Summit. Our three guests are Leigh Day, Vice Present of Marketing and Communications at Red Hat. Ellie Galloway with Jewelbots, and Sara Chipps, CTO at Jewelbots Thanks for spending the time and coming on. I really appreciate it. Love this story because I always, as a computer person, I always love getting nerdy, but now nerd is the new cool. So starting young and coding is not just for guys anymore, it's for everybody. So congratulations on your success. Take a minute to explain what's happened here, because the folks watching don't know what happened yesterday. You guys were featured at part of Open Source Stars. Leigh, talk about the story. >> So about three years ago, the Red Hat Marketing Communications Group decided that they needed a passion project, something that would make them feel more energized about coming to work and not just selling products, but telling genuine stories about people. We started our Open Source Stories films series, and that has turned into Open Source Stories Live as well. So yesterday we brought awesome stories, like Jewelbots to our stage to tell the story of children and others getting involved in coding. And Ellie and Femmie on our stage, talking about how people should code for good and we really love that message and applaud that. >> And coding is so social because it's fun. So talk about Jewelbots and what's happening here? So how did this get started? And then I'll go into some specific questions for the young future star here. (laughter) Sara, how did it all get started? >> Yeah, so Jewelbots got started out of a desire to make a product for young girls, to get them excited about coding. So we talked to about 200 girls and we asked them what was interesting to them, and over and over from them we heard that their friendships are really important to them. And so when we were talking to them about a bracelet that lights up when your friends are nearby and you can use it to send secret messages, they got really excited. And so that's what we built and we made it open source so they would code it as well. >> How did it all get started? What was the motivation, what motivated you to take on this project? >> Good question. So I've been a software developer for seventeen years, I was five years into my career before I worked with another woman and it was another five years after that, before I worked with another one. So I really, you know, I love this career and I wanted to figure out a way to get more women excited about doing it. So, talking to my male peers, I heard from them that they started about middle school age, and so I wanted to find something for girls that would also inspire them in that way. >> That's awesome, thank you so much for doing that. I love the story, it's super important. Now, how did you get involved? You just loved programming? You wake up one day and say, hey, I love programming? How did you get involved? >> Well first, me and my dad, my dad works for Microsoft, he helped me code a game in Unity and so I love coding games so much that later he showed me Minecraft min code. And so I got involved in that, by then I kind of knew how to code and everything, so I only asked my dad for help if I absolutely needed it. And then, since my dad new Sara Chipps from Microsoft, he showed me Jewelbot one day when I got home from school and I've been on my own programming since then. >> John: You having fun? >> I am. >> What's the favorite thing about coding that you like? >> I love solving problems, and so solving problems is probably my favorite part in coding. I solve a lot of problems and inventions, tiny ones and just kind of figuring things out. >> Did you get all your friends involved? Did you spread it around to your friend group? >> I am getting some friends involved. In my YouTube channel I have someone I shared Jewel a lot with and showed how to code, and yeah. And at school, at my next school, I am going to create a Jewelbots club, and I'm hoping I can get a lot of people to join. >> So is it fun, is Jewelbot fun? I mean, how does it work, how does he Jewelbot work? So I wear a bracelet and then it lights up? So how does the code work? Is it an io sensor in the front end? How does it work? >> It works by Bluetooth. Do you mean friendship coding mode, or? >> Friendship coding mode. >> Okay, friendship coding mode. Yeah, you use Bluetooth for friendship coding mode. You pair Jewelbots together and it's pretty simple. You don't need a program, you can start right away without any program and it already has a default on it, so yeah. >> Do you have an agreement with Snapchat yet? Because that would be a great geofence feature, if I had like a Jewelbot with Snapchat integration. >> You can communicate by vibrates but there's not a Snapchat picture. >> Not yet, we'll make sure that we get that back and I'll get my daughter involved to jump in. How about the community aspect? I love the story, because what it does, it makes it fun. You don't want coding to be like eating spinach or, you know, taking out the trash or sweeping, you know, the floor up, you want to make it fun. Kids want to make it fun and gaming is key. When did it start clicking with you, Sara? You know, when did it start getting momentum? >> Yeah, well I think one thing that we realized, is that coding doesn't have to be a lonely activity, it doesn't have to be just one person sitting in a basement coding, it could be really anyone, and it's such a social thing, you know? All coders are self-taught and we all learn from each other, so having the ability to have a community that you can reach out to that are excited to help you and that kind of thing was a really important part of what we were building. >> So you guys were on stage... So tell about what happened here, 'cause folks didn't get to see and they can see it online after on a replay, you guys are out on stage, did you do like a demo? Tell us what happened on stage. >> We had a whole afternoon session that was focused on showcasing collaboration, young people coding, STEM. We had a group from our co-op, alumni come to the stage and talk about their experiences with Co.Lab, programming Raspberry Pis to take pictures. These are middle school girls, we've done programs with them all over the east coast. Then we had our CMO talk about his open-source experience. We had Women Open Source Awards, and then Sara and Ellie came out and told the audience about Jewelbots and it was just an opportunity to shine a light on their awesome project and to showcase young women doing great things. And showing women that they should have the confidence to code alongside men. >> Yeah, great program, how does someone get involved? How can someone get involved with Red Hat's Open Stories and your communities with Jewelbots. What can you guys share? Is there locations or a web app? Is there something you can get involved in? How does someone get involved? >> Well, Red Hat, we have seven Open Source Stories films, that people can go online and watch. But then yet, there's 90 of them for an open-source story, OpenSourceStories@RedHat.com is a way to contribute to that. But we're always thinking about new ideas, taking contributions and love to hear about these stories. >> Sara, how do I get involved in the Jewelbots? For anyone else watching who might be inspired by this awesomeness you guys have going on here. Great practice, I love how you're doing this. How do they get involved with what you're doing? >> So, if you have young girls in your life Jewelbots.com, Amazon.com, Target.com is all where you can get Jewelbots. If you don't and you know some people that do, a lot of people have started hosting events around Jewelbots, so if people in your office might have daughters and they might be interested in something like that, that's something that we help people do, as well. >> That's great. Ellie, what's your thoughts on all this? This celebrity status you have? Your YouTube followers are going to go through the roof now. >> Yeah, since yesterday I've had over 75 new followers. >> John: Wow. >> So yeah, it's amazing. >> Can she say the name of her YouTube channel? >> Of course. >> EllieGJewelbots. >> EllieGJewelbots, we're going to promote it, make sure it's on the screen, guys, great program. I'm so excited for you, that's amazing, don't stop. It gets better, more fun every time. When you build cool stuff it's magical. And tell all your friends. Great stuff, thanks so much for doing this. Great program, thanks for coming on. >> Thanks for having us. >> Thanks for having us. It's theCUBE, live here. A really inspirational inspirational moment here, getting everyone started at the young age really kind of opens the aperture of all people, all diversity, inclusion and diversity, really critical part of the community paying it forward. Of course, theCUBE's doing our part here, be back with more live coverage after this short break. (upbeat electronic music)