>> Live from Orlando, Florida, it's theCUBE, covering Microsoft Ignite. Brought to you by Cohesity and theCUBE's ecosystem partners. >> Welcome back to theCUBE'S coverage of Microsoft Ignite 2018 here in Orlando. I'm Stu Miniman, and happy to welcome back to the program John Mracek who's the CEO of a Imanis Data. It's our first time at the show, but not your first time on theCube. Thanks so much for joining us and tell us we caught up with you in New York City talking about kind of the AI, analytics, all those things there. what what what brings a Imanis to Microsoft Ignite? >> So this has been a great show for us. And what I really see happening here is there's a vibrancy that probably didn't exist in Microsoft events, maybe four or five years ago. Because Microsoft really getting their act together on the whole how you migrate and bring people to the Azure. Right, because that's their agenda. And so where we fit in there is in our data management platform. We help customers migrate to a Azure. So whether it's moving your Hadoop workloads to Azure, or one of the products that's been featured here that we've gotten a lot of Microsoft support on is our migration tool to move from MongoDB to Cosmo DB. So we play really well into the migration story and it really leverages our platform. >> Yeah, one of the questions we talk about all the time is customers trying to figure out where things live and, well, it's like your cloud strategy. Things are changing over time. Customers have really multi-cloud environments, which really means they're doing a lot of different things and a lot of times they need to move them and sort those out. So what are the challenges you're seeing? How do you help those businesses make decisions today and be able to move things as needed in the future? >> Yeah, what we see and what we're playing into is really this evolution. You know, solutions really drive technologies. So in a large enterprise, you might have a division or a particular group that says, I need this BI or analytics tool and I need a big data platform to do it. So they build this. They build on top of some either NoSQL or Hadoop and then they've got this great solution. Well, that happens four or five times across the enterprise, and at some point in the enterprise, the CIO or somebody says, "you know, "we kind of got all these distributed data systems, "and like, who's managing them? "How is that data being moved "to your point about cloud migration? "Well, these are on-prem, these are in the cloud. "We want to put them all in the cloud, how do we do that?" And so that's where we're seeing as kind of the call for our product, which is, okay, I need a central way to manage and manipulate this data, as a fundamental problem. >> Yeah, so we all know that data is fundamental to a business. It's one of the most important things. We can use all the tropes of, it's the new oil or anything like that. But when you dig down, it's a lot of complexity into how, how do I get data? How do I manage data? How do I share data? We're sitting here in Cohesity, is the where we are in the booth. Can you help us understand, what are the solutions that you complement in the data space? What are the solutions that you replace? or a modern version or compete against in this space? >> So the way to look at us, we're at our most general, we're a platform for moving data from one platform to another. Okay, and that has many different use cases. But where we're getting a lot of customer uptake is on the backup recovery. It's like, I've got it here, I want to make a backup. We also see a lot in terms of migration, whether it's the Mongo to DB or I want to move from on-prem to cloud or cloud to cloud. And where we fit is if you look there's a legacy providers who don't traditionally go after the NoSQL and Hadoop space. And so where were a perfect complement to either those companies or folks like Cohesity. We have partnerships with Cohesity, Veem and others where they get in RFP or they're talking to a customer and the customer has a specific request for data management solution for NoSQL or Hadoop platforms. And that's where we come in. Because that's what we focused on exclusively from day one. >> Yeah, well, being at a Microsoft show, I mean, applications are central to so much and Microsoft does. Everything from Office, but on the data side, we spend a lot of time this week talking about SQL. Talking about Cosmos DB and cool new things they're doing. And of course, Microsoft's playing in a lot of the modern areas. We see them, big developers base here, even more of it at the Microsoft Build show, what do you see in the Microsoft space on the application modernization? Sounds like that would tie in quite a bit to what you're helping customers with. >> Yeah, so we have customers across all the cloud providers. But what we see in the Microsoft case is really people looking for maybe global easy deployment, customer facing as typical examples. So people who are really pushing the envelope, frankly. And there's almost like a bi-modal distribution. There's kind of some folks who are still trying to retrofit the old world and then others who are really embracing some of the new platforms. >> I'm not sure if you were at the keynote on Monday, Satya Nadella unveiled the Open Data Initiative. We've got Adobe and SAP and Microsoft there. I was talking to one analyst and reading some reports, and I'm like, well, it's not a coincidence that this was launched the week of Salesforce. Salesforce has a lot of data. Maybe that's a little bit of an attack there. But data across these big providers is important. I want to be able to share and leverage my data. You're in the data business. But what viewpoint you have of some of these really big providers of the application as they're going through their digital transformation, and making how do customers get the best value out of their data? >> So, my background, most recent background, I was in an ad tech company, where we're all big data. And the whole play there, is how do you manage your audiences, right? How do you have a unifying way to look at audiences? And so this is what's playing out on a more higher level, a more general level of how do I normalize and create a unified view of the customer and consistent data so that I can then manage it. And so that's an essential requirement to get the maximum value at out of that. Once you have that and you're in your data repositories, it's incredibly critical to protect them, to be able to orchestrate and move around. Where we fit in and how we see it is, these things are data, to reuse the term is the new oil and the new gold. And companies are realizing that it's really time to protect this data. I put all this investment into getting unified view of data. Wow, what are we doing about how do we back it up, restore it and move it? >> It's interesting, I've watched the space long enough. You go back kind of BI and DW days, go through big data. Now, we talk about a lot more of the analytics in the intelligence there. Help us as to, what are we actually realizing today that we were been talking about for years, and what what are still some of the stumbling blocks as to what we need to mature as an industry to really help unlock data. >> So, I mean, there's clearly the, what's driven a lot of the machine learning AI is the availability of data. It wasn't so much algorithms change dramatically, it was, we have a, so all the machine learning applications are really benefiting from this. But what we see as you know, some of the immediate things with our customers, is they're using big data as they create their front ends, engage with their customers. So how do they have the most up to date, real-time information to whether it's present an offer to a customer, provide customer service. So a lot of the use case we see is in that really bread and butter customer-level interactions and having an appropriate database to front end that process. >> Alright, so one of the biggest challenges of our time is really talking about distributed architecture. When I talk to companies scale comes on a lot, but it means very different things to different people. Can maybe talk about what you're hearing from customers, and how your solution helps customers for a variety of implementations. >> Yeah, so, we typically are targeting and working with customers in the 10s to 100s of terabytes. Up to, and our system handles up into into the petabytes. Typically, what we see is an evolution is, as I said earlier, somebody will develop a solution in a particular division, and then realize we've got this asset to protect. And then so IT starts to get involved and basically look at it holistically. So, we had one of our prospects, we went in and pitched at an SVP level and said, "what are the problems you're facing?" and it was basically this, I have all these silos of data. To get the maximum value out of them, and have a uniform look, whether it's look at our customers, the market, I need a uniform view to do my BI and AI. And so they brought us in and said, "Okay, paint a picture of how I can continue to have "these groups run autonomously and run their solutions, "yet at the same time, give me a unified view "and make me feel comfortable "that I've been able to protect the data, "move the data, massage the data." >> Great. Talk to me, when I look at this show, I see a lot of customers are still doing things, I'm trying to think how to say it nicely. Kind of the old way, it's like, if you look at them five years ago, is like, okay, Windows 2019's there great. I'll get there in five years, you play with a lot of more modern applications. What do you hear from customers? What, what is the profile of a customer that is, taking advantage and being competitive in the world? And what do you advise companies that maybe are a little bit behind the eight ball. >> So, you're right, and there's a really big spectrum of where people are in the adoption curve. And the way we look at it, if people were waiting for it, you know, when somebody goes, "Yeah, we're looking at setting up a big data system", it's like, okay, we'll talk to you in a year once you get the basics set up. But I see kind of two types of things. There's, say, the smaller, more aggressive companies, who are willing to move forward and say, "I just got to create a product, I don't care how I do it, "I don't have legacy issues." And they've moved ahead, and they're starting to get to the point where they're like, "Okay, we're mature enough where we actually need to spend on data management." The more typical case though is, as I said earlier. It's like these these new apps, that larger companies might have bleeding edge groups. So it's not being driven centrally. And so my, you asked about advice, right? So if you're sitting in the top of large enterprise and say, "Well, how do we get there. "There's kind of the tops down, "I need somebody to help me figure out." But there's also, let 1,000 flowers and let there be some kind of anarchy, if you will. Breaking the model, breaking the mold. Let people go build stuff and then over time start to figure out how to assimilate. So that'd be the biggest single biggest advice is, Yeah, you want to do the top down, but you really want to do the bottoms up. Because those people really know how to use the technology to provide a solution. >> Yeah, absolutely. Guy Kawasaki let 1,000 flowers bloom out there and everything. All right. Help bring this in. What kind of customer conversations are you having this week? We talked to the top about, there's real good energy to this show. Definitely, I felt that. What would you share with your peers that haven't been at the show? >> So the topics here are typically around the migration. Whether it's like to like, moving an existing workload into Azure, or the transformation. We also announced the show cooperation with Microsoft on moving any of your NoSQL workloads to Cosmos DB. So most of the conversations here have been related to migration. Either of, if you will, within the same Hadoop family, or, you know, like to unlike. Going from something to Cosmos DB. And that goes back to your earlier point about people trying to figure out what to do. They know there's this imperative to move to the cloud, and they're trying to figure out how they do it in bite-sized chunks. Right and protect their business at the same time. >> Yeah, so you mentioned Cosmos DB. We had an interview earlier this week about Cosmos DB. I definitely heard some good buzz at the show, What is it about that is drawing customers to it and what's that enable for them? >> Two things that I'm aware of, that I've seen is, again, the global nature and the ability to just kind of deploy anywhere. But also, I've seen a little bit around the dynamic schemas and the ability to map between them as a very quick way to ingest data. So you can get up and running quickly, instead of doing a lot of manual work to start using it. So those are things that are going to win developers 'cause it makes their life easier. >> Alright, John I want to give you the final word. What should we look to see from Imanis over the next six to 12 months. >> So we're going to continue to push forward with our platform around data management. You've seen in some recent announcements that, where leveraging machine learning in a very concrete way to do anomaly detection around ransomware. And also for administrators to be able to basically set rules or set goals and have the software do it. And that really steams from the fact that we're using a big data platform and machine learning to solve the problem of well, if you're running a big data platform, how do you manage the data? So the whole DNA of the company is built around that, and from a go-to-market standpoint, you know, partnering with folks like Cohesity and others where you've already got people in market selling a broad solution but they're missing a piece. So the other thing you'll see from us, is more partner announcements as we go forward. Alright, well, John Mracek really appreciate all the updates on a Imanis Data. Congrats on the progress so far. And look forward to catching with you up at future show. >> Great, thank you. >> Alright, we'll be back with more coverage here. Day three of three days live coverage. Microsoft Ignite here in Orlando. I'm Stu Miniman and thanks for watching theCUBE.

>> Let me check. (uptempo orchestral music) (uptempo techno music) >> Live, from San Francisco, it's theCUBE! Covering Red Hat Summit 2018. Brought to you by Red Hat. >> Hey welcome back everyone, we are live here with theCUBE in San Francisco, Moscone West, for Red Hat Summit 2018. I'm John Furrier, co-host of theCUBE, with John Troyer co-host, analyst this week. the TechReckoning co-founder. Our next two guests are Ashesh Badani, vice president and general manager of OpenShift Platform and Alex Polvi, CEO of CoreOS, interview of the week because CoreOS now part of Red Hat. Congratulations, good to see you again. Thanks for coming on theCUBE. >> You're welcome. >> So obviously this is for us, we've been covering both of you guys pretty heavily and we've been commenting very positively around the acquisition of CoreOS. Two great companies that know open-source, pure open-source. You guys got the business model nailed down, these guys got great tech. You bring it together. So the first question is how's everyone doing? How's everyone feeling? And where's the overlap, if any and where's the fix? Explain the true fit of CoreOS. >> I'm going to start Alex, you want to jump in after. We're very excited right, so when we first had interactions with CoreOS, we knew this is going to be a great fit. The conversation we had earlier, both companies delivers in open-source, delivers in the mission center to take us forward regard to Kubernetes, as the container orchestration engine, and then being able to build out value for our customers around it. I think from our perspective, the work that both CoreOS did in advancing the community forward but also the work they've done around automation or their upgrades, management metering, charge back and so on. Being able to bring all those qualities into Red Hat is incredible. So I think the fits been good. It's been three months, I'll let Alex comment some more on that but we've been doing a lot of work from integration perspective around engineering, around product management. At Red Hat Summit this week, we reveal details around some of the converged road maps, which I can talk about some more as well. So we're feeling pretty good about it. >> Alex, your reaction. >> Yes, it's been three months. If you've studied CoreOS at all, you know everything that we do really centers around this concept of automated operations. And so by being part of Red Hat, we're starting to bring that to market in a much bigger and faster way of really accelerating it. The way the acquisition are really successful is either mutually beneficial to both companies and they accelerate the adoption of technology and that's definitely happening. We had the announcement yesterday with Red Hat CoreOS around the Linux distribution. Last week, we did the operator framework. It was very central to the work that we've been doing as part of CoreOS, and then as companies in a lot of ways is being part of Red Hat for three months now. This is what our company would have looked like if we ever just another 10 years along or whatever very similar, we're like a mini Red Hat, and now we're leaped ahead in a big way. >> And you guys done a good work. We've documented on theCUBE many times, and we were in Copenhagen last week. Now covering the operating framework but I want to get your reaction. You guys did a lot of great work on the tech side obviously, you can go into more detail but we've always been saying on theCUBE. If you try to force monetization in these emerging markets, you're optimizing behavior. And this was something that's gone on, we've seen containers. It's been well documented obviously what's happened. It's certainly a beautiful thing. Got Kubernetes now on top working together with that. If as an entrepreneur out there that are building companies. If you try to force the monetization too early, you really thinking differently. You guys stay true to it. Now we've got a good home with Red Hat. Talk about that dynamic because that was something that I know you guys faced at CoreOS and you've managed through it. Tempted probably many times to do something. Talk about the mission that you had, staying true to that and just that dynamic. It's challenging. >> Yeah, as we set out to build a company in general, there are really three operating principles. There is build a great technology to solve our mission which is to secure the internet through automated operations, build a great place to spend their days which is really about the people and the culture and so on. Why are we doing this, and the third was to make it sustainable and by that I mean to build their own money fountains, building out of the middle of our campus. And so by joining Red Hat it's we have a money fountain sitting there. (laughing) It's spewing off a ton of cash flow every single quarter that allows us to continue to do those first two things in perpetuity, and that third one is something every company needs in order to continue to execute towards the mission. And the thing that's so awesome about working with Red Hat is we're very much aligned and compatible. Red Hat's mission isn't exactly the same thing we are working but it's definitely compatible. It's like Apache and GPL are compatible. It's like that type of compatible. >> You both believe in open-source in a big way. Talk about the Red Hat perspectives. Now you got like a kid in a candy store. Openshift made a big bed with Kubernetes. You see now, you have the CoreOS, how has it changed in Red Hat internally? Things moving around actually accelerates the game a bit for you guys, and you're seeing new life being pumped into OpenStack. You're seeing clear line of sight with Kubernetes on the app side. We were just at KubeCon. A lot of people are pretty excited. There's clear lines of sight on what's defacto. What people are going to build around, and also differentiate. >> Right, so I'll start off by saying I really hope our CEO, Jim Whitehurst doesn't see this interview but if it goes off in terms of money factor. I'm currently make budget request. I think I know what's going on. >> Balance sheet, cashless now. It's in the public filings. If I see a fountain of money spewing off the thing, >> The ability to reinvest. >> This is a really good fit. (laughing) The way to say this, they have a great business model. >> Yeah, yeah. >> Some of us will make money, some of us will spend the money. Some of us will spend the money, it will work out well. (laughing) >> It's a great win. It's a great win. It obviously accelerates the plans. The commercialization is already there with Red Hat. This is just a good thing for everybody but the impact of you guys accelerating, just seeing OpenShift. You can boil it down to the impact of Red Hat. What is the impact? >> So in all seriousness, I think the focus for us really has been about there is so much complimentary work that's been going on with the CoreOS team that we're bringing into OpenShift, and to Red Hat in general that accelerates everything that you're seeing. You saw some amazing announcements happen this week with regard to our partnership with Microsoft and getting OpenShift out and Azure, and joint support offering. The work we're doing with IBM to get IBM middleware as well as IBM Cloud Private support integrated with OpenShift. The work that Alex referred to around automation, being able to bring that to our customers. We see all the excitement around that front as well so we want to take all Techtonic work that has been going on at CoreOS, then move that to OpenShift. Carry forward the community that CoreOS built around Container Linux, and actually inject a lot those ideas into that Linux, our flagship technology. Bring that passion and energy to bear as well, and then carry forward a lot of the other projects that they have. For example, the Quake Container Registry, that's extremely popular. Carry that forward, support our customers to use that both stand alone integrated with the OpenShift platform. Other projects like FCB that Alex has been talking about which is the underpinnings of Kubernetes plus running worldwide. So all of those things, we can bring forward, and then all the advancements that were made in place by CoreOS as they're working towards their money fountain, just plug that right into it. >> And just as a point of reference, Brendan Burns flew in yesterday. Microsoft Build is going up so he left their own conference to come down here. >> As did Scar Guthrie, right? >> That's a great testament. This is the testament. They're coming down, really laying down support. This is a real big deal. This is not a fake deal, it's real. >> And so I want to talk a little bit about specifics of the timeline, the road maps. Sometimes with these mergers or acquisitions, it's well the technology will be incorporated at some point, and then it goes away to die and you never see it again. And then the people all leave, and then you ask what was going on. But here, you actually have, I was great. You were talking to me. You have some specific timelines and we'll start to see some of the Techtonics Stack in OpenShift fairly soon. >> Yes, absolutely so the acquisition was announced three months ago and we said at that time that by Red Hat Summit, we'll lay out for you a road map and so we're now starting to do that. We put out release of some materials around some details with regard to how that's coming out. We have detailed sessions going on at Red Hat Summit around the integration plans between Red Hat, OpenShift and CoreOS with a few specific areas with regard to OpenShift. You'll start seeing the earliest versions if you will of the work that's being done. This summer, we'll deliver the full road map to you there by the end of this calendar year. With regard to, for example pieces like the Quake Container Registry that's being made available and being sold now as we speak. Customers can go get that, and we want to make sure no customer is left behind. Right, that's a principle we put out. And with regard to supporting any existing customers on Techtonic or the Container Linux space, we're doing that as we're working to integrate them into the Red Hat portfolio. Can you talk a little bit about the decision for Red Hat's atomic coast and Container Linux? Now re-named again, CoreOS. That was one of the seminal inventions that you all made as you started the company. I think it had some brilliant ideas again about security and the operational aspects but can you talk about some of those technologies and the decisions made there? >> Yeah, like I said, the acquisition of CoreOS Red Hat was about saying look what can we take that CoreOS has been doing to accelerate both work and community but also what could be doing to deliver this technology to customers. So the goal was we'll take all the atomic and the word that's been going on there have that be superseded by the work that's coming out of CoreOS Container Linux carry the community forward. Release a version of that called Red Hat CoreOS and in its initial form make that actually an underlying environment to run OpenShift in. Okay so for customers who want the automation that Alex talked about earlier. They made that available both at the underlying platform. Make it available in OpenShift platform itself via the work that's come from Techtonic, and then ultimately, Alex will talk about this some more through operators. So trusted operations from ISP or third party software that would run on the platform. All right so now if you will, we'll have full stack automation all the way through. OpenShift also support Red Hat Linux, a traditional environment for the thousands of customers that we have globally. Over a period of time, you should expect to see much of the work that's going on Red Hat CoreOS find its way into it as well. So I think this just benefits all around for us both in the near term as well as long. >> And Red Hat Container certification, where does that fit into all this? >> Yeah, a great question, so what we announced maybe was, actually was two years ago was a Container certification program. Last year, we spent some time talking about the health of those containers, and being able to provide that to customers. And this year, we're talking about trusted operations around those containers. That carries forward, we've got hundreds of ISPs that have built certified containers around it, and now with the operator framework, we've had, I think it's four ISPs demonstrating previews of their operators working with our platform as well as 60 more that are committed to building ISP operators that will be certified again. >> So people are certified in general, pretty much. I think we're very excited. The fact that we went to KubeCon last week, announced that the operating framework have been based on the ideas that the CoreOS team has been working on for at least two years. Making that available to the community and then saying for the ISPs that want a path to market. Going back to the money fountain again for the ISP that want to pass through market which is pretty much all of them. We also have the ability to do that so give them an opportunity to make sure that as wide as possible some adoption of the software at the same time help with commercialization. >> Can you guys share your definition of operator because I saw the announcement but we we're on a broader definition when we see the DevOps movement going the next level. It's all about automation and security, you mentioned that admin roles are being automated in a way to see more of an operator function within enterprise and emerging service providers. So the role operator now takes on two meanings. It's a software developer. It also is a network operator, it's also a service, so what is that, how do you guys view that role because if this continues, you're going to have automation. More administrator is going to be self healing, all this stuff is going to go on. Potentially operations is now the developers and IT all blurring together. How do you guys define the word operator in the future state? >> Well I know the scenario of great interest to you. >> So operator is the term for the piece of software that implements the automated operations. And so automated operations, what is that? Well that's what sets apart, the way I think about it is what sets apart a cloud provider verses a hosting provider. It's a set of software that really runs the thing for you and so if we're going to get into specific Kubernetes lingo, it would be an application specific controller. That's a piece of software that's implements the automated operations. And automated operation is a software that gives you that simplicity of cloud. It's at the core of a database as a service. It's both hosting but also automated operations. Those two things together make up a cloud service and that software piece is what we're decoupling from the hosting providers for the first time and allowing any open-source project or ISP brings the simplicity of cloud but in any environment. And that's what the operator is a piece of software that actually goes and implements that. >> So a microservices framework, this fits in pretty nicely. How do you see obviously? >> Microservices, there's all these terms. Microservice is more of an architecture than anything but it's saying look, there's these basic things that every operations team has to go and do. You have to go and install something, you have to upgrade it, you have to back it up, when it crashes in the middle of the night, get it going again. A lot of these things, the best practices for how you do them are all common. There's no ingenuity in it. And for those things, we can now because of Kubernetes write software that just automates it, and this was not possible five years ago. You couldn't write those software. There were things like configuration management systems and stuff like that that would allow companies to build their own custom versions of this. But to build a generic piece of software that knows how to run application like Prometheus or a database or so on. It wasn't possible to write that and that's what the first four or five years of CoreOS was is making it possible, that's why you saw all these mat and new open-source projects being built. But once it was possible it was like let's start leveraging that. You saw the first operator come out about a year ago, and I think it was our ATD operator was the first one, and we started talking about this as a concept. And now we're releasing operator framework which is from all the learnings of building the first couple. We now made a generic, so anybody can go and do it, and as part of Red Hat, we're now bringing it to the whole ISP ecosystem. So the whole plan to make automated operations ubiquitous is still well underway. >> I'd love to extend that conversation though to the operator, the person. >> Right. I think you and your team brought the perspective of the operational excellence right to the table. A lot of cloud has been driven by the role of developer and DevOps but I've always felt like well wait a minute operators the people who use to be known as IT insisted they had a lot to bring to the table too about security and about keeping things running, and about compliance and about all that good stuff. So can you talk a little bit as you see the community emerging, and as you see all these folks here. How do you talk to people who want to understand what their role is going to be with all this automation in keeping the clouds running? >> Computers use to be people too. (laughing) But we're not going to completely automate away everything because there's still parts of this wildly complex system that justifies whole conferences of thousands of people that require a whole lot of human ingenuity. What we're doing is saying let's not like do the part that is the fire drill in the middle of the might that keeps you from making forward progress. The typical role of an operations person today is just fighting fires of mundane things that don't actually add a lot of value to the business. In fact, this guy is difficult because you only get brought up when things are on fire. You never get an praise when things are going well. And so what we want to do is help the operations folks put out those fires like the security updates. Let's just roll those out automatically. The way you do those across all organizations does not need to be special and unique but they're really critical to do right. >> Well it's just automate that stuff away and let the operations team focus on moving the business forward. The parts that require the human spirit to actually go and do, and if we get to a point where a CEO of a company is like, wow, I can not come up with a new vision for this imitative 'cause my operations team are just so fast at influencing them. Then we have to start worrying about operations people's job but I don't see that happening for a very long time. >> And no one is going to be sitting around twiddling their thumbs either. >> Let me just extend that point a little bit. The whole point of operators is to encapsulate human knowledge that ISPs have and bring that in the platform and automate it. So the challenge that we've had is an operations person is required to know a lot about a lot. So the question then really is how can we at least take some of what's already known by people and be able to replicate that and that allows for every one to move forward. I think that's just forward-- >> Well, there's a bigger picture beyond that, so I agree but there is also scale. With cloud, you have scale issues. So with scale automation is a beautiful thing 'cause the fire has also grown exponentially too so you can't be operating like this. Scale matters, super. >> The reason that this stuff was invented at Google initially was not because of Google's high career per second. Is that they were, to build the application they're building required so many servers that you couldn't hire enough operations people without writing software to automate it. So they were forced to custom design the system because they had so many servers to run to build the software that they wanted to build. And other companies are just now getting to that point because every company is going through a digital transformation. They have to have thousands of servers just to run their applications. There's no way you're just going to hire the operations staff to go and do it all by hand. You have to write software to turn the operations people into mech warriors of running servers. You need to wrap them in automation in order to scale that. >> At KubeCon, she made a comment that all those operations folks at Google are software developers. >> Brand engineers. >> Brand engineering, so they're not Ops guys just pushing buttons and provisioning gear and what not. They're actually writing code. You bring up the Google piece, the other piece that we heard at KubeCon. We hear this consistently that this is now a new way to do software development. So when a former Googler went to work for another company, left Google. She went in and she said, "Oh my God, you guys don't do. "You don't use board?" To her, she's like how do you write software? So she was like young and went out in the real world and was like wait a minute, you don't do this? So this is a new model in software development at scale with these new capabilities. >> I think so and I think what's really important is the work we're doing with regards to an ecosystem perspective to help folks. So one of the top things I hear from customers all the time is this sounds fantastic. Everyone's talking about DevOps or microservices or wanting to run Kubernetes at scale. Do I have the skills? Can I keep up with the change that's in place and how do I continue going forward around that? So we announced at Red Hat Summit Managed offerings from let's say Atos and DXC where you've got goals to integrate us helping folks, or companies like Extension T systems. The CEO came and spoke today about the work we're doing with them to help connected cars, and those applications be rolled out quick and fast. I think it's going to take a village to get us to where we want to because the rate of change is so fast around all of these areas and it's not slowing down that we'll have to ensure there's more automation and then there's more enablement that's going on for our customers. >> So some clarity, can you guys comment on your reaction to obviously we've seen OpenStack has done over the years and now with well Containers, now Kubernetes. You seeing at least two ecosystems clearly identified. Application developers, cloud native and then I would call under the hood infrastructure, you got OpenStack. Almost it clarifies where people can actually focus on real problems that the Kubernetes needs. So how has the Container, maturation of Containers with Kubernetes clarified the role of the community? If this continues with automation, you can almost argue that the clarity happens everywhere. Can you comment on how you see that happening? Is it happening or is it just observation that's misguided? >> I think we're getting better with regard to fit for a purpose or fit for use case. All right, so if you start thinking about the earliest days of OpenStack. OpenStack is going to be AWS in a box, and then you realize well that's not a practical way of thinking about what a community can do a build at scale. And so when you start thinking about a Word appropriate use case for this. Now you start betting if you will, a set of scales, you set expectations around how to make that successful. I think we'll go through the same if we haven't already or even going through it with regard to Kubernetes. So not every company in the world can run Managed World call. DYI Kubernetes, don't many companies will start with that. And so the question is how do we get to the point where there's balance around it and then be able to take advantage of the work? For example, companies like Red Hat work for us was doing to help accelerate that path 'cause to the point Alex was trying to make is the value for them being able to keep up with the core release of Kubernetes? And every time a bug shows up to go off and be able to fix and patch it, and watch that or is the value building the next set of applications set on top of platforms. >> That's great, well congratulations guys. Thanks for coming on theCUBE. Appreciate the insight. Congratulations on the three months into Red Hat. Good fit, and enjoy the rest of the show. Thanks for coming on, I appreciate it. >> Thanks. >> Live from Red Hat Summit, it's theCUBE's coverage here of Red Hat and all the innovation going on out in the open. We're here in the middle of, we open the floor with Moscone West with live coverage. Stay with us for more after this short break. (uptempo techno music)

>> Announcer: Live from San Francisco, it's theCUBE. Covering Red Hat Summit 2018. Brought to you by Red Hat. >> Hello everyone, welcome to theCUBE's special coverage here at Red Hat Summit. This is exclusive three days of wall-to-wall coverage of theCUBE. I've been covering Red Hat for years. Excited to be back here at Moscone West. I'm John Furrier, the co-host of theCUBE, with my co-host analyst this week, John Troyer. He's the CEO of TechReckoning, an advisory firm in the technology industry as well as an influencer, and he advises on influencer and influencer of communities. I would say it's community focused. John, great to see you. Welcome to the Red Hat Summit. We're going to kick it off! >> Great to be here. Thanks for having me. >> So you know I am pretty bullish on open source. I have been from day one. At my age who have lived through the wars of when it was second class citizen. Now it's first class citizen. Software power in the world. Again, on and on, this is not a new story. What is the new story is the cloud impact to the world of open source and business. We're seeing the results of Amazon just continue to be skyrocketing. You see Microsoft as you're having their developer conference of Microsoft Build this week. Google I/O is also this week. There is a variety of events happening. It's all pointing to cloud economics, cloud scale, and the role of software and data, and Red Hat has been a big time winner in taking advantage of these trends by making some good bets. >> Absolutely. I think one of the words were going to hear a lot this week is OpenShift. They are a container and cloud platform. Hybrid cloud is a super big emphasis here. Hybrid cloud, multi cloud already on stage at the first key note. They had a big stack of machines and they were going out to a multi cloud deployment right there on stage. Open source, also huge this week, right? The key note, the tagline, of the whole conference, if you are interested in open source, you should be here. I think you nailed it. It's going to be about multi cloud. >> It's exciting for me, I got to say. The disruption that's happening obviously with IT, with cloud, is pretty much out there. We pretty much recognize IT as transforming into a whole other look in terms of how it's operating, but the interesting thing that's just happening recently is the overwhelming takeover of Kubernetes and the conversation and in the stack you're seeing a rallying point and a rallying cry and establishing a de facto standard of Kubernetes. The big news of 2018 is, to me, the de facto standard of Kubernetes across a multi cloud, hybrid cloud architecture to allow developers and also infrastructure providers the ability to move workloads around, managing workloads across clouds. This is kind of the holy grail outcome everyone's looking for is how do I get to a true multi cloud world? And I think Kubernetes this year has the stake in the ground to say we're going to make that the interoperable capability. And Red Hat made a bet a couple years ago, three, four years ago. Everyone was scratching their head. What the hell are they doing with Kubernetes? What's Red Hat-- They're looking like geniuses now because of the results. >> Absolutely. In fact, I think by the end my joke is going to be this is the OpenShift Summit. I'll be very interested, John in your observations. You were at KubeCon last week. So that's the open source project and the ecosystem around Kubernetes. Red Hat owns a lot of Kubernetes. Red Hat employs many of the Kubernetes' leaders. They have really taken over from Google in a lot of ways about the implementation and go-forward path for Kubernetes. So this is the show that takes that open source project and packages it into something that an IT buyer can understand and take. >> I got to say one of the things that is interesting, and this is not well-reported in the news. It's a nuanced point but it's kind of an interesting thing, I think an inflection point for Red Hat. By them buying CoreOS has been a really good outcome for both companies. CoreOS, pure open source DNA in that business. Those guys were doing some amazing technology development, and again, all pure open source. Total pure. There is nothing wrong with being a pure open source. My point is, when you have that kind of religious point of view and then the pressure to monetize it Docker has had. We know what happened there. So CoreOS was doing amazing things but it kind of took a lot of pressure from the market. How are you going to make money? You know I always say it's hard to make money when you're trying to do it too early. So CoreOS lands at Red Hat who has generations of commercialization. Those two together is really going to give Red Hat the capability to go to the next level when you talk about applications. It's going to increase their total addressable market. It's going to give them more range. And with Kubernetes becoming the de facto standard, OpenShift now can become a key platform as a service that really enables new applications, new management capabilities. This should expand the RHEL opportunity from a market standpoint in a significant, meaningful way. I think if you're like a financial analyst or you're out there looking at this going, hmm, where's the dots connecting? It's connecting up the stack, software to service, with DevOps, with cloud native, Red Hat is positioned well. So that's my takeaway from KubeCon. >> Interesting. Yeah, before we move away from CoreOS, a lot of announcements today about how Red Hat will be incorporating CoreOS technologies into their platform. They talked about the operator framework. I think one of the bigger pieces of news is that CoreOS' OS, called Container Linux changes its name back to CoreOS and will now be the standard container operating system for Red Hat. That's kind of big news because Red Hat had its own atomic host, its own kind of micro, mini Linux distribution and so now they're switching over to that. They also talked about Tectonic, which actually is a really good automated operations stack, some of those technologies. In the future they will be incorporated into OpenShift. So they were talking a little bit about futures but it at least they've given a roadmap. No one was quite sure what the super-smart rocket scientists at CoreOS were doing here and so now we know a little more. >> And also at KubeCon they announced the open source of the operator framework. It's an open source toolkit for managing Kubernetes clusters. Again, and first of all, I love the CoreOS name. This is all about what Red Hat is doing. Now let's not forget the ecosystem that Red Hat has. So you're talking about a company that's been successful in open source for multiple generations now. Looking forward to this next generation modern infrastructure, you're seeing the stack look completely different with the cloud. If you look at all the presentations from Amazon, Google, Microsoft, the stack is not the old stack. It's a new concept. New things are happening so you've got to swap some pieces out. You get CoreOS, you bring that in, new puzzle piece. But look at the deals they're doing. They did a relationship with IBM, so IBM's back into the fold with Red Hat joining forces. >> Containerizing some of their biggest components like WebLogic and Dv2 and MQ. >> I think the containerization will create a nice compatibility mode, bring these old legacy apps into a modern cloud native architecture and gives that an opportunity to kind of get into the game, but also bring cloud native to the table. >> Absolutely. >> You've got IoT Edge, all these new applications. You just can't go anywhere without hearing about Internet of Things, machine learning, AI, cameras, whatnot. All this is happening. >> Absolutely. So we're going to break it down all week for the next three days. Red Hat Summit. It's all about containers, it's all about the Linux moment, kind of going to the next level. Cloud native, big time data action. All the great stuff happening. All done with open source with projects with new products being commercialized from these projects. This is the open source ethos. This is of course theCUBE coverage. We'll be back with more live coverage here in San Francisco at Moscone West after this short break.

>> Narrator: Live from San Francisco, it's theCUBE covering Samsung Developer Conference 2017, brought to you by Samsung. >> Hello, everyone. Welcome back to theCUBE's live coverage, exclusive coverage of Samsung Developer Conference, SDC 2017. I'm John Furrier, the co-founder of SiliconANGLE Media. Next guest is Patrick Moorhead who is the president and principal analyst at Moor Insights and Strategy, friend of theCUBE. We see him everywhere we go. He's quoted in the Wall Street Journal, New York Times, all the top publications, and today, he was just on Power Lunch on CNBC. Here for our Power Cube segment, welcome to theCUBE. Good to see you again. >> Hey, thanks for being here, and I appreciate you putting up with me heckling you from outside of theCUBE. >> Always great to have you on. Hard hitting, you're one of the best analysts in the business. We know you work hard, we see you at all the events that we go to. I got to get your take, Samsung. Obviously now obviously you run in parallel, at some point on Amazon, obviously winning in the cloud. Samsung downplaying their cloud, but calling about smart things. I get that, the cloud is kind of fragmented, they're trying to hide the ball there, I get that. But they talk about IOT which you got to talk about cloud without IOT, what's your analysis of Samsung? >> Yeah so first off, Samsung is a collection of really really successful stovepiped companies, right? You have displays, you have semiconductors, you have mobile phones, you have all these different areas and they say a lot of times your strength is sometimes your weakness, and the divisions just don't talk a whole lot. But what they did, and this is the first time I've seen this in a long time, is they got on the same page and said you know, we have to work together because IOT and connected and intelligent connectedness can't be done in stovepipes, we can't all go do our thing. So they're agreeing on standards, they're doing some really good stuff. >> And obviously we know from the cloud game now go back to the enterprises, more consumer, backing in from the edge, obviously the edge being devices and other things, I get that. But now the horizontally scalable nature of the cloud is the holy grail, we've seen Amazon's success continue to boom, they do more compute than any other cloud out I think combined. Maybe outside Google with their internal cloud. That horizontal resource pool, serverless as example trend, IOT, you got to have, the stovepipes got to be decimated. However, you need specialism at the application level. >> That's exactly right, and a smartphone will act a little bit differently from a camera which would be different from a refrigerator as we saw, right? Samsung wants the new meeting area to be, well not the new meeting area, we all meet in the kitchen, but the connected meeting area. So they all act differently, so they have to have even though they're different devices they have to connect into that horizontal cloud to make it efficient enough and effective enough for good responsiveness. >> I like the message of smart things, I think that's phenomenal, and I like that 'cause it connects their things, which are consumer things, and people like 'em, like you said very successful stovepipes. The question that I ask here and I try to get the execs to talk about it but they weren't answering yet, and I think it's by design. They're not talking about the data. Because again at the end of the day what's different from Alibaba again last week when I was in China, they are very up front. We're all about data acquisition and using the data to fuel the user experience. >> Right. >> That has to traverse across stovepipes. So is Samsung baked in that area, they have things going on, what's your analysis of data traversal across, is Bixby 2.0 the answer? >> So companies have to take, particularly consumer companies related to the cloud, have to have one or two paths. The one that says, we're not going to mine personal data to either sell you products or run ads, so Facebook, AWS and even Google, that's their business model, and then the other side you have people like Apple who are only going to use the data to make the products and experiences better. I think, I'll just pontificate here, the reason you're not getting a straight answer is I don't think they know exactly what they want to do yet. Because look at the market cap of Facebook. Apple, and even Amazon is planning to start and expand their own ad network. So I just don't think they know yet. Now what I would recommend to them is- >> Or they might not have visibility on it product-wise. So there's knowing what to do, or how to do it, versus the product capability. >> Well they have access to a ton of data, so if you're using Samsung Mail, if you're using, they know every application gets deleted, usage models of those applications. So they know a lot more than I think people think. They have a lot more data than people probably give them credit for. >> So they're going to hide the ball, I think they said that they're buying more time, I would agree with you there. Alright, question on IOT. Do you think that hangs together, that strategy? Obviously security updates to chip-level, that's one thing, can they succeed with IOT in this emerging stovepipe collapse fabric that they're bringing out? >> So I need to do a little bit more research on the security and also their scalability. 'Cause if you're going to connect billions of devices you have to have scalability and we already saw what GE Predix did, right? They did an about-face and partnered up with AWS realizing they just couldn't handle the scale and the complexity. And the second thing is the security model and how things like RM Embed Cloud and the latest announcements from Intel which is how from a gateway perspective you secure this work. So I have to go do some research on this. >> And by the way it's a moving train, you mentioned the GE thing, great example, I mean let's take that example, I got to ask you about cloud, because let's talk about Amazon, Cloud Foundry. Cloud Foundry became this thing and Pivotal tried to take and shape it, now they're claiming huge success, some are questioning the numbers. They're claiming victory on one hand, and I hear record, record, record! But I just don't see any cloud on Cloud Foundry out there. >> Yeah and I think the reason is, PCF, Pivotal Cloud Foundry is a Fortune 500 thing. And if I compare Fortune 500 to startups and other people, there's not nearly as much activity in the Fortune 500 as there is with the startups and the cloud native companies. So I'm optimistic. >> So you're saying Pivotal Cloud is more Fortune 500, less cloud native? >> Exactly, exactly. >> How about Amazon, what's your take, I know you were on Power Lunch kind of, now you're on the Power Cube, our new segment that you just invented by being here. (laughing) What is the Amazon take, 'cause that Reinvent event's coming up, what's the preview? Obviously we're going to have some one on ones with Jassi and the team beforehand, theCUBE will be there with two sets to come on if you're going to be there I'd love to have you on. >> I'd love to. >> Again, what's the preview for AWS Reinvent? >> AWS right, they had a seven-year headstart on almost everybody and then Azure and GCP just recently jumped in, and if you notice over the past year they've been firing canons at each other. One vendor says hey, I do by the minute pricing, and then another one says, oh, I have the by-the-second pricing, right, and I'm going to accept VMWare, oh no I'm not doing VMWare, I'm doing SAP. So what you have now is a feature fest and a fistfight now. AWS is no longer the only man standing here. So what I'm expecting is they are going to come in and make the case that, okay, we still are the best choice not just for IAS but also for PAS, okay? Because they have a lot of competition. And also I think they're going to fill in gaps in some of the regional services where oh they don't have GPUs in a certain country. Oh, I don't have FPGAs over here. I think they're going to fill that in to look better against GCP and Azure. >> I know you cover Intel as well, I was just over there and saw some of the folks there, I saw some of the Linux Foundation folks, obviously you're seeing Intel be more a computing company, not a chip company anymore, they have that Five-G end to end UK Mind and Mobile World Congress, talked a little bit about Five-G. End-to-end is big message here at Samsung, how is Intel positioned in all this, what's your take on Intel? >> Yes so I think related to Intel, I think in some areas they're competitors, because they have their own gateway solutions, they don't have cloud solutions but they have the gateway solutions. Regarding to some of the endpoints, Intel has exited the small cork endpoints in watches, so I would say right now there's less overlap with Intel now. >> From Samsung perspective? >> Exactly, now on the back end it's more than likely there's a 99% chance that the back end doing the cloud processing is going to be Intel. >> If I'm Samsung, why wouldn't I want to partner within Samsung? 'Cause they make their own chips, is that the issue or is it more a...? >> No, I think Samsung up until this point hasn't taken a lot of responsibility for the cloud. So this is a first step, and I think it would make a good partnership. >> And Intel could get the home theater market, the home, how connected home is, but every CES going back 10 years has been a connected home theme. Finally they could get it here. >> That's right, and I have seen Intel get into things, a lot of Amazon's products with the cameras in the bedroom and in the bathroom, scary stuff. But Movidius, silicon that's doing object recognition, that is a place where I think they compete which frankly Samsung could develop the silicon but they just don't have it. Silicon doesn't have capability that a Movidius has. That can be used in any type of camera. >> Okay so final question I know we got to break here and I appreciate you coming on, making room for you, PowerCUBE segment here in San Francisco at SDC 2017. Ecosystem, we hear the host of SDC, Thomas Coe, come up and saying we're going to be honest and transparent to the community here at large in San Francisco and around the globe, kind of incurring that they've been kind of stovepiped and they're going to open up, they believe in open cloud, open IOT, and he talks about ecosystem, I'm not seeing a lot of ecosystem partners around here. What does Samsung need to do to, well first of all, what's your letter grade on the ecosystem and certainly they got an opportunity. What moves should they be making to build a robust healthy ecosystem, because we know you can't do it end to end without support in the white spaces. >> Yeah so I go to a lot of the developer conferences, whether it's Microsoft Build, Apple WWDC, and even the enterprise ones, and this is a smaller, low-key event and I think first and foremost, operating system drives a lot of the ecosystem. And other than Tizen they don't have an operating system. So what they're doing is they're working on the connectedness of it, which is a different kind of ecosystems, it's farther up in the stack, but I think what they can do is they have to be very clear and differentiated and I think back to our earlier, our first conversation, they're not going to mine the data, therefore they're the safe place for you, consumer and our smart things ecosystem, to put your data. And we're going to help you make money to do that, because I don't think Google is as interested in that and I don't think Amazon is as interested in that either. >> They were clear, they said permission-based and even if they don't know what their permission is offering we're going to take the conservative route and protect the data, but they still got to use the data. They got to get their cloud story together, if they want to do the data play, cloud has to be more clear at least in my mind. >> Well I think what they can do is they're sitting on and they will sit on a bigger treasure trove of data that can help their partners deliver better experiences and products, because if you're at the epicenter and you're at that smart things hub? You know everything that's going on in that home whether it's your stuff or your partner's stuff. >> Yeah and they got to be trusted, and they got to be transparent, okay. Patrick Moorhead from Moorhead Insights here on theCUBE, great analyst, follow him everywhere on Twitter, your Twitter handle is, let me just get the Twitter handle. >> It's @patrickmoorhead. >> Okay, @patrickmoorhead on Twitter. He travels the world, gets the data and so does theCUBE, traveling for you, this is John Furrier. More after this short break. (electronic beats)

>> Live from Boston, Massachusetts. It's theCUBE covering Red Hat Summit 2017. Brought to you by Red Hat. {Electronic music} >> Welcome to the session wrap of the Red Hat Summit. I am your host, Rebecca Knight, along with my co-host Stu Miniman. Wrapping up three great days of open source talk. Where are we, Stu? Tell us the state of Red Hat, the state of open source. What have we learned? >> You mean, beyond we're in the seaport district of Boston, Massachusetts, you know, a couple blocks away from >> or the heart of open source the new open innovation lab coming from Red Hat. So, Rebecca it's been a lot of fun with you these last couple of days. >> I feel the same way. >> Did over thirty interviews: executives from Jim Whitehurst you know on down to many of the product teams many people participating greatly in open source, open innovation award winners, the women of open source award winners, open invest in lab participants. A lot of topics but okay Red Hat itself. I've worked with Red Hat in various roles in my career for quite a long time. We didn't talk a lot about Linux this week. >> Stu, Stu, Stu I've got to stop you Linux is containers, containers is Linux. So we're hearing so much about containers it's the same diff. >> Yeah, well I got the t-shirt "Linux is containers, containers are Linux" however, if I even look at Red Hat's messaging Red Hat Enterprise Linux is like the first platform what they built around and it's a little surprising that they didn't at least in the conversation we had, it was very much about some of the newer things coming into the show I said What's the progress that they've made around some of the cloud offerings, some of the management offerings, Ansible, weaving its way into a lot of the products. OpenShift really maturing and expanding the portfolio with things like the OpenShift io to be able to really help with application modernization. Middleware progressing even heard a little bit of the future where they are doing things like server lists. So Red Hat's making good progress. We love when we do these shows multiple years is they talk about it, they deliver on it, and in the way a couple guests talked about there's a little more transparency in open source and being part of all of these communities you have some visibility as to where you're going it doesn't mean that things don't slip every now and again and not every piece makes it into the product lease that they're expecting, but they've made great progress. Linux still is just a mainstay. It's a piece of lots of environments. The ecosystem reminds me of the same way I talk about OpenStack which we'll go into next week. We had a great session with Radhesh towards the end here talking about OpenStack in many ways is like that it's weaving its way into lots of infrastructure pieces some we'll dig into more this week, but let's focus on this week for now. >> Right, so you said we didn't talk a lot about Linux. I set you straight there. But what else did we, what else did you not hear? What do you remain skeptical of? As you said, Red Hat seems to be going from strength to strength. It had two point four billion in revenue this year. >> Yeah it did. For 2016, two point four billion in revenue and three billion in bookings >> Right And there was, I read a financial report that Jim Whithurst said Golda Company is five billion within five years. And you look at it and you say okay from two point four to five well, you know >> yeah actually if it was three billion in bookings and I think back to three years ago when we first started it was around two billion dollars that was almost a 50% growth rate in three years. So, if three years from now we do 50% growth rate we're going to have three to four point five. Of course the math is not linear, there's scaling of the company, there's lots of products in here, but they've got a big tam. >> Ambitious but achievable. >> Ambitious but achievable. The question we've had for a bunch of years is when I look at the cloud. Public cloud is affecting a lot of the traditional infrastructure companies. Red Hat is a software company. They're an open source company. We heard the cloud messaging. Microsoft and Google up on stage. Andy Jassy on video. That was a big question coming in. What about Amazon? How close will Red Hat do? Amazon actually has their own AMI for Linux which means I can get a package for Linux from Amazon not only that I could take that package outside of Amazon and put it in a data center so I could use the same type of Linux for AWS to work with Red Hat to take RedShift make what's deeper integration in the public cloud with AWS and if I put that on premises I'm going to have access to the AWS services so that tighter application integration for what they're laying out really the open hybrid cloud. Red Hat terminology, we'll see if other people take that up. But really it's a multi-cloud world and Red Hat has a good position to live in lots of those environments and provide and really help solutionize and give really almost that almost adult supervision that the enterprise wants for all of these open packages. So I was heartened to see the progress made. Strong ecosystem. As always, you know passionate customers, developers, and really just heartwarming stories of you know making the world a better place. What was your take on those pieces? >> Yes, absolutely. Those are really what you come away remembering. It is the story of a woman saving a man's life in a park in Singapore. It is the story of an emergency room doing a better job of serving its patients. It is scaling up technology use in the developing world. This is what you come away. And you say that is open source. >> Maybe next year that apple you get at the grocery store won't have been sitting there 18 months. >> Well maybe. But in a code climate. Boston going to be beautiful year round. No, but so I really do agree and that is I think what Red Hat did so brilliantly at this summit. Is really showcasing the ways in which this technology is having an impact at transforming industries obviously, helping businesses make more money, but also really doing a lot of good. >> Yeah, absolutely. And Rebecca I want a big shout out to the community here. This is a community show. Red Hat is a great participant of the community. We talked to Jim Whitehurst they want to help raise up the community it's not about Red Hat leadership. We don't hear number one at a show like this, we hear where they're participating and when they get involved they go deep. We heard about OpenPOWER. How excited they are that Red Hat you know getting involved and working in some of these pieces. So, we could not be here without Red Hat support. It's our fourth year doing the show. We had a blast with it. We see Red Hat at a lot of shows. They bring us great customers, their ecosystem partners and their executives. And it's been a pleasure to cover it. >> Yeah. No, I couldn't agree more and I do think, just in terms of what your talking about, the humility of the Red Hat folks is that they aren't going banging drums of we're number one in this and number one in that and you sort of think, "okay, blah, blah." No, they don't at all. They really are saying, "No we're about making our partners and our customers shine." >> Yeah, yeah. What's going to happen with the future of jobs? You know where are people going to work these days in the future? >> How will they work? >> Rebecca: What kind of processes will they work with? >> We've all said it's very much a global ecosystem here. Got to interview quite a few international guests here and hear how technology is spreading, how people are interacting, how innovation happens in a global environment. I'm sure ties back to a lot of the things that you write about. >> Absolutely. And I think, that Radhesh some of his words of wisdom was technology is the easy part what we need to be fundamentally rethinking is how we write these applications, how we develop these applications, how we design them, and how we deliver them. And, also really bearing in mind the end user. And, that is what we learned in a lot of our other sessions. Is really thinking about that. We heard from another person you know your competitor is maybe not necessarily the competitor you're thinking of it's the last app you opened or the last application that that company was using and what is drawing them toward that application or that technology or that infrastructure and not yours? [Stu]- Right. >> And so it's really thinking much more broadly about technology and who you're competing with and how you're working. >> Yeah, that was it was a bank. I loved that. They're like we're not competing against other banks it's like where's that other attention span that you have. >> Rebecca: Right, where are your eyeballs. >> One of my favorite lines is you know what you, Michelangelo, and Einstein have in common? You only have 24 hours in the day so you need to make sure you take advantage of that. That's the kind of thing that >> That's depressing Stu, when you leverage >> I don't know. the community. I thought it's inspiring. >> Okay. You know we can do >> Good great things when we work together and do that. So, we're always like oh I'm too busy or I don't have time it's like hogwash. >> Right. >> That's not the case. I'm inspired and fired up after all the conversations we had especially some of these great users here and looking forward to the next one. >> You're looking forward to the next one, you're looking forward to OpenStack coming up. >> Yeah, oh my gosh so right. >> Got to plug it. >> So Rebecca next week we're both going to be on theCUBE but in two different locales. Our team is in the midst of the sprint that is the spring tour. So we had the Micron event and we're here. Next week our team is at Service Now Knowledge, we're also at DELL EMC World in Vegas, we're at OpenStack Summit back in Boston. We've got some of our teams going to Microsoft Build. I'm sure we'll have analyst reports follow up from there. Boy do we have more shows than I can mention through the rest of May and June and beyond. Check out siliconangle.tv to catch all of them. Rebecca I'm going to let you do the close, but I have to say a big thanks to our team here and remote. >> Yes, yes. Leonard, Chuck, Alex, Ava. >> We love you all. Jeff and the team back there. You know we were doing some cool things playing with Facebook Live as part of this event, we always love playing around with some of the new technologies finding more ways that we can help reach you. We always appreciate your feedback. And Rebecca take us on home. >> Thank you so much for joining us here at theCUBE Red Hat Summit, Boston, Massachusetts. I'm Rebecca Knight for Stu Miniman, Thanks so much. {Electronic music}