>>Hello, welcome to the Cube here in Palo Alto, California. We're here for a preview of Ansible Fest 2022 this year in Chicago, in Person. And I'm here with Andreas. I've been on Craus, who's a senior manager for Ansible Technical Marketing at Red Hat. And just great to see you Cube alumni. Thanks for coming on and giving us a preview of what to expect at Ansible Fest. Thanks. >>No problem. Thanks for having us and thanks for everyone tuning in. >>You know, one of the things that's exciting this year is one, it's back in person from 2019 was the last in person Ansible Fest. Always a great event for folks doing it. Cloud native configuration management and automation, I think, and last year in our virtual event was the three things where automation, automation, automation kind of drove the point home. This year it's, it's more exciting than ever because if you look at the growth of Cloud Native, we're seeing a lot more traction in mainstream enterprises with Kubernetes. And obviously containers continue to grow with open source, powering everything under the coverage. So like this has like become such a whole nother inflection point this year more than ever. There's a focus on not just automation, but where the dots are gonna connect into the future. So I'd like to get your thoughts on what we're gonna expect this year at Ansible Fest. What's the themes? What do you, what do you see coming down the pike? What can people expect, >>People can really expect? Thanks. Thanks very much John. Really excited. So we're gonna see a lot of what we've seen before, right? So a little difference is from the previous onsite Ansel Fest is, I think we no longer have to say, you know, what's Ansible? We typically have had to say, you know, what is this Ansible thing? I don't know what this is. This is automation. I think we've gone beyond that and this is great. Ansible itself is now the defacto, what we believe is the de facto kind of automation language and Ansible automation platform is the defacto automation platform. So as you move into this year, we we're gonna be able to see, be able to really hone in on really having those beginners starting off much, much more quickly. But also those that have no and love Ansible for over the years to take that automation to the next level to, to new areas. Either new domains going beyond the data center, into the cloud, and then going beyond by all the partner certifications, integrations that we have. So it's a lot, it's just more of, of everything I think. So it's more for everyone all the time. So it's not, it's you, it's, it's no longer kind of a beginner's for everything, but we go all the way to kind of crawl, walk, run for this one. >>You know, it always surprises me every year, I'm always surprised by how great open source I remember every year. It's like, pinch me, This is amazing. If you're a developer right now, it's a good time to be coding because of open source growth is, is at an all time high, continues to grow, more projects are emerging. DevOps, which really came out of the ethos of the kind of the early days of the cloud and, and and scaling infrastructure was, was about infrastructure as code, which was the dream we all had in the late two thousands. If you remember right now that's happened. DevOps is now in the C I C D pipeline. Developers are shifting. Left cloud native hybrid actually now is a steady state and that's pretty well documented. What, what's next beyond infrastructures code? What's beyond the on premise cloud integration from a, from a, from a tech standpoint, what are you guys seeing around infrastructures, code, what's next and then what's beyond on premise? >>I think the big thing is scale, right? So we've always been able to kind of automate people, developers, as you said, DevOps, you can automate from your laptop, you can open up your laptop, download some open source Ansible and you know, automate your windows, your Linux, your network, no problem. But how do you actually operationalize that in an enterprise way across large teams, right? A global environment and then being able to like actually secure that, right? Security is such a big, sp a big piece of that now. So being able to actually apply automation securely in secure environments. So, and wrap all of that around cloud, right? So we've always been talking about a, you, you mentioned it on premises going into the cloud, right? So being able to operationalize in the cloud. So being able to automate cloud targets. So being able to automate aws, Azure GCP targets, but also running your automation on the cloud like say OpenShift. So being able to dynamically load load balance, create execution on demand for Ansible in OpenShift. So it's kind of hard and we, we hope that an Ansible fest will be able to kind of like demystify that from like when you hear, when you hear the word cloud and, and cloud native and hybrid cloud, it kind of goes in your head. We hope to kind of clear that up for folks at, at the fest. >>Certainly we're gonna talk about Super Cloud as well with the cube there. I wanna hear your thoughts real quick on the edge. You know, we gonna hear anything about the edge. This, this year, again, Edge has become hugely important, but yet it's not clear to a lot of people what that looks like. Are we gonna hear anything there? >>Absolutely. Edges is huge. And to some people I will say that when, when you say edge automation, it may not click to some folks, but if you were to say automating wireless access points in a branch office, you thinking, oh, okay, I can't now I know what you're talking about. Right? So a lot of people really may not have made the connection to what Edge Automation is because we, you know, maybe that hasn't been defined. And as we start moving into edge automation, we can start talking about extending, right? We're already talking about extending the data center, especially for network automation. So network automation no longer is in data center. You can now extend that out to the branch office to campus Wireless, right? And you can also extend that out into other areas such as industrial applications, right? If you wanna move a glue gun from one end of the warehouse to the other, you know, that has to be automated and we'll be able to be able to do that by means of some of the enhancements we made for that. >>What can customers and attendees who are gonna be there either in person and after remote hybrid expect us hear about Ansible's automation platform this year? What's gonna be some of the announcements? Can you tease a little bit out on what >>I can tease a little bit? Yeah. You know, day one's gonna be more of making me upleveling what you have today. I think you're gonna see some of the, the futures, right? A lot of the things around Edge, you'll hear something called event driven automation. So you, this is, this is very akin to maybe self-driving or self-healing or, you know, being able to automatically say event is triggered and then you can actually cause some automation to be spun up to actually remediate those things. So going beyond observability, right? Observability is great, but just observing problems is, is, you know, I can look at a million things wrong in my network, but if they're not being remediated, you know, it doesn't really mean much. So, you know, talking about event driven there is gonna be really hot. And then a lot of the other use cases in frameworks, you know, going beyond the configuration, I think, yeah, >>I think they develop things. Cool. And, and final question for you, because one of the things that last year we came away with was automation. What's that next automation at scale. Because remember, you know, we remember where we came from writing scripts, automating things from just basic scripting and, and configuration automation to full scale automation. That's become a big part and we see a lot of that in the cloud. Native conversations with containers and whatnot. How do you scale at, at, at, in the cloud with the cloud na hyperscalers. So again, the relationship with the hyperscalers and scale, what can we expect to hear there? >>Oh, everything from, so we'll be teasing out a little bit. You, you know that we have Ansible automation platform on Azure as a marketplace offering. We may be extending that to maybe some other hyperscalers. So making it super easy for customers or prospects to get automating quickly in their hyperscaler of choice, using their own means and, and, and methods and processes. And then going beyond that and ensuring security. So I mess in security again, how do you ensure that what you're in, what you're actually automating is part of like a security supply chain is part of your content or part of your playbooks and keeping things actually running well at scale, like you said, >>Okay, you got Azure, I'll put, I'll put my guessing hat on. There's only a few others in the pull from. That's awesome. Congratulations. And looking forward to the event, final word here. What's, what's, what do you see outcome at the end of the event? What's gonna, what's in your mind's eye? What's the, what's the outcome look like? >>Yeah, I, I just gotta do a shameless plug. I'm actually running the labs and workshops. So if you're in person or if you're not, you know, come check out the labs and workshops. We have four rooms. You can just camp out and just do hands on learning with workshop instructor led learnings or self-paced training. You can see me and all that. But I think the future learnings here is really trying to futureproof everyone's use cases. So actually, you know, you talk about ai, you talk about Cloud native, talking about other Red Hat products being, being part of that conversation with re and OpenShift, it's really a great time to, to be automating right now. >>And it's interesting. And the Ansible community that's well, well known. They all know each other and it's, it, I won't say niche, it's not niche anymore. It used to be one of those areas where super important for making things run now we need to take cloud and cloud scale. Horizontal scalability across multiple environments is kind of an Ansible thing, right? It's like you need to think about how to scale the Ansible concept. And I think that's the big exciting thing that I see with Cloud Native Andrews is this idea that, you know, what Ansible stood for back then now applies to almost all environments. So the automation, the scaling of, of, of configurations and tearing stuff down and standing things up with machines and software is just, I think, an incredible opportunity. And I think it operations is now in the developer's hands and data and security ops are front and center in, in all these conversations. And it's gonna be super exciting. Can't wait to, can't wait to hear. Okay. Thanks for coming on. I really appreciate it. Thanks for, for giving your opinion. >>All right. I appreciate it. Thank you very much for hosting us. See you and we'll see you there in Chicago. >>Okay. Andrew's been a creative senior manager and it's potential marketing to breaking it down, getting the preview on what's coming, expect to hear more about automation and how it's relevant at scale and, and all new things are happening with cloud native inflection point. We're living right now. So we'll see you there. Thanks for watching.

>>live from Atlanta, Georgia. It's the Q covering Answerable Fest 2019. Brought to you by >>Red Hat. >>Okay, welcome back. It runs two cubes. Live coverage of Ansel Fest here in Atlanta, Georgia. I'm John for a host of the Cube with stewed Minutemen. Analysts were looking angle. The Cube are next to guest Tom Anderson and most product owner. Red Hat is part of the sensible platform automation properly announced. And Richard Henshaw, product manager. Guys, welcome to the Cube Way had all the execs on yesterday and some customers all pretty jazzed up about this year, mainly around just the timing of how automation is really hitting the scene and some of the scale that's going on. You guys had big news with the answerable automation platform. New addition to the portfolio. What's the feedback? >>So far, I think the feedback has been super positive. We have customers have come to us. A lot of the last little one said, Hey, we're maturing. We're moving along the automation maturity curve, right, and we have multiple teams coming to us and saying, Hey, can you help us connect this other team? We've had a lot of success doing cloud provisioning or doing network automation were doing security automation. What have you and they're coming to us and saying, Help us give us kind of the story if you will, to be able to connect these other teams in our organization. And so that way I kind of feel the pole for this thing to move from a tool that automates this or that. This task for that task. Too much more of a platform center. >>It seems to be scaling out in terms of what automation is touching these days. And look at the numbers six million plus activations on get Hub versus other projects. So activities high in the community. But this seems to be much more broader. Scope now. Bring more things together. What's the rationale behind? What's the reasoning? What's the strategy? But the main thing is, >>automation is got to that point where it's becoming the skill set that we do. So it was always the focus. You know, I'm a database administrator. I'm assists out, man. I'm a middle where I'm a nap deaf on those people, then would do task inside their job. But now we're going to the point off, actually, anybody that can see apiece. Technology can automate piece technology in the clouds have shown This is the way to go forward with the things what we had. We bring that not just in places where it's being created from scratch, a new How do you bring that into what's existing? Because a lot of our customers have 20 or 30 years like a heritage in the I T estate. How do you do with all of that? You can't just rebuild everything into new as well. So you gotta be ableto automate across both of those areas and try and keep. You know, we say it's administrative efficiency versus organization effectiveness. Now how do I get to the point of the organization? Could be effective, supposed just doing things that make my job easier. And that's what we're gonna bring with applying automation capability that anybody can take advantage of. >>Richard. I actually felt the keynote demo this morning did a nice job of that line that they set it up with is this is this is tools that that all the various roles and teams just get it, and it's not the old traditional okay, I do my piece and set it up and then throw it over the wall. There was that, you know? Oh, I've got the notification and then some feedback loops and, you know, we huddled for something and it gets done rather fast, not magic. It's still when I get a certain piece done. Okay, I need to wait for it's actually be up and running, but you know, you're getting everybody into really a enterprise collaboration, almost with the tool driving those activities together >>on that. And that's why yesterday said that focus on collaboration is the great thing. All teams need to do that to be more successful because you get Maur inclusivity, Maurin puts. But organizations also need to coordinate what activities they're doing because they have rules, regulations, structures and standards they have to apply. Make sure that those people can do things in a way that's guided for them so that they're they're effective at what they're trying to do. >>Okay, I think I'm going to explain what's in the platform first because an engine and tower and there, what else is in there, what's new? What's what our customers is going to see. That's new. That's different >>it's the new components are automation Hope Collections, which is a technology inside answer ball itself. On also Automation Analytics and the casing is that engine and terrorist of the beating heart of the platform. But it's about building the body around the outside. So automation is about discover abilities like, What can we find out? What automation can I do that I'm allowed to do? Um, and let six is about the post activity. So I've automated all these things. I've done all this work well, How did it go? Who did what, who did? How much of what? How well did it work? How much did it failed? Succeeds and then, once you build on that, you don't start to expand out into other areas. So what? KP eyes, How much of what I do is automated versus no automated? You can start to instigate other aspects of business change, then Gamification amongst teams. Who's the Who's the boat? The closest motive here into the strategy input source toe How? >>Find out what's working right, essentially and sharing mechanism to for other groups in terms of knowing what's happening >>and how is my platform performing which areas are performing well, which airs might not be performing well. And then, as we move down the road, kind of how my performing against my peers are other organizations that are automating using the ants will automation platform doing? And am I keeping up on my doing better? That kind of stuff. >>So, Tom, there's a robust community as we was talking about. Their platform feels like it builds on yet to change the dynamic a little bit. When you talk about the automation hub and collections, you've already got a long list of the ecosystem vendors that are participating here. Bring us two through a little bit. What led Thio. You know all these announcements and where you expect, you know, how would this change the dynamics of >>the body? And maybe we'll split up that question. I'll talk a little bit about partners because it's both partners and customers in community here that's been driving us this way. I'll talk a little bit about partners and Rich talk about the customer piece here, which is partners have been traditionally distributing their content there. Ansel automation content through our engine capability. So our engine release cycle, or cadence, has been sort of the limiting factor to how fast they can get content out to their users and what what the collections does is part of the platforms allows us to separate those things. Rich talked about it yesterday in his keynote, having that stable platform. But you having yet having content be able to read fast. And our partners love that idea because they can content. They can develop content, create content, get into their users hands faster. So partners like at five and Microsoft you've seen on stage here are both huge contributors. And they've been part of the pole for us to get to the platform >>from a customer perspective. And the thing I love most about doing this job with the gas of customers is because I was a customer on Guy was danceable customer, and then I came over to this side on Dhe. I now go and see customers. I see what they've done, and I know what that's what I want to do. Or that's what I was trying to do. And she started to see those what people wanted to achieve, and I was said yesterday it is moving away from should I automate. How would we automate Maura? What should I automate? And so we'll start to see how customers are building their capabilities. And there's no there's many different ways people do. This is about different customers, >>you know. What's interesting is you guys have such a great success formula first. Well, congratulations. It's great to see how this is turning into such a wider market, because is not just the niche configuration management. More automation become with cloud to point a whole new wider category. So congratulations. The formula we see with success is good product, community customers adopting and then ecosystem that seems to be the successful former in these kinds of growth growth waves you guys experiencing? What is the partnering with you mentioned? S five Microsoft? Because that, to me, is gonna be a tipping point in a tel sign for you guys because you got the community. You got the customers that check check ecosystem. What's the partner angle? How do they involve? Take us through that. What's going on? They're >>so you're absolutely so you know, kind of platform velocity will be driven by partner adoption and how many things customers can automate on that platform or through that platform and for us I mean, the example was in the demo this morning where they went to the automation hub and they pulled down the F five collection, plugged it into a workflow, and they were automating. What are partners? Experience through their customers is Look, if I'm a customer, I have a multi cloud environment or hybrid cloud environment. I've got automation from AWS. I've got azure automation via more automation. Five. Got Sisko. I've got Palo Alto. I've got all these different automation tools to try and string them together, and the customers are coming and telling those vendors Look, we don't want to use your automation to end this automation tooling that one we want to use Ansel is the common substrate if you will automation substrate across this platform. So that's motivating the partners to come to us and say, Hey, I had I was out five Aspire last week, and they're all in a natural. I mean, it's really impressive to see just how much there in unanswerable and how much they're being driven by their customers when they do Ansell workshops without five, they say the attendance is amazing so they're being pulled by their customers and therefore the partners are coming to us. And that's driving our platform kind of usability across the across the scale. >>Another angle we'll see when we talk to the engineers of the partners that are actually doing the work to work with danceable is that they're seeing is ah, change also in how they it's no longer like an individual customer side individual day center because everything is so much more open and so much more visible. You know there's value in there, making it appealing and easy for their customers to gain advantage of what they're doing. And also the fact that the scales across those customers as well because they have their internal team's doing it, saying the same things and so bringing them to an automation capable, like Ansel have to push. That means that they also gained some of the customers appreciation for them, making it easier to do their tasking collaboration with us and you know, the best collaborations. We've got some more partners, all initiated by customers, saying Hey, I want you to go and get danceable content, >>the customer driving a lot of behavior, the guest system. Correct. On the just another point, we've been hearing a lot of security side separate sector, but cyber security. A lot of customers are building teams internally, Dev teams building their own stacks and then telling the suppliers a support my AP eyes. So now you start to see more of a P I integration point. Is that something that is gonna be something that you guys gonna be doubling down on? What's that? What's the approach there? How does that partner connected scale with the customers? So we've >>been eso Ansel security automation, which is the automation connecting I. P. S. C. P. S that kind of stuff. It is almost a replay of what we did the network automation space. So we saw a need in the network automation space. We feel that we became a catalyst in the community with our partners and our customers and our and our contributors. And after about three years now, Ansel Network automation is a huge piece of our business and adoption curve. We're doing the exactly see the exact same thing in the security automation space compliance. The side over here, we're talking about kind of automating the connections between your firewalls, your threat detection systems and all that kind of stuff. So we're working with a set of partners, whether it's Cisco, whether it's Palo Alto, whether it's whether it's resilient by the EMS, resilient and being able to connect and automate the connections between the threat and the response and and all of that kind of >>the same trajectory as the network automation >>Zach. Same trajectory, just runnin the same play and it's working out right now. We're on that kind of early part of that curve, that adoption curve, and we have partners jumping in with us. >>You're talking to customers. We've heard certain stories. You know how I got, you know, 1000 hours of work down to a dozen hours of work there. Is there anything built into the tool today that allows them to kind of generate those those hero stats O. R. Any anything along those lines? >>Talk about analytic committee from yes, >>well, again without any analytic side. I mean, those things starts become possible that one of the things we've been doing is turning on Maur more metrics. And it's actually about mining the data for the customer because Tower gives this great focal point for all the automation that's going on. It's somewhere that everything comes through. So when we export that and then we can we can do that work for all the customers rather than have to duel themselves. Then you start to build those pictures and we start with a few different areas. But as we advance with those and start, see how people use them and start having that conversation customers about what data they want to use and how they want to use it, I think that's gonna be very possible. You know, it's so >>important. E think was laid out here nicely. That automation goes from a tactical solution to more strategic, but more and more how customers can leverage that data and be data driven. That's that's gonna drive them for it. And any good customer examples you have of the outcomes. No, you're talking to a lot of >>PS one from this morning. Yeah, >>so I mean, I'll be Esther up this morning, and I think that the numbers they used in the demo that she's like, you know, last year they did 100,000 from launch to the end of the year. 100,000 changes through their platform on this year so far that in a 1,000,000. So now you know, from my recollection, that's about the same time frame on either side of the year. So that's a pretty impressive acceleration. Side of things. We've had other ones where people have said, You know how many times you were telling some customers yesterday? What used to take eight hours to a D R test with 20 or 30 people in for the weekend now takes 12 minutes for two People on the base is just pushing a few buttons just as they go through and confirm everything worked that that type of you can't get away from that type of change. >>J. P. Morgan example yesterday was pretty compelling. I mean, time savings and people are, I mean, this legit times. I mean, we're talking serious order of magnitude, time savings. So that's awesome. Then I want to ask you guys, Next is we're seeing another pattern in the market where amongst your customer base, where it's the same problem being automated, allover the place so playbooks become kind of key as that starts to happen is that where the insights kind of comes in? Can you help us kind of tie that together? Because if I'm a large enterprise with its I'm decentralized or centralized, are organized problem getting more gear? I'm getting more clouds, game or operations. There's more surface area of stuff and certainly five g I ot is coming around the corner. Mention security. All this is expanding to be much more touchpoints. Automation seems to be the killer app for this automation, those mundane task, but also identifying new things, right? Can you guys comment on that? >>Yeah, so maybe I'll start rich. You could jump in, which is a little bit around, uh, particularly those large accounts where you have these different disparate teams taking a approach to automate something, using Ansel and then be able to repeat or reuse that somewhere else. The organization. So that idea of being for them to be able to curate they're automation content that they've created. Maybe they pulled something down from galaxy. Maybe they've got something from our automation husband. They've made it their own, and now they want to curate that and spread it across the organization to either obviously become more efficient, but also in four standards. That's where automation hub is going to come into play here. Not only will it be a repo for certify content from us and our partners, but it will also be an opportunity for them to curate their own content and share it across the organization. >>Yeah, I think when you tie those two things together and you've got that call discover abilities, I had away go and find what I want. And then the next day, the next day, after you've run the automation, you then got the nerve to say, Well, who's who's using the right corporate approved rolls? Who's using the same set of rolls from the team that builds the standards to make sure you're gonna compliant build again, showing the demo That's just admin has his way of doing it, puts the security baseline application on top and you go, Oh, okay, who's running that security baseline continuously every time. So you can both imposed the the security standards in the way the build works. But you can also validate that everybody is actually doing the security standards. >>You what I find fascinating about what you guys are doing, and I think this is came out clearly yesterday and you guys are talking about it. And some of the community conversations is a social construct here. Going on is that there's a cultural shift where the benefits that you guys are throwing off with the automation is creating a network effect within the companies. So it's not just having a slack channel on texting. The servers are up or down. It's much more of a tighter bond between the stakeholders inside the company's. Because you have people from different geography is you have champions driving change. And there's some solidarity happening between the groups of people, whether they're silo door decentralized. So there's a whole new social network, almost a cultural shift that's happening with the standardization of the substrate. Can you guys comment on this dynamic? Did you see this coming? You planning forward? Are you doubling down on it? >>I think so. And we talk about community right on how important that is. But how did you create that community internally and so ask balls like the catalyst so most teams don't actually need to understand in their current day jobs. Get on all the Dev ops, focus tools or the next generation. Then you bring answer because they want to automate, and suddenly they go. Okay, Now I need to understand source control, and it's honest and version. I need to understand how to get pulls a full request on this and so on and so forth on it changes that provides this off. The catalyst for them to focus on what changed they have to make about how they work, because what they wanted to do was something that requires them to do you no good disciplines and good behaviors that previously there was no motivation or need to do. I think >>Bart for Microsoft hit on that yesterday. You know, if you saw Bart Session but their network engineers having to get familiar with concepts of using automation almost like software development, life cycles right and starting to manage those things in repose. And think of it that way, which is intimidating at first for people who are not used to. But once they're over that kind of humping understand that the answer language itself is simple, and our operations person admin can use it. No problem, >>he said himself. Didn't my network engineers have become network developers. >>It's funny watching and talking to a bunch of customers. They all have their automation journey that they're going through. And I hear the Gamification I'm like, Okay, what if I have certain levels I have to reach in it unlocked capabilities, you know, in the community along the way. Maybe that could build a built in the future. >>Maybe it's swag based, you know, you >>get level C shows that nice work environment when you're not talking about the server's down on some slack channel when you're actually focusing on work. Yeah, so that mean that's the shift. That's what I'm saying, going >>firefighting to being able to >>do for throwing bombs. Yeah, wars. And the guy was going through this >>myself. Now you start a lot of the different team to the deaf teams and the ops teams. And I say it would be nice if these teams don't have to talk to complain about something that hadn't worked. It was Mexican figured it was just like I just like to talk to you because you're my friend. My colleague and I'd like to have a chat because everything's working because it's all automated, so it's consistent. It's repeatable. That's a nice, nice way. It can change the way that people get to interact because it's no longer only phoned me up when something's wrong. I think that absent an interesting dynamic >>on our survey, our customer base in our community before things one of the four things that came up was happier employees. Because if they're getting stuff done and more efficient, they have more time to actually self actualizing their job. That becomes an interesting It's not just a checkbox in some HR manual actually really impact. >>And I kind of think the customers we've heard talk rvs, gentlemen, this morning gave me a lot of the fear initially is, well, I automate myself out of a job, and what we've heard from everybody is that's not absolutely That's not actually true at all. It just allows them to do higher value things that, um or pro >>after that big data, that automation thing. That's ridiculous. >>I didn't use it yesterday. My little Joe Comet with that is when I tried to explain to my father what I do. Andi just said Well, in the 19 seventies, they said that computers you mean we'll do a two day week on? That hasn't come >>true. Trade your beeper and for a phone full of pots. But Richard, Thanks for coming on. Thanks for unpacking the ants. Full automation platforms with features. Congratulations. Great to see the progress. Thank you, Jonah. Everybody will be following you guys to Cuba. Coverage here in Atlanta, First Amendment Stevens for day two of cube coverage after this short break.

>>live from Atlanta, Georgia. It's the Q covering answerable best 2019. Brought to you by Red hat. >>Hey, welcome back to the Cuban Live coverage in simple fest. Two days of coverage. Day one, wrapping up. I'm John forwards. Accused Too many men. My guest co host today, our next two guests at his van. Van Velzen. Okay, welcome to the Cube. You're an engineer at I n G Bank and Robert de Bock, product owner, engineer I n g. Bank. Hey, guys, Thanks for coming on. Thank you. Have the practitioner on. Well, first of all, we have a lot of great feedback from the practitioners here. And also people in deploying answerable and other other cool Dev ops Tools on automation is at the top of the list. Yes, More efficient. Getting things done. Focus. You got satisfaction in job because things go awaiting time savings. I'm saving security drives a conversation and re skilling opportunities. Love. These are cutting edge. Things you got to do is take a minute to explain what you guys do. What a night. What a night. Angie bank. >>Yeah. I work in a team that provides redhead images for other teams. in 90 to consume to use two insane she ate way. Also live from playbooks, amendable code and rolls to manage those things. And he's very scattered, which sort of decentralized, which is a good thing. In my opinion, it's ready for scaling. In that case, I used to work with Dennis are lots in the tower team, so take it away. >>Okay, so I still work at the answer, built our squad What we do, it's ah, We make sure that the instable tower service keeps running 24 7 and we also ensure that we, uh, provide updates next to all this. We also have unanswerable community where we basically support our end users, which are their love. So, uh, from some numbers, I heard we have 1200 applications teams that are using our service. Um, and they all have, like, answerable playbook, sensible rolls, questions, difficulties with, uh, with anything. And we're basically there to support them as well. >>So 1200 teams are using answerable, Yes, inside the bank. Yes. Yeah, like >>it's set up very decentralized. And I think what I hear from instable fest that is not very common. I still think it's very good thing to do. We try to basically give these teams all the tools they need to do their stuff on. What I hear hear mostly is that there's essential team off administrators pushing the buttons for them. Towers. Great answer was great in that case, I think, for our case is really it's a perfect fit. >>E guess help Explain. Is this do you provide? You know, he said it's not centralized, but is this you know, here's best practices here. Some play boat out. How do you end? You support them? Because they're a little bit those relationships. >>Okay. Okay. Um so what we do is we basically all the rules and get ah ah, good lap. So it's an own premise. Get environment. You can search in this. Get for rules. Uh, not like all rules are easily to be found when searching for them. So that's why there are these communities to share what you have made. Um, >>plus these teams, they can themselves pick and choose. Some will try to rewrite everything That's fine. Others can can benefit from existing coat, so it's just a good trick. Thio enable these team to participate on it really different. Some people make it all themselves another >>next to this. So we basically have these 12 on the teams do their own thing. But next to this, we also have a self service portal where they can choose, like from, uh, generic finks like us. But your machine at new disc. So New capacity Cp use memory. That's all being done through a portal s so they don't need to do anything on their own for this they can, but most of them choose the easy way off using this portal. This portal basically doesn't a vehicle to instable tower, which executes a sensible playbook and some other stuffs. Maybe some AP eyes. And this is one of the things you guys create A manage these books. So, um >>and if you go back in time so the alternative way, which we happily got rid off, is to do it ourselves. I think it was before we we work together. Way had batch weekends, for example, and it >>was no very different. No life. Oh, that's working on weekends, >>weekends and, for example, he used to patch machine some 10,000 or so, and we were not aware what was important. What? Not so you you'd stop the whole pitch. Oh, this machine has a problem. Let's stop everything in focus and that's >>not important. Was like a complete order. >>And the other way around Also this machine. I guess it's not that important. Let's just >>continue this >>Sunday morning. Oh, my God. Everything's broken. >>Can you give us a little flavor of kind of the spectrum of solutions that you leverage answerable on >>tap? Yeah. We, uh I think what we see Moses for Lennox machines, eso fetching is a big one. We got a second operation, so there's a few of them. The deployment also depends on and small. So if you order a new machine, answer was involved somewhere to do to make it happen on network on board and the Windows teams are very interested. I'm not sure if we notice on board yet. To >>be honest, I know we did some book in the boss so a couple of months ago, using wind around when you needed set on policies there, But you can see that the networking teams were getting more momentum. Uh, five. There's some suffer suffer to find switches Bob. I don't know. The, uh Never mind the name, but ah, you can see some momentum in the in the networking. Uh, it's not Morgan departments >>configuration network networking with the activists. So that's where the action is in the >>network. Um, there were some cool talks also here on five workshops. So you can see there is, um, that there is some attention on these modules and integrations as well. >>What's your guy's goal here for the show? What brought you here? I'll see Big user. >>Yeah. So what do you think was like sharing our own thing? We did. They talk this morning. Ah, regarding and programming A really cool we wanted to share. It is this behavioral thing, and and >>we'll talk about take a minute and programming. >>So, um, basically, it's, ah programming with the whole team and making sure that you get something done with all the knowledge in the team. So you don't have to align off the words or if some other if you're Kulik says from basically session, you can do better using this staying. It's all, um it's It's all done during the decision >>as basically a good way to get a team up to speed. So in a team that's probably a few few people that are very quick and understand the concept and few starters or so So >>you guys decentralized, which makes sense for scale. I get that. So this sounds like you can operate decentralized, but where danceable. You can still have that common a book Switch >>teams, for example. So it used to be very specific. H team would have their own type of coat. Now that more answers used people can switch a little easier to to another product of surface because the languages have lied, shared, steal it, steal. It's quite >>well happy with this, right? I am. I really, really have to work on the weekend. That's good. I think >>the good thing is that you have one generic way of working. So his playbook is readable by all engineers. And if you want to learn this thing, you just do the inevitable course. So you know what this thing is? A mosque and roll, and it's all like >>way. We do see horrible >>koto. Come on, don't throw your college under the bus. But here's the international tough question can see is what we have been here. I want you guys to test this. We hear that there's a lot of time savings involved. Yes, with answer. True or false. That's true order of magnitude. What? What kind of saving way talking about? I >>think it depends on the thing because we saw a huge I don't know, except numbers. But this this os patching that Really? Really Uh, >>yes. Now, especially waas. Two people working a full time basically collecting, who needs to do what? The win. And then for a weekend, 10 15 people or so. So, uh, that's reduced now to sort of nothing. Yes, some maintenance to that playbook and roll. But I mean, yeah, it's difficult to express what message? So >>no one's getting phone call? Hey, come in on the weekend. So 15 people on the weekend jam and then to Fulton will just managing it all Go away. >>Yeah, not needed, but not needed. But they basically they can do something else, so those people are still there. But now they're not doing Os patching and doing all the excel sheets and keeping order off. The systems are important, and this shall be the first, and then they because way are basically doing the thing they know better. This application team knows their dependency, so they know they. But first I need to patch the database machine and then there during the front end or Andi. It's difficult to do this so they do it themselves. >>That's Dev Ops. That's that's the way it's supposed to be, right? >>So you've matured this thes deployments over time. As you look back, What key learnings do you have that maybe you'd recommend to your peers toe? You know how things could run a little bit smoother >>next time, a good amount of time. So they're stools. That's not the problem, So answer is great, but there's others to their great Give it time to sink in with the people. So you start something and you have to have a pretty strong team to do the long the long stretch with it and give it some time, maybe a year or so before everyone's on board it. In our case, in the beginning, we spend lots of time on this community model where we basically organized small meet ups or get together, too, show things or to hear problems and try to express them. That really helped a lot. And by now it's starting to get normal, more normal. So all the teams do sensible, basically. And problem starts slowly disappearing. Also. So So >>one of the things, um, that will be better. Probably in our scenario. Housekeeping metrics. So what are the improvements over time? I don't know how to measure this. No, no, no aspect. But it will be better if you had, like, better numbers like we did hair Very good. Or this is something like, what did the community thing bring way indirectly what the results are Because the engineers are doing things really, really things. They're really patching the replication. And they're really, um, restarting their own machines, for example, when there is something wrong. Whatever. Um, but our days related to our community thing or all that's really related to Sensible Tower >>last. I think we we are very technical focus. So So we like it as a nerd, so to say, to do things but what the business value is, for example, I'm not so interested or less interested so way typically, like the technology, so it could be good to have some someone onboard and your team that says, Yeah, but this is the problem. It's crossed. This amount of money and that solved now are improved. >>Well, they assume the applications are doing a good job. So you guys helped those guys out. They get to do their own thing. They do the heavy lifting. They're doing the coding anyway for those guys that were coming in managing full time on the 15 or so on the weekend. What are they doing now? >>Most are spread across. All the application teams go back. But the other side there is now it's our team that was not there s. So that's the price you have to pay. And that's a serious team. I mean, it's far six people now 86 people and 100 machines or so. So it is a serious amount of time, but it makes it at least much more constant. So people are not surprised by machines being patched, and Monday they come back into the half broken or so. So it's a lot more control now, so I don't know if you can express it in price, but at least it's more stable >>more consistent. >>Well, one of the things that we hear here and I want to get your thoughts as we wrap up is as you go forward, you got answerable 1200 teams using it. You got a lot of collaboration. The work cultures change. Sounds like a shower. Team steps service everything else. So some scale building out what's next? Because as it becomes a platform. Okay, you have to enable something. There has value there. Okay, technical nerd value and then business value >>scaling, uh, because we continuously see this thing growing like more application teams are adapting answerable, invincible tower. So, um, right now we have, like, a cluster. We have different clusters running. Go into much detail, but we can see that the load is getting higher and higher, so we need to skill. Um, and this is sort of difficult, but red. That is really supporting in this because they're going to change some things at the application level two to allow scaling even better. Um, >>plus, also, for most teams, they're starting their configuration. Everything is coat process. They're not there yet. As soon as they discover the power of it, I'm sure that's being used a lot. A lot more. And plus, there's other countries that are going to be connected. So you have a lot of work >>because your engineering doing some getting down and dirty with the code, automating everything. >>Yeah. Yeah. So, um, what else do we >>Oh, what's the coolest thing you've done that you've automated? >>Uh >>uh, Pick your favorite. >>So but the child during Encircle Tower and with answerable, um, let me think about this. >>I I really like the patching that saved us so much work. And, uh, I think also one of the next goes to make much more simpler. So we as a company, we're complex and the people also like complexity. That's wrong. We should change >>that. Patching up our >>offense, Melissa Simplicity. So we should really use that. >>You don't want any open holes in the network housely and assistance >>about your previous question. Like I have sort of a finger and all these small things. So it's sort of what I did. It's more like an A team thing. We created the OS patch playbooks, the configure stuff, the second day offs. So we did this as a team >>like sports but the playbooks together run the play. Some defense on security >>and programming. So you're doing >>this as a team, which is very cool. Has a scoreboard look good? Winning? >>Yeah, Yeah, yeah, yeah. We're looking at the graphite. Uh, it's girl. >>Final question. How you enjoying the show here? Having a good time? What's the vibe here? What's it like here? Share for the people who aren't here. What's going on? What's the vibe with >>a conversation? It's great. We went to some sessions yesterday really technical stuff with developers. And this was really amazing because you heard details that that are not in the India in the talks today and tomorrow. Um, yeah, it's great. It's great community. It's just I really I really enjoy it because you can. It's You can have, like one on one conversations go into depth. I was showing something I created, and this guy's we'll hold. This is really great in the It's cool. It's just if you it's really great. It's really >>cool. Really? Yeah, for me also, it feels like coming home, So I know these people and I think the first day, the collaboration day, what's it called and I'm not sure you community, that's it's great because it's been a bit rough and unpolished in today's more polished and more presented and prepared to, uh, both are great. >>Good. Give the hard feedback. >>Yeah, you meet all the people. So, for example, I used instable a lot, and then I'm getting up. I see all these names. Like, who would that be there walking here and shake hands like, Oh, that's >>why guys like your code looking good. Yeah. Looks good. A contributor. Summit contributed. Okay. Sorry. After it for >>anyone that goes to visit that day, too. That's just great. >>It's great to see people face to face that, you know, online for their digital identity or the code >>you can You can't complain about stuff out on. Do you know that you don't hurt them or something with just commenting on get like after this issue and this issue and this issue. Then you can see them in person. And then you >>him a high five assault, you know? Hey, >>it's really very cool. >>Guys. Great conversations were coming on cue. Thanks, Dennis. Appreciate Robert. Thanks for coming on. Skew coverage here Day one of two days of live coverage here inside the Cube here in Atlanta, Georgia for Ansel Fest is the cute I'm John 1st 2 minute. Thanks for watching.

>>live from Atlanta, Georgia. It's the Q covering answerable Best 2019. Brought to you by Red Hat. >>Welcome back. Everyone keeps live coverage of answerable fast here in Atlanta. Georgia John for my coach do Minutemen were here. Stephanie chairs to the vice president of general manager of the rail business unit. Red Hat. Great to see you. Nice to see you, too. You have all your three year career. IBM now Invincible. Back, Back in the fold. >>Yeah. >>So last time we chatted at Red Hat Summit Rail. Eight. How's it going? What's the update? >>Yeah, so we launched. Related some. It was a huge opportunity for arrested Sort of Show it off to the world. A couple of key things we really wanted to do There was make sure that we showed up the red hat portfolio. It wasn't just a product launch. It was really a portfolio. Lunch feedback so far on relate has been great. We have a lot of adopters on their early. It's still pretty early days. When you think about it, it's been about a little over 445 months. So, um, still early days the feedback has been good. You know it's actually interesting when you run a subscription based software model, because customers can choose to go to eight when they need those features and when they assess those features and they can pick and choose how they go. But we have a lot of folks who have areas of relate that they're testing the feature function off. >>I saw a tweet you had on your Twitter feed 28 years old, still growing up, still cool. >>Yeah, >>I mean 28 years old, The world's an adult now >>know Lennox is running. The enterprise is now, and now it's about how do you bring new innovation in when we launched Relate. We focused really on two sectors. One was, how do we help you run your business more efficiently? And then how do we help you grow your business with innovation? One of the key things we did, which is probably the one that stuck with me the most, was we actually partnered with the Redhead Management Organization and we pulled in the capability of what's called insights into the product itself. So all carbon subscription 678 all include insights, which is a rules based engine built upon the data that we have from, you know, over 15 years of helping customers run large scale Lennox deployments. And we leverage that data in order to bring that directly to customers. And that's been huge for us. And it's not only it's a first step into getting into answerable. >>I want to get your thoughts on We're here and Ansel Fest ate one of our two day coverage. The Red Hat announced the answer Automation platform. I'll see. That's the news. Why is this show so important in your mind? I mean, you see the internal. You've seen the history of the industry's a lot of technology changes happening in the modern enterprises. Now, as things become modernized both public sector and commercial, what's the most important thing happening? Why is this as well fest so important this year? >>To me, it comes down to, I'd say, kind of two key things. Management and automation are becoming one of the key decision makers that we see in our customers, and that's really driven by. They need to be efficient with what they have running today, and they need to be able to scale and grow into innovation. platform. So management and automation is a core critical decision point. I think the other aspect is, you know, Lennox started out 28 years ago proving to the world how open source development drives innovation. And that's what you see here. A danceable fest. This is the community coming together to drive innovation, super modular, able to provide impact right from everything from how you run your legacy systems to how you bring security to it into how do you bring new applications and deploy them in a safe and consistent way? It spans the whole gambit. >>So, Stephanie, you know, there's so much change going on in the industry you talked about, you know what's happening in Relate. I actually saw a couple of hello world T shirts which were given out at Summit in Boston this year, maybe help tie together how answerable fits into this. How does it help customers, you know, take advantage of the latest technology and and and move their companies along to be able to take advantage of some of the new features? >>Yeah, and so I really believe, of course, that unopened hybrid cloud, which is our vision of where people want to go, You need Lennox. So Lenox sits at the foundation. But to really deploy it in in a reasonable way in a Safeway in an efficient way, you need management on automation. So we've started on this journey. When we launched, we announced its summit that we brought in insights and that was our first step included in we've seen incredible uptick. So, um, when we launch, we've seen 87% increase since May in the number of systems that are linked in, we're seeing 33% more increase in coverage of rules based and 152% increase in customers who are using it. What that does is it creates a community of people using and getting value from it, but also giving value back because the more data we have, the better the rules get. So one interesting thing at the end of May, the engineering team they worked with all the customers that currently have insights. Lincoln and they did a scan for Specter meltdown, which, of course, everyone knows about in the industry with the customers who had systems hooked up, they found 100 and 76,000 customer systems that were vulnerable to Spector meltdown. What we did was we had unanswerable playbook that could re mediate that problem. We proactively alerted those customers. So now you start to see problems get identified with something like insights. Now you bring an answerable and answerable tower. You can effectively decide. So I want to re mediate. I can re mediate automatically. I can schedule that remediation for what's best for my company. So, you know, we've tied these three things together kind of in the stepwise function. In fact, if you have a real subscription, you've hooked up to insights. If insights finds an issue, there's a fix it and with answerable, creates a playbook. Now I can use that playbook and answerable tower so really ties through nicely through the whole portfolio to be able to to do everything in feeling. >>It also creates collaboration to these playbooks can be portable, move across the organization, do it once. That's the automation pieces that >>yeah, absolutely. So now we're seeing automation. How do you look at it across multiple teams within an organization so you could have a tower, a tower admin be able to set rules and boundaries for teams, I can have an array l writes. I t operations person be able to create playbooks for the security protocols. How do I set up a system being able to do things repeatedly and consistently brings a whole lot of value and security and efficiency? >>One of the powers of answerable is that it can live in a header Ji. In this environment, you got your windows environment. You know, I've talked of'em where customers that are using it and, of course, in cloud help help us understand kind of the realm. You know why rail plus answerable is, you know, an optimal solution for customers in those header ingenious environment. And what would love I heard a little bit in the keynote about kind of the road map where it's going. Maybe you can talk to about where those would fit together. >>Yeah, perfect and e think your comment about Header genius World is is Keith. That is the way we live, And folks will have to live in a head or a genius, a cz far as the eye can see. And I think that's part of the value, right to bring choice when you look at what we do with rail because of the close collaboration we have between my team and Theo team. That in the management bu around insights are engineering team is actively building rules so we can bring added value from the sense of we have our red Hat engineers who build rail creating rules to mitigate things, to help things with migration. So us develop well, Aden adoption. We put in in place upgrades, of course, in the product. But also there's a whole set of rules curated, supported by red hat that help you upgrade to relate from a prior version. So it's the tight engineering collaboration that we can bring. But to your point, it's, you know, we want to make sure that answerable and answerable tower and the rules that are set up bring added value to rebel and make that simple. But it does have to be in a head of a genius world. I'm gonna live with neighbors in any data center. Of course, >>what one of the pieces of the announcement talked about collections, eyes there, anything specific from from your team that it should be pointed out about from a collections in the platform announcement. >>So I think I think his collection starts to starts to grow on. Git brings out sort of the the simplicity of being pulled. It pulled playbooks and rolls on and pull that all in tow. One spot. We'll be looking at key scenarios that we pulled together that mean the most Terrell customers. Migration, of course, is one. We have other spaces, of course. Where we work with key ecosystem partners, of course, ASAP, Hana, running on rail has been a big focus for us in partnership with S A P. We have a playbook for installing ASAP Hana on Well, so this collaboration will continue to grow. I think collections offers a huge opportunity for a simpler experience to be able to kind of do a automated solution, if you will kind of on your floor >>automation for all. That's the theme here. >>That's what I >>want to get your thoughts on. The comment you made about analytical analytics keep it goes inside rail. This seems to be a key area for insights. Tying the two things together so kind of cohesive. But decoupled. I see how that works. What kind of analytical cables are you guys serving up today and what's coming around the corner because environments are changing. Hybrid and multi cloud are part of what everyone's talking about. Take care of the on premises. First, take care of the public cloud. Now, hybrids now on operating model has to look the same. This is a key thing. What kind of new capabilities of analytics do you see? >>Yes, that's it. So let me step you through that a little bit because because your point is exactly right. Our goal is to provide a single experience that can be on Prem or off Prem and provides value across both, as as you choose to deploy. So insights, which is the analytics engine that we use built upon our data. You can have that on Prem with. Well, you can have it off from with well, in the public cloud. So where we have data coming in from customers who are running well on the public cloud, so that provides a single view. So if you if you see a security vulnerability, you can skin your entire environment, Which is great. Um, I mentioned earlier. The more people we have participating, the more value comes so new rules are being created. So as a subscription model, you get more value as you go. And you can see the automation analytics that was announced today as part of the platform. So that brings analytics capabilities to, you know, first to be able to see what who's running what, how much value they're getting out of analytics, that the presentation by J. P. Morgan Chase was really compelling to see the value that automation is delivering to them. For a company to be ableto look at that in a dashboard with analytics automation, that's huge value, they can decide. Do we need to leverage it here more? Do we need to bring it value value here? Now you combine those two together, right? It's it, And being informed is the best. >>I want to get your reaction way Make common. Are opening student in our opening segment around the J. P. Morgan comment, you know, hours, two minutes, days, two minutes, depending on what the configurations. Automation is a wonderful thing. Where pro automation, as you know, we think it's gonna be huge category, but we took, um ah survey inside our community. We asked our practitioners in our community members about automation, and then they came back with the following. I want to get your reaction. Four. Major benefits. Automation focused efforts allows for better results. Efficiency. Security is a key driver in all this. You mentioned that automation drives job satisfaction, and then finally, the infrastructure Dev ops folks are getting re skilled up the stack as the software distraction. Those are the four main points of why automation is impacting enterprise. Do you agree with that? You make comments on some of those points? >>No, I do. I agree. I think skills is one thing that we've seen over and over again. Skills is skills. His key. We see it in Lennox. We have to help, right? Bridge window skills in tow. Lennox skills. I think automation that helps with skills development helps not only individuals but helps the company. I think the 2nd 2nd piece that you mentioned about job satisfaction at the end of the day, all of us want to have impact. And when you can leverage automation for one individual toe, have impact that that is much broader than they could do before with manual tasks. That's just that's just >>you know, Stew and I were talking also about the one of the key note keywords that kept on coming out and the keynote was scales scales, driving a lot of change in the industry at many levels. Certainly, software automation drives more value. When you have scale because you scaling more stuff, you can manually configure his stuff. A scale software certainly is gonna be a big part of that. But the role of cloud providers, the big cloud providers see IBM, Amazon, all the big enterprises like Microsoft. They're traveling massive scale. So there's a huge change in the open source community around how to deal with scale. This is a big topic of conversation. What's your thoughts on this? Sending general opinions on how the scales change in the open source equation. Is it more towards platforms, less tools, vice versa? Is there any trends? You see? >>I think it's interesting because I think when I think a scale, I think both volume right or quantity as the hyper scale ours do. I think also it's about complexity. I think I think the public clouds have great volume that they have to deal with in numbers of systems, but they have the ability to customize leveraging development teams and leveraging open source software they can customize. They can customize all the way down to the servers and the processor chips. As we know for most folks, right, they scale. But when they scale across on Prem in off from its adding complexity for them. And I think automation has value both in solving volume issues around scale, but also in complexity issues around scale. So even you know mid size businesses if they want a leverage on Prem, an off ramp to them, that's complexity scale. And I think automation has a huge amount of value to >>bring that abstracts away. The complexity automated, absolutely prized job satisfaction but also benefits of efficiency >>absolutely intimately. The greatest value of efficiency is now. There's more time to bring an innovation right. It's a zoo, Stephanie. >>Last thing I wondering, What feedback are you hearing from customers? You know, one of the things that struck me we're talking about the J. P. Morgan is they made great progress. But he said they had about a year of working with security of the cyber, the control groups to help get them through that knothole of allowing them toe really deploy automation. So, you know, usually something like answerable. You think? Oh, I can get a team. Let me get it going. But, oh, wait, no, Hold on. Corporate needs to make its way through. What is that something you hear generally? Is that a large enterprise thing? You know what? What are you hearing from customers that you're >>talking? I think I think we see it more and more, and it came up in the discussions today. The technical aspect is one aspect. The sort of cultural or the ability to pull it in is a whole separate aspect. And you think that technology from all of us who are engineers, we think, Well, that's the tough bit. But actually, the culture bit is just it's hard. One thing that that I see over and over again is the way cos air structured has a big impact. The more silo the teams are, do they have a way to communicate because fixing that so that you, when you bring in automation, it has that ability to sort of drive more ubiquitous value across. But if you're not structured toe leverage that it's really hard if your I T ops guys don't talk to the application folks bringing that value is very hard, so I think it is kind of going along in parallel right. The technical capabilities is one aspect. How you get your organization structure to reap the benefits is another aspect, and it's a journey. That's that's really what I see from folks. It is a journey. And, um, I think it's inspiring to see the stories here when they come back and talk about it. But to me the most, the greatest thing about it's just start right. Just start wherever you are and and our goal is to try and help on ramps for folks wherever their journey is, >>is a graft over people's careers and certainly the modernization of the enterprise and public sector and governments from how they procure technology to how they deploy and consume it is radically changing very quickly. By the way too scale on these things were happening. I've got to get your take on. I want to get your expert opinion on this because you have been in the industry of some of the different experiences. The cloud one Datta was the era of compute storage startups started Airbnb start all these companies examples of cloud scale. But now, as we start to get into the impact to businesses in the enterprise with hybrid multi cloud, there's a cloud. 2.0 equation again mentioned Observe Ability was just network management at White Space. Small category. Which company going public? It's important now kind of subsystem of cloud 2.0, automation seems to feel the same way we believe. What's your definition of cloud to point of cloud? One daughter was simply stand up some storage and compete. Use the public cloud and cloud to point is enterprise. What does that mean to you? What? How would you describe cloud to point? >>So my view is Cloud one Dato was all about capability. Cloud to Dato is all about experience, and that is bringing a whole do way that we look at every product in the stack, right? It has to be a seamless, simple experience, and that's where automation and management comes in in spades. Because all of that stuff you needed incapability having it be secure, having it be reliable, resilient. All of that still has to be there. But now you now you need the experience or to me, it's all about the experience and how you pull that together. And that's why we're hoping. You know, I'm thrilled here to be a danceable fast cause. The more I can work with the teams that are doing answerable and insights and the management aspect in the automation, it'll make the rail experience better >>than people think it's. Software drives it all. Absolutely. Adam, Thanks for sharing your insights on the case. Appreciate you coming back on and great to see you. >>Great to be here. Good to see >>you. Coverage here in Atlanta. I'm John for Stupid Men Cube coverage here and answerable Fest Maur coverage. After the short break, we'll be right back. >>Um