>> Announcer: From San Francisco, it's theCUBE. Covering VMware Radio 2019. Brought to you by VMware. >> Hi, welcome to theCUBE's exclusive coverage of VMware Radio 2019. Lisa Martin with John Furrier, in San Francisco. This is an internal R&D innovation off site that VMware does, lots of innovation going on here from engineers from all over the globe. We're pleased to welcome Joe Baguley, the CTO from EMEA, from VMware. Joe, welcome to theCUBE. >> Hi. >> So we've been having some great conversations this morning about this tremendous amount of innovation, I mean the potential is massive. Not just from Radio, but from all the other innovation programs that VMware has, really speaks very strongly to the culture of innovation that VMware has had. But of course all this innovation has to be able to be harnessed to deliver what customers need. Talk to us about that, you're in the field, field CTO. What is that connection with the innovation that happens within VMware? How do customers help influence that and vice versa? >> Yeah, I think we're very unique in the structure that we've put around that to drive that innovation over the years. So my job as field CTO is, I call it sort of 50, 50. So 50% is Chief Technology Officer, which is this kind of stuff for Radio and 50% is Chief Talking Officer, which is out with our customers and presenting at conferences, et cetera. But the general remit is connecting R&D in the field. And so for eight years now I've been connecting R&D in the field at VMware, I actually did at my previous company as well. And what we've done is, we've built a series of programs over the years to do that, and one of the biggest ones is the CTO Ambassadors. And so that was, you know, you get to a point, you get to a growth size, I've been here eight years, and suddenly you need someone else to help you because I can't be everywhere. And the original role was, back in the day I was hired to scale Steve Herrod, because Steve Herrod couldn't be in Europe all the time, I was like mini Steve Herrod that could be there when needed. But then eventually I can't be in every European country and our major regions as we get bigger and bigger, and we've grown dramatically. So the CTO Ambassadors is to support that. And that's really, we've got 140 of our top customer facing techies from around the globe in this program called the Ambassadors. And they have to be customer facing, and they have to be individual contributors, so like a pre-sales manager or something doesn't count. They're a massively active community, there's a whole bunch of them here at Radio as well. And their job is really that conduit, that source of information, and also a sounding board, a much shorter range sounding board for R&D. So if R&D want to get a feel of what's going on, they don't have to ask everyone they can bounce off the Ambassadors, which is part of what we do, and that makes it easier. >> So like a filter too, they're also also filtering input from the field, packaging it up for R&D. >> Totally. Yeah, and when you're at an organization of our scale, filtering is really important. Because obviously, you can't have every customer directly talking to every engineer, it's never going to work. (laughs) >> I mean another radio project stay right there, a machine learning based champion CTO to go through all the feedback. >> Yeah, so I started my career, with my previous company doing that, I was the filter. So I'd get a hundred questions a day from various people in the field, and 99 of those I'd bounce right back because I knew the answer. But there was the one that I was like, uh. Then I'd turn around to R&D and ask them. But the great thing was that R&D knew that if I was asking then it was a real question, it wasn't the 99. So the CTO Ambassadors, and what we do in Octo Global field is really a method of scaling that. >> I want to ask you about that because that's a great example of here reputation comes in. Because your reputation is on the line if you go back and pull the fire alarm, if you will, send too many lame requests back, you're going to be lame. So you've got to kind of check, balance there. So that begs the question, how do you do the filtering for the champions that work for you? Is there a high bar? Is there a certain line? Like being a kid, you've got to be this tall to ride the roller coaster. Is there criteria? Is there certification? Take us through the filtering there. >> The Ambassador program is a rotating nomination system. So essentially there's a two year tenure. So what happens is, if you're in the field and you want to be an ambassador, which is a really prestigious thing, then you nominate yourself or get nominated and then people vote on you and you put forward your case, et cetera. Essentially it's a democratic process based on your peers and other people in the company. And then after you're allowed a maximum of two years. Sorry, two tenures so you get four years, if that makes sense, I'm not confusing you. >> John: So term limits? >> Yeah there's term limits, right, we have term limits. And after two terms you have to go out for a year to give someone else a chance because otherwise it will just glub- >> It'll turn into the US government. (laughs) >> But no, it's important to maintain freshness, maintain diversity and all those kind of things. And so it comes back to that filter piece we were talking about before. The reputation is massive, of the CTO Ambassadors. I mean when we started this six years ago as a program, most of R&D were like, who are these Ambassador guys? What value are they going to add? Now, if you're in R&D, one of the best things you can say, if you want to get something done, is what the CTO Ambassador said. I mean, literally it is, you can go and we have- >> John: The routine approach to that. Talk about how you guys add in a new category. So, for instance kubernetes, we saw this years ago when KubeCon was started, theCUBE was there present at the creation of that trend we kind of got it right away. Now Gelsinger and the team sees this as a massive traction layer. So that would be an example, where we need an Ambassador. So do you like just create one or how does that work? >> They create themselves, that's the best thing. So we have an annual conference which is in February, held in Paolo Alto where we all get together along with all the chief technologists, which is the level below me. And the principles, which the most senior field people. So literally the best of the best get together. It's about 200 plus get together for a week. And we are an hour and a half on on one with Pat for example, so Pat's there with all of us in a room. But one of the sessions we do is the shark tank, and there's two of them. One of them is, come up with your really cool, crazy, wacky ideas, and the other one is the acquisition shark tank. So there we get the MNA team, include our E-staff sit in, and the Ambassadors, as teams, will come in and present. We think we should acquire, uh because that's making a big difference. The great thing is, not nine times out of 10 but probably seven times out of 10, the E-staff are going, yeah we know about that, when actually we can't really tell you what's going on but yeah we know about them. But there's the two or three times out of 10 that people are like, oh yeah, so tell me more about them. And it might be a company that's just coming up, it might be 2013 and there's this company called Docker that no one's heard of, but the Ambassadors are shouting about Docker, and saying it's a big, you know. So there's that- >> So white space is too emerging you can see it's a telemetry, literally feedback from the field to direct management on business strategy. >> And our customers are pushing our field in directions faster than maybe R&D get pushed if you know what I mean. >> You guys deserve a lot of credit because Pat Gelsinger was just on this morning with Lisa and me, and we were talking about that. He just came back from the Sales President's club cruise, and one of the comments he said was the sales executive said, hey, who does strategy? Because everything's fitting together beautifully. Which kind of highlights how radiance this all progresses, not like magic, there's a process here, and this kind of points to your job is to fit that pieces in, is that correct? >> Yeah. People always say, as a CTO do you all sit down once a week and talk about strategy? And that's not what you do. There's a hive mind, there's a continual interaction, there's conference calls, there's phone calls, there's meetings, there's get togethers of various different types, groups, and levels. And what happens is there's themes that emerge over that. And so my role specifically, as the EMEA CTO is to represent Europe, Middle East, and Africa's voice in those conversations. And maybe the nuances that we might have around particular product requirements or whatever, to remind people that maybe sit in a bubble in Silicon Valley. >> John: I'm sure you raised your hand on privacy and GDPR? (laughs) >> Just a couple of times, yeah. Yeah, now and again. >> The canary in the coal mine is a really big point that helps companies, if they're not listening to the signals coming in. >> Well you do, and you see a lot. There's a lot of the tech companies that I see, it's often defined as the three bubbles, or your Massimo Re Ferrè, who's now at Amazon. When he was here, did this fantastic blog post talking about the first bubble is Silicon Valley, and the second bubble is North America, and the third bubble is everywhere else. And so you kind of watch these things emerge. And my job is to jump over that pop into the Silicon Valley bubble before something happens and say, no you should be thinking about X, you should think about Y. At an event like Radio I've got a force multiplier because I've got 40 plus Ambassadors with me all popping up at all these little booths you see behind you, and the shows, and the talks. >> And the goal here is not to be a bubble, but to be completely one hive mind. >> And the diversity at VMware just blows my mind, it really does. I think a lot of people comment on it quite often, and in fact I've been asked to be a non-exec director of other companies, to help them advise on their culture. Which is not in tech, in culture, which is quite interesting. And so the diversity that we have here is really infusing people to innovate in a way that they've not done before. It's that diverse set of opinions really helps. >> Well it does. And this, from what we've heard, Radio is a very, there's a lot of internal competition, it's like a badge of honor to be able to respond to the call for papers, let alone get selected. Touch on the synergies, the symbiosis that I feel like I'm hearing between the things that are presented here, the CTO Ambassadors and the customers. Like maybe a favorite example of a product or service that came from, maybe a CTO Ambassador, to Radio, to market. >> Yeah, I'm just trying to think of any one specific one. There are always bits and pieces, and things here and there. I think I should have thought of that before I came on really. I think what you're looking at here is, it's much more about an informed conversation and so it's those ideas around the fact. And also, quite often someone will have a cool idea, and they'll go to the Ambassadors, can you find me five customers that want to try this? Bang, we've got it. So if you're out there on a customer, and someone comes to you as an ambassador and says, I've got a really cool thing I'd like you to try. It might be before, we have a thing called Fling, so it might even be before it's made a fling. You probably heard from Morney how that process goes. Then engage fast, because you're probably getting that conduit direct into the core of R&D. So a lot of the features that people see and functions and products et cetera, that people see. A lot of the work you see, we're doing with the next version if you realized our management platform, a lot of that has been driven by work that's been done by Ambassadors in the field, and what we're doing there. All the stuff you'll see, I've got my jacket over there with NANO EDGE written on it. A lot of the EDGE stuff that you see, a lot of the stuff around ESXi on Arm, a lot of the stuff around that is driven specifically around a particular product range. So a really good example is, a few years ago, probably around four, myself and Ray sat down and had a meeting in VMware Barcelona, with a retail customer, and the retail customer was talking about could we get them an STDC, but small enough to fit in every store. They didn't say that at the time, but that's how we kind of got to it. So that started off a whole process in our minds, and then I went back and we, the easiest actual way for me to do it was to then get a bunch of the Ambassadors to present that as one of their innovation ideas, which became NANO EDGE. I originally called it VX Nook, because we were going to do it on intel Nooks. (laughs) Unfortunately the naming committee wouldn't allow VX Nook, so it became NANO EDGE. And that drove a whole change within the company, I think within R&D. So if you think up until that point, four years ago, most of what we were doing was, how do we run things bigger and faster? It was all like Monster VM, remember that? All those kinds of things, right? How do we get these SAP HANA 12 terabyte VMs running? And really NANO EDGE was not necessarily a product, per se but it was more of a movement driven by a particular individual, Simon Richardson, who had got promoted to Principle as a result, through the Ambassador program. That was driven through our R&D to get them to think small as well as big, you know. So next time you're building that thing, how small can you run your SX, how small can we get an SX? >> John: Small, at scale. Which is EDGE, right? >> And, you know, so get small, at scale, which was EDGE. And so suddenly everyone starts talking about EDGE, and I'm like, hang on I've been talking about this for a while now, but we just didn't really call it that. And then along comes technology like Kubernetes, which is how do you manage thousands of small things. And it's kind of, these things come together. But yes, totally, you can almost say our EDGE strategy, and a lot of the early EDGE work was done and driven out of stuff that was done from CTO Ambassadors. It's just one of the examples. >> What are some of the Kubernetes service mesh? Because one of the things we heard from Pat, and we've heard this before, but most recently at Dell Technologies World, in the last couple of weeks, was don't look down, look up. Which basically means we're automating the infrastructure. I get that, I've covered ad nauseam. But looking up the stack means you're talking about kubernetes app developers, you've got cloud native, you've got services meshes, microservices, new kinds of challenges around instrumentation. How are you guys inside Radio looking at that trend? Because there's some commercial impact, You've got Heptio, you've got Craig and the team, some of the original guys. >> Yeah, yeah. >> As well as you have a future state coming out, with state, pun intended, data, stateless. (laughs) These are new dynamics. >> Yeah, yeah. >> What's the R&D take on this? >> So there's two ways that I really talk to people about this. The first one is, I've got a concept that I talk about called application chromatography. Which sounds mental, but you remember from high school probably, chromatography was where you had that really special paper and you put the dot of liquid on and it spread it to all it's constituent parts. That's actually what's happening with our applications right now. So, we've gone through a history of re-platform. You know, mainframe, blah blah blah blah blah. So then when we got to x86, everything's on x86, along comes cloud, and as you know John, for the last 10 years it's been everything's going to cloud because we think that's the next platform. It's not, but then everything's not going to SAS, it's not all going to paths, it's not all going to Functions, it's not all going to containers. What you're seeing is those applications are coming off that one big server, and they're spreading themselves out to the right places. So I talk to customers now and they say, okay, well actually I need a management plan, and a strategy and an architecture for infrastructure as a service, containers as a service, functions as a service platform as a service and SAS, and I need a structure for that on premises and off premises. So that's truly driving R&D thinking is not how do we help our customers get from one of those to the other? They're going to all of them. >> It sounds like a green screen for media. >> It is, and then the other side of that is I've just had a conversation with some of the best, you know, what these events are like? Some of the best conversations in the water cooler, in the- >> In the hallway, yup exactly. >> I've just had a fascinating conversation with one of our guys has been talking about, oh it's really cool if we got kubernetes cause I could use it right down at the edge. I could use it to manage thousands as a tiny EDGE things. And as I'm talking to him and sort of saying, you know what he's doing, I suddenly went, hang on a second, how does a developer talk to that? He's like, well I've not really thought about that. I said, well that's your problem. We need to stop thinking about things from how can that framework help me? But how can I extend that framework? And so a lot of that- >> Moving beyond just standing up kubernetes, for what purpose? Or is that what you know, the why, what? >> So if the developers there, it shouldn't be all. I'm going to use this new framework to solve my problem or the EDGE if an R&D person would, but people like myself are there to drive them to think of the bigger picture. So ultimately at some point a developer in the future is going to want to sit there and through an API, push out software SQL server, a bit of Mongo over here, some stuff on AWS, go and use the service on our Azure at the same time pushing stuff into their own data center and maybe push a container to every store if they're a retailer and they want to do that through one place. That's what we're building. And you know, driving that, all these bits and pieces you see behind you pulling those all together into this sort of consistent operations model. As I'm sure you've heard many of- >> And it's dynamics not static, so it's not like provisioning the old way. You got to track what's being turned on and off because how do you log off? What goes turns on? What services get turned on? Turned off, turned on. >> If you don't get a theme of really, I suppose not only Radio, but our industry of the last few years, people have always said if that cliche change is constant, right? Oh, change is constant. Yet still architects build systems that are static, right? You guys that just, I'm designing an architect in this new system for the next three years. I'm like, that's stupid. What you need to do is design a system that you know is going to change before you've even finished starting it. More or less started going half way through it. So actually, as I see, I was in a fantastic session yesterday with the Architects around ESXi and VCenter, which might be boring to most, but where we architecting that for scale at a huge way. >> Well, I think that's the key thing I mean this is, first of all, we'd love this conversation because, if you can make it programmable with API and have data available, that's the architecture because it's programmable, it's not static. So you let it morph into however the application, because I think I mentioned green screen, you know chroma keys as we have those concepts here, but that's what you're saying. The apps are going to have this notion of, I need an app right now and then it goes away. Services are going to be provisioning and turning on and off. >> There is a transience, there's a transience to infrastructure, there's a transience to applications, there's a transience to components that traditional mechanisms aren't built to do. So if you look at actually, what are we building here? And what's that sort of hive mind message? It's how do we provide that platform going forward that supports transience? that allows customers to come, I mean people used to use the term agile, but it's been over years and it's not right. It's the fact that literally it's a situation of constant change. And what your deploying onto, it's constantly changing and what you're deploying is constantly changing. So we're trying to work out how do we put that piece in the middle, that is also changing but allows you some kind of constancy in what you're doing, right? So we can plug new things in the bottom, a new cloud here, a new piece of software there, a new piece of hardware there or whatever. And at the same time, there's new ways of doing architecture coming on top. That's the challenge of this, the software defined data centers, almost like an operating system for clouds or the future operating system for all apps on all clouds and all of- >> It's a systems thinking for sure, absolutely. >> Let's put your Chief Talking Officer hat on for a second as we look- >> I thought I've been doing that for the last fifteen minutes. (laughs) >> At VMWorld 2019, which is just around the corner. Any cool ANEA customers that are going to be on stage that we should be excited to hear about it? >> Actually, I was having a meeting yesterday morning about that, so I can't really say, but there's some exciting stuff we're lining up right now. We're obviously now is the time we start thinking about the keynotes, now at the time you start thinking about who's on stage. Myself and a few others are responsible for what those demos are, you know the cool demos you see on stage every year. So we literally had the meeting yesterday morning at Radio to discuss what's going to be the wow at VMWorld this year. So I'm not going to give anything away to you. I'll just say make sure you're there to watch it because it's going to be good. And we're also making sure there's a big difference between what we're doing in Moscone now and what we're going to be doing it in Barcelona when we- >> And when expand theCUBE outside of the United States certainly, we'd love to have you guys plug in and localize some of these unique challenges. Like you said, I agree bubble now the west of the world has different challenges content different. >> Definitely, I think to that end, multicloud is probably more of a thing in Europe than it was necessarily in, in North America for a longer time because those privacy laws you talked about before, people have always been looking at the fact that maybe they had to use a local cloud for some things. You know, a German cloud run by German people in a German data center and they could use another cloud like Amazon for other things. And you know, we have UK cloud who provide a specific government based cloud, et cetera. Whereas in America there was, you could use an American cloud and that was fine. So I think actually in Europe we've already been at the forefront of that multicloud thinking for a while. So it's worth watching. >> It is worth watching, I wish we had more time to, so you're just going to have to come back. >> Definitely, anytime tell me when. >> We look forward to seeing you at VMWorld. We thank you for sharing some insights with John and me on theCUBE today. >> Cool, thank you. >> For John Ferrier, I'm Lisa Martin. You're watching theCUBE's exclusive coverage of VMware Radio 2019, thanks for watching. (upbeat music)