>>mhm Yes. >>Welcome back to the Cube coverage of Red Hat summit 21 2021. I'm john for host of the Cubans virtual this year as we start preparing to come out of Covid a lot of great conversations here happening around technology. This is the emerging technology with Red hat segment. We've got three great guests steve watt manager, distinguished engineer at Red Hat hurl saying senior software engineer Red Hat and luke Hines, who's the senior software engineer as well. We got the engineering team steve, you're the the team leader, emerging tech within red hat. Always something to talk about. You guys have great tech chops that's well known in the industry and I'll see now part of IBM you've got a deep bench um what's your, how do you view emerging tech um how do you apply it? How do you prioritize, give us a quick overview of the emerging tech scene at Redhead? >>Yeah, sure. It's quite a conflated term. The way we define emerging technologies is that it's a technology that's typically 18 months plus out from commercialization and this can sometimes go six months either way. Another thing about it is it's typically not something on any of our product roadmaps within the portfolio. So in some sense, it's often a bit of a surprise that we have to react to. >>So no real agenda. And I mean you have some business unit kind of probably uh but you have to have first principles within red hat, but for this you're looking at kind of the moon shot, so to speak, the big game changing shifts. Quantum, you know, you got now supply chain from everything from new economics, new technology because that kind of getting it right. >>Yeah, I think we we definitely use a couple of different techniques to prioritize and filter what we're doing. And the first is something will pop up and it will be like, is it in our addressable market? So our addressable market is that we're a platform software company that builds enterprise software and so, you know, it's got to be sort of fit into that is a great example if somebody came up came to us with an idea for like a drone command center, which is a military application, it is an emerging technology, but it's something that we would pass on. >>Yeah, I mean I didn't make sense, but he also, what's interesting is that you guys have an open source D N A. So it's you have also a huge commercial impact and again, open sources of one of the 4th, 5th generation of awesomeness. So, you know, the good news is open source is well proven. But as you start getting into this more disruption, you've got the confluence of, you know, core cloud, cloud Native, industrial and IOT edge and data. All this is interesting, right. This is where the action is. How do you guys bring that open source community participation? You got more stakeholders emerging there before the break down, how that you guys manage all that complexity? >>Yeah, sure. So I think that the way I would start is that, you know, we like to act on good ideas, but I don't think good ideas come from any one place. And so we typically organize our teams around sort of horizontal technology sectors. So you've got, you know, luke who's heading up security, but I have an edge team, cloud networking team, a cloud storage team. Cloud application platforms team. So we've got these sort of different areas that we sort of attack work and opportunities, but you know, the good ideas can come from a variety of different places. So we try and leverage co creation with our customers and our partners. So as a good example of something we had to react to a few years ago, it was K Native right? So the sort of a new way of doing service um and eventing on top of kubernetes that was originated from google. Whereas if you look at Quantum right, ibms, the actual driver on quantum science and uh that originated from IBM were parole. We'll talk about exactly how we chose to respond to that. Some things are originated organically within the team. So uh luke talking about six law is a great example of that, but we do have a we sort of use the addressable market as a way to sort of focus what we're doing and then we try and land it within our different emerging technologies teams to go tackle it. Now. You asked about open source communities, which are quite interesting. Um so typically when you look at an open source project, it's it's there to tackle a particular problem or opportunity. Sometimes what you actually need commercial vendors to do is when there's a problem or opportunity that's not tackled by anyone open source project, we have to put them together to create a solution to go tackle that thing. That's also what we do. And so we sort of create this bridge between red hat and our customers and multiple different open source projects. And this is something we have to do because sometimes just that one open source project doesn't really care that much about that particular problem. They're motivated elsewhere. And so we sort of create that bridge. >>We got two great uh cohorts here and colleagues parole on the on the Quantum side and you got luke on the security side. Pro I'll start with you. Quantum is also a huge mentioned IBM great leadership there. Um Quantum on open shift. I mean come on. Just that's not coming together for me in my mind, it's not the first thing I think of. But it really that sounds compelling. Take us through, you know, um how this changes the computing landscape because heterogeneous systems is what we want and that's the world we live in. But now with distributed systems and all kinds of new computing modules out there, how does this makes sense? Take us through this? >>Um yeah john's but before I think I want to explain something which is called Quantum supremacy because it plays very important role in the road map that's been working on. So uh content computers, they are evolving and they have been around. But right now you see that they are going to be the next thing. And we define quantum supremacy as let's say you have any program that you run or any problems that you solve on a classical computer. Quantum computer would be giving you the results faster. So that is uh, that is how we define content supremacy when the same workload are doing better on content computer than they do in a classical computer. So the whole the whole drive is all the applications are all the companies, they're trying to find avenues where Quantum supremacy are going to change how they solve problems or how they run their applications. And even though quantum computers they are there. But uh, it is not as easily accessible for everyone to consume because it's it's a very new area that's being formed. So what, what we were thinking, how we can provide a mechanism that you can you don't connect this deal was you have a classical world, you have a country world and that's where a lot of thought process been. And we said okay, so with open shift we have the best of the classical components. You can take open shift, you can develop, deploy around your application in a country raised platform. What about you provide a mechanism that the world clothes that are running on open shift. They are also consuming quantum resources or they are able to run the competition and content computers take the results and integrate them in their normal classical work clothes. So that is the whole uh that was the whole inception that we have and that's what brought us here. So we took an operator based approach and what we are trying to do is establish the best practices that you can have these heterogeneous applications that can have classical components. Talking to our interacting the results are exchanging data with the quantum components. >>So I gotta ask with the rise of containers now, kubernetes at the center of the cloud native value proposition, what work clothes do you see benefiting from the quantum systems the most? Is there uh you guys have any visibility on some of those workloads? >>Uh So again, it's it's a very new, it's very it's really very early in the time and uh we talk with our customers and every customers, they are trying to identify themselves first where uh these contacts supremacy will be playing the role. What we are trying to do is when they reach their we should have a solution that they that they could uh use the existing in front that they have on open shift and use it to consume the content computers that may or may not be uh, inside their own uh, cloud. >>Well I want to come back and ask you some of the impact on the landscape. I want to get the look real quick because you know, I think security quantum break security, potentially some people have been saying, but you guys are also looking at a bunch of projects around supply chain, which is a huge issue when it comes to the landscape, whether its components on a machine in space to actually handling, you know, data on a corporate database. You guys have sig store. What's this about? >>Sure. Yes. So sick store a good way to frame six store is to think of let's encrypt and what let's encrypt did for website encryption is what we plan to do for software signing and transparency. So six Door itself is an umbrella organization that contains various different open source projects that are developed by the Six door community. Now, six door will be brought forth as a public good nonprofit service. So again, we're very much basing this on the successful model of let's Encrypt Six door will will enable developers to sign software artifacts, building materials, containers, binaries, all of these different artifacts that are part of the software supply chain. These can be signed with six door and then these signing events are recorded into a technology that we call a transparency log, which means that anybody can monitor signing events and a transparency log has this nature of being read only and immutable. It's very similar to a Blockchain allows you to have cryptographic proof auditing of our software supply chain and we've made six stores so that it's easy to adopt because traditional cryptographic signing tools are a challenge for a lot of developers to implement in their open source projects. They have to think about how to store the private keys. Do they need specialist hardware? If they were to lose a key then cleaning up afterwards the blast radius. So the key compromise can be incredibly difficult. So six doors role and purpose essentially is to make signing easy easy to adopt my projects. And then they have the protections around there being a public transparency law that could be monitored. >>See this is all about open. Being more open. Makes it more secure. Is the >>thief? Very much yes. Yes. It's that security principle of the more eyes on the code the better. >>So let me just back up, is this an open, you said it's gonna be a nonprofit? >>That's correct. Yes. Yes. So >>all of the code is developed by the community. It's all open source. anybody can look at this code. And then we plan alongside the Linux Foundation to launch a public good service. So this will make it available for anybody to use if your nonprofit free to use service. >>So luke maybe steve if you can way into on this. I mean, this goes back. If you look back at some of the early cloud days, people were really trashing cloud as there's no security. And cloud turns out it's a more security now with cloud uh, given the complexity and scale of it, does that apply the same here? Because I feel this is a similar kind of concept where it's open, but yet the more open it is, the more secure it is. And then and then might have to be a better fit for saying I. T. Security solution because right now everyone is scrambling on the I. T. Side. Um whether it's zero Trust or Endpoint Protection, everyone's kind of trying everything in sight. This is kind of changing the paradigm a little bit on software security. Could you comment on how you see this playing out in traditional enterprises? Because if this plays out like the cloud, open winds, >>so luke, why don't you take that? And then I'll follow up with another lens on it which is the operate first piece. >>Sure. Yes. So I think in a lot of ways this has to be open this technology because this way we have we have transparency. The code can be audited openly. Okay. Our operational procedures can be audit openly and the community can help to develop not only are code but our operational mechanisms so we look to use technology such as cuba netease, open ship operators and so forth. Uh Six store itself runs completely in a cloud. It is it is cloud native. Okay, so it's very much in the paradigm of cloud and yeah, essentially security, always it operates better when it's open, you know, I found that from looking at all aspects of security over the years that I've worked in this realm. >>Okay, so just just to add to that some some other context around Six Law, that's interesting, which is, you know, software secure supply chain, Sixth floor is a solution to help build more secure software secure supply chains, more secure software supply chain. And um so um there's there's a growing community around that and there's an ecosystem of sort of cloud native kubernetes centric approaches for building more secure software. I think we all caught the solar winds attack. It's sort of enterprise software industry is responding sort of as a whole to go and close out as many of those gaps as possible, reduce the attack surface. So that's one aspect about why 6th was so interesting. Another thing is how we're going about it. So we talked about um you mentioned some of the things that people like about open source, which is one is transparency, so sunlight is the best disinfectant, right? Everybody can see the code, we can kind of make it more secure. Um and then the other is agency where basically if you're waiting on a vendor to go do something, um if it's proprietary software, you you really don't have much agency to get that vendor to go do that thing. Where is the open source? If you don't, if you're tired of waiting around, you can just submit the patch. So, um what we've seen with package software is with open source, we've had all this transparency and agency, but we've lost it with software as a service, right? Where vendors or cloud service providers are taking package software and then they're making it available as a service but that operationalize ng that software that is proprietary and it doesn't get contributed back. And so what Lukes building here as long along with our partners down, Lawrence from google, very active contributor in it. Um, the, is the operational piece to actually run sixth or as a public service is part of the open source project so people can then go and take sixth or maybe run it as a smaller internal service. Maybe they discover a bug, they can fix that bug contributed back to the operational izing piece as well as the traditional package software to basically make it a much more robust and open service. So you bring that transparency and the agency back to the SAS model as well. >>Look if you don't mind before, before uh and this segment proportion of it. The importance of immune ability is huge in the world of data. Can you share more on that? Because you're seeing that as a key part of the Blockchain for instance, having this ability to have immune ability. Because you know, people worry about, you know, how things progress in this distributed world. You know, whether from a hacking standpoint or tracking changes, Mutability becomes super important and how it's going to be preserved in this uh new six doorway. >>Oh yeah, so um mutability essentially means cannot be changed. So the structure of something is set. If it is anyway tampered or changed, then it breaks the cryptographic structure that we have of our public transparency service. So this way anybody can effectively recreate the cryptographic structure that we have of this public transparency service. So this mutability provides trust that there is non repudiation of the data that you're getting. This data is data that you can trust because it's built upon a cryptographic foundation. So it has very much similar parallels to Blockchain. You can trust Blockchain because of the immutable nature of it. And there is some consensus as well. Anybody can effectively download the Blockchain and run it themselves and compute that the integrity of that system can be trusted because of this immutable nature. So that's why we made this an inherent part of Six door is so that anybody can publicly audit these events and data sets to establish that there tamper free. >>That is a huge point. I think one of the things beyond just the security aspect of being hacked and protecting assets um trust is a huge part of our society now, not just on data but everything, anything that's reputable, whether it's videos like this being deep faked or you know, or news or any information, all this ties to security again, fundamentally and amazing concepts. Um I really want to keep an eye on this great work. Um Pearl, I gotta get back to you on Quantum because again, you can't, I mean people love Quantum. It's just it feels like so sci fi and it's like almost right here, right, so close and it's happening. Um And then people get always, what does that mean for security? We go back to look and ask them well quantum, you know, crypto But before we get started I wanted, I'm curious about how that's gonna play out from the project because is it going to be more part of like a C. N. C. F. How do you bring the open source vibe to Quantum? >>Uh so that's a very good question because that was a plan, the whole work that we are going to do related to operators to enable Quantum is managed by the open source community and that project lies in the casket. So casket has their own open source community and all the modification by the way, I should first tell you what excuse did so cute skin is the dedicate that you use to develop circuits that are run on IBM or Honeywell back in. So there are certain Quantum computers back and that support uh, circuits that are created using uh Houston S ticket, which is an open source as well. So there is already a community around this which is the casket. Open source community and we have pushed the code and all the maintenance is taken care of by that community. Do answer your question about if we are going to integrate it with C and C. F. That is not in the picture right now. We are, it has a place in its own community and it is also very niche to people who are working on the Quantum. So right now you have like uh the contributors who who are from IBM as well as other uh communities that are specific specifically working on content. So right now I don't think so, we have the map to integrated the C. N. C. F. But open source is the way to go and we are on that tragic Torri >>you know, we joke here the cube that a cubit is coming around the corner can can help but we've that in you know different with a C. But um look, I want to ask you one of the things that while you're here your security guru. I wanted to ask you about Quantum because a lot of people are scared that Quantum is gonna crack all the keys on on encryption with his power and more hacking. You're just comment on that. What's your what's your reaction to >>that? Yes that's an incredibly good question. This will occur. Okay. And I think it's really about preparation more than anything now. One of the things that we there's a principle that we have within the security world when it comes to coding and designing of software and this aspect of future Cryptography being broken. As we've seen with the likes of MD five and Sha one and so forth. So we call this algorithm agility. So this means that when you write your code and you design your systems you make them conducive to being able to easily swap and pivot the algorithms that use. So the encryption algorithms that you have within your code, you do not become too fixed to those. So that if as computing gets more powerful and the current sets of algorithms are shown to have inherent security weaknesses, you can easily migrate and pivot to a stronger algorithms. So that's imperative. Lee is that when you build code, you practice this principle of algorithm agility so that when shot 256 or shot 5 12 becomes the shar one. You can swap out your systems. You can change the code in a very least disruptive way to allow you to address that floor within your within your code in your software projects. >>You know, luke. This is mind bender right there. Because you start thinking about what this means is when you think about algorithmic agility, you start thinking okay software countermeasures automation. You start thinking about these kinds of new trends where you need to have that kind of signature capability. You mentioned with this this project you're mentioning. So the ability to actually who signs off on these, this comes back down to the paradigm that you guys are talking about here. >>Yes, very much so. There's another analogy from the security world, they call it turtles all the way down, which is effectively you always have to get to the point that a human or a computer establishes that first point of trust to sign something off. And so so it is it's a it's a world that is ever increasing in complexity. So the best that you can do is to be prepared to be as open as you can to make that pivot as and when you need to. >>Pretty impressive, great insight steve. We can talk for hours on this panel, emerging tech with red hat. Just give us a quick summary of what's going on. Obviously you've got a serious brain trust going on over there. Real world impact. You talk about the future of trust, future of software, future of computing, all kind of going on real time right now. This is not so much R and D as it is the front range of tech. Give us a quick overview of >>Yeah, sure, yeah, sure. The first thing I would tell everyone is go check out next that red hat dot com, that's got all of our different projects, who to contact if you're interested in learning more about different areas that we're working on. And it also lists out the different areas that we're working on, but just as an overview. So we're working on software defined storage, cloud storage. Sage. Well, the creator of Cf is the person that leads that group. We've got a team focused on edge computing. They're doing some really cool projects around um very lightweight operating systems that and kubernetes, you know, open shift based deployments that can run on, you know, devices that you screw into the sheet rock, you know, for that's that's really interesting. Um We have a cloud networking team that's looking at over yin and just intersection of E B P F and networking and kubernetes. Um and then uh you know, we've got an application platforms team that's looking at Quantum, but also sort of how to advance kubernetes itself. So that's that's the team where you got the persistent volume framework from in kubernetes and that added block storage and object storage to kubernetes. So there's a lot of really exciting things going on. Our charter is to inform red hats long term technology strategy. We work the way my personal philosophy about how we do that is that Red hat has product engineering focuses on their product roadmap, which is by nature, you know, the 6 to 9 months. And then the longer term strategy is set by both of us. And it's just that they're not focused on it. We're focused on it and we spend a lot of time doing disambiguate nation of the future and that's kind of what we do. We love doing it. I get to work with all these really super smart people. It's a fun job. >>Well, great insights is super exciting, emerging tack within red hat. I'll see the industry. You guys are agile, your open source and now more than ever open sources, uh, product Ization of open source is happening at such an accelerated rate steve. Thanks for coming on parole. Thanks for coming on luke. Great insight all around. Thanks for sharing. Uh, the content here. Thank you. >>Our pleasure. >>Thank you. >>Okay. We were more, more redhead coverage after this. This video. Obviously, emerging tech is huge. Watch some of the game changing action here at Redhead Summit. I'm john ferrier. Thanks for watching. Yeah.

>>mhm Yes, Welcome back to the cubes coverage of red hat summit 2021 virtual, which we were in person this year but we're still remote. We still got the Covid coming around the corner. Soon to be in post. Covid got a great guest here, Clayton Coleman architect that red hat cuba love and I've been on many times expanded role again this year. More cloud, more cloud action. Great, great to see you. Thanks for coming on. >>It's a pleasure >>to be here. So great to see you were just riffing before we came on camera about distributed computing uh and the future of the internet, how it's all evolving, how much fun it is, how it's all changing still. The game is still the same, all that good stuff. But here at Red had some and we're gonna get into that, but I want to just get into the hard news and the real big, big opportunities here you're announcing with red hat new managed cloud services portfolio, take us through that. >>Sure. We're continuing to evolve our open shift managed offerings which has grown now to include um the redhead open shift service on amazon to complement our as your redhead open shift service. Um that means that we have um along with our partnership on IBM cloud and open ship dedicated on both a W S and G C P. We now have um managed open shift on all of the major clouds. And along with that we are bringing in and introducing the first, I think really the first step what we see as uh huh growing and involving the hybrid cloud ecosystem on top of open shift and there's many different ways to slice that, but it's about bringing capabilities on top of open shift in multiple environments and multiple clouds in ways that make developers and operation teams more productive because at the heart of it, that's our goal for open shift. And the broader, open source ecosystem is do what makes all of us safer, more, uh, more productive and able to deliver business value? >>Yeah. And that's a great steak you guys put in the ground. Um, and that's great messaging, great marketing, great value proposition. I want to dig into a little bit with you. I mean, you guys have, I think the only native offering on all the clouds out there that I know of, is that true? I mean, you guys have, it's not just, you know, you support AWS as your and I B M and G C P, but native offerings. >>We do not have a native offering on GCPD offered the same service. And this is actually interesting as we've evolved our approach. You know, everyone, when we talk about hybrid, Hybrid is, um, you know, dealing with the realities of the computing world, We live in, um, working with each of the major clouds, trying to deliver the best immigration possible in a way that drives that consistency across those environments. And so actually are open shift dedicated on AWS service gave us the inspiration a lot of the basic foundations for what became the integrated Native service. And we've worked with amazon very closely to make sure that that does the right thing for customers who have chosen amazon. And likewise, we're trying to continue to deliver the best experience, the best operational reliability that we can so that the choice of where you run your cloud, um, where you run your applications, um, matches the decisions you've already made and where your future investments are gonna be. So we want to be where customers are, but we also want to give you that consistency. That has been a hallmark of um of open shift since the beginning. >>Yeah. And thanks for clarifying, I appreciate that because the manage serves on GCB rest or native. Um let me ask about the application services because Jeff Barr from AWS posted a few weeks ago amazon celebrated their 15th birthday. They're still teenagers uh relatively speaking. But one comment he made that he that was interesting to me. And this applies kind of this cloud native megatrend happening is he says the A. P. I. S are basically the same and this brings up the hybrid environment. You guys are always been into the api side of the management with the cloud services and supporting all that. As you guys look at this ecosystem in open source. How is the role of A PS and these integrations? Because without solid integration all these services could break down and certainly the open source, more and more people are coding. So take me through how you guys look at these applications services because many people are predicting more service is going to be on boarding faster than ever before. >>It's interesting. So um for us working across multiple cloud environments, there are many similarities in those mps, but for every similarity there is a difference and those differences are actually what dr costs and drive complexity when you're integrating. Um and I think a lot of the role of this is, you know, the irresponsible to talk about the role of an individual company in the computing ecosystem moving to cloud native because as many of these capabilities are unlocked by large cloud providers and transformations in the kinds of software that we run at scale. You know, everybody is a participant in that. But then you look at the broad swath of developer and operator ecosystem and it's the communities of people who paper over those differences, who write run books and build um you know, the policies and who build the experience and the automation. Um not just in individual products or an individual clouds, but across the open source ecosystem. Whether it's technologies like answerable or Terror form, whether it's best practices websites around running kubernetes, um every every part of the community is really involved in driving up uh driving consistency, um driving predictability and driving reliability and what we try to do is actually work within those constraints um to take the ecosystem and to push it a little bit further. So the A. P. I. S. May be similar, but over time those differences can trip you up. And a lot of what I think we talked about where the industry is going, where where we want to be is everyone ultimately is going to own some responsibility for keeping their services running and making sure that their applications and their businesses are successful. The best outcome would be that the A. P. R. S are the same and they're open and that both the cloud providers and the open source ecosystem and vendors and partners who drive many of these open source communities are actually all working together to have the most consistent environment to make portability a true strength. But when someone does differentiate and has a true best to bring service, we don't want to build artificial walls between those. I mean, I mean, that's hybrid cloud is you're going to make choices that make sense for you if we tell people that their choices don't work or they can't integrate or, you know, an open source project doesn't support this vendor, that vendor, we're actually leaving a lot of the complexity buried in those organizations. So I think this is a great time to, as we turn over for cloud. Native looking at how we, as much as possible try to drive those ap is closer together and the consistency underneath them is both a community and a vendor. And uh for red hat, it's part of what we do is a core mission is trying to make sure that that consistency is actually real. You don't have to worry about those details when you're ignoring them. >>That's a great point. Before I get into some architectural impact, I want to get your thoughts on um, the, this trends going on, Everyone jumps on the bandwagon. You know, you say, oh yeah, I gotta, I want a data cloud, you know, everything is like the new, you know, they saw Snowflake Apollo, I gotta have some, I got some of that data, You've got streaming data services, you've got data services and native into the, these platforms. But a lot of these companies think it's just, you're just gonna get a data cloud, just, it's so easy. Um, they might try something and then they get stuck with it or they have to re factor, >>how do you look >>at that as an architect when you have these new hot trends like say a data cloud, how should customers be thinking about kicking the tires on services like that And how should they think holistically around architect in that? >>There's a really interesting mindset is, uh, you know, we deal with this a lot. Everyone I talked to, you know, I've been with red hat for 10 years now in an open shift. All 10 years of that. We've gone through a bunch of transformations. Um, and every time I talked to, you know, I've talked to the same companies and organizations over the last 10 years, each point in their evolution, they're making decisions that are the right decision at the time. Um, they're choosing a new capability. So platform as a service is a great example of a capability that allowed a lot of really large organizations to standardize. Um, that ties into digital transformation. Ci CD is another big trend where it's an obvious wind. But depending on where you jumped on the bandwagon, depending on when you adopted, you're going to make a bunch of different trade offs. And that, that process is how do we improve the ability to keep all of the old stuff moving forward as well? And so open api is open standards are a big part of that, but equally it's understanding the trade offs that you're going to make and clearly communicating those so with data lakes. Um, there was kind of the 1st and 2nd iterations of data lakes, there was the uh, in the early days these capabilities were knew they were based around open source software. Um, a lot of the Hadoop and big data ecosystem, you know, started based on some of these key papers from amazon and google and others taking infrastructure ideas bringing them to scale. We went through a whole evolution of that and the input and the output of that basically let us into the next phase, which I think is the second phase of data leak, which is we have this data are tools are so much better because of that first phase that the investments we made the first time around, we're going to have to pay another investment to make that transformation. And so I've actually, I never want to caution someone not to jump early, but it has to be the right jump and it has to be something that really gives you a competitive advantage. A lot of infrastructure technology is you should make the choices that you make one or two big bets and sometimes people say this, you call it using their innovation tokens. You need to make the bets on big technologies that you operate more effectively at scale. It is somewhat hard to predict that. I certainly say that I've missed quite a few of the exciting transformations in the field just because, um, it wasn't always obvious that it was going to pay off to the degree that um, customers would need. >>So I gotta ask you on the real time applications side of it, that's been a big trend, certainly in cloud. But as you look at hybrid hybrid cloud environments, for instance, streaming data has been a big issue. Uh any updates there from you on your managed service? >>That's right. So one of we have to manage services um that are both closely aligned three managed services that are closely aligned with data in three different ways. And so um one of them is redhead open shift streams for Apache Kafka, which is managed cloud service that focuses on bringing that streaming data and letting you run it across multiple environments. And I think that, you know, we get to the heart of what's the purpose of uh managed services is to reduce operational overhead and to take responsibilities that allow users to focus on the things that actually matter for them. So for us, um managed open shift streams is really about the flow of data between applications in different environments, whether that's from the edge to an on premise data center, whether it's an on premise data center to the cloud. And increasingly these services which were running in the public cloud, increasingly these services have elements that run in the public cloud, but also key elements that run close to where your applications are. And I think that bridge is actually really important for us. That's a key component of hybrid is connecting the different locations and different footprints. So for us the focus is really how do we get data moving to the right place that complements our API management service, which is an add on for open ship dedicated, which means once you've brought the data and you need to expose it back out to other applications in the environment, you can build those applications on open shift, you can leverage the capabilities of open shift api management to expose them more easily, both to end customers or to other applications. And then our third services redhead open shift data science. Um and that is a, an integration that makes it easy for data scientists in a kubernetes environment. On open shift, they easily bring together the data to make, to analyze it and to help route it is appropriate. So those three facets for us are pretty important. They can be used in many different ways, but that focus on the flow of data across these different environments is really a key part of our longer term strategy. >>You know, all the customer checkboxes there you mentioned earlier. I mean I'll just summarize that that you said, you know, obviously value faster application velocity time to value. Those are like the checkboxes, Gardner told analysts check those lower complexity. Oh, we do the heavy lifting, all cloud benefits, so that's all cool. Everyone kind of gets that, everyone's been around cloud knows devops all those things come into play right now. The innovation focuses on operations and day to operations, becoming much more specific. When people say, hey, I've done some lift and shift, I've done some Greenfield born in the cloud now, it's like, whoa, this stuff, I haven't seen this before. As you start scaling. So this brings up that concept and then you add in multi cloud and hybrid cloud, you gotta have a unified experience. So these are the hot areas right this year, I would say, you know, that day to operate has been around for a while, but this idea of unification around environments to be fully distributed for developers is huge. >>How do you >>architect for that? This is the number one question I get. And I tease out when people are kind of talking about their environments that challenges their opportunities, they're really trying to architect, you know, the foundation that building to be um future proof, they don't want to get screwed over when they have, they realize they made a decision, they weren't thinking about day to operation or they didn't think about the unified experience across clouds across environments and services. This is huge. What's your take on this? >>So this is um, this is probably one of the hardest questions I think I could get asked, which is uh looking into the crystal ball, what are the aspects of today's environments that are accidental complexity? That's really just a result of the slow accretion of technologies and we all need to make bets when, when the time is right within the business, um and which parts of it are essential. What are the fundamental hard problems and so on. The accidental complexity side for red hat, it's really about um that consistent environment through open shift bringing capabilities, our connection to open source and making sure that there's an open ecosystem where um community members, users vendors can all work together to um find solutions that work for them because there's not, there's no way to solve for all of computing. It's just impossible. I think that is kind of our that's our development process and that's what helps make that accidental complexity of all that self away over time. But in the essential complexity data is tied the location, data has gravity data. Lakes are a great example of because data has gravity. The more data that you bring together, the bigger the scale the tools you can bring, you can invest in more specialized tools. I've almost do that as a specialization centralization. There's a ton of centralization going on right now at the same time that these new technologies are available to make it easier and easier. Whether that's large scale automation um with conflict management technologies, whether that's kubernetes and deploying it in multiple sites in multiple locations and open shift, bringing consistency so that you can run the apps the same way. But even further than that is concentrating, mhm. More of what would have typically been a specialist problem, something that you build a one off around in your organization to work through the problem. We're really getting to a point where pretty soon now there is a technology or a service for everyone. How do you get the data into that service out? How do you secure it? How do you glue it together? Um I think of, you know, some people might call this um you know, the ultimate integration problem, which is we're going to have all of this stuff and all of these places, what are the core concepts, location, security, placement, topology, latency, where data resides, who's accessing that data, We think of these as kind of the building blocks of where we're going next. So for us trying to make investments in, how do we make kubernetes work better across lots of environments. I have a coupon talk coming up this coupon, it's really exciting for me to talk about where we're going with, you know, the evolution of kubernetes, bringing the different pieces more closely together across multiple environments. But likewise, when we talk about our managed services, we've approached the strategy for managed services as it's not just the service in isolation, it's how it connects to the other pieces. What can we learn in the community, in our services, working with users that benefits that connectivity. So I mentioned the open shift streams connecting up environments, we'd really like to improve how applications connect across disparate environments. That's a fundamental property of if you're going to have data uh in one geographic region and you didn't move services closer to that well, those services I need to know and encode and have that behavior to get closer to where the data is, whether it's one data lake or 10. We gotta have that flexibility in place. And so those obstructions are really, and to >>your point about the building blocks where you've got to factor in those building blocks, because you're gonna need to understand the latency impact, that's going to impact how you're gonna handle the compute piece, that's gonna handle all these things are coming into play. So, again, if you're mindful of the building blocks, just as a cloud concept, um, then you're okay. >>We hear this a lot. Actually, there's real challenges in the, the ecosystem of uh, we see a lot of the problems of I want to help someone automate and improved, but the more balkanize, the more spread out, the more individual solutions are in play, it's harder for someone to bring their technology to bear to help solve the problem. So looking for ways that we can um, you know, grease the skids to build the glue. I think open source works best when it's defining de facto solutions that everybody agrees on that openness and the easy access is a key property that makes de facto standards emerged from open source. What can we do to grow defacto standards around multi cloud and application movement and application interconnect I think is a very, it's already happening and what can we do to accelerate it? That's it. >>Well, I think you bring up a really good point. This is probably a follow up, maybe a clubhouse talk or you guys will do a separate session on this. But I've been riffing on this idea of uh, today's silos, tomorrow's component, right, or module. If most people don't realize that these silos can be problematic if not thought through. So you have to kill the silos to bring in kind of an open police. So if you're open, not closed, you can leverage a monolith. Today's monolithic app or full stack could be tomorrow's building block unless you don't open up. So this is where interesting design question comes in, which is, it's okay to have pre existing stuff if you're open about it. But if you stay siloed, you're gonna get really stuck >>and there's going to be more and more pre existing stuff I think, you know, uh even the data lake for every day to lake, there is a huge problem of how to get data into the data lake or taking existing applications that came from the previous data link. And so there's a, there's a natural evolutionary process where let's focus on the mechanisms that actually move that day to get that data flowing. Um, I think we're still in the early phases of thinking about huge amounts of applications. Microservices or you know, 10 years old in the sense of it being a fairly common industry talking point before that we have service oriented architecture. But the difference now is that we're encouraging and building one developer, one team might run several services. They might use three or four different sas vendors. They might depend on five or 10 or 15 cloud services. Those integration points make them easier. But it's a new opportunity for us to say, well, what are the differences to go back to? The point is you can keep your silos, we just want to have great integration in and out of >>those. Exactly, they don't have to you have to break down the silos. So again, it's a tried and true formula integration, interoperability and abstracting away the complexity with some sort of new software abstraction layer. You bring that to play as long as you can paddle with that, you apply the new building blocks, you're classified. >>It sounds so that's so simple, doesn't it? It does. And you know, of course it'll take us 10 years to get there. And uh, you know, after cloud native will be will be galactic native or something like that. You know, there's always going to be a new uh concept that we need to work in. I think the key concepts we're really going after our everyone is trying to run resilient and reliable services and the clouds give us in the clouds take it away. They give us those opportunities to have some of those building blocks like location of geographic hardware resources, but they will always be data that spread. And again, you still have to apply those principles to the cloud to get the service guarantees that you need. I think there's a completely untapped area for helping software developers and software teams understand the actual availability and guarantees of the underlying environment. It's a property of the services you run with. If you're using a disk in a particular availability zone, that's a property of your application. I think there's a rich area that hasn't been mined yet. Of helping you understand what your effective service level goals which of those can be met. Which cannot, it doesn't make a lot of sense in a single cluster or single machine or a single location world the moment you start to talk about, Well I have my data lake. Well what are the ways my data leg can fail? How do we look at your complex web of interdependencies and say, well clearly if you lose this cloud provider, you're going to lose not just the things that you have running there, but these other dependencies, there's a lot of, there's a lot of next steps that we're just learning what happens when a major cloud goes down for a day or a region of a cloud goes down for a day. You still have to design and work around those >>cases. It's distributed computing. And again, I love the space where galactic cloud, you got SpaceX? Where's Cloud X? I mean, you know, space is the next frontier. You know, you've got all kinds of action happening in space. Great space reference there. Clayton, Great insight. Thanks for coming on. Uh, Clayton Coleman architect at red Hat. Clayton, Thanks for coming on. >>Pretty pleasure. >>Always. Great chat. I'm talking under the hood. What's going on in red hats? New managed cloud service portfolio? Again, the world's getting complex, abstract away. The complexities with software Inter operate integrate. That's the key formula with the cloud building blocks. I'm john ferry with the cube. Thanks for watching. Yeah.

>>Mhm Yes. Hello and welcome back to the cube coverage of red hat summit 2021 Virtual. I'm john furrier host of the Q. We've got a great lineup here. We've got two great guests just bad padan, E. S. V. P. Of cloud platforms at red hat and Tracy ranking VP of open shift engineering at Red Hat folks. Thanks for coming on. Good to see. You got some big news, you guys have made some acquisitions. Uh stack rocks you guys bought into red hat was a really big deal. People want to know, what's the story? How's it going? What's the uptake? What's the integration, how's it going? >>Right, thanks john, thanks for having us on. Um so yeah, we're really excited with stack rocks acquisition being the team on board. Uh Well, the first thing to note before even why we did it uh was for for you and and then the beers have been following us closely. This is our first acquisition as red Hat being part of IBM. So, so, so quite big for us from that perspective as well. Right? Continue to maintain our independence um within uh IBM uh and I really appreciate that way of working together. Um but saying all of that aside, you know, as a company have always been focused on ensuring that were direct enterprise capabilities to just sort of doing that for two decades. With with Lennox, security has always been a big part of our story, right, ensuring that, you know, we're finding cbs updating uh and sending out patches to our customers and doing that in a reliable fashion running mission critical applications. We applied that same if you will um security mindset on the community side with the open ship platform. Um we've invested insecurity ourselves organically, right, you know, uh in various areas and making it more secure, all right, can't run containers uh as Root by default, uh investing in things like role based access control and so on. And we really felt like we want to deepen our commitment to security. Uh and so, you know, in conversations with stack rocks, we found just a great fit, just a great team building a really interesting approach to community security, right? You know, very declared of approach to it. Uh you know, focus on a vision around this notion of shift left. But you've probably been hearing from that because we're a little bit right. Which is this uh idea that, you know, we're in the world moving from devops to death setups. Uh and the approach that sack rocks were saying, so great team, great product, really great vision with regard to kind of weather going forward and finding a nice alignment between, you know what, you know, they've been thinking about the value that we want to bring >>Yeah, I want to dig into the depths cops, piece of it. But you brought up the IBM acquisition as part of now Red Hat bought IBM you know it's just you remember back in 2019 I interviewed Arvin on the cube when he was at IBM you guys were still independent and he had a smile on his face. He is pro cloud, he is all about cloud Native and even that interview I had no idea what was going on behind the scenes but I was kind of drilling him on some of the things that were important at that time which are now certainly relevant today which is cloud Native, Agile development Programmable infrastructure. I don't think we touched on security that much was kind of inherent in the conversation. He was like all smiling, he loves the cloud Native and and this is where it comes into the relevant, I have to ask you, what was it like to get this through? IBM where they're like girl green light or was it, was it different? What was different about this acquisition? >>John great, great question for you to ask. And you know, I will say that, uh, you know, everyone's heard the stories they're telling us. They get, you know, part of IBM, you know, it's definitely working on red hat jOHn the cube we've talked to you and several of your colleagues about that. Um, the great thing has been that, look, the redhead way of working, uh, are still pushing forward with regard to our commitment to open source, uh, and our culture, you know, is still the way it is. And I have to give huge credit not just to urban and his and his team, but definitely to orbit right. He's always champion, He's champion rather acquisition. He's champion kind of, you know, the independence that we've had and he takes very, very firm stance around it. Um, and look, IBM uh, story company uh, in the United States and really in the world, um, they have, there was working and you know, for redhead, they've kind of said, look, we'll give you a pass path, right? So, uh, getting the acquisition through, if you will, diarrhea processes, um, really was, was hugely supported by, you know, from mormon, but all the way down. Russian strategic >>strategic bet with the dollars involved trace, they want to get you in this because, you know, one of the things about shift left and getting security built in by default, which has always been part of red hat, that's never been an issue. It just extends as developers want to have native security built in. There's a technology angle to this as well. So, um, obviously cloud native is super important. What investments are you guys making with this acquisition and how does that translate to customer benefits? >>Yeah, I mean the one thing that is really important about the stock rocks acquisition and kind of, you know, key for us is, you know, this was a cube native solution and I think that's really, you know, was important piece as to why stock rocks might have been, you know, was a great fit for us. Um, and so you know, what we've been trying to do in the short time that that team has been on board with us is really, you know, taken a deep look and understanding where are the intersection points of some of the things that we have been trying to focus on, you know, just with inside of, you know, open shift in red hat in general and where do they have bring the additional value. Um, and really trying to make sure that when we create this solution and ultimately it is a solution that's cohesive across the board. Um, we don't add confusion too. You know what, some of the things that maybe we already do this team knows, you know, how to they know their customer base. They really know what the customers are looking for. And we are just trying to absorb, I would say so much of this information uh as we are trying to, you know, create what the right road map will be uh for stack rocks from a long term and infrared had ultimately in the security space. I mean, as the chef said, I mean we are red hats known for being, you know, security mind focus built on top of realm, you know, uh the leader and so we want to make sure that what we've got that actually serves, you know, the developers being able to not just secure the environment and the platform, but also the workloads, customers need that security from us. Um and build it in so that we have, you know, into the cube native >>controls. >>So stack rocks was known for reinventing and security enterprise security with cloud native. How is it complimentary? How does it fit in? Can you guys just quickly talk to that point because um like you said, you guys had security but as kubernetes and containers in general continue to rise up and and kubernetes continue to become a hybrid cloud kind of linchpin for applications. Um where's the synergy? Where's where does this connect? And what are some of the uh the part of the areas where it's it's fitting in nicely or or any overlaps that you can talk about as well? >>Yeah, I can start and then maybe Tracy if you want to add to that securities of it's a wide space. Right? So, you know, just saying security is like, well, you know what security you're talking about, you're talking about, you know, and use the security, like what your desktop are you talking about? You know, intrusion prevention? I mean, it's a huge, huge, you know, space. Uh you know, many companies devoted to the entire spectrum, you know, self has a very robust security business. We're very focused on uniting Tracy. Was talking about this, the Kubernetes Native security part of this. Right. You know, do we have the appropriate runtime uh, controls in place? Uh You know, our policies configured appropriately Well, if they're in one cluster, are they being applied consistently across, you know, every cluster? How do we make sure that, you know, we make security the domain, not just of the operators but also uh in in uh make it easier for it to be adopted at development time. So, you know, there's a, there's a, if you will, a very sort of uh a lot of surface area for security, we're trying to really think about the pieces that are most relevant for our enterprise customers and the ones that are deploying it at scale. And I'm sure we can build on it. Having said that, john what I do want to add also is that because expands even of Cuban any security is so large, there is a lot of room for our partners to play. Right? And so before you asked me that question, I want to say that there is space. Right? So you know, I've had conversations with you know, all the other folks in the cloud native security space. We know them well, we've been working with them over the years and we could do to look forward to ensure that they're building over and above the foundation of Berlin. >>So plenty of beachhead, what you're saying from a, from a security sample, you guys hit the table stakes added into the product, but there's so much surface area going on with this hybrid cloud and soon to be multi cloud that you're saying this room for partners to play. >>Exactly, right, >>okay. Tracy quick under the hood, you know, actually shift left. That's kind of the mindset for developers who are writing modern applications might not want to get under the hood, who just wanted all the program ability of security and not have to come back to it. I mean that seems to be the complaint that I hear. It's like okay I gotta come back and do a security, more security work. I just wrote the code that was last week or yesterday and that seems to be the developer productivity. Then there's also under the hood devops what how does this all fit? >>Yeah, so it's uh let's take a take a step back and this is how I kind of like to think about it. So we are trying to look at, you know, how do we just enable in some of the C. I. C. D. The tooling that we have? How do we actually take and enable some of the technology that was already available in stock rocks today and actually put it into those tools. Because if we can make it easy for you to not just develop your application and, you know, integrated in with what you're, the tooling is that you're trying to use for the entire life cycle of developing your application. It then becomes exactly what you didn't say, you know, what they're doing now is it's an after thought. We don't need it to be an afterthought. Um and I think, you know, we're seeing the changing from a customer mindset where um they're become customers are becoming a lot more aware of these things. So if we actually get this into, you know, some of the Argo and the ci cd pipe pipeline work, then it just becomes something natural and not a secondary thought because actually when it's a secondary thought, uh we have exposures and that's not what a customer wants when they're creating, you know, creating these workloads, they're trying to rapidly create the workloads, so we need to make it um to have those integration points in as quickly >>as possible. >>Totally nailed. I mean there's productivity issues and there's also the top line which is security. Great stuff. Congratulations on that acquisition. Security continues to be built in from the beginning. That's what people want. They want productivity want want security, great stuff, Great acquisition. Congratulations. Um Next next segment I want to get into is uh open shifts around telemetry. Tell us about telemetry for open shift. What is this about? >>Yeah, another big interesting topic for us. So over a year ago we released open Ship for and you know, we learned a lot of lessons, you know, shipping open ship three up and over the years and really getting feedback from hundreds of customers around the globe. One of the things obviously we heard from a lot was you know, make install the upgrade experience better. Right. But you know, we were thinking about how can we take that forward to the next level, which is is there a way for us to say, you know, let these clusters they connected up so we can get a better sense of cluster help and help with remote health monitoring will be able to proactively provide information back to our customers around, let's say, you know, if applications are healthy clusters healthy and how they're running and how we can help them um could figure them if they're not. Um And so that led us to introducing uh inflammatory remote health monitoring directly into open ship for as a value that we can provide to customers. Um And what that really starts doing is starts bringing this notion of a public cloud, like experience to customers with clusters run across the hybrid cloud. Right? So you have the expectation that, you know, your clusters are monitored and watched over in the public cloud and we want to make sure we can provide that to customers regardless of, you know, where they're running in. So, so that's just >>a quick question on that insights for open shit. That's what you're getting to. Is that on premise? And in the cloud? So it's hybrid environment, is that correct? >>Exactly. Right. So, the insights for open ship is all about that, Right? So how can be proactively, you know, uh identify risk helped remediated? How can we uh do things like, for example, give you recommendations, cost optimization, right insights around around around that. Uh and to your point, right? The goal is to make it completely hybrid. So, it's obviously a new area right for customers want Leslie used to that, you know, in an on premise environment, they're used to that in a public cloud or cloud native environment. And we're trying to make sure we bring that consistently across to our customers, you know, regardless of where they're running apart. >>Tracy. Talk about the the developer productivity involved because if you have telemetry and you have insight into what's going on in the infrastructure and the data, what's going on the application, you can be more proactive, You don't have to get pulled into these rabbit holes of troubleshooting. Oh, is a trace over here or something going on over here. Are clusters going down or should I could have caught that there's a lot of, you know, good intentions with with the code and then all of a sudden new code gets pushed and then also that triggers this to go off and you have all these kind of dependencies, day two operations, many people call this kind of that phenomenon where everything looks good and then you start pushing more stuff more code and then the cluster goes down and then it's like wait, that could have been avoided. That was a dumb error, we could have fixed that this is kind of the basic what I call human software error kind of stuff that's not intended. The telemetry help this area. >>Yeah, it does. And actually one point that even to take it further, that I think it's important is our customers can learn from each other not even having to talk to each other, which is the beauty of what telemetry is and what redhead insights, rope and shift is. You know, what we have been able to see is you know, there are certain characteristics that happen even across, you know, certain groups of customers but they don't know that they don't talk to each other, but the telemetry is giving us a night into what some of those patterns are. And so when a customer in one site starts to have, we start to see telemetry, you know, you know, maybe a. T. D. Is going down for a certain reason and and we can determine that we then have the ability to take that telemetry and you know, be able to send alerts back to all the other customers and say, hey we recognize this might be becoming an issue, You know, here's how you might re mediate it or hey we've already put a fix out for this issue that we're starting to see you having an issue, you should probably take action on. So it's an increasing the the efficiency of customers without them necessarily having to, you know, constantly be understanding, monitoring, you know, watching everything like they had had to do from of the three perspective, we're now giving them some of the insights of what we know as developers back to them, >>you know, that's interesting. I think that's really key because it's talking to a friend last night we just talked about cybersecurity and we're talking about how a lot of these things are patterns that have that are the same and people just don't talk to each other. There's no shared insights. I think this is an interesting dynamic where you can get the collective intelligence of other patterns and then share that. So the question that I mean that's that's a game changer in my opinion. So that's awesome. The question I have is can you guys push alerts and recommendations to the customers? So from this data? So how does that work? Is that built into the product? Can I get some proactive notifications and saying, hey, you know, your cluster might go down and we've seen this before, we've seen this movie. I mean she is that built in. >>Yeah, so john you're keeping it exactly where we're taking this, right? And I think Tracy started putting out some breadcrumbs for you there. So uh, first get comfortable with the foundation was laid out, get clusters connected right. Then information starts going, reported, we start getting exactly to what you said, john write a set of patterns that we can see Tracy, start talking about what we can, if we see pattern on one end, we can go off and help customers on other end. Now, if you take this forward interest for your viewers today, um introduce a I you know, into this, right? And then we can start almost starting to proactive now of saying, look, you know, following actions are going to be committed or we expect them to be committed. You know, here's what the outcome is a result of that. Here's what we recommend for you to do, right? So start proactive remediation along that. So that is exactly, you know, the surface that we're trying to lay down here and I think this is a huge, >>huge game changer. Well, great stuff, want to move on the next we're getting go on for hours on that one topic. I think telemetry is a super important trend. Uh you guys are on top of a great, great job to bring in the Ai piece. I think that's super cool. Let's get back to the end of blocking and tackling Tracy. You know, one of the things that we're seeing with devops as it goes mainstream now, you've got def sec apps in there too, is you've got the infrastructure and you've got the modern application development, modern application developers, just wanna code, be productive, all that security shifting left, everyone's all happy that things are going great under the hood. You have a whole set of developers working on infrastructure. The end of the customers don't want to manage their own infrastructure. How is red hat focused on these two groups? Because you got this SRE like cloud Ops persona developing in the enterprise and you got the developers, it's kind of like almost two worlds coming together, how you, how you helping customers, you know, control their infrastructure and manage it better. >>Yeah, so great question. And you know, this really plays to the strength of what, you know, we have been trying to champion here at red hat for for many years now around the hybrid cloud and this, you know, hopefully everybody's recently heard about the announcement we've made with our new offering Rosa in partnership with amazon. Um you know, we've got different offerings that enables customers to really focus, as you mentioned on the key aspects that they are concerned about, which is how do they drive their businesses, how do they create their applications, their workloads that they need to and offload, you know, the need for having to understand all of the I. T. Infrastructure that's underneath. Um We want to red hat to reduce the operational complexity that customers are having um and give them the ability to really focus on what's important for them. Um how can they be able to scale out their applications, their businesses and continue to add value where they need to have and so um I think it's great we're seeing a huge uptake right now and we've got customers and they understand completely this hybrid cloud model where they're, you know, purchasing open shift um for certain, you know, applications and workloads that they want to run inside their own data centers. And then for those that they know that they don't, you know, don't have to be inside their own data centers. They don't want to have all of that operational complexity. They want to utilize some of the clouds. That's when they're starting to look at other things like rosa or open shift dedicated and and really starting to find the right mix that works well for their business. >>So are you saying that you guys are going to the next level because the previous, I won't say generation but the current situation was okay, you're born in the cloud or you lift and shift to the cloud, You do that manually, then you go on premise to build that cloud operations. Now you're in a hybrid environment. So you're saying if I get this right that you guys are providing automation around standing up in building services on AWS and cloud, public cloud and hybrid, is that kinda what you're getting at? >>Yeah. So the to go to the higher multi cloud world, right? You want platform consistency, right? Running my application running on a platform consistently, you know, where we go. Right. Tracy started talking about this idea of in some cases you say, well I've got the infrastructure team, I've got the ops team, johnny talked about this notion of, well the dwarves can be hard, sometimes right to some groups. Um, and so hey, red hat or hey redhead, plus, you know, my hyper scale of choice, you know, take that off of my hands, Right. Run that for me consistently yourself. Right. So I focused on my application uh and the management of infrastructure is something that's on you Tracy talked about rosa, that's our joint uh first party service that you know, we've got with amazon were directly available in amazon's console, you can go pull that down, right. You'll see red hat open shift on AWS, right on their uh we've got a similar one with Microsoft Azure Tracy mentioned open dedicated, we stand up the platform, we have our own sorry team that manages it with IBM as well as with google. So you pick your cloud of choice and we'll make sure, you know, we'll give you a platform that if you as a customer so choose to self manage. Great, go for it. If you'd like for us to manage it directly ourselves or in conjunction with the cloud provider and provided to you as a native service, you know, we can do that for you as well. Right? So that day to obsolete, you know, challenge that we're talking about. You know, it's something that we can get your hands if you want us to. >>That's really cool. You gotta manage service. They can do it themselves whatever they want. They can do it on public cloud and hybrid. Great stuff. Yeah, I think that's the key. Um, and that's, that's, that's killer. Now, the next question is my favorite. I want to ask you guys both pretend I'm a customer and I'm like, okay, Tracy shit, tell me what's in it for me. What is open shifts and red hat doing for me is the customer? What are you bringing to the table for me? What are you gonna do for me? What is red hat doing for me today? So if you have the kind of bottom line we were in the elevator or probably I ask you, I like what I'm hearing. Why? Why are you cool? Why are you relevant? What's in it for me? >>You >>already start? Okay. Yeah, so I mean I think it's a couple of things that we let's just tie it back to the first initial blend. I mean we've got, we're enabling the customers to choose like where do they want to work that run their workloads, what do they want to focus on? I think that's the first thing. Um we're enabling them to also determine like what workloads do they want to put on there. We continue to expand the workloads that we are providing um capabilities to customers. You know most, you know one of the more recent ones we've had is you know, enablement of Windows containers a huge plus for us. Um, you know, it's just kind of talked about, dropped the buzzword ai you know, recently, you know, we're looking at that, we're talking about, you know, moving workloads need to go to the edge now. It's not just about being in the data centers, so it's about enablement. That's really what open shift as you know, bread and butter is, is, you know, let us, you know, create the ability for you to drive your workloads, whichever, whatever your workloads is, modernize those workloads um, in place them wherever you want to. >>Yes, your your answer. How would you say to that? >>I'll build on what Tracy said, right. She obviously took the, you know, build up tribal Benjamin perspective and I'll sort of talk about a business thing you're introducing, actually add threat at summit. So, you know, we go up and acquire stock rocks, you know, further deepen investment in communities or containment of security. Uh if you recall, john, we've talked to you about, you know, advanced cluster management team that we actually got from IBM incorporate that within red hat, um, to start providing, you know, those capabilities are consistent, you know, cluster policy, immigration management. Um, and you know, in the past we've made an acquisition of Core West, we've got a lot of technology from that incorporated the platform and also things like the quake container registry. What we're introducing address had some it is a way for us to package all of that together. So a customer doesn't say, look, you know, let me pick out a container platform here, let me go find, you know, somebody manage it over there. You let me see, you know what security you adhere. We introduced something called open shift platform plus right. Which is the packaging of, you know, core Open shift contain a platform uh, capabilities within uh, stack rocks, which we're calling advanced cluster security capabilities of cluster management, which is called advanced cluster management. And the quake container registry always want to make it much easier for customers to consume that. And again, you know, the goal is, you know, run that consistently in your hybrid multi club >>chef Tracy. Great, great segment, great insight. Um, here on the cloud platform and open shift under the hood. Uh, you guys are well positioned and I was talking about Arvin and idea who acquired red hat. You know, it's pretty clear that cloud native hybrid is the new cloud operating environment. That's clear. You guys are well positioned. And congratulations. Final question Chef. Take a minute to quickly put the plug in for open shift. What's next? Um, looking forward, what do you guys building on? Um, what's on the roadmap if you can negative share the road map, but yeah, tell us what you're thinking about. I mean you're innovating out in the open, love your shirt by the way and that's the red hat way, looking ahead. What's coming for? Open shift? >>So john I will say this, our roadmap is out in the open every quarter. Our product managers host the session right open to anybody, right? You know, customers prospect, competitors, anybody can can come on. Um, and uh, you hear about our road map, lots of interesting things they're working on uh, as you can imagine investments on the edge front, right? So that's across our portfolio, right on the open shift side, but also on learning platform as well as on the open stack front, make it easier to have, you know, slim down open shift. we'll run that you won't be able to run uh open ship in remote locations and then manage it. Um So expect for us uh you know, just to show you more work there, drinking things like uh ai and more workloads directly onto the platform, but you'll see what they're doing to get more Alex on what we're doing to take uh technologies that we've got called Open data hub to make it easier to run more data intensive, more ai ml types of frameworks directly a platform. Um And so that's a great interest, more workloads Tracy, start talking about that. Right, so Windows containers, support has G eight, uh and what's really awesome about that is that we've done that with Microsoft, right, so that offering is jointly supported by both us and our partners over at Microsoft uh virtualization, which is taking much machines and being able to run them as dangerous orchestrated by communities Um, and and doing more work, you know, on that front as well. So just a lot of different areas uh, were investigated and really, really excited to bring more workloads on 2:00. >>Well, Chef Tracy, great segment with a lot of data in there. Thanks for spending time in and providing that insight and uh, sharing the information. A lot of flowers blooming um, here in the cloud native environment, a lot of action. A lot of new stuff going on. Love the shift left. I think that's super relevant. You guys do a great job. Thanks for coming on. I appreciate it. >>Okay. >>This the cubes coverage of red hat summit. I'm john for a host of the cube. Thank you for watching.

>>mhm Yes. Hello and welcome back to the cubes coverage of red hat summit 2021 virtual. I'm john for your host of the cube and cube coverage here with matt Hicks. Executive vice president of products and technologies at red hat cuba lum I've been on many times, knows the engineering side now running all the process of technologies matt. Great to see you. Thanks for coming on remote. I wish we were in real real life in person. I RL but doing it remote again. Thanks for coming on. >>Hey, thanks thanks for having me today. >>Hey, so what a year you know, um, I was just talking to a friend and another interview with the red hat colleagues. Chef on your team in 2019 I interviewed Arvin at IBM right before he bought red hat and you smile on his face and he wasn't even ceo then um, he is such a big fan of cloud native and you guys have been the engine underneath the hood if you will of IBM this transformation huge push now and with Covid and now with the visibility of the post Covid, you're seeing cloud Native at scale with modern applications just highly accelerated across the board In almost every industry, every vertical. This is a very key trend. You guys at the, at the center of it always have been, we've been covering you for many years, interesting time and so now you guys are really got the, got the formula at red hat, take us through the key transit you see on this wave for enterprises and how is red hat taking that, taking that through? >>Yeah, no, absolutely. It has been, it's been a great ride actually. I remember a couple years ago standing on stage with Arvin prior to the acquisition. So it's been uh, it's been a world one but I think if we look at Really would emerge in 2020, we've seen three trends that we hope we're gonna carry through in 2021 just in a better and better year for that. That the first is open hybrid cloud is really how customers are looking to adapt to change. They have to use what they have um assets they have today. On premise, we're seeing a lot of public cloud adoption that blend of being hybrid is just, it is a reality for how customers are having to deliver a edge computing I think is another area I would say uh the trend is really not going to be a fad or a new, you know, great texture. Um the capabilities of computing at the edge, whether that is automotive vehicles, radio access network capabilities to five G. It's pretty astounding at this point. So I think we're gonna see a lot of pushing edge computing for computing, getting closer to users. Uh but then also the choice aspect we're seeing with Ceos, we often talk about technology is choice, but I think the model of how they want to consume technology has been another really strong trend in 2020. Uh We look at this really is being able to deliver a cloud managed services in addition to technology that ceos around themselves. But those, those will probably be the three that stand out to me at least in 2020 we've seen, >>so matt take us through in your minds and red hats, perspective the workloads that are going to be highlighted in this cloud native surge that's happening. We're seeing it everywhere. You mentioned edge industrial edge to consumer Edge to lightweight, edge, massive new workloads. So take us through how you see kind of the existing workloads evolving and potentially new workloads that emerging. >>Yeah. So I think um you know first when you talk about edge workloads a big umbrella but if you look at data driven workloads, especially in the machine learning artificial intelligence spectrum of that, that's really critical. And a reason that those workloads are important is five G. Aside for now when you're running something at the edge you have to also be able to make decisions pretty well at the edge. And that that is that's where your data is being generated and the ability to act on that closely. Whether that's executing machine learning models or being able to do more than that with A I. That's going to be a really really critical workload. Uh huh. Coupled to that, we will see I think five G. Change that because you're going to see more blending in terms of what can you draw back to uh closer to your data center to augment that. So five G will shift how that's built but data driven workloads are going to be huge then I think another area will see is how you propagate that data through environment. Some Kafka has been a really popular technology will actually be launching a service in relation to that. But being able to get that data at the edge and bring it back to locations where you might do more traditional processing, that's going to be another really key space. Um and then we'll still have to be honest, there is still a tremendous amount of work loads out there that just aren't going to get rebuilt. And So being able to figure out how can you make them a little more cloud native? You know, the things your companies have run on for the last 20 years, being able to step them closer to cloud native, I think it's going to be another critical focus because he can't just rewrite them all in one phase and you can't leave them there as well. So being able to bridge shadow B T to >>what's interesting if folks following red hat, No, no, you guys certainly at the tech chops you guys have great product engineering staff been doing this for a long time. I mean the common Lennox platform that even the new generation probably have to leave it load limits on the server anymore. You guys have been doing this hybrid environment in I T for I T Sloan for decades. Okay. In the open, so, you know, it's servers, virtualization, you know, private, public cloud infrastructures and it's been around, we've been covering it in depth as you know, but that's been, that's a history. But as you go from a common Lennox platform into things with kubernetes as new technologies and this new abstraction layers, new control plane concept comes to the table. This need for a fully open platform seems to be a hot trend this year. >>How do you >>describe that? Can you take a minute to explain what this is, this is all about this new abstraction, this new control plane or this open hybrid cloud as you're calling? What is this about? What does it mean? >>Yeah, no, I'll do a little journey that she talked about. Yeah. This has been our approach for almost a decade at this point. And it started, if you look at our approach with Lennox and this was before public clouds use migrants existed. We still with Lennox tried to span bare metal and virtualized environments and then eventually private and public cloud infrastructure as well. And our goal there was you want to be able to invest in something, um, and in our world that's something that's also open as in Lennox but be able to run it anywhere. That's expanded quite a bit. That was good for a class of applications that really got it started. That's expanded now to kubernetes, for example, kubernetes is taking that from single machines to cluster wide deployments and it's really giving you that secure, flexible, fast innovation backbone for cloud native computing. And the balance there is just not for cloud native, we've got to be able to run traditional emerging workloads and our goal is let those things run wherever rail can. So you're really, you're based on open technologies, you can run them wherever you have resources to run. And then I think the third part of this for us is uh, having that choice and ability to run anywhere but not being able to manage. It can lead to chaos or sprawl and so our investments in our management portfolio and this is from insights the redhead advanced cluster management to our cluster security capabilities or answerable. Our focus has been securing, managing and monitoring those environments so you can have a lot of them, you can run where you want, but she just sort of treat it as one thing. So you are our vision, how we've executed up to this point has really been centered around that. I think going forward where you'll see us um really try to focus is, you know, first you heard paul announced earlier that we're donating more than half a billion dollars to open. I would cloud research and part of this reason is uh running services. Cloud native services is changing. And that research element of open source is incredibly powerful. We want to make sure that's continuing but we're also going to evolve our portfolio to support this same drive a couple areas. I would call out, we're launching redhead open shift platform plus and I talked about that combination from rail to open shift to being able to manage it. We're really putting that in one package. So you have the advanced management. So if you have a huge suites of cloud native real estate there, you can manage that. And it also pushes security earlier into the application, build workflows. This is tied to some of our technology is bolstered by the stack rocks acquisition that we did. Being able to bring that in one product offering I think is really key to address security and management side. Uh we've also expanded Redhead insights beyond Rehl to include open shift and answerable and this is really targeted it. How do we make this easier? How do we let customers lean on our expertise? Not just for Lennox as a service, but expand that to all of the things you'll use in a hybrid cloud. And then of course we're going to keep pushing Lennox innovation, you'll see this with the latest version of red hat enterprise, like so we're gonna push barriers, lower barriers to entry. Uh But we're also going to be the innovation catalyst for new directions include things like edge computing. So hopefully that sort of helps in terms of where, where we started when it was just Lennox and then all the other pieces were bringing to the table and why and some new areas. Uh We're launching our investment going forward. >>Yeah, great, that's great overview. Thanks for taking the time to do that. I think one of the areas I that's jumping out at me is the uh, advanced cluster management work you guys are doing saw that with the security peace and also red hat insights I think is is another key one and you get to read that edge. But on the inside you mentioned at the top of this interview, data workloads pretty much being, I mean that pretty much everything, much more of an emphasis on data. Um, data in general but also, you know, serve abilities a hot area. You know, you guys run operating system so you know, in operating systems you need to have the data, understand what's being instrumented. You gotta know that you've got to have things instrument and now more than ever having the data is critical. So take us through your vision of insights and how that translates. Because he said mentions in answerable you're seeing a lot more innovations because Okay I got provisions everything that's great. Cloud and hybrid clouds. Good. Okay thumbs up everyone check the box and then all of a sudden day too As they call day two operations stuff starts to, you know, Get getting hairy, they start to break. Maybe some things are happening. So day two is essentially the ongoing operational stability of cloud native. You need insights, you need the data. If you don't have the data, you don't even know what's going on. You can't apply machine learning. It's kind of you if you don't get that flywheel going, you could be in trouble. Take me through your vision of data driven insights. >>Yeah. So I think it's it's two aspects. If you go to these traditional traditional sport models, we don't have a lot of insight until there's an issue and I'm always amazed by what our teams can understand fix, get customers through those and I think that's a lot of the success red hats had at the same note, we want to make that better where if you look at real as an example, if we fixed an issue for any customer on the planet of which we fix a lot in the support area, we can know whether you're going to hit that same issue or not in a lot of cases and so that linkage to be able to understand environments better. We can be very proactive of not just hey apply all the updates but without this one update, you risk a kernel panic, we know your environment, we see it, this is going to keep you out of that area. The second challenge with this is when things go do break or um are failing the ability to get that data. We want that to be the cleanest handshake possible. We don't want to. Those are always stressful times anyway for customers being able to get logs, get access so that our engineering knowledge, we can fix it. That's another key part. Uh when you extend this to environments like open shift things are changing faster than humans can respond in it. And so those traditional flows can really start to get strained or broken broken down with it. So when we have connected open shift clusters, our engineering teams can not only proactively monitor those because we know cooper net is really well. We understand operators really well. Uh we can get ahead of those issues and then use our support teams and capabilities to keep things from breaking. That's really our goals. Finding that balance where uh we're using our expertise in building the software to help customers stay stable instead of just being in a response mode when things break >>awesome. I think it's totally right on the money and data is critical in all this. I think the trust of having that partnership to know that this pattern recognition is gonna be applied from the environment and that's been hurting the cybersecurity market people. That's the biggest discussion I had with my friends and cyber is they don't share the data when they do, things are pretty obvious. Um, so that's good stuff there and then obviously notifications proactive before there's a cause or failure. Uh great stuff. This brings up a point that paul come here, said earlier, I want to get your reaction to this. He said every C. I. O. Is now a cloud operator. >>That's a pretty bold >>statement. I mean, that's simply means that it's all cloud all the time. You know? Again, we've been saying this on the queue for many years, cloud first, whatever people want to call it, >>what does that actually >>mean? Cloud operator, does that just mean everything's hybrid? Everything's multiple. Cloud. Take me through an unpacked what that actually means? >>Yeah. So I think for the C I O for a lot of times it was largely a technology choice. So that was sort of a choice available to them. And especially if you look at what public clouds have introduced, it's not just technology choice. You're not just picking Kafka anymore. For example, you really get to make the choice of do I want to differentiate my business by running it myself or is this just technology I want to consume and I'm going to consume a cloud, native service and other challenges come with that. It's an infrastructure, not in your control, but when you think about a ceo of the the axes they're making decisions on, there are more capabilities now and I think this is really crucial to let the C i O hone in on where they want to specialist, what do they want to consume, what do they really want to understand, differentiate and Ron? Um and to support this actually, so we're in this vein, we're going to be launching three new managed cloud services and our our focus is always going to be hybrid in these uh but we understand the importance of having managed cloud services that red hat is running not the customers in this case. So one of those will be red hat open shift streams for Patrick Kafka. We've talked about that, that data connectivity and the importance of it and really being able to connect apps across clouds across data centers using Kafka without having to push developers to really specialize in running. It is critical because that is your hybrid data, it's going to be generated on prim, it's going to be generated the edge, you need to be able to get access to it. The next challenge for us is once you have that data, what do you do with it? And we're launching a red hat open shift data science cloud service and this is going to be optimized for understanding the data that's brought in by streams. This doesn't matter whether it's an Ai service or business intelligence process and in this case you're going to see us leverage our ecosystem quite a bit because that last mile of AI workloads or models will often be completed with partners. But this is a really foundational service for us to get data in and then bring that into a workflow where you can understand it and then the last one for us is that red hat open shift api management and you can think of this is really the overseer of how apps are going to talk to services and these environments are complex, their dynamic and being able to provide that oversight up. How should my apps be consuming all these a. P. S, how should they be talking? How do I want to control? Um and understand that is really critical. So we're launching these, these three and it fits in that cloud operator use, we want to give three options where you might want to use Kafka and three Scale technologies and open data hub, which was the basis of open shift data sides, but you might not want to specialize in running them so we can run those for you and give you as a C. I. O. That choice of where you want to invest in running versus just using it. >>All right, we're here with matt Hicks whose executive vice president prospect technology at red hat, matt, your leader at red hat now part of IBM and continues to operate um in the red hat spirit, uh innovating out in the open, people are wearing their red hat uh hoodies, which has been great to see. Um I ask every executive this question because I really want to get the industry perspective on this. Um you know, necessity is the mother of invention as the saying goes and, you know, this pandemic was a challenge for many In 2020. And then as we're in 2021, some say that even in the fall we're gonna start to see a light at the end of the tunnel and then maybe back to real life in 2022. This has opened up huge visibility for CSOS and leaders and business in the enterprise to say, Hey, what's working, what do we need? We didn't prepare for everyone to be working at home. These were great challenges in 2020. Um, and and these will fuel the next innovations and achievements going forward. Um again necessity is the mother of all invention. Some projects are gonna be renewed and double down on some probably won't be as hybrid clouds and as open source continues to power through this, there's lessons to be learned, share your view on what um leaders in in business can do coming out of the pandemic to have a growth strategy and what can we learn from this pandemic from innovation and and how open source can power through this adversity. >>Yeah. You know, I think For as many challenging events we had in 2020, I think for myself at least, it it also made me realize what companies including ourselves can accomplish if we're really focused on that if we don't constrain our thinking too much, we saw projects that were supposed to take customers 18 months that they were finishing in weeks on it because that was what was required to survive. So I think part of it is um, 2020 broke a lot of complacency for us. We have to innovate to be able to put ourselves in a growth position. I hope that carries into 2021 that drives that urgency. When we look at open source technologies. I think the flexibility that it provides has been something that a lot of companies have needed in this. And that's whether it could be they're having to contract or expand and really having that moment of did the architectural choices, technology choices, will they let me respond in the way I need? Uh, I'm biased. But first I think open models, open source development Is the best basis to build. That gives you that flexibility. Um, and honestly, I am an optimist, but I look at 2021, I'm like, I'm excited to see what customers build on sort of the next wave of open innovation. I think his life sort of gets back to normal and we keep that driving innovation and people are able to collaborate more. I hope we'll see a explosion of innovation that comes out and I hope customers see the benefit of doing that on a open hybrid cloud model. >>No better time now than before. All the things are really kind of teed up and lined up to provide that innovation. Uh, great to have you on the cube. Take a quick second to explain to the folks watching in the community What is red hat 2021 about this year? And red hat someone, I'll see. We're virtual and we're gonna be back in a real life soon for the next event. What's the big takeaway this year for the red hat community and the community at large for red hat in context of the market? >>You know, I think redhead, you'll keep seeing us push open source based innovation. There's some really exciting spaces, whether that is getting closer and closer towards edge, which opens up incredible opportunities or providing that choice, even down to consumption model like cloud managed services. And it's in that drive to let customers have the tools to build the next incredible innovations for him. So, And that's what summit 2021 is going to be about for us, >>awesome And congratulations to, to the entire team for the donation to the academic community, Open cloud initiative. And these things are doing to promote this next generation of SRS and large cloud scale operators and developers. So congratulations on that props. >>Thanks john. >>Okay. Matt Hicks, executive vice president of products and technology. That red hat here on the Cube Cube coverage of red hat 2021 virtual. I'm John Ferrier. Thanks for watching. Yeah.

>>Hey, welcome to the Cubes coverage of Red Hat Summit 2021, the virtual experience, I'm lisa martin, I have two guests joining me. One is a cube alum kamal Shah is back, he's now the VP of cloud platforms at Brent had come on, it's great to have you back on the program. You're in a new role, we're going to talk about that. Thank you. And Kirsten newcomer is here as well. She's the Director of cloud and Death stickups strategy at Red Hat, Kirsten, Welcome and thank you for bringing the red hat vibe to the segment. >>Absolutely, very happy to be here. >>So looking forward to this conversation that we're going to be having in the next 20 minutes or so. We're gonna be talking about the last time come on, you were on, you were the ceo of stack rocks In January of 2021. The announcement that red hat plans to acquire stack rocks, it wouldn't be talking all about that. But I'd like to start with Kirsten, give us your perspective from red hats perspective, why is red hat a good fit for stack rocks? >>You know, there are so many reasons first of all as as you know, right? Red hat has been working with product Izing kubernetes since kubernetes one dato. Right, so so open shift three dato shipped with kubernetes one dot Oh, so we've been working with kubernetes for a long time, stack rocks embraces kind of is kubernetes native security embraces the declarative nature of kubernetes and brings that to security. Red hats, Custer's red hat enterprise customers, we have a great set across different verticals that are very security conscious and and during my five years at red hat, that's where I spend the majority of my time is talking with our customers about container and kubernetes security. And while there's a great deal of security built in to open shift as it goes to market out of the box, customers need the additional capabilities that stack rock springs. Historically, we've met those needs with our security partners. We have a great ecosystem of security partners. And with the stack rocks acquisition, we're now in a position to offer additional choice. Right. If a customer wants those capabilities from Red hat tightly integrated with open shift, we'll have those available and we continue to support and work with our broad ecosystem of security partners. >>Excellent customers always want choice. Come on. Give me your perspective. You were at the helm the ceo of stack rocks as you were last time you were on the cube. Talk to me about the redhead acquisition from your seat. >>Yeah. So as as Kirsten mentioned, we were partners of red hat. You're part of the red hat partner ecosystem. And uh, what we found is that was both a great strategic fit and a great cultural fit between our two companies. Right? And so the discussions that we had were how do we go and quickly enable our customers to accelerate their digital transformation initiatives to move workloads to the cloud, to containerized them, to manage them through kubernetes and make sure that we seamlessly addressed their security concerns. Right? Because it continues to be the number one concern for large enterprises and medium sized enterprises and frankly any enterprise that uh, you know, uh, working out today. So, so that was kind of the impetus behind it. And I must say that so far the the acquisition has been going on very smoothly. So we had two months in roughly and everybody and has been very welcoming, very collaborative, very supportive. And we are already working hand in hand to to integrate our companies and to make sure that we are working closely together to make our customers successful. >>Excellent. We're gonna talk about that integration in a second. But I can imagine challenging going through an acquisition during a global pandemic. Um but that is one of the things that I think lends itself to the cultural alignment. Kamal that you talked about, Kirsten. I want to get your perspective. We know we talk about corporate culture and corporate culture has changed a lot in the last year with everybody or so many of us being remote. Talk to me about kind of the core values that red hat and stack rocks share >>actually, you know, that's been one of the great joys doing during the acquisition process in particular, Kamal and and ali shared kind of their key values and how they um how they talked to talk with their team And some of the overlap was just so resonated so much for all of us. In particular the sense of transparency, uh, that the, that the team the stack rocks executive team brings and approaches. That's a that's a clear value for red hat um strongly maintained. Uh, that was one of the key things the interest in um uh, containers and kubernetes. Right. So the technology alignment was very clear. We probably wouldn't have proceeded without that. But again, um and I think the investment in people and the independence and the and the strong drive of the individuals and supporting the individuals as they contribute to the offering so that it really creates that sense of community um and collaboration that is key. Uh and and it's just really strong overlap in in cultural values and we so appreciated that >>community and collaboration couldn't be more important these days. And ultimately the winner is the customers. So let's dig in. Let's talk about what stack rocks brings to open shift Kirsten take it away >>man. So as I said earlier, um so I think we we really believe in continuous security at red hat and in defense and depth. And so when we look at an enterprise kubernetes distribution that involves security at the real core os layer security and kubernetes adding the things into the distribution, making sure they're there by default, that any distribution needs to be secured to be hardened, auditing, logging, identity, access management, just a wealth of things. And Red hat has historically focused on infrastructure and platform security, building those capabilities into what we bring to market stack rocks enhances what we already have and really adds workload protection, which is really when it comes down to it. Especially if you're looking at hybrid cloud, multi cloud, how you secure, not just the platform, but how you secure your workloads changes. And we're moving from a world where, you know, you're deploying anti virus or malware scanners on your VMS and your host operating system to a world where those work clothes may be very short lived. And if they aren't secured from the get go, you miss your opportunity to secure them right? You can't rely on, you know, you do need controls in the infrastructure but they need to be kubernetes native controls and you need to shift that security left. Right? You never patch a running container. You always have to rebuild and redeploy if you patch the running container the next time that container images deployed, you've missed, you've lost that patch. And so the whole ethos the whole shift left. The Deb sec ops capabilities that stack rock springs really adds such value. Right? You can't just do DEF SEc or set cops. You need to do a full infinity loop to really have def SEc ops and stack rocks. I'm gonna let Kamal tell you about it, but they have so many capabilities that that really drive that shift left and enable that closed loop. We're just so excited that they're part of our offerings. >>So can you take us through that? How does stack rocks facilitate the shift left? >>Yeah, absolutely. So stack rocks, which we we announced at summit is now being rebranded as red hat. Advanced cluster security was really purpose built to help our customers address the use cases across the entire application lifecycle. Right? So from bill to deploy to run time. So this is the infinite loop that Kirsten mentioned earlier and one of our foundations was to be kubernetes native to ensure that security is really built into the application is supposed to bolt it on. So specifically, we help our customers shift left by securing the supply chain and we're making sure that we identifying vulnerabilities early during the build process before they make it to a production environment. We helped them secure the infrastructure by preventing miS configurations again early in the process because as we all know, MIS configurations often lead to breaches at at runtime. Right? We help them address uh compliance requirements by ensuring that we can check for CS benchmarks are regulatory requirements around the C I P C I, hip hop and this and and that's uh you know, just focusing on shift left, doesn't really mean that you ignore the right side or ignore the controls you need uh when your applications are running in production. So we help them secure that at runtime by identifying preventing breaches the threat detection, prevention and incident response. >>That built in security is you both mentioned that built in versus bolt on Kirsten? Talk to me about that, that as really kind of a door opener. We talked a lot about security issues, especially in the last year. I don't know how many times we've talked about miS configurations leading to breaches that we've seen so many security challenges present in the last year. We talked to me a little bit Kirsten about >>what >>customers appetites are for going. All right now, I've got cloud native security, I'm going to be able to, I'm going to feel more comfortable with rolling out production deployments. >>It's, it's a great place to go. So there are a number of elements to think about. And if I could, I could, I could start with by building on the example that Kamal said, Right, So when we think about um I need to build security into my pipeline so that when I deliver my containerized workloads, they're secure. What if I miss a step or what if a new vulnerability is discovered after the fact? Right. So one of the things that stack rocks or redhead a CS offers is it has built in policy checks to see whether a container or running image has something like a package manager in it. Well, a package manager can be used to load software that is not delivered with the container. And so the idea of ensuring that you are including workload, built in workload, protect locks with policies that are written for you. So you can focus on building your applications. You don't necessarily have to learn everything there is to know about the new attack vectors that are really just it it's new packaging, it's new technology. It's not so much there are some new attack vectors, but mostly it's a new way of delivering and running your applications. That requires some changes to how you implement your security policies. And so ensuring that you have the tools and the technology that you're running on have those capabilities built in. So that when we have conversations with our security conscious customers, we can talk with them about the attack vectors they care about. We can illustrate how we are addressing those particular concerns. Right? One of them being malware in a container, we can look for stack. Rocks can look for a package manager that could be used to pull in, you know, code that could be exploited and you can stop a running container. Um, we can do deeper data collection with stack rocks. Again, one of the challenges when you're looking at moving your security capabilities from a traditional application environment is containers come and go all the time. In a kubernetes cluster nodes, your servers can come and go in a cloud native kubernetes cluster, right? If you're running on on cloud public cloud infrastructure, um, those things are the nodes are ephemeral to, they're designed to be shut down and brought back up. So you've got a lot more data that you need to collect and that you need to analyze and you need to correlate the information between these. Right? I no longer have one application stack running on one or more VMS, it's just things are things are moving fast so you want the right type of data collection and the right correlation to have good visibility into your environment. >>And if I can just build on that a little bit. The whole idea here is that these policies really serve as god rails right for the developers. So the it allows developers to move quickly to accelerate the speed of development without having to worry about hundreds of potential security issues because there are guardrails that will notify that with concrete recommendations early in the process. And the analogy I often use is that you know the reason we have breaks in our cars, it's not to slow us down but to allow us to go faster because we know we can slow down when we need to write. So similarly these policies are really it's really designed to accelerate the speed of development and accelerate digital transformation initiatives that our customers are embarking on >>and come on. I want to stick with you on the digital transformation front. We've talked so much about how accelerated that has been in the last year with everything going on in such a dynamic market. Talk to me Kamal about some of the feedback that you've gotten from stack rocks customers about the acquisition and how it is that maybe that facilitator of the many pivots that businesses have had to do in the last year to go from survival mode to thriving business. >>Yeah. Yes, absolutely. The feedback from all of our customers bar none has been very very positive. So it's been it's allowed us to invest more in the business and you know, we publicly stated that we are going to invest more in adding more capabilities. We are more than doubling the size of our teams as an example. And really working hand in hand with our uh the broader team at Red had to uh further accelerate the speed of development and digital transformation initiatives. So it's been extremely positive because we're adding more resources, We're investing more. We're accelerating the product roadmap uh based on uh compared to what we could do as a, as a start up as you can imagine. And and the feedback has been nothing but positive. So that's kind of where we are today. And what we're doing with the summit is rolling out a new bundle called open shift uh, Open shift platform plus, which includes not just Red hat A CS which used to be Stock rocks, but also red hat open shift hybrid cloud platform as well as Red hat advanced uh container cluster management, ACM capabilities as well as create the container registry. So we're making it easier for our customers to get all the capabilities that they need to for the drive digital transformation initiatives to get. It goes back to this whole customer centric city team that red hat has, that was also core value of stack rocks and and the winner and all of this, we believe ultimately is our, our our customers because that's where we exist to serve them, >>right. And I really like that if I could chime in kind of on top of that a little bit. Um so, so I think that one of the things we've seen with the pandemic is more of the red Hat customers are accelerating their move to public cloud and away from on premises data centers. Uh and and you know, that's just part partly because of so many people working remotely. Um it just has really pushed things. And so with Hybrid cloud becoming even more key to our joint customer base and by hybrid cloud, I mean that they have some environments that are on premises as they're making this transition. Some of those environments may stay that footprint may stay on premises, but it might be smaller, they may not have settled on a single public cloud. They could, in fact, they often are picking a public cloud based on where their development focuses. Google is very popular for ai and ml workloads. Amazon of course is just used, you know, by pretty much everybody. Um and then Azzurri is popular with um a subset of customers as well. And so we see our customers investing in all of these environments and stack rocks red hat A CS like open shift runs in all these environments. So with open shift platform plus you get a complete solution that helps with multi cluster management with a C. M with security across all of these environments, right? You can take one approach to how you secure your cluster, how you secure your workloads, how you manage configurations, You get one approach no matter where you're running your containers and kubernetes platform when you're doing this with open shift platform plus. So you also get portability. If today you want to be running an amazon maybe tomorrow you need to spin up a cluster in google, you can do that if you're working with the K s or G K E, you can or a Ks, you can do that with red hat a CS as well. So we really give you everything you need to be successful in this move and we give you back to that choice word, right? We give you the opportunity to choose and to migrate at the speed that works for you. >>So that's simplicity. That streamlining. I gotta ask you the last question here in our last couple of minutes. Come on, what's the integration process been like? as we said the acquisition just a couple of months in. But talk to me about that integration process. What that's been like? >>Yeah, absolutely. So as I mentioned earlier, the process has been very smooth so far, so two months in and it's largely driven by the common set of culture and core values that exists between our two companies. And so uh you know, from a product standpoint, we've been working hand in hand because I mentioned earlier, we were partners are working hand in hand on accelerating the road map the joint roadmap that we have here uh from a go to market perspective teams are well integrated. We are going to be rolling out the rolling out the bundle and we're gonna be rolling out additional uh options for our customers. We've also publicly announced that will be open sourcing uh red hat A. C. S. Uh formerly known as Stock Rock. So stay tuned for further news and that announcement. And, and so you know, uh, again two months and everybody's been super collaborative. Super helpful, super welcoming. And the team is the well settled and we're looking forward to now focusing on our primary objective is just to make sure that our customers are successful. >>Absolutely. That customer focus is absolutely critical. But also so is the employee experience. And it sounds like we both talked about the ethos and the and the core value alignment. They're probably being pretty critical to doing an integration during a very challenging time globally. I appreciate both of you joining me on the program today, sharing what's going on stack rocks now asks the opportunities for customers to have that built in cuBA and the security. Thanks so much for your time. >>Thank you. Thank >>you for Camel shaw and Kirsten newcomer. I'm lisa martin. You're watching the cubes coverage of Red Hat Summit, The virtual experience. Mhm

[Music] welcome back to red hat summit 2021 my name is dave vellante and you're watching the cube where we go out to the events and extract the signal from the noise of course virtually in this case and i'm pleased to welcome victor carumpus who is the senior vice president of digital banking at bank mandiri coming in from jakarta welcome to the cube victor great to see you hi dave great to see you and great to be invited here thank you yeah you're very welcome i i wonder if you could just give us an overview of the bank maybe talk a little bit about your strategy your customers you know what the what the focus is of your company and what your role is there okay uh maybe i'm i'll give a short overview about bang mandir itself so bang money is a state-owned enterprise owned by the government but we also public company currently we already have a very big distribution channel in so uh you know indonesia is an island country it's very huge country so we are we are representing all over indonesia from province of aceh and i'm up to profits of papua and we have about 2600 branches all over indonesia and about uh 15 000 atms all over indonesia so bangladesh itself is focused on a lot of segment customers like indonesia from the corporate side small medium enterprise and also retail banking now uh we are we are currently focused in turning ourselves to become having to have more digital capability and currently in our uh current situations actually it is very good uh about 95 percent of our transactions is already coming from the electronic channel so it's only about five percent that coming from the branches but we know that this is still a journey uh and we are building more digital capability and features and functions on our digital channels to our customer got it um okay and so your your your digital journey kind of coincides i guess in a way with your your your container uh adoption journey uh i think that started a few years ago um and so maybe you could talk a little bit about that i i mean in thinking about modernizing your application portfolio obviously containers been around forever but they weren't packaged in a way that could actually be easily you know utilized and now you're seeing people in i.t roles like yourself really leaning in maybe you could talk about some of the technology considerations that impacted that desire to actually leverage containers i think uh first it's about the scalability because with a monolithic architecture it's kind of difficult to scale up for only specific features by doing container microservices we have options to scale up in a very fast way because one of the features is auto scaling on the container architectures uh one monitor is a very focused on the transaction banking so you might say bangladesh is supporting the economy of the country because in a in any given time in bangladesh we we're running about four thousand transactions per seconds that's a huge transactions number and have having said that uh our channel like i told you already running about 95 percent of the transactions so scalability is always important for us because especially like like now is the the in indonesia is a festive month it's a ramadan month where muslim is actually doing fasting but at the same time actually there's a lot of needs and people do a lot of transactions and on this kind of festive seasons the transition can be increased up to 40 or 50 suddenly and that's kind of things always happen in bangladesh and we must be ready and we must have a scalability on demand now containerization is enabling us to do that other thing is about flexibility because on the old days actually when we want to set up a new environment it's very difficult and takes a lot of time and that's affecting the time to market our products by doing the containerizations and putting it on a ci cd continuous integration called the development plan platform we are we call devsecops platform that kind of things becoming automatic because we set up the devsecos platform and the third one is the consistency actually so by by doing the contact investigations we can put the the apis on our back-end apis in the container itself and actually it's deliverable environment and a consistent experience to our customer because for example we promise our customer that every transaction should be finished within two seconds from their mobile banking up to our hosts and back forward to their mobile banking is only two seconds so that kind of thing is driving us to move to the current technology which we're using containerization and micro services great okay so 4 000 transactions per second you can't can't do that on erc20 ethereum for all you crypto fans out there that's that's pretty high volume uh and if i understand it correctly victor your role is really to envision this digital environment and then ultimately make it happen from a technology standpoint is that correct that's product that's got it yeah so okay so you now have a number of of product lines and teams you're using the same container platform maybe you could share with our audience some of the best practices and learnings that that you've taken away on this journey so i think first of all we can reuse a lot of components by doing this containerization platform is different when we still use the monolithic platform like the application server of java application server uh by using containerization actually uh be providing like a service banking as a service so whenever we build a new channel for example the first one we built a new service for example like a fun transfer service but when we create another channel for example a corporate banking electronic channel or we create another uh let's say wealth management channel whatever we already built before can be reusable instantly by using this technology so uh if i might say that actually there is a lot of best practices coming by using this platform and my team get a lot of benefit in terms of faster development time and also they can deliver the product and service in a high quality manner minimize the number of errors as well you know there's a lot of choices out there obviously i wonder if you could share what led you to the choice of red hat and open shift okay so first of all before we choose the platform actually we also comparing ourselves with the with the fintechs and also with the big tech in indonesia as well so we see we see that actually they already start using kubernetes and uh their platform is quite stable and even they can support about 90 to 100 million of customers without any issues at all so when we see this uh we choose a lot of we learn about a lot of platform and we finally choose opencv because we think that openshift and we we already do our research openshift is quite stable and for banks like us that have for having 4500 transaction per seconds stability is number one uh availability is also number one now uh having said that after doing our research we choose openshift and we implemented openshift in our environment because we promise our customers to provide 99.95 percent uh availability can i just i'm sorry to interrupt you victor can you just repeat that you cut out a little bit so you you said you you promised your customers to deliver and then you cut out a little bit can you just repeat what you just said there okay so we're giving a promise to our to our customer providing a 99.95 availability so this is the starting point of our channel sure in the efficiency we have efficient also to providing four nines which is 99.99 but i mean the starting point is 99.95 and because we have that the demand that requirement that's one of the reason we choose the openshift and red hat as our technology stack platform got it okay and so i have a question um what was it like in terms of just the skills and the adoption uh for your developers uh was it was it a big gap to go from where you were to you know where you are today did you have to what kind of training did you have to do did you have to do any sort of outsourcing to accelerate that maybe you could describe that how you close that skills gap so definitely in the beginning is quite challenging because although they are using modern languages like jaffa or kotlin but uh to understand the concept and to design correctly yes we we did a lot of training to them uh it takes a it takes me about three months to give them the proper training uh in terms of building the right uh microservices platform and also to building modular architecture in terms of the customer channel because this will be the fundamental when you build it correctly in the beginning and actually at the later point you will enjoy the benefit so the first three months actually is training and doing research and development and doing a lot of trial and errors but after the three months actually we already have the right technology stack have the right models and our devsecops is already working then actually after that the speed is very fast because uh it sprints uh we do agile way of working the agiles dlc it's only one month so every one month we already have new features coming in so that's what we call a huge transformation a digital transformation inside of our bank it's three months actually not bad i mean i would i would have thought on average it's going to take five or six months to get people up to speed so three months is pretty good and i'm also inferring that you weren't just paving the cow path you weren't just saying okay let's take our traditional and then you know re refactor it to digital you had to re-envision what digital looked like because the digital is different uh than the traditional uh so so that's actually pretty good uh ramp rate i wonder if you could just go ahead and comment if you could because when you say about uh revamp so actually it's not on the id side not only but also the business side we implement new way as well so actually if clearly they're implementing a new model so they're using a design thinking and also a co-creation model where now when we building a product so we're not writing the old product in a new way no we totally building it from from scratch and involving our key customer and our stakeholder when we're building this product so actually we implementing new models what we call design thinking and also uh co-creation with our customer so that's actually changing the face of the customer electronic channel a lot and and actually when we when we want to to deploy we invite our customer to test it first we call it like usability testing if they like it we continue to design if they they don't like it they give us a feedback how they would like it to be changed and and that's we appreciate our customer feedback because customers experience is everything now yeah so so the product can be accepted if the experience on that product is really making customer uh solving their problem solving the customer problem and making them enjoying uh doing transactions in our mobile banking product i think this is a really important point for people to understand so you weren't just paving the cow path i call it you're taking the old and and just trying to refactor it and make it exactly turn it into digital you had to really think about the business the business processes the dependencies the customer experience and then bring it back um what have been some of the business outcomes of this initiative and maybe you could we then after that we can get into some of the the future plans so so the outcome uh i think this journey uh since last year uh not last year actually since no october 2019 we already started the journey uh what took us by surprise is actually the pandemic uh suddenly the first three months when we have the pandemic of coffee we are being forced to close a lot of branches for temporary because we want to avoid the pandemic situations and that time actually the the demand using our digital channel is increasing a lot but because we already prepared actually we get the benefit one of the thing is uh the business benefit is relating so during the pandemic nobody can come to the branch and mostly the account opening actually happening online so uh we even got about 9000 account opening per day which is something that we are not imagining before so uh the benefit is very clear by using this this technology actually enabling us to provide digital capability for our customer and enabling us to open more accounts we see ourselves can grow even not linear but exponentially grow by using this platform uh talking about that indonesia is a is a huge country with we have about 200 250 million populations and actually there's still a lot of people is not having a bank account at all now by doing this actually we open opportunity doing financial inclusion for those people that need a banking account now they can reach us by using the digital platform as well yeah that's an awesome story and it goes back to the to the reason the real motivator for for moving to kubernetes and containers was scale uh and and you know it's you obviously started your digital journey prior to the pandemic but a lot of customers and i'm sure you as well were were forced to speed up a portion anyway of the digital component uh because of the pandemic like you said you couldn't people couldn't walk into the branches so but now you've got some more time to think about that journey you've had a lot of learnings 2020 was like a petri dish of experimentation but but in real time having to serve customers what's the future look like for the bank's technology journey okay so basically we uh we are not stopping only on the retail side yeah uh we want to redefine our customer journey also on the wholesale side and also on the small medium enterprise there is still a lot of things that need to be done uh and required by the customer actually so uh on the on the on the sme side we want to give them easier access uh for uh financing their businesses i think when we are back to the new normal uh the business need to have funding for for starting their business again so building an sme platform for them will will help a lot and will help the country as well on the retail side actually like i told you uh we are focusing on the more financial inclusion because uh i give you example right uh from the 230 million of indonesians uh populations i think by today maybe it's only about 50 million customers that already have a banking account so there is still a lot of people that need an access faster and cheaper and more efficient way for doing banking transactions so that's this also will become our focus and the last part is actually corporate what we see now a lot of the corporate require us to open uh api connectivity doing open banking with them the government actually the central bank supporting it supporting all the banks they are trying to create an api playbooks now and then they create they want to create an api standard for all the core all the use corporate also can connect it to the bank directly using api so this is also our focus because it will help the country economy when the economy costs the transaction costs getting more efficient getting more cheaper and there's a lot of transaction can be supported by our bank as well so i think i think that's the the future that we are imagining and i'm really hope that the pandemi will be finished and we come back to the to the new normal and we can support more transactions for this country yeah you're here to that i call it the new abnormal but so this is this is a great story everybody loves to talk about disruption we do as well and but people think oh it's out with out with the old in with the new and it's not like that this is a great story victor of uh of an established incumbent that is modernizing its its applications and its digital experience and of course the incumbent has the advantage of it's a real business it has customers that has a data it has experiences it and if it can modernize its infrastructure and and it's in its application portfolio it actually has an advantage because it's got way more features way more data way more customers and more resources so victor thanks so much for coming on thecube i really appreciate you sharing your story thank you dave thank you for inviting me thank you that was our pleasure and thank you for watching red hat summit 21 this is thecube you

(upbeat music) >> Hello, and welcome back to theCUBE's coverage of Red Hat Summit 2021 Virtual. I'm John Furrier, host of theCUBE. We got a great guest here, Raymond Kok, Senior Vice President Cloud Application Solutions at Siemens Digital Industry Software. Raymond, thanks for remoting in with theCUBE Virtual all the way from the Netherlands. Great to see you. We're in Palo Alto, California. Great to see you. >> All right, thanks for having me. >> Love the international culture of the vibe with virtual, one of the benefits of having remote, which we were in person, but soon the pandemics coming around the corner, but great to see you. Let's get started, let's get into the Digital Industry Software Group that you're involved in, your relationship with Red Hat. But first let's start with, if you could take a minute to give us a brief overview of Siemens and your role there. >> Yeah, so first of all, let me talk a little bit about Siemens because Siemens is obviously a big company. So as you already announced, I'm part of Siemens Digital Industries Software. So Digital Industries is actually the vision at Siemens that is really focused on how to help companies to become a digital enterprise. And so as part of this IoT (faintly speaking) Industrial Internet of Things is obviously an important element of that. And so if you look at my role at Siemens, is really to be the business lead for the cloud part of IoT. And so what I mean with that is specifically a product line called MindSphere. And so Siemens, like I said, is looking at the overall digital transformation of customers, relay product landscape but also how we can support them with new technologies and IoT is very much part of that. >> One of the benefits of doing theCUBE interviews over the years and having the team that we have in the media side, we get to see things early. Industrial IoT, we've been blogging about and reporting for a couple of years now, now it's hard. Because with the pandemic, you still need things to run. And so Industrial IoT, not withstanding, there's still the other edges like consumer edge and other devices, but Industrial IoT is getting all the focus because of security and also because of just critical operations, critical infrastructure and for business and public sector, private sector, everything. This is a huge area. Could you talk about your strategy around Industrial IoT and specifically how you guys are using this analytics, MindSphere as you mentioned, what is that about? How does that help me if I'm a manufacturing organization? >> Yeah, so first of all, maybe it's good to clarify what we mean with Industrial IoT, because there's IoT and there's Industrial IoT. So, when people typically talk about Industrial IoT, it's really three main areas. It's smart grid. So it's really around IoT for energy management and energy usage. There is smart cities. So this is really IoT for smart buildings but also any kind of infrastructure that goes with smart cities. And then the last one is smart factories. And so, we typically, when we say Industrial IoT, we have clients that cover the three main areas that I just mentioned. And so really what it is about is to take advantage of data, right? So IoT is really about how you take advantage of data and how do you actually get insights from this data to run your business better? So maybe to give a specific example, if you look at one of our major customers, like for example, Coke Hellenic, and they just actually presented that (mumbles) last week. They are trying to use IoT to advance how they actually operate the bottling lines of the factories. And so it's really above operational excellence. So, meaning how to get more trooper, how to get more efficiency into how they do production. But in many cases, John, it's also about energy management because data is not just about, okay, operational excellence but also surrounding topics like, how can I better preserve energy as I produce something? And so, yeah. So in many cases, IoT is all about data, getting next levels of insight from the data and then put that to a particular use. So this can be answering the quality of production, getting better performance of your equipment, getting a better use of your equipment when it comes to energy consumption. So there are many use cases typically related to Industrial IoT. >> Yeah, and you got to love the industrial definition to the way you laid it out. That's critical infrastructure and emerging infrastructure and plant and equipment, all those things. But it's also a proxy for (faintly speaking) for business. So this kind of brings me to the kind of connecting the dots. If you don't mind, I'll jump to the convergence question I'd love to bring up, which is the convergence of IT, Information Technology and Operational Technology, OT, which has been discussed before, but you talked about culture clashes, different cultures. Also systems are different, purpose-built, potentially on one side, but they've got to come together, okay? These are both very important software pieces to the puzzle on the platform. How do you see that evolving? What's your take on resolving this dilemma of the priorities, of innovation and security and openness? What's your take on this? >> (Faintly speaking) Topic, John, because the reality is that OT has to ITinice and IT has to OTinice I guess, when we talk about IoT, right? So I think that's why at Siemens, we have kind of a unique viewpoint because Siemens looks at both the OT side of the world through, for example the context of discrete, the process industries look at the automation part of it, so meaning the actual operational automation and then obviously only equipment that comes with it, which is really typically an OT conversation. Then if you look at my business unit, so, Siemens Digital Industries Software, we look at it really from an IT point of view, and so how can we help these customers to become a digital enterprise? And so at Siemens, we're kind of bringing these two views together. And then to your point, we're trying to make the integration as seamless as possible. And to your point actually, it includes also making sure that we actually drive the standards that are going to make this enable, that are going to make this possible, can be open standards like OPC UA, for example, when you look at discrete manufacturing, but can also be standardizing on certain technologies, right? And so what we're seeing is that, for example, back to my word, talking is really Kubernetes and kind of the container technology that is out there, standard technology is helping this conversation as well. >> Yeah, the integration piece, that's the Kubernetes, containers and micro services. These are bringing cloud native integration points. And that's really going to be key, I'm going to get that in a second, but I want to come back to the MindSphere Analytics piece because data is critical as you mentioned. So integration data security and observability means security, monitoring all these things are evolving. You guys earlier this year, announced you expanding this MindSphere reach in partnership with IBM and Red Hat, so consumers could run on on-prem and cloud. That's the topic of this event. The main theme at Red Hat Summit this year is clearly hybrid cloud, in a distributed kind of computing paradigm which we all love. This is what we're talking about here. We're talking about distributed computing edge, Core Cloud. Why is this important for Siemens and your customers? Why did you decide to work with IBM and Red Hat on this initiative? >> Yeah, it kind of was already somewhat in your question, meaning that if we work with our customers, really the cloud conversation that we have with them is a hybrid cloud conversation. And what we mean with that is, yes, there're elements of public clouds, but especially when you talk about critical factory operations, many of these workloads that we're talking about are actually very close to the shop floor or are at least some what near, and therefore any kind of large enterprise OEM that we work with, so whether it's an automotive OEM, whether it's an aerospace and defense OEM, they all have a hybrid cloud strategy. And so what is interesting about IoT is that this is where hybrid cloud kind of comes together. It kind of goes back to your previous question about IT and OT coming together. As you can imagine OT has always been very on-premise because it's near real time critical factory operations. IT obviously much more comfortable with public cloud. So we're trying to bring this together and therefore, many of these conversations that we have with large enterprise OEMs is really a hybrid cloud conversation. So specifically, what we're doing here together with Red Hat is to enable exactly that. So meaning that we can take MindSphere or solution for IoT Analytics, we can bring that not just to a public cloud or make that available as a public cloud solution, but also on-premise private clouds. And I think it's very interesting because it opens a conversation that allows people to really now start talking about value as opposed to being worried about, okay, where is my data going? Is it secure? Is it actually going to be available when I need it for factory operations? So, yeah, I'm pretty excited about this work that we're doing together, because again, it's about value, making sure that our customers actually can fit what we do at Siemens into a landscape that they feel comfortable with. >> It feels to me, I may be a little bit old school but I feel like this is the innovation that we saw in the eighties and nineties as networks got more expansive and inter networking happened and you start to see that life blood of the action and the value get enabled. And I think your point about hybrid and operating around the environment is critical, because this brings up new challenges and new opportunities. For instance, you don't need to bolt on a caching layer to manage a slow database or you can get real time, and you can get better performance and compute. You don't need to move the data around. So, bringing compute and resource and scale to these edges when they need it, focuses more on the solution architect less on putting point technologies in place to solve. >> Yeah, exactly. Maybe to chime in on that, I think what is also interesting is that it allows the customers to optimize where to best place the workloads that they care about. And so maybe to make that a bit more specific, if you think about a use case like energy management. So let's say that I have a production line, 1500 assets that are consuming energy. If you then think about the data that is involved in analytics, you can imagine that if I start sending all this data to public cloud, maybe, maybe not the most efficient setup, because a first level of filtering and analytics, I can very much close do or do that close to a 2D equipment. And then when I get to aggregation of data, and some further filtering to figure out, okay, what is really happening at the line level? What is really happening at a particular production area level? Again, I think you can do that prior to actually sending some of this data to the cloud, meaning public cloud. Where the public cloud becomes interesting is when you want to aggregate, for example across multiple manufacturing facilities. Now you want to look at the KPIs of one factory versus another, you want to aggregate across multiple factories, you want to figure out, okay, why are certain trends happening just in this factory and it's better in this one? But I think that's why, what we're seeing with clients is that they're expecting from us a layered architecture and to your point, the most efficient way of actually dealing with their use cases across the infrastructure that is available to them. So yeah, if you look at Siemens, we're trying to kind of carefully think about all these layers from fields to edge, to on-premise private cloud, to public clouds, and then make sure that along the way each layer has value and that it's there for a purpose and for a real reason, right? And not just for the sake of having it. >> Yeah, or being limited by the architecture that you're stuck with, constrained by the architecture by what the solutions are. You're saying, the script is flipped upside down where you can optimize your business, which by the way will flow up more data to evaluate. So there's a new post analysis mode of post configuration, and you could align your resources best way you see fit to maximize your business model. This is the beautiful thing about this distributed edge concept is the software enablement of the business is there. So the data is critical. So, as more controlled data comes in, it's not just set it up and watch it run. Yeah, there's automation involved in a lot of software but you're getting new data coming in. If you have this new observation space, of new horizontally scalable data, this new data coming in. >> Yeah, exactly, exactly. And I think you said a key point there. We don't want our architecture to constrain. I guess, what kind of value the customer can actually get out of these use cases and therefore, I think it's kind of exciting that in this ecosystem, especially also the interplay between Red Hat and Siemens, that we kind of take it one step further and think about, okay, what is actually truly the most optimal way for customers to go do this? And that we've formed these kinds of partnerships to really help the customer even take another step forward. So I think it's pretty, pretty nice. >> Well, Raymond, I really appreciate it. That's a masterclass, a commentary, nice gems you're dropping here on theCUBE, I appreciate it. The way I look at it, I'd love to get your final reaction to kind of the world we're living in. Just my take on it is that, we have a new operating system of business, and we're kind of getting at, is that you guys now can have an operating model for your customers and software. It's not just another (faintly speaking) For a server and the server is the business, it's the world now. >> Yeah, exactly. And I think from my point of view, I think it's exciting to see us again in this world of complex technology always to find new ways to help the customer to kind of advance their use cases, right? Because the imperatives that, for example discreet manufacturing doesn't really change. They've been there for many, many years. And I think for us to be able to bring out technology closer together and then solve, and I do use use cases in an even more efficient way. I think that's pretty interesting. And yeah, so I see good things and I think ultimately IoT, I think those that can actually bring real value are going to be able to deal like we just talked about, the hybrid scenarios, but the people that are going to matter is the people that can bring the most insights out of this data, right? Because what I always say about IoT is, it's yet more a messy data. So it's only worth actually collecting all this data if you actually get next to levels and new levels of insight from it. And I think, yeah, it has to kind of fit that kind of a mantra, and I think together that we're really trying to figure that out, so- >> I know some people as well would agree with that statement, I do as well, but the other side of that question is, if you don't architect the edge properly or the IoT edge, the data costs could be compelling. You could get hit with some charges because most people have been burned by the idea of moving data around versus say, moving compute. So, back to this value, where's the edge? What're you optimizing for? That's kind of the big question. How do you react to that when someone says, Raymond, what should I be optimizing for as I lay out my architecture for the core to edge, data center cloud edge scenario, what am I optimizing for? >> Yeah, I think you kind of work backwards from what you're trying to achieve. I think it may sound kind of obvious, but quite often I get in discussions with customers where we first start talking technology, obviously it's exciting. I'll be kind of attacking myself. So it's exciting to talk about technology but they forget to start from, okay, what's the return of the invest and what's the use case, right? And so, what are we trying to solve? Who is trying to benefit from it? And what benefit are they looking for? And then if you carefully work backwards from there, you will actually see that as we just talk about data and insights into data are in many cases, leading some elements of the value that a particular person is looking for. And then working backwards from there, you will actually figure out that back to the layer of discussion that we just had, this data doesn't have to be available at every level, right? Every layer adds some value, and so therefore you have to have kind of an open discussion and that's meaning an open discussion about what layers to use. And that's why at Siemens, we kind of follow that approach. So meaning that we work backwards from the use case, then we think about, okay, what is most appropriate at the field and control level? Then what to your point, is the most appropriate at the edge level? Then what is the most appropriate at the cloud level? And then from there, you actually figure out, okay, where do I deploy? What kind of acquisition of data? What kind of insights am I interested in at that level? And then basically, what kind of machine learning am I going to deploy there? And then work all the way from there. And it seems to work. And that's why to your point, it's all about making sure that at every level data is there for a reason and you process it for a reason, because otherwise it's just acknowledging it, interesting still, but it doesn't have any value, right? >> Awesome. Raymond, great insight there. And this is all about engineering. You guys are doing a great job. Engineering, the solutions, this is DevOps, DevSecOps, it's some hybrid cloud, really bringing those that value to the edge, industrial edge. Congratulations for all the great work. Raymond Kok, Senior Vice President, Cloud Application Solutions at Siemens Digital Industries Software. Thanks for coming on theCUBE. >> Okay, yeah. Thanks for having me. >> Okay. >> Thank you. >> I'm John Furrier with theCUBE, Red Hat Summit 2021 Virtual. Thanks for watching. (upbeat music)

(Upbeat music) >> Okay, welcome back everyone, to theCUBE's Coverage of Red Hat Summit 2021 virtual I'm John Furrier, your host of theCUBE got two great guests from Deloitte Consulting Dave Knight who manages the Red Hat Relationship, Lee he's the lead there, and Mike Bourgeois who's the Public Sector Managing Director both from Deloitte Consulting LLP official name. Guys, great to come on, and we were just talking before camera about all the stories. Great to have you on theCUBE, thanks for coming on. >> Yeah, thanks for having me. >> Like I said we were just talking about all the stories from the transition from pre-COVID, COVID. Now we've got a view into post-COVID. I want to dig into that 'cause there's a lot of things happening. You guys have been in the trenches, front lines bringing solutions, but before we get into that, can you guys just introduce yourself share your roles at Deloitte and give us a quick overview of what you work on. >> Yeah, so again, thanks for having us John Dave Knight I'm a solution architect and Global Red Hat Alliance Manager for Deloitte. I've got responsibility for making sure that play nicely in the sandbox together or we've got a joint customer and solutions to deliver to those customers. >> Hi everyone, thanks for having us John, I'm a Managing Director Mike Bushwa out of Boston Texas. I am coming up on year 20 and Public Sector Consulting. My area of expertise is large state government systems that serve the needs of millions of citizens and thousands of state workers, good to be here. >> Yeah. Great to have you. And I wanted to chime in with you right away because Mike you are living in probably one of the hottest markets Public Sector. I've been following that for many, many years, generations actually from the early computer industry GSA contracts, all these contracts you've got all the Public Sector, they move very slowly but now the pandemic, there was no place to hide. Everything got pulled back, disruption, you can't just shut down critical infrastructure and critical services. People had to move fast. What was your experience and how is it now give us a taste of some of the challenges and the landscape. >> You bet John, so we talked a little bit before we started this, but my 20 year consulting career, I can't think of anything really in close to this, other than maybe Y2K and as Dave mentioned the Affordable Care Act Legislation in 2009, though that was a much smaller scale as it turned out to be. So I would be remiss not to share examples of extraordinary challenges our clients have had related to the pandemic. Department of Labor and Health and Human Service Agencies for example, responded to the pandemic in rapid timeframe that were rarely seen in government. Citizens that were used to coming in appealed offices, We're now required to do most things virtually. Deloitte has been privileged to assist clients with digital solutions across the country in response to this unprecedented event. And so I'd like to share just a couple of examples. The first is for Department of Labor, the pandemic contributed to millions of layoffs throughout the country Department of Labor workers found called volumes increasing by a 1000% in some cases, the amount of increased volume required agencies across the country hire temporary workers to help out. Millions of new unemployment claims needed to be filed in benefits rapidly provided to citizens of name. So the big challenge was the agency had to figure out how to rapidly file claims into the unemployment system, rather than requiring new citizens to use an external web application they were really unfamiliar, the agency needed more efficient approach. The approach we used was to create an internal web application that enabled workers to file unemployment insurance claims on behalf of citizens. Workers collected the necessary data from citizens and claims were filed into the system. The application enabled workers to focus on filing claims rather than sort of a technical support role showing how to people use an external web application. More citizen were served in much less time, claims are filed efficiently by train workers which resulted in benefits being received in a much more timely fashion. And so a second example is, with Department of Human Services. So one stay as mentioned Citizens were used to going into field offices but suddenly they were told you can't come into the field office. So once they provided a 100% virtual application and the important part here is certification solution for the Disaster Supplemental Nutrition Assistance Program or DSNAP for short. this application was stood up in two weeks, families who needed food assistance can now apply and be certified for benefits remotely. Today over 50,000 cases have certified and citizens receiving food nutrition assistance. Back to you John. >> So, I mean obviously there's some great use cases you got, basically I got to work at home, new architecture there you got to have a new workflows. I mean, this poses some real challenges. How did you guys put it together? I mean, Dave take us through where this all fits in with the Red Hat, because obviously now it's new deployment new capabilities have to be deployed for the pandemic. How does this bring together the partnership with Red Hat? >> Yeah, so great question and it really plays to the strength of both Deloitte and Red Hat, right? The success stories that Mike has illustrated show how we can quickly pivot as a firm to delivering these types of solutions and help our customers think through innovative ways to solve the problems. So, I mean the prime example that Mike just gave, everything used to be done in offices. Now it's all done remotely cause you can't go to the office even if you want to. And that is very much aligned with the innovation we get with our partnership with Red Hat, right? They've led the way in open source and some of the technologies that we've leveraged that our solutions include, answerable for automation, some of the middleware products, and I would say one of the cornerstones is the OpenShift Platform. Now that allows us to greatly accelerate the development and delivery of those solutions to our customers. Sort of again, aligning our innovative thinking with Red Hats Innovative Technologies. >> What would you say if someone said, "what's the partnership strengths and what needs specifically are you addressing with customers and customer needs?" >> So I, again, I think our lean towards innovation is a common thread across both firms and where we have our greatest strength. We like to take our customers on a journey but it's not our journey, it's their journey, right? So we help them figure out where they want to go and how they want to get there in a way that aligns with their business goals, their budgets all the sort of factors that drive those things and Red Hat is very open to that approach. They sort of invented the crowdsourcing of open source they made it into a business model. They've developed that from literally nothing. And that aligns very nicely with us. That's one of the key strengths. We also are firm believers in open source again to the degree that our customers like the leverage that to drive their journeys. And we're seeing that, especially in the Public Sector Space as being a key driver of the technologies they employ. >> Mike, I want to come back to you on this open ma component open question, open source, open to technology open innovation out in the open as Red Hat calls it. How does Red Hat open source software, address the needs for your customers for security and on-premise considerations. >> I'll talk a little bit about open source principles in general still the open source principles of transparency meritocracy community problem solving and collaboration. These are on its of both software innovation as well as organizational transformation. One of the highest demand transformation needs that I'm seeing in the market is the desire to adopt innovative technology, and most importantly, moving workloads to the cloud. It's no longer a thought, it is an imperative moving workloads to the cloud, on new deals hosted in the cloud, on an existing, is it large systems let Deloitte help us get to the cloud. So I believe the key to success embracing the cloud is recognizing first the need for change in people, processes and technology. The vehicle for this transformation is DevSecOps and innovative open source platforms, such as the OpenShift platform that Dave mentioned. OpenShift focuses on people, processes and technology and the security conversation becomes even easier. I mean, I see Linux was around for years, and we've always used Linux on our Java based workloads now we can have the conversation about saying, Hey, well that se Linux operating system we've been using for years now, there's this really cool Container Management Platform that we can solve real problems like auto scaling, in my Health and Human Services career, I can remember every year when open enrollment comes around systems engineers are teed up, and ready to manually add those to a BMR cluster or something like that. Well, now we don't have to do these things. We can rely on Kubernetes so auto scale, and then and get rid of those instances when workload demands seven resolved. So it's a really cool technology kind of behind the scenes. It's not the dog and pony show sometimes but in the end it helps the clients and Deloitte remain consistent with those service level agreements. >> That's a great example about the open enrollment illustrates the fact that, you got to provision more stuff to take that load on it. It's always hard in Public Sector you might not have the speed. So I got to follow up and ask you, you guys have had wins in the Public Sector lately with Red Hat, you guys Deloitte and Red Hat working together and get some wins under your belt, on around cloud and cloud and technology obviously with the pandemic has needs there. Are you guys seeing any particular sector challenges specifically around Public Sector as it goes this next level a lot of modernization happening we're seeing that, but any challenges that you're seeing, can you give some examples of how these challenges are being addressed? First talk about the challenges and then give some examples of how they're overcoming them. >> So I can jump in here with this one then, and Mike I think you probably have some maybe Public Sector specific examples, but one of the things that I think is common across all industries is resource constraints, right? And particularly as we look for human resources and not in the HR sense, but developers, CIS admins those types of resources as Mike said, the cloud is here to stay, right? And it's not something that people are thinking about it's de facto part of the conversation. And that's great, but it leads to silos of skills which puts further sort of strain on a limited pool of resources within most sites IT organization. So something like an OpenShift, something like an Ansible solves problems related to resource constraints, because they're skills that are portable across cloud environments, right? If you can manage OpenShift you can manage OpenShift on-prem, you can manage it recently released AWS version of that ROSA on the Azure version of that. So it's no matter where you're running it you've got a common set of skills and access sort of a force multiplier, same thing with Ansible automation, right? If you can write scripts, with an Ansible you can do those repeatable tasks in a much more efficient fashion. And again sort of multiplying the capacity of your existing workforce. >> So you've got an operating leverage there. I mean, this is what you're getting at is that, Public Sector and other commercial areas they kind of got to get used to this fact that, you get some leverage here, you get some operating leverage. >> More or less has always been a thing in IT. And it's not relenting that's for sure. >> It's been more at the more, with less has always been kind of a tagline for budget cuts, right? You can squeeze more out of the investment. Here it's kind of like do more with less than the sense of there's more net new things happening with leverage. So, I mean, do you agree with that? What's your take on that? >> Yeah, I think that's exactly right. It's more with less from a resource perspective, right? Typically it was budget, but no money is just another resource. Now we're getting into the personnel side of it. The other thing I would say is, something like an OpenShift Platform allows the Mike's point around DevOps, it allows the developers to develop, right? I have an article in wired.com about this, where developers are saddled with meetings and they have to become concerned with infrastructure and they have traditionally and security. And I am I doing all these things that aren't related to development. If you have a good DevOps Platform in place the security folks can build guard rails into the platform and the developers can just go develop which is what they want to do in the first place. Yeah exactly, that's another riff on the more, with less, again in a resource, the human resource way versus the budget way. >> Yeah, and that really is where OpenShift ties in. Mike what's your take on this? Because with this kind of program ability infrastructure as code DevSecOps kind of modern developers, Public Sector loves that, because they just want to build the new apps. They got to modernize. So change the infrastructure once. And then a lot of ma many benefits on top of it. It's almost like, it sounds like an operating system to me. >> Yeah, lots of thoughts going around my head right now but I'll say the more with less to me when I'm having client conversations is imagine a world of higher innovation, more technology at lower costs, right? I mean, so CIO is light up when I explained to them the orders of magnitude cost savings on top of the innovation introduced to their environment. So when moving workloads to the cloud is not as easy as just packaging up a binary and dropping in on a name, your cloud provider, right? There's an entire, a blueprinting strategy. There's a Cloud Native Architecture, modernization discussion, so we do those sorts of things, at Deloitte and we work with clients very closely to do that. I want to say teaming with Red Hat allows us to be proactive with our design and reference architecture validation. The Collaborative Partnership in Relationship allows us to connect senior engineers from Deloitte and Red Hat. So we have low level strategic discussions, we validate our assumptions and optimize to use a Red Hat technology. What we're doing in Public Sector is separating the monolithic application into layers. And whenever it comes to technologies like Ansible, like OpenShift, like Jenkins, all of these things that any application needs and Public Sector, we're saying out to the account teams across the country, look this is a slower layer DevOps Platform. And by the way, you can run any .Net or Java based workload on it. So we're trying to make opinionated reference architecture so that regardless of the solution, we can just go to market with that platform that tried and true production application. So I'll give a quick example John, if now's a convenient time regarding, well, one of the things that we've done for particular state client. >> Definitely yeah, give the use cases we love those. >> Yes so one of the impactful modernization that struck my mind was the State of Washington. They've mentioned the affordable care act earlier, there are two major things that came out of that. One was the eligibility and enrollment systems had to be modified across all 50 states. But the second thing and the primary driver behind the affordable care act was health insurance exchange. A way for millions of citizens to have access to healthcare using Subsidized Health Insurance Plans. So in Washington and health benefits exchange is that health insurance exchange, State of Washington has been a client of Deloitte since 2012. The solution was originally designed using closed source proprietary products. There are three drivers for change. The first is the API gateway was end of life and needed to be replaced. Number two was the client wanted it to move health benefit exchange to the cloud from an on-premise hosting arrangement. And third is reducing cost of those solution with innovative products. So the agency was looking for a platform that provided flexibility, auto-scaling and performance and lower cost of ownership. So we worked with the agency and we evaluated a variety of API Management and Integration Platforms after reviewing the outcomes for each proof of concept the agency decided to move forward with Red Hats, three skill API Management Platform, Red Hat Fuse for Integration and OpenShift Container Platform that offered the auto-scaling continuous integration tools and out of the box monitoring and reporting capabilities proactively monitor the health of the solution. I often describe a little bit of OpenShift as a data center or DevSecOps in the box. It just is all there. You don't need to add layers on top of OpenShift install and configure it, tune it and just you're off and running in a short amount of time. So three outcomes I'll mention, go ahead, John. >> NO continue, I thought you were finished. So on the outcomes side, the first outcome the agency substantially lower the cost of ownership using commercially supported open source while increasing access to innovative emerging technology. So the agency wanted a solution not only to meet their current needs, but extend the solution going forward. The beautiful thing about OpenShift is you can drop a container images into the platform without installing an operating system. It's all just there and it's spreading to be extended. The number two outcome cloud migration. Deloitte work collaboratively with the agencies and infrastructure and managed services team to successfully migrate the health benefit exchange to the cloud. And the last thing a bit obvious, but that's successful release, working collaboratively with our client. We were able to migrate the solution within 100 days from making the products decision. The cut over to the new solution was seamless with minimal downtime and zero production issues or exceptionally proud of that. >> Great stuff, great use case. And again, those are great business examples. Dave, I want to get this last question to you and Mike can chime in too. As Red Hat Summit evolves, and we're hearing the theme here at the event about transformation is the innovation, Innovation is about scale. When you hear the words like in a box or Hybrid Cloud you hear about an operating environment. So it's an opportunity to set the table for the next generation, this is what I see. What do you guys see as people talk about Hybrid Cloud and soon to be Multiple Cloud? Because you guys you said have tough relationships. You deal with IBM and Red Hat and you probably deal with other people. Clients want, from what we hear they want back to the Multi Vendor Open Connection Distributed Environment. That's what they want. So how does your relationship evolve, given all this is happening? How do you see the future, please chime in. >> Thanks, that's a fantastic question. I actually think the market is coming catching up to where I've been thinking for quite a while. And that is the Hybrid is kind of where it's at. A lot of customers have been in some sort of Hybrid mode as part of the step or a journey to the cloud, getting all the way to the cloud. But I think we're seeing some transition. I know customers are starting to ask me more and more about Hybrid solutions for a variety of reasons, right? The easy workloads for the most part have either been moved or be are being moved, or at least there's a strategy and a plan to get them moved. And now we're starting to be asked about some of the more difficult architecture type questions, right? The workloads that are a little bit more sticky to the on-premise model. And so Hybrid becoming more of the endpoint as opposed to a step along the journey. The other big thing is some repatriation, right? Workloads coming off of cloud. Maybe they seem like good candidates but for whatever reason, the cost drivers or other things weren't realized, let's get them back on premise. Maybe it's a regulatory thing and new regulations are making folks uncomfortable. So I see Hybrid as a pretty interesting next wave of cloud, Deloitte as a far or we're skilling up or tooling up in order to address the needs of our customers, again are starting to ask us these really challenging questions about Hybrid Cloud and Hybrid Cloud Architectures. >> Yeah and just the key point there is that you think about it like with the way you're discussing it, it's a platform, not a tool, right? So if you think about it like a platform then you can move things around and look at architectures and changes of how resources and workloads are deployed and then what data you're getting from it. Whether you bring it to a factory, for instance you say, Hey, okay, we're going to put it on prem because it's a factory or whatever, and you need more data. What was the changeover? This is like a day to operations kind of mindset. What's your comment on that? >> Well I mean I have actually going back three years now, one of the marketing lines that we developed internally, was moved to a platform, not a provider. But because you get that flexibility, now, the reality is what works stay where they're put for a variety of reasons. But I think one of those reasons could be, because they're put in places where they tend to not want to move, right? So if we could put them into a platform where, there is some portability built into the platform, I think we might have a different sort of outcomes for customers. And I think architecture is absolutely the key, right? That to me is the secret sauce here. >> Mike set up for you to close us out here, platform, Public Sector, Hybrid, that's what they want. It's an ideal scenario for anyone in Public Sector and in general, and why wouldn't you want to have a great platform that's it can be programmed, and rearchitected at will for the benefit of the business powered by software. What's your thoughts? >> Yeah, all good points and I will agree with Dave that Hybrid is certainly evolving. Eight years ago, Hybrid was consuming and address validation API in the cloud and not custom coding that, but today I do agree that Hybrid Cloud is all about a vehicle a way of moving workloads across data centers. It's an architecture that is encapsulated by something like an OpenShift so that you can federate your workloads across data centers. You can put them in one or easily moved them to the other. Maybe that's for a variety of reasons. It could be compute and storage is being reduced by one provider versus the other. So the solutions were we're designing today, they are data center agnostic, we're not being tied to data centers anymore. The best design solutions, you can just let them move in their easy manner. So that that's my take on Hybrid Cloud. And I would say the and Red Hat are making investments to help us advance that thinking help us advance those solutions. We had Deloitte have created a Red Hat OpenShift lab environment, and we've done this purposely to validate reference architectures to show account teams the way we have delivered the very very large accounts to show them what DevSecOps to means from a product perspective and to give them opinionated processes to be successful in delivering these large type solutions. >> Dave, Mike, thanks for coming on, and I appreciate you guys coming on theCUBE and sharing the perspective on the Red Hat Relationship with Deloitte Consulting. Thanks for coming on. >> Thank you. >> Thank you, John. >> This is CUBE Coverage of Red Hat Summit 2021, am John for your host, thanks for watching.

(upbeat electronic music) >> Hello, welcome back to the Red Hat Summit, 2021 virtual coverage. I'm John Ferez, theCUBE coverage. I'm in Palo Alto with the remote interviews for our virtual conference here. We've got two great guests, CUBE alumnis, Tom Anderson, VP of Ansible Automation Platform, and Robin Bergeron, who's the Senior Manager, Ansible Community, community architect and all the great things involved. Robin, great to see you. Tom, thanks for coming back on Red Hat Summit, here, virtual. Good to see you. >> Thanks for having us. >> So since last summit, what's the updates on the Ansible Community and the Automation Platform? Tom, we'll start with you. Automation Platform, what's the big updates? >> Yeah. So since last Summit a lot has happened in Ansible land, if you will. So last time, I remember talking to you about content collections. Packing distribution format for into the sports. So we put a lot of effort into bringing all the Ansible content collections really, as well as the commercial users. And we launched last year a program certified content, working with our partners, including partners to certify the content collections that they create. Co-certify them, where we work together to make sure that the developed against, and tested against a Proctor spec, so that both of us can provide them to our customer bases with the confidence that they're going to be working and performing properly, and that we at Red Hat, and our partnership, co-support those out in our customer's production parts. That was a big deal. The other thing that we announced, late last fall, was the private automation hub. And that's the idea where our customers, obviously appreciate the idea of being able to go to Ansible galaxy or to the Ansible automation opt, to go and grab these content collections, these integrations, and bring them down in their environment. They wanted a way, they wanted a methodology, or a repository, where they can curate content from different sources, and then the manager across their environment, the automation across the environment. Kind of leaning into a little bit of automation content as code, if you will. And so we launched the automation hub, the private automation hub, where that sits in our customer's infrastructure; whether that's in the cloud, or on premise, or both, and allows them to grab content from galaxy, from the Ansible automation hub, the Ansible, automation hub on call.red hat.com, as well as their internally developed content, and be able to manage and provide that across their organization, governed by a set policies. So lots of stuff that's going on. Really advanced considering the amount of content that we provide. The amount of collections that we provide. Have certified that for our customers. And have the ability to curate and manage that content across the teams. >> I want to do a drill down on some of the unification of teams, which is a big message as well, as operating at scale, cause that's a super value proposition you guys have. And I want to get into that, but Robin, I want to come back to you on the community. So much has gone on. We're now into the pandemic for almost a year and a half now. It's been a productivity boom. Developers have been working at home for a long time, so it's not a new workflow for them, but you've seen a lot more productivity. What it's changed in the community since last summit, again, virtual to virtual again, between the windows here, event windows. You guys have a lot going on. What's new in the community? Gives us an update. >> Yeah, well, I mean, if we go back to summit, you know, this time-ish, you know, last year, we were wrapping up, more or less, the, it was, you know, we used to have everything you would install Ansible. You would get all the modules. You had everything, you know. It was all all altogether, which, you know, it was great for new users, who don't want to have to figure things out. It helps them to really get up and started running quickly. And, but, you know, from a community perspective, trying to manage that level of complexity turned out to be pretty hard. So the move to collections was actually great for, you know, not just, you know, for about user perspective, but also from a community perspective. And we came out with the Ansible 2-10. That was last fall, I believe. And that was the first real release of Ansible where we had, you know, collections were fully instantiated. We, you know, they were available on galaxy, but you could also get them as part of the Ansible community distribution. Fast forward to now, you know, we just had the Ansible 3.0 release, here in February, and we're looking to Ansible 4.0 here in early May. So, you know, there's been a lot of activity. A lot has improved, honestly, as a result of the changes that we've made. It's made it a lot easier for contributors to get in with a smaller group, that's more of their size and, you know, be able to get started and identify, you know, who are their interested peers in the community. So it's been a boom for us, honestly. You know, the pandemic otherwise is, you know, I think taught all of us, you know, certainly you, John, about the amazing things that we can do virtually. So we've had a lot of our meetups pivot to being virtual meetups, and things like that. And it's been great to see how easily the community has been able to pivot around, you know, this sort of event. I hope that we don't have to just keep practicing it for forever, but in the meantime, you know, it's enabled us to continue to get things done. Thank goodness to every video platform on Earth. >> Yeah. Well, we appreciate it. We're going to come back and talk more about that in the future; the best practice, what we all learned, and stories, but I think I want to come back to you on the persona side of Ansible, because one of the things we talked about last time that seems to be gaining a lot of traction, is that multiple personas. So I want to just hold on to that. We'll come back. Tom, back to you. We're at Red Hat summit. You guys have Ansible Fest, which is your own event that you guys drilled down on this. So users watching can know this your own community, but now we're part of Red Hat, part of IBM, which IBM Thinks, also happening soon as well. Red Hat summit still is unique event. How is Ansible fitting into the big picture? Because the value proposition of unifying teams is really consistent now with Red Hat's overall arching thing; which is operating at scale, open shift, Robin just mentioned. Where's the automation platform going this year? What's the story here at Red Hat summit for the automation platform? >> Yeah, no, that's a great question . We've seen so, we got time, just a little bit of the pandemic, and how it has accelerated some existing trends that we already saw. And one of those is really around the democratization of the application to work routines. More people delivering infrastructure and applications, independent of each other. Which is great. Faster and more agile, all those other good words that apply to that. But what that does bring up is the opportunity for patient work. Replication of effort. Not reusing necessarily things that are in existence already that other teams may have. They'd be not complying with all of the policies, if you will, the configuration and clients' policies. And so it's really kind of brought Ansible out into focus even more here. Now, because of the kind of common back lane that Ansible provides; a common language and common automation backplane across these different teams, and across these different personas. The great thing about what we supply for these different personas, whether it's outpatient developers, infrastructure honors, network engineers, SecOps teams, GetOps teams. There's so many of these obstacles out there, who now all want independent access to infrastructure, and deploying infrastructure. And Ansible has the kind of leverage that each of those communities, whether it's APIs or CLIs, or event based automation, or web hooks, et cetera, et cetera, you know? Service catalogs, utilize all of those interfaces, if you will, or modalities are accessible in Ansible automations. So it's really allowed us to be this sort of connective tissue, or glue, across these different silos or manes of the organization. Timing it opens specifically, one of the things that we talked about last fall, at our Ansible Fest, was our integration between the Ansible automation platform, our advanced cluster management product, and our OpenShift platform, that allows native applications, running on OpenShift, be able to talk to a Ansible automation operator that's running on that same platform, to do things off platform for their customers are already using Ansible. So connecting their cloud native platforms with our existing systems and infrastructures. Systems of records, network systems, ticketing systems, you name it. So all of those sorts of integrations, Ansible's become the connected glue across all of these different environments. Tying traditional IT, cloud IT, cloud native, you name it. So it's really been fun, and it's been an exciting time for us inside the portfolio and out. >> That's a great point. Connective tissue is a great way to describe some of these platform benefits, cause you guys have been on this platform for really long time. And the benefits are kind of being seen in the market, certainly as people have to move faster with the agility. Robin, I want to come back to you because he brought up this idea of personas. I mean, we all know DevOps infrastructure has code; it's been our religion for over a decade or more, but now the word DevSecOps is more prevalent in all the conversations. The security's now weaved in here. How are you seeing that play out in the community? And then, Tom, if you can give some color commentary too, on the automation platform, how security fits in? So DevOps, everything's being operationalized at scale, we get that. That's one of the value propositions you have, but DevSecOps has a persona. More people want more sec. Dev is great, more ops and standardization, more developers, agile standards, and then security. DevSecOps. What's your? >> I thought it was DevNetSecOps? (man chuckling) >> Okay. I've forgot net. Put net in there. Well, networks abstracted away, you know, as we say. >> Yeah! Well, you know, from my perspective, you know, they're people in their jobs all over the places, right? Like, they, you know, the more they can feel like they're efficient, and doing great stuff at their work, like, they're happy to bring as many people into the fold as possible. Right? And you know, normally, security's always been this, you know, it's sort of like networking, right? It's always been this sort of isolated, this special group over here, that's the traditional, you know, one of the traditional IT bottlenecks that causes us to not be able to get anything done. But, you know, on a community level, we see folks who are interested in security, you know, all the time. I know we've certainly done quite a bit of work with the some folks at IBM around one of their products; which I assume Tom will get more into here in just a moment. But from, you know, community perspective, I mean, we've seen people who've been writing, you know, playbooks and roles and, you know, now collections for, you know, all of the traditional government testing, you know, is, you know, missed standards, all of that kind of stuff. And, you know, it's one of those, it's part of network effects. And it's a great place for actually automation hub. I think, you know, for folks who were on prem or, you know, any of our customers are really going to start to see lots of value. How it will be able to connect folks inside the organization, you know, organically through just the place where I'm doing my Ansible things, allows them to find each other, really. And build those, you know, take it from being silos of automation everywhere into a really sort of networked, you know, internal network of Ansible friends and Ansible power users that, you know, can work together and collaborate, you know, just the same way that we do in open source. >> Yeah. And Tom, so IT modernization requires security. What's your take on this? Because you know, you got cluster, a lot of cluster, advanced cluster management issues. You got to deal with the modern apps that are coming. IT's got to evolve. What's your take on all this? >> Yeah. Not only does IT have to evolve, but it's the integration of IT into the rest of the environment. To be able to respond. So, one of the areas that we put a lot of effort into advancement of curating and solutions around security automation. And we've talked about that in the past, the idea of connecting SecOps teams that are doing intrusion detection, or threat hunting, and then responding in an automated way to those threat protections. Right? So connect SecOps with my team; which has traditionally been siloed operations and silo teams. And now with this curated, Ansible security automation solution that we brought to market, with our partners, that connects those two teams in a seamless sort of way. And we've got a lot of work with our friends at IBM, around this area because they are digging that security, their facility, the products in their portfolio. So we've done a lot of work with them. We've done a lot of work with lots of our partners; whether it's cyber or Microsoft, or whoever. Those areas are traditionally, Ansible's done a great job on sort of compliance around configuration enforcement, right? Setting configuration. Now we moved into connecting set-mops with IT. Security automation, now of our acquisition of SecOps, along with our advanced cluster management integration with Ansible, we're starting to say, what are the things inside that DevSecOps workflow that may require integration or automation, or package automation with other parts of the environment? So bringing all of those pieces together, as we move forward, which is really exciting for us. >> Okay, I got to ask you guys the number one question that I get all the time, and I see in the marketplace, kind of a combo question, is, how do I accelerate the automation of my cloud native development, with my traditional infrastructure? Because as people put in green, if one of the cloud projects, whether it's, and then integrating with the cloud on premises with the traditional infrastructure, how do I accelerate those two environments? How do I automate, accelerate the automation? >> It's a great short for us, as what we were talking about last Ansible Fest. We are bringing together with our advanced, cluster management product, ownership platform. Ansible is just been widespread use in all of the automation of both traditional, and cloud native, infrastructures. Whether it's cloud infrastructure, on-premise storage, compute network, you name it. Customers are using Ansible, using Ansible to do all kinds of pieces of infrastructure. Being able to tie that to their new, cloud native initiatives, without having to redo all of that work that they've already done, you integrate that, this thing, infrastructure automation, with their cloud native stuff, it accelerates substantially the, what I call, the operationalization of their cloud native platforms, with their existing IT infrastructure in the existing, IT ecosystem. I believe that that's what the Ansible automation platform plays a key role in connecting those pieces together, without having to redo all that work, that's been done and invested. >> Robin, what's your take on this? This is what people are working on in the trenches. They realize cloud benefits. They've got some cloud native action, and also then they got on the traditional environment, and they've got to get them connected and automated. >> Yeah, absolutely. I mean, you know, the beauty of Ansible, you know, from a end user perspective is, you know, how easy it is to learn and how easy the languages to learn. And I think, you know, that portability, you know, it doesn't matter like, how much of a rocket scientist you are, you know? Everybody appreciates simplicity. Everybody appreciates being able to hand something simple to somebody else, and letting other people get done, and having it, be more or less, it's not quite English, but it's definitely, you know, Ansible's quite readable. Right? And you know, when we looked at, when we started to work on all the Ansible operators, you know, one of that, one of the main pieces there was making sure that that simplicity that we have in Ansible, is brought over directly into the operator. So, just because it's cloud native doesn't mean you suddenly have to learn, you know, a whole set of new languages. Ansible's just as portable there, as it is to any other part of the, your IT organization, infrastructure, whatever it is that you have going on. >> Well, there's a lot of action going on here at Red Hat summit, 2021. Things I wanted to bring up, in context of the show, is the success, and the importance, of you guys having Ansible collections. This has come up multiple times, as we talked about those personas, and you've got these new contributors. You've got people contributing content, as open-source continues to grow and be phenomenal. Value proposition. Touch on this concept of collections. What's the updates? Why is it important? Why should folks pay attention to it, and continue to innovate with collections? >> From a commercial perspective, or from a product perspective, collections have made it a lot easier for contributors to create, and deploy, and distribute content. As Robin's mentioned earlier, previous iterations of Ansible have all of that integration. All of those collections, all within one big group. We call the "batteries included" back in the time. Back in the day, right? That that meant that contributors deployed content with the base, Ansible distribution, they had to wait for the next version of Ansible to come out. That's when that content would get redistributed with the next version of Ansible. By de-coupling, on platform, or engine, putting that into collections, individual elements of related integrations, those can move that their own pace. So users, new customers, can get the content they need, based their contributors like and keep up with. So, customers will have to wait for the next version of the shipping products and get a new version of the new integration they really like now. So again, de-coupling those things, it allows them to move at different paces. The engine, or the platform itself, needs to be stable, performance secure. It's going to move at a certain lifecycle. The content itself, all the different content, hub, and network providers, platforms, all of those things can now move at their own pace. Each of those have their own life cycle. Allows us to get more functionality in our customers hands a lot quicker. And then launching our certified program, partners, when we support that content, certified support that content, helps meet the values that we bring to our customers with this subscription. It's that ecosystem of partners that we work with, who certified and support the stuff that we ship and support with our customers. Benefits both from the accessing the technology, as well as to the access to the value added in terms of integration, testing and support. >> Robin, what's your take on the community? I see custom automation with connect here. A lot of action going on with collections. >> Yeah. Absolutely. You know, it's been interesting, you know? Tom just mentioned the, you know, how everything, previously, all had to be released all at once. Right? And if you think about, you know, sure I have Ansible installed, but you know, how often do I have to, you know, just even as a regular, I'm not a system administrator these days, type person, like how often do I have to, you know, click that button to update, you know, my Mac or my Linux machine? Or, you know, my windows machine, or you know, the operating system on my telephone, right? Every time one of these devices that Ansible connects to, or program, or whatever it is, connects to something, those things are all operating and, you know, developing themselves at their own paces. Right? So when a new version of, you know, we'll call it Red Hat, Enterprise Linux. When a new version of Red Hat, Enterprise Linux comes out, if there are new changes, or new features that, you know, we want to be able to connect to, that's not really helpful when we're not releasing for another six months. Right? So it's really helped us, you know, from a community angle, to able to have each of these collections working in concert with, you know, for example, the Lennox subsystems that are actually making things that will turn be turned into collections, right? Like, SE Linux, or a system D, right? Like, those things move at their own pace. We can update those at our own pace in collections, and then people can update those collections without having to wait another six months, or eight months, or whatever it is, for a new version of Ansible to come out. It's really made it easier for all of those, you know, developers of content to work on their content and their, you know, Ansible relationships almost in sync. And make sure that, you know, not, "I'm going to do it over here. And then I'm going to come back over here and fix everything later." It's more of a, you know, continuous development process. >> So, the experience. So the contributor experience is better then? You'd say? >> I'm sorry? >> The contributor experience is better then? >> Oh, absolutely. Yeah. 100%. I mean, it's, you know, there's something to be said for, I wouldn't say it's like, instant satisfaction, but certainly the ability to have a little bit more independence, and be able to release things as you see fit, and not be gated by the entire rest of the project, is amazing for those folks. >> All right. So I'll put you on the spot, Robin. So if I'm a developer, bottom line me, what's in it for me? Why should I pay attention to collections? What's the bottom line? >> Well, you know, Ansible is a platform, and Ansible benefits from network effects. You know, the reason that we've gotten as big as we have, is sort of like the snowball rolling downhill, right? The more people that latch onto what you're doing, the more people benefit and the more, you know, additional folks want to join in. So, you know, if I was working on any other product that I would consider being able to have automated with Ansible, you know, the biggest thing that I would look at is, well, you know, what are those people also using? Are they automating it with Ansible? And I can guarantee you, 99% of the time, everything else that people are using is also being automated with Ansible. So you'd be crazy to not, you know, want to participate, and make sure that you're providing the best, Ansible experience for, you know, your application, cause for every application or, you know, device that we can connect to, there's probably 20 other competitors that also make similar applications that, you know, folks might also consider in lieu of you if you're not using, if you're not providing Ansible content for it. >> Hey, make things easier, simple to use, and you reduce the steps it takes to do things. That's a winning formula, Tom. I mean, when you make things that good, then you get the network effect. But this highlights what you mentioned earlier, about connective tissue. When you were using words like "connective tissue" it implies an organizational's, not a mechanism. It's not just software, it's people. As a people experience here in the automation platform. >> Robin: Yep. >> This seems to be the bottom line. What's your take? What's your bottom line view? I'm a developer, what's in it for me? Why should I pay attention to the automation platform? >> What Robert just said to me is, more people using. Automation platform, crossing those domains, and silos as kind of connective tissue across those teams, and its personas, means those contributors, those developers, creating automation content, getting in the hands of more people across the organization. In a more simplified way by using Ansible automation. They get access, the automation itself, those personas, they get access to the system automation faster, they can have the money quicker, local to local folks. To reinvent the wheel in terms of automation, we're trying to, (man speaking faintly) They don't want to know about the details, and what it takes to configure the network, configure the storage elements. They rely on those automation developers and contributors that review that for them. One powers of the platform. Across those teams, across those others. Okay we're going to talk about SecOps, The ITOps, in SecOps, in networkOps. And to do all of these tasks, with the same language, and same unition content, running faster, and it's monitoring core responsibilities without worrying. >> Robin, you wanted to talk about something in the community, any updates? I think navigator, you mentioned you wanted to mention a plug for that? >> Absolutely! So, you know, much like any other platform in the universe, you know, if you don't have really great tools for developing content, you're kind of, you know, dead in the water, right? Or you're leaving it to fate. So we've been working on a new project, not part of the product yet, but you know, it's sort of in a community, exploratory phrase. A release, early release often, or, you know, minimum viable product, I guess, might be the other way to describe it currently. It's called Ansible navigator. It's a Tooey, which is like a gooey, but it's got a, sort of a terminal, user interface look to it, that allows you to, you know, develop, it's a sort of interface where you can develop content, you know, all in one window. Have your, you know, documentation accessible to you. Have, you know, all of your test results available to you in one window, rather than, I'm going to do something here, And then I'm going to go over here, and now I'm not sure. So now I'm going to go over here and look at docs instead. It's all, you know, it's all in one place. Which we think will actually, but I mean, I know the folks who have seen it already been like, (woman squealing) but you know, it's definitely in early, community stages right now. It's, you know, we can give you the link. It's github.com/Ansible/Ansiblenavigator >> A tooey versus a gooey, versus a command line interface. >> Yeah! >> How do you innovate on the command line? It's a cooey, or a? >> Yeah! >> It's, you know, there are so many IDs out there and I think Tom can probably talk to some of this, you know, how that might relate to VA code or, you know, many of the other, you know, traditional developer IDs that are out there. But, you know, the goal is certainly to be able to integrate with some of those other pieces. But, you know, it's one of those things where, you know, if everybody's using the same tool and we can start to enforce higher levels, quality and standards through that tool, there's benefits for everyone. Tom, I don't know if you want to add on to that in any way? >> Yeah, it's just kind of one of our focus areas here, which is making it as easy as possible for contributors to create Ansible automation content. And so part of that is production, meaning S & K. Remember what happened to S & K for Ansible? That involved developers and contributors to use ID's, build and deploy automation content. So, I'm really focused on making that contributor life their job. >> Well, thanks for coming on Tom and Robin. Thanks for sharing the insight here at Red Hat Summit 21, virtual. So you guys continue to do a great job with the success of the platform, which has been, you know, consistently growing and having great satisfaction with developers, and now ops teams, and sec teams, and net teams. You know, unifying these teams is certainly a huge priority for enterprises because the end of the day, cloud-scale is all about operating. Which means more standards, more operations. That's what you guys are doing. So congratulations on the continued success. Thanks for sharing. >> Thanks for having us. >> Okay. I'm John for here in theCUBE we are remote with CUBE virtual for Red Hat Summit, 2021. Thanks for watching. (upbeat electronic music)

>>Mhm Yes. Hello and welcome back to the cubes coverage of red hat summit 2021 virtual. I'm john for your host of the cube we're here with Hillary Hunter, the VP and CTO and IBM fellow of IBM cloud at IBM. Hillary, Great to see you welcome back, You're no stranger to us in the cube your dentist few times. Thanks for coming on. >>Thanks so much for having me back. Great to talk more today >>I believe I B M is the premier sponsor for red hat summit this year. No, I mean I think they're somewhat interested in what's happening. >>Yeah, you know, somebody is such a great event for us because it brings together clients that, you know, we work together with red head on and gives us a chance to really talk about that overall journey to cloud and everything that we offer around cloud and cloud adoption um, and around redheads capabilities as well. So we look forward to the summit every year for sure. >>You know, the new IBM red hat relationship obviously pretty tight and successful seeing the early formations and customer attraction and just kind of the momentum, I'll never forget that Red hat something was in SAN Francisco. I sat down with Arvin at that time, uh, Red hat was not part of IBM and it was interesting. He was so tied into cloud native. It was almost as if he was dry running the acquisition, which he announced just moments later after that. But you can see the balance. The Ceo at IBM really totally sees the cloud. He sees that experience. He sees the customer impact. This has been an interesting year, especially with Covid and with the combination of red hat and IBM, this cloud priority for IT leaders is more important than ever before. What's your, what's your take on this? Because clearly you guys are all in on cloud, but not what people think, what's your, what's your view on this? >>Yeah. You know, from, from the perspective of those that are kind of data oriented IBM Institute for Business Value, did lots of studies over the last year, you know, saying that over 60% of leaders feel, you know, increased urgency to get to the cloud, um they're intending to accelerate their program to the cloud, but I think, you know, just even as consumers where each very conscious that our digital behaviors have changed a lot in the last year and we see that in our enterprise client base where um everything from, you know, a bank, we work that that that had to stand up their countries equivalent of the payroll protection program in a matter of weeks, which is just kind of unheard of to do something that robust that quickly or um, you know, retail obviously dealing with major changes, manufacturing, dealing with major changes and all consumers wanting to consume things on an app basis and such, not going into brick and mortar stores and such. And so everything has changed and months, I would say have sort of timeframes of months have been the norm instead of years for um, taking applications forward and modernizing them. And so this journey to cloud has compressed, It's accelerated. And as one client I spoke with said, uh, in the midst of last year, you know, it is existential that I get to cloud with urgency and I think That's been that has been the theme of 2020 and now also 2021. And so it is, it is the core technology for moving faster and dealing with all the change that we're all experiencing. >>That's just so right on point. But I got I want to ask you because this is the key trend enterprises are now realizing that cloud native architecture is based on open source specifically is a key architectural first principle now. >>Yeah. >>What's your, what, what would you say to the folks out there who were listening to this and watching this video, Who were out in the enterprise going, hey, that's a good call. I'm glad I did it. So I don't have any cognitive dissidence or I better get there faster. >>Yeah. You know, open source is such an important part of this conversation because I always say that open source moves at the rate and pays a global innovation, which is kind of a cute phrase that I really don't mean it in anyways, cute. It really is the case that the purpose of open sources for people globally to be contributing. And there's been innovation on everything from climate change to you know, musical applications to um things that are the fundamentals of major enterprise mission critical workloads that have happened is everyone is adopting cloud and open source faster. And so I think that, you know this choice to be on open source is a choice really, you know, to move at the pace of global innovation. It's a choice too um leverage capabilities that are portable and it's a choice to have flexibility in deployment because where everyone's I. T is deployed has also changed. And the balance of sort of where people need the cloud to kind of come to life and be has also changed as everyone's going through this period of significant change. >>That's awesome. IBM like Red has been a long supporter and has a history of supporting open source projects from Lenox to kubernetes. You guys, I think put a billion dollars in Lenox way back when it first started. Really power that movement. That's going back into the history books there. So how are you guys all collaborating today to advance the open source solutions for clients? >>Yeah, we remain very heavily invested in open source communities and invested in work jointly with Red Hat. Um you know, we enabled the technology known as um uh Rackham the short name for the Red Hat advanced cluster management software, um you know, in this last year, um and so, you know, provided that capability um to to become the basis of that that product. So we continue to, you know, move major projects into open source and we continue to encourage external innovators as well to create new capabilities. And open source are called for code initiatives for developers as an example, um have had specific programs around um uh social justice and racial issues. Um we have a new call for code out encouraging open source projects around climate change and sustainable agriculture and all those kind of topics and so everything from you know, topics with developers to core product portfolio for us. Um We have a very uh very firm commitment in an ongoing sustained contribution on an open source basis. >>I think that's important. Just to call out just to kind of take a little sidebar here. Um you guys really have a strong mission driven culture at IBM want to give you props for that. Just take a minute to say, Congratulations call for code incredible initiative. You guys do a great job. So congratulations on that. Appreciate. >>Thank you. Thank you. >>Um as a sponsor of Red Hat Summit this year, I am sponsoring the zone Read at um you have you have two sessions that you're hosting, Could you talk about what's going on? >>Yeah, the the two sessions, so one that I'm hosting is around um getting what we call 2.5 x value out of your cloud journey. Um and really looking at kind of how we're working with clients from the start of the journey of considering cloud through to actually deploying and managing environments and operating model on the cloud um and where we can extract greater value and then another session um that I'm doing with Roger Primo, our senior vice President for strategy at IBM We're talking about lessons and clouded option from the Fortune 500, so we're talking there about coca cola european bottling partners, about lumen technologies um and um also about wonderman Thompson, um and what they're doing with us with clouds, so kind of two sessions, kind of one talking a sort of a chalkboard style um A little bit of an informal conversation about what is value meaning cloud or what are we trying to get out of it together? Um And then a session with roger really kind of focused on enterprise use cases and real stories of cloud adoption. >>Alright so bottom line what's going to be in the sessions, why should I attend? What's the yeah >>so you know honest honestly I think that there's kind of this um there's this great hunger I would say in the industry right now to ascertain value um and in all I. T. Decision making, that's the key question right? Um not just go to the cloud because everyone's going to the cloud or not just adopt you know open source technologies because it's you know something that someone said to do, but what value are we going to get out of it? And then how do we have an intentional conversation about cloud architecture? How do we think about managing across environments in a consistent way? Um how do we think about extracting value in that journey of application, modernization, um and how do we structure and plan that in a way? Um that results in value to the business at the end of the day, because this notion of digital transformation is really what's underlying it. You want a different business outcome at the end of the day and the decisions that you take in your cloud journey picking. Um and open hybrid, multi cloud architecture leveraging technologies like IBM cloud satellite to have a consistent control plan across your environments, um leveraging particular programs that we have around security and compliance to accelerate the journey for regulated industries etcetera. Taking intentional decisions that are relevant to your industry that enable future flexibility and then enable a broad ecosystem of content, for example, through red hat marketplace, all the capabilities and content that deploy onto open shift, et cetera. Those are core foundational decisions that then unlock that value in the cloud journey and really result in a successful cloud experience and not just I kind of tried it and I did or didn't get out of it what I was expecting. So that's really what, you know, we talk about in these in these two sessions, um and walk through um in the second session than, you know, some client use cases of, of different levels and stages in that cloud journey, some really core enterprise capabilities and then Greenfield whitespace completely new capabilities and cloud can address that full spectrum. >>That's exciting not to get all nerdy for a second here, But you know, you bring up cloud architecture, hybrid cloud architecture and correct me if I'm wrong if you're going to address it because I think this is what I'm reporting and hearing in the industry against the killer problem everyone's trying to solve is you mentioned, um, data, you mentioned control playing for data, you mentioned security. These are like horizontally scalable operating model concepts. So if you think about an operating system, this is this is the architecture that becomes the cloud model hybrid model because it's not just public cloud cloud native or being born in the cloud. Like a startup. The integration of operating at scale is a distributed computing model. So you have an operating system concept with some systems engineering. Yeah, it sounds like a computer to me, right. It sounds like a mainframe. Sounds like something like that where you're thinking about not just software but operating model is, am I getting that right? Because this is like fundamental. >>Yeah, it's so fundamental. And I think it's a great analogy, right? I think it's um you know, everyone has kind of, their different description of what cloud is, what constitutes cloud and all that kind of thing, but I think it's great to think of it as a system, it's a system for computing and what we're trying to do with cloud, what we're trying to do with kubernetes is to orchestrate a bunch of, you know, computing in a consistent way, as, you know, other functions within a single server do. Um What we're trying to do with open shift is, you know, to enable um clients to consume things in a consistent way across many different environments. Again, that's the same sort of function um conceptually as, you know, an operating system or something like that is supposed to provide is to have a platform fundamentally, I think the word platform is important, right? Have a platform that's consistent across many environments and enables people to be productive in all those environments where they need to be doing their computing. >>We were talking before we came on camera about cloud history and we were kind of riffing back and forth around, oh yeah, five years ago or six years ago was all the conversations go to the cloud now, it's like serious conscience around the maturity of cloud and how to operate that scale in the cloud, which is complex, it's complex system and you have complexity around system complexity and novelty complexity, so you have kind of all these new things happening. So I want to ask you because you're an IBM fellow and you're on the cloud side at IBM with all this red hat goodness you've got going on, Can you give us a preview of the maturity model that you see the IBM season, that red hats doing so that these architectures can be consistent across the platforms, because you've got def sec ops, you've got all these new things, you've got security and data at scale, it's not that obviously it's not easy, but it has to be easier. What's what's the preview of the maturity model? >>Yeah, you know, it really is about kind of a one plus one equals three conversation because red hats approach to provide a consistent platform across different environments in terms of Lennox and Kubernetes and the open shift platform um enables that first conversation about consistency and maturity um in many cases comes from consistency, being able to have standards and consistency and deployment across different environments leads to efficiency. Um But then IBM odds on that, you know, a set of conversations also around data governance, um consistency of data, cataloguing data management across environments, machine learning and ai right bringing in A. I. For I. T. Operations, helping you be more efficient to diagnose problems in the IT environment, other things like that. And then, you know, in addition, you know, automation ultimately right when we're talking about F. R. I. T. Ops, but also automation which begins down at the open shift level, you know with use of answerable and other things like that and extends them up into automation and monitoring of the environment and the workloads and other things like that. And so it really is a set of unlocking value through increasing amounts of insight, consistency across environments, layering that up into the data layer. Um And then overall being able to do that, you know efficiently um and and in a consistent way across the different environments, you know, where cloud needs to be deployed in order to be most effective, >>You know, David Hunt and I always talk about IBM and all the years we've been covering with the Cube, I mean we've pretty much been to every IBM events since the Cube was founded and we're on our 11th year now watching the progression, you guys have so much expertise in so many different verticals, just a history and the expertise and the knowledge and the people. They're so smart. Um I have to ask you how you evolved your portfolio with the cloud now um as it's gone through, as we are in the 2021 having these mature conversations around, you know, full integration, large scale enterprise deployments, Critical Mission Mission Critical Applications, critical infrastructure, data, cybersecurity, global scale. How are you evolve your portfolio to better support your clients in this new environment? >>Yeah, there's a lot in there and you hit a lot of the keywords already. Thank you. But but I think that you know um we have oriented our portfolio is such that all of our systems support Red hat um and open shift, um our cloud, we have redhead open shift as a managed service and kubernetes is at the core of what we're doing as a cloud provider and achieving our own operational efficiencies um from the perspective of our software portfolio, our core products are delivered in the form of what we refer to as cloud packs on open shift and therefore deploy across all these different environments where open shift is supported, um products available through Red hat marketplace, you know, which facilitates the billing and purchasing an acquisition and installation of anything within the red hat ecosystem. And I think, you know, for us this is also then become also a journey about operational efficiency. We're working with many of our clients is we're kind of chatting about before about their cloud operating model, about their transformation um and ultimately in many cases about consumption of cloud as a service. Um and so um as we, you know, extend our own cloud capabilities, you know, out into other environment through distributed cloud program, what we refer to as as IBM cloud satellite, you know, that enables consistent and secure deployment of cloud um into any environment um where someone needs, you know, cloud to be operated. Um And that operating model conversation with our clients, you know, has to do with their own open shift environments that has to do with their software from IBM, it has to do their cloud services. And we're really ultimately looking to partner with clients to find efficiency in each stage of that journey and application modernization in deployment and then in getting consistency across all their environments, leveraging everything from uh the red hat, you know, ACM capabilities for cluster management up through a i for beauty shops and automation and use of a common console across services. And so it's an exciting time because we've been able to align our portfolio, get consistency and delivery of the red half capabilities across our full portfolio and then enable clients to progress to really efficient consumption of cloud. >>That's awesome. Great stuff there. I got to ask you the question that's on probably your customers minds. They say, okay, Hillary, you got me sold me on this. I get what's going on, I just gotta go faster. How do I advance my hybrid cloud model faster? What are you gonna do for me? What do you have within the red hat world and IBM world? How are you gonna make me go faster? That's in high quality way? >>Yeah. You know, we often like to start with an assessment of the application landscape because you move faster by moving strategically, right? So assessing applications and the opportunity to move most quickly into a cloud model, um, what to containerized first, what to invest in lift and shift perspective, etcetera. So we we help people look at um what is strategic to move and where the return on investment will be the greatest. We help them also with migrations, Right? So we can help jump in with additional skills and establish a cloud center of competency and other things like that. That can help them move faster as well as move faster with us. And I think ultimately choosing the right portfolio for what is defined as cloud is so important, having uh, an open based architecture and cloud deployment choice is so important so that you don't get stuck in where you made some of your initial decisions. And so I think those are kind of the three core components to how we're helping our clients move as quickly as possible and at the rate and pace that the current climate frankly demands of everyone. >>You know, I was joking with a friend the other night about databases and how generations you have an argument about what is it database, what's it used for. And then when you kind of get to that argument, all agree. Then a new database comes along and then it's for different functions. Just the growth in the internet and computing. Same with cloud, you kind of see a parallel thing where it's like debate, what is cloud? Why does he even exist? People have different definitions. That was, you know, I mean a decade or so ago. And then now we're at almost another point where it's again another read definition of, okay, what's next for cloud? It's almost like an inflection point here again. So with that I got to ask you as a fellow and IBM VP and Cto, what is the IBM cloud because if I'm going to have a discussion with IBM at the center of it, what does it mean to me? That's what people would like to know. How do you respond to that? >>Yeah. You know, I think two things I think number one to the, to the question of accelerating people's journeys to the cloud, we are very focused within the IBM cloud business um on our industry specific programs on our work with our traditional enterprise client base and regulated industries, things like what we're doing in cloud for financial services, where we're taking cloud, um and not just doing some sort of marketing but doing technology, which contextualize is cloud to tackle the difficult problems of those industries. So financial services, telco uh et cetera. And so I think that's really about next generation cloud, right? Not cloud, just for oh, I'm consuming some sauce, and so it's going to be in the cloud. Um but SAS and I SV capabilities and an organization's own capabilities delivered in a way appropriate to their industry in in a way that enables them to consume cloud faster. And I think along those lines then kind of second thing of, you know, whereas cloud headed the conversation in the industry around confidential computing, I think is increasingly important. Um It's an area that we've invested now for several generations of technology capability, confidential computing means being able to operate even in a cloud environment where there are others around um but still have complete privacy and authority over what you're doing. And that extra degree of protection is so important right now. It's such a critical conversation um with all of our clients. Obviously those in things like, you know, digital assets, custody or healthcare records or other things like that are very concerned and focused about data privacy and protection. And these technologies are obvious to them in many cases that yes, they should take that extra step and leverage confidential computing and additional data protection. But really confidential computing we're seeing growing as a topic zero trust other models like that because everyone wants to know that not only are they moving faster because they're moving to cloud, but they're doing so in a way that is without any compromise in their total security, um and their data protection on behalf of their clients. So it's exciting times. >>So it's so exciting just to think about the possibilities because trust more than ever now, we're on a global society, whether it's cyber security or personal interactions to data signing off on code, what's the mutability of it? I mean, it's a complete interplay of all the fun things of uh of the technology kind of coming together. >>Absolutely, yeah. There is so much coming together and confidential computing and realizing it has been a decade long journey for us. Right? We brought our first products actually into cloud in 2019, but its hardware, it's software, it services. It's a lot of different things coming together. Um but we've been able to bring them together, bring them together at enterprise scale able to run entire databases and large workloads and you know um pharmaceutical record system for Germany and customer records for daimler and um you know what we're doing with banks globally etcetera and so you know it's it's wonderful to see all of that work from our research division and our developers and our cloud teams kind of come together and come to fruition and and really be real and be product sizable. So it's it's very exciting times and it's it's a conversation that I think I encourage everyone to learn a little bit more about confidential computing. >>Hillary hunter. Thank you for coming on the cube. Vice President CTO and IBM fellow which is a big distinction at IBM. Congratulations and thanks for coming on the Cuban sharing your insight. Always a pleasure to have you on an expert always. Great conversation. Thanks for coming on. >>Thanks so much for having me. It was a pleasure. >>Okay, so cubes coverage of red Hat Summit 21 of course, IBM think is right around the corner as well. So that's gonna be another great event as well. I'm john Feehery, a host of the cube bringing all the action. Thanks for watching. Yeah.

(upbeat music) >> And, welcome back to theCube's coverage of Red Hat Summit, 2021. I'm John Furrier, host of theCube. We've got a great segment here on how Red Hat is working with telcos and the disruption in the telco cloud. We've got a great guest Cube alumni, Darrell Jordan Smith, senior vice president of industries and global accounts at Red Hat. Darrell, great to see you. Thanks for coming back on theCube. >> Oh, it's been, it's great to be here and I'm really excited about having the opportunity to talk to you today. >> Yeah, we're not in person, in real life's coming back soon. Although I hear Mobile World Congress, might be in person this year, looking like it's good. A lot of people are going to be virtual and activating I know. A lot to talk about. This is probably one of the most important topics in the industry because when you talk about telco industry, you're really talking about the edge. You're talking about 5G, talking about industrial benefits for business, because it's not just edge for connectivity access. We're talking about innovative things from self-driving cars to business benefits. It's not just consumer, it's really bringing that together. You guys are really leading with the cloud-native platform from REL, OpenShift managed services. Everything about the cloud-native underpinnings, you guys have been successful as a company. But now in your area, telco is being disrupted. You're leading the way >> Absolutely. Give us your take on this, this is super exciting. >> Well, it's actually one of the most exciting times. I've been in the industry for 30 years. I'm probably aging myself now, but in the telecommunications industry, this for me, is the most exciting. It's where, you know, technology is actually going to visibly change, the way, that everyone interacts with the network. And with the applications that are being developed out there on, on our platform. and, you know, as you mentioned, IoT, and a number of the other AI and ML innovations, that are occurring in the marketplace. We're going to see a new wave of applications and innovation. >> What's the key delivery workload you're seeing, with 5G environment. Obviously it's not just, you know 5G in the sense of thinking about mobile phones or mobile computers as they are now. It's not just that consumer, "Hey surf the web and check your email and get an app and download and, and communicate". It's bigger than that now. Can you tell us, where you see the workloads coming in on the 5G environment? >> You, you hit the nail on the head. The, the, the, the killer application, isn't the user or the consumer and the way that we traditionally have known it. Because you might be able to download a video and that might take 20 seconds less, but you're not going to pay an awful lot more money for that. The real opportunity around 5G, is the industrial applications. Things like connected car. You know automotive driving, factory floor automation. How you actually interface digitally with your bank. How we're doing all sorts of things, more intelligently at the edge of the network, using artificial intelligence and machine learning. So all of those things are going to deliver a new experience, for everyone that interacts with the network and the telcos are at the heart of it. >> You know, I want to get into the real kind of underpinnings, of what's going on with the innovations happening. You just kind of laid out kind of the implications of the use cases and the target application workloads, but there's kind of two big things going on with the edge and 5G. One is under the hood networking, you know, what's going on with the moving the packets around the workload, throughput, bandwidth, et cetera, and all that, that goes on under the hood. And then there's the domain expertise in the data, where AI and machine learning have to kind of weave in. So let's take the first part, first. OpenShift is out there. Red Hat's got a lot of products, but you have to nail the networking requirements and cloud native with containerization, because at large scales, not just packets, it's all kinds of things going on, security, managing compute at the edge. There's a lot of things under the hood, if you will, from a networking perspective. >> Could you share what Red Hat's doing in that area? >> Yep, so, so that's a very good question, in that we've been building on our experience with OpenStack and the last time I was on theCube, I talked about, you know, people virtualizing network applications and network services. We're taking a lot of that knowledge, that we've learned from OpenStack and we're bringing that into the container based world. So we're looking at how we accelerate packets. We're looking at how we build cloud-native applications, on bare metal, in order to drive that level of performance. We're looking at actually how we do, the certification around these applications and services, because they may be sitting in different applets across the cloud. And in some instances running on multiple clouds, at the same time. So we're building on our experience from OpenStack. We're bringing all of that into OpenShift, our container based environment. With all of the tooling necessary to make that effective. >> It's interesting with all the automation going on and certainly with the edge developing nicely, the way you're describing it, it's certainly disrupting the telco cloud. You have an operator mindset a cloud-native operator thinking, kind of, I mean it's distributed computing. We know that, but it's hybrid. So it's essentially cloud operations. So there's an operator mindset here, that's just different. Could you just share quickly, before we move on to the next segment, what's different about this operating model, for the, these new kinds of operators. As, as you guys have been saying, the CIO is the new cloud operator. That's the skill set they have to be thinking. And certainly IT, to anyone else provisioning and managing infrastructure has to think like an operator, what's your view? >> Exactly. They certainly do need to think like an operator. They need to look at how they automate a lot of these functions, because they're actually deployed in many different places, all at the same time. They have to live independently of each other, that's what cloud-native actually really is. So the whole, the whole notion of five nines and vertically orientated stacks of five nines availability that's kind of going out the window. We're looking at application availability, across a hybrid cloud environment and making sure the application can live and sustain itself. So operators as part of OpenShift is one element of that, operations in terms of management and orchestration and all the tooling that we actually also provide as Red Hat, but also in conjunction with a big partner ecosystem, such as companies like Netcracker, for example, or IBM as another example. Or Ericsson bringing their automation tool sets and their orchestration tool sets, to that whole equation, to address exactly that problem. >> Yeah. You bring up the ecosystem and this is really an interesting point. I want to, just hit on that real quick, because it reminds me of the days, when we had this massive innovation wave in the nineties. During that era, the client server movement, really was about multi-vendor, right? And that, you start to see that now and where this ties into here I think, is and I want to get your reaction to this is that, you know, moving to the cloud was all about to 2015, moved to the cloud, move to the cloud, cloud-native. Now it's all about not only being agile and better performance, but you're going to have smaller footprints, with more security requirements, more net, enterprise requirements. This is now, it's more complicated. So you have to kind of make the complication go away. And now you have more people in the ecosystem, filling in these white spaces. So, you have to be performance and purpose built, if you will. I hate to use that word, but, or, or at least performing and agile, smaller footprint, greater security, enabling other people to participate. That's a requirement. Can you share your reactions to that? >> Well, that's core of what we do at Red Hat. I mean, we take open source community software, into a hardened distribution, fit for the telecommunications marketplace. So we're very adapt to working with communities and third parties. That ecosystem is really important to us. We're investing hundreds of engineers, literally hundreds of engineers, working with our ecosystem partners, to make sure that their application is services certified running on our platform. But also importantly, is certified to be running in conjunction with other cloud-native applications that sit under the same cloud. So that, that is not trivial to achieve, in any stretch of the imagination. And a lot of IT technology skills come to bear. And as you mentioned earlier a lot of networking skills, things that we've learned, and we build with a lot of these traditional vendors as we bring that to the marketplace. >> You know, I've been saying on theCube, I think five years ago, I started talking about this and it was kind of a loose formulation. I want to get your reaction, because you brought up ecosystem. Now saying, you know, you're going to see the big clouds develop obviously Amazon and Microsoft came in after and now Google and others. And then I said, there's going to be a huge wave of, of what I call secondary clouds. And you see companies, like Snowflake building on top of Amazon. And so you start to see the power law, of new cloud service providers emerging, that can either sit and work with, across multiple clouds, either one cloud or others, that's now multi-cloud and hybrid. But this rise of the new, more CSPs, more cloud service providers. This is a huge part of your area right now because some call that telco, telco cloud, edge hits that. What is Red Hat doing in this cloud service provider market specifically? How do you help them? If I'm a cloud service provider, what do I get in working with Red Hat? How do I be successful? Because it's very easy to be a cloud service provider now more than ever. What do I do? How do you help? How do you help me? >> Well, we, we, we offer a, a platform called OpenShift which is our containerized based platform, but it's not just a container. It involves huge amounts of tooling associated with operating it, developing in and around it. So the, the concept that we have, is that you can bring those applications, develop them once, on one, one single platform, and run it on premise. You can run it natively as a service in Microsoft's environment. You can actually run it natively as a service in Amazon's environment. You can run it natively in IBM's environment. You can build an application once and run it in all of them, depending on what you want to achieve and who actually provides you the best zoning, the best terms and conditions, the best, the best tooling in terms of other services, such as an AI, associated with that. So it's all about developing it once, certifying it once, but deploying it in many, many different locations, leveraging the largest possible developer ecosystem, to drive innovation through applications on that common platform. >> So the assumption there, is that's going to drive down costs. Can you tell me about why the benefits, the economics are there? Talk about the economics. >> Well, Yeah, so, so, A, it does drive down costs and that's an important aspect but more importantly, it drives up agility, so time to market advantage is actually attainable for you. So many of the telcos when they deploy a network service, traditionally it would take them literally, maybe a year to roll it all out. They have to do it in days, they have to do updates in real time, in day two operations, in literally minutes. So we were building the fabric necessary, in order to enable those applications and services to occur. And as you move into the edge of the network and you look at things like private 5G networks, service providers or telcos, in this instance, will be able to deliver services all the way out to the edge, into that private 5G environment and operate that, in conjunction with those enterprise clients. >> So OpenShift allows me if I get this right, from the CSP to run, have a horizontally scalable organization. Okay. And from a unification platform standpoint. Okay. Whether it's 5G and other functions, is that correct? >> Darrell: That's correct. >> Okay. So you've got that. Now I want to come in and bring in the top of the stack with the other element that's been been a big conversation here at Red Hat Summit and in the industry. That is AI and the use of data. One of the things that's emerging is the ability to have both the horizontal scale, as well as the specialism of the data and have that domain expertise. You're in the industries for Red Hat. This is important because you're going to have, one industry is going to have different jargon, different language, different data, different KPIs. So you got to have that domain expertise, to enable the ability, to, to write the apps and also enable AI. Can you comment on how that works and what's Red Hat do in there? >> So, so, so, we, we're developing OpenShift and a number of our, other technologies, to be fit for the edge of the network, where a lot of these AI applications will reside, because you want them at the closest to the client or the, or the application itself, where it needs to reside. We're, we're creating that edge fabric, if you like. The next generation of hybrid cloud is really going to be, in my view at the edge. We're enabling a lot of the service providers to go after that, but we're also igniting by industry. You mentioned different industries. So if I look at, for example, manufacturing with MindSphere, we recently announced with Siemens, how they do at the edge of the network, factory automation, collecting telemetry, doing real-time data and analytics, looking at materials going through the factory floor, in order to get a better quality result, with lower, lower levels of imperfections, as they run through that system. It's just one industry and they have, their own private and favorite AI platforms and data sets they want to work with. With their own data scientists who understand that, that, that ecosystem inherently. You can move that to healthcare. And you can imagine, you know, how you actually interface with your healthcare professionals here in North America, but also around the world. How those applications and services and what the AI needs to do, in terms of understanding x-rays and looking at, you know common errors associated with different x-rays, so, so our practitioner can make a more specific diagnosis, faster, saving money and potentially lives as well. So different, different vertical markets in this space, have different AI and ML requirements and needs, different data sciences and different data models. And what we're seeing is an ecosystem of companies, that are starting up there in that space, you know, we have Watson as part of IBM, but you have Perceptor Labs, you have H2O and a number of other, very very important AI based companies in that ecosystem. >> Yeah. And you've got the horizontal scalability of the control plane then in the platform, if you will, that gives us cross-organizational leverage and enable that, that vertical domain expertise. >> Exactly. And you'd want to build an AI application, that might run on a factory floor for certain reasons, it's location and what they're actually physically building. You might want to run that on premise. You might actually want to put it in the IBM cloud, or in Zuora or into AWS. You develop it once to OpenShift, you can deploy it in all of those as a service, sitting natively in those environments. >> Darrell, great chat. You got a lot going on. telco cloud, there is a lot of cloud-native disruption going on. It's a challenge and an opportunity. And some people have to be on the right side of history, on this one, if they're going to get it right. We'll know, and the scoreboard will be very clear, 'cause this is a shift, it's a shift. So again, you hit all the key points that I wanted to get out, but I want to ask you two more areas that are hot here at Red Hat Summit 21, as well, again as well in the industry. I want to get your reaction and thoughts on. And they are DevSecOps and automation. Okay. Two areas everyone's talking about, DevOps, which we know is infrastructure as code, programmability, under the hood, modern application development, all good. You add the second there, security, DevSecOps, it's critical. Automation is continuing to be the benefits of cloud-native. So DevSecOps and automation, what's your take, and how's that impact the telco world and your world? >> You can't, you can't operate a network without having security in place. You're talking about very sensitive data. You're talking about applications that could be real-time critical And this is actually, even lifesaving or life threatening, if you don't get them right. So the acquisition that Red Hat recently made around StackRox, really helps us, make that next level of transition into that space. And we're looking at about how we go about securing containers, in a cloud-native environment. As you can imagine, there'll be many many thousands, tens of thousands of containers running. If one is actually misbehaving for want of a better term, that creates a security risk and a security loophole. We're shoring that up. That's important for the deployment OpenShift in the telco domain and other domains. In terms of automation, if you can't do it at scale and if you look at 5G and you look at the radios at the edge of the network and how you're going to provision those services. You're talking about hundreds of thousands of nodes, hundreds of thousands. So you have to automate a lot of those processes, otherwise you can't scale to meet the opportunity. You can't physically deploy. >> You know, Darrell this is a great conversation, you know as a student of history and Dave Vellante and I always kind of joke about that. And you've been in and around the industry for a long time. Telcos have been balancing this evolution of digital business for many, many decades. And now with cloud-native, it's finally a time where you're startin' to see, that it's just the same game, now, new infrastructure. You know, video, voice, text, data, all now happening, all transformed and going digital, all the way, all aspects of it. In your opinion, how should telcos be thinking about, as they put their plans in place for next generation? Because you know, the world is, is now cloud-native. There's a huge surface here of opportunities, different ecosystem relationships. The power dynamics are shifting. It's, it's really a time where there will be winners and there will be losers. What's your, what's your view on on how the telco industry needs to Cloudify, and how to be positioned for success? >> So, so one of the things I, I truly believe very deeply, that the telcos need to create a platform, horizontal platform that attracts developer and ecosystems to their platform, because innovation is going to sit elsewhere. Then you know, there might be a killer application that one telco might create, but in reality, most of those innovations, the most of those disruptors are going to occur from outside of that telco company. So you want to create an environment, where you're easy to engage and you've got maximum sets of tools and versatility and agility in order to attract that innovation. If you attract the innovation, you're going to ignite the business opportunity that 5G and 6G and beyond is going to actually provide you, or enable your business to drive. And you've really got to unlock that innovation. And you can only unlock it, in our view at Red Hat innovation, if you're open. You know, you follow open standards, you're using open systems and open source, is a method or a tool, that you guys, if you're a telco I would ask, you guys need to leverage and harness. >> Yeah. And there's a lot. And there's a lot of upside there if you get that right. >> Yes. >> There's plenty of upside. A lot of leverage, a lot of assets, take advantage of the whole offline, online, coming back together. We are living in a hybrid world, certainly with the pandemic. We've seen what that means. It's put a spotlight, on critical infrastructure and the critical shifts. If you had to kind of get pinned down Darrell, how would you describe that learnings from the pandemic. As folks start to come out of the pandemic, there is a light at the end of the tunnel. As we come out of this pandemic, companies want a growth strategy. Want to be positioned for success. What's your learning coming out of the pandemic? >> So from, from my perspective, which really kind of in one respect was, was very admirable, but, in another respect is actually deeply, a lot of gratitude, is the fact that the telecommunications companies, because of their carrier grade capabilities and their operational prowess, were able to keep their networks up and running and they had to move significant capacity from major cities to rural areas, because everyone was working from home. And in many different countries around the world, they did that extremely, extremely well. And their networks held up. I don't know, and maybe someone will correct me and email me, but I don't know one telco had a huge network outage, through this pandemic. And that kept us connected. It kept us working. And it also, what I also learned is, that in certain countries, particularly Latam, where they have a very large prepaid market. They were worried that the prepaid market in the pandemic would go down, because they felt that people would have less money to spend. And therefore they wouldn't top up their phones as much. The opposite effect occurred. They saw prepaid grow. And that really taught me, that, that connectivity is critical, in times of stress, that we are also, where everyone's going through. So, I think there were some key learnings there. >> Yeah, I think you're right on the money there. It's like they pulled the curtain back of all the FUD and said, you know, necessity's the mother of invention. And when you look at what happened and what had to happen, to survive in the pandemic and be functional, you're, you nailed it. The network stability, the resilience, but also the new capabilities that were needed, had to be delivered in an agile way. And I think, you know, it's pretty much a forcing function, for all the projects that are on the table, to know which ones to double down on. So, I think you pretty much nailed it. >> Thank you. Darrell Jordan Smith, senior vice president of industries and global accounts for Red Hat, theCube alumni. Thanks for that insight. Thanks for sharing. Great conversation around telcos and telco clouds and all the edge opportunities. Thanks for coming on. >> Thank you, John. >> Okay. It's theCube's coverage of Red Hat Summit 21. I'm John Furrier, your host. Thanks for watching. (upbeat music)

>>Mhm Yes. Hello. Welcome back to the cubes coverage of red hat summit 2021 Virtual. I'm john for your host of the cube we're here with Roberto Pellegrini, head of architecture and digital ai services from stam he's remote promoting in from Milan Italy Roberto. Great to see you. Thanks for joining us on the cube. >>Great to see you too john. Thanks for having me here. >>Love the virtual events. We can bring people in from all around the world. I love the virtual. I mean it's one of the trade us for not being in person as we can still get you in. Thanks for coming on. Before we get started. I want to dig into the digital architecture of what you guys are doing. Very compelling in a hybrid cloud. It's got you got all the things going on which I like. But before we start, can you provide a short overview of Snam who are your customers? What is your company's focus and what's your role there? >>Sure. So his name is one of the worst leading energy infrastructure operators. And we basically beat the energy infrastructures and offering the way the services our mission is to guide the evolution of the energy sector and leave the energy transition to a low carbon future. And as you can see in our last investment plan, we declared our net zero-carbon objective to bridge by 2040. This is why we basically are investing a lot in uh, technology in renovating our technology stack in order to provide our business line with the most innovative sustainable energy network, thanks to which we are already guaranteeing stable supplies to europe of natural gas. >>Love your title. Love the fact you've got the ai piece in there. Um, what about specifically is your role? What do you oversee? >>I'm responsible for architecture, digital and artificial intelligence services. That basically means that uh, with with my team and my extended team of the digital technology department are designing the entire technology stack for islam. And I'm specifically focusing more on developing intelligent than usable services for our business lines >>awesome. You guys were there, it's nam have transformed a lot the stack. That's cool. When you get into that, you redesign your applications map. Right? So it's really edge to cloud now. Edge up to the cloud. What were the business drivers and the objectives to reach that goal? Because that's really a great use case. I mean you got the edge to deal with intelligent, you got industrial, global business drivers and objectives. >>Yeah. Our main business drivers has always been to to increase the effectiveness of our processes and business lines so bear support the decision of our internal line of business. And we soon discover that we need a more data in order to do that. And we structure very extensive of your program. But those data provide information about internal states of our assets because they're coming from the census and we thought what about the environment in which our assets are located. So uh following up on that we integrated data coming from remote sensing technologies. So think about drones and satellites. Major data and we soon discover that we needed to renew and extend our technology stack from edge to cloud as you said. And to be the scalable that the platform in order to process this new level of uh data this way we think we will be able to enter the new volume of data that we predict. It will be 100 times what we currently manage and efficiently use AI and machine learning to the riding side from this new scale and complexity. So we're talking about big data >>repairs. I gotta ask you could you take a minute to describe your transformation journey you guys went through and how red hat helped you guys execute the digital transformation? >>Yeah we basically started working in 2018. We read up to set up our 12 grade in a snap. We basically needed to decide what to scale what you lift and shift what we factor in order to move our application to a modern architectural stack. And right up to us with this uh we use open ship for our container orchestration platform and from this we're developing our new application act. Then in 2019 we decided to accelerate the moving of our application workloads. We started moving 10-20 of our work clothes on open shift. And since then most of our new software project Islam, a club native and developed on open shifts. We're still in the process of leveraging modern architecture. So microservices based and using our continual construction platform and other software as a service platform in order to complete the modernization of our application that And we are targeting 2023 2024 to complete the entire process but as you know, is an ever changing landscape. So you basically never complete such a task in some way. >>Do you see red hat technology helping stem in its ecosystem for energy efficiency and aiming for low carbon emissions? >>I think that open ship provide provide us with the right level of flexibility and agility to move at the speed of our new businesses. That's one way to look at the quest and the other one. Uh huh. I think it would be in terms of energy efficiency and the carbon footprint that our application workloads generate. And I think that uh in that in that respect it could happen in the mid to long term, probably so it will be in proportion to the workloads. We will be able to re factor as purely reactive so as non blocking apps. This probably in fact for the same business service could improve the effective resource consumption, so indirectly saving energy and CO two, >>you know, I love this conversation and I know you're in Italy and wish we could be in person but I'm glad to get you on because you guys are kind of an example of the main theme at the conference this year, which is an edge, you know, intelligent edge and IOT, but you know, I O T has been around for a while and we've talked about it before, but now with the cloud and connecting to the cloud, that's a huge topic here at red hat summit 2021 you guys are well versed on the call O. T. Technology operational technologies and what's interesting is kubernetes and containerized orchestration all help operators, operations people. So you have this ot tight integration where the operational technology, old school technology people and the stack and the people in the disciplines are meeting the old I. T. And creating a new thing. So I have to ask you, what are these, what's that world like what are some of the use cases that you're working on and you're planning to deploy? >>Yeah. Yeah. Yeah exactly. It's exactly like that name has a long ot history as you said. So right now we have a complex brownfield uh, situation for our edges and gateways on the field. There are various technical components that resigns on the field. You must consider that Italian network, the Italian Transportation Network has more than 34,000 km of pipeline and differently sides of plants across the country. So we have several already several use cases currently running on our data centers that could benefit we think from distributed processing at the edge. Think about for example physical security. So just to give you an example privacy preserving local video processing for anomaly detection done at the edge, it's much more effective in our opinion. Poor hierarchical processing for data intensive task that involves field data so that you can process the data coming from the field at different level and take to the central data center only was needed. And we're also working on the usual problem there is with with the Widow Tea with the operation of the countries that is standardization. So we have many exogenous components and communication protocol there and you know without a proper rieti stack gathering and normalizing the data for a higher level process could become cumbersome. So security is also is also a relevant topic because it is usually preserve and the physical and natural layer and we we think that we can introduce variety pre main improvements about this. We're expanding the level of cybersec to the food technologists act, bringing modern internet security standard to the edge. We're pushing continue realization to the edge, being able to orchestrate our work clothes from data centers to the cloud. And we think that we this will provide us with a high level of flexibility and a better exploitation of the geographical distribution of our data. And last but not least we're standardizing our gateways and edges and this will help us streamline the message of the transfer conversion and normalization uh of the data we will receive from the field >>awesome. I gotta, I gotta ask for such a great job on the edge. I think that's a great vision. Uh building insecurity, it's important having that edge intelligent is really well done. Congratulations. Love the vision. I gotta ask you, what's your future plans for um Snam technology journey as a whole. What's your vision? What's your next step? >>So well, what we would like to focus on uh in the coming years is how to best leverage the average cloud environment we currently set up. So right now we have an average cloud environment with the data center and one cloud tenant and having our poor clothes running on open ship would make it easier for us to leverage the offering of different club providers and of course to best exploit what we currently have on our tenants. Second one is find the best way to leverage IOT. So as I said before, our focus in the coming years will be to complete our IOT foundation, rolling out our edges are gateways and put our new unified opposition system to work. And this will provide the computational backbone of our intelligent investments. And finally, uh and this is a less objective that is will be built on top of the other two. We must find different ways and export different ways to leverage data and artificial intelligence. So we need to exploit our data uh in order to generate insight for our business lines. Need to the scale of our new data streams, artificial intelligence machine learning, we think will be ubiquitous in our applications right now. We're already using it but not at the scale uh that the new data streams uh well we'll need and most of the algorithms are working on data that are apart from legacy system and scare the system. So they are specifically created for each project. We're about to begin an exciting data journey where everything will reside on a unified data platform and our data scientists, our data analyst in the business lines will be able to derive value from them >>awesome. You know, you guys are great customer use case. I love the real operational impact. I talked with a lot of other practitioners and end user enterprises and I get the same question and I got the statement. They say actually security needs to be built in, but the challenges and where they want to, what they want to do. And I want to get your thoughts on this. If you don't mind commenting, they all say, I want to run cloud native applications, cloud native applications from my data center to the cloud and then out to the edge and with this as a distributed platform, one operation set, whether it's O T I T I want to make that, that's my endgame. In the short term, I get there fast. So I gotta ask you for those people that want that is open shift, a good solution for that. In your opinion, >>we, we of course think it is uh, it is part of our IOT foundation, uh, is not the only technology components, but is one of the, one of the most relevant and it is absolutely happiness in uh, enabling the possibility of orchestrating more clothes uh, from the cloud to the edge. And we will be able to give you more information about that as soon as uh, we will release the first Distribue work clothes within 2021. So I'll be happy to to answer any any questions from our peers or or other colleagues from other industries. >>You guys have thousands and thousands of sites. This is the classic industrial edge implementation, closely monitoring just monitoring the pipes. I mean, you gotta monitoring the system just physically. I mean, this is like a, just a physical thing. So now as you have technology, you guys have to monitor and get that early detection of any gas leaks, this is critical to your business. Um how is that changing? How is that environment changing with technology is more automated? What's your vision? How are you guys looking at that? >>Well, we, we surely are trying to move along to two main drivers. The first is um, unification and standardization of how we monitor all these distributed technology stock. This is very important because even for the simplest use case, you're now dealing with distributed application and this is a entirely different game to what we are used to basically. And and um uh the the other rather the other relevant thing is how can we get the best from um the machines we put on the field. So in other in other in other terms, how can we standardize how we connect to the machines we have on the field and how much intelligence we need to put there and how to test it. And in order to do that, we're thinking about um building a digital twin of our assets that will enable us to being able to test and to end before getting to the real thing on field. How will it work? What are the security vulnerabilities, potential security vulnerability and other aspects uh of the technology infrastructure and the data infrastructure? And we think this is very important because in some way uh in order to provide the acceleration and the scale that we uh are going to provide uh to, to our company, we need to be sure well in advance that what we designed will work in practice without getting to the field. We would like to get into the field where everything is already tested, >>repair too. Great to have you on the cube. Great to see you. Thanks for coming in from Milan Italy. Um cute virtual. It's one of the benefits and hope to see you in person soon at the next event. But great use case, love your environment, love how you're looking at that platform is a distributed platform and bringing that O T T together data center to the cloud to the edge. That's a really relevant use case and architecture. So congratulations. >>Thank you very much, john and I hope to see you too very soon. Alive >>when I'm in Italy, we're gonna come by and do a site visit and uh, see each other coming on. I appreciate it. Thank you. >>Absolutely. >>Okay. Cube coverage for Red Hat Summit 2021. I'm John for your host. Thanks for watching. Mhm. Mhm. Mhm.

(upbeat music) >> Hey, welcome back to theCubes coverage of Red Hat Summit 2021 virtual, I'm John Furry hosts of theCube, Cube Virtual. We're remote, we're not in person this year. Like last year, soon, we'll be back in person. We've got a great guest here, Mark Potts, managing director at Accenture for the Red Hat relationship. Mark, great to see you. Thanks for coming on theCube. >> Hey, thanks for having me John. I really appreciate it. >> Yeah, we've been covering pretty extensively throughout this event, as well as you know the many, many years, the impact of cloud computing. Obviously, you guys have a really big strategic relation with IBM and now Red Hat, Red Hat's part of IBM. It's pretty clear that, you know, that Red Hats got this operating system mindset of open source and, you know, innovation. It's extending into cloud, cloud native, and edge, distributed computing. That's kind of in their DNA if you will, distributed computing and system software and open source, kind of the perfect storm. So, really interesting as this enables new services you guys are on the front lines working with the biggest companies in the world as the global businesses is changing. So, I want to get your take on Red Hat and what you guys are doing together, but first give a quick overview of the center role with Red Hat, your role there and what you do. >> Yeah, thanks. Perfect John. So Mark Potts, as you mentioned I'm the managing director responsible for our global business with Red Hat and our partnership with Red Hat. As you probably saw in our announcements last Fall, around the September timeframe, Accenture made a very large, bold announcement about forming a new cloud first business unit within Accenture. And so we're going to invest $3 billion into that business unit. We're going to dedicate 70 over 70,000 people worldwide to that business unit and that cloud first initiative. And as part of that cloud fishing first initiative we've also developed our new hybrid cloud strategy. And we're looking for new partners and existing partners to help us grow in that hybrid cloud strategy, not hybrid cloud business. We see Red Hat as a very important partner in that business. And as you mentioned there, they've also been, you know, in the distributed computing for a long time. We also see them as a partner for clients that are lifting and shifting and migrating to the cloud on RHEL, like SAP and other workloads like that. And I'm excited to talk to you today about OpenShift, and Ansible, and all those great technologies that Red Hat brings to the table for our hybrid cloud approach and strategy. >> That's awesome. Great investment. And I love Paul coming in that you were saying on his keynote, you know, every CIO should be a cloud operator. I mean, running business at scale this is what hybrid cloud is all about. And so with your new hybrid cloud strategy and the formation of the new business group at Accenture what kind of challenges are you guys looking to solve? What are the opportunities that you're seeing for companies? How do you guys solve those challenges? What do you, what are you guys looking at right now? >> Yeah, that's a great question. As you mentioned, the keynote. So, Karthik Laredo actually runs our cloud first business was actually part of that keynote with Larry Slack as well, or Larry Stack, sorry, as well. And so he mentioned in his keynote something called the cloud continuum, right? And so historically Accenture has been working with our partner on cloud native development moving to about 20 to 25% of the existing workloads in the data center, the easy stuff to the cloud, right? But now we realize that there's a need for the hybrid cloud. There's a need to modernize, maybe on premise, there's a need to maybe modernize in the cloud one way or the other. And then we also look at the holistic view of cloud, on-prem, edge. And that's what Karthik is talking about when he's talking about the, the cloud continuum. And that's a very important part of our strategy within Accenture, and OpenShift really helps us meet those needs. So if a client is a little bit nervous about taking some of those complex workloads but they want a modernize and they want to use the latest and greatest cloud native technologies but they want to do it on-prem and move to the cloud a little bit later they can do that with OpenShift, right? And Red Hat. That's a great platform for that. Maybe it's a client that wants to lift and shift and get to the cloud as soon as possible, close their data centers save that cost of money and then modernize later, but they don't want to necessarily be locked and want to be locked into one cloud provider. Again, OpenShift is great for that. Take those legacy workloads that you move to the public cloud, modernize them on Red Hat OpenShift maybe it's Rosa on AWS, maybe it's aro on Azure. And then when you're ready to you can move those to any other public cloud, if you'd like to, when, when you're ready to, right. And that whole control plan as we call it, being able to see across public cloud, on-prem, the edge is really important for our story and our strategy, and Red Hat OpenShift, and Red Hat Satellite. And those technologies bring a lot to the table for us to meet those needs of our clients and our customers. >> That's great insight there, Mark. I really appreciate that. And one of the things brought up when he was saying that I was thinking to myself, okay, the cloud conversation has many evolutions and, you know, go back five years. It was all moved to the cloud. Everyone was moving to the cloud. That was the big discussion point. Now it's, you know, enterprise ready the cloud get that next level of scale. And as you know, in the enterprise everything we do all everything complicated is a lot of legacy and is existing stuff. So this, you know, this, this is the next enterprise at scale is the conversation that includes hybrid multi-cloud or running on that, on the horizon. So with that, can you expand on what you mean by this cloud continuum that you refer to, that essentially refers to and what is needed to make it a reality for customers? >> Yeah, I mean, what's really needed is the latest greatest in hybrid cloud technology like OpenShift and what Red Hat brings to the table, right. It's also new skills and new capabilities, and, and policy management and those types of things that are important for our company to decide when they're ready to move those workloads to the cloud, right. They need the ability to see across their entire infrastructure. Like I mentioned earlier, whether that be a public cloud provider, whether that in their existing data center, in a colo, or on the, in the edge, like in a retail store or something like that, they need, we need the ability to see across those, that seeing all that infrastructure is a single control plane. So we can manage and know where things are to feel confident about security and everything with our clients. The other big thing that we need is skills. Skills to, you know, build the migration, the modernization, and more importantly, the interaction and integration into legacy workloads like the mainframe, for example, Accentures got a lot of use cases, leveraging Red Hat OpenShift for our cloud coupling solution, where we interact and build new applications that connect to the mainframe sitting right next to the mainframe but their new digital mobile applications, web applications that can be quickly modified and deployed in, into production at a rapid pace. Right, and so when we look at everything that's needed, it's skills, it's technology partners like Red Hat, and then it's, it's really building assets and offerings to help make that journey for our clients better, and, and secure. >> We just found out here at the event that you guys at Accenture had been recognized as Red Hats, global systems integrated partner of the year for North America, congratulations on that. What do you see as some of the key reasons for the recognition? Was there anything that they called out in particular? Obviously you guys have a great track record well-known brand you've known for, you know, creating a lot of value for companies as they do digital transformation. What's the, what's the recognition for this year? >> Yeah, we're super excited about this, right. I mean, this is, we've been partners with Red Hat for a long time. I think we were one of the first system integrators, if not the first system integrators to partner with Red Hat many years ago. Right, so, to get this award, and get it for the first time, is super exciting for us. Right, and so we're very grateful for that recognition and opportunity. You know, I think what really, what really, what got us the recognition for this award was really the effort we put into our partnership over the last 12 to 24 months, right. We had had a really big business in Europe with GDPR and, and the risk averse of going to the public cloud in Europe. OpenShift and Red Hat really had taken off. In North America our business was lagging behind Europe and we significantly invested with Red Hat and new offerings and new clients and new people, right. New talent to build a better business and partnership in North America. You know, I think a lot of the things that we got recognized with were what I mentioned earlier some of our cloud coupling solutions for an insurance client in North America where we're building cloud native applications on Red Hat OpenShift sitting next to the mainframe we're building new cloud, cloud native applications for our transportation company in, in the South region of the US right? So it's really that business transformation work that we're doing working with the legacy, but building new core applications for our customers that are truly portable, nimble and agile, and they can use to get speeds to the market and get to the cloud. >> Cloud first organization you guys are investing billions of dollars, 3 billion. That was referenced. I saw an article. I think we covered it as well on (mumbles). Congratulations, cloud first also implies that cloud native is going to be there. Mark, in all your years in the industry talk about from your personal perspective and even from Accentures, the, the shift that's happening because it's almost mind blowing what's going on in the sense of so fast this is accelerated, even the pandemic exactly accelerate even further. The opportunities that were, that are available now that weren't there before and what it's done to the project timelines and what it's done as a forcing function. Could you share your view on the reality of the current situation and opportunities for companies to take advantage of that wave? >> Yeah, and, and I think Accentures done a great job talking about this recently, even from our C-suite down, right. And Karthik we'll mention, has mentioned this as well in his keynote. I mean, we are seeing an acceleration to get to the cloud that was completely unplanned for us. I think the, the numbers I heard was we thought most clients are going to get to the cloud in eight to 10 years and be fully in the cloud in eight to 10 years. But that's accelerated with COVID and the pandemic, right. We're looking at four to five years we think most of our clients will be in a majority of their, their infrastructure and everything, a new, a new applications and legacy applications will be in the cloud. Right, so the, the, the change and the impact of the pandemic had, had a significant impact on our customers and their need to, to, to get to the cloud. We've even seen those that were leaders in the cloud journey accelerate even more, right. And, and they're being rewarded for that acceleration. Right, a lot of our customers that were first to cloud are seeing the benefits and seeing the, the, the ability to scale and for the pandemic, like, like a lot of our customers in the, in the US in particular. And I think OpenShift is going to help them, help us with that, right, And, and Red Hat in particular. And let's not be lost on the fact that Realms is a great product out there as well. We have many of our clients that are running SAP on Realm and that lift and shift and moving SAP to Azure or AWS or Google or something like that is, is a viable solution for our, to help accelerate our customers as they expand, right. We've seen internationally a lot of our customers that have been really focused just in their local region are now expanding their business outwards, and now they need to get to the clouds to be able to expand those businesses. >> You know it's interesting Mark, just as we're talking, just, you know thinking about my experience over the years in the computer industry everything had to display something else, disrupt something, you know, the mainframes were disrupted by client server. Now we're living in an era where with the containers and microservices and service meshes and cloud native technologies you can embrace existing legacy and abstract away some of the complexity on the integration side, right? So you don't have to kill the old to bring in the new. And I think this phenomenon has opened up a new class of services and, you know the people I talk to and interview the leaders in the industry all have the same kind of view. And the ones that stand out are the ones that recognize that the operating system of business will be software. And that software hasn't yet been built in clouds. The beginning, it's not just one cloud. So I think what's interesting about Red Hat is that their operating system people you almost to see, you know, Arvin kind of snapping the lines and kind of cornering the market on the operating system for business and applications then are a thousand flowers that bloom from that. So, very interesting take here again. That's my opinion. I don't think they've said that formally but if you look at it, that's kind of what's going on. What's your reaction to that? >> I think you're a hundred percent, right. I mean, it, you know, I, I also carry a little bit of the responsibility on the IBM side. And you mentioned mainframe and I've mentioned mainframe a handful of times, right? There's a lot of customers that have this legacy estate like the mainframe in particular but they need to be nimble. Right, they need to be agile and mainframe is a challenge sometimes around that. Right, and so to your point creating those applications that participate with the mainframe allowed the mainframe to participate better with these cloud native applications and these new digital transformation applications is a very key component to it. And so I, a hundred percent agree with with everything you said. And I think, I think we're going to see more around this operating system type software. And I, you almost, to an extent, you you kind of view Red Hat OpenShift as kind of that new operating system, right? And you look at some of the announcements that Red Hat has made around Palentier, right, and adding Palentier and ISV to their marketplace to allow customers that are bought OpenShift or make it easy for clients to buy Red Hat OpenShift, and then bring in these ISVs that have been certified, they're secure, they're easy to consume and buy it through Red Hats marketplaces is very exciting and very interesting, and very easy to do, right. Once you get that Red Hat OpenShift layer in there, that operating system and now you're bringing in products all over the place, right. And, and all the new stuff. And I think we're going to see a lot more of those announcements during summit as well. >> Yeah, I think it was a 20 year run here. It's trillions of dollars as it's been forecasted. Mark, great to have you on. Super valuable resource. Great insight! While we got you here let's get a quick free consulting a minute here for the customers watching. What's your advice. I need some help here. I'm going to go to the cloud. I want a good, I want enough headroom so I can grow into I want to foreclose any opportunities. I want to move to the cloud. I want to have a hybrid distributed computing architecture. I want to program my business. I want infrastructure as code. I want dev sec ops. What's my playbook? What should I do? >> So Accenture's got a real smart approach and strategy around us. We leveraged an, an assessment approach really to look at what's in your what's in your data center today and what, what you have from an infrastructure and application standpoint, there should be-- We have a seminar where it's can completely rewrite an application, and we would apply those six hours or seven hours to that assessment to help you figure out the disposition of your applications and your infrastructure to figure out what is the right cloud. What's the right journey. I mean, we talked about, you know the mainframe and mainframe being an anchor in a lot of our client's data centers, right. How do we move those applications that have data gravity challenges to those legacy applications, to the cloud. How do we consider that? So the right way to do it is take a holistic approach. Do the assessment, do the disposition of your applications. And then let's let Accenture put together a full plan of how we would migrate you incidents into the public cloud. >> Mark FOS, managing director of Accenture. Congratulations on your North America award, partner of the year. And also awesome to hear. And we've been covering again cloud first. Totally believe it, great investment. That's going to pay back huge dividends for you guys and you know, having the hybrid, which is pretty much determined as a fact now in the industry. Congratulations, thanks for coming on. >> Perfect, thanks, and thanks for having me, and thank you Red Hat for the award. Really appreciate it. And look forward to talking to you soon. >> All right, this is theCubes coverage of Red Hat summit, 2021, virtual. This is the Cube virtual, I'm John Furry, your host. Thanks for watching.

(ambient music) >> Hello and welcome back to theCUBEs' coverage of Red Hat Summit 21 virtual. I'm John Furrier. Host of theCUBE. This year, virtual again, soon to be in real life, Post COVID. As the fall comes into play, we're going to start to see life come back and the digital transformation continue to accelerate. And we've got a great guest, Stefanie Chiras, Senior Vice President and General Manager at Red Hat. CUBE alumni. Great to see you. Stephanie, Thanks for coming on. >> No, it's my pleasure, John. Thanks for having me. I'm thrilled to be here with you and look forward to doing it in person soon. >> I can't wait. A lot of people on their vaccine, some say that by the fall vaccines, where pretty much everyone 12 and over, will be vaccinated but we're going to start to see the onboarding of real life again but never going to be the same. Digital business, at the speed of online, offline, almost redefined and re-imagine. Not the old, offline, online paradigms. You're starting to see that come together. That's the focus. That's the top story in the technology industry. That really brings together the topic that I'd like to talk to you about, which is edge computing and RHEL and Linux. This is the topic where all the action is. Obviously hybrid operating models have been pretty much agreed upon by the industry. That is the way it is. Multicloud is on the horizon but edge part of the distributed system. This is where the action is. A natural extension to the open hybrid cloud which you guys have been pioneering. Take me through your thoughts on this edge computing dynamic with RHEL. >> Yeah. So as you said, we have been on this open hybrid cloud strategy for eight years or so. Very focused on providing customers choice both in where they run, what they run, how they run their applications. And the beauty of this strategy is the strategy endures because it's able to adapt to new technologies coming in. And as you said, edge is where things are happening now. It's enabling customers to do so many new and different things. You take kind of all of the dynamics that are happening in technology with data being produced everywhere, new even architectures and compute capabilities that can bring compute right out there to the data. You get 5G networks coming in and incredible advances in telco and networking. You pull that out. Now you've created a dynamic where the technology can really make edge a viable place to now extend how open hybrid cloud can reach and deliver value. And, our goal is to bring our platform and our ecosystem to do everything from the core of your data center out to public clouds, multiple public clouds. And now bring that all the way out to the edge. >> You know, we talk about edge, you know, we talk decentralization, distributed computing. These are the paradigms that are getting re-imagined, if you will, and expanded. You guys talk about and you talk about specifically this idea of digital fast economy requires a new kind of infrastructure. Talk about this because this is, you know, some say virtual first, media first, data first, video first, I mean, developer first, everything's like a first thing, but this is...focuses on the new normal. Take us through this new economy. >> It's really about how you focus on being able to deliver digitally with decisions near the data, and to be able to adapt to that. It's thinking about how you take footprints and now your footprint out at the edge becomes a part of that. One of the things that's really exciting about edge is it does have some specific use case requirements. And we're seeing some things come back. Things like, I mean, we've talked in the past about heterogeneous computing and heterogeneous architectures and the possibilities that exist there. Now at the edge we're seeing different architecture show up, which is great to see. Being able to bring a platform that can allow the use of those different architectures out at the edge to deliver value is a great thing. In addition, we're seeing bare-metal come back out at the edge. You can really imagine spaces where out at the edge you have new architectures with bare-metal deployments and you're operating containers that are touching directly onto that bare-metal. It brings a whole new paradigm to how to deliver value but now we can bring the consistency of what Linux and RHEL and OpenShift with containers can bridge across that whole space. >> So heterogeneous computing, distributed computing, multi-vendor, if you kind of weave those keywords together you have to have a supporting operating model that allows for different services, cloud services, network services, application services, work together. This kind of puts an emphasis on a control plane, a software platform that can bring this together. This is the core, if I understand the Red Hat strategy properly, you guys are going right at this point. Is that true? >> Yeah, that's absolutely right. It is. When everything else, you can get value from everything else changing what stays the same to help keep you efficient and consistent across it? And that's where we focus on the platforms. And as open hybrid cloud changes with different optionalities, our focus is to bring that sort of single common control plane that provides consistency. So you can develop once and reuse, but make it adaptable to how you want to leverage that application as a container, as a BM, on bare-metal, out at the edge, on multiple public clouds. It's really about expanding that landscape that open hybrid cloud can touch. And you'll see in other discussions, you know, one of the places we're going into new is in the edge, manage services also become part of that paradigm. So, it really is our focus to be that common control plane, provide accessibility while still delivering consistency. And let's face it consistency down at the operating system level, that's what starts to deliver your things like security. And boy, it's a critical topic today, right? To make sure that as you expand and distribute and you've got compute running out there with data, security is top of mind. >> I have to ask you, we've been having many conversations in the open source community, Linux foundation, CNCF, KubeCon, CloudNativeCon, and other other communities. And the common thread is... And I want to get your reaction to this statement, the statement is "Edge computing's foundation must be open across the board." Talk about that. What's your reaction to that? And how does that relate to Red Hat and what you guys are doing at the edge and with RHEL. >> I mean, we really believe an open source brings compatibility and standardization that allows innovation to grow. In any new technology, fragmentation causes the death of the new technology. So you...our focus is, it will have to be, I mean, we firmly believe it absolutely has to be built on an open platform that has standards so that the ecosystem, and the ecosystem around edge is complex. You have multiple hardware capabilities, multiple vendors, any edge deployment will be multi-vendor. So how do you pull all of that together in an ecosystem? It is about having that foundation be open and be able to be accessible and built upon by everyone. >> You know, you were talking earlier about the edge in 5G and we just talking about open. This is the future of computing, both consumer and enterprise, whether it's, you know, a factory or a consumer wearing a wearable device or sensors on cameras, on lights and cities and all these things are happening. I want to get your reaction to that because there's a difference between industrial IOT devices and consumer IOT devices. Both have different ramifications. You know, 5G certainly is not so much a consumer as it is also a business technology, as you get the kind of throughputs you're seeing. So, both consumer and industrial enterprise capabilities are emerging. What's your position on that? >> I mean, I think edge is one of those things that it's been hard for people to wrap their head around a bit because what we deal with edge in our own personal lives, whether that be in our connected home or our mobile phone, that's one view of what edge does in one set of value that it does. But from a separate lens edge is everything from how telco is deployed to how data is aggregated in from sensors and how decisions are made. I mean, we're seeing in spaces, whether it be in manufacturing and adding AI onto manufacturing floors, how do you have, you know, in vehicles, I mean, vehicles are becoming sort of mobile software centers now. So, there is a whole shift in edge that is different from industry 4.0 and from kind of operational transformation edge that it's driving all the way into kind of the things that we see everyday which is more the global space and how our homes are connected. And I think now we're starting to see a real maturity in how the world views edge to be able to compartmentalize what enterprise edge is able to do, how edge can change operational technologies, as well as how edge can change kind of our daily lives. >> Great vision and great insights. Definitely awesome. Thought leadership there. I totally agree. I think it's exciting you see confluence of so many awesome technologies and a bright future with the technology platforms and with society open now is defacto everything not just in tech and truth, whether it's journalism or reporting, society and security, again, trust. Open, trust, technology. I got all come in together. The confluence of all those are as going on. So, I think you've got a great read on that. So thanks for sharing. Red Hat Summit. What's new? Tell us what's new here and what's being talked about that no one's heard before and what's the existing stuff that's getting better. >> Yeah, we'd love to. So we are really doubling down on edge within our portfolio. We have, you probably saw in November, we had some announcements, both in OpenShift as well as in RHEL in order to add features and capabilities that deliver specifically for edge use cases. Things like the ability to do updates and roll back in a RHEL deployment. We are continuing to drive things into our products that cater to the needs of edge deployment. As part of that, we are engaged with a whole lot of customers today deploying their edge, and that's across industries, things from telco to energy to transportation. And so, as we look at all of those cases that we've been kind of engaged with and delivering value to customers, we are bringing forward the Red Hat edge brand. It's going to be our collection point to shine a spotlight for how the features and functions in our portfolio can come together and be used to deliver in edge deployments. It'll be our space where we can showcase use cases, where we're seeing success with customers but really to pull together 'cause it is a portfolio story and it's an ecosystem story. How do we pull that together in one spot? And in order to support that here at Summit, we are announcing some really key additions into RHEL 8.4 that really focused on the specific needs of what edge is driving. You'll see things like the ability in RHEL to create streamlined OS image generation. And we can simply manage that into container images. That container magic, right? To be able to repeatably deploy an image, repeatably deployed application out to the edge, that has become a key need in these edge deployments. So we've simplified that so operations teams can really meet the scale of their fleets and deploy it in a super consistent way. We've added capabilities. Image builder, we had brought out already, but we've added capabilities to create customized installation media. It's simplifies for bare-metal deployments. And as I mentioned out at the edge work, it's really small bare-metal deployments where you can bring that container right onto their bare-metal. Can imagine a lot of situations where that brings a lot of value. We introduced in RHEL 8.0 podman as our container engine. And we've added new automatic updates in that. So, again, getting back to security fixes. Simple to ensure that you have the latest security fixes. Application updates and we're continuing to add changes and updates into Universal Base Image. Universal base image is a collection of user space packages that are available to the community, fully redistributable. The goal of those user space packages is to enable developers to be able to create container images with those packages included and then they can redistribute them when they're run on OpenShift or they're run on RHELs. So we can really work through that user space and to that host, matching, and we can stand behind that matching, then we can support it, but it allows for a lot of freedom and flexibility with Universal Based Image to really expand where we can go and help folks kind of create, deploy and develop their applications. We're also moving into, I think, one of the things you see in edge is a real industry slant. We're starting to see edge deployments take on real industry flavors. And so we are engaging in some spots, things like, whether it be from automotive to industrial and operational technology. How do we engage in those industry verticals? How do we engage with the right partners? One of the things that's key that we're looking at, 'cause it is core to what we do, is things like functional safety. And, we're working with a company called Axeda who's a leader in this space for functional safety, for how do we bring that level of security and certification into the RHEL space when it's deployed out there at the edge? So, it's an exciting space, everything from the technology to the partnerships, to how we engage as industry verticals. But this is a... I'm really excited to have the Red Hat... >> I can tell. Super excited. You know, one of the things that's interesting is that the industry trivia as theCUBE has been around for 11 years now. We've been to all of Red Hat events and IBM events for many, many years. But I actually interviewed Arvind, who is now the CEO of IBM, who now owns Red Hat, at Red Hat Summit in San Francisco, like three years ago. And, he had a smile on his face and he just announced the acquisition shortly after 'cause I was hitting him with some cloud native questions. A lot of this stuff about kind of what's hitting today and you just laid it out. RHEL, if I get this right, and of course I'm connecting the dots here in real time, It's an operating system that hits bare-metal, open hybrid cloud, edge, public cloud and across the enterprise. It's an operating system. Okay. So, okay. We know all know that. Okay, you apply that to a cloud operating model, you have some system software. So the question, which by the way is, what's going to power the next gen cloud. I think is what Arvind wants and you guys hope. So the question for you Stephanie is, what applications do you hope to create on top of... and what do you have today that RHEL is powering because if you have great systems software like RHEL, that's enabling applications. I'm assuming that's cloud services, that's new cloud native. Take us through that part of the stack. What's your vision? >> Yeah, absolutely. And I think one of the key things that I would touch on is that it's part of the reason we build our portfolio the way we do, right? We have RHEL of course for your kind of Linux deployments that you described but RHEL CoreOS is part of OpenShift and that consistency delivers into the platform and then both of those can then serve the applications that you need to deploy. And we are really excited to be able to do things like work with the transportation industry, folks like Alstom who do really bring edge capabilities all the way out into the rails of the train systems. They, from high speed trains to metros to monorail, they have built their whole strategy on RHEL and Ansible Automation Platform. It's about the platform, just as you said that operating system, delivering the flexibility to pull the applications on top and those applications could be anything from things that require functional safety, right? Things like in vehicles, as an example, could be anything from artificial intelligence, which goes out into manufacturing. But having that stable platform underneath, whether or not using RHEL or OpenShift, that consistency, it opens up the world to how applications can be deployed on it. But I am super excited about what AI and machine learning out at the edge can do and what being able to bring really hardened security capabilities out to the edge, what that opens up for new technologies and businesses. >> That's super exciting. And I think the edge is a great exclamation point around any debate anyone might've had around what the distributed architecture is going to look like. It's pretty clear now what the landscape is from an enterprise standpoint. And given that, what should people know about the edge? What's the update? What's the modern takeaway now that we're, I mean, obviously COVID has proven that there's a lot of edge applications that kind of were under forecast or accelerated, working at home, dealing with network security, you name it. It's been kind of over-amplified, for sure. But now that COVID is kind of coming, there's light at the end of the tunnel, coming to an end, it's going to be still a hybrid world. I mean, hybrid everything, not just hybrid cloud I mean hybrid everything. So edge now can not be ignored. What should people take away from Red Hat Summit this year? >> Absolutely. I think it's the possibilities that edge can bring. And there are different stages of maturity. Telco, beautiful example of how to deploy edge. In telco, as a market continues to drive the.... kind of pioneer what is done in edge. You see a lot of embedded edge, right? Things that you deploy or your business may deploy that is... you purchase it from a company and it's more embedded as an appliance level. And then there's what the enterprise will do with edge specifically for their businesses. What I think you'll see is a catch-up across all of these spaces, that those three are complimentary, right? You've may consume some of your edge from a partner and a full solution. You may build some of your own edge as you expand your data center and distribute it. And you're made leverage. Of course you'll leverage what's being done by the telcos. So what I think you'll see is a balance in multiple types of edge being deployed and the different values that it can deliver. >> Stefanie, final question for you. And thanks for taking the time. Great conversation and interview here for Red Hat Summit. As the General Manager you're constantly talking to customers. I know that. Personally, you've told me that. Many stories off-camera. But also you have to look inside the organization, run the business, keep an eye on the product roadmap and make sure everything's pumping on all cylinders. What is the customer telling you right now? And what's the common pattern that people are talking about, things that they're looking to do, projects they're funding, and what's the most important story that we should be covering. And what's the most important story people aren't talking about? >> So I think one of the things, I'm really seeing, as you mentioned at the beginning we've been talking about open hybrid cloud for a long time. There was a period of time where hybrid cloud was happening to folks or kind of, it was a bit... some of developers were using it from here. Now, hybrid cloud is intentional. It is very intentional about how customers are strategically taking a view of what they deploy where, how they deploy it and taking a bit advantage of the optionality that hybrid can do. So that's one of the things I'm most excited about. I think the next steps that will happen is a balancing of how do they expand that out into, how do they balance a managed services addition into their hybrid cloud, how do they manage that with also having VMs and a large VM deployment on prem. To me now the biggest thing that is being looked at is how do companies make these decisions in a strategic way that is kind of holistic rather than making point decisions. And I am seeing that transition in the customers I talk to. It's not how do I deal with hybrid cloud, it's how do I make hybrid cloud work for me and really deliver value to me and how do I make those decisions as a company. And honestly that requires kind of what you talked about earlier. It requires within those customers to have the structure, the organizational structure, the communication, the transparency, the openness that you've talked about. That takes a strategy like open hybrid cloud a long way. So it's both the people and the process and the technology coming together. >> You know, Stefanie, we do so many interviews in theCUBE and you've been on so many times, you go back and look back and say, "You know, in that year, 2010, we were talking about this." Chiras, I was talking to a friend and we were just talking about 2015. That was the big conversation of moving to the cloud, you know. Startups are all there. Born in the cloud. So, you know, early generation was all about the startup cloud. They all got that. 2015 was like move to the cloud. This year, the conversation isn't about moving to the cloud is about scale and all those enterprise requirements now that are coming from the hybrid. Now that that's been decided, you starting to see that operating model connect. So it's not so much moving to the cloud, it's I've moved to the cloud and now I got to run some now enterprise grade scale operationally. What's your reaction to that? >> Absolutely. I mean, to me, the, I love the intentionality that I'm seeing now in customers, but when it comes down to it, it's about speed of deploying applications, it's about having the security and the stability in order to deploy that, to give you confidence in order to go out and scale it out. So to me, it is speed, stability and scale. Those three comes together. And how do you pull that together with whole of the choices we have today and the technologies today to deliver value and competitive differentiation. >> Open source is winning and you guys are doing a great job. Stefanie, thank you for coming on and spending so much time chatting here in theCUBE for Red Hat Summit. Thanks for your time. >> Well, my pleasure, John. Good to see you. >> Okay. Great to see you. This is theCUBEs' coverage of Red Hat Summit 21 virtual. I'm John Furrier with theCUBE. Thanks for watching. (ambient music)

>>mhm Yes. >>Welcome back to the cubes coverage of red hat summit 2021 virtual. I'm john for a host of the cube we're here in Palo alto. Were remote with our great guest here cube alumni. I've been on many times chris wright, Senior vice president and CTO of red hat chris great to see you. Always a pleasure to have you on the screen here too. But we're not in person but thanks for coming in remote. >>Yeah, you bet. Glad to be here. >>Not only were talking about speeds and feeds, digital transformation going under the hood here we're gonna talk about red hats, expanded collaboration with boston University to help fund education and research for open source projects. So you guys have a huge relationship with boston University. Talk about this continued commitment. What's the news, what's the, what's the story? >>Well, we have a couple different things going on uh and and the relationship we have with the EU is many years in. So this itself isn't brand new. Um one of the things that's important to highlight here is we are giving something north of $550 million dollars worth of software to be you really in pursuit of running uh powering and running scaled infrastructure. That's part of the open hybrid class. Um and that's that's an important piece which we can touch on a little bit as we talk to this conversation. The other one is like I said, this isn't a new relationship with the U. And what we're doing now is really expanding the relationship. So we've we've built a great connection directly with the You were substantially expanding that. Um The original relationship we had was a $5 million relationship spread over five years now. We're talking about a $20 million Relationship spread over five years. So really a significant expansion. And of course that expansion is connected to some of the work that we plan to do together in this open hybrid cloud infrastructure and research space. So a lot of things coming together at once to really really advance the red hat ca laboratory at the U. That combined effort in bringing you know, cloud research and open source and all these things together >>and a lot of actually going on. So basically the boston area lot of universities, but I love the shirt you're wearing with his red hat innovation in the open. This is kind of one of those things you also mentioned out of this huge subscription of software grant that's going to be you just a huge number give value for for the boston University. But you also have another project that's been going on the collaborative research and education agreement called red hat collaborative orI Okay, this was in place. You mentioned that. How's that tying in because that was pre existing. Now. You've got the grant, you got your funding more and more research. Talk about how this connects into the open cloud initiative because this is kind of interesting. You're not bringing hybrid cloud kind of research and practical value in A i ops is hot. You can't you can't go anywhere these days without having great observe ability. Cloud native more and more is more complex and you've got these young students and researchers dying and get their hands on it. Take us through the connection between the CA laboratory and open open cloud. >>So the CA laboratory is a clever name that just talks about collaboration and research laboratory type research. And initially the CA laboratory focus was on the infrastructure running the cloud and some of the application workloads that can run on top of an open cloud infrastructure uh that are that's very data centric. And so this is uh an opportunity for multidisciplinary work looking at modeling for um for health care, for example for how you can improve imaging and we've had a great results in this collaboration. Um We've talked at times about the relationship with the boston Children's Hospital and the chris project not related to me, but just similar acronym that spells chris. Um and these things come together in part through connecting relationships to academia, where academia as research is increasingly built in on and around open source software. So if you think of two parallel worlds, open source software development, just the activity of building open source software, it brings so many people together and it moves so quickly that if you're not directly connected to that as an academic researcher, you risk producing academic research results that aren't relevant because it's hard for them to connect back to these large, fast moving projects, which may have invented a solution to the problem you've been focused on as an academic if you're not directly connected. So we see academia and open source coming together to build really a next generation of understanding of the scientific in depth and he's joining the >>train operations you're talking about here though, this is significant because there's dollars behind it, right? There's real money, it's not >>just the right software, >>it's it's a center, it's a joint operation. >>That's right. And so when you think about just the academic research of producing um ideas that manifest themselves as code and software projects, we want to make sure we're first connecting the software projects to open source communities in with our own engineering experience, bringing code into these open, open source projects to just advance the the feeds and speeds and speeds, the kind of functionality the state of the art of the actual project. We're also taking this to a new level with this expanded relationship and that is software today. When you, when you operate software as a cloud, a critical part of the software is the operationalization of that software. So software just sitting there on the shelf doesn't do anybody any good. Even if the shelf is an open source project, it's a tar ball waiting for you to download. If you don't ever grab it and run it, it's not doing anybody any good. And if the challenge of running it is substantial enough that it stops you from using that software, you've created a barrier to the value that's locked inside that project. The focus here is how can we take that the operations experience of running a cloud, which itself is a big complex distributed system, tie some of those experiences back into the projects that are used to build that infrastructure. So you're taking not just the output of the project, but also the understanding of what it takes to run a project and bringing that understanding and even the automation and code associated with that back into the project. So, your operational izing this open source software and you're building deeper understanding of what it means to operate things that scale, including data and data sets that you can use to build models that show how you can create the remediation and closed loop systems with AI and machine learning, you know, sort of synthesizing all the data that you generate out of a big distributed infrastructure and feed that back into the operations of that same infrastructure. So a lot going on there at the same time operationalization as as an open source initiative but also um really the understanding advancement of A I and data centric operations, so ai ops and closed the remediation. >>Yeah, I mean, devops developer and operations to operationalize it and certainly cloud Native put an emphasis on Day two operations, which leads a lot more research, a lot more uh student work on understanding the coding environment. Um so with that I got to ask um I asked you about this uh massachusetts focused or this open cloud initiative because you guys are talking about this open cloud initiative including this massachusetts. Open Cloud, what is that? What is the massachusetts? Open Cloud sounds like you're offering a kind of open person, not just bu but other um Yeah, institutions. >>That's right. So the the M o C massachusetts open cloud is itself a cross um organizational collaboration bringing together five different academic institutions in New England In massachusetts. It's bu it's Harvard mit, its Northeastern and its U. Mass. Coming together to support a common set of infrastructure which is cloud. It's a cloud that runs in a data center and then um it serves a couple of different purposes. One is research on clouds directly. So what does it mean to run a cloud? What does it look like from a research point of view to understand large scale distributed systems? And then the other is more on top. When you have a cloud you can run workloads and those workloads scaled out to do say data processing, looking at the implications of across different fields which could be natural sciences, could be medicine, could be, even political science or social science is really a multidisciplinary view of what it means to leverage a cloud and run data centric workloads on top. So two different areas that are of a focus for the M. O. C. And this becomes this sort of vehicle for collaboration between Red Hat View and the Red Hot Laboratory. >>So I have to ask only because I'm a big fan of the area and I went to one of those schools, is there like a bean pot for technical hackathons where you get all the schools matched up against each other on the mass open cloud and compete for who gets bragging rights and the text city there. >>It's a great question. Not yet. But I'll jot that down here in hell. Up on that. >>Happy to sponsor. We'll we'll do the play by play coverage, you know. Great. >>I love that. Yeah, kind of twitch tv style. The one thing that there is which is very practical is academic research grants themselves are competitive, right? People are vying for research dollars to put together proposals, Bring those proposals to um the agency that's that's that's giving out grants and winning those grants is certainly prestigious. It's important as part of her research institutes continue to fund the work that they're doing. Uh Now we've been associated uh through the work we've done to date with the U. With Yeah almost $15 million 20 papers. So there's there's a lot of work you can't quite call the play by play. It's a >>scoreboard. I mean their numbers you can put numbers on the board. I mean that's what's one of the things you can measure. But let me ask you on those grants. So you're saying this is just the bu you guys actually have data on um the impact of the relationship in terms of grants and papers and stuff like that academic work. >>That's right. That's right. And so those numbers that I'm giving you are examples of how we've worked together with the u to help their faculty generate grant dollars that then fund some of the research that's happening there together with redhead engineers and on and on the infrastructure like the massachusetts Open cloud. >>That's a good way to look at the scoreboard. It's a good point. We have to research that if you don't mind me asking on this data that you have um are all those projects contributing to open source or do they have to be? That's just generic. Is that all of you all papers around bu is part of the research. In other words, I'm trying to think if I'm in open source, has this contributed to me as an >>open source? Yeah, it's a big and complex question because there's so much research that can happen through a research institution. And those research grants tend to be governed with agreements and some of those agreements have intellectual property rights um front and center and might require things like open source software as a result, the stuff that we're working on clearly isn't that focus area of open source software and and research activities that help kind of propel our understanding forward of what does it mean to do large scale distributed systems creation and then operation. So how do you develop software that does it? How do you how do you run the software that builds these big large distributed systems? So we're focused in that area. Um some of the work that we facilitated through that focus includes integrating non open source software that might be part of um same medical imaging. So for example work we've done with the boston Children's Hospital That isn't 100 doesn't require us to be involved 100 of the open source pieces. All the infrastructure there to support it is. And so we're learning how we can build integrated pipelines for data analysis and image analysis and data sharing across different institutions uh at the open source project level. Well maybe we have a specific imaging program that is not generated from this project. And of course that's okay with >>us. You know chris you bring up a good point with all those conversations. I could see this really connecting the dots. Most computer science programs. Most engineering programs haven't really traditionally focused on it at the scale we're talking about because we look at cloud scale but now scaling with hybrid it's real engineering going on to think about the large scale. We know all the big hyper scale ear's right so it's not just I. T. Provisioning you know network connection and doing some I. T. Work. We're talking about large scale. So I have to ask you as you guys look at these relationships with academics uh academia like like bu and others um how are the students responding to this? Are you guys seeing any specific graduate level advancements? Because you're talking about operational roles that are becoming so important whether it's cyber security and as cloud needed because once more data driven you need to have all this new scale engineered up. That's >>what how >>do you look at that? >>There's two different pieces that I would highlight. One is just the data science itself. So schools still need to produce data scientists. And having data is a big part of being a data scientist and knowing what your what your goals are with that data and then experimenting with different techniques, whether it's algorithms or tools. It's a big part of being a data scientist sort of spelunking through the data. So we're helping produce data. We're looking at data science efforts around data that's used to operationalize infrastructure, which is an interesting data science endeavor by itself. The other piece is really what you highlighted, which is there's an emergence of a skill set in the industry, often referred to as SRE site reliability engineering. Um it is a engineering discipline. And if you back up a little bit and you start thinking about what are the underlying principles behind large scale distributed systems, you get to some information theory and computer science. So this isn't just something that you might think of as um some simple training of a few key tools and knowing how to interpret a dashboard. And you're good to go, this is a much more sophisticated view of what does it mean to really operate large scale infrastructure, which to date, there aren't a lot of these large scale infrastructures available to academics to research because their commercial endeavors >>and their new to me. I was talking to some young folks my son's age and daughters age and I was saying, you know, architect in a building, a skyscraper isn't trivial. You can't just do that overnight. There's a lot of engineering that goes on in that science, but you're bringing kind of operating systems theory, systems thinking to distributed computing. I mean that's combination of a interdisciplinary shift and you got, I won't say civil engineering, but like concept is there, you've got structure, you've got networks, they're changing and then you've got software so again completely new area. >>That's right and there's not a lot of even curriculum that explores this space. So one of the opportunity, there's a great program that really focuses on um that that space of site reliability engineering or operational izing software. Um And then the other piece that I'm I'm really excited about is connecting to open source communities so that as we build software, we have a way to run and operationalize that software that doesn't have to be directly tied to a commercial outlet. So products running in the cloud will have a commercial S. L. A. And commercial agreements between the user and the producer of that service. How do you do that in open source context? How do you leverage a community, bring that community software to a community run service, learn through the running of that service. How to best build architect the service itself and then operationalized with the tooling and automation that service? How do you, how do you bring that into the open source community? And that's something that we've been referring to as the operate first initiative. How do you get the operationalization of software? Really thought of as a primary focal point in the software project where you normally think about the internals of software, the features, the capabilities of functionality, less about the operationalization. So important shift at the open source project level, which is something that I think will really be interesting and we'll see a lot of reaping a lot of rewards. Just an open source communities directly. >>Yeah, speed and durability. Certainly having that reliability is great. You know, I love talking with you guys at red hat because, you know, software, you know, open source and you know, operating systems because as it comes together in this modern era, what a great, great fit, great work you're doing with Boston University's and the mass open cloud initiative. Congratulations on that. I got I got to ask you about this Red Hat Graduate Fellows program you have because this kind of speaks to what you guys are doing, you have this kind of this redhead graduate fellows network and the work that's being done. Does that translate into red hat at all? From an engineering standpoint? How does that, how does that work together? >>Basically, what we do is we support um PhD students, we support post docs. So there's a real direct support to the, you know, that is the Red Jack Graduate Fellow program on our focus there is connecting those um uh academics, the faculty members and the students to our engineers to work together on key research initiatives that we think will help drive open source software agendas forward really broad can be in all different areas from security to virtualization too, the operating systems to cloud distributed systems, uh and one of the things that we've discovered is it creates a great relationship with the university and we find students that will be excited to leave university and come into the the industry workforce and work at Red hat. So there is a direct talent relationship between the work that we do at bu and the talent that we can bring into red hat, which is awesome. Uh We know these people we've worked with well with them, but also we're kind of expanding understanding of open source across, you know, more and more of academia, which I think is really valuable and important for red hat. We just go out to the the industry at large, um, and helping bring a set of skills to the industry that whether they're coming, whether these are students that come into red hat or go elsewhere into the industry, these are important skills to have in the industry. So we look at the, how do you work in open source communities? How to operationalize software at scale? These are important things. They didn't >>expand, expand the territory if you will in terms of systems thinking. We just talked about great collaboration. You guys do a great job chris great to have you on a quick final word from you on this year at red hat summer. I know it's virtual again, which we could be in person, but we're starting to come out of the covid kind of post covid right around the corner. Um, what's the update? How would you describe the current state of red hat? Obviously you guys still got that, that vibe. You still pumping strong a lot going on. What's the current? What's the current, uh, bumper sticker? What's the vibe? >>Well, in many ways, because we're so large and distributed. Um, the last year has been, uh, can't say business as usual because it's been an impact on everybody, but it hasn't required us to fundamentally change. And as we work across open source communities, there's been a lot of continuity that's come through a workforce that's gone completely distributed. People are anxious to get to the next phase, whatever back to normal means. Uh, and people at Red Hat are no different. So we're looking forward to what it can mean to spend time with colleagues in offices, were looking forward to what it means to spend time together with our friends and families and travel and all those things. But from a, from a business point of view, Red Hat's focus on the open hybrid cloud and that distributed view of how we work with open source communities. That's something that's, it's only continued to grow and pick up over the course of the last year. So it's clearly an important area for the industry and we've been busier than ever the last year. So, uh, interesting, interesting times for everybody. >>Well, it's great to see and I love how the culture maintains its its relevance, its coolness intersection between software, Open Source and systems. Great, Great working congratulations chris. Thanks for coming on. >>Thank you. >>All right. I'm John for here with the Cube for Red Hat Summit 2021. Thanks for watching. Mhm.