>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America 2020 Virtual brought to you by Red Hat The Cloud, Native Computing Foundation and Ecosystem Partners. Hello, everyone. And welcome back to the cubes Ongoing coverage of Cuba con North America. Joe Fernandez is here. He's with Stephanie, Cheras and Joe's, the V, P and GM for core cloud platforms. That red hat and Stephanie is this s VP and GM of the Red Hat Enterprise. Lennox bu. Two great friends of the Cube. Awesome seeing you guys. How you doing? >>It's great to be here, Dave. Yeah, thanks >>for the opportunity. >>Hey, so we all talked, you know, recently, uh, answerable fest Seems like a while ago, but But we talked about what's new? Red hat really coming at it from an automation perspective. But I wonder if we could take a view from open shift and what's new from the standpoint of you really focus on helping customers, you know, change their operations and operationalize. And Stephanie, Maybe you could start, and then, you know, Joe, you could bring in some added color. >>No, that's great. And I think you know one of the things we try and do it. Red hat clearly building off of open source. We have been focused on this open hybrid cloud strategy for, you know, really years. Now the beauty of it is that hybrid cloud and open hybrid cloud continues to evolve right with bringing in things like speed and stability and scale and now adding in other footprints, like manage services as well as edge and pulling that all together across the whole red hat portfolio from the platforms, right? Certainly with Lennox and roll into open shift in the platform with open shift and then adding automation, which certainly you need for scale. But it's ah, it's continues to evolve as the as the definition of open hybrid cloud evolves. >>Great. So thank you, Stephanie jokes. You guys got hard news here that you could maybe talk about 46? >>Yeah. Eso eso open shift is our enterprise kubernetes platform. With this announcement, we announced the release of open ship 4.6 Eso eso We're doing releases every quarter tracking the upstream kubernetes release cycle. So this brings communities 1.19, which is, um but itself brings a number of new innovations, some specific things to call out. We have this new automated installer for open shift on bare metal, and that's definitely a trend that we're seeing is more customers not only looking at containers but looking at running containers directly on bare metal environments. Open shift provides an abstraction, you know, which combines Cuban. And he's, uh, on top of Lennox with RL. I really across all environments, from bare metal to virtualization platforms to the various public clouds and out to the edge. But we're seeing a lot of interest in bare metal. This is basically increasing the really three automation to install seamlessly and manage upgrades in those environments. We're also seeing a number of other enhancements open shifts service mesh, which is our SDO based solution for managing, uh, the interactions between micro services being able to manage traffic against those services. Being able to do tracing. We have a new release of that on open shift Ford out six on then, um, some work specific to the public cloud that we started extending into the government clouds. So we already supported AWS and Azure. With this release, we added support for the A W s government cloud as well. Azaz Acela's Microsoft Azure government on dso again This is really important to like our public sector customers who are looking to move to the public cloud leveraging open shift as an abstraction but wanted thio support it on the specialized clouds that they need to use with azure gonna meet us Cup. >>So, joke, we stay there for a minute. So so bare metal talking performance there because, you know, you know what? You really want to run fast, right? So that's the attractiveness there. And then the point about SDO in the open, open shift service measure that makes things simpler. Maybe talk a little bit about sort of business impact and what customers should expect to get out of >>these two things. So So let me take them one at a time, right? So so running on bare metal certainly performances a consideration. You know, I think a lot of fixed today are still running containers, and Cuban is on top of some form of virtualization. Either a platform like this fear or open stack, or maybe VMS in the in one of the public clouds. But, you know containers don't depend on a virtualization layer. Containers only depend on Lennox and Lennox runs great on bare metal. So as we see customers moving more towards performance and Leighton see sensitive workloads, they want to get that Barry mental performance on running open shift on bare metal and their containerized applications on that, uh, platform certainly gives them that advantage. Others just want to reduce the cost right. They want to reduce their VM sprawl, the infrastructure and operational cost of managing avert layer beneath their careers clusters. And that's another benefit. So we see a lot of uptake in open shift on bare metal on the service match side. This is really about You know how we see applications evolving, right? Uh, customers are moving more towards these distributed architectures, taking, you know, formally monolithic or enter applications and splitting them out into ah, lots of different services. The challenge there becomes. Then how do you manage all those connections? Right, Because something that was a single stack is now comprised of tens or hundreds of services on DSO. You wanna be able to manage traffic to those services, so if the service goes down, you can redirect that those requests thio to an alternative or fail over service. Also tracing. If you're looking at performance issues, you need to know where in your architecture, er you're having those degradations and so forth. And, you know, those are some of the challenges that people can sort of overcome or get help with by using service mash, which is powered by SDO. >>And then I'm sorry, Stephanie ever get to in a minute. But which is 11 follow up on that Joe is so the rial differentiation between what you bring in what I can just if I'm in a mono cloud, for instance is you're gonna you're gonna bring this across clouds. I'm gonna You're gonna bring it on, Prem And we're gonna talk about the edge in in a minute. Is that right? From a differentiation standpoint, >>Yeah, that That's one of the key >>differentiations. You know, Read has been talking about the hybrid cloud for a long time. We've we've been articulating are open hybrid cloud strategy, Andi, >>even if that's >>not a strategy that you may be thinking about, it is ultimately where folks end up right, because all of our enterprise customers still have applications running in the data center. But they're also all starting to move applications out to the public cloud. As they expand their usage of public cloud, you start seeing them adopted multi cloud strategies because they don't want to put all their eggs in one basket. And then for certain classes of applications, they need to move those applications closer to the data. And and so you start to see EJ becoming part of that hybrid cloud picture on DSO. What we do is basically provide a consistency across all those environments, right? We want run great on Amazon, but also great on Azure on Google on bare metal in the data center during medal out at the edge on top of your favorite virtualization platform. And yeah, that that consistency to take a set of applications and run them the same way across all those environments. That is just one of the key benefits of going with red hat as your provider for open hybrid cloud solutions. >>All right, thank you. Stephanie would come back to you here, so I mean, we talk about rail a lot because your business unit that you manage, but we're starting to see red hats edge strategy unfolded. Kind of real is really the linchpin I wanna You could talk about how you're thinking about the edge and and particularly interested in how you're handling scale and why you feel like you're in a good position toe handle that massive scale on the requirements of the edge and versus hey, we need a new OS for the edge. >>Yeah, I think. And Joe did a great job of said and up it does come back to our view around this open hybrid cloud story has always been about consistency. It's about that language that you speak, no matter where you want to run your applications in between rela on on my side and Joe with open shift and and of course, you know we run the same Lennox underneath. So real core os is part of open shift that consistently see leads to a lot of flexibility, whether it's through a broad ecosystem or it's across footprints. And so now is we have been talking with customers about how they want to move their applications closer to data, you know, further out and away from their data center. So some of it is about distributing your data center, getting that compute closer to the data or closer to your customers. It drives, drives some different requirements right around. How you do updates, how you do over the air updates. And so we have been working in typical red hat fashion, right? We've been looking at what's being done in the upstream. So in the fedora upstream community, there is a lot of working that has been done in what's called the I. O. T Special Interest group. They have been really investigating what the requirements are for this use case and edge. So now we're really pleased in, um, in our most recent release of really aid relate 00.3. We have put in some key capabilities that we're seeing being driven by these edge use cases. So things like How do you do quick image generation? And that's important because, as you distribute, want that consistency created tailored image, be able to deploy that in a consistent way, allow that to address scale, meet security requirements that you may have also right updates become very important when you start to spread this out. So we put in things in order to allow remote device mirroring so that you can put code into production and then you can schedule it on those remote devices toe happen with the minimal disruption. Things like things like we all know now, right with all this virtual stuff, we often run into things like not ideal bandwidth and sometimes intermittent connectivity with all of those devices out there. So we put in, um, capabilities around, being able to use something called rpm Austria, Um, in order to be able to deliver efficient over the air updates. And then, of course, you got to do intelligent rollbacks for per chance that something goes wrong. How do you come back to a previous state? So it's all about being able to deploy at scale in a distributed way, be ready for that use case and have some predictability and consistency. And again, that's what we build our platforms for. It's all about predictability and consistency, and that gives you flexibility to add your innovation on top. >>I'm glad you mentioned intelligent rollbacks I learned a long time ago. You always ask the question. What happens when something goes wrong? You learn a lot from the answer to that, but You know, we talk a lot about cloud native. Sounds like you're adapting well to become edge native. >>Yeah. I mean, I mean, we're finding whether it's inthe e verticals, right in the very specific use cases or whether it's in sort of an enterprise edge use case. Having consistency brings a ton of flexibility. It was funny, one of our talking with a customer not too long ago. And they said, you know, agility is the new version of efficiency. So it's that having that sort of language be spoken everywhere from your core data center all the way out to the edge that allows you a lot of flexibility going forward. >>So what if you could talk? I mentioned just mentioned Cloud Native. I mean, I think people sometimes just underestimate the effort. It takes tow, make all this stuff run in all the different clouds the engineering efforts required. And I'm wondering what kind of engineering you do with if any with the cloud providers and and, of course, the balance of the ecosystem. But But maybe you could describe that a little bit. >>Yeah, so? So Red Hat works closely with all the major cloud providers you know, whether that's Amazon, Azure, Google or IBM Cloud. Obviously, Andi, we're you know, we're very keen on sort of making sure that we're providing the best environment to run enterprise applications across all those environments, whether you're running it directly just with Lennox on Ralph or whether you're running it in a containerized environment with Open Chef, which which includes route eso eso, our partnership includes work we do upstream, for example. You know, Red Hat help. Google launched the Cuban community, and I've been, you know, with Google. You know, we've been the top two contributors driving that product that project since inception, um, but then also extends into sort of our hosted services. So we run a jointly developed and jointly managed service called the Azure Red Hat Open Shift Service. Together with Microsoft were our joint customers can get access to open shift in an azure environment as a native azure service, meaning it's, you know, it's fully integrated, just like any other. As your service you can tied into as you're building and so forth. It's sold by by Azure Microsoft's sales reps. Um, but you know, we get the benefit of working together with our Microsoft counterparts and developing that service in managing that service and then in supporting our joint customers. We over the summer announced sort of a similar partnership with Amazon and we'll be launching are already doing pilots on the Amazon Red Hat Open ship service, which is which is, you know, the same concept now applied to the AWS cloud. So that will be coming out g a later this year, right? But again, whether it's working upstream or whether it's, you know, partnering on managed services. I know Stephanie team also do a lot of work with Microsoft, for example, on sequel server on Lenox dot net on Lenox. Whoever thought be running that applications on Linux. But that's, you know, a couple of years old now, a few years old, So eso again. It's been a great partnership, not just with Microsoft, but with all the cloud providers. >>So I think you just shared a little little He showed a little leg there, Joe, what's what's coming g A. Later this year. I want to circle back to >>that. Yeah, eso we way announced a preview earlier this year of of the Amazon Red Hat Open ships service. It's not generally available yet. We're you know, we're taking customers. We want toe, sort of be early access, get access to pilots and then that'll be generally available later this year. Although Red Hat does manage our own service Open ship dedicated that's available on AWS today. But that's a service that's, you know, solely, uh, operated by Red Hat. This new service will be jointly operated by Red Hat and Amazon together Idea. That would be sort of a service that we are delivering together as partners >>as a managed service and and okay, so that's in beta now. I presume if it's gonna be g a little, it's >>like, Yeah, that's yeah, >>that's probably running on bare metal. I would imagine that >>one is running >>on E. C. Two. That's running an A W C C T V exactly, and >>run again. You know, all of our all of >>our I mean, we you know, that open shift does offer bare metal cloud, and we do you know, we do have customers who can take the open shift software and deploy it there right now are managed. Offering is running on top of the C two and on top of Azure VM. But again, this is this is appealing to customers who, you know, like what we bring in terms of an enterprise kubernetes platform, but don't wanna, you know, operated themselves, right? So it's a fully managed service. You just come and build and deploy your APS, and then we manage all of the infrastructure and all the underlying platform for you >>that's going to explode. My prediction. Um, let's take an example of heart example of security. And I'm interested in how you guys ensure a consistent, you know, security experience across all these locations on Prem Cloud. Multiple clouds, the edge. Maybe you could talk about that. And Stephanie, I'm sure you have a perspective on this is Well, from the standpoint of of Ralph. So who wants to start? >>Yeah, Maybe I could start from the bottom and then I'll pass it over to Joe to talk a bit. I think one of these aspects about security it's clearly top of mind of all customers. Um, it does start with the very bottom and base selection in your OS. We continue to drive SC Lennox capabilities into rural to provide that foundational layer. And then as we run real core OS and open shift, we bring over that s C Lennox capability as well. Um, but, you know, there's a whole lot of ways to tackle this we've done. We've done a lot around our policies around, um see ve updates, etcetera around rail to make sure that we are continuing to provide on DCA mitt too. Mitigating all critical and importance, providing better transparency toe how we assess those CVS. So security is certainly top of mind for us. And then as we move forward, right there's also and joke and talk about the security work we do is also capabilities to do that in container ization. But you know, we we work. We work all the way from the base to doing things like these images in these easy to build images, which are tailored so you can make them smaller, less surface area for security. Security is one of those things. That's a lifestyle, right? You gotta look at it from all the way the base in the operating system, with things like sc Lennox toe how you build your images, which now we've added new capabilities. There And then, of course, in containers. There's, um there's a whole focus in the open shift area around container container security, >>Joe. Anything you want to add to that? >>Yeah, sure. I >>mean, I think, you know, obviously, Lennox is the foundation for, you know, for all public clouds. It's it's driving enterprise applications in the data center, part of keeping those applications. Security is keeping them up to date And, you know, through, you know, through real, we provide, you know, securing up to date foundation as a Stephanie mentioned as you move into open shift, you're also been able to take advantage of, uh, Thio to take advantage of essentially mutability. Right? So now the application that you're deploying isn't immutable unit that you build once as a container image, and then you deploy that out all your various environments. When you have to do an update, you don't go and update all those environments. You build a new image that includes those updates, and then you deploy those images out rolling fashion and, as you mentioned that you could go back if there's issues. So the idea, the notion of immutable application deployments has a lot to do with security, and it's enabled by containers. And then, obviously you have cured Panetti's and, you know, and all the rest of our capabilities as part of open Shift managing that for you. We've extended that concept to the entire platform. So Stephanie mentioned, real core West Open shift has always run on real. What we have done in open shift for is we've taken an immutable version of Ralph. So it's the same red hat enterprise Lennox that we've had for years. But now, in this latest version relate, we have a new way to package and deploy it as a relic or OS image, and then that becomes part of the platform. So when customers want toe in addition to keeping their applications up to date, they need to keep their platform up to dates. Need to keep, you know, up with the latest kubernetes patches up with the latest Lennox packages. What we're doing is delivering that as one platform, so when you get updates for open shift, they could include updates for kubernetes. They could include updates for Lennox itself as well as all the integrated services and again, all of this is just you know this is how you keep your applications secure. Is making sure your you know, taking care of that hygiene of, you know, managing your vulnerabilities, keeping everything patched in up to date and ultimately ensuring security for your application and users. >>I know I'm going a little bit over, but I have I have one question that I wanna ask you guys and a broad question about maybe a trends you see in the business. I mean, you look at what we talk a lot about cloud native, and you look at kubernetes and the interest in kubernetes off the charts. It's an area that has a lot of spending momentum. People are putting resource is behind it. But you know, really, to build these sort of modern applications, it's considered state of the art on. Do you see a lot of people trying to really bring that modern approach toe any cloud we've been talking about? EJ. You wanna bring it also on Prem And people generally associate this notion of cloud native with this kind of elite developers, right? But you're bringing it to the masses and there's 20 million plus software developers out there, and most you know, with all due respect that you know they may not be the the the elites of the elite. So how are you seeing this evolve in terms of re Skilling people to be able, handle and take advantage of all this? You know, cool new stuff that's coming out. >>Yeah, I can start, you know, open shift. Our focus from the beginning has been bringing kubernetes to the enterprise. So we think of open shift as the dominant enterprise kubernetes platform enterprises come in all shapes and sizes and and skill sets. As you mentioned, they have unique requirements in terms of how they need toe run stuff in their data center and then also bring that to production, whether it's in the data center across the public clouds eso So part of it is, you know, making sure that the technology meets the requirements and then part of it is working. The people process and and culture thio make them help them understand what it means to sort of take advantage of container ization and cloud native platforms and communities. Of course, this is nothing new to red hat, right? This is what we did 20 years ago when we first brought Lennox to the Enterprise with well, right on. In essence, Carozza is basically distributed. Lennox right Kubernetes builds on Lennox and brings it out to your cluster to your distributed systems on across the hybrid cloud. So So nothing new for Red Hat. But a lot of the same challenges apply to this new cloud native world. >>Awesome. Stephanie, we'll give you the last word, >>all right? And I think just a touch on what Joe talked about it. And Joe and I worked really closely on this, right? The ability to run containers right is someone launches down this because it is magical. What could be done with deploying applications? Using a container technology, we built the capabilities and the tools directly into rural in order to be able to build and deploy, leveraging things like pod man directly into rural. And that's exactly so, folks. Everyone who has a real subscription today can start on their container journey, start to build and deploy that, and then we work to help those skills then be transferrable as you movinto open shift in kubernetes and orchestration. So, you know, we work very closely to make sure that the skills building can be done directly on rail and then transfer into open shift. Because, as Joe said, at the end of the day, it's just a different way to deploy. Lennox, >>You guys are doing some good work. Keep it up. And thanks so much for coming back in. The Cube is great to talk to you today. >>Good to see you, Dave. >>Yes, Thank you. >>All right. Thank you for watching everybody. The cubes coverage of Cuba con en a continues right after this.

>>live from Atlanta, Georgia. It's the Q covering Answerable Fest 2019. Brought to you by Red Hat. >>Hey, welcome back, everyone. It's the cubes. Live coverage here in Atlanta, Georgia, for answerable fast. Part of redheads. Big news. Ansel Automation Platform was announced. Among other things, they're great products. I'm John for ear, with my coast to minimum, but two great guests. You unpack all the automation platform features and benefits. Walter Bentley, senior manager. Automation Practicing red hat and vj Job Olu, director of Red Hat Consulting Guys Thanks for coming on. Thanks. So the activity is high. The buzz this year seems to be at an inflection point as this category really aperture grows big time seeing automation, touching a lot of things. Standardization. We heard glue layer standard substrate. This is what answer is becoming so lots of service opportunity, lot of happy customers, a lot of customers taking it to the next level. And a lot of customers trying to consolidate figure out hadn't make answerable kind of a standard of other couples coming in. You guys on the front lines doing this. What's the buzz? What's the main store? What's the top story going on around the service is how to deploy this. What are you guys seeing? >>So I think what we're seeing now is customers. Reactor building automation. For a long time, I have been looking at it at a very tactical level, which is very department very focused on silo. Whether country realizes with this modern develops and the change in how they actually go to the market, they need to bring the different teams together. So they're actually looking at watching my enterprise automation strategy be how to actually take what I've learned in one organization. And I still roll it across the enterprise so that now struggling and figuring out how to be scared, what we have, how do we change the culture of the organization to collaborate a lot more and actually drive automation across enterprise? >>Walter One of the things we've been we've talked about all the time in the Cube, and it's become kind of cliche. Digital transformation. Okay, I heard that before, and three things people process, technology, process and capability you guys have done You mentioned the siloed having capabilities that's been there. Check was done very, very well as a product technology Red hat in the portfolio. Great synergies. We talked about rail integration, all the benefits there. But the interesting thing this year that I've noticed is the people side of the equation is interesting. The people are engaged, is changing their role because automation inherently changes there, function in the organization because it takes away probably the mundane tasks. This is a big part of the equation. You guys air hitting that mark. How do you How are you guys seeing that? How you accelerating that has that changing your job, >>right? So customers are now economy realizing that going after automation in a very tactical manner is not exactly getting them what they want as a far as a return on investment in the automation. And what they're realizing is that they need to do more. And they're coming to us and more of an enterprise architectural level and say we want to talk mortgage grander strategy. And what they're coming to realize is that having just one small team of people that were calling the Dev Ops team is not gonna be ableto drive that adoption across the organization. So what we're trying to do is work with customers to show them how they collaboration in the culture of peace is huge. It's a huge part of adopting automation. Answerable is no longer considered a emerging tech anymore. And and I when I say that, I mean a lot of organizations are using answerable in many different ways. They're past that point, and now they're moving on to the next part, which is what is our holistic strategy and how we're gonna approach automation. And And we wanted leverage danceable, unanswerable tower to do that. >>Does that change how you guys do your roll out your practices in some of your programs? >>Well, we did have to make some adjustments in the sense of recognizing that the cultural piece is a pivotal part of it, and we can go in and we can write playbooks and rolls, and we can do all those things really great. But now we need to go in and help them structure themselves in a way where they can foster that collaboration and keep a moment. >>And I'll actually add on to that so reactive, large, open innovation labs three years ago, and what we have to learn doing that is using labs and allows practices to actually help customers embrace new culture and change. How they actually operate has actually helped us take those practices and bring it into our programs and kind of drive that to our customers. So we actually run our automation adoption program and the journey for customers through those practices that we actually learned in open innovation loves like open practice, library, even storming priority sliders and all of those modern techniques. So the goal is to help our customers understand those practices and actually embrace them and bring them into the organization to drive the change that that's looking for within the organization. >>A. J. Is there anything particular for those adoption practices when you're talking about Cloud? Because the communication amongst teams silos, you know, making things simpler is something that we absolutely do need for cloud. So I'm just curious how you connect kind of the cloud journey with the automation journey. >>So all of the journey program that actually created, whether it's a contender adoption program or the automation adoption program, we actually followed the same practices. So whether you're actually focused on a specific automation to, like, answerable or actually embarking on hybrid multicolored journey. We actually use the same practices so the customers don't have toe learn new things every time you have to go from one product, one of the so that actually brings a consistent experience to customers in driving change within the organization. So let's picture whether it is focusing automation focused on cloud migrating to the cloud. The practices remained the same, and the focus is about not trying to boil the ocean on day one. Try to break it into manageable chunks that give it a gun back to the business quickly learned from the mistakes that you make in each of the way and actually build upon it and actually be successful. >>So, Walter, I always love when we get to talk to the people that are working straight with customers because you come here to the conference, it's like, Oh, it's really easy Get started. It doesn't matter what role or what team you're in. Everybody could be part of it. But when you get to the actual customers, they're stumbling blocks. You know what are some of those things? What are some of the key things that stop people from taking advantage of all the wonderful things that all the users here are doing >>well. One of the things that I've identified and we've identified as a team is a lot of organizations always want to blow the ocean. And when and when it comes down to automation, they feel that if they are not doing this grand transformation and doing this this huge project, then they're not doing automation. And the reality is is that we're Trent with showing them that you can break things up into smaller chunks, as Visi alluded to. And even if you fail, you fail fast and you can start over again because you're dealing with things in a smaller chunk. And we've also noticed that by doing that, we're able to show them to return on investment faster so they can show their leadership, and their leadership can stand behind that and want to doom. Or so that's one of the areas. And then I kind of alluded to the other area, which is you have to have everybody involved. You want just subject matter experts riding content to do the automation. You don't want that just being one silo team. You want to have everybody involved and collaborate as much as possible. >>Maybe can you give us an example? Is about the r A y How fast to people get the results and, you know, prove toe scale this out. >>So with the automation adoption journey, what we're able to do is is that we come in and sit down with our customers and walk them through how to properly document their use cases. What the dependencies, What integration points, possibly even determining what is that? All right, ranking for that use case. And then we move them very quickly in the next increment. And in the next increment, we actually step them through, taking those use cases, breaking them down into minimum viable products and then actually putting those in place. So within a 90 day or maybe a little bit more than a little bit more than the 90 day window, were able to show the customer in many different parts of the organization how they're able to take advantage of automation and how the return on investment with hopes of obviously reducing either man hours or being able to handle something that is no a mundane task that you had to do manually over and over again. >>What are some of the things that people get confused about when they look at the breath of what's going on with the automation platform? When I see tool to platform, transitions are natural. We've seen that many times in the industry that you guys have had product success, got great community, that customers, they're active. And now you've got an ecosystem developing so kind of things air popping on all cylinders here. >>So the biggest challenge that we're actually being seeing customers is they actually now come to realize that it's very difficult to change the culture of the organization right there, actually embarking on this journey and the biggest confusion that is, how do we actually go make those changes? How do we bring some of the open practice some of the open source collaboration that Riddle had into the organization so they actually can operate in a more open source, collaborative way, and what we have actually learned is we actually have what we call its communities of practice within Red Hack. It is actually community off consultants, engineers and business owners. The actual collaborate and work together on offering the solutions to the market. So we're taking those experiences back to our customers and enabling them to create those communities of practice and automation community that everybody can be a part off. They can share experiences and actually learn from each other much easier than kind of being a fly on the wall or kind of throwing something or defense to see what sticks and what does not. >>What's interesting about the boiling the ocean comment you mentioned Walter and B J is your point. There is, is that the boil? The ocean is very aspirational. We need change rights. That's more of the thing outcome that they're looking for. But to get there is really about taking those first steps, and the folks on the front lines have you their applications. They're trying to solve or manage. Getting those winds is key. So one of things that I'm interested in is the analytics piece showing the victory so in the winds early is super important because that kind of shows the road map of what the outcome may look like versus the throw the kitchen, sink at it and, you know, boil the ocean of which we know to the failed strategy. Take us through those analytics. What are some of the things that people tend to knock down first? What are some of the analytical points that people look at for KP eyes? Can you share some insight into that? >>Sure, sure. So we always encourage our customers to go after the platform first. And I know that may sound the obvious, but the platform is something that is pretty straightforward. Every organization has it. Every organization struggles with provisioning, whether of a private cloud, public cloud, virtualization, you name it. So we have the customer kind of go after the platform first and look at some of their day to operations. And we're finding that that's where the heaviest return on investment really sits. And then once you get past that, we can start looking like in the end, work flows. You know, can they tie service now to tower, to be able to make a complete work flow of someone that's maybe requesting a BM, and they can actually go through that whole workflow by by leveraging tower and integration point like service. Now those air where we're finding that the operators of these systems going getting the fastest benefit. And it also, of course, benefits the business at the end of the day because they get what they need a lot fast. >>It's like a best practice and for you guys, you've seen that? Yes, sir. Docked with that out of E. J. What's your comment on all this? >>So going back to the question on metrics Automation is great, but it does not provide anybody to the business under the actually show. What was the impact, whether it's from a people standpoint, cost standpoint or anything else. So what we try to drive is enable customers. You can't build the baseline off where they are today, and as they're going through the incremental journey towards automation, measure the success of that automation against the baseline. And that actually adds the other way back to the customer. As a business you didn't get to see. I was creating a storage land. I was doing it probably 15 times a month. Take it or really even automated. It spend like a day created a playbook. I'll save myself probably half, of course, and that could be doing something that's better. So building those metrics and with the automation analytics that actually came in the platform trying those bass lines. So the number of executions, actually the huge value they'll actually be ableto realize the benefits of automation and measure the success off within enterprise. >>So I'm a customer prospect, like I want to get a win. I don't want to get fired. I won't get promoted. Right, I say, Okay, I gotta get a baseline and knock down some playbooks. Knock that down first. That what you're gonna getting it. That's a good starting. >>Starting. Understand your baseline today. Plan your backlog as to what you want to knock down. And once you know them down, build a dashboard as to what the benefits were, what the impact was actually built upon it. You actually will see an incremental growth in your success with automation. >>And then you go to the workflow and too, and that's your selling point for the next level. Absolutely good playbook. Is that the automation programs that in a nutshell or is that more of a best practice >>those components of the ah, the automation adoption journey that we allow the customer to kind of decide how they want their journey to be crafted. Of course, we have a very specific way of going about and walking them through it. But we allowed in the kind of crap that journey and that is those the two components that make up the automation. >>We're gonna put you guys on the spot with the tough question We heard from G. P. Morgan yesterday on the Kino, which I thought was very compelling. You know, days, hours, two minutes. All this is great stuff. It's real impact. Other customers validate that. So, congratulations. Can you guys share any anecdotal stories? You know, the name customers? Just about situations Where customs gone from this to this old way, new way and throw some numbers around Shearson Samantha >>is not a public reference, but I like to give you a customer. Exactly. Retail company. When we first actually went and ran a discovery session, it took them 72 days to approach in an instance. And the whole point was not because it took that long. It because every task haven't s l. A We're actually wait for the Acela manually. Go do that. We actually went in >>with our 72 hours, two days, two days, >>actually, going with the automation? We Actually, it was everybody was working on the S L. A. We actually brought it down to less than a day. So you just gave the developers looking to code 71 days back for him to start writing code. So that's the impact that we see automation bringing back to the customers, right? And you'll probably find the use causes across everywhere. Whether J. P. Morgan Chase you actually had the British Army and everyone here on states talking about it. It is powerful, but it is powerful relief you can measure and learn from it >>as the baseline point. Get some other examples because that's that's, uh, that's 70 days is that mostly delay its bureaucracy. It's It's so much time. >>It's manual past and many of the manual tasks that actually waiting for a person to do the task >>waterfall past things sound, although any examples you can >>yes, so the one example that always stands out to me and again, it's a pretty interviewing straight forward. Is Citrix patching? So we work with the organization. They were energy company, and they wanted to automate patching their searches environment, patching this citrus environment took six weekends and it took at least five or six engineers. And we're talking about in bringing an application owners, the folks who are handling the bare metal, all all that whole window. And by automating most of the patching process, we were able to bring it down to one weekend in one engineer who could do it from home and basically monitor the process instead of having to be interactive and active with it. And to me, that that was a huge win. Even though it's, you know, it's such dispatching. >>That's the marketing plan. Get your weekends back. Absolutely awesome. Shrimp on the barbecue, You know, Absolutely great job, guys. Thanks for the insight. Thanks. Come on. The key. Really appreciate it. Congratulations. Thank you. Thanks for sharing this queue here. Live coverage. Danceable fest. Where the big news is the ass. Full automation platform. Breaking it down here on the Q. I'm John. First to Minutemen. We're back with more coverage after this short break

>> live from San Francisco, celebrating 10 years of high tech coverage. It's the Cube covering Veum, World 2019 brought to you by VM Wear and its ecosystem partners. >> Welcome back. We're here! Mosconi North for VM World 2019 10th Year of the Cube covering VM World. I'm stupid and my co host is John Troyer. And welcome to the program to guest from Del Technologies. Sitting to my right is Tender, my Mondal, who's the director of storage solutions and sitting to his right is David when the senior director of server, product planning and management also with Dell. Gentlemen, thanks so much for joining us. All right, so we've got server and storage and talk about something that we've been talking about for a while on the server side been delivered for a bit and on the storage side is now rolling out. So everybody's favorite topic. Nonviolent till memory express or envy me as it rolls off the tongue storage class memory, or SCM and lots of other things, you know, down there, really helping a big, transformational wave that, you know, we really changes how our applications interact with the infrastructure channel, you know, bring us up to date on the latest. >> Sure on, let's start where you ended. We're seeing explosion off applications, right? And in fact, in mornings, keynote. Bad girl singer had a stocky speaks. There are 352 million enterprise applications today. On it will be 792 million in three years. Now, as the applications are growing exponentially, we cannot keep growing the infrastructure at that rate, So N v m e is the way we can consolidate it. Ah, lot off the infrastructure. If we can think about in tow and envy, Emmy starting from the server in fear me off our fabric through the stories area down, toe the back end with envy Emmy necessities. This actually can put together a great platform where you can consulate it. Ah, lot off the applications and delivering the high performance low latency that will need while meeting video surfaced level objectives so we can go over a little bit off the details, but I think it all starts from envy me over fabric coming from the server to the story, Ari. So probably like that's the fourth step we need to consider >> David. Do You know, I love this discussion when we get to talk at the application later because, you know, Flash changed the market a lot. You know, it's like, you know, much better energy, and it's much faster, Anything. But you know, this inflection point that we're talking about for application modernization, you know, envy me is one of those enablers there and something they know your team's been working on >> for a while. Yeah, actually, on the power each side we've been, You know, we've been embracing the benefits of enemy for quite some so many years now, right? We start out by introducing enemy in our 12 generations servers, you know, frontloaded hot, serviceable drives. And then, of course, we branch out from there on in today, you know, Ah, a lot of the servers from a Polish family all support enemy devices. So the benefit there is really giving customer choices in terms of what kind of storage kind of cheering they wanted, you know, for the applications needs. Right now, one of things that's great about, you know, enemy over fabric is it's more than just a flash storage itself. It's about enabling the standards, you know, across the host across the data fire Break down to the storage really to deliver on the overall performance that you know the applications of needs and buy, you know, improving I ops and lower late, Easy overall, from a server perspective, this just means that we're releasing more CPU cycles back into the application so that they can run different types of workloads. And for us, this is this is a great story from power. Just was from Power Macs and coming together to enable this Emmy, Emmy or fabric. >> You know, I'm I'm I'm kind of slow about some of these things, but if you kind of squint at the history and, you know, we went from the PC revolution and then we had, you know, we had Sands and raise right and we had we had centralized toward shared storage last couple of years, a lot of interest and stale right hyper converged. And you had a You had a lot of pizza boxes with the storage right there. It's I mean, I now think right and I'm following the threat, I think which is now that where we now can have ah, Iraq with again a fabric and and again, now we can We can focus on our envy me storage over our envy me over fabric driven, solid state storage somewhere below my servers that are that are doing handling compute somewhere else. Is that that the future we're headed towards now >> Yes. I mean, everything has its place. But to give you the perspective, right? It's not just, I mean coming down to the storage area, but how This is enough bling, the future storage as well. And the storage class memory is the perfect example. And as Defeat said, let's take power, Max, as an example, right. Eso in power Max, you can It is like entrant, envy me ready like you get envy emi over Fabrica de front end But then we have n v m E s s trees in the back end. The thing is now it is also the N v m e is enabling technologies like stories class memory which is bringing in very high performance, very less latency Latency is going down in the order off like tents off microseconds. Now this is as close as you can get. Tow the like Dedham with persistent story. However, you need a balance. This is like order of magnitude are costlier. Now you got bar Max. What we're doing in terms of first, it's envy me. Done right? What do you mean by that? You have, like, Marty controller architectures that can actually do this level of parallel processing and our concurrency. And then we have bought, like, ECM for storage, class, memory and envy, Emmy essences. And we're doing intelligent tearing best on the built in mission learning engine that we have. And it is looking at 40 million data sets. Really time to decide. Like which sort of walk lords should go on this same drives which should go on and the M. E s estates. And on top of it, you add quality of service. So this platform gives you are service level objectives. You can choose from diamond, platinum, gold, silver or bronze, and you can consulate it. Ah, lot off those 352 million different types of applications on this area guaranteeing you are going to meet all off your SL s, no matter what type of applications they were consolidated into. >> Okay, I'm wonder if you could boast. You know bring us into what this means for VM wear customers and break it into two pieces. One is kind of a traditional virtualized shop. And secondly, you know, spend a lot of time in the keynote this morning talking about the cloud native containerized, you know, type of environment. Will there be any difference from from both of your world? >> Yeah, absolutely. I'm glad you brought that up because, you know, from from our perspective, right, what we've seen with the enablement of enemy platforms. You know, John, you brought up a very interesting point, right? It seems like you know, past couple years, we went from moving storage onto the host and now would envy me with fabric. We're actually taking the storage away from the host again. Right? And that's exactly true, because, you know, the first, the first statement you brought up stew. It's about how flash enabled different applications to run better on the host. What? We see that still right? And so what enemy? You know, we see the lower response time enabling our customers Thio run more jobs and more v ems per server. That's one aspect of it. You know, we've seen his benefit a lot of our platform today or using various different applications and solutions, and you talk about the ex rail that's a visa and story for Del. You Talk about Visa and ready notes for customers who want to build it themselves. Right platforms enabled would envy me back playing enemies. Storage allows them to use enemy or SAS sata whatever they want. But the point is, here is that when they're using every me flash, for instance, and I'll talk a little bit about the power climaxed with this all flash, uh, me back plane in a case in the study that we did with V San application running, oh ltp type of workload, we saw the response time with every me over traditional SAS, you know, from our competitors improved by 56% right, which means that from that same particular solution build out, we were able to add 44% more of'em on the platform. Now, at the same time, we increase the overall orders per minute by roughly over 600,000. Oh, pm's for that type of, uh, benchmark over our nearest competitors so that right there is the benefit that we see from my virtual eyes from, Ah, being where perspective >> on. I'll add from the storage perspective in two ways. In fact, in last vehement in a MIA, we demonstrated in tow and envy, EMI over five break up with special build off this fear supporting Envy me over fabric and stories. Class memory with envy Me drives what it gives you a regular like this fear best environment is that you have the ability to move your PM's around like the applications where the highest performance and Latin's is critical. It will be on those special service levels and special like de testers. In fact, that demonstration was like ECM did a store, and in P m E Sense media does so in the same fabric with in Bar Mexican moved things around, whether it's like regular Fibre Channel or CNN and then the other part. I want to add in the morning like we saw the announcement that now communities is built in or will be built in with the years Excite platform, right and you're sexy is bread and butter off all the storage customers that we have now with like when you consider those, uh, those things built in under this fear black from Think about, like how many applications? How many actualized workloads you can run, where that it's on premise or humor. Cloud on AWS. All of those consolidation, as well as like the performance needs while reducing your footprint does the benefit of the V M R R shops. But the PM admits are going to see from the storage site >> again. I'm not following the parts, but what kind of we're not talking about a couple of megabytes here anymore, Right? What size of parts are shipping these days? So >> So, from our perspective, up to 77 gigabyte actually start. Seven terabytes drives are available on the markets today for Envy Me Now, whether customer by those drives, you know, it depends on economic factor. But yeah, it's something that's in this available from Dell >> so on. I'll act to what David said so far in CM drives 750 gig to 1.5. Articulate a C M drives on Dwell ported often drives that will be available in the power Max Acela's 15 terabyte envy EMI assistants. So this is the capacity we're talking about. And again the Latin's is at the application level, like from the storage like you're going to see, like, less than 300 microsecond. That's the power we are bringing in with this technology to the market. >> Give >> us a >> little look forward we talked about, you know, envy me has been shipping for a bit on the servers now, really rolling out on the storage side, I saw there's a lot of started from the space. You know, one recent acquisition got guts and people talking. What? What should we be looking for from both of you over kind of the next 6 to 12 months. >> So over next to a next 6 to 12 months, he will see a lot of innovation in this case from the storage site where wth e order of magnitude. I mean, the one single Ari, I mean, today it supports, say, like, 10 million I offs less than 500 microsecond latency. Ah, I cannot give you the exact details, but within like, a short time, these numbers are going to go up by more than, like, 50%. Latency is goingto get reduced. The troop would will be driving will actually like more than double s o. You see, like a lot of these innovations and kind of like evolution in terms off the drive capacities both from the CME, drives perspective. Envy me, assess these. Those will continue to expand, leading to foster performance. Better consolidation, Uh, for all the workloads. >> Yeah, from our perspective, I mean, you know, data growth is gonna continue. We all know that, And for us, it's like designing systems based on what the customers need, what the applications needs, right. And that's why we have different types of storage available today. So for us, you know, while we're doing a lot of things from a direct attached storage perspective, customers continue to have a need for share storage. EMI over fabric just provides a better know intense story for us, really from a Power edge and Power Macs perspective. But in the future, you asked what we're going to do. Well, we see the need to probably decouple stories, class memory from the host again. And really, what's preventing us from doing today? It's really having the right fabric in place to be able to deliver to that performance level that applications needs. MM evil fabrics, fibre Channel Ethernet ice, scuzzy or I'm sorry, Infinite Band, whatever. These are some of the things that you know we're looking forward to in the future to make that that lead. All >> right, well, it's really been great to see technology that I know the people that build your products have been excited about for many years. But rolling out into the real world deployment for customers that will transform what they're doing. So for John Troyer, I'm still Minuteman back with lots more coverage here from Be enrolled 2019. Thanks for watching the Cube.

>> live from Boston, Massachusetts. It's the you covering your red hat some twenty nineteen brought to you by bread hat. >> Welcome back to our continuing live coverage here, read. Had summat. Twenty nineteen. You're watching Cube. I'm John Wallis along with stewed minimum. Nice to have you here with us as we head toward the homestretch. Day three of our three days of coverage here on the Q. We're now joined by a couple of guys who they put on their traveling shoes to get here, both hailing from Sydney, Australia. Gilman, pull a Matisse who's a senior innovation lead at Optimise and Vasily Check Culkin, who's a principal software architect, also adopted, which is the second largest mobile phone service provider in Australia. Gentlemen, thanks for being with us. Thanks, fiving. It's a long way to come, right? >> Yes, it is, but it's very worst trip. >> Excellent. Well, you're both on the keynote stage this morning. We'LL talk about that in just a little bit for folks who might not be familiar with obvious once you tell us a little bit about your footprint in Australia and what brings you here to talk about red hat and open >> shift well as you mentioned the obvious is a leading telco in Australia way are lucky that we own our infrastructure, which makes it a fantastic place As software engineers or infrastructure engineers working a CZ, we can develop new products and new solutions or innovate. It was in this network. Um all roles for the city and I adopted is essentially to identify new opportunities to innovate within our networks. We use our core I sets to innovate, but not on ly Just do this research and development also execute on this way. Call this a bit of an applied innovation where a ninety we would work really hard in in taking it, Teo to realise come but live writing on Colossus. >> So we're having a lot of stories with customers about transformation and telecommunications is one that's fascinating to look at because, you know, you work on software, you know, when I think back to tell Comet was, you know, fiber and towers and you know, physical implementation. But, you know, software, such a large part of what's going on. You tell us some of the changes going on and you know what's impacting your role in Annapolis? >> Uh, it's it's impacting all. Tell CAS actually, but yes, kill Cosa Switching from this old mine set off just fathers just hours. And this is Dan movements and five hundred Carmen, which is driving a lot of changes. People start thinking about social network functions and how we can dip alone on edge. How we can help our customers and developers to collaborate on next features how we can leverage although technologists and a state we have. >> I think if you think of software defined network and they moved to naturalization, you can now think of this. Australia is a big country that so you can not think of this entire infrastructure is being virtualized and could be made available for Also use a CZ well, so it's really changing that sense that it's not closed anymore and you can open to new cases. >> You know, you bring up it. Just a point about the pure geography of Australia. Huge country. Twenty five million people. No way would jealous here in the States, you had twenty five just, you know, in the Boston New York area. Probably I would think somewhere around there, but house that factor and just in terms of your operations in general that you do have nine million subscribers spread out over so much geography on dure trying to deliver the state of the art circuit service. Just, >> I said I couldn't take this one. So in terms of distance that there is an important impact. But what Today we were talking about phone calls. Video is essentially managing infrastructure, and you know, it's such a large country as its challenges. But it's something we're getting very good at a CZ. We pushing very hard to be present in regional Australia so you can sink of this beautiful landscape in getting five of there being a challenge, but with challenges that they did. The luck that comes with this is that we get to a parade, a scaled network, maybe not with the scale of subscribers that you have in any US, but we're the same challenges. So when it comes to innovation way, get the opportunities to way find you. >> So in the keynote, there was a lot of residents in the audience when you, you know, talked about breaking the language barrier. Maybe, you know, go in share with our audience here, just a tidbit as to what you were talking about. How that works from a technology standpoint. Roll >> out from technology. A point off you telephone you're stuck is it's complex thing. And if you want to integrate directly this telephone system directly with a phone call, it's our job. Okay, I did it. It's tough we did it. I'm never getting so. And the software developers what we tend to do when the get some complex things to solve. We obstructed away, and for us it was off the solution. We need to obstruct away all this complex ing all complex signaling nadiya handling and a very simple way off getting additional voice services within phone call. It's additional challenges like distance, and you can't just kind of older in the cloud because we need to be close to the customer. Otherwise, it will be very, very but quality. Always what and yeah, and it's opens availability toe innovate further, we can bring more services, not only voice, translation and transcription, but just think about it. You got your voice. We can help you. We can like new exciting services on plain old. >> So we had translate today and that we were here to talk about the technology may also the culture changed around. If on network becomes more open. And if we have these opportunities to live rage this network to try to build new products on DH, there are plenty of products that way. Also working on that are based on this idea that waken build products like people build APS to build a napkin, a smartphone or you need this environment way can expose the network in the same digital environment on DH. Translation is very interesting because it's emotional. If you think of communication, language can be a barrier. The a. D that we digitize the phone call and that we can then let build products or or engineer products that break barriers is very exciting. And so this is where we pick the specific use case for for the keynote today, Aziz, you mentioned before it has a emotional showing it, >> but there was if I got it right and police correct me if I didn't, um, you were engaged in a real time phone call right now and then if we pretended that one of you spoke one language, one of you spoke another. There was an immediate translation from English to French, French to English. And the call was being transcribed in real time as well. So it could be used another medium, right? I want to use it in, you know, e mails or other communications text, whatever. So you were stockpiling all this capability right in through the transcription, but doing real time voice translation. >> Take the venue, We idea. So things like translation is something that Microsoft, for example, does really well and many club companies to really well, the value we add is to move from having an adult translation request conditions like this to Russian, to integrating this in in one of the most natural communication channel, which is person to person. Phone call is a perfect place to start, because if there is one place where you're going to a language barrier as phone calls global, you can call anywhere in the world. This's pretty exciting environment. >> Oh, I thought so. I mean, >> you know, it's fascinating to think kind of history of telecommunications. It's well, you know, every country has their own, you know, system. But there needs to be that interconnection so that you know, today I don't think about whether you know I'm calling across the street across the country or across the globe. It takes care of that boy. If I could just plug into some of the available services on INDU translation, you know, right you're goingto bring Bring the world a little bit closer together. >> And the phone. Nichole's of Quintus, You don't sign up to brand, so you do sign up to a telescope. But this is regardless of your device. You can establish a phone call on used the services. I >> know some teenagers I'd like to have their conversations translated for May. Really helpful. >> You can build it a cz. Well, >> can you do work on that? Good. I'll have to think about it. What about five g And what is that doing for you? Just from a purely technical standpoint, the opportunities that you see coming with that I know rollouts. Probably still year or twenty four months away from taking place. I don't know what the Australia rollout is compared to the U. S. But in terms of what that speed is going to do for you, what kinds of possibilities you think the ceiling exist? I >> must after very developed. I'm thinking, like from Pew Software Development Point of view. Excuse me. Perfect opportunity to be connect customers with developers on an edge on a on your network. Andi, it's all the world later NCIS and bend with and you can do fascinating thing on edge ofthe network I raise that sings real time Rachael here at the open to reality five g will enable it and we'LL keep thiss development and improve speed off this stuff. And I'm looking forward to have all of this available not only for me as I'm looking for Loker, I don't want it close the opening network we're opening Tell Kal Toh the cool world off wonderful software development and it's fascinating >> The Savages. Also, if you think of five, you gotta think about momentum. There is this momentum that we have now to improve our networks, and it's not entirely just five g. We've got network function visualizations. We've got Coyote, and that momentum is very interesting because as we improve our network, it becomes more digital and especially mentioned as it becomes more digital. It's more open and enables new opportunities for enterprise customers off for startups to innovate in this environment. >> Okay, so my understanding from what you talked about and, you know, this is built on open shift, you know, what's the importance? You know, why Open shift and what is that enable for your business and ultimately your customers? >> This is actually something way quite proud off. When we started this journey in this software engineering space, it's inclined narrative. It's only natural to build functions in containers, but there was There was effectively that gap between building new applications in the current state of a network that has a a very different approach of operation. So, communities, where's the right tool for us? But when you operate a carrier network, you need strong support and you need Teo. You need to have a very firm Acela's because you don't drop phone calls. This is very important minute communication, and this is where we had a fantastic relationship is really to find a way to operationalize thiss deployment. >> Ricardo wasn't only like operating this thing way worked hand in hand last few years, they've helped a lot this designing systems like best practices. We learned a lot off each other and it was fantastic journey way really enjoyed working on this. It's extremely professional team, >> No, in from a timing perspective Oh, our journey came together a same time, as read it started seeing telcos has being where the next big thing or the next something to very much start focusing on. >> So so what's your next big thing? We're talking about five G and what that's going to open up, and we've read a lot about it here in the States. But from your perspective, you know what? What is that going to enable? What kind of services? Because for G's already, you know, blowing everybody's mind in some respects, right with the data capabilities there imaging transactions, those kinds of things, but five g your thought, I think, >> previews. Innovation cycles things three G for G Always came, came in with a pre pre baked benefits, often speeds with five minutes a little. My opinion is a little bit different. What's happening? What we're doing is is an example of this is in a V that you have a new environment and important environment where new things can happen and so you're going to see this as Oppen versus closed what it means is that the next big thing is not necessarily five year. And Evie. Next big thing is what software developers will make of this environment. And that might be a start up. Or they could be enterprised could bring you cooperate, right? And we are very much very much open to start conversation with anyone that would like to make use of this. He's >> got the next big thing. That was God the next big thing yet, Right, gentlemen, thank you for making the long trip. I know not just to see us, but we do appreciate your carving out some time for us. Good job this morning. And, uh, good luck down the road. >> Thank you for having us. >> Thank you. Thank you. Back with more live from Boston. You're watching the Cuban. You're watching coverage from Red Hat Summit twenty nineteen