 So it looks like it's time to get started. Welcome to another OpenShift Commons briefing, everybody. Your usual host, Diane Mueller, is helping a bunch of kids learn about the outdoors of British Columbia. So I am your guest host for today. Today we're going to have a briefing on some of the work happening inside of Red Hat on an operational dashboard for OpenShift V3 and Kubernetes. Kubernetes is underneath both OpenShift, well, it's underneath OpenShift. And Julim and Serena Doyle have been working on creating a single pane to manage both for all their operational needs. So I'm gonna turn over the rest of the presentation to Julim and Serena. They've asked that you hold questions until they ask for them. If you have a question while they're in the middle of talking though, one or the other will be monitoring the chat session. So go ahead and put your questions in there and take it away. So thank you, Steve. And good day to everybody and thank you for joining us in our operational dashboard for OpenShift V3 and Kubernetes briefing. And my name is Julim and I have here with me Serena Doyle and we're part of the Red Hat user experience design team. And thank you for joining us today. So without further ado, I'll jump right in. What we're going to talk about today is give you a quick overview about some of the underlying technologies and some of the ways we're approaching how we're going to actually monitor or operationalize the management of OpenShift V3 and Kubernetes. And as Steve mentioned, if you have questions, we will be pausing throughout the presentation and feel free to also use chat during that time. So just in case folks aren't aware, OpenShift V3 is an on-premise version of Red Hat's pass and it's built on top of Red Hat Enterprise Linux. And it's built around the central idea of being able to run applications built in Docker containers and being able to run them on top of OpenShift. And the notion behind this is we'll use Kubernetes which is a technology that Google opensource in order to schedule and orchestrate the containers. And one of the things that folks are using this technology for is to improve their DevOps or development in the enterprise or in any kind of on-premise or public cloud environment. If you're interested in getting started with OpenShift, please take a look at that URL and take a look at it. I'm gonna jump briefly and then dive in. So Kubernetes is an open-source orchestration system for Docker containers in a clustered environment. As mentioned, it's going to handle the scheduling of the nodes within the cluster and actively manage the containers and other entities in order to make sure that the cluster matches what the user's intended. And again, there's a link there if you'd like more information about it. And where we're gonna spend a lot of our time today is around a technology called ManageIQ. Now ManageIQ is the upstream project that Red Hat has around providing best of breed management across multiple environments, whether it's virtualization cloud or a containerized environment. For OpenShift V3, there are two consoles. For the operator or the administrator, we are providing the operations console for actually managing your OpenShift V3 and Kubernetes workloads from ManageIQ and from a downstream or from a Red Hat perspective, the Red Hat branded version of ManageIQ is cloud formed. So if you look at that picture that you see on the left, I mean, sorry, on the right, it basically shows that whether you're in a bare metal environment, a virtualized environment or a cloud environment and the cloud could be with an open stack, it could even be AWS or Google or any of the other clouds that are supported that run containerized workloads, you should be able to use ManageIQ or cloud forms to manage these workloads. Let me jump ahead. So some of the different concepts with regards to OpenShift and Kubernetes to keep in mind is that in a containerized environment that's clustered, you have a whole bunch of different entities. These include containers, images, namespaces or projects, the nodes or the machines that are actually running the pods and containers and pods are basically groups of containers. Some of these concepts that you see on the screen are basically some of the different components that will be managing from a ManageIQ or a cloud forms perspective. And I'll become a little bit more evident as we share with you some of our proof of concept that we're about to share with you. So as mentioned, what we're planning to share with you are some design concepts. We have a running prototype that Serena is going to show you and what we'd like to invite from you is any kind of feedback or thoughts that you have on what we're about to share with you today. And just... Let me ask a minute of questions. Thank you. I'm going to pause and see if anyone has any questions. Thanks. Any questions? Sorry, I'm not able to see. Nope, not yet, so just noting, yeah. If anybody wants to ask questions, feel free to put them in the chat. Otherwise, we're going to continue on and switch off, I'm going to start sharing. Yeah, so before you go there, let me just briefly talk about some of the use cases we're going to show. As I mentioned earlier, we have the ability with ManageIQ to manage the whole OpenShift V3 and Kubernetes environment. Now, from a management perspective, this is the full lifecycle of your application containers, everything from being able to deploy all the way to troubleshooting it and retiring it. Today, we are going to focus on the monitoring set of use cases. And what I mean by that, we're not going to be doing any kind of active management of provisioning or deployments, but rather we're going to focus on taking a look at the health, the status of the OpenShift V3 and Kubernetes entities, the health of the cluster, the state of it, the relationships of it, how a container connects to a pod, to a node, to the underlying infrastructure, utilization type information, and being able to identify issues in the environment. And now I'm going to actually turn it over to Serena to share with you our prototype. Okay. Great. Want to start sharing? Oh, sorry. Yep. Yes. And once again, if you have any questions, please feel free to use the chat. Okay. So I'm just going to start this off with, and et cetera is not appropriate, or is not in working mode right now or how it will be released. Essentially what we have is this is a prototype of what ManageIQ's navigation scheme is currently, when containers would be dropped into it. And the operational dashboards that I'm showing you are essentially what we have designed for the first deliverable of cloud forms, first deliverable of containers in cloud forms. And as you mentioned, we're trying to get feedback and validation with customers and then in the coming months to see if we can enhance it. We are limited by what's currently supported by Kubernetes at this point though. So there are a lot of things that I think you mentioned in the use cases, which we will be doing at further date, but some of those things were limited to and can't provide those right now. So just to give you a quick overview of the global dashboard, this is looking at your entire environment. So any of the container-related objects in your environment. So the top piece up, I'm going to show with my mouse, you can see my mouse going in here. You're not sharing it. I'm not sharing? No. It seems to me that I'm sharing. I can see your mouse moving. Can you see the dashboard as well? Yeah. Okay, great, thank you. So the top, there's about two, there's nine cards on the top, the top strip, I would call them. And essentially what they are, they're cards just trying to give you a quick overview of the container-related objects in your environment. So the first card on your left says that there's three providers currently in your environment. We have one that's an open shift and two Kubernetes providers. All of these things will be able, you can drill down into each of these items. So if you're not in the prototype but in the product, you'll be able to. So you'd be able to drill down into your single provider that's over open shift or you can drill down into your two Kubernetes providers. The next two cards are nodes and pods. So there's 52 nodes in this environment and three of which three with the error icon next to it. Means there's three nodes that have issues. You would be able to drill down into those and see the three specific nodes with issues as well in the product. Anything we have with pods, at this point we only have nodes and pods which are able to report back that they have errors or some status. So the rest of the six cards which are containers, services, registries, images, projects and routes, all we're able to do at this point for the first release is just say how many of those object types exist in your environment. So I'm going to pause for a moment and Dean Richardson had a question asking if this is CloudForms functionality anticipated for 3.1 or later release and our understanding that it's currently being planned for the 4.0 release at the end of this year is the current plan. Thank you. Okay, so I'm going to traverse to the lower, the middle, the middle left. One second for that question, hold on. Julian, I think he's actually is, Dean, can you please clarify? Do you mean 3.1 of OpenShift or do you mean 3.1 of CloudForms? Oh, sorry. Because we have a 3, OpenShift 3.1. It is, yes, I'm sorry. It is planned for the OpenShift 3.1 release because OpenShift 3.1 comes out around the same time as the CloudForms 4.0. It will come out before it. But the dashboards will be in managed. But that is correct. The functionality that you're seeing right now is going to be within CloudForms and not within OpenShift. Right, and that will all be part of Red Hat's cloud application suite as well. So you can get OpenShift and CloudForms separately, but you can also get Red Hat application suite, cloud application suite, sorry. And that will include, that will bundle together a whole bunch of stuff, but part of that will also be CloudForms and OpenShift. That's correct, yeah. Thank you. Okay, so on the middle part of the page on the left-hand side is node utilization. So we have two utilization charts, the first one's CPU. So what it's telling you, I'm gonna try to highlight this a little bit, is how much available you have. And then what the donut chart is depicting, the amount of used CPU. So what we're doing here is, we're showing the used inside the donut chart. We're coloring the chart based on two different thresholds. So the chart should be colored blue until you hit your warning threshold, which at this point we have 75%. And when it hits 75%, it's gonna turn orange, but then once it hits 90%, like in this case, it's 92, it turns red, just so that the user can visually quickly identify threshold usage or where you've met your thresholds. On the bottom of this card is essentially the Sparkline. So the last 30 days, what your CPU utilization has done for your nodes throughout the last 30 days. Then we have the same thing on the right-hand side, but it's from memory. So it's the same exact concept. The amount of available is up on the upper left. The amount used in the percentage is shown within the donut chart. And then underneath is the last 30 days with a Sparkline of usage. So we just want to pause and ask for any questions. And I know on the chat there were some questions that came up. One of the questions that came up is, will OpenShift have its own management console as well? Perhaps a stripped-down version of this. And in, with regards to that, OpenShift will have its own management console and it's targeted more towards a developer, whereas managed IQ or CloudForms is more targeted towards the operations person or administrator. Now, the second question was asked, by E&P, will you be providing support for installing OpenShift via CloudForms, i.e. within the Services tab? And the plan is yes. As of right now, CloudForms does support installing OpenShift v2. However, for v3, it is being planned, but I don't know the exact timelines yet. They're also talking about integrating OpenShift and deployment through RHCI install. That is correct, yeah. And let's see if I'm missing something else. Okay. Were there any other questions with regards to the prototype that you're seeing with some of the dashboards that Serena showed? I have a question. The node and memory utilization, that's showing utilization for both the entire environment, whether it's an OpenShift or Kubernetes provider like environment, correct? And this screen, yes, it is. But we're gonna show it. We will show you a provider-specific screen as well. Where it would be filtered. I'm gonna close. Okay. So I'm gonna quickly go and keep monitoring. There's actually one more question. This screen shows all the nodes. The nodes may be configured based on labels such as region zones and maybe more. Because can this UI drill down and categorize based on those labels? What were the labels again? So these are related to services. Not at this point. It is definitely in the works and plans. Okay, yeah, so remember that what we're looking at right now is just, it's all of your entire container environment, right? So I'm gonna quickly show again, the bottom is utilization per node. So this is showing CPU utilization. What we do here is we have one block to represent each node. The way that it's sorted at this point is the nodes with the highest CPU utilization is on the upper left and colored red. And then as you go down to the bottom right, you see the ones that have the most available. What we will also be able to do is you can hover over and see which you'd be able to see the node names. You can also drill down. So if you wanted to look at the ones with the most problems or highest utilization, you'd be able to drill down and see details of those specific nodes themselves. So again, at this point, we have this information available for CPU and memory. In future releases, once Kubernetes provides support, we'll also be including network and storage information in the same manner. Just to pause one more time. Thank you, Scott, for your kind comments. Nentioned he liked the dashboard. It looks, the look and feel is nice, easy to see, important top level information. Vera, Michonde had a question. Can we add capacity in new nodes based on threshold set for utilization? For example, CPU utilization raises 75% spin up node time. So with regards to that, and it sounds like it's being able to scale out or scale up type question, the plan is to have that capability within CloudForms and I believe also within OpenShift. And from being able to visualize the threshold, we don't currently have that, but it's something we have planned for later. And also to be able to set the threshold to your desired values. Well, that's the scaleability part and the policies. From Nicholas Schultz, will developers or users of OpenShift be able to gather stats from inside their Docker containers? Will they be able to monitor specific container performance? OpenShift better. From OpenShift, I'm not certain. Steve, would you know? Yeah, that is definitely on the dashboard. I mean dashboard. It's definitely on the timeline for something that we know developers need access to see what is happening inside of their containers. So yeah, the developer dashboard over time will have some of those metrics for your projects and stuff happening inside of your projects. Right, thank you. And Dean Richardson asked, will this demo environment be available for essays in the field? If not, can demo flows via screenshots be made available? Yes. Screenshots, yes. The demo environment, not yet. And so are we gonna share the presentation then? This is being recorded. Oh right, so they're- So you- Well in the deck, also in the deck that we've created, I've put these screenshots into that deck. Yeah, we can make the deck available as well. And we can put that in, we'll ask Diane where to put it. And then Jeff Hoffman has a question. When you scale down, will containers reorganize themselves across the environment or is this still a manual effort? That's a great question. I'm not really sure. I suspect it's a manual effort at this point. But Steve, would you know the answer to that question? Yeah, I don't know the specific answer to that question, but my guess would be that that's more of a Kubernetes functionality since it's in charge of scheduling, right? So it's gonna schedule what containers end up where. I don't know specifically though. Okay. And there's another question. Actually, I think Kevin Connor made a comment that there's work going on to integrate Hocular for retrieving metrics. Some of that is supposed to be present for OpenShift Enterprise 3.1. And that's with regards to being able to set thresholds in order to scale up. Let me see. There's another question from Veer. Can we use manage IQ to move the pods across nodes? Pods across nodes. That's a good question. I'm not sure just yet. I think that might be something that we can try to add to an ask product management to see that's something planned in the roadmap. And Kevin goes, not autoscaling that is currently being discussed with Google. The intention is to include this for autoscaling but likely OpenShift Enterprise 3.2. Thank you. All right, and then we move on. Okay, so I'm gonna go to the right half of the screen where we have four cards that are showing trends. The first one is network utilization and it's going to be a live chart. So what's gonna happen in the last 15 minutes? So you should be able to see this moving when you have your dashboard open. The next one is network utilization but over the last 30 days. So this chart will be actually very similar to what we have for memory and CPU. The reason we don't have a donut chart showing your percentage available or percentage used is because right now we don't know how much is available through Kubernetes. And the bottom two items are the total number of pods and the total number of images and their trends throughout the last 30 days. So you'll be able to see that again, it's just the total number, not the amount new or anything like that. It's the total number that are existing on each one of those days. So what I'm gonna go to next is the single provider. So for OpenShift, right? If you had a single OpenShift provider, the default view will be a dashboard or an overview. And it's essentially just the same thing as that global dashboard was, but it's filtered for this specific OpenShift provider. So again, we go through all the blocks but I already explained them all. I'm gonna go, is there a question? Yes, there is. From Veer Machandi, the question is, can we drill down to the individual quad levels to see what containers of pod is running? Would we be able to look at JVM metrics running inside a container? For example, there are assumptions that such features would be part of, would all be part of the CloudForms console. Okay, so one of the things that we don't have access to in this demo today is there's a whole set of inventory views. So if you look up in this prototype, if you look up to the top, container providers, projects, nodes, pods, roots, replicators, images, registries, services, and containers, all of those things have, we have inventory views for each of those. And yes, we'd be able to drill down from those directly from these areas. The caveat for us right now is that our dashboard prototype is in a different code location than where our inventory views are being developed. So we don't have the ability to go from one to the other in this specific concept. So just to expand on what Serena mentioned in these inventory views, they were shown at the Red Hat Summit recently. I don't know if it was recorded or not. Do you know? We can find out. It was in a mark. Yeah, I don't know. I'm not sure if there is, but one of the things we can do is have a follow-up discussion or presentation in this briefings to show those set of views to you. Now with regards to being able to look at JVM metrics running inside the container, I know the plan is to be able to do that. And I know from a Hocular perspective or a Fabric 8 perspective, they actually do have a working prototype that does that. I'm just not sure on the timelines on how some of these land inside OpenShift. Any other questions? Okay, so I'm just showing you the alternate where if it's a Kubernetes provider, you can see the same thing. At some point in the future, we will likely tailor the contents of these views to be a little bit different for the Kubernetes provider versus the OpenShift provider. But at this point today, we don't have those differences at this point. The final one I'm going to show you is the providers, I'm sorry, the project dashboard. So once you're looking at a single project, this is again what you'd be seeing from an overview perspective. Very similar layout, right? We have these cards again up on the top left, which are container-related objects. So you have an idea of how many of them are associated with the project that you're looking at in context. And then we have the same thing, node utilization. So this is CPU and memory utilization of the nodes that are associated with the project that you're looking at, as well as the heat maps again, utilization per node used by this project. We also have something a little bit different on the top right, which is quotas. And this piece up here might be reworked a little bit. We might have some additional items or take some off as well. But again, this is what we have currently. And then the bottom four cards are exactly the same trend cards that we had on the global dashboards. But again, they're filtered in context to the project that you're looking at. So are there any questions on the dashboard? Or comments? Or comments? Do folks have any thoughts around what they've seen or would like to see added? Are you grabbing those quotas from OpenShift directly or because you can also do quota management inside CloudForms today based on the, some wondering if there's a tie-in for that. So the next question, Lucy, with regards to the quotas, the quotas are actually the Kubernetes and OpenShift quotas, and they are not the quotas from CloudForms. Ian, P asks, do we have table views as well as graphs? Yes, and those are in those inventory views. So actually, if that's something that's of interest to this audience, we could ask Diane if she wanted us to come back and do another presentation and show you all the information that's available in the inventory views. But like I said, we don't have access to those at this moment. And we have another comment from Veer Machandi. Mountain persistent volumes to nodes could be a feature that can be added and monitoring usage of persistent volumes by OpenShift pods. I believe Serena mentioned the plan is longer term to have storage and networking be more a part of what you've seen in the dashboards today. Currently, we don't have that capability or visibility, but the plan is to actually include them. Any other comments or questions? Yeah, I had another question. One of the things you can do in CloudForms is customize the dashboard based on any data that CloudForms can collect. Is that something that is, I assume that's not available now, but is that in the plan? In the future, yes, that's a desire. The question is where, you know, what priority will that hold? Just to note that these dashboards are different than the containers, I'm sorry, than the CloudForms dashboard where the CloudForms dashboards are actually running on reports, right? This is a little bit different. These are completely fixed and there are no, at this point, there are no reports associated with each of the individual parts that are shown on the dashboard. And one of the things that we probably should mention is we're using slightly different technologies from the native CloudForms to actually generate this dashboard. So today, as Serena mentioned, they're not customizable, but in the future, they likely will be. Sorry, I'm just going back to the presentations. Do you see things moving around? So the last thing I wanted to show, if there was no more questions is there, and this isn't just a screenshot. Again, if we came back and wanted to show the inventory views, maybe we could get a live view of this prototype as well. So this is essentially a topology view, and it's just showing all of the container-related objects in a graph. At this point, for the first release, there's no plan to, well, we don't think that we'll be able to have highlighting, et cetera, of issues or errors or things being up or down, but that's something that we are talking about enhancing in the future. When pods or containers are created or instantiated, you see them automatically appear here, the way that they've implemented it at this time is they kind of jiggle around a little bit so your eye is brought to it and you can see it. This same topology view is going to be, or a very similar version, is going to be also included in satellite. Yeah, in cockpit. In cockpit. Sorry about that. So I don't know if anybody has any comments on this type of view as well. It seems like there's, people have strong stances for and against, so if anybody has any feedback, we'd love to hear on that as well. So while we wait for a few more questions, there are some questions from Judd at Dell, and the question is, can code push events be correlated with performance data? The answer to that is absolutely. We are collecting event data, and that is going to be in CloudForms or managed IQ, and whatever performance data that can be collected can be correlated as of right now because we don't have that much data. We're not able to produce those set of reports or charts to show, but that's something that we do plan for longer term. Now from Veer Machandi, the question is, or comment was pruning resources on nodes is another feature that will be useful for administrators if it's made available via this console? And we absolutely agree with you, and I believe that's part of the active management piece of lifecycle management of a containerized environment. And today, we don't yet have those set of use cases addressed, but it's something being planned. With regard to container update events, those are definitely related to code push events, and on the dashboard, do we have any? Not right now. Not right now. Sorry, I forget what we don't have. So that's something that we're planning for the future. And another comment from Veer is maybe coloring the node circles on the topology view based on usage labels, grouping related nodes by regions, zones, et cetera, will be useful. Yeah, so just so you know, yeah, we have been talking about how we design for usage because color, because of color blind issues, I'm not sure that we can just primarily count on the color itself, but we have definitely been talking about those concepts. Also how you filter by labels, et cetera, regions and zones. That's something that we've been talking about at this point, I don't wanna detract from what we've done here because I think it's great for a step, but at this point, all you can do is either toggle, you can toggle these types to be shown or not. So that's what this bar here is up here on the top left. If you don't wanna see your container groups, you can toggle it off, et cetera. So that filtering is pretty limited at this point, but it's definitely gonna be enhanced as we go along. Dominic, can you maximize that again, please? Oh, sure, I'm sorry. For folks who are looking at this presentation, how would you use this topology view? Do you have a need for such a view? In looking at this topology view, one of the things I think that would be nice is if you could show dynamic connections between services. Right, so I'm gonna see like, I can't quite, oh, so there's the node and it's got, there's this long graph coming out of the center of the middle left node. Where it's got a lot of stuff coming out of it. Do you see that one? Yeah, no, the one up. Up here, up here. No, oh, according to this graph, there's a node coming out of a node or they're connected through, they're on the same host? Is that what's happening? I don't get that graph. But anyway. I think it's a little confusing right now. Yeah, so this host has two VMs associated, right? Yeah. And then, so you're asking about this node here. Well, what I was actually talking about more, I thought that was actually one node and a long graph coming off of it with a lot of services. Okay. If services are talking to each other, it would be good as the admin to know what services are talking to which services and how much data is flowing between them. And some other dashboards I've used, these are more application developer dashboards. You can actually see like how much data is flowing from your app servers to your database, right? But I would imagine as an admin, if there's a bunch of nodes talking to a bunch of other nodes or services, even within the same node talking to each other, you might want to move those to other nodes because you wanna share the load around, you don't want it all on one node. It's just something I think the interaction between the nodes is, between the endpoints of the graph is important. Yes, we've heard that and that's something that we're definitely planning. Let me ask you this, would it be better to have the services or a specialized view that's more targeted between these service endpoints to actually see that information? Or would you still want to see it with all these other entities connected to it? I would imagine for sure you'd wanna see it on a node, but on a node basis as well though, right? Because it's not just which, I do wanna see which services talking to which service, but as an admin, I would imagine I would also wanna see, are these co-located on the same node? Are they in the same district? Like I would wanna know more of how that, I don't know that I need all the graphs, it's kinda hard, let's see containers. I think I'd probably wanna, I think I'd kinda wanna see all of that stuff. Maybe they've become smaller or something, but you'd still wanna be able to know, are they happening on the same machines or what's the relationship between quote unquote machines? But I'll leave that to other people to say it. Some of the other things we're talking about is being able to put something in, like more in context. So you wanna see your environment based on a specific node or on a specific, hierarchy potentially. And so it would kind of fade everything out, but it'd bring up any of the relationships associated with that one object in the front. So that's another thing that the future we're talking about in Florentine. And just to pause for one moment, Bob, because Demba had a question, can the topology view be cropped and zoomed? Not at this point. That is the intention going forward. I mean, we would not promise that for the first release, say that. Right, I think one of the caveats we probably should mention is this topology view is sort of an early concept for it. And we're still in very early stages of it. We'd definitely love to get more input on it. And so if you have any additional comments, we'd love to hear them or things that we ought to be doing. Actually, for this specific view at ContainerCon next week, Alyssa bonus from Red Hat is going to be demoing this live. So I don't know if anybody is there. Hope you're going to see that. Right. And that's next week at ContainerCon in Seattle. Bob also mentioned this topology view will be useful for large environments. Vera asked, it is showing containers at the bottom level. Is that a pod? Oh, yeah. One of the things we should mention in the topology view is that where you see the word container groups, that's actually pods. And we have some terminology things that we still have to update. And somebody asked a question, combined topology with heat, if not already. We've heard that. And thank you for that comment. So that was the last slide that we had in our deck. Again, I'm not sure if there's any other comments. We'd be happy to answer them. Otherwise, I think we can pass it back on to Steve. One comment. When you have the type of container info, perhaps the container can indicate what is running there. That's right. So one of the things to mention in the live demo is that we actually do have some views where if you're clicking on the object, you can actually see details information about the object. So for example, if you're clicking on a container, you should be able to see information about the image and other information about the containers. And because we don't have the live working prototype, we're not able to show that to you, but I believe there is a cockpit recording that actually does show that. And if folks are interested in that recording, we're happy to send the link to you. I'm gonna type in our email address in the chat and please feel free to reach out to us if you'd like. And if you have any additional comments or questions. Okay, it looks like we're done. Give it one more second. Okay, thanks. Those dotted lines, I'm sorry. Those dotted lines, what were they for? Were they for just services only? In that topology view? I think in that topology view, some of them only had dotted lines, not solid lines. Sorry. No, I have to share. You have to share, because I don't think anyone can see. No, no, no, thank you. We're trying to get the image shared again. Yes, I believe those dotted lines basically means we've lost connection to it or something is unavailable. And that's the same thing of the ones that are not connected, I guess. They're either not connected or a friend or they've lost connection. There could be a number of different reasons. And would I, if I hover over like the containers and the nodes and services, would I be able to see the actual names of them or they like any more detailed info, like if I hover over them? Yeah, at this point, you see the name. What we're trying to do and I'm not sure how much will be done for this first release or not. There's also a design that when you select one, you'll see all of the associated information on the right. There'd be like a details panel that shows up, which shows you all the information associated with it. Isn't the cockpit already implemented? Okay, so if you look at some of the cockpit recordings and I believe those are already in the public space, you should be able to see that information. And this topology view is actually based on that implementation that was done in the cockpit. So some of these capabilities will be coming. Okay, thank you. Thank you. Any other questions, comments? And viewer, thank you. And thank you everybody for taking the time out of your busy schedule to take a look at what we had to share. Yep, thanks, Julianne and Serena. We'll be posting this, we will, I'll say we, I mean, Diane. Diane will be posting this up on YouTube. And again, thanks for showing us some of the exciting things coming for Kubernetes and OpenShift. Thank you very much. Thank you. Have a great day. Bye bye.