>>From the Cube Studios in Palo Alto in Boston, bringing you data-driven insights from the cube and E T R. This is breaking analysis with Dave Valante. >>Making technology predictions in 2022 was tricky business, especially if you were projecting the performance of markets or identifying I P O prospects and making binary forecast on data AI and the macro spending climate and other related topics in enterprise tech 2022, of course was characterized by a seesaw economy where central banks were restructuring their balance sheets. The war on Ukraine fueled inflation supply chains were a mess. And the unintended consequences of of forced march to digital and the acceleration still being sorted out. Hello and welcome to this week's weekly on Cube Insights powered by E T R. In this breaking analysis, we continue our annual tradition of transparently grading last year's enterprise tech predictions. And you may or may not agree with our self grading system, but look, we're gonna give you the data and you can draw your own conclusions and tell you what, tell us what you think. >>All right, let's get right to it. So our first prediction was tech spending increases by 8% in 2022. And as we exited 2021 CIOs, they were optimistic about their digital transformation plans. You know, they rushed to make changes to their business and were eager to sharpen their focus and continue to iterate on their digital business models and plug the holes that they, the, in the learnings that they had. And so we predicted that 8% rise in enterprise tech spending, which looked pretty good until Ukraine and the Fed decided that, you know, had to rush and make up for lost time. We kind of nailed the momentum in the energy sector, but we can't give ourselves too much credit for that layup. And as of October, Gartner had it spending growing at just over 5%. I think it was 5.1%. So we're gonna take a C plus on this one and, and move on. >>Our next prediction was basically kind of a slow ground ball. The second base, if I have to be honest, but we felt it was important to highlight that security would remain front and center as the number one priority for organizations in 2022. As is our tradition, you know, we try to up the degree of difficulty by specifically identifying companies that are gonna benefit from these trends. So we highlighted some possible I P O candidates, which of course didn't pan out. S NQ was on our radar. The company had just had to do another raise and they recently took a valuation hit and it was a down round. They raised 196 million. So good chunk of cash, but, but not the i p O that we had predicted Aqua Securities focus on containers and cloud native. That was a trendy call and we thought maybe an M SS P or multiple managed security service providers like Arctic Wolf would I p o, but no way that was happening in the crummy market. >>Nonetheless, we think these types of companies, they're still faring well as the talent shortage in security remains really acute, particularly in the sort of mid-size and small businesses that often don't have a sock Lacework laid off 20% of its workforce in 2022. And CO C e o Dave Hatfield left the company. So that I p o didn't, didn't happen. It was probably too early for Lacework. Anyway, meanwhile you got Netscope, which we've cited as strong in the E T R data as particularly in the emerging technology survey. And then, you know, I lumia holding its own, you know, we never liked that 7 billion price tag that Okta paid for auth zero, but we loved the TAM expansion strategy to target developers beyond sort of Okta's enterprise strength. But we gotta take some points off of the failure thus far of, of Okta to really nail the integration and the go to market model with azero and build, you know, bring that into the, the, the core Okta. >>So the focus on endpoint security that was a winner in 2022 is CrowdStrike led that charge with others holding their own, not the least of which was Palo Alto Networks as it continued to expand beyond its core network security and firewall business, you know, through acquisition. So overall we're gonna give ourselves an A minus for this relatively easy call, but again, we had some specifics associated with it to make it a little tougher. And of course we're watching ve very closely this this coming year in 2023. The vendor consolidation trend. You know, according to a recent Palo Alto network survey with 1300 SecOps pros on average organizations have more than 30 tools to manage security tools. So this is a logical way to optimize cost consolidating vendors and consolidating redundant vendors. The E T R data shows that's clearly a trend that's on the upswing. >>Now moving on, a big theme of 2020 and 2021 of course was remote work and hybrid work and new ways to work and return to work. So we predicted in 2022 that hybrid work models would become the dominant protocol, which clearly is the case. We predicted that about 33% of the workforce would come back to the office in 2022 in September. The E T R data showed that figure was at 29%, but organizations expected that 32% would be in the office, you know, pretty much full-time by year end. That hasn't quite happened, but we were pretty close with the projection, so we're gonna take an A minus on this one. Now, supply chain disruption was another big theme that we felt would carry through 2022. And sure that sounds like another easy one, but as is our tradition, again we try to put some binary metrics around our predictions to put some meat in the bone, so to speak, and and allow us than you to say, okay, did it come true or not? >>So we had some data that we presented last year and supply chain issues impacting hardware spend. We said at the time, you can see this on the left hand side of this chart, the PC laptop demand would remain above pre covid levels, which would reverse a decade of year on year declines, which I think started in around 2011, 2012. Now, while demand is down this year pretty substantially relative to 2021, I D C has worldwide unit shipments for PCs at just over 300 million for 22. If you go back to 2019 and you're looking at around let's say 260 million units shipped globally, you know, roughly, so, you know, pretty good call there. Definitely much higher than pre covid levels. But so what you might be asking why the B, well, we projected that 30% of customers would replace security appliances with cloud-based services and that more than a third would replace their internal data center server and storage hardware with cloud services like 30 and 40% respectively. >>And we don't have explicit survey data on exactly these metrics, but anecdotally we see this happening in earnest. And we do have some data that we're showing here on cloud adoption from ET R'S October survey where the midpoint of workloads running in the cloud is around 34% and forecast, as you can see, to grow steadily over the next three years. So this, well look, this is not, we understand it's not a one-to-one correlation with our prediction, but it's a pretty good bet that we were right, but we gotta take some points off, we think for the lack of unequivocal proof. Cause again, we always strive to make our predictions in ways that can be measured as accurate or not. Is it binary? Did it happen, did it not? Kind of like an O K R and you know, we strive to provide data as proof and in this case it's a bit fuzzy. >>We have to admit that although we're pretty comfortable that the prediction was accurate. And look, when you make an hard forecast, sometimes you gotta pay the price. All right, next, we said in 2022 that the big four cloud players would generate 167 billion in IS and PaaS revenue combining for 38% market growth. And our current forecasts are shown here with a comparison to our January, 2022 figures. So coming into this year now where we are today, so currently we expect 162 billion in total revenue and a 33% growth rate. Still very healthy, but not on our mark. So we think a w s is gonna miss our predictions by about a billion dollars, not, you know, not bad for an 80 billion company. So they're not gonna hit that expectation though of getting really close to a hundred billion run rate. We thought they'd exit the year, you know, closer to, you know, 25 billion a quarter and we don't think they're gonna get there. >>Look, we pretty much nailed Azure even though our prediction W was was correct about g Google Cloud platform surpassing Alibaba, Alibaba, we way overestimated the performance of both of those companies. So we're gonna give ourselves a C plus here and we think, yeah, you might think it's a little bit harsh, we could argue for a B minus to the professor, but the misses on GCP and Alibaba we think warrant a a self penalty on this one. All right, let's move on to our prediction about Supercloud. We said it becomes a thing in 2022 and we think by many accounts it has, despite the naysayers, we're seeing clear evidence that the concept of a layer of value add that sits above and across clouds is taking shape. And on this slide we showed just some of the pickup in the industry. I mean one of the most interesting is CloudFlare, the biggest supercloud antagonist. >>Charles Fitzgerald even predicted that no vendor would ever use the term in their marketing. And that would be proof if that happened that Supercloud was a thing and he said it would never happen. Well CloudFlare has, and they launched their version of Supercloud at their developer week. Chris Miller of the register put out a Supercloud block diagram, something else that Charles Fitzgerald was, it was was pushing us for, which is rightly so, it was a good call on his part. And Chris Miller actually came up with one that's pretty good at David Linthicum also has produced a a a A block diagram, kind of similar, David uses the term metacloud and he uses the term supercloud kind of interchangeably to describe that trend. And so we we're aligned on that front. Brian Gracely has covered the concept on the popular cloud podcast. Berkeley launched the Sky computing initiative. >>You read through that white paper and many of the concepts highlighted in the Supercloud 3.0 community developed definition align with that. Walmart launched a platform with many of the supercloud salient attributes. So did Goldman Sachs, so did Capital One, so did nasdaq. So you know, sorry you can hate the term, but very clearly the evidence is gathering for the super cloud storm. We're gonna take an a plus on this one. Sorry, haters. Alright, let's talk about data mesh in our 21 predictions posts. We said that in the 2020s, 75% of large organizations are gonna re-architect their big data platforms. So kind of a decade long prediction. We don't like to do that always, but sometimes it's warranted. And because it was a longer term prediction, we, at the time in, in coming into 22 when we were evaluating our 21 predictions, we took a grade of incomplete because the sort of decade long or majority of the decade better part of the decade prediction. >>So last year, earlier this year, we said our number seven prediction was data mesh gains momentum in 22. But it's largely confined and narrow data problems with limited scope as you can see here with some of the key bullets. So there's a lot of discussion in the data community about data mesh and while there are an increasing number of examples, JP Morgan Chase, Intuit, H S P C, HelloFresh, and others that are completely rearchitecting parts of their data platform completely rearchitecting entire data platforms is non-trivial. There are organizational challenges, there're data, data ownership, debates, technical considerations, and in particular two of the four fundamental data mesh principles that the, the need for a self-service infrastructure and federated computational governance are challenging. Look, democratizing data and facilitating data sharing creates conflicts with regulatory requirements around data privacy. As such many organizations are being really selective with their data mesh implementations and hence our prediction of narrowing the scope of data mesh initiatives. >>I think that was right on J P M C is a good example of this, where you got a single group within a, within a division narrowly implementing the data mesh architecture. They're using a w s, they're using data lakes, they're using Amazon Glue, creating a catalog and a variety of other techniques to meet their objectives. They kind of automating data quality and it was pretty well thought out and interesting approach and I think it's gonna be made easier by some of the announcements that Amazon made at the recent, you know, reinvent, particularly trying to eliminate ET t l, better connections between Aurora and Redshift and, and, and better data sharing the data clean room. So a lot of that is gonna help. Of course, snowflake has been on this for a while now. Many other companies are facing, you know, limitations as we said here and this slide with their Hadoop data platforms. They need to do new, some new thinking around that to scale. HelloFresh is a really good example of this. Look, the bottom line is that organizations want to get more value from data and having a centralized, highly specialized teams that own the data problem, it's been a barrier and a blocker to success. The data mesh starts with organizational considerations as described in great detail by Ash Nair of Warner Brothers. So take a listen to this clip. >>Yeah, so when people think of Warner Brothers, you always think of like the movie studio, but we're more than that, right? I mean, you think of H B O, you think of t n t, you think of C N N. We have 30 plus brands in our portfolio and each have their own needs. So the, the idea of a data mesh really helps us because what we can do is we can federate access across the company so that, you know, CNN can work at their own pace. You know, when there's election season, they can ingest their own data and they don't have to, you know, bump up against, as an example, HBO if Game of Thrones is going on. >>So it's often the case that data mesh is in the eyes of the implementer. And while a company's implementation may not strictly adhere to Jamma Dani's vision of data mesh, and that's okay, the goal is to use data more effectively. And despite Gartner's attempts to deposition data mesh in favor of the somewhat confusing or frankly far more confusing data fabric concept that they stole from NetApp data mesh is taking hold in organizations globally today. So we're gonna take a B on this one. The prediction is shaping up the way we envision, but as we previously reported, it's gonna take some time. The better part of a decade in our view, new standards have to emerge to make this vision become reality and they'll come in the form of both open and de facto approaches. Okay, our eighth prediction last year focused on the face off between Snowflake and Databricks. >>And we realized this popular topic, and maybe one that's getting a little overplayed, but these are two companies that initially, you know, looked like they were shaping up as partners and they, by the way, they are still partnering in the field. But you go back a couple years ago, the idea of using an AW w s infrastructure, Databricks machine intelligence and applying that on top of Snowflake as a facile data warehouse, still very viable. But both of these companies, they have much larger ambitions. They got big total available markets to chase and large valuations that they have to justify. So what's happening is, as we've previously reported, each of these companies is moving toward the other firm's core domain and they're building out an ecosystem that'll be critical for their future. So as part of that effort, we said each is gonna become aggressive investors and maybe start doing some m and a and they have in various companies. >>And on this chart that we produced last year, we studied some of the companies that were targets and we've added some recent investments of both Snowflake and Databricks. As you can see, they've both, for example, invested in elation snowflake's, put money into Lacework, the Secur security firm, ThoughtSpot, which is trying to democratize data with ai. Collibra is a governance platform and you can see Databricks investments in data transformation with D B T labs, Matillion doing simplified business intelligence hunters. So that's, you know, they're security investment and so forth. So other than our thought that we'd see Databricks I p o last year, this prediction been pretty spot on. So we'll give ourselves an A on that one. Now observability has been a hot topic and we've been covering it for a while with our friends at E T R, particularly Eric Bradley. Our number nine prediction last year was basically that if you're not cloud native and observability, you are gonna be in big trouble. >>So everything guys gotta go cloud native. And that's clearly been the case. Splunk, the big player in the space has been transitioning to the cloud, hasn't always been pretty, as we reported, Datadog real momentum, the elk stack, that's open source model. You got new entrants that we've cited before, like observe, honeycomb, chaos search and others that we've, we've reported on, they're all born in the cloud. So we're gonna take another a on this one, admittedly, yeah, it's a re reasonably easy call, but you gotta have a few of those in the mix. Okay, our last prediction, our number 10 was around events. Something the cube knows a little bit about. We said that a new category of events would emerge as hybrid and that for the most part is happened. So that's gonna be the mainstay is what we said. That pure play virtual events are gonna give way to hi hybrid. >>And the narrative is that virtual only events are, you know, they're good for quick hits, but lousy replacements for in-person events. And you know that said, organizations of all shapes and sizes, they learn how to create better virtual content and support remote audiences during the pandemic. So when we set at pure play is gonna give way to hybrid, we said we, we i we implied or specific or specified that the physical event that v i p experience is going defined. That overall experience and those v i p events would create a little fomo, fear of, of missing out in a virtual component would overlay that serves an audience 10 x the size of the physical. We saw that really two really good examples. Red Hat Summit in Boston, small event, couple thousand people served tens of thousands, you know, online. Second was Google Cloud next v i p event in, in New York City. >>Everything else was, was, was, was virtual. You know, even examples of our prediction of metaverse like immersion have popped up and, and and, and you know, other companies are doing roadshow as we predicted like a lot of companies are doing it. You're seeing that as a major trend where organizations are going with their sales teams out into the regions and doing a little belly to belly action as opposed to the big giant event. That's a definitely a, a trend that we're seeing. So in reviewing this prediction, the grade we gave ourselves is, you know, maybe a bit unfair, it should be, you could argue for a higher grade, but the, but the organization still haven't figured it out. They have hybrid experiences but they generally do a really poor job of leveraging the afterglow and of event of an event. It still tends to be one and done, let's move on to the next event or the next city. >>Let the sales team pick up the pieces if they were paying attention. So because of that, we're only taking a B plus on this one. Okay, so that's the review of last year's predictions. You know, overall if you average out our grade on the 10 predictions that come out to a b plus, I dunno why we can't seem to get that elusive a, but we're gonna keep trying our friends at E T R and we are starting to look at the data for 2023 from the surveys and all the work that we've done on the cube and our, our analysis and we're gonna put together our predictions. We've had literally hundreds of inbounds from PR pros pitching us. We've got this huge thick folder that we've started to review with our yellow highlighter. And our plan is to review it this month, take a look at all the data, get some ideas from the inbounds and then the e t R of January surveys in the field. >>It's probably got a little over a thousand responses right now. You know, they'll get up to, you know, 1400 or so. And once we've digested all that, we're gonna go back and publish our predictions for 2023 sometime in January. So stay tuned for that. All right, we're gonna leave it there for today. You wanna thank Alex Myerson who's on production and he manages the podcast, Ken Schiffman as well out of our, our Boston studio. I gotta really heartfelt thank you to Kristen Martin and Cheryl Knight and their team. They helped get the word out on social and in our newsletters. Rob Ho is our editor in chief over at Silicon Angle who does some great editing for us. Thank you all. Remember all these podcasts are available or all these episodes are available is podcasts. Wherever you listen, just all you do Search Breaking analysis podcast, really getting some great traction there. Appreciate you guys subscribing. I published each week on wikibon.com, silicon angle.com or you can email me directly at david dot valante silicon angle.com or dm me Dante, or you can comment on my LinkedIn post. And please check out ETR AI for the very best survey data in the enterprise tech business. Some awesome stuff in there. This is Dante for the Cube Insights powered by etr. Thanks for watching and we'll see you next time on breaking analysis.

>>Hello everyone and welcome back to Motor City, Michigan. We're live from the Cube and my name is Savannah Peterson. Joined this afternoon with my co-host John Ferer. John, how you doing? Doing >>Great. This next segment's gonna be awesome about application modernization, scaling pluses. This is what's gonna, how are the next generation software revolution? It's gonna be >>Fun. You know, it's kind of been a theme of our day today is scale. And when we think about the complex orchestration platform that is Kubernetes, everyone wants to scale faster, quicker, more efficiently, and our guests are here to tell us all about that. Please welcome to Char and Andy, thank you so much for being here with us. You were on the Red Hat OpenShift team. Yeah. I suspect most of our audience is familiar, but just in case, let's give 'em a quick one-liner pitch so everyone's on the same page. Tell us about OpenShift. >>I, I'll take that one. OpenShift is our ES platform is our ES distribution. You can consume it as a self-managed platform or you can consume it as a managed service on on public clouds. And so we just call it all OpenShift. So it's basically Kubernetes, but you know, with a CNCF ecosystem around it to make things more easier. So maybe there's two >>Lights. So what does being at coupon mean for you? How does it feel to be here? What's your initial takes? >>Exciting. I'm having a fantastic time. I haven't been to coupon since San Diego, so it's great to be back in person and see old friends, make new friends, have hallway conversations. It's, it's great as an engineer trying to work in this ecosystem, just being able to, to be in the same place with these folks. >>And you gotta ask, before we came on camera, you're like, this is like my sixth co con. We were like, we're seven, you know, But that's a lot of co coupons. It >>Is, yes. I mean, so what, >>Yes. >>Take us status >>For sure. Where we are now. Compare and contrast co. Your first co con, just scope it out. What's the magnitude of change? If you had to put a pin on that, because there's a lot of new people coming in, they might not have seen where it's come from and how we got here is maybe not how we're gonna get to the next >>Level. I've seen it grow tremendously since the first one I went to, which I think was Austin several years ago. And what's great is seeing lots of new people interested in contributing and also seeing end users who are trying to figure out the best way to take advantage of this great ecosystem that we have. >>Awesome. And the project management side, you get the keys to the Kingdom with Red Hat OpenShift, which has been successful. Congratulations by the way. Thank you. We watched that grow and really position right on the wave. It's going great. What's the update on on the product? Kind of, you're in a good, good position right now. Yeah, >>No, we we're feeling good about it. It's all about our customers. Obviously the fact that, you know, we have thousands of customers using OpenShift as the cloud native platform, the container platform. We're very excited. The great thing about them is that, I mean you can go to like OpenShift Commons is kind of a user group that we run on the first day, like on Tuesday we ran. I mean you should see the number of just case studies that our customers went through there, you know? And it is fantastic to see that. I mean it's across so many different industries, across so many different use cases, which is very exciting. >>One of the things we've been reporting here in the Qla scene before, but here more important is just that if you take digital transformation to the, to its conclusion, the IT department and developers, they're not a department to serve the business. They are the business. Yes. That means that the developers are deciding things. Yeah. And running the business. Prove their code. Yeah. Okay. If that's, if that takes place, you gonna have scale. And we also said on many cubes, certainly at Red Hat Summit and other ones, the clouds are distributed computer, it's distributed computing. So you guys are focusing on this project, Andy, that you're working on kcp. >>Yes. >>Which is, I won't platform Kubernetes platform for >>Control >>Planes. Control planes. Yes. Take us through, what's the focus on why is that important and why is that relate to the mission of developers being in charge and large scale? >>Sure. So a lot of times when people are interested in developing on Kubernetes and running workloads, they need a cluster of course. And those are not cheap. It takes time, it takes money, it takes resources to get them. And so we're trying to make that faster and easier for, for end users and everybody involved. So with kcp, we've been able to take what looks like one normal Kubernetes and partition it. And so everybody gets a slice of it. You're an administrator in your little slice and you don't have to ask for permission to install new APIs and they don't conflict with anybody else's APIs. So we're really just trying to make it super fast and make it super flexible. So everybody is their own admin. >>So the developer basically looks at it as a resource blob. They can do whatever they want, but it's shared and provisioned. >>Yes. One option. It's like, it's like they have their own cluster, but you don't have to go through the process of actually provisioning a full >>Cluster. And what's the alternative? What's the what's, what's the, what's the benefit and what was the alternative to >>This? So the alternative, you spin up a full cluster, which you know, maybe that's three control plane nodes, you've got multiple workers, you've got a bunch of virtual machines or bare metal, or maybe you take, >>How much time does that take? Just ballpark. >>Anywhere from five minutes to an hour you can use cloud services. Yeah. Gke, E Ks and so on. >>Keep banging away. You're configuring. Yeah. >>Those are faster. Yeah. But it's still like, you still have to wait for that to happen and it costs money to do all of that too. >>Absolutely. And it's complex. Why do something that's been done, if there's a tool that can get you a couple steps down the path, which makes a ton of sense. Something that we think a lot when we're talking about scale. You mentioned earlier, Tohar, when we were chatting before the cams were alive, scale means a lot of different things. Can you dig in there a little bit? >>Yeah, I >>Mean, so when, when >>We talk about scale, >>We are talking about from a user perspective, we are talking about, you know, there are more users, there are more applications, there are more workloads, there are more services being run on Kubernetes now, right? So, and OpenShift. So, so that's one dimension of this scale. The other dimension of the scale is how do you manage all the underlying infrastructure, the clusters, the name spaces, and all the observability data, et cetera. So that's at least two levels of scale. And then obviously there's a third level of scale, which is, you know, there is scale across not just different clouds, but also from cloud to the edge. So there is that dimension of scale. So there are several dimensions of this scale. And the one that again, we are focused on here really is about, you know, this, the first one that I talk about is a user. And when I say user, it could be a developer, it could be an application architect, or it could be an application owner who wants to develop Kubernetes applications for Kubernetes and wants to publish those APIs, if you will, and make it discoverable and then somebody consumes it. So that's the scale we are talking about >>Here. What are some of the enterprise, you guys have a lot of customers, we've talked to you guys before many, many times and other subjects, Red Hat, I mean you guys have all the customers. Yeah. Enterprise, they've been there, done that. And you know, they're, they're savvy. Yeah. But the cloud is a whole nother ballgame. What are they thinking about? What's the psychology of the customer right now? Because now they have a lot of choices. Okay, we get it, we're gonna re-platform refactor apps, we'll keep some legacy on premises for whatever reasons. But cloud pretty much is gonna be the game. What's the mindset right now of the customer base? Where are they in their, in their psych? Not the executive, but more of the the operators or the developers? >>Yeah, so I mean, first of all, different customers are at different levels of maturity, I would say in this. They're all on a journey how I like to describe it. And in this journey, I mean, I see a customers who are really tip of the sphere. You know, they have containerized everything. They're cloud native, you know, they use best of tools, I mean automation, you know, complete automation, you know, quick deployment of applications and all, and life cycle of applications, et cetera. So that, that's kind of one end of this spectrum >>Advanced. Then >>The advances, you know, and, and I, you know, I don't, I don't have any specific numbers here, but I'd say there are quite a few of them. And we see that. And then there is kind of the middle who are, I would say, who are familiar with containers. They know what app modernization, what a cloud application means. They might have tried a few. So they are in the journey. They are kind of, they want to get there. They have some other kind of other issues, organizational or talent and so, so on and so forth. Kinds of issues to get there. And then there are definitely the quota, what I would call the lag arts still. And there's lots of them. But I think, you know, Covid has certainly accelerated a lot of that. I hear that. And there is definitely, you know, more, the psychology is definitely more towards what I would say public cloud. But I think where we are early also in the other trend that I see is kind of okay, public cloud great, right? So people are going there, but then there is the so-called edge also. Yeah. That is for various regions. You, you gotta have a kind of a regional presence, a edge presence. And that's kind of the next kind of thing taking off here. And we can talk more >>About it. Yeah, let's talk about that a little bit because I, as you know, as we know, we're very excited about Edge here at the Cube. Yeah. What types of trends are you seeing? Is that space emerges a little bit more firmly? >>Yeah, so I mean it's, I mean, so we, when we talk about Edge, you're talking about, you could talk about Edge as a, as a retail, I mean locations, right? >>Could be so many things edges everywhere. Everywhere, right? It's all around us. Quite literally. Even on the >>Scale. Exactly. In space too. You could, I mean, in fact you mentioned space. I was, I was going to >>Kinda, it's this world, >>My space actually Kubernetes and OpenShift running in space, believe it or not, you know, So, so that's the edge, right? So we have Industrial Edge, we have Telco Edge, we have a 5g, then we have, you know, automotive edge now and, and, and retail edge and, and more, right? So, and space, you know, So it's very exciting there. So the reason I tag back to that question that you asked earlier is that that's where customers are. So cloud is one thing, but now they gotta also think about how do I, whatever I do in the cloud, how do I bring it to the edge? Because that's where my end users are, my customers are, and my data is, right? So that's the, >>And I think Kubernetes has brought that attention to the laggards. We had the Laed Martin on yesterday, which is an incredible real example of Kubernetes at the edge. It's just incredible story. We covered it also wrote a story about it. So compelling. Cuz it makes it real. Yes. And Kubernetes is real. So then the question is developer productivity, okay, Things are starting to settle in. We've got KCP scaling clusters, things are happening. What about the tool chains? And how do I develop now I got scale of development, more code coming in. I mean, we are speculating that in the future there's so much code in open source that no one has to write code anymore. Yeah. At some point it's like this gluing things together. So the developers need to be productive. How are we gonna scale the developer equation and eliminate the, the complexity of tool chains and environments. Web assembly is super hyped up at this show. I don't know why, but sounds good. No one, no one can tell me why, but I can kind of connect the dots. But this is a big thing. >>Yeah. And it's fitting that you ask about like no code. So we've been working with our friends at Cross Plain and have integrated with kcp the ability to no code, take a whole bunch of configuration and say, I want a database. I want to be a, a provider of databases. I'm in an IT department, there's a bunch of developers, they don't wanna have to write code to create databases. So I can just take, take my configuration and make it available to them. And through some super cool new easy to use tools that we have as a developer, you can just say, please give me a database and you don't have to write any code. I don't have to write any code to maintain that database. I'm actually using community tooling out there to get that spun up. So there's a lot of opportunities out there. So >>That's ease of use check. What about a large enterprise that's got multiple tool chains and you start having security issues. Does that disrupt the tool chain capability? Like there's all those now weird examples emerging, not weird, but like real plumbing challenges. How do you guys see that evolving with Red >>Hat and Yeah, I mean, I mean, talking about that, right? The software, secure software supply chain is a huge concern for everyone after, especially some of the things that have happened in the past few >>Years. Massive team here at the show. Yeah. And just within the community, we're all a little more aware, I think, even than we were before. >>Before. Yeah. Yeah. And, and I think the, so to step back, I mean from, so, so it's not just even about, you know, run time vulnerability scanning, Oh, that's important, but that's not enough, right? So we are talking about, okay, how did that container, or how did that workload get there? What is that workload? What's the prominence of this workload? How did it get created? What is in it? You know, and what, what are, how do I make, make sure that there are no unsafe attack s there. And so that's the software supply chain. And where Red Hat is very heavily invested. And as you know, with re we kind of have roots in secure operating system. And rel one of the reasons why Rel, which is the foundation of everything we do at Red Hat, is because of security. So an OpenShift has always been secure out of the box with things like scc, rollbacks access control, we, which we added very early in the product. >>And now if you kind of bring that forward, you know, now we are talking about the complete software supply chain security. And this is really about right how from the moment the, the, the developer rights code and checks it into a gateway repository from there on, how do you build it? How do you secure it at each step of the process, how do you sign it? And we are investing and contributing to the community with things like cosign and six store, which is six store project. And so that secures the supply chain. And then you can use things like algo cd and then finally we can do it, deploy it onto the cluster itself. And then we have things like acs, which can do vulnerability scanning, which is a container security platform. >>I wanna thank you guys for coming on. I know Savannah's probably got a last question, but my last question is, could you guys each take a minute to answer why has Kubernetes been so successful today? What, what was the magic of Kubernetes that made it successful? Was it because no one forced it? Yes. Was it lightweight? Was it good timing, right place at the right time community? What's the main reason that Kubernetes is enabling all this, all this shift and goodness that's coming together, kind of defacto unifies people, the stacks, almost middleware markets coming around. Again, not to use that term middleware, but it feels like it's just about to explode. Yeah. Why is this so successful? I, >>I think, I mean, the shortest answer that I can give there really is, you know, as you heard the term, I think Satya Nala from Microsoft has used it. I don't know if he was the original person who pointed, but every company wants to be a software company or is a software company now. And that means that they want to develop stuff fast. They want to develop stuff at scale and develop at, in a cloud native way, right? You know, with the cloud. So that's, and, and Kubernetes came at the right time to address the cloud problem, especially across not just one public cloud or two public clouds, but across a whole bunch of public clouds and infrastructure as, and what we call the hybrid clouds. I think the ES is really exploded because of hybrid cloud, the need for hybrid cloud. >>And what's your take on the, the magic Kubernetes? What made it, what's making it so successful? >>I would agree also that it came about at the right time, but I would add that it has great extensibility and as developers we take it advantage of that every single day. And I think that the, the patterns that we use for developing are very consistent. And I think that consistency that came with Kubernetes, just, you have so many people who are familiar with it and so they can follow the same patterns, implement things similarly, and it's just a good fit for the way that we want to get our software out there and have, and have things operate. >>Keep it simple, stupid almost is that acronym, but the consistency and the de facto alignment Yes. Behind it just created a community. So, so then the question is, are the developers now setting the standards? That seems like that's the new way, right? I mean, >>I'd like to think so. >>So I mean hybrid, you, you're touching everything at scale and you also have mini shift as well, right? Which is taking a super macro micro shift. You ma micro shift. Oh yeah, yeah, exactly. It is a micro shift. That is, that is fantastic. There isn't a base you don't cover. You've spoken a lot about community and both of you have, and serving the community as well as your engagement with them from a, I mean, it's given that you're both leaders stepping back, how, how Community First is Red Hat and OpenShift as an organization when it comes to building the next products and, and developing. >>I'll take and, and I'm sure Andy is actually the community, so I'm sure he'll want to a lot of it. But I mean, right from the start, we have roots in open source. I'll keep it, you know, and, and, and certainly with es we were one of the original contributors to Kubernetes other than Google. So in some ways we think about as co-creators of es, they love that. And then, yeah, then we have added a lot of things in conjunction with the, I I talk about like SCC for Secure, which has become part security right now, which the community, we added things like our back and other what we thought were enterprise features needed because we actually wanted to build a product out of it and sell it to customers where our customers are enterprises. So we have worked with the community. Sometimes we have been ahead of the community and we have convinced the community. Sometimes the community has been ahead of us for other reasons. So it's been a great collaboration, which is I think the right thing to do. But Andy, as I said, >>Is the community well set too? Are well said. >>Yes, I agree with all of that. I spend most of my days thinking about how to interact with the community and engage with them. So the work that we're doing on kcp, we want it to be a community project and we want to involve as many people as we can. So it is a heavy focus for me and my team. And yeah, we we do >>It all the time. How's it going? How's the project going? You feel good >>About it? I do. It is, it started as an experiment or set of prototypes and has grown leaps and bounds from it's roots and it's, it's fantastic. Yeah. >>Controlled planes are hot data planes control planes. >>I >>Know, I love it. Making things work together horizontally scalable. Yeah. Sounds like cloud cloud native. >>Yeah. I mean, just to add to it, there are a couple of talks that on KCP at Con that our colleagues s Stephan Schemanski has, and I, I, I would urge people who have listening, if they have, just Google it, if you will, and you'll get them. And those are really awesome talks to get more about >>It. Oh yeah, no, and you can tell on GitHub that KCP really is a community project and how many people are participating. It's always fun to watch the action live to. Sure. Andy, thank you so much for being here with us, John. Wonderful questions this afternoon. And thank all of you for tuning in and listening to us here on the Cube Live from Detroit. I'm Savannah Peterson. Look forward to seeing you again very soon.

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

>> From theCUBE Studios in Palo Alto in Boston, bringing you data driven insights from theCUBE and ETR. This is Breaking Analysis with Dave Vellante. >> After a two-year epic run in tech, 2022 has been an epically bad year. Through yesterday, The NASDAQ composite is down 30%. The S$P 500 is off 21%. And the Dow Jones Industrial average 16% down. And the poor holders at Bitcoin have had to endure a nearly 60% decline year to date. But judging by the attendance and enthusiasm, in major in-person tech events this spring. You'd never know that tech was in the tank. Moreover, walking around the streets of Las Vegas, where most tech conferences are held these days. One can't help but notice that the good folks of Main Street, don't seem the least bit concerned that the economy is headed for a recession. Hello, and welcome to this weeks Wiki Bond Cube Insights powered by ETR. In this Breaking Analysis we'll share our main takeaways from the first half of 2022. And talk about the outlook for tech going forward, and why despite some pretty concerning headwinds we remain sanguine about tech generally, but especially enterprise tech. Look, here's the bumper sticker on why many folks are really bearish at the moment. Of course, inflation is high, other than last year, the previous inflation high this century was in July of 2008, it was 5.6%. Inflation has proven to be very, very hard to tame. You got gas at $7 dollars a gallon. Energy prices they're not going to suddenly drop. Interest rates are climbing, which will eventually damage housing. Going to have that ripple effect, no doubt. We're seeing layoffs at companies like Tesla and the crypto names are also trimming staff. Workers, however are still in short supply. So wages are going up. Companies in retail are really struggling with the right inventory, and they can't even accurately guide on their earnings. We've seen a version of this movie before. Now, as it pertains to tech, Crawford Del Prete, who's the CEO of IDC explained this on theCUBE this very week. And I thought he did a really good job. He said the following, >> Matt, you have a great statistic that 80% of companies used COVID as their point to pivot into digital transformation. And to invest in a different way. And so what we saw now is that tech is now where I think companies need to focus. They need to invest in tech. They need to make people more productive with tech and it played out in the numbers. Now so this year what's fascinating is we're looking at two vastly different markets. We got gasoline at $7 a gallon. We've got that affecting food prices. Interesting fun fact recently it now costs over $1,000 to fill an 18 wheeler. All right, based on, I mean, this just kind of can't continue. So you think about it. >> Don't put the boat in the water. >> Yeah, yeah, yeah. Good luck if ya, yeah exactly. So a family has kind of this bag of money, and that bag of money goes up by maybe three, 4% every year, depending upon earnings. So that is sort of sloshing around. So if food and fuel and rent is taking up more, gadgets and consumer tech are not, you're going to use that iPhone a little longer. You're going to use that Android phone a little longer. You're going to use that TV a little longer. So consumer tech is getting crushed, really it's very, very, and you saw it immediately in ad spending. You've seen it in Meta, you've seen it in Facebook. Consumer tech is doing very, very, it is tough. Enterprise tech, we haven't been in the office for two and a half years. We haven't upgraded whether that be campus wifi, whether that be servers, whether that be commercial PCs as much as we would have. So enterprise tech, we're seeing double digit order rates. We're seeing strong, strong demand. We have combined that with a component shortage, and you're seeing some enterprise companies with a quarter of backlog, I mean that's really unheard of. >> And higher prices, which also profit. >> And therefore that drives up the prices. >> And this is a theme that we've heard this year at major tech events, they've really come roaring back. Last year, theCUBE had a huge presence at AWS Reinvent. The first Reinvent since 2019, it was really well attended. Now this was before the effects of the omicron variant, before they were really well understood. And in the first quarter of 2022, things were pretty quiet as far as tech events go But theCUBE'a been really busy this spring and early into the summer. We did 12 physical events as we're showing here in the slide. Coupa, did Women in Data Science at Stanford, Coupa Inspire was in Las Vegas. Now these are both smaller events, but they were well attended and beat expectations. San Francisco Summit, the AWS San Francisco Summit was a bit off, frankly 'cause of the COVID concerns. They were on the rise, then we hit Dell Tech World which was packed, it had probably around 7,000 attendees. Now Dockercon was virtual, but we decided to include it here because it was a huge global event with watch parties and many, many tens of thousands of people attending. Now the Red Hat Summit was really interesting. The choice that Red Hat made this year. It was purposefully scaled down and turned into a smaller VIP event in Boston at the Western, a couple thousand people only. It was very intimate with a much larger virtual presence. VeeamON was very well attended, not as large as previous VeeamON events, but again beat expectations. KubeCon and Cloud Native Con was really successful in Spain, Valencia, Spain. PagerDuty Summit was again a smaller intimate event in San Francisco. And then MongoDB World was at the new Javits Center and really well attended over the three day period. There were lots of developers there, lots of business people, lots of ecosystem partners. And then the Snowflake summit in Las Vegas, it was the most vibrant from the standpoint of the ecosystem with nearly 10,000 attendees. And I'll come back to that in a moment. Amazon re:Mars is the Amazon AI robotic event, it's smaller but very, very cool, a lot of innovation. And just last week we were at HPE Discover. They had around 8,000 people attending which was really good. Now I've been to over a dozen HPE or HPE Discover events, within Europe and the United States over the past decade. And this was by far the most vibrant, lot of action. HPE had a little spring in its step because the company's much more focused now but people was really well attended and people were excited to be there, not only to be back at physical events, but also to hear about some of the new innovations that are coming and HPE has a long way to go in terms of building out that ecosystem, but it's starting to form. So we saw that last week. So tech events are back, but they are smaller. And of course now a virtual overlay, they're hybrid. And just to give you some context, theCUBE did, as I said 12 physical events in the first half of 2022. Just to compare that in 2019, through June of that year we had done 35 physical events. Yeah, 35. And what's perhaps more interesting is we had our largest first half ever in our 12 year history because we're doing so much hybrid and virtual to compliment the physical. So that's the new format is CUBE plus digital or sometimes just digital but that's really what's happening in our business. So I think it's a reflection of what's happening in the broader tech community. So everyone's still trying to figure that out but it's clear that events are back and there's no replacing face to face. Or as I like to say, belly to belly, because deals are done at physical events. All these events we've been to, the sales people are so excited. They're saying we're closing business. Pipelines coming out of these events are much stronger, than they are out of the virtual events but the post virtual event continues to deliver that long tail effect. So that's not going to go away. The bottom line is hybrid is the new model. Okay let's look at some of the big themes that we've taken away from the first half of 2022. Now of course, this is all happening under the umbrella of digital transformation. I'm not going to talk about that too much, you've had plenty of DX Kool-Aid injected into your veins over the last 27 months. But one of the first observations I'll share is that the so-called big data ecosystem that was forming during the hoop and around, the hadoop infrastructure days and years. then remember it dispersed, right when the cloud came in and kind of you know, not wiped out but definitely dampened the hadoop enthusiasm for on-prem, the ecosystem dispersed, but now it's reforming. There are large pockets that are obviously seen in the various clouds. And we definitely see a ecosystem forming around MongoDB and the open source community gathering in the data bricks ecosystem. But the most notable momentum is within the Snowflake ecosystem. Snowflake is moving fast to win the day in the data ecosystem. They're providing a single platform that's bringing different data types together. Live data from systems of record, systems of engagement together with so-called systems of insight. These are converging and while others notably, Oracle are architecting for this new reality, Snowflake is leading with the ecosystem momentum and a new stack is emerging that comprises cloud infrastructure at the bottom layer. Data PaaS layer for app dev and is enabling an ecosystem of partners to build data products and data services that can be monetized. That's the key, that's the top of the stack. So let's dig into that further in a moment but you're seeing machine intelligence and data being driven into applications and the data and application stacks they're coming together to support the acceleration of physical into digital. It's happening right before our eyes in every industry. We're also seeing the evolution of cloud. It started with the SaaS-ification of the enterprise where organizations realized that they didn't have to run their own software on-prem and it made sense to move to SaaS for CRM or HR, certainly email and collaboration and certain parts of ERP and early IS was really about getting out of the data center infrastructure management business called that cloud 1.0, and then 2.0 was really about changing the operating model. And now we're seeing that operating model spill into on-prem workloads finally. We're talking about here about initiatives like HPE's Green Lake, which we heard a lot about last week at Discover and Dell's Apex, which we heard about in May, in Las Vegas. John Furrier had a really interesting observation that basically this is HPE's and Dell's version of outposts. And I found that interesting because outpost was kind of a wake up call in 2018 and a shot across the bow at the legacy enterprise infrastructure players. And they initially responded with these flexible financial schemes, but finally we're seeing real platforms emerge. Again, we saw this at Discover and at Dell Tech World, early implementations of the cloud operating model on-prem. I mean, honestly, you're seeing things like consoles and billing, similar to AWS circa 2014, but players like Dell and HPE they have a distinct advantage with respect to their customer bases, their service organizations, their very large portfolios, especially in the case of Dell and the fact that they have more mature stacks and knowhow to run mission critical enterprise applications on-prem. So John's comment was quite interesting that these firms are basically building their own version of outposts. Outposts obviously came into their wheelhouse and now they've finally responded. And this is setting up cloud 3.0 or Supercloud, as we like to call it, an abstraction layer, that sits above the clouds that serves as a unifying experience across a continuum of on-prem across clouds, whether it's AWS, Azure, or Google. And out to both the near and far edge, near edge being a Lowes or a Home Depot, but far edge could be space. And that edge again is fragmented. You've got the examples like the retail stores at the near edge. Outer space maybe is the far edge and IOT devices is perhaps the tiny edge. No one really knows how the tiny edge is going to play out but it's pretty clear that it's not going to comprise traditional X86 systems with a cool name tossed out to the edge. Rather, it's likely going to require a new low cost, low power, high performance architecture, most likely RM based that will enable things like realtime AI inferencing at that edge. Now we've talked about this a lot on Breaking Analysis, so I'm not going to double click on it. But suffice to say that it's very possible that new innovations are going to emerge from the tiny edge that could really disrupt the enterprise in terms of price performance. Okay, two other quick observations. One is that data protection is becoming a much closer cohort to the security stack where data immutability and air gaps and fast recovery are increasingly becoming a fundamental component of the security strategy to combat ransomware and recover from other potential hacks or disasters. And I got to say from our observation, Veeam is leading the pack here. It's now claiming the number one revenue spot in a statistical dead heat with the Dell's data protection business. That's according to Veeam, according to IDC. And so that space continues to be of interest. And finally, Broadcom's acquisition of Dell. It's going to have ripple effects throughout the enterprise technology business. And there of course, there are a lot of questions that remain, but the one other thing that John Furrier and I were discussing last night John looked at me and said, "Dave imagine if VMware runs better on Broadcom components and OEMs that use Broadcom run VMware better, maybe Broadcom doesn't even have to raise prices on on VMware licenses. Maybe they'll just raise prices on the OEMs and let them raise prices to the end customer." Interesting thought, I think because Broadcom is so P&L focused that it's probably not going to be the prevailing model but we'll see what happens to some of the strategic projects rather like Monterey and Capitola and Thunder. We've talked a lot about project Monterey, the others we'll see if they can make the cut. That's one of the big concerns because it's how OEMs like the ones that are building their versions of outposts are going to compete with the cloud vendors, namely AWS in the future. I want to come back to the comment on the data stack for a moment that we were talking about earlier, we talked about how the big data ecosystem that was once coalescing around hadoop dispersed. Well, the data value chain is reforming and we think it looks something like this picture, where cloud infrastructure lives at the bottom. We've said many times the cloud is expanding and evolving. And if companies like Dell and HPE can truly build a super cloud infrastructure experience then they will be in a position to capture more of the data value. If not, then it's going to go to the cloud players. And there's a live data layer that is increasingly being converged into platforms that not only simplify the movement in ELTing of data but also allow organizations to compress the time to value. Now there's a layer above that, we sometimes call it the super PaaS layer if you will, that must comprise open source tooling, partners are going to write applications and leverage platform APIs and build data products and services that can be monetized at the top of the stack. So when you observe the battle for the data future it's unlikely that any one company is going to be able to do this all on their own, which is why I often joke that the 2020s version of a sweaty Steve Bomber running around the stage, screaming, developers, developers developers, and getting the whole audience into it is now about ecosystem ecosystem ecosystem. Because when you need to fill gaps and accelerate features and provide optionality a list of capabilities on the left hand side of this chart, that's going to come from a variety of different companies and places, we're talking about catalogs and AI tools and data science capabilities, data quality, governance tools and it should be of no surprise to followers of Breaking Analysis that on the right hand side of this chart we're including the four principles of data mesh, which of course were popularized by Zhamak Dehghani. So decentralized data ownership, data as products, self-serve platform and automated or computational governance. Now whether this vision becomes a reality via a proprietary platform like Snowflake or somehow is replicated by an open source remains to be seen but history generally shows that a defacto standard for more complex problems like this is often going to emerge prior to an open source alternative. And that would be where I would place my bets. Although even that proprietary platform has to include open source optionality. But it's not a winner take all market. It's plenty of room for multiple players and ecosystem innovators, but winner will definitely take more in my opinion. Okay, let's close with some ETR data that looks at some of those major platform plays who talk a lot about digital transformation and world changing impactful missions. And they have the resources really to compete. This is an XY graphic. It's a view that we often show, it's got net score on the vertical access. That's a measure of spending momentum, and overlap or presence in the ETR survey. That red, that's the horizontal access. The red dotted line at 40% indicates that the platform is among the highest in terms of spending velocity. Which is why I always point out how impressive that makes AWS and Azure because not only are they large on the horizontal axis, the spending momentum on those two platforms rivals even that of Snowflake which continues to lead all on the vertical access. Now, while Google has momentum, given its goals and resources, it's well behind the two leaders. We've added Service Now and Salesforce, two platform names that have become the next great software companies. Joining likes of Oracle, which we show here and SAP not shown along with IBM, you can see them on this chart. We've also plotted MongoDB, which we think has real momentum as a company generally but also with Atlas, it's managed cloud database as a service specifically and Red Hat with trying to become the standard for app dev in Kubernetes environments, which is the hottest trend right now in application development and application modernization. Everybody's doing something with Kubernetes and of course, Red Hat with OpenShift wants to make that a better experience than do it yourself. The DYI brings a lot more complexity. And finally, we've got HPE and Dell both of which we've talked about pretty extensively here and VMware and Cisco. Now Cisco is executing on its portfolio strategy. It's got a lot of diverse components to its company. And it's coming at the cloud of course from a networking and security perspective. And that's their position of strength. And VMware is a staple of the enterprise. Yes, there's some uncertainty with regards to the Broadcom acquisition, but one thing is clear vSphere isn't going anywhere. It's entrenched and will continue to run lots of IT for years to come because it's the best platform on the planet. Now, of course, these are just some of the players in the mix. We expect that numerous non-traditional technology companies this is important to emerge as new cloud players. We've put a lot of emphasis on the data ecosystem because to us that's really going to be the main spring of digital, i.e., a digital company is a data company and that means an ecosystem of data partners that can advance outcomes like better healthcare, faster drug discovery, less fraud, cleaner energy, autonomous vehicles that are safer, smarter, more efficient grids and factories, better government and virtually endless litany of societal improvements that can be addressed. And these companies will be building innovations on top of cloud platforms creating their own super clouds, if you will. And they'll come from non-traditional places, industries, finance that take their data, their software, their tooling bring them to their customers and run them on various clouds. Okay, that's it for today. Thanks to Alex Myerson, who is on production and does the podcast for Breaking Analysis, Kristin Martin and Cheryl Knight, they help get the word out. And Rob Hoofe is our editor and chief over at Silicon Angle who helps edit our posts. Remember all these episodes are available as podcasts wherever you listen. All you got to do is search Breaking Analysis podcast. I publish each week on wikibon.com and siliconangle.com. You can email me directly at david.vellante@siliconangle.com or DM me at dvellante, or comment on my LinkedIn posts. And please do check out etr.ai for the best survey data in the enterprise tech business. This is Dave Vellante for theCUBE's Insights powered by ETR. Thanks for watching be well. And we'll see you next time on Breaking Analysis. (upbeat music)

>>The cube presents HPE discover 2022 brought to you by HPE. >>Hey everyone. Welcome back to the Cube's day one coverage of HPE. Discover 22 live from Las Vegas. Lisa Martin, here with Dave Velante of a couple of guests from red hat. You may have seen some news yesterday. We're gonna be talking about that. Please. Welcome Ryan King, the senior director of hardware partner ecosystem, and Lori Fontine joins us as well. The senior director of global commercial partner ecosystem. Welcome to the program guys. >>Thanks for having us. Yeah, >>Thank you so great to be back in person and nobody word has summit was just last month or so. That's right. Ryan. Talk about hybrid cloud. It's all the buzz. We've been talking a lot about it in the last hour and a half alone. What are some of the trends that, that red hat is seen with respect to hybrid cloud? >>Well, I, I mean, hybrid cloud of red hat has been a trend for quite some time. In fact, we were very early in setting our course towards hybrid cloud with our products and platforms. And that's been a key part of our strategy in terms of the number of transformations have been happening in the enterprise. And with HPE, we're super excited about, you know, we're hitting our stride with OpenShift. I've been working with OpenShift for the better part of my 10 years here at 12 years at red hat, 10 years with OpenShift. And we're very excited about seeing the pattern of going where customers want to build their cloud. It's very important that where, where the market is going. So we're seeing trends from the public cloud now go into edge and telco and 5g and really exceed, see them expanding their infrastructure footprint out to those use cases. And again, we see REL everywhere. So re has continued to expand as well. And then Ansible automation platform has also been a great means of kind of bringing together community for that last mile of automating your entire infrastructure. >>Well, the Lin, the functionality of Linux continues to improve OpenShift is everywhere. I mean, I remember at the red hat summit, I mean, well, we, we, we coined this term super cloud, which is this layer that floats, you know, on-prem took across clouds out to the edge we had Verizon on. They were talking about, you know, 5g developers and how they're developing using, you know, a combination of, of, of OpenShift. So guys have been really crushing it with, with OpenShift. I remember, gosh, I mean, we've been covering, you know, red hat summits for a long time now. And just to see that evolution is actually quite amazing. >>Yeah. It's actually really neat to see our CEOs align too. Right. So the messaging that we've had around hybrid cloud from red hat, like you said, we were kind of the pioneers, honestly, this we've been talking about hybrid cloud from the very beginning. We always knew that it wasn't gonna be public cloud or private cloud. We had to have, you know, hybrid. And, and it's interesting to see that Antonio, you know, took that on and wanted to say, we're gonna do everything as a service right. A few years ago. And, and the whole theme was around hybrid cloud and giving customers that choice. Right? So it's exciting for us to see all of that come together. And I actually worked for HP for like 17 and a half years. So it's really fun for me to be on this side now with red hat and see the messaging come together, the vision come together and just really being able to align and move forward on >>This tremendous amount of transformation in the last few years >>Alone. Oh my gosh, we >>Talk about, you know, customers need choice. They want choice, but you also talked about, we have to meet customers where they are. That seems the last few years to have accelerated, there is no more option for companies. You've gotta meet the customers where they are. >>Exactly. Yeah. And it's all about choice, like you said, and it, everybody's got, you know, their own way to do everything as far as consumption goes and we have to be available and spot on with it, you know, and be able to move quickly with these trends that we're seeing. And so it's great to be aligned. And >>From a partnership standpoint, I mean, you, you mentioned H HP 17 years. I mean, it was, it was a hard to follow company. You had, you had PCs over here, you had services, the kind of the old EDS business. Now there's such a focus absolutely. On this mission, absolutely. Of as a service. And, you know, obviously a key part of that is having optionality and bringing open source tooling into that. I mean, we heard about this in, in spades, at, at red hat summit, which is really interesting this year. It was a smaller VIP event in Boston. And I, and I loved it, you know, cuz it was really manageable. We had all the execs on and customers and partners. It was awesome. What's new since red hat summit. >>Well, I mean, I would say that obviously GreenLake and what we've announced this week is a big new thing for us, but really like we're just continuing on our pattern. We are. Now, if you look at the Q1 report from IBM, you'll see that the growth of the customer base for OpenShift that they reported just continues to go up into the right. You'll see that now, like AMIA is saying that we're like 47.8% of the containers market for the enterprise. You'll see that like we're now in 65% of the fortune 500 with OpenShift, 90% with red hat in general. So we've established our footprint. And when you establish your footprint and customers start taking you out to the edge, we're going into these 5g use cases, we're, we've got an incredible amount happening in the AI space, all these emerging areas of where people are building their cloud, like we're now going to that next level of saying, how do they want to consume it? >>So what's really important to me about that is, is so Omni data around 50% of the market is, is open shift. A people may not realize a lot of people use, you know, do Kubernetes for free, you know, Hey, we're doing Kubernetes, but they don't have that application development framework and all the recovery and all the, the tooling around it. And the reason why I think that's so important, Laurie is ecosystems wanna monetize. So people are paying for things that becomes more interesting and it actually starts to attract people just naturally. >>Yeah, absolutely. And speaking of ecosystem, I mean, that's the beauty of what we're doing with GreenLake too. We're taking on a building block approach. So we're really, it's kind of ISV as a service if you will. And you know, personally, I, this was my baby for the past couple years, trying to make sure that we took into consideration every partner use case, every customer use case. So we created an agreement that would make sense to be able to scale, but also to meet all the demands of our customers. And so the, the what's really exciting about this is now we have a chance to take this building block approach, scale it out to all types of partner types, right throughout the entire ecosystem and build offerings together. That is really exciting for us. And that's where we see the real potential here with GreenLake and with red hat, >>What's actually available inside a GreenLake. >>So we are starting with OpenShift. So OpenShift will be available in Q3 that will follow in Q4 with re and then after that Ansible. So we're, we're moving very quickly to bring our platforms into it and it's really our strategic platforms, but it's all based on customer demand. We know we're seeing amazing transformation of customers moving to Kubernetes. You said, you know, OpenShift is Kubernetes with useful additions to it and an ecosystem around it, right? So that transformation is also happening at the bare metal layer. So we're seeing people move into Kubernetes bare metal, which is an amazing growth market for us. >>Explain those useful additions if you would. So why shouldn't I just go out and, and get the free version of Kubernete? Why should I engage red hat and, and OpenShift? What do I get? >>So you get all the day, two management stuff, you get, we have a whole set of additional stuff you can purchase around it, OpenShift platform. Plus you can get our ACM, our advanced cluster management. So you wanna manage multiple clusters, right? You get the ACS, the security side of it. You can also get ODF. So you get storage built into it as well. And we've done all these integrations. You can manage the whole thing as a cluster or as multiple clusters with the whole enterprise support and the long term support that we provide for these things up to 10 years. So >>When you look at the early days lease of, of Kubernetes, it was really, the focus was on simplicity. You had other platforms that were actually doing more sophisticated cluster management. And the, the committers that in Kubernetes said, you know, we're not gonna do that. We're gonna keep it simple. And so that leave some holes and gaps and you know, they're starting to fill those, but what if, if correct me if I'm wrong, but what red hat has done is said, okay, we're gonna accelerate, you know, the, the, the closing of those gaps and stay ahead and actually offer incremental value. And that's why you're winning in the marketplace. >>Well, we're an open company, so we're still doing everything upstream and open source as we do, of course, sticking with, you know, the APIs and APIs to make this all work, both, you know, in terms of what the community's trying to drive, what we're trying to drive for our customers on their behalf. And then just where things are going from a technology basis, make it a lot of investment, >>But you have to, you have to make a red hat, has to make a choice as to where it puts its commitments. You can't spread yourself too thin, so you gotta pick your spots. And you've, you've proven that you're pretty adept at doing that. >>That just comes back to customer centricity, right. And just knowing where our customers need to take the platform. That's, >>That's easy to say, but it's, it's an art form. And a little bit of science. >>Remember these customers have experts that are deep in this space. So it's like, you know, those experts trust us with where they needed to go. And they trust us to help shepherd that and deliver that as a platform to them. So it's not like anybody tell us what you want, right? Like it's really about like, knowing what's the best way to do it. And working with the people that can help you understand how to apply that to their use case >>And within the customer environment, who are you working with? Who is that key constituent or constituents that are guiding red hat in this direction? >>Well, it's certainly infrastructure folks. So it's your, it's your standard folks that are looking at the, how do we lay down our infrastructure? How do we manage it? How do we grow it? It goes out to the application developers. They're trying to deliver this in a cloud native way. And we have new personas, you know, coming in with the AI practitioners, right? So we've announced at before summit at Invidia's event, their new offering called Invidia AI enterprise. And so that's them bringing in enterprise support for GPU, for Kuda and for a software stack above that to start offering some more support there. So they're certifying OpenShift, we're both certifying the servers that run underneath it, and then they're offering support for their stuff on top of it. And that's a whole new use case for us. >>And, you know, I should also mention that even though this paper use with the GreenLake is new for us, and we just had this big announcement, we have done GreenLake deals though. We've done numerous GreenLake deals with our annual subs, right? So I, so even though this is new to us, as far as, you know, monthly utilization and being able to do this cloud consumption this isn't new to us as two companies coming together, we've been doing GreenLake deals for the past couple years. It's just, now we have this cloud consumption availability, which is really gonna make this thing launch. So, >>So what have been some of the customer benefits so far, you've been doing it for a couple years. The announcement was yesterday, but there's obviously feed on the street going on. What are some of the, the big outcomes that you're seeing customers actually bring to reality? >>I think speed and agility, right? That's the biggest thing with, with our products, being able to have it everything predictable and being able to have it consumed one way, instead of having this fragmented customer experience, which is, you know, what we've seen in the past. So I think that's the biggest thing is speed agility and just, you know, a really good customer experience at this point. >>Go get it, please. >>I would say the customer experience is critical. Yes. That's one of the things that we know that in terms of, of patients wearing thin the last couple of years, people expect to have a really strong consumer experience regardless of what you're doing, regardless of what industry and so attention and mind on that is a differentiator in my opinion. >>Absolutely. Yeah. And we've gotta constantly keep our eye on that. I mean, that's, that's our north star, if you will. Right. So, and Lori, >>I know you've saying you're, you've done GreenLake deals in the past, but what feels different to me now in that it's actually coalescing some of the things that Alma Russo announced this morning, the platform on which, you know, ISV is a service. I think you, you called it. Yeah. You, it, it now seems like, you know, look a couple years ago, HP said, okay, this is the direction that we're going. Yeah. They weren't there at that time. And they're still not there. There's a lot of work to be, to be done. But now it's starting to form. You're seeing, you know, the pieces come together, the puzzle pieces that sort of substrate being laid out. And now you're hoping that we see the steep part of the S-curve and that's what customers I think are expecting. >>Right. And it's bringing that operating model to move to a monthly model so they can do pay as you go. Right. And that pairs up nicely with like the cloud native capabilities we're bringing to OpenShift and hybrid cloud in general. So it's, it just shows like we're already getting demand from customers. It's saying like, this is part of our model. Like we know a certain amount of infrastructure we wanna own, and we just wanna own it outright, but there's a lot that they want to have flexibility on. And so being able to add that portion to it is just, you know, gonna help us both. >>And you think about the critical aspects of, of the cloud operating model. It's obviously pay as you go it's, you know, massive scale it's ecosystem enablement, and also automation. I mean, that is, that is a key, what's your point of view on that? You guys with Ansible, you, you, you know, you go back to a couple years ago and it was, you know, there was this, there were a lot of other tooling, but now, I mean, Ansible is really taken off. Yeah. >>It's just, you know, Cinderella story, right? Like it really an amazing community driven thing where we just knew, we all know this, right. You have, when you get to the very last mile of doing infrastructure management, there's a variety of devices, there's variety, a variety of vendors. And then you have like the variety of skills of the people that have to figure out how to do automate all of this. And what Ansible did is it provided a common language across all of that. And so what we do with automation, our, an ible automation platform is we make it. So now teams can manage all of this together and they can share their playbooks and they can host that privately for all their enterprise stuff that they need to do. So it's just, you know, it fits our DNA so well to have something so community driven now with a really nice enterprise message wrapped around it. And it's playing out very well for where, you know, hybrid cloud. Right. Cause there's some more additional variety. You need to be able to manage, you know, across all of your different footprints, because really it's like, it's not just about flexibility and scale up scale down it's where do you need it to run at what time? Right. And that, that last leg Ansible plays a key role in that. >>And we actually, Ansible will be coming further down the, you know, the patch. I know we're gonna talk a little bit about what's available today versus what's available down the road, but yeah, we have that on the radar. So right outta the gate, we're working on OpenShift, obviously bare metal. And we see that happening in Q3 and then behind that as well in Q4 and then Ansible is gonna be right behind that. So that's kind of the order that, and there's other pieces, right? So our whole portfolio is basically available to HP right now. It's just making sure that we can operationalize everything and have the best experience >>All inside of GreenLake, >>All inside a GreenLake. Yeah. Pretty neat. Lori >>Question for you. You've been, you were with HP for a very long time. This is obviously the first discover in three years in person. Exactly. You know, three years ago, Antonio near stood on stage and said, we are going to buy 20, 22. And here we are deliver everything as a service, as a partner and as a former HP, what are you seeing at this discover 22? >>It's it's so interesting. I it's such a sea change if you will. Right. And having come from HPE, I actually led the software as a service organization for a while on the software side of things. And we thought that was like state of the art and cutting edge that was 10, 11, 12 years ago. Right. So to actually see this come to life, because we were all thinking really, everything is a service. How are you gonna do that? Like your entire portfolio is gonna be available. Like that is lofty. Right. And having worked at HP, I thought, wow, I don't, you know, I know things take time. And, but actually just even being around the showcase here and watching everything come to life is amazing. Cause I, I, you know, I, I was very positive about it, but at the same time, it's like that, that was a big goal three years. Right. And it's, I'm seeing it happen >>A big goal in two of those years during a pandemic. Right. So right. Talk about lofty. Oh my gosh. Quite a bit of accomplishments guys. Thank you so much for joining David me on the program talking about actually guys, this is great. What red hat and HPE are doing your power partnership, power ship. Is that a word? It is now your power. >>I like >>That with GreenLake. We appreciate that. We'll look forward to having you guys back on. >>Thank you so much, guys. >>All right. For our guests. I'm Lisa Martin. He's Dave ante. We are at HPE discover 22 live from the show floor in Las Vegas. This is just day one of our cupboards stick around. We'll be right back with our next guest.

(upbeat music) >> Hi everybody. We're back at VeeamON 2022, we're winding down coverage to The Cube day two. We've done a lot of VeeamON. We're at the Aria hotel, smaller physical audience, huge hybrid audience, little different program. Great keynotes, really loved the keynote yesterday and today kind of product day today. Sean Smith is here with myself and David Nicholson. He's the staff Solution Architect at VMware. Sean, thanks for coming on the Cube, taking some time with us. >> Hey guys. Great to be here and great to be in person again. >> Yeah, it sure is. Hoping to see VMworld is no longer VMworld, right? >> It's VMware Explore now. Yep. >> Okay. Awesome. Looking forward to that. That was one of the first shows we ever did. It's kind of got that same vibe, I hope you don't lose that, the core of VMware. >> What we've been told is it's still going to be, the core of what we do and it's going to be the showcase of VMware. >> Which is the ecosystem, great vibe. You always know a million people there, which is great fun. How's it going at VMware today? I mean, let's start there. It's been a while since we've talked physically with... >> Yeah. VMware is, we've come through the pandemic, fairly well, relative speaking to what others have done. I'm part of the VCPP Program, the VMware Cloud Provider Program, and I look after cloud service providers, cloud builders, people who are actually building out networks for customers and environments that are very specialized and focusing on their needs and VMware is forefront with cloud service providers these days, doing really well. >> The last time we were physically proximate to VMware executives, I think Pat Gelsinger was still the CEO, Dell still owned the majority of VMware. So that spin happened. So that's good. I think the ecosystem in particular is probably really happy about that. Does it have any effect on your world? >> From a day to day business perspective, not really, right. Obviously we still have a very tight relationship with Dell. We still do a lot of innovative solutions and products with the Dell team. We have a tight integration there. It really gives us the opportunity to also work with many other vendors as well. And focus on solutions that our customers are looking for really, is where VMware is tryna focus. >> Yeah. It's funny, we were at Red Hat Summit last week. IBM Think was right across the street there was very little mention, if any, I think they talked about an IBM mainframe at Red Hat Summit. That was it. I mean IBM fully owns Red Hat, but a lot of people said, we hope that it's going to be like VMware and you guys have always had that independent culture. >> Fiercely independent. >> Fiercely independent. Yes. >> Yes. It's like when you coach, I don't know me anyway, when I coach my kids baseball, I'm a tougher on them than am with the other kids. I think you guys were sometimes tougher on your own or... And rightly so, you have a huge ecosystem. >> We do. >> That is epic. And so you have to look out for that. VMware has always done that. VCPP the V is for a VMware what's what's the acronym. >> So the CPP is Cloud Provider Program. It's a program that's specifically aimed at our cloud service providers. There's several solutions within the program, which are really focused on helping them build business, helping them go to market, helping them with being able to, for certain part of it compete with the hyperscalers and our support several cloud providers, mostly out of the Northeast, and they're doing really well. They're doing well against the hyperscalers, they very often provide solutions that are not easy to get on a hyperscaler. When you want to have customer interaction and things like that. So the VCP Program as I said, is really tailored, it has solutions which are very much focused on allowing them to build their businesses as a cloud service provider. >> Just a follow up if I may. >> Yeah. >> So the history of VMware Cloud has been really interesting. At one point vCloud Air, we know what happened there. This is not vCloud Air. >> This is not vCloud Air. It's got nothing to do with vCloud Air. It's really a program where we provide solutions that the cloud builders build with, right? So it's software solutions. There's no hardware involved. There's no VMware having the environment, it's really cloud providers building solutions. >> So it's interesting, Dave, this has come full circle, you used to work at Virtustream. There was point Rodney was like, bring it on AWS, correlation and back said, we can't lose to a book seller and all that was just, fun marketing talk for media people like us. But the interesting thing is, well, so VMware Cloud on AWS. Huge success of VMware Cloud Foundation. Doing really well. And obviously you've got momentum. Everybody thought, not everybody. >> It's in Google's, in Azure, it's in Oracle. >> Yeah, yeah. Sorry. >> It's an IBM. >> IBM a... >> It's an IBM. >> Number one in IBM. Yeah. >> And so a lot of people thought, I shouldn't say everybody, but a lot of people thought, MSPs, the cloud service providers, non-hyperscalers are cooked through 2010, 2011. The exact opposite happened. >> It's 100%. >> It's growing like crazy. We want to understand why, but it's come full circle. >> Yeah, it certainly has. I mean, the industry has changed considerably and especially over the last few years with COVID, I will say that the cloud service providers that are support and by the way, Virtustream was one of them, when I first joined VMware, I supported Virtustream. And they have had to adapt their businesses, the hyperscalers have come at them with everything that they've got and honesty, the cloud service providers that I support are phenomenal growth. They they're growing on a par with what some of the hyperscalers are doing. So there's definitely a place for cloud service providers, they've got great business, they've got great customers, great relationships. And it's as I said, it's growing a huge business. >> So we've talked a lot about theme from the perspective of the idea of a Supercloud. Something that can overlay a variety of on-premises and off-premises providers and provide sort of a unified view, unified management methodology. How much is what at least was formerly known as the SDDC stack, the Software Defined Data Center stack, still a part of VMwares vision that is right in line with that, from what Veeam is doing. How much of your business is deploying SDDC stacks that are then customized in one way or another. >> 100% of it. >> 100% of it. Right, okay. >> Yeah. So, when you're talking about having that single view of everything in the cloud provider program, there's a product called VMware Cloud Director. and it is the multi-tenant view of the infrastructure and the environment that the cloud providers are building. Right. So VMware Cloud Director has gone through many iterations and we've recently launched Cloud Director Service, which is a SaaS offering of the product. But what it actually does is you put it on top of VMC on AWS. you put it on top of GCVE, you put it on top of the cloud service providers, SDDCs, right. All of these are SDDCs underneath. >> AVS and Azure. >> AVS and Azure. >> I was associated with that. So I must have it mentioned. >> Exactly. >> They're all SDDC's. >> SDDC's, yeah, yeah, exactly. And as well as your on premise environment. Right. So all of these federate together through the VMware Cloud Director, and you end up having a single pane of glass across all of those environments. So whether it's running in the hyperscale, or running on your premises, running in a cloud service provider's environment, you have a single view, a single interface that you log into and you can see everything that's going on inside your environment. So it really brings that holistic, single view of everything to reality. >> How about from a licensing perspective? >> So from a licensing perspective... >> I'm a non-premises customer, I'm running VMware on-prem, I have been, I was at world VMworld 2004 and enjoyed BattleBots. So hopefully you'll start bringing BattleBots back. >> We will have to. >> And now I'm dealing with a service provider. That is one of the partners that you're working with. How does that licensing work? >> So the Cloud Provider Program actually has a slightly different licensing model to what you would have on premises, right? They have a rental model with VMware, it's a PAYGo model, right. One of the great things about the program is that it's consumption based. So it makes it easy for cloud service providers to build a consumption based business, which is kind of where everything is moving, right? >> Yeah, for sure. >> So whether you have an on-premise environment that's licensed through what we call perpetual or ELA licensing, from a VMware perspective, you can still layer on top, that cloud service provider solution VCD, right? And you would obviously have a financial relationship with the cloud service provider in terms of the environment that you have with them. And they will be able to hook up that environment to your on-premises environment and get that single view. So the licensing is not a restriction, right, you can still continue to have your traditional licensed environment in your data center, as well as being able to connect into these seamlessly, right. That's the great thing about it. And that's where VMC, AVS, GCVE, the OCVS, the Oracle version, the RBM one, you can bring all of these together and really look at it from a holistic perspective, bring in things like NSX-T and other solutions like that VM as well, it works seamlessly across all these environments. >> I am talking about Supercloud, I asked Raghu last year, who's virtually at VMworld, I kind of explained that concept of hiding the complexity, the abstraction layer, being able to hide the underlying primitives and APIs, seems like it's evolving. One of the things he said was yes, but if developers want to go there, we let them. And that was a key point, because you're getting more into that DevOps. >> Correct 100%. >> And I would imagine the cloud service providers really oftentimes need for their reasons to get to those underlying primitives and APIs. >> And actually VCD is the enabler, right? So VCD allows you to provide a container based service sitting right alongside your IAS in the same SDDC, right? We're not even talking about segregating them out, you can have it inside the exact same SDDC, all linked together, all taking a common security approach to what's going on and providing you with that ease of use. So from an end user perspective, the DevOps type of people, VCD is an awesome solution, because they can go in fire up a new VM, or fire up a new container or whatever, without having to go through the rigmarole of asking IT for a VM, or asking somebody's permission, as a organization, you would give your DevOps teams certain amount of resources, how they use it's up to them, right? Whether they put containers in there or they bring VMs, it's all there. And it's all in one single solution. >> You mentioned that your community is doing very well growing it let's call it 35, 40% a year. And it's a market that's quite large worldwide. Because it's a lot of local, regional CSPs, a lot of big country CSPs and you said... >> It's four and a 1/2 thousand of them. So, it's huge. >> There you >> Versus four hyperscalers. >> Yeah, exactly. >> Include Alibaba. So, they might be individually smaller, but collectively they're larger. But you said that the hyperscalers coming after them with everything they had was a comment that you made, are customers choosing CSPs over hyperscalers? If so, when and why. >> Sometimes they are choosing CSPs over hyperscalers, but not always, very often they're choosing CSPs and hyperscalers, right. And it really depends on what their needs are. So historically speaking, it's been everybody rushing to the hyperscalers because that's the flavor of the day let's move out of our data center. It's much cheaper to run everything in these hyperscalers, and they do it. And then the bill comes in and reality suddenly hits. And it's definitely not as cheap as they thought it was going to be, right. So there's many aspects that cause tenants to not only rethink that, but also repatriate, right. Repatriation is a big thing for our cloud service providers. Things like egress costs, most cloud service providers have no egress costs, right? They encourage movement of things amongst themselves and for their tenants, because that's what they want, right? So egress costs are a huge problem for many tenants who come into these environments and that's sometimes why they would choose a CSP over a hyperscaler. But really, it's more about choosing the right place for your workload. There are workloads that belong in hyperscalers, right? And if you have a solution with a CSP like VCD, that allows you not only to be able to connect your on premises and the CSP, but also the hyperscalers and actually have a much more holistic solution where you can determine where you want to put stuff and put it in the right place. It's more about that, than it is about choosing one over the other really. >> Yeah, and sometimes it's more of a business differentiation than a technical one. Is it a hyperscale or is it a CSP? If you're licensing the SDDC stack and you're running it on IAS in Amazon or in Google or Azure? >> I think the other thing too is the CSPs oftentimes they manage service providers, right? Is that true? >> The relationship, right? And that's one of the things if you talk to a cloud service provider and yesterday I was, I had a session and I was talking to a bunch of people about VMware stuff. And I said to them, how many of you have tried to pick up a phone and talk to somebody at AWS? And there was laughter, because the reality is that what AWS does is a kind of one size fits all approach, right? There isn't somebody on the end of the phone that you can pick up and call, if they have a major outage that outage is affecting 1000s of different customers and you one of those thousands really means nothing to them, right? Whereas a cloud service provider, generally speaking, has a very tight one-on-one relationship with both from an engineering perspective, right. With their tenants, but also at a higher managerial level. So they create those relationships and those relationships often drive these things. It's not always financial, there is a financial component to it, but very often it's the relationship, have they got somebody that they can talk to? If they getting many different solutions, can they get all those solutions from one provider? And if they can, it's much easier for them to manage from a... >> And I think so does that manage service... There's also a lot of things that despite their breadth and portfolio that the cloud service providers don't support, you can't do Oracle rack in the cloud, right? But you can in a service provider. >> Exactly. >> And Oracle, look you can negotiate with Oracle, so you can get similar pricing AWS, but this price is two x. They're either on-prem or in Oracle. So I could take my Oracle instance, stick it into a managed service provider or cloud service provider, do whatever I need to, and there are I'm sure 1000s of configurations like that, that aren't necessarily identically supported, security edicts that aren't necessarily exactly the same, so many specials that managed service say welcome to your point. AWS is as long as it's black, it's good. >> Yeah, exactly. And that's the thing, right? Those cloud service providers are doing exactly that. They have Oracle racks in there, they have all sorts of those solutions that are there in their data centers. And proximity is also an issue, right? Very often the people who are using those systems need their ancillary things to be close by, they can't be 10s or 20s or 30 milliseconds away, they need to be sub millisecond connectivity. And those are the areas where the cloud service providers really shine, they can offer those solutions that really enable their tenants to get what they want at the end of the day. Again to your point, you can negotiate with Oracle, but these cloud service providers do it day in and day out. Who wants their business? >> Who wants to do that with Oracle anyway, their lawyers are smarter than yours. Veeam, what are you doing with Veeam, in resilient architectures and cyber recovery? >> Yeah, we are a sponsor here at the event and Veeam is a great partner with VMware and we're great partner to them. A lot of cloud service providers actually use Veeam as their primary backup solution for their tenants, right. VMware Cloud Director that I was talking about just now, the thing that gives you a view of everything over the top, Veeam was actually one of the very first vendors to integrate with VCD. And you can use your Veeam environment directly from the screen, you right click, and you say do a backup and that's as easy as that from a Veeam perspective. So we have a lot of integrations with Veeam. We help the cloud service providers, ransomware is a big talking thing around this event, but all over the place, right? So a lot of the solutions that Veeam brings to the party, these cloud service providers are also deploying into their environments to help with ransomware. They have so many solutions that help those cloud service providers provide a holistic solution. >> Well, Veeam was basically founded saying, Hey, we're going to better our business on VMware. I first saw Veeam at a V mug, I think in Boston, and I was like, who is Veeam? VMware is that their product? It was just so you guys have had a long relationship, even though initially VMware was probably saying the same thing, who the heck are these guys? Well, how do you like them now? Sean, thanks so much for... >> Thank you. It's been great to be here. Appreciate it. Thank you for watching. Keep it right there. We'll be back shortly. We'll get a couple more segments left. Dave and I are going to wrap up later in the day, you watching The Cube at VeeamON 2022, be right back. (upbeat music)

(pleasant music) >> We're back at Veeamon 2022. We're here at the Aria hotel in Las Vegas. This is theCube's continuous coverage. We're in day two. Welcome to the CXO session. We have CEO, CTO, CSO, chief strategy officer. Brett Diamond is the CEO, Justin Giardina is the CTO, and Dante Orsini is the chief strategy officer for 11:11 Systems recently named, I guess today, the impact cloud service provider of the year. Congratulations, guys. Welcome to theCube. Welcome back to theCube. Great to see you again. >> Thank you. >> Great. >> Likewise. >> Thanks for having us. Okay, Brett, let's start with you. Give us the overview of 11:11, your focus area, talk about the Island acquisition, what that's all about, give us the setup. >> Yeah, so we started 11:11, really, with a focus on taking the three core pillars of our business, which are cloud, connectivity, and security, bring them together into one platform, allowing a much easier way for our customers and our partners to procure those three solution sets through a single company and really focus on the three main drivers of the business, which, you know, have a litany of other services associated with them under each platform. >> Okay, so Justin, cloud connectivity and security, they all dramatically changed in March of 2020. Everybody had to go to the cloud, had to rethink the network, had to secure remote workers. So what did you see, from a CTO's perspective, what changed and how did 11:11 respond? >> Sure, so early on, when we built our cloud, even back into 2008, we really focused on enterprise grade features, one of which being very flexible in the networking. So we found early on was that we would be able to architect solutions for customers that were dipping their toe in the cloud and set ourselves apart from some of the vendors at the time. So if you fast forward from 2008 until today, we still see that as a main component for IaaS and DRaaS and the ability to start taking into some of the things Brett talked about, where customers may need a point to point circuit to offload data connectivity to us, or develop SD-WAN and multi-cloud solutions to connect to their resources in the cloud. In my opinion, it's just the natural progression of what we set out to do in 2008. And to couple that with the security, if you think about what that opens up from a security landscape, now you have multiple clouds, you have different ingress and egress points, you have different people accessing workloads in each one of these clouds, so the idea or our idea is that we can layer a comprehensive security solution over this new multi-cloud networking world and then provide visibility and manageability to our customer base. >> So what does that mean specifically for your customers? Because, I mean, we saw obviously a rapid move toward end point, cloud security, identity access. You know, people really started rethinking that as opposed to trying to just, you know, build a moat around the castle. >> Right. >> What does that mean for your customer? You take care of all that? You partner with whomever you need to partner in the ecosystem and then you provide the managed service? How does that work? >> Right. It does and that's a great analogy. You know, we have a picture of a hamburger in our office, exploded with all the components and they say, a good security policy has all the pieces and it's really synonymous with what you said. So to answer your question, yes. We have all that baked in the platform. We can offer managed services around it, but we also give the consumer the ability to access that data, whether it's a UI or API. >> So Dante, I know you talked to a lot of customers. All you do is watch the stock market go like this and like that and you say, okay, the pandemic drove all these, but when you talk to CISOs and customers, a lot of things are changing permanently. First of all, they were forced to march to digital when previously, they were like, eh, we'll get there. I mean, a lot of customers were. Let's face it. I mean, some were serious about it, but many weren't. Now, if you're not a digital business, you're out of business. What have you seen when you talk to customers in terms of the permanence of some of these changes? What are they telling you? >> Well, I think, you know, we go through this ourselves, right? The business continues to grow. You've got tons of people that are working remotely and they are going to continue to work remotely, right? As much as we'd like to offer up hybrid workspace and things like that, some folks are like, hey, I've worked it out. I'm working out great from home, right? And also, I think what Justin was saying also is, as we've seen time go on, that operating environment has gotten much more complex. You've got stuff in the data center, stuff in somebody's, you know, endpoint, you've got various different public clouds, different SAS services, right? That's why it's been phenomenal to work with Veeam because we can protect that data regardless of where it exists. But when you start to look at some of the managed security services that we're talking about, we're helping those CSOs, you know, get better visibility, better control, and take proactive action against the infrastructure when we look at threat mitigation and how to actually respond when something does happen, right? And I think that's the key because there's no shortage of great security vendors, right? But how do you tie it all together into a single solution, right, with a vendor that you can actually partner with to help secure the environment while you go focus on the things that are more strategic to the business? >> I was talking to Jim Mercer at Red Hat Summit last week. He's an IDC analyst and we did a survey, I think it was last summer, and we asked customers to your point about, there's no shortage of security tools. How do you want to buy your security? And, you know, do you want, you know, best to breed bespoke tools and you sort of put it together or do you kind of want your platform provider to do it? Now surprisingly, they said platform provider. The problem is, that's aspirational for a lot of platform providers, so they got to look to a managed service provider. So Brett, talk about the Island acquisition, what Green Cloud is, how that all fits together. >> So we acquired Island and Green Cloud last year and the reality is, the people at both of those companies and the technology is what drove us to making those acquisitions. They were the foundational pieces to 11:11. Obviously, the things that Justin has been able to create from an automation and innovation perspective at the company is transforming this business in a litany of different ways, as well. So, those two acquisitions allow us at this point to take a cloud environment on a geographic footprint, not only throughout the US but globally, have a security product that was given to us from the Green Cloud acquisition of Cascade, and add on connectivity to allow us to have all three platforms in one, all three pillars in one. >> So I like 11:11. 11:11 is near and dear to my heart. So where'd the name come from? >> Everybody asked me this question, I think, five times a day. So growing up as a kid, everyone in my family would always say 11:11 make a wish whenever you'd see it on the clock. And during COVID, we were coming up with a new name for the business. My daughter looked at the microwave, said, dad, it's 11:11, make a wish. The reality was though, I had no idea why I'd been doing it for all that time and when you look up kind of the background origination, derivation of the word, it means the time of day when everything's in line and when things are complex, especially with running all the different businesses that we have, aligning them so that they're working together, it seemed like the perfect thing >> So when I had the big corner office at IDC, I had my staff meetings at 11:11. >> Yep. >> Because the universe was aligned and then the other thing was, nobody could forget the time. So they gave me 11 minutes to be there, so they were never late. >> And now you'll see it all the time, even when you don't want to. (chuckles) >> So Justin, we've been talking a lot about ransomware and not just backup, but recovery. My friend, Fred Moore, who, you know, coined the phrase backup is one thing, recovery is everything, and recovery time, network speeds and the like are critical, especially when you're thinking cloud. How are you architecting recovery for your clients? Maybe you could dig into that a little bit. >> Sure. So it's really a multitude of things. You know, you mention ransomware. Seeing the ransomware landscape evolve over time, especially in our business with backup NDR, is very singular, you know, people protecting against host nodes. Now we're seeing ransomware be able to get into an environment, land and expand, actually delete backups, target backup vendors. So the ransomware point, I guess, trying to battle that is a multi-step process, right? You need to think about how data flows into the organization from a security perspective, from a networking perspective, you need to think about how your workloads are protected, and then when you think about backups, I know we're at Veeamon now talking about Veeam, there's a multitude of ways to protect that data, whether it's retention, whether it's immutability, air gapping data. So, while I know we focus a lot sometimes on protecting data, it's really that hamburger analogy where the sum of the parts make up the protection. >> So how do you provide services? I mean, do you say, okay, do you want immutability? There's a line item for that. You want low RPO, fast RTO? How does that all work as a customer? What am I buying from you? Is it just a managed service? We'll take care of everything, platinum, gold, silver, or is it? >> If you don't mind, so I'm glad you asked that question because this is something that's very unique about us. Years ago, his team actually built the IP because we were scaling at such an incredible rate globally through all our joint partners with Veeam that, how do we take all the intelligence that we have and his team and all of our solution architects and scale it? So they actually developed a tool called Catalyst, and it's a pre-sales tool. It's an application. You download it, you install it. It basically takes a snapshot of your environment. You start to manipulate the data. What are you trying to do, Dave? Are you trying to protect that data? Are you backing up to us? Are you trying to replicate it for DR purposes? You know, what are you doing for production, or maybe it's a migration? It analyzes the network. It analyzes all your infrastructure. It helps the SEs know immediately if we're a feasible solution based on what you are trying to do. So, nobody in the space is doing this and that's been a huge key to our growth because the channel community, as well as the customer, they're working with real data. So we can get past all the garbage, you get right to what's important for them for the outcome. >> Yeah, that's huge. Who do you guys sell to? Is it more mid-size businesses that maybe don't have the large teams? Is it larger enterprises who want to compliment to their business? Is it both? >> Well, I would say with the two acquisitions that we made to go to market sales strategies and the clientele were very different, when you look at Green Cloud, they're selling predominantly wholesale through MSPs and those MSPs are mostly selling to SMBs, right? So we covered that SMB market for the most part through our acquisition of Green Cloud. Island, on the other hand, was more focused on selling direct, inbound, through VARs through the channel, mid-enterprise, big enterprise. So really, those two acquisitions outside of the IP that we got from the systems, we have every single go to market sales strategy and we're aligned from SMB all the way up to the Fortune 500. >> I heard a stat a couple months ago that less than 50% of enterprises have a SAQ. That blew me away. And, you know, even small businesses need one. They may not be able to afford, but there's certainly a medium size or a larger business should have some kind of SAQ. Does that stat jive with what you're seeing in the marketplace? >> A hundred percent. >> If that's true, the need for a managed service like this, it's going to explode. It is exploding, I mean. >> Yeah, I mean, a hundred percent, right? There is zero unemployment in the cyberspace, right? Just North America alone, there's about a million or so folks in that space and right now you've got about 600,000 open recs just in North America, right? So earlier, we talked about no shortage of tools, right? But the shortage of headcount is a significant challenge, big time, right? Most importantly, the people that you do have on staff, they've got alert fatigue from the tools that they do have. That's why you're seeing this massive surgence in the managed security services provider. >> Lack of talent is number one challenge for CISOs. That's what they'll tell you and there's no end in sight to that. And it's, you know, another tool and it's amazing 'cause you see security companies popping up all the time. I mean, billion dollar valuations, I mean, Lacework did a billion dollar raise. And so, there's no shortage of funding. Now, maybe that'll change, you know, with the market but I wanted to turn our attention to the keynotes this morning. You guys got some serious love up on stage. There was a demo. It was a pretty cool demo, fast recovery, very tight RPO, as I recall. It was, I think, four minutes of, of data loss? Is that right? Is that the right stat? I was happy it wasn't zero data loss 'cause there's really, you know, no such thing, but so you got to feel good about that. Tell us about how that all came about, your relationship with Veeam. Who wants to take it? >> Sure, I can take a stab at it. So two of the things that I'm most excited about, at least with this Veeamon, is our team was able to work with Veeam on that demo, and what that demo was showing was some CDP based features for cloud providers. So we're really happy to see that and the reason why we're happy to see that is that with the Veeam platform, it's now given the customers the ability to do things like snapshot replication, CDP replication, on-prem backup, cloud backup, immutability air gap, the list goes on and on. And in our opinion, having a singular software vendor that can provide all that, you know, with a cloud provider on-prem or not is really like, the icing on the cake. So for us, it's very exciting to see that, and then also coupled with a lot of the innovation that's Veeam's doing in the SAS space, right? So again, having that umbrella product that can cover all those use cases. >> I'll tell you, that was a very cool demo. If you can get a YouTube of that demo, I'll make sure we put it in the show notes of this video or maybe pop it into one of the blogs that we write about it. So, how do you guys feel? I mean, this is a new chapter for you. Very cool, with a couple of acquisitions that are now the main spring of your strategy, so the first Veeamon in a couple years. So what's the vibe been like for you? What's the nighttime activity, the customer interaction? I know you guys are running a lot of the backend demos, so you're everywhere. What's the vibe like at Veeamon and how does it feel to be back? >> I'll give that one to Dante as far as the vibes, so far. >> Yeah, yeah, you got a lot of experience. >> Yeah, let me loose on this one, Dave. I'm like, so excited about this, right? It's been far too long to get face to face again and Veeam always does it right. And I think that for years, we've been back ending like, all the hands on lab infrastructure here, but forget about that. I think the part that's really exciting is getting face to face with such a great team, right? We have phenomenal architects that we work with at Veeam day in and day out. They put up with us, pushing them, pushing them, pushing them and together, we've been able to create a lot of magic together, right? But I think you can't replace the human interaction that we've all been starving for, for the last two years. But the vibe's always fantastic at Veeam. If you're going to be around tonight, I'll be looking forward to enjoying some of that Veeam love with you at the after party. >> Yeah, well, famous after parties. We'll see if that culture continues. I have a feeling it will. Brett, where do you want to take 11:11? New phase in all of your careers. You got a great crew out here, it looks like. I love that you're all out and, make some noise here, people. Let's hear it! (audience cheering) You see, this is the biggest audience we've had all week. Where do you want to take 11:11? >> I think, you know, if you look at what we've done so far in the short six months since the acquisitions of Green Cloud and Island, obviously the integration is a key piece. We're going to be laser focused on growing organically across those three pillars. We've got to put more capital and resources into the incredible IP, like I said earlier, that Justin and his team have created on those front ends, the user experience. But, you know, we made two large acquisitions, obviously M and A is a key piece for us. We're going to be diligent and we're probably going to be very aggressive on that front as well, to be able to grow this business into the global leader of cloud connectivity and security. And I think we've really hit a void in the industry that's been looking for this for a very long time and we want to be the first ones to be able to collaborate and combine those three into one. >> When the cloud started to hit the steep part of the S-curve, kind of early part of last decade, people thought, oh wow, these managed service providers are toast. The exact opposite happened. It created such a tailwind and need for consistent services and integration and managed services. We've seen it all across the stacks. So guys, wish you best of luck. Congratulations on the acquisitions, >> Thank you. >> And hope to have you back soon. >> Absolutely, thanks for having us. >> All right, keep it right there everybody. Dave Vellante for theCube's coverage of Veeamon 2022. We'll be right back after this short break. (pleasant music)

(calm music) >> Hi everybody. We're here at VeeamON 2022. This is day two of the CUBE's continuous coverage. I'm Dave Vellante. My co-host is Dave Nicholson. A ton of energy. The keynotes, day two keynotes are all about products at Veeam. Veeam, the color of green, same color as money. And so, and it flows in this ecosystem. I'll tell you right now, Michael Cade is here. He's the senior technologist for product strategy at Veeam. Michael, fresh off the keynotes. >> Yeah, yeah. >> Welcome. Danny Allen's keynote was fantastic. I mean, that story he told blew me away. I can't wait to have him back. Stay tuned for that one. But we're going to talk about protecting containers, Kasten. You guys got announcements of Kasten by Veeam, you call it K10 version five, I think? >> Yeah. So just rolled into 5.0 release this week. Now, it's a bit different to what we see from a VBR release cycle kind of thing, cause we're constantly working on a two week sprint cycle. So as much as 5.0's been launched and announced, we're going to see that trickling out over the next couple of months until we get round to Cube (indistinct) and we do all of this again, right? >> So let's back up. I first bumped into Kasten, gosh, it was several years ago at VeeamON. Like, wow this is a really interesting company. I had deep conversations with them. They had a sheer, sheer cat grin, like something was going on and okay finally you acquire them, but go back a little bit of history. Like why the need for this? Containers used to be ephemeral. You know, you didn't have to persist them. That changed, but you guys are way ahead of that trend. Talk a little bit more about the history there and then we'll get into current day. >> Yeah, I think the need for stateful workloads within Kubernetes is absolutely grown. I think we just saw 1.24 of Kubernetes get released last week or a couple of weeks ago now. And really the focus there, you can see, at least three of the big ticket items in that release are focused around storage and data. So it just encourages that the community is wanting to put these data services within that. But it's also common, right? It's great to think about a stateless... If you've got stateless application but even a web server's got some state, right? There's always going to be some data associated to an application. And if there isn't then like, great but that doesn't really work- >> You're right. Where'd they click, where'd they go? I mean little things like that, right? >> Yeah. Yeah, exactly. So one of the things that we are seeing from that is like obviously the requirement to back up and put in a lot of data services in there, and taking full like exposure of the Kubernetes ecosystem, HA, and very tiny containers versus these large like virtual machines that we've always had the story at Veeam around the portability and being able to move them left, right, here, there, and everywhere. But from a K10 point of view, the ability to not only protect them, but also move those applications or move that data wherever they need to be. >> Okay. So, and Kubernetes of course has evolved. I mean the early days of Kubernetes, they kept it simple, kind of like Veeam actually. Right? >> Yeah. >> And then, you know, even though Mesosphere and even Docker Swarm, they were trying to do more sophisticated cluster management. Kubernetes has now got projects getting much more complicated. So more complicated workloads mean more data, more critical data means more protection. Okay, so you acquire Kasten, we know that's a small part of your business today but it's going to be growing. We know this cause everybody's developing applications. So what's different about protecting containers? Danny talks about modern data protection. Okay, when I first heard that, I'm like, eh, nice tagline, but then he peel the onion. He explains how in virtualization, you went from agents to backing up of VMware instance, a virtual instance. What's different about containers? What constitutes modern data protection for containers? >> Yeah, so I think the story that Danny tells as well, is so when we had our physical agents and virtualization came along and a lot of... And this is really where Veeam was born, right, we went into the virtualization API, the VMware API, and we started leveraging that to be more storage efficient. The admin overhead around those agents weren't there then, we could just back up using the API. Whereas obviously a lot of our competition would use agents still and put that resource overhead on top of that. So that's where Veeam initially got the kickstart in that world. I think it's very similar to when it comes to Kubernetes because K10 is deployed within the Kubernetes cluster and it leverages the Kubernetes API to pull out that data in a more efficient way. You could use image based backups or traditional NAS based backups to protect some of the data, and backup's kind of the... It's only one of the ticks in the boxes, right? You have to be able to restore and know what that data is. >> But wait, your competitors aren't as fat, dumb and happy today as they were back then, right? So it can't... They use the same APIs and- >> Yeah. >> So what makes you guys different? >> So I think that's testament to the Kubernetes and the community behind that and things like the CSI driver, which enables the storage vendors to take that CSI abstraction layer and then integrate their storage components, their snapshot technologies, and other efficiency models in there, and be able to leverage that as part of a universal data protection API. So really that's one tick in the box and you're absolutely right, there's open source tools that can do exactly what we're doing to a degree on that backup and recovery. Where it gets really interesting is the mobility of data and how we're protecting that. Because as much as stateful workloads are seen within the Kubernetes environments now, they're also seen outside. So things like Amazon RDS, but the front end lives in Kubernetes going to that stateless point. But being able to protect the whole application and being very application aware means that we can capture everything and restore wherever we want that to go as well. Like, so the demo that I just did was actually a Postgres database in AWS, and us being able to clone or migrate that out into an EKS cluster as a staple set. So again, we're not leveraging RDS at that point, but it gives us the freedom of movement of that data. >> Yeah, I want to talk about that, what you actually demoed. One of the interesting things, we were talking earlier, I didn't see any CLI when you were going through the integration of K10 V5 and V12. >> Yeah. >> That was very interesting, but I'm more skeptical of this concept, of the single pane of glass and how useful that is. Who is this integration targeting? Are you targeting the sort of traditional Veeam user who is now adding as a responsibility, the management of protecting these Kubernetes environments? Or are you at the same time targeting the current owners of those environments? Cause I know you talk about shift left and- >> Yeah. >> You know, nobody needs Kubernetes if you only have one container and one thing you're doing. So at some point it's all about automation, it's about blueprints, it's about getting those things in early. So you get up, you talk about this integration, who cares about that kind of integration? >> Yeah, so I think it's a bit of both, right? So we're definitely focused around the DevOps focused engineer. Let's just call it that. And under an umbrella, the cloud engineer that's looking after Kubernetes, from an application delivery perspective. But I think more and more as we get further up the mountain, CIS admin, obviously who we speak to the tech decision makers, the solutions architects systems engineers, they're going to inherit and be that platform operator around the Kubernetes clusters. And they're probably going to land with the requirement around data management as well. So the specific VBR centralized management is very much for the backup admin, the infrastructure admin or the cloud based engineer that's looking after the Kubernetes cluster and the data within that. Still we speak to app developers who are conscious of what their database looks like, because that's an external data service. And the biggest question that we have or the biggest conversation we have with them is that the source code, the GitHub or the source repository, that's fine, that will get your... That'll get some of the way back up and running, but when it comes to a Postgres database or some sort of data service, oh, that's out of the CI/CD pipeline. So it's whether they're interested in that or whether that gets farmed out into another pre-operations, the traditional operations team. >> So I want to unpack your press release a little bit. It's full of all the acronyms, so maybe you can help us- >> Sure. >> Cipher. You got security everywhere enhance platform hardening, including KMS. That's key- >> Yeah, key management service, yeah. >> System, okay. With AWS, KMS and HashiCorp vault. Awesome, love to see HashiCorp company. >> Yeah. >> RBAC objects in UI dashboards, ransomware attacks, AWS S3. So anyway, security everywhere. What do you mean by that? >> So I think traditionally at Veeam, and continue that, right? From a security perspective, if you think about the failure scenario and ransomware's, the hot topic, right, when it comes to security, but we can think about security as, if we think about that as the bang, right, the bang is something bad's happen, fire, flood, blood, type stuff. And we tend to be that right hand side of that, we tend to be the remediation. We're definitely the one, the last line of defense to get stuff back when something really bad happens. And I think what we've done from a K10 point of view, is not only enhance that, so with the likes of being able to... We're not going to reinvent the wheel, let's use the services that HashiCorp have done from a HashiCorp vault point of view and integrate from a key management system. But then also things like S3 or ransomware prevention. So I want to know if something bad's happened and Kasten actually did something more generic from a Veeam ONE perspective, but one of the pieces that we've seen since we've then started to send our backups to an immutable object storage, is let's be more of that left as well and start looking at the preventative tasks that we can help with. Now, we're not going to be a security company, but you heard all the way through Danny's like keynote, and probably when he is been on here, is that it's always, we're always mindful of that security focus. >> On that point, what was being looked for? A spike in CPU utilization that would be associated with encryption? >> Yeah, exactly that. >> Is that what was being looked- >> That could be... Yeah, exactly that. So that could be from a virtual machine point of view but from a K10, and it specifically is that we're going to look at the S3 bucket or the object storage, we're going to see if there's a rate of change that's out of the normal. It's an abnormal rate. And then with that, we can say, okay, that doesn't look right, alert us through observability tools, again, around the cloud native ecosystem, Prometheus Grafana. And then we're going to get insight into that before the bang happens, hopefully before the bang. >> So that's an interesting when we talk about adjacencies and moving into this area of security- >> We're talking to Zeus about that too. >> Exactly. That's that sort of creep where you can actually add value. It's interesting. >> So, okay. So we talked about shift left, get that, and then expanded ecosystem, industry leading technologies. By the way, one of them is the Red Hat Marketplace. And I think, I heard Anton's... Anton was amazing. He is the head of product management at Veeam. Is been to every VeeamON. He's got family in Ukraine. He's based in Switzerland. >> Yeah. >> But he chose not to come here because he's obviously supporting, you know, the carnage that's going on in Ukraine. But anyway, I think he said the Red Hat team is actually in Ukraine developing, you know, while the bombs are dropping. That's amazing. But anyway, back to our interview here, expanded ecosystem, Red Hat, SUSE with Rancher, they've got some momentum. vSphere with Tanzu, they're in the game. Talk about that ecosystem and its importance. >> Yeah, and I think, and it goes back to your point around the CLI, right? Is that it feels like the next stage of Kubernetes is going to be very much focused towards the operator or the operations team. The CIS admin of today is going to have to look after that. And at the moment it's all very command line, it's all CLI driven. And I think the marketplace is OpenShift, being our biggest foothold around our customer base, is definitely around OpenShift. But things like, obviously we are a longstanding alliance partner with VMware as well. So their Tanzu operations actually there's support for TKGS, so vSphere Tanzu grid services is another part of the big release of 5.0. But all three of those and the common marketplace gives us a UI, gives us a way of being able to see and visualize that rather than having to go and hunt down the commands and get our information through some- >> Oh, some people are going to be unhappy about that. >> Yeah. >> But I contend the human eye has evolved to see in color for a very good reason. So I want to see things in red, yellow, and green at times. >> There you go, yeah. >> So when we hear a company like Veeam talk about, look we have no platform agenda, we don't care which cloud it's in. We don't care if it's on-prem or Google Azure, AWS. We had Wasabi on, we have... Great, they got an S3 compatible, you know, target, and others as well. When we hear them, companies like you, talk about that consistent experience, single pane of glass that you're skeptical of, maybe cause it's technically challenging, one of the things, we call it super cloud, right, that's come up. Danny and I were riffing on that the other day and we'll do that more this afternoon. But it brings up something that we were talking about with Zeus, Dave, which is the edge, right? And it seems like Kubernetes, and we think about OpenShift. >> Yeah. >> We were there last week at Red Hat Summit. It's like 50% of the conversation, if not more, was the edge. Right, and really true edge, worst cases, use cases. Two weeks ago we were at Dell Tech, there was a lot of edge talk, but it was retail stores, like Lowe's. Okay, that's kind of near edge, but the far edge, we're talking space, right? So seems like Kubernetes fits there and OpenShift, you know, particularly, as well as some of the others that we mentioned. What about edge? How much of what you're doing with container data protection do you see as informing you about the edge opportunity? Are you seeing any patterns there? Nobody's really talking about it in data protection yet. >> So yeah, large scale numbers of these very small clusters that are out there on farms or in wind turbines, and that is definitely something that is being spoken about. There's not much mention actually in this 5.0 release because we actually support things like K3s,(indistinct), that all came in 4.5, but I think, to your first point as well, David, is that, look, we don't really care what that Kubernetes distribution is. So you've got K3s lightweight Kubernetes distribution, we support it, because it uses the same native Kubernetes APIs, and we get deployed inside of that. I think where we've got these large scale and large numbers of edge deployments of Kubernetes and that you require potentially some data management down there, and they might want to send everything into a centralized location or a more centralized location than a farm shed out in the country. I think we're going to see a big number of that. But then we also have our multi cluster dashboard that gives us the ability to centralize all of the control plane. So we don't have to go into each individual K10 deployment to manage those policies. We can have one big centralized management multi cluster dashboard, and we can set global policies there. So if you're running a database and maybe it's the same one across all of your different edge locations, where you could just set one policy to say I want to protect that data on an hourly basis, a daily basis, whatever that needs to be, rather than having to go into each individual one. >> And then send it back to that central repository. So that's the model that you see, you don't see the opportunity, at least at this point in time, of actually persisting it at the edge? >> So I think it depends. I think we see both, but again, that's the footprint. And maybe like you mentioned about up in space having a Kubernetes cluster up there. You don't really want to be sending up a NAS device or a storage device, right, to have to sit alongside it. So it's probably, but then equally, what's the art of the possible to get that back down to our planet, like as part of a consistent copy of data? >> Or even a farm or other remote locations. The question is, I mean, EVs, you know, we believe there's going to be tons of data, we just don't.. You think about Tesla as a use case, they don't persist a ton of their data. Maybe if a deer runs across, you know, the front of the car, oh, persist that, send that back to the cloud. >> I don't want anyone knowing my Tesla data. I'll tell you that right now. (all laughing) >> Well, there you go, that one too. All right, well, that's future discussion, we're still trying to squint through those patterns. I got so many questions for you, Michael, but we got to go. Thanks so much for coming to theCUBE. >> Always. >> Great job on the keynote today and good luck. >> Thank you. Thanks for having me. >> All right, keep it right there. We got a ton of product talk today. As I said, Danny Allan's coming back, we got the ecosystem coming, a bunch of the cloud providers. We have, well, iland was up on stage. They were just recently acquired by 11:11 Systems. They were an example today of a cloud service provider. We're going to unpack it all here on theCUBE at VeeamON 2022 from Las Vegas at the Aria. Keep it right there. (calm music)

>> From theCUBE Studios in Palo Alto in Boston, bringing you data driven insights from theCUBE and ETR. This is Breaking Analysis with Dave Vellante. >> Cybersecurity stocks have been sending mixed signals as of late, mostly negative like much of tech, but some such as Palo Alto Networks, despite a tough go of it recently have held up better than most tech names. Others like CrowdStrike, had been out performing Broader Tech in March, but then flipped in May. Okta's performance was pretty much tracking along with CrowdStrike for most of the past several months, a little bit below, but then the Okta hack changed the trajectory of that name. Zscaler has crossed the critical billion dollar ARR revenue milestone, and now sees a path to five billion dollars in revenue, but the company stock fell sharply after its last earnings report and has been on a down trend since last November. Meanwhile, CyberArk's recent beat and raise, was encouraging and the stock acted well after its last report. Security remains the number one initiative priority amongst IT organizations and the spending momentum for many high flying cyber names remain strong. So what gives in cyber security? Hello, and welcome to this week's Wikibon CUBE insights powered by ETR. In this breaking analysis, we focus on security and will update you on the latest data from ETR to try to make sense out of the market and read into what this all means in both the near and long term, for some of our favorite names in cyber. First, the news. There's always something happening in security news cycles. The big recent news is new President Rodrigo Chavez declared a national emergency in Costa Rica due to the preponderance of Russian cyber attacks on the country's critical infrastructure. Such measures are normally reserved for natural disasters like earthquakes, but this move speaks to the nature of today's cyber threats. Of no surprise is modern superpower warfare even for a depleted power like Russia almost certainly involves cyber warfare as we continue to see in Ukraine. Privately held Arctic Wolf Networks hired Dustin Williams as its new CFO. Williams has taken three companies to IPO, including Nutanix in 2016, a very successful IPO for that company. Whether AWN chooses to pull the trigger this year or will wait until markets are less choppy or obviously remains to be seen. But it's a pretty clear sign the company is headed to IPO at some point. Now, big point of discussion this week at Red Hat Summit in Boston and the prior week at Dell technologies world was security. In the case of Red Hat, securing the digital supply chain was the main theme. And from Dell building, many security features into its storage arrays and cyber resilience services into its as a service offering called Apex. And we're seeing a trend where buyers want to reduce the number of bespoke tools they use if they, in fact can. Here's IDC's Jim Mercer, sharing data from a recent survey they conducted on the topic. Play the clip. >> Interestingly, we did a survey, I think around last August or something. And one of the questions was around where do you want your security, right? Where do you want to get your DevSecOps security from? Do you want to get it from individual vendors, right? Or do you want to get it from like your platforms that you're using and deploying changes in Kubernetes? >> Great question. What did they say? >> The majority of them, they're hoping they can get it built into the platform. That's really what they want-- >> Now, whether that's actually achievable is debatable because you have so much innovation and investment going on from the likes of startups and for instance, lace work or sneak and security companies that you see even trying to build platforms, you've got CrowdStrike, Okta, Zscaler and many others, trying to build security platforms and put it all under their umbrella. Now the last point will hit here is there was a lot of buzz in the news about Okta. The reaction to what was a relatively benign hack was pretty severe and probably overblown, but Okta's stock is paying the price of what is generally considered a blown communications plan versus a technical failure. Remember, identity is not an easy thing to rip and replace and Okta remains a best-of-breed player and leader in the space. So we're going to look at some ETR data later in this segment to try and make sense of the recent action in the market and certain names. Speaking of which let's take a look at how some of the names in cybersecurity have fared relative to some of the indices and relative indicators that we like to look at. Here's a Google finance comparison for a number of stocks and names in the bottom there you can see we plot the hack ETF which tracks security stocks. This is a year to date view. And so we don't show it here but the tech heavy NASDAQ is off around 26% year to date whereas the cyber ETF that we're showing is down 18%, okay. So cyber holding up a little bit better than broader tech as we've reported earlier, was actually much better and still seems to be a gap there, but the data are mixed. You can see Okta is way off relative to its peers. That's a combination of the breach that we talked about but also the run up in the stock since COVID. CrowdStrike was actually faring better but broke this month, we'll see how it's upcoming earnings announcements are received when it announces on June 2nd after the close. Palo Alto in the light blue has done better than most and until recently was holding up quite well. And of course, Sailpoint is another identity specialist, it is kind of off the charts here because it's going private with the acquisition by Thoma Bravo at nearly seven billion dollars. So you see some mixed signals in cyber these past several months and weeks. And so we're trying to understand what that all means. So let's take a look at the survey data and see how spending momentum is holding up. As we've reported IT spending forecast, at the macro level, they've come off their 8% highs from the end of the year, the ETRS December survey, but robust tech spending is still there. It's expected at nearly seven percent and this is amongst 1200 ETR respondents. Here's a picture from the ETR survey of the cybersecurity landscape. That y-axis that's net score or a measure of spending momentum and that horizontal access is overlap. We used to talk about it as a market share which is a measure of pervasiveness in the data set. That dotted red line at 40% indicates an elevated spending momentum level on the vertical axis and we filter the names and limited to only those with a hundred or more responses in the ETR survey. Then the pictures still pretty crowded as you can see. You got lots of companies above the red dotted line, including Microsoft which is up into the right, they're so far off the chart, it's just amazing. But also Palo Alto and Okta, Auth0, which of course is now owned by Okta, Zscaler, CyberArk is making moves. Sailpoint and Cloudflare, they're all above that magic 40% line. Now, you look at Cisco, it shows a very large presence in the horizontal axis in the data set. And it's got pretty respectable momentum and you see Splunk doing okay, no before and tenable just below that 40% line and a lot of names in the very respectable 20% zone. And we've included some legacy names just for context that fall below the zero percent line with a negative net score. And that means a larger proportion, that negative net score means a larger proportion of their customers in the survey are spending less than those that are spending more. Now, typically for these legacy names you're going to have a huge proportion of customers who have flat spending that kind of fat middle and that's why they sort of don't have that highly elevated score, but they're still viable as they get the recurring revenue each year. But the bottom line is that spending remains robust for some of the top names that we've talked about earlier despite their rocky stock performance. Now, let's filter this data a bit more to make it a little bit easier to read. So to do that, we take out Microsoft because they're just so dominant and we cherry pick some names to make the data more consumable and scannable. The other data point we've added is Okta's net score breakdown, the multicolored rows there, that row in the bottom right. Net score, it measures the percent of customers that are adding the platform new, that's the lime green, at 18% for Okta. The forest green is at 42%. That's the percent of customers in the survey that are spending six percent or more. The gray is flat spending. That's 32% for Okta, this past survey. The pink is customers that are spending less, that's three percent. They're spending six percent or worse in the survey, so only three percent for Okta. And the bright red at three percent is decommissioning the platform. You subtract the reds from the greens and you get a net score, well, into the 50s for Okta and you can see. We highlight Okta here because it's a name that we've been following for quite some time and customers have given us really solid feedback on the technology and up until the hack, they're affinity to Okta, but that seems to be continuing. We'll talk more about that. This recent breach to Okta has caused us to take a closer look. And you may recall, we reported with our ETR colleague, Eric Bradley. The breach was announced right in the middle of ETR collecting data in the last survey. And while we did see a noticeable downtick right after the announcement, the exposure of the hack and Okta's net score just after the breach was disclosed, you can see the combination of Okta and Auth0 remains very strong. I asked Eric Bradley this morning what he thought about Okta, and he pointed out that you can't evaluate this company on its price to earnings ratio. But it's forward sales multiple is now below 7X. And while attractive, these high flyers at some point, Eric says, they got to start making a profit. So you going to hold that thought, we'll come back to that. Now, another cut of the ETR data to look at our four star security names here. A while back we developed a methodology to try and cut through the noise of the crowded security sector using the ETR data to evaluate two key metrics; net score and shared N. Net score again is, spending momentum, the latter is an indicator of presence in the data set which is a proxy for market presence. Okay, we assigned those companies that cracked the top 10 in both net score and shared N, we give them four stars, okay, if they make the top 10. This chart here shows the April survey data for those companies with an N that's greater than, equal to a hundred responses. So again, we're filtering on those with a hundred or more responses. The table on the left that you see there, that's sorted by net score, okay. So we're sorting by spending momentum. And then the one on the right is sorted by shared N, so their presence in the data set. Seven companies hit the top 10 for both categories; Palo Alto Network, Splunk, CrowdStrike Okta, Proofpoint, Fortinet and Zscaler. Now, remember, take a look, Okta excludes Auth0, in this little methodology that we came up with. Auth0 didn't make the cuts but it hits the top 10 for net score. So if you add in Auth0's 112 N there that you see on the right. You add that into Okta, we put Okta in the number two spot in the survey on the right most table with the shared N of 354. Only Cisco has a higher presence in the data set. And you can see Cisco in the left lands just below that red dotted line. That's the top 10 in security. So if we were to combine Okta and Auth0 as one, Cisco would make the cut and earn four stars. Now, some other notables are CyberArk, which is just below the red line on the right most chart with an impressive 177 shared N. Again, if you combine Auth0 and Okta, CyberArk makes the four star grade because it's in the top 10 for net score on the left. And Sailpoint is another notable with a net score above 50% and it's got a shared N of 122, which is respectable. So despite the market's choppy waters, we're seeing some positive signs in the survey data for some of the more prominent names that we've been following for the last couple of years. So what does this mean for the markets going forward? As always, when we see these confusing signs we like to reach out to the network and one of the sharpest traders out there is Chip Simonton. We've quoted him before and we like to share some of his insights. And so we're going to highlight some of that here. So technically, almost every good tech stock is oversold. And as such, he suggested we might see a bounce here. We certainly are seeing that on this Friday, the 13th. But the right call tactically has been to sell into the rally these past several months, so we'll see what happens on Monday. The key issue with the name like Okta and some other momentum names like CrowdStrike and Zscaler is that when money comes back into tech, it's likely going to go to the FAANG stocks, the Facebook, Apple, Amazon, Netflix, Google, and of course, you put Microsoft in there as well. And we'll see about Amazon, by the way, it's kind of out of favor right now, as everyone's focused on the retail side of the business meanwhile it's cloud business is booming and that's where all the profit is. We think that should be the real focus for Amazon. But the point is, for these momentum names in cybersecurity that don't make money, they face real headwinds, as growth is slowing overall and interest rates rise, that makes the net present value of these investments much less attractive. We've talked about that before. But longer term, we agree with Chip Simonton that these are excellent companies and they will weather the storm and we think they're going to lead their respective markets. And in cyber, we would expect continued M&A activity, which could act as a booster shot in the arms of these names. Now in 2019, we saw the ETR data, it pointed to CrowdStrike, Zscaler, Okta and others in the security space. Some of those names that really looked to us like they were moving forward and the pandemic just created a surge in these names and admittedly they got out over their skis. But the data suggests that these leading companies have continued momentum and the potential for stay in power. Unlike the SolarWinds hack, it seems at this point anyway that Okta will recover in the market. For the reasons that we cited, investors, they might stay away for some time but longer term, there's a shift in CSO security strategies that appear to be permanent. They're really valuing cloud-based modern platforms, these platforms will likely continue to gain share and carry their momentum forward. Okay, that's it for now, thanks to Stephanie Chan, who helps with the background research and with social, Kristen Martin and Cheryl Knight help get the word out and do some great work as well. Alex Morrison is on production and handles all of our podcast. Alex, thank you. And Rob Hof is our Editor in Chief at SiliconANGLE. Remember, all these episodes, they're available as podcast, you can pop in the headphones and listen, just search "Breaking Analysis Podcast." I publish each week on wikibon.com and SiliconANGLE.com. Don't forget to check out etr.ai, best in the business for real customer data. It's an awesome platform. You can reach me at dave.vellante@siliconangle.com or @dvellante. You can comment on our LinkedIn posts. This is Dave Vellante for the CUBEinsights powered by ETR. Thanks for watching. And we'll see you next time. (bright upbeat music)

(upbeat music) >> Welcome back to theCUBE. We're covering Red Hat Summit 2022. We're going to wrap up now, Dave Vellante, Paul Gillin. We want to introduce you to Stephanie Chan, who's our new correspondent. Stephanie, one of your first events, your very first CUBE event. So welcome. >> Thank you. >> Up from NYC. Smaller event, but intimate. You got a chance to meet some folks last night at some of the after parties. What are your overall impressions? What'd you learn this week? >> So this has been my first in-person event in over two years. And even though, like you said, is on the smaller scale, roughly around 1000 attendees, versus it's usual eight to 10,000 attendees. There's so much energy, and excitement, and openness in these events and sessions. Even before and after the sessions people have been mingling and socializing and hanging out. So, I think a lot of people appreciate these in-person events and are really excited to be here. >> Cool. So, you also sat in some of the keynotes, right? Pretty technical, right? Which is kind of new to sort of your genre, right? I mean, I know you got a financial background but, so what'd you think of the keynotes? What'd you think of the format, the theater in the round? Any impressions of that? >> So, I think there's three things that are really consistent in these Red Hat Summit keynotes. There's always a history lesson. There's always, you know, emphasis in the culture of openness. And, there's also inspirational stories about how people utilize open source. And I found a lot of those examples really compelling and interesting. For instance, people use open source in (indistinct), and even in space. So I really enjoyed, you know, learning about all these different people and stories. What about you guys? What do you think were the big takeaways and the best stories that came out of the keynotes? >> Paul, want to start? >> Clearly the Red Hat Enterprise Linux 9 is a major rollout. They do that only about every three years. So that's a big deal to this audience. I think what they did in the area of security, with rolling out sigstore, which is a major new, I think an important new project that was sort of incubated at Red Hat. And they're trying to put in to create an open source ecosystem around that now. And the alliances. I'm usually not that much on partnerships, but the Accenture and the Microsoft partnerships do seem to be significant to the company. And, finally, the GM partnership which I think was maybe kind of the bombshell that they sort of rushed in at the last minute. But I think has the biggest potential impact on Red Hat and its partner ecosystem that is really going to anchor their edge architecture going forward. So I didn't see it so much on the product front, but the sense of Red Hat spreading its wings, and partnering with more companies, and seeing its itself as really the center of an ecosystem indicates that they are, you know, they're in a very solid position in their business. >> Yeah, and also like the pandemic has really forced us into this new normal, right? So customer demand is changing. There has been the shift to remote. There's always going to be a new normal according to Paul, and open source carries us through that. So how do you guys think Red Hat has helped its portfolio through this new normal and the shift? >> I mean, when you think of Red Hat, you think of Linux. I mean, that's where it all started. You think OpenShift which is the application development platforms. Linux is the OS. OpenShift is the application development platform for Kubernetes. And then of course, Ansible is the automation framework. And I agree with you, ecosystem is really the other piece of this. So, I mean, I think you take those three pieces and extend that into the open source community. There's a lot of innovation that's going around each of those, but ecosystems are the key. We heard from Stefanie Chiras, that fundamental, I mean, you can't do this without those gap fillers and those partnerships. And then another thing that's notable here is, you know, this was, I mean, IBM was just another brand, right? I mean, if anything it was probably a sub-brand, I mean, you didn't hear much about IBM. You certainly had no IBM presence, even though they're right across the street running Think. No Arvind present, no keynote from Arvind, no, you know, Big Blue washing. And so, I think that's a testament to Arvind himself. We heard that from Paul Cormier, he said, hey, this guy's been great, he's left us alone. And he's allowed us to continue innovating. It's good news. IBM has not polluted Red Hat. >> Yes, I think that the Red Hat was, I said at the opening, I think Red Hat is kind of the tail wagging the dog right now. And their position seems very solid in the market. Clearly the market has come to them in terms of their evangelism of open source. They've remained true to their business model. And I think that gives them credibility that, you know, a lot of other open source companies have lacked. They have stuck with the plan for over 20 years now and have really not changed it, and it's paying off. I think they're emerging as a company that you can trust to do business with. >> Now I want to throw in something else here. I thought the conversation with IDC analyst, Jim Mercer, was interesting when he said that they surveyed customers and they wanted to get the security from their platform vendor, versus having to buy these bespoke tools. And it makes a lot of sense to me. I don't think that's going to happen, right? Because you're going to have an identity specialist. You're going to have an endpoint specialist. You're going to have a threat detection specialist. And they're going to be best of breed, you know, Red Hat's never going to be all of those things. What they can do is partner with those companies through APIs, through open source integrations, they can add them in as part of the ecosystem and maybe be the steward of that. Maybe that's the answer. They're never going to be the best at all those different security disciplines. There's no way in the world, Red Hat, that's going to happen. But they could be the integration point. And that would be, that would be a simplifying layer to the equation. >> And I think it's smart. You know, they're not pretending to be an identity in access management or an anti-malware company, or even a zero trust company. They are sticking to their knitting, which is operating system and developers. Evangelizing DevSecOps, which is a good thing. And, that's what they're going to do. You know, you have to admire this company. It has never gotten outside of its swim lane. I think it's understood well really what it wants to be good at. And, you know, in the software business knowing what not to do is more important than knowing what to do. Is companies that fail are usually the ones that get overextended, this company has never overextended itself. >> What else do you want to know? >> And a term that kept popping up was multicloud, or otherwise known as metacloud. We know what the cloud is, but- >> Oh, supercloud, metacloud. >> Supercloud, yeah, here we go. We know what the cloud is but, what does metacloud mean to you guys? And why has it been so popular in these conversations? >> I'm going to boot this to Dave, because he's the expert on this. >> Well, expert or not, but I mean, again, we've coined this term supercloud. And the idea behind the supercloud or what Ashesh called metacloud, I like his name, cause it allows Web 3.0 to come into the equation. But the idea is that instead of building on each individual cloud and have compatibility with that cloud, you build a layer across clouds. So you do the hard work as a platform supplier to hide the underlying primitives and APIs from the end customer, or the end developer, they can then add value on top of that. And that abstraction layer spans on-prem, clouds, across clouds, ultimately out to the edge. And it's new, a new value layer that builds on top of the hyperscale infrastructure, or existing data center infrastructure, or emerging edge infrastructure. And the reason why that is important is because it's so damn complicated, number one. Number two, every company's becoming a software company, a technology company. They're bringing their services through digital transformation to their customers. And you've got to have a cloud to do that. You're not going to build your own data center. That's like Charles Wang says, not Charles Wang. (Paul laughing) Charles Phillips. We were just talking about CA. Charles Phillips. Friends don't let friends build data centers. So that supercloud concept, or what Ashesh calls metacloud, is this new layer that's going to be powered by ecosystems and platform companies. And I think it's real. I think it's- >> And OpenShift, OpenShift is a great, you know, key card for them or leverage for them because it is perhaps the best known Kubernetes platform. And you can see here they're really doubling down on adding features to OpenShift, security features, scalability. And they see it as potentially this metacloud, this supercloud abstraction layer. >> And what we said is, in order to have a supercloud you got to have a superpaz layer and OpenShift is that superpaz layer. >> So you had conversations with a lot of people within the past two days. Some people include companies, from Verizon, Intel, Accenture. Which conversation stood out to you the most? >> Which, I'm sorry. >> Which conversation stood out to you the most? (Paul sighs) >> The conversation with Stu Miniman was pretty interesting because we talked about culture. And really, he has a lot of credibility in that area because he's not a Red Hat. You know, he hasn't been a Red Hat forever, he's fairly new to the company. And got a sense from him that the culture there really is what they say it is. It's a culture of openness and that's, you know, that's as important as technology for a company's success. >> I mean, this was really good content. I mean, there were a lot, I mean Stefanie's awesome. Stefanie Chiras, we're talking about the ecosystem. Chris Wright, you know, digging into some of the CTO stuff. Ashesh, who coined metacloud, I love that. The whole in vehicle operating system conversation was great. The security discussion that we just had. You know, the conversations with Accenture were super thoughtful. Of course, Paul Cormier was a highlight. I think that one's going to be a well viewed interview, for sure. And, you know, I think that the customer conversations are great. Red Hat did a really good job of carrying the keynote conversations, which were abbreviated this year, to theCUBE. >> Right. >> I give 'em a lot of kudos for that. And because, theCUBE, it allows us to double click, go deeper, peel the onion a little bit, you know, all the buzz words, and cliches. But it's true. You get to clarify some of the things you heard, which were, you know, the keynotes were, were scripted, but tight. And so we had some good follow up questions. I thought it was super useful. I know I'm leaving somebody out, but- >> We're also able to interview representatives from Intel and Nvidia, which at a software conference you don't typically do. I mean, there's the assimilation, the combination of hardware and software. It's very clear that, and this came out in the keynote, that Red Hat sees hardware as matter. It matters. It's important again. And it's going to be a source of innovation in the future. That came through clearly. >> Yeah. The hardware matters theme, you know, the old days you would have an operating system and the hardware were intrinsically linked. MVS in the mainframe, VAX, VMS in the digital mini computers. DG had its own operating system. Wang had his own operating system. Prime with Prime OS. You remember these days? >> Oh my God. >> Right? (Paul laughs) And then of course Microsoft. >> And then x86, everything got abstracted. >> Right. >> Everything became x86 and now it's all atomizing again. >> Although WinTel, right? I mean, MS-DOS and Windows were intrinsically linked for many, many years with Intel x86. And it wasn't until, you know, well, and then, you know, Sun Solaris, but it wasn't until Linux kind of blew that apart. And the internet is built on the lamp stack. And of course, Linux is the fundamental foundation for Red Hat. So my point is, that the operating system and the hardware have always been very closely tied together. Whether it's security, or IO, or registries and memory management, everything controlled by the OS are very close to the hardware. And so that's why I think you've got an affinity in Red Hat to hardware. >> But Linux is breaking that bond, don't you think? >> Yes, but it still has to understand the underlying hardware. >> Right. >> You heard today, how taking advantage of Nvidia, and the AI capabilities. You're seeing that with ARM, you're seeing that with Intel. How you can optimize the operating system to take advantage of new generations of CPU, and NPU, and CPU, and PU, XPU, you know, across the board. >> Yep. >> Well, I really enjoyed this conference and it really stressed how important open source is to a lot of different industries. >> Great. Well, thanks for coming on. Paul, thank you. Great co-hosting with you. And thank you. >> Always, Dave. >> For watching theCUBE. We'll be on the road, next week we're at KubeCon in Valencia, Spain. We're at VeeamON. We got a ton of stuff going on. Check out thecube.net. Check out siliconangle.com for all the news. Wikibon.com. We publish there weekly, our breaking analysis series. Thanks for watching everybody. Dave Vellante, for Paul Gillin, and Stephanie Chan. Thanks to the crew. Shout out, Andrew, Alex, Sonya. Amazing job, Sonya. Steven, thanks you guys for coming out here. Mark, good job corresponding. Go to SiliconANGLE, Mark's written some great stuff. And thank you for watching. We'll see you next time. (calm music)

(upbeat music) >> Welcome back. We're winding down theCUBE's coverage of Red Hat Summit 2022. We're here at the Seaport in Boston. It's been two days of a little different Red Hat Summit. We're used to eight, 9,000 people. It's much smaller event this year, fewer developers or actually in terms of the mix, a lot more suits this year, which is kind of interesting to see that evolution and a big virtual audience. And I love the way, the keynotes we've noticed are a lot tighter. They're pithy, on time, they're not keeping us in the hall for three hours. So we appreciate that kind of catering to the virtual audience. Dave Vellante here with my co-host, Paul Gillin. As to say things are winding down, there was an analyst event here today, that's ended, but luckily we have Jim Mercer here as a research director at IDC. He's going to share maybe some of the learnings from that event today and this event overall, we're going to talk about DevSecOps. And Kirsten Newcomer is director of security, product management and hybrid platforms at Red Hat. Folks, welcome. >> Thank you. >> Thank you. >> Great to see you. >> Great to be here. >> Security's everywhere, right? You and I have spoken about the supply chain hacks, we've done some sort of interesting work around that and reporting around that. I feel like SolarWinds created a new awareness. You see these moments, it's Stuxnet, or WannaCry and now is SolarWinds very insidious, but security, Red Hat, it's everywhere in your portfolio. Maybe talk about the strategy. >> Sure, absolutely. We feel strongly that it's really important that security be something that is managed in a holistic way present throughout the application stack, starting with the operating system and also throughout the life cycle, which is partly where DevSecOps comes in. So Red Hat has kind of had a long history here, right? Think SELinux and Red Hat Enterprise Linux for mandatory access control. That's been a key component of securing containers in a Kubernetes environment. SELinux has demonstrated the ability to prevent or mitigate container escapes to the file system. And we just have continued to work up the stack as we go, our acquisition of stack rocks a little over a year ago, now known as Red Hat Advanced Cluster Security, gives us the opportunity to really deliver on that DevSecOps component. So Kubernetes native security solution with the ability to both help shift security left for the developers by integrating in the supply chain, but also providing a SecOps perspective for the operations and the security team and feeding information between the two to really try and do that closed infinity loop and then an additional investment more recently in sigstore and some technologies. >> Interesting. >> Yeah, is interesting. >> Go ahead. >> But Shift Left, explain to people what you mean by Shift Left for people might not be familiar with that term. >> Fair enough. For many, many years, right, IT security has been something that's largely been part of an operations environment and not something that developers tended to need to be engaged in with the exception of say source code static analysis tools. We started to see vulnerability management tools get added, but even then they tend to come after the application has been built. And I even ran a few years ago, I ran into a customer who said my security team won't let me get this information early. So Shift Left is all about making sure that there are security gates in the app dev process and information provided to the developer as early as possible. In fact, even in the IDE, Red Hat code ready dependency analytics does that, so that the developers are part of the solution and don't have to wait and get their apps stalled just before it's ready to go into deployment. >> Thank you. You've also been advocating for supply chain security, software supply chain. First of all, explain what a software supply chain is and then, what is unique about the security needs of that environment? >> Sure. And the SolarWinds example, as Dave said, really kind of has raised awareness around this. So just like we use the term supply chain, most people given kind of what's been happening with the pandemic, they've started hearing that term a lot more than they used to, right? So there's a supply chain to get your groceries, to the grocery store, food to the grocery store. There's a supply chain for manufacturing, where do the parts come for the laptops that we're all using, right? And where do they get assembled? Software has a supply chain also, right? So for years and even more so now, developers have been including open source components into the applications they build. So some of the supplies for the applications, the components of those applications, they can come from anywhere in the world. They can come from a wide range of open source projects. Developers are adding their custom code to that. All of this needs to be built together, delivered together and so when we think about a supply chain and the SolarWinds hack, right, there are a couple of elements of supply chain security that are particularly key. The executive order from May of last year, I think was partly in direct response to the SolarWinds hack. And it calls out that we need a software bill of materials. Now again, in manufacturing that's something folks are used to, I actually had the opportunity to contribute to the software package data exchange format, SPDX when it was first started, I've lost track of when that was. But an S-bomb is all about saying, what are all of those components that I'm delivering in my solution? It might be an application layer. It might be the host operating system layer, but at every layer. And if I know what's in what I'm delivering, I have the opportunity to learn more information about those components to track where does Log4Shell, right? When the Log4j or Spring4Shell, which followed shortly thereafter. When those hit, how do I find out which solutions that I'm running have the vulnerable components in them and where are they? The software bill of materials helps with that but you also have to know where, right. And that's the Ops side. I feel like I missed a piece of your question. >> No, it's not a silver bullet though, to your point and Log4j very widely used, but let's bring Jim into the conversation. So Jim, we've been talking about some of these trends, what's your focus area of research? What are you seeing as some of the mega trends in this space? >> I mean, I focus in DevOps and DevSecOps and it's interesting just talking about trends. Kirsten was mentioning the open source and if you look back five, six, seven years ago and you went to any major financial institution, you asked them if they use an open source. Oh, no. >> True. >> We don't use that, right. We wrote it all here. It's all from our developers-- >> Witchcraft. >> Yeah, right, exactly. But the reality is, they probably use a little open source back then but they didn't realize it. >> It's exactly true. >> However, today, not only are they not on versed to open source, they're seeking it out, right. So we have survey data that kind of indicates... A survey that was run kind of in late 2021 that shows that 70% of those who responded said that within the next two years 90% of their applications will be made up of open source. In other words, the content of an application, 10% will be written by themselves and 90% will come from other sources. So we're seeing these more kind of composite applications. Not, everybody's kind of, if you will, at that 90%, but applications are much more composite than they were before. So I'm pulling in pieces, but I'm taking the innovation of the community. So I not only have the innovation of my developers, but I can expand that. I can take the innovation to the community and bring that in and do things much quicker. I can also not have my developers worry about things that, maybe just kind of common stuff that's out there that might have already been written. In other words, just focus on the business logic, don't focus on, how to get orders or how to move widgets and those types of things that everybody does 'cause that's out there in open source. I'll just take that, right. I'll take it, somebody's perfected it, better than I'll ever do. I'll take that in and then I'll just focus and build my business logic on top of that. So open source has been a boom for growth. And I think we've heard a little bit of that (Kirsten laughs) in the last two days-- >> In the Keynotes. >> From Red Hat, right. But talking about the software bill of materials, and then you think about now I taking all that stuff in, I have my first level open source that I took in, it's called it component A. But behind component A is all these transitive dependencies. In other words, open source also uses open source, right? So there's this kind of this, if you will, web or nest, if you want to call it that, of transitive dependencies that need to be understood. And if I have five, six layers deep, I have a vulnerability in another component and I'm over here. Well, guess what? I picked up that vulnerability, right. Even though I didn't explicitly go for that component. So that's where understanding that software bill of materials is really important. I like to explain it as, during the pandemic, we've all experienced, there was all this contact tracing. It was a term where all came to mind. The software bill of materials is like the contact tracing for your open source, right. >> Good analogy. >> Anything that I've come in contact with, just because I came in contact with it, even though I didn't explicitly go looking for COVID, if you will, I got it, right. So in the same regard, that's how I do the contact tracing for my software. >> That 90% figure is really striking. 90% open source use is really striking, considering that it wasn't that long ago that one of the wraps on open source was it's insecure because anybody can see the code, therefore anybody can see the vulnerabilities. What changed? >> I'll say that, what changed is kind of first, the understanding that I can leapfrog and innovate with open source, right? There's more open source content out there. So as organizations had to digitally transform themselves and we've all heard the terminology around, well, hey, with the pandemic, we've leapfrog up five years of digital transformation or something along those lines, right? Open source is part of what helps those teams to do that type of leapfrog and do that type of innovation. You had to develop all of that natively, it just takes too long, or you might not have the talent to do it, right. And to find that talent to do it. So it kind of gives you that benefit. The interesting thing about what you mentioned there was, now we're hearing about all these vulnerabilities, right, in open source, that we need to contend with because the bad guys realize that I'm taking a lot of open source and they're saying, geez, that's a great way to get myself into applications. If I get myself into this one open source component, I'll get into thousands or more applications. So it's a fast path into the supply chain. And that's why it's so important that you understand where your vulnerabilities are in the software-- >> I think the visibility cuts two ways though. So when people say, it's insecure because it's visible. In fact, actually the visibility helps with security. The reality that I can go see the code, that there is a community working on finding and fixing vulnerabilities in that code. Whereas in code that is not open source it's a little bit more security by obscurity, which isn't really security. And there could well be vulnerabilities that a good hacker is going to find, but are not disclosed. So one of the other things we feel strongly about at Red Hat, frankly, is if there is a CVE that affects our code, we disclose that publicly, we have a public CVE database. And it's actually really important to us that we share that, we think we share way more information about issues in our code than most other users or consumers of open source and we work that through the broad community as well. And then also for our enterprise customers, if an issue needs to be fixed, we don't just fix it in the most recent version of the open source. We will backport that fix. And one of the challenges, if you're only addressing the most recent version, that may not be well tested, it might have other bugs, it might have other issues. When we backport a security vulnerability fix, we're able to do that to a stable version, give the customers the benefit of all the testing and use that's gone on while also fixing. >> Kirsten, can you talk about the announcements 'cause everybody's wondering, okay, now what do I do about this? What technology is there to help me? Obviously this framework, you got to follow the right processes, skill sets, all that, not to dismiss that, that's the most important part, but the announcements that you made at Red Hat Summit and how does the StackRox acquisition fit into those? >> Sure. So in particular, if we stick with DevSecOps a minute, but again, I'll do. Again for me, DevSecOps is the full life cycle and many people think of it as just that Shift Left piece. But for me, it's the whole thing. So StackRox ACS has had the ability to integrate into the CI/CD pipeline before we bought them. That continues. They don't just assess for vulnerabilities, but also for application misconfigurations, excess proof requests and helm charts, deployment YAML. So kind of the big, there are two sort of major things in the DevSecOps angle of the announcement or the supply chain angle of the announcement, which is the investment that we've been making in sigstore, signing, getting integrity of the components, the elements you're deploying is important. I have been asked for years about the ability to sign container images. The reality is that the signing technology and Red Hat signs everything we ship and always have, but the signing technology wasn't designed to be used in a CI/CD pipeline and sigstore is explicitly designed for that use case to make it easy for developers, as well as you can back it with full CO, you can back it with an OIDC based signing, keyless signing, throw away the key. Or if you want that enterprise CA, you can have that backing there too. >> And you can establish that as a protocol where you must. >> You can, right. So our pattern-- >> So that would've helped with SolarWinds. >> Absolutely. >> Because they were putting in malware and then taking it out, seeing what happened. My question was, could sigstore help? I always evaluate now everything and I'm not a security expert, but would this have helped with SolarWinds? A lot of times the answer is no. >> It's a combination. So a combination of sigstore integrated with Tekton Chains. So we ship Tekton, which is a Kubernetes supply chain pipeline. As OpenShift pipelines, we added chains to that. Chains allows you to attest every step in your pipeline. And you're doing that attestation by signing those steps so that you can validate that those steps have not changed. And in fact, the folks at SolarWinds are using Tekton Chains. They did a great talk in October at KubeCon North America on the changes they've made to their supply chain. So they're using both Tekton Chains and sigstore as part of their updated pipeline. Our pattern will allow our customers to deploy OpenShift, advanced cluster manager, advanced cluster security and Quay with security gates in place. And that include a pipeline built on Tekton with Tekton Chains there to sign those steps in the pipeline to enable signing of the code that's moving through that pipeline to store that signature in Quay and to validate the image signature upon deployment with advanced cluster security. >> So Jim, your perspective on this, Red Hat's, I mean, you care about security, security's everywhere, but you're not a security company. You follow security companies. There's like far too many of them. CISOs all say my number one challenge is lack of talent, but I have all these tools to deal with. You see new emerging companies that are doing pretty well. And then you see a company that's highly respected, like an Okta screw up the communications on a pretty benign hack. Actually, when you peel the onion on that, it's just this mess (chuckles) and it doesn't seem like it's going to get any simpler. Maybe the answer is companies like Red Hat kind of absorbing that and taking care of it. What do you see there? I mean, maybe it's great for business 'cause you've got so many companies. >> There's a lot of companies and there's certainly a lot of innovation out there and unique ways to make security easier, right. I mean, one of the keys here is to be able to make security easier for developers, right. One of the challenges with adopting DevSecOps is if DevSecOps creates a lot of friction in the process, it's hard to really... I can do it once, but I can't keep doing that and get the same kind of velocity. So I need to take the friction out of the process. And one of the challenges a lot of organizations have, and I've heard this from the development side, but I've also heard it from the InfoSec side, right. Because I take inquiry for people on InfoSec, and they're like, how do I get these developers to do what I want? And part of the challenge they have is like, I got these teams using these tools. I got those teams using those tools. And it's a similar challenge that we saw on DevOps where there's just too many, if you will, too many dang tools, right. So that is a challenge for organizations is, they're trying to kind of normalize the tools. Interestingly, we did a survey, I think around last August or something. And one of the questions was around, where do you want your security? Where do you want to get your DevSecOps security from, do you want to get it from individual vendors? Or do you want to get it from like, your platforms that you're using and deploying changes in Kubernetes. >> Great question. What did they say? >> The majority of them, they're hoping they can get it built into the platform. That's really what they want. And you see a lot of the security vendors are trying to build security platforms. Like we're not just assess tool, we're desk, we're this, whatever. And they're building platforms to kind of be that end-to-end security platform, trying to solve that problem, right, to make it easier to kind of consume the product overall, without a bunch of individual tools along the way. But certainly tool sprawl is definitely a challenge out there. Just one other point around the sigstore stuff which I love. Because that goes back to the supply chain and talking about digital providence, right. Understanding where things... How do I validate that what I gave you is what you thought it was, right. And what I like about it with Tekton Chains is because there's a couple things. Well, first of all, I don't want to just sign things after I built the binary. Well, I mean, I do want to sign it, but I want to just sign things once, right. Because all through the process, I think of it as a manufacturing plant, right. I'm making automobiles. If I check the quality of the automobile at one stage and I don't check it to the other, things have changed, right. How do I know that I did something wasn't compromised, right. So with sigstore kind of tied in with Tekton Chains, kind of gives me that view. And the other aspect I like it about is, this kind of transparency in the log, right-- >> The report component. >> Exactly. So I can see what was going on. So there is some this kind of like public scrutiny, like if something bad happened, you could go back and see what happened there and it wasn't as you were expected. >> As with most discussions on this topic, we could go for an hour because it's really important. And thank you guys for coming on and sharing your perspectives, the data. >> Our pleasure. >> And keep up the good work. Kirsten, it's on you. >> Thanks so much. >> The IDC survey said it, they want it in platforms. You're up. >> (laughs) That's right. >> All right. Good luck to both you. >> Thank you both so much. >> All right. And thank you for watching. We're back to wrap right after this short break. This is Dave Vellante for Paul Gill. You're watching theCUBE. (upbeat music)

(upbeat music) >> We're back. You're watching theCUBE's coverage of Red Hat Summit 2022 here in the Seaport in Boston. I'm Dave Vellante with my co-host, Paul Gillin. Justin Boitano is here. He's the Vice President of Enterprise and Edge Computing at NVIDIA. Maybe you've heard of him. And Tushar Katarki who's the Director of Product Management at Red Hat. Gentlemen, welcome to theCUBE, good to see you. >> Thank you. >> Great to be here, thanks >> Justin, you are a keynote this morning. You got interviewed and shared your thoughts on AI. You encourage people to got to think bigger on AI. I know it's kind of self-serving but why? Why should we think bigger? >> When you think of AI, I mean, it's a monumental change. It's going to affect every industry. And so when we think of AI, you step back, you're challenging companies to build intelligence and AI factories, and factories that can produce intelligence. And so it, you know, forces you to rethink how you build data centers, how you build applications. It's a very data centric process where you're bringing in, you know, an exponential amount of data. You have to label that data. You got to train a model. You got to test the model to make sure that it's accurate and delivers business value. Then you push it into production, it's going to generate more data, and you kind of work through that cycle over and over and over. So, you know, just as Red Hat talks about, you know, CI/CD of applications, we're talking about CI/CD of the AI model itself, right? So it becomes a continuous improvement of AI models in production which is a big, big business transformation. >> Yeah, Chris Wright was talking about basically take your typical application development, you know, pipeline, and life cycle, and apply that type of thinking to AI. I was saying those two worlds have to come together. Actually, you know, the application stack and the data stack including AI need to come together. What's the role of Red Hat? What's your sort of posture on AI? Where do you fit with OpenShift? >> Yeah, so we're really excited about AI. I mean, a lot of our customers obviously are looking to take that data and make meaning out of it using AI is definitely a big important tool. And OpenShift, and our approach to Open Hybrid Cloud really forms a successful platform to base all your AI journey on with the partners such as NVIDIA whom we are working very closely with. And so the idea really is as Justin was saying, you know, the end to end, when you think about life of a model, you've got data, you mine that data, you create models, you deploy it into production. That whole thing, what we call CI/CD, as he was saying DevOps, DevSecOps, and the hybrid cloud that Red Hat has been talking about, although with OpenShift as the center forms a good basis for that. >> So somebody said the other day, I'm going to ask you, is INVIDIA a hardware company or a software company? >> We are a company that people know for our hardware but, you know, predominantly now we're a software company. And that's what we were on stage talking about. I mean, ultimately, a lot of these customers know that they've got to embark on this journey to apply AI, to transform their business with it. It's such a big competitive advantage going into, you know, the next decade. And so the faster they get ahead of it, the more they're going to win, right? But some of them, they're just not really sure how to get going. And so a lot of this is we want to lower the barrier to entry. We built this program, we call it Launchpad to basically make it so they get instant access to the servers, the AI servers, with OpenShift, with the MLOps tooling, with example applications. And then we walk them through examples like how do you build a chatbot? How do you build a vision system for quality control? How do you build a price recommendation model? And they can do hands on labs and walk out of, you know, Launchpad with all the software they need, I'll say the blueprint for building their application. They've got a way to have the software and containers supported in production, and they know the blueprint for the infrastructure and operating that a scale with OpenShift. So more and more, you know, to come back to your question is we're focused on the software layers and making that easy to help, you know, either enterprises build their apps or work with our ecosystem and developers to buy, you know, solutions off the shelf. >> On the harbor side though, I mean, clearly NVIDIA has prospered on the backs of GPUs, as the engines of AI development. Is that how it's going to be for the foreseeable future? Will GPUs continue to be core to building and training AI models or do you see something more specific to AI workloads? >> Yeah, I mean, it's a good question. So I think for the next decade, well, plus, I mean not forever, we're going to always monetize hardware. It's a big, you know, market opportunity. I mean, Jensen talks about a $100 billion, you know, market opportunity for NVIDIA just on hardware. It's probably another a $100 billion opportunity on the software. So the reality is we're getting going on the software side, so it's still kind of early days, but that's, you know, a big area of growth for us in the future and we're making big investments in that area. On the hardware side, and in the data center, you know, the reality is since Moore's law has ended, acceleration is really the thing that's going to advance all data centers. So I think in the future, every server will have GPUs, every server will have DPUs, and we can talk a bit about what DPUs are. And so there's really kind of three primary processors that have to be there to form the foundation of the enterprise data center in the future. >> Did you bring up an interesting point about DPUs and MPUs, and sort of the variations of GPUs that are coming about? Do you see those different PU types continuing to proliferate? >> Oh, absolutely. I mean, we've done a bunch of work with Red Hat, and we've got a, I'll say a beta of OpenShift 4.10 that now supports DPUs as the, I'll call it the control plane like software defined networking offload in the data center. So it takes all the software defined networking off of CPUs. When everybody talks about, I'll call it software defined, you know, networking and core data centers, you can think of that as just a CPU tax up to this point. So what's nice is it's all moving over to DPU to, you know, offload and isolate it from the x86 cores. It increases security of data center. It improves the throughput of your data center. And so, yeah, DPUs, we see everybody copying that model. And, you know to give credit where credit is due, I think, you know, companies like AWS, you know, they bought Annapurna, they turned it into Nitro which is the foundation of their data centers. And everybody wants the, I'll call it democratized version of that to run their data centers. And so every financial institution and bank around the world sees the value of this technology, but running in their data centers. >> Hey, everybody needs a Nitro. I've written about it. It's Annapurna acquisition, 350 million. I mean, peanuts in the grand scheme of things. It's interesting, you said Moore's law is dead. You know, we have that conversation all the time. Pat Gelsinger promised that Moore's law is alive and well. But the interesting thing is when you look at the numbers, that's, you know, Moore's law, we all know it, doubling of the transistor densities every 18 to 24 months. Let's say that, that promise that he made is true. What I think the industry maybe doesn't appreciate, I'm sure you do, being in NVIDIA, when you combine what you were just saying, the CPU, the GPU, Paul, the MPU, accelerators, all the XPUs, you're talking about, I mean, look at Apple with the M1, I mean 6X in 15 months versus doubling every 18 to 24. The A15 is probably averaging over the last five years, a 110% performance improvement each year versus the historical Moore's law which is 40%. It's probably down to the low 30s now. So it's a completely different world that we're entering now. And the new applications are going to be developed on these capabilities. It's just not your general purpose market anymore. From an application development standpoint, what does that mean to the world? >> Yeah, I mean, yeah, it is a great point. I mean, from an application, I mean first of all, I mean, just talk about AI. I mean, they are all very compute intensive. They're data intensive. And I mean to move data focus so much in to compute and crunch those numbers. I mean, I'd say you need all the PUs that you mentioned in the world. And also there are other concerns that will augment that, right? Like we want to, you know, security is so important so we want to secure everything. Cryptography is going to take off to new levels, you know, that we are talking about, for example, in the case of DPUs, we are talking about, you know, can that be used to offload your encryption and firewalling, and so on and so forth. So I think there are a lot of opportunities even from an application point of view to take of this capacity. So I'd say we've never run out of the need for PUs if you will. >> So is OpenShift the layer that's going to simplify all that for the developer. >> That's right. You know, so one of the things that we worked with NVIDIA, and in fact was we developed this concept of an operator for GPUs, but you can use that pattern for any of the PUs. And so the idea really is that, how do you, yeah-- (all giggle) >> That's a new term. >> Yeah, it's a new term. (all giggle) >> XPUs. >> XPUs, yeah. And so that pattern becomes very easy for GPUs or any other such accelerators to be easily added as a capacity. And for the Kubernetes scaler to understand that there is that capacity so that an application which says that I want to run on a GPU then it becomes very easy for it to run on that GPU. And so that's the abstraction to your point about how we are making that happen. >> And to add to this. So the operator model, it's this, you know, open source model that does the orchestration. So Kubernetes will say, oh, there's a GPU in that node, let me run the operator, and it installs our entire run time. And our run time now, you know, it's got a MIG configuration utility. It's got the driver. It's got, you know, telemetry and metering of the actual GPU and the workload, you know, along with a bunch of other components, right? They get installed in that Kubernetes cluster. So instead of somebody trying to chase down all the little pieces and parts, it just happens automatically in seconds. We've extended the operator model to DPUs and networking cards as well, and we have all of those in the operator hub. So for somebody that's running OpenShift in their data centers, it's really simple to, you know, turn on Node Feature Discovery, you point to the operators. And when you see new accelerated nodes, the entire run time is automatically installed for you. So it really makes, you know, GPUs and our networking, our advanced networking capabilities really first class citizens in the data center. >> So you can kind of connect the dots and see how NVIDIA and the Red Hat partnership are sort of aiming at the enterprise. I mean, NVIDIA, obviously, they got the AI piece. I always thought maybe 25% of the compute cycles in the data center were wasted doing storage offloads or networking offload, security. I think Jensen says it's 30%, probably a better number than I have. But so now you're seeing a lot of new innovation in new hardware devices that are attacking that with alternative processors. And then my question is, what about the edge? Is that a blue field out at the edge? What does that look like to NVIDIA and where does OpenShift play? >> Yeah, so when we talk about the edge, we always going to start talking about like which edge are we talking about 'cause it's everything outside the core data center. I mean, some of the trends that we see with regard to the edges is, you know, when you get to the far edge, it's single nodes. You don't have the guards, gates, and guns protection of the data center. So you start having to worry about physical security of the hardware. So you can imagine there's really stringent requirements on protecting the intellectual property of the AI model itself. You spend millions of dollars to build it. If I push that out to an edge data center, how do I make sure that that's fully protected? And that's the area that we just announced a new processor that we call Hopper H100. It supports confidential computing so that you can basically ensure that model is always encrypted in system memory across the bus, of the PCI bus to the GPU, and it's run in a confidential way on the GPU. So you're protecting your data which is your model plus the data flowing through it, you know, in transit, wallet stored, and then in use. So that really adds to that edge security model. >> I wanted to ask you about the cloud, correct me if I'm wrong. But it seems to me that that AI workloads have been slower than most to make their way to the cloud. There are a lot of concerns about data transfer capacity and even cost. Do you see that? First of all, do you agree with that? And secondly, is that going to change in the short-term? >> Yeah, so I think there's different classes of problems. So we'll take, there's some companies where their data's generated in the cloud and we see a ton of, I'll say, adoption of AI by cloud service providers, right? Recommendation engines, translation engines, conversational AI services, that all the clouds are building. That's all, you know, our processors. There's also problems that enterprises have where now I'm trying to take some of these automation capabilities but I'm trying to create an intelligent factory where I want to, you know, merge kind of AI with the physical world. And that really has to run at the edge 'cause there's too much data being generated by cameras to bring that all the way back into the cloud. So, you know, I think we're seeing mass adoption in the cloud today. I think at the edge a lot of businesses are trying to understand how do I deploy that reliably and securely and scale it. So I do think, you know, there's different problems that are going to run in different places, and ultimately we want to help anybody apply AI where the business is generating the data. >> So obviously very memory intensive applications as well. We've seen you, NVIDIA, architecturally kind of move away from the traditional, you know, x86 approach, take better advantage of memories where obviously you have relationships with Arm. So you've got a very diverse set of capabilities. And then all these other components that come into use, to just be a kind of x86 centric world. And now it's all these other supporting components to support these new applications and it's... How should we think about the future? >> Yeah, I mean, it's very exciting for sure, right? Like, you know, the future, the data is out there at the edge, the data can be in the data center. And so we are trying to weave a hybrid cloud footprint that spans that. I mean, you heard Paul come here, talk about it. But, you know, we've talked about it for some time now. And so the paradigm really that is, that be it an application, and when I say application, it could be even an AI model as a service. It can think about that as an application. How does an application span that entire paradigm from the core to the edge and beyond is where the future is. And, of course, there's a lot of technical challenges, you know, for us to get there. And I think partnerships like this are going to help us and our customers to get there. So the world is very exciting. You know, I'm very bullish on how this will play out, right? >> Justin, we'll give you the last word, closing thoughts. >> Well, you know, I think a lot of this is like I said, it's how do we reduce the complexity for enterprises to get started which is why Launchpad is so fundamental. It gives, you know, access to the entire stack instantly with like hands on curated labs for both IT and data scientists. So they can, again, walk out with the blueprints they need to set this up and, you know, start on a successful AI journey. >> Just a position, is Launchpad more of a Sandbox, more of a school, or more of an actual development environment. >> Yeah, think of it as it's, again, it's really for trial, like hands on labs to help people learn all the foundational skills they need to like build an AI practice and get it into production. And again, it's like, you don't need to go champion to your executive team that you need access to expensive infrastructure and, you know, and bring in Red Hat to set up OpenShift. Everything's there for you so you can instantly get started. Do kind of a pilot project and then use that to explain to your executive team everything that you need to then go do to get this into production and drive business value for the company. >> All right, great stuff, guys. Thanks so much for coming to theCUBE. >> Yeah, thanks. >> Thank you for having us. >> All right, thank you for watching. Keep it right there, Dave Vellante and Paul Gillin. We'll be back right after this short break at the Red Hat Summit 2022. (upbeat music)

>> Welcome back to the Seaport in Boston and this is theCUBE's coverage of Red Hat Summit 2022. I'm Dave Vellante with my co-host Paul Gillin. Rob Belson is here as the Developer Relations Lead at Verizon. Robbie great to see you. Thanks for coming on theCUBE. >> Thanks for having me. >> So Verizon and developer relations. Talk about your role there. Really interesting. >> Absolutely. If you think about our mobile edge computing portfolio in Verizon 5G Edge, suddenly the developer is a more important persona than ever for actually adopting the cloud itself and adopting the mobile edge. So the question then quickly became how do we go after developers and how do we tell stories that ultimately resonate with them? And so my role has been spearheading our developer relations and experience efforts, which is all about meeting developers in the channels where they actually are, building content that resonates with them. Building out architectures that showcase how do you actually use the technology in the wild? And then ultimately creating automation assets that make their lives easier in deploying to the mobile edge. >> So, you know, telcos get a bad rap, when you're thinking it's amazing what you guys do. You put out all this capital infrastructure, big outlays. You know, we use our phones to drop a call. People like, "Ah, freaking Verizon." But it's amazing what we can actually do too. You think about the pandemic, the shift that the telcos had to go through to landlines to support home, never missed a beat. And yet at the same time you're providing all this infrastructure for people to come over the top, the cost forbid is going down, right? Your cost are going up and yet now we're doing this big 5G buildup. So I feel like there's a renaissance about to occur in edge computing that the telcos are going to lead new forms of monetization new value that you're going to be able to add, new services, new applications. The future's got to be exciting for you guys and it's going to be developer-led, isn't it? >> Absolutely. I mean it's been such an exciting time to be a part of our mobile edge computing portfolio. If you think back to late 2019 we were really asking the question with the advent of high speed 5G mobile networks, how can you drive more immersive experiences from the cloud in a cloud native way without compromising on the tools you know and love? And that's ultimately what caused us to really work with the likes of AWS and others to think about what does a mobile edge computing portfolio look like? So we started with 5G Edge with AWS Wavelength. So taking the compute and storage services you know and love in AWS and bringing it to the edge of our 4G and 5G networks. But then we start to think, well, wait a minute. Why stop at public networks? Let's think about private networks. How can we bring the cloud and private networks together? So you turn back to late 2021 we announced Verizon 5G Edge with AWS Outposts but we didn't even stop there. We said, "Well, interest's cool, but what about network APIs? We've been talking about the ability and the programmability of the 5G network but what does that actually look like to the developers? And one great example is our Edge Discovery Service. So you think about the proliferation of the edge 17 Wavelength Zones today in the US. Well, what edge is the right edge? You think about maybe the airline industry if the closest exit might be behind you absolutely applies to service discovery. So we've built an API that helps answer that seemingly basic question but is the fundamental building block for everything to workload orchestration, workload distribution. A basic network building block has become so important to some of these new sources of revenue streams, as we mentioned, but also the ability to disintermediate that purpose built hardware. You think about the future of autonomous mobile robots either ground and aerial robotics. Well, you want to make those devices as cheap as possible but you don't want to compromise on performance. And that mobile edge layer is going to become so critical for that connectivity, but also the compute itself. >> So I just kind of gave my little narrative up front about telco, but that purpose built hardware that you're talking about is exceedingly reliable. I mean, it's hardened, it's fossilized and so now as you just disaggregate that and go to a more programmable infrastructure, how are you able to and what gives you confidence that you're going to be able to maintain that reliability that I joke about? Oh, but it's so reliable. The network has amazing reliability. How are you able to maintain that? Is that just the pace of technology is now caught up, I wonder if you can explain that? >> I think it's really cool as I see reliability and sort of geo distribution as inextricably linked. So in a world where to get that best in class latency you needed to go to one place and one place only. Well, now you're creating some form of single source of failure whether it's the power, whether it's the compute itself, whether it's the networking, but with a more geo distributed footprint, particularly in the mobile edge more choices for where to deliver that immersive experience you're naturally driving an increase in reliability. But again, infra alone it's not going to do the job. You need the network APIs. So it's the convergence of the cloud and network and infra and the automation behind it that's been incredibly powerful. And as a great example, the work we've been doing in hybrid MEC the ability to converge within one single architecture, the private network, the public network, the AWS Outposts, the AWS Wavelength all in one has been such a fantastic journey and Red Hat has been a really important part in that journey. >> From the perspective of the developer when they're building a full cloud to edge application, where does Verizon pick up? Where do they start working primarily with you versus with their cloud provider? >> Absolutely. And I think you touched on a really important point. I think when you often think about the edge it's thought of as an either, or. Is it the edge? Is it the cloud? Is it both? It's an and I can't emphasize that enough. What we've seen from the customers greenfield or otherwise it's about extending an application or services that were never intended to live at the edge, to the edge itself, to deliver a more performant experience. And for certain control plane operations, metadata, backend operations analytics that can absolutely stay in the cloud itself. And so our role is to be a trusted partner in some of our enterprise customers' journeys. Of course, they can lean on the cloud provider in select cases, but we're an absolutely critical mode of support as you think about what are those architectures? How do you integrate the network APIs? And through our developer relations efforts, we've put a major role in helping to shape what those patterns really look like in the wild. >> When they're developing for 5G I mean, the availability of 5G of particularly you know, the high bandwidth 5G is pretty spotty right now. Mostly urban areas. How should they be thinking in the future developing an application roll out two years from now about where 5G will be at that point? >> Absolutely. I think one of the most important things in this case is the interoperability of our edge computing portfolio with both 4G and 5G. Whenever somebody asks me about the performance of 5G they ask how fast? Or for edge computing. It's always about benchmark. It's not an absolute value. It's always about benchmarking the performance to that next best alternative. What were you going to get if you didn't have edge computing in your back pocket? And so along that line of thought having the option to go either through 4G or 5G, having a mobile edge computing portfolio that works for both modes of connectivity even CAN-AM IoT is incredibly powerful. >> So it sounds like 4G is going to be with us for quite a while still? >> And I think it's an important part of the architecture. >> Yeah. >> Robert, tell us about the developer that's building these applications. Where does that individual come from? What's their persona? >> Oh, boy I think there's a number of different personas and flavors. I've seen everything from the startup in the back of a garage working hard to try to figure out what could I do for a next generation media and entertainment experience but also large enterprises. And I think a great area where we saw this was our 5G Edge Computing Challenge that we hosted last year. Believe it or not 100 submissions from over 22 countries, all building on Verizon 5G Edge. It was so exciting to see because so many different use cases across public safety, healthcare, media and entertainment. And what we found was that education is so important. A lot of developers have great ideas but if you don't understand the fundamentals of the infrastructure you get bogged down in networking and setting up your environment. And that's why we think that developer education is so important. We want to make it easy and in fact, the 5G Edge portfolio was designed in such a way that we'll abstract the complexities of the network away so you can focus on building your application and that's such a central theme and focus for how we approach the development. >> So what kind of services are you exposing via APIs? >> Absolutely, so first and foremost, as you think about 5G Edge with say AWS Wavelength, the infra there are APIs that are exposed by AWS to launch your infra, to patch your infrastructure, to automate your infrastructure. Specifically that Verizon has developed that's our network APIs. And a great example is our Edge Discovery Service. So think of this as like a service registry you've launched an application in all 17 edge zones. You would take that information, you would send it via API to the Edge Discovery Service so that for any mobile client say, you wake up one morning in Boston, you can ask the API or query, "Hey, what's the closest edge zone?" DNS isn't going to be able to figure it out. You need knowledge of the actual topology of the mobile network itself. So the API will answer. Let's say you take a little road trip 1,000 miles south to say Miami, Florida you ask that question again. It could change. So that's the workflow and how you would use the network API today. >> How'd you get into this? You're an engineer it's obvious how'd you stumble into this role? >> Well, yeah, I have a background in networks and distributed systems so I always knew I wanted to stay in the cloud somewhere. And there was a really unique opportunity at Verizon as the portfolio was being developed to really think about what this developer community looked like. And we built this all from scratch. If you look at say our Verizon 5G Edge Blog we launched it just along the timing of the actual GA of Wavelength. You look at our developer newsletter also around the time of the launch of Wavelength. So we've done a lot in such a short period and it's all been sort of organic, interacting with developers, working backwards from the customer. And so it's been a fairly new, but incredibly exciting journey. >> How will your data, architecture, data flow what will that look like in the future? How will that be different than it is sort of historically? >> When I think about customer workloads real time data architecture is an incredibly difficult thing to do. When you overlay the edge, admittedly, it gets more complicated. More places that produce the data, more places that consume data. How do you reconcile all of these environments? Maintain consistency? This is absolutely something we've been working on with the ecosystem at large. We're not going to solve this alone. We've looked at architecture patterns that we think are successful. And some of the things that we found that we believe are pretty cool this idea of taking that embedded mobile database, virtualizing it to the edge, even making it multi-tenant. And then you're producing data to one single source and simplifying how you organize and share data because all of the data being produced to that one location will be relevant to that topology. So Boston, as an example, Boston data being produced to that edge zone will only service Boston clients. So having a geo distributed footprint really does help data architectures, but at the core of all of this database, architectures, you need a compute environment that actually makes sense. That's performant, that's reliable. That's easy to use that you understand how to manage and that the edge doesn't make it any more difficult to manage. >> So are you building that? >> That's exactly what we're doing. So here at Red Hat Summit we've had the unique opportunity to continue to collaborate with our partners at Red Hat to think about how you actually use OpenShift in the context of hybrid MEC. So what have done is we've used OpenShift as is to extend what already exists to some of these new edge zones without adding in an additional layer of complexity that was unmanageable. >> So you use OpenShift so you don't have to cobble this together on your own as a full development environment and that's the role really that OpenShift plays here? >> That's exactly right. And we presented pieces of this at our re:Invent this past year and what we basically did is we said the edge needs to be inextricably linked with the cloud. And you want to be able to manage it from some seamless central pane of glass and using that OpenShift console is a great way. So what we did is we wanted to show a really geo-distributed footprint in action. We started with a Wavelength zone in Boston, the region in Northern Virginia, an outpost in the Texas area. We cobbled it all together in one cluster. So you had a whole compute mesh separated by thousands of miles all within a single cluster, single pane of glass. We take that and are starting to expand on the complexity of these architectures to overlay the network APIs we mentioned, to overlay multi-region support. So when we say you can use all 17 zones at once you actually can. >> So you've been talking about Wavelength and Outposts which are AWS products, but Microsoft and Google both have their distributed architectures as well. Where do you stand with those? Will you support those? Are you working with them? >> That's a great question. We have made announcements with Microsoft and Google but today I focus a lot on the work we do with AWS Wavelength and Outposts and continuing to work backwards from the customer and ultimately meet their needs. >> Yeah I mean, you got to start with an environment that the developers know that obviously a great developer community, you know, you see it at re:Invent. What was the reaction at re:Invent when you showed this from a developer community? >> Absolutely. Developers are excited and I think the best part is we're not the only ones talking about Wavelength not even AWS are the only ones talking about Wavelength. And to me from a developer ecosystem perspective that's when you know it's working. When you're not the one telling the best stories when others are evangelizing the power of your technology on your behalf that's when the ecosystem's starting to pick up. >> Speaking of making a bet on Outposts you know, it's somewhat limited today. I'll say it it's limited today in terms of we think it supports RDS and there's a few storage players. Is it your expectation that Outposts is going to be this essentially the cloud environment on your premises is that? >> That's a great question. I see it more as we want to expand customer choice more than ever and ultimately let the developers and architects decide. That's why I'm so bullish on this idea of hybrid MEC. Let's provide all of the options the most complicated geo distributed hybrid deployment you can imagine and automate it, make it easy. That way if you want to take away components of this architecture all you're doing is simplifying something that's already automated and fairly simple to begin with. So start with the largest problem to solve and then provide customers choice for what exactly meets their requirements their SLAs, their footprint, their network and work backwards from the customer. >> Exciting times ahead. Rob, thanks so much for coming on theCUBE. It's great to have you. >> Appreciate it, thanks for your time. >> Good luck. All right, thank you for watching. Keep it right there. This is Dave Vellante for Paul Gillin. We're live at Red Hat Summit 2022 from the Seaport in Boston. We'll be right back.

(gentle music) >> We're back at the Seaport in Boston. I'm Dave Vellante with my co-host, Paul Gillin. Tracie Zenti is here. She's the Director of Global Partner Management at Microsoft, and Tom Anderson is the Vice President of Ansible at Red Hat. Guys, welcome to theCube. >> Hi, thank you. >> Yep. >> Ansible on Azure, we're going to talk about that. Why do I need Ansible? Why do I need that kind of automation in Azure? What's the problem you're solving there? >> Yeah, so automation itself is connecting customers' infrastructure to their end resources, so whether that infrastructure's in the cloud, whether it's in the data center, or whether it's at the edge. Ansible is the common automation platform that allows customers to reuse automation across all of those platforms. >> And so, Tracie, I mean, Microsoft does everything. Why do you need Red Hat to do Ansible? >> We want that automation, right? We want our customers to have that ease of use so they can be innovative and bring their workloads to Azure. So that's exactly why we want Ansible. >> Yeah, so kind of loaded questions here, right, as we were sort of talking offline. The nature of partnerships is changing. It's about co-creating, adding value together, getting those effects of momentum, but maybe talk about how the relationship started and how it's evolving and I'd love to have your perspective on the evolving nature of ecosystems. >> Yeah, I think the partnership with Red Hat has been strong for a number of years. I think my predecessor was in the role for five years. There was a person in there for a couple years before that. So I think seven or eight years, we've been working together and co-engineering. Red Hat enterprised Linux. It's co-engineered. Ansible was co-engineered. We work together, right? So we want it to run perfectly on our platform. We want it to be a good customer experience. I think the evolution that we're seeing is in how customers buy, right? They want us to be one company, right? They want it to be easy. They want be able to buy their software where they run it on the cloud. They don't want to have to call Red Hat to buy and then call us to buy and then deploy. And we can do all that now with Ansible's the first one we're doing this together and we'll grow that on our marketplace so that it's easy to buy, easy to deploy, easy to keep track of. >> This is not just Ansible in the marketplace. This is actually a fully managed service. >> That's right. >> What is the value you've added on top of that? >> So it runs in the customer account, but it acts kind of like SaaS. So Red Hat gets to manage it, right? And it's in their own tenant. So they get in the customer's own tenant, right? So with a service principle, Red Hat's able to do that management. Tom, do you want to add anything to that? >> Yeah, the customers don't have to worry about managing Ansible. They just worry about using Ansible to automate their infrastructure. So it's a kind of a win-win situation for us and for our customers. We manage the infrastructure for them and the customer's resources themselves and they get to just focus on automating their business. >> Now, if they want to do cross-cloud automation or automation to their hybrid cloud, will you support that as well? >> 100%. >> Absolutely. >> Yeah. >> We're totally fine with that, right? I mean, it's unrealistic to think customers run everything in one place. That isn't enterprise. That's not reality. So yeah, I'm fine with that. >> Well, that's not every cloud provider. >> No (laughing) that's true. >> You guys over here, at Amazon, you can't even say multicloud or you'll get thrown off the stage. >> Of course we'd love it to all run on Azure, but we want our customers to be happy and have choice, yeah. >> You guys have all, I mean, you've been around a long time. So you had a huge on-prem state, brought that to the cloud, and Azure Stack, I mean, it's been around forever and it's evolved. So you've always believed in, whatever you call it, Hybrid IT, and of course, you guys, that's your call of mission. >> Yeah, exactly. >> So how do you each see hybrid? Where's the points of agreement? It sounds like there's more overlap than gaps, but maybe you could talk about your perspective. >> Yeah, I don't think there are any points of disagreement. I think for us, it's meeting our customers where their center of gravity is, where they see their center of management gravity. If it's on Azure, great. If it's on their data center, that's okay, too. So they can manage to or from. So if Azure is their center of gravity, they can use automation, Ansible automation, to manage all the things on Azure, things on other cloud providers, things in their data center, all the way out to their edge. So they have the choice of what makes the most sense to them. >> And Azure Arc is obviously, that's how Azure Stack is evolving, right? >> Yeah, and we have Azure Arc integration with Ansible. >> Yeah. >> So yeah, absolutely. And I mean, we also have Rell on our marketplace, right? So you can buy the basement and you could buy the roof and everything in between. So we're growing the estate on marketplace as well to all the other products that we have in common. So absolutely. >> How much of an opportunity, just go if we go inside? Give us a little peak inside Microsoft. How much of an opportunity does Microsoft think about multi-cloud specifically? I'm not crazy about the term multicloud, 'cause to me, multicloud, runs an Azure, runs an AWS, runs on Google, maybe runs somewhere else. But multicloud meaning that common experience, your version of hybrid, if you will. How serious is Microsoft about that as a business opportunity? A lot of people would say, well, Microsoft really doesn't want. They want everything in their cloud. But I'd love to hear from you if that is good. >> Well, we have Azure Red Hat OpenShift, which is a Microsoft branded version of OpenShift. We have Ansible now on our marketplace. We also, of course, we have AKS. So I mean, container strategy runs anywhere. But we also obviously have services that enhance all these things. So I think, our marketplace is a third party marketplace. It is designed to let customers buy and run easily on Azure and we'd want to make that experience good. So I don't know that it's... I can't speak to our strategy on multicloud, but what I can speak to is when businesses need to do innovation, we want it to be easy to do that, right? We want it to be easy to buy, defined, buy, deploy, manage, and that's what we're trying to accomplish. >> Fair to say, you're not trying to stop it. >> No, yeah, yeah. >> Whether or not it evolves into something that you heavily lean into or see. >> When we were talking before the cameras turned on, you said that you think marketplaces are the future. Why do you say that? And how will marketplaces be differentiated from each other in the future? >> Well, our marketplace is really, first of all, I think, as you said off camera, they're now. You can buy now, right? There's nothing that stops you. But to me, it's an extension of consumerization of IT. I've been in IT and manageability for about 23 years and full automation is what we and IT used to always talk about, that single pane of glass. How do you keep track of everything? How do you make it easy? How do you support? And IT is always eeking out that last little bit of funding to do innovation, right? So what we can do with consumerization of IT is make it easier to innovate. Make it cheaper to innovate, right? So I think marketplaces do that, right? They've got gold images you can deploy. You're also able to deploy custom images. So I think the future is as particularly with ours, like we support, I don't remember the exact number, but over a hundred countries of tax calculation. We've got like 17 currencies. So as we progress and customers can run from anywhere in the world and buy from anywhere in the world and make it simple to do those things that used to take maybe two months to spin up services for innovation and Ansible helps with that, that's going to help enterprises innovate faster. And I think that's what marketplaces are really going to bring to the forefront is that innovation. >> Tom, why did Ansible, I'm going to say one, I mean, you're never done. But it was unclear a few years ago, which automation platform was going to win in the marketplace and clearly, Ansible has taken a leading position. Why? What were the factors that led to that? >> Honestly, it was the strength of the community, right? And Red Hat leaning into that community to support that community. When you look out at the upstream community for Ansible and the number of participants, active participants that are contributing to the community just increases its value to everybody. So the number of integrations, the number of things that you can automate with Ansible is in the thousands and thousands, and that's not because a group of Red Hat engineers wrote it. That's because our community partners, like Microsoft wrote the user integrations for Ansible. F5 does theirs. Customers take those and expand on them. So the number of use cases that we can address through the community and through our partners is immense. >> But that doesn't just happen. I mean, what have you done to cultivate that community? >> Well, it's in Red Hat's DNA, right? To be the catalyst in a community, to bring partners and users together, to share their knowledge and their expertise and their skills, and to make the code open. So anybody can go grab Ansible from upstream and start doing stuff with it, if they want. If they want to mature on it and management for it and support all the other things that Red Hat provides, then they come to us for a subscription. So it's really been about sort of catalyzing and supporting that community, and Red Hat is a good steward of these upstream communities. >> Is Azure putting Ansible to use actually within your own platform as opposed to being a managed service? Are you adopting Ansible for automation of the Azure Platform? >> I'll let you answer that. >> So two years ago, Microsoft presented at AnsibleFest, our fall conference, Budd Warrack, I'm butchering his last name, but he came on and told how the networking team at Microsoft supports about 35,000 access points across hundreds of buildings, all the Microsoft campuses using Ansible to do that. Fantastic story if you want to go on YouTube and look up that use case. So Microsoft is an avid user of the Ansible technology in their environment. >> Azure is kind of this really, I mean, incredible strategic platform for Microsoft. I wonder if you could talk about Azure as a honeypot for partners. I mean, it seems, I mean, the momentum is unbelievable. I mean, I pay attention to their earnings calls every quarter of Azure growth, even though I don't know what the exact number is, 'cause they won't give it to me but they give me the growth rates and it's actually accelerating. >> No lie. (Tracie laughing) >> I've got my number. It's in the tens of billions. I mean, I'm north of 35 billion, but growing at the high 30%. I mean, it's remarkable. So talk about the importance of that to the ecosystem as a honey pot. >> Paul Satia said it right. Many times partners are essential to our strategy. But if you think about it, software solves problems. We have software that solves problems. They have software that solves problems, right? So when IT and customers are thinking of solving a problem, they're thinking software, right? And we want that software to run on Azure. So partners have to be essential to our strategy. Absolutely. It's again, we're one team to the customer. They want to see that as working together seamlessly. They don't want it to be hardware Azure plus software. So that's absolutely critical to our success. >> And if I could add for us, the partners are super important. So some of our launch partners are like F5 and CyberArk who have certified Ansible content for Ansible on Azure. We have service provider partners like Accenture and Kindra that are launching with us and providing our joint customers with help to get up to speed. So it really is a partner play. >> Absolutely. >> Where are you guys taking this? Where do you want to see it go? What are some of the things that observers should pay attention to as marketers of success and evolution? >> Well, certainly for us, it's obviously customer adoption, but it is providing them with patterns. So out of the box patterns that makes it easy for them to get up and running and solve the use cases and problems that they run into most frequently. Problems ain't the right word. Challenges or opportunities on Azure to be able to automate the things. So we're really leaning into the different use cases, whether it's edge, whether it's cloud, whether it's cloud to edge, all of those things. We want to provide users with out of the box Ansible content that allows 'em to just get up and automating super fast, and doing that on Azure makes it way easier for us because we don't have to focus on the install and the setting up and configuring it. It's all just part of the experience >> And Tracie, for Microsoft, it's world domination with a smile. (all laughing) >> Of course. No, of course not. No, I think it's to continue to grow the co-engineering we do across all of the Red Hat products. I can't even tell you the number of things we work on together, but to look forward strategically at what opportunities we have across our products and theirs to integrate like Arc and Ansible, and then making it all easy to buy, making it available so that customers have choice and they can buy how they want to and simplify. So we're just going to continue to do that and we're at that infancy right now and as we grow, it'll just get easier and easier with more and more products. >> Well, bringing the edge into the equation is going to be really interesting. Microsoft with its gaming, vector is amazing, and recent, awesome acquisitions. All the gamers are excited about that and that's a huge edge play. >> You'll have to bring my son on for that interview. >> Yeah. >> My son will interview. >> He knows more than all of us, I'm sure. What about Ansible? What's ahead for Ansible? >> Edge, so part of the Red Hat play at the Edge. We've getting a lot of customer pull for both industrial Edge use cases in the energy sector. We've had a joint customer with Azure that has a combined Edge platform. Certainly, the cloud stuff that we're announcing today is a huge growth area. And then just general enterprise automation. There's lots of room to run there for Ansible. >> And lots of industries, right? >> Yeah. >> Telco, manufacturing. >> Retail. >> Retail. >> Yeah. >> Yeah. There's so many places to go, yeah, that need the help. >> The market's just, how you going to count it anymore? It's just enormous. >> Yeah. >> It's the entire GDP the world. But guys, thanks for coming to theCUBE. >> Yeah. >> Great story. Congratulations on the partnership and the announcements and look forward to speaking with you in the future. >> Yeah, thanks for having us. >> Thanks for having us. >> You're very welcome. And keep it right there. This is Dave Vellante for Paul Gillin. This is theCUBE's coverage of Red Hat Summit 2022. We'll be right back at Seaport in Boston. (gentle music)