(light music) >> Narrator: theCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (upbeat music) >> Welcome back to Spain everyone. Lisa Martin here with theCUBE Dave Vellante, my co-host for the next four days. We're live in Barcelona, covering MWC23. This is only day one, but I'll tell you the theme of this conference this year is velocity. And I don't know about you Dave, but this day is flying by already. This is ecosystem day. We're going to have a great discussion on the ecosystem next. >> Well we're seeing the disaggregation of the hardened telco stack, and that necessitates an ecosystem open- we're going to talk about Open RAN, we've been talking about even leading up to the show. It's a critical technology enabler and it's compulsory to have an ecosystem to support that. >> Absolutely compulsory. We've got two guests here joining us, Gautam Bhagra, Vice President partnerships at Dell, and Scott Walker, Vice President of global Telco ecosystem at Wind River. Guys, welcome to the program. >> Nice to be here. >> Thanks For having us. >> Thanks for having us. >> So you've got some news, this is day one of the conference, there's some news, Gautam, and let's start with you, unpack it. >> Yeah, well there's a lot of news, as you know, on Dell World. One of the things we are very excited to announce today is the launch of the Open Telecom Ecosystems Community. I think Dave, as you mentioned, getting into an Open RAN world is a challenge. And we know some of the challenges that our customers face. To help solve for those challenges, Dell wants to work with like-minded partners and customers to build innovative solutions, and join go-to-market. So we are launching that today. Wind River is one of our flagship partners for that, and I'm excited to be here to talk about that as well. >> Can you guys talk a little bit about the partnership, maybe a little bit about Wind River so the audience gets that context? >> Sure, absolutely, and the theme of the show, Velocity, is what this partnership is all about. We create velocity for operators if they want to adopt Open RAN, right? We simplify it. Wind River as a company has been around for 40 years. We were part of Intel at one point, and now we're independent, owned by a company called Aptiv. And with that we get another round of investment to help continue our acceleration into this market. So, the Dell partnership is about, like I said, velocity, accelerating the adoption. When we talk to operators, they have told us there are many roadblocks that they face, right? Like systems integration, operating at scale. 'Cause when you buy a traditional radio access network solution from a single supplier, it's very easy. It's works, it's been tested. When you break these components apart and disaggregate 'em, as we talked about David, it creates integration points and support issues, right? And what Dell and Wind River have done together is created a cloud infrastructure solution that could host a variety of RAN workloads, and essentially create a two layer cake. What we're, overall, what we're trying to do is create a traditional RAN experience, with the innovation agility and flexibility of Open RAN. And that's really what this partnership does. >> So these work, this workload innovation is interesting to me because you've got now developers, you know, the, you know, what's the telco developer look like, you know, is to be defined, right? I mean it's like this white sheet of paper that can create all this innovation. And to do that, you've got to have, as I said earlier, an ecosystem. But you've got now, I'm interested in your Open RAN agenda and how you see that sort of maturity model taking place. 'Cause today, you got disruptors that are going to lean right in say "Hey, yeah, that's great." The traditional carriers, they have to have a, you know, they have to migrate, they have to have a hybrid world. We know that takes time. So what's that look like in the marketplace today? >> Yeah, so I mean, I can start, right? So from a Dell's perspective, what we see in the market is yes, there is a drive towards, everyone understands the benefits of being open, right? There's the agility piece, the innovation piece. That's a no-brainer. The question is how do we get there? And I think that's where partnerships become critical to get there, right? So we've been working with partners like Wind River to build solutions that make it easier for customers to start adopting some of the foundational elements of an open network. The, one of the purposes in the agenda of building this community is to bring like-minded developers, like you said like we want those guys to come and work with the customers to create new solutions, and come up with something creative, which no one's even thought about, that accelerates your option even quicker, right? So that's exactly what we want to do as well. And that's one of the reasons why we launched the community. >> Yeah, and what we find with a lot of carriers, they are used to buying, like I said, traditional RAN solutions which are provided from a single provider like Erickson or Nokia and others, right? And we break this apart, and you cloudify that network infrastructure, there's usually a skills gap we see at the operator level, right? And so from a developer standpoint, they struggle with having the expertise in order to execute on that. Wind River helps them, working with companies like Dell, simplify that bottom portion of the stack, the infrastructure stack. So, and we lifecycle manage it, we test- we're continually testing it, and integrating it, so that the operator doesn't have to do that. In addition to that, wind River also has a history and legacy of working with different RAN vendors, both disruptors like Mavenir and Parallel Wireless, as well as traditional RAN providers like Samsung, Erickson, and others soon to be announced. So what we're doing on the northbound side is making it easy by integrating that, and on the southbound side with Dell, so that again, instead of four or five solutions that you need to put together, it's simply two. >> And you think about today how we- how you consume telco services are like there's these fixed blocks of services that you can buy, that has to change. It's more like the, the app stores. It's got to be an open marketplace, and that's where the innovation's going to come in, you know, from the developers, you know, top down maybe. I don't know, how do you see that maturity model evolving? People want to know how long it's going to take. So many questions, when will Open RAN be as reliable. Does it even have to be? You know, so many interesting dynamics going on. >> Yeah, and I think that's something we at Dell are also trying to find out, right? So we have been doing a lot of good work here to help our customers move in that direction. The work with Dish is an example of that. But I think we do understand the challenges as well in terms of getting, adopting the technologies, and adopting the innovation that's being driven by Open. So one of the agendas that we have as a company this year is to work with the community to drive this a lot further, right? We want to have customers adopt the technology more broadly with the tier one, tier two telcos globally. And our sales organizations are going to be working together with Wind Rivers to figure out who's the right set of customers to have these conversations with, so we can drop, drive, start driving this agenda a lot quicker than what we've seen historically. >> And where are you having those customer conversations? Is that at the operator level, is it higher, is it both? >> Well, all operators are deploying 5G in preparation for 6G, right? And we're all looking for those killer use cases which will drive top line revenue and not just make it a TCO discussion. And that starts at a very basic level today by doing things like integrating with Juniper, for their cloud router. So instead of at the far edge cell site, having a separate device that's doing the routing function, right? We take that and we cloudify that application, run it on the same server that's hosting the RAN applications, so you eliminate a device and reduce TCO. Now with Aptiv, which is primarily known as an automotive company, we're having lots of conversations, including with Dell and Intel and others about vehicle to vehicle communication, vehicle to anything communication. And although that's a little bit futuristic, there are shorter term use cases that, like, vehicle to vehicle accident avoidance, which are going to be much nearer term than autonomous driving, for example, which will help drive traffic and new revenue streams for operators. >> So, oh, that's, wow. So many other things (Scott laughs) that's just opened up there too. But I want to come back to, sort of, the Open RAN adoption. And I think you're right, there's a lot of questions that that still have to be determined. But my question is this, based on your knowledge so far does it have to be as hardened and reliable, obviously has to be low latency as existing networks, or can flexibility, like the cloud when it first came out, wasn't better than enterprise IT, it was just more flexible and faster, and you could rent it. And, is there a similar dynamic here where it doesn't have to replicate the hardened stack, it can bring in new benefits that drive adoption, what are your thoughts on that? >> Well there's a couple of things on that, because Wind River, as you know, where our legacy and history is in embedded devices like F-15 fighter jets, right? Or the Mars Rover or the James Web telescope, all run Wind River software. So, we know about can't fail ultra reliable systems, and operators are not letting us off the hook whatsoever. It has to be as hardened and locked down, as secure as a traditional RAN environment. Otherwise they will (indistinct). >> That's table stakes. >> That's table stakes that gets us there. And when River, with our legacy and history, and having operator experience running live commercial networks with a disaggregated stack in the tens of thousands of nodes, understand what this is like because they're running live commercial traffic with live customers. So we can't fail, right? And with that, they want their cake and eat it too, right? Which is, I want ultra reliable, I want what I have today, but I want the agility and flexibility to onboard third party apps. Like for example, this JCNR, this Juniper Cloud-Native Router. You cannot do something as simple as that on a traditional RAN Appliance. In an open ecosystem you can take that workload and onboard it because it is an open ecosystem, and that's really one of the true benefits. >> So they want the mainframe, but they want (Scott laughs) the flexibility of the developer cloud, right? >> That's right. >> They want their, have their cake eat it too and not gain weight. (group laughs) >> Yeah I mean David, I come from the public cloud world. >> We all don't want to do that. >> I used to work with a public cloud company, and nine years ago, public cloud was in the same stage, where you would go to a bank, and they would be like, we don't trust the cloud. It's not secure, it's not safe. It was the digital natives that adopted it, and that that drove the industry forward, right? And that's where the enterprises that realized that they're losing business because of all these innovative new companies that came out. That's what I saw over the last nine years in the cloud space. I think in the telco space also, something similar might happen, right? So a lot of this, I mean a lot of the new age telcos are understanding the value, are looking to innovate are adopting the open technologies, but there's still some inertia and hesitancy, for the reasons as Scott mentioned, to go there so quickly. So we just have to work through and balance between both sides. >> Yeah, well with that said, if there's still some inertia, but there's a theme of velocity, how do you help organizations balance that so they trust evolving? >> Yeah, and I think this is where our solution, like infrastructure block, is a foundational pillar to make that happen, right? So if we can take away the concerns that the organizations have in terms of security, reliability from the fundamental elements that build their infrastructure, by working with partners like Wind River, but Dell takes the ownership end-to-end to make sure that service works and we have those telco grade SLAs, then the telcos can start focusing on what's next. The applications and the customer services on the top. >> Customer service customer experience. >> You know, that's an interesting point Gautam brings up, too, because support is an issue too. We all talk about when you break these things apart, it creates integration points that you need to manage, right? But there's also, so the support aspect of it. So imagine if you will, you had one vendor, you have an outage, you call that one vendor, one necktie to choke, right, for accountability for the network. Now you have four or five vendors that you have to work. You get a lot of finger pointing. So at least at the infrastructure layer, right? Dell takes first call support for both the hardware infrastructure and the Wind River cloud infrastructure for both. And we are training and spinning them up to support, but we're always behind them of course as well. >> Can you give us a favorite customer example of- that really articulates the value of the partnership and the technologies that it's delivering to customers? >> Well, Infra Block- >> (indistinct) >> Is quite new, and we do have our first customer which is LG U plus, which was announced yesterday. Out of Korea, small customer, but a very important one. Okay, and I think they saw the value of the integrated system. They don't have the (indistinct) expertise and they're leveraging Dell and Wind River in order to make that happen. But I always also say historically before this new offering was Vodafone, right? Vodafone is a leader in Europe in terms of Open RAN, been very- Yago and Paco have been very vocal about what they're doing in Open RAN, and Dell and Wind River have been there with them every step of the way. And that's what I would say, kind of, led up to where we are today. We learned from engagements like Vodafone and I think KDDI as well. And it got us where we are today and understanding what the operators need and what the impediments are. And this directly addresses that. >> Those are two very different examples. You were talking about TCO before. I mean, so the earlier example is, that's an example to me of a disruptor. They'll take some chances, you know, maybe not as focused on TCO, of course they're concerned about it. Vodafone I would think very concerned about TCO. But I'm inferring from your comments that you're trying to get the industry, you're trying to check the TCO box, get there. And then move on to higher levels of value monetization. The TCO is going to come down to how many humans it takes to run the network, is it not, is that- >> Well a lot of, okay- >> Or is it devices- >> So the big one now, particularly with Vodafone, is energy cost, right? >> Of course, greening the network. >> Two-thirds of the energy consumption in RAN is the the Radio Access Network. Okay, the OPEX, right? So any reductions, even if they're 5% or 10%, can save tens or hundreds of millions of dollars. So we do things creatively with Dell to understand if there's a lot of traffic at the cell site and if it's not, we will change the C state or P state of the server, which basically spins it down, so it's not consuming power. But that's just at the infrastructure layer. Where this gets really powerful is working with the RAN vendors like Samsung and Ericson and others, and taking data from the traffic information there, applying algorithms to that in AI to shut it down and spin it back up as needed. 'Cause the idea is you don't want that thing powered up if there's no traffic on it. >> Well there's a sustainability, ESG, benefit to that, right? >> Yes. >> And, and it's very compute intensive. >> A hundred percent. >> Which is great for Dell. But at the same time, if you're not able to manage that power consumption, the whole thing fails. I mean it's, because there's going to be so much data, and such a intense requirement. So this is a huge issue. Okay, so Scott, you're saying that in the TCO equation, a big chunk is energy consumption? >> On the OPEX piece. Now there's also the CapEx, right? And Open RAN solutions are now, what we've heard from our customers today, are they're roughly at parity. 'Cause you can do things like repurpose servers after the useful life for a lower demand application which helps the TCO, right? Then you have situations like Juniper, where you can take, now software that runs on the same device, eliminating at a whole other device at the cell site. So we're not just taking a server and software point of view, we're taking a whole cell site point of view as it relates to both CapEx and OPEX. >> And then once that infrastructure it really gets adopted, that's when the innovation occurs. The ecosystem comes in. Developers now start to think of new applications that we haven't thought of yet. >> Gautam: Exactly. >> And that's where, that's going to force the traditional carriers to respond. They're responding, but they're doing so very carefully right now, it's understandable why. >> Yeah, and I think you're already seeing some news in the, I mean Nokia's announcement yesterday with the rebranding, et cetera. That's all positive momentum in my opinion, right? >> What'd you think of the logo? >> I love the logo. >> I liked it too. (group laughs) >> It was beautiful. >> I thought it was good. You had the connectivity down below, You need pipes, right? >> Exactly. >> But you had this sort of cool letters, and then the the pink horizon or pinkish, it was like (Scott laughs) endless opportunity. It was good, I thought it was well thought out. >> Exactly. >> Well, you pick up on an interesting point there, and what we're seeing, like advanced carriers like Dish, who has one of the true Open RAN networks, publishing APIs for programmers to build in their 5G network as part of the application. But we're also seeing the network equipment providers also enable carriers do that, 'cause carriers historically have not been advanced in that way. So there is a real recognition that in order for these networks to monetize new use cases, they need to be programmable, and they need to publish standard APIs, so you can access the 5G network capabilities through software. >> Yeah, and the problem from the carriers, there's not enough APIs that the carriers have produced yet. So that's where the ecosystem comes in, is going to >> A hundred percent >> I think there's eight APIs that are published out of the traditional carriers, which is, I mean there's got to be 8,000 for a marketplace. So that's where the open ecosystem really has the advantage. >> That's right. >> That's right. >> That's right. >> Yeah. >> So it all makes sense on paper, now you just, you got a lot of work to do. >> We got to deliver. Yeah, we launched it today. We got to get some like-minded partners and customers to come together. You'll start seeing results coming out of this hopefully soon, and we'll talk more about it over time. >> Dave: Great Awesome, thanks for sharing with us. >> Excellent. Guys, thank you for sharing, stopping by, sharing what's going on with Dell and Wind River, and why the opportunity's in it for customers and the technological evolution. We appreciate it, you'll have to come back, give us an update. >> Our pleasure, thanks for having us. (Group talks over each other) >> All right, thanks guys >> Appreciate it. >> For our guests and for Dave Vellante, I'm Lisa Martin. You're watching theCUBE, Live from MWC23 in Barcelona. theCUBE is the leader in live tech coverage. (upbeat music)

(lively music) >> Good morning. Welcome back to theCUBE's coverage at Supercomputing Conference 2022, live here in Dallas. I'm Dave Nicholson with my co-host Paul Gillin. So far so good, Paul? It's been a fascinating morning Three days in, and a fascinating guest, Ian from AWS. Welcome. >> Thanks, Dave. >> What are we going to talk about? Batch computing, HPC. >> We've got a lot, let's get started. Let's dive right in. >> Yeah, we've got a lot to talk about. I mean, first thing is we recently announced our batch support for EKS. EKS is our Kubernetes, managed Kubernetes offering at AWS. And so batch computing is still a large portion of HPC workloads. While the interactive component is growing, the vast majority of systems are just kind of fire and forget, and we want to run thousands and thousands of nodes in parallel. We want to scale out those workloads. And what's unique about our AWS batch offering, is that we can dynamically scale, based upon the queue depth. And so customers can go from seemingly nothing up to thousands of nodes, and while they're executing their work they're only paying for the instances while they're working. And then as the queue depth starts to drop and the number of jobs waiting in the queue starts to drop, then we start to dynamically scale down those resources. And so it's extremely powerful. We see lots of distributed machine learning, autonomous vehicle simulation, and traditional HPC workloads taking advantage of AWS Batch. >> So when you have a Kubernetes cluster does it have to be located in the same region as the HPC cluster that's going to be doing the batch processing, or does the nature of batch processing mean, in theory, you can move something from here to somewhere relatively far away to do the batch processing? How does that work? 'Cause look, we're walking around here and people are talking about lengths of cables in order to improve performance. So what does that look like when you peel back the cover and you look at it physically, not just logically, AWS is everywhere, but physically, what does that look like? >> Oh, physically, for us, it depends on what the customer's looking for. We have workflows that are all entirely within a single region. And so where they could have a portion of say the traditional HPC workflow, is within that region as well as the batch, and they're saving off the results, say to a shared storage file system like our Amazon FSx for Lustre, or maybe aging that back to an S3 object storage for a little lower cost storage solution. Or you can have customers that have a kind of a multi-region orchestration layer to where they say, "You know what? "I've got a portion of my workflow that occurs "over on the other side of the country "and I replicate my data between the East Coast "and the West Coast just based upon business needs. "And I want to have that available to customers over there. "And so I'll do a portion of it in the East Coast "a portion of it in the West Coast." Or you can think of that even globally. It really depends upon the customer's architecture. >> So is the intersection of Kubernetes with HPC, is this relatively new? I know you're saying you're, you're announcing it. >> It really is. I think we've seen a growing perspective. I mean, Kubernetes has been a long time kind of eating everything, right, in the enterprise space? And now a lot of CIOs in the industrial space are saying, "Why am I using one orchestration layer "to manage my HPC infrastructure and another one "to manage my enterprise infrastructure?" And so there's a growing appreciation that, you know what, why don't we just consolidate on one? And so that's where we've seen a growth of Kubernetes infrastructure and our own managed Kubernetes EKS on AWS. >> Last month you announced a general availability of Trainium, of a chip that's optimized for AI training. Talk about what's special about that chip or what is is customized to the training workloads. >> Yeah, what's unique about the Trainium, is you'll you'll see 40% price performance over any other GPU available in the AWS cloud. And so we've really geared it to be that most price performance of options for our customers. And that's what we like about the silicon team, that we're part of that Annaperna acquisition, is because it really has enabled us to have this differentiation and to not just be innovating at the software level but the entire stack. That Annaperna Labs team develops our network cards, they develop our ARM cards, they developed this Trainium chip. And so that silicon innovation has become a core part of our differentiator from other vendors. And what Trainium allows you to do is perform similar workloads, just at a lower price performance. >> And you also have a chip several years older, called Inferentia- >> Um-hmm. >> Which is for inferencing. What is the difference between, I mean, when would a customer use one versus the other? How would you move the workload? >> What we've seen is customers traditionally have looked for a certain class of machine, more of a compute type that is not as accelerated or as heavy as you would need for Trainium for their inference portion of their workload. So when they do that training they want the really beefy machines that can grind through a lot of data. But when you're doing the inference, it's a little lighter weight. And so it's a different class of machine. And so that's why we've got those two different product lines with the Inferentia being there to support those inference portions of their workflow and the Trainium to be that kind of heavy duty training work. >> And then you advise them on how to migrate their workloads from one to the other? And once the model is trained would they switch to an Inferentia-based instance? >> Definitely, definitely. We help them work through what does that design of that workflow look like? And some customers are very comfortable doing self-service and just kind of building it on their own. Other customers look for a more professional services engagement to say like, "Hey, can you come in and help me work "through how I might modify my workflow to "take full advantage of these resources?" >> The HPC world has been somewhat slower than commercial computing to migrate to the cloud because- >> You're very polite. (panelists all laughing) >> Latency issues, they want to control the workload, they want to, I mean there are even issues with moving large amounts of data back and forth. What do you say to them? I mean what's the argument for ditching the on-prem supercomputer and going all-in on AWS? >> Well, I mean, to be fair, I started at AWS five years ago. And I can tell you when I showed up at Supercomputing, even though I'd been part of this community for many years, they said, "What is AWS doing at Supercomputing?" I know you care, wait, it's Amazon Web Services. You care about the web, can you actually handle supercomputing workloads? Now the thing that very few people appreciated is that yes, we could. Even at that time in 2017, we had customers that were performing HPC workloads. Now that being said, there were some real limitations on what we could perform. And over those past five years, as we've grown as a company, we've started to really eliminate those frictions for customers to migrate their HPC workloads to the AWS cloud. When I started in 2017, we didn't have our elastic fabric adapter, our low-latency interconnect. So customers were stuck with standard TCP/IP. So for their highly demanding open MPI workloads, we just didn't have the latencies to support them. So the jobs didn't run as efficiently as they could. We didn't have Amazon FSx for Lustre, our managed lustre offering for high performant, POSIX-compliant file system, which is kind of the key to a large portion of HPC workloads is you have to have a high-performance file system. We didn't even, I mean, we had about 25 gigs of networking when I started. Now you look at, with our accelerated instances, we've got 400 gigs of networking. So we've really continued to grow across that spectrum and to eliminate a lot of those really, frictions to adoption. I mean, one of the key ones, we had a open source toolkit that was jointly developed by Intel and AWS called CFN Cluster that customers were using to even instantiate their clusters. So, and now we've migrated that all the way to a fully functional supported service at AWS called AWS Parallel Cluster. And so you've seen over those past five years we have had to develop, we've had to grow, we've had to earn the trust of these customers and say come run your workloads on us and we will demonstrate that we can meet your demanding requirements. And at the same time, there's been, I'd say, more of a cultural acceptance. People have gone away from the, again, five years ago, to what are you doing walking around the show, to say, "Okay, I'm not sure I get it. "I need to look at it. "I, okay, I, now, oh, it needs to be a part "of my architecture but the standard questions, "is it secure? "Is it price performant? "How does it compare to my on-prem?" And really culturally, a lot of it is, just getting IT administrators used to, we're not eliminating a whole field, right? We're just upskilling the people that used to rack and stack actual hardware, to now you're learning AWS services and how to operate within that environment. And it's still key to have those people that are really supporting these infrastructures. And so I'd say it's a little bit of a combination of cultural shift over the past five years, to see that cloud is a super important part of HPC workloads, and part of it's been us meeting the the market segment of where we needed to with innovating both at the hardware level and at the software level, which we're going to continue to do. >> You do have an on-prem story though. I mean, you have outposts. We don't hear a lot of talk about outposts lately, but these innovations, like Inferentia, like Trainium, like the networking innovation you're talking about, are these going to make their way into outposts as well? Will that essentially become this supercomputing solution for customers who want to stay on-prem? >> Well, we'll see what the future lies, but we believe that we've got the, as you noted, we've got the hardware, we've got the network, we've got the storage. All those put together gives you a a high-performance computer, right? And whether you want it to be redundant in your local data center or you want it to be accessible via APIs from the AWS cloud, we want to provide that service to you. >> So to be clear, that's not that's not available now, but that is something that could be made available? >> Outposts are available right now, that have this the services that you need. >> All these capabilities? >> Often a move to cloud, an impetus behind it comes from the highest levels in an organization. They're looking at the difference between OpEx versus CapEx. CapEx for a large HPC environment, can be very, very, very high. Are these HPC clusters consumed as an operational expense? Are you essentially renting time, and then a fundamental question, are these multi-tenant environments? Or when you're referring to batches being run in HPC, are these dedicated HPC environments for customers who are running batches against them? When you think about batches, you think of, there are times when batches are being run and there are times when they're not being run. So that would sort of conjure, in the imagination, multi-tenancy, what does that look like? >> Definitely, and that's been, let me start with your second part first is- >> Yeah. That's been a a core area within AWS is we do not see as, okay we're going to, we're going to carve out this super computer and then we're going to allocate that to you. We are going to dynamically allocate multi-tenant resources to you to perform the workloads you need. And especially with the batch environment, we're going to spin up containers on those, and then as the workloads complete we're going to turn those resources over to where they can be utilized by other customers. And so that's where the batch computing component really is powerful, because as you say, you're releasing resources from workloads that you're done with. I can use those for another portion of the workflow for other work. >> Okay, so it makes a huge difference, yeah. >> You mentioned, that five years ago, people couldn't quite believe that AWS was at this conference. Now you've got a booth right out in the center of the action. What kind of questions are you getting? What are people telling you? >> Well, I love being on the show floor. This is like my favorite part is talking to customers and hearing one, what do they love, what do they want more of? Two, what do they wish we were doing that we're not currently doing? And three, what are the friction points that are still exist that, like, how can I make their lives easier? And what we're hearing is, "Can you help me migrate my workloads to the cloud? "Can you give me the information that I need, "both from a price for performance, "for an operational support model, "and really help me be an internal advocate "within my environment to explain "how my resources can be operated proficiently "within the AWS cloud." And a lot of times it's, let's just take your application a subset of your applications and let's benchmark 'em. And really that, AWS, one of the key things is we are a data-driven environment. And so when you take that data and you can help a customer say like, "Let's just not look at hypothetical, "at synthetic benchmarks, let's take "actually the LS-DYNA code that you're running, perhaps. "Let's take the OpenFOAM code that you're running, "that you're running currently "in your on-premises workloads, "and let's run it on AWS cloud "and let's see how it performs." And then we can take that back to your to the decision makers and say, okay, here's the price for performance on AWS, here's what we're currently doing on-premises, how do we think about that? And then that also ties into your earlier question about CapEx versus OpEx. We have models where actual, you can capitalize a longer-term purchase at AWS. So it doesn't have to be, I mean, depending upon the accounting models you want to use, we do have a majority of customers that will stay with that OpEx model, and they like that flexibility of saying, "Okay, spend as you go." We need to have true ups, and make sure that they have insight into what they're doing. I think one of the boogeyman is that, oh, I'm going to spend all my money and I'm not going to know what's available. And so we want to provide the, the cost visibility, the cost controls, to where you feel like, as an HPC administrator you have insight into what your customers are doing and that you have control over that. And so once you kind of take away some of those fears and and give them the information that they need, what you start to see too is, you know what, we really didn't have a lot of those cost visibility and controls with our on-premises hardware. And we've had some customers tell us we had one portion of the workload where this work center was spending thousands of dollars a day. And we went back to them and said, "Hey, we started to show this, "what you were spending on-premises." They went, "Oh, I didn't realize that." And so I think that's part of a cultural thing that, at an HPC, the question was, well on-premises is free. How do you compete with free? And so we need to really change that culturally, to where people see there is no free lunch. You're paying for the resources whether it's on-premises or in the cloud. >> Data scientists don't worry about budgets. >> Wait, on-premises is free? Paul mentioned something that reminded me, you said you were here in 2017, people said AWS, web, what are you even doing here? Now in 2022, you're talking in terms of migrating to cloud. Paul mentioned outposts, let's say that a customer says, "Hey, I'd like you to put "in a thousand-node cluster in this data center "that I happen to own, but from my perspective, "I want to interact with it just like it's "in your data center." In other words, the location doesn't matter. My experience is identical to interacting with AWS in an AWS data center, in a CoLo that works with AWS, but instead it's my physical data center. When we're tracking the percentage of IT that's that is on-prem versus off-prem. What is that? Is that, what I just described, is that cloud? And in five years are you no longer going to be talking about migrating to cloud because people go, "What do you mean migrating to cloud? "What do you even talking about? "What difference does it make?" It's either something that AWS is offering or it's something that someone else is offering. Do you think we'll be at that point in five years, where in this world of virtualization and abstraction, you talked about Kubernetes, we should be there already, thinking in terms of it doesn't matter as long as it meets latency and sovereignty requirements. So that, your prediction, we're all about insights and supercomputing- >> My prediction- >> In five years, will you still be talking about migrating to cloud or will that be something from the past? >> In five years, I still think there will be a component. I think the majority of the assumption will be that things are cloud-native and you start in the cloud and that there are perhaps, an aspect of that, that will be interacting with some sort of an edge device or some sort of an on-premises device. And we hear more and more customers that are saying, "Okay, I can see the future, "I can see that I'm shrinking my footprint." And, you can see them still saying, "I'm not sure how small that beachhead will be, "but right now I want to at least say "that I'm going to operate in that hybrid environment." And so I'd say, again, the pace of this community, I'd say five years we're still going to be talking about migrations, but I'd say the vast majority will be a cloud-native, cloud-first environment. And how do you classify that? That outpost sitting in someone's data center? I'd say we'd still, at least I'll leave that up to the analysts, but I think it would probably come down as cloud spend. >> Great place to end. Ian, you and I now officially have a bet. In five years we're going to come back. My contention is, no we're not going to be talking about it anymore. >> Okay. >> And kids in college are going to be like, "What do you mean cloud, it's all IT, it's all IT." And they won't remember this whole phase of moving to cloud and back and forth. With that, join us in five years to see the result of this mega-bet between Ian and Dave. I'm Dave Nicholson with theCUBE, here at Supercomputing Conference 2022, day three of our coverage with my co-host Paul Gillin. Thanks again for joining us. Stay tuned, after this short break, we'll be back with more action. (lively music)

(upbeat music) >> Hello and welcome to theCUBE. I'm Dave Nicholson, Chief Technology Officer at theCUBE and we are here for a very special Cube Conversation with Andy Brown from Broadcom. Andy, welcome to theCUBE, tell us a little about yourself. >> Well, a little bit about myself, my name is Andy Brown, I'm currently the Senior Director of Software Architecture and Performance Analysis here within the Data Center Solutions Group at Broadcom. I've been doing that for about seven years prior to that, I held various positions within the system architecture, systems engineering, and IC development organization, but ultimately as well as spent some time in our support organization and managing our support team. But ultimately have landed in the architecture organization as well as performance analysis. >> Great, so a lot of what you do is around improving storage performance, tell us more about that. >> So let me give you a brief history of storage from my perspective. As I mentioned, I go back about 30 years in my career and that would've started back in the NCR Microelectronics days. And originally with Parallel SCSI, so that would be, if anyone would remember the the 5380 Controller, which was one of the original Parallel SCSI controllers that existed in built by NCR Microelectronics at the time, I've seen the advent of Parallel SCSI, a stint of fiber channel, ultimately leading into the serialization of the SCSI standard into SaaS, as well as SATA, and then ultimately leading to NVMe protocols and the advent of flash moving from hard drives into a flash based media and as well on that's on the storage side on the host side, moving from parallel interfaces, ISA if everybody could remember that, moving to PCI, PCI Express and that's where we land today. >> So Andy, we are square in the middle of the era of both NVMe and SaaS. What kinds of challenges does that overlap represent? >> Well, I think obviously we've seen SaaS around for a while, it was the conversion from parallel into a serial attached SCSI and that really SaaS brings with it, the ability to connect really a high number of devices and was kind of the original scaling of devices. And really also enabled was one of the things that enabled flash based media, given the the speed and performance that came to the table. Of course NVMe came in as well with the promise of even higher speeds. And as we saw flash media really, really take a strong role in storage. NVMe came around and really was focused on trying to address that, whereas SaaS originated with hard drive technology. NVMe was really born out of how do we most efficiently deal with flash based media, SaaS with its. But SaaS still carries a benefit on scalability and NVMe maybe has, I don't want to say challenges there, but it's definitely was not designed as much to be broadly scale across many, many, say high hundreds or thousands of devices. But definitely addressed some of the performance issues that were coming up as flash media was becoming. So it was increasing the overall storage performance that we could experience if you will. >> Let's talk about host interfaces, PCIe. What's the significance there? >> Really all the storage in the world, all the performance in the world on the storage side, is not of much use to you unless you can really feed it into the beast, if you will, into the CPU and into the the rest of the service subsystem. And that's really where PCI comes into play. PCI originally was in parallel form and then moved to serial with the PCI Express as we know it today, and really has created a pathway to enable not only storage performance but any other adapter or any other networking or other types of technologies to just open up that pathway and feed the processor. And as we've moved through from PCI to PCI Express PCI 2.0 3.0 4.0, and just opening up those pipes has really enabled just a tremendous amount of flow of data into the compute engine, allowing it to be analyzed, sorted used to analyze data, big data, AI type applications. Just those pipes are critical in those types of applications. >> We know we've seen dramatic increases in performance, going from one generation of PCIe to the next. But how does that translate into the worlds of SaaS, SATA and NVMe? >> So from a performance perspective when we look at these different types of media whether it be SATA, SaaS or NVMe, of course, there are performance difference inherent in that media, SATA being probably the lowest performing with NVMe topping out at higher performing although SaaS can perform quite well as a flash based as protocol connected to flash based media. And of course, NVMe from an individual device scaling, from a by one to a by four interface, really that is where NVMe kind of has enabled a bigger pipe directly to the storage media, being able to scale up to by four whereas SaaS can limit it to by one, maybe by two in some cases, although most servers only connect the SaaS device of by one. So from a different perspective then you're really wanting to create a solution or enable the infrastructure to be able to consume that performance at NVMe is going to give you. And I think that is something where our solutions have really in the recent generation shined, at their ability to really now keep up with storage performance and NVMe, as well as provide that connectivity back down into the SaaS and SATA world as well. >> Let's talk about your perspective on RAID today. >> So there've been a lot of views and opinions on RAID over the years, it's been and those have been changing over time. RAID has been around for a very, very long time, probably about as long as again, going back over my 30 year career, it's been around for almost the entire time. Obviously RAID originally was viewed as some thing that was very, very necessary devices fail. They don't last forever, but the data that's on them is very, very important and people care about that. So RAID was brought about knowing that individual devices that are storing that data are going to fail, and really took cold as a primary mechanism of protection. But as time went on and as performance moved up both in the server and both in the media itself if we start talking about flash. RAID really took on, people started to look at traditional server storage RAID, well, maybe a more of a negative connotation. I think that because to be quite honest, it fell behind a little bit. If you look at things like parity RAID 5 and RAID 6, very, very effective efficient means of protecting your data, very storage efficient, but ultimately had some penalty a primarily around right performance, random rights in RAID 5 volumes was not keeping up with what really needed to be there. And I think that really shifted opinions of RAID that, "Hey it's just not, it's not going to keep up and we need to move on to other avenues." And we've seen that, we've seen disaggregated storage and other solutions pop up and protect your data obviously in cloud environments and things like that have shown up and they have been successful, but. >> So one of the drawbacks with RAID is always the performance tax associated with generating parody for parody RAID. What has Broadcom done to address those potential bottlenecks? >> We've really solved the RAID performance issue the right performance issue. We're in our latest generation of controllers we're exceeding a million RAID 5 right IOPS which is enough to satisfy many, many, many applications as a matter of fact, even in virtual environments aggregated solutions, we have multiple applications. And then as well in the rebuild arena, we really have through our architecture, through our hardware automation have been able to move the bar on that to where the rebuild not only the rebuild times have been brought down dramatically in SaaS based or in I'm sorry in flash based solutions. But the performance that you can observe while those rebuilds are going on is almost immeasurable. So in most applications you would almost observe no performance deficiencies during a rebuild operation which is really night and day compared to where things were just few short years ago. >> So the fact that you've been able to, dramatically decrease the time necessary for a RAID rebuild is obviously extremely important. But give us your overall performance philosophy from Broadcom's point of view. >> Over the years we have recognized that performance is obviously a critically important for our products, and the ability to analyze performance from many many angles is critically important. There are literally infinite ways you can look at performance in a storage subsystem. What we have done in our labs and in our solutions through not only hardware scaling in our labs, but also through automation scripts and things like that, have allowed us to collect a substantial amount of data to look at the performance of our solutions from every angle. IOPS, bandwidth application level performance, small topologies, large topologies, just many, many aspects. It still honestly only scratches the surface of all the possible performance points that you could gather, but we have moved them bar dramatically in that regard. And it's something that our customers really demanded of us. Storage technology has gotten more complex, and you have to look at it from a lot different angles, especially on the performance front to make sure that there are no holes there that somebody's going to run into. >> So based on specific customer needs and requests, you look at performance from a variety of different angles. What are some of the trends that you're seeing specifically in storage per performance today and moving into the future? >> Yeah, emerging trends within the storage industry. I think that to look at the emerging trends, you really need to go back and look at where we started. We started in compute where people were you would have basically your server that would be under the desk in a small business operation and individual businesses would have their own set of servers, and the storage would really be localized to those. Obviously the industry has recognized that to some extent, disaggregation of that, we see that obviously in what's happening in cloud, in hyper-converged storage and things like that. Those afford a tremendous amount of flexibility and are obviously great players in the storage world today. But with that flexibility has come some sacrifice and performance and actually quite substantial sacrifice. And what we're observing is almost, it comes back full circle. The need for inbox high performing server storage that is well protected. And with people with confidence that people have confidence that their data is protected and that they can extract the performance that they need for the demanding database applications, that still exists today, and that still operate in the offices around the country and around the world, that really need to protect their data on a local basis in the server. And I think that from a trend perspective that's what we're seeing. We also, from the standpoint of NVMe itself is really started out with, "Hey, we'll just software rate that. We'll just wrap software around that, we can protect the data." We had so many customers come back to us saying, you know what? We really need hardware RAID on NVMe. And when they came to us, we were ready. We had a solution ready to go, and we're able to provide that, and now we're seeing ongoing on demand. We are complimentary to other storage solutions out there. Server storage is not going to necessarily rule a world but it is surely has a place in the broader storage spectrum. And we think we have the right solution for that. >> Speaking of servers and server-based storage. Why would, for example, a Dell customer care about the Broadcom components in that Dell server. >> So let's say you're configuring a Dell server and you're going, why does hardware where RAID matter? What's important about that? Well, I think when you look at today's hardware RAID, first of all, you're going to see a dramatically better performance. You're going to see dramatically better performance it's going to enable you to put RAID 5 volumes a very effective and efficient mechanism for protecting your data, a storage efficient mechanism. You're going to use RAID 5 volumes where you weren't able to do that before, because when you're in the millions of IOPS range you really can satisfy a lot of application needs out there. And then you're going to also going to have rebuilt times that are lightning fast. Your performance is not going to degrade, when you're running those application, especially database applications, but not only database, but streaming applications, bandwidth to protected RAID volumes is almost imperceptively different from just raw bandwidth to the media. So the RAID configurations in today's Dell servers really afford you the opportunity to make use of that storage where you may not have already written it off as well RAID just doesn't, is not going to get me there. Quite frankly, into this in the storage servers that Dell is providing with RAID technology, there are huge windows open in what you can do today with applications. >> Well, all of this is obviously good news for Dell and Dell customers, thanks again, Andy for joining us, for this Cube Conversation, I'm Dave Nicholson for theCUBE. (upbeat music)

>>Okay, welcome back everyone. To the cubes coverage of AWS summit, 2022 in San Francisco, California. We're here, live on the floor at the Mosconi south events are back. I'm John fur, your host. Remember AWS summit 2022 in New York city is coming this summer. We'll be there with the live cube there as well. Look for us there, but of course, we're back in action with the cloud and AWS. Our next guest Garrett Miller is the general manager of navigation at Mapbox. I mean, it's been a Amazon customer for a long time, Garrett. Thanks for coming on the cube. >>Yeah. Thanks for having us, John. >>So you guys are in the middle of, I love the whole location base slash we developer integration. We've had many conversations on the cube around how engineers and developers are becoming embedded into the application, whether it's from a security standpoint, biometrics, all kinds of stuff, being built into the app and, and location navigation. That's right. Is huge from cars. Everyone knows their car, car map. That's right. GPS satellites, some space it's complicated. It sounds like it sounds easy, but I know it's hard. Yeah. You, you get the keynote going on today. Give us a quick update on Mapbox and we'll then we'll talk about the keynote. >>Yeah. You bet John that's right. So as you were saying, you know, it really is. It's all about location intelligence. And how does that get embedded into the applications? And to the point you made vehicles that are out there on the roads to today. So we target developers. Those are our key customers, and we've got over three and a half million registered on the platform today. They consume the modules that we build with APIs, SDKs, data sets, and more and more applications to accomplish whatever those location needs might be. >>Why we appreciate you coming on. You are featured keynote by presenter here at summit, which means Amazon thinks you're super important to share. I'll say your customer. So you, I know you've been a customer for a long time as a company, but what was your keynote about what was the main theme? The developers were all here. You got the builders. What was your content? What did you present this morning on the keynote? Yeah, >>Well, this morning we really talked a lot about logistics and the, this story that we told was know in the logistics industry, there is a massive movement to shorter and shorter delivery windows. And so the, the, the story that we told is really around a 10 minute delivery. Now, have you ever wondered how you get a 10 minute delivery? You, you place an order on your phone and all of a sudden somebody shows up at your front doorstep. You ever wonder about that? >><laugh> >>Some shows supply >>Chain. Someone's waiting in the wings from my call. >>Yeah. >>Yeah. Well, that's right. >>John's about to order sometime soon. That's right. You ready? That's right. Do all these assets. That's >>Right. They're all ready for you. But there's actually a tremendous amount that actually goes into that. And so it really starts with designing the right distribution system up front. And so we've got tools and, and applications and, and APIs that support that. And really it, every single step of the way, location is a critical aspect to making that delivery happen and getting it to a customer's doorstep in 10 minutes or less. And so how are you understanding the real time road graph that underlies a, a, a driver going from perhaps a dark store, dark kitchen to getting in, excuse me, in front of a customer in 10 minutes with hot food. >>I mean, this is a big point. I was just joking about waiting for me, you know, that, but the point is, is that it's not obvious, but it sounds really hard. I know it's hard because to have that delivery, a lot of things have to happen. It's not just knowing location. >>That's exactly >>Right. So can you just UN pull appeal back the covers on that? What's going on there? >>Yeah. So imagine this is, is, it really starts, as I was saying with designing that distribution system and it's putting in place where you might not expect it, it's actually putting in place a retail store, but these aren't any retail stores, right? These are dark stores. These are dark kitchens that are strategically placed as close as possible, the customer density, so that you can actually shorten that window as much as possible to get you whatever that order might be. But from there, it actually goes quite a bit further when an order actually comes in, you've gotta be able to understand how do I sign an, a driver to get that order to the customer in that, in that very short period of time, more often than not, it's getting it to the driver that can get there the fastest, once you've got the right driver identified, how are you actually then going to enable them to get from point a to B to get that order. >>And then perhaps from B to C to get to your front door, being able to do turn by turn navigation that reflects everything. That's how happening in the real world to be able to get there on a timely way is critical. And then wrapping around that actually the, the, the end customer's experience your experience with how are you placing that order? Yeah. How are you using Mapbox services to do that? How are you being able to track on your application and say, well, you know, great, I expect 10 minutes and they're five minutes away. Are you gonna show up our APIs and SDKs power? That experience, >>I wanna get into the product in a second, but you brought up something I think's important to highlight. One is dark kitchens, dark stores. That's right. Okay. Term people may or may not have heard of, we all have experience in COVID going to our favorite restaurant, which has been kind of downsized because of the COVID and we're waiting for our food. And someone comes in from another delivery ever standing in line next was just pick something up. I mean, they're going through the front door. That's like the, the, the branded store. So, so is it right to say that dark kitchens are essentially replicas of the store to minimize that traffic, but, but also to be efficient for something else that's right. >>It actually even goes further than that. There are many restaurant brands. Now, it only exists as a brand. They don't have a restaurant that you can go to and sit down and have that meal. They actually only operate dark kitchens to, to serve that demand of people wanting to order up, Hey, I want my food. I want it. Now, those brands exist to serve that need. >>All right. So great for the definition, we just define dark kitchens, dark stores, but also brings, I wanna get your reaction to this before we get into the product, cuz this is a trend that's right. This is not like a one off thing. That's right. It's not a pulled forward TA a market that was COVID enabled. This is actually a user experience inflection point. That's >>Right. >>Can you share your vision on what this means? Because there's mobile ordering, there's the dynamics of the kitchens as a supplier of something in stores. So that's content or a product that's being delivered to a consumer via of the web. So now there's gotta be a whole nother reef factoring of the operating environment. Now that's what's happening is that might get that >>Right? No, that's exactly right. And even if you step back, even further and you, you think about the, the journey that the logistics industry has been on, it used to be that two days was that really exciting delivery time. Right. And everybody got it super excited. Then it became next day. Then it became same day and now it's become 10 minutes. And even some companies are out there offering seven minute deliveries, right. And in order to do that, you've gotta completely retool your business. So you can think the logistics and industry really existing on two continuums, you've got pre-planned deliveries on one hand and on-demand deliveries on the other. And there are two parallel distribution systems and ecosystems and industries really springing up to serve those different types of demand. >>So you've been on Amazon web services customer for how many years, >>Since 2013 in our founding. And you know, actually we're really proud to say that we were born on Amazon and we have scaled on Amazon. >>How are they helping you scale? What are they doing to help you? >>Well, I'd say just about everything. And if you think about their, the, the services that Amazon provides for us, they power every single step of our business along the way. And so I'll give you an example. We can walk through that with some of the tech technology. I, if you think about again, how do you get 10 minutes? You gotta have a pretty precise understanding of what's going on in the real world. And so to do that, it, for us, it all starts with collecting billions and billions of data points from sensors that are out there in the world. We stream that into our technology stack, starting at the very beginning with Amazon ESIS. And so that's just the start. But then that feeds into our entire technology stack that all runs on site on top of AWS, to where we're running our own AI models that we use Amazon SageMaker to make, and then stream it back out to our AP, through our APIs, to our se Ks and applications that sit on the edge again, all leveraging Amazon technology. >>Well, I think this is a great use case and I'll get back into the, the Mapbox a second, but Amazon, you guys are executing what I call the super cloud vision, which is snowflake you guys building on their CapX leverage. You're building a super cloud on your own. It's your app, it's your cloud. >>That's right. That's right. So if you, again, if you think about it, you know, and actually just stepping back for a moment, tell about Mapbox for a second is what, what Mapbox can do is provide the most accurate digital representation of the physical world. Think about the Mapbox technology, delivering the most accurate digital twin of mother earth, right? That's what we do. And the way that we do that is to consume, as I said earlier, vast amounts of data, we've got powerful AI that structures that data, and then really robust and scalable infrastructure that underpins all of that. Now the benefit of working with a company like AWS is that they take care of that third point. Yeah. Which means we get to go focus on the first two, which is how we differentiate and build our >>Business. And that's exactly the model of how you win in the cloud. In my opinion, that's the go big piece, the go and there's tools that fit in white spaces. But that's the, I think that's the right formula. Let's get back to Mac boxer. I know you've got news. You got the, the, uh, Mapbox fleet SDK. You announced, I wanna hold on that we'll get to in a second, let's get back to what you got are providing that example as you have this new operating environment of how delivery and, and supply chain and that's example, I want to know how tech your technology is making all that work. Because I was just talking to someone last night about this web van was web 1.0 and crash never was successful. Instacart is kind of hurting. So maybe they're optimized. You could save them. I mean, cuz the economics gotta work. If you don't have the underlying system built, that might fail. So there'll be probably the third version that gets it. Right. Maybe at Mapbox again, I'm speculating, but I'll let you talk. Yeah. How does Mapbox solve the, that problem? >>You know, it's interesting if you come back to that, that, that analogy we're using with AWS and how do you use AWS to win in the cloud? It's the same story for Mapbox of how do you win in the location industry? And what we do is provide those same tool sets of APIs and SDKs, the thing go power, those logistics companies like an Instacart, who's a great customer of ours to run in their logistics business on top of it again, it's all about how do you provide technology that allows your customers yeah. To focus on what matters from a differentiation perspective as they focus on building their >>Business and you think your economics is gonna enable these people to be successful >>100%. That's >>The goal >>100%. >>All right. So another thing that I wanna bring up is the fleet SDK, what was the, that you announced they can, you just quickly share the news on what this >>Is? Yeah, yeah, absolutely. I appreciate that, John. Yeah. So today on the Eve of earth day, we're very excited to announce Mapbox fleet going into, uh, our beta launch and what Mapbox fleet is, is, uh, a set of tools and application that allows our customers to more efficiently route their vehicles, which means lowering their fuel consumption. And at the same time, more efficiently dispatching those vehicles, which means that you can get more done with fewer assets, essentially. How do you get more packages onto a single vehicle to get those to the customers? Now you may be watching the news and understanding, yeah, there's a tremendous explosion of delivery going. Yeah. And that's fantastic. Right? That's great business for our logistics customers. Good business for us too. What's happening though, is that as those volumes are ballooning, everybody's all of a sudden, really looking at their cost structures and trying to understand how do I manage this? >>Right. I have efficiency targets as a business. Maybe I've been really focused on customer acquisition. Now it's time to flip the model and really understand in the economics of profitable growth. We help with that, with that focus on efficiency, but the double edged sword with growth and, and you know, running a logistics business is that you actually have a tremendous amount of carbon emissions that are associated with that. Yeah. For a car to show up or a truck to show up, to deliver something to your house, their emissions associated with that. So what we find is that we're able to not only drive dollar savings for our customers, but also as part of that, with the efficiency angle, really help to drive down the overall carbon impact in the carbon footprint of what they do. And >>How do you do that? >>Well, it's the efficiency lens, right? So if somebody is driving 20%, fewer miles, they're going to emit 20% fewer. Okay. >>Gotcha. So it's a numbers game across the board with actual measurement. That's exactly right. Built in and say optimization paths, all kinds of navigation. >>That's exactly right. So embedded within Mapbox fleet application are those optimization algorithm. >>So you got a platform that's setting up for the next level delivery system slash new way to connect people to goods and services and other things getting from point a to point B, you got the sustainability check you're in the cloud, born in the cloud cloud scale. I gotta a, I can't go without asking if you're on Amazon, you do all this cool stuff. There's gotta be a machine learning an AI angle. So what is that? Yeah, absolutely. >>Absolutely. AB yeah. You know, <laugh> guilty as charged. >>I would say >>John. Uh, so look, I >>Think, I mean AI and, and sustainability are gonna be, I think filings in my, in the future we be talking about on the cube, if you're not an AI company or, and doing force for good stuff, I think there's gonna be mandatory requirements on those. >>I couldn't three more. I think the ESG agenda is an incredibly important one. One that's core to Mapbox has been since the founding of the company back in 2013. Uh, but if you look at how does AI and ML fit into Mapbox, it does that in a number of different ways. And really when we come back to this idea of Mapbox creating a digital twin of the earth, the way that we do that, it is through ingesting a tremendous amount of sensor data. Right? You can imagine, uh, Mapbox customers on any given week drive, billions of miles, we're capturing all of that telemetry data to understand and make sense of what does that mean for, for, for the world that allows us to push in any given day 700,000 updates to our underly, your location technology stack, and at the same time provide insights as to exactly what's happening. Are there roadside incidents? Are there, are there issues with traffic? So by collecting all of that data, we run incredibly powerful AI models on top of it that allow us to create the, the real world representation of what's happening. That's exactly how >>It works. What, what, as they say in the, um, big data AI world is you guys have a tremendous observation space. You're looking at a lot of surface area data that's exactly right. Across multiple workloads and apps. That's >>Exactly >>Right. You can connect those dots with the right AI. >>That's exactly right. That's exactly right. And I think I, you know, coming back to your point around sustainability, I do think that the AI and ML capabilities that are being delivered are going to be paramount to that. It being such a fundamental aspect to what am, to what Mapbox does as a business allows us to launch these game changing solutions like Mapbox fleet and staying on that, that kind of environmental and sustainable kick for a second. Just last week, we launched our, our EV routing API that powers the next generation of EVs. So AI ML sustainability. If it's not core business today, it's gotta very quickly become core. >>It's really interesting. I really think what we're teasing out here and it's fun to talk about it now because we'll look back at it later 10 years or more and say, wow, this is completely refactored the industry and lives and the planet ultimately. Right. So this is a, a kind of got force for good built into the system natively. That's >>Right. That's >>That's interesting, Garrett, thanks so much for sharing the story. Give you the last word, share with the audience, what you guys are up to, what you're promoting, what you're looking for. Are you hiring, uh, is there a call to action? You wanna share? Give the plug for the company? Yeah, >>Absolutely hiring like crazy come join Mapbox and BU build the future of geolocation and intelligent location services with us. Uh, the, thanks so much for the time, >>John. Thanks for coming on cube coverage here in San Francisco, California Mosconi center back at live events. I'm John for host cube stayed with us as day two wraps down. Remember New York city. This summer will be there as well. Cube coverage of more cloud coverage events are back. Thanks for watching.

(bright upbeat music) >> Hello, welcome to theCUBE, "Unstoppable Domains Showcase." I'm John Furrier, your host of theCUBE. We got a great discussion here called the influencers around what's going on Web 3.0. And also this new sea change, cultural change around this next generation, internet, web, cloud, all happening, Jeremiah Owyang, Industry Analyst and Founding Part of Kaleido Insights. Jeremiah, great to see you thanks for coming on I appreciate it. Ren Besnard, Vice President of Marketing and Unstoppable Domains in the middle of all the action. Gentlemen, thanks for coming on on theCUBE for this showcase. >> Wow, my pleasure. >> Thanks for having us, John. >> Jeremiah, I want to start with you. You've seen many ways refer in all of your work for over a decade now. You've seen the Web 2.0 wave now the Web 3.0 is here. And it's not, I wouldn't say hyped up it's really just ramping up. And you're seeing real practical examples. You're in the middle of all the action. What is this Web 3.0, can you frame for us? I mean, you've seen many webs. What is Web 3.0 mean, what is it all about? >> Well John, you and I worked in the Web 2.0 space and essentially that enabled peer-to-peer media where people could upload their thoughts and ideas and videos without having to rely on centralized media. Unfortunately, that distributed and decentralized movement actually became centralized on the platform which are the big social networks and big tech companies. And this has caused an uproar because the people who are creating the content did not have control, could not control their identities, and could not really monetize or make decisions. So Web 3.0 which is a moniker of a lot of different trends, including crypto, blockchain and sometimes the metaverse. Is to undo the controlling that has become centralized. And the power is now shifting back into the hands of the participants again. And in this movement, they want to have more control over their identities, their governance, the content that they're creating, how they're actually building it, and then how they're monetizing it. So in many ways it's changing the power and it's a new economic model. So that's Web 3.0. Without really even mentioning the technologies. Is that helpful? >> Yeah, it's great. And Ren, we're talking about on theCUBE many times and one notable stat I don't think it's been reported, but it's been more kind of a rumor. I hear that 30% of the Berkeley computer science students are dropping out and going into to crypto or blockchain or decentralized startups. Which means that there's a big wave coming in of talent. You're seeing startups, you're seeing a lot more formation, you're seeing a lot more, I would say it's kind of ramping up of real people, not just people with dream is actual builders out here doing stuff. What's your take on the Web 3.0 movement with all this kind of change happening from people and also the new ideas being refactored? >> I think that the competition for talent is extremely real. And we start looking at the stats, we see that there is an enormous draft of people that are moving into this space. People that are fascinated by technology and are embracing the ethos of Web 3.0. And at this stage I think it's not only engineers and developers, but we have moved into a second phase where we see that a lot of supporting functions, you know, marketing being one of them, sales, business development are being built up quite rapidly. It's not without actually reminding me of the mid 2000s, you know. When I started working with Google, at that point in time the walled gardens rightly absorbing vast, vast cohorts of young graduates and more experienced professionals that were passionate and moving into the web environment. And I think we are seeing a movement right now, which is not entirely similar except faster. >> Yeah, Jeremiah, you've seen the conversations of the cloud, I call the cloud kind of revolution. You had mobile in 2007. But you got Amazon Web Services changed the application space on how people developed in the cloud. And again, that created a lot of value. Now you're seeing the role of data as a huge part of how people are scaling and the decentralized movements. So you've got cloud which is kind of classic today, state of the art enterprise and or app developers. And you've got now decentralized wave coming, okay. You're seeing apps being developed on that architecture. Data is central in all this, right. So how, how do you view this as someone who's watching the landscape, you know, these walled gardens are hoarding all the data I mean, LinkedIn, Facebook. They're not sharing that data with anyone they're using it for themselves. So as- >> That's right. >> They can control back comes to the forefront. How do you see this market with the applications and what comes out of that? >> So the thing that we seen out of the five things that I had mentioned that are decentralizing. (Jeremiah coughing) Are the ones that have been easier to move across. Have been the ability to monetize and to build. But the data aspect has actually stayed pretty much central, frankly. What has decentralized is that the contracts, the blockchain ledgers, those have decentralized. But the funny thing is often a big portion of these blockchain networks are on Amazon 63 to 70%, same thing with (indistinct). So they're still using the Web 2.0 architectures. However, we're also seeing other forms like IPFS where the data could be spread across a wider range of folks. But right now we're still dependent on what Web 2.0. So the vision and the promise Web 3.0 when it to full decentralization is not here by any means. I'd say we're at a Web 2.25. >> Pre-Web 3.0 no, but actions there. How do you guys see the dangers, 'cause there's a lot of negative press but also there's a lot of positive press. You're seeing a lot of fraud, we've seen a lot of the crypto fraud over the past years. You've seen a lot of now positive. It's almost a self-governance thing and environment, the way the culture is. But what are the dangers, how do you guys educate people, what should people pay attention to, what should people look for to understand, you know, where to position themselves? >> Yes, so we've learned a lot from Web 1.0, Web 2.0, the sharing economy. And we are walking into Web 3.0 with eyes wide open. So people have rightfully put forth a number of challenges, the sustainability issues with excess using of computing and mining the excessive amount of scams that are happening in part due to unknown identities. Also the architecture breaks DAOn in some periods and there's a lack of regulation. This is something different though. In the last periods that we've gone through, we didn't really know what was going to happen. And we walked and think this is going to be great. The sharing economy, the gig economy, the social media's going to change the world around. It's very different now. People are a little bit jaded. So I think that's a change. And so I think we're going to see that sorted out in suss out just like we've seen with other trends. It's still very much in the early years. >> Ren, I got to get your take on this whole should influencers and should people be anonymous or should they be docs out there? You saw the board, eight guys that did that were kind of docs a little bit there. And that went viral. This is an issue, right? Because we just had a problem of fake news, fake people, fake information. And now you have a much more secure environment imutability is a wonderful thing. It's a feature, not a bug, right? So how is this all coming down? And I know you guys are in the middle of it with NFTs as authentication. Take us, what's your take on this because this is a big issue. >> Look, I think first I am extremely optimistic about technology in general. So I'm super, super bullish about this. And yet, you know, I think that while crypto has so many upsides, it's important to be super conscious and aware of the downsides that come with it to, you know. If you think about every Fortune 500 company there is always training required by all employees on internet safety, reporting of potential attacks and so on. In Web 3.0, we don't have that kind of standard reporting mechanisms yet for bad actors in that space. And so when you think about influencers in particular, they do have a responsibility to educate people about the potential, but also the dangers of the technology of Web 3.0 of crypto basically. Whether you're talking about hacks or online safety, the need for hardware, wallet, impersonators on discord, you know, security storing your seed phrase. So every actor influencer or else has got a role to play. I think that in that context to your point, it's very hard to tell whether influencers should be anonymous, oxydemous or fully docked. The decentralized nature of Web 3.0 will probably lead us to see a combination of those anonymity levels so to speak. And the movements that we've seen around some influencers identities become public are particularly interesting. I think there's probably a convergence of Web 2.O and Web 3.0 at play here, you know. Maybe occurring on the notion of 2.5. But for now I think in Web 2.0, all business founders and employees are known and they held accountable for their public comments and their actions. If Web 3.0 enables us to be anonymous, if DAOs have voting control, you know. What happens if people make comments and there is no way to know who they are, basically. What if the DAO doesn't take appropriate action? I think eventually there will be an element of community self-regulation where influencers will be acting in the best interest of their reputation. And I believe that the communities will self-regulate themselves and will create natural boundaries around what can be said or not said. >> I think that's a really good point about influencers and reputation because. Jeremiah, does it matter that you're anonymous have an icon that could be a NFT or a picture. But if I have an ongoing reputation I have trust, to this trust there. It's not like just a bot that was created just to spam someone. You know I'm starting to getting into this new way. >> You're right, and that word you said trust, that's what really this is about. But we've seen that public docs, people with their full identities have made mistakes. They have pulled the hood over people's faces and really scammed them out of a lot of money. We've seen that in the, that doesn't change anything in human behavior. So I think over time that we will see a new form of a reputation system emerge even for pseudonym and perhaps for people that are just anonymous that only show their potential wallet, address a series of numbers and letters. That form might take a new form of a Web 3.0 FICO Score. And you could look at their behaviors. Did they transact, you know, how did they behave? Were they involved in projects that were not healthy? And because all of that information is public on the chain and you can go back in time and see that. We might see a new form of a scoring emerge, of course. Who controls that scoring? That's a whole nother topic gone on controling and trust. So right now, John we do see that there's a number of projects, new NFT projects, where the founders will claim and use this as a point of differentiation that they are fully docs. So you know who they are and in their names. Secondly, we're seeing a number of products or platforms that require KYC, you know, your customers. So that's self-identification often with a government ID or credit card in order to bridge out your coins and turn that into fiat. In some cases that's required in some of these marketplaces. So we're seeing a collision here between our full names and pseudonyms and being anonymous. >> That's awesome. And I think this is the new, again, a whole new form of governance. Ren, you mentioned some comments about DAO. I want to get your thoughts again. You know, Jeremiah we've become historians over the years. We're getting old I'm a little bit older than you. (Jeremiah laughs) But we've seen the- >> You're young men. You know, I remember breaking in the business when the computer standards bodies were built to be more organic and then they became much more of a, kind of an anti-innovation environment where people, the companies would get involved, the standards organization just to slow things DAO and mark things up a little bit. So, you know, you look at DAOs like, hmm, is DAO a good thing or a bad thing. The answer is from people I talk to is, it depends. So I'd love to get your thoughts on getting momentum and becoming defacto with value, a value proposition, vis-a-vis just a DAO for the sake of having a DAO. This has been a conversation that's been kind of in the inside the baseball here, inside the ropes of the industry, but there's trade offs. Can you guys share your thoughts on when to do a DAO and when not to do a DAO and the benefits and trade offs of that? >> Sure, maybe I'll start off with a definition and then we'll go to, Ren. So a DAO, a decentralized autonomous organization, the best way to think about this It's a digital cooperative. and we've heard of worker cooperatives before. The difference is that they're using blockchain technologies in order to do three things, identity, governance, and rewards and mechanisms. They're relying on Web 2.0 tools and technologies like discord and Telegram and social networks to communicate. And as a cooperative they're trying to come up with a common goal. Ren, what's your take, that's the setup. >> So, you know for me when I started my journey into crypto and Web 3.0, I had no idea about what DAO actually meant. And an easy way for me to think of it and to grasp the nature of it was about the comparison between a DAO and perhaps a more traditional company structure, you know. In the traditional company structure, you have (indistinct), the company's led by a CEO and other executives. The DAO is a flat structure, and it's very much led by a group of core contributors. So to Jeremiah's point, you know, you get that notion of a cooperative type of structure. The decision making is very different, you know. We're talking about a super high level of transparency proposals getting submitted and voting systems using (indistinct) as opposed to, you know, management, making decisions behind closed doors. I think that speaks to a totally new form of governance. And I think we have hardly, hardly scratched the surface. We have seen recently very interesting moments in Web 3.0 culture. And we have seen how DAO suddenly have to make certain decisions and come to moments of claiming responsibility in order to police behavior of some of the members. I think that's important. I think it's going to redefine how we're thinking about that particularly new governance models. And I think it's going to pave the way for a lot of super interesting structure in the near future. >> Yeah and that's a great point. >> Go ahead, Jeremiah. >> That's a great point, Ren. Around the transparency for governance. So, John you post the question, does this make things faster or slower? And right now in the most doubts are actually pretty slow because they're set up as a flat organization. So as a response to that they're actually shifting to become representative democracies. Does that sound familiar? Or you can appoint delegates and use tokens to vote for them and they have a decision power. Almost like a committee and they can function. And so we've seen actually there sometimes are hierarchy except the person at the top is voted by those that have the tokens. In some cases, the people at the top had the most tokens. But that's a whole nother topic. So we're seeing a wide variety of governance structures. >> You know, Ren I was talking with Matt G, the Founder of Unstoppable. And I was telling him about the Domain Name System. And one little trivia note that many people don't know about is that the US government 'cause the internet was started by the US. The Department of Commerce kept that on tight leash because the international telecommunications wanted to get their hands on it because of ccTLDs and other things. So at that time, 'cause the innovation yet was isn't yet baked out. It was organically growing the governance, the rules of the road, keeping it very stable versus melding with it. So there's certain technologies that require, Jeremiah that let's keep an eye on as a community let's not formalize anything. Like the government did with the Domain Name System. Let's keep it tight and then finally released it. I think multiple years after 2004, I think it went over to the ITU. But this is a big point. I mean, if you get too structured, organic innovation can't go. What's you guys reaction to that? >> So I think, you know to take the stab at it. We have as a business, you know, thinking of Unstoppable Domains, a strong incentive to innovate. And this is what is going to be determining long-term value growth for the organization, for partners, for users, for customers. So you know the degree of formalization actually gives us a sense of purpose and a sense of action. And if you compare that to DAO, for instance, you can see how some of the upsides and downsides can pan out either way. It's not to say that there is a perfect solution. I think one of the advantages of the DAO is that you can let more people contribute. You can probably remove buyers quite effectively and you can have a high level of participation and involvement in decisions and own the upside in many ways. You know as a company, it's a slightly different setup. We have the opportunity to coordinate a very diverse and part-time workforce in a very you a different way. And we do not have to deal with the inefficiencies that might be inherent to some form of extreme decentralization. So there is a balance from an organizational structure that comes either side. >> Awesome. Jeremiah, I want to get your thoughts on a trend that you've been involved in, we've both been involved in. And you're seeing it now with the kind of social media world, the world of the role of an influencer. It's kind of moved from what was open source and influencer was a connect to someone who shared, created content enabled things to much more of a vanity. You update the photo on Instagram and having a large audience. So is there a new influencer model with Web 3.0 or is it, I control the audience I'm making money that way. Is there a shift in the influencer role or ideas that you see that should be in place for what is the role of an influencer? 'Cause as Web 3.0 comes you're going to see that role become instrumental. We've seen it in open source projects. Influencers, you know, the people who write code or ship code. So what's your take on that? Because this has been a conversation. People have been having the word influencer and redefining and reframing it. >> Sure, the influence model really hasn't changed that much, but the way that they're behaving has when it comes to Web 3.0. In this market, I mean there's a couple of things. Some of the influencers are investors. And so when you see their name on a project or a new startup, that's an indicator there's a higher level of success. You might want to pay more attention to it or not. Secondly, influencers themselves are launching their own NFT projects. So, Gary Vaynerchuk, a number of celebrities, Paris Hilton is involved. They are also doing theirs as well. Steve Aok, famous DJ launched his as well. So they're going head first and participating in building in this model. And their communities are coming around them and they're building economy. Now the difference is it's not I speak as an influencer to the fans. The difference is that the fans are now part of the community and they literally hold and own some of the economic value, whether it's tokens or the NFTs. So it's a collaborative economy, if you will, where they're all benefiting together. And that's a big difference as well. >> Can you see- >> Lastly, there's one little tactic we're seeing where marketers are air dropping NFTs, branded NFTs influencers wallet. So you can see it in there. So there's new tactics that are forming as well. Back to you. >> That's super exciting. Ren, what's your reaction to that? Because he just hit on a whole new way of how engagement's happening, how people are closed looping their votes, their votes of confidence or votes with their wallet. And the brands which are artists now influencers. I mean, this is a whole game changing instrumentation level. >> I think that what we are seeing right now is super reinvigorating as a marketeer who's been around for a few years, basically. I think that the shift in the way brands are going to communicate and engage with their audiences is profound. It's probably as revolutionary and even more revolutionary than the movement for brands in getting into digital. And you have that sentiment of a gold rush right now with a lot of brands that are trying to understand NFTs and how to actually engage with those communities and those audiences. There are many levels in which brands and influencers are going to engage. There are many influencers that actually advance the message and the mission because the explosion of content on Web 3.0 has been crazy. Part of that is due to the network effect nature of crypto. Because as Jaremiah mentioned, people are incentivized to promote projects. Holders of an NFT are also incentivized to promote it. So you end up with a fly wheel which is pretty unique of people that are hyping their project and that are educating other people about it and commenting on the ecosystem with IP right being given to NFT holders. You're going to see people promote brands instead of the brands actually having to. And so the notion of brands are gaining and delivering elements of the value to their fans is something that's super attractive, extremely interesting. And I think again, we have hardly scratched the surface of all that is possible in that particular space. >> That's interesting. You guys are bringing some great insight here. Jeremiah, the old days the word authentic was a kind of a cliche and brands like tried to be authentic. And they didn't really know what to do they called it organic, right? And now you have the trust concept with authenticity and environment like Web 3.0 where you can actually measure it and monetize it and capture it if you're actually authentic and trustworthy. >> That's right, and be because it's on blockchain, you can see how somebody's behaved with their economic behavior in the past. Of course, big corporations aren't going to have that type of trail on blockchain just yet. But individuals and executives who participate in this market might be. And we'll also see new types of affinity. Do executives do they participate in these NFT communities, do they purchase them or numerous brands like Adidas to acquire, you know, different NFT projects to participate. And of course the big brands are grabbing their domains. Of course you could talk to, Ren about that because it's owning your own name is a part of this trust and being found. >> That's awesome. Great insight guys. Closing comments, takeaways for the audience here. Each of you take a minute to share your thoughts on what you think is happening now where it goes, all right, where's it going to go? Jeremiah, we'll start with you. >> Sure, I think the vision of Web 3.0 where full decentralization happens, where the power is completely shifted to the edges. I don't think it's going to happen. I think we will reach Web 2.5. And I've been through so many tech trends where we said that the power's going to shift completely to of the end, it just doesn't. In part there's two reasons. One is the venture capital are the ones who tend to own the programs in the first place. And secondly, the startups themselves end up becoming the one-percenter. We see Airbnb and Uber are one-percenter now. So that trend happens over and over and over. Now with that said, the world will be in a better place. We will have more transparency. We will see economic power shifted to the people, the participants. And so they will have more control over the internet that they are building. >> Awesome, Ren final comments. >> I'm fully aligned with Jeremiah on the notion of control being returned to users, the notion of ownership and the notion of redistribution of the economic value that is created across all the different chains that we are going to see and all those ecosystems. I believe that we are going to witness two parallel movements of expansion. One that is going to be very lateral. When you think of crypto and Web 3.0 essentially you think of a few 100 tribes. And I think that more projects are going to be a more coalitions of individuals and entities, and those are going to exist around those projects. So you're going to see, you know, an increase in the number of tribes that one might join. And I also think that we're going to progress rapidly from the low 100 millions of crypto and NFT holders into the big hands basically. And that's going to be extreme interesting. I think that the next waves of crypto users, NFT fans are going to look very different from the early adopters that we had witnessed in the very early days. So it's not going to be your traditional model of technology adoption curves. I think the demographics are going to shift and the motivations are going to be different as well, which is going to be a wonderful time to educate and engage with new community members. >> All right, Ren and Jeremiah, thank you both for that great insight great segment breaking down Web 3.0 or Web 2.5 as Jeremiah says but we're in a better place. This is a segment with the influencers. As part of theCUBE and the Unstoppable Domain Showcase. I'm John Furrie, your host. Thanks for watching. (bright upbeat music)

>> From theCUBE Studios in Palo Alto in Boston, bringing you data-driven insights from theCUBE and ETR. This is "Breaking Analysis" with Dave Vellante. >> When Facebook changed its name to Meta last fall, it catalyzed a chain reaction throughout the tech industry. Software firms, gaming companies, chip makers, device manufacturers, and others have joined in hype machine. Now, it's easy to dismiss the metaverse as futuristic hyperbole, but do we really believe that tapping on a smartphone, or staring at a screen, or two-dimensional Zoom meetings are the future of how we work, play, and communicate? As the internet itself proved to be larger than we ever imagined, it's very possible, and even quite likely that the combination of massive processing power, cheap storage, AI, blockchains, crypto, sensors, AR, VR, brain interfaces, and other emerging technologies will combine to create new and unimaginable consumer experiences, and massive wealth for creators of the metaverse. Hello, and welcome to this week's Wiki Bond Cube Insights, powered by ETR. In this "Breaking Analysis" we welcome in cyber expert, hacker gamer, NFT expert, and founder of ORE System, Nick Donarski. Nick, welcome, thanks so much for coming on theCUBE. >> Thank you, sir, glad to be here. >> Yeah, okay, so today we're going to traverse two parallel paths, one that took Nick from security expert and PenTester to NFTs, tokens, and the metaverse. And we'll simultaneously explore the complicated world of cybersecurity in the enterprise, and how the blockchain, crypto, and NFTs will provide key underpinnings for digital ownership in the metaverse. We're going to talk a little bit about blockchain, and crypto, and get things started there, and some of the realities and misconceptions, and how innovations in those worlds have led to the NFT craze. We'll look at what's really going on in NFTs and why they're important as both a technology and societal trend. Then, we're going to dig into the tech and try to explain why and how blockchain and NFTs are going to lay the foundation for the metaverse. And, finally, who's going to build the metaverse. And how long is it going to take? All right, Nick, let's start with you. Tell us a little bit about your background, your career. You started as a hacker at a really, really young age, and then got deep into cyber as a PenTester. You did some pretty crazy stuff. You have some great stories about sneaking into buildings. You weren't just doing it all remote. Tell us about yourself. >> Yeah, so I mean, really, I started a long time ago. My dad was really the foray into technology. I wrote my first program on an Apple IIe in BASIC in 1989. So, I like to say I was born on the internet, if you will. But, yeah, in high school at 16, I incorporated my first company, did just tech support for parents and teachers. And then in 2000 I transitioned really into security and focused there ever since. I joined Rapid7 and after they picked up Medis boy, I joined HP. I was one of their founding members of Shadowlabs and really have been part of the information security and the cyber community all throughout, whether it's training at various different conferences or talking. My biggest thing and my most awesome moments as various things of being broken into, is really when I get to actually work with somebody that's coming up in the industry and who's new and actually has that light bulb moment of really kind of understanding of technology, understanding an idea, or getting it when it comes to that kind of stuff. >> Yeah, and when you think about what's going on in crypto and NFTs and okay, now the metaverse it's you get to see some of the most innovative people. Now I want to first share a little bit of data on enterprise security and maybe Nick get you to comment. We've reported over the past several years on the complexity in the security business and the numerous vendor choices that SecOps Pros face. And this chart really tells that story in the cybersecurity space. It's an X,Y graph. We've shown it many times from the ETR surveys where the vertical axis, it's a measure of spending momentum called net score. And the horizontal axis is market share, which represents each company's presence in the data set, and a couple of points stand out. First, it's really crowded. In that red dotted line that you see there, that's 40%, above that line on the net score axis, marks highly elevated spending momentum. Now, let's just zoom in a bit and I've cut the data by those companies that have more than a hundred responses in the survey. And you can see here on this next chart, it's still very crowded, but a few call-outs are noteworthy. First companies like SentinelOne, Elastic, Tanium, Datadog, Netskope and Darktrace. They were all above that 40% line in the previous chart, but they've fallen off. They still have actually a decent presence in the survey over 60 responses, but under that hundred. And you can see Auth0 now Okta, big $7 billion acquisition. They got the highest net score CrowdStrike's up there, Okta classic they're kind of enterprise business, and Zscaler and others above that line. You see Palo Alto Networks and Microsoft very impressive because they're both big and they're above that elevated spending velocity. So Nick, kind of a long-winded intro, but it was a little bit off topic, but I wanted to start here because this is the life of a SecOps pro. They lack the talent in a capacity to keep bad guys fully at bay. And so they have to keep throwing tooling at the problem, which adds to the complexity and as a PenTester and hacker, this chaos and complexity means cash for the bad guys. Doesn't it? >> Absolutely. You know, the more systems that these organizations find to integrate into the systems, means that there's more components, more dollars and cents as far as the amount of time and the engineers that need to actually be responsible for these tools. There's a lot of reasons that, the more, I guess, hands in the cookie jar, if you will, when it comes to the security architecture, the more links that are, or avenues for attack built into the system. And really one of the biggest things that organizations face is being able to have engineers that are qualified and technical enough to be able to support that architecture as well, 'cause buying it from a vendor and deploying it, putting it onto a shelf is good, but if it's not tuned properly, or if it's not connected properly, that security tool can just hold up more avenues of attack for you. >> Right, okay, thank you. Now, let's get into the meat of the discussion for today and talk a little bit about blockchain and crypto for a bit. I saw sub stack post the other day, and it was ripping Matt Damon for pedaling crypto on TV ads and how crypto is just this big pyramid scheme. And it's all about allowing criminals to be anonymous and it's ransomware and drug trafficking. And yes, there are definitely scams and you got to be careful and lots of dangers out there, but these are common criticisms in the mainstream press, that overlooked the fact by the way that IPO's and specs are just as much of a pyramid scheme. Now, I'm not saying there shouldn't be more regulation, there should, but Bitcoin was born out of the 2008 financial crisis, cryptocurrency, and you think about, it's really the confluence of software engineering, cryptography and game theory. And there's some really powerful innovation being created by the blockchain community. Crypto and blockchain are really at the heart of a new decentralized platform being built out. And where today, you got a few, large internet companies. They control the protocols and the platform. Now the aspiration of people like yourself, is to create new value opportunities. And there are many more chances for the little guys and girls to get in on the ground floor and blockchain technology underpins all this. So Nick, what's your take, what are some of the biggest misconceptions around blockchain and crypto? And do you even pair those two in the same context? What are your thoughts? >> So, I mean, really, we like to separate ourselves and say that we are a blockchain company, as opposed to necessarily saying(indistinct) anything like that. We leverage those tools. We leverage cryptocurrencies, we leverage NFTs and those types of things within there, but blockchain is a technology, which is the underlying piece, is something that can be used and utilized in a very large number of different organizations out there. So, cryptocurrency and a lot of that negative context comes with a fear of something new, without having that regulation in place, without having the rules in place. And we were a big proponent of, we want the regulation, right? We want to do right. We want to do it by the rules. We want to do it under the context of, this is what should be done. And we also want to help write those rules as well, because a lot of the lawmakers, a lot of the lobbyists and things, they have a certain aspect or a certain goal of when they're trying to get these things. Our goal is simplicity. We want the ability for the normal average person to be able to interact with crypto, interact with NFTs, interact with the blockchain. And basically by saying, blockchain in quotes, it's very ambiguous 'cause there's many different things that blockchain can be, the easiest way, right? The easiest way to understand blockchain is simply a distributed database. That's really the core of what blockchain is. It's a record keeping mechanism that allows you to reference that. And the beauty of it, is that it's quote unquote immutable. You can't edit that data. So, especially when we're talking about blockchain, being underlying for technologies in the future, things like security, where you have logging, you have keeping, whether you're talking about sales, where you may have to have multiple different locations (indistinct) users from different locations around the globe. It creates a central repository that provides distribution and security in the way that you're ensuring your data, ensuring the validation of where that data exists when it was created. Those types of things that blockchain really is. If you go to the historical, right, the very early on Bitcoin absolutely was made to have a way of not having to deal with the fed. That was the core functionality of the initial crypto. And then you had a lot of the illicit trades, those black markets that jumped onto it because of what it could do. The maturity of the technology though, of where we are now versus say back in 97 is a much different world of blockchain, and there's a much different world of cryptocurrency. You still have to be careful because with any fed, you're still going to have that FUD that goes out there and sells that fear, uncertainty and doubt, which spurs a lot of those types of scams, and a lot of those things that target end users that we face as security professionals today. You still get mailers that go out, looking for people to give their social security number over during tax time. Snail mail is considered a very ancient technology, but it still works. You still get a portion of the population that falls for those tricks, fishing, whatever it might be. It's all about trying to make sure that you have fear about what is that change. And I think that as we move forward, and move into the future, the simpler and the more comfortable these types of technologies become, the easier it is to utilize and indoctrinate normal users, to be able to use these things. >> You know, I want to ask you about that, Nick, because you mentioned immutability, there's a lot of misconceptions about that. I had somebody tell me one time, "Blockchain's Bs," and they say, "Well, oh, hold on a second. They say, oh, they say it's a mutable, but you can hack Coinbase, whatever it is." So I guess a couple of things, one is that the killer app for blockchain became money. And so we learned a lot through that. And you had Bitcoin and it really wasn't programmable through its interface. And then Ethereum comes out. I know, you know a lot about Ether and you have solidity, which is a lot simpler, but it ain't JavaScript, which is ubiquitous. And so now you have a lot of potential for the initial ICO's and probably still the ones today, the white papers, a lot of security flaws in there. I'm sure you can talk to that, but maybe you can help square that circle about immutability and security. I've mentioned game theory before, it's harder to hack Bitcoin and the Bitcoin blockchain than it is to mine. So that's why people mine, but maybe you could add some context to that. >> Yeah, you know it goes to just about any technology out there. Now, when you're talking about blockchain specifically, the majority of the attacks happen with the applications and the smart contracts that are actually running on the blockchain, as opposed to necessarily the blockchain itself. And like you said, the impact for whether that's loss of revenue or loss of tokens or whatever it is, in most cases that results from something that was a phishing attack, you gave up your credentials, somebody said, paste your private key in here, and you win a cookie or whatever it might be, but those are still the fundamental pieces. When you're talking about various different networks out there, depending on the blockchain, depends on how much the overall security really is. The more distributed it is, and the more stable it is as the network goes, the better or the more stable any of the code is going to be. The underlying architecture of any system is the key to success when it comes to the overall security. So the blockchain itself is immutable, in the case that the owner are ones have to be trusted. If you look at distributed networks, something like Ethereum or Bitcoin, where you have those proof of work systems, that disperses that information at a much more remote location, So the more disperse that information is, the less likely it is to be able to be impacted by one small instance. If you look at like the DAO Hack, or if you look at a lot of the other vulnerabilities that exist on the blockchain, it's more about the code. And like you said, solidity being as new as it is, it's not JavaScript. The industry is very early and very infantile, as far as the developers that are skilled in doing this. And with that just comes the inexperience and the lack of information that you don't learn until JavaScript is 10 or 12 years old. >> And the last thing I'll say about this topic, and we'll move on to NFTs, but NFTs relate is that, again, I said earlier that the big internet giants have pretty much co-opted the platform. You know, if you wanted to invest in Linux in the early days, there was no way to do that. You maybe have to wait until red hat came up with its IPO and there's your pyramid scheme folks. But with crypto it, which is again, as Nick was explaining underpinning is the blockchain, you can actually participate in early projects. Now you got to be careful 'cause there are a lot of scams and many of them are going to blow out if not most of them, but there are some, gems out there, because as Nick was describing, you've got this decentralized platform that causes scaling issues or performance issues, and people are solving those problems, essentially building out a new internet. But I want to get into NFTs, because it's sort of the next big thing here before we get into the metaverse, what Nick, why should people pay attention to NFTs? Why do they matter? Are they really an important trend? And what are the societal and technological impacts that you see in this space? >> Yeah, I mean, NFTs are a very new technology and ultimately it's just another entry on the blockchain. It's just another piece of data in the database. But how it's leveraged in the grand scheme of how we, as users see it, it can be the classic idea of an NFT is just the art, or as good as the poster on your wall. But in the case of some of the new applications, is where are you actually get that utility function. Now, in the case of say video games, video games and gamers in general, already utilize digital items. They already utilize digital points. As in the case of like Call of Duty points, those are just different versions of digital currencies. You know, World of Warcraft Gold, I like to affectionately say, was the very first cryptocurrency. There was a Harvard course taught on the economy of WOW, there was a black market where you could trade your end game gold for Fiat currencies. And there's even places around the world that you can purchase real world items and stay at hotels for World of Warcraft Gold. So the adoption of blockchain just simply gives a more stable and a more diverse technology for those same types of systems. You're going to see that carry over into shipping and logistics, where you need to have data that is single repository for being able to have multiple locations, multiple shippers from multiple global efforts out there that need to have access to that data. But in the current context, it's either sitting on a shipping log, it's sitting on somebody's desk. All of those types of paper transactions can be leveraged as NFTs on the blockchain. It's just simply that representation. And once you break the idea of this is just a piece of art, or this is a cryptocurrency, you get into a world where you can apply that NFT technology to a lot more things than I think most people think of today. >> Yeah, and of course you mentioned art a couple of times when people sold as digital art for whatever, it was 60, 65 million, 69 million, that caught a lot of people's attention, but you're seeing, I mean, there's virtually infinite number of applications for this. One of the Washington wizards, tokenized portions of his contract, maybe he was creating a new bond, that's really interesting use cases and opportunities, and that kind of segues into the latest, hot topic, which is the metaverse. And you've said yourself that blockchain and NFTs are the foundation of the metaverse, they're foundational elements. So first, what is the metaverse to you and where do blockchain and NFTs, fit in? >> Sure, so, I mean, I affectionately refer to the metaverse just a VR and essentially, we've been playing virtual reality games and all the rest for a long time. And VR has really kind of been out there for a long time. So most people's interpretation or idea of what the metaverse is, is a virtual reality version of yourself and this right, that idea of once it becomes yourself, is where things like NFT items, where blockchain and digital currencies are going to come in, because if you have a manufacturer, so you take on an organization like Nike, and they want to put their shoes into the metaverse because we, as humans, want to individualize ourselves. We go out and we want to have that one of one shoe or that, t-shirt or whatever it is, we're going to want to represent that same type of individuality in our virtual self. So NFTs, crypto and all of those digital currencies, like I was saying that we've known as gamers are going to play that very similar role inside of the metaverse. >> Yeah. Okay. So basically you're going to take your physical world into the metaverse. You're going to be able to, as you just mentioned, acquire things- I loved your WOW example. And so let's stay on this for a bit, if we may, of course, Facebook spawned a lot of speculation and discussion about the concept of the metaverse and really, as you pointed out, it's not new. You talked about why second life, really started in 2003, and it's still around today. It's small, I read recently, it's creators coming back into the company and books were written in the early 90s that used the term metaverse. But Nick, talk about how you see this evolving, what role you hope to play with your company and your community in the future, and who builds the metaverse, when is it going to be here? >> Yeah, so, I mean, right now, and we actually just got back from CES last week. And the Metaverse is a very big buzzword. You're going to see a lot of integration of what people are calling, quote unquote, the metaverse. And there was organizations that were showing virtual office space, virtual malls, virtual concerts, and those types of experiences. And the one thing right now that I don't think that a lot of organizations have grasp is how to make one metaverse. There's no real player one, if you will always this yet, There's a lot of organizations that are creating their version of the metaverse, which then again, just like every other software and game vendor out there has their version of cryptocurrency and their version of NFTs. You're going to see it start to pop up, especially as Oculus is going to come down in price, especially as you get new technologies, like some of the VR glasses that look more augmented reality and look more like regular glasses that you're wearing, things like that, the easier that those technologies become as in adopting into our normal lifestyle, as far as like looks and feels, the faster that stuff's going to actually come out to the world. But when it comes to like, what we're doing is we believe that the metaverse should actually span multiple different blockchains, multiple different segments, if you will. So what ORE system is doing, is we're actually building the underlying architecture and technologies for developers to bring their metaverse too. You can leverage the ORE Systems NFTs, where we like to call our utility NFTs as an in-game item in one game, or you can take it over and it could be a t-shirt in another game. The ability for having that cross support within the ecosystem is what really no one has grasp on yet. Most of the organizations out there are using a very classic business model. Get the user in the game, make them spend their money in the game, make all their game stuff as only good in their game. And that's where the developer has you, they have you in their bubble. Our goal, and what we like to affectionately say is, we want to bring white collar tools and technology to blue collar folks, We want to make it simple. We want to make it off the shelf, and we want to make it a less cost prohibitive, faster, and cheaper to actually get out to all the users. We do it by supporting the technology. That's our angle. If you support the technology and you support the platform, you can build a community that will build all of the metaverse around them. >> Well, and so this is interesting because, if you think about some of the big names, we've Microsoft is talking about it, obviously we mentioned Facebook. They have essentially walled gardens. Now, yeah, okay, I could take Tik Tok and pump it into Instagram is fine, but they're really siloed off. And what you're saying is in the metaverse, you should be able to buy a pair of sneakers in one location and then bring it to another one. >> Absolutely, that's exactly it. >> And so my original kind of investment in attractiveness, if you will, to crypto, was that, the little guy can get an early, but I worry that some of these walled gardens, these big internet giants are going to try to co-op this. So I think what you're doing is right on, and I think it's aligned with the objectives of consumers and the users who don't want to be forced in to a pen. They want to be able to live freely. And that's really what you're trying to do. >> That's exactly it. You know, when you buy an item, say a Skin in Fortnite or Skin in Call of Duty, it's only good in that game. And not even in the franchise, it's only good in that version of the game. In the case of what we want to do is, you can not only have that carry over and your character. So say you buy a really cool shirt, and you've got that in your Call of Duty or in our case, we're really Osiris Protocol, which is our proof of concept video game to show that this all thing actually works, but you can actually go in and you can get a gun in Osiris Protocol. And if we release, Osiris Protocol two, you'll be able to take that to Osiris Protocol two. Now the benefit of that is, is you're going to be the only one in the next version with that item, if you haven't sold it or traded it or whatever else. So we don't lock you into a game. We don't lock you into a specific application. You own that, you can trade that freely with other users. You can sell that on the open market. We're embracing what used to be considered the black market. I don't understand why a lot of video games, we're always against the skins and mods and all the rest. For me as a gamer and coming up, through the many, many years of various different Call of Duties and everything in my time, I wish I could still have some this year. I still have a World of Warcraft account. I wasn't on, Vanilla, Burning Crusade was my foray, but I still have a character. If you look at it that way, if I had that wild character and that gear was NFTs, in theory, I could actually pass that onto my kid who could carry on that character. And it would actually increase in value because they're NFT back then. And then if needed, you could trade those on the open market and all the rest. It just makes gaming a much different thing. >> I love it. All right, Nick, hey, we're out of time, but I got to say, Nick Donarski, thanks so much for coming on the program today, sharing your insights and really good luck to you and building out your technology platform and your community. >> Thank you, sir, it's been an absolute pleasure. >> And thank you for watching. Remember, all these episodes are available as podcasts, just search "Breaking Analysis Podcast", and you'll find them. I publish pretty much every week on siliconangle.com and wikibond.com. And you can reach me @dvellante on Twitter or comment on my LinkedIn posts. You can always email me david.vellante@siliconangle.com. And don't forget, check out etr.plus for all the survey data. This is Dave Vellante for theCUBE Insights, powered by ETR, happy 2022 be well, and we'll see you next time. (upbeat music)

>>mhm Yes. >>Welcome back to the cubes coverage of red hat summit 2021 virtual. I'm john for a host of the cube we're here in Palo alto. Were remote with our great guest here cube alumni. I've been on many times chris wright, Senior vice president and CTO of red hat chris great to see you. Always a pleasure to have you on the screen here too. But we're not in person but thanks for coming in remote. >>Yeah, you bet. Glad to be here. >>Not only were talking about speeds and feeds, digital transformation going under the hood here we're gonna talk about red hats, expanded collaboration with boston University to help fund education and research for open source projects. So you guys have a huge relationship with boston University. Talk about this continued commitment. What's the news, what's the, what's the story? >>Well, we have a couple different things going on uh and and the relationship we have with the EU is many years in. So this itself isn't brand new. Um one of the things that's important to highlight here is we are giving something north of $550 million dollars worth of software to be you really in pursuit of running uh powering and running scaled infrastructure. That's part of the open hybrid class. Um and that's that's an important piece which we can touch on a little bit as we talk to this conversation. The other one is like I said, this isn't a new relationship with the U. And what we're doing now is really expanding the relationship. So we've we've built a great connection directly with the You were substantially expanding that. Um The original relationship we had was a $5 million relationship spread over five years now. We're talking about a $20 million Relationship spread over five years. So really a significant expansion. And of course that expansion is connected to some of the work that we plan to do together in this open hybrid cloud infrastructure and research space. So a lot of things coming together at once to really really advance the red hat ca laboratory at the U. That combined effort in bringing you know, cloud research and open source and all these things together >>and a lot of actually going on. So basically the boston area lot of universities, but I love the shirt you're wearing with his red hat innovation in the open. This is kind of one of those things you also mentioned out of this huge subscription of software grant that's going to be you just a huge number give value for for the boston University. But you also have another project that's been going on the collaborative research and education agreement called red hat collaborative orI Okay, this was in place. You mentioned that. How's that tying in because that was pre existing. Now. You've got the grant, you got your funding more and more research. Talk about how this connects into the open cloud initiative because this is kind of interesting. You're not bringing hybrid cloud kind of research and practical value in A i ops is hot. You can't you can't go anywhere these days without having great observe ability. Cloud native more and more is more complex and you've got these young students and researchers dying and get their hands on it. Take us through the connection between the CA laboratory and open open cloud. >>So the CA laboratory is a clever name that just talks about collaboration and research laboratory type research. And initially the CA laboratory focus was on the infrastructure running the cloud and some of the application workloads that can run on top of an open cloud infrastructure uh that are that's very data centric. And so this is uh an opportunity for multidisciplinary work looking at modeling for um for health care, for example for how you can improve imaging and we've had a great results in this collaboration. Um We've talked at times about the relationship with the boston Children's Hospital and the chris project not related to me, but just similar acronym that spells chris. Um and these things come together in part through connecting relationships to academia, where academia as research is increasingly built in on and around open source software. So if you think of two parallel worlds, open source software development, just the activity of building open source software, it brings so many people together and it moves so quickly that if you're not directly connected to that as an academic researcher, you risk producing academic research results that aren't relevant because it's hard for them to connect back to these large, fast moving projects, which may have invented a solution to the problem you've been focused on as an academic if you're not directly connected. So we see academia and open source coming together to build really a next generation of understanding of the scientific in depth and he's joining the >>train operations you're talking about here though, this is significant because there's dollars behind it, right? There's real money, it's not >>just the right software, >>it's it's a center, it's a joint operation. >>That's right. And so when you think about just the academic research of producing um ideas that manifest themselves as code and software projects, we want to make sure we're first connecting the software projects to open source communities in with our own engineering experience, bringing code into these open, open source projects to just advance the the feeds and speeds and speeds, the kind of functionality the state of the art of the actual project. We're also taking this to a new level with this expanded relationship and that is software today. When you, when you operate software as a cloud, a critical part of the software is the operationalization of that software. So software just sitting there on the shelf doesn't do anybody any good. Even if the shelf is an open source project, it's a tar ball waiting for you to download. If you don't ever grab it and run it, it's not doing anybody any good. And if the challenge of running it is substantial enough that it stops you from using that software, you've created a barrier to the value that's locked inside that project. The focus here is how can we take that the operations experience of running a cloud, which itself is a big complex distributed system, tie some of those experiences back into the projects that are used to build that infrastructure. So you're taking not just the output of the project, but also the understanding of what it takes to run a project and bringing that understanding and even the automation and code associated with that back into the project. So, your operational izing this open source software and you're building deeper understanding of what it means to operate things that scale, including data and data sets that you can use to build models that show how you can create the remediation and closed loop systems with AI and machine learning, you know, sort of synthesizing all the data that you generate out of a big distributed infrastructure and feed that back into the operations of that same infrastructure. So a lot going on there at the same time operationalization as as an open source initiative but also um really the understanding advancement of A I and data centric operations, so ai ops and closed the remediation. >>Yeah, I mean, devops developer and operations to operationalize it and certainly cloud Native put an emphasis on Day two operations, which leads a lot more research, a lot more uh student work on understanding the coding environment. Um so with that I got to ask um I asked you about this uh massachusetts focused or this open cloud initiative because you guys are talking about this open cloud initiative including this massachusetts. Open Cloud, what is that? What is the massachusetts? Open Cloud sounds like you're offering a kind of open person, not just bu but other um Yeah, institutions. >>That's right. So the the M o C massachusetts open cloud is itself a cross um organizational collaboration bringing together five different academic institutions in New England In massachusetts. It's bu it's Harvard mit, its Northeastern and its U. Mass. Coming together to support a common set of infrastructure which is cloud. It's a cloud that runs in a data center and then um it serves a couple of different purposes. One is research on clouds directly. So what does it mean to run a cloud? What does it look like from a research point of view to understand large scale distributed systems? And then the other is more on top. When you have a cloud you can run workloads and those workloads scaled out to do say data processing, looking at the implications of across different fields which could be natural sciences, could be medicine, could be, even political science or social science is really a multidisciplinary view of what it means to leverage a cloud and run data centric workloads on top. So two different areas that are of a focus for the M. O. C. And this becomes this sort of vehicle for collaboration between Red Hat View and the Red Hot Laboratory. >>So I have to ask only because I'm a big fan of the area and I went to one of those schools, is there like a bean pot for technical hackathons where you get all the schools matched up against each other on the mass open cloud and compete for who gets bragging rights and the text city there. >>It's a great question. Not yet. But I'll jot that down here in hell. Up on that. >>Happy to sponsor. We'll we'll do the play by play coverage, you know. Great. >>I love that. Yeah, kind of twitch tv style. The one thing that there is which is very practical is academic research grants themselves are competitive, right? People are vying for research dollars to put together proposals, Bring those proposals to um the agency that's that's that's giving out grants and winning those grants is certainly prestigious. It's important as part of her research institutes continue to fund the work that they're doing. Uh Now we've been associated uh through the work we've done to date with the U. With Yeah almost $15 million 20 papers. So there's there's a lot of work you can't quite call the play by play. It's a >>scoreboard. I mean their numbers you can put numbers on the board. I mean that's what's one of the things you can measure. But let me ask you on those grants. So you're saying this is just the bu you guys actually have data on um the impact of the relationship in terms of grants and papers and stuff like that academic work. >>That's right. That's right. And so those numbers that I'm giving you are examples of how we've worked together with the u to help their faculty generate grant dollars that then fund some of the research that's happening there together with redhead engineers and on and on the infrastructure like the massachusetts Open cloud. >>That's a good way to look at the scoreboard. It's a good point. We have to research that if you don't mind me asking on this data that you have um are all those projects contributing to open source or do they have to be? That's just generic. Is that all of you all papers around bu is part of the research. In other words, I'm trying to think if I'm in open source, has this contributed to me as an >>open source? Yeah, it's a big and complex question because there's so much research that can happen through a research institution. And those research grants tend to be governed with agreements and some of those agreements have intellectual property rights um front and center and might require things like open source software as a result, the stuff that we're working on clearly isn't that focus area of open source software and and research activities that help kind of propel our understanding forward of what does it mean to do large scale distributed systems creation and then operation. So how do you develop software that does it? How do you how do you run the software that builds these big large distributed systems? So we're focused in that area. Um some of the work that we facilitated through that focus includes integrating non open source software that might be part of um same medical imaging. So for example work we've done with the boston Children's Hospital That isn't 100 doesn't require us to be involved 100 of the open source pieces. All the infrastructure there to support it is. And so we're learning how we can build integrated pipelines for data analysis and image analysis and data sharing across different institutions uh at the open source project level. Well maybe we have a specific imaging program that is not generated from this project. And of course that's okay with >>us. You know chris you bring up a good point with all those conversations. I could see this really connecting the dots. Most computer science programs. Most engineering programs haven't really traditionally focused on it at the scale we're talking about because we look at cloud scale but now scaling with hybrid it's real engineering going on to think about the large scale. We know all the big hyper scale ear's right so it's not just I. T. Provisioning you know network connection and doing some I. T. Work. We're talking about large scale. So I have to ask you as you guys look at these relationships with academics uh academia like like bu and others um how are the students responding to this? Are you guys seeing any specific graduate level advancements? Because you're talking about operational roles that are becoming so important whether it's cyber security and as cloud needed because once more data driven you need to have all this new scale engineered up. That's >>what how >>do you look at that? >>There's two different pieces that I would highlight. One is just the data science itself. So schools still need to produce data scientists. And having data is a big part of being a data scientist and knowing what your what your goals are with that data and then experimenting with different techniques, whether it's algorithms or tools. It's a big part of being a data scientist sort of spelunking through the data. So we're helping produce data. We're looking at data science efforts around data that's used to operationalize infrastructure, which is an interesting data science endeavor by itself. The other piece is really what you highlighted, which is there's an emergence of a skill set in the industry, often referred to as SRE site reliability engineering. Um it is a engineering discipline. And if you back up a little bit and you start thinking about what are the underlying principles behind large scale distributed systems, you get to some information theory and computer science. So this isn't just something that you might think of as um some simple training of a few key tools and knowing how to interpret a dashboard. And you're good to go, this is a much more sophisticated view of what does it mean to really operate large scale infrastructure, which to date, there aren't a lot of these large scale infrastructures available to academics to research because their commercial endeavors >>and their new to me. I was talking to some young folks my son's age and daughters age and I was saying, you know, architect in a building, a skyscraper isn't trivial. You can't just do that overnight. There's a lot of engineering that goes on in that science, but you're bringing kind of operating systems theory, systems thinking to distributed computing. I mean that's combination of a interdisciplinary shift and you got, I won't say civil engineering, but like concept is there, you've got structure, you've got networks, they're changing and then you've got software so again completely new area. >>That's right and there's not a lot of even curriculum that explores this space. So one of the opportunity, there's a great program that really focuses on um that that space of site reliability engineering or operational izing software. Um And then the other piece that I'm I'm really excited about is connecting to open source communities so that as we build software, we have a way to run and operationalize that software that doesn't have to be directly tied to a commercial outlet. So products running in the cloud will have a commercial S. L. A. And commercial agreements between the user and the producer of that service. How do you do that in open source context? How do you leverage a community, bring that community software to a community run service, learn through the running of that service. How to best build architect the service itself and then operationalized with the tooling and automation that service? How do you, how do you bring that into the open source community? And that's something that we've been referring to as the operate first initiative. How do you get the operationalization of software? Really thought of as a primary focal point in the software project where you normally think about the internals of software, the features, the capabilities of functionality, less about the operationalization. So important shift at the open source project level, which is something that I think will really be interesting and we'll see a lot of reaping a lot of rewards. Just an open source communities directly. >>Yeah, speed and durability. Certainly having that reliability is great. You know, I love talking with you guys at red hat because, you know, software, you know, open source and you know, operating systems because as it comes together in this modern era, what a great, great fit, great work you're doing with Boston University's and the mass open cloud initiative. Congratulations on that. I got I got to ask you about this Red Hat Graduate Fellows program you have because this kind of speaks to what you guys are doing, you have this kind of this redhead graduate fellows network and the work that's being done. Does that translate into red hat at all? From an engineering standpoint? How does that, how does that work together? >>Basically, what we do is we support um PhD students, we support post docs. So there's a real direct support to the, you know, that is the Red Jack Graduate Fellow program on our focus there is connecting those um uh academics, the faculty members and the students to our engineers to work together on key research initiatives that we think will help drive open source software agendas forward really broad can be in all different areas from security to virtualization too, the operating systems to cloud distributed systems, uh and one of the things that we've discovered is it creates a great relationship with the university and we find students that will be excited to leave university and come into the the industry workforce and work at Red hat. So there is a direct talent relationship between the work that we do at bu and the talent that we can bring into red hat, which is awesome. Uh We know these people we've worked with well with them, but also we're kind of expanding understanding of open source across, you know, more and more of academia, which I think is really valuable and important for red hat. We just go out to the the industry at large, um, and helping bring a set of skills to the industry that whether they're coming, whether these are students that come into red hat or go elsewhere into the industry, these are important skills to have in the industry. So we look at the, how do you work in open source communities? How to operationalize software at scale? These are important things. They didn't >>expand, expand the territory if you will in terms of systems thinking. We just talked about great collaboration. You guys do a great job chris great to have you on a quick final word from you on this year at red hat summer. I know it's virtual again, which we could be in person, but we're starting to come out of the covid kind of post covid right around the corner. Um, what's the update? How would you describe the current state of red hat? Obviously you guys still got that, that vibe. You still pumping strong a lot going on. What's the current? What's the current, uh, bumper sticker? What's the vibe? >>Well, in many ways, because we're so large and distributed. Um, the last year has been, uh, can't say business as usual because it's been an impact on everybody, but it hasn't required us to fundamentally change. And as we work across open source communities, there's been a lot of continuity that's come through a workforce that's gone completely distributed. People are anxious to get to the next phase, whatever back to normal means. Uh, and people at Red Hat are no different. So we're looking forward to what it can mean to spend time with colleagues in offices, were looking forward to what it means to spend time together with our friends and families and travel and all those things. But from a, from a business point of view, Red Hat's focus on the open hybrid cloud and that distributed view of how we work with open source communities. That's something that's, it's only continued to grow and pick up over the course of the last year. So it's clearly an important area for the industry and we've been busier than ever the last year. So, uh, interesting, interesting times for everybody. >>Well, it's great to see and I love how the culture maintains its its relevance, its coolness intersection between software, Open Source and systems. Great, Great working congratulations chris. Thanks for coming on. >>Thank you. >>All right. I'm John for here with the Cube for Red Hat Summit 2021. Thanks for watching. Mhm.

(upbeat music) >> Hi everyone, welcome to this special CUBE conversation and kickoff preview of the Mobile World Congress, Barcelona event. It's a physical event that's going to be taking place in person. It will probably be the first hybrid big event, 68 days until the June 28th kickoff. You might've heard TelcoDR, Telco Disruptor is on a mission to move the Telco industry to the public cloud. And it's taken one of the biggest spaces this year from Ericsson, is the big story everyone's talking about. And of course theCUBE is excited to be there and broadcast and be a partner with TelcoDR. So I'm excited to bring on the founder and CEO of TelcoDR, Danielle Royston. Danielle great to see you. Thanks for coming on for this Mobile World Congress Preview. >> Thank you so much for having me. I'm psyched to talk to you about this, it's going to be great. >> So Ericsson always has the biggest booth 14 years, you're disrupting Barcelona, people are not sure it's going to be on or off. It's officially on, it's happening and there's going to be a physical event, we're coming out of COVID still a risky move. It's going to be a big hybrid event, it's going to be in person. Tell us the story. How did you guys come out of nowhere, a disruptor take the biggest real estate in the place and turn it into a community event, a news event, a media event, everything, tell us. >> Yeah, well, I think it was March 9th, a little over a month ago. Ericsson announced that they were pulling out of MWC and it's very analogous to what happened in 2020. They were one of the first vendors to bail as well. And it kind of started this like tidal wave of people saying, can't do it. And I think the distinction now is that, that was at the beginning of COVID, there's a lot of unknowns. Is it coming, is it not, is it safe, is it not? We're now, year 50 to three, four months into it. I think that when you look at where we are now, cases are trending down, the vaccine is up. And I think the legacy players were sort of backward looking. They're like, this is a repeat of 2020 it's not safe to go, we're going to pull out. And I'm like with the a hundred days to go, in the vaccine ramping, I think I see the different way. I think there's a really big opportunity. John Hoffman, CEO of the GSMA had put out a two page missive on LinkedIn where he was personally responding to questions, about how serious they were about making sure that the event was safe and could be held. And my view was this is going to happen. And with Ericsson pulling out, I mean this is hollowed ground. I mean, this is massively successful company that has customers literally trained like Skinner's chickens to come to the same spot every year. And now I get to put out my shingle right there and say welcome and show them the future. And instead of the legacy past and all the normal rhetoric that you hear from those sort of dinosaurs, Ericsson and Nokia, now they're going to hear about the public cloud. And I'm really excited for this opportunity. I think the ROI on this event is instant. And so it was a pretty easy decision. I think I thought about it for about 30 seconds. >> It's a real bold move. And again it's a risk that pays off if it happens, if it doesn't, didn't happen, but it's like the startups that put a Superbowl commercial off for the first time. It's a big hit and it's a big gamble that pays off huge. Take us through, how did it all happen? Did you just wake up and saw it was open? How did you know that it was open? Was it like, does an email go out and say, hey I got this huge space for 55 years. >> Well, I mean, it was big news. It was big news in the industry that they were pulling out and all other journalists were like, oh, here we go again. Everyone's going to bail, who's next, right? And everyone was sort of like building that sort of negative momentum energy. And I'm like, we got to squash this. So I put out a tweet on Twitter. I mean, I'm not the most followed person but I'm kind of known in Telco. And I was like, hey, GSMA, I'll take over the booth. And I don't think people even liked my tweet, right? Like no likes no retweets. I reached out to a couple of journalists. I'm like, let's do an interview, let's do a story. Everyone's like, we'll have you on the podcast, like in a month, I'm like, what's? So when John Hoffman had put out that letter I had connected to him. And so I was like, oh, I'm connected to the CEO of the GSMA. So I went out on LinkedIn and I referenced the story and I said, John Hoffman, I'll take over the booth. And I think about 30 minutes later he responded and said, let's do it. And I said, great, who do I talk to? And I was in touch with someone within a couple of hours. And I think we put the whole deal together in 48. And I think wrote the press release and announced it on Friday. So happened on Tuesday the 9th, announced by that Friday. And I really, I was like, GSMA, we've got to get this out, and we got to stop the negative momentum of the show, and get people to realize it's going to be different in June. This is going to happen, let's go do it. And so I think they're psyched that I stepped into the booth. It's a big booth it's 65,000 square feet. 6,000 square meters for the rest of the world that use the metric system. And I mean, that's huge. I mean, that's the size of a professional pitch in a football field, a soccer field. That's a one and a half football fields. It's a ton of space, it's a ton of space to fill up. >> I think what's interesting, as this points out that this new business model of being connected you were on LinkedIn, you connect to them, you get a deal done so fast. This is the direct to consumer as a start up, you're literally took over the Primo space, the best face in the area, so congratulations. And the other thing that's notable and why I'm excited to talk to you is that this kind of sets the table for the first global, what I call hybrid event. This will probably be a cornerstone case study in and of itself, because we're still kind of coming out of the pandemic. People are getting vaccinated, people want to fly, they want to get out of the house. You're partnering with theCUBE, and the CUBE 365 platform. And we love hybrid, we love doing events, theCUBE, that's what we do with video. Now, we're going to do a partnership with you to create this hybrid experience. What can people and guests who come to Barcelona or watch remotely expect? >> Yeah so, I think there's a couple of experiences that we're trying to drive in the booth. I think obviously demonstrations, I can't fill 65,000 square feet on my own. I'm a startup small company. And so I am inviting like-minded, forward thinking companies to join me in the booth. I'm paying for it providing a turnkey experience for those vendors. And so I think what we have in common is we're thinking about future technologies, like open ran on the network side and obviously public cloud which is a big part of my message. And so first and foremost, come and see the companies that are driving the change, the new technologies that are out there, and what's available for carriers to start to adopt and think about. MWC is a meeting intensive event. Deals are done at this show. In 2019, I think the stat is $65 billion of deals were put together at the show. And so a big component of the booth will be a place for executives to come together and have private conversations. And so we're going to have that. So that's going to be a big piece of it. And I think the third part is driving education and thought leadership. And so there's going to be a whole talk track, right? Tech topics, business topics, customer case studies, involve the hyperscalers, and really start to educate the telco community around these new technologies. But there'll be shorter talks. They won't be like hour long keynotes. We're talking 15, 20 minutes. And I think one thing that we're going to do with you as you were just talking about with the CUBE is, you know, MWC was the first big show to have to cancel with COVID, I think in 2019, sorry, 2020, the dates, it's always the last Monday in February and the rest of that week. And so that's like right at the beginning of the COVID stuff, Italy was just starting to take off. And so it was one of the first shows that had to make a big call and decide to cancel, which they did. This is going to be one of the first shows that comes back online post COVID, right? And so I don't think things just snap back to the way that they used to be. I don't think we as consumers are going to snap back to the way that we were operating, we're now used to being able to get curbside delivery from any restaurant in the city. I mean, it's just a sort of a different expectation. And so partnering with the CUBE, we really want to provide an experience that brings the virtual people into the booth. Typically in events like this, you really have to be there to see it. Booths are kind of like unveiled the day of the show, what's going on. One thing I'm trying to do is really educate people about what you can expect. What can you see? This is what it's going to look like. And so we're going to start to share some pictures of the booth of what it looks like. Number one, to drive excitement with the partners that are coming, right? Like you're going to be part of something really, really fabulous. I think number two, attendees can wait, I don't know week off, to make the decision to go. And so maybe if COVID continues to trend down and vaccines are picking up steam, maybe they're like it's safe for me to go and I want to go be a part of that. But I think from here on now we're going to have sort of that virtual experience. It's always going to be part of shows. And so we're going to experiment with you guys. We're going to have a live streaming event, over the course of all MWC. It's going to be a way for people who are unable to travel or can't afford it, COVID or whatever, see what's going on in the booth. And it's going to be everything from listen to a talk, to watch what you guys are typically famous for, your awesome interviews. We're going to have man on the street, like we're here at at a demo station, take us through your little demo. We're going to have telepresence robots that people can reserve. And cruise through the booth the robot can go to a talk. The robot can watch on this streaming thing, the robot can go to a demo. The robot can go to a meeting and it's controlled by the the virtual attendees. And so experimenting, right? Like how do we make this great for virtual people? How do we make the virtual people feel part of the physical? How do the physical people feel the virtual people that are attending and really just make it feel like a community or both. So, we're excited. >> That's super awesome, and first of all, thank you for having paying for everyone and including theCUBE in there. But I think this speaks to the ecosystem of open, you're creating an open ecosystem. And I think that is a huge thing. So for people who are at Mobile World Congress in Barcelona this is going to be a nice, safe place to hang space as well as get deals done. As we comfortable doing media center, we'll get you on the digital TV, but also you're also designing what I call the first hybrid experience, not just having people, having on-demand videos on their website, connecting Barcelona with other parts of the world, with media and stories and content. I think that to me is going to be a great experiment slash upgrade. We'll see, we'll get to see it how it goes. >> Well, it was really, I mean, we all lived through 2020. I mean, some of the shows went on, AWS's re-invent happened, Google did like a crazy nine week program. It's very lonely to participate in those virtual events. You kind of log on by ourselves. No one's really tweeting about it. You're watching an event, the event is great but it was really lonely. And so I think what people love about the physical events is we're together and we're networking and we're meeting people and so, I think continuing to evolve that experience so that virtual is not as lonely. So we'll see, we'll see how it goes. >> I got to say your vision is really aligned with us and others that are in this open innovation world. Because if you look at like theCUBE, physical went away, we had no events, we did CUBE Virtual, a new brand. It wasn't a pivot, it was an extension, a line extension of theCUBE. Now theCUBE's coming back to the physical, we're going to bring that CUBE Virtual to connect everybody. So this is it, and it just amplifies the value of the physical event. So if done right, it's so much cooler. So that's cool. And what I want to ask you on the physical side to kind of bring it back to physical is, there's still going to be keynotes, there's still going to be talks at Mobile World Congress, and so I saw that scheduled and I just saw last week, GSM may announced you're going to be doing a keynote speech. That's amazing, so, how did that happen? So give us the lowdown on the keynote that you're doing. >> I'm sure the entire industry is like that happened. And it probably has something to do with the fact that I have one of the biggest booths at the space. I always put in a request to speak. I feel that I have a really exciting message to share with the industry. Over the last, I guess it's been nine or 10 months, I really been trying to amplify my voice. I have a podcast, I have a newsletter, I'm talking to execs. I have a list that I literally go down one by one stalking each executive of like, have I talked to them? Like how I told them about like the power of the public cloud. And so I am super thankful that I have this opportunity to spread that this message and I'm planning a really epic talk. I really want to shake the industry And this is my opportunity, right? This is my opportunity to stand on the biggest stage in our industry and command a presence and send out my message. And I'm absolutely thrilled to go do it. And I hope I crush it, I hope it's like a mic drop experience. And can't wait to do it. >> Well, we're looking forward to covering it. And we love the open vision. We love the idea of public cloud and the enablement and the disruption. Because just like you got the deal so fast you can move fast with modern applications with the cloud, moving at cloud scale, complete content game changer, so great stuff. So totally applaud that looking forward to and we're here cheer you on and ask the tough questions. I do want to get to... On Twitter yesterday though, you put out on tweetstorm on Twitter about the plans kind of teasing out the booth, how are you going to plan to build the booth. Are you worried that you're opening up too much of the kimono here and putting too much on the table 'cause it's usually a secret. Mobile World Congress is supposed to be secret, not publicly out there. What's the-- >> Well, I mean, I think this is just a little bit of a change has happened post COVID, right. People usually build their booth at don't reveal it until the first day of the show and it's kind of like this excitement to go see what is their big message and what's the big reveal. And there's always fun stuff. I think this years will be different as a first, like I said, a first big event back. I think I need to create a little bit of excitement for people who are going and maybe entice people that maybe you should think about coming. I realized this is a super personal decision, right? It depends on where you are and the country and your health and your status. But if you can do it, I want people to know that you're going to miss out. It's going to be super fun. So, yeah. >> Let's take a look at the booth 'cause I'm sure my next question wants to see. I know we have guys, do we have that rendering... Let's pull that up and let's talk this through. Let's go look at the rendering. So you can see here on the screen... Take us through this. >> Yeah, so what we want to do is give the sense of of cloud city and that's what we're calling the space. In cloud city there's outdoor space, like you see here. And then there's an indoor space. And indoors is where you work, where you buy, where you meet. And so you can see here on the left, the demonstration that would have different vendors displaying and it goes way back. I mean, what we're feeling like I said is like a football field, an American football field and a half or a European football field, a pitch. It's pretty extensive. And so we think we're going to have, I don't know, 20, 30 vendors showing their different software. I think we're scheduling or planning for about 24 different meeting rooms that we can schedule. All COVID safe with the space requirements in there. But in that outdoor space, it would be where you learn, the education. And then I think we're going to have this fabulous booth for theCUBE. It's going to look just so amazing with the backdrop of this amazing building. And I think I underappreciated or didn't really realize how devastated the event planning industry has been from COVID as well as construction. Obviously when events were shut down, these companies had to lay off thousands of workers. Some of the big firms have laid off 50% of their workforce. And those people they didn't just go home and sit around, they had to come up with a livelihood and those people have pivoted into another job. And they're not really, I mean, events aren't really back yet. So some of these firms are shrunk. The manpower is severely reduced. But then I think on the other side is, and you can see this in just housing construction. There's a lumber shortage, there's a shortage of materials. And so everything that we source for the booth, pretty much has to come from Spain. And so when we look at the booth, we have a pretty significant ceiling, where it looks like the roof of the building. It's an engineering feat to do that we're still working through the... I'm sure someone with a protractor is doing lots of math. The glass, we have those huge beautiful glass spans in the front. Getting a glass that spans that height, I think it's 18 feet. It's six meters tall. That's going to be hard. Things like the flooring. I want to have like hardwood laminate flooring. So it looks like hardwood floors. Don't know if we can find them. There like, why don't you do carpet? I'm like, can you just check one more vendor. I really want my floor. So we'll see how it goes. And yeah, I think that sharing this plan, the trials and tribulations, like how can this small startup, take over a space that usually takes nine months to plan, right? Who is this girl? What is she doing? How are they going to pull this off? I think it's like, grab your popcorn and watch the train wreck or hero's journey. We get it done. And I'm obviously-- >> It's like keeping up with the Kardashians. It's the bachelor, it's theCUBE, reality TV show. We can keep track of everything. It's all the fun. >> No, totally. I don't know how many people would be interested in a reality TV show about how you build a booth but I find it absolutely fascinating. I think a lot of people have eyes on the GMA and MWC coming out of COVID and what does that look like, and what's the attendance like. And so I'm excited to share (murmurs) So, exact. >> Well, people are on clubhouse, they're bored, they want to get out. I think this is a case time. Mobile World Congress has a huge economic impact, as a show it's got its own little economy built around. It impacts the country of Spain in Barcelona, the city, a great city. People love it. And so it certainly is notable and newsworthy. We will be following that story. I have to ask you more kind of a tactical question if you don't mind, while I have you here. Can you talk about some of the vendors that are coming and the kinds of talks you're going to have inside the booth and how do people get involved? You mentioned it's open to people who love open ran and open public cloud, open technologies. I mean, that's pretty much everybody. That's cool and relevant, which is like almost the whole world now. Like, is it going to be a space as a criteria? How do people get involved? What's the collaboration formula? >> Yeah, no, I have been working on putting together a list of potential vendors. You'd be surprised, not everyone is as bullish as I am on the public cloud. And so there was a little bit of a filtering criteria but otherwise anyone can come. Enterprise software vendors in telco where their primary customer is communications service provider. That's their software runs on the public cloud, come on in. People using open ran. And it's still a little sort of small band of cohorts that are really trying to drive this new technology forward and they're going up against some of the biggest companies in telco, right? They're going up against Huawei, they're going up against Ericsson. Both those guys are very anti and they're not really pro open ran 'cause it's hugely disruptive to their business. And so I'm pretty sure those guys are not psyched to see open ran become a thing in telco. And so it's really sort of about disruptive technologies that are in the booth. And so yeah, I'm paying for the space, I'm paying for the build-out, bring your demos, bring your people, come with your marketing message and let's build a community. And so we're talking to open ran vendors like Mavenir which is a pretty big name in the open ran space. I've been talking with Parallel Wireless in LTO Star. Those are also great players. Software vendors like to Tutoki, which is a talk that I did a little over a month ago about this new startup that has a web-scale charger that they're trying to put out there. Auria is another company that I'm really familiar with that has some cloud for software. And in little tiny startups like Sequence and some other up-and-comers that no one's heard of. So we're really excited to invite them into the booth. I've been secretly stalking Elon Musk, and Starlink and Space X to be a part of it. And we'll see. I'm kind of using Twitter and whatever I can to reach out and see if they want to be a part of it. But yeah, it really open arms. Not really excluding-- >> Well, Elon is very disruptive and you can reach out to him on Twitter. He's accessible. I mean, you've got to break through and he's antenna up for innovators, people who think differently, they love people who break down walls and markets lower open wins. I mean, we know there's a history, we've been covering it. I've been involved in all my career. People who bet against open always lose. It's happened in every single wave of innovation. So Elon's gettable. Let's get him. >> Who doesn't love Elon Musk? I mean, I think some people don't, I love him. He's my hero. I model a lot of the things that I do around his approach, his vision. 20 years ago, or close to 20 years ago, 2003, he said he was going to put people on Mars. And I think people laughed at him for being like the PayPal guy and this guy is crazy, but every year he makes progress against his goals. We have a relandable rocket. He's doing a manned mission this week, the second man mission or third man mission. The guy makes progress. And I think I'm on the same mission here. My mission is to move Telco to the public cloud. I think it's a long journey, right? I think people are like, who is this girl? And she's like 12 people and what's her story. And I'm like, I don't care. I have a singular mission is a quest. I am not going to stop until I move the industry to the public cloud. And it's my life's mission and I'm psyched to do it. >> Well, we love the mojo, we love your style. We love Elon Musk's mojo. And again, just to bring the dots together you have that same mindset, which is, love like Elon, he's a builder. He builds things and he delivers. So as you said, so... Danielle, I really appreciate the work you're doing. I love your philosophy. We're in total agreement. Open building. Doing it together as a collective, being part of something? This is what the world needs. You got a lot of great ideas in the works and we can't wait to hear them. And what you got coming up over the next 68 days. This is the first of many conversations together. Thank you. >> Yeah, that's going to be so awesome. Thank you so much for having me. Psyched to talk to you about it. >> Okay. Mobile World Congress is happening in Barcelona on the June 28th. It's going to be in person and it's going to be probably the biggest hybrid event to date. Be there, check out TelcoDR and theCUBE and the space that they took over 14 years at the helm there. Ericson had it, now it's TelcoDR. Danielle Royston, founder and CEO here with me from TelcoDR. Thanks for watching. (upbeat music)

from around the globe it's thecube with digital coverage of exascale day made possible by hewlett packard enterprise welcome everyone to the cube celebration of exascale day ben bennett is here he's an hpc strategist and evangelist at hewlett-packard enterprise ben welcome good to see you good to see you too son hey well let's evangelize exascale a little bit you know what's exciting you uh in regards to the coming of exoskilled computing um well there's a couple of things really uh for me historically i've worked in super computing for many years and i have seen the coming of several milestones from you know actually i'm old enough to remember gigaflops uh coming through and teraflops and petaflops exascale is has been harder than many of us anticipated many years ago the sheer amount of technology that has been required to deliver machines of this performance has been has been us utterly staggering but the exascale era brings with it real solutions it gives us opportunities to do things that we've not been able to do before if you look at some of the the most powerful computers around today they've they've really helped with um the pandemic kovid but we're still you know orders of magnitude away from being able to design drugs in situ test them in memory and release them to the public you know we still have lots and lots of lab work to do and exascale machines are going to help with that we are going to be able to to do more um which ultimately will will aid humanity and they used to be called the grand challenges and i still think of them as that i still think of these challenges for scientists that exascale class machines will be able to help but also i'm a realist is that in 10 20 30 years time you know i should be able to look back at this hopefully touch wood look back at it and look at much faster machines and say do you remember the days when we thought exascale was faster yeah well you mentioned the pandemic and you know the present united states was tweeting this morning that he was upset that you know the the fda in the u.s is not allowing the the vaccine to proceed as fast as you'd like it in fact it the fda is loosening some of its uh restrictions and i wonder if you know high performance computing in part is helping with the simulations and maybe predicting because a lot of this is about probabilities um and concerns is is is that work that is going on today or are you saying that that exascale actually you know would be what we need to accelerate that what's the role of hpc that you see today in regards to sort of solving for that vaccine and any other sort of pandemic related drugs so so first a disclaimer i am not a geneticist i am not a biochemist um my son is he tries to explain it to me and it tends to go in one ear and out the other um um i just merely build the machines he uses so we're sort of even on that front um if you read if you had read the press there was a lot of people offering up systems and computational resources for scientists a lot of the work that has been done understanding the mechanisms of covid19 um have been you know uncovered by the use of very very powerful computers would exascale have helped well clearly the faster the computers the more simulations we can do i think if you look back historically no vaccine has come to fruition as fast ever under modern rules okay admittedly the first vaccine was you know edward jenner sat quietly um you know smearing a few people and hoping it worked um i think we're slightly beyond that the fda has rules and regulations for a reason and we you don't have to go back far in our history to understand the nature of uh drugs that work for 99 of the population you know and i think exascale widely available exoscale and much faster computers are going to assist with that imagine having a genetic map of very large numbers of people on the earth and being able to test your drug against that breadth of person and you know that 99 of the time it works fine under fda rules you could never sell it you could never do that but if you're confident in your testing if you can demonstrate that you can keep the one percent away for whom that drug doesn't work bingo you now have a drug for the majority of the people and so many drugs that have so many benefits are not released and drugs are expensive because they fail at the last few moments you know the more testing you can do the more testing in memory the better it's going to be for everybody uh personally are we at a point where we still need human trials yes do we still need due diligence yes um we're not there yet exascale is you know it's coming it's not there yet yeah well to your point the faster the computer the more simulations and the higher the the chance that we're actually going to going to going to get it right and maybe compress that time to market but talk about some of the problems that you're working on uh and and the challenges for you know for example with the uk government and maybe maybe others that you can you can share with us help us understand kind of what you're hoping to accomplish so um within the united kingdom there was a report published um for the um for the uk research institute i think it's the uk research institute it might be epsrc however it's the body of people responsible for funding um science and there was a case a science case done for exascale i'm not a scientist um a lot of the work that was in this documentation said that a number of things that can be done today aren't good enough that we need to look further out we need to look at machines that will do much more there's been a program funded called asimov and this is a sort of a commercial problem that the uk government is working with rolls royce and they're trying to research how you build a full engine model and by full engine model i mean one that takes into account both the flow of gases through it and how those flow of gases and temperatures change the physical dynamics of the engine and of course as you change the physical dynamics of the engine you change the flow so you need a closely coupled model as air travel becomes more and more under the microscope we need to make sure that the air travel we do is as efficient as possible and currently there aren't supercomputers that have the performance one of the things i'm going to be doing as part of this sequence of conversations is i'm going to be having an in detailed uh sorry an in-depth but it will be very detailed an in-depth conversation with professor mark parsons from the edinburgh parallel computing center he's the director there and the dean of research at edinburgh university and i'm going to be talking to him about the azimoth program and and mark's experience as the person responsible for looking at exascale within the uk to try and determine what are the sort of science problems that we can solve as we move into the exoscale era and what that means for humanity what are the benefits for humans yeah and that's what i wanted to ask you about the the rolls-royce example that you gave it wasn't i if i understood it wasn't so much safety as it was you said efficiency and so that's that's what fuel consumption um it's it's partly fuel consumption it is of course safety there is a um there is a very specific test called an extreme event or the fan blade off what happens is they build an engine and they put it in a cowling and then they run the engine at full speed and then they literally explode uh they fire off a little explosive and they fire a fan belt uh a fan blade off to make sure that it doesn't go through the cowling and the reason they do that is there has been in the past uh a uh a failure of a fan blade and it came through the cowling and came into the aircraft depressurized the aircraft i think somebody was killed as a result of that and the aircraft went down i don't think it was a total loss one death being one too many but as a result you now have to build a jet engine instrument it balance the blades put an explosive in it and then blow the fan blade off now you only really want to do that once it's like car crash testing you want to build a model of the car you want to demonstrate with the dummy that it is safe you don't want to have to build lots of cars and keep going back to the drawing board so you do it in computers memory right we're okay with cars we have computational power to resolve to the level to determine whether or not the accident would hurt a human being still a long way to go to make them more efficient uh new materials how you can get away with lighter structures but we haven't got there with aircraft yet i mean we can build a simulation and we can do that and we can be pretty sure we're right um we still need to build an engine which costs in excess of 10 million dollars and blow the fan blade off it so okay so you're talking about some pretty complex simulations obviously what are some of the the barriers and and the breakthroughs that are kind of required you know to to do some of these things that you're talking about that exascale is going to enable i mean presumably there are obviously technical barriers but maybe you can shed some light on that well some of them are very prosaic so for example power exoscale machines consume a lot of power um so you have to be able to design systems that consume less power and that goes into making sure they're cooled efficiently if you use water can you reuse the water i mean the if you take a laptop and sit it on your lap and you type away for four hours you'll notice it gets quite warm um an exascale computer is going to generate a lot more heat several megawatts actually um and it sounds prosaic but it's actually very important to people you've got to make sure that the systems can be cooled and that we can power them yeah so there's that another issue is the software the software models how do you take a software model and distribute the data over many tens of thousands of nodes how do you do that efficiently if you look at you know gigaflop machines they had hundreds of nodes and each node had effectively a processor a core a thread of application we're looking at many many tens of thousands of nodes cores parallel threads running how do you make that efficient so is the software ready i think the majority of people will tell you that it's the software that's the problem not the hardware of course my friends in hardware would tell you ah software is easy it's the hardware that's the problem i think for the universities and the users the challenge is going to be the software i think um it's going to have to evolve you you're just you want to look at your machine and you just want to be able to dump work onto it easily we're not there yet not by a long stretch of the imagination yeah consequently you know we one of the things that we're doing is that we have a lot of centers of excellence is we will provide well i hate say the word provide we we sell super computers and once the machine has gone in we work very closely with the establishments create centers of excellence to get the best out of the machines to improve the software um and if a machine's expensive you want to get the most out of it that you can you don't just want to run a synthetic benchmark and say look i'm the fastest supercomputer on the planet you know your users who want access to it are the people that really decide how useful it is and the work they get out of it yeah the economics is definitely a factor in fact the fastest supercomputer in the planet but you can't if you can't afford to use it what good is it uh you mentioned power uh and then the flip side of that coin is of course cooling you can reduce the power consumption but but how challenging is it to cool these systems um it's an engineering problem yeah we we have you know uh data centers in iceland where it gets um you know it doesn't get too warm we have a big air cooled data center in in the united kingdom where it never gets above 30 degrees centigrade so if you put in water at 40 degrees centigrade and it comes out at 50 degrees centigrade you can cool it by just pumping it round the air you know just putting it outside the building because the building will you know never gets above 30 so it'll easily drop it back to 40 to enable you to put it back into the machine um right other ways to do it um you know is to take the heat and use it commercially there's a there's a lovely story of they take the hot water out of the supercomputer in the nordics um and then they pump it into a brewery to keep the mash tuns warm you know that's that's the sort of engineering i can get behind yeah indeed that's a great application talk a little bit more about your conversation with professor parsons maybe we could double click into that what are some of the things that you're going to you're going to probe there what are you hoping to learn so i think some of the things that that are going to be interesting to uncover is just the breadth of science that can be uh that could take advantage of exascale you know there are there are many things going on that uh that people hear about you know we people are interested in um you know the nobel prize they might have no idea what it means but the nobel prize for physics was awarded um to do with research into black holes you know fascinating and truly insightful physics um could it benefit from exascale i have no idea uh i i really don't um you know one of the most profound pieces of knowledge in in the last few hundred years has been the theory of relativity you know an austrian patent clerk wrote e equals m c squared on the back of an envelope and and voila i i don't believe any form of exascale computing would have helped him get there any faster right that's maybe flippant but i think the point is is that there are areas in terms of weather prediction climate prediction drug discovery um material knowledge engineering uh problems that are going to be unlocked with the use of exascale class systems we are going to be able to provide more tools more insight [Music] and that's the purpose of computing you know it's not that it's not the data that that comes out and it's the insight we get from it yeah i often say data is plentiful insights are not um ben you're a bit of an industry historian so i've got to ask you you mentioned you mentioned mentioned gigaflop gigaflops before which i think goes back to the early 1970s uh but the history actually the 80s is it the 80s okay well the history of computing goes back even before that you know yes i thought i thought seymour cray was you know kind of father of super computing but perhaps you have another point of view as to the origination of high performance computing [Music] oh yes this is um this is this is one for all my colleagues globally um you know arguably he says getting ready to be attacked from all sides arguably you know um computing uh the parallel work and the research done during the war by alan turing is the father of high performance computing i think one of the problems we have is that so much of that work was classified so much of that work was kept away from commercial people that commercial computing evolved without that knowledge i uh i have done in in in a previous life i have done some work for the british science museum and i have had the great pleasure in walking through the the british science museum archives um to look at how computing has evolved from things like the the pascaline from blaise pascal you know napier's bones the babbage's machines uh to to look all the way through the analog machines you know what conrad zeus was doing on a desktop um i think i think what's important is it doesn't matter where you are is that it is the problem that drives the technology and it's having the problems that requires the you know the human race to look at solutions and be these kicks started by you know the terrible problem that the us has with its nuclear stockpile stewardship now you've invented them how do you keep them safe originally done through the ascii program that's driven a lot of computational advances ultimately it's our quest for knowledge that drives these machines and i think as long as we are interested as long as we want to find things out there will always be advances in computing to meet that need yeah and you know it was a great conversation uh you're a brilliant guest i i love this this this talk and uh and of course as the saying goes success has many fathers so there's probably a few polish mathematicians that would stake a claim in the uh the original enigma project as well i think i think they drove the algorithm i think the problem is is that the work of tommy flowers is the person who took the algorithms and the work that um that was being done and actually had to build the poor machine he's the guy that actually had to sit there and go how do i turn this into a machine that does that and and so you know people always remember touring very few people remember tommy flowers who actually had to turn the great work um into a working machine yeah super computer team sport well ben it's great to have you on thanks so much for your perspectives best of luck with your conversation with professor parsons we'll be looking forward to that and uh and thanks so much for coming on thecube a complete pleasure thank you and thank you everybody for watching this is dave vellante we're celebrating exascale day you're watching the cube [Music]

>>welcome. My name is Ben Bennett. I am the director of HPC Strategic programs here at Hewlett Packard Enterprise. It is my great pleasure and honor to be talking to Professor Mark Parsons from the Edinburgh Parallel Computing Center. And we're gonna talk a little about exa scale. What? It means we're gonna talk less about the technology on Maura about the science, the requirements on the need for exa scale. Uh, rather than a deep dive into the enabling technologies. Mark. Welcome. >>I then thanks very much for inviting me to tell me >>complete pleasure. Um, so I'd like to kick off with, I suppose. Quite an interesting look back. You and I are both of a certain age 25 plus, Onda. We've seen these milestones. Uh, I suppose that the S I milestones of high performance computing's come and go, you know, from a gig a flop back in 1987 teraflop in 97 a petaflop in 2000 and eight. But we seem to be taking longer in getting to an ex a flop. Um, so I'd like your thoughts. Why is why is an extra flop taking so long? >>So I think that's a very interesting question because I started my career in parallel computing in 1989. I'm gonna join in. IPCC was set up then. You know, we're 30 years old this year in 1990 on Do you know the fastest computer we have them is 800 mega flops just under a getting flogged. So in my career, we've gone already. When we reached the better scale, we'd already gone pretty much a million times faster on, you know, the step from a tariff block to a block scale system really didn't feel particularly difficult. Um, on yet the step from A from a petaflop PETA scale system. To an extent, block is a really, really big challenge. And I think it's really actually related to what's happened with computer processes over the last decade, where, individually, you know, approached the core, Like on your laptop. Whoever hasn't got much faster, we've just got more often So the perception of more speed, but actually just being delivered by more course. And as you go down that approach, you know what happens in the supercomputing world as well. We've gone, uh, in 2010 I think we had systems that were, you know, a few 1000 cores. Our main national service in the UK for the last eight years has had 118,000 cores. But looking at the X scale we're looking at, you know, four or five million cores on taming that level of parallelism is the real challenge. And that's why it's taking an enormous and time to, uh, deliver these systems. That is not just on the hardware front. You know, vendors like HP have to deliver world beating technology and it's hard, hard. But then there's also the challenge to the users. How do they get the codes to work in the face of that much parallelism? >>If you look at what the the complexity is delivering an annex a flop. Andi, you could have bought an extra flop three or four years ago. You couldn't have housed it. You couldn't have powered it. You couldn't have afforded it on, do you? Couldn't program it. But you still you could have You could have bought one. We should have been so lucky to be unable to supply it. Um, the software, um I think from our standpoint, is is looking like where we're doing mawr enabling with our customers. You sell them a machine on, then the the need then to do collaboration specifically seems mawr and Maura around the software. Um, so it's It's gonna be relatively easy to get one x a flop using limb pack, but but that's not extra scale. So what do you think? On exa scale machine versus an X? A flop machine means to the people like yourself to your users, the scientists and industry. What is an ex? A flop versus >>an exa scale? So I think, you know, supercomputing moves forward by setting itself challenges. And when you when you look at all of the excess scale programs worldwide that are trying to deliver systems that can do an X a lot form or it's actually very arbitrary challenge. You know, we set ourselves a PETA scale challenge delivering a petaflop somebody manage that, Andi. But you know, the world moves forward by setting itself challenges e think you know, we use quite arbitrary definition of what we mean is well by an exit block. So, you know, in your in my world, um, we either way, first of all, see ah flop is a computation, so multiply or it's an ad or whatever on we tend. Thio, look at that is using very high precision numbers or 64 bit numbers on Do you know, we then say, Well, you've got to do the next block. You've got to do a billion billion of those calculations every second. No, a some of the last arbitrary target Now you know today from HPD Aiken by my assistant and will do a billion billion calculations per second. And they will either do that as a theoretical peak, which would be almost unattainable, or using benchmarks that stressed the system on demonstrate a relaxing law. But again, those benchmarks themselves attuned Thio. Just do those calculations and deliver and explore been a steady I'll way if you like. So, you know, way kind of set ourselves this this this big challenge You know, the big fence on the race course, which were clambering over. But the challenge in itself actually should be. I'm much more interesting. The water we're going to use these devices for having built um, eso. Getting into the extra scale era is not so much about doing an extra block. It's a new generation off capability that allows us to do better scientific and industrial research. And that's the interesting bit in this whole story. >>I would tend to agree with you. I think the the focus around exa scale is to look at, you know, new technologies, new ways of doing things, new ways of looking at data and to get new results. So eventually you will get yourself a nexus scale machine. Um, one hopes, sooner rather >>than later. Well, I'm sure you don't tell me one, Ben. >>It's got nothing to do with may. I can't sell you anything, Mark. But there are people outside the door over there who would love to sell you one. Yes. However, if we if you look at your you know your your exa scale machine, Um, how do you believe the workloads are going to be different on an extra scale machine versus your current PETA scale machine? >>So I think there's always a slight conceit when you buy a new national supercomputer. On that conceit is that you're buying a capability that you know on. But many people will run on the whole system. Known truth. We do have people that run on the whole of our archer system. Today's A 118,000 cores, but I would say, and I'm looking at the system. People that run over say, half of that can be counted on Europe on a single hand in a year, and they're doing very specific things. It's very costly simulation they're running on. So, you know, if you look at these systems today, two things show no one is. It's very difficult to get time on them. The Baroque application procedures All of the requirements have to be assessed by your peers and your given quite limited amount of time that you have to eke out to do science. Andi people tend to run their applications in the sweet spot where their application delivers the best performance on You know, we try to push our users over time. Thio use reasonably sized jobs. I think our average job says about 20,000 course, she's not bad, but that does mean that as we move to the exits, kill two things have to happen. One is actually I think we've got to be more relaxed about giving people access to the system, So let's give more people access, let people play, let people try out ideas they've never tried out before. And I think that will lead to a lot more innovation and computational science. But at the same time, I think we also need to be less precious. You know, we to accept these systems will have a variety of sizes of job on them. You know, we're still gonna have people that want to run four million cores or two million cores. That's absolutely fine. Absolutely. Salute those people for trying really, really difficult. But then we're gonna have a huge spectrum of views all the way down to people that want to run on 500 cores or whatever. So I think we need Thio broaden the user base in Alexa Skill system. And I know this is what's happening, for example, in Japan with the new Japanese system. >>So, Mark, if you cast your mind back to almost exactly a year ago after the HPC user forum, you were interviewed for Premier Magazine on Do you alluded in that article to the needs off scientific industrial users requiring, you know, uh on X a flop or an exa scale machine it's clear in your in your previous answer regarding, you know, the workloads. Some would say that the majority of people would be happier with, say, 10 100 petaflop machines. You know, democratization. More people access. But can you provide us examples at the type of science? The needs of industrial users that actually do require those resources to be put >>together as an exa scale machine? So I think you know, it's a very interesting area. At the end of the day, these systems air bought because they are capability systems on. I absolutely take the argument. Why shouldn't we buy 10 100 pattern block systems? But there are a number of scientific areas even today that would benefit from a nexus school system and on these the sort of scientific areas that will use as much access onto a system as much time and as much scale of the system as they can, as you can give them eso on immediate example. People doing chroma dynamics calculations in particle physics, theoretical calculations, they would just use whatever you give them. But you know, I think one of the areas that is very interesting is actually the engineering space where, you know, many people worry the engineering applications over the last decade haven't really kept up with this sort of supercomputers that we have. I'm leading a project called Asimov, funded by M. P S O. C in the UK, which is jointly with Rolls Royce, jointly funded by Rolls Royce and also working with the University of Cambridge, Oxford, Bristol, Warrick. We're trying to do the whole engine gas turbine simulation for the first time. So that's looking at the structure of the gas turbine, the airplane engine, the structure of it, how it's all built it together, looking at the fluid dynamics off the air and the hot gasses, the flu threat, looking at the combustion of the engine looking how fuel is spread into the combustion chamber. Looking at the electrics around, looking at the way the engine two forms is, it heats up and cools down all of that. Now Rolls Royce wants to do that for 20 years. Andi, Uh, whenever they certify, a new engine has to go through a number of physical tests, and every time they do on those tests, it could cost them as much as 25 to $30 million. These are very expensive tests, particularly when they do what's called a blade off test, which would be, you know, blade failure. They could prove that the engine contains the fragments of the blade. Sort of think, continue face really important test and all engines and pass it. What we want to do is do is use an exa scale computer to properly model a blade off test for the first time, so that in future, some simulations can become virtual rather than having thio expend all of the money that Rolls Royce would normally spend on. You know, it's a fascinating project is a really hard project to do. One of the things that I do is I am deaf to share this year. Gordon Bell Price on bond I've really enjoyed to do. That's one of the major prizes in our area, you know, gets announced supercomputing every year. So I have the pleasure of reading all the submissions each year. I what's been really interesting thing? This is my third year doing being on the committee on what's really interesting is the way that big systems like Summit, for example, in the US have pushed the user communities to try and do simulations Nowhere. Nobody's done before, you know. And we've seen this as well, with papers coming after the first use of the for Goku system in Japan, for example, people you know, these are very, very broad. So, you know, earthquake simulation, a large Eddie simulations of boats. You know, a number of things around Genome Wide Association studies, for example. So the use of these computers spans of last area off computational science. I think the really really important thing about these systems is their challenging people that do calculations they've never done before. That's what's important. >>Okay, Thank you. You talked about challenges when I nearly said when you and I had lots of hair, but that's probably much more true of May. Um, we used to talk about grand challenges we talked about, especially around the teraflop era, the ski red program driving, you know, the grand challenges of science, possibly to hide the fact that it was a bomb designing computer eso they talked about the grand challenges. Um, we don't seem to talk about that much. We talk about excess girl. We talk about data. Um Where are the grand challenges that you see that an exa scale computer can you know it can help us. Okay, >>so I think grand challenges didn't go away. Just the phrase went out of fashion. Um, that's like my hair. I think it's interesting. The I do feel the science moves forward by setting itself grand challenges and always had has done, you know, my original backgrounds in particle physics. I was very lucky to spend four years at CERN working in the early stage of the left accelerator when it first came online on. Do you know the scientists there? I think they worked on left 15 years before I came in and did my little ph d on it. Andi, I think that way of organizing science hasn't changed. We just talked less about grand challenges. I think you know what I've seen over the last few years is a renaissance in computational science, looking at things that have previously, you know, people have said have been impossible. So a couple of years ago, for example, one of the key Gordon Bell price papers was on Genome Wide Association studies on some of it. If I may be one of the winner of its, if I remember right on. But that was really, really interesting because first of all, you know, the sort of the Genome Wide Association Studies had gone out of favor in the bioinformatics by a scientist community because people thought they weren't possible to compute. But that particular paper should Yes, you could do these really, really big Continental little problems in a reasonable amount of time if you had a big enough computer. And one thing I felt all the way through my career actually is we've probably discarded Mawr simulations because they were impossible at the time that we've actually decided to do. And I sometimes think we to challenge ourselves by looking at the things we've discovered in the past and say, Oh, look, you know, we could actually do that now, Andi, I think part of the the challenge of bringing an extra service toe life is to get people to think about what they would use it for. That's a key thing. Otherwise, I always say, a computer that is unused to just be turned off. There's no point in having underutilized supercomputer. Everybody loses from that. >>So Let's let's bring ourselves slightly more up to date. We're in the middle of a global pandemic. Uh, on board one of the things in our industry has bean that I've been particularly proud about is I've seen the vendors, all the vendors, you know, offering up machine's onboard, uh, making resources available for people to fight things current disease. Um, how do you see supercomputers now and in the future? Speeding up things like vaccine discovery on help when helping doctors generally. >>So I think you're quite right that, you know, the supercomputer community around the world actually did a really good job of responding to over 19. Inasmuch as you know, speaking for the UK, we put in place a rapid access program. So anybody wanted to do covert research on the various national services we have done to the to two services Could get really quick access. Um, on that, that has worked really well in the UK You know, we didn't have an archer is an old system, Aziz. You know, we didn't have the world's largest supercomputer, but it is happily bean running lots off covert 19 simulations largely for the biomedical community. Looking at Druk modeling and molecular modeling. Largely that's just been going the US They've been doing really large uh, combinatorial parameter search problems on on Summit, for example, looking to see whether or not old drugs could be reused to solve a new problem on DSO, I think, I think actually, in some respects Kobe, 19 is being the sounds wrong. But it's actually been good for supercomputing. Inasmuch is pointed out to governments that supercomputers are important parts off any scientific, the active countries research infrastructure. >>So, um, I'll finish up and tap into your inner geek. Um, there's a lot of technologies that are being banded around to currently enable, you know, the first exa scale machine, wherever that's going to be from whomever, what are the current technologies or emerging technologies that you are interested in excited about looking forward to getting your hands on. >>So in the business case I've written for the U. K's exa scale computer, I actually characterized this is a choice between the American model in the Japanese model. Okay, both of frozen, both of condoms. Eso in America, they're very much gone down the chorus plus GPU or GPU fruit. Um, so you might have, you know, an Intel Xeon or an M D process er center or unarmed process or, for that matter on you might have, you know, 24 g. P. U s. I think the most interesting thing that I've seen is definitely this move to a single address space. So the data that you have will be accessible, but the G p u on the CPU, I think you know, that's really bean. One of the key things that stopped the uptake of GPS today and that that that one single change is going Thio, I think, uh, make things very, very interesting. But I'm not entirely convinced that the CPU GPU model because I think that it's very difficult to get all the all the performance set of the GPU. You know, it will do well in H p l, for example, high performance impact benchmark we're discussing at the beginning of this interview. But in riel scientific workloads, you know, you still find it difficult to find all the performance that has promised. So, you know, the Japanese approach, which is the core, is only approach. E think it's very attractive, inasmuch as you know They're using very high bandwidth memory, very interesting process of which they are going to have to, you know, which they could develop together over 10 year period. And this is one thing that people don't realize the Japanese program and the American Mexico program has been working for 10 years on these systems. I think the Japanese process really interesting because, um, it when you look at the performance, it really does work for their scientific work clothes, and that's that does interest me a lot. This this combination of a A process are designed to do good science, high bandwidth memory and a real understanding of how data flows around the supercomputer. I think those are the things are exciting me at the moment. Obviously, you know, there's new networking technologies, I think, in the fullness of time, not necessarily for the first systems. You know, over the next decade we're going to see much, much more activity on silicon photonics. I think that's really, really fascinating all of these things. I think in some respects the last decade has just bean quite incremental improvements. But I think we're supercomputing is going in the moment. We're a very very disruptive moment again. That goes back to start this discussion. Why is extra skill been difficult to get? Thio? Actually, because the disruptive moment in technology. >>Professor Parsons, thank you very much for your time and your insights. Thank you. Pleasure and folks. Thank you for watching. I hope you've learned something, or at least enjoyed it. With that, I would ask you to stay safe and goodbye.

>> Sue: Hello everybody. Thank you for joining us today for the Virtual Vertica BDC 2020. Today's breakout session in entitled Extending Vertica with the Latest Vertica Ecosystem and Open Source Initiatives. My name is Sue LeClaire, Director of Marketing at Vertica and I'll be your host for this webinar. Joining me is Tom Wall, a member of the Vertica engineering team. But before we begin, I encourage you to submit questions or comments during the virtual session. You don't have to wait. Just type your question or comment in the question box below the slides and click submit. There will be a Q and A session at the end of the presentation. We'll answer as many questions as we're able to during that time. Any questions that we don't get to, we'll do our best to answer them offline. Alternatively, you can visit the Vertica forums to post you questions after the session. Our engineering team is planning to join the forums to keep the conversation going. Also a reminder that you can maximize your screen by clicking the double arrow button in the lower right corner of the slides. And yes, this virtual session is being recorded and will be available to view on demand later this week. We'll send you a notification as soon as it's ready. So let's get started. Tom, over to you. >> Tom: Hello everyone and thanks for joining us today for this talk. My name is Tom Wall and I am the leader of Vertica's ecosystem engineering team. We are the team that focuses on building out all the developer tools, third party integrations that enables the SoftMaker system that surrounds Vertica to thrive. So today, we'll be talking about some of our new open source initatives and how those can be really effective for you and make things easier for you to build and integrate Vertica with the rest of your technology stack. We've got several new libraries, integration projects and examples, all open source, to share, all being built out in the open on our GitHub page. Whether you use these open source projects or not, this is a very exciting new effort that will really help to grow the developer community and enable lots of exciting new use cases. So, every developer out there has probably had to deal with the problem like this. You have some business requirements, to maybe build some new Vertica-powered application. Maybe you have to build some new system to visualize some data that's that's managed by Vertica. The various circumstances, lots of choices will might be made for you that constrain your approach to solving a particular problem. These requirements can come from all different places. Maybe your solution has to work with a specific visualization tool, or web framework, because the business has already invested in the licensing and the tooling to use it. Maybe it has to be implemented in a specific programming language, since that's what all the developers on the team know how to write code with. While Vertica has many different integrations with lots of different programming language and systems, there's a lot of them out there, and we don't have integrations for all of them. So how do you make ends meet when you don't have all the tools you need? All you have to get creative, using tools like PyODBC, for example, to bridge between programming languages and frameworks to solve the problems you need to solve. Most languages do have an ODBC-based database interface. ODBC is our C-Library and most programming languages know how to call C code, somehow. So that's doable, but it often requires lots of configuration and troubleshooting to make all those moving parts work well together. So that's enough to get the job done but native integrations are usually a lot smoother and easier. So rather than, for example, in Python trying to fight with PyODBC, to configure things and get Unicode working, and to compile all the different pieces, the right way is to make it all work smoothly. It would be much better if you could just PIP install library and get to work. And with Vertica-Python, a new Python client library, you can actually do that. So that story, I assume, probably sounds pretty familiar to you. Sounds probably familiar to a lot of the audience here because we're all using Vertica. And our challenge, as Big Data practitioners is to make sense of all this stuff, despite those technical and non-technical hurdles. Vertica powers lots of different businesses and use cases across all kinds of different industries and verticals. While there's a lot different about us, we're all here together right now for this talk because we do have some things in common. We're all using Vertica, and we're probably also using Vertica with other systems and tools too, because it's important to use the right tool for the right job. That's a founding principle of Vertica and it's true today too. In this constantly changing technology landscape, we need lots of good tools and well established patterns, approaches, and advice on how to combine them so that we can be successful doing our jobs. Luckily for us, Vertica has been designed to be easy to build with and extended in this fashion. Databases as a whole had had this goal from the very beginning. They solve the hard problems of managing data so that you don't have to worry about it. Instead of worrying about those hard problems, you can focus on what matters most to you and your domain. So implementing that business logic, solving that problem, without having to worry about all of these intense, sometimes details about what it takes to manage a database at scale. With the declarative syntax of SQL, you tell Vertica what the answer is that you want. You don't tell Vertica how to get it. Vertica will figure out the right way to do it for you so that you don't have to worry about it. So this SQL abstraction is very nice because it's a well defined boundary where lots of developers know SQL, and it allows you to express what you need without having to worry about those details. So we can be the experts in data management while you worry about your problems. This goes beyond though, what's accessible through SQL to Vertica. We've got well defined extension and integration points across the product that allow you to customize this experience even further. So if you want to do things write your own SQL functions, or extend database softwares with UDXs, you can do so. If you have a custom data format that might be a proprietary format, or some source system that Vertica doesn't natively support, we have extension points that allow you to use those. To make it very easy to do passive, parallel, massive data movement, loading into Vertica but also to export Vertica to send data to other systems. And with these new features in time, we also could do the same kinds of things with Machine Learning models, importing and exporting to tools like TensorFlow. And it's these integration points that have enabled Vertica to build out this open architecture and a rich ecosystem of tools, both open source and closed source, of different varieties that solve all different problems that are common in this big data processing world. Whether it's open source, streaming systems like Kafka or Spark, or more traditional ETL tools on the loading side, but also, BI tools and visualizers and things like that to view and use the data that you keep in your database on the right side. And then of course, Vertica needs to be flexible enough to be able to run anywhere. So you can really take Vertica and use it the way you want it to solve the problems that you need to solve. So Vertica has always employed open standards, and integrated it with all kinds of different open source systems. What we're really excited to talk about now is that we are taking our new integration projects and making those open source too. In particular, we've got two new open source client libraries that allow you to build Vertica applications for Python and Go. These libraries act as a foundation for all kinds of interesting applications and tools. Upon those libraries, we've also built some integrations ourselves. And we're using these new libraries to power some new integrations with some third party products. Finally, we've got lots of new examples and reference implementations out on our GitHub page that can show you how to combine all these moving parts and exciting ways to solve new problems. And the code for all these things is available now on our GitHub page. And so you can use it however you like, and even help us make it better too. So the first such project that we have is called Vertica-Python. Vertica-Python began at our customer, Uber. And then in late 2018, we collaborated with them and we took it over and made Vertica-Python the first official open source client for Vertica You can use this to build your own Python applications, or you can use it via tools that were written in Python. Python has grown a lot in recent years and it's very common language to solve lots of different problems and use cases in the Big Data space from things like DevOps admission and Data Science or Machine Learning, or just homegrown applications. We use Python a lot internally for our own QA testing and automation needs. And with the Python 2 End Of Life, that happened at the end of 2019, it was important that we had a robust Python solution to help migrate our internal stuff off of Python 2. And also to provide a nice migration path for all of you our users that might be worried about the same problems with their own Python code. So Vertica-Python is used already for lots of different tools, including Vertica's admintools now starting with 9.3.1. It was also used by DataDog to build a Vertica-DataDog integration that allows you to monitor your Vertica infrastructure within DataDog. So here's a little example of how you might use the Python Client to do some some work. So here we open in connection, we run a query to find out what node we've connected to, and then we do a little DataLoad by running a COPY statement. And this is designed to have a familiar look and feel if you've ever used a Python Database Client before. So we implement the DB API 2.0 standard and it feels like a Python package. So that includes things like, it's part of the centralized package manager, so you can just PIP install this right now and go start using it. We also have our client for Go length. So this is called vertica-sql-go. And this is a very similar story, just in a different context or the different programming language. So vertica-sql-go, began as a collaboration with the Microsoft Focus SecOps Group who builds microfocus' security products some of which use vertica internally to provide some of those analytics. So you can use this to build your own apps in the Go programming language but you can also use it via tools that are written Go. So most notably, we have our Grafana integration, which we'll talk a little bit more about later, that leverages this new clients to provide Grafana visualizations for vertica data. And Go is another rising popularity programming language 'cause it offers an interesting balance of different programming design trade-offs. So it's got good performance, got a good current concurrency and memory safety. And we liked all those things and we're using it to power some internal monitoring stuff of our own. And here's an example of the code you can write with this client. So this is Go code that does a similar thing. It opens a connection, it runs a little test query, and then it iterates over those rows, processing them using Go data types. You get that native look and feel just like you do in Python, except this time in the Go language. And you can go get it the way you usually package things with Go by running that command there to acquire this package. And it's important to note here for the DC projects, we're really doing open source development. We're not just putting code out on our GitHub page. So if you go out there and look, you can see that you can ask questions, you can report bugs, you can submit poll requests yourselves and you can collaborate directly with our engineering team and the other vertica users out on our GitHub page. Because it's out on our GitHub page, it allows us to be a little bit faster with the way we ship and deliver functionality compared to the core vertica release cycle. So in 2019, for example, as we were building features to prepare for the Python 3 migration, we shipped 11 different releases with 40 customer reported issues, filed on GitHub. That was done over 78 different poll requests and with lots of community engagement as we do so. So lots of people are using this already, we see as our GitHub badge last showed with about 5000 downloads of this a day of people using it in their software. And again, we want to make this easy, not just to use but also to contribute and understand and collaborate with us. So all these projects are built using the Apache 2.0 license. The master branch is always available and stable with the latest creative functionality. And you can always build it and test it the way we do so that it's easy for you to understand how it works and to submit contributions or bug fixes or even features. It uses automated testing both for locally and with poll requests. And for vertica-python, it's fully automated with Travis CI. So we're really excited about doing this and we're really excited about where it can go in the future. 'Cause this offers some exciting opportunities for us to collaborate with you more directly than we have ever before. You can contribute improvements and help us guide the direction of these projects, but you can also work with each other to share knowledge and implementation details and various best practices. And so maybe you think, "Well, I don't use Python, "I don't use go so maybe it doesn't matter to me." But I would argue it really does matter. Because even if you don't use these tools and languages, there's lots of amazing vertica developers out there who do. And these clients do act as low level building blocks for all kinds of different interesting tools, both in these Python and Go worlds, but also well beyond that. Because these implementations and examples really generalize to lots of different use cases. And we're going to do a deeper dive now into some of these to understand exactly how that's the case and what you can do with these things. So let's take a deeper look at some of the details of what it takes to build one of these open source client libraries. So these database client interfaces, what are they exactly? Well, we all know SQL, but if you look at what SQL specifies, it really only talks about how to manipulate the data within the database. So once you're connected and in, you can run commands with SQL. But these database client interfaces address the rest of those needs. So what does the programmer need to do to actually process those SQL queries? So these interfaces are specific to a particular language or a technology stack. But the use cases and the architectures and design patterns are largely the same between different languages. They all have a need to do some networking and connect and authenticate and create a session. They all need to be able to run queries and load some data and deal with problems and errors. And then they also have a lot of metadata and Type Mapping because you want to use these clients the way you use those programming languages. Which might be different than the way that vertica's data types and vertica's semantics work. So some of this client interfaces are truly standards. And they are robust enough in terms of what they design and call for to support a truly pluggable driver model. Where you might write an application that codes directly against the standard interface, and you can then plug in a different database driver, like a JDBC driver, to have that application work with any database that has a JDBC driver. So most of these interfaces aren't as robust as a JDBC or ODBC but that's okay. 'Cause it's good as a standard is, every database is unique for a reason. And so you can't really expose all of those unique properties of a database through these standard interfaces. So vertica's unique in that it can scale to the petabytes and beyond. And you can run it anywhere in any environment, whether it's on-prem or on clouds. So surely there's something about vertica that's unique, and we want to be able to take advantage of that fact in our solutions. So even though these standards might not cover everything, there's often a need and common patterns that arise to solve these problems in similar ways. When there isn't enough of a standard to define those comments, semantics that different databases might have in common, what you often see is tools will invent plug in layers or glue code to compensate by defining application wide standard to cover some of these same semantics. Later on, we'll get into some of those details and show off what exactly that means. So if you connect to a vertica database, what's actually happening under the covers? You have an application, you have a need to run some queries, so what does that actually look like? Well, probably as you would imagine, your application is going to invoke some API calls and some client library or tool. This library takes those API calls and implements them, usually by issuing some networking protocol operations, communicating over the network to ask vertica to do the heavy lifting required for that particular API call. And so these API's usually do the same kinds of things although some of the details might differ between these different interfaces. But you do things like establish a connection, run a query, iterate over your rows, manage your transactions, that sort of thing. Here's an example from vertica-python, which just goes into some of the details of what actually happens during the Connect API call. And you can see all these details in our GitHub implementation of this. There's actually a lot of moving parts in what happens during a connection. So let's walk through some of that and see what actually goes on. I might have my API call like this where I say Connect and I give it a DNS name, which is my entire cluster. And I give you my connection details, my username and password. And I tell the Python Client to get me a session, give me a connection so I can start doing some work. Well, in order to implement this, what needs to happen? First, we need to do some TCP networking to establish our connection. So we need to understand what the request is, where you're going to connect to and why, by pressing the connection string. and vertica being a distributed system, we want to provide high availability, so we might need to do some DNS look-ups to resolve that DNS name which might be an entire cluster and not just a single machine. So that you don't have to change your connection string every time you add or remove nodes to the database. So we do some high availability and DNS lookup stuff. And then once we connect, we might do Load Balancing too, to balance the connections across the different initiator nodes in the cluster, or in a sub cluster, as needed. Once we land on the node we want to be at, we might do some TLS to secure our connections. And vertica supports the industry standard TLS protocols, so this looks pretty familiar for everyone who've used TLS anywhere before. So you're going to do a certificate exchange and the client might send the server certificate too, and then you going to verify that the server is who it says it is, so that you can know that you trust it. Once you've established that connection, and secured it, then you can start actually beginning to request a session within vertica. So you going to send over your user information like, "Here's my username, "here's the database I want to connect to." You might send some information about your application like a session label, so that you can differentiate on the database with monitoring queries, what the different connections are and what their purpose is. And then you might also send over some session settings to do things like auto commit, to change the state of your session for the duration of this connection. So that you don't have to remember to do that with every query that you have. Once you've asked vertica for a session, before vertica will give you one, it has to authenticate you. and vertica has lots of different authentication mechanisms. So there's a negotiation that happens there to decide how to authenticate you. Vertica decides based on who you are, where you're coming from on the network. And then you'll do an auth-specific exchange depending on what the auth mechanism calls for until you are authenticated. Finally, vertica trusts you and lets you in, so you going to establish a session in vertica, and you might do some note keeping on the client side just to know what happened. So you might log some information, you might record what the version of the database is, you might do some protocol feature negotiation. So if you connect to a version of the database that doesn't support all these protocols, you might decide to turn some functionality off and that sort of thing. But finally, after all that, you can return from this API call and then your connection is good to go. So that connection is just one example of many different APIs. And we're excited here because with vertica-python we're really opening up the vertica client wire protocol for the first time. And so if you're a low level vertica developer and you might have used Postgres before, you might know that some of vertica's client protocol is derived from Postgres. But they do differ in many significant ways. And this is the first time we've ever revealed those details about how it works and why. So not all Postgres protocol features work with vertica because vertica doesn't support all the features that Postgres does. Postgres, for example, has a large object interface that allows you to stream very wide data values over. Whereas vertica doesn't really have very wide data values, you have 30, you have long bar charts, but that's about as wide as you can get. Similarly, the vertica protocol supports lots of features not present in Postgres. So Load Balancing, for example, which we just went through an example of, Postgres is a single node system, it doesn't really make sense for Postgres to have Load Balancing. But Load Balancing is really important for vertica because it is a distributed system. Vertica-python serves as an open reference implementation of this protocol. With all kinds of new details and extension points that we haven't revealed before. So if you look at these boxes below, all these different things are new protocol features that we've implemented since August 2019, out in the open on our GitHub page for Python. Now, the vertica-sql-go implementation of these things is still in progress, but the core protocols are there for basic query operations. There's more to do there but we'll get there soon. So this is really cool 'cause not only do you have now a Python Client implementation, and you have a Go client implementation of this, but you can use this protocol reference to do lots of other things, too. The obvious thing you could do is build more clients for other languages. So if you have a need for a client in some other language that are vertica doesn't support yet, now you have everything available to solve that problem and to go about doing so if you need to. But beyond clients, it's also used for other things. So you might use it for mocking and testing things. So rather than connecting to a real vertica database, you can simulate some of that. You can also use it to do things like query routing and proxies. So Uber, for example, this log here in this link tells a great story of how they route different queries to different vertical clusters by intercepting these protocol messages, parsing the queries in them and deciding which clusters to send them to. So a lot of these things are just ideas today, but now that you have the source code, there's no limit in sight to what you can do with this thing. And so we're very interested in hearing your ideas and requests and we're happy to offer advice and collaborate on building some of these things together. So let's take a look now at some of the things we've already built that do these things. So here's a picture of vertica's Grafana connector with some data powered from an example that we have in this blog link here. So this has an internet of things use case to it, where we have lots of different sensors recording flight data, feeding into Kafka which then gets loaded into vertica. And then finally, it gets visualized nicely here with Grafana. And Grafana's visualizations make it really easy to analyze the data with your eyes and see when something something happens. So in these highlighted sections here, you notice a drop in some of the activity, that's probably a problem worth looking into. It might be a lot harder to see that just by staring at a large table yourself. So how does a picture like that get generated with a tool like Grafana? Well, Grafana specializes in visualizing time series data. And time can be really tricky for computers to do correctly. You got time zones, daylight savings, leap seconds, negative infinity timestamps, please don't ever use those. In every system, if it wasn't hard enough, just with those problems, what makes it harder is that every system does it slightly differently. So if you're querying some time data, how do we deal with these semantic differences as we cross these domain boundaries from Vertica to Grafana's back end architecture, which is implemented in Go on it's front end, which is implemented with JavaScript? Well, you read this from bottom up in terms of the processing. First, you select the timestamp and Vertica is timestamp has to be converted to a Go time object. And we have to reconcile the differences that there might be as we translate it. So Go time has a different time zone specifier format, and it also supports nanosecond precision, while Vertica only supports microsecond precision. So that's not too big of a deal when you're querying data because you just see some extra zeros, not fractional seconds. But on the way in, if we're loading data, we have to find a way to resolve those things. Once it's into the Go process, it has to be converted further to render in the JavaScript UI. So that there, the Go time object has to be converted to a JavaScript Angular JS Date object. And there too, we have to reconcile those differences. So a lot of these differences might just be presentation, and not so much the actual data changing, but you might want to choose to render the date into a more human readable format, like we've done in this example here. Here's another picture. This is another picture of some time series data, and this one shows you can actually write your own queries with Grafana to provide answers. So if you look closely here you can see there's actually some functions that might not look too familiar with you if you know vertica's functions. Vertica doesn't have a dollar underscore underscore time function or a time filter function. So what's actually happening there? How does this actually provide an answer if it's not really real vertica syntax? Well, it's not sufficient to just know how to manipulate data, it's also really important that you know how to operate with metadata. So information about how the data works in the data source, Vertica in this case. So Grafana needs to know how time works in detail for each data source beyond doing that basic I/O that we just saw in the previous example. So it needs to know, how do you connect to the data source to get some time data? How do you know what time data types and functions there are and how they behave? How do you generate a query that references a time literal? And finally, once you've figured out how to do all that, how do you find the time in the database? How do you do know which tables have time columns and then they might be worth rendering in this kind of UI. So Go's database standard doesn't actually really offer many metadata interfaces. Nevertheless, Grafana needs to know those answers. And so it has its own plugin layer that provides a standardizing layer whereby every data source can implement hints and metadata customization needed to have an extensible data source back end. So we have another open source project, the Vertica-Grafana data source, which is a plugin that uses Grafana's extension points with JavaScript and the front end plugins and also with Go in the back end plugins to provide vertica connectivity inside Grafana. So the way this works, is that the plugin frameworks defines those standardizing functions like time and time filter, and it's our plugin that's going to rewrite them in terms of vertica syntax. So in this example, time gets rewritten to a vertica cast. And time filter becomes a BETWEEN predicate. So that's one example of how you can use Grafana, but also how you might build any arbitrary visualization tool that works with data in Vertica. So let's now look at some other examples and reference architectures that we have out in our GitHub page. For some advanced integrations, there's clearly a need to go beyond these standards. So SQL and these surrounding standards, like JDBC, and ODBC, were really critical in the early days of Vertica, because they really enabled a lot of generic database tools. And those will always continue to play a really important role, but the Big Data technology space moves a lot faster than these old database data can keep up with. So there's all kinds of new advanced analytics and query pushdown logic that were never possible 10 or 20 years ago, that Vertica can do natively. There's also all kinds of data-oriented application workflows doing things like streaming data, or Parallel Loading or Machine Learning. And all of these things, we need to build software with, but we don't really have standards to go by. So what do we do there? Well, open source implementations make for easier integrations, and applications all over the place. So even if you're not using Grafana for example, other tools have similar challenges that you need to overcome. And it helps to have an example there to show you how to do it. Take Machine Learning, for example. There's been many excellent Machine Learning tools that have arisen over the years to make data science and the task of Machine Learning lot easier. And a lot of those have basic database connectivity, but they generally only treat the database as a source of data. So they do lots of data I/O to extract data from a database like Vertica for processing in some other engine. We all know that's not the most efficient way to do it. It's much better if you can leverage Vertica scale and bring the processing to the data. So a lot of these tools don't take full advantage of Vertica because there's not really a uniform way to go do so with these standards. So instead, we have a project called vertica-ml-python. And this serves as a reference architecture of how you can do scalable machine learning with Vertica. So this project establishes a familiar machine learning workflow that scales with vertica. So it feels similar to like a scickit-learn project except all the processing and aggregation and heavy lifting and data processing happens in vertica. So this makes for a much more lightweight, scalable approach than you might otherwise be used to. So with vertica-ml-python, you can probably use this yourself. But you could also see how it works. So if it doesn't meet all your needs, you could still see the code and customize it to build your own approach. We've also got lots of examples of our UDX framework. And so this is an older GitHub project. We've actually had this for a couple of years, but it is really useful and important so I wanted to plug it here. With our User Defined eXtensions framework or UDXs, this allows you to extend the operators that vertica executes when it does a database load or a database query. So with UDXs, you can write your own domain logic in a C++, Java or Python or R. And you can call them within the context of a SQL query. And vertica brings your logic to that data, and makes it fast and scalable and fault tolerant and correct for you. So you don't have to worry about all those hard problems. So our UDX examples, demonstrate how you can use our SDK to solve interesting problems. And some of these examples might be complete, total usable packages or libraries. So for example, we have a curl source that allows you to extract data from any curlable endpoint and load into vertica. We've got things like an ODBC connector that allows you to access data in an external database via an ODBC driver within the context of a vertica query, all kinds of parsers and string processors and things like that. We also have more exciting and interesting things where you might not really think of vertica being able to do that, like a heat map generator, which takes some XY coordinates and renders it on top of an image to show you the hotspots in it. So the image on the right was actually generated from one of our intern gaming sessions a few years back. So all these things are great examples that show you not just how you can solve problems, but also how you can use this SDK to solve neat things that maybe no one else has to solve, or maybe that are unique to your business and your needs. Another exciting benefit is with testing. So the test automation strategy that we have in vertica-python these clients, really generalizes well beyond the needs of a database client. Anyone that's ever built a vertica integration or an application, probably has a need to write some integration tests. And that could be hard to do with all the moving parts, in the big data solution. But with our code being open source, you can see in vertica-python, in particular, how we've structured our tests to facilitate smooth testing that's fast, deterministic and easy to use. So we've automated the download process, the installation deployment process, of a Vertica Community Edition. And with a single click, you can run through the tests locally and part of the PR workflow via Travis CI. We also do this for multiple different python environments. So for all python versions from 2.7 up to 3.8 for different Python interpreters, and for different Linux distros, we're running through all of them very quickly with ease, thanks to all this automation. So today, you can see how we do it in vertica-python, in the future, we might want to spin that out into its own stand-alone testbed starter projects so that if you're starting any new vertica integration, this might be a good starting point for you to get going quickly. So that brings us to some of the future work we want to do here in the open source space . Well, there's a lot of it. So in terms of the the client stuff, for Python, we are marching towards our 1.0 release, which is when we aim to be protocol complete to support all of vertica's unique protocols, including COPY LOCAL and some new protocols invented to support complex types, which is our new feature in vertica 10. We have some cursor enhancements to do things like better streaming and improved performance. Beyond that we want to take it where you want to bring it. So send us your requests in the Go client fronts, just about a year behind Python in terms of its protocol implementation, but the basic operations are there. But we still have more work to do to implement things like load balancing, some of the advanced auths and other things. But they're two, we want to work with you and we want to focus on what's important to you so that we can continue to grow and be more useful and more powerful over time. Finally, this question of, "Well, what about beyond database clients? "What else might we want to do with open source?" If you're building a very deep or a robust vertica integration, you probably need to do a lot more exciting things than just run SQL queries and process the answers. Especially if you're an OEM or you're a vendor that resells vertica packaged as a black box piece of a larger solution, you might to have managed the whole operational lifecycle of vertica. There's even fewer standards for doing all these different things compared to the SQL clients. So we started with the SQL clients 'cause that's a well established pattern, there's lots of downstream work that that can enable. But there's also clearly a need for lots of other open source protocols, architectures and examples to show you how to do these things and do have real standards. So we talked a little bit about how you could do UDXs or testing or Machine Learning, but there's all sorts of other use cases too. That's why we're excited to announce here our awesome vertica, which is a new collection of open source resources available on our GitHub page. So if you haven't heard of this awesome manifesto before, I highly recommend you check out this GitHub page on the right. We're not unique here but there's lots of awesome projects for all kinds of different tools and systems out there. And it's a great way to establish a community and share different resources, whether they're open source projects, blogs, examples, references, community resources, and all that. And this tool is an open source project. So it's an open source wiki. And you can contribute to it by submitting yourself to PR. So we've seeded it with some of our favorite tools and projects out there but there's plenty more out there and we hope to see more grow over time. So definitely check this out and help us make it better. So with that, I'm going to wrap up. I wanted to thank you all. Special thanks to Siting Ren and Roger Huebner, who are the project leads for the Python and Go clients respectively. And also, thanks to all the customers out there who've already been contributing stuff. This has already been going on for a long time and we hope to keep it going and keep it growing with your help. So if you want to talk to us, you can find us at this email address here. But of course, you can also find us on the Vertica forums, or you could talk to us on GitHub too. And there you can find links to all the different projects I talked about today. And so with that, I think we're going to wrap up and now we're going to hand it off for some Q&A.

>> Announcer: From theCUBE studios in Palo Alto and Boston, connecting with thought leaders all around the world, this is a CUBE Conversation. >> Hi, everybody, welcome back to theCUBE's coverage of the Virtual Vertica BDC, Big Data Conference. It was, of course, going to be in Boston, but now we're covering it online. It's really our pleasure to invite back Joy King, she's the vice president of product and go-to-market strategy at Vertica. She also manages marketing and education programs. Joy, great to see you. >> It's great to be back, as always, Dave, thank you. >> Let's talk about BDC, Virtual BDC. We took a break. theCUBE has been at every Big Data Conference. I love that show, great customers, awesome buzz, great outside speakers. I actually had the pleasure of being up on stage with some database experts, of which I'm not, but I'm a (laughs) inch deep and a mile wide. >> I remember that! (laughs) >> And it was a lot of fun going head to head with some of the folks, and just really a great vibe over that conference. But, so, now, you had to make the decision, because of the coronavirus, to go digital. You didn't delay, and I love the fact that you guys leaned right in, you've got all this content. So talk about what we can expect at BDC. >> Well, you know, Dave, the BDC is really special, and I have to give Colin Mahoney, our GM, the credit for the idea. Sometimes his ideas are really good, and the execution can be, well, challenging. But when we started the BDC, he had an idea. He said, "You know, we have such a passionate "community, we need to get them together. "We need, like, a user group." Well, that user group, for the first BDC, was the first and only event I have ever been responsible for where, yes, it's true, we exceeded the fire code of the venue, and we had more people that registered than we were allowed to accept. That's never happened before. It's because the passion was so real. We made a commitment. We said the only people that could speak at the BDC were engineers who architected and write the code, and customers who've used the code. We were determined to keep the technical credibility, the value of best practices, the sharing among the community. Marketing was responsible for appropriate amounts of coffee and alcohol at the appropriate times, (Dave laughs) but today, that is still why the BDC is so special. Now, I have to tell you, we have been somewhat limited in our ability to confirm coffee, alcohol, et cetera in the Virtual BDC, but we are still true to our mission. The people that will be speaking during the sessions that we have, and for all of the recordings that we will do in addition after we complete the live BDC, are engineers and architects who design and write the code, hands on the keyboard, and customers who use Vertica to power their businesses every day. That's the rule. Some people don't like it, but that's how we play. >> Well, and to your point, and we've interviewed a number of your customers, and I can second that. The database engineers are proud to put Vertica in their title. >> Yes. >> They embrace it, they love to train people and get adoption going, so that's awesome. Let's talk about some of the logistics of the BDC, the Virtual BDC. Tuesday, March 31st, and then the next day, April 1st, you've got keynotes, you've got breakouts, and of course, we've got theCUBE. After the keynotes, we'll be doing CUBE coverage for two days, wall-to-wall coverage of Virtual BDC. And to your point, and I think this is a nuance that I think people are going to learn with digital, is there's a post-event that really is going to continue that engagement with your community. >> That's right. As much as everybody knows there's nothing that replaces face-to-face interaction, there are advantages to the virtual world. First of all, people are getting pretty creative, I've got to say, and second, it gives global reach to people who would have loved to come to the BDC but couldn't. They couldn't travel, there were restrictions, they were busy with other things. So, yes, all day Tuesday and all day Wednesday. After the keynote on Tuesday will be two parallel tracks, and this is East Coast time, from U.S. East Coast time, on Tuesday afternoon, and then two parallel tracks all day Wednesday. And then on Thursday, in addition to all of those webinars, all of those sessions being available on demand, we are also, right now, recording additional sessions because we just didn't have enough slots, but we had more speakers, both customers and engineers, that wanted to, and all of that will be available on the BDC website on Thursday and beyond. And we're going to continue with two webinar series that we're very proud of. One is called "Under the Hood," which is technical webinars, and the other is called "Data Disruptors," and those are the customers that love to tell their stories. And that, in parallel with ongoing CUBE interviews, will keep the energy all the way up until late March of 2021, when we have already confirmed the next live BDC. >> Awesome, so go to vertica.com/bdc2020, register, you got to register, to see the keynotes. It's lightweight registration, it's not a hundred fields, we want you to come in. And then, of course, theCUBE.net is going to be covering, theCUBE interviews, and SiliconANGLE.com will have editorial. Joy, looking forward to it. Thanks so much for giving us the update, and we'll see you online. >> It will be a pleasure, see ya, bye. >> And we'll see you. Thank you, everybody, and go, like I said, go register, again, it's vertica.com/bdc2020. This is Dave Vellante from theCUBE, and we'll see you at the Virtual Vertica Big Data Conference. (upbeat music)

>> Live from Las Vegas. It's the queue covering del Technologies. World twenty nineteen. Brought to you by Del Technologies and its ecosystem partners. >> Good morning. Welcome to the Cubes coverage. Day three. Odell Technologies, World from Las Vegas. Lisa Martin With student Amanda We're pleased to welcome one of our alumni back to the key. We've got Jay Snyder with us SPP of global alliances, service providers and industries chaebol. Thank >> you so much for having me again. >> Our pleasure. So we have been talking for This is our third day of covering the lots of news, lots of technology conversations We know there's a big global Cartner summit. >> It's been fantastic, actually. >> Abd el Technologies World Thriving partner ecosystem Give us an overview of global alliances and some of the feedback from the last few days of the partners. So >> fantastic. Thank you again for having me. I'll tell you this. The feedback is off the chart eye. Don't even I've lost the ability to find new words to describe how excited are partners seem to be with the messaging that we've had here. But what's been consistent is best l technologies world ever and best global partners. Summer that we've ever had and I think the reason behind that is not just because we've done a great job presenting the content. It's because of the content, right. If you think about the partner ecosystem, it's interesting. We've always worked incredibly well with them and our partners love what we do in the products we make. But our messages have never been perfectly aligned. Think about the messages we have now on the main stage. We have four transformations and delivering outcomes and then we have multi cloud and the multi cloud strategy and then think about what the partners do. They deliver the strategy around designing and defining what a multi cloud architecture is going to look like and or being the providers that actually deliver it. Our messages are perfectly aligned, so they're so excited to see that there now at the epicenter of everything that we go and do, and the fact that I would say probably more exciting is our entire sales force is trained on those messages, understanding those messages and embracing those messages. So they're getting huge lift now from our cellars, as opposed to kind of. I wouldn't say we were never at conflict. But we're Maurin Parallel. And now we're really lock. Step. Well, does that make sense? >> It does, Jay. And and he brought up a really good point, you know? Congratulations. Glad to hear everybody's in lock step. Because I remember we talked about the transformation of the channel. Yeah, and I go back when converge infrastructure first rolled out. They're people. Oh, my gosh. I make millions of dollars racking it, Stacking, shoveling stuff. I need to shift Cloud that there was, you know, at VM wears partner Summit, you know, one of the executive V M. Where you know, every time Amazon winds, you know, we all lose. Sure. So helped us for today. You know, cloud big theme of the message. How Teo his partners fit into those environments. And how have they gotten to over the fear of cloud and to be fully embracing in executing a multi cloud? >> Maybe I should just context to about who my partners are, so that would be helpful. So we representing alliance is the largest global systems integrators. So think about firms like in HCL, Deloitte dating, censure. And I hate to leave anybody out, but there's eighteen of them. And then we represent the clouds of the cloud service provider ecosystem. So a couple of hundred cloud providers that actually do provide manage private clouds off from or public clouds. So they're super excited about the message because they fit in on both ends, right, As I was just describing right there, the ones that are really gonna have to deliver the strategy around what it's going to look like and how they're going to get their customers ask us all the time. Hey, I want to get to the cloud, but they don't really know what it means. So we have to ask them, What do you really trying to accomplish and why? Right, Once we understand that we can engage with these partners, and it's a perfect entree for them to go figure out, articulating design that architecture. And then last time I checked, we're actually not a cloud company, right? We have great products. We have great services. We've rate platforms, but we're not a cloud company, right? We don't provide those types of capabilities. So when you think about being able to leverage >> multi cloud and it started just clever, you're saying you're not a public cloud company because company Private Cloud absolutely se Eun apart >> from Private Cloud, right? But when we want to go off from and create that multi claude environment based on use case now all those partners fit into that play and they have the ability through the capabilities we just announced with Del Technologies clown tow leverage, those hyper scale er's. So where they used to see them as foe. They're now part of the solution, and they can deliver that solution through our new platform that we just brought to market. So again it gets back to we used to fight it. Now we're embracing it and leveraging it and delivered a comprehensive solution. >> So starting Monday, when Michael walked out on stage your hat with Jeff, the message over lying on, of course, with salt from Microsoft was collaboration integration. So really starting to see all the layers of Del technologies and its brands come together in a much more cohesive way than we've seen so far in terms of what the partners are now enabled to deliver. Some of the feedback on that is, do they feel that it's been made more simplified that has been made more streamlined, that it's opening up new market opportunities with, you know, the Del Technologies Cloud and some of the related announcements. >> So So it's a complicated question you're actually asking, because for years the partners have been saying We'd love to view you as a single company, right? That's kind of the missing ingredient to really a lot unlock the full potential. I think the first big piece big mover in this is the Del Technology Cloud platform. It's really the end, Stan, she ation of what Michael's been talking about for the last three years, which is I'm going to bring all this stuff together and create a force in the industry where we compete in the market together, not against one another. So we're seeing that so the partners are ecstatic right there, seeing the best of all the piece parts come together in that platform, and we've told him that's the first step. But we have been working with them for years to provide what I'LL call an umbrella effect across all the different companies to allow them to tap into all those resource is. So in some degree, we've been doing it already. We've been playing that multi cloud game and working cross strategically aligned business to bring those values to life. But now we put our money where our mouth is, and we have simplified the approach with the product and the platform to make it easier for them to go tomorrow. Way to have a little bit. We do have a little bit a ways to go, though. I want to be clear. >> So, yeah, and Jay really good points there because I I one article recently about hybrid cloud cut a lot of history with it and simplifying a piece of the overall puzzle. But as you said, those hyper scales fit into it. Sergeant Dellape, upstate eight of us, a strong partner on VM where you know, Google announcement. You know, just a few weeks ago, those s eyes that air your partner's There are some of the critical pieces because there's a lot of complexity out there and we need key partners to be a help us to do there. You know, the Del of Technology family is a piece of it, but those s eyes air really thie arms and legs that are going to go help all of the customers understand. Try to get their arms around and, you know, hopefully simplify. And what what I said is they need to turn from a bunch of point pieces in the new overall solution. They do that, help me drive innovation and drive by. Visit forward, not trying to manage all of the pieces >> We had talked about it yesterday. I mean, I D c. Says that sixty two percent of customers will have a multi cloud architecture. But for my partner Rico system, it's more interesting. You know that seventy percent of the customers are going to choose a provider to design, architect and manage that infrastructure. So if you think about that seven ten, customers will use one of those global systems integrators and or cloud service writers or, more likely both to deliver on their vision and their outcomes that they need to achieve to change their business models, which is again great for our business. >> How influential are your is your partner ecosystem in terms of some of the announces that we've heard this week? They're out feet on the street there, talking with customers about the challenges that they're having emerging trends. A. M L. What's that sort of center? Just a partner. Feedback loop like that helps Del Technologies, right thruster >> way Run partner advisory boards in each major theater multiple times a year, and these are the exact things we ask them. What tribe trends are you seeing? We map it against our product portfolio in our solutions to identify where there's gaps. Five g's a great example, right? We're looking at where the market's going happen. Have responsibility for a big chunk of our telco vertical as well within the company. So it's a hot topic and, you know, for a while we were. We were honestly lagging in this particular space. If I think back two years ago, we talked Telco, but we didn't walk Telco. We've made a lot of investments over the last two years to build a product business unit specifically around Telco solutions, and I'm proud to say, especially coming out of Mobile World Congress this year that we have arrived. We have incredible products solutions that really are exactly what are partners are looking for and our end user customers looking for. And it's an interesting dynamic because a lot of our partners, our customers. If you think about the telco community that's really gonna embrace and drive five G, we both sell to them and we sell through them. So we love the fact they'LL consume our underlying technology. But more importantly, I love the fact that we can use them as a route to market to expose hundreds thousands of customers to those capabilities in the broader scale. >> Yeah, J that the networking is such a critical component of that service fighter piece. So how much of that solution that you're talking about? Polls in some of the aspects from GM wear, you know, NSX, the SD win. Those pieces seem natural fit to help drive that overall solution. >> Yeah, I would actually tell you that my opinion is probably the first products that we brought to market that were really crossed Company cross collaboration. You know, even before we got to the Del Technologies cloud were exactly what you're talking about. Some of those networking asked it some security assets that vm where has integrated with some of our products server technology to build some integrated telco specific things for the core and the edge, which is really where they're operating specifically around the edge. Fellow cloud is going to be a huge piece of that SD. When we see the telcos, has a huge route to market again for that particular product and as a massive consumer of that particular product, we understand they have to cannibalize some of their own business. But it's the way the markets going. So the answer is yes. We're seeing great integration, great collaboration between our product business unit under cabin, Kevin Shots Camera in Telco and his V M or counterparts. And I think I said his name right there, too. >> Yeah, I had to interview him once, and absolutely nothing I'm getting that right was tough. You know, one of things always at the show is just the feedback that you get from from customers and from from your partners. So gives the mood, you know, Where are they? What are some of, you know, key opportunities, challenges? What? What's top of mind issues for? >> I'm telling you like I can't make this up. The mood is off the chart, right? They've said consistently best sessions ever. I was talking to one particular partner last night. I won't say his name, but he's worked in this industry for thirty years. He's worked for major companies ASAP. Adobe, Microsoft. This is his first time Adele Technologies world working as a partner of ours, he said. Hands down. This is the best partner driven partner content partner event I've ever seen in the industry. So excited about the focus Del Technologies has as a company on our ecosystem and the types of conversations we're having to actually not just sell to us, but sell through us, right? We're really, I think we've really worked hard to view our partners not as customers, but truly as partners. It's all about the business. We build together, not about the business we do together. If that makes sense, right >> well, that trust trusting relationship is absolutely table stakes. It is for an organization. It sounds like you guys have really done a tremendous amount of work in the last few years to get that to the highest level that it's ever been on. >> I would agree. I think we've come a long way from where we were. We have a lot more work to do it .'LL never end, but I'm super excited with what achieved. I think our partners are, too, because the results they're getting are fantastic. I talked about the profitability of our business and their business together, which means what we're selling has value, which is fantastic as well. So it's good to know that we're not just winning in the market, but we're winning with high value, and again it gets back to where this conversation started, which is everyone talking about transformation and outcomes. It's hard to deliver value if you're not delivering an outcome or vice versa, right >> J. One of the areas that I I think your partner's and the solutions that your help bringing to market what would have some good opinion on is this move from kind of the Catholics, the optics model, you know, one of things. We look at the cloud announcements and it's like, Okay, wait, which of these air as a service? Which one of these he's, you know, can I do financing on and which one of these you know are mostly built on hardware? We're just that fit in the overall discussion, and it's what what do you get feedback from your partners and to cultivate that >> users? It's literally in every single conversation we have. So I can't think of a particular partner conversation that doesn't send around a variety of things. One is always our technology. One is our go to market engine and how we can leverage that and the other is commercials. And it's not the price. It's the consumption, right? How are we going to consume your technology, CAF, ex office and everything in between? And that everything in between used to be one or two things. Now it's ten or fifteen things right. The models have got very complex and very dynamic, so it's top of mind. And the beautiful thing is, you know, a few years ago the only way to get a consumption model on as a service model. It was through my partner Rico system. Now Dell's done a good job to catch up to some degree. But to truly deliver what a lot of the customers air accident for, which is pure op X, no caf X pays you grow. Models were still leveraging heavily our partner ecosystem to Babel. Deliver that, and the challenge for us is to be able to keep up with them, right? They're moving at such a rapid pace and the dynamics of those models Archangel. We have to evolve too quickly to be able to offer what our competitors aire doing. I'm excited to say, so far, so good, but we're doing a great job of that. But I would I would agree with you, right? The commercial model, The consumption models are top of mind, and every conversation had to today right on how we're going to structure these things. And it's really exciting, right? Because when we do it right, it tends to be not only great for Dell and great for the partner, but great for the customer. So it really is. It's the classic win win win. >> Are you know, one of the things that it seems that Dell has been technologies working to Dio for awhile now has become this sort of one stop shop for all things partners. Are they looking to have that single trusted source Do they appreciate now that they've got that, that they can really go today l technologies and enable their customers and your customers to transform security work for us? We heard a lot about work first. Urination, >> very common, >> are they now seeing Dallas? This Hey, this is this really a one stop shop. We can actually deliver everything that our customers are looking for. >> They're definitely seeing because we're telling it to him all the time, right? But yes, the answers without question, I think one of the big drivers for our business has been the ability to aggregate the breath of Del Technologies and bring the full portfolio to beer to them. I'd love to see them all standardised on us exclusively. That's my job, right? That's what we do. We try to eliminate white space and own all marketshare. We'LL never get there one hundred percent. But we've seen, you know, we look out of right of metrics in our business. We look at revenue, growth, probability, growth way. Also, look at white space, which is what you're talking about. Have we consume the white space where competitors used to be with inside our partners, and we've seen massive growth there in the last two years significant growth across the board. And the reason is because of what you just described. We now have an economies of scale advantage in a breath of portfolio advantage where it just makes sense for them to bet on us to get what they need, right, whether it's a pivotal capability or of'em were capability or Bhumi capability. When we have that, everybody pointed in the same direction. This story is just so much more powerful and there, and I'm not going to say they're buying it. They're believing it and they're seeing it in the field. So again, I talked about it earlier. If weaken transact at that level at Adele Technologies level, it means more value to our partners. But ultimately they can provide more value to their customers. So they're more profitable or customers get better solutions. So yes, yes, and yes, >> everybody went well. Jay, thank you so much for joining student May assuring the tremendous momentum that you guys have achieved. We look forward to hearing next year. >> I do to >> even better news will be Thanks. Thank you again for joining us. >> Thanks for having me. >> Great to meet you. Thanks, Tio for student a man. I'm Lisa Martin. You're watching us on the Cube. Live from jail technology World twenty nineteen day three of the cubes to set coverage continues after this

>> Announcer: Live from Orlando, Florida, it's theCUBE, covering .conf2018. Brought to you by Splunk. >> Welcome back to .conf2018 everybody, this is theCUBE the leader in live tech coverage. I'm Dave Vellante with Stu Miniman, wrapping up day one and we're pleased to have Bina Khimani, who's the global head of Partner Ecosystem for the infrastructure segments at AWS. Bina, it's great to see you, thanks for coming on theCUBE. >> Thank you for having me. >> You're very welcome. >> Pleasure to be here. >> It's an awesome show, everybody's talking data, we love data. >> Yes. >> You guys, you know, you're the heart of data and transformation. Talk about your role, what does it mean to be the global head Partner Ecosystems infrastructure segments, a lot going on in your title. >> Yes. >> Dave: You're busy. (laughing) >> So, in the infrastructure segment, we cover dev apps, security, networking as well as cloud migration programs, different types of cloud migration programs, and we got segment leaders who really own the strategy and figure out where are the best opportunities for us to work with the partners as well as partner development managers and solution architects who drive adoption of the strategy. That's the team we have for this segment. >> So everybody wants to work with AWS, with maybe one or two exceptions. And so Splunk, obviously, you guys have gotten together and formed an alliance. I think AWS has blessed a lot of the Splunk technology, vice versa. What's the partnership like, how has it evolved? >> So Splunk has been an excellent partner. We are really joined hands together in many fronts. They are fantastic AWS marketplace partner. We have many integrations of Splunk and AWS services, whether it is Kinesis data, Firehose, or Macy, or WAF. So many services Splunk and AWS really are well integrated together. They work together. In addition, we have joined go to market programs. We have field engagement, we have remand generation campaigns. We join hands together to make sure that our customers, joint customers, are really getting the best value out of it. So speaking of partnership, we recently launched migration program for getting Splunk on prem, Splunk Enterprise customers to Splunk Cloud while, you know, they are on their journey to Cloud anyway. >> Yeah, Bina let's dig into that some, we know AWS loves talking about migrations, we dig into all the databases that are going and we talk at this conference, you know Splunk started out very much on premises but we've talked to lots of users that are using the Cloud and it's always that right. How much do they migrate, how much do they start there? Bring us instead, you know, what led to this and what are the workings of it. >> So what, you know if you look at the common problems people have customers have on prem, they are same problems that customers have with Splunk Enterprise on prem, which is, you know, they are looking for resiliency. Their administrator goes on vacation. They want to keep it up and running all the time. They help people making some changes that shouldn't have been made. They want the experts to run their infrastructure. So Splunk Cloud is run by Splunk which is, you know they are the best at running that. Also, you know I just heard a term called lottery proof. So Splunk Cloud is lottery proof, what that means the funny thing is, that you know, your administrator wins lottery, you're not out of business. (laughs) At the same time if you look at the the time to value. I was talking to a customer last night over dinner and they were saying that if they wanted to get on Splunk Enterprise, for their volume of data that they needed to be ingested in Splunk, it would take them six months to just get the hardware in place. With Splunk Cloud they were running in 15 minutes. So, just the time to value is very important. Other things, you know, you don't need to plan for your peak performance. You can stretch it, you can get all the advantages of scalability, flexibility, security, everything you need. As well as running Splunk Cloud you know you are truly cost optimized. Also Splunk Cloud is built for AWS so it's really cost optimized in terms of infrastructure costs, as well as the Splunk licensing cost. >> Yeah it's funny you mentioned the joke, you know you go to Splunk cloud you're not out of a job, I mean what we've heard, the Splunk admins are in such high demand. Kind of running their instances probably isn't, you know a major thing that they'd want to be worrying about. >> Yes, yes, so-- >> Dave: Oh please, go. >> So Splunk administrators are in such a high demand and because of that, you know, not only that customers are struggling with having the right administrators in place, also retaining them. And when they go to Cloud, you know, this is a SAS version, they don't need administrators, nor they need hardware. They can just trust the experts who are really good at doing that. >> So migrations are a tricky thing and I wonder if we can get some examples because it's like moving a house. You don't want to move, or you actually do want to move but it's, you have be planful, it's a bit of a pain, but the benefits, a new life, so. In your world, you got to be better, so the world that you just described of elastic, you don't have to plan for peaks, or performance, the cost, capex, the opex, all that stuff. It's 10 X better, no debate there. But still there's a barrier that you have to go through. So, how does AWS make it easier or maybe you could give us some examples of successful migrations and the business impact that you saw. >> Definitely. So like you said, right, migration is a journey. And it's not always easy one. So I'll talk about different kinds of migration but let me talk about Splunk migration first. So Splunk migration unlike many other migration is actually fairly easy because the Splunk data is transient data, so customers can just point all their data sources to Splunk Cloud instead of Splunk Enterprise and it will start pumping data into Splunk Cloud which is productive from day one. Now if some customers want to retain 60 to 90 days data, then they can run this Splunk Enterprise on prem for 60 more days. And then they can move on to Splunk Cloud. So in this case there was no actual data migration involved. And because this is the log data that people want to see only for 60 to 90 days and then it's not valuable anymore. They don't really need to do large migration in this case it's practically just configure your data sources and you are done. That's the simplest part of the migration which is Splunk migration to Splunk Cloud. Let's talk about different migrations. So... you have heard many customers, you know like Capital One or many other Dow-Jones, they are saying that we are going all in on AWS and they are shutting down their data centers, they are, you know, migrating hundreds of thousands of applications and servers, which is not as simple as Splunk Cloud, right? So, what AWS, you know, AWS does this day in and day out. So we have figured it out again and again and again. In all of our customer interactions and migrations we are acquiring ton of knowledge that we are building toward our migration programs. We want to make sure that our customers are not reinventing the wheel every time. So we have migration programs like migration acceleration program which is for custom large scale migrations for larger customers. We have partner migration programs which is entirely focused on working with SI partners, consulting partners to lead the migrations. As well as we're workload migration program where we are standardizing migrations of standard applications like Splunk or Atlassian, or many of their such standard applications, how we can provide kind of easy button to migrate. Now, when customers are going through this migration journey, you know, it's going to be 10 X better like you said, but initially there is a hump. They are probably needing to run two parallel environments, there is a cost element to that. They are also optimizing their business processes there is some delay there. They are doing some technical work, you know, discovery, prioritization, landing zone creations, security, and networking aspects. There are many elements to this. What we try to do is, if you look at the graph, their cost is right now where this and it's going to go down but before that it goes up and then goes down. So what we try to do is really provide all the resources to take that hump out in terms of technical support, technical enablement, you know, partner support, funding elements, marketing. There are all types of elements as well as lot of technical integrations and quick starts to take that hump out and make it really easy for our customers. >> And that was our experience, we're Amazon customer and we went through a migration about, I don't know five or six years ago. We had, you know, server axe and a cage and we were like, you know, moving wires over and you'd get an alert you'd have to go down and fix things. And so it took us some time to get there, but it is 10 X better now though. >> It is. >> The developers were so excited and I wanted to ask you about, sort of the dev-ops piece of it because that's really, it became, we just completely eliminated all the operational pieces of it and integrated it and let the developers take care of it. Became, truly became infrastructure as code. So the dev-ops culture has permeated our small organization, can't imagine the impact on a larger company. Wonder if you could talk about that a little bit. >> Definitely. So... As customers are going through this cloud migration journey they are looking at their entire landscape of application and they're discovering things that they never did. When they discover they are trying to figure out should I go ahead and migrate everything to AWS right now, or should I a refactor and optimize some of my applications. And there I'm seeing both types of decisions where some customers are taking most of their applications shifting it to cloud and then pausing and thinking now it is phase two where I am on cloud, I want to take advantage of the best of the breed whatever technology is there. And I want to transform my applications and I want to really be more agile. At the same time there are customers who are saying that I'm going to discover all my workload and applications and I'm going to prioritize a small set of applications which we are going to take through transformation right now. And for the rest of it we will lift and shift and then we will transform. But as they go through this transformation they are changing the way they do business. They are changing the way they are utilizing different technology. Their core focus is on how do I really compete with my competition in the industry and for that how can IT provide me that agility that I need to roll out changes in my business day in day out. And for that, you know, Lambda, entire code portfolio, code build, code commit, code deploy, as well as cloud trail, and you know all the things that, all the services we have as well as our partners have, they provide them truly that edge on their industry and market. >> Bina, how has the security discussion changed? When Stu and I were at the AWS public sector summit in June, the CIO of the CIA stood up on stage in front of 10,000 people and said, "The cloud on my worst day from a security perspective "is better than my client server infrastructure "on a best day." That's quite an endorsement from the CIA, who's got some chops in security. How has that discussion changed? Obviously it's still fundamental, critical, it's something that you guys emphasize. But how has the perception and reality changed over the last five years? >> Cloud is, you know, security in cloud is a shared responsibility. So, Amazon is really, really good at providing all the very, very secure infrastructure. At the same time we are also really good at providing customers and business partners all of the tools and hand-holding them so that they can make their application secure. Like you said, you know, AWS, many of the analysts are saying that AWS is far more secure than anything they can have within their own data center. And as you can see that in this journey also customers are not now thinking about is it secure or not. We are seeing the conversation that, how in fact, speaking of Splunk right, one customer that I talked to he was saying that I was asking them why did you choose Splunk cloud on AWS and his take was that, "I wanted near instantaneous SOA compliant "and by moving to Splunk cloud on AWS "I got that right away." Even I'm talking to public sector customers they are saying, you know, I want fair DRAM I want in healthcare industry, I want HIPPA Compliance. Everywhere we are seeing that we are able to keep up with security and compliance requirements much faster than what customers can do on their own. >> So they, so you take care of, certainly from the infrastructure standpoint, those certifications and that piece of the compliance so the customer can worry about maybe some of the things that you don't cover, maybe some of their business processes and other documentation, ITIL stuff that they have to do, whatever. But now they have more time to do that presumably 'cause that's check box, AWS has that covered for me, right? Is that the right thinking? >> Yes, plus we provide them all the tools and support and knowledge and everything so that they, and even partner support who are really good at it so that not only they understand that the application and infrastructure will come together as entire secure environment but also they have everything they need to be able to make applications secure. And Splunk is another great example, right? Splunk helps customer get application level security and AWS is providing them infrastructure and together we are working together to make sure our customers' application and infrastructure together are secure. >> So speaking about migrations database, hot topic at a high level anyway, I wonder if you could talk about database migrations. Andy Jassy obviously talks a lot about, well let's see we saw RDS on Prim at VMworld, big announcement. Certainly Aurora, DynamoDB is one of the databases we use. Redshift obviously. How are database migrations going, what are you doing to make those easier? >> So what we do in a nutshell, right for everything we try to build a programatic reputable, scalable approach. That's what Amazon does. And what we do is that for each of these standard migrations for databases, we try to figure out, that let's take few examples, and let's figure out Play Books, let's figure out runbooks, let's make sure technical integrations are in place. We have quick starts in place. We have consulting partners who are really good at doing this again and again and again. And we have all the knowledge built into tools and services and support so that whenever customers want to do it they don't run into hiccups and they have really pleasant experience. >> Excellent. Well I know you're super busy thanks for making some time to come on theCUBE I always love to have AWS on. So thanks for your time Bina. >> Thank you very nice to meet you both. >> Alright you're very welcome. Alright so that's a wrap for day one here at Splunk .conf 2018, Stu and I will be back tomorrow. Day two more customers, we got senior executives coming on tomorrow, course Doug Merritt, always excited to see Doug. Go to siliconangle.com you'll see all the news theCUBE.net is where all these videos live and wikibon.com for all the research. We're out day one Splunk you're watching theCUBE we'll see you tomorrow. Thanks for watching. >> Bina: Thank you. (electronic music)

>> Announcer: Live from the Bill Graham Auditorium in San Francisco, it's theCUBE, covering Pure Storage Accelerate 2018. Brought to be you by Pure Storage. >> Welcome back to theCUBE, we are live at Pure Storage Accelerate 2018 in San Francisco. I'm Lisa Prince Martin with Dave The Who Vellante, and we're with David Hatfield, or Hat, the president of Purse Storage. Hat, welcome back to theCUBE. >> Thank you Lisa, great to be here. Thanks for being here. How fun is this? >> The orange is awesome. >> David: This is great. >> Super fun. >> Got to represent, we love the orange here. >> Always a good venue. >> Yeah. >> There's not enough orange. I'm not as blind yet. >> Well it's the Bill Graham, I mean it's a great venue. But not generally one for technology conferences. >> Not it's not. You guys are not conventional. >> So far so good. >> But then-- >> Thanks for keeping us out of Las Vegas for a change. >> Over my dead body I thin I've said once or twice before. >> Speaking of-- Love our customers in Vegas. Unconventional, you've said recently this is not your father's storage company. What do you mean by that? >> Well we just always want to do things a little bit less conventional. We want to be modern. We want to do things differently. We want to create an environment where it's community so our customers and our partners, prospective customers can get a feel for what we mean by doing things a little bit more modern. And so the whole orange thing is something that we all opt in for. But it's more about really helping transform customer's organizations think differently, think out of the box, and so we wanted to create a venue that forced people to think differently, and so the last three years, one was on Pier 48, we transformed that. Last year was in a big steelworkers, you know, 100 year old steel manufacturing, ship building yard which is now long since gone. But we thought the juxtaposition of that, big iron rust relative to what we're doing from a modern solid state perspective, was a good metaphor. And here it's about making music, and how can we together as an industry, develop new things and develop new songs and really help transform organizations. >> For those of you who don't know, spinning disk is known as spinning rust, right? Eventually, so very clever sort of marketing. >> The more data you put on it the slower it gets and it gets really old and we wanted to get rid of that. We wanted to have everything be online in the data center, so that was the point. >> So Hat, as you go around and talk to customers, they're going through a digital transformation, you hear all this stuff about machine intelligence, artificial intelligence, whatever you want to call it, what are the questions that you're getting? CEO's, they want to get digital right. IT professionals are wondering what's next for them. What kind of questions and conversations are you having? >> Yeah, I think it's interesting, I was just in one of the largest financial services companies in New York, and we met with the Chief Data Officer. The Chief Data Officer reports into the CEO. And he had right next to him the CIO. And so they have this development of a recognition that moving into a digital world and starting to harness the power of data requires a business context. It requires people that are trying to figure out how to extract value from the data, where does our data live? But that's created the different organization. It drives devops. I mean, if you're going to go through a digital transformation, you're going to try and get access to your data, you have to be a software development house. And that means you're going to use devops. And so what's happened from our point of view over the last 10 years is that those folks have gone to the public cloud because IT wasn't really meeting the needs of what devops needed and what the data scientists were looking for, and so what we wanted to create not only was a platform and a tool set that allowed them to bridge the gap, make things better today dramatically, but have a platform that gets you into the future, but also create a community and an ecosystem where people are aware of what's happening on the devop's side, and connect the dots between IT and the data scientists. And so we see this exploding as companies digitize, and somebody needs to be there to help kind of bridge the gap. >> So what's your point of view and advice to that IT ops person who maybe really good at provisioning LUNS, should they become more dev like? Maybe ops dev? >> Totally, I mean I think there's a huge opportunity to kind of advance your career. And a lot of what Charlie talked about and a lot of what we've been doing for nine years now, coming up on nine years, is trying to make our customers heroes. And if data is a strategic asset, so much so they're actually going to think about putting it on your balance sheet, and you're hiring Chief Data Officers, who knows more about the data than the storage and infrastructure team. They understand the limitations that we had to go through over the past. They've recognized they had to make trade offs between performance and cost. And in a shared accelerated storage platform where you have tons of IO and you can put all of your applications (mumbles) at the same time, you don't have to make those trade offs. But the people that really know that are the storage leads. And so what we want to do is give them a path for their career to become strategic in their organization. Storage should be self driving, infrastructure should be self driving. These are not things that in a boardroom people care about, gigabytes and petabytes and petaflops, and whatever metric. What they care about is how they can change their business and have a competitive advantage. How they can deliver better customer experiences, how they can put more money on the bottom line through better insights, etc. And we want to teach and work with and celebrate data heroes. You know, they're coming from the infrastructure side and connecting the dots. So the value of that data is obviously something that's new in terms of it being front and center. So who determines the value of that data? You would think it's the business line. And so there's got to be a relationship between that IT ops person and the business line. Which maybe here to for was somewhat adversarial. Business guys are calling, the clients are calling again. And the business guys are saying, oh IT, they're slow, they say no. So how are you seeing that relationship changing? >> It has to come together because, you know, it does come down to what are the insights that we can extract from our data? How much more data can we get online to be able to get those insights? And that's a combination of improving the infrastructure and making it easy and removing those trade offs that I talked about. But also being able to ask the right questions. And so a lot has to happen. You know, we have one of the leaders in devops speaking tomorrow to go through, here's what's happening on the software development and devops side. Here's what the data scientists are trying to get at. So our IT professionals understand the language, understand the problem set. But they have to come together. We have Dr. Kate Harding as well from MIT, who's brilliant and thinking about AI. Well, there's only .5% of all the data has actually been analyzed. You know, it's all in these piggy banks as Burt talked about onstage. And so we want to get rid of the piggy banks and actually create it and make it more accessible, and get more than .5% of the data to be usable. You know, bring as much of that online as possible, because it's going to provide richer insights. But up until this point storage has been a bottleneck to making that happen. It was either too costly or too complex, or it wasn't performing enough. And with what we've been able to bring through solid state natively into sort of this platform is an ability to have all of that without the trade offs. >> That number of half a percent, or less than half a percent of all data in the world is actually able to be analyzed, is really really small. I mean we talk about, often you'll here people say data's the lifeblood of an organization. Well, it's really a business catalyst. >> David: Oil. >> Right, but catalysts need to be applied to multiple reactions simultaneously. And that's what a company needs to be able to do to maximize the value. Because if you can't do that there's no value in that. >> Right. >> How are you guys helping to kind of maybe abstract storage? We hear a lot, we heard the word simplicity a lot today from Mercedes Formula One, for example. How are you partnering with customers to help them identify, where do we start narrowing down to find those needles in the haystack that are going to open up new business opportunities, new services for our business? >> Well I think, first of all, we recognize at Pure that we want to be the innovators. We want to be the folks that are, again, making things dramatically better today, but really future-proofing people for what applications and insights they want to get in the future. Charlie talked about the three-legged stool, right? There's innovations that's been happening in compute, there's innovations that have been happening over the years in networking, but storage hasn't really kept up. It literally was sort of the bottleneck that was holding people back from being able to feed the GPUs in the compute that's out there to be able to extract the insights. So we wanted to partner with the ecosystem, but we recognize an opportunity to remove the primary bottleneck, right? And if we can remove the bottleneck and we can partner with firms like NVIDIA and firms like Cisco, where you integrate the solution and make it self driving so customers don't have to worry about it. They don't have to make the trade offs in performance and cost on the backend, but it just is easy to stamp out, and so it was really great to hear Service Now and Keith walk through is story where he was able to get a 3x level improvement and something that was simple to scale as their business grew without having an impact on the customer. So we need to be part of an ecosystem. We need to partner well. We need to recognize that we're a key component of it because we think data's at the core, but we're only a component of it. The one analogy somebody shared with me when I first started at Pure was you can date your compute and networking partner but you actually get married to your storage partner. And we think that's true because data's at the core of every organization, but it's making it available and accessible and affordable so you can leverage the compute and networking stacks to make it happen. >> You've used the word platform, and I want to unpack that a little bit. Platform versus product, right? We hear platform a lot today. I think it's pretty clear that platforms beat products and that allows you to grow and penetrate the market further. It also has an implication in terms of the ecosystem and how you partner. So I wonder if you could talk about platform, what it means to you, the API economy, however you want to take that. >> Yeah, so, I mean a platform, first of all I think if you're starting a disruptive technology company, being hyper-focused on delivering something that's better and faster in every dimension, it had to be 10x in every dimension. So when we started, we said let's start with tier one block, mission critical data workloads with a product, you know our Flash Array product. It was the fastest growing product in storage I think of all time, and it still continues to be a great contributor, and it should be a multi-billion dollar business by itself. But what customers are looking for is that same consumer like or cloud like experience, all of the benefits of that simplicity and performance across their entire data set. And so as we think about providing value to customers, we want to make sure we capture as much of that 99.5% of the data and make it online and make it affordable, regardless of whether it's block, file, or object, or regardless if it's tier one, tier two, and tier three. We talk about this notion of a shared accelerated storage platform because we want to have all the applications hit it without any compromise. And in an architecture that we've provided today you can do that. So as we think about partnering, we want to go, in our strategy, we want to go get as much of the data as we possibly can and make it usable and affordable to bring online and then partner with an API first open approach. There's a ton of orchestration tools that are out there. There's great automation. We have a deep integration with ACI at Cisco. Whatever management and orchestration tools that our customer wants to use, we want to make those available. And so, as you look at our Flash Array, Flash Deck, AIRI, and Flash Blade technologies, all of them have an API open first approach. And so a lot of what we're talking about with our cloud integrations is how do we actually leverage orchestration, and how do we now allow and make it easy for customers to move data in and out of whatever clouds they may want to run from. You know, one of the key premises to the business was with this exploding data growth and whether it's 30, 40, 50 zettabytes of data over the next you know, five years, there's only two and a half or three zettabytes of internet connectivity in those same period of time. Which means that companies, and there's not enough data platform or data resources to actually handle all of it, so the temporal nature of the data, where it's created, what a data center looks like, is going to be highly distributed, and it's going to be multi cloud. And so we wanted to provide an architecture and a platform that removed the trade offs and the bottlenecks while also being open and allowing customers to take advantage of Red Shift and Red Hat and all the container technologies and platform as a service technologies that exist that are completely changing the way we can access the data. And so we're part of an ecosystem and it needs to be API and open first. >> So you had Service Now on stage today, and obviously a platform company. I mean any time they do M and A they bring that company into their platform, their applications that they build are all part of that platform. So should we think about Pure? If we think about Pure as a platform company, does that mean, I mean one of your major competitors is consolidating its portfolio. Should we think of you going forward as a platform company? In other words, you're not going to have a stovepipe set of products, or is that asking too much as you get to your next level of milestone. >> Well we think we're largely there in many respects. You know, if you look at any of the competitive technologies that are out there, you know, they have a different operating system and a different customer experience for their block products, their file products, and their object products, etc. So we wanted to have a shared system that had these similar attributes from a storage perspective and then provide a very consistent customer experience with our cloud-based Pure One platform. And so the combination of our systems, you hear Bill Cerreta talk about, you have to do different things for different protocols to be able to get the efficiencies in the data servers as people want. But ultimately you need to abstract that into a customer experience that's seamless. And so our Pure One cloud-based software allows for a consistent experience. The fact that you'll have a, one application that's leveraging block and one application that's leveraging unstructured tool sets, you want to be able to have that be in a shared accelerated storage platform. That's why Gartner's talking about that, right? Now you can do it with a solid state world. So it's super key to say, hey look, we want consistent customer experience, regardless of what data tier it used to be on or what protocol it is and we do that through our Pure One cloud-based platform. >> You guys have been pretty bullish for a long time now where competition is concerned. When we talk about AWS, you know Andy Jassy always talks about, they look forward, they're not looking at Oracle and things like that. What's that like at Pure? Are you guys really kind of, you've been also very bullish recently about NVME. Are you looking forward together with your partners and listening to the voice of the customer versus looking at what's blue over the corner? >> Yes, so first of all we have a lot of respect for companies that get big. One of my mentors told me one time that they got big because they did something well. And so we have a lot of respect for the ecosystem and companies that build a scale. And we actually want to be one of those and are already doing that. But I think it's also important to listen and be part of the community. And so we've always wanted to the pioneers. We always wanted to be the innovators. We always wanted to challenge conventions. And one of the reasons why we founded the company, why Cos and Hayes founded the company originally was because they saw that there was a bottleneck and it was a media level bottleneck. In order to remove that you need to provide a file system that was purpose built for the new media, whatever it was going to be. We chose solid state because it was a $40 billion industry thanks to our consumer products and devices. So it was a cost curve where I and D was going to happen by Samsung and Toshiba and Micron and all those guys that we could ride that curve down, allowing us to be able to get more and more of the data that's out there. And so we founded the company with the premise that you need to remove that bottleneck and you can drive innovation that was 10x better in every dimension. But we also recognize in doing so that putting an evergreen ownership model in place, you can fundamentally change the business model that customers were really frustrated by over the last 25 years. It was fair because disk has lots of moving parts, it gets slower with the more data you put on, etc., and so you pass those maintenance expenses and software onto customers. But in a solid state world you didn't need that. So what we wanted to do was actually, in addition to provide innovation that was 10x better, we wanted to provide a business model that was evergreen and cloud like in every dimension. Well, those two forces were very disruptive to the competitors. And so it's very, very hard to take a file system that's 25 years old and retrofit it to be able to really get the full value of what the stack can provide. So we focus on innovation. We focus on what the market's are doing, and we focus on our customer requirements and where we anticipate the use cases to be. And then we like to compete, too. We're a company of folks that love to win, but ultimately the real focus here is on enabling our customers to be successful, innovating forward. And so less about looking sidewise, who's blue and who's green, etc. >> But you said it before, when you were a startup, you had to be 10x better because those incumbents, even though it was an older operating system, people's processes were wired to that, so you had to give them an incentive to do that. But you have been first in a number of things. Flash itself, the sort of All-Flash, at a spinning disk price. Evergreen, you guys set the mark on that. NVME you're doing it again with no premium. I mean, everybody's going to follow. You can look back and say, look we were first, we led, we're the innovator. You're doing some things in cloud which are similar. Obviously you're doing this on purpose. But it's not just getting close to your customers. There's got to be a technology and architectural enabler for you guys. Is that? >> Well yeah, it's software, and at the end of the day if you write a file system that's purpose built for a new media, you think about the inefficiencies of that media and the benefits of that media, and so we knew it was going to be memory, we knew it was going to be silicon. It behaves differently. Reads are effectively free. Rights are expensive, right? And so that means you need to write something that's different, and so you know, it's NVME that we've been plumbing and working on for three years that provides 44,000 parallel access points. Massive parallelism, which enables these next generation of applications. So yeah we have been talking about that and inventing ways to be able to take full advantage of that. There's 3D XPoint and SCM and all kinds of really interesting technologies that are coming down the line that we want to be able to take advantage of and future proof for our customers, but in order to do that you have to have a software platform that allows for it. And that's where our competitive advantage really resides, is in the software. >> Well there are lots more software companies in Silicon Valley and outside Silicon Valley. And you guys, like I say, have achieved that escape velocity. And so that's pretty impressive, congratulations. >> Well thank you, we're just getting started, and we really appreciate all the work you guys do. So thanks for being here. >> Yeah, and we just a couple days ago with the Q1FY19, 40%, you have a year growth, you added 300 more customers. Now what, 4800 customers globally. So momentum. >> Thank you, thank you. Well we only do it if we're helping our customers one day at a time. You know, I'll tell you that this whole customer first philosophy, a lot of customers, a lot of companies talk about it, but it truly has to be integrated into the DNA of the business from the founders, and you know, Cos's whole pitch at the very beginning of this was we're going to change the media which is going to be able to transform the business model. But ultimately we want to make this as intuitive as an iPhone. You know, infrastructure should just work, and so we have this focus on delivering simplicity and delivering ownership that's future proofed from the very beginning. And you know that sort of permeates, and so you think about our growth, our growth has happened because our customers are buying more stuff from us, right? If you look at our underneath the covers on our growth, 70 plus percent of our growth every single quarter comes from customers buying more stuff, and so, as we think about how we partner and we think about how we innovate, you know, we're going to continue to build and innovate in new areas. We're going to keep partnering. You know, the data protection staff, we've got great partners like Veeam and Cohesity and Rubrik that are out there. And we're going to acquire. We do have a billion dollars of cash in the bank to be able to go do that. So we're going to listen to our customers on where they want us to do that, and that's going to guide us to the future. >> And expansion overseas. I mean, North America's 70% of your business? Is that right? >> Rough and tough. Yeah, we had 28%-- >> So it's some upside. >> Yeah, yeah, no any mature B2B systems company should line up to be 55, 45, 55 North America, 45, in line with GDP and in line with IT spend, so we made investments from the beginning knowing we wanted to be an independent company, knowing we wanted to support global 200 companies you have to have operations across multiple countries. And so globalization is always going to be key for us. We're going to continue our march on doing that. >> Delivering evergreen from an orange center. Thanks so much for joining Dave and I on the show this morning. >> Thanks Lisa, thanks Dave, nice to see you guys. >> We are theCUBE Live from Pure Accelerate 2018 from San Francisco. I'm Lisa Martin for Dave Vellante, stick around, we'll be right back with our next guests.