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

>>lost myself. >>You know, one of the things that I love about the Cuba being doing it for 11 years now is that everyone that we interviewed years and years ago, they all getting promoted. So much fun to watch everyone grow and and now it's stews over there now so it's fun to get to do something. When >>are you gonna, are you gonna get to interview stew for? Way >>to put them on the hot seat? I think he's afraid actually >>throughout all the talking points. Right. 1st question. The way >>we do miss too. I will say that it is amazing. Okay, I'm ready to go. >>Red >>Hat Summit read. Pat Summitt, we're coming to you in. Hello and welcome back to the Red Hat Summit 2021 virtual coverage I'm john for is the cube coverage of Palo alto with the remote interviews for our virtual conference. You've got two great guests cube alumni's Tom Anderson VP of answerable automation platform and Robyn Bergeron who's the Senior manager and small community community architect and all the great things involved, Robyn great to see you tom. Thanks for coming back on red hat some of this year. Virtual. Good to see you. >>Thanks for having us. >>So since last summit, what's the updates on the answerable community and the automation platform? Tom we'll start with you automation platform. What's the big updates? >>Yeah. So since the last time a lot has happened in the unanswerable land. If you will also last time that we were talking about constant collections have given distribution format or the integrations that ends this close. So a lot of the content. Uh huh. As well as the commercial users we launched last year a fucking program certified contact program with our partners and including partners to certify the content collections today. Create co certify them where we work together to make sure that they're uh developed against and tested against a proper step so that both of us can provide them to our customer basis with confidence that they're going to be working informed broccoli and that we red hat and our partners co support those out in our customers 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 Ansel Galaxy or the answerable automation to go and grab these content collections. This these integrations and bring them down in their environment. They wanted a way that they wanted a methodology where there are a repository where they can curate content from different sources and then manager across the environment. The automation across their environment. Kind of leaning into a little bit of automation content as code if you will. And um, so we launched the automation of the private automation hub where that sits in our customers infrastructure, whether that's in the cloud or on premises with both, and allows them to grab content from Galaxy from the answer automation. Uh, the answer automation hub on cloud got red hat dot com as well as their internally developed content and to be able to manage and provide that across their organization governed by a set of policies. So lots of stuff is going on real advancement in the amount of content that we provide, uh, the amount of collections that we provide them certified up for customers and and the ability to manage that company 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 scale because that's the super value proposition you guys have and want to get that. But robert, I want to come back to you on the community so much has gone on, we are now into the pandemic for almost a year and a half now, um it's been a productivity boom. People, 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 has 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 gets 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, you know, everything you would install answerable, you would get all the modules, you get everything, you know, it was all all all together, which, you know, is 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. Um and But, you know, for a from a community perspective, trying to manage that level of complexity turned out to be pretty hard. So the move to collection was actually great for, you know, not just, you know, for a user perspective, but also from a community perspective. Um and we came out with the answerable to 10 that was last fall, I believe, and that was the first real release advance. Well, where we had, you know, collections were fully in stan she hated uh you know, they were available on Galaxy, but you can also get them as part of the animal community distribution. Um, fast forward to now. You know, we just had the answer to all three point oh release here in february and we're looking to answer bill ford auto 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 start and identify, you know, who are, they're interested peers in the community. So that's been a boon for us honestly. Um, you know, the pandemic otherwise is, you know, I think taught all of us, you know, certainly you john about the, the amazing things that we can do virtually. So we've had a lot of our meetups pivot to being virtual meetups and, and things like that. And it's been great to see how, how easily the community's been able to pivot around. You know, this sort of event. Um, 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 we're gonna come back and talk more about that in the future, but best practice what we all learned and stories. But I think I want to come back to you on the persona side of answerable because one of the things we talked about last time that seems to be getting a lot of traction is that multiple personas. So I want to just hold off that will come back tom back to back to you were red hat summit. You guys have an apple fest, which is your own event that you guys drill down on this. So users Washington, you know this, your own community, but now part of red hat part of IBM, which IBM thinks also happening soon as well. Red hat some, it still is unique event. How is answerable fitting into the big picture? Because the, the value proposition of unifying teams is really consistent now with red hats overall arching thing, which is operating at scale open shift Robin just mentioned, where is the automation platform going this year? What's the story here at red hat summit for the automation platform? >>Yeah, that's that's a great question. We've seen so kind of timeless, a little bit of dependent and how it has accelerated some existing trends that we already saw and one of those is really around the democratization of the application delivery teams, more people delivering infrastructure and applications independent of each other, which is right, faster and more agile, all of those other. Good, good uh, words that apply to that. But what that does bring up is the opportunity for um >>patient >>of work, replication of effort, uh not reusing necessary things that are in existence already that other things may have maybe not complying with all of the policies if you will, the configuration and compliance policies. And so it's really kind of brought danceable out into focus even more here because of the car comin back plane that provides a common language and common automation back plane across these different teams and across these different personas. The great thing about what we supply for these different personas, whether its application developers, infrastructure owners, network engineers set up teams, get ox teams, There's so many of these options out there now, All want independent access to infrastructure and deploying infrastructure. And Answerable has the kind of levers that each of those communities, whether it's API or Cli s or event based automation or uh web hooks, et cetera et cetera. You know, service catalog. He lies all of those um interfaces if you will or modalities are accessible into hands of water nations. What's really allowed us to be this sort of connective tissue or blue across these different silos or remains of the organization the time of the year? Open ship specifically one of the things that we talked about last fall and are answerable fest was our integration between Answerable to automation platform are advanced cluster management product and are open ship platform that allows native applications running on open ship. Be able to talk to a sensible automation operator that's running on that same platform to do things off platform for it that our customers are already using. Answer before. So connecting their cloud, native platforms with their existing ecosystems and infrastructures. Systems of records, network systems, uh, ticketing systems, you name it. So all of those sort of integrations and school has become the connected blew across all of these different environments time. Traditional, anti biotic native, you name it. So it's really been it's really been fun and it's been an exciting time for us inside the portfolio. And uh, >>that's a great point connective tissue is a great way to describe some of these platform benefits because you have been on this platform for a really long time and the benefits are kind of being seen in the market. Certainly as people have to move faster with the agility robert. I want to come back to you because you brought up this idea of personas. I mean we all know devops infrastructure as code has been our religion for over a decade more, but now the word DEv sec ops is more prevalent in all the conversations the securities now weaved in here. How are you seeing that play out in the community and then tom if you can give some color commentary to 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 problems You have. But def sec off as a persona, more people want more sex. Deb is great more ops and standardisation. More developers, agile standards and then security def sec ops. What's your? I >>thought it was dev net sec off. >>Okay. I've forgotten that they were putting that in their networks abstracted away, you know, As we say. Yeah. >>Well, you know, from, from my perspective, you know there are people and their jobs all over the place is 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 has 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 I. T. 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 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, a community perspective, I mean, we've seen people who have been writing, you know, playbooks and roles and you know, now collections for uh you know, all the traditional government testing, you know, is are, you know, missed standards, all of that kind of stuff. Um and you know, it's one of those, it's part of network effects and it's a great place where actually automation hub, I think, you know, for folks who are on prem or you know, any of our customers are really going to start to see lots of value is how it will be able to connect folks inside the organization organically through just the place where I'm doing my answerable 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 of answerable friends and uh danceable power users that can work together and collaborate, you know, just the same way that we do an open source >>and tom so I. T. Modernization requires security. What's your take on this? Because, you know, you got cluster a lot of cluster advanced cluster management issues, you've got to deal with the modern apps, they're coming, I. T. S got to evolve. What's your take on all >>this? Yeah, not only does I have to call but it's it's an integration like the rest of the environment and be able to respond the spirit of that song on the areas that we put a lot of effort into advanced in terms of curating and solutions around national security automation. We talked about that in the past, the idea of connecting the SEc ops teams that are doing intrusion detection or threat hunting and then responding in an automated way to those threats protections. Right? So, connecting stepped up to the bike, which is traditionally been styled operations and silo teams. And now it is curated against the security automation uh, solution that we've got a market with our partners. It connects those two teams in a single sort of way. We've done a lot of work with our friends that idea around this area because they are big and that security area, a radar and other products in their portfolio. So we've done a lot of work with them but we don't want to work with lots of our partners for their side. There are Microsoft in those areas. Traditionally Danceable has done a great job on sort of compliance around configuration enforcement, right setting and enforcing configuration. Now we moved into connecting set pops with IT security automation. And now with our acquisition of staff blocks along with our advanced custom management immigration with Danceable were starting to say, what are the things inside that sack office workflow that may require integration or automation packaged? Automate automation with other parts of the environment, bringing all of those pieces together as we move forward to security for us. >>Okay. I gotta ask you guys the number one question that I get all the time and I see in the marketplace is 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 born the cloud projects, whether it's whether and then integrating able to cloud on premises with nutritional infrastructure, how do I accelerate those two environments? How I automate accelerate the automation? >>Yeah. So it's a great story for us and this is what we're talking about, small and special as we have bringing together of our advanced cluster management product, open ship platform and it's just, you know, widespread use through all the automation of both traditional and cognitive changes. Whether it's cloud infrastructure on premise, start network, you name it, customers are using answerable user, you're using answer to do all kinds of pieces in the system infrastructure. Being able to tie that to their new collaborative initiatives without having to redo all of that work that they've already done to integrate that existing um infrastructure automation with their cognitive accelerate substantial what I call the offer operationalization to say operated operationalization, their cloud native platforms that are existing infrastructure and existing I uh, ecosystem. I believe that that's where the answer the automation and plays a key role in connecting those students is together without having to redo all that work that's been done in investment >>robert. What's your take on this? This is what people are working on the trenches, they realized cloud benefits. They got some cloud native action, and also that they got the on the traditional environment, they got to get them connected and automated. >>Yeah, absolutely. I mean, you know, the beauty of answerable, you know, from an 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 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 in a it's not quite english, but it's definitely, you know, answer is quite readable, right? Um, and you know, when we looked at, you know, when we started to work on all the answerable operators, you know, one of that, one of the main pieces there was, making sure that that simplicity that we have an answerable is brought over directly into the operators. So just because it's cloud native doesn't mean you suddenly have to learn, you know, a whole set of new languages and peoples just as portable there as it is to any other part of the your mighty organization, infrastructure or 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 um is the successor and the importance of you guys having answerable collections. This has come up multiple times. Um as we talked about those personas and you've got these new contributors, you've got people contributing content. Um, as open source continues to grow and be phenomenal value proposition. Touch on this uh, concept of collections. What's the updates? Why is it important? Why should folks pay attention to it and continue to innovate with collection? >>This is from a commercial perspective of food products, questions and down has made a lot of these contributors to create an exploit, distribute content at the end, the problems mentioned earlier, these iterations announced, we'll have all of the documentation, all those collections, all within one. If you call the batteries included back at the time that day. Right. But that, that meant that contributors um, be able to deploy their content with the base, has the distribution. They have to wait for the next version. Events. Alright, that's when that content would get redistributed the next investment. He coupled content from the core engine, putting that into elections that are individual elements of related innovations closes can use at their own pace. So users and customers can get content baby a case that contributors like in public. So, uh, customers don't have to wait for the next evolution shipping products. You get a new version of the immigration is really like, you know, so again, a couple of those things that last into the different faces the engine or the platform itself is the state Department's here. It's going to be a certain website. Content itself, all the different content, the network providers ready platforms, all of those same pace. You girls have their own life cycle quite sweet. It allows us to get more functionality for customers hands like bigger and then launching our Certified can support that. Okay. Certified. Support that content tells me the values that we bring our customers with the subscription. Is that ecosystem and highest partners that we work with Certified and support the stuff that we should and support with possible superb benefits, both on the access to the technology as well as the access to the value of this. In terms of immigration testing and support >>Robin, What's your take on the community? I see custom automation with with the connector, a lot of action going on collections. >>Yeah, absolutely. Um, 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 answerable 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 Lennox machine or, you know, my Windows machine or, you know, the operating system on my telephone, right? Every time one of these devices that answerable connects to or a program or whatever it is, connects to something, those things are all operating and, you know, developing themselves at their own pace is right? So when a new version of, you know, uh, uh, well, we'll call Red Hat enterprise Linux when a new version of Red Hat enterprise Lennox comes out, uh, if there are new changes or new features that, you know, we want to be able to connect to it. 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 be able to have each of these collections working in concert with, you know, like for example, in real like the Lennox subsystems that are actually making things that will be turned into collections, right? Like Sc Lennox or System D right? Like those things move at their own pace, we can update those at our own pace in 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 answerable 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, answerable relationships almost in sync and make sure that, you know, but not, I'm going to do it over here and then I'm gonna come back over here and fix everything later. It's more of a continuous >>development. So they contribute experience is better than you'd say. >>I'm sorry, >>the contributor experiences better than. Oh, >>absolutely. Yeah, 100%. I mean, it's, >>it's, >>you know, there's something to be said for. I wouldn't say it's like instant satisfaction, but, but certainly the ability to have a little bit more independence and be able to release things as as you see fit and not be gated by the entire rest of the project is amazing for those >>votes. So I put you on the spot, Robin. So if I'm a, I'm a developer bottom line, me, what's in it for me? Why? Why should I pay attention to collections? What's the bottom >>line? Well, you know, answerable as a platform and, and for benefits from network effects. Um, you know, the reason that we've gotten as big as we have sort of like the snowball rolling downhill, right, the more people that latch on to what you're doing, the more people benefit and the more, you know, additional folks want to join in. So, you know, if I, if I was working on any other product that I would consider being able to have automated with answerable, um, you know, the biggest thing that I would look at is, well, you know, what are those people also using or they automating it with an apple and I can guarantee you 99% of the time, everything else that people are using is also being automated with answerable. So you'd be crazy to not, you know, want to participate and make sure that you're providing the best, you know, and experience for your application because for every Application or device that we can connect you, there's probably 20 other competitors that also make similar applications that folks might also consider in lieu of you if you're not using your not providing ample 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 use words like connective tissue, it implies an organizational is not a mechanism. It's not just software, it's people, there's a people experience here in the automation platform. This seems to be the bottom line. What's, what's your take? What's your bottom line of you? I'm a developer. What's in it for me? Why should I pay attention to the automation platform? >>States of the public developer. What excites me is using it? Yeah, I'm just composition department and crossing those domains in silence and sort of can issue across these tools and resolve this means those contributors is developed as a great denomination come embedded in the hands of more people across the organization. Absoluteal more simple. five way by using the explanation. Sometimes they get access right. You see those out the automation of South coast for so long as they get access to existing automation faster. They have to run into the expert on their part requirement a local hotel folks and the real in terms of automation and that kind of a patient. Excellently. When I'm getting on you about the details of what it takes them, you configure the network and figure the storage elements. They rely on those automation developers and contributors that would do that for them. You must really work powers of this Children across those news process of human. Again when I got kidnapped and sent cops, the idea of connecting to the network, being able to do all of these tasks with the same language and the same. In addition, funds had some money faster and get some of the kind of quote responsibilities without worrying. Line >>Robin, you wanted to talk about something uh, in the community. Any updates? I think navigator you mentioned you wanted to mention uh, plug for that. Absolutely. >>So, you know, um, much like any other platform in the universe. You know, if you don't have really great uh, 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. I'm not part of the product yet, but you know, it's sort of in a community exploratory phrase released early release often or you know, minimum viable project I guess might be the other way to describe it currently. Uh it's a called Animal Navigator, it's a TUI 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, its a sort of interface where you can develop content, uh 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, um rather than I'm going to do something here and then I'm gonna go over here and now, I'm not sure. So now I'm gonna go over here and look at docs instead. It's all, you know, it's all in one place, um which we think will actually, but I mean, I know the folks who have seen it have already been like, but you know, it's definitely an early community stages right now. It's, you know, we can give you the link github dot com slash answer slash danceable navigator, but >>versus a gooey versus a command line interface are how do you innovate on the command line? It's a kuwaiti uh it's >>um you know, there there's so many ideas out there and I think tom can probably talk to some of this, you know, how that might relate to V. S. Code or you know, many of the other traditional developer ideas that are out there, but you know, the goal certainly to be able to integrate with some of those other pieces. Um but you know, it's one of those things where, you know, if everybody is using the same tool, we can start to enforce higher levels of quality and standards through that tool. Uh 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 religious making it as easy as possible to create things and a lot of nations. So part of that is essentially a kind of road map in the nesting table and spoke that that's not presented to the security is you don't build test deploy. So people are making a contributor that builders life job. >>Well, thanks for coming on tom and Robyn. Thanks for sharing the insight here. Redhead Summit 21 virtual. I'll see you guys do 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 a skill, 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 the queue, we are remote with Cube virtual for Reddit Summit 2021. Thanks for watching what?

>> Good morning, good afternoon and good evening wherever you are. My name is Robyn Bergeron and I'm very, very, very, truly excited to welcome all of you to this year's Ansible Fest. Whether you're joining us for the first time or if you've attended in the past. It's wonderful to know that you're all out there watching from the office in your home, maybe the makeshift office in your closet or dining room, or maybe even your actual office. Even though I've attended many Ansible Fest in the fast I continue to find to be one of the most educational and interesting events I've ever been to. I hope you do as well. One of the most exciting things about Ansible Fest for me this year is our theme, which can you shared in her opening remarks, automate to connect. As a community architect and as a manager of the Ansible community team. The solitating connections enable our community is most important thing we do every day. And scaling what we can all accomplish together is becoming credibly important, as Ansible become one of the most active open source projects in the world. There's no better example of understanding the growth and the scale of the Ansible community than seeing just how many of you were, we were able to connect with today at our very first virtual Ansible Fest with tens of thousands of folks attending over the course of our time together and even more on their own schedules. We're now actually able to connect with more members of our community than we ever have before. And this statement we are all the community continues to be as true as ever for Ansible. I truly believe that every connection counts I really believe that each and every one of us has the ability to participate in the Ansible community in countless ways, whether it's through code, whether it's through sharing with your friends or coworkers or helping others all over the world. And no matter how big we becomes a community we want to make sure that those connections and your sense of being part of this community to be alive and is full of potential as it always has been. And we want that because that very potential and taking advantage of all of those connections and opportunities is what enables innovation to happen. And we see that innovation happening in Ansible every single day. We all know that open source communities and produce some of the most innovative and most popular software that exists today. But being a community doesn't just come simply by the virtue of being open source, right? And neither does innovation growing the community requires frameworks and enable these connections to exist right between developers and users code and tools. And when we are able to combine those frameworks with opportunities and ideas, that's where innovation can actually flourish and that's the place where the benefits of opensource truly shine. And in Ansible from the very beginning, we strive to ensure that all of those frameworks and ingredients versus such a successful project were present. We made it easy to learn and get started with. We made sure it was at least minimally useful and then it could grow over time. We built the tool itself with a modular plugin architecture that would make it easy to contribute to. In turn, all of those contributions enabled Ansible to become even more useful, connecting audit, connecting and automating even more technologies which then made it useful to even more people. And this, this is really open source innovation at its finest, right? Thousands of users and contributors working together developing feedback loops all going to build software that everybody loves. But doing it well and having some good fortune and timing along the way has also meant that we've gotten fairly large and incredibly active as a community. What this level of scale and more relatable terms that we probably understand since we've all been on video call lately, imagine that you've made something and you would like to get feedback about the thing that you've made. So you invite a hundred people to your video call and you want all of them to provide feedback. Cause you want that feedback, You need the feedback cause you want to act on the feedback. Are you actually going to get that feedback in the phone call? Or the folks that you invited truly feel like they were heard or will you spend the whole call saying I'm sorry, are you trying to talk? Are you, are you on mute? Maybe? Could you make yourself? No, no, not you. The other person you can, you, can you try again? Thanks, for us in Ansible we want to make sure that every voice counts, every contribution matters. Every single bug reported, every improvement and usability, every question answered every word for me Emoji really does count, over its history Ansible had more than 13,000 individual voices speak at least once. And many of those individuals have done so hundreds and some even thousands of times. And for every single connection individual makes multiple automated processes and communications occur fanning out to even more members of our community. And for end users, while we know that adding new ways to automate with Ansible increases its usefulness we've heard that particular folks get more experienced that things like being more selective and flexible in what they choose rather than having all 6,800 modules included for them. The collection concept is the innovative answer to improving our country contributor process and the end user experience and ensuring they'll both scale smarter ways as we move into the future. And it's really more the result of more than a year of work. In a nutshell, collections are a new way to make use of the content that you connect to Ansible modules even roles, and do soar in more dynamic and flexible ways. There's a couple of things that really excited me about collections. So number one, it's easier to contribute to right? collections can live in their own individual repositories which for the Ansible community makes it a lot easier for folks to find and connect with the content that they care about and connect with the users and contributors to that more human scaled community. The second thing, is for users, it's not easier to easier than ever to use Ansible in all the ways that you want to or need to. Since collections can be packaged and made available on their own schedules, you can update them or upgrade them as frequently or as infrequently as you'd like or you can upgrade a more minimal Ansible installation without updating your collection. Now, I know what you're all saying. What do we want? Collections. When do we want it? yesterday. Woo. Well, behold I am super proud to re announce the release of Ansible to Dutch and which arrives in late September. And yes, the collection curated by the Ansible community for inclusion in Ansible are into 2.10. The amazing thing about this release is really the amount of coordination amongst so many points of connection, right? We required changes to our build and release processes extraordinary amounts of work being done under the hood. And it was a significant part of our feedback loop as well. We finished the work on the collections concept but the important thing about two 10 is this as an upstream community that continually develops new technologies. You know, we really see collections as a significant part of the future of Ansible. So getting early feedback on your experiences and using collections is incredibly important to our community. Two 10 is the first release where we're actually able to start broadly gathering an information. And as a part of the process we can hear your feedback a lot better as well now. Now, we all know that this year has been interesting for all of us, right here, I have the 2020 dumpster fire. Yes, it's been the best. We've all had to adapt and change in lots of ways right? At home, at work in public and at school and in the communities that we love. I always like to remind people that contributing code is not the only way to contribute or participate in the community. Our aunts will meet up communities that have been growing in size and membership over the past number of years. We now have more than 260 groups all over the world still looking for that one in Antarctica. Self organizing and creating Ansible content to share in their local communities. This is really an aspect of the Ansible community that I've always loved that so many humans recognize how sharing information in their own local areas collaborating together to teach each other new things helps to improve their own communities for the better. But this year they've also reminded me that humans are incredibly resilient right? We bounce back from life altering situations. We bounce back from, you know, New store, we adapt to new situations and we always form new connections and points of collaboration along the way. A ton of these groups still wanting to share all of their experiences and teach each other together pivoted their meetup groups in a variety of ways. Since March, there've been more than 54 virtual Ansible meetups all over the world. And all those organizers are starting to see the patterns that connect local and not so local meetup members in the best ways whether that's by common language, time zone country rather than a city they're all coming together adapting as best as they can given the year. But for me personally one of the most important lessons that I draw from is a community person over and over again, is that connecting contributors to opportunities isn't necessarily about deciding what I think should be available as opportunities. It's about making that the short doors open for anyone to create those connections and opportunities that nobody had yet started. This year in Ansible, we've seen this in action with the creation of a diversity and inclusion working group which meets regularly to explore all the ways in which we can improve and do outreach and be more inclusive. And the group was also key in our projects work to improve the inclusiveness of our code and language itself, which began many months ago. I can honestly say that all of these activities initiated by all the passionate folks in the Ansible community are things that make me so proud to call Ansible my home. And it really does make me proud to see how much we're maturing as a community. In my role, I've had the privilege of you know, being able to meet and chat with Ansible users all over the world. Sometimes the person, sometimes on the internet one of the discussions I had a few years ago was with someone who was a systems administrator which was a job that I had numerous years ago. So lots of empathy. It was the nineties for me, but anyway, chatted with him and he told me how much he loves Ansible how's finally a tool that he could get started with and be productive with and you know, felt good about it very quickly, he was able to start solving problems. And he told me about all the things that he had accomplished and you know, he'd been able to change things you know, for the better for himself at work for his coworkers and you know, they're actually finally getting ahead. I asked how long they've been using Ansible. And he said, well, you know, it's been about a year but then he also said this, you know, a year ago I wasn't really sure that I could go on at my job. Like, you know, there was so much to do I was, you know, fight fighting fires. I was on call constantly, you know, nothing ever ended I was deep underwater and I was missing out on my family and their lives, you know, all of their milestones. And he said, this year I actually got to go to my daughter's fifth birthday which he had missed her fourth birthday the year before because he was at work fighting fires and he said, you know, Ansible has changed my life I can see my kids again, like on the weekends and you know like a normal person should and you know, hearing stories like that, that's stuff that makes me very proud you know, and humbled to be in this community. And one of the main reasons why I go to work every single day and feel great about what I do and those stories, aren't really all that uncommon it's really our shared love of automation. Our, all of our shared embrace of this universal language and tool that we call Ansible that has helped so many people to improve their personal lives their work lives, their careers you know, the world they're in the world for all of us. And it really truly does connect us in so many amazing ways. It's not just shared code, it's a shared passion and that kind of connection is something that can change our own worlds or the world for all of us. If you're attending Ansible festival live this week I hope you'll take time to connect with others in the event platform to meet all of the other automation users in your community our experts ask questions or share your own experiences. And I hope to bump into you too on the internet and hear your stories about your own connections to automation and the Ansible community. Thank you so much and I hope you enjoy the event.

>> Announcer: From around the globe, it's theCUBE! With digital coverage of AnsibleFest 2020. Brought to you by Red Hat. >> Hello, everyone. Welcome back to theCUBE's coverage of AnsibleFest 2020. I'm your host with theCUBE John Furrier. And we've got two great guests. A CUBE alumni, Robyn Bergeron, senior manager, Ansible community team. Welcome back, she's with Ansible and Red Hat. Good to see you. And Matt Jones, chief architect for the Ansible Automation Platform. Again, both with Red Hat, Ansible was acquired by Red Hat. Robyn used to work for Red Hat, then went to Ansible. Ansible got bought by Red Hat. Robyn, great to see you, Matt, great to see you. >> Yep, thanks for having me back again. It's good to see you. >> We're not in person. It's the virtual event. Thanks for coming on remotely to our CUBE virtual, really appreciate it. I want to talk about the, and I brought that Red Hat kind of journey Robyn. We talked about it last year, but it really is an important point. The roots of Ansible and kind of where it's come from and what it's turned into and where it is today, is an interesting journey because the mission is still the same. I would like to get your perspectives because you know, Red Hat was acquired by IBM, Ansible's under Red Hat, all part of one big happy family. A lot's going on around the platform, Matt, you're the chief architect, Robyn you're on the community team. Collections, collections, collections, is the message, content, content, content, community, a lot going on. So take a minute, both of you explain the Ansible roots, where it is today, and the mission. >> Right, so beginning of Ansible was really, there was a small team of folks and they'd actually been through an iteration before that didn't use SSH called Funk, but you know, it was, let's make a piece of software that is open source that allows people to automate other things. And we knew at the time that, you know, based on a piece of research that we had seen out of Harvard that having a piece of software be architected in a modular fashion wasn't just great for the software, but it was also great for developing pathways and connections for the community to actually contribute stuff. If you have a car, this is always my analogy. If you have a car, you don't have to know how the engine works in order to swap out the windshield wipers or embed new windshield wipers, things like that. The nice thing about modular architectures is that it doesn't just mean that things can plug in. It means you can actually separate them into different spots to enable them to be plugged in. And that's sort of where we are today with collections, right? We've always had this sense of modules, but everything except for a couple of points in time, all of the modules, the ways that you connect Ansible to the vast array of technologies that you can use it with. All of those have always been in the full Ansible repository. Now we've separated out most of, you know, nearly everything that is not absolutely essential to having in a, you know, a very minimal Ansible installation, broken them out into separate repositories, that are usually grouped by function, right? So there's probably like a VMware something and a cloud something, and a IBM, z/OS something, things like that, right? Each in their own individual groups. So now, not only can contributors find what they want to contribute to in much smaller spots that are not a sea of 5,000 plus folks doing work. But now you can also choose to use your Ansible collections, update them, run them independently of just the singular release of Ansible, where you got everything, all the batteries included in one spot. >> Matt, this brings up the point about she's bringing in more advanced functionality, she's talking about collections. This has been kind of the Ansible formula from the beginning in its startup days, ease of use, easy, fast automation. Talk about the, you know, back in 2013 it was a startup. Now it's part of Red Hat. The game is still the same. Can you just share kind of what's the current guiding principles around Ansible this year? Because lots going on, like I said, faster, bigger, a lot going on, share your perspective. You've been there. >> Yeah, you know, what we're working on now is we're taking this great tool that has changed the way that automation works for a lot of people and we want to make it faster and bigger and better. We want it to scale better. We want it to automate more and be easier to automate, automate all the things that people want to do. And so we're really focusing on that scalability and flexibility. Robyn talked about content and collections, right? And what we want to enable is people to bring the content collections, the collections, the roles, the models, and use them in the way that they feel works best for them, leaving aside some of the things that they maybe aren't quite as interested in and put it together in a way that scales for them and scales for a global automation, automation everywhere. >> Yeah, I want to dig into the collections later, Robyn, for sure. And Matt, so let's, we'll put that on pause for a minute. I want to get into the event, the virtual event. Obviously we're not face to face, this year's virtual. You guys are both keynoting. Matt, we'll start with you. If you can each give 60 seconds, kind of a rundown of your keynote talk, give us the quick summary this year on the keynotes, Matt, we'll start with you. >> Yeah. That's, 60 seconds is- >> If you need a minute and a half, we'll give you 90 seconds, Robyn, that's going to be tough. Matt, we'll start with you. >> I'll try. So this year, and I mentioned the focus on scalability and flexibility, we on the product and on the platform, on the Ansible Automation Platform, the goal here is to bring content and flexibility of that content into the platform for you. We focused a lot on how you execute, how you run automation, how you manage your automation, and so bringing that content management automation into the system for you. It's really important to us. But what we're also noticing is that we, people are managing automation at a much larger scale. So we are updating the Ansible Tower, Ansible AWX, the automation platform, we're updating it to be more flexible in how it runs content, and where it can run content. We're making it so that execution of automation doesn't just have to happen in your data center, in one data center, we recognize that automation occurs globally, and we want to expand that automation execution capability to be able to run globally and all report back into your central business. We're also expanding over the next six months, a year, how well Ansible integrates with OpenShift and Kubernetes. This is a huge focus for us. We want that experience for automation to feel the same, whether you're automating at the edge, in devices and virtual machines and data centers, as well as clusters and Kubernetes clusters anywhere in the world. >> That's awesome. That's why I brought that up earlier. I wanted to get that out there because it's worth calling out that the Ansible mission from the beginning was similar scope, easy to do and simplify, but now it's larger scale. Again, it's everywhere, harder to do, hence complexity being extracted away. So thank you for sharing. We'll dig into that in a second. Okay, Robyn, 60 seconds or more, if you need it, your keynote this year at AnsibleFest, give us the quick rundown. >> All right. Well, I think we probably know at this point, one of the main themes this year is called automate to connect and, you know, the purpose of the community keynote is really to highlight the achievements of the community. So, you know, we are talking about, well, we are talking about collections, you know, going through some of the very broad highlights of that, and also how that has contributed, or, not contributed, how that is included as part of the recent release of Ansible 2.10, which was really the first release where we've got it very easy for people to actually start using collections and getting familiar with what that brings to them. A good portion of the keynote is also just about innovation, right? Like how we do things in open source and why we do things in certain ways in open source to accelerate us. And how that compares with the Red Hat, traditional product model, which is, we kind of, we do a lot of innovation upstream. We move quickly so that if something is maybe not the right idea, we can move on. And then in our products, that's sort of the thing that we give to our customers that is tried, tested and true. All of that kind of jazz. We also talk about, or I guess I also talk about the, all of our initiatives that we're doing around diversity and inclusiveness, including some of the code changes that we've made for better, more inclusive language in our projects and our downstream products, our diversity and inclusion working group that we have in the community land, which is, you know, just looking to embrace more and more people. It's a lot about connectivity, right? To one of Matt's points about all the things that we're trying to achieve and how it's similar to the original principles, the third one was, it's always, we need to have it to be easy to contribute to. It doesn't necessarily just mean in our community, right? Like we see in all of these workplaces, which is one of the reasons why we brought in Automation Hub, that folks inside large organizations, companies, government, whatever it is, are using Ansible and there's more and more, and, you know, there's one person, they tell their friend, they tell another friend, and next thing you know, it's the whole department. And then you find people in other departments and then you've got a ton of people doing stuff. And we all know that you can do a bunch of stuff by yourself, but you can accomplish a lot more together. And so, making it easy to contribute inside your organization is not much different than being able to contribute inside the community. So this is just a further recognition, I think, of what we see as just a natural extension of open source. >> I think the community angle is super important 'cause you have the community in terms of people contributing, but you also have multiple vendors now, multiple clouds, multiple integrations, the stakeholders of collaboration have increased. It was just like, "Oh, here's the upstream and et cetera, we're done, and have meetings, do all that stuff." And Matt, that brings me to my next question. Can you talk about some of the recent releases that have changed the content experience for the Ansible users in the upstream and within the automation platform? >> Well, so last year we released collections, and we've really been moving towards that over the 2.9, 2.10 timeframe. And now I think you're starting to see sort of the realization of that, right? This year we've released Automation Hub on cloud.redhat.com so that we can concentrate that vendor and partner content that Red Hat supports and certifies. In AnsibleFest you'll hear us talk about Private Automation Hub. This is bringing that content experience to the customer, to the user of this content, sort of helping you curate and manage that content yourself, like Robyn said, like we want to build communities around the content that you've developed. That's the whole reason that we've done this with collections is we don't want to bind it to Ansible core releases. We don't want to block content releases, all of this great functionality that the community is building. This is what collections mean. You should be free to use the collections that you want when you want it, regardless of when Ansible core itself has released. >> Can you just take a minute real quick and just explain what is collections, for folks out there who are rich? 'Cause that's the big theme here, collections, collections, collections. That's what I'm hearing resonate throughout the virtual hallways, if you will. Twitter and beyond. >> That's a good question. Like what is a collection itself? So we've talked a lot in the past about reusable content for Ansible. We talk a lot about roles and modules and we sort of put those off to the side a little bit and say, "These are your reusable components." You can put 'em anywhere you want. You can put 'em in source control, distribute them through email, it doesn't matter. And then your playbooks, that's what you write. And that's your sort of blessed content. Collections are really about taking the modules and roles and plugins, the things that make automation possible, and bundling those up together in groups of content, groups of modules and roles, or standing by themselves so that you can decide how that's distributed and how you consume that, right? Like you might have the Azure, VMware or Red Hat satellite collection that you're using. And you're happy with that. But you want a new version of Ansible. You're not bound to using one and the same. You can stick with the content that matters to you, the roles, the modules, the plugins that work for you. And you decide when to update those and you know, what the actual modules and plugins you're using are. >> So I got to ask the content question, you know, I'm a content producer. We do videos as content, blog posts content. When you talk about content, it's code, clarify that role for us because you got, you're enabling developers with content and helping them find experts. This is a concept. Robyn, talk about this. And Matt, you can weigh in, too, define what does content mean? It means different things. (indistinct) again, content could be. >> It is one of those words, it's right up there with developers, you know, so many different things that that can mean, especially- >> Explain content and the importance of the semantics of that. Explain it, it's important that people understand the semantics of the word "content" with respect to what's going on with Ansible. >> Yeah, and Matt and I actually had a conversation about the murkiness of this word, I believe that was yesterday. So what I think about our content, you know, and I try to put myself in the mind, my first job was a CIS admin. So I try to put myself in the mind of someone who might be using this content that I'm about to attempt to explain. Like Matt just explained, we've always had these modules, which were included in Ansible. People have pieces of code that show very basic things, right? If I get one of the AWS modules, it would, I am able to do things like "I would like to create a new user." So you might make a role that actually describes the steps in Ansible, that you would have to create a new user that is able to access AWS services at your company. There may be a number of administrators who want to use that piece of stuff, that piece of code over and over and over again, because hopefully most companies are getting bigger and not smaller, right? They want to have more people accessing all sorts of pieces of technology. So making some of these chunks accessible to lots of folks is really important, right? Because what good is automation, if, sure we've taken care of half of it, but if you still have to come up with your own bits of code from scratch every time you want to invoke it, you're still not really leveraging the full power of collaboration. So when we talk about content, to me, it really is things that are constantly reusable, that are accessible, that you tie together with modules that you're getting from collections. And I think it's that bundle, you can keep those pits of reusable content in the collections or keep them separate. But, you know, it's stuff that is baked for you, or that maybe somebody inside your organization bakes, but they only have to bake it once. They don't have to bake it in 25 silos over and over and over again. >> Matt, the reason why we're talking about this is interesting, 'cause you know what this points out, in my opinion, it's my opinion. This points out that we're talking about content as a word means that you guys were on the cutting edge of new paradigms, which is content, it's essentially code, but it's addressable, community it's being shared. Someone wrote the code and it's a whole 'nother level of thinking. This is kind of a platform automation. I get it. So give us your thoughts because this is a critical component because the origination of the content, the code, I mean, I love it. Content is, I've always said content, our content should be code. It's all data, but this is interesting. This is the cutting edge concept. Could you explain what it means from your perspective? >> This is about building communities around that content, right? Like it's that sharing that didn't exist before, like Robyn mentioned, like, you know, you shouldn't have to build the same thing a dozen times or 100 times, you should be able to leverage the capabilities of experts and people who understand that section of automation the best, like I might be an expert in one field or Robyn's an expert in another field, we're automating in the same space. We should be able to bring our own expertise and resources together. And so this is what that content is. Like, I'm an expert in one, you're an expert in another, let's bring them together as part of our automation community and share them so that we can use them iterate on them and build on them and just constantly make them better. >> And the concepts are consumption, there's consumption of the content. There's the collaboration of the content. There's the sharing, all this, and there's reputation, there's expertise. I mean, it's a multi sided marketplace here, isn't it? >> Yeah. I read a article, I don't know, a year or two ago that said, we've always evolved in the technology industry around, if you have access to this, first it was the mainframes. Then it was, whatever, personal computers, the cloud, now it's containers, all of this, but, once everybody buys that mainframe or once everybody levels up their skills to whatever the next thing is that you can just buy, there's not much left that actually can help you to differentiate from your competitors, other than your ability to actually leverage all of those tools. And if you can actually have better collaboration, I think than other folks, then that is one of those points that actually will get you ahead in your digital transformation curve. >> I've been harping on this for a while. I think that cloud native finally has gone, when I say "mainstream" I mean like on everyone's mind, you look at the container uptake, you're looking at containers. We had IDC on, five to 10% of the enterprises are containerizing. That's huge growth opportunity. The IPO of, say, Snowflake's on Amazon. I mean, how does this happen? That's a company that's went public, It's the most valuable IPO in the history of IPOs on Wall Street. And it's built on Amazon, it has its own cloud. So it's like, I mean, this points to the new value that's being created on top of these new cloud native architectures. So I really think you guys are onto something big here. And I think you're starting to see this, new notions of how things are being rethought and reimagined. So let's keep it, while I've got you guys here real quick, Ansible 2.1 community release. Tell us more about the updates there. >> Oh, 2.10, because, yeah. Oh, that's fine. I know I too have had, I'm like, "Why do we do that?" But it's semantic versioning. So I am more accustomed to this now, it's a slightly different world from when I worked on Fedora. You know, I think the big highlight there is really collections. I mean, it's collections, collections, collections. That is all the work that we did, it's under the hood, over the hood, and really, how we went from being all in one repo to breaking things out. It's a big line for, we're advancing both the tool and also advancing the community's ability to actually collaborate together. And, you know, as folks start to actually use it, it's a big change for them potentially in how they can actually work together in their organizations using Ansible. One of the big things we did focus on was ensuring that their ease of use, that their experience did not change. So if they have existing Ansible stuff that they're running, playbooks, mod roles, et cetera, they should be able to use 2.10 and not see any discernible change. That's all the under the hood. That was a lot of surgery, wasn't it, Matt? Serious amounts of work. >> So Matt, 2.10, does that impact the release piece of it for the developers and the customers out there? What does it change? >> It's a good point. Like at least for the longer term, this means that we can focus on the Ansible core experience. And this is the part that we didn't touch on much before now with the collections pieces that now when we're fixing bugs, when we're iterating and making Ansible as an engine of automation better, we can do that without negatively impacting the automation that people actually use. We could focus on the core experience of actually automating itself. >> Execution environments, let's talk about that. What are they, are they being used in the community today? What do you guys react to that? >> We're actually, we're sort of in the middle of building this right now. Like one of the things that we've struggled with is when you, you need to automate, you need this content that we've talked about before. But beyond that, you have the system that sits underneath the version of Linux, the kernel that you're using, going even further, you need Python dependencies, you need library dependencies. These are hard and complicated things, like in the Ansible Tower space, we have virtual environments, which lets you install those things right alongside the Ansible Tower control plane. This can cause a lot of problems. So execution environments, they take those dependencies, the unit that is the environment that you need to run your automation in, and we're going to containerize it. You were just talking about this from the containerization perspective, right? We're going to build more easily isolated, easy to use distinct units of environments that will let you run your automation. This is great. This lets you, the person who's building the content for your organization, he can develop it and test it and send it through the CI process all the way up through production, it's the exact same environment. You could feel confident that the automation that you're running against the libraries and the models, the version of Ansible that you're using, is the same when you're developing the content as when you're running it in production for your business, for your users, for your customers. >> And that's the Nirvana. This is really where you talk about pushing it to new limits. Real quick, just to kind of end it out here for Ansible 2020, AnsibleFest 2020. Obviously we're now virtual, people aren't there in person, which is really an intimate event. Last year was awesome. Had theCUBE set right there, great event, people were intimate. What's going on for what you guys have for people that obviously we got the videos and got the media content. What's the main theme, Robyn and Matt, and what's going on for resources that might be available for folks who want to learn more, what's going on in the community, can you just take a minute each to talk about some of the exciting things that are going on at the event that they should pay attention to, and obviously, it's asynchronous so they can go anywhere anytime they want, it's the internet. Where can they go to hang out? Is there a hang space? Just give the quick two second commercial, Robyn, we'll start with you. >> All right. Well of course you can catch the keynotes early in the morning. I look forward to everybody's super exciting, highly polite comments. 'Cause I hear there's a couple people coming to this event, at least a few. I know within the event platform itself, there are chat rooms for each track. I myself will be probably hanging out in some of the diversity and inclusion spaces, honestly, and I, this is part of my keynote. You know, one of the great things about AnsibleFest is for me, and I was at the original AnsibleFest that had like 20 people in Boston in 2013. And it happened directly across the street from Red Hat Summit, which is why I was able to just ditch my job and go across the street to my future job, so to speak. We were... Well, I just lost my whole train of thought and ruined everything. Jeez. >> We got that you're going to be in the chat rooms for the diversity and community piece, off platform, is there a Slack? Is there like a site? Anything else? 'Cause you know, when the event's over, they're going to come back and consume on demand, but also the community, is there a Discord? I mean, all kinds of stuff's going on, popping up with these virtual spaces. >> One thing I should highlight is we do have the Ansible Contributor Summit that goes on the day before AnsibleFest and the day after AnsibleFest. Now, normally this is a pretty intimate event with the large outreach that we've gotten with this Fest, which is much bigger than the original one, much, much, much bigger, we've, and signing up for the contributor summit is part of the registration process for AnsibleFest. So we've actually geared our first day of that event to be towards new or aspiring contributors rather than the traditional format that we've had, which is where we have a lot of engineers, and can you remember sit down physically or in a virtual room and really talk about all of the things going on under the hood, which is, you know, can be intimidating for new people. Like "I just wanted to learn about how to contribute, not how to do surgery." So the first day is really geared towards making everything accessible to new people because turns out there's a lot of new people who are very excited about Ansible and we want to make sure that we're giving them the content that they need. >> Think about architects. I mean, SREs are jumping in, Matt, you talked about large scale. You're the chief architect, new blood's coming in. But give us an update on your perspective, what people should pay attention to at the event, after the event, communities they could be involved in, certainly people want to tap into you are an expert and find out what's going on. What's your comment? >> Yeah, you know, we have a whole new session track this year on architects, specifically for SREs and automation architects. We really want to highlight that. We want to give that sort of empowerment to the personas of people who, you know, maybe you're not a developer, maybe you're not, operations or a VP of your company. You're looking at the architecture of automation, how you can make our automation better for you and your organization. Everybody's suffered a lot and struggled with the COVID-19. We're no different, right? We want to show how automation can empower you, empower your organization and your company, just like we've struggled also. And we're excited about the things that we want to deliver in the next six months to a year. We want you to hear about those. We want you to hear about content and collections. We want you to hear about scalability, execution environments, we're really excited about what we're doing. You know, use the tools that we've provided in the AnsibleFest event experience to communicate with us, to talk to us. You can always find us on IRC via email, GitHub. We want people to continue to engage with us, our community, our open source community, to engage with us in the same ways that they have. And now we just want to share the things that we're working on, so that we can all collaborate on it and automate better. >> I'm really glad you said that. I mean, again, people are impacted by COVID-19. I got, it sounds like all channels are open. I got to say of all the communities that are having to work from home and are impacted by digital, developers probably are less impacted. They got more time to gain, they don't have to travel, they could hang out, they're used to some of these tools. So I think I guess the strategy is turn on all the channels and engage in new ways. And that seems to be the message, right? >> Yeah, exactly. >> Alright, Robyn Bergeron, great to see you again, Matt Jones, great to chat with you, chief architect for Ansible Automation Platform and of course, Robyn senior manager for the community team. Thanks so much for joining me today. I appreciate it. >> Thank you so much. >> Okay. It's theCUBE's coverage. I'm John Furrier, your host. We're here in the studio in Palo Alto. We're virtual. This is theCUBE virtual with AnsibleFest virtual. We're not face to face. Thank you for watching. (calm music)

(slow music) >> From around the globe. It's the cube with digital coverage of Red Hat Summit 2020 brought to you by Red Hat. >> Welcome back. This is the cubes coverage of a Red Hat Summit 2020. The event happening digitally this year. We are bringing in Red Hat executives, customers and partners from where they are around the globe. And happy to welcome back to the program. One of our cube alumni. Robin Bergeron is the senior principal community architect with Ansible part of Red Hat. Robin, great to see you. Thanks so much for joining us. So we've got the community coming together even while we're apart. >> Indeed. That's what we're good at. So, I'm glad to be back here again with you all. So, hello. >> All right. So, Robin, we caught up with you last at AnsibleFest of course Red Hat Summit. So much community activity that goes on. The Ansible, community is a big piece of summit even though they also have, the separate AnsibleFest. So just give us a little bit update what's happening in your world and in the community. >> Well. I hate to say it's a, "it's a big wide world" because it sounds very cliche, but the Ansible world is fairly big. I don't know if, let's see, we talked, lasted, AnsibleFest and that was in September in Atlanta, is that correct? >> Sounds right. Yep. >> I believe so. So right around that time was when GitHub released their annual list of, they have a report called the Octoverse they publish every year, in conjunction with their annual event. And one of their metrics they have on that list is, most active projects. So, we clocked in at the number ninth most active project on Github this past year. And that's out of, I've lost count of github, like number of projects. It's not quite the, United States national debt status, but it's a, like a hundred million repositories or something like that. So we're the number nine most active repository this year. And I believe we are one of two projects who's been on that list every year since 2016 I want to say. So, yeah, we're at 5900 contributors right now. So it's, all over the globe. A lot of people keeping us very busy. I guess that and fact it's so busy and we talked about collections a bit when we were at AnsibleFest this past year and it's been a thing that we've been talking about continuously in Ansible community and also, as part of Red Hats product line for a while and we've actually now gotten to the point of sort of splitting out the Ansible repository. Ansible is going to continue to be the, you a car and you look under the engine and there's like the things that make the car run. >> Ansible base, separate from the windshield wipers and all the ad-ons and all the cool stuff that you actually, want to get when you get a car. And that stuff is actually getting split out into Ansible collections that we'll have or repository that's actually more managed by the community, which will empower them to be able to make more decisions for us to be able to get things done, more rapidly. Cause in the past it's always been a really a tug of war between, work and github have always been very respectful about, how the balances between community and product because obviously without a community you don't have a product. And this is a obviously a method that Red Hat has sort of nailed down. I guess IBM really liked the idea. So here we are. But we're really looking forward to, right now we've got a handful of contributors who are adding new modules into this new repo. But, they're also helping us work out all the kinks in the contributor process and how it works that way. Once we opened for business, since we've got several thousand contributors, we don't say, open for business and then have everybody comes running into a glass wall like it and then all on the floor, right? We want the doors to be open. We want the, registers so to speak to be processing things. We want, all the box to be working, all of the, all of the magic to be happening just as it is, as it has in past. But, this time with a little bit more empowerment to the community, that's on a work progress for it was like forever, but, nine months, and here in the next few weeks that will be open for business and we're hoping that, by the time the AnsibleFest rolls around, that will be part of the two, part and parcel to the 2.10 release. And, we're hoping that, even though under the hood for contributors, that's changed. We believe we'll be very transparent brand eaters, which has been one of the most important things for us because, we don't like to break people. That's, >> yeah, >> {Robin] Glad yeah >> Absolutely Robin. So it was one of the key things a announced at a AnsibleFest last year. Anybody that knows the software world is the traditional release train. Get on that train. Got to make sure you get your feature in there. But for a solution like Ansible, which as you said, has a lot of partners and it's a very big ecosystem. If you have to worry about how much stuff do I get shoved into one release, it's a little bit limiting. So you break those pieces up more like the, containers, that go on the train and you can make sure that you're adding and, doing the various pieces as they go. So maybe >> Yeah >> not the perfect analogy. >> Yeah. >> But very important so, Robin, as you've been going through this, I'm wondering, what feedback are you getting from the contributors there? and how about as you said, very active community. We know if anybody you know, says something, you got, the crowd and the wisdom coming in and giving you ideas. But, how do you balance that? You're not going to have everybody be happy about every decision, but making sure that the ultimate release train, does the job and delivers the overall solution. >> Yes. What color are we going to paint? Paint our bike shed. Right? Like the yak for circling. So it's, I don't want to to say it's been mixed, it's, you know, we, I can, I compare and contrast this, one of my, previous roles was being the newer project leader, right. And, which is, as we know the upstream, for Red Hat enterprise Linux, and its some of the, Linux and, a lot of the Linux distributions have been around for forever. Back when there were like, I don't know. 10, 15 opensource projects that anybody at all, could contribute to. Now as we can see looking on, github and many other places get lab, open dev. There's a, you name it, there's a gazillion opensource projects out there. People aren't always as attached to, I don't want to say attached, coz that sounds, terrible, but open source has become such a norm people are just very used to, there's something wrong. I'm going to submit it, I'm going to hope it gets accepted, but I'm going to move on with my life because I also have all these other places that I can also contribute, right. That said, we do have, a significant number of compute of contributors who have been with us back since Ansible started. Some of those folks go back with us to Fidor days, on Linux days on and on and on. Some of them, some folks I have concerns, they do like that this is the opportunity to give them more empowerment to figure out better ways to run the, contributor process. I think the number one thing that everybody's been concerned about is what diseases your experience going to be. And I think that's a testament to, just the power of our community is that, people aren't just concerned about how am I going to get my stuff in and your stuff in and like the tug of war of like, is one person can get something else in before someone else. Everybody's very concerned about is this going to still work for the end users? Is this going to disrupt them? Because it's a change under hood. Are they going to have to change all their playbooks and all of their, rules and everything that they have. And right now the goal is, it should be transparent. Anything that you have written right now, you should continue work, you shouldn't notice. Once we get your 3.O our goal is to ramp people up into harnessing the power of collections. But first we need to get the collections, infrastructure in place, before we get in. Start giving them to artists the power of collections. You can't just flip the switch and be like, hi . So it used to be this way, now we have collections and now you've got to redo everything, right. Because that's-- you still have the opportunity because it's open source. We'll have this window where we can still find all the bugs and get that re rapid feedback, which means, once we roll out, Red Hat Ansible automation platform, the next version. I'm not going to say an AnsibleFest. That would be shocking, right? We never do announcements at events. But, whenever that product comes out, we want to make sure, that power of open source and, having that rapid feedback loop, ensures that, what we end up, we'll bring to customers, winds up being solid, but I believe it will be very, very solid for contributors because or, and, a community. There's, because, a significant number of our contributors are community users and they have that in their own interest in mind. And we've seen that not just from, I'm a community user at a university, but all of our partners are actually participating in the community as well. And there, just painting and chatting and we had a, we had planned to have a European as well contributor summit, which is a thing we normally run in combination or the day before AnsibleFest. and we had planned that for Sweden. I was so excited. I was going to go to Gothenburg. I hear it's a charming little town, except, when we are all stuck in, the a world that we are in currently. so we ran that virtually and a lot of our longterm contributors are actually from Europe. So that was really exciting except for me, cause I had to get up 8 Am but it was still nice to see them all. So we had, 50 some odd folks pop in over the course of, that day. And we talked through elections and debated and, got some demos from folks. Had some folks talk through some specific collections, folks talking about AWS and some of the networking things. So, yeah it was nice to see everyone. I was sad that it wasn't in Gothenburg. But it is what it is. I'm going to roll. >> So Robin, I think back to 2019 an automation, was right at the top of a hot topics. When I talk to practitioners out there, many conferences I went to, not just of course Ansible test, which focus on it, but many other shows and events. Well when you talk to people about key initiatives, its in a really leveraging automation, something that I've heard talked about my entire career, but really it feels like the last painful of years and people are much more serious about it. You know, you referenced the times that we live in right now, we're unprecedented global pandemics. So I'm not saying that, somebody, everybody all of a sudden woke up and say, Oh my gosh, I have to work from home and I need to be smarter. Let me finally use this automation that I've been hearing about all these years. But why don't you bring us into, what is happening today, what you are hearing customers, because automation obviously is a critical piece of what everybody is doing and probably just, shines a light on it even more. Now that we need to make sure that people are being efficient and still being able to deal with their lives while everything else is going on. >> Yeah. It's interesting because some of is, as well as used. Yeah, there's actually a, there's the dependency graph that you can look at on github and it will tell you how many other things in github are actually depending on the Ansible. It's, I can't even remember the number. It's a very large number, like tens of thousands of things as I recall. Disclaimer, my memory is terrible sometimes. I believe it was in the tens of thousands of things. Lots of people use Ansible and it's almost like probably not quite as popular as, the uses Docker container to get started, but, venture to guess it might be a number to that. Type this Ansible thing and this thing will magically come up. Right. For folks that are, in a traditional IT department, just trying to get along, day to day right now who are, they're like me. They're at home, they're with their spouse, they're sharing an office. They're also homeschooling their kids if they got out of bed. Hopefully we all have enough bandwidth. For those folks it's, I'm just glad that I continue to have this Ansible thing, they're using Ansible tower, they're glad that they can still manage to figure out how to collaborate their coworkers in that type of environment. For all the folks out there who are doing, research or trying to set up any type of infrastructure anywhere to related to this, I don't care if it's a, grocery store or you're a research laboratory, whatever it is. Last thing you want to do is spend five hours, be like, oh God okay, let me get out my manual. Where did I, it's hey, there's an Ansible. Excellent, I can type this Ansible thing in. And if for some reason it gets hung up. We have folks on IRC, we have, there's folks on stack overflow . There folks literally everywhere. You can ask a question on Twitter and It's a Pretty large, friendly, global community of people who have plenty of answers. And that's, I can't say we're like, hey, we solved everything, but we got all the >> stuff out of the way so that people can actually solve all of their, they can get down to what's actually important for them. And so that, that's always been one of the most redeeming things about Ansible that it's, for me, it's, the thing that I work on is, it's easy and it helps people solve their problems and gets all there, stuff out of the way so that they can concentrate on what's actually important to them. So I like to think, it's most important to them. And I know it is, but it's interesting seeing how things change, as people are like, are you going to teach a bunch of people Ansible now? And it's like, well, if they're in need of a job, there are a lot of online resources for that. But if they're just trying to get through their job, like everybody's sort of in a don't rock the boat position. Like if I can get a little bit ahead, that's cool. If I've already got a bunch of stuff automated Yes. That's one less thing that I have to worry about right now and that's all we can really hope for at this moment. >> Yeah, great stuff Robin. One of the high point always is seeing, the value and support of the community and as you said, it's something that we definitely see highlighted up out there. All right, Robyn Bergeron, greatest as always to catch up with you. Thank you so much. I'm sure you know so many community activities that people will be able to participate in. This week at Red Hat Summit, even though we're, all doing it remotely, >> and the >> yeah >> challenges there. >> Glad I, great uni central area city. You can come on, come on by and see all of the, various Red Hat open source communities doing their thing. >> All right, watch lots more coverage from Red Hat Summit coming at you. I'm Stu Miniman and always, thank you for watching, the cube (slow music)

>>live from Atlanta, Georgia. It's the Q covering answerable best 2019. Brought to you by Red hat. >>Welcome back, everyone to the Cube. Live coverage in Atlanta, Georgia for answerable fest. This is Red Hats Event where all the practices come together. The community to talk about automation anywhere. John Kerry with my coast to Minutemen, our next two guests arrive. And Bergeron, principal community architect for answerable now Red Hat and Greg Dankers Berg, senior director, Community Ansel's. Well, thanks for coming on. Appreciate it. >>Thank you. >>Okay, So we were talking before camera that you guys had. This is a two day event. We're covering the Cube. You guys have an awful fast, but you got your community day yesterday. The day before the people came in early. The core community heard great things about it. Love to get an update. Could you share just what happened yesterday? And then we'll get in some of the community. Sure. >>We s o uh, for all of our answer professed for a while now we've started them with ah, community contributor conference. And the goal of that conference is to get together. Ah, lot of the people we work with online right people we see is IRC nicks or get hub handles rights to get them together in the same room. Ah, have them interact with, uh, with core members of our team. Uh, and that's where we really do, uh, make a lot of decisions about how we're gonna be going forward, get really direct feedback from some of our key contributors about the decisions were making The things were thinking about, uh, with the goal of, you know, involving our community deeply in a lot of decisions we make, that's >>a working session, meets social, get together. That's >>right, Several working sessions and then, you know, drinks afterward for those who want the drinks and just hang out time that >>way. Drinks and their last night was really good. I got the end of it. I missed the session, but >>they have the peaches, peaches, it on the >>table. That was good. But this is the dynamic community. This is one things we notice here. Not a seat open in the house on the keynote Skinny Ramon Lee, active participant base from this organic as well Be now going mainstream. How >>you >>guys handling it, how you guys ride in this way? Because certainly you certainly do. The communities which is great for feedback get from the community. But as you have the commercial eyes open sores and answerable, it's a tough task. >>Well, I'd like to think part of it is, I guess maybe it's not our first rodeo. Is that what we'd say? I mean, yeah, uh, for Ansel. I worked at ELASTICSEARCH, uh, doing community stuff. Before that, I worked at Red Hat. It was a fedora. Project leader, number five. And you were Fedora project Leader. What number was that? Number one depends >>on how you count, but >>you're the You're the one that got us to be able to call it having a federal project leader. So I sort of was number one. So we've been dealing with this stuff for a really long time. It's different in Anselm that, you know, unlike a lot of, you know, holds old school things like fedora. You know, a lot of this stuff is newer and part of the reason it's really important for us to get You know, some of these folks here to talk to us in person is that you know especially. And you saw my keynote this morning where they talked about we talked about modularity. Lot of these folks are really just focused on. They're one little bit and they don't always have is much time. People are working in lots of open source projects now, right, and it's hard to pay deep attention to every single little thing all the time. So this gives them a day of in case you missed it. Here's the deep, dark dive into everything that you know we're planning or thinking about, and they really are. You know, people who are managing those smaller parts all around answerable, really are some of our best feedback loops, right? Because they're people who probably wrote that model because they're using it every single day and their hard core Ansel users. But they also understand how to participate in community so we can get those people actually talking with the rest of us who a lot of us used to be so sad. Men's. I used to be a sis admin, lots of us. You know. A lot of our employees actually just got into wanting to work on Ansel because they loved using it so much of their jobs. And when you're not, actually, since admitting every day, you you lose a little bit of >>the front lines with the truth of what's around. Truth is right there >>and putting all these people together in room make sure that they all also, you know, when you have to look at someone in the eye and tell them news that they might not like you have a different level of empathy and you approach it a little bit differently than you may on the Internet. So, >>Robin So I lived in your keynote this morning. You talked about answerable. First commit was only back in 2012. So that simplicity of that modularity and the learnings from where open source had been in the past Yes, they're a little bit, you know, what could answerable do, being a relatively young project that it might not have been able to dio if it had a couple of decades of history? >>Maybe Greg should tell the story about the funk project >>way. There was a There was a project, a tread hat that we started in 2007 in a coffee shop in Chapel Hill, North Carolina is Ah, myself and Michael the Han and Seth the doll on entry likens Who still works with this with us? A danceable Ah, and we we put together Ah, an idea with all the same underpinnings, right? Ah, highly modular automation tool We debated at the time whether it should be based on SSL or SS H for funk. We chose SSL Ah, and you know, after watching that grow to a certain point and then stagnates and it being inside of red Hat where, you know, there were a lot of other business pressures, things like that. We learned a lot from that experience and we were able to take that experience. And then in 2012 there there's the open source community was a little different. Open source was more acceptable. Get Hubbell was becoming a common plat platform for open source project hosting. And so a lot of things came together in a short pier Time All that experience, although, >>and also market conditions, agenda market conditions in 2007 Cloud was sort of a weird thing that not really everyone was doing 2012 rolls around. Everyone has these cloud images and they need to figure out how to get something in it. Um, and it turns out that Hansel's a really great way to actually do that. And, you know, even if we had picked SS H back in the beginning, I don't know, you know, not have had time projects grow to a certain point. And I could point a lots of projects that were just It's a shame they were so ahead of their time. And because of that, you know, >>timing is everything with the key. I think now what I've always admired about the simplicity is automation requires that the abstract, the way, the complexities and so I think you bring a cloud that brings up more complexity, more use cases for some of the underlying paintings of the plumbing. And this is always gonna This is a moving train that's never going to stop. What was the feedback from the community this year around? As you guys get into some of these analytical capabilities, so the new features have a platform flair to it. It's a platform you guys announced answerable automation platform that implies that enables some value. >>You know, I >>think in >>a way. We've always been a platform, right, because platform is a set of small rules and then modules that attached to it. It's about how that grows, right? And, uh, traditionally, we've had a batteries included model where every module and plug in was built to go into answerable Boy, that got really big bright and >>we like to hear it. I don't even know how many I keep say, I'll >>say 2000. Then it'll be 3000 say 3000 >>something else, a lot of content. And it's, you know, in the beginning, it was I can't imagine this ever being more than 202 150 batteries included, and at some point, you know, it's like, Whoa, yeah, taking care of this and making sure it all works together all the time gets >>You guys have done a great You guys have done a great job with community, and one of the things that you met with Cloud is as more use cases come, scale becomes a big question, and there's real business benefits now, so open source has become part of the business. People talk about business, models will open source. You guys know that you've been part of that 28 years of history with Lennox. But now you're seeing Dev Ops, which is you'll go back to 78 2009 10 time frame The only the purest we're talking Dev ops. At that time, Infrastructures Co was being kicked around. We certainly been covering the cubes is 2010 on that? But now, in mainstream enterprise, it seems like the commercialization and operational izing of Dev ops is here. You guys have a proof point in your own community. People talk about culture, about relationships. We have one guest on time, but they're now friends with the other guy group dowels. So you stay. The collaboration is now becoming a big part of it because of the playbook because of the of these these instances. So talk about that dynamic of operational izing the Dev Ops movement for Enterprise. >>All right, so I remember Ah, an example at one of the first answer professed I ever went thio There were there were a few before I came on board. Ah, but it was I >>think it was >>the 1st 1 I came to when I was about to make the jump from my previous company, and I was just There is a visitor and a friend of the team, and there was an adman who talked to me and said, For the first time, I have this thing, this playbook, that I can write and that I can hand to my manager and say this is what we're going to D'oh! Right? And so there was this artifact that allowed for a bridging between different parts of the organization. That was the simplicity of that playbook that was human readable, that he could show to his boss or to someone else in the organ that they could agree on. And suddenly there was this sort of a document that was a mechanism for collaboration that everyone could understand buy into that hadn't really existed before. Answerable existed after me. That was one of the many, you know, flip of the light moments where I was like, Oh, wow, maybe we have something >>really big. There were plenty of other infrastructures, code things that you could hand to someone. But, you know, for a lot of people, it's like I don't speak that language right? That's why we like to say like Ansel sort of this universal automation language, right? Like everybody can read it. You don't have to be a rocket scientist. Uh, it's, you know, great for your exact example, right? I'm showing this to my manager and saying This is the order of operations and you don't have to be a genius to read it because it's really, really readable >>connecting system which connects people >>right. It's fascinating to May is there was this whole wave of enterprise collaboration tools that the enterprise would try to push down and force people to collaborate. But here is a technology tool that from the ground up, is getting people to do that collaboration. And they want to do it. And it's helping bury some >>of those walls. And it's interesting you mention that I'm sure that something like slack is a thing that falls into that category. And they've built around making sure that the 20 billion people inside a company all sign up until somebody in the I T departments like, What do you mean? These random people are just everyone's using it. No one saving it isn't secure, and they all freak out, and, um, well, I mean, this is sort of, you know, everybody tells her friend about Ansel and they go, Oh, right, Tool. That's gonna save the world Number 22 0 wait, actually, yeah. No, this is This actually is pretty cool. Yeah, yeah, yeah, I get started. >>Well, you know, sometimes the better mouse trap will always drive people to that solution. You guys have proven that organic. What's interesting to me is not only does it keep win on capabilities, it actually grew organically. And this connective tissue between different groups, >>right? Got it >>breaks down that hole silo mentality. And that's really where I tease been stuck? Yes. And as software becomes more prominent and data becomes more prominent, it's gonna just shift more power in the hands of developer and to the, uh, just add mons who are now being redeployed into being systems, architects or whatever they are. This transitional human rolls with automation, >>transformation architect >>Oh my God, that's a real title. I don't >>have it, but >>double my pay. I'll take it. >>So collections is one of the key things talked about when we talk about the Antelope Automation platform. Been hearing a lot discussion about how the partner ecosystems really stepping up even more than before. You know, 4600 plus contributors out there in community, But the partners stepping up Where do you see this going? Where? Well, collections really catalyze the next growth for your >>It's got to be the future for us that, you know, there there were a >>few >>key problems that we recognize that the collections was ultimately the the dissolution that we chose. Uh, you know, one key problem is that with the batteries included model that put a lot of pressure on vendors to conform to whatever our processes were, they had to get their batteries in tow. Are thing to be a part of the ecosystem. And there was a huge demand to be a part of our ecosystem. The partners would just sort of, you know, swallow hard and do what they needed to d'oh. But it really wasn't optimized Tol partners, right? So they might have different development processes. They might have different release cycles. They might have different testing on the back end. That would be, you know, more difficult to hook together collections, breaks a lot of that out and gives our partners a lot of freedom to innovate in their own time. Uh, >>release on their own cycle, the down cycle. We just released our new version of software, but you can't actually get the new Ansel modules that are updated for it until answerable releases is not always the thing that you know makes their product immediately useful. You know, you're a vendor, you really something new. You want people to start using it right away, not wait until, you know answerable comes around so >>and that new artifact also creates more network effects with the, you know, galaxy and automation hub. And you know, the new deployment options that we're gonna have available for that stuff. So it's, I think it's just leveling up, right? It's taking the same approach that's gotten us this foreign, just taking out to, uh, to another level. >>I certainly wouldn't consider it to be like that. Partners air separate part of our They're still definitely part of the community. It's just they have slightly different problems. And, you know, there were folks from all sorts of different companies who are partners in the contributor summit. Yesterday >>there were >>actually, you know, participating and you know, folks swapping stories and listening to each other and again being part of that feedback. >>Maybe just a little bit broader. You know, the other communities out there, I think of the Cloud Native Computing Foundation, the Open Infrastructure Foundation. You're wearing your soul pin. I talk a little bit of our handsome How rentable plays across these other communities, which are, you know, very much mixture of the vendors and the end users. >>Well, I mean and will certainly had Sorry. Are you asking about how Ansel is relating to those other communities? Okay, Yeah, because I'm all about that. I mean, we certainly had a long standing sort of, ah fan base over in the open stacks slash open infrastructure foundation land. Most of the deployment tools for all of you know, all the different ways. So many ways to deploy open stack. A lot of them wound up settling on Ansel towards the end of time. You know, that community sort of matured, and, you know, there's a lot of periods of experimentation and, you know, that's one of the things is something's live. Something's didn't but the core parts of what you actually need to make a cloud or, you know, basically still there. Um And then we also have a ton of modules, actually unanswerable, that, you know, help people to operationalize all their open stack cloud stuff. Just like we have modules for AWS and Google Cloud and Azure and whoever else I'm leaving out this week as far as the C N. C f stuff goes, I mean again, we've seen a lot of you know how to get this thing up and running. Turns out Cooper Daddy's is not particularly easy to get up and running. It's even more complicated than a cloud sometimes, because it also assumes you've got a cloud of some sort already. And I like working on our thing. It's I can actually use it. It's pretty cool. Um, cube spray on. Then A lot of the other projects also have, you know, things that are related to Ansel. Now there's the answer. Will operator stuff? I don't know if you want to touch on that, but >>yeah, uh, we're working on. We know one of the big questions is ah, how do answerable, uh, and open shift slash kubernetes work together frequently and in sort of kubernetes land Open shift land. You want to keep his much as you can on the cluster. Lots of operations on the cluster. >>Sometimes you got >>to talk to things outside of the cluster, right? You got to set up some networking stuff, or you gotta go talk to an S three bucket. There's always something some storage thing. As much as you try to get things in a container land, there's all there's always legacy stuff. There's always new stuff, maybe edge stuff that might not all be part of your cluster. And so one of the things we're working on is making it easier to use answerable as part of your operator structure, to go and manage some of those things, using the operator framework that's already built into kubernetes and >>again, more complexity out there. >>Well, and and the thing is, we're great glue. Answerable is such great glue, and it's accessible to so many people and as the moon. As we move away from monolithic code bases to micro service's and vastly spread out code basis, it's not like the complexity goes away. The complexity simply moves to the relationship between the components and answerable. It's excellent glue for helping to manage those relationships between. >>Who doesn't like a glue layer >>everyone, if it's good and easy to understand, even better, >>the glue layers key guys, Thanks for coming on. Sharing your insights. Thank you so much for a quick minute to give a quick plug for the community. What's up? Stats updates. Quick projects Give a quick plug for what's going on the community real quick. >>You go first. >>We're big. We're 67 >>snow. It was number six. Number seven was kubernetes >>right. Number six out of 96 million projects on Get Hub. So lots of contributors. Lots of energy. >>Anytime. I tried to cite a stat, I find that I have to actually go and look it up. And I was about to sight again. >>So active, high, high numbers of people activity. What's that mean? You're running the plumbing, so obviously it's it's cloud on premise. Other updates. Projects of the contributor day. What's next, what's on the schedule. >>We're looking to put together our next contributor summit. We're hoping in Europe sometime in the spring, so we've got to get that on the plate. I don't know if we've announced the next answer will fast yet >>I know that happens tomorrow. So don't Don't really don't >>ruin that for everybody. >>Gradual ages on the great community. You guys done great. Work out in the open sores opened business. Open everything these days. Can't bet against open. >>But again, >>I wouldn't bet against open. >>We're here. Cube were open. Was sharing all the data here in Atlanta with the interviews. I'm John for his stupid men. Stayed with us for more after this short break.

>>Hi, everyone. And thanks for joining us today for our session on the 2020 Data Drivers Award winners. I'm excited to be here today with you. I'm a lease. Bergeron, vice president, product marketing for snowflake. Thes rewards are intended to recognize companies and individuals for using snowflakes, data cloud to drive innovation and impact in their organizations. Before we start our conversations, I want to quickly congratulate all of our award winners. First in the business awards are data driver of the year is Cisco. Our machine learning master is you Nipper, Our data sharing leader is Rakuten. Our data application of the year is observed and our data for good award goes to door dash for the individual and team awards. We first have the cost. Jane, Chief Digital officer of Paccar. We have a militiamen, director of cybersecurity and data science winning our data science Manager of the Year award at Comcast for a date. A pioneer of the year. We have Faisal KP, who's our senior manager of enterprise data Services at Pizza Hut. And lastly, we have our best data team going to McKesson, led by Jimmy Herff Data and Analytics platform leader Huge congratulations to all of these winners. It was very difficult to pick them amongst amazing set of nominations. So now let's dive into our conversations. We'll start with the data driver of the year. Representing Cisco today is Robbie. I'm a month do director data platform, data and analytics. >>Let me welcome everybody to the wonderful. Within a few years before Cisco used to be a company, you know, in making the decisions partly with the data and partly with the cuts. Because, you know, the data is told in multiple places the trading is not done right and things like that. So we, you know, really understood it. You know what was a challenge in the organism? By then we defined the data strategy on we put in a few plants in place, and it is working very well. But what is more important is basically how we provide the data towards data scientists and the data community in Cisco. I'm making them available in a highly available scalable on the elastic platforms. That's where you know, snowflake came into picture really very well for arrest, along with the other data strategies that we have had in place more importantly, data. Democratization was a key. You know, you along with the simplification, something technologies involved in the past. Our clients need to be worrying, laudable the technologies involved, you know, for example, we used to manage her before we make it. Snowflake Andi Snowflake, in a solve all of these problems for us with the ease on it. Really helping enabling a data data given ordinances in our >>system. In the data sharing leaders category, Rockhampton was our winner. We have mark staying trigger VP of analytics here to share their story. I >>wanna thank Snowflake for the award, and it's an honor to be a today. The ease of use of snowflake has allowed projects to move forward innovation to move forward in a way that it simply couldn't have done on old Duke systems or or or other platforms. And I think the truth the same is true for us on a lot of the similar topics, but also in the data sharing space, data sharing is a part off innovation. Like I think, most of the tech companies we work with certainly are business partners, merchants, but also with a range of other service providers and other technology vendors, um on other companies that we strategically share data with 2 May benefit of their service or thio to allow data modeling or advanced data collaboration or strategic business deals using the data and evaluated with the data on. But I think if you look Greece snowflake, you would see a lot of time and effort money going to just establishing that data connection that often involved substantial investments in technology data pipelines, risk evaluation, hashing, encrypt encryption. Security on what we found with snowflakes sharing functionality is that we can not eliminate those concerns, but that the technology just supports the ability to share data securely easily, quickly in a way that we could never do >>previously. Now we have a really inspiring winner of the data for good award door dash with their Project Dash Initiative here to speak about their work is act shot near Engineering manager >>Thank you sports to snowflake for recognizing us for this initiative. Eso For those of you who don't know, Dash, the logistics technology platform company that connects people with the best in their cities and Project Dash, our flagship social impact program, uses the door dash logistics platform to tackle the challenges like hunger and food waste. It was launched in 2018 on over the first two years in partnership with food recovery organizations, we powered the delivery off over £2 million of surplus food from businesses to hunger relief agencies across the U. S. And Canada. Andi simply do Toko with tremendous need has a much we were ableto power. The delivery often estimated 5.8 million meals to food insecure communities and frontline workers across 48 states on the 3.5 million off. These meals have been delivered since much. We do all of our analysis for our business functions from like product development to skills and social impact in snowflake On the numbers I just provided here actually have come from Snowflake on. We have used it to provide various forms of reporting, tow our government and non profit partners on this snowflake. We can help them understand the impact, analyzed friends and ensure complaints in cases where we are supporting efforts for agencies like FEMA, our USDA onda. Lastly, our team is really excited to be recognized by snowflake for using data for good. It has reminded us to continue doubling down on our commitment to using our product and expertise to partner with communities we operated. Thank you again. >>The winner of the machine Learning Master's word is unit for Energy. Viola Sarcoma Data Innovation leader is here on behalf of unit for >>Hello, everyone, Thanks for having me here. It's really a pleasure. And we were really proud to get this award. It means a lot for you. Nipper. It's huge recognition for our effort since last couple of years assed part of our journey and also a celebration off our success now for you. Newport. It would not be possible to start looking at Advanced Analytics techniques, not having a solid data foundation in place. And that's where we invested a lot in our cloud data platform in the cloud back by snowflake. Having this platform allowed us to employ advanced analytics techniques, combining data from Markit from fundamental data, different other sources of data like weather and extracting new friends, new signals that basically help us to partly or even in some cases fully automate some trading strategy. And we believe this will be really fundamental for for the future off raiding in our company and we will definitely invest in this area in the future. >>Our data application of the year is observed. Observers recognizes the most innovative, data driven application built on Snowflake and representing observed today is their CEO, Jeremy Burton. >>Let me just echo the thanks from the other folks on the coal. I mean snowflakes, separation of storage. Compute. I can't overstate what a really big deal it is. Um, it means that we can ingest in store data. Really? For the price of Amazon s three on board, we're in a category where vendors of historically charged for volume of data ingested. So you can imagine this really represents huge savings. Um, in addition, and maybe on a more technical note, snowflakes, elastic architectures really enables us to direct queries appropriately, based on the complexity of the query. So small queries or simple queries weaken director extra small warehouses and complex queries. We can direct, you know, for Excel. Or I think even a six x l is either there are on its way. The key thing there is that users they're not sitting around waiting for results to appear regardless of the query complexity. So I mean, really? The separation storage compute on the elastic architectures is a really big deal for us. >>Turning to the data Pioneer of the Year Award, I'm excited to be here with Faisal KP, senior manager of Enterprise Data Services from Pizza Hut. >>First of all, thank you, Snowflake, for giving this wonderful person. I think it means a lot for us in terms of validating what we're doing. I think we were one of the earlier adopters of Snowflake. We saw the vision of snowflake, you know, stories. Russell's computer separation on all the goodies, right? Right from back in 2017, I believe what snowflake enabled us is to actually get the scale with very little manpower, which is needed to man the entire system. So on the Super Bowl day, we have, you know, the entire crew literally a boardroom where the right from the CME, most of the CEOs to all the folks will be sitting and watching what is happening in the system. And we have to do a lot of real time analytics during that time. So with snowflake, you know, way used the elasticity of the platform we use, you know, platform you know their solutions, like snow pipe to basically automate the data ingestion coming through various channels, from the commas, from the stores, everything simultaneously. So as soon as the program is done, you know, we can scale scale down to our normal volume, which means we can, you know, way can save a lot. Of course. So definitely it snowflake has been game changer for us in terms of how we provide real time analytics. Our systems are used by thousands off restaurants throughout the country and, you know, by hundreds of franchisees. So the scale is something we have achieved with a lot of ability and success. >>In the category of data science Manager of the Year Award, we have a mission Min, director of cybersecurity and data science at Comcast. >>So thank you for having me and thank you for this wonderful award. So one of the biggest challenges you see in this other security spaces the tremendous amount of data that we have to compute every day to find the gold haystack. So one of the big challenges we overcame with by uniting snowflake was how do we go from like my other counterparts on the panel have said Theo operational overhead of maintaining a large data store and moved to more of results driven and data focused environment. And, you know, part of that journey was really the tremendous leadership. Comcast saying, You know, we want Thio through our day to day lives by relying less on operational work and Maura on answering questions. And so you know, over the last year we've really put Snowflake at the center of our ecosystem, knowing that it's elastic platform and its ability scale infinitely have given us the ability to dream big and use it to drop five cybersecurity. And while it's traditionally used for cybersecurity, we're starting to see the benefits right away and the beauty of the snowflake. Ecos, Miss. We're now able to enable folks that not traditionally have big data skills, but they have standards, sequel skills, and they could still work in the snowflake platform. So, you know, the transition to cloud has been very powerful for us as an organization. But I think the end story, the real takeaways, by moving our secretary operation to the cloud, we're now been able to enable more people and get the results they were looking for. You know, as other people have said fast, people hate to wait. So the scale of snowflake really shines. >>Yeah. Now, let's hear from our data Executive of the year. The Cost. Jane. Chief Digital Officer Packer. >>Thank you very much, Snowflake, for this really incredible recognition and honor of the work we're doing it back. Are we began. The first step in this process was for us to develop an enterprise Great data platform in the cloud capable off managing every aspect of data at scale. This this platform includes snowflake as our analytics data warehouse amongst many other technologies that we used for ingestion of data, data processing, uh, data governance, transactional, uh, needs and others. So this platform, once developed, has really helped us leverage data across the broad pack. Our systems and applications globally very efficiently and is enabling pack are, as a result to enhance every aspect. Selfish business with data. >>Ah, big congratulations again to all of the winners of the 2020 Data Drivers Awards. Thanks so much for joining us for a great conversation. And we hope that you enjoy the rest of the data cloud summit

(melodic music) >> Narrator: From around the globe, it's theCUBE. With digital coverage of AnsibleFest 2020. Brought to you by Red Hat. >> Hey, welcome back. Get ready, Jeff Frick here with theCUBE. Welcome back to our ongoing coverage of AnsibleFest 2020, it's virtual this year. But we've had a lot of great interviews and just coming off the keynotes, want to invite John Furrier in, he's been doing a lot of the keynotes and attending this thing for years. So John, first off, get your impressions of AnsibleFest 2020. >> Hey Jeff, great to cover this event. It's too bad we're not in person, we're virtual, theCUBE virtual AnsibleFest is virtual. Last year was in person, it's a really intimate event last year. And again with that theme, a similar vibe here for 2020 again, not face-to-face, but the content has that same kind of community vibe. Just some notable things just of the Keynote and some of the news is obviously last year they launched the Ansible Automation Platform. They've grown their collections community from five supported platforms to 50. And they launched the automation services catalog. So, you starting to see from the Keynotes, the positioning of Red Hat and Ansible. Just a series of announcements at AnsibleFest that include a lot integrations. Okay, and I think that's the key thing, obviously Kubernetes we heard at VMworld continued to take center stage in cloud native and CI/CD Pipeline. So yeah, with that, that's the vibe collections, collections, collections, and some new terminology, which could be confused depending on where you come from, but the word 'content' means something here and content is code and there's a collaboration aspect. And so, overall you seeing that positioning of agile, DevOps, security network automation and obviously community, a big part of Red Hat and Ansible is the core community and this future development environment of easy to consume, easy to code, easy to troubleshoot and built-in security and make it collaborative. That's the open-source ethos. And that's really the focus of AnsibleFest 2020 virtual. >> Yeah, I thought it was interesting. Richard Henshaw you know came out with, and it really reinforced the theme that automate and connect. And it's pretty interesting 'cause he talks about Ansible being the language of collaboration and how important collaboration is. And as we know with COVID and everybody working from home, now kind of the traditional methods of development teams getting together and a DevOps culture and doing daily stand-ups and having this kind of co-mingling of people isn't available anymore really as an option. So the pressure to collaborate is harder than ever before. So really an interesting twist for Ansible taking that tack that they are the language of collaboration. >> I liked his philosophy and some of his narrative around, he used to be a developer. They had a different group from their network-op brethren and they had different kind of siloed bill work together, it's all IT back in the day. But as things have become more cloud native, they have to integrate more and work together. And so this notion of collections is a big deal at Ansible. It's the idea of having these, these playbooks and having people be responsible for their playbooks and share those playbooks. They have a thing called content, which is how you can share these playbooks as content to be consumed and also collaborated and built on and with. But ultimately the theme around Ansible has always been a tool for automation. And now as a platform, the focus is making that automation platform wide across multiple environments, not just public cloud or on premises, it's edge, it's multicloud. So this idea of network automation has moved resources across the environments. And security is a big part of it. The automation platform for instance has a new 2.10 release, which brings back a huge amount of change releases where you don't have to be tied to the local host where you have this module updates are not directly tied to release cycles. Now this means that there's more availability of code. So network automation and updates, synchronous updates are huge. They talked about the VMware collection, IBM Z collections, all these things point to integrations. And that's really the focus of this integrate, this cloud native is, can I play well with others? This is again an extension to the community theme of open source. And if you're not integrating well in cloud native, you probably not going to be around longer. And that's a good theme for them. >> Yeah. So John, I wonder if you can unpack it a little bit, Robyn Bergeron and her Keynote went through this concept of the collection that I'm checking my notes here. They actually have three different types, they've got playbooks, roles, modules, PES, docks and plugins. And she talked about this is a way to basically aggregate information and share it in a bundle that other people can take full advantage of. >> Yeah, and I think that's the key of these collections. And I asked each of them when I was talking to them on camera prior to the event. And I say, what's the big theme for AnsibleFest this year? And they all said, Robyn was like collections, collections, collections. But the idea of writing code in a collection is all about Integry, so the VMware for instance is a great example. IBM Z, which is their mainframe piece. Ansible now part of Red Hat, and now Red Hat's part of IBM, you seeing that they now have more innovation going on with let's say mainframes. So the IBM Z integration allows Ansible to be compatible and bring a modern error to the mainframes. And this speaks to how people are working with these new roles and can leverage code in a new way. So, I think that's a real big thing about providing that last mile innovation and bringing it in other environments. Not just being on Ansible, but really integrating in with others. >> The other piece getting a lot attention John is OpenShift and the rule of OpenShift and the play of OpenShift. So how should people think about how OpenShift fits in this whole puzzle? >> I think OpenShift brings the Red Hat, a hybrid cloud automation piece to it, to Ansible, which is the, where the developers are playing with the CI/CD Pipeline. So the combination of, if you remember back in the days of OpenStack when we covered Red Hat and when OpenShift kind of really hit the scene, that was around private cloud. And then OpenShift adopted Kubernetes and that kind of cloud native vibe. And then since then the growth has been phenomenal. So when you take Red Hat's OpenShift, which is the cloud platform and you bring it to the automation platform of Ansible, it allows customers to have an easy to use capability to do hybrid and multicloud automation. And where this matters is where containers are getting traction. IDC was reporting numbers where only five to 15% of the enterprise, depending upon how you look at it are containerized, which means there's a huge surge of opportunity in these enterprises to bring containers into the cloud model. So for lift and shift and for modern workloads. So the OpenShift provides that path. So it's a nice compliment for the two together to work. So when we heard customers talking about the game system, one customer we talked about using Ansible Tower and the entire cloud, private cloud environment across data centers. So it's a good fit, automation with cloud. And honestly that's where the magic is. >> Right, right. The other piece that we keep hearing about over and over and over, and there's a play here as well as the edge, right. And really moving the compute closer to the place the data is generated and closer to the place that the data is consumed. But where do you see kind of the edge, the edge play here at AnsibleFest? (deep breath) >> Well this kind of ties into the earlier question about OpenShift and Ansible, that kind of automation meets hybrid cloud and addressing this like last mile aspect that Ansible provides in terms of load balancing, configuration, applications, application servers, pushing the apps to the edge. That's a big deal. And as 5G comes out and as edge becomes more, more important, you're going to need to have automation, the surface area of things (chuckles) to automate becomes critical. So the whole discussion is, it's larger scale, more devices, more code being shipped. This is where the engineers got to get involved early, bake security in from the beginning. But also have that automation capability, so it's not context switching between I ship some code, I got to troubleshoot it. They can all do it from within the Ansible platform. (hands rubs together) And that's where the traction with developers is. And this notion, this was the notion of sharing and collections and content become important because you have more people involved. And the betterment of the, of the collections and the crowd and the developers make sense. So edge is real and you got to have a software defined operational model. And you got to have a cloud piece like OpenShift, and you got to have an automation component like Ansible. So, this is a critical, whether you're talking space or 5G or inside an office or on a person, software defined operations will be the key. And that is a big trend that we're seeing right now. >> Yeah, so final question, John, what are you hoping to get out of this show, AnsibleFest 2020? Are there any open questions that you're hoping to get, get kind of answered or closed? Or what are you hoping to walk away with at the end of this event? >> Well, I'm curious to see how they handle the virtual event. Obviously the face to face is a very important intimate part of their community model. So I want to see how that goes. I want to see, I want to hear and look and squint through and connect the dots on the relationship with the Red Hat IBM acquisition, because Ansible is part of Red Hat and Red Hat is now (chuckles) part of IBM. So I think that's going to be a huge lift for Ansible, because once Ansible gets into the slipstream of IBM sales channels, that acceptance is going to be a really important factor for their growth. And then ultimately what's the developer trend? What new things are developers doing with automation that help customers have modern applications so that more, better apps can be deployed coming out of COVID, and as CXO's and the ivory tower of businesses change their business models, what new things are developers doing and how did that scale? So that's my, my key focus. >> All right, well that's great. Well, John, thanks for sharing your thoughts, your insight. And enough of us talking. Let's get to the tech athletes at AnsibleFest 2020. >> Awesome, thanks. >> Alright, he's John I'm Jeff. You're watching theCUBE with ongoing coverage of AnsibleFest 2020. Thanks for watching. We'll see you next time. (melodic music)

>> Announcer: Live from Atlanta, Georgia. It's theCUBE covering Ansible Fest 2019. Brought to you by Red Hat. >> Hello everyone, welcome to theCUBE. We are broadcasting live here, in Atlanta, Georgia. I'm John Furrier with Stu Miniman, my co-host, TheCUBE's 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, Stu, Ansible just finished their keynotes, keynote analysis, general availability of their new platform, the Ansible Automation Platform is the big news. It seems nuanced for the general tech practitioner out there, what's Ansible doing? Why are we here? We saw the rise of network management turn into observability as the hottest category in the cloud 2.0. companies going public, lot of M&A activity, observability is data driven. Automation's this other category that is just exploding in 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 Ansible and their show Automation for all, your analysis of the keynote, What's the most important thing going on here? >> So John, as you said automation is a super hot topic. I was just at the New Relic show talking about observability last week, we've got the Pager Duty show also going on this week. The automation is so critical. We know that IT can't keep up with things if they can't automate it. It's not just replacing some scripting. I loved in the keynote the talked about strategically thinking about automation. We've been watching the RPA companies talk about automation. There's lots of different automation, there's the right way to do it and another angle, John, that we love covering is 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. They use Open Source and everything that Red Hat does is 100% Open Source and that was core and key to what Ansible was and how it's created. This isn't a product pitch here, it is a community, John this is the 6th most active repository in GitHub. Out of over 100 million repositories out there, the 6th most active. 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 the Nusers. We heard JP Morgan in the keynote this morning, so a lot of participation there. But it is building out that sweep with a platform that you talked about, and we're going to spend a lot of time 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 Stu, the word they're using here is scale. This is something that you brought up the Open Core summit which I attended last week was the inaugural conference, lot of controversy. And this is a generational shift we are seeing 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 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 and 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 infrastructures code and as more stuff gets scaled up, as more stuff gets provisions, as more stuff gets built and created, the management and the controlling of the configurations, this has been real hotspot. This has been an opportunity and a problem. Anyone who's here, they're active because you know, 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, configuring standing up infrastructure, enabling applications and making it a competitive advantage. This is why they game is changing. We're starting to see platforms not tools. Your analysis, are they positioned? Was this keynote successful? >> Yeah, John. I really liked what Robyn Bergeron came out and talked about the key principles of what Ansible has done. It's simplicity, it's modularity and it's learning from Open Source. This project was only started in 2012. One of the things I always look at is in the old days you wanted to have that experience. There's not compressions algorithm for experience. Today, if I could start from day one today, and build with the latest tools, 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 acquired Ansible, to today in 2019, they're making huge growth and helping companies really leverage and mature their IT processes and move toward true business innovation with leveraging automation. >> Stu, this is not for the faint of heart either. These are rockstar DevOps infrastructure folks who are evolving in taking either network or infrastructure development to enable a software extraction layer for applications. It's not a joke either. I mean they've got some big names up on stage. One tweet I want to call out and get your reaction to. JP Morgan, his presentation the exec there, a tweet came out from Christopher Festa, "500 developers are working to automate business processes leading to among other benefits, 98% improvement in recovery times. What used to take 6 - 8 hours to recover, now takes 2 - 5 minutes." Christopher Festa. Stu. >> So John, that's what we wanted. How can we take these things that took hours and I had to go through this ticketing process and make that change. What I loved of what Chris from JP Morgan did, is he brought us inside and he said look, too make this change it took us a year of sorting through the security, the cyber, the control processes. We understand there's not just oh hey, lets sprinkle a little DevOps on everything and it's wonderful, we need to get buy in from the team, and it can spread between groups and change that culture. It's something that we've tracked in Red Hat for years and all of these environments. This is something that does require commitment, because it's not just John taking oh I scripted something, 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 going to help out business. We really need to make sure we understand what we're automating, the business value and what is going to be the ramifications of what we're doing. >> Well one of the things I want to share with folks watching is research that we did at SiliconAngle, theCUBE and Wikibon as part of our CUBE insights, Stu I know you're a part of this. We talked to a bunch of practitioners and customers, dozens of our community members and we found that observability we've just pointed out, has been an explosive category. That automation has been identified, and we're putting a stake in the ground, right here in theCUBE 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, here's the results of our survey. Automations quickly becoming a critical foundational element of the network as enterprises focus on multi-cloud, network being infrastructures, service and storage, and multi-cloud rapid development and deployment. Software to find everything's happening, pretty much we've been covering that on theCUBE. And most enterprises are just grappling with this concept and see opportunities. The benefit that people see in automation as we've discovered, Stu, are the following: 1. Focused on focused efforts for better results, efficiency, security is a top driver on all these things. You've got to have security built into the software, and then automation is creating job satisfaction for these guys. This is mundane tasks being automated away. So people are happier so job satisfaction. And finally, this is an opportunity to re-skill. Stu, these are the key bullets points that we've found in talking to our community. Your reaction to those results. >> Yeah John, I love that. Ultimately 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, how can I retool some of my sales force and get them engaged. And if you want to hire the millennials, they want to not be doing the drudgery, they want to do something where they feel that they are making a difference. You laid out a lot of good reasons why it would help and why people would want to get involved. John, you know I've talked to a number of government adgencys, when we changed that 40 year old process and now we're doing things faster and better, and that means I can really higher that next generation of workers because otherwise I wouldn't be able to higher them to just do things the old way. >> Stu this is about cloud 2.0 and this is about modernization. You mentioned Open Source, Open Core summit, that is a tell sign that Open Source is changing, the communities are changing, this is going to be a massive wave. Again, we've been chronicling this cloud 2.0, we coined that term, and we're trying to identify those key points, obviously observability, automation. But look, at the end of the day, You've go to have a focused effort to make the job go better you heard JP Morgan pointing out. Minutes versus hours. This is the benefit of infrastructure as code. At the end of the day employee satisfaction, the people that you want to hire 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 question Stu, What are you expecting for the next two days, we're going to be here for two days, what do you expect to hear from our guests. >> So John, one of the things I'm going to really look at is as you mentioned, infrastructure where this all started. So how do I use it to deploy a VM, Ansible's there. VMware, I've already talked to a number of people in the virtualization community, the love and embrace Ansible. We saw Microsoft up on stage, loving and embracing. As we move towards micro-service architectures, containerization and all of these cloud native deployments, how is Ansible and this community doing? Where are the stumbling blocks? To be honest, from what I hear coming into this, Ansible has been doing well. Red Hat has helped them grow even more, and the expectation is that IBM will help proliferate this even further. The traditional competitors to Ansible, you think about the Chefs and Puppets of the world, have been struggling with that cloud native world. John, I know I see Ansible when I go to the cloud shows, I hear customers talking about it. So Ansible seems to making that transition to cloud native well but there are other threats in the cloud native world. When I go to the serverless conference, I have not yet heard where this fits into the environment. So we always know that that next generation in technology, how will this automation move forward. >> As Red Hat starts getting much more proliferated in major enterprises with IBM, which will extend their lead even further in the enterprise, it's an opportunity for Ansible. The community angle is interesting. I want to get your community angle real quick So I saw a tweet from NetApp, their tagline at their booth is Simplify, automate, orchestrate. Sounds like they're leaning into the Kubernetes world, containers, you've got the start of thinking about software obstructions, this aint the provisioning hardware anymore. Whole new ball-game. Your assessment of Ansible's community presence, I mentioned that was a tweet from Red Hat, I mean NetApp. What's your take on the community angle here? >> John it's all about community. The GitHub's staff speak for themselves, this is very much a community event. Kudos to the team here, a lot on the diversity, inclusion effort, so really pushing those things forward. So John, something we always notice at the tech shows, the ratios of gender is way more diverse at an event like this. We know we see it in the developer communities, that there's more diversity in there, gender and ethnicity. >> Still a lot of guys though. >> Sure there is, by the way, when they took over this hotel, all of the bathrooms are gender-neutral, so you can use whatever bathroom you want there. >> I'll make sure I'm using the right pronouns when I'm saying hello to people. Stu, thanks for Commentary. Keynote analysis, I'm John Ferrier with Stu Miniman, breaking down why we are here? Why Ansible? Why is automation important? We believe automation will be a killer category, we're going to see a lot of growth here, and again the impact is with machine learning and A.I. This is where it all starts, automating the data, the technology and the configurations going to empower the next generation modern enterprise. More live coverage from Ansible Fest after this short break. (Upbeat techno 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