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

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

(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)

(upbeat music) >> Hello, I'm John Furrier with theCUBE, here in Palo Alto, California. We're part of the ongoing coverage of AnsibleFest 2021, virtual this year like all years. We're covering it virtually. In-person events soon will be back, and we'll be back in person when that happens this year. Year two of virtual coverage of AnsibleFest 2021. And just like last year, a great lineup of virtual interviews. We have the ability to pull people in remotely, which gives us more access to more people. So we've got a lot more content, a lot more content and stories to report. The big theme this year coming up is going to be automation, automation, automation, and hybrid environments. So automation, hybrid, and now the emergence of the democratization of AI. You're seeing AI being driven by automation. You're seeing automation going from repeating tasks that need to be automated to being programmatic in cloud-development life cycle. So a lot of changes going on. We had some great guests. Tom Anderson, Richard Henshall has been there. We had a lot of community updates. Carol Chen was on. Joe Fitzgerald, and Tom Anderson, and Alessandra Perelli were on. Great lineup there. The thought leadership there was all about how Red Hat Ansible are bringing the next generation automation platform to the community and making it easy for new people to come in. We heard from Kentrell, IBM, Scott Kinane, and Anand Gopalakrishnan, and Lisa Chavez. So great, great content there. Again, more and more community. The constant theme of open source and community continues to reign true for Red Hat AnsibleFest 2021. And the big surprise to me was they had great customer attraction, okay? Sapphire Health came on talking about migration. Enterprise customers are taking automation mainstream, powering programmatic, cloud-native solutions. So you're starting to see evidence, not just the hardcore automation folks that Ansible's been servicing in the enterprise and the developer community, but mainstream developers in the enterprises are adopting Ansible. This is the real deal . We heard from the chief architect of Ansible, Matthew Jones, going into great detail on how the enablement of the system is going to be creating more headroom for future growth. All in all, great content from theCUBE. Great guests as usual. And of course, check out Twitter and LinkedIn and all the social networks for CUBE highlights, and of course content and the guests themselves are awesome. So take a listen, and watch those videos, and enjoy the show. (upbeat music playing)

(bright upbeat music) >> Narrator: From around the globe, it's theCUBE! With digital coverage of AnsibleFest 2020 brought to you by Red Hat. >> Welcome back to the cube virtual coverage of AnsibleFest 2020. Virtual, not face to face this year, obviously because of COVID, and all events are going virtual. This is theCUBE virtual. I'm excited to have on CUBE, alumni Mandy Whaley, who's the Senior Director of DevNet & Cisco Certifications. Mandy, great to see you, >> Thank you. >> virtually. >> Great to see you too. It's exciting to be here with theCUBE again, and especially here at AnsibleFest. >> Last time we saw each other at a physical event was Barcelona in January, as the world was taking a turn. I see a lot of people online, learning has been great. What would DevOpsSec things going on, we'll get to that in a second, but I want to first talk about you and your role in Cisco and Red Hat Ansible. You're a trusted adviser. What are customers experiencing? And what are their expectations around automation? The big theme of this conference? >> Absolutely. So, in terms of the community that I work with at Cisco, it's our DevNet, and our learning community, all of our Cisco certified engineers, as well as our DevNet developer audience. And so, automation is at the core of what they're working on. And we've seen even the move to more work from home, all the virtual things that we're dealing with, that's even more emphasis on companies needing to do automation and needing to have the skills to build that within their teams. So we're really seeing that everyone has expectations around platforms being able to have open API's, integrate with tool sets, having choice in how they integrate things into their different workflows that they may already be using. And then we're seeing a big demand for people wanting to skill up and learn about automation, learn about Ansible, learn about Python. Our new DevNet certifications, they actually cover Cisco platforms as well as industry standard topics like Python and Ansible. And we've seen really great feedback from the community around loving that combination of getting to work really deeply with our Cisco technologies, as well as learning things like Ansible and Python. We had a special special challenge when we launched the DevNet Certifications, for the first 500 people to earn that certification. And we were really excited to see the community achieve that within the first 16 days. So I just think that shows how important automation is to our community right now. >> What do you hear from customers around this certification opportunity around Ansible and Python? Can you give an example? >> So what we're hearing from companies and customers and individual developers is that they're having to deal with more scale, they are seeing more opportunity to handle consistent policy to make sure configurations are consistent. All of these things are really important right now with the scale they're trying to handle. And so, they're looking for ways that they can quickly add these skills to their tool set. And since we are working from home, not traveling as much, everyone's schedule is a little bit different. There is extra opportunity for teams to dig in and do some learning. So, leaders, IT leaders are looking for how do they work with their teams to go after these skills and add them into their way that they approach problems, the way solve problems. And then individuals are looking for how they add them to open up new job roles and new opportunities for themselves. >> Well, I want to give you a shout out and props and kudos for the work you guys have done over at DevNet. We've watched the evolution. Obviously you guys have transformed the learning but also, the API enabled products and economy that Cisco is driving with the SaaS. This is consistent with Ansible's success in the cloud and on premise with private cloud. Again, Cloud, Ops, Sec, everything's kind of happening. Tell us the importance of automation within the Cisco products and how Ansible fits in. >> Absolutely. So, like I said earlier, having this open API's really, across the whole Cisco portfolio, and up and down the stack at the device level, at the controller level. That's part of our strategy. It's important to our customers, it's important to Cisco. We actually have a developer event, DevNet Create, coming up. And, Chuck Robbins, will be talking about some of that importance of developers and automation in the Cisco strategy at DevNet Create. So maybe you can tune in and see some of that as well. We have been working with Ansible since early on in terms of how we bring Cisco technologies together with Ansible. And as Ansible moved to the new collections, we stepped into that very early, we knew it was important to have a seamless transition around that for our community. And that's been a big part of our work this year in terms of how we've been working with Ansible and getting ready for the the new collection structure. >> The people who are watching and know theCUBE know that, or maybe new to theCUBE and our work, know that I've been a cheerleader for Cloud Native, but now it's actually happening, Mandy, we've been cheering it on and saying it's going to happen. Cloud Native and the modern app focus, again, this is some of the narrative on the inside, the industry is now mainstream. This is really a big deal because it's now DevOps and sec, so all that's happening mainstream, the rise of Kubernetes. Everything is on the front burner when it comes to Cloud Native. So I got to ask you, how do the developers here at AnsibleFest get to learn more about Cisco? Because now you're bringing everything together. The automation up and down the stack from modern apps down to the plumbing network's certainly super important from edge, 5G's right around the corner. This is a business enterprise opportunity. How can developers at AnsibleFest learn more about Cisco? >> Fantastic, yes. The one place to learn about all of our Cisco platforms, and like you said, how all these things, Cloud Native, DevOps, DevsSecOps, how all of these things are coming together. You can learn about it at developer.cisco.com. It's where all of our developer resources are, it's where you can find, if you're wanting to get started with Cisco products and Ansible. We have learning labs, engineer to engineer tutorials, videos, sample code, all kinds of the resources to help people get started on that journey. And the other thing we're really seeing is, like you said, this coming together and the real move in enterprises towards DevOps is creating all of these new job roles around DevSecOps, and network automation engineer, and web scale developer. And one of the things we're seeing is people are needing to add skills to their current skill set, mix and match, bringing hardware and software together, cloud and networking skills and development skills to really meet the need for these new job roles, which is being driven by the business demands that we're facing. And that's one of the things that we're working really hard on in the DevNet and Cisco community right now. >> Can't go wrong by continuing your career at Cisco and certainly configuration management software comes together as awesome. So, thanks for sharing that. One of the topics at AnsibleFest 2020 virtual this year is the theme is kind of three things, as we heard on some of the interviews, collections, collections collections. This notion of Ansible (Mandy laughs) automation platform has a numerous Cisco certified collections. Can you share some insight and anecdotes from your community on, from the DevNet users on what they're dealing with day to day around automation and how these collections and the certified collections fits in? >> Yeah, absolutely. So, part of my team has been working with our community, with Ansible, to bring the Cisco Ansible collections together. And it's been a big part of our work throughout the year. And we've seen tremendous use by the community. So we've been following the downloads of people downloading connections and using them is growing rapidly. We are really excited to see the use of the community and then the community interest support. And then we're doing our best to make sure that we have playbooks in our DevNet code exchange, so people can go in and find them. That we're helping people understand collections and how all that fits together in the current Ansible structure. And we've just seen tremendous interesting response from the community on that. >> How does this tie into security automation? Another theme that comes up, you talk about network, you got cloud, you got security, intrusion, detection, prevention, these are all useful things to DevNet users, how does that all fit in? >> Security is one of the areas that I'm consistently hearing about from our community and customers. I think people are really looking for how they can deal with increased scale, how they can increase the scale that they're able to deal with and keep it secure. We're seeing people want to take quick action, when a malicious activity occurs, or even something like ensuring that policy is consistent across a range of security endpoints. And these are all places where automation can really help out, and help teams manage the scale that they're having to deal with. So, one of the things we've been working with is showing some learning labs on DevNet, that combine using Ansible with our security products to help people tackle some of those use cases. We have an area called automation exchange. And it's all about these automation use cases, and giving you the sample code to get started on tackling some of these harder use cases. That's where we have seen a lot of interest around security. >> On a broader scale, could you tell us where you see NetOps going? I mean, it's a big theme, Susie Wee, April, yourself. We've all chatted about this in the past NetOps, or DevOps for networking ops for basically DevOps for networking, basically. >> Yes. >> Where's this... Where's it going in the future? Where are we on the progress? Certainly there's been great evolution. How is DevNet evolving to push this mission forward? >> So, one of the things that we talk with customers a lot about when they are moving down this pathway to bringing DevOps to the way that they run their network is we talk about a walk, run, fly progression. And walk is where there, I use cases where maybe you are only doing read-only type things, and you're gathering insight, you're gathering information to help with troubleshooting, you're gathering information that maybe gets packaged up into a ticket that then an engineer takes action on. And this is a great place where a lot of organizations can start. If they are learning these skills, building these practices, they don't have to worry about it, making changes but they get a lot of the benefit of the automation. So, we're recommending that to at least two companies who are getting started, teams that are getting started, as a place to start their automation journey. And then really moving through that progression of next, taking some automated action, all the way to that full DevOps, lifecycle and workflow. And we're seeing companies move through that progression as their teams also move through that progression. >> Just as a side note, one of the things we've been riffing on lately around the Cloud Native, as you know now, it's mainstream as we just talked about, is that the integrations are a big part of it. So, you could have an environment that has a little bit of that, a little bit of this. A lot of integrations because of API's, and also microservices, you get Kubernetes around to tie it on, glue it all together. You got DevNet Create coming up, and you guys always have a great DevNet Zone at your events. It's a real learning environment. Talk of Ansible developers in the community out there and how you guys work together for these classes, because you guys have a lot of learning, is like a cross section of the community that work together, some don't some do. The Cloud Native really enables the integrations to happen quicker. Can you just share what's going on at DevNet Create, and your world? >> Absolutely. So, and it's great because, John, you were at our first DevNet Create years ago when we started it. So it's really exciting. This is our first virtual DevNet Create, that's October 13th. And we had planned it to be an in person event in March when the pandemic hit the US, and so we had to re-plan, and regroup and bring it to a virtual audience this fall. And it's actually been great with our virtual events, we've been able to see how there's many more people who can participate, who can learn who can be a part of that community, because it's not only limited to the people who can be there in person. So we're actually really excited about that virtual part of it. And DevNet Create is the event where we have speakers from all over our community, from companies, from partners, from community groups, and all kinds of technologies, like you said, it's a great place to look at the integrations. So you'll find talks on Ansible, you'll find talks on Kubernetes, you'll find talks on IoT, you'll find talks on mashing up different API's to go after use cases. And it's really about that strength of the community speakers that brings a lot of excellent content into DevNet Create, and we're so thankful for them, and the way that our community likes to, step up and share and help each other. >> Well, yes, we were there for the first one we will still be there with you. But the question that comes up, and I'd like you to just quickly take a minute to clarify the difference between DevNet and DevNet Create, cause there is a nuance here, it's important. Take a minute to explain DevNet and DevNet Create, and the objective of the two. >> Absolutely. So DevNet are DevNet Zone Event, which happen typically in our Cisco lives, they have more of a focus on our more network engineer community who's spanning into programmability, DevOps, moving that direction because it happens within a Cisco live event, normally, the DevNet Zone. DevNet Create is our conference that started to focus on the application developer, the cloud developer, and how they are starting to tackle some of these hybrid use cases. And so DevNet Create is the place where that really comes together. And when, last year, Susie and I are on stage and we really wanted to know kind of what aspects people were bringing to the conference. And we asked the community, how many people are really focused on application development in their day job? That's their main focus. How many people are more on the Ops side? Infrastructure developer, DevOps engineer? And then how many people are really working to bridge that? And it was one third, one third, one third, in terms of the people at Create that year. And that was just really great to see. And to me, I think really shows the community that's building around around DevNet Create. >> And if you look at the trends too, the discussions are about modern applications, and certainly with COVID, people are looking at this and saying, "Hey, it's an opportunity to use this pandemic "and look at the opportunity to be very agile, "and create these modern apps which require programmability, "which require "some instructions away >> That's right. >> "from the complexity, all the way down to the network." I mean, it really gives great vision. >> All the way to the network. Yeah, and even things like, using things with Meraki cameras with using things like our collaboration products, to build those use cases that are really helping out in a lot of the new challenges that we're facing. So that's all what you can find at DevNet Create. It's one of my favorite events because it does cover such a range of topics. >> I'm in my first interview at one of your first event with Todd Nightingale. He is doing the Meraki thing. Now he's running a lot of the big part of the business there. But it really was a great vision. You guys really nailed it. Hats off to you guys. Kudos props. Congratulations and stay safe. And we'll see you at your event. Thanks for joining me. >> Thank you so much, and thanks to AnsibleFest. >> Okay, that's theCUBE virtual coverage. I'm John Furrier, your host with AnsibleFest 2020. Thanks for watching. (bright upbeat music)

(soft music) >> From around the globe, it's theCUBE. Presenting, Accelerating Automation with DevNet, brought to you by Cisco. >> And welcome back everybody, Jeff Frick here with theCUBE. We have our ongoing coverage of the Cisco DevNet event. It's really Accelerating with Automation and Programmability in the new normal. And we know the new normal is definitely continuing to go. We've been doing this since the middle of March and now we're in October. So, we're excited to have our next guest. He's Thomas Scheibe, he is the vice president of product management for data center for Cisco, Thomas, great to see you. >> Hey, good to see you too. >> Yeah. >> Yeah, and truly run it in normal as everybody can see on our background. >> Exactly, so, I mean, I'm curious, we've talked to a lot of people. We talked to a lot of leaders, you know, especially like back in March and April with this light switch moment, which was, you know, no time to prep, and suddenly everybody has to work from home. Teachers got to teach from home. And so you got the kids home, you got the spouse home, everybody's home trying to get on the network and do their zoom calls and their classes. I'm curious from your perspective, you guys are right there on the network, you're right in the infrastructure. What did you hear and see kind of from your customers when suddenly, you know, March 16th hit and everybody had to go home? >> Well, (laughs) good point, hey, I do think we all appreciate the network much more than we used to do before. And then the only other difference is I'm really more on WebEx calls and zoom calls, but, you know, otherwise yes. What I do see actually is that as I said network becomes much more operas as a critical piece. And so before we really talked a lot about agility and flexibility, these days we talk much more about resiliency quite frankly, and what do I need to have in place with respect to network to get my things from left to right. And you know, north to south and east to west, as we see in the data center. >> Right. >> And touches as for most of my customers, a very, very important topic at this point. >> Right, you know, it's amazing to think, you know, had this happened, you know, five years ago, 10 years ago, you know, the ability for so many people in the information industry to be able to actually make that transition relatively seamlessly is actually pretty amazing. I'm sure there was (chuckles) some excitement and some kudos in terms of, you know, it is all based on the network and it is kind of this quiet thing in the background that nobody pays attention to. It's like a ref in the football game until they make a bad play. So, you know, it is pretty fascinating that you and your colleagues have put this infrastructure and that enabled us to really make that move with really no prep, no planning and actually have a whole lot of services delivered into our homes that we're used to getting at the office or are used to getting at school. >> Yeah, and I mean, to your point, I mean, some of us did some planning. We clearly talking about some of these trends and the way I look at this trend as being distributed data centers and having the ability to move your workloads and access for users to wherever you want to be. And so I think that clearly went on for a while. And so, in a sense we prep was our normal we're prepping for. But as I said, resiliency just became so much more important. And, you know, one of the things I actually do a little preview for a blog I put out end of August around resiliency. If you didn't put this in place, you better put it in place. Because I think as we all know, we saw it in March this is like maybe two or three months, we're now in October. And I think this is the new normal for some time being. >> Yeah, I think so. So, let's stick on that theme in terms of trends, right? The other great trend is public cloud and hybrid cloud and multi cloud. There's all types of variants on that theme, you had in that blog post about resiliency in data center cloud networking, data center cloud. You know, some people think, wait, it's kind of an either or I either got my data center or I've got my stuff in the cloud and I've got public cloud. And then as I said, hybrid cloud, you're talking really specifically about enabling both inner data center resiliency within multi data center resiliency within the same enterprise as well as connecting to the cloud. That's probably counterintuitive for some people to think that that's something that Cisco is excited about and supporting. So, I wonder if you can share, you know, kind of how the market is changing, how you guys are reacting and really putting the things in place to deliver customer choice. >> Yeah, no, it's actually, to me, it's really not counterintuitive because in the end, what I'm focusing on and the company is focusing on is what our customers want to do and need to do. And that's really, you know, most people call hybrid cloud or multicloud. In the end, what it is is really the ability to have the flexibility, to move your workloads where you want them to be. And there are different reasons why you want to place them, right? You might've placed them for security reason. You might played some compliance reasons depending on which customer segment you're after. If you're in the United States or in Europe or in Asia, there are a lot of different reasons where you're going to put your syncs. And so I think in the end what an enterprise looks for is that agility, flexibility, and resiliency. And so really what you want to put in place is what we call like a cloud on ramp, right? You need to have an ability to move syncs as needed. But the logic context section which we see in the last couple of months accelerating is really this whole theme around digital transformation, which goes hand in hand than was the requirement on the IT side really do. And IT operations transformation, right? How IT operates. And I think that's really exciting to see, and this was excellent. Well, a lot of my discussions I was customized. What does it actually mean with respect to the IT organization? And what are the operational changes there's a lot of our customers are going through quite frankly accelerated going through? >> Right, and automation is in the title of the event. So, automation is an increasingly important thing, you know, as we know, and we hear all the time, you know, the flows of data, the complexity of the data. Either on the security or the way the network's moving, or as you said, shifting workloads around, based on the dynamic situations, whether that's business security, et cetera. And a software defined networking has been around for a while. How are you seeing kind of this evolution in adding more automation, you know, to more and more processes to free up those you know, kind of limited resources in terms of really skilled people to focus on the things that they should be focused on and not stuff that hopefully you can, you know, get a machine to run with some level of automation. >> Yeah, that's a good point. And I said, TechLine, I have, you know, sometimes when my mind is really going from CloudReady, which is in most of our infrastructure is today to cloud-native. And so let me a little expand on those, right? It's like the CloudReady is basically what we have put in place over the last five to six years, all the infrastructure that our customers have, network infrastructure or the Nexus 9000, they're all CloudReady, right? And what this really means, you have APIs everywhere, right? Whether this is on the box, whether it's on the controller, whether this is on the operations tools, all of these are API enabled. And that's just the foundation for automation, right? You have to have that. Now, the next step really is what do you do with that capability, right? And this is the integration with a lot of automation tools and that's the whole range, right? This is where the IT operation transformation kicks in different customers at different speed, right? Some just, you know, I use these APIs and use normal tools that they have on a network world just to pull information. Some customers go for further saying, "I want to integrate this with some CMDB tools." Some go even further and saying, "This is like the cloud-native (indistinct), "Oh, I want to use, let's say, Red Hat Ansible, or I want to use (indistinct) Terraform and use those things to actually drive how I managed my infrastructure. And so that's really the combination of the automation capability plus the integration was relevant cloud-native enabling tools that really is happening at this point. We're seeing customers accelerating in that motion. Which really then drives us how they run their IT operations. >> Right. >> And so that's a pretty exciting area to see. given as I said, we have the infrastructure in place. There's no need for customers to actually do change something. Most of them have already the infrastructures that can do this. It's just not doing the operational change the process change is to actually get there. >> Right, and it's funny, we recently covered, you know, PagerDuty and they highlight what you just talked about, the cloud-native, which is, you know, all of these applications now are so interdependent on all these different API, you know, pulling data from all these technical applications. So, hey, when they work great, it's terrific. But if there's a problem, you know, there's a whole lot of potential throats to choke out there and find those issues. And it's all being connected via the network. So, you know, it's even more critically important, not only for the application, but for all these little tiny components within the application to deliver, you know, ultimately a customer experience within very small units of time. So, that you don't lose that customer. You complete that transaction. They check out of their shopping cart. You know, all these things that are now created with cloud-native applications that just couldn't really do before. >> Now, you're absolutely right. And this is like, just as I said, I'm actually very excited because it opens up a lot of abilities for our customers. How they want to actually structure the operation, right? One of the nice things around this whole automation plus cloud network tool integration is you actually opened us up not a sole automation training, not just to the network operations personnel, right? You also open it up and can use those for the SecOps person or for the DevOps person or for the CloudOps engineering team, right? Because the way it's structured, the way we built this, it's literally as an API interface and you can now decide, what is your process? Do you want to have a more traditional process, you have to request, a network operation teams executes the request using these tools and then hands it back over. Or do you say, "Hey, maybe some of these security things, "I can hand over the SecOps team and they can "directly call these APIs, right?" Or even one step further, you can have the opportunity that the DevOps or the application team actually says, "Hey, I going to write a whole infrastructure as code "kind of a script or template, and I just execute, right?" And it's really just using what the infrastructure provides. And so that whole range of different user roles in our customer base, what they can do with the automation capability that's available. It's just very, very exciting way because it literally unleashes a lot of flexibility. How they want to structure and how they want to rebuild the IT operations processes. >> That's interesting, you know, 'cause the, you know, the DevOps culture has taken over a lot, right? Obviously changed software programming for the last 20 years. And I think, you know, there's a lot of just kind of the concept of DevOps versus necessarily, you know, the actual things that you do to execute that technique. And I don't think most people would think of, you know, NetworkOps or, NetOps, whatever the equivalent is in the networking world to have kind of a fast changing dynamic kind of point of view versus a stick it in, spec it, stick it in, lock it down. So, I wonder if you can, you can share how, kind of that DevOps attitude point of view, workflow, whatever the right verb is has impacted things at Cisco in the way you guys think about networking and flexibility within the networking world. >> Yeah, literally, absolutely. And again, it's all customer driven, right? It's none of these is really actually, you know, a little bit of credit, maybe some of us where we have a vision, but a lot of it is just customer driven feedback. And yeah, we do have EU Network Operations Teams come to you saying, "Hey, we use Ansible heavily on the compute, "so, we might use this for Alpha Seven. "We want to use the same for networking." And so we made available all these integrations with sobriety as a state, whether these are the switches, whether these are ACI and dc network controller or our multi site orchestration capabilities, all of these has Ansible integration the way to the right. The other one as I mentioned that how she formed Tarco Terraform, we have integrations available and they see the requests for these tools to use that. And so that is the motion we're in for over a year now. And another blog actually is out there we just posted saying, Yeah, all set what you can do. And then a parallel to this, right? Just making the integration available. We also have a very, very heavy focus on definite and enablement and training. And, you know, a little plucking I know probably part of the segment, the whole definite community that Cisco has is very, very vibrant. And the beauty of this is right. If you look at us, whether you're a NetOps person or a DevOps person or a SecOps person, it doesn't really matter. There's a lot of like capability available to just help you get going or go from one level to the next level, right? And there's simple things like sandbox environments where you can, you know, without stress try things out, snippets of code are there, you can do all of these things. And so we do see it's a kind of a push and pull a tremendous amount of interest and a tremendous time people spend to learn. Quite frankly then, that's another side product of the suggestion when people say, "Oh man, and say, okay, online learning is the thing." So, these tools are used very heavily. >> Right. That's awesome 'cause you know, we've had Susie Leon a number of times and I know he and Mandy and the team, right? Really built this DevNet thing. And it really follows along this other theme that we see consistently across other pieces of tech, which is democratization, right? Democratization is the access tool, taking it out of just a mahogany row with, again, a really limited number of people that know how to make it work. And it can make the changes in an opening up to a software defined world where now it's application centric point of view, where the people that are building the apps to go create competitive advantage now don't have to wait for, you know, the one network person to help them out in and out of these environments really interesting. And I wonder if, you know, when you look at what's happened with public cloud and how they kind of changed the buying parameter, how they kind of changed the degree of difficulty to get project started, you know, how you guys have kind of integrated that type of thought process to make it easier for app developers to get their job done. >> Yeah, I mean, again, I typically look at this more from a customer lens, right? It's the transformation process and it always starts as I want agility, I want flexibility and I want resiliency, right? This is where we talk to a business owner what they're looking for. And then that translates into an IT operations process, right? Your strategy needs to map then how you actually do this. And that just drives then what tools do you want to have available to actually enable this, right? And the enablement again is for different roles, right? You need to give sync services to the app developer and the platform team and the security team, right? To your point so the network can act at the same speed. But you also give tools to the network operations teams because they need to adjust then, they have the ability to react to some of these requirements, right? And it's not just automation, I said we focused on that, but there's also to your point, the need, how do I extend between data centers? You know, just for backup and recovery, and how do I extend into public clouds, right? And in the end that's a network connectivity problem, and we have solved as, we have meters available, we have integrations into AWS. We have integrations into Ajua to actually make this very easy from a network perspective to extend your private domains, private networks into which have private networks on these public clouds. So, from an app developer perspective, now it looks like it's on the same network. It's a protective enterprise network. Some of it might sit here, some of it might sit here. But it's really looking the same. And that's really in the end I said what a business looks at, right? They don't necessarily want to say, I need you to have something separate for this deployment or separate for that deployment. What they want is I need you to deploy something. I need to do this resilience. And the resilient way and an agile way gives me the tools. And so that's really where we focused and what we're driving, right? It's that combination of automation consistently, and then definite tools available that we support, but they're all open. They're all standard tools as the ones I mentioned, right? That everybody's using. So, you're not getting into this, "Oh, this is specific to Cisco, right? It's really democratization, I actually liked your term. >> Yeah, it's a great term and it's really interesting, especially with the APIs and the way everything is so tied together. That everyone kind of has to enable this because that's what the customer is demanding. And it is all about the applications and the workloads and where those things are moving, but they don't really want to manage that. They just want to, you know, deliver business benefit to their customers in respond to, you know, competitive threats in the marketplace, et cetera. So, it's really an interesting time for the infrastructure to really support kind of this app first point of view, versus the other way around is kind of what it used to be. And enable this hyper fast development, hyper fast change in the competitive landscape or else you will be left behind. So, super important stuff. >> Yeah, no, I totally agree. And as I said, I mean, it's kind of interesting because we started on the Cisco data center. It's where we started this probably six or seven years ago. When we named the application-centric, clearly a lot of these concepts evolved. But in a sense it is that reversal of the role from the network provides something and you use to, this is what I want to do. And I need a service thinking on the networking side to expose services that can be consumed. And so that clearly is playing out. And as I said, automation is a key foundation that we put in place. And our customers most of our customers at this point are on these products. They have all the capabilities there are. They can literally take advantage. There's really nothing that stops them at this point. >> Well, it's good times for you because I'm sure you've seen all the memes in social media, right? What's driving your digital transformation is the CEO, the CMO or COVID. And we all know the answer to the question. So, I don't think the pace of change is going to slow down anytime soon. So, (indistinct) keeping the network up and enabling us all to get done what we have to get done and all the little magic that happens behind the scenes. >> Yeah, I know, thanks for having me and again, yeah, if you're listening and you're wondering, how do I get started? Cisco definitely is the place to go. It's, you know, fantastic, fantastic environment. And I highly recommend everybody, roll up the sleeves and you know, the best reasons you can have. >> Yeah, and we know once the physical events come back, we've been to DevNet Create a bunch of times, and it's a super vibrant, super excited, really engaged community, sharing lots of information. It's still kind of that early vibe, you know, where everyone is still really enthusiastic and really about learning and sharing information. So, like Susie and the team have really built a great thing and we're happy to continue to cover it and eventually we'll be back face to face. >> Okay, (chuckles) look forward to that as well. >> All right, thanks. He's Thomas and I'm Jeff you're watching continuing coverage of CiscoDevNet Accelerating With Automation and Programmability. Thanks for watching, we'll see you next time. (upbeat music)

live from Atlanta Georgia it's the tube covering ansible fest 2019 brought to you by Red Hat hello everyone welcome to the queue we are broadcasting live here in Atlanta Georgia I'm John force too many men my co-host the cubes coverage of Red Hat ansible Fest this is probably one of the hottest topic areas that we've been seeing in Enterprise tech emerging along with observability automation and observability is the key topics here automation is the theme stew ansible just finished their keynote keynote analysis general availability of their new platform the ansible automation platform is the big news this is a big I mean it seems nuanced for the general tech practitioner out there what's ansible doing why we here we saw the rise of network management turned into observability as the hottest category in the cloud cloud 2.0 companies going public a lot of M&A activity and observability is data-driven automations this other category that is just exploding and growth and change huge impact to all industries and it's coming from the infrastructure scale side where the blocking and tackling of DevOps has been this is the focus of ansible and their show automation for all your analysis of the keynote what's the most important thing going on here yes so John as you said automation is a super hot topic you know I was just at the New Relic show talking about observability last week we've got the Pedro Duty show also going on this week the the automation is so critical we know that IT can't keep up with things if they can't automate it and it's not just replacing some scripting I loved in the keynote they talked about strategically thinking about automation we've been watching the RP a companies talking about automation so there's lots of different automation there's the right way to do it and another thing angle John that we love covering is you know what's going on with open source you were just at the open core summit in San Francisco the Red Hat team very clear open source is not their business model it is they use open source and everything that Red Hat does is a hundred percent open source and that was core and key to what ansible was and how its created this isn't a product pitch here it's a community you know it's John this is the six most active you know repository in github so out of over a hundred million repositories out there the six most active so that tells you that this is being used by the community it's not a couple of companies using this but it's a broad ecosystem we hear Microsoft and Cisco f5 lots of companies that are contributing as well as just all of the end users we of JPMorgan in the keynote this morning so a lot of participation there but you know it is building out that suite with the platform that you talked about and we're gonna spend a lot of time in the next few days understanding this maturation and growth yeah the automation platform that they announced that's the big news the general availability of their automation platform and stew the word they're using here is scale okay and this is something that you brought up to open core summit which I attended last week was the inaugural conference a lot of controversy and this is a generational shift we are seeing in the midst of our own eyes right in front of us on the ground floor of a shift in open source community how the platform of open source is evolving what Amazon now azure and Google and the others are doing is they're showing that scale has changed the game in how open-source is going to not only grow and evolve but shape application developers and the reason why ansible is so important right now in this conference is that we all know that when you stand up stuff infrastructure you've got to configure the hell out of it DevOps has always been infrastructure is code and as more stuff gets scaled up as more stuff gets provision as more stuff gets built and created the management and the controlling of the configurations this has been a real hot spot this has been an opportunity and a problem so you know everyone who's here they're they're active because you know what this is a major pain point this is a problem area that's an opportunity to take what is a blocking and tackling operational role configurating standing up infrastructure enabling applications and making it a competitive advantage this is why the game is changing starting to see platforms not tools your analysis are they positioned was this keynote successful John and I really liked rut Robin Bergeron came out and talked about the key principles of what antal is done its simplicity its modularity and it's learning from open source this project was only started in 2012 so one of the things I always look at is in the old days you wanted you know to have that experience there's no compression algorithm for experience today if I could start from day one today and build with the latest tools you know heavily using DevOps understanding all of the experience that's happened in open source we can move forward so from 2012 to 2015 Red Hat you know acquired ansible to today in 2019 they're making huge growth and helping companies really leverage and mature their IT processes and move towards you know true business innovation with leveraging automation dude this is not and again this is not for the faint of heart either again these are Rockstar DevOps infrastructure folks who are evolving in taking either network and or infrastructure development to enable and software abstraction layer for applications and this not it's not a joke either I mean got some big names up on stage of just one tweet I want to call out and get your reaction to JP Morgan on his presentation the exact there he was tweet came out from Christopher Festa 500 developers are working to automate business processes leading to among other benefits ninety-eight percent improvement in recovery times what used to take six to eight hours to recover now takes two to five minutes Christopher Festa student so John that's what we want is how can we take these things that took you know hours and I had to go through this ticketing process and make that change what I loved of what Chris from JP Morgan said is he brought us inside he said look to make this change it took us a year of sorting through the security the cyber the the control processes we understand there's not just you know oh hey let's sprinkle a little DevOps on everything and it's wonderful we need to get you know buy-in from the team it you know and it can spread between groups and you know change that culture it's something that you know we've tracked in Red Hat for years and all of these environments this something that does require commitment because it's not just John taking oh I scripted something and and and that's good we need to be able to really look at these changes because automation if we just automate a bad process that's not gonna help our business we really need to make sure we understand what we're automating the business value and and what is going are going to be the ramification to what we're doing well one of the things I want to share with folks watching is some research that we did at Silk'n angle the cube and wiki bond it's part of our cube insights do I know you were part of this we talked to a bunch of practitioners and customers and dozens of our of our community members and we found that observability we've just pointed out has been you know explosive category that automation has been identified and we're putting a stake in the ground right here in the cube as one of the next big sectors that will rise up as a small little white space will become a massive market automation you watch that cloud 2.0 sector called automation why the reasoning was this and here's the results of our of our survey automation is quickly becoming a critical foundational element of the network as enterprises focus on multi cloud network being infrastructure servers and storage a multi cloud rapid application development and deployment software-defined everything's happening pretty much we've been covering that on the cube and most enterprises are just crap lling with this concept and see opportunities the benefits that people see in automation as we've discovered still in the following one focused on focused efforts for better results efficiency security is a top driver on all these things because you got to have security built into the software and then automation is creating job satisfaction for these guys I mean they've been doing this is mundane tasks being automated way so people are happier so job satisfaction and finally this is an opportunity to rescale do these are the key bullet points that we found in talking to our serve our community your reaction to those those results yeah John I love that we know ultimately when we want to be able to provide not only better value to my ultimate end user but I need to look internal as you said John you know how can i you know retool some of my sales force and get them engaged and if you want to hire the Millennials they want a bit just and not be doing the drudgery they want to do something where they feel that they are making a difference and you know you laid out a lot of good reasons why it would help and why people would want to get involved John you know the government I've talked to a number of government agencies when they talk about you know we changed that 40-year old process and now we're doing things faster and better and that means I can really hire that next generation of workforce because otherwise I wouldn't be able to hire them to just do things the old way this is about cloud 2 point and this is about modernization and you mention open source open core summit that I think is a tell sign that open source is changing the communities are changing this is gonna be a massive wave again we've been chronicling this cloud 2 point of the week we coined that term we're trying to identify those key points obviously observability automation but look at the end of the day you got to have a focused effort to make the job go better you heard JP Morgan pointing out minutes versus hours this is the benefits of infrastructure as code in the end of the day employee satisfaction the people that you want to hire to re-skill that can be redeployed into new roles analytics math quantitative analysis versus the mundane tasks automation is going to impact all aspects of the stack so final questions do what are you expecting for the next two days we're gonna be here for two days what do you expect to hear from our guests yeah so John one of the things I'm going to really look at is as you mentioned infrastructure is that where this all started so you know how do I easy to play a VM you know ansible is there you know VMware I've already talked to a number of people in the virtualization community they love and embrace ansible we saw Microsoft up on stage loving embrace it as we move towards micro service architectures containerization and all of these cloud native deployments you know how is ansible in this community doing where the stumbling blocks to be honest from what I hear John coming into this anta Buhl's been doing well Red Hat has helped them grow even more and the expectation is that IBM will help proliferate this in even further the traditional competitors to ansible you think about the chef's in puppet to the world have been struggling with that cloud native world John I know I see ansible when I go to the cloud shows and I hear customers talking about it so ansible seems to be making that transition towards cloud native well but other threats in the cloud native world you know if I've said you know that when I when I go to the server lists you know conference I I don't I have not yet heard you know where this fits into the environment so we always know that that next generation and technology you know how will you know this automation move forward as Red Hat starts to get much more proliferating into major enterprises with IBM which will take their extend their lead even further in the enterprise it's an opportunity for ansible and the community angle is interesting I saw our tweets don't get your community your angle real quick on this I saw a tweet from NetApp their tagline at their booth is simplify automate and orchestrate sounds like they're leading into the kubernetes world containers you got to start thinking about software abstractions and this is the st. the you know provisioning hardware anymore whole new ballgame your assessment of an Sable's community presence mentioned I was a tweet from Red Hat I mean NetApp what's your take on the community angle here John it's all about community we the github stats speak for themselves this is very much a community invent you know kudos to the team here a lot on the diversity inclusion effort so really pushing those things forward John something we always notice at the tech shows the ratio of you know gender is way to more diverse at an event like this we know we see it in the developer communities that there was more diversity in there so by the way when they took over this hotel all of the bathrooms are I believe it's you know it's gender-neutral so you can use whatever bathroom yeah you know you you want there let's make sure I'm using the right pronoun when I'm going saying a lot of people Stu thanks for commentary keynote analysis I'm John first dude minimun breaking down why we are here why ansible why is automation important we believe automation will be a killer category we want to see a lot of growth here and again the impact is with machine learning and AI this is where it all starts automating the data the technology and the configuration is going to empower the next generation modern enterprise more live coverage from ansible fests after this short break