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

(bright music) >> Hello everyone. Welcome to theCUBE's coverage of AWS re:Invent 22. I'm John Furrier, host of theCUBE. Got some great coverage here talking about software supply chain and sustainability in the cloud. We've got a great conversation. Gunnar Hellekson, vice president and general manager at Red Hat Enterprise Linux and Business Unit of Red Hat. Thanks for coming on. And Adnan Ijaz, director of product management of commercial software services, AWS. Gentlemen, thanks for joining me today. >> It's a pleasure. (Adnan speaks indistinctly) >> You know, the hottest topic coming out of Cloud Native developer communities is slide chain software sustainability. This is a huge issue. As open source continues to power away and fund and grow this next generation modern development environment, you know, supply chain, you know, sustainability is a huge discussion because you got to check things out, what's in the code. Okay, open source is great, but now we got to commercialize it. This is the topic, Gunnar, let's get in with you. What are you seeing here and what's some of the things that you're seeing around the sustainability piece of it? Because, you know, containers, Kubernetes, we're seeing that that run time really dominate this new abstraction layer, cloud scale. What's your thoughts? >> Yeah, so I, it's interesting that the, you know, so Red Hat's been doing this for 20 years, right? Making open source safe to consume in the enterprise. And there was a time when in order to do that you needed to have a long term life cycle and you needed to be very good at remediating security vulnerabilities. And that was kind of, that was the bar that you had to climb over. Nowadays with the number of vulnerabilities coming through, what people are most worried about is, kind of, the providence of the software and making sure that it has been vetted and it's been safe, and that things that you get from your vendor should be more secure than things that you've just downloaded off of GitHub, for example. Right? And that's a place where Red Hat's very comfortable living, right? Because we've been doing it for 20 years. I think there's another aspect to this supply chain question as well, especially with the pandemic. You know, we've got these supply chains have been jammed up. The actual physical supply chains have been jammed up. And the two of these issues actually come together, right? Because as we go through the pandemic, we've got these digital transformation efforts, which are in large part, people creating software in order to manage better their physical supply chain problems. And so as part of that digital transformation, you have another supply chain problem, which is the software supply chain problem, right? And so these two things kind of merge on these as people are trying to improve the performance of transportation systems, logistics, et cetera. Ultimately, it all boils down to, both supply chain problems actually boil down to a software problem. It's very interesting. >> Well, that is interesting. I want to just follow up on that real quick if you don't mind. Because if you think about the convergence of the software and physical world, you know, that's, you know, IOT and also hybridcloud kind of plays into that at scale, this opens up more surface area for attacks, especially when you're under a lot of pressure. This is where, you know, you have a service area on the physical side and you have constraints there. And obviously the pandemic causes problems. But now you've got the software side. How are you guys handling that? Can you just share a little bit more of how you guys looking at that with Red Hat? What's the customer challenge? Obviously, you know, skills gaps is one, but, like, that's a convergence at the same time more security problems. >> Yeah, yeah, that's right. And certainly the volume of, if we just look at security vulnerabilities themselves, just the volume of security vulnerabilities has gone up considerably as more people begin using the software. And as the software becomes more important to, kind of, critical infrastructure. More eyeballs around it and so we're uncovering more problems, which is kind of, that's okay, that's how the world works. And so certainly the number of remediations required every year has gone up. But also the customer expectations, as I mentioned before, the customer expectations have changed, right? People want to be able to show to their auditors and to their regulators that no, in fact, I can show the providence of the software that I'm using. I didn't just download something random off the internet. I actually have like, you know, adults paying attention to how the software gets put together. And it's still, honestly, it's still very early days. I think as an industry, I think we're very good at managing, identifying remediating vulnerabilities in the aggregate. We're pretty good at that. I think things are less clear when we talk about, kind of, the management of that supply chain, proving the providence, and creating a resilient supply chain for software. We have lots of tools, but we don't really have lots of shared expectations. And so it's going to be interesting over the next few years, I think we're going to have more rules are going to come out. I see NIST has already published some of them. And as these new rules come out, the whole industry is going to have to kind of pull together and really rally around some of this shared understanding so we can all have shared expectations and we can all speak the same language when we're talking about this problem. >> That's awesome. Adnan, Amazon web service is obviously the largest cloud platform out there. You know, the pandemic, even post pandemic, some of these supply chain issues, whether it's physical or software, you're also an outlet for that. So if someone can't buy hardware or something physical, they can always get to the cloud. You guys have great network compute and whatnot and you got thousands of ISVs across the globe. How are you helping customers with this supply chain problem? Because whether it's, you know, I need to get in my networking gears and delay, I'm going to go to the cloud and get help there. Or whether it's knowing the workloads and what's going on inside them with respect to open source. 'Cause you've got open source, which is kind of an external forcing function. You've got AWS and you got, you know, physical compute stores, networking, et cetera. How are you guys helping customers with the supply chain challenge, which could be an opportunity? >> Yeah, thanks John. I think there are multiple layers to that. At the most basic level, we are helping customers by abstracting away all these data center constructs that they would have to worry about if they were running their own data centers. They would have to figure out how the networking gear, you talk about, you know, having the right compute, right physical hardware. So by moving to the cloud, at least they're delegating that problem to AWS and letting us manage and making sure that we have an instance available for them whenever they want it. And if they want to scale it, the capacity is there for them to use. Now then, so we kind of give them space to work on the second part of the problem, which is building their own supply chain solutions. And we work with all kinds of customers here at AWS from all different industry segments, automotive, retail, manufacturing. And you know, you see the complexity of the supply chain with all those moving pieces, like hundreds and thousands of moving pieces, it's very daunting. And then on the other hand, customers need more better services. So you need to move fast. So you need to build your agility in the supply chain itself. And that is where, you know, Red Hat and AWS come together. Where we can enable customers to build their supply chain solutions on platforms like Red Hat Enterprise Linux RHEL or Red Hat OpenShift on AWS, we call it ROSA. And the benefit there is that you can actually use the services that are relevant for the supply chain solutions like Amazon managed blockchain, you know, SageMaker. So you can actually build predictive analytics, you can improve forecasting, you can make sure that you have solutions that help you identify where you can cut costs. And so those are some of the ways we're helping customers, you know, figure out how they actually want to deal with the supply chain challenges that we're running into in today's world. >> Yeah, and you know, you mentioned sustainability outside of software sustainability, you know, as people move to the cloud, we've reported on SiliconANGLE here in theCUBE, that it's better to have the sustainability with the cloud because then the data centers aren't using all that energy too. So there's also all kinds of sustainability advantages. Gunnar, because this is kind of how your relationship with Amazon's expanded. You mentioned ROSA, which is Red Hat, you know, on OpenShift, on AWS. This is interesting because one of the biggest discussions is skills gap, but we were also talking about the fact that the humans are a huge part of the talent value. In other words, the humans still need to be involved. And having that relationship with managed services and Red Hat, this piece becomes one of those things that's not talked about much, which is the talent is increasing in value, the humans, and now you got managed services on the cloud. So we'll look at scale and human interaction. Can you share, you know, how you guys are working together on this piece? 'Cause this is interesting, 'cause this kind of brings up the relationship of that operator or developer. >> Yeah, yeah. So I think there's, so I think about this in a few dimensions. First is that it's difficult to find a customer who is not talking about automation at some level right now. And obviously you can automate the processes and the physical infrastructure that you already have, that's using tools like Ansible, right? But I think that combining it with the elasticity of a solution like AWS, so you combine the automation with kind of elastic and converting a lot of the capital expenses into operating expenses, that's a great way actually to save labor, right? So instead of like racking hard drives, you can have somebody do something a little more like, you know, more valuable work, right? And so, okay, but that gives you a platform. And then what do you do with that platform? You know, if you've got your systems automated and you've got this kind of elastic infrastructure underneath you, what you do on top of it is really interesting. So a great example of this is the collaboration that we had with running the RHEL workstation on AWS. So you might think, like, well why would anybody want to run a workstation on a cloud? That doesn't make a whole lot of sense. Unless you consider how complex it is to set up, if you have, the use case here is like industrial workstations, right? So it's animators, people doing computational fluid dynamics, things like this. So these are industries that are extremely data heavy. Workstations have very large hardware requirements, often with accelerated GPUs and things like this. That is an extremely expensive thing to install on-premise anywhere. And if the pandemic taught us anything, it's if you have a bunch of very expensive talent and they all have to work from home, it is very difficult to go provide them with, you know, several tens of thousands of dollars worth of workstation equipment. And so combine the RHEL workstation with the AWS infrastructure and now all that workstation computational infrastructure is available on demand and available right next to the considerable amount of data that they're analyzing or animating or working on. So it's a really interesting, it was actually, this is an idea that was actually born with the pandemic. >> Yeah. >> And it's kind of a combination of everything that we're talking about, right? It's the supply chain challenges of the customer, it's the lack of talent, making sure that people are being put to their best and highest use. And it's also having this kind of elastic, I think, OpEx heavy infrastructure as opposed to a CapEx heavy infrastructure. >> That's a great example. I think that illustrates to me what I love about cloud right now is that you can put stuff in the cloud and then flex what you need, when you need it, in the cloud rather than either ingress or egress of data. You just get more versatility around the workload needs, whether it's more compute or more storage or other high level services. This is kind of where this next gen cloud is going. This is where customers want to go once their workloads are up and running. How do you simplify all this and how do you guys look at this from a joint customer perspective? Because that example I think will be something that all companies will be working on, which is put it in the cloud and flex to whatever the workload needs and put it closer to the compute. I want to put it there. If I want to leverage more storage and networking, well, I'll do that too. It's not one thing, it's got to flex around. How are you guys simplifying this? >> Yeah, I think, so, I'll give my point of view and then I'm very curious to hear what Adnan has to say about it. But I think about it in a few dimensions, right? So there is a technically, like, any solution that Adnan's team and my team want to put together needs to be kind of technically coherent, right? Things need to work well together. But that's not even most of the job. Most of the job is actually ensuring an operational consistency and operational simplicity, so that everything is, the day-to-day operations of these things kind of work well together. And then also, all the way to things like support and even acquisition, right? Making sure that all the contracts work together, right? It's a really... So when Adnan and I think about places of working together, it's very rare that we're just looking at a technical collaboration. It's actually a holistic collaboration across support, acquisition, as well as all the engineering that we have to do. >> Adnan, your view on how you're simplifying it with Red Hat for your joint customers making collaborations? >> Yeah, Gunnar covered it well. I think the benefit here is that Red Hat has been the leading Linux distribution provider. So they have a lot of experience. AWS has been the leading cloud provider. So we have both our own points of view, our own learning from our respective set of customers. So the way we try to simplify and bring these things together is working closely. In fact, I sometimes joke internally that if you see Gunnar and my team talking to each other on a call, you cannot really tell who belongs to which team. Because we're always figuring out, okay, how do we simplify discount experience? How do we simplify programs? How do we simplify go to market? How do we simplify the product pieces? So it's really bringing our learning and share our perspective to the table and then really figure out how do we actually help customers make progress. ROSA that we talked about is a great example of that, you know, together we figured out, hey, there is a need for customers to have this capability in AWS and we went out and built it. So those are just some of the examples in how both teams are working together to simplify the experience, make it complete, make it more coherent. >> Great, that's awesome. Next question is really around how you help organizations with the sustainability piece, how to support them simplifying it. But first, before we get into that, what is the core problem around this sustainability discussion we're talking about here, supply chain sustainability, what is the core challenge? Can you both share your thoughts on what that problem is and what the solution looks like and then we can get into advice? >> Yeah. Well from my point of view, it's, I think, you know, one of the lessons of the last three years is every organization is kind of taking a careful look at how resilient it is, or I should say, every organization learned exactly how resilient it was, right? And that comes from both the physical challenges and the logistics challenges that everyone had, the talent challenges you mentioned earlier. And of course the software challenges, you know, as everyone kind of embarks on this digital transformation journey that we've all been talking about. And I think, so I really frame it as resilience, right? And resilience at bottom is really about ensuring that you have options and that you have choices. The more choices you have, the more options you have, the more resilient you and your organization is going to be. And so I know that's how I approach the market. I'm pretty sure that's how Adnan is approaching the market, is ensuring that we are providing as many options as possible to customers so that they can assemble the right pieces to create a solution that works for their particular set of challenges or their unique set of challenges and unique context. Adnan, does that sound about right to you? >> Yeah, I think you covered it well. I can speak to another aspect of sustainability, which is becoming increasingly top of mind for our customers. Like, how do they build products and services and solutions and whether it's supply chain or anything else which is sustainable, which is for the long term good of the planet. And I think that is where we have also been very intentional and focused in how we design our data center, how we actually build our cooling system so that those are energy efficient. You know, we are on track to power all our operations with renewable energy by 2025, which is five years ahead of our initial commitment. And perhaps the most obvious example of all of this is our work with ARM processors, Graviton3, where, you know, we are building our own chip to make sure that we are designing energy efficiency into the process. And you know, the ARM Graviton3 processor chips, they are about 60% more energy efficient compared to some of the CD6 comparable. So all those things that also we are working on in making sure that whatever our customers build on our platform is long term sustainable. So that's another dimension of how we are working that into our platform. >> That's awesome. This is a great conversation. You know, the supply chain is on both sides, physical and software. You're starting to see them come together in great conversations. And certainly moving workloads to the cloud and running them more efficiently will help on the sustainability side, in my opinion. Of course, you guys talked about that and we've covered it. But now you start getting into how to refactor, and this is a big conversation we've been having lately is as you not just lift and shift, but replatform it and refactor, customers are seeing great advantages on this. So I have to ask you guys, how are you helping customers and organizations support sustainability and simplify the complex environment that has a lot of potential integrations? Obviously API's help of course, but that's the kind of baseline. What's the advice that you give customers? 'Cause you know, it can look complex and it becomes complex, but there's an answer here. What's your thoughts? >> Yeah, I think, so whenever I get questions like this from customers, the first thing I guide them to is, we talked earlier about this notion of consistency and how important that is. One way to solve the problem is to create an entirely new operational model, an entirely new acquisition model, and an entirely new stack of technologies in order to be more sustainable. That is probably not in the cards for most folks. What they want to do is have their existing estate and they're trying to introduce sustainability into the work that they are already doing. They don't need to build another silo in order to create sustainability, right? And so there has to be some common threads, there has to be some common platforms across the existing estate and your more sustainable estate, right? And so things like Red Hat Enterprise Linux, which can provide this kind of common, not just a technical substrate, but a common operational substrate on which you can build these solutions. If you have a common platform on which you are building solutions, whether it's RHEL or whether it's OpenShift or any of our other platforms, that creates options for you underneath. So that in some cases maybe you need to run things on-premises, some things you need to run in the cloud, but you don't have to profoundly change how you work when you're moving from one place to another. >> Adnan, what's your thoughts on the simplification? >> Yeah, I mean, when you talk about replatforming and refactoring, it is a daunting undertaking, you know, especially in today's fast paced world. But the good news is you don't have to do it by yourself. Customers don't have to do it on their own. You know, together AWS and Red Hat, we have our rich partner ecosystem, you know, AWS has over 100,000 partners that can help you take that journey, the transformation journey. And within AWS and working with our partners like Red Hat, we make sure that we have- In my mind, there are really three big pillars that you have to have to make sure that customers can successfully re-platform, refactor their applications to the modern cloud architecture. You need to have the rich set of services and tools that meet their different scenarios, different use cases. Because no one size fits all. You have to have the right programs because sometimes customers need those incentives, they need those, you know, that help in the first step. And last but not least, they need training. So all of that, we try to cover that as we work with our customers, work with our partners. And that is where, you know, together we try to help customers take that step, which is a challenging step to take. >> Yeah, you know, it's great to talk to you guys, both leaders in your field. Obviously Red Hats, I remember the days back when I was provisioning and loading OSs on hardware with CDs, if you remember those days, Gunnar. But now with the high level services, if you look at this year's reinvent, and this is kind of my final question for the segment is, that we'll get your reaction to, last year we talked about higher level service. I sat down with Adam Saleski, we talked about that. If you look at what's happened this year, you're starting to see people talk about their environment as their cloud. So Amazon has the gift of the CapEx, all that investment and people can operate on top of it. They're calling that environment their cloud. Okay? For the first time we're seeing this new dynamic where it's like they have a cloud, but Amazon's the CapEx, they're operating. So, you're starting to see the operational visibility, Gunnar, around how to operate this environment. And it's not hybrid, this, that, it's just, it's cloud. This is kind of an inflection point. Do you guys agree with that or have a reaction to that statement? Because I think this is, kind of, the next gen supercloud-like capability. We're going, we're building the cloud. It's now an environment. It's not talking about private cloud, this cloud, it's all cloud. What's your reaction? >> Yeah, I think, well, I think it's very natural. I mean, we use words like hybridcloud, multicloud, I guess supercloud is what the kids are saying now, right? It's all describing the same phenomena, right? Which is being able to take advantage of lots of different infrastructure options, but still having something that creates some commonality among them so that you can manage them effectively, right? So that you can have, kind of, uniform compliance across your estate. So that you can have, kind of, you can make the best use of your talent across the estate. I mean this is, it's a very natural thing. >> John: They're calling it cloud, the estate is the cloud. >> Yeah. So yeah, so fine, if it means that we no longer have to argue about what's multicloud and what's hybridcloud, I think that's great. Let's just call it cloud. >> Adnan, what's your reaction, 'cause this is kind of the next gen benefits of higher level services combined with amazing, you know, compute and resource at the infrastructure level. What's your view on that? >> Yeah, I think the construct of a unified environment makes sense for customers who have all these use cases which require, like for instance, if you are doing some edge computing and you're running WS outpost or you know, wavelength and these things. So, and it is fair for customer to think that, hey, this is one environment, same set of tooling that they want to build that works across all their different environments. That is why we work with partners like Red Hat so that customers who are running Red Hat Enterprise Linux on-premises and who are running in AWS get the same level of support, get the same level of security features, all of that. So from that sense, it actually makes sense for us to build these capabilities in a way that customers don't have to worry about, okay, now I'm actually in the AWS data center versus I'm running outpost on-premises. It is all one. They just use the same set of CLI, command line APIs and all of that. So in that sense it actually helps customers have that unification so that consistency of experience helps their workforce and be more productive versus figuring out, okay, what do I do, which tool I use where? >> Adnan, you just nailed it. This is about supply chain sustainability, moving the workloads into a cloud environment. You mentioned wavelength, this conversation's going to continue. We haven't even talked about the edge yet. This is something that's going to be all about operating these workloads at scale and all with the cloud services. So thanks for sharing that and we'll pick up that edge piece later. But for re:Invent right now, this is really the key conversation. How to make the sustained supply chain work in a complex environment, making it simpler. And so thanks you for sharing your insights here on theCUBE. >> Thanks, thanks for having us. >> Okay, this is theCUBE's coverage of AWS re:Invent 22. I'm John Furrier, your host. Thanks for watching. (bright music)

>>Hello, brilliant humans and welcome back to Las Vegas, Nevada, where we are live from the AWS Reinvent Show floor here with the cube. My name is Savannah Peterson, joined with Dave Valante, and we have a very exciting conversation with you. Two, two companies you may have heard of. We've got AWS and Red Hat in the house. Manu and Joel, thank you so much for being here. Love this little fist bump. Started off, that's right. Before we even got rolling, Manu, you said that you wanted this to be the best segment of, of the cubes airing. We we're doing over a hundred segments, so you're gonna have to bring the heat. >>We're ready. We're did go. Are we ready? Yeah, go. We're ready. Let's bring it on. >>We're ready. All right. I'm, I'm ready. Dave's ready. Let's do it. How's the show going for you guys real quick before we dig in? >>Yeah, I think after Covid, it's really nice to see that we're back into the 2019 level and, you know, people just want to get out, meet people, have that human touch with each other, and I think a lot of trust gets built as a functional that, so it's super amazing to see our partners and customers here at Reedman. Yeah, >>And you've got a few in the house. That's true. Just a few maybe, maybe a couple >>Very few shows can say that, by the way. Yeah, it's maybe a handful. >>I think one of the things we were saying, it's almost like the entire Silicon Valley descended in the expo hall area, so >>Yeah, it's >>For a few different reasons. There's a few different silicon defined. Yeah, yeah, yeah. Don't have strong on for you. So far >>It's, it's, it is amazing. It's the 10th year, right? It's decade, I think I've been to five and it's, it grows every single year. It's the, you have to be here. It's as simple as that. And customers from every single industry are here too. You don't get, a lot of shows have every single industry and almost every single location around the globe. So it's, it's a must, must be >>Here. Well, and the personas evolved, right? I was at reinvent number two. That was my first, and it was all developers, not all, but a lot of developers. And today it's a business mix, really is >>Totally, is a business mix. And I just, I've talked about it a little bit down the show, but the diversity on the show floor, it's the first time I've had to wait in line for the ladies' room at a tech conference. Almost a two decade career. It is, yeah. And it was really refreshing. I'm so impressed. So clearly there's a commitment to community, but also a commitment to diversity. Yeah. And, and it's brilliant to see on the show floor. This is a partnership that is robust and has been around for a little while. Money. Why don't you tell us a little bit about the partnership here? >>Yes. So Red Hand and AWS are best friends, you know, forever together. >>Aw, no wonder we got the fist bumps and all the good vibes coming out. I know, it's great. I love that >>We have a decade of working together. I think the relationship in the first phase was around running rail bundled with E two. Sure. We have about 70,000 customers that are running rail, which are running mission critical workloads such as sap, Oracle databases, bespoke applications across the state of verticals. Now, as more and more enterprise customers are finally, you know, endorsing and adopting public cloud, I think that business is just gonna continue to grow. So a, a lot of progress there. The second titration has been around, you know, developers tearing Red Hat and aws, Hey, listen, we wanna, it's getting competitive. We wanna deliver new features faster, quicker, we want scale and we want resilience. So just entire push towards devs containers. So that's the second chapter with, you know, red Hat OpenShift on aws, which launched as a, a joint manage service in 2021 last year. And I think the third phase, which you're super excited about, is just bringing the ease of consumption, one click deployment, and then having our customers, you know, benefit from the joint committed spend programs together. So, you know, making sure that re and Ansible and JBoss, the entire portfolio of Red Hat products are available on AWS marketplace. So that's the 1, 2, 3, it of our relationship. It's a decade of working together and, you know, best friends are super committed to making sure our customers and partners continue successful. >>Yeah, that he said it, he said it perfectly. 2008, I know you don't like that, but we started with Rel on demand just in 2008 before E two even had a console. So the partnership has been there, like Manu says, for a long time, we got the partnership, we got the products up there now, and we just gotta finalize that, go to market and get that gas on the fire. >>Yeah. So Graviton Outpost, local zones, you lead it into all the new stuff. So that portends, I mean, 2008, we're talking two years after the launch of s3. >>That's right. >>Right. So, and now look, so is this a harbinger of things to come with these new innovations? >>Yeah, I, I would say, you know, the innovation is a key tenant of our partnership, our relationship. So if you look at from a product standpoint, red Hat or Rel was one of the first platforms that made a support for graviton, which is basically 40% better price performance than any other distribution. Then that translated into making sure that Rel is available on all of our regions globally. So this year we launched Switzerland, Spain, India, and Red Hat was available on launch there, support for Nitro support for Outpost Rosa support on Outpost as well. So I think that relationship, that innovation on the product side, that's pretty visible. I think that innovation again then translates into what we are doing on marketplace with one click deployments we spoke about. I think the third aspect of the know innovation is around making sure that we are making our partners and our customers successful. So one of the things that we've done so far is Joe leads a, you know, a black belt team that really goes into each customer opportunity, making sure how can we help you be successful. We launched and you know, we should be able to share that on a link. After this, we launched like a big playlist, which talks about every single use case on how do you get successful and running OpenShift on aws. So that innovation on behalf of our customers partners to make them successful, that's been a key tenant for us together as >>Well. That's right. And that team that Manu is talking about, we're gonna, gonna 10 x that team this year going into January. Our fiscal yield starts in January. Love that. So yeah, we're gonna have a lot of no hiring freeze over here. Nope. No ma'am. No. Yeah, that's right. Yeah. And you know what I love about working with aws and, and, and Manu just said it very, all of that's customer driven. Every single event that we, that he just talked about in that timeline, it's customer driven, right? Customers wanted rail on demand, customers want JBoss up in the cloud, Ansible this week, you know, everything's up there now. So it's just getting that go to market tight and we're gonna, we're gonna get that done. >>So what's the algorithm for customer driven in terms of taking the input? Because if every customers saying, Hey, I this a >>Really similar >>Question right up, right? I, that's what I want. And if you know, 95% of the customers say it, Jay, maybe that's a good idea. >>Yeah, that's right. Trends. But >>Yeah. You know, 30% you might be like, mm, you know, 20%, you know, how do you guys decide when to put gas on the fire? >>No, that, I think, as I mentioned, there are about 70,000 large customers that are running rail on Easy Two, many of these customers are informing our product strategy. So we have, you know, close to about couple of thousand power users. We have customer advisory booths, and these are the, you know, customers are informing us, Hey, let's get all of the Red Hat portfolio and marketplace support for graviton, support for Outpost. Why don't we, why are we not able to dip into the consumption committed spend programs for both Red Hat and aws? That's right. So it's these power users both at the developer level as well as the guys who are actually doing large commercial consumption. They are the ones who are informing the roadmap for both Red Hat and aws. >>But do, do you codify the the feedback? >>Yeah, I'm like, I wanna see the database, >>The, I think it was, I don't know, it was maybe Chasy, maybe it was Besos, that that data beats intuition. So do you take that information and somehow, I mean, it's global, 70,000 customers, right? And they have different weights, different spending patterns, different levels of maturity. Yeah. Do you, how do you codify that and then ultimately make the decision? Yeah, I >>If, I mean, well you, you've got the strategic advisory boards, which are made up of customers and partners and you know, you get, you get a good, you gotta get a good slice of your customer base to get, and you gotta take their feedback and you gotta do something with it, right? That's the, that's the way we do it and codify it at the product level, I'm sure open source. That's, that's basically how we work at the product level, right? The most elegant solution in open source wins. And that's, that's pretty much how we do that at the, >>I would just add, I think it's also just the implicit trust that the two companies had built with each other, working in the trenches, making our customers and partners successful over the last decade. And Alex, give an example. So that manifests itself in context of like, you know, Amazon and Red Hat just published the entire roadmap for OpenShift. What are the new features that are becoming over the next six to nine to 12 months? It's open source available on GitHub. Customers can see, and then they can basically come back and give feedback like, Hey, you know, we want hip compliance. We just launched. That was a big request that was coming from our >>Customers. That is not any process >>Also for Graviton or Nvidia instances. So I I I think it's a, >>Here's the thing, the reason I'm pounding on this is because you guys have a pretty high hit rate, and I think as a >>Customer, mildly successful company >>As, as a customer advocate, the better, you know, if, if you guys make bets that pay off, it's gonna pay off for customers. Right. And because there's a lot of failures in it. Yeah. I mean, let's face it. That's >>Right. And I think, I think you said the key word bets. You place a lot of small bets. Do you have the, the innovation engine to do that? AWS is the perfect place to place those small bets. And then you, you know, pour gas on the fire when, when they take off. >>Yeah, it's a good point. I mean, it's not expensive to experiment. Yeah. >>Especially in the managed service world. Right? >>And I know you love taking things to market and you're a go to market guy. Let's talk gtm, what's got your snow pumped about GTM for 2023? >>We, we are gonna, you know, 10 x the teams that's gonna be focused on these products, right? So we're gonna also come out with a hybrid committed spend program for our customers that meet them where they want to go. So they're coming outta the data center going into a cloud. We're gonna have a nice financial model for them to do that. And that's gonna take a lot of the friction out. >>Yeah. I mean, you've nailed it. I, I think the, the fact that now entire Red Hat portfolio is available on marketplace, you can do it on one click deployment. It's deeply integrated with Amazon services and the most important part that Joel was making now customers can double dip. They can drive benefit from the consumption committed spend programs, both from Red Hat and from aws, which is amazing. Which is a game changer That's right. For many of our large >>Customers. That's right. And that, so we're gonna, we're gonna really go to town on that next year. That's, and all the, all the resources that I have, which are the technology sellers and the sas, you know, the engineers we're growing this team the most out that team. So it's, >>When you say 10 x, how many are you at now? I'm >>Curious to see where you're headed. Tell you, okay. There's not right? Oh no, there's not one. It's triple digit. Yeah, yeah. >>Today. Oh, sweet. Awesome. >>So, and it's a very sizable team. They're actually making sure that each of our customers are successful and then really making sure that, you know, no customer left behind policy. >>And it's a great point that customers love when Amazonians and Red Hats show up, they love it and it's, they want to get more of it, and we're gonna, we're gonna give it to 'em. >>Must feel great to be loved like that. >>Yeah, that's right. Yeah. Yeah. I would say yes. >>Seems like it's safe to say that there's another decade of partnership between your two companies. >>Hope so. That's right. That's the plan. >>Yeah. And I would say also, you know, just the IBM coming into the mix here. Yeah. I, you know, red Hat has informed the way we have turned around our partnership with ibm, essentially we, we signed the strategic collaboration agreement with the company. All of IBM software now runs on Rosa. So that is now also providing a lot of tailwinds both to our rail customers and as well as Rosa customers. And I think it's a very net creative, very positive for our partnership. >>That's right. It's been very positive. Yep. Yeah. >>You see the >>Billboards positive. Yeah, right. Also that, that's great. Great point, Dave. Yep. We have a, we have a new challenge, a new tradition on the cube here at Reinvent where we're, well, it's actually kind of a glamor moment for you, depending on how you leverage it. We're looking for your 32nd hot take your Instagram reel, your sizzle thought leadership, biggest takeaway, most important theme from this year's show. I know you want, right, Joel? I mean, you TM boy, I feel like you can spit the time. >>Yeah. It is all about Rosa for us. It is all in on that, that's the native OpenShift offering on aws and that's, that's the soundbite we're going go to town with. Now, I don't wanna forget all the other products that are in there, but Rosa is a, is a very key push for us this year. >>Fantastic. All right. Manu. >>I think our customers, it's getting super competitive. Our customers want to innovate just a >>Little bit. >>The enterprise customers see the cloud native companies. I wanna do what these guys are doing. I wanna develop features at a fast clip. I wanna scale, I wanna be resilient. And I think that's really the spirit that's coming out. So to Joel's point, you know, move to worlds containers, serverless, DevOps, which was like, you know, aha, something that's happening on the side of an enterprise is not becoming mainstream. The business is demanding it. The, it is becoming the centerpiece in the business strategy. So that's been really like the aha. Big thing that's happening here. >>Yeah. And those architectures are coming together, aren't they? That's correct. Right. You know, VMs and containers, it used to be one architecture and then at the other end of the spectrum is serverless. People thought of those as different things and now it's a single architecture and, and it's kind of right approach for the right job. >>And, and a compliments say to Red Hat, they do an incredible job of hiding that complexity. Yeah. Yes. And making sure that, you know, for example, just like, make it easier for the developers to create value and then, and you know, >>Yeah, that's right. Those, they were previously siloed architectures and >>That's right. OpenShift wanna be place where you wanna run containers or virtual machines. We want that to be this Yeah. Single place. Not, not go bolt on another piece of architecture to just do one or the other. Yeah. >>And hey, the hybrid cloud vision is working for ibm. No question. You know, and it's achievable. Yeah. I mean, I just, I've said unlike, you know, some of the previous, you know, visions on fixing the world with ai, hybrid cloud is actually a real problem that you're attacking and it's showing the results. Agreed. Oh yeah. >>Great. Alright. Last question for you guys. Cause it might be kind of fun, 10 years from now, oh, we're at another, we're sitting here, we all look the same. Time has passed, but we are not aging, which is a part of the new technology that's come out in skincare. That's my, I'm just throwing that out there. Why not? What do you guys hope that you can say about the partnership and, and your continued commitment to community? >>Oh, that's a good question. You go first this time. Yeah. >>I think, you know, the, you know, for looking into the future, you need to look into the past. And Amazon has always been driven by working back from our customers. That's like our key tenant, principle number 1 0 1. >>Couple people have said that on this stage this week. Yeah. >>Yeah. And I think our partnership, I hope over the next decade continues to keep that tenant as a centerpiece. And then whatever comes out of that, I think we, we are gonna be, you know, working through that. >>Yeah. I, I would say this, I think you said that, well, the customer innovation is gonna lead us to wherever that is. And it's, it's, it's gonna be in the cloud for sure. I think we can say that in 10 years. But yeah, anything from, from AI to the quant quantum computing that IBM's really pushing behind that, you know, those are, those are gonna be things that hopefully we show up on a, on a partnership with Manu in 10 years, maybe sooner. >>Well, whatever happens next, we'll certainly be covering it here on the cube. That's right. Thank you both for being here. Joel Manu, fantastic interview. Thanks to see you guys. Yeah, good to see you brought the energy. I think you're definitely ranking high on the top interviews. We >>Love that for >>The day. >>Thank >>My pleasure >>Job, guys. Now that you're competitive at all, and thank you all for tuning in to our live coverage here from AWS Reinvent in Las Vegas, Nevada, with Dave Valante. I'm Savannah Peterson. You're watching The Cube, the leading source for high tech coverage.

>>Hello everyone. Welcome to the Cube's coverage of AWS Reinvent 22. I'm John Ferer, host of the Cube. Got some great coverage here talking about software supply chain and sustainability in the cloud. We've got a great conversation. Gunner Helickson, Vice President and general manager at Red Hat Enterprise Linux and Business Unit of Red Hat. Thanks for coming on. And Edon Eja Director, Product Management of commercial software services aws. Gentlemen, thanks for joining me today. >>Oh, it's a pleasure. >>You know, the hottest topic coming out of Cloudnative developer communities is slide chain software sustainability. This is a huge issue. As open source continues to power away and fund and grow this next generation modern development environment, you know, supply chain, you know, sustainability is a huge discussion because you gotta check things out where, what's in the code. Okay, open source is great, but now we gotta commercialize it. This is the topic, Gunner, let's get in, get with you. What, what are you seeing here and what's some of the things that you're seeing around the sustainability piece of it? Because, you know, containers, Kubernetes, we're seeing that that run time really dominate this new abstraction layer, cloud scale. What's your thoughts? >>Yeah, so I, it's interesting that the, you know, so Red Hat's been doing this for 20 years, right? Making open source safe to consume in the enterprise. And there was a time when in order to do that you needed to have a, a long term life cycle and you needed to be very good at remediating security vulnerabilities. And that was kind of, that was the bar that you had that you had to climb over. Nowadays with the number of vulnerabilities coming through, what people are most worried about is, is kind of the providence of the software and making sure that it has been vetted and it's been safe, and that that things that you get from your vendor should be more secure than things that you've just downloaded off of GitHub, for example. Right? And that's, that's a, that's a place where Red Hat's very comfortable living, right? >>Because we've been doing it for, for 20 years. I think there, there's another, there's another aspect to this, to this supply chain question as well, especially with the pandemic. You know, we've got these, these supply chains have been jammed up. The actual physical supply chains have been jammed up. And, and the two of these issues actually come together, right? Because as we've been go, as we go through the pandemic, we've had these digital transformation efforts, which are in large part people creating software in order to manage better their physical supply chain problems. And so as part of that digital transformation, you have another supply chain problem, which is the software supply chain problem, right? And so these two things kind of merge on these as people are trying to improve the performance of transportation systems, logistics, et cetera. Ultimately it all boils down to it all. Both supply chain problems actually boil down to a software problem. It's very >>Interesting that, Well, that is interesting. I wanna just follow up on that real quick if you don't mind. Because if you think about the convergence of the software and physical world, you know, that's, you know, IOT and also hybrid cloud kind of plays into that at scale, this opens up more surface area for attacks, especially when you're under a lot of pressure. This is where, you know, you can, you have a service area in the physical side and you have constraints there. And obviously the pandemic causes problems, but now you've got the software side. Can you, how are you guys handling that? Can you just share a little bit more of how you guys are looking at that with Red Hat? What's, what's the customer challenge? Obviously, you know, skills gaps is one, but like that's a convergence at the same time. More security problems. >>Yeah, yeah, that's right. And certainly the volume of, if we just look at security vulnerabilities themselves, just the volume of security vulnerabilities has gone up considerably as more people begin using the software. And as the software becomes more important to kind of critical infrastructure, more eyeballs are on it. And so we're uncovering more problems, which is kind of, that's, that's okay. That's how the world works. And so certainly the, the number of remediations required every year has gone up. But also the customer expectations, as I've mentioned before, the customer expectations have changed, right? People want to be able to show to their auditors and to their regulators that no, we, we, in fact, I can show the providence of the software that I'm using. I didn't just download something random off the internet. I actually have, like you, you know, adults paying attention to the, how the software gets put together. >>And it's still, honestly, it's still very early days. We can, I think the, in as an industry, I think we're very good at managing, identifying remediating vulnerabilities in the aggregate. We're pretty good at that. I think things are less clear when we talk about kind of the management of that supply chain, proving the provenance, proving the, and creating a resilient supply chain for software. We have lots of tools, but we don't really have lots of shared expectations. Yeah. And so it's gonna be interesting over the next few years, I think we're gonna have more rules are gonna come out. I see NIST has already, has already published some of them. And as these new rules come out, the whole industry is gonna have to kind of pull together and, and really and really rally around some of this shared understanding so we can all have shared expectations and we can all speak the same language when we're talking about this >>Problem. That's awesome. A and Amazon web service is obviously the largest cloud platform out there, you know, the pandemic, even post pandemic, some of these supply chain issues, whether it's physical or software, you're also an outlet for that. So if someone can't buy hardware or, or something physical, they can always get the cloud. You guys have great network compute and whatnot and you got thousands of ISVs across the globe. How are you helping customers with this supply chain problem? Because whether it's, you know, I need to get in my networking gears delayed, I'm gonna go to the cloud and get help there. Or whether it's knowing the workloads and, and what's going on inside them with respect open source. Cause you've got open source, which is kind of an external forcing function. You got AWS and you got, you know, physical compute stores, networking, et cetera. How are you guys helping customers with the supply chain challenge, which could be an opportunity? >>Yeah, thanks John. I think there, there are multiple layers to that. At, at the most basic level we are helping customers buy abstracting away all these data central constructs that they would have to worry about if they were running their own data centers. They would have to figure out how the networking gear, you talk about, you know, having the right compute, right physical hardware. So by moving to the cloud, at least they're delegating that problem to AWS and letting us manage and making sure that we have an instance available for them whenever they want it. And if they wanna scale it, the, the, the capacity is there for them to use now then that, so we kind of give them space to work on the second part of the problem, which is building their own supply chain solutions. And we work with all kinds of customers here at AWS from all different industry segments, automotive, retail, manufacturing. >>And you know, you see that the complexity of the supply chain with all those moving pieces, like hundreds and thousands of moving pieces, it's very daunting. So cus and then on the other hand, customers need more better services. So you need to move fast. So you need to build, build your agility in the supply chain itself. And that is where, you know, Red Hat and AWS come together where we can build, we can enable customers to build their supply chain solutions on platform like Red Hat Enterprise, Linux Rail or Red Hat OpenShift on, on aws. We call it Rosa. And the benefit there is that you can actually use the services that we, that are relevant for the supply chain solutions like Amazon managed blockchain, you know, SageMaker. So you can actually build predictive and s you can improve forecasting, you can make sure that you have solutions that help you identify where you can cut costs. And so those are some of the ways we are helping customers, you know, figure out how they actually wanna deal with the supply chain challenges that we're running into in today's world. >>Yeah, and you know, you mentioned sustainability outside of software su sustainability, you know, as people move to the cloud, we've reported on silicon angle here in the cube that it's better to have the sustainability with the cloud because then the data centers aren't using all that energy too. So there's also all kinds of sustainability advantages, Gunner, because this is, this is kind of how your relationship with Amazon's expanded. You mentioned Rosa, which is Red Hat on, you know, on OpenShift, on aws. This is interesting because one of the biggest discussions is skills gap, but we were also talking about the fact that the humans are huge part of the talent value. In other words, the, the humans still need to be involved and having that relationship with managed services and Red Hat, this piece becomes one of those things that's not talked about much, which is the talent is increasing in value the humans, and now you got managed services on the cloud, has got scale and human interactions. Can you share, you know, how you guys are working together on this piece? Cuz this is interesting cuz this kind of brings up the relationship of that operator or developer. >>Yeah, Yeah. So I think there's, so I think about this in a few dimensions. First is that the kind of the, I it's difficult to find a customer who is not talking about automation at some level right now. And obviously you can automate the processes and, and the physical infrastructure that you already have that's using tools like Ansible, right? But I think that the, combining it with the, the elasticity of a solution like aws, so you combine the automation with kind of elastic and, and converting a lot of the capital expenses into operating expenses, that's a great way actually to save labor, right? So instead of like racking hard drives, you can have somebody who's somebody do something a little more like, you know, more valuable work, right? And so, so okay, but that gives you a platform and then what do you do with that platform? >>And if you've got your systems automated and you've got this kind of elastic infrastructure underneath you, what you do on top of it is really interesting. So a great example of this is the collaboration that, that we had with running the rel workstation on aws. So you might think like, well why would anybody wanna run a workstation on, on a cloud? That doesn't make a whole lot of sense unless you consider how complex it is to set up, if you have the, the use case here is like industrial workstations, right? So it's animators, people doing computational fluid dynamics, things like this. So these are industries that are extremely data heavy. They have workstations have very large hardware requirements, often with accelerated GPUs and things like this. That is an extremely expensive thing to install on premise anywhere. And if the pandemic taught us anything, it's, if you have a bunch of very expensive talent and they all have to work from a home, it is very difficult to go provide them with, you know, several tens of thousands of dollars worth of worth of worth of workstation equipment. >>And so combine the rail workstation with the AWS infrastructure and now all that workstation computational infrastructure is available on demand and on and available right next to the considerable amount of data that they're analyzing or animating or, or, or working on. So it's a really interesting, it's, it was actually, this is an idea that I was actually born with the pandemic. Yeah. And, and it's kind of a combination of everything that we're talking about, right? It's the supply chain challenges of the customer, It's the lack of lack of talent, making sure that people are being put their best and highest use. And it's also having this kind of elastic, I think, opex heavy infrastructure as opposed to a CapEx heavy infrastructure. >>That's a great example. I think that's illustrates to me what I love about cloud right now is that you can put stuff in, in the cloud and then flex what you need when you need it at in the cloud rather than either ingress or egress data. You, you just more, you get more versatility around the workload needs, whether it's more compute or more storage or other high level services. This is kind of where this NextGen cloud is going. This is where, where, where customers want to go once their workloads are up and running. How do you simplify all this and how do you guys look at this from a joint customer perspective? Because that example I think will be something that all companies will be working on, which is put it in the cloud and flex to the, whatever the workload needs and put it closer to the work compute. I wanna put it there. If I wanna leverage more storage and networking, Well, I'll do that too. It's not one thing. It's gotta flex around what's, how are you guys simplifying this? >>Yeah, I think so for, I'll, I'll just give my point of view and then I'm, I'm very curious to hear what a not has to say about it, but the, I think and think about it in a few dimensions, right? So there's, there is a, technically like any solution that aan a nun's team and my team wanna put together needs to be kind of technically coherent, right? The things need to work well together, but that's not the, that's not even most of the job. Most of the job is actually the ensuring and operational consistency and operational simplicity so that everything is the day-to-day operations of these things kind of work well together. And then also all the way to things like support and even acquisition, right? Making sure that all the contracts work together, right? It's a really in what, So when Aon and I think about places of working together, it's very rare that we're just looking at a technical collaboration. It's actually a holistic collaboration across support acquisition as well as all the engineering that we have to do. >>And on your, your view on how you're simplifying it with Red Hat for your joint customers making Collabo >>Yeah. Gun, Yeah. Gunner covered it. Well I think the, the benefit here is that Red Hat has been the leading Linux distribution provider. So they have a lot of experience. AWS has been the leading cloud provider. So we have both our own point of views, our own learning from our respective set of customers. So the way we try to simplify and bring these things together is working closely. In fact, I sometimes joke internally that if you see Ghana and my team talking to each other on a call, you cannot really tell who who belongs to which team. Because we're always figuring out, okay, how do we simplify discount experience? How do we simplify programs? How do we simplify go to market? How do we simplify the product pieces? So it's really bringing our, our learning and share our perspective to the table and then really figure out how do we actually help customers make progress. Rosa that we talked about is a great example of that, you know, you know, we, together we figured out, hey, there is a need for customers to have this capability in AWS and we went out and built it. So those are just some of the examples in how both teams are working together to simplify the experience, make it complete, make it more coherent. >>Great. That's awesome. That next question is really around how you help organizations with the sustainability piece, how to support them, simplifying it. But first, before we get into that, what is the core problem around this sustainability discussion we're talking about here, supply chain sustainability, What is the core challenge? Can you both share your thoughts on what that problem is and what the solution looks like and then we can get into advice? >>Yeah. Well from my point of view, it's, I think, you know, one of the lessons of the last three years is every organization is kind of taking a careful look at how resilient it is. Or ever I should say, every organization learned exactly how resilient it was, right? And that comes from both the, the physical challenges and the logistics challenges that everyone had. The talent challenges you mentioned earlier. And of course the, the software challenges, you know, as everyone kind of embarks on this, this digital transformation journey that, that we've all been talking about. And I think, so I really frame it as, as resilience, right? And and resilience is at bottom is really about ensuring that you have options and that you have choices. The more choices you have, the more options you have, the more resilient you, you and your organization is going to be. And so I know that that's how, that's how I approach the market. I'm pretty sure that's exact, that's how AON is, has approaching the market, is ensuring that we are providing as many options as possible to customers so that they can assemble the right, assemble the right pieces to create a, a solution that works for their particular set of challenges or their unique set of challenges and and unique context. Aon, is that, does that sound about right to you? Yeah, >>I think you covered it well. I, I can speak to another aspect of sustainability, which is becoming increasingly top of mind for our customer is like how do they build products and services and solutions and whether it's supply chain or anything else which is sustainable, which is for the long term good of the, the planet. And I think that is where we have been also being very intentional and focused in how we design our data center. How we actually build our cooling system so that we, those are energy efficient. You know, we, we are on track to power all our operations with renewable energy by 2025, which is five years ahead of our initial commitment. And perhaps the most obvious example of all of this is our work with arm processors Graviton three, where, you know, we are building our own chip to make sure that we are designing energy efficiency into the process. And you know, we, there's the arm graviton, three arm processor chips, there are about 60% more energy efficient compared to some of the CD six comparable. So all those things that are also we are working on in making sure that whatever our customers build on our platform is long term sustainable. So that's another dimension of how we are working that into our >>Platform. That's awesome. This is a great conversation. You know, the supply chain is on both sides, physical and software. You're starting to see them come together in great conversations and certainly moving workloads to the cloud running in more efficiently will help on the sustainability side, in my opinion. Of course, you guys talked about that and we've covered it, but now you start getting into how to refactor, and this is a big conversation we've been having lately, is as you not just lift and ship but re-platform and refactor, customers are seeing great advantages on this. So I have to ask you guys, how are you helping customers and organizations support sustainability and, and simplify the complex environment that has a lot of potential integrations? Obviously API's help of course, but that's the kind of baseline, what's the, what's the advice that you give customers? Cause you know, it can look complex and it becomes complex, but there's an answer here. What's your thoughts? >>Yeah, I think so. Whenever, when, when I get questions like this from from customers, the, the first thing I guide them to is, we talked earlier about this notion of consistency and how important that is. It's one thing, it it, it is one way to solve the problem is to create an entirely new operational model, an entirely new acquisition model and an entirely new stack of technologies in order to be more sustainable. That is probably not in the cards for most folks. What they want to do is have their existing estate and they're trying to introduce sustainability into the work that they are already doing. They don't need to build another silo in order to create sustainability, right? And so there have to be, there has to be some common threads, there has to be some common platforms across the existing estate and your more sustainable estate, right? >>And, and so things like Red Hat enterprise Linux, which can provide this kind of common, not just a technical substrate, but a common operational substrate on which you can build these solutions if you have a common platform on which you are building solutions, whether it's RHEL or whether it's OpenShift or any of our other platforms that creates options for you underneath. So that in some cases maybe you need to run things on premise, some things you need to run in the cloud, but you don't have to profoundly change how you work when you're moving from one place to another. >>And that, what's your thoughts on, on the simplification? >>Yeah, I mean think that when you talk about replatforming and refactoring, it is a daunting undertaking, you know, in today's, in the, especially in today's fast paced work. So, but the good news is you don't have to do it by yourself. Customers don't have to do it on their own. You know, together AWS and Red Hat, we have our rich partner ecosystem, you know AWS over AWS has over a hundred thousand partners that can help you take that journey, the transformation journey. And within AWS and working with our partners like Red Hat, we make sure that we have all in, in my mind there are really three big pillars that you have to have to make sure that customers can successfully re-platform refactor their applications to the modern cloud architecture. You need to have the rich set of services and tools that meet their different scenarios, different use cases. Because no one size fits all. You have to have the right programs because sometimes customers need those incentives, they need those, you know, that help in the first step and last but no needs, they need training. So all of that, we try to cover that as we work with our customers, work with our partners and that is where, you know, together we try to help customers take that step, which is, which is a challenging step to take. >>Yeah. You know, it's great to talk to you guys, both leaders in your field. Obviously Red hats, well story history. I remember the days back when I was provisioning, loading OSS on hardware with, with CDs, if you remember, that was days gunner. But now with high level services, if you look at this year's reinvent, and this is like kind of my final question for the segment is then we'll get your reaction to is last year we talked about higher level services. I sat down with Adam Celski, we talked about that. If you look at what's happened this year, you're starting to see people talk about their environment as their cloud. So Amazon has the gift of the CapEx, the all that, all that investment and people can operate on top of it. They're calling that environment their cloud. Okay, For the first time we're seeing this new dynamic where it's like they have a cloud, but they're Amazon's the CapEx, they're operating. So you're starting to see the operational visibility gun around how to operate this environment. And it's not hybrid this, that it's just, it's cloud. This is kind of an inflection point. Do you guys agree with that or, or having a reaction to that statement? Because I, I think this is kind of the next gen super cloud-like capability. It's, it's, we're going, we're building the cloud. It's now an environment. It's not talking about private cloud, this cloud, it's, it's all cloud. What's your reaction? >>Yeah, I think, well I think it's a very natural, I mean we used words like hybrid cloud, multi-cloud, if, I guess super cloud is what the kids are saying now, right? It's, it's all, it's all describing the same phenomena, right? Which is, which is being able to take advantage of lots of different infrastructure options, but still having something that creates some commonality among them so that you can, so that you can manage them effectively, right? So that you can have kind of uniform compliance across your estate so that you can have kind of, you can make the best use of your talent across the estate. I mean this is a, this is, it's a very natural thing. >>They're calling it cloud, the estate is the cloud. >>Yeah. So yeah, so, so fine if it, if it means that we no longer have to argue about what's multi-cloud and what's hybrid cloud, I think that's great. Let's just call it cloud. >>And what's your reaction, cuz this is kind of the next gen benefits of, of higher level services combined with amazing, you know, compute and, and resource at the infrastructure level. What's your, what's your view on that? >>Yeah, I think the construct of a unified environment makes sense for customers who have all these use cases which require, like for instance, if you are doing some edge computing and you're running it WS outpost or you know, wave lent and these things. So, and, and it is, it is fear for customer to say, think that hey, this is one environment, same set of tooling that they wanna build that works across all their different environments. That is why we work with partners like Red Hat so that customers who are running Red Hat Enterprise Linux on premises and who are running in AWS get the same level of support, get the same level of security features, all of that. So from that sense, it actually makes sense for us to build these capabilities in a way that customers don't have to worry about, Okay, now I'm actually in the AWS data center versus I'm running outpost on premises. It is all one. They, they just use the same set of cli command line APIs and all of that. So in that sense, it's actually helps customers have that unification so that that consistency of experience helps their workforce and be more productive versus figuring out, okay, what do I do, which tool I use? Where >>And on you just nailed it. This is about supply chain sustainability, moving the workloads into a cloud environment. You mentioned wavelength, this conversation's gonna continue. We haven't even talked about the edge yet. This is something that's gonna be all about operating these workloads at scale and all the, with the cloud services. So thanks for sharing that and we'll pick up that edge piece later. But for reinvent right now, this is really the key conversation. How to bake the sustained supply chain work in a complex environment, making it simpler. And so thanks for sharing your insights here on the cube. >>Thanks. Thanks for having >>Us. Okay, this is the cube's coverage of ados Reinvent 22. I'm John Fur, your host. Thanks for watching.

(upbeat music) >> Good afternoon, everyone. Welcome back to theCUBE Live in Detroit, Michigan. Lisa Martin here with John Furrier. We are covering KubeCon + CloudNativeCon '22. John, this is day two of our coverage wall-to-wall three days of coverage on theCUBE. We've been talking a lot about the developer and how the world is starting to really revolve around developer and DevOps portfolios. >> Yes, developers, startups, big companies, all transforming. This next segment, we want to hear from how Dell Technologies cloud natives, big time strategy there and looking forward to it. It's good. It's going to be a great segment. >> Yes, please welcome back one of our alumni to theCUBE. Brad Maltz is here, Senior Director of DevOps Portfolio and DevRel for Dell Technologies. Good to see you. >> Thank you guys for having me. >> So, Dell at KubeCon, what's going on? >> Yeah, that's literally the most common question I'm getting. So for us, it's a lot about our customer base is making that transformation into a DevOps world. And they have a ton of Dell and they're like, Hey, from a Dell perspective, how do you help us make that transformation into a DevOps operating model? So we're here to explain that. We're here to talk about infrastructure as code, our container Kubernetes story, our multi-cloud story. We're talking about all of it. >> Tell us about those stories and what the value is in it for companies to work with Dell as they transition. >> So when we look at it from a DevOps perspective for us, it's all about the culture, the operating model shift they're trying to make. And what that means to them is they have to figure out how do they automate all of the stacks they have to deal with. Whether it's going to be server, storage, data protection, network, and all the way up through the hypervisor and Kubernetes. That means they need to work with an ecosystem of tools. Things like Ansible, things like Terraform, all that stuff. Our job is to make our portfolio more consumable in the infrastructure as code space. That's one part of the discussion. The second part of the conversation is Kubernetes won. Kubernetes won the abstraction in this multi-cloud world and we as Dell are helping our customers consume Kubernetes. Whether it's by bringing solutions and more appliance oriented mentality to the market or whether it's actually enabling them with our container storage modules and CSI drivers. >> So it as supercloud as we call or multi-cloud as some people call it, you're starting to see the abstraction for interoperability, but essentially just distributed hybrid cloud. Edge as you guys have a big presence. So Dell's supplying not just the data center anymore. Cloud models are moving to hybrid on-premises, edge is growing. We saw some great use cases where military applications are using Kubernetes and all kinds of new things. So this real examples happening right now. This is going to impact Dell's customers and Dell as a supplier of compute and servers. And the gear that runs everything. Like at a telco, you can have a data center at an edge spot, like a box could be a data center. >> Telco is a great example cause we created the business, the Telco business unit. And in the Telco business unit, our goal was, hey, telco is a little different than enterprise edge. Enterprise edge, retail, manufacturing, healthcare. They have certain needs. Telco, much smaller group of customers that have a much different set of needs. And that's very similar is how do we scale at the edge? How do we control things programmatically? How do we do it in a secure way? And how do we do it so that our people internally don't have to deal with the underpinnings of all that infrastructure. Just make it easier for them. That's our goal through the edge discussions, through telco and all that. >> Yeah. We've been doing a big thing on why hardware matters. Hardware's back. We look at all the hyperscalers, the big competition is faster, faster, faster chips, faster the physics. This is part of the supply chain both hardware and software. Okay. So developers want more power. At the end of the day, this community here wants invisible infrastructure and they want it fast. >> Brad: Yes, that's exactly right. >> There's a lot under the hub. It's still servers. >> You still got firmware, you still got bio, you still got to management operating system, You still got to patch things, kernels, security issues, all of that from a server perspective. We haven't even talked about storage or networking or any of the other stuff. So there's a ton of buttons and dials under the covers. >> And that's totally going to be awesome. And the question comes in, okay, now take me to the cloud native because automation, infrastructures code, these are now the hotspots. Software supply chain, not hardware, software supply chain. So these are all things that are going to be intersecting. What's your view? >> In the multi-cloud view of the world, what we really have are our customers are saying, okay, we started on one cloud, Amazon or Azure or Google. And they're like, you know what? We had to go to a second cloud for whatever reason, many reasons. Now we have to manage two clouds. And by the way, we never got fully off-prem. So now we have all of our on-premises stuff plus multiple clouds. How do we deal with the complexity there? And the complexity there is everything from data problems of data mobility, data protection, replication, all that stuff. How do we deal with the actual application life cycle management across that? And that's where a lot of the tooling we're discussing comes in. That's where Kubernetes comes in and they want to do it in an agnostic way. 'Cause if they can't begin to transition to do it in a standardized layer, then the end of the day they're still going to be managing three totally different environments with three separate engineering teams. >> So is your target audience primarily existing Dell customers, legacy customers, or is it really wide open? >> It's actually been opening up. So we have kind of, the way I view it is we have three different segments that we're going to be going after. We have what I would say is the top 10% of the industry that's really able to skill up into this DevOps world very quickly. They're going to go after the GitOps, they're going to go after all those things. That's a combination of existing customers, but also the really, really large customers that can build their own clouds on-premises. We then have the other end of the spectrum. People that aren't making the shift. People that are like, you know what this DevOps transformation it's not going to help us there, but we still need server and storage and whatnot. And then I like to call it the squishy middle. 60, 70% of the market that's like, we can't scale up in time, we can't hire the people, they're not available 'cause that 10% just got them all, but we still have the same problems. And how do we operate in a world where we have that multi-cloud type of a problem, but we can't find the people. Now you got to figure out more of the no-code, low-code packaged solutions, packaged automation coming from companies like Dell and others. >> So there's customers that are either at the beginning of their journey are not convinced yet. What are some of the barriers that they're seeing that Dell can help them overcome? >> Number one thing, education. >> Lisa: Really? >> We're hearing that consistently here at KubeCon and just customer meetings all over the place. There is a segment of the industry that they're empowered to move into a DevOps model. They don't have the ability or resources. They're not able to say, I've been doing this forever in this way in storage. How do I do that in another thing? And they're scared. They want somebody to come in and kind of handhold them a little bit, but somebody they trust. Somebody they've been working with for a very long time. That's Dell's role. Hands-on labs, training materials, how-to videos, but do it in the comfortable way that they feel like, okay we got this. >> And the success with the customers has been that well-documented. The success with the company, again, continues to survive and thrive in all conditions. So Michael Dell knows what he's doing. Love following his strategy. Michael, if you're watching, I know he watches theCUBE video, congratulations. But now the hard question for Dell is this, the applications used to run on PCs, now they're running PCs under the covers and servers. The application space here at this community is enabled by Kubernetes, is creating a new application runtime like environment. I like, compared to the old app server days when things were like just application specific, development got easier. We're in that renaissance now where the app runtime is being enabled by Kubernetes. You guys been there, done that in the old school, now the new school. What's your view on this Kubernetes? What's Dell's view on? >> Yeah, so back to Kubernetes won in my head. It's just flat out won and part of the reason, and it beat out a lot of things. You remember Cloud Foundry, which there's still a thing, but Cloud Foundry went a little too far up into the application stack and constrained the application developers a bit too much. Kubernetes success is two things. It's because they're not constraining the developer, but they're also figuring out how to enable that IT operations mindset. And they become that happy medium that's out there. So now all of a sudden, application modernization conversations and cloud-native app development, there is a standard package. There's standard load balancing and security paradigm, standard registration mechanisms, all built into the Kubernetes layer, by the way, enabled by an ecosystem. And because they're actually going through that, what's happening now is we can finally move forward. We can take that next step and we can build around that ecosystem of Kubernetes. >> That is thematically something that we've been hearing, John, for the last day and a half is the maturation of Kubernetes People, what's next? We are ready for the next step. Talk about Dell as an enabler of that. >> Yeah, so a funny, another part of that paradigm is Kubernetes does not equal virtualization. And this is a hard one in this industry right now. A lot of people say, well, yeah, we did the VMware pivot and then the KVM and everything else and they're like, this is just another one of those pivots. I'm like, no it's not. Virtualization was the pivot of physical hardware became virtual hardware, but you still thought of it in CPU memory disc and you managed it in the same way. Kubernetes, it's a such a different way of thinking about operationalization and all that abstraction that what we're realizing is people need to take baby steps into Kubernetes right now. The maturity of it is great because there is an ecosystem around it, but the majority of the industry isn't even aware of the basics of Kubernetes right now. So our job, we look at it as the education part, but also can we deliver the solutions together with the OpenShift's of the world and the Tanzu's of the world and the Rancher's of the world. Can we deliver more of that full stack experience going into the next few years? That's where we believe we can help accelerate them. Education and that delivery mechanism. >> And the community support is going to be there too. You got to have the. >> 100%. >> The community, not just education, which you guys done before, but doing it with open source vibe. >> That's where DevRel comes in. So the DevRel half of my world now is all about Dell in the community. And to be part of community isn't just to say, Hey, I'm going to go sponsor something. That's not community to me. >> It doesn't hurt. >> It doesn't hurt, but we're going to do that. We're definitely going to help with that. What our notion is you got to participate, you got to contribute, you got to be there, you got to be part of the community. That's part of my developer relations team is to become part of it. >> You got to be part of it and belong. Belonging is earning. >> Brad: Yes. >> And that's the key. And the other thing we were talking about standards and Dell has won a lot of business 'cause the PC and the servers all had standards, standard components. Standards now in the community are being driven by developer consensus. >> Brad: Yes. >> So that is an interesting new paradigm. So if you make cloud native work where all the hardware and software that's powering the builders is invisible. The developers will tell you what they want. >> 100%. >> And that's why your Kubernetes, Cloud Foundry example is so on point. It's a little bit nuanced, but what happened there is, let's explain Kubernetes was loosely de facto enabling. They didn't try to take too much territory. They didn't over push. >> Brad: Exactly. >> They were very flexible, lightweight at first, but it was enabling. >> It was organic. >> And we called it on theCUBE, I'm not going to lie, we called that early on. So props to us. >> Brad: Good job. >> Pat on the back. >> Lisa: Pat your own back. >> We get it right a lot. But now there's impact though. But the Dell I think speaks to the theme here, which just we talked is that you got startups here. We had from Envoy, we saw the donator there. He started his own company. You got Dell, which has large enterprises running massive workloads with a lot of legacy and modernization. So you got a combination of both coming together. This is going to be a collision of innovation. >> Oh I look, that's exactly right. Part of what I've been getting is not just the end users, the infrastructure developers, and whatnot around here. Startups look, come to Dell, and they're like, why are you here? Like we build this and we don't talk to you. And we're like, why not? If we come to market and start delivering more of those Kubernetes oriented solutions and the Kubernetes stack experience, that's where you guys should be working with us. You're part of the ecosystem. >> Well, your job is to say to them, look it when you want to write your software for the edge and we have market share of the most hardware at the edge, 'cause we perform better on the edge. No one wants to write software on the slower platform. >> No. >> Name me one I want to write software that's just, this is something, but people don't understand that's why you're here. >> Brad: That's exactly right. >> The game is about performance. >> Brad: Yeah. >> Cloud can do it, you can do it with a machine. So it depends where in the distributed computing chain you're at. >> You bring up one topic that actually isn't a core discussion topic around DevOps, but I am seeing more HPC and a AI/ML conversations popping up in this DevOps cloud native space. 'Cause even the market of HPC, which is a very traditional market, commodity server driven in the past, they're starting to say, how do I take advantage of Kubernetes and all of the benefits that we've been talking about. >> What are some of the things that you've heard like in your sense is the key theme or the talk track of Kubernetes, its evolution? What's on the developer's minds the last day and a half at this conference? >> Oh, okay. That's a hard question, but a good one. So the way I look at it is probably it's the robustness of the features within Kubernetes, not the native features, but even partner included features. They just want to be able to handle security in a much more, I hate to say zero trust, but secure cloud native way. There's tools in the Kubernetes ecosystem that are so integrated into Kubernetes. They don't have to think sometimes as much about how do they do it themselves. They can go find through open source or off-the-shelf startup and say, I need that and I can spin it up in about five minutes and now I'm doing that without having to spend weeks or months and having to build that. And that's security is one example. You can go through the networking discussion, you can go through so many different areas. The fact is because of community and the ecosystem, that is the winning formula for Kubernetes to enable the development. That's all I'm hearing here is they're like, give me more, give me more startups, give me more of these technologies. >> And ease of use has been a big topic here. We've been talking before we came on camera about VMware has done great since it used the virtual machine example versus Kubernetes. That is millions of developers and operators on VMware. They have about 200,000 plus just in VMUG alone. So they are going to transform their careers. They're looking for a home. They're looking for a community for the next 10 years. I mean, VMware will still be around with Broadcom, but I'm speculating that it will be much more in maintenance mode. But to get someone's career in fourth gear, fifth gear, you got to go and get that next skill set, and that's the question. Where do all these operators, IT operators go to become enterprise operators? >> Brad: That's exactly right. >> That is a big topic. What's your reaction? >> Sp I'm actually a living proof of that. I grew up in the VMware ecosystem. And for me making that pivot, it took me many years. One of the ways I did that was I actually have run in Dell, our advanced development pivotal Dojos, if you remember Pivotal. >> Yes. >> And doing the Pair Programming in Agile. It took me that mental shift to say, okay, we were doing it that way and now there's a new way to do it through code with developers and using all the new buzzwords. And that pivot is different for somebody that's just starting now, and they don't have access to a Dojo that they can go handle like a whole bunch of pair programmers. How do they make that pivot? That's 100% what we have to do. >> Okay, so my question is this, this is a hard question for you, maybe you can answer or not or maybe you can. What's different now than the attempt in the past from Dell EMC to do work or align with the developers? I think, was it five, six years ago, it was an effort. Was it timing? What's different now from then? >> So that attempt was awesome. That team was great. I was very close to that team and that was from the EMC side originally is where they have built that out. And the notion of that was that we just have to go start contributing knowledge and technology into the community and start really taking the brand and trying to expand the brand to be relevant in that community. Nothing wrong. That was actually an amazing way they did it. I think through the merger there was definitely a little bit of, okay, well, maybe this isn't one of our top priorities right now and that's probably what happened through the actual merger. >> John: It's a little bit distraction. >> It was distraction. >> Timings wasn't as good now. >> You try merging a 67 billion merger. I mean it's just really hard to do. What happened here is I think we finally got past a lot of that with the merger and now we're in steady stage/growth mode, which is a notion that now we can go and do this again in the new world, taking our lessons learned from what we did before, and try to actually go and update that in these new power apps. >> And you could point to some specific timing issues. Like at that time this community wasn't as advanced along. Kubernetes wasn't as clear. Visibility to that value proposition. Although a lot of people were speculating what happened that way. >> Exactly. >> But now with multi-cloud, I think developers starting to see the reality that it ain't going to be one cloud. >> Well, multi-cloud is not one cloud, so 100%. >> Well, I mean there's multi-cloud today, but it's really not multi-cloud by the way it could be. The people have multiple clouds. I think that gives developers comfort that existing enterprise players. Remember Microsoft wasn't really in the cloud game six, seven years ago. Look where they are now. Significant progress, nipping at the heels of AWS. So all the enterprise players are back at the table. >> Brad: Yeah, definitely. We're here. >> And that's timing issue. >> We're here. >> Talk about, you're here, you are helping customers get to the basics of Kubernetes. You talked a lot about the importance of the education. >> Brad: Yes. >> That screams to me that Dell can be a facilitator of cultural change within organizations, whether it's a bank or a hospital or a retailer or whatnot. Another thing that I'm curious about, what you guys are doing, how you've evolved, Dell is a massive partner ecosystem. How is the partner ecosystem involved in helping customers build their DevOps portfolios and really start embracing, understanding, and learning about Kubernetes? >> So that's an ever changing world right now. And that's part of why we're here at KubeCon is to help expand that. We have a very, very strong partner community. Not even just channel, but like technology partner community. And our goal is to understand with our DevOps portfolio what needs to be the next step of that partner community. Do we have to go partner up with like the, I'll use examples, the Solo.io. Do we have to partner up with all the mesh companies, the HashiCorp, which we are, We have to understand where the layers that make sense and where don't. There are some that don't make sense because they're so often to an app developer land or they're so far above even Kubernetes sometimes that maybe they don't make sense in our partner community. >> How influential are, I know we got to go soon, but how influential are your customers in helping to make some of those decisions? It's all about the customer at the end of the day. >> They're the only one that's deciding for us. They have to come to us. We have to see the need. We have to understand the discussions through our sales mechanisms, our other mechanisms. We're using that data every single day, every hour to make those decisions. >> Awesome. Brad, it's been great to have you. Sorry we took more of your time than we planned, but it was so interesting. >> No, this is awesome. >> Dell at KubeCon, you've done a great job of explaining why that absolutely resonates, the relevance, and why customers should be looking at Dell as their partner for this. Thank you so much for your time and your insights. >> Thank you guys. >> All right. For John Furrier and our guest, I'm Lisa Martin. You're watching theCUBE live at KubeCon + CloudNativeCon '22 from Detroit, Michigan. Stick around, our next guest will be here in just a minute. (gentle music)

>>Welcome back everyone, to the special presentation of Cloud Native at scale, the Cube and Platform nine special presentation going in and digging into the next generation super cloud infrastructure as code and the future of application development. We're here with Bickley, who's the chief architect and co-founder of Platform nine Pick. Great to see you Cube alumni. We, we met at an OpenStack event in about eight years ago, or later, earlier when OpenStack was going. Great to see you and great to see congratulations on the success of Platform nine. Thank >>You very much. >>Yeah. You guys have been at this for a while and this is really the, the, the year we're seeing the, the crossover of Kubernetes because of what happens with containers. Everyone now has realized, and you've seen what Docker's doing with the new docker, the open source Docker now just a success Exactly. Of containerization. Right? And now the Kubernetes layer that we've been working on for years is coming, Bearing fruit. This is huge. >>Exactly, Yes. >>And so as infrastructure, as code comes in, we talked to Bacar, talking about Super Cloud. I met her about, you know, the new Arlon, our, our lawn you guys just launched, the infrastructure's code is going to another level, and then it's always been DevOps infrastructure is code. That's been the ethos that's been like from day one, developers just code. Then you saw the rise of serverless and you see now multi-cloud or on the horizon. Connect the dots for us. What is the state of infrastructures code today? >>So I think, I think I'm, I'm glad you mentioned it. Everybody or most people know about infrastructures code, but with Kubernetes, I think that project has evolved at the concept even further. And these dates, it's infrastructure is configuration, right? So, which is an evolution of infrastructure as code. So instead of telling the system, here's how I want my infrastructure by telling it, you know, do step A, B, C, and D. Instead, with Kubernetes, you can describe your desired state declaratively using things called manifest resources. And then the system kind of magically figures it out and tries to converge the state towards the one that you specify. So I think it's, it's a even better version of infrastructures code. Yeah, >>Yeah. And, and that really means it's developer just accessing resources. Okay. That declare, Okay, give me some compute, stand me up some, turn the lights on, turn 'em off, turn 'em on. That's kind of where we see this going. And I like the configuration piece. Some people say composability, I mean now with open source, so popular, you don't have to have to write a lot of code, this code being developed. And so it's into integrations, configuration. These are areas that we're starting to see computer science principles around automation, machine learning, assisting open source. Cuz you've got a lot of code that's right in hearing software, supply chain issues. So infrastructure as code has to factor in these new, new dynamics. Can you share your opinion on these new dynamics of, as open source grows, the glue layers, the configurations, the integration, what are the core issues? >>I think one of the major core issues is with all that power comes complexity, right? So, you know, despite its expressive power systems like Kubernetes and declarative APIs let you express a lot of complicated and complex stacks, right? But you're dealing with hundreds if not thousands of these yamo files or resources. And so I think, you know, the emergence of systems and layers to help you manage that complexity is becoming a key challenge and opportunity in, in this space. That's, >>I wrote a LinkedIn post today, it was comments about, you know, hey, enterprise is the new breed, the trend of SaaS companies moving our consumer comp consumer-like thinking into the enterprise has been happening for a long time, but now more than ever, you're seeing it the old way used to be solve complexity with more complexity and then lock the customer in. Now with open source, it's speed, simplification and integration, right? These are the new dynamic power dynamics for developers. Yeah. So as companies are starting to now deploy and look at Kubernetes, what are the things that need to be in place? Because you have some, I won't say technical debt, but maybe some shortcuts, some scripts here that make it look like infrastructure is code. People have done some things to simulate or or make infrastructure as code happen. Yes. But to do it at scale Yes. Is harder. What's your take on this? What's your >>View? It's hard because there's a per proliferation of methods, tools, technologies. So for example, today it's very common for DevOps and platform engineering tools, I mean, sorry, teams to have to deploy a large number of Kubernetes clusters, but then apply the applications and configurations on top of those clusters. And they're using a wide range of tools to do this, right? For example, maybe Ansible or Terraform or bash scripts to bring up the infrastructure and then the clusters. And then they may use a different set of tools such as Argo CD or other tools to apply configurations and applications on top of the clusters. So you have this sprawl of tools. You, you also have this sprawl of configurations and files because the more objects you're dealing with, the more resources you have to manage. And there's a risk of drift that people call that where, you know, you think you have things under control, but some people from various teams will make changes here and there and then before the end of the day systems break and you have no idea of tracking them. So I think there's real need to kind of unify, simplify, and try to solve these problems using a smaller, more unified set of tools and methodologies. And that's something that we tried to do with this new project. Arlon. >>Yeah. So, so we're gonna get into our line in a second. I wanna get into the why Arlon. You guys announced that at our GoCon, which was put on here in Silicon Valley at the, at the community invite in two where they had their own little day over there at their headquarters. But before we get there, vascar, your CEO came on and he talked about Super Cloud at our in AAL event. What's your definition of super cloud? If you had to kind of explain that to someone at a cocktail party or someone in the industry technical, how would you look at the super cloud trend that's emerging? It's become a thing. What's your, what would be your contribution to that definition or the narrative? >>Well, it's, it's, it's funny because I've actually heard of the term for the first time today, speaking to you earlier today. But I think based on what you said, I I already get kind of some of the, the gist and the, the main concepts. It seems like super cloud, the way I interpret that is, you know, clouds and infrastructure, programmable infrastructure, all of those things are becoming commodity in a way. And everyone's got their own flavor, but there's a real opportunity for people to solve real business problems by perhaps trying to abstract away, you know, all of those various implementations and then building better abstractions that are perhaps business or application specific to help companies and businesses solve real business problems. >>Yeah, I remember that's a great, great definition. I remember, not to date myself, but back in the old days, you know, IBM had a proprietary network operating system, so of deck for the mini computer vendors, deck net and SNA respectively. But T C P I P came out of the osi, the open systems interconnect and remember, ethernet beat token ring out. So not to get all nerdy for all the young kids out there, look, just look up token ring, you'll see, you've probably never heard of it. It's IBM's, you know, connection to the internet at the, the layer too is Amazon, the ethernet, right? So if T C P I P could be the Kubernetes and the container abstraction that made the industry completely change at that point in history. So at every major inflection point where there's been serious industry change and wealth creation and business value, there's been an abstraction Yes. Somewhere. Yes. What's your reaction to that? >>I think this is, I think a saying that's been heard many times in this industry and, and I forgot who originated it, but I think the saying goes like, there's no problem that can't be solved with another layer of indirection, right? And we've seen this over and over and over again where Amazon and its peers have inserted this layer that has simplified, you know, computing and, and infrastructure management. And I believe this trend is going to continue, right? The next set of problems are going to be solved with these insertions of additional abstraction layers. I think that that's really a, yeah, it's gonna continue. >>It's interesting. I just, when I wrote another post today on LinkedIn called the Silicon Wars AMD stock is down arm has been on a rise. We've remember pointing for many years now, that arm's gonna be hugely, it has become true. If you look at the success of the infrastructure as a serviced layer across the clouds, Azure, aws, Amazon's clearly way ahead of everybody. The stuff that they're doing with the silicon and the physics and the, the atoms, the pro, you know, this is where the innovation, they're going so deep and so strong at ISAs, the more that they get that gets come on, they have more performance. So if you're an app developer, wouldn't you want the best performance and you'd want to have the best abstraction layer that gives you the most ability to do infrastructures, code or infrastructure for configuration, for provisioning, for managing services. And you're seeing that today with service MeSHs, a lot of action going on in the service mesh area in in this community of, of co con, which we will be covering. So that brings up the whole what's next? You guys just announced Arlon at ar GoCon, which came out of Intuit. We've had Mariana Tessel at our super cloud event. She's the cto, you know, they're all in the cloud. So they contributed that project. Where did Arlon come from? What was the origination? What's the purpose? Why arlon, why this announcement? Yeah, >>So the, the inception of the project, this was the result of us realizing that problem that we spoke about earlier, which is complexity, right? With all of this, these clouds, these infrastructure, all the variations around and, you know, compute storage networks and the proliferation of tools we talked about the Ansibles and Terraforms and Kubernetes itself, you can think of that as another tool, right? We saw a need to solve that complexity problem, and especially for people and users who use Kubernetes at scale. So when you have, you know, hundreds of clusters, thousands of applications, thousands of users spread out over many, many locations, there, there needs to be a system that helps simplify that management, right? So that means fewer tools, more expressive ways of describing the state that you want and more consistency. And, and that's why, you know, we built our lawn and we built it recognizing that many of these problems or sub problems have already been solved. So Arlon doesn't try to reinvent the wheel, it instead rests on the shoulders of several giants, right? So for example, Kubernetes is one building block, GI ops, and Argo CD is another one, which provides a very structured way of applying configuration. And then we have projects like cluster API and cross plane, which provide APIs for describing infrastructure. So arlon takes all of those building blocks and builds a thin layer, which gives users a very expressive way of defining configuration and desired state. So that's, that's kind of the inception of, >>And what's the benefit of that? What does that give the, what does that give the developer, the user, in this case, >>The developers, the, the platform engineer, team members, the DevOps engineers, they get a a ways to provision not just infrastructure and clusters, but also applications and configurations. They get a way, a system for provisioning, configuring, deploying, and doing life cycle management in a, in a much simpler way. Okay. Especially as I said, if you're dealing with a large number of applications. >>So it's like an operating fabric, if you will. Yes. For them. Okay, so let's get into what that means for up above and below the, the, this abstraction or thin layer below as the infrastructure. We talked a lot about what's going on below that. Yeah. Above our workloads. At the end of the day, you, I talk to CXOs and IT folks that, that are now DevOps engineers. They care about the workloads and they want the infrastructure's code to work. They wanna spend their time getting in the weeds, figuring out what happened when someone made a push that that happened or something happened to need observability and they need to, to know that it's working. That's right. And here's my workloads running effectively. So how do you guys look at the workload side of it? Cuz now you have multiple workloads on these fabric, right? >>So workloads, so Kubernetes has defined kind of a standard way to describe workloads and you can, you know, tell Kubernetes, I wanna run this container this particular way, or you can use other projects that are in the Kubernetes cloud native ecosystem, like K native, where you can express your application in more at a higher level, right? But what's also happening is in addition to the workloads, DevOps and platform engineering teams, they need to very often deploy the applications with the clusters themselves. Clusters are becoming this commodity. It's, it's becoming this host for the application and it kind of comes bundled with it. In many cases it is like an appliance, right? So DevOps teams have to provision clusters at a really incredible rate and they need to tear them down. Clusters are becoming more, >>It's coming like an EC two instance, spin up a cluster. We very, people used words like that. >>That's right. And before arlon you kind of had to do all of that using a different set of tools as, as I explained. So with Arlon you can kind of express everything together. You can say I want a cluster with a health monitoring stack and a logging stack and this ingress controller and I want these applications and these security policies. You can describe all of that using something we call a profile. And then you can stamp out your app, your applications and your clusters and manage them in a very, >>So essentially standard like creates a mechanism. Exactly. Standardized, declarative kind of configurations. And it's like a playbook, deploy it. Now what there between say a script like I'm, I have scripts, I can just automate scripts >>Or yes, this is where that declarative API and infrastructures configuration comes in, right? Because scripts, yes you can automate scripts, but the order in which they run matters, right? They can break, things can break in the middle and, and sometimes you need to debug them. Whereas the declarative way is much more expressive and powerful. You just tell the system what you want and then the system kind of figures it out. And there are these things got controllers which will in the background reconcile all the state to converge towards your desire. It's a much more powerful, expressive and reliable way of getting things done. >>So infrastructure has configuration is built kind of on it's super set of infrastructures code because it's >>An evolution. >>You need edge re's code, but then you can configure the code by just saying do it. You basically declaring it's saying Go, go do that. That's right. Okay, so, alright, so cloud native at scale, take me through your vision of what that means. Someone says, Hey, what does cloud native at scale mean? What's success look like? How does it roll out in the future as you, not future next couple years. I mean people are now starting to figure out, okay, it's not as easy as it sounds. Kubernetes has value. We're gonna hear this year coan a lot of this. What does cloud native at scale mean? >>Yeah, there are different interpretations, but if you ask me, when people think of scale, they think of a large number of deployments, right? Geographies, many, you know, supporting thousands or tens or millions of, of users there, there's that aspect to scale. There's also an equally important a aspect of scale, which is also something that we try to address with Arran. And that is just complexity for the people operating this or configuring this, right? So in order to describe that desired state, and in order to perform things like maybe upgrades or updates on a very large scale, you want the humans behind that to be able to express and direct the system to do that in, in relatively simple terms, right? And so we want the tools and the abstractions and the mechanisms available to the user to be as powerful but as simple as possible. So there's, I think there's gonna be a number and there have been a number of CNCF and cloud native projects that are trying to attack that complexity problem as well. And Arlon kind of falls in in that >>Category. Okay, so I'll put you on the spot. Rogue got Coan coming up and obviously this'll be shipping this segment series out before. What do you expect to see at this year? What's the big story this year? What's the, what's the most important thing happening? Is it in the open source community and also within a lot of the, the people jogging for leadership. I know there's a lot of projects and still there's some white space in the overall systems map about the different areas get run time, there's ability in all these different areas. What's the, where's the action? Where, where's the smoke? Where's the fire? Where's the piece? Where's the tension? >>Yeah, so I think one thing that has been happening over the past couple of cub cons and I expect to continue and, and that is the, the word on the street is Kubernetes is getting boring, right? Which is good, right? >>Boring means simple. >>Well, >>Well maybe, >>Yeah, >>Invisible, >>No drama, right? So, so the, the rate of change of the Kubernetes features and, and all that has slowed, but in, in a, in a positive way. But there's still a general sentiment and feeling that there's just too much stuff. If you look at a stack necessary for hosting applications based on Kubernetes, there are just still too many moving parts, too many components, right? Too much complexity. I go, I keep going back to the complexity problem. So I expect Cube Con and all the vendors and the players and the startups and the people there to continue to focus on that complexity problem and introduce further simplifications to, to the stack. >>Yeah. Vic, you've had an storied career, VMware over decades with them, obviously in 12 years with 14 years or something like that. Big number co-founder here at Platform now you's been around for a while at this game. We, man, we talked about OpenStack, that project you, we interviewed at one of their events. So OpenStack was the beginning of that, this new revolution. I remember the early days it was, it wasn't supposed to be an alternative to Amazon, but it was a way to do more cloud cloud native. I think we had a cloud a Rod team at that time. We would joke we, you know, about, about the dream. It's happening now, now at Platform nine. You guys have been doing this for a while. What's the, what are you most excited about as the chief architect? What did you guys double down on? What did you guys pivot from or two, did you do any pivots? Did you extend out certain areas? Cuz you guys are in a good position right now, a lot of DNA in Cloud native. What are you most excited about and what does Platform Nine bring to the table for customers and for people in the industry watching this? >>Yeah, so I think our mission really hasn't changed over the years, right? It's been always about taking complex open source software because open source software, it's powerful. It solves new problems, you know, every year and you have new things coming out all the time, right? Open Stack was an example where the Kubernetes took the world by storm. But there's always that complexity of, you know, just configuring it, deploying it, running it, operating it. And our mission has always been that we will take all that complexity and just make it, you know, easy for users to consume regardless of the technology, right? So the successor to Kubernetes, you know, I don't have a crystal ball, but you know, you have some indications that people are coming up of new and simpler ways of running applications. There are many projects around there who knows what's coming next year or the year after that. But platform will, a, platform nine will be there and we will, you know, take the innovations from the, the, the community. We will contribute our own innovations and make all of those things very consumable to customers. >>Simpler, faster, cheaper. Exactly. Always a good business model technically to make that happen. Yes. Yeah. I think the, the reigning in the chaos is key, you know, Now we have now visibility into the scale. Final question before we depart Yeah. On this segment, what is at scale, how many clusters do you see that would be a, a watermark for an at scale conversation around an enterprise? Is it workloads we're looking at or, or clusters? How would you Yeah, I would you describe that when people try to squint through and evaluate what's a scale, what's the at scale kind of threshold? >>Yeah. And, and the number of clusters doesn't tell the whole story because clusters can be small in terms of the number of nodes or they can be large. But roughly speaking when we say, you know, large scale cluster deployments, we're talking about maybe hundreds, two thousands. Yeah. >>And final final question, what's the role of the hyperscalers? You got AWS continuing to do well, but they got their core ias, they got a PAs, they're not too too much putting a SaaS out there. They have some SaaS apps, but mostly it's the ecosystem. They have marketplaces doing, doing over $2 billion billions of transactions a year. And, and it's just like, just sitting there. It hasn't really, they're now innovating on it, but that's gonna change ecosystems. What's the role the cloud play in the cloud Native at scale? >>The the hyper square? >>Yeah. Yeah. Abras, Azure, Google, >>You mean from a business perspective, they're, they have their own interests that, you know, that they're, they will keep catering to, They, they will continue to find ways to lock their users into their ecosystem of services and, and APIs. So I don't think that's gonna change, right? They're just gonna keep Well, >>They got great I performance, I mean from a, from a hardware standpoint, yes. That's gonna be key, right? >>Yes. I think the, the move from X 86 being the dominant way and platform to run workloads is changing, right? That, that, that, that, and I think the, the hyperscalers really want to be in the game in terms of, you know, the, the new risk and arm ecosystems and the >>Platforms. Yeah. Not joking aside, Paul Morritz, when he was the CEO of VMware, when he took over once said, I remember our first year doing the cube. Oh, the cloud is one big distributed computer. It's, it's hardware and you got software and you got middleware. And he kinda over, well he kind of tongue in cheek, but really you're talking about large compute and sets of services that is essentially a distributed computer. Yes, >>Exactly. >>It's, we're back in the same game. Thank you for coming on the segment. Appreciate your time. This is cloud native at scale special presentation with Platform nine. Really unpacking super cloud Arlon open source and how to run large scale applications on the cloud, Cloud native develop for developers. And John Feer with the cube. Thanks for Washington. We'll stay tuned for another great segment coming right up.

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

>>Everyone, welcome to the cube here in Palo Alto, California for a special presentation on Cloud native at scale, enabling super cloud modern applications with Platform nine. I'm John Furry, your host of The Cube. We've got a great lineup of three interviews we're streaming today. Mattor Makki, who's the co-founder and VP of Product of Platform nine. She's gonna go into detail around Arlon, the open source products, and also the value of what this means for infrastructure as code and for cloud native at scale. Bickley the chief architect of Platform nine Cube alumni. Going back to the OpenStack days. He's gonna go into why Arlon, why this infrastructure as code implication, what it means for customers and the implications in the open source community and where that value is. Really great wide ranging conversation there. And of course, Vascar, Gort, the CEO of Platform nine, is gonna talk with me about his views on Super Cloud and why Platform nine has a scalable solutions to bring cloud native at scale. So enjoy the program, see you soon. Hello and welcome to the cube here in Palo Alto, California for a special program on cloud native at scale, enabling next generation cloud or super cloud for modern application cloud native developers. I'm John Forry, host of the Cube. Pleasure to have here me Makowski, co-founder and VP of product at Platform nine. Thanks for coming in today for this Cloudnative at scale conversation. >>Thank you for having >>Me. So Cloudnative at scale, something that we're talking about because we're seeing the, the next level of mainstream success of containers Kubernetes and cloud native develop, basically DevOps in the C I C D pipeline. It's changing the landscape of infrastructure as code, it's accelerating the value proposition and the super cloud as we call it, has been getting a lot of traction because this next generation cloud is looking a lot different, but kind of the same as the first generation. What's your view on Super cloud as it fits to cloud native as scales up? >>Yeah, you know, I think what's interesting, and I think the reason why Super Cloud is a really good and a really fit term for this, and I think, I know my CEO was chatting with you as well, and he was mentioning this as well, but I think there needs to be a different term than just multi-cloud or cloud. And the reason is because as cloud native and cloud deployments have scaled, I think we've reached a point now where instead of having the traditional data center style model, where you have a few large distributors of infrastructure and workload at a few locations, I think the model is kind of flipped around, right? Where you have a large number of micro sites. These micro sites could be your public cloud deployment, your private on-prem infrastructure deployments, or it could be your edge environment, right? And every single enterprise, every single industry is moving in that direction. And so you gotta rougher that with a terminology that, that, that indicates the scale and complexity of it. And so I think super cloud is a, is an appropriate term for >>That. So you brought a couple things I want to dig into. You mentioned Edge Notes. We're seeing not only edge nodes being the next kind of area of innovation, mainly because it's just popping up everywhere. And that's just the beginning. Wouldn't even know what's around the corner. You got buildings, you got iot, o ot, and it kind of coming together, but you also got this idea of regions, global infrastructures, big part of it. I just saw some news around cloud flare shutting down a site here, there's policies being made at scale. These new challenges there. Can you share because you can have edge. So hybrid cloud is a winning formula. Everybody knows that it's a steady state. Yeah. But across multiple clouds brings in this new un engineered area, yet it hasn't been done yet. Spanning clouds. People say they're doing it, but you start to see the toe in the water, it's happening, it's gonna happen. It's only gonna get accelerated with the edge and beyond globally. So I have to ask you, what is the technical challenges in doing this? Because it's something business consequences as well, but there are technical challenge. Can you share your view on what the technical challenges are for the super cloud across multiple edges and >>Regions? Yeah, absolutely. So I think, you know, in in the context of this, the, this, this term of super cloud, I think it's sometimes easier to visualize things in terms of two access, right? I think on one end you can think of the scale in terms of just pure number of nodes that you have, deploy number of clusters in the Kubernetes space. And then on the other access you would have your distribution factor, right? Which is, do you have these tens of thousands of nodes in one site or do you have them distributed across tens of thousands of sites with one node at each site? Right? And if you have just one flavor of this, there is enough complexity, but potentially manageable. But when you are expanding on both these access, you really get to a point where that skill really needs some well thought out, well-structured solutions to address it, right? A combination of homegrown tooling along with your, you know, favorite distribution of Kubernetes is not a strategy that can help you in this environment. It may help you when you have one of this or when you, when you scale, is not at the level. >>Can you scope the complexity? Because I mean, I hear a lot of moving parts going on there, the technology's also getting better. We we're seeing cloud native become successful. There's a lot to configure, there's a lot to install. Can you scope the scale of the problem? Because we're talking about at scale Yep. Challenges here. >>Yeah, absolutely. And I think, you know, I I like to call it, you know, the, the, the problem that the scale creates, you know, there's various problems, but I think one, one problem, one way to think about it is, is, you know, it works on my cluster problem, right? So, you know, I come from engineering background and there's a, you know, there's a famous saying between engineers and QA and the support folks, right? Which is, it works on my laptop, which is I tested this change, everything was fantastic, it worked flawlessly on my machine, on production, It's not working. The exact same problem now happens and these distributed environments, but at massive scale, right? Which is that, you know, developers test their applications, et cetera within the sanctity of their sandbox environments. But once you expose that change in the wild world of your production deployment, right? >>And the production deployment could be going at the radio cell tower at the edge location where a cluster is running there, or it could be sending, you know, these applications and having them run at my customer's site where they might not have configured that cluster exactly the same way as I configured it, or they configured the cluster, right? But maybe they didn't deploy the security policies or they didn't deploy the other infrastructure plugins that my app relies on all of these various factors at their own layer of complexity. And there really isn't a simple way to solve that today. And that is just, you know, one example of an issue that happens. I think another, you know, whole new ball game of issues come in the context of security, right? Because when you are deploying applications at scale in a distributed manner, you gotta make sure someone's job is on the line to ensure that the right security policies are enforced regardless of that scale factor. So I think that's another example of problems that occur. >>Okay. So I have to ask about scale because there are a lot of multiple steps involved when you see the success cloud native, you know, you see some, you know, some experimentation. They set up a cluster, say it's containers and Kubernetes, and then you say, Okay, we got this, we can configure it. And then they do it again and again, they call it day two. Some people call it day one, day two operation, whatever you call it. Once you get past the first initial thing, then you gotta scale it. Then you're seeing security breaches, you're seeing configuration errors. This seems to be where the hotpot is. And when companies transition from, I got this to, Oh no, it's harder than I thought at scale. Can you share your reaction to that and how you see this playing out? >>Yeah, so, you know, I think it's interesting. There's multiple problems that occur when, you know, the, the two factors of scale is we talked about start expanding. I think one of them is what I like to call the, you know, it, it works fine on my cluster problem, which is back in, when I was a developer, we used to call this, it works on my laptop problem, which is, you know, you have your perfectly written code that is operating just fine on your machine, your sandbox environment. But the moment it runs production, it comes back with p zeros and POS from support teams, et cetera. And those issues can be really difficult to try us, right? And so in the Kubernetes environment, this problem kind of multi folds, it goes, you know, escalates to a higher degree because yeah, you have your sandbox developer environments, they have their clusters and things work perfectly fine in those clusters because these clusters are typically handcrafted or a combination of some scripting and handcrafting. >>And so as you give that change to then run at your production edge location, like say you radio sell tower site, or you hand it over to a customer to run it on their cluster, they might not have not have configured that cluster exactly how you did it, or they might not have configured some of the infrastructure plugins. And so the things don't work. And when things don't work, triaging them becomes like ishly hard, right? It's just one of the examples of the problem. Another whole bucket of issues is security, which is, is you have these distributed clusters at scale, you gotta ensure someone's job is on the line to make sure that these security policies are configured properly. >>So this is a huge problem. I love that comment. That's not not happening on my system. It's the classic, you know, debugging mentality. Yeah. But at scale it's hard to do that with error prone. I can see that being a problem. And you guys have a solution you're launching, Can you share what our lawn is, this new product, What is it all about? Talk about this new introduction. >>Yeah, absolutely. I'm very, very excited. You know, it's one of the projects that we've been working on for some time now because we are very passionate about this problem and just solving problems at scale in on-prem or at in the cloud or at edge environments. And what arwan is, it's an open source project and it is a tool, it's a Kubernetes native tool for complete end to end management of not just your clusters, but your clusters. All of the infrastructure that goes within and along the sites of those clusters, security policies, your middleware plugins, and finally your applications. So what alarm lets you do in a nutshell is in a declarative way, it lets you handle the configuration and management of all of these components in at scale. >>So what's the elevator pitch simply put for what this solves in, in terms of the chaos you guys are reigning in. What's the, what's the bumper sticker? Yeah, >>What would it do? There's a perfect analogy that I love to reference in this context, which is think of your assembly line, you know, in a traditional, let's say, you know, an auto manufacturing factory or et cetera, and the level of efficiency at scale that that assembly line brings, right online. And if you look at the logo we've designed, it's this funny little robot. And it's because when we think of online, we, we think of these enterprise large scale environments, you know, sprawling at scale creating chaos because there isn't necessarily a well thought through, well structured solution that's similar to an assembly line, which is taking each components, you know, addressing them, manufacturing, processing them in a standardized way, then handing to the next stage. But again, it gets, you know, processed in a standardized way. And that's what Arlon really does. That's like the I pitch. If you have problems of scale of managing your infrastructure, you know, that is distributed. Arlon brings the assembly line level of efficiency and consistency >>For those. So keeping it smooth, the assembly on things are flowing. C C I CD pipelining. Exactly. So that's what you're trying to simplify that ops piece for the developer. I mean, it's not really ops, it's their ops, it's coding. >>Yeah. Not just developer, the ops, the operations folks as well, right? Because developers, you know, there is, the developers are responsible for one picture of that layer, which is my apps, and then maybe that middleware of application that they interface with, but then they hand it over to someone else who's then responsible to ensure that these apps are secure properly, that they are logging, logs are being collected properly, monitoring and observability integrated. And so it solves problems for both those >>Teams. Yeah. It's DevOps. So the DevOps is the cloud native developer. The OP teams have to kind of set policies. Is that where the declarative piece comes in? Is that why that's important? >>Absolutely. Yeah. And, and, and, and you know, Kubernetes really in introduced or elevated this declarative management, right? Because, you know, c communities clusters are Yeah. Or your, yeah, you know, specifications of components that go in Kubernetes are defined in a declarative way. And Kubernetes always keeps that state consistent with your defined state. But when you go outside of that world of a single cluster, and when you actually talk about defining the clusters or defining everything that's around it, there really isn't a solution that does that today. And so online addresses that problem at the heart of it, and it does that using existing open source well known solutions. >>Ed, do I wanna get into the benefits? What's in it for me as the customer developer? But I want to finish this out real quick and get your thoughts. You mentioned open source. Why open source? What's the, what's the current state of the product? You run the product group over at platform nine, is it open source? And you guys have a product that's commercial? Can you explain the open source dynamic? And first of all, why open source? Yeah. And what is the consumption? I mean, open source is great, People want open source, they can download it, look up the code, but maybe wanna buy the commercial. So I'm assuming you have that thought through, can you share open source and commercial relationship? >>Yeah, I think, you know, starting with why open source? I think it's, you know, we as a company, we have, you know, one of the things that's absolutely critical to us is that we take mainstream open source technologies components and then we, you know, make them available to our customers at scale through either a SaaS model on from model, right? But, so as we are a company or startup or a company that benefits, you know, in a massive way by this open source economy, it's only right, I think in my mind that we do our part of the duty, right? And contribute back to the community that feeds us. And so, you know, we have always held that strongly as one of our principles. And we have, you know, created and built independent products starting all the way with fi, which was a serverless product, you know, that we had built to various other, you know, examples that I can give. But that's one of the main reasons why opensource and also opensource because we want the community to really firsthand engage with us on this problem, which is very difficult to achieve if your product is behind a wall, you know, behind, behind a block box. >>Well, and that's, that's what the developers want too. I mean, what we're seeing in reporting with Super Cloud is the new model of consumption is I wanna look at the code and see what's in there. That's right. And then also, if I want to use it, I, I'll do it. Great. That's open source, that's the value. But then at the end of the day, if I wanna move fast, that's when people buy in. So it's a new kind of freemium, I guess, business model. I guess that's the way that, Well, but that's, that's the benefit. Open source. This is why standards and open source is growing so fast. You have that confluence of, you know, a way for helpers to try before they buy, but also actually kind of date the application, if you will. We, you know, Adrian Karo uses the dating me metaphor, you know, Hey, you know, I wanna check it out first before I get married. Right? And that's what open source, So this is the new, this is how people are selling. This is not just open source, this is how companies are selling. >>Absolutely. Yeah. Yeah. You know, I think, and you know, two things. I think one is just, you know, this, this, this cloud native space is so vast that if you, if you're building a close flow solution, sometimes there's also a risk that it may not apply to every single enterprises use cases. And so having it open source gives them an opportunity to extend it, expand it, to make it proper to their use case if they choose to do so, right? But at the same time, what's also critical to us is we are able to provide a supported version of it with an SLA that we, you know, that's backed by us, a SAS hosted version of it as well, for those customers who choose to go that route, you know, once they have used the open source version and loved it and want to take it at scale and in production and need, need, need a partner to collaborate with, who can, you know, support them for that production >>Environment. I have to ask you now, let's get into what's in it for the customer. I'm a customer, why should I be enthused about Arlo? What's in it for me? You know? Cause if I'm not enthused about it, I'm not gonna be confident and it's gonna be hard for me to get behind this. Can you share your enthusiastic view of, you know, why I should be enthused about Arlo customer? >>Yeah, absolutely. And so, and there's multiple, you know, enterprises that we talk to, many of them, you know, our customers, where this is a very kind of typical story that you hear, which is we have, you know, a Kubernetes distribution. It could be on premise, it could be public clouds, native es, and then we have our C I CD pipelines that are automating the deployment of applications, et cetera. And then there's this gray zone. And the gray zone is well before you can you, your CS CD pipelines can deploy the apps. Somebody needs to do all of their groundwork of, you know, defining those clusters and yeah. You know, properly configuring them. And as these things, these things start by being done hand grown. And then as the, as you scale, what typically enterprises would do today is they will have their home homegrown DIY solutions for this. >>I mean, the number of folks that I talk to that have built Terra from automation, and then, you know, some of those key developers leave. So it's a typical open source or typical, you know, DIY challenge. And the reason that they're writing it themselves is not because they want to. I mean, of course technology is always interesting to everybody, but it's because they can't find a solution that's out there that perfectly fits the problem. And so that's that pitch. I think Spico would be delighted. The folks that we've talked, you know, spoken with, have been absolutely excited and have, you know, shared that this is a major challenge we have today because we have, you know, few hundreds of clusters on s Amazon and we wanna scale them to few thousands, but we don't think we are ready to do that. And this will give us >>Stability. Yeah, I think people are scared, not sc I won't say scare, that's a bad word. Maybe I should say that they feel nervous because, you know, at scale small mistakes can become large mistakes. This is something that is concerning to enterprises. And, and I think this is gonna come up at co con this year where enterprises are gonna say, Okay, I need to see SLAs. I wanna see track record, I wanna see other companies that have used it. Yeah. How would you answer that question to, or, or challenge, you know, Hey, I love this, but is there any guarantees? Is there any, what's the SLAs? I'm an enterprise, I got tight, you know, I love the open source trying to free fast and loose, but I need hardened code. >>Yeah, absolutely. So, so two parts to that, right? One is Arlan leverages existing open source components, products that are extremely popular. Two specifically. One is Lon uses Argo cd, which is probably one of the highest rated and used CD open source tools that's out there, right? It's created by folks that are as part of Intuit team now, you know, really brilliant team. And it's used at scale across enterprises. That's one. Second is arlon also makes use of cluster api capi, which is a ES sub-component, right? For lifecycle management of clusters. So there is enough of, you know, community users, et cetera, around these two products, right? Or, or, or open source projects that will find Arlan to be right up in their alley because they're already comfortable, familiar with algo cd. Now Arlan just extends the scope of what Algo CD can do. And so that's one. And then the second part is going back to a point of the comfort. And that's where, you know, Platform nine has a role to play, which is when you are ready to deploy Alon at scale, because you've been, you know, playing with it in your DEF test environments, you're happy with what you get with it, then Platform nine will stand behind it and provide that sla. >>And what's been the reaction from customers you've talked to Platform nine customers with, with, that are familiar with, with Argo and then Arlo? What's been some of the feedback? >>Yeah, I, I, I think the feedback's been fantastic. I mean, I can give you examples of customers where, you know, initially, you know, when you are, when you're telling them about your entire portfolio of solutions, it might not strike a card right away. But then we start talking about Arlan and, and we talk about the fact that it uses Argo CD and they start opening up, they say, We have standardized on Argo and we have built these components, homegrown, we would be very interested. Can we co-develop? Does it support these use cases? So we've had that kind of validation. We've had validation all the way at the beginning of our line before we even wrote a single line of code saying this is something we plan on doing. And the customer said, If you had it today, I would've purchased it. So it's been really great validation. >>All right. So next question is, what is the solution to the customer? If I asked you, Look it, I have, I'm so busy, my team's overworked. I got a skills gap. I don't need another project that's, I'm so tied up right now and I'm just chasing my tail. How does Platform nine help me? >>Yeah, absolutely. So I think, you know, one of the core tenets of Platform nine has always been that we try to bring that public cloud like simplicity by hosting, you know, this in a lot of such similar tools in a SaaS hosted manner for our customers, right? So our goal behind doing that is taking away or trying to take away all of that complexity from customer's hands and offloading it to our hands, right? And giving them that full white glove treatment as we call it. And so from a customer's perspective, one, something like arlon will integrate with what they have so they don't have to rip and replace anything. In fact, it will, even in the next versions, it may even discover your clusters that you have today and, you know, give you an inventory and that, >>So customers have clusters that are growing, that's a sign correct call you guys. >>Absolutely. Either they're, they have massive large clusters, right? That they wanna split into smaller clusters, but they're not comfortable doing that today, or they've done that already on say, public cloud or otherwise. And now they have management challenges. So >>Especially operationalizing the clusters, whether they want to kind of reset everything and remove things around and reconfigure Yeah. And or scale out. >>That's right. Exactly. >>And you provide that layer of policy. >>Absolutely. >>Yes. That's the key value >>Here. That's right. >>So policy based configuration for cluster scale up >>Profile and policy based declarative configuration and life cycle management for clusters. >>If I asked you how this enables Super club, what would you say to that? >>I think this is one of the key ingredients to super cloud, right? If you think about a super cloud environment, there's at least few key ingredients that that come to my mind that are really critical. Like they are, you know, life saving ingredients at that scale. One is having a really good strategy for managing that scale, you know, in a, going back to assembly line in a very consistent, predictable way so that our lot solves then you, you need to compliment that with the right kind of observability and monitoring tools at scale, right? Because ultimately issues are gonna happen and you're gonna have to figure out, you know, how to solve them fast. And alon by the way, also helps in that direction, but you also need observability tools. And then especially if you're running it on the public cloud, you need some cost management tools. In my mind, these three things are like the most necessary ingredients to make Super Cloud successful. And, you know, alarm flows >>In one. Okay, so now the next level is, Okay, that makes sense. There's under the covers kind of speak under the hood. Yeah. How does that impact the app developers and the cloud native modern application workflows? Because the impact to me, seems the apps are gonna be impacted. Are they gonna be faster, stronger? I mean, what's the impact if you do all those things, as you mentioned, what's the impact of the apps? >>Yeah, the impact is that your apps are more likely to operate in production the way you expect them to, because the right checks and balances have gone through, and any discrepancies have been identified prior to those apps, prior to your customer running into them, right? Because developers run into this challenge to their, where there's a split responsibility, right? I'm responsible for my code, I'm responsible for some of these other plugins, but I don't own the stack end to end. I have to rely on my ops counterpart to do their part, right? And so this really gives them, you know, the right tooling for >>That. So this is actually a great kind of relevant point, you know, as cloud becomes more scalable, you're starting to see this fragmentation gone of the days of the full stack developer to the more specialized role. But this is a key point, and I have to ask you because if this Arlo solution takes place, as you say, and the apps are gonna be stupid, there's designed to do, the question is, what did, does the current pain look like of the apps breaking? What does the signals to the customer Yeah. That they should be calling you guys up into implementing Arlo, Argo, and, and, and on all the other goodness to automate, What are some of the signals? Is it downtime? Is it, is it failed apps, Is it latency? What are some of the things that Yeah, absolutely would be in indications of things are effed up a little bit. >>Yeah. More frequent down times, down times that are, that take longer to triage. And so you are, you know, the, you know, your mean times on resolution, et cetera, are escalating or growing larger, right? Like we have environments of customers where they, they have a number of folks on in the field that have to take these apps and run them at customer sites. And that's one of our partners. And they're extremely interested in this because the, the rate of failures they're encountering for this, you know, the field when they're running these apps on site, because the field is automating their clusters that are running on sites using their own script. So these are the kinds of challenges, and those are the pain points, which is, you know, if you're looking to reduce your, your meantime to resolution, if you're looking to reduce the number of failures that occur on your production site, that's one. And second, if you are looking to manage these at scale environments with a relatively small, focused, nimble ops team, which has an immediate impact on your, So those are, those are the >>Signals. This is the cloud native at scale situation, the innovation going on. Final thought is your reaction to the idea that if the world goes digital, which it is, and the confluence of physical and digital coming together, and cloud continues to do its thing, the company becomes the application, not where it used to be supporting the business, you know, the back office and the IIA terminals and some PCs and handhelds. Now if technology's running, the business is the business. Yeah. The company's the application. Yeah. So it can't be down. So there's a lot of pressure on, on CSOs and CIOs now and see, and boards is saying, how is technology driving the top line revenue? That's the number one conversation. Yeah. Do you see that same thing? >>Yeah. It's interesting. I think there's multiple pressures at the CXO CIO level, right? One is that there needs to be that visibility and clarity and guarantee almost that, you know, that the, the technology that's, you know, that's gonna drive your top line is gonna drive that in a consistent, reliable, predictable manner. And then second, there is the constant pressure to do that while always lowering your costs of doing it, right? Especially when you're talking about, let's say retailers or those kinds of large scale vendors, they many times make money by lowering the amount that they spend on, you know, providing those goods to their end customers. So I think those, both those factors kind of come into play and the solution to all of them is usually in a very structured strategy around automation. >>Final question. What does cloudnative at scale look like to you? If all the things happen the way we want 'em to happen, The magic wand, the magic dust, what does it look like? >>What that looks like to me is a CIO sipping at his desk on coffee production is running absolutely smooth. And his, he's running that at a nimble, nimble team size of at the most, a handful of folks that are just looking after things with things. So just >>Taking care of, and the CIO doesn't exist. There's no CSO there at the beach. >>Yeah. >>Thank you for coming on, sharing the cloud native at scale here on the cube. Thank you for your time. >>Fantastic. Thanks for having >>Me. Okay. I'm John Fur here for special program presentation, special programming cloud native at scale, enabling super cloud modern applications with Platform nine. Thanks for watching. Welcome back everyone to the special presentation of cloud native at scale, the cube and platform nine special presentation going in and digging into the next generation super cloud infrastructure as code and the future of application development. We're here at Bickley, who's the chief architect and co-founder of Platform nine b. Great to see you Cube alumni. We, we met at an OpenStack event in about eight years ago, or well later, earlier when opens Stack was going. Great to see you and great to see congratulations on the success of platform nine. >>Thank you very much. >>Yeah. You guys have been at this for a while and this is really the, the, the year we're seeing the, the crossover of Kubernetes because of what happens with containers. Everyone now was realized, and you've seen what Docker's doing with the new docker, the open source Docker now just a success Exactly. Of containerization, right? And now the Kubernetes layer that we've been working on for years is coming, bearing fruit. This is huge. >>Exactly. Yes. >>And so as infrastructure's code comes in, we talked to Bacar talking about Super Cloud, I met her about, you know, the new Arlon, our R lawn you guys just launched, the infrastructure's code is going to another level. And then it's always been DevOps infrastructure is code. That's been the ethos that's been like from day one, developers just code. Then you saw the rise of serverless and you see now multi-cloud or on the horizon, connect the dots for us. What is the state of infrastructures code today? >>So I think, I think I'm, I'm glad you mentioned it, everybody or most people know about infrastructures code. But with Kubernetes, I think that project has evolved at the concept even further. And these dates, it's infrastructure as configuration, right? So, which is an evolution of infrastructure as code. So instead of telling the system, here's how I want my infrastructure by telling it, you know, do step A, B, C, and D instead with Kubernetes, you can describe your desired state declaratively using things called manifest resources. And then the system kind of magically figures it out and tries to converge the state towards the one that you specify. So I think it's, it's a even better version of infrastructures code. >>Yeah, yeah. And, and that really means it's developer just accessing resources. Okay. Not declaring, Okay, give me some compute, stand me up some, turn the lights on, turn 'em off, turn 'em on. That's kind of where we see this going. And I like the configuration piece. Some people say composability, I mean now with open source, so popular, you don't have to have to write a lot of code. It's code being developed. And so it's into integration, it's configuration. These are areas that we're starting to see computer science principles around automation, machine learning, assisting open source. Cuz you got a lot of code that's right in hearing software, supply chain issues. So infrastructure as code has to factor in these new, new dynamics. Can you share your opinion on these new dynamics of, as open source grows, the glue layers, the configurations, the integration, what are the core issues? >>I think one of the major core issues is with all that power comes complexity, right? So, you know, despite its expressive power systems like Kubernetes and declarative APIs let you express a lot of complicated and complex stacks, right? But you're dealing with hundreds if not thousands of these yamo files or resources. And so I think, you know, the emergence of systems and layers to help you manage that complexity is becoming a key challenge and opportunity in, in this space that, >>That's, I wrote a LinkedIn post today was comments about, you know, hey, enterprise is the new breed, the trend of SaaS companies moving our consumer comp consumer-like thinking into the enterprise has been happening for a long time, but now more than ever, you're seeing it the old way used to be solve complexity with more complexity and then lock the customer in. Now with open source, it's speed, simplification and integration, right? These are the new dynamic power dynamics for developers. Yeah. So as companies are starting to now deploy and look at Kubernetes, what are the things that need to be in place? Because you have some, I won't say technical debt, but maybe some shortcuts, some scripts here that make it look like infrastructure is code. People have done some things to simulate or or make infrastructure as code happen. Yes. But to do it at scale Yes. Is harder. What's your take on this? What's your >>View? It's hard because there's a per proliferation of methods, tools, technologies. So for example, today it's very common for DevOps and platform engineering tools, I mean, sorry, teams to have to deploy a large number of Kubernetes clusters, but then apply the applications and configurations on top of those clusters. And they're using a wide range of tools to do this, right? For example, maybe Ansible or Terraform or bash scripts to bring up the infrastructure and then the clusters. And then they may use a different set of tools such as Argo CD or other tools to apply configurations and applications on top of the clusters. So you have this sprawl of tools. You, you also have this sprawl of configurations and files because the more objects you're dealing with, the more resources you have to manage. And there's a risk of drift that people call that where, you know, you think you have things under control, but some people from various teams will make changes here and there and then before the end of the day systems break and you have no idea of tracking them. So I think there's real need to kind of unify, simplify, and try to solve these problems using a smaller, more unified set of tools and methodologies. And that's something that we try to do with this new project. Arlon. >>Yeah. So, so we're gonna get into Arlan in a second. I wanna get into the why Arlon. You guys announced that at our GoCon, which was put on here in Silicon Valley at the, at the by intu. They had their own little day over there at their headquarters. But before we get there, Vascar, your CEO came on and he talked about Super Cloud at our inaugural event. What's your definition of super cloud? If you had to kind of explain that to someone at a cocktail party or someone in the industry technical, how would you look at the super cloud trend that's emerging? It's become a thing. What's your, what would be your contribution to that definition or the narrative? >>Well, it's, it's, it's funny because I've actually heard of the term for the first time today, speaking to you earlier today. But I think based on what you said, I I already get kind of some of the, the gist and the, the main concepts. It seems like super cloud, the way I interpret that is, you know, clouds and infrastructure, programmable infrastructure, all of those things are becoming commodity in a way. And everyone's got their own flavor, but there's a real opportunity for people to solve real business problems by perhaps trying to abstract away, you know, all of those various implementations and then building better abstractions that are perhaps business or application specific to help companies and businesses solve real business problems. >>Yeah, I remember that's a great, great definition. I remember, not to date myself, but back in the old days, you know, IBM had a proprietary network operating system, so to deck for the mini computer vendors, deck net and SNA respectively. But T C P I P came out of the osi, the open systems interconnect and remember, ethernet beat token ring out. So not to get all nerdy for all the young kids out there, look, just look up token ring, you'll see, you've probably never heard of it. It's IBM's, you know, connection for the internet at the, the layer too is Amazon, the ethernet, right? So if T C P I P could be the Kubernetes and the container abstraction that made the industry completely change at that point in history. So at every major inflection point where there's been serious industry change and wealth creation and business value, there's been an abstraction Yes. Somewhere. Yes. What's your reaction to that? >>I think this is, I think a saying that's been heard many times in this industry and, and I forgot who originated it, but I think the saying goes like, there's no problem that can't be solved with another layer of indirection, right? And we've seen this over and over and over again where Amazon and its peers have inserted this layer that has simplified, you know, computing and, and infrastructure management. And I believe this trend is going to continue, right? The next set of problems are going to be solved with these insertions of additional abstraction layers. I think that that's really a, yeah, it's gonna continue. >>It's interesting. I just really wrote another post today on LinkedIn called the Silicon Wars AMD Stock is down arm has been on rise, we've remember pointing for many years now, that arm's gonna be hugely, it has become true. If you look at the success of the infrastructure as a service layer across the clouds, Azure, aws, Amazon's clearly way ahead of everybody. The stuff that they're doing with the silicon and the physics and the, the atoms, the pro, you know, this is where the innovation, they're going so deep and so strong at ISAs, the more that they get that gets come on, they have more performance. So if you're an app developer, wouldn't you want the best performance and you'd wanna have the best abstraction layer that gives you the most ability to do infrastructures, code or infrastructure for configuration, for provisioning, for managing services. And you're seeing that today with service MeSHs, a lot of action going on in the service mesh area in, in this community of co con, which will be a covering. So that brings up the whole what's next? You guys just announced our lawn at ar GoCon, which came out of Intuit. We've had Maria Teel at our super cloud event, She's a cto, you know, they're all in the cloud. So they contributed that project. Where did Arlon come from? What was the origination? What's the purpose? Why our lawn, why this announcement? Yeah, >>So the, the inception of the project, this was the result of us realizing that problem that we spoke about earlier, which is complexity, right? With all of this, these clouds, these infrastructure, all the variations around and you know, compute storage networks and the proliferation of tools we talked about the Ansibles and Terraforms and Kubernetes itself, you can think of that as another tool, right? We saw a need to solve that complexity problem, and especially for people and users who use Kubernetes at scale. So when you have, you know, hundreds of clusters, thousands of applications, thousands of users spread out over many, many locations, there, there needs to be a system that helps simplify that management, right? So that means fewer tools, more expressive ways of describing the state that you want and more consistency. And, and that's why, you know, we built AR lawn and we built it recognizing that many of these problems or sub problems have already been solved. So Arlon doesn't try to reinvent the wheel, it instead rests on the shoulders of several giants, right? So for example, Kubernetes is one building block, GI ops, and Argo CD is another one, which provides a very structured way of applying configuration. And then we have projects like cluster API and cross plane, which provide APIs for describing infrastructure. So arlon takes all of those building blocks and builds a thin layer, which gives users a very expressive way of defining configuration and desired state. So that's, that's kind of the inception of, And >>What's the benefit of that? What does that give the, what does that give the developer, the user, in this case, >>The developers, the, the platform engineer, team members, the DevOps engineers, they get a a ways to provision not just infrastructure and clusters, but also applications and configurations. They get a way, a system for provisioning, configuring, deploying, and doing life cycle management in a, in a much simpler way. Okay. Especially as I said, if you're dealing with a large number of applications. >>So it's like an operating fabric, if you will. Yes. For them. Okay, so let's get into what that means for up above and below the, the, this abstraction or thin layer below the infrastructure. We talked a lot about what's going on below that. Yeah. Above our workloads at the end of the day, and I talk to CXOs and IT folks that, that are now DevOps engineers. They care about the workloads and they want the infrastructure's code to work. They wanna spend their time getting in the weeds, figuring out what happened when someone made a push that that happened or something happened. They need observability and they need to, to know that it's working. That's right. And here's my workloads running effectively. So how do you guys look at the workload side of it? Cuz now you have multiple workloads on these fabric, right? >>So workloads, so Kubernetes has defined kind of a standard way to describe workloads and you can, you know, tell Kubernetes, I want to run this container this particular way, or you can use other projects that are in the Kubernetes cloud native ecosystem, like K native, where you can express your application in more at a higher level, right? But what's also happening is in addition to the workloads, DevOps and platform engineering teams, they need to very often deploy the applications with the clusters themselves. Clusters are becoming this commodity. It's, it's becoming this host for the application and it kind of comes bundled with it. In many cases it is like an appliance, right? So DevOps teams have to provision clusters at a really incredible rate and they need to tear them down. Clusters are becoming more, >>It's coming like an EC two instance, spin up a cluster. We've heard people used words like that. That's >>Right. And before arlon you kind of had to do all of that using a different set of tools as, as I explained. So with AR loan you can kind of express everything together. You can say I want a cluster with a health monitoring stack and a logging stack and this ingress controller and I want these applications and these security policies. You can describe all of that using something we call the profile. And then you can stamp out your app, your applications and your clusters and manage them in a very, So >>It's essentially standard, like creates a mechanism. Exactly. Standardized, declarative kind of configurations. And it's like a playbook, just deploy it. Now what there is between say a script like I'm, I have scripts, I can just automate scripts >>Or yes, this is where that declarative API and infrastructure as configuration comes in, right? Because scripts, yes you can automate scripts, but the order in which they run matters, right? They can break, things can break in the middle and, and sometimes you need to debug them. Whereas the declarative way is much more expressive and powerful. You just tell the system what you want and then the system kind of figures it out. And there are these things are controllers which will in the background reconcile all the state to converge towards your desire. It's a much more powerful, expressive and reliable way of getting things done. >>So infrastructure as configuration is built kind of on, it's a super set of infrastructures code because it's >>An evolution. >>You need edge's code, but then you can configure the code by just saying do it. You basically declaring saying Go, go do that. That's right. Okay, so, alright, so cloud native at scale, take me through your vision of what that means. Someone says, Hey, what does cloud native at scale mean? What's success look like? How does it roll out in the future as you, not future next couple years. I mean people are now starting to figure out, okay, it's not as easy as it sounds. Kubernetes has value. We're gonna hear this year at CubeCon a lot of this, what does cloud native at scale >>Mean? Yeah, there are different interpretations, but if you ask me, when people think of scale, they think of a large number of deployments, right? Geographies, many, you know, supporting thousands or tens or millions of, of users there, there's that aspect to scale. There's also an equally important a aspect of scale, which is also something that we try to address with Arran. And that is just complexity for the people operating this or configuring this, right? So in order to describe that desired state, and in order to perform things like maybe upgrades or updates on a very large scale, you want the humans behind that to be able to express and direct the system to do that in, in relatively simple terms, right? And so we want the tools and the abstractions and the mechanisms available to the user to be as powerful but as simple as possible. So there's, I think there's gonna be a number and there have been a number of CNCF and cloud native projects that are trying to attack that complexity problem as well. And Arlon kind of falls in in that >>Category. Okay, so I'll put you on the spot rogue, that CubeCon coming up and now this'll be shipping this segment series out before. What do you expect to see at this year? It's the big story this year. What's the, what's the most important thing happening? Is it in the open source community and also within a lot of the, the people jockeying for leadership. I know there's a lot of projects and still there's some white space in the overall systems map about the different areas get run time and there's ability in all these different areas. What's the, where's the action? Where, where's the smoke? Where's the fire? Where's the piece? Where's the tension? >>Yeah, so I think one thing that has been happening over the past couple of coupon and I expect to continue and, and that is the, the word on the street is Kubernetes is getting boring, right? Which is good, right? >>Boring means simple. >>Well, well >>Maybe, >>Yeah, >>Invisible, >>No drama, right? So, so the, the rate of change of the Kubernetes features and, and all that has slowed but in, in a, in a positive way. But there's still a general sentiment and feeling that there's just too much stuff. If you look at a stack necessary for hosting applications based on Kubernetes, there are just still too many moving parts, too many components, right? Too much complexity. I go, I keep going back to the complexity problem. So I expect Cube Con and all the vendors and the players and the startups and the people there to continue to focus on that complexity problem and introduce further simplifications to, to the stack. >>Yeah. Vic, you've had an storied career VMware over decades with them within 12 years with 14 years or something like that. Big number co-founder here a platform. I you's been around for a while at this game, man. We talked about OpenStack, that project we interviewed at one of their events. So OpenStack was the beginning of that, this new revolution. I remember the early days it was, it wasn't supposed to be an alternative to Amazon, but it was a way to do more cloud cloud native. I think we had a Cloud Aati team at that time. We would joke we, you know, about, about the dream. It's happening now, now at Platform nine. You guys have been doing this for a while. What's the, what are you most excited about as the chief architect? What did you guys double down on? What did you guys pivot from or two, did you do any pivots? Did you extend out certain areas? Cuz you guys are in a good position right now, a lot of DNA in Cloud native. What are you most excited about and what does Platform Nine bring to the table for customers and for people in the industry watching this? >>Yeah, so I think our mission really hasn't changed over the years, right? It's been always about taking complex open source software because open source software, it's powerful. It solves new problems, you know, every year and you have new things coming out all the time, right? Opens Stack was an example and then Kubernetes took the world by storm. But there's always that complexity of, you know, just configuring it, deploying it, running it, operating it. And our mission has always been that we will take all that complexity and just make it, you know, easy for users to consume regardless of the technology, right? So the successor to Kubernetes, you know, I don't have a crystal ball, but you know, you have some indications that people are coming up of new and simpler ways of running applications. There are many projects around there who knows what's coming next year or the year after that. But platform will a, platform nine will be there and we will, you know, take the innovations from the the community. We will contribute our own innovations and make all of those things very consumable to customers. >>Simpler, faster, cheaper. Exactly. Always a good business model technically to make that happen. Yes. Yeah, I think the, the reigning in the chaos is key, you know, Now we have now visibility into the scale. Final question before we depart this segment. What is at scale, how many clusters do you see that would be a watermark for an at scale conversation around an enterprise? Is it workloads we're looking at or, or clusters? How would you, Yeah, how would you describe that? When people try to squint through and evaluate what's a scale, what's the at scale kind of threshold? >>Yeah. And, and the number of clusters doesn't tell the whole story because clusters can be small in terms of the number of nodes or they can be large. But roughly speaking when we say, you know, large scale cluster deployments, we're talking about maybe hundreds, two thousands. >>Yeah. And final final question, what's the role of the hyperscalers? You got AWS continuing to do well, but they got their core ias, they got a PAs, they're not too too much putting a SaaS out there. They have some SaaS apps, but mostly it's the ecosystem. They have marketplaces doing, doing over $2 billion billions of transactions a year and, and it's just like, just sitting there. It hasn't really, they're now innovating on it, but that's gonna change ecosystems. What's the role the cloud play in the cloud need of its scale? >>The, the hyper squares? >>Yeah, yeah. A's Azure Google, >>You mean from a business perspective, they're, they have their own interests that, you know, that they're, they will keep catering to, they, they will continue to find ways to lock their users into their ecosystem of services and, and APIs. So I don't think that's gonna change, right? They're just gonna keep well, >>They got great performance. I mean, from a, from a hardware standpoint, yes. That's gonna be key, >>Right? Yes. I think the, the move from X 86 being the dominant way and platform to run workloads is changing, right? That, that, that, that, and I think the, the hyper skaters really want to be in the game in terms of, you know, the, the new risk and arm ecosystems, the platforms. >>Yeah. Not joking aside, Paul Morritz, when he was the CEO of VMware, when he took over once said, I remember our first year doing the cube. Oh the cloud is one big distributed computer. It's, it's hardware and you got software and you got middleware and he kinda over, well he's kind of tongue in cheek, but really you're talking about large compute and sets of services that is essentially a distributed computer. Yes, >>Exactly. >>It's, we're back in the same game. Thank you for coming on the segment. Appreciate your time. This is cloud native at scale special presentation with Platform nine. Really unpacking super cloud Arlon open source and how to run large scale applications on the cloud, cloud native develop for developers. And John Furrier with the cube. Thanks for Washington. We'll stay tuned for another great segment coming right up. Hey, welcome back everyone to Super Cloud 22. I'm John Fur, host of the Cuba here all day talking about the future of cloud. Where's it all going? Making it super multi-cloud is around the corner and public cloud is winning. Got the private cloud on premise and Edge. Got a great guest here, Vascar Gorde, CEO of Platform nine, just on the panel on Kubernetes. An enabler blocker. Welcome back. Great to have you on. >>Good to see you >>Again. So Kubernetes is a blocker enabler by, with a question mark I put on on there. Panel was really to discuss the role of Kubernetes. Now great conversation operations is impacted. What's just thing about what you guys are doing at Platform nine? Is your role there as CEO and the company's position, kind of like the world spun into the direction of Platform nine while you're at the helm, right? >>Absolutely. In fact, things are moving very well and since they came to us, it was an insight to call ourselves the platform company eight years ago, right? So absolutely whether you are doing it in public clouds or private clouds, you know, the application world is moving very fast in trying to become digital and cloud native. There are many options for you to run the infrastructure. The biggest blocking factor now is having a unified platform. And that's what where we come into >>Patrick, we were talking before we came on stage here about your background and we were kind of talking about the glory days in 2000, 2001 when the first ASPs application service providers came out. Kind of a SaaS vibe, but that was kind of all kind of cloud-like >>It wasn't, >>And web services started then too. So you saw that whole growth. Now, fast forward 20 years later, 22 years later, where we are now, when you look back then to here and all the different cycles, >>In fact, you know, as we were talking offline, I was in one of those ASPs in the year 2000 where it was a novel concept of saying we are providing a software and a capability as a service, right? You sign up and start using it. I think a lot has changed since then. The tooling, the tools, the technology has really skyrocketed. The app development environment has really taken off exceptionally well. There are many, many choices of infrastructure now, right? So I think things are in a way the same but also extremely different. But more importantly now for any company, regardless of size, to be a digital native, to become a digital company is extremely mission critical. It's no longer a nice to have everybody's in the journey somewhere. >>Everyone is going digital transformation here. Even on a so-called downturn recession that's upcoming inflations sea year. It's interesting. This is the first downturn, the history of the world where the hyperscale clouds have been pumping on all cylinders as an economic input. And if you look at the tech trends, GDPs down, but not tech. Nope. Cause pandemic showed everyone digital transformation is here and more spend and more growth is coming even in, in tech. So this is a unique factor which proves that that digital transformation's happening and company, every company will need a super cloud. >>Everyone, every company, regardless of size, regardless of location, has to become modernize their infrastructure. And modernizing infrastructure is not just some, you know, new servers and new application tools. It's your approach, how you're serving your customers, how you're bringing agility in your organization. I think that is becoming a necessity for every enterprise to survive. >>I wanna get your thoughts on Super Cloud because one of the things Dave Alon and I want to do with Super Cloud and calling it that was we, I, I personally, and I know Dave as well, he can, I'll speak from, he can speak for himself. We didn't like multi-cloud. I mean not because Amazon said don't call things multi-cloud, it just didn't feel right. I mean everyone has multiple clouds by default. If you're running productivity software, you have Azure and Office 365. But it wasn't truly distributed. It wasn't truly decentralized, it wasn't truly cloud enabled. It didn't, it felt like they're not ready for a market yet. Yet public clouds booming on premise. Private cloud and Edge is much more on, you know, more, More dynamic, more unreal. >>Yeah. I think the reason why we think Super cloud is a better term than multi-cloud. Multi-cloud are more than one cloud, but they're disconnected. Okay, you have a productivity cloud, you have a Salesforce cloud, you may have, everyone has an internal cloud, right? So, but they're not connected. So you can say, okay, it's more than one cloud. So it's, you know, multi-cloud. But super cloud is where you are actually trying to look at this holistically. Whether it is on-prem, whether it is public, whether it's at the edge, it's a store at the branch. You are looking at this as one unit. And that's where we see the term super cloud is more applicable because what are the qualities that you require if you're in a super cloud, right? You need choice of infrastructure, you need, but at the same time you need a single pan or a single platform for you to build your innovations on, regardless of which cloud you're doing it on, right? So I think Super Cloud is actually a more tightly integrated orchestrated management philosophy we think. >>So let's get into some of the super cloud type trends that we've been reporting on. Again, the purpose of this event is as a pilot to get the conversations flowing with, with the influencers like yourselves who are running companies and building products and the builders, Amazon and Azure are doing extremely well. Google's coming up in third Cloudworks in public cloud. We see the use cases on premises use cases. Kubernetes has been an interesting phenomenon because it's become from the developer side a little bit, but a lot of ops people love Kubernetes. It's really more of an ops thing. You mentioned OpenStack earlier. Kubernetes kind of came out of that open stack. We need an orchestration. And then containers had a good shot with, with Docker. They re pivoted the company. Now they're all in an open source. So you got containers booming and Kubernetes as a new layer there. >>What's, >>What's the take on that? What does that really mean? Is that a new defacto enabler? It >>Is here. It's for here for sure. Every enterprise somewhere in the journey is going on. And you know, most companies are, 70 plus percent of them have 1, 2, 3 container based, Kubernetes based applications now being rolled out. So it's very much here. It is in production at scale by many customers. And it, the beauty of it is yes, open source, but the biggest gating factor is the skill set. And that's where we have a phenomenal engineering team, right? So it's, it's one thing to buy a tool and >>Just be clear, you're a managed service for Kubernetes. >>We provide, provide a software platform for cloud acceleration as a service and it can run anywhere. It can run in public private. We have customers who do it in truly multi-cloud environments. It runs on the edge, it runs at this in stores about thousands of stores in a retailer. So we provide that and also for specific segments where data sovereignty and data residency are key regulatory reasons. We also un on-prem as an air gap version. Can >>You give an example on how you guys are deploying your platform to enable a super cloud experience for your customer? Right. >>So I'll give you two different examples. One is a very large networking company, public networking company. They have hundreds of products, hundreds of r and d teams that are building different, different products. And if you look at few years back, each one was doing it on a different platforms, but they really needed to bring the agility. And they worked with us now over three years where we are their build test dev pro platform where all their products are built on, right? And it has dramatically increased their agility to release new products. Number two, it actually is a light out operation. In fact, the customer says like, like the Maytag service person, cuz we provide it as a service and it barely takes one or two people to maintain it for them. >>So it's kinda like an SRE vibe. One person managing a >>Large 4,000 engineers building infrastructure >>On their tools, >>Whatever they want on their tools. They're using whatever app development tools they use, but they use our platform. What >>Benefits are they seeing? Are they seeing speed? >>Speed, definitely. Okay. Definitely they're speeding. Speed uniformity because now they're building able to build, so their customers who are using product A and product B are seeing a similar set of tools that are being used. >>So a big problem that's coming outta this super cloud event that we're, we're seeing and we heard it all here, ops and security teams. Cause they're kind of part of one thing, but option security specifically need to catch up speed wise. Are you delivering that value to ops and security? Right? >>So we, we work with ops and security teams and infrastructure teams and we layer on top of that. We have like a platform team. If you think about it, depending on where you have data centers, where you have infrastructure, you have multiple teams, okay, but you need a unified platform. Who's your buyer? Our buyer is usually, you know, the product divisions of companies that are looking at or the CTO would be a buyer for us functionally cio definitely. So it it's, it's somewhere in the DevOps to infrastructure. But the ideal one we are beginning to see now many large corporations are really looking at it as a platform and saying we have a platform group on which any app can be developed and it is run on any infrastructure. So the platform engineering teams. So >>You working two sides to that coin. You've got the dev side and then >>And then infrastructure >>Side. >>Okay. Another customer that I give an example, which I would say is kind of the edge of the store. So they have thousands of stores. Retail, retail, you know food retailer, right? They have thousands of stores that are on the globe, 50,000, 60,000. And they really want to enhance the customer experience that happens when you either order the product or go into the store and pick up your product or buy or browse or sit there. They have applications that were written in the nineties and then they have very modern AIML applications today. They want something that will not have to send an IT person to install a rack in the store or they can't move everything to the cloud because the store operations has to be local. The menu changes based on it's classic edge. It's classic edge, yeah. Right? They can't send it people to go install rack access servers then they can't sell software people to go install the software and any change you wanna put through that, you know, truck roll. So they've been working with us where all they do is they ship, depending on the size of the store, one or two or three little servers with instructions that >>You, you say little servers like how big one like a box, like a small little box, >>Right? And all the person in the store has to do like what you and I do at home and we get a, you know, a router is connect the power, connect the internet and turn the switch on. And from there we pick it up. >>Yep. >>We provide the operating system, everything and then the applications are put on it. And so that dramatically brings the velocity for them. They manage thousands of >>Them. True plug and play >>Two, plug and play thousands of stores. They manage it centrally. We do it for them, right? So, so that's another example where on the edge then we have some customers who have both a large private presence and one of the public clouds. Okay. But they want to have the same platform layer of orchestration and management that they can use regardless of the locations. >>So you guys got some success. Congratulations. Got some traction there. It's awesome. The question I want to ask you is that's come up is what is truly cloud native? Cuz there's lift and shift of the cloud >>That's not cloud native. >>Then there's cloud native. Cloud native seems to be the driver for the super cloud. How do you talk to customers? How do you explain when someone says what's cloud native, what isn't cloud native? >>Right. Look, I think first of all, the best place to look at what is the definition and what are the attributes and characteristics of what is truly a cloud native, is CNC foundation. And I think it's very well documented, very well. >>Tucan, of course Detroit's >>Coming so, so it's already there, right? So we follow that very closely, right? I think just lifting and shifting your 20 year old application onto a data center somewhere is not cloud native. Okay? You can't put to cloud, not you have to rewrite and redevelop your application in business logic using modern tools. Hopefully more open source and, and I think that's what Cloudnative is and we are seeing a lot of our customers in that journey. Now everybody wants to be cloudnative, but it's not that easy, okay? Because it's, I think it's first of all, skill set is very important. Uniformity of tools that there's so many tools there. Thousands and thousands of tools you could spend your time figuring out which tool to use. Okay? So I think the complexity is there, but the business benefits of agility and uniformity and customer experience are truly being done. >>And I'll give you an example, I don't know how clear native they are, right? And they're not a customer of ours, but you order pizzas, you do, right? If you just watch the pizza industry, how dominoes actually increase their share and mind share and wallet share was not because they were making better pizzas or not, I don't know anything about that, but the whole experience of how you order, how you watch what's happening, how it's delivered. There were a pioneer in it. To me, those are the kinds of customer experiences that cloud native can provide. >>Being agility and having that flow to the application changes what the expectations >>Are >>For the customer. Customer, >>The customer's expectations change, right? Once you get used to a better customer experience, you learn. >>That's to wrap it up. I wanna just get your perspective again. One of the benefits of chatting with you here and having you part of the Super Cloud 22 is you've seen many cycles, you have a lot of insights. I want to ask you, given your career where you've been and what you've done and now let's CEO platform nine, how would you compare what's happening now with other inflection points in the industry? And you've been, again, you've been an entrepreneur, you sold your company to Oracle, you've been seeing the big companies, you've seen the different waves. What's going on right now put into context this moment in time around Super Cloud. >>Sure. I think as you said, a lot of battles. CARSs being been in an asb, being in a real time software company, being in large enterprise software houses and a transformation. I've been on the app side, I did the infrastructure right and then tried to build our own platforms. I've gone through all of this myself with lot of lessons learned in there. I think this is an event which is happening now for companies to go through to become cloud native and digitalize. If I were to look back and look at some parallels of the tsunami that's going on is a couple of paddles come to me. One is, think of it, which was forced to honors like y2k. Everybody around the world had to have a plan, a strategy, and an execution for y2k. I would say the next big thing was e-commerce. I think e-commerce has been pervasive right across all industries. >>And disruptive. >>And disruptive, extremely disruptive. If you did not adapt and adapt and accelerate your e-commerce initiative, you were, it was an existence question. Yeah. I think we are at that pivotal moment now in companies trying to become digital and cloudnative. You know, that is what I see >>Happening there. I think that that e-commerce is interesting and I think just to riff with you on that is that it's disrupting and refactoring the business models. I think that is something that's coming out of this is that it's not just completely changing the gain, it's just changing how you operate, >>How you think and how you operate. See, if you think about the early days of e-commerce, just putting up a shopping cart that made you an e-commerce or e retailer or an e e e customer, right? Or so. I think it's the same thing now is I think this is a fundamental shift on how you're thinking about your business. How are you gonna operate? How are you gonna service your customers? I think it requires that just lift and shift is not gonna work. >>Nascar, thank you for coming on, spending the time to come in and share with our community and being part of Super Cloud 22. We really appreciate, we're gonna keep this open. We're gonna keep this conversation going even after the event, to open up and look at the structural changes happening now and continue to look at it in the open in the community. And we're gonna keep this going for, for a long, long time as we get answers to the problems that customers are looking for with cloud cloud computing. I'm Sean Fur with Super Cloud 22 in the Cube. Thanks for watching. >>Thank you. Thank you. >>Hello and welcome back. This is the end of our program, our special presentation with Platform nine on cloud native at scale, enabling the super cloud. We're continuing the theme here. You heard the interviews Super Cloud and its challenges, new opportunities around solutions around like Platform nine and others with Arlon. This is really about the edge situations on the internet and managing the edge multiple regions, avoiding vendor lock in. This is what this new super cloud is all about. The business consequences we heard and and the wide ranging conversations around what it means for open source and the complexity problem all being solved. I hope you enjoyed this program. There's a lot of moving pieces and things to configure with cloud native install, all making it easier for you here with Super Cloud and of course Platform nine contributing to that. Thank you for watching.

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

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

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

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

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

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

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

>>Welcome back everyone, to the special presentation of Cloud Native at scale, the Cube and Platform nine special presentation going in and digging into the next generation super cloud infrastructure as code and the future of application development. We're here with Bickley, who's the chief architect and co-founder of Platform nine Pick. Great to see you Cube alumni. We, we met at an OpenStack event in about eight years ago, or well later, earlier when OpenStack was going. Great to see you and great to see congratulations on the success of Platform nine. Thank >>You very much. >>Yeah. You guys have been at this for a while and this is really the, the, the year we're seeing the, the crossover of Kubernetes because of what happens with containers. Everyone now has realized, and you've seen what Docker's doing with the new docker, the open source, Docker now just the success of containerization, right? And now the Kubernetes layer that we've been working on for years is coming, Bearing fruit. This is huge. >>Exactly. Yes. >>And so as infrastructures code comes in, we talked to Basco talking about Super Cloud. I met her about, you know, the new Arlon, our R lawn, and you guys just launched the infrastructures code is going to another level, and then it's always been DevOps infrastructures code. That's been the ethos that's been like from day one, developers just code. Then you saw the rise of serverless and you see now multi-cloud or on the horizon. Connect the dots for us. What is the state of infrastructures code today? >>So I think, I think I'm, I'm glad you mentioned it. Everybody or most people know about infrastructures code, but with Kubernetes, I think that project has evolved at the concept even further. And these dates, it's infrastructure is configuration, right? So, which is an evolution of infrastructure as code. So instead of telling the system, here's how I want my infrastructure by telling it, you know, do step A, B, C, and D. Instead, with Kubernetes you can describe your desired state declaratively using things called manifest resources. And then the system kind of magically figures it out and tries to converge the state towards the one that you specified. So I think it's, it's a even better version of infrastructures code. Yeah, >>Yeah. And that really means it developer just accessing resources. Okay, not clearing, Okay, give me some compute. Stand me up some, Turn the lights on, turn 'em off, turn 'em on. That's kind of where we see this going. And I like the configuration piece. Some people say composability, I mean, now with open source, so popular, you don't have to have to write a lot of code, this code being developed. And so it's integration, it's configuration. These are areas that we're starting to see computer science principles around automation, machine learning, assisting open source. Cuz you've got a lot of code that's right in hearing software, supply chain issues. So infrastructure as code has to factor in these, these new dynamics. Can you share your opinion on these new dynamics of, as open source grows, the glue layers, the configurations, the integration, what are the core issues? >>I think one of the major core issues is with all that power comes complexity, right? So, you know, despite its expressive power systems like Kubernetes and declarative APIs let you express a lot of complicated and complex stacks, right? But you're dealing with hundreds if not thousands of these yamo files or resources. And so I think, you know, the emergence of systems and layers to help you manage that complexity is becoming a key challenge and opportunity in, in this space. The that's, >>I wrote a LinkedIn post today was comments about, you know, hey, enterprise is a new breed. The trend of SaaS companies moving our consumer comp consumer-like thinking into the enterprise has been happening for a long time, but now more than ever, you're seeing it the old way used to be solve complexity with more complexity and then lock the customer in. Now with open source, it's speed, simplification and integration, right? These are the new dynamic power dynamics for developers. Yeah. So as companies are starting to now deploy and look at Kubernetes, what are the things that need to be in place? Because you have some, I won't say technical debt, but maybe some shortcuts, some scripts here that make it look like infrastructure is code. People have done some things to simulate or or make infrastructure as code happen. Yes. But to do it at scale Yes. Is harder. What's your take on this? What's your view? >>It's hard because there's a per proliferation of methods, tools, technologies. So for example, today it's very common for DevOps and platform engineering tools, I mean, sorry, teams to have to deploy a large number of Kubernetes clusters, but then apply the applications and configurations on top of those clusters. And they're using a wide range of tools to do this, right? For example, maybe Ansible or Terraform or bash scripts to bring up the infrastructure and then the clusters. And then they may use a different set of tools such as Argo CD or other tools to apply configurations and applications on top of the clusters. So you have this sprawl of tools. You, you also have this sprawl of configurations and files because the more objects you're dealing with, the more resources you have to manage. And there's a risk of drift that people call that where, you know, you think you have things under control, but some people from various teams will make changes here and there and then before the end of the day systems break and you have no idea of tracking them. So I think there's real need to kind of unify, simplify, and try to solve these problems using a smaller, more unified set of tools and methodologies. And that's something that we try to do with this new project. Arlon. >>Yeah. So, so we're gonna get into Arlan in a second. I wanna get into the why Arlon. You guys announced that at our GoCon, which was put on here in Silicon Valley at the computer by, in two, where they had their own little day over there at their headquarters. But before we get there, Bacar, your CEO came on and he talked about Super Cloud at our in aural event. What's your definition of super cloud? If you had to kind of explain that to someone at a cocktail party or someone in the industry technical, how would you look at the super cloud trend that's emerging? It's become a thing. What's your, what would be your contribution to that definition or the narrative? >>Well, it's, it's, it's funny because I've actually heard of the term for the first time today, speaking to you earlier today. But I think based on what you said, I I already get kind of some of the, the gist and the, the main concepts. It seems like super cloud, the way I interpret that is, you know, clouds and infrastructure, programmable infrastructure, all of those things are becoming commodity in a way. And everyone's got their own flavor, but there's a real opportunity for people to solve real business problems by perhaps trying to abstract away, you know, all of those various implementations and then building better abstractions that are perhaps business or application specific to help companies and businesses solve real business problems. >>Yeah, I remember that's a great, great definition. I remember, not to date myself, but back in the old days, you know, IBM had a proprietary network operating system. So the deck for the mini computer vendors, deck net and SNA respectively. But T C P I P came out of the osi, the open systems interconnect and remember, ethernet beat token ring out. So not to get all nerdy for all the young kids out there, look, just look up token ring, you'll see, you've probably never heard of it. It's IBM's, you know, connection for the internet at the, the layer two is Amazon, the ethernet, right? So if T C P I P could be the Kubernetes and the container abstraction that made the industry completely change at that point in history. So at every major inflection point where there's been serious industry change and wealth creation and business value, there's been an abstraction Yes. Somewhere. Yes. What's your reaction to that? >>I think this is, I think a saying that's been heard many times in this industry and, and I forgot who originated it, but I think the saying goes like, there's no problem that can't be solved with another layer of indirection, right? And we've seen this over and over and over again where Amazon and its peers have inserted this layer that has simplified, you know, computing and, and infrastructure management. And I believe this trend is going to continue, right? The next set of problems are going to be solved with these insertions of additional abstraction layers. I think that that's really a, yeah, >>It's >>Gonna >>Continue. It's interesting. I just, when I wrote another post today on LinkedIn called the Silicon Wars AMD stock is down arm has been on a rise. We've remember pointing for many years now, that arm's gonna be hugely, it has become true. If you look at the success of the infrastructure as a service layer across the clouds, Azure, aws, Amazon's clearly way ahead of everybody. The stuff that they're doing with the silicon and the physics and the, the atoms, the pro, you know, this is where the innovation, they're going so deep and so strong at ISAs, the more that they get that gets come on, they have more performance. So if you're an app developer, wouldn't you want the best performance and you'd wanna have the best abstraction layer that gives you the most ability to do infrastructures, code or infrastructure for configuration, for provisioning, for managing services. And you're seeing that today with service MeSHs, a lot of action going on in the service mesh area in in this community of, of co con, which will be a covering. So that brings up the whole what's next? You guys just announced our lawn at ar GoCon, which came out of Intuit. We've had Mariana Tessel at our super cloud event. She's the cto, you know, they're all in the cloud. So they contributed that project. Where did Arlon come from? What was the origination? What's the purpose? Why our lawn, why this announcement? >>Yeah, so the, the inception of the project, this was the result of us realizing that problem that we spoke about earlier, which is complexity, right? With all of this, these clouds, these infrastructure, all the variations around and, you know, compute storage networks and the proliferation of tools we talked about the Ansibles and Terraforms and Kubernetes itself, you can think of that as another tool, right? We saw a need to solve that complexity problem, and especially for people and users who use Kubernetes at scale. So when you have, you know, hundreds of clusters, thousands of applications, thousands of users spread out over many, many locations, there, there needs to be a system that helps simplify that management, right? So that means fewer tools, more expressive ways of describing the state that you want and more consistency. And, and that's why, you know, we built Arlan and we built it recognizing that many of these problems or sub problems have already been solved. So Arlon doesn't try to reinvent the wheel, it instead rests on the shoulders of several giants, right? So for example, Kubernetes is one building block, GI ops, and Argo CD is another one, which provides a very structured way of applying configuration. And then we have projects like cluster API and cross plane, which provide APIs for describing infrastructure. So arlon takes all of those building blocks and builds a thin layer, which gives users a very expressive way of defining configuration and desired state. So that's, that's kind of the inception of, >>And what's the benefit of that? What does that give the, what does that give the developer, the user, in this case, >>The developers, the, the platform engineer, team members, the DevOps engineers, they get a a ways to provision not just infrastructure and clusters, but also applications and configurations. They get a way, a system for provisioning, configuring, deploying, and doing life cycle management in a, in a much simpler way. Okay. Especially as I said, if you're dealing with a large number of applications. >>So it's like an operating fabric, if you will. Yes. For them. Okay, So let's get into what that means for up above and below the, the, this abstraction or thin layer below as the infrastructure. We talked a lot about what's going on below that. Yeah. Above our workloads. At the end of the day, you know, I talk to CXOs and IT folks that, that are now DevOps engineers. They care about the workloads and they want the infrastructure's code to work. They wanna spend their time getting in the weeds, figuring out what happened when someone made a push that that happened or something happened. They need observability and they need to, to know that it's working. That's right. And here's my workloads running effectively. So how do you guys look at the workload side of it? Cuz now you have multiple workloads on these fabric, right? >>So workloads, so Kubernetes has defined kind of a standard way to describe workloads. And you can, you know, tell Kubernetes, I want to run this container this particular way, or you can use other projects that are in the Kubernetes cloud native ecosystem, like K native, where you can express your application in more at a higher level, right? But what's also happening is in addition to the workloads, DevOps and platform engineering teams, they need to very often deploy the applications with the clusters themselves. Clusters are becoming this commodity. It's, it's becoming this host for the application and it kind of comes bundled with it. In many cases, it's like an appliance, right? So DevOps teams have to provision clusters at a really incredible rate and they need to tear them down. Clusters are becoming more, >>It's coming like an EC two instance, spin up a cluster. We've heard people used words like that. That's >>Right. And before arlon, you kind of had to do all of that using a different set of tools as, as I explained. So with Arlon you can kind of express everything together. You can say, I want a cluster with a health monitoring stack and a logging stack and this ingress controller and I want these applications and these security policies. You can describe all of that using something we call a profile. And then you can stamp out your app, your applications, and your clusters and manage them in a very, So >>It's essentially standard, like creates a mechanism. Exactly. Standardized, declarative kind of configurations. And it's like a playbook, deploy it. Now what's there is between say a script like I have scripts, I can just automate scripts >>Or yes, this is where that declarative API and infrastructures configuration comes in, right? Because scripts, yes, you can automate scripts, but the order in which they run matters, right? They can break, things can break in the middle and, and sometimes you need to debug them. Whereas the declarative way is much more expressive and powerful. You just tell the system what you want and then the system kind of figures it out. And there are these things about controllers, which will in the background reconcile all the state to converge towards your desire. It's a much more powerful, expressive and reliable way of getting things done. >>So infrastructure has configuration is built kind of on its super set of infrastructures code because it's an evolution. You need edge retro's code, but then you can configure the code by just saying do it. You basically declaring it saying Go, go do that. That's right. Okay, So, all right, so Cloudnative at scale, take me through your vision of what that means. Someone says, Hey, what does cloudnative at scale mean? What's success look like? How does it roll out in the future as you, not future next couple years? I mean, people are now starting to figure out, okay, it's not as easy as it sounds. Kubernetes has value. We're gonna hear this year at co con a lot of this, what does cloud native at scale >>Mean? Yeah, there are different interpretations, but if you ask me, when people think of scale, they think of a large number of deployments, right? Geographies, many, you know, supporting thousands or tens or millions of, of users. There, there's that aspect to scale. There's also an equally important a aspect of scale, which is also something that we, we try to address with Arlan. And that is just complexity for the people operating this or configuring this, right? So in order to describe that desired state, and in order to perform things like maybe upgrades or updates on a very large scale, you want the humans behind that to be able to express and direct the system to do that in, in relatively simple terms, right? And so we want the tools and the abstractions and the mechanisms available to the user to be as powerful but as simple as possible. So there's, I think there's gonna be a number and there have been a number of CNCF and cloud native projects that are trying to attack that complexity problem as well. And Arlon kind of falls in in that >>Category. Okay, So I'll put you on the spot road that Coan coming up, and obviously this will be shipping this segment series out before. What do you expect to see at Coan this year? What's the big story this year? What's the, what's the most important thing happening? Is it in the open source community and also within a lot of the, the people jocking for leadership. I know there's a lot of projects and still there's some white space in the overall systems map about the different areas get run time and there's their ability in all these different areas. What's the, where's the action? Where, where's the smoke? Where's the fire? Where's the piece? Where's the tension? >>Yeah, so I think one thing that has been happening over the past couple of cub cons and I expect to continue, and, and that is the, the word on the street is Kubernetes is getting boring, right? Which is good, right? >>Boring means simple. >>Well, well >>Maybe, >>Yeah, >>Invisible, >>No drama, right? So, so the, the rate of change of the Kubernetes features and, and all that has slowed, but in, in a, in a positive way. But there's still a general sentiment and feeling that there's just too much stuff. If you look at a stack necessary for hosting applications based on Kubernetes, there're just still too many moving parts, too many components, right? Too much complexity. I go, I keep going back to the complexity problem. So I expect Cube Con and all the vendors and the players and the startups and the people there to continue to focus on that complexity problem and introduce further simplifications to, to the stack. Yeah. >>B, you've had a storied career VMware over decades with them, obviously with 12 years, with 14 years or something like that. Big number. Co-founder here, a platform. Now you guys been around for a while at this game. We, man, we talked about OpenStack, that project you, we interviewed at one of their events. So OpenStack was the beginning of that, this new revolution. And I remember the early days it was, it wasn't supposed to be an alternative to Amazon, but it was a way to do more cloud cloud native. I think we had a cloud a Rod team at that time. We to joke we, you know, about, about the dream. It's happening now, now at Platform nine. You guys have been doing this for a while. What's the, what are you most excited about as the chief architect? What did you guys double down on? What did you guys pivot from or two, did you do any pivots? Did you extend out certain areas? Cuz you guys are in a good position right now, a lot of DNA in Cloud native. What are you most excited about and what does Platform nine bring to the table for customers and for people in the industry watching this? >>Yeah, so I think our mission really hasn't changed over the years, right? It's been always about taking complex open source software because open source software, it's powerful. It solves new problems, you know, every year and you have new things coming out all the time, right? OpenStack was an example where the Kubernetes took the world by storm. But there's always that complexity of, you know, just configuring it, deploying it, running it, operating it. And our mission has always been that we will take all that complexity and just make it, you know, easy for users to consume regardless of the technology, right? So the successor to Kubernetes, you know, I don't have a crystal ball, but you know, you have some indications that people are coming up of new and simpler ways of running applications. There are many projects around there who knows what's coming next year or the year after that. But platform will a, platform nine will be there and we will, you know, take the innovations from the, the, the community. We will contribute our own innovations and make all of those things very consumable to customers. >>Simpler, faster, cheaper. Exactly. Always a good business model technically to make that happen. Yeah, I think the reigning in the chaos is key, you know, Now we have now visibility into the scale. Final question before we depart this segment. What is at scale, how many clusters do you see that would be a, a watermark for an at scale conversation around an enterprise? Is it workloads we're looking at or, or clusters? How would you Yeah, how would you describe that? When people try to squint through and evaluate what's a scale, what's the at scale kind of threshold? >>Yeah. And, and the number of clusters doesn't tell the whole story because clusters can be small in terms of the number of nodes or they can be large. But roughly speaking when we say, you know, large scale cluster deployments, we're talking about maybe hundreds, two thousands. >>Yeah. And final final question, what's the role of the hyperscalers? You got AWS continuing to do well, but they got their core ias, they got a PAs, they're not too too much putting a SaaS out there. They have some SaaS apps, but mostly it's the ecosystem. They have marketplaces doing over $2 billion tran billions of transactions a year and, and it's just like, just sitting there. It hasn't really, they're now innovating on it, but that's gonna change ecosystems. What's the role the cloud play in the cloud need of its scale? >>The, the hyperscalers? >>Yeah. A's Azure, Google >>You mean from a business perspective, technical, they're, they have their own interests that, you know, that they're, they will keep catering to, they, they will continue to find ways to lock their users into their ecosystem of services and, and APIs. So I don't think that's gonna change, right? They're just gonna keep >>Well, they got great I performance, I mean from a, from a hardware standpoint, yes. That's gonna be key, right? >>Yes. I think the, the move from X 86 being the dominant way and platform to run workloads is changing, right? That, that, that, that, and I think the, the hyperscalers really want to be in the game in terms of, you know, the, the new risk and arm ecosystems and, and platforms. >>Yeah. Not joking aside, Paul Morritz, when he was the CEO of VMware, when he took over once said, and I remember our first year doing the cube, Oh, the cloud is one big distributed computer. It's, it's hardware and you got software and you got middleware and he kind of over, well he's kind of tongue in cheek, but really you're talking about large compute and sets of services that is essentially a distributed computer. >>Yes, >>Exactly. It's, we're back in the same game. Vic, thank you for coming on the segment. Appreciate your time. This is cloud native at scale special presentation with Platform nine. Really unpacking super Cloud Arlon open source and how to run large scale applications on the cloud. Cloud Native Phil for developers and John Furrier with the cube. Thanks for Washington. We'll stay tuned for another great segment coming right up.