>>president >>so called big data promised to usher in a new era of innovation where companies competed on the basis of insights and agile decision making. There's little question that social media giants, search leaders and e commerce companies benefited. They had the engineering shops and the execution capabilities to take troves of data and turned them into piles of money. But many organizations were not as successful. They invested heavily in data architecture is tooling and hyper specialized experts to build out their data pipelines. Yet they still struggle today to truly realize they're busy. Did data in their lakes is plentiful but actionable insights aren't so much chaos. Search is a cloud based startup that wants to change this dynamic with a new approach designed to simplify and accelerate time to insights and dramatically lower cost and with us to discuss his company and its vision for the future is cuba Lem Ed Walsh had great to see you. Thanks for coming back in the cube. >>I always love to be here. Thank you very much. It's always a warm welcome. Thank you. >>Alright, so give us the update. You guys have had some big funding rounds, You're making real progress on the tech, taking it to market what's new with chaos surgery. >>Sure. Actually even a lot of good exciting things happen. In fact just this month we need some, you know, obviously announced some pretty exciting things. So we unveiled what we consider the industry first multi model data late platform that we allow you to take your data in S three. In fact, if you want to show the image you can, but basically we allow you to put your data in S three and then what we do is we activate that data and what we do is a full index of the data and makes it available through open a P. I. S. And the key thing about that is it allows your end users to use the tools are using today. So simply put your data in your cloud option charge, think Amazon S three and glacier think of all the different data. Is that a natural act? And then we do the hard work. And the key thing is to get one unified delic but it's a multi mode model access so we expose api like the elastic search aPI So you can do things like search or using cabana do log analytics but you can also do things like sequel, use Tableau looker or bring relational concepts into cabana. Things like joins in the data back end. But it allows you also to machine learning which is early next year. But what you get is that with that because of a data lake philosophy, we're not making new transformations without all the data movement. People typically land data in S. Three and we're on the shoulders of giants with us three. Um There's not a better more cost effective platform. More resilient. There's not a better queuing system out there and it's gonna cost curve that you can't beat. But basically so people store a lot of data in S. Three. Um But what their um But basically what you have to do is you E. T. L. Out to other locations. What we do is allow you to literally keep it in place. We index in place. We write our hot index to rewrite index, allow you to go after that but published an open aPI S. But what we avoid is the GTL process. So what our index does is look at the data and does full scheme of discovery normalization, were able to give sample sets. And then the refinery allows you to advance transformations using code. Think about using sequel or using rejects to change that data pull the dead apartheid things but use role based access to give that to the end user. But it's in a format that their tools understand cabana will use the elasticsearch ap or using elasticsearch calls but also sequel and go directly after data by doing that. You get a data lake but you haven't had to take the three weeks to three months to transform your data. Everyone else makes you. And you talk about the failure. The idea that Alex was put your data there in a very scalable resilient environment. Don't do transformation. It was too hard to structure for databases and data. Where else is put it there? We'll show you how value out Largely un delivered. But we're that last mile. We do exactly that. Just put it in s. three and we activated and activate it with a piece that the tools of your analysts use today or what they want to use in the future. That is what's so powerful. So basically we're on the shoulders of giants with street, put it there and we light it up and that's really the last mile. But it's this multi model but it's also this lack of transformation. We can do all the transformation that's all to virtually and available immediately. You're not doing extended GTL projects with big teams moving around a lot of data in the enterprise. In fact, most time they land and that's three and they move it somewhere and they move it again. What we're saying is now just leave in place well index and make it available. >>So the reason that it was interesting, so the reason they want to move in the S three was the original object storage cloud. It was, it was a cheap bucket. Okay. But it's become much more than that when you talk to customers like, hey, I have all this data in this three. I want to do something with it. I want to apply machine intelligence. I want to search it. I want to do all these things, but you're right. I have to move it. Oftentimes to do that. So that's a huge value. Now can I, are you available in the AWS marketplace yet? >>You know, in fact that was the other announcement to talk about. So our solution is one person available AWS marketplace, which is great for clients because they've been burned down their credits with amazon. >>Yeah, that's that super great news there. Now let's talk a little bit more about data. Like you know, the old joke of the tongue in cheek was data lakes become data swamps. You sort of know, see no schema on, right. Oh great. I can put everything into the lake and then it's like, okay, what? Um, so maybe double click on that a little bit and provide a little bit more details to your, your vision there and your philosophy. >>So if you could put things that data can get after it with your own tools on elastic or search, of course you do that. If you don't have to go through that. But everyone thinks it's a status quo. Everyone is using, you know, everyone has to put it in some sort of schema in a database before they can get access to what everyone does. They move it some place to do it. Now. They're using 1970s and maybe 1980s technology. And they're saying, I'm gonna put it in this database, it works on the cloud and you can go after it. But you have to do all the same pain of transformation, which is what takes human. We use time, cost and complexity. It takes time to do that to do a transformation for an user. It takes a lot of time. But it also takes a teams time to do it with dBS and data scientists to do exactly that. And it's not one thing going on. So it takes three weeks to three months in enterprise. It's a cost complexity. But all these pipelines for every data request, you're trying to give them their own data set. It ends up being data puddles all over this. It might be in your data lake, but it's all separated. Hard to govern. Hard to manage. What we do is we stop that. What we do is we index in place. Your dad is already necessary. Typically retailing it out. You can continue doing that. We really are just one more use of the data. We do read only access. We do not change that data and you give us a place in. You're going to write our index. It's a full rewrite index. Once we did that that allows you with the refinery to make that we just we activate that data. It will immediately fully index was performant from cabana. So you no longer have to take your data and move it and do a pipeline into elasticsearch which becomes kind of brittle at scale. You have the scale of S. Three but use the exact same tools you do today. And what we find for like log analytics is it's a slightly different use case for large analytics or value prop than Be I or what we're doing with private companies but the logs were saving clients 50 to 80% on the hard dollars a day in the month. They're going from very limited data sets to unlimited data sets. Whatever they want to keep an S. Three and glacier. But also they're getting away from the brittle data layer which is the loosen environment which any of the data layers hold you back because it takes time to put it there. But more importantly It becomes brittle at scale where you don't have any of that scale issue when using S. three. Is your dad like. So what what >>are the big use cases Ed you mentioned log analytics? Maybe you can talk about that. And are there any others that are sort of forming in the marketplace? Any patterns that you see >>Because of the multi model we can do a lot of different use cases but we always work with clients on high R. O. I use cases why the Big Bang theory of Due dad like and put everything in it. It's just proven not to work right? So what we're focusing first use cases, log analytics, why as by way with everything had a tipping point, right? People were buying model, save money here, invested here. It went quickly to no, no we're going cloud native and we have to and then on top of it it was how do we efficiently innovate? So they got the tipping point happens, everyone's going cloud native. Once you go cloud native, the amount of machine generated data that you have that comes from the environment dramatically. It just explodes. You're not managing hundreds or thousands or maybe 10,000 endpoints, you're dealing with millions or billions and also you need this insight to get inside out. So logs become one of the things you can't keep up with it. I think I mentioned uh we went to a group of end users, it was only 60 enterprise clients but we asked him what's your capture rate on logs And they said what do you want it to be 80%, actually 78 said listen we want eight captured 80 200 of our logs. That would be the ideal not everything but we need most of it. And then the same group, what are you doing? Well 82 had less than 50%. They just can't keep up with it and every everything including elastic and Splunk. They work harder to the process to narrow and keep less and less data. Why? Because they can't handle the scale, we just say landed there don't transform will make it all available to you. So for log analytics, especially with cloud native, you need this type of technology and you need to stop, it's like uh it feels so good when you stop hitting your head against the wall. Right? This detail process that this type of scale just doesn't work. So that's exactly we're delivering the second use case uh and that's with using elastic KPI but also using sequel to go after the same data representation. And we come out with machine learning. You can also do anomaly detection on the same data representation. So for a log uh analytic use case series devops setups. It's a huge value problem now the same platform because it has sequel exposed. You can do just what we use the term is agile B. I people are using you think about look or tableau power bi I uh metabolic. I think of all these toolsets that people want to give and uh and use your business or coming back to the centralized team every single week asking for new datasets. And they have to be set up like a data set. They have to do an e tail process that give access to that data where because of the way just landed in the bucket. If you have access to that with role based access, I can literally get you access that with your tool set, let's say Tableau looker. You know um these different data sets literally in five minutes and now you're off and running and if you want a new dataset they give another virtual and you're off and running. But with full governance so we can use to be in B I either had self service or centralized. Self service is kind of out of control, but we can move fast and the centralized team is it takes me months but at least I'm in control. We allow you do both fully governed but self service. Right. I got to >>have lower. I gotta excel. All right. And it's like and that's the trade off on each of the pieces of the triangle. Right. >>And they make it easy, we'll just put in a data source and you're done. But the problem is you have to E T L the data source. And that's what takes the three weeks to three months in enterprise and we do it virtually in five minutes. So now the third is actually think about um it's kind of a combination of the two. Think about uh you love the beers and diaper stories. So you know, think about early days of terror data where they look at sales out data for business and they were able to look at all the sales out data, large relational environment, look at it, they crunch all these numbers and they figured out by different location of products and the start of they sell more sticker things and they came up with an analogy which everyone talked about beers and diapers. If you put it together, you sell more from why? Because afternoon for anyone that has kids, you picked up diapers and you might want to grab a beer of your home with the kids. But that analogy 30 years ago, it's now well we're what's the shelf space now for approximate company? You know it is the website, it's actually what's the data coming from there. It's actually the app logs and you're not capturing them because you can't in these environments or you're capturing the data. But everyone's telling, you know, you've got to do an E. T. L. Process to keep less data. You've got to select, you got to be very specific because it's going to kill your budget. You can't do that with elastic or Splunk, you gotta keep less data and you don't even know what the questions are gonna ask with us, Bring all the app logs just land in S. three or glacier which is the most it's really shoulders of giants right? There's not a better platform cost effectively security resilience or through but to think about what you can stream and the it's the best queuing platform I've ever seen in the industry just landed there. And it's also very cost effective. We also compress the data. So by doing that now you match that up with actually relatively small amount of relational data and now you have the vaccine being data. But instead it's like this users using that use case and our top users are always, they start with this one then they use that feature and that feature. Hey, we just did new pricing is affecting these clients and that clients by doing this. We get that. But you need that data and people aren't able to capture it with the current platforms. A data lake. As long as you can make it available. Hot is a way to do it. And that's what we're doing. But we're unique in that. Other people are making GTL IT and put it in a in 19 seventies and 19 eighties data format called a schema. And we avoided that because we basically make S three a hot and elected. >>So okay. So I gotta I want to, I want to land on that for a second because I think sometimes people get confused. I know I do sometimes without chaos or it's like sometimes don't know where to put you. I'm like okay observe ability that seems to be a hot space. You know of course log analytics as part of that B. I. Agile B. I. You called it but there's players like elastic search their star burst. There's data, dogs, data bricks. Dream EOS Snowflake. I mean where do you fit where what's the category and how do you differentiate from players like that? >>Yeah. So we went about it fundamentally different than everyone else. Six years ago. Um Tom hazel and his band of merry men and women came up and designed it from scratch. They may basically yesterday they purposely built make s free hot analytic environment with open A. P. I. S. By doing that. They kind of changed the game so we deliver upon the true promises. Just put it there and I'll give you access to it. No one else does that. Everyone else makes you move the data and put it in schema of some format to get to it. And they try to put so if you look at elasticsearch, why are we going after? Like it just happens to be an easy logs are overwhelming. You once you go to cloud native, you can't afford to put it in a loose seen the elk stack. L is for loosen its inverted index. Start small. Great. But once you now grow it's now not one server. Five servers, 15 servers, you lose a server, you're down for three days because you have to rebuild the whole thing. It becomes brittle at scale and expensive. So you trade off I'm going to keep less or keep less either from retention or data. So basically by doing that so elastic we're not we have no elastic on that covers but we allow you to well index the data in S. Tree and you can access it directly through a cabana interface or an open search interface. Api >>out it's just a P. >>It's open A P. I. S. It's And by doing that you've avoided a whole bunch of time cost, complexity, time of your team to do it. But also the time to results the delays of doing that cost. It's crazy. We're saving 50-80 hard dollars while giving you unlimited retention where you were dramatically limited before us. And as a managed service you have to manage that Kind of Clunky. Not when it starts small, when it starts small, it's great once at scale. That's a terrible environment to manage the scale. That's why you end up with not one elasticsearch cluster, dozens. I just talked to someone yesterday had 125 elasticsearch clusters because of the scale. So anyway, that's where elastic we're not a Mhm. If you're using elastic it scale and you're having problems with the retired off of cost time in the, in the scale, we become a natural fit and you don't change what your end users do. >>So the thing, you know, they had people here, this will go, wow, that sounds so simple. Why doesn't everybody do this? The reason is it's not easy. You said tom and his merry band. This is really hard core tech. Um and it's and it's it's not trivial what you've built. Let's talk about your secret sauce. >>Yeah. So it is a patented technology. So if you look at our, you know, component for architecture is basically a large part of the 90% of value add is actually S. Three, I gotta give S three full kudos. They built a platform that we're on shoulders of giants. Um But what we did is we purpose built to make an object storage a hot alec database. So we have an index, like a database. Um And we basically the data you bring a refinery to be able to do all the advanced type of transformation but all virtually done because we're not changing the source of record, we're changing the virtual views And then a fabric allows you to manage and be fully elastic. So if we have a big queries because we have multiple clients with multiple use cases, each multiple petabytes, we're spending up 1800 different nodes after a particular environment. But even with all that we're saving them 58%. But it's really the patented technology to do this, it took us six years by the way, that's what it takes to come up with this. I come upon it, I knew the founder, I've known tom tom a stable for a while and uh you know his first thing was he figured out the math and the math worked out. Its deep tech, it's hard tech. But the key thing about it is we've been in market now for two years, multiple use cases in production at scale. Um Now what you do is roadmap, we're adding a P. I. So now we have elasticsearch natural proofpoint. Now you're adding sequel allows you open up new markets. But the idea for the person dealing with, you know, so we believe we deliver on the true promise of Data Lakes and the promise of Data lakes was put it there, don't focus on transferring. It's just too hard. I'll get insights out and that's exactly what we do. But we're the only ones that do that everyone else makes you E. T. L. At places. And that's the innovation of the index in the refinery that allows the index in place and give virtual views in place at scale. Um And then the open api is to be honest, uh I think that's a game. Give me an open api let me go after it. I don't know what tool I'm gonna use next week every time we go into account they're not a looker shop or Tableau Sharp or quick site shop there, all of them and they're just trying to keep up with the businesses. Um and then the ability to have role based access where actually can give, hey, get them their own bucket, give them their own refinery. As long as they have access to the data, they can go to their own manipulation ends up being >>just, >>that's the true promise of data lakes. Once we come out with machine learning next year, now you're gonna rip through the same embassy and the way we structured the data matrices. It's a natural fit for things like tensorflow pytorch, but that's, that's gonna be next year just because it's a different persona. But the underlining architecture has been built, what we're doing is trying to use case that time. So we worked, our clients say it's not a big bang. Let's nail a use case that works well. Great R. O. I great business value for a particular business unit and let's move to the next. And that's how I think it's gonna be really. That's what if you think about gardener talks about, if you think about what really got successful in data, where else in the past? That's exactly it wasn't the big bang, it was, let's go and nail it for particular users. And that's what we're doing now because it's multi model, there's a bunch of different use cases, but even then we're focusing on these core things that are really hard to do with other relational only environments. Yeah, I >>can see why you're still because you know, you haven't been well, you and I have talked about the api economy for forever and then you've been in the storage world so long. You know what a nightmare is to move data. We gotta, we gotta jump. But I want to ask you, I want to be clear on this. So you are your cloud cloud Native talked to frank's Lukman maybe a year ago and I asked him about on prem and he's like, no, we're never doing the halfway house. We are cloud all the >>way. I think >>you're, I think you have a similar answer. What what's your plan on Hybrid? >>Okay. We get, there's nothing about technology, we can't go on, but we are 100 cloud native or only in the public cloud. We believe that's a trend line. Everyone agrees with us, we're sticking there. That's for the opportunity. And if you can run analytics, There's nothing better than getting to the public cloud like Amazon and he was actually, that were 100 cloud native. Uh, we love S three and what would be a better place to put this is put the next three and we just let you light it up and then I guess if I'm gonna add the commercial and buy it through amazon marketplace, which we love that business model with amazon. It's >>great. Ed thanks so much for coming back in the cube and participating in the startup showcase. Love having you and best of luck. Really exciting. >>Hey, thanks again, appreciate it. >>All right, thank you for watching everybody. This is Dave Volonte for the cube. Keep it right there.

>>live from Las Vegas. It's the Q covering AWS executive. Something brought to you by extension. >>Welcome back, everyone to the cubes. Live coverage of the ex Center Executive Summit here at AWS reinvent I'm your host, Rebecca Knight. I'm joined by Marum Best Aerobic. He is the managing director Global Cloud and Infrastructure Attic Center. Thank you so much for coming on the show again. We met last year. So you're a Cuba Lem. >>Yes, I am. >>So we're talking today about moving a $43 billion company to the Cloud X Century. This is X Center as its own as its own use cases. But Accenture has been engaged in a major move to the public Cloud moving a company of the size and heft of ex center. Must have been intimidating. How did you even sort of wrap your brain around the challenges? Walk? Walk us through this. >>So you know, the tough part about working at Accenture is you have 480,000 people that work for Accenture or at least 1/2 a 1,000,000 let's say, and those half a 1,000,000 people all think they can do the job better and differently than you do, right. So the first challenge is our own our own organization. But I would tell you I say that, you know, just in a joking way. They're very supportive. It was. We're telling our clients the cloud is the future. So when we told our organization we're going to the cloud, it was massive support. It was what's taking so long? Let's do this. And now, granted, this was over a little over four years ago when we started the journey. So the cloud providers in the world was very different. So today we run, you know, tens of thousands of workloads on Amazon. We run all kinds of the capability to do cloud native. We do platform service's. We consume so much cloud service that, in my opinion, we're never going back to a data center. Never. >>So what Ex center is really well known as a big advocate of the public cloud? First of all, why? Why the public club? Well, the public cloud is >>the future. I really think when you think about how especially somebody like Amazon, if you listen to Andy Jassy this morning, right, it's they are innovating at a scale and a pace that that's just truly exceptional, and it gives us opportunity to take those things and implement them to change the way we run our business. So the weak and implement a lot of these capabilities toe help enable our business and then through that, by enabling our business be a credential for not only ourselves but to our clients to say, Hey, we do this to ourselves and way can help you do it as well. >>We're walking the walk >>or totally walking the walk and we push very hard on that angle because for us, it's very important for me personally to say, you know, I started my career client service. So I know serving our clients is one of the key things for us in our business. So I want to be able to solve these things, these air hard things itself so we can solve them faster for our clients ourselves. It makes it easier for them on their journey, >>and you also understand the pain points and the challenges A CZ you said your employees, your workforce was very supportive of it, but that's not always the case. >>No, it's not. It's not in But I'll tell you, our own teams in the early days they struggled with this. To be honest, right? It was a It was a change because we were heavily, heavily virtualized. We were great at running our infrastructure. We were doing all those things. Those are the things you did back then. So then when we said the team's Hey, we're going to the cloud They said, Well, we're not so sure. Do we really think we're going to save money? And in the early days we said We're doing this because this is the right thing to do But in the end, we actually did save a lot of money going to the cloud because we learn toe work differently and I think that's one of the key messages I would convey back is you are not going to work in the cloud the same way you work in a data center. You are going to shut things off. When you don't use them, you're going to have an opportunity to optimize them. You will have an opportunity to spend new capabilities up sooner, used them for what you need and faster and then you know things you can't do in a data center. You can't spend up. You can't use Dynamo. You can't use lambda. You can't. You can't use these. Micro service is in the data center, but in a cloud you can. So now you leave yourself in a situation where you have so much capability you can turn on to enable In enterprise is just mind boggling and exciting and exciting. >>So the time table t make this transformation was ambitious, to say the least. How aggressive did you need to beating? This is a journey. You said you started a little over four years ago. >>Yeah, it took the entire program for us. Took us about three years. But the real aggressive part of the journey was we said, you know, we can't We're dabbling a little bit in it. So let's just say our starting point was around 9%. You know, one of the big things we said is, how do we get the 50% in one year? And it was like, Okay, how do we do that? So we put a program in place and we got the team organized, and we did, you know, kind of like what Andy Jesse was talking about today at the keynote. We set some top down goals. We said to the teams were going to do this. This is the future. We're not kidding. We're going to do it. We have full support and we work with the business. And we explain what it was what was going to be. And you know what? One of the first things we took the public cloud, like three months into this program, was accenture dot com. I mean, we literally three months into the program, took our market facing capability of what our clients look at. People look at to think about us. They moved into the public cloud. >>We've described as a very disciplined approach and also one that was led from the top brass. So how talk a little bit about how the transformation started? >>Yes. So the transformation was really I will tell you, in the early days it was a function of we're going to start to take thes workloads and move them to the cloud. How do you do that? We made a decision to say, Let's take this. Let's take it a data center approach perspective. We're going to shut down an actual data center one at a time. And that's how we do migrations now. A lot of clients think about it from a different perspective. From our point of view, it made the most sense of Shut down the data center and get out of that location because then you're not maintaining all these things twice the fastest you can do it. The better way to do it is to do that. So that's kind of how we approach that. We said all the workloads in the data center go now. We took on our North American workloads first because we didn't make it easy for ourselves, right, because that's where all of our production work clothes where it wasn't just the test environments. It wasn't just a, you know, development environment. It was the real deal, everything it takes to run and support Accenture And we said we're gonna move those first. And so from a transformation perspective, that was our key. And then the other one is we had this. We had this notion of cloud first and cloud only. So any new capability also, we said here on out the minute we started the program. We said no more data center. We are anything you need now is going to be provisioned in the cloud. >>And what about digitally native applications? Yes. So when you think >>about like, um, a clown native capability. So now you start to get into another. You're into cloud, You go. Oh, man, what else can I do? And then So our previous CEO announced to the world extension was no wonder going to do performance reviews. And we're like, Okay, this is great. What we gonna >>do >>about this? And we need it implemented in three or four months. So when our HR business team came to work with us, one of the things we said is, Hey, this >>is the >>time because at that point we were about six or seven months into the program of Cloud. We said, Well, you can't spend up of'em. You're gonna go into the cloud. So we built a capability to does performance achievement for 405 100,000 people globally that runs it with Lambda and Dynamo. And it's been there for a little over now, four years, believe it or not. >>Amazing. So we talk about other challenges that you face because I mean, the way you're describing it, It sounds as though it people were supportive and you had a lot of winds along the way. But of course, there there were. I'm sure there were some dark days to weigh, had some >>growing pains. I think you know, when you think about it a lot of times because a lot of work loads we did pick up. We did a lot of lifting shift. Um, and I hate that term because what we learned as we went is we could actually lift, configure and run for less. So I don't know if there's an industry term for I haven't coined one yet. If somebody here is one that they want to share with us, I'd love to hear it. But lift and shift itself is a bad. It's a misnomer because that's not how you do this right. You have to touch a little bit of something. But what happened is in the early days we weren't quite sure how to size these environments, so when we would pick them up and we would say, Well, let's let's let's kind of give it some more capability. Let's let's throw some more CPU at it. But what we learned very quickly was that costs a lot of money. And we started applying some tools that would love, help us see what the utilization needed to be. And then we learned very quickly that Oh, you know what this environment that used to exist in the data center? Well, that's >>kind of >>on a couple of generations ago. CPU a couple of generations ago, memory a couple of generations ago storage because all the stuff in the cloud is all newer, all new or CPU on your memory. So then very quickly it's not even a like for like it's a like for less. So we figured out very quickly that we can actually take a workload. Let's say they had eight CPU use and we can run in the cloud with two. And so, But it was. It was. It was growing pains through that process that we learned to say, How do we do it then? Frankly, I think a lot of times we talked about this with our clients who is how do you get the team along the way? Because it's it's and When we set the edict, the team realized they had to go do this stuff. But, you know, we thought we'd have a little bit of resistance. What we found instead was a team very eager to learn and very eager to be part of this program and part of this capability. Because they see it. They saw that it was this new stuff that we were doing. So a little bit of the early growing pains around who's gonna work on what? How do we How do we focus our training? You know, how do we get these teams to help us really drive some of this capability and as we started, enabled them or that helped us get momentum. And I think the other one is just when you start to get all these workloads and how do you actually manage this stuff? How do you manage this capability? And for us? You know, we spent a lot of time with our eccentric cloud platform friends because we needed a capability to said, How do I actually manage all this building? How do I discover all the capabilities that are out there? How do I track my compliance How do I make sure all these things are aligned to my security? Construct that in, You know, info SEC is asking us to drive. So we need to do all do all those things that we didn't have it perfect in the beginning and we learned along the way. >>So talk about some of the other benefits you've described cutting some costs. And you've also described this new mindset that so many of your employees have adopted a rials learning minds, a growth mindset, one of embracing innovation. What are some other of the benefits that you've seen? >>You know, the benefits that are to me today is just this art of the possible is just mind bogglingly so much more open to whatever you want to do. It's almost scary how much is out there. You actually have to kind of pull back a little bit and say, How do I apply some guardrails around us? And I think when I think about the other benefits are we have more capability now than ever to spin workloads up. I'll give an example, like on Amazon spot instances are one of the things that they offer. We spend up 700,000 spot instances a year to do work along the way. And it's unfathomable to even think about doing some of those things in the data center. So the flexibility that you get if you want to test the release sometimes some of these big systems you might have to bring in hardware to test that in the data center. But in the cloud I >>don't have >>to buy hardware. I could just spend up more excuse. So it's just the benefits of flexibility, the agility, the speed that not waiting on and also, I think, the other one that I think sometimes gets overlooked as Excuse me. Sometimes that gets overlooked as I don't have a capacity management team that's worried about the capacity in the data center. I don't have AH team managing the vendor. Providing the data center service is right. It's all these things. You start to turn off that you didn't know that you don't need in a cloud anymore because they're managing those things. So even even if you're some, I think some clients get lost and waiting too long to do this. But there's all these other costs around there that you're spending money on anyway, you may not realize is you think about this business case, so I think the benefits are just tremendously there. But you really have to look at it holistically. >>So this morning, on the main stage we heard Andy Jassy describes a dizzying number of new products and service is that eight of the U. S. Is coming out with How how are you thinking about those and integrating them into what you're doing at Accenture with this initiative? And what's the energy that you're taking away from? I mean, he's certainly a very dynamic leader. >>Well, the energy the energy is great at this event. Every single year, the amount of innovation that comes out, it's fantastic. I think one of the great things that came out today is this concept of we're gonna take the hyper visor. We're actually gonna move it into a chip set to help you give you more processing power on the computer. I think on the server is huge. That's a huge capability. Lets us think about how do we manage things differently? I think some of this, uh, you know, uh, capabilities run enterprise, search enterprise, search is very hard, very difficult, right? This ml capability that, you know, it's very appealing. What am I gonna do with that? How do I help my organization think about search differently? That's very appealing. And I think the other one that's you know, there are a lot of other ones around the ML and the Data Lake stuff and everything else, but I think some of these things that get overlooked sometimes the pure review with ML was awesome, right? It's like, How do I help? How do I help them? Has the machine helped me do a code peer review with my people? So those were just, you know, real quick things that come to mind. But it's just great to see all this innovation, and it becomes available so quickly, right? So you've got you have an opportunity to get into these things very fast. >>So as you look back on this journey, this transformation, what are you most proud of? And what are you most excited about in the future? I'm most >>proud of the bold bets. Not only that, we all individually took, but the team's I'm so proud of our team in taking the journey onto trusting us, tow working and pushing and learning themselves to really take this on and it's it's it's just this magical. It's like it's a compound ing thing that just infested everybody else writes. Everybody's been excited about the cloud and how do we do it? How do we do this stuff? I think you know. And then from a future perspective, I'm really interested in MAWR in As the capabilities evolve and they get announced, I think the benefit we have is as we're there. It's easy for us to see some of these things. I think the container landscape is going to be huge. All the kubernetes stack and everything else that's that's out there. We need to think about. How does that help me continue to evolve? The service's I provide either more custom cost, effectively arm or efficiently back to the business and turn on more capability faster and try stuff faster and turn it off faster. And that's the great part of the cloud, right? You get the try stuff, you get to play >>with it, >>and if you don't like it, you turn it off. You don't have to wait three years for this equipment toe. Appreciate you move on with life. And that, to me, is exciting because there's just so much innovation that's coming. There's so much opportunity for us to really just jump out there and, uh, have fun. >>Excellent old Merrin. Best aerobic. Thank you so much for coming on. The cubic pleasure talking to you too. I'm Rebecca. Night. Stay tuned for more of the cubes. Coverage of the ex center Executive Summit coming up tomorrow. We'll see you here right now. Early.

>> live from Anaheim, California. It's the queue covering nutanix dot next twenty nineteen Brought to you by nutanix. >> Hello, everyone. You are watching the Cube and we are live at nutanix dot Next here in Anaheim. I'm your host, Rebecca Night, along with my co host, John Farrier. We're joined by Michael Bushong. He is the vice president Enterprise marketing at Juniper Networks. Thank you so much for returning to the Cube, Your Cuba Lem. >> So thank you for this is this is awesome and you can't see it on the cameras. But this is a, like, just amazing. >> It's very We are in the clouds up here. It's a very high stage. Everything's coming full circle. >> Jim Cramer. Ask a little bit >> serious. Okay. >> Of course. I'm going to ask the tough questions >> going on. He's going to start slamming everything very soon, >> But we've known each other for a long time, Jennifer Going back ten years ago. So look, a tangle started. We're in our tenth year. You know, if you've seen the journey, I am a juniper. You left juniper startup brocade, then back to juniper. So you've seen that circle? You've seen the couple waves? I mean one of the things we were talking about before we came on camera was saw. Network fabrics to Dover had Juno's and then be anywhere. But you know, So this arrow, which became the ESPN Wave, are now suffer to find data center. So you've been in that journey is a product person. And now marking juniper, it's actually goes back about a decade. This whole esti n stuff networking. So what's What's the role now that you're doing? What's juniper doing? Why Nutanix? What's your story year? >> Sure. So I run enterprise marketing at Juniper, so my goal is effectively toe to make some of the hype makes sense, right? It goes back a decade. Actually, the early days of the only ESPN movement we didn't call it s tiene right. Juniper started with open flow and PC and alto and all these acronyms, and we actually, we're a great engineering company. Maybe not so great marketing company. And we actually call it network program ability. That didn't take off. But the technology's kind of endured. And I think what we saw was this lengthy incubation period to the point that now, as we sit here dot next in twenty nineteen. We're starting to see now some of the attraction of the last couple of years. That's a junipers general position. So we wantto dr Adoption. Certainly there's products and technology that underpins that, but But fundamentally, we're looking at a huge operational shift. And if that operational shift doesn't happen, then that's to the detriment of everyone in the industry. >> What's the relationship with NUTANIX? Can you talk about how you guys work together? What's the connection? >> Sure. So nutanix obviously does the whole hyper converge space. We provide the networking components to that. So whether that's the top Iraq connectivity, how do you get your traffic into the rest of the network? We've done some security stuff which we can talk more about. And then, if you look at the overall management piece, we've got integrations at the management policy layer as well. >> So your relationship you both got a very similar world view. How you see technology, you're both taken on VM. Where to? Can you talk a little bit about the relationships there and and why it works? >> Sure, fundamentally, if you look at what Nutanix is trying to do, it's this whole idea of one click. It ties ing everything right. They talk a lot in their keynote sessions. You hear the executives talk, You look at their collateral, the messages they take, the customers. It's about making things simple. Junipers Strategy is this idea of engineering simplicity. So just a top level? What's our purpose? What's our role in this industry at large? I think we have a very common worldview. Of course, driving simplicity is going to happen in the context of real architectural change on the change That's kind of everywhere is cloud and increasingly multi cloud. And so both Nutanix and Juniper about really driving simplicity in the context of Cloud multi cloud, giving customers the opportunity, toe run workloads wherever they need Teo without taking on additional operational burden. That's kind of cesarean unwanted in enterprises networking. >> So the Big Tran, this multi cloud you guys. That's a key part of the strategy. Dave along tonight and Stew Minutemen were arguing on the cute couple events ago. There are not one of our sessions about the hype around multi cloud. The reality of it. The reality is, is that everyone kind of has multiple clouds. It's not like that the clouds aren't talking to each other, and then we're just kind of riffing on the cloud is just big. One big distributed network, different computing, distributed networks. These air knew these aren't new paradigms. These are existing things that have computer science behind them. Engineering behind it. So juniper, you have been around for a long time. Connecting networks. The cloud is like some of the same concert on premise Hybrid Cloud and multiplied it basically a distributed network. It's all cloud operations. We get that, but the technology issue is not that hard, but I won't say that that hard, but it's similar to what you guys have done in the past. Just differently. How are you guys looking at that? Because multiple clouds, just like Internet working the switches routers, you move from packet that point A and point B get storage. His store stuff So concepts are all the same. How do you guys seeing the multi cloud opportunity within juniper? >> So I would make the distinction between multiple clouds and multi cloud? I agree with you. If you look at most enterprises, they have a workload in Amazon. They're using sales force, and so you know, they're multi cloud, right? They have multiple clouds, multi clouds, more of an operational condition. It's about taking disparate pools of resource is and managing. That is one thing. So think of it more about how you do stuff and less about where you host an application. If you look it even like describing Amazon, some people say, Well, Amazon is just, you know, Cloud is just using other people servers. It's not. You're not renting their servers. What you're leveraging is their operations. That's the transformation. That's this kind of underfoot. And so while some of the technology bits are common, the ability to do abstracted control moving to declare it over intent based management, right, these air right technology building blocks. What you're seeing now is the operational models are coming along, and that's really that's the change we have to drive on. I'll just kind of close with when you change technology. If it's just about deploying a piece of software, if it's just about deploying a piece of hardware like candidly, that challenge isn't that it's not that hard, right? We know how to deploy stuff when you start talking about changing how people fundamentally do their jobs. When you started talking about changing, you know how businesses operate. That's that's the piece that takes some time and I would venture. That's why you know, you look a decade ago why we're where we started. If you look at what's taking a decade, it's the operational change, not the technology piece >> and the cultural jobs movement. Certainly forcing function on that, which is awesome. And that's the tale when I think. And then again, Gene Came was on yesterday Who wrote The Devil's Handbook and also does that death. The Devil Enterprise. Someone said, We're three percent in. I would agree with him. I think it's so early, but But the challenge. I want to get your thoughts, Michael. And this is that Connecting multiple on disparity environments is great, but late in C kills now. So now late and see these air old school concepts, you know, get a time can't change the laws of physics. Right? So Leighton sees matters s l A's matter. So these air network challenges these air software challenges. What's your view on that piece of the puzzle? >> We leave when we say cloud, you know a lot of people probably think, um, you know, G C P Azure. They might think a WSB probably picture in your head, you know, some logically central cloud. First, we need to disavow people of the notion that cloud is this thing that somehow sits at the center of everything. It's not. There are centralized clouds. If you're optimizing for economics, that makes perfect sense. Tow To do that. There's distributed clouds. The whole rise of multi axis edge computing is about changing the paradigm from moving data to the application. Right. If your applications in Amazon and you're going to send your data there, that's one model Teo. Sometimes you might want to move the application to the data. If you have a lot of data like an i o t. Use case as an example, I was used oil platforms is a really good example. I don't know if you know, but you know how they get all their. They have all these mining and manufacturing bits. They've got lots of data. How did they get that data off the oil platforms? Snowball. So what they do is the helicopters come in, they take the drives off and they they they leave right. The reason they do that because if your reliance on satellite links just too much data, you can't statue >> is going to get a helicopter to ransom helicopter to come in, >> we'LL know when they're swapping the crew out every fourteen days, that's what happens. So here's the thing, right? If in that kind of model than the cloud, the data center exists on premises. And if that's the case, then when we think about you know kind of what the cloud is, cloud is, it's It's a lot. It's a lot more than what we most of us probably think about. Certainly, we see it with Outpost as a WS is starting to move on premises versions, and there's a lot of reasons you might wanna have a distributed cloud. Certainly it could be, you know, your comfort and security and control. There's real privacy implications, country of origin, so subpoenas can access your information depending on where it resides. >> What you're saying is, basically, it's all cloud. It's operational is the new definition. So you figured from an operational standpoint, Ops and Dev's That's it. The rest is just all connected somehow through the text, >> and then you need to have it. Yes. So we we understand the connectivity, bitch, you've gotta have the right, you know, elements. But if it's operational, it's about how do you do policy management? So part of the whole nutanix thing and kind of what drove us together was this idea that if I want a one click everything. If you could do that within the hyper converge space, you still have to do that over the connected environment, which means managing policy from a single location, regardless of where it is. And of course, using that policy to Dr Security >> and their strategy is to take what that worked for. The CIA and the data center move that into this new operator operating model, which spans multiple quote, disparity, environments or clouds or edges. It's similar similar concept, but different environmental. Yeah, >> that's exactly right. And so then what Nutanix needs that is a strong networking partner because they have tto do the bits that they do. They need other people to do the bits that that you know that we can do. We pull those things together and then you can provide essentially a secure environment for hybrid workload. >> So you guys embed it into their product? You guys joined cell together. Is it more of a partnership? How deep is the partnership with you With Nutanix >> s all just They'LL say yes, we get along s o and it kind of the most surface level you know, you need to have top Iraq switches. You gotta connect to the network and so we do qualification there. So if you deploy nutanix, you can deploy juniper alongside and that looks more like a kind of a co selling meat in the channel type model. Beyond that, if you look at how we provide security over like a workload environment, the question is, then you know what's the security element? So we've taken our virtual firewall. We cut our V s are axe, which essentially runs in the V M. And we can run it on a V, and so that gives them a segmentation strategies. So if you look it workloads that air distributed across the cluster by having a firewall element that we can enforce policy. Of course, that firewall element is then integrated with prism. So if I want to deploy these things when I spin up a new V M. What I want to do is spin up the security with it, and so you see management integration. Then if we continue this too, it's kind of full conclusion. We have, ah, product suite We call contrail in the enterprise version Contra Enterprise Multi Cloud, which is all about policy management and underlay management. And so, as we extend the partnership, it gives us additional opportunity to take um to provide routed elements which provide policy enforcement points and then to give us a way of managing policy over a diverse environment. >> And you guys can bring in that platform element for nutanix. Is there now a platform? They have a full stack of software on Lee. So you guys, you cannot take their stuff, put it there and vice versa. >> That's exactly right. So whether the workload resides in a ws on two or whether it resides kind of on premises in a jiffy, weaken one, we're kind of co managed and then to it gives us the security elements toe play across that >> one of the things that we're talking a lot about at this rinse it and at a lot of other events like it, it's sort of or the dark side of technology. We're at a time where major presidential candidates are talking about breaking up. Big tech were becoming much more aware of the privacy concerns. The biases that are built into algorithms. Exactly. I want to hear your thoughts as a technology veteran. Do you? Are you still a technology optimist or do you did? Does this stuff keep you up at night? I mean, how where do you fit your personal views? I was >> somewhat of a technology optimists, but I'm a skeptic when it comes to the people. I think if the technology existed in a vacuum, I think some of the problems go away. I think privacy is a major concern. I think it's going to shape regulatory action, especially in Europe. Well, so I think we'LL see similar actions in the US I don't have quite a strong connection to what's happening in Asia. Um, I think that the regulatory, the challenge I have from a technology perspective is that if the regulations come in the absence of understanding how the technology works, then you end up with some really terrifying outcomes on DSO I'm Sam. I'm a fan of the technology. I'm nervous of the people on that in terms of like, our overall Ruelas is cos here, I think, you know, we need to do a candidate a better job of, of making sure things land before we move on to the next big thing on DH. You know, we're talking cloud. We're ten years into cloud and people were always talking about the next frontier. To some extent, I think the world doesn't move as fast as we like to think it does. I don't think that the even like the mark, I'm in a marketing role. I don't think that the marketing hype necessary. I don't think it serves us by moving too far ahead because I will tell you when the gap between the promise and the reality becomes insurmountable e wide. I think it's Ah, I think I think everyone loses Andi. You run the risk of stranding an entire generation of people who who gets stuck behind it, and I don't you know, I'm nervous about about what that means, and I think it's you asked the question that you're the dark side. I think it's Certainly it plays out in our industry. I think it plays out. You know, there's a digital divide that's growing in the U. S. Based on broadband access. By the way, that's gonna widen with five G. I think it plays out between different nation states. So I Yeah, I don't know. I'm an optimist. Maybe I'm a pragmatist. >> Realist. >> Yeah, I'm I'm I'm I'm a little scared. >> Little cloud definitely happened, and that's a good point. And we took a lot of heat at looking ankle. Keep on the cube. Was too many Men in the team put out the first private cloud report People like this is nonsense. Well, well. And our thesis was clouds grade if you want. If you're in the cloud as a cloud native or, you know, new startup, why wouldn't you go on Amazon? Everyone, we did that. But if once you taste cloud operations, you go Wow. This is so much awesome. Right? Then go into a modern and enterprise. It's not going to be overnight. Change over. I mean, we might say it's going to take about a decade. We fell from the beginning that cloud operations once you taste cloud you realize this is a new operating model. There's a lot of benefits to that, but to change it over in the enterprise, and that turned out to be what everyone's now do it. But that was three years ago. >> Well, there's implications. So if its operations then operations is inherently an end end proposition, you can't have operations in a silo. Things like you're monitoring tools. How do you do cloud monitoring it on premises monitoring. How do you do workflow Execution? How do you do? You know, automation, whether that's event driven or even just scripted. If you have wildly different environments that require you to buy for Kate, your investment, then there's a very real There's a complexity that comes with that your people have tto do more than one thing that's that's hard. There's a cost that comes with that because you have different teams for different things. There's a lack of coordination. I don't think you unlock the value of cloud in that in that environment. And I think that operational pieces really around converging on >> Michael your point about people in technology. It's so right on. We see that all the time where I'm a technology Optimus. I love technology, but I totally agree that people can really destroy it looked fake news. It's just, you know, it's infrastructure network effect with bad content policy because Facebook's immediate company not a platform >> well, technology's only is good on our end are >> gonna run. The government don't even have the Internet work. So you know when you when you go to the cloud, same >> knowledge just also want the government to come away with that we do it >> where the government just doesn't know how the Internet works. Some people that do but like the good hearings, it's ridiculous. But you know, there's a real D o. D project going on future military Jet I contract. We've been reporting on where modern data driven application workloads. I could use a soul, cloud or multi class so that the dogma of what multi vendor was in the old days is changing. >> I don't I actually don't know if you look at multi cloud. If it's an end end proposition, then by definition it's also going to be multi vendor like there's no future where it's like end in all one vendor. I think we have to come to grips with that is an industry. But I think if you're clinging to your you know, kind of I want my single procurement vehicle. I want my single certification. By the way, I think if you believe fundamentally that incumbency is going to be that your path forward, I think it's a dangerous place to be. That's not to say that. I think the incumbents all go away. I don't There's a there's a heavy rule to play but certainly were going to open things up. And >> you see procurement modernized. I mean, I mean, government goes back to nineteen ninety five procurement standards, but either the enterprise procurement moving So the text moves so fast. Procurement still has rules from >> so no, I don't think all >> of the second right. >> Then there's a whole A procurement in our industry is driven by our peace. Our peace tend to be derivative. I take my last r p. I had some new lines. If you want Esti n so you take the cup copy and paste five hundred seventy four lines at the five hundred seventy fifth line. S T n. You're gonna end up in the same solution because the first five seventy four of the same I do think we should learn a little bit from what the big public cloud cos they're doing, which is, you know, tightening refreshed cycles, retiring things with as much passion as they introduced new things tightening up. Ultimately, what gets deployed? Maintaining diversity of underlying components so you could maintain economic leverage when you're doing procurement. But then solidifying on operationally streamlined model, That's I think that's the future. That's certainly what we've been on as a company. I think that's what we're betting on with Nutanix From a partnership point of view, I think we'LL be on the right side of change on that, and I think it's going to, you know, it may take some time to play out. That's where I think things go >> well. Michael Bushong. Always a pleasure having you on the Cube. Thank you for coming on. >> Thank you very much. >> I'm Rebecca Knight for John Furrier. You are watching the Cube

>> live from Boston, Massachusetts. It's the queue covering your red hat. Some twenty nineteen lots. You buy bread >> and good morning. Welcome to Beantown, Boston, Massachusetts to Mina Mons Hometown by the police Town of residents. John Wallis was stupid from here on the Q. Bert had summit and stew for you. Good to see you here. And a home game. >> Yeah, John, Thanks so much. Nice. You know, Boston, The Cube loves Boston. The B C E C is actually where the first cube event was way back in twenty ten. And we wish there were more conferences here in Boston. Gorgeous weather here in the spring. Ah, little chilly at night with the wind coming off the water, but really good. Here is the sixth year we've had the Cube here, right? Had some in my fifth year at the show. Great energy. And, you know, thirty four billion reasons why people are spending a lot of time keeping a close eye on. Let's just know. Yeah, >> jump right in thirty four billion dollar deal. I am red hatt gotta prove by doj uh, here in the States. But there's still some hurdles that they have to get over in order for that to come to fruition, Maybe later this year. That's the expectation. But just your thoughts right now about about that synergy about that opportunity that that we think is about to have. >> Yeah, so? So right, let's get this piece out of the way. Because here at the conference, we're talking about Red Hat. The acquisition has not completed. So while the CEO of IBM you know Jenny will be up on stage tonight along with, you know, Jim White Hirsi over at Hat and Sakina della, you know, flying in from Seattle, where you might get your name yesterday. So you know, at least two of those three your Cuba Lem's. So we'LL get Jenny on one of these days. But, you know, this is a big acquisition, the largest software acquisition ever, and third largest acquisition in tech history. Now we watched the first biggest tech acquisition in history, which was Del buying AMC just a couple of years ago. And this is not the normal. Okay? Hey, we announced it and you know, it closed quietly in a few months. So as you mentioned, DOJ approved it. There's a few more government agencies Europe needs to go through. You never know what China might ask to come in here, but, you know, really, at the core if you look at it, you know, IBM and Red Hat have worked together for decades. You know, we wrote a lot about this when the announcement happened. You know, IBM is no stranger to open source. IBM is no stranger to the clinics and the areas where Red Hat has been growing and expanded too. You see, IBM, they're so communities, you know, super hot space. If you look, you know, Red hat is they're they're open shift platform, which is what Red Hat does for cloud. Native Development has over a thousand customers. They're adding between one hundred one hundred fifty a quarter is what they talk about publicly. We're gonna have some of those customers on this week. So huge area. That multi cloud hybrid cloud world absolutely is where it's at. We did four days of broadcast from IBM. Think earlier this year in San Francisco. And, you know, once again, Jim white hairs and Jenny were on stage together. They're talking about where they've been working together for a long time. and just, you know, some things will change, but from IBM standpoint, they said, Look, you know, the day after this closes, you know, Red Hat doesn't go away. That had just announced new branding, and everybody's like, Well, why are they changing their branding? You know, when you know IBM is taking over and the answer was, Look, Red Hat's going to stay as a standalone entity. IBM says they're not going to have a single lay off, not even HR consolidation, at least in the beginning. We understand, you know, give me your stuff to work out some of these pieces, but there are ears. They will work together. I look at it. John is like the core. What is the biggest piece of IBM's business is services. That Army of services, both from IBM and all of their Esai partners and everybody they worked with Khun really supercharge and help scale some of the environment that red hats doing so really interesting. Expect them to talk a little bit about it. Red hat is way more transparent than your average company. They had an analyst event like a week or two after it happened, and I was really surprised how much they would tell us and that we could talk about publicly. As I said, just cause I've seen so many acquisitions happen, including some you know, mega ones in the past. And we know how little usually you talk about until it it's done and it's signed. And, you know, the bankers and lawyers have been paid all their fees. >> Let me ask you, you raise an interesting point. Um, you know that there are some different approaches, obviously, between IBM redhead, just in terms of their institutional legacies in terms of processes. Red hat. You mentioned very transparent organization. Open source. Right. So we're all about the rebrand. They come out, you know, the drop shadow, man, They got the hat. What's that cultural mix going to be like? Can they truly run independently? Yeah, they're a big piece. So And if your IBM can you let that run on its own? >> So, John, that is the question most of us have. So, you know, I've worked with Red Hat for coming up on twenty years now, you know, Remember when Lennox was just this mess of colonel dot organ. So much changes that red hat came and gave, you know, adult supervision to help move that forward on. The thing I I wrote about is what Red Hat is really, really good at. If you look at the core, there do is managing that chaos and change on the industry. If you look how many changes happen, toe Lennox, you know every you know, day, week, month and they package all that together and they test all that same thing in Kou Burnett is the same thing in so many different spaces where that open source world is just frenetic and changing. So they're really geared for today's industry. You talk what's the only constant in our industry? John is it is changed. IBM, on the other hand, is like, you know, over one hundred years old, and I tried and true, you know, Big Blue. You know, I ibm is this, you know, the big tanker, you know, it's not like they turn on a dime and you know, rapid pace of change. You think of IBM, you think of innovation. You think of, you know, trust. You think of all the innovations that have come out over the century. Plus do there and absolutely there is a little bit of impeded mismatch there and we'LL see So if ibm Khun truly let them do their own thing and not kind of merged suit groups and take over where the inertia of a larger group can slow things down I hope it will be successful But they're definitely our concerns And time will tell we'll see But you know analytics front You know, they just announced this morning Rehl eight Red hat enterprise linen, you know, just got announced and definitely something will be spent a lot of time So >> let's just jump in a relative Look again, We're gonna hear a little bit later on. We have several folks coming on board to talk aboutthe availability. Now what? What do you see from the outside? Looking at that. What is it going to allow you or us to do that? Seven Didn't know. Where did they improve? Is that on the automation side? Is it being maybe more attentive, Teo Hybrid environment or just What is it about? Really? That makes that special? >> Yes. So you know, first of all, you know these things take a while in the nice thing about being open sources. We've had transparency. If you wanted to know it was going to be in relate. You just look in the Colonel and and it's all out there. They've been working on this since twenty thirteen. Well, seven came out back in June of twenty fourteen. This has been a number of years in the mix. You know, security. The new, like crypto policy is a big piece that that's in their thie bullets that I got when I got the pre briefing on, It was, you know, faster and easier Deploy faster on boarding for non lennox users on, you know, seamless nondestructive migration from earlier versions of rail. So that's one of the things they really want to focus on is that it needs to be predictable, and I need to be able to move from one version the other. If you look at the cloud world, you know, when you don't go asking customers say, Hey, what version of Azure a ws are you running on your running on the latest and greatest? But if you look at traditional shrink wrap software, it was well, what virginity running? Well, I'm running in minus two and Why is that? Because I have to get it. I have to test it out. And then I, you know, find a time that I'm gonna roll that out, work it in my environment. So there is stability and understanding of the release cycle. My understanding is that they're going to do major releases every three years and minor releases every six months. So that cadence a little bit more like the cloud. And as I said, getting from one version a rail to the next should be easier and more non disruptive. Ah, a lot of people are going to want manage offerings where they don't really think about this. I have the latest version because that has not just the latest features but the latest security setting, which, of course, is a major piece of my infrastructure today to make sure that if there was some vulnerability released, I can't wait, You know, six or nine months for me to bake that in there. The limits community's always good have done a good job of getting fixes into it. But how fast can I roll that out into my environment is >> something I would assume that's that's a major factor in any consideration right now is is on the security front, because every day we hear about one more problem and these are just small little issues. These these air are could be multi billion dollar problems. But in terms of making products available today, how Muchmore important? How's that security shift? If you could put a percentage on it used to be, you know, axe and now it's X plus. I mean I mean, what kind of considerations are being given? >> You know what I'd say? Used to be that security got great lip service A. Said it was usually top of mind, but often towards bottom of budget. When you talk to administrators and you say, Oh, hey, where's your last security initiative? And that, like I've had that thing sitting on my desk for the last six months and I haven't had a chance to roll that out. I will get to it, but I want to again. If you go to that cloud operating model. If you talk about you know Dev, Ops movement is, I need to bake security into the process. If I'm doing C i D. It's not, I do something and then think about security afterwards. Security needs to be built in from the ground level. A CZ. You know, I I've heard people in the industry. Security is everyone's responsibility, and security must be baked in everywhere. So from the application all the way down to the chipset, we need to be thinking about security along the bar. Mind it is a board level discussion. Any user you talk too, you know, you don't say, Hey, where's the security sitting? Your priorities. You know, it's up there towards the top, if not vey top, because that's the thing that could put us out of business or, you know, definitely ruin careers. If if it doesn't go >> right, so there are there are probably a couple of platforms, every will or pillars. I think you like to call them that. You're looking forward to learning more about this week. I think in terms of red hats work one of those green hybrid cloud infrastructure, and we'LL get to the other to a little bit. But just your thoughts about how they're addressing that with the products that they offered the services they offer and where they're going in that >> Yeah, so look everything for red at start with rail. Everything is built on Lenox, and that's a good thing, because Lennox Endeavor is everywhere. If last year is that Microsoft ignite for the first time. And when you hear them talking a Microsoft talking about how Lennox is the majority of the environment, more than fifty percent of the environment are running linen goto a ws Same thing. All the cloud deployment Lennox is the preferred substrate underneath and Rehl doing very well to live in all those environment. So what we look at is, you know, some people say, is this olynyk show. It's like, well, at the core. Lin IX is the piece of it and relate the latest and greatest substantiation. But everywhere you go, there's going to be Lennox there from doing container ization. If a building on top of it with the the new cloud native models, it's there. And if you talk about how I get from my data center to a multi cloud environment, it's building things like Cooper Netease, which read that of course, uses open shift and you know those ties to eight of us and azure and you know, Google they're all there. So we mention Santina della's on stage tonight at Microsoft build. Yesterday there was announcement of this thing called Kita ke e d A, which has, like as your functions and ties in with open shift and spend a little time squinting it, trying to tease it apart. We've got some guests this week that'LL hopefully give some clarity, but it is. The answer is people today have multiple clouds and they have a lot of different ways they want. They want to do things, and Red has going to make sure that they help bridge the gap and simplify those environments across the board. Two years ago, when we were at the show big announcement about how open shift integrates with a W s so that if I'm using a ws But I want to have things in my environment still leverage some of those services. That was something that that Red had announced. I was, you know, quite impressed a time it was, you know, just last week being at the Del Show, it's V m. Where is the del strategy for how they get you know, A W, S, G, C, P and Azure and, you know, Red Hat does that themselves. Their software company. They live in all these cloud worlds, and therefore, open shift will help you extend from your data center through all of those public cloud environments on DH, you know? Yeah. So it's fascinating >> you've talked about Lennox to we're going to hear a little bit later on to about a fascinating the global economic study, that Red Hat Commission with the I. D. C. Of that talks about this ten trillion dollar impact of Lennox around the globe like to dive into that a little bit later on. >> Yeah, well, it's interesting, you know, it's the line I used is you say, and you say, Oh, well, how much impact is Lennox had? You know? You know, Red hats now, a three billion dollar company. That's good. But I was like, Okay, let's just take Google. You know, no slots of a company. Google underneath. It's not Red Hat Lennox, but Lennox is the foundation. I don't really think that Google could become the global search and advertising powerhouse they were. If it wasn't for Lennox to be able to help them get environment, there's a CZ we always talk with these technologies. You talk about Lennox, you talk about How do you talk about, you know, Cooper Netease? There are companies that will monetize it, but the real value is what business models and creation by. You know, all the enterprise is the service riders in the hyper scales that those technologies help enable. And that's where open source really shines is, you know, the order of magnitude network effect, that open source solutions have that its you say okay, three billion dollars? And is that what ten trillion dollars? It doesn't faze me, doesn't surprise me at all, but because my attention it look it. I'm not trying to trivialize. There's no But, you know, I've been watching clinics for twenty years, and I've seen the ripples of that effect. And if you dig down underneath your often finding it inside, >> I mentioned pillars that you were talking about cloud native development being another. But automation, let's just hit on that real quick before we head off on DH just again, with how that is being, I guess, highlighted. Or that's a central focus at and relate and and what automation? How that's playing in there I guess the new efficiencies they're trying to squeeze out. >> Yes. So? So what we always looked for it shows you're probably the last year is you know, you. How are they getting beyond the buzzwords? Aye, aye. When you talk about automation on area that that we've really enjoyed digging into is like robotic process automation. How do I take something that was manual? And maybe it was a fish injure? Not great. How can I make it perfectly efficient and use software robots to do that? So where are the places where I know that the amount of change and the scale and the growth that we have that I couldn't just put somebody to keyboard, you know, and have them typing or even a dashboard to be able to monitor and keep up with things? If I don't have the automation and intelligence in the system to manage things, I can't reach the scale and the growth that I need to. So where are you know, real solutions that are helping customers, you know, get over a little bit of the fear of Oh, my gosh, I'm losing a job. Or will this work or will this keep my business running and oh, my gosh, this will actually enabled me to be able to grow work on that security issue if I need to, rather than some of the other pieces and help really allow it agility to meet the requirements of what the business requires to help me move forward. So those are some of the things we kind of look across the shows. So, you know? Yeah. How much do we get? You know, buzzword, Bingo at the show. Where How much do we hear? You know, real customers with real solutions digging in and having, you know, new technologies that a couple of years ago would have had a saying, Wow, that's magic. >> But you say, Oh, my gosh. Yeah, and I don't want gosh right back with more. You're watching to serve the cube with the red had summit. We're in Boston, Massachusetts, that we'll be back with more coverage right after this

>> From Las Vegas. It's the cute covering knowledge sixteen Brought to you by service. Now carry your host David, Dante and Jeffrey. We're >> back. This is knowledge. Sixteen. This is the Q. We go out to the events. We extract the signal from the noise. This is day one of a three day Walter Wall coverage. The Cube has of knowledge. Sixteen Hashtag No. Sixteen like a lander is here. He's the CEO and vice chancellor of college services at Lone Star College. Longtime Cuba Lem like it's great to see again. >> Good scene again to >> another is >> great to catch up with this >> place, Another knowledge have a bigger and better than ever. You're you're speaking later on this afternoon. You've been over at the CIA event house this year going for you. You know, it's going >> great. The CIA oven, of course, is excellent lot of leadership foundations. Keynote TOC where, you know, service now is heading right now. Kind of. You know, that the shift and I always were still back to one of the themes from eons ago. Let's kill email. But the reality is emails not dead. So as we focus on it, you know, I came into this from the stance of moving the enterprise service management. So as I bring a team here, we really get the opportunity to see where we're at today in that comparison, and then how we can leverage the platform and move yourself forward >> So your role is evolving at Lone Star College, You said off camera, you're not giving up a title. A CIA, your CEO. >> Yes, I am the CEO >> and bread. That's not Teo, but your responsibilities are expanding. Talk about that side of things well, >> so well, last year actually been a year and a half. Now human resource is put underneath me. That's why the title change and all that to fit better and then analytics because, you know, analytics is not it much. People want us to think it should be buried inside of it. It never should, because it's about the business process. About the business service human resource is was just around the concept of aligning that service management what we had completed in it around service excellence. One of my right hand's basically put it as customer delight. Our focus is on customer no light. So it is about that communications piece. How do you talk to your customer? How do you move forward? How do you understand what their challenges are and help them find a solution. It may not be its instead of saying no, I can't do that for you. Sorry. You're out of luck. So in that, in that evolution, we've really moved ourselves forward on the enterprise service management platform side and early days, financial aid. We brought in student call centers. Now you've got human. Resource is were talking earlier about We're moving our legal in there. It's going to accelerate the pace it takes to get a contract illegal down TTO one day, maybe two days or some way didn't catch their approvals fast enough. So that's the big transformation from an organization >> of automated. That whole process over I actually, before going, I want to ask you questions about analytics. So you have. Ah, datas are that's working for you outside of it. Is that right or you? The days are >> well, you know, I actually have a team, >> have a data >> team s o. We're talking two different sets. Analytics too, because we're actually using service now. Analytics when it comes to the Service management analytics. Right. But for the organizational analytics, we actually have a large team that that does our analytics everything from dash boarding through, You know, in our case, core institutional reporting that's required. >> And is there a chief data officer as part of that team? >> I have a personal leading that group. >> De facto even >> factor. Yes. >> So there's a lot of discussion to about whether the CDO should report to the c. E. O. In this case, it does. But you had you had said things questions as to whether or not that Data Analytics function should be in it. It's not a night function. We kind of agree on that, but yes, but what kind of reports in to the head of, Well, >> you know, But see, when I when I sit down at that table, I sit down as the vice chancellor college services. So I have to sit down with three separate hats in front of me. Andi, I can't favor one over the other. Otherwise I wouldn't be doing my job currently. So when I look at the analytic side from a perspective, I will get on my team that provides the data, my database services and, you know, why are you not getting this done or what's happening here? So I've gotta look at it from all areas >> like Bill Belichick, GM coach way Tom Brady. You got to figure out who >> you are. At that point, I'm >> well. So is this how the role of the CEO is evolving? I mean, we've heard of this event previously. Frank's Lupin one year a couple years ago, said CEO should be a business person. Absolutely certainly seen examples of that. Now you're sort of given responsibility for you. No other services beyond just services. How was that role evolving? >> Well, rolls about for years. The question is, Is the CIA evolving? So? And that's where the challenges in the organization. So a lot of CEOs they're going through this process now where they're understanding that, Yes, I need to understand what are the business goals and objectives howto achieve those goals howto I had value to the organization. How did not become a cost center that has a target on my back? How you become an enabler enabler for the business And that's really where we came into that part of the process because we're recognized that Alcide nightie was here trying to help find solutions and provide better customer service. I myself come from a background in higher it for a long time through different institutions. And so when somebody talk to me about student services or student success, these air topics, I understand. I came to Lone Star originally because I didn't feel I had the strength in the academic side. And so when I first arrived there, I was really focused on academic understanding how the academic side operates and what they need in it. So I've had the opportunity to get well rounded in education, but it doesn't. It really is just about anybody that comes into this role. You must understand the business you're in, and then the next part is you need to be able to talk. I have an intelligent conversation around a topic area, bring value to the organization and come back with ideas. Well, you know, if we did this so the legal one was rather interesting because we had a new general counsel. Come on, and we're trying to help him, and he's like, Well, there has to be something better. You ask me. It's a better way to approach this. And we were able to dig through. Is that you know, What service? Now we've been doing this in HR. We're doing this here. So finally, we've got them into service now. And they see an opportunity the same way we see it. Which is we're improving. We're getting rid of the little stuff, the mundane work, You know that the task orientated work and we're focusing on the things that are really a challenge. And it has been there for a while because self service and all the other opportunities we've given the customer. Now we can shift that back and say, Okay, I cannot focus on what does the hard thing to get completed. How Doe I really put in effort in and a lot of a lot of staff hours into this one piece. >> So you started service management You mentioned hr Legal >> Financial Aid General Student Carlson are We're looking at scholarships right now. We tell a little bit ideas around our foundation in scholarships and what we could do for them. Grants. Grants are very big challenge because you have to really track and trend your grants. When you look at it, sm the areas that we've matured there are phenomenal, and then we're getting ready now to move and I Tom, which we didn't do because we already built a complete structure around that we were feeding that to service now. So now I'm looking at from opportunity that if I can eliminate a lot of the tools, I put in a play and get into one single tool and maximize the value of that tool. So I think you heard me many times when we talked in this. It's never about the tool. It's always about people in a process first. And then how does the tool come in? Well, this platform, we can actually adjust that because we're not We're not bound by the tool. Like the legal module. They have a great legal module. Well, it didn't fit what we needed. So it's been adjusted accordingly. T meet our needs from the platform side by keeping the core components so we haven't customized. We haven't taken it to a path where we can never upgrade. But at the same time as we looked at the process they had and how do we take that process and then actually put it into play with service now? >> And they were all inward service now do you worry about locking? >> Always. I think >> that Do you manage that risk? >> Well, the very first thing, to be honest with you is any time you enter in any cloud situation or any product situation, you want an exit strategy of some kind In case something goes wrong, something happens. You have to be at that point. So the only way to manage it really is to one. Keep a good, strong partnership. I believe that I have a strong partnership was service now. I don't believe it's a vendor relationship and I think that's critical because as we look at what we're doing each time as a partner, were were engaged with things like Where you heading? What's happening next? You know what? And then the same thing with the user group community were engaged with that group. So from a partner standpoint, we look at that first. But if the worst case scenario came, I've got to be able to get out of the solution. I've gotta have an exit strategy which we actually had designed before we went into it. Now the question becomes is we get further and further entrenched. What do we do and I'm comfortable. I'm comfortable that the company and the operations are going the right direction for me at the same time. If I'm gonna protect my organization to make sure we're safe. >> And that's a big, big part of transparency on the part of service now and your ability to communicate, you know your road map and your needs, I mean, a scale of one to ten ten being, you know, really transparent. How Where would you put service now as an organization >> who? That's a tough one, Especially when I'm sitting here. >> Uh, Frank's not around is a freaking God. He's breathing guy. Let's see. You know, >> a CZ forest transparency. I would give him good, strong seven. >> Yeah, >> I think I would. No company can be completely transparent. They've got a lot of things working in the back room or ideas that they're moving forward >> because they don't know. They don't know what they don't know. Going. Yeah, >> but there's there's ideas that they have that they're moving forward. It's gonna like today with the watch demo. I'm like, Oh, yeah, I love wearables. I you know, I live off. I could very easily now just say Oh, yeah, I just >> got an e mail. Sorry. Yeah, but, >> uh, at the same time is, you know, for them to bring that forward at this point. So they're creative and looking at these items, but they don't want to get out there too soon. >> I'm curious on the partner vendor, you know, mentioned a couple aspects of what defines that relationship of all the vendors you have. How many do you consider to be? You know, close business partners where your, you know, really sitting at the table and building a long term relationship, You gotta have an exit, but its life so much easier. If >> you're working with a partner verse a vendor right now, I would stay out of our partner strategy. We've got four. That's it. But those are four core providers for the organisation. Their leaders in the market space. That's the other key. Most my partnerships or with leaders, of course service. Now, at the time when we first engaged with them and actually I would say, from a partnership standpoint, a strong partner was service. Now, probably since about two thousand ten, we've been on the platform since two thousand eight. So we built that partnership over that first couple of years. You got past that vendor relationship and then moved on from there. But right now, just our core technology stack would be sitting in that partnership room, and I've got others than in that court Technologies. Technically, I'm not a partner there. A vendor there there were by cell. They have a great product, but they don't really want to bring us into that point. And we really haven't approached that point. >> We had a great discussion off camera about you had mentioned. You're looking at potentially expanding into this security realm with service now. And you were sharing with me like your philosophy on security. So I want to document that The premise that I'm going to put forth summarizing our conversation is, you should organizations increasingly should treat security as an ongoing part of their business continuity plans, not necessarily as a sort of separate stovepipe managed by a few security practitioners. Is that a fair summary? >> Yeah, Service continuity is what I use. I don't have >> service continuity, service continuity, that your business. Yeah, it always comes >> out to service continuity. How do you How do you continue that process and provide the same level of service in the in the event. It's very simple to me as I look at all those events as like problem management incident management, you have a response that you have to take, so it has to be inherit. It has to be natural. You just do it way we're talking about that. That response, specially for security, is what's more important is that you have everything planned out and you're ready to deal with that incident in that rock response because it's gonna happen. So how you handle that response can actually dictate your future, right? Wei had that little bit of that discussion there, too. So it does come down to that service continuity. How do you continue to move forward as and get through that threat and then afterwards make sure that you prevent that from happening again. >> Unlike many CEOs that I talked to, your discussions with the overseers at the college are not entrenched largely in the security discussion. You've earned some level of trust with regard to your capabilities. Is a business your ability to respond. Can you talk about that a little bit? How you actually achieve that, what expectations you were able to set and how you're able to execute on that? >> Well, the biggest, biggest part, especially when you look at it at that event, it's how. How is it performed overall over the history? You've gotta have some history. You've gotta have some credentials. How do you deal with these responses in these emergencies? That gives you a little bit more slack in that process, but it is about constant communications. So what the board received for me is communications. It's very straightforward. Typically, in an annual report type format, Short updates clear, concise updates. But then, when event happens, we're talking about the flood that happened in Houston, and very quickly I had an email out and my service test team was already on it. They already implemented their service continuity because while we may be shut down, we have students online taking classes. We have students that need to know what's going on, what's happening so they're calling in, and our service desk continued on through that entire process without issue. So they see that as an example on a regular basis. If we have a system down, everybody gets to see exactly. We did X, Y and Z or if we even have a like today, I should say today Monday we had a blip. We did, Nam. We have. We saw performance degradation. We immediately had a team on. We had a WebEx open with everything running. So we're preparing for a service continuity event that didn't happen. And they see those two because the business units are getting these notifications. Hey, we've gotta WebEx open. We have this issue coming up, and when they see that, they realize how fast we are to respond to what could be a potential issue that we built that trusting relations. >> So that's a good example. If I understand it correctly, the regime that you've put in place puts a heavy emphasis on the response. I mean, obviously you're trying to stop the bad guys who wouldn't go innovated on the response as well. Is that a fair assessment? >> Yes. I mean, the threats, goingto threats gonna happen. The threat happens all the time. So it is about that response. It is being quick to respond to communicate and take care of the problem. >> Do you think that's changed amongst the CEO community in the last ten years that that the shift in mindset toward that response versus so to keep him out big dig a bigger mode, Wider moat. >> Well, you can dig a big, wide moat. Doesn't matter. >> I think I've >> got these big, robust to hot data centers. Amazing firewalls. They're redundant. You tried overload him. They're going to take over. I've got next gen firewalls behind that. I've got you. Just you, layer layer. This tax of protection I have put in you still have to prepare that we're talking about it is Okay, so that's the perimeter. Well, inside my perimeter is one hundred thousand students, those hundred thousand students around my network. So how do I protect against that? So now I have inside perimeter protection. You can build all this entrenchment that you want to build. But the reality is you need we prepared Just gonna happen that you are. Somebody is going to get to that point. Or at least then the alarms up that you have to respond to >> service now is talking yesterday at the financial analyst meeting about you know, the statistic. And I've heard a range here, but it's large that that after an intrusion it takes, on average two hundred five days for the average organization toe. Realize that there's been an intrusion. I've seen numbers as high as three, three, three, fifty, etcetera. Um, first of all, does that sound consistent with what you see in there in the real world and conservative now help compress that time. >> So the interest was service. Now, of course, is tracking and trending those responses. I, tom and Service watch. There's a lot opportunities with those tools and course we have a perimeter we have a pile of tools were using. In our case, our threats are a bit different because, of course, we're not a big financial institutions. So we were not right with all those other pieces. But you're from the days to recover from a major event and my peers and what that have actually experienced a data loss event? Yeah, it easily is that it is easy. That >> and you think, feel is, though that service now could help you attack that compress that >> yes, mainly through the data collection and then the reporting and then as the events going on all of this information that's happening in the problem management side. What you're seeing from outside information coming in and technicians on the inside updating information as they go through it. You have a comprehensive log of the event from start to finish. >> Now you're speaking just right after this. I think you're just what? You're what you're talking about. >> The shift for my tea service management. Teo Enterprise Service Management. It's actually Enterprise. Wow. But I'm actually walking through the journey. But the best part about that is it's the pitfalls we learned along the way because Wei didn't know we went to Enterprise Service Management. It's kind of I think we had a discussion when we went to the cloud. I didn't know we went to cloud. Exactly. I just knew we went to this heavy virtualization, these two out data centers and I kind of realized, Wow, we really pushed into this new this new wage, this new change. >> We've got a new operating model on on, >> you know. But now yeah, it really is about how we are journey to enterprise service management and the fact that we actually started in a price servicemen before I've even heard of it. It just was around The fundamentals of Hungary. Better service provider. How can we help our customers, uh, achieve their objectives and the business units make it simpler? >> My last question is, what's exciting you these days? A CEO practitioner. What? Float your boat? True. >> What's exciting? You see, I asked if you're gonna give me any hard >> questions for you. That's exciting. >> You know, What excites me is that you're seeing the maturity level of a cloud. The platform side. It is so flexible that you can respond to a customer need quickly that you, khun dynamically spin up the capacity Your When I first started this process, trying to build this high availability was difficult. Now hie availability is really not difficult. It's just around. The process is so that the maturity of the technology and the maturity the service piece that excites me. But it also excites me when I start seeing new team, people come into the market space and they understand that already they're coming in with an idol understanding there they're coming down, understand that business mentality. So original Lighty practitioners didn't have that business background. They didn't have that communication skill you're seeing a lot more of it. The organization now. >> Well, you're a real leader in this space. You've got a lot of experience. Appreciate you sharing your knowledge. And I'm sure the service now community does as well. So good luck with your talk this afternoon. And thanks again for coming. >> Thank you. It's great being here. >> All right, Link a lender. Always a pleasure. Keep right, everybody. This is the cue. We'LL be back Live from Mandalay Bay. This is knowledge sixteen. Right back. >> Service. Now is the time.