 So now is the fun part of the day. So I can see our numbers have dwindled a little bit because it's been a long day. We did have, at one point, 380 of you here. I know there's not 308 of you here right now, but that means there's more beer and chips upstairs later for us. Now I'm going to ask the Red Hatters who've been on stage and some of the support folks to come up and join us now so that we can have a little bit of a Q&A session before we go off and have a beer and you really drill them down. Nas, is he in the room? Is Nas here? My runner? My runner's not here. I may be the runner. Or I might tap. Oh, there you are, Nas. Great. So take one of these. And whoever asks the first question gets the first beer. Can you walk? Can I ask it? Yeah, no, you can't ask it. So if you can come all the way onto the stage, grab a few seats. Let the people who are the most tired the furthest away. And I'm going to give that to you. And all right, so do we have a volunteer for the first question right there, Nas? So as we're getting set up, all right, and some of you can sit down. You're allowed. Oh, nobody wants to sit down. I was looking at those chairs going, I need new chairs for my kitchen and my living room. And I'm like, oh, I really like those chairs. They may be coming home. I can't get that in my suitcase. So all right, go ahead, Nas. Ask your first question here. My question is related to the last session which we had. I'm glad to hear that OpenShift Addicted will be available for GCP soon. So do you have the same plans like AWS that customers will be able to deploy it in their own VPCs? No, there's not a plan for that necessarily. So OpenShift installer today builds a VPC when you do the IPI install. And we use the IPI install for OpenShift dedicated. Right, OK. This is what we do to our interns. We make them runners. And yes? We've heard a bit about various clouds today, including Red Hat and IBM Z Cloud. Obviously, with the merger of Red Hat and IBM, where do you see the relationship of those two cloud services? What do you see the future? Oh, did the right. I have not been authorized to speak about this, but I will anyway. I think the conversations that a lot of us have been having across groups, right? I mean, we're the same company now, but we're still independent, have been very positive. We're bringing each other into projects and learning from each other. And I think we're all getting better for it. Yeah, I would say. Is that a non-answer for it? Yeah, I'm going to add Lib a little bit on that, too. Because one of the interesting things, I don't know if you remember at the very beginning of the day, because that was a long time ago, there was that jellyfish diagram, where I was showing the intersection of the IBM and the Red Hatters, who are working on different open source projects and the collaborations. There isn't always a lot of overlap, too. But what it's done is it has extended our reach into a lot of different projects, so that we are now connected to these other projects and we have resources to reach out and tap to find out about new features and functions and help us integrate in there. So from an open source perspective, it's really opened up a lot of doors for us. Also, I think the Tecton work, too. We've seen a lot of people coming together from IBM and Red Hat and working on that. So there's lots of really great examples, even in the past, how many months has been? Six months? I can't even, it seems like forever, maybe not. But it's really expanded our universe in terms of how we can support each other in the open source community, as well as extended the resources that are available for us to help you implement and deploy OpenShift and OpenStack and all of the other projects that we have. It's really, I think the ramp up, training everybody on all of our technologies has been interesting. Yeah. I think one of the concerns that I've, sorry, one of the concerns that I've heard from a lot of customers is, is this going to change the Red Hat culture, right? Is this gonna change the way we do business, the way we interact with customers and partners? And the answer so far has been a resounding no. If anything, we have been given opportunities to accelerate. Yeah. And we've been given additional revenue to support hosting events like this. So like the IBM Z folks who have a wonderful reference architecture and you should go talk to them about Linux one and all the great things they're upstairs. But it's also, you know, it's given us, I think it's given us a lot more resources to do more innovation and grab more resources from different places. The whole multi-cloud project group that's come on board, it's pretty amazing. And without the acquisition, we wouldn't see something like that happen. Would have been very difficult to expand like that. Yeah, so I do want to be clear open first. And so it's not going to be going to doing any kind of proprietary exclusive offerings with IBM Cloud. And so the choices you have today, you'll have more choices in the future to be clear. All right, another question right down here. We get to point to. In a multi-cloud design, do you see OpenShift being the one joining and giving the view of the security across all cloud service provider because each is having a lot of recommendation in this space. So do you see OpenShift to implement something, to unify? I think there's lots of opportunities there. We're still kind of fluffing out some of the details to be honest. I guess one of the areas, you kind of got a flash of it this morning that I didn't go into that kind of goes to your question is we're doing some work on the networking side to kind of join these clouds together. And when we looked at it, the initial thought was, well, you've got multiple different clusters. Let's just stick a VPN in there and connect them together and you're done and everything's nice and good. But then when we took a second look at it, we realized we're dependent on services in there. We want to do that. And then you get to, well, actually, I'm going to set up some network policies. So what do I do about that? How do we propagate them? How do I handle them? So we're looking at, I don't know if I said this already, sorry, I'm blanking on it. We're using the Submariner project and part of that are things called Lighthouse and Coast Guard and Coast Guard is about this spread and this policy around. So that together with the integration, I kind of talked about IBM, MCM, that has policies and you can look at whether you're in policy or not on your clusters. So there's kind of opportunities right across the stack to do that. So yes, I think it's core to the answer. Do we have that all fleshed out yet? Not quite now, but I think we're close with things like the networking pieces that we're doing, the great work that the storage teams are doing as well to kind of pull that all together. So yeah, it could be a good solution there. Similar sort of vein around the multi-cloud thing over here. I was really taken by the O-Shift Hive operator. Right now I'm guessing that is single-cloud, but with the capabilities to have clusters across multiple and have a true hybrid, do you think it may go that way so that you can have a management hive that can actually stand up into different cloud infrastructure so you can have some on-prem, some public? So yeah, I don't probably let the dedicated team chip in as well. So one of the things that we're looking at, I think we had it on the roadmap as integration with MCM, so I feel like a sales rep for MCM at the moment, sorry about that. But one of the things that you'll see on the demos that you do today is they'll have their environment running and then looking across different cloud providers with Red Hat OpenShift in there. So Hive, from however you point, it's gonna plug into that because the thing that's missing in multi-cloud manager right now is the ability to deploy additional clusters just like you guys have done with OpenShift that's dedicated already that lets you do that. So yeah, we're gonna go across hybrid. I mean, that's a, I don't know, let me ask you all. We see that as a major use case, right? Where position ourselves as being cloud agnostic, go with any of the providers, go with two, go with on-prem and one is that, I'm seeing some nodden heads. That's definitely where we see ourselves sitting. So absolutely we'll be doing tooling around that. I want everybody to keep hands at different sides so we run them around. Hi, so like a bunch of folk, we use Calico. We need to because we're layer three. I think Calico stops us from using your Istio, your service mesh version. And then I was hearing today that you've built your Knative solution on your service mesh and then Tecton on top of Knative. I'm a little bit worried that you're building links within links and that we might be excluded from some of the capability within OpenShift. I'll try. So I'm, yes, I definitely did mention that for serverless, it will install service mesh and service mesh consists of three additional projects, Istio, Yeager and Keali. So there are some dependencies there. Pipelines just to clarify, pipelines is built on top of Tecton but Tecton doesn't have any of those other dependencies on any of those other products. Projects, excuse me. I guess I'm not sure, I'm sorry. I'm not sure what the question was exactly. Well, if you don't use OpenShift's built-in network solution because you can't because you can't do overlays. Okay. Are you excluded from using Red Hat service mesh and therefore excluded from using Red Hat's Knative implementation as well? That part, I don't know. Can I grab you later on and I'll get you an answer off later? Good question though. Yeah, that's a good question. I remember, your name's in the book now. Yeah. Another question, not there? I'm sorry, which network solution are you using? Calico. Calico, yeah. I mean, I'm new to Red Hat so I think there's a lot of unknown knowns to me but, I mean Calico, I worked at Docker so I did a lot of integration with Calico and Docker, right, so there's nothing that prevents you to work with Calico, it's all the containers and container networking. Red Hat uses OVN, you know, inheritance of OpenV switch, right? So I don't know the exact answer but like I think there's a close answer there of, you know, there shouldn't be anything completely inconsistent of your ability to use Calico for your sort of network framework for container support within Kubernetes but I don't know the exact answer because I came from the non-Red Hat version of the integration. I don't know if that helps or not. Hi, hello. I've got a question really more about the futures and specifically around edge computing. You're seeing the major hyperscale providers showing their hand around their strategy. You've seen AWS with AWS Wavelength, for example, and help post the on-prem and look zones, et cetera and also to move around in terms of supporting low latency next generation services, for one to a better term, moving the network edge out into the 5G network. What is Red Hat's position around edge computing and integration with the 5G network, et cetera, et cetera? I'll make Duncan answer that. I'll give you another tap dance answer. I guess I tried to kind of hint at this this morning. Talco and Edge and 5G, we've seen that as a major opportunity for us. We've ramped up significantly, bringing lots of people into work on it. So it is areas that we're investigating. It's still kind of being fleshed out. We took a project that was more generic and I'm desperately trying to think of the code name for it right now and I can't, I'm blanking. And we've essentially repurposed them to look at the use cases that you're talking about. You'll probably see some more about this in the next few months as we flesh out what the project's doing. I can be candid in the room. What we're doing right now is we've actually picked a partner, stroke vendor, stroke customer that we're working with on now to kind of go and deliver something right now. I'm sure some of my colleagues here went through the pain. Believe it or not, we do plan and we did 4-4 planning a while ago. And we just had to do a little mini-replan because of this Talco opportunity because there was quite a lot of features just had to drop off the road map because we needed to go and execute on that side. So I can't give you specifics right now. I can maybe get you, if you really want to answer, I can get you in contact with someone who can but there'll be more coming on that soon. But yes, it's definitely, as I said, it's one of our four strategic areas of investment, one of our four big bets where we just see massive opportunity. And it really did kind of, I don't know, I'm not the brightest of people so I don't know, we'll see the train coming down the track to hit me in the face but that really kind of snuck up on us. If I could add just a couple of things. So what you saw with us previously with OpenStack was taking a great IAS solution and making it fit for purpose for Telcos. So a lot of work went into OpenStack and been the past is to make it more robust and better for the Telco providers. So that's the goal now for 5G and OpenShift, to look at one of the feature gaps we have. Like a Telco provider has some extreme requirements, more so than even some of the banks that we see here now. So that's the focus to the point about the 4.4 planning and beyond to fill those gaps. In terms of kind of the broader vision, I mean, we'll watch this space and we'll talk more about that in the future but we're gonna make this enterprise great for Telcos and carriers as the same one we've done for Linux in the past and then OpenStack. And I'll put in a pitch for, we do have a Telco edge sig. If so, if you go to commons.openshift.org, you can sign up and we do keep everybody informed and we are going to host an edge Telco OpenShift Commons gathering in 2020. Hoping it's in Vancouver alongside of an OpenStack foundation event in mid June. So as he said, watch this space because we'll bring all of the product managers from both the edge and the Telco initiatives as well as a number of the customers and partners that we're working with to talk about just this and we have a whole track that's all that has a number of talks at Red Hat Summit. We're hosting a gathering there as well in, when is Red Hat Summit? It's in San Francisco, end of May. Thank you very much. End of April. Okay, end of May's Tel Aviv. We'll keep them straight but yeah, so there's a lot of working on. There's a few OpenShift Commons briefings. China Mobile did a wonderful one that went way over my head. But talking about the use case and a lot of that and that's really again, where you guys coming on stage, talking about your use cases, help inform our road masks and stuff and have gotten us into the space and into the conversation. So it's quite helpful. Another question? Okay, everybody else can see. Way up in the back, yeah. That's okay, cool. So can we prepare a question out of that? Yeah, really. We're just gonna make them run back and forth. That's all good. Thank you, crew and dine. We just seen a brilliant presentation from HPE on health and we all know that the Chinese have got major issues in this space and they're wonderful connected 5G networks. Do you think next time we see a major virus like that, you'll be ready to assist and give people down to the handset guidance in real time? I'm not sure how I answered that. What was the question? I'm not quite sure what the question was. Your last question alluded to 5G, as it happens there's a summit for that upstairs now. The integration to the back ends, to the health systems and that mass surveillance and the ability to update people, that could be something that you do next time. I think actually Francesco who is here, is he still in the room from public health? He may have had to go. But if you looked at some of the work that they're doing around predictive and using leveraging OpenShift and other tools in OpenStack to predict this, to predict the size of epidemics and stuff, a lot of that work, we're hoping to enable to predict that sort of stuff and make that happen. It's always amazing to me and I think to all of us what people are actually doing on top of OpenShift and on top of the other projects and we just hope with projects like Open Data Hub and some of the great things that are going on to really enable that work and yeah, it's what inspires us to keep going. Question? Is there a question over there really? Are we just gonna make him run away over there? All right. Go ahead. Go ahead. Go ahead. Let's take it, let's go. The beer's up there. Thank you. No, I think, first of all, this event is only as good as the engagement that we get from the community and so far these have been amazing which is why we've had more and more events around the world and why they get richer and richer in content but we are coming up with EMEA CubeCon and with Red Hat Summit and others. So I just wanted to make a request. If we have ISVs in the crowd that are looking to certify we're looking to make a big push at Red Hat Summit. So feel free to reach out to us so that we can help you with that and then if you're a customer using operators we'd like to tell that story as well. So we have a number of partners, they've certified their operators. We'd like to see a customer who's using them that can speak to what that experience has been like. So just a shameless plug on things that we're looking for in the next few events. All right and I'm gonna do a few more shameless plugs here too. So I'm really thrilled to have John Willis and having kicked off the dev ops, the dev sec ops saved too and it's really gonna be a lot of fun and we're gonna learn a lot and there's a lot of great folks, the automated governance, tons of really cool stuff. So if you go to commons.openshift.org and you scale about or you slide down about halfway through you'll see a section called interests. If there's an interest group there that's or something that's missing there that you think we should be talking about, let me know because I'll make you chair that working group or that SIG and I'll find a counterpart for you too. So we're really interested in teasing out these stories, getting more feedback and making sure that we're the best fit for your workloads. So that's really, there's another question down here in the middle because Naz is gonna get two beers. I apologize, in the roadmap there is something in terms of function as a service to abstract across all different across service provider because anyway, the biggest trend is to move fast but there is a lot of vendor locking. So do you envision something in the next future into that space? Again, it's not, I'm not an expert on that, just side knowledge. Knative is supposed to be that solution. It's supposed to provide you diagnostic that you get from other services within OpenShift. So currently you can go online to look for Knative, they have benchmarks there, they have their plans there and a lot of additional information to answer that point. And it will product wise, it will go by the name of serverless, OpenShift serverless. Because we have to rename everything and that's just our SIG here. Any other questions? Diane, can I answer two questions? Pass it on down. Because we're gonna start asking you questions. There were two people there didn't get round to at lunchtime with answers. So for the persons that asked, power support for OpenShift is April Mage timeframe and someone was asking about Red Hat and their prize virtualization is a provider that you can install on and that's in the 4.4 release, both automated install and user provided infrastructure. Hopefully they're still here, doesn't look like it. I'm gonna make you pass it to Christian and a shameless plug again for OKD and when do we think the OKD beta is coming out? Soon. Yeah, hopefully next week actually. He's been saying that for about three weeks so I'm just putting him on the spot here. Yeah, you can actually try out what we just talked about the overt based install on OKD already that works already. So it'll be supported. We build off of the master branch which eventually will become 4.4. So yeah, just like that. All right. Well, if we can get a big round of applause for all of these people, especially one. Thank you.