(upbeat electronic music) >> Hello, welcome back to the Red Hat Summit, 2021 virtual coverage. I'm John Ferez, theCUBE coverage. I'm in Palo Alto with the remote interviews for our virtual conference here. We've got two great guests, CUBE alumnis, Tom Anderson, VP of Ansible Automation Platform, and Robin Bergeron, who's the Senior Manager, Ansible Community, community architect and all the great things involved. Robin, great to see you. Tom, thanks for coming back on Red Hat Summit, here, virtual. Good to see you. >> Thanks for having us. >> So since last summit, what's the updates on the Ansible Community and the Automation Platform? Tom, we'll start with you. Automation Platform, what's the big updates? >> Yeah. So since last Summit a lot has happened in Ansible land, if you will. So last time, I remember talking to you about content collections. Packing distribution format for into the sports. So we put a lot of effort into bringing all the Ansible content collections really, as well as the commercial users. And we launched last year a program certified content, working with our partners, including partners to certify the content collections that they create. Co-certify them, where we work together to make sure that the developed against, and tested against a Proctor spec, so that both of us can provide them to our customer bases with the confidence that they're going to be working and performing properly, and that we at Red Hat, and our partnership, co-support those out in our customer's production parts. That was a big deal. The other thing that we announced, late last fall, was the private automation hub. And that's the idea where our customers, obviously appreciate the idea of being able to go to Ansible galaxy or to the Ansible automation opt, to go and grab these content collections, these integrations, and bring them down in their environment. They wanted a way, they wanted a methodology, or a repository, where they can curate content from different sources, and then the manager across their environment, the automation across the environment. Kind of leaning into a little bit of automation content as code, if you will. And so we launched the automation hub, the private automation hub, where that sits in our customer's infrastructure; whether that's in the cloud, or on premise, or both, and allows them to grab content from galaxy, from the Ansible automation hub, the Ansible, automation hub on call.red hat.com, as well as their internally developed content, and be able to manage and provide that across their organization, governed by a set policies. So lots of stuff that's going on. Really advanced considering the amount of content that we provide. The amount of collections that we provide. Have certified that for our customers. And have the ability to curate and manage that content across the teams. >> I want to do a drill down on some of the unification of teams, which is a big message as well, as operating at scale, cause that's a super value proposition you guys have. And I want to get into that, but Robin, I want to come back to you on the community. So much has gone on. We're now into the pandemic for almost a year and a half now. It's been a productivity boom. Developers have been working at home for a long time, so it's not a new workflow for them, but you've seen a lot more productivity. What it's changed in the community since last summit, again, virtual to virtual again, between the windows here, event windows. You guys have a lot going on. What's new in the community? Gives us an update. >> Yeah, well, I mean, if we go back to summit, you know, this time-ish, you know, last year, we were wrapping up, more or less, the, it was, you know, we used to have everything you would install Ansible. You would get all the modules. You had everything, you know. It was all all altogether, which, you know, it was great for new users, who don't want to have to figure things out. It helps them to really get up and started running quickly. And, but, you know, from a community perspective, trying to manage that level of complexity turned out to be pretty hard. So the move to collections was actually great for, you know, not just, you know, for about user perspective, but also from a community perspective. And we came out with the Ansible 2-10. That was last fall, I believe. And that was the first real release of Ansible where we had, you know, collections were fully instantiated. We, you know, they were available on galaxy, but you could also get them as part of the Ansible community distribution. Fast forward to now, you know, we just had the Ansible 3.0 release, here in February, and we're looking to Ansible 4.0 here in early May. So, you know, there's been a lot of activity. A lot has improved, honestly, as a result of the changes that we've made. It's made it a lot easier for contributors to get in with a smaller group, that's more of their size and, you know, be able to get started and identify, you know, who are their interested peers in the community. So it's been a boom for us, honestly. You know, the pandemic otherwise is, you know, I think taught all of us, you know, certainly you, John, about the amazing things that we can do virtually. So we've had a lot of our meetups pivot to being virtual meetups, and things like that. And it's been great to see how easily the community has been able to pivot around, you know, this sort of event. I hope that we don't have to just keep practicing it for forever, but in the meantime, you know, it's enabled us to continue to get things done. Thank goodness to every video platform on Earth. >> Yeah. Well, we appreciate it. We're going to come back and talk more about that in the future; the best practice, what we all learned, and stories, but I think I want to come back to you on the persona side of Ansible, because one of the things we talked about last time that seems to be gaining a lot of traction, is that multiple personas. So I want to just hold on to that. We'll come back. Tom, back to you. We're at Red Hat summit. You guys have Ansible Fest, which is your own event that you guys drilled down on this. So users watching can know this your own community, but now we're part of Red Hat, part of IBM, which IBM Thinks, also happening soon as well. Red Hat summit still is unique event. How is Ansible fitting into the big picture? Because the value proposition of unifying teams is really consistent now with Red Hat's overall arching thing; which is operating at scale, open shift, Robin just mentioned. Where's the automation platform going this year? What's the story here at Red Hat summit for the automation platform? >> Yeah, no, that's a great question . We've seen so, we got time, just a little bit of the pandemic, and how it has accelerated some existing trends that we already saw. And one of those is really around the democratization of the application to work routines. More people delivering infrastructure and applications, independent of each other. Which is great. Faster and more agile, all those other good words that apply to that. But what that does bring up is the opportunity for patient work. Replication of effort. Not reusing necessarily things that are in existence already that other teams may have. They'd be not complying with all of the policies, if you will, the configuration and clients' policies. And so it's really kind of brought Ansible out into focus even more here. Now, because of the kind of common back lane that Ansible provides; a common language and common automation backplane across these different teams, and across these different personas. The great thing about what we supply for these different personas, whether it's outpatient developers, infrastructure honors, network engineers, SecOps teams, GetOps teams. There's so many of these obstacles out there, who now all want independent access to infrastructure, and deploying infrastructure. And Ansible has the kind of leverage that each of those communities, whether it's APIs or CLIs, or event based automation, or web hooks, et cetera, et cetera, you know? Service catalogs, utilize all of those interfaces, if you will, or modalities are accessible in Ansible automations. So it's really allowed us to be this sort of connective tissue, or glue, across these different silos or manes of the organization. Timing it opens specifically, one of the things that we talked about last fall, at our Ansible Fest, was our integration between the Ansible automation platform, our advanced cluster management product, and our OpenShift platform, that allows native applications, running on OpenShift, be able to talk to a Ansible automation operator that's running on that same platform, to do things off platform for their customers are already using Ansible. So connecting their cloud native platforms with our existing systems and infrastructures. Systems of records, network systems, ticketing systems, you name it. So all of those sorts of integrations, Ansible's become the connected glue across all of these different environments. Tying traditional IT, cloud IT, cloud native, you name it. So it's really been fun, and it's been an exciting time for us inside the portfolio and out. >> That's a great point. Connective tissue is a great way to describe some of these platform benefits, cause you guys have been on this platform for really long time. And the benefits are kind of being seen in the market, certainly as people have to move faster with the agility. Robin, I want to come back to you because he brought up this idea of personas. I mean, we all know DevOps infrastructure has code; it's been our religion for over a decade or more, but now the word DevSecOps is more prevalent in all the conversations. The security's now weaved in here. How are you seeing that play out in the community? And then, Tom, if you can give some color commentary too, on the automation platform, how security fits in? So DevOps, everything's being operationalized at scale, we get that. That's one of the value propositions you have, but DevSecOps has a persona. More people want more sec. Dev is great, more ops and standardization, more developers, agile standards, and then security. DevSecOps. What's your? >> I thought it was DevNetSecOps? (man chuckling) >> Okay. I've forgot net. Put net in there. Well, networks abstracted away, you know, as we say. >> Yeah! Well, you know, from my perspective, you know, they're people in their jobs all over the places, right? Like, they, you know, the more they can feel like they're efficient, and doing great stuff at their work, like, they're happy to bring as many people into the fold as possible. Right? And you know, normally, security's always been this, you know, it's sort of like networking, right? It's always been this sort of isolated, this special group over here, that's the traditional, you know, one of the traditional IT bottlenecks that causes us to not be able to get anything done. But, you know, on a community level, we see folks who are interested in security, you know, all the time. I know we've certainly done quite a bit of work with the some folks at IBM around one of their products; which I assume Tom will get more into here in just a moment. But from, you know, community perspective, I mean, we've seen people who've been writing, you know, playbooks and roles and, you know, now collections for, you know, all of the traditional government testing, you know, is, you know, missed standards, all of that kind of stuff. And, you know, it's one of those, it's part of network effects. And it's a great place for actually automation hub. I think, you know, for folks who were on prem or, you know, any of our customers are really going to start to see lots of value. How it will be able to connect folks inside the organization, you know, organically through just the place where I'm doing my Ansible things, allows them to find each other, really. And build those, you know, take it from being silos of automation everywhere into a really sort of networked, you know, internal network of Ansible friends and Ansible power users that, you know, can work together and collaborate, you know, just the same way that we do in open source. >> Yeah. And Tom, so IT modernization requires security. What's your take on this? Because you know, you got cluster, a lot of cluster, advanced cluster management issues. You got to deal with the modern apps that are coming. IT's got to evolve. What's your take on all this? >> Yeah. Not only does IT have to evolve, but it's the integration of IT into the rest of the environment. To be able to respond. So, one of the areas that we put a lot of effort into advancement of curating and solutions around security automation. And we've talked about that in the past, the idea of connecting SecOps teams that are doing intrusion detection, or threat hunting, and then responding in an automated way to those threat protections. Right? So connect SecOps with my team; which has traditionally been siloed operations and silo teams. And now with this curated, Ansible security automation solution that we brought to market, with our partners, that connects those two teams in a seamless sort of way. And we've got a lot of work with our friends at IBM, around this area because they are digging that security, their facility, the products in their portfolio. So we've done a lot of work with them. We've done a lot of work with lots of our partners; whether it's cyber or Microsoft, or whoever. Those areas are traditionally, Ansible's done a great job on sort of compliance around configuration enforcement, right? Setting configuration. Now we moved into connecting set-mops with IT. Security automation, now of our acquisition of SecOps, along with our advanced cluster management integration with Ansible, we're starting to say, what are the things inside that DevSecOps workflow that may require integration or automation, or package automation with other parts of the environment? So bringing all of those pieces together, as we move forward, which is really exciting for us. >> Okay, I got to ask you guys the number one question that I get all the time, and I see in the marketplace, kind of a combo question, is, how do I accelerate the automation of my cloud native development, with my traditional infrastructure? Because as people put in green, if one of the cloud projects, whether it's, and then integrating with the cloud on premises with the traditional infrastructure, how do I accelerate those two environments? How do I automate, accelerate the automation? >> It's a great short for us, as what we were talking about last Ansible Fest. We are bringing together with our advanced, cluster management product, ownership platform. Ansible is just been widespread use in all of the automation of both traditional, and cloud native, infrastructures. Whether it's cloud infrastructure, on-premise storage, compute network, you name it. Customers are using Ansible, using Ansible to do all kinds of pieces of infrastructure. Being able to tie that to their new, cloud native initiatives, without having to redo all of that work that they've already done, you integrate that, this thing, infrastructure automation, with their cloud native stuff, it accelerates substantially the, what I call, the operationalization of their cloud native platforms, with their existing IT infrastructure in the existing, IT ecosystem. I believe that that's what the Ansible automation platform plays a key role in connecting those pieces together, without having to redo all that work, that's been done and invested. >> Robin, what's your take on this? This is what people are working on in the trenches. They realize cloud benefits. They've got some cloud native action, and also then they got on the traditional environment, and they've got to get them connected and automated. >> Yeah, absolutely. I mean, you know, the beauty of Ansible, you know, from a end user perspective is, you know, how easy it is to learn and how easy the languages to learn. And I think, you know, that portability, you know, it doesn't matter like, how much of a rocket scientist you are, you know? Everybody appreciates simplicity. Everybody appreciates being able to hand something simple to somebody else, and letting other people get done, and having it, be more or less, it's not quite English, but it's definitely, you know, Ansible's quite readable. Right? And you know, when we looked at, when we started to work on all the Ansible operators, you know, one of that, one of the main pieces there was making sure that that simplicity that we have in Ansible, is brought over directly into the operator. So, just because it's cloud native doesn't mean you suddenly have to learn, you know, a whole set of new languages. Ansible's just as portable there, as it is to any other part of the, your IT organization, infrastructure, whatever it is that you have going on. >> Well, there's a lot of action going on here at Red Hat summit, 2021. Things I wanted to bring up, in context of the show, is the success, and the importance, of you guys having Ansible collections. This has come up multiple times, as we talked about those personas, and you've got these new contributors. You've got people contributing content, as open-source continues to grow and be phenomenal. Value proposition. Touch on this concept of collections. What's the updates? Why is it important? Why should folks pay attention to it, and continue to innovate with collections? >> From a commercial perspective, or from a product perspective, collections have made it a lot easier for contributors to create, and deploy, and distribute content. As Robin's mentioned earlier, previous iterations of Ansible have all of that integration. All of those collections, all within one big group. We call the "batteries included" back in the time. Back in the day, right? That that meant that contributors deployed content with the base, Ansible distribution, they had to wait for the next version of Ansible to come out. That's when that content would get redistributed with the next version of Ansible. By de-coupling, on platform, or engine, putting that into collections, individual elements of related integrations, those can move that their own pace. So users, new customers, can get the content they need, based their contributors like and keep up with. So, customers will have to wait for the next version of the shipping products and get a new version of the new integration they really like now. So again, de-coupling those things, it allows them to move at different paces. The engine, or the platform itself, needs to be stable, performance secure. It's going to move at a certain lifecycle. The content itself, all the different content, hub, and network providers, platforms, all of those things can now move at their own pace. Each of those have their own life cycle. Allows us to get more functionality in our customers hands a lot quicker. And then launching our certified program, partners, when we support that content, certified support that content, helps meet the values that we bring to our customers with this subscription. It's that ecosystem of partners that we work with, who certified and support the stuff that we ship and support with our customers. Benefits both from the accessing the technology, as well as to the access to the value added in terms of integration, testing and support. >> Robin, what's your take on the community? I see custom automation with connect here. A lot of action going on with collections. >> Yeah. Absolutely. You know, it's been interesting, you know? Tom just mentioned the, you know, how everything, previously, all had to be released all at once. Right? And if you think about, you know, sure I have Ansible installed, but you know, how often do I have to, you know, just even as a regular, I'm not a system administrator these days, type person, like how often do I have to, you know, click that button to update, you know, my Mac or my Linux machine? Or, you know, my windows machine, or you know, the operating system on my telephone, right? Every time one of these devices that Ansible connects to, or program, or whatever it is, connects to something, those things are all operating and, you know, developing themselves at their own paces. Right? So when a new version of, you know, we'll call it Red Hat, Enterprise Linux. When a new version of Red Hat, Enterprise Linux comes out, if there are new changes, or new features that, you know, we want to be able to connect to, that's not really helpful when we're not releasing for another six months. Right? So it's really helped us, you know, from a community angle, to able to have each of these collections working in concert with, you know, for example, the Lennox subsystems that are actually making things that will turn be turned into collections, right? Like, SE Linux, or a system D, right? Like, those things move at their own pace. We can update those at our own pace in collections, and then people can update those collections without having to wait another six months, or eight months, or whatever it is, for a new version of Ansible to come out. It's really made it easier for all of those, you know, developers of content to work on their content and their, you know, Ansible relationships almost in sync. And make sure that, you know, not, "I'm going to do it over here. And then I'm going to come back over here and fix everything later." It's more of a, you know, continuous development process. >> So, the experience. So the contributor experience is better then? You'd say? >> I'm sorry? >> The contributor experience is better then? >> Oh, absolutely. Yeah. 100%. I mean, it's, you know, there's something to be said for, I wouldn't say it's like, instant satisfaction, but certainly the ability to have a little bit more independence, and be able to release things as you see fit, and not be gated by the entire rest of the project, is amazing for those folks. >> All right. So I'll put you on the spot, Robin. So if I'm a developer, bottom line me, what's in it for me? Why should I pay attention to collections? What's the bottom line? >> Well, you know, Ansible is a platform, and Ansible benefits from network effects. You know, the reason that we've gotten as big as we have, is sort of like the snowball rolling downhill, right? The more people that latch onto what you're doing, the more people benefit and the more, you know, additional folks want to join in. So, you know, if I was working on any other product that I would consider being able to have automated with Ansible, you know, the biggest thing that I would look at is, well, you know, what are those people also using? Are they automating it with Ansible? And I can guarantee you, 99% of the time, everything else that people are using is also being automated with Ansible. So you'd be crazy to not, you know, want to participate, and make sure that you're providing the best, Ansible experience for, you know, your application, cause for every application or, you know, device that we can connect to, there's probably 20 other competitors that also make similar applications that, you know, folks might also consider in lieu of you if you're not using, if you're not providing Ansible content for it. >> Hey, make things easier, simple to use, and you reduce the steps it takes to do things. That's a winning formula, Tom. I mean, when you make things that good, then you get the network effect. But this highlights what you mentioned earlier, about connective tissue. When you were using words like "connective tissue" it implies an organizational's, not a mechanism. It's not just software, it's people. As a people experience here in the automation platform. >> Robin: Yep. >> This seems to be the bottom line. What's your take? What's your bottom line view? I'm a developer, what's in it for me? Why should I pay attention to the automation platform? >> What Robert just said to me is, more people using. Automation platform, crossing those domains, and silos as kind of connective tissue across those teams, and its personas, means those contributors, those developers, creating automation content, getting in the hands of more people across the organization. In a more simplified way by using Ansible automation. They get access, the automation itself, those personas, they get access to the system automation faster, they can have the money quicker, local to local folks. To reinvent the wheel in terms of automation, we're trying to, (man speaking faintly) They don't want to know about the details, and what it takes to configure the network, configure the storage elements. They rely on those automation developers and contributors that review that for them. One powers of the platform. Across those teams, across those others. Okay we're going to talk about SecOps, The ITOps, in SecOps, in networkOps. And to do all of these tasks, with the same language, and same unition content, running faster, and it's monitoring core responsibilities without worrying. >> Robin, you wanted to talk about something in the community, any updates? I think navigator, you mentioned you wanted to mention a plug for that? >> Absolutely! So, you know, much like any other platform in the universe, you know, if you don't have really great tools for developing content, you're kind of, you know, dead in the water, right? Or you're leaving it to fate. So we've been working on a new project, not part of the product yet, but you know, it's sort of in a community, exploratory phrase. A release, early release often, or, you know, minimum viable product, I guess, might be the other way to describe it currently. It's called Ansible navigator. It's a Tooey, which is like a gooey, but it's got a, sort of a terminal, user interface look to it, that allows you to, you know, develop, it's a sort of interface where you can develop content, you know, all in one window. Have your, you know, documentation accessible to you. Have, you know, all of your test results available to you in one window, rather than, I'm going to do something here, And then I'm going to go over here, and now I'm not sure. So now I'm going to go over here and look at docs instead. It's all, you know, it's all in one place. Which we think will actually, but I mean, I know the folks who have seen it already been like, (woman squealing) but you know, it's definitely in early, community stages right now. It's, you know, we can give you the link. It's github.com/Ansible/Ansiblenavigator >> A tooey versus a gooey, versus a command line interface. >> Yeah! >> How do you innovate on the command line? It's a cooey, or a? >> Yeah! >> It's, you know, there are so many IDs out there and I think Tom can probably talk to some of this, you know, how that might relate to VA code or, you know, many of the other, you know, traditional developer IDs that are out there. But, you know, the goal is certainly to be able to integrate with some of those other pieces. But, you know, it's one of those things where, you know, if everybody's using the same tool and we can start to enforce higher levels, quality and standards through that tool, there's benefits for everyone. Tom, I don't know if you want to add on to that in any way? >> Yeah, it's just kind of one of our focus areas here, which is making it as easy as possible for contributors to create Ansible automation content. And so part of that is production, meaning S & K. Remember what happened to S & K for Ansible? That involved developers and contributors to use ID's, build and deploy automation content. So, I'm really focused on making that contributor life their job. >> Well, thanks for coming on Tom and Robin. Thanks for sharing the insight here at Red Hat Summit 21, virtual. So you guys continue to do a great job with the success of the platform, which has been, you know, consistently growing and having great satisfaction with developers, and now ops teams, and sec teams, and net teams. You know, unifying these teams is certainly a huge priority for enterprises because the end of the day, cloud-scale is all about operating. Which means more standards, more operations. That's what you guys are doing. So congratulations on the continued success. Thanks for sharing. >> Thanks for having us. >> Okay. I'm John for here in theCUBE we are remote with CUBE virtual for Red Hat Summit, 2021. Thanks for watching. (upbeat electronic music)

>> Welcome. My name is Richard Henshall. I'm a senior manager for product management, for Ansible Automation Platform. Think to yourself, how did you adapt to the changes this year? How was your team forced to adapt? And were you prepared and had you been automating already? Talking for the Ansible team, we're ready to move forward. Now we suspect that sentiment is shared by many of us here. We just had a good lesson in why being able to adapt quickly is so important. The previous ways of working may not always be available to us, and we have to change the way we focus and look at things. And this is why I have such a strong belief in the power that automation can gift us. And if we remind ourselves of what the goal of automation is, and to put it very simply, to perform work with minimal human interaction On one hand, this sounds great, no work. But it can also seem very impersonal. And the reality is automation cannot be achieved without knowledge and experience. Because what needs to be automated is what we learn. So much of what we do is specific to our circumstances, to our business or our own personal backgrounds. So how we approach automation is also important. And that's why this year's message "Automate to connect" is relevant to the times we find ourselves in. As a rhetorical question, and of course, all of these are rhetorical questions. I'm sat in a room at my house, staring at a camera. I would next ask you why we need to connect? And what do we connect for? Do we connect to share knowledge, to learn from others, to work on common goals and objectives? Reality is it should be all of these. Any intent when we connect from our work perspective, needs to be about collaboration. Collaboration is essential when we approach how we deal with change. Because when we talk about change, we often see it explained as people process and technology. But when we're forced to change, the unexpected circumstances, you can't always be prepared. You're not always given the time to plan and prepare the way you'd like. So having a way to connect, to build relationships and to collaborate is more important than ever. Back in the days when I was learning my trade, middleware engineering before the endless video calls, presentations and spreadsheets, the most difficult relationship to improve was between us in engineering and the network team. And it wasn't because of the skills it wasn't because we didn't like each other, at least I'd like to think so. And it wasn't for lack of trying. It's because the network team, they're on a different floor, big security door, magnetic locks, special key cards that you needed to have access for. It was aggressively protected so they couldn't be interfered with. It wasn't this opportunity to build the relationships in the same way that we could when we could go and collaborate with the Linux Windows or storage teams. You couldn't wander off and discuss a problem, just have a chat, they were locked away. Now, maybe they like that and sometimes it's good to be locked away, but it forms a barrier. And it's a barrier to collaboration. And so with this group, collaboration required meetings, it required planning and this made it harder. And when something's hard, it makes it easier not to do it. And additionally, we didn't have a platform to help us. So ask yourself, does that sound familiar to your circumstance? What we needed to connect those relationships and we've seen this time and time again, is that for automation we need a consistent technology foundation to connect. With the foundation encourages simplicity for collaboration foundation to connect the people, process and technology and a foundation to help us build trust in those relationships. If we'd had that foundation, that platform, we could have been successful much faster. 'Cause it's important we understand that success depends on trust between groups. To be successful in adapting to change we need to know we trust when the situation may not be perfect. It might be different offices, could be different countries, probably different languages, maybe even different objectives between these different groups. It might be a global pandemic, which is a phrase I never thought I would say in a keynote, but connecting with your colleagues, collaborating and therefore participating in the work that's done. Working as a wider team, enables you to see a broader perspective. Because how else do we trust? Unless we understand each other. How do we trust what we can create? Who has created it? Is he up to standard? And how do we trust what's running where? And who's been running it that we can scale with the correct control? And how do we trust that we can engage removing friction and complexity. And we can do all these things by being given the opportunity to participate, to be included in the overall process. Ultimately, how do we participate to achieve our goals? And what goals do we choose? Your goals are your business challenges automate what makes both your business and IT successful because participation is key to that process. And the more people you can bring together to connect, the more benefit you can achieve. If we've connected and collaborated, we trust what's being produced because automation can be a selfish act. I, the individual do something to make my job easier, but you should think of automation as a gift of knowledge and experience. How can you automate your job to make your colleagues' lives easier? So as we assume and know that participation enables collaboration, how do we help you to collaborate? Well with Ansible, the language of collaboration. And to collaborate, we need to connect. And for that, we have the Ansible Automation Platform. Everything I've described so far is drawn from our collective experience with customers. When Ansible the tool was released, it started as a way to perform automation in a simpler way. As your needs changed, we added more domains and then your needs changed again. As complexity and scale surfaced, a different set of challenges for us to look after. Not only did you do the automation, you need to do more automation as you achieve some successes. And afterwards you have to manage all that automation. To be successful we have deserved that it's not just what you do, it's how and where you do it. It's not just about the tool. It's about the structure, the framework. A focal point and a user experience in maintaining your automation assets. And this is why we focused all of our product offerings into Ansible Automation Platform, a single offering for enterprise grade automation. We've supported your changes in the past, and we've been working to support your changes for the future, help you adapt and connect. Now, if Ansible is the language of collaboration, collections, Ansible content collections are the building blocks of how you simplify the connection of your trusted technologies. Last year, we launched collections as a way to improve the management of content distributed within the Ansible project and the Ansible products. The teams involved were busy working on making this happen over the last 12 months. Working with our community and partners to migrate over 4000.5 modules. This work including this summer with the Ansible collections, 1.0 release. Last Ansible Fest we unveiled certified platforms with the Ansible certified partner program. End to end support for Ansible content between Red Hat and our trusted partners. We now have over 50 certified platforms focused on curated enterprise technology domains. The platforms that you use and rely upon because connecting these domains is connecting your teams. I'm talking about connecting teams. I'm sure that your planning has started already working on cloud native adoption. Key to that cloud native journey and story are containers. And that brings its own set of changes to the way that we work. And we want to support you as you adapt to these changes. I assume most of you are aware that OpenShift is Red Hat's intuivating container orchestration platform based on Kubernetes. And I'd like to announce the release of certified Ansible content collections of Red Hat OpenShift. Whether it be for augmenting provisioning, customizing cluster nodes, or data operations. Collections gives us the perfect opportunity to deliver these use cases and more. Because we know Red Hat customers have chosen and trust Ansible Automation and OpenShift platforms to drive transformation programs. But the connection between these two platforms and the teams that deliver these has always been very implementation efforts. We know that we need to move away from that implementation effort and move to product integration. The reality of evolving tech is it's never all or nothing. If you're fortunate, you can deploy your cloud native application entirely on OpenShift. But what happens, we need to manage across clusters or access existing infrastructure like networks or databases. We're excited to bridge traditional container and edge through Ansible Automation. Perhaps the only automation and container platform solution that is truly agnostic Ansible just doesn't care whose platform you're running on. The new Ansible resource operator, which we deployed as part of Red Hat advanced cluster management is our answer. We're making the Ansible Automation platform a first class provider inside ACM. To enable call outs to automation assets deployed on the automation platform and to make it easily accessible to container management workflows and connect two industry leading technology platforms. Enabling this integration with our customers to identify and enforce policies, applied governance models consistently across multiple clusters, as a deploy and scale complex applications across hybrid multi cluster environments. In the future, the resource operator will be available for any OpenShift deployed service to integrate to the Ansible Automation Platform. And to find out more about this, be sure to checkout Matt Jones' "Future of Ansible Automation Talk" as well as the ACM breakout sessions. Now, as collections are about connecting technology and product integrations are about connecting process. We still need to think about connecting people. How do we ensure that users can find trusted content? So while many users are happy to get content from Ansible galaxy, we know that many enterprises are far less comfortable with that situation. And certainly not comfortable uploading private developed content themselves. We also know that galaxy isn't the only source of content for you to use. There are other source control, repositories, other locations, perhaps even file shares where you allow your teams to collaborate and connect. With all these different sources it can be hard for your users, your internal communities to connect and trust they're using approved content. So we want to connect teams, help them collaborate, have shared goals and ensure trust in how they automate. We need to fill that gap. And that's why last year we launched the automation hub on cloud@redhat.com. As a trusted source for download downstream certified Ansible content supported as part of ground sports automation platform subscription. And this is where you access the collections for those 50 certified platforms I mentioned earlier. But that was only part one of the plan. So while we can provide a location for trusted content that doesn't bring together content from other sources. Before, I mentioned collections were introduced to help the management of automation content. By adopting collections, you provide a path for automation developers to bring content together in a common location, allow multiple teams to increase their time to value in the automation adoption journeys. But to connect internal communities of practice, we need to provide a focal point for all things related to automation content. And that's why we're pleased to announce that the private version of automation hub will be released to the content and knowledge management component of the Ansible Automation Platform. Your privately hosted location for all your Ansible content, to allow you to curate which content is available from which sources, whether it's from Red Hat, the Ansible community, or develop internally. You now have the control over which content you trust. Finally, this year we launched our third hosted service and no additional cost to platform customers. The automation services catalog. The purpose of this service was to allow you to connect your business users with rules-based governance and a simplified user experience to the automation creator deployed via the platform. We're announcing a tech preview launch with the connected technology security connect to your own prem platform environments. It's based on a technology that's part of our future plans. And again, if you attend Matt Jones' "Future of Ansible Automation Talk", you'll hear more about what we're planning in this area. Because this year has been somewhat challenging, automation and Ansible have become more important to many individuals and organizations. So I could leave you with one set of thoughts to adapt and to change as we face, keep things simple, participate in making automation happen and understand the problems to be solved, but always try and keep it simple. Evolve and scale as you connect your teams, as you would grow and expand your automation, grow and expand the scale you're working at as you move forward. And collaborate to break down the silos and domains that build and build your automation that makes change possible. Whether you're an Ansible expert or someone looking for some way to start, we have sessions we hope will inspire you to make your own changes and sessions that will give you the knowledge of how to adapt for the future. Thank you and happy automating.