>> From around the globe, it's theCube with digital coverage of Red Hat Summit 2020, brought to you by Red Hat. >> Welcome back. I'm Stu Miniman, and this is the cubes coverage of Red Hat Summit 2020. Of course, this year's event happening digitally, we're talking to Red Hat executives, partners, customers, where they are around the globe, bringing them remotely into this digital event. And really important topic, of course, has been Automation for a long time, I think back to my career automation is something we've been talking about for decades, but even more important in today's age. Happy to welcome back to the program, Tim Kramer with Red Hat, Vice President of Engineering is that I don't have listed view here. But since we last talked to him at Ansible Fest, has been a little expansion in the scope of what you're working on. First of all, welcome back, and tell us what's new in your world? >> All right, thanks a lot. Yeah, there's been rather substantial change in roles. I'm now in charge actually, of all of the engineering within Red Hat. All the development engineering site includes: the middleware teams, Red Hat Enterprise Linux, of course management and automation, the new team that we just brought over from IBM doing Advanced Container Management. I'm basically running the whole thing and OpenShift of course. >> Excellent. Just a few things to keep you busy. Congratulations on that and love your support in the the Boston "Hello World" rella eight shirt that of course we saw last year at summit. I know one of the things being digital is people do miss some of the t-shirts. I know my family was quite fond of the "May The Fourth Be With You" shirts, that Red Hat did one year at summit. Of course, celebrating Star Wars Day, highly celebrated in in the Miniman household. But Tim, let's talk about Ansible. This brings our audience up to speed, what's happening that some of the latest pieces, and of course, it's been one of the great success stories. Ansible was a lot of adoption before the acquisition, but really accelerated over the last few years? >> At Ansible Fest, we talked a lot about technology to come and showed a few demos of the possibilities. What we have done since then is actually bring all of that technology to life and to expand it. One thing that Red Hat has really done is continue to invest heavily in Ansible, to make sure that we can bring new capabilities and new value to the subscription for everyone. Some of the things that have been happening since summit, which of course we are in, and since Ansible Fest, since we last talked was it, the community continues to scale at a really rapid rate. It's almost hard to keep up. And the number of modules that we have had is grown just tremendously. We have well over 3000 modules now that are available, and as customers and partners and also just casual users are looking through that, it's difficult to figure out: what's really supported? What's really rock solid? What can I count on? And what is, maybe sort of that Wild West community, I'm just trying out some stuff with Ansible and see how it goes. We've been focusing on a lot, is a place that you can come to the Ansible automation platform and the hub where you can now get this content and you can rely on the fact that it's going to be certified by partners, tested by partners, they're always keeping up with the latest updates. A great example of this is, let's just take NetApp or F5, or Cisco as good examples, across the various spaces, we absolutely in the Ansible engineering team are not experts on all of the latest changes, the new hardware coming out, the new software upgrades that they're making. And our ability to keep up with that is pretty difficult. We just can't do it, but they sure can. And their customers, and our customers are both demanding that we give them more content, better content, and we need to be able to do it at the rate that our partners want to be able to provide that kind. As an example, normally we were kind of slowing Ansible down and trying to do one release every six months. But if a new piece of software, a new switch or a new disk array or anything comes out in the meantime, all of our customers had to wait for that next six months release, that was not very convenient. And having an expectation that our partners are going to line up on our schedule is, well, That didn't work out so well for them. We've created the certified content. And we now have the goals to have 50 certified partners. Back at first, I think we had three or four. We're now up to 30, our goal is to hit 50. We had about 100 modules that we showed at fest that were certified, we now have over 1200 modules that are certified content. And these are our partners, creating this content and making it stable and secure for everyone to use. >>So that, I think, by far   >> That was the coolest thing that we've done. >> Yeah, it's great to see that progress. Congratulations on the momentum since Ansible Fest. One of the other things talked about that back at that show, we talked about how analytics and automation, how those are going together, how's adoption been? Is this impossibly met? >> Adoption on the analytic side has been... It's been taking off. It was pretty nascent. I can tell you that, that we've grown by about five X there, but we started a little bit small. We had a few customers that signed up early on to do it. I think probably the more impressive thing is that, we have a couple of customers in markets that you would traditionally think, we're not going to get their data, they're more concerned about what we're sharing, but we have a major bank, we have a major manufacturer that have well over 10,000 systems providing data back into Red Hat that allows us then to analyze and provide a bunch of analytics back on their running estate. And I think that's amazing, seeing the big customers that are coming in from Marcus that you might think, we're probably not going to get a lot of uptake has been really exciting to me. >> All right, you talked a bit about how Ansible fits into the ecosystem, of course being at summit, want to understand a bit more how Ansible the latest of how it's fitting into the rest of the Red Hat portfolio. I've got interviews with Stephanie Shiraz, talking about you, Raul and Joe Fitzgerald, talking about ACM, your group I know is heavily involved working on a lot of those pieces. Help us understand how this is kind of a seamless portfolio. >> I think that's one of the most important things that we do within Red Hat team, is that we have to share the sufficiency across all the product groups and make them better and provide an additional enhanced value there. We've done a lot on the RHEL side, probably one of the maybe lesser known thing is that, we've been working really closely on OpenShift. And actually, we have a lot of customers now that really want the Ansible automation hub available on OpenShift as a first-class application. We're doing things, we're writing operators for those so that we can automate the updates and upgrades and back up and all of that important functionality, so that it's really easy, than to manage your Ansible automation hub, running on OpenShift, that's one big thing. And then we're going to integrate that really well into the advanced container management, that the team from IBM that came over is working towards. I have a really close partnership with ACM team to make sure that we can start to not only gather lists of affected systems, but then take that list and do a bunch of automations against it. >> That's one. On the RHEL side, we've done a lot. We introduced at last summit rally, and we talked about having insights as part of that. Since then, we've been adding more and more capabilities into insights, and to enhance that value of the subscription route. We looked at adding in, well, advisor is now what we used to call insights. It's just something that advises you about problems or issues that may be occurring in your URL instances that are running on prem. We've also added in a drift service, so you can tell if your configurations are sort of drifting apart. We've added in a compliance checker, so you can define some kind of a policy or compliance that you want to enforce on all of your running instances, and we make sure that you're still compliant. We also have a vulnerability detector, which you'd kind of expect, so any nasty security issues that come along, we can pop those up and show you right away. And probably some of the... One of the newer things is, we allow you to do patching. And you can do that patching, right from cloud@redhat.com. We also have another new very exciting feature, which is Subscription Watch, also on cloud@redhat.com. And what this allows you to do is to see and manage all of your subscriptions across your entire hybrid estate. From what you're running on prem, to what you're running in any of the public clouds, we can actually track that for you. You can see what kind of usage you have. And then, make better economic decisions for yourself, and then be able to easily expand that usage if you want to, it used to be a little bit more difficult to do that. We're trying to make subscriptions just like as much in the background as possible to make it easier for our customers. >> Tim, one of one of the big changes customers have to go through is moving from, their environment in their data centers, to the leverage of SaaS and managing things that are outside of their control and the public cloud. You've got an engineering development team, and you've got software that went from, mostly going in customers data centers too, you've got SaaS offerings, you're living in the public cloud. Want to understand, what's changing in your world? What advice would you give to other people as to kind of the learnings that Red Hat has had going through those pieces? >> It's actually a kind of a neat story, because after we change to start making a lot of our services that we had just only shipping products on prem into cloud based services, we had to develop this platform to be able to host all of these services. We started with the insights platform, because we already had that running out in the public cloud. So that was the obvious first thing to base everything on. But we had to build out that platform so that it could support all these services, the ones I just talked about, that are with REL are really good examples. Between a policy, compliance drift, all of these different kinds of services that we're offering, we had to build out that set of capabilities and services in what we're calling sort of the cloud@redhat.com platform. What I'm seeing is that a lot of customers are going through some of these same kinds of thoughts. Like they have a myriad, let's say of applications that are running that they're trying to provide back into their their own company. Different divisions of a company, they have things that are running in the cloud, some things that are running on prem, and they want to start to be able to offer a more cohesive set of services, consolidate some of these, share some of the engineering effort that they have across their various teams. This is exactly the journey that we went through to get to cloud@redhat.com. Finding a surprising number of customers that are actually really interested just in that story, about how we did that. One of the things that we've found is, we've been working with the folks at the open innovation labs within Red Hat. And this is one of the transformation stories that they see constantly as well. We've worked with them and shared this, they're a great resource to help customers kind of think through that problem and get them into a new kind of a platform. But it's quite a journey. We've been really focused on the infrastructure and on prem. Moving to the cloud was a big. But I'll tell you it engineering can move so much faster in a SaaS service than it can with on prem software delivery. It's been remarkable how quickly we could get there. >> Tim, one other thing, if I look at Red Hat, you're a global company, most development organizations are highly distributed to begin with. So many companies today are now having to rapidly figure out how do I manage people that are working from home? How do I live in these environments? From an automation tooling, we'd love to hear any advice you have there, as well as just anything else from your engineering experience in your teams that other people might be able to learn from, as they're dealing with today's landscape. >> To be honest, this is a... We have never seen anything like this in our history, with this kind of pandemic that's happening worldwide. It's shifting everything about business. And it has been challenging just within Red Hat engineering for how we can manage the engineers and their expectations and how difficult it can be to work from home. I have amazing stories from my own engineers. I had an engineer who's in Spain and his wife is a nurse. She's on like 18-hour shifts, the hospital comes back, they have to separate, he's got the kids. And because they don't want them to get infected, it's a really, really difficult working situation for a lot of families out there to try to make it through this. One of the things at Red Hat is, we just have to recognize that it's okay to slow things down a little bit. Let our engineers not feel the pressure that they have to do both childcare and school-at-home and caring for sick relatives or sick family, as well as meet all of your deadlines, it's kind of too much. We've been really... We're trying to be very compassionate with our folks letting them know that we have their back, and it's going to be okay as we try to get ourselves through this ridiculously different time that we've never seen anything like this, like I said. From an engineering perspective, I think work-from-home has been, it's okay for some people. If you have a larger home, I think it's a little easier maybe to find a room that you can go into and do your work. For some, no, if they're in an apartment, or you're sharing with a bunch of friends, it's not your workplace. And it can be really challenging to figure out how to work for eight hours a day with sort of a lot of distractions or just feeling confined and it's just been really difficult for anybody that wants to try to get out, you go a little stir-crazy. The good thing I guess is that engineering is naturally lends itself to being able to be remote and work from home. We have an advantage that way, than other industries, which is great. But it's definitely been really challenging for our teams to be able to cope with this and all we can do is just be really understanding. >> Tim, we appreciate the stories, they're definitely everyone's working through some challenging times. Want to give you the final word as to really takeaways as to what should people be watching? What things should people be going back and looking at from an automation standpoint as they leave Red Hat Summit 2020? >> We're just going to continue to work with the community, work with our partners, get more certified content and continue to scale, the best way that we can for all of our users and our customers. That is the key focus. We want to continue automating and providing all of that flexibility. If you want all 4000 modules and a big download, we certainly are... We're going to continue to give you that option. But if you want to be able to start customizing what you download, maybe only relying on certified content, instead of community content, we're going to give you that option now as well, so that you know what you're running. And with the analytics, we're just scratching the surface here. We're getting some great data. It's helping us to develop new ways of insights into how your systems are running. And that'll get very exciting as we go forward. I know that we've seen like a Forex increase already in the amount of insights attached to REL, which is really great, and for now, at least in the hundreds of customers that are using the AI, I think as we show more value there, you'll get a lot more customers to provide some of their data which will allow us then collectively to come up with some really great analytics to help people become more efficient with your automation. >> Well, Tim Kramer, thank you so much for the updates. And thank you to everything your team's doing. And just a reminder to the audience, of course, these communities not only are important technical resources, but many of them you've made friends with over the years. If you need help, reach out to the community. There are so many good stories that can be found amongst these communities helping each other through these challenging times. Much more coverage from Red Hat Summit 2020. I'm Stu Miniman, and thank you as always for watching theCube. (gentle upbeat music)

>> From around the globe, it's The Cube, with digital coverage of Red Hat Summit 2020, brought to you by Red Hat. >> Hi, and welcome back, I'm Stu Miniman, this is The Cube's coverage of the Red Hat 2020, bringing you guests from Red Hat and their partner ecosystem, practitioners, where they are around the globe, bringing to them this digital event, and while we wish we could all be together in person, we'll just be together apart for 2020. Happy to welcome to the program, a longtime Red Hatter, but first time, on The Cube, Rich Sharples, who's the senior director of product management inside Red Hat, Rich, thank you so much for joining us. >> Yeah, thanks for the invitation, great to be here. >> All right, so the topic we're going to talk about today is something you've got a long background of the middleware space. But in, Quarkus so, I personally was not familiar with Quarkus. Obviously we know, god, I believe someone told me once that there's like, 2 million open source projects out there, so I believe I can be forgiven for not having every one of them memorized there, but of course anybody in our community is going to know Java. What a huge impact that has had on the industry. Linux and Java are two of the, you know, major movers of how we, you know, build an, you know, deal with application today, so give us a little bit of a framework as to what Quarkus is, you know, why it was created. >> Yeah, so it's no secret that as organizations and developers move to this kind of new styled cloud native development, developing applications running in containers or in a kind of serverless environment that Java is not necessarily the best fit. Java does many incredible things, it's an amazing field of engineering. But many of the coolest things it does, assumes that it's going to be a long running application, it can do this cool dynamic class loading and dynamic optimization as the application runs. Those things are pretty impressive, but they're also fairly, very heavyweight. And in our kind of ephemeral environments, whether containers or functions of service, you don't have long running applications. And you can't make use of those things, so in a Java environment you pay for those radical features that you don't necessarily get any benefit from them. So, you know, where we're really trying to lay focus is ensure developers to continue to use Quarkus, it's still the, you know, the dominant language for enterprise development. You still get the benefits of these new architectures, so ensuring that Java continues to be you know, performant and efficient in these new you know, constrained environments. >> Okay, excellent, so we're not calling it cloud native Java though, right Rich? But we are bringing, if I heard right, Java for things like containers Kubernetes, I even heard functions as a service so, we're talking to server lists of you know, open shift server lists something that's being talked about this week. So help us understand you know, if Java was long in the tooth. You know, what stays the same, what's different, how have people been managing and you know building applications in this environment, because obviously you know, we've been dealing with containers for a number of years now, so what have they been doing so far and, you know, why is Quarkus different from some of the alternatives that are out there. >> Really, the goal is to introduce those that stayed the same. It's not a different language, it's not a fork. It is Java, you're writing Java applications, essentially in the same way you used to write them. And you may be using Microsoft still functions so slight difference in terms of design, but it's, you know, we want to ensure that you can bring your favorite frameworks and wipers with you as well. When you're accessing databases or message brokers. We want to ensure you can still use those technologies so we're trying to bring the whole ecosystem with us, with Quarkus, so those things can run well, in a you know, container or service environment as well. And that's super important because the real benefit here is any organizations face the choice of I want to develop cloud native, I want to develop functions, but I've got this huge investment in Java in terms of skills and you know, tools and tool trains and I don't want to go learn a new language, just because I need to you know, take advantage of things new environments so we're essentially giving developers their cake and allowing them to eat it. We are trying to provide the best of both worlds. Stick with the language you already know and you know, have lots of experience with, and still be able to get the benefits of running in our containerized environment. >> Okay. what are some of the challenges here, so you know from an infrastructure standpoint. My background is, you know, virtualization broke a lot of pieces and containerization does the same thing. As you mentioned, things you know, spin up really fast and they don't stay on nearly as long. You know, god, you mentioned functions as a service, often we're measuring things in milliseconds, so everything genomes, understand what's up how do I manage it, how do I monitor it all of those pieces so, you know, I understand you're saying we take the skill set and what we know. But, you know, there's got to be some on ramp here and some considerations >> Yes, so, yeah, absolutely so, Red has taken on the ramp and ensuring that this ecosystem moves with us. We do a lot of hard work within Quarkus, so developers don't have to. We do some very, very clever stuff that very few organizations, would be able to do because they don't have the depth of knowledge of the Java virtual machine that we do. We're able to take a lot of things that you'd normally start off once only, like loading classes and you know, building kind of memory data around, all the kind of reading configurations all of the things applications do once and only once. Why do it another time? Why not build that into the component time, you're going to do it once but take it out of your runtime environment completely, so there are many ways where we're having to kind of rethink the way you know, applications run. We have to do a reset on what job was built for this environment of long running applications where, if the application took 10 minutes to load up all the stage area and classes and config, it didn't really matter, because it's not going to run for 36 months. You got to do a resale on those design decisions and think very very differently and given with our deep experience with containers and you know, working on things like native, serverless and on deep, deep roots in Java, we were able to do that and really think differently. So, Quarkus takes a lot of that kind of work away from developers they don't have to think too much about it. And by and large, what they can do is focus on their applications and their micro services and read all of that wiring and optimization for them. And hopefully deliver some you know, real significant improvements both in development productivity, but also the kind of runtime resource utilization as well to really lower costs. >> Okay, and Rich, what's is great that's been really the nirvana when you talk about developers is they don't want to have to think about some of that underlying you know, gobbledygook. That was why you know, the term serverless is so polarizing is because from a developer standpoint I don't think about this but everybody screams, but there are servers and there is networking and there's you know, things underneath that I need to think about. So, what is the underlying assumption here. We talked about you know, containers, Kubernetes, functions as a service, what integration is done there? Does this live across? Is it kind of like, you know, does it sit just just on RHEL and therefore everywhere the RHEL lives it's there? Or, help me understand kind of what that underlying you know, substrate is. >> Yeah, right now our focus is RHEL x86, 'cause that's kind of the dominant platform in a cloud. It is just Java, some have that natural kind of portability and you know, as other architectures become important, we can certainly look at those as well. The reason why the underlying machine architecture is important, is because one of the options you have with Quarkus is actually the ability to compile everything down to a binary executable, right? That may give you some additional footprint reduction and performance enhancements. And also if we compile down to native, we do need to think about the underlying operating system and the architecture. But by and large, as a developer you really don't have to care. Just like to you don't have to care with Java today. You also have the option with Quarkus, to run on conventional JVM, open JDK is our preference and if you can run on open JDK, then you can pretty much run anywhere. Under you know, different reasons for compiling down a native, this is running on a traditional JDK, different optimizations, different trade-offs that you'd like to make. >> All right, so Rich, an open source project here, can you tell us a little bit about you know, who's contributed to this, you know, what general adoption is this, and, you know, where are we with the solution today. Is it today ready for production environments? >> Yeah, it's getting close to production ready, yeah, we'll be making this Germany available and during Summit and many of the components we use are tried and tested, again we're not reinventing everything from the ground up. We leverage things like REHL VM, we leverage open JDK, we leverage all our frameworks and library, the developer that are familiar with, we just have to optimize them for Quarkus, so, yeah, much of this is not brand new technology. The existing technology that has that kind of maturity and tolling support. So yeah, we're confident it's production ready. One of the early stages of the development of Quarkus, was to use some of Red Hats own products as goody picks. Actually, you know, optimize those products for containerized environments by rebuilding them on top of Quarkus and that gave us obviously a lot of insight into the general readiness, yeah, the whole kind of eating around and dog food principle. In terms of the organizations in investing Quarkus, you know, we have this kind of have old addedge, we often use at Red Hat, which is you know, if you want to, if you want to move quickly, go alone. If you want to go far, then go with others. We're at a stage, where we've been developing Quarkus very, very rapidly and that's mostly been a Red Hat effort. We've certainly got some help from the mothership IBM and I expect that to be an increase overtime and we're now in a point where we have a Germany available product coming up and we're ready to really kind of expand the ecosystem. So, we're looking for you, whether you're a framework provider, you've written a framework for Java and you want to have that Quarkus provider, ensure that runs really well and partly the kind of growing ecosystem around Quarkus, we're looking for that, we're for, you know, cloud providers to you know, take this technology and see how it runs in other environments and give us feedback. So, yeah, definitely looking to expand that ecosystem of contributors, so we can really turn this into kind of the facto technology for the cloud. >> So, Richard, stop back for us for a second, you've got a long history with Java. You know, why in 2020 is you know, Java still, I believe it's like number two on the language list there. Why is it so important today and why is moving forward to all of these cloud solutions so important for that ecosystem. >> Yeah, I think it comes down to you know, organizations are faced with a tough choice. That they stick with the language that they know and love, which is Java, the language, the relevant applications for the last decade and not be able to take the best advantage of cloud and native or serverless environment. Whereas if they go and learn a new language, Datalog or No.js and you know, kind of hunt around and trying to see if that has the same kind of ecosystem and support. So, we want give organizations a better choice, which is you can stick with a language you already know and love and you have skills and the resources, yeah, you can still take advantage of these new environments and that's you know, I'm mean, fundaments the problem we're trying to solve for your customers. That twice open source projects are, they live or die, depending on, they really do scratch an itch, you know, fulfill a need with real developments. I'm going to think we've certainly from the adoption and interest we've seen with Quarkus, we really do think we've found a very real problem to solve. >> Yeah, Rich, before we wrap up, I just want to give you the opportunity, you know, how is your teams doing, I think you know, Red Hat's making a real concerted effort to make you know, an appropriate tone for the event this week. Trying to make sure it's not you know, some of the usual glam that we normally expect to see, full on the community all together, but, you know, the community is so important and you know, the network of people that, you know, built not only you know, technologies but also careers and you know, relationships, so, give us a insight as to how your teams doing, everybody in these challenging times. >> I think this is another good example of where open source really does show it's resilience. Open source projects are simply very, very distributed. No open source projects rely on an office being open, so your word distributed team all used to work using distributed tools across the world, different time zones. It's kind of natural for us, so we're kind of plugging on, you know, just as we have them in the task, you have a few more dogs in the background and crying babies and you know, we're all humans, we all tolerate that. We have great support from our leaderships, that's Red Hat and IMB. They're very clear that they've got people and families before revenue and that's good to know. Everybody's you know continuing as they can to you know, ensure that we have you know, great technology out there 'cause like I said there's real demand here that needs to filled and we're going to continue doing that. So, yeah, everybody's kind of holding up pretty well, so, let's just see how long this thing goes but again, I do think it is a valuable kind of lesson on the resilience of distributed teams and open source in particular. So, yeah. >> All right, well thank you for that Rich. Just to bring it on home, as you said, the general availability of Quarkus you know, is in front of us here, really expecting the ecosystem in costumers move. Give us a little bit of what we should be looking at going forward, what are some of the kind of maturity steps and what should we expect to see, through the remainder of 2020. >> Yeah, it's going to be a pretty exciting year, I mean, given the changes we were all going through we are going to try and come meet developers, where they are, which is you know, on their laptops and in front of their computers, so, we're going to do, we're playing through a bunch of you know, kind of very quick webinars, you know, quick bye what it takes, you know, interesting features, we're going to do some virtual hackathons as well, so you can actually get people with time and talk with some experts. We have platform for doing that. So, we're pretty excited, we, you know, again with the incident, we can reach a lot of developers very easily. Actually far more than we could at a live even like Summit, so, we're going to make the best of it and try to get at to as many developers as we can with Quarkus and you know, hopefully they'll repay us by investing a little bit of time into it and giving us some feedback and you know, trying some applications and you know, see how it goes. >> All right and you know, final, final question for your Rich, you know, Quarkus, I have to imagine that the Quark, the subatomic particle, you know, came into the naming there. Is there some connection with that? I guess why the name to the project? >> Yeah, I mean that's pretty much it, you know, the Quarkus you know, kind of. (mumbles) Arguably the smallest fundamental particle. >> And can we find something smaller? >> Well, there potentially is something smaller but that's kind of in the realm of quantum mechanics and physics, which I'm not an expert on, so, but yeah, it's meant to mean small and the us bit, the US bit. I'd like to think there was a really good big meaning around that. The meaning is that we understand, that trying to do any kind of brand leadership or trademark protection on a well know server like Quark, is it possible? So, we had to add something to Quark and Quarkus kind of sounded cool. >> All right, Rich Sharples, pleasure to catch up with you, congrats on the progress for Quarkus, definitely looking forward to watching it's progression in the future. >> Thanks, great talking to you. >> All right, I'm Stu Minneman. Lot's more coverage here at Red Hat Summit 2020. Thank you as always for watching The Cube. (gentle music)

from around the globe it's the cube with digital coverage of Red Hat summit 2020 brought to you by Red Hat welcome back this is the cubes coverage of Red Hat summit 2020 of course the event happening digitally we're bringing in the guests from where they are around the globe happy to welcome back to the program and he's one of the keynotes because he's also many times cube alumni chris wright is the senior vice president and chief technology officer at Red Hat chris it is great to see you and we've got almost matching hats you have a real red hat fedora I've got one that the you know kubernetes Red Hat team OpenShift team gives out in Europe so in case anybody in the Red Hat community goes yes I've been a longtime member of the community I got you know I think my original Red Hat baseball cap probably 15 years ago but the Hat that I had is not one of the nice felt one it is they're pretty good to see here all right so we've gotta wait a little bit to get your keynote but so many topics I want to get to with you but you know of course as I mentioned me open and it's pretty obvious everyone's remote right now is kind of you know special times we are living in so bring us inside a little bit you know your your organization your group or community you know what what this means and how's everybody doing well I mean it'd be hard not to sort of acknowledge that there's a major global event happening right now and and kovetz really changing how we operate how we work from a RedHat perspective our number one priority is just employee safety and employ health and so we we were quick to send our folks home and have everybody to work from home and so what's interesting from a RedHat point of view I think and then even if you broaden that out to open-source communities the the distributed nature of open-source development and and specifically the engineering teams Red Hatter are pretty distributed kind of mirroring those open-source communities that we participate in so in the one hand you can kind of say well things haven't changed substantially in the sense of how do we how do we operate in upstream communities but on the other hand people working from home is it's a whole new set of challenges I mean my kids are 12 and 14 but you know say you have toddlers that's a real distraction or you have a working environment at home that's crowded with multiple people I mean it can really change how you approach your daily your your your daily work life um so creating that balance has been really important and for our teams we talk a lot about just think empathy think about how you're supporting one another and again when you broaden that out to the larger communities I think probably a really important aspect of open-source development is crossing corporate boundaries and being inclusive of such a broad set of contributors that there's a built-in resiliency associated with open source communities which i think is fantastic and then when you add to that sort of the the enthusiasm around just doing great things there's a lot of interesting activities that are collaborative in nature that are community based that are trying to address the Kovach crisis whether it's 3d printing of supplies or whether it's contact tracing applications that help people understand where they become across kovat or anything like that I mean a lot of cool stuff happening that's inspired by a real challenge to the entire globe yeah okay Chris one of my favorite things the last few years that summit has you know talk and he's cut talking to companies that are going through their journey of you know what we usually call digital transformation what we have always said from the research side is what separates you know people that have successfully gone through this is that data and they become data-driven and data is such an important piece of what they're doing well I think everyone has been getting a real crash course on data because not only businesses but you know governments and you know the entire globe now is you know watching the daily data trying to understand data sources you know bring us inside is to you know really the importance of data and you know where that intersects with everything that red hat is well the those are great examples I mean it's sometimes a little depressing but the the notion that data is a critical part of decision-making and access to quality data in real time is what helps us make better decisions more effective decisions and more efficient decisions and so when you when you look at the amount of data being produced it just keeps growing you know it's sort of on the exponential growth curve and when you look at the commensurate amount of compute power associated with all of that data it's also growing which is maybe an obvious statement what it says is we are gathering more and more data and the degree to which we can pull meaningful insights out of that data is really how much we can impact our companies you know value and differentiation and in the context of something like Cova that means vaccine discoveries and you know shortening times to field trials in in a more business context it's talking about how quickly you can respond to your customers needs and we see a really dynamic shift and the work force all working from home that puts a real strain on the infrastructure we're here supporting infrastructure builders and the amount of data that they can collect to efficiently operate infrastructure is critical at a time when people are distributed and getting access into the lab environments is challenging and so it you know I think there's a lot to be said for the amount of data that's being produced and then how we analyze it we think of it in terms of bringing data to applications and historically they kind of lived in separate I'd call them silos bringing the data sources and data processing and model development all onto a common platform is a really powerful thing that's happening in the industry today which is which is exciting so you know we were bringing data to be a central actors how I like to describe it yeah well look I'm really glad how you connected that discussion of data to the applications we as you know my background really is on the infrastructure side and the concern I have a lot of times as infrastructure people you know we talk about the bits and bytes we talk about the infrastructure but the only reason we have infrastructure is to run those applications and you know deal with that data it was hoping you can connect the dots for us the key note that all gave one of the main things he's talking about it where's the open hybrid cloud and I had a great discussion with him on the cube so with that setup of applications and data you know how does that intersect you know with what Red Hat calls the open hybrid cloud and what differentiates Red Hat's position there from some of the other discussions that we hear in the industry about cloud whether the open hybrid cloud is is a platform I think that's the best way to think of it and that platform it's a it's a platform that spans different types of infrastructures so that's public clouds that's on-premises data centers you know the enterprise zones themselves and I think important increasingly out to the edge so the notion of where you deploy isn't also coupled to what platform do I have to develop to in order to do that deployment and you know when we talk about the edge extending out to the edge that means you're getting closer to those data sources so bringing the data in doing the Associated inference and making decisions close to that data where latency really can matter is a big part of what that open hybrid cloud platform brings to to the market or to our customers and when you think about an application developer typically an application developer is trying to in a you know enable some some behavior or feature or functionality and the more we can drive use data to drive the behavior or drive the functionality the more personalized and application is the more intelligent the application is and so the connection between data the data sources the data processing the data science behind data cleansing and model generation and the associated models that can be easily accessed by applications that's the real power that's the real value that works to help develop for our customers so they can change their business we actually do this internally it's how we operate you know we collect data we use data to make decisions we use data in our product release process and the platform that we've created is a data processing and analytics and machine learning platform that we use internally and we also make that externally available as an open source project the open data hub so open and data and hybrid cloud are all intertwined at this point yeah one of the things that really has been highlighted to me at Summit this year is that connection you know we always knew Red Hat had you know strong developer community out there but you know you think back to Linux Linux has eyes directly into the application you look across the portfolio and it's not the app dev team over here and the infrastructure team over here and you know how do we operate all of these various pieces you know ansible you know has connections into all the various roles so what want you to just comment you know with kind of your you know CTO role and you you look over the entire portfolio but that discussion of you know how roles are changing how organization and make sure that they're not a bunch of various functions that aren't in sync but you know we're really coming together to help respond to the business needs and move forward in the speed that is needed in today's world well I think the the early stages of that were well captured with the DevOps phrase so bringing developers and operations closer together it's not always clear what that means and in some cases that the the notion of a of a platform and the notion of operating an application and then who operates the platform I think there there's been some question in the industry about exactly what that means we're thinking of it today to sort of stick with the buzzwords in the dev sac ops context and even what I would call AI dead set cops so in data and intelligence infused obses cops and the idea is developers are just trying to move rapidly so the degree to which the underlying infrastructure is just there to support application development is the operations teams need yeah that's what the operation seems trying to provide developers need at the same time access to tooling to consistency from test environments through to production environments and also access to those data models that I was talking about earlier so bringing that all together I think on the DevOps side or the dev Sackhoff side it's how can you build a platform that gives the right business specific guidelines and sort of guardrails that allow developers to move as quickly as possible without getting themselves into trouble and you know inadvertently creating a security vulnerability by pulling in an old dependency as a concrete example so bringing these things together I think is what's really important and it's a big part of what we're focused on the so operational side being infused with intelligence that's data in telemetry you're gathering from at the platform level and using models to inform how you operate the system and then if you go up a level to the application development sort of CIC deep pipeline where can you make intelligent recommendations to developers as they're pulling in dependencies or even writing code and then give easy access to the data science workflow to intercept so that what you're delivering is a well integrated model with an application that you know has a lifecycle and a maintenance that is well understood yeah so so Chris you know we've watched this is the seventh year we've had the cubit at Red Hat summit of course Red Hat itself has a large portfolio but not only Red Hat but you know the open source communities there are so many you know countless projects out there and you have a huge partner ecosystem you were just talking a bunch about DevOps you know I've got sitting at my desk you know one of those charts that shows you know DevOps tooling and it here's some of the platforms and here's all the various pieces and it's like you know I think there's only you know 50 or 80 different rules on that but how's Red Hat and the community overall how are you helping customers you know deal with this you know challeng world is you know we've got the paradox in place out there on it you know we understand that you know everybody's needs something a little bit different but how are we helping to give a little bit of structure and guidance in the the ever-changing world well I think it's one of the values of pulling content together if you think of a set of components being brought together as curation then we're helping curate the content and assembling pieces together it turns out is a is a lot of work especially when you want a lifecycle manage those components together so one basic thing that we're doing is bringing together an entire distribution of content so it's not just a single it's not just Linux it's not just kubernetes it's Linux and kubernetes engineered together with a set of supporting tooling for logging and monitoring and CI pipelines and all of that we bring together in a context that we opinionated or prescriptive what we also focus on is understanding that every Enterprise has a as its own legacy and history and set of investments that they've made so that process where we bring together an opinionated stack also needs to incorporate the flexibility so where can we plug in a CI pipeline that your your enterprise already has or where can we plug in your monitoring logging tools so that kind of flexibility allows us to bring together some best-of-breed components that we're finding in the open-source communities with flexibility to bring a whole set of ecosystem partners and if we go back to that open data have conversation there are a lot of data centric tools that we put in the open data have open source project we have commercial partners that can support things like say spark as a concrete example or tensorflow and so you know combine those those are open source projects but they're not coming from Red Hat they're coming from our ecosystem partners combine that all together into something that's engineered to work together and you're taking a lot of the friction out of the system so that developers can just move quickly all right so Chris give us a little bit of preview what what are people gonna see in the keynote and you know there's some people that are going to be watching this interview live but others will be efforts though I believe edge is one of the pieces we'll be touching on in the keynote but give us a little bit of what will we can expect well whatever you'll have to come to the keynote to really get the full full experience but what we're trying to to talk through is how data is really fundamentally changing business and if and we talk through that that's sort of story line starting with how it impacts red hats but you know at one level we're an enterprise we have our own business needs we use data to drive how we operate we also see that the platforms that we're building are really helpful for our customers to harness the value of data and change their own business and in the context of doing that we get to take a look at some ways where those business changes have industry-wide effects you know that we talk about things like 5g and artificial intelligence and where these things come together especially in edge computing really interesting space for these things all kind of converge and you know so kind of that that broad broad story line of data something that we use to change how we operate something that we build is from a platform point of view of our customers change how they operate and ultimately those changes have major impacts across the industry which is was which is pretty exciting pretty cool yeah I'm curious Chris you know I think back a few years ago I would have been interviewing you about like NFB and many of the themes it feels like we were talking about there we're really setting the table for the discussion we've been having for 5b is is that you know do you agree with that you know what would what's kind of the same and different from what we might have been looking at five years ago this it's very much and I love that question because it touches on something I think is really important it's very much an evolution and so in the tech world we talked so much about disruption and I think we overplay disruption I think what's interesting is technology evolution just consistently changing and moving forward gives rise at points in time to really interesting convergence of change that can be disruptive so as a concrete example NFV historically was about really improving the operational efficiencies of the service providers building networks and helping them move more rapidly so they could introduce new services most of that was focused on 4G most of that was focused on the core of the network today we're introducing 5g across the industry the discussions are moving technology wise into where do containers fit into this new world and the discussion at the network level is not only in the core but all the way out to the edge and then when you look at the edge where you have a portion of the network operating as software you have a platform like open ship that can also host enterprise or consumer facing education so this is really all of those early stages of NFV are culminating in this in a place today where the technology supports total software infrastructure for the network and utilizing that same cloud that you're running using to run the network to power enterprise or consumer facing applications that's pretty far away from where we were in the early days of NFB very much in evolution and then if you take it one step further and say orgy smart devices and cloud computing gave rise to a set of disruptive businesses ten years ago those businesses did not exist today we can't imagine life without them 5g device proliferations and not just smartphones but a whole set of new devices and edge computing are the ingredients that give rise to that same next wave of innovation where 10 years from now we can't really imagine what are the businesses that in 10 years we won't be able to imagine our lives without so we're at a really interesting inflection point and it's it's partially through this evolution of technology I think it's really exciting all right Chris last question for you there's always so many different pieces going on you know red hats really striking a nice balance there's not really as much of the habla and announcements but you know so much you know everything that does is built on open source so you know there's always things I run across it's like oh I need to you know look down the rabbit hole a little bit and what was that Farkas thing I think I'd heard that word before where all of the projects at the CN CF where you know Red Hat's involved in so you know in the last minute he or give us you know any areas where people said hey you know go google this go look up this you know project other cool things that you know you and your team are working on that you want to make sure to highlight well you you've mentioned one which is Korkis and not often time we talk about infrastructure I think it's a really cool project that is developer focus it's it's in the Java space and it's really bringing Java from an enterprise development platform into a modern language that can be used to build cloud native applications or even serverless functions I think serverless is a critical space so we've been talking for quite some time about all the ways serverless can be impactful we're in a place now where K native as a project is maturing and the the kind of world around it is getting more sophisticated so we have a serverless offer and as part of part of the open shift platform so you know making sure you're paying attention to what's happening in the K native space I think is is really important there's a whole new set of management challenges that will be in the security and a multi cluster space we're bringing those we're bringing technology to bear in this space and as RedHat we will bring those out as open source projects so looking for the open source communities around where you hear things like ECM or advanced container management or multi cluster managed environments which are the norm at this point you know those are some examples of things I think are important and then there's a world of stuff that's data focused there's all of the data science tools you know too many to really enumerate but that I think is an example where open-source is leading the space leading the industry in terms of where all where all those tools are developed and how the coverage and access developers have to data science tools all right well thank you so much Chris right always a pleasure to catch up with you and definitely looking forward to your your you know alright thank you all right lots more coverage check out the cube dotnet you can see all the interviews after they've gone out live they will be on demand all those projects Chris mentioned I've had deep dives on all of them so also hit up Chris square myself on Twitter if you have any follow up always love to hear the feedback I'm Stu minimun and as always thank you for watching the cube [Music]

>> From around the globe, it's the CUBE with digital coverage of Red Hat Summit 2020 brought to you by Red Hat. >> Hi, I'm Stu Miniman, and this is the CUBE's coverage of a Red Hat Summit 2020 happening digitally. We're connecting with Red Hat executives, thought leaders, practitioners, wherever they are around the globe, bringing them remotely into this online event. Happy to welcome back to the program, Joe Fernandez, who's the Vice President and General Manager, of Core Cloud Platforms with Red Hat. Joe, thanks so much for joining us. >> Yeah, thanks for having me. Glad to be here. >> All right, so, Joe, you know, Cloud, of course, has been a conversation we've been having for a lot of years. When I went to Red Hat Summit last year, when I went to IBM, I think last year, there was discussion of moving from kind of chapter one, if you will, to chapter two. Some of the labels that we put on things back in the early days, like Hybrid Cloud and Multicloud, they're coming into a little bit clearer picture. So, let's just give a high level, what you're seeing from your customers when they talk about Hybrid and Multicloud environment? What does that mean to your customers? And therefore, how is Red Hat meeting them where they are? >> Yeah, sure. So, Red Hat obviously, serves an enterprise customer base. And what we've seen in that customer base, really since the start and it's really informed our strategy, is the fact that all their applications aren't going to run in one place, right? So they're really employing a hybrid class strategy, a Hybrid and Multicloud strategy, that spans from their data centers out to a public cloud, typically then out to multiple public clouds as their cloud investments grow, as they move more applications. And now, even out to the edge for many of those customers. So that's the newest footprint that we're getting asked about. So really we think of that as the open hybrid cloud. And you know, our goal is really to provide a consistent platform for applications regardless of where they run across all those environments. >> Yeah. Let's get down a second on that because we've had consistency for quite a while. You look at the largest cloud provider out there, they said, hybrid environment, will give you the exact same hardware that we're running in the public cloud of your bet. You know, that in your environment. Of course, Red Hat's a software company. You've lived across lots of platforms. We're going to Red Hat's entire existence. So, you know, where is that consistency needed? How do you, well, think about how Red Hat does things? Maybe the same and a little different than some of the other players that are then, positioning and even repositioning their hybrid story over the last year or so. >> Yeah. So, we're really excited to see a lot of folks in the industry, including all the major public cloud providers are now talking about Hybrid and talking about these types of initiatives that we've been talking about for quite some time. But yeah, it's a little bit different when we talk about Hybrid Cloud, when we talk about Multicloud, we're talking about being able to run not just in one public cloud and then in a non-premise clients that mirrors that cloud. We're really talking about being able to run across multiple clouds. So having that consistency across, running in, say Amazon to Azure to Google, and then carrying that into your on-premise environments, whether that's on Bare Metal, on VMware, on OpenStack, and then, like I said, out out to the edge, right? So that consistency is important for people who are concerned about how their applications are going to operate in these different environments. Because otherwise, they'd have to manage those differences themselves. I'm speaking as part of Red Hat, right? This is what the company was built on, right? In 20 years ago, it was all about Linux bringing consistency for enterprise applications running across x86 hardware, right? So regardless of who your OEM vendor was, as long as you're building to the x86 standard and leveraging Linux as a base, Red Hat Enterprise Linux became that same consistent operating environment for applications, which is important for our software vendors, but also more importantly for customers themselves as they yep those apps into production. >> Yeah, I guess, you know, last question I have for kind of just the landscape out there. We've been talking for a number of years. When you talk to practitioners, they don't get caught up in the labels that we use in the industry. Do they have a cloud strategy? Yes, most companies have a cloud strategy, and if you ask them is their cloud strategy same today, as it was a quarter ago or a year ago, they say, of course not. Everything's changed. We know in today's day and age, what I was doing a month ago is probably very different from what I am doing today. So, I know you've got a survey that was done of enterprise users. I saw it when it came out a month ago. And, you know, some good data in there. So, you know, where are we? And what data do you have to share with us on kind of the customer adoption with (mumbles). >> Yeah, so I think, you know, we put out a survey not too long ago and we started as, I think, over 60% of customers were adopting a hybrid cloud strategy exactly as I described. Thinking about their applications in terms of, in an environment that spans multiple cloud infrastructures, as well as on-premise footprints. And then, you know, going beyond that, we think that number will grow based on what we saw in that survey. That just mirrors the conversations that I've had with customers, that many of us here at Red Hat have been having with those same customers over the years. Because everybody's in a different spot in terms of their transformation efforts, in terms of their adoption of cloud technologies and what it means for their business. So we need to meet customers where they're at, understand that everybody's at a different spot and then make sure that we can help them make that transition. And it's really an evolution, as opposed to , I think, some people in the past might've thought of as a revolution where all the data centers are going to shut down and everything's going to move all at once. And so helping customers evolve. And that transition is really what Red Hat is all about. >> Yeah. And, so often, Joe, when I talk to some of the vendors out there, when you talk about Hybrid, you talk about Multicloud, it's talking about something you mentioned, it's a box, it's a place, it's, you know, the infrastructure discussion. But when I've been having conversations with a lot of your peers of these interviews for Red Hat Summit. We know that, it's the organization and it's the applications that are hugely important as these changes go and happen. So talk a little bit about that. What's happening to the organization? How are you helping the infrastructure team keep up and the app dev team move forward? >> Yeah, so first, I'll start with, that on the technology side, right? One of the things that that has enabled this type of consistency and portability has been sort of the advent of Linux containers as a standard packaging format that can span across all these different (mumbles), right? So we know that Linux runs in all these different footprints and Linux containers, as a portable packaging format, enables that. And then Kubernetes enables customers to orchestrate containers at scale. So that's really what OpenShift is focused on, is delivering an enterprise Kubernetes platform. Again, spanning all these environments that leverages container-based packaging, provides enterprise Kubernetes orchestration and management, to manage in all those environments. What that then also does on the people front is bring infrastructure and operations teams together, right? Because Kubernetes containers represents the agility for both sides, right? Or application developers, it represents the ability to pay their application and all their dependencies. And know that when they run it in one environment, it will be consistent with how it runs in other environments. So eliminating that problem of, works on my machine, but it doesn't work, you know, in prod or what have you. So it brings consistency for developers. Infrastructure teams, it gives them the ability to basically make decisions around where the best places to run these applications without having to think about that from a technology perspective, but really from things that should matter more, like cost and convenience to customers and performance and so forth. So, I think we see those teams coming together. That being said, it is an evolution in people and process and culture. So we've done a lot of work. We launched a global transformation office. We had previously launched a Red Hat open innovation labs and have done a lot of work with our consulting services and our partners as well, to help with, sort of, people in process evolutions that need to occur to adopt these types of technologies as well as, to move towards a more cloud native approach. >> All right. So Joe, what one of the announcements that made it the show, it is talking about how OpenShift is working with virtualization. So, I think back to the earliest container days, there was a discussion of, "oh, you know, Docker and containers, "it kills VM." Or you know, Cloud of course. Some Cloud services run on VMs, other run on containers, they're serverless. So there's a lot of confusion out there as to. >> Yep. >> What happened, we know in IT, no technology ever dies, everything's always additive. It's figuring out the right solutions and the right bet. So, help us understand what Red Hat is doing when it comes to virtualization in OpenShift and Kubernetes and, how is your approach different than some of what we've already seen in the marketplace? >> Yeah, so definitely we've seen just explosive adoption of containers technology, right? Which has driven the OpenShift business and Red Hat's business overall. So, we expect that to continue, right? More applications moving towards that container-based, packaging and deployment model and leveraging Kubernetes and OpenShift to manage those environments. That being said, as you mentioned, virtualization has been around for a really long time, right? And, predominantly, most applications, today, are running virtualized. And so some of them have made the transition to containers or were built a container native from the start. But many more are still running in VM based environments and may never make that switch. So, what we were looking at is, how do we manage this sort of hybrid environment from the application perspective where you have some applications running in containers, other applications running in VMs? We have platforms like Red Hat, OpenStack, Red Hat Virtualization that leveraged the KVM hypervisor and Red Hat Enterprise Linux to serve apps running in a VM based environment. What we did with Kubernetes is, instead, how could we innovate to have convergence on the orchestration and management fund? And we leveraged the fact that, KVM, you know, a chosen hypervisor, is actually a Linux process that can itself be containerized. And so by running the hypervisor in a container, we can then span VMs that could be managed on that same platform as the containers run. So what you have in OpenShift Virtualization is the ability to use Kubernetes to manage containerized workloads, as well as, standard VM based workloads. And these are full VMs. These aren't micro VMs or, you know, things like Firecracker Kata Container. These are standard VMs that could be, well, Windows guests or Linux guests, running inside those VMs. And so it helps you basically, manage that type of environment where you may be moving to containers and more cloud native approach, but those containers need to interact or work with applications that are still in a VM based deployment environment. And we think it's really exciting, we've demoed it at the last Red Hat Summit. We're going to talk about it even more here, in terms of how we're going to bring those products to market and enable customers. >> Okay, yeah, Joe, let me make sure I understand this because as you said, it is a different approach. So, number one, if I'm moving towards a (mumbles) management solution, this is going to fit natively into what I'm doing. It's not taking some of my traditional management tools and saying, "oh, I also get some visibility containers." There's more, you know, here's my Kubernetes solution. And just some of those containers happen to be virtualized. Did I get that piece right? >> Yeah, I think it's more like... so we know that Kubernetes is going to be in in the environment because we know that, yeah, people are moving application workloads to standard Linux containers. But we also know that virtual machines are going to still exist in that environment. So you can think about it as, how would we enable Kubernetes to manage a virtual machine in the same way that it manages a Linux container? And, what we do there, is we actually, put the VM inside the container, right? So because the VM, specifically with (mumbles) is just a Linux process, and that's what a Linux container is. It's a Linux process, right? So you can run the hypervisor, span the virtual machines, inside of containers. But those virtual machines, are just like any other VM that would run in OpenStack or Red Hat Virtualization or what have you. And you could, vSphere for example. So those are traditional virtual machines, that are now being managed in a Kubernetes environment. And what we're seeing is sort of, this evolution of Kubernetes to take on these new types of workloads. VMs is just one example, of something that you can now manage with Kubernetes. >> Okay. And, help me understand what this means to really the app dev in my application portfolio. Because you know, the original promise of virtualization was, I can just stick my application in a VM and I never need to think about it ever again. And well, that was super helpful when windows NT was going end of life. In 2020, we do find that most companies do want to update their applications, and they are talking about, do I refactor them? Do I make them microservices architecture? I don't want to have that iceberg of an application that I'm just dragging along slowly into the new world. So. >> Yeah. >> What is this virtualization integration with Kubernetes? You mean for the AppDev and the applications? >> Yeah, sure, so what we see customers doing, what we see the application development team is doing is modernizing a lot of their existing applications, right? So they're taking traditional monolithic applications or end tier, like the applications that may run in a VM based environment and they're moving them towards more of a distributed architecture leveraging microservices based approach. But that doesn't happen all at once either, right? So, oftentimes what you see is your microservices, are still connected to VM based applications. Or maybe you're breaking down a monolithic application. The core is still running in a VM, but some of those business functions have now been carved out and containerized. So, you're going to end up in a hybrid environment from the application perspective in terms of how these applications are packaged, and deployed. The question is, what does that mean for your deployment architecture? Does it mean you always have to run a virtualization platform and a container platform together? That's how it's done today, right? OpenShift and Kubernetes run on top of vSphere, they run on top of Amazon and Azure and Google bands, and on top of OpenStack. But what if you could actually just run Kubernetes directly on Bare Metal and manage those types of workloads? That's really sort of the idea. A whole bunch of virtualization solution was based on is, let's just merge VMs natively with Kubernetes in the same way that we manage containers. And then, it can facilitate for the application developer. This evolution of apps that are running in one environment towards apps that are running essentially, in a hybrid environment from how they're packaged and deployed. >> Yeah, absolutely, something I've been hearing for the last year or so, that hybrid deployment, pulling apart application, sometimes it's even, the core piece as you said, is on premises and then I might have some of the more transactional pieces happening in the public cloud. So really interesting. So, how long has Red Hat been working on this? My (mumbles), something, you know, I'm familiar with in the CNCF. I believe it has been around for a couple of years. >> Yeah. >> So talk to us about just kind of how long it took to get here and, fully support stateful applications now. What's the overall roadmap look like? >> Yeah, so, so (mumbles) as a open source project was launched more than two years ago now. As you know, Red Hat really drives all of our development upstream in the open source community. So we launched (mumbles) project. We've been collaborating with other vendors and even customers on that. But then, you know, over time we then decided, how do we bring these technologies to market, which technologies make sense to bring the market? So, (mumbles) is the open source project. OpenShift and OpenShift Virtualization, which is what this feature is referred to commercially, is the product that then we would ship and support for running this in production environments. The capabilities, right. So, I think, those have been evolving as well. So, virtual machines have a specific requirements in terms of not only how they're deployed and managed, but how they connect to storage, how they connect networking, how do you do things like fencing and all sorts of live migration and that type of thing. We've been building out those types of capabilities. They're certainly still more to do there. But it's something that we're really excited about, not just from the perspective of running VMs, but just even more broadly from the perspective of how Kubernetes is expanding to take on new workloads, right? Because Kubernetes has moved far beyond just running, cloud native applications, today, you can run stateful services in containers. You can run things like AI and machine learning and analytics and IoT type services. But it hasn't come for free, right? This has come through a lot of hard work in the Kubernetes community, in the various associated communities, the container communities, communities like (mumbles). But it's all kind of trying to leverage that same automation, that same platform to just do more things. The cool thing is, it'll not just be Red Hat talking about it, but you'll see that from a lot of customers that are doing sessions at our summit this year and beyond. Talking about how, what it means to them. >> Yeah, that's great. Always love hearing the practitioner viewpoint. All right, Joe, I want to give you the final word when it comes to this whole space things kind of move pretty fast, but also we remember it when we first saw it. So, tell us what the customers who were kind of walking away from Red Hat Summit 2020 should be looking at and understanding that they might not have thought about if they were looking at Kubernetes, a year or two ago? >> Yeah, I think a couple of things. One is, yeah, Kubernetes and this whole container ecosystem is continuing to evolve, continuing to add capabilities and continue to expand the types of workloads, that it can run. Red Hat is right in the center of it. It's all happening in open source. Red Hat as a leading contributor to Kubernetes and open source in general, is driving a lot of this innovation. We're working with some great customers and partners, other vendors, who are working side by side with us as well. And I think the most important thing is we understand that it's an evolution for customers, right? So this evolution towards moving applications to the public cloud, adopting a hybrid cloud approach. This evolution in terms of expanding the types of workloads, and how you run and manage them. And that approach is something that we've always helped customers do and we're doing that today as they move out towards embracing a cloud native. >> All right, well, Joe Fernandez, thank you so much for the updates. Congratulations on the launch of OpenShift Virtualization. I definitely look forward to talking to some the customers in finding out that helping them along their hybrid cloud journey. All right. Lots more coverage from the CUBE at Red Hat Summit. I'm Stu Miniman ,and thank you for watching the CUBE.

from around the globe it's the cube with digital coverage of Red Hat summit 2020 brought to you by Red Hat hi I'm Stu min a man and this is the cubes coverage of Red Hat summit 2020 of course this year the event is happening all online and that gives us an opportunity to meet with red hat executives customers partners and practitioners where they are around the globe in this segment one of our favorites ever years we're talking to the women in open source and joining me for this segment first of all we have Elissa and Alexander who is the executive vice president and chief people officer of Red Hat this award fit thunder her domain dallisa it is great to see you again thanks so much for joining us thank you so much for having us all right and we have two of the Award winners so first if you see right next bit Elissa we have an epic Sain who's a doctor and PhD candidate in clinical neuroscience at the University of Gothenburg coming to us from Sweden method great to see you thank you very much all right we also have Megan Burge Sinicki who is a manager of research and operations at the open source program office at Google Megan thank you so much for joining us off though thanks for having me all right so dallisa let me hand it off to you is give our audience a little bit if they're not familiar with whipping an open source what the initiative is the community and you know what might have changed from previous years when we've talked about this sure so we realized that the tech industry is a great industry for diverse populations but a lot of diverse populations don't realize that and so as the open source leader we wanted to shine a light on the contributions that some of our underrepresented populations are making an open source that trying to inspire more people to join communities to participate to contribute we know that more diverse populations help us to innovate more rapidly they help us to solve more problems and so it's really important especially today with what's happening in the world lots of important problems to solve that we really invite more of our other upper sort of populations to join in the communities awesome so absolutely there there are lots of people that volunteer there are lots of people that do it as their day job Megan why don't we fuck you have a roll open source first Google as a strong legacy and open source in general so tell us a little bit about you know what you were working on and what you're being recognized for here yeah well a lot of the recognition comes from my work with the Drupal Association I had been with Drupal for 8 years hoping to build that foundation in supporting that community and lots of different ways from fundraising to community events running sprints and helping with their developer tools and so that was a lot what the award was based on and now I'm at Google and I've been here for about a year and a half and I run their research and operations and so Google is an expression of open source and we have thousands of people using thousands of projects and we want to make sure they do it well they feel supported that we are good citizens in the projects that we participate in and so my group provides the operational support to make sure that happens you know you know what one of the things that's always fascinating when I go to Red Hat there's so many projects there's so many participants from various walks of life last year at the show there was a lot of discussion of you know it was a survey really and said that you know the majority of people that tribute now it's actually part of their job as opposed to when I think back you know you go back a couple of decades ago and it was like oh well in my spare time or down in my basement I'm contributing here so maybe talk a little bit about the communities and you know what what Megan is embodying CSUN she worked on project now she's working for obviously a good partner of Red Hat's that does a lot of open source yeah I love the way she described what her role is at Google and that it's fascinating and Google has been really a huge contributor in the community for in communities for years and years so I think that what we're seeing with the communities and people saying yeah now it's part of my day job is that you know 20 years ago the idea that open-source development would be kind of on par with proprietary development and on par in terms of being used in the enterprise and the data center was something that I think many people questioned proprietary software was the way that most people felt comfortable making sure that their intellectual property is protected and that users could feel comfortable using it within the parameters required so that was the way it was 20 years ago and then now you think about you know most companies there is some form of open source that is part of their infrastructure so now open source is no longer you know that disrupter but it's really a viable alternative and organizations really want to use both they want to have some propriety or they want to have some open sources so that means like every company is going to need to have some need to understand how to participate in communities how to influence communities and Red Hat's a great partner in helping enterprise customers to be able to understand what those red Nets might look like and then helping to kind of harden it make sure things that they need to have application city to have certified or certified and make it really usable in a way they're comfortable with in the enterprise that's kind of special Red Hat place but it's just a tribute to where we come in a world in terms of open source being really accepted and thriving and it helps us to innovate much more rapidly yeah and there's there's no better way to look at not only where we are but where we're going then talk about what's happening in the academic world so that gives it brings us Aneta so you are the academic award winner you're a PhD candidate so tell us a little bit about your participation and open source what it means to be part of this community my PhD project involves using virtual reality to measure the arm movements of people with stroke so we have participants coming in into our lab so they we're these 3d glasses and then they start seeing virtual objects in the 3d space and they use their hands to touch at these targets and make them disappear and we have all these movements data specially interpreters and then we write code and analyze the data and find out how much they have recovered within one year after stroke this is my PhD project but my involvement with open source happens they before like in starting from 2010 I have been editing Wikipedia and I have been writing several articles related to medicine and healthcare so that is where I started with open open knowledge and then I moved on words and after my medical studies I moved to research and worked on this awesome project and so there are multiple ways by which I have engaged with open source that's far that's awesome my understanding is also some of the roots that you had and some of the medical things that you're doing have an impact on what's happening today so obviously we're all dealing with the global pandemic in Koba 19 so I'd like to hear you know what your involvement there you know your data obviously is politically important that we have the right data getting to the right people as fast as possible definitely yes right now I'm working on writing creating content for Wikipedia writing on articles related to Kobe 19 so I mostly work on writing about its socio-economic impact writing about Kobe 19 testing and also about the disease in general mental health issues surrounding that social stigma associated began with it and so forth so I use all these high-quality references from the World Health Organization the United Nations and also from several journals and synthesize them and write articles on Wikipedia so we have a very cool project called wiki project code 19 on Wikipedia where people who are interested in writing articles creating data uploading images related to poet 19 come together and create some good content out of it so I am a very active participant there alright and making my understanding is you you also have some initiatives related to kovat 19 maybe you can tell us a little bit about those yeah well one I'm loosely affiliated with this kovat act now and that is a combination of developers data scientists epidemiologists and US state government officials and it's looking at how was the curve look like and how does that curve get flattened if governor's made decisions faster or differently than what they're making today and how does it impact the availability of ICU beds and ventilators and so that is a tool that's being used today by many decision-makers here in the US and my contribution to that was they needed some resources I reached into Google and found some smart generous volunteers that are contributing to the dataset and actually I just connected with Neda do this award program and now she's connected and is gonna start working on this as well yes oh that's fantastic yeah I mean dallisa you know we've known for a long time you want to move fast if you want to connect you know lots of diverse groups you know open sources is an important driver there what what else are you seeing in your group you know with your hat is the the people officer you know obviously this is a big impact not only on all of your customers partners but on fun Red Hatters themselves well it is a huge impact we're so fortunate that we have some experience working remotely we have about 25 percent of our population that historically works remotely so we have that as a foundation but certainly the quick move the rapid move to really thinking about our people first and having them work from home across the globe that is unprecedented and at this point we have some individuals who have been working from home for many many many week and others that are really in entering their fourth week so we're starting to have this huge appreciation for what it's like to work remotely and what we can learn about more effective inclusion so I think you know back to the idea of women and open source and diversity inclusion one of the things you may always prided ourself in is we focus on inclusion and we think about things like okay if the person is not in the room with their remote let's make sure for including them let's make sure they get to speak first etcetera well now we're learning what it's really like to be remote and for everyone to be remote and so we're creating this muscle as an organization I think most organizations are doing this right getting a muscle you didn't have before we really really having to think about inclusion in a different way and you're building a capability as an organization that you didn't have to appreciate those that are not in the room and to make sure they are included because no one's in the room you know we're really important pieces and dallisa you know one of the things that that's always great about Red Hat summit is you you bring together all these people as we just heard you know that your two Award winners here you know got connected through the awards so maybe give us a little bit of a peek as to what sort of things the community can still look forward to how they can continue to connect even though we're all going to be remote for this event yeah this event is is it going to be great event and I hope everyone joins us along our journey we are fortunate that Red Hat you know as the open source leader really wants to take a leadership position in thinking about how we can shine a light on opportunities for us to highlight the value of diversity and inclusion and so we've got a number of events not throughout the summit that we'd love people to join in and we're going to be celebrating our women and open-source again at our women's leadership community lunch is now not a lunch it is now a discussion unless you're having your lunch that you can check your desk but we're having a great conversation at that event I mean by people to join in and have a deeper conversation and also another look at our women in open source Award winners but these Award winners are just so amazing every year that applications that are submitted are just more and more inspiring and all the finalists were people that are so impressive so I love the fact that our community continues to grow and that they're more and more impressive people that are joining the community and that they're making those connections so that together we can you know really shine a light on the value that women bring to the communities and continue to inspire other underrepresented groups to join in and participate then a you know research obviously is an area where open-source is pretty well used but just give us a little bit of viewpoint from your standpoint yourself and your peers you know I would think from the outside that you know open sourced is just kind of part of the fabric of the tools that you're using is it something that people think specifically about a course or does it just come naturally that people are you know leveraging using and even contributing what what's available the tool I'm using is called cuteness it's an open source tool written in Python and so that gives me the possibility to have a look in deeper into the code and see what's actually inside for example I would like to know how what is the size of the target that is shown in the virtual space and I can fit know that correctly to the millimeters because it's available to me in open source so I think these are the advantages which researchers see when they have tools open-source tools and at the same time there's also a movement in Sweden and in most of Europe where they want the researchers are asking for publishing their articles in open access journals so they want most of their research be published as transparent as possible and there is also this movement where people want researchers want to have their data put in some open data city so that everybody can have a look at it and do analysis on the data and build up on that data if other people want to so there's a lot going from the open access side and knowledge side and also the open source side in the research community and I'm looking forward to what probably 19 will do to this movement in future and I am sure people will start using more more and more open-source tools because after the Manderly yeah making I'm curious from your standpoint when I think about a lot of these communities you know meetups are just kind of some of the regular fabric of how I get things done as well as you know just lots of events tie into things so when you're talking to your colleagues when you're talking to your peers out there how much is kind of the state of reality today having an impact in any any learnings that you can share with gaudí yeah that is definitely a challenge that we're going to figure out together and I am part of a group called Foss responders we are reaching out to projects and listening to their needs and amplifying their needs and helping to get them connected with resources and one of the top three areas of need include how do I run an online community event how do I replace these meetups and what is wonderful is that groups have been moving in this direction already and so who would release a guide of how they run online events and they provide some tooling as well but so has WordPress put out a guide and other projects that have gone down this path and so in the spirit of open source everyone is sharing their knowledge and Foss responders is trying to aggregate that so that you can go to their site find it and take advantage of it yeah definitely something I've seen one of the silver linings is you know these communities typically have been a lot of sharing but even more so everybody's responding everybody's kind of rallying to the cause don't want to give you the final word obviously you know this is a nice segment piece that we usually expect to see at Red Hat summit so what else do you want to help share where the community is final closing thoughts well I think that you know we're not done yet we have been so fortunate to be able to highlight you know the contributions that women make to open source and that is a honor that we get to take that role but we need to continue to go down this path we are not we're not done we have not made the improvement in terms of the the representative in our communities that will actually foster all of the improvements and all the solutions that need to happen in the world though we're going to keep down this pathway and really encourage everyone to think through how you can have a more inclusive team how you can make someone feel included if you're participating in a community or in an organization so that we really continue to bring in more diversity and have more innovation well excellent thank you so much Alisa for sharing it thank you too - both of you Award winners and really look forward to reading more online definitely checking out some of the initiatives that you've shared valuable pieces that hopefully everybody can leverage all right lots more coverage from Red Hat summit 2020 I'm Stu minimun and as always thank you for watching the cube [Music]

>>from around the globe. It's the Cube with digital coverage of Red Hat. Summit 2020 Brought to you by Red Hat. >>Hi, I'm stupid, man. And this is the Cube's coverage of the Red Hat Summit 2020 course. The event this year is digital. We're talking to Red Hat executives, partners and customers where they are around the globe, pulling them in remotely happy to welcome back to the program. One of our Cube alumni on a very important topic, of course, that red hat open shift and joining me is Clayton Coleman. Who's the open shift chief architect with Red Hat. Clayton, thanks so much for joining us. Thank you >>for having me today. >>All right, So before we get into the product, it's probably worthwhile that we talked about you know what's happening in the community and talking specifically, you know, kubernetes the whole cloud, native space. Normally we would have gotten together. I would have seen you at Cube Con Ah, you know, at the end of March. But instead, here we are at the end of April. Looking out, you know, more CN cf events later this year, but first Red Hat Summit is a great open source event and broad community. So would really love your viewpoint as to what's happening in that ecosystem. >>It's been a really interesting year, obviously. Ah, with an open source community, you know, we react to this. Um, like we always react to all the things that go on in open source. People come to the community and sometimes they have more time, and sometimes they have less time. I think just from a community perspective, there's been a lot of people you know. It's reaching out to their colleagues outside of their companies, to their friends and coworkers and all of the different participants in the community. And there's been a lot of people getting together for a little bit of extra time trying todo, you know, connect virtually where they can't connect physically. And it's been it's been great to at least see where we've come this year. We haven't had Cube con and that'll be coming up later this year. But Kubernetes just had the 1 18 release, and I think Kubernetes is moving into that phase where it's a mature, open source project. We've got a lot of the processes down. I'm really happy with the work that the steering committee, um, has gone through. We handed off the last of the bootstrap Steering Committee members hand it off to the new, fully elected steering committee last year, and it's gone absolutely smoothly, which has been phenomenal on the The core project is trying to be a little bit more stable and to focus on closing out those loose ends being a little bit more conservative to change. And at the same time, the ecosystem has really exploded in a number of directions, as as Kubernetes becomes more of a bedrock technology for, um, enterprises and individuals and startups and everything in between. We've really seen a huge amount of of innovation in the space, and every year it just gets bigger and bigger. There's a lot of exciting projects that >>I >>have never even talk to somebody on the Kubernetes project. But they have made and build and, uh, and solve problems for their environments without us ever having to be involved, which I think it's success. >>Yeah, Clayton, you know, one of the challenges when you talk to practitioners out there is just keeping up with the pace of change. Can really be challenging. Something we really saw acutely was Docker was rolling out updates every six weeks. Most customers aren't going to be able to change fast enough to keep up with things you love your view point both is toe really what the CN CF says, as well as how Red Hat thinks of products. So you talked about you know, kubernetes 1.18. My understanding, even Google isn't yet packaging and offering that version there. So there's a lag between things. And as we start talking about managing across lots of clusters, how does Red Hat think of this? How should customers think about this? How do we make sure that we're, you know, staying secure and keeping updated on things without getting run over by the constant treadmill of >>change? That the interesting part about kubernetes Is it so much more than just that core project? You know, no matter what any of us in the in the core kubernetes project or in the products that red hat that build around open shift and layers on top, there's a There's a whole ecosystem of components that most people think of this fundamental to accomplishing building applications deploying them, running them, Whether it's their continuous integration pipelines or it's their monitoring stacks, we really as communities has become a little bit more conservative. >>Um, I >>think we really nail down our processes for taking that change from the community, testing it. You know, we run tens of thousands of automation tests a week on the latest and greatest kubernetes code, given time to soak, and we did it together with all those pieces of the ecosystem and then make sure that they work well together. And I've noticed over the last two years that the rate of oops we missed that in KUBERNETES 1 17 that by the time someone saw it, people are already using that that started to go down for us, it really hasn't been about the pace of keeping up with the upstream. But it's about making sure that we can responsibly pull together all the other ecosystem components that are still have much newer and a little bit. How do we say, Ah, they are then the exciting phase of their development while still giving ah predictable, reliable update stream. I would say that the challenges that most people are going to see is how they bring together all those pieces. And that's something that, on open shift, we think of as our goal is to help pull together all the pieces of this ecosystem, Um, and to make some choices for customers that makes sense and to give them flexibility where it's not clear yet what the right choice might be or where different people could reasonably disagree. And I'm really excited. I feel like we've got our We have a release cadence down and we're shipping the latest Cube after it's had time to quickly review, and I think we've gotten better and better at that. So I'm really proud of the team on Red Hat and how they've worked within the community so that everybody benefits from that in that testing of that stability. >>Great. I'd like to teach here, you dig in a little bit on the application side what's happening from the work loads that customers are using? Ah, what other innovations happening around that space? And how is Red Hat really helping? Really, The the infrastructure team and the developer team work even closer together, like Red Hat has done for a long time. >>This is This is a great question. I say There's two key, um, two key groups coming together. People are bringing substantial important critical production workloads, and they expect things both to just work, but also to be able to understand it. And they're making the transition. Ah, lot of folks I talked to were making the transition from previous systems they've got. They've been running open shift for a while, or they've been running kubernetes for a while, and they're getting ready to move, um, a significant portion of their applications over. And so, you know, in the early days of any project, you get the exciting Greenfield development and you get to go play with new technologies. But as you start moving your 1st 1 and then 10 and then 100 of your core business applications from the EMS or from bare metal into containers, you're taking advantage of that technology in a responsible way. And so the the expectations on us as engineers and community members is to really make sure that we're closing out the little stuff. You know, no bug is too small, but it can't trip up someone's production applications. So seeing a lot of that whether it's something new and exciting like, Um uh, model is a service or ai workloads or whether it's traditional big enterprise transaction processing. APS on the other side on that development, um, model I think we're starting to see phase to our community is 2.0, in the community, which is people are really leveraging the flexibility and the power of containers, things that aren't necessarily new to people who had. We got into containers early and had a chance to go through a couple of iterations. But now people are starting to find patterns that up level development teams, so being able to run applications the same way on a local machine as in a production environment. Well, most production environments are there now, and so people are really having toe. They're having to go through all of their tools and saying, Well, does this process that works for an individual developer also work when I want to move it there, my production or staging environments to production, and so on. New projects like K native and tectonic, which are kubernetes native, that's just one part of the ecosystem around development. On top of kubernetes, there's tons of exciting projects out there from companies that have adopted the full stack of kubernetes. They built it into their mindset, this idea of flexible infrastructure, and we're seeing this explosion of new ways where kubernetes is really just a detail, and containers are just the detail and the fact that it's running this little thing called Docker down at the heart of it. Nobody talks about anymore, and so that that transition has been really exciting. I think there's a lot that we're trying to do to help developers and administrators see eye to eye. And a lot of it's learning from the customers and users out there who really paved the way the which is the open source way. It's learning from others and helping others benefit from that. >>Yeah, I think you bring up a really important point we've been saying for a couple of years. Now that you know KUBERNETES should get to the point where it's boring and boring in a way also cause it's gonna be baked in everywhere we saw from basically customers just taking the code, really spending a lot of their own things by building the stack to, of course, lots of customers have used open shift over the year to If I'm adopting Public Cloud more and more, they're using those services from that standpoint. Can you talk a bit about how Red Hat is really integrating with public clouds? And you know your architectural technical philosophy on that? And how might that be? Differ from some other companies that you might call a little bit more, you know, Cloud of Jason, as opposed to being deeply integrated with the public cloud. >>The interesting thing about Kubernetes is that while it was developed on top of the clouds, it wasn't really built from Day one assuming a cloud underneath it. And I think that was an opportunity that we really missed. And to be fair, we had to make the thing work first before we depended on these unreliable clouds. You know, when we started, the clouds were really hitting their stride on stability and reliability, and people were it was the hot was becoming the obvious choice to some of what we've tried to do is take flexible infrastructure is a given, um, assume that the things that the cloud provides should be programmed for the for the benefit of the developer and the application, and I think that's a that's a key trend is we're not using the cloud because our administration teams want us. We're using the cloud because it makes us more powerful developers. That enables new scenarios. It shortens the the time between idea reality. What we have done in open shift is we've really built around The idea of open shift running on a cloud should take advantage of that cloud to an extreme degree, which is infrastructure could be flexible. The machines in that cluster need to come and go according to the demands of the applications on top of it. So giving a little bit more power to the cluster and taking a little bit of way from the cloud I'm. But that benefits. That also needs to benefit that those who are running on premise because I think, as you noted, our goal is you want this ubiquitous kubernetes environment everywhere, and the operations teams and the development teams and the Dev Ops teams in between need to have a consistent environment and so you can do this on the cloud. But you don't have that flexibility on premise. You've lost something. And so what we've tried to do as well is to think about those ideas that are what we think of as quote unquote cloud native that starts with a mutable operating systems. It starts with everything being declarative and working backwards from, you know, I wanna have 15 machines and then the cluster or controllers on the cluster say, Oh, well, you know, one of the machines has gone bad. Let's replace it on the cloud. You ask for a new I'm cloud infrastructure provider or you ask the the cloud a p i for a new machine, and then you replace it automatically, and no one knows any better on premise. We'd love to do the same thing with both bare metal virtualization on top of kubernetes. So we have that flexibility to say you may not have all of the options, but we should certainly be able to say, Oh, well, this hardware is bad or the machine stopped, so let's reboot it, and there's a lot of that same mindset that could be applied. We think that'll, um if you need virtualization, you can always use it. But virtualization is a layer on top benefits from some of the same things that all the other extensions and applications on top of kubernetes competitive trump. So trying to pay that layer and make sure that you have flexible, reliable storage on premise through our SEF and red hat storage products, which are built on top of the cluster exactly like virtualization, is both on top of the cluster. So you get cloud native storage mixed in working with those teams toe. Take those operational best practices. You know there's well, I think one of the things that interests me is no. 1 20 years ago, who was running an early version of SEF wouldn't have some approach to run these very large things that scales organizations like CERN have been using SEF for over a decade at extremely large scales. Some of what our mindset is we think it's time to bake some of that knowledge actually into our software for a very long time. We've kind of been building out and adding more and more software, but we always left the automation and the the knowledge about how that software supposed to be run to the side. And so by taking that and we talked about operators. Kubernetes really enshrines. This principle is taking that idea, taking some of that operational knowledge into the software we ship. Um, though that software can rely on kubernetes open shift tries to hide the details of the infrastructure underneath and our goal. I think in the long run it will just make everybody's lives easier. I shouldn't have to ship you a SEF admin for you to be successful. And we think we think there's a lot more room here that's really gonna improve how operations teams work, that the software that they use day to day. >>So Clinton you mentioned virtualization is one of the topics in there. Of course, virtualization is very prevalent in a customer's data center environment today. Red Hat open shift, oftentimes in data centers, is sitting on BM ware environments. Of course. Recently, VM Ware announced that they have kubernetes baked into the solution, and red hat has open shift with red hat virtualization. Maybe, you know, without going into too much depth, and you probably have breakouts and white papers on this. But you know what kind of decision point should customers be thinking about when they're deciding? Do I do this in bare metal. Do I do it in virtualization? What are some of the, you know, just high level trade offs there when they need to make those decisions, >>I think it's, um I think the 1st 1 is Virtualization is a mature technology. It's a known quantity for many organizations, and so those who are comfortable with virtualization, I'd say, like any responsible, uh, architecture engineering team. You don't want to stop using something that's working well just because you can. And a lot of what I would see as the transition that companies on is for some organizations without a big investment in virtualization. They don't see the need for it anymore, except as maybe a technical detail of how they isolate insecure workloads. One of the great things about virtualization technology that we're all aware of over the last couple years is it creates a boundary between work loads and the underlying environment. That doesn't mean that the underlying environment and containers can't be as secure or benefit from those same techniques. And so we're starting to see that in the community, this kind of spectrum of virtualization all the way from the big traditional virtualization to very streamlined, stripped down virtualization wrappers around containers. Um, like some of the cloud providers use for their application environments. So I'm really excited about the open source. Community is touching each of these points on the spectrum. Some of our goals are if you're happy with your infrastructure provider, we want to work well with, and that's kind of the pragmatic of everyone's on a different step in that journey. The benefit of containers is no matter how fast you make of VM, it's never gonna be quite as fast, is it containers. And it's never gonna be quite as easy for a developer to run on their laptop. And I think working through this is there's still a lot of work that we as a community to do around, making it easier for developers to build containers and test them locally in smaller environments. But all of that flexibility can still benefit from virtualization under later or virtualization used as an isolation technology. So projects like Kata and some of the work that's being done in the open source community around projects like firecracker taking the same, um, open source ideas and remixing them a different points gives us a lot of flexibility. So I would say, um, I'm actually less interested in virtualization then all of the other technologies that are application centric and at the heart of it, a VM isn't really a developer centric idea. It's specifically an administrative concept that benefits the administrator, and developers can take advantage of it. But I think all of the capabilities that you think of when you think about building an application like scaling out and making sure patches are applied, being able to roll back separating your configuration on then all of the hundreds of other levels of complexity that will add around that like service MASH and the ability to gracefully tolerate failures in your database. These were where I think, um, virtualization needs to work with the platform rather than being something that dominates how we think about the platform. It's application first, not being first. >>Yeah, no, you're absolutely right that the critique I've always given, you know for a number of years now is if you look at virtualization, the promise was, let's take that old application that probably should have been updated and just shove it in a VM and never think about it again. That's not doing good things for the user. So if I look at that at one end of the spectrum away at the other end of the spectrum, trying not to think about infrastructure, you mentioned K native s 01 of the things that you know I've been digging in tryingto learn more about at Red Hat Summit has really been the open shift server lists. So give us the update on that piece. Um, you know, that's obviously very different discussion than what we were just having from a virtualization standpoint. Eso How does open shift look at server lists? How does that tie into what? You know, if I'm doing server, listen, Amazon versus you know some of the other open source options for serverless. How should I be thinking about that? >>There's a lot of great choices on the spectrum out there. I think one of the interesting things and I love the word spectrum here because cane native kind of sits in a spot where it tries to be, as the name says, it tries to be as kubernetes native as possible, which lets you tap into some of those additional capabilities when you need it. And one of the things I've always appreciate it is the more restrictive framework is usually the better. It is doing that one thing and doing it really well. We learned this with rails. We learned this with no Js. And as people have built over the years, the idea of simple development platforms. The core function idea is a great simple idea, but sometimes you need to break out of that. You need extra flexibility or your application needs to run longer or slow Start is actually an issue. One of the things I think is most interesting about K native and I see comers and user. I think this way it's a good point. Um, that gives you some of the flexibility of kubernetes and a lot of the simplicity of, um, the functions is a service, but I think that there's going to be an inevitable set of use cases that tie into that which are simpler where open organization has a very opinionated way of running applications, and I think that flexibility will really benefit K native. Whereas some of the more opinionated remarks around server lists lose a little bit of that. So that's one dimension that I still think a native is well positioned to kind of capture the broadest possible audience, which for kubernetes and Containers was kind of our mindset. We wanted to solve enough of the problems that you can solve. You can run all your software. We don't have to solve all those problems to such a level that there's endless complexity, although we've been accused of having endless complexity and Cooper days before, but just trying to think through what are the problems that everyone's going to have to give them a way out? I'm at the same time for us, when we think about prioritization functions is service about integration. It's about taking applications and connecting them, connecting them through kubernetes. And so it really depends on identity and access to data and tying that into your cloud environment. If you're running on top of a cloud or tying it into your back end databases, if your on premise, >>I >>think that is where the ecosystem is still working to bring together and standardize some of those pieces in kubernetes or on top of Kubernetes. What I'm really excited about is the team as much. You know, there's been this core community effort to get a native to a G, a quality. Alongside that, the open shift serverless team has been trying to make it a dramatically simpler action. If you have kubernetes and open shift, it's a one click action to get started with, Um Kay native and just like any other technology. How accessible it is determines how easy users find it to get started and to build the applications they need. So for us, it's not just about the core technology. It's about someone who's not familiar with Serverless or not familiar with kubernetes. Bring up an editor and build a function and then deploy it on top of open shift. See it scale out like a normal kubernetes application, not having to know about pods or persistent volumes or notes. And so these air, these are some of the steps. I've been really proud that the team's done. I think there's a huge amount of innovation that will happen this year and next year, as the maturity of the kubernetes ecosystem really grows up, we'll start to see standardized technologies, for I'm sharing identity across multiple clouds across multiple environments. It's no good if you've got these applications on the cloud that need to tie into your corporate L dap. But you can't connect your corporate held up to the cloud. And so your applications need 1/3 identity system. Nobody wants 1/3 identity system. And so, working through some of this thing where the challenges I think that hybrid organizations are already facing and our job is just to work with them in the open source communities and with the cloud providers partner with them and open source so that the technologies in kubernetes fit very well into whatever environment they run it. Alright, >>well, Clayton, really appreciate all the updates there. I know the community is definitely looking forward to digging through some of the breakout sessions reading all the new announcements. And, of course, we look forward to seeing you on the team participating in many of the kubernetes related events happening later this >>year. That's right. It's ah, gonna be a good year. >>All right. Thanks so much for joining us. I'm still Minuteman and as always thank you for watching you. >>Yeah, yeah, yeah, yeah

(slow music) >> From around the globe. It's the cube with digital coverage of Red Hat Summit 2020 brought to you by Red Hat. >> Welcome back. This is the cubes coverage of a Red Hat Summit 2020. The event happening digitally this year. We are bringing in Red Hat executives, customers and partners from where they are around the globe. And happy to welcome back to the program. One of our cube alumni. Robin Bergeron is the senior principal community architect with Ansible part of Red Hat. Robin, great to see you. Thanks so much for joining us. So we've got the community coming together even while we're apart. >> Indeed. That's what we're good at. So, I'm glad to be back here again with you all. So, hello. >> All right. So, Robin, we caught up with you last at AnsibleFest of course Red Hat Summit. So much community activity that goes on. The Ansible, community is a big piece of summit even though they also have, the separate AnsibleFest. So just give us a little bit update what's happening in your world and in the community. >> Well. I hate to say it's a, "it's a big wide world" because it sounds very cliche, but the Ansible world is fairly big. I don't know if, let's see, we talked, lasted, AnsibleFest and that was in September in Atlanta, is that correct? >> Sounds right. Yep. >> I believe so. So right around that time was when GitHub released their annual list of, they have a report called the Octoverse they publish every year, in conjunction with their annual event. And one of their metrics they have on that list is, most active projects. So, we clocked in at the number ninth most active project on Github this past year. And that's out of, I've lost count of github, like number of projects. It's not quite the, United States national debt status, but it's a, like a hundred million repositories or something like that. So we're the number nine most active repository this year. And I believe we are one of two projects who's been on that list every year since 2016 I want to say. So, yeah, we're at 5900 contributors right now. So it's, all over the globe. A lot of people keeping us very busy. I guess that and fact it's so busy and we talked about collections a bit when we were at AnsibleFest this past year and it's been a thing that we've been talking about continuously in Ansible community and also, as part of Red Hats product line for a while and we've actually now gotten to the point of sort of splitting out the Ansible repository. Ansible is going to continue to be the, you a car and you look under the engine and there's like the things that make the car run. >> Ansible base, separate from the windshield wipers and all the ad-ons and all the cool stuff that you actually, want to get when you get a car. And that stuff is actually getting split out into Ansible collections that we'll have or repository that's actually more managed by the community, which will empower them to be able to make more decisions for us to be able to get things done, more rapidly. Cause in the past it's always been a really a tug of war between, work and github have always been very respectful about, how the balances between community and product because obviously without a community you don't have a product. And this is a obviously a method that Red Hat has sort of nailed down. I guess IBM really liked the idea. So here we are. But we're really looking forward to, right now we've got a handful of contributors who are adding new modules into this new repo. But, they're also helping us work out all the kinks in the contributor process and how it works that way. Once we opened for business, since we've got several thousand contributors, we don't say, open for business and then have everybody comes running into a glass wall like it and then all on the floor, right? We want the doors to be open. We want the, registers so to speak to be processing things. We want, all the box to be working, all of the, all of the magic to be happening just as it is, as it has in past. But, this time with a little bit more empowerment to the community, that's on a work progress for it was like forever, but, nine months, and here in the next few weeks that will be open for business and we're hoping that, by the time the AnsibleFest rolls around, that will be part of the two, part and parcel to the 2.10 release. And, we're hoping that, even though under the hood for contributors, that's changed. We believe we'll be very transparent brand eaters, which has been one of the most important things for us because, we don't like to break people. That's, >> yeah, >> {Robin] Glad yeah >> Absolutely Robin. So it was one of the key things a announced at a AnsibleFest last year. Anybody that knows the software world is the traditional release train. Get on that train. Got to make sure you get your feature in there. But for a solution like Ansible, which as you said, has a lot of partners and it's a very big ecosystem. If you have to worry about how much stuff do I get shoved into one release, it's a little bit limiting. So you break those pieces up more like the, containers, that go on the train and you can make sure that you're adding and, doing the various pieces as they go. So maybe >> Yeah >> not the perfect analogy. >> Yeah. >> But very important so, Robin, as you've been going through this, I'm wondering, what feedback are you getting from the contributors there? and how about as you said, very active community. We know if anybody you know, says something, you got, the crowd and the wisdom coming in and giving you ideas. But, how do you balance that? You're not going to have everybody be happy about every decision, but making sure that the ultimate release train, does the job and delivers the overall solution. >> Yes. What color are we going to paint? Paint our bike shed. Right? Like the yak for circling. So it's, I don't want to to say it's been mixed, it's, you know, we, I can, I compare and contrast this, one of my, previous roles was being the newer project leader, right. And, which is, as we know the upstream, for Red Hat enterprise Linux, and its some of the, Linux and, a lot of the Linux distributions have been around for forever. Back when there were like, I don't know. 10, 15 opensource projects that anybody at all, could contribute to. Now as we can see looking on, github and many other places get lab, open dev. There's a, you name it, there's a gazillion opensource projects out there. People aren't always as attached to, I don't want to say attached, coz that sounds, terrible, but open source has become such a norm people are just very used to, there's something wrong. I'm going to submit it, I'm going to hope it gets accepted, but I'm going to move on with my life because I also have all these other places that I can also contribute, right. That said, we do have, a significant number of compute of contributors who have been with us back since Ansible started. Some of those folks go back with us to Fidor days, on Linux days on and on and on. Some of them, some folks I have concerns, they do like that this is the opportunity to give them more empowerment to figure out better ways to run the, contributor process. I think the number one thing that everybody's been concerned about is what diseases your experience going to be. And I think that's a testament to, just the power of our community is that, people aren't just concerned about how am I going to get my stuff in and your stuff in and like the tug of war of like, is one person can get something else in before someone else. Everybody's very concerned about is this going to still work for the end users? Is this going to disrupt them? Because it's a change under hood. Are they going to have to change all their playbooks and all of their, rules and everything that they have. And right now the goal is, it should be transparent. Anything that you have written right now, you should continue work, you shouldn't notice. Once we get your 3.O our goal is to ramp people up into harnessing the power of collections. But first we need to get the collections, infrastructure in place, before we get in. Start giving them to artists the power of collections. You can't just flip the switch and be like, hi . So it used to be this way, now we have collections and now you've got to redo everything, right. Because that's-- you still have the opportunity because it's open source. We'll have this window where we can still find all the bugs and get that re rapid feedback, which means, once we roll out, Red Hat Ansible automation platform, the next version. I'm not going to say an AnsibleFest. That would be shocking, right? We never do announcements at events. But, whenever that product comes out, we want to make sure, that power of open source and, having that rapid feedback loop, ensures that, what we end up, we'll bring to customers, winds up being solid, but I believe it will be very, very solid for contributors because or, and, a community. There's, because, a significant number of our contributors are community users and they have that in their own interest in mind. And we've seen that not just from, I'm a community user at a university, but all of our partners are actually participating in the community as well. And there, just painting and chatting and we had a, we had planned to have a European as well contributor summit, which is a thing we normally run in combination or the day before AnsibleFest. and we had planned that for Sweden. I was so excited. I was going to go to Gothenburg. I hear it's a charming little town, except, when we are all stuck in, the a world that we are in currently. so we ran that virtually and a lot of our longterm contributors are actually from Europe. So that was really exciting except for me, cause I had to get up 8 Am but it was still nice to see them all. So we had, 50 some odd folks pop in over the course of, that day. And we talked through elections and debated and, got some demos from folks. Had some folks talk through some specific collections, folks talking about AWS and some of the networking things. So, yeah it was nice to see everyone. I was sad that it wasn't in Gothenburg. But it is what it is. I'm going to roll. >> So Robin, I think back to 2019 an automation, was right at the top of a hot topics. When I talk to practitioners out there, many conferences I went to, not just of course Ansible test, which focus on it, but many other shows and events. Well when you talk to people about key initiatives, its in a really leveraging automation, something that I've heard talked about my entire career, but really it feels like the last painful of years and people are much more serious about it. You know, you referenced the times that we live in right now, we're unprecedented global pandemics. So I'm not saying that, somebody, everybody all of a sudden woke up and say, Oh my gosh, I have to work from home and I need to be smarter. Let me finally use this automation that I've been hearing about all these years. But why don't you bring us into, what is happening today, what you are hearing customers, because automation obviously is a critical piece of what everybody is doing and probably just, shines a light on it even more. Now that we need to make sure that people are being efficient and still being able to deal with their lives while everything else is going on. >> Yeah. It's interesting because some of is, as well as used. Yeah, there's actually a, there's the dependency graph that you can look at on github and it will tell you how many other things in github are actually depending on the Ansible. It's, I can't even remember the number. It's a very large number, like tens of thousands of things as I recall. Disclaimer, my memory is terrible sometimes. I believe it was in the tens of thousands of things. Lots of people use Ansible and it's almost like probably not quite as popular as, the uses Docker container to get started, but, venture to guess it might be a number to that. Type this Ansible thing and this thing will magically come up. Right. For folks that are, in a traditional IT department, just trying to get along, day to day right now who are, they're like me. They're at home, they're with their spouse, they're sharing an office. They're also homeschooling their kids if they got out of bed. Hopefully we all have enough bandwidth. For those folks it's, I'm just glad that I continue to have this Ansible thing, they're using Ansible tower, they're glad that they can still manage to figure out how to collaborate their coworkers in that type of environment. For all the folks out there who are doing, research or trying to set up any type of infrastructure anywhere to related to this, I don't care if it's a, grocery store or you're a research laboratory, whatever it is. Last thing you want to do is spend five hours, be like, oh God okay, let me get out my manual. Where did I, it's hey, there's an Ansible. Excellent, I can type this Ansible thing in. And if for some reason it gets hung up. We have folks on IRC, we have, there's folks on stack overflow . There folks literally everywhere. You can ask a question on Twitter and It's a Pretty large, friendly, global community of people who have plenty of answers. And that's, I can't say we're like, hey, we solved everything, but we got all the >> stuff out of the way so that people can actually solve all of their, they can get down to what's actually important for them. And so that, that's always been one of the most redeeming things about Ansible that it's, for me, it's, the thing that I work on is, it's easy and it helps people solve their problems and gets all there, stuff out of the way so that they can concentrate on what's actually important to them. So I like to think, it's most important to them. And I know it is, but it's interesting seeing how things change, as people are like, are you going to teach a bunch of people Ansible now? And it's like, well, if they're in need of a job, there are a lot of online resources for that. But if they're just trying to get through their job, like everybody's sort of in a don't rock the boat position. Like if I can get a little bit ahead, that's cool. If I've already got a bunch of stuff automated Yes. That's one less thing that I have to worry about right now and that's all we can really hope for at this moment. >> Yeah, great stuff Robin. One of the high point always is seeing, the value and support of the community and as you said, it's something that we definitely see highlighted up out there. All right, Robyn Bergeron, greatest as always to catch up with you. Thank you so much. I'm sure you know so many community activities that people will be able to participate in. This week at Red Hat Summit, even though we're, all doing it remotely, >> and the >> yeah >> challenges there. >> Glad I, great uni central area city. You can come on, come on by and see all of the, various Red Hat open source communities doing their thing. >> All right, watch lots more coverage from Red Hat Summit coming at you. I'm Stu Miniman and always, thank you for watching, the cube (slow music)

from around the globe it's the cube with digital coverage of Red Hat summit 2020 brought to you by Red Hat welcome back this is the cubes coverage of Red Hat summit 2020 I'm Stu minimun and it's our seventh year doing the cube this year of course it is a digital event which means we are reaching all the community members where they are around the globe really excited to bring program first time guests and a first time to redhead summit Vachon Vora he's the chief technology officer of Vodafone idea joining me from Mumbai India bhishan nice to see you take so much for joining us it's a pleasure to be here as >> I'm looking forward to this interaction all right so as I said I've been at Red Hat show for many years the the telecommunications space you know service providers are some of the you know more interesting in the technology space you talk about scale you talk about change you talk about you know software eating the world all of those discussions are ones I've had for many years but you know I think many people know Vodafone may be a vote a fun idea escape for us you know the organisation and of course you've got the CTO at so you know what that means inside your organization sure so what a fun idea is a company that came came to acclaim as a result of a merger about 18 months ago so the number two and number three operators in India which was Vodafone an idea came together to create a telco serving over 300 million subscribers and we've been integrating the the networks over the last 18 months and consolidating and doing one of the largest integration in the world of two networks comprising over 200 thousand sites and carrying you know more than 50 billion MB of traffic per hour per day serving more than 40 million voltaic customers and we have been duplicating the network very very busy with her and we taken down so far almost a hundred thousand base stations which is equivalent to the size of a large operator in us so that's about the carnahan that is about the scale of the the operator that word of an idea is and what we've been busy with for the last day yeah well well Besant of course the reason we're doing this event online is because right now with the global pandemic the vast majority of the population they're at home so you know healthcare of course you know one of the major concerns I actually have done interviews with some of the power and energy companies critically important at this time but you know telecommunications you know what one of the top of the list you know in normal times for what people need but today it's the the only way that we can all connect it so tell us a little bit about do you know what the current situation you know the impact and importance this really highlights of your business yeah so just as the rest of the world India is also in a lockdown and India actually has one of the largest the largest lockdown in the world putting all 1.3 billion people in a lockdown yeah across the entire country so within that context the telecom network is crucial to make sure that the life goes on the essential services are delivered the industry continues to still operate as the best it can and all of that is made possible because of a stable and reliable network that we offer so a huge huge impact on the society always has been but in in this current context it is even more more critical and crucial so what we do is we make sure that we are the invisible layer you talked about health healthcare workers and emergency services well we are the invisible essential service that probably many people don't see but we are the ones who are really helping this country survive this this crisis and so far we have seen 25 30% increase in traffic in a single day in one week we experienced the same amount of traffic growth we would have experienced in the entire year so we we scalability is very very critical in our network and we've been able to keep up with that kind of a growth and continue to serve the communities and in this crucial juncture and all this dude large extent has been made possible because of a large-scale deployment of cloud technologies that we have done over the last 18 months which has really helped us scale up a large lot of our capabilities in the back yeah I'd love if you could explain a little bit more on that it you know challenging times you know I'm curious the amount of people that are using your services probably haven't changed but the demand and how much they're using it as change a lot so cloud obviously gives you scalability but you know are there concerns about what this does the profitability how you maintain things how much of this is a temporary change and how much will this be you know I know in the United States there's a lot of talk about how much work from home will become more of a standard than it had been before this pandemic so you know short term what's the impact on your business and what are you and other telecommunication companies thinking about what long-term impact this will have >> I think that's a very very interesting question I think even for me and my organization what we have been able to do working from home is amazing I never would have thought that it was possible to do as much as we've been able to do just staying young with most of the work for staying at home and that has really I think happened across industries across the entire country I think many organizations have now realized that work from home or work from anywhere which is the other term he's gonna become quite possible and prevalent going forward because people have realized that you can just get you can get just as much productivity out you can get so many things done working from home and it gives so much more personal flexibility to the individuals so I see when I look back at our organizational experience I see our productivity has been actually quite good actually better then haha where probably even in the office days so I think that is definitely one thing that is gonna come out as a global change across all industries I think the second thing that is gonna happen is data analytics I think there is going to be far more analysis of data to understand patterns and understand trends and how to take advantage of that I think of course the immediate application is in the healthcare and the spread of the pandemic but I think this will spur a lot of other analytics I think the third thing is going to do is the adoption of digital as the primary mode digital was already something that most companies are working on as is a top priority but I think going outward is gonna become very evident to people that it is actually essential just talking about my business I can tell you today you know all the stores all the shops every place that we used to check our cell or recharge vouchers are closed so the only place we are able to get any revenue from is our digital channel and on end only place where customers have been able to recharge their prepaid subscriptions etc has all been through digital I think digital we will also become a massive massive requirement so in that context I think telecom will be seen as a critical critical backbone I think to a large extent it has been seen by many in the past is more of an essential commodity but I think many organizations will realise that this is actually a value creator so I think it's a great exciting opportunity for us to take advantage of those new business opportunities that will come and at the same time be a very very important player in the digital economy that every nation around the world is gonna press you know for Sean said it really appreciates some really good commentary there you know we've been talking for years about customers going through their digital transformation it's really about the data and how they leverage that and if you're data-driven then you really have gone through that transformation and you kind of described what we call the new innovation cocktail you're leveraging cloud that there's data you put those all together as to how you drive your company and you can drive innovation oftentimes when we think about what results we're going to get from deploying cloud and using these types of new technologies we think we know what we're gonna get but the reality of how your company is dealing with things today of course you know proves what you were hoping that build for here help us understand you know what we're talking here is part of red hat summit this week you know what's red hats role in this piece and you know how did the reality of rolling this out and then how it has helped you in the current global situation impacted your business sure oh so I would say actually the three words that I used digital cloud and analytics to me they're actually inseparable cuz I do not believe that you can have a digital business that is not based on cloud or that is not good at data analytics I think if you want to really have a successful cloud offering it implies that automatically that you are a digital business and you're gonna do extensive modern data and analytics and build those capabilities I think those are three inseparable terms now speaking specifically about a red head I would say that red head has been a very very critical partner for us right from the beginning 18 months ago when the two companies too came together to create this network we knew that we had to do several things number one was actually to have a completely rationalized structure which was around extracting the synergies from the from the merger but beyond that we needed to build a telco of the future technology company of the future which will let us transform the business and create capabilities that will give us a step ahead a leapfrog ahead of our competition and cloud was a very very essential part of the journey and we knew we needed to build a cloud based on open systems because we did not want to get into a proprietary logins with anybody and we are a very large business we have suffered a sufficiently large scale to really be able to build a very large cloud so we started working with Red Hat about two years ago and it in the last two years we have deployed 80 plus cloud locations distributed cloud locations across the country and these all of these clouds our vision is to orchestrate them as a single cloud our vision is to build a cloud there is a universal cloud actually that is the word there is a word we use when we talk about cloud it's a universal cloud what does that mean that means that cloud will carry not only the traditional telco workloads but it will also carry IT workloads it will also carry lot of the enterprise offerings we have so - for the end-user for our enterprise clients and all of those capabilities out to be accommodated with a platform that is versatile that is scalable and that is gonna give me in enormous amount of flexibility and control as a organization so Red Hat has been a very important part of the journey and on the red head OpenStack cloud today I have a Daffy's working from any major supplier you can think of I have any enemies working from Nokia Ericsson Huawei ziti even some smaller players like Marvin here so we have demonstrated that this is possible we've been able to break the lock in that the traditional naps have had on their cloud offerings which were really more of a virtualized offerings rather than a cloud computer is a truly universal cloud on the back of the technology provided by a red well that's that's fantastic congratulations on that I love the the result of what you're calling Universal Cloud is the promise that we talked about for a number of years you know is that nitty gritty networking piece it was like you know network functions virtualization and if be sitting an open stack and everybody's like well OpenStack am I trying to build a cloud to compete against the public cloud providers it was like no what you said exactly there's services that you want to be able to deliver and it's not just about oh we're getting away from hardware appliances it's you know just like most people today they're used to whatever smart device they're doing I want to be able to turn on channels and access new things that's your now you know reducing that barrier to Vodafone idea to deliver that to your users have I captured that properly that is correct as a matter of fact I'll just give you one proof point my water phone app is the app that we we have for our consumers and that app is currently running on my telco clock what used to be called the telco cloud so on that platform we are running my packet or actually there are about 40 and FB is for virtualized traditional calculations running alongside with an IT application a digital application okay so one of the things I you know I would like to understand there that what you've deployed there over the last couple of years sounds like a significant shift so you know you're talking about apps you're talking more of a developer type of environment bring us inside a little organizationally you know what new skills have new people had to learn has there been new people added to the organization have there been in a restructures what what is this this this whole initiative to get to universal cloud meant for your organization sure so I look after both the network and IT pieces of the part of parts of the company and you know we traditionally were in the past legacy we have had a IT cloud and we have heard indigo cloud what we are now creating is a single universal cloud what either of the two workloads are gonna be facilitated so for that actually the two organization the two parts of the organization need to come together and start to really work as one now it is very important that the telco guys understand the scale and the 99-year the five nines required in a running a network but at the same time IT guys also understand very much what all of the the flexibility that the business requires and the responsiveness required for the for the enterprise so bringing those two talents together I think in infusing that to create a single organization is one of the biggest challenges I think any telco has we also face it that is one aspect of it the second aspect of it is that there just aren't too many cloud experts in the world and we have been struggling with that I think skill shortage is a clear challenge for us now we try to address it using variety of means we of course try to upscale rescale lot of the traditional network core engineers that we have had we also try to use talent available or from consultants and then we also try to use our vendors so one of the concepts we've been working with our vendors is a concept of a resident engineer so we try to actually get them to second some of their engineers to work with us and at the same time we've been now working with both IBM and redhead to create a program to really go out and create a community around us of developers who can really work with this cloud and therefore we will have enough of skills available to leverage all of the potential benefits there are then the platform but can only be unleashed if I have the right skills and right people you touched on a very important issue it is a challenge but we are working our way through it and so far we've been a bit we make good all right well if it's shot I can't let a CTO go without looking a little bit into the future so want to help understand we talked about some of the technologies talked about transformation of what's happening your business what's happening your organization and there's some big waves coming week you know cloud is still in early days 5g of course you know is expected to have massive impact on on everyone's environment for this so what is the winning formula for the the telecoms going forward well I think Phi G is an exciting world we are a 4G network today the Phi G spectrum hasn't been auctioned in India but what we are building today is what I call a 4G plus network which means the lot of the architectural principles of PI G we have already applied in my core networks today and in my transport network in that world I think IOT is gonna play a very very big role and if you want to do things like IOT and if you want to do things like blockchain now I think telco cloud has a huge role to play because we are the telcos are traditionally the only ones in a country anywhere in the world who have experiences experience in operating in very far front powerful places dealing with lot of the infrastructure challenges especially if you're in a developing country you know that you have to work with a poor power availability poor transport etc I do not see any of the big guys the the big cloud players really having those capabilities today I think telcos are gonna play a very big role in enabling that pi g io t work and it is going to be an exciting journey for telcos I think telcos will very soon be called tech companies that is one thing that I strongly believe in I think also many of the things that depend on blockchain will require the kind of cloud that telcos will create because a telco cloud is far more demanding than a traditional IT application in many ways for example latency or for example throughputs now all those things aren't very important in blockchain apple type of applications I think that's another exciting opportunity for telcos really is to get into that and of course there are discussions about smart cities smart government government and because of Kovach kharkova crisis I think many governments are gonna explore new ways of organizing Society's new ways of governing economic activities and the backbone for a lot of those things is gonna be our telecom networks and the cloud distributed clouds to the edge that we create so I think it'll create many many exciting business opportunities as a consequence of some of those technological innovation yeah Shanta I can't remember who said it as they said don't waste a crisis but Vasant Bora CTO of Vodafone idea pleasure talking with you thank you so much for joining us hope you enjoy the Red Hat event as it is distributed this year and definitely look to be able to meet you sometime at a future physical event back when we have those in the future Thank You Stu it's been a pleasure meeting you virtually and look forward to these all right lots more coverage from the cubes Red Hat summit at 20/20 activity I'm Stu minimun and thanks as always for watching [Music]

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

>>from around the globe. It's the Cube with digital coverage of Red Hat. Summit 2020 Brought to you by Red Hat. >>Hi, I'm stupid, man. And this is the Cube's coverage of Red Hat Summit. Of course, it's happening digitally. We're interviewing Red Hat executives, customers and partners from around the globe who can are gonna be part of this event. And happy to welcome back to the program. One of our Cube alumni, Joe Fitzgerald, who is the vice president and general manager of the management business unit at Red Hat. Last time I caught up with Joe is that answerable fest last year. And, uh, Joseph, fourth year in a row, You've been on the Cube here at Red Hat Summit. Thanks so much for joining us again. >>Thanks for having me back. Still, I'm happy to be here, >>All right, So, Joe, I think it actually makes sense for us to kind of pick up the conversation where we left off and answer both best last year, so answerable fast. It's all about automation. You're really helping with digital transformation. What companies are going through in today's day and age automation and being able to be more agile. Of course, everybody, for the most part, is working from home, being able to enable things remote. The adoption of cloud is even more consideration. So what part there? And since we last talked, you know, obviously things have changed for everyone some, but give us the latest from your organization. >>Thanks to you know, when we met and so fast in Atlanta last fall, we were talking about strategic use of our nation. Um, in today's current crisis, if you will. There's a lot of folks who are leaning on automation in a much more immediate and tactical way. We're seeing a lot of automation being used by folks to the boy, either the infrastructure they need to deal with capacity and surge demand that they have. Right now, we're seeing people use it for things like working from home because they can't get access to gear we're seeing for bursting to public clouds because they can add more physical equipment, perhaps in the data center. So last year we were excited to talk to you about strategic automation. That's still really important. But right now a lot of folks have more pressing matters in terms of automating to get through the current crisis coming to you from northern New Jersey, which is certainly a hot spot on, but certainly a lot appreciation for the folks on the front lines. They're taking care of us and protecting us and things like that. We want to do everything we can as a company, as red hat, to enable folks to do whatever they need to do to be able to get through this crisis. >>Yeah, absolutely. Joe Ah, very important topics there. In the keynote for Red Hat Summit, there's discussion of your group, and of course, management has always been a critical piece of how we look at overall i t. When I first became an analyst, the joke was, Well, you know, security and management. We can always kind of okay, those pillars is two things we need to do is an industry to make things better. Ah, specifically, we've been talking for years about the growth of container ization and kubernetes. Of course, Red hat, strong leadership position with open shift. My understanding that if I heard right from the keynote, it's the advanced cluster. Management is the new piece. Can you give us a little bit about, you know, the team, the technology, how this fits into the overall red hat portfolio. >>Sure, so we're super excited around advanced cluster management. It turns out that you know, we have a lot of customers that are running open shift to other container based applications, and as they evolve, they inevitably end up with multiple clusters based on separation of duties or lines of business, perhaps for distributed availability zones and things like that with their clusters, so they inevitably back into a multi cluster scenario. What we've done is working with IBM would develop some very rich technology around advanced management for multi cluster environments built from scratch for container environments and kubernetes. We worked with IBM. We move that technology over to Red Hat. But when the process of doing two things one is we're announcing tech preview here at Summit of that technology and where the process we're open sourcing that technology because we're red hat and everything we do is open source. We're going to take some of the most advanced container management cluster management technology in the world that we've gotten from IBM, and we're going to open source that we're excited here is that we're gonna provide this red hat, offering advanced cluster management to help people who are struggling with managing clusters. >>Yeah, Joe, absolutely a super important point point. Anybody that's watched this space for the last few years, simplicity has not been the word that people have used for it. And over the last year there's been a lot of announcements from some of the major players in the industry about how do I manage those multiple cluster environment? So, Joe, if I think back two years ago Ah, it was, you know, here's the best way to run kubernetes. And when you talk to a lot of customers, it was well, they were starting with often spinning their own because that was what was available. And the number one choice that I usually heard from customers was, Oh, if I'm a Red Hat customer, started using open shift and start using open ships everywhere, fast forward to where we are today. Of course, you have lots of customers running open shift, but also in the public clouds. If I'm using Amazon, Google, Microsoft, other platform environments, often there's a native kubernetes, and I need to manage across those environments. So do I understand right? ACM Is that going toe? Help me not only with my open shift but as it moves forward. Also, manage some of those other kubernetes environment. And how does Red Hat approach this kind of the same or differently? From what I hear from from Microsoft with Arc with VM Ware with Andrew >>So ACM vessels Management from Red Hat supports any standard kubernetes environment. One of the advantages we have working in an open shift environments Open shift has a lot of functionality sides Kuban aids. In other words, it's already a layer of sophistication built on top of kubernetes, so open shift itself provides a lot of management automation. Now you had advanced cluster management on top of that, which will be able to import other communities clusters from other environments. But the ability for its take advantage of the sophistication that's already in open shift and then leverage things like Hansel Automation and then some of the management. SAS Services cloud at red dot com We're connected customer experience the ability to proactively look at open shift clusters and be ableto some cases tell people about problems they're having before they even realize they have the problem. That combination of management automation on top of the already rich open shift environment really puts us. A couple of you know, runs up in terms of capabilities. I'll be on a standard kubernetes vanilla. Our >>yeah, so one of the reasons I was looking forward to this conversation is one of the things that we've been looking at for the last few years is how is multi cloud the same or different from what we have done back, You know, 10 15 years ago with multi vendor. And I think anybody that's been around long enough and you talk about management in a multi vendor environment and you think about the leading tools from a software standpoint. We're out there and it gives us a little bit of flashbacks, and it's not. Not in a good way. So what have we learned as an industry? And, you know, you talked about it, you know, integration with answerable all the automation, you know, how do we make sure that we aren't repeating the sins of the past with these new generation of management tools? >>Well, what we've seen is that enterprises are inherently going to be hybrid and multi cloud red has been talking about open hybrid cloud for almost eight years. Right? So our CTO Paul Cormier, you know, sort of anticipated this, which was pretty insightful eight years ago because everybody thought and people gonna move exclusively cloud it would have any data centers and maybe hardware anywhere. That's why you've got data centers edge multiple public clouds with services that are all over those different footprints. We believe that, you know, unlike the past when you had heterogeneous systems management, right where you have different platforms that we're trying to manage is the lowest common denominator is a common platform. Now what Red hat is offering is open shift, which will run on all the public clouds, as well as on your physical and virtual hardware in the data centers at the edge. So it basically provides the consistency, which means that the management can then talk to a consistent environment, provided much higher level hybrid cloud management and trying to either have silos of different management tools by cloud by vendor by environment, um, and then try to Federated at the lowest common denominator. You'll see kubernetes management tools, for example, that have to use the lowest, you know, sort of common denominator, which is the straight kubernetes AP eyes. We could take advantage of those, but also the additional functionality That open shift brings in, for example, with the other kids abilities. It allows us to have a higher level of management but provide that consistency by having the same hybrid cloud platform this case. Coburn's shift run across those different environments. >>Yeah, so what? One of the things that also consumer concerns me a little bit as the industry when they talk about kubernetes. It's very much a discussion of the infrastructure piece, but we know this move to cloud native is very much about the application and the application development. So help me understand a little bit how that overall story for kind of the app Dev see I CD all those pieces fit into your story. I was one of the major points of discussion. You know, the best. >>Yeah, so So it is really all about the application. People really don't want to think about the infrastructure. They don't think about the application. That's really what's driving their business and their differentiation in the case of open shift, but open shift provides application. Lifecycle management for kubernetes environments are advanced. Cluster management sort of takes that a step further and allows you to extend that life cycle so that you can deploy applications based on policy to different environments based on your needs. Keeps compliance. All those things enforce regardless of how many different places the traction application. So it's not just a Z Z as taking an application to going into one location. People want to be able to continuously update their applications and deploy it to all of the places that it needs to be there based on availability, a proximity security environments and things like that represents a hard challenge. And so that's why some of the tools, like Advanced cluster Management, are exactly designed to help those kind of new applications. Yeah, >>all right, Joe, you talked about that. Some of the technology for for ACM came from the IBM side. Give us the update. When you look at the IBM Cloud portfolio, how is your group really interacting and supporting and working with the overall IBM solutions? >>So IBM has a very robust portfolio and they have you know a number of the cloud packs in their portfolio that address things like applications and data management, things like that. So IBM, in this case, I developed some advanced cluster management technology, but it was not open source. It wasn't available to other folks. One of the challenges with that is that we believe, as red Hat that the innovations happening in open source. If you develop something in a closed, proprietary way, maybe the best thing in the world today, a year, two years, three years from now there are other projects and there are other technologies have being collaborated on open that are going to make. But we leave you behind, right? So we think open is the future. So in this case, and working with IBM, we took some very advanced technology. We moved it over to Red Hat, and now we're in the process of open sourcing it, as well as providing an enterprise consumable version. More technology in Red Hat Advanced Cluster Management for kubernetes, IBM again has to support a much broader, diverse environment, right in terms of everything from mainframes to edge and containers and V M's and physical machines applications that span decades, So they have a much bigger sort of, you know, target environment that they have to work in. Red Hat's focused on the future. We're really sort of skating to where the puck is, if you will use a you know, hockey analogy where basically, we're trying to anticipate what enterprises are going to need and address that with not only the platforms with management automation, you're going to need to be successful with the cloud. >>Yeah, Joe, I want I want you to bring it into your customers and you talk about all these changes that are happening in the landscape and how they manage it. Any insight you can give as to, you know, organizational structures. You know, I remember last year at Summit I talked to a number of companies going through digital transformation. And, you know, we know that there is as much if not more organizational change that needs happen along with the technology pieces. So from your world, you know who's kind of leading the charge, what skill sets do people need to either, you know, bring to it or learn new on And you know, our companies, you know, taking advantage of >>Well, as they say, developers are sort of the new kingmakers, right? In some ways. And so you know the tools that you've always said people process and technology, right? And I know as software companies get very, very excited about technology, but it turns out that the people, the process here way people building their applications, Way Dev ops and see I CD. It's a very, very sort of different environment for management automation tools, you know and sort of. The relationship between teams has changed and will change more, by the way. And so one of things we're trying to do. You see this with answerable, but you're also seeing this with Advanced Cluster Management is ability to delegate and give different kinds of operational and management capabilities to the teams, whether it's like business developers, QE teams. So it's fundamentally changing the way that the processes were working. That requires that the tools map to those new team structures. There's no new processes on, and that's what I think's going on it fundamentally different, and one of things I think you're going to see is management tools that were built in the past for these were the old style organizing are not going to fare well in the new World, where these processes and the team structures are changing. >>All right, So, Joe, before I want to get some feedback from you on how your technologies and teams they're helping with the code 19 piece. But let's just wrap up the ACM discussion before we do that. So you said it's a tech preview. S 01 of things that really nice is when you move things to open source, the community gets pretty good visibility as to when things were getting releases. New features down the pike. So what should we be looking for as an industry for ACM? When that rolls out, how two people start getting their hands on it and you know, what does that look like? >>So there's really two paths there. One is from a tech preview point of view. You know, customers can get access to the technology right and see it in their environment and give us feedback. The fact that it's been developed for the past two years probably constitutes hundreds of years of developer, um, you know, time in it. It's not Alfa technology. It's pretty robust. So even though we're calling a tech preview, we anticipate that it's going to be production ready in short fashion. It will take us a little bit of time to open. Source. The technology's red hat has a history of open sourcing technologies that we acquire. Each one varies in terms of what's in the code licenses, how it's structured, how it should be open source. We just don't back the truck up and take a bunch of code and put in a repository is actually a thoughtful process about the way that's projects or set up a communities they should be in. We're going through that process now, but customers will be able to take advantage of it in short fashion, and I think they're gonna find a very high level of maturity, given how long and how much. I mean it's work of this, >>you know, a really important piece is there. The other one closed the discussion with how we started off. Obviously, you know, workers and companies are having to make changes and be more flexible than ever in response to the Kobe 19 endemic. What are some of the pieces of technologies and services Ah, that that you want to highlight as toe that are helping companies really adjust to what is happening in today's world. >>Well, Red Hat is always been a very conscientious company. And in my particular area, one of things we're doing is with sensible. We're trying to enable folks to use automation providing free workshop, free workshops and access to code playbooks and things for different environments. If you think about the different kinds of industries right now, some are struggling with no smaller workforces work at home. Other ones are under tremendous pressure to deliver services to help keep us safe and protect us. So we're trying to provide as much a so we can in terms of automation, enabling people to use free, open source innovation on automation to enable work from home to do everything from creative TVNZ toe, you know, set their statuses and communicate between teams in this new environment, but to burst into a lot of clouds in some cases because somewhere trying to scale because their business is now change but is under tremendous pressure. You see that delivery services and things like that. So we're trying to to help as much as we can with automation is something that could be immediately helpful and has been some of these other projects. You know, somebody's doing a transformation, and they're designing new applications as much longer. Burn to it. Whereas automation is needed today by companies under duress, you can help them accelerate, um, and connect the their their new work at home environments. Sweetie Automation. Helping a lot. The other thing I want to mention is that we have free capabilities like red hat insights that can actually access systems for security. The last thing you need is a security breach or some other problem. Why you're dealing with fighting fires. There are bad actors out there. We've seen a few already eso insides ability to look at systems and tell people what their current posture is. So they immediately, quickly, whether with our tools or some other tool they have. We're trying to do as much as we can to help our customers for this really tough time. >>Well, Joe, thank you so much for the updates. Ah, congratulations to the team on the progress and absolutely very important topics to help customers that need to react even faster than ever in today's time. Extra funding. I'm stew. Minimum lots more coverage from Red Hat Summit on the Cube. Check out the cube dot net. And thank you for watching. >>Yeah, yeah, yeah.

from around the globe it's the cube with digital coverage of Red Hat summit 2020 brought to you by Red Hat welcome back to the cubes coverage of Red Hat summit 2020 of course this year it's rather than all coming to San Francisco we are talking to red hat executives their partners and their customers where they are around the globe happy to welcome back one of our cube alumni Lisa Spellman who's a corporate vice president and general manager of the Intel Xeon and memory group Lisa thanks so much for joining us and where are you joining us from well thank you for having me and I'm a little further north than where the conference was gonna be held so I'm in Portland Oregon right now excellent yeah we've had you know customers from around the globe as part of the cube coverage here and of course you're near the mothership of Intel so Lisa you know but let's start of course you know the Red Hat partnership you know I've been the Intel executives on the keynote stage for for many years so talk about to start us off the Intel Red Hat partnership as it stands today in 2020 yeah you know on the keynote stage for many years and then actually again this year so despite the virtual nature of the event that we're having we're trying to still show up together and demonstrate together to our customers and our developer community really give them a sense for all the work that we're doing across the important transformations that are happening in the industry so we view this partnership in this event as important ways for us to connect and make sure that we have a chance to really share where we're going next and gather feedback on where our customers and that developer community need us to go together because it is a you know rich long history of partnership of the combination of our Hardware work and the open-source software work that we do with Red Hat and we see that every year increasing in value as we expand to more workloads and more market segments that we can help with our technology yeah well Lisa you know we've seen on the cube for for many years Intel strong partnerships across the industry from the data centers from the cloud I think we're gonna talk a little bit about edge for this discussion too though edge and 5g III think about all the hard work that Intel does especially with its partnership you know you talked about and I think that the early days of Red Hat you know the operating system things that were done as virtualization rolled out there's accelerations that gone through so when it comes to edge in 5g obviously big mega waves that we spend a lot of talking about what's what's Intel's piece obviously we know Intel chips go everywhere but when it comes to kind of the engineering work that gets done what are some of the pieces that Intel spork yeah and that's a great example actually of what I what we are seeing is this expansion of areas of workloads and investment and opportunity that we face so as we move forward into 5g becoming not the theoretical next thing but actually the thing that is starting to be deployed and transformed you can see a bunch of underlying work that Intel and Red Hat have done together in order to make that a reality so you look at they move from a very proprietary ASIC based type of workload with a single function running on it and what we've done is drive to have the virtualization capabilities that took over and provided so much value in the cloud data center also apply to the 5g network so the move to network function virtualization and software-defined networking and a lot of value being derived from the opportunity to run that on open source standard and have that open source community really come together to make it easier and faster to deploy those technologies and also to get good SLA s and quality of service while you're driving down your overall total cost of ownership so we've spent years working on that together in the 5g space and network space in general and now it's really starting to take off then that is very well connected to the edge so if you think about the edge as this point of content creation of where the actions happening and you start to think through how much of the compute or the value can I get out at the edge without everything having to go all the way back to the data center you start to again see how those open standards in very complex environments and help people manage their total cost of ownership and the complexity all right Lisa so when you're talking about edge solutions when I've been talking to Red Hat where their first deployments have really been talking to the service providers really I've seen it as an extension of what you were talking about network functions virtualization you know everybody talks about edges there's a lot of different edges out there the service providers being the first place we see things but you know all the way out even to the consumer edge and the device edge where Intel may or may not have you know some some devices there so help us understand you know where where you're sitting and where should we be looking as these technologies work you know it's a it's a great point we see the edge being developed by multiple types of organizations so yes the service providers are obviously there in so much as they already even own the location points out there if you think of all the myriad of poles with the the base stations and everything that's out there that's a tremendous asset to capitalize on you also see our cloud service provider customers moving towards the edge as well as they think of new developer services and capabilities and of course you see the enterprise edge coming in if you think of factory type of utilization methodologies or in manufacturing all of those are very enterprise based and are really focused on not that consumer edge but on the b2b edge or the you know the infrastructure edge is what you might think of it as but they're working through how do they add efficiency capability automation all into their existing work but making it better so at Intel the way that we look at that is it's all opportunities to provide the right foundation for that so when we look at the silicon products that we develop we gather requirements from that entire landscape and then we work through our silicon portfolio you know we have our portfolio really focused on the movement the storage and the processing of data and we try to look at that in a very holistic way and decide where the capability will best serve that workload so you do have a choice at times whether some new feature or capability goes into the CPU or the Zeon engine or you could think about whether that would be better served by being added into a smart egg type of capability and so those are just small examples of how we look at the entirety of the data flow in the edge and at what the use case is and then we utilize that to inform how we improve the silicon and where we add feature well Lisa as you were going through this it makes me also think about one of the other big mega waves out there artificial intelligence so lots of discussion as you were saying what goes where how we think about it cloud edge devices so how does AI intersect with this whole discussion of edge that we were just having yeah and you're probably gonna have to cut me off because I could go on for a long time on on this one but AI is such an exciting at capability that is coming through everywhere literally from the edge through the core network into the cloud and you see it infiltrating every single workload across the enterprise across cloud service providers across the network service providers so it is truly on its way to being completely pervasive and so again that presents the same opportunity for us so if you look at your silicon portfolio you need to be able to address artificial intelligence all the way from the edge to the cloud and that can mean adding silicon capabilities that can handle milliwatts like ruggedized super low power super long life you don't literally out at the edge and then all the way back to the data center where you're going for a much higher power at a higher capability for training of the models so we have built out a portfolio that addresses all of that and one of the interesting things about the edges people always think of it as a low compute area so they think of it as data collection but more and more of that data collection is also having a great benefit from being able to do an amount of compute and inference out at the edge so we see a tremendous amount of actual Zeon product being deployed out at the edge because of the need to actually deliver quite high-powered compute right there and that's improving customer experiences and it's changing use cases through again healthcare manufacturing automotive you see it in all the major fast mover edge industries yeah now we're really good points they make their Lisa we all got used to you know limitless compute in the cloud and therefore you know let's put everything there but of course we understand there's this little thing called the speed of light that makes it that much of the information that is collected at the edge can't go beyond it you know I saw a great presentation actually last year talking about the geosynchronous satellites they collect so much information and you know you can't just beam it back and forth so I better have some compute there so you know we've known for a long time that the challenge of you know of our day has been distributed architectures and edge just you know changes that you know the landscape and the surface area that we need the touch so much more when I think about all those areas obviously security is an area that comes up so how does Intel and its partners make sure that no matter where my data is and you talk about the various memory that you know security is still considered at each aspect of the environment oh it's a huge focus because if you think of people and phrases they used to say like oh we got to have the fat pipe or the dumb pipe to get you know data back and or there is no such thing as a dumb pipe anymore everything is smart the entire way through the lifecycle and so with that smartness you need to have security embedded from the get-go into that work flow and what people need to understand is they undergo their edge deployments and start that work is that your obligation for the security of that data begins the you collect that data it doesn't start when it's back to the cloud or back in the data center so you own it and need to be on it from the beginning so we work across our Silicon portfolio and then our software ecosystem to think through it in terms of that entire pipeline of the data movement and making sure that there's not breakdowns in each of the handoff chain it's a really complex problem and it is not one that Intel is able to solve alone nor any individual silicon or software vendor along the way and I will say that some of the security work over the past couple years has led to a bringing together of the industry to address problems together whether they be on any other given day a friend or a foe when it comes to security I feel like I've seen just an amazing increase over the past two two and a half years on the collaboration to solve these problems together and ultimately I think that leads to a better experience for our users and for our customers so we are investing in it not just at the new features from the silicon perspective but in also understanding newer and more advanced threat or attack surfaces that can happen inside of the silicon or the software component all right so Lisa final question I have for you want to circle back to where we started it's Red Hat summit this week-long partnerships as I mentioned we see Intel it all the cloud shows you partner with all the hardware software providers and the like so big message from Red Hat is the open hybrid cloud to talk about how that fits in with everything that Intel is doing it's an area of really strong interconnection between us and Red Hat because we have a vision of that open hybrid cloud that is very well aligned and the part about it is that it is rooted not just in here's my feature here's my feature from either one of us it's rooted in what our customers need and what we see our enterprise customers driving towards that desire to utilize the cloud to in prove their capabilities and services but also maintain that capability inside their own house as well so that they have really viable work load transformation they have opportunities for their total cost of ownership and can fundamentally use technology to drive their business forward all right well Lisa Spellman thank you so much for all the update from Intel and definitely look forward to seeing the breakouts the keynotes and the like yes me too all right lots more coverage here from the cube redhead summit 2020 I'm Stu minimun and thanks as always for watching [Music]

>> Announcer: From around the globe, it's theCUBE, with digital coverage of Red Hat Summit 2020, brought to you by Red Hat. >> Welcome back to theCUBE's coverage of Red Hat Summit 2020. I'm Stu Minneman and, of course, this year, the event is really happening globally where people are. So, we're talking to Red Hat executives, their partners, and we're always thrilled when we get to talk to the customer. So, joining me, from Buenos Aires, Argentina, I have Maria Alehandro-Trosee, who is the Deputy Manager of Solutions Architecture at Edenor. Alejandra, thank you so much for joining us. >> Oh, thanks to you, of course. I am pleased to be here. >> All right, so we know we are living in some challenging times right now. Certain things become very important. Everybody is working at home. Of course, Edenor is energy. So, talk about something that is essential. You look at Maslow's hierarchy, want to make sure everyone is healthy and, pretty soon after that, your company is making sure that things get running. So why don't we start with a little bit, Edenor. Tell us a little bit about the company, and your role in the organization. >> Yeah, of course, of course. Well, Edenor is the largest electricity company of Argentina with almost 5000 employees and three million customers, in parts of Buenos Aires city and surroundings, too. It represents a 9-million population. And we have the residential, commercial and industrial customers. So, we bring electricity to homes, to schools, to hospitals, to airport. And well, of course, commercial and industrial customers that are in our concession area. >> Excellent. Great, and solutions architecture. So tell us a little bit about your role there, or purview of your group. >> Well, I am part of the information systems, of the technology information direction in Edenor. And, as the solution architecture area, we are helping to establish good architectures for business objectives. For the business to meet the objectives in a very, or in the best quality, and in the best way. We are seeing how the trends, how technology moves, how industries, similar industries and companies are moving, beyond technology and architectures, and we try to go this way for the company. >> Great. So, just so I understand. So is that this infrastructure piece? Is cloud part of the mix? Where is your connection to, really, the business applications? Any developers, you know? >> Yes. I usually think about it as the glue. As the glue that join our pieces together. Applications, infrastructure, and the business that makes a solution. It involves software, but it depends on power, it depends on infrastructure, security and so on. There is an infrastructure area, a security area, a solutions area. In I.T. too. Now our I.T., too. And architecture is one of them, and we try to glue all these pieces to meet requirement. >> Yeah. I love you give that analogy of the glue, bringing things together. >> (laughs) Yeah. >> We know there, you know, the pace of technology continues to change so fast. The requirements of the business don't stand still. So, bring us inside. Help us to understand some of the integration challenges you're facing. What drivers of the business are causing you to evaluate what you're doing. And tell us a little bit about what you're using, today. >> Yeah. Well, we have had a lot of challenges. Some time ago, we had lots of integrations running. And I think that I usually see, see these challenges in several ways. The integrations that we are running, and we are having trouble. We are having a a lot of issues. Maybe issues in data, in quality, and in performance or viability, too. And, most of these issues were because of online transactions that, maybe started to grow, much more, and started to add some complexity to the system platform that was almost for batch processing. So we have a huge amount of LAN integrations, that started to be big, to be big in volume, to be critical for the business. Any maybe we don't have, we didn't have the right picture. We had to do it, a lot of hand craft job, with a lot of work force behind. A lot of micro-batches and so on, to keep things running. But with a lot of effort behind that. >> Yeah. >> Yeah, tell me. >> Yeah. Just, you know, very typical challenges that I am hearing from you. Help us understand, you know. How do you choose the technology partners that you're working with? You know, it is the paradox of choice out there. There are so many companies, so many products. You know, especially you company. You've got the DevOps pieces. I look at the DevOps tool chain today, and it is more than any one person can comprehend. So, how does Edenor approach, you know, who you integrate with? And choose the various pieces? >> Okay. Well, the center of the evaluation, or the decision, was integration. Of course, the center of the evaluation process, and the research, was about integration. But we wanted an integration platform or to be, as an architecture, an integration architecture that could solve all of the issues that I mentioned before. All of the issues that we had. But that could take Edenor to a next stage. That prepare us for what, in that time, we could see as the future of departments. And nowadays, they are almost, actual departments. But, at that time, two years ago, we are some kind of future requirements, like DevOps, micro services, APIs, and the cloud. Well, the cloud requirement was one of the first that we managed at IT. The new concept, for Edenor. And we had to manage all of that. Some platform that prepare us for all that were coming, and for cloud or high-width architecture. So, we started our research, and we found, in Red Hat, an excellent technology. But this is a technical aspect, and the other aspects that we looked for, were the experience in the region. You know, maybe there are a lot of technologies that could be great, but maybe unrepresented in our region. It's not just a case of integration, because integration platforms, the biggest, or the best integration platforms, I think they are mostly clear. But, with many technologies, it could happen that, maybe there are good technologies, but not with some presence in our local region. Adding that, I would say that experience in similar industries, and a presence and, most important for us, I mean, was, pretty well, it works really well. A supportive way of working. That the company could support us. Support all along the project. Not just the possible additional support, but also, support for all the journey. All the learning process, all the implementation process. We could find all of these in Red Hat. Of course, that's why we chose it. >> Absolutely. So, Alejandra. Tell me, where are you with the roll out of what you are using with Red Hat? What have you put into it? Give us where you are so far. >> Well, we started with an initial phase, a pilot phase, where we chose some initial services that were not so complicated, not so complex, not so critical. But, with a good sample of what we have, in terms of protocol, in terms of patterns, in terms of connectors with other systems. So we started with a kind of sample of all of that. And not, making some changes, making changes in the way of working. It's something like, well okay, let's go and try the technology. Let's put some first services, and let's learn. One of the services was not-so-complicated, but just had a lot of volume, a lot of transactions. We have almost 800,000 events per day, with that service, and was maybe the one of the most important, of that initial phase, in terms of scalability. And we could test it and see the bright of the technology, with that pilot. >> Excellent. And so what's been the result inside the organization? Has that impacted development time? Is it something that your ultimate end customers would have any positive results, after you've rolled this out? >> Well yes. After we started, or we finished the initial pilot phase, we started another phase, that consisted in a review, all the integrations, flows. And we knew which ones were the most critical, for the business, and have a lot of issues in the architecture, so we agreed with the rest of the team, solutions teams and business teams, just where to start to making real changes. So, another initiative started, that consisted in implementing a trial methodologies, in trying this on framework, for example. And we thought that it was a great combination, to try new ways of working, in this new phase of integration, with re-engineering. So, these new services, that we arrived. We are about, we are between the outage management system, the system that manages all of the technical reframe, of the electricity service, and the field management system. That is the system that manages all the work force industry, the logistics, or distributes the work, or in terms of priority. So all these flow, all of these flows are, increanals, are online flows. We have to send data, in simultaneously, just to change or to renew those priorities, all the time. To make a new schedule, and repair things better and faster. So, the business. I could say that the business and I, and our team, put a lot of increases in agility and speed. We could solve issues faster. For example, I learned about outages that could flow in terms of seconds, rather than in minutes. And, the development processes that fix. We could fix problems in production, maybe in a day, when sometimes we took weeks. So, we could find things like that, but with a new way of working, too. That could take all of the technology could being to us. >> Excellent. Well, when you talk about integration platform, traditionally middle ware, sits right in the middle between the infrastructure side of the house, and all of the app, you know, development pieces that you have. So, I am just curious. As you have rolled out the solution with Red Hat. Have there been any cultural change? You know, one of the things we have been looking at is, You know. Can tooling help bring teams together? You know. How much retraining do you need to do? How much fear and uncertainty is there, from groups? So, from an organizational standpoint. How has this gone inside of Edenor? >> Well. We have had a few huge changes. And I can mention some of them, or the most important. One of them was that we have to reorganize. Many teams have to reorganize their activities. Maybe it is not structural, or organizational chart situation, but functional. The way that the teams, maybe, organized their activity. We started to build a team where we have a project owner, a scrum master, Devs and architects from different providers, all on teams. And different specialties all working together, in the same space, with kind of dedication. I couldn't get full dedication. But yes, with a great dedication, that could give that team the autonomy, and the communication, and the collaborative space that we needed. So the teams, and managers of those teams, had to reorganize their activities. And it was possible, thanks to that. Thanks to them. But, the other aspect was that we have to learn, learn technology and learn new ways of working at the same time. And it's not just to have a training. This is an important aspect, but besides that, we have to incorporate all of these new concepts. This is a difficult, or the most difficult part, because we could do training and take courses. But we really, incorporate those new ways of working. It's really difficult. And we were, with you in the process, the team, helping the team. Just to, not to make a hybrid or something that is not the genuine. Because we wanted the genuine change, in the way of working, just to see better results. Then you, maybe we could get more flexibility, with time, with some level of maturity. But, in the first time. We saw, and our experts tell us, that it's better to attach to the pure sense of the way of working. A new way of working. So we have to incorporate all of that, to make a genuine change. >> Great. Well Alejandra. My final question, actually. I want to talk a little bit about community. So, you've been to Red Hat Summit before. Many of the things that you were talking about, and the change that you are going through. Many of the companies that I talk to. Of course, you know, the vendors are going to help you. Red Hat. They're partners. If you have a channel partner, they will help you. But often times, it is the peers in the community that are an important piece of this. That you can learn from others. You contribute back what you're learning. So, the question for you is. You know, this week, we're coming together while being apart at Red Hat Summit. So tell us how you engage with the community? The importance of Red Hat's ecosystem, and your peers in the community, around using these sorts of solutions? >> Well, I always said Red Hat people, Red Hat group that are near me, here in Argentina, and now with the U.S. guys, that I am really thankful of all of the Red Hat community. Because they've made real great things. It's really amazing to see the great technology that they could build as a community, as a whole community, in all the world. All around the world, people contributing, and coding technology. This is the biggest collaborative experience, I think, that we could see, and we could learn of. A very high collaboration, remote and very spread around the world. Really, a great inspiration for all of that, all of this, all of us. >> All right. Well Alejandra. Thank you so much for sharing your story, and all of the update with Edenor. And wish you the best of luck with the rest of the roll out of the projects you are working on. >> Oh, thanks to you for giving me this opportunity. It's a pleasure to talk to you. >> All right. Lot's more coverage from Red Hat Summit. I'm Stu Minnamen. And, as always, thank you for watching theCUBE. (gently chiming music)

>>from around the globe. It's the Cube with digital coverage of Red Hat. Summit 2020 Brought to you by Red Hat. >>Yeah. Hi. And welcome back to the Cube's coverage of Red Hat Summit 2020 on stew. Minimum in this year's event, of course, happened globally. Which means we're talking to Red Hat executives, customers and partners where they are around the globe on and happy to welcome back to the program. One of our cube alumni, Badani, who is the senior vice president. Cloud platforms at Red Hat is great to see you. >>Yeah, thanks a lot for having me back on. >>Yeah, absolutely. So you know, the usual wall to wall coverage that we do in San Francisco? Well, it's now the global digital, a little bit of a dispersed architecture to do these environments. Which reminds me a little bit of your world. So, you know, the main keynote stage. You know, Paul's up There is the, you know, new CEO talking about open hybrid cloud. And of course, the big piece of that is, you know, open shift and the various products, you know, in the portfolio there, So ah, personal. We know there's not, you know, big announcements of, you know, launches and the like, But your team and the product portfolio has been going through a lot of changes. A lot of growth since last time we connected. So bring us up to speed as to what we should know about. >>Sure. Thanks s Oh, yes, not not a huge focus around announcements, this summit, especially given everything going on in the world around us today. Ah, but you know, that being said, we continue our open shift journey. We started that well, you know, many years ago. But in 2015 and we had our first release both the stone kubernetes in a container focused platform. Ever since then, you know, we continue to groan to evolve Atlassian count now over 2000 customers globally. I trusted the platform in industries that literally every industry and also obviously every job around around the globe. So that's been great to see you. And last summit, we actually announced a fairly significant enhancement of a platform with a large fortune before big focus around created manageability ability to use operators which is, you know, kubernetes concept to make applications much more manageable. um, you know, when they're being run natively within within the platform, we continue to invest. There s so there's a new release off the platform. Open shift 4.4 based on kubernetes 1.17 big made available to our customers globally. And then really, sort of this this notion of over the air updates right to create a platform that is almost autonomous in nature, you know, acts more like your your your mobile phone in the way you can manage and and update and upgrade. I think that's a key value proposition that, you know, we're providing to our customers. So we're excited to see that and then be able to share that with you. >>Yeah, so a chef won't want to dig into that a little bit. So one of the discussions we've had in the industry for many years is how much consistency there needs to be across my various environments. We know you know Kubernetes is great, but it is not a silver bullet. You know, customers will have clusters. They will have different environments. I have what I do in my data centers or close. I'm using things in the public clouds and might be using different communities offering. So you know, as you said, there's things that Red Hat is doing. But give us a little insight into your customers as to how should they be thinking about it? How do they manage it? One of the new pieces that we're building it into a little bit, of course, from a management sand point is ACM, which I know open shift today, but going toe support some of the other kubernetes options you know down the road. So how should customers be thinking about this? How does Red Hat think about managing? Did this ever complex world >>Yes, So Student should have been talking about this for several years now, right with regard to just the kind of the customers are doing. And let's start with customers for us, because it's all about you know, the value for them so that this year's summit we're announcing some innovation award winners, right? So a couple of interesting ones BMW and Ford, um, you know BMW, you know, building It's next generation autonomous driving platform using containers. And then, you know, police Massive data platform an open ship for doing a lot of interesting work with regard to, uh, bringing together. It's a development team taking advantage of existing investments in hardware and so on, You know, the in place, you know, with the platform. But also, increasingly, companies that are you know, for example, in all accept. All right, so we've got the Argentine Ministry of Health. We've got a large electricity distribution company adopting containers, adopting middleware technology, for example, on open shift until great value. Right. So network alerts when there's electricity outrage going from three minutes to 10 seconds. And so, as you now see more and more customers doing, you know, more and more if you will mission critical activities on these platforms to your points to your question is a really good one is not got clusters running in multiple markets, right? Perhaps in their own data center, across multiple clouds and managing these clusters at scale, it becomes, you know, more, more critical up. And so, you know, we've been doing a bunch of work with regard to the team, and I actually joined us from IBM has been working on this. Let's remember technology for a while, and it's part of Red Hat. We're now releasing in technology preview. Advanced cluster management trying to solve address questions around. What does it mean to manage the lifecycle of the application process? Clusters. How do I monitor and imbue cluster help? You know, regardless of you know, where they run. How do I have consistent security and compliance for my policies across the different clusters. So really excited, right? It is a really interesting technology. It's probably most advanced placement. That's our market. What? IBM working on it. We know. Well, before you know, the team from from there, you know, joined us. And now we're making it much more >>widely available. Yeah, actually, I just want one of things that really impressed some of those customers. First off. Congratulations. 2000 you know, great milestone there. And yeah, we've had We're gonna have some of the opportunity to talk on the cube. Some of those essential services you talk Ministry of Health. Obviously, with a global pandemic on critically environment, energy companies need to keep up and running. I've got Vodafone idea also from India, talking about how communication service is so essential. Pieces and definitely open shift. You know, big piece of this story asst to how they're working and managing and scaling. Um, you know, everybody talks about scale for years, but the current situation around the globe scale something that you know. It's definitely being stressed and strained and understood. What? What? What's really important? Um, another piece. Really interesting. Like to dig in a little bit here. Talk about open shift is you know, we talk kubernetes and we're talking container. But there's still a lot of virtualization out there. And then from an application development standpoint, there's You know what? Let's throw everything away and go all serverless on there. So I understand. Open shift. Io is embracing the full world and all of the options out there. So help us walk through how Red Hat maybe is doing things a little bit differently. And of course, we know anything right Does is based on open source. So let's talk about those pieces >>Yes, to super interesting areas for us. Um, one is the work we're doing based on open source project called Kube Vert, and that's part of the CN CF incubating projects. And that that is the notion off bringing virtualization into containers. And what does that mean? Obviously There are huge numbers of workloads running in which machines globally and more more customers want, you know, one control plane, one environment, one abstraction to manage workloads, whether they're running in containers or in IBM, I believe you sort of say, Can we take workloads that are running in these, uh, give, um, based which machines or, uh, VMS running in a VM based environment and then bring them natively on, run them as containers and managed by kubernetes orchestrate across this distributed cluster that we've talked about? I've been extremely powerful, and it's a very modern approach to modernizing existing applications as well as thinking about building new services. And so that's a technology that we're introducing into the platform and trying to see some early customer interest. Um, around. So, >>you know, I've got ah, no, I'm gonna have a breakout with Joe Fernandez toe talk about this a little bit, but you know what a note is you're working on. That is, you're bringing a VM into the container world and what red hat does Well, because you know your background and what red hat does is, you know, from an operating system you're really close to the application. So one of my concerns, you know, from early days of virtualization was well, let's shut things in a VM and leave it there and not make any changes as opposed to What you're describing is let's help modernize things. You know, I saw one of the announcements talking about How do I take job of workloads and bring them into the cloud? There's a project called Marcus. So once again, do I hear you right? You're bringing V M's into the container world with help to move towards that journey, to modernize everything so that we were doing a modern platform, not just saying, Hey, I can manage it with the tool that I was doing before. But that application, that's the important piece of it. >>Yeah, and it's a really good point, you know, We've you know, so much to govern, probably too little time to do it right, because the one that you touched on is really interesting. Project called caucuses right again. As you rightly pointed out, everything that is open source up, and so that's a way for us to say, Look, if we were to think about Java and be able to run that in a cloud native way, right? And be able to run, um, that natively within a container and be orchestrated again by kubernetes. What would that look like? Right, How much could be reduced density? How much could be improved performance around those existing job applications taking advantage off all the investments that companies have made but make that available in kubernetes and cloud native world. Right? And so that's what the corpus project is about. I'm seeing a lot of interest, you know, and again, because the open source model right, You don't really have companies that are adopting this, right? So there's I think there's a telecom company based out of Europe that's talking about the work that they're already doing with this. And I already blogged about it, talking about, you know, the value from a performance and use of usability perspective that they're getting with that. And then you got So you couple this idea off. How do I take BMC? Bring them into contempt? Right? Right. Existing workloads. Move that in. Run that native check. Right? Uh, the next one. How do I take existing java workloads and bring them into this modern cloud native Kubernetes space world, you know, making progress with that orchestra check. And then the third area is this notion off several lists, right? Which is, you know, I've got new applications, new services. I want to make sure that they're taking advantage, appropriate resources, but only the exact number of resources that require We do that in a way that's native to kubernetes. Right? So we're been working on implementing a K native based technologies as the foundation as the building blocks, um, off the work we're doing around serving and eventing towards leading. Ah, more confortable several institution, regardless of where you run it across any off your platform prints up. And that will also bring the ability to have functions that made available by really any provider in that same platform. So So if you haven't already to put all the pieces together right that we were thinking about this is the center of gravity is a community space platform that we make fully automated, that we make it very operational, make it easy for different. You know, third party pieces to plug in, writes to sort of make sure that it's in trouble in modular and at the same time that start layering on additional Kim. >>Yeah, I'm a lot of topics. As you said, it's Siachin. I'm glad on the serverless piece we're teasing out because it is complicated. You know, there are some that were just like, Well, from my application developer standpoint, I don't >>need to >>think about all that kubernetes and containers pieces because that's why I love it. Serverless. I just developed to it, and the platform takes care of it. And we would look at this year to go and say, Well, underneath that What is it? Is it containers? And the enter was Well, it could be containers. It depends what the platform is doing. So, you know, from from Red Hat's standpoint, you're saying open shift server lists, you know? Yes, it's kubernetes underneath there. But then I heard you talk about, you know, live aware of it is so, um, I saw there's, you know, a partner of Red Hat. It's in the open source community trigger mesh, which was entering one of the questions I had. You know, when I talk to people about serverless most of the time, it's AWS based stuff, not just lambda lots of other services. You know, I didn't interview with Andy Jassy a few years ago, and he said if I was to rebuild AWS today, everything would be built on serverless. So might some of those have containers and kubernetes under it? Maybe, but Amazon might do their own thing, so they're doing really a connection between that. So how does that plug in with what you're doing? Open shift out. All these various open sourced pieces go together. >>Yes, I would expect for us to have partnerships with several startups, right? You know you name, you know, one in our ecosystem. You know, you can imagine as your functions, you know, running on our serverless platform as well as functions provided by any third party, including those that are built and by red hat itself, Uh, you know, for the portal within this platform. Because ultimately, you know, we're building the platform to be operational, to be managed at scale to create greater productively for developments. Right? So for example, one of things we've been working on we are in the area of developer tools. Give the customers ability. Do you have you know, the product that we have is called cordon Ready workspaces. But essentially this notion off, you know, how can we take containers and give work spaces that are easy for remote developers to work with? Great example. Off customer, actually, in India that's been able to rapidly cut down time to go from Dev Productions weeks, you know, introduced because they're using, you know, things like these remote workspaces running in containers. You know, this is based on the eclipse. Ah, Apache, the the CI Project, You know, for this. So this this notion that you know, we're building a platform that can be used by ops teams? Absolutely true, but the same time the idea is, how can we now start thinking about making sure these abstractions are providing are extremely productive for development teams. >>Yeah, it's such an important piece. Last year I got the chance to go to Answerable Fest for the first time, and it was that kind of discussion that was really important, you know, can tools actually help me? Bridge between was traditionally some of those silos that they talked about, You know, the product developer that the Infrastructure and Ops team and the AB Dev teams all get things in their terminology and where they need but common platforms that cut between them. So sounds like similar methodology. We're seeing other piece of the platforms Any other, you know, guidance. You talked about all your customers there. How are they working through? You know, all of these modernizations adopting so many new technologies. Boy, you talked about like Dev ops tooling it still makes my heads. Then when I look at it, some of these charts is all the various tools and pieces that organizations are supposed to help choose and pick. Ah, out of there, they have. So how how is your team helping customers on kind of the organizational side? >>Yes. So we'll do this glass picture. So one is How do you make sure that the platform is working to help these teams? You know, by that? What I mean is, you know, we are introducing this idea and working very closely with our partners globally and on this notion of operators, right, which is every time I want to run data bases. And you know, there's so many different databases. There are, you know, up there, right? No sequel, no sequel. and in a variety of different ones for different use cases. How can you make sure that we make it easy for customers trial and then be able to to deploy them and manage them? Right? So this notion of an operator lifecycle because application much more manageable when they run with data s O. So you make you make it easier for folks to be able to use them. And then the question is, Well, what other? If you will advise to help me get that right So off late, you probably heard, you know, be hired a bunch of industry experts and brought them into red hat around this notion of a global transformation and be able to bring that expertise to know whether you know, it's the So you know, Our Deep in Dev Ops and the Dev Ops Handbook are you know, some of the things that industry is a lot like the Phoenix project and, you know, just just in various different you know what's your business and be able to start saying looking at these are told, music and share ideas with you on a couple that with things like open innovation labs that come from red hat as well as you know, similar kinds of offerings from our various partners around the world to help, you know, ease their transition into the >>All right. So final question I have for you, let's go a little bit high level. You know, as you've mentioned you and I have been having this conversation for a number of years last year or so, I've been hearing some of the really big players out there, ones that are, of course, partners of Red Hat. But they say similar things. So you know, whether it's, you know, Microsoft Azure releasing arc. If it's, you know, VM ware, which much of your open ship customers sit on top of it. But now they have, you know, the Project Pacific piece and and do so many of them talk about this, you know, heterogeneous, multi cloud environment. So how should customers be thinking about red hat? Of course. You partner with everyone, but you know, you do tend to do things a little bit different than everybody else. >>Uh, yeah. I hope we do things differently than everyone else. You know, to deliver value to customers, right? So, for example, all the things that we talk about open ship or really is about industry leading. And I think there's a bit of a transformation that's going on a swell right within the way. How Red Hat approaches things. So Sam customers have known Red Hat in the past in many ways for saying, Look, they're giving me an operating system that's, you know, democratizing, if you will. You know what the provider provides, Why I've been given me for all these years. They provided me an application server, right that, you know, uh, it's giving me a better value than what proprietary price. Increasingly, what we're doing with, you know, the work they're doing around, Let's say whether it's open shift or, you know, the next generation which ization that we talked about so on is about how can we help customers fundamentally transform how it is that they were building deploy applications, both in a new cloud native way. That's one of the existing once and what I really want to 0.2 is now. We've got it least a five year history on the open shift platform to look back at you will point out and say here are customers that are running directly on bare metal shears. Why they find, you know, this virtualization solution that you know that we're providing so interesting Here we have customers running in multiple different environments running on open stack running in these multiple private clouds are sorry public clouds on why they want distribute cluster management across all of them. You know, here's the examples that you know we could provide right? You know, here's the work we've done with, you know, whether it's these, you know, government agencies with private enterprises that we've talked to write, you know, receiving innovation awards for the world been doing together. And so I think our approach really has been more about, you know, we want to work on innovation that is fundamentally impacting customers, transforming them, meeting them where they are moving the four into the world we're going into. But they're also ensuring that we're taking advantage of all the existing investments that they've made in their skills. Right? So the advantage of, for example, the years off limits expertise that they have and saying How can we use that? Don't move you forward. >>Well, a chef's Thank you so much Absolutely. I know the customers I've talked to at Red Hat talking about not only how they're ready for today, but feel confident that they're ready to tackle the challenges of tomorrow. So thanks so much. Congratulations on all the progress and definitely look forward to seeing you again in the future. >>Likewise. Thanks, Ian Stewart. >>All right, I'm still Minuteman. And much more coverage from Red Hat Summit 2020 as always. Thanks for watching the Cube. >>Yeah, Yeah, yeah, yeah, yeah, yeah.

>> Announcer: From around the globe, it's theCUBE with digital coverage of Red Hat Summit 2020. brought to you by Red Hat. >> Welcome back. This is theCUBE's coverage of Red Hat Summit 2020. Of course this year instead of all gathering together in San Francisco, we're getting to talk to Red Hat executives, their partners and their customers where they are around the globe. I'm your host Stuart Miniman and happy to welcome to the program Nick Barcet, who is the Senior Director of Technology Strategy at Red Hat. He happens to be on a boat in the Bahamas. So Nick, thanks so much for joining us. >> Hey thank you for inviting me. It's a great pleasure to be here and it's a great pleasure to work for a company that has always dealt with remote people. So it's really easy for us to, kind of thing. >> Yeah Nick. You know it's interesting, I've been saying probably for the last 10 years that the challenge of our time is really distributed systems. You know from a software standpoint that's what we talk about and even more so today number one of course the current situation with the global pandemic but number two the topic we're going to talk to you about is edge and 5G. It's obviously gotten a lot of hype. So before we get into that my understanding Nick, you know you came into Red Hat through an acquisition. So give us a little bit about your background and what you work on for Red Hat. >> About five years ago company I was working for eNovance got acquired by Red Hat and I've been very lucky in that acquisition where I found a perfect home to express my talent. I've been free software advocate for the past 20 some years. Always been working in free software for the past 20 years and Red Hat is really wonderful for that. >> Yeah it's addressing me okay yeah. I remember back the early days we used to talk about free software. Now we don't talk free, open-source is what we talk about you know. Bream is a piece of what we're doing but let's talk about you know, You know, eNovanceI absolutely remember they were partner of Red Hat. I talked to them and a lot at some of the OpenStack shows. So I'm guessing when we're talking about edge, these are kind of the pieces coming together of what Red had done for years with OpenStack and with NFB. So what, what's the solution set you're talking about? Bring us inside, how you're helping your customers with these types of split. >> Well clearly the solution we are trying to put together as to combine what people already have with where they want to go. Our vision for the future is a vision where OpenShift is delivering a common service on any platform including hardware at the far edge on a model where both v-ends and containers can be hosted on the same machine. However there is a long road to get there and until we can fulfill all the needs, we are going to be using combination of OpenShift, OpenStack and many other product that we have in our portfolio to fulfill the needs of our customer. We've seen for example Verizon starting with OpenStack quite a few years ago now going with us with OpenShift that they're going to place on up of OpenStack or directly on bare metal. We've seen other big telcos use that in very successful to deploy their 5G networks. There is great capabilities in the existing portfolio. We are just expanding that simplifying it because when we are talking about the edge, we are talking about managing thousands if not millions of device and simplicity is key if you do not want to have your management parts in Crete. >> Excellent. So you talked a lot about the service providers. Obviously 5G as a big wave coming a lot of promise as what it will enable both for the service providers as well as the end-users. Help us understand where that is today and what we should expect to see in the coming years though. >> So in respect of 5G, there is two reason why 5G is important. One it is-- It is important in terms of edge strategy because any person deploying 5G will need to deploy computer resources much closer to the antenna if they want to be able to deliver the promise of 5G and the promise of very low latency. The second reason it is important is because it allows to build a network of things which do not need to be interconnected other than through a 5G connection. And this simplifies a lot some of the edge application that we are going to see where sensors need to provide data in a way where you're not necessarily always connected to a physical network and maintaining a WiFi connection is really complex and costly. >> Yeah Nick a lot of pieces that sometimes get confused or conflated, I want you to help us connect the dots between what you're talking about for edge and what's happening in the telcos and the the broader conversation about hybrid cloud or Red Hat calls at the open hybrid cloud because you know there were some articles that were like you know edge is going to kill the cloud. I think we all know an IP nothing ever dies, everything is all additive. So how do these pieces all go together? >> So for us at Red Hat, it's very important to build edge as an extension of our open hybrid cloud strategy. Clearly what we are trying to build is an environment where developers can develop workloads once and then can the administrator that needs to deploy a workload or the business mode that needs to deploy a workload can do it on any footprint. And the edge is just one of these footprint as is the cloud as is a private environment. So really having a single way to administer all these footprints, having a single way to define the workloads running on it, is really what we are achieving today and making better and better in the years to come. The reality of... to process the data as close as possible to where the data is being consumed or generated. So you have new footprints to let's say summarize or simplify or analyze the data where it is being used. And then you can limit the traffic to a more central site to only the essential of it. It is clear that with the current growth of data, there won't be enough capacity to have all the data going directly to the central path. And this is what the edge is about, making sure we have intermediary of points of processing. >> Yeah absolutely. So Nick you talked about OpenStack and OpenShift. Of course there's open source project with with OpenStack. OpenShift the big piece of that is is Kubernetes. When it comes to edge are there other open source project, the parts of the foundations out there that we should highlight when looking at these edge loop? >> Oh, there is a tremendous amount of projects that are pertaining to the edge. Red Hat carries many of these projects in its portfolio. The middleware components for example Quercus or AMQ mechanism, Carlcare are very important components. We've got storage solutions that are super important also when you're talking about storing or handling data. You've got in our management portfolio two very key tool one called Ansible that allows to configure remotely confidence that is super handy when you need to reconfigure firewall in mass. You've got another tool that is the central piece of our strategy which is called ACM, Red Hat's I forgot the name of the product now. We are using the acronym all the time which is our central management mechanism just delivered to us through IBM. So this is a portfolio wide we are making and I forgot the important one which is Red Hat Enterprise Linux which is delivering very soon a new version that is going to enable easier management at yet. >> Yeah. Well of course we know that realers you know the core foundational piece fit with most of the solution in a portfolio. That it's really interesting how you laid that out though. As you know some people on the outside look and say, " Okay, Red Hat's got a really big portfolio. How does it all fit together?" You just discussed that all of these pieces become really important when they come together for the edge. So maybe you know, one of the things when we get together summit of course, we get to hear a lot from your customers. So any customers you can talk about, that might be a good proof point for these solutions that you're talking about today? >> So right now most of the proof points are in the telco industry because these are the first one that have made the investment in depth. And when we are talking about various and we are talking about very large investment that is reinforced in their strategy. We've got customers in telco all over the world that are starting to use our products to deploy their 5G networks and we've got lots of customer starting to work with us on creating their strategy for in other vertical particularly in the industrial and manufacturing sector which is our next endeavour after telco yet. >> Yeah well absolutely. Verizon a customer, I'm well familiar with when it comes to what they've been used with Red Hat. I'd interviewed them, it opens back few years back when they talked about that those nav-pipe solutions. You brought a manufacturing so that brings up one of the concerns when you talk about edge or specifically about IOT environment. When we did some original research looking at the industrial internet, the boundaries between the IT group and the OT which heavily lives in manufacturing wouldn't, they don't necessarily talk or work together. So how's Red Hat helping to make sure that customers you know, go through these transitions, pass through those silos and can take advantage of these sorts of new technologies? >> Well obviously you have to look at a problem in the entirety. You've got to look at the change management aspect and for this, you need to understand how people interact together if you intend on modifying the way they work together. You also need to ensure that the requirements of one are not impeding the other on demand, on environment of a manufacturer. Is really important especially when we are talking about dealing with IOT sensors which have very limited security capability. So you need to add in the appropriate security layers to make what is not secure, secure and if you don't do that you're going to introduce a friction. And you also need to ensure that you can delegate administration of the component to the right people. You cannot say, Oh from now on all of what you used to be controlling on a manufacturing floor is now controlled centrally and you have to go through this form in order to have anything modified. So having the flexibility in our tooling to enable respect of the existing organization and handle a change management the appropriate way. These are way to answer this... >> Right Nick, last thing for you. Obviously this is a maturing space, lots of change happening. So give us a little bit of a look forward as to what users should be expecting and you know what pieces will be the industry and Red Hat be working on that bring full value out of the edge and 5G solution? >> So as always, any such changes are driven by the applications. And what we are seeing is in terms of application, a very large predominance of requirements for AI, ML and data processing capability. So reinforcing all the components around this environment is one of our key addition and that we are making as we speak. You can see Chris keynote which is going to demonstrate how we are enabling a manufacturer to process the signal sent from multiple sensors through an AI and during early failure detection. You can also expect us to enable more and more complex use case in terms of footprint. Right now, we can do very small data center that are residing on three machine. Tomorrow we'll be able to handle remote worker nodes that are on a single machine. Further along we'll be able to deal with disconnected node. A single machine acting as a cluster. All these are elements that are going to allow us to go further and further in the complication of the use cases. It's not the same thing when you have to connect a manufacturer that is on solid grounds with fiber access or when you have to connect the knowledge for example or a vote and talk about that to. >> Well, Nick thank you so much for all the updates. I know there's some really good breakouts. I'm sure there's lots on the Red Hat website to find out more about edge in five B's. Nick Barcet thanks so much for joining us. >> Thank you very much for having me. >> All right. Back with lots more covered from Red Hat Summit 2020. I'm Stuart Miniman and thanks for watching theCUBE. (bright upbeat music)

>>from around the globe. It's the Cube with digital coverage of Red Hat. Summit 2020 Brought to you by Red Hat. >>Hi. And welcome back to the Cube's coverage of Red Hat Summit 2020. I'm stew Minuteman. And while this year's event is being held virtually, which means we're talking to all of the guests where they're coming from, one of the things that we always love about the user conference is talking to the practitioners themselves And Red Hat Summit. Of course, we love talking to customers and really happy to welcome to the program. Uh, Alejandro Lopez Asano, who's the director of e health with the Argentine Ministry of Health, Coming to us from Buenos Iris, Argentina. Alessandro, thank you so much for joining us. Thank you for having me. All right, So Ah, you know, look, healthcare obviously is, You know, normally, you know, challenging in the midst of what is happening globally. There are strange and pressures on. What? What is happening? So really appreciate. You think with us? Um, tell us a little bit about you know, the organization, and you know your role in Nike's role in supporting the company's mission. >>I'm part of the minister of girls in Argentina, Argentina Federal country. That's a national military girls, according it's Felker Healthcare System. All around the country with different provinces work, we work with the with the Ministry of Culture, which problems with the governor of problems trying to maintain and coordination the healthcare system. And we create the national policies that tried everybody. Show them to apply on the assistance that we create national incentive. This is much more. It's similar to the US, with the national government. Create incentives the province since the states adopt new new new practices and the best quality >>Excellent. So, yeah, the anytime we talk about healthcare, you know, uh, you know, medical records, of course, critically important. It's usually a key piece of, I d you know, governance, compliance in general. So what are some of the challenges that the ministry basis when it comes to you know, this piece >>of overall health care? My role in the midst of cops is exactly that. Coordinate health information systems around the country and having and access to the single sorts of medical records around the country. It's a great thing that we're trying to achieve We don't want to have a central repository, but they're going to have some kind of have that allows you to access information for all around the country. So the fragmentation of the seat between different provinces and also having public providers and private providers. It's a challenge because the information for one patient is this. Turn a lot of different places. I need to have some kind off have or enterprise services. But you're allows you to gather this information at the point of care and to provide the best quality of care for the patient having the full road regardless of work. It was taking her before. >>Yeah, pretty Universal Challenger talking about their distributed architecture, obviously security of Paramount performance, but still has to have the scale and performance that customers need to bring us in a little bit. This this project, you know, how long has this national health information system? How long has it been to put that together, Bring us through a little bit as to you know, how you choose how to architect these pieces, >>except that we've been working on for the last three years and then be able to create an architecture that was not invasive, that anyone can collaborate and contribute to this information network, but still having the on the rights and other responsibility for Monday in their own data. And we didn't want to have a central that the rates that it's acceptable security issues or privacy issues. We wanted information to remain distributed. But to be able to collect that a 10 point so they're able to create a set off AP Eyes Bay seven Healthcare interoperability standards that allow developers off critical systems all around the country to adopt this new way of changing information to your and privately provided to the practitioners so they can access information. Another side, >>Excellent. And so three years. You know, that's a rather big project. You've got quite a lot of constituents, and obviously, you know, healthcare is, you know, completely essential and critical service. There, underneath the pieces obviously were part of Red Hat Summit covering this so help us understand a little bit, you know, Red Hat and any other partners. You know what technologies they're using to deliver this? >>That's the big challenge was to have this kind of distributed organization with a central how that needs to provide services around the country at any time today. And we really think people need to be confident that they can use this network, that we're treating patients. We don't want them to try to do it and fail from the lost confidence in that you're not going to have the greater adoption from system developers. We need to have a very strong and company in the world, and this can grow really exponentially cause data. I mean, any chess is constructing, like one billion right work on math or something like that. But we know we can grow exponentially, but we need to have some kind of infrastructure that was reliable, but it was easy to deploy the first time. But the house and growth road map that will allow us to incorporate all the extra capacity around Argentina, Mr Safeway Way, need to be confident that we can grow a dog's level. So basically we were working already. We're Kalina and all the basic things. We wanted to go to open shift. It was really important to be able to have the container station system that allows us to found according to the needs and the adoption, right? That was really unpredictable because we need to create incentives for election. But you never know how fast the adoption would be. We need to have some flexibility of attracted by open ship, but also, we need to use a P. I like the scale in order to provide this way to communicate ap eyes to give people secure form to access the FBI's to learn about them and to try. So we're using different parts off the off the stack we have in order to do that. >>Okay, great. Tell us the adoption of this solution. How was the how is the learning curve? But, you know, moving to containerized architectures. You talking about all the AP eyes in there? How much was there a retraining of your group? Were there any new people that came in? You know what was what was Red Hat's role in really the organizational pieces of getting everybody on this on this new skill set? >>Well, the role of record was central because we didn't have the capability to go on research all these open source tools and find the proper combination between the container administrated orchestrator, the continuous integration part it was really difficult for us to start from scratch. I mean, this is something that this violent wanting to have a huge team, a lot of time, special skills and when you, because there are teams were used to work in monolithic applications with a very long development cycles that every time you need to change, we need, like, three months another. See, the change lives in the application for the end user, but we need to make a radical change there. So we saw in Red Hat Opportunity. We have a robot on the container adoption program sandcastle the steps that we need to work true. So what's really good to have our 16 team to retrain and to go through the container adoption program to use the combination of tools that breath already provides, like a stock that's the really compatible with each other. Then you need to know that that is easy to update when there are changes in their security things that they need to take to get the notification. So this and you have the daily support also because we have to create a new brand developers and the Dev Ops team was negative and you have developers and very technical person that didn't know anything about the application. We helped to create the tools that this, these new roles that combined these activities on the day to day work record expert was really key to that because they give us the roadmap. But what we need to do with timeframe with thing, that sort of statement we need to do in order on give us the daily support, the retraining, and they were really excited to work. Yeah, attempting that also was really good news for them because they were using old versions of job on old versions, off deployment systems, that they were everything by heart and the common life. And now, when they learn to do that with sensible and with the continuous integration system, a lot of menial tasks that they were doing everything you know there are automated. But that's a really great impact on the quality of life for them. >>Well, it's interesting that you talk about that, you know. Automation, of course, has been something we've been talking about for decades, but critically important today, you know, 100. I'm curious with kind of the situation happening with the pandemic. You know, people are having to work from home. There needs to be social, distancing the automation. And you know some of this new tooling. You know, what impact has that had on being able to deal with today's work >>environment? That kind of very good impact also, because not only for the automation, because that was that. It's really people have a secure way to work from home to the place ever. You don't need to access directly. Each one of the servers with logging or things like that is much more secure, much safer, much easier to work from home and maintaining the city. But also the dynamic has put a strain on the system because we are maintaining in open shift the whole family objects and violence system for Argentina, and that has much more information going through all the decision making. Politicians are getting information from the violence system and make predictions the style policies and they did. That information is to be available all the time, and previously, when a new strain came like the officially system went down, what was old workings globally So but now, with open shift, we were able to dial up more resources. The system, I maintain the quality, the world, the perimeter Signet work until the decision making person that needs information just in there. >>All right, so So all 100. We've talked about kind of a transformation that you've had. There's the government impact. There's the practice, the other providers of services. If you talk about you know, the ultimate end patient, you know what is the impact on them or you know what? What you have implemented here, >>what they did, that the patients now would be able to move between different parts of this complex system we have before. It was very common that the patient arrived hospital with about full of studies in paper, like somebody from a previous hospital finishes reported lab reports. And they have to bring about Dr and don't have to go to all the way from the foundation or a basic both from a province to the capital to get terrible, especially when they go back. And the Dr in the province don't have any information about what happened on one side that said no. They will care if you but no information. I get it through the patient. But now I think the system will integrate the older caregiver around Argentina in a much more simpler where you will be able to collaborate with doctors, another throwing, sitting, other CPIs on the patient will be able to vote from private to public. We have different kind of procedures, and every information will follow him on. Everyone will be able to take care of him with the best information. >>I'll under that. That's really powerful pieces there. So I guess the last piece is a little bit about kind of where you are with the overall project. What future goals do you have for this initiative? >>You've been really happy with the way we're starting to have adoption. We have more than 37 knows not already working in this network. And so this is really good. We have a good adoption right on. The implementation of open shift is going really well. The developers are really happy. We see the impact. That there are no downtime is really good. We need to continue transforming old legacy applications, monolithic applications to transform that into micro services. This work to do in deconstructing these big applications into more scalable micro services, and we need to take more advantage off. Sorry. Scale, Because really excellent feature for Developer portal. So, like that, everything will be about the adoption of the FBI. That information much simpler when we give all those tools developed. >>That's that. Once again, Andre, thank you so much. This has been, ah, really important work that your team is doing. Congratulations on the progress that you've made and, you know, definitely hope in the future. We will get to see you at one of the Red hat summits in person. So thank you so much for joining us. Thank you very much. All right, Lots more coverage from the cube at Red Hat Summit 2020. I'm stew minimum. And thank you. As always for watching the Cube. >>Yeah, yeah, yeah, yeah.

>> From around the globe. It's theCUBE with digital coverage of Red Hat Summit 2020 brought to you by Red Hat. >> Welcome back, I'm Stuart Miniman and this is theCUBE's coverage of Red Hat summit 2020, 7th year we've been covering the event of course, one of the differentiators this year is it is a virtual event. We're bringing a Red Hat executives, customers and partners from where they are around their globe to this digital event and really happy to bring back one of our cube alumni is also one of the keynote speakers. He's got a new role but lots of technology to share. Matt Hicks, the SVP of product and technologies with Red Hat. Matt, thank you so much for joining us. Normally we'd all get together. You and I are even geographically relatively close to each other, but of course today as we've said many times, we are together apart. So thanks so much for joining us. >> Hey, thanks for having me. >> All right, so compared to some say it, the company that owns Red Hat, IBM, you're a relatively short timer with Red Hat you only been there for 14 years, Matt, but we, we've talked to many times OpenShift. One of the big things we talk about with you over the last few years, you're one of the founding members of that team, but before we get into it, you've got a new role, the product pieces we said you're kind of stepping up, filling in for the shoes that Paul has, As Paul now says steps up to the CEO role. So tell us a little bit about what that means for you and your your organization. >> Yeah, sure, so you're right. I used to run an engineering for Red Hat and now I have the scope of engineering and the business and our support organization so previous role and it's a great opportunity. I'm excited about emission I've been at Red Hat 14 years. I was actually at IBM prior. So the combination asking pretty significant there. But it's, it's just the neat opportunity. I love being able to, to focus on the entire portfolio for example how it's impacting customers. Especially right now this is tricky time right now for a lot of customers I think Red Hat we're doing our best to make sure we have that value them just to sort of get through the crisis bench form. >> Yeah, absolutely Matt. We usually, when we're looking at a keynote, it's celebrating some new announcement, talking about the culmination of these things and there's a real effort of course, to set a nice balanced tone here. Of course you've got lots of critical companies that rely on Red Hat technologies, on your partner solutions to make sure things work. So, bring us in a little inside basically the organization and how you're helping your customers. I know in these challenging times. >> Yeah, I know this year didn't make a big push and PR who fluff hall all the work. Really proud of that work, but it just, it wasn't the right time to have that focus on product releases. That said, if you look at our customer base there pretty split right now. We have a large part of our customer base they are folks centers weathering the storm right now, and a lot of that work is it's cost savings, it's efficiency it's actually I'm doubling down on their data centers where they've got to go back to things that they own and down that side we'vethrown a whole host of efforts setback from extending our support services. We've gone through extending our product life cycle so customers don't get and then having to do an upgrade right now. We're working with Ansible and with RHEL just in and how we can help customers save and get through it sort of in the way that they want. On the other side though take some industries, whether they're developing a vaccine or shipping, they say there exploding like they need to scale and push and we're making sure that we didn't hold back any technology. 'Cause the toughest thing would be to say, "Well, okay, let's take in OpenShift." We have new serverless capabilities or pipelines. We didn't want it take any of those pieces away from the customer that might be needing to scale 500% right now, but it, it is it's a challenging time. We sort of have helping customers is either end of a really, really wide spectrum. And the good news though we have I think we have good solutions on both album through, but it is a unique experience for me. And as long as I've been in then sure I haven't quite seen as much of AI, I divide. >> Yeah, it's really Matt, I think back to I was working in the tech vendor community back when 9/11 happened and some of the rallying of the community but this has a personal impact for everyone, it's 9/11, it was kind of everybody went home for a day and then rally the troops. You didn't make a big deal of it, but you made sure you helped those customers. Today, this has such a wide impact and yeah, as you said but very unique time that we're living in here. One of the messages you talked about in your keynote is was really emphasizing message we've heard for Red Hat for a number of years. Talking about how your solution really everywhere. Even more than ever. Some of the stories you hear about where technology is accelerating, of course things like work from home. But also customers that are doing digital transformations or I've been looking at cloud adoption, sometimes those things, they need to move through some of the last few steps even faster because they can't touch the gear or they can't access stuff. Or I need to got that automation going even faster so that we can leverage it. So help us walk through a little bit. Yow know where are your technology pieces are OpenShift some of the other technologies that are so critically important for customers today. >> Yeah, you touched on a lot of areas and I would say we probably saw this start and certainly been amplified and just worldwide importance with Telecom. Telecom providers as they've pushed towards things like 5G it's it's not the traditional like you have one data center type thing play and that's what you think troll and whether you call this edge or anything else that relate. You have these multiple tiers of infrastructure and they run it massive scale. And so they wanted one technology platform that could run it was close to the user as possible. And I run into a bunch of different form factors and footprints and also and that's where we really started working with the Telecom providers on OpenShift and taking some of the experience. We certainly work a lot with them with OpenStack for networks, but as things got closer to the edge that pushed to OpenShift was pretty prevalent. We are now seeing you mentioned it where I think customers, a lot of customers are being forced into the digital transformation journey right now I really like, well, everyone's home. How do you serve your customers with this? And they're really that last mile of changes is coming very quick to them. And I think we're seeing a lot of similarities with that technology based, right. The same challenges that the telecom providers had can be applied to other industries, whether it's manufacturing, others in this generally we call it like it's that edge focused area you don't have and infrastructure that runs in one place, you're having to aggregate a lot of it we call this our hybrid cloud work and OpenShift is really Red Hats hybrid cloud. >> Yeah, so often we talk about some of the hype that goes around certain words. I think about cloud-native we've been talking about cloud for so many years out of close partners with all the various solutions out there. When things need to get done, how does it help businesses? How does it help IT reacts to the business and how do we make sure we stay in business? So how was that conversation of cloud-native changed and where's Red Hat sitting in that discussion? >> Yeah, I think not the best circumstance, but I think one of the things that's been really prevalent is when you see this pull back in some way basis to data centers, that conversation about did I build my apps to a standard that I've got it costs, can I move them to a lower cost center structure for me? Like right now, in a week for two weeks. Yeah, that's becoming pretty critical where, we've believed in that model for a long time of whether it's cloud native services building them to a platform that gives you that flexibility that has become a pain point for customers right now. And one of the nice things we've seen this in some government services where if they're built on OpenShift even on premise, they're on the other side of that, where they're having to scale these services massively, they're able to take the same app, same platform, go out to public cloud providers actually help fulfill that scale. Customers, I think that built to that pattern. If they're contracting for a bit or doubling down on their data center, they have the same thing. They can pull back from the public cloud if they need to, but that, that app affordability has gone from being real like secondary, tertiary concern to being a critical aspect of cost savings or just a lot of enterprises right now and in a shockingly short period of time. >> It's interesting when you talk about engineering groups and how they're building product. Most of the development teams I talked to, we're distributed before this event happened. And yes, there's some adjustments that need to happen. I think Red Hat has some almost unique capabilities compared to some others out there. Because, not only do you have your development teams, but of course everything that Red Hat is doing is open source. So I'd love to hear your viewpoint as to, as you think about your product roadmap and what's going to happen in 2020, how do the communities and there's been a number of course key acquisitions that Red Hat has done over the years. Talk a little bit about that dynamic and how much this affects what's happening and how this helps Red Hat both put together the products and the portfolio that it offers. >> Yeah, I think you're right, We're, we are incredibly lucky just business model wise and even as a starting where on the engineering team over half of our engineering team is remote to begin with. And then on top of that, we work with open source communities where we're still just the minority presence in most of those. And so you're working with team members that you've never met. So you could say, the bulk of the work that we did was really distributed. So it wasn't just a huge system shock. Everybody stay productive, stay from home. The second part, that was great our strategy overall, it really doesn't change for us because we're, we're seeing a lot of pressure applied to it where customers maybe a three year plan to get there is becoming their six months plan. But in terms of running infrastructure in these combinations being able to run it in your data center, being able to scale off public clouds and do that consistently, that hasn't changed for us. We are refining areas of making sure that we contributed really double down on infrastructure, mission critical infrastructure like telecom's right now because they're certainly going through the scale there going to push for things like 5G we want to make sure we're doing everything we can for that. Well, we were already working pretty closely with them, so not a huge strategy shift for us. It's okay, how can we just really focus these on the value that customers need right now. We're excited about if you look in the efficiency areas in these combinations, what we're doing with Ansible it's pretty critical to users. Like if you take a real user that's running a data centers worth a year and they need to remotely be able to manage it, control it, optimize it to see you can't get people there. great solutions around around and so we're, we're really pushing down that path. Then if you look at other areas, like with OpenShift, some of the management work group I've been doing, or the scaling areas, if you go through serverless models or pipelines, if you're in the shipping industry or you're in pharmaceuticals working on vaccines, they have massive scaling needs right now. And so they're pushing very hard on and that's what a new technology has reached. All right, there is one technology area that I'd love to get your view. Well, you talked a little bit about in the keynote, definitely plenty of breakouts and we actually have you've interviews digging into of course, current eddies, the latest is going on with OpenShift and a big piece is the virtualization with OpenShift virtualization. As I mentioned at the beginning, you're one of the founding members of the OpenShift team. So as you look at, bare metal virtualization painters were at VMs public cloud on premises. Give us your viewpoint as to where we are in 2020 and how some of that journey has changed over time and how Red Hat might have a slightly different view of how things should be built and where the future should go compared to others in the industry. >> Yeah, really excited about this area because if you look at Red Hat sort of view on this is that we can run Kubernetes sort of as the thing that directly runs on Linux and Bare-metal and for us that's OpenShifting RHEL and it's, it's very powerful because if you look at what virtualization came from, it was machines got really, it's strong and so we needed to carve them up into smaller pieces, make it manageable, that's what Linux containers do is they take a machine they carve them up into these units and let you use all of the power on the physical hardware and we know this world from RHEL for us, that's what Linux does it lights up hardware. So I think the norm in the industry for the last yours years was people would still carve up machines with virtualization, then they would run containers on top and virtualization was sort of your main substrate and there were some challenges with that. The containers it's harder for them to move across those boundaries like BMS isolated for a reason we actually think, and it was an upstream project called KubeVert. Again, we saw this in the telcos pretty early where they were putting OpenShift on bare metal on gear itself, and they were driving to run virtualization inside. And then really you have the flexibility of containers carving up the hardware and we need to bring VMs in. We can run VMs inside of it containers and that it's the opposite of how most people think about it. But it, it gives you the best of both worlds. 'Cause we look at Kubernetes it is sort of that next generation infrastructure layer and you can fit VMs very nicely into that. That's what we're doing with container-native virtualization it gives you a good cost benefits on that. And also if you're going from a virtualized world to a container world you're optimizing towards that destination with OpenShift it's just, it is neat technology 'cause I think most customers they still have a ton of VMs out there. So even if they're bought off on an OpenShift path how do they bring VMs into that story? And so that as of now that's something we're enabling them to be able to do. Cool technology, I mean I'm excited about that. And again, it has a great telco focus for us right now, but I think this is one where it'll have broad reach cross enterprise users to just that are already down this journey and need to accelerate it for cost savings. That's great solution there. >> Yeah, definitely from what I've learned, it's pretty empowering to really help that application development team understand really those cloud native architectures if you will. One of the challenges of VMs was used to just kind of stick the application in there. I think about it anymore and that does not meet where really companies are going. It's all right, Matt, I got to ask you the last question. Since you own product and technologies, talk about some of the tough areas. Where is Red Hat really working with the community to help really improve things for the ecosystem and for customers as you look out through the rest of the 2020? >> Yeah, I think looking out for the rest of 2020 it's sort of, it's picking focus areas because that the most challenging thing the nice part especially at Red Hat too, there is a ton of goodwill. What can we jump in help can we do and when we looked at it, a lot of our customers, they're doing awesome thanks. And they're sort of in the middle of the crisis. So a big part of our focus then making sure we help them. One of my friends favorite stories, it's close to really like Red Hats ethos is a Medtronic, they're a ventilator. They manufacture ventilators, they open source there are ventilator designs so that companies like Ford or Telsa could actually they're retooling their factories to build them Medtronics open sources so they can actually get the designs to build. When we see those things it's just awesome. Like those are great like that is what for us opens spaces is build on and we are really doubling down to make sure that whether it is a support case or bug or problem where we have to jump in and give them engineering expertise to help them scale. That has been our focus probably for most of 2020. In doing that well, I think our challenge our hard part is just bringing focus from all of them, little things we can do, to what are the things that are going to have the most impact right now, which is, it's tough but we have a lot of them. Like on the technology side, we have the virtualization areas. Some of the, the workaround cork is like, how do we bring Java workloads into this Kubernetes world? Like really good things there, but I'm sure what we know right now we'll unfortunately it probably change again and another couple of months. We just have to he really flexible, keep prioritizing focus on it. >> Right, well Matt Hicks taking a new leadership role is always challenging especially in these times. So I want to wish you the best of luck and of course thank you to the team. We always really appreciate the partnership with Red Hat to be able to share this content with the communities. Always good to talk to you man. >> Sounds good, it's great talking to you too. And maybe next year we'll be back to the in person. >> Absolutely. All right, watch more coverage for Red Hat summit 2020 I'm Stuart Miniman and thank you for watching theCUBE. (upbeat music)