>> Announcer: From around the globe, it's theCUBE, with digital coverage at Mirantis Launchpad 2020, brought to you by Mirantis. >> Welcome back. And I'm Stu Miniman, and this is theCUBE's coverage of Mirantis Launchpad 2020. Of course we're spending a lot of time talking about Kubernetes. We're going to be digging in talking about some of the important developer tooling that Mirantis is helping to proliferate in the market, solve some real important challenges in the space. So happy to welcome to the program Miska Kaipiainen. He is the senior director of engineering with Mirantis. Miska, thanks so much for joining us. Welcome to theCUBE. >> Thank you so much. >> All right, so Miska, I notice you've got on the Kontena sweatshirt. You were the founder of the company, did some tools. One of the tools that you and your team helped create was Lens. You and your team joined Mirantis, and recently Lens was pulled in. So maybe if you could just give us a little bit about your background. You do some coding yourself, the team that you have there, and let's tee up the conversation, 'cause it's that Lens piece that we're going to spend a bunch of time talking about. >> Yeah, so the background of what we did, basically Kontena, we started back in 2015, and we a the focus on creating technologies around the container orchestration technologies to basically to make developer tooling that are very easy to use for the developers. So during the years at Kontena, we did many different types of products, and maybe the most interesting product that we created was Lens. And now really when we joined Mirantis in January this year, so we have been able to work on Lens, and actually, since the Lens was made open source, fully open source in March this year, so it's been really kind of picking up, and now Mirantis acquired the whole technology, so we can really start investing even more in the development. >> All right, so let's talk specifically about Lens. As I teed up at the beginning, we're talking about managing multiple clusters. Gosh, and I think back to 2015. It was early on. Most people were still learning about Docker, Docker swarms, Kubernetes, Mesos. There were a lot of fights over how orchestration would be done. A little bit different discussion about what developers were doing, how they scaled out configurations, how they manage those. So help us understand kind of that core, what Lens does, and how the product has matured and expanded over those last five years. >> Yeah, so over the last five years, so originally Lens was developed for our internal product. So like Mesosphere and Docker, and they all have their own orchestration technologies even before Kubernetes. And we also started working on our own orchestration technology. And I'm a huge believer in when we are dealing with very complex technologies, so if you can visualize it and make it kind of more interesting to look at, so it will kind of help with the adoption, and it's kind of more acceptable to the market. And that's why we started doing Lens. And over the years, we turned Lens to work with Kubernetes environments, and nowadays really Lens is very much loved by the Kubernetes developers, who are those people who need to deal with the Kubernetes clusters on a daily basis. So they are not necessarily those ops people who are creating those clusters , but they are the people who actually use those clusters. >> Well, of course that that general adoption is something that, you know, super important. You have some stats you can share on, you talk about the love of developers. You said it's open source, it's available on GitHub, but how many people are using it? What are some of those usage stats? >> Yeah, so it was interesting. So when we released Lens open source under MIT license in March, so since then we have been getting, in half a year, we have been getting 8,000 stargazers on GitHub. That is kind of mind-blowing because we try to create projects and trying to create anything that would get a lot of traction in the past, but truly, it totally happened just now after years of trying. So it has been since the last six months, it's been just amazing the adopts and we have more than 50,000 users using Lens and the retention is great. People keep on coming back. So yeah, the numbers look very, very good for Lens, and we are just getting started. >> Yeah, well, it's something that this community definitely is huge growth, and anybody in this space remembers just the huge adoption of Docker, which of course the enterprise piece of Docker is now part of Mirantis. Inside those developers, help us understand a little bit more, what is it that has them really not only looking at the GitHubs, starring it, as you said, they're the stargazers. It's like a favorite, for those that aren't in the system. I've had a chance to look at some of the demos, and it seems rather straightforward. But if you could, just in your words, explain what it is that it solves for developers that otherwise they either had to do themselves or they had to cobble together a lot of different tools. We know developers out there. The wonderful thing is there's no shortage of tools to choose from. It's about the right tool that can do the right thing. >> Absolutely, absolutely. So Lens, we are calling it IDE for a reason. So we are talking about IDE for Kubernetes developers. And what does it mean actually is that we are taking all those necessary tools and technologies and packaging them, integrating them seamlessly together for the purpose of making it more easy for developers to deploy, operate, observe, inspect their workloads that are running on Kubernetes clusters. And I think the main benefits that Lens will provide for these developers is that if you're a newcomer in the Kubernetes ecosystem, so Lens gives you a very easy way to learn Kubernetes because it's so visual. And for more experienced users, it just radically improves the, let's say the speed of business and the way how you can perform things with your clusters. >> So one of the pieces that that Lens does is that multi-cluster management. So first of all, I believe, as you said, it's open source and can work with, is it any certified Kubernetes out there, whether it be from the public cloud, companies like VMware and Red Hat that have Kubernetes, of course, Mirantis has Kubernetes, too. And secondly, I think you teased out a little bit, but help help us understand a little bit. Multi-cluster management is something that the big players, you hear Azure and Google Cloud talking about how they look at managing not only other environments, but oh yeah, we can have other clusters and we can help you manage it. I think that's more on the ops side of things, as opposed to, as you said, this is really a developer tool set. >> Yeah, so of course, all the organizations, they want to most likely have some sort of centralized system where they can manage multiple clusters, and some companies provide systems for on-premises, and some public cloud vendors, they provide systems for provisioning those clusters on their own own systems. And then we have also the kind of multicloud management systems. Most of these technologies, they are really designed for the operations side, so how the IT administrations can manage these multiple clusters. So now if you look at the situation from the developer's perspective, they are now given access to certain number of clusters from different environments. And by the way, some of these clusters are also running on their local development environments on their laptops. So what Lens is doing is basically provides a unified user experience across all these clusters no matter what is the flavor of the Kubernetes. It can be the Minikube. It can be from AKS. It can be Mirantis Enterprise, Docker Enterprise offering, or whatever. So it kind of brings them all together and makes it very easy to navigate and go around and do your work. >> Yeah, well, that's, the promise of Kubernetes isn't that it just levels the playing field amongst everything. As I've talked to the founders of Kubernetes, people like Joe Beda said it's not a silver bullet. It's a thin layer. But that skillset is what's so important because there is a lot of difference between every platform they deal with. So as a developer, it's nice to have some tools that I can work across those environments. From a developer standpoint, I think it's on Windows, Linux, Mac, works across those environment. What do you hear from your customers? How are they using it? Is this something that they're like, oh hey, I can go make an adjustment on my mobile when I'm not necessarily in the office? Are we not quite there yet? >> Actually, it's kind of funny, because sometimes we hear these type of requests that we would like to have a mobile app version of Lens. I don't know how that would actually work in practice. So we haven't been doing anything on that front yet. I think still the most common use case is that developers, they are given access to clusters from somewhere and they are just desperately trying to find a kind of convenient way how to navigate around these different clusters and how to manage their workloads. And I think Lens is hitting the sweet spot in there with the ease of use. >> All right, so let me understand. It's been open sourced, yet Mirantis owns it. Is there a service or support? Does this tie into other products in the Mirantis portfolio? How do people get it? What do they need to, if anything, pay for it? And help us understand how this fits into the broader Mirantis story. >> Yes, so it's still kind of early days, so we just kind of announced that Lens is now part of Mirantis, let's say portfolio. So I must say that still the kind of main focus for us is around improving Lens and making it better for developers. So that's much more important than trying to think about the ways how potentially we could monetize this. So, but there are plans going ahead, going around for different ways how we can better support bigger enterprises who want to start using Lens in a big scale. >> Well, yeah, that's so important. Of course, developers, we need to lower the friction, help them adopt things fast. Miska, just get your general viewpoint, though. One of the big value propositions that Mirantis has is of course allowing enterprises to take advantage of these new types of solutions, especially today around Kubernetes. So help us understand from your standpoint the philosophy of what your team's helping to build and the customer engagements that you're having. >> Yes, so Mirantis, of course, has a broad portfolio of products, and many of those products, of course, are related to Kubernetes. And so we have many products which I'm also one of the leading development efforts around those. So some of the products are related to how to manage image repositories and registries. Some of them are related to how to handle the helm charts, which has basically become the defacto packaging format for Kubernetes applications. And we are kind of trying to bring all these different products and technologies together in a way that make it even more easy for developers then to access through Lens. So it's still a little bit work in progress, of course, since the Lens ecosystem is quite new, but we are on track there trying to make a beautiful one kind of experience for our customers. >> All right, well, final question I have for you. As you said, it's new there, but it gives a little taste as to feedback you're getting from the community. Anything we should be looking at on kind of the near to mid-term road map when it comes to Lens. >> Oh yeah, so we are just barely scratching the surface of the potential on what we can do with Lens. So one of the big features that we will be releasing still during this year in a couple of months time is going to be the extension API, which will allow all these cloud-native technology ecosystem vendors to bring their own technologies easily available and accessible through Lens. So it is possible for third parties to extend the user interface with their own kind of unique features and visualizations. And we are already actively working with certain partners to integrate their technologies through this extension API. So that's going to be huge. It's going to be game-changer. >> Well, the great thing about an open source project is people can go out, they can grab it now, they can give feedback, participate in the community. Miska, thank you so much for joining us and great to chat. >> Thank you for having me. Thank you. >> All right, stay with us for more coverage of Mirantis Launchpad 2020. I'm Stu Miniman and thank you for watching theCUBE. (bright music)

>> Narrator: From around the globe, its theCUBE with digital coverage of Mirantis Launchpad 2020 brought to you by Mirantis . >> Welcome back, I'm Stu Miniman and this is theCUBE coverage of Mirantis Launchpad 2020, really looking at how Mirantis Docker Enterprise are coming together, changes happening in the field and to help us dig into that customer and product discussion. Happy to welcome to the program, Shaun O'Meara. He is the global Field Chief Technology Officer with Mirantis coming to us from Germany. Shaun thanks so much for joining us. >> Thanks for having me. >> All right, so let's start with the customers. I always love talking to the Field CTOs you're out there. You're talking strategy, you're getting into some of the architecture, lots of customers, probably still, trying to figure out that whole cloud native containerization, Kubernetes and modernization piece. So when you talk to your customers, what are some of their biggest challenges they're facing and those main discussion points that bring them to talk to Mirantis. >> Very good question, I think you've just laid it out yourself in many ways. It's complexity our customers are dealing with more and more change, more and more options, and it's driving complexity in their environments, and they're looking for ways to deal with that complexity and to allow more and more access and reduce barriers to getting applications and getting tools to market. And if we look at it and we look at the way the world is going today, we have multiple cloud environments. We have every single developer on the face of the planet wants to use different tools, different ways to build applications that don't want to be dictated to. Now, if you turn that around and you look at what operators have to deal with, it's just more and more complexity. Ultimately, that complexity is growing and we're looking for ways to make it easier, simpler, and subsequently increase the speed of getting applications to market for our customers. >> Yeah, You know we talk a bit about some of the macro challenges that customers have. What talk you kind of teed up a little bit, the operators and the developers. I remember a couple of years ago, I had the opportunity to interview Solomon Hykes and of course the founder from Docker. And there was that talk of well, containerization, it's this wonderful thing for developers. And he's like, hold on Stu we actually, really started looking at this or the operators we want that unit of operation to be closer to the application. So it should be simpler, it used to be okay, how many different applications do they have on a server or VMs all over the place and containers I could really have this microservice or this application is a container. So there is some operational simplicity there, but how is that dynamic inside the customer? Of course, we've seen the growth and the importance and the embracing of developers, but there's still the DevOps adoption and we'd love to be able to say one of these years that, oh, we don't have silos anymore and everybody works together and we're all on the same page. >> Oh yeah, the reality is in the big enterprise companies and the companies that are building applications for market today, your big financial services companies, there's still a very clear separation between operators and developers. A lot of that is driven by legislation, a lot of that's driven by just old fashioned thinking in many ways, but developers are starting to have a lot more influence on what applications are used and the infrastructure. We just see with the rise of AWS, all the contenders to AWS in the form of Azure and Google. Developers are starting to have a lot more power over that decision, but they're still highly dependent on operators to deliver those platforms that they use, and to make sure that the platforms that they're running their applications on top of, are stable and run well in production situations. There's a big difference between building something on your laptop in one or two instances, and then trying to push it out to a massive scalable cloud platform. And I think those are the areas that we can have a lot of impact, and that's where we are building our tools for at the moment. >> Well, great. Let's dig into those tools a little bit, as I said, at the beginning, we're familiar, Mirantis had the Mirantis Cloud Platform for a few years, big embrace of Kubernetes and then Docker Enterprise, it comes into the mix. So help me understand a little bit, what is kind of the solution set to portfolio? How does Mirantis present that today? >> Yeah, well, it's been an interesting eight, nine months now of the whole process since with the Docker Enterprise business, a couple of key areas. So if we look at what MCP was, and MCP still here today apparently, it focuses on delivering all the components necessary to have an effective cloud platform. So lifecycle management, lifecycle management of all those underlying components, which in their own right is extremely complex set of software. What we focused on there was understanding in enterprise infrastructure, the right way to do that. As soon as you bring in from the Docker Enterprise business is that they have a scalable, large, well deployed container platform. And many thousands of users across the world in all sorts of different scales and production systems. We are merging that knowledge that we have around infrastructure, infrastructure management, and simplifying access to infrastructure with this platform that provides for all that application, hosting provides for all the control of containers, plus all the security components around the container lifecycle. And delivering in such a way that you can choose your underlying preference. So we're no longer looking to lock you in to say, you have to go on-prem, you have to go into cloud. We're saying, we'll give you the choice, but we'll also give you a standardized platform for your developers across all of those potential infrastructure environments, so I'll use it again, public cloud, private cloud, bare metal on-premise, or your options like the VMware of this world. By consolidating all of that into one platform, we're giving you that as a developer, the ability to write applications that'll run anyway and sorry, go on. >> No, please finish up, I've just got to follow, yeah. >> But that simplicity drives and like that's simple choice across all those platforms essentially drives speed. It takes away the typical barriers that we're seeing in our customers. We hear every reason, we love Docker Enterprise because it solves the problem of getting containers, it solves a problem of securing containers, but it takes four teams to deploy it. Same for the MCP, we're saying is we cannot do that in a day and provide other self sets. So you can deploy a brand new container cloud in minutes rather than days or weeks. And that's one of the biggest changes that we're bringing to the product. >> Yeah, so absolutely what we hear from customers that agility, that speed that you talk about is the imperative, especially talk about 2020, everybody has had to readjust often accelerating some of the plans they had to meet the realities of what we have today. What I want to understand is when you talk about that single platform being able to be in any environment, oftentimes there's a misnomer that it's about portability. Most customers we talked to, they're not moving things lots of places. They do want that operational consistency, wherever they go. At the same time, you mentioned the rise of AWS and the hyperscalers often when they're now going to have to manage multiple clusters, it's not that I choose one Kubernetes and I use it anywhere, but I might be using AKS Azure had an early version of it, of course, Amazon has a couple of options now for enterprises. So help us understand how the Mirantis solutions, fit with the clouds, leverage cloud services and if I have multiple clusters, you even mentioned VMware, I might have a VMware cluster, have something from Mirantis, have something from one of the hyperscalers. Is that what you're seeing from your customers today? And how do they and how do they want to manage that going forward? Because we understand this is still a maturing space. >> So I mean, that's exactly the point. What we're seeing from our customers is that they have policies to go cloud first. They still have a lot of infrastructure on-premise. The question is which cloud, which cloud suits their needs in which region. Now, all of a sudden you've got a risk management policy from an organization that says, well, I have to go to Azure and I have to go to AWS. That's using them as examples. The deployment and management of those two platforms is completely different. Just the learning curve for a developer who wants to focus on writing code, to build a platform on top of AWS is barely extensive. Yes, it's easy to get started, but if you really want to deal with the fine print of how to run some in production, it's not that simple. There are potentially a thousand different buttons, you can click when deploying an instance on Amazon. So what we're saying is, instead of you having to deal with that we're going to abstract that pain from you. We're going to say we'll deploy Docker Enterprise on top of Amazon, on top of Google, on top of Azure, on top of your VMware cluster, give you a consistent interface to that, consistent set of tools across all those platforms, still consuming those platforms as you would, but solve all those dependency problems. To set up a cube cluster on top of Amazon, I'm not talking about an AKS or something like that right now, but the sort of cube cluster means I have to set up load balances, I have to set up networks, I have to set up monitors, I have to set up the instances, I have to deploy Kubernetes, and then I'm only getting started. I still haven't integrated that to my corporate identity management. We're saying we'll bring all that to give them, we are bringing all that together in the form of Docker Enterprise container cloud. >> Yeah, definitely as you said, we need more simplicity here. The promise of cloud it's supposed to be simplicity and now of course we have the paradox of choice when it comes there. >> Yeah. >> One of the other things we've seen, rapid change a lot the last year or so is many of the offerings out there are now managed services. So as you said, I don't want to have to build all of those pieces. I want to just be able to go to somebody. What are you hearing from your customers? How does manage service fit into what Mirantis is doing? >> Great, well, what we're hearing from customers is they want the pain to go away. The answer to that could be delivered through software that's really easy to use and doesn't set up any barriers and gets them started fast, which is where we focus from a product perspective. Mirantis also has a strong manage services on so we've been doing manage services for some of the biggest enterprises in the world for MCP products for many years. We've brought those teams forward and we're now offering those same managed services on top of all of our platforms. So Docker Enterprise container cloud, we'll deploy it for you, we'll manage it for you. We'll handle all the dependencies around getting container cloud up and running within your organization, and then offer you that hands on service. So when you build clusters, when you want clusters that are much more longer lived, we can handle all the extra detail that goes around those. Short term, so if you just want quick clusters for your developers, easy access, you still have that as part of the service. So we're focusing on how fast can we get you started? How fast can you get up the cushions to market, not put any infrastructure barriers on the way, or where there are traditional infrastructure barriers find ways around us. That still acceptable to those enterprise operators who still have list as long as my arm, probably twice as long as my arm of fine print that they have to comply with for everything under the sun, the regulators, et cetera. >> Yeah, Shaun since you are based in Europe, I'm wondering if you can give us a little bit of the perspective on cloud adoption there, here in North America, discussion point has been for many years, just that massive movement to public cloud, of course governance the key issue in Europe and above also kind of the COVID impact, anecdotally there's lots of discussions of acceleration of public cloud. So what's the reality on the ground? How do your enterprise customers look at public cloud? How fast or slow are they moving and what is the 2020 impact? >> So interesting if you'd asked me this question, six months ago, seven months ago, pre COVID, I would have said public cloud is growing. People are still building some small private clouds for very unique use cases, looking at where our customers are now, all of a sudden there's a risk balance. So they're driving into public cloud, but they want those public clouds to be with European companies and European operators, or at least to have some level of security. You know, recently the European community canceled the privacy shield legislation that was in place between the US and Europe, which meant all of a sudden, a lot of companies in Europe had to look for other places to store their data, or had to deal with different rules around storing the data that they may have but in the US previously. What we're seeing customers saying is we have to go multicloud. The drive is no longer we can accept one vendor risk. We want to remove that risk, we will still have equipment on-premise. So on-prem equipment is still important to us, but as a backup to the public cloud, and as a way to secure our data and the mechanisms that we own and can touch and control. That's the operator's view. If we talk to developers, people writing applications, if they are not forced to, they will go public cloud almost every time. It's just easier for them. And that's really what we're, that's really the challenge that we're also trying to focus on here. >> Yeah, I'm curious, are there any European cloud providers that are rising to the top the big three have such a large megaphone that they kind of drown out a lot of discussion and understand that there's pockets and many local suppliers, and of course thousands of kind of cloud service providers out there, but any ones that are good partners of Mirantis or ones that you're hearing. >> There are a couple. >> Yeah. >> Sorry, there are a couple, I dunno if I can mention them here, but there's some great ones providing very unique businesses, places like the Netherlands, very unique, very focused business where they're taking advantage of specific laws within, well, the Netherlands and Germany, there's another company that we're working very closely with that feels that they can do a much more affordable, much more hands on service or cloud. So their cloud experience provide everything developers want, but at the same time handle those operator requirements and those enterprise requirements within Germany. So focusing on the GDPR laws, focusing on German technology laws, which are very complex, very much focused on privacy. And there are a few unique companies like that across Europe, I know of one in Italy, there's a company that focuses on providing cloud services to the EU government themselves, who we've worked with in the past. So yeah, but as you say, it's the big three, they're growing, they're dealing with those challenges. We see them as resources, we see them as partners to what we're trying to achieve. We certainly not trying to compete with them at that level. >> Absolutely, all right, Shaun final question I have for you, tell us what your customers see as the real differentiation, what draws them to Mirantis and what we should expect to see over the coming months? >> So I think choice is a key differentiator. We're offering choice, we're not trying to tell you you can only use one cloud platform or one cloud provider. And that's extremely important as one of the key differentiators. I've mentioned this many times, simplicity, driving simplicity at all levels, from the operator through to the developer, to the consumer of the cloud, let's make it easy. Let's truly reduce the friction to getting started, all right that's one of the really key focus areas for us and that's something we talk about all the time in every meeting and we question ourselves constantly is, does this make it easier? And then security is a major component for us. We really focus on security as part of our tool sets, providing that standardized platform and that standardized security across all of these environments, and ultimately reducing the complexity. >> Shaun O'Meara, thank you so much. Great to hear that the real customer interaction and what they're dealing with today. >> Sure, thank you very much. >> Be sure to check out the tracks for developers, for infrastructure as well as all the rest theCUBE interviews on the Mirantis Launchpad site of course powered by CUBE365. I'm Stu Miniman and thank you for watching theCUBE. (upbeat music)

>> Announcer: From around the globe, it's theCUBE, with digital coverage of Mirantis Launchpad 2020, brought to you by Mirantis. >> Welcome back I'm Stu Miniman, and this is theCUBE's coverage of Mirantis Launchpad 2020. Big event, multiple tracks powered by theCUBE365. Happy to welcome you to the program. We have a first time guest, Willem du Plessis. He's the Director of Customer Success and Operations with Mirantis. Willem, thanks so much for joining us. >> Hi Stu, thanks for having me. >> So customer success, of course, a big topic in the industry last few years. CX a is so important. Employee success and enabling that, but what, give us a little bit, your background and the purview that you and your team cover. >> Exactly, yeah, so everything under my umbrella would be basically post-sales. The whole customer experience after the point of a sale's been made so the whole account management, thereafter, the success of the accounts, as well as the health of the account, thereafter, that will be anything basically post-sales would be under my umbrella. >> Wonderful, well, the big piece is the shift. As we know, software went from shrink wrapped, and hardware talking about CapX to the cloud really ushered in OpX we're touching more subscription managed services and the like, so Mirantis has a subscription offering. Why don't you lay out for us the new pieces of this and how Mirantis puts together its offerings? >> Yeah, absolutely. So with the launch of our new product, Docker Enterprise Container Cloud, we're making two subscriptions available as well, named ProdCare, which is a 24/7 mission critical support offering and OpsCare, being a fully managed platform as a service subscription. Now, these offerings have been available on the Mirantis Cloud platform side of our business for quite some time, we've been very successful with them, so it's really excited making them available to our Docker Enterprise customers. So what we're trying to achieve with these accounts or with these subscriptions, rather, you know, 30% of the Fortune 100 companies are Mirantis customers, so we work on a day to day basis with their container and Kubernetes initiatives. So when we speak to these customers, there are really two trends that are becoming very clear, the first being the requirements of service providers or vendors being able to provide a true 24/7 experience. What I mean by that is not the ability to just react to an incident on a 24/7 basis. That's what I mean, what I mean is all of these companies would have operation centers spread across the globe. So it is at every hour of the day, it would be business as usual. And what these companies require is a, a partner or a service provider that can match that level, that way of operating. That is the first trend that we're noting. The second piece is really the, the evolution of the dev environment. The dev environment is no longer really seen as a secondary or a lower class citizen, if you want to call it, it's really become part of the whole DevOps pipeline, so it is really part of a mission critical process so that what customers, what we hear from our customers is that they require a real enterprise-grade subscription that they can cover this whole pipeline under and, you know, have the same quality of service from whether that is a dev or a production environment. So if you have a failure on your dev environment and your developer cannot push code, that is, is the same level of criticality than there would then they would be on if the failure was on the production environment. So this whole pipeline is decidedly seen as a mission critical component. And that's a great, that's really where ProdCare comes in. It is really this 24/7 mission critical follow the sun, enterprise-grade subscription that provides our customers with enhanced SLAs that, like I said, we've been running on the Mirantis Cloud platform side for quite some time, we've had some significant success with some really large companies. The second offering that we're making available with, like I said, is OpsCare. Now OpsCare is an ITIL-based managed service subscription, where we provide a platform as a service experience to a customer on their infrastructure of choice. So it is really irrelevant for us what your infrastructure is, whether that is on-prem or in the public cloud, as long as the product can support the infrastructure, you know, the subscription would be available for you and the experience would be very much the same. So what OpsCare, like I said, entails is, is this whole ITIL framework that would include, you know, the monitoring and managing of your alerts, the incident management process, the problem management process, as well as change management that would include the lifecycle management of the whole environment. And that would just enable our customers to run on the latest and greatest offer of our product at all times. And same as with ProdCare that's been available for our brass cloud platform customers for quite a while, and have seen some significant success with that, as well. >> Well, we definitely have seen that growth of the managed care offerings like you're talking about with OpsCare, you know, shift left is so important for companies to be able to focus on what's critically important. As you said, developers need to be enabled, it can't just be waiting for things or be, you know, relegated to, you know, have to wait in line or use something that's not optimal. What are some of those outcomes? What can companies do that they weren't able before? What are some of those successes that you're seeing with the managed care OpsCare solution? >> Yeah, so the real way we OpsCare really comes to its own is allowing the customer ability to focus on what is important to their business and spend less time on what we call, keep the lights on. What I mean by that is they're solely focused on developing the application, developing the workload and spend basically no time on managing the infrastructure and, you know, maintaining it, or, you know, providing, do whatever to, to keep the platform stable, because that is done by Mirantis, already. So for example, if we take 2020 year to date, all the platforms running under OpsCare has an availability number of above four nines, and that is a significant number. So that really just sets such a strong foundation for a customer to just have that sole focus on, on what is important to them and, you know, just sets that foundation for them to develop their workload, to develop their business, and achieve their goals. >> Well, what about when it comes to the managing and monitoring of the environment? What kind of metrics are your customers having? Help us understand what the customer still does themselves or the reporting they're getting and what Mirantis, I'm assuming there's probably a Tam involved for at least some of the larger accounts there. Help us understand that shared responsibility, if you would for these type of environments. >> Yeah, exactly. So the whole ITIL framework, as I explained earlier, incident management, problem management, change, all of that, this is wrapped around why a customer success manager that is, you know, brings a single level of ownership on an accountability, and just have a customer direct for a single point of contact as a business partner. So all this is all our customers, their primary KPI or metric that we look at is just the availability of the platform. That is the primary SLA and thereafter, all of the other things happening, you know, the success of the workload and so on, because there's a lot of things that makes the result of the workload, not just the platform or the infrastructure, it's the quality of the workload, and so on, and so forth. But the main metric our customer would be looking at is that availability number, you know, how available and how stable and accessible is the environment, and, you know, like I said, just removing that requirement for them to spend, basically, no time on the platform or the infrastructure, and just focusing on the workload. >> Yeah, when it comes to in the field, your field, your partners, that line between ProdCare and OpsCare, obviously, the trend is going towards, you know, the fully managed option, but what guidance do you have out there, or what trends do you seeing? Is it a certain size company, that tends to be trending that way? Are there certain verticals that may be are further ahead? What's the reality, today? What do you expect to see over the next kind of six, 12 months? >> Yeah, so most of the companies that we see that as, that is engaging with us on an OpsCare, or managed service engagement, you know, they have the ambitions to go down the block model and build, operate, transfer, you know, to take the operations over themselves, at some point, and we have that option available to them, if they wish to choose it further along the line. What we do find is, is that they, that they don't really, you know, exercise that later on. It is, we do find it is such a smooth integration with our customers, that they tend to stay on OpsCare and see the value. This is actually a money saver for them, if they could, just focus their efforts on building, you know, focusing their time on the workload on top of the platform. From a vertical perspective, it's really anything and everything. We have customers in the science and research, we have TELCOs, large manufacturing, manufacturing, a lot of large organizations. There's really the breadth of the verticals that we see that are utilizing OpsCare and not even to mention ProdCare, that's really everything in there, as well. So it is not a really a subscription that is, that is custom for one vertical. It is basically something that we, that any vertical can actually utilize and find a significant amount of value in. >> All right, well, what final words do you have that you want to leave everyone with today? >> Yeah, so over the last six to nine months, you know, we've invested a significant amount of resources in the Docker Enterprise support business and we just with one focus, and that is just to take the support business to the next level and improve or give the customers an optimal customer experience. So with the availability of all these new subscriptions, I'm really excited to engage with our Docker Enterprise customers with these new, enhanced SLAs and just be able to work with them on these, like I said, enhanced subscriptions and just see, just give them a better customer experience. So, I'm really looking forward to working with them on the subscriptions. >> Willem, thank you so much for all the updates and want to welcome everyone to be sure to check out all the rest of the tracks on the Launchpad 2020 event. I'm Stu Miniman and thank you for watching theCUBE. (soft electronic music)

>> Narrator: From around the globe it's the CUBE with digital coverage of Mirantis Launchpad 2020, brought to you by Mirantis. >> Welcome back, I'm Stu Miniman, and this is the CUBE's coverage of Mirantis Launchpad 2020. And always love when we get to be able to talk to the practitioners that are using some of the technologies here. One of the interesting things we've been digging into is lens, the IDE in this space, as it's being referred to. So, happy to welcome to the program Matti Paksula. He is the founder and chief technology officer at supervisor.com. Matti, thanks so much for joining us. >> Thank you, thank you thank you for having me. >> So, if you could just, you help us understand, you know, your company as supervisor.com. What's the background as the founder? What was kind of the impetus to creating that business too? >> Sure, so, supervisor was this like super simple because we believe, and we know, that the only way to tests websites, if they can handle load, for example, eCommerce sites on black Friday, or when you, or, just about to make a product launch or that kind of stuff. Is just by sending real web browsers to the site. That's actually click and scroll and do it all the same things as a real users will do. But, and unlike, our secret thing is that we can do it, like before Black Friday. So, if somebody wants to simulate if they can handle like 2000 users or 5000 users, then they can use supervisor.com to make it happen like today. >> So, I'm just curious, you know, the concern always is about the DDoS attacks and the like. Do you help companies along that line too? Or is it more the, the testing for proper traffic and we leave the security aspect to somebody else? >> Yeah, well, like with any load testing tool, you have to verify yourself somehow. And with us, it's super easy because we integrated with Google analytics. And if you authorize us to read your Google Analytics Data, then we know that you are allowed to test your site. >> Wonderful, well, as I said in the lead, you're using lens, my understanding you've been using it since the early day, of course, a technology that closed source Mirantis has, has acquired that and the team, it's now also open source. So if you could bring us back to, you know, how did you get involved with lens? What was the, you know, the problem statement that it helped you resolve? >> Yeah, sure. So the (inaudible) super briefly is that Lens was developed by this startup called Condena, it's a finish startup, and they made a couple of attempts in container orchestration, like before Kubernetes and then Coobernetti's game. And they just felt like Kubernetes is super hard to kind of visualize or like, understand what's going on because you have these containers flying around, you have nodes going in going out. So they built this lens and then since I'd be working with those guys from 2015 or so, I was like one of the first outside users, or probably the first user outside of the company. >> So, that, pretty neat that you had that, you know, that project that they were doing. As an early user, you know, give us a little bit of that journey. What does it enable for your company? You know, how has it expanded from kind of the early use cases to where it is today. >> Yeah. So, if you're using Kubernetes traditionally, or like how most of the people who haven't yet heard about Lens use it is by or from the command line. So that's where you use keep CTL or cube control. You say cube CTL pod, and then you get the listing pod. But the problem is that, all that data is stale on the screen. So if you trend try to, for example, delete a port and you issue cutesy delete pod, blah, blah, blah, blah. And then you enter on the pod all ready, it might be gone. So Lens makes like everything real time. And like, if you try to delete something with lens, you move your mouse on top of the pod. And if it's getting deleted, you know, this, it, because it just disappears from your screen and like, it's not there anymore. And I think that's a huge a productivity boost in a way, that's how you can like get more and more stuff done every day as these kind of like, when you are a developer or CSI admin or whatever you need to kind of like, see what's happening in your cluster and house that note and pods are doing. And that. So back to your question, when you asked, like, how has the evolved lens it's like nowadays it's super stable. It handles big workloads very well. In the very, very early on, they had some performance issues with like, like large clusters, for example, when supervisor, when we run a load test with, for example, 10,000 concurrent web browsers. So basically what we have in Kubernetes is we have 10,000 pods. And then when you connect something like lens to it, it's just like started to spin up my fans until on the laptop, still about eating all the Ram. So I helped them a lot with my special use case of running like super big Ephemeral workloads there. >> Yeah. It's an interesting discussion. And in the whole, you know, container space, there's all that discussion of scale(chuckling). You know, of course everybody thinks back to Google and how they use it. So we know it can go really big, but, you know, environments, I needed to be able to work really small or youth cases like yours. I needed to be able to, you know, burst use that usage when you need it and go back on that a less density that we hope for in, in cloud. So I'm curious any, what's your expectation with it, you know, going open source, coming into Mirantis as a, as a longtime user of it, you know, what do you expect to see? >> Well, I think like Mirantis offers the right kind of home for the product, because they really get what's happening in the space. And I think they're like commercial offering on top of the open source will be around authentication. That's why, like, I kind of understood from the press release. And I think it makes sense because like, developers don't want to pay for these kinds of tools. And there are other tools that are commercial. And even if it's like just 100 bucks per year, I think that's still not going to work out with most of the developers and you kind of need this kind of long tail developer adoption for these kinds of products to succeed. And I think that, like, that's kind of like authentication, like centralized, like who can see what, and that kind of stuff. It doesn't like affect most of the startups or Indie Devs, but like for any company who was doing it like a real business, those are the features that are needed. And when you use that, the products for business, then I think it makes sense to pay also. >> Yeah, absolutely. There's always that, challenge developers of course love open source tools if they can use them. And, you know, the packaging, the monetization, isn't a question for you it's(chuckling), you know, for the Miranda's team. What would you say to your peers out there, people that are in this space, you know, what are the areas that they say, Oh, you know, if I have this type of environment, or if I have type, if I have this team, this is what lens will really be awesome for me. What are some of the things that you would recommend to your peers out there from, from all the usage that you've done? >> Yeah. So let's say three things. The first thing is what I already mentioned the real timeness that everything updates live, the second thing is the integrated metrics. So you cannot, for example, follow how much memory or CPU something is consuming. It's super helpful when you want to like, understand what's really going on and how much resources something is taken. And then the third thing is that Landis is great for debugging because once you have deployed something and something is off, and it's kind of hard to reproduce locally, especially with this kind of a microservice architecture, whatever, what you might have is that you can just like go inside at any part or note instantly from the UI. You don't have to, like, again, you don't have to use cubes sheets, the L blah, blah, blah, blah, blah. And, and you have just like in there also, because you are already in the. But its the fourth thing is that if you manage multiple Kubernetes clusters, it's super easy to accidentally connect to the wrong cluster. But like, if you have, some visual tool where you can see in I'm in this. I mean, my production cluster are I'm in my staging cluster and you make the selection like visually there, then all the cube sees and everything works against that's a cluster. So I think that's like very helpful so that you don't actually accidentally delete something from production, for example. >> Wonderful. Last question I have for you either blend specifically, or kind of the eco-system around it, what, would be on your wishlist for, as I said, either lance specifically, or to, you know, manage your environments surrounding that, you know, what, what would you be asking kind of Miranda and, the broader eco-system for? >> I know that, well, let me think. Yeah. Okay. First of all, I have like maybe 50, 60 issues still open a GitHub that I have opened there. So that's like my wish list, but like, if you, they got like longer term, I think it would just be great, if you could actually like start deployments from Lance, there are a bunch of deployment tools, like customize and help. But again, if you just wanted to get something running quickly, I think integrating that to Lance would be like, super good. Just you it's just like click like I want to deploy this app. That's, that's something I'm looking forward to. >> Yeah, absolutely. Everybody wants that simplicity. All right. Well, Hey, thank you so much. Great to hear the feedback. We always talk about the people that developed code, as well as, you know, the people that do the beta testing and the feedback. So critically important to the maturation development of everything that's based though. Thanks so much for joining us. >> Thank you. >> Stay tuned for more coverage from Mirantis Launchpad 2020 I'm Stu Miniman. And thank you for watching the cube. (upbeat music)

>>thank you everyone for joining. I'm here today to talk about English controllers. AP Gateways and service mention communities three very hot topics that are also frequently confusing. So I'm Richard Lee, founder CEO of Ambassador Labs, formerly known as Data Wire. We sponsor a number of popular open source projects that are part of the Cloud Native Computing Foundation, including telepresence and Ambassador, which is a kubernetes native AP gateway. And most of what I'm going to talk about today is related to our work around ambassador. Uh huh. So I want to start by talking about application architecture, er and workflow on kubernetes and how applications that are being built on kubernetes really differ from how they used to be built. So when you're building applications on kubernetes, the traditional architectures is the very famous monolith, and the monolith is a central piece of software. It's one giant thing that you build, deployed run, and the value of a monolith is it's really simple. And if you think about the monolithic development process, more importantly, is the architecture er is really reflecting that workflow. So with the monolith, you have a very centralized development process. You tend not to release too frequently because you have all these different development teams that are working on different features, and then you decide in advance when you're going to release that particular pieces offering. Everyone works towards that release train, and you have specialized teams. You have a development team which has all your developers. You have a Q A team. You have a release team, you have an operations team, so that's your typical development organization and workflow with a monolithic application. As organization shift to micro >>services, they adopt a very different development paradigm. It's a decentralized development paradigm where you have lots of different independent teams that are simultaneously working on different parts of the application, and those application components are really shipped as independent services. And so you really have a continuous release cycle because instead of synchronizing all your teams around one particular vehicle, you have so many different release vehicles that each team is able to ship a soon as they're ready. And so we call this full cycle development because that team is >>really responsible, not just for the coding of that micro service, but also the testing and the release and operations of that service. Um, >>so this is a huge change, particularly with workflow. And there's a lot of implications for this, s o. I have a diagram here that just try to visualize a little bit more the difference in organization >>with the monolith. You have everyone who works on this monolith with micro services. You have the yellow folks work on the Yellow Micro Service, and the purple folks work on the Purple Micro Service and maybe just one person work on the Orange Micro Service and so forth. >>So there's a lot more diversity around your teams and your micro services, and it lets you really adjust the granularity of your development to your specific business need. So how do users actually access your micro services? Well, with the monolith, it's pretty straightforward. You have one big thing. So you just tell the Internet while I have this one big thing on the Internet, make sure you send all your travel to the big thing. But when you have micro services and you have a bunch of different micro services, how do users actually access these micro services? So the solution is an AP gateway, so the gateway consolidates all access to your micro services, so requests come from the Internet. They go to your AP gateway. The AP Gateway looks at these requests, and based on the nature of these requests, it routes them to the appropriate micro service. And because the AP gateway is centralizing thing access to all the micro services, it also really helps you simplify authentication, observe ability, routing all these different crosscutting concerns. Because instead of implementing authentication in each >>of your micro services, which would be a maintenance nightmare and a security nightmare, you put all your authentication in your AP gateway. So if you look at this world of micro services, AP gateways are really important part of your infrastructure, which are really necessary and pre micro services. Pre kubernetes Unhappy Gateway Well valuable was much more optional. So that's one of the really big things around. Recognizing with the micro services architecture er, you >>really need to start thinking much more about maybe a gateway. The other consideration within a P A gateway is around your management workflow because, as I mentioned, each team is actually response for their own micro service, which also means each team needs to be able to independently manage the gateway. So Team A working on that micro service needs to be able to tell the AP at Gateway. This this is >>how I want you to write. Request to my micro service, and the Purple team needs to be able to say something different for how purple requests get right into the Purple Micro Service. So that's also really important consideration as you think about AP gateways and how it fits in your architecture. Because it's not just about your architecture. It's also about your workflow. So let me talk about a PR gateways on kubernetes. I'm going to start by talking about ingress. So ingress is the process of getting traffic from the Internet to services inside the cluster kubernetes. From an architectural perspective, it actually has a requirement that all the different pods in a kubernetes cluster needs to communicate with each other. And as a consequence, what Kubernetes does is it creates its own private network space for all these pods, and each pod gets its own I p address. So this makes things very, very simple for inter pod communication. Cooper in any is, on the other hand, does not say very much around how traffic should actually get into the cluster. So there's a lot of detail around how traffic actually, once it's in the cluster, how you routed around the cluster and it's very opinionated about how this works but getting traffic into the cluster. There's a lot of different options on there's multiple strategies pot i p. There's ingress. There's low bounce of resource is there's no port. >>I'm not gonna go into exhaustive detail on all these different options on. I'm going to just talk about the most common approach that most organizations take today. So the most common strategy for routing is coupling an external load balancer with an ingress controller. And so an external load balancer can be >>ah, Harvard load balancer. It could be a virtual machine. It could be a cloud load balancer. But the key requirement for an external load balancer >>is to be able to attack to stable I people he address so that you can actually map a domain name and DNS to that particular external load balancer and that external load balancer, usually but not always well, then route traffic and pass that traffic straight through to your ingress controller, and then your English controller takes that traffic and then routes it internally inside >>kubernetes to the various pods that are running your micro services. There are >>other approaches, but this is the most common approach. And the reason for this is that the alternative approaches really required each of your micro services to be exposed outside of the cluster, which causes a lot of challenges around management and deployment and maintenance that you generally want to avoid. So I've been talking about in English controller. What exactly is an English controller? So in English controller is an application that can process rules according to the kubernetes English specifications. Strangely, Kubernetes is not actually ship with a built in English controller. Um, I say strangely because you think, well, getting traffic into a cluster is probably a pretty common requirement. And it is. It turns out that this is complex enough that there's no one size fits all English controller. And so there is a set of ingress >>rules that are part of the kubernetes English specifications at specified how traffic gets route into the cluster >>and then you need a proxy that can actually route this traffic to these different pods. And so an increase controller really translates between the kubernetes configuration and the >>proxy configuration and common proxies for ingress. Controllers include H a proxy envoy Proxy or Engine X. So >>let me talk a little bit more about these common proxies. So all these proxies and there >>are many other proxies I'm just highlighting what I consider to be probably the most three most well established proxies. Uh, h a proxy, uh, Engine X and envoy proxies. So H a proxy is managed by a plastic technology start in 2000 and one, um, the H a proxy organization actually creates an ingress controller. And before they kept created ingress controller, there was an open source project called Voyager, which built in ingress Controller on >>H a proxy engine X managed by engine. Xing, subsequently acquired by F five Also open source started a little bit later. The proxy in 2004. And there's the engine Xing breast, which is a community project. Um, that's the most popular a zwelling the engine Next Inc Kubernetes English project which is maintained by the company. This is a common source of confusion because sometimes people will think that they're using the ingress engine X ingress controller, and it's not clear if they're using this commercially supported version or the open source version, and they actually, although they have very similar names, uh, they actually have different functionality. Finally. Envoy Proxy, the newest entrant to the proxy market originally developed by engineers that lift the ride sharing company. They subsequently donated it to the cloud. Native Computing Foundation Envoy has become probably the most popular cloud native proxy. It's used by Ambassador uh, the A P a. Gateway. It's using the SDO service mash. It's using VM Ware Contour. It's been used by Amazon and at mesh. It's probably the most common proxy in the cloud native world. So, as I mentioned, there's a lot of different options for ingress. Controller is the most common. Is the engine X ingress controller, not the one maintained by Engine X Inc but the one that's part of the Cooper Nannies project? Um, ambassador is the most popular envoy based option. Another common option is the SDO Gateway, which is directly integrated with the SDO mesh, and that's >>actually part of Dr Enterprise. So with all these choices around English controller. How do you actually decide? Well, the reality is the ingress specifications very limited. >>And the reason for this is that getting traffic into the cluster there's a lot of nuance into how you want to do that. And it turns out it's very challenging to create a generic one size fits all specifications because of the vast diversity of implementations and choices that are available to end users. And so you don't see English specifying anything around resilience. So if >>you want to specify a time out or rate limiting, it's not possible in dresses really limited to support for http. So if you're using GSPC or Web sockets, you can't use the ingress specifications, um, different ways of routing >>authentication. The list goes on and on. And so what happens is that different English controllers extend the core ingress specifications to support these use cases in different ways. Yeah, so engine X ingress they actually use a combination of config maps and the English Resource is plus custom annotations that extend the ingress to really let you configure a lot of additional extensions. Um, that is exposing the engineers ingress with Ambassador. We actually use custom resource definitions different CRTs that extend kubernetes itself to configure ambassador. And one of the benefits of the CRD approach is that we can create a standard schema that's actually validated by kubernetes. So when you do a coup control apply of an ambassador CRD coop Control can immediately validate and tell >>you if you're actually applying a valid schema in format for your ambassador configuration on As I previously mentioned, ambassadors built on envoy proxy, >>it's the Gateway also uses C R D s they can to use a necks tension of the service match CRD s as opposed to dedicated Gateway C R D s on again sdo Gateway is built on envoy privacy. So I've been talking a lot about English controllers. But the title of my talk was really about AP gateways and English controllers and service smashed. So what's the difference between an English controller and an AP gateway? So to recap, an immigrant controller processes kubernetes English routing rules and a P I. G. Wave is a central point for managing all your traffic to community services. It typically has additional functionality such as authentication, observe, ability, a >>developer portal and so forth. So what you find Is that not all Ap gateways or English controllers? Because some MP gateways don't support kubernetes at all. S o eso you can't make the can't be ingress controllers and not all ingrates. Controllers support the functionality such as authentication, observe, ability, developer portal >>that you would typically associate with an AP gateway. So, generally speaking, um, AP gateways that run on kubernetes should be considered a super set oven ingress controller. But if the A p a gateway doesn't run on kubernetes, then it's an AP gateway and not an increase controller. Yeah, so what's the difference between a service Machin and AP Gateway? So an AP gateway is really >>focused on traffic into and out of a cluster, so the political term for this is North South traffic. A service mesh is focused on traffic between services in a cluster East West traffic. All service meshes need >>an AP gateway, so it's Theo includes a basic ingress or a P a gateway called the SDO gateway, because a service mention needs traffic from the Internet to be routed into the mesh >>before it can actually do anything Omelet. Proxy, as I mentioned, is the most common proxy for both mesh and gateways. Dr. Enterprise provides an envoy based solution out of the box. >>Uh, SDO Gateway. The reason Dr does this is because, as I mentioned, kubernetes doesn't come package with an ingress. Uh, it makes sense for Dr Enterprise to provide something that's easy to get going. No extra steps required because with Dr Enterprise, you can deploy it and get going. Get exposed on the Internet without any additional software. Dr. Enterprise can also be easily upgraded to ambassador because they're both built on envoy and interest. Consistent routing. Semantics. It also with Ambassador. You get >>greater security for for single sign on. There's a lot of security by default that's configured directly into Ambassador Better control over TLS. Things like that. Um And then finally, there's commercial support that's actually available for Ambassador. SDO is an open source project that has a has a very broad community but no commercial support options. So to recap, ingress controllers and AP gateways are critical pieces of your cloud native stack. So make sure that you choose something that works well for you. >>And I think a lot of times organizations don't think critically enough about the AP gateway until they're much further down the Cuban and a journey. Considerations around how to choose that a p a gateway include functionality such as How does it do with traffic management and >>observe ability? Doesn't support the protocols that you need also nonfunctional requirements such as Does it integrate with your workflow? Do you offer commercial support? Can you get commercial support for this on a P? A. Gateway is focused on north south traffic, so traffic into and out of your kubernetes cluster. A service match is focused on East West traffic, so traffic between different services inside the same cluster. Dr. Enterprise includes SDO Gateway out of the box easy to use but can also be extended with ambassador for enhanced functionality and security. So thank you for your time. Hope this was helpful in understanding the difference between a P gateways, English controllers and service meshes and how you should be thinking about that on your kubernetes deployment

>>from the Cube Studios in Palo Alto in Boston, connecting with thought leaders all around the world. This is a cube conversation. >>Hey, welcome back. You're ready, Jeffrey here with the Cuban Apollo Alto studios today, and we're excited. You know, we're slowly coming out of the, uh, out of the summer season. We're getting ready to jump back into the fall. Season, of course, is still covet. Everything is still digital. But you know, what we're seeing is a digital events allow a lot of things that you couldn't do in the physical space. Mainly get a lot more people to attend that don't have to get in airplanes and file over the country. So to preview this brand new inaugural event that's coming up in about a month, we have We have a new guest. He's Dave and Everen. He is the senior vice president of marketing. Former ran tous. Dave. Great to see you. >>Happy to be here today. Thank you. >>Yeah. So tell us about this inaugural event. You know, we did an event with Miranda's years ago. I had to look it up like 2014. 15. Open stack was hot and you guys sponsored a community event in the Bay Area because the open stack events used to move all over the country each and every year. But you guys said, and the top one here in the Bay Area. But now you're launching something brand new based on some new activity that you guys have been up to over the last several months. So let us give us give us the word. >>Yeah, absolutely. So we definitely have been organizing community events in a variety of open source communities over the years. And, you know, we saw really, really good success with with the Cube And are those events in opens tax Silicon Valley days? And, you know, with the way things have gone this year, we've really seen that virtual events could be very successful and provide a new, maybe slightly different form of engagement but still very high level of engagement for our guests and eso. We're excited to put this together and invite the entire cloud native industry to join us and learn about some of the things that Mantis has been working on in recent months. A zwelling as some of the interesting things that are going on in the Cloud native and kubernetes community >>Great. So it's the inaugural event is called Moran Sous launchpad 2020. The Wares and the Winds in September 16th. So we're about a month away and it's all online is their registration. Costars is free for the community. >>It's absolutely free. Eso everyone is welcome to attend You. Just visit Miranda's dot com and you'll see the info for registering for the event and we'd love it. We love to see you there. It's gonna be a fantastic event. We have multiple tracks catering to developers, operators, general industry. Um, you know, participants in the community and eso we'd be happy to see you on join us on and learn about some of the some of the things we're working on. >>That's awesome. So let's back up a step for people that have been paying as close attention as they might have. Right? So you guys purchase, um, assets from Docker at the end of last year, really taken over there, they're they're kind of enterprise solutions, and you've been doing some work with that. Now, what's interesting is we we cover docker con, um, A couple of months ago, a couple three months ago. Time time moves fast. They had a tremendously successful digital event. 70,000 registrants, people coming from all over the world. I think they're physical. Event used to be like four or 5000 people at the peak, maybe 6000 Really tremendous success. But a lot of that success was driven, really by the by the strength of the community. The docker community is so passionate. And what struck me about that event is this is not the first time these people get together. You know, this is not ah, once a year, kind of sharing of information and sharing ideas, but kind of the passion and and the friendships and the sharing of information is so, so good. You know, it's a super or, um, rich development community. You guys have really now taken advantage of that. But you're doing your Miranda's thing. You're bringing your own technology to it and really taking it to more of an enterprise solution. So I wonder if you can kind of walk people through the process of, you know, you have the acquisition late last year. You guys been hard at work. What are we gonna see on September 16. >>Sure, absolutely. And, you know, just thio Give credit Thio Docker for putting on an amazing event with Dr Khan this year. Uh, you know, you mentioned 70,000 registrants. That's an astounding number. And you know, it really is a testament thio. You know, the community that they've built over the years and continue to serve eso We're really, really happy for Docker as they kind of move into, you know, the next the next path in their journey and, you know, focus more on the developer oriented, um, solution and go to market. So, uh, they did a fantastic job with the event. And, you know, I think that they continue toe connect with their community throughout the year on That's part of what drives What drove so many attendees to the event assed faras our our history and progress with with Dr Enterprise eso. As you mentioned mid November last year, we did acquire Doctor Enterprise assets from Docker Inc and, um, right away we noticed tremendous synergy in our product road maps and even in the in the team's eso that came together really, really quickly and we started executing on a Siris of releases. Um that are starting Thio, you know, be introduced into the market. Um, you know, one was introduced in late May and that was the first major release of Dr Enterprise produced exclusively by more antis. And we're going to announce at the launch pad 2020 event. Our next major release of the Doctor Enterprise Technology, which will for the first time include kubernetes related in life cycle management related technology from Mirant is eso. It's a huge milestone for our company. Huge benefit Thio our customers on and the broader user community around Dr Enterprise. We're super excited. Thio provide a lot of a lot of compelling and detailed content around the new technology that will be announcing at the event. >>So I'm looking at the at the website with with the agenda and there's a little teaser here right in the middle of the spaceship Docker Enterprise Container Cloud. So, um, and I glanced into you got a great little layout, five tracks, keynote track D container track operations and I t developer track and keep track. But I did. I went ahead and clicked on the keynote track and I see the big reveal so I love the opening keynote at at 8 a.m. On the 76 on the September 16th is right. Um, I, Enel CEO who have had on many, many times, has the big reveal Docker Enterprise Container Cloud. So without stealing any thunder, uh, can you give us any any little inside inside baseball on on what people should expect or what they can get excited about for that big announcement? >>Sure, absolutely so I definitely don't want to steal any thunder from Adrian, our CEO. But you know, we did include a few Easter eggs, so to speak, in the website on Dr Enterprise. Container Cloud is absolutely the biggest story out of the bunch eso that's visible on the on the rocket ship as you noticed, and in the agenda it will be revealed during Adrian's keynote, and every every word in the product name is important, right? So Dr Enterprise, based on Dr Enterprise Platform Container Cloud and there's the new word in there really is Cloud eso. I think, um, people are going to be surprised at the groundbreaking territory that were forging with with this release along the lines of a cloud experience and what we are going to provide to not only I t operations and the Op Graders and Dev ops for cloud environment, but also for the developers and the experience that we could bring to developers As they become more dependent on kubernetes and get more hands on with kubernetes. We think that we're going thio provide ah lot of ways for them to be more empowered with kubernetes while at the same time lowering the bar, the bar or the barrier of entry for kubernetes. As many enterprises have have told us that you know kubernetes can be difficult for the broader developer community inside the organization Thio interact with right? So this is, uh, you know, a strategic underpinning of our our product strategy. And this is really the first step in a non going launch of technologies that we're going to make bigger netease easier for developing. >>I was gonna say the other Easter egg that's all over the agenda, as I'm just kind of looking through the agenda. It's kubernetes on 80 infrastructure multi cloud kubernetes Miranda's open stack on kubernetes. So Goober Netease plays a huge part and you know, we talk a lot about kubernetes at all the events that we cover. But as you said, kind of the new theme that we're hearing a little bit more Morris is the difficulty and actually managing it so looking, kind of beyond the actual technology to the operations and the execution in production. And it sounds like you guys might have a few things up your sleeve to help people be more successful in in and actually kubernetes in production. >>Yeah, absolutely. So, uh, kubernetes is the focus of most of the companies in our space. Obviously, we think that we have some ideas for how we can, you know, really begin thio enable enable it to fulfill its promise as the operating system for the cloud eso. If we think about the ecosystem that's formed around kubernetes, uh, you know, it's it's now really being held back on Lee by adoption user adoption. And so that's where our focus in our product strategy really lives is around. How can we accelerate the move to kubernetes and accelerate the move to cloud native applications on? But in order to provide that acceleration catalyst, you need to be able to address the needs of not only the operators and make their lives easier while still giving them the tools they need for things like policy enforcement and operational insights. At the same time, Foster, you know, a grassroots, um, upswell of developer adoption within their company on bond Really help the I t. Operations team serve their customers the developers more effectively. >>Well, Dave, it sounds like a great event. We we had a great time covering those open stack events with you guys. We've covered the doctor events for years and years and years. Eso super engaged community and and thanks for, you know, inviting us back Thio to cover this inaugural event as well. So it should be terrific. Everyone just go to Miranda's dot com. The big pop up Will will jump up. You just click on the button and you can see the full agenda on get ready for about a month from now. When when the big reveal, September 16th will happen. Well, Dave, thanks for sharing this quick update with us. And I'm sure we're talking a lot more between now in, uh, in the 16 because I know there's a cube track in there, so we look forward to interview in our are our guests is part of the part of the program. >>Absolutely. Eso welcome everyone. Join us at the event and, uh, you know, stay tuned for the big reveal. >>Everybody loves a big reveal. All right, well, thanks a lot, Dave. So he's Dave. I'm Jeff. You're watching the Cube. Thanks for watching. We'll see you next time.

>>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.