>>Hello, everyone. My name is Rick Pew. I'm a senior product manager at Mirant. This and I have been working on the Doctor Enterprise Container Cloud for the last eight months. Today we're gonna be talking about multi cloud kubernetes. So the first thing to kind of look at is, you know, is multi cloud rial. You know, the terms thrown around a lot and by the way, I should mention that in this presentation, we use the term multi cloud to mean both multi cloud, which you know in the technical sense, really means multiple public clouds and hybrid cloud means public clouds. And on Prem, uh, we use in this presentation will use the term multi cloud to refer to all different types of multiple clouds, whether it's all public cloud or a mixture of on Prem and Public Cloud or, for that matter, multiple on Prem clouds as doctor and price container. Cloud supports all of those scenarios. So it really well, let's look at some research that came out of flex era in their 2020 State of the cloud report. You'll notice that ah, 33% state that they've got multiple public and one private cloud. 53% say they've got multiple public and multiple private cloud. So if you have those two up, you get 86% of the people say that they're in multiple public clowns and at least one private cloud. So I think at this stage we could say that multi cloud is a reality. According to 4 51 research, you know, a number of CEO stated that the strong driver their desire was to optimize cost savings across their private and public clouds. Um, they also wanted to avoid vendor lock in by operating in multiple clouds and try to dissuade their teams from taking too much advantage of a given providers proprietary infrastructure. But they also indicated that there the complexity of using multiple clouds hindered the rate of adoption of doing it doesn't mean they're not doing it. It just means that they don't go assed fast as they would like to go in many cases because of the complexity. And here it Miranda's. We surveyed our customers as well, and they're telling us similar things, you know. Risk management, through the diversification of providers, is key on their list cost optimization and the democratization of allowing their development teams, uh, to create kubernetes clusters without having to file a nightie ticket. But to give them a self service, uh, cloud like environment, even if it's on prem or multi cloud to give them the ability to create their own clusters, resize their own clusters and delete their own clusters without needing to have I t. Or of their operations teams involved at all. But there are some challenges with this, with the different clouds you know require different automation. Thio provisioned the underlying infrastructure or deploy and operating system or deployed kubernetes, for that matter, in a given cloud. You could say that they're not that complicated. They all have, you know, very powerful consoles and a P I s to do that. But did you get across three or four or five different clouds? Then you have to learn three or four or five different AP ice and Web consoles in order to make that happen on in. That scenario is difficult to provide self service for developers across all the cloud options, which is what you want to really accelerate your application innovation. So what's in it for me? You know We've got a number of roles and their prizes developers, operators and business leaders, and they have somewhat different needs. So when the developer side the need is flexibility to meet their development schedules, Number one you know they're under constant pressure to produce, and in order to do that, they need flexibility and in this case, the flexibility to create kubernetes clusters and use them across multiple clouds. Now they also have C I C D tools, and they want them to be able to be normalized on automated across all of the the on prim and public clouds that they're using. You know, in many cases they'll have a test and deployment scenario where they'll want to create a cluster, deploy their software, run their test, score the tests and then delete that cluster because the only point of that cluster, perhaps, was to test ah pipeline of delivery. So they need that kind of flexibility. From the operator's perspective, you know, they always want to be able to customize the control of their infrastructure and deployment. Uh, they certainly have the desire to optimize their optics and Capex fans. They also want to support their develops teams who many times their their customers through a p I access for on Prem and public clouds burst. Scaling is something operators are interested in, and something public clouds can provide eso the ability to scale out into public clouds, perhaps from there on prem infrastructure in a seamless manner. And many times they need to support geographic distribution of applications either for compliance or performance reasons. So having you know, data centers all across the world and be able to specifically target a given region, uh, is high on their list. Business leaders want flexibility and confidence to know that you know, they're on prim and public cloud uh, deployments. Air fully supported. They want to be able, like the operator, optimize their cloud, spends business leaders, think about disaster recovery. So having the applications running and living in different data centers gives them the opportunity to have disaster recovery. And they really want the flexibility of keeping private data under their control. On on Prem In certain applications may access that on Prem. Other applications may be able to fully run in the cloud. So what should I look for in a container cloud? So you really want something that fully automates these cluster deployments for virtual machine or bare metal. The operating system, uh, and kubernetes eso It's not just deploying kubernetes. It's, you know, how do I create my underlying infrastructure of a VM or bare metal? How do I deploy the operating system? And then, on top of all that, I want to be able to deploy kubernetes. Uh, you also want one that gives a unified cluster lifecycle management across all the clouds. So these clusters air running software gets updated. Cooper Netease has a new release cycle. Uh, they come out with something new. It's available, you know, How do you get that across all of your clusters? That air running in multiple clouds. We also need a container cloud that can provide you the visibility through logging, monitoring and alerting again across all the clouds. You know, many offerings have these for a particular cloud, but getting that across multiple clouds, uh, becomes a little more difficult. The Doctor Enterprise Container cloud, you know, is a very strong solution and really meets many of these, uh, dimensions along the left or kind of the dimensions we went through in the last slide we've got on Prem and public clouds as of RG A Today we're supporting open stack and bare metal for the on Prem Solutions and AWS in the public cloud. We'll be adding VM ware very soon for another on Prem uh, solution as well as azure and G C P. So thank you very much. Uh, look forward, Thio answering any questions you might have and we'll call that a rap. Thank you. >>Hi, Rick. Thanks very much for that. For that talk, I I am John James. You've probably seen me in other sessions. I do marketing here in Miran Tous on. I wanted to to take this opportunity while we had Rick to ask some more questions about about multi cloud. It's ah, potentially a pretty big topic, isn't it, Rick? >>Yeah. I mean, you know, the devil's in the details and there's, uh, lots of details that we could go through if you'd like, be happy to answer any questions that you have. >>Well, we've been talking about hybrid cloud for literally years. Um, this is something that I think you know, several generations of folks in the in the I. A s space doing on premise. I s, for example, with open stack the way Miran Tous Uh does, um, found, um, you know, thought that that it had a lot of potential. A lot of enterprises believed that, but there were There were things stopping people from from making it. Really, In many cases, um, it required a very, ah, very high degree of willingness to create homogeneous platforms in the cloud and on the premise. Um, and that was often very challenging. Um, but it seems like with things like kubernetes and with the isolation provided by containers, that this is beginning to shift, that that people are actually looking for some degree of application portability between their own Prem and there and their cloud environments. And that this is opening up, Uh, you know, investment on interest in pursuing this stuff. Is that the right perception? >>Yeah. So let's let's break that down a little bit. So what's nice about kubernetes is through the a. P. I s are the same. Regardless of whether it's something that Google or or a W s is offering as a platform as a service or whether you've taken the upstream open source project and deploy it yourself on parameter in a public cloud or whatever the scenario might be or could be a competitor of Frances's product, the Kubernetes A. P I is the same, which is the thing that really gives you that application portability. So you know, the container itself is contained arising, obviously your application and minimizing any kind of dependency issues that you might have And then the ability to deploy that to any of the coup bernetti clusters you know, is the same regardless of where it's running, the complexity comes and how doe I actually spend up a cluster in AWS and open stack and D M Where and gp An azure. How do I build that infrastructure and and spin that up and then, you know, used the ubiquitous kubernetes a p I toe actually deploy my application and get it to run. So you know what we've done is we've we've unified and created A I use the word normalized. But a lot of times people think that normalization means that you're kind of going to a lowest common denominator, which really isn't the case and how we've attacked the the enabling of multi cloud. Uh, you know, what we've done is that we've looked at each one of the providers and are basically providing an AP that allows you to utilize. You know, whatever the best of you know, that particular breed of provider has and not, uh, you know, going to at least common denominator. But, you know, still giving you a ah single ap by which you can, you know, create the infrastructure and the infrastructure could be on Prem is a bare metal infrastructure. It could be on preeminent open stack or VM ware infrastructure. Any of the public clouds, you know, used to have a a napi I that works for all of them. And we've implemented that a p i as an extension to kubernetes itself. So all of the developers, Dev ops and operators that air already familiar operating within the, uh, within the aapi of kubernetes. It's very, very natural. Extension toe actually be able to spend up these clusters and deploy them >>Now that's interesting. Without giving away, obviously what? Maybe special sauce. Um, are you actually using operators to do this in the Cooper 90? Sense of the word? >>Yes. Yeah, we've extended it with with C R D s, uh, and and operators and controllers, you know in the way that it was meant to be extended. So Kubernetes has a recipe on how you extend their A P I on that. That's what we used as our model. >>That, at least to me, makes enormous sense. Nick Chase, My colleague and I were digging into operators a couple of weeks ago, and that's a very elegant technology. Obviously, it's a it's evolving very fast, but it's remarkably unintimidating once you start trying to write them. We were able toe to compose operators around Cron and other simple processes and just, >>you know, >>a couple of minutes on day worked, which I found pretty astonishing. >>Yeah, I mean, you know, Kubernetes does a lot of things and they spent a lot of effort, um, in being able, you know, knowing that their a p I was gonna be ubiquitous and knowing that people wanted to extend it, uh, they spent a lot of effort in the early development days of being able to define that a p I to find what an operator was, what a controller was, how they interact. How a third party who doesn't know anything about the internals of kubernetes could add whatever it is that they wanted, you know, and follow the model that makes it work. Exactly. Aziz, the native kubernetes ap CSTO >>What's also fascinating to me? And, you know, I've I've had a little perspective on this over the past, uh, several weeks or a month or so working with various stakeholders inside the company around sessions related to this event that the understanding of how things work is by no means evenly distributed, even in a company as sort of tightly knit as Moran Tous. Um, some people who shall remain nameless have represented to me that Dr Underprice Container Cloud basically works. Uh, if you handed some of the EMS, it will make things for you, you know, and this is clearly not what's going on that that what's going on is a lot more nuanced that you are using, um, optimal resource is from each provider to provide, uh, you know, really coherent architected solutions. Um, the load balancing the d. N s. The storage that this that that right? Um all of which would ultimately be. And, you know, you've probably tried this. I certainly have hard to script by yourself in answerable or cloud formation or whatever. Um, this is, you know, this is not easy work. I I wrote a about the middle of last year for my prior employer. I wrote a dip lawyer in no Js against the raw aws a piece for deployment and configuration of virtual networks and servers. Um, and that was not a trivial project. Um, it took a long time to get thio. Uh, you know, a dependable result. And to do it in parallel and do other things that you need to do in order to maintain speed. One of the things, in fact, that I've noticed in working with Dr Enterprise Container Cloud recently, is how much parallelism it's capable of within single platforms. It's It's pretty powerful. I mean, if you want to clusters to be deployed simultaneously, that's not hard for Doc. Aerated price container cloud to dio on. I found it pretty remarkable because I have sat in front of a single laptop trying to churn out of cluster under answerable, for example, and just on >>you get into that serial nature, your >>poor little devil, every you know, it's it's going out and it's ssh, Indian Terminals and it's pretending it's a person and it's doing all that stuff. This is much more magical. Um, so So that's all built into the system to, isn't it? >>Yeah. Interesting, Really Interesting point on that. Is that you know, the complexity isn't not necessarily and just creating a virtual machine because all of these companies have, you know, spend a lot of effort to try to make that as easy as possible. But when you get into networking, load balancing, routing, storage and hooking those up, you know, two containers automating that if you were to do that in terror form or answerable or something like that is many, many, many lines of code, you know, people have to experiment. Could you never get it right the first or second or the third time? Uh, you know, and then you have to maintain that. So one of the things that we've heard from customers that have looked a container cloud was that they just can't wait to throw away their answerable or their terror form that they've been maintaining for a couple of years. The kind of enables them to do this. It's very brittle. If if the clouds change something, you know on the network side, let's say that's really buried. And it's not something that's kind of top of mind. Uh, you know, your your thing fails or maybe worse, you think that it works. And it's not until you actually go to use it that you notice that you can't get any of your containers. So you know, it's really great the way that we've simplified that for the users and again democratizing it. So the developers and Dev ops people can create these clusters, you know, with ease and not worry about all the complexities of networking and storage. >>Another thing that amazed me as I was digging into my first, uh, Dr Price container Cloud Management cluster deployment was how, uh, I want I don't want to use the word nuanced again, but I can't think of a better word. Nuanced. The the security thinking is in how things air set up. How, um, really delicate the thinking about about how much credential power you give to the deploy. Er the to the seed server that deploys your management cluster as opposed thio Um uh or rather the how much how much administrative access you give to the to the administrator who owns the entire implementation around a given provider versus how much power the seed server gets because that gets its own user right? It gets a bootstrap user specifically created so that it's not your administrator, you know, more limited visibility and permissions. And this whole hierarchy of permissions is then extended down into the child clusters that this management cluster will ultimately create. So that Dev's who request clusters will get appropriate permissions granted within. Ah, you know, a corporate schema of permissions. But they don't get the keys to the kingdom. They don't have access to anything they don't you know they're not supposed to have access to, but within their own scope, they're safe. They could do anything they want, so it's like a It's a It's a really neat kind of elegant way of protecting organizations against, for example, resource over use. Um, you know, give people the power to deploy clusters, and basically you're giving them the power toe. Make sure that a big bill hits you know, your corporate accounting office at the end of the billing cycle, um so there have to be controls and those controls exist in this, you know, in this. >>Yeah, And there's kind of two flavors of that. One is kind of the day one that you're doing the deployment you mentioned the seed servers, you know, And then it creates a bastion server, and then it creates, you know, the management cluster and so forth, you know, and how all those permissions air handled. And then once the system is running, you know, then you have full access to going into key cloak, which is a very powerful open source identity management tool on you have dozens of, you know, granular permissions that you can give to an individual user that gives them permission to do certain things and not others within the context of kubernetes eso. It's really well thought out. And the defaults, you know, our 80% right. You know, there's very few people are gonna have to go in and sort of change those defaults. You mentioned the corporate directory. You know, hooks right upto l bap or active directory can suck everybody down. So there's no kind of work from a day. One perspective of having to go add. You know everybody that you can think of different teams and groupings of of people. Uh, you know, that's kind of all given from the three interface to the corporate directory. And so it just makes kind of managing the users and and controlling who can do what? Uh, really easy. And, you know, you know, day one day two it's really almost like our one hour to write because it's just all the defaults were really well thought out. You can deploy, you know, very powerful doctor and price container cloud, you know, within an hour, and then you could just start using it. And you know, you can create users if you want. You can use the default users. That air set up a time goes on, you can fine tune that, and it's a really, really nice model again for the whole frictionless democratization of giving developers the ability to go in and get it out of, you know, kind of their way and doing what they want to do. And I t is happy to do that because they don't like dozens of tickets and saying, you know, create a cluster for this team created cluster for that team. You know, here's the size of these guys. Want to resize when you know let's move all that into a self service model and really fulfill the prophecy of, you know, speeding up application development. >>It strikes me is extremely ironic that one of the things that public cloud providers bless them, uh, have always claimed, is that their products provide this democratization when in the experience, I think my own experience and the experience of most of the AWS developers, for example, not toe you know, name names, um, that I've encountered is that an initial experience of trying to start start a virtual machine and figuring out how to log into it? A. W s could take the better part of an afternoon. It's just it's not familiar once you have it in your fingers. Boom. Two seconds, right. But, wow, that learning curve is steep and precipitous, and you slip back and you make stupid mistakes your first couple 1000 times through the loop. Um, by letting people skip that and letting them skip it potentially on multiple providers, in a sense, I would think products like this are actually doing the public cloud industry is, you know, a real surface Hide as much of that as you can without without taking the power away. Because ultimately people want, you know, to control their destiny. They want choice for a reason. Um, and and they want access to the infinite services And, uh, and, uh, innovation that AWS and Azure and Google are all doing on their platforms. >>Yeah, you know, and they're solving, uh, very broad problems in the public clouds, you know, here were saying, you know, this is a world of containers, right? This is a world of orchestration of these containers. And why should I have to worry about the underlying infrastructure, whether it's a virtual machine or bare metal? You know, I shouldn't care if I'm an application developer developing some database application. You know, the last thing I wanna worry about is how do I go in and create a virtual machine? Oh, this is running. And Google. It's totally different than the one I was creating. An AWS I can't find. You know where I get the I P address in Google. It's not like it was an eight of us, you know, and you have to relearn the whole thing. And that's really not what your job is. Anyways, your job is to write data base coat, for example. And what you really want to do is just push a button, deploy a nor kiss traitor, get your app on it and start debugging it and getting it >>to work. Yep. Yeah, it's It's powerful. I've been really excited to work with the product the past week or so, and, uh, I hope that folks will look at the links at the bottoms of our thank you slides and, uh, and, uh, avail themselves of of free trial downloads of both Dr Enterprise Container, Cloud and Lens. Thank you very much for spending this extra time with me. Rick. I I think we've produced some added value here for for attendees. >>Well, thank you, John. I appreciate your help. >>Have a great rest of your session by bike. >>Okay, Thanks. Bye.

>>from around the globe. It's the Cube with digital coverage of Miranda's launchpad 2020 brought to you by more antis. >>Hi, I'm stupid man. And this is the cubes coverage of Miran Tous Launchpad 2020. Happy to welcome to the program First time guest William Do places. He's the head of customer success in operations with Miran Tous William. Thanks so much for joining us, >>Steve. Thanks for two. Thanks for having me. >>Yeah, why don't we start with a little bit? You know, customer success operations. Tell us what that's entail, What's what's under your purview, Right? >>So is everything basically, you know, post sales, right? So after a customer has portions, their their subscription, we basically take it from there Going forward, you know, looking after the relationship with the customer, ensure they you know, the whole, you know, subscription fulfillment element off it. Whether that is just bored with that is to cut the relationship management from a post sales perspective and so on, so forth. So that is basically into end from the point off purchase to the renewal face. Would would would fall with any supporting operations. >>Well, that's such an important piece of the whole cloud conversation. Of course, people, you know, we talked for such a long time cap ex op X. We talk about descriptions and manage services. Of course, has been a riel. You know, growth segment of the market place. Love to hear a little bit, you know, What are you hearing from your customers? And, you know, give us the lay of the land As to the various options that that that Miranda is offering today and we'll get into any of the new pieces also. >>Yeah. So the the the options that we're making available for our customers primary called Prod Care, which is a 24 7 mission critical support subscription. Andi Ops Care, which is a fully managed service offering. Um, what we hear from our customers is is, you know, the the the notion of having a development environment and a production environment with different, you know, sls and entitlements and so on. You know that that that notion is disappearing because your divots chain or pipeline is all connected. So you could just think for yourself. If you have a group of developers like 50 or 100 or 1000 developers that are basically standing there still, because they cannot push code because there's a problem or a new issue on the development cloud. But the development cloud is not. Beings is not seen or is treated as a mission critical platform. You know, those developers are standing date stole, so that is a very expensive problem for a customer at that point in time, so that the whole chain, the whole pipeline that makes part off your your develop cycle, should be seen as one entity. And that's what we've seen in the market at the moment that we're realizing with a large customers that are really embracing the kind of the approach to modern applications. Andi. This is why we're making these options available. Thio, our Doctor Enterprise customers We've been running with them for quite a while on the on the Miranda's cloud platform, which is our Infrastructures service offering on. We've had some great success with that, and we now in a position to make that available to our customers. So it's really providing a customer that true enterprise mission critical regardless of time off they the day of the week availability off support whether that is a my question or whether that is really an outage or a failure. You know, you know, you've got that safety net that is that is online and available for you. Thio to sort Whatever problem you have about, you know, that is from the support perspective, you know. And if we go over into the manage service offering we have for on up Skate that is a really hardened Eitel based, um infrastructure or platform as a service offering that we provide eso. We've had some great success. Like I said on the on the Miranda's cloud platform Peace. And we're now making that available for Doc Enterprise customers as well. So that is taking the whole the whole chain through. We look after the the whole platform for the customer and allow the customer to get on with what is important to them. You know, how do they develop their applications? You know, optimize that for their business instead, off spending their times and keep spending their time on keeping the lights on, so to speak, you know? So we take care of all of that. They have that responsibility over to us on DWI. We manage that as our own and we basically could become an extension of their business. So we have a fully integrated into the environment, the whole logging and not monitoring piece we take over the whole life cycle. Management off the environment. We take over, we do the whole change Management piece Incident Management Incident Management piece on. This whole process is truly transparent to the customer. At no point are they, you know, in the dark what's going on where we're going and we have the and the whole pieces wrapped around Bio customer success Manager which is bringing this whole sense off ownership Onda priority. That customer, you've got a single point of contact that is your business partner and that the only piece, the only metric that that individuals measured on is the success off that customer with our our product. So that in a nutshell, at a very high level what these are. But these offerings are all about >>well, we all know these days how important it is toe, you know, make your developers productive. It's funny listening to you, I think back to the Times where you talked about making sure that it's mission critical environment You know, years ago it was like, Oh, well, the developer just gets whatever old hardware we have, and they do it on their own. Now, of course, you know you want Dev in production toe have a very similar environment. And as you said, those manage services offering and be, you know, so important because we want to be able to shift left, let my platform let my vendors take care of some of the things that's gonna be able to enable me to build my new applications toe, respond to the business and do. In fact, I don't want my developers getting bogged down. So do you have any, You know, what are some of the successes there? How do your customers measure that? They Hey, I'm getting great value for going to manage service. Obviously, you know, you talked about that, That technical manager that helps them there. Anybody that's used, you know, enterprise offerings. There's certain times where it's like, Hey, I use it a lot. Other times it's it's just nice to be there, but, you know, why do you bring us in a little bit? Some of the customers, obviously anonymous. You need Teoh you know, how do they say, You know, this is phenomenal value for my business. >>Yes, it's all. It's all about the focus, right? So you're the customer. 100% focus on what is like I said, important to them, they are not being distracted at any point for, you know, on spending time on infrastructure related or platform related issues they purely focused on. Like I said, that is, that is important to their business. Andi, The successes that we see from that it is, is that we have this integration into into our customers like a seamless approach. We work with them is a true, transparent approach to work with our customers. There's a there's an active dialogue off what they developers want to see from the environment, what the customers want to see from from from the environment, what is working well, what we need to optimize. And that is really seeing ah, really good a approach from from from us and we're seeing some some great successes in it. But it all comes down to the customer is focusing on one thing, and that is on what is important to them on. But is there business instead off. You know, like you said, focusing on the stuff that shoot me, that that should be shift left. >>Yeah. And will, um, is there anything that really stands out when you talk about that? The monitoring that you in the reporting that you give the customers Is it all self serve? You know, how did they set that up and make sure that I'm getting valuable data. That's what what my company needs. >>Yes. So that is where your custom success manager comes in is really how to customize that approach to what fit for the customers. So we've got it in the background, very much automated, but we do the tweaks Thio customize it for for the customer that makes sense for them. Some customers want to see very granular details. Other customers just want a glance over it and look at the the high level metrics what they find important. So it is finding that balance and and understanding what your customer find important, and then put that in a way that makes sense for them Now. That might sound might sound kind of obvious, but it's more difficult than you think to put data from the customer That makes sense to them, uh, in their in their context. And then, you know, be in a position where you can take the information that you receive and give your customer the the runway to plan their the application. You know, where are they trending? So be able. Dutilleux. Look. 3452 quarters 345 months to quarters ahead to say this is where you're going to be. If you continue down this path, we might need to look at shifting direction or shift workload around or at Resource is or or, you know, depending on the situation. But it's all about having that insight going forward, looking forward. Rather, um, instead off, you know, playing things by year end, looking, looking at the year. And now because then that ISS that is done and dusted, really. So it's all about what is coming down the line for us and then be able to to plan for it and have an educated conversation of with with with your customer where they want to go. >>You mentioned that part of this offering is making this available for the Docker Enterprise base. Uh, maybe, if you could explain a little bit as to you know, what's gonna be compelling for for those customers. You know what Laurentis is has built specifically for that base? >>Yeah. So, like I said, this is an offering we have available on our Miranda's cloud platform for quite a while. You've seen some great success from it. Um, we're making it now available for the Doctor Enterprise customers. So it is really a true platform as a service offering, um, on your infrastructure of choice, whether that is on prim or whether that is on public cloud, we don't really care. We'll work with customers whichever way it is. And yeah, Like I said, just give that true platform as a service experience for our customers, Onda allow them to to focus on what's important to them. >>Alright, let me let you have the final word. Will tell us what you want your customers to understand about Iran tous when they leave launchpad this year. >>Yeah, So the main thing the main theme that I want to leave with is is that you know, the the we've made significant progress over the last 62 229 months on the doc enterprise side on. We're now in a position where we're taking the next step in making these offerings available for our customers, and we're really for the customers. That's the handful of custom that we have already. My greater to these offerings with getting some really good feedback from them on it is really helping them just thio thio just to expedite. They they, you know, wherever they're gonna go, whatever they want to want to achieve the, you know, expedite, think goals on bond. It is really there to ensure that we provide a customer or customers a true, um, you know, mission critical feeling, uh, giving them the support they need when they needed at the priority or the severity or the intensity that they need as well as they provide them. The ability to to focus on what is important to them on board. Let us look after the infrastructure and platform for them. >>Well, well, okay. Congratulations on Although the work that the team's done and definitely look forward to hearing more in the future. >>Excellent. Thank you very much for your time. >>Be sure to check out all the tracks for Miranda's launchpad 2020 of course. Powered by Cuba 3. 65. Got the infrastructure. The developers Lots of good content. Both live and on demand. And I'm still minimum. Thank you for watching. Thank you.