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

>>from the Cube Studios in >>Palo Alto and Boston connecting with thought leaders all around the world. This is a cube conversation. Hi. I'm stupid, man. And welcome to a cube conversation. I'm coming to you from our Boston area studio. Happy to welcome to the program. First time guest on the program. Francis Mattis. He is the vice president of engineering at Pensando. Francis. Thanks so much for joining us. >>Thank you. Good to be here. All >>right. So, Frances, you and I actually overlapped. Ah, you know, some of the companies who work with, you know, if anybody familiar with Pensando, you have worked with some of the mpls team over the years through some of those spin ins, but for our audience, give us a little bit about your background. You know, what brought you to help and be part of the team that you started pensando? >>Sure. Yeah. Yeah. So I started my career with Advanced Micro Devices in the mid nineties, got out of school, really wanted to build micro processors. And so, Andy, being in Austin, Texas, and be going to ls you for undergrad was perfect sort of alignment. And so I got to say M. D and Austin built K five worked on that team or kind of team with K seven. And, uh, when I came out to California to help with K, and that brought me to California. And then we got into the dot com era and and being a A and B fighting intel, so to speak, seemed like a hard battle. And so, with the dot com era coming, I just saw this perfect opportunity to jump into the Internet. And so that's how we got into building Internet and data communications equipment, went to the show on systems. We talked a little bit about that earlier, and that got me into storage. From there, I got into a company called on GMO, which was building fibre channel sand equipment. So built chips there, and I got to know the Mpls team there. I always say they hired me off the street. And from that point on, while we've been together since Jews 1001 So 19 years, yeah. Yeah, and I've been building silicon with them and systems for almost 20 years now. So we had quite a journey. Yeah, it's been fun. Great >>stuff. Yeah, you know it's going back, you know, niche on talking about ice scuzzy. You know, in the networking world, you know, it's a little bit of a dark arts in general for most people, you know, understanding the networking protocols and all the various pieces and three and four letter acronyms aren't something that most people are familiar with. Pensando, I'm curious. You know what? You know, networking In general, you're like, I work on Internet stuff and we're the tubes that, you know, Things go around. So when when you describe pensando, you know how to explain that to the people that maybe aren't deep into East, west, south, over on under underlay protocols? >>Yeah, absolutely. So for me, pensando was kind of the sort of the culmination of all the things I've done in my career processing, you know, being able to build compute engines that have programmable, starting with microprocessors, being able to do storage and storage networking with Andy on no, we build a computer with druva and the virtualization layers around the Ethernet interfaces in the adapter with what was really our first smart nick, Um, in 6 4007 timeframe and then with STN in CNI, all of these elements kind of came together. These multiple different layers in the infrastructure stack, if you will, and so pensando for me. What was interesting was the explosion of scale in both space and time with the advent of, let's say, 25 gig 50 gig 100 gig to the server, the notion of very dense computing on in each rack and the need for very high scale After doing all of these technologies and seeing where silicon kind of started to fall in place, I was 16 centimeter. It seemed that bringing this kind of technology to the edge very low power with sort of an end to end security architecture and to end policy engine architecture, distributed services as we're doing all seem to naturally fit into place. And the cloud was already proving this morning when I say the cloud, I mean, the hyper scaler is like Amazon and Microsoft. We are already building these platforms. And so yeah, it dawned on me that, uh I didn't think this was possible unless you built the entire platform. We built the entire system. If you build any one piece, the market transition would take a lot longer. And I think this is true. In technology, history tends to repeat itself, starting with mainframes. When IBM built an entire computer and that built the entire computer, HP built these people. So these kinds of things, um, are important if you want to really push a market transition. And so pensando became this opportunity to take all of these things that I've done in my past life and bring them together in a way that would give a complete stack for the purposes of what I call the new computer, which is basically the data center. And so, um, you know, when my mom asks me, you know, what is it that you're doing? I said, Well, it's just imagine the computer you have right now and multiplying by thousands and thousands stacking in Iraq, and anyone can use it at any one time. And we provide the infrastructure and the mechanisms to be able to Teoh, orchestrate and control that very, very high speed layers. So I don't know if that was a long answer. >>No, no, no. It's fascinating stuff, and you know, when I look at the industry, you know cloud. Of course. Is that just make a wave? That changed the way a lot of people look at this. The way we architect things, there was this belief for a number of years. Well, you know, I'm going to go from this complicated mess that I had in my own data centers and cloud was going to be, you know, inexpensive and easy. And I don't think anybody thinks about inexpensive and easy when they look at cloud computing these days, then add edge into these environments. So I guess what I'm asking is, you know, today's environment, you know, we know I t always is additive. So I have various pieces that I need to put together. You talked about building platforms, and how can it be a complete stack? So companies like Oracle, you know, for many years said we can do everything from the silicon all the way up through your application. Amazon in many ways does the same thing they can. You can build everything on Amazon, but they built out their ecosystem. So how does Pensando fit into this? You know, multi cloud, multi dimensional multi vendor. >>So yeah, so that's a good question. so So one of the things we wanted to do is to be able to bring a systematic management layer two header Genius, beauty. And what I mean by that is in any enterprise data center, modern data center, you're gonna have multiple types of computing. You're gonna have virtual machines, you're gonna have their metal, and you're gonna have containers, or at least in the last, say, three or four years. Chances are you'll have some containers and moving there. And so what we wanted to do was be able to Brighton Infrastructure a management mechanism where all of these head Virginia's types of computing could be managed the same way with respect to policy. What I mean by policy is sort of this declarative or intent based model of I have declared what I'd like to see, whether that the network policy or and and security with data in motion and be able to plot apply it in a distributed manner. Across these different types of hetero genius elements, the cloud has the advantage that it's homogenous for the most part. I mean, they own the entire infrastructure and they can control everything on their now our systems will obviously manage the marginal systems as well, and in many ways that's easier. But bringing together these this notion of heterogeneity these types of computing with one management plane one type of interface for the operator, specifically the networking services operator, was fundamental. That and then the second thing is being able to bring the scale and speed to the edge. So a top of rack switch or something in the in the middle of the network is obviously very dense in terms of this Iot capability. So the silicon area that you spend building a high speed switch is really spent for the most part on the Iot, unless typically, 30 to 40% of the area will be Iot and the rest will be very much hardwired control protocols. We know that as we go to STN services and we want, uh, let's say software defined mechanisms in terms of what the policy looks like, what the protocols look like. The ability to change over time in the lifespan of the computer, which is 3 to 5 years, are you want that to be programmable, very difficult to apply a very dense scale in the core of the network. And so it was an obvious move to bring that to the edge where we could plug it into the server effectively, just like we did. Really? In the UCS system. Uh, no system. >>Yeah, some some really tough engineering challenges. You know, for the longest time, it was very predictable in the networking world, You know, you go from one gig to 10 gig. You know, there was a little discussion how we went the next step, whether, you know, 25 50 40 and 100 gig now. But you talk about containerized architectures. You talk about distributed systems with edge. Things change at a much smaller granular level and change much more frequently. So what are some of the design principles and challenges that you make sure that you're ready for what's happening today but also knowing that, you know, technology changes there always coming, and you need to be able to handle, You know, that next thing. Yeah, >>that's right. Yes. So, uh, I think part of the biggest challenges we have are around power with respect to design power. And then what is the usefulness of each transistor? So, um, when you you have sort of a scale of flexibility. See, views are the most flexible, obviously, but have probably the least performance in them. PG A's are pretty useful in terms of its flexibility, but not very dense in terms of its logic capability. And then you have hardwired a six, which are extremely dense, very much purpose built logic, but completely inflexible. And so the design challenge it was put in front of us is how do we find that sweet spot of extremely programmable, extremely flexible, but still having a cost profile that didn't look like an F PGA And God knows the benefits of the CPU. And and that's where this sort of this notion of domain specific processing came in, which is okay, well, if we're going to solve a few problems, we're going to solve them well. And those few problems are going to be we're gonna bring PC services. We're going to bring networking services. We're going to bring stories, services. We're gonna bring security services around the edge of the computer so that we can offload or let's say, partition correctly the computing problem in a data center. And to do that, we knew a core of sea views wasn't going to do a job that's basically borrowing from this guy to pay this other guy. Right? So what we wanted to do was bring this notion of domain specific processing, and that's where our design challenges came in, which is okay, So now we build around this language called P four, What is the most optimal way to pack? The most amount of threads are processing elements into the silicon while managing the memory bandwidth, which is obviously, you know, packet processing is it has been said to be embarrassingly parallel, which is true. However, the memory bandwidth is insane. And so how do we build a system that insurance that memory is not the bottleneck? Obviously, we're producing a lot of data or, uh, computing a lot of data. And so So these were some of our design challenges. All of that within a power envelope where this part of this device could sit at the edge inside of a computer within a typical power profiling by PC, a attached card in a modern computer. So that was a huge design challenge for us. >>Yeah, I'd love to hear, you know, it was a multi year journey toe solution. And I think of the old World. It was very much a hardware centric 18 to 24 months for design and all the tape out you need to do on this. Sounds like obviously there is still hardware, but it is more software driven. Then it would have been, you know, 10 years ago. So give us some of the ups and downs in that journey. Love to hear any. Any stories that you can share their Well, yeah, I >>think you know, good question. It's always there's always ups and downs in anything you do, especially in the start up. And I think one of the biggest challenges we we've faced is, uh, the exact hardware software boundary. So what is it that you want in hardware? What is it that you want in software And, uh, you know, one of the greatest assets and our company depends on who are the people. We have amazing software and hardware architects who work extremely well together because most of us have been together for so long. So, um, so that always helps when you start to partition the problem. We spent the first year of Pensando, which was basically 2017. The company was founded really thinking through this problem, would it for for all the problems, we wanted to solve the goals that were given to us and and security. Okay, so I want to be able to terminate TCP and initiate TLS connections. What's the right architecture for that? I want to be able to do storage off load and be able to provide encryption of data at rest data in motion. I want to be able to do compression these kinds of things. What's the right part of our software boundary for that? What do we what do we hardwire in silicon versus what we make it programmable and silicon, obviously, but still through a computing engine. And so we spent the first year of the company really thinking through those different partitioning problems, and that was definitely a challenge. And we spent a lot of time and and, uh, you helped me conference rooms and white boards figuring that out. And then 2018. The challenge there was now taking this architecture, this sort of technology substrate, if you will that we built and then executing on it, making sure that it was actually going to yield what we hope that would that we would be able to provide the services. When we talk about El four firewall at line rate, that's completely programmable. Uh, we achieved that. Can we do load balancing? And we do all of it with this before processing engine and the innovations we brought before satisfy all of these requirements we put for us. And so 2018 was really about execution. And there you always have. The challenge is in execution. In terms of, you know, things are going to go wrong. It's not. It's not. If it's when and then how do you deal with it? And so again, um, I would say the biggest challenge and execution is, uh, containing the changes. You know, it's so easy for things to change, especially when you're trying to really build a software platform right, because it's always easy to sort of kick the can and say we'll deal with that later and software. But we know that given what we're trying to do, which is build a system that is highly performance, um, you can't get that. Can you have to deal with it when it comes in. So we spend a lot of time doing performance analysis, making sure that all these applications we were building we're going t yield the right performance. And so that was quite a challenge. And then 2019 was kind of the year of shaping the product. Really lots of product design. Okay, now that we have this technology and it does these, he says that we wanted to do these pieces meaning services. What are all the different ways we can shake this product after talking to customers for, you know, months and months and months. You know, Sony is very much custom, customer driven customer centric. So we we were fortunate enough that we got to spend a lot of time with customers and then that brings us out of challenges, right? Because every customer has a unique problems and so I don't know how to reform this product around a solution that solves quite a bit of problems that really brings value. And so that was the those are the challenges in 2019 which we overcame. Now, obviously we have several releases that we've come out with already. We've got a six and the chips and the It's all there now. So now, 2020. Unfortunately, covitz here, But this is this is a year of growth. This is the year that we really bring it out into the world with our partners and our customers and show how this technology has been developed and benefit will benefit customers over over the next years. Two years. >>Frances really appreciate the insight there. Yeah, that that discussion of the hardware versus software brings back memories for May. Lots of heated debates. A CIO What? One of lines you know we've used on the Cube many times is you know, you know, software will eventually work. Hardware will eventually break. So those trade rto >>taught me something over time ago. He said that uh huh, hardware is hard to change. Software is hard to stop changing. So >>that that's a great one to All right, So you gave us through the last three years journey. Give us a little bit. Look, you know, on the next three years and where you expect pensando to be going >>Sure. Where I see pensando in the next three years as we go through this market transition is uh, both a market leader in a thought leader in terms of the next wave of data center edge computing, whether the, uh in the service provider space, whether it be in the enterprise space or whether it be in the cloud space, the hyper hyper scale of space. As I was mentioning in the beginning, we had when we were talking about, uh, the journey. Market transitions of this major really require understanding the entire stack. If you provide a piece and someone else provides a piece, you will eventually get there. But it's a matter of when, and by the time you get there, there's probably something new. So, you know, uh, time in and of itself is an innovation in this area, especially when you're dealing with the market transition like this. And so we've been fortunate enough that we're building the entire system when we go from the transistors to the rest of the FBI's way, have the entire staff. And so where I see us in three years is not only being a market leader in this space, but also being a thought leader in terms of what does domain specific processing look like at the edge. Um, you know, what are the tools? What are the techniques for? Really a z save? Democratizing the cloud bringing, bringing this technology to everyone. >>Excellent. Well, hey, Frances, That has been a pleasure to talk with you. Thank you so much. Congratulations on the journey so far and I can't wait to see you. How? Thanks for going >>forward. Yeah, we're excited, and I appreciate it. Thank you for your time to. All >>right, check out the cube dot net. We've got lots of back catalogue with pensando. Also, I'm stew minimum. And thank you for watching the Q. Yeah, yeah, yeah.

>>from Miami Beach, Florida It's the Q covering a Cronus Global Cyber Summit 2019. Brought to you by a Cronus. >>Welcome back with Cubes Coverage here for two days at the Cronus Global Cyber Sum of 2019. I'm John Courier, Post keeper in Miami Beach at the Fontainebleau Hotel, and I am here with the CEO and chairman of Cronus SP Sergei, known as SP. >>Yeah, joining that, that's fine. It's fine. >>So your inaugural event of the Global Cyber Summit What you're what you're feeling so far like it's >>very good to have exceeded the expectations. In terms of a dangerous with high quality audience. Everything is organized quite well. It's our first event of a kind. It's a first marks a transformation of the company from being data protection company to be decided protection company from the application company to be a platform. >>Talk about the vision and we're how you got here. Because again, the market's changing cloud computing, Internet of things, more threats than ever before data seems to be at the center of all this. >>Don't think about the team in terms of data, will look at 18 terms of foreclose, so workload could be day to put the application for the system. We also look at the team, not from the standpoint large passed him a small fast mark, but from the standpoint off and point, like your computer right here on the table or a mobile device from step with authority, which is a large that the center of a gentle price. Or it is a cloud like Amazon, like Google, like Microsoft. And from the standpoint of something in the middle, which we call EJ, and it's growing very rapidly, that's a small data center. That more door is that a small office that's also specialized vacations, like practically my hospital, like a railway station like restaurants. Like any retail location where you actually have specialized computers. Detective Lee servers running the infrastructure, for example. Every Starbucks location is actually 12 and those computers edge and then point. Need protection, need complete protection. And our mission is to provide a complete protection from the standpoint of safety, accessibility, privacy, authenticity of security that something which will go for any of us. >>You know, I think your divisions right on. In fact, when you think about data protection, my observation is it was because of disruption and operations. Somehow an event happened. Hurricane flood the operation of destructive. They gotta roll back and get the snapshots and bring it back. But security is now causing a disruption. I think you guys are honing in on with disruptions coming from a security vector way. Official mechanisms have to change a little bit. That seems a bit your success here with. >>I think we look at this holistically way, don't see really different, so safe its accessibility, privacy of authenticity and security. A love. This vectors are a problem, you know, perhaps authenticity. He's not yet visible as march, and privacy is new, So privacy is not the bad guys. You know, it's a good guys, guys. It's maybe yours. Employees. Maybe your partner. Or maybe maybe it's your customer. One. You don't want to see the information about somebody else and so alone. This is a threat, and you really don't want your infrastructure to be damage to your business to yourself. Unintentional damage. If you want to break something, you better break it, wasting your decision and you better be able to roll back so you know it comes from data protection, but it goes to security and privacy and authenticity. All of this together is important for defensive your idea. Infrastructure is functional and old times controlled by you. >>In your opinion, has ransomware provided a wake up call to I t around this area? Because that seems to be a theme. A lot with Ransomware. People realize that they're stuck highlights >>a problem somewhere is an interesting trend. I wouldn't really be happy about Ransomware around somewhere is a scene. So we help people to be protected against run somewhere. But that doesn't mean we like Ransomware. So yeah, >>extortion. Not really. Well, like, yeah, you're the one being extorted. >>Nice. But it's one of the wake up calls in reality again. It comes from all the directions. I think Ransomware is just very, very easy to understand. >>People can see and understand it. Explain You mentioned s a P A s. What does that explain that acronym? What does it mean? What's the vision behind >>Sabba says is safe Accessibility, privacy else intensity and security combined in a single product. That's what it means. It means that you know, don't lose in using everything is accessible at all times with the right people have access and you can control the access. Nothing is mortified in such ways that you don't know it was modified and no bad guys can break into your tea or into your date or NT applications >>you mentioned. The platform platforms are well known concept and computer science and certainly the Internet. You've seen great successes with platforms, enable something. How would you describe the enablement that comes from Cronus platform, Cyber platform. >>I think it comes back to what you start at the waist. There is a lot of new friends and part of this new Frances. The world for a while maybe 20 years ago looked like the world which is consolidating. And you can one vendor which provide solutions to watch majority of problems. Which was Michael, right? So you remember 1999. It looked like pretty much everybody is gonna use windows. Mark is not going to be there. Microsoft was making some inroads in Mobile was in C and so on and so forth. Well, now the water is consolidating. You have thousands of different types of workers. You have different systems. You have different applications. You have different cloud applications. You need to protect them in a very different way. That's another thing you need to integrate a lot about. You cannot do it all. So we opened our applications and our black from certain parties. Was event like this toe actually build on top of the platform to provide the functionality, which we don't >>You say that word system a few times, and I think this is interesting platform validation systems Thinking is like an operating system. It's a lot of consequences and systems The old system that seems that systems thinking is back in in the front lines of I t and technology because you got a cloud you got on premises, you got I ot way networks. It's a system, and so realistically thinking about it's interesting. Do you think people are getting their are you get the right thing to do? I think like a system >>wear simple people in a Cronus. We look at the world and we don't see anything but data by zeros and ones way don't look it everywhere, and I don't see anything but more clothes and these workers they could be in the cloud that could be on prayer. Music would be a partner location. It could be on your mobile device. It could be the whole device apart with. And we also see the world in terms of partners. And from our point of view, you know, it's it's was that people realize that, you know, people have idea needs to work on their partners to help him. So if I did, that work can do, innit? They cannot call their friends. They can communicate is a relative word possible head of the world. And so what we provide is a protection to make sure that it works a full time, no matter what is a possible challenge. >>That's me. Thank you for taking the time to answer some questions. I want to get one final question to you. News today Opening AP Eyes up Trading Developer network and a portal New New things. What's your message to the folks that want developing on your platform? What's the guiding principles with what's the simple value proposition of why I'm a developer? I wouldn't want to work on The Cronus is Global Platform >>so way might look relatively small. We're only 1.5000 people and we're only several $100 million. They were growing very rapidly. We have 6000 partners who can sell your products, and this number is going. Read it after you have 30,007 years. And so you have also a lot of data on the management. Five exabytes of data on the management and this amount of it is growing very rapidly. If you build applications for protection of this data, this number of workloads, this number off partners to sell it, you can sell your products successfully. Ultimately, for developers, it's It's about doing something which makes money and doing something which makes sense. And with our partner network, with our workload and they reach, they get to make sense and they get to make money. >>And it's a hot area. Cyber protection of a new Category Emerging out of the old data protection If you had to describe someone, the old waivers of the New way data protection the old way. Cyber Protection New Way. What's the difference between the two? >>Well, the difference is that includes security, privacy management, know sadistic management in one package. The difference is that it's designed to work in the world which is in parenting secure. It designed to work in the world where if you connect a network, you don't trust this network. And so if you have a cyber protection application cyber protection car where it has to be protected itself, that's >>thank you. Come on. Cue and taking the time out of your busy schedule to talk to us. Thank you. Very welcome. Appreciate it to give coverage here in Miami Beach across Global Cyber 7 2019 I'm John. Four year. Thanks for watching two days of coverage here. Be right back.

>>from San Francisco. It's the Q covering pager duty Summit 2019. Brought to you by pager Duty. >>Hey, welcome back there, Right, Jeffrey here with the cue, We're pager duty Psalm in its fourth year page summit Third year The Cube being here at West say, Fritz in downtown San Francisco and tying a pager duty summons up running the Western Frances. We're excited to be joined by our next two guests coming all way across the Pacific Ocean. My media left is Daniel Sultaana, group director for >>Sass for Technology. Want Daniel? Great to see you. Thank you. On his left camera. Network TV production engineer Lee also for technology one woke up. So first question. First time in the States. >>Not the first time. The state of into the states, Many tires. So it's a great comeback. California particular center. It is the >>first time for May, but it's been absolutely great. I got the whole weekend to explore San Francisco. Just one >>good give great. It's a great place thio around, but let's talk about Pedro December 1st time duty, Simon A lot. Actually, 1000 people company I P o. This year, a lot of buzz around here >>Really exciting. Great for pages. Video. I appreciate very similar company to technology wanted. Tim saws terms off genetic heritage. So there's a lot of affiliation between our two companies. >>All right, let's jump into what is technology. >>So technology wanted to Australia's largest enterprise software company. We produce software in a few vertical markets, focusing on higher education, local federal government, asset intensive and healthy. >>All right, so you guys are presenting later today on a really interesting topic referenced in the keynote. Your conversation is having increased customer experiences without burning out your people. I think the official report was unplanned work. The human impact been always on world. This is a really deal. People about the human impact duty, the pager. Peter's got a ring somewhere. You see a big impact in terms of the pressure on the teams to deliver with this kind of consumerism ation of I t expect. And that's >>exactly if you look at the enterprise well. Vanda pauses, expecting consumer response. You know, if your Netflix goes down your home tonight, you want that keeps immediately. It's the same pressure now that we're saying transferring today, it's complicated >>for me on on myself. So implementing these kind of systems that just helps an awful ones really understand and reduce the amount of time that we're spending on those incidents after Alice. >>Right? Because we talk a lot about unplanned downtime and maintenance for here, right on machines. And it's hugely impactful and a lot of conversations about prescriptive maintenance and kind of getting ahead of that. We don't hear that conversation so much about people you got humans about. The humans evolved, and I really interesting take as we go aboard. The complexity of the systems between the 80 eyes and everything's connected is no astronomically more complex. And it wasn't >>it definitely is way usedto have very simple traditional surfaces, but now it's hundreds of different services and applications that only talk together. Managing That's a very different game when it used to be >>right. So how does painting maybe help you? How did you start to build a I machine learning for it to be able to get a triage and more importantly, you know, assigned right tasked with the right people, >>I think first start off with us having many district systems bring that together, falling through. So it's like having many different nations around the world. Trying to talk, but not a common interface on bringing together was a first >>for us. What's next? They're still together, >>still pulling together now, actually understanding what we have turning that into processes that are more efficient, using the technology to move the various conversation alerts and information right ares triage ahead of time before problems actually happening. >>I think the other thing that we're more towards starting to use the diner a lot more to make more valuable got agreement, decisions, a supposed toe, intuition based decisions that we used to make >>right, replace something else that you already had kind of a supplement, >>not replace it. So So if I go back just to the technology wanted a street we're 30 years old started off before the Internet. So as we made this transition from on premises to a sax baseball way, needed tools help us in these multiple always on world. >>So So what? What are the characteristics of the biggest problems come up in terms of application interfaces or no way at all? These things tied together what seems to be the weakest link What is the one that you know most banks Now you can kind of reduced the settings. >>I don't think there's any one specific thing way. Talk about Cole's. An awful lot guards really great causes. It's very rarely ever one simple thing that's caused the problem. It's normally a multiple factors that come into play, and some of that can be. Has the engineer being cold three times. I've not came to what with two hours sleep, >>right? And you said you said you carry a pager and hopefully you don't have it All right Now >>it is on >>its way to switch number inside of me. Have you seen seen a reduction in kind of the pressure call in the qualities stuff that gets through triage and actually make it to the major >>way some stuff, way fix from bed. Now you stop to wake up >>way getting up. >>So we used a pager beauty my bollock way. Have some stuff that we built into that as well. And waken fix things from Ben >>give you exact way, have some issues that take us minutes to resolve. We've managed to bring that down to three >>wise that because better, better tasking of the people. Better identification problems were some things that drive exactly that. >>So it is bringing the multiple inputs into a central place that being interpreted and then being shifted off to the right resources to be able to fix it behind. Or there's no some automated, tacit kickoff. And that just condenses the whole into in process dramatically. So our customers seeing a much greater meantime between failure because we could get on the things a lot faster. >>Okay, so lessons for people thinking about paging me. What would you tell him? Some of your peers that are that are carrying the pager and red eyed way. >>Look, I think managing your PayPal is very important, I think way living in a world where talent is actually hard to secure. So you need to ensure that that talent is protected and looked after well nourished and grows on. So we've just page me to help do that, sure that teams don't burn out to understand what root causes also attack a rock, pools on become more efficient. >>Is there any specific characteristics are attributes in the people leaving? They're in their behavior, things that they do You're measuring as being now less burning? Absolutely >>way. Actually running employee in peace >>So they all just wrote a book. Five. So they get >>Andrea Lee. Something fundamental was around with number out of Dallas. That was That was really died. Other measure its foreign off. I wonder what a >>charity secrets. But when things were not good, orders of magnitude of work was done. Kind of unscheduled, which is causing this angst. How's that? Kind of? Just >>wear multiple hours every night. I'll be, quite frankly, people was on way. Knew that's how far. >>Right? Right, Right. >>Good. Well, thank you. Thank you for sharing the story. And good luck. Hopefully nobody else resigns and keep a couple a bunch of happy, happy clients opened out and deliver the great customer experience. Absolutely. Alright, >>stand the camera. Jeff, You're watching the cube? Were some it downtown