>> Well, hello everybody, John Walls here on theCUBE and continuing our coverage. So splunk.com for 21, you know, we talk about big data these days, you realize the importance of speed, right? We all get that, but certainly Formula One Racing understands speed and big data, a really neat marriage there. And with us to talk about that is James Hodge, who was the global vice president and chief strategy officer international at Splunk. James, good to see it today. Thanks for joining us here on theCUBE. >> Thank you, John. Thank you for having me and yeah, the speed of McLaren. Like I'm, I'm all for it today. >> Absolutely. And I find it interesting too, that, that you were telling me before we started the interview that you've been in Splunk going on nine years now. And you remember being at splunk.com, you know, back in the past other years and watching theCUBE and here you are! you made it. >> I know, I think it's incredible. I love watching you guys every single year and kind of the talk that guests. And then more importantly, like it reminds me of conf for every time we see theCUBE, no matter where you are, it reminds me of like this magical week there's dot com for us. >> Well, excellent. I'm glad that we could be a part of it at once again and glad you're a part of it here on theCUBE. Let's talk about McLaren now and the partnership, obviously on the racing side and the e-sports side, which is certainly growing in popularity and in demand. So just first off characterize for our audience, that relationship between Splunk and McLaren. >> Well, so we started the relationship almost two years ago. And for us it was McLaren as a brand. If you think about where they were, they recently, I think it's September a Monza. They got a victory P1 and P2. It was over 3200 days since their last victory. So that's a long time to wait. I think of that. There's 3000 days of continual business transformation, trying to get them back up to the grid. And what we found was that ethos, the drive to digital the, the way they're completely changing things, bringing in kind of fluid dynamics, getting people behind the common purpose that really seem to fit the Splunk culture, what we're trying to do and putting data at the heart of things. So kind of Formula One and McLaren, it felt a really natural place to be. And we haven't really looked back since we started at that partnership. It's been a really exciting last kind of 18 months, two years. >> Well, talk a little bit about, about the application here a little bit in terms of data cars, the, the Formula One cars, the F1 cars, they've got hundreds of sensors on them. They're getting, you know, hundreds of thousands or a hundred thousand data points almost instantly, right? I mean, there's this constant processing. So what are those inputs basically? And then how has McLaren putting them to use, and then ultimately, how is Splunk delivering on that from McLaren? >> So I learned quite a lot, you know, I'm, I'm, I been a childhood Formula One fan, and I've learned so much more about F1 over the last kind of couple of years. So it actually starts with the car going out on the track, but anyone that works in the IT function, the car can not go out on track and less monitoring from the car actually is being received by the garage. It's seen as mission critical safety critical. So IT, when you see a car out and you see the race engineer, but that thumbs up the mechanical, the thumbs up IT, get their vote and get to put the thumbs up before the car goes out on track there around about 300 sensors on the car in practice. And there were two sites that run about 120 on race day that gets streamed on a two by two megabits per second, back to the FIA, the regulating body, and then gets streams to the, the garage where they have a 32 unit rack near two of them that have all of their it equipment take that data. They then stream it over the internet over the cloud, back to the technology center in working where 32 race engineers sit in calm conditions to be able to go and start to make decisions on when the car should pit what their strategy should be like to then relate that back to the track side. So you think about that data journey alone, that is way more complicated and what you see on TV, you know, the, the race energy on the pit wall and the driver going around at 300 kilometers an hour. When we look at what Splunk is doing is making sure that is resilient. You know, is the data coming off the car? Is it actually starting to hit the garage when it hits that rack into the garage, other than streaming that back with the right latency back to the working technology center, they're making sure that all of the support decision-making tools there are available, and that's just what we do for them on race weekend. And I'll give you one kind of the more facts about the car. So you start the beginning of the season, they launched the car. The 80% of that car will be different by the end of the season. And so they're in a continual state of development, like constantly developing to do that. So they're moving much more to things like computational fluid dynamics applications before the move to wind tunnel that relies on digital infrastructure to be able to go and accelerate that journey and be able to go make those assumptions. That's a Splunk is becoming the kind of underpinning of to making sure those mission critical applications and systems are online. And that's kind of just scratching the surface of kind of the journey with McLaren. >> Yeah. So, so what would be an example then maybe on race day, what's a stake race day of an input that comes in and then mission control, which I find fascinating, right? You've got 32 different individuals processing this input and then feeding their, their insights back. Right. And so adjustments are being made on the fly very much all data-driven what would be an example of, of an actual application of some information that came in that was quickly, you know, recorded, noted, and then acted upon that then resulted in an improved performance? >> Well, the most important one is pit stop strategy. It can be very difficult to overtake on track. So starting to look at when other teams go into the pit lane and when they come out of the, the pit lane is incredibly important because it gives you a choice. Do you stay also in your current set of tires and hope to kind of get through that team and kind of overtake them, or do you start to go into the pits and get your fresh sets of tires to try and take a different strategy? There are three people in mission control that have full authority to go and make a Pit lane call. And I think like the thing that really resonated for me from learning about McLaren, the technology is amazing, but it's the organizational constructs on how they turn data into an action is really important. People with the right knowledge and access to the data, have the authority to make a call. It's not the team principle, it's not the person on the pit wall is the person with the most amount of knowledge is authorized and kind of, it's an open kind of forum to go and make those decisions. If you see something wrong, you are just as likely to be able to put your hand up and say, something's wrong here. This is my, my decision than anyone else. And so when we think about all these organizations that are trying to transform the business, we can learn a lot from Formula One on how we delegate authority and just think of like technology and data as the beginning of that journey. It's the people in process that F1 is so well. >> We're talking a lot about racing, but of course, McLaren is also getting involved in e-sports. And so people like you like me, we can have that simulated experience to gaming. And I know that Splunk has, is migrating with McLaren in that regard. Right. You know, you're partnering up. So maybe if you could share a little bit more about that, about how you're teaming up with McLaren on the e-sports side, which I'm sure anybody watching this realizes there's a, quite a big market opportunity there right now. >> It's a huge market opportunity is we got McLaren racing has, you know, Formula One, IndyCar and now extreme E and then they have the other branch, which is e-sports so gaming. And one of the things that, you know, you look at gaming, you know, we were talking earlier about Ted Lasso and, you know, the go to the amazing game of football or soccer, depending on kind of what side of the Atlantic you're on. I can go and play something like FIFA, you know, the football game. I can be amazing at that. I have in reality, you know, in real life I have two left feet. I am never going to be good at football however, what we find with e-sports is it makes gaming and racing accessible. I can go and drive the same circuits as Lando Norris and Daniel Ricardo, and I can improve. And I can learn like use data to start to discover different ways. And it's an incredibly expanding exploding industry. And what McLaren have done is they've said, actually, we're going to make a professional racing team, an e-sports team called the McLaren Shadow team. They have this huge competition called the Logitech KeyShot challenge. And when we looked at that, we sort of lost the similarities in what we're trying to achieve. We are quite often starting to merge the physical world and the digital world with our customers. And this was an amazing opportunity to start to do that with the McLaren team. >> So you're creating this really dynamic racing experience, right? That, that, that gives people like me, or like our viewers, the opportunity to get even a better feel for, for the decision-making and the responsiveness of the cars and all that. So again, data, where does that come into play there? Now, What, what kind of inputs are you getting from me as a driver then as an amateur driver? And, and how has that then I guess, how does it express in the game or expressed in, in terms of what's ahead of me to come in a game? >> So actually there are more data points that come out of the F1 2021 Codemasters game than there are in Formula One car, you get a constant stream. So the, the game will actually stream out real telemetry. So I can actually tell your tire pressures from all of your tires. I can see the lateral G-Force longitudinal. G-Force more importantly for probably amateur drivers like you and I, we can see is the tire on asphalt, or is it maybe on graphs? We can actually look at your exact position on track, how much accelerator, you know, steering lock. So we can see everything about that. And that gets pumped out in real time, up to 60 Hertz. So a phenomenal amount of information, what we, when we started the relationship with McLaren, Formula One super excited or about to go racing. And then at Melbourne, there's that iconic moment where one of the McLaren team tested positive and they withdrew from the race. And what we found was, you know, COVID was starting and the Formula One season was put on hold. The FIA created this season and called i can't remember the exact name of it, but basically a replica e-sports gaming F1 series. We're using the game. Some of the real drivers like Lando, heavy gamer was playing in the game and they'd run that the same as race weekends. They brought celebrity drivers in there. And I think my most surreal zoom call I ever was on was with Lando Norris and Pierre Patrick Aubameyang, who was who's the arsenal football captain, who was the guest driver in the series to drive around Monaco and Randy, the head of race strategy as McLaren, trying to coach him on how to go drive the car, what we ended up with data telemetry coming from Splunk. And so Randy could look out here when he pressing the accelerator and the brake pedal. And what was really interesting was Lando was watching how he was entering corners on the video feed and intuitively kind of coming to the same conclusions as Randy. So kind of, you could see that race to intuition versus the real stats, and it was just incredible experience. And it really shows you, you know, racing, you've got that blurring of the physical and the virtual that it's going to be bigger and bigger and bigger. >> So to hear it here, as I understand what you were just saying now, the e-sports racing team actually has more data to adjust its performance and to modify its behaviors, then the real racing team does. Yep. >> Yeah, it completely does. So what we want to be able to do is turn that into action. So how do you do the right car setup? How do you go and do the right practice laps actually have really good practice driver selection. And I think we're just starting to scratch the surface of what really could be done. And the amazing part about this is now think of it more like a digital twin, what we learn on e-sports we can actually say we've learned something really interesting here, and then maybe a low, you know, if we get something wrong, it may be doesn't matter quite as much as maybe getting an analytics wrong on race weekend. >> Right. >> So we can actually start to look and improve through digital and then start to move that support. That's over to kind of race weekend analytics and supporting the team. >> If I could, you know, maybe pun intended here, shift gears a little bit before we run out of time. I mean, you're, you're involved on the business side, you know, you've got, you know, you're in the middle east Africa, right? You've got, you know, quite an international portfolio on your plate. Now let's talk about just some of the data trends there for our viewers here in the U S who maybe aren't as familiar with what's going on overseas, just in terms of, especially post COVID, you know, what, what concerns there are, or, or what direction you're trying to get your clients to, to be taking in terms of getting back to work in terms of, you know, looking at their workforce opportunities and strengths and all those kinds of things. >> I think we've seen a massive shift. I think we've seen that people it's not good enough just to be storing data its how do you go and utilize that data to go and drive your business forwards I think a couple of key terms we're going to see more and more over the next few years is operational resilience and business agility. And I'd make the assertion that operational resilience is the foundation for the business agility. And we can dive into that in a second, but what we're seeing take the Netherlands. For example, we run a survey last year and we found that 87% of the respondents had created new functions to do with data machine learning and AI, as all they're trying to do is go and get more timely data to front line staff to go. And next that the transformation, because what we've really seen through COVID is everything is possible to be digitized and we can experiment and get to market faster. And I think we've just seen in European markets, definitely in Asia Pacific is that the kind of brand loyalty is potentially waning, but what's the kind of loyalty is just to an experience, you know, take a ride hailing app. You know, I get to an airport, I try one ride hailing app. It tells me it's going to be 20 minutes before a taxi arrives. I'm going to go straight to the next app to go and stare. They can do it faster. I want the experience. I don't necessarily want the brand. And we're find that the digital experience by putting data, the forefront of that is really accelerating and actually really encouraging, you know, France, Germany are actually ahead of UK. Let's look, listen, their attitudes and adoption to data. And for our American audience and America, America is more likely, I think it's 72% more likely to have a chief innovation officer than the rest of the world. I think I'm about 64% in EMEA. So America, you are still slightly ahead of us in terms of kind of bringing some of that innovation that. >> I imagine that gap is going to be shrinking though I would think. >> It is massively shrinking. >> So before we, we, we, we are just a little tight on time, but I want to hear about operational resilience and, and just your, your thought that definition, you know, define that for me a little bit, you know, put a little more meat on that bone, if you would, and talk about why, you know, what that is in, in your thinking today and then why that is so important. >> So I think inputting in, in racing, you know, operational resilience is being able to send some response to what is happening around you with people processing technology, to be able to baseline what your processes are and the services you're providing, and be able to understand when something is not performing as it should be, what we're seeing. Things like European Union, in financial services, or at the digital operational resilience act is starting to mandate that businesses have to be operational in resilient service, monitoring fraud, cyber security, and customer experience. And what we see is really operational resilience is the amount of change that can be absorbed before opportunities become risk. So having a stable foundation of operational resilience allows me to become a more agile business because I know my foundation and people can then move and adjust quickly because I have the awareness of my environment and I have the ability to appropriately react to my environment because I've thought about becoming a resilient business with my digital infrastructure is a theme. I think we're going to see in supply chain coming very soon and across all other industries, as we realize digital is our business. Nowadays. >> What's an exciting world. Isn't it, James? That you're, that you're working in right now. >> Oh, I, I love it. You know, you said, you know, eight and an eight and a half years, nine years at Splunk, I'm still smiling. You know, it is like being at the forefront of this diesel wave and being able to help people make action from that. It's an incredible place to be. I, is liberating and yeah, I can't even begin to imagine what's, you know, the opportunities are over the next few years as the world continually evolves. >> Well, every day is a school day, right? >> It is my favorite phrase >> I knew that. >> And it is, James Hodge. Thanks for joining us on theCUBE. Glad to have you on finally, after being on the other side of the camera, it's great to have you on this side. So thanks for making that transition for us. >> Thank you, John. You bet James Hodge joining us here on the cube coverage of splunk.com 21, talking about McLaren racing team speed and Splunk.

(upbeat music) >> Announcer: Live from Vancouver, Canada. It's The Cube covering Openstack Summit, North America, 2018. Brought to you by Red Hat, The Open Stack Foundation, and it's ecosystem partners. >> Welcome back to The Cube's coverage of Openstack Summit 2018 in Vancouver. I'm Stu Miniman with cohost of the week, John Troyer. Happy to welcome back to the program Stephan Fabel, who is the Director of Ubuntu product and development at Canonical. Great to see you. >> Yeah, great to be here, thank you for having me. Alright, so, boy, there's so much going on at this show. We've been talking about doing more things and in more places, is the theme that the Open Stack Foundation put into place, and we had a great conversation with Mark Shuttleworth, and going to dig in a little bit deeper in some of the areas with you. >> Stephan: Okay, absolutely. >> So we have the Cube, and we're go into all of the Kubernetes, Kubeflow, and all those other things that we'll mispronounce how they go. >> Stephan: Yes, yes, absolutely. >> What's your impression of the show first of all? >> Well I think that it's really, you know, there's a consolidation going on, right? I mean, we really have the people who are serious about open infrastructure here, serious about OpenStack. They're serious about Kubenetes. They want to implement, and they want to implement at a speed that fits the agility of their business. They want to really move quick with the obstrain release. I think the time for enterprise hardening delays an inertia there is over. I think people are really looking at the core of OpenStack, that's mature, it's stable, it's time for us to kind of move, get going, get success early, get it soon, then grow. I think most of the enterprise, most of the customers we talk to adopt that notion. >> One of the things that sometimes helps is help us lay out the stack a little bit here because we actually commented that some of the base infrastructure pieces we're not talking as much about because they're kind of mature, but OpenStack very much at the infrastructure level, your compute, storage, and network need to understand. But then we when we start doing things like Kubernetes as well, I can either do or, or on top of, and things like that, so give us your view as to what'd you put, what Canonical's seeing, and what customers-- how you lay out that stack? >> I think you're right, I think there's a little bit of path-finding here that needs to be done on the Kubernetes side, but ultimately, I think it's going to really converge around OpenStack being operative-centric, and operative-friendly, working and operating the infrastructure, scaling that out in a meaningful manner, providing multitenancy to all the different departments. Having Kubernetes be developer-centric and really help to on-board and accelerate the workload that option of the next gen initiatives, right? So, what we see is absolutely a use case for Kubernetes and OpenStack to work perfectly well together, be an extension of each other, possibly also sit next to each other without being too incumbenent there. But I think that ultimately having something like Kubernetes contain a based developer APIs that are providing that orchestration layer are the next thing, and they run just perfectly fine on Canonical OpenStack. >> Yeah, there certainly has been a lot of talk about that here at the show. Let's see, let's go a level above that, things we run on Kubernetes, I wanted to talk a little bit about ML and AI and Kubeflow. It seems like we're, I'd almost say that we're, this is like, if we were a movie, we're in a sequel like AI-5; this time, it's real. I really do see real enterprise applications incorporating these technologies into the workflow for what otherwise might be kind of boring, you know, line of business, can you talk a little bit about where we are in this evolution? >> You mean, John, only since we've been talking about it since the mid-1800s, so yeah. >> I was just about to point that out, I mean, AI's not new, right? We've seen it since about 60 years. It's been around for quite some time. I think that there is an unprecedented amount of sponsorship of new startups in this area, in this space, and there's a reason why this is heating up. I think the reason why ultimately it's there is because we're talking about a scale that's unprecedented, right? We thought the biggest problem we had with devices was going to be the IP addresses running out, and it turns out, that's not true at all, right? At a certain scale, and at a certain distributed nature of your rollout, you're going to have to deal with just such complexity and interaction between the underlying, the under-cloud, the over-cloud, the infrastructure, the developers. How do I roll this out? If I spin up 1000 BMs over here, why am I experiencing dropped calls over there? It's those types of things that need to be self-correlated. They need to be identified, they need to be worked out, so there's a whole operator angle just to be able to cope with that whole scenario. I think there's projects that are out there that are trying to ultimately address that, for example, Acumos (mumbles) Then, there is, of course, the new applications, right? Smart cities to connect to cars, all those car manufacturers who are, right now, faced with the problem: how do I deal with mobile, distributed inference rollout on the edge while still capturing the data continually, train my model, update, then again, distribute out to the edge to get a better experience. How do I catch up to some of the market leaders here that are out there? As the established car manufacturers are going to come and catch up, put more and more miles autonomously on the asphalt, we're going to basically have to deal with a whole lot more of proctization of machine-learning applications that just have to be managed at scale. And so we believe for all certain good company in that belief that having to manage large applications at scale, that containers and Kubernetes is a great way to do that, right? They did that for web apps. They did that for the next generation applications. This is one example where with the right operators in mind, the right CRDs, the right frameworks on top of Kubernetes managed correctly, you are actually in a great position to just go to market with that. >> I wonder if you might have a customer example that might go to walk us through kind of where they are in this discussion, talk to many companies, you know, the whole IOT even pieces were early in this. So what's actually real today, how much is planning, is this years we're talking before some of these really come to fruition? >> So yeah, I can't name a customer, but I can say that every single car manufacturer we're talking to is absolutely interested in solving the operational problem of running machine-learning frameworks as a service, making sure those are up running and up to speed at any given point in time, spin them up in a multitenant fashion, make sure that the GPU enablement is actually done properly at all layers of the virtualization. These are real operational challenges that they're facing today, and they're looking to solve with us. Pick a large car manufacturer you want. >> John: Nice. We're going down to something that I can type on my own keyboard then, and go to GitHub, right? That's one of the places to go where it is run, TensorFlow of machine-learning framework on Kubernetes is Kubeflow, and that little bit yesterday on stage, you want to talk about that maybe? >> Oh, absolutely, yes. That's the core of our current strategy right now. We're looking at Kubeflow as one of the key enablers of machine-learning frameworks as a service on top of Kubernetes, and I think they're a great example because they can really show how that as a service can be implemented on top of a virtualization platform, whether that be KVM, pure KVM, on bare metal, on OpenStack, and actually provide machine-learning frameworks such as TensorFlow, Pipe Torch, Seldon Core. You have all those frameworks being supported, and then basically start mix and matching. I think ultimately it's so interesting to us because the data scientists are really not the ones that are expected to manage all this, right? Yet they are the core of having to interact with it. In the next generation of the workloads, we're talking to PHDs and data scientists that have no interest whatsoever in understanding how all of this works on the back end, right? They just want to know this is where I'm going to submit my artifact that I'm creating, this is how it works in general. Companies pay them a lot of money to do just that, and to just do the model because that's where, until the right model is found, that is exactly where the value is. >> So Stephan, does Canonical go talk to the data scientists, or is there a class of operators who are facilitating the data scientists? >> Yes, we talk to the data scientists who understand their problems, we talk to the operators to understand their problems, and then we work with partners such as Google to try and find solutions to that. >> Great, what kind of conversations are you having here at the show? I can't imagine there's too many of those, great to hear if there are, but where are they? I think everybody here knows containers, very few know Kubernetes, and how far up the stack of building new stuff are they? >> You'd be surprised, I mean, we put this out there, and so far, I want to say the majority of the customer conversations we've had took an AI turn and said, this is what we're trying to do next year, this is what we're trying to do later in the year, this is what we're currently struggling with. So glad you have an approach because otherwise, we would spend a ton of time thinking about this, a ton of time trying to solve this in our own way that then gets us stuck in some deep end that we don't want to be. So, help us understand this, help us pave the way. >> John: Nice, nice. I don't want to leave without talking also about Microcades, that's a Kubernetes snap, you code some clojure download, Can we talk a little bit about that? >> Yeah, glad to. This was an idea that we conceived that came out of this notion of alright, well if I do have, talking to a data scientist, if I do have a data scientist, where does he start? >> Stu: Does Kubernetes have a learning curve to date? >> It does, yeah, it does. So here's the thing, as a developer, you have, what options do you have right when you get started? You can either go out and get a community stood up on one of the public clouds, but what if you're in the plane, right? You don't have a connection, you want to work on your local laptop. Possibly, that laptop also has a GPU, and you're a data scientist and you want to try this out because you know you're going to submit this training job now to a (mumbles) that runs un-prem behind the firewall with a limited training set, right? This is the situation we're talking about. So ultimately, the motivation for creating Microcades was we want to make this very, very equivalent. Now you can deploy Kubeflow on top of Microcades today, and it'll run just fine. You get your TensorBoard, you have Jupyter notebook, and you can do your work, and you can do it in a fashion that will then be compatible to your on-prem and public machine-learning framework. So that was your original motivation for why we went down this road, but then we noticed you know what, this is actually a wider need. People are thinking about local Kubernetes in many different ways. There are a couple of solutions out there. They tend to be cumbersome, or more cumbersome than developers would like it. So we actually said, you know, maybe we should turn this into a more general purpose solution. So hence, Microcades. It works like a snap on your machine, you kick that off, you have Kubernetes API, and under 30 seconds or little longer if your download speed plays a factor here, you enable DNS and you're good to go. >> Stephan, I just want to give you the opportunity, is there anything in the Queens Release that your customers have been specifically waiting for or any other product announcements before we wrap? >> Sure, we're very excited about the Queens Release. We think Queens Release is one of the great examples of the maturity of the code base and really the knot towards the operator, and that, I think was the big challenge beyond the olden days of OpenStack where the operators took a long time for the operators to be heard, and to establish that conversation. We'd like to say and to see that OpenStack Queens has matured in that respect, and we like things like Octavia. We're very exciting about (mumbles) as a service, taking its own life and being treated as a first-class citizen. I think that it was a great decision of the community to get on that road. We're supporting as a part of our distribution. >> Alright, well, appreciate the update. Really fascinating to hear about all, you know, everybody's thinking about it and really starting to move on all the ML and AI stuff. Alright, for John Troyer, I'm Tru Miniman. Lots more coverage here from OpenStack Summit 2018 in Vancouver. Thanks for watching The Cube. (upbeat music)