>> Well, thank you, Gary. Well, you know, reasonable people could debate when the so-called big data era started. But for me it was in the fall of 2010 when I was sleepwalking through this conference in Dallas. And the conference was focused on data being a liability. And the whole conversation was about, how do you mitigate the risks of things like work in process and smoking-gun emails. I got a call from my business partner, John Fard, he said to me, "get to New York and come and see the future of data. We're doing theCUBE at Hadoop World tomorrow." I subsequently I canceled about a dozen meetings that I had scheduled for the week. And with only one exception, every one of the folks I was scheduled to meet said, "what's a Hadoop?" Well, I flew through an ice storm across country. I got to the New York Hilton around 3:00 AM, and I met John in the Dark Bar. If any of you remember that little facility. And I caught a little shut eye. And then the next day I met some of the most interesting people in tech during that time. They were thinking a lot differently than we were used to. They looked at data through a prism of value. And they were finding new ways to do things like deal with fraud, they were building out social networks, they were finding novel marketing vectors and identifying new investment strategies. The other thing they were doing is, they were taking these little tiny bits of code and bring it to really large sets of data. And they were doing things that I hadn't really heard of like no schema-on-write. And they were transforming their organizations by looking at data not as a liability, but as a monetization opportunity. And that opened my eyes and theCUBE, like a lot of others bet its business on data. Now over the past decade, customers have built up infrastructure and have been accommodating a lot of different use cases. Things like offloading ETL, data protection, mining data, analyzing data, visualizing. And as you know, you no doubt realize this was at a time when the cloud was, you know, really kind of nascent. And it was really about startups and experimentation. But today, we've evolved from the wild west of 2010, and many of these customers they're leveraging the cloud for of course, ease of use and flexibility it brings, but also they're finding out it brings complexity and risk. I want to tell you a quick story. Recently it was interviewing a CIO in theCUBE and he said to me, "if you just shove all your workloads into the cloud, you might get some benefit, but you're also going to miss the forest to the trees. You have to change your operating model and expand your mind as to what is cloud and create a cloud light experience that spans your on premises, workloads, multiple public clouds, and even the edge. And you have to re-imagine your business and the possibilities that this new architecture this new platform can bring." So we're going to talk about some of this today in a little bit more detail and specifically how we can better navigate the data storm. And what's the role of hybrid cloud. I'm really excited to have two great guests. Manish Dasaur is the managing director in the North America lead for analytics and artificial intelligence at Accenture. Anupam Singh is the chief customer officer for Cloudera. Gentlemen, welcome to theCUBE, great to see you. >> Hi Dave good to see you again. >> All right, guys, Anupam and Manish, you heard my little monologue upfront Anupam we'll start with you. What would you? Anything you'd add, amend, emphasize? You know, share a quick story. >> Yeah, Dave thank you for that introduction. It takes me back to the days when I was an article employee and went to this 14 people meet up. Just a couple of pizza talking about this thing called Hadoop. And I'm just amazed to see that today we are now at 2000 customers, who are using petabytes of data to make extremely critical decisions. Reminds me of the fact that this week, a lot of our customers are busy thinking about elections and what effect it would have on their data pipeline. Will it be more data? Will it be more stressful? So, totally agree with you. And also agree that cloud, is almost still in early days in times of the culture of IT on how to use the cloud. And I'm sure we'll talk about that today in greater detail. >> Yeah most definitely Manish I wonder if we could get your perspective on this. I mean, back when Anupam was at Oracle you'd shove a bunch of, you know, data, maybe you could attach a big honking disc drive, you'd buy some Oracle licenses, you know, it was a Unix box. Everything went into this, you know, this God box and then things changed quite dramatically, which was awesome, but also complex. And you guys have been there from the beginning. What's your perspective on all this? >> Yeah, it's been fascinating just to watch the market and the technology evolve. And I think the urgency to innovate is really just getting started. We're seeing companies drive growth from 20% in cloud today, to 80% cloud in the next few years. And I think the emergence of capabilities like hybrid cloud, we really get upfront a lot of flexibility for companies who need the ability to keep some data in a private setting, but be able to share the rest of the data in a public setting. I think we're just starting to scratch the surface of it. >> So let's talk a little bit about what is a hybrid cloud Anupam I wonder if you could take this one let's start with you and then Manish we come back to you and to get the customer perspective as well. I mean, it is a lot of things to a lot of people, but what is it? Why do we need it? And you know, what's the value? >> Yeah, I could speak poetic about Kubernetes and containers et cetera. But given that, you know, we talk to customers a lot, all three of us from the customer's perspective, hybrid cloud is a lot about collaboration and ease of procurement. A lot of our customers, whether they're in healthcare, banking or telco, are being asked to make the data available to regulatory authority, to subsidiaries outside of their geography. When you need that data to be available in other settings, taking a from on-prem and making it available in public cloud, enables extreme collaboration, extreme shared data experience if you will, inside the company. So we think about hybrid like that. >> Manish anything you'd add? How are your customers thinking about it? >> I mean, in a very simple way, it's a structure that where we are allowing mixed computing storage and service environments that's made of on-prem structures, private cloud structures, and public cloud structures. We're often calling it multicloud or mixcloud. And I think the really big advantage is, this model of cloud computing is enabling our clients to gain the benefits of public cloud setting, while maintaining your own private cloud for sensitive and mission critical and highly regulated computing services. That's also allowing our clients and organizations to leverage the pay-as-you-go model, which is really quite impressive and attractive to them because then they can scale their investments accordingly. Clients can combine one or more public cloud providers together in a private cloud, multicloud platform. The cloud can operate independently of each other, communicate over an encrypted connection. This dynamic solution offers a lot of flexibility and scalability which I think is really important to our clients. >> So Manish I wonder if we would stay there. How do they, how do your customers decide? How do you help them decide, you know, what the right mix is? What the equilibrium is? How much should it be in on-prem? How much should be in public or across clouds? Or, you know, eventually, well the edge will I guess decide for us. But, how do you go through, what are the decision points there? >> Yeah, I think that's a great question Dave. I would say there's several factors to consider when developing a cloud strategy that's the right strategy for you. Some of the factors that come to my mind when contemplating it, one would be security. Are there data sets that are highly sensitive that you don't want leaving the premise, versus data sets that need to be in a more shareable solution. Another factor I'd consider is speed and flexibility. Is there a need to stand up and stand down capabilities based on the seasonality of the business or some short-term demands? Is there a need to add and remove scale from the infrastructure and that quick pivot and that quick reaction is another factor they should consider. The third one I'd probably put out there is cost. Large data sets and large computing capacities often much more scalable and cost effective than a cloud infrastructure so there's lots of advantages to think through there. And maybe lastly I'd share is the native services. A lot of the cloud providers enable a set of native services for ingestion, for processing, of modeling, for machine learning, that organizations can really take advantage of. I would say if you're contemplating your strategy right now, my coaching would be, get help. It's a team sport. So definitely leverage your partners and think through the pros and cons of the strategy. Establish a primary hyperscaler, I think that's going to be super key and maximize your value through optimizing the workload, the data placement and really scaling the running operations. And lastly, maybe Dave move quickly right? Each day that you wait, you're incurring technical debt in your legacy environment, that's going to increase the cost and barrier to entry when moving to the new cloud hybrid driver. >> Thank you for that. Anupam I wonder if we could talk a little bit about the business impact. I mean, in the early days of big data, yes, it was a heavy lift, but it was really transformative. When you go to hybrid cloud, is it really about governance and compliance and security and getting the right mix in terms of latency? Are there other, you know, business impacts that are potentially as transformative as we saw in the early days? What are your thoughts on that? >> Absolutely. It's the other business impacts that are interesting. And you know, Dave, let's say you're in the line of business and I come to you and say, oh, there's cost, there's all these other security governance benefits. It doesn't ring the bell for you. But if I say, Dave used to wait 32 weeks, 32 weeks to procure hardware and install software, but I can give you the same thing in 30 minutes. It's literally that transformative, right? Even on-prem, if I use cloud native technology, I can give something today within days versus weeks. So we have banks, we have a bank in Ohio that would take 32 weeks to rack up a 42 node server. Yes, it's very powerful, you have 42 nodes on it, 42 things stacked on it, but still it's taking too much time. So when you get cloud native technologies in your data center, you start behaving like the cloud and you're responsive to the business. The responsiveness is very important. >> That's a great point. I mean, in fact, you know, there's always this debate about is the cloud public cloud probably cost more expensive? Is it more expensive to rent than it is to own? And you get debates back and forth based on your perspective. But I think at the end of the day, what, Anupam you just talked about, it may oftentimes could dwarf, you know, any cost factors, if you can actually, you know, move that fast. Now cost is always a consideration. But I want to talk about the migration path if we can Manish. Where do, how should customers think about migrating to the cloud migration's a, an evil word. How should they think about migrating to the cloud? What's the strategy there? Where should they start? >> No I think you should start with kind of a use case in mind. I think you should start with a particular data set in mind as well. I think starting with what you're really seeking to achieve from a business value perspective is always the right lens in my mind. This is the decade of time technology and cloud to the fitness value, right? So if you start with, I'm seeking to make a dramatic upsell or dramatic change to my top line or bottom line, start with the use case in mind and migrate the data sets and elements that are relevant to that use case, relevant to that value, relevant to that unlock that you're trying to create, that I think is the way to prioritize it. Most of our clients are going to have tons and tons of data in their legacy environment. I don't think the right way to start is to start with a strategy that's going to be focused on migrating all of that. I think the strategy is start with the prioritized items that are tied to the specific value or the use case you're seeking to drive and focus your transformation and your migration on that. >> So guys I've been around a long time in this business and been an observer for awhile. And back in the mainframe days, we used to have a joke called CTAM. When we talk about moving data, it was called the Chevy truck access method. So I want to ask you Anupam, how do you move the data? Do you, it's like an Einstein saying, right? Move as much data as you need to, but no more. So what's going on in that front? what's happening with data movement, and, you know, do you have to make changes to the applications when you move data to the cloud? >> So there's two design patterns, but I love your service story because you know, when you have a 30 petabyte system and you tell the customer, hey, just make a copy of the data and everything will be fine. That will take you one and a half years to make the copies aligned with each other. Instead, what we are seeing is the biggest magic is workload analysis. You analyze the workload, you analyze the behavior of the users, and say so let's say Dave runs dashboards that are very complicated and Manish waits for compute when Dave is running his dashboard. If you're able to gather that information, you can actually take some of the noise out of the system. So you take selected sets of hot data, and you move it to public cloud, process it in public cloud maybe even bring it back. Sounds like science fiction, but the good news is you don't need a Chevy to take all that data into public cloud. It's a small amount of data. That's one reason the other pattern that we have seen is, let's say Manish needs something as a data scientist. And he needs some really specific type of GPUs that are only available in the cloud. So you pull the data sets out that Manish needs so that he can get the new silicone, the new library in the cloud. Those are the two patterns that if you have a new type of compute requirement, you go to public cloud, or if you have a really noisy tenant, you take the hot data out into public cloud and process it there. Does that make sense? >> Yeah it does and it sort of sets up this notion I was sort of describing upfront that the cloud is not just, you know, the public cloud, it's the spans on-prem and multicloud and even the edge. And it seems to me that you've got a metadata opportunity I'll call it and a challenge as well. I mean, there's got to be a lot of R and D going on right now. You hear people talking about cloud native and I wonder on Anupam if you could stay on that, I mean, what's your sense as to how, what the journey is going to look like? I mean, we're not going to get there overnight. People have laid out a vision of this sort of expanding cloud and I'm saying it's a metadata opportunity, but I, you know, how do you, the system has to know what workload to put where based on a lot of those factors that you guys were talking about. The governance, the laws of the land, the latency issues, the cost issues is, you know, how is the industry Anupam sort of approaching this problem and solving this problem? >> I think the biggest thing is to reflect all your security governance across every cloud, as well as on-prem. So let's say, you know, a particular user named Manish cannot access financial data, revenue data. It's important that that data as it goes around the cloud, if it gets copied from on-prem to the cloud, it should carry that quality with it. A big danger is you copy it into some optic storage, and you're absolutely right Dave metadata is the goal there. If you copy the data into an object storage and you lose all metadata, you lose all security, you lose all authorization. So we have invested heavily in something called shared data experience. Which reflects policies from on-prem all the way to the cloud and back. We've seen customers needing to invest in that, but some customers went all hog on the cloud and they realize that putting data just in these buckets of optic storage, you lose all the metadata, and then you're exposing yourself to some breach and security issues. >> Manish I wonder if we could talk about, thank you for that Anupam. Manish I wonder if we could talk about, you know, I've imagined a project, okay? Wherever I am in my journey, maybe you can pick your sort of sweet spot in the market today. You know, what's the fat middle if you will. What does a project look like when I'm migrating to the cloud? I mean, what are some of the, who are the stakeholders? What are some of the outer scope maybe expectations that I better be thinking about? What kind of timeframe? How should I tackle this and so it's not like a, you know, a big, giant expensive? Can I take it in pieces? What's the state-of-the-art of a project look like today? >> Yeah, lots of thoughts come to mind, Dave, when you ask that question. So there's lots to pack. As far as who the buyer is or what the project is for, this is out of migration is directly relevant to every officer in the C-suite in my mind. It's very relevant for the CIO and CTO obviously it's going to be their infrastructure of the future, and certainly something that they're going to need to migrate to. It's very important for the CFO as well. These things require a significant migration and a significant investment from enterprises, different kind of position there. And it's very relevant all the way up to the CEO. Because if you get it right, the truly the power it unlocks is illuminates parts of your business that allow you to capture more value, capture a higher share of wallet, allows you to pivot. A lot of our clients right now are making a pivot from going from a products organization to an as a service organization and really using the capabilities of the cloud to make that pivot happen. So it's really relevant kind of across the C-suite. As far as what a typical program looks like, I always coach my clients just like I said, to start with the value case in mind. So typically, what I'll ask them to do is kind of prioritize their top three or five use cases that they really want to drive, and then we'll land a project team that will help them make that migration and really scale out data and analytics on the cloud that are focused on those use cases. >> Great, thank you for that. I'm glad you mentioned the shift in the mindset from product to as a service. We're seeing that across the board now, even infrastructure players are jumping on the bandwagon and borrowing some sort of best practices from the SaaS vendors. And I wanted to ask you guys about, I mean, as you move to the cloud, one of the other things that strikes me is that you actually get greater scale, but there's a broader ecosystem as well. So we're kind of moving from a product centric world and with SaaS we've got this sort of platform centric, and now it seems like ecosystems are really where the innovation is coming from. I wonder if you guys could comment on that, maybe Anupam you could start. >> Yeah, many of our customers as I said right? Are all about sharing data with more and more lines of businesses. So whenever we talk to our CXO partners, our CRO partners, they are being asked to open up the big data system to more tenants. The fear is, of course, if you add more tenants to a system, it could get, you know, the operational actually might get violated. So I think that's a very important part as more and more collaboration across the company, more and more collaboration across industries. So we have customers who create sandboxes. These are healthcare customers who create sandbox environments for other pharma companies to come in and look at clinical trial data. In that case, you need to be able to create these fenced environments that can be run in public cloud, but with the same security that you expect up. >> Yeah thank you. So Manish this is your wheelhouse as Accenture. You guys are one of the top, you know, two or three or four organizations in the world in terms of dealing with complexity, you've got deep industry expertise, and it seems like some of these ecosystems as Anupam was just sort of describing it in a form are around industries, whether it's healthcare, government, financial services and the like. Maybe your thoughts on the power of ecosystems versus the, you know, the power of many versus the resources of one. >> Yeah, listen, I always talk about this is a team sport right? And it's not about doing it alone. It's about developing as ecosystem partners and really leveraging the power of that collective group. And I've been for as my clients to start thinking about, you know, the key thing you want to think about is how you migrate to becoming a data driven enterprise. And in order for you to get there, you're going to need ecosystem partners to go along the journey with you, to help you drive that innovation. You're going to need to adopt a pervasive mindset to data and democratization of that data everywhere in your enterprise. And you're going to need to refocus your decision-making based on that data, right? So I think partner ecosystem partnerships are here to stay. I think what we're going to see Dave is, you know, at the beginning of the maturity cycle, you're going to see the ecosystem expand with lots of different players and technologies kind of focused on industry. And then I think you'll get to a point where it starts to mature and starts to consolidate as ecosystem partners start to join together through acquisitions and mergers and things like that. So I think ecosystem is just starting to change. I think the key message that I would give to our clients is take advantage of that. There's too much complexity for any one person to kind of navigate through on your own. It's a team sport, so take advantage of all the partnerships you can create. >> Well, Manish one of the things you just said that it kind of reminds me, you said data data-driven, you know, organizations and, you know, if you look at the pre-COVID narrative around digital transformation, certainly there was a lot of digital transformation going on, but there was a lot of complacency too. I talked to a lot of folks, companies that say, "you know, we're doing pretty well, our banks kicking butt right now, we're making a ton of money." Or you know, all that stuff that's kind of not on my watch. I'll be retired before then. And then it was the old, "if it ain't broke, don't fix it." And then COVID breaks everything. And now if you're not digital, you're out of business. And so Anupam I'll start with you. I mean, to build a data-driven culture, what does that mean? That means putting data at the center of your organization, as opposed to around in stove pipes. And this, again, we talked about this, it sort of started in there before even the early parts of last decade. And so it seems that there's cultural aspects there's obviously technology, but there's skillsets, there's processes, you've got a data lifecycle and a data, what I sometimes call a data pipeline, meaning an end to end cycle. And organizations are having to rethink really putting data at the core. What are you seeing? And specifically as it relates to this notion of data-driven organization and data culture, what's working? >> Yeah three favorite stories, and you're a 100% right. Digital transformation has been hyperaccelerated with COVID right? So our telco customers for example, you know, Manish had some technical problems with bandwidth just 10 minutes ago. Most likely is going to call his ISP. The ISP will most likely load up a dashboard in his zip code and the reason it gives me stress, this entire story is because most likely it's starting on a big data system that has to collect data every 15 minutes, and make it available. Because you'll have a very angry Manish on the other end, if you can't explain when is the internet coming back, right? So, as you said this is accelerated. Our telco providers, our telco customers ability to ingest data, because they have to get it in 15 minute increments, not in 24 hour increments. So that's one. On the banking sector what we have seen is uncertainty has created more needs for data. So next week is going to be very uncertain all of us know elections are upcoming. We have customers who are preparing for that additional variable capacity, elastic capacity, so that if investment bankers start running hundreds and thousands of reports, they better be ready. So it's changing the culture at a very fundamental level, right? And my last story is healthcare. You're running clinical trials, but everybody wants access to the data. Your partners, the government wants access to the data, manufacturers wants access to the data. So again, you have to actualize digital transformation on how do you share very sensitive, private healthcare data without violating any policy. But you have to do it quick. That's what COVID has started. >> Thank you for that. So I want to come back to hybrid cloud. I know a lot of people in the audience are, want to learn more about that. And they have a mandate really to go to cloud generally but hybrid specifically. So Manish I wonder if you could share with us, maybe there's some challenges, I mean what's the dark side of hybrid. What should people be thinking about that they, you know, they don't want to venture into, you know, this way, they want to go that way. What are some of the challenges that you're seeing with customers? And how are they mitigating them? >> Yeah, Dave it's a great question. I think there's a few items that I would coach my clients to prioritize and really get right when thinking about making the migration happen. First of all, I would say integration. Between your private and public components that can be complex, it can be challenging. It can be complicated based on the data itself, the organizational structure of the company, the number of touches and authors we have on that data and several other factors. So I think it's really important to get this integration right, with some clear accountabilities build automation where you can and really establish some consistent governance that allows you to maintain these assets. The second one I would say is security. When it comes to hybrid cloud management, any transfers of data you need to handle the strict policies and procedures, especially in industries where that's really relevant like healthcare and financial services. So using these policies in a way that's consistent across your environment and really well understood with anyone who's touching your environment is really important. And the third I would say is cost management. All the executives that I talk about have to have a cost management angle to it. Cloud migration provides ample opportunities for cost reduction. However many migration projects can go over budget when all the costs aren't factored in, right? So your cloud vendors. You've got to be mindful of kind of the charges on accessing on premise applications and scaling costs that maybe need to be budgeted for and where if possible anticipated and really plan for. >> Excellent. So Anupam I wonder if we could go a little deeper on, we talked a little bit about this, but kind of what you put where, which workloads. What are you seeing? I mean, how are people making the choice? Are they saying, okay, this cloud is good for analytics. This cloud is good. Well, I'm a customer of their software so I'm going to use this cloud or this one is the best infrastructure and they got, you know, the most features. How are people deciding really what to put where? Or is it, "hey, I don't want to be locked in to one cloud. I want to spread my risk around. What are you seeing specifically? >> I think the biggest thing is just to echo what Manish said. Is business comes in and as a complaint. So most projects that we see on digital transformation and on public cloud adoption is because businesses complaining about something. It's not architectural goodness, it is not for just innovation for innovation's sake. So, the biggest thing that we see is what we call noisy neighbors. A lot of dashboards, you know, because business has become so intense, click, click, click, click, you're actually putting a lot of load on the system. So isolating noisy neighbors into a cloud is one of the biggest patterns that you've seen. It takes the noisiest tenant on your cluster, noisiest workload and you take them to public cloud. The other one is data scientists. They want new libraries, they want to work with GPU's. And to your point Dave, that's where you select a particular cloud. Let's say there's a particular type silicone that is available only in that cloud. That GPU is available only in that cloud or that particular artificial intelligence library is available only in a particular cloud. That's when customers say, Hey miss, they decided, why don't you go to this cloud while the main workload might still be running on them, right? That's the two patterns that we are seeing. >> Right thank you. And I wonder if we can end on a little bit of looking to the future. Maybe how this is all going to evolve over the next several years. I mean, I like to look at it at a spectrum at a journey. It's not going to all come at once. I do think the edge is part of that. But it feels like today we've got, you know, multi clouds are loosely coupled and hybrid is also loosely coupled, but we're moving very quickly to a much more integrated, I think we Manish you talked about integration. Where you've got state, you've got the control plane, you've got the data plane. And all this stuff is really becoming native to the respective clouds and even bring that on-prem and you've got now hybrid applications and much much tighter integration and build this, build out of this massively distributed, maybe going from it's a hyper-converged to hyper-distributed again including the edge. So I wonder Manish we could start with you. How are your customers thinking about the future? How are they thinking about, you know, making sure that they're not going down a path where that's going to, they're going to incur a lot of technical debt? I know there's sort of infrastructure is code and containers and that seems it seems necessary, but insufficient there's a lot of talk about, well maybe we start with a functions based or a serverless architecture. There's some bets that have to be made to make sure that you can future proof yourself. What are you recommending there Manish? >> Yeah, I, listen I think we're just getting started in this journey. And like I said, it's really exciting time and I think there's a lot of evolution in front of us that we're going to see. I, you know, I think for example, I think we're going to see hybrid technologies evolve from public and private thinking to dedicated and shared thinking instead. And I think we're going to see advances in capabilities around automation and computer federation and evolution of consumption models of that data. But I think we've got a lot of kind of technology modifications and enhancements ahead of us. As far as companies and how they future proof themselves. I would offer the following. First of all, I think it's a time for action, right? So I would encourage all my class to take action now. Every day spent in legacy adds to the technical debt that you're going to incur, and it increases your barrier to entry. The second one would be move with agility and flexibility. That's the underlying value of hybrid cloud structures. So organizations really need to learn how to operate in that way and take advantage of that agility and that flexibility. We've talked about creating partnerships in ecosystems I think that's going to be really important. Gathering partners and thought leaders to help you navigate through that complexity. And lastly I would say monetizing your data. Making a value led approach to how you viewed your data assets and force a function where each decision in your enterprise is tied to the value that it creates and is backed by the data that supports it. And I think if you get those things right, the technology and the infrastructure will serve. >> Excellent and Anupam why don't you bring us home, I mean you've got a unique combination of technical acumen and business knowledge. How do you see this evolving over the next three to five years? >> Oh, thank you Dave. So technically speaking, adoption of containers is going to steadily make sure that you're not aware even of what cloud you're running on that day. So the multicloud will not be a requirement even, it will just be obviated when you have that abstraction there. Contrarily, it's going to be a bigger challenge. I would echo what Manish said start today, especially on the cultural side. It is great that you don't have to procure hardware anymore, but that also means that many of us don't know what our cloud bill is going to be next month. It is a very scary feeling for your CIO and your CFO that you don't know how much you're going to to spend next month forget next year, right? So you have to be agile in your financial planning as much you have to be agile in your technical planning. And finally I think you hit on it. Ecosystems are what makes data great. And so you have to start from day one that if I am going on this cloud solution, is the data shareable? Am I able to create an ecosystem around that data? Because without that, it's just somebody running a report may or may not have value to the business. >> That's awesome, guys. Thanks so much for a great conversation. We're at a time and I want to wish everybody a terrific event. Let me now hand it back to Vanita. She's going to take you through the rest of the day. This is Dave Vellante for theCUBE, thanks. (smooth calm music)