>>Keon Cloud Native Con kicks off in Detroit on October 24th, and we're pleased to have Stewart Miniman, who's the director of Market Insights, hi, at, for hybrid platforms at Red Hat back in the studio to help us understand the key trends to look for at the events. Do welcome back, like old, old, old >>Home. Thank you, David. It's great to, great to see you and always love doing these previews, even though Dave, come on. How many years have I told you Cloud native con, It's a hoodie crowd. They're gonna totally call you out for where in a tie and things like that. I, I know you want to be an ESPN sportscaster, but you know, I I, I, I still don't think even after, you know, this show's been around for so many years that there's gonna be too many ties into Troy. I >>Know I left the hoodie in my off, I'm sorry folks, but hey, we'll just have to go for it. Okay. Containers generally, and Kubernetes specifically continue to show very strong spending momentum in the ETR survey data. So let's bring up this slide that shows the ETR sectors, all the sectors in the tax taxonomy with net score or spending velocity in the vertical axis and pervasiveness on the horizontal axis. Now, that red dotted line that you see, that marks the elevated 40% mark, anything above that is considered highly elevated in terms of momentum. Now, for years, the big four areas of momentum that shine above all the rest have been cloud containers, rpa, and ML slash ai for the first time in 10 quarters, ML and AI and RPA have dropped below the 40% line, leaving only cloud and containers in rarefied air. Now, Stu, I'm sure this data doesn't surprise you, but what do you make of this? >>Yeah, well, well, Dave, I, I did an interview with at Deepak who owns all the container and open source activity at Amazon earlier this year, and his comment was, the default deployment mechanism in Amazon is containers. So when I look at your data and I see containers and cloud going in sync, yeah, that, that's, that's how we see things. We're helping lots of customers in their overall adoption. And this cloud native ecosystem is still, you know, we're still in that Cambridge explosion of new projects, new opportunities, AI's a great workload for these type type of technologies. So it's really becoming pervasive in the marketplace. >>And, and I feel like the cloud and containers go hand in hand, so it's not surprising to see those two above >>The 40%. You know, there, there's nothing to say that, Look, can I run my containers in my data center and not do the public cloud? Sure. But in the public cloud, the default is the container. And one of the hot discussions we've been having in this ecosystem for a number of years is edge computing. And of course, you know, I want something that that's small and lightweight and can do things really fast. A lot of times it's an AI workload out there, and containers is a great fit at the edge too. So wherever it goes, containers is a good fit, which has been keeping my group at Red Hat pretty busy. >>So let's talk about some of those high level stats that we put together and preview for the event. So it's really around the adoption of open source software and Kubernetes. Here's, you know, a few fun facts. So according to the state of enterprise open source report, which was published by Red Hat, although it was based on a blind survey, nobody knew that that Red Hat was, you know, initiating it. 80% of IT execs expect to increase their use of enterprise open source software. Now, the CNCF community has currently more than 120,000 developers. That's insane when you think about that developer resource. 73% of organizations in the most recent CNCF annual survey are using Kubernetes. Now, despite the momentum, according to that same Red Hat survey, adoption barriers remain for some organizations. Stu, I'd love you to talk about this specifically around skill sets, and then we've highlighted some of the other trends that we expect to see at the event around Stu. I'd love to, again, your, get your thoughts on the preview. You've done a number of these events, automation, security, governance, governance at scale, edge deployments, which you just mentioned among others. Now Kubernetes is eight years old, and I always hear people talking about there's something coming beyond Kubernetes, but it looks like we're just getting started. Yeah, >>Dave, It, it is still relatively early days. The CMC F survey, I think said, you know, 96% of companies when they, when CMC F surveyed them last year, were either deploying Kubernetes or had plans to deploy it. But when I talked to enterprises, nobody has said like, Hey, we've got every group on board and all of our applications are on. It is a multi-year journey for most companies and plenty of them. If you, you look at the general adoption of technology, we're still working through kind of that early majority. We, you know, passed the, the chasm a couple of years ago. But to a point, you and I we're talking about this ecosystem, there are plenty of people in this ecosystem that could care less about containers and Kubernetes. Lots of conversations at this show won't even talk about Kubernetes. You've got, you know, big security group that's in there. >>You've got, you know, certain workloads like we talked about, you know, AI and ml and that are in there. And automation absolutely is playing a, a good role in what's going on here. So in some ways, Kubernetes kind of takes a, a backseat because it is table stakes at this point. So lots of people involved in it, lots of activities still going on. I mean, we're still at a cadence of three times a year now. We slowed it down from four times a year as an industry, but there's, there's still lots of innovation happening, lots of adoption, and oh my gosh, Dave, I mean, there's just no shortage of new projects and new people getting involved. And what's phenomenal about it is there's, you know, end user practitioners that aren't just contributing. But many of the projects were spawned out of work by the likes of Intuit and Spotify and, and many others that created some of the projects that sit alongside or above the, the, you know, the container orchestration itself. >>So before we talked about some of that, it's, it's kind of interesting. It's like Kubernetes is the big dog, right? And it's, it's kind of maturing after, you know, eight years, but it's still important. I wanna share another data point that underscores the traction that containers generally are getting in Kubernetes specifically have, So this is data from the latest ETR survey and shows the spending breakdown for Kubernetes in the ETR data set for it's cut for respondents with 50 or more citations in, in by the IT practitioners that lime green is new adoptions, the forest green is spending 6% or more relative to last year. The gray is flat spending year on year, and those little pink bars, that's 6% or down spending, and the bright red is retirements. So they're leaving the platform. And the blue dots are net score, which is derived by subtracting the reds from the greens. And the yellow dots are pervasiveness in the survey relative to the sector. So the big takeaway here is that there is virtually no red, essentially zero churn across all sectors, large companies, public companies, private firms, telcos, finance, insurance, et cetera. So again, sometimes I hear this things beyond Kubernetes, you've mentioned several, but it feels like Kubernetes is still a driving force, but a lot of other projects around Kubernetes, which we're gonna hear about at the show. >>Yeah. So, so, so Dave, right? First of all, there was for a number of years, like, oh wait, you know, don't waste your time on, on containers because serverless is gonna rule the world. Well, serverless is now a little bit of a broader term. Can I do a serverless viewpoint for my developers that they don't need to think about the infrastructure but still have containers underneath it? Absolutely. So our friends at Amazon have a solution called Fargate, their proprietary offering to kind of hide that piece of it. And in the open source world, there's a project called Can Native, I think it's the second or third can Native Con's gonna happen at the cncf. And even if you use this, I can still call things over on Lambda and use some of those functions. So we know Dave, it is additive and nothing ever dominates the entire world and nothing ever dies. >>So we have, we have a long runway of activities still to go on in containers and Kubernetes. We're always looking for what that next thing is. And what's great about this ecosystem is most of it tends to be additive and plug into the pieces there, there's certain tools that, you know, span beyond what can happen in the container world and aren't limited to it. And there's others that are specific for it. And to talk about the industries, Dave, you know, I love, we we have, we have a community event that we run that's gonna happen at Cubans called OpenShift Commons. And when you look at like, who's speaking there? Oh, we've got, you know, for Lockheed Martin, University of Michigan and I g Bank all speaking there. So you look and it's like, okay, cool, I've got automotive, I've got, you know, public sector, I've got, you know, university education and I've got finance. So all of you know, there is not an industry that is not touched by this. And the general wave of software adoption is the reason why, you know, not just adoption, but the creation of new software is one of the differentiators for companies. And that is what, that's the reason why I do containers, isn't because it's some cool technology and Kubernetes is great to put on my resume, but that it can actually accelerate my developers and help me create technology that makes me respond to my business and my ultimate end users. Well, >>And you know, as you know, we've been talking about the Supercloud a lot and the Kubernetes is clearly enabler to, to Supercloud, but I wanted to go back, you and John Furrier have done so many of, you know, the, the cube cons, but but go back to Docker con before Kubernetes was even a thing. And so you sort of saw this, you know, grow. I think there's what, how many projects are in CNCF now? I mean, hundreds. Hundreds, okay. And so you're, Will we hear things in Detroit, things like, you know, new projects like, you know, Argo and capabilities around SI store and things like that? Well, you're gonna hear a lot about that. Or is it just too much to cover? >>So I, I mean the, the good news, Dave, is that the CNCF really is, is a good steward for this community and new things got in get in. So there's so much going on with the existing projects that some of the new ones sometimes have a little bit of a harder time making a little bit of buzz. One of the more interesting ones is a project that's been around for a while that I think back to the first couple of Cube Cuban that John and I did service Mesh and Istio, which was created by Google, but lived under basically a, I guess you would say a Google dominated governance for a number of years is now finally under the CNCF Foundation. So I talked to a number of companies over the years and definitely many of the contributors over the years that didn't love that it was a Google Run thing, and now it is finally part. >>So just like Kubernetes is, we have SEO and also can Native that I mentioned before also came outta Google and those are all in the cncf. So will there be new projects? Yes. The CNCF is sometimes they, they do matchmaking. So in some of the observability space, there were a couple of projects that they said, Hey, maybe you can go merge down the road. And they ended up doing that. So there's still you, you look at all these projects and if I was an end user saying, Oh my God, there is so much change and so many projects, you know, I can't spend the time in the effort to learn about all of these. And that's one of the challenges and something obviously at Red Hat, we spend a lot of time figuring out, you know, not to make winners, but which are the things that customers need, Where can we help make them run in production for our, our customers and, and help bring some stability and a little bit of security for the overall ecosystem. >>Well, speaking of security, security and, and skill sets, we've talked about those two things and they sort of go hand in hand when I go to security events. I mean, we're at reinforced last summer, we were just recently at the CrowdStrike event. A lot of the discussion is sort of best practice because it's so complicated. And, and, and will you, I presume you're gonna hear a lot of that here because security securing containers now, you know, the whole shift left thing and shield right is, is a complicated matter, especially when you saw with the earlier data from the Red Hat survey, the the gaps are around skill sets. People don't have the skill. So should we expect to hear a lot about that, A lot of sort of how to, how to take advantage of some of these new capabilities? >>Yeah, Dave, absolutely. So, you know, one of the conversations going on in the community right now is, you know, has DevOps maybe played out as we expect to see it? There's a newer term called platform engineering, and how much do I need to do there? Something that I, I know your, your team's written a lot about Dave, is how much do you need to know versus what can you shift to just a platform or a service that I can consume? I've talked a number of times with you since I've been at Red Hat about the cloud services that we offer. So you want to use our offering in the public cloud. Our first recommendation is, hey, we've got cloud services, how much Kubernetes do you really want to learn versus you want to do what you can build on top of it, modernize the pieces and have less running the plumbing and electric and more, you know, taking advantage of the, the technologies there. So that's a big thing we've seen, you know, we've got a big SRE team that can manage that for use so that you have to spend less time worrying about what really is un differentiated heavy lifting and spend more time on what's important to your business and your >>Customers. So, and that's, and that's through a managed service. >>Yeah, absolutely. >>That whole space is just taken off. All right, Stu I'll give you the final word. You know, what are you excited about for, for, for this upcoming event and Detroit? Interesting choice of venue? Yeah, >>Look, first of off, easy flight. I've, I've never been to Detroit, so I'm, I'm willing to give it a shot and hopefully, you know, that awesome airport. There's some, some, some good things there to learn. The show itself is really a choose your own adventure because there's so much going on. The main show of QAN and cloud Native Con is Wednesday through Friday, but a lot of a really interesting stuff happens on Monday and Tuesday. So we talked about things like OpenShift Commons in the security space. There's cloud Native Security Day, which is actually two days and a SIG store event. There, there's a get up show, there's, you know, k native day. There's so many things that if you want to go deep on a topic, you can go spend like a workshop in some of those you can get hands on to. And then at the show itself, there's so much, and again, you can learn from your peers. >>So it was good to see we had, during the pandemic, it tilted a little bit more vendor heavy because I think most practitioners were pretty busy focused on what they could work on and less, okay, hey, I'm gonna put together a presentation and maybe I'm restricted at going to a show. Yeah, not, we definitely saw that last year when I went to LA I was disappointed how few customer sessions there were. It, it's back when I go look through the schedule now there's way more end users sharing their stories and it, it's phenomenal to see that. And the hallway track, Dave, I didn't go to Valencia, but I hear it was really hopping felt way more like it was pre pandemic. And while there's a few people that probably won't come because Detroit, we think there's, what we've heard and what I've heard from the CNCF team is they are expecting a sizable group up there. I know a lot of the hotels right near the, where it's being held are all sold out. So it should be, should be a lot of fun. Good thing I'm speaking on an edge panel. First time I get to be a speaker at the show, Dave, it's kind of interesting to be a little bit of a different role at the show. >>So yeah, Detroit's super convenient, as I said. Awesome. Airports too. Good luck at the show. So it's a full week. The cube will be there for three days, Tuesday, Wednesday, Thursday. Thanks for coming. >>Wednesday, Thursday, Friday, sorry, >>Wednesday, Thursday, Friday is the cube, right? So thank you for that. >>And, and no ties from the host, >>No ties, only hoodies. All right Stu, thanks. Appreciate you coming in. Awesome. And thank you for watching this preview of CubeCon plus cloud Native Con with at Stu, which again starts the 24th of October, three days of broadcasting. Go to the cube.net and you can see all the action. We'll see you there.

>>Okay. Today we welcome Evan Kaplan, CEO of Influx Data, the company behind Influx DB Welcome, Evan. Thanks for coming on. >>Hey, John. Thanks for having me. >>Great segment here on the influx. DB Story. What is the story? Take us through the history. Why Time series? What's the story? >>So the history of history is actually actually pretty interesting. Paul Dicks, my partner in this and our founder, um, super passionate about developers and developer experience. And, um, he had worked on Wall Street building a number of times series kind of platform trading platforms for trading stocks. And from his point of view, it was always what he would call a yak shave, which means you have to do a tonne of work just to start doing work. Which means you have to write a bunch of extrinsic routines. You had to write a bunch of application handling on existing relational databases in order to come up with something that was optimised for a trading platform or a time series platform. And he sort of he just developed This real clear point of view is this is not how developers should work. And so in 2013, he went through y Combinator and he built something for he made his first commit to open source influx TB at the end of 2013. And basically, you know, from my point of view, you invented modern time series, which is you start with a purpose built time series platform to do these kind of work clothes, and you get all the benefits of having something right out of the box or developer can be totally productive right away. >>And how many people in the company What's the history of employees and stuff? Yeah, >>I think we're you know, I always forget the number, but it's something like 230 or 240 people now. Um, the company I joined the company in 2016 and I love Paul's vision, and I just had a strong conviction about the relationship between Time series and Iot. Because if you think about it, what sensors do is they speak time, series, pressure, temperature, volume, humidity, light. They're measuring their instrumented something over time. And so I thought that would be super relevant over long term, and I've not regretted. Oh, >>no, and it's interesting at that time to go back in history. You know the role of databases are relational database, the one database to rule the world. And then, as clouds started coming in, you're starting to see more databases, proliferate types of databases. And Time series in particular, is interesting because real time has become super valuable. From an application standpoint, Iot, which speaks Time series, means something. It's like time matters >>times, >>and sometimes date is not worth it after the time. Sometimes it's worth it. And then you get the Data lake, so you have this whole new evolution. Is this the momentum? What's the momentum? I guess the question is, what's the momentum behind >>what's causing us to grow? So >>the time series. Why is time series in the category momentum? What's the bottom line? We'll >>think about it. You think about it from abroad, abroad, sort of frame, which is where what everybody's trying to do is build increasingly intelligent systems, whether it's a self driving car or a robotic system that does what you want to do or self healing software system. Everybody wants to build increasing intelligence systems, and so, in order to build these increasingly intelligence systems. You have to instrument the system well, and you have to instrument it over time, better and better. And so you need a tool, a fundamental tool to drive that instrumentation. And that's become clear to everybody that that instrumentation is all based on time. And so what happened? What happened? What happened? What's going to happen? And so you get to these applications, like predictive maintenance or smarter systems. And increasingly, you want to do that stuff not just intelligently, but fast in real time, so millisecond response, so that when you're driving a self driving car and the system realises that you're about to do something, essentially, you want to be able to act in something that looks like real time. All systems want to do that. I want to be more intelligent, and they want to be more real time. So we just happened to, you know, we happen to show up at the right time. In the evolution of the market. >>It's interesting. Near real time isn't good enough when you need real time. Yeah, >>it's not, it's not, and it's like it's like everybody wants even when you don't need it. Uh, ironically, you want it. It's like having the feature for, you know, you buy a new television, you want that one feature even though you're not going to use it, you decide that you're buying criteria. Real time is a buying criteria. >>So what you're saying, then is near real time is getting closer to real time as possible as possible. Okay, so talk about the aspect of data cause we're hearing a lot of conversations on the Cubans particular around how people are implementing and actually getting better. So iterating on data. >>But >>you have to know when it happened to get know how to fix it. So this is a big part of what we're seeing with people saying, Hey, you know, I want to make my machine learning albums better after the fact I want to learn from the data. Um, how does that How do you see that evolving? Is that one of the use cases of sensors as people bring data in off the network, getting better with the data knowing when it happened? >>Well, for sure, So for sure, what you're saying is is none of this is non linear. It's all incremental. And so if you take something, you know, just as an easy example. If you take a self driving car, what you're doing is your instrument in that car to understand where it can perform in the real world in real time. And if you do that, if you run the loop, which is I instrumented, I watch what happens. Oh, that's wrong. Oh, I have to correct for that. Correct for that in the software, if you do that four billion times, you get a self driving car. But every system moves along that evolution. And so you get the dynamic of you know of constantly instrumented, watching the system behave and do it and this and sets up driving cars. One thing. But even in the human genome, if you look at some of our customers, you know people like, you know, people doing solar arrays. People doing power walls like all of these systems, are getting smarter. >>What are the top application? What are you seeing your with Influx DB The Time series. What's the sweet spot for the application use case and some customers give some examples. >>Yeah, so it's pretty easy to understand. On one side of the equation. That's the physical side is sensors are the sensors are getting cheap. Obviously, we know that, and they're getting. The whole physical world is getting instrumented your home, your car, the factory floor, your wrist watch your healthcare, you name it. It's getting instrumented in the physical world. We're watching the physical world in real time, and so there are three or four sweet spots for us. But they're all on that side. They're all about Iot. So they're talking about consumer Iot projects like Google's Nest Tato Um, particle sensors, Um, even delivery engines like Happy who deliver the interesting part of South America. Like anywhere. There's a physical location doing that's on the consumer side. And then another exciting space is the industrial side. Factories are changing dramatically over time, increasingly moving away from proprietary equipment to develop or driven systems that run operational because what it has to get smarter when you're building, when you're building a factory, systems all have to get smarter. And then lastly, a lot in the renewables sustainability. So a lot, you know, Tesla, lucid motors, Nicola Motors, um you know, lots to do with electric cars, solar arrays, windmills are raised just anything that's going to get instrumented, that where that instrumentation becomes part of what the purpose is. >>It's interesting. The convergence of physical and digital is happening with the data Iot you mentioned. You know, you think of Iot. Look at the use cases there. It was proprietary OT systems now becoming more I p enabled Internet protocol and now edge compute getting smaller, faster, cheaper ai going to the edge. Now you have all kinds of new capabilities that bring that real time and time series opportunity. Are you seeing Iot going to a new level? What was that? What's the Iot? Where's the Iot dots connecting to? Because, you know, as these two cultures merge operations basically industrial factory car, they gotta get smarter. Intelligent edge is a buzzword, but it has to be more intelligent. Where's the where's the action in all this? So the >>action really, really at the core? >>It's >>at the developer, right, Because you're looking at these things. It's very hard to get off the shelf system to do the kinds of physical and software interaction. So the actions really happen at the developers. And so what you're seeing is a movement in the world that that maybe you and I grew up in with I t r o T moving increasingly that developer driven capability. And so all of these Iot systems, their bespoke, they don't come out of the box. And so the developer and the architect, the CTO they define what's my business? What am I trying to do trying to sequence the human genome and figure out when these genes express themselves? Or am I trying to figure out when the next heart rate monitor is going to show up in my apple watch, right? What am I trying to do? What's the system I need to build? And so starting with the developers where all of the good stuff happens here, which is different than it used to be, right, used to be used by an application or a service or a sad thing for But with this dynamic with this integration of systems, it's all about bespoke. It's all about building something. >>So let's get to the death of a real quick, real highlight point. Here is the data. I mean, I could see a developer saying, Okay, I need to have an application for the edge Iot, edge or car. I mean, we're gonna test look at applications of the cars right there. I mean, there's the modern application lifecycle now, so take us through how this impacts the developer doesn't impact their CI CD. Pipeline is a cloud native. I mean, where does this all Where does this go to? >>Well, so first of all you talking about, there was an internal journey that we had to go through as a company, which which I think is fascinating for anybody's interested as we went from primarily a monolithic software that was open source to building a cloud native platform, which means we have to move from an agile development environment to a C I C d. Environ. So two degree that you're moving your service whether it's, you know, Tesla, monitoring your car and updating your power walls right? Or whether it's a solar company updating your race right to the degree that services cloud then increasingly removed from an agile development to a CI CD environment which is shipping code to production every day. And so it's not just the developers, all the infrastructure to support the developers to run that service and that sort of stuff. I think that's also going to happen in a big way >>when your customer base that you have now and you see evolving with influx DB is it that they're gonna be writing more of the application or relying more on others? I mean, obviously the open source component here. So when you bring in kind of old way new Way Old Way was, I got a proprietary platform running all this Iot stuff and I got to write, Here's an application. That's general purpose. I have some flexibility, somewhat brittle. Maybe not a lot of robustness to it, but it does its job >>a good way to think about this. >>This is what >>So, yeah, a good way to think about this is what What's the role of the developer slashed architect C T o that chain within a large enterprise or a company. And so, um, the way to think about is I started my career in the aerospace industry, and so when you look at what Boeing does to assemble a plane, they build very, very few of the parts instead. What they do is they assemble, they buy the wings, they buy the engines they assemble. Actually, they don't buy the wings. It's the one thing they buy, the material of the way they build the wings because there's a lot of tech in the wings and they end up being assemblers, smart assemblers of what ends up being a flying aeroplane, which is pretty big deal even now. And so what happens with software people is they have the ability to pull from, you know, the best of the open source world, so they would pull a time series capability from us. Then they would assemble that with potentially some E t l logic from somebody else, or they assemble it with, um, a Kafka interface to be able to stream the data in. And so they become very good integrators and assemblers. But they become masters of that bespoke application, and I think that's where it goes because you're not writing native code for everything, >>so they're more flexible. They have faster time to market because they're assembling way faster and they get to still maintain their core competency. OK, the wings. In this case, >>they become increasingly not just coders, but designers and developers. They become broadly builders is what we like to think of it. People who started build stuff. By the way. This is not different than the people have just up the road Google have been doing for years or the tier one Amazon building all their own. >>Well, I think one of the things that's interesting is that this idea of a systems developing a system architecture, I mean systems, uh, systems have consequences when you make changes. So when you have now cloud data centre on premise and edge working together, how does that work across the system? You can't have a wing that doesn't work with the other wing. That's exactly >>that's where that's where the, you know that that Boeing or that aeroplane building analogy comes in for us. We've really been thoughtful about that because I o. T. It's critical. So are open Source Edge has the same API as our cloud native stuff that hasn't enterprise on premises or multiple products have the same API, and they have a relationship with each other. They can talk with each other, so the builder builds at once. And so this is where when you start thinking about the components that people have to use to build these services is that you want to make sure at least that base layer that database layer that those components talk to each other. >>We'll have to ask you. I'm the customer. I put my customer hat on. Okay. Hey, I'm dealing with a lot. >>I mean, you have appeal for >>a big check blank check. If you can answer this question only if you get the question right. I got all this important operation stuff. I got my factory. I got my self driving cars. This isn't like trivial stuff. This is my business. How should I be thinking about Time Series? Because now I have to make these architectural decisions as you mentioned and it's going to impact my application development. So huge decision point for your customers. What should I care about the most? What's in it for me? Why is time series important? Yeah, >>that's a great question. So chances are if you've got a business that was 20 years old or 25 years old, you're already thinking about Time series. You probably didn't call it that you built something on a work call or you build something that IBM db two. Right, and you made it work within your system, right? And so that's what you started building. So it's already out there. There are, you know, they're probably hundreds of millions of Time series applications out there today. But as you start to think about this increasing need for real time and you start to think about increasing intelligence, you think about optimising those systems over time. I hate the word but digital transformation, and you start with Time series. It's a foundational base layer for any system that you're going to build. There's no system I can think of where time series shouldn't be the foundational base layer. If you just want to store your data and just leave it there and then maybe look it up every five years, that's fine. That's not time. Serious time series when you're building a smarter, more intelligent, more real time system, and the developers now know that, and so the more they play a role in building these systems, the more obvious it becomes. >>And since I have a P o for you in a big check, what what's the value to me as like when I implement this What's the end state? What's it look like when it's up and running? What's the value proposition for me? What's in it? >>So when it's up and running, you're able to handle the queries, the writing of the data, the down sampling of the data transforming it in near real time. So the other dependencies that a system that gets for adjusting a solar array or trading energy off of a power wall or some sort of human genome those systems work better. So time series is foundational. It's not like it's, you know, it's not like it's doing every action that's above, but it's foundational to build a really compelling intelligence system. I think that's what developers and architects are seeing now. >>Bottom line. Final word. What's in it for the customer? What's what's your What's your statement of the customer? Would you say to someone looking to do something in time, series and edge? >>Yeah. So it's pretty clear to clear to us that if you're building, if you view yourself as being in the building business of building systems that you want them to be increasingly intelligent, self healing, autonomous, you want them to operate in real time that you start from Time series. I also want to say What's in it for us in flux? What's in it for us is people are doing some amazing stuff. I highlighted some of the energy stuff, some of the human genome, some of the health care. It's hard not to be proud or feel like. Wow. Somehow I've been lucky. I've arrived at the right time in the right place, with the right people to be able to deliver on that. That's That's also exciting on our side of the equation. >>It's critical infrastructure, critical critical operations. >>Yeah, great >>stuff. Evan. Thanks for coming on. Appreciate this segment. All right. In a moment. Brian Gilmore, director of Iot and emerging Technology that influx, they will join me. You're watching the Cube leader in tech coverage. Thanks for watching

>>Hey, welcome back to live coverage in San Francisco, California, the cubes coverage of 80 west summit, 2022 here in SF and NYC New York city. Summit's coming up in the summer. We'll be there as well. Check it out. Okay. We've got a great guest here. C Bhan co and CEO RAI systems. Welcome to the cube, hot startup and growing company. And Kubernetes is great to see you. >>Yeah, John, thanks for having me. Appreciate it. >>Great to have you on. So Cubans coming up, you got cloud native here at AWS. You guys in the middle of it, take a minute to explain what your company does. Sure. >>So 50,000 enterprises are going to modernize in the next five to 10 years. They're all going to run into the exact same problem, which is they're gonna choose Kubernetes as the orchestra platform. And then they're gonna invest in building a platform essentially on top of Kubernetes so that their internal consumers, that developers can consume it. That requires a lot, a lot of effort. We, lot of people, a lot of time, a lot of effort, what we did was we thought about entire journey for Kubernetes operations that a team would go through and we package that as an offering. It's a SaaS product that you can consume. You can make it work with Amazon's Kubernetes, Azures Kubernetes, Googles, Kubernetes, upstream, Kubernetes, but then you can move significantly faster so that the goal of modernization can be achieved now versus two years more. >>What's the big, uh, opportunity that Kubernetes brings. And what are some of the pain points that are being removed or solved or blockers being removed and pain being reduced? Is it standing up Kubernetes? Is it running it in production? Is it the new revisions? I mean, honestly, it's huge. Yeah. What's the pain point. The customers that you guys solve. >>Yeah. Look, the, the paradox with Kubernetes is when it's working. It's awesome. It's great. And we can move it fast, but to get there, it's hard. Yeah. So simple things as a starting point, how do I provision my infrastructure repeatedly in the same way with the right blueprints? How do I make sure they all look the same? How do I make sure John can access certain things? And he cannot, how do I make sure the right policies are set up? How do I make sure consistent deployment is happening? Can I watch every we think, and I measure everything and we are not beyond basic things, right? Yeah. I need to back this up, you know, on and on. I need to do cost management. I need to network policy management. I need service management. You already built the team now. Right? Each of these is, is, is multiple people's jobs sometimes. Right? So it's really complicated. But again, everybody is investing. This is complexity. It's complexity. Yes. But people are investing in this because everybody understands now that once this is all working, the beauty, the, the P the pace at which you can run is exactly what we were promised five, six years ago when we were all told about modernization. Yeah. So the, when you get there, it's awesome. And we are helping companies get there significantly faster. Then they would've had, were they not working with a company? >>It's it really is a holy grail kind of orchestration layer if it works. And a lot of people, even myself, which a big fan of Kubernetes, caution, cautions over the oo problem, which is the clusters are up. I can't find talent to run them. They're too hard. Um, that's kind of in the back of people's minds and there's a lot of scar tissue around that. Uh, and then a little bit of open stack, you know, is it too hard, too hard? So the question is, is that what needs to happen to be successful with Kubernetes to make that go faster? So that's easy to deploy. Exactly. Yeah. And what what's your product do? Is it software open source? Yeah. What's, what's your product? >>The, the key here is repeatably usable automation. It's automation that it can use again and again, and it's flexible enough that it solves for many companies problem. You know, the funny thing is, and this is something that took me a while to figure out whether we have a financial services customer or an insurance company, or a healthcare company, or a high tech company, you know, what their problems are exactly the same. <laugh> when it comes to Kubernetes, it's all the same, right? So we figured out what it takes to build that automation in a repeatable fashion so that we could essentially sell it as a product. Our product is a SaaS product. Um, and once you have the right automation in place that you can ideally consume as a service, then now the beauty is that the people who are using it on a day to day basis, they don't need to be as expert at Kubernetes as today. Yeah. And that's the issue today? The issue is, you know, people, I've seen ads now where people say, you know, looking for Kubernetes expertise, 10 years, minimum experience, okay, that's ridiculous. Right. But you see these ads out there, right? Because people are rude about it, a tool like this makes it easy for you to take your existing skillset, existing resources and allow them to become Kubernetes. >>That's the key. I think that's the key in my mind is like hiring talent for these, I call DevOps glass eating projects, cuz it's hard. Yep. Some of this stuff's hard when you get down to the early stuff. And even in the hyperscalers, you look at the early hyperscalers, they were rolling their own and they were rock stars. And they were like the 1% of top developers. Right? Yep. And now you have general audiences who just want to code. Yep. They want abstractions. They want Kubernetes as a service. Uh, and they want all the benefits. And even if they could hire the Oddsly hiring the low level core people yeah. Is hard. Yeah. >>It takes time. Yeah. >>Absolutely. That's a core problem you guys solve. >>Absolutely. I think look, the, the one thing that every enterprise you think about is when the, the big companies, the hyperscale is that you mentioned that build this themselves when they us out 5, 6, 7, whatever years ago, when, you know, even some, some of them pre Kubernetes, it was a competitive advantage to roll this out because nobody else was doing it now as, as an enterprise who is trying to use software to move faster. Yeah. It's actually a competitive disadvantage because now you're building your own product. And now you're building this thing called Kubernetes that doesn't make any sense, focus your application, focus on your products, roll them out faster, and then essentially reuse the learnings from the market. Right. That's what we are doing. Really? What, what are we doing? We're taking the best practices of this industry and packaging that up into an easy to consume platform. That's awesome. That's it? >>Well, we'll see you in Cooper, Cuban, not Kubernetes contest in Valencia. Yep. Uh, and thanks for coming on. I know we didn't have a lot of time to drill into it, um, here, but great to meet you and the company. Final question as a co-founder what's your north star, you got, you got a company to run in. Bill got employees, you're managing and hiring inspiring. What's the north star for the company. >>So I'd say, I mean, the phrase that I, that, that I think about when, when you say north star is, is loyalty with urgency. >>So loyalty to whom? Yeah. It's to my team, right? My team comes first beyond before anything else. Right? And then my customers, right? My customers, many, many of our, our customers even now, right? We a four old company, they have my cell phone number and people call me at odd hours and I will show up. I will get people on a call. I will show up. Right. That's critical. But with urgency now my customer needs help. It needs to happen now. Not tomorrow, not next week. My team has heard me say this a thousand times, by the way, not tomorrow, not next week now. And this, if you do this in a startup, you will be successful. >>Yeah. I mean, you gotta make the market as the founder, inspiring people, product market fits huge. Yep. Getting that scale point. Yep. Where you're got the value proposition in position you're in mode to scale, you got visibility on unit economics. It's hard. Yep. It's super hard look. Good news is you get in a good area. Cloud native Kubernetes, automation, cloud, native modernization of apps. Super hot right now. Yeah. Big >>Time. Yeah. Look, I mean, you know, of course you, you want your teams to be topnotch. Right. But I gotta tell you there's a lot of luck and timing to everything. >>Exactly. >>Timing is in hindsight, nobody times anything. Right. So we have, time is perfect, but it's luck. Yeah. Right. We're very lucky. We're we have the right team. We're doing a great job. I think our customers are very happy. What we've rebuilt and uh, you know, look forward >>To Steve. You're humble. And you're a humble person. I can tell. I don't believe in luck. I think you make luck. I think luck is just part of the hustle, making those phone calls, doing those calls, doing the right things, grinding. And then when you get the shot, you're ready. Yeah. Yeah. So congratulations. Thanks for coming the queue. Appreciate it. Appreciate your time, sir. Nice to meet you coverage here in San Francisco, back with more day, two coverage. After this short break, stay with us.

>>I want to welcome back to the cubes coverage. We're here at another event in person I'm John furrier, host of the cube. We've got to CNCF coop con cloud native con for in-person 2021. And we're back. It's a hybrid event and we're streaming lives on all channels, as well as all the folks watching a great guest kicking off the show here from the co-chairs from cataract coast. Is that right? Danielle Cook. Who's the vice president at Fairwinds and John Foreman director at Accenture. Thanks for coming on your co-chair. Your third co-chair is not here, but you guys are here to talk about the cloud maturity model. Pretty mature funding is flowing tons of announcements. We're going to have a startup on $200 million. They're announcing in funding and observability of all of all hot spaces. Um, so the maturity is it's the journey in the cloud native space now is crossed over to mainstream. That's the we've been telling that story for a couple of years. Now, you guys have been working on this. Tell us about the cloud maturity model you guys worked on. >>So we got together earlier this year because we, um, four of us had been working on maturity models. So Simon Forester, who is one of the co-chairs, who isn't here, he had worked on a maturity model that looked at your legacy journey, all the way to cloud native, um, myself, I had been part of the Fairwinds team working on the Kubernetes maturity model. So, and then, um, we have Robbie, who's not here. And John Foreman, who we all got together, they had worked on a maturity model and we put it together and I've been working since February to go, what is cloud native maturity and what are the stages you need to go through to achieve maturity. So put this together and now we have this great model that people can use to take them from. I have no idea what cloud native is to the steps they can take to actually be a mature organization. >>And, you know, you've made it when you have a book here. So just hold that up to the camera real quick. So you can see it. It's very much in spirit of the community, but in all seriousness, it book's great, but this is a real need. What was the pain point? What was jumping out at you guys on the problem? Was it just where people like trying to get more cloud native, they want to go move faster. It was a confusing, what were the problems you solve in? >>Well, and if anything is, if we start at the beginning, right, there was during the cloud journey DevSecOps and the Kootenays being a thing that then there's journeys to DevSecOps tributaries as well. But everything is leading to cloud native. It's about the journey to cloud native. So everybody, you know, we're taught to go John, the ecosystem's an eyesore man. If I look at, you know, landscape, >>The whole map I >>Need, it's just like in trend map, it's just so confusing what we do. So every time we go to, I revert the wheel and I get them from zero to hero. So we just put together a model instead that we can re reuse yeah. As a good reference architecture. So from that is a primary, how we built because the native trademark you have with us today. So it's a five scale model from one to five what's twice today, or how to, to, you know, what our job is getting to a five where they could optimize a really rocket rolling. >>You know, it's interesting. I love these inflection points and, you know, being a student of history and the tech business there's moments where things are the new thing, and they're really truly new things like first-time operationalized dev ops. I mean the hardcore dev ops or early adopters we've been doing that, you know, we know that, but now mainstream, like, okay, this is a real disruption in a positive way. So the transformation is happening and it's new, new roles, new, new workflows, new, uh, team formations. So there's a, it's complicated in the sense of getting it up and running so I can see the need. How can you guys share your data on where people are? Because now you have more data coming in, you have more people doing dev ops, more cloud native development, and you mentioned security shepherds shifting left. Where's the data tell you, is it, as you said, people are more like a two or more. What's the, what's the data say? >>So we've had, so part of pulling this model together was your experience at Accenture, helping clients, the Fairwinds, um, experience, helping people manage Kubernetes. And so it's from out dozens of clusters that people have managed going, okay, where are people? And they don't even know where they are. So if we provide the guidelines from them, they can read it and go, oh, I am at about two. So the data is actually anecdotal from our experiences at our different companies. Um, but we, you know, we we've made it so that you can self identify, but we've also recognized that you might be at stage two for one application, but five for another application. So just because you're on this journey, doesn't mean everything is in, >>It's not boiler plate. It's really unique to every enterprise because they everyone's different >>Journey. Put you in journey with these things. A big part of this also torn apart one to five, your clients wants to in denial, you know? So, so Mr. CX level, you are level two. We are not, there's no way we would deal with this stuff for years. You've got to be a five. No, sorry. You're too. >>So >>There's use denial also about this. People think they do a cloud-native director rolling, and I'm looking at what they're doing and go, okay, do you do workups security? And they go, what's that? I go, exactly. So we really need to peel back the onion, start from seed year out and we need to be >>All right. So I want to ask more about the, um, the process and how that relates to the themes are involved. What are some of the themes around the maturity model that you guys can share that you see that people can look at and say, how do I self identify? What's the process will come to expect? >>Well, one of the things we did when we were putting it together was we realized that there were themes coming out amongst the maturity model itself. So we realized there's a whole people layer. There's a whole policy layer process and technology. So this maturity model does not just look at, Hey, this is the tech you need to do. It looks at how you introduce cloud native to your organization. How do you take the people along with it? What policies you need to put in place the process. So we did that first and foremost, but one of the things that was super important to all of us was that security was ever present throughout it. Because as everything is shifting left, you need to be looking at security from day one and considering how it's going to happen and roll out from your developers all the way to your compliance people. Um, it's super important. And one of the themes throughout. >>So, so it would be safe to say, then that security was a catalyst for the maturity models because you gotta be mature. I mean, security, you don't fool around security. >>About the last year when I created the program for, since I worked with Cheryl Holland, from CCF, we put together the community certification, her special program. I saw a need where security was a big gap in communities. Nobody knew anything about it. They wanted to use the old rack and stack ways of doing it. They wanted to use their tray micro tombs from yesteryear, and that doesn't work anymore. You need a new set of tools for Kubernetes. It's the upgrade system. It's different way of doing things. So that knowledge is critical. So I think you're part of this again, on this journey was getting certifications out there for people to understand how to do better. Now, the next phase of that now it's how do we put all these pieces together and built this roadmap? >>Well, it's a great group. You guys have the working groups hard to pronounce the name, but, uh, it's a great effort because one of the things I'm hearing and we've been reporting this one, the Cubans looking angle is the modern software developers want speed, and they don't want to wait for the old slow groups now and security, and it are viewed as blockers and like slow things down. And so you start to see a trend where those groups could provide policy and then start putting, feeding up, uh, data models that allow the developers in real time to do their coding, to shift left and to be efficient and move on and code not be waiting for weeks or days >>Comes to play. So today is the age of Caleb's right now, get up this emerging we're only to have now where everything is code policies, code, securities, code policies, cookie figures, code. That is the place for, and then again, walk a fusion more need for a cargo office. >>Okay. What's your thoughts on that? >>So I think what's really important is enabling service ownership, right? You need the developers to be able to do security, see policy, see it live and make sure that, you know, you're not your configuration, isn't stopping the build or getting into production. So, you know, we made sure that was part of the maturity model. Like you need to be looking continuous scanning throughout checking security checking policy. What is your process? Um, and we, you know, we made that ever present so that the developers are the ones who are making sure that you're getting to Kubernetes, you're getting to cloud native and you're doing it. >>Well, the folks watching, if you don't know the cloud native landscape slide, that ecosystem slide, it's getting bigger and bigger. There's more new things emerging. You see role of software abstractions coming in, automation and AI are coming in. So it makes it very challenging if you want to jump right in lifting and shifting to the clouds, really easy check, been there, done that, but companies want to refactor their applications, not just replatform refactoring means completely taking advantage of these higher level services. So, so it's going to be hard to navigate. So I guess with all that being said, what you guys advice to people who are saying, I need the navigation. I need to have the blueprint. What do I do? How do I get involved? And how do I leverage this? >>We want people to, you can go on to get hub and check out our group and read the maturity model. You can understand it, self identify where you're at, but we want people to get involved as well. So if they're seeing something that like, actually this needs to be adjusted slightly, please join the group. The cardiograph is group. Um, you can also get copies of our book available on the show. So if you, um, if you know, you can read it and it takes you line by line in a really playful way as to where you should be at in the maturity model. >>And on top of that, if you come Thursday was Sonia book. And of course, a lot of money, one day, I promise >>You guys are good. I gotta ask, you know, the final question is like more and more, just more personal commentary. If you don't mind, as teams start to change, this is obviously causing a lot of positive transformation if done, right? So the roles and the teams are starting to change. Hearing SRS are now not just the dev ops guys provisioning they're part of the, of the scale piece, the developers shifting left, new kind of workflows, the role of certain engineers and developers now, new team formations. Why were you guys seeing that evolve? Is there any trends that you see around how people are reconfiguring their team makeup? >>I think a lot of things is going to a single panic last tonight, where I'm taking dev and ops and putting them one panel where I can see everything going on in my environment, which is very critical. So right now we're seeing a pre-training where every client wants to be able to have the holy grail of a secret credit class to drive to that. But for you to get there, there's a lot of work you've got to do overnight that will not happen. And that's where this maturity model, I think again, will enhance that ability to do that. >>There's a cultural shift happening. I mean, people are changing there's new skillsets and you know, obviously there's a lot of people who don't have the skill. So it's super important that people work with Kubernetes, get certified, use the maturity model to help them know what skills they need. >>And it's a living document too. It's not, I mean, a book and I was living book. It's going to evolve. Uh, what areas you think are going to come next? So you guys have to predict if you had to see kind of where the pieces are going. Uh, obviously with cloud, everything's getting, you know, more Lego blocks to play with more coolness you have in the, in this world. What's coming next with Sue. Do you guys see any, any, uh, forecasts or >>We're working with each one of the tag groups within the CNCF to help us build it out and come up with what is next based on their expertise in the area. So we'll see lots more coming. Um, and we hope that the maturity grows and because of something that everybody relies on and that they can use alongside the landscape and the trail map. And, um, >>It's super valuable. I think you guys need a plug for any people want to, how they join. If I want to get involved, how do I, what do I do? >>Um, you can join the Carter Garfish group. You can check us out on, get hub and see all the information there. Um, we have a slack channel within the CNCF and we have calls every other Tuesday that people can see the pools. >>Awesome. Congratulations, we'll need it. And super important as people want to navigate and start building out, you know, you've got to edge right around the corner there it's happening real fast. Data's at the edge. You got cloud at the edge. Azure, AWS, Google. I mean, they're pushing really hardcore 5g, lot changes. >>Everybody wants to cloud today. Now one client is, one is more cloud. At least both the cloud is comfortable playing everywhere. One pump wife had DevOps. >>It's distributed computing back in the modern era. Thank you so much for coming on the keep appreciating. Okay. I'm Jennifer here for cube con cloud native con 2021 in person. It's a hybrid event. We're here live on the floor show floor, bringing you all the coverage. Thanks for watching station all day. Next three days here in Los Angeles. Thanks for watching. >>Thank you.

>>Mhm Welcome back to Los Angeles. The Cubans live, I can't say that enough. The Cubans live. We're at cu con cloud Native Con 21. We've been here all day yesterday and today and tomorrow talking with lots of gas. Really uncovering what's going on in the world of kubernetes, lisa martin here with Dave Nicholson. We've got some folks. Next we're gonna be talking about a customer use case, which is always one of my favorite things to talk about. Please welcome Michael Coletti, the principal platform engineer at CHG Healthcare and then cat from a christian VP of products from port works by pure storage. Guys, welcome to the program, Thank you. Happy to be here. Yeah. So Michael, first of all, let's go ahead and start with you, give the audience an overview of CHG healthcare. >>Yeah, so CHG Healthcare were a staffing company so we sure like a locum pen and so our clients are doctors and hospitals, so we help staff hospitals with temporary doctors or even permanent placing. So we deal with a lot of doctors, a lot of nursing and we're were a combination of multiple companies to see if she is the parents. So and uh yeah, we're known in the industry is one of the leaders in this, this field and providing uh hospitals with high quality uh doctors and nurses and uh you know, our customer services like number one and one of these are Ceos really focused on is now how do we make that more digital, how we provide that same level of quality of service, but a digital experience as rich for >>I can imagine there was a massive need for that in the last 18 months alone. >>Covid definitely really raised that awareness out for us and the importance of that digital experience and that we need to be out there in the digital market. >>Absolutely. So your customer report works by pure storage, we're gonna get into that. But then can talk to us about what's going on. The acquisition of port works by peer storage was about a year ago I talked to us about your VP of product, what's going on? >>Yeah, I mean, you know, first of all, I think I could not say how much of a great fit for a port works to be part of your storage. It's uh uh Pure itself is a very fast moving large start up that's a dominant leader in a flash and data center space. And you know, pure recognizes the fact that Cuban it is is the new operating system of the cloud is now how you know, it's kind of virtualizing the cloud itself and there is a, you know, a big burgeoning need for data management in communities and how you can kind of orchestrate work lords between your on prem data centers in the cloud and back. So port books fits right into the story as complete vision of data management for our customers and uh spend phenomenal or business has grown as part of being part of Pure and uh you know, we're looking at uh launching some new products as well and it's all exciting times. >>So you must have been pretty delighted to be acquired as a startup by essentially a startup because because although pure has reached significant milestones in the storage business and is a leader in flash storage still, that, that startup mindset is there, that's unique, that's not, that's not the same as being acquired by a company that's been around for 100 years seeking to revitalize >>itself. Can >>you talk a little bit about that >>aspect? So I think it will uh, Purest culture is highly innovation driven and it's a very open flat culture. Right? I mean everybody impure is accessible, it can easily have a conversation with folks and everybody has his learning mindset and Port works is and has always been in the same way. Right? So when you put these teams together, if we can create wonders, I mean we, right after that position, just within a few months we announced an integrated solution that Port works orchestrates volumes and she file shares in Pure flash products and then delivers as an integrated solution for our customers. And Pure has a phenomenal uh, cloud based monitoring and management system called Pure one that we integrated well into. Now we're bringing the power of all of the observe ability that Purest customers are used to for all of the partners customers and having super happy, you know, delivering that capability to our customers and our customers are delighted now they can have a complete view all the way from community is an >>app to the >>flash and I don't think any one company on the planet can even climb, they can do that. >>I think, I think it's fair to acknowledge that pure one was observe ability before observe ability was a word. Exactly one used regularly. So that's very interesting. >>I could talk to us about obviously you are a customer CHD as a customer of court works now Port works by peer storage. Talk to us about the use case, what what was the compelling? It was their compelling event and from a storage perspective that that led you to Port works in the >>first so we be, they began this our Ceo basically in the vision, we we need to have a digital presence, we need and hazards and this was even before Covid, so they brought me on board and my my manager read uh glass or he we basically had this task to how are we going to get out into the cloud, how we're going to make that happen And we we chose to follow very much cloud native strategy and the platform of choice. I mean it just made sense with kubernetes and so when we were looking at kubernetes, we're starting to figure out how we're doing, we knew that data is going to be a big factor, you know, um being to provide data, we're very much focused on an event driven, were really pushing to event driven architecture. So we leverage Kafka on top of kubernetes, but at the time we were actually leveraging Kafka with M S K down out in a W S and that was just a huge cost to us. So I came on board, I had experienced with poor works prior company before that and I basically said we need to figure out a great storage away overlay. And the only way to do is we gotta have high performance storage, we've got to have secure, we gotta be able to back up and recover that storage and the poor works was the right match and that allowed us to have a very smooth transition off of M S K onto kubernetes, saving us, it's a significant amount of money per month and just leverage that already existing hardware that are existing, compute memory and just in the and move right to port works, >>leveraging your existing investments. >>Exactly which is key. Very, very key. So, >>so been kept, how common are the challenges that when you guys came together with the HD, how common are the challenges? It's actually, >>that's a great question, you know, this is, I'll tell you the challenges that Michael and his team are running into is what we see a lot in the, in the industry where people pay a ton of money, you know, to, you know, to to other vendors or especially in some cases use some cloud native services, but they want to have control over the data. They want to control the cost and they want higher performance and they want to have, you know, there's also governance and regulatory things that they need to control better. So they want to kind of bring these services and have more control over them. Right? So now we will work very well with all of our partners including the cloud providers as well as uh, you know, an from several vendors and everybody but different customers are different kinds of needs and port works gives them the flexibility if you are a customer who want, you know, have a lot of control over your applications, the performance of the agency and want to control cars very well in leveraging existing investments board works can deliver that for you in your data center right now you can integrate it with pure slash and you get a complete solution or you won't run it in cloud and you still want to have leverage the agility of the cloud and scale for books delivers a solution for you as well. So it kind of not only protects their investment in future proves their architecture, you get future proving your architecture completely. So if you want to tear the cloud or burst the cloud, you have a great solution that you can continue to leverage >>when you hear a future proof and I'm a marketer. So I always go, I love to know what it means to different people, what does that mean to you in your environment? >>My environment. So a future proof means like one of the things we've been addressing lately, that's just a real big challenge and I'm sure it's a challenge in the industry, especially Q and A's is upgrading our clusters ability to actually maintain a consistent flow with how fast kubernetes is growing, you know, they they're out I think yes, we leverage eks so it's like 1 21 or 1 22 now, uh that effort to upgrade a cluster, it can be a daunting one with port works. We actually were able to make that to where we could actually spin up a brand new cluster and with port work shift, all our application services, data migrated completely over poor works, handles all that for us and stand up that new cluster in less than a day. And that effort, it would take us a week, two weeks to do so not even man hours the time spent there, but just the reliability of being able to do that and the cost, you know, instead of standing up a new cluster and configuring it and doing all that and spending all that time, we can just really, we move to what we call blue green cut over strategy and port works is an essential piece of that. >>So is it fair to say that there are a variety of ways that people approach port works from a, from a value perspective in terms of, I I know that one area that you are particularly good in is the area of backups in this environment, but then you get data management and there's a third kind of vector there. What is the third vector? >>Yeah, it's all of the data services. Data services, like for example, database as a service on any kubernetes cluster paid on your cloud or you're on from data centers, which >>data, what kind of databases >>you were talking about? Anything from Red is Kafka Postgres, my sequel, you know, council were supporting, we just announced something called port books, data services offering that essentially delivers all these databases as a service on any kubernetes cluster uh that that a customer can point to unless than kind of get the automated management of the database on day one to day three, the entire life cycle. Um you know, through regular communities, could curdle experience through Api and SDK s and a nice slick ui that they can, you know, just role based access control and all of that, that they can completely control their data and their applications through it. And, you know, that's the third vector of potatoes Africans >>like a question for you. So what works has been a part of peer storage? You've known it since obviously for several years before you were a c h G, you brought up to see H G, you now know it a year into being acquired by a fast paced startup. Talk to me about the relationship and some of the benefits that you're getting with port works as a part of pure storage. >>Well, I mean one of the things, you know, when, when I heard about the accusation, my first thing was I was a little bit concerned is that relationship going to change and when we were acquiring, when we're looking at a doctor and Poor works, One thing I would tell my management is poor works is not just a vendor that wants to throw a solution on you and provide some capability there, partner, they want to partner with you and your success in your journey and this whole cloud native journey to provide this rich digital experience for not only our platform engineering team, but our dev teams, but also be able to really accelerate the development of our services so we can provide that digital portal for our end users and that didn't change. If anything that accelerated that that relationship did not change. You know, I came to the cat with an issue we just, we're dealing with, he immediately got someone on the phone call with me and so that has not changed. So it's really exciting to see that now that they've been acquired that they still are very much invested in the success of their customers and making sure we're successful. You know, it's not all of a sudden I was worried I was gonna have to do a whole different support process and it's gonna go into a black hole didn't happen. They still are very much involved with their customers. And >>that sounds kind of similar to what you talked about with the cultural alignment I've known here for a long time and they're very customer centric. Sounds like one of the areas in which there was a very strong alignment with port works. >>Absolutely important works has always taken pride in being customer. First company. Our founders are heavily customer focused. Uh, you know, they are aligned. They want, they have always aligned uh, the portraits business to our customers needs. Uh Pure is a company that's men. I actually focused on customers, right? I mean, that's all, you know, purist founder cause and everybody care about and so, you know, bringing these companies together and being part of the pure team. I kind of see how synergistic it is. And you know, we have, you know, that has enabled us to serve our customers customers even better than before. >>So, I'm curious about the two of you personally, in terms of your histories, I'm going to assume that you didn't both just bounce out of high school into the world of kubernetes, right? So like lisa and I your spanning the generations between the world of, say, virtualization based on X 86 architecture and virtualization where you can have microservices, you have a full blown operating system that you're working with, that kind of talk about, you know, Michael with you first talk about what that's been like navigating that change. We were in the midst of that, Do you have advice for others that are navigating that change? >>Don't be afraid of it, you know, a lot of people want to, you know, I call it, we're moving from where we're uh naming, we still have cats and dogs, they have a name, the VMS either whether or not their physical boxes or their VMS to where it's more like it's a cattle, you know, it's like we don't own the Os and not to be afraid afraid of that because change is really good. You know, the ability for me to not have to worry about patching and operating system is huge, you know, where I can rely on someone like the chaos and and the version and allow them to, if CV comes out, they let me know I go and I use their tools to be able to upgrade. So I don't have to literally worry about owning that Os and continues the same thing. You know, you, you, you know, it's all about being fault tolerant, right? And being able to be changed where you can actually brought a new version of a container, a base image with a lot of these without having to go and catch a bunch of servers, I mean patch night was held, I'm sorry if I could say that, but it was a nightmare, you know, but this whole world has just been a game changer >>with that. So Van cut from your perspective, you were coming at it, going into a startup, looking at the landscape in the future and seeing opportunity, um what what what's that been like for you? I guess the question for you is more something lisa and I talk about this concept of peak kubernetes, where are we in the wave, is this just is this just the beginning, are we in the thick of it? >>Yeah, I think I would say we're kind of transitioning from earlier doctors too early majority face in the whole, you know, um crossing the chasm analogy. Right, so uh I would say we're still the early stages of this big wave that's going to transform how infrastructure is built, apps are, apps are built and managed and run in production. Um I think some of the uh pieces, the key pieces are falling in place and maturing, uh there are some other pieces like observe ability and security, uh you know, kind of edge use cases need to be, you know, they're kind of going to get a lot more mature and you'll see that the cloud as we know today and the apps as we know today, they're going to be radically different and you know, if you're not building your apps and your business on this modern platform, on this modern infrastructure, you're gonna be left behind. Um, you know, I, my wife's birthday was a couple of days ago. I was telling this story a couple of friends is that I r I used another flowers delivery website. Uh they missed delivering the flowers on the same day, right? So when they told me all kinds of excuses, then I just went and looked up, you know, like door dash, which delivers uh, you know, and then, you know, like your food, but there's also flower delivery, indoor dash and I don't do it, I door dash flowers to her and I can track the flower does all the way she did not eat them, okay, You need them. But my kids love the chocolates though. So, you know, the case in point is that you cannot be, you know, building a modern business without leveraging the moral toolchain and modern toolchain and how the business is going to be delivered. That that thing is going to be changing dramatically. And those kind of customer experience, if you don't deliver, uh, you're not gonna be successful in business and communities is the fundamental technology that enables these containers. It's a fundamental piece of technology that enables building new businesses, you know, modernizing existing businesses and the five G is gonna be, there's gonna be new innovations that's going to get unleashed. And uh, again, communities and containers enable us to leverage those. And so we're still scratching the surface on this, it's big now, it's going to be much, much bigger as we go to the next couple of years. >>Speaking of scratching the surface, Michael, take us out in the last 30 seconds or so with where CHG healthcare is on its digital transformation. How is port works facilitating that? >>So we're right in the thick of it. I mean we are we still have what we call the legacy, we're working on getting those. But I mean we're really moving forward um to provide that rich experience, especially with inventing driven platforms like Kafka and Kubernetes and partnering with port works is one of the key things for us with that and a W s along with that. But we're, and I remember I heard a talk and I can't, I can't remember me but he he talked about how, how kubernetes just sort of like 56 K. Modem, You're hearing it, see, but it's got to get to the point where it's just there, it's just the high speed internet and Kelsey Hightower, That's who Great. Yeah, and I really like that because that's true, you know, and that's where we're on that transition, where we're still early, it's still that 50. So you still want to hear a note, you still want to do cube Cto, you want to learn it the hard way and do all that fun stuff, but eventually it's gonna be where it's just, it's just there and it's running everything like five G. I mean stripped down doing Micro K. It's things like that, you know, we're gonna see it in a lot of other areas and just proliferate and really accelerate uh the industry and compute and memory and, and storage and >>yeah, a lot of acceleration guys, thank you. This has been a really interesting session. I always love digging into customer use cases how C H. G is really driving its evolution with port works Venkat. Thanks for sharing with us. What's going on with port works a year after the acquisition. It sounds like all good stuff. >>Thank you. Thanks for having us. It's been fun, our >>pleasure. Alright for Dave Nicholson. I'm lisa martin. You're watching the cube live from Los Angeles. This is our coverage of Yukon cloud native Con 21 mhm

>>from the bellagio hotel >>in Las Vegas, it's the cube covering Ui Path forward. Four brought to you >>by Ui Path. Welcome back from the bellagio in Las Vegas. The Cubans live at Ui Path forward for I'm lisa martin here with Dave Volonte. We're gonna be talking about roadblocks to automation and how to navigate around them, joining us next as Pernando Panini expert associate partner at bain and company per night. Welcome to the program. >>Thanks lisa. Happy to be here. >>Talk to us about some of the use cases that bain is working on with you I Path and then we'll dig into some of those roadblocks that you guys have uncovered. >>Yes. Uh I started a few months ago where we're working with Brandon who's the product lead on the Ui part side. We wanted to understand what's the state of citizen development and what are the blockers and how we should Both from the product side. But also on the automation journey side we need to dig deeper and understand where each of the clients and the employees are going through the journey together >>and if you look at it from the citizen developer perspective, what are some of those roadblocks? >>There are a few. So when like if you before we go to the roadblocks there are three main concerns or I would say critical groups that are involved in being successful with automation. The organization or bu leaders, the I. T. And employees. So each of the groups have different perceptions on like misconceptions or perceptions on benefits of automation and how to go up go about it. The blockers that we have seen where like a three sets of blockers. The first is cognitive where employees are unaware of automation on the benefits of automation and the second one is more organizational where organization leaders and how they feel about automation or how the how they think about employees when we introduce automation to them. One part of that is there is a misconception without nation leaders that employees are fearful of job loss when you introduce automation. What we have seen in our research is it's completely the opposite of employees are eager to adopt automation have given an opportunity, they are willing to upscale themselves and they are willing to save the time so that they can spend that on critical value added activities for um for their customers in the process. And a third blocker that we have seen is more on the product side where the some of the employees that we talked to as much as progress has been made by RPF vendors and local local vendors. It's still these tools are not intuitive user friendly for business users. They still feel they need to go through some training programs and have a better user friendly interface is >>what's the entry point she would organization first time I ever heard of Arpaio Years and years and years ago was at a CFO conference. Okay so that's cool. It seems like it forward for there's a lot more C. I. O presence here and that. Is that relatively new or did I just miss it before? >>It is relatively new. So like when we looked at like in the past few years the empty point has been someone in finance or I. T. Has heard about R. P. A. The benefits of head. They went and bought a handful of licenses and then they went and implemented it but it's just a handful of processes. It's not organizational wide. It has been mostly on a smaller sub scale of processes. And projects now that like organizations are realizing employees are asking and we are like slowly growing up with automation ceo es it's now it's intersecting with the C XL level of if it has to intersect with your or if you want to reinvent your business through automation, it has to come from the sea X level and that's where we're seeing more and more. See IOS are being involved in decisions on automation journeys, the technologies they have to buy and adopt for the business processes. >>So I. T. Can be an enabler of course. Also sometimes it can be a blocker. Um and you know, certainly from security standpoint governance etcetera. And so one of the things that we heard today in the keynotes was you don't want to automate the C I. O. He or she owns this application portfolio and everybody wants to do new projects because that's the fun stuff we heard from one CFO. Yeah. You add up all the NPV from the new projects. It's bigger than the valuation of the company. Right. But the C i O is stuck having to manage the infrastructure and all the processes around the existing application portfolio. One of things I heard today was don't automate an application or a process that you're trying to retire because we never get rid of stuff in it. So I wonder should automation like an enterprise wide automation? Should there be kind of an application rationalization exercise or a business process rationalization coincident with that >>initiative? Absolutely. I think that was one of the blockers that we have seen. Like some of the misconceptions and some of the blockers when I looked at it for them, they consider like you're bringing all these tools you're asking business users to like who haven't had haven't been trained in technology or programming, You're asking them to build these automation ins So one they have to manage with the all the applications and the tools for all that happens. And to manage these automation is after business users have either left the company or moved on. So it is essential for them to think through and provide a streamline tools it on on two aspects. one it needs to be as as you started off, it needs to be an enabler to provide them the specific tools that they can, they have already blessed. They've curated it which are ready for business consumption. A second part I can also do is providing collaboration platforms so that business users can learn from each other and from it so that they can one are developing the right processes with the right methodology that is governed by I. T. And no security or data governance issues. Come through. >>One of the things that you mentioned in terms of the three roadblocks ceo uncovered was that you were surprised that the results of the research showed that in fact employees are really wanting to adopt automation. In fact I think the stat is um 86% of employees want automation but only 30% of leaders are giving them the opportunity to use that. That's a big gap. Why do you think that is >>so a few things. Right. I mean as we talked about the three constituents that you have right one is automation leaders. If you consider from them. Their view is their employees are not capable of adopting or building on the automation is using these tools and they need technical skills. But the all the automation vendors have made progress and if you look at the tools today are much more user friendly and business users are willing to adopt. The second part as we talked about is like the fear of job loss from the employee standpoint. Whereas employees are looking at it as an opportunity for them to up skill but also eliminate the pain points that they have today in the day to day activities using the automation tools. And for them it is like this is helping them spend the time with the customers where it matters on critical value added activities versus going through reparative process of the journey. And the third part we talked about earlier with I. T. I. T. Has this notion that they need to build and develop anything technical. Business users will not be able to build or manage and they're also worried about the governance, the security and the third part which you brought up earlier is that tool sprawl, It's like we need to manage like this volume of tools that are coming in which is only adding to their plate of already busy busy workforce. >>I have one of those. It depends questions and it's a good consultant I'm sure you say well it depends but are there patterns best practice or even more than best pressures? Are there sort of play books if you will? And patterns? I'm sure it's situational. But are you seeing patterns emerge, you can say okay this sort of category should approach it this way. Here's another one in a different, maybe it's a department bottoms up top down, can you help us sort of squint through that? >>Yeah. So in terms of approaches like at least up till now the prevalent thing that is happening is like C. O. Es went and buy some licenses they talk about like opportunities that they have. So it's more of a top down driven uh like ceo driven agenda. What we're seeing now especially with citizen automation or democratisation of automation is there's a new approach of including employees into the journey and bringing the bottoms up approach. So there's a happy path where you marry up the top down approach with bottoms up and one you will find opportunities which are organizational wide with the bu leaders and they are ones which are on the long tail of opportunities which employees feel the pain but I. T. Or C. O. He doesn't have the time to come and implement or automate these activities. Um considering like one part we have seen which is increasingly helpful for people who have done this properly is including employees. And one thing we talked yesterday is invest in employees. They consider automation as investment in employees rather than something they're doing to employees. So it's kind of collaborating with employees to make progress which seems to be helping evangelize and also benefit with automation. How >>Have the events of the last 18 months impacted this as well, we've seen so much acceleration and the mandate for automation. What are some of the things that you've seen? >>Sure. So for us like even before the pandemic we've seen in our research so like more than close to 50% of the organizations that they started the automation journey were unable to achieve the savings or targets that they set themselves for whatever the success factors are. Which which hard. A few reasons one they didn't have the organizational support, not they were taking the end to end journey or a customer journey to figure out like what are these big opportunities that they can go through and they haven't included employees and to figure out what are the major pain points to go through the journey. One thing it was clear was with covid, no one expected this kind of disruption in a pan and a pandemic. There are a lot of offshore centres or like pretty much different geography is got disconnected from the work that's being done. You still need to support your customers, there is still a higher demand, what do you do? It's not like you can scale up your employees in a pandemic, that's where like we have seen increasing push towards automation and technology to see that can help and support and scale in a pandemic environment uh and also help your customers in the journey. >>So has in your opinion has automation become a mandate? Uh As a result of the pandemic >>I would say. Yeah I I would consider it's more of like now it's become a I would say uh business won a competitive differentiator to say like one I needed to keep my lights on and resiliency but also the companies have done really well they saw the advantage and they whether the pandemic better with the customers now they use that as a platform to create a competitive differentiation against their peers and push things forward. >>one of the things we heard of today and the keynotes is you got to think about my words, the life cycle, you don't just put in the bot and then just leave it alone. You really have to think through that. And that seems to me to be where you would help customers think through how to get the most return out of their investment. You I passed product company I think it's great. And so you talk about the value layer that you guys bring. >>So for us it's it's like when we talked to mostly be bringing from the business side of the house to understand what are the key drivers that you need to work on. I mean even before we talk about technology, we talk about, let's understand from the customer standpoint what is your customer journey into end and look through that journey lens and let's take the process and to end, let's look at redesigning process and making it more optimal and streamlined and where technology fits in. That's when we talk about like if it is an RPG or if it's a UI Path platform that can support, let's go through that journey versus taking the tool itself as the solution and trying to find every nail that you can hurt, which usually is not sustainable to your point. Like we need to think through the whole life cycle, make sure this is going to last. Or if you are retiring. Like in the ceo panel that was a discussion where that we need to think through when we are going to retire and make sure like we are in that journey versus building all these automation zor bringing all these tools and leaving them alone for I. T. To manage long term. >>No. Again the last 18 months. Again, question about the the um reactions catalyzed facilitated thinking about those three roadblocks. The cognitive roadblocks the organizational roadblocks since particularly what I'm interested in this question and product, what are some of the conversations that you've seen or trends that you seem to help those organizations better understand how to collaborate with each other so that what they're not doing is putting in our P. A point tools but really starting to build the right part of the nomination and and journey into their digital transformation plans. Yeah. >>I mean in a way to again, I'll go back to the three concerns that we talked earlier, right? It's it can only go so far and automate so much because they haven't seen the business lens of like how the processes are what they have to do and to end, which is where you need to involve the business leaders who can give you that view from the business side and employees who are seeing the work day to day and where they can eliminate the pain points. So the organisms that are successful, they are creating a collaborative environment between the three groups to push things forward. You >>have to have that collaboration that's critical. Otherwise, that's probably one of the road blockers as well. >>Yeah, absolutely. >>Where does automation fit? I mean you're obviously heavily into automation, but let's think about the bane portfolio, the boardroom discussions. Where does automation fit? I mean there's security, there's how do we embed ai into our business? How do we sas if I our business um how do we do transform digitally? Where's automation fit in that hole discourse? >>So I think the automation is like at the heart of digital transformation, the part which we have seen where the gap is is not taking the business angle and actually thinking through the process and to end versus picking up a tool and trying to go solve a problem or find a problem to solve. And that's where we think in our discussions with boardrooms, it's more of let's think through how you want to reimagine your company or how you want to be more competitive looking into the future and like walk back from that standpoint and then started part from, I mean, the way we call it the future back like where you are today and now, like let's go forward and to what your end status and where technology broadly a digital tools and where automation fits in the process. >>How do you see what you i path is talking about at this conference? The announcements from yesterday? There's a lot of people here which is fantastic. How do you see what they're announcing? The vision that they set out a couple years ago that they're now delivering on. How is that a facilitator of organizations removing those roadblocks? Because as you said automation is a huge competitive differentiator these days and If we've learned nothing in the last 19 months you gotta you gotta be careful because there's always a competitor in the rear view mirror who might be smaller faster more agile ready to take your place. >>Yeah so like a few things that we've seen in the product roadmap that you talked about is they are providing the collaboration platform or tools where the I. T. Business owners can work through. Like for automation hub is what they talked at length yesterday is that's the platform where business users can provide their ideas. Like you provide process mining tools which can capture the process and the business users understand the process and they are the ones who are putting in an opportunity on the road map. So you have now a platform where all the ideas are being catalogued and once you implement they're being tracked on the automation hub so that that is providing a platform for everyone to collaborate together. The second one which Brandon talked yesterday is the tool itself for Studio X. When we're talking about citizen developers, employees trying to use and make it more user friendly. Is that where the Studio X which is providing that you are interface? Which is easy intuitive for business users to build basic automation is and try to take that long tail of opportunities that we talked about. So all these tools are coming together as one platform play, which you ipod has been talking about all through the conference and that is critical for everyone to collaborate to make a progress versus only thinking it's an easy job to implement the automation opportunities. That >>collaboration is business critical these days. Right. Thank you for joining David me and the program talking about some of the roadblocks that you've uncovered, but also some of the ways that organizations in any industry can navigate around them and really empower those employees who want automation in their jobs. We appreciate your insights. >>Happy to be here. Thanks for having us. You're welcome >>for day Volonte. I'm lisa martin live in las Vegas at UI Path forward for we'll be right back with our next guest. Yeah. >>Yeah. Mm. Mhm

>>text, you know, consumer opens up their iphone and says, oh my gosh, I love the technology behind my eyes. What's it been like being on the shark tank? You know, filming is fun, hang out, just fun and it's fun to be a celebrity at first your head gets really big and you get a good tables at restaurants who says texas has got a little possess more skin in the game today in charge of his destiny robert Hirschbeck, No stars. Here is CUBA alumni. Yeah, okay. >>Hi. I'm john Ferry, the co founder of silicon angle Media and co host of the cube. I've been in the tech business since I was 19 1st programming on many computers in a large enterprise and then worked at IBM and Hewlett Packard total of nine years in the enterprise brian's jobs from programming, Training, consulting and ultimately as an executive salesperson and then started my first company with 1997 and moved to Silicon Valley in 1999. I've been here ever since. I've always loved technology and I love covering you know, emerging technology as trained as a software developer and love business and I love the impact of software and technology to business to me creating technology that starts the company and creates value and jobs is probably the most rewarding things I've ever been involved in. And I bring that energy to the queue because the Cubans were all the ideas are and what the experts are, where the people are and I think what's most exciting about the cube is that we get to talk to people who are making things happen, entrepreneur ceo of companies, venture capitalists, people who are really on a day in and day out basis, building great companies and the technology business is just not a lot of real time live tv coverage and, and the cube is a non linear tv operation. We do everything that the T. V guys on cable don't do. We do longer interviews. We asked tougher questions, we ask sometimes some light questions. We talked about the person and what they feel about. It's not prompted and scripted. It's a conversation authentic And for shows that have the Cube coverage and makes the show buzz. That creates excitement. More importantly, it creates great content, great digital assets that can be shared instantaneously to the world. Over 31 million people have viewed the cube and that is the result. Great content, great conversations and I'm so proud to be part of you with great team. Hi, I'm john ferrier. Thanks for watching the cube. >>Hello and welcome to the cube. We are here live on the ground in the expo floor of a live event. The AWS public sector summit. I'm john for your host of the cube. We're here for the next two days. Wall to wall coverage. I'm here with Sandy carter to kick off the event. Vice president partner as partners on AWS public sector. Great to see you Sandy, >>so great to see you john live and in person, right? >>I'm excited. I'm jumping out of my chair because I did a, I did a twitter periscope yesterday and said a live event and all the comments are, oh my God, an expo floor a real events. Congratulations. >>True. Yeah. We're so excited yesterday. We had our partner day and we sold out the event. It was rock them and pack them and we had to turn people away. So what a great experience. Right, >>Well, I'm excited. People are actually happy. We tried, we tried covering mobile world congress in Barcelona. Still, people were there, people felt good here at same vibe. People are excited to be in person. You get all your partners here. You guys have had had an amazing year. Congratulations. We did a couple awards show with you guys. But I think the big story is the amazon services for the partners. Public sector has been a real game changer. I mean we talked about it before, but again, it continues to happen. What's the update? >>Yeah, well we had, so there's lots of announcements. So let me start out with some really cool growth things because I know you're a big growth guy. So we announced here at the conference yesterday that our government competency program for partners is now the number one industry in AWS for are the competency. That's a huge deal. Government is growing so fast. We saw that during the pandemic, everybody was moving to the cloud and it's just affirmation with the government competency now taking that number one position across AWS. So not across public sector across AWS and then one of our fastest growing areas as well as health care. So we now have an A. T. O. Authority to operate for HIPPA and Hi trust and that's now our fastest growing area with 85% growth. So I love that new news about the growth that we're seeing in public sector and all the energy that's going into the cloud and beyond. >>You know, one of the things that we talked about before and another Cuban of you. But I want to get your reaction now current state of the art now in the moment the pandemic has highlighted the antiquated outdated systems and highlighted help inadequate. They are cloud. You guys have done an amazing job to stand up value quickly now we're in a hybrid world. So you've got hybrid automation ai driving a complete change and it's happening pretty quick. What's the new things that you guys are seeing that's emerging? Obviously a steady state of more growth. But what's the big success programs that you're seeing right now? >>Well, there's a few new programs that we're seeing that have really taken off. So one is called proserve ready. We announced yesterday that it's now G. A. And the U. S. And a media and why that's so important is that our proserve team a lot of times when they're doing contracts, they run out of resources and so they need to tap on the shoulder some partners to come and help them. And the customers told us that they wanted them to be pro served ready so to have that badge of honor if you would that they're using the same template, the same best practices that we use as well. And so we're seeing that as a big value creator for our partners, but also for our customers because now those partners are being trained by us and really helping to be mentored on the job training as they go. Very powerful program. >>Well, one of the things that really impressed by and I've talked to some of your MSP partners on the floor here as they walk by, they see the cube, they're all doing well. They're all happy. They got a spring in their step. And the thing is that this public private partnerships is a real trend we've been talking about for a while. More people in the public sector saying, hey, I want I need a commercial relationship, not the old school, you know, we're public. We have all these rules. There's more collaboration. Can you share your thoughts on how you see that evolving? Because now the partners in the public sector are partnering closer than ever before. >>Yeah, it's really um, I think it's really fascinating because a lot of our new partners are actually commercial partners that are now choosing to add a public sector practice with them. And I think a lot of that is because of these public and private partnerships. So let me give you an example space. So we were at the space symposium our first time ever for a W. S at the space symposium and what we found was there were partners, they're like orbital insight who's bringing data from satellites, There are public sector partner, but that data is being used for insurance companies being used for agriculture being used to impact environment. So I think a lot of those public private partnerships are strengthening as we go through Covid or have like getting alec of it. And we do see a lot of push in that area. >>Talk about health care because health care is again changing radically. We talked to customers all the time. They're like, they have a lot of legacy systems but they can't just throw them away. So cloud native aligns well with health care. >>It does. And in fact, you know, if you think about health care, most health care, they don't build solutions themselves, they depend on partners to build them. So they do the customer doesn't buy and the partner does the build. So it's a great and exciting area for our partners. We just launched a new program called the mission accelerator program. It's in beta and that program is really fascinating because our healthcare partners, our government partners and more now can use these accelerators that maybe isolate a common area like um digital analytics for health care and they can reuse those. So it's pretty, I think it's really exciting today as we think about the potential health care and beyond. >>You know, one of the challenge that I always thought you had that you guys do a good job on, I'd love to get your reaction to now is there's more and more people who want to partner with you than ever before. And sometimes it hasn't always been easy in the old days like to get fed ramp certified or even deal with public sector. If you were a commercial vendor, you guys have done a lot with accelerating certifications. Where are you on that spectrum now, what's next? What's the next wave of partner onboarding or what's the partner trends around the opportunities in public sector? >>Well, one of the new things that we announced, we have tested out in the U. S. You know, that's the amazon way, right, Andy's way, you tested your experiment. If it works, you roll it out, we have a concierge program now to help a lot of those new partners get inundated into public sector. And so it's basically, I'm gonna hold your hand just like at a hotel. I would go up and say, hey, can you direct me to the right restaurant or to the right museum, we do the same thing, we hand hold people through that process. Um, if you don't want to do that, we also have a new program called navigate which is built for brand new partners. And what that enables our partners to do is to kind of be guided through that process. So you are right. We have so many partners now who want to come and grow with us that it's really essential that we provide a great partner, experienced a how to on board. >>Yeah. And the A. P. M. Was the amazon partner network also has a lot of crossover. You see a lot a lot of that going on because the cloud, it's you can do both. >>Absolutely. And I think it's really, you know, we leverage all of the ap in programs that exist today. So for example, there was just a new program that was put out for a growth rebate and that was driven by the A. P. N. And we're leveraging and using that in public sector too. So there's a lot of prosecutes going on to make it easier for our partners to do business with us. >>So I have to ask you on a personal note, I know we've talked about before, your very comfortable the virtual now hybrid space. How's your team doing? How's the structure looks like, what are your goals, what are you excited about? >>Well, I think I have the greatest team ever. So of course I'm excited about our team and we are working in this new hybrid world. So it is a change for everybody uh the other day we had some people in the office and some people calling in virtually so how to manage that, right was really quite interesting. Our goals that we align our whole team around and we talked a little bit about this yesterday are around mission which are the solution areas migration, so getting everything to the cloud and then in the cloud, we talk about modernization, are you gonna use Ai Ml or I O T? And we actually just announced a new program around that to to help out IOT partners to really build and understand that data that's coming in from I O T I D C says that that idea that IOT data has increased by four times uh in the, during the covid period. So there's so many more partners who need help. >>There's a huge shift going on and you know, we always try to explain on the cube. Dave and I talked about a lot and it's re platform with the cloud, which is not just lift and shift you kind of move and then re platform then re factoring your business and there's a nuance there between re platform in which is great. Take advantage of cloud scale. But the re factoring allows for this unique advantage of these high level services. >>That's right >>and this is where people are winning. What's your reaction to that? >>Oh, I completely agree. I think this whole area of modernizing your application, like we have a lot of folks who are doing mainframe migrations and to your point if they just lift what they had in COBOL and they move it to a W S, there's really not a lot of value there, but when they rewrite the code, when they re factor the code, that's where we're seeing tremendous breakthrough momentum with our partner community, you know, Deloitte is one of our top partners with our mainframe migration. They have both our technology and our consulting um, mainframe migration competency there to one of the other things I think you would be interested in is in our session yesterday we just completed some research with r C T O s and we talked about the next mega trends that are coming around Web three dato. And I'm sure you've been hearing a lot about web www dot right? Yeah, >>0.04.0, it's all moving too fast. I mean it's moving >>fast. And so some of the things we talked to our partners about yesterday are like the metaverse that's coming. So you talked about health care yesterday electronic caregiver announced an entire application for virtual caregivers in the metaverse. We talked about Blockchain, you know, and the rise of Blockchain yesterday, we had a whole set of meetings, everybody was talking about Blockchain because now you've got El Salvador Panama Ukraine who have all adopted Bitcoin which is built on the Blockchain. So there are some really exciting things going on in technology and public sector. >>It's a societal shift and I think the confluence of tech user experience data, new, decentralized ways of changing society. You're in the middle of it. >>We are and our partners are in the middle of it and data data, data data, that's what I would say. Everybody is using data. You and I even talked about how you guys are using data. Data is really a hot topic and we we're really trying to help our partners figure out just how to migrate the data to the cloud but also to use that analytics and machine learning on it too. Well, >>thanks for sharing the data here on our opening segment. The insights we will be getting out of the Great Sandy. Great to see you got a couple more interviews with you. Thanks for coming on. I appreciate you And thanks for all your support. You guys are doing great. Your partners are happy you're on a great wave. Congratulations. Thank you, john appreciate more coverage from the queue here. Neither is public sector summit. We'll be right back. Mhm Yeah. >>Mhm. Mhm robert Herjavec. People obviously know you from shark tank

>>mhm Yes. >>Welcome back to the Cube coverage of Red Hat summit 21 2021. I'm john for host of the Cubans virtual this year as we start preparing to come out of Covid a lot of great conversations here happening around technology. This is the emerging technology with Red hat segment. We've got three great guests steve watt manager, distinguished engineer at Red Hat hurl saying senior software engineer Red Hat and luke Hines, who's the senior software engineer as well. We got the engineering team steve, you're the the team leader, emerging tech within red hat. Always something to talk about. You guys have great tech chops that's well known in the industry and I'll see now part of IBM you've got a deep bench um what's your, how do you view emerging tech um how do you apply it? How do you prioritize, give us a quick overview of the emerging tech scene at Redhead? >>Yeah, sure. It's quite a conflated term. The way we define emerging technologies is that it's a technology that's typically 18 months plus out from commercialization and this can sometimes go six months either way. Another thing about it is it's typically not something on any of our product roadmaps within the portfolio. So in some sense, it's often a bit of a surprise that we have to react to. >>So no real agenda. And I mean you have some business unit kind of probably uh but you have to have first principles within red hat, but for this you're looking at kind of the moon shot, so to speak, the big game changing shifts. Quantum, you know, you got now supply chain from everything from new economics, new technology because that kind of getting it right. >>Yeah, I think we we definitely use a couple of different techniques to prioritize and filter what we're doing. And the first is something will pop up and it will be like, is it in our addressable market? So our addressable market is that we're a platform software company that builds enterprise software and so, you know, it's got to be sort of fit into that is a great example if somebody came up came to us with an idea for like a drone command center, which is a military application, it is an emerging technology, but it's something that we would pass on. >>Yeah, I mean I didn't make sense, but he also, what's interesting is that you guys have an open source D N A. So it's you have also a huge commercial impact and again, open sources of one of the 4th, 5th generation of awesomeness. So, you know, the good news is open source is well proven. But as you start getting into this more disruption, you've got the confluence of, you know, core cloud, cloud Native, industrial and IOT edge and data. All this is interesting, right. This is where the action is. How do you guys bring that open source community participation? You got more stakeholders emerging there before the break down, how that you guys manage all that complexity? >>Yeah, sure. So I think that the way I would start is that, you know, we like to act on good ideas, but I don't think good ideas come from any one place. And so we typically organize our teams around sort of horizontal technology sectors. So you've got, you know, luke who's heading up security, but I have an edge team, cloud networking team, a cloud storage team. Cloud application platforms team. So we've got these sort of different areas that we sort of attack work and opportunities, but you know, the good ideas can come from a variety of different places. So we try and leverage co creation with our customers and our partners. So as a good example of something we had to react to a few years ago, it was K Native right? So the sort of a new way of doing service um and eventing on top of kubernetes that was originated from google. Whereas if you look at Quantum right, ibms, the actual driver on quantum science and uh that originated from IBM were parole. We'll talk about exactly how we chose to respond to that. Some things are originated organically within the team. So uh luke talking about six law is a great example of that, but we do have a we sort of use the addressable market as a way to sort of focus what we're doing and then we try and land it within our different emerging technologies teams to go tackle it. Now. You asked about open source communities, which are quite interesting. Um so typically when you look at an open source project, it's it's there to tackle a particular problem or opportunity. Sometimes what you actually need commercial vendors to do is when there's a problem or opportunity that's not tackled by anyone open source project, we have to put them together to create a solution to go tackle that thing. That's also what we do. And so we sort of create this bridge between red hat and our customers and multiple different open source projects. And this is something we have to do because sometimes just that one open source project doesn't really care that much about that particular problem. They're motivated elsewhere. And so we sort of create that bridge. >>We got two great uh cohorts here and colleagues parole on the on the Quantum side and you got luke on the security side. Pro I'll start with you. Quantum is also a huge mentioned IBM great leadership there. Um Quantum on open shift. I mean come on. Just that's not coming together for me in my mind, it's not the first thing I think of. But it really that sounds compelling. Take us through, you know, um how this changes the computing landscape because heterogeneous systems is what we want and that's the world we live in. But now with distributed systems and all kinds of new computing modules out there, how does this makes sense? Take us through this? >>Um yeah john's but before I think I want to explain something which is called Quantum supremacy because it plays very important role in the road map that's been working on. So uh content computers, they are evolving and they have been around. But right now you see that they are going to be the next thing. And we define quantum supremacy as let's say you have any program that you run or any problems that you solve on a classical computer. Quantum computer would be giving you the results faster. So that is uh, that is how we define content supremacy when the same workload are doing better on content computer than they do in a classical computer. So the whole the whole drive is all the applications are all the companies, they're trying to find avenues where Quantum supremacy are going to change how they solve problems or how they run their applications. And even though quantum computers they are there. But uh, it is not as easily accessible for everyone to consume because it's it's a very new area that's being formed. So what, what we were thinking, how we can provide a mechanism that you can you don't connect this deal was you have a classical world, you have a country world and that's where a lot of thought process been. And we said okay, so with open shift we have the best of the classical components. You can take open shift, you can develop, deploy around your application in a country raised platform. What about you provide a mechanism that the world clothes that are running on open shift. They are also consuming quantum resources or they are able to run the competition and content computers take the results and integrate them in their normal classical work clothes. So that is the whole uh that was the whole inception that we have and that's what brought us here. So we took an operator based approach and what we are trying to do is establish the best practices that you can have these heterogeneous applications that can have classical components. Talking to our interacting the results are exchanging data with the quantum components. >>So I gotta ask with the rise of containers now, kubernetes at the center of the cloud native value proposition, what work clothes do you see benefiting from the quantum systems the most? Is there uh you guys have any visibility on some of those workloads? >>Uh So again, it's it's a very new, it's very it's really very early in the time and uh we talk with our customers and every customers, they are trying to identify themselves first where uh these contacts supremacy will be playing the role. What we are trying to do is when they reach their we should have a solution that they that they could uh use the existing in front that they have on open shift and use it to consume the content computers that may or may not be uh, inside their own uh, cloud. >>Well I want to come back and ask you some of the impact on the landscape. I want to get the look real quick because you know, I think security quantum break security, potentially some people have been saying, but you guys are also looking at a bunch of projects around supply chain, which is a huge issue when it comes to the landscape, whether its components on a machine in space to actually handling, you know, data on a corporate database. You guys have sig store. What's this about? >>Sure. Yes. So sick store a good way to frame six store is to think of let's encrypt and what let's encrypt did for website encryption is what we plan to do for software signing and transparency. So six Door itself is an umbrella organization that contains various different open source projects that are developed by the Six door community. Now, six door will be brought forth as a public good nonprofit service. So again, we're very much basing this on the successful model of let's Encrypt Six door will will enable developers to sign software artifacts, building materials, containers, binaries, all of these different artifacts that are part of the software supply chain. These can be signed with six door and then these signing events are recorded into a technology that we call a transparency log, which means that anybody can monitor signing events and a transparency log has this nature of being read only and immutable. It's very similar to a Blockchain allows you to have cryptographic proof auditing of our software supply chain and we've made six stores so that it's easy to adopt because traditional cryptographic signing tools are a challenge for a lot of developers to implement in their open source projects. They have to think about how to store the private keys. Do they need specialist hardware? If they were to lose a key then cleaning up afterwards the blast radius. So the key compromise can be incredibly difficult. So six doors role and purpose essentially is to make signing easy easy to adopt my projects. And then they have the protections around there being a public transparency law that could be monitored. >>See this is all about open. Being more open. Makes it more secure. Is the >>thief? Very much yes. Yes. It's that security principle of the more eyes on the code the better. >>So let me just back up, is this an open, you said it's gonna be a nonprofit? >>That's correct. Yes. Yes. So >>all of the code is developed by the community. It's all open source. anybody can look at this code. And then we plan alongside the Linux Foundation to launch a public good service. So this will make it available for anybody to use if your nonprofit free to use service. >>So luke maybe steve if you can way into on this. I mean, this goes back. If you look back at some of the early cloud days, people were really trashing cloud as there's no security. And cloud turns out it's a more security now with cloud uh, given the complexity and scale of it, does that apply the same here? Because I feel this is a similar kind of concept where it's open, but yet the more open it is, the more secure it is. And then and then might have to be a better fit for saying I. T. Security solution because right now everyone is scrambling on the I. T. Side. Um whether it's zero Trust or Endpoint Protection, everyone's kind of trying everything in sight. This is kind of changing the paradigm a little bit on software security. Could you comment on how you see this playing out in traditional enterprises? Because if this plays out like the cloud, open winds, >>so luke, why don't you take that? And then I'll follow up with another lens on it which is the operate first piece. >>Sure. Yes. So I think in a lot of ways this has to be open this technology because this way we have we have transparency. The code can be audited openly. Okay. Our operational procedures can be audit openly and the community can help to develop not only are code but our operational mechanisms so we look to use technology such as cuba netease, open ship operators and so forth. Uh Six store itself runs completely in a cloud. It is it is cloud native. Okay, so it's very much in the paradigm of cloud and yeah, essentially security, always it operates better when it's open, you know, I found that from looking at all aspects of security over the years that I've worked in this realm. >>Okay, so just just to add to that some some other context around Six Law, that's interesting, which is, you know, software secure supply chain, Sixth floor is a solution to help build more secure software secure supply chains, more secure software supply chain. And um so um there's there's a growing community around that and there's an ecosystem of sort of cloud native kubernetes centric approaches for building more secure software. I think we all caught the solar winds attack. It's sort of enterprise software industry is responding sort of as a whole to go and close out as many of those gaps as possible, reduce the attack surface. So that's one aspect about why 6th was so interesting. Another thing is how we're going about it. So we talked about um you mentioned some of the things that people like about open source, which is one is transparency, so sunlight is the best disinfectant, right? Everybody can see the code, we can kind of make it more secure. Um and then the other is agency where basically if you're waiting on a vendor to go do something, um if it's proprietary software, you you really don't have much agency to get that vendor to go do that thing. Where is the open source? If you don't, if you're tired of waiting around, you can just submit the patch. So, um what we've seen with package software is with open source, we've had all this transparency and agency, but we've lost it with software as a service, right? Where vendors or cloud service providers are taking package software and then they're making it available as a service but that operationalize ng that software that is proprietary and it doesn't get contributed back. And so what Lukes building here as long along with our partners down, Lawrence from google, very active contributor in it. Um, the, is the operational piece to actually run sixth or as a public service is part of the open source project so people can then go and take sixth or maybe run it as a smaller internal service. Maybe they discover a bug, they can fix that bug contributed back to the operational izing piece as well as the traditional package software to basically make it a much more robust and open service. So you bring that transparency and the agency back to the SAS model as well. >>Look if you don't mind before, before uh and this segment proportion of it. The importance of immune ability is huge in the world of data. Can you share more on that? Because you're seeing that as a key part of the Blockchain for instance, having this ability to have immune ability. Because you know, people worry about, you know, how things progress in this distributed world. You know, whether from a hacking standpoint or tracking changes, Mutability becomes super important and how it's going to be preserved in this uh new six doorway. >>Oh yeah, so um mutability essentially means cannot be changed. So the structure of something is set. If it is anyway tampered or changed, then it breaks the cryptographic structure that we have of our public transparency service. So this way anybody can effectively recreate the cryptographic structure that we have of this public transparency service. So this mutability provides trust that there is non repudiation of the data that you're getting. This data is data that you can trust because it's built upon a cryptographic foundation. So it has very much similar parallels to Blockchain. You can trust Blockchain because of the immutable nature of it. And there is some consensus as well. Anybody can effectively download the Blockchain and run it themselves and compute that the integrity of that system can be trusted because of this immutable nature. So that's why we made this an inherent part of Six door is so that anybody can publicly audit these events and data sets to establish that there tamper free. >>That is a huge point. I think one of the things beyond just the security aspect of being hacked and protecting assets um trust is a huge part of our society now, not just on data but everything, anything that's reputable, whether it's videos like this being deep faked or you know, or news or any information, all this ties to security again, fundamentally and amazing concepts. Um I really want to keep an eye on this great work. Um Pearl, I gotta get back to you on Quantum because again, you can't, I mean people love Quantum. It's just it feels like so sci fi and it's like almost right here, right, so close and it's happening. Um And then people get always, what does that mean for security? We go back to look and ask them well quantum, you know, crypto But before we get started I wanted, I'm curious about how that's gonna play out from the project because is it going to be more part of like a C. N. C. F. How do you bring the open source vibe to Quantum? >>Uh so that's a very good question because that was a plan, the whole work that we are going to do related to operators to enable Quantum is managed by the open source community and that project lies in the casket. So casket has their own open source community and all the modification by the way, I should first tell you what excuse did so cute skin is the dedicate that you use to develop circuits that are run on IBM or Honeywell back in. So there are certain Quantum computers back and that support uh, circuits that are created using uh Houston S ticket, which is an open source as well. So there is already a community around this which is the casket. Open source community and we have pushed the code and all the maintenance is taken care of by that community. Do answer your question about if we are going to integrate it with C and C. F. That is not in the picture right now. We are, it has a place in its own community and it is also very niche to people who are working on the Quantum. So right now you have like uh the contributors who who are from IBM as well as other uh communities that are specific specifically working on content. So right now I don't think so, we have the map to integrated the C. N. C. F. But open source is the way to go and we are on that tragic Torri >>you know, we joke here the cube that a cubit is coming around the corner can can help but we've that in you know different with a C. But um look, I want to ask you one of the things that while you're here your security guru. I wanted to ask you about Quantum because a lot of people are scared that Quantum is gonna crack all the keys on on encryption with his power and more hacking. You're just comment on that. What's your what's your reaction to >>that? Yes that's an incredibly good question. This will occur. Okay. And I think it's really about preparation more than anything now. One of the things that we there's a principle that we have within the security world when it comes to coding and designing of software and this aspect of future Cryptography being broken. As we've seen with the likes of MD five and Sha one and so forth. So we call this algorithm agility. So this means that when you write your code and you design your systems you make them conducive to being able to easily swap and pivot the algorithms that use. So the encryption algorithms that you have within your code, you do not become too fixed to those. So that if as computing gets more powerful and the current sets of algorithms are shown to have inherent security weaknesses, you can easily migrate and pivot to a stronger algorithms. So that's imperative. Lee is that when you build code, you practice this principle of algorithm agility so that when shot 256 or shot 5 12 becomes the shar one. You can swap out your systems. You can change the code in a very least disruptive way to allow you to address that floor within your within your code in your software projects. >>You know, luke. This is mind bender right there. Because you start thinking about what this means is when you think about algorithmic agility, you start thinking okay software countermeasures automation. You start thinking about these kinds of new trends where you need to have that kind of signature capability. You mentioned with this this project you're mentioning. So the ability to actually who signs off on these, this comes back down to the paradigm that you guys are talking about here. >>Yes, very much so. There's another analogy from the security world, they call it turtles all the way down, which is effectively you always have to get to the point that a human or a computer establishes that first point of trust to sign something off. And so so it is it's a it's a world that is ever increasing in complexity. So the best that you can do is to be prepared to be as open as you can to make that pivot as and when you need to. >>Pretty impressive, great insight steve. We can talk for hours on this panel, emerging tech with red hat. Just give us a quick summary of what's going on. Obviously you've got a serious brain trust going on over there. Real world impact. You talk about the future of trust, future of software, future of computing, all kind of going on real time right now. This is not so much R and D as it is the front range of tech. Give us a quick overview of >>Yeah, sure, yeah, sure. The first thing I would tell everyone is go check out next that red hat dot com, that's got all of our different projects, who to contact if you're interested in learning more about different areas that we're working on. And it also lists out the different areas that we're working on, but just as an overview. So we're working on software defined storage, cloud storage. Sage. Well, the creator of Cf is the person that leads that group. We've got a team focused on edge computing. They're doing some really cool projects around um very lightweight operating systems that and kubernetes, you know, open shift based deployments that can run on, you know, devices that you screw into the sheet rock, you know, for that's that's really interesting. Um We have a cloud networking team that's looking at over yin and just intersection of E B P F and networking and kubernetes. Um and then uh you know, we've got an application platforms team that's looking at Quantum, but also sort of how to advance kubernetes itself. So that's that's the team where you got the persistent volume framework from in kubernetes and that added block storage and object storage to kubernetes. So there's a lot of really exciting things going on. Our charter is to inform red hats long term technology strategy. We work the way my personal philosophy about how we do that is that Red hat has product engineering focuses on their product roadmap, which is by nature, you know, the 6 to 9 months. And then the longer term strategy is set by both of us. And it's just that they're not focused on it. We're focused on it and we spend a lot of time doing disambiguate nation of the future and that's kind of what we do. We love doing it. I get to work with all these really super smart people. It's a fun job. >>Well, great insights is super exciting, emerging tack within red hat. I'll see the industry. You guys are agile, your open source and now more than ever open sources, uh, product Ization of open source is happening at such an accelerated rate steve. Thanks for coming on parole. Thanks for coming on luke. Great insight all around. Thanks for sharing. Uh, the content here. Thank you. >>Our pleasure. >>Thank you. >>Okay. We were more, more redhead coverage after this. This video. Obviously, emerging tech is huge. Watch some of the game changing action here at Redhead Summit. I'm john ferrier. Thanks for watching. Yeah.

>>on the globe. It's the Cube with digital coverage of AWS reinvent 2020 sponsored by Intel, AWS and our community partners. Hello and welcome back to the Cubes Live coverage Cube live here in Palo Alto, California, with the Virtual Cube this year because we can't be there in person. I'm your host, John Fairy year. We're kicking off Day two of the three weeks of reinvent a lot of great leadership sessions to review, obviously still buzzing from the Andy Jassy three. Our keynote, which had so many storylines, is really hard to impact. We're gonna dig that into into into that today with Jerry Chan, who has been a Cube alumni since the beginning of our AWS coverage. Going back to 2013, Jerry was wandering the hallways as a um, in between. You were in between vm ware and V C. And then we saw you there. You've been on the Cube every year at reinvent with us. So special commentary from you. Thanks for coming on. >>Hey, John, Thanks for having me and a belated happy birthday as well. If everyone out there John's birthday was yesterday. So and hardest. Howard's working man in technology he spent his entire birthday doing live coverage of Amazon re events. Happy birthday, buddy. >>Well, I love my work. I love doing this. And reinvent is the biggest event of the year because it really is. It's become a bellwether and eso super excited to have you on. We've had great conversations by looking back at our conversations over the Thanksgiving weekend. Jerry, the stuff we were talking about it was very proposed that Jassy is leaning in with this whole messaging around change and horizontal scalability. He didn't really say that, but he was saying you could disrupt in these industries and still use machine learning. This was some of the early conversations we were having on the Cube. Now fast forward, more mainstream than ever before. So big, big part of the theme there. >>Yeah, it z you Amazon reinvent Amazon evolution to your point, right, because it's both reinventing what countries are using with the cloud. But also what Amazon's done is is they're evolving year after year with their services. So they start a simple infrastructure, you know, s three and e c. Two. And now they're building basically a lot of what Andy said you actually deconstructed crm? Ah, lot of stuff they're doing around the call centers, almost going after Salesforce with kind of a deconstructed CRM services, which is super interesting. But the day you know, Amazon announces all those technologies, not to mention the AI stuff, the seminar stuff you have slack and inquired by Salesforce for $27.7 billion. So ah, lot of stuff going on in the cloud world these days, and it's funny part of it, >>you know, it really is interesting. You look up the slack acquisition by, um, by Salesforce. It's interesting, you know, That kind of takes slack out of the play here. I mean, they were doing really well again. Message board service turns into, um, or collaboration software. They hit the mainstream. They have great revenue. Is that going to really change the landscape of the industry for Salesforce? They've got to acquire it. It opens the door up from, or innovation. And it's funny you mention the contact Center because I was pressing Jassy on my exclusive one on one with him. Like they said, Andy, my my daughter and my sons, they don't use the phone. They're not gonna call. What's this? Is it a call center deal? And he goes, No, it's the It's about the contact. So think about that notion of the contact. It's not about the call center. It's the point of contact. Okay, Linked in is with Microsoft. You got slack and Salesforce Contact driven collaboration. Interesting kind of play for Microsoft to use voice and their data. What's your take on that? >>I think it's, um you know, I have this framework. As you know, I talked my friend systems of engagement over systems intelligence and systems record. Right? And so you could argue voice email slack because we're all different systems of engagement, and they sit on top of system of record like CRM customer support ticketing HR. Something like that. Now what sells first did by buying slack is they now own a system engagement, right? Not on Lee is slack. A system engagement for CRM, but also system engagement for E. R. P Service. Now is how you interact with a bunch of applications. And so if you think about sales for strategy in the space, compete against Marcus Soft or serves now or other large AARP's now they own slack of system engagement, that super powerful way to actually compete against rival SAS companies. Because if you own the layer engagement layer, you can now just intermediate what's in the background. Likewise, the context center its own voice. Email, chat messaging, right? You can just inter mediate this stuff in the back, and so they're trying to own the system engagement. And then, likewise, Facebook just bought that company customer a week ago for a billion dollars, which also Omni Channel support because it is chat messaging voice. It's again the system engagement between End User, which could be a customer or could be employees. >>You know, this really gonna make Cit's enterprise has been so much fun over the past 10 years, I gotta say, in the past five, you know, it's been even more fun, has become or the new fun area, you know, And the impact to enterprise has been interesting because and we're talking about just engaging system of record. This is now the new challenge for the enterprise. So I wanna get your thoughts, Jerry, because how you see the Sea, X O's and CSOs and the architects out there trying to reinvent the enterprise. Jassy saying Look and find the truth. Be on the right side of history here. Certainly he's got himself service interest there, but there is a true band eight with Cove it and with digital acceleration for the enterprise to change. Um, given all these new opportunities Thio, revolutionize or disrupt or radically improve, what's the C. C X's do? What's your take on? How do you see that? >>It's increasingly messy for the CXS, and I don't I don't envy them, right? Because back in the day they kind of controlled all the I t spend and kind of they had a standard of what technologies they use in the company. And then along came Amazon in cloud all of sudden, like your developers and Dio Hey, let me swipe my credit card and I'm gonna access to a bunch of a P I s around computing stories. Likewise. Now they could swipe the credit card and you strike for billing, right? There's a whole bunch of services now, so it becomes incumbent upon CSOs. They need Thio new set of management tools, right? So not only just like, um, security tools they need, they need also observe ability, tools, understanding what services are being used by the customers, when and how. And I would say the following John like CSOs is both a challenge for them. But I think if I was a C X, so I'll be pretty excited because now I have a bunch of other weapons and other bunch of services I could offer. My end users, my developers, my employees, my customers and, you know it's exciting for them is not only could they do different things, but they also changed how their business being done. And so I think both interact with their end users. Be a chat like slack or be a phone like a contact center or instagram for your for your for your kids. It's actually a new challenge if I were sick. So it's it's time to build again, you know, I think Cove it has said it is time to build again. You can build >>to kind of take that phrase from the movie Shawshank Redemption. Get busy building or get busy dying. Kinda rephrase it there. And that's kind of the theme I'm seeing here because covert kind of forced people saying, Look, this things like work at home. Who would have thought 100% people would be working at home? Who would have thought that now the workloads gonna change differently? So it's an opportunity to deconstruct or distant intermediate these services. And I think, you know, in all the trends that I've seen over my career, it's been those inflection points where breaking the monolith or breaking the proprietary piece of it has always been an opportunity for for entrepreneur. So you know, and and for companies, whether you're CEO or startup by decomposing and you can come in and create value E I think to me, snowflake going public on the back of Amazon. Basically, this is interesting. I mean, so you don't have to be. You could kill one feature and nail it and go big. >>I think we talked to the past like it's Amazon or Google or Microsoft Gonna win. Everything is winner take all winner take most, and you could argue that it's hard to find oxygen as a start up in a broad platform play. But we think Snowflake and other companies have done and comes like mongo DB, for example, elastic have shown that if you can pick a service or a problem space and either developed like I p. That's super deep or own developer audience. You can actually fight the big guys. The Big Three cloud vendors be Amazon, Google or or market soft in different markets. And I think if you're a startup founder, you should not be afraid of competing with the big cloud vendors because there there are success patterns and how you can win and you know and create a lot of value. So I have found Investor. I'm super excited by that because, you know, I don't think you're gonna find a company takedown Amazon completely because they're just the scale and the network effects is too large. But you can create a lot of value and build Valuable comes like snowflake in and around the Amazon. Google Microsoft Ecosystem. >>Yeah, I want to get your thoughts. You have one portfolio we've covered rock rock set, which does a lot of sequel. Um, one of your investments. Interesting part of the Kino yesterday was Andy Jassy kind of going after Microsoft saying Windows sequel server um, they're targeting that with this new, uh, tool, but, you know, sucks in the database of it is called the Babel Fish for Aurora for post Chris sequel. Um, well, how was your take on that? I mean, obviously Microsoft big. Their enterprise sales tactics are looking like more like Oracle, which he was kind of hinting at and commenting on. But sequel is Lingua Franca for data >>correct. I think we went to, like, kind of a no sequel phase, which was kind of a trendy thing for a while and that no sequel still around, not only sequel like mongo DB Document TV. Kind of that interface still holds true, but your point. The world speaks sequel. All your applications be sequel, right? So if you want backwards, compatibility to your applications speaks equal. If you want your tire installed base of employees that no sequel, we gotta speak sequel. So, Rock said, when the first public conversations about what they're building was on on the key with you and Me and vent hat, the founder. And what Rock said is doing their building real time. Snowflake Thio, Lack of better term. It's a real time sequel database in the cloud that's super elastic, just like Snowflake is. But unlike snowflake, which is a data warehouse mostly for dashboards and analytics. Rock set is like millisecond queries for real time applications, and so think of them is the evolution of where cloud databases air going is not only elastic like snowflake in the cloud like Snowflake. We're talking 10 15 millisecond queries versus one or two second queries, and I think what any Jassy did and Amazon with bowel officials say, Hey, Sequels, Legal frank of the cloud. There's a large installed base of sequel server developers out there and applications, and we're gonna use Babel fish to kind of move those applications from on premise the cloud or from old workload to the new workloads. And, I think, the name of the game. For for cloud vendors across the board, big and small startups thio Google markets, often Amazon is how do you reduce friction like, How do you reduce friction to try a new service to get your data in the cloud to move your data from one place to the next? And so you know, Amazon is trying to reduce friction by using Babel fish, and I think it is a great move by them. >>Yeah, by the way. Not only is it for Aurora Post Chris equal, they're also open sourcing it. So that's gonna be something that is gonna be interesting to play out. Because once they open source it essentially, that's an escape valve for locking. I mean, if you're a Microsoft customer, I mean, it ultimately is. Could be that Gateway drug. It's like it is ultimately like, Hey, if you don't like the licensing, come here. Now there's gonna be some questions on the translations. Um, Vince, um, scuttlebutt about that. But we'll see it's open source. We'll see what goes on. Um great stuff on on rocks that great. Great. Start up next. Next, uh, talk track I wanna get with you is You know, over the years, you know, we've talked about your history. We're gonna vm Where, uh, now being a venture capitalist. Successful, wanted Greylock. You've seen the waves, and I would call it the two ways pre cloud Early days of cloud. And now, with co vid, we're kind of in the, you know, not just born in the cloud Total cloud scale cloud operations. This is kind of what jazz he was going after. E think I tweeted Cloud is eating the world and on premise and the edges. What it's hungry for. It kind of goof on mark injuries since quote a software eating the world. This is where it's going. So it's a whole another chapter coming. You saw the pre cloud you saw Cloud. Now we've got basically global I t everything else >>It's cloud only I would say, You know, we saw pre cloud right the VM ware days and before that he called like, you know, data centers. I would say Amazon lawns of what, 6 4007, the Web services. So the past 14 15 years have been what I've been calling cloud transition, right? And so you had cos technologies that were either doing on migration from on premise and cloud or hybrid on premise off premise. And now you're seeing a generation of technologies and companies. Their cloud only John to your point. And so you could argue that this 15 year transitions were like, you know, Thio use a bad metaphor like amphibians. You're half in the water, half on land, you know, And like, you know, you're not You're not purely cloud. You're not purely on premise, but you can do both ways, and that's great. That's great, because that's a that's a dominant architecture today. But come just like rock set and snowflake, your cloud only right? They're born in the cloud, they're built on the cloud And now we're seeing a generation Startups and technology companies that are cloud only. And so, you know, unlike you have this transitionary evolution of like amphibians, land and sea. Now we have ah, no mammals, whatever that are Onley in the cloud Onley on land. And because of that, you can take advantage of a whole different set of constraints that are their cloud. Only that could build different services that you can't have going backwards. And so I think for 2021 forward, we're going to see a bunch of companies or cloud only, and they're gonna look very, very different than the previous set of companies the past 15 years. And as an investor, as you covering as analysts, is gonna be super interesting to see the difference. And if anything, the cloud only companies will accelerate the move of I t spending the move of mawr developers to the cloud because the cloud only technologies are gonna be so much more compelling than than the amphibians, if you will. >>Yeah, insisting to see your point. And you saw the news announcement had a ton of news, a ton of stage making right calls, kind of the democratization layer. We'll look at some of the insights that Amazon's getting just as the monster that they are in terms of size. The scope of what? Their observation spaces. They're seeing all these workloads. They have the Dev Ops guru. They launched that Dev Ops Guru thing I found interesting. They got data acquisition, right? So when you think about these new the new data paradigm with cloud on Lee, it opens up new things. Um, new patterns. Um, S o. I think I think to me. I think that's to me. I see where this notion of agility moves to a whole nother level, where it's it's not just moving fast, it's new capabilities. So how do you How do you see that happening? Because this is where I think the new generation is gonna come in and be like servers. Lambs. I like you guys actually provisioned E c. Two instances before I was servers on data centers. Now you got ec2. What? Lambda. So you're starting to see smaller compute? Um, new learnings, All these historical data insights feeding into the development process and to the application. >>I think it's interesting. So I think if you really want to take the next evolution, how do you make the cloud programmable for everybody? Right. And I think you mentioned stage maker machine learning data scientists, the sage maker user. The data scientists, for example, does not on provisioned containers and, you know, kodama files and understand communities, right? Like just like the developed today. Don't wanna rack servers like Oh, my God, Jerry, you had Iraq servers and data center and install VM ware. The generation beyond us doesn't want to think about the underlying infrastructure. You wanna think about it? How do you just program my app and program? The cloud writ large. And so I think where you can see going forward is two things. One people who call themselves developers. That definition has expanded the past 10, 15 years. It's on Lee growing, so everyone is gonna be developed right now from your white collar knowledge worker to your hard core infrastructure developer. But the populist developers expanding especially around machine learning and kind of the sage maker audience, for sure. And then what's gonna happen is, ah, law. This audience doesn't want to care about the stuff you just mentioned, John in terms of the online plumbing. So what Amazon Google on Azure will do is make that stuff easy, right? Or a starved could make it easy. And I think that the move towards land and services that moved specifically that don't think about the underlying plumbing. We're gonna make it easy for you. Just program your app and then either a startup, well, abstract away, all the all the underlying, um, infrastructure bits or the big three cloud vendors to say, you know, all this stuff would do in a serverless fashion. So I think serverless as, ah paradigm and have, quite frankly, a battlefront for the Big Three clouds and for startups is probably one in the front lines of the next generation. Whoever owns this kind of program will cloud model programming the Internet program. The cloud will be maybe the next platform the next 10 or 15 years. I still have two up for grabs. >>Yeah, I think that is so insightful. I think that's worth calling out. I think that's gonna be a multi year, um, effort. I mean, look at just how containers now, with ks anywhere and you've got the container Service of control plane built in, you got, you know, real time analytics coming in from rock set. And Amazon. You have pinned Pandora Panorama appliance that does machine learning and computer vision with sensors. I mean, this is just a whole new level of purpose built stuff software powered software operated. So you have this notion of Dev ops going to hand in the glove software and operations? Kind of. How do you operate this stuff? So I think the whole new next question was Okay, this is all great. But Amazon's always had this problem. It's just so hard. Like there's so much good stuff. Like, who do you hired operate it? It is not yet programmable. This has been a big problem for them. Your thoughts on that, >>um e think that the data illusion around Dev ops etcetera is the solution. So also that you're gonna have information from Amazon from startups. They're gonna automate a bunch of the operations. And so, you know, I'm involved to come to Kronos Fear that we talked about the past team kind of uber the Bilson called m three. That's basically next generation data dog. Next generation of visibility platform. They're gonna collect all the data from the applications. And once they have their your data, they're gonna know how to operate and automate scaling up, scaling down and the basic remediation for you. So you're going to see a bunch of tools, take the information from running your application infrastructure and automate exactly how to scale and manager your app. And so AI and machine learning where large John is gonna be, say, make a lot of plumbing go away or maybe not completely, but lets you scale better. So you, as a single system admin are used. A single SRE site reliability engineer can scale and manage a bigger application, and it's all gonna be around automation and and to your point, you said earlier, if you have the data, that's a powerful situations. Once have the data can build models on it and can start building solutions on the data. And so I think What happens is when Bill this program of cloud for for your, you know, broad development population automating all this stuff becomes important. So that's why I say service or this, You know, automation of infrastructure is the next battleground for the cloud because whoever does that for you is gonna be your virtualized back and virtualized data center virtualized SRE. And if whoever owns that, it's gonna be a very, very strategic position. >>Yeah, it's great stuff. This is back to the theme of this notion of virtualization is now gone beyond server virtualization. It's, you know, media virtualization with the Cube. My big joke here with the Q virtual. But it's to your point. It's everything can now be replicated in software and scale the cloud scale. So it's super big opportunity for entrepreneurs and companies. Thio, pivot and differentiate. Uh, the question I have for you next is on that thread Huge edge discussion going on, right. So, you know, I think I said it two years ago or three years ago. The data center is just a edges just a big fat edge. Jassy kind of said that in his keynote Hey, looks at that is just a Nedum point with his from his standpoint. But you have data center. You have re alleges you've got five G with wavelength. This local zone concept, which is, you know, Amazon in these metro areas reminds me the old wireless point of presence kind of vibe. And then you've got just purpose built devices like cameras and factory. So huge industrial innovation, robotics, meet software. I mean, whole huge edge development exploding, Which what's your view of this? And how do you look at that from? Is an investor in industry, >>I think edges both the opportunity for start ups and companies as well as a threat to Amazon, right to the reason why they have outposts and all the stuff the edges if you think about, you know, decentralizing your application and moving into the eggs from my wearable to my home to my car to my my city block edges access Super interesting. And so a couple things. One companies like Cloudflare Fastly company I'm involved with called Kato Networks that does. SAS is secure access service edge write their names and the edges In the category definition sassy is about How do you like get compute to the edge securely for your developers, for your customers, for your workers, for end users and what you know comes like Cloudflare and Kate have done is they built out a network of pops across the world, their their own infrastructure So they're not dependent upon. You know, the big cloud providers, the telco providers, you know, they're partnering with Big Cloud, their parting with the telcos. But they have their own kind of system, our own kind of platform to get to the edge. And so companies like Kato Networks in Cloud Player that have, ah, presence on the edge and their own infrastructure more or less, I think, are gonna be in a strategic position. And so Kate was seen benefits in the past year of Of of Cove it and locked down because more remote access more developers, Um, I think edge is gonna be a super great area development going forward. I think if you're Amazon, you're pushing to the edge aggressively without post. I think you're a developer startup. You know, creating your own infrastructure and riding this edge wave could be a great way to build a moat against a big cloud guy. So I'm super excited. You think edge in this whole idea of your own infrastructure. Like what Kato has done, it is gonna be super useful going forward. And you're going to see more and more companies. Um, spend the money to try to copy kind of, ah, Cloudflare Kato presence around the world. Because once you own your own kind of, um, infrastructure instead of pops and you're less depend upon them a cloud provider, you're you're in a good position because there's the Amazon outage last week and I think like twilio and a bunch of services went down for for a few hours. If you own your own set of pops, your independent that it is actually really, really secure >>if you and if they go down to the it's on you. But that was the kinesis outage that they had, uh, they before Thanksgiving. Um, yeah, that that's a problem. So on this on. So I guess the question for you on that is that Is it better to partner with Amazon or try to get a position on the edge? Have them either by you or computer, create value or coexist? How do you see that that strategy move. Do you coexist? Do you play with them? >>E think you have to co exist? I think that the partner coexist, right? I think like all things you compete with Amazon. Amazon is so broad that will be part of Amazon and you're gonna compete with and that's that's fair game, you know, like so Snowflake competes against red shift, but they also part of Amazon's. They're running Amazon. So I think if you're a startup trying to find the edge, you have to coexist in Amazon because they're so big. Big cloud, right, The Big three cloud Amazon, Google, Azure. They're not going anywhere. So if you're a startup founder, you definitely coexist. Leverage the good things of cloud. But then you gotta invest in your own edge. Both both figure early what? Your edge and literally the edge. Right. And I think you know you complement your edge presence be it the home, the car, the city block, the zip code with, you know, using Amazon strategically because Amazon is gonna help you get two different countries, different regions. You know you can't build a company without touching Amazon in some form of fashion these days. But if you're a star found or doing strategically, how use Amazon and picking how you differentiate is gonna be key. And if the differentiation might be small, John. But it could be super valuable, right? So maybe only 10 or 15%. But that could be ah Holton of value that you're building on top of it. >>Yeah, and there's a little bit of growth hack to with Amazon if you you know how it works. If you compete directly against the core building blocks like a C two has three, you're gonna get killed, right? They're gonna kill you if the the white space is interest. In the old days in Microsoft, you had a white space. They give it to you or they would roll you over and level you out. Amazon. If you're a customer and you're in a white space and do better than them, they're cool with that. They're like, basically like, Hey, if you could innovate on behalf of the customer, they let you do that as long as you have a big bill. Yeah. Snowflakes paying a lot of money to Amazon. Sure, but they also are doing a good job. So again, Amazon has been very clear on that. If you do a better job than us for, the customer will do it. But if they want Amazon Red Shift, they want Amazon Onley. They can choose that eso kind of the playbook. >>I think it is absolutely right, John is it sets from any jassy and that the Amazon culture of the customer comes first, right? And so whatever is best for the customer that's like their their mission statement. So whatever they do, they do for the customer. And if you build value for the customer and you're on top of Amazon, they'll be happy. You might compete with some Amazon services, which, no, the GM of that business may not be happy, but overall. Net Net. Amazon's getting a share of those dollars that you're that you're charging the customer getting a share of the value you're creating. They're happy, right? Because you know what? The line rising tide floats all the boats. So the Mork cloud usage is gonna only benefit the Big Three cloud providers Amazon, particularly because they're the biggest of the three. But more and more dollars go the cloud. If you're helping move more. Absolute cloud helping build more solutions in the cloud. Amazon is gonna be happy because they know that regardless of what you're doing, you will get a fraction of those dollars. Now, the key for a startup founder and what I'm looking for is how do we get mawr than you know? A sliver of the dollars. How to get a bigger slice of the pie, if you will. So I think edge and surveillance or two areas I'm thinking about because I think there are two areas where you can actually invest, own some I p owned some surface area and capture more of the value, um, to use a startup founder and, you know, are built last t to Amazon. >>Yeah. Great. Great thesis. Jerry has always been great. You've been with the Cube since the beginning on our first reinvented 2013. Um, and so we're now on our eighth year. Great to see your success. Great investment. You make your world class investor to great firm Greylock. Um great to have you on from your perspective. Final take on this year. What's your view of Jackie's keynote? Just in general, What's the vibe. What's the quick, um, soundbite >>from you? First, I'm so impressed and you can do you feel like a three Archy? No more or less by himself. Right then, that is, that is, um, that's a one man show, and I'm All of that is I don't think I could pull that off. Number one. Number two It's, um, the ability to for for Amazon to execute at so many different levels of stack from semiconductors. Right there, there there ai chips to high level services around healthcare solutions and legit solutions. It's amazing. So I would say both. I'm impressed by Amazon's ability. Thio go so broad up and down the stack. But also, I think the theme from From From Andy Jassy is like It's just acceleration. It's, you know now that we will have things unique to the cloud, and that could be just a I chips unique to the cloud or the services that are cloud only you're going to see a tipping point. We saw acceleration in the past 15 years, John. He called like this cloud transition. But you know, I think you know, we're talking about 2021 beyond you'll see a tipping point where now you can only get certain things in the cloud. Right? And that could be the underlying inference. Instances are training instances, the Amazons giving. So all of a sudden you as a founder or developer, says, Look, I guess so much more in the cloud there's there's no reason for me to do this hybrid thing. You know, Khyber is not gonna go away on Prem is not going away. But for sure. We're going to see, uh, increasing celebration off cloud only services. Um, our edge only services or things. They're only on functions that serve like serverless. That'll be defined the next 10 years of compute. And so that for you and I was gonna be a space and watch >>Jerry Chen always pleasure. Great insight. Great to have you on the Cube again. Great to see you. Thanks for coming on. >>Congrats to you guys in the Cube. Seven years growing. It's amazing to see all the content put on. So you think it isn't? Just Last point is you see the growth of the curve growth curves of the cloud. I'd be curious Johnson, The growth curve of the cube content You know, I would say you guys are also going exponential as well. So super impressed with what you guys have dealt. Congratulations. >>Thank you so much. Cute. Virtual. We've been virtualized. Virtualization is coming here, or Cubans were not in person this year because of the pandemic. But we'll be hybrid soon as events come back. I'm John for a year. Host for AWS reinvent coverage with the Cube. Thanks for watching. Stay tuned for more coverage all day. Next three weeks. Stay with us from around the globe. It's the Cube with digital coverage of aws reinvent 2020 sponsored by Intel >>and AWS. Welcome back here to our coverage here on the Cube of AWS.

>>lie from Copenhagen, Denmark. >>It's the >>Q covering Nutanix dot Next 2019. Brought to you by >>Nutanix. Welcome back, everyone to the cubes. Live coverage of Nutanix. Stop! Next here in Copenhagen, Denmark. I'm your host, Rebecca Knight, coasting along side of stew minimum. Of course. We're joined by Regime Mirani. He is the CTO clad platforms at Nutanix. Thank you so much for coming on the Cubans. You need >>to be here as usual. >>So you were up on the main stage talking about your guiding force. Your mission to make enterprise computing so reliable, so ubiquitous that it's invisible. >>You don't think about >>it. You don't even get a little No, I mean, look, >>if you look at any successful technology, consumer technology doesn't need to be aware of the details around it, right? I mean, take cars, even because the first introduced you probably had to understand Rick operate. There was how it all works. Remember for water in the radiator. But most people don't know how to do that today. I wouldn't know how to do that today, even though my Utah actually had to do some of those things. Um, that isn't the point. of the cars or self driving. Now the same thing should happen to computing. And we spend way too much time today just doing things that keep the light. Don't nights on. Just imagine infrastructure patching things up, grading them. I really should be something that not what idea is doing i d should be focusing on the business, delivering applications that their customers need and not so much on managing infrastructure. >>Rajiv, that one click Simplicity is so important, yet we know things are becoming even more complicated. Bring us inside a little bit that you know, you've got 14,000 customers. Guess and there's been a major, basically rewrite of a less to be able to be ready for all of the new ash cloud Native envy me obtained, you know, you name it all of these things. How do you balance getting all of this new stuff up with making sure that you keep that simplicity and don't make things for all of your customers while all the jet engines, uh, you know, >>it takes constant effort. It takes a conscious effort to make sure that things are in drifting away from our goal of being simple and to be frank. At times it has and you know, we periodically to audits off all our work floors. Make sure that as simple as you think they are and haven't drifted over time. And occasionally we do find some rail clunkers and have to go back and fix those things. What >>makes it >>different is that we start with a fairly opinionated view on how things should be done. The idea is to make it simple for 99% of the people, while still offering the all that washed options of one person power users would need them and making sure that we understand what 90% 99% of people need. And focusing on that is very important to a lot of customer focus study sort of design reviews, but also this constant going back and you're taking work feel like we m creation like provisioning of'em. When he started, it was pretty simple right then, as we started adding more and more options eyes, this thing going to use a PC I passed through isn't going to use this option. That option suddenly realized that now they're 30 things that people are feeling into provisional we have, most of which nobody cares I care about. So you go back, read I tte keep doing that again and again and again. >>So rich Eve It's one thing when you talk about living on different servers, whether it be super micro underneath or Delhi Emcee Lenovo H p e. It's >>gonna be a >>little bit different if you're talking about where you're going with H p E Green Lake with, you know, the X in AWS that you talk about when I talk to people, you know, it's like, Oh, I'm trying to use terror form and you know, But I have to write it. One way to work with Amazon. I have to write it another way. If it's, you know, azure G C P S o. You know, will Nutanix be able to keep that simplicity and bring, you know, homogeneity to thes dispersed invite? >>Absolutely. So the point is, watch a layer of abstraction right the way we are going to public cloud away we go every server winter out the way of doing things and sigh all if it starts with the hyper wiser and the story of stock and networking with three layers of abstraction. And if you have the same three components everywhere, everything we built on top of that remains exactly the same. Prison was the same on a P S. On the same. Everything looks the same. So higher level constructs like calm and so on don't have to be aware of what the actual substrate is creating a calm blueprint, whether it works on ZAY on AWS or whether Trump's on SX or whether runs on Nutanix H way. The blue blueprint remains exactly the same. Now, if you want to consume more, service is if you want to consume. So this is an Amazon, which are not available on premises. You want to use things like auto scaling groups in Ec2. Sure, you could then create blueprints that our customers we're putting in the substrate. >>So, in terms of this, you said, you start with a very opinionated place of where the customer is well, First of all, it's based on customer feedback and customer surveys. And so where were are you right now in terms of where the customer is? Are you meeting the customer now, or is the customer ahead or what? Where would you describe that? I think it >>depends on what you're looking at. If you're looking at the core products, absolutely, the customers are with us. They were ready to consume. They actually drive a lot of the innovation that we're doing. We're feeding, feeding back changes that we could be doing to make things even simpler on the private cloud side that's getting there. I think we get a lot off feedback on files on on present pro on com on on Flow because those have started getting a lot of adoption in the market, and we do get a lot of feedback on them on. So our newer products that you started a war being more recently, it's a more collaborative process. There were actually working with customers directly understanding their problems on dhe, moving a roadmap forward based on that. So while it's early in terms off adoption in production, the whole process is very collaborative in those situations. So we really are very close to the customers there. >>What are some of the biggest customer problems right now that they're facing what's what's keeping them up at night and therefore keeping you up at night? >>Security is always a big one. Complexity, people skills. All those things are big problems. In fact, one of the biggest things like that was just training enough people to handle all the complexity in a data set. Is the Morrigan removed from that? The more they don't have to focus on that, the easier you make their lives. The other thing is just a lot of time to spend on routine activities which, which acquired disruption to service is right. This is something we've talked about before. Why does it Why does it require a legacy three tier system to have maintenance windows and downtime to do an upgrade? Google our has downtime. Google is never down for maintenance. Doesn't mean they're not already there waiting all the time. So how do we bring that same kind of capabilities on premises that's gonna focus our long power? >>So, Rajiv, when I'm talking to users out there, when they talk about all of the items that are out there that they need to deal with and the routine task automation is something keeps, you know, coming up. So tell us where automation fits into some of the new things that you were talking about today in this week with your customer? >>Yeah, automation >>for us. Waking automation in three steps anything that's automatic better be safe. First of all, safety is paramount. Started security. It has to be simple, and we talked about how calm provides for that. And then you can start adding in this new wave off technologies around artificial intelligence and machine learning. And it's not so much about automation right now. It's all gone to me. It's it's autonomous operations, not just scripts. That due to a task on dhe, that's >>an area >>we invested in very heavily early on with our prison pro product way, build our own patented or thumbs for machine learning applied them to operational metrics like capacity planning. And what if modeling and dynamic alerts and what we've been doing with that is extending that more into the application layer so that not only can you apply these algorithms to CP when memory, we can actually get insights into Hey, the Leighton see on this particular application looks somewhat unusual, or the amount of cash available on a sequel server is unusually low and act on those, and the other part is acting on on alert. Something happens. There's a human being need to get in wall to solve for that. And if it does, then well, it's not really automatic. Right? So that's the other part that we introduce, which is a cross for a product which lets you define these action chains that automatically, uh, what about to be triggered when Annie went on alert takes place, they can go ahead and fix the problem. But also, you know, simple things like send your slack notification or an email locked. They went, maybe create a snapshot of your wee am so that you could go back and be back problems later. All that sort of thing made really, really simple. >>Yes, it goes back to the simplicity and the invisibility to this. >>Yes, yes. Uh, autonomous data centers, by definition, have to be invisible, right? If if if If you're to get involved in marriage and autonomous Data center, then what's the plane? It's a point. Exactly. So the whole idea is that, uh, human involvement in day to day operations against solo that everybody's focused on applications on line of business use cases. >>Rajiv, when it when it comes to those applications. You know, you talked about some of the new enhancements like envy me on and obtain, You know, Where are your customers today? You know, Are there any interesting applications that you're seeing them deploying today? Ah, Pattern. I've talked about the last couple of years of the Nutanix show, is modernized the platform and then modernized the absolute top of it. Things like container ization. I'm sure to bell curve in a journey where all the customers But you know, what are some of the patterns that air starting emergen where they finding success? >>Yeah, This >>whole wave off new applications around data pipelines with Kafka spark things like that Apache stack effectively which are putting more more off load on storage in particular. So that's that's one area. We see customers looking for more performance. But >>even, >>you know, some of the traditional ah traditional uh, applications like ASAP Hana and epic and meditate expanse. They also have patterns which can benefit greatly with some of that wants wants that we have been making and gets a technical issue. No, The size of the working said with it all fits and car and on sst was spitting on magnetic drives. But something like we've been doing is moving the overheads. If you do have a miss and you go to slow a media, you still get good performance. And that's really how we're getting good to the new. >>Well, yeah, maybe without getting, you know, we don't need to go drill down into the core of the intel chip everything. But you know, Nutanix doesn't just take off the shelf stuff and, you know, put a box together. It's software, and there's work that happens with your partners in the ecosystem. Give us a little flavor as toe. You know where you're making the investments and where some of those partnerships and integrations or a key? >>Yeah, So on the platform side, Ah, a lot of the investments happen in validation of the platforms, making sure that we're ahead of the curve in adopting technologies but also feeding back from our side things we would like to see in the platform. Right? So how do you adapt things like R d m A. To handle not just the traditional work with the happy converge workload? How do you essentially look for things in this new class? of memories that would benefit from data locality for us. So that's one class off partnership that we have the hardware vendors with GHB, with Intel, with the IBM, a whole bunch of people. But >>then >>we also have partnerships up the stock these days with companies like service. Now, with we for backup for for our mind product. I think you saw a little bit of that today. It's a whole bunch of things happening across all areas. >>One of the things that it really comes across at this conference is just how strong Nutanix culture is. The company culture, the humble, honest, hungry and another word that's creeping in now is resilient. I'm wondering if you could talk a little bit about your division of the company and describe how the company's resilience, the employees and the company itself has really displayed itself. >>So, you know, as it any company you know, Any time you go through the kind of growth we have, there's the forward momentum that everybody sees. They also a lot of setbacks that people don't really see, and they've been a whole bunch of us off these in our history. They've been areas where literally. The product has has a floor which is so fundamental we call it internally a near death experience. What's really great until again, from an engineering point of yours, how the teams come together at that point instead of these war rooms, even working weekends, Everybody's there. Everybody's on it and nobody talks about. Hey, look, where's my work? Life? Balance of things like that, especially when they're the customer in world. If there's if there's a problem that's causing customers outages, our engineers will give up everything. They'll give up everything and not just at work with their lives to make sure that gets fixed. And that has helped us get Basti setbacks get back in stride. Happens last Now. It used to happen a lot earlier, but spill this real culture resilience from the big *** in the early engineers. >>All right, Rajiv, what's exciting? You going forward? You know you don't have to touch on this one. But you know, when I saw at the end, the site clusters and hibernate feature was something that was like, Oh, yeah. I don't think I've seen that as to how I could make sure I save my data be ableto, you know, Shut things down. Maybe start there. But give us You know what a little bit. Look forward as to where the team's playing. >>Now, that's kind of, >>you know, thinking that detail thing that you have to do. What, you want to launch a new product, right? Okay, look, the whole point of doing doings, I clusters on Amazon. One of the biggest use cases. This cloud bursting cloud busting is not just about increasing your workload size, scaling it up at some point, you want to scale it down? How do you do that for state for work? Stateless. It's easy. All I'm registering Web servers over that sort of my way, they're gone. But our database that I scaled out over there well, that data can't go away. So we had to find ways to essentially solve for those from. So that's how the hibernate feature came around in general, The bigger question that you asked about, You know what I'm most excited about? I >>think this >>whole convergence of private and public cloud with same stack on both sides is a new new tank. It really hasn't existed before. Um, the father applications can now move back and forth seamlessly between public cloud and private cloud without rewriting without re factoring without a big lift and shift is very, very interesting. But by itself, it's not enough. Um, the flip that's missing is what about data movement? What about if you have your data and Amazon and I want to move it on premises? That there really are no good solutions of the Amazon doesn't give you a P eyes on dhe the tools to do that. So I think data movement's gonna be a big thing. And then Billy, a common service's tack on board because it's not just networking, storage in and compute anymore, right? If you're an Amazon, you're probably using all kinds off. Networking service is security groups. Ah, Route 53. How do you take those kind of service is and also make them available on premises. >>So, Rajiv, is there anything you've learned as a team when you look at AWS outposts or Oracle clouded customer, we've had a few years of talking about, but not a lot of deployments yet, so, you know, not saying you're late to the market, but you know what would have been able to sit back and learn from what has been done so far. >>So the >>reason we >>a little bit late to the market is that we think of solving a problem which the other windows are not, Which is kind of what I alluded to before that is that how do you support both the legacy applications on the cloud Net Cloud applications? How do you provide for migration both ways? Applications of a born in the cloud and now you want to move them on premises or applications of a born on premises and you want to move them to the Cloud Outpost is great. I think it's a good good product of technologies that AWS are thinks that hybrid is the right strategy, but it's also one problem. It's also the problem off cloud applications running on premises it does not solve for the problem of legacy applications running and cloud right, that is just a cz difficult as ever. That's that's not become any easier without force. Similarly, if you look at what we are very swing with AWS, it's also legacy applications going going to AWS. But in doing so, they don't have access to all the different networking services that AWS offers because you're not running and a sex, and you're kind of running a different networking start tonight. So with well, thought long and hard about this problem. And I said, Hey, look, we're not going to take the easy answer over here. You can take Take our stock, which is known to run both legacy and cloud native applications. If probe in that on Internet natively into Amazon so that you can use Amazon service is you can use our service is you can a legacy. Applications can run more than applications without giving up. Anything on that, I think is why signal this longer? But I think it's a more powerful solution for the long term. >>Thank you so much for coming on the Cube. It's always a pleasure having you on my back and see us again. Thanks. I'm Rebecca Knight for stew. Minutemen stay more of the cubes. Live coverage of dot Next Nutanix here in Copenhagen,

>>live from Seattle, Washington. It's the key nude covering Smartsheet engaged 2019. Brought to you by smartsheet. >>Welcome back, everyone to the cubes. Live coverage of smartsheet engaged here in Seattle, Washington. I'm your host along with my co host, Jeff Rick. We're joined by Jean Farrell. He is the CPO of smartsheet. Thanks for coming on the show. >>Thanks for being here. >>Great to be here here last year and even bigger and better. You moved out of the hotel and convention center. That gets something. Did >>we did, We were. We have almost 4000 strong this year and we're super excited. We've been looking forward to this for a while. So >>So this is the third, the third annual conference yet. Just tell us a little bit. Let's let's open it up by telling our viewers a little bit about what this means to you, how big the show is. Give us a few stats. >>Yeah, well, you know, we ran our first customer conference, our first engaged really three years ago in in Bellevue at a conference center attached to a hotel that's right next to our headquarters, which is so super convenient, and I think we had 5 700 people there, and it was a great start andan. Last year we doubled in size and we actually outgrew the facility in Bellevue on. So when we planned for this year, we said, You know, let's go Big way felt this momentum building. We had such great feedback from customers what they learned and what they came away and could do after coming to engage that we felt we could. We were ready to kind of take it to a big stage. And so it was really exciting. I spent before joining Smartsheet two and half years ago. I spent five years that Amazon Web service is, and I was fortunate enough to be there when they did their first reinvent in Las Vegas, and it was roughly 5000 people, and I had a very interesting deja vu moment walking into the main auditorium here yesterday, Andi, it just brought back all the memories of Oh my gosh, this is like the size of remain so in three years we should be. Roughly 25,000 will be >>in Vegas >>today, up on the main stage. A lot of great new product announcements I want it, I want you to sort of break it down for our viewers. He started talking about how you really served three core customers and these new product announcements are really targeted. Each of these >>Yeah, we kind of broke it out. And what we find >>your way, sir? Customers of all sizes. So from startups, toe, medium sized businesses to large enterprise and within almost every one of those customers, we really see three distinct user groups really work force, which is at the core kind of where we started the I T teams, which many times there to support the workforce but also drive a lot of their own work clothes. And then the business decision makers. Folks that are really looking at, How do I drive overall organizational effectiveness and improve efficiency? And so what we tried to do was make sure we were delivering a set of capabilities for everybody on DSO for the workforce. We announced a bunch of new capabilities. Probably the highlight was our new conversations in context, which we're really excited about. It's gonna enable ah, whole new level of collaboration and engagement within the platform, and >>it was really >>grounded in customer feedback. That said they wanted the ability to actually interact in the context of their work and too many times what they were forced to do is they would have a question and they would have to go send an email or they go send a chat and then the response is disconnected. So it just wasn't as efficient. That could be. So we took that signal and work very closely with customers to design the new experience. So really excited about those those capabilities. We launched new forms, capabilities and multi select dropped down a lot of things that our customers are really excited around. From the workforce perspective on the I t front, we've introduced a ton of new things all year. The two big announcements today were around our accelerator for GDP are which it actually affects almost anybody that does business with an EU citizen. So a lot of folks don't really connect the dots ago. I'm in. You know, I'm in Redmond, Oregon. Why do I need to comply with GDP? Are well, if you sell the anybody in the you need to figure that out, um, and and then, um beyond GDP are. We talked about our federal offering on our new govcloud, which is really key for government agencies but also all the contractors to support government agencies. And so a lot of our customers are very interested in that. And then the final piece was really business leaders. Andi talked there about new enhancements to control center. Do it really let it scale and move across the organization roll ups, ability to do multi tier on then. Importantly, we talked about the new content collaboration capability, which is which is a really big it integrates are our slope technology. So marketing and other types of, uh, disciplines can use content collaboration in their work. I'd be remiss if I didn't mention 10,000 feet. >>So lots to talk about a lot. But you clearly, this is the customers, right? Because I think it was at the pasting. Widgets between Dashboard was a standing ovation. It's amazing the power of copy and paste when you can pull that work, you know, it's it's what the people want. It's funny you say that I am constantly >>amazed with that. The things that when you saw little problems that unlock all sorts of new use cases and many times that cheer you here is because customers have been trying to work around those problems, right? So multi select Drop Down is a great example where they had to do all sorts of gyrations in how they configure their work to support multiple selections. And so now we've made that much more elegant for them, and they're like, ecstatic because they no longer have to invest that time and >>I can't >>let you go. >>Wow, Is that all it took? I would sooner. It is a lot of times right, the simple things that have the huge, a huge improvement in kind of getting away from this repetitive work, which is under the theme we keep hearing over and over and over again. >>No, that's absolute. That's absolutely true. And it is really little things can have a big impact or Or or the analogy I sometimes will use is if you're creating a puzzle or if you have kids and you've ever built, you know, the X wing fighter set. If you're missing a few pieces, it's just not the same, right It just right. You can't kind of complete the work and so sometimes just completing that play for customers, giving them that that last piece they need to really go in power. Their workflow is is really cute. >>And I also think because we're living at a time where we have way demand so much from technology in our personal lives, and it delivers most for most. For the most part, our lives are pretty seamless and the way we can order things from anywhere. And so when we have, when we deal with these little aggravations at work, it's just that much more so. One of the things you said on the main stage is that customers are not shy about telling you what they want. So I want to hear from you how you solicit feedback and your process for making these changes for >>way actually, have >>we actually have a bunch of different mechanisms? We used to listen a customer, and I actually call it customer signal because it comes from a lot of different places. Way have kind of foundation. Aly we have a process actually called enhancement request. So many of our customers can go in our community and actually submit a form and say I really want you to build this Andi, That's very intentional, like there's no confusion, and usually they're very straightforward. But beyond that, we also we have the community in general. So we monitor that we get feedback on on kind of a freefall flowing forum where they give us feedback. We have user groups that this year will due north of 40 user groups around the world, where we bring collections of customers together, many time hosted at different customer locations, and customs will talk and share best practices and give us feedback on things that they'd like to see. I spend a ton of time out in the field with customers just visiting with them, talking about their use cases, helping themselves problems on and importantly, we have AH product advisory Council and a customer advisory board. And these air both specific groups of customer smaller groups that we've recruited and we actually use them tow, consult with us very closely to give us kind of overall direction. And then probably the most valuable feedback once we know where we want to go is once we start building, we have a private beta program, and then what we call an early adopter program. Both of those enroll customers in interacting with things were building before they're launched. And that gives us a chance to get real time feedback into what they like. What? They don't know what we need to improve. And sometimes the product will stay in in that private beta phase for longer than we expected, because the signal we get requires that we make changes. So we think that's really important to make sure we actually hit the mark. Because if you if you're on, if you're not satisfied, customer need or solving a problem, >>they're not gonna buy. What's the point? You're >>surely gonna get a lot of customers signal here at >>engaged over the next couple of Absolutely. And they're absolutely not shy. Every time I'm running some, it's like, Oh, we love this. And here's the 10 things I want that exactly. >>Thank you so much for coming on the Cubans. Pleasure having you >>my pleasure. Thanks for having me. And thanks for being here. It engaged. Thanks >>for having us. Great. >>I'm Rebecca Knight for Jeff. Rick, You are watching the cube. Stay tuned

>> live from San Francisco, celebrating 10 years of high tech coverage. It's the Cube covering Veum World 2019. Brought to you by VM Wear and its ecosystem partners. >> Welcome back. We're here. Of'em World 2019. You're watching the Cubans? Our 10th year of coverage at the event. I'm stupid. And my co host this afternoon is Justin Warren. And happy to welcome back to the program. Bob Ghaffari, who's the general manager of the Enterprise and Claude networking division at Intel. Bob, welcome back. Great. Great to be here. Thank you. S Oh, uh, you know, it's a dressing. And I think that last year I felt like every single show that I went to there was an Intel executive up on the stage. You know, there's a way we talked about. You know, the tic tac of the industry is something that drove things. So last year? Ah, lot going on. Um, haven't seen intel quite as much, but we know that means that, you know, you're you and your team aren't really busy. You know a lot of things going on here. VM worldwide. Give us the update since last we spoke. Well, you know, um >> So I think we have to just go back a little bit in terms of how until has been involved in terms of really driving. Just hold this whole network transformation. I want to say it started about a decade ago when we were really focused on trying to go Dr. You know, a lot of the capabilities on to more of a standard architecture, right? In the past, you know, people were encumbered by challenging architectures, you know, using, you know, proprietary kind of network processors. We were able to bring this together until architecture we open source dp decay, which is really this fast packet processing, you know, library that we basically enabled the industry on. And with that, there's basically been this. I want to say this revolution in terms of how networking has come together. And so what we've seen since last year is you know how NSX via Miranda sex itself has really grown up and be able to sort of get to these newer, interesting usage models. And so, for us, you know what really gets us excited is being really involved with enabling hybrid cloud multi cloud from a network perspective. And that's just what really gets me out of bed every day. Yeah, An s >> t n is, I think, gone from that early days where it was all a bit scary and new, and people weren't quite sure that they wanted to have that. Whereas now Stu is the thing, it's people are quite happy and comfortable to use it. It's it's now a very accepted way of doing networking. What have you noticed about that change where people have gone? Well, actually, it's accepted. Now, what is that enabling customers to do with S T. N. >> You know, um I mean, I think what you know S Dan really does. It gives you a lot of the enterprise customers and cloud customers, and a lot of other is really the flexibility to be able to do what you really need to do much better. And so if you can imagine the first stage, we had to go get a lot of the functions virtualized, right? So we did that over the last 10 years, getting the functions virtualized, getting him optimized and making sure that the performance is there as a virtual function. The next step here is really trying to make sure that you know you weaken enable customers to be able to do what they need to end their micro service's and feels. Or do this in a micro segmented kind of view. When and so um and also being in a scenario, we don't have to trombone the traffic, you know, off to be there, be it's inspected or, you know, our load balance and bringing that capability in a way, in a distributed fashion to where the workloads Neto happen. >> Yeah, who you mentioned micro segmentation there, And that's something which has been spoken about again for quite a while. What's the state of play with micro segmentation? Because it some customs have been trying to use it and found it a little bit tricky. And so they were seeing lots of vendors who come in and say We'll help you manage that. What's the state of play with Michael segmentation From your perspective, >> you know, I would say the way I would categorize it as micro segmentation has definitely become a very important usage model. In turn, how did really contain, you know, uh, policies within certain segments, right? So, one you know, you're able to sort of get to a better way of managing your environments. And you're also getting to a better way of containing any kind of threats. And so the fact that you can somehow, you know, segment off, um, you know, areas and FAA. And if you basically get some kind of, like attack or some kind of, you know, exploit, it's not gonna, you know, will go out of that segmented area to to some extent, that simplifies how you look at your environment, but you want to be able to do it in the fashion that you know, helps. Ultimately, the enterprises managed what they got on their environments. >> So, Bob, one of things that really struck me last year was the messaging that VM were had around networking specifically around multi cloud. It really hearken back to what I had heard from my syrup reacquisition on. Of course. Now, Veum, we're extending that with of'em or cloud in all of you know, aws the partnerships they are false, extended with azure, with Google in non premises with Delhi emcee and others. And a big piece of that message is we're gonna be able to have the same stack on on both sides. You could kind of explain. Where does Intel fit in there? How does Intel's networking multi cloud story dovetail with what we're hearing from VM? Where Right, So I >> think >> the first thing is that until has been very involved in terms of being into, um, any on Prem or public clouds, we get really involved there. What were you really trying to do on my team does is really focusing on the networking aspects. And so, for us is to not only make sure that if you're running something on prime, you get the best experience on from but also the consistency of having a lot of the key instruction sets and any cloud and be able to sort of, ah, you know, managed that ballistically, especially when you're looking at a hybrid cloud environment where you're basically trying to communicate between a certain cloud. It could be on Prem to another cloud that might be somewhere else. Having the consistent way of managing through encrypted tunnels and making sure you're getting the kind of performance that you need to be able to go address that I think these are the kind of things that we really focus on, and I think that for us, it's not only really bring this out and, um improving our instructions that architecture's so most recently What we did is, you know, we launched our second generations Aeon Scaleable processors that really came out in April, and so for us that really takes it to the next level. We get some really interesting new instruction, sets things like a V X 5 12 We get also other kind of, you know, you know more of, like inference, analytic inference capabilities with things like Deal Boost that really brings things together so you can be more effective and efficient in terms of how you look at your workloads and what you need to do with them, making sure they're secure but also giving you the insights that you need to be able to make that kind of decisions you want from a enterprise perspective >> steward. It always amuses me how much Intel is involved in all of his cloud stuff when it it would support. We don't care about hardware anymore. It's all terribly obstructed. And come >> on, Justin, there is no cloud. It's just someone tells his computer and there's a reasonable chance there's an Intel component or two Wednesday, right? >> Isn't Intel intelligence and the fact that Intel comes out and is continuing to talk to customers and coming to these kinds of events and showing that it's still relevant, and the technology that you're creating? Exactly how that ties into what's happening in cloud and in networking, I think is an amazing credit to what? To Intel's ability to adapt. >> You know, it's definitely been very exciting, and so not only have we really been focused on, how do we really expand our processor franchise really getting the key capabilities we need. So any time, anywhere you're doing any kind of computer, we want to make sure we're doing the best for our customers as possible. But in addition to that, what we've really done is we've been helped us around doubt our platform capabilities from a solution perspective to really bring out not only what has historically been a very strong franchise, pressed with her what we call our foundational nicks or network interface cards, but we've been eldest would expand that to be able to bring better capabilities no matter what you're trying to do. So let's say, for example, you know, um, you are a customer that wants to be able to do something unique, and you want to be able to sort of accelerate, you know, your own specific networking kind of functions or virtual switches. Well, we have the ability to do that. And so, with her intel, f p g. A and 3000 card as an example, you get that capability to be able to expand what you would traditionally do from a platform level perspective. >> I want to talk about the edge, but before we go there, there's a topic that's hot conversation here. But when I've been talking to Intel for a lot of years out container ization in general and kubernetes more specifically, you know, where does that fit into your group? I mentioned it just cause you know that the last time Intel Developer forum happened, a friend of mine gave a presentation working for intel, and, you know, just talking about how much was going on in that space on. Do you know, I made a comment back there this few years ago. You know, we just spent over a decade fixing all the networking and storage issues with virtualization. Aren't we going to have to do that again? And containers Asian? Of course, we know way are having toe solve some of those things again. So, you >> know, and for us, you know, as you guys probably know, until it's been really involved in one of the biggest things that you know sometimes it's kept as a secret is that we're probably one of the bigger, um, employers of software engineers. And so until was really, really involved. We have a lot of people that started off with, you know, open source of clinics and being involved there. And, of course, containers is sort of evolution to that. And for us really trying to be involved in making sure that we can sort of bring the capabilities that's needed from our instructions, said architecture is to be able to do containers kubernetes, and, you know, to do this efficient, efficiently and effectively is definitely key to what we want to get done. >> All right, so that was a setup. I I wanted for EJ computing because a lot of these we have different architectures we're gonna be doing when we're getting to the edge starting here. A little bit of that show that this show. But it's in overall piece of that multi cloud architecture that we're starting to build out. You know, where's your play? >> Well, so for us, I mean the way that we look at it as we think it starts all, obviously with the network. So when you are really trying to do things often times Dedge is the closest to word that data is being, you know, realized. And so for us making sure that, you know, we have the right kind of platform level capabilities that can take this data. And then you have to do something with this data. So there's a computer aspect to it, and then you have to be able to really ship it somewhere else, right? And so it's basically going to be to another cloud and might be to another micro server somewhere else. And so for us, what really sets the foundation is having a scale will set a platform sort of this thick, too thin kind of concept. That sort of says, depending on what you're trying to do, what you need to have something that could go the answer mold into that. And so for us, having a scaleable platform that can go from our Biggers eons down to an Adam processor is really important. And then also what we've been doing is working with the ecosystem to make sure that the network functions and software defined when and you know that we think sets a foundation to how you want to go and live in this multi cloud world. But starting off of the edge, you want to make sure that that is really effective, efficient. We can basically provide this in a very efficient capability because there's some areas where you know this. It's gonna be very price sensitive. So we think we have this awesome capability here with our Adam processors. In fact, yesterday was really interesting. We had Tom Burns and Tom Gillis basically get on the stage and talk about how Dell and VM we're collaborating on this. Um, and this basically revolves around platforms based on the Adam Process sitter, and that could scale up to our ze aan de processors and above that, so it depends on what you're trying to do, and we've been working with our partners to make sure that these functions that start off with networker optimized and you can do as much compute auras little computer as you want on that edge >> off the customers who were starting to use age because it's it's kind of you, but it's also kind of not. It's been around for a while. We just used to call it other things, like robots for the customers who were using engine the moment. What's what's the most surprising thing that you've seen them do with your technology? >> You know what is interesting is, you know, we sometimes get surprised by this ourselves and so one of the things that you know, some customers say, Well, you know, we really need low cost because all we really care about is just low level. You know, we we want to build the deploy this into a cafe, and we don't think you're gonna be all that the price spot because they automatically think that all intel does is Biggs eons, and we do a great job with that. But what is really interesting is that with their aunt in processors, we get to these very interesting, you know, solutions that are cost effective and yet gives you the scalability of what you might want to do. And so, for example, you know, we've seen customers that say, Yeah, you know, we want to start off with this, but you know, I'm networking, is it? But you know what? We have this plan, and this plan is like this. Maybe it's a 90 day plan or it could be up to a two year plan in terms of how they want to bring more capabilities at that branch and want to want to be able to do more. They want to be able to compute more. They want to make decisions more. They want to be able to give their customers at that place a much better experience that we think we have a really good position here with their platforms and giving you this mix and match capability, but easily built to scale up and do what our customers want. Great >> Bob, You know, when I think about this space in general, we haven't talked about five g yet, and you know, five g WiFi six, you know, expected to have a significant impact on networking. We're talking a little bit about you know edge. It's gonna play in that environment. Uh, what do you hear from Augusta Summers? How much is that involved with the activities you're working through? You know, >> it's definitely, really interesting. So, uh, five g is definitely getting a lot of hype. Were very, very involved. We've been working on this for a while until it's, uh, on the forefront of enabling five G, especially as it relates to network infrastructure, one of the key focus areas for us. And so the way that we sort of look at this on the edges that a lot of enterprises, some of them are gonna be leading, especially for cases where Leighton see is really important. You want to be able to make decisions, you know, really rather quickly. You want to be able to process it right there. Five g is gonna be one of these interesting technologies that starts, and we're already starting to see it enabled these new or used cases, and so we're definitely really excited about that. We're already starting to see this in stadium experience being enabled by five G what we're doing on the edge. There's experiences like that that we really get excited when we're part of, and we're really able to provide this model of enabling, you know, these new usage models. So for us, you know the connectivity aspects five g is important. Of course, you know, we're going to see a lot of work clothes used for G as basically predominant option. And, of course, the standard wired connective ity of I p m pl less and other things. >> I want to give you the final word. Obviously, Intel long partnership. As we know you know, current CEO Pack else under, you know, spent a good part of his, you know, early part of career at Intel. Give us the takeaway intel VM wear from VM 2019. You know, I mean, we've had a >> long partnership here between intel on VM, where we definitely value the partnership for us. It started off with virtual light servers a while back. Now we've been working on networking and so for us, the partnership has been incredible. You know, we continue to be able to work together. Of course. You know, we continue to see challenges as we go into hybrid cloud Malta Cloud. We are very excited to how in terms of how we can take this to the next level. And, you know, we're very happy to be be great partners with them. >> All right. Well, Bob Ghaffari, thank you for giving us the Intel networking update. We go up the stack down the stack, Multi cloud, all out the edge, coyote and all the applications for Justin Warren. I'm stupid. Men will be back for our continuing coverage of the emerald 2019. Thanks for watching the Cube.

>> live from San Francisco, celebrating 10 years of high tech coverage. It's the Cube covering Veum World 2019. Brought to you by VM Wear and its ecosystem partners. >> Welcome back to two cubes. Live coverage in San Francisco, California for VM World 2019. I'm John Ferrier, Postal Cuba David Lattin, My Coast, Dave. 10 years covering the BM World Paul Maritz laid out the stack early on. We saw that and watch it go through Its motions now >> remain from the marketing people got a hold of >> that mainframe turned into cloud Now hybrid cloud seven years after we first started about 2012 has been great Our next guest, Paul Falsone, S V. P and general manager of the Cloud Native APS. This is a business unit within VM where that is going to the next level. This is the Act three is Jerry Chen said any of you I talked earlier for VM wears a company. I won't say moving up the staff because there is no stack. It's cloud, right? So its applications on top of operating infrastructure Dev ops going enterprise scale is about developers building APS operating them in scale. This is a big focus of what you're doing. >> It is a dead end of the day. One of my close friend of mine, who's in front of customers all the time, reminds our team constantly that our customers applications matter of the most cause. That's what they used to get in front of their customers with the Dillman teams and the tools they're building the user. Japs come second cause that's what supports the abs. And then the infrastructure comes third zone away. There is that stacks it, but never forget you were at the bottom of the pecking order, if you will, when it comes to ultimately bringing full customer value to our company, our customers, businesses. >> And it's one of the things we've been looking back at our 10 years covering VM where I think you're 13 15 of'em world is that the virtual ization of all very quickly around really optimizing server virtualization really kind of change. The game of one kind of knows that our knows the history there, but it did it without any code changes, too, APs and I think that was a very innovative thing. Now we looking containers and what Kubernetes is bringing to the table. You're starting to get some clear visibility into what's happening and what's possible. Could >> you >> share your vision on what that visibility is that you guys are eyeing for the marketplace in four of'em, where, >> sure, the APP development methodologies are changing, changing more today than they have in the last 20 years. We're seeing ah lot of new concepts and approaches that right now really only accessible to a small percentage of application developers worldwide. We want to try to bring those application development methodologies, practices tools to the mainstream so we can. We can touch the 13 or $14 million.1,000,000 enterprise developers around the world and help the CEOs in their line of business counterparts at our customers get a CZ much productivity out of their development teams as possible. At the end of the day, those APS we're gonna power the next decade of those organizations success or failures with their customers, and so that's becoming a real competitive asset. I've had a number of customer discussions here this week where the primary theme is how me help my developers move faster at enterprise scale, but in a regulated environment in an environment where compliance is is front center >> to big things going on in your world that we covered extensively, honestly, pretty impactful to the Vienna, where portfolio one as open source and hefty oh, acquisition half a billion dollars almost a year ago, about a year left in less than a year, probably was that we close in December last year. So yes, ovary. Just recently we know those guys all people. I mean, I've been covering that for a while, and then I'll see the pivotal acquisition. Just announced a drink from the fire hose. There be doing tons of press briefings, those to impact points, kind of leaving a mark. >> So we've been we've been building up to this. I joined AA Drink them were in 2012 through the Sierra acquisition, but I moved into this role about just about three years ago, and one of the things that we identified early on was, ah, close partnership with Pivotal was going to be essential inside of the Del Technologies umbrella for us to exist in thrive together. And so that's where the idea for P Cass was born. So the combination of V. M. R. R and D with pivotal RND focused on delivering our first community service to our enterprise. Customers we brought helped you in last year. Once they saw what we were doing and thought about the possibility of what would happen if we actually took some of the concepts of communities and p ks and embed them into V sphere, That was, I think, the real ah ha moment for for us and the happier team coming together in the power of what that could enable. But all along the way, we always believed that that was just covering the infrastructure side of the equation. You still needed to get through the making the APP developers productive and efficient in this new infrastructure world and so on to be able to do so on any cloud. And that's where the pivotal piece finally came together last just last month. July Pivotal put out a lot of information in the market around how they're evolving their portfolio to be very cool, bernetti centric, moving forward. And that was a big part about getting all the pieces lined up so that the M word could deliver what we announced this week. The in the town's a portfolio with the component tree for building running in managing modern applications on any club, >> we've kind of come full circle here, predates, and I Sarah, But you guys talking about the stack? Yeah. Paul Moretz. I used to have the whole stack. Ed actually applications up here with Simba. Spring sources around. Exactly. And then you had these when I used to call the misfit toys. Have you had some assets in the M. C as coming in Vienna, where Paul Maritz, Joe Tucci decided, create pivotal as the The platform developed next generation applications. Now it's all come full circle there. So my question is related to that stack and particularly the death part of that stack. This audience is not Deb's not, but increasingly, you've gotta attract that audience. So what's what's your thoughts there? And so >> I think pivotals done a very nice job over the years through the Con Foundry Foundation. The work they've done there through the spring community Spring is at this stage is is arguably the most popular modern Java development environment on the planet. So, you know, we're seeing a tremendous amount of leverage of that of that framework and so between the events of pimples is actively involved in Leeds and their ability to help customers, um teach their enterprise developers how to get the most out of this modern tool kit. We think that there is some wonderful ingredients to a recipe to really scale this thing up in a big way. We way. I also believe that Veum we're still has a lot to learn about what it means to best support enterprise developers and their organizations. And so we are quite a bit in learning mode right now. We're gonna take a lot of lessons from the pivotal team as we as we move forward towards the close and learn a lot more about the team in the culture and their customer engagements. But one of the things I think is is front and center to what pivotal has for customers today is their transformation Service's customers. You've got different groups inside a customer summer looking to build the newest applications. Some of them are just trying to get more operational efficiency out of what they have today. Some of these customers have 12,000 applications in their environments. Um, pivotal has ah set of service is that come in and they help them take their existing monolithic applications and just modernize key components of them so they can operate them more efficiently and reclaim a lot of resources to go do other things. That, I think is probably the lowest hanging fruit for enterprise organizations today. And I'm very, very excited about the service is that pimple has to make available the customers on that front. >> Assad and Jerry Chen, earlier than the other set I was mentioning earlier is a VC now, Greylock, big time to your one. We see former VM Where, uh, guy from 22,003. He also worked on cloud foundries in sight. We ask about the white spaces where starts to thrive in one of the transit is kind of pointing to was have some cummings going public. Some are being bought at sizable numbers, but we rift on. The idea of monitoring was a boring category right now. Observe ability, which is just be monitoring 2.0, you got I pose. You got acquisitions. I mean, major action happening in this observe ability space. I bring this up because that's an area you think, Oh, it's a white space Data opportunities for companies to build service is really points to this cloud. 2.0 application Renaissance And I want to get your thoughts on that environment. What needs to be in place to make that happen? Honestly, pivotals keep for you guys. I get that on Vienna. Where side, but for the ecosystem and for the marketplace, people trying to make careers and or do things What is that cloud 2.0, complexity that need to be abstracted away or >> so The Pepto team had a great Craig and Joe had this great, uh, one liner on kubernetes is all about where the people structure meets the infrastructure. When you think about that, our enterprise organizations have thousands if not tens of thousands of developers all trying to do similar. But a lot of cases different things at the same time, across lots of different cloud infrastructures. On the infrastructure team side, you've got private cloud, you've got hybrid cloud. You've got public cloud environments that you have to get your arms around, monitor, manage, secure and get visibility into. We believe that Carini sits at that perfect layer between the two domains on. This is a big part of why we developed Tom's a mission control. It's just that that perfect layer between the two domains, too, access the company's later and give you full visibility into what all of your developers were doing on every piece of your infrastructure. And we also think that's gonna be a very interesting place for third parties to plug into to gain access to all of the community's clusters that we're helping. Our customers managed across their app landscape to do very interesting things. And so we're really excited about the ecosystem that that project will open up. >> You think this opportunity to start ups in there? >> I do. I do. I think there's a ton of other I mean, think about it just really basic math. Ah, VM based application. When it gets containerized, it has just on the compute side alone. Never mind the networking in the storage site. There are 10 times as many moving parts. A typical containerized EPA's 10 times as many moving parts as avian bay Step. If you think about that applied to the networking layer, you think about that applied to the storage layer, the security layer. You've got 10 times as many points to secure. Now, how do you get your head around that level of complexity As a an operations person, you can't do it. Humans can't do it anywhere. You can't write down your actions. Control this on a pad of paper and know what's what's accessing what anymore, >> Dave. One more question, if I may, on the on the VM container thing, there's a debate or are architectural kind of conversation, and customers are having around when to do containers in three days on bare metal or with V EMS. How do you guys talk to that house? The >> steam going because that was my question. So there was a snarky tweets yesterday. I want to get your reaction to it. And the tweet was during yesterday's keynote. I thought we we launched pivotal so that we didn't have to run containers on V EMS. Now the reality to your point is that people are running containers on bare metal. They're running him on vehement the EMS. I don't have any data, but I wonder if you could comment on that >> so way Probably have a couple of snarky comments of our own on this three share one of the things that put up on stage. Yes, I'll start at the kind of a little little. And I worked my way up at the base layer. The testing we're doing with Project Pacific, which is something we announced this week, which is effectively bringing kubernetes into the heart of the sphere. We're actually using combinations to make the sphere better. We're also going to expose communities to our customers through V sphere, just like we exposed the EMS today. This is a pretty exciting project for the for the company in our early testing of this project, based on the advanced scheduling capabilities of the SX hyper visor take advantage of modern hardware. We're seeing an 8% better performance in a certain test sweet versus what you'd see on bare metal so are ready at the early stages. We're seeing some benefits now take that a step further. The big public college for writers out there if you look at service is like G K on Google. If you look at a ks, uh, recast on Amazon, a cast on his door, every single one of their community service is is run against a virtualized environment, not on a bare metal environment. Why is that? Well, because their customers are using containers in VM, side by side, the flexibility you get out of that virtualization layer. Whether you're a big public cloud provider or your ah smaller enterprise shop running your own data centers, the benefits are proportionate, rather equal on dso >> the narratives off a little bit. What you're saying. What I hear you saying is people use virtualization for a lot of efficiency and scale reasons that's independent of what happens with bearnaise decisions. So if you decide you want to run Cubans on bare metal, go >> to go to town. We think >> if you want to do that, >> you want to do that. But we don't. We actually see a lot of customers who have started down that path. When they go to get to that operational stage, they're realizing they're now dealing with firm where again, they're dealing with Nick drivers again. They're dealing with stuff, and they can easily take that and turn it over to their ops team that's already managing a huge virtualized state and operated with the same tool. >> That's a really a layer thing around round scale. You do the virtual ization for Ryan reasons, and then cos sits on top of it for a whole another reason. >> And the I'd say its operations scale these operations teams need to, you know, just look at the number of announcements we made this week. For an ops team to get their head around all of these new technologies simultaneously is impossible to bring them in one new capability of time into the thing that they're already operating for. That organization is very >> positive. If I understood yesterday, you're claiming better before 8% better performance relative to bare metal. I know that's apples to apples. Or what kind of juicing you're doing on the benchmark >> sex schedule that it chooses it right there. >> I want to ask you about integration and look at it as a quasi. His story of the the industry. You go back to see A with all the acquisitions, right? Historical force it with fusion. Different layer of the stack. I know. Certainly Del did a lot of acquisitions. Some of them work. Some of them didn t m c. Same thing pretty successful. Actually. VM were great engineering. Um, very strong. Go to market on really good acquisitions. My question is on integration with the nice Sarah background, I wonder. I mean, nice. Sarah seems to be very well integrated into the VM. Where platform How is integration The state of integration today within V. M. Where is it a lot easier today because we're living in this AP I economy. What about VM? Wears sort of integration ethos. One of the challenges. I wonder if you could comment and that long. So >> I've been through, uh, to significant integrations of'em where the 1st 1 was with this nice era on. I was on the I was on the incoming side, not the receiving side. The next was with hep Theo. I was on the receiving side, not the incoming side. And so, as coming into this year, back in 2012 Pat was extremely supportive and asked his entire team to be very supportive of getting us integrated quickly and productive. A CZ fastest possible. We were on campus on the via more campus from the next era office within days of the deal closing. That's how efficient Veum work. That's like that's the mindset hammerhead coming into. We were in a building. We were co located with the other networking engineers and product managers. Within the first week on, we were off to the races. That was about 100 20 person company. Hep Ko is about 100% company, Um, about the same efficiency we were consolidating. Offices were bringing them over again, mostly distributed team, but they had a center of gravity. In Seattle. We had a center of gravity in Bellevue. We brought the team's over within within a couple of months in about three months. In three and 1/2 months in, we had the team fully integrated. The organizational design done all the tools in a greater we're all in the same systems. So what happens very quickly now, an organization that's much bigger like like pivotal 3000 employees. Public company takes a little bit longer to get from Deal announced the deal close because it's too public entities. It'll take a little bit longer to do all the integration, but we're already thinking thinking about we know them so well and they know us so well. We already know where the potential landmines are, where the potential rough spots are. Pat prides himself and, uh, this pushes down into the rest of them were on well, welcoming new team members in new groups into the company. And so we try to do that really were very culturally sensitive way optimized for the right tool kit s O that we take, we take some learning like cloud health. When they came in, they had a lot of expertise around. SAS drooling and support of customers were adopting all of that, right. Were jettisoned some of our older tools in favor of some of the things that >> we're gonna win the modernization. So I want to get your thoughts on the last question for the second congratulations, your your your area. We love what you're doing. We think it's super important. Would be covering it like a blanket this year and going forward. But Pakistan came on was wrapped. Talking about 10 years and doing the riffing on the Cube are 10 years covering it. We have some 10 years forward, which waves to be on. They highlighted on the past 10 years in this ear acquisition as a critical moment to bring VM. We're into the S T D C kind of concept started networking up, so we know the history they're sti n and then going forward, he says. If you're not a networking and security in the next wave and Kubernetes is Number one, you're really gonna be missing out. So we highlighted networking, security and kubernetes. But networking. It's nice here on both sides of that 10 year spectrum. You're part of that. >> Why is that? Why is that wise >> watching people know that networking is the most important piece of the wave here? What's the relevance of what he's saying? Share their thoughts on >> Think about the increasing complexity of what at modernization drives into the infrastructure. You're getting smaller and smaller moving parts that that need to operate together at scale in a comprehensive, logical way. But at any point in time, if you're if you're an enterprise organization, if you've got if you've got compliance requirements, audit ability, requirements. If you want to protect, you hear about the number of of small towns that get blackmailed on a daily basis because someone's secured an encrypted There, there, there count taxpayer data and they're there, their victims. All right, this is this >> is some say, cyber warfare. >> It is something. So if you think about in orderto help, our customers get the most out of their developers, these tools that open up I think the potential of a lot more avenues of attack get a lot more complex. And so we think that these two have to progress hand in hand. One. We do want to help developers go as fast as possible. We won't help enterprises get the most out of those developers. That's a big part of why we brought them were into into the damn warfare. We're bringing a pivotal into the VM. We're family, but at the same time, we recognize that the infrastructure has to progress. Every bit is fast, and the network is the thing that ties all these parts together. Whether it's a layer three year layer for networking today or level layer several networking layer seven AP I based networking in the future >> all. I mean, I'm not gonna bring up I ot or industrial i ot to takeovers of physical devices, whether it's a self driving bus off a cliff or taking over towns and cities warfare, I mean the service areas of enormous networks, Internet connectivity applications over the cloud native. Anyway, we know that, right? So a lot to talk about. Thanks for coming on. The Cube Sharing your insight. Senior Vice President, General manager, The Cloud Native APS Group. This is really the key instrument with envy em where to take kubernetes and the advancement of cloud to 0.0 to the next level. I'm John for a day. Volante, be back after this short break.

>> lie from San Francisco celebrating 10 years of high tech coverage. It's the Cube covering Veum World 2019. Brought to you by VM Wear and its ecosystem partners. >> Welcome back to the cubes. Live coverage here in San Francisco, California, for VM World 2019. I'm Jeff Davis Davis, our 10th year, 10 years covering the M world. Quite a run. Got a great stories. More stories coming, Emma days. A lot of organic growth. A lot of typos in the startup scene. Our next two guests Mike Adams, CIA Director bm wear and Ziv Kalman. Oh, vich product line manager here. Welcome to the Cube. Great to see you. Yes, Curtsy to you guys. Got a lot of activity happening around bit fusion. A lot of news to share. Exciting. I mean, in the M. And a story has been high on VM. Where we talking back? Elsie earlier. Continue to fill in on the strategy. >> Yeah, absolutely. Give us the update. Yeah, I think the key thing for us is we really want to become a key player in the A. I am l space and say that those workloads should come on visa. And with this acquisition we think, provides a great framework for a lot of the hardware accelerator devices. The best of you known of those his GP use. But we think there's four coming market with PG A's and also custom a six. So we're super excited about that. >> For the folks that don't know much about the acquisition, what was the motivation? What was the company's core product? What was the interest? Yeah, the >> company had a product called Flex Direct, and that particular product was really focused on taking, ah, similar concept that a lot of V m writes No, which was, Hey, we knew that computes space. We were trying to take these isolated islands and pull them together. Same type of thing. Here you had these expensive devices that people were buying and they were isolated. And now if we could take a single server, it's got a bunch of GP use on it. Why don't we share it? You see all these papers that come out around machine learning at the very end. It says she's I'm amazed that thes GP user so underutilized even when we're actually using them. It's kind of like buying a car and then using the radio only right? Doesn't. It just doesn't make sense. I >> got this trend of alternative processors just sort of exploding all over the place. I mean, obviously in video, sort of people know what's going on there, but but you've got arm. Now you've got the edge coming in, you know, Intel. Still dominant in the server space. But even even storage devices today use different type, not in the not Intel processors in there. It's a combination of our mo are Sometimes you know, G. P uses you say F g a Z, even though they're sort of a narrow use case. You're seeing a six make a comeback. So you got all this additional processing power, you know, going. So that's a tailwind. Absolutely, guys, and it's sort of the intersection of those to maybe talk about some of the trends you see in that regard and how you're taking advantage of them. >> Yeah, it reminds me of many moons ago when we had new chips that were coming out. We said, Jesus, hardware, flurry here, right? And now we're in a really similar spot. Ziv and I see a lot of different types of devices and acceleration devices, whether it's computer network or storage. And in this particular case, right, we just see a hotbed of all these customers that air seeing the same problem, right? And we've got great partnerships with Intel you mentioned in video and and many others. And we just want to really leverage those for these devices because you look at V sphere and say, OK, your traditional workloads. We've done those very, very well. But as we get into containers, KUBERNETES, machine Learning and I, we want these newer cloud native and newer workloads to come our way. And taking advantage of these new capabilities really helps accelerate that in a big way. >> Could you >> explain Maur on the the sphere impact? Because, you know, first of all, of'em, where community you get the feedback right away on Twitter and a lot of things. But sometimes you gotta dig in and find out what people are thinking and where there might. I think that could be future up opportunities or because it meets skepticism. Well, the the sphere native having a eye on the sphere, that's just mind blowing to me. But I mean, I can see I can see a data processor kind of vibe going on here where data needs to be processed. That seems to be a trend. What is it going on with the sphere with this? Is there what's the what's to customers? No. >> Well, I think the first thing to clarify here is that, you know, some often there is this question. Why would Iran m Ellery I work? Look specifically envy. Sphere is a platform. But then customers do run Emily and workers and public clouds. And those layers are not that different than the spirits virtualization layer, and they're running it in virtual machines. So the whole idea would be fusion specifically, is it? Actually, we can make it even more efficient to run these workloads on top of the sphere because the underlying infrastructure that you two actually, you have to accelerate these workloads there. Today they are mostly GP use, obviously, but in the futures, Michael so mentioned you a six are coming in and effigies are coming in. We are going to make those as well. That's the plan using the B fusion framework. Be more efficient to use. A lot >> of people are skeptical around running machine learning on these are not skeptical because, I mean, it's great for any time you have the opportunity to automate something or used software to make something go away. That's not the difference. You're undifferentiated, so it makes sense. But I just can't figure out where, specifically, within these fears of being targeted to use >> where envy sphere as in, Well, >> if I'm operating the sphere on top operator, I got Debs kicking around the corner. I got a cloud Mom reclaiming. Where's this fit in? Where >> this fits into essentially any place for a visa is running. It doesn't matter if it would run on via MacLeod and for any other for cloud partnerships or on the the edge of our Vesey runs. This is a core capability of the sphere, so it doesn't matter. You know where physically or infrastructure is, we would be able to expose this technology. The idea is also that you mentioned the trends in the A six as they're coming into the enterprise. There's an architectural changes also coming in, and in the server perspective, it's just it's the servers are actually getting more dense there, in there, in there in the accelerator infrastructure that they have in them. So you're seeing four to a GP using a single server. Those are very powerful machines. You can just move oil, represent a single machine again. That brings us back to be fusion and descend. The segregated model affects territory used, which is very similar by the way to centralize stories use. >> You guys are on something really big here. I think that hardware assists off load anything. Hardware system, harbor off load is gonna be a more of a bigger trend. And we saw it happen big time and hyper converge just for storage and everything. But I think as you want to stack where kubernetes gonna flourish? Yeah. I mean, imagine all the service is that he turned on Turned off. I mean, that's not I mean, men even know when it gets turned on or off. >> Absolutely offload for awhile with things like a raise, right, trying to push processing off to a bigger ray that you've got there. And then one other thing you said that I think was really important is the audience, right? If you look at a i n m l, we have traditionally haven't talked to the data, scientists of the machine learning folks. And we need to get to the I t. Folks that air supporting those workloads saying similar to some other workloads that were new and saying these were gonna come your way. And so we need to be prepared and you need to be able to leverage. So >> what's the What's the pitch to those folks? What's that? What's what you guys saying to them? Because it is a benefit for Debs and Dev Ops is to have an ops right. You got the ops down. Okay, see that and this change happening. But a dev, What's the pitch? But how do you get their attention? What's the value proposition? >> The the Actually, that's the beauty of it. It's exactly the same bottle proposition that the sphere in Vienna, where the Vienna state provides the developers and the only thing is that now we are letting the the office people to actually provide this doing this infrastructure as well in the same efficient manner. So it's your transformation. Basically, it's giving the exact same value proposition. >> Talk about the multi cloud tie in here. We've heard a lot about multi cloud and I think multi cloud in part anyway, is being able to run any application and workload anywhere. And one of things about your technology is the ability to not have to rewrite the application to take advantage of acceleration. Does it fit into multi cloud? And if so, how? >> Yeah, when we made the bet Fusion acquisition, if you look at their story, they had the any any any story as well, just like we do. And so, you know, we made announcement this week within video and eight of us and VM, where it's definitely possible of the technology that we have to extend that even further. And so, you know, the only thing I know with users going forward is they're gonna have more than one cloud, and so we just need to prepare for that and make sure that it works. And it works well across the board and the common layer. When you look at our multi cloud strategy is vey sphere is going to be at each of those layers. So if it's ties in disease here, it should be pretty easy to make it work in each of those environments. >> What was that What was the announcement you made you share? The big >> one was being able to use in video in the context of cloud in AWS. So's GPU capabilities and bring it to the service as we do on Prem. And so that was a big piece. And then we also obviously, in making that announcement talking about Hey, you know, this is a critical area for us because not only are we doing this, but we're also saying that your bit fusion will help enhance this because we think in video and bit fusion work very well together as well. >> And is that a product of service? Ah, go to market initiative. >> In the case of the coordinated us, it would be offered as part of the service. So when you can consume the compute, you know you want a GPU, it'll be there for you to help run that workload in the cloud. >> And that's available. When >> that's an nvidia in AWS kind of question. When they are making that infrastructure available, it's essentially going to be a nun. In another instance, type that the ember cloud in AWS will offer okay, I >> mean, it's a tech preview. >> What if some of the things that people should know about because again, in the pattern I'm seeing here of'em world is as in love to stack with kubernetes being that abstraction layer that guessing eyes promoting heavily on rightfully so. We're big fans communes with that for the beginning is that you're gonna have this this purpose built, um, native capability so that when you guys got this native vibe going on native to hype the sphere native TSX native, what does that actually mean? Native like Cooper, naked native on I. But what does it native mean? Explain to the audience what that actually means. >> I'll start up. Sure. You could >> elaborate 30 minutes if you want. But what is that >> true native native? The idea >> for us was used kubernetes really two ways. You know, most of the time when we were talking about Cooper Naser Containers, it's running that on top of these Fair right? What happens if you could take the DNA of that and put it actually inside of east here? Right, so not only you could run these clusters and native pods, but you could also leverage some of the value and one of the things that Cubans does really well is it handles workloads really well. So if we take an example where we have 145 e ems and they make up your app, right, normally you'd have to go to each one of those and figure out OK, let's make some changes in tweaks. And now what I can do is I can treat all of those is one workload and I can move them. I could do really interesting things with that. And that's the power one of the powers that you have with Kubernetes. >> And that's where the differentiation. Then you don't think that there's a >> Yeah, exactly. I mean you are essentially getting There are a lot of benefits our customers, our values value that the customer is getting today from V Sphere, generically speaking, and our longtime customers are familiar with the value propositions. And what we are saying is that when you're getting something as a native capability is that essentially ties into all the other capabilities that you already were know very well and you will be able to get those. But with on top on, sometimes on top orbit in conjunction with what >> is that gonna enable? Now let's talk about the enablement. >> So let's go back all the way. If you go all the way back to be fusion, for example, if you enable it is a native technology, then if you're running containers or viens on the sphere natively they can consume to be fusion technology. If you have cool, it is. It can orchestrate natively, the PM's and containers that are using the confusion to collision. Excited. Oh, so this is the whole thing, >> more efficient platform standpoint, >> and it's easier to manage as well, because you don't have to install a bunch of stuff on top of each other because it's needed. It's part of the first. >> A lot of hassle go away that people might >> take it in and you're gonna have to guess tomorrow they're going to go deep into it with >> you. Great, we're excited. So we're hearing a lot, obviously, but kubernetes at this event and and but most of the audience, they're not developers. So how can you use the sort of bit Fusion mojo to attract developers for some of these new workloads, that air come into the marketplace? >> Yeah, I mean it's all about acquiring new audiences in a case of infusions. More the data scientists. In the case of the communities, it's more around the developer. But I think let's use the kubernetes examples as a good one and what we announced with Project Pacific. Basically, the way it looks, the technology looks to them. It'll look like the kubernetes, a p I with a little bit of east for goodness from the operator perspective, the people that we know the 20,000 that are here, it looks to them like the sphere was from kubernetes Goodness. So that's the right mix is you've got to get it. So it looks exactly the smells and feels just like what they're used to. And I think that's a that's a key aspect. And then for the data Scientists with fusion, we really need to say Okay, you know you want to run these workloads, but she's you're paying really a lot of money for these expensive, isolated devices, and you could get more value by kind of grouping them up and making sure that they're used kind of in aggregate, right? >> So there's more leverage on the data science side So if I'm say hiring someone I know I'm or more to work with with >> exactly, essentially, it's it's the same story. They don't need to change their applications, their framework. Their models use the same could interface, which is the GPU interface for for the GPS computer. >> So So let's talk about that. So data scientist, you know, they always complain that most their time is spent wrangling data That's their, you know, bugaboo. And then there's a collaboration between data scientists and developers, which probably doesn't happen enough. What are you seeing in terms of the trends from the data science role? And can you help solve some of those problems? >> Well, what we are about to solve is really access access to infrastructure for them. Easy access to the infrastructure in their software stack. And the way to get there is to make the data engineers that serve these data scientists and the application administrators that surges data scientist to get easy access to the infrastructure Dany to provide the software, and that's where the sphere eventually comes in. So it's not the Celia direct relationship with the end users. It's more enabling the entire organization that actually served these end users and let them use as much infrastructure as your partners. And >> that and that and user organization. The buffer >> guys last question share what the plans are. What's next? What's your goals for the next 6 to 12 months? I'll see. Get the acquisition under your belt. Native in these fear, a lot of other cool things. I mean that I could talk about >> customers and maybe you can talk about product from a customer perspective. You know, we want engage in proof of concepts. So we want to bring them in, let them test out the software. It already works with the beast here, so I'll be running with multiple proof of concepts across the globe. We >> use cases in the U. S. Case or what? >> Yeah, I mean, it's it's pretty simple at the moment. It seems to be most people that are using GP use around ml. We have a great demo down the floor that shows people trying to run inception, three year resident 50 And how can we actually help those v EMs that are running that? So that's gonna be my focus. The next six >> years you want get some use cases come over here, bring him up to Mike. >> And from that perspective, I mean, obviously, we acquired occasion in an early stage. The technology works well. It works well enough to be product eyes. However, Veum, wherein the sphere has very high enterprise software stone standards in terms of security and management and governance. All this capabilities so that's going to be are focused on the next, you know, even almost a year to make sure that we bring it up to a level where we can confidently provide it and sell. It is a product >> you gotta engineering hye bar there absolutely thanks to Russia coming on keeping the update, the end world coverage Breaking it down. 2019. It's the Cuba job for David. Thanks for watching Be back with more after this short break.