>>from around the globe. It's the Cube with digital coverage of Red Hat. Summit 2020 Brought to you by Red Hat. >>Hi, I'm Stew Minimum And and this is the Cube's coverage of Red Hat Summit 2020 course Digital event This year. We're not together at Mosconi, but we are bringing together many of the speakers thought leaders, customers in this very important ecosystem. Really excited to welcome back to our program. Stephanie Cheers. Who's the vice president and general manager of the Red Hat Enterprise Linux business unit inside of Red Hat. Stephanie. So great to see you have to give you a virtual hug high five year, but you know, always great to see and have you on the program. >>Oh, thank you. So it's great to be here, and this is what together means today. But it's great to be together with you >>again. Here it's limit. >>Yeah, the discussion is you talk on it together apart for for a time we talk in tact. That change is one of the only constants that we have, and there are more changes than ever happening right now. So before we get into kind of your B you talk a little bit about, You know, some of the big changes. There's organizational changes, you know, I know we spoke to you about in 2019 at IBM Think and Red Hat Summit because you've worked for both sides of the equation here, Uh, give us kind of the latest from your standpoint. >>Yes, certainly the leadership changes which have been public now for a couple weeks. Those were a big change >>for for us. I think one of the things that has come through is IBM has really been respecting what red hat is. What? Um, what we do. But also how we do it is very important and valued. And we at red Hat >>believe in it so strongly. We're sticking to what Red Hat does best. Everything is open source. Everything is collaborative. And honestly, I have to say it. It >>feels great as a red Hatter to see Jim in the position he's in at IBM Um, Paul's passion, >>which clearly comes across in his keynotes and >>his passion for how we do have an open source development model. It's great to have them now take over the CEO role for Red hat. So it's it's really exciting times. I think. Last year when we spoke, it was, um it was a bit of a wait and see and see what happens. And I think now the recent announcements really solidify this sort of synergy and partnership that IBM and Red Hat have and what our intentions are in the market. But at Red Hat, we still stay red hat, and we're still driving things the way we always have. And that's great. Feels that >>that that's great. And thank you so much for the update. So when we talk about your business unit that the Red Hat Enterprise, Linux, of course, Rehl, um, you know, I've got a little too much history, you know. I go back when it was, whereas, you know, before well and kind of wash the growth of Linux sto become really, you know, the underlying fabric of so much of what we see out there today for all of businesses, so many companies could not exist if it wasn't for Linux. And in the seven years we've been having the Cube, of course, we've really watched that that moved from Lennox to not only be some of the foundations of what's happening in customer's environments, but also a major piece of cloud and cloud. Native S O. You know, give us that up date as to, you know, here in 2020. You know why? You know Linux has been around for quite a long time, but, you know, it's still is relevant. >>Yeah, so that's it. That's a >>great leader and ties exactly to how we look at well in the red hat sort of entire portfolio. Um, when you look at Lenox of how it evolved, it started out as being a bit of a cheaper alternative to units. But it quickly became, because of the open source way and collaborative way it's developed. It quickly became sort of this springboard for innovation because you have all these incredible innovators collaborating upstream. All of that has fed to a whole different view of what Linux is. Is cloud exists because of Linux is containers are just a different deployment mechanism or Lennox workloads, artificial intelligence. All those APS are built on Linux, so it's become this standardized foundation upon which innovation is done today, And for me, that's the most exciting thing, because it red hat and rail. Our goal is to one. Have it just work right? It has >>to be the standard. And, um well, sometimes that can be misinterpreted. It >>is boring or a commodity. It is anything but a commodity. It's probably one of the most strategic decisions that someone makes. Is which Raoul Distribution? Which Red Hat, which Lennox distribution did they use and that really take real pride that it's built for the enterprise? It's build for security. It's built for resiliency, and all of that build it once deploy anywhere, translates into also using all the innovation, all the container ization capabilities, using it across multiple public clouds. So it's really that combination of having it just work, be the foundation of where you build once and then being able to leverage all the innovation that's coming out of the open source world today. >>Yeah, really interesting points. Stephanie, I think back to when we talked for years about the consumer nation consumers, consumer ization. Excuse me of I t and people thought that therefore, there wouldn't be differentiation, you know, just by white box things and everything will be off the shelf. But if you look at how most companies build things, they really hyper optimize that. I need to build what I need. I need to use the tools that are available, and I need to be able to be agile. You know, I want one of my highlights last year talking to a lot of companies going through their digital transformation and a number of them at Red Hat Summit last year where they talked about both the organization and technology changes that they're making to move faster. And, of course, your portfolio is a big piece of helping them move forward. >>And that's one thing we're seeing that that ability to consume, innovation and get the >>most and extract the most out of what they're running today in their data center. As customers transform and take on this digital transformation, it's not just a technology statement. In most cases, it's an organizational statement as well. And how do you bridge both those and move it forward? It's one thing we focus a lot on right with the open innovation labs, with a lot of customers as well, because it's not just about the technology, it's about the way we work in the way we do things as well. >>Yeah. So, Stephanie, you know, every every year or so I hear it's like, Oh, well, we've got a new way to To the operating system. There was the Jeff just enough operating system for for a while when container ization came out, there was little company named core Os. That was like, Oh, we're going to make a thin version or core OS is now Ah, piece of red hat. Um, so still, with the cloud, there's always, you know, we're going to change the way the operating system it's done. Um, we just love your viewpoint as to, you know, Red Hat has, you know, a few options and kind of a spectrum of offerings. But how do your customers think about the OS these days? And you know, how should we be thinking about rail specifically in that overall spectrum? >>No, it's so that's a great question, too. And we look at >>it as Lennox and Rehl is be one thing that stays the same and helps you get the value out of all the work you've already put in all the development work you've already put in. And make sure that that translates to the future, where everything is changing, how you deploy where you deploy what you deploy. All of that may change, but if you want to get the value out of the work in the development that has been done yesterday, you need something to stay the same. In our view, that's real. We build it with um in mind for the enterprise along lifecycle security support. We build all of that into it so that when you build on a rail monorail kernel, you can take that. If you want to deploy it in a container, you can deploy on Rehl itself. Or if you need orchestration, you can deploy it on open shift. And that's part of the reason why you mentioned Core OS. So we now have a rail core. OS is within open shift 4.0, on beyond, of course. But what we did was we tailor down what is. In reality, it's the same packages. It's the same certification, security, all of that work that we put in. We take the core OS piece of it, what's essential and really optimized for open shift. We build that into an immutable image, and it goes out as part of open shift. It's not available separately because it's really tailored. What we pick the life cycle is all matching open shift, >>and what that does >>is provide you on open shift experience. That's easy to update fully across the board, all the way down to the kernel. But you know, it's the same Lennox that you have in rail, >>and it's that consistency >>of technology that we really strive for. Um, same thing in public Cloud. So when you build an image on Prem on REL, you can take that image up into the public cloud. And no, it's the same level of security and it just will work, you know, part of part of my team. And we take a lot of pride in the fact that it will just work on. And while that >>may not sound super exciting, particularly in days >>like like right now, being dependable and being reliable and knowing that it's secure, all of that is really important when you run your business that those those features or anything but commoditized >>Well, yeah, I think one of the real volumes that customers see with real specifically is there's so much change going on there, and you look at the Linux community, you look at what open shifts doing in the Kubernetes community. There's so much coaches going on red hat packages that make sure that you don't need to think about the almost chaos that's going out there in all of those communities. But you packaged those together. So Stephanie rarely was, of course, one of the highlights of last year's Red Hat Summit. So we'd love to hear you know, if you've got any good customer stories, really, the momentum of relate as you've seen it, you roll out around the world as and then we'll talk about the new updates. You have this. >>Yeah, great. So Rehl eight was a big deal for us last year, as you remember, and partly because not >>only all the features and functions, of course, which we put into it, but also because we really wanted to reposition what the value of an operating system is within a data center and within their innovation future. So we really focus all the features and functions into two buckets. One is about how do we help you with the operating system? Run your business better, more efficiently If the most out of the systems you have in the critical workloads that you run today and how do we use the operating system to help you bridge into the next level of innovation? What's coming down the pipeline? Things like containers. >>And we really wanted to >>make sure that, as we see you know, most customers are looking to how they digitally transform. But of course, no one has the freedom to throw away everything they've done in the past. They want to build upon that and get value out of it. So we really focused on balancing those two things now, as we look at. In fact, one of the commitments we made because we heard it from customers was they wanted a more predictable deployment of our minor releases and our major releases. And we committed, um, at the REHL eight launch that we would be delivery minor releases every six months, major releases every three years, and we have held to that. We delivered 816 months after we delivered eight. And now you saw last week we delivered eight dot too. Um, this is what it means for us to stand by our world and be dependable as an operating system. And the beauty of the subscription with well is that if you're a customer and you're running REL seven, particularly in times right now, it's It's not that easy to get into your data center, perhaps. And so if you don't choose to update to eight now, you can stay on seven until that time works. That's to me. That's part of the beauty and the flexibility of the subscription model. We have course want to continue to bring your new capabilities and new features. But the subscription Our goal is to have a value subscription that you can you can get the most value from No matter when you decide to upgrade or no forward with, uh, with a different releases, we have >>Well, you can go. And congratulations on keeping the releases going on schedule. One of the nice things about open source is we can see the roadmap out there. You've made this Ah, this promise and you're keeping to it. So ah is you said the announcements we made has been talked about in the keynote. So give us a couple of highlights. Says what people to be looking at and looking to learn more when they dig into a thought to >>Yeah, great. So we really wanted to stick with a few key >>messages with it, and they do really tie to How do we help you run your business? And how do we help you grow your business? It's one thing that we announced and what we pivoted to, um, with the eight dot io is we >>really moved to? How do we How do we >>deliver what we called an intelligent OS, which means an OS that helps you bridge the gap and brings more value to you in your data center than you got before? One of the key aspects to this was adding in the capability of red hat insights, and we added insights capability into every single rail subscription that is under current support. So whether or not you moved to relate whether you have real seven, if you have a supported version of real six, all of those had insights added to it, and what insights is is a as a service on cloud at red hat dot com and link up your servers, and >>it will give you insight >>into operational capability. Is it configured correctly is it could be optimized for better performance. Where are you on your C V E updates and what it does is take all that knowledge that Red Hat has from all the support cases and things that we're seeing what's happening in the industry, what we're seeing other customers have, and we can even proactively help customers. The feedback on this capability has been huge. In fact, you'll see in the announcement last week we've added a lot of new capabilities into this specifically For that reason we've had customers, you know, it's like having it's like having more ops people on my team because I'm getting this input in directly from Red Hat for things to look at. And so that, to me, was probably one of the key aspects that, as we look from going to eight into eight dot too, how do we build up that capability? And of course, last week you saw we added a lot to that, and I think now more than ever, we want to make sure that everyone who has a real subscription is getting the most value out of that and I think insights is one of the places where if you have a subscription and, um, you can value or you can get more value from operational help, insights is a place where we want to help you. Um, we everything we had prior we have now bucket sized into a capability and insights called advisor is really about performance, stability and security and doing an analysis for you. We've added a new capabilities around vulnerability, Right. How do you re mediate common vulnerabilities and exposures, compliance aspect, patch aspect policies and drift? Um, kind of all of those we've now bucket it in into that insights capability. So this friends a lot more value to something that we have already seen. Customers say, You know, we didn't expect to get this amount of input and continuous growth because we constantly add new new rules into that engine. And so you know what? What we what we knew yesterday will be what we know tomorrow, and we look forward to sharing with that with everyone >>who has a subscription. So this is >>a place where I think it's ah, it's an important place for folks to look, particularly now because operational efficiency is really key. And security is really we have a lot of capabilities in both. What? Yes, Please, >>please, please, go ahead. Now, >>one other aspect on that that I wanted to mention >>was we also added a capability called subscription watch and subscription Watch helps you get a very simple, clean view of all the subscriptions you have and where they're running. And that was one thing that we saw. Customers say there was friction. And how do I know where my entitlements are? How I'm using them across my entire enterprise Corruption watch can help with that. So, um, this sort of cloud dot red hat dot com capability that we can assist with and is already part of your subscription. These are the kinds of things that we really want to help augment this to make Really intelligent os for the enterprise. >>Yeah. Stuff Stephanie. The comment I was gonna make is there's certain shows that I go to that every year. You go to it, You say Okay, it's a little bit bigger. They announce something. They made some progress on it. What has impressed me most about going to the red Hat show year after year is really the the growth of the of the portfolio, if you will. So when I first started going to it, it was, you know, a lot of the people there were, you know, the hard core Linux people. Um And then, you know, there's some storage people, some networking people is cloud containers really grew. It really blossomed into this really robust ecosystem. Oh, and growth there. So would love just to get your viewpoint on, you know, the skill set because, you know, I'm sure there's plenty of companies out there that are like, Well, you know, I've got some people that are, you know, my limits people, and they do things that aren't there. But, you know, how do you see kind of the skill set and what what Red Hat's doing really permeating more and more of, of companies, day to day activity. >>I think one of the things that I'm >>most proud of is even since last year's all the deeper collaborations we have between the various product lines. Certainly we'll talk with Joe Fitzgerald, and he and I work together very closely. Capabilities like insights. How do we add answerable capabilities directly into real. And what that does is really help. I think in any customer today, skills is probably one of the biggest concerns that they have. How do they grow those skills? How do they help folks grow and learn more and progress into the innovation areas? But clearly they still need their their mission critical applications to run and how do they span that? And I think what we're really trying to do is be able to bring the strength of the portfolio together to help a customer have more flexibility in how they leverage their skills and how they grow their skills. >>Because I think coming back to >>that statement that that you made earlier it's not just about technology. It's about how, if >>you really want to be, have agile, it's about >>how a company has organized. And I think we're hoping that we bring together the strength of the portfolio so that a customer is able todo leverage their organization and leverage their skills and the best way possible. I think another place where we worked hard on eight dot too. Some similar lines of bridging the portfolio was, you know, we announced back in eight dot io. We were putting container ization tools directly in Terrell with build a pod made in scope e 08 dot too. We brought in the newest versions of Scope EO and Build Up. In fact, in tech preview, you get containerized versions of those, and so we're continuing to add. What we are seeing is the container ization is a journey for customers. Many customers just want to deploy a single container on a server. Or they were. They want to deploy a single container in a VM Um, they're not ready for orchestration. We wanted to put the tools in so that a customer could do that on REHL. Get started, get those containers deployed on REHL. Put those tools directly, and we added it to old protocol, which is a tool built for security. It brings that security of SC Lennox and brings that up and adds value at the container level. It's those kinds of things as you see the bridge from well into open shift. How do we help a customer rich? That skill journey as well along that path and I think right now in kubernetes and Containers skills is a is a big, big area of focus, so the more we can help ease that across the portfolio and bring those things together is really important. And I know we're working very closely with the chefs in the, um and the team there in order to help bridge that. >>Excellent. Stephanie, I just want to give you the last word. We talked a lot about the ongoing journey that customers are going through. So give us your final take away as to how customers should be thinking about red hat in general and role specifically as their journey goes forward. >>I think I think one of the things >>we're very proud of here at Red Hat is that we always, particularly in the open source communities with our customers, with our partners, we want to roll up our sleeves and help, and that's we want. So, developer, we wanna work upstream with you. It's one of the things we're very proud of, and now, particularly in this time it's We want to make sure that folks understand we're here to help, and we want to make sure that you're getting the most out of the subscriptions you have, Um, and we help. We help you on that journey both to get the most out of you can out of your data center today. But also be ready for the innovation that you want to consume going forward. And we're collectively working across red Hat in order to make that happen. But it's, um >>even though this is different and it's there the virtual Experience edition of Red Hat Summit. It's >>great to be together and be able to share the whole message. >>Well, Stephanie, the open source community is definitely used to collaborating remotely. So thank you so much for joining us. It's a pleasure to see you. And we would hope to talk again soon. >>Great to see you too. Thank you for the time. >>Alright. You're watching the Cube's coverage of Red Hat Summit 2020 digitally with remote guests from around the globe. Instrument a man and thank you for watching the Cube. >>Yeah, yeah, yeah.

>> Announcer: Live from Boston, Massachusetts, it's theCUBE. Covering IFS World Conference 2019. Brought to you by IFS. >> Welcome back to Boston everybody, you're watching theCUBE, the leader in live tech coverage. My name is Dave Vellante, I'm here with my co-host Paul Gillin. This is IFS World Conference 2019, theCUBE's second year covering this conference. Michael Ouissi is here. He's the Chief Customer Officer at IFS. And Raul Sahas. Industry Partner, Enterprise Application Services at TCS, a platinum partner at IFS World. Gents, welcome to theCUBE. >> Thank you. >> Thank you for having us. >> You're very welcome. So last night I poked around the customer event and I was impressed with the number of partners here. I think the number is 400, is the public number. What is it about the ecosystem that's attracted to IFS? >> Well, first of all, I think the ecosystem has now understood that we have renewed our commitment to the ecosystem. That is something a shift in mindset in IFS that is demanded by our customers, that our customers actually ask of us especially while we're moving into also more global corporations, and win more business there. They appreciate the choice of either IFS or our partners, or a combination of our partners and IFS actually helping them deliver the value that they expect from an ERP solution. >> So Rahul, from your perspective, so TCS you're obviously platinum partner so you're making a big investment. Why, what's happening in the market place? Where's the momentum with the tailwind? >> If you look at TCS, TCS is obviously helping customers to become business 4.0 organization, which is all about harnessing the abundance of possibilities around digital technologies and getting more intelligent, better, lean, harmonized, standardized. And so that's where we believe we are partnering with, and we are trying to leverage the ecosystem and one of the ecosystem obviously partners are IFS, which is a strategy partnership for us. And we believe that the investments that IFS has made and some of the unique last-mile solutions are going to help us to deliver those different shaded offerings to the customer, and create newer partnerships with them. >> Michael your role is a net new role at IFS, did you get to write your own job description? I guess, what does a Chief Customer Officer do? >> Well, first of all, well, in a sense yes. We actually did specify exactly what that role is, and we did discuss what the best is for the journey we want to get on, when Darren asked me to take on the role. And what a Chief Customer Officer does, and there's a specific reason why we're doing it that way, a Chief Customer Officer really is heading up, and that's what I'm doing, is I'm heading up all customer-facing functions within IFS. So from sales, to pre-sales, to support, to services. So it's all the customer-facing functions, coming from how do we engage with a customer, pre-sales, and after sales. And the reason why we did it that way is we wanted to have complete ownership and accountability for the transformation that we underwent and that we wanted to go through because we really needed to make sure that all parts of the business were aligning around this transformation, and pulling in the same direction. And that's why this role got created newly. >> So what's the nature of the partnership, what the history of the partnership? How did it start, and where do you guys want to take it? >> Well I think we have a obviously longstanding partnership with IFS. And I think both of the organizations have a deep mutual respect. And I think that one thing that we are trying to see the centricity around our partnership is all about the customer. We keep the customer and we want to ensure that we help our customers. We're customer-first organizations. And obviously the investments that IFS made, especially in the field services area, ERP area. I guess those are the areas which is helping, because ERP, if you see, one of the strategic lever for an organization to elevate their digital agenda, and get the right infrastructure in place, the right partner in place, to ensure that they create a differentiation and create exponential value for the customer. And that's exactly where IFS and TCS are looking at the market, and ensuring that we are helping our customer create exponential value for themselves in the market. >> Michael: Yeah and I think that maybe adding to that, we share the same belief as well that actually the time of the monolithic ERP, one solution for a huge enterprise- >> Who are you talking about? (Laughter) >> They are gone, those days are gone. I think it's about blended solutions where the ERP is much more agile, it has to be much more open and allow for much more agile deployments and much more agile development around the core ERP. So that actually customers can digitally transform, because it's all about speed. And TCS sees it the same way so we've got the same view. >> But the cloud mindset has changed that right Paul? >> Absolutely. And Rahul I'm interested the companies like Tata historically have done a lot of custom development work for customers that we have been hearing from Darren on down today is no customization. What value do you add to a customer bringing in an IFS solution? >> See there are two things here, very simple. One is basically customers are moving from best in class to the sub-breed, that's quite evident. And secondly, while IFS brings the software expertise, we bring the industry expertise. We bring the domain expertise. We bring the SI, system integration expertise. And that's where, it's a very strategic combination. Strategic combination is helping the customer to get the right software, the right domain expertise, the right industry expertise. And together they're helping them to address their business requirements, business need, and last mile critical mile needs that they need to differentiate themselves in the marketplace. And, as a result, create exponential value, and also, a great customer experience for the customers. >> Paul: So, how does that engage and differ from a more traditional one where you would come in and you would build custom screens and custom processes? You're not doing that. Now, what does that relationship look like? >> Yeah so I think if you see the scratch approach, obviously it has really transformed over the course of time. Customers are wanting off the shelf, out of the box products. Best of the beat products to help them differentiate their business function, create exponential value for the customer for that business function as a matter of say, service. If I look at fin services as an example, and you talk about telcos, you talk about utilities. Where last mile delivery, last mile solution for that customer is very very important to create the positive customer experience. And the investments that IFS have made in there makes them a premium choice. And that's where I believe that developing something with scratch means you know you're boarding the entire ocean again. And whereas we have got softwares like, IFS build softwares which have invested their years of expertise, the years of, I would say, competency in building that. Getting the best of the breed solution, get the best KPIs into there in this solution, gives the customer a choice. A ready choice to take, to expedite their time to reality, time to value, and time to production reality. >> So, a few times now, Raoul, you've mentioned last mile solutions. I like that term, I think it has meaning. Especially deep in specific industries. And I think the intent is so that you don't have to do customizations. And I asked Aaron about tailoring, which he said, I wouldn't use that word. That wasn't my word, by the way, that was Christian's word. He used that in his keynote. So I'm trying to understand here. I think what Christian meant is look, we got this API platform to allow people to bring in whatever solutions they want, if it's a RPA solution, or a blockchain solution, or some AI module, they can bring that in and tailor it for their needs, as opposed to customizing the software. Is that correct? >> I think when you listen to Darren, what he's talking about is customizing the core, which very often has happened in the past, where customizations have gone into the core, have been mandated to be on the core platform, which then actually has customers being stuck at some stage on the platform upgrades becoming paid for. So with Christian's talk track around the APIs, API enabling the whole solution so that the core actually remains untouched. There will always be customizations, because customers need to differentiate. But they will be outside the core. There will be a level that you can upgrade the core solutions, you will have those maintained either application services, which will be custom out of the box solutions, best in breed, that actually tap into what we're doing. Or actually you'll have bespoke solutions that you will write yourself, and that is then a choice a customer can make, but without actually having the pain of not being able to upgrade the very stable, very performant transactional backbone. >> So the API announcements give you guys a real opportunity to do integrations, right? And it's been harder to do integrations. But that now, to your previous question, opens up I would think a whole new tam for you all. Can you comment? >> Oh absolutely. As I said, bringing exponential value means integrating and delivering a frictionless business. And that's where it'll fit in, rightly fit in, and obviously that would result in creating exponential value for the customer. Not only they can differentiate themselves from the market but also get their product faster to the market, and ensure that also focus on custom centers as we are. >> So the core can be, it should be, Evergreen. We want people to get the new version as soon as possible. Bug fixes, security updates, et cetera. >> New functionality. >> New functionality, avoid custom mods, but rely on service providers and partners to do further integrations that make sense. >> Rahul, I want to ask you the same question we just asked Melissa Di Donato about digital transformation. I'm sure your company does a lot of that kind of consulting work. What are the mistakes that companies make that we hear that these transformation products, most of them fail. What are the biggest mistakes that companies make? >> Let me put it this way. I think there are three elements to it. I think digital transformation, see I think creating the agenda for the digital transformation, what you're expecting out of it is very very important. Creating a charter, what you want to expect, what is the output of it. Where do you want to take it. What does a futuristic organization on a digital platform means? It's very very important. I think if you look at TCS, our vision has been helping the customer get into a business 4.0 enterprise. I think we have made the agenda very very very clear. Now how we can mass personalize the experience for the customer, how you can leverage the ecosystem, how you can basically help the customer embrace the risk, and obviously harness the abundance. I believe these are the pillars of any transformation, or digital transformation, that customers are taking. I believe if we can stick to these agendas, I think getting to the production reality, seeing the success has become more evident. If you're going to go to the nitty gritty, I think there are many things, looking at the processes, making sure that they are harmonized, standardized and rationalized, getting the right KPIs in the business. So I think these are things that is very very important as a precursor to our digital transformation. Once we do that, we know that roads ahead will be much smoother than what it looks like. >> Is it more important to do a transformation with the customer at the center, with operational efficiency at the center, or can it be either? >> The customer centricity is very very key to all our organization at this point of time, because if you look at any organization at this point of time, they're looking at the customer experience as the top most agenda. Keeping the customer experience on the agenda, when you're trying to keep that agenda, it means that you are trying to bring up a customer first organization. So customer first organization, it just doesn't mean that you have a very intelligent front office, but also have a very intelligent back office. And gluing this two together, very intelligent mid office. So I guess customer centricity has to be on the top of the agenda, and then you have to ensure that your processes are streamlined, harmonized, standardized, lean, to meet that objective. >> Makes sense. >> So I think, for customer centricity, so I feel as though, but part of that's cultural, you know? And it's true, you said this earlier this morning. Some companies are customer centrics, some are product centric, some are competitive. And you can kind of tell the difference, especially when you're a customer. But I think true customer centricity mandates data access as central to the philosophy, the core. And I think the role that ERP provider or vendor provides is you have a data pipeline that gives access to an organization such that a digital transformation allows them to put data at their core, and then build whatever processes around it. I think that's a real challenge for incumbents especially where data's all over the place, in different stove pipes and silos. But your thoughts on the role of data in terms of digital transformation, and IFS's role in that regard? >> Okay. >> A long-winded question, but I haven't heard enough about data I guess. >> Okay, (laughs) I'll try it, sweet and short. I think data is absolutely key to anything we do. Once you have and when you go into a digital transformation, what you need to start with in my humble view is you need to start with what business outcome do you want to achieve? Most of the time it's customer centricity, it's something centered around the customer which you want to achieve. That will define both the digital transformation agenda, the KPI's you're measuring to, but also the flow of data and processes. So you will need to build your digital transformation agenda around the targets you have, and then define where does data need to reside, which data do I need to fulfill on that outcome? And I think that consistency going through that whole chain is actually something that very often isn't at the moment taken into account, but it's very often isolated efforts to do something fast without actually looking at the implications of what kind of transactional engine do I need, what kind of data exits do I need, and how do I get through the process to the KPI that I want to influence? >> Okay, and let me peel the onion on that, and I'd love for your thoughts. To me when you talk to a C-suite executive, what that business outcome ultimately comes down to is I want to increase revenue, so I want to cut my cost. Now of course if you're in a different hospital, you want to save lives. But generally in a commercial business, increase revenue, cut cost. Now how I get there, I might want to have a better customer service organization to get cohort sales or follow on sales. I mean the strategy is different. But it comes back to data and how data affects the monetization of my organization, whether it's increasing revenue or cutting cost. Do you buy that premise, or am I just simplifying it too much? >> No, completely agreed. I think in a business world it's always either top line or bottom line, but the challenges are obviously very different from company to company and from industry to industry. So if you're looking at manufacturing companies, trying to actually be less commoditized and getting into a situation where they stabilize revenue streams, increase margins, servitization is the name of the game. Very different value proposition to, for example in the finance industry, in banking and insurance. So there are very different models here where there it's about ease of use and speed of actually interacting and transacting as a customer with the company. So very different value propositions, very different data streams you need to tap into. And things you need to know about your customer, and know about the service you're providing. So completely agree with it is always about revenue and cost, that's what businesses are in for. But eventually, data is at the core, but how to get that data, which data you need, that is then specific to each. >> And bringing it back to IFS, your ability to go that last mile as you've been saying Rahul allows companies to think, construction and engineering, supply chain, contractors, just more efficiently managing their ecosystem, their resources to either cut costs or do more business and scale. >> Exactly. And that's really where the whole idea of API, enabling the whole suite came from, enabling the reuse of services, the reuse of data within those services, exposing it transparently, making it available for customers to then use in their digital transformation effort. Whatever they need. We can't predict and we can't actually preempt what a customer will need, we'll just need to make it all available, and then with partners like TCS, make sure we actually go on to the right journey with a customer to digitally transform and use the right data streams. We can make it easy and accessible. >> And that's the different between a platform and a product. To the extent that you can deliver an API-enabled system, it becomes a platform that you can evolve versus a product that you install and manage. Final thoughts, Rahul? >> I think what we discussed obviously, I fully agree on that. And as I mentioned that our take is to ensure that we have the customer built future systems enterprises, and we believe our partnership with IFS is a very key and strategic partnership for us to achieve the same, and we have some early success, and we want to ensure that we scale that, we ensure we go to the market together, and create a differentiation for our customers. >> Michael, your thoughts. Where do you want to see this ecosystem go? >> Where do I want to see it go? Well I want to see it thrive. I want partners to be successful with their customers on IFS implementations. That's what our ambition is. We need to provide world class technology, a world class platform, as you said, that actually then can be used to help the digital transformation that all our customers will have to go through in one or the other way. >> Success is outcome driven. Good outcomes mean people come back, more business? >> Absolutely, absolutely. >> Exactly. >> That's core to our DNA, I'm sure core to DNA to IFS as well. Repeat customers. >> Congratulations on the partnerships, and good luck going forward. >> Thank you very much. >> Appreciate you coming on theCUBE, you're welcome. >> Thank you very much. >> Thank you. >> All right thank you for watching everybody, we'll be right back with our next guest, Paul Gillan and Dave Vellante. You're watching theCUBE. (electronic jingle)

>> live from Boston, Massachusetts. It's the you covering your red hat. Some twenty nineteen >> rots. >> You buy bread >> hat, >> and we'LL go back here on the Cube as we continue our coverage here. Red Hat Summit day. One of three days of Walter Wall coverage coming to you exclusively here on the Q. I'm John Walls was too Millman. Thank you for joining us. And we're now joined by a couple of gentlemen. Guess the dynamic duo of the container World it at Red Hat. Scott McCarty is the principal product manager of Containers. That open shift and Forell. Scott. Good to see you, sir. >> You could see it >> and been. Bree are Who's the principal product? Manager of Containers and Koro s, Of course. Also it Red hat Been. Thank you for joining us. First off, just your thought about show. Obviously, there's a lot of educational programming going on up down, big crowds, a lot of buzz. Good activity day one, at least from our perspective. How are you guys seeing this so far? >> I love it. I mean, it's been great so far. We just had us. I just had a session, just got out of it. was completely full of people trying to get in that were lined up against a wall. So it's been very exciting so far. >> Yeah. Ben. So it's one of >> my favorite times of the year, right? It's so much energy. Everybody comes with the exchange of ideas, just feedback and everything is one of my favorites. >> Oh, good. Right now s o l e made available publicly today for the first time. We talked about that a lot so far on the program, I'd like to hear from >> your side of the fence. Then what does that mean to you in terms of the container world and the impact that you, you know, from here going forward, you've got a whole new world of concern, I would think Scott. >> Yeah. I mean, with the relic, it's it's >> exciting because we're releasing, uh, you know, a lot of new tools around containers, >> a ton of new operational, you know, management capabilities. I mean, it's just it's an exciting release, Ben. It's a It's a big step forward, right? Every single release is a big deal, and we look at the container space. It's evolved a lot in the past for five years right when we came out. Seven. So technology's matured, Really, it's Ah, it's a smooth, easy experience to get to the release. And if lots going into it a lot, >> Yeah, so, Scott, It's funny. I think back. Turn back. Five years ago, we had a lot of jokes about doctors. You mean the pants? Because container ization and, you know, limits, containers and everything. That was something most people hadn't heard about here. Twenty nineteen, You said, There's, you know, crowds trying to get in the door. And it's not what but there really digging in and understand the tools we give a little bit of. You know what? What's what's with the excitement these days? Where are the customers? And you know what? What do you digging into >> with them? Yeah, well ah, >> funny example. So I asked I asked this last session, You know, raise your hand if you've used containers. If you just even fired up a container before and everyone raise your hand. And now, five years ago, that was, like one person >> and then even last you worked for Google. Yeah. Even last >> year that it was still maybe forty percent of the people, and now it's one hundred percent when they come to a session. So I mean, it's it is it is definitely changed, a tremendous amount. And now it's about So I joked, You know, five years ago is about using a chef knife, you know, just like you cut everything with it, right? You cut it. Vegetables, meat, whatever. And there was like one thing, and you just figured out Doctor and Cooper names was even on the radar Yet now it's about refining all the tools and getting to a place where, like, it's really getting excited, cause now we have special paring knives and chef knife and, you know, hibachi, knife and all these different, more specialized >> tools. So it's getting saying >> You think it's easy to >> adopt now to write, because years ago everyone was hedging their bets on you know what orchestration am I going to use? What piece? Um, I'm gonna build my stack. We have >> now. It's much, much clear, well defined. You know, Cooper Netease is dominant factor, right? Mean, open shift is huge, huge growth for us in that space. So I mean, it's it's it's a lot easier for customers to get in that game now than it was, you know? Yeah, just a couple years ago. Yeah, just a couple years ago. All right, so let's let's sticking out security a little bit because that was one of the big question marks in the early days. And you know something? We talk about it all the shows. It's it's definitely a focus of the real late launch. So where were the container world today and anything new or nuance that the audience should understand? I think on the security side you've got I have three or four big points there. One is the container tools of worshipping. Today they basically inherit the full Lennox security model. Right? So no longer do you have ah, privilege socket. That is, I kind of that weak factor, if you will, that's gone on. Really? So that's a big That's a big win right there. Beyond that, we've got a new crystal policies. You can set a central policy for the O. S. And that works in the containers well, so of you and enforce a particular kind of floor, if you will, of crypto. You could do that with relate for the host way and images as well. That's a that's a big part of it. And then we also have new tools that you can build smaller containers because how did the security is what is in my container? So if you're putting less less packages and content in that image, that's a much smaller Becker as well. Soon. >> Yeah. So, um, from from a security perspective, too, you know, you know the fact that now we have, um, kind of we've got a set of tools now that we can do experiments with things like ruthless, for example. You know, we're tech preview release of ruthless contract, so historically have always ran them, you know, as route. That's just how it works. I mean, we kind of figured it out one way and did it, and it was cool. And then at a certain point, we went all right, we need these other use cases where want developers to build to do it. For example, I just talked to a customer that it has four two hundred. I'm sorry, developers that are all running instances on their laptops PM's with pod man and build a running and, you know, using these tools to actually build containers, and they want to do ruthless bad. They want to do it in all their essentially all their environment, so that people are really hungry for a lot of these security features that we're working on now and relate. And it's something that we're releasing even as a vato. >> How did the capabilities changed in terms of relate now and what you have to provide the support? So what's transformed? And then what will be the need in order to build on that toe work on that and to make it more secure stables on so >> far? Well, I think I think you kind of have to dig into, like, a selection of what tools we decided to go in. Relate you'LL see that it's pod man. Build a scope. Here are the three main lower level tools that we have, and those tools are built serving a Unix mindset where it's like you can pipe things together and do things and use them collaboratively together to go remotely inspect images, pull them, build them from scratch, you know, run them locally, not as roots run them as a non route, contains things like that way or not at, you know, we're not releasing doctrine. Relate. And so so the transition. There is probably the biggest transition for users. Kind of realizing. Okay, we're going kind of broken this apart into three little or tools that we can then use Todd Man being the main one you go to. And then and then it's got a command line that's very similar. And so it's very easy, tio kind of transition over. But then you start to again kind of my my chef knife reference. You realize once you transition from, say, Dr Pod man, you kind of that's your chef knife. You kind of know what? How to start doing things that way. But then you start to get more refined and start to dig deeper into, you know, like, you know, into building scope. You essentially teacher. Yeah. >> You're good there. Yeah. I don't know. All right. Whatever he says. Scott >> Universal base image. Something we've talked a little bit about to tell us how that this is going to impact, you know, talk about everybody building things on their laptop. Seems like that's an extension of where this fits. Help help us understand? >> Yeah, I can't hide my enthusiasm. One how excited I am by Eva, and I will admit Ivory had a couple people come to me and say, This is the most exciting thing for me at Summit period And I think that's interesting because it's not actually something new and that, you would say from a technology perspective, how exciting is that? I don't know, but like it allows a set of collaboration that we've never been able to like, really, really do with a well base image historically, and I think the real base image is the highest quality basement temperament out there. But the problem is, even if you had something really simple, like so you had one university and that created some kind of science experiment in a container, and then they want to push that out to a public registry, then pull it down a different university and share it. They couldn't do that under the terms of the rail base image. So that was that. Was that create a little bit of friction with the FBI? Now that's completely gone. You can now run it anywhere you want, distribute anywhere you want, just the distribution alone is exciting. It and the fact that when you >> run it on rail, you >> build on rail, run on relics completely supported Israel. But you can now push it out to a public registry and let it sit out there and other people can >> use it in an experiment. So is the, you know, coming together of container ization in that distribution is that would kind of is really new with this, as opposed to the ways that I used to be able to share lennox images in the past. >> Well, all I think I think the challenge was you'd have some people that would want to do something. They want to build a distributed anywhere they want have that freedom. But they still wanted the quality of the rail basement. Now that created friction, right? So then they'd have to make an unnatural choice between, like, a fedora or I use, you know, well, maybe how you sent to less and your lying and none of those have all the things that I want, right? It was like a card game trying to get all the components that you want. You want sport, ability of Raoul. You want the security of the performance center center. But you couldn't. You couldn't distribute anywhere, so that created friction where you make on natural choices on basement. Now you be. I just The name implies that universal use it for anything you want. >> Same for communities to write because they don't want to make one that could freely distribute and then another like supported variant. They have more to maintain its more cycles and everything so simple. Find that it is a big deal. Yeah, >> and migration between base images is a linen migration, so it's frustrating to do. You don't want to do it. You want to build on one thing. And then I thought I distribute that thing anywhere. Well, then it's >> interesting, you know, go back a few years. There was this big movement to do, like just enough OS. How do I slim down the core? Os was I don't need everything that you know Realm necessarily does. So have we gotten over that? And we now gotten with you know, the things like you be I down to like a nice unit that's easily terrible and distributed. It's a good question. It's a topic that we'LL never go away. I don't think we're still. It's just changing its form, right? It still exists on the host. It's still exists in images. It's still exist with unit colonels and everything. I >> think where we >> are today. That was a really good spot, right? We've got several footprints of FBI. If there's several footprints of Rehl, including well, Core OS, which is like bedded version of rail into open shift right for a small form factor container host. So where we are today is very strong, but it's going to continue to evolve and get better. So, yeah, >> and we I mean, we look at the future and we're we're looking at ways toe. Make it even smaller, you know, you're always looking at, but yeah, Ben, mention there's three footprints of you B i today. There's a minimal image. There's a standard image, and then there's even a little bit bigger images allows you run multiple services, but you know that's the selection today. But in the future, we're looking at making the minimal one more minimal. Were even looking at, you know, making the standard one more minimal. >> Yeah, we're not done. Yeah, we're not done. You're never done. I guess the last thing I have on this, you know, multi cloud is such you know where customers are today. You know, you're gonna have the CEO Microsoft up on stage today. Two years ago, when I was here, it was the partnership between Red had an eight of us was all the discussion. I spoke to the Red Hat team, the Cloud show recently. So how does the tooling that you have fit in tow all the clouds discussion that I have when I talked to users? You know, one of the biggest lock ins they have is the skill set and the understanding of different tools and knowledge. And so you know, where we standardize and where do we still have work to do in this space? That's a big question. So yeah, I guess way addressing a multiple levels right at the core. The center Israel. Right. So well ate right now today on all those cloud platforms that you just name, right. So same say maybe I level guarantee that ten years hard work everything. It's it's everywhere. It's pervasive today. Level up, right. You've got the container images and stuff same story. They're Goa level. You've got open shift that is pervasive everywhere. And now we're doing really cool things. And Cooper Net. He's like a machine, a p I and all these other things toe actually control those individual cloud infrastructures which abstracts all of the customers ations per for food for him, which is >> powerful. So I think, for me was the most exciting things is the open shift for paradigm shift that shift from managing individual nodes to ship to managing the cluster as a computer, which we've said for what, twenty years? The sun? I think you know the cluster is the computer, you know? But we're really there today. Like we have a single E p I. Ben mention the machine, the machine, a PR machine configure operator. There's there's essentially automation built into the chip platform now that allows you to appoint the same on any cloud. So eight of us azure, you know, open stack, even on VM, where even on, you know, even in liver gonna look a laptop. There's a way to deploy it in the identical, you know, in an identical configuration. To me, that's exciting, because now I have one set of things I could learn. And then again in the standard red hat way. If you feel locked in, you can go use a Okay, Daddy, you can use the upstream. So you're never locked into our product, Which that's something. Get a lot with Kat drives, right? Like if you're locked in there, you're you're locked in there. There's no there's no, you know, open source version of that to get out of that. >> So you've talked about growth opportunities? You said, No, we're not done yet. Making the joke about your own work. You've talked about a twenty year evolution, you know, Just refer to that. And if you could look, you know, whether it's three, four, five, whatever years down the road, where's the big leap? Where's that have to come? Where do you think it's going to come in terms of the capabilities that you want to work on and what you want to be able to deliver from where you are right? Now >> get my crystal ball. Yeah. >> Yeah, Well, I think you've got one. Yeah. Then I have a lot of confidence in you, but if you had to say okay, this is this is atleast where we're gonna be. We're gonna have to spend a lot of our time because this this is the area that we think I think needs most attention. A >> couple of things, right? People only scale so much. So automation is an area that's bulletproof going forward, and it's going to evolve and take many forms. Right now, our big push has been on the operator space and obviously technologies like answerable that's going to continue to evolve and make make people scale better. That's probably one of the biggest ones. And I >> think that's one of the biggest ones. I think I think for me, probably where my mind wanders, is around partners and building that ecosystem in the open ship space similar to what you see in the realm. Because system today I think three, four years from now you're going to see it really exploded at ABC that I already see it exploding. But by then you'LL see it maturing and you'LL really see. I think if you look at the operator paradigm, I'm very excited by that because it's kind of like the Emma science dollar that Microsoft invented. You know that kind of made that that ubiquitous that install experience. Except that operators make it you because they install and managed a too. So I think, like, kind of to his point of, like making that the install really simple and then the operation of it. Over time, I think you're going to see a lot of I think. I think you couldn't fill a room and ask him, Like what I in fact, I did. I asked what an operator was, you know, and they they weren't super aware of it yet. But I think in the next five years, that will become the big with this way of just installing software. >> All right, well, we're going to check back in five. We'LL see how it turns out and been by then. Bring that crystal ball back with wood. Ok, I'll do a good deal. Thanks, gentlemen. Thanks for the time you haven't put on the Cuba as we continue our coverage here. Red Hat Summit. We're in Boston back with more right after this