>>Hey everyone. Welcome back to the Cube's coverage of Ansible Fest 2022. We are live in Chicago. This is day two of Waldo Wall coverage on the cube. John Fhrer here with me. Lisa Martin. John, today's a big news day. Yeah, >>Big time. I mean, we got the chief architect on this segments to be great. We have the lead product management. All the new stuff coming out really is a game changer. It's very cool and relevant. Very key to be relevant. And then, and being a part of the future. This is a changeover you see in the NextGen Cloud developer environment. Open source all coming together. So Ansible we've been covering for many, many years. We've always said they're in the middle of all the action and you're starting to see the picture. Yes. For me. So we're looking forward to a great segment. >>Yes. We've got two alumni back with us to unpack the news and all the great stuff that's going on here. Richard Hensel joins us Senior manager, Ansible Product Management, and Matthew Jones here, fresh from the keynote stage, Chief architect of Ansible Automation. Guys, great to have you on the program. Thanks >>For having us. Good to be here. >>So this morning was all about event driven Ansible. Unpack that. Talk about the impact that this is gonna have, The excitement, the buzz that you've heard on the show floor today. >>Yeah. You know, it's, it's exciting. We've been working on this for a while. We've been really excited to show this off because it's something that feels like the natural evolution of the platform and where it's going. Really being able to connect the automation with the sources of data and the actions that we know people want to use. We, we came into this knowing everybody here at this conference, this is something that everybody will be able to use. >>Talk about the innovations strategy. Cause we've always had these great conversations with Ansible. Oh yeah. The, the practitioners, they're, they're building the product with you. You guys are very hardcore on that. No secret. This is different. This is like a whole nother level of opportunity that's gonna take the, the community to new heights in terms of what they do in their job and free them up to do more creative development. >>Yeah, you're exactly right. You know, we, we know that people need to bring that sort of reactive and active automation to it. We've, we've done a lot of work to bring automation to everybody, to the masses. Now we need to meet them at the place where they are, where the, the where, where they have to do the most work and, and act in the most strategic and specific ways. >>All right. So now before we get into some of the deep dive, cause a ton of questions. This is really exciting product. Take a minute to explain what was the key announcement? Why, what specifically does this mean for the audience, watching customers and future customers? What's the big deal? To take a minute to explain what was announced. >>So this is about the, the evolution and the maturity of the automation that our users are doing. So, you know, you think about provisioning servers, you know, configuring networks, all that sort of, the stuff that we've established and everybody's been doing for a number of years. And then you go, Well, I've invested in that. I've done the heavy lifting, I've done the things that cost me agility. I think that cost me time. Well now I need to go further. So what can I go further into? And you move further at the stacks. You move away from the infrastructure, please. You move away from infrastructure as code. You move towards through configures code, up to officer's code. And you start to get into, well, I've got, I've got road tasks, I've got repetitive actions that I'm doing. I've got investigations, I've got remediations, I've got responses. >>Well, there's work that I do on a daily basis that is toil. Right. It's not efficient work. Right. Actually, we doing valuable work in the operation space as much as you were doing in, in the build space. And how do we move them up into that space? And it's, this is all based off observation. You can do this today, but how do we make it easier? We've gonna make it easier for them to do that and get, it's all about success. It's about the outcomes we're gonna drive users towards. They need to be successful as quickly as possible. How do we make that >>Happen? And Matt, I remember we talked in 2019 with Ansible, the word platform where we say, Hey, you know, platforms are super important. It's not a tool, tools and platforms as distinctions. You mentioned platform. This is now platform. A lot of people put a lot of work in into this Yeah. Claim what went on behind the scenes. So >>You're exactly right. And we've spent the last couple of years really taking that disparate set of tools that, that we've invested a lot of time in building that platform. It's been exciting to see it come together. We always knew that we wanted to capture more of, more of where people find automation and find they need automation, not just out on the edge, on the end of the, of the, of the actions and tasks that they need to do. They've got a lot of things coming in, a lot of things that they need to take care of. And the community is really what drives this for us. People who have been doing this for years and they've been asking us, Meet me halfway. Give me something. Give me a part of this platform and a capability that enables me to do this. So I I feel like we've done that and you did >>It. Yeah, exactly. For step one. >>And that must feel pretty good too, to be able to deliver what, you know, the masses are looking for and why they're looking >>For it. Yeah. This was, there was no question that we knew this was gonna deliver the kind of real value that people were looking for. >>Take us through the building blocks real quick. I know on stage you went through it in detail. What should people know about the core building blocks of, of this particular event driven >>Piece? Yeah. You know, I think the most important thing to understand at the, at the outset is the sources of data and events that come in. It's really easy to get lost in the details. Like, what do you mean a source? But, you know, we've shown examples using Kafka, but it's not just Kafka, right? It's, it's, it's web hooks, it's CI systems, it's any, any place that you can imagine an evict coming from your monitoring platforms. You can bring those together under the same umbrella. We're not requiring you to pick one or choose or what's your favorite one. You can bring, you can use them all and and condense them down into the, into the same place. >>There's a lot of data events everywhere now. There's more events. Yeah. Is there a standard interface? Is what's the, is there any kind of hook in there? Is what's, what's gonna limit? Or is there any limits? >>I I don't think there is a limit. I, you know, it's, and we can't even imagine where events and data are gonna come from, but we know we need to get them into the system in a way that makes the most sense for the, the customers. And then that, that drives through into the rule books. Like, okay, we have the data now, but what do we do with that data? How do we translate that into, into the action? What are the rules that need to follow? It's giving the, the, the person who is automating, who understands the data that's coming in and understands the task that they need to take. The, the rules are where they map those into it. And then the last part, of course is the playbook, the automation itself, which they already know. They're already experts in the system. So we've, we've, we've built this like eight lane highway. They get some right end of those actions. >>Let's talk about Richard, let's unpack those actions and the really kind of double click on the business outcomes that this is actually gonna enable organizations and any industry to achieve. >>Yeah, so >>I mean, it's, it, like Matt said, it's really hard to encapsulate everything that we see as possible. But if you just think about what happens when a system goes down, right? At that point in time, I'm potentially not making money, right? I'd say it's costing me time, it's costing me, that's a business impact. If I can speed up how quick I can resolve that problem, if I can reduce time in there, that's customer improvement, that's custom satisfaction. That's bottom line money for businesses, right? But it's also, it's also satisfaction for the users. You know, they're not involved in having the stressful get online, get quickly, activate whatever accounts you need to do, go and start doing discovery. You can detect a lot of that information for the discovery use case that we see, respond to an event, scan the system for that same logic that you would normally do as a user, as a human. >>And that's why the rules are important to add into ed. It's like, how do I take that human, that brain part that I would say, well, if I see this bit, oh, I'll go and have a look in this other log file. If I see this piece, I'll go and do something different. How do we translate that into Ansible so that you've got that conditional logic just to be able to say, if this do that, or if I see these three things, it means a certain outcome has happened. And then again, that defined, that's what's gonna help people like choose where it becomes useful. And that's how we, that's how we take that process >>Forward. I'm sure people are gonna get excited by this. I'm not sure the community already knows that, but as it's gonna attract more potential customers, what's different about it? Can you share the differentiation? Like wait minute, I already have that already. Do they have it already? What's different? What makes this different? What's, what's in it for them? >>Yeah. When we step up into a customer situation, an enterprise, an organization, what's really important becomes the, the ability to control where you do some of that work. So the control and the trust, You know, would you trust an automatic system to go and start making changes to hundreds of thousands of devices? And the answer is often not, not straight away. So how do we put this sort of sep the same separation of duties we have between dev and ops and all the nice structures we've done over the last number of years, and actually apply that to that programmatic access of automation that other systems do. So let's say a AIML systems that are detecting what's going on, observability platforms are, are much more intru or intrusive is the wrong word. They're much more observable of what's going on in the systems, right? But at the same time you go, I wanna make sure that I know that any point in time I can decide what, what is there and what can be run and who can run it and when they can run it. And that becomes an important dimension. >>The versatility seems like a big deal too. They can, Yeah. Any team could get >>Involved. And, and that's the, the same flexibility and the same extensibility of Ansible exists in this use case, right? The, the, the ability to take any of those tasks you wanna do in action, string them together, but what the way that it works for you, not the way that it works that we see, but the way that you see and you convert your operational DNA into how you do that automation and how that gets triggered as you see fit. >>Talk about this both of you. I'd like to get your perspectives on event driven Ansible as part of the automation journey that businesses are on. Obviously you can look at different industries and different businesses are, are at different places along that journey, but where does this fit in and kind of plugin to accelerating that journey? That's, >>That's a good question. You know, sometimes this ends up being like that last mile of we've adopted this automation, we've learned how to write automation. We even understand the things that we would need to automate, but how do we carry it over that last topic and connect it to our, our knowledge systems, our data stores, our data lakes, and how do we combine the expertise of the systems that we're managing with this automation that we've learned? Like you, you mentioned the, the, the community and the, the coalescing of data and information, the, the definition of the event rules and, and the event driven architecture. It lives alongside the automation that you've developed in the exact same place where you can feel that trust and ubiquity that we keep talking about. Right? It's there, it's certified. And we've talked a lot about secure supply chain recently. This gives you the ability to sign and certify that the rules and actions that we're taking and the sources that we're communicating with works exactly the same way. Yeah. And >>There's something we didn't, we didn't correlate this when we first started doing the work. We were, we were, we observe teams doing self-healing and you know, extending Ansible. And then over the last 18 months, what we've also seen is this movement, this platform engineering movement, the SRE teams becoming much more prominent. And this just nicely sits in as a type of use case for that type of transformation. You know, we've gotta remember that Ansible at is heart is also a transformative tool. Is like, how do you teach this behavior to a bunch of people? How do you upscale a larger base of engineers with what you want to be able to do? And I think this is such an important part that we, we just one say we stumbled into it, but it was a very, very nice, >>It was a natural progression. >>Exactly. >>Yeah. Yeah. Tom, Tom, when we were talking about Tom yesterday, Tom Anderson and he said, You guys bring up the SRE to you guys when you come on the cube. This is exactly a culture shift that we're talking about. I mean, SRE is really his legacy with Google. We all know that. Everyone kind of knows that, but it's become like a job title. Well they kind of, what does that even mean now if you're not Google, it means you're running stuff. DevOps has become a title. Yeah. So what that means is that's a cultural shift, not so much semantics Yeah. On title. This is kind of what you guys are targeting here, enabling people to run platforms, engineer them. Yeah. Like an architect and enable more co composability coding. >>And, and it's, so that's, that distinction is so important because one of the, you know, we see many customers come from different places. Many users from, you know, all the legacy or heritage of tools that have existed. And so often those processes are defined by the way that tool worked. Right? You had no other way that, that, and the, and it's, it happened 10 years ago, somebody implemented it, that's how it now works. And then they come and try and take something new and you go, well, you can't let the tool define your process. Now your culture and your objective has to define the process. So this is really, you know, how do we make sure we match that ability by giving them a flexible tool that let's say, Well what are you trying to achieve? I wanna achieve this outcome. That's the way you can do it. I >>Mean, that's how we match basically means my mind to get your reaction. It means I'm running stuff at scale. Yep. Engineer, I'm engineering and infrastructure at scale to enable, >>I'm responsible for it. And it's, it's my, it's my baby. It's my responsibility to do that. And how do we, how do we allow people to do that better? And you know, it, it's about, it's about freeing people up to focus on things that are really important and transformative. We can be transformative. And we do that by taking away the complexity and making things work fast. >>And that's what people want. People in their daily jobs want to be able to deliver value to the organization. You wanna feel that. But something Richard that you were talking about that struck me a couple minutes ago is, was a venture of an Ansible. There's employee benefits, there's customer benefits, Those two are ex inextricably linked. But I liked how you were talking about what it facilitates for both Yes. And all the way to the customer satisfaction, brand reputation. That's an important Yeah. Element for any brand to >>Consider. And that, I mean, you know, think about what digital transformation was all about. I mean, as we evolve past all these initial terms that come about, you know, we actually start getting to the meat of what these things are. And that is it connecting what you do with actually what is the purpose of what your business is trying to achieve. And you can't, you can't almost put money on that. That's, that's the, that's the holy grail of what you're trying to get to. So how, you know, and again, it just comes back to how do we facilitate, how do we make it easy? If we don't make it easier, we're not doing it right. We've gotta make it easier. >>Right. Well, exciting news. I want to get your guys' reaction and if you don't mind sharing your opinion or your commentary on what's different now with Ansible this year than just a few years ago in terms of the scope of what's out there, what's been built, what you guys are doing for the, for the customer base and the community. What's changed? Obviously the people's roles looked that they're gonna expand and have more, I say more power, you know, more keys to the kingdom, however you wanna look at it. But things have changed. What's changed now from a few years >>Ago. It's, you know, it, it's funny because we've spent a lot of time over the last couple years setting up the capabilities that you're seeing us deliver right now. Right. We, we look back two or three years ago and we knew where we wanted to be. We wanted to build things like eda. We wanted to invest in systems like Project Wisdom and the, the types of content, the cloud journey that, that now we're on and we're enabling for folks. But we had to make some really big changes. And those changes take time and, and take investment. The move into last year, John, we talked about execution environments. Yeah. And separating the control plane from the execution plane. All of that work that we did and the investment into the platform and stability of the platform leads us now into what >>Cap. And that's architectural decision. That's the long game in mind. Exactly. Making things more cohesive, but decoupled, that's an operating system kind of thinking. >>It, it totally is. It's a systems engineering and system architecture thinking. And now we can start building on top of these things like what comes after ed, what does ED allow us to do within the platform? All of the dev tools that we focused on that we haven't spent a lot of time talking about that from the product side. But being, coming in with prescriptive and opinionated dev tools, now we can show you how to build it. We can show you how to use it and connect it to your systems. Where can we go next? I'm really excited. >>Yeah. Your customer base two has also been part of from the beginning and they solve their own problems and they rolled it up, grow with it, and now it's a full on platform. The question I then ask is, okay, you believe it's a platform, which it is, it's enabling. What do you guys see as that possible dots that could connect that might come on top of this from a creativity standpoint, from an ecosystem standpoint, from an Ansible standpoint, from maybe Red Hat. I mean, wisdom shows that you can go into the treasure trove of IBM's research, pull out some AI and some machine learning. Both that in or shim layered in whatever you do. >>I mean, what I'm starting to see much more, especially as I, the nice thing about being here is actually getting face to face with customers again and you know, actually hearing what they're talking about. But you know, we've moved away from a Ansible specific story where I'm talking about how I, I was always, I was looking to automate, I was looking to go to Ansible. Well now I've got the automation capability. Now we've enhanced the automation. Capabil wisdom enhances the automation capability further. What about all those, those broader set of management solutions that I've got that I would like to start connecting to each other. So we're starting to take the same like, you know, you mentioned as then software architecture, software design principles. We'll apply those same application design principles, apply them to your IT management because we've got data center with the pressures on there. We've got the expansion into cloud, we've got the expansion to the edge, right? Each adding a new layer of complexity and a new layer of, you know, more that you have to then look after. But there's still the same >>Number of people. So a thousand flower blooms kind of situation. >>Exactly. And so how do I, how do I constrain, how do I tame it, right? How do I sit there and go, I, I can control that now I can look after that. I contain that. I can, I can deal with what I wanna do. So I'm focusing on what's important and we are getting stuff done. >>We, we've been quoting Andy Grove on the cube lately. Let chaos, rain and then rain in the chaos. Yes. Right? I mean that's kind of every inflection point has complexity before it gets simpler. >>Yeah, that's right. >>Yeah. You can't, there's answer that one. That's >>Perfectly. >>Yeah. Yeah. What do you expect to see chief ar you gotta have the vision. What's gonna pop out? What's that low, low hanging fruit? What's gonna bloom first? What do you think's gonna come? >>I, you know, my overarching vision is that I just want to be able to automate more. Where, where can we bring back, So edge cloud, right? That's obvious, but what things run in the cloud and and on the edge, right? Devices, you heard Chad in the keynote this morning talk about programmable logic controllers, sensors, fans, motors, things like that. This is the, the sort of, this is the next frontier of automation is that connecting your data centers and your systems, your applications and needs all the way out to where your customers are. Gas stations, point of sale systems. >>It's instant. It's instant. It is what it is. It's like just add, Just >>Add faster and bigger. Yeah. >>But what happens if, I'll give you a tease. What I think is, is what happens if this happens? So I've got much more rich feature, rich diverse set of tools looking after my systems, observing what's going on. And they go through a whole filtering process and they say such and such has happened, right? Wisdom picks that up and decides from that natural language statement that comes outta the back of that system. That's the task I think is now appropriate to run. Where do you run that? You need a secure execution capability. Pass that to an support, that single task. And now we run inside the automation platform at any of those locations that you just mentioned, right? Stitching those things together and having that sequence of events all the way through where you, you predefine what's possible. You know, you start to bias the system towards what is your accepted standard and then let those clever systems do what you are investing in them for, which is to run your IT and make it >>Easier. Rich here was on earlier, I said, hey, about voice activated it. Provision the cluster. Yeah. >>Last question guys, before we run out of time for this. For customers who take advantage of this new frontier, how can they get started with the bench of an what's? >>That's a good question. You know, we, we've engaged our community because they trust us and we trust them to build really good products. ansible.com/events. Oh man, >>I did have the, I >>Had the cup, the landing page. >>Find somebody find that. >>Well it's on GitHub, right? GitHub It is. >>Yeah it >>Is. Absolutely ansible.com. It's probably a link somewhere if I on the front page. Exactly. On GitHub. The good code too. >>Right? Exactly. And so look at there, you can see where we're going on our roadmap, what we're capable of today. Examples, we're gonna be doing labs and blogs and demonstrations of it over the next day, week, month. Right. You'll be able to see this evolve. You get to be the, the sort of vanguard of support and actions on this and >>Cause we really want, we really want users to play with it, right? Of course. We've been doing this for a while. We've seen what we think is right. We want users to play with it. Tell us whether the syntax works, whether it makes sense, how does it run, how does it work? That's the exciting part. But at the same time, we want the partners, you know, we, we don't know all the technologies, right? We want the partners that we have that work with us already in the community to go and sort of, you know, do those integrations, do those triggers to their systems, define rules for their stuff cuz they'll talk to their customers about it as >>Well. Right? Right. It'll be exciting to see what unfolds over the next six to nine months or so with the partners getting involved, the community getting involved. Guys, congratulations on the big announcements. Sounds like a lot of work. I can tell. We can tell. Your excitement level is huge and job well done. Thank you so much for joining us on the Cube. Thank you very much. Thank you. Our pleasure. Just All right, for our guests and John Furrier, I'm Lisa Martin. You're watching The Cube Live from Chicago, Ansible Fest 22. John and I will be right back with our next guest of Stay tuned.

(upbeat music) >> Welcome back to Chicago, guys and gals. Lisa Martin here in Chicago with Ansible Fest 2022 with John Furrier. John, we've had great conversations. This is day two of our coverage. We were here yesterday. >> Yeah. >> We're here today. We've gotten to talk with great folks in the Ansible community, the partner ecosystem customers. We've broken some news that they've talked about. Now we're going to talk about industrial automation, IT/OT convergence. What excites you about this conversation? >> Yeah, this is going to be a great segment. This is one of the feature keynote presenters, customer Rockwell. Huge in OT, IT, edge, robotics, plants, equipment. Everything that we probably have, they do. This guest has really great story about what's cutting edge and what's relevant in the edge and IT slash automation area. Super relevant. Looking forward to the segment. >> Yes, please welcome David Rapini, the Global PlantPAx business manager at Rockwell Automation. David, great to have you on theCUBE. >> Thank you. Nice to be here. >> Give the audience a bit of an overview of Rockwell Automation and then let's dig into what you guys are doing there. >> Sure. Rockwell Automation probably is the largest global automation provider of equipment focused exclusively on automation. About 22,000 employees. About 7 billion kind of revenue numbers. We make, basically, controllers for the automation industry, industrialized software, power drives, you know, of the robotics content, smart cart kind of applications. >> Lisa: And what are your key industries that you're covering? >> Wow, so that's a broad market. So we do a lot of different industries. So we cover, obviously, oil and gas, life science, water, wastewater. We do automotive. So just about any industry, actually. Any place that needs industrial automation covering any type of manufacturing process or any type of process application. We're pretty much there. >> John: You know, it's interesting, IOT has been a word, in and of things, light bulb, wearables, industrial IOT where you're in is a really key space. It's physical plants. Sometimes it's sensitive critical infrastructure for governments, businesses. >> David: Exactly. >> I mean there's running stuff. >> David: Definitely. >> This is huge. >> Yeah, and it's a big area for us, like getting that data, you know, everybody talks about analytics and what the world's going to be happening to in that IT, OT space. And Rockwell's really well positioned at that lower level where we actually own the data, create the data for all that analytics that you're talking about. >> What was your main message today on stage? I want to replay that here and then get into it because I think this is really, we're starting to see, real traction in adoption, in automation, cloud scale, edges happening, exploding. What was your key message on stage today? >> Yeah, I think it's that the world's really changing in that space. You know, five years ago you would have had a completely different message around, you know that connectivity and having that content actually delivered to that space and having, like even the connectivity to that OT space makes people uncomfortable in that world because there's obviously moving pieces, you know, damage to equipment, you know God forbid any types of explosions or things like that on bad environmental type conditions. So we're working in that space to really make those connections much more open and now that those connections are starting to happen and we're getting more and more comfort with that, in that layer, there's a lot more we can do in that space which is kind of why we're here. >> And talk about why Ansible and what it's going to be able to unlock for Rockwell to be able to achieve. >> Sure. There's a lot of areas that we want to play with, but our, in Ansible but our first targets are really our, primarily our servers. So there's a lot of edge based servers out there, you know, we call them a pass server, which is a process automation system server. And there's an engineering workstation operator, which are those main core servers. Some of them are redundant, you know, the OT guys to them it's a burden to manage that content. They're good at making, you know, oil and gas they know how to do water wastewater. They know how to build cars. But managing servers, you know, not in their wheelhouse. >> John: Not in their wheelhouse.(laughs) >> Exactly. Right. So having that capability and that connection to get down there gives us some power with Ansible to go ahead and start building them initially. So making that initial builds out of the gate. That makes them really consistent and built together, so every application looks and feels the same and they know what they're going to get when their servers power up. So that's a big one. But, but just maintain them, keeping them patched, you know keeping security vulnerabilities down. You know, I was in a facility not long ago that was still running Windows 2000. Right. So, you know, they have an application there that's just working. It works. They don't want to touch it and it's been running for 20 years, so why touch it? Right. So this was going to kind of hopefully break that challenge. >> Make sure that you keep that password handy. (laughs) >> David: Yeah, exactly right. (laughs) >> We've had (indistinct) people leave. What about the security aspect is OT has been locked down, mindset, hardened, end to end, supply chains, vetted. Everything's kind of tight on the old OT model. Relatively secure when you get to IT, you mentioned vulnerabilities but the innovation's there too. So how does that reconcile for you? What's your reaction to that? >> Yeah, we see a big move there, right? So it used to be they were always head head to head butting heads IT, OT, you know it focuses on, you know, keeping the system secure keeping the data down, locked down, and reliable. OT focuses more on production, right? Making sure they hit their numbers in the production. So oftentimes, you know, having it push out a patch in the middle of production line in the middle of a day and rebooting a server shuts down production and you know, that those kind of conflicts. Yeah, exactly. So those conflicts were, were pretty common. There's still a lot of that there, but it's getting better. Yeah, right. And I see more and more of that working together as a team to, to solve a lot of those challenges. And honestly, I keep going back to the analytics angle and the diagnostics and that world of deep data, you know, big data kind of mining, you know, without the IT space to cover that the cloud data storage, the horsepower. >> If you had to kind of like rank the complexity 'cause we were just talking before you came on about things got to get complex before they can get simpler 'cause the inflection points bring that new capability. What's some of the complexities that you're seeing that are going to be either abstracted away or solved with some of these new technologies like Ansible and others that are coming fast? Cause at the end of the day it's got to still be easier. It's not going to be hard. That can't be harder. >> Yeah. So I'll give you a real world example that's a little embarrassing. So today we deliver our past servers as a solution and we we provide that as a VM image that people start with as the first building block. But once you start to deploy that and actually connect it with the rest of the infrastructure, hook it up to our factory talk directory, hook it up to the DNS service, once you start doing all that work it's about 700 mouse clicks that somebody has to know what they're doing to actually spin it up the rest of the way and get it connected with Ansible. We're cutting that number like in half is the hope. So, and, and we're going to continue to expand that and make it even less work for the users to >> Talk about skill gap issue. The training alone on that is to have the right people. >> That's the second big piece, right? So, so those OT people typically don't have that skill set. So you have to have a fairly high skilled level person to do that work. We're hoping to take that, that work off of them and put that on on answer. >> Yeah, that sounds pretty consistent. Do you think, is that the, kind of the consistency of the problem space is that the OT just has a different goal and they just need something to be invisible and easy, like electricity? >> Yeah, I think so. Especially in this world, right? In that OT space, right in in that IT space. Sorry. Yeah, so, so managing servers and things like that it's just is not what they want to want to deal with and it's not what they went to school for and it's not what they're doing when their job when they get hired. Right. Yeah. >> It sounds to me like Rockwell Automation is a facilitator of the IT and OT folks coming together and actually working better together, maybe understanding each other's requirements, goals, objectives. >> Most definitely. So we have, you know we are offering a lot of cloud content now. We're continuing to expand that content. We're working with a lot of different IT departments and OT departments to try to marriage those two groups together to try to bring that stuff together. We have a partnership with Cisco where we actually, you know, industrialize you know, some of their switch components and sell that as as part of our content and that relationship gives us a big inroad with a lot of the IT departments. >> That's important to have that be able to speak the language of both sides. >> Yeah, definitely. Right. Knowing and understanding the terminology and just being able to know the challenges that IT guys face as well as the OTs is really a big component of what we do. >> You know, one of the questions I wanted to ask and 'cause the keynote was very cool, but you made a comment that your claim to fame was that you wrote the code for the Spider-Man ride at Universal. Tell a story. How does that work? I'm just, I've rode them many times. So take us through that little journey. >> Yeah, so I, every time people ask me what we do for a living and automation, you know, I can talk about, you know, making cars and things like that, but it doesn't ring troops. So I did do a lot of work on Spider-Man Ride which is at Universal Studios, you know it was a real challenge, making sure you know how that connections actually work and make, I did most of the motion control content for that to make the movements of the cars, you know, seamless with the backgrounds. Definitely a lot of fun. So those kind of projects are rare but they're really fun when you get those. >> I hope you have a free pass for any time you want to go on it. >> I don't, unfortunately. >> Oh, you should. >> I try to get in the backrooms all the time at that facility but it's rare to hear. >> I mean it's like, it's a high end rollercoaster machine. It's like, I mean that is this robotics, industrial cause, this, I mean it's an intense ride. >> It is, and you know, you never move more than like eight feet on that whole ride and it feels like you've dropped, you know 2000 feet out of the sky on some of that content. So it's really amazing. I will say it's a little dated. I've been writing on the part of my team worked on the the Harry Potter rides, which are much next generation. >> I couldn't get on that one, line was too long. >> It's a long way, but it's worth it. >> Dave I asked you a question on the future for people watching who are new observing industrial IOT. What's the most important story going on in your world today? Is it the transformation? Is it the standards? Is it the security? What's, what are the top two or three things that are going on that are really transformative right now in automating at the edge? >> I really want to say that it's standardization. It's about using open standards and standard protocols to deliver content in a reusable fashion. So, you know, having custom proprietary content like a lot of automation suppliers or even like a lot of other industries, it's hard to maintain. It doesn't work well with other products. It's great 'cause you can do a lot of flexibility what you want to do, but at the end of the day it's about keeping the thing running and hooking it up to other components so that open standards based solution you'll see us spending more energy on you know, part of the Ansible open community thing is nice in that space as well. And you'll see us doing more stuff in that place that, that play. >> Talk about your influence there in the community. You know, we, we've been talking the last couple of days about Ansible is nothing if not the power of the community, the collaboration within. Talk about being able to influence that and what that means to you personally as well as to Rockwell. >> Yeah, so open communities are big for us. We have, you know, obviously a customer advisory boards and things like that that we deal with but we also have an open community forum where people can share dialogues and share ideas. We have large events, we have a process solution users group events where we bring in, you know hundreds not thousands of engineering people to to talk to all of these problems that they're facing. And it's not a Rockwell event it's a, you know, community event, right. Where we actually are talking about, you know what industry problem people are seeing. And a lot of the IT OT convergence thing is really top of mind. A lot of people say no minds especially the cybersecurity content. >> What are some of the things that you heard the last couple of days, announcement wise? Obviously big news coming out today that excites you about the direction that Ansible's going and how it's responding to the community. >> Yeah, I think a lot of their feedback that they get and sitting a lot of these sessions, they get a lot of interesting feedback from their customer base. And reacting to that I think is very high on their priority list. And what I've been seeing here, you know, some of the AI stuff that they were showing on automatically, like defining some of the scripts for their code that intelligence behind a lot of that content was amazing. I see a lot of that moving forward. And we're heading the same direction at Rockwell as well with more AI in our company. >> The data's a big story too coming out of all the devices, analytics, great stuff. >> Yeah, I'm pulling that data up into the cloud space and trying to do something valuable with all that data. It's, you know, we've had big data for a long time. It's just figuring out analytics and how to actually act on that data and get it back into the control to do something with. >> It's all getting aside. My serious question on this is that, you know is it the year finally OT and IT converge? Seems like it's been trying for about a decade. >> Yeah, that's a tough one to answer. So I would say it's not there yet. I think there's still a lot of conflict in that space. You know, the OT guys still have a long history of that space, but as you see more retirement and more people phasing out of that and younger crowds coming in, you know the automation space is ripe for that kind of transition because coming out of college, you know jumping into automation isn't always the top of the notch. A lot of people want to go work at the big Amazons or wherever. >> A lot, a lot of stuff going on in space. It's pretty cool. A lot of physical, I've seen a lot more machine learning and physical devices in the industry we've been reporting on. It's interesting. I think it's close to a tipping point because we saw machine learning and the trivial apps like chat bots never really took off, yep. Just expert systems basically, but they're not really going the next level. So now they are, you're starting to see more, you know of wisdom projects, you know, different models being adopted. So I see AI now kind of kicking up similar to OT IT. >> Yeah, most definitely. You know, we have a lot of projects in that space like doing predictive analysis on, let's just say something simple like a pump, right? If you have pumps out there that are running for years and years, but you notice that there's a trend that on day 305 or whatever you know, a bearing starts to fail all the time. You know, that kind of analytics can start doing predictive maintenance content and start pushing out work orders in advance before the things fail because downtime costs millions of dollars for these maintenance. >> Downtime also incidents, right? So you never know, right? >> Exactly. Right, right. So it's good to have that safety net at least from a manufacturing perspective. >> Final question for me. What's the most exciting thing going on in your world right now if you had to kind of pick one thing that you're most jazzed up about? >> I have to say, you know, Rockwell's doing a big shift to cloud-based content and more big data numbers like we were just talking about for that AI. That complexity of what you can do with AI and the value that you can do to like just, you know if I can make quality of a product a half a percent better that's millions of dollars for my customer and I see us doing a lot of work in that space and moving that forward. That's big for me, I think. >> And what are some of that, my last question is what are some of the impacts that customers can expect from that? >> Yeah, so everything from downtime to product quality to increasing production rates and volumes of data that come out. You know, we do something called model predictive control that does, you know, very tight control on control loops to improve like just the general product quality with a lot of the big data numbers that are coming in on that. So you'll see us moving more in that space too to improve you know, product quality and then downtime. >> And really driving outcomes, business outcomes for your customers. David, thank you so much for joining us on the program, sharing what Rockwell Automation is doing. We appreciate your insights, your time and we want to keep watching to see what comes next. >> Sure. Glad to be here. It's great. Thank you very much. >> Our pleasure. For our guest, our John Furrier. I'm Lisa Martin. You've watched theCUBE Live in Chicago, Ansible Fest 2022. Thanks for watching. (gentle music)

(soft music) >> Welcome back to Chicago guys and gals. Lisa Martin here with John Furrier. We have been covering Ansible Fest '22 for the last two days. This is our show wrap. We're going to leave you with some great insights into the things that we were able to dissect over the last two days. John, this has been an action packed two days. A lot of excitement, a lot of momentum. Good to be back in person. >> It's great to be back in person. It was the first time for you to do Ansible Fest. >> Yes. >> My first one was 2019 in person. That's the last time they had an event in person. So again, it's a very chill environment here, but it's content packed, great active loyal community and is growing. It's changing. Ansible now owned by Red Hat, and now Red Hat owned by IBM. Kind of see some game changing kind of movements here on the chess board, so to speak, in the industry. Ansible has always been a great product. It started in open source. It evolved configuration management configuring servers, networks. You know, really the nuts and bolts of IT. And became a fan favorite mainly because it was built by the fans and I think that never stopped. And I think you started to see an opportunity for Ansible to be not only just a, I won't say niche product or niche kind of use case to being the overall capabilities for large scale enterprise system architectures, system management. So it's very interesting. I mean I find it fascinating how, how it stays relevant and cool and continues to power through a massive shift >> A massive shift. They've done a great job though since the inception and through the acquisition of being still community first. You know, we talked a lot yesterday and today about helping organizations become automation first that Ansible has really stayed true to its roots in being community first, community driven and really that community flywheel was something that was very obvious the last couple of days. >> Yeah, I mean the community thing is is is their production system. I mean if you look at Red Hat, their open source, Ansible started open source, good that they're together. But what people may or may not know about Ansible is that they build their product from the community. So the community actually makes the suggestions. Ansible's just in listening modes. So when you have a system that's that efficient where you have direct working backwards from the customer like that, it's very efficient. Now, as a product manager you might want to worry about scope creep, but at the end of the day they do a good job of democratizing that process. So again, very strong product production system with open source, very relevant, solves the right problems. But this year the big story to me is the cultural shift of Ansible's relevance. And I think with multicloud on the horizon, operations is the new kind of developer kind of ground. DevOps has been around for a while. That's now shifted up to the developer themselves, the cloud native developer. But at cloud scale and hybrid computing, it's about the operations. It's about the data and the security. All of it's about the data. So to me there's a new ops configuration operating model that you're seeing people use, SRE and DevOps. That's the new culture, and the persona's changing. The operator of a large scale enterprise is going to be a lot different than it was past five, 10 years. So major cultural shift, and I think this community's going to step up to that position and fill that role. >> They seem to be having a lot of success meeting people where they are, meeting the demographics, delivering on how their community wants to work, how they want to collaborate. But yesterday you talked about operations. We talked a lot about Ops as code. Talk about what does that mean from your perspective, and what did you hear from our guests on the program with respect that being viable? >> Well great, that's a great point. Ops as code is the kind of their next layer of progression. Infrastructure is code. Configuration is code. Operations is code. To me that means running the company as software. So software influencing how operators, usually hardware in the past. Now it's infrastructure and software going to run things. So ops as code's, the next progression in how people are going to manage it. And I think most people think of that as enterprises get larger, when they hear words like SRE, which stands for Site Reliable Engineer. That came out of Google, and Google had all these servers that ran the search engine and at scale. And so one person managed boatload of servers and that was efficient. It was like a multiple 10x engineer, they used to call it. So that that was unique to Google but not everyone's Google. So it became language or parlance for someone who's running infrastructure but not everyone's that scale. So scale is a big issue. Ops as code is about scale and having that program ability as an operator. That's what Ops as code is. And that to me is a sign of where the scale meets the automation. Large scale is hard to do. Automating at large scale is even harder. So that's where Ansible fits in with their new automation platform. And you're seeing new things like signing code, making sure it's trusted and verified. So that's the software supply chain issue. So they're getting into the world where software, open source, automation are all happening at scale. So to me that's a huge concept of Ops as code. It's going to be very relevant, kind of the next gen positioning. >> Let's switch gears and talk about the partner ecosystem. We had Stefanie Chiras on yesterday, one of our longtime theCUBE alumni, talking about what they're doing with AWS in the marketplace. What was your take on that, and what's the "what's in it for me" for both Red Hat, Ansible and AWS? >> Yeah, so the big news on the automation platform was one. The other big news I thought was really, I won't say watered down, but it seems small but it's not. It's the Amazon Web Services relationship with Red Hat, now Ansible, where Ansible's now a product in AWS's marketplace. AWS marketplace is kind of hanging around. It's a catalog right now. It's not the most advanced technical system in the world, and it does over 2 billion plus revenue transactions. So even if it's just sitting there as a large marketplace, that's already doing massive amounts of disruption in the procurement, how software is bought. So we interviewed them in the past, and they're innovating on that. They're going to make that a real great platform. But the fact that Ansible's in the marketplace means that their sales are going to go up, number one. Number two, that means customers can consume it simply by clicking a button on their Amazon bill. That means they don't have to do anything. It's like getting a PO for free. It's like, hey, I'm going to buy Ansible, click, click, click. And then by the way, draw that down from their commitment to AWS. So that means Amazon's going into business with Ansible, and that is a huge revenue thing for Ansible, but also an operational efficiency thing that gives them more of an advantage over the competition. >> Talk what's in it for me as a customer. At Red Hat Summit a few months ago they announced similar partnership with Azure. Now we're talking about AWS. Customers are living in this hybrid cloud world, often by default. We're going to see that proliferate. What do you think this means for customers in terms of being able to- >> In the marketplace deal or Ansible? >> Yeah, the marketplace deal, but also what Red Hat and Ansible are doing with the hyperscalers to enable customers to live successfully in the hyper hybrid cloud world. >> It's just in the roots of the company. They give them the choice to consume the product on clouds that they like. So we're seeing a lot of clients that have standardized on AWS with their dev teams but also have productivity software on Azure. So you have the large enterprises, they sit on both clouds. So you know, Ansible, the customer wants to use Ansible anyway, they want that to happen. So it's a natural thing for them to work anywhere. I call that the Switzerland strategy. They'll play with all the clouds. Even though the clouds are fighting against each other, and they have to to differentiate, there's still going to be some common services. I think Ansible fits this shim layer between clouds but also a bolt on. Now that's a really a double win for them. They can bolt on to the cloud, Azure and bolt on to AWS and Google, and also be a shim layer technically in clouds as well. So there's two technical advantages to that strategy >> Can Ansible be a facilitator of hybrid cloud infrastructure for organizations, or a catalyst? >> I think it's going to be a gateway on ramp or gateway to multicloud or supercloud, as we call it, because Ansible's in that configuration layer. So you know, it's interesting to hear the IBM research story, which we're going to get to in a second around how they're doing the AI for Ansible with that wisdom project. But the idea of configuring stuff on the fly is really a concept that's needed for multicloud 'Cause programs don't want to have to configure anything. (he laughs) So standing up an application to run on Azure that's on AWS that spans both clouds, you're going to need to have that automation, and I think this is an opportunity whether they can get it or not, we'll see. I think Red Hat is probably angling on that hard, and I can see them kind of going there and some of the commentary kind of connects the dots for that. >> Let's dig into some of news that came out today. You just alluded to this. IBM research, we had on with Red Hat. Talk about what they call project wisdom, the value in that, what it also means for for Red Hat and IBM working together very synergistically. >> I mean, I think the project wisdom is an interesting dynamic because you got the confluence of the organic community of Ansible partnering with a research institution of IBM research. And I think that combination of practitioners and research groups is going to map itself out to academic and then you're going to see this kind of collaboration going forward. So I think it's a very nuanced story, but the impact to me is very clear that this is the new power brokers in the tech industry, because researchers have a lot of muscle in terms of deep research in the academic area, and the practitioners are the ones who are actually doing it. So when you bring those two forces together, that pretty much trumps any kind of standards bodies or anything else. So I think that's a huge signaling benefit to Ansible and Red Hat. I think that's an influence of Red Hat being bought by IBM. But the project itself is really amazing. It's taking AI and bringing it to Ansible, so you can do automated configurations. So for people who don't know how to code they can actually just automate stuff and know the process. I don't need to be a coder, I can just use the AI to do that. That's a low code, no code dynamic. That kind of helps with skill gaps, because I need to hire someone to do that. Today if I want to automate something, and I don't know how to code, I've got to get someone who codes. Here I can just do it and automate it. So if that continues to progress the way they want it to, that could literally be a game changer, 'cause now you have software configuring machines and that's pretty badass in my opinion. So that thought that was pretty cool. And again it's just an evolution of how AI is becoming more relevant. And I think it's directionally correct, and we'll see how it goes. >> And they also talked about we're nearing an inflection point in AI. You agree? >> Yeah I think AI is at an inflection point because it just falls short on the scale side. You see it with chatbots, NLP. You see what Amazon's doing. They're building these models. I think we're one step away from model scaling. I think the building the models is going to be one of these things where you're going to start to see marketplace and models and you start to composability of AI. That's where it's going to get very interesting to see which cloud is the best AI scale. So I think AI at scale's coming, and that's going to be something to watch really closely. >> Something exciting. Another thing that was big news today was the event driven Ansible. Talk about that, and that's something they've been working on in conjunction with the community for quite a while. They were very proud of that release and what that's going to enable organizations to do. >> Well I think that's more meat on the bone on the AI side 'cause in the big trend right now is MLAI ops. You hear that a lot. Oh, data ops or AI ops. What event driven automation does is allows you to take things that are going on in your world, infrastructure, triggers, alarms, notifications, data pipelining flows, things that go on in the plumbing of infrastructure. are being monitored and observed. So when events happen they trigger events. You want to stream something, you send a trigger and things happen. So these are called events. Events are wide ranging number of events. Kafka streaming for data. You got anything that produces data is an event. So harnessing that data into a pipeline is huge. So doing that at scale, that's where I think that product's a home run, and I think that's going to be a very valuable product, 'cause once you understand what the event triggers are, you then can automate that, and no humans involved. So that will save a lot of time for people in the the higher pay grade of MLAI ops automate some of that low level plumbing. They move their skill set to something more valuable or more impactful. >> And we talked about, speaking of impact, we talked about a lot of the business impact that organizations across industries are going to be able to likely achieve by using that. >> Yeah, I mean I think that you're going to see the community fill the gap on that. I mean the big part about all this is that their community builds the product and they have the the playbooks and they're shareable and they're reusable. So we produce content as a media company. They'd talk about content as is playbooks and documentation for people to use. So reuse and and reusing these playbooks is a huge part of it. So as they build up these catalogs and these playbooks and rules, it gets better by the community. So it's going to be interesting to see the adoption. That's going to be a big tell sign for what's going to happen. >> Yep, we get definitely are going to be watching that space. And the last thing, we got to talk to a couple of customers. We talked to Wells Fargo who says "We are a tech company that does banking," which I loved. We got to talk with Rockwell Automation. What are some of your takeaways from how the customers are leveraging Ansible and the technology to drive their businesses forward to meet demanding customers where they are? >> I think you're seeing the script flipping a little bit here, where the folks that used to use Ansible for configuration are flipping to be on the front edge of the innovation strategy where what process to automate is going to drive the profitability and scale. Cause you're talking about things like skill gaps, workflows. These are business constructs and people These are assets so they have economic value. So before it was just, IT serve the business, configure some servers, do some stuff. When you start getting into automation where you have expertise around what this means, that's economic value. So I think you're going to see the personas change significantly in this community where they're on the front lines, kind of like developers are. That's why ops as code is to me a developer kind of vibe. That's going to completely change how operations runs in IT. And I think that's going to be a very interesting cultural shift. And some will make it, some won't. That's going to be a big thing. Some people say, I'm going to retire. I'm old school storage server person, or no, I'm the new guard. I'm going to be the new team. I'm going be on the right side of history here. So they're clearly going down that right path in my opinion. >> What's your overall summary in the last minute of what this event delivered the last couple of days in terms of really talking about the transformation of enterprises and industries through automation? >> I think the big takeaway from me in listening and reading the tea leaves was the Ansible company and staff and the community together. It was really a call for arms. Like, hey, we've had it right from the beginning. We're on the right wave and the wave's getting bigger. So expand your scope, uplevel your skills. They're on the right side of history. And I think the message was engage more. Bring more people in because it is open source, and if they are on that track, you're going to see more of hey, we got it right, let's continue. So they got platform release. They got the key products coming out after years of work. So you know, they're doing their work. And the message I heard was, it's bigger than we thought. So I think that's interesting. We'll see what that means. We're going to unpack that after the event in series of showcases. But yeah, it was very positive, I thought. Very positive. >> Yeah, I think there was definitely some surprises in there for them. John, thank you so much. It's been a pleasure co-hosting with you the last couple of days, really uncovering what Ansible is doing, what they're enabling customers in every industry to achieve. >> Been fun. >> Yes. All right for my co-host, John Furrier, I'm Lisa Martin. You've been watching theCUBE's coverage of Ansible Fest 2022 live from Chicago. We hope you take good care and we'll see you soon.

>>Hey guys. Welcome back to the Cubes coverage of Ansible Fast 2022. This is day two of our wall to wall coverage. Lisa Martin here with John Ferer. John, we're seeing this world where companies are saying if we can't automate it, we need to, The automation market is transforming. There's been a lot of buzz about that. A lot of technical chops here at Ansible Fest. >>Yeah, I mean, we've got a great guest here coming on Cuba alumni, Dean Newman, future room. He travels every event he's got. He's got his nose to the grindstone ear to the ground. Great analysis. I mean, we're gonna get into why it's important. How does Ansible fit into the big picture? It's really gonna be a great segment. The >>Board do it well, John just did my job for me about, I'll introduce him again. Daniel Newman, one of our alumni is Back Principal Analyst at Future and Research. Great to have you back on the cube. >>Yeah, it's good to join you. Excited to be back in Chicago. I don't know if you guys knew this, but for 40 years, this was my hometown. Now I don't necessarily brag about that anymore. I'm, I live in Austin now. I'm a proud Texan, but I did grow up here actually out in the west suburbs. I got off the plane, I felt the cold air, and I almost turned around and said, Does this thing go back? Yeah. Cause I'm, I've, I've grown thin skin. It did not take me long. I, I like the warm, Come on, >>I'm the saying, I'm from California and I got off the plane Monday. I went, Whoa, I need a coat. And I was in Miami a week ago and it was 85. >>Oh goodness. >>Crazy. So you just flew in. Talk about what's going on, your take on, on Ansible. We've talked a lot with the community, with partners, with customers, a lot of momentum. The flywheel of the community is going around and round and round. What are some of your perspectives that you see? >>Yeah, absolutely. Well, let's you know, I'm gonna take a quick step back. We're entering an era where companies are gonna have to figure out how to do more with less. Okay? We've got exponential data growth, we've got more architectural complexity than ever before. Companies are trying to discern how to deal with many different environments. And just at a macro level, Red Hat is one of the companies that is almost certainly gonna be part of this multi-cloud hybrid cloud era. So that should initially give a lot of confidence to the buying group that are looking at how to automate their environments. You're automating workflows, but really with, with Ansible, we're focused on automating it, automating the network. So as companies are kind of dig out, we're entering this recessionary period, Okay, we're gonna call it what it is. The first thing that they're gonna look at is how do we tech our way out of it? >>I had a wonderful one-on-one conversation with ServiceNow ceo, Bill McDermott, and we saw ServiceNow was in focus this morning in the initial opening session. This is the integration, right? Ansible integrating with ServiceNow. What we need to see is infrastructure automation, layers and applications working in concert to basically enable enterprises to be up and running all the time. Let's first fix the problems that are most common. Let's, let's automate 'em, let's script them. And then at some point, let's have them self resolving, which we saw at the end with Project Wisdom. So as I see it, automation is that layer that enterprises, boards, technologists, all can agree upon are basically here's something that can make our business more efficient, more profitable, and it's gonna deal with this short term downturn in a way that tech is actually gonna be the answer. Just like Bill and I said, let's tech our way out of it. >>If you look at the Red Hat being bought by ibm, you see Project Wisdom Project, not a product, it's a project. Project Wisdom is the confluence of research and practitioners kind of coming together with ai. So bringing AI power to the Ansible is interesting. Red Hat, Linux, Rel OpenShift, I mean, Red Hat's kind of position, isn't it? Kind of be in that right spot where a puck might be coming maybe. I mean, what do you think? >>Yeah, as analysts, we're really good at predicting the, the recent past. It's a joke I always like to make, but Red Hat's been building toward the future. I think for some time. Project Wisdom, first of all, I was very encouraged with it. One of the things that many people in the market probably have commented on is how close is IBM in Red Hat? Now, again, it's a $34 billion acquisition that was made, but boy, the cultures of these two companies couldn't be more different. And of course, Red Hat kind of carries this, this sort of middle ground layer where they provide a lot of value in services to companies that maybe don't use IBM at, at, for the public cloud especially. This was a great indication of how you can take the power of IBM's research, which of course has some of the world's most prolific data scientists, engineers, building things for the future. >>You know, you see things like yesterday they launched a, you know, an AI solution. You know, they're building chips, semiconductors, and technologies that are gonna power the future. They're building quantum. Long story short, they have these really brilliant technologists here that could be adding value to Red Hat. And I don't know that the, the world has fully been able to appreciate that. So when, when they got on stage and they kind of say, Here's how IBM is gonna help power the next generation, I was immediately very encouraged by the fact that the two companies are starting to show signs of how they can collaborate to offer value to their customers. Because of course, as John kind of started off with, his question is, they've kind of been where the puck is going. Open source, Linux hybrid cloud, This is the future. In the future. Every company's multi-cloud. And I said in a one-on-one meeting this morning, every company is going to probably have workloads on every cloud, especially large enterprises. >>Yeah. And I think that the secret's gonna be how do you make that evolve? And one of the things that's coming out of the industry over the years, and looking back as historians, we would say, gotta have standards. Well, with cloud, now people standards might slow things down. So you're gonna start to figure out how does the community and the developers are thinking it'll be the canary in the coal mine. And I'd love to get your reaction on that, because we got Cuban next week. You're seeing people kind of align and try to win the developers, which, you know, I always laugh cuz like, you don't wanna win, you want, you want them on your team, but you don't wanna win them. It's like a, it's like, so developers will decide, >>Well, I, I think what's happening is there are multiple forces that are driving product adoption. And John, getting the developers to support the utilization and adoption of any sort of stack goes a long way. We've seen how sticky it can be, how sticky it is with many of the public cloud pro providers, how sticky it is with certain applications. And it's gonna be sticky here in these interim layers like open source automation. And Red Hat does have a very compelling developer ecosystem. I mean, if you sat in the keynote this morning, I said, you know, if you're not a developer, some of this stuff would've been fairly difficult to understand. But as a developer you saw them laughing at jokes because, you know, what was it the whole part about, you know, it didn't actually, the ping wasn't a success, right? And everybody started laughing and you know, I, I was sitting next to someone who wasn't technical and, and you know, she kinda goes, What, what was so funny? >>I'm like, well, he said it worked. Do you see that? It said zero data trans or whatever that was. So, but if I may just really quickly, one, one other thing I did wanna say about Project Wisdom, John, that the low code and no code to the full stack developer is a continuum that every technology company is gonna have to think deeply about as we go to the future. Because the people that tend to know the process that needs to be automated tend to not be able to code it. And so we've seen every automation company on the planet sort of figuring out and how to address this low code, no code environment. I think the power of this partnership between IBM Research and Red Hat is that they have an incredibly deep bench of capabilities to do things like, like self-training. Okay, you've got so much data, such significant size models and accuracy is a problem, but we need systems that can self teach. They need to be able self-teach, self learn, self-heal so that we can actually get to the crux of what automation is supposed to do for us. And that's supposed to take the mundane out and enable those humans that know how to code to work on the really difficult and hard stuff because the automation's not gonna replace any of that stuff anytime soon. >>So where do you think looking at, at the partnership and the evolution of it between IBM research and Red Hat, and you're saying, you know, they're, they're, they're finally getting this synergy together. How is it gonna affect the future of automation and how is it poised to give them a competitive advantage in the market? >>Yeah, I think the future or the, the competitive space is that, that is, is ecosystems and integration. So yesterday you heard, you know, Red Hat Ansible focusing on a partnership with aws. You know, this week I was at Oracle Cloud world and they're talking about running their database in aws. And, and so I'm kind of going around to get to the answer to your question, but I think collaboration is sort of the future of growth and innovation. You need multiple companies working towards the same goal to put gobs of resources, that's the technical term, gobs of resources towards doing really hard things. And so Ansible has been very successful in automating and securing and focusing on very certain specific workloads that need to be automated, but we need more and there's gonna be more data created. The proliferation, especially the edge. So you saw all this stuff about Rockwell, How do you really automate the edge at scale? You need large models that are able to look and consume a ton of data that are gonna be continuously learning, and then eventually they're gonna be able to deliver value to these companies at scale. IBM plus Red Hat have really great resources to drive this kind of automation. Having said that, I see those partnerships with aws, with Microsoft, with ibm, with ServiceNow. It's not one player coming to the table. It's a lot of players. They >>Gotta be Switzerland. I mean they have the Switzerland. I mean, but the thing about the Amazon deal is like that marketplace integration essentially puts Ansible once a client's in on, on marketplace and you get the central on the same bill. I mean, that's gonna be a money maker for Ansible. I >>Couldn't agree more, John. I think being part of these public cloud marketplaces is gonna be so critical and having Ansible land and of course AWS largest public cloud by volume, largest marketplace today. And my opinion is that partnership will be extensible to the other public clouds over time. That just makes sense. And so you start, you know, I think we've learned this, John, you've done enough of these interviews that, you know, you start with the biggest, with the highest distribution and probability rates, which in this case right now is aws, but it'll land on in Azure, it'll land in Google and it'll continue to, to grow. And that kind of adoption, streamlining make it consumption more consumable. That's >>Always, I think, Red Hat and Ansible, you nailed it on that whole point about multicloud, because what happens then is why would I want to alienate a marketplace audience to use my product when it could span multiple environments, right? So you saw, you heard that Stephanie yesterday talk about they, they didn't say multiple clouds, multiple environments. And I think that is where I think I see this layer coming in because some companies just have to work on all clouds. That's the way it has to be. Why wouldn't you? >>Yeah. Well every, every company will probably end up with some workloads in every cloud. I just think that is the fate. Whether it's how we consume our SaaS, which a lot of people don't think about, but it always tends to be running on another hyperscale public cloud. Most companies tend to be consuming some workloads from every cloud. It's not always direct. So they might have a single control plane that they tend to lead the way with, but that is only gonna continue to change. And every public cloud company seems to be working on figuring out what their niche is. What is the one thing that sort of drives whether, you know, it is, you know, traditional, we know the commoditization of traditional storage network compute. So now you're seeing things like ai, things like automation, things like the edge collaboration tools, software being put into the, to the forefront because it's a different consumption model, it's a different margin and economic model. And then of course it gives competitive advantages. And we've seen that, you know, I came back from Google Cloud next and at Google Cloud next, you know, you can see they're leaning into the data AI cloud. I mean, that is their focus, like data ai. This is how we get people to come in and start using Google, who in most cases, they're probably using AWS or Microsoft today. >>It's a great specialty cloud right there. That's a big use case. I can run data on Google and run something on aws. >>And then of course you've got all kinds of, and this is a little off topic, but you got sovereignty, compliance, regulatory that tends to drive different clouds over, you know, global clouds like Tencent and Alibaba. You know, if your workloads are in China, >>Well, this comes back down at least to the whole complexity issue. I mean, it has to get complex before it gets easier. And I think that's what we're seeing companies opportunities like Ansible to be like, Okay, tame, tame the complexity. >>Yeah. Yeah, I totally agree with you. I mean, look, when I was watching the demonstrations today, my take is there's so many kind of simple, repeatable and mundane tasks in everyday life that enterprises need to, to automate. Do that first, you know? Then the second thing is working on how do you create self-healing, self-teaching, self-learning, You know, and, and I realize I'm a little broken of a broken record at this, but these are those first things to fix. You know, I know we want to jump to the future where we automate every task and we have multi-term conversational AI that is booking our calendars and driving our cars for us. But in the first place, we just need to say, Hey, the network's down. Like, let's make sure that we can quickly get access back to that network again. Let's make sure that we're able to reach our different zones and locations. Let's make sure that robotic arm is continually doing the thing it's supposed to be doing on the schedule that it's been committed to. That's first. And then we can get to some of these really intensive deep metaverse state of automation that we talk about. Self-learning, data replication, synthetic data. I'm just gonna throw terms around. So I sound super smart. >>In your customer conversations though, from an looking at the automation journey, are you finding most of them, or some percentage is, is wanting to go directly into those really complex projects rather than starting with the basics? >>I don't know that you're, you're finding that the customers want to do that? I think it's the architecture that often ends up being a problem is we as, as the vendor side, will tend to talk about the most complex problems that they're able to solve before companies have really started solving the, the immediate problems that are before them. You know, it's, we talk about, you know, the metaphor of the cloud is a great one, but we talk about the cloud, like it's ubiquitous. Yeah. But less than 30% of our workloads are in the public cloud. Automation is still in very early days and in many industries it's fairly nascent. And doing things like self-healing networks is still something that hasn't even been able to be deployed on an enterprise-wide basis, let alone at the industrial layer. Maybe at the company's on manufacturing PLAs or in oil fields. Like these are places that have difficult to reach infrastructure that needs to be running all the time. We need to build systems and leverage the power of automation to keep that stuff up and running. That's, that's just business value, which by the way is what makes the world go running. Yeah. Awesome. >>A lot of customers and users are struggling to find what's the value in automating certain process, What's the ROI in it? How do you help them get there so that they understand how to start, but truly to make it a journey that is a success. >>ROI tends to be a little bit nebulous. It's one of those things I think a lot of analysts do. Things like TCO analysis Yeah. Is an ROI analysis. I think the businesses actually tend to know what the ROI is gonna be because they can basically look at something like, you know, when you have an msa, here's the downtime, right? Business can typically tell you, you know, I guarantee you Amazon could say, Look for every second of downtime, this is how much commerce it costs us. Yeah. A company can generally say, if it was, you know, we had the energy, the windmills company, like they could say every minute that windmill isn't running, we're creating, you know, X amount less energy. So there's a, there's a time value proposition that companies can determine. Now the question is, is about the deployment. You know, we, I've seen it more nascent, like cybersecurity can tend to be nascent. >>Like what does a breach cost us? Well there's, you know, specific costs of actually getting the breach cured or paying for the cybersecurity services. And then there's the actual, you know, ephemeral costs of brand damage and of risks and customer, you know, negative customer sentiment that potentially comes out of it. With automation, I think it's actually pretty well understood. They can look at, hey, if we can do this many more cycles, if we can keep our uptime at this rate, if we can reduce specific workforce, and I'm always very careful about this because I don't believe automation is about replacement or displacement, but I do think it is about up-leveling and it is about helping people work on things that are complex problems that machines can't solve. I mean, said that if you don't need to put as many bodies on something that can be immediately returned to the organization's bottom line, or those resources can be used for something more innovative. So all those things are pretty well understood. Getting the automation to full deployment at scale, though, I think what often, it's not that roi, it's the timeline that gets misunderstood. Like all it projects, they tend to take longer. And even when things are made really easy, like with what Project Wisdom is trying to do, semantically enable through low code, no code and the ability to get more accuracy, it just never tends to happen quite as fast. So, but that's not an automation problem, That's just the crux of it. >>Okay. What are some of the, the next things on your plate? You're quite a, a busy guy. We, you, you were at Google, you were at Oracle, you're here today. What are some of the next things that we can expect from Daniel Newman? >>Oh boy, I moved Really, I do move really quickly and thank you for that. Well, I'm very excited. I'm taking a couple of work personal days. I don't know if you're a fan, but F1 is this weekend. I'm the US Grand Prix. Oh, you're gonna Austin. So I will be, I live in Austin. Oh. So I will be in Austin. I will be at the Grand Prix. It is work because it, you know, I'm going with a number of our clients that have, have sponsorships there. So I'll be spending time figuring out how the data that comes off of these really fun cars is meaningfully gonna change the world. I'll actually be talking to Splunk CEO at the, at the race on Saturday morning. But yeah, I got a lot of great things. I got a, a conversation coming up with the CEO of Twilio next week. We got a huge week of earnings ahead and so I do a lot of work on that. So I'll be on Bloomberg next week with Emily Chang talking about Microsoft and Google. Love talking to Emily, but just as much love being here on, on the queue with you >>Guys. Well we like to hear that. Who you're rooting for F one's your favorite driver. I, >>I, I like Lando. Do you? I'm Norris. I know it's not necessarily a fan favorite, but I'm a bit of a McLaren guy. I mean obviously I have clients with Oracle and Red Bull with Ball Common Ferrari. I've got Cly Splunk and so I have clients in all. So I'm cheering for all of 'em. And on Sunday I'm actually gonna be in the Williams Paddock. So I don't, I don't know if that's gonna gimme me a chance to really root for anything, but I'm always, always a big fan of the underdog. So maybe Latifi. >>There you go. And the data that comes off the how many central unbeliev, the car, it's crazy's. Such a scientific sport. Believable. >>We could have Christian, I was with Christian Horner yesterday, the team principal from Reside. Oh yeah, yeah. He was at the Oracle event and we did a q and a with him and with the CMO of, it's so much fun. F1 has been unbelievable to watch the momentum and what a great, you know, transitional conversation to to, to CX and automation of experiences for fans as the fan has grown by hundreds of percent. But just to circle back full way, I was very encouraged with what I saw today. Red Hat, Ansible, IBM Strong partnership. I like what they're doing in their expanded ecosystem. And automation, by the way, is gonna be one of the most robust investment areas over the next few years, even as other parts of tech continue to struggle that in cyber security. >>You heard it here. First guys, investment in automation and cyber security straight from two analysts. I got to sit between. For our guests and John Furrier, I'm Lisa Martin, you're watching The Cube Live from Chicago, Ansible Fest 22. John and I will be back after a short break. SO'S stick around.

>>Hey everyone. Welcome back to Chicago. The Cube is excited to be live on day two of Ansible Fest, 2022. Lisa Martin and John Fur. You're here having some great conversations, a lot of cube alumni, a lot of wisdom from the Ansible community coming at you on this program this week. You know, John, we've been, we've been hearing stories about the power and the capabilities and the collective wisdom of the Ansible community. You can feel it here. Yeah, there's no doubt about that. It's, Ansible is nothing, as Stephanie Chair said yesterday, if not a community and the significant contributions that it makes over and over again, or it's fuel. >>I mean the power of the community is what drives Ansible is gonna drive the future of, I think, cloud in our next generation modern application environment. And it's collective intelligence. It's a production system at the end of the day. And I think these guys have harnessed it. So it should be a really great segment to talk about all the contributor work that's been done. So I'm looking forward to it. >>We've got two great alumni here to talk about the contributor work, how you can get involved. Please welcome back to the cube. Carol Chen, principal community architect at Red Hat. Adam Miller joins us as well, fresh from the keynote stage senior principal software engineer at Red Hat. Guys, great to have you on the cube. Great to be here. Yeah, thank you. So we, we talked, we enjoyed your keynotes, Adam, and what you were talking about on stage, the Ansible contributor summit. That's, you guys have been doing what, this is the seven you've had seven so far in just a couple of years. >>Well, we had seven virtual contributor summits. >>Seven virtual. This is the first Monday was the first in person in. >>First in person since the pandemic and actually the 15th contributor summit overall >>15th overall. Talk about the contributor summits, what the contributors are able to do and the influence that it's having on Ansible Red Hat and what people are able to do with cloud. At the Edge automation. Yeah. >>So our community contributors have always had ways to influence and contribute to the project. But the contributor Summit is really a place where we can get people together, preferably in the same place so that we can, you know, have a really great dynamic conversations and interactions. But we also want to make sure that we don't leave out people who have been constantly online joining us. So this year we are so happy to be here in Chicago in person. We've had about 60 to 70 here joining us. And at first I thought maybe we'll have one third of the attendees joining online because about 30 to 40 people signed up to join online. But in the end, we have more than 100 per people watching our live stream. So that's more than half of the attendees overall, were joining us online. So that really shows where, you know, the contributors are interested in participating for >>Develop. Right. Yeah, it's been, it's been interesting. It's been since 2019, since the in-person Ansible Fest in Atlanta. Now we're in Chicago, we had the pandemic. Couple interesting observations from our side that I wanna get your reaction to Adam Carol. And that is one Ansible's relevance has grown significantly since then. Just from a cloud growth standpoint, developer open source standpoint, and how people work and collaborate has changed. So your contributor based in your community is getting more powerful in scope, in my opinion. Like in, as they become, have the keys to the kingdom in the, in their respective worlds as it gets bigger and larger. So the personas are changing, the makeup of the community's changing and also how you guys collaborate is changing. Can you share your, what's going on with those two dynamics? Cause I think that power dynamic is, is looking really good. How are you guys handling >>That? Yeah, so I mean, I, I had the opportunity to represent the community on stage yesterday as part of the keynote and talk to this point specifically is one of the things that we've seen is the project has had the opportunity to kind of grow and evolve. There's been certain elements that have had to kind of decompose from a technology perspective. We actually had to kind of break it apart and change the architecture a little bit and move things into what are called Ansible collections, which, you know, folks here are very familiar with No One Love. And we've seen a lot of community work in the form of working groups coalesce around those organically. However, they've done so in kind of different ways. They, they pick tools and collaboration platforms that are popular to their subject matter expertise audience and things like that. So we find ourselves in a place where kind of the, the community itself had more or less segmented naturally in a way. And we needed to find ways to, you know, kind of ke that >>Fragmentation by demographics or by expertise or both as >>A Mostly, mostly expertise. Yeah. And so there was a open source technology called Matrix. It is a open source, standardized, federated messaging platform that we're able to use to start to bridge back some of those communities that have kind of broken off and, and made their their own home elsewhere on the internet. So now we're able to, for example, the right, the docs organization, they had a, a group of people who was very interested in contributing to the Ansible documentation, but they'd already self-organized on Discord. And what was interesting there is the existing team for the Ansible documentation, they were already on internet Relay Chat, also known as irc. And Matrix allowed us to actually bring those two together and bridge that into the other matrix cha chat channels that we had. So now we're able to have people from all over the world in different areas and different platforms, coalesce and, and cross. It's like a festival cross pollinate. Yeah. >>And you're meeting the contributors exactly where they are and where they want to be, where they're comfortable. >>Yes. Yeah, we always say we, we reach out to where they are. So, >>And, and, and much in the way that Ansible has the capability to reach out to things in their own way, Right. And allow that subject matter expertise to, you know, cause the technology has the potential and possibility and capability to talk to anything over any protocol. We're able to do, you know, kind of the same thing with Matrix, allowing us to bridge into any chat platform that it has support for bridging and, and we're able to bring a lot of people >>Together. Yeah. And how's that, how's the feedback been on that so far? >>I, I think it has been very positive. For example, I want to highlight that the technical writers that we have contributing via Discord is actually a group from Nigeria. And Dave also participated in the contributor summit online virtually joining us in, in, you know, on the matrix platform. So that, that bridge that really helps to bring together people from different geographical regions and also different topics and arenas like that. >>So what were some of the outcomes of the contributor summit? The, the first in person in a while, great. That you guys were able to do seven virtually during the pandemic. That's hard. It's hard to get people together. You, there's so much greatness and innovation that comes when we're all together in person that just can't replicate by video. You can do a lot. Right. But talk about some of the outcomes from Monday. What were some of the feedback? What were some of the contributions that you think are really going to impact the community? >>I think for a lot of us, myself included, the fact that we are in person and meeting people face to face, it helps to really build the connections. And when we do talk about contribution, the connection is so important that you understand, well this person a little bit about their background, what they've done for the SPO project and or just generally what, what they're interested in that builds the rapport and connection that helps, you know, further, further collaboration in the future. Because maybe on that day we did not have any, you know, co contributions or anything, but the fact that we had a chance to sit together in the same place to discuss things and share new ideas, roadmaps is really the, the kind of a big step to the future for our community. Yes, >>Yes. And in a lot of ways we often online the project has various elements that are able to function asynchronously. So we work very well globally across many time zones. And now we were able to get a lot of people in the same place at the same time, synchronously in the same time zone. And then we had breakout sessions where the subject matter, you know, working groups were able to kind of go and focus on things that maybe have been taking a little while to discuss in, in that asynchronous form of communication and do it synchronously and, you know, be in the same room and work on things. It's been, it's been fantastic >>Developers there, like they, they take to asynchronous like fish to water. It's not a problem. But I do want to ask if there's any observations that you guys have had now that we're kind of coming out of that one way, but the pandemic, but the world's changed. It's hybrid, hybrid work environment, steady state. So we see that. Any observations on your end on what's new that you observed that people are gravitating to? Is there a pattern of styles is or same old self-governing, or what's new? What do you see that's coming out of the pandemic that might be a norm? >>I I think that even though people are excited to get back in person, there are, things have changed, like you said, and we have to be more aware of, there are people who think that not be in person, it's okay. And that's how they want to do it. And we have to make sure that they, they are included. So we, we did want to make a high priority for online participation in this event. And like I said, even though only 4 30, 40 people signed up to join us online initially, so that it was what we were expecting, but in the end, more than 100 people were watching us and, and joining participation in >>Actually on demand consumption be good too, >>Right? Yeah. So, you know, I think going forward that is probably the trend. And as, as much as we, we love being in person, we, we want this to continue that we, we take care of people who are, has been constantly participating online and contributing you >>Meaning again, meaning folks where they are, but also allowing the, the, those members that want to get together to, to collaborate in person. I can only imagine the innovation that's gonna come even from having part of the back, Right. >>And, and not to continue to harp on the matrix point, but it, it's been very cool because Matrix has the ability to do live video sessions using open source another to open source technology called jy. So we're able to actually use the same place that we normally find ourselves, you know, congregating and collaborating for the project itself in an asynchronous and, you know, somewhat synchronous way to also host these types of things that are, are now hybrid that used to be, you know, all one way or all the other. Yeah. And it's been, it's >>Been incredible. Integration is, the integration is have been fascinating to watch how you guys do that. And also, you know, with q we've been virtual too. It's like, it's like people don't want another microsite, but they want a more of a festival vibe, a hub, right? Like a place to kind of check in and have choice, not get absolutely jammed into a, you know, forum or, you know, or whatever. Hey, if you wanna be on Discord, be on Discord, right? Why >>Not? And we still, you know, we do still have our asynchronous forms of >>Work through >>Our get GitHub. We have our projects, we have our issues, we have our, you know, wiki, we have various elements there that everybody can continue to collaborate on. And it's all been, it's all been very good. >>Speaking of festivals, octoberfest that's going on, not to be confused with Octoberfest, that was last month. Talk about how the Ansible project and the Ansible community is involved in Octoberfest. Give us the dates, Carol. So >>YesTo Fest is a annual thing in October. So October Octoberfest, I think it's organized by Digital Ocean for the past eight or nine years. And it's really a, a way to kind of encourage people to contribute to open source projects. So it's not anal specific, but we as an Ansible project encourage people to take this opportunity to, you know, a lot of them doing their first contributions during this event. And when, when we first announced, we're participating in Octoberfest within the first four days of October, which is over a weekend actually. We've had 24 contributions, it, 24 issues fixed, which is like amazing, like, you know, just the interest and the, the momentum that we had. And so far until I just checked with my teammates this morning that we've had about 35 contributions so far during the month, which is, and I'm sorry, I forgot to mention this is only for Ansible documentation. So yeah, specifically. And, and that's also one thing we want to highlight, that contributions don't just come in code in, you know, kind of software side, but really there's many ways to contribute and documentation is such a, a great way for first time users, first time contributors to get involved. So it's really amazing to see these contributions from all over the world. And also partly thanks to the technical writers in Nigeria kind of promoting and sharing this initiative. And it's just great to see the, the results from that. Can >>You double click on the different ways of contribution? You mentioned a couple documentation being one, code being the other, but what is the breadth of opportunities that the contributors have to contribute to the project? >>Oh, there's, there's so many. So I actually take care more of outreach efforts in the community. So I helped to organize events and meetups from around the world. And now that we're slowly coming out of the pandemic, I've seen more and more in person meetups. I was just talking to someone from Minneapolis, they're trying to get, get people back together again. They have people in Singapore, in Netherlands from pretty much, you know, all corners of the globe wanting to form not just for the Ansible project, but the local kind of connection with the re people in the region, sometimes in their own language, in their local languages to really work together on the project and just, >>You know, you to create a global Yeah. Network, right? I mean it's like Ansible Global. >>Exactly. >>Create local subnets not to get all networking, >>Right? >>Yeah. >>Yeah. One, one quick thing I want to touch on Theto Fest. I think it's a great opportunity for existing contributors to mentor cause many people like to help bring in new contributors and this is kind of a focal point to be able to focus on that. And then to, to the the other point we, you know, it, it's been, it's been extremely powerful to see as we return these sub communities pop up and, and kind of work with themselves, so on different ways to contribute. So code is kind of the one that gets the most attention. I think documentation I think is a unsung hero, highly important, great way. The logistical component, which is invaluable because it allows us to continue with our adoption and evangelization and things like that. So specifically adoption and evangelize. Evangelization is another place that contributors can join and actually spawn a local meetup and then connect in with the existing community and try to, you know, help increase the network, create a new subject. Yeah. >>Yeah. Network affects huge. And I think the thing that you brought up about reuse is, is part of that whole things get documented properly. The leverage that comes out of that just feeds into the system that flywheel. Absolutely. I mean it's, that's how communities are supposed to work, right? Yep. Yes. >>That's what I was just gonna comment on is the flywheel effect that it's clearly present and very palpable. Thank you so much for joining John, me on the program, talking about the contributors summit, the ways of contribution, the impacts that are being made so far, what Octoberfest is already delivering. And we're, we still have about 10 days or so left in October, so there's still more time for contributors to get involved. We thank you so much for your insights and your time. Thank >>You. Thank you so much for having us. >>Our pleasure. For our guests and John Purer, I'm Lisa Martin. You're watching The Cube Live from Chicago, day two of our coverage of Red Hat Ansible Summit 22. We will see you right n after this short break with our next guest.

>>Good morning live from Chicago. It's the cube on the floor at Ansible Fast 2022. This is day two of our wall to wall coverage. Lisa Martin here with John Furrier. John, we're gonna be talking next in the segment with two alumni about what Red Hat and IBM are doing to give Ansible users AI superpowers. As one of our alumni guests said, just off the keynote stage, we're nearing an inflection point in ai. >>The power of AI with Ansible is really gonna be an innovative, I think an inflection point for a long time because Ansible does such great things. This segment's gonna explore that innovation, bringing AI and making people more productive and more importantly, you know, this whole low code, no code, kind of right in the sweet spot of the skills gap. So should be a great segment. >>Great segment. Please welcome back two of our alumni. Perry is here, the Chief scientist, IBM Research and IBM Fellow. And Tom Anderson joins us once again, VP and general manager at Red Hat. Gentlemen, great to have you on the program. We're gonna have you back. >>Thank you for having >>Us and thanks for joining us. Fresh off the keynote stage. Really enjoyed your keynote this morning. Very exciting news. You have a project called Project Wisdom. We're talking about this inflection point in ai. Tell the audience, the viewers, what is Project Wisdom And Wisdom differs from intelligence. How >>I think Project Wisdom is really about, as I said, sort of combining two major forces that are in many ways disrupting and, and really constructing many a aspects of our society, which are software and AI together. Yeah. And I truly believe it's gonna result in a se shift on how not just enterprises, but society carries forefront. And as I said, intelligence is, is, I would argue at least artificial intelligence is more, in some ways mechanical, if I may say it, it's about algorithms, it's about data, it's about compute. Wisdom is all about what is truly important to bring out. It's not just about when you bring out a, a insight, when you bring out a decision to be able to explain that decision as well. It's almost like humans have wisdom. Machines have intelligence and, and it's about project wisdom. That's why we called it wisdom. >>Because it is about being a, a assistant augmenting humans. Just like be there with the humans and, and almost think of it as behave and interact with them as another colleague will versus intelligence, which is, you know, as I said, more mechanical is about data. Computer algorithms crunch together and, and we wanna bring the power of project wisdom and artificial intelligence to developers to, as you said, close the skills gap to be able to really make them more productive and have wisdom for Ansible be their assistant. Yeah. To be able to get things for them that they would find many ways mundane, many ways hard to find and again, be an assistant and augmented, >>You know, you know what's interesting, I want to get into the origin, how it all happened, but interesting IBM research, well known for the deep tech, big engineering. And you guys have been doing this for a long time, so congratulations. But it's interesting here at this event, even on stage here event, you're starting to see the automation come in. So the question comes up, scale. So what happens, IBM buys Red Hat, you go raid the, the raid, the ip, Trevor Treasure trove of ai. I mean this cuz this is kind of like bringing two killer apps together. The Ansible configuration automation layer with ai just kind of a, >>Yeah, it's an amazing relationship. I was gonna say marriage, but I don't wanna say marriage cause I may be >>Last. I didn't mean say raid the Treasure Trobe, but the kind of >>Like, oh my God. An amazing relationship where we bring all this expertise around automation, obviously around IP and application infrastructure automation and IBM research, Richie and his team bring this amazing capacity and experience around ai. Bring those two things together and applying AI to automation for our teams is so incredibly fantastic. I just can't contain my enthusiasm about it. And you could feel it in the keynote this morning that Richie was doing the energy in the room and when folks saw that, it's just amazing. >>The geeks are gonna love it for sure. But here I wanna get into the whole evolution. Computers on computers, remember the old days thinking machines was a company generations ago that I think they've sold or went outta business, but self-learning, learning machines, computers, programming, computers was actually on your slide you kind of piece out this next wave of AI and machine learning, starting with expert systems really kind of, I'm almost say static, but like okay programs. Yeah, yeah. And then now with machine learning and that big debate was unsupervised, supervised, which is not really perfect. Deep learning, which now explores some things, but now we're at another wave. Take, take us through the thought there explaining what this transition looks like and why. >>I think we are, as I said, we are really at an inflection point in the journey of ai. And if ai, I think it's fair to say data is the pain of ai without data, AI doesn't exist. But if I were to train AI with what is known as supervised learning or or data that is labeled, you are almost sort of limited because there are only so many people who have that expertise. And interestingly, they all have day jobs. So they're not just gonna sit around and label this for you. Some people may be available, but you know, this is not, again, as I as Tom said, we are really trying to apply it to some very sort of key domains which require subject matter expertise. This is not like labeling cats and dogs that everybody else in the board knows there are, the community's very large, but still the skills to go around are not that many. >>And I truly believe to apply AI to the, to the word of, you know, enterprises information technology automation, you have to have unsupervised learning and that's the only way to skate. Yeah. And these two trends really about, you know, information technology percolating across every enterprise and unsupervised learning, which is learning on this very large amount of data with of course know very large compute with some very powerful algorithms like transformer architectures and others which have been disrupting the, the domain of natural language as well are coming together with what I described as foundation models. Yeah. Which anybody who plays with it, you'll be blown away. That's literally blown away. >>And you call that self supervision at scale, which is kind of the foundation. So I have to ask you, cuz this comes up a lot with cloud, cloud scale, everyone tells horizontally scalable cloud, but vertically specialized applications where domain expertise and data plays. So the better the data, the better the self supervision, better the learning. But if it's horizontally scalable is a lot to learn. So how do you create that data ops where it's where the machines are gonna be peaked to maximize what's addressable, but what's also in the domain too, you gotta have that kind of diversity. Can you share your thoughts on that? >>Absolutely. So in, in the domain of foundation models, there are two main stages I would say. One is what I'll describe as pre-training, which is think of it as the, the machine in this particular case is knowledgeable about the domain of code in general. It knows syntax of Python, Java script know, go see Java and so, so on actually, and, and also Yammel as well, which is obviously one would argue is the domain of information technology. And once you get to that level, it's a, it's almost like having a developer who knows all of this but may not be an expert at Ansible just yet. He or she can be an expert at Ansible but is not there yet. That's what I'll call background knowledge. And also in the, in the case of foundation models, they are very adept at natural language as well. So they can connect natural language to code, but they are not yet expert at the domain of Ansible. >>Now there's something called, the second stage of learning is called fine tuning, which is about this data ops where I take data, which is sort of the SME data in this particular case. And it's curated. So this is not just generic data, you pick off GitHub, you don't know what exists out there. This is the data which is governed, which we know is of high quality as well. And you think of it as you specialize the generic AI with pre-trained AI with that data. And those two stages, including the governance of that data that goes into it results in this sort of really breakthrough technology that we've been calling Project Wisdom for. Our first application is Ansible, but just watch out that area. There are many more to come and, and we are gonna really, I'm really excited about this partnership with Red Hat because across IBM and research, I think where wherever we, if there is one place where we can find excited, open source, open developer community, it is Right. That's, >>Yeah. >>Tom, talk about the, the role of open source and Project Wisdom, the involvement of the community and maybe Richard, any feedback that you've gotten since coming off stage? I'm sure you were mobbed. >>Yeah, so for us this is, it's called Project Wisdom, not Product Wisdom. Right? Sorry. Right. And so, no, you didn't say that but I wanna just emphasize that it is a project and for us that is a key word in the upstream community that this is where we're inviting the community to jump on board with us and bring their expertise. All these people that are here will start to participate. They're excited in it. They'll bring their expertise and experience and that fine tuning of the model will just get better and better. So we're really excited about introducing this now and involving the community because it's super nuts. Everything that Red Hat does is around the community and this is no different. And so we're really excited about Project Wisdom. >>That's interesting. The project piece because if you see in today's world the innovation strategy before where we are now, go back to say 15 years ago it was of standard, it's gotta have standard bodies. You can still innovate and differentiate, but yet with open source and community, it's a blending of research and practitioners. I think that to me is a big story here is that what you guys are demonstrating is the combination of research and practitioners in the project. Yes. So how does this play out? Cuz this is kind of like how things are gonna get done in the cloud cuz Amazon's not gonna just standardize their stack at at higher level services, nor is Azure and they might get some plumbing commonalities below, but for Project Project Wisdom to be successful, they can, it doesn't need to have standards. If I get this right, if I can my on point here, what do you guys think about that? React to that? Yeah, >>So I definitely, I think standardization in terms of what we will call ML ops pipeline for models to be deployed and managed and operated. It's like models, like any other code, there's standardization on DevOps ops pipeline, there's standardization on machine learning pipeline. And these models will be deployed in the cloud because they need to scale. The only way to scale to, you know, thousands of users is through cloud. And there is, there are standard pipelines that we are working and architecting together with the Red Hat community leveraging open source packages. Yeah. Is really to, to help scale out the AI models of wisdom together. And another point I wanted to pick up on just what Tom said, I've been sort of in the area of productizing AI for for long now having experience with Watson as well. The only scenario where I've seen AI being successful is in this scenario where, what I describe as it meets the criteria of flywheel of ai. >>What do I mean by flywheel of ai? It cannot be some research people build a model. It may be wowing, but you roll it out and there's no feedback. Yeah, exactly. Okay. We are duh. So what actually, the only way the more people use these models, the more they give you feedback, the better it gets because it knows what is right and what is not right. It will never be right the first time. Actually, you know, the data it is trained on is a depiction of reality. Yeah. It is not a reality in itself. Yeah. The reality is a constantly moving target and the only way to make AI successful is to close that loop with the community. And that's why I just wanted to reemphasize the point on why community is that important >>Actually. And what's interesting Tom is this is a difference between standards bodies, old school and communities. Because developers are very efficient in their feedback. Yes. They jump to patterns that serve their needs, whether it's self-service or whatever. You can kind of see what's going on. Yeah. It's either working or not. Yeah, yeah, >>Yeah. We get immediate feedback from the community and we know real fast when something isn't working, when something is working, there are no problems with the flow of data between the members of the community and, and the developers themselves. So yeah, it's, I'm it's great. It's gonna be fantastic. The energy around Project Wisdom already. I bet. We're gonna go down to the Project Wisdom session, the breakout session, and I bet you the room will be overflowed. >>How do people get involved real quick? Get, get a take a minute to explain how I would get involved. I'm a community member. Yep. I'm watching this video, I'm intrigued. This has got me enthusiastic. How do I get more confident with this opportunity? >>So you go to, first of all, you go to red hat.com/project Wisdom and you register your interests and you wanna participate. We're gonna start growing this process, bringing people in, getting ready to make the service available to people to start using and to experiment with. Start getting their feedback. So this is the beginning of, of a journey. This isn't the, you know, this isn't the midpoint of a journey, this is the begin. You know, even though the work has been going on for a year, this is the beginning of the community journey now. And so we're gonna start working together through channels like Discord and whatnot to be able to exchange information and bring people in. >>What are some of the key use cases, maybe Richie are starting with you that, that you think maybe dream use cases that you think the community will help to really uncover as we're looking at Project Wisdom really helping in this transformation of ai. >>So if I focus on let's say Ansible itself, there are much wider use cases, but Ansible itself and you know, I, I would say I had not realized, I've been working on AI for Good for long, but I had not realized the excitement and the power of Ansible community itself. It's very large, it's very bottom sum, which I love actually. But as I went to lot of like CTOs and CIOs of lot of our customers as well, it was becoming clear the use cases of, you know, I've got thousand Ansible developers or IT or automation experts. They write code all the time. I don't know what all of this code is about. So the, the system administrators, managers, they're trying to figure out sort of how to organize all of this together and think of it as Google for finding all of these automation code automation content. >>And I'm very excited about not just the use cases that we demonstrated today, that is beginning of the journey, but to be able to help enterprises in finding the right code through natural language interfaces, generating the code, helping Del us debug their code as well. Giving them predictive insights into this may happen. Just watch out for it when you deploy this. Something like that happened before, just watch out for it as well. So I'm, I'm excited about the entire life cycle of IT automation, Not just about at the build time, but also at the time of deployment. At the time of management. This is just a start of a journey, but there are many exciting use cases abound for Ansible and beyond. >>It's gonna be great to watch this as it unfolds. Obviously just announcing this today. We thank you both so much for joining us on the program, talking about Project wisdom and, and sharing how the community can get involved. So you're gonna have to come back next year. We're gonna have to talk about what's going on. Cause I imagine with the excitement of the community and the volume of the community, this is just the tip of the iceberg. Absolutely. >>This is absolutely exactly. You're excited about. >>Excellent. And you should be. Congratulations. Thank, thanks again for joining us. We really appreciate your insights. Thank you. Thank >>You for having >>Us. For our guests and John Furrier, I'm Lisa Barton and you're watching The Cube Lie from Chicago at Ansible Fest 22. This is day two of wall to wall coverage on the cube. Stick around. Our next guest joins us in just a minute.

>>Good morning, everyone from Chicago Live. The Cube is live at Ansible Fast 2022. Lisa Martin and John Ferer are here for two days of multiple coverage on the cube. Very excited to be back in person. Ansible's 10th anniversary, the first in-person event. John, since 2019. Yeah, great to be perfect. One of the nuggets dropped this morning and I know you was Opss code. >>Yeah, we're gonna hear about that OPSIS code here in this segment. We're gonna get in, but the leader of the, the business unit at Ansible, part of Red Hat. So look forward >>To this. Exactly. Tom Anderson joins us, one of our alumni. Welcome back to the program. Thank you. The VP and general manager of Red Hat. First of all, how great is it to be back in person with live guests and an engaged audience and then robust community? >>It is amazing. It really is. I kind of question whether this day was ever gonna come again after three years of being apart, but to see the crowd here and to see, like you said, the energy in the room this morning and the keynotes, it's fantastic. So it's fa I just couldn't be happier. >>So opsis code nugget drop this morning. Yep. We wanna dissect that with you as, as that was mentioned in the keynote this morning. As Ansible is pushing into the cloud and and into the edge, what does OPSIS code mean for end users and how is it gonna help them to use a term that was used a lot in the keynote level up their automation? >>Yeah, so what we see is, look, the day zero, day one provisioning of infrastructure. There's lots of tools, there's lots of ways to do that. Again, it's just the company's ambition and dedication to doing it. The tools are there, they can do that. We see the next big opportunity for automation is in day two operations. And what's happening right now in ops is that you have multiple clouds, you've got multiple data centers and now you've got edge environments. The number of things to manage on a day-to-day basis is only increasing. The complexity is only increasing this idea of a couple years ago where we're gonna do shift everything left onto the developer. It's nice idea, but you still have to operate these environments on a day two basis. So we see this opportunity as opsis code, just like we did infrastructures code, just like we did configuration as code. We see the next frontier as operations code. >>Yeah, and this is really a big trend as you know with cube reporting a lot on the cloud native velocity of the modern application developer these days, they're under, they're, it's a great time to be a software developer because all the open source goodness is happening, but they're going faster. They want self-service, they want it built in secure, They need guardrails, they need, they need faster ops. So that seems to be the pressure point. Is ops as code going to be that solution? Because you have a lot of people talking about multi-cloud, multiple environments, which sounds great on paper, but when you try to execute it, Yeah, there's complexity. So you know, the goal of complexity management has really been one of the key things around ops. How do I keep speed up and how do I reduce the complexities? These are big. How does, how does ops code fit into that? >>Yeah, so look, we, we see Ansible as this common automation back plane, if you will, that goes across all of these environments. It provides a common abstraction layer so that whether you're running on Azure, whether you're a GCP or whether you're AWS or whether you're, you know, a PLC out on a shop industrial edge floor with a plc, each of those things need to be automated. If we can abstract that into a common automation language, then that allows these domain experts to be able to offer their services to developers in a way that promotes the acceleration, if you will, of those developers tasks. And that developer doesn't have to know about the underlying complexities of storage or database or cloud or edge. They can just do their >>Job. You know, Tom, one of the things I observed in Keynote, and it comes across every time I, we have an event and in person it's more amplified. Cause you see it, the loyalty of the customer base. You have great community. It's very not corporate like here. It's very no big flashy news. But there's some news, hard news, It's very community driven. Check the box there. So continuing on the roots, I wanna get your thoughts on how now the modern era we're in, in this world, the purchasing power, again, I mentioned multicloud looks good on paper, which every CX I wanna be multiple clouds. I want choice now. Now you talk to the people running things like, whoa, hold on, boss. Yeah, the bottoms up is big part of the selection process of how people select and buying consume technology with open source, you don't need to like do a full buy. You can use open source and then get Ansible. Yeah. This is gonna be a big part of how the future of buying product is and implementing it. So I think it's gonna be a groundswell, bottoms up market in this new cloud native with O in the ops world. What's your reaction to that? What's your thoughts? >>So here, here's my thoughts. The bulk of the people here are practitioners. They love Ansible, they use Ansible in their day to day job. It's how it helped, makes 'em successful. Almost every executive that I go out and talk to and our customers, they tell me one of their number one pro or their number one problem is attracting you talent and retaining the talent that they have. And so how can they do that? They can give them the tools to do their job, the tools that they actually like. So not a top down, you know, old fashioned systems management. You're gonna use this tool whether you like it or not. But that bottoms up swell of people adopting open source tools like Ansible to do their job and enjoy it. So I see it as a way of the bottoms up addressing the top down initiative of the organization, which is skills retention, skills enhancement. And that's what we focus on here at this event. Are the practitioners, >>Is that the biggest customer conversation topic these days? Is this the skills gap, retention, attraction talent? Would you say it's more expansive as the organizations are so different? >>Well, so a lot of the folks that I meet are, you know, maybe not sea level, but they're executives in the organization, right? So they're struggling with attract, you know, pretty much everywhere I go, I was in Europe this summer, conversation was always the same. We got two problems. Tracking people. We can't find people, people we find we can't afford. So we need to automate what they would do. And, and then the second piece is the complexity of our environment is growing, right? I'm being asked to do more and I can't find more people to do it. What's my solution? It's automation, you know, at the end of the day, that's what it comes down to. >>It's interesting, the people who are gonna be involved in the scaling horizontally with automation are gonna have the keys to the kingdom. The old joke when it was, you know, they run everything. They power the business now the business is digital. You gotta be hybrid. So we see hybrids a steady state right now, hybrid cloud. When you bring the edge into the equation, how do you see that developing? Because we think it's gonna be continually be hybrid and that's gonna extend out on the edge. What is the ansible's view on how the edge evolves? What's, what's going on there? Can you share your thoughts on the expansion to the edge? >>There's a, our experience is there's a rapid modernization happening out at the edge, industrial edge, you know, oil and gas platforms, retail locations, industrial floors, all that kind of stuff. We see this convergence of OT and IT happening right now where some of the disciplines that enterprises have used in the IT area are gonna expand out into ot. But some of the requirements of ot of not having skilled IT resources, you know, in the store, in the fast food restaurant, on the oil platform, needing to have the tools to be able to automate those changes remotely. We're seeing a real acceleration of that right now. And frankly, Ansible's playing a big role in that. And it's connecting a lot of the connective tissue is around network. What is the key piece that connects all of this environment as network and those number of endpoints that need to be managed. Ansible is, you know, >>It's way use case for Ansible because Ansible built their business on configuration automation, which was don't send someone out to that branch office back in the old days. Exactly. Do it. Manual versus automation. Hey, automation every time. Yes. This is at large scale. I mean the scale magnitude, can you scope the scale of what's different? I mean go even go back 10 years, okay, where we were and how we got here, where we are today. Scope the size of the scale that's happening here. >>You know, hundreds of thousands of endpoints and things. That's not even the API points, but that's the kind of compute points, the network points, the servers it's in. It's, it's, you know what we would've never thought, you know, 10 years ago, a thousand endpoints was a lot or 10,000 endpoints was a lot of things to manage when you start talking about network devices. Yeah, yeah. Home network devices for employees that are remote employees that need to be in a secured network. Just the order of magnitude, maybe two orders of magnitude larger than it has been in the past. And so again, coming home to the automation world, >>The world's spun in your front, your front door right now. >>Yeah, yeah, yeah, >>Absolutely. Talk about, you talked about the acceleration. If we think of about the proliferation of, of devices online, especially the last two years, when, to your point, so many people shifted to remote and are still there. What are some of the, the changes in automation that we've seen as businesses have had to pivot and change so frequently and so many times to be successful? >>Yeah, so here's what we've seen, which is it's no longer acceptable for the owner of the network team or the ownership of the database or of the storage facility to, you can't wait for them to offer their service to people. Self-service is now the rule of thumb, right? So how can those infrastructure owners be able to offer their services to non IT people in a way that manages their compliance and makes them feel that they can get those resources without having to come and ask. And they do that by automating with Ansible and then offering those as package services out to their developers, to their QE teams, to their end users, to be able to consume and subscribe to that infrastructure knowing that they are the ones who are controlling how it's being provisioned, how it's being used. >>What are some of the, there were some great customers mentioned this morning in the keynote, but do you have a favorite example of a customer, regardless of industry that you think really shows the value and, and the evolution of the Ansible platform in its first 10 years and that really articulates the business value that automation delivers to a company? >>Yeah, no, it's a great question. I would think that, you know, if you wound the clock back 10 years, Ansible was all about server configuration management, right? That's what it was about was per provisioning, provisioning, you know, VMware infrastructure, vSphere, and then loading on VMs on top of that as it's expanded into network, into security and to storage and to database into cloud. It's become a much broader platform, if you will. And a good example is we have a customer, large oil and gas customer who is modernizing their oil platforms. I can imagine I not, I've not been on one, but I imagine the people that are out working on that oil platforms have greasy hands that are pushing on things. And they had this platform that the technology modernization included Azure. So connecting to data on Azure, rolling out new application updates, has to have a firewall, has to have network capabilities, has to have underlying OS to be able to do that. And Ansible was the glue that brought all that together to be able to modernize that oil platform. And so for me, that's the kind of thing where it sort of makes it real. You know, the actual businesses, >>The common set of services, this is, this is where we're seeing multi-cloud. Yeah. You start to have that conversation where, okay, I got this edge, it kind of looks the same, I gotta make it work. I'm a developer, I want some compute, I want to put this together. I have containers and orchestration behind it and kind of seeing the same kind of pattern. Yeah. Evolving at scale. So you guys have the platform, okay, I'm an open source. I love the open source. I got the platform 2.3, I see supply chain management in there. You got trusted signatures. That's a supply chain. We've been hearing a lot about security in the code. What else is in the platform that's updated? Can you share the, the, the new things that people should pay attention to in the platform? >>Yeah, we're gonna talk about a couple of things smaller around event driven Ansible, which is bringing Ansible into that really day two ops world where it's sort of hands free automation and, and, and operations where rather than someone pushing a button to trigger or initiate a piece of, of automation, an event will take place. I've detected an outta space condition, I've detected a security violation, I've detected something. Go to a rule book. That rule book will kick off in automation close that remediate that problem and close the thing without anyone ever having to do anything with that. So that's kind of one big area. And we're gonna talk tomorrow. We've got a real special announcement tomorrow with our friends from IBM research that I'm gonna, >>We'll have you on 10 30 Martha Calendars. >>But there's some really great stuff going on on the platform as we start to expand these use cases in multiple directions and how we take Ansible out to more and more people, automation out to more and more people from the inside, experts out to the consumers of automation, make it easier to create automation. >>Yeah. And one of the things I wanted to follow up on that and the skill gap, tying that together is you seeing heard in the keynote today around Stephanie was talking about enterprise architecture. It's not, I won't say corner case answer. I mean it's not one niche or narrow focus. Expanding the scope was mentioned by Katie, expand your scope grow, you got a lot of openings. People are hire now, Now Ansible is part of the enterprise architecture. It's not just one thing, it's, it's a complete, Explain what that means for the folks out there. Yeah. >>So when you start to connect what I call the technology domains, so the network team uses Ansible to automate their network infrastructure and configure all their systems. And the compute team uses it to deploy new servers on aws. And the security ops team use it to go out and gather facts when they have a threat detection happening and the storage team is using it to provision storage. When you start to then say, Okay, we have all these different domains and we want to connect those together into a set of workflows that goes across all of those domains. You have this common language and we're saying, okay, so it's not just the language, it's also the underlying platform that has to be scalable. It's gotta be secure. We talked about signing content. I mean, people don't understand the risk of an automation gone wild. You can, you can do a lot of damage to your infrastructure real fast with automation, just like you can do repair, right? So is what's running in my environment secure? Is it performant and is it scalable? I mean, those are the two, those are the three areas that we're really looking at with the platform right >>Now. Automation gone wild, it sounds like the next reality TV show. Yeah, I >>May, I may regret saying that. >>Sounds >>Like great. Especially on live tv. Great, >>Great podcast title right there. I made a mental note. Automation Gone Wild episode one. Here we are >>Talk about Ansible as is really being the, the catalyst to allow organizations to truly democratize automation. Okay. You, you talked about the different domains there and it seems to me like it's, it's positioned to really be the catalyst that's the driver of that democratization, which is where a lot of people wanna get to. >>Yeah. I mean for us, and you'll see in our sessions at Ansible Fest, we talk a lot about the culture, the culture of automation, right? And saying, okay, how do you include more and more people in your organization in this process? How can you get them to participate? So we talk about these ideas of communities of practice. So we bring the open source, the concepts of open source communities down into enterprises to build their own internal communities of practice around Ansible, where they're sharing best practices, skills, reusable content. That is one of the kind of key factors that we see as a success in inside organizations is the scales, is sort of bringing everybody into that culture of automation and not being afraid of automation saying, Look, it's not gonna take my job, it's gonna help me do my job better. >>Exactly. That automation argument always went, went to me crazy. Oh yeah, automating is gonna take my job away. You know, bank teller example, there's more bank tellers now than ever before. More atm. So the, the job shifts, I mean the value shifts. Yeah. This is kind of where the, where the automation helps. What's real quick, final minute we have left. Where does that value shift? I'm the person being automated away or job. Yeah. Where do you see the value job? Cause it's still tons of openings for people's skills, >>You know? So we see the shift from, particularly in operations from, here's my job, I look at a ticket queue, I grab a ticket, it's got a problem, I go look at a log, I look for a string and a log, I find out the air and I go, configuration change that. That's not a really, I wouldn't call that a fund existence for eight or 10 hours a day, but the idea, if I can use automation to do that for me and then focus on innovating, creating new capabilities in my environment, then you start to attract a new, you know, the next generation of operations people into a much more exciting role. >>Yeah. Architects too, they turned into architects that turned into the multiple jobs scope. It's like multi-tool player. It's like >>A, you know, Yeah, yeah. The five tool player, >>Five tool player in baseball is the best of the best. But, but kind of that's what's >>Happening. That's exactly what's happening, right? That's exactly what's happening. And it helps address that skills challenge. Yeah. And the talent challenge that organizations have as well. >>And everybody wants to be able to focus on delivering value to the organization. I have to get the end of the day. That's a human component that we all want. So it sounds like Ansible is well on its way to helping more and more organizations across industries achieve just that. Tom, it's great to have you back on the program. Sounds like you're coming back tomorrow, so we get day two of Tom. All right, excellent. Look forward to it. Congratulations on the first in-person event in three years and we look forward to talking to you >>Tomorrow. Thank you so much. >>All right, for our guests and John Furrier, I'm Lisa Martin. You're watching The Cube Live from Chicago, Day one of our coverage of Ansible Fest 2022. Stick around. John and I welcome back another Cube alumni next.

(melodic music) >> Good afternoon. Welcome back to Chicago. Lisa Martin here with John Furrier. Day one of our coverage of Ansible Fest 2022. John, it's great to be back in person. People are excited to be here. >> Yeah. We've had some great conversations with folks from Ansible and the community and the partner side. >> Yeah. One of the things I always love talking about John, is talking with organizations that have been around for a long time that maybe history, maybe around nearly a hundred years, how are they embracing technology to modernize? Yeah, we got a great segment here with the financial services leader, end user of Ansible. So it's be great segment. >> Absolutely. Please welcome Noor Shadid to the program, the senior SVP, excuse me, senior technology manager at Wells Fargo. Noor it's great to have you on theCUBE. Thank you for joining us. >> Of course. Happy to be here. >> Thanks. >> Talk a little bit about technology at Wells Fargo. I was mentioning to you I've been a longtime customer and I've seen the bank evolve incredibly so in the years I've been with it. But... >> Yeah. >> ...talk about Wells Fargo was a technology-driven company. >> Yeah. So I like to consider Wells, right? Being in a financial institution company. So I consider us a technology company that does banking as a customer, right? Like we were talking about. There's so much that we've been able to release over the couple of years, right? I mean, decades worth of automation and technology has been coming out, but lately, right? The way we provide for our customers, how fast at scale, what we're doing for our customers, it's been, it's been significant, right? And I think our goal is always how can we enhance the process for our customers and how can we provide them the next best thing? And I think technology has really allowed us to evolve with our customers. >> The customers. We are so demanding these days. Right? I think one of the things that short supplied in the last two years was patience and tolerance. >> Yes. >> People. And I don't think that's going to rubber band back? >> Yeah. No, I don't think so. >> So how, talk to us about how Wells is using automation to really drive innovation and, surprise and delight those customers on a minute by minute basis. >> Yeah. And so, you know, if you think about banking, we've been able, with automation, we've been able to bring banking into the 21st century. You do not have to go to a branch to manage your money anymore. You do not have to go, you know, go to deposit your check inside of a branch. You can do it through your mobile app, right? That's driven by automation and innovation, right? And, you know, we have all of these back ends tools working for us to help get us to this next generation of, of banking. We can instantly send money to each other. We don't have to worry about, I need to go and figure out how I'm going to get money to this person and I need to wait, you know, X amount of days. You, you have the ability and you have, you feel safe being able to manage your money at the organization. And so automation has really allowed us to get to this place where we can constantly enhance and provide features and reliability to our customers. >> It's interesting you mentioned that you guys are a technology can have it do banking reminds me of the old iPhone analogy. It's a computer that happens to make phone calls. >> Yeah. >> So like, this is the similar mindset. How do you guys keep up? >> Yeah. >> With the technology? >> So it's tough, right? Because there's so much that comes out. And I think the only thing that's constant in technology is change, right? Because it's constantly evolving. But what we do is we, integrate very well with these new tools. We do proof of concepts where we try to, you know, what's on the market, what's hot, how can we involve, like, how can we involve these new tools in our processes? How can we provide a better end result for our customers by bringing in these new tools? So we have a lot of different teams that bring, you know, their jobs are to like, do these proof of concepts and help us build and evolve our own strategies, right? So it keeps us, it keeps us on our toes and I think it keeps, you know, all these new things that are coming out in the market. We're a part of it. We want to evolve with those, what the latest and greatest is. And it's, it's been working right as customers of financial services and us managing our money through, you know, through banks. It's been great. >> So the business is the application. >> Yes. >> And how do you guys make that happen when it comes down to getting the teams aligned? What's the culture like? Explain. >> Yeah. So at Wells we have evolved so much over the, over the last few years. The culture right now is we want to make changes. You know, we are making changes. We want to drive through innovation. We want to be able to provide our, you know, it's a developer centric approach right now, right? We want to push to the next and the greatest. And so everybody is excited and everybody's adapting to all of what's happening in the environment right now. So it's been great because we are able to use all of these new features and tools and things that we were just talking about by allowing our developers to do that work and allowing people to learn these new skills and be able to apply them in their jobs, which is now creating this, you know, a better result for our customers because we're releasing at such a faster pace. And at scale. >> Talk about how, you talked about multiple groups in the organization really investing in innovative technology. How do you get buy-in? What's that sort of pyramid like up to the top level? >> Yeah. >> Because to your point, you're making changes very quickly and consumers demand it. >> Yep. >> You can do everything from home these days. >> Yep. >> You don't have to go into a branch. >> Yeah, yeah. >> Which has changed dramatically in the last it's. >> Powerful few years. Yeah. >> But how, what's that buy-in conversation like from our leadership? >> Yeah. If you don't have leadership buy-in, it's very difficult to make those changes happen. But we at Wells have such a strong support from our leadership to be a part of the change and be, you know, constantly evolve and get better. So the way we work, cause we're such a large organization, you know, we bring in our business, you know, our business teams and we talk to them about what is it that's best going to better our customers. How do we also not just support external but internal, right? How do we provide these automated tools or processes for people to want to do this next work and, and do these, you know, these new releases for our customers. And so we bring in our business partners and, and we bring in our leadership and, our stakeholders and we kind of present to them, you know, this is what we're trying to do. This is the return that you'll get. This is what our customers will also receive. And this is, you know, this is how we keep evolving with that. >> How has the automation culture changed? Because big discussion here is reuse, teamwork, I call it multiplayer kind of organizations where people are working together. 'Cause that's a big theme of automation. >> Yeah. >> Reuse, leverage. >> Yep. >> Can you explain how you guys look at that? >> Yeah. It's changed the way that we do banking because we're eliminating a lot of the repetitive tasks in the toil because we have partners that are developing these, you know, services. So specifically with Ansible, we have these playbooks, rather than having every customer write the same playbook but with their own little, you know, flavor to it, we're able to create these generic patterns that customers can just consume simply by just going into a tool, filling out you know, filling out that playbook template, credentials, or whatever it is that they need and executing it. They don't have to worry about developing something from scratch. And it also allows our customers to feel safe because they don't have to have those skills out the box to be able to use these automation tools, right? They can use what's already been written and executed. >> So that make things go faster with the benefits or what? Speed? >> Faster stability, right? We're now speed, stability, scalability, because we're now able to use this at scale. It's not just individual teams trying to do this within small spaces. We're able to reliable, right? Automation allows us to be reliable internally and for our customers. Because you're not asking, there's no human intervention when you're automating, right? You have these opportunities now for people to just, it's one click, you know, one click solution or you're, you're end to end. You got self-healing involved. It's really driving the way that we do our work today. >> So automation sounds like it's really fueling the internal employee experience at Wells... >> Yes. >> ...as well as the customer experience. And those two things are like this to me. They're inextricably linked. >> A hundred percent because if you need it, they need to be together, right? You want your internal to also be happy because they want to be able to develop these solutions and provide these automation opportunities for our teams, right? And so with the customers, they're constantly seeing these great features come out, right? We can, you know, with AIML today, we're now able to detect fraud significantly. What we would've, what we could've done a couple years ago. And, and developers are excited to be able to do that, right? To be able to learn all these new tools and new technologies. >> What's interesting Wells is you guys are like an edge application. Obviously everyone's got banking in their hand. FinTech obviously money's involved. So there's people interested in getting that money. >> Yeah. >> Security hackers or whatnot. So when you got speed and you got the consistency, I get that. As you look at securing the app, that becomes a big part of what, what's the conversations like there? >> Yeah. >> 'Cause that's the number one concern. And it's an Edge app. I got my mobile, I got my desktop. >> Yeah. >> Everything's in the cloud on premise. >> Yeah. And, and I think for us, security is number one. You know, we want to make sure that we are providing the best for our customers and that they feel safe. Banking, whatever financial service you're working with, you want to feel like you can trust that your money with those services. Right? So what we do is we make sure that our security partners are with us from day one. They're a part of the process. They're automating their pieces as well. We don't want to rely on humans to do a lot of the manual work and do the checking and the logging. You want it to be through automation and new tools, right? You want it to be done through trusted services. You don't, you know, security is right there with us. They're part of our technology organization. They are in the technology org. So they're the ones that are helping us get to that next generation to provide, you know, more secure processes and services for customers. >> And that's key for trust. >> Yes. >> And trust is critical to reduce churn and to, you know, increase the customer lifetime value. But, but people, I mean, especially with the amount of generations that are alive today in banking, you need to be able to deliver that trust intrinsically to any customer. >> Yes, a hundred percent. And you want to be able to not only trust the service but yourself that you can do it. You know, when you go into your app and you make a payment, or when you go in and you want to send, you know, you want to send money to a different, you know, a different bank account, you want to be able to know that what you just did is secure and is where you plan to send it. And so being able to create that environment and provide those services is, is everything right for our customers. >> What are some of the state-of-the-art kind of techniques or trade craft around building apps? 'Cause I mean, basically you're digitally transformed. I mean, you guys are technology first. >> Yeah. >> The app is the company. >> Yeah. >> That's, that's the bank. How do you stay current? What's some of the state of the art things that you guys do that wasn't around just a few years ago? >> Yeah, I mean, right now just using, we're using tools like Terraform and Ansible. We're making sure that those two are hand in hand working well together. So when we work on provisioning, when we, during provisioning where it's all, you know, it's automated, fully end to end, you know, AI ops, right? Being able to detect reoccurring issues that are happening. So if you have a incident we want to learn from that incident and we want to be able to create, you know, incident tickets without having to rely on a human to find that, you know, that problem that was occurring and self-healing, right? All of this is starting to evolve and bringing in the, the proper alerting tools, bringing in the pro, you know, the right automation tools to allow that self-healing to work. That's, you know, these are things that we didn't have, you know, year, decade ago. This is all coming out now as we're starting to progress and, and really take innovation and, you know, automation itself.... >> What's the North star internally when you guys say, hey, you know, down five years down the road, bridge to the future, we're transforming, we've continued to innovate. Scale is a big deal. Data, data sovereignty, all these things are coming up. And what's the internal conversation like when you talk about a future state? >> Yeah, I think right now we're on our cloud transformation journey, right? We're moving right now. We have workloads into our two CSPs or public cloud. Also providing a better service for infrastructure and being able to provide services internally at a faster space, right? So moving into the public cloud, making sure everything's virtualized, moving away from hard, you know, physical hardware or physical servers. That's kind of the journey that we're on right now. Right? Also, machine learning. We want to be able to rely on these, you know, bots. We want to be able to rely on, on things learning from what we're doing so that we don't make the same mistakes again. >> Where would you say the most value or the highest ROI that you've gotten from automation today? Where is that in the organization? >> There's so much, but what I mean because of all of the work that we're doing, there's a lot that I could list, but what I will say is that the ability to allow self-healing in our environments without causing issues is a very big return. Automating failovers, right? I think a lot of our financial institutions have made that a priority where they want to make sure that their applications are active, active and also that when things do go wrong, there is something in place to make sure that that incident actually doesn't, you know, take down any problems. I think it's just also investing in people. Right now, the market is hot and we want to make sure that people feel like they're being able to contribute, they're using the latest and greatest tools. They're able to upskill within our own environments at the firm. And I think our organization does an amazing job of prioritizing people. And so we see the return because we're prioritizing people. And I think, you know, a lot of institutions are trying, you know, people first, people first. But I can say that at Wells, because we are actually driving this, we're allowing, you know, we're enforcing that. We want our engineers to get the certifications. We're providing, you know, vouchers so that people can get those clouds certifications. It's when you do that and you put people first, everything kind of comes together. And I think, you know, a lot of what we see in our industry, it's not really the technology that's the problem, it's process because you're so, you know, we're working at large scales. Our environments are massive. So, you know, my three years at Wells have seen a significant amount of change that has really driven us to be.... >> On that point better. How about changing of the roles? IT, I mean, back in the day, IT serves the business, you know, IT is the business now, right? As, as you've been pointing out. What does the roles change of as automation scales in, is it the operator? I mean, we know what's going on with dev's devs are doing more IT in the CICD pipe lining. >> Yep. >> So we see that velocity check, good cloud native development. What's the op scene look like? It seems to be a multi-tool role. >> Yeah. >> Where the versatility of the skill set... >> Yep. >> ...is the quick learner. >> Yep, able to adapt. >> And yeah, what's your view on this new persona that's emerging from this new opportunity? >> Yeah, and I think it's a great question because if you think about where we're going, and even the term DevOps, right? It means so many things to different people. But literally when you think about what DevOps is allowing our developers and our operations to work together on one team, it's allowing, you know, our operation engineers aren't, you know, years ago, ops engineers were not doing the development work. They were relying on somebody to do the development work and they were just supporting making sure our systems were always available, right? Our engineers are ops are now doing the development work. They're able to contribute and to get, they're writing their own playbooks. They're able to take them into production and ensure that they're, being used correctly. We are change driven execution organization. Everything is driven through change and allowing our ops engineers or production score engineers to write their own playbooks, right? And they know what's happening in the environment. It's powerful. >> Yeah. You're seeing DevOps become a job title. >> Yeah (laughs). >> Used to be like a function of philosophy... >> Yeah, yeah. >> ... and then SRE's... >> SRE's. >> SRE are like how many servers do you have? I don't know, a cloud, what's next? (all laugh) >> What's next? Yeah, I think with SREs it's, you know, it's important that if you have site reliability engineers, you're working towards, you know, those non-functional requirements... >> Yeah. >> ...making sure that you're handling those key components that are required to ensure that our systems, our applications and our integrations, you know, are up there and they're meeting the standards that we set for those other faults. >> And, and I think Red Hat Ansible nailed it here because infrastructure is code. We get that infrastructure has configuration as code, but OPS says code really is that SRE outcome. SRE also came from the Google background, but that means infrastructure's just doing, it's thing. >> Yes. >> The ops is automated. >> Yes. >> That's an interesting concept. >> Yeah, because it's not, you know, it's still new, right? A lot of organizations used to see, and they probably still see operations as being the, you know, their role is just to make sure that the lights are on and they have specific access so they, you know, they're not touching code, but the people that are doing the work and know the environment should really be the ones under creating the content for it. So yeah, I mean it's crazy what's happening now. >> So I got an analogy that's going to be banking analogy, but for tech, you know, back in the automation, Oh, going to put my job out of business, ATMs are going to put the teller out of business as more tellers now than there are before the ATMs. So that metaphor applies into tech where people are like, "What am I auto? What's automating away? Is it my job?" And so actually people know it's not. >> Yeah. >> But what does that free up? So if you assume, if you believe that's good, you say, okay, all the grunt work and the low level on differentiated heavy lifting gets automated away. >> Yeah. >> Great. What does that free up the talent to do? >> Yeah, so when you, and that's great that you bring it up because I think people fear, you know, of automation, especially people that weren't doing automation in the past and now their roles are now they're able to automate those roles out. They're fearful that they don't have a space, a role anymore. But that's not the case at all. What we prioritize is now that those new engineers have this new skill set, apply them. Start using it to be a part of this transformation, right? We're moving from, we went from physical to virtual to now, you know, we're moving into the public, moving into the cloud, right? And that, that transformation, you need people who are ramping up their skill sets, you know, being a part of one of the tools that I own is terraform at Wells that, you know, right now our priority is we're trying to ramp up the organization to learn terraform, right? We want people to learn, you know, this new syntax, this new, you know, HCL and it's, you know, people have been automating some of the stuff that they're doing in their day to day and now trying to learn something new so that they can contribute to this new transformation. >> So new functionality, higher value services? >> Yes, yeah. >> It brings tremendous opportunity for those folks involved in automation. >> Yes. >> or on so many levels. >> Yep. >> Last question, Noor for you is what, you know, as we are rounding out calendar year 2022, entering into 2023, that patience is, that we talked about is still not coming back. What's next for Wells as a technology company that does banking? >> I mean, you name it, we're working on it, because we want to be able to deliver the best for our customers. And I think right now, you know, our digital transformation strategy and, and moving into the public cloud and getting our applications re-architected so that we are moving into microservice driven apps, right? We're moving these workloads into the public cloud in a seamless way. We're not lifting and shifting so that we're not causing more problems into the environment. Right. And I think our, our, our goal is right, Like I was saying earlier, people and evolving with the technology that's coming out. We're not, you know, we are a part of the change and we are happy to be a part of that change and making those changes happen. >> People first. >> Awesome, awesome stuff. >> Automation first sounds outstanding and I will never look at Wells Fargo as a bank again. >> Yeah. (laughter) >> Perfect. Perfect. >> Yeah, that's awesome. >> It's been such a pleasure having you on the program, talking about how transformative Wells has been and continues to be. >> Yeah. >> We appreciate your insights and your time. >> Thank you. >> Thank you so much. It was lovely being her. Pleasure here. Thank you guys. >> For our guest and John Furrier, I'm Lisa Martin. You've been watching theCUBE all day, I'm sure, live from Chicago at Ansible Fest 2022. We hope you have a wonderful rest of your day and John and I will see you tomorrow morning.

>>Hello from Chicago, Lisa Martin, back with you and John Furrier. This is day one of the Cube's coverage of Ansible Fest 2022. John, we've been having great conversations all morning about automation and how it's really pivotal and central. One of the things that we want to talk about next is automation as a strategy. Yeah. You know, some of the barriers to customer adoption, one of them is, well, can we, can we really understand where the most ROI is gonna be? But another one is automation happening kind of in pockets and silos. And we're gonna be talking next with one of our alumni about breaking those down. >>This is gonna be a great segment from the customer perspective, the conversations they're having problems trying to solve, and really got a great cube alumni back to share. And we're excited. It's be a good segment. >>We do have a great alumni, Walter Bentley, Fresh from the keynote stages back with us, the senior manager of the automation practice at Red Hat. Walter, it's great to have you back on the program. >>Thank you. Thank you for having me back. I really look forward to doing this every year and you know, it's, it's >>Exciting. So we had your great energetic keynote this morning and you were really talking about organizations need to think about automation from a strategic lens perspective, a really a true long term investment. Where are most organizations today and how are you gonna help them get there? >>Right. So most organizations today are kind of in that sweet spot where they've discovered that they can do the tactical automation and they can deal with those small day-to-day things. And now they wanna move into the space where they're really able to plug automation into their current workflows and try to optimize it. And, and that's the perfect direction to be heading. And, and what I always encourage our customers is that once you get to that point, don't stop. You gotta keep going because the next phase is, is when you begin to innovate with automation. And when automation is at first is, is at the beginning of the, of everything you're creating. And at that point, that's when you're really gonna see the great benefits from it. >>How have your customer conversations evolved over the last couple of years, particularly as the world has changed, but we've also seen the acceleration of automation and so much, so much advancement in the technology. >>Right. You know, you'll be shocked that our customers wanted us to speak to them in more of an enterprise architecture level. They wanted us to really be able to come in and help them design how they're going to lay out their automation vision. And that surprised me at first. My background being in architecture for many years, I didn't know that, you know, automation had evolved to that level. And, and that was one of the things that we, we tried to do our best to rise to the occasion and be able to answer that call. >>You know, Walter, one of the things when we were in person last in 2019, you were on the cube and then we did the remote. We were kind of right. You got it right. When we were, we were talking about this, Hey, if this goes the way we think it's gonna go, the automation layer is gonna be horizontally scaled with the cloud. So income, cloud, growth, lift and shift. Now I got some refactored applications in the cloud and I got on premises edge coming hybrid steady state. What does automation look like? You had said it's gonna scale. Yep. And so as clients realize, well this is was the kind of a group within the group doing some automation stuff with Ansible, all great stuff, Product leadership, great community check, check, check. Now, how do you make that a global architecture for a company? What, what's it take to make that an enterprise scale architecture? What's the next step for the, for the journey and, and for the community and the customers? >>So one of the major announcements today is actually one of the right steps in the right direction, which is now that you can deploy a on all of your hyperscalers, right? So you have it local, you're covering your private cloud area, now you're able to cover your hyperscalers. Now it's time to unite them together so that they can all kind of work as one function. And to me, that is the enterprise approach that that to aap. And I'm just so excited that we finally have rolled it out for aws. We have it for Azure, of course we have it inside. And we're also working on things like you said, like the edge, but also things like making sure we're covering customers that are air gaped customers that do not have the capability of the ingress in, in, in, in being, of being able to go in and out of that environment and that network. Right. We're working on strategic, strategic solutions to be able to do that better >>For what's interesting, we've been talking about super cloud on the cube. I, we coined that term at reinvent about people using cloud in a different way to kind of do things and it's become kind of also a, a term for multi-cloud. Yes. So if you think about what you just said, it's interesting, this cloud services that could, they all have stores, they have compute, There might be a day where they're all kind of invisible. Yes. And you can have spanning services across the cloud, but yet they can still differentiate on their own. So it's not so much about sneakers, it's more about that interoperability. How do you see that? What's your reaction to that? Right. >>Well, that's one of the core reasons why we move to the name of the answ automation platform. Platform being the key right? Is, is the platform is supposed to be able to span into different environments and really kind of unite them together. And that was one of the the things that I really liked about when we went to that late last year. Yeah. Late last year. And, and we've been working with our customers and make sure that we make that front and center, that they move towards that environment so that they can begin to do better scale and really operate at that, at that executive level. >>What's your favorite customer story that you think really articulates the value of what you just said? >>Right. So the one, so I'll give you a different one from the one that I, that I talked about on stage. And, and again, it it, when we went in from a services engagement, we did not expect the outcome of the fact that they would access this particular customer. We went in something very tactical, just laying down the platform for them. And, and the expectation was we would lay it down and walk away and then hopefully they would pick it up and kind of run with it. What we came to realize is that they liked the oversight and they liked the way that we were working with them. And they wanted to take those preferred approaches and really embed them Right. And their organization. And so they invited us back actually for two or three different consulting engagements to come back and just help them drive that adoption. And this is at the, they're at the very beginning, right? So they're doing it a little bit different in a lot of other organizations. The other organizations would lay down the platform, do some things, and then call us back to help them them with adoption, Right. >>Is the report card out? Yeah, >>Absolutely. They did it differently. And, and that to me stood out as the level of maturity their IT organization is. >>It sounds like they went from tactical to strategic Yes. Pretty quickly. Which is not normally the >>Case. No, no, not at all. Not normally the case. But as you can clearly see that, we're starting to see that more and more with our customers. They're upleveling, I hate for the theme, but they're upleveling. Right. And, and, and that's what I meant by my organization, my team that I, that I run, we have to do more with our customers because they're expecting more >>For them to level up. And I loved how that was used this morning. I'm like, Yeah, that's a cool term. Level up. We all gotta level up to some degree. How are you helping organizations do that from a cultural shift perspective? Because of course the people are so integral to this being successful. Can't forget >>That. Absolutely. So, you know, you know, remember the days of when you would have the DevOps team and that was like the thing, like you have to form your DevOps team and once you got that, you're good to go. And, and I always tell our customers that's a good start, but that's definitely not where you want to end. And you have to get to the point where you have all parts of your organization writing automation content, feeling comfortable, being able to kind of control their day to day. And so that's where you have to break down those silos. You have to really have those, you know, your operators and your developers and, and your DBAs and your networking folks really communicating. And, and if everyone kind of takes care of their own world and write content to control what they do on a day to day, they can bring those together. >>Walter, on buzzword it's been kicking around Silicon Valley in the tech industry re recently is multiplayer versus single player software. Yes. And I I heard that must be from gamers obviously. Yes. Discourse pop. I heard that on, stayed here in the matrix announcement earlier. You know, when you talk about teamwork ops devs while working together, clearly the operator role is changing. What that means is changing devs are getting stronger and more open source, they're shifting left and all that good stuff in the, in the CID pipeline as the teams work together, multiplayer in an organization. What's the success form of that you see emerging for how to organize, how to motivate, how to get people kind of in a good, you know, teamwork pass score kind of team oriented approach? >>Well, I'm really proud to talk about is how AAP has really enabled that and, and kind of fast tracks that ability for everyone to work together within a, the all the functionality that's now built into it. There's pieces of it that are focused on different operators or different parts of the IT organization, right. And, and, and we're made to be able to help to bring them all together. You know, I love the components such as the service catalog. You know, imagine being able to have a place where you can publish all of your, your content for other people to consume. You know, back in the day everything was stored in, in a repository, right? And you had to know what you were looking for. And so just small changes like that, having the, the, the Ansible toy, right? So you're having tools that are actually built in for those who are writing the content to be able to have at their fingertips the ability to test their content right from inside of the, the, the toy, right? So the terminal interface, just those small little nuances to me is what helps to bring it all together and kind of create that >>Great leverage glue. Yes. Not a lot of busy work and you know, absolutely. Hunting and packing for stuff like configuring manually. >>Absolutely. >>Awesome. What's next for you guys? >>Well, you know, we have some big announcements coming up tomorrow. I won't, I won't get into as much as I want to talk about >>It. Events. Yeah, >>Yeah, yeah. Something starts with the e but also some really fantastic technology. We're, what we're doing is, is we're really taking the idea of automation and really feeding into it in a sense that we're building into some mar some, some really smart technology into aap. And I'm, I'm, I'm excited, I'm excited for direction it's going and I know everyone tomorrow are gonna really, really hear some great >>Things. We heard upleveling, we heard upleveling culture shift. If I asked you what does culture shift mean, how would you answer that? >>I would answer that in a sense that it, it, the culture shift is, is shifting from the place where you feel that you're on an island and you have to solve for it alone as well as feeling that you have to solve for the whole ribbon of whatever you're working on. And that culture shift is moving from that mentality to the fact that you have a whole team of folks who may know how to solve for that already. And you feel comfortable being able to reach out to them and work with them to be able to build that. And that's, that to me is the change. You know, I'm, I'm a old school infrastructure dude, you know, I was the one who would, who would wake up two o'clock in the morning to fix a problem, right? I thought it was on me, but now the culture shift is now it's, we are a team and we're gonna work together to solve it. So that's, that's kind of my view on >>It. And the appetite in organizations is there, cuz oftentimes in the, in the siloed world, it's, I own this, this is my baby. Right? Right. How do you help them as a, as a trusted advisor to really open up the kimono and embrace that collaboration? Because ultimately that's the right strategic direction for the business, >>Right? The first step in that is making sure that everyone is kind of operating from the same book, right. Or the same plan. And, and until you actually write that plan down and publish it in a place for other people to consume it, it creates a little bit of a barrier, right? So that's the first thing we do is write down that plan, make it available for all the consume. And at the beginning, you know, not everyone runs to it, but over time if their curiosity begins to peak and then over time they begin to consume it and possibly contribute to it themselves over time, that's, that's how we kind of conquer that. And so far we've seen some good success. >>What would you say if someone said, you know, I want some proof, proof in the pudding proven methods to help accelerate the time to value with automation and help organizations to really understand and quantify the ROI for doing so. >>Right. And, and to me that's, this is the conversation I love having because we've, we've come out with something that we call success metrics and, and yes, they are exactly what they sound like, right? There are some metrics that you can use to measure in your organization to kind of determine your maturity around automation. The two key things that I would love to share about that is that when we think of metrics, right? We think of performance, we think of, you know, how well something is running, how long it's been running. Those are all great, but the two additional success metrics that we include in there are around more of the cultural field. The perception, right? The perception as well as how comfortable your employees feel using that product. And that's where that, that the shift of looking at the cultural, not just the technical side, but the cultural side of things has made a big difference. So I love sharing those metrics with our customers. It usually resonates and then we help them dig in on, to see how they, how they fit, and also give them some ideas as to how they can improve going forward. >>I'm sure they appreciate that knowing where that, where we are now, how do we get to the end, not the end state. Obviously it's a journey, but how do we get farther along in this from a unified front approach rather than absolutely operating in these silos, which is not gonna get us to the, the the on the journey that we should be on. Correct. Yeah. Yep. So some good stuff coming out tomorrow. Not gonna give us any nuggets, which totally understands. Nope. >>No, but it's, you're gonna be very excited. Yes. It's good stuff. >>Awesome. I gotta ask you one quick question before we wrap up. You mentioned multi-cloud earlier. This is a big conversation in the industry. A lot of people are debating what that is. It sounds good on paper. Where is the customer's view as they look at this journey? Because we, we see a future where there'll be services that won't be common across clouds. There's a differentiation and some that will be, and that, that just be shared like compute for instance. And let, let us be there where you can call in to the multi-cloud. What's, how do you, how do your customers think about multi-cloud? Are they having that conversation more they go, Is that more of a destination of the future? In their mind >>It feels more like a destination of the future. Right now, a lot of organizations have kind of solidified on one cloud per se that they want to be able to roll out as far as being able to scale up and down their resources. But the idea is, is eventually, you know, you, you're gonna go with whatever works best for that product or whatever works best for that, that business case that you're trying to solve for. And, and that's why I love the fact that AEP is kind of generically being able to be applied across all of them. So that, that is, that is gonna be your unifier, right? That's gonna be the layer that will stay the same no matter where you go. And that's one of the things that I love about our product around that is that, that we are meant to be the unifier and we're >>Bless the whole today. It's a great opportunity for Ansible that's there. All >>Right. To be the unifier. Last question for you before we wrap. What was some of the feedback about, from your session this morning on Ansible really being that unifier? Any, any folks come up to you and say anything that was particularly insightful? >>Well, you know what, it it, what was kind of alluded to or shared with me directly was the fact that, you know, thinking about automation as you would traditional platforms, right? And, and building a strategy and, and the idea that you need to write that down and actually make some decisions around that. And, and it wasn't that it wasn't thought about it, it was just, it just never came front to mind. And, and so I'm happy that I was able to plant that seed because that, that's what we're seeing that makes the difference between those who are very successful with automation and those, those who may >>Not be writing it down. Sometimes it's fact to basics that back to basics really help absolutely fuel the growth of organizations. Walter, thank you. Thanks for joining John and me on the queue today talking about what's going on, automation as a strategy, the vision and how Ansible is really on its way to becoming that unifier. We appreciate your insights. Cool. >>No, it's my pleasure. And thank you for having me again. All >>Right, cool. Our pleasure for Walter Bentley and John Furrier. I'm Lisa Martin. You're watching The Cube Live from Chicago. Day one of our coverage of Ansible Fest 2022 continues next.

(upbeat music) >> Hey everyone, welcome back to Chicago theCUBE is live on the floor at AnsibleFest 2022, the first in-person Ansible event that we've covered since 2019. Lisa Martin here with John Furrier. John, great to be here. There's about 1400 to 1500 people here in person, the partner ecosystem is growing and evolving, and that's going to be one of the themes of our next conversation. >> CloudScale is continuing to change the ecosystem, and this segment with AWS is going to be awesome. >> Exactly, we've got one of our alumni back with us, Stefanie Chiras joins us again, senior vice president, partner ecosystem success at Red Hat. and Manasi Jagannatha is also here Global Alliance Manager at AWS. Ladies, welcome to the program. >> Both: Thank you. >> Manasi: Nice to be here. >> Stefanie: Yeah. >> So some exciting news that came out. First of all was great to see you on stage. >> Thank you. >> In front of a live audience. The community is, you talked about this before we went live. The Ansible is nothing, if not the community. So I can only imagine how great that felt to be on stage in front of live bodies announcing the next step with Ansible and AWS. Tell us about that. >> I mean, you can't compete with the energy that comes from a live event. And I remember the first AnsibleFest I came to, it's just this electric feeling born out of the community, born out of collaboration and getting together feeds that collaboration in a way that like nothing else. >> Lisa: Can't do it by video alone. >> You cannot. And so it was so fun cuz today was big news. We announced that Ansible will be available through the AWS marketplace, the next step in our partnership journey. And we've been hearing like most of our announcements, we do these because customers ask for them. And that's really what is key. And the combination of what Red Hat brings to the table and what AWS brings to the table. That's what underpins this announcement this morning. >> Talk about it from a customer demand perspective and how you are not only meeting customers where they are, but you're speaking their language. >> Manasi: Yeah. >> Yeah, there's a couple of aspects and then I want to pass it to Manasi because nothing speaks better than a customer experience. But the specifics I think of what come together is this is where technology, procurement, experience, accessibility all come together. And it took both of us in order to do that. But we actually talked about a great example today, the TransUnion. >> So we have TransUnion, they are a credit reporting company and they're a giant customer. They use RHEL, they use AWS services. So while they were transitioning to the cloud, the first thing they wanted to know was compliance, right? Like, how do we have guardrails around compliance? That was a key feature for them. And then the other piece was how do we scale without increasing the complexity? And then the critical piece was being able to integrate with the depth of AWS services without having to do it over and over again. So what TransUnion did was they basically integrated Ansible automation platform with the AWS Cloud Control API that gave them the flexibility To basically integrate with what, 200 plus services? And it's amazing to see them grow over time. >> What's interesting is that Amazon, obviously cloud has been awesome. We've been covering it since the beginning. DevOps infrastructures code was the dream. Now it's app says code, you have configuration code before that. As cloud goes next level here, we're starting to see a lot more higher level services on AWS being adopted by customers. And so I want to get into how the marketplace deal works. So what's in it for the customer? Because as they bring Ansible across the enterprise and edge, now we're seeing that develop. If I'm the customer, am I buying it through the marketplace? What's the mechanics of the deal? Can I just tap into the bill, explain the marketplace workflow or how it works? >> Yeah, I'd love to do that. So customers come to the marketplace for three key benefits, right? Like one is the consumption based model, pay as you go, you can get hourly, annual, and spot instances. For some services you even get per second billing, right? Like, that's amazing, that's one. And then the other piece is John and Stefanie, as you know, customers would love to draw down on their EDPs, right? Like they want a single- >> EDPs, explain that with acronym. >> It's enterprise discount program. So they want a single bill where they can use third party services and AWS services and they don't have to go through the hustle of saying, "Hey, let me combine all these different pieces." So combining that, and of course the power of Ansible, right? Like customers love Ansible, they've built playbooks. The beauty of it is whatever you want to build on AWS, there is most likely a playbook or a module that already exists. So they can just tap into that and build into- >> Operationally it's a purchasing through marketplace. >> And you know, I mean, being an engineer myself, we always often get caught up in the technology aspect. Like what's the greatest technology? And everyone, as Manasi said, everyone loves the technology of Ansible, but the procurement aspect is also so important. And this is where I think this partnership really comes together. It is natively, Ansible is now, natively integrated into AWS billing. So one bill, you go and you log in. Now you have a Red Hat subscription, you get all the benefits from Red Hat that comes along with that subscription. But the like Ansible is all about simplicity. This brings simplicity to that procurement model and it allows you to scale within your AWS cloud environment that you have set up. And as Manasi mentioned, pull in those other native services from AWS. It's Great. >> It's interesting one of the things that buzzword Lisa and I were just talking as in the industry is the word multiplayer. I've heard people say that's multiplayer software, kind of a gaming analogy. But what you guys are doing is setting up, once they go with Ansible in the marketplace, they're just buying as things get more collaborative off the marketplace. So it kind of streamlines, if I get this right. >> Stefanie: Yep. >> The purchasing process. So they're already in, they just use it's on the bill. Is that kind of how it works? >> Yep. >> Absolutely done, yeah. >> So it the customer has a partnership with us more on the technology side and this particular case and with AWS and the procurement side, it brings that together. >> So multiplayer software, is it multiplayer software? >> We like to talk about multi-partner solutions and I think this provides a new grounding for other partners to come in and build upon that with their services capabilities, with their other technology capabilities. So well clearly in my world, we talk about multi-partner. (both laughs) >> Well, what you're doing is empowering the developers. I know that Red Hat is one of its goals is let's make things much more seamless, much smoother for the developers as the buyer's journey has changed. And John, you've talked about that quite a bit. You're empowering those buyers to actually have a much simpler, streamlined process and to be able to start seeing automation become democratized across organizations. >> Yeah, and one of the things I love about the announcement as well is it pulls in the other values of Ansible automation platform in that simplicity model that you mentioned with like things like certified collections, certified collections that have been built by partners. We have built certified collections, to go along with this offering as well as part of the AWS offering that pulls in these other partner engagements together. And as you said, democratizes not only what we've done together, but what we've done with other partners together. >> Lisa: Right. >> Yeah. >> Can you kind of talk kind of about the depths of the partnership, the co-engineering, and sort of the evolution and the customer involvement in the expansion of the partnership? >> Yeah, I'd love to walk you through that. So we've had a longstanding partnership coming up on 15 years now Stefanie, can you believe it? >> Stefanie: Yeah. (laughs) >> 15 years we've been building, to give you some historical context, right? In back in 2008 we launched RHEL and in 2015 we supported SAP workloads on RHEL. And then the list goes on, right? Like we've been launching Graviton instances, Arm instances, Nitro. The key to be noted here is that every new instance Launch, RHEL has always been supported on day one, right? Like that's been our motto. So that's one. And then in 2021, as you know, we launched Rosa Red Hat OpenShift service on AWS. And that's helped customers with their modernization journey to AWS. So that's been context historically around where we were and where we are today. And now with Ansible, it just gives customer another tool in their arsenal, right? And then the goal is to make sure we meet customers where they are, give them all the Red Hat products that they love using on their hybrid workloads. >> Sounds like a lot is coming maybe at re:Invent too, coming up. >> Yeah. >> What's next? >> This is the beginning, right? We'll continue to grow and based upon not only laying the building blocks for what customers can build with, and you mentioned Lisa, right? We follow this journey that Manasi talked about because of what customers ask for. So it's always a new adventure to determine what'll come next based upon what we hear from our joint customers. >> On that front though, Stefanie, talk about the impact of the broader ecosystem that this is just scratching the surface. >> One of the things, and we've been going through a whole transformation at Red Hat about how we engage with the ecosystem. We've done organizational shifts, we've done a complete revamp of how we engage with the ecosystem. One of our biggest focus is to make sure that the partnerships that we have with one partner bring value to the rest of our partners. No better example than something like this when we work with AWS to create accessibility and capability through a procurement model that we know is important to customers. But that then serves as a launch point for other partners to build certified collections around or now around validated content, which we talked about today at AnsibleFest, that allows other partners to engage. And we're seeing a huge amount in services partners, right? Automation is so pervasive now as customers want to go out and scale. We're seeing services partners really come in and help customers go from, it's always challenging when you have a broad set of IT. You have cloud native over here, you have bare metal over here, you have virtual, it's complex. >> John: Yeah. >> There's sometimes an energy activation barrier to get over that initial automation. We're seeing partners come in with really skilled services capabilities to help customers get over that hump to consolidate with an automation plan. It gets them better equipped to do day one automation and day two automation. And that's where Ansible automation platform is going. It's not just about configuration management, it's about day two management as well. >> Talk about those barriers a little bit more and how Ansible and AWS together are helping customers really knock those out of the park. Another baseball reference for you. We see that a lot of organizations, the skills gap, which we've talked about already on the conversation today, but Ansible as being a facilitator of helping organizations to attract talent, to retain talent, but also customers that maybe don't know where to start or don't know how to determine the ROI that automating processes will bring. How can this partnership help customers nock those out of the park? >> So I'll start and then I'll pass it to Manasi here. But I think one of the key things in this particular partnership is just plain old accessibility. Accessibility, which public cloud has taught the world a new way to get fast access that consumption based pricing. Right you can get your hands on it, you can test it out, you can have a team go in and test it out, and then you can see it's built for scale. So then you can scale it as far as you want to go forward. We clearly have an ecosystem of services partners, so does AWS to help people then sort of take it to the next level as they want to build upon it. But to me the first step is about accessibility, getting your hands dirty. You can build it into those committed spend programs that you may have with AWS as well to try new things. But it's a great test bed. >> Absolutely. And then to add to what Stefanie said, together Red Hat and AWS, we have about a hundred thousand partners combined, right? Like resellers, sis, GSI, distributors. So the reach the combined partnership has just amplifies. >> Yeah, it's huge news. I think it's a big deal because you operationalize the heavy lifting of procurement for all your joint customers and the scale piece is huge. So congratulations. I think it's going to make a lot of money for Ansible. So good call there. My question is, as we hear here, the next level's edge. So AWS has been doing a ton of hybrids since outpost announcement years ago. Now you got all kinds of regional expansions, you've got local zones, you've got all kinds of new edge activity. So are there dots connecting here with the edge with Red Hat Ansible? >> Do you want- >> Yeah, so I think we see two trends with our customers, right? Like mainly I'm specifically talking about our RHEL customer base on AWS. We have almost hundreds to thousands of customers using RHEL on AWS. These are 90% of fortune 500 companies use RHEL, right? So with that customer base, they are looking to expand your point into the edge. There's outposts, there are so many hybrid environments that they're trying to expand in. So just adding Ansible, RHEL, Rosa, OpenShift, that entire makes, just gives customers that the plethora of products they need to run their workloads everywhere, right? Like we have certifications outpost, we have certifications with OpenShift, right? So it just completes the puzzle, if you- >> So it's a nice fit. >> Yeah. >> It is a really nice fit. And I love Edge and Edge once you start going distributed, this automation aspect is key for all the reasons, for security reasons to make sure you do it the same way every single time. It's just pervasive in it. But things like the Cloud Control API allow it to bridge into things like Outpost. It allows a simple way, one clean way to do API and then you can expand it out and get the value. >> So this is why you are on stage and you said that Ansible's going to expand the scope to be more enterprise architecture. >> Stefanie: That's right. >> That's essentially what you're getting at. This is now a distributed computing fabric at cloud scale on AWS. >> Stefanie: That's right. >> Did I get that right? >> Yep, and it touches all the different deployments you may have, on-prem, virtual, cloud native, you name it. >> So how do the people turn into architects? Cuz this is, again, we had this earlier conversation with Tom, multi-tool players, a baseball analogy I used. It's like signifies the best player, your customers are becoming multiple tool players or operators. The new operator is now the top talent. They got to run Ansible, they got to automate, they got to provide services to the cloud native developers. So this new role is emerging, it's not a cloud architect but it's, if it's going to be system architecture wide, what's this new person look like that's going to run all this? >> I think it's an interesting question. We were talking yesterday, actually, Tom and I were talking with the partners. We had Partner Day, the first ever at AnsibleFest yesterday, which was great. We got a lot of insight. They talked a lot about this platform focus, right? Customers are looking to create that platform so that the developers can come in and build upon it without compromising what they want to do. So I do think there's a move in that direction to say how do you create these platforms at a company that no compromises, but it provides that consistency. I would say one thing in partnerships like this, I think customer expectations on the partner ecosystem to have it be trusted is increasing. They expect us as we've done to have our engineers roll up their sleeves together to come to the table together. That's going to show up in our curated content. It's going to show up in our validated content. Those are the places I think where we come up from the bottom through our partnership and we help bridge that gap. >> John: Awesome. >> And trust was brought up a number of times this morning during the keynote. We're almost out of time here, but I think it's one of those words that a lot of companies use. But I think what you're showing is really the value in it from Ansible's perspective from AWS's perspective and ultimately the value in it for the customer. >> Stefanie: Yes. >> So I got to ask you one final question. >> Stefanie: Absolutely. >> And maybe as as reinvent is around the corner, what's next for the partnership? Obviously big news today, Manasi, looking down down the pipe- >> Stefanie: Big news today. >> What are some of the things that you think are going to become next that you can share? >> I mean at this point, and I'll pass it to Manasi to close us out, but we are continuing to follow, to meet our customers where they want to be. We are looking across our portfolio for different ways that customers want to consume within AWS. We'll continue to look at the procurement models through the partner programs that Manasi and the team have had. And to me the next step is really bringing in the rest of the ecosystem. How do we use this as a grounding step? >> Yeah, absolutely. So we are always listening to customer feedback and they want more Red Hat products in the marketplace. So that's where we'll be. >> In the marketplace. >> Congratulations great deal. >> Yes great work there guys. And customers always want more. That's the thing. But that's what keeps us going. So we love it. >> Absolutely. >> Thank you so much for joining John and me on the program today. It's been great to have you. And congratulations again. >> It's a pleasure. >> Thank you. >> For our guests and for John Furrier, I'm Lisa Martin. You're watching theCUBE Live from Chicago at AnsibleFest 2022. This is only day one of our coverage. We'll be back after a short break for more. (upbeat music)

>>Hey everyone. Welcome back to Chicago. Lisa Martin here with John Furrier. We're live with the Cube at Ansible Fest 2022. This is not only Ansible's 10th anniversary, John Wood. It's the first in-person event in three years. About 14 to 1500 people here talking about the evolution of automation, really the democratization opportunities. Ansible >>Is money, and this segment's gonna be great. Cub alumni are back, and we're gonna get an industry perspective on the automation journey. So it should be great. >>It will be great. We've got two alumni back for the price of wine. Scott Canine joins us, Director of Worldwide Automation at Kendra. A Nelson Shoe is back as well. Product marketing director at Red Hat. Guys, great to have you back on the, on the live cube. >>Oh, thank you for having us. And, and you know, it's really great to be back here live and in person and, and, you know, get a chance to see you guys again. >>Well, and also you get, you get such a sense of the actual Ansible community here. Yeah. And, and only a fraction of them that are here, but people are ready to be back. They're ready to collaborate in person. And I always can imagine the amount of innovation that happens at these events, just like off the show floor, people bumping into each other and go, Hey, I had this idea. What do you think, Scott? It's been just about a, a year since Kenel was formed. Talk to us about the last close to a year and what that's been like. Especially as the world has been so, chops >>The world been Yeah, exactly. Topsy turvy. People getting back to working in person and, and everything else. But, you know, you know, throw on that what we've done in the last year, taking Kendra, you know, outside of being a part of ibm Right. In our own company at this point, you know, and you know, you hear a lot of our executives and a lot of our people when we talk about it, like, Oh yeah, it's, you know, it's a $19 billion startup. We got freedom of action. We can do all these different things. But, you know, one of the ways I look at it is we are a $19 billion startup, which means we've got a lot of companies out there that are trusting us to, no matter what change we're doing, continue to deliver their operations, do it flawlessly, do it in a way so they can continue to, to service their clients effectively and, and don't break 'em. And, and so that to me, you know, the way we do that and the way I focusing on that is automation Ansible, obviously corridor strategy, getting there. >>Yeah. And I'd like to get your thoughts too, because we seeing a trend, we've been reporting on this with the cloud growth and the scale of cloud and distributed computing going cloud native, the automation is the front and piece center of all conversations. Automate this, make developers go faster. And with the pandemic, we're coming out of that pandemic. You post pandemic with large scale automation, system architecture, a lot more like architectural conversations and customers leaning on new things. Yeah. What are you seeing in this automation framework that you guys are talking about? What's been the hot playbook or recipe or, or architecture to, you know, play on words there, but I mean, this is kind of the, the key focus. >>Yeah. I mean, if you, one of the things that I com customer comp talks, I've been pulled into a lot recently, have all been around thinking about security, right? A lot in terms of security and compli, I think, I mean, think about the world environment as a whole, right here, everything that's been going on. So, so people are, are conscious of how much energy that's being used in their data centers, right? And people are conscious of how secure they are, right? Are they, you know, the, their end customers are trusting them with data information about them, right? And, and they're trusting us to make sure that those systems are secure to make sure that, you know, all that is taken care of in the right way. And so, you know that what's hot security and compliance, right? What can we do in the energy space, right? Can we do things to, to help clients understand better their energy consumption as, as, you know, especially as we get now in Europe to the winter months, can we do things there that'll help them also be better in that space, Right? Reduce their >>Costs and a lot more cloud rails obviously right there. You got closer and you got now Ansible, they're kind of there to help the customers put it together at scale. This has been the big conversation last year, remember was automate, automate, automate, right? This year it's automation everywhere, in every piece of the, the landscape edge. It's been big discussion tomorrow here about event driven stuff. This is kind of a change of focus and scope. Can you like, share your thoughts on how you see how big this is in terms of the, the, the customer journey >>In terms, I'm sorry, in terms of, >>In terms of their architecture, how they're rolling out automation, >>What's their Yeah, yeah. So, so in terms of their rolling out arch, arch in terms of them consuming architecture, right? And the architecture or consuming automation. Yeah. And rolling out the architecture for how they do that. You know, again, it, to me it's, it's a lot of, it's been focused around how do we do this in the most secure manner possible? How do we deliver the service to them and the most secure managers possible? How do they understand that it, that they can trust the automation and it's doing the right things on their environments, right? So it's not, you know, we're not pushing out or, or you know, it's not making bad policies >>And they're leaning on you guys. >>It's, it's not being putting malware out there, right? At the same time we're doing different things. And so they really rely on, on our customers, rely on us to really help them with that journey. >>I think a, a big part of that with Kendra as such a great partner and so many customers trusting them, is the fact that they really understand that enterprise. And so as, as Scott talks about the security aspect, we're not just talking to the IT operations people, right? We're talking across the enterprise, the security, the infrastructure, and the automation around that. So when we talk about hybrid cloud, we talk about network and security edge is a natural conversation to that, cuz absolutely at the edge network and security automation is critical. Otherwise, how are you gonna manage just the size of your edge as it grows? >>Yeah. And, and we've been, and that's another area that we've been having a a lot more conversations with clients on, is how do you do automation for IOT and edge based devices, right? We, you know, traditionally data center cloud, right? Kind of the core pieces of where we've been focusing on, but I, you know, recently I've been seeing a lot more opportunities and a lot more companies coming forward saying, you know, help us with the network space, help us with the iot space. We really wanna start getting to that level of automation and that part of our environments. And what >>Are some of the key barriers that customers are coming to you with saying, help us overcome these so that they can, you're smiling so that they can, can obviously attract and retain the right talent and also be able to determine what processes to automate to extract the most value and the most ROI for the organization. >>Yeah. And, and, and you know, that's, that's an interesting, the ROI conversation's always an interesting one, right? Because when you start having that with customers, some of the first things they think about, or the first, the natural place people go is, >>Oh, >>Labor takeout. I can do this with less people. Right? But that's not the end all be all of automation. In fact, you know, my personal view is that's, you know, maybe the, the the bottom 30%, right? That's kind of, then you have to think about the value you get above and beyond that standard operations, standardized processes, right? How are you gonna able to do those faster? How's that enabling your business, right? What's all the risks that's now been taken out by having these changes codified, right? By having them done in a manner that is repeatable, scalable, and, and, and really gets them to the point of, you know, what their business needs from an operational standpoint and >>Extracting that value. Nelson, talk about the automation journey from your perspective, How have you seen that evolve from your lens, especially over the last couple of years? >>It's a great question. You know, it's interesting because obviously all of our customers are at different stages of their automation journey. We have someone that just beginning looking at automation, they've been doing old scripts, if you will, the past. And then we have more that are embracing it, right? As a culture. So we have customers that are building cultures of automation, right? They have standups, they have automation guilds. It's, it's kind of a little bit of a, of a click. It's kind of, you know, building up steam in that momentum. And then we have, you know, the clients that Kindra works with, right? And they're very much focused on automation because they understand that they have a lack of resources, they don't have the expertise, they don't have the time to be able to deliver all this. Yeah. And that's really, Kendra really comes into effect to really help those customers accelerate their automation. Yeah. Right. And to that point, you know, we're doing a lot of innovation work with Kendra and we lean on them heavily because, you know, they're willing to make that commitment as a partner both on the, the, the day to day work that we do together as well as Ford looking at different architectures. >>Yeah. And, and the community aspect from our side internally has been tremendous in terms of us being able to expand what we'll be doing with automation and, and what a's been able to do with that community to get there. Right? Yeah. So to last month we did about 33 million day one, day two operations through automation, right? So that's what we've done. If you look at it, you know, if I break it down, it's really 80% of that standard global process stuff that we bring to the table. 20% of that is what our, our account teams are bringing specifically to their clients based on their needs and what they need to get done. Right. You know, one of my favorite examples of of, of this, right? We have a automation example out there for a, a client we've got in Japan, right? They tie, you know, they're, they're obviously concerned, you know, security a everything else that we've been talking about. >>They're also concerned about resiliency, right? In the face of natural disasters. Yeah. So they took our automation, they said, Okay, we're gonna tie your platform to seismic data that's coming through, and we understand what seismic data's happening. Okay, it's hitting a certain event. Let's automatically start kicking off resiliency operations so we can be prepared and thus keeps serving our clients when that's happening. Right? And that's not something like when you talk about a global team coming in and, and saying, we're gonna do all this. It's that community aspect, getting, getting the account focus, getting to that level, right? That's really brings value to clients. And that's one of the use cases, you know, and aaps enabled us to do with the a the community approach. We've got >>Now talk about this partnership. I think earlier when we were talking to Stephanie and Tom, the bottoms up Ansible community with top down kind of business objectives kind of come into play. You guys have a partnership where it's, there's some game changing things happening because Ansible's growing, continuing to have that scope grow from a skill set standpoint, expand the horizons, doing more automation at scale, and then you got business objectives where people wanna move faster in their, in their digital transformation. So to me, it's interesting that this part kind of hits both. >>It does really hit both. I mean, you know, the community cloud that Kendra has is so critical, right? Because they build that c i CF architecture internally, but they follow that community mantra, if you will. And community is so important to us, right? And that's really where we find innovation. So together with what we were call discussing about validated content earlier today becomes critical to build that content to really help people get started, Right? Validated content, content they can depend on and deliver, right? So that becomes critical on the other side, as you mentioned, is the reality of how do we get this done? Yeah. Right? How do we mature, how do we accelerate? And without the ability to drive those solutions to them to fix, if you are the problems that the line of business has. Well, if you don't answer those questions with the innovation, with the community, and then with the ap, it's, it, it does, it's gotta all come >>Together as, I mean, that community framework is interesting. I think we hear a lot in the cube, you know, Hey, let's do this. Sounds good. Who's gonna do it? Someone who's the operator. So there's a little skills gap going on. It's also a transformation in the roles of the operators in particular, and the dev, So the DevOps equation's completely going to the next level, right? And this is where people wanna move faster. So you're seeing a lot more managed services, a lot more Yes. Services that's, I won't say so much top down, but more like, let's do it and here's a play to get it done, right? Then backfill on the hiring, whether it's taking on a little bit of technical debt or going a little faster to get the proof points, >>Right? And I think one of the critical aspects is, you know, Ansible has it certified collections, right? And oftentimes we, we don't, I don't, I meet with customers two, three times a week, right? There's not a single one that doesn't emphasize the importance of partners and the importance of certified collections, Right? And kindra is included in that, right? Because they bring a lot of those certified collections. Use them, leverage them, it's helps customers get a jumpstarter, right? It's a few, it's their easy button, right? But they only get that and they value that because of the support that's there. >>Yeah. Right? They get the with >>The cert. Yeah. I was gonna say, just adding on the certified collections, right? We, so, you know, it was, it was great to see the hub come out with those capabilities because, you know, as we've gone through the last 12 months and, and change, one of the things that we focused more in on is network devices, network support, right? And, and so, you know, some of the certified collections out there for Cisco for F five, right? Some of those things we've been able to take back in and now build on top of with the expertise that we, we have in that space as well. And then use that as a starting point to more value for our clients. >>How is Kentrell working together with, with Red Hat and with Ansible to help organizations like you mentioned Nelson, they're on the journey varies considerably. Some are well on their way, others aren't. But for those to really start developing an automation, first culture, we talked a lot about cultural ship, we talked about it this morning. You can feel the power of that community and driving it, but how do you guys work together to help companies and any industry kind of really start understanding what an automation first culture is and then building it internally and getting some grounds? Well, >>Well, it's interesting, right? One of the, one of the things that really is we found really helpful is assessments, right? So you have silos and pockets of automation, and that's that challenge, right? So to be able to bring that, if you are automation community within an enterprise together, we often go out and we'll do an assessment, right? An automation assessment to really understand holistically how the enterprise could leverage automation not just in the pockets, but to bring it together. And when they bring that automation together, they can share, playbooks can share their experiences, right? And with Kindra and the multiple and the practices they have, right? They really bring that home from an industry perspective. They also bring that home, if you will, from a technology perspective. And they bring that together. So, you know, Kindra in that respect is the glue for our customer success. >>What's news? What's the next big thing that you guys see? Because if this continues down the road, this path, people are gonna get, the winds gonna get the successes. The new beachhead, if you will, is established. You got the edge around the corner. What's next for you guys in the partnership? How do you see it developing? >>No, we're looking at >>No, it's all good. So really, you know, I, I mentioned it earlier and, and the jour the automation journey paralleled by innovation, right? Customers today are automating, they're doing a great job. There's multiple tools out there. We understand we're not gonna be the only tool in the shed, but Ansible can come in and integrate that entire environment. And in a hybrid cloud environment, you want that there, right? I think what next is obviously the hybrid cloud is critical. The edge is critical, right? And I think that, you know, the needs and the requirements that Kindra hears that we have is kind of that future. And, you know, we, we often, often in, in Red Hat, we talk about a north star, right? And when I work with partners, ikin, do we talk about the North Star, where we want to get to? And that is the acceleration of automation. And I think both by the practical aspect of working with our customers and the innovation as partners, as business partners, technology partners will help accelerate >>That. Yeah. Scott, your perspective to bridge to the future is obviously hybrid and edge, how you bringing your customers along? >>Yes. So, so we see, you know, when we talk about my, when I talk about my automation strategy, our automated strategy, right? It's about being automated, orchestrated and intelligent, right? Kind of those, those three layers of the stack. We've been building out a lot of work, what we call our integrated AIOps layer for actionable insights, right? We've got a, you know, a goal to integrate that and, and we have integrated into our automation service for how we're delivering the whole package to our clients so they can better see opportunities for automation. What's the best way to go about it? You know, what are the, what are some of the, the issues they have, vulnerabilities they have in their environment and really bringing it to them in, in a real holistic manner. In fact, we internally, we call it our F five steering wheel, right? Based on the, the race thing, right? >>Because you think about the, the racing cars, f fives know they're right there, right? They got everything they need in front of 'em. Yeah. So our goal is been to, to include that into our automation view and service and build that out, right? So that's one way we're doing it. The additional way is, is through some announcements you probably heard, hopefully heard the last couple weeks through something called Kendra Bridge, right? Kendra Bridge is more the digitization of, of the way we deliver services for our clients to make it easier for them to consume and, and to, to make the barrier to entry for things like getting automation, getting it more in their environment, right? Lower as much as possible, right? So really integrated AIOps kind bridge. Those are really the two ways we see it as, as going forward. >>It's interesting, you know, we live through a lot of these different inflection points in the industry. Every time there's a big inflection point, there's more complexity that needs to be tamed, you know? And so you got innovation. If you got innovation coming and you got the clients wanna simplify and tame the complexity, this is a big part of what you guys do. >>Absolutely. Yeah. I mean, how do we, you know, most, when the clients come to us, right? Like I said, one, it's about trust. They trust us to do it because we can make it easy for them to not have to worry about that, right? Yeah. They don't have to worry about what it takes to secure the environment, manage it, run it, design it, build it for the, the cloud. We give 'em the ability, we give them the ability to focus on their core business while we do the stuff that's important to them, which >>Is absolutely critical that you, you can't emphasize trust in this relationship enough. I wish we had more time, guys, you're gonna have to come back. I think that's basically what this is boil down to. But thanks so much guys for talking with John and me about how Kendra and and Ansible are working together, really enabling your customers to, to unlock the value of automation across their organization and really make some big business changes. We appreciate your insights and your time. Fantastic. Thank you. Happy to do it and happy to do it any time. All right. Our pleasure. Thank you so much for our guests and John Furrier. I'm Lisa Martin. You're watching The Cube Live from Chicago. This is day one of our coverage of Ansible Fest 22. Don't go anywhere. Our next guest joins us in just a minute.

(gentle music) >> Hello from Chicago, Lisa Martin here at AnsibleFest 2022 with John Furrier. John, it's great to be here. The transformation of enterprise and industry through automation. This is not only the 10th anniversary of Ansible, this was the first in-person AnsibleFest since 2019. >> It's awesome, it's awesome, Lisa, and I want to welcome everyone to our live performance here in Chicago. We were remote for two years, 2019 in Atlanta. AnsibleFest, part of Red Hat now, Red Hat part of IBM. So much has happened in the past couple years and I think one of the things that we're going to cover this week here in Chicago, is the evolution of Ansible, where it fits into the new cloud-native ecosystems emerging, and also, kind of, what it means for developers and operators. And we're going to see a lot of that here at AnsibleFest with wall-to-wall coverage, keynote just happened. Very interesting to see, you know, Ansible stayed true to their knitting, as you say, you know. What do they do? No big announcements. Some big community news. But humble. >> Very humble. Very humble, but also very excited. All the keynotes did a great job of addressing that community, and being grateful to the community for, really, the evolution that we see at Ansible and now 10 years later. They were talking a lot about smoothing operations for the developers, democratizing automation across the organization. They talked a little bit about that skills gap. I wanted to get your opinion, 'cause as we know there's, they talked about it from a demand perspective, there's over 300,000 open positions on LinkedIn for Ansible skills. So a lot of opportunity there, a lot of opportunity for them to help democratize automation across organizations. >> Yeah, I mean, I think the big theme last year we heard, "Three things, top three things at AnsibleFest 2021, Animation, Automation, Automation." Again, this year the same theme, "Automate everywhere" is what they're talking about. But I think you're right, there's a cultural shift where the entire cloud ecosystems kind of spun to the doorstep of what Ansible's ecosystem stood for for many years in the decade, which is configuration, running things at scale. That notion is now persistent across all the enterprise. And I think the key takeaway from the keynote, in my opinion, is that configuration and automation around devices and infrastructure stuff is an enterprise architecture now, it's not just a, kind of a corner case, or a specific use case, it's going to be native across the entire enterprise architecture. And that's why we heard a lot of cultural shift conversations. And that is where the people who are running the Ansible stuff, they're going to be the keys to having the keys to the kingdom. And I think you're going to see a lot more of this automation at scale. I love the introduction of ops-as-code, that's a little piggyback off of infrastructure-as-code and infrastructure-as-configuration. They're saying operations now is the new software model and it's like ops dev, not dev ops. So it's really interesting to see how the operator is now a very big important role in the next level of cloud native. And it's really exciting because this is kind of what we've been reporting on theCUBE, for over 12 years. So, watching Ansible grow organically into a powerhouse community is very interesting. To see how they operationalize this, you know, going forward. >> Well the operator's becoming really pivotal catalysts in this next way, that you've been covering for 12 years. You know, if we think about some of the challenges and the barriers to adopting automation that organizations have had, one of them has been skills, staff rather. The other has been, "Hey, we need to really determine which processes to automate, that's actually going to give us the most ROI, most bang for our buck." They talked a little bit about that today, but that's still something that Ansible is working with its customers and the community to help sort of demystify. >> Yeah and I think that they were front and center around, "You on the room," people in the room, "you make this happen." They're very much, it's not a top-down corporate thing, Ansible staying true to their roots as I mentioned. But the thing about skills gap is interesting, you heard Kaete Piccirilli talking about, "Level Up how your organization automates, push your people, expand your scope." So the theme is, the power is in the hands of this community to essentially be the new enterprise architecture for operations. At the same time that feeds the trend around, we're seeing this accelerated cloud-native developer we're seeing, we're going to be at KubeCon next week, that cloud-native developer, they want to go faster, they want self-service. So you're seeing higher velocity cloud-native development putting pressure on the ops teams to level up, so the theme kind of connects for me. I think Red Hat has got it right here, with Ansible, that the theme is shifting to ops better get their act together, to level up and to the velocity of what the developers are expecting. At the same time, giving them the freedom to be using infrastructure-as-code, infrastructure-as-configuration, and ultimately, ops-as-code. To me, I think this is like the evolution of how infrastructure-as-code, which is the nirvana of DevOps, now is ops-as-code. Which means, if that's true, ops becomes much more invisible, if you will, which is what developers want. >> And we're going to be breaking down ops-as-code today, no doubt, in our conversations with some of the great Ansible community folks and partners and leaders that we have on, as well as tomorrow in our full two days of coverage. You talked about cultural shift, we talk about that a lot John, it's challenging, but one of the things I think that was very palpable this morning, is the power of the Ansible community. Not just those folks that are here with us in Chicago, but all the folks watching virtually online. >> Yeah. >> Truly help drive that cultural shift that is needed for organizations to really be able to streamline cloud ops. >> Yeah and I think Adam Miller who came on, I thought his portion was excellent, around community. He talked about, you know, the 10 years, put a little exclamation point on that. Managing the communications within the community. He actually brought up IRC and Slack and then, "We have Discord." And they introduced a new standard for communications it's called Matrix, which is open-source based. And even in their decision making, their principles around open source stay true. Again, they checked the box there, I thought that was really cool. The other thing that, within the meat of the product, the automation platform, Matt Jones was talking about the scale, the managing at scale, is one thing. But the thing that I think that hit, jumped out at me, was that this trusted automation messaging was really huge. Signing, having signatures, that really hits the supply chain that we've been talking about, and we're going to talk about it next week at KubeCon, the software supply chain is trusting the code. And I think as you have automation, it's a really big part of the new platform. So, I thought that was really the meat on the bone there. >> That was a very strong theme, was the trust this morning. You know, another thing that was important was Walter Bentley, who's coming on, I believe, later today, talked about how organizations really need to think about the value that automation can deliver to the business and then develop an automation strategy, really thinking at it strategically rather than what a lot of folks have done. And they've put automation in sort of in silos and pockets. He's really talking about, how can you actually make it strategic across the organization and make sure that you really fully see and understand and can articulate the value to the business, from a competitive advantage perspective, that it's going to deliver. >> Yeah, and Stefanie Chiras who's coming on too, she mentioned a lot about the multi-cloud, multi-environment layer, how Ansible can sit across all the environments and then still support the cloud-native through what she called "an automation loop". That's going to be really talking to what we're seeing as multi-cloud or super-cloud, next-gen cloud, where Ansible's role of automating isn't just corner case in the enterprise. Again, if it's an enterprise-wide architecture, it will be a centerpiece of multi-cloud, multiple capabilities. Whether that's compatibility services or, you know, stuff running best of breed on different clouds. 'Cause, obviously Amazon was on stage here, they're talking about this, big Ansible supporter. So, we've got Google supporting Ansible, so you got the multiple clouds and even VM-Ware environments. So, Ansible sits across all this. And so, I think the big opportunity that I'm seeing come out of this, is that if Ansible is in this position, this could be a catalyst for them to be the multi-cloud hybrid architecture for configuration and operations, and I think, the edge is going to be a really interesting conversation. We have a lot of guests coming on, I'll talk about that. But, I think running distributed workloads across multiple clouds in multiple environments, that's a killer app and we'll see if they can pull it off. We're going to be drilling everyone on that topic today, so I'm looking forward to it. >> We're going to be dissecting that. I like how you paint that picture of Ansible really as the nucleus of that hybrid cloud strategy. You know, so many organizations are living in a hybrid cloud world for many reasons, but for Ansible to be able to be that catalyst. And question for you, if we think about that, when we talk about multi-cloud strategically or organically or whatnot, where is automation moving in terms of the customer conversation? We know Ansible's really focused on smoothing the developer experience, but where is automation going, in your vision, up the C-suite stack? >> Well, multi-cloud is a C-suite message and they love to hear that, but you talk to anyone who's in the trenches, they hate multi-cloud. It's more complexity and there's a lot of issues around latency. So what you're seeing is, you're starting to see an evolution of more about compatibility and interoperability. And this is kind of classic enterprise abstraction layers when you start getting into these inflection points, as things get better, so it gets sometimes more complex. So I think Ansible's notion of simplicity and ease of use, could be the catalyst for this abstraction layer between clouds. So it's all about reducing the complexities, because at the end of the day, if you want to do something on multiple clouds, whether that's run common services across, that's not making it simpler. You got to, it's going to be harder before it gets easier. So, if that makes any sense. So doing multi-cloud sounds great on paper, but it's really hard and that's why no one's really doing it. So you're going to start to see multi-cloud, what we call super-cloud, which is more capabilities on one cloud. And then having them still differentiate the idea that some standard's going to emerge, is complete fantasy. I think you're going to, we still need more innovation. Amazon does a great job, Microsoft's coming up on number two position as well, the clouds still need to differentiate. But that doesn't change Ansible's position. They can still be that shim layer or bolt-on, to whatever clouds do best. If you run 'em on machine learning on Google, that's cool. You want to use Amazon for this? How do you make those work? That's a hard problem. And, again, that's where automation ends up. >> And with that context, do you think that Ansible has the capability of helping to dial down some of the complexity that's in this hybrid multi-cloud world? >> Yeah, I mean, I think the thing about what's going on great here, that's unique in the history of the computer industry, is open source is so powerful and it continues to power away with growth. So, more code is coming. So, software supply chain is a big issue, we heard that with the trusted thing, but also now, how people buy now is different. You can actually try stuff out on open source and then go to Red Hat, Ansible, and say, "Hey, I'm going to get some support." So there's a lot of community collective intelligence involved in decision making, not just coding, but buyer selection and consumption. So the entire paradigm of purchasing software and using it, has completely changed. So, that puts Ansible in a leading position because they got a great community, and now you've got open source continuing to thrive away. So, if you're a customer, you don't need the big enterprise sales pitch you can just try the code, if you like it, then you go with Ansible. So it's really kind of set up nicely, this cloud market, for companies like Ansible, because they have the community and they got the software, it's open and it is what it is, it's transparent, everything's above board. >> Yeah, you know, you talk about the community, you mentioned Matrix earlier, and one of the things that was also quite resonant during the keynote this morning was the power of collaboration and how incredibly important that is to them, to stay native to their open-source roots, as you you said. But also really go to where the customers are. And they talked about that with respect to Matrix and Discord and that was an interesting, this is the community reaching out to really kind of grow upon itself. >> Well, being someone who's used all those tools, even IRC 'cause I'm old, all the old folks use IRC. Then the, kind of, Gen X'ers use, and the millennials use Slack. Discord, the way they mentioned Discord, it's so true. If you're a gamer, you're younger, you're using Discord. Now, Matrix is new, they're trying to introduce an open source, 'cause remember they don't control Discord and they don't control Slack. So Slack's Salesforce now, and Discord is probably going to try to get bought by Microsoft, but still, it's not open. So Matrix is their open-sourced chat service. And I thought that was interesting and I think, that got my attention, because that went against the principles of users that like Slack. So, it'd be great. I mean if Matrix, if that takes off, then that's going to be a case study of going against-the-grain on the best-of-breed package software like Slack or Discord. But I think the demographic shift is interesting. Discord is for younger generations, let's see how Matrix will do. And the uptake wasn't that big. Only been around for a couple months, we've seen almost 5,000 members. But, you know, not a failure. >> Right. >> But not a home run either. >> Right. Well we'll have to see how that progresses- >> Yeah, we'll see how that plays out. >> as all of the generations in the workforce today try to work together and collaborate. You know, if we think about some of the things that we're going to talk about today and tomorrow, business outcomes, increasing business agility, being able to ensure compliance, with security and regulatory requirements, which are only proliferating, really also helping organizations to optimize those costs and be as competitive as they possibly can. So I'm excited to dissect the announcements that came out today, some of the things that we're going to hear today and tomorrow, and really get a great view of the automation infrastructure marketplace and what's going on. >> Yeah, it's going to be great. Infrastructure-as-code, infrastructure-as-config, operations-as-code, it's all leading to, you know, distributed computing edge. It's hybrid. >> Yep. All right John- >> Yeah. >> looking forward to two days of wall-to-wall CUBE coverage with you, coming to you live from Chicago, at the first AnsibleFest in person, since 2019. Lisa Martin and John Furrier with you here all day today and tomorrow, stick around, our first guest joins us. We're going to dissect ops-as-code, stick around. (gentle music)

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

(upbeat music) >> Welcome to AnsibleFest, 2021, the virtual version. This is The Cube and my name is Dave Volante. We're going to dig into automation and its continuing evolution. Tom Anderson is here. He's the vice president of Red Hat Ansible, the automation platform. And Richard Henshall is also here, Senior Manager of Ansible Product Management, of course, at Red Hat. Guys, welcome to the cube. Good to see you. >> Thanks for having us. >> Thank you for having us Dave. You're welcome, so Rich with this latest release of the Ansible Automation Platform, AAP, we'll get the acronyms out of the way. The focus seems to be an expanding the reach of automation and its potential use cases. I mean, I'll say automation everywhere, not to be confused with the RPA vendor, but the point is, you're trying to make it easier to automate things like provisioning, configuration management, application deployment, throw in orchestration and all these other IT processes. Now, you've talked about this theme in previous releases of AAP. So what's new in this release? What can customers do now that they couldn't do before? >> Yeah, it's a good question thank you. So, we look at this in two dimensions. So, the first dimension we have is like where automation can happen, right? So, you know, we always have traditional data center, clouds being been very prevalent for us for the last, you know, sort of five, 10 years in most people's view. But now we have the Edge, right? So now we have Edge computing, which is sometimes a lot more of the same, but also it comes with a different dynamic of how it has to be sort of used and utilized by different use cases, different industry segments. But then, while you expand the use cases to make sure that people can do automation where they need to do it and make sure if we don't close to the Edge or close to the data center, based on where the technology needs to be run, you also have to think about who's now using automation. So, the second dimension is making sure that different users can take access. You mentioned like application deployment, or infrastructure, or network configuration. We expand the number of different users we have that are starting to take advantage of Ansible. So how do we get more developers? How do we get into the developer workflow, into the development workflow, for how Ansible is created, as well as how we help with the operational, the posts deployment stage that people do operating automation, as well as then the running of Ansible Automation Platform itself. >> Excellent, okay. So, in thinking about some of those various roles or personas, I mean, I think about product leads. I would see developers, obviously you're going to be in there. Managers I would think want that view. You know the thrust seems to be, you're trying to continue to enhance the experience, for these personas and others, I suppose, with new tooling. Maybe you could add some color to that and what's happening in the market Tom if you take this and Rich chime in, what's happening in the market that makes this so important? Who are the key roles and personas that you're targeting? >> Yeah. So, there's a couple of things happening here. I mean, traditionally the people that had been using Ansible to automate their subsystems were the domain expert for that subsystem, right? I'm the storage operations team. I'm the network operations team. I'm using this tool to automate the tasks that I do day to day to operate my piece of the sub system. Now, what they're being asked to do is to expose that subsystem to other constituencies in the organization, right? So they had not, they're not waiting for a call to come in to say, can I have a network segment? Can I have this storage allocated to me? Can I deploy these servers so I can start testing or building or deploying my application. Those subsystems need to be exposed to those different audiences. And so the type of automation that is required is different. Now, we need to expose those subsystems in a way that makes those domain owners comfortable. So they're okay with another audience having access to their subsystem. But at the same time, they're able to ensure the governance and compliance around that, and then give that third-party that developer, that QE person, that man, that business, that line of business manager, whoever it might be, that's accessing that resource, a interface that is friendly and easy enough for them to do. It's kind of the democratization. I know it's a cliche, but the democratization of automated automation within organizations, giving them roles, specific experiences, of how they can access these different subsystems and speed their access to these systems and deploy applications. >> So if we could stay on that for a second, cause that's a complicated situation. You're now opening this up. You Richard mentioned the Edge. So you got to make sure that the person that's getting access has access, but then you also have to make sure that that individual can't screw it up, do things that you don't want that individual to do. And it's probably a whole other set of compliance issues and policy things that you have to bake in. Is that, am I getting that right? >> Yeah. And then that's the aspect of it. When you start to think, you know, Tom listed off there, you know, 10, you can just keep adding different sort of personas that individuals that work in roles, identify with as themselves. I'm a network person, I'm a storage person. To us they're all just Ansible users, right? There may be using a slightly different way, maybe using it slightly different places, but they're just an Ansible user, right? And so as you have, like those people that just like become organically, you've now got thousands potentially of Ansible users inside a large enterprise organization, or if you know, a couple of hundred if your smaller. But you're then go, well, what do I do with Ansible, right? And so at that point, you then start to say, now we try to look at it as what's their use of Ansible itself, because it's not just a command line tool. It's got a management interface, it's got analytics, we've got content management, we've got operational runtime, we've got responsiveness to, you know, disaster recovery scenarios for when, you know, when you need to be able to do certain actions, you may use it in different ways at different places. So we start, try and break out, what is the person doing with Ansible Automation Platform at this part of their workflow? Are they creating content, right? Are they consuming content, or are they operating that automation content for those other constituent users that Tom referred to. >> Yeah, that's really helpful because there's context, there are different roles, different personas need different contexts, you know, trying to do different things. Sometimes somebody just wants to see the analytics to make sure it's, you know, hey, everything's green, Oh, we got a yellow, versus, hey actually want to make some changes and I'm authorized to do so. Let's shift gears a little bit and talk about containers. I want to understand how containers are driving change for customers. Maybe what new tools you're providing to support this space? What about the Edge? Yeah, how real is that in terms of tangible pockets or patterns that you can identify that require new types of capabilities that you're delivering? Maybe you can help us unpack that a little bit. >> Okay so, I think there's two ways to look at containers, right? So the first is how are we utilizing the container technology itself, right? So containers are a package, right? So the amount of work we've been doing as Ansible's become more successful in the last couple of years, separating content out with Ansible collections. The ability to bring back manage, control a containerized runtime of Ansible so that you can lifecycle it, you can deploy it, it becomes portable. Edge is important there. How do I make sure I have the same automation running in the data center as the same automation running out on the Edge, if I'm looking at something that needs to be identical. The portability that the packaging of the container gives us, is a fantastic advantage, given you need to bring together just that automation you want. Smaller footprint, more refined footprint, lifecycle manage footprint. But at the same time, containers are also a very useful way of scaling the operation, right? And so as red hat puts things like Open Shift out in all these different locations, how can we leverage those platforms, to push the runtime of Ansible, the execution component, the execution plane of Ansible. How into anywhere that's hospitable for it to run? And as you move out towards Edge, as you move further away from the data center, you need a more ubiquitous sort of like run-time plane that you can put these things on. So they can just spin up when as, and when you need to. Potentially even at the end, actually being on the device, because at the same time with Edge, you also have different limits around how Edge works. It's not just about, hey I'm wifi points in an NFL stadium, actually, you're talking about I'm at the end of a 2000 mile, you know, piece of cable on an oil pipeline or potentially I'm a refinery out in the Gulf of Mexico. You know, you've got a very different dynamic to how you interact with that end point, than you do when it's a nice big controlled network, you know, powered location, which is well-governed and well-orchestrated. >> That's good. Thank you Rich. So Tom, think about automation, you know, back in the day, seems like a long time ago, but it really wasn't, automation used to scare some IT folks, because you know, sometimes it created unintended consequences or maybe it was a cultural thing and that you didn't want to automate themselves out of a job, but regardless. The cloud has changed that mindset, you know, showing us what's possible. You guys obviously had a big role in that, and the pandemic and digital initiatives, they really have made I call it the automation mandate. It was like the fourth March to digital, at least that's how I see it. I wonder if you could talk about, how you see your users approaching automation in as it relates to their business goals. Do you think automation is still being treated sometimes with trepidation or as a side project for some organizations or is it really continuing to evolve as a mainstream business imperative? >> Yes, so Dave we see it continuing to evolve as a strategic imperative for our customers. I mean, you'll, hear some of the keynote folks that are speaking here today. I've done an interview or doing an interview with Joe Mills from Discover, talking about extreme automation throughout Discovers organization. You'll hear representatives from JPMC talk about 22,000 JPMC employees contributing automation content in their environment, across 20 or 22 countries. I mean, just think about that scale, and the number of people that are involved in automation now and their tasks. So I think it's, I think we are, we have moved beyond or are moving beyond that idea that automation is just there to replace people's jobs. And it's much more about automation replacing the mundane, increasing consistency, increasing security, increasing agility, and giving people an opportunity to do more and more interesting stuff. So that's what we hear from our customers, this idea of them building. And it's not just the technology piece, but it's the cultural piece inside organizations where they're building these guilds or communities of practice, bringing people together to share best practices and experience with automation, so that they can feel comfortable learning from others and sharing with others and driving the organization forward. So we see a lot of that, and you'll hear a lot of that, at some of the Ansible Fest sessions this week. >> Well, I mean though I think that's a really important point. The last point you made about the skills, because I think you're right. I think we have moved beyond it's just job replacement. I don't know anybody who loves provisioning LUNs and say, oh, I'm the best in the world at that. It's just kind of something that was maybe important 10, 15, 20 years ago, but today, he should let the machines do that. So that's the whole skills transformation, is obviously a big part of digital transformation. Isn't it? >> It absolutely is. And frankly, we still hear, it's an impediment, that skills shortages are still an impediment to our customer success. They are still skilling up. I mean, honestly, that's one of the differentiators, for Ansible, as a language, a human readable language, that is easy to learn, easy to use, easy to share across an organization. So that's why you see job boards, and whatnot with so many opportunities that require or, or ask for Ansible skills out there. It's just a, it's become sort of a ubiquitous automation language in organizations, because it can be shared across lots of different roles. You don't have to be a Ruby software developer or a Python software developer to create automation with Ansible. You can be Tom Anderson or Rich Henshall. You don't have to, you don't have to be the, you know, the, the sharpest software developer in the world to take advantage of it. So anyway, that's one of the things that kind of overcoming some of the skills apprehension and bringing people into this, into the kind of new environment, of thinking about automation as code, not software code, but thinking of it like code. >> Got it. Guys we've got to leave it there, but Rich, how about you bring us home. We'll give you the last word. >> I mean, I think, you know what Tom just said there I think, about the skills side of things, is I think that the part that made it resonates the most. I mean I was a customer before I joined Red Hat, and trying to get large numbers of people, onto a same path, to try and achieve that outbound objective, that an organization has. The objective of an organization is not to automate, it's to achieve what is needed by what the automation facilitates. So how do we get those different groups to go from, Hey, this is about me, to this is actually about what we're trying to achieve as a business what we're trying to facilitate as a business, and how do we get those people easier access, a reduced barrier of entry to the skills they need to help make that successful, that compliments what they do, in their primary role, with a really strong secondary skill set that helps them do all the bits and pieces they need to do to make that job work. >> That's great, I mean you guys have done a great job, I mean it wasn't clear, you know, decade ago, or maybe half a decade ago, who was going to win this battle. Ansible clearly has market momentum and has become the leader. So guys congratulations on that and good job. Keep it going. I really appreciate your time. >> Thank you. >> Thank you. Thanks. >> Okay. This is the cubes, continuous coverage of Ansible Fest, 2021. Keep it right there for more content that educates and inspires. Thanks for watching. (upbeat music)

(bright intro music) >> Hello and welcome to theCUBE coverage of AnsibleFest 2021, virtual, hybrid, all online now. It's been a hell of a year. It's been going great with all the interactions. AnsibleFest 2021, Carol Chen is here. She's the Principal Community Architect for Ansible Community with Red Hat. Carol, thanks for coming on the AnsibleFest 2021 virtual coverage. >> Thanks for having me here, John. >> You know, one of the things about the pandemic I was mentioning, there's the online communities have been really, that have been online, have thrived. Developers know how to do virtual, and virtual, first, now is becoming a norm for developers. So the pandemic, although it's been a really big inconvenience for many, developers, actually, haven't been truly impacted other than the face to face interactions around hallway conversations and events. You're seeing a lot more community open conversations happening more than ever before, just the trend itself was hot. Now you have more people collaborating. What's the state of the Ansible Community right now? Because you know, online content at an all-time high, I'm seeing videos hit. I've seen a lot of content flowing. All around the internet seems to be more action. What's the state of the Ansible Community? >> Yeah, definitely. And actually, from the very start Ansible Community is a very much online community because of the diverse nature in terms of, you know, geographical distribution and just people from all of the world coming together. So initially, I mean, of course we do have like in-person meet-ups, which were a popular thing before the pandemic. That kind of took a little backseat and while it turned virtual, initially, people were like wondering what to do, but, you know, we are used to video conferences and online chats. So virtual meet-ups became quite a popular thing in the first half of the pandemic. So pretty much most of last year, we actually saw a slight rise in the number of, the median number of attendees at these meet-ups, because it's more accessible. You can attend from home, you can, you know, you don't have to go to a physical place to attend these meet-ups. However, this year we are starting to see some virtual fatigue and, you know, the numbers are dropping a little bit, but, you know, hopefully with the, some parts of the world are opening up and we are seeing some meet-ups coming into, in person again, depending on the region, of course, because it's not the same around the world. But I think that the need for people to connect socially is always there, whether it's online or in person. And the Ansible Community is pretty strong in that. And I want to stress that a lot of these meet-ups are organized by the community members, not necessarily by Red Hat or the Ansible team. So, you know, the desire to connect with other people in the community has always there and it's going on strong. >> Yeah, that's a good call out on the community side. I think that the affinity groups around the communities, self forming these meet-ups. >> Right. >> People want to meet in person, that's going to come back. You're starting to see that hybrid. But it's also, you're starting to see again, a fatigue for being like attending these virtual events. But at the same time, you're seeing the asynchronous consumption still go high, too. You're seeing, "Okay, I can do a fly by the event." Or if it's in person, "I'd prefer that." But there's still a lot more asynchronous going on, and a lot more opportunities to contribute. And you guys have done this contributor summits virtually. Can you talk about that trend? Tell me about the virtual contributor summits. >> Sure. So of course we have our regular community meetings, weekly, in fact. But the contributor summit is a place where we can actually gather, previously it was face-to-face, usually part of AnsibleFest, like the day before or after, depending. And, you know, to really, you know, hash out different discussions and more in-depth technical analyses of different parts of the project that we were working on. Even though, virtually, we are still able to do that, and we are, actually, able to increase in frequency of these events. Usually, it used to be once or twice a year, depending on whether or not we have, when we have the AnsibleFest. But last year we had three contributors summits. And this year, the third one will happen along with AnsibleFest in September, end of September, so in this week. So yeah, you know, there's definitely the advantage of making things easier to, for participants. But um... >> Talk about the vibe- Talk about the vibe of the summit. I mean, these contributors. I mean, what's it like and what are people experiencing? Are they just contributing code? They working on projects? Is it hackathons? Is it more, >> Right. >> What's the format of, what are people preferring? What's the best practice? >> So, what we want to encourage is not just one person giving presentations and like a one-way thing, but actually a dialogue. So a lot of these discussions are kind of interactive. So we use tools that allow people, not just like streaming one direction, but people can also appear on video and talk and express their opinions and join the discussions or in chat if they prefer not to show their face. But in any case, it's a lot of times it's not a full presentation, but perhaps an introduction for 5, 10 minutes. And then we go to discussion of a certain topic in-depth. So it's a very, I would say discussion-based, and also we are introducing a hackathon at this contributor summit, because I think it's quite a popular thing for people to get hands-on experience or work on something right away with people to support them then and there. So, you know, you can get results in real-time. So in actual fact, even before the pandemic, our contributor summits have had like, a virtual online component. So we were doing hybrid events before they were, you know, called popular hybrid events, but... >> Before they were necessary, it was cool. >> Right, Right. Exactly. So, because like I said, our contributors are from around the world, so we always made sure that they had a way of participating in the contributor summit as well. >> Yeah. I think that's really important to point out. I mean, I won't say it's cool to do hybrids necessary now because of the pandemic, but that format actually is interesting because you got a linear event that's physical face to face. Certainly that's super valuable when that comes back. But now that the online side has kind of been tied together with the simulated live asynchronous capability, you have this new format. Talk about how you guys are taking that to the next level around trust. Because one of the things about being face-to-face and then being online and knowing people is working together and getting a feeling of trusting each other, right? So, this is a- >> Right. huge part of community. >> How are you guys, now that we're more dispersed than ever, how are you guys handling, or facilitating and nurturing that trust equation? >> Right. So as a open source project, one of the key things is we do a lot of the things in the open. We, you know, the pull request, the development of the code is all done in the open. That's, you know, a very kind of implicit trust that you can have through that. And also the community meetings are open up to the public. Anybody can join if they're interested in. And even if you're not able to join the meetings because time zones or whatever, we share the meeting minutes after the meetings to everyone. Which brings me to, we actually started a newsletter for the community called the Bullhorn, since last April, I think. Because, you know, again, we are trying to explore more channels to be able to reach to different people who may not be able to attend in person, or even during the same time as the community meetings. So they can have this bi-weekly newsletter every two weeks that, you know, shares the meeting minutes. What has been discussed, the new developments in the community, the new collections, updates, new tools and so on. So definitely we see, like, we want to improve the communication to the community and ways that they can provide feedback to us as well. >> And that's called the Bullhorn? That's just getting the word out? >> Yeah, Bullhorn. Yes. Thank you. >> It's like the updates, like it's like, you know, a quick, quick executive summary of kind of what's happening. Is that kind of the vibe? >> Right, Right. >> Okay. Well, I want to ask you specifically, I heard about this new Community Steering Committee. What's the purpose of this? What's this evolving into? Can you give us some background on the purpose and the objective of the community? >> Yeah Sure. Yeah. We established the Ansible Community Steering Committee earlier this year, and as we were saying that the Ansible project is growing, so of course the user community, and also, they're very happy to say that the contributor community is growing. So, you know, we want to provide a better structure for the upstream Ansible project. And a lot of changes are taking place that we want to have some, a group of people to be able to facilitate that. For example, people are, want to make, create new collections, Ansible collections, for automated technologies that they are, you know, working on, or even contribute to existing collections that they have invested interest in. So what are some of the procedures and policies that are needed? Right? So the Steering Committee defines these procedures and make sure that the new content coming in are in compliance to the policies and so on. I mean, this kind of decision-making and stuff has been happening in the committee, I mean the community in an ad hoc manner, to a large extent, even before this. But having the Steering Committee will provide, to add more structure, like I said, and also guidance and accountability for the Ansible Community. >> That's awesome. You know, I love, first of all, I love your title, Principal Community Architect. And you know, one of the things I've always been a big fan of with Ansible, and now as part of Red Hat, is one, Red Hat didn't screw up Ansible. They let it become what it was and became really big with the combination. But the community has always been content driven. And now you've got recipes, you've got collections, you've got content, but the community piece is key. And right now, more than ever with the pandemic, community is more important than ever before. Open source is more important than ever before. How do you look at the architecture of how to sustain and evolve communities to be more inclusive and to grow and to survive and thrive post pandemic? What's your learnings? What's your vision on architecting community for the future? >> I think the key thing is to really find channels and ways to listen to the community. We talk about how to reach our newsletter or whatever, meetings to the community, but it's also what's coming from them. If we don't listen to what they have to say, we don't know what they want and how we can make the community better, the process better for them. I mean, I've been managing different open source communities before Ansible, but every community is different, right? I cannot say what worked for the previous community works for this. So I always try to reach out to the current members in the Ansible Community and hear what they have to say, their complaints, their criticisms, good and bad, because, you know, without those feedback, we cannot grow and we cannot improve. So, and I myself, I've lived in three different continents. So I know the struggle of whether it's like language barriers or time zone restrictions. So, you know, we keep all these in mind as we, you know, build our relationships with the community. >> And I think there's, I think there's a real opportunity with this new virtual standards that not yet emerged. I mean, you mentioned you've been doing hybrid, which has always been part of a physical event, which is going to become normal. But I think there's an opportunity that we're learning in this past a year and a half, where there are new, there are new things and there's, it's good, bad and ugly. I mean, there's been some really ugly conferences. Virtual's a bit painful. But there's also been some really nice moments where people are seeing interaction. So is there any learnings that you've taken away from this past year and a half that you can point to that you might want to share with folks watching around how to tap into the magical moments that could be enabled by, you know, the virtual and or bringing people together? >> You know, I myself, I'm a lover of technology, anything new I like to try. So definitely in this pandemic there's been lots of opportunities to try different technologies. What works, what doesn't work. I think, you know, just trying things out helps. I know sometimes people are resistant to change. I myself sometimes find it hard to change my ways in, in certain, you know, I'm used to this too. I want to use it most of the time, but. But anyway, you know, give, things a chance, but most, I think most importantly, is focus on the people. Because technology aside, it is the people you are reaching out to. Right? So again, listen what they have to say. You know? If this doesn't work for them, find out what they prefer, or you know, what, how we can make things better to improve things for them. So I always keep the focus on the people, on the community and, you know, give new technology a chance. And you know sometimes it works out, sometimes it doesn't, but you don't know 'til try and yeah, just- >> Jump in the water is warm. >> Hope for the best. >> Come on in, water is fine. So the meet-ups are happening. >> Right. >> People are getting together where there, where there's a geography opportunity where there's not a lot of scaring, too much scare going on with the meet-ups. So that's cool. What, what is the current AnsibleFest 2021 key thing that you'd like people to walk away with Carol? Because obviously the momentum is continuing. The world needs to go on. We are seeing hybrid, and then we're going to end up coming out of this soon. What's the, what's the key message this year from the AnsibleFest 2021, from the community. >> That, Ansible is open, Ansible is, you know, open to contributions from anyone. And especially the Ansible Community team is working very hard to make things easy and accessible. So please feel free to visit Ansible.com/community for ways of reaching us. And, you know, use Ansible to automate your stuff, and then use the free time that you have from that to spend more time for your family and friends. >> That's great. Be open. Listen. Now you've got a Steering Committee to steer that ship in the right direction. Congratulations. Thanks for coming on theCUBE and for the update, really appreciate it. Again, props to the community at the Ansible part of Red Hat. You guys do a great job. And again, we'll see you on the other side of the pandemic and thanks for coming in remotely all the way in Finland. >> Thank you so much for having me. Its been my pleasure. Thanks. >> Thank you, Carol. I'm John Furrier for AnsibleFest 2021 coverage. This is theCUBE. Thanks for watching. (bright exit music)

(cheerful music) >> Hello everyone, welcome to theCUBE's coverage of AnsibleFest 2021, with Red Hat. Topic of this power panel is the future of automation, we've got a great lineup of CUBE alumni, Joe Fitzgerald, vice president, general manager of the Red Hat business unit, thanks for coming on, Tom Anderson, vice president, product manager of Red Hat, and Alessandro Perilli, the senior director of product market at Red, all good CUBE alumni. Distinct power panel, Joe we'll start out with you, what have you seen in automation game right now, 'cause it continues to evolve. I mean you can't go to an event, a virtual event, or read anything online without hearing AI automation, automation hybrid, automation hybrid hybrid hybrid hybrid, I mean automation is the top conversation in almost all verticals. What do you see happening right now? >> Yeah, it's sort of amazing, you know? Automation is quite fashionable these days, as you pointed out. Automation's always been on the radar of a lot of enterprises, and I think it was always perceived as sort of like that, an efficiency, a task model thing, that people did. Now automation is, if you believe some of the analysts, it's up to a board room imperative in some cases. So we are seeing with our customers that the level of complexity they're dealing with, particularly exaggerated by what's gone past year and a half in the world, is putting a tremendous amount of pressure, attention and importance on automation. So automation's definitely one of the busiest places to be right now. >> What's the big change this year, though? I mean we love the automation conversation, we had it last year a lot too, as well. What's the change, what's the trend right now that's driving this next level automation conversation with customers? >> Well, I'll ask my colleagues to comment on that in a second, but, the challenges here with automation, is people are constrained now, they can't access facilities as easy as they used to be able to. They still need to go fast, some businesses have had to expand dramatically, and introduce new services to handle all sorts of new scenarios, they've had to deploy things faster. Security, not a week goes by you don't read about something going on regarding security and breaches and hacking and things like that, so they're trying to secure things as fast as possible, right, and deploy critical fixes and patches and things like that. So there's just tremendous amount of activity, that's really been exaggerated by what's gone on over the past year. >> And all of this is being compounded with a nature of increasing complexity, that we're seeing in the architecture, explosion microservices, the adoption en masse of containers, and the adoption of multiple clouds for most customers around the world. So really, the extension of the IT environment, especially for large enterprises, enormous for any team, no matter how big it is, so how scale it is, to really go after and look for all the systems, and then the complexity of the architectures, is enormous within that IT environment. It is impossible to scale the applications and to scale the infrastructure, and not scale the IT operations. And so automation becomes really a way to scale IT operations, rather than just keep repeating the same steps over and over, in an attempt to simplify, or to reduce costs. It's well beyond that at this point. >> That's a great point. Tom, what's your reaction to this, because Alessandro brings up a good point, developers are going faster than ever before. The changes of speed and complexity have gone up, so the demand for the IT and/or security groups, or anyone, to be faster, not weeks, minutes. We're talking about a complete time shift here. >> Yeah, so I talk to a lot of customers, and what I keep hearing again and again from them is kind of two things, which is, a need for skills, and reskilling existing staff. When Alessandro talks about the complexity and the scale, think about all the different new tools, new environments, new platforms that these employees and these associates are being exposed to and expected to be able to handle. So, a real, not a skill shortage, but a stress on the skills of the organization. And then secondly, really, our customers are talking to us about the culture in the environment itself, the culture of collaboration, the culture of automation, and the kind of impact that has in our organization, the way teams are now expected to work together, to share information, to share automation, to push, you know, we talk about shifting left in a lot of things now in IT, automation is now shifting left, pushing automation and access to subsystems, IT subsystems and resources, into the hands of people who traditionally haven't had direct access to those resources. So really kind of shift in skills, and a shift in culture I see. >> Ah, the culture. (indistinct), I want to come back to that culture thing, but I want to ask you specifically on that point, do you think automation users still view automation as just repeating and simplifying processes that they already are doing? You've heard the term, "Done it three times, automate it." Is that definition changing and evolving, what's your thoughts? >> Yeah, IT is really changing, going from the traditional, "I'm a network engineer and I use a command line to update my devices I'm responsible for, the config devices, and then I decide to write a playbook using a really cool product like Ansible to drive automation into my daily tasks." And then it comes up to exposing, again, exposing that subsystem I'm responsible for, whatever it is, storage, network, compute, whatever it is, exposing that op so other people can consume it without me being involved, right? So that's a real change in a mindset, and tooling, and approach, that I'm going to expose that op to a set of workflows, business workflows, that drive automation throughout an organization. So that's a real kind of evolution of automation, (indistinct) first, and that's usually focused mostly on day zero, provisioning of a new service. Now we see a lot more focus, or a lot of additional focus on day two operations. How do I automate my day two operations to make them a lot more efficient, as my scale and complexity grows? How do I take the human element out of operating this on a day to day basis? >> So you're saying basically, if I understand you correctly, the system's architecture view, or mindset, around automation, it moves from "Hey, I'm going to use," and Ansible by the way is great for "Hey, I want to automate something, I'm doing a lot," that's cool. But you're looking at it differently. If I understand you correctly, you're saying the automation has to be a system view, meaning you create the rules of the road so that automation can happen at the front lines of the CICD pipeline. You mentioned shift left, is that the difference, is that kind of what's happening here, that's beyond just doing automation, because you can automate it, so you've done that, this is like the next level, is that what you're getting at? >> It is, and we joke about it a little bit, crushing silos, right? Breaking down silos, and again, I keep talking about culture, it really is important, tools are important and technology's important, but the culture's super important, and trying to think of that thing from a systems mindset, of sort of workflows and orchestration of a business process that touches IT components, and how do I automate that and expose that to that workflow, without a human having to touch it, right? Yet still enforce my security protocols, my performance expectations, my compliance stuff, all of that stuff still needs to be enforced, and that's where repeatable automation comes in, of being able to expose this stuff up into these system-level workflows. >> And then there is another element to this (indistinct), I think it's really important to attach to this, the element of speed. We talk about complexity, we talk about scale, but then there is this emerging third dimension, as I call it, that is the speed. And the speed has a number of different articulation, it's the speed when you're thinking about how quickly you need to deliver the application. If you're in a very competitive environment, think about web scale startups for example, or companies in an emerging market, and then you have the speed in terms of reacting to a cybersecurity attack, which Tom just mentioned. And then you have the third kind of speed I'm thinking about right now, which is the increasing amount of artificial intelligence, so an algorithmic kind of operation that is taking place in the organization. For now it's still very limited, but it's not unthinkable that going forward, the operations will be driven, or at least assisted by artificial intelligence. This speed, just like the scale and the complexity we mentioned before, are impossible to be addressed by a single team, and so automation becomes indispensable. >> Yeah, that's a great point, I want to just double click on that, I mean both Tom and Joe were just talking about system, they used the word system. In a subsystem, if one is going faster than the other, to your point, there's a bottleneck there. So if the IT group or security groups are going to take time to approve things, they're not putting rules to the road together to automate and help developers be faster, because look, it's clear, we've been reporting on this in theCUBE, cloud developers are fast. They're moving really fast with code. And so what happens is, if they're going to shift left, that means they're going to be at the point of coding to set policies on security. So, that's going to put pressure on the other subsystems to go faster, so they have to then expose rules of the road, or I'm just making that up, but policy base, or have some systems thinking. They can't just be the old way of saying "No, slow it down." So this is a cultural thing, I think Joe, you brought up culture, Alessandro, you brought up culture. Is that still there? That speed, fast team here and a slow team here? Is that still around, or people getting faster on both sides? And I'm kind of talking about IT, generally speaking, they tend to be slower than the developers. >> Well, just a couple comments, first of all, you heard silos, you heard complexity, you heard speed, talked about shift left. Let me sort of maybe tie those together, right? What's happened to date is every silo has their own set of tooling, right? And so one silo might move very fast, with a very private set of tools, or network management, or security, or whatever, right? And if you think about it, one of the number one skills gaps right now is for automation people. But if an automation person has to learn 17 different tools, 'cause I'm running on three public clouds, I'm on-premise, edge, and I'm doing things to move network storage, compute, security, all sorts of different systems, the tooling is so complicated, right, that I end up with a bunch of specialists. Which can only do one or two things, because they don't know the other domains and they don't know the skills. One of the things we've seen from our customers, I think this is a fundamental shift in automation, is that what we've done with Ansible in particular is, we actually adopted Ansible because of its simplicity. It's actually human-readable, you don't have to be a hardcore programmer to write automation. So that allows the emergence of citizen creators of automation. There's not like a group in some ivory tower that now can make automation and they do it for the masses. Individuals can now use Ansible to create automation. Going cross-domain, Ansible automation touches networks, security, storage, compute, cloud, edge, Linux, Windows, containers, traditional, ITSM, it touches so many systems, that basically what you have is you have a set of power tooling, in Ansible, that allows you now to share automation across teams, 'cause they speak the same language, right? And that's how you go faster. If every silo is fast, but when you have to go inter-silo you slow down, or have to open a ticket, or have some (indistinct) mismatch, it causes delays, errors, and exposures. >> I think that is a very key point, I mean that delay of opening up tickets, not being responsive, Alessandro, you put up machine learning and AI, I mean if you think about what that could do from an automation standpoint, if you can publish the HIPAA rules for your healthcare, you can just traverse that with a bot, right? I mean this is the new... This just saves so much time, why even open up a ticket? So if you can shift left and do the security, and there's kind of rules there, this is a trend, how do you make that happen, how do you bust the silos, and I guess that's the question I'd love to get everyone to react to, because that implies some sort of horizontally scalable control plane. How does someone do that in an architectural way, that doesn't really kind of, maybe break everything, or make the (indistinct) go into a cultural sideways situation? >> Maybe I can jump in, and grab this one, and then maybe ask Alessandro to weigh in afterwards, but, what we've seen and what you'll see some of the speakers at AnsibleFest this year talk about, from a cultural perspective is bringing teams together across automation guilds, JPMC calls it a community of practice, where they're bringing hundreds and thousands of individuals in the organization together virtually, into these teams that share best practices, and processes and automation that they've created. Secondly, and this is a little bit of a shameless plug for Ansible, which is having a common language, a common automation language across these teams, so that sharing becomes obviously a lot easier when you're using the same language. And then thirdly, what we see a lot now is people treating automation as code. Storing that, and get version managing and version controlling and checking in, checking out, really thinking of automation differently from an individual writing a script, to this being infrastructure or whatever my subsystem is, managed it and automated it as code, and thinking of themselves as people responsible for code. >> These are all great points. I think that on top of all these things, there is an additional element which is change management. You cannot count on technology alone to change something that is purely cultural, as we kept saying during this video right now. So, I believe that a key element to win, to succeed in an automation project, is to couple the technology, great technology, easy to understand, able to become the common language as Tom just said, with an effort in change management that starts from the top. It's something you don't see very often because a technology vendor rarely works with a more consulting firm, but it's definitely an area that I think would be very interesting to explore for our customers. >> That's a great point on the change management, but let me ask you, what do you think it needs to make automation more frictionless for users, what do you see that needs to happen, Alessandro? >> I think there are at least a couple of elements that need to change. The first one is that, the effort that we're seeing right now in the industry, to further democratize the capability to automate has to go one notch further. And by that I mean, implementing cell service provisioning portals and ways for automatically execute an automation workflow that already exists, so that an end user, somebody that works in the line of business, and doesn't understand necessarily what the automation workflow, the script is doing, still able to use it, to consume it when it, she or he needs to use it. This is the first element, and then the second element that is definitely more ambitious, is about the language, about how do I actually write the automation workflow? This is a key problem. It's true that some automation engines and some workflows have done, historically speaking, a better job than others, in simplifying the way we write automation workflows, and definitely this is much simpler than writing code with a programming language, and it's simpler than writing automation compared to a tool that we use 10, 15 years ago. But still, there is a certain amount of complexity, because you need to understand how to write in a way that the automation framework understands, and you need even before that, you need to express what you want to achieve, and in a way that the automation engine understands. So, I'm thinking that going forward we'll start to see artificial intelligence being applied to this problem, in a way that's very similar to what OpenAI Microsoft are doing with Codex, the capability that is a model that allows a person to write in plain English through a comment in code, to translate that comment into actual code, taken from GitHub or through the machine learning process that's been done. I'm really thinking that going forward, we will start to see some effort in the same direction, but applied to automation. What if the AI could assist us, not replace us, in writing the automation workflow so that more people are capable to translating what they want to achieve, in a way that is automatable? >> So you're saying the language, making it easy to program, or write, or create. Being a creator of automation. And then having that be available as code, with other code, so there's kind of this new paradigm of automating the automation. >> In a sense, this is absolutely true, yes. >> In addition to that, John, I think there's another dimension here which is often overlooked, which we do spend a lot of time on. It's one thing to have things like Alessandro mentioned, that are front edge in terms of helping you write code, but you want to know something? In big organizations, a lot of times what we find is, someone's already written the code that you need. You know what the problem is? You don't know about it, you can't find it, you can't share it and you can't collaborate on it, so the best code is something that somebody's already invested the time to write, test, burn in, certify, what if they could share it, and what if people could find it, and then reuse it? Right, everybody's talking about low code, no code, well, reuse is the best, right? Because you've already invested expertise into doing it. So we've spent a lot of time working with our customers based on their feedback, on building the tools necessary for them to share automation, to collaborate on it, certify it, and also to create that supply chain from partners who create integrations and interfaces to their systems, and to be able to share that content through the supply chain out to our customers and have them be able to share automation across very large globally distributed organizations. Very powerful. >> That's a powerful point, I mean reuse, leverage there, is phenomenal. Discovery engine's got to be built. You got to know, I mean someone's got to build a search engine for the code. "Hey code, who's written some code?" But just a whole 'nother mindset, so this brings up my next question for you guys, 'cause this is really, we're teasing out the biggest things coming next in automation. These are all great points, they're all about the future, where will the puck be, let's skate to where the puck will be, but it's computer science and automation that's being democratized and opened up more, so it's, what do you guys think is the biggest thing coming next for automation? >> Joe, you want to go next? >> Sure. Sure. Yeah, I'll take it. So we're getting a glimpse of that with a number of customers right now that we're working with that are doing things around concepts like self-healing infrastructures. Well what the heck is that? Basically, it's tying event systems, and AI, which is looking at what's going on in an environment, and deciding that something is broken, sub-optimal, spending too much, there's some issue that needs to be dealt with. In the old days, it was, that system would stop with opening a ticket, dispatch some people who were either manually or semi-automated go fix their whatever. Now people are connecting these systems and saying "Wait a minute. I've got all this rich data coming through my eventing systems. I can make some sense out of it with AI or machine learning. Then I can drive automation, I just eliminated a whole bunch of people, time, exposure, cost, everything else." So I think that, sort of a ventureman automation is going to be huge. I'm going to argue that every single system in the world that uses AI, the result of that's going to be, I want to go do something, I want to change, optimize my move, secure, stop, start, relocate, how's that going to get done? It's going to get done with automation. >> And what Joe just said is really highly successful in the consumer space. If you think about solutions like If This Then That, or Zapier for example, those are examples of event-driven automation. They've been in the consumer space for a long time, and they are wildly popular to the point that there are dozens of clones and competitors. The enterprise space, it didn't adopt the same approach so far, but we start to see event bridges, and event hubs that can really help with this. And this really connects to the previous point, at this point I'm a broken record, which is about the speed and the complexity. If the environment is so spread out, so complex, and it goes all the way to the edge, and all these events take place at a neck-breaking pace, the only way for you is to tie the automation workflows that you have written, to a trigger, an event that takes place at some point, according to your logic. >> Tom, what are your thoughts? >> Yeah, last but not least on that kind of thread, which is sort of the architectures as we get out to the edge, what does it take to automate things at the edge? We thought there was a big jump from data center to cloud, and now when you start extending that out to the edge, am I going to need a new automation platform to handle those edge devices? Will I need a new language, will I need a new team, or can I connect these things together using a common platform to develop the automate at the edge? And I think that's where we see some of our customers moving now, which is automating those edge environments which have become critical to their business. >> Awesome, I want to ask one final question while I've got you guys here in this power panel, great insights here. Operational complexity was mentioned, skills gap was mentioned earlier, I want to ask you guys about the organizational behavior and dynamic going on with this change. Automation, hybrid, multi-cloud, all happening. When you start getting into speed of application development for the modern app, opensource where things are opening up and things are going to be democratized with automation and code and writing automation, and scaling that, you're going to have a cultural battle that's happening, and we're kind of seeing it play out in real time. DevOps has kind of gone and been successful, and we're seeing cloud-native bring new innovation, people are refactoring their business models with cloud technologies, now the edge is here, so this idea of speed, shifting left, from a developer standpoint, is putting pressure on the old, incumbent systems, like the security group, or the IT group that's still holding onto their ticketing system, and they're slower, they're getting requests, and the developer's like "Okay, go faster, I want this done faster." So we're seeing departments reorganizing. What do you guys see, 'cause Red Hat, you guys have been in there, all these big accounts for the generation of this modern era. What's the cultural dynamics happening, and what can companies do to be successful, to get to the next level? >> So I think for us, John, we certainly see it and we experience it, across thousands of customers, and what we've done as an organization is put together adoption journeys, a consulting engagement for our customers around an automation adoption journey, and that isn't just about the technology, it's all throughout that technology, it's about those cultural things, thinking differently about the way I automate and the way I share, and the way I do these tasks. So it's as much about cultural and process as it is about technology. And our customers are asking us for that help. Red Hat, you have thousands of customers that are using this product, surely you can come and tell us how we can achieve more with automation, how can we break down these silos, how can we move faster, and so we've put together these offerings, both directly as well as with our partners, to try and help these customers kind of get over that cultural hump. >> Awesome. Anyone else want to react to the cultural shift and dynamics and how it can play out in a positive way? >> Yeah, I think that it's a huge issue. We always talk about people, processes, and technology. Well the people issue's a really big deal here. We're seeing customers, huge organizations, with really capable teams building apps and services and infrastructures, saying "Help me think about automation in a new way." The old days, it was "Hey, I'm thinking about it as a cost savings thing." Yeah, there's still cost savings in there. To your point, John, now they're talking about speed, and security, and things like that. How fast, zero day exploits, now it's like zero hour exploits. How fast can I think about securing something? You know, time to heal, time to secure, time to optimize, so people are asking us, "What are the best practices? What is the best way to look at what I've got, my automation deficits," used to have tech deficits, now you got automation deficits, right? "What do I need to do culturally?" It's very similar to what happened with DevOps, right? Getting teams to get together and think about it differently and holistically, that same sort of transition is happening, and we're helping customers do that, 'cause we're talking to a lot of them where you've got the scholars have been through it. >> Awesome. Alessandro, your thoughts on this issue. >> I think that what Tom and Joe just said is going to further aggravate, it's going to happen more and more going forward, and there is a reason for that. And this connects back with the skill problem, that we discussed before. In the last 10 years, I've seen growing demand for developers to become experts in a lot of areas that have nothing to do with development, code development. They had to become experts in cloud infrastructures, they had to become experts in security because, you've probably heard this many times, security's everybody's responsibility. Now they've been asked to become experts in artificial intelligence, transforming their title into something like ML engineer. The amount of skills and disciplines that they need to master, alone, by themself, would require a lifetime of work. And we're asking human beings to get better and better at all of these things, and all of the best practice. It's absolutely impossible. And so the only way for them, yeah, five jobs in one, six jobs in one, right? Probably for the same seller, and the only way that these people can execute the best practice, enforce the best practice, if the best practices are encoded in automation workflow, not necessarily written by them, but by somebody else, and execute them at the right time, the right context, and for the right reason. >> It's like the five tool player in baseball, you got to do five different things, I mean this is, you got to do AI, you got to do machine learning, you got to have access to all the data, you got to do all these different things. This is the future of automation, and automation's critical. I've never heard that term, automation deficit or automation debt, we used to talk about tech debt, but I think automation is so important because the only way to go fast is to have automation, kind of at the center of it. This is a huge, huge topic. Thank you very much for coming on, power panel on the future of automation, Joe, Tom, Alessandro from Red Hat, thanks for coming on, everyone, really appreciate the insight, great conversation. >> Thanks, John. >> 'Kay, this is theCUBE's coverage of AnsibleFest 2021 virtual. This is theCUBE, I'm John Furrier, your host, thanks for watching. (calm music)