from Seattle Washington extracting the signal from the noise it's the cube on the ground at OpenStack days Seattle 2015 now here's your host John furrier hello and welcome to Seattle this is a special Q presentation cube on the ground OTG we call it on the ground we go out to the event and talk to all the thought leader I'm John far with the QNX arendelle with SolidFire also the famous cloudcast podcast great to see you again I know good to see John cloudcast is a hot podcast all the thought leaders are listening customers are listening guys are really the signal out there on cloud and also SolidFire growing yes all flash storage you gotta kick in some but they're always keeping tabs on you guys new approach the cloud what's going on with cloud give us the update of OpenStack what's the bottom line I mean is it failing is it winning is it growing is it stalled what do we expect to see ya know so it's at an interesting point because it absolutely is growing but it still has some operational challenges that's the number one thing we're seeing right now is actually just talking to some folks in the hall of common theme is you're still trying to figure how to upgrade it easily still figuring how to operate it easily right and the gentleman from canonical made that made the the reference you know ketchup right everyone has the in green stuff in your kitchen but no one makes their ketchup right and I thought that was fantastic because it's you know everyone's kind of looking for that easy button and it's starting to show up you know you've got you the blue box folks you've got the platform nine folks you've got some interesting startups actually coming into the OpenStack space which shows us there is some definitely some innovation and some new things going on but it's because of the challenges we faced until now the question is the ketchup good I mean is that last ingredient going to make it so that it's not too watery I mean is Cooper Nettie's is containers so truly is it good ketchup and yeah what's the next was the key ingredient well yeah and that's that's a fantastic point because we are at this inflection point where OpenStack was a necessary next that without a doubt we had to get that first step into cloud native applications had to do it but where we're going with Mesa sand cabrion at ease with mesa con going on down the street is that the true next evolution is it like the OpenStack Murano project where you're kind of getting containers built into OpenStack we'll have to wait and see because that anytime you talk to burn a DS anytime you talk Mesa that's is so cutting edge so at this point I'm still Silicon Valley home so OpenStack obviously meme of a sec being dead is kind of falls we saw some things happen last year so it opens dec sv some people aren't going to be there this year that were there last year yes either went out of business or executives have left but yet a lot of dynamics going on palma risks is stepping down as CEO of cloud pivotal cloud foundry cleans 100 million dollars in revenue leather to see those books but but the question now see amazon is doing their thing and but it's really a dynamic market right now so so it's there yes the question is who's doing what in revenue what's the numbers is it all professional surgery and cloud found your hundred million that's a huge number i just is that all professional services do they actually selling product yeah and that's a fantastic moment because the m the cloud cast we saw this consolidation coming for a long time we really started covering OpenStack about four years ago and we were just waiting for at some point you know when we first started there was 15 plus startups in the OpenStack space and there just wasn't enough customers there there wasn't enough revenue there and you just saw this natural consolidation come to a head last year and yeah some are no longer here a lot of them were sucked up into the various vendors and what you're seeing now is especially at the OpenStack summits and like these events here you have a much more mature ecosystem it's almost like the new legacy of you know all of these vendors are there they're all mature they're trying to play in this space they're trying to make money off of it and time will tell and then it's an evolution anybody brought to point you right over the easy button what is that easy button now is it just deployment in a box is it like just give me prefabricated OpenStack is it tooling is it management we're hearing a lot of different things yeah and I think time will tell but I do think the preference we're seeing in our customers is definitely moving towards that easy button as a service if you will of some of those companies where the operations have open stack because it hasn't gotten easier at the same level of the adoption people are looking to what is that next step if the operations were to get easier i don't think we'd see that market be as popular as it is right now is it is the market still in early adopter that's the thing that's on my mind has it crossed over yet I think it has I think we're at least in OpenStack context where we're beyond early adopter phase there is a lot of folks out there using it but what's interesting is is to kind of go back around to the previous question a little bit the district's taken off like I think they probably should have most of the large customers I've seen are still roll your own and it is still that staff of Engineers really keeping up and running and again because the what was the value-added the distributions we're starting to see the Red Hat distribution get a you know to that point where we're getting good adoption of that we're seeing the marantis one with all the fuel work they're doing we're getting good adoption with that so the question on adoption is it's either not Oh people aren't aware of it or the product sucks so is it mix of both is it awareness issue or is it a product issue oh that's a great question i think it's a it's a question of differentiation I don't know that it's differentiated enough at this point in time it's it's you know if you go build your own versus you farm it out if you will completely big differences right but it's almost like shades who could be fear yeah it could be a third dimension you could absolutely be fear well that's the thing you've been the issue solution of operators we hear a lot of an operator so the question is if I'm an engineering team I might want to have my tire kickers go through the motions and that's not necessary approval con so that's just core competency building so that fear could be an issue of cork opera so maybe they're aware of it maybe the products decent maybe it's just that their team's not core enough to do that yeah when it comes to the folks in house um yeah again going back to the easy button what we really need in the opposite community is that POC in a box and that's probably there today don't get me wrong but but everyone sees that POC in a box but then they're afraid of does that mean can I scale it out to 100 nodes a thousand nodes and will it be as easy and it's almost gotten a reputation now of know and and so how do we get it to grow to 100 notes thousand nodes whatever you want and do the business value out of I don't need a big staff of people and how do I get you know the underlying infrastructure to be simpler at the end of the day a little cloud cast we got going on here I mean I think in my opinion my opinion I think it's just a matter of the customers having the ability to execute and have the total cost of ownership equation nailed I think there's still this gray area of there's no straight and narrow on on the execution what's my cost i'm gonna be locked into that vendor what's going to be the lock-in oh my god yeah the shark fin the iceberg whatever metaphor you want to use yes no is that reading is their visibility on the ownership side because downstream what's the impact well it what's interesting there too is the biggest thing I'm seeing is for again from an operation standpoint how do we make this as simple as possible because what happens is you have this weird convoluted thing if you have the whole legacy apps versus cloud native apps and you take that put it aside for a second rank if we take that and put it aside well what what do they really want doesn't matter what kind of app it is well the developers want API driven infrastructure you can call it cloud but the end of the day it's it's an infrastructure that's driven by api's and then as simple as possible you know being able to really guarantee the uptime guarantee the performance and that's where OpenStack at times it gets a bad rap I don't and I'm not even necessarily agreeing with that might not even be worthy of a bad rap in that agreed absolutely because there are known customers out there that are doing it and doing it very well but again is how do you get beyond that room well Stu miniman I'm Wikibon and Brian Grace Lee and now Wikibon and and I Robin conversation about this and I think Dave vellante even chimed in and we were debating was up across the board different opinions yes what the hell is cloud native app mean you know is it is amazonas cloudy of course they're cloud Facebook a cloud native app okay but what does that mean for enterprises that mean that the app was built for just API so to me it just doesn't seen it's been a lot of there's not a lot of cloud native apps out there right now or are now what is a cloud yeah and and it's a fantastic question and my opinion have always been you know there's there was this kind of trend in the industry how do I take these legacy apps and make them cloud native well the simple answer is you don't the way I look at it is it's really more of like a star of the old build the new mentality you you want to maintain those legacy systems but the same time as those kind of age off the books if you will you're going to have to build a new infrastructure so if you're going to build new infrastructure you might as well build it the new way but that has to happen over time that is not something that happens you know most businesses out there today they don't do technology for the sake of technology there has to be a business reason and a business driver if that legacy app is still out there making them money they're going to keep using I not untrue to your point it's you cloud native is the future the soil asked of you know yeah yield some fruit on that tree if you will so that's going to take some time exactly so so you know I very much see this as a longer tail that most people would like without a doubt it is just a matter of how are we going to get their long-term and yeah there's lots of terminology and the cloud native and what does that mean big picture and architectural II that's all solved it's getting the businesses to rewrite the apps and really give them Aaron we're in Seattle right now on the ground so quickly describe to the folks out there what's the vibe here what's it like a Seattle it's been it is so it's been interesting I've been in here since tuesday now and i've done lenox con cloudstack day OpenStack day and mesa con all in the in three days now so it's what did you learn yeah it's been a world in 30-second I know yeah so it the biggest thing is there is still a lot of confusion in yes people are starting to get legacy versus cloud native but when it comes to which technologies do i use why would i use them what are the actual business drivers to actually go adopt some of these new technologies massive amounts of confusion around that and that's probably the biggest reason for you know trying to get knowledge out in the industry without a doubt okay we are OTG on the ground this is the cube in Seattle I'm John for thanks for watching and all the coverage here at OpenStack innovation day thanks for watching

(upbeat music) >> Welcome back to Supercloud 2 this is Dave Vellante. We're here exploring the intersection of data and analytics and the future of cloud. And in this segment, we're going to look at the evolution of cloud, and try to test some of the Supercloud concepts and assumptions with Brian Gracely, is the founder and co-host along with Aaron Delp of the popular Cloudcast program. Amazing series, if you're not already familiar with it. The Cloudcast is one of the best ways to keep up with so many things going on in our industry. Enterprise tech, platform engineering, business models, obviously, cloud developer trends, crypto, Web 3.0. Sorry Brian, I know that's a sore spot, but Brian, thanks for coming >> That's okay. >> on the program, really appreciate it. >> Yeah, great to be with you, Dave. Happy New Year, and great to be back with everybody with SiliconANGLE again this year. >> Yeah, we love having you on. We miss working with you day-to-day, but I want to start with Gracely's theorem, which basically says, I'm going to paraphrase. For the most part, nothing new gets introduced in the enterprise tech business, patterns repeat themselves, maybe get applied in new ways. And you know this industry well, when something comes out that's new, if you take virtualization, for example, been around forever with mainframes, but then VMware applied it, solve a real problem in the client service system. And then it's like, "Okay, this is awesome." We get really excited and then after a while we pushed the architecture, we break things, introduce new things to fix the things that are broken and start adding new features. And oftentimes you do that through acquisitions. So, you know, has the cloud become that sort of thing? And is Supercloud sort of same wine, new bottle, following Gracely's theorem? >> Yeah, I think there's some of both of it. I hate to be the sort of, it depends sort of answer but, I think to a certain extent, you know, obviously Cloud in and of itself was, kind of revolutionary in that, you know, it wasn't that you couldn't rent things in the past, it was just being able to do it at scale, being able to do it with such amazing self-service. And then, you know, kind of proliferation of like, look at how many services I can get from, from one cloud, whether it was Amazon or Azure or Google. And then, you know, we, we slip back into the things that we know, we go, "Oh, well, okay, now I can get computing on demand, but, now it's just computing." Or I can get database on demand and it's, you know, it's got some of the same limitations of, of say, of database, right? It's still, you know, I have to think about IOPS and I have to think about caching, and other stuff. So, I think we do go through that and then we, you know, we have these sort of next paradigms that come along. So, you know, serverless was another one of those where it was like, okay, it seems sort of new. I don't have to, again, it was another level of like, I don't have to think about anything. And I was able to do that because, you know, there was either greater bandwidth available to me, or compute got cheaper. And what's been interesting is not the sort of, that specific thing, serverless in and of itself is just another way of doing compute, but the fact that it now gets applied as, sort of a no-ops model to, you know, again, like how do I provision a database? How do I think about, you know, do I have to think about the location of a service? Does that just get taken care of for me? So I think the Supercloud concept, and I did a thing and, and you and I have talked about it, you know, behind the scenes that maybe the, maybe a better name is Super app for something like Snowflake or other, but I think we're, seeing these these sort of evolutions over and over again of what were the big bottlenecks? How do we, how do we solve those bottlenecks? And I think the big thing here is, it's never, it's very rarely that you can take the old paradigm of what the thing was, the concept was, and apply it to the new model. So, I'll just give you an example. So, you know, something like VMware, which we all know, wildly popular, wildly used, but when we apply like a Supercloud concept of VMware, the concept of VMware has always been around a cluster, right? It's some finite number of servers, you sort of manage it as a cluster. And when you apply that to the cloud and you say, okay, there's, you know, for example, VMware in the cloud, it's still the same concept of a cluster of VMware. But yet when you look at some of these other services that would fit more into the, you know, Supercloud kind of paradigm, whether it's a Snowflake or a MongoDB Atlas or maybe what CloudFlare is doing at the edge, those things get rid of some of those old paradigms. And I think that's where stuff, you start to go, "Oh, okay, this is very different than before." Yes, it's still computing or storage, or data access, but there's a whole nother level of something that we didn't carry forward from the previous days. And that really kind of breaks the paradigm. And so that's the way I think I've started to think about, are these things really brand new? Yes and no, but I think it's when you can see that big, that thing that you didn't leave behind isn't there anymore, you start to get some really interesting new innovation come out of it. >> Yeah. And that's why, you know, lift and shift is okay, when you talk to practitioners, they'll say, "You know, I really didn't change my operating model. And so I just kind of moved it into the cloud. there were some benefits, but it was maybe one zero not three zeros that I was looking for." >> Right. >> You know, we always talk about what's great about cloud, the agility, and all the other wonderful stuff that we know, what's not working in cloud, you know, tie it into multi-cloud, you know, in terms of, you hear people talk about multi-cloud by accident, okay, that's true. >> Yep. >> What's not great about cloud. And then I want to get into, you know, is multi-cloud really a problem or is it just sort of vendor hype? But, but what's not working in cloud? I mean, you mentioned serverless and serverless is kind of narrow, right, for a lot of stateless apps, right? But, what's not great about cloud? >> Well, I think there's a few things that if you ask most people they don't love about cloud. I think, we can argue whether or not sort of this consolidation around a few cloud providers has been a good thing or a bad thing. I think, regardless of that, you know, we are seeing, we are hearing more and more people that say, look, you know, the experience I used to have with cloud when I went to, for example, an Amazon and there was, you know, a dozen services, it was easy to figure out what was going on. It was easy to figure out what my billing looked like. You know, now they've become so widespread, the number of services they have, you know, the number of stories you just hear of people who went, "Oh, I started a service over in US West and I can't find it anymore 'cause it's on a different screen. And I, you know, I just got billed for it." Like, so I think the sprawl of some of the clouds has gotten, has created a user experience that a lot of people are frustrated with. I think that's one thing. And we, you know, we see people like Digital Ocean and we see others who are saying, "Hey, we're going to be that simplified version." So, there's always that yin and yang. I think people are super frustrated at network costs, right? So, you know, and that's kind of at a lot of, at the center of maybe why we do or don't see more of these Supercloud services is just, you know, in the data center as an application owner, I didn't have to think about, well where, where does this go to? Where are my users? Yes, somebody took care of it, but when those things become front and center, that's super frustrating. That's the one area that we've seen absolutely no cost savings, cost reduction. So I think that frustrates people a lot. And then I think the third piece is just, you know, we're, we went from super centralized IT organizations, which, you know, for decades was how it worked. It was part of the reason why the cloud expanded and became a thing, right? Sort of shadow IT and I can't get things done. And then, now what we've seen is sort of this proliferation of little pockets of groups that are your IT, for lack of a better thing, whether they're called platform engineering or SRE or DevOps. But we have this, expansion, explosion if you will, of groups that, if I'm an app dev team, I go, "Hey, you helped me make this stuff run, but then the team next to you has another group and they have another group." And so you see this explosion of, you know, we don't have any standards in the company anymore. And, so sort of self-service has created its own nightmare to a certain extent for a lot of larger companies. >> Yeah. Thank you for that. So, you know, I want, I want to explore this multi-cloud, you know, by accident thing and is a real problem. You hear that a lot from vendors and we've been talking about Supercloud as this unifying layer across cloud. You know, but when you talk to customers, a lot of them are saying, "Yes, we have multiple clouds in our organization, but my group, we have mono cloud, we know the security, edicts, we know how to, you know, deal with the primitives, whether it's, you know, S3 or Azure Blob or whatever it is. And we're very comfortable with this." It's, that's how we're simplifying. So, do you think this is really a problem? Does it have merit that we need that unifying layer across clouds, or is it just too early for that? >> I think, yeah, I think what you, what you've laid out is basically how the world has played out. People have picked a cloud for a specific application or a series of applications. Yeah, and I think if you talk to most companies, they would tell you, you know, holistically, yes, we're multi-cloud, not, maybe not necessarily on, I don't necessarily love the phrase where people say like, well it happened by accident. I think it happened on purpose, but we got to multi-cloud, not in the way that maybe that vendors, you know, perceived, you know, kind of laid out a map for. So it was, it was, well you will lay out this sort of Supercloud framework. We didn't call it that back then, we just called it sort of multi-cloud. Maybe it was Kubernetes or maybe it was whatever. And different groups, because central IT kind of got disbanded or got fragmented. It turned into, go pick the best cloud for your application, for what you need to do for the business. And then, you know, multiple years later it was like, "Oh, hold on, I've got 20% in Google and 50% in AWS and I've got 30% in Azure. And, you know, it's, yeah, it's been evolution. I don't know that it's, I don't know if it's a mistake. I think it's now groups trying to figure out like, should I make sense of it? You know, should I try and standardize and I backwards standardize some stuff? I think that's going to be a hard thing for, for companies to do. 'cause I think they feel okay with where the applications are. They just happen to be in multiple clouds. >> I want to run something by you, and you guys, you and Aaron have talked about this. You know, still depending on who, which keynote you listen to, small percentage of the workloads are actually in cloud. And when you were with us at Wikibon, I think we called it true private cloud, and we looked at things like Nutanix and there were a lot of other examples of companies that were trying to replicate the hyperscale experience on Prem. >> Yeah. >> And, we would evaluate that, you know, beyond virtualization, and so we sort of defined that and, but I think what's, maybe what's more interesting than Supercloud across clouds is if you include that, that on Prem estate, because that's where most of the work is being done, that's where a lot of the proprietary tools have been built, a lot of data, a lot of software. So maybe there's this concept of sending that true private cloud to true hybrid cloud. So I actually think hybrid cloud in some cases is the more interesting use case for so-called Supercloud. What are your thoughts on that? >> Yeah, I think there's a couple aspects too. I think, you know, if we were to go back five or six years even, maybe even a little further and look at like what a data center looked like, even if it was just, "Hey we're a data center that runs primarily on VMware. We use some of their automation". Versus what you can, even what you can do in your data center today. The, you know, the games that people have seen through new types of automation through Kubernetes, through get ops, and a number of these things, like they've gotten significantly further along in terms of I can provision stuff really well, I can do multi-tenancy, I can do self-service. Is it, you know, is it still hard? Yeah. Because those things are hard to do, but there's been significant progress there. I don't, you know, I still look for kind of that, that killer application, that sort of, you know, lighthouse use case of, hybrid applications, you know, between data center and between cloud. I think, you know, we see some stuff where, you know, backup is a part of it. So you use the cloud for storage, maybe you use the cloud for certain kinds of resiliency, especially on maybe front end load balancing and stuff. But I think, you know, I think what we get into is, this being hung up on hybrid cloud or multi-cloud as a term and go like, "Look, what are you trying to measure? Are you trying to measure, you know, efficiency of of of IT usage? Are you trying to measure how quickly can I give these business, you know, these application teams that are part of a line of business resources that they need?" I think if we start measuring that way, we would look at, you know, you'd go, "Wow, it used to be weeks and months. Now we got rid of these boards that have to review everything every time I want to do a change management type of thing." We've seen a lot more self-service. I think those are the things we want to measure on. And then to your point of, you know, where does, where do these Supercloud applications fit in? I think there are a bunch of instances where you go, "Look, I have a, you know, global application, I have a thing that has to span multiple regions." That's where the Supercloud concept really comes into play. We used to do it in the data center, right? We'd had all sorts of technologies to help with that, I think you can now start to do it in the cloud. >> You know, one of the other things, trying to understand, your thoughts on this, do you think that you, you again have talked about this, like I'm with you. It's like, how is it that Google's losing, you know, 3 billion dollars a year, whatever. I mean, because when you go back and look at Amazon, when they were at that level of revenue where Google is today, they were making money, you know, and they were actually growing faster, by the way. So it's kind of interesting what's happened with Google. But, the reason I bring that up is, trying to understand if you think the hyperscalers will ever be motivated to create standards across clouds, and that may be a play for Google. I mean, obviously with Kubernetes it was like a Hail Mary and kind of made them relevant. Where would Google be without Kubernetes? But then did it achieve the objectives? We could have that conversation some other time, but do you think the hyperscalers will actually say, "Okay, we're going to lean in and create these standards across clouds." Because customers would love that, I would think, but it would sub-optimize their competitive advantage. What are your thoughts? >> I think, you know, on the surface, I would say they, they probably aren't. I think if you asked 'em the question, they would say, "Well, you know, first and foremost, you know, we do deliver standards, so we deliver a, you know, standard SQL interface or a SQL you know, or a standard Kubernetes API or whatever. So, in that, from that perspective, you know, we're not locking you into, you know, an Amazon specific database, or a Google specific database." You, you can argue about that, but I think to a certain extent, like they've been very good about, "Hey, we're going to adopt the standards that people want." A lot of times the open source standards. I think the problem is, let's say they did come up with a standard for it. I think you still have the problem of the costs of migration and you know, the longer you've, I think their bet is basically the longer you've been in some cloud. And again, the more data you sort of compile there, the data gravity concept, there's just going to be a natural thing that says, okay, the hurdle to get over to say, "Look, we want to move this to another cloud", becomes so cost prohibitive that they don't really have to worry about, you know, oh, I'm going to get into a war of standards. And so far I think they sort of realize like that's the flywheel that the cloud creates. And you know, unless they want to get into a world where they just cut bandwidth costs, like it just kind of won't happen. You know, I think we've even seen, and you know, the one example I'll use, and I forget the name of it off the top of my head, but there's a, there's a Google service. I think it's like BigQuery external or something along those lines, that allows you to say, "Look, you can use BigQuery against like S3 buckets and against other stuff." And so I think the cloud providers have kind of figured out, I'm never going to get the application out of that other guy's cloud or you know, the other cloud. But maybe I'm going to have to figure out some interesting ways to sort of work with it. And, you know, it's a little bit, it's a little janky, but that might be, you know, a moderate step that sort of gets customers where they want to be. >> Yeah. Or you know, it'd be interesting if you ever see AWS for example, running its database in other clouds, you started, even Oracle is doing that with, with with Azure, which is a form of Supercloud. My last question for you is, I want to get you thinking about sort of how the future plays out. You know, think about some of the companies that we've put forth this Supercloud, and by the way, this has been a criticism of the concept. Charles Fitzer, "Everything is Supercloud!" Which if true would defeat the purpose of course. >> Right. >> And so right with the community effort, we really tried to put some guardrails down on the essential characteristics, the deployment models, you know, so for example, running across multiple clouds with a purpose build pass, creating a common experience, metadata intelligence that solves a specific problem. I mean, the example I often use is Snowflake's governed data sharing. But yeah, Snowflake, Databricks, CloudFlare, Cohesity, you know, I just mentioned Oracle and Azure, these and others, they certainly claim to have that common experience across clouds. But my question is, again, I come back to, do customers need this capability? You know, is Mono Cloud the way to solve that problem? What's your, what are your thoughts on how this plays out in the future of, I guess, PAs, apps and cloud? >> Yeah, I think a couple of things. So, from a technology perspective, I think, you know, the companies you name, the services you've named, have sort of proven that the concept is viable and it's viable at a reasonable size, right? These aren't completely niche businesses, right? They're multi-billion dollar businesses. So, I think there's a subset of applications that, you know, maybe a a bigger than a niche set of applications that are going to use these types of things. A lot of what you talked about is very data centric, and that's, that's fine. That's that layer is, figuring that out. I think we'll see messaging types of services, so like Derek Hallison's, Caya Company runs a, sort of a Supercloud for messaging applications. So I think there'll be places where it makes a ton of sense. I think, the thing that I'm not sure about, and because again, we've been now 10 plus years of sort of super low, you know, interest rates in terms of being able to do things, is a lot of these things come out of research that have been done previously. Then they get turned into maybe somewhat of an open source project, and then they can become something. You know, will we see as much investment into the next Snowflake if, you know, the interest rates are three or four times that they used to be, do we, do we see VCs doing it? So that's the part that worries me a little bit, is I think we've seen what's possible. I think, you know, we've seen companies like what those services are. I think I read yesterday Snowflake was saying like, their biggest customers are growing at 30, like 50 or 60%. Like the, value they get out of it is becoming exponential. And it's just a matter of like, will the economics allow the next big thing to happen? Because some of these things are pretty, pretty costly, you know, expensive to get started. So I'm bullish on the idea. I don't know that it becomes, I think it's okay that it's still sort of, you know, niche plus, plus in terms of the size of it. Because, you know, if we think about all of IT it's still, you know, even microservices is a small part of bigger things. But I'm still really bullish on the idea. I like that it's been proven. I'm a little wary, like a lot of people have the economics of, you know, what might slow things down a little bit. But yeah, I, think the future is going to involve Supercloud somewhere, whatever people end up calling it. And you and I discussed that. (laughs) But I don't, I don't think it goes away. I don't think it's, I don't think it's a fad. I think it is something that people see tremendous value and it's just, it's got to be, you know, for what you're trying to do, your application specific thing. >> You're making a great point on the funding of innovation and we're entering a new era of public policy as well. R and D tax credit is now is shifting. >> Yeah. >> You know, you're going to have to capitalize that over five years now. And that's something that goes back to the 1950s and many people would argue that's at least in part what has helped the United States be so, you know, competitive in tech. But Brian, always great to talk to you. Thanks so much for participating in the program. Great to see you. >> Thanks Dave, appreciate it. Good luck with the rest of the show. >> Thank you. All right, this is Dave Vellante for John Furrier, the entire Cube community. Stay tuned for more content from Supercloud2.