>> The Cube presents Dell Technologies World brought to you by Dell. >> Good evening, welcome back to the Cube's coverage of Dell Technologies World, live from the show floor in Las Vegas. Lisa Martin, Dave Vellante. We've been here two and a half days. We've unpacked a lot of announcements in the last couple days, and we're going to be doing a little bit more of that for our final segment. We've got a couple of guests joining us. Itzik Reich, the VP of the Technologist ISG at Dell and Magi Kapoor Director of Storage Product Management at Dell. Guys, welcome. >> Thank you for having us. >> So great to be back in person. I'm sure great for all of you to see customers and partners and your team that you probably haven't seen in quite a while. But Itzik we want to, we want to start with you VP of the Technologists. That sounds like a, like you need to wear a cape or something. >> Right? Yeah. I wish I do sometimes >> Talk about that role and what you do. >> Right, so our role, we have an outbound part and an inbound part. From an outbound perspective, our role is to ensure that our customers are knowing where we going from a technology perspective. And we do it via conferences or customer calls or via blogs, and think of that nature. But as important, we also have an inbound role to ensure that our employees are knowing where we're going. You can imagine they're a very large company. Not every engineer or any other role knows exactly what we are doing in that space, especially around innovation. So we also ensure that they understand it internally about where we going into that nature. And as a side role, I also have a side job which is to be responsible for our container strategy which has started couple of years ago which I'm sure we're going to talk about today. >> Yeah, that's-- >> Got a side gig. My goodness. >> That's right. >> Maggie, lots of announcements in the last couple of days. Great attendance here. Seven to 8,000 people. Dell's coming off its best year ever, north of 100 billion in revenue and FY 22, 17% year on year growth. What are some of the things that excite you about the strategic direction that Dell is going in with its partners, with the hyperscalers storage bringing it to the hyperscalers? >> Yeah. No lots of great announcements. It's been an exciting week. Like you said, it's been great to be back in person, have these face to face meetings and, you know, see the customers, have presentations in person. Like I feel like we haven't done that in forever. So it's felt really, really great. And announcements, it's been incredible. Like the two keynotes that we had on Monday and Tuesday were both incredible. And so I'd like to talk about a couple of key ones, you know, so just to let you know, I'm a director of product management and I'm responsible for a bunch of pan-ISG initiatives, DevOps and our container strategy being one of those items. And so, you know, we're at this cusp where there are, you know, customers that are on this journey of, you know, developers coming up to speed with multicloud being one of the key areas. We've heard that a lot this week, right? And what I loved about Chuck's keynote when he talked about, you know, a multicloud by default and how we're working to change that to be multicloud for design by design, right? And so what we mean by that is, and DevOps plays a very key role there, right? In the last few years developers have had this opportunity to pick different multi from different multi clouds, right? And develop the applications wherever they find the right tool sets. But that's creating havoc with IT operations because IT has worked in it in different ways, right? So what we're trying to do with DevOps is really bridge the gap between the developers and the IT ops and make it more frictionless. And project Alpine is one of the key ones to make that, you know, to bring that bridge together. Really bring that operational consistency across on-prem and the public clouds and colo facilities and Edge and everything that we've talked about. So project Alpine is really key to the success of DevOps that we're driving across. And then the other thing that I would like to call out in terms of announce and Chuck brought that up on Monday was our focus on developers. And we have a portal called developer.dell.com which we announced and launched in January of this year. Right? It's think of that as our one stop shop for all of our APIs. You heard from Caitlin, you heard from a lot of our leaders that we have been on this journey of having a API first approach to everything we're doing be it products, be it features, functionality. And so the developer portal is the place where we're putting all of our ISG APIs and not just having a one stop shop but standardizing on APIs, which is really key. >> We just spoke to Shannon Champion and Gemma from Salesforce. And we talked about how we entered last decade for visioning lungs. And now we're programming infrastructure. So really interested in your container strategy, your DevOps strategy. How did it start? How was it evolving? Where are you in the spectrum? You know, where are customers in that maturity? Let's dig in >> 2015, I believe was the year when DockerCon their CTO went on stage and they explained their customer that they shouldn't care about storage. They should design their applications running in containers in the 12 factor way, designed to fail, storage doesn't matter. And I remember scratching my head because I was hearing this one before. If there's one thing that I've learned both as a customer and later on as an employee of a storage company at the time, is that customers care about data and they care a lot about their data. Especially if it's not available. It's a bad day for the customer and possibly a very bad day for me as well. And so we actually, at the time, work with a startup called Cluster HQ to offer persistent volumes for Kubernetes. That startup eventually went down of business. But Google took over the some part of the intellectual property and came with an API called CSI. Which does not stand for your famous TV show. It's actually an acronym for container storage interface. And the CSI role in life is to be able to provide persistent volume from a storage array to Kubernetes. So we start working with Google, just like many other vendors in order to ensure that our stands outs are part of the CSI stand out. And we start to providing CSI interfaces for our storage arrays. And that's how all of these things started. We started to get more and more customers telling us I'm going all in with Kubernetes and I need you to support me in that journey. But what we've also learned is that Kubernetes similarly in a way to the open stock days is very fragmented. There are many distributions that are running on the top of Kubernetes. So seed side itself is not just the end of it. Many customer wants day to be working with VMware (indistinct) with zoo or with red OpenShift or with Rancher. So we need to do different adjustments for each one of these distributions in order to ensure that we are meeting the customer where they are today but also in the future as well. >> Yeah, and Kubernetes back in 2015 was, you know, pretty immature. We were focused on simplicity. You had Mesos doing, you know, more sophisticated things, you know, cluster HQ, obvious. And now you see Kubernetes moving into that realm tackling all those, a lot of those problems. So where does storage fit into that resilient resiliency equation? >> Yeah, so, you know, I think storages are key. What we're hearing a lot from customers is they have infrastructure in place already and they want to take advantage of cloud native and modernizing their applications whether they're the legacy applications or as they're building new applications. So how do really take advantage of the infrastructure that they have invested in? And they love, and they need. I mean, the reason why our customers love our products is because of the enterprise and the data management capabilities that we provide, right? Be it PowerMax for our gold standards on SRDF replication, for instance, they want to make sure that they leverage all of that as they are containerizing their applications. So the piece that Itzik talked about with the CSI plugins, that gives customers the opportunity to take advantage of the infrastructure that's already in place, take advantage of all the enterprise capabilities that it provides but yet take advantage of cloudifying, if I can say, the applications that they're doing, right? And then on top of that we also have what we call our CSM modules which is the container storage modules which is so, you know, going back again, we, CSI industry stack spec standards, you know, customers started to use it. And what we heard from our customers was, this is great but it has very minimum capabilities, right? Very basic ones. And we love your enterprise products. We want enterprise capabilities with it. So we've been working with CNCF very closely on, you know, working on contributions. But what we have realized is that they're, the community is still far from delivering some of these enterprise capabilities. So we came up with container storage modules which is an extension of CSI modules but to add those enterprise capabilities, you know, be it observability, be it replication, authorization, resiliency. These are the things that customers wanted to use enterprise storage when it comes to containers. And that's what we've been delivering on with our container storage modules. I do want to call out that all of our CSM modules just like CSI are all open source. That's what developers want. They don't want it closed source. And so we're listening to them and we're creating all of this in open source waiting, you know, and wanting them to contribute to the court. So it's not just us doing, you know and writing what we want but we also want the community to contribute. >> You're committing resources there, publishing them, it's all open source? >> Exactly. >> That's the contribution. >> And working with CNCF to see if they can be standardized across the board not just for Dell customers. >> Is that a project going, is that your ideal? It that becomes a project within CNCF or is it? >> That's our goal. Yes. We're definitely working and influencing. We'll see how it goes. >> More committers. Just keep throwing committers at it. >> Support these day is done via slack channel. So if we're changing the way that we run interacting with our customers that are now the developers themselves via slack channel. You don't need to call 100, 800 Dell to get a support case. >> So I'm interested in, you mentioned project Alpine, and it was very interesting to me to see that. You know, you guys talk about multicloud. I try to take it to another level. I call it super cloud and that's this abstraction layer. You know, some people laugh at that, but it has meaning. Multi-cloud is going to multivendor by default. And my premise is data ultimately is going to stay where it belongs in place. And then this mesh evolves, not my word, Jamoc Degani kind of invented. And there needs to be standards to be able to share data and govern that data. And it's wide open now. There are no standards there. And I think open sources has an opportunity as opposed to a defacto standard that would emerge. It seems to be real white space there. I think a company like Dell could provide that self-service infrastructure to those data points on the mesh and standards or software that governs that in a computational way. Is that something that's, you know, that super cloud idea is a reality from a technologist perspective? >> I think it is. So for example, Katie Gordon, which I believe you interviewed earlier this week, was demonstrating the Kubernetes data mobility aspect, which is another project. That's exactly power part of the its rational, the rationale of customers being able to move some of their Kubernetes workloads to the cloud and back and between different clouds. Why we doing it? Because customers wants to have the ability to move between different cloud providers using a common API that will be able to orchestrate all of those things with a self-service that may be offered via the apex console itself. So it's all around enabling developers and meeting them where they are today and also meeting them in tomorrow's world where they actually may have changed their mind to do those things. So, yes, we are working on all of those different aspects. >> Dell meeting the developers where they are. Guys thank you so much for joining David and me and unpacking that. We appreciate your insights and your time. >> Thank you so much for having us. >> Thank you. >> Thank you. Speaking of unpacking, Lisa. We're unpacking Dell tech world. >> They're packing up around us. Exactly. We better go. We want to thank you for watching The Cube's two and a half days of live coverage of Dell Technologies world. Dave it's been great to co-host with you, be back in person. >> Thank you Lisa. It was really a pleasure. >> Of course. My pleasure too. >> Let's do more of this. >> Let's do it! >> All right. >> We want to thank you again for watching. You can catch all of this on replay on thecube.net. We look forward to seeing you next time. (soft music)

hey welcome back to los angeles lisa martin here with the cube we are live at kubecon and cloudnativecon 21. it's been great to be here we've been broadcasting the last couple of days about 2 700 people joining us in person great buzz great energy i've got two guests here next joining me remotely please welcome it's reich the vp technologist at dell emc anivis iyer senior principal product manager at dell technologies gentlemen welcome to the program thanks for having us lisa thank you lisa and we're pleased that you're joining us today it's like let's go ahead and start with you let's talk we've seen a lot of of uptick and kubernetes it's been picking up a lot what are some of the things that you're seeing through your lens right that's a great question lisa so really we need to take a step back bobby into 2019 we just mentioned in-person conferences so back then we started to see a slow adoption of customers that are starting to play with kubernetes in their test environment maybe running some pocs but then the pandemic happened obviously and we started to see huge explosion in terms of adoption and accelerating the digital based projects for our customers so they're really starting to pick up kubernetes and use it heavily in their production and of course in addition to their test and dev environments as well and because of that adoption they started to think about other scenarios and other considerations that are relevant for their production environment which is based upon kubernetes things like disaster recovery availability all of those things that typically you don't worry about when you just run them in a small desk or a poc environment but are super critical for our customers and you know it's the largest storage company in the world we have the smallest company customers in the world but also the largest and the most demanding one it's a really huge adoption that needs to basically accelerate all of those aspects that belong to an enterprise environment that happens to run on kubernetes itself if ask do you see something similar yeah absolutely i agree with itzik and actually one of the brief stories actually i start out with is because a few years ago actually several years ago when i was taking a cab in new york remember the point-of-sale terminal was not working so you know you took my credit card just like use the magnetic spike so not having the technology access was like an inconvenience but it still could transact but now today's age when you look at digital transform trans digitally transformed companies starting with all these web companies like you know you've got like uber lyft and things like that but then you also have mainstream companies where the entire business is now taking over digital hence all these applications are the ones that are powering the entire business if you will and not having these applications available or these apps available uh will basically the business is gonna lose money and and that's and that's what is and the pandemic has only accelerated digital transformation right because everyone working from home and and also the customers are also remote so now you have the entire operation is just software is running the business pretty much every company is a technology company and then you have you know and then all these applications they are modernized so they are modernized in the way that they're not built to the traditional architectures they're now using you know microservices devops and agile these are three major aspects that kind of you know drove the new application modernized applications to build more complex applications and kubernetes has emerged as the sole platform that can you know kind of serve the underlying platform between all of these aspects and hence we see that you know kubernetes adoption has taken off a lot because pretty much every organization is running several projects within the enterprise including app modernization you know transformation of any kind of secondary kind of use cases iot you know the whole digital transformation story is kind of running on kubernetes and as sick was pointing out so now kubernetes are simmered as the key infrastructure as a service layer if you will or above the infrastructure service and it needs to consume storage and it needs to have you know all these traditional capabilities that were for uh for applications right i mean like uh disaster recovery uh having enterprise grade uh availability aspects like you know for this uh data protection things like that and that's sort of is and the enterprise capabilities are relatively i would say uh accelerating a lot earlier kubernetes was more on the non-enterprise aspects of the journey now we are seeing a lot more enterprise growth are you seeing your conversations within organizations elevate up the chain where kubernetes is concerned is this a c-level conversation or the understanding that from a competitive differentiation perspective from a modernization perspective it's the direction they need to go in yeah absolutely and for them you know vmware ran itself a couple of months ago about the reasons that are important for customers to run containers in production there were like ten tens of them but the number one reason is to accelerate software adoption and to basically write codes faster that's like the number one reason it's not about the technology itself you know technology is just an enabler and the enabler is to write the code as quickly as you could deploy it in test and dev quickly as you could run some qa cycles on it and release release release the code that's at the end of the day that's the main difference between the old way of the waterfall approach to the new way of agile approach which eventually got translated into the infrastructure layer itself it needs to accommodate those changes if you will well releasing code faster is going to enable organizations presumably in any industry to be able to develop and release products and services faster to the demanding consumer market i imagine that's absolutely correct we've all got spoiled by the smartphone industry we'll just expect a new version to be just deployed to your device almost every day now it's exactly the same it is we i think we carry that i think it's i think it's impossible not to carry that consumer expectation from our consumer life into our business life and we just expect that things are going to work that way because in our consumer lives they do i want to ask you guys about is that this question is directly for you talk to me about csi what is it besides a tv show i know you have a great answer for this and many spin-offs by the way right not just a single one csi right so let's take a step back into 2015. docker rebecca dockercon they sit on the stage and during the keynote and they explain that you should write your code in the 12 factor way resiliency should be built in into the containers themselves and you shouldn't care about storage persistency now we're in the storage industry for the best part of my life right now and storage persistence is important if a customer lose data that's a very bad day for the customer and possibly a very bad day for me as well so it's all about the data nothing else really matters the data itself is the goal and so there was no data persistency back then you go here and we actually work with the startup that did just storage consistency for containers basically meaning the ability to provision a volume from storage array into kubernetes and kubernetes will know about this that style tab went busted but the need still existed and so into that need google came and they come up with this api called container storage interface short for csi that does exactly that it allows kubernetes administrator of the kubernetes api to consume storage from the underlying storage array so provision volumes map mapping volumes taking a snapshot of the volume and mapping those from those very basic capabilities now those capabilities are very basic and we now have customers that are telling us i need far more than just the ability to provision a volume for my kubernetes environments i need this volume to be protected i need this volume to be replicated and it is volume to be protected into a backup device all of those things that csi doesn't know to do today no we didn't know to do in the near future so what we did is we said right we're not going to reinvent the wheel that's csi we're not just going to repeat csi all over again we're going to extend csi with open source tools that will enable our customers to do all of those things that are just mentioned before so csm is container storage modules which is what we announced today and it's very high level it provides you i provided the capabilities to do the following the first one is the observability module so if you're monitoring your open source environments you are very very likely to use open source tools like graphing and commit use so we have this plugin that allows you to monitor your storage array with gofundme and prometus and really uh becomes the liaison point between the storage admin the kubernetes admin they can connect both to the console and each really understand the the entity that is not aware of i call it the two-way mirror base second module is the resiliency module kubernetes is very infant in terms of understanding storage it doesn't understand storage failure conditions and so our resiliency module run as the k3s is like a minimum version of kubernetes if you will which keeps monitoring both the storage array and the host and in case of a storage arrow it knows to act upon it and do things like volume unmapping and map those volumes to other surviving servers in the product center etc the other module is the replication module so back into 2015 uh customers are basically telling us today i want to use kubernetes but i also want to replicate the data to either a passive site or an active site and in case of a failure if my primary site goes down i want to fail over this kubernetes volumes and data to a remote site so literally within a click of a button you can fail over your kubernetes environment from site a to site b using the underlying storage array capabilities replication etc etc and the other module that we've also announced is the volume group snapshots so instead of just taking a single volume which is what csr is all about you can actually take multiple volume that belong to multiple micro services that at the end of the day running within those containers in order to really back up a service and not just the micro service itself so all of these modules and future modules that will come in the future as well belong to csm and csm for us is just the beginning it's everything that our most most the demanding customers want us to provide today and they are not willing to wait for csi to catch up base got it so we you've done a great job of explaining what csi is what it isn't what csm is and all the great things that were announced today let's talk about the data protection the security angle we've seen so much change in the security the threat landscape in the last 18 months we've seen ransomware become a household word the proliferation of ddos attacks and of course there's this scattered workforce that is still scattered talk to me about why data protection for kubernetes and what are some of the unique needs that that presents uh sure uh thanks lisa so um so when you look at the kubernetes landscape it originally started out with mostly the front-end aspects multi like you know like web tier type applications but as the landscape has evolved now we are seeing actually in the kubernetes community also there has been newer concepts like stateful sets for example which allows you to have more persistent type uh or basically they you know the application that have retained state and data uh in the kubernetes cluster and we are seeing a huge proliferation and that is also increasing you know across the board on uh for example everything from experimentation or like any kind of user experience kind of data the understanding about sessions you know what users like what they don't like to all critical operational aspects to transactional elements too all of them being brought into the kubernetes we are seeing organizations in various stages of the journey and then add on to the additional uh capabilities on the storage side as she was mentioning about csi and csm and are basically the ways for the kubernetes layer to consume these storage services so when you're building these modern applications uh the state is now preserved as part of the kubernetes and actually recently we had a case with one of the customers we've had and uh so they did not have data protection as part of their kubernetes and uh and you know and we are seeing this in several organizations where you have an it ops kind of a team and there is a devops team there's a two-speed it concept so devops teams a lot of time they do not take into consideration a lot of these uh you know disaster recovery and uh you know the data protection aspects as part of the design and then one of the customers just what happened and they lost you know data because the you know their systems crashed and it was not through ransomware luckily but it was through uh you know a general logical you know failure of hardware things like that and so they could not recover that so they had to go back and they had to like rest all the whole thing so they started investing in saying oh we need a ways to protect the data so that i can recover so data is all about recovery it's about you know making sure you can record to a certain point in time and also recovering in the minimal amount of time and the challenges that kubernetes adds on top of traditional application that you know the entire application definition in kubernetes is split across multiple of these smaller metadata aspects like the application itself will have labels they will have uh you know they'll have secrets they'll have config maps they'll have custom resource definitions they have all this additional metadata that make up the entire application not just the data so you need to have all of that captured in context in a cloud native fashion if you if you're trying to protect that kubernetes environment and that's kind of a little bit of a unique challenge and then from a security aspect that you alluded to from kubernetes yes there are been you know multiple security challenges that we see although we don't directly work on the front end on the uh on the prevention side but on the cure side data protection is an important aspect right i mean if you look at the open source community there is so much open source today and how do you know that the open source and the api that you're consuming is is coming from a valid source you need so there is all kinds of like different security solutions that kubernetes community offers to validate making sure the source code is good the apis are authenticated and you know authorized things like that so there is a lot of these but even despite that you know there is always ability for some attacks to sneak in and that's where data protection is providing that cure so in case something does happen and you have a ransomware attack i have a cyber security vault or i have data stored in a secure fashion in a panic room if you will that i can so my business like i was alluding to my earlier example the business depends on that data and that operational transactional customer data and you need to recover that and you need to store it in a secure place and that's sort of the whole aspect of that it's got to be recoverable that's the whole point guys thank you so much for joining me talking to me about what you're seeing from a kubernetes adoption acceleration perspective thank you for helping me learn a new definition of csi not a show or a spin-off and talk to us about what csm is and the things that you are the modules that you're announcing today we appreciate your candor and your time thank you lisa thanks for having us my pleasure for my guests i'm lisa martin coming to you live from los angeles at kubecon cloudbanditcon21 be right back dave nicholson will rejoin me with our next guest stay tuned you

>> Announcer: Live from Las Vegas, it's theCUBE. Covering Dell EMC World 2017. Brought to you by Dell EMC. >> Welcome back to Dell EMC World 2017. We're live here in the Venetian in Las Vegas. Day one of the three day show. Had Michael Dell out on the keynote stage earlier today. Also had David Blaine, world famous magician. Pretty interesting performance to say the least. >> Yeah I went down to get an ice pick. (man laughing) During our break. >> We'll get into that later but it was interesting. Keith Townsend, John Walls also joined by Itzik Reich who is the CTO of XtremeIO at Dell EMC. Itzik, thanks for being with us. It's good to see you sir. >> Thank you very much. >> All the way from Tel Aviv and great to have you. Alright, so your sweet spot of the company is giving birth to a new baby today. >> There you go. >> XtremeIO X2, tell us about that. What spawned that, and then what that responses be, what you developed. >> Right, I think in order to understand Xtreme, you need to start with the beginning, the X1. So, November 2015 I was having my class reunion, meeting my ex-girlfriend, and we've launched X1. And X1 became, within two quarters, the largest sole Dell flash array in the world. From nowhere to the largest sole flash array, at least in terms of units sold to the market. Right, both Garthner and I. And it was huge. A huge building and a success for us. A success because nobody would become the number one leader. And we built them because we didn't have the life cycle to normally mature a product. Right, so you mentioned being a father. I'm a father to two daughters, lovely daughters. One of them is six years old, one of them is five. And the young one is starting to show some signs of being a really clever person. And I'm afraid that somebody will tell me, oh she can skip the first class. Because skipping class serves some association with it. Social aspects of it. So we've been really busy trying to understand XtremeIO X1. Making super stable. Today we're already about 5/9 in the market. But it also would stand to refresh the product and come with something new. So our life cycle wasn't a traditional year or year and a half of refreshing the product. It took us longer for us to X2 and this is what we announced today. So what's new with X2. The first thing is the ability to come with really Dell's XO Drive and Dell's configuration. In X1 each DAE, you could put up to 25 drives inside of the DAE. And X2 can put out up to 72 drives per DAE right. And you can scale just like before. Up to 8X bricks. It's a huge capacity which you need for the vast majority of the use cases out there they don't know. Just VDR or just a single database is right. Today XtremeIO can fill pretty much every transaction while closing including virtualization wall close. You just need a lot of capacity for thousands of VM's. So that's one of the things. The other thing we improved performance of the X2 array. And the magic story around there was that because of the thousands and thousands of customers that we're involved with really got the good insight of the workload that they are running. And what we found out is something very interesting. The majority of those customers are running workload that they're very small block size. So you storage every item that arrives in the system as a different blocks characteristic and we found that the majority of them are using very, very small block size. And we want them to improve the performance of those block sizes. The IOPS and the latency. And we also wanted to make sure that it's actually more economical cheaper than the very expensive drives that the new NVMe drives that are out there. So different design goals. Making it faster and also making it cheaper in different dimensions. So we come with a new feature called Drive Boost. In a nut shell, in a nut shell Drive Boost will give you 80% better latency for pretty much every walkthrough that is out there. >> So... With that small block sizes versus big block sizes. Why is that important? We're at a conference and we're talking a lot about digital transformation. CEO, we teased John earlier. You know he's a sports guy, he doesn't do LAG goals. >> (laughing) Sorry. >> That's alright. >> Help us understand the value of that data type. >> Sure, so you know we like to think about digital transformation but at the end of the day. You're the customer, you have a database. You'll use it on query or queries against the database. If it's a very large database, there are thousands maybe even millions of queries everyday. Those queries take time for the end user to get a response for. So let's assume that you want a monthly report. And this report normally takes nine hours to generate. If I can shrink the report crunching time to two hours instead of nine, that means that I have provided better value for the business success. Right. One of the stories is that we have a financial customer in the Middle East. They need to generate the report every month between midnight because this is where they locate their reports. Up until eight o'clock in the morning. Why eight o'clock because this is when the employees start to come to work. And every hour that they exceed after the eight hour generation they get fined by the government. So if I'm saving this customer four hours then they are not getting fined by the government for generating the report. That's a true value for the customer return. Cause those things are important. People tend to think about just performance numbers in terms of IOPS but the real magic number is latency. How quick can you make the query? Whether it's a database application or a VDI VM or just a generic web server running on a Voltron machine. Those are the important things today. >> So transactional apps. Big deal. Are these transactional apps, we learned a lot about virtualization and cloud computing to date. Are these transactional apps running in a virtualized environment or are we still relying on big heavy metal workloads going to treat IO2. >> Yeah, it's a good question. At least from my experience some would argue that anywhere between 70 to 80% of the customer that allowed it went full virtualized. So their running their entire application running either under V6 or a Microsoft type of V. So they are fully virtualized. Some of the customers are still running their workload on a traditional physical servers right. Even in the S6 at the end of the day it runs on a physical server to all day the kill in itself. But yeah, the majority of them are already there in terms of virtualization. >> So what are customers really excited about when it comes to features sets for an XIO2 versus XtremeIO version wise. >> Right, amazing question. So performance, we've already discussed performance. 80% better latency, that's not something that you get because of the usage of better CPU's. Intel moves slow, it's basically dead right. They don't give you 200% performance between generation so we wanted to do something else and solve the same problem. The other thing is quality of service. We are not cheaping NGA but it's coming soon. The ability to give a specific VM, a specific IO copying and the latency copying. And also could give you the ability to burst to more IOP's techniques needed for a couple of minutes. So quality of service I the noisy neighbor right. Somebody generate too much noise you want him to be quiet. That's what quality of service is. The other things that we've announced native replication. We found out finally of our own replication that can replicate between one XtremeO2 and another. But it's not a traditional replication. The unique thing about XtremeIO was always the cusp. The content of dressable architecture. People typically think about it as a D Duplication feature but in fact we don't have a feature called D Duplication. We analyze the data as it goes through the system itself. And we give a unique shot signature to each one of those blocks. And if the shot signature already exists in the system we dupe the block. But it's not the feature per se. That why the D Duplication's so fast on XtremeIO. So up until now the customers architecture was only applicable to writing the data into the array itself. Now it's also applicable for replicating the data. So for example if you have a data reduction of five to one which is very common in virtualize use case. Many VM, many the same template and so on. You know need to replicate four times less the data at the source to the destination target. Right. So that's a very, very big thing because you need to replicate more and more data. But the 24 hour window isn't changed. God didn't upgrade it where the server respects the time. Right. >> (laughing) Right. >> It's still 24 hours per day. So this is super important for us and we're very excited about it. And the other thing is that, again larger denser configuration of the array itself so the customer can have up until two-thirds cheaper. The drive, the cost drive of the XtremeIO in itself so it's cheaper for them to put their walkthrough on ExtemeIO. Whether to really pick up the just the database that needs all the performance in the world. So we can really become a true enterprise array with those features. >> It seems like it's got to be for you a constant chase though right. You're looking for higher performance, you're looking for lower costs. You've said you just gained 80% increase in your performance capabilities. >> Yup. >> And now people are going to be looking at you over the next Xtreme and so what next? You know, where are the gains to be had in the next generation of technology and just in terms of philosophically approaching that so what do you do. >> Yeah, yeah again another good question. I actually gave a briefing about it just earlier. So, the first thing we need to do is an industry not just the daily insists to lower the costs of the drive itself to be even cheaper than and economical drive. That's not Dell today right, the hybrid mechanical drive. You can get a more economical drive if you apply data reduction on it right. So if you're five times cheaper because of the data that's gets integrated into the array and get a different compress and different provisioning. Then you can be on par with the mechanical drives. So first we want to be on par if not cheaper. We want everybody to move to S's. And we were the first twirl for charade the portfolio of Dell EMC. That's the first thing. The second thing is to really get a better insight into your wall application, wall close. Today people analyze things like IOP's and latency but what does your application really think? Where are the cues in the application stock itself right. How can you find them out in the storage sub-system itself right. So we are on a journey to over there with our importing mechanisms. So a year and a half ago, we started a new project to completely change the reporting mechanism of the WebUI. The interface of XtremeIO right. And today you can really get to drill down into pretty much every aspect. Up until now you had to purchase a third party software that will analyze your walkthrough for you. So things like Instagram, IO's, block size, read and write like I can see pair of blocks. So you can really understand your workload. We also give you something like abnormalities. We can tell you every week this application is being fine but on that Friday for some reason the response time wasn't that good. You should go in and check it out. Maybe it's in the application there is a bottleneck. Maybe it was a bottleneck in the storage load. So you can actually find it out. But I would argue that the long term goal. That's a vision right? That I'm not announcing anything yet. Is really the ability to marriage or combine between the softer defined wall right. The input converge mechanism, to the traditional arrays right. Although SSD's not that traditional. Maybe you can have a denser configuration with very small to DAE but the performance aspect of it will not be drive from the DEA where it actually store the data but from Voltron machines. That you can spin up and down in a cloud like fishing. That will bring you all the performance that you need. That's a thing to me the only gray. The really merging between the walls. Cause there isn't one perfect answer right. The softer refined guys will tell you everything should go to softer defined storage. We will tell you everything should go to flash arrays. But really the truth is like always right in between. And this is really one of the direction that we are approaching. >> I tell you what, for now I want you to enjoy X2 for now. How about that. >> That sound good. >> It's a good day for you. And don't let that five year old skip either. I think that's a good idea too. >> Very good. Very good. Thank you very much. >> And so thanks for joining us. >> Thank you. Thanks. >> Back with more here on theCUBE. We're live in Las Vegas at Dell EMC World 2017. (exciting techno music)

>> From The Cube studios in Palo Alto, in Boston, bringing you data driven insights from the cube and ETR. This is breaking analysis with Dave Vellante. >> Last year, we noted in a breaking analysis that the cloud ecosystem is innovating beyond the idea or notion of multi-cloud. We've said for years that multi-cloud is really not a strategy but rather a symptom of multi-vendor. And we coined this term supercloud to describe an abstraction layer that lives above the hyperscale infrastructure that hides the underlying complexities, the APIs, and the primitives of each of the respective clouds. It interconnects whether it's On-Prem, AWS, Azure, Google, stretching out to the edge and creates a value layer on top of that. So our vision is that supercloud is more than running an individual service in cloud native mode within an individual individual cloud rather it's this new layer that builds on top of the hyperscalers. And does things irrespective of location adds value and we'll get into that in more detail. Now it turns out that we weren't the only ones thinking about this, not surprisingly, the majority of the technology ecosystem has been working towards this vision in various forms, including some examples that actually don't try to hide the underlying primitives. And we'll talk about that, but give a consistent experience across the DevSecOps tool chain. Hello, and welcome to this week's Wikibon, Cube insights powered by ETR. In this breaking analysis, we're going to share some recent examples and direct quotes about supercloud from the many Cube guests that we've had on over the last several weeks and months. And we've been trying to test this concept of supercloud. Is it technically feasible? Is it business rational? Is there business case for it? And we'll also share some recent ETR data to put this into context with some of the players that we think are going after this opportunity and where they are in their supercloud build out. And as you can see I'm not in the studio, everybody's got COVID so the studios shut down temporarily but breaking analysis continues. So here we go. Now, first thing is we uncovered an article from earlier this year by Lori MacVittie, is entitled, Supercloud: The 22 Answer to Multi-Cloud Challenges. What a great title. Of course we love it. Now, what really interested us here is not just the title, but the notion that it really doesn't matter what it's called, who cares? Supercloud, distributed cloud, someone even called it Metacloud recently, and we'll get into that. But Lori is a technologist. She's a developer by background. She works at F-Five and she's partial to the supercloud definition that was put forth by Cornell. You can see it here. That's a cloud architecture that enables application migration as a service across different availability zones or cloud providers, et cetera. And that the supercloud provides interfaces to allocate, migrate and terminate resources... And can span all major public cloud providers as well as private clouds. Now, of course, we would take that as well to the edge. So sure. That sounds about right and provides further confirmation that something new is really happening out there. And that was our initial premise when we put this fourth last year. Now we want to dig deeper and hear from the many Cube guests that we've interviewed recently probing about this topic. We're going to start with Chuck Whitten. He's Dell's new Co-COO and most likely part of the Dell succession plan, many years down the road hopefully. He coined the phrase multi-cloud by default versus multi-cloud by design. And he provides a really good business perspective. He's not a deep technologist. We're going to hear from Chuck a couple of times today including one where John Furrier asks him about leveraging hyperscale CapEx. That's an important concept that's fundamental to supercloud. Now, Ashesh Badani heads products at Red Hat and he talks about what he calls Metacloud. Again, it doesn't matter to us what you call it but it's the ecosystem gathering and innovating and we're going to get his perspective. Now we have a couple of clips from Danny Allan. He is the CTO of Veeam. He's a deep technologist and super into the weeds, which we love. And he talks about how Veeam abstracts the cloud layer. Again, a concept that's fundamental to supercloud and he describes what a supercloud is to him. And we also bring with Danny the edge discussion to the conversation. Now the bottom line from Danny is we want to know is supercloud technically feasible? And is it a thing? And then we have Jeff Clarke. Jeff Clark is the Co-COO and Vice Chairman of Dell super experienced individual. He lays out his vision of supercloud and what John Furrier calls a business operating system. You're going to hear from John a couple times. And he, Jeff Clark has a dropped the mic moment, where he says, if we can do this X, we'll describe what X is, it's game over. Okay. So of course we wanted to then go to HPE, one of Dell's biggest competitors and Patrick Osborne is the vice president of the storage business unit at Hewlett Packet Enterprise. And so given Jeff Clarke's game over strategy, we want to understand how HPE sees supercloud. And the bottom line, according to Patrick Osborne is that it's real. So you'll hear from him. And now Raghu Raghuram is the CEO of VMware. He threw a curve ball at this supercloud concept. And he flat out says, no, we don't want to hide the underlying primitives. We want to give developers access to those. We want to create a consistent developer experience in that DevsSecOps tool chain and Kubernetes runtime environments, and connect all the elements in the application development stack. So that's a really interesting perspective that Raghu brings. And then we end on Itzik Reich. Itzik is a technologist and a technical team leader who's worked as a go between customers and product developers for a number of years. And we asked Itzik, is supercloud technically feasible and will it be a reality? So let's hear from these experts and you can decide for yourselves how real supercloud is today and where it is, run the sizzle >> Operative phrase is multi-cloud by default that's kind of the buzz from your keynote. What do you mean by that? >> Well, look, customers have woken up with multiple clouds, multiple public clouds, On-Premise clouds increasingly as the edge becomes much more a reality for customers clouds at the edge. And so that's what we mean by multi-cloud by default. It's not yet been designed strategically. I think our argument yesterday was, it can be and it should be. It is a very logical place for architecture to land because ultimately customers want the innovation across all of the hyperscale public clouds. They will see workloads and use cases where they want to maintain an On-Premise cloud, On-Premise clouds are not going away, I mentioned edge clouds, so it should be strategic. It's just not today. It doesn't work particularly well today. So when we say multi-cloud by default we mean that's the state of the world today. Our goal is to bring multi-cloud by design as you heard. >> Really great question, actually, since you and I talked, Dave, I've been spending some time noodling just over that. And you're right. There's probably some terminology, something that will get developed either by us or in collaboration with the industry. Where we sort of almost have the next almost like a Metacloud that we're working our way towards. >> So we manage both the snapshots and we convert it into the Veeam portable data format. And here's where the supercloud comes into play. Because if I can convert it into the Veeam portable data format, I can move that OS anywhere. I can move it from physical to virtual, to cloud, to another cloud, back to virtual, I can put it back on physical if I want to. It actually abstracts the cloud layer. There are things that we do when we go between cloud some use BIOS, some use UEFI, but we have the data in backup format, not snapshot format, that's theirs, but we have it in backup format that we can move around and abstract workloads across all of the infrastructure. >> And your catalog is control in control of that. Is that right? Am I thinking about that the right way? >> Yeah it is, 100%. And you know what's interesting about our catalog, Dave, the catalog is inside the backup. Yes. So here's, what's interesting about the edge, two things, on the edge you don't want to have any state, if you can help it. And so containers help with that You can have stateless environments, some persistent data storage But we not not only provide the portability in operating systems, we also do this for containers. And that's true. If you go to the cloud and you're using say EKS with relational database services RDS for the persistent data later, we can pick that up and move it to GKE or move it to OpenShift On-Premises. And so that's why I call this the supercloud, we have all of this data. Actually, I think you termed the term supercloud. >> Yeah. But thank you for... I mean, I'm looking for a confirmation from a technologist that it's technically feasible. >> It is technically feasible and you can do it today. >> You said also technology and business models are tied together and enabler. If you believe that then you have to believe that it's a business operating system that they want. They want to leverage whatever they can. And at the end of the day, they have to differentiate what they do. >> Well, that's exactly right. If I take that in what Dave was saying and I summarize it the following way, if we can take these cloud assets and capabilities, combine them in an orchestrated way to deliver a distributed platform, game over. >> We have a number of platforms that are providing whether it's compute or networking or storage, running those workloads that they plum up into the cloud they have an operational experience in the cloud and they now they have data services that are running in the cloud for us in GreenLake. So it's a reality, we have a number of platforms that support that. We're going to have a a set of big announcements coming up at HPE Discover. So we led with Electra and we have a block service. We have VM backup as a service and DR on top of that. So that's something that we're providing today. GreenLake has over, I think it's actually over 60 services right now that we're providing in the GreenLake platform itself. Everything from security, single sign on, customer IDs, everything. So it's real. We have the proofpoint for it. >> Yeah. So I want to clarify something that you said because this tends to be very commonly confused by customers. I use the word abstraction. And usually when people think of abstraction, they think it hides capabilities of the cloud providers. That's not what we are trying to do. In fact, that's the last thing we are trying to do. What we are trying to do is to provide a consistent developer experience regardless of where you want to build your application. So that you can use the cloud provider services if that's what you want to use. But the DevSecOp tool chain, the runtime environment which turns out to be Kubernetes and how you control the Kubernetes environment, how do you manage and secure and connect all of these things. Those are the places where we are adding the value. And so really the VMware value proposition is you can build on the cloud of your choice but providing these consistent elements, number one, you can make better use of us, your scarce developer or operator resources and expertise. And number two, you can move faster. And number three, you can just spend less as a result of this. So that's really what we are trying to do. We are not... So I just wanted to clarify the word abstraction. In terms of where are we? We are still, I would say, in the early stages. So if you look at what customers are trying to do, they're trying to build these greenfield applications. And there is an entire ecosystem emerging around Kubernetes. There is still, Kubernetes is not a developer platform. The developer experience on top of Kubernetes is highly inconsistent. And so those are some of the areas where we are introducing new innovations with our Tanzu Application Platform. And then if you take enterprise applications, what does it take to have enterprise applications running all the time be entirely secure, et cetera. >> Well, look, the multi-cloud by default today are isolated clouds. They don't work together. Your data is siloed. It's locked up and it is expensive to move and make sense of it. So I think the word you and I were batting around before, this is an interconnected tissue. That's what the world needs. They need the clouds to work together as a single platform. That's the problem that we're trying to solve. And you saw it in some of our announcements here that we're starting to make steps on that journey to make multi-cloud work together much simpler. >> It's interesting, you mentioned the hyperscalers and all that CapEx investments. Why wouldn't you want to take advantage of a cloud and build on the CapEx and then ultimately have the solutions machine learning as one area. You see some specialization with the clouds. But you start to see the rise of superclouds, Dave calls them, and that's where you can innovate on a cloud then go to the multiple clouds. Snowflakes is one, we see a lot of examples of supercloud... >> Project Alpine was another one. I mean, it's early, but it's its clearly where you're going. The technology is just starting to come around. I mean it's real. >> Yeah. I mean, why wouldn't you want to take advantage of all of the cloud innovation out there? >> Is that something that's, that supercloud idea is a reality from a technologist perspective. >> I think it is. So for example Katie Gordon, which I believe you've interviewed earlier this week, was demonstrating the Kubernetes data mobility aspect which is another project. That's exactly part of the it's rationale, the rationale of customers being able to move some of their Kubernetes workloads to the cloud and back and between different clouds. Why are we doing? Because customers wants to have the ability to move between different cloud providers, using a common API that will be able to orchestrate all of those things with a self-service that may be offered via the APEX console itself. So it's all around enabling developers and meeting them where they are today and also meeting them into tomorrow's world where they actually may have changed their mind to do those things. So yes we are walking on all of those different aspects. >> Okay. Let's take a quick look at some of the ETR data. This is an X-Y graph. You've seen it a number of times on breaking analysis, it plots the net score or spending momentum on the Y-axis and overlap or pervasiveness in the ETR dataset on the X-axis, used to be called market share. I think that term was off putting to some people, but anyway it's an indicator of presence in the dataset. Now that red dotted line that's rarefied air where anything above that line is considered highly elevated. Now you can see we've plotted Azure and AWS in the upper right. GCP is in there and Kubernetes. We've done that as reference points. They're not necessarily building supercloud platforms. We'll see if they ever want to do so. And Kubernetes of course not a company, but we put 'em in there for context. And we've cherry picked a few players that we believe are building out or are important for supercloud build out. Let's start with Snowflake. We've talked a lot about this company. You can see they're highly elevated on the vertical axis. We see the data cloud as a supercloud in the making. You've got pure storage in there. They made the public, the early part of its supercloud journey at Accelerate 2019 when it unveiled a hybrid block storage service inside of AWS, it connects its On-Prem to AWS and creates that singular experience for pure customers. We see Hashi, HashiCorp as an enabling infrastructure, as code. So they're enabling infrastructure as code across different clouds and different locations. You see Nutanix. They're embarking on their multi-cloud strategy but it's doing so in a way that we think is supercloud, like now. Now Veeam, we were just at VeeamON. And this company has tied Dell for the number one revenue player in data protection. That's according to IDC. And we don't think it won't be long before it holds that position alone at the top as it's growing faster than in Dell in the space. We'll see, Dell is kind of waking up a little bit and putting more resource on that. But Veeam, they're a pure play vendor in data protection. And you heard their CTO, Danny Allan's view on Supercloud, they're doing it today. And we heard extensive comments as well from Dell that's clearly where they're headed, project Alpine was an early example from Dell technologies world of Supercloud in our view. And HPE with GreenLake. Finally beginning to talk about that cross cloud experience. I think it in initially HPE has been more focused on the private cloud, we'll continue to probe. We'll be at HPE discover later on the spring, actually end of June. And we'll continue to probe to see what HPE is doing specifically with GreenLake. Now, finally, Cisco, we put them on the chart. We don't have direct quotes from recent shows and events but this data really shows you the size of Cisco's footprint within the ETR data set that's on the X-axis. Now the cut of this ETR data includes all sectors across the ETR taxonomy which is not something that we commonly show but you can see the magnitude of Cisco's presence. It's impressive. Now, they had better, Cisco that is, had better be building out a supercloud in our view or they're going to be left behind. And I'm quite certain that they're actually going to do so. So we have a lot of evidence that we're putting forth here and seeing in the marketplace what we said last year, the ecosystem is take taking shape, supercloud is forming and becoming a thing. And really in our view, is the future of cloud. But there are always risks to these predictive scenarios and we want to acknowledge those. So first, look, we could end up with a bunch of bespoke superclouds. Now one supercloud is better than three separate cloud native services that do fundamentally the same thing from the same vendor. One for AWS, one for GCP and one for Azure. So maybe that's not all that bad. But to point number two, we hope there evolves a set of open standards for self-service infrastructure, federated governance, and data sharing that will evolve as a horizontal layer versus a set of proprietary vendor specific tools. Now, maybe a company like Veeam will provide that as a data management layer or some of Veeam's competitors or maybe it'll emerge again as open source. As well, and this next point, we see the potential for edge disruptions, changing the economics of the data center. Edge in fact could evolve on its own, independent of the cloud. In fact, David Floria sees the edge somewhat differently from Danny Allan. Floria says he sees a requirement for distributed stateful environments that are ephemeral where recovery is built in. And I said, David, stateful? Ephemeral? Stateful ephemeral? Isn't that an oxymoron? And he responded that, look, if it's not ephemeral the costs are going to be prohibitive. He said the biggest mistake the companies could make is thinking that the edge is simply an extension of their current cloud strategies. We're seeing that a lot. Dell largely talks about the edge as retail. Now, and Telco is a little bit different, but back to Floria's comments, he feels companies have to completely reimagine an integrated file and recovery system which is much more data efficient. And he believes that the technology will evolve with massive volumes and eventually seep into enterprise cloud and distributed data centers with better economics. In other words, as David Michelle recently wrote, we're about 15 years into the most recent cloud cycle and history shows that every 15 years or so, something new comes along that is a blind spot and highly disruptive to existing leaders. So number four here is really important. Remember, in 2007 before AWS introduced the modern cloud, IBM outpost, sorry, IBM outspent Amazon and Google and RND and CapEx and was really comparable to Microsoft. But instead of inventing cloud, IBM spent hundreds of billions of dollars on stock buybacks and dividends. And so our view is that innovation rewards leaders. And while it's not without risks, it's what powers the technology industry it always has and likely always will. So we'll be watching that very closely, how companies choose to spend their free cash flow. Okay. That's it for now. Thanks for watching this episode of The Cube Insights, powered by ETR. Thanks to Stephanie Chan who does some of the background research? Alex Morrison is on production and is going to compile all this stuff. Thank you, Alex. We're all remote this week. Kristen Nicole and Cheryl Knight do Cube distribution and social distribution and get the word out, so thank you. Robert Hof is our editor in chief. Don't forget the checkout etr.ai for all the survey action. Remember I publish each week on wikibon.com and siliconangle.com and you can check out all the breaking analysis podcasts. All you can do is search breaking analysis podcast so you can pop in the headphones and listen while you're on a walk. You can email me at david.vellante@siliconangle.com. If you want to get in touch or DM me at DVellante, you can always hit me up into a comment on our LinkedIn posts. This is Dave Vellante. Thank you for watching this episode of break analysis, stay safe, be well and we'll see you next time. (upbeat music)