>>Live from Copenhagen, Denmark. It's the Q covering Nutanix dot. Next 2019 brought to you by Nutanix. >>Welcome back everyone to the cubes live coverage of dot. Next here in Copenhagen. I'm your host, Rebecca Knight along with my cohost Stu Miniman. We are joined by Sammy Zog LaMi. He is the SVP sales Europe, Nutanix and Sylvan CU. He is the senior director systems engineer for EMEA at Newtanics. Thank you so much for coming on the cube for you for returning. And this is your first time. >>First time. Absolutely. >>Well I want to, I want to start with you. You were on the main stage this morning and you were describing being one of the first few employees in France, working out of hotel lobbies, keeping all the promotional materials in your house and people not even knowing how to pronounce Nutanix. Now here you are for you six years later. Describe, describe a little bit what it, what, what this journey has been like for you. Being at Nutanix >>for this journey. Um, you know, is a, is a successful journey obviously, uh, where we started from scratch in Eva, uh, where we built a lot of relationship with the channel. We started to have our first stories with customers and, uh, you know, the only thing we could not, uh, you know, focus was the speed of growth. And I, if you told me six years ago that we would be four and a half thousand, you know, in this conference, I wouldn't have believed it. And I think the, you know, overall journey is a, you know, an accelerated journey of development and that we have, >>yeah, Sam, Sammy, prednisone side, a little bit about, uh, you know, we sometimes call it nation building, but, uh, you know, the channel of course, a very important, uh, you know, talked about some of the, kind of, the challenges in, uh, some of the successes as to what, what has made Nutanix so successful, uh, in, in your time. Yeah. I think, uh, >>you know, the technology is for sure a big element in this that is solving business problems. But when you think about it, there's many stories of great technologies that didn't make it or didn't make it big. So I think the openness of this company from day one, uh, to work with partners to work with an ecosystem of Alliance partners. Uh, we were also very open to share how the Nutanix technology is built and is working. So there's a lot of openness around your Hasise works. It's not a black box. Uh, and we integrate with the ecosystem. So for our positioning, which is mainly initially the data center, the large environments we have to integrate into customer environment, we have to integrate with existing technologies and uh, the fact that we are open from day one and we keep that line is helping a lot in the traction. >>I want to get into that strategy in a little bit, but I want to bring you into this conversation to Sylvan and, and just to have you talk a little bit about what you're seeing in the competitive landscaping, what, what are some of the things that Nutanix needs to focus on? Because the competitors are a really edging in. We are focused to deliver >>our vision and continue to build the pieces that are still under construction there right now. And to be back on the question about the partners, the adoption also come first from the partners before their customers. And really working with them on engaging with them was the result of the success was not just signing contract enabled them, but really engaging with them at customer sites. And as soon as they see the reaction of the customer, they can be believe in it. And we scaled very fast because of them. I'm wondering, get both of your comments. Talk about the, uh, the competition for talent. Also, when you talk about Nutanix over 5,000, the channel is very strong. It makes it a little bit tougher, uh, to kind of pull those pieces in. If you're Silicon Valley, Oh, there's this startup, I want to join, things like that, but have to imagine things are a little bit different. And I'm in Mia, >>I would say. Well, competition for talent is definitely here in Emir, especially on the topics that we are tackling in the cloud, the DevOps, big data, et cetera. Um, now, you know, we are not attractive brand, uh, you know, there's a demonstrated pass of development for our employees. So I think on top of being a successful company, we have a lot of proof points of building careers. So people want to join for the fun for the success. We are also to be able to fast career. That's helps now saying that it's still not an easy task. You know, there's a, especially the volume of recruitment we are doing, uh, so we have organized ourselves very well, uh, to onboard people, enable people and maybe be in a position to hire people that don't have all the skills but have the right DNA and then we can, you know, always teach the skills. That's the way we are. >>and on a technical side, uh, all the user's previous it vendor let's say, was looking for specialists of complexity. You know, what is the behind the scene and we are in different situation, meaning that we can start small first and we talk about the project of the customer. And until this project works, we cannot move forward. We cannot obsessive. So our situation is more consultative and being a trusted advisor of what they tried to achieve and not anymore on what we tried to build our own our side. >>That's a very important point. The mindset of successful employees are the ones that are focused on the outcomes. You know, they're not here to sell a product, they focus on project and the outcome of customers. >>So how do you find that person when you are, when you're interviewing your pool of applicants? I mean that, that is, that is such an important part of the culture here, this people first attitude and really being all hands on deck if a customer has an issue. So how do you, how do you know when you're interviewing someone that, that, that they have got their, the right DNA to be here? >>Well, first we knew before they, during the interview, because we are well connected on the market and we have sources of information about how they operate on day to day. Now, of course, of hiring so many people over the years helps. And there's a lot of small details that, you know, we can notice, uh, in, uh, in our recruitment process. I think we've gotten very professional in the way we recruit. We still have a lot of refills as well from employees, which helps in terms of, uh, you know, making sure we hiring the right DNA, but we want to diversify. We don't want people coming from the same background. We're doing a pretty good job on diversity, on every topic, you know, gender, ethnicity, background, uh, this is a, you know, pretty good success. Alright, so >>semi you, you've got a new role. So it gives us a little bit of insight as to your vision. What should we should expect to see as a strategy for Nutanix and EMEA? >>I would say first, uh, you know, three months on the job and I have no intent to break anything that works. Uh, I think there's a successful recipe in anemia, which is a legacy of Chris Keller Ross. Uh, lots of good methodologies, verse of good principles of working, no intention to change that and maybe the phase after that for MEA, but for the whole company is to focus on Australia. And we see that, you know, our technology is well suited for mission critical environment is well suited for strategic projects for customers. And maybe we should become the default, uh, you know, uh, vendor that you think about when you go for mission critical projects and you know, trust formation. Uh, I think today we do a very broad set of projects with customers. Um, tomorrow I would like customers to think first about Nutanix when they think about something that is critical to their business. >>And in the same way for partners, uh, if we can move from being a vendor with high grows, great margin to a vendor that is helping them transform, you know, their business model or the way they attack different segments, you know, then we will have achieved a good phase two. What do you see as the biggest challenges facing you right now? Well, the biggest challenge is inside clearly is growth. We see that in every area, every time we grow fast, then suddenly you need to change organization processes, your principle of working and you, you need to reassess yourself and your way of doing things. Even at pesonal level. Uh, that's the biggest challenge. I think we, if we are not constantly paranoid about re re assessing that uh, growth can break a lot of quality, uh, in the relationship we have with customers but also in our velocity. >>Oh, I wonder if you could bring us inside the customers a little bit. What are some of the key roles that you find in, you know, where does Nutanix has the best engagement with and you know, strategically where would Nutanix may be a change over time as to where they're, where they're engaging with a customer. >>So now there is no more question about the fact that part of the, it will be in the cloud part will be internally, some people will go more one side or the other side because Nutanix both technology >>on both sides, we can take care of old school application and be sure that can still run in the cloud. And on this society, if you develop an application totally distributed and so on, meaning a cloud native, we can run it on a Nutanix and all the platform looks like the pubic cloud for this application. So we are the unique situation where we can, we don't need to be in the cloud or outside of the cloud, meaning that we can give a strategy with the customers or what it can do. What is the good point, what is the most difficult to achieve on both sides. And also we provide a way to package application to deploy everywhere. We have all these governance tools on top of it because we know the new way of consuming the cloud is more open bar, which you need some way of controlling the situation and we are really trusted advisor on their strategy to define what will be their it in two, three or four years. >>Okay. So sounds like not just the infrastructure owner but talking to the application owner or some of the C suite that might make some of those broader strategic decisions. >>Yeah. Yeah, exactly. Uh, the platform works, meaning that there is no more cushion on that at scale. You get all the benefits that you can see on the, on the public cloud. Now it's more the way you consume it, you organize the consumption and also you've have those, the same of urine Mount whatever is the application, uh, to, to find the, to have the best place for this application. >>What would you say your, your, your here as you said, uh, at in Copenhagen, thousands of European customers all here under one roof. What are you getting out of this? What kind of conversations are you hearing? What's most surprising to you? Just to, I mean we're, I know we're only in the beginning of day one, but what, what do you, what are you hearing right now? >>Well, we talked to a few customers already and what's a very common pattern? Most of the customers I took so far, they really accelerating on becoming a service organization. So enterprise companies, they really want to organize themselves to be cloud ops. And even though we were talking about automation before, now they really are doing it and they are actually focusing on changing the skills of their teams, their organizations and of course the technology afterwards. >>Yeah. Uh, any, any particular is on automation. Cause I think back, we've been talking about automation my entire career. I agree with you today. It is a, you know, more substantial conversation on automation. Are there any particular as either in Newtanics portfolio where some of the kind of partner tooling out there that are kicking things along? >>So, uh, we talk about automation since a long time, but most of the time that was, you have an orchestrator, it's like a Swiss knife and you can orchestrate what you want, but at the end of the day, nothing was done. We believe that the platform must be automated by design, right? And everything need to be by design. So it's a, it's the difference between the, between the previous way of thinking, automation and now where the platform is totally it. >>I believe Leber GF said autonomous is what >>we were looking for. Yes. You got to the point. If it's not autonomous, why? Why bother? Yeah. Or we had examples of customers who launched private cloud projects and they had like 8,000 Mondays to build the orchestration of the private cloud. And honestly, if you don't have a a hundred thousand VMs to run, it makes no sense. So the fact that no, it's built in and it's not a project to have automation, you know, that makes sense economically as well. Great. Well semi and see you. Thank you so much for coming on the cube. It's a pleasure having you later, Rebecca. Thanks a lot. Thank you. I'm Rebecca Knight for Stu Mittleman. Stay tuned for more of the cubes live coverage of.next.

(soft electronic music) >> Announcer: Live from Vancouver, Canada, it's theCUBE. Covering OpenStack Summit North America 2018. Brought to you by Red Hat, the OpenStack Foundation, and it's ecosystem partners. >> Welcome back, I'm Stu Miniman here with my cohost John Troyer and you're watching theCUBE's exclusive coverage of OpenStack Summit 2018 in Vancouver. Happy to welcome you back to the program, off the keynote stage this morning, Mark Shuttleworth, the founder of Canonical. Thank you so much for joining us. >> Stu, thanks for the invitation. >> Alright, so you've been involved in this OpenStack stuff for quite a bit. >> Right, since the beginning. >> I remember three years ago we were down in the other hall talking about the maturity of the platform. I think three years ago, it was like this container thing was kind of new and the basic infrastructure stuff was starting to get, in a nice term, boring. Because that meant we could go about business and be on the buzz of there's this cool new thing and we're going to kill Amazon, kill VMware, whatever else things that people thought that had a misconceived notion. So bring us forward to where we are 2018, what you're hearing from customers as you look at OpenStack and this community. >> Well, I think you pretty much called it. OpenStack very much now is about solving a real business problem, which is the automation of the data center and the cost parody of private data centers with public data centers. So I think we're at a time now where people understand the public cloud is a really good thing. It's great that you have these giant companies dueling it out to deliver better quality infrastructure at a better price. But then at the same time, having your own private infrastructure that runs cost-effectively is important. And OpenStack really is the only approach to that that exists today. And it's important to us that the conversation is increasingly about what we think really matters, which is the economics of owning it, the economics of running it, and how people can essentially keep that in line with what they get from the public cloud providers. >> Yeah, one of the barometers I use for vendors these days is in this multi-cloud world, where do you sit? Do you play with the HyperScalers? Are you a public cloud denier? Or, like most people you're, most people are somewhere in-between. In your keynote this morning, you were talking a bit about all of the HyperScalers that use your products as well as-- >> Ubuntu is at the heart of all of the major public cloud operations at multiple levels. So we see them as great drivers of innovation, great drivers of exposure of Ubuntu into the enterprise. We're still, by far, the number one platform used in public cloud by enterprises. It's hard to argue that public cloud is testing Dev now. It really, really isn't and so most of that is still Ubuntu. And now we're seeing that pendulum swing, all of those best practices, that consumption of Ubuntu, that understanding of what a leaner, meaner Enterprise Linux looks like. Bringing that back to the data center is exciting. For us, it's an opportunity to help enterprises rethink the data center to make it fully automated from the ground up. OpenStack is part of that, Kubernetes is part of that and now the cherry on top is really AI where people understand they have to be able to do it on public cloud, on private infrastructure and at the Edge. >> Mark, I wanted to talk about open source. Marketing open source, for a minute. We are obviously here, we're part of an open source community. Open source, defacto, has won the cloud technology stack wars. So there's one way of selling OpenStack where you pound on open a lot. >> I'm always a bit nervous about projects that put open. It sounds like they're sort of trying to gloss over something or wash over something or prove a point. They shouldn't have to. >> There's one about the philosophy of open source, which certainly has to stay there, right. Because that's what drove the innovation but I was kind of impressed about on the stage today, you talked about the benefits. You didn't say, well the venture's open. You said, well, we're facilitating these benefits. Speed to market, cost, et cetera. Can you talk about your approach, Canonical's approach to talking about this open source product in terms of its benefits? >> Sure, look, open source is a license. Under that license, there's room for a huge spectrum of interest and opinions and approaches. And I'd say that I certainly see an enormous amount of value in what I would call the passion-based open source story. Now, OpenStack is not that. It's too big, too complicated, to be one person's deep passion. It really isn't. But there's still a ton of innovation that happens in our world, across the full spectrum of what we see with open source, which is really experts trying to do something beautiful and elegant. And I still think that's really important in open source. You also have a new kind of dimension, which is almost like industrial trench warfare with open source. Which is huge organizations leveraging effectively their ability go get something widespread, widely adopted, quickly and efficiently by essentially publishing it as open source. And often, people get confused between these two ends of the spectrum. There's a bunch in between. What I like about OpenStack is that I think it's over the industrial trench warfare phase. You know, you just don't see a ton of people showing up here to throw parties and prove to everyone how cool they are. They've moved on to other open source projects. The people who are here are people who essentially have the real problem of I want to automate my data center, I want to have, essentially, a cloud that runs cost-effectively in my data center that I can use as part of a multi-cloud strategy. And so now I think we're in to that sort of, a more mature place with OpenStack. We're not either sort of artisan or craftsmen oriented, nor are we a guns blazing brand oriented. It's kind of now just solving the problems. >> Mark, there's still some nay-sayers out in the marketplace. Either they say that this never matured, there's a certain analyst firm that put out a report a couple of months ago that, it kind of denigrated what's happening here. And then there's others that, as you said, off chasing that next big wave of open source. What are you hearing from your customers? You've got a good footprint around the globe. >> So that report is nonsense, for a start. They're always wrong, right. If they're hyping something, they're wrong and if they're dissing something then they're usually wrong too. >> Stu: They have a cycle for that, I believe. (chuckling) >> Exactly. Selling gold at the barroom. Here's how I see it. I think that enterprises have a real problem, which is how do they create private cloud infrastructure. OpenStack had a real problem in that it had too many opinions, too many promises. Essentially a governing structure not a leadership structure. Our position on this has always been focus on the stuff that is really necessary. There was a ton of nonsense in OpenStack and that stuff is all failing. And so what? It was never essential to the mission. The mission is stand up a data center in an automated way, provide it, essentially, as resources, as a service to everybody who you think is authorized to be there, effectively. Segment and operate that efficiently. There's only a small part of OpenStack that was ever really focused on that. That's the stuff that's succeeding, that's the stuff we deliver. That's the stuff, we think very carefully about how to automate it so that, essentially, anybody can consume it at reasonable prices. Now, we have learned that it's better for us to do the operations almost. It's better for us actually to take it to people as a solution, say look, explain your requirements to us then let us architect that cloud with you then let us build that cloud then let us operate that cloud. Until it's all stable and the economics are good, then you can take over. I think what we have seen is that you ask every single different company to build OpenStack, they will make a bunch of mistakes and then they'll say OpenStack is the problem. OpenStack's not the problem. Because we do it again and again and again, because we do it in many different data centers, because we do it with many different industries, we're able to essentially put it on rails. When you consume OpenStack that way it's super cheap. These aren't my numbers, analysts have studied the costs of public infrastructure, the cost of the established, incumbent enterprise, virtualization solutions and so on. And they found that when you consume OpenStack from Canonical it is much, much cheaper than any of your other options in your own private data center. And I think that's a success that OpenStack should be proud of. >> Alright, you've always done a good job at poking at some of the discussions happening in the industry. I wouldn't say I was surprised but you were highlighting AI as something that was showing a lot of promise. People have been a little hot and cold depending on what part of the market you're at. Tell us about AI and I'd love to hear your thoughts in general. Kubernetes, Serverless, and ask you to talk about some of those new trends that are out there. >> Sure, the big problem with data science was always finding the right person to ask the right question. So you could get all the data in the world in a data lake but now you have to hire somebody who instinctively has to ask the right question that you can test out of that data. And that's a really hard problem. What machine learning does is kind of inverts the problem. It says, well, why don't we put all that data through a pattern matching system and then we'll end up with something that reflects the underlying patterns, even if we don't know what they are. Now, we can essentially say if you saw this, what would you expect? And that turns out to be a very powerful way to deal with huge amounts of data that, previously, you had to kind of have this magical intuition to kind of get to the bottom of. So I think machine learning is real, it's valuable in almost every industry, and the challenges now are really about standardizing underlying operations so that the people who focus on the business problems can, essentially, use them. So that's really what I wanted to show today is us working with, in that case it was Google, but you can generalize that. To standardize the experience for an institution who wants to hire developers, have them effectively build machine-driven models if they can then put those into production. There's a bunch of stuff I didn't show that's interesting. For example, you really want to take the learnings from machine-learning and you want to put those at the Edge. You want to react to what's happening as close to where it's happening as possible. So there's a bunch of stuff that we're working on with various companies. It's all about taking that AI outcome right to the Edge, to IOT, to Edge Cloud but we don't have time to get in to all of that today. >> Yeah, and Ubuntu is at the Edge, on the mobile platform. >> So we're in a great position that we're on the Cloud. Now you see what we're doing in the data center for enterprises, effectively recrafting the data center has a much leaner, more automated machine. Really driving down the cost of the data center. And yes, we're on the higher-end things. We're never going to be on the LightBulb. We're a full general-purpose operating system. But you can run Ubuntu on a $10 board now and that means that people are taking it everywhere. Amazon, for example, put Ubuntu on the DeepLens so that's a great example of AI at the edge. It's super exciting. >> So the Kubernetes, Serverless-type applications, what are your thinkings around there? >> Serverless is a lovely way to think about the flow of code in a distributed system. It's a really nice way to solve certain problems. What we haven't yet seen is we haven't seen a Serverless framework that you can port. We've seen great Serverless experiences being built inside the various public clouds but there's nothing consistent about them. Everything that you invest in a particular place is very useful there but you can't imagine taking that anywhere else. I think that's fine. >> Stu: Today's primarily Lando. >> And I think the other clouds have done a credible job of getting there quickly. But kudos to Amazon for kind of pioneering that. I do think we'll see generalized Serverless, it just doesn't exist at the moment and as soon as it does we'll be itching to get it into people's hands. >> Okay, yeah? >> Well, I just wanted to pull out something that you had said in case people miss it, you talked about managed OpenStack. And that, I think, managed Kubernetes has been a trend over the last year. Managed OpenStack now. Has been trans-- >> With these complex pieces of infrastructure, you could easily drown in learning it all and if you're only ever going to do one, maybe it makes sense to have somebody else do it for a while. You can always take it over later. So we're unusual in that we will essentially standup something complex like an OpenStack or a Kubernetes, operate it as long as people want and then train them to take over. So we're not exclusively managed and we're not exclusively arms-length. We're happy to start the one way and then hand over. >> I think that's an important development, though, that's been developing as the systems get more complicated. One UNIX admin needs a whole new skill set or broader skill set now that we're orchestrating a whole cloud so that's, I think that's great. And that's interesting. Anything else you're looking forward to, in terms of operation models. I guess we've said, Ubuntu everywhere from the edge to the center and now managed, as well. Anything else we're looking at in terms of operators should be looking at? >> Well, I think it just is going to stay sort of murky for a while simply because each different group inside a large institution has a boundary of their authority and to them, that's the edge. (chuckling) And so the term is heavily overloaded. But I would say, ultimately, there are a couple of underlying problems that have to be solved and if you look at the reference architectures that the various large institutions are putting out, they all show you how they're trying to attack these patterns using Ubuntu. One is physical provisioning. The one thing that's true with every Edge deployment is there are no humans there. So you can't kind of Band-Aid over the idea that when something breaks you need to completely be able to reset it from the ground up. So MAAS, Middle as a Service, shows up in the reference architectures from AT&T and from SoftBank and from Dorich Telecom and a bunch of others because it solves their problem. It's the smallest piece of software you can use to take one server or 10 servers or 100 servers and just reflash them with Windows or CentOS or whatever you need. That's one thing. The other thing that I think is consistently true in all these different H-Cloud permutations or combinations is that overhead's really toxic. If you need three nodes of overhead for a hundred node OpenStack, it's 3%. For a thousand node OpenStack, it's .3%. It's nothing, you won't notice it. If you need three nodes of OpenStack for a nine node Edge Cloud, well then that's 30% of your infrastructure costs. So really thinking through how to get the overhead down is kind of a key for us. And all the projects with telcos in particular that we're working, that's really what we bring is that underlying understanding and some of those really lightweight tools to solve those problems. On top of that, they're all different, right. Kubenetes here, Lixti there, OpenStack on the next one. AI everywhere. But those two problems, I think, are the consistent things we see as a pattern in the Edge. >> Alright, so Mark, last question I have for you. Company update. So last year we talked a little bit about focusing, where the company's going, talked a bit about the business model and you said to me, "Developers should never have to pay for anything." It's the governance people and everything like that. Give us the company update, everything from rumors from hey, maybe you're IPO-ing to what's happening, what can you share? >> Right, so the twin areas of focus, IOT and cloud infrastructure. IOT continues to be an area of R and D for us so we're still essentially underwriting an IOT investment. I'm very excited about that. I think it's the right thing to be doing at the moment. I think IOT is the next wave, effectively, and we're in a special position. We really can get down, both economically and operationally, into that sort of small itch kind of scenario. Cloud, for us, is a growth story. I talked a little bit about taking Ubuntu and Canonical into the finance sector. In one year, we closed deals with 20% of the top 20 banks in the world to build Ubuntu base and open infrastructure. That's a huge shift from the traditional dependence exclusively on VMware Red Hat. Now, suddenly, Ubuntu's in there, Canonical's in there. I think everybody understands that telcos really love Ubuntu and so that continues to grow for us. Commercially, we're expanding both in Emir and here in the Americas. I won't talk more about our corporate plans other than to say I see no reason for us to scramble to cover any other areas. I think cloud infrastructure and IOT is plenty for one company. For me, it's a privilege to combine that kind of business with what happens in the Ubuntu community. I'm still very passionate about the fact that we enable people to consume free software and innovate. And we do that without any friction. We don't have an enterprise version of Ubuntu. We don't need an enterprise version of Ubuntu, the whole thing's enterprise. Even if you're a one-person startup. >> Mark Shuttleworth, always a pleasure to catch up. Thank you so much for joining us. >> Mark: Thank you, Stu. >> For John Troyer, I'm Stu Miniman. Back with lots more coverage here from OpenStack Summit 2018 in Vancouver. Thanks for watching theCUBE. (soft electronic music)

>> live from the Mandalay Bay Convention Center in Las Vegas. It's the King covering via World 2016 brought to you by IBM Wear and its ecosystem sponsors. Now here's your host stew minimum. Welcome back to the Cube here at VM World 2016. Happy to welcome back to the PO program. Christos Caramel analysts. Who's the fellow in CTO of the V A more storage and availability business unit. Thank you for joining us again. >> About to be buck >> Storage is a big focus here. Big announcements around. Not only the sand, but everything happened in the storage room. Tell us what you've been working on the last year. >> Yeah, quite a few things. As you know, Miss Olsen has become practically mainstream product now, especially since we saved the very same 6.2 back in March 2016 with a number of new enterprise grade features for space efficiency. New availability. Fisher's with the razor calls right 56 The product is really taking off. Taking off, especially in old flask configurations, is becoming the predominant model that our customers are using. So ultimately, of course, customers buy a new product like this on and hyper converts product because of the operational efficiencies and brings to their data centers. The way I present this is you have the personal efficiency off public clouds into your private data center now. But this is for me is thus the stepping stone for even a longer term term, bolder vision will have around the stores, the data management. So, the last several months now, I have been working on a new range of projects. Main theme. There is moving up the stock from stores and the physical infrastructure implications. It has two data management on starting with data protection on overall and managing the life cycle of your data for protection, for disaster recovery, for archival, so that you can have tools to be able to effectively and efficiently discover your data. Mine your data. Use them by new applications, including cloud native applications and a dent even know that this may sound a little controversial coming from Vienna, where sitio even moving your data to public clouds and allow application mobility freely between private public clouds. >> Yeah, it's really interesting and wonder if you can packed out a little bit for us, Veum, where, of course, really dominant, the Enterprise Data Center. We're trying to understand where Veum, where fits into the public cloud on how you cut both support the existing ecosystem and move forward. So, you know, it's interesting off >> course. There are silences. There are many open questions. I do not claim that we have the answers to everything. Everything. But you do see that we put a lot of emphasis on that because it is obvious that the I T world is evolving. Our own customers are gradually slowly, but certainly there start incorporating public clouds into the bigger I T organizations that have. So our goal is to start delivering value to our customers based on clouds, starting with what they have today into the data centers. Let me give you a specific example in the case of Virtual San, who have some really cool tools for Mona's in your infrastructure in a holistic way, computer networking and now stores a SZ part of that you have ah solutions and tools that allow the customer to monitor constantly there covered infrastructure, the configuration of that. The class is the network servers controller's down to individual devices, and we provide a lot of data to the customers, not only for the health but also for the performance off the off the infrastructure data to the customer can today used to perform root cause analysis of potential issues to decide how to optimize there. Infrastructure in the world clothes. But that is actually pretty no sophisticated house. You cannot expect a lot 500 thousands 1000 customers. Of'em were to be ableto do this kind of sophisticate analysis. So what we're working on right now is a set off analytics tools that do all this data Kranz ink and analysis a root cause analysis on DDE evaluation of the infrastructure on because of the customer instead of providing data now we're providing answers and suggestions now way want to be able to deliver those analytics in a very rapid cadence. So what we do is we develop all those things in via Morse. Cloud will collect data from the customer side through telemetry, the emir's phone home product, and we get off the data up in our club. We crunch the data on because of the customer, and we use really sophisticated methods that will be evolving over time and eventually will be delivering feedback and suggestions at a kind level to the customer that can be actionable. For example, weekend point out that certain firm were the 1st 1 off certain controllers, and the infrastructure is falling behind. I may have problems or point out to a certain SS thes uh, a problem getting close to the end off life. For more sophisticated thing. Starts us reconfigure your application with a different policy for data distribution to achieve better performers. The interesting thing is that going to be, you're going to be combining data from must multiple sites, multiple customers to be able to do this holistic analytics and say, You know what? Based on trance, I see. Another customer says. It says You also do that. Now they're really coursing out of this is that the customer does not have to go and use yet another portal on a public cloud to take advantage of that. But they in fact, we send all that feedback through the this fear you. I own premise to the customers, so really cool. So you have the best of both wars. There are big development off analytics using actually behind the senses a really complex cloud native application with the existing tools that the customers are usedto in on premise. So this is just one example >> crystals. Could you give us a little bit of insight as the guiding light for your development process? Do you use that kind of core customers that you're pulling in and working in? Is it a mandate from above that says, you know, Hey, we need to build a more robust and move up the stack. You know, what are some of the pieces that lead to the development that you >> know? This is a very interesting point. I must start by stating that vehement has always bean admitting they're driven company. Um, and look for products were, you know, ideas that were, you know, Martin by engineers, while others thought that was not your not even visible, of course, Mutualization in several stages. But features like the Muslim or stores of emotion Oreo even, you know, ideas kind of ritual, son, right. Claiming that I could do very effectively rate six in software was something that was not really, you know, appreciated in the industrial area stages. So a lot of the innovation is a grassroots innovation. We have our engineers exposed directly to customers customer problems off course. They also understand what is happening in the industry. The trends, whether that is encounter as its case these days with a new generation off first or its cover that is emerging, or where that that is a trend. Samoan customers, for example, using public clouds in certain ways where that is for doing testing dead or archiving their data way. Observe those things and then through a grassroots. Therefore, all this get amalgamated into some concrete ideas. I'm not saying that all those ideas result into products, but we definitely have a very open mind in letting engineers experiment and prove sometimes common sense to be wrong. So this is the process thesis. How Virtual Son started were a couple of us went to our CEO back then for marriage and suggested we do this drastic thing that is called no softer stores on that you can run the soft store of stock in software on the same servers that we visualize, and we're under V. M. So this is really how the process has always been working and this is still the case and we're very proud of this culture. This is one way we're actually tracking opens enduring talent in the competent. >> Yeah, I was loved digging into some of the innovation processes. Had a good chat with Steve Harris, former CEO of GM, where if I remember right? One of the thing processes user called flings, whereas you can actually get visibility from the outside it to some of those kind of trials and things that are going on that aren't yet fully supported yet. >> Absolutely. And that is still the case. Probably the best known fling these days is the HTML five days they you I for your sex, which is used extensively, both internally in the humor where it actually started as a tool for that purpose, but now wild by the community. And that Flynn gave us a lot off insides and how to evolve our mainstream user interface for for this fear, proper notes, Astoria sex. So this is exactly this alternative process that leads us to test the water and feel much more confident when we make bigger and investments in in Ireland, >> right architecturally via Moore has been around for quite a while now. I had a good talk with such a Pagani Who? I m f s earlier today and we were talking about, you know, new applications and new architectures when vms foot fest was built. You know, nobody's thinking about containers. You know, they weren't thinking about applications like duper some of these more cloud native applications. How do you take into consideration where things were going? How did these fit into, you know, kind of traditional VM wear V sphere. You know what things need to change? How do you look at kind of the code basis? >> Right. So first of all of'em affairs, I must say it's probably the most mature and most widely adopted class. The file system in the industry for over 10 years now has been used to visualize enterprise grade store, its stores, alien networks, and it was going to have a role for many years to come. But on the other hand, we all are technologists, and we understand that the product is designed with certain assumptions and constraints, and the EM affairs was designed back in the meat to thousands toe address the requirements for ritual izing lungs, and you know the traditional volumes that you'd be consuming from a disgrace. Now the world is changing, right. We have a whole new generation off solid state devices for stores. Servers on softer on commodity servers with Commodity stores Devices is becoming as your own reports that have been indicating the predominant no mortal of delivering stores in there in the enterprise that the sender and off course in even public clouds with copper scale storage. So what? The requirements there? Some things are changing. You need the store. Its plot from that can really take out the violence of the very low latency is off those devices. I was at Intel Developer for form a couple of weeks ago, and their intel announced for first time performance numbers for the new generation off Envy Me devices obtained that include the three D Chris Point technology under the covers. Latents is at around 10 microseconds, right and Iost per second scruples that are in the several kinds of thousands, if not millions so completely young game changer. And that is not the only company that is coming up with this technology. So you need to invest now in new technologies that can take the can harness the capabilities of this new devices, lightweights protocols like Envy me. In fact, I see envy me as the protocol is not just a protocol to accident device, but I can see a future for that off. Replacing Scott Z into the software start soon, and this is committing specific days. But soon will be sipping a vision off this fear that comes with ritual and via me in the guest visual ization of envy Me. So you can see here where we're heading and envy me, becoming a predominant protocol for the transport and for brutalizing stores. >> Interesting. And we've got a long history of things that start on. The guests Usually then takes a lot of engineering work to get them down to the hyper visor themselves. So, you know, without having to give away too much, is that we see that kind of progression sometime in the future. For some of these new memory, architectures >> certainly certainly are the sex store stock, and this is the stuff that is used by Veum infest by ritual son. It has been designed again for another era off stores. Now we are regarding a lot of these things there, and I cannot disclose too much detail, obviously, but I can tell that it's going to be a very different software stock. Much leaner, much more optimized for local, very fast devices and ultimately envying me is going to be a key technology in this new store stock. >> All right, so just last follow up on that topic. I think about kind of a new memory architectures. What's going on? As of September 7th, Del will acquire TMC. There's the relationship between A. M, C and V M wear. So could we expect some of these new memory technologies impacting things to be something that you'll work even closer with a deli emcee? And >> that is definitely case irrespective off the deal between the emcee and Dell, which, as you said, it's going to be closing. It seems pretty soon. From what I read in the newspapers, >> Michael confirmed, it's finally official. Some of the pathetic ALS. >> Yes, we're moving ahead with this new technologists, and we're working closely with all the partners micro intel and many of the other car vendors that are introducing such technologies to incorporate them into our systems into our software, for example, I see great opportunities for this very fast Cayenne dude owns but still quite expensive technologies to be used, for example, to store meta data. Things like duplication. Costabile is those kind off meta data that have an impact through because of my own verification to the performance that is perceived by the application by moving meta data like that into those tears are going to make a great difference in terms of performance consistent, late and see predictability of the day for the application. Now, thanks to the relations with del Auntie em. See, I can hope that some of these technologies will find their way into several platforms sooner than later. So all of us and our customers would benefit from that. >> All right? What? Christos really appreciate getting the update from you. Lots happening on the storage world. We're kind of talking about. One of my things coming into this this'll week was, if we can really simplify storage, we might actually have a storage. This world doesn't mean it reduces the value of storage or the importance of it, but gonna help the users to be able to move beyond that, we'll be back with lots more coverage here from the emerald 2016. You're watching the Cube. Glad to be here. Whatever. Apply from the Mandalay Bay Convention Center in Las Vegas. It's the King covering via World 2016 brought to you by IBM Wear and its ecosystem sponsors. Now here's your host stew minimum. Welcome back to the Cube here at VM World 2016. Happy to welcome back to the PO program. Christos Caramel analysts. Who's the fellow in CTO of the V A more storage and availability business unit. Thank you for joining us again. >> Glad to be back.