>>Live from Atlanta, Georgia. It's the cube covering Ansible Fest 2019 brought to you by red hat. >>Welcome back. This is the cubes coverage of Ansible Fest 2019. I'm Stu Miniman. My cohost of the week is John farrier. And this is the cube insights where we share our independent analysis, break down what we're hearing from the community, what we've learned from all of our interviews. John, uh, you know, we knew community would be a big portion of what we did here. Uh, culture and collaboration were things that we talked a lot about that wasn't necessarily what I thought I would be hearing. Uh, you've been talking a lot about how observability and automation are the, the huge wave. We've seen, you know, acquisitions, we've seen IPOs, we've seen investments. So, you know, your, your, your take here as we're wrapping up. Sure, sure. Last to, um, as we said in our opening in the big scene here has been automation for all that's Ansible's kind of rap because they're, you know, they're announcing their main news ants, full automation platform. >>So that's the big news. But the bottom line is where this emerged from was configuration management and supple started out as a small little project that's solved a very specific problem. It solved configuring devices and all the automation around, you know, opening up ports and things that that were important beyond the basic static routing, the old web one. Dot. O web 2.0 model. And it grew into a software abstraction layer for automating because a lot of that stuff, the mundane tasks in configuring networks and servers frankly were boring and redundant. Everyone hated them patches. So easy ground to automate. And I think, um, it's evolved a lot into dev ops because with the cloud scale more devices, just because software's defining everything, it doesn't mean servers go away. So we know that is more servers is more storage, it's in the cloud, it's on premise, it's cloud operations. >>So automation I think, and I'm, my prediction is is that automation will be as big of a category as observability was. And remember we kinda missed observability we saw it as important. We've covered all those companies, but especially in network management on steroids with the cloud. But look what happened. Multiple companies when public big companies getting sold for billions of dollars, a lot of M and a activity observability is the most, one of the most important areas of cloud 2.0 it's not just some white space around network management. The data is super important. I think automation is going to grow into a highly competitive, highly relevant in the lucrative marketplace for companies and I think Ansible is in pole position to capture that with red hat and now red hat part of IBM. I think automation is going to be very big land grab. It's going to be where the value is created. >>I think observability and automation are going to go hand in hand and I think AI and data, those are the things programming infrastructure revolve around those two spheres. I think it is going to be super important. I think that's why the cube is here. We smelled it out, we sniffing it and we can see. We can touch it and the community here, they're doing it. They're there actually have proof points. Yup. These, this community is demonstrating that the process is going to be more efficient. The technology works and the people are transforming and that is a key piece with automation. People can work on other things and it's certainly changing the game. So all three aspects of digital transformation are in lockstep and, and, and, and expanding rapidly. >>Yeah. John, I would expect nothing less than a bold prediction from you on this space. You know, it's only $150 million acquisition, which is really small compared to a lot of the acquisitions that we see these as heck. You know, red hat Ansible didn't get talked about all that much when you know, IBM went and spent over $30 billion for red hat. But absolutely automation is so important that infrastructure is code movement that we've been tracking for quite a long time helps enable automation across the entire stack. A lot of discussion this week here, networking and security, two areas that we know need to make progress and we need to have, you know, less errors. We need to be able to make changes faster and cloud. We just as in the infrastructure space, that configuration management, we need to be able to simplify things. Absolutely. One of the things that will slow down the growth of cloud is that if we can't simplify those environments, so the same type of tooling and where Ansible is trying to, you know, span between the traditional environments and the cloud is to get this working in the containerization cloud native Kubernetes world that we're living in. >>Yeah, and it's still, you're right on, I mean this is the analysis and that it's spot on. I think one of the nuances in the industry landscape is a, when red hat got acquired by IBM for a massive amount of money, everyone's scratching their heads. But if you think about what red hat has done and you know I'm a real big fan of red hat, you are too. They're smart. They make great acquisitions, Ansible, not a big payout. They had coral West, they, they got open shifts there. They're the decouple their operating systems people. They get the notion of systems architecture. I think red hat is executed brilliantly in that systems mindset, which is perfect for cloud computing. I think Arvin Krishna at IBM really understood the impact of red hat and when I talked to him at red hat summit two years ago, right before the acquisition, he had the twinkle in his eye when I asked him about red at, because you can see them connecting the dots. Red hat brings a lot to the table and if IBM doesn't screw up red hat, then they're going to do well and we talk about red hat not screwing up Ansible and they didn't. Now part of it, if IBM doesn't screw up the red hat acquisition, let red hat bring that systems mindset in. I think IBM could use red has a beautiful way to bring a systems architecture into cloud, cloud native and really take a lot of territory down these new cloud native apps. >>John F automation is a force multiplier for customers and Ansible has that capability to be a force multiplier for red hat. When you look at the ecosystem they're building out here, the Ansible automation platform really helps it get customers more in lock steps. So you know, I was talking to the people and said, Oh, you know, AWS has an update. Oh we need to roll the entire core and put out another version. I can't wait for that. I need to be able to decouple the partner activity, which by the way, they talked about how the disk project is the six most popular in get hub decoupling collections might actually put them lower on the on the list, but that's okay because they're solving real customer problems. And it's interesting, John, we talk about the ecosystem here. One of, there's only a couple of other companies other than red hat that can commit without having to go through approval. Microsoft is one of them. So you talk about the, the collaboration, the ecosystem here where this can be, >>let's do the, the thing about Ansible is that it's a double edged sword. There value is also an Achilles heel. And one of the critical analysis that I have is, is that they're not broad enough yet. On and there and there. I won't say misunderstood the customers here in the community, they totally get it. Everyone here loves Ansible. The problem is is that in the global landscape of the industry, they're tiny red hat needs to bring this out faster. I think IBM has to get animal out there faster because they have all the elements kind of popping right now. You got community, very strong customer base, loyal and dynamic. You got champions developing. That's classic sign of success. They got a great product, perfectly fit for this glue layer, this integration layer, you know, below containers and maybe you can even sitting above containers depending on how you look at it. And then finally the ecosystem of partners. Not yet fully robust, but all the names are here. Microsoft, Cisco net app F five kind of feels like VMworld on a small scale. They have to up level it. I think that's the critical problem I see with with these guys is that it's almost too good and too small. >>Yeah. Uh, you know, when I look back at when red hat made the acquisition, there were a handful of companies, most of them embracing open source as to which configuration management tool you're going to do. Ansible did well against them and red hat helped make them the category leader in this space. There is a different competitive landscape today. Just public cloud. You know, Ansible can help, but there's some customers that would be like, Oh, I've got different tooling and it doesn't fit into what I'm doing today. So there's some different competitors in the landscape and we know John, every customer we've talked to, they've got a lot of tools. So how does Ansible get mind share inside the company? They had some great stories that we heard both on the Q from like ING and the Southern company as well as in the keynotes from JP Morgan where they're scaling out, they're building playbooks, they're doing this, but you know, this is not, you know, it's not just push a button to get all of this rolled out. >>The IBM marketing should help here. And if I'm, you know, um, uh, the marketing team at IBM, I'd be like all over this because this is a, a game changer because this could be a digital transformation ingredient. The people equation. The problem is, is that again, IBM to embrace this and Ansible has that glue layer integration. This could be great. Now the benefit to them, I think they're tailwind is they can solve a lot of problems. One nuance from the show that I learned was, okay, configuration management, dev ops, great. The network automation is looking good. Security is a huge opportunity because if you think about the basic blocking and tackling patches, configuration, misconfigurations, automation plays perfect role. So to get beachhead in the enterprise as an extraction layer is to own and dominate those basics. Because think about the big hacks. Capitol one, misconfigured firewall to an S three bucket, that wasn't Amazon's fault, but the data on Amazon, this is automation can solve a lot of these problems, patches, malware, vulnerabilities, the adversaries are going to be all over that. >>So I think the security piece, huge upside position, Ansible and red hat as an abstraction layer to solve those basic problems rather than overselling it could be a great strategy. I think they're doing a good job with that. Uh, it totally, you know, built on simplicity and modularity. Uh, this, this tooling is something that it can sit lots of places in the organization, uh, and help that cultural communication. Uh, I was a bit critical of, uh, you know, enterprise collaboration, uh, that, that top down push that you'd get. Um, but here, you know, you've got a tool that uh, as we, we just had on our final interview with, uh, Pirog, you know, developers, they didn't build this for developers, but developers are embracing it. The infrastructure people are embracing it. It gives a sense of some why we here to why we're here is I think Ansible fast as a community event, which we love. >>But two, I think this is early, you know, days in the Canadian, the coal mine and saying that the Ansible formula for automation is going to be a growth year. That's my prediction. And we have data to back it up. If you look at our our community and the folks out in the cube alumni know no that when we reach out to them and get some data. But here's what supports why I think the automation thing with Ansible and red hat is relevant because it applies what we just talked about. The number one thing that came back from the community stew was focused efforts on better results. Automation from time efficiency days, hours to minutes check. Security is absolutely a top driver for automation. That's a tailwind. The job satisfaction issue is not like a marketing feel. Good thing. People actually liked their jobs when they have to, don't have to come in on the weekends. >>So this automation does align with that. And finally infrastructure and developers re-skilling with new capabilities and new things. Is it just an uplift? So those are the drivers driving the automation. That's why RPA is so hot and this is a critical foundation in my opinion. So you know Ansible's is the leading the wave here in this new automation wave and I think it's going to be a big part because it's controlling the plumbing. Yeah, John wanted the machinery. Johnny is the, the, the future of work. We know that automation is going to be hugely important. You mentioned >>RPA, a huge one. I had an interview with the associate professor from Syracuse university or they're teaching this to education. It's not just, Oh Hey you got to go learn coding and learn this programming language. No, we need to have that. That combination of the business understanding and the technology and automation can sit right at that intersection. What's your big learning point? What did you take away? Yeah, so it is, it's that point here that this is not just to some, you know, cool little tool on the side. This is something you John, we've talked at many shows. Software can actually be a unifying factor inside companies to help build platforms and for customers to help them collaborate and work together. This a tool like Ansible isn't just something that is done tactically but strategically, you know, gets everyone on the same page enables that collaboration isn't just another channel of you know, some other thing that a, I don't want to have to deal with it. >>It helps me get my job better. Increases that job satisfaction. That's so hugely important as to if you think about the digital transformation form of the people, process technology, how many interviews have we done, how many interviews have we done, a companies we've talked to where they have the great product and on the process side to address the process. They have the tech but they fail on the people side. It's the cultural adoption, it's the, it's the real enablement and I think Ansible's challenge is to take the platform, the capabilities of their, of their, of their software, launch the platform and create value because if they're not enabling value out of the platform that does not cross check with what platforms are supposed to do, which is create value. And John, the thing I want to look for when we come back to this show next year is how much are they allowing customers delivered through data? >>When we heard from their engineering division here, okay, the platforms, the first piece, but how do I measure internally and how do I measure against our peers? We know that that people want to have, there's so much information out there. How am I doing? Am I, where am I on my the five, five step progression and adoption of automation and you know, Hey, am I doing good against my competition or are they smoking me? Well? That's the metrics with the insight piece and tying it to the rail. Now people can say, look, I just saved a bunch of money. I saved some time. That's the business impact and I think you know when you have the KPIs and you had the analysts to back it up, good things will happen. Students been great. All right, John, always a pleasure to catch up with you. We got lot more here toward the second half of 2019 a big thanks to the whole community for of course watching this here at antelopes Fest. Check out the cube.net for all the upcoming shows. Thank you to our whole production team and to our hosts. Red hat for giving this beautiful set right in the middle of the show. And thanks as always for watching the cube.

>> 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.