>> Narrator: From around the globe. It's theCUBE with digital coverage of VMworld 2020, brought to you by VMware and its ecosystem partners. >> Hello, welcome back to theCUBE's coverage of VMworld 2020. This is theCUBE virtual with VMworld 2020 virtual. I'm John Furrier your host of theCUBE with Dave Vellante. It's our 11th year covering VMware. We're not in person, we're virtual, but all the content is flowing. Of course, we're here with Pat Galsinger, the CEO of VMware. Who's been on theCUBE all 11 years. This year virtual of theCUBE as we've been covering VMware from his early days in 2010, when theCUBE started 11 years later, Pat is still changing and still exciting. Great to see you. Thanks for taking the time. >> Hey, you guys are great. I love the interactions that we have, the energy, the fun, the intellectual sparring. And of course that audiences have loved it now for 11 years. And I look forward to the next 11 that we'll be doing together. >> It's always exciting cause we'd love great conversations. Dave and I like to drill in and really kind of probe and unpack the content that you're delivering at the keynotes, but also throughout the entire program. It is virtual this year, which highlights a lot of the cloud native changes. Just want to get your thoughts on the virtual aspect of VMworld, not in person, which is one of the best events of the year. Everyone loves it. The great community. It's virtual this year, but there's a slew of content. What should people take away from this virtual VMworld? >> Well, one aspect of it is that I'm actually excited about is that we're going to be well over a hundred thousand people, which allows us to be bigger, right? You don't have the physical constraints. You also are able to reach places like I've gone to customers and maybe they had 20 people attend in prior years. This year they're having a hundred, they're able to have much larger teams. Also like some of the more regulated industries where they can't necessarily send people to events like this, the international audience. So just being able to spread the audience much more broadly well, also our key messages a digital foundation for unpredictable world. And man, what an unpredictable world it has been this past year? And then key messages, lots of key products announcements technology, announcements partnership, announcements and of course in all of the VMworld, is that hands on (murmurs) interactions that we'll be delivering our virtual, you come to the VMware because the content is so robust and it's being delivered by the world's smartest people. >> Yeah. We've had great conversations over the years. And we've talked about hybrid clothing 2012, a lot of this stuff I looked back in lot of the videos was early on, we're picking out all these waves, but it was that moment four years ago or so, maybe even four, three, I can't even remember, seems like yesterday. You gave the Seminole keynote and you said, "This is the way the world's going to happen." And since that keynote I'll never forget was in Moscone. And since then you guys have been performing extremely well both on the business as well as making technology bets and is paying off. So what's next? I mean, you've got the cloud scale. Is it space? Is it cyber? I mean, all these things are going on. What is next wave that you're watching and what's coming out and what can people extract out of VMworld this year about this next wave? >> Yeah, one of the things I really am excited about I went to my buddy Jensen. I said, "Boy, we're doing this work and smart. Next We really liked to work with you and maybe some things to better generalize the GPU." And Jensen challenged me. Now, usually, I'm the one challenging other people with bigger visions, this time Jensen said, "Hey Pat, I think you're thinking too small. Let's do the entire AI landscape together. And let's make AI a enterprise classwork stowed from the data center to the cloud and to the Edge. And so I'm going to bring all of my AI resources and make VMware, And Tansu the preferred infrastructure to deliver AI at scale. I need you guys to make the GPS work like first class citizens in the vSphere environment, because I need them to be truly democratized for the enterprise. so that it's not some specialized AI development team, it's everybody being able to do that. And then we're going to connect the whole network together in a new and profound way with our Monterey Program as well being able to use the SmartNIC, the DPU as Jensen likes to call it. So now it's CPU, GPU and DPU, all being managed through a distributed architecture of VMware." This is exciting. So this is one in particular that I think we are now rearchitecting the data center, the cloud in the Edge. And this partnership is really a central point of that. >> Yeah, the Nvid thing's huge. And I know Dave, Perharbs has some questions on that. But I ask you a question because a lot of people ask me, is it just a hardware deal? I mean, talking about SmartNIC, you talking about data processing units. It sounds like a motherboard in the cloud, if you will, but it's not just hardware. Can you talk about the aspect of the software piece? Because again, Nvidia is known for GP use, we all know that, but we're talking about AI here. So it's not just hardware. Can you just expand and share what the software aspect of all this is? >> Yeah. Well, Nvidia has been investing in their AI stack and it's one of those where I say, this is Edison at work, right? The harder I work, the luckier I get. And Nvidia was lucky that their architecture worked much better for the AI workload, but it was built on two decades of hard work in building a parallel data center architecture. And they have built a complete software stack for all of the major AI workloads running on their platform. All of that is now coming to vSphere and Tansu, that is a rich software layer across many vertical industries. And we'll talk about a variety of use cases. One of those that we highlight at Vmworld is the university of California, San Francisco partnership UCSF one of the world's leading research hospitals, some of the current vaccine use cases as well, the financial use cases for threat detection and trading benefits. It really is about how we bring that rich software stack. this is a decade and a half of work to the VMware platform so that now every developer and every enterprise could take advantage of this at scale, that's a lot of software. So in many respects, yeah, there's a piece of hardware in here, but the software stack is even more important. >> So well on the sort of Nvidia the arm piece, there's really interesting, these alternative processing models. And I wonder if you could comment on the implications for AI inferencing at the Edge. It's not just as well processor implications, it's storage, it's networking. It's really a whole new fundamental paradigm. How are you thinking about that Pat? >> Yeah, we've thought about, there's three aspects, but what we said three problems that we're solving. One is the developer problem, what we said, now you develop once, right? And the developer can now say, "Hey, I want to have this new AI centric app and I can develop, and it can run in the data center on the cloud or at the Edge." You'll secondly, my operations team can be able to operate this just like I do all my infrastructure. And now it's VMs containers and AI applications and third, and this is where your question really comes to bear. Most significantly is data gravity, right? These data sets are big. Some of them need to be very low latency as well. They also have regulatory issues. And if I have to move these large regulated data sets to the cloud, boy, maybe I can't do that generally for my apps or if I have low latency heavy apps at the Edge, ah, I can't pull it back to the cloud or to my data center. And that's where the uniform architecture and aspects of the Monterey program, where I'm able to take advantage of the network and the SmartNIC that are being built, but also being able to fully represent the data gravity issues of AI applications at scale 'cause in many cases I'll need to do the processing, both the learning and the inference at the Edge as well. So that's a key part of our strategy here with Nvidia. And I do think is going to be a lock, a new class of apps because when you think about AI and containers, what am I using it for? Well, it's the next generation of applications. A lot of those are going to be Edge 5G based. So very critical. >> We got to talk about security now, too. I mean, I'm going to pivot a little bit here John if it's okay. Years ago you said security is a do over. You said that on theCUBE, It stuck with us. There's there's been a lot of complacency it's kind of, if it didn't broke, don't fix it, but COVID kind of broke it. That's why you see three mega trends. You've got cloud security, you see in Z scaler rocket, you got identity access management and I'll check, I think a customer of yours. And then you've got endpoint you're seeing CrowdStrike explode. You guys pay 2.7 billion I think for carbon black yet CrowdStrike has this huge valuation. That's a mega opportunity for you guys. What are you seeing there? How are you bringing that all together? You've got NSX components, EUC components. You've got sort of security throughout your entire stack. How should we be thinking about that? >> Well, one of the announcements that I am most excited about at Vmworld is the release of carbon black workload, this research we're going to take those carbon black assets and we're going to combine it with workspace one. We're going to build it in NSX. We're going to make it part of Tansu and we're going to make it part of vSphere. And carbon black workload is literally the vSphere embodiment of carbon black in an agentless way. Ans so now you don't need to insert new agents or anything. It becomes part of the hypervisor itself, meaning that there's no attack surface available for the bad guys to pursue, but not only is this an exciting new product capability, but we're going to make it free, right? And what I'm announcing at VMworld and everybody who uses vSphere gets carbon black workload for free for an unlimited number of VMs for the next six months. And as I said in the keynote today is a bad day for cybercriminals. This is what intrinsic security is about, making it part of the platform. Don't add anything on, just click the button and start using what's built into vSphere. And we're doing that same thing with what we're doing at the networking layer. This is the act, the last line acquisition. We're going to bring that same workload kind of characteristic into the container. That's why we did the Octarine acquisition. And we're releasing the integration of workspace one with a carbon black client, and that's going to be the differentiator. And by the way, CrowdStrike is doing well, but guess what? So are we, and like both of us are eliminating the rotting dead carcasses of the traditional AV approach. So there is a huge market for both of us to go pursue here. So a lot of great things in security. And as you said, we're just starting to see that shift of the industry occur that I promised last year in theCUBE. >> So it'd be safe to say that you're a cloud native in a security company these days? >> You all, absolutely. And the bigger picture of us, is that we're critical infrastructure layer for the Edge for the cloud, for the telco environment and for the data center from every end point, every application, every cloud. >> So Padagonia asked you a virtual question, we got from the community, I'm going to throw it out to you because a lot of people look at Amazon, The cloud and they say, "Okay, we didn't see it coming. We saw it coming. We saw it scale all the benefits that are coming out of cloud, Well-documented." The question for you is what's next after cloud, as people start to rethink, especially with COVID highlighting all the scabs out there. As people look at their exposed infrastructure and their software, they want to be modern. They want the modern apps. What's next after cloud. What's your vision? >> Well, with respect to cloud, we are taking customers on the multicloud vision, right? Where you truly get to say, "Oh, this workload, I want to be able to run it with Azure, with Amazon. I need to bring this one on premise. I want to run that one hosted. I'm not sure where I'm going to run that application." So develop it and then run it at the best place. And that's what we mean by our hybrid multicloud strategy is being able for customers to really have cloud flexibility and choice. And even as our preferred relationship with Amazon is going super well. We're seeing a real uptick. We're also happy that the Microsoft Azure VMware services now GA so they're in marketplace, our Google, Oracle, IBM and Alibaba partnerships in the much broader set of VMware cloud Partner Program. So the future is multicloud. Furthermore, it's then how do we do that in the Telco Network for the 5G build out, The Telco cloud? And how do we do that for the Edge? And I think that might be sort of the granddaddy of all of these because increasingly in a 5G world will be a nibbling Edge use cases. We'll be pushing AI to the Edge like we talked about earlier in this conversation, will be enabling these high bandwidth, with low latency use cases at the Edge, and we'll see more and more of the smart embodiment, smart cities, smart street, smart factory, or the autonomous driving. All of those need these type of capabilities. >> So there's hybrid and there's multi, you just talked about multi. So hybrid are data partner ETR, they do quarterly surveys. We're seeing big uptick in VMware cloud and AWS, you guys mentioned that in your call. we're also seeing the VMware cloud, VMware cloud Coundation and the other elements, clearly a big uptake. So how should we think about hybrid? It looks like that's an extension of on-prem maybe not incremental, maybe a share shift whereas multi looks like it's incremental, but today multi has really running on multiple clouds, but vision toward incremental value. How are you thinking about that? >> Yeah, so clearly the idea of multi is to link multiple. Am I taking advantage of multiple clouds being my private clouds, my hosted clouds. And of course my public cloud partners, we believe everybody will be running a great private cloud, picking a primary, a public cloud, and then a secondary public cloud. Hybrid then is saying, which of those infrastructures are identical so that I can run them without modifying any aspect of my infrastructure operations or applications. And in today's world where people are wanting to accelerate their move to the cloud, a hybrid cloud is spot on with their needs because if I have to refactor my applications it's a couple million dollars per app, And I'll see you in a couple of years. If I can simply migrate my existing application to the hybrid cloud, what we're consistently seeing is the time is one quarter and the cost is one eight, four less. Those are powerful numbers. And if I need to exit a data center, I want to be able to move to a cloud environment, to be able to access more of those native cloud services. Wow. That's powerful. And that's why for seven years now we've been preaching that hybrid is the future. It is not a waystation to the future. And I believe that more fervently today than when I declared it seven years ago. So we are firmly on that path that we're enabling a multi and a hybrid cloud future for all of our customers. >> Yeah. You addressed that like CUBE 2013. I remember that interview vividly was not a waystation. I got (murmurs) the answer. Thank you Pat, for clarifying than going back seven years. I love the vision. You're always got the right wave. It's always great to talk to you, but I got to ask you about these initiatives you seeing clearly last year or a year and a half ago, project Pacific name out almost like a guiding directional vision, and then put some meat on the bone Tansu and now you guys have that whole Cloud Native Initiative is starting to flower up thousand flowers are blooming. This year Project Monterrey has announced same kind of situation. You're showing out the vision. What are the plans to take that to the next level and take a minute to explain how project Monterey, what it means and how you see that filling out. I'm assuming it's going to take the same trajectory as Pacific. >> Yeah. Monetary is a big deal. This is rearchitecting The core of vSphere. It really is ripping apart the IO stack from the intrinsic operation of a vSphere and ESX itself, because in many ways, the IO we've been always leveraging the NIC and essentially virtual NICs, but we never leverage the resources of the network adapters themselves in any fundamental way. And as you think about SmartNICs, these are powerful resources now where they may have four, eight, 16, even 32 cores running in the smartNIC itself. So how do I utilize that resource? But it also sits in the right place in the sense that it is the network traffic cop. It is the place to do security acceleration. It is the place that enables IO bandwidth optimization across increasingly rich applications where the workloads, the data, the latency get more important both in the data center and across data centers to the cloud and to the Edge. So this rearchitecting is a big deal. We announced the three partners, Intel, Nvidia, Mellanox, and Penn Sandow that we're working with. And we'll begin the deliveries of this as part of the core vSphere offerings of beginning next year. So it's a big rearchitecting. These are our key partners. We're excited about the work that we're doing with them. And then of course our system partners like Dell and Lenovo, who've already come forward and says, "Yeah, we're going to be bringing these to market together with VMware." >> Pat, personal question for you. I want to get your personal take, your career, going back to Intel. You've seen it all, but the shift is consumer to enterprise. And you look at just recently snowflake IPO, the biggest ever in the history of wall street, an enterprise data's company. And the enterprise is now relevant. Enterprise feels consumer. We talked about consumerization of IT years and years ago, but now more than ever the hottest financial IPO enterprise, you guys are enterprise. You did enterprise at Intel. (laughs) You know the enterprise, you doing it here at VMware. The enterprise is the consumer now with cloud and all this new landscape. What is your view on this? Because you've seen the waves, and you've seen the historical perspective. It was consumer, was the big thing. Now it's enterprise, what's your take on all this? How do you make sense of it? Because it's now mainstream. what's your view on this? >> Well, first I do want to say congratulations to my friend Frank, and the extraordinary snowflake IPO, and by the way, they use VMware. So not only do I feel a sense of ownership 'cause Frank used to work for me for a period of time, but they're also a customer of ours. So go Frank, go snowflake. We're we're excited about that. But there is this episodic, this to the industry where for a period of time it is consumer-driven and CES used to be the hottest ticket in the industry for technology trends. But as you say, it is now shifted to be more business centric. And I've said this very firmly, for instance, in the case of 5G where I do not see consumer a faster video or a better Facebook, isn't going to be why I buy 5G. It's going to be driven by more business use cases where the latency, the security and the bandwidth will have radically differentiated views of the new applications that will be the case. So we do think that we're in a period of time and I expect that it's probably at least the next five years where business will be the technology drivers in the industry. And then probably, hey, there'll be a wave of consumer innovation and I'll have to get my black turtlenecks out again and start trying to be cool, but I've always been more of an enterprise guy. So I like the next five to 10 years better. I'm not cool enough to be a consumer guy. And maybe my age is now starting to conspire against me as well. >> Hey, Pat, I know you've got to go, but quick question. So you guys, you gave guidance, pretty good guidance, actually. I wondered have you and Zane come up with a new algorithm to deal with all this uncertainty or is it kind of back to old school gut feel? (laughs) >> Well, I think as we thought about the year as we came into the year and obviously, COVID smacked everybody, we laid out a model, we looked at various industry analysts, what we call the swoosh model, right? Q2, Q3 and Q4 recovery, Q1 more so, Q2 more so, and basically, we build our own theories behind that. We test it against many analysts, the perspectives, and we had vs and we had Ws and we had Ls and so on. We picked what we thought was really sort of grounded of the best data that we could put our own analysis, which we have substantial data of our own customer's usage, et cetera, and pick the model. And like any model, you put a touch of conservatism against it, and we've been pretty accurate. And I think there's a lot of things, we've been able to sort of, with good data good thoughtfulness, take a view and then just consistently manage against it and everything that we said when we did that back in March, sort of proven out incrementally to be more accurate. And some are saying, "Hey, things are coming back more quickly." And then, oh we're starting to see the fall numbers climb up a little bit. Hey, we don't think this goes away quickly. There's still a lot of secondary things to get flushed through the various economies, as stimulus starts tailoring off small businesses are more impacted and we still don't have a widely deployed vaccine. And I don't expect we will have one until second half of next year. Now there's the silver lining to that, as we said, which means that these changes, these faster to the future shifts in how we learn, how we work, how we educate, how we care for, how we worship, how we live, they will get more and more sedimented into the new normal relying more and more on the digital foundation. And we think ultimately that has extremely good upsides for us longterm, even as it's very difficult to navigate in the near term. And that's why we are just raving optimists for the longterm benefits of a more and more digital foundation for the future of every industry, every human, every workforce, every hospital, every educator, they are going to become more digital. And that's why I think going back to the last question, this is a business driven cycle, we're well positioned, and we're thrilled for all of those who are participating with VMworld 2020. This is a seminal moment for us and our industry. >> Pat, thank you so much for taking the time. It's an enabling model. It's what platforms are all about. You get that. My final parting question for you is whether you're a VC investing in startups or a large enterprise who's trying to get through COVID with a growth plan for that future. What is a modern app look like? And what does a modern company look like in your view? >> Well, a modern company would be that instead of having a lot of people looking down at infrastructure, the bulk of my IT resources are looking up at building apps. Those apps are using modern CICD data pipeline approaches built for a multicloud embodiment, right? And of course, VMware is the best partner that you possibly could have. So if you want to be modern, cool on the front end, come and talk to us. >> All right. Pat Galsinger the CEO of VMware here on theCUBE for VML 2020 virtual here with theCUBE virtual. Great to see you virtually Pat. Thanks for coming on. Thanks for your time. >> Hey, thank you so much. Love to see you in person soon enough, but this is pretty good. Thank you, Dave. Thank you so much. >> Okay. You're watching theCUBE virtual here for VMworld 2020. I'm John Furrier with Dave Vallente with Pat Gelsinger. Thanks for watching. (upbeat music)

>>From the cube studios in Palo Alto, in Boston, connecting with thought leaders all around the world. This is a cute conversation. Hi, welcome back. I'm Stu middleman. And this is a cube conversation digging in with, talking about what they're doing to help people. Yeah. Really bringing some of the networking ideals to cloud native environment, both know in the cloud, in the data centers program, Krishna penny. He is the vice president of software. Thanks so much for joining us. Thank you so much for talking to me. Alright, so, so Krishna the pin Sandow team, uh, you know, very well known in the industry three, uh, you innovation. Yeah. Especially in the networking world. Give us a little bit about your background specifically, uh, how long you've been part of this team and, uh, you know, but, uh, you know, you and the team, you know? Yeah. >>And Sando. Yup. Um, so, uh, I'm VP of software in Sandow, um, before Penn Sarno, before founding concern, though, I worked in a few startups in CME networks, uh, newer systems and Greenfield networks, all those three startups have been acquired by Cisco. Um, um, my recent role before this, uh, uh, this, this company was a, it was VP of engineering and Cisco, uh, I was responsible for a product called ACA, which is course flagship SDN tonic. Mmm. So I mean, when, why did we find a phone, uh, Ben Sandoz? So when we were looking at the industry, uh, the last, uh, a few years, right? The few trends that are becoming clear. So obviously we have a lot of enterprise background. We were watching, you know, ECA being deployed in the enterprise data centers. One sore point for customers from operational point of view was installing service devices, network appliances, or storage appliances. >>So not only the operational complexity that this device is bringing, it's also, they don't give you the performance and bandwidth, uh, and PPS that you expect, but traffic, especially from East West. So that was one that was one major issue. And also, if you look at where the intelligence is going, has been, this has been the trend it's been going to the edge. The reason for that is the motors or switches or the devices in the middle. They cannot handle the scale. Yeah. I mean, the bandwidths are growing. The scale is growing. The stateful stuff is going in the network and the switches and the appliances not able to handle it. So you need something at the edge close to the application that can handle, uh, uh, this kind of, uh, services and bandwidth. And the third thing is obviously, you know, x86, okay. Even a few years back, you know, every two years, you know, you're getting more transistors. >>I mean, obviously the most lined it. And, uh, we know we know how that, that part is going. So the it's cycles are more valuable and we don't want to use them for this network services Mmm. Including SDN or firewalls or load balancer. So NBME, mutualization so looking at all these trends in the industry, you know, we thought there is a good, uh, good opportunity to do a domain specific processor for IO and build products around it. I mean, that's how we started Ben signed off. Yeah. So, so Krishna, it's always fascinating to watch. If you look at startups, they are often yeah. Okay. The time that they're in and the technologies that are available, you know, sometimes their ideas that, you know, cakes a few times and, you know, maturation of the technology and other times, you know, I'll hear teams and they're like, Oh, well we did this. >>And then, Oh, wow. There was this new innovation came out that I wish I had add that when I did this last time. So we do, a generation. Oh, wow. Talking about, you know, distributed architectures or, you know, well, over a decade spent a long time now, uh, in many ways I feel edge computing is just, you know, the latest discussion of this, but when it comes to, and you know, you've got software, uh, under, under your purview, um, what are some of the things that are available for that might not have been, you know, in your toolkit, you know, five years ago. Yeah. So the growth of open source software has been very helpful for us because we baked scale-out microservices. This controller, like the last time I don't, when we were building that, you know, we had to build our own consensus algorithm. >>We had to build our own dishwasher database for metrics and humans and logs. So right now, uh, we, I mean, we have, because of open source thing, we leverage CD elastic influx in all this open source technologies that you hear, uh, uh, since we want to leverage the Kubernetes ecosystem. No, that helped us a lot at the same time, if you think about it. Right. But even the software, which is not open source, close source thing, I'm maturing. Um, I mean, if you talk about SDN, you know, seven APS bank, it was like, you know, the end versions of doing off SDN, but now the industry standard is an ADPN, um, which is one of the core pieces of what we do we do as Dean solution with DVA. Um, so, you know, it's more of, you know, the industry's coming to a place where, you know, these are the standards and this is open source software that you could leverage and quickly innovate compared to building all of this from scratch, which will be a big effort for us stocked up, uh, to succeed and build it in time for your customer success. >>Yeah. And Krishna, I, you know, you talk about open forum, not only in the software, the hardware standards. Okay. Think about things, the open compute or the proliferation of, you know, GPS and, uh, everything along that, how was that impact? I did. So, I mean, it's a good thing you're talking about. For example, we were, we are looking in the future and OCP card, but I do know it's a good thing that SEP card goes into a HP server. It goes into a Dell software. Um, so pretty much, you know, we, we want to, I mean, see our goal is to enable this platform, uh, that what we built in, you know, all the use cases that customer could think of. Right. So in that way, hardware, standardization is a good thing for the industry. Um, and then same thing, if you go in how we program the AC, you know, we at about standards of this people, programming, it's an industry consortium led by a few people. >>Um, we want to make sure that, you know, we follow the standards for the customer who's coming in, uh, who wants to program it., it's good to have a standards based thing rather than doing something completely proprietary at the same time you're enabling innovations. And then those innovations here to push it back to the open source. That's what we trying to do with before. Yeah. Excellent. I've had some, some real good conversations about before. Um, and, and the way, uh, and Tondo is, is leveraging that, that may be a little bit differently. You know, you talk about standards and open source, oftentimes it's like, well, is there a differentiator there, there are certain parts of the ecosystem that you say, well, kind of been commodified. Mmm. Obviously you're taking a lot of different technologies, putting them together, uh, help, help share the uniqueness. Okay. And Tondo what differentiates, what you're doing from what was available in the market or that I couldn't just cobbled together, uh, you know, a bunch of open source hardware and software together. >>Yeah. I mean, if you look at a technologist, I think the networking that both of us are very familiar with that. If you want to build an SDN solution, or you can take a, well yes. Or you can use exhibit six and, you know, take some much in Silicon and cobble it together. But the problem is you will not get the performance and bandwidth that you're looking for. Okay. So let's say, you know, uh, if you want a high PPS solution or you want a high CPS solution, because the number of connections are going for your IOT use case or Fiji use case, right. If you, uh, to get that with an open source thing, without any assist, uh, from a domain specific processor, your performance will be low. So that is the, I mean, that's once an enterprise in the cloud use case state, as you know, you're trying to pack as many BMCs containers in one set of word, because, you know, you get charged. >>I mean, the customer, uh, the other customers make money based on that. Right? So you want to offload all of those things into a domain specific processor that what we've built, which we call the TSC, which will, um, which we'll, you know, do all the services at pretty much no cost to accept a six. I mean, it's to six, you'll be using zero cycles, a photo doing, you know, features like security groups or VPCs, or VPN, uh, or encryption or storage virtualization. Right. That's where that value comes in. I mean, if you count the TCO model using bunch of x86 codes or in a bunch of arm or AMD codes compared to what we do. Mmm. A TCO model works out great for our customers. I mean, that's why, you know, there's so much interest in a product. Excellent. I'm proud of you. Glad you brought up customers, Christina. >>One of the challenges I have seen over the years with networking is it tends to be, you know, a completely separate language that we speak there, you know, a lot of acronyms and protocols and, uh, you know, not necessarily passable to people outside of the silo of networking. I think back then, you know, SDN, uh, you know, people on the outside would be like, that stands for still does nothing, right? Like networking, uh, you know, mumbo jumbo there for people outside of networking. You know what I think about, you know, if I was going to the C suite of an enterprise customer, um, they don't necessarily care about those networking protocols. They care about the, you know, the business results and the product Liberty. How, how do you help explain what pen Sandow does to those that aren't, you know, steeped in the network, because the way I look at it, right? >>What is customer looking? But yeah, you're writing who doesn't need, what in cap you use customer is looking for is operational simplicity. And then he wants looking for security. They, it, you know, and if you look at it sometimes, you know, both like in orthogonal, if you make it very highly secure, but you make it like and does an operational procedure before you deploy a workload that doesn't work for the customer because in operational complexity increases tremendously. Right? So it, we are coming in, um, is that we want to simplify this for the customer. You know, this is a very simple way to deploy policies. There's a simple way to deploy your networking infrastructure. And in the way we do it is we don't care what your physical network is, uh, in some sense, right? So because we are close to the server, that's a very good advantage. >>We have, we have played the policies before, even the packet leaves the center, right? So in that way, he knows his fully secure environment and we, and you don't want to manage each one individually, we have this, okay, Rockwell PSM, which manages, you know, all this service from a central place. And it's easy to operationalize a fabric, whether you talk about upgrades or you talk about, you know, uh, deploying new services, it's all driven with rest API, and you can have a GUI, so you can do it a single place. And that's where, you know, a customer's value is rather than talking about, as you're talking about end caps or, you know, exactly the route to port. That is not the main thing that, I mean, they wake up every day, they wake up. Have you been thinking about it or do I have a security risk? >>And then how easy for me is to deploy new, uh, in a new services or bring up new data center. Right. Okay. Krishna, you're also spanning with your product, a few different worlds out. Yeah. You know, traditionally yeah. About, you know, an enterprise data center versus a hyperscale public cloud and ed sites, hi comes to mind very different skillset for management, you know, different types of okay. Appointments there. Mmm. You know, I understand right. You were going to, you know, play in all of those environments. So talk a little bit about that, please. How you do that and, you know, you know, where you sit in, in that overall discussion. Yes. So, I mean, a number one rule inside a company is we are driven by customers and obviously not customer success is our success. So, but given said that, right. What we try to do is that we try to build a platform that is kind of, you know, programmable obviously starting from, you know, before that we talked about earlier, but it's also from a software point of view, it's kind of plugable right. >>So when we build a software, for example, at cloud customers, and they use BSC, they use the same set of age KPI's or GSP CRS, TPS that DSC provides their controller. But when we ship the same, uh, platform, what enterprise customers, we built our own controller and we use the same DC APS. So the way we are trying to do is things is fully leverage yeah. In what we do for enterprise customers and cloud customers. Mmm. We don't try to reinvent the wheel. Uh, obviously at the same time, if you look at the highest level constructs from a network perspective, right. Uh, audience, for his perspective, what are you trying to do? You're trying to provide connectivity, but you're trying to avoid isolation and you're trying to provide security. Uh, so all these constructs we encapsulated in APA is a, which, you know, uh, in some, I, some, some mostly like cloud, like APS and those APIs are, are used, but cloud customers and enterprise customers, and the software is built in a way of it. >>Any layer is, can be removed on any layer. It can be hard, right? Because it's not interested. We don't want to be multiple different offers for different customers. Right. Then we will not scale. So the idea when we started the software architecture, is that how we make it pluggable and how will you make the program will that customer says, I don't want this piece of it. You can put them third party piece on it and still integrate, uh, at a, at a common layer with using. Yeah. Yeah. Well, you know, Krishna, you know, I have a little bit of appreciation where some of the hard work, what your team has been doing, you know, a couple of years in stealth, but, you know, really accelerating from, uh, you know, the announcement coming out of stealth, uh, at the end of 2019. Yeah. Just about half a year, your GA with a major OEM of HPE, definitely a lot of work that needs to be done. >>It brings us to, you know, what, what are you most proud about from the work that your team's doing? Uh, you know, we don't need to hear any, you know, major horror stories, but, you know, there always are some of them, you know, not holes or challenges that, uh, you know, often get hidden yeah. Behind the curtain. Okay. I mean, personally, I'm most proud of the team that we've made. Um, so, uh, you know, obviously, you know, uh, our executors have it good track record of disrupting the market multiple times, but I'm most proud of the team because the team is not just worried about that., uh, that, uh, even delegate is senior technologist and they're great leaders, but they're also worried about the customer problem, right? So it's always about, you know, getting the right mix, awfully not execution combined with technology is when you succeed, that is what I'm most proud of. >>You know, we have a team with, and Cletus running all these projects independently, um, and then releasing almost we have at least every week, if you look at all our customers, right. And then, you know, being a small company doing that is a, Hmm, it's pretty challenging in a way. But we did, we came up with methodologists where we fully believe in automation, everything is automated. And whenever we release software, we run through the full set of automation. So then we are confident that customer is getting good quality code. Uh, it's not like, you know, we cooked up something and that they should be ready and they need to upgrade to the software. That's I think that's the key part. If you want to succeed in this day and age, uh, developing the features at the velocity that you would want to develop and still support all these customers at the same time. >>Okay. Well, congratulations on that, Christian. All right. Final question. I have for you give us a little bit of guidance going forward, you know, often when we see a company out and we, you know, to try to say, Oh, well, this is what company does. You've got a very flexible architecture, lot of different types of solutions, what kind of markets or services might we be looking at a firm, uh, you know, download down the road a little ways. So I think we have a long journey. So we have a platform right now. We already, uh, I mean, we have a very baby, we are shipping. Mmm Mmm. The platforms are really shipping in a storage provider. Uh, we are integrating with the premier clouds, public clouds and, you know, enterprise market, you know, we already deployed a distributed firewall. Some of the customers divert is weird firewall. >>So, you know, uh, so if you take this platform, it can be extendable to add in all the services that you see in data centers on clubs, right. But primarily we are driven from a customer perspective and customer priority point of view. Mmm. So BMW will go is even try to add more ed services. We'll try to add more storage features. Mmm. And then we, we are also this initial interest in service provider market. What we can do for Fiji and IOT, uh, because we have the flexible platform. We have the, see, you know, how to apply this platform, this new application, that's where it probably will go into church. All right. Well, Krishna not a penny vice president of software with Ben Tondo. Thank you so much for joining us. Thank you, sir. It was great talking to you. All right. Be sure to check out the cube.net. You can find lots of interviews from Penn Sundo I'm Stu Miniman and thank you. We're watching the cute.

>>From New York city. It's the cube covering. Welcome to the new edge brought to you by systems. >>Okay, we'll come back. You're ready. Jeff Frick here with the cube. We're in downtown Manhattan at the top of Goldman Sachs, like 43 stories above the Hudson. It was a really beautiful view a couple hours ago, but the cloud has moved in and that's only appropriate cause it's cloud is a big theme of why we're here today. We're here for the Penn Zando event. It's called welcome to the new edge. They just come out of stealth mode after two and a half years, almost three years, raised a ton of money, got a really rockstar team and we're excited to have the CEO with us today to tell us a little bit about more what's going on. And that's prem Jane and again, the CEO of Penn Sandow prem. Great to see you. Nice to see you too. So everything we did running up to this event before we could get any of the news, we, we, we tried to figure out what was going on and all it kept coming up was NPLS, NPLS, NPLS, which I thought was a technology, which it is, but it's really about the team. Tell us a little bit about the team in which you guys have built prior and, and why you're such a, a well functioning and kind of forward thinking group of people. >>So I think the team is working together. Mario Luca, myself and Sony were working together since 1983 except for Sony. Sony joined us after the first company, which has crescendo, got acquired by Cisco in 1993 and since then four of us are working together. Uh, we have done many, uh, spinnings inside the Cisco and demo was the first one. Then we did, uh, uh, Nova systems, which was the second, then we did recently in CMA. Uh, and then after we left we thought we are going to retire, but we talked about it and we says, you know, there is still transitions happening in the industry and maybe we have few more years to go back to the, you know, industry and, and do something which is very challenging and, and uh, impacting. I think everything which we have done in the past is to create a impact in the industry and make that transition which is occurring very successful, >>which is really hard to do. And, and John Chambers who, who's on the board and spoke earlier today, you know, kind of talked about these 10 year cycles of significant change in our industry and you know, Clayton Christianson innovator's dilemma, it's really easy when you are successful at one of those to kind of sit on your laurels. In fact, it's really, really hard to kill yourself and go on to the next thing you guys have done this time and time and time again. Is there a unique chemistry in the way you guys look forward or you just, you just get bored with what you built and you want to build something new. I mean, what is some of the magic, because even John said, as soon as he heard that you were the team behind it, he was like, sign me up. I don't know what they're building but I don't really care cause I know these people can deliver. >>I think it's very good the, whenever you look at any startup, the most important thing which comes up as the team and you're seeing a lot of startup fails because the team didn't work together or they got their egos into this one. Since we are working for so long, they compliment each other. That's the one thing which is very important. Mario, Luca, myself, they come from engineering backgrounds. Sony comes from marketing, sales, uh, type of background and we all lady in terms of the brain, if you think about is the Mario behind the scene, Luca is really the execution machine and I'm, you can think like as a heart, okay. Putting this thing together. Uh, as a team, we work very complimentary with each other. It does not mean that we agree on everything, right? We disagree. We argue. We basically challenge each other. But one thing good about this particular team is that once we come to a conclusion, we just focus and execute. And team is also known to work with customers all the time. I mean, even when we started Penn Sando, we talked to many customers in the very beginning. They shape up our ideas, they shape up the directions, which is we are going and what transitions are occurring in the industries and all that. That's another thing which is we take customer very seriously in our thought process of building a product. >>So when you were thinking around sitting around the table, deciding whether you guys wanted to do it again, what were the challenges that you saw? What was the kind of the feedback loop that came in that, that started this? The, uh, the gym of the idea >>thing is also is that, uh, we had, we had developed so many different products as you saw today in the launch, eight or nine, uh, billion dollar product line and stuff like that. So we all have a very good system experience what is really needed, what transitions are occurring and stuff like that. When we started this one, we were not really sure what we wanted to do it, but in the last one when we did the, uh, NCMA, we realize that the enterprise thing, which we deliver the ACI solution for the enterprise, the realize that these services was the most complex way of incorporating into that particular architectures. So right from the beginning of interview realized that the, this particular thing is nobody has touched it, nobody thought about it out of the box thinking that how can you make it into a distributed fashion, which has also realized that cloud is going, everything distributed. >>They got away from the centralized appliances. So as the enterprise is now thinking of doing it cloud-like architectures and stuff like that. And the third thing which was really triggered us also, there was a company which is a new Poona which got acquired by Amazon in 2016 and we were looking at it what kinds of things they are doing and we said we can do much better architecturally and next generation, uh, architecture, which can really enable all the other cloud vendors. Some of them are our partners to make sure they can leverage that particular technologies and build the next generation cloud. And that's where this idea of new edge came in because we also saw that the new applications like IOT is five G's and artificial intelligence, machine learning, robotics or drones, you just name it intelligent devices, which is going to get connected. What is the best place to process them is at the edge or also at the backend with the application where the server is running these and that is another edge compute edge, right? >>In that particular sense. So our idea was to develop a product so that it can cover wide segment of the market, enterprise cloud providers, service borders, but focus very narrowly delivering these services into existing architectures. Also people who are building, building the next generation architectures. Right, so it's the distributed services platform or the distributed services architecture. So at its core for people that didn't make it today, what is it? It's basically is a distributed service platforms. The foundation of that is really our custom processor, which is we have designed is highly programmable. It's software defined so that all the protocols, which is typically people hardwired in our case is programmable. It's all programs which is we are writing the language which you selected as before and before extensions. The software stack is the major differentiated thing which is running on the top of this particular processor, which is we have designed in such a way that is hardware agnostics. >>The the, the capabilities which we have built is easily integrated into the existing environment. So if people already have cloud and they want to leverage our technologies, they can really deploy it in the enterprise. We are basically replacing lot of appliances, simplifying the architectures, making sure they can enable the service as they grow model, which is really amazing because right now they had to say firewall goes here, load balancer goes here, these a VPN devices goes there. In our case it's very simple. You put in every server of our technologies and our software stack and our Venice, which is our policy manager, which is sitting outside and it's based upon Kubernete X a architectures is basically a microservices, which is we are running and managing the life cycle of this particular product family and also providing the visibility and uh, uh, accountability in terms of exactly what is going on in that particular network. >>And it's all driven by intent-based architecture, which is policy driven, right? So software defined sitting on software defined Silicon. So you get the benefits of the Silicon, but it's also programmable Silicon, but it's still, you're sitting, you've got a software stack on top of that that manages that cloud and then the form factors as small as a Nick. Yes. So he can stick it in the HP HP server. Yeah. It specifically goes into any PCI slot in any server, uh, in the industry. Yes. It's amazing. Well, first incarnation, but, but, but, but, but that's a really simple implementation, right? Just to get radiation and easy to deploy. Right. And you guys are, you're yourself where involved in security that's involved in managing the storage. It's simple low power, which I thought was a pretty interesting attribute that you defined early on. Clearly thinking about edge and these distributed, uh, things all over the place. >>They're metal programmable. And then the other thing that was talked about a lot today was the observability. Yes. Um, why observability why was that so important? What were you hearing from customers that were really leading you down that path? Yeah, it's important. Uh, you know, surprisingly enough, uh, the visibility is one of the biggest challenge. Most of the data center faces today. A lot of people tried to do multiple different things, but they're never able to do it, uh, in, in the way we are doing it. One is that we don't run anything on the host. Some people have done it right on the train running the agent on the host. Some people have tried to run virtual machines on the those particular environment. In our case there's nothing which is running on the host site. It runs on our card and having end to end that visibility we can provide latency, very accurate latency to the, to the applications which is very important for these customers. >>Also, what is really going on there is the problem in the network. Isolation is another big thing. When something get lost they don't know where it got lost. We can provide that thing. Another important thing that you're doing, which is not being done in the industries. Everything which is we are doing is flow based means if I'm talking to you, there is a flow being set up between you and me and we are monitoring every flow and one of the advantages of our processor is we have four to eight gigabytes of memory, so we can keep these States, have these flows inside, and that gives a tremendous advantage for us to do lots of things, which as you can imagine going forward, we will be delivering it such as, for example, behavior of these flows and things from this point of view, once you understand the behavior of the flow, you can also provide lot of security features because if I'm not talking to you and suddenly I start talking to you and I know that there's something went wrong, right, right. >>And they should be able to look at the behavior analysis and should be able to tell exactly what's going on. You mean we want a real time snapshot of what's really happening instead of a instead of a sample of something that happened a little. No, absolutely. You're absolutely connected. Yeah. Yeah. Um, that's terrific. So you put together to accompany and you immediately went out and talked to a whole bunch of customers. I was amazed at the number of customers and partners that you had here at the launch. Um, was that for validation? Were you testing hypotheses or, or were there some things that the customers were telling you about that maybe you weren't aware of or maybe didn't get the right priority? I think it's all of the above. What you mentioned our, it's in our DNA by the way. You know, we don't design products, we don't design things without talking to customers. >>Validation is very important that we are on the right track because you may try to solve the customer problem, which is not today's problem. Maybe future's problem. Our idea was that then you can develop the product it was set on the shelf. We don't want to do that. We wanted to make sure that, that this is the hard problem customer is facing today. At the same time looking at it, what futuristic in their architecture is understanding the customers, how, what are they doing today, how they're deploying it. The use cases are understanding those very well and making sure that we are designing. Because when we design a seeker, when your designer processor, you know, you cannot design for one year, it has to be a longterm, right? And you need to make sure that we understand the current problems, we understand the future problems and design that in pretty much your spark and you've been in this space forever. >>You're at Cisco before. And so just love to get your take on exponential growth. You know, such an interesting concept that people have a really hard time grasping exponential growth and we're seeing it clearly with data and data flows and ultimately everything's got to go through the network. I mean, when you, when you think back with a little bit of perspective at the incredible increase in the data flow and the amount of data is being stored and the distribution of these, um, applications now out to the edge and store and compute and take action at the edge, you know, what do you think about, how do you, how do you kind of stay on top of that as somebody who kind of sees the feature relatively effectively, how do you try to stay on top of exponential curves? As you know, very valuable data is very important for anybody in any business. >>Whether it's financial, whether it's healthcare, whether it's, and it's becoming even more and more important because of machine learning, artificial intelligence, which is coming in to really process this particular data and predict certain things which is going to happen, right? We wanted to be close to the data and the closest place to be data is where the application is running. That's one place clears closest to the data at the edge is where data is coming in from the IOT devices, from the 5g devices, from the, you know, you know all kinds of appliances which is being classified under IOT devices. We wanted to be, make sure that we are close to the data, doesn't matter where you deploy and we want to be agnostic. Actually our technologies and architectures designed that this boundary is between North, South, East, West is going to go away in future cloud. >>A lot of things which is being done in the backend will be become at the edge like we talked about before. So we are really a journey which is just starting in this particular detectors and you're going to see a lot more innovations coming from us continuously in this particular directions. And again, based upon the feedback which you're going to get from cloud customers with enterprise customers, but they were partners and other system ecosystem partners, which is going to give us a lot of feedback. Great. Well again, thanks for uh, for having us out and congratulations to uh, to you and the team. It must be really fun to pull the covers off. absolutely. It is very historical day for us. This is something we were waiting for two years and nine months to see this particular date, to have our customers come on the stage and talk about our technologies and why they think it's very important. Thank you very much for giving me this opportunity to talk to you. Thank you. Alright, thanks prem. Thanks. He's prem. I'm Jeff. You're watching the cube where it depends. Sandow launch at the top of Goldman Sachs in downtown Manhattan. Thanks for watching. We'll see you next time.

>>From New York city. It's the cube covering. Welcome to the new edge brought to you by systems. >>Hey, welcome back everybody. Jeff, Rick here with the cube. We are in Manhattan at the top of Goldman Sachs. It is a great view if you ever get an opportunity to come up here, I think 43 floors over the Hudson you could see forever. But this is the cloud events. So the clouds are here and we're excited to be here is the Penn Penn Sandow launch in the name of the event is welcome to the new edge, which is a pretty interesting play. We hear a lot about edge but we haven't really heard of that company really focusing on the edge as their primary go to market activity and really thinking about the edge first. So we're excited to have the cofounder cube Olam and many time guests a Sony Gian Deni. She's the co founder and chief business officer. So many great to see you. Good to see you too. >>And our hosts here at Goldman Sachs is uh, Josh Matthews. He's a managing director of technology at Goldman. Josh. Great to see you. You too. And thank you and thanks for hosting us. Nice. A nice place to come to work every day. So great conversation today. Congratulations on the launch of the company over two years in stealth mode. Talk a little bit about that. What is it like to be in stealth mode for so long and you guys raised big money, you've got a big team, you're doing heavy duty technology. What's it been like to finally open up the curtains and tell everybody what you've been? >>It's clearly very interesting and exciting. Normally it's taken me nine months to deliver a baby this time it's been two and a half years of being instilled while we have been getting ready for this baby to come out. So it's phenomenally exciting that too to be sharing the stage with our customers and our investors and our strategic partners. >>Yeah, I thought it was pretty interesting that you're launching with customers and when you really told the story on stage of how early you engaged with Josh and his team, um, first I want to get your kinda your perspective. Why were you doing that so early and what did that ultimately do with some of the design decisions that you guys made? And then we'll come back to Josh as to, you know, his participation. >>So I think whenever you conduct technology transitions, having a sense from customers that have the ability to look out two to three years is very important because when you're capturing market transitions, doing it with customer inputs is far more relevant than going about it alone. Uh, the other key thing about this architectural shift is that it allows the flexibility for every customer to go take pieces of how they want to bring the cloud architectures and bring it into their environment. So understanding that use case and understanding the compelling reasons of what problems both technological and business can be solving and having that perspective into the product definition and the design and the influence that customers like Josh you've had is why we are sitting here and talking about them in production. Uh, as opposed to, yeah, we're thinking about where we are. We are looking at it from a proof of concept perspective. Right. >>And Josh, your, your perspective, you said earlier today that, you know, as long as a sign is involved, you're, you're, uh, you're happy to jump in and see what she's been working on. So how, >>you know, how did you get involved, how did they reach out to you and, and what is it like working on, you know, technology so early in its development that you get to actually have some serious influence? Well, it's an amazing opportunity, um, to get exactly what you want, um, exactly what you know is going to solve problems for the business here. Um, you know, and the other thing is, you know, we've worked with this team, uh, through almost every spinning. Uh, I think it was a little young for the, maybe the first one. Um, but, uh, otherwise this team has worked with them through at least 15 years or more. So we knew the track record for execution and then for us on this product, I mean, it was an opportunity because it's truly a startup. Um, you know, Sony and the team brought us in. >>Uh, we kind of just put out problems on the table that we were trying to solve and then, you know, they came up with the product and the idea and we were able to put together, you know, yeah, these are our priority one, two, three that we want to go for. And you know, we've just been developing alongside them. So both software and, you know, driving what the feature set is. Right. So what were some of those problems guys? Price seemed like forever ago when you started this conversation, but as you kind of looked forward a couple of years back that you could see that were coming, that you needed addressed. You know, it's funny, we started with kind of like, well we think containerization is going to be explosive and, and you know, really everything's on virtual machines or bare metal, mostly virtual machines. So one, you know, as containers come out, how do we track them, secure them, um, how do we even secure, uh, you know, the virtual machines and our environment cause they're, you know, over almost a quarter million of them. >>The idea of being able to put, um, network policy, that's I would say incorruptible, not actually on the server, but at, you know, that's why we use firewalls, right? So solving that security problem was number one. The other one was being able to have the telemetry to see what's happening, what's changing, um, and troubleshoot at, you know, at the network layer from every single server. Again, it's all about scale. Like things were just scaling and the throughput's going up, traditional methods of being able to see what's on your network. You can't look in the middle, it just can't keep up. It's just speeds and feeds. So being able to push those things to the edge. And then lastly, it really happened more, um, through the process here. But about a year and a half ago, um, we began segmenting our network the same way a 5g provider does with a technology called segment routing. >>And we just said, that's kind of our follow on technologies to, you know, put the network in the server and put this segment routing capability all the way out at the edge. So, you know, some things we foresaw and other things we've just developed. You know, it's been, it's been two and a half years. So, um, it's been a great partnership and you know, I think more, more features will come. Well Sony, you and the team, but it's been talked about all day long, have have a history of multiple times that you've kind of brought these big transformational technologies. Um, head what, what did you guys see a couple of years back and kind of this progression, you saw this opportunity >>to do something a little bit different than you've done in the past, which is actually go out, raise, raise around and uh, and do a real startup. What was the opportunity that you saw this? >>So we saw a number of challenges and opportunities. At the same time, we, we clearly saw that, uh, the cloud architectures that have been built by the leaders, like the incumbents like AWS today have a lot of the intelligence that is being pushed into their, their respective compute platforms. Uh, and we also noticed that at the same time, while that was what was needed to build the first generation of the cloud, the new age applications, and even as gardener has predicted that 75% of all enterprise data and applications will be processed at the edge by 2025. If that happens, then you need that intelligence at the edge. You need the ability to go do it where the action is, which is at the edge. And very consistently we found that the architectures, including scale out storage, we're also driving the need for this intelligence to be on in a scale-out manner. >>So if you're going to scale out computing, you need the services to be going hand in hand with that scale. Our computer architecture for the enterprises so they can simplify their architectures and bring the cloud models that have only existed in the cloud world, into their own data centers and their own private clouds. So there were these technology transitions we saw were coming down the pike. It's easier said now in 2019 it wasn't so simple in 2017 because we had to look at these multiple technology transitions. And surprisingly, when we call those things out, as we were shaping the company's strategy, getting validation of the use cases from customers like Josh was pivotally important because it was for the validating that this would be the direction that the enterprises and the cloud customers would be taking. So the reason you start with a vision, you start with looking at where the technology transitions are going to be occurring and getting the customers that are looking farther out validated plays a very important role so that you can go and focus on the biggest problems that you need to go and solve. Right, right. >>It just seems like the, the, the big problem, um, for most layman's is, is the old one, which, why networking exists in the first place, which is do you bring the data to the compute or do you bring the compute to the data? And now as you said, in kind of this hyper distributed world, um, that's not really a viable answer either one, right? Because the two are blended and have to be together so that you don't necessarily have to move one to the other or the other back the other direction. So, and then the second piece that you talked about over and over in your, in your presentation with security and you know, everybody talks about security all the time. Everybody gets hacked every day. Um, and there's this constant theme that security has to be baked in, you know, kind of throughout the process as opposed to kind of bolted on at the end. You guys took that approach from day, just speak >>it into the architecture. Yes. That was crucially important because when you are trying to address the needs of the enterprise, particularly in regulated markets like financial services, you want to be in a position where you have thought about it and baked it into the platform ground up. Uh, and so when we are building the program of a process, so we had the opportunity to go put the right elements on it. In order to make it tamper proof, we had to go think about encrypting all the traffic and communication between our policy manager and the distributed services platforms at the edge. We also then took it a step further to say, now if there were to be a bad actor that were to attack from an operating system vulnerability perspective, how do we ensure that we can contain that bad actor as opposed to being propagated over the infrastructure? So those elements are things you cannot bolt on at design time, or when you need to go put those into the design day one, right. Only on top of that foundation, then can you build a very secure set of services, whether it's encryption, whether it's distributed via services, so on and so forth. >>Uh, and Josh, I'm curious on your take as we've seen kind of software defined everything, uh, slowly take over as opposed to, you know, kind of single purpose machines or single purpose appliances, et cetera. Yep. Really a different opportunity for you to control. Um, but also to see a lot of talk today about, about policy management. A lot of talk about, um, observability and as you said now even segmentation of the networks, like you segment the nodes and you segment everything else. You know, how, how do you see this kind of software defined everything continuing to evolve and what does it enable you to do that you can't do with just a static device? I mean, the approach we took, um, we started like, you know, years ago, about six years ago was saying we can get computers, uh, deployed for our applications. No problem. Uh, and you know, at, at on demand and in our internal cloud, now we can do it as a hybrid cloud solution. >>One of the biggest problems we had in software defined was how do you put security policy, firewall policy, um, with that compute and in, you know, our industry, there's lots of segmentation for material nonpublic information. Um, compliance, you know, it could be internet facing, B2B facing. Uh, we do that today. We program various firewall vendors automatically. Uh, we allow our application developers to create, um, these policies and push them through as code and then program the firewall. What we were really looking to do here is distribute that. So we F day one in getting pen Sandow into production was to use our uh, our firewall system. It's called pinnacle. We, um, we programmed from pinnacle directly into the Penn Songdo Venice manager via API and then it, you know, uses its inventory systems to push those things out. So for us, software defined has been around, I like to call it the store front, but for the developer it's network policy, it's load balancing. >>Um, and, and that's really what they see. Those are the big products on the net. Everything else is just packet forwarding to them. So we wanted with pen Sandow at least starting with security to have that bar set day one and then get, you know, all the benefits of scale, throughput and having the policies close to the, on the edge. You know, we're back to talking about the edge. We want to right there with the, with the deployment, with the workload or the application. And that's, that's what we're doing right off the bat. Yeah. What are the things you mentioned in your talk was w is, you know, kind of in the theme of atomic computing, right? You want to get smaller and smaller units so that you can apply and redeploy based on wherever the workload is and in the change. And you said you've now been able to, you know, basically take things out of dedicated, you know, kind of a dedicated space, dedicated line and dedicated job so that you can now put them in a more virtualized situation. >>Exactly. Grab more resources as you need them. Well, you'd think the architecture, I mean even just theater of the mind is just, you're saying, I'm going to put this specific thing that I have to secure behind these firewalls. So it's one cabinet of computers or a hundred it's still behind a set of firewalls. It's a very North, South, you know, get in and get out here. You're talking about having that same level of security and I think that's novel, right? There hasn't been, if you look at virtual firewalls or you know, IP tables on Linux, I mean it's corruptible. It's, it's, it can be attacked on the computer. And once it's, you know, once you've been attacked in that, that that attack vector has been, you know, hit your, your compromised. This is a separate management plane. Um, you know, separate control plane. The server doesn't see it. >>That security is provided. It's at scale, it's East, West. The more computers that have the pen Sandow, you know, architecture inside of them, the, you know, the wider you can go, right. And then the North South goes away. I'm just curious to get your perspective. Um, as you know, everyone is a technology company. At the same time, technology budgets are going down, people are hard to hire. Uh, your data is growing exponentially and everything's a security threat. Yes. So as you get up in the morning, get ready to drive to work and you're drinking your coffee, I mean, how do you, you know, kind of communicate to make sure to senior management knows kind of what your objectives are in this, this kind of ongoing challenge to do more with less. And it, even though it's an increasingly strategic place or is it actually is what the company does now, it just happens to wrap it around your plane services or financial services or travel or whatever. >>Uh, I think your eye, and I had said it to John before, um, it has to come from that budget has to come from somewhere. So I think a combination of, of one that's less, well, I'll say the one that's easier to quantify is you're going to take budget from say appliance manufacturer and move it to a distributed edge and you're going to hopefully save some money while you do it. Um, you're going to do it at scale. You're gonna do it at, you know, high throughput and the security is the same or better. So that's, that's one, that's one place to take capital from. The other one is to say, can I use the next computer? Yes. Because I don't have to deploy these other new computers behind this stack of firewalls. Is there agility there? Is there efficiency, um, on my buying less servers and using, you know, more of what I have and doing it, you know, able to deploy faster. >>And it's harder to quantify. I think if you could, you know, over time, see I bought 20% less server, uh, capacity or, you know, x86 capacity, that's a savings. And the other one that's very hard to quantify, but it's always nice to have the development community. And we've had it recently where they say, Hey, this took me a month to deploy instead of a year. Um, and you know, the purchase cycles, uh, you know, for procurement and deployment, they're long, you know, in enterprise you want them to be quick, but they're really not. So all of those things add up. And that's the story. You know, I would tell, you know, any manager, right? Yeah, >>yeah. I think, you know, the old historic way that utilization rates were just so, so, so, so low between CPU and memory, everything else. Cause if nothing else, because to get another box, you know, could take a long time. Yeah. Well, final, final question for you, Tony. You talked about architectures and being locked into architectures and you and you talked about you guys are already looking forward, you know, to kind of your next rev, your next release, kind of your next step forwards. What, where do you see kind of the direction, don't give away any secrets, but um, you know, kind of where you guys going. What are your priorities now that you've launched? You got a little bit more money in the bank. >>Well, our biggest priorities will be to focus on customer success is to make sure that the customer journey is indeed replicable at scale, is to enable the partner's success. Uh, so in addition to Goldman Sachs, the ability to go and replicate it across the federated markets, whether it's global financial services, healthcare, federal, and partnering with each B enterprise so that they can on their platform, amplify the value of this architecture, not just on the compute platforms but on, in other areas. And the third one clearly is for our cloud customers is to make sure that they are in a position to build a world class cloud architecture on top of which then they can build their own, deliver their own services, their own secret sauces, uh, so that they can Excel at whatever that cloud is. Whether it's to become the leading edge platform as a service customer, whether it is to be the leading edge of software's a service platform customer. So it's all about the execution as a, as you heard in that room. And that's fundamentally what we're going to strive to be, is to be a great execution machine and keep our heads down and focused on making our customers and our partners very successful. >>Well, certainly, congratulations again to you and the team on the launch today. And Josh, thank you for hosting this terrific event and being an early customer. Yeah. Yeah. Happy to be. Alright. I'm Jetta. Sone. Josh, we're the topic. Goldman Sachs at the Penn Sandow the new welcome to the new edge. Thanks for watching. We'll see you next time.

[Music] [Music] [Music] [Laughter] [Laughter] [Laughter] [Laughter] [Music] [Music] [Music] [Music] you you [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Applause] [Music] wake up feeling blessed peace you warned that Russia ain't afraid to show it I'll expose it if I dressed up riding in that Chester roasted nigga catch you slippin on myself rocks on I messed up like yes sir [Music] [Music] [Music] [Music] our program [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] you are not welcome to Red Hat summit 2018 2018 [Music] [Music] [Music] [Laughter] [Music] Wow that is truly the coolest introduction I've ever had thank you Wow I don't think I feel cool enough to follow an interaction like that Wow well welcome to the Red Hat summit this is our 14th annual event and I have to say looking out over this audience Wow it's great to see so many people here joining us this is by far our largest summit to date not only did we blow through the numbers we've had in the past we blew through our own expectations this year so I know we have a pretty packed house and I know people are still coming in so it's great to see so many people here it's great to see so many familiar faces when I had a chance to walk around earlier it's great to see so many new people here joining us for the first time I think the record attendance is an indication that more and more enterprises around the world are seeing the power of open source to help them with their challenges that they're facing due to the digital transformation that all of enterprises around the world are going through the theme for the summit this year is ideas worth exploring and we intentionally chose that because as much as we are all going through this digital disruption and the challenges associated with it one thing I think is becoming clear no one person and certainly no one company has the answers to these challenges right this isn't a problem where you can go buy a solution this is a set of capabilities that we all need to build it's a set of cultural changes that we all need to go through and that's going to require the best ideas coming from so many different places so we're not here saying we have the answers we're trying to convene the conversation right we want to serve as a catalyst bringing great minds together to share ideas so we all walk out of here at the end of the week a little wiser than when we first came here we do have an amazing agenda for you we have over 7,000 attendees we may be pushing 8,000 by the time we got through this morning we have 36 keynote speakers and we have a hundred and twenty-five breakout sessions and have to throw in one plug scheduling 325 breakout sessions is actually pretty difficult and so we used the Red Hat business optimizer which is an AI constraint solver that's new in the Red Hat decision manager to help us plan the summit because we have individuals who have a clustered set of interests and we want to make sure that when we schedule two breakout sessions we do it in a way that we don't have overlapping sessions that are really important to the same individual so we tried to use this tool and what we understand about people's interest in history of what they wanted to do to try to make sure that we spaced out different times for things of similar interests for similar people as well as for people who stood in the back of breakouts before and I know I've done that too we've also used it to try to optimize room size so hopefully we will do our best to make sure that we've appropriately sized the spaces for those as well so it's really a phenomenal tool and I know it's helped us a lot this year in addition to the 325 breakouts we have a lot of our customers on stage during the main sessions and so you'll see demos you'll hear from partners you'll hear stories from so many of our customers not on our point of view of how to use these technologies but their point of views of how they actually are using these technologies to solve their problems and you'll hear over and over again from those keynotes that it's not just about the technology it's about how people are changing how people are working to innovate to solve those problems and while we're on the subject of people I'd like to take a moment to recognize the Red Hat certified professional of the year this is known award we do every year I love this award because it truly recognizes an individual for outstanding innovation for outstanding ideas for truly standing out in how they're able to help their organization with Red Hat technologies Red Hat certifications help system administrators application developers IT architects to further their careers and help their organizations by being able to advance their skills and knowledge of Red Hat products and this year's winner really truly is a great example about how their curiosity is helped push the limits of what's possible with technology let's hear a little more about this year's winner when I was studying at the University I had computer science as one of my subjects and that's what created the passion from the very beginning they were quite a few institutions around my University who were offering Red Hat Enterprise Linux as a course and a certification paths through to become an administrator Red Hat Learning subscription has offered me a lot more than any other trainings that have done so far that gave me exposure to so many products under red hair technologies that I wasn't even aware of I started to think about the better ways of how these learnings can be put into the real life use cases and we started off with a discussion with my manager saying I have to try this product and I really want to see how it really fits in our environment and that product was Red Hat virtualization we went from deploying rave and then OpenStack and then the open shift environment we wanted to overcome some of the things that we saw as challenges to the speed and rapidity of release and code etc so it made perfect sense and we were able to do it in a really short space of time so you know we truly did use it as an Innovation Lab I think idea is everything ideas can change the way you see things an Innovation Lab was such an idea that popped into my mind one fine day and it has transformed the way we think as a team and it's given that playpen to pretty much everyone to go and test their things investigate evaluate do whatever they like in a non-critical non production environment I recruited Neha almost 10 years ago now I could see there was a spark a potential with it and you know she had a real Drive a real passion and you know here we are nearly ten years later I'm Neha Sandow I am a Red Hat certified engineer all right well everyone please walk into the states to the stage Neha [Music] [Applause] congratulations thank you [Applause] I think that - well welcome to the red has some of this is your first summit yes it is thanks so much well fantastic sure well it's great to have you here I hope you have a chance to engage and share some of your ideas and enjoy the week thank you thank you congratulations [Applause] neha mentioned that she first got interest in open source at university and it made me think red hats recently started our Red Hat Academy program that looks to programmatically infuse Red Hat technologies in universities around the world it's exploded in a way we had no idea it's grown just incredibly rapidly which i think shows the interest that there really is an open source and working in an open way at university so it's really a phenomenal program I'm also excited to announce that we're launching our newest open source story this year at Summit it's called the science of collective discovery and it looks at what happens when communities use open hardware to monitor the environment around them and really how they can make impactful change based on that technologies the rural premier that will be at 5:15 on Wednesday at McMaster Oni West and so please join us for a drink and we'll also have a number of the experts featured in that and you can have a conversation with them as well so with that let's officially start the show please welcome red hat president of products and technology Paul Cormier [Music] Wow morning you know I say it every year I'm gonna say it again I know I repeat myself it's just amazing we are so proud here to be here today too while you all week on how far we've come with opens with open source and with the products that we that we provide at Red Hat so so welcome and I hope the pride shows through so you know I told you Seven Summits ago on this stage that the future would be open and here we are just seven years later this is the 14th summit but just seven years later after that and much has happened and I think you'll see today and this week that that prediction that the world would be open was a pretty safe predict prediction but I want to take you just back a little bit to see how we started here and it's not just how Red Hat started here this is an open source in Linux based computing is now in an industry norm and I think that's what you'll you'll see in here this week you know we talked back then seven years ago when we put on our prediction about the UNIX error and how Hardware innovation with x86 was it was really the first step in a new era of open innovation you know companies like Sun Deck IBM and HP they really changed the world the computing industry with their UNIX models it was that was really the rise of computing but I think what we we really saw then was that single company innovation could only scale so far could really get so far with that these companies were very very innovative but they coupled hardware innovation with software innovation and as one company they could only solve so many problems and even which comp which even complicated things more they could only hire so many people in each of their companies Intel came on the scene back then as the new independent hardware player and you know that was really the beginning of the drive for horizontal computing power and computing this opened up a brand new vehicle for hardware innovation a new hardware ecosystem was built around this around this common hardware base shortly after that Stallman and leanness they had a vision of his of an open model that was created and they created Linux but it was built around Intel this was really the beginning of having a software based platform that could also drive innovation this kind of was the beginning of the changing of the world here that system-level innovation now having a hardware platform that was ubiquitous and a software platform that was open and ubiquitous it really changed this system level innovation and that continues to thrive today it was only possible because it was open this could not have happened in a closed environment it allowed the best ideas from anywhere from all over to come in in win only because it was the best idea that's what drove the rate of innovation at the pace you're seeing today and it which has never been seen before we at Red Hat we saw the need to bring this innovation to solve real-world problems in the enterprise and I think that's going to be the theme of the show today you're going to see us with our customers and partners talking about and showing you some of those real-world problems that we are sought solving with this open innovation we created rel back then for this for the enterprise it started it's it it wasn't successful because it's scaled it was secure and it was enterprise ready it once again changed the industry but this time through open innovation this gave the hardware ecosystem a software platform this open software platform gave the hardware ecosystem a software platform to build around it Unleashed them the hardware side to compete and thrive it enabled innovation from the OEMs new players building cheaper faster servers even new architectures from armed to power sprung up with this change we have seen an incredible amount of hardware innovation over the last 15 years that same innovation happened on the software side we saw powerful implementations of bare metal Linux distributions out in the market in fact at one point there were 300 there are over 300 distributions out in the market on the foundation of Linux powerful open-source equivalents were even developed in every area of Technology databases middleware messaging containers anything you could imagine innovation just exploded around the Linux platform in innovation it's at the core also drove virtualization both Linux and virtualization led to another area of innovation which you're hearing a lot about now public cloud innovation this innovation started to proceed at a rate that we had never seen before we had never experienced this in the past in this unprecedented speed of innovation and software was now possible because you didn't need a chip foundry in order to innovate you just needed great ideas in the open platform that was out there customers seeing this innovation in the public cloud sparked it sparked their desire to build their own linux based cloud platforms and customers are now are now bringing that cloud efficiency on-premise in their own data centers public clouds demonstrated so much efficiency the data centers and architects wanted to take advantage of it off premise on premise I'm sorry within their own we don't within their own controlled environments this really allowed companies to make the most of existing investments from data centers to hardware they also gained many new advantages from data sovereignty to new flexible agile approaches I want to bring Burr and his team up here to take a look at what building out an on-premise cloud can look like today Bure take it away I am super excited to be with all of you here at Red Hat summit I know we have some amazing things to show you throughout the week but before we dive into this demonstration I want you to take just a few seconds just a quick moment to think about that really important event your life that moment you turned on your first computer maybe it was a trs-80 listen Claire and Atari I even had an 83 b2 at one point but in my specific case I was sitting in a classroom in Hawaii and I could see all the way from Diamond Head to Pearl Harbor so just keep that in mind and I turn on an IBM PC with dual floppies I don't remember issuing my first commands writing my first level of code and I was totally hooked it was like a magical moment and I've been hooked on computers for the last 30 years so I want you to hold that image in your mind for just a moment just a second while we show you the computers we have here on stage let me turn this over to Jay fair and Dini here's our worldwide DevOps manager and he was going to show us his hardware what do you got Jay thank you BER good morning everyone and welcome to Red Hat summit we have so many cool things to show you this week I am so happy to be here and you know my favorite thing about red hat summit is our allowed to kind of share all of our stories much like bird just did we also love to you know talk about the hardware and the technology that we brought with us in fact it's become a bit of a competition so this year we said you know let's win this thing and we actually I think we might have won we brought a cloud with us so right now this is a private cloud for throughout the course of the week we're going to turn this into a very very interesting open hybrid cloud right before your eyes so everything you see here will be real and happening right on this thing right behind me here so thanks for our four incredible partners IBM Dell HP and super micro we've built a very vendor heterogeneous cloud here extra special thanks to IBM because they loaned us a power nine machine so now we actually have multiple architectures in this cloud so as you know one of the greatest benefits to running Red Hat technology is that we run on just about everything and you know I can't stress enough how powerful that is how cost-effective that is and it just makes my life easier to be honest so if you're interested the people that built this actual rack right here gonna be hanging out in the customer success zone this whole week it's on the second floor the lobby there and they'd be glad to show you exactly how they built this thing so let me show you what we actually have in this rack so contained in this rack we have 1056 physical chorus right here we have five and a half terabytes of RAM and just in case we threw 50 terabytes of storage in this thing so burr that's about two million times more powerful than that first machine you boot it up thanks to a PC we're actually capable of putting all the power needs and cooling right in this rack so there's your data center right there you know it occurred to me last night that I can actually pull the power cord on this thing and kick it up a notch we could have the world's first mobile portable hybrid cloud so I'm gonna go ahead and unplug no no no no no seriously it's not unplug the thing we got it working now well Berg gets a little nervous but next year we're rolling this thing around okay okay so to recap multiple vendors check multiple architectures check multiple public clouds plug right into this thing check and everything everywhere is running the same software from Red Hat so that is a giant check so burn Angus why don't we get the demos rolling awesome so we have totally we have some amazing hardware amazing computers on this stage but now we need to light it up and we have Angus Thomas who represents our OpenStack engineering team and he's going to show us what we can do with this awesome hardware Angus thank you Beth so this was an impressive rack of hardware to Joe has bought a pocket stage what I want to talk about today is putting it to work with OpenStack platform director we're going to turn it from a lot of potential into a flexible scalable private cloud we've been using director for a while now to take care of managing hardware and orchestrating the deployment of OpenStack what's new is that we're bringing the same capabilities for on-premise manager the deployment of OpenShift director deploying OpenShift in this way is the best of both worlds it's bare-metal performance but with an underlying infrastructure as a service that can take care of deploying in new instances and scaling out and a lot of the things that we expect from a cloud provider director is running on a virtual machine on Red Hat virtualization at the top of the rack and it's going to bring everything else under control what you can see on the screen right now is the director UI and as you see some of the hardware in the rack is already being managed at the top level we have information about the number of cores in the amount of RAM and the disks that each machine have if we dig in a bit there's information about MAC addresses and IPs and the management interface the BIOS kernel version dig a little deeper and there is information about the hard disks all of this is important because we want to be able to make sure that we put in workloads exactly where we want them Jay could you please power on the two new machines at the top of the rack sure all right thank you so when those two machines come up on the network director is going to see them see that they're new and not already under management and is it immediately going to go into the hardware inspection that populates this database and gets them ready for use so we also have profiles as you can see here profiles are the way that we match the hardware in a machine to the kind of workload that it's suited to this is how we make sure that machines that have all the discs run Seth and machines that have all the RAM when our application workouts for example there's two ways these can be set when you're dealing with a rack like this you could go in an individually tag each machine but director scales up to data centers so we have a rules matching engine which will automatically take the hardware profile of a new machine and make sure it gets tagged in exactly the right way so we can automatically discover new machines on the network and we can automatically match them to a profile that's how we streamline and scale up operations now I want to talk about deploying the software we have a set of validations we've learned over time about the Miss configurations in the underlying infrastructure which can cause the deployment of a multi node distributed application like OpenStack or OpenShift to fail if you have the wrong VLAN tags on a switch port or DHCP isn't running where it should be for example you can get into a situation which is really hard to debug a lot of our validations actually run before the deployment they look at what you're intending to deploy and they check in the environment is the way that it should be and they'll preempts problems and obviously preemption is a lot better than debugging something new that you probably have not seen before is director managing multiple deployments of different things side by side before we came out on stage we also deployed OpenStack on this rack just to keep me honest let me jump over to OpenStack very quickly a lot of our opens that customers will be familiar with this UI and the bare metal deployment of OpenStack on our rack is actually running a set of virtual machines which is running Gluster you're going to see that put to work later on during the summit Jay's gone to an awful lot effort to get this Hardware up on the stage so we're going to use it as many different ways as we can okay let's deploy OpenShift if I switch over to the deployed a deployment plan view there's a few steps first thing you need to do is make sure we have the hardware I already talked about how director manages hardware it's smart enough to make sure that it's not going to attempt to deploy into machines they're already in use it's only going to deploy on machines that have the right profile but I think with the rack that we have here we've got enough next thing is the deployment configuration this is where you get to customize exactly what's going to be deployed to make sure that it really matches your environment if they're external IPs for additional services you can set them here whatever it takes to make sure that the deployment is going to work for you as you can see on the screen we have a set of options around enable TLS for encryption network traffic if I dig a little deeper there are options around enabling ipv6 and network isolation so that different classes of traffic there are over different physical NICs okay then then we have roles now roles this is essentially about the software that's going to be put on each machine director comes with a set of roles for a lot of the software that RedHat supports and you can just use those or you can modify them a little bit if you need to add a monitoring agent or whatever it might be or you can create your own custom roles director has quite a rich syntax for custom role definition and custom Network topologies whatever it is you need in order to make it work in your environment so the rawls that we have right now are going to give us a working instance of openshift if I go ahead and click through the validations are all looking green so right now I can click the button start to the deploy and you will see things lighting up on the rack directors going to use IPMI to reboot the machines provisioned and with a trail image was the containers on them and start up the application stack okay so one last thing once the deployment is done you're going to want to keep director around director has a lot of capabilities around what we call de to operational management bringing in new Hardware scaling out deployments dealing with updates and critically doing upgrades as well so having said all of that it is time for me to switch over to an instance of openshift deployed by a director running on bare metal on our rack and I need to hand this over to our developer team so they can show what they can do it thank you that is so awesome Angus so what you've seen now is going from bare metal to the ultimate private cloud with OpenStack director make an open shift ready for our developers to build their next generation applications thank you so much guys that was totally awesome I love what you guys showed there now I have the honor now I have the honor of introducing a very special guest one of our earliest OpenShift customers who understands the necessity of the private cloud inside their organization and more importantly they're fundamentally redefining their industry please extend a warm welcome to deep mar Foster from Amadeus well good morning everyone a big thank you for having armadillos here and myself so as it was just set I'm at Mario's well first of all we are a large IT provider in the travel industry so serving essentially Airlines hotel chains this distributors like Expedia and others we indeed we started very early what was OpenShift like a bit more than three years ago and we jumped on it when when Retta teamed with Google to bring in kubernetes into this so let me quickly share a few figures about our Mario's to give you like a sense of what we are doing and the scale of our operations so some of our key KPIs one of our key metrics is what what we call passenger borders so that's the number of customers that physically board a plane over the year so through our systems it's roughly 1.6 billion people checking in taking the aircrafts on under the Amarillo systems close to 600 million travel agency bookings virtually all airlines are on the system and one figure I want to stress out a little bit is this one trillion availability requests per day that's when I read this figure my mind boggles a little bit so this means in continuous throughput more than 10 million hits per second so of course these are not traditional database transactions it's it's it's highly cached in memory and these applications are running over like more than 100,000 course so it's it's it's really big stuff so today I want to give some concrete feedback what we are doing so I have chosen two applications products of our Mario's that are currently running on production in different in different hosting environments as the theme here is of this talk hybrid cloud and so I want to give some some concrete feedback of how we architect the applications and of course it stays relatively high level so here I have taken one of our applications that is used in the hospitality environment so it's we have built this for a very large US hotel chain and it's currently in in full swing brought into production so like 30 percent of the globe or 5,000 plus hotels are on this platform not so here you can see that we use as the path of course on openshift on that's that's the most central piece of our hybrid cloud strategy on the database side we use Oracle and Couchbase Couchbase is used for the heavy duty fast access more key value store but also to replicate data across two data centers in this case it's running over to US based data centers east and west coast topology that are fit so run by Mario's that are fit with VMware on for the virtualization OpenStack on top of it and then open shift to host and welcome the applications on the right hand side you you see the kind of tools if you want to call them tools that we use these are the principal ones of course the real picture is much more complex but in essence we use terraform to map to the api's of the underlying infrastructure so they are obviously there are differences when you run on OpenStack or the Google compute engine or AWS Azure so some some tweaking is needed we use right at ansible a lot we also use puppet so you can see these are really the big the big pieces of of this sense installation and if we look to the to the topology again very high high level so these two locations basically map the data centers of our customers so they are in close proximity because the response time and the SLA is of this application is are very tight so that's an example of an application that is architectures mostly was high ability and high availability in minds not necessarily full global worldwide scaling but of course it could be scaled but here the idea is that we can swing from one data center to the unit to the other in matters of of minutes both take traffic data is fully synchronized across those data centers and while the switch back and forth is very fast the second example I have taken is what we call the shopping box this is when people go to kayak or Expedia and they're getting inspired where they want to travel to this is really the piece that shoots most of transit of the transactions into our Mario's so we architect here more for high scalability of course availability is also a key but here scaling and geographical spread is very important so in short it runs partially on-premise in our Amarillo Stata Center again on OpenStack and we we deploy it mostly in the first step on the Google compute engine and currently as we speak on Amazon on AWS and we work also together with Retta to qualify the whole show on Microsoft Azure here in this application it's it's the same building blocks there is a large swimming aspect to it so we bring Kafka into this working with records and another partner to bring Kafka on their open shift because at the end we want to use open shift to administrate the whole show so over time also databases and the topology here when you look to the physical deployment topology while it's very classical we use the the regions and the availability zone concept so this application is spread over three principal continental regions and so it's again it's a high-level view with different availability zones and in each of those availability zones we take a hit of several 10,000 transactions so that was it really in very short just to give you a glimpse on how we implement hybrid clouds I think that's the way forward it gives us a lot of freedom and it allows us to to discuss in a much more educated way with our customers that sometimes have already deals in place with one cloud provider or another so for us it's a lot of value to set two to leave them the choice basically what up that was a very quick overview of what we are doing we were together with records are based on open shift essentially here and more and more OpenStack coming into the picture hope you found this interesting thanks a lot and have a nice summer [Applause] thank you so much deeper great great solution we've worked with deep Marv and his team for a long for a long time great solution so I want to take us back a little bit I want to circle back I sort of ended talking a little bit about the public cloud so let's circle back there you know even so even though some applications need to run in various footprints on premise there's still great gains to be had that for running certain applications in the public cloud a public cloud will be as impactful to to the industry as as UNIX era was of computing was but by itself it'll have some of the same limitations and challenges that that model had today there's tremendous cloud innovation happening in the public cloud it's being driven by a handful of massive companies and much like the innovation that sundeck HP and others drove in a you in the UNIX era of community of computing many customers want to take advantage of the best innovation no matter where it comes from buddy but as they even eventually saw in the UNIX era they can't afford the best innovation at the cost of a siloed operating environment with the open community we are building a hybrid application platform that can give you access to the best innovation no matter which vendor or which cloud that it comes from letting public cloud providers innovate and services beyond what customers or anyone can one provider can do on their own such as large scale learning machine learning or artificial intelligence built on the data that's unique probably to that to that one cloud but consumed in a common way for the end customer across all applications in any environment on any footprint in in their overall IT infrastructure this is exactly what rel brought brought to our customers in the UNIX era of computing that consistency across any of those footprints obviously enterprises will have applications for all different uses some will live on premise some in the cloud hybrid cloud is the only practical way forward I think you've been hearing that from us for a long time it is the only practical way forward and it'll be as impactful as anything we've ever seen before I want to bring Byrne his team back to see a hybrid cloud deployment in action burr [Music] all right earlier you saw what we did with taking bare metal and lighting it up with OpenStack director and making it openshift ready for developers to build their next generation applications now we want to show you when those next turn and generation applications and what we've done is we take an open shift and spread it out and installed it across Asia and Amazon a true hybrid cloud so with me on stage today as Ted who's gonna walk us through an application and Brent Midwood who's our DevOps engineer who's gonna be making sure he's monitoring on the backside that we do make sure we do a good job so at this point Ted what have you got for us Thank You BER and good morning everybody this morning we are running on the stage in our private cloud an application that's providing its providing fraud detection detect serves for financial transactions and our customer base is rather large and we occasionally take extended bursts of traffic of heavy traffic load so in order to keep our latency down and keep our customers happy we've deployed extra service capacity in the public cloud so we have capacity with Microsoft Azure in Texas and with Amazon Web Services in Ohio so we use open chip container platform on all three locations because openshift makes it easy for us to deploy our containerized services wherever we want to put them but the question still remains how do we establish seamless communication across our entire enterprise and more importantly how do we balance the workload across these three locations in such a way that we efficiently use our resources and that we give our customers the best possible experience so this is where Red Hat amq interconnect comes in as you can see we've deployed a MQ interconnect alongside our fraud detection applications in all three locations and if I switch to the MQ console we'll see the topology of the app of the network that we've created here so the router inside the on stage here has made connections outbound to the public routers and AWS and Azure these connections are secured using mutual TLS authentication and encrypt and once these connections are established amq figures out the best way auda matically to route traffic to where it needs to get to so what we have right now is a distributed reliable broker list message bus that expands our entire enterprise now if you want to learn more about this make sure that you catch the a MQ breakout tomorrow at 11:45 with Jack Britton and David Ingham let's have a look at the message flow and we'll dive in and isolate the fraud detection API that we're interested in and what we see is that all the traffic is being handled in the private cloud that's what we expect because our latencies are low and they're acceptable but now if we take a little bit of a burst of increased traffic we're gonna see that an EQ is going to push a little a bi traffic out onto the out to the public cloud so as you're picking up some of the load now to keep the Layton sees down now when that subsides as your finishes up what it's doing and goes back offline now if we take a much bigger load increase you'll see two things first of all asher is going to take a bigger proportion than it did before and Amazon Web Services is going to get thrown into the fray as well now AWS is actually doing less work than I expected it to do I expected a little bit of bigger a slice there but this is a interesting illustration of what's going on for load balancing mq load balancing is sending requests to the services that have the lowest backlog and in order to keep the Layton sees as steady as possible so AWS is probably running slowly for some reason and that's causing a and Q to push less traffic its way now the other thing you're going to notice if you look carefully this graph fluctuate slightly and those fluctuations are caused by all the variances in the network we have the cloud on stage and we have clouds in in the various places across the country there's a lot of equipment locked layers of virtualization and networking in between and we're reacting in real-time to the reality on the digital street so BER what's the story with a to be less I noticed there's a problem right here right now we seem to have a little bit performance issue so guys I noticed that as well and a little bit ago I actually got an alert from red ahead of insights letting us know that there might be some potential optimizations we could make to our environment so let's take a look at insights so here's the Red Hat insights interface you can see our three OpenShift deployments so we have the set up here on stage in San Francisco we have our Azure deployment in Texas and we also have our AWS deployment in Ohio and insights is highlighting that that deployment in Ohio may have some issues that need some attention so Red Hat insights collects anonymized data from manage systems across our customer environment and that gives us visibility into things like vulnerabilities compliance configuration assessment and of course Red Hat subscription consumption all of this is presented in a SAS offering so it's really really easy to use it requires minimal infrastructure upfront and it provides an immediate return on investment what insights is showing us here is that we have some potential issues on the configuration side that may need some attention from this view I actually get a look at all the systems in our inventory including instances and containers and you can see here on the left that insights is highlighting one of those instances as needing some potential attention it might be a candidate for optimization this might be related to the issues that you were seeing just a minute ago insights uses machine learning and AI techniques to analyze all collected data so we combine collected data from not only the system's configuration but also with other systems from across the Red Hat customer base this allows us to compare ourselves to how we're doing across the entire set of industries including our own vertical in this case the financial services industry and we can compare ourselves to other customers we also get access to tailored recommendations that let us know what we can do to optimize our systems so in this particular case we're actually detecting an issue here where we are an outlier so our configuration has been compared to other configurations across the customer base and in this particular instance in this security group were misconfigured and so insights actually gives us the steps that we need to use to remediate the situation and the really neat thing here is that we actually get access to a custom ansible playbook so if we want to automate that type of a remediation we can use this inside of Red Hat ansible tower Red Hat satellite Red Hat cloud forms it's really really powerful the other thing here is that we can actually apply these recommendations right from within the Red Hat insights interface so with just a few clicks I can select all the recommendations that insights is making and using that built-in ansible automation I can apply those recommendations really really quickly across a variety of systems this type of intelligent automation is really cool it's really fast and powerful so really quickly here we're going to see the impact of those changes and so we can tell that we're doing a little better than we were a few minutes ago when compared across the customer base as well as within the financial industry and if we go back and look at the map we should see that our AWS employment in Ohio is in a much better state than it was just a few minutes ago so I'm wondering Ted if this had any effect and might be helping with some of the issues that you were seeing let's take a look looks like went green now let's see what it looks like over here yeah doesn't look like the configuration is taking effect quite yet maybe there's some delay awesome fantastic the man yeah so now we're load balancing across the three clouds very much fantastic well I have two minute Ted I truly love how we can route requests and dynamically load transactions across these three clouds a truly hybrid cloud native application you guys saw here on on stage for the first time and it's a fully portable application if you build your applications with openshift you can mover from cloud to cloud to cloud on stage private all the way out to the public said it's totally awesome we also have the application being fully managed by Red Hat insights I love having that intelligence watching over us and ensuring that we're doing everything correctly that is fundamentally awesome thank you so much for that well we actually have more to show you but you're going to wait a few minutes longer right now we'd like to welcome Paul back to the stage and we have a very special early Red Hat customer an Innovation Award winner from 2010 who's been going boldly forward with their open hybrid cloud strategy please give a warm welcome to Monty Finkelstein from Citigroup [Music] [Music] hi Marty hey Paul nice to see you thank you very much for coming so thank you for having me Oh our pleasure if you if you wanted to we sort of wanted to pick your brain a little bit about your experiences and sort of leading leading the charge in computing here so we're all talking about hybrid cloud how has the hybrid cloud strategy influenced where you are today in your computing environment so you know when we see the variable the various types of workload that we had an hour on from cloud we see the peaks we see the valleys we see the demand on the environment that we have we really determined that we have to have a much more elastic more scalable capability so we can burst and stretch our environments to multiple cloud providers these capabilities have now been proven at City and of course we consider what the data risk is as well as any regulatory requirement so how do you how do you tackle the complexity of multiple cloud environments so every cloud provider has its own unique set of capabilities they have they're own api's distributions value-added services we wanted to make sure that we could arbitrate between the different cloud providers maintain all source code and orchestration capabilities on Prem to drive those capabilities from within our platforms this requires controlling the entitlements in a cohesive fashion across our on Prem and Wolfram both for security services automation telemetry as one seamless unit can you talk a bit about how you decide when you to use your own on-premise infrastructure versus cloud resources sure so there are multiple dimensions that we take into account right so the first dimension we talk about the risk so low risk - high risk and and really that's about the data classification of the environment we're talking about so whether it's public or internal which would be considered low - ooh confidential PII restricted sensitive and so on and above which is really what would be considered a high-risk the second dimension would be would focus on demand volatility and responsiveness sensitivity so this would range from low response sensitivity and low variability of the type of workload that we have to the high response sensitivity and high variability of the workload the first combination that we focused on is the low risk and high variability and high sensitivity for response type workload of course any of the workloads we ensure that we're regulatory compliant as well as we achieve customer benefits with within this environment so how can we give developers greater control of their their infrastructure environments and still help operations maintain that consistency in compliance so the main driver is really to use the public cloud is scale speed and increased developer efficiencies as well as reducing cost as well as risk this would mean providing develop workspaces and multiple environments for our developers to quickly create products for our customers all this is done of course in a DevOps model while maintaining the source and artifacts registry on-prem this would allow our developers to test and select various middleware products another product but also ensure all the compliance activities in a centrally controlled repository so we really really appreciate you coming by and sharing that with us today Monte thank you so much for coming to the red echo thanks a lot thanks again tamati I mean you know there's these real world insight into how our products and technologies are really running the businesses today that's that's just the most exciting part so thank thanks thanks again mati no even it with as much progress as you've seen demonstrated here and you're going to continue to see all week long we're far from done so I want to just take us a little bit into the path forward and where we we go today we've talked about this a lot innovation today is driven by open source development I don't think there's any question about that certainly not in this room and even across the industry as a whole that's a long way that we've come from when we started our first summit 14 years ago with over a million open source projects out there this unit this innovation aggregates into various community platforms and it finally culminates in commercial open source based open source developed products these products run many of the mission-critical applications in business today you've heard just a couple of those today here on stage but it's everywhere it's running the world today but to make customers successful with that interact innovation to run their real-world business applications these open source products have to be able to leverage increase increasingly complex infrastructure footprints we must also ensure a common base for the developer and ultimately the application no matter which footprint they choose as you heard mati say the developers want choice here no matter which no matter which footprint they are ultimately going to run their those applications on they want that flexibility from the data center to possibly any public cloud out there in regardless of whether that application was built yesterday or has been running the business for the last 10 years and was built on 10-year old technology this is the flexibility that developers require today but what does different infrastructure we may require different pieces of the technical stack in that deployment one example of this that Effects of many things as KVM which provides the foundation for many of those use cases that require virtualization KVM offers a level of consistency from a technical perspective but rel extends that consistency to add a level of commercial and ecosystem consistency for the application across all those footprints this is very important in the enterprise but while rel and KVM formed the foundation other technologies are needed to really satisfy the functions on these different footprints traditional virtualization has requirements that are satisfied by projects like overt and products like Rev traditional traditional private cloud implementations has requirements that are satisfied on projects like OpenStack and products like Red Hat OpenStack platform and as applications begin to become more container based we are seeing many requirements driven driven natively into containers the same Linux in different forms provides this common base across these four footprints this level of compatible compatibility is critical to operators who must best utilize the infinite must better utilize secure and deploy the infrastructure that they have and they're responsible for developers on the other hand they care most about having a platform that can creates that consistency for their applications they care about their services and the services that they need to consume within those applications and they don't want limitations on where they run they want service but they want it anywhere not necessarily just from Amazon they want integration between applications no matter where they run they still want to run their Java EE now named Jakarta EE apps and bring those applications forward into containers and micro services they need able to orchestrate these frameworks and many more across all these different footprints in a consistent secure fashion this creates natural tension between development and operations frankly customers amplify this tension with organizational boundaries that are holdover from the UNIX era of computing it's really the job of our platforms to seamlessly remove these boundaries and it's the it's the goal of RedHat to seamlessly get you from the old world to the new world we're gonna show you a really cool demo demonstration now we're gonna show you how you can automate this transition first we're gonna take a Windows virtual machine from a traditional VMware deployment we're gonna convert it into a KVM based virtual machine running in a container all under the kubernetes umbrella this makes virtual machines more access more accessible to the developer this will accelerate the transformation of those virtual machines into cloud native container based form well we will work this prot we will worked as capability over the product line in the coming releases so we can strike the balance of enabling our developers to move in this direction we want to be able to do this while enabling mission-critical operations to still do their job so let's bring Byrne his team back up to show you this in action for one more thanks all right what Red Hat we recognized that large organizations large enterprises have a substantial investment and legacy virtualization technology and this is holding you back you have thousands of virtual machines that need to be modernized so what you're about to see next okay it's something very special with me here on stage we have James Lebowski he's gonna be walking us through he's represents our operations folks and he's gonna be walking us through a mass migration but also is Itamar Hine who's our lead developer of a very special application and he's gonna be modernizing container izing and optimizing our application all right so let's get started James thanks burr yeah so as you can see I have a typical VMware environment here I'm in the vSphere client I've got a number of virtual machines a handful of them that make up my one of my applications for my development environment in this case and what I want to do is migrate those over to a KVM based right at virtualization environment so what I'm gonna do is I'm gonna go to cloud forms our cloud management platform that's our first step and you know cloud forms actually already has discovered both my rev environment and my vSphere environment and understands the compute network and storage there so you'll notice one of the capabilities we built is this new capability called migrations and underneath here I could begin to there's two steps and the first thing I need to do is start to create my infrastructure mappings what this will allow me to do is map my compute networking storage between vSphere and Rev so cloud forms understands how those relate let's go ahead and create an infrastructure mapping I'll call that summit infrastructure mapping and then I'm gonna begin to map my two environments first the compute so the clusters here next the data stores so those virtual machines happen to live on datastore - in vSphere and I'll target them a datastore data to inside of my revenue Arman and finally my networks those live on network 100 so I'll map those from vSphere to rover so once my infrastructure is map the next step I need to do is actually begin to create a plan to migrate those virtual machines so I'll continue to the plan wizard here I'll select the infrastructure mapping I just created and I'll select migrate my development environment from those virtual machines to Rev and then I need to import a CSV file the CSV file is going to contain a list of all the virtual machines that I want to migrate that were there and that's it once I hit create what's going to happen cloud forms is going to begin in an automated fashion shutting down those virtual machines begin converting them taking care of all the minutia that you'd have to do manually it's gonna do that all automatically for me so I don't have to worry about all those manual interactions and no longer do I have to go manually shut them down but it's going to take care of that all for me you can see the migrations kicked off here this is the I've got the my VMs are migrating here and if I go back to the screen here you can see that we're gonna start seeing those shutdown okay awesome but as people want to know more information about this how would they dive deeper into this technology later this week yeah it's a great question so we have a workload portability session in the hybrid cloud on Wednesday if you want to see a presentation that deep dives into this topic and how some of the methodologies to migrate and then on Thursday we actually have a hands-on lab it's the IT optimization VM migration lab that you can check out and as you can see those are shutting down here yeah we see a powering off right now that's fantastic absolutely so if I go back now that's gonna take a while you got to convert all the disks and move them over but we'll notice is previously I had already run one migration of a single application that was a Windows virtual machine running and if I browse over to Red Hat virtualization I can see on the dashboard here I could browse to virtual machines I have migrated that Windows virtual machine and if I open up a tab I can now browse to my Windows virtual machine which is running our wingtip toy store application our sample application here and now my VM has been moved over from Rev to Vita from VMware to Rev and is available for Itamar all right great available to our developers all right Itamar what are you gonna do for us here well James it's great that you can save cost by moving from VMware to reddit virtualization but I want to containerize our application and with container native virtualization I can run my virtual machine on OpenShift like any other container using Huebert a kubernetes operator to run and manage virtual machines let's look at the open ship service catalog you can see we have a new virtualization section here we can import KVM or VMware virtual machines or if there are already loaded we can create new instances of them for the developer to work with just need to give named CPU memory we can do other virtualization parameters and create our virtual machines now let's see how this looks like in the openshift console the cool thing about KVM is virtual machines are just Linux processes so they can act and behave like other open shipped applications we build in more than a decade of virtualization experience with KVM reddit virtualization and OpenStack and can now benefit from kubernetes and open shift to manage and orchestrate our virtual machines since we know this virtual machine this container is actually a virtual machine we can do virtual machine stuff with it like shutdown reboot or open a remote desktop session to it but we can also see this is just a container like any other container in openshift and even though the web application is running inside a Windows virtual machine the developer can still use open shift mechanisms like services and routes let's browse our web application using the OpenShift service it's the same wingtip toys application but this time the virtual machine is running on open shift but we're not done we want to containerize our application since it's a Windows virtual machine we can open a remote desktop session to it we see we have here Visual Studio and an asp.net application let's start container izing by moving the Microsoft sequel server database from running inside the Windows virtual machine to running on Red Hat Enterprise Linux as an open shipped container we'll go back to the open shipped Service Catalog this time we'll go to the database section and just as easily we'll create a sequel server container just need to accept the EULA provide password and choose the Edition we want and create a database and again we can see the sequel server is just another container running on OpenShift now let's take let's find the connection details for our database to keep this simple we'll take the IP address of our database service go back to the web application to visual studio update the IP address in the connection string publish our application and go back to browse it through OpenShift fortunately for us the user experience team heard we're modernizing our application so they pitched in and pushed new icons to use with our containerized database to also modernize the look and feel it's still the same wingtip toys application it's running in a virtual machine on openshift but it's now using a containerized database to recap we saw that we can run virtual machines natively on openshift like any other container based application modernize and mesh them together we containerize the database but we can use the same approach to containerize any part of our application so some items here to deserve repeating one thing you saw is Red Hat Enterprise Linux burning sequel server in a container on open shift and you also saw Windows VM where the dotnet native application also running inside of open ships so tell us what's special about that that seems pretty crazy what you did there exactly burr if we take a look under the hood we can use the kubernetes commands to see the list of our containers in this case the sequel server and the virtual machine containers but since Q Bert is a kubernetes operator we can actually use kubernetes commands like cube Cpl to list our virtual machines and manage our virtual machines like any other entity in kubernetes I love that so there's your crew meta gem oh we can see the kind says virtual machine that is totally awesome now people here are gonna be very excited about what they just saw we're gonna get more information and when will this be coming well you know what can they do to dive in this will be available as part of reddit Cloud suite in tech preview later this year but we are looking for early adopters now so give us a call also come check our deep dive session introducing container native virtualization Thursday 2:00 p.m. awesome that is so incredible so we went from the old to the new from the close to the open the Red Hat way you're gonna be seeing more from our demonstration team that's coming Thursday at 8 a.m. do not be late if you like what you saw this today you're gonna see a lot more of that going forward so we got some really special things in store for you so at this point thank you so much in tomorrow thank you so much you guys are awesome yeah now we have one more special guest a very early adopter of Red Hat Enterprise Linux we've had over a 12-year partnership and relationship with this organization they've been a steadfast Linux and middleware customer for many many years now please extend a warm welcome to Raj China from the Royal Bank of Canada thank you thank you it's great to be here RBC is a large global full-service is back we have the largest bank in Canada top 10 global operate in 30 countries and run five key business segments personal commercial banking investor in Treasury services capital markets wealth management and insurance but honestly unless you're in the banking segment those five business segments that I just mentioned may not mean a lot to you but what you might appreciate is the fact that we've been around in business for over 150 years we started our digital transformation journey about four years ago and we are focused on new and innovative technologies that will help deliver the capabilities and lifestyle our clients are looking for we have a very simple vision and we often refer to it as the digitally enabled bank of the future but as you can appreciate transforming a hundred fifty year old Bank is not easy it certainly does not happen overnight to that end we had a clear unwavering vision a very strong innovation agenda and most importantly a focus towards a flawless execution today in banking business strategy and IT strategy are one in the same they are not two separate things we believe that in order to be the number one bank we have to have the number one tactic there is no question that most of today's innovations happens in the open source community RBC relies on RedHat as a key partner to help us consume these open source innovations in a manner that it meets our enterprise needs RBC was an early adopter of Linux we operate one of the largest footprints of rel in Canada same with tables we had tremendous success in driving cost out of infrastructure by partnering with rahat while at the same time delivering a world-class hosting service to your business over our 12 year partnership Red Hat has proven that they have mastered the art of working closely with the upstream open source community understanding the needs of an enterprise like us in delivering these open source innovations in a manner that we can consume and build upon we are working with red hat to help increase our agility and better leverage public and private cloud offerings we adopted virtualization ansible and containers and are excited about continuing our partnership with Red Hat in this journey throughout this journey we simply cannot replace everything we've had from the past we have to bring forward these investments of the past and improve upon them with new and emerging technologies it is about utilizing emerging technologies but at the same time focusing on the business outcome the business outcome for us is serving our clients and delivering the information that they are looking for whenever they need it and in whatever form factor they're looking for but technology improvements alone are simply not sufficient to do a digital transformation creating the right culture of change and adopting new methodologies is key we introduced agile and DevOps which has boosted the number of adult projects at RBC and increase the frequency at which we do new releases to our mobile app as a matter of fact these methodologies have enabled us to deliver apps over 20x faster than before the other point about around culture that I wanted to mention was we wanted to build an engineering culture an engineering culture is one which rewards curiosity trying new things investing in new technologies and being a leader not necessarily a follower Red Hat has been a critical partner in our journey to date as we adopt elements of open source culture in engineering culture what you seen today about red hearts focus on new technology innovations while never losing sight of helping you bring forward the investments you've already made in the past is something that makes Red Hat unique we are excited to see red arts investment in leadership in open source technologies to help bring the potential of these amazing things together thank you that's great the thing you know seeing going from the old world to the new with automation so you know the things you've seen demonstrated today they're they're they're more sophisticated than any one company could ever have done on their own certainly not by using a proprietary development model because of this it's really easy to see why open source has become the center of gravity for enterprise computing today with all the progress open-source has made we're constantly looking for new ways of accelerating that into our products so we can take that into the enterprise with customers like these that you've met what you've met today now we recently made in addition to the Red Hat family we brought in core OS to the Red Hat family and you know adding core OS has really been our latest move to accelerate that innovation into our products this will help the adoption of open shift container platform even deeper into the enterprise and as we did with the Linux core platform in 2002 this is just exactly what we did with with Linux back then today we're announcing some exciting new technology directions first we'll integrate the benefits of automated operations so for example you'll see dramatic improvements in the automated intelligence about the state of your clusters in OpenShift with the core OS additions also as part of open shift will include a new variant of rel called Red Hat core OS maintaining the consistency of rel farhat for the operation side of the house while allowing for a consumption of over-the-air updates from the kernel to kubernetes later today you'll hear how we are extending automated operations beyond customers and even out to partners all of this starting with the next release of open shift in July now all of this of course will continue in an upstream open source innovation model that includes continuing container linux for the community users today while also evolving the commercial products to bring that innovation out to the enterprise this this combination is really defining the platform of the future everything we've done for the last 16 years since we first brought rel to the commercial market because get has been to get us just to this point hybrid cloud computing is now being deployed multiple times in enterprises every single day all powered by the open source model and powered by the open source model we will continue to redefine the software industry forever no in 2002 with all of you we made Linux the choice for enterprise computing this changed the innovation model forever and I started the session today talking about our prediction of seven years ago on the future being open we've all seen so much happen in those in those seven years we at Red Hat have celebrated our 25th anniversary including 16 years of rel and the enterprise it's now 2018 open hybrid cloud is not only a reality but it is the driving model in enterprise computing today and this hybrid cloud world would not even be possible without Linux as a platform in the open source development model a build around it and while we have think we may have accomplished a lot in that time and we may think we have changed the world a lot we have but I'm telling you the best is yet to come now that Linux and open source software is firmly driving that innovation in the enterprise what we've accomplished today and up till now has just set the stage for us together to change the world once again and just as we did with rel more than 15 years ago with our partners we will make hybrid cloud the default in the enterprise and I will take that bet every single day have a great show and have fun watching the future of computing unfold right in front of your eyes see you later [Applause] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] anytime [Music]