>> Narrator: Live from San Diego California it's theCUBE covering Cisco Live, US, 2019 brought to you by Cisco and its ecosystem partners. >> Welcome back we're here at the San Diego convention center for Cisco Live 2019 and you're watching theCUBE the worldwide leader in enterprise tech coverage helping extract the signal from the noise. I'm Stu Miniman we've had three days wall to wall coverage my co-host Dave Vellante and Lisa Martin are all in the house and I'm really excited to actually sit down one on one with one of the users at this user conference the 30th anniversary conference actually for Cisco with their users and partners over 28,000 so speaking for all of them right? We have Sebastien Morissette who's an IT architect specialist at Intact Financial Corporation come to us from beautiful Montreal Canada. >> Exactly. >> All right thank you so much for joining us so Sebastien first of all how many Cisco Lives have you been too? >> Honestly this is my first. >> Oh absolutely exciting for that, my first one I came too was actually 10 years ago I joked at the 20th anniversary they went back 20 years to have some 80's bands they had The Bangles and Devo on and now on the 30 year they moved 10 years forwards they have two great bands from the 90's Wheezer and Foo Fighters so your first time at Cisco Live give us your general impressions of the show. >> Well actually it's been very great I've had a lot of appearances I had to do as well so I got some sessions in I did some work as well so it's amazing to see how these events unfold right? Like the sheer size of this thing and how many people are involved, how many booths how many technical sessions you can have so, I was very pleased I'm here with a lot of people from my team as well from Intact so you know we get the chance to do stuff outside of the work area as well so it's interesting right? It's giving us this opportunity to really deep dive into what we love which is technology but at the same time spend some time together outside of work. >> That's awesome, we've had gorgeous weather here in San Diego hope you definitely get to see the sights before we geek out on some of the technology just give our audience a little bit about Intact and the insurance business but give us a little bit about the history of the company and core focus. >> Okay well Intact is a company that was, they grew as acquisitions with acquisitions we've typically, we were ING Canada back in, before 2010 and afterwards we were publicly traded now so we're Intact Financial Corp. Typically we're the number one PNC insurer in Canada and we've been working with different partners to build our data center 2.0 initiative which is kind of a new offering of you know modern IT services within Intact. >> Okay great and just to, your purview in the company and just the comment about the company is you know when you talk about those transformations you know MNA is something we see a lot in your industry and put some extra special challenges in place when you're doing that but tell us a little bit about what's under your role and scope as to kind of locations, people however you measure you know what, boxes or ports or whatever. >> Okay well you know typically my role is lead architect within the infrastructure and security group for North America Intact through acquisition we actually bought OneBeacon Insurance last year, so typically we now have a US presence as well in specialty insurance, specialty lines so typically whenever we're looking at different technologies we look at the skills sets that we have, we look to see what can be the better half for us to you know accelerate and be more agile in how we actually consume technology so in some cases whatever we're looking at building up these new features like I was talking for data center 2.0 it happens that some of the technologies and the skill sets we have were with Cisco which is why we are here today with the team. >> All right so Sebastien you talk about data center 2.0 and transformation there at the organizational level is it branded data center transformation does the word digital transformation come up in your discussions? >> Yeah data center 2.0 is actually kind of the project name that we've been giving this initiative for the past two years but it really is at the essence a digital transformation, what we're doing is we're typically taking training wheels to the Cloud so we're building an on-prem private Cloud offering with multi-sites so we have three sites in the scope right now and the goal is really to actually allow our business to expand into the Cloud while being in a secure on-prem environment when we get to that maturity level where we feel we're ready to actually really go into public Cloud our software engineering teams our development teams will have experienced it on-prem safely and will have a confidence level to bringing them there so it has been transformational also because we decided to push DevOps culture as far as we can from an infrastructure team so we were trying to get all the adoption from our software engineering folks to actually structure themselves, bring on DevOps team and that we can share with them so they can actually be more agile and get a lot more done without having to depend on us and spend a lot of time waiting for VM's or stuff so trying to accelerate that. >> Awesome I love that 'cause sometimes you hear okay we're going to 2.0 it's basically a fancy refresh but we're going to keep things mostly the same when I hear DevOps I know that culture and organization is something that is a key piece of that, I have to ask you without getting down into the pedantics of this, when you say a private Cloud that's in your data center we understand some of the covenants and reasons what you have but how do you determine whether, what was your guiding line as to how is this a Cloud versus just some new virtualized environment? >> I've had the chance to have great executive sponsorship from my senior vice president typically we were looking at how can we access the Cloud? The way I approached it was overhauling what we do was not the route to go what I asked him to do is say you know trust me I'll start with a clean slate and we will build a brand new landing area for Cloud native applications and new methodologies for modern IT services so typically in the end we didn't overhaul anything that we had we built a brand new sandbox for Intact to be able to work with so we went from disaster recovery to business continuity in that move we've built a three site approach because when I was looking at kind of my capex expenditure if I was building two sites to be fully resilient and be business continuity I would be spending 200% of my capital to actually build up that capacity when you go to three sites it seems awkward but you just need 50% on each site of your capacity to ensure 100% of coverage of your requirements, so in the end you're actually spending 150% of your capacity, or your capex to buy the compute, so there's an incentive there as well. So to answer your question more precisely it's very easy for us to see how it's a Cloud because we're not operating it the same way we're operating our other environment and since we started from scratch every process has been revised we haven't kept everything we had before so we had the chance to build something brand new for that specific offering that our software engineering groups were asking us to do. >> All right that's exciting stuff there when you look at these multi-site deployments I think back in my career and I worked on some of these environments, management, security and networking are absolutely critical, I hear oh okay I've got 50% in each oh my God what if a site gets isolated and I can't talk to those other two so luckily I'm guessing Cisco has something to do with your rollout, we're obviously here at Cisco Live so give us a little bit inside the architecture and especially you know what kind of Cisco pieces are you using? >> All right well you know typically the way that our story started was kind of weird the first thing we've done is we've actually went to Cisco to redesign a DMZ and we got out from Cisco Montreal team with an idea to not just change and buy ACI switches for the DMZ but actually rebuild our whole design to you know integrate ACI into the fabric and then when you start talking about firewalls or switches they tell you well with ACI you have contracts so it really started that way so we built an ACI fabric with the Cisco HyperFlex hyper-converged infrastructure as our compute layer so typically think of it as Intact is building our new version of a software defined data center. So with building that we have all the components so we have the virtualization like you spoke of earlier which is running like you know VMware on site, on top of the HyperFlex and then we have the ACI since we had three sites we topped it off with the multi-site orchestrator to be able to manage consistent policies around all of our three sites and in the end we needed to have an orchestrator to be able to deploy the content onto that and when we were looking at it early on it was Clicker when Cisco purchased Clicker we were looking at finding a Cloud management platform, so we ended up using CloudCenter which is now CloudCenter Suite and in the way we were using it, which was a little atypical from the typical way clients are using CloudCenter today we're taking it into the data center and out to the Cloud whereas when I was talking with Kip Compton earlier this week he was saying you know what sometimes our clients buy it more for the Cloud first and I was like well we have like the inverse story of exactly how we did the opposite but it works as well, so typically where we stand today I have the three sites we're able to deploy with CloudCenter we've got multi-site on top of that and the idea it really is that, I spoke about training wheels earlier well we're taking them off right? In the next couple of weeks we're starting to look into negotiations with public Cloud providers trying to move towards the public Cloud and you know there's exciting news that came out from Cisco this week while I was here about the fact that now you know they're forecasting a lot more collaboration with Microsoft and AWS and now they have all the three major Cloud providers covered with ACI Anywhere so that means all of our security that you were talking about earlier will now have a consistent policy model applied all, everywhere so to be honest I'm not too concerned about if we did a good choice a couple of years back I think we're in our sweet spot right now. >> Yeah and you're right it's a different story than we've generally heard from Cisco and some customers which is I have all of these public Cloud's and I have my data center and I'm looking for some piece to help tie it together and that the CloudCenter Suite is there so you feel you're confident with the platform that you chose and that's going to give you the flexibility as to whichever public Cloud or public Cloud you choose are you at the point there that do you know which public Cloud you're going to be on or maybe it's a little too early? >> Well to be honest you know we're keeping our options open you know we have different providers that are offered, you know the major public one there's Amazon there's Google Cloud we're not closing any options it's really a question of us to do the same secure approach that we've done right now with this offering to really go one at a time make sure that we're able to nail it down, make it secure that we get all the information back so I'm not at a possibility right now to disclose which ones we're dealing with because we're still negotiating but in the end we're not limiting ourselves we just want to be able to scale. >> Right you're confident that the Cisco solution that you choose will give you the flexibility no matter which one you use or if you use multiples or need to make switches along the way? >> Yeah. >> Question I have for you on that is when you look at multi-Cloud one of the things that are challenging for companies is how do I make sure I've got the skillsets because workloads might be portable, networks might be connected but understanding how I manage each of those environments so do you feel CloudCenter Suite's going to help you through that? You know what do you see as you look out over your roadmap as to what that's going to mean for you know your DevOps team and the people managing this environment as it spreads out to the public Cloud? >> Actually I'm feeling really confident because you know especially after seeing a couple of sessions of what Roland Acra and Kip have announced for the data center and for the Cloud piece we're seeing more and more normalization being done by Cisco to actually allow us to be confident in the fact that on prem we're doing ACI and that our policies are going to be mapped to the constructs of the different Cloud providers. So for me what it means is I don't necessarily need to become specialized in how we're going to be operating inside of a Cloud we need to make sure that we get the proper policies built into the different products you know Cisco's branding it the Anywhere right? They have the HX Anywhere the ACI Anywhere and typically that's what we like about it is I can have one consistent set of skillsets and allow the people to use it one thing I found interesting about this week and it's not necessarily to do like more promotion for Cisco is like the Cloud First ACI right? So being able to be starting with ACI in the Cloud I found that was kind of interesting because when you know how the multi-site orchestrator works means apps you build out in the Cloud you're going to be able to to pull back in through the MSO and push it back on prem or anywhere in other Clouds afterwards so I found that was very intuitive of them to go to that route of allowing us to you know transparently migrate apps between sites. >> All right so Sebastien you're using a lot of the latest and greatest from Cisco you talk about the HX the ACI the CloudCenter Suite what advice do you give to your peers out there and they say you know I've used Cisco products for a long time Cisco makes great products but you know simplicity and management across the product lines was something that you know needed some work what does the Cisco of today look like you know what's working well? What still would you like to see them progress on? >> Well you know for us one of the things that was nice like I mentioned earlier is we're typically going greenfield so I didn't have a lot of the issues that other companies might be facing if they're trying to take their brownfield and actually make it into what we've built so my first advice would be if you're able to get the executive sponsorship to build a greenfield environment there's nothing in Cloud native applications that is you know symmetric with the traditional environment of a data center, it's completely different ways of working we have one week sprints we patch everything as it comes out if an application goes into the environment it needs to be functional with that patching cycle of almost every time we're at n or n-1 so, my thing is think about applications as being the center of what you actually need and not the infrastructure, let the infrastructure be what it is because you're going to be anywhere right? So that's one of the things I would say, from what you said about Cisco and the integration you were right, we have lived a couple of items like that in the last two years and a half, however I've noticed that these new software components like CloudShare and everything not necessarily the hardware part Cisco nails hardware like it works they've been doing it for years the thing is with these software teams they're very customer driven we have access to the engineers now I mean we've had meetings with the Canadian execs Roland Acra's team we were able to get access to the developers and the teams here in the US so, every company has challenges I would be lying if I told you that even at Intact we don't have silos and we don't have issues sometimes with different teams managing together but I feel as if at least for the technologies that we're using they've done good work for us to actually help us get through that. >> Well it's interesting Sebastian you bring that up because I look at you say okay, you've got a greenfield environment awesome, we can go do some new tech, well let's throw in there the DevOps and let's change all the other pieces you're like completely overhauling your environment how much of that were there some new team members that came in as part of that or you know I look people, process and technology sounded like you were taking it all on at once, did that work well? Would you have if you looked back would you have changed some of the ordering and maybe you know gotten one piece before the other or did it help to kind of you know start brand new start fresh and get everything going? >> Well I wouldn't redo the part of starting fresh however, it helped us get really good pace and work you know it's our first agile project as an infrastructure group so all of that was great learning experience the only thing I would say is you need to make sure your organization is ready for that level of change because it's one thing to have one VP sponsorship to actually build out this type of approach but where we struggled a little bit was afterwards getting the rest of our IT organization to kind of want to get onboard. because we are building something new, the traditional environment is not disappearing and we're telling our software engineering groups here's a new area where you can play in but you know typically I'd say that it's been well received we have not had the need to build new skillsets because we're doing infrastructure as code so typically a lot of the stuff we're building we're making sure it's automated so that way it's very nice and lean and when we build a new site we have a lot of automation already built in so we can properly just deploy so lessons learned like you've asked me I'd say that typically I'd probably do much of what I did the same way, but I would work a little bit more on the people area just to make sure that the message is clearly understood that what we're building is for the future of Intact and make sure that we spend a little bit more time managing that aspect because for the technology it's fine for the time it took and everything it's fine, it's really people the change is significant to most of them and when you've been doing something for a long time and someone comes up and disrupts it's like if we were disrupting our own company right? So typically I'd say, that would be something that I would say to people manage that properly or you will have a lot more work to do inside of that initiative to actually gain everybody's momentum and get them to be behind you. >> Well Sebastien I really appreciate you walking us through all of your transformation I want to just give you the final word sounds like you've got great access to Cisco really hope you're happy with what you've done final word is to you know your expectations coming into a show like this and you know what your take aways will be from Cisco Live 2019 in San Diego? >> Well outside from the amazing weather you mean or yeah? so you know typically I like the event I've been to other events before, like I said this is my first time at Cisco but what I've seen is that Cisco's really into getting their customers to understand their technology so they're really present so I really liked how you know we were given the opportunity to do hands on labs and actually learn new technologies so typically great experience coming here and great opportunities and thanks so much for having us. >> Well Sebastien Morissette congratulations to your team at Intact and thank you so much for sharing this story. >> Thank you so much. >> All right we've got a little bit more left here of three days wall to wall coverage Cisco Live 2019 in San Diego for Dave Vellante, Lisa Martin I'm Stu Miniman and thanks as always for watching theCUBE. (electronic jingle)

>>from around the globe. It's the Cube with coverage of Coop con and cloud, native con Europe 2020 Virtual brought to you by Red Hat, The Cloud Native Computing Foundation and its ecosystem partners >>Welcome back. This is the Cube coverage of Cube Con Cloud, native con, the European show for 2020. I'm your host to Minuteman. And when we talk about the container world, we talk about what's happening in cloud. Native storage has been one of those sticking points. One of those things that you know has been challenging, that we've been looking to mature and really happy to welcome back to the program two of our cube alumni to give us the update on the state of storage for the container world. Both of them are oh, founders and CEOs. First of all, we have Xiang Yang from Rancher Labs, of course, was recently acquired by Sue Save it and the intention to acquire on and also joining us from early the relay. Who is with port works? Shang Amerli. Thanks so much for joining us. Thank you. Thank you. Alright. So early. I actually I'm going to start with you just cause you know we've seen, you know, a couple of waves of companies working on storage. In this environment, we know storage is difficult. Um, And when we change how we're building things, there's architectural things that can happen. Eso maybe if you could just give us a snapshot, you know, Port works, you know, was created to help unpack this. You know, straight on here in 2020 you know, where you see things in the overall kind of computer storage landscape? >>Absolutely. Still, before I kind of jump into port works. I just want to take a minute to publicly congratulate the the whole rancher team, and and Shang and Shannon And will China have known those folks for a while there? They're kind of true entrepreneurs. They represent the serial entrepreneur spirit that that so many folks know in the valley, and so, you know, great outcome for them. We're very happy for them and ah, big congrats and shout out to the whole team. What works is is a little over five years old, and we've been kind of right from the inception of the company recognized that to put containers in production, you're gonna have to solve, not just the orchestration problem. But the issue of storage and data orchestration and so in a natural kubernetes orchestrates containers and what works orchestrates storage and data. And more specifically, by doing that, what we enable is enterprises to be able to take APS that are containerized into production at scale and and have high availability. Disaster recovery, backup all of the things that for decades I t has had to do and has done to support application, reliability and availability. But essentially we're doing it for purpose with the purpose build solution for containerized workloads. >>Alright, shaming. Of course, storage is a piece of the overall puzzle that that ranchers trying to help with. Maybe if you could just refresh our audience on Longhorn, which your organization has its open source. It's now being managed by the CN. CF is my understanding. So help us bring Longhorn into the discussion >>thanks to. So I'm really glad to be here. We've I think rancher and port work started about the same time, and we started with a slightly different focus. More is exactly right to get containers going, you really need both so that the computer angle orchestrating containers as well as orchestrating the storage and the data. So rancher started with, ah, it's slightly stronger focus on orchestrating containers themselves, but pretty quickly, we realized, as adoption of containers grow, we really need it to be able to handle ah, storage feather. And like any new technology, you know, uh, Kubernetes and containers created some interesting new requirements and opportunities, and at the time, really, they weren't. Ah, a lot of good technologies available, you know, technologies like rook and SEF at the time was very, very premature, I think, Ah, the You know, we actually early on try to incorporate ah, the cluster technology. And it was just it was just not easy. And And at the time I think port Works was, ah, very busy developing. Ah, what turned out to be there flagship product, which we end up, end up, uh, partnering very, very closely. But but early on, we really had no choice but to start developing our own storage technology. So Long horn. As a piece of container storage technology, it's actually almost as oh, there's rancher itself. When about funding engineers, we hired he he ended up, you know, working on it and Then over the years, you know the focus shift that I think the original version was written in C plus plus, and over the years it's now being completely re written in Golan. It was originally written more for Docker workload. Now, of course, everything is kubernetes centric. And last year we you know, we we decided to donate the Longhorn Open Source project to CN CF. And now it's a CN CF sandbox project, and the adoption is just growing really quickly. And just earlier this year, we we finally ah decided to we're ready to offer a commercial support for it. So So that's that's where rancher is. And with longhorn and container storage technology. >>Yeah, it has been really interesting to watch in this ecosystem. A couple of years ago, one of the Q con shows I was talking to people coming out of the Believe It was the Sigs, the special interest group for storage, and it was just like, Wow, it was heated. Words were, you know, back and forth. There's not a lot of agreement there. Anybody that knows the storage industry knows that you know standards in various ways of doing things often are contentious and there's there's differences of opinion. Look at the storage industry. You know, there's a reason why there's so many different solutions out there. So maybe it love to hear from early. From your standpoint, things are coming to get a little bit more. There are still a number of options out there. So you know, why is this kind of coop petition? I actually good for the industry? >>Yeah, I think this is a classic example of Coop petition. Right? Let's let's start with the cooperation part right? The first part of time the you know, the early days of CN, CF, and even sort of the Google Communities team, I think, was really very focused on compute and and subsequent years. In the last 34 years, there's been a greater attention to making the whole stack works, because that's what it's going to take to take a the enterprise class production and put it in, you know, enterprise class application and put it in production. So extensions like C and I for networking and CS I container storage interface. We're kind of put together by a working group and and ah ah you know both both in the CN CF, but also within the kubernetes Google community. That's you talked about six storage as an example. And, you know, as always happens, right? Like it It looks a little bit in the early days. Like like a polo game, right where folks are really? Ah, you know, seemingly, uh, you know, working with each other on on top of the pool. But underneath they're kicking each other furiously. But that was a long time back, and we've graduated from then into really cooperating. And I think it's something we should all be proud of. Where now the CS I interface is really a A really very, very strong and complete solution tow, allowing communities to orchestrate storage and data. So it's really strengthened both communities and the kubernetes ecosystem. Now the competition part. Let's kind of spend. I want to spend a couple of minutes on that too, right? Um, you know, one of the classic things that people sometimes confuse is the difference between an overlay and an interface. CSC is wonderful because it defines how the two layers off essentially kind of old style storage. You know, whether it's a san or ah cloud, elastic storage bucket or all of those interact with community. So the the definition of that interface kind of lay down some rules and parameters for how that interaction should happen. However, you still always need an overlay like Port Works that that actually drives that interface and enables Kubernetes to actually manage that storage. And that's where the competition is. And, you know, she mentioned stuff and bluster and rook and kind of derivatives of those. And I think those have been around really venerable and and really excellent products for born in a different era for a different time open stack, object storage and all of that not really meant for kind of primary workloads. And they've been they've been trying to be adapted for, for for us, for this kind of workload. Port Works is really a built from right from the inception to be designed for communities and for kubernetes workloads at enterprise scale. And so I think, you know, as I as I look at the landscape, we welcome the fact that there are so many more people acknowledging that there is a vital need for data orchestration on kubernetes right, that that's why everybody and their brother now has a CS I interface. However, I think there's a big difference between having an interface. This is actually having the software that provides the functionality for H. A, D R. And and for backup, as as the kind of life cycle matures and doing it not just at scale, but in a way that allows kind of really significant removal or reduction off the storage admin role and replaces it with self service that is fully automated within communities. Yeah, if I >>can, you know, add something that that I completely agree. I mean, over the Longhorns been around for a long time. Like I said, I'm really happy that over the years it hasn't really impacted our wonderful collaborative partnership with what works. I mean, Poll works has always been one of our premier partners. We have a lot of, ah, common customers in this fight. I know these guys rave about what works. I don't think they'll ever get out for works. Ah, home or not? Uh huh. Exactly. Like Morissette, you know, in the in the storage space, there's interface, which a lot of different implementations can plugging, and that's kind of how rancher works. So we always tell people Rancher works with three types of storage implementations. One is let we call legacy storage. You know, your netapp, your DMC, your pure storage and those are really solid. But they were not suddenly not designed to work with containers to start with, but it doesn't matter. They've all written CS I interfaces that would enable containers to take advantage of. The second type is some of the cloud a block storage or file storage services like EBS, GFS, Google Cloud storage and support for these storage back and the CS I drivers practically come with kubernetes itself, so those are very well supported. But there's still a huge amount of opportunities for the third type of you know, we call container Native Storage. So that is where Port Works and the Longhorn and other solutions like open EBS storage OS. All these guys fitting is a very vibrant ecosystem of innovation going on there. So those solutions are able to create basically reliable storage from scratch. You know, when you from from just local disks and they're actually also able to add a lot of value on top of whatever traditional or cloud based, persistent storage you already have. So so the whole system, the whole ecosystem, is developing very quickly. A lot of these solutions work with each other, and I think to me it's really less of a competition or even Coop petition. It's really more off raising the bar for for the capabilities so that we can accelerate the amount of workload that's been moved onto this wonderful kubernetes platform in the end of the benefit. Everyone, >>Well, I appreciate you both laying out some of the options, you know, showing just a quick follow up on that. I think back if you want. 15 years ago was often okay. I'm using my GMC for my block. I'm using my netapp for the file. I'm wondering in the cloud native space, if we expect that you might have multiple different data engine types in there you mentioned you know, I might want port works for my high performance. You said open EBS, very popular in the last CN CF survey might be another one there. So is do we think some of it is just kind of repeating itself that storage is not monolithic and in a micro service architecture. You know, different environments need different storage requirements. >>Yeah, I mean quick. I love to hear more is view as well, especially about you know, about how the ecosystem is developing. But from my perspective, just just the range of capabilities that's now we expect out of storage vendors or data management vendors is just increased tremendously. You know, in the old days, if you can store blocks to object store file, that's it. Right. So now it's this is just table stakes. Then then what comes after that? There will be 345 additional layers of requirements come all the way from backup, restore the our search indexing analytics. So I really think all of this potentially off or in the in the bucket of the storage ecosystem, and I just can't wait to see how this stuff will play out. I think we're still very, very early stages, and and there, you know what? What, what what containers did is they made fundamentally the workload portable, but the data itself still holds a lot of gravity. And then just so much work to do to leverage the fundamental work load portability. Marry that with some form of universal data management or data portability. I think that would really, uh, at least the industry to the next level. Marie? >>Yeah. Shanghai Bean couldn't. Couldn't have said it better. Right? Let me let me let me kind of give you Ah, sample. Right. We're at about 160 plus customers now, you know, adding several by the month. Um, just with just with rancher alone, right, we are. We have common customers in all common video expedient Roche March X, Western Asset Management. You know, charter communications. So we're in production with a number off rancher customers. What are these customers want? And why are they kind of looking at a a a Port works class of solution to use, You know, Xiang's example of the multiple types, right? Many times, people can get started with something in the early days, which has a CS I interface with maybe say, $10 or 8 to 10 nodes with a solution that allows them to at least kind of verify that they can run the stack up and down with, say, you know, a a rancher type orchestrator, workloads that are containerized on and a network plug in and a storage plugging. But really, once they start to get beyond 20 notes or so, then there are problems that are very, very unique to containers and kubernetes that pop up that you don't see in a in a non containerized environment, right? Some. What are some of these things, right? Simple examples are how can you actually run 10 to hundreds of containers on a server, with each one of those containers belonging to a different application and having different requirements? How do you actually scale? Not to 16 nodes, which is sort of make typically, maybe Max of what a San might go to. But hundreds and thousands of notes, like many of our customers, are doing like T Mobile Comcast. They're running this thing at 600 thousands of notes or scale is one issue. Here is a critical critical difference that that something that's designed for Kubernetes does right. We are providing all off the storage functions that Shang just described at container granted, granularity versus machine granularity. One way to think about this is the old Data center was in machine based construct. Construct everything you know. VM Ware is the leader, sort of in that all of the way. You think of storage as villains. You think of compute and CPUs, everything. Sub sub nets, right? All off. Traditional infrastructure is very, very machine centric. What kubernetes and containers do is move it into becoming an app defined control plane, right? One of the things were super excited about is the fact that Kubernetes is really not just a container orchestrator, but actually a orchestrator for infrastructure in an app defined way. And by doing that, they have turned, uh, you know, control off the infrastructure via communities over to a kubernetes segment. The same person who uses rancher uses port works at NVIDIA, for example to manage storage as they use it, to manage the compute and to manage containers. And and that's marvellous, because now what has happened is this thing is now fully automated at scale and and actually can run without the intervention off a storage admin. No more trouble tickets, right? No more requests to say, Hey, give me another 20 terabytes. All of that happens automatically with the solution like port works. And in fact, if you think about it in the world of real time services that we're all headed towards right Services like uber now are expected in enterprises machine learning. Ai all of these things analytics that that change talk about are things that you expect to run in a fully automated way across vast amounts of data that are distributed sometimes in the edge. And you can't do that unless you're fully automated and and not really the storage admin intervention. And that's kind of the solution that we provide. >>Alright, well, we're just about out of time. If I could just last piece is, you know, early and saying to talk about where we are with long for and what we should expect to see through the rest of this year and get some early for you to you know, what differentiates port works from Just, you know, the open source version. So And maybe if we start with just kind of long or in general and then really from from your standpoint, >>yeah, so it's so so the go along one is really to lower the bar for folks to run state for workloads on on kubernetes we want you know, the the Longhorn is 100% open source and it's owned by CN cf now. So we in terms of features and functionalities is obviously a small subset of what a true enterprise grade solution like Port Works or, um, CEO on that that could provide. So there's just, you know, the storage role. Ah, future settle. The roadmap is very rich. I don't think it's not really Ranchers go Oh, our Longhorns goal to, you know, to try to turn itself into a into a plug in replacement for these enterprise, great storage or data management solutions. But But they're you know, there's some critical critical feature gaps that we need address. And that's what the team is gonna be focusing on, perhaps for the rest of the year. >>Yeah, uh, still, I would I would kind of, you know, echo what Chang said, right? I think folks make it started with solutions, like longer or even a plug in connector plug in with one of their existing storage vendors, whether it's pure netapp or or EMC from our viewpoint, that's wonderful, because that allows them to kind of graduate to where they're considering storage and data as part of the stack. They really should that's the way they're going to succeed by by looking at it as a whole and really with, You know, it's a great way to get started on a proof of concept architecture where your focus initially is very much on the orchestration and the container ization part. But But, as Xiang pointed out, you know what what rancher did, what I entered it for Kubernetes was build a simple, elegant, robust solution that kind of democratized communities. We're doing the same thing for communities storage right? What Port works does is have a solution that is simple, elegant, fully automated, scalable and robust. But more importantly, it's a complete data platform, right? We we go where all these solutions start, but don't kind of venture forward. We are a full, complete lifecycle management for data across that whole life cycle. So there's many many customers now are buying port works and then adding deal right up front, and then a few months later they might come back and I'd backup from ports. So two shanks point right because of the uniqueness of the kubernetes workload, because it is an app defined control plane, not machine to find what is happening is it's disrupting, Just like just like virtualization day. VM exist today because because they focused on a VM version off. You know, the their backup solution. So the same thing is happening. Kubernetes workloads are district causing disruption of the D r and backup and storage market with solutions like sports. >>Wonderful. Merlin Chang. Thank you so much for the updates. Absolutely. The promise of containers A Z you were saying? Really, is that that Atomic unit getting closer to the application really requires storage to be a full and useful solution. So great to see the progress that's being made. Thank you so much for joining us. >>Welcome, Shannon. We look forward to ah, working with you as you reach for the stars. Congratulations again. We look >>forward to the containing partnership morally and thank you. Still for the opportunity here. >>Absolutely great talking to both of you And stay tuned. Lots more coverage of the Cube Cube Con cloud, native con 2020 Europe. I'm stew minimum. And thank you for watching the Cube. Yeah, yeah, yeah, yeah, yeah, yeah