(upbeat music) >> Hello, everybody. John Walls here, as we continue our coverage of AWS re:Invent here on theCUBE. And today we're going to go talk about the edge. What's out there on the edge, and how do we make sense of it? How do we use that data, and put it to work, and how do we keep it secure? Big questions, a lot of questions, and at the end of the day, what's the value prop for you, the customer, to make it all work? With me to talk about that is the Executive Vice President and GM of HPE GreenLake, Keith White. Keith, thanks for joining us here on theCUBE. >> John, thanks so much for having me. I really appreciate the opportunity, and excited to have a conversation today. >> Yeah, good. Well, let's just jump right in. First off, about the edge. There was a time, not so long ago, that it was kind of the Wild, Wild West out there, right? And we were trying to corral this fantastic reservoir of data that was streaming in from every which point, to the point now where we've realized how to refine that, how to develop that, how to reduce that complexity, to make that actionable. Talk about that journey a little bit, about where we were with edge technology maybe five, six years ago, and how we've migrated to the point we are now, where GreenLake is doing the great work that it is. >> You know, it's really a great question, John, cause I think there's a lot of different definitions of the edge, and what does "the edge" actually mean. And you're right, you know, there's been a pretty big transformation over the last few years, especially as we think about things like IoT, and just being able to engage with edge scenarios. But today what you're seeing is a lot of digital transformations happening with companies around three big megatrends. Cloud, meaning hybrid cloud, multi-cloud, data, and how you analyze that data to make decisions. And of course the edge, like we're talking through. And you know, frankly, with the edge, this is where we see the connectivity and security requirements really connect, because that edge information is so important, so critical to stay secure, but also it's creating that tremendous amount of data, as you mentioned. And so folks want to pull that into their cloud environment, and then make decisions and analyze that data, and plug it into the systems that they have overall. And you know, you're seeing companies like Auckland Transport, right? They basically do an AI-enhanced video feed to optimize their transport routes. And as you think about supply chain and the big challenges that we're seeing today, or you think about public transportation, and, you know, really providing information with respect to customers, but how do you take and get all that information pulled together, to then make decisions from these various edge points throughout? Or a company like ABB, who's been building the factory of the future, and doing, basically, you know, robotics-as-a-service, if you will, in order to really get that precision required at the edge in order to manufacture what they need to. So, massive uses around the edge, massive data getting created, and HPE GreenLake's a great spot for folks to help, you know, really take and leverage that data, to make those those decisions that are required. >> You know, one example in terms of case studies, or in terms of your client base that you talk about, you know, the automotive sector. >> Yeah. >> And I think about what's going on in terms of, with that technology, and I can't even imagine the kind of mechanics that are happening, right? In real time, at 60, 70 miles an hour, through all kinds of environmental conditions. So maybe just touch base, too, about what you're doing that's in terms of automotive, and what's going to be- >> No, it's great, John, yeah. >> (indistinct) then? >> Yeah, no, it's an awesome question, because, you know, we're working closely with a lot of the car manufacturers, as well as their sort of subsidiaries, if you will. So you look at autonomous driving, which is a great example. All that data has to come in and get analyzed. And if you look at a company like Volvo, they use a third party called Zenseact, who basically uses our high-performance compute to deliver it as a service through HPE GreenLake. They get all this massive parallel computing, modeling and simulations happening, with all this data coming in. And so what we've done with GreenLake is we give them that ability to easily scale up, to grow capacity, to get access to that hundreds of petabytes of data that you just mentioned. And then, you know, really basically take and make analytics and AI models and machine learning capabilities out of that, in order to really direct and fuel their mission to develop that next-generation software to support that autonomous driving capability. And so you're seeing that with a ton of different car manufacturers, as well as a lot of different other scenarios as well. So you're spot on. Automotive is a key place for that. >> You know, and too, the similarities here, the common thread, I think, threads, actually, plural, are very common. We think about access, right? We think about security, we think about control, we think about data, we think about analytics, so I mean, all these things are factoring in, in this extraordinarily dynamic environment. So is there a batting order, or a pecking order, in terms of addressing those areas of concern, or what kind of, I guess, learning curve have we had on that front? >> Well, I think you're, I think the key is, as I mentioned earlier, so you have this connectivity piece, and you've got to be able to connect and be available as required. That might be through SD-WAN, that might be Wi-Fi, that might be through a network access point, et cetera. But the key is that security piece of it as well. Customers need to know that that data and that edge device is very, very secure. And then you've got to have that connectivity back into your environment. And so what we've learned with HPE GreenLake, which, really what that does, is that brings that cloud experience, that public cloud experience, to customers in their data center, on-premise, in their colo, or at the edge, like we're talking about now, because there's a lot of need to keep that data secure, private, to make sure that it's not out in the public cloud and accessible, or those types of scenarios. So as I think about that piece of it, then it turns into, okay, how do we take all that data and do the analytics and the AI modeling that we talked about before? So it's a really interesting flow that has to happen. But what's happening is, people are really transforming their business, transforming their business models, as we just talked about. Factory of the future, you know, transportation needs. We're seeing it in different environments as well. Automotive, as you mentioned. But it's exciting, it's an exciting time, with all of this opportunity to really change not only how a business can run, but how we as consumers interact and engage with that. >> And then ultimately for the company, the value prop's got to be there. And you've already cited a number of areas. Is there one key metric that you look at, or one key deliverable that you look at here, in terms of what the ultimate value proposition is for a customer? >> You bet. I think the biggest thing is, you know, our customers and their satisfaction. And so, to date, you know, we have well over 60,000 customers on the platform. We have a retention rate of 96%, so a very, very small number that haven't stayed on the platform itself. And that means that they're satisfied. And what we're seeing also is a continued growth in usage for new environments, new workloads, new solutions that a customer is trying to drive as well. And so those are some of the key metrics we look at, with respect to our customer satisfaction, with their retention rate, with their usage capabilities, and then how we're growing that piece. And the interesting thing, John, is what we've learned is that HPE, as a company, traditionally was very hardware focused, it was a hardware vendor, transacting, responding to RFPs for compute, storage, and networking. With GreenLake now moving into the cloud services realm, we're now having conversations with customers as their partner. How do we solve this problem? How do we transform our business? How do we accelerate our growth? And that's been very exciting for us as a company, to really make that significant transformation and shift to being part of our customer's environments in a partnership type way. >> Yeah. And now you're talking about ecosystem, right? And what you're developing, not only in your partners, but also maybe what lessons you're learning in one respect you can apply to others. What's happening in that respect, in terms of the kind of universe that you're developing, and how applicable, maybe, one experience is to another client's needs? >> Yeah, no, it's a great question, because in essence, what happens is, we're sort of the tip of the spear, and we're partnering with customers to really go in deep, and understand how to utilize that. We can take that learning, and then push that out to our ecosystem, so that they can scale and they can work with more customers with respect to that piece of it. The second is, is that we're really driving into these more solution-oriented partners, right? The ISVs, the system integrators, the managed service providers, the colos, and even the hyperscalers, as we've talked about, and why we're here with our friends at AWS, is, customers are requiring a hybrid environment. They want to leverage tools up in the public cloud, but they also want the on-prem capabilities, and they need those to work together. And so this ecosystem becomes very dynamic with respect to, hey, what are we learning, and how do we solve our customer's problems together? I always talk about the ecosystem being 1 + 1 = 3 for our customers. It has to be that way, and frankly, our customers are expecting that. And that's why we're excited to be here today with our, as I said, our friends at AWS. >> And how does open play in all this too, right? Because, I mean, that provides, I assume, the kind of flexibility that people are looking for, you know, they, you know, having that open environment and making an opportunity available to them is a pretty big attractive element. >> It's huge, right? Yeah, as you know, people don't want to get locked in to a single technology. They don't want to get locked in to a single cloud. They don't want to have to, they want to be able to utilize the best of the best. And so maybe there's some tools in the public cloud that can really help from an analytics standpoint, but we can store and we can process it locally in our data center, at the edge, or in a colo. And so that best of both worlds is there, but it has to be an open platform. I have to be able to choose my container, my virtual machine, my AI tools, my, you know, capabilities, my ISV application, so that I have that flexibility. And so it's been fantastic for us to move into this open platform environment, to be able to have customers leverage the best and what's going to work best for them, and then partnering with those folks closely to, again, deliver those solutions that are required. >> You know, this is, I mean, it appears, as I'm hearing you talk about this, in terms of the partnerships you're creating, the ecosystem that you're developing, how that's evolving, lessons that you've learned, the attention you've paid to security and data analytics. I get the feeling that you've got a lot of momentum, right? A lot of things are happening here. You've got big mo on your side right now. (Keith laughs) Would you characterize it that way? >> Yeah, you know, there's a ton of momentum. I think what we're finding is, customers are requiring that cloud experience on-prem. You know, they're getting it from AWS and some of the other hyperscalers, but they want that same capability on-prem. And so what we've seen is just a dramatic increase with respect to usage, customers. We're adding hundreds of customers every quarter. We're growing in the triple digits, three of the last four quarters. And so, yeah, we're seeing tremendous momentum, but as I said, what's been most important is that relationship with the customer. We've really flipped it to becoming that partner with them. And again, bringing that ecosystem to bear, so that we can have the best of all worlds. And it's been fantastic to see, and frankly, the momentum's been tremendous. And we're in a quiet period right now, but you'll see what our earnings are here in the next couple weeks, and we can talk more details on that, but in the past, as we talked about, we've grown, you know, triple digits three of the last four quarters, and, you know, well over $3 billion, well over $8 billion of total contract value that we've implemented to date. And, you know, the momentum is there, but, again, most importantly is, we're solving our customers' problems together, and we're helping them accelerate their business and their transformation. >> I know you mentioned earnings, the report's a few weeks away. I saw your smile, that big old, you know, grin, so I have a feeling the news is pretty good from the HPE GreenLake side. >> It is. We're excited about it. And you know, again, this really is just a testament to the transformation we've made as a company in order to move towards those cloud services. And you know, you'll hear us talk about it as the core of what we're doing as a company, holistically, again, because this is what customers are requiring, this is what our ecosystem is moving towards. And it's been really fun, it's been a great, great ride. >> Excellent. Keith, appreciate the time, and keep up the good work, and I'm going to look for that earnings report here in a few weeks. >> Awesome. Thanks so much, John. Take good care. Appreciate it. >> You bet, you too. Keith White joining us here, talking about HPE GreenLake, and defining what they're doing in terms of bringing the edge back into the primary systems for a lot of companies. So, good work there. We'll continue our coverage here in theCUBE. You're watching theCUBE coverage of AWS re:Invent. And I'm John Walls. (lively music)

>> Thank you for joining us today for this session entitled, Deploy any Workload as a Service, When General Purpose Technology isn't Enough. This session today will be on our HPE GreenLake platform. And my name is Mark Seamans, and I'm a member of our GreenLake cloud services team. And I'll be kind of leading you through the material today which will include both a slide presentation as well as an interactive demo to get some experience in terms of how the process goes for interacting with your initial experience with our GreenLake system. So, let's go ahead and get started. One of the things that we've noticed over the last decade and I'm sure that you have as well has been the tremendous focus on accelerating business while concurrently trying to increase agility and to reduce costs. And one of the ways a lot of businesses have gone about doing that has been leveraging a cloud based technology set. And in many cases, that's involved moving some of the workloads to the public cloud. And so with that much said, though, while organizations have been able to enjoy that cost control and the agility associated with the public cloud. What we've seen is that the easy to move workloads have been moved but there's a significant amount as much as 70% in many cases of workloads that organizations run which still remain on prem. And there's reasons for that. Some cases it's due to data privacy and security concerns. Other times it's due to latency of really needing high-performance access to data. And the other times, it's really just related to the interconnected nature of systems and that you need to have a whole bunch of systems which form an overall experience and they need to be located close together. So, one of the challenges that we've worked with customers and have actually developed our GreenLake solution to address is this idea of trying to achieve this cloud-like experience for all of your apps and data in a way that leverages the best of the public cloud with also that same type of experience delivered on premise. So as you think about some of the challenges, again, we touched on this that customers are trying to address. One of the ones is this idea of agility, being able to move quickly and to be able to take a set of IT resources that you have and deploy them for different use cases and different models. So, it's one of the things as we built GreenLake, we really had a strong focus on is how do we provide a common foundation, a common framework to deliver that kind of agility. The next one is this term on the top right called scale. And one of the words you may hear is you hear cloud talked about regularly is this notion of what's called elasticity and the ability to have something stretch and get larger kind of on an on demand basis. That's another challenge and premise that we've really tried to work through. And you'll see how we've addressed that. Now, obviously, as you do this, you can achieve scale if you just put a ton of equipment in place much more maybe than you need at any given time but with that comes a lot of costs. And so as you think about wanting to have an agile and flexible system, what you'd also like is something where the costs flexes as your needs grow and it's elastic and that it can get larger and then it can get smaller as needed as well. So, we'll talk about how we do that with our GreenLake solution. And then finally it's complexity, it's trying to abstract away the vision for people of having to be aware of all the complexity it takes to build these systems and provide a single interface, a single experience for people to manage all of their IT assets. So we do that through this solution called HPE GreenLake and really we call it the cloud that comes to you. And as you think about what we're really trying to do here is take the notion of a cloud from being a place where people have thought about the public cloud and turning that to an idea of the cloud being an experience. And so it's regardless of whether it's in the public cloud or running on premise or as is the case with GreenLake, whether it's a mixture of those and maybe even a mixture of multiple public clouds with on-prem experience, the cloud now becomes something you experience and that you leverage as opposed to a place where you have an account and that can include edge computing combined with co-location or data center based computing. It could include equipment stored in your own data center and certainly it can include resources in the public cloud. So, let's take a look at how we go about delivering the experience and what some of those benefits are as we put these solutions in place. So, as you think about why you'd want to do this and the benefits you get from GreenLake, what we've seen in terms of both working with customers and actually having studies done with analysts is the benefits are numerous, but they come in areas that are shown here, one time to deployment. And that once you get this flexible and easily to manage environment in place with what we'll show you are these prebuilt, pre-configured and managed as a service solutions, your time to deployment for putting new workloads in place can shrink dramatically. The next in terms of having these pre-configured solutions and combining both the hardware and software technology with a set of managed services through our GreenLake managed services team, what you can do is dramatically reduce the risk of putting a new workload in place. So for example, if you wanted to deploy virtual desktop infrastructure and maybe you haven't done that in the past, you can leverage a GreenLake VDI solution along with GreenLake management services to very predictably and very reliably put that solution in place. So you're up and running focusing on the needs of your users with incredibly lowered risk, because this was built on a pre-validated and a pre-certified foundation. Obviously, I talked earlier about the idea with GreenLake is that you have flexibility in terms of scaling up your use of the resources, even though they're computers that may be in your data center or a colo, and also scaling them back down. So if you have workloads over time, that may be even an end of month cycle or an end to quarter cycle where certain workloads get larger and then would get smaller again, the ability with GreenLake on a consumption billing basis is there where your costs can flow as your use of the systems flow. And again, I'll show you a screen in just a few minutes, that kind of illustrates what that looks like. And then the last piece is the single pane of glass for control and insight into what's going on. And what we mean by that is not just what's going on from a cost perspective, but also what's going on from a system utilization perspective. You'll see in one of the screens I'll show that there's a system utilization report of all of your GreenLake resources that you can view at any time. And so what you can get visibility to, for example, with storage capacity as your storage capacity is being consumed over time as you generate more data, the system will tell you, hey, you're getting up to about 60, 70% utilized. And then at that point, we would be able to work with you to automatically deploy even though you won't be paying for it yet, additional storage capacity so it's ready as your needs grow to encompass that. So in terms of what are some of these services that we deliver as part of GreenLake? Well, they range and you see here a portfolio of services that we offer. If you start at the bottom, it's simple things, right? Things like compute as a service, and I'll show you examples of that today, networking as a service, hyper-converged infrastructure as a service. And then if we work our way up the stack, we move from kind of basic services to platform services, things like VMware and containers as a service. And then if we go to the top layer of this, we actually can offer complete solutions for targeted workloads. So if your need was for example, to run machine learning and AI, and you wanted to have a complete environment put in place that you could leverage for machine learning and AI and use it and consume it on a consumption as a service basis, we've got our MLOps solution that delivers that. And similarly, I mentioned earlier, VDI for virtual desktops or a solution for SAP HANA. So, the solutions range from very basic compute at the foundation all the way up to complete workload solutions that you can achieve. And the portfolio of what these are is expanding all the time. And as you'll see, you can go out to our hpe.com site and see a complete catalog of all the GreenLake services that are available. So let's take a minute and let's drill in like on that MLOps solution. And we can take a look at how that fits together and what makes that up. So, if you think about GreenLake for MLOps, it's a fast path for data scientists, and it's really oriented around the needs of data scientists within your organization who have a desire to be able to get in and start to analyze data for advantage in your business. So, what comes with an MLOps solution from GreenLake starts at the left side of the slide here with a fully curated hardware platform, including GPU based nodes, data science, optimized hardware, all the storage that you're going to need to run at scale and that performance to make these workloads work. And so that's one piece of it is a curated hardware stack for machine learning. Next in the software component, we pre-validated a whole bunch of the common stack elements that you would need. So beyond operating systems, but things for doing continuous integration, for things like TensorFlow and Jupyter notebooks are already pre-validated and delivered with this solution. So, the tools that your data scientists will need come with this, ready to go, out of the box. And then finally, as this solution gets delivered, there's a services component to it beyond just us installing this full thing and delivering a complete solution to you. But the GreenLake management services options where our services teams can work side by side with data scientists to assist them in getting up to speed on the solution, to leveraging the tools, to understanding best practices if you want those, if you want that assistance for deploying MLOps and the whole thing's delivered as a service. As similar, we similar solutions for other workloads like SAP HANA that would leverage again, different compute building blocks, but always in a way that's done for workload optimized solutions, best practice and that build up that stack. And so your experience in consuming this is always consistent, but what's running under the hood isn't just a generic solution that you might see in for example, a public cloud environment, it's a best practice, hardware optimized, software optimized environment built for each one of the workloads that we can deploy. So I like to do at this point is actually show you what's the process like for actually specifying a GreenLake solution. And maybe we'll take a look at compute as our example today. So, what I've got here is a browser experience, I'm just in my web browser, I'm on the hpe.com website and what I'd like to do. I mean the GreenLake section and I've actually clicked on this services menu and I'm going to go ahead and scroll down. And one of the things you can see here is that catalog of GreenLake services that I referenced. So, just like we showed you on the slide, this is that catalog of services that you can consume. I'm going to go to compute and we'll go about quoting a GreenLake compute solution. So we see when I clicked on that, one of the options I have is to get a price in my inbox. And I'll click on that to go in here to our GreenLake quick quote environment where if in my case here for our demonstration, I'll specify that I'd like to purchase to add to my GreenLake environment some additional general compute capability for some workloads that I might like to run. If I click on this, I go in and you notice here that I'm not going to specify server types. I'm really going to tell the system about the types of workloads that I'd like to run and the characteristics of those workloads. So for example, my workload choices would be adaptable performance or maybe densely optimized compute for highly scalable and high performance computing requirements. So, I'll select adaptable performance. I have a choice of processor types, my case, I'll pick Intel. And I then say, how many servers for the workloads that I want to run would be part of the solution. Again, in my case, maybe we'll quote a 20 server configuration. Now, as we think about the plans here, what you can see is we're really looking at the different options in terms of a balanced performance and price option which is the recommended option. But if I knew that the workloads I were going to run were more performance optimized, I could simply click on that option. And in the system under the hood does all the work to reconfigure the system. I'm not having to pick individual server options as you see. So once I picked between cost optimized balance or performance, I can go in here and select the rest of the options. Now, we'll start at the top right and you see here from a services perspective, this is where it specifies how much services content and in services assistance I'd like all the way from just doing proactive metering of my solution all the way through being able to do actual workload deployment and assistance with me physically managing the equipment myself. The other piece I'll focus on is this variable usage. And this comes back to how much of the variable time, variable capacity of additional capacity, what I like to have available in my data center for this solution. So if I know that my flex could be larger in the future of the capacity, I want to flex up and down. I might pick a slightly larger amount of flex capacity at my location as part of this solution. With that, I'd select that workload. And the less steps would be, I could click on get price and this whole thing will be packaged up and shipped to you in terms of the price of the solution. And any other details that you might like to see. And I encourage you to go out to hpe.com and to go through this process yourself for one of the workloads that might be of interest for you to get a flavor of that experience. So if we move forward, once you've deployed your GreenLake solution, one of the things you see here is that single pane of glass experience in terms of managing the system, right? We've got a single panel that all in one place provides you access to your cost information for billing, and what's driving that billing, your middle and the middle of the top center, you can see we've got information on the capacity planning but then we can actually drill in and actually look at additional things like services we offer around continuous compliance, capacity planning data for you to build and see how things like storage or filling, cost control information with recommendations around how you could reduce or minimize your costs based on the usage profile that you have. So, all of this is a fully integrated experience that can span components running both on-premise and also incorporating services that could be in the public cloud. Now, when we think about who's using this and why is this becoming attractive? You can imagine just looking at this capability that this ability to blend public cloud capabilities with on-premise or in a co-location, private data center capabilities provides tremendous power and provides tremendous flexibility for users. And so we're seeing this adopted broadly as kind of a new way, people are looking to take the advantages of cloud, but bring them into a much more self-managed or on-premise experience. And so some example, customers here include deployments in the automotive field, both at Porsche or over on the right at Zenseact, which is the autonomous driving division of Volvo where they're doing research with tremendous amounts of data to produce the best possible autonomous driving experience. And then in the center, Danfoss who is one of the world's leading manufacturers of both electric and hydraulic control components. And so as they produce components themselves, that drive an optimized management of physical infrastructure, power, liquids and cooling, they're leveraging GreenLake for the same type of control and best practice deployment of their data centers and of their IT infrastructure. So again, somebody who's innovating in their own world taking advantage of compute innovations to get the benefits of the cloud and the flexibility of a cloud-like environment but running within their own premise. And it's not just those three customers clearly. I mean, what we're seeing is, as you see on the slide, it's a unique solution in the market today. It provides the true benefits of the cloud, but with your own on-premise experience, it provides expertise in terms of services to help you take best advantage of it. And if you look at the adoption by customers, over a thousand customers in 50 countries have now deployed GreenLake based solutions as the foundation on which they're building their next generation IT architecture. So, there's a lot of unique capabilities that as we built GreenLake, that we have that really make this a single pane of glass and a very, very unified and elegant experience. So as we kind of wrap up, there's three things I want to call your attention to, one, GreenLake, which we focused a lot on today. I'd also like to call your attention to the point next services, which are an extension of those GreenLake services that I talked about earlier but there's a much broader portfolio of what Pointnext can do in delivering value for your organization. And then again, HPE financial services who much like what we do with GreenLake in this as a service consumption environment can provide a lot of financial flexibility in other models and other use cases. So, I'd encourage you to take time to learn about each of those three areas. And then there's obviously many many resources available online. And again, there's some that are listed here but it kind of as a single point takeaway from this slide, I encourage you to go to hpe.com. If you're interested in GreenLake, click on our GreenLake icon and you can take yourself through that quoting experience for what would be interesting and certainly as well for our compute solutions, there's a tremendous amount of information about the leading solutions that HPE brings to market. So with that, I hope that's been an informative set of experience. I'm thanking you for spending a little bit of time with us today and hopefully you'll take some time to learn more about GreenLake and how it might be a benefit for you within your organization. Thanks again.

>>Lai from Orlando, Florida. It's the cube covering Microsoft ignite brought to you by Cohesity. >>Good afternoon, cube viewers. We are here at Microsoft ignite at the orange County convention center. I'm your host, Rebecca Knight. Along with my cohost Stu Miniman. We're joined by Edward Thompson. He is the product manager at get hub. Thank you so much for coming on the queue. So the get hub acquisition closed this time last year, uh, for our viewers who are maybe unfamiliar with get hub, explain what get hub is and then also tell us a little bit how it's going since the, >>yeah, I'd be happy to. So yeah, get hub is like the home for software development. If you're a, if you're a software developer, uh, you know, get hub rehost, you know, most of the open source repositories in the world. Um, you know, just to give you some stats. So at this time, last year, about the time the acquisition happened, um, we announced ad get hub universe, which is our annual developer conference, uh, that we had 30 million developers on GitHub and a hundred million repositories. So that's, that's a huge number of developers. I haven't seen the latest numbers. We'll announce the newest, uh, at get hub university this year, which is coming up next week. Uh, but the last number I saw was 40 million developers. So that's a growth of, you know, 10 million developers in just a year. Unbelievable. And that, that also means the 25% of our developers on get hub have joined within the last year. So that's just absolutely incredible. Um, and so yeah, I get hope. Is, is, is that, is that place for development? >>Yeah, it's really interesting when I look at some acquisitions that Microsoft has made back in 2016, they spent $26 billion for LinkedIn, which is most people's resume. And if you look last year it was seven and a half billion dollars for my friends in the software world. Get hub is their resume. That's right. Oh, when you talk about how you do things online, so you've got an interesting perspective on this because you've worked for Microsoft and get hub a couple of times. So give us a little bit about, you know, the relationship when you joined Microsoft 10 years ago, you know, open source developers, developers, developers weren't exactly on everyone's lips. So it gives a little bit of viewpoint through the various incarnations. >>So as you said, I joined Microsoft about 10 years ago. I came in through a little acquisition. Uh, we were just a very small software company, but we were building enterprise cross platform developer tools and we were about five engineers. And when you're building for, you know, Mac OS, Linux, Sonos, all these different platforms you use with so many people with so few rather, so few developers, you really need to take as much off the shelf as possible. You can't build all that yourself, you know. So if, if you needed a logging library, we would just go and use some open source products. We're not going to spend our time working on that when we could be building customer value in step. So when Microsoft acquired that company, they looked at, you know, they did their due diligence, they looked at the source code and they saw all this open source and they, I mean it was almost a deal breaker. >>They really lost their mind. Um, they were not geared up to deal with open source, to use open source, certainly not to contribute to open source. Uh, and so that's the Microsoft that I first saw. And, and to get from there to here is, is incredible. You know, over time. Um, we worked closely with some open source tools. We worked closely with get hub at Microsoft and that was really one of the early sort of unions between Microsoft and get hub was starting to work together on, on some open source software. And so we kind of started to know each other. We started to understand each other's companies and each other's cultures. And we started to, I don't know, I dare say like each other. Like I still count some of those early get hub employees that I met, uh, as some of my closest friends. Uh, and so at some point, uh, they became such close friends that I went to go work with them and get hub and then of course the Microsoft acquisition and so on. But I really think that that, you know, the, the transformation in Microsoft between, uh, the 10 years ago, Microsoft that really didn't get open source and today is, is just incredible. >>Well, let me just sit in that, in that culture and maybe culture clash a little bit the first time around because Microsoft developers have their own culture and their own uniform and their own way of interacting with each other. The, the, the hours that they work, which is very different from Microsoft, which is a pretty middle-aged Volvo driving kind of organization. So how, how does that work and, and what is, what has it been like the second time around the Microsoft as a middle aged Volvo driver? I think you can, you can >>wear a hoodie in and drive a Volvo. Um, no, I think it's been, I think it's been really great. The interesting thing about Microsoft is that it's not, you know, with so many people, it's not just like a homogenous big company. Um, we do have, you know, the developer tools division is a little bit different than offices, a little bit different than windows. And so they all have their own sort of unique cultures and, and now get hub slots in as its own unique culture. And we can, you know, we can talk to each other and we can understand each other, but we don't necessarily have to be all the same, you know, we can get hub team does kind of work some, some of us do work kind of weird hours. And, and I think that somehow that that works, especially with, you know, new tools coming to, um, coming to the marketplace, uh, you know, chat applications, we can be a lot less synchronous. We can be a lot more online and leave a message for each other. You know, we get out, we use get hub issues and pull requests to collaborate on almost everything, whether it's legal, uh, or, you know, our, our PR department. And it's not just developers. So we're trying to take these, these tools and, and sort of apply them to allow us to have the culture that we want at get hub. And I think Microsoft's doing the same thing as well. >>So speaking of new tools and you're, you're speaking here at ignite, you're about to announce the new repository with lots of new capabilities, enabling users to deploy at to any cloud. So tell us a little bit about, about the, this new tool. >>Yeah, so, uh, we announced, we call it get hub actions. We announced it last year at, at get hub universe. Our, uh, again, our, our annual developer conference. And our goal with GitHub actions was to allow people to take, you know, we've got 100 million repositories on get hub. We wanted our users to, to take those repositories and automate common tasks. Let me, let me give you a concrete example. Um, a lot of times somebody will open an issue on a, on a good hub repository, you know, uh, Hey, this doesn't work. I've got a bug report, you know, and they'll fill out an issue. And often either they didn't understand things or, um, the issue resolved itself, you know, who knows. We call that, uh, an issue that goes stale. And so you can build a workflow around that repository that will look for these stale issues and it will, uh, you know, just close them automatically. >>That gets rid of the mental tacks for somebody who, for a, for a developer who owns this repository to allow this, you know, this workload to just do it automatically. And so that's an example of a, a get hub actions workflow. Um, some people, uh, don't like swearing in their repository and you know, so if somebody were to open a bug report, you know, they might be angry. And so you could actually have a get hub workflow that looks for certain words and then replies and says, Hey, that's, here's our code of conduct. That's not the way we roll here. And actually a lot of people find that that feedback coming from a robot, uh, is a lot easier to take than a feedback coming from a human cause. They might want to meet with a person, can't argue with a robot. Well, not successfully. >>I think I have argued with the chat bot in my day. But anyway, >>yeah. So that's what we did a year ago and we opened it up into the beta program and we really quickly got feedback that, that people liked it and people were doing some really innovative things. But the one thing that people really wanted to automate was their bills. They wanted it to be able to build their code and deploy it. And we were just not set up for that. We, we, we didn't build, get hub actions as that platform in 2018 so we kind of had to pause our beta program. You know, I, they, they, they say that no, uh, no good plan survives first contact with the customer. So we had to, we had to hit pause on that. Uh, and we retooled. Um, we, we just sort of, I don't know, iterated on it, I guess. Uh, and we basically built a new platform that supported all of that repository automation capability that we had planned for in the first place. But also allowed for continuous integration build and deployments. So, um, we brought Macko S we brought Linux and windows runners, uh, that we host, uh, in our cloud, um, that people can use to build their software and then deploy it. And again, yeah, we want to be absolutely a tool agnostic. So any, any operating system, any, uh, language and cloud agnostic, we want to let anybody deploy anywhere, whether it's to a public cloud or on premises. >>Yeah. Uh, so, and with this, the second year we've done our program at this show and we really feel it's gone through a transformation. You know, this is a multi decade in a windows office. Uh, the business applications, uh, you know, cloud seeped in, developers are all over the place here. The day two keynote was all about app dev. Um, I'd love to get a little compare and contrast as to, you know, what you see here at Microsoft ignite versus, and I guess what I would call a pure dev show next week. Get hub universe happening in San Francisco. >>It's true. Get up universe is pretty much a pure dev show. Um, we, we have fewer booths, we have smaller booths. Uh, but, uh, and, and honestly, we have fewer sort of, um, I don't know, enterprise sorta. It, it pro crowd is what we used to call them. Um, but we do of course have a lot of dev ops. So, you know, we get up university has a lot of developers, but, uh, we're seeing a lot of dev ops, so there's a lot of meeting in the middle because, you know, I started out my career as assistant man actually. So I remember just, you know, doing everything manually. Um, but that's not the way we do things anymore. We automate all of our, uh, automate, uh, deployments. We automate all of our builds. You know, I don't want to sit there and type something into a console cause I'm going to get it wrong. Um, you know, I've accidentally deleted config files on production servers and that's, that's no good. So I think that they're, uh, get up universe is very different. A to ignite, it's much smaller, it's more intimate, but at the same time, there's a lot of, uh, overlap, especially around dev ops. >>Yeah. Uh, Satya Nadella yesterday in the keynote talked about the citizen developer as a big push for Microsoft. He said 61% of job openings for developers are outside the tech sector. Um, w what do you see in that space? Uh, the different developer roles these days? >>Uh, I think it's, it's absolutely fascinating. When I, uh, when I started my career, you know, you were, you were a developer and you, and you wrote code probably at a development company. Um, but now like everybody is automating tools, everybody's adopting machine learning. Um, when I look around at some of my friends in finance, uh, it's not about, it's not about anything but tech anymore. That's th they're, they're putting technology into absolutely everything that they do to succeed. Uh, and I think that, I think that it's amazing. Um, uh, like I said earlier, uh, 25% of developers on get hub have joined within the last year. So it's clear that it's just exploding. Um, everybody is doing, uh, software now. Yeah. >>There's something for the citizen developer on get hub though. Or is it too high level? I think >>I don't think it's too high level. I think that, uh, I think that that's a great challenge that we need to really step up to. Yeah. So Edward, >>the other big themes we heard here is talking about trust. So, you know, we talked about how Microsoft is different today than it wasn't in past, but I'm curious what good hub seen because you know, in social media when the acquisition first happened, it was, wait, I love GoodHub hub, I love all those people, but Hey, get lab. Hey, some of these other things I'm, you know, I'm fleeing for the woods. And every time I've seen an open source company get bought by a public company, there's always that online backlash. What are you seeing? How has the community reacted over the last year? >>I understand that skepticism. Uh, you know, I would be skeptical of any, uh, sort of change really. I, you know, the, the whole notion of who moved my cheese. But I think that the only way that we can, we can counter that is just to prove ourselves. And I think that we have, I think that Microsoft has allowed get hub to operate independently. And I think that, you know, I think a lot of people expect it to all of a sudden everything to change. And I don't think everything did change. I think that, uh, get hub now has more resources than it used to to be able to tackle bigger and more challenging problems. I think that get hub, uh, now can hire more and, and, and deploy to more places. And so I really just think that we're just going to keep doing exactly what we've been doing just better. So I think it's great. >>So universe happening next week teed up a little bit for us. What are some of the most exciting things that you're looking forward to? What kinds of conversations that will you be having? Presentations? >>So the big one for me is, is actions. I've, I, I've been just completely heads down working on, on get hub actions. So I'm really excited to be able to put that out there and, and you know, finally give it to everybody. Cause you know, we've been in beta now. Uh, like I said, we've been in beta for a year, which sounds like a ridiculous amount of time. Uh, but you know, it, it did involve a lot of retooling and rethinking and, and iteration with our, our beta testers. Um, and so the biggest thing for me is, is talking to people about actions and showing what they can do with actions. I'm super excited about that, but we've got a lot of other interesting stuff. You know, we've done a lot in the last year since our last universe. We've done a lot in the security space. Um, we've done, uh, we've both built tools and we've acquired some. Um, and so we'll be talking about those, uh, get hood package registry, which goes along really well with get hub actions. Uh, I'm super excited about that too. But yeah, I mean my, my calendar is, is, is just booked. Um, it's great. So many people like want to want to sit down and talk that I'm, I'm super excited about it. >>Excellent. Well great note to end on Edgar Thompson. Thank you so much for coming on the queue. We appreciate it. Thank you. I'm Rebecca Knight. First two minutes, stay tuned for more of the cubes live coverage from Microsoft ignite.

>>Live from Denver, Colorado. It's the cube covering comm vault. Go 2019 brought to you by Combolt. >>Hey, good morning. Welcome to the cubes coverage of combo go 19 I'm Lisa Martin and it was stupid man. Hey Sue. Hey Lisa. Are you ready? I was going to ask you. Yes. Are you ready? >>I believe the statement this morning was, we're born ready. >>We are born ready? Yes. That was a big theme this morning. It's the theme of the event here at con Volvo 19 in Colorado and great parody this morning of all these old video clips of all these actors including the Lego movie stars from saying I'm ready. Even SpongeBob. That one got me, so we had a great day. Yesterday's to love some news came out Monday and Tuesdays a lots of great stuff to talk about. We had there a lot of their C level execs and let a new changes a call yesterday. Really got the vibe of, Hey, this is a new Combalt. >>It's interesting Lisa, because one of the things we've been talking about is the 20 years of pedigree that the company has. This Andre Mirchandani said yet they're doing some new items. I was talking to some of the partners in there like how come metallics like a separate brand, don't you worry about brand spread? We knew a thing about having too many brands on the program so it is the history, the experience, the lessons learned, the war chest as they said of all of the things that have gone wrong over the years and I sure know that from my time living on the vendor side is there's no compression algorithm for all the experience you've had and like, Oh we fixed something in that stays in the code as opposed to there's something brand new might need to work through things over time but metallic a separate brand but leveraging the partnerships and the go to market and the experience of Convolt overall. >>So if you want, my quick take is, you know metallic. I definitely, I think coming out of here is the thing we will be talking the most about their SAS plus model. I want to see how that plays in the marketplace. As I probed Rob, when we interviewed him, customers, when you think about SAS, it should just be, I worry about my data and I get up and running and they said they have a very fast up and running less than 15 minutes. That's great. But some of that optionality that they built in, Oh well I can bring this along or I can add this and do this. It's always worried that a wait, do I have to remember my thing? And as it changes down the road, do I have everything set up right? Those are things that we're trying to get away from when we go to a SAS or cloud model. >>And to your point, another theme of the show has been about operational simplification, not just what Combolt is doing internally to simplify their operations, but what they need to deliver to customers. Customers want simplicity rates. Do we, we talk about that at every show regardless of industry, but there is this, this line, and maybe it's blurring, >>like we talked a lot about blurred lines yesterday of too much choice versus simplification. Where's the line there? >> Yeah and a great point Lisa, so one of the items Sandra Mirchandani said yesterday in his keynote was that blurring the line between primary and secondary storage and I probed him on our interview is Convolt going into the primary storage market with Hedvig. Hedvig has got a, you know, a nice offering, strong IP, good engineering team. I think they want to make sure that customers that have bought head vigor want to keep buying Hedvig we'll do it, but it really, I think two years from now when you look back at is that core IP, how does that get baked into the solution? That's why they bought it. That's where it's going to be there. I don't think we're going to be looking two years from now and saying, Oh wow know Convolt they're going up against all the storage star Walton competing a bit gets HCI and everything. >>They have a strong partnership, so I think I got clarity on that for the most part, even though the messaging will will move over time on that, it will move over time on that. >> That's a good point that the song blurred lines kept popping into my head yesterday as we were talking about that. But one of the things that was clear was when we spoke with Rob Kalusi and about metallic, we spoke with Avinash Lakshman about Hedvig Sanjay as well as Don foster. They're already working on the technical integration of of this solutions and we even spoke with their VP of pricing. So from a customer, from a current Hedvig customer perspective, there is focus on that from Combolt's perspective. It's not just about integrating the technologies and obviously that has to be done really well, but it's also about giving customers that consistency and really for combo kind of a new era of transparency with respect to pricing. >>And another thing we talked about some of that transformation of the channel and Mercer row came on board only a couple of days officially on the job. He's helped a number of companies get ready for multicloud and absolutely we've seen that change in the channel over the last five to 10 years. Know back in his days when he was at VM world at VMware there the channel was, Oh my gosh, you know, when Amazon wins we all lose and today we understand it as much more nuance there. The channel that is successful partners with the hyperscale cloud environments, they have practices built around it. The office three 65 and Microsoft practices are an area that Convolt in their partners should be able to do well with and the metallic will tie into as well as of course AWS. The 800 pound gorilla in this space will be there. Combolt plays into that and you know, setting the channel up for that next generation with the SAS, with the software and living in a broader multicloud environment is definitely something to watch you a lot of news about the channel, not just from a leadership standpoint but also so metallic for the mid market >>really delivered exclusively through the channel but also the new initiative that they have. And we talked a little bit about this yesterday about going after and really a big focus with global systems integrators on the largest global enterprises. And when we spoke with their GTM chief of staff yesterday along with Mercer with Carmen, what they're doing, cause I said, you know, channel partners, all the channel partners that they work with work with their competitors. So you have to really deliver differentiation and it can't just be about pricing or marketing messaging goes all the way into getting those feet on the street. And that's another area in which we heard yesterday Combolt making strategic improvements on more feet on the street co-selling with partners, really pulling them deeper into enablement and trainings and to them that's one of the key differentiators that they are delivering to their partners. Yeah >>and Lisa, he, we got to speak to a number, a couple of customers we have more coming on today. It's a little bit telling that you know the average customer you talk to, they have five 10 years of experience there. They are excited about some of the new offerings, but as we've said many times metallic, the new Hedvig we want to talk to the new logos that they're going to get on board. That is something that for the partners has been an incentive. There were new incentives put in place to help capture those new logos because as we know, revenue was actually down in the last fiscal year a bit and Convolt feels that they have turned the corner, they're all ready to go. And one other note I'd like to make, the analogy I used last year is we knew a CEO was canoe CEO search was happening, a lot of things were in motion and it's almost as if you were getting the body ready for an organ transplant and you make sure that the antibodies aren't going to reject it. And in conversation with Sanjay, he was very cognizant of that. His background is dev offs and he was a CIO. We went for it, he was the CEO of puppet. So he's going to make things move even faster. And the pace of change of the last nine months is just the beginning of the change. And for the most part I'm not hearing grumbling underneath the customer seem fully on board. The employees are energized and definitely there was good energy last year, but a raise of the enthusiasm this year. >>Well Stu, first of all, you have just been on fire the last two days comparing their CEO transition to getting a body ready for a transplant. It's probably one of the best things I've heard in a long time. That was awesome. But you're right, we've heard a lot of positivity. Cultural change is incredibly difficult. You talked a minute ago about this as a 20 year old company and as we all have all experience and the industries in which we're in, you know, one of the things that's important is, is messaging that experience and talking about the things that that worked well, but also the things that didn't work well, that they've learned from that message was carried through the keynote this morning. That three customers on stage that we saw before we had to come to the side. And I, I had, my favorite was from Sonic healthcare. Matthew McCabe's coming on in shortly with us and I always appreciate, you know, I think the voice of the customer is the best brand validation that you can get. However, what's even better is a customer talking about when the technologies that they're using fail because it does happen. How are they positioned with the support and the training and the education that is giving them to make those repairs quickly to ensure business continuity and ensure disaster recovery. I think that to me that speaks volumes about the legacy, the 20 years of experience that combo has. >>Yeah, no, Lisa, you're absolutely right. There's certain products out there that we talk about uptime in 100% in this space. You, I believe the stat was about 94% success rate and we had NASA in the keynote yesterday talking about success versus partial success versus failures and Convolt really embraces that and has customers that we'll talk about that because there are times that things will happen and there are things that you need to be able to recover from ransomware. Often it is not a question of if, when it is going to be happened, at least. The other thing I want to get your comment on Jimmy chin who is the director and one of the, the cameraman of the free solo Oscar-winning free solo documentary definitely gave me a little bit of, Oh my gosh, look at some of the Heights and I was nervous just looking at some of this stuff they're doing. I like a little bit of lightweight hiking. I'm not a mountain climber, nothing like that. But he talked about when the camera goes on, there's that added pressure that goes on and it's sitting there. It's like, yeah, you know, we sit here live all day doing that. There's that, that energy to perform. But you know, we all appreciate the everybody watching and understanding that we're all human here and every time, every once in awhile a word or a mistake gets in there, but we keep going summit. Yeah, >>that's life. But also Jimmy chin, phenomenal. I think at 2018 they just won the Oscar just earlier this year for free. Solo. I have to watch that this weekend. But a couple of things that he talked about is that failure is a huge part of preparation. Couldn't agree more. What a simplified statement for somebody that not only has has skied Everest, the climbed Meru, I think they call it the shark fin of India, but what you talked about with what he documented with free solo and all of the thousands of sequences and he talked about that, Alex, I'm forgetting his last name, the guy who closed, who free soloed, El Capitan, all of these different failure scenarios that he rehearsed over and over again in case he encountered any of them, he would immediately be to remedy that situation and get himself back on track. I thought that message to me, failure is a good F-word if you use it properly. You know NASA, you mentioned yesterday and NASA was famous for coining in the 60s failure is not an option and I always say onto that cause I used to work for NASA, but it's a distinct possibility. And so what Jimmy chin shared this morning was electrified, but it also was a great understatement of what Combolt is helping their customers. We have to help you prepare for this. We can't help you prepare for all of it. As you mentioned, ransomware, it's not if but when. >>Well, right and both NASA and when the climbing is understanding where something could go wrong and therefore what the failures scenarios are. So you know rockets today you can't have a failure and by failure they mean look, if the rocket isn't going to work or something goes wrong, we need to make sure we don't have loss of life. That is something that if you look at blue origin and SpaceX that is pre eminent in there is we can't have another challenger disaster. We can't have some of these environments where we have the loss of human life. So that is number one. Some of the other ones, sometimes we know that the unknown happens or things don't go quite right. So being prepared to understand if something goes wrong, how do we recover from that? And that brings us back to the whole data protection and recovery of the environment because the best laid architecture, eventually something will happen and therefore we need to make sure that that data, the lifeblood of the company is able to be recovered and used and that the business can go forward even if some piece of infrastructure or some attack got through. >>There are, and there's inherent risk in every industry, whether you're talking about healthcare data, we talked with AstraZeneca yesterday, you know, genetics, clinical data, or you're talking about a retailer, doesn't matter. There's an inherent risks with every business and one of the most important things that I got out of the NASA talk yesterday, Jimmy Chin's talked today, some of the customers, is that preparation is key. You can't be over prepared. You really can't act fact. He said that you can't be overprepared in his line of work, but I think it applies to the inherent risks that any business has. Managing data. As we talk about Sue all the time, it's the lifeblood. It's the new oil. It is. It has to be available, accessible 24 by seven if it isn't and can't be. Businesses are massive risk in this day and age. Competitive competitors who have maybe better risk fault tolerance scenario in play. >>So that risk that they have to mitigate comes a preparation. We're going to be talking with Sandra Hamilton in just a few minutes about who leads customer success for combo. Really want to dig into the training, the support. We've heard that articulated from customers on stage that I don't wake up in the middle of the night anymore because I have this support from my trusted vendor combo and that is critical to any business staying up. Absolutely. We're going to hear from number of customers. I'm sure they're ready and we are ready for day two. We are ready. See, let's have a great day. Yeah, thanks. All right, so Sue and I will be right back with our first guest on day two of our coverage of comm Volkow for Stu. I'm Lisa Martin. We'll be right back.

>> live from London, England. It's the queue covering a ws summat. London twenty nineteen Brought to you by Amazon Web services >> Hello and welcome to the Age Ws Summit live from London's Excel Center. I'm Susanna Street, and this is my co host on the Cube Day Volonte on. There are lots of breakout sessions taking place right across this venue. One of them all about Bring Thio life, the eight of us marketplace and really helping people, companies and stand cow to make that journey to the cloud. And my two guests here right now have been at that session trying to communicate that toe many delegates who were there here Mobile, who's from Computer Center. He is the public cloud lead for the UK and Ireland, and Garforth, who's a director off a ws marketplace. Thank you very much for joining us >> to be here >> Now there are riel complexities are their way. Just helping people navigate their way through. Tell me that a bit more about how marketplace has evolved because it's being rapid. Hasn't >> it? Has been rapid. We launched a CZ initial service in two thousand twelve, so we just had our seventh birthday last year. We started with pretty modest aspirations, and it was all about helping developers take advantage of the sea to and be able to take advantage of. A bus. Service is available at the time. So it was a cattle about two hundred fifty mostly open source applications that developers could sort of find, explore, discover and provisions straight from the council where they were doing their work. Overtime. We've added support for a lot of new product type, so we support SAS applications. All right, reinvent Last year, we announce support for Dr in being able to take Dr Images and deploy those into stage maker. We're talking about that earlier. Also support for containers. And so his customers are moving to more of a survivalist type architecture. We have already made set of container images that they could deploy directly into the S E. K s or far gate. I'd say one of more interesting sort of inflection point in our evolution was when people started buying real stuff for real money because I think when we got started serving the developers, I kind of think of that is kind of a Lamborghini kind of crowd. That's a customer, by the way, but, uh, Lamborghini guys just, you know, developers want to go as fast as they possibly can. They don't really care for speed limits, you know, they just want to get the job done as quick as they can. Um, we had an example, for example, our first million dollar transaction. Wait, We're surprised to see it. We woke up on Monday and we saw a million dollar transaction. So I told my finance team not to get too excited. I went to the customer and I said, Was this a mistake or did you intend >> to do >> that? And the developer team said No, that was the best software sale ever because I didn't have to talk to anybody. >> I couldn't make money while you sleep isn't absolutely, but they were >> able to. Basically, they didn't have to go through a lengthy process of procurement and legal reviews and everything else. They literally were able to subscribe to the product and get it deployed within seconds, and the estimated that it took about three months off of their engineering cycle was being able to go that fast. But >> the interesting thing on >> million dollar transactions is, there's a lot of other people that care about that. So I got a letter about eight weeks later from their corporate headquarters in New York. It said that Development team was not >> really authorized to spend that much money on that product, >> and so that is what I call the Volvo crowd. And there are big parts of our customer that are very, very interested in safety and airbags and collision avoidance and all that other fun stuff. And so what Marketplace has been really innovating on in the last couple of years is finding a way to modernize how companies buy and deploy softer in the cloud. Do that at speed. But do it in a way that's compliant with whatever regulations governing the things. >> So do it speed but variable speed, >> variable speed and just, you know, a lot of our customers in the public sector or in health care financial services. They're heavily regulated on on their own, and they have a certain way they need to do things. And so we've been building features like the private marketplace which we just launched actually allows the customer to go in and reason over our catalog We've got forty eight hundred listings in our catalog, fourteen hundred different vendors and they can decide on their own. Which one of those air fruit for use or not, >> because it's very hard to meet the procurement demands of various of public sector organization because they're so >> they are very diverse. But that's also one of the reasons, like I'm excited too heavy in here. We've been working for the last couple of years to figure out how we can more effectively work with partners to sort of serve our joint customers. So he and what's your story? How >> do you fit what? It's a good question. So I think Computer Center entered into the fray with eight of us, sort of circa reinvent twenty seventeen. So just a time where Marketplace was launching two partners, I guess in the mainstream on on, we looked at what the offering in partnership with these guys and what it would mean to our customers, and that was kind of very customer letters and organization if you know anything about us. Customers were asking for different ways to potentially by traditional software packages as they moved into the Ws Cloud, and they were moving at scale and that velocity that we talk about and it was about well, is this a product or a mechanism that can help them streamline? Can they simplify on the way? Can they cut some of that complexity on that journey? We see that very much as a Roald. Help them achieve that. This seems like a really good mechanism, so we fast forward through twenty eighteen. We do some great deals together, those sort of way talk about on way. See that this is becoming more mainstream for customers. Is their landing in a ws in the cloud and thinking about different ways? Different software titles challenging Do We Need to Do Things is normal, or should we do things a different way? What about this dynamic that we were just talking about? That garden was just saying about the procurement folk, the >> Volvo crowd versus the Lamborghini Cross You what do you have developed a workflow approval process that it worked? Yeah, well, unpack it a little bit, the the private marketplace allows, and every customer is a little bit different. Sometimes it's the chief security officer who kind of makes the final decision. Sometimes it's procurement. Sometimes the legal team has specific move constraints on what they what. They want to prove that not I really haven't found two customers that are identical in terms of how they're worked over an l O B manager. Correct CFO. I mean, you're right, lots of different roles. So we effectively, we did some surgery on the underlying service to create a new I am role. And so if Ian is the administrator for his organization, regardless of role, he's given permission to go approve and disapprove products. And some customers are kind of in a white list load, which is basically you can use, uh, only the things that I wait listed. So everything's forbidden until I've explicitly approved it. Other companies, like a lot of smaller companies that may not have that much process. We're more of a blacklist mode. We're sort of like everything in the marketplace is fair game, except the ones I've specifically said not to use on DH. So we just created this really flexible infrastructure that lets customers customize the marketplace to their needs. So you give superpowers to some admin and then the white list black blacklist, depending on what it is. And then it becomes frictionless. It becomes frictionless, and then the user experience the customer can actually have their own logo. They can put their own language around, kind of how they wantto sort of represent that to the developers. And then every developer in their organization then sees that experience and they can see what's been approved in what hasn't. OK, so you get a private label through the channel. Yeah, so that I, as a consumer see whatever brand that your customer yet need to see exactly. And then we've also got a facility because, you know, with over forty eight hundred listings in the marketplace, fourteen hundred different vendors, you know, nobody's got time to go reason over every single item, and we're adding hundreds every year, so that keeps growing. And so we've got a facility. If the developer has a specific technology that they really require, we've got a little simple work flow so developed could say, I need this widget to build this thing, and then we kick it off to the admin who could approve it. And as we were talking about for our video closet, you gonna have precise understanding of the pricing. You know this one hundred percent clarity. And then once you have that on you, Khun, split the pie hole, then you can split up and we did. But like one of the foundational technologies that we launched, twenty seventeen was this notion of a private offer. And so if I want to make a private offer to Ian at a price that he and I have negotiated on legal terms that he and I have agreed to, I can do that through marketplace. And then what with the way that would work in a large organization is once somebody's subscribes Once to that price, everybody in the organization that used that product is using it at the agreed price. OK, right. And then we extended that to enable Channel partners now. So for the ice fees that included center works with now, he's now able to go create private offers for his custom. So what, you're essentially created a two sided >> marketplace that effect? Yeah, I think the interface between the two organizations is really important. It becomes that sort of tripartite with the ice V, putting the customer right in the center. I think that's the signage is that we seem to organizations. >> Do you really see what your input has bean there items that are listed as well. Did you get that >> for, like, selection? >> Yeah, yeah, that that like, you know, >> saying it's pretty customer focused, you know, we work with customers we have. We have a set of people around the world that do what we call category management, and they theirjob is to work with customers and make sure that we're stocking the right inventory on the shelves, so to speak. So we get that input like every day, >> and then that helps you develop you new products, >> New continent, new products. And that's >> ahead of the competition. >> Wei. Try to think more about like, let's focus on our customers. Wei don't spend a lot of time chasing tail lights, but very customer obsessed. What things always >> interested me about the marketplaces. It's so complex in terms of region's >> tax laws, pricing considerations on and on and on so many permutations. You talk a little bit about how you've >> succeeded in just essentially making that all transparent and what what's behind that? >> Um well, I think you know Amazon >> and eight of us like we operate within the legal frameworks and all the countries where we operate in. So we have our own requirements in terms of how we remit and collect tax in countries compliant with local laws. Right. So we had to do that just to operate a to B S right way were able to leverage a lot of the same plumbing we had to build for ourselves and effectively make that available to our lives. So we have, like, there's a small eyes. We actually they've grown to be quite big. But here in the UK is a company called Matile Ian, who uses us exclusively a cz, their cloud channel. Um and we take him the HBS available eighteen regions marketplace on, and then everywhere we need to we will remit and collect tax on his behalf and then give him reports that he could share with his auditor to ensure compliance with local laws. And so we do a lot of that stuff. He's a small firm, you know, and for us to be able to sort of, like, extract and abstract all that complexity from him and just give him a nice monthly report that shows him all the taxes we can on his behalf. That's a big service right >> now. How's it transform your business? >> So I say transforming rather than transformed because it's a continuum thing all the time. I think it's absolutely that a different way of procurement is, firstly, the thing that customers are asking for. So it's just one cog in the wheel for a ws that customs picking up on. I think the point that golf is very well glossing over is that between us, we're doing the heavy lifting on behalf of the customer. I think that's today's point thing. That's that's the whole point here, where that we've all got a part to play in the ecosystem and it's it's all about customer experience. That's most important. I think what we're seeing is repeat customers come back. Actually, that's the biggest from if I look up from the start of twenty eighteen to the end, it was the repeat visits, so you get you know, the one million pound or dollar deal customer coming back twice or three times in the year to do the same thing again, >> but have any being put off by this new >> approach, but I haven't seen that so genuine. It hasn't appeared so far, so there's some education. Of course, that has to happen because it's different. It's not the norm. If you think about enterprise customers, they've been buying up a particular mode for twenty or thirty years or longer, a CZ we joke about. So this is just an education process that let them know what on how on then, what's there on the bandwagon? It kind of becomes that streamline process. >> Yeah, ad I'd build on top again. Sport like you kind of think about the way way >> customers thought about procuring infrastructure before eight of us existed, like back in way. But in the way big back of two thousand five, like buying hardware in storage and networking gear was crazy, hard and very difficult and long and laborious. And your racket and stacking everything else. And then a dubious comes along with services like Three and Easy to know what it makes provisioning access, the hard work. It's seconds, you know, not months of procurement, and in a way, we're kind of software is now catching up, and in a way, what marketplace is trying to do is to revolutionize the way people acquire software for the cloud in the same way that eight of us to infrastructure well, and you're creating a to be a consumer dynamic, not unlike my Amazon retail, where there's trust, simplicity, comfort levels on DH. You know, you even don't tell Jeff. I'Ll pay a little bit more from, you know, Amazon website cause I trust it. Yeah, you know, not too much, right? And you guys have to stay price competitive. Absolutely so. But that to me, is that it's that consumer like experience that you're obviously it is more complex but somewhat creating that way looked, we look to retail for all sorts of cool inspiration. You know, on the retail side, they have a retail marketplace, which is huge and thriving business with millions of merchants. And so we're constantly comparing notes and saying, like one of the things that you're doing for your merchants and are the things that can inspire us on our side kind of follow suit. I will note that you know, I when I get in front of customers I like to do, I'd like to show our user experience we have a pretty website and all that other good stuff. The vast majority of customers actually interfaced with us through command line and automation tools and all that other stuff. So retail analogy gets me so developers, >> thank >> you very much for it's really great to have you here, Director A ws marketplace and here mobile. As you say, >> we're in the midst of this transformation. It's really great to hear your story. So thank you very much for two years here >> on the Cube, on the aid everywhere summits in London That's all from us for now.

(funky upbeat music) >> Live from Barcelona, Spain. It's theCUBE covering Cisco Live! Europe. Brought to you by Cisco and its ecosystem partners. >> Welcome back to Barcelona everybody we're wrapping up day one of Cisco Live! Barcelona CUBE coverage. I'm Dave Vellante, he's Stu Miniman. You're watching theCUBE, the leader in live tech coverage. Donnie Williams is the IT Director at Scott Equipment out of Louisiana and Eric Herzog is back. He's the CMO of IBM Storage. Gentlemen, good to see you, welcome. >> Thank you. >> Thank you for having us. >> You're very welcome. So tell us about Scott Equipment. What do you guys do? What's the company all about? >> We're a heavy equipment dealer, so we've been in the business for 80 years, privately owned company. And so we started out in farm implement 80 years ago by the founder Tom Scott which is where the name Scott Equipment comes from. And so we transitioned over the years to construction equipment and we're now, so back in 2014 we sold all of our, the farm stores that handle all of that equipment, and now we're strictly servicing the construction industry and petrochemical industry. >> So you're a dealer of large equipment. And you service it as well, or? >> Yes we service it. We're primarily a rental company first. Then we also sell what we rent. We service it and it also parts as well. >> So we're talking massive? >> Yes big. If you think, one of our main clients is Volvo which if you've seen the show Gold Rush, that Volvo equipment that you see there, that's what we sell. >> It's incredible machines. >> Yeah, yeah they are I had a chance to play with one. I went to a Shippensburg Pennsylvania where their North America office is and had a chance to play with their largest excavator. That was fun. >> So is a lot of you IT centered on sort of the maintenance business and the service business or? >> Yes. Mostly Mirror is like a car dealership. So like I said, we do sale service, parts, all of that. >> So the business flow starts after the sale is made, obviously. >> Exactly, yes, we sell, yeah, exactly. We get the equipment out there in the territory and then the revenue continues to come in. >> So what are some of the challenges, the external challenges that are driving your business? >> So really, our, the whole heavy equipment industry is, is kind of behind the times in my, from a dealership perspective. From a manufacturer perspective. They're somewhat up with technology, especially Volvo, but from a dealership, they're mainly privately owned, so they're not, there's not a whole lot of resources in technology. That's not a focus for them. They're focused on the business side of it, so. When I first started at the company 10, 11 years ago now, there was one guy servicing 600 employees. And it was-- >> One IT person? >> One IT person. So, as you can imagine, it was a nightmare. I mean it's not the guy's fault. I don't blame him at all. It's just the way that they had done business and not changed. >> He was a bummed out IT person. >> Yeah, right exactly, yeah. >> Now how'd you guys find them? >> So they're a customer of ours for the verses stack. We have a partner that they've been buying their IBM and their Cisco gear from, and then when they were doing a modernization effort, the reseller talked to Scott and said, Donnie, what d'ya think? How about doing this converge infrastructure. Easier to employ at sep-tor. So it all came through their existing channel partner that they were using for both IBM gear and Cisco gear. >> So you wanted a solution that one guy could run, right? >> We've now at least grown that, our company to, now we have six total in our department. So we've changed a lot since I started 11 years ago. >> And what are they spending their time doing? >> Primarily, we do a lot of help desk, assistant administration, we do mostly, my focus is to make sure that our employees are satisfied so they can take care of the customer. And that's the primary goal and along with that comes systems administration, as well, so. >> But you know, a full stack like this. I mean the joke. You need more than one person. >> Right. But it's going to be simplified, you know what you're buying, >> Right, exactly. >> It's predictable, and therefore, you shouldn't need to be seen on a day to day basis. >> Yes, I like keeping things simple, simple as possible. So, that makes my job easier, it makes my team's job easier, as well. >> So what kind of things are you driving? Is it, ya know, data protection? Is it, what sort of, you know, use cases do you have on your stack? >> We're from our, we're servicing on our, with Cisco, I'm sorry, verses stack. It's mostly it's all private cloud. We're servicing applications that supplement our core ERP system. So, we have reporting solutions. When we first bought the verses stack, we were considering moving to another ERP system, and we would have that infrastructure in place to migrate to that. So we still have that, actually, element table as an option for us. >> The migration to a new ERP system? >> Yes. >> We should talk afterwords. >> We're avoiding that all costs. >> Right, well, of course. You don't want to convert if you don't have to. Yeah but sometimes it's a business case. Sometimes it's hard to make. We'll talk. >> Exactly. >> Cloud in your future or present? >> We're doing some-- >> SAS stuff, or? >> Yeah a little of that. I mean anything. I mean things that make sense for us to do cloud. Security services. We're doing, of course, probably the most common is hosting email. We're doing a lot of that. Share point. That type of solution in the cloud. >> How long you've been with the company? >> 11 years. >> 11 years, okay, so, thinking about the last decade, I mean a lot has changed. >> Yes. >> What are you most proud of? What's like your biggest success that you can share with us? >> Really building the IT department and bringing our company into the 21st century from a technology perspective. I mean, like I said, we had one person that was handling it. It was really impossible. I mean, you couldn't depend on one person and expect the company to survive long term. >> Yeah, that one person had to say no a lot. >> Exactly, right. He just couldn't get everything done. >> So, really that modernization and that's kind of where you guys came in, right? >> IT modernization play. The verses stack is heavily used for that and, you know, as we've said on the earlier interview, we had a CSPN. We've also used it to go to the next level from an IT transformation to the future. 'Cause in that case, as you know, that was a CSP who uses it to service, you know, hundreds of customers all across the UK in a service model. And in this case, this is more of a IT modernization, take the old stuff, upgrade it to what it was. They even had an old IBM blade servers. That's old this stuff was. Old XE6 Blade servers that must've been 10 years old before they went to the verses stack. >> How many people in the company? Roughly? >> Right now, we've actually sold off side since I've been with the company, we've sold off some of our nonperforming business units. We're probably roughly around 550 now. >> Okay. >> So I mean, we're actually more profitable now than we were 11 years ago. We have less employees, but our profitability is actually exceeded. >> Theme of simplification. >> Exactly, right. >> So what's the biggest challenge you face as the head of IT, today? >> The biggest, probably the biggest challenge would be me wanting to implement technologies that are not ready. I want to have the competitive edge of the industry. I want to be able to be ahead of the curve. And that's probably the biggest challenge. >> And you're saying you can't because the tech isn't ready? Or it's a skills issue? >> It's just the industry. Just trying to work with vendors and getting them to be ready for, I say vendors, manufacturers. They're our vendors. To get them to, and know their dealers as well. To all be acceptable to the technology's that's been there 20 years. >> What would you say is the top, number one, or the top things IBM has done to make your life easier? And what's the one thing they could to do that they're not doing that could make your life easier? What's the, start with what they've done. You know what the success is that have helped. >> Really, we've been a longtime IBM customer. We have not just the verses stack, but we also have the power system, which actually runs our core ERP. >> Ah, okay, so. >> So I mean, we've had long standing relationship with IBM. Reliability is there. The trust is there, as well. >> Yeah, long term partnership. Alright, what's the one thing they could do? If you could wave a wand and you said, IBM will to X, what would x be to make your life better? >> Cut the price. >> Ah, here we go! (all laughing) I should've prefaced that soon! Besides cut the price. Alright we'll leave it there on that topic. But you know, the power system thing brings up, you know, our friend Bob Piccano's running the cognitive systems group now. You guys doing some stuff with AI. Maybe talk about that a little bit. >> So what we've done is two things. First of all, we've imbued inside of our systems AI all over the place. So for example, we tier data which can do not only to own array, but literally to 440 arrays that have someone else's logo on them. It's all AI done. So when the data's hot, it's on the fastest tier. So if you have 15,000 RPM drives and 7,200 RPM drives, it goes to 15,000 when it cools off. AI automatically moves it. The storage admin does nothing. You don't set palsies AI takes care of it. We have Flash, and you have hard drives. Same thing. It'll move around. And you could have an IBM array talking to an EMC array. So all sorts of technology that we've implemented that's AI in the box. Then on top of that, what we've done is come up with a series of AI reference architectures for storage as one of the critical elements of the platform. So what we've done is create what we call a data pipeline. It involves not only our storage arrays, but four pieces or our software, spectrum scale, which is giant scale off file system, in fact, the two fastest supercomputers in the world have almost half an exabyte of that software, storage with that software. Our spectrum discover, which we announced in CUBE 4, which is all about better management of metadata. So, for AI workloads, big data analytic workloads, the data scientist doesn't prep the data. They can actually talk to what we do, and you can create all these metadata templates, and then boom, they run an AI workload on Thursday, and then run an analytic workload on Friday, but all automated. Our archive, and then our cloud object storage. So, all that is really, think about it more as an oval, because when you're doing an AI system, you're constantly learning. So the thing you got to do is, one, you've got to have high performance and be able to handle the analytics which you we do on Flash. 'Kay, so the Flash is connected. You've got to be able to move the data around and part of the thing with the Spectrum Discover is that we can talk through an API, to a piece of AI software, to piece of analytic software, to a piece of big data software. And they can literally go through that API, create templates for the metadata, and then automatically suck what they need into their app and then munge it and then spew it back out. And then obviously on the archive side, want to be able quickly recall the data because if you think about an AI system, it's like a human. So let's give you my Russian example. So I'm old enough, when I was a kid, there were bomb shelters in my neighborhood that people dug in the backyard. Then we have, you know, Nixon lighting up the Chinese. Then we have Reagan and Gorbachev. Next thing you know, the wall comes down, right? Then the next thing you know, there's no longer a Soviet Union. All of a sudden, ah, the Russians might be getting a little aggressive even though they're no longer communist, and now you see, depending on which political party, that they're totally against us, or they're totally helping us, but, you know, if they really were hacking systems, whatever political party you're in, they really were hacking our systems trying to manipulate the election. Pro or con, the point is that's kind of like a cyber attack. And that's not a good thing. So we learn and it changes. So an AI system needs to understand and change, constantly learn, if all of a sudden you have flying cars, that's going to be different than a car with tires. Now a lot of it may be the same. The interior, all the amenities, but the engines going to be different, and there are companies, including the big three, four, five, auto, who are actually working on flying cars. Who knows if it'll happen, but the AI system needs to understand and learn that and constantly learn. And so, the foundation has to heavily resilient, heavily performant, heavily available, last thing you want is an AI system going down on you. Especially if you're in healthcare, or big giant manufacturing, like Volvo, his customer. When they're building those cranes and things, they must cost 50, 60 million dollars. If that assembly line goes down, it's probably a big deal for them. So you need AI systems that always keep your other systems up and running. So you have to have that solid foundation of storage underneath. >> Awesome, alright, we got to leave it there. Give the customer the last word. Donnie, first time in Barcelona, right? >> Yes it is. >> How are you finding the show and the city? >> Oh it's awesome. This is my fifth Cisco Live. First time in Europe, so yeah. Enjoying it. >> Good, good. Well thank you guys for coming to theCUBE. >> Great thank you for coming. >> Thank you! >> Really appreciate it. >> You're welcome. Alright keep it right there everybody. We'll be back to wrap day one Cisco Live! Barcelona. You're watching theCUBE. (techno music)

>> Live from Barcelona, Spain. It's the cue covering Sisqo Live Europe, brought to you by Cisco and its ecosystem partners. Welcome back >> to Barcelona. Everybody would adapt. Wrapping up day one of Sisqo live Barcelona Cube coverage. I'm David. Long day. He's stupid men. You're watching the Cube. The leader in live tech coverage. Donnie Williams is it director at Scott Equipment out of Louisiana. And Eric hurts August back. He's the CMO of IBM storage. Gentlemen, good to see you. Welcome. >> Thank you for having us. >> You're very welcome. So tell us about Scott equipment. What do you guys do? Look, what's the company all about were >> a heavy equipment dealer, So we've been we've been in the business for eighty years, privately owned company. And so we're we're We started out and farm implement eighty years ago by the founder, Thomas Scott, which is where the name Scott equipment comes from. And so we transition over the years, Teo construction equipment, Andi were now back in two thousand fourteen, we sold all of our the farm stores that handled all of that equipment. And now we're We're strictly servicing the construction industry and petrochemical in >> history. So your dealer of exactly what equipment and your services as well? >> Yes. We service that we were primarily a rental company. First then then we We also sell what we rent. We service service it and and also parts as well. So we're talking massive? Yes, they got. If you if you think our one of our main lines is Volvo, which you have you have you seen the show? Gold rush that that Volvo equipment you see there, that's that's what we sell. So is incredible machine. Yeah, Yeah, they are. Hada chance tio to play with one. I went Teo Shippensburg, Pennsylvania. Where were their North America offices and had a chance to play with their largest excavator? That was That was >> fun. So is a lot of your Senate on sort of the maintenance business in the service business? >> Yes. So we were just mostly. Mirror is like a car dealership. If if you so we were like I said, we do sale service parts, all of that. >> So the business flow starts after the sale is made on >> exactly. Yes. We still like, Yeah, exactly. We get. We get equipment out there in the in the in the territory, and then the revenue continues tio to come in. >> So what are some of the challenges? The external challenges that are driving your business? You really >> are. The whole heavy equipment industry is It's kind of behind the times in my from a dealership perspective from from a manufacturer perspective there. They're somewhat up with technology, especially especially Volvo. But from a dealership there, there might mainly privately owned. So they're not there's not a whole lot of resource is in, and ah, in technology they don't. That's not a focus for them that they're they're focused on the business side of it. So what? We we're not When I first started the company ten, eleven years ago, now there was one guy servicing six hundred employees and and it was one eyed person, one i t person. So, as you can imagine, it was, it was a nightmare. Go. I mean, it's not the guy's fault. I don't blame him at all. Is this Is this the way that they had done business and not change bombed out, >> right? Exactly. Yeah. Guys >> find them. >> So their customer of ours for the versus stack, we have, ah, partner that they've been buying their IBM in their Cisco gear from. And then when they were doing a modernization effort, the reseller talk to Scott and said, Dani, what do you think? How about doing this? Converge infrastructure. Easier to play. It's after. So it all came through their existing channel. Part of that they were using for both IBM gear and Cisco Gear. >> So you wanted a solution. That one guy could run, right? We've now at least growing that company to house. We have six total in our in our department. So we've changed a lot since I started the eleven years ago. >> And why are they spending their time doing what? Premier >> Li? We do a lot of help desk on systems administration way do mostly, uh, are My focus is to make sure that our employees are satisfied that so they could take care of the customer, and that's that's the primary goal. And along with that comes comes systems administration. A cz. Well, so, But, >> you know, a full stack like this. I mean, the joke. You need more than one person, but it's going to be simplified. You know what you're buying, right? Predictable. And therefore, you shouldn't need to be seen on a basis. >> Yes, I like keeping things simple. Simple as possible. So that makes that makes my job easier. It makes my team's job easier. What >> kind of >> things you driving? Is it? You know, data protection, is it? You know what? What? What? What sort of, you know, use cases do you have on your stack >> on that Were from our were servicing on our with Francisco verse. Sorry versus stack. We are mostly it is all profit cloud were servicing applications. That's the supplement. Our court system. So we have reporting solutions. We were when we first bought it. The vs stack way were considering moving to another Air P system. Oh, and we would have that that infrastructure in place tio migrate to that. So we see what we still have that that actually on the table as a as an option >> for us, but the migration to a new Europe E system. Yes, we should talk afterwards. No, you >> were warning that it >> all about you. Of course, you don't want to convert if you don't have to write. But sometimes there's a business case. Sometimes it's hard to make you talk. Cloud in your in your future president were doing some that's ass stuff. >> Yeah, a little of that. I mean, anything. I mean things that that makes sense for us to to cloud I security services we're doing. Of course, probably most common is hosting email. Were doing a lot of that share point that that type of solution in the cloud >> How long you been with the company? Eleven years. Eleven years. Okay, So, thinking about the last decade, I mean, it's a lot of lot has changed. Yes. What's your What do you most proud of? What you like your biggest success that you can share with us. Oh, >> really? Building my the that dude the I T department and bringing our company into the twenty first system century from a from a technology perspective. I mean, like I said, we had one person that was that was handing. It was really impossible. I mean, you couldn't depend. Depends on one person. And and and, yeah, expect the company's or saw survive long term. Yeah, That one person had to say no a lot. Exactly. Right. Why would he? Just couldn't get everything >> done right? So that really that modernization? Yes, I know where you guys >> can. Ninety Mater, My team modernization play. The versus stack is heavily used for that. And, you know, as we said, on the earlier and every we had to see ESPN, we've also used it to do you know, to the next level from a night transformation to the future. Because in that case, as you know that was a CSP who uses it to service. You know, hundreds of customers all across the UK in a service model. And in this case, this is more of a mighty modernization. Take the old stuff, upgraded to what it was. They even have old IBM blade servers. That's how old the stuff wass old, actually, six played servers that must have been ten years old before they went to the Versus Stack. >> How many people in the company >> right now? We've actually sold off side since I've been with the company we sold off. Some of our non performing business units were probably roughly around five hundred fifty now. Okay, so I mean, we're Ah, we're actually more profitable now than we were eleven years ago from Ah, I mean, we have less employees, but our profitability is actually exceeded >> the name of simplification. Exactly. Right. So what's the biggest challenge you face Is the head of it today? The biggest, Probably >> the biggest challenge would be me wanting to implement technologies. They're not really not ready. I want it. I want tohave the competitive edge, that of the industry. I want to be able to be ahead of of the ahead of the curve. Uh, and that's probably the probably biggest challenge. And you're >> saying you can't Because the tech is ready or skills >> is just is just the industry just trying Teo. I work with vendors and getting getting them to be ready for I say, vendors, manufacturers, they're our vendors. Toe Get them Tio and other dealers as well. Teo Teo Albee. Acceptable to technology that's been there twenty years. >> What would you say is the but the top number one or the top things that IBM has done to make your life easier? And what's the one thing they could do that they're they're not doing that could make your life easier. What's the start with what they've done? You know whether successes, you know that >> really? Really. I mean, we've been a long time IBM customer. We have not, not just the versus Stack, but we also have the power system, which were actually runs are our core AARP. Um, okay. And so that we had long standing relationship with IBM, and the reliability is there. The trust is, >> there's well, a long term partnership. But what's the one thing they could do? One thing that you could If you could wave a wand and IBM will do x what would x B to make your life better? Uh, cut the price way. Go >> way. I should have prefaced that something that size >> on that topic. But you know, the power system thing brings up. You know, our friend Bob. Pity on who's running the cognitive systems group now You guys do with some stuff in a I talked about that a little bit. >> So what we've done is two things. First of all, we've been beauty inside of our system's ai ai all over the place. So, for example, we tear data which can weaken due not only to our own array, but literally two four hundred forty rays that have someone else's logo on them. It's all a eye dunce. When the data is hot, it's on the fastest here. So if you have fifteen thousand rpm drives in seventeen hundred rpm drives, it goes to fifteen thousand. When it cools off A. I automatically moves that the storage admin does nothing. You don't set policies, A takes care. We have flash and you have hard drive's same thing. It'll move around and you could have on IBM array talking to any AMC array. So all sorts of technology that we implement, that's a I in the box. Then, on top of that, what we've done is come up with a Siri's of a reference architectures for storage, as one of the critical elements in the platform. So we've done is create what we call a data pipeline. It involves not only our storage raise, but four pieces of our software spectrum scale, which is giant scale out file system, in fact, to fastest super computers in the world have almost half an exabyte of that software storage. With that software, our spectrum discover which we announced in queue for which is all about better management of metadata. So for a I workloads, big get anally work loves the data scientist doesn't prep the data. They can actually talk to what we do, and you could create all these meditate a template, then boom. They run a a ay workload on Thursday and then run a analytic workload on Friday. But all automated our archive and then our cloud objects towards. So all that is really think about it. Maura's an oval because when you're doing an A I system, you're constantly learning. So the thing you got to do is one you've got to have high performance and be ableto handle the analytics, which we do on flash. Okay, so the flashes connected, you've got to be able to move the date around. And part of thing with the spectrum Discover is that we can talk through an A P I to a piece of a AI software two piece of analytic software to piece of big data software, and they can literally go through that. AP I create templates for the metadata and then automatically suck what they need into their app and then munge it and then spirit back out and then obviously on the archives side, you want to be able to quickly recall the data, because if you think about a I system, it's like a human. So it's giving my Russian example. So I'm old enough. When I was a kid, there were bomb shelters in my neighborhood that people dug in the backyard. Then we have, you know, Nixon lightening up with the Chinese and we have Reagan and Gorbachev next, You know, the wall comes down right then. Next thing you know, there's no longer Soviet Union. All of a sudden, no, the Russians might get a little aggressive, even though they're no longer communist. And now, you see, depending on which political party. Either they're totally against us where they're totally helping us. But, you know, if they really were hacking systems whose whatever political party urine, they really were hacking our system, tried to manipulate the election pro or con. The point is, that's kind of like a cyber attack, and that's not a good thing. So we learn and it changes. So when a I system needs to understand and change constantly, learn. If all of a sudden you have flying cars, that's going to be different than a car with tires. Now, a lot of it, maybe the same, the interior, all the amenities. But the engine is going to be different. And there are companies, including the big Big three, four five who are actually working on flying cars, knows it will happen. But the A I system needs to understand and learn that and constantly learning. So the foundation has to be heavily resilient, heavily performance, heavily available, lasting one is an A I system going down on you, especially if you're in health care or big giant manufacturing. Like Volvo, his customer. When they're building those cranes and things, they must cost fifty sixty million dollars at that assembly line goes down its prey a big deal for them. So you need a I systems that always keep your other systems up and running. So you have to have that solid foundation storage underneath. >> Awesome. All right, we got to leave it there. Give the customer the last word. Donnie. First time in Barcelona, right? Yes. It ISS how you find in the show and the >> syphilis is awesome. This's my, actually my fifth, uh, Cisco lifers our first time in Europe, so yeah, enjoying it. >> Good. Good. Well, thank you, guys. For German of the >> correct. Thank you. Have you appreciate it? >> You're welcome. Alright. Keep right there, everybody. We'll be back to rap Day one. Sisqo live Barcelona watching you.

>> Live from San Francisco, it's theCUBE, covering DockerCon 18. Brought to you by Docker and it's ecosystem partners. >> Welcome back to theCUBE's coverage of DockerCon 2018 in beautiful San Francisco. It's a stunning day here. We're at Moscone West, I'm Lisa Martin with John Troyer. Very honored to welcome to theCUBE, for the first time, the CEO of Docker Inc., Steve Singh. Welcome, Steve. >> Hi Lisa, very nice to meet you. John, how are you? >> So the general session this morning, standing room only between five and six thousand people. I gotta say a couple things that jumped out at me. One, coolest stage entrance I've ever seen with this great, if you haven't seen it from the livestream, this, like, 3D Golden Gate Bridge and I loved that and I loved the demo of Docker Desktop that your kids did, fueled by Mountain Dew, which actually single handedly got me through college here in San Francisco. So, the momentum that you guys, it was kicking off with a bang. >> Yeah, I, look, I've got a great team and one of the things we wanted to communicate this morning is that you're seeing a massive transformation in the world of software. And this transformation is enabling every company in the world to think about their business in a new light. To think about how their business meets customer needs in a way that's much more personal, in a way that delivers more value. And this is the beauty of where Docker is, right, we have a chance to help literally every company in the world. And that's the part, honestly, that gets me excited, is, like, how do you help other people go create amazing businesses? And so this is, I couldn't be more happy to be at Docker. >> Steve, keying on that, one of the customers on stage today, McKesson. >> Yeah. >> And I loved Rashmi Kumar came out and talked about future-proofing for applications, their infrastructure, their applications in partnership with Docker. >> Yeah. And that implies a certain amount of trust that they have in Docker and Docker's technology platform and in partnering with you. You come from a, so you've been at Docker for about a year now, right? Came in as CEO. Docker is still a small company, a couple hundred folks but punching way above its weight with a huge community impact. How do you, and, you know, you've worked with the biggest companies in the world, how do you come in and establish that trust and help reassure them that you're gonna be a good partner for them and, kinda, what are you seeing with your customers? >> It's a great question, John, and look, there's maybe two or three pieces of how we think about that. The first thing, trust is very human, right? You've gotta know that you're walking into a situation as a vendor and as a customer but really as partners. And you're trying to solve a problem together. Because the reality is, this transformation that companies are going through is the first time in 40 years that this kind of transformation has happened. Second is, the technology stack is still in the early stages. Now, it's incredible and it enables amazing things, but it's still in the early stages. So both of us have to walk into the relationship knowing that, you know what, sometimes it won't go perfect, but guess what? We're gonna be, you know, if it doesn't go perfect we're gonna honor everything we ever committed to you and the same thing on the customer's side. They look at it and say, "I may have actually described my needs differently than what they actually are." And that's what a real partnership is. That's number one. Number two is, trust is driven by culture. And one of the things that I love about Docker is that we see our place in the world but we wanna make sure the customer always has choice. We wanna make sure that if we do a great job the customer will choose to work with us. If we don't, they should have the choice to go somewhere else. And that's what our platform enables, is the choice to be able to work with anybody you'd like to work with, whether you're the developer or you're an operator or you're an IT, I'm sorry, an architect, or the executive. The other piece around this is that part of the value of Docker is it's not just the 400 people of our company, right? There's 5,000 members of our community that are adding value to our community. One of the things that I wanna make sure we do for our community is help them not just innovate on this incredible platform but how do we help them take their innovations to market? And so that's part of the ethos of our company. >> One of the things that you talked about this morning that I thought was really compelling was, you said software innovation used to be, for the last 40 years, it's been driven by tech companies. That's changing. You talked about distributed innovation and distributed consumption. How is Docker helping to, culturally, I don't wanna say instill, but helping to influence, maybe, organizations to be able to distribute innovation and be able to share bi-directionally? >> Yeah, so, a great question, Lisa. So, first of all, is there's a cultural change within companies. When you think about the next generation or the next 40 years being, software being driven from non-technology companies. First of all, we're seeing that. Second is that it requires a cultural change within the business but that change is critical 'cause in the absence of becoming more of a software company your business is gonna be under threat, right? From the competing business. Look at what Netflix has done in media compared to every other media company. That same example applies in every single industry. Now, the way that we help enable that software transformation is to provide a platform that is so easy to use that it doesn't require a lot of training. Now this is complicated platforms, so, yes you have to be a fantastic developer or an IT professional but our job is to take complicated technology like container management software, orchestration layers like Swarm or Kubernetes, service mesh, storage networking, all of those, and make it so simple and easy to use that your IT department can say, "I can use this platform to effectively future-proof your company," right? So, how do you have a platform that you can build every application on, take all of you legacy applications on, run it, and then run it anywhere you like. >> I think that's been one of the through lines for Docker since the very beginning, that developer experience, right? >> Yes. >> And what's been interesting in Docker's development was, I think for both inside and outside, is kind of, what is Docker Inc, and the project versus the company, what is it selling, what's the commercial aspect here? I think, I kind of think back to my experience at BMWare, where there was an enterprise side and then a huge install base of workstation folks. And it's even stronger with Docker because actually now with Docker Desktop as an application development environment or a, you know, I don't wanna, not quite development environment but, you know, the one you announced today with Docker Desktop. That's an even more valuable through line into the Enterprise Edition. >> Yeah. >> But I don't, so, I guess where I'm heading, Steve, is, can you talk a little bit about the commercial situation? Docker EE as the flagship platform. >> Yeah, of course. >> And, kind of, where we are in the maturity journey with customers right now, it's real and important. >> Absolutely John, but you're bringing up a great point within this. Look, we're both, we're a enterprise software company and we're this incredible community where innovation is being brought in by every member of the community. And there's nothing in the world that says you can't do both. This idea that you're one company versus another, this is nonsense, alright? It's a very narrow view of the world. In fact, I would argue that, more and more, companies have to think about that they have multiple people that they serve. Multiple constituents that they serve. In our case we serve the Enterprise IT organization and we also serve developers. And developers are a critical part, not just of our community, that is the life of every company going forward. Which is why we're so excited about this. That's the life of every company. So, Docker Desktop, the reason we're so excited about it is, first of all, it is the easiest way to engage with Docker, to build applications. And then we feel like there's a lot more innovation that we can actually deliver within Docker Desktop. Alright, so a million new developers joined on Docker Desktop this year. In fact, we're growing about seven or eight percent month over month on that. And so you should expect over the next year another million will be on Docker Desktop. But it's incumbent upon us to say, the only way that we continue to earn the trust of that portion of our constituents, that of the developer community, is to make sure we're innovative, to make sure we're open to allow others to innovate on top of us. >> I'd love to, kind of, explore on audience a little bit. So, in terms of innovation, you know, we know that the companies that have the ability to aggressively innovate, and to do that they have to have the budget, are the ones that stay relevant and that are the most competitive. But I think I saw some stats and I think Scott Johnson said that close to 90 percent of IT budgets are spent keeping the lights on. So you have very little dollars to actually drive innovation. So when you're talking with customers, and you said you just met with 25 of Docker Inc's biggest customers just this morning, are you talking to both the developer guys and girls as well as the C suite? >> Yeah. >> What is, how are you connecting and then, maybe, is it a conversation to enable the developers to be able to sell the value up the stack or is it vice versa? >> A couple of things here, so, first of all, John, I didn't answer part of your question which is the growth in our Enterprise customer base. We've literally doubled it year over year, right? So, more than 500 Global 10,000 companies that are using Docker to run their applications and to manage their applications. The way that we engage with our customers is literally across the entire constituents of that organization, right? A developer by themselves, as genius as that group of people are, you can't deliver the application. And delivering the application is just as important as building it. And so the IT organization, the ops organization is critical. And then there's gotta be an overriding objective. What is it we're trying to do? How do we transform ourselves into a software company? You think about, think about just for example, Tesla, right? When you have a company, and I realize Tesla's stock goes up and down, they're always in the news, but when you have a company that's worth more than some of the biggest automotive companies in the world, you have to ask yourself why. Well, part of the reason why isn't just the fact that we've got an electric vehicle that's better for the environment. Part of it is, it's really as much a software company as it is a automotive company. They have incredible amounts of data about how we use our cars, where we go, and in fact the Tesla cars are actually interconnected. And so, that brings a perspective in how you build cars and how they're gonna be used and how they're gonna be consumed that's radically different than if you're just an auto manufacturer. Now, look, Ford and GM and Volvo are all really smart, great companies and they're quickly moving through to themselves being software companies. >> Steve, can you talk a little bit about ecosystems? Microsoft, on stage this morning, a long partnership with them but also here at the show, right, enterprise folks, Dell and Accenture and I'm just looking down the list as well as Google and Amazon, right? So, you need to be partnering with a lot of folks to make all this work. How are you approaching that? >> John, part of the reason for that is, let's start with a simple premise, is something this large, alright, you can't possibly innovate fast enough on your own, alright? There's seven billion amazing people on this planet. The only way you can really drive mass scale global innovation, is you have to be open, right? I'm literally a guy that was born in a mud house in India, so I certainly appreciate the opportunity to participate in the rest of the world's economy. So we have to be open to say, anybody that wants to contribute, can. Now, obviously we think that contribution has to be within an ethos, right? If your definition of contribution is how do you help your own business, that's not good enough. You have to look at this and say, there has to be choice, in our view, choice, security and agility. So, how do we deliver those values or that ethos to our customers? And if you're willing to do that, man we want to partner with everybody in this space. >> Yeah, I, sometimes I despair of the tech press, although I consume a lot of it and if I never have to read another Swarm versus Kubernetes article again I would be happy. But Kubernetes' all over the keynote and it seems like Docker you all have embraced it and in fact are supporting it in very innovative ways with the cloud providers. In terms of ecosystem can you talk a little bit about-- >> Yeah, well, part of the value of Docker is we simplify very complex things and make it available to our customers to consume with little training, little understanding of the underlying deep technology. And the other part is that it comes back to this idea that innovation will happen everywhere. Why should we view the world as it's our solution or, you know, nobody's? That's nonsense, right? Kubernetes is a fantastic orchestrational entity. Why shouldn't it be integrated into the Docker container platform? And so, as we did that, guess what happened? Our customers, all they saw was, instead of conflict they saw the opportunity to work together. In fact it's been amazing for the growth in our business, that's why ewe doubled year over year. >> Now, collaboration is essential and we were talking with Scott Johnson a little bit earlier today about the internal collaboration but also the external collaboration with customers. You talked about partnerships, I think that the MTA program, the Modernization of Traditional Apps launched about a year ago with Avanade, Cisco, HPE and Microsoft. Tell us a little bit about that, probably around the same time that you came to the helm. You're seeing, you know, customers like Visa, PayPal as part of this program, be able to transform and go to the container journey. >> Yeah, and Lisa, this speaks to an observation you made a few minutes ago about the fact that, you know, 85, 90% of IT budgets are fixed before you even walk into the year. So, look, the Docker platform can be used for any kind of application. Legacy apps, next generation apps that run in the data center, next generation apps that run on Edge devices. But if you accept that 90% of the apps that sit within a company are all legacy apps, well, guess what, that's where their cost is. And then if you marry that to the fact that every CIO has this problem that I don't have a lot of money that's free in my budget. Well, how do we help solve that? And the way we chose to solve it is this Docker MTA solution. Modernizing Traditional Apps. Take your traditional apps, run 'em on the Docker platform, run 'em on any infrastructure you like, cut your app and infrastructure management costs in half. Now, then take that savings and then apply it towards innovation. This is why it resonates with CIO's. I mean, as much as they may love Docker and they may love us, they have a business to serve and they're very, very practical in how they think about, you know, going about their business. >> So with that approach, thanks John, how receptive were those enterprise CIO's to going, "You're right, we've gotta start with our enterprise apps." They don't have the luxury of time, of ripping out old infrastructure and building them on containers or microservices architectures. And these are often mission-critical applications. Was that an easy sell, was that, tell me about that. >> (laughs) Well, nothing's easy but the reality is, is that it, they got it quickly, right? Because it speaks directly to their paying point. And what I'm very proud of with my team is not only were we able to deliver a great product for MTA but we're also helping our customers actually make sure they can migrate these apps over. But what's been really a positive, you know, kind of a signal we've seen, that's still the early stages, is that as our customers are moving their legacy apps to Docker and running 'em on new infrastructure, sometimes public cloud, and cutting costs, they're starting to take that cost savings and actually applying it to their next generation apps. So they're not using Docker for new apps. And so that is, that's the benefit of when you really try to solve the problem the way the customer wants to consume it. >> So, Steve, the user conference, very energizing, right. >> Yeah. >> Already the energy's been good here, you've been doing trainings and certifications, there's people behind us, everyone's talking, so that kind of in some ways sets the tone for the year, so as you and your team go back to the office after this week, you know, what are you looking to do and what can we expect out of Docker? >> I'll just speak to two things. First of all, there's so much innovation we still have to deliver. If anything, you know, I would say my team will tell me I might be pushing a little hard. But you know what, this is the fun, you only have x number of years in life and you should make the most of it. So we're really excited about new apps, we're excited about SecurEdge apps. We're excited about, I don't know if you saw the demo this morning, of Armada, which allows you to run any app on any operating system, on any infrastructure, all from a single pane of glass. Our customers love that and they're very excited about that. That said, you know, this is a, it's a big test. We have a huge opportunity to welcome a lot of other companies, so when you walk around and see 5,000 people that see amazing opportunity, not just for Docker, for themselves, right? That's the secret part of Docker that I love. We're creating jobs that didn't exist before, right? I mean, you see kids coming out of college now getting Docker skills and they're using that to grow their IT profession. In fact, I was just at i.c.stars, this is an amazing organization in Chicago that helps individuals who've been displaced in the workforce learn the IT skills required to come back to the workforce and really help run internal IT organizations. Guess what they're learning? They're learning Docker. So that's, these are the kind of things that get us excited. >> And that's essential for enterprise organizations who, that's one of the challenges they face, was, you know, modernizing the data center, which they have to do, but then it requires new skill sets, maybe upskilling, so it's exciting to hear that you're seeing this investment in people that have an opportunity, the proclivity to actually learn this technology. >> Yeah, this is, we are happy because we help customers but we also create amazing new jobs that, you know, are, certainly our community can still benefit from. >> So, last question, the three themes that came out of your session and really the general session this morning was, you talked about someone's choice, agility and security. Are those the three pillars that you believe Docker, upon which Docker sits as really competitive differentiators? >> Amen, amen, number one, but it's also our values, right? This is rooted in our values and when a company performs best is when their values show up in their products. Because then you're never lost, you'll always know what you're focused on. And you know, when I ran Concur, we had this vision, north star, called The Perfect Trip. And our objective was to always go create a delightful business trip experience. And for Docker I wanna make sure that we have a north star. And our north star is our values and they have to translate directly to what actually helps the customer. >> Love that, the north star. Well, hopefully theCUBE is the north star of modern tech media. Steve, thanks so much for stopping by. >> Thank you, it's wonderful to meet you. It was great to meet you as well and congratulations on the big success. >> Thank you. >> We look forward to hearing-- >> Thank you Lisa, thank you John. >> What's coming out in the next year. >> Thank you. >> And we wanna thank you for watching theCUBE, I'm Lisa Martin with John Troyer today live from San Francisco DockerCon 2018. Stick around, we'll be back after a short break. (upbeat music)

[Music] from San Francisco it's the covering Red Hat summit 2018 brought to you by Red Hat everyone welcome back is the cubes live coverage here in San Francisco Red Hat summit 2018 I'm Sean furry co-host of the cube with my coasts analyst this week John Troyer who's the co-founder of tech reckoning advisory and Community Development firm our next guess is red hash Balakrishnan is the general manager of OpenStack for Red Hat welcome to the cube good to see you ready to be here so OpenStack is very hot obviously with the with the with the trends we've been covering from day one been phenomenal to watch that grow and change but with kubernetes you seeing cloud native to robust communities you got application developers and you got under the hood infrastructure so congratulations and you know what's what's the impact of that what is how is OpenStack impacted by the cloud native trend and what is Red Hat doing they're the best epidermis ation of that is openshift on OpenStack if you had caught the keynotes earlier today there was a demo that we did whereby they were spawning open shifts on bare metal using OpenStack and then you run open shift on power that's what we kind of see as the normed implementation for customers looking to get - I want an open infrastructure on Prem which is OpenStack and then eventually want to get to a multi cloud application platform on top of it that makes up the hybrid cloud right so it's a essential ingredient to the hybrid cloud that customers that are trying to get to and open shifts role in this is what I'm assuming we are asked about openshift ownerships will be multi cloud from a application platform perspective right so OpenStack is all about the infrastructure so as long as you're worrying about info or deployment management lifecycle that's going to be openstax remet once you're thinking about applications themselves the packaging of it the delivery of it and the lifecycle of it then you're in openshift land so how do you bring both these things together in a way that is easier simpler and long-standing is the opportunity and the challenge in front of us so the good news is customers are already taking us there and there's a lot of production workflow is happening on OpenStack but I got to ask the question that someone might ask who hasn't been paying attention in a year or so it was thick hey OpenStack good remember that was what's new with OpenStack what would you say that person if they asked you that question about what's new with OpenStack the answer would be something along the lines of boring is the new normal right we have taken the excitement out of OpenStack you know the conversations are on containers so OpenStack has now become the open infrastructure that customers can bring in with confidence right so that's kind of the boring Linux story but you know what that's what we thrive on right our job as reddit is to make sure that we take away the complexities involved in open source innovation and make it easy for production deployment right so that's what we're doing with OpenStack too and I'm glad that in five years we've been able to get here I definitely I think along with boring gos clarity right last year the cube was that OpenStack summit will be there again in two weeks so with you and I enjoy seeing you again for it the last year there was a lot of you know containers versus there was some confusion like where people got sorted out in their head oh this is the infrastructure layer and then this is the a play I think now people have gotten it sorted out in their head open open shipped on OpenStack very clear message so a meaning of the community in two weeks in any comments on the growth of the open OpenStack community the end users that are there the the depth of experience it seemed like last year was great everywhere for OpenStack on the edge it ended you know set top devices and pull top devices all the way to OpenStack in in private data centers and and for various security or logistical reasons where is OpenStack today yeah I think that he phrased would be workload optimization so OpenStack has now evolved to become optimized for various workloads so NFV was a workload that people were talking about now people are in when customers are in production across the globe you know beat Verizon or the some of the largest telcos that we have in any and a pack as well the fact that you can actually transform the network using OpenStack has become real today now the conversation is going from core of the data center to the edge which is radio networks so the fact that you can have a unified fabric which can transcend from data center all the way to a radio and that can be OpenStack is a you know great testament to the fact that a community has rallied around OpenStack and you know delivering on features that customers are demanding pouring is the new normal of that is boring implies reliable no-drama clean you know working if you had to kind of put a priority in a list of the top things just that it are still being worked on I see the job is never done with infrastructure always evolving about DevOps certainly shows that with programmability what are the key areas still on the table for OpenStack that are that are key discussion points where there's still innovation to be done and built upon I think the first one is it's like going from a car to a self-driving car how can we get that infrastructure to autonomously manage itself we were talking about network earlier even in that context how do you get to a implementation of OpenStack that can self manage itself so there's a huge opportunity to make sure that the tooling gets richer to be able to not just deploy manage but fine-tune the infrastructure itself as we go along so clearly you know you can call it AI machine learning implementation you on OpenStack to make sure that the benefit is occurring to the administrator that's an opportunity area the second thing is the containers and OpenStack that we taught touched upon earlier OpenShift on OpenStack in many ways is going to be the cookie cutter that we're gonna see everywhere there's going to be private cloud if you've got a private cloud it's gotta be an open shift or on OpenStack and if it's not I would like to know why right it's a it becomes a de-facto standard you start to have and they enablement skills training for a few folks as you talk to the IT consumer right the the IT admins out there you know what's the message in terms of upskilling and managing say an OpenStack installation and and what does Red Hat doing to help them come along yeah so those who are comfortable with Braille Linux skills are able to graduate easily over to OpenStack as well so we've been nationally focused on making sure that we are training the loyal Linux installed based customers and with the addition of the fact that now the learnings offerings that we have are not product specific but more at the level of the individual can get a subscription for all the products that reddit has you could get learning access to learning so that does help make sure that people are able to graduate or evolve from being able to manage Linux to manage a cloud and the and face the brave new world of hybrid cloud that's happening in front of our eyes but let's talk about the customer conversations you're having as the general manager of the stack red hat what what are the what's the nature of the conversations are they talking about high availability performance or is it more under the hood about open shift and containers or they range across the board depending upon the use cases whose they do range but the higher or the bit is that applications is where the focuses well closes where the focus is so the infrastructure in many ways needs to get out of the way to make sure that the applications can be moving from the speed of thought to execution right so that's where the customer conversations are going so which is kind of ties back to the boring is the new normal as well so if we can make sure that OpenStack is boring enough that all the energy is focused on developing applications that are needed for the enterprise then I think the job is done self-driving OpenStack it means when applications are just running and that self-healing concepts you were talking about automation is happening exactly that's the opportunity in front of us so you know it's by N's code by code we will get there I think I love the demo this morning which showed that off right bare metal stacks sitting there on stage from different vendors right actually you're the you know OpenStack is the infrastructure layer so it's it's out there with servers from Dell and HP II and others right and then booting up and then the demo with the with Amadeus showing you know OpenStack and public clouds with openshift all on top also showed how it fit into this whole multi cloud stack is it is it challenging to to be the layer with with the hardware hardware heterogeneous enough at this point that OpenStack can handle it are there any issues they're working with different OEMs and if you look at the history of red add that's what we've done right so the rel became rel because of the fact that we were able to abstract multi various innovation that was happening at the so being able to bring that for OpenStack is like we've got you know that's the right to swipe the you know employee card if you will right so I think the game is going back to what you were only talking about the game is evolving to now that you have the infrastructure which abstracts the compute storage networking etc how do you make sure that the capacity that you've created it's applied to where the need is most right for example if you're a telco and if you're enabling Phi G IOT you want to make sure that the capacity is closest to where the customer fool is right so being able to react to customer needs or you know the customers customers needs around where the capacity has to be for infrastructure is the programmability part that we've you know we can enable right so that's a fascinating place to get into I know you are technology users yourself right so clearly you can relate to the fact that if you can make available just enough technology for the right use case then I think we have a winner at hand yeah and taking as you said taking the complexity out of it also means automating away some of those administrative roles and moving to the operational piece of it which developers want to just run their code on it kind of makes things go a little faster and and so ok so I get that and I but I got to ask the question that's more Redhead specific that you could weigh in on this because this is a real legacy question around red hats business model you guys have been very strong with rel the the the record speaks for itself in terms of warranty and and serviceability you guys give like I mean how many years is it now like a zillion years that support for rel OpenStack is boring is Red Hat bringing that level of support now how many years because if I use it I'm gonna need to have support what's the Red Hat current model on support in terms of versioning xand the things that you guys do with customers thank you for bringing that up what have you been consciously doing is to make sure that we have lifecycle that is meeting two different customers segments that we are talking about one is customers who want to be with the latest and the greatest closer to the trunk so every six months there is an openstack released they want to be close enough they want to be consuming it but it's gotta be production ready in their environment the second set of customers are the ones who are saying hey look the infrastructure part needs to stay there cemented well and then every maybe a couple of years I'll take a real look at you know bringing in the new code to light up additional functionality or on storage or network etc so when you look at both the camps then the need is to have a dual life cycle so what we have done is with OpenStack platform 10 which is two years ago we have a up to five year lifecycle release so obvious that platform 10 was extensible up to five years and then every two releases from there 11 and 12 are for just one year alone and then we come back to again a major release which is OSP 13 which will be another five years I know it can be and they get the full Red Hat support that they're used to that's right so there are years that you're able to either stay at 10 or you could be the one who's going from 10 to 11 to 12 to 13 there are some customers were saying staying at 10 and then I won't go over to 13 and how do you do that we'll be a industry first and that's what we have been addressing from an engineering perspective is differentiated - I think that's a good selling point guy that's always a great thing about Red Hat you guys have good support give the customers confidence or not you guys aren't new to the enterprise and these kinds of customers so right - what are you doing here at the show red hat summit 2018 what's on your agenda what some of the hallway conversations you're hearing customer briefings obviously some of the keynote highlights were pretty impressive what going on for you it's a Volvo OpenShift on OpenStack that's where the current and the future is and it's not something that you have to wait for the reality is that when you're thinking about containers you might be starting very small but the reality is that you're going to have a reasonably sized farm that needs to power all the innovation that's going to happen in your organization so given that you need to have an infrastructure management solution thought through and implemented on day one itself so that's what OpenStack does so when you can roll out OpenStack and then on top of it bring in openshift then you not only have to you're not only taking care of today's needs but also as you scale and back to the point we were talking about moving the capacity where is needed you have a elastic infrastructure that can go where the workload is demanding the most attention so here's another question that might come up from when I asked you and you probably got this but I'll just bring it up anyway I'm a customer of OpenStack or someone kicking the tires learning about deploying up a stack I say ritesh what is all this cloud native stuff I see kubernetes out there what does that mean for me visa V OpenStack and all the efforts going on around kubernetes and above and the application pieces of the stack right let's say if you looked at the rear view mirror five years ago when we looked at cloud native as a contract the tendency was that hey look I need to be developing net new applications that's the only scenario where cloud native would be thought thought off now fast forward five years now what has happened is that cloud native and DevOps culture has become the default if you are a developer if you're not sort of in that ploughed native and DevOps then you are working on yesterday's problem in many ways so if digital transformation is urging organizations to drive - as cloud native applications then cloud native applications require an infrastructure that's fungible inelastic and that's how openshift on OpenStack again coming back to the point of that's the future that customers can build on today and moving forward so summarize I would say what I heard you saying periphery if I'm wrong open ship is a nice bridge layer or an up bridge layer but a connection point if you bet on open ship you're gonna have best of both worlds that that's a good summary and you gotta be you know betting on open first of all is the first order a bet that you should be making once you've bet on open then the question is you gotta bet on an infrastructure choice that's OpenStack and you gotta bet on an application platform choice that's open shift once you've got both of these I think then the question is what are you going to do with your spare time okay count all the cash you're making from all the savings but also choice is key you get all this choice and flexibility is a big upside I would imagine British thanks for coming on sharing your insight on the queue appreciate it thanks for letting us know what's going on and best of luck see you in Vancouver thank you for having okay so the cube live coverage here in San Francisco for Red Hat summit 2018 John four with John Troy you're more coverage after this short break

>> Host: Live from Las Vegas, it's theCUBE, covering Dell Technologies World 2018, brought to you by Dell EMC and its ecosystem partners. >> Welcome back to theCUBE. We are live, day three of Dell Technologies World. I'm Lisa Martin, back hosting with Dave Velante and we're very excited to welcome back to theCUBE Karen Quintos, Chief Customer Officer at Dell EMC. Hey, welcome back. >> Thank you, thank you. It's great to be here with you both. >> Dave: Good to see you again. >> So, we saw you on stage on Monday, recognizing innovators and trailblazers. I always love, as a marketer, when customers are recognized for their achievements because the voice of the customer is the best brand validation that you can get. Talk to us about the customer awards program and highlight a few of the winners that were on stage. >> Well, first of all, I agree with you, Lisa, that the best way to talk about your products and your solutions is to do it through the eyes of the customer, so being able to honor eight of our super most inspiring customers on stage was great. We had hundreds of submissions from our sales teams working with our customers. We really wanted to bring the transformation stories to life. The stories that we were able to tell and the evolution that these customers have done in their industry and their business, was remarkable, so, you think about Ford and the autonomous car. You think about J and J and the work they're doing around securing their customer data. You think about Volvo and Zenuity, and the opportunities that they have had with technology and then some of my favorite, Arrowfarms, >> Love that. >> Teleconnected farm, and they're using technology in Newark, New Jersey, to transform the way that farming is done, conserving our natural resources, using 95% less water, and being able to do it, and, this, the IOT of farming, they're just all super rich and really really great stories. >> And then, you got, I have to ask you to say it, to pronounce, I loved your pronunciation of, Unidad, come on, help me. >> I know it was the first one, right? >> Dave: Unidad de Conocimiento. (laughing) >> Yes, yeah, you got it right, you got it right. >> Okay. >> They're a great story, too, right, I mean, here's an organization in Colombia that is a consolidation of different industries that are providing these services across Colombia and Latin America. They've absolutely figured out how to take a country like Columbia out of the perils of what has happened there with the drug cartel, really thrive on economic prosperity and they're absolutely kicking butt when it comes to the services that they're providing to all of their, their customers, so it's... >> And the state bank of India, was that the other one? >> State bank of India. >> They really had a global representation, it's awesome. >> Well, we looked hard for that. We looked hard for the global representation. We also looked really really hard and gave extra points to companies that had a purpose and a soul, so what they were doing, either with the technology or with the services that they're providing to their end customers, what's that, that purpose side? And, you know, you saw that in a number of these really awesome organizations. >> I'm going to ask you, so I'm going to ask a leadership question. When we first met, I think it was at Dell World. It might have been 2012, I think you were CMO of Dell at the time, so you, like a lot of leaders, you chair hop, that's kind of what you do. So you've now, playing it up. >> But 18 years at Dell, so, you know. >> Right, but, right, so, you take your best leaders and you say, alright, go fix this problem, go fix this problem, go, go inspire some people to do that, so, you've been, and also it's the, is it the chief customer office that you started? >> I did. Well, actually, Michael started it. >> A year and a half ago? >> Right. >> Well, what's that all about? How's the progress going? Give us the update there. >> Well, you know, I have to tell you, I give a ton of credit to Michael because he saw an opportunity in something that was quite new and quite novel, and now you look a year and a half later at what some of our competitors and others are doing. You know, Microsoft just named somebody that sits at their executive leadership team meeting, recognizing that customer relationships are the ultimate prize. Our ability to deliver a great customer experience is going to be the, is the next battleground, and, we've been leading in that area now for a year and a half, so, I'm the first chief customer officer ever at Dell Technologies, and our mission is really to make sure that we continue to push the needle, and drive an even better end to end customer experience. We're doing a lot around taking our top, most important customers, and there's a couple of thousand of them at Dell. I'm not talking about five or six, I'm talking about like thousands of customers that have consistently honored us with their business over the years so how do we put high touch, high loyalty kind of programs in place? The customer awards were a great way to recognize some of those top customers and put them on the stage and tell their story, and the piece that gets me even more excited is what we're doing around our customer data, so, how do we unleash the power of our customer data? How do we integrate it? How do we automate it? How do we put real time predictive analytics? By looking at a customer end to end and being able to figure out if that account is going to go red, because they've had a combination of things, go figure out what are the sources of value for them and unleash those, so, we're living in this AI big data world and living it realtime with, under the remit of the chief customer office. >> And if I heard you correctly, at the leadership team, you're kind of the voice of the customer? >> I am, I am. There's a lot of voices for the customer. >> Well, yeah, because the head, the head of sales are going to be doing that and. >> But they all come with their own bias, right? Or their own lens, right, so, we're actually, my team is a very very strong partner to our heads of sales, because sometimes heads of sales, I mean, they see these things clearly the same way that we do, but sometimes the voice around, well, this isn't working, we need to get better at this, our customers want us to go faster here, tends to get lost in, you know, business performance and close rates and all of that, and we have this unique ability to look at this end to end, and help to really advocate on behalf of customers and really do the right thing for them at the end of the day. >> Independent of the transaction metrics, is what you're saying. >> Yes. >> And it's different perspective, right? We talked about the voice of the customer being an objective brand validation, and you come from a different perspective. One of the things that, we had your CIO on earlier today, Bask, and he said, "We drink our own champagne." And then we had Ravi Pentaconti and he says, we eat our own dog food, we're right next to the therapy dogs. So I like that, but from what you're saying, you're using customer data to help make Dell Technologies differentiated, be able to revolutionize the customer experience, listening to those customers is key. Can you tell us a little bit more about how some of that data is being applied to revolutionize that experience? >> Sure, so, some of it's basic, some of it can be pretty transformational, so, and by the way Baz Guyer has been a significant partner with me on this journey, because he understands it. Listen, Dell's the only technology company out there today that has the rich, direct data that we have, combined with rich channel partner data. So, we have all of it, right? And some of our competitors do everything through the channel, a few of them do everything all direct, we do both. So, we have a huge advantage when it comes to that. We can look at the amalgamation of all of the listening posts that we have for our customers. We have a booth here, where we've brought in hundreds, thousands of customers, and we've asked them a series of questions. We have voice of the field surveys that we do with our sales team, we do NPS surveys, this survey, all of that. We can bring all of that together using big data and insights and we can prioritize the big things that matter. So one of the things that I see a lot of my peers at other companies get caught up in, is they're chasing 15 or 20 things. You know, at any given moment, we're chasing 3 to 5. And we want to move the needle on those 3 to 5 and then we want to get, capture and address the next ones. So that's what I would call kind of the basic, fundamental pieces. What I think is exciting, is, we can now take a view of a customer, a complete view of that customer, we know what they bought, we know who they bought it from, we know the number of escalations they've had, we know what their delivery performance has been, we know how many times they've changed the AE on the account we know what their corporate responsibility priorities are, and we can look at that in totality, and we can put an outreach kind of program in place for them, or, we can look at it and go, this one is about to go south, and we need to put our best people to go call on the account and help the account executive, who in a lot of ways sees this also, and help to figure out how to turn it around. >> So, and you can do that across the integrated company today? >> We have piloted across the integrated set of companies, and in the Q3 period of time, working closely with Baz, we're going to automate this and turn it into like an Amber Alert, early warning type of system, so that we can help the AE and our customers before things happen. And the other piece that we can do, is we know, we know the ten levers of customer value. And, you know, for the most part we do those generally well. But in some cases, some of the reasons that our customers come back to us is because we've discovered things at their account that they didn't even know was happening. So we're, we've got this power of big data sitting right in front of us with Chief Customer Office that can really, really light it up. >> Well the other thing you said is the account teams know when there's a problem, but the executive teams, they have limited resources. So you don't know where to prioritize. >> Right, and some of our AE's have more than one account. >> Dave: Yeah, right. >> So, you know, some of them are handling 20 accounts. So where this thing becomes really interesting is as you think about scaling it, down through the organization, not just at the top ones. The top accounts, they're one to, one-to-one kind of engagement, and those types of things. It gets really interesting when you start to get below that and you start to really use it in a more scaleable way. >> Plus, as you go more channel, right, and you go more to edge, you get all these complexities beyond just product portfolio. You're dealing with that stuff, but then the channel complexities, and then the new markets that are emerging, particularly in edge, and the channels that that's going to precipitate. >> Right, right. >> To me, this is even more important. >> So 18 months into this new role that Michael Dell created, lots of accomplishments, it sounds like you're really leveraging it to partner with customers to help, not just them, but also your internal teams, be able to identify where there needs to be escalations. What are some of the things that you're opening up with respect to diversity and inclusion, because that's also under your purview? >> That's right, that's right Lisa. What I think is really interesting is how much our sales teams now is coming to my team, to use some of these other platforms to open doors and have conversations with CIOS that they could not get before. So I'll give you a perfect case in point. The sales leader in the U.K. came to me and said, "I have a particular account in London, "I haven't really been able to make any progress, "the CIO is a woman, their head of infrastructure is a woman "you're going to be there in London, would you send her a note "and let's have a conversation around some of the things "that we have some mutual interest in." Technology being one, as well as getting more women involved in to technology. So we had this conversation, an hour in, she said, you know, if Dell would host a session with other female CIOs in the U.K area, I will open up my Rolodex and we will get other women to come. Two months later, we did it, in London in January. I was there, Michael was there, our heads of sales were there, we had about 15 or 20 of these super impressive women in the public sector, the private sector, higher education universities, big brands, we just did a similar one here at Dell Technologies World. We just hosted, as a matter of fact yesterday, 20 women, we actually had a couple of men that were there, too, all just coming together talking about areas that we deeply care about. How do we get more women and minorities interested in these technology fields. >> And here we are in 2018, this is still such an issue, and it's something that's still surprising when we get to see females on stage in keynotes, like yourself, like Allison Doo who was just chatting with you, Dave, and Stu. It's still, we're actually kind of going, hey, we're starting from a deficit whereas 20 30 years ago we were kind of going up. What are some of the things that you hear from your male peers in terms of the importance of showing multiple generations of girls and women you do belong here, if this is something that you're interested in, do not be afraid. >> Yeah, what I find remarkable in these conversations is there's clearly a number of key themes that are emerging. One of the biggest ones is, this is an economic imperative. You think about, there's going to be 1.1 million jobs in the computer science technology field over the next ten years. 45% of those jobs are going to be filled by U.S. college grads. It's a gap 55%. Women that are graduating in the area of computer science and technology is down, significantly, from like 30% down to like 18% right now. You are simply not going to have enough of what has been the traditional workforce in order to fill these jobs. So, that's one, and that's one that we at Dell care about a lot. Second piece that we care about, is, we just know that when you bring together a diverse group of individuals, always get to a better answer for your customers, you do. Research has proven it, we can prove it, we can see it, all of that. And then the third piece is, I just think women bring unique skills in a collaborative global context that can really bust through some of the big, complex, thorny opportunities that corporations are working through. >> So, ladies, let me jump in here, if I may. So there's two sides to this coin is, one is yes, we've got to get young women excited, but the other is you've got to promote women to leadership positions. Obviously Dell does a good job of that, clearly IBM gets high marks for that, I mean one of the sad things about seeing Meg Whitman go was that you had a dynamic woman leader. Maybe not the greatest speaker in the world, but one-on-one, super strong, and I think an inspiration to a lot of young women. And I think our industry clearly, Silicon Valley, Boston, just not doing enough. Particularly in smaller companies, larger companies I think do a better job, so your thoughts on that? >> My thought on that is it's a hard problem, but at its very basic, it's actually quite simple. And these are the things that we're doing at Dell, it takes commitment from the top, and at all levels of the company to make change, drive the accountability, set goals. To your point, go place some bets on the younger generation up-and-coming diverse talent, put them in roles, and then surround them with a support system that they need to be successful. And, we've done that, you know, Michael has done that, he did it with me. When, six or seven years ago, he called me and said how'd ya like to be Dell's next Chief Marketing Officer? And then you know, called me 18 months ago and said, how'd ya like to be Dell's first Chief Customer Officer. You need people that see things in that talent and you need that commitment. You need a culture that supports that. You need more role models. You need to get rid of and totally eliminate the harassment and the bullying and the old boys kind of club. You've got to create places where women and minorities feel like they can be themselves. Culture plays a huge, huge, huge role. And then, you know, communities play a huge role. So we have a very, very growing and thriving employee resource group set of networks. We have 14 of them across Dell and Dell EMC. And they're just a safe haven for where people of color, women, LGBT, veterans, disabilities can come and just be themselves, and be with others that they feel safe with. So, some level, it's not that hard. It really does take the commitment and the wherewithal and the sense of urgency that says we've got to fix it, and we have to fix it now. >> I feel like 2017 was a milestone year, I'd love to know what your thoughts are. You had that incident in the tech industry, with that poor misguided soul from Google who decided to write this Jerry Maguire memo and just brought a lot of attention to the issue, and then the #MeToo movement, so I feel like 2018 is a more optimistic year, but still, a lot of that stuff that you were talking about goes on, and it needs to be exposed. Again, I think the #MeToo movement brings that out and a lot of people are thinking uh-oh, wow. This really has to stop. Your thoughts, do you agree with that, or do you just think, no Dave, we're still way too far away. >> I think what #MeToo has done is opened a lot of eyes around how pervasive all of this is. I know, in the case of Dell, we have a zero tolerance zero tolerance policy when it comes to all of that. What was so shocking to us is how pervasive it still was in either other companies or other industries. To me, what is encouraging now, is the conversation is going beyond harassment, to aggression and bullying and culture and some of the things that have happened over the years, and by the way, it happens across all genders. There's articles that are being written now about women that are bullying and have bullied, so. This is something that all corporations need to be setting the tone around what are the right behaviors and those types of things, and we've been doing that now, for years. The other piece that I feel very strongly about, is, if men retreat from this conversation, that is a huge problem, a huge problem. Leaders like you have to be part of it. They have to be part of, this has to change. I want to be part of the solution. I have daughters, or wives, or nieces or whatever it is that I know that they have just as much capability as boys and men do, and my job is to help them. So I love it, I love the way that men and women are both coming together and engaging in this conversation. And we are seeing progress. I think everybody wants it to be faster, but we are seeing progress. Hey, yesterday at this CIO round table that we have, one of my favorite quotes, we got into this whole conversation around, well what is the next generation feeling? And one of the women that was there said, "hey, my daughter told me three weeks ago, "you know mom, she goes, I really think, "to me it's really simple. "I want to be a mom and I want to be a CEO." It's that simple. >> Wow, I love that. So in the last few seconds or so, Karen, you've made a tremendous amount of progress impact as the Chief Customer Officer in 18 months. What are you looking forward to accomplishing the rest of 2018? >> Well I think the thing that gets me really energized, too is how we're applying our technology in the area of corporate responsibility and innovation. So, you know, you saw our plastic bottle demo that we had here, that fish moves from one event to another, we got really serious around how do we play a really key role in stopping the plastics from entering the ocean? So there's 86 million metric tons of plastic that is in the ocean today. By the year 2050, there will be more pieces of plastic in the ocean than there are fish. You have to stop the plastic from entering the ocean, which is a pilot project that we did about a year ago, and we recently announced an expansion of that called next wave, where we have our customers that are partnering with us to figure out how do we scale that? So, General Motors, Herman Miller, are just a couple of examples. And then, at CES this year, we announced an effort that we're doing around how do you extract gold out of motherboards, and using that, and recycling that back into our motherboards and using it in jewelry manufacturing. So we partnered with a jewelry manufacturer out of the West Coast, Nikki Reed. She is creating this jewelry, these rings, through recycled gold, and it's 99% more environmentally friendly. So, I love the fact that we can use our technology to innovate, change the world, use, reuse the stuff that we're putting into the economy. So, scaling these is a big, big priority for me in 2018. >> Dave: Awesome. >> Wow, momentum is the only word I can think of to describe what you've achieved, what you're doing so far. Karen, thank you so much for stopping by and chatting with Dave and me, and congratulations on what you've accomplished, and we look forward to talking to you next year. >> Thanks, thank you. >> We want to thank you for watching theCUBE we are live, finishing up day three at Dell Technologies World in Las Vegas, I am Lisa Martin for Dave Vellante, thanks for watching.

(click) >> Hey, welcome back everybody. Jeff Frick here with theCUBE. It's 2018. We just got out of the CES show and all the rage is autonomous vehicles. You can't get away from it. It's what everybody's talking about. Tesla just announced their autonomous truck, their autonomous Roadster. We're here in Palo Alto, right on San Antonio Road. Googleplex and Waymo's are right up the street. So everyone is all about autonomous vehicles, but we're excited to be here at Phantom Auto and they're taking a slightly different approach for a slightly different problem. We're excited to have Shai Magzimof. He's the co-founder and CEO of Phantom Auto. Shai, great to see you. >> Nice talking to you, yeah. Thanks for having me. >> So Phantom Auto, you guys just got back from CES. You were giving demos, but you weren't stuck in, like, the little lane that was protected. You were actually driving people all over the streets. >> We were driving on the Strip, yeah, yeah. We actually were picking people from the hotel lobby, so the valet guys would let us in with an empty vehicle. These videos are actually also online, and we drove them off the Strip and back to the hotel, or to another destination. >> So you're doing a whole different thing. You do not have an autonomous vehicle. >> It's not an autonomous vehicle. >> You were the ultimate chauffeur driven vehicle. >> Right. Right. So again, for the show, we did our job to show that the vehicle can drive without a driver in the driver's seat, but what we do is actually a safety solution for autonomous vehicles. And that safety is basically what happens if an autonomous vehicle artificial intelligence doesn't work. Let's say there's something that it cannot see, or something that, you know, an unidentified object, road construction areas, severe weather conditions, all this stuff happens all the time. And autonomous vehicles may struggle with the situation so Phantom Auto provides a solution that we work with these companies. We provide them that solution that allows remote operations, so someone will connect remotely. >> So let's back up a couple steps. Autonomous vehicles are meant for no driver. You guys have a driver but you're really assisted driving with a person from a remote location. So how do you describe that in a short category? I'm sure the analysts will want you to have a category. >> The category would be the same way you think about air traffic control, right, or any type of control center, like call control centers. Any type of support for customers, you would have a bunch of people sitting in front of computers, in our case they're sitting at computers with steering wheels, we'll see that later, and they can connect to a vehicle remotely, and when they move the steering wheel or press the gas or brake, it would actually happen in realtime. So we have this software that allows this realtime, critical communication for autonomous vehicles. >> Now what's weird is when we first heard about you guys, I'm thinking, okay what is the use case? Am I going to send the Phantom Auto to go pick up my hundred-year old grandfather who probably shouldn't be driving anymore, where you're escorting it. But really it's a very different application, and I don't think most people understand that, in autonomous vehicles, there's a whole lot of use cases still that they haven't quite figured out. My favorite one is when two of them pull up to a four-way stop, and neither of them wants to go first. They get stuck in a friendly lock, right, they get paper-logger, some poor kid has his foot in the intersection and is trying to wave the car through and it won't go through. So it's corner cases that you guys are all about, to really enable that next-stage of machinery. >> When I started a company, right, I'm a big believer in autonomous vehicle, I wanted to make them happen faster and sooner because it's life-saving technology. This is going to change the world. We all want it faster. Now, the reason why we're still not there yet is because there are many corner cases, edge cases, these situations where the machine didn't train enough for, and in this situation they provide a cover. So we have a person that would sit in an office, he doesn't have to be so close nearby. When we were in Vegas a couple weeks ago, the driver was in Mountain View, so Mountain View, California, Silicon Valley to Vegas, and he moves the steering wheel and he moves it real time. >> But he's driving the car. >> Yeah. >> So one of the great knocks on cloud, right, is latency, and clearly the use case that's always brought up is if you're in a self-driving car, you don't have time for the data to get it to the cloud and back to make a decision if a little ball rolls out into the street. So latency is a big issue. How do you guys deal with the latency issue? >> That's our secret sauce, obviously, but I'm happy to share as much as I can. The high level description would be, we connect multiple networks at the same time. We would usually have only AT&T in your cellphone, right, or in your car, and then we have AT&T, Verizon, T-Mobile, and a few networks, all of these together are bonded, and once they're bonded they get a much stronger connection. It sounds maybe easy, okay so let's plug a few phones and then get a really good connection, but it's much more complicated than that. We share and split the data across multiple networks at the same time, we prioritize the data. So, like a brake, it's very important, right, so if the remote operator is pressing the brake, you want it to be first in the vehicle, where the right side of the camera is not as critical, so lower latency for the brake, and then a little bit higher latency for something less important. >> So you've got dynamic, kind of, latent distribution. >> It's all dynamic, realtime, you know, so that's what we do, our real core. We provide this communication, real time, critical layer of communication for the video streaming and back of the data from the remote operator, back and forth all the time. >> So that's one big piece of it. Another big piece of it is the communications between the occupants in the vehicle and the driver. Another really important piece that obviously most people aren't thinking about for autonomous vehicles because they don't have that use case. But that's a pretty important piece of your solution. >> Yeah, that's a big one. I'd say that for this, you don't need to do a lot of innovation. It could be a simple call with the driver remotely. But, we're all about safety, right, and we're all about giving passengers this psychological trust, and it is true, you want to sit in a car that drives 100% of the time. If I tell you that your car today would go in and drives only 95% of the time, you would not buy this car. Same thing with autonomous vehicles. So we provide a safety and service layer. On the safety side, it's about assisting the vehicle when there's an emergency. It could be post-emergency or before it happens. Let's say you're just stuck in the middle of the lane and you don't know what happens. Even if the driver remotely wouldn't actually drive the car, you still want to be able to talk to somebody, right. So, I'd start with first the person, the driver, the human being would greet you when you enter the vehicle. It's an autonomous vehicle, he would say hello, how are you, nice to meet you, my name is let's say Ben- >> Ben is going to be your driver. >> Your driver soon, and Ben is going to tell you that whenever you have a problem, if you need any assistance, he would be there for you. That already gives you like a whole different type of experience, and when you leave the vehicle too, he's not going to be there all the time engaged with the car. The car is going to drive on an autonomous AV system, but at least he's there in case you need him. >> And again, the attention thing, which is an issue, you see with some of the test autonomous cars out there we were talking before we turned the cameras on, where the engineer's got his hands ready to grab the wheel if there's an emergency. That's not really Ben's role here. The car is going to take evasive action in terms of emergency. It's more to get out of like these weird corner cases as you said. >> Correct, it's not a test driver. Today, most autonomous vehicle companies still require and mandate it, it's actually illegal. By the regs, you have to have a person in the car. We also have a person in the car, and we do that same thing, although when Ben is driving, he's not replacing that person. He's just assisting when the autonomous vehicle system would have an issue. >> Right. So the next thing I think that's pretty interesting about your company, as you said, you're a software company. There is hardware components, you can see the back of the car, we'll take some film of the driving station, but you use a lot of off the shelf, really simple hardware to execute this. There's Logitech, little steering wheels are over there, it feels like a big video game, you've got the big, curved Samsung screens, basic cameras on the car, so talk about the opportunity to build a software company and you're leveraging somebody else's autonomous vehicle technology to really get in the middle of this with just software, a pretty cool opportunity. >> I'll tell you what. The best time of my life was earlier this year, when I was just putting this whole thing together because it was plugging in the hardware and the software, I did it together with a team that's also here in the office. Obviously, it was more challenging because from a software person to try and build this hardware, you know, is more challenging, but I'd say today, you can get anything on Amazon, you buy on eBay a part you need, you plug it in and it would just work. So, again, we did a lot of iteration, I'd say we spent a bit more money than we were supposed to. But, that works. >> Right. And then the last piece of the puzzle that I think is fascinating is the way you're going to integrate in with other people's autonomous vehicle, so again, we talked about Waymo up the street, the Google one, Uber is working on theirs, Volvo, every day you read about BMW, et cetera et cetera, so you really get to take advantage of those hardware systems, the sensor systems, the control systems, not only from those autonomous vehicles, but you're seeing now all this stuff that's coming in factory, right, avoidance collision and radar and all types of sensors, so you will have to be able to take advantage of those different platforms and integrate your system into those various platforms. >> Right. So we would work with a company, let's say if it's one of the big OEMs or ride-sharing companies, we would know how their vehicle is set up, all we need for our solution to work is a bunch of cameras and a few modems, right, so cameras everybody have, it's one of the most essential things in an autonomous vehicle- >> Right, right. >> We would just tag into these cameras, use the modems that we need for the software to run, and that's about it. So it's a pretty straightforward solution to allow remote control assistant for autonomous vehicles. >> I'm just curious, when you're talking to customers or potential partners, what is the piece that really resonates with them when you kind of explain your solution and how it fits with what they're trying to accomplish? >> Right, so our solution is really trying to help them reach market faster, so we're not replacing anybody's work. We're adding another layer of support and safety so when yous computer crashed, when your software crashed in the car, we're going to be there with another redundancy system to support with a driver remotely. So, that's what we do at the service level. >> Okay, so can I go take a drive? >> Yeah, sure. Let's do it. >> All right, we're going to check it out, we're going to take a drive. We'll see you in the car. Thanks for watching. (upbeat music)

>> Announcer: Live from Austin, Texas. It's theCUBE, covering KubeCon and CloudNativeCon 2017 Brought to you by Red Hat, the Linux Foundation and theCUBE's ecosystem partners. >> Welcome back, everyone. This is a special live coverage here in Austin, Texas with theCUBE with KubeCon and CloudNativeCon. I'm John Furrier with my co-host Stew Minniman. Our next guests Mike Barrett, senior project manager at Red Hat and Brian Gracely, director of strategy, Red Hat. Guys, welcome to theCUBE. Welcome back, Brian. >> Thanks. >> Thanks. >> Alright, so Red Hat. I was at re:Invent last week and they want the Red Hat stamp of approval. A lot of customers, you guys have had a huge track record in all the large enterprises. Tier 1, now with cloud gain What's going on? OpenShift has been a big momentum point for you guys Give us the update. What's the status? How are you guys taking that Red Hat stamp of approval value with OpenShift? >> Well, even if we just start from where AWS was, so we were there last week. We're seeing a ton of customers who were Red Hat enterprise Linux customers picking that up, moving it into AWS. So we're seeing that footprint migrate, which is great. We had a huge announcement with AWS around extending their services back into OpenShift through what we call the open service broker. So, basically, think about putting AWS services in your data center or at least making it virtually look like your data center. Those things themselves are huge 'cause now customers don't have to say "Is it like all cloud, public cloud, "or all private cloud?" It's like hybrid cloud is there today, right now. >> Yeah. This started for us back in 2015 I remember the first five minutes of every customer conversation was "How do you pronounce Kubernetes?" >> John: (laughs) >> And 2016 was pretty much your choice of "How do I use containers?" And then the tail end of 2016, it got exciting, right? People were doing big numbers on deployments. 2017 was an unbelievable year for us. I mean, you name the market sector we have penetrated it pretty deeply with Kubernetes technologies, so it's been a great year. >> You guys have been really, Brian, I remember when we were working together I remember, what? Three or four years ago cloud-native we were kicking it around. We were joking with Lou Tucker earlier, "Hey, three years ago. Remember in Vancouver in open stack, when we were talking about how this could really be the land grab? And we were kind of pontificating. But I got to ask you specifically, you were early on cloud-native. You guys certainly saw it coming, as you always, always do in Red Hat, but what changed in your mind? What surprised you? What happened? You kind of called it out. It played out almost exactly as you said. Are you surprised that cloud-native and the whole pass folding into... How did it turn out in your mind? >> I think what it was and it is a little bit of a surprise 'cause you're trying to think what's going to happen in the future. I think what ended up happening and we hear this from pretty much every customer is we're going to change what our user experience is going to be. So if you're Hilton Hotels today, your user experience is a mobile phone with a digital key. Those folks are using Kubernetes We're seeing banks using Kubernetes, airlines, trains. All of them are like I want to be mobile I want my user experience to be better than it was before. I want to deal with like spikes in demand and stuff. What's been really surprising is, you would've thought okay, those aren't Silicon Valley companies, but all of those companies are using Kubernetes. So the technology, the community has made it simple to use. They've adopted containers like crazy. Which has been, we've seen a little bit of that with docker but it's accelerated. That's been the big trend we've seen. People want to change their customer experience, and containers make it easier and Kubernetes makes it scalable. >> Mike, I got to get your take on this, because he's bringing up a good point about the mobile phone. Software is now the product of the company. No one goes into a bank anymore, there's tellers around sure, but the app is the interface. The software is the product. >> Mike: It is. >> It's not IT anymore. It's actually a whole new business model. I mean it sounds cliche but that's actually happening. >> Mike: For OpenShift, it's always been about developer velocity even before it was about Kubernetes. It was about helping people bring new ideas to market through software. And the interesting thing about a CADs and a PASs and that debate in the industry on which would survive. Our take was that, you can build whatever you want, if you have the right technologies and the right solution and that you shouldn't have to make that choice. If you want to just launch containers, then just launch containers. If you want to developer experience, have that developer experience, but they're not two different things. >> One of the things that's been beaten around for the last couple of years is customers want to have really, as much of the same stack in their own data center as they have in the cloud. You know talked about Brian start talking about Linux everywhere. Of course Linux is everywhere. It's been very prevalent at the edge. How much of that stack needs to be the same? How much is okay different? How does Kubernetes fit into that? Mike maybe we can start with you. >> For Kubernetes, we've been asked a lot. How do we feel about the announcements of all the cloud providers now offering to manage Kubernetes service, and we love it. There are certain like Uber and Lyft. I'm sure Uber wishes Lyft wasn't there, but in a platform technology space. You want people to gravitate towards the technology. And now that we have that debate over and so many people are offering Kubernetes. People are willing to move forward with their careers around that Kubernetes. They're willing to bring their whole clientele and their corporations to Kubernetes, and we are in a good early adopter, early mover position to really help them with that. >> Explain that a little bit more because before if I wanted Kubernetes, well I could go get OpenShift. Where cater platform, that's Kubernetes but I'm using Azure, if I'm using Google Cloud, I'm using AWS. Where do you fit? Where do they fit? How does that relationship work. >> So it's a container platform right, and containers are movable images. The thing that people forget about is part of the trick of working with containers is how do you introduce change? We just talked about how we have to introduce developer velocity. You need a hook in front of it and a user experience in front of it that helps you deal with these containers. Build them, deploy them, wake up when they change, connected to the GitHub code repositories. All these different scenarios. Kubernetes is an engine and you can put it in a truck or you can put it in a Ferrari, and we just happen to put it in OpenShift. >> I got to ask you guys, what of the point about the whole industry comes and pass all this stuff. It's interesting, you guys didn't take the bait in that debate and one of the things I said at re:Invent. Brian I'd like to get your thoughts on this question too is I said at re:Invent to Andy Jazzy. Look all the fudd around cloud specifically Amazon has been debunked. It never happened and we just kept on executing. My point was, if you pay attention to the fudd and their rhetoric in the industry, and not be practical about what's going on. You can loose sight of the value groups, so I got to ask you the question. What has been debunked about OpenShift? I'll give you a chance to say it because I've heard over the years. We've heard many come oh, OpenShift. Share your thoughts because now we have enough history say look at, you're successful. You got great customers. What's been debunked all that fudd? >> I think when it comes down to is there's a lot of companies who get wrapped up in our technology is going to change the world. You need to adapt to our technology, whether it was a platform or a container thing. We got humbled. We got humbled about three or four years ago because the original OpenShift while it was great, it was simple for developers. Just was not getting the adoption that we wanted. We made a huge choice to say we're going Kubernetes. That was crazy back then. Now it was crazy to think you were going to partner with Google, who had never done Open Source in the open before. They were a cloud, we were a software provider like but we wanted the technology hook, line and sinker, and then we were really pragmatic with customers. Mike spends a huge amount of his time, going out and talking to customers going what do you want to do. I think when you do that and Amazon is the same way right, Andy says the same thing like listen to your customers. When you listen to customers, they tell you their problems and you're not religious about the technology and you're willing to make changes like that's how you can be successful and ultimately that's how OpenShift evolved. We embraced Kubernetes when the other thing wasn't working and now it's given us a huge advantage. >> Mike give us some color to that because you guys didn't get caught up with OpenShift into trying to line up with the industry rhetoric at the time. You just got down and dirty, and I bet on Kubernetes, by the way great bet. Hey what are customer's saying? What are the (indistinct speaking) workers? When customers talk, they don't say I want a pass layer. They don't say that but what do they say? How did you get there? >> At the end of the day, it's true that they want a application right. They want a service, they wanted to deploy a service, but the nuance to that is that how you deliver the platform will dictate the application or architecture that you're allowed to have. And what was happening in the market at the time it was a very narrow scope or types of apps that they were trying to provide. What we found was that we have a very large green field environment in those customers that are revenue generating apps. And they had a different application pattern than this micro services and this pure cloud-native. You always want to be able to do both, and we were the only one in the market that was helping you do both. Great and less super, congratulations. I want to get that out, I think you guys have a great accomplishment that's good job with the two days at good spot. Results, obviously is what they are but going forward where are we today. What's next? What's happening? I heard in the key note. I didn't hear several. I heard pluggable architectures and I heard service mesh. Okay you got my attention, what does that mean? I actually wrote down service mesh. So now that's the big thing. Is it going to redefine, reimagine? So these are cool concepts, how did that relate to OpenShift? >> Well from a pluggable perspective right, there was a time when people said, "I want to build a structure platform, "make it simple to get stuff." That model is blown up. That's where Kubernetes is gone. Make everything composable right, if you want like OpenShift brings together a lot but it's pluggable. You can integrate with a ton of the people that are here for customer choice, and then what we're learning is people are saying I'm learning how to build these distributed applications. I'm learning how to build them. But I need help, it's very hard to translate what you can do in Silicon Valley to what you can do in Cleveland or Austin or Boston or something. And so things like service meshes and STO and all these things are basically saying let me give you enough of a framework to build these cool applications. Don't make your developers have to do so much. Build some things into Kubernetes. Build them around this distributor architecture. Make it easier so that when the business goes, "Hey I want to try something new." developers don't go, aww I got to reinvent the wheel. It's like, oh there's a bunch of scaffolding there. I can build a building from that. >> And you guys have a product there, a state of the art. >> We do, obviously everything we do is going to be upstream. So we've been working very heavily with STO. We've been working with Onvoy which is coming out of Lyft. That's the cool thing right. Technology coming out of Lyft is now in the open source community. We can use it to help banks. We can use it to help insurance companies, like that's what's going on there. >> Mike one of the things we were looking at coming to this show is talk about complexity in the space. So many projects, how do you balance having an opinionated solution that hopefully helps customers through some of the main things verses giving them the flexibility to meet what their business needs. >> Yeah I think Brian touched on it and that's at the essence why Kubernetes is so successful as an open source community. If you look at any component of it, it is layerable, it's pluggable, it has defined APIs and interfaces where you can remove stuff. And that allows different businesses to come in and be extremely successful in the ecosystem without taking out the entire platform. And that API compatibility, those folks are what we look for and what we're offering to our customers. If our customer is invested in say NSX networking. They can use NSX networking with OpenShift. There's just a variability of mix and match. I think the last 12 months, 18 months have told us like opinionated, went too far. I mean essentially everybody who's made announcement on Kubernetes said, yeah we tried opinionated, didn't work. And that's where we are today, people have come back around to composable and we've seen it for three or four years, and that's what customer's want. They want it to be simpler but they still want some flexibility whether it's a vendor they want to work with or just a deployment model they want to work with. So you guys probably have more customers than almost anyone in this space. Any trends or data you can share as to what are the most success customers doing. What pitfalls should you avoid? >> The leading sectors for us so far has been government surprisingly, we provide an SE Linux layer on top that most people don't and that's very attracting to those types of customers. After that financial services, insurance industry in particular. Pharmaceutical type, an awesome trend right now is the energy around Kubernetes for HPC and GPU type computing. That's attracting oil and gas, that's attracting marketing analysis. >> Yeah there's a bunch around planes, trains and automobiles and here's what's cool about it. We'll look at BMW. BMW was working on next generation apps in their cars and then we look at Volvo, and Volvo is looking at how do you modernize their existing supply chain to be able to either just have a better sales experience. So same industry attacking different parts of their install base and so forth. So that for us has been really interesting. One day, you'll talk to a company that wants to build a mobile app and reshape their interface. And the next time, the next one wants to rebuild their back office system and that's what OpenShift has been able to do and have been successful. >> Mike Barrett, Brian Gracely, thanks for coming on theCUBE. Great to have you on. Obviously Red Hat continues to be a leader in open source, everyone contributed across the board. From day one and great success on OpenShift. Good bet on Kubernetes. >> Thank you. >> Nice to see those bets come home isn't it. >> Absolutely. >> (indistinct speaking) meet a lot of naysayers at the beginning. Love Kubernetes, good job, congratulations. Live coverage here at KubeCon and CloudNativeCon. I'm John Furrier. Stew Minniman live. After this short break, be right back. (uptempo techno music)

>> This is George Gilbert from Wikibon. We're back on the ground with Aman Naimat at Demandbase. >> Hey. >> And, we're having a really interesting conversation About building next-gen enterprise applications. >> It's getting really deep. (laughing) >> So, so let's look ahead a little bit. >> Sure. >> We've talked in some detail about the foundation technologies. >> Right. >> And you told me before that we have so much technology, you know, still to work with. >> Yeah. >> That is unexploited. That we don't need, you know, a whole lot of breakthroughs, but we should focus on customer needs that are unmet. >> Yeah. >> Let's talk about some problems yet to be solved, but that are customer facing with, as you have told me, existing technology. >> Right, can solve. >> Yes. >> Absolutely, I mean, there's a lot of focus in Silicon Valley about, like, scaling machine learning and investing in, you know, GPUs and what have you. But I think there's enough technology there. So where's the gap? The really gap is in understanding how to build AI applications, and how to monetize it, because it is quite different than building traditional applications. It has different characteristics. You know, so it's much more experimental in nature. Although, you know, with lean engineering, we've moved towards iterative to (mumbles) development, for example. Like, for example, 90% of the time, I, you know, after 20 years of building software, I'm quite confident I can build software. It turns out, in the world of data science and AI driven, or AI applications, you can't have that much confidence. It's a lot more like discovering molecules in pharma. So you have to experiment more often, and methods have to be discovered, there's more discovery and less engineering in the early stages. >> Is the discovery centered on do you have the right data? >> Yeah, or are you measuring the right thing, right? If you thought you were going to maximize, work the model to maximize revenue, but really, maybe the end function should be increasing engagement with the customer. So, often, we don't know the end objective function, or incorrectly guess the right or wrong objective function. The only way to do that is to be able to build and end-to-end system in days, and then iterate through the different models in hours and days as quickly as possible with the end goal and customer in mind. >> This is really fascinating because we were, some of the research we're doing is on the really primitive capabilities of the, sort of, analytic data pipeline. >> Yes. >> Where, you know, all the work that has to do with coming up with the features. >> Yeah. >> And then plugging that into a model, and then managing the model's life cycle. That those, that whole process is so fragmented. >> Yeah. >> And it's, you know, chewing gum and bailing wire. >> Sure. >> And I imagine that that's slows dramatically that experimentation process. >> I mean, it slows it down, but it's also mindset, right? >> Okay. >> So, now that we have built, you know, we probably have a hundred machine learning models now, Demandbase, that I've contributed to the build with our data scientists, and in the end we've found out that you can actually do something in a day or two with extremely small amount of data over, using Python and SKLearn, today, very quickly, that will give you, and then, you know, build some simple UI that a human can evaluate and give feedback or whatever action you're trying to get to. And get to that as quickly as possible, rather than worrying about the pipelines, rather than worry about everything else because in 80% of the cases, it will fail anyways. Or you will realize that either you don't have the right data, or nobody wants it, or it can never be done, or you need to approach it completely different, from a completely different objective function. >> Let me parse what you've said in a different way. >> Sure. >> And see if I understand it. Traditional model building is based, not on sampling, but on the full data set. >> That's right. >> And what you're saying, in terms of experimentation. >> Start doing that, yes. >> Is to go back to samples. >> That's right. Go back to, there's a misunderstanding that we need, you know, while Demandbase processes close to a trillion rows of data today, we found that almost all big data, AI solutions, can be initially proven with very small amounts of data, and small amount of features. And if they don't work that, if you cannot have a hundred rows of data and have a human look at some rows and make a judgment, then it's not possible, most likely, with one billion, and with ten billion. So, if you cannot work it, now there are exceptions to this, but in 90% of the cases, if the solution is not at, you know, few thousand or million rows of data. Now the problem is that all the easy, you know, libraries and open-source stuff that's out there, it's all designed to be workable in small amounts of data. So, what we don't want to do is build this whole massive infrastructure, which is getting easier, and worrying about data pipelines and putting it all together, only to realize that this is not going to work. Or, more often, it doesn't solve any problem. >> So, if I were to sort of boil that down into terms of product terms. >> Yeah. >> The notion that you could have something like Spark running on your laptop. >> Yeah. >> And scaling out to a bit cluster. >> Yeah, just run it on laptop. >> That, yeah. >> In fact, you don't even need Spark. >> Or, I was going to say, not even spark. >> No. >> Just use Python. >> Just by scale learning is much better for something like this. >> It's almost like, this is, so it's back to Visual Basic. You know, you're not going to build a production app in >> I wouldn't go that far. >> Well >> It's a prototype. >> No I meant for the prototype GUI app you do in Visual Basic, and then, you know, when you're going to build a production one, you use Microsoft Foundation Class. >> Because most often, right, more often, you don't have the right data, you have the wrong objective function, or your customer is not happy with the results or wants to modify. And that's true for conventional business applications, the old school whatever internet applications. But it is more true for here because it's much, the data is much more noisy, the problems are much more complex, and ultimately you need to be able to take real world action, and so build something that can take the real world action, be it for a very narrow problem or use case. And get to it, even without any model. And the first model that I recommend, or I do, or my data scientists do, is I just do it yourself by hand. Just label the data and say as if, let's pretend that this was the right answer, and we can take this action and the workflow works, like, did something good happen? You know, will it be something that will satisfy some problem? And if that's not true, then why build it? And you can do that manually, right? So I guess it's no different than any other entrepreneurial endeavor. But it's more true in data science projects, firstly, because they're more likely to be wrong than I think we have learned now how to build good software. >> Imperative software. >> The imperative software. And data science is called data science for a reason. It's much more experimental, right? Like, in science, you don't know. A negative experiment is a fine experiment. >> This is actually, of all that we've been talking about, it might sound the most abstract, but it's also the most profound because what you're saying is this elaborate process and the technology to support it, you know, this whole pipeline, that it's like you only do that once you've proven the prototype. >> That's right. And get the prototype in a day. >> You don't want that elaborate structure and process when you're testing something out. >> No, yeah, exactly. And, you know, like when we build our own machine learning models, obviously coming out of academia, you know, there was a class project that it took us a year or six months to really design the best models, and test it, and prove it out intrinsic, intrinsic testing, and we knew it was working. But what we should really have done, what should we do now is we build models, we do experiments daily. And get to, in essence, the patient with our molecule every day, so, you know, we have the advantage given that we entail the marketing, that we can get to test our molecules or drugs on a daily basis. And we have enough data to test it, and we have enough customers, thankfully, to test it. And some of them are collaborating with us. So, we get to end solution on a daily basis. >> So, now I understand why you said, we don't need these radical algorithmic breakthroughs or, you know, new super, turbo-charged processors. So, with this approach of really fast prototyping, what are some of the unmet needs in, you know, it's just a matter of cycling through these experiments? >> Yeah, so I think one of the biggest unmet need today, we're able to understand language, we're able to predict who should you do business with and what should you talk about, but I think natural language generation, or creating a personalized email, really personalized and really beautifully written, is still something that we haven't quite, you know, have a full grasp on. And to be able to communicate at human level personalization, to be able to talk, you know, we can generate ads today, but that's not really, you know, language, right? It is language, but not as sophisticated as what we're talking here. Or to be able to generate text or have a bot speak to you, right? We can have a bot, we can now understand and respond in text, but really speak to you fluently with context about you is definitely an area we're heavily investing in, or looking to invest in in the near future. >> And with existing technology. >> With existing technology. I think, we think if you can narrow it down, we can generate emails that are much better than what are salesperson would write. In fact, we already have a product that can personalize a website, automatically, using AI, reinforcement learning, all the data we have. And it can rewrite a website to be customized for each visitor, personalized to each visitor, >> Give us an example of what. >> So, you know, for example if you go to Siemens or SAP and you come from pharma, it will take you and surface different content about pharmaceuticals. And, you know, in essence, at some point you can generate a whole page that's personalized to if somebody comes to pharma from a CFO versus an IT person, it will change the entire page content, right? To that, to, in essence, the entire buyer journey could be personalized. Because, you know, today buying from B2B, it's quite jarring, it's filled with spam, it's, you know, it's not a pleasant experience. It's not concierge level experience. And really, in an ideal world, you want B2B or marketing to be personalized. You want it to be like you're being, you know, guided through, if you need something, you can ask a question and you have a personalized assistant talking to you about it. >> So that there's, the journey is not coded in. >> It isn't, yeah. >> The journey, or the conversation response reacts to the >> To the customer. >> To the customer. >> Right, and B2B buyers want, you know, they want something like that. They don't have time to waste to it. Who want's to be lost on a website? >> Right. >> You know, you go to any Fortune 500 company's website and you, it's a mess. >> Okay, so let's back up to the Demandbase in the Bay Area, software ecosystem. >> Sure. >> So, SalesForce is a big company. >> Yes. >> Marketing is one of their pillars. >> Yes. >> Tell us, what is it about this next gen technology that is so, we touched on this before, but so anathema to the way traditional software companies build their products? >> Yeah, I mean, SalesForce is a very close partner, they're a customer, we work with them very closely. I think they're also an investor, small investor for Demandbase. We have a deep relationship with them. And I, myself, come from the traditional software background, you know, I've been building CRM, so I'll talk about myself, because I've seen how different and, you know, I have to sort of transition at a very early stage from a human centric CRM to a data driven CRM, or a human driven versus data driven. And it's, you have to think about things differently. So, one difference is that, when you look at data in human driven CRM, you trust it implicitly because somebody in your org put it in. You may challenge it, it's old, it's stale, but there's no fear that it's a machine recommending you and driving you. And it requires the interfaces to be much different. You have to think about how do you build trust between the person, you know, who's being driven in a Tesla, also, similar problem. And, you know, how do you give them the controls so they can turn of the autopilot, right? And how do you, you know, take feedback from humans to improve the models? So, it's a different way that human interface even becomes more different, and simpler. The other interesting thing is that if you look at traditional applications, they're quite complicated. They have all these fields because, you know, just enter all this data and you type it in. But the way you interact with our application, is that we already know everything, or a lot. So, why bother asking you? We already know where you are, who you are, what you should do, so we are in essence, guiding you more of a, using the Tesla autopilot example, it already knows where you are. It knows you're sitting in the car and it knows that you need to break because, you know, you're going to crash, so it'll just break by itself. So, you know, the interface is. >> That's really an interesting analogy. Tesla is a data driven piece of software. >> It is. >> Whereas, you know, my old BMW or whatever is a human driven piece of software. >> And there's some things in the middle. So, I recently, I mean, looking at cars, I just had a baby, and Volvo is something in the middle. Where, if you're going to have an accident or somebody comes close, it blinks. So, it's like advanced analytics, right? Which is analogous to that. Tesla just stops if you're going to have an accident. And that's the right idea, because if I'm going to have an accident, you don't want to rely on me to look at some light, what if I'm talking on the phone or looking at my kid? You know, some blinking light over there. Which is why advanced analytics hasn't been as successful as it should be. >> Because the hand off between the data driven and the human driven is a very difficult hand off. >> It's a very difficult hand off. And whenever possible, the right answer for us today is if you know everything, and you can take the action, like if you're going to have an accident just stop. Or, if you need to go, go, right? So if you come out in the morning, you know, and you go to work at 9 am, it should just put itself out, like, you know, why wait for human to, you know, get rid of all the monotonous problems that we ourselves have, right? >> That's a great example. On that note, let's break and this is George Gilbert. I'm with, and having a great conversation with Aman Naimat, Senior VP and CTO of Demandbase, and we will be back shortly with a member of the data science team. >> Thank you, George.

>> Announcer: Live from the Javits Center in New York City, it's the theCUBE, covering Inforum 2017. Brought to you by Infor. (bright electronic music) >> We are back with theCUBE's coverage of Inforum 2017. I'm your host, Rebecca Knight, along with my cohost, Dave Vellante. We're joined by Barig Siraj and Nasser Bayram. They are both of the Zahid Group, out of Saudi Arabia. Thank you both so much for joining us. >> Good to be here, thank you for having us. >> So I want you to start out by just explaining to our viewers a little bit about what Zahid Group and Zahid Tractor, what you do. >> We are a large group based in Saudi Arabia. We're very diversified. We are mainly in heavy equipment, capital equipment business. We are the importer of Caterpillar machinery and Volvo trucks, Renault trucks, and many other products. More than 40 franchises. We have locations in more than 40 locations, or branches, more than 40 locations for their area, and we have about 4,000 employees, and we mainly focus on providing sales and after-sales services in the kingdom, with a big focus on after-sales. We pride ourselves to be the second to none when it comes down to after-sales services, and we strongly believe in technology and in digital transformation that is sweeping the world of business, and thus far, we embarked on this journey five years ago. >> So what does that digital transformation mean for your business, and generally, and then specifically for IT. Maybe you can start, Nasser. >> Well, first, we have to agree. The business model has changed. There are new business models that has disrupted every single industry landscape out there, and you have to be ready to change and accept that transformation, otherwise, you'll be left behind. The digital transformation takes you beyond managing an organization introducing an IT platform or technology. You have to change the way you think and your readiness to be able to manage where the future is going. If we look, we just attended this session, 52% of Fortune 500 companies in year 2000 no longer exist. They went out of business. In 2015, 55% of Fortune 500 companies lost money. There was no economic crisis or downfall. It simply missed the boat, or they did not, they were not very innovative in their digital strategy or thinking ahead, allowing their industry to be disrupted by people like Uber, Amazon, Alibaba, Souq, an other new entrants with very great innovative ideas and technologies. The old business model of cutting cost or restructuring an organization no longer works. You need to think differently and act differently, and hence, digital transformation becomes critical for your organization, and implementing an ERP platform, standardizing rationalization of your ERP platform, if you have more than one, like in our case, we have more than one, you have to have one standardized platform, one standardized processes, business processes, so that we have one source of data in order to be ready for the future where you can mine that data, have it be by analytics or business intelligence, in order to be able to better serve your customers and learning on about their behavior, about their trends, and how you can better position production services for them in the future to buy, and for you to remain profitable. >> So Barig, okay so now, that's, what Nasser just described, I'm inferring, is much more real-time, much faster, and more data. Your ability to analyze that data wherever it is, how do you, and the processes and people behind that as we talked about technology's the easy part even though some technology's even more complicated than ever. So what does that mean for the IT organization? >> Well for IT organization, we had, and we still have a legacy application built over 30 years. Now, and there we could not reap the benefits of the data mining, the standardization, even that just from AI capabilities on top of that. We cannot reap that until we have that standardized ERP Platform across all our companies. So basically, that's the tall order that was put on our plate, and what we have done, we started the journey. We're partly through it. We went live with two of our companies. We still have three more to go, and we've done it with lesser volume, allowing us to learn and therefore, once we reach our biggest volume company, we would have learned as an organization, not just applying the technology that even the personnel, the change management, the resistant pockets have to deal with all of that. >> Can you give an example of what you've learned along the way, becoming, as we said, it is so much about change management, and it's about getting people over this fear of change. Can you give an example of what you've learned, of what you're doing differently for the companies that have yet to have the rollout? >> The biggest learning experience we had, we just went live with one of our companies, called EJAR, which is a rental company. The success there of the learning, the success is a learning experience. We have a long journey for to go live with five companies, and this is the first one to go live. What we learned by doing that company first is the challenges of change management, how to support on live, challenge of data migration, data cleansing, readiness of the organization, not simply from change management perspective, but also from IT, legal, readiness of your documentation, the contracts, et cetera. It's a vast learning curve to overcome, and we're very happy that we took the strategic decision to go live once more company, so that we gain that experience, and that is the real success we got out of this project now. Now we better we feel we are in better position for the new companies to go forward with, when we go live, we learn so much about change management, where we failed and where we succeeded, we learn better about our readiness, whether it is Zahid Tractor, or Infor, or our IT, our infrastructure, our training program, our after go-live support, the war room was set up to support the go-live, and go in production. We've been two month in production. We're still having some challenges, but nothing that, there are no showstoppers, however, more and more every day, we learn more and more, and we are better positioned to go live with a bing bang on the big company. >> Nasser, as the executive in sort of leading this transformation, do you look for and demand new metrics, new types of KPIs that you want to see? >> Well, definitely, you do the whole thing because of the new metrics. The new metrics have to have built into it, not simply the traditional KPIs of your GPs and revenue and discount and so on, you need to look at customer behavior, customer analytics, pricing positioning, where you are going forward. In the old days, everybody would sit down around the table, say, "Hey, we're number one, okay?" That doesn't hold water anymore. You're number one in what? It's about number one in responding to customer requirements on that customer behavior. Today, with Amazon.com, many retail businesses are challenged, they're going out of business. How do you stop that business model? You can't. So how do you compete? You can. To do that, you have to have the right data in place, the right organization in place, and the right mindset to be able to lead your organization to compete in the new market space. >> Can you give our viewers some examples of the kind of data that you are deriving, in terms of this business analytics, in terms of understanding and deepening your understanding of customer behavior, and what customers want, and how it's changing, how you approach your customers and what you do for them. >> I'll give you a comparison. When we have a legacy systems, what you do at end of day, you extract your data, you transform it and you load it up to your data mart or data warehouse, and then you run your report, and if you're lucky, you have savvy users who can create their own reports on the fly, but with the way we're going with an integrated ERP solution and one standardized platform, we do hope we have the right analytics in place, and business intelligence in place, that we give our management the right data to make decisions, ready to make decisions. Not filtered data, not reports designed, and that takes me straight into your question on IT and ability to IT to deliver. There is no way for any IT organization to cope with the changes. Nowadays, when Amazon went live recently with Whole Food, it took them three to six, three to four months to deal with legal, to deal with retail, with pricing, with the announcement, the whole nine yards of marketing. How did they have their IT ready? That's a challenge. How can you do that in four to six month? That is the challenge in the future. If you don't have the right platform to do that, you will never be able to compete, and data analytics are critical for you to respond or predict the behavior of customer, so before a customer comes next time to the counter, you already have certain statistics that tell you what that person is ready for, and that takes you straight also into IoT. Your products, or our products now, are connected to the Internet. If you don't have IoT in place, connected to your back end, and your analytics, you won't be able to compete, and that would be the differentiator in the future. Those who could do that versus those who will continue to follow the old brick and mortar business model, restructuring and cost-cutting and whatnot. >> So your instrumenting your heavy equipment in the field, presumably, and that's, you're well down the road with that. That changes the data model, it changes the analytics model so I wonder if you could describe that a little bit. I mean, obviously you're processing data at the edge. How much data stays at the edge versus comes back to your central location, maybe you could add some color to that whole equation. >> Well the devices that are put on the machines, there are several ways of putting. The older models, you have, actually the PSSR has to actually go with his laptop, hook it up, suck the data, and bring it back for analytics. The newer models are more, are sending it to, directly to us, and enabling our, what I call tower, to do equipment monitoring, and be able to anticipate, we call up the customer and saying, "By the way." Actually tell the salesmen to call up the customer and saying, "You need to bring your machine in "because it's, you might face a failure "in so amount of time." So improving the customer side, that is, that is that part, but coming back to the organization change issue, we went from a legacy application that the branch managers waited until the end of the month to get the truth, to now being able to, seeing the performance on a daily basis, because they're seeing the truth because everything is connected, whereas before, whatever they did, they don't, their piece of the puzzle, they have a lot missing, and they, information that they waited until it show, send them back there, a report. >> And none of this takes place in the public cloud, is that right? >> No, it does, to add to that, the data is stored in the cloud. Customers have access to it, along with our SOS lab, which is oil sampling lab. They have access to the data to see what is happening, like predictive analysis of their machine performance, and as a result of analyzing the oil, plus any data collected from these machines. We do have cloud implementation. We just went live with our treasury management system. It is on the cloud, and it was our first deployment on the cloud, though the implementation of Infor today is still on-premise. Long-term, down the road, we may be looking at the cloud. >> I got to ask you, we hear Infor messaging about microspecialization, that last mile, all the hard stuff that nobody else wants to do. Is that something that you take advantage of in your industry, or is it? >> I'll give you an example. We utilize the implementation accelerator from Infor for the rental, and it's 77% of our processes map directly into that, so we, that enabled us, that, to have EJAR, which is a rental company, go much smoother. Now, we're working with Infor to enhance their equipment implementation accelerator, and it will be partly the same ratio, around 70% of the processes that we're going to go live with, are the standard processes in the product, out of the box, for the equipment rental, for the equipment business space. >> Our objective is to reduce customization as much as possible, go out of the box, or native, out of the box, as much as possible, but you have to accept the fact, depending on your business environment and some localization requirement, you have to do some customization. However we do have a governance in place, to make sure it's to the minimal. Otherwise, long-term, you'll be challenged with release management and change management and so on, and when you speak of the cloud, if you ever elect to go to the cloud, you can kiss customization goodbye. (Dave laughs) You have to be ready to adopt and adapt. >> And how about your security regime, as a result of the edge and IoT and now, cloud, how is that evolving? >> That's close to my heart. (laughs) >> Yeah, I'll bet, and probably the board's. >> Actually, well, (laughs) actually, interesting enough, many organization, like ourselves included, we invested so much money in building firewalls and security systems to protect what's behind the wall. Now with the cloud, well your most important data is no longer behind the wall. >> Rebecca: It's right there. >> It's outside the wall, so you have to have some kind of a hybrid security system, and you really have to pick the right partner who is hosting your cloud application, leasing your cloud application to you, so the challenge or the perspective of security, cybersecurity, changes drastically and totally, and your understanding of it has to change, otherwise, you just stay behind your own wall and guess what? You can end up locking yourself behind the wall, and you're going to miss the boat, but this does not mean that you'll let down your guard. You have to maintain your security awareness, you have to maintain your security diligence, and you should not underestimate the threats out there, because even if you are on the cloud, the biggest threat nowadays is through phishing. That's what we call the human firewall. Relegating the right awareness, the right education to your organization from within, to understand the threats and the danger of such a threat, otherwise, your password, that's how you access the cloud, you'll end up be compromised and guess what? So will be your data. >> Yes, so, Barig, Nasser, thank you so much for joining us. It's been great to have you on the program. >> Our pleasure. >> Thank you. >> Nasser: Thank you for hosting us, thank you. >> See you guys again, great, thank you. >> I'm Rebecca Knight, for Dave Vellante, we will have more from Inforum after this. (bright electronic music) (bright instrumental music)

>> Announcer: Live from Austin, Texas. It's theCUBE. Covering DockerCon 2017. Brought to you by Docker, and support from its ecosystem partners. (bright electronic music) >> Welcome to SiliconANGLE Media's coverage of DockerCon 2017. This is theCUBE. I'm Stu Miniman. My cohost for the next two days is Jim Kobielus, and happy to have as our first guest on the program, is Brian Gracely. A year ago, actually, Brian had a beard, and he was one of the hosts on theCUBE. He's now with Red Hat. Brian, welcome back to the program. >> Stu, great to be on this side of the table again. Good to see you guys. >> And Brian, you were at the first CUBE event back in 2010. We've had you on at least once or twice every year. You did a few more when you were on our team, but happy to have you back as a guest. Why don't you bring our audience up to speed? What brought you to Red Hat and what's your role there, and what brings you to DockerCon? >> Yeah, so, been at Red Hat about a year, a little less than a year now, worked on the OpenShift team, so focused on Kubernetes containers, integrated Linux. It was a great opportunity to be in open source, which I've been working on for a year. It was at home, it was in Raleigh, and it's a great team. It's a team that's growing. The Kubernetes space is growing, so, the vendor side of the world drew me back into Red Hat, so it's been good. >> Yeah, open source, big component about what we're talking here at this show. I heard open source mentioned a ton. It was developers, it was contributors. What's your take, did you get a chance to see some of the keynote? Solomon got out there, thanked the 3300-plus contributor. When he put up the name of the companies, I think it was 41% of the contributors for all of this are independent, but then, Red Hat's in the top six companies there. What's your take on that and the ecosystem in general? >> Yeah, I thought it was, I thought the keynote was good. Obviously, the show's doing well, so it's great to see the container space doing really well. We've been part of the Docker ecosystem since sort of day one. We like to say that we're probably the biggest distributor of what used to be Docker is now Moby, within Rail. But yeah, I think we see that, we obviously believe in the open source movement. We're seeing more and more customers, our customers who want to contribute, who want to make it the de facto buying decision as to what they use, so, yeah, it's great to see not only huge open source support, but then seeing it become, to blossom into very viable, commercial offerings around the market. >> Yeah, so, Brian, your team actually wrote a blog leading up to the show that says, "Containers or Linux." After listening to the keynote, with LinuxKit announced, it felt like, oh well, Linux is containers. It seems like, reminds me back, Sun is, the network is the computer, the computer is the network. It's all kind of looking at it. What's your take as to kind of the relationship of containers with Linux, of course Windows fits in the mix, too, but the operating system and the containers. >> Well, I think, the reason we really put that out was if you go back a little bit historically, not to bore people, containers aren't a Docker thing. Containers are a Linux thing. They were created by Google, Red Hat made a huge contribution sort of secondarily around namespaces, Google did cgroups, IBM did LXC, so it's been a core Linux feature for over a decade now. Docker did a great job of making it easier to use, but at the end of the day, even if you look at, like, what LinuxKit and some of these other things are, they're not about sort of Linux versus Windows, it's, they are all Linux, and it's how do I represent Linux in ways of doing that? So we really kind of want to just reinforce this idea that there are things that you expect out of your operating system, containers being one of them, but if you look at every other project that's being built around this space, whether it's Kubernetes, whether it's management tools that are be, they're all being built on Linux. That's the foundation of this, and it's kind of just a reinforcement to people that, remember where your tools come from, what that thing is that drives security for you, things in that space. >> Brian, you wrote a lot about kind of cloud-native and that journey kind of, rewriting applications, containers, for the fits into that a lot. What have you seen changing kind of last 12 to 18 months? Couple of shows I've been to lately, it feels like we're talking about lift-and-shift more than we are about building new applications. What's the application space look like, and I know Jim's going to want to jump in here. He covers the cloud-native stuff. >> So I think there's a couple of big things that, and I wrote about it for a while, and it's, how much has changed in the last two years have been really interesting. So, I think originally, when you went and looked at platforms, whether it was OpenShift or Cloud Foundry or Heroku or whatever, lots of sort of what we used to call opinionated systems. You dictated what developers did, right? And then, we had-- >> Jim: Opinionated systems? >> Very opinionated platforms, right? The opinion of us, the creators, was going to get forced on you, the developer, right? >> Stu: It made a lot of the decisions for you, so. (Jim laughs) >> And again, the idea was make it easier for you. You don't have to think about those things, but you're going to get them in the way that we want them, and what ended up happening was Docker would kind of became a standard way, a standard container format. We ended up having these open source schedulers like Mesos and Kubernetes and other things, and that allowed the platforms to be a little more, what I was calling composable, so, because developers may not want to use the languages that you force on them, they may not want to use them in those ways. So I think what we've seen is this sort of blurring between what used to be heavily opinionated to becoming more composable, modular, and there's always this trade-off between how much do developers want to care, how much do they not? So that's one big trend that we've seen, is this start of back and forth of what that is. The other one we saw was-- >> In terms of compatibility, (mumbles) quickly, do you see any trend in this space, containers, toward visual composition of applications? What I'm seeing in today, and I've seen generally in this space, is mostly coding, command line interfaces, any visual composition tools you guys provide or any partners of yours for-- >> Brian: Yeah, there's-- >> For building containerized applications? >> And so I think there's sort of two pieces there. It's a great question because ultimately, if the coding piece is hard, you only reach a small segment of those developers, right? You want to, it's like when websites came out, they were all hand-coded in HTML and stuff, and then you had things like Dreamweaver and these other visual tools, and then it exploded. We've seen that. To be successful in this, you've got to have tools in the desktop that make it easier for the developers. Red Hat does something that we call the Container Developer Kit, which is really, write your application, a lot of the stuff in the background gets hidden. Docker has Docker for Mac and Docker for Windows. We see some other tools. So that piece is important. The other piece that, to come back to your question about it, is it lift-and-shift? We probably see 75, 80% of the customers we work with who say, "Look, I know I've got to do cloud-native. "I've got digital transformation "and all these sort of things, "but I've got a lot of portfolio "that I'd like to modernize. "Can I do that with containers?" And I think what we've seen is, for the early days, it was containers are only for new. They only work for microservices, they're only for new, and what we're seeing, and this again goes back to the sort of, containers are Linux, is customers say, "I have an application that ran perfectly fine in Linux. "Why wouldn't it run really well in there?" And we've got customers nowadays, and this sort of blows people's minds, like, we've got customers who will pick up things like WebSphere, put them into a container, run them, modernize them somewhat, but, because the platform will give them automation, it gives them high availability, it gives them scalability, and they go, it works, and they get cost-effectiveness. So we're seeing a lot of that because you can address a lot of your portfolio. >> Oh, Brian, it's the typical maturation that we've seen. The use cases that put on stage, keep planes in the air, power the largest infrastructure, monitor fire alarms, websites, it's like, oh, this is same thing we saw in virtualization in every kind of way that's like, oh, containers run applications. (chuckles) >> Right. >> Right? >> Jim: Have you seen a big push by your customers or in the ecosystem to containerize more of the deep learning and artificial intelligence toolkits, like TensorFlow or Theano? Is that, with your customers, is that a big priority rate now or going forward? >> Yeah, so, I think the big data space was always an area that was kind of on the fence if it made sense to, in container, do you need an abstraction layer, do you want to be closer to it? We're starting to see more and more, so for example, Google with TensorFlow. Google, huge proponent of containers and Kubernetes. They're doing a lot of work to make that happen. We've been doing a lot of work with the Spark community to make Spark work really well in containers, and it becomes an issue of can you manage the resources? The container schedulers do that great, and then, can you manage getting access to the data, and we're seeing more and more storage become container-native and people understanding how that works, so yeah, the breadth of what you can do around containers has gotten very, very large. >> Yeah, any difference in how your customers look at it, whether they're doing on-premises or public cloud, or do things like Docker and Kubernetes make that not matter as much? >> I think what they, so, I joke all the time, none of our customers have a container problem. None of them have a, none of them wake up in the morning and say, "That's my problem," right? What they're saying more and more is, "I know I want to, I'd like to start getting away "from maybe owning data centers, "or by destiny, being data centers. "I need to leverage public clouds, multiple, plural," and they're sort of saying, "Look, I get the benefit of what they do, "but there's still operational differences, "what Azure does, what AWS does. "I would like some level of consistency," and so that's where the OpenShift conversation really comes into play. The operational model I can build with OpenShift as a platform is the same thing I can run on top of Azure, on top of AWS, on top of Google, and we're seeing more and more of our deals, our customers who say, "That's what it's going to look like. "Help us make that work," and today, they do it on a basic level. Somebody like Volvo, for example, some in their data center, some in AWS, and then, more and more, they go, "Go contribute upstream in Kubernetes, "and federate this stuff." Make it look more consistent, make it look more operationally consistent, and that's coming in the next version of Kubernetes, and so forth, so, that shift is happening, but what they want is sort of this consistency. The Kubernetes part, the Docker part, they're sort of details under the covers, but it does provide them a level of portability that's really important. >> All right, Brian, want to give you the final word. Red Hat has got Red Hat Summit coming up, OpenStack and Jim Whitehurst is going to be given, I think, the day one keynote there. Talk a little bit of Red Hat's presence here at the show, what we can expect to see in this space from Red Hat throughout the year. >> Yeah, so I think, from us here, and what you'll see at Red Hat Summit, like, containers are front and center. Obviously, it's an extension of Linux, but it's, we're becoming a company that's more about how to do applications faster, how to modernize applications, how to do them across multiple clouds, and it's this whole idea that those things that used to be really hard, you do them in software now, and the community is helping to fix those, so big presence here. Again, we've got a ton of customers who use Docker as a packaging format, run their containers, open, at Red Hat Summit, we're going to have 25-plus production OpenShift customers that you want to talk about running governments, running airplanes, running, like, they're going to talk about that stuff, so that part, we're really excited about. It's fun, it's fun at this point. They don't, our customers don't want to talk about containers. They want to talk about this digital transformation stuff, and that is making the technology industry fun again. >> All right, so that was my last question for Brian Gracely with Red Hat. My last question for Brian Gracely of the Cloudcast is, I haven't heard Serverless mentioned yet this week. What's wrong? >> I know, that's a good, it's a good question. The Serverless stuff's taking off two weeks from now, probably, at the same, no, down the street. Serverlessconf is happening. >> Stu: Is that part of OSCON then, or? >> No, it's its own event now. >> It's own event. >> Serverless complement to their own event. They'll probably get five, 600 people. We're seeing it as another way of looking at applications. It's functions, containerize them, write your own code, and you'll see us, you'll see what we're doing around OpenShift begin to incorporate that, sort of functions as a server, Serverless stuff, very, very soon, and around Boston timeframe. >> All right, well, Brian, always great to talk to you, and glad I can bring it to the audience, so Brian Gracely with Red Hat. We'll be back with lots more coverage here, DockerCon 2017. You're watching theCUBE. (bright electronic music)