>>Live from Atlanta, Georgia. It's the cube covering Ansible Fest 2019. Brought to you by red hat. >>Welcome back. Everyone's cubes live covers here in Atlanta for Ansible Fest. Here's the cube covers. Have red hats event around automation for all. John Ford's do many men. Our next guest is Joe Fitzgerald, Cuba Lum, vice president, general manager of the management business unit at red hat. Great timing for Ansible. Great to have you back on the cube. Good to see you. Thanks for coming on. Thanks for having me. And it's great to have you here at Ansible Fest. Super essential for camera timing about Ansible. Let's do an, I did our intro, uh, analysis and platformization of automation. Big, big move, big news. But there's a bigger trend at play here around automation. Why is the timing now for automation discussions with Ansible? So good. The demand for automation is so broad in enterprises, right? They're trying to do everything from, you know, dev ops, tool chains to IOT devices. >>I'm trying to deploy things faster, uh, you know, fix security vulnerabilities faster. It's all about speed, agility, efficiency. It all comes back to automation. And the news here is the general availability, although available in November as announced on keynote of the Ansible automation platform. So this is something that's been going on for a while and I suppose just been grown weighing now it's a platform. What's in the platform? Why is it important? Why should customers care? So, uh, you know, we've been on this journey with Ansible which started off as this incredibly simple, elegant architecture and a way to automate things. And what's happened over the past couple of years is it's exploded in terms of the number of people who are using it, the number of people who are generating automation integration. Um, and so in working with a lot of customers, right, what we saw the need for was really to help them collaborate and scale their automation efforts. >>Um, scale, you know, who could, you know, build, reuse, share, uh, score content and track it. Really important. So we put a lot of those efforts into the platform to take it to the next level. Really. You know, we've been talking about Ansible, gum stew, going back when you know, 2014 OpenStack, I think I remember we are first talking about the cube. It had a cult following when it emerged. You guys acquired it at what, the next year, 2015 roughly. Um, but Annabelle had this cult following of people who just loved to get into the configuration side of things, make them go better. You guys acquired it, done well with it, kept it going, get the community flywheel, keep rolling a lot of progress since then. So what are you most proud of? What's the most notable things? Oh, the growth of the Ansible journey. What's, what's the big story there? >>So, uh, it's almost four years since red hat acquired Ansible. And I remember when I proposed acquiring Ansible and swell was this small, you know, Eastern U S company with sort of a community cult following, but very small in terms of, you know, commercials and, and reach and stuff like that. Mostly focused on the configuration space. Like a lot of the other automation tools over the past four years. Probably the best thing we did that redhead is really good at is we let the community do what the community does best, right? The innovation, the number of contributors, the amount of Ansible integration modules, playbooks has exploded, right. Uh, if you were in the keynote this morning, um, it was number six on the, you know, repository list out of 100 million, you know, almost, you know, just a massive amount of projects and here it is at number six. >>So we didn't perturb the community, we actually helped it grow and we've been able to help the technology evolve from a config automation product and technology into this very broad spectrum. Now enterprise automation platform that crosses domains like, you know, networks and security and storage and cloud and windows. Just a phenomenal, uh, you know, growth in it. Yup. Show help. Explain how platform sets up Ansible for it future. They talked in the keynote a little bit about starting with some of the, uh, kinda core partners in the collections that they're offering. But in the future for a platform to really be a platform, it needs to be something that users themselves can build on top of. So, you know, help us understand where it is today. You know, when it first announced here for November, um, and where it shows shall be going in the future. >>So we didn't use the platform word lightly. Um, I think that, you know, platform has a set of connotations and, and it's sort of a set of requirements. What we saw was that different teams and groups inside organizations, we're bringing Ansible in and using the technology and having very good success in their particular area. Then what we saw was these teams were trying to share automation and collaborate across organizations. Then even in the community, there's tens of thousands of rolls and playbooks out there that the community has built. There might be 300 that do the same thing, which is the best one, which, which one are people using? Uh, you know, how successful is it? How long does it take? Um, what we found was that they needed a bunch of tools to be able to collaborate, track, uh, analytics about stuff so that they could share and collaborate at a higher scale. >>Yeah. I, that's one of the great value propositions when we talk about SAS is if it's done well, not only can I share internally, but I can learn from others that have used the platform and make it easier to take advantage of that. So is that part of that vision that you see with the platform? Yeah, so I mean, there's a couple different ways of sharing. If you're running a SAS service, then you know, a central person is coordinating the sharing and things like that. What we tried to do with the, with the Ansible platform is basically enabled the way that people can share content without having to go through a central, you know, agent, if you will. So we provide services and things to help them manage their, their content, you know, with uh, you know, uh, galaxy and collections and things like that. >>Um, it's all about organizing and being able to share content in a way, uh, to make them more efficient. Should I talk about the trends around, um, you've done it. First of all, you done a great job with Ann's book. Congratulations. Um, the big fan of that company and you guys did a good job of it. As it goes full, where you're thinking about cloud complexities as people start looking at the cloud equation, hybrid and cloud 2.0 and the enterprise complexity still is coming as more of it. How do you guys see that? How are you viewing that, um, that marketplace because it's not just one vertical, it's all categories. So how are you guys taking animal to the next level? How you guys look at that, managing those complexities that are around the corner? Yeah. So if you think about it, you know, everybody's moving towards a multi, multi hybrid cloud, you know, sort of configuration, right? >>Um, each one of these platforms and clouds has their own set of tools which work really well perhaps in their particular cloud or their silo or their environment. If you're an organization and you're running multi-cloud, you're responsible for automating things that might span these clouds. You don't want to have different silos of automation tools and teams that only work in one cloud or one environment. So the fact that Ansible can automate across these, both on premise and in the public clouds, multiple public clouds, across domains, network storage, compute, create accounts, uh, you know, do all sorts of things that you're gonna need to do. So it's one automation technology that will span the complexity of those environments. So it really, it's, I don't see how people are going to do it otherwise without fielding lots of people and lots of tools. You know, we were talking with Stephanie and Sue and I talked on our intro insights segment around the word scale has been kicked around, certainly is changing a lot of the landscape on how companies are modernizing the open source equation, but it's also changing the people equation. >>I want you to explain your vision on this because I think this is a key point that we're seeing in our community where people have told us that automation provides great efficiency, et cetera. Good security, but job satisfaction is a real big part of it. You know, people, it's a people challenge. This is about people, your view on scale and people. So organizations are under tremendous pressure right now to do more, right? Whether it's deploying new application faster to close security vulnerabilities faster, uh, to move things around to, to, to right size, you know, resources and applications and things like that. And you know, Ansible allows them to do that in a way where they can be much more efficient and be much more responsive to the business, right? Otherwise, you know, you see some of the customer testimonials here where the amount of time goes down from six hours to five minutes, the teams can be far more productive. >>Um, it, it really gives job satisfaction because they can do things that were almost impossible to automate before by using Ansible to automate network storage and compute in the same playbook. Before, those were three different tools or three teams and people of solving some of the same problems in different areas. And this is where playbooks can be a problem and an opportunity because we have too many playbooks, you have to know which playbook to be available. I mean you can almost have a playbook of playbooks and this is kind of a opportunity to use the sharing collaboration piece. What's your rich to thought on that as that playbook complexity comes in as more playbooks enter the organizations, you know, there's a lot of deployment of the same kind of stack or the same kind of configuration and things like that. So you know, it's really extending community beyond, you know, you know, working on code into working on content, right around automation. >>So if somebody wants to deploy engine X, I think there's over 300 different, you know, playbooks to deploy engine X, right? We don't want to have 5,000 playbooks to deploy engine X. Why can't there be a couple that people take and say, wow, this is perfect. I can tweak it from my organization, integrate my particular systems, and I can hit the ground running instead of trying to either start from a blank page or to go sift through hundreds of almost close, uh, you know, playbooks that do sort of the same thing a lot of times. David's big time. Enormous. Alright. >>So Joe, congratulations on the four years of just continued growth, you know, great momentum in the community wanting to touch on, you know, the, the, the big move, uh, you know, in the last year is, you know, IBM spending, you know, quite a few dollars to, to acquire red hat. What will this mean for kind of the reach and activity around Ansible in the community, the IBM acquisition. >>So IBM had been involved in Ansible in a number of their, you know, products, right? In terms of integration into Ansible. So they have teams and folks within IBM that obviously got Ansible all before the acquisition. Um, I think that it's, it's highly complimentary. IBM has very strong capabilities around management and monitoring, security and things like that. All of those things inevitably turn to automation. Right. Um, so I think it really, um, it only gives us access to IBM and, and they're sort of, you know, their their channel and their accounts in their, and their reach, but also their teams that have these, these sets of technologies, um, that are natural compliment, you know, whether it's Watson driving Ansible or security or network monitoring, driving Ansible automation. It's a really powerful combination. >>Yeah. I also just want to get your kind of macro level view on automation. I sat on a panel talking to CIS admins about careers and it was the number one thing that they felt they needed to embrace. We see like the RPA community probably in adjacency to what you see heavily pushing automation, uh, you know, help explain how important automation is and that it's not, you know, just a silver bullet also. >>Yeah. So, you know, a lot of times people are, you know, the, the sort of the easy, um, you know, description is automation's gonna eliminate jobs or things like that. I think it's more like sort of the power tool analogy. You know, you know, if you had a, you know, a hammer and a screwdriver before, now you've got a power screwdriver and a pneumatic hammer and uh, you know, all sorts of additional things. They're force multipliers for these people to do broader, bigger things faster, right? Um, and that's what every organization is driving them to do. How agile can you be our competition deployed something, how fast can we deploy it and how many, you know, new releases a week. Can we deploy, um, when security hits, you know, how fast can we close the vulnerabilities that hours, days, weeks, or can we do it in minutes? >>The old expression, if you, if you're a hammer, everything looks like a nail. But if you're an agile, you can adjust to figure out the opportunity. It's kind of awesome kind of quote there. This speaks to the changes. I want to get your thoughts. Last question for you is, as someone who's been in the industry for awhile, we've first interviewed and I think 2014 at OpenStack when we first started chatting around the industry. So much has changed now more than ever. The modern enterprise is looking at cloud impact, operating as an operating model, cloud one, Datto, Amazon compute, storage standups software, and they're piece of cake startups. We're doing it now as enterprises really want to crack the code on cloud software automation. Observability these new categories are emerging, kind of speaks to this cloud 2.0, how would you describe that to folks if, if asked, what's the modern era enterprise cloud architecture look like? >>What is cloud 2.0, how would you take a stab at that definition? So I would say after all these years, cloud is really entering its infancy and what does that mean? We're just starting now to appreciate what can be built in cloud and we're going to get a big boost soon with five G, which is gonna, you know, increase the amount of data, the amount of, uh, you know, edge devices, uh, IOT and things like that. Um, the cloud is becoming, you know, the first choice for people when they build their architectures and their business. Um, it's gonna fundamentally change everything. So I think, you know, some people, what's the quote? You know, some people overestimate, you know, what the technology can do in the short term and underestimate what it can do in the longterm. We're now getting to that point where people are starting to build some really powerful cloud based applications. See this as a big wave then big time wave. Yeah. I mean, we had a quote still on the cube last week. Data is the new software, so software, abstractions, automation. This is the new way. I mean, it's a whole new architecture. So exciting. Thanks for coming on the cube. Appreciate juncture having thanks. We're here at the Asheville Fest, the Cuban Chalfont stupid men. Break it down. The analysis, getting into the automation for all conversation. Big category developing. We're covering it here. Live back more after this short break.

>>Live from Atlanta, Georgia. It's the cube covering Ansible Fest 2019 brought to you by red hat. >>Welcome back everyone. That's the cubes live coverage for two days here in Atlanta, Georgia for Ansible Fest. I'm John fire with my cohost, stupid man. Andrew has been, Oh Kratos who's here and senior principal product manager at Ansible. Welcome to the cube. Welcome back. Thank you. Good to see you. 2017 you were last on red hat summit. It's like, Oh it was a, it was basically the introduction to the Ansible network basically. So, so much has gone on. One of the things I'm really impressed by this event and why we're here is um, configuration management and super important part of the plumbing. We all know dev ops is infrastructure as code, but as the evolution of cloud and software is changing the game, you start to see visibility into where automation's coming in. This is the whole focus of the event automation for all. It's the theme w w and this is about the core infrastructure. >>So it's not like it's just a random thing. Six most popular in get hub project out of millions. This is real. It's real. It's quite real and especially on the network side. This is something that came out organically. The birth of Ansible network was because it was agent lists, honestly, you know, simple, powerful agent lists. The agent list piece was the piece that really made it really fly for Ansible. Configuration management. By the way, on net networking side when we talked about this before is the most important because that's where it's the most static has one of those where it's been most static. I mean we all know networking, right? But as networking becomes policy base and moves up the stack, we've seen some firms like Cisco trying to figure out their dev net. It's like you starting to see the networking mindset moving up the stack. >>This is super huge change. It's a huge change. But the nice thing is that it's easy to get into. So all the network operators and network engineers, they're still used to using command and config modules with their iOS devices, their iOS devices, Juniper, all those things, right? They don't have to throw away everything they've learned for the past 10 15 years in order to get with Ansible. And then when they go beyond that, then they can start seeing the real power of the platform, which we announced today. So going from command line to programmability is kind of what's happening. Yes, absolutely. And what's the big four, the big key factors right now that are driving this? So a lot of key factors are, I mean, you saw the keynote this morning with Microsoft, that's our, that was a huge, and it'd been doing this for about two years. >>So they started from, from nothing. He chose Ansible and they quickly saw that the power of automation for the networks, but they had to grow it at scale. So that was the big problem was how do we do this at scale while still using all the knowledge that we've learned? So day zero, day one, it's extremely important and obviously we know that, but as we were going down the journey with them from a engineering standpoint, day two became extremely important. And that's what we're, we're focused on now. You know, uh, it was really interesting. Microsoft really talked about that cultural shift. Uh, you know, we've heard in the networking space forever, it was like you're all going to need to become coders. You're going to need to be able to do this to tell us how Ansible is really impacting some of those cultural shifts in a, you know, how is that discussion changed today versus what it might've been a few years ago? >>It's truly half the battle is the culture I like to call it as everyone's talking about digital transformation in a network world, this is an analog transformation in all honesty. This isn't anything about the bits and bytes. You cannot automate anything today. There are lots of point tools to automate networks today, but how are you gonna actually move that into a world where culturally you can have people buy in from the bottom up organically as well as from the top down from the it managers. It's extremely important. So on the platform announcement, the key and as was the Ansible automation platform, where can you just help us understand the relationship between network automation and the automation platform? Because I'll see an you need to move things around the network, but there's a lot of other things being configured as well and automated. What's the relationship between the two? >>So before we had the platform actually ends well network was an actual product. It was a separate skew as a separate offering and we treated it as such as a platform. We were like the first Guinea pigs I like to think of, we were the ones that said let's treat Ansible as a platform and let's move it that way. So we actually went out and built roles. We built modules, we built a network engine, which is a parser, right? Similar like text, FSM, uh, you know, those kinds of things. We put those in galaxy 22,000 downloads later. We proved it. We know that everything that we're doing in galaxy today for Ansible network proves the fact that people are using it as a platform. And we were successful in that, doing that and then telling me yours was that just track record wise, what was it, how many years? >>Oh, that was a year. So to.seven was when we released network engine for parsing, parsing CLI commands, you know, and that moves into the next generation of what we call the day two operations for networking is typically we see network configuration has been a one way street. So you would pull a configuration data from a device, you would have to parse it, you put it in SCM, it's an an SCM and now you actually have to put into a template and then you push it. Right. This has been a one way street typically, and it's an Ansible has been very good at one way streets, but now we're moving towards an Ansible two. Dot nine coming soon is making that a two way street. So integrating the fat collection from module, so when you pull facts from iOS, EOS and XLS, et cetera, treating that data consistently across the board and using that for it. >>Networking is one of the tracks here at this show. What are, what are some of the more popular things? What, what, what? Where's the focus? The focus is, it's across the board. Again, you have people that are it managers that have been doing Ansible for years and now they're saying, Hey look, they're seeing network automation is extremely pervasive. How can we get that into our pipeline? We have ticketing systems. How can we integrate ancil network with our larger business processes? And then tops like top five use cases, the typical backing up systems, uh, from, uh, you know, backup, restore a, and then doing a lot of sorts of true things there too. So making sure that you have all of your, your network configuration data off the box, right? A lot of people are fetching configurations from thousands and thousands devices. That's pretty hard to do. So let's make that easier for them. >>What's been the customer interest and the growth path for network automation? Because I'll see, that makes sense. I see a different product, but now that the automation picture's getting wider and bigger, what's the interest from customers say? The key focus area though on that? Well, we've typically focused on to date and, and from the marketing slides is the number of platforms we've supported. We can always see up to the right, right. We support 10 platforms, 2030, we're up to 65 platform supported. I think we've pretty much proven the fact that I think we can pretty much work on anything. So it's going beyond that and making lives easier for the network operators, engineers holistically. And this event here, what's going on here for you guys here? What specific tracks are doing? Right? So we're actually conversations you having. Yeah, we're talking more about the actual resource modules that are coming in two dot nine I was talking about, which is bringing fact collection and the modules together as a two way street. >>So as people start moving into this day two operations, um, we have a lot of experts here and they're hitting stumbling blocks around. They're managing ginger temp like 500 lines into templates, like on a daily basis. Nobody wants to do that. So we're getting to a place where the people that are really relying on Ansible in it, in the expert field, making it much, much easier for them to look forward. We had Greg on earlier. And um, Robin, they talk about the glue layer that Ansible provides for the folks that are not using Ansible, what's the big message that you'd like to send them? What's the, what's the real, uh, attraction from the customers and why should people be using Ansible? Well, it, yeah, I mean it's, it, it's for everything. I mean, you don't have to, you really don't. I mean, it, it speaks for itself, but it breaks down the barriers. >>If you're a server person, a restorative person or a cloud person or a windows person or a network person, you all have the same language base in Ansible and you can get things done more quickly and more efficiently that way. So one of the other things we were talking to the community about is the, the feedback loops that you have with the community to tell us a little bit about what your teams hoping to get from the users attending and barges. Oh, absolutely. On the animal network side, everything is done transparently in the community. We have weekly, we have a community meetup. We've had this for a long time. Everything's out in the open. Everything's in get hub. Everything that we've done, we've had a contributor day. I don't know if you were here on Monday, it was focused on network. We're pitching this idea around resource modules in the, in the forward strategy of, of the platform as it relates to network, everyone including the contributors, developers, the partners, all of the people that you could see that half the off half the vendors here on the floor, our network partners. >>So they're invested as well. They want this to succeed. So we're extremely proud and happy that they're along for the ride as well. Alright. Maybe explain to our audience what an angry potato is. Uh, it's a, was it a tater, it's an angry tater. Uh, yeah, it's a, the mascot for AWX I believe. And um, yeah, they're fun. The stickers and little plushes. So we're going back to keep sticking appreciation. What's the coolest thing that you're, you've seen this year that you think people should know about? Oh, wow. Um, I think a lot of, a lot of focus around testing and development. So a lot of developers are now writing code. They're rebuilding the wheel themselves. So developers are writing the same stuff over and over and over again. So how can we scale that to say, Hey, why don't we all get together and write the same code and then about testing. >>So once you actually have the code, you have a lot of vendors here on CIC, D testing quality. So we at its Ansible, um, we can talk, and this was Greg, I don't know if you mentioned earlier, but Greg to go into Sprig said, you know, we're really good at making sure, um, playbooks and roles and modules are correct, but we want to make sure that the vendors and the developers like focused on the functionality. We can give them guidance around, um, syntax and correctness, but we want to make sure that the innovation really comes from them. Andrea, talk about this annual Fest this year, 2019 as we run into 2020 coming up towards the end of the year, fall here. Why is this year different? What's important about this year? Um, this seems to be, this almost seems to be an inflection point this year. Why? Why is it so important as what's what's going on right now that makes this event so popular? >>You're seeing convergence in a lot of different activities. The, the silos around you typically say, I'm a, I'm a, you know, I'm, I do Kubernetes or I do network or I do cloud. You're starting to see a lot of these people like, okay, well I have to do a cloud. I have to do a cloud VPN connection using containers and automate the network. So you're starting to see a lot of these different traditional people having to think outside of their traditional areas and have to start thinking about other areas to their, whatever that whatever their technology silo is in their head, they have to start learning or they're being forced to learn around a lot of different things. It's a systems architecture. Absolutely. System says consequences. You can't just dig in the silo. That's the issue. Absolutely. That seems to be the core issue. And also culturally it's collaborative. I mean, who would have thought configuration management be the next social network for enterprises at turning it out to be, yeah, absolutely. Not social network. Literally like Facebook, but you know, thanks to come on. Thank you so much for having said, we're bringing all the action down here at Asheville Fest where dev ops is being operationalized cultural change within organizations, but keep abilities much more of a systems view now. So the networking is a key part of it. I'm John for a stupid man back after this short break.

>>Okay. We're back here inside the cube, our flagship program about the events and extract the signal from the noise. This is strata conference. O'Reilly media is a big data event. We're talking about Hadoop analytics, data platforms, and big is come into the enterprise from the front door. As we heard them yesterday. I'm John Frey with Dave Volante, wiki.org. And we're here with Jack Norris, our cube alumni, and a favorite guest here. You're a in charge executive at map. Our, you guys are leading the charge with this use of a dupe. Welcome back to the cube. Thank you. Okay, so what's, let's chat about what's going on. What's your take on all the big news out here for the distributions. I'll the big power moose. You guys have a relationship with EMC. Okay. Exclusive relationship with those guys. Intel's got a distribution Horton versus with Microsoft, a lot of things going on. So this is your wheelhouse. So what's your take on the Hadoop action here? >>Well, I think there's an article in Forbes where I think they, they said it best. This is showing that map bars had the right strategy all along. And what we're seeing is, is basically there's a fairly low bar to taking a patchy Hadoop and providing a distribution. And so we're seeing a lot of new entrance in the market and there's, there's a lot of options. If you want to try Hadoop and experiment and get started. And then there's production class Hadoop, which includes enterprise data protection, snapshots mirrors, ability to integrate. And that's basically map R so start and test and dev with, with a lot of options and then move into production, class >>Mapbox. So break it down for the folks out there who are tipping the toe in the water and hearing all the noise. Cause it's right now, the noise level is very high, right? With the, with the recent announcements. But you guys have been doing business obviously for many years in this area. So when people say, Hey, I want to get a Hadoop distribution with enterprise. What, what should they be looking for? Okay. Because it's not that easy to kind of swing through the noise. So could you share with the folks out there, what, what to look for in like the, the table stakes, the check boxes? Cause there's a lot of claims. There's a lot of noise is this. And that is a lot of different options. Some teams have more committers or no committers than others, so that's all noise, but let's what are the key things that customers need to know? So I think there's, miling, >>There's three areas. All right. One is kind of how it integrates into your enterprise. And with Hadoop, you have the Hadoop distributed file system API. That's how you interact. Well, if you're able to also use standard tools that can use standard file and database access, it makes it much, much easier. So map ours unique and supporting NFS and making that happen. That's a, that's a big difference. The second is on dependability and there's high availability capabilities and then there's data protection. So I'll focus on snapshots as an example, you've got data replicated and Hindu. That's great. But if you have a user error, an application error, that's replicated just as quickly. So having the ability to recover and double-edged in time. Yeah. So if I can say, Hey, I made a mistake. Can I go back two minutes earlier with snapshots that makes it possible map ours, unique and snapshot support. And then finally, there's there's disaster recovery mirroring where you can go across clusters, mirror, what's going on across the land and being able to recover in the case of a disaster where you lose a whole cluster or use a whole >>Section and that's not available in >>Other, those aren't available either. That's >>NFS, >>Snapshots has been on the JIRA list for over five years. >>Yeah. Okay. So I wonder >>If I could find that and then there's third. Cause I said three and almost said two, the third is performance and scale and, but >>That'd be for >>Integration, dependability and speed. >>Okay. So dependability Jr's part of the VR snapshots. MDR. Okay. So let's talk about the performance because you guys had asked a Google's a big partner of you guys. So we should, we just had them on the cube strata. So you have to have a record setting. Do you have a record setting? EMC take that. Well, you work with DMC. So let me talk about the performance real quick. Then we'll talk about some of the EMC conversations, but performance, you have a variety of diverse performance benchmarks, Google you have within the enterprise. Can you talk about those? >>So, so what we announced this week was the minute sort world record. So minutes or runs across technologies is just, how can you, you know, how much data can you sort in 60 seconds? And if you look back at, at the previous record that was done in the labs with Microsoft with special purpose software, and they did 1.4 terabytes Hadoop hasn't been used since 2009, it's been several years because it's got features in there that work against performance. Things like checkpointing and logging because it assumes you've got long running MapReduce jobs. So we set the record with our distribution of Hadoop. So we have kind of one hand tied behind our back, given that technology. Secondly, we sent it in the cloud, which is the other hand tied behind our back because it's a, it's a virtualized environment. So we set the record with just with your legs And a 1.5 terabytes in 60 seconds. Very proud of that. >>Well, that's interesting because we've been doing a lot of labs testing, Dave and I and our teams on cost. Right. So, yeah. And it's an interesting benchmark because you always don't look at the nuance, the cost to compare a cloud performance versus bare metal. Most people don't factor into setup, cost of deployment. Exactly. So can you just quickly talk about that and how significant of an order of magnitude of your customer? >>So the, the previous Hadoop record took 3,400 servers about 27,000 cores, 13, 13,000, almost 14,000 discs and did 600 gigs, actually a little less than that at 5 78. And on Google, we did it with 2020 100 virtual instances, 8,000 cores did 1.5 terabytes >>And costs. You spin up the Google versus >>Basically if you look at that and you assume conservatively 4,000 per server, it's $13.8 million worth of hardware previously. And the cost to do that run on Google was $20 and 33 cents. >>Well, you got to discount. I mean, come on a partner mean it really costs that much. I mean, they that's what they would charge for it. Actually >>We are map artist's case on that minute. If you look at the Asheville charges to be 1200, >>Okay. It's not six millions, so millions to thousands. Yep. Okay. That's impressive. We'll have to go look at the numbers. Like we're going to look at GreenPlum's numbers in the next couple of weeks when talking about the Google relationship and men were that the up way with that was that >>Very excited about it. We're actually deployed throughout the cloud. We've got multiple partners Google's in limited preview. So we've got a number of customers kind of, you know, testing that and, and doing some really interesting things. >>So we monitor the data center market. I'll see with our proprietary tool that you know about the viewfinder and crowd spots and thing is that the data center verticals interesting, right? If you look at the sentiment analysis of what the conversation is on, on just the Twitter data, it's Facebook, apple, these companies. And when we dig into the numbers, it's not so much the companies, it's the fact that their data center operations are significantly being looked at as the leading indicator for where CEO's are going. So I want to ask you in your conversations with your customers, what are the conversations around moving to the cloud and where are they on that transition? Because we hear, yeah, one of the cloud for all the benefits you were mentioning, but Google and Facebook, these are the gold standards as, as architecture necessarily a cut and paste architecture, but they see the benefits that they're doing. So what are your conversations with your enterprise customers around the cloud cloud architecture and what other features besides replication and disaster recovery, are they, are they looking at >>Well, it's basically work, workload driven and dataset driven. So data that's already in the cloud are kind of a natural first step is, well, why don't I do the analysis there as well? So things like Google earth and digital advertising data, that's real interesting candidates for that also periodic workload. So if they have workloads that need to spin up and spin down, the, the cloud works, works really well for that. And in some cases it's driven by their own environments. They've got data centers that are approaching capacity and they need to kind of do offloads and then looking at the, at the cloud because it's easy to get up running quickly and uses an alternative. >>I want to do come back to one of your three sort of value props here, particularly the dependability piece and specifically the snapshot. So somebody asked me one time, how do you know a couple of years ago, how do you back up a petabyte as he could do this thing? And then his answer was, well, you don't know. So I want to, I want to ask you how your customers are protecting and, and, and, and what you guys are bringing to the table. >>So snapshots is not a bolt on feature. It's basically a low level feature based on the underlying data architecture. So when we architected that from the beginning, snapshots was, was a, was a core feature. And if you use a technique called redirect on, right, you're not copying the data, right? So you can do efficient, you can do a petabyte snapshot, you know, basically almost instantaneously because you're tracking the pointers of the latest blocks that have been written. So if, if the data change rate is, is basically, data's not changing, you can snapshot every minute and not have any additional storage overhead. >>Right. Okay. And, and so you can set that. So you, you map, map, our technologies will allow them to set that, dial that up, dial it down and switches. >>So we support logical volumes. So you can set policies at that volume and you can say, well, this volume is critical data. And then I can set policies. Well, critical data is every minute. And then I can change what the definition of critical data is. Maybe it's every five minutes, et cetera. So you can set up these different policies at volumes and have snapshots happen independently for each. >>Can you do that by workload or dataset or by application or whatever I get essentially provided as a service, as opposed to kind of a one size fits all approach. >>Exactly. And that, that also corresponds to user access, administrative privileges, you know, other features and policies within the, within the cluster. >>How about the, you know, this whole trend toward bringing SQL into, into Hadoop. What's, what's your take on that? And what's your angle? >>So interactive, SQL's an important aspect because you've got so many people trained in the organization and, and leverage, you know, sequel, but it's one of many use cases that needs to run across a big data platform. So there's a range of big data analytics, batch analytics, interactive capabilities with sequel, database operations, no sequel search streaming, all those are kind of functions that need to run across a platform. So it's a piece, but it's not the big driver, because what we've seen is that there's higher rival rate of machine generated data and machine generated response to respond to those for digital advertising, for recommendation engines for fraud detection can really move the needle for an organization, have huge swings and profitability >>And the ball down the field big time. Yeah. And >>Having an interactive piece with a kind of a human element involved, it doesn't really scale and work on a 24 by seven basis. >>Jack final question, we're over now by a minute. But when I ask a one party question, obviously, very competitive landscape right now in terms of competitiveness, the stakes are higher because the demand in the market market opportunities is massive. What's map ours business strategy going forward, no change in direction. Is it going to be same old, same old. You guys have any new things going down and you see the marketplace. >>We've got a huge lead when it comes to kind of mission critical enterprise grade features. And our focus is one platform. So the ability to support enterprise Hadoop, enterprise HBase and provide those full capabilities for ease of use for dependability, for performance. And, you know, we've seen a lot of companies test on one distribution and switch to map are and will continue to help that in the future. >>Well, we, we will, we will say we've been covering this big data space now going on four years now, Dave and I, and we've watched all the players pivot a few times. You guys have not, you guys have been true to your mission from day one and that we know where you stand. No one, everyone knows where you stand enterprise grade. It's a good strategy. I think everyone's putting that on their label now. So enterprise grade Washington, we call it a congratulations map art and said the cube. We'll be right back with our next guest here on day three wall-to-wall coverage at O'Reilly media. When do our news, our next from 12 to one, we'll be right back after this short break.