(upbeat music) >> Welcome back friends. It's theCUBE LIVE in Las Vegas at the Venetian Expo, covering the first full day of AWS re:Invent 2022. I'm Lisa Martin, and I have the privilege of working much of this week with Dave Vellante. >> Hey. Yeah, it's good to be with you Lisa. >> It's always good to be with you. Dave, this show is, I can't say enough about the energy. It just keeps multiplying as I've been out on the show floor for a few minutes here and there. We've been having great conversations about cloud migration, digital transformation, business transformation. You name it, we're talking about it. >> Yeah, and I got to say the soccer Christians are really happy. (Lisa laughing) >> Right? Because the USA made it through. So that's a lot of additional excitement. >> That's true. >> People were crowded around the TVs at lunchtime. >> They were, they were. >> So yeah, but back to data. >> Back to data. We have a couple of guests here. We're going to be talking a lot with customer challenges, how they're helping to overcome them. Please welcome Kevin Zawodzinski, VP of Sales Engineering at COMMVAULT. >> Thank you. >> And Paul Meighan, Director of Product Management at AWS. Guys, it's great to have you on the program. Thank you for joining us. >> Thanks for having us. >> Thanks for having us. >> Isn't it great to be back in person? >> Paul: It really is. >> Kevin: Hell, yeah. >> You cannot replicate this on virtual, you just can't. It's nice to see how excited people are to be back. There's been a ton of buzz on our program today about Adam's keynote this morning. Amazing. A lot of synergies with the direction, Paul, that AWS is going in and where we're seeing its ecosystem as well. Paul, first question for you. Talk about, you know, in the customer environment, we know AWS is very customer obsessed. Some of the main challenges customers are facing today is they really continue this business transformation, this digital transformation, and they move to cloud native apps. What are some of those challenges and how do you help them eradicate those? >> Well, I can tell you that the biggest contribution that we make is really by focusing on the fundamentals when it comes to running storage at scale, right? So Amazon S3 is unique, distributed architecture, you know, it really does deliver on those fundamentals of durability, availability, performance, security and it does it at virtually unlimited scale, right? I mean, you guys have talked to a lot of storage folks in the industry and anyone who's run an estate at scale knows that doing that and executing on those fundamentals day after day is just super hard, right? And so we come to work every day, we focus on the fundamentals, and that focus allows customers to spend their time thinking about innovation instead of on how to keep their data durably stored. >> Well, and you guys both came out of the storage world. >> Right. >> Yeah, yeah. >> It was a box world, (Kevin laughs) and it ain't no more. >> Kevin: That's right, absolutely. >> It's a service and a service of scale. >> Kevin: Yeah. So architecture matters, right? >> Yeah. >> Yeah. >> Paul, talk a little bit about, speaking of innovation, talk about the evolution of S3. It's been around for a while now. Everyone knows it, loves it, but how has AWS architected it to really help meet customers where they are? >> Paul: Right. >> Because we know, again, there's that customer first focus. You write the press release down the road, you then follow that. How is it evolving? >> Well, I can tell you that architecture matters a lot and the architecture of Amazon S3 is pretty unique, right? I think, you know, the most important thing to understand about the architecture of S3 is that it is truly a regional service. So we're laid out across a minimum of 3 Availability Zones, or AZs, which are physically separated and isolated and have a distance of miles between them to protect against local events like floods and fires and power interruption, stuff like that. And so when you give us an object, we distribute that data across that minimum of 3 Availability Zones and then within multiple devices within each AZ, right? And so what that means is that when you store data with us, your data is on storage that's able to tolerate the failure of multiple devices with no impact to the integrity of your data, which is super powerful. And then again, super hard to do when you're trying to roll your own. So that's sort of a, like an overview of the architecture. In terms of how we think about our roadmap, you know, 90% of our roadmap comes directly from what customers tell us matters, and that's a tenant of how we think about customer obsession at AWS and it really is how we drive a roadmap. >> Right, so speaking of customers Kevin, what are customers asking you guys- >> Yeah. >> for, how does it relate to what you're doing with S3? >> Yeah, it's a wonderful question and one that is actually really appropriate for us being at re:Invent, right? So we got, last three years we've had customers here with us on stage talking about it. First of all, 3 years ago we did a virtual session, unfortunately, but glad to be back as you mentioned, with Coca-Cola and theirs was about scale and scope and really about how can we protect hundreds of thousands of objects, petabyte to data, in a simple and secure way, right. Then last year we actually met with a ACT, Inc. as well and co-presented with them and really talked about how we could protect modern workloads and their modern workloads around whether it was Aurora or as well as EKS and how they continue to evolve as well. And, last but not least it's going to be, this year we're talking with Illinois State University as well about how they're going to continue to grow, adapt and really leverage AWS and ourselves to further their support of their teachers and their staff. So that is really helping us quite a bit to continue to move forward. And the things we're doing, again, with our customer base it's really around, focused on what's important to them, right? Customer obsession, how are we working with that? How are we making sure that we're listening to them? Again, working with AWS to understand how can we evolve together and really ultimately their journeys. As you heard, even with those 3 examples they're all very different, right? And that's the point, is that everybody's at a different point in the journey. They're at a different place from a modernization perspective. So we're helping them evolve, as they're helping us evolve as well, and transform with AWS. >> So very mature COMMVAULT stack, the S3 bucket and all the other capabilities. Paul, you just talked about coming together- >> Right. >> Dave: for your customers. >> Yeah, yeah, absolutely. And just, you know, we were talking the other day, Paul and I were talking the other day, it's been, you know, we've worked with AWS, with integration since 2009, right? So a long time, right? I mean, for some that may not seem like a long time ago, but it is, right? It's, you know, over a decade of time and we've really advanced that integration considerably as well. >> What are some of the things that, I don't know if you had a chance to see the keynote this morning? >> Yeah, a little bit. >> What are some of the things that there was, and in fact this is funny, funny data point for you on data. One of my previous guests told me that Adam Selipsky spent exactly 52 minutes talking about data this morning. 52 minutes. >> Okay. >> That there's a data point. But talk about some of the things that he talked about, the direction AWS is going in, obviously new era in the last year. Talk about what you heard and how you think that will evolve the COMMVAULT-AWS relationship. >> Yeah, I think part of that is about flexibility, as Paul mentioned too, architecture matters, right? So as we evolve and some of the things that we pride ourselves on is that we developed our systems and our software and everything else to not worry about what do I have to build to today but how do I continue to evolve with my customer base? And that's what AWS does, right? And continues to do. So that's really how we would see the data environment. It's really about that integration. As they grow, as they add more features we're going to add more features as well. And we're right there with them, right? So there's a lot of things that we also talk about, Paul and I talk about, around, you know, how do we, like Graviton3 was brought up today around some of the innovations around that. We're supporting that with Auto Scale right now, right? So we're right there releasing, right when AWS releasing, co-developing things when necessary as well. >> So let's talk about security a little bit. First of all, what is COMMVAULT, right? You're not a security company but you're an adjacency to security. It's sort of, we're rethinking security. >> Kevin: Yep. >> including data protection, not a bolt-on anymore. You guys both have a background in that world and I'm sure that resonates. >> Yeah. >> So what is the security play here? What role does COMMVAULT play? I think we know pretty well what role AWS plays, but love to hear, Paul, your thoughts as well on security. >> Yeah, I'll start I guess. >> Go on Paul. >> Okay. Yeah, so on the security side of things, there's a quite a few things. So again, on the development side of things, we do things like file anomaly detection, so seeing patterns in data. We talked a lot about analytics as well in the keynote this morning. We look at what is happening in the customer environment, if there's something odd or out of place that's happening, we can detect that and we'll notify people. And we've seen that, we have case studies about that. Other things we do are simple, simple but elegant. Is with our security dashboard. So we'll use our security dashboard to show best practices. Are they using Multi-Factor Authentication? Are you viewing password complexity? You know, things like that. And allows people to understand from a security landscape perspective, how do we layer in protection with their other systems around security. We don't profess to be the security company, or a security company, but we help, you know, obviously add in those additional layers. >> And obviously you're securing, you know, the S3 piece of it. >> Mmmhmm. >> You know, from your standpoint because building it in. >> That's right. And we can tell you that for us, security is job zero. And anyone at AWS will tell you that, and not only that but it will always be our top priority. Right from the infrastructure on down. We're very focused on our shared responsibility model where we handle security from the hypervisor, or host operating system level, down to the physical security of the facilities in which our services run and then it's our customer's responsibility to build secure applications, right. >> Yeah. And you talk about Graviton earlier, Nitro comes into play and how you're, sort of, fencing off, you know, the various components of the system from the operating system, the VMs, and then that is designed in and that's a new evolution that it comes as part of the package. >> Yeah, absolutely. >> Absolutely. >> Paul, talk a little bit about, you know, security, talking about that we had so many conversations this year alone about the threat landscape and how it's dramatically changing, it's top of mind for everybody. Huge rise in ransomware attacks. Ransomware is now, when are we going to get hit? How often? What's the damage going to be? Rather than, are we going to get hit? It's, unfortunately it's progressed in that direction. How does ensuring data security impact how you're planning the roadmap at AWS and how are partners involved in shaping that? >> Right, so like I said, you know, 90% of our roadmap comes from what customers tell us matters, right? And clearly this is an issue that matters very much to customers right now, right? And so, you know, we're certainly hearing that from customers, and COMMVAULT, and partners like COMMVAULT have a big role to play in helping customers to secure and protect their applications, right? And that's why it's so critical that we come together here at re:Invent and we have a bunch of time here at the show with the COMMVAULT technical folks to talk through what they're hearing from customers and what we're hearing. And we have a number of regular touch points throughout the year as well, right? And so what COMMVAULT gets from the relationship is, sort of, early access and feedback into our features and roadmap. And what we get out of it really is that feedback from that large number of customers who interface with Amazon S3 through COMMVAULT. Who are using S3 as a backup target behind COMMVAULT, right? And so, you know, that partnership really allows us to get close to those customers and understand what really matters to them. >> Are you doing joint engineering, or is it more just, hey here you go COMMVAULT, here's the tools available, go, go build. Can you address that? >> Yeah, no, absolutely. There's definitely joint engineering like even things around, you know, data migration and movement of data, we integrate really well and we talk a lot about, hey, what are you, like as Paul mentioned, what are you seeing out there? We actually, I just left a conversation about an hour ago where we're talking about, you know, where are we seeing placement of data and how does that matter to, do you put it on, you know, instant access, or do you put it on Glacier, you know, what should be the best practices? And we tell them, again, some of the telemetry data that we have around what do we see customers doing, what's the patterns of data? And then we feed that back in and we use that to create joint solutions as well. >> You know, I wonder if we could talk about cloud, you know, optimization of cloud costs for a minute. That's obviously a big discussion point in the hallways with customers. And on your earnings call you guys talked about specifically some customers and they specifically mentioned, for example, pushing storage to lower cost tiers. So you brought up Glacier just then. What are you seeing in the field in that regard? How are customers taking advantage of that? And where does COMMVAULT play in, sort of, helping make that decision? >> You want to take part one or you want me to take it? >> I can take part one. I can tell you that, you know, we're very focused on helping customers optimize costs, however necessary, right? And, you know, we introduced intelligent hearing here at the show in 2019 and since launch it's helped customers to reduce costs by over $750 million, right? So that's a real commitment to optimizing costs on behalf of customers. We also launched, you know, later in 2020, Glacier Deep Archive, which is the lowest cost storage in the cloud. So it's an important piece of the puzzle, is to provide those storage options that can allow customers to match the workloads that are, that need to be on folder storage to the appropriate store. >> Yeah, and so, you know, S3 is not this, you know, backup and recovery system, not an archiving system and, you know, in terms of, but you have that intelligence in your platform. 'Cause when I heard that from the earnings call I was like, okay, how do customers then go about deciding what they can, you know, when it's all good times, like yeah, who cares? You know, just go, go, go. But when you got to tighten the belt, how do you guys? >> Yeah, and that goes back to understanding the data pattern. So some of that is we have intelligence and artificial intelligence and everything else and machine learning within our, so we can detect those patterns, right? We understand the patterns, we learn from that and we help customers right size, right. So ultimately we do see a blend, right? As Paul mentioned, we see, you know, hey I'm not going to put everything on Glacier necessarily upfront. Maybe they are, it all depends on their workloads and patterns. So we use the data that we collect from the different customers that we have to share those best practices out and create, you know, the right templates, so to speak, in ways for people to apply it. >> Guys, great joint, you talked about the joint engineering, joint go to market, obviously a very strong synergistic partnership between the two. A lot of excitement. This is only day one, I can only imagine what's going to be coming the next couple of days. But I have one final question for you, but I have same question for both of you. You had the chance to create your own bumper sticker, so you get a shiny new car and for some reason you want to put a bumper sticker on it. About COMMVAULT, what would it say? >> Yeah, so for me I would say comprehensive, yet simple, right? So ultimately about giving you all the bells and whistles but if you want to be very simple we can help you in every shape and form. >> Paul, what's your bumper sticker say about AWS? >> I would say that AWS starts with the customer and works backwards from there. >> Great one. >> Excellent. Guys- >> Kevin: Well done. >> it's been a pleasure to have you on the program. Thank you- >> Kevin: Thank you. >> for sharing what's going on, the updates on the AWS-COMMVAULT partnership and what's in it for customers. We appreciate it. >> Dave: Thanks you guys. >> Thanks a lot. >> Thank you. >> All right. For our guests and Dave Vellante, I'm Lisa Martin. You're watching theCUBE, the leader in live enterprise and emerging tech coverage. (upbeat music)

(bright upbeat music) >> Hello, and welcome back to the DockerCon 2021 virtual coverage. I'm John Furrie host of theCUBE here in Palo Alto with a remote interview with a great guest Cuban alumni, Jim Walker VP of Product Marketing at Cockroach Labs. Jim, great to see you remotely coming into theCUBE normally we're in person, soon we'll be back in real life. Great to see you. >> Great to see you as well John, I miss you. I miss senior live and in person. So this has got to do, I guess right? >> We we had the first multi-cloud event in New York city. You guys had was I think one of the last events that was going on towards the end of the year before the pandemic hit. So a lot's happened with Cockroach Labs over the past few years, accelerated growth, funding, amazing stuff here at DockerCon containerization of the world, containers everywhere and all places hybrid, pure cloud, edge everywhere. Give us the update what's going on with Cockroach Labs and then we'll get into what's going on at DockerCon. >> Yeah Cockroach Labs, this has been a pretty fun ride. I mean, I think about two and a half years now and John it's been phenomenal as the world kind of wakes up to a distributed systems and the containerization of everything. I'm happy we're at DockerCon talking about containerization 'cause I think it has radically changed the way we think about software, but more importantly it's starting to take hold. I think a lot of people would say, oh, it's already taken hold but if you start to think about like just, these kind of modern applications that are depending on data and what does containerization mean for the database? Well, Cockroach has got a pretty good story. I mean, gosh, before Escape I think the last time I talked to you, I was at CoreOS and we were playing the whole Kubernetes game and I remember Alex Povi talking about GIFEE Google infrastructure for everyone or for everyone else I should say. And I think that's what we've seen that kind of happened with the infrastructure layer but I think that last layer of infrastructure is the database. Like I really feel like the database is that dividing line between the business logic and infrastructure. And it's really exciting to see, just massive huge customers come to Cockroach to rethink what the database means in cloud, right? What does the database mean when we moved to distributed systems and that sort of thing, and so, momentum has been building here, we are, upwards of, oh gosh, over 300 paying customers now, thousands of Cockroach customers in the wild out there but we're seeing this huge massive attraction to CockroachCloud which is a great name. Come on, Johnny, you got to say, right? And our database as a service. So getting that out there and seeing the uptake there has just been, it's been phenomenal over the past couple of years. >> Yeah and you've got to love the Cockroach name, love it, survive nuclear war and winter all that good stuff as they say, but really the reality is that it's kind of an interesting play on words because one of the trends that we've been talking about, I mean, you and I've been telling this for years with our CUBE coverage around Amazon Web Services early on was very clear about a decade ago that there wasn't going to be one database to rule the world. They're going to many, many databases. And as you started getting into these cloud native deployments at scale, use your database of choice was the developer ethos just whatever it takes to get the job done. Now you start integrating this in a horizontally scalable way with the cloud, you have now new kinds of scale, cloud scale. And it kind of changed the game on the always on availability question which is how do I get high availability? How do I keep things running? And that is the number one developer challenge whether it's infrastructure as code, whether it's security shifting left, it all comes down to making sure stuff's running at scale and secure. Talk about that. >> Yeah, absolutely and it's interesting it's been, like I said, this journey in this arc towards distributed systems and truly like delivery of what people want in the cloud, it's been a long arc and it's been a long journey and I think we're getting to the point where people, they are starting to kind of bake resilience and scale into their applications and I think that's kind of this modern approach. Look we're taking legacy databases today. There are people are kind of lift and shift, move them into the cloud, try to run them there but they aren't just built for that infrastructure like the there's a fundamentally different approach and infrastructure when it talks, when you talk about cloud it's one of the reasons why John early on your conversations with the AWS Team and what they did, it's like, yeah, how do we give resilient and ubiquitous and always on scalable kind of infrastructure people. Well, that's great for those layers but when you start to get into the software that's running on these things, it isn't lift and shift and it's not even move and improve. You can't like just take a legacy system and change one piece of it to make it kind of take advantage of the scale and the resilience and the ubiquity of the cloud, because there's very very explicit challenges. For us, it's about re-architect and rebuild. Let's tear the database down and let's rethink it and build from the ground up to be cloud native. And I think the technologies that have done that, that have kind of built from scratch, to be cloud native are the ones that are I believe, three years from now that's what we're going to be talking about. I mean, this comes back to again, like the Genesis of what we did is Google Cloud Spanner. Spanner white paper and what Google did, they didn't build, they didn't use an existing database because they needed something for a transactional relational database. They hire a bunch of really incredible engineers, right? And I got like Jeff Dean and Sanjay Ghemawat over there, like designing and doing all these cool things, they build and I think that's what we're seeing and I think that's, to me the exciting part about data in the cloud as we move forward. >> Yeah, and I think the Google cloud infrastructure, everyone I think that's the same mindset for Amazon is that I want all the scale, but I don't want to do it like over 10 years I to do it now, which I love I want to get back to in a second, but I want to ask you specifically this definition of containerization of the database. I've heard that kicked around, love the concept. I kind of understand what it means but I want you to define it for us. What does it mean when someone says containerizing the database? >> Yeah, I mean, simply put the database in container and run it and that's all that I can think that's like, maybe step one I think that's kind of lift and shift. Let's put it in a container and run it somewhere. And that's not that hard to do. I think I could do that. I mean, I haven't coded in a long time but I think I could figure that out. It's when you start to actually have multiple instances of a container, right? And that's where things get really, really tricky. Now we're talking about true distributed systems. We're talking about how do you coordinate data? How do you balance data across multiple instances of a database, right? How do you actually have fail over so that if one node goes down, a bunch of them are still available. How do you guarantee transactional consistency? You can't just have four instances of a database, all with the same information in it John without any sort of coordination, right? Like you hit one node and you hit another one in the same account which transaction wins. And so the concepts in distributed systems around there's this thing called the cap theorem, there's consistency, availability, and partition tolerance and actually understanding how these things work especially for data in distributed systems, to make sure that it's going to be consistent and available and you're going to scale those things are not simple to solve. And again, it comes back to this. I don't think you can do it with legacy database. You kind of have to re-architect and it comes down to where data is stored, it comes down to how it's replicated, it comes down to really ultimately where it's physically located. I think when you deploy a database you think about the logical model, right? You think about tables, and normalization and referential integrity. The physical location is extremely important as we kind of moved to that kind of containerized and distributed systems, especially around data. >> Well, you guys are here at DockerCon 2021 Cockroach Labs good success, love the architectural flexibility that you guys offer. And again, bringing that scale, like you mentioned it's awesome value proposition, especially if people want to just program the infrastructure. What's going on with with DockerCon specifically a lot of talk about developer productivity, a lot of talk about collaboration and trust with containers, big story around security. What's your angle here at DockerCon this year? What's the big reveal? What's the discussion? What's the top conversation? >> Yeah, I mean look at where we are a containerized database and we are an incredibly great choice for developers. For us, it's look at there's certain developer communities that are important on this planet, John, and this is one of them, right? This is I don't know a developer doesn't have that little whale up in their status bar, right? And for us, you know me man, I believe in this tech and I believe that this is something that's driven and greatly simplify our lives over the next two to three to 10 to 15 years. And for us, it's about awareness. And I think once people see Cockroach, they're like oh my God, how did I ever even think differently? And so for us, it's kind of moving in that direction. But ultimately our vision where we want to be, is we want to abstract the database to a SQL API in the cloud. We want to make it so simple that I just have this rest interface, there's end points all over the planet. And as a developer, I never have to worry about scale. I never have to worry about DR right? It's always going to be on. And most importantly, I don't have to worry about low latency access to data no matter where I'm at on the planet, right? I can give every user this kind of sub 50 millisecond access to data or sub 20 millisecond access to data. And that is the true delivery of the cloud, right? Like I think that's what the developer wants out of the cloud. They want to code against a service like, and it's got to be consumption-based and you secure and I don't want to have to pay for stuff I'm not using and that all those things. And so, for us, that's what we're building to, and interacting in this environment is critical for us because I think that's where audiences. >> I want to get your thoughts on you guys do have success with a couple of different personas and developers out there, groups, classic developers, software developers which is this show is that DockerCon full of developers KubeCon a lot of operators cool, and some dads, but mostly cloud native operations. Here's a developer shops. So you guys got to hit the developers which really care about building fast and building the scale and last with security. Architects you had success with, which is the classic, cloud architecture, which now distributed computing, we get that. But the third area I would call the kind of the role that both the architects and the developers had to take on which is being the DevOps person or then becomes the SRE in the group, right? So most startups have the DevOps team developers. They do DevOps natively and within every role. So they're the same people provisioning. But as you get larger and an enterprise, the DevOps role, whether it's in a team or group takes on this SRE site reliability engineer. This is a new dynamic that brings engineering and coding together. It's like not so much an ops person. It's much more of like an engineering developer. Why is that role so important? And we're seeing more of it in dev teams, right? Seeing an SRE person or a DevOps person inside teams, not a department. >> Yeah, look, John, we, yeah, I mean, we employ an army of SREs that manage and maintain our CockroachCloud, which is CockroachDB as a service, right? How do you deliver kind of a world-class experience for somebody to adopt a managed service a database such as ours, right? And so for us, yeah I mean, SREs are extremely important. So we have personal kind of an opinion on this but more importantly, I think, look at if you look at Cockroach and the architecture of what we built, I think Kelsey Hightower at one point said, I am going to probably mess this up but there was a tweet that he wrote. It's something like, CockroachDB is the Spanner as Kubernetes is the board. And if you think about that, I mean that's exactly what this is and we built a database that was actually amenable to the SRE, right? This is exactly what they want. They want it to scale up and down. They want it to just survive things. They want to be able to script this thing and basically script the world. They want to actually, that's how they want to manage and maintain. And so for us, I think our initial audience was definitely architects and operators and it's theCUBE con crowd and they're like, wow, this is cool. This is architected just like Kubernetes. In fact, like at etcd, which is a key piece of Kubernetes but we contribute back up to NCD our raft implementation. So there's a lot of the same tech here. What we've realized though John, with database is interesting. The architect is choosing a database sometimes but more often than not, a developer is choosing that database. And it's like they go out, they find a database, they just start building and that's what happens. So, for us, we made a very critical decision early on, this database is wire compatible with Postgres and it speaks to SQL syntax which if you look at some of the other solutions that are trying to do these things, those things are really difficult to do at the end. So like a critical decision to make sure that it's amenable so that now we can build the ORMs and all the tools that people would use and expect that of Postgres from a developer point of view, but let's simplify and automate and give the right kind of like the platform that the SREs need as well. And so for us the last year and a half is really about how do we actually build the right tooling for the developer crowd too. And we've really pushed really far in that world as well. >> Talk about the aspect of the scale of like, say startup for instance, 'cause you made this a great example borg to Kubernetes 'cause borg was Google's internal Kubernetes, like thing. So you guys have Spanner which everyone knows is a great product at Google had. You guys with almost the commercial version of that for the world. Is there, I mean, some people will say and I'll just want to challenge you on this and we'll get your thoughts. I'm not Google, I'll never be Google, I don't need that scale. Or so how do you address that point because some people say, well this might dismiss the notion of using it. How do you respond to that? >> Yeah, John, we get this all the time. Like, I'm not global. My application's not global. I don't need this. I don't need a tank, right? I just need, like, I just need to walk down the road. You know what I mean? And so, the funny thing is, even if you're in a single region and you're building a simple application, does it need to be always on does it need to be available. Can it survive the failure of a server or a rack or an AZ it doesn't have to survive the failure of a region but I tell you what, if you're successful, you're going to want to start actually deploying this thing across multiple regions. So you can survive a backhoe hit in a cable and the entire east coast going out, right? Like, and so with Cockroach, it's real easy to do that. So it's four little SQL commands and I have a database that's going to span all those regions, right? And I think that's important but more importantly, think about scale, when a developer wants to scale, typically it's like, okay, I'm going to spin up Postgres and I'm going to keep increasing my instance size. So I'm going to scale vertically until I run out of room. And then I'm going to have to start sharding this database. And when you start doing that, it adds this kind of application complexity that nobody really wants to deal with. And so forget it, just let the database deal with all that. So we find this thing extremely useful for the single developer in a very small application but the beauty thing is, if you want to go global, great just keep that in notes. Like when that application does take off and it's the next breakthrough thing, this database going to grow with you. So it's good enough to kind of start small but it's the scale fast, it'll go global if you want to, you have that option, I guess, right? >> I mean, why wouldn't you want optionality on this at all? So clearly a good point. Let me ask you a question, take me through a use case where with Cockroach, some scenario develops nicely, you can point to the visibility of the use case for the developer and then kind of how it played out and then compare that and contrast that to a scenario that doesn't go well, like where where we're at plays out well, for an example, and then if they didn't deploy it they got hung up and went sideways. >> Yeah like Cockroach was built for transactional workloads. That that's what we are like, we are optimized for the speed of light and consistent transactions. That's what we do, and we do it very well. At least I think so, right. But I think, like my favorite customer of all of ours is DoorDash and about a year ago DoorDash came to us and said, look at we have a transactional database that can't handle the right volume that we're getting and falls over. And they they'd significant challenges and if you think about DoorDash and DoorDash is business they're looking at an IPO in the summer and going through these, you can't have any issues. So like system's got to be up and running, right? And so for them, it was like we need something that's reliable. We need something that's not going to come down. We need something that's going to scale and handle burst and these sort of things and their business is big, their businesses not just let me deliver food all the time. It's deliver anything, like be that intermediary between a good and somebody's front door. That's what DoorDash wants to be. And for us, yeah, their transactions and that backend transactional system is built on Cockroach. And that's one year ago, they needed to get experienced. And once they did, they started to see that this was like very, very valuable and lots of different workloads they had. So anywhere there's any sort of transactional workload be it metadata, be it any sort of like inventory, or transaction stuff that we see in companies, that's where people are coming to us. And it's these traditional relational workloads that have been wrapped up in these transactional relational databases what built for the cloud. So I think what you're seeing is that's the other shoe to drop. We've seen this happen, you're watching Databricks, you're watching Snowflake kind of do this whole data cloud and then the analytical side John that's been around for a long time and there's that move to the cloud. That same thing that happened for OLAP, is got to happen for OLTP. Where we don't do well is when somebody thinks that we're an analytic database. That's not what we're built for, right? We're optimized for transactions and I think you're going to continue to see these two sides of the world, especially in cloud especially because I think that the way that our global systems are going to work you don't want to do analytics across multiple regions, it doesn't make sense, right? And so that's why you're going to see this, the continued kind of two markets OLAP and OLTP going on and we're just, we're squaring that OLTP side of the world. >> Yeah talking about the transaction processing side of it when you start to change a distributed architecture that goes from core edge, core on premises to edge. Edge being intelligent edge, industrial edge, whatever you're going to have more action happening. And you're seeing, Kubernetes already kind of talking about this and with the containers you got, so you've got kind of two dynamics. How does that change the nature of, and the level of volume of transactions? >> Well, it's interesting, John. I mean, if you look at something like Kubernetes it's still really difficult to do multi-region or multicloud Kubernetes, right? This is one of those things that like you start to move Kubernetes to the edge, you're still kind of managing all these different things. And I think it's not the volumes, it's the operational nightmare of that. For us, that's federate at the data layer. Like I could deploy Cockroach across multiple Kubernetes clusters today and you're going to have one single logical database running across those. In fact you can deploy Cockroach today on top of three public cloud providers, I can have nodes in AWS, I could have nodes in GCP, I could have nodes running on VMs in my data center. Any one of those nodes can service requests and it's going to look like a single logical database. Now that to me, when we talked about multicloud a year and a half ago or whatever that was John, that's an actual multicloud application and delivering data so that you don't have to actually deal with that in your application layer, right? You can do that down in the guts of the database itself. And so I think it's going to be interesting the way that these things gets consumed and the way that we think about where data lives and where our compute lives. I think that's part of what you're thinking about too. >> Yeah, so let me, well, I got you here. One of the things on my mind I think people want to maybe get clarification on is real quick while you're here. Take a minute to explain that you're seeing a CockroachDB and CockroachCloud. There are different products, you mentioned you've brought them both up. What's the difference for the developers watching? What's the difference of the two and when do I need to know the difference between the two? >> So to me, they're really one because CockroachCloud is CockroachDB as a service. It's our offering that makes it a world-class easy to consume experience of working with CockroachDB, where we take on all the hardware we take on the SRE role, we make sure it's up and running, right? You're getting connection, stringing your code against it. And I think, that's side of our world is really all about this kind of highly evolved database and delivering that as a service and you can actually use it's CockroachDB. I think it was just gets really interesting John is the next generation of what we're building. This serverless version of our database, where this is just an API in the cloud. We're going to have one instance of Cockroach with multi-tenant database in there and any developer can actually spin up on that. And to me, that gets to be a really interesting world when the world turns serverless, and we have, we're running our compute in Lambda and we're doing all these great things, right? Or we're using cloud run and Google, right? But what's the corresponding database to actually deal with that? And that to me is a fundamentally different database 'cause what is scale in the serverless world? It's autonomous, right? What scale in the current, like Cockroach world but you kind of keep adding nodes to it, you manage, you deal with that, right? What does resilience mean in a serverless world? It's just, yeah, its there all the time. What's important is latency when you get to kind of serverless like where are these things deployed? And I think to me, the interesting part of like the two sides of our world is what we're doing with serverless and kind of this and how we actually expose the core value of CockroachDB in that way. >> Yeah and I think that's one of the things that is the Nirvana or the holy grail of infrastructure as code is making it, I won't say irrelevant, but invisible if you're really dealing with a database thing, hey I'm just scaling and coding and the database stuff is just working with compute, just whatever, how that's serverless and you mentioned Lambda that's the action because you don't want the file name and deciding what the database is just having it happen is more productivity for the developers that kind of circles back to the whole productivity message for the developers. So I totally get that I think that's a great vision. The question I have for you Jim, is the big story here is developer simplicity. How you guys making it easier to just deploy. >> John is just an extension of the last part of the conversation. I don't want to developer to ever have to worry about a database. That's what Spencer and Peter and Ben have in their vision. It's how do I make the database so simple? It's simple, it's a SQL API in the cloud. Like it's a rest interface, I code against it, I run queries against it, I never have to worry about scaling the thing. I never have to worry about creating active, passive, and primary and secondary. All these like the DevOps side of it, all this operation stuff, it's just kind of done in the background dude. And if we can build it, and it's actually there now where we have it in beta, what's the role of the cost-based optimizer in this new world that we've had in databases? How are you actually ensuring data is located close to users and we're automating that so that, when John's in Australia doing a show, his data is going to follow him there. So he has fast access to that, right? And that's the kind of stuff that, we're talking about the next generation of infrastructure John, not like we're not building for today. Like, look at Cockroach Labs is not building for like 2021. Sure, do we have something that's great. We're building something that's 22 and 23 and 24, right? Like what do we need to be as a extremely productive set of engineers? And that's what we think about all day. How do we make data easy for the developer? >> Well, Jim, great to have you on VP of Product Marketing at Cockroach Labs, we've known each other for a long time. I got to ask you while I had got you here final question is, you and I have chatted about the many waves of in open source and in the computer industry, what's your take on where we are now. And I see you're looking at it from the Cockroach Labs perspective which is large scale distributed computing kind of you're on the new side of history, the right side of history, cloud native. Where are we right now? Compare and contrast for the folks watching who we're trying to understand the importance of where we are in the industry, where are we in and what's your take? >> Yeah John I feel fortunate to be in a company such as this one and the past couple that I've like been around and I feel like we are in the middle of a transformation. And it's just like the early days of this next generation. And I think we're seeing it in a lot of ways in infrastructure, for sure but we're starting to see it creep up into the application layer. And for me, it is so incredibly exciting to see the cloud was, remember when cloud was like this thing that people were like, oh boy maybe I'll do it. Now it's like, it's anything net new is going to be on cloud, right? Like we don't even think twice about it and the coming nature of cloud native and actually these technologies that are coming are going to be really interesting. I think the other piece that's really interesting John is the changing role of open source in this whole game, because I think of open source as code consumption and community, right? I think about those and then there's license of course, I think people were always there. A lot of people wrapped around the licensing. Consumption has changed, John. Back when we were talking to Dupe, consumption was like, oh, it's free, I get this thing I could just download it use it. Well consumption over the past three years, everybody wants everything as a service. And so we're ready to pay. For us, how do we bring free back to the service? And that's what we're doing. That's what I find like I am so incredibly excited to go through this kind of bringing back free beer to open source. I think that's going to be great 'cause if I can give you a database free up to five gig or 10 gig, man and it's available all over the planet has fully featured, that's coming, that's bringing our community and our code which is all open source and this consumption model back. And I'm super excited about that. >> Yeah, free beer who doesn't like free beer of course, developers love free beer and a great t-shirt too that's soft. Make sure you get that, get the soft >> You just don't want free puppy, you know what I mean? It was just like, yeah, that sounds painful. >> Well Jim, great to see you remotely. Can't wait to see you in person at the next event. And we've got the fall window coming up. We'll see some events. I think KubeCon in LA is going to be in-person re-invent a data breast for sure we'll be in person. I know that for a fact we'll be there. So we'll see you in person and congratulations on the work at Cockroach Labs. >> Thanks, John, great to see you again. All right, this keep coverage of DockerCon 2021. I'm John Furrie your host of theCUBE. Thanks for watching.

(upbeat music) >> Hello everyone, and welcome to this Cube conversation. We're going to dig into some of the more specific and sometimes gory details of managing the nuances of database, database management systems. You know, it's a lot of fun to get it to the daily buzz of cloud and database competition and get a little snarky on Twitter, but there are a lot of mundane issues that you have to address to really do proper database sizing, capacity planning, and you know whether or not database consolidation makes sense. These are not trivial issues. And decades ago they spawned an entire role around the database administrator. They had to do the dirty work of database management so that users and customers would be satisfied. And while automation and cloud are changing that role, at the end of the day, somebody actually has to make the databases work in the cloud and make sure that the business doesn't feel any impact on the transition along the way. So on that note, we have with us Oracle senior director of product management for mission critical databases. He works in Juan Loaiza's group, Chris Craft, and Steve Zivanic whom we know well on the cube says this guy is the Jedi master when it comes to consolidating databases in the cloud. Nobody knows more on the face of the planet Earth. So we're really excited Chris, to have you inside the Cube. Welcome. >> Thanks, thanks Dave. >> That's a very humble thanks. So when it comes to running databases in the cloud can you explain the difference between sizing and capacity planning? Aren't they two sides of the same coin? >> Yeah, you know, they really are. It's like, you know sizing is really part of capacity to planning. It's really, I look at sizing as a one-time effort whereas capacity planning is more your ongoing. You perform sizing initially when the application is deployed. And then, then when you're changing platforms, like going from on-prem to the Cloud you're going to go through a sizing exercise 'cause you're looking at going to a new platform. That's more of a one-time effort, and then ongoing, you're looking at your capacity management over time. So yeah, they are very related so. >> Okay, thank you. So we're going to talk about database consolidation. A lot of people would say, look the cloud makes consolidating databases maybe not irrelevant, but maybe not the best strategy because I got all these different purpose-built databases. Why consolidate databases if they're already going to consolidate it in the cloud in one location? >> Yeah. So, so we're really talking about in in the cloud, you're running virtual machines but consolidation still applies on the virtual machines. So if you have a virtual machine that's dedicated to a database that database is that server, that virtual machine is going to be under utilized over time. So what we're doing with consolidation is running multiple databases within a virtual machine or what it, Oracle virtual cluster. We do everything on clusters. So multiple machines multiple databases within that will drive up the utilization and improve your cost structure. So it's a sizing it's it's absolutely critical on even in the cloud. >> Okay. But, but wouldn't it, I might say to that, wouldn't it be better to have each database have a dedicated VM? I mean, from a performance perspective, it doesn't try to make the database do too much affect performance. >> Yeah. It, so whenever, so we know historically that a database on a dedicated server back in the day that was a physical server, today it's a virtual machine. When you do that, your utilization will be in the range of 15 to 20%. And that's, you know very highly under utilized systems when you do that. So we don't need to isolate things onto dedicated virtual machines for a performance perspective. There are other ways that we can manage that we have resource management built into Oracle and the Oracle database. And then on Exadata we have an integrated IO resource management as well so we can deal with that different ways. >> Okay. So you're basically proposing that you're putting these databases onto a single VM and managing it accordingly. Is there additional details you can provide on that? >> So, you know, we don't put everything into you know, literally one, one VM. You want to have some isolation built in there, but see and take a more pragmatic approach. You know, like every single database in one VM that's the wrong way to go. Each database in a dedicated VM is also the other extreme, also the wrong way to go. So we're kind of right down the middle and be more pragmatic about it, and do some level of consolidation to drive up utilization. >> I remember when I first started following tech I was studying up on, you know kind of how disc drives work and so forth. And there was probably like I can't even remember what it was. It was like probably like 10 megabytes under an actuator. And people were saying, Oh my God, that's so much data. You, you got your blast radius is, is so big. You got to split that up. So it's the same concept, apply with availability. Some would say, there's a problem because you're consolidating all this data and you've got this blast radius that increases. How do you address that? >> And so, you know, redundancy. So we have redundancy at all levels. So if you look at a single, so we're talking about Exadata here, taught in an Exadata machine we can lose up to 24 disc drives out of 30. 30 machines with 36 disc drives, we can use 24 of those. So that'd be 12 per storage cell. You can lose two storage cells as 24 out of 36 drives so we can lose and keep on running. We can also, we also cluster, we also do clustering. So the database servers are clustered together for high availability. So we can take, we can suffer multiple simultaneous failures and keep on running without performance impact either. So it's, so recovery, we handle that in different ways. So it's, look at blast radius from a standpoint, you want some, some isolation for blast radius but we have physical failures is just not something that we're concerned with. >> Why do you deal with taking down a VM? Doesn't that normally mean there's going to be some kind of disruption? >> Oh, so you know, the, so Oracle database, you're talking about real application clusters on on Oracle database, on Exadata. We've got, we have a very fast detection of of failures and then resolution of the failure. So we're looking at a small blip in performance, you know we're looking at a few milliseconds to detect failure and then maybe up around three seconds to actually affect the failover. So the applications that are not getting disconnected, they continue operating in the, in that kind of condition. So that's kind of unique to the Exadata platform. And so, you know, in our cloud, we're running Exadata. We have this built in there. So we're, we're resilient to that type of failure, so. >> And sorry, you mentioned real application clusters. You're saying because you're running real application clusters that's how you're able to become more resilient? >> So yeah, so we have, so Oracle database real application clusters runs on top of a clustered virtual machines on Exadata. We have integration then optimizes the fail over times of that clustering. So it's, it's not the cluster same, it's the optimizations are only built into Exadata. So we have much much faster, much better tighter integration, so much more scalability because of that, that integration that we have. >> Can I run rack in other clouds? Can I put that into Amazon's cloud? >> So, so real application clusters requires two things. It's a, you require shared storage in a fast interconnect, a fast networking interconnecting. And those things just don't exist in the other clouds. We have those built into Exadata in our cloud. And we also, we also allow real application clusters in our relational database, our database cloud service offering as well. But it's, really the highest implementation of that is in Exadata. >> Well, of course I was tongue in cheek joking but this is, this is why, you know, I was listening to Arvind Krishna the other day in IBM Think. And he was saying only 25% of mission critical applications have moved into the cloud. I didn't think it's that high. I mean, but, but what you're doing is basically building a mission critical, you know, cloud or a cloud for mission critical databases. And that's, that's unique. I mean, I would expect other cloud vendors that eventually you know, are going to get there, but you're kind of starting with the hard stuff and working backwards. But, that is what I've always interpreted is unique to Oracle, but how does that affect cost? Isn't that more expensive? >> Actually, no. We're taking services that that start out at a very similar price point. And then we drive. So what we've seen from other customers that are running in like Amazon, for example, we see databases on dedicated virtual machines that run anywhere from 15 to 20% utilization. So what we do is, that low, low utilization, what we do is take that and triple that. So we run, so we run maybe 50% utilization. At that point we still have full redundancy, but we've now made the service one third of the cost. So we're starting at a third, we're starting at a very similar cost. And then we drive it to, you know three times a utilization. This is not crazy numbers. This is, you know, 50% is, is fine and retain the redundancy at that level as well. >> Got it, well so. >> What we've seen is about a third the cost. >> Really? Okay. Well, so, but, what about, like for instance, on AWS, couldn't I run this in a multi availability zone, running RDS or some other cloud database? >> So, so you can run a Multi-AZ environment like in in Amazon, for example, you can run locals. That's what we call local standby. If you do that, you're now instead of being one third, instead of being three times more expensive, you're now six times more expensive. Because that is another copy of the entire platform, the entire instance, the storage, everything on the other availability zone instead of being three times more, it's now six. >> Because you're essentially replicating everything in a brute force mode, right? >> Yeah. It's a data guard standby, local standby in another AZ, or what we call availability domain in our cloud. >> So let's maybe geek out a little bit. So, let's talk more about availability. You know, for years, I mean, I remember going back to reading about this stuff with tandem computers, you know, coincident failures. How are you dealing with those in today's modern world? >> So what we call simultaneous failures is, so we, we deal with that with redundancy in the system. So we have redundancy at all layers in the storage. Like I said earlier, we can take across, you know, two storage cells and each storage cell has a dozen drives. So that's 24 disc drives. That's eight flashcard failures simultaneously. And we keep on running no data loss, no loss of service. That's at the storage layer. We have multiple, multiple redundant networking switches at that, at the networking layer, the internal network. Then we go up into the database server. We then have redundancy across the nodes of a cluster. You have multiple virtual machines that comprise a virtual cluster. So it's at each and every level, we have redundancy. And then we drive the redundancy into the application using what's called application continuity. So the application connections have knowledge of the failure, failure modes of the database. They can follow to the surviving node, and continue operating. >> And you do this with math, you're doing some kind of magic bit slicing, or how do you do that? >> That, so that is that particular thing, application continuity, so technology that's been built into Oracle database since, since 12c, and that it's been around for quite a long time. And it allows the application to follow the rack cluster, any kind of issues with the rack cluster. We can drain connections off. It's very well-proven technology in, you know, prior to to proactive maintenance, we can drain connections over and then it will also handle a failure of a connection as well. And the application following that, yes. >> I learned from my old mainframe days and hanging around with David Floyer. It's always ask, what happens when something goes wrong and it's all about recovery. And you guys have the gold standard there. I mean, we've talked about this a lot. So you got Exadata. That's what is behind your Exadata cloud service, X8M I think you call it, and you've got autonomous database. I'm not great with model numbers, but, but talk about the way you can handle simultaneous failures. I mean, are there like triple redundancies that you've built in? >> Yeah. So everything what we do in our cloud is everything is triple redundancy by default. So we, you can suffer, that way we can suffer two failures and continue operating. So the, the other thing, so recovery, if you look at transaction recovery, when a failure occurs a transaction will flip that session, will flip to the machine that keeps running. It'll reposition all in the work that's in flight, any kind of inflight transactions, any in flight queries that are going on, reposition and continue operating. >> So you've essentially created like the old three site data centers, but you're in a single platform because you're synchronous. But, that same concept in a package. >> It's, you know, it's a lot of times you show a picture of an Exadata. It looks like a single box, but in the box there's some redundancy built in the box. And in fact, in the cloud it's actually across an entire aisle. So it's, we kind of obscure that a little bit, from your provisioning, you know, our database nodes and our storage cells and in the cloud but it's actually across an entire aisle of a dataset. >> Okay, and of course, that's within a synchronous location. Let's talk about disaster recovery, and what you're doing in that area, around Oracle Cloud What are my options there? What's different from other cloud providers we were talking earlier about, AZs, how are you different and what are you doing there? >> Yeah, so we, we talked earlier about the Multi-AZ deployment, what we call it availability domain, AD, so a little different terminology. But we can deploy another, another copy of the database into another availability domain, if you like. It's not often that you lose an entire AZ or AD, it's more, we're protecting from regional failures. So across another region. And that's where we look at, we really look at that as that technology, as a standby, as a data, disaster recovery solution not for HA. HA, we build HA into the machine itself. >> So you're saying, we were talking earlier about AZ, you're saying that's for HA versus DR. Is that, is that what you're contending? >> Yeah, like, you know again, pick on Amazon for a second here. Amazon uses a standby database. What we would normally use for disaster recovery, they're using that for availability. And you're looking at a few minutes of time to flip over to another AZ, whereas within an Exadata frame, we can flip over in milliseconds. We keep continue running. There is no loss of conductivity. And then we use the standby in another region for disaster. That's a true disaster solution. >> As opposed to incurring that penalty of latency, or whatever, to spin up the other resource. >> Right, right. >> Okay, so that's clear how kind of you guys address that, that challenge. Last question, maybe you could give us your take, again folks, coming out of Oracle's mouth, but what's the bottom line cost Delta based on your experience between your service and competitive services? I love these conversations because you're not afraid to talk about the competition, so bring it on. >> I've seen, so we've just based on what we've seen with customers deploying databases in Amazon, versus what, you know we've replaced that within, in our cloud service. We're seeing from just a list price perspective. Now, you know, we discount, I know Amazon discounts, but the only thing I can really speak to is list price perspective. It's about a third the cost. So we're talking about a more powerful platform, runs faster. We get these incredible, we haven't even talked about performance here. Talk about availability, performance where we're getting IO rates, IO latencies in the 19 microsecond range. Now with Exadata, that's going to be 50 times faster than what you get with these traditional cloud vendors. So much, much faster, and a third the cost. >> So talk about discounts, I mean, I know Oracle discounts, Oracle from list price, Oracle provides significant discounts. I'm not as familiar with your cloud pricing but I mean, Amazon's discounts are really in the form of like reserved instances. Is your pricing similar in that regard or different? I mean, if I'm just paying on demand, I'm paying through the nose. I presume it's same with you. If I, but if I buy in bulk getting a discount, is that what you mean by discount? Or is it more similar to the way you've traditionally discounted, you know large customers, the more you spend, the more you you get kind of thing. >> It's a, there's a discount structure. So it's, we don't have the same kind of lock-in like with reserved instance structure, but yeah, it's, there are discounts and that's going to be very customer specific. >> Right. >> So, but I think that the end result we're starting at, a three X differential on the price. >> But the reason I'm asking the question is that the stats you gave me are for list price, right? >> Yeah, yes, yeah. >> Okay, and sure, you're saying that at list price you're, you're less expensive. I, and again, my contention would be just by experiences that your discounts would be more aggressive traditionally in Oracle's traditional business. You know, I've done a lot of Oracle negotiation in my days. And if you're, you know, if you're a big customer you can get good deals. And again, I'm not as familiar with the cloud pricing, but still that's, that's good. If you're doing it on a list price basis, to me, that's a conservative statement if that makes any sense. >> Right, that's where it starts. We know that's where it's starting out. So I, you know, once you get into discounts, it's very customer specific. >> Right. >> We know the starting point is at three X differential. Before you do something in the Multi-AZ would be a six X differential, by the way, so. >> Yeah, okay. All right, Chris. Well, Hey, I appreciate you taking us through this, good stuff, and best of luck, good work. You know, you guys keep, I always say Oracle invest you guys spend a lot of money in RD and, and, you know you're quiet for a while in the cloud and all of a sudden you came out like you invented it. So good job! >> All right. >> All right, thanks. Thanks for coming on. All right. >> Thanks. >> Thank you for watching everybody. This is Dave Vellante for Cube conversations. We'll see you next time. (upbeat music)

[Music] hi everybody this is David on tape with the Cuban welcome to Boston we're covering storage here at Amazon storage day and we're looking at all the innovations and the expansion of Amazon's pretty vast storage portfolio Duncan Lennox is here is the director of product management for Amazon DFS Duncan good to see it's great to be here so what is so EF s stands for elastic file system what is Amazon EFS that's right EFS is our NFS based filesystem service designed to make it super easy for customers to get up and running with the file system in the cloud so should we think of this as kind of on-prem file services just stuck into the cloud or is it more than that it's more than that but it's definitely designed to enable that we wanted to make it really easy for customers to take the on pram applications that they have today that depend on a file system and move those into the cloud when you look at the macro trends particularly as it relates to file services what are you seeing what a customer's telling you well the first thing that we see is that it's still very early in the move to the cloud the vast majority of workloads are still running on Prem and customers need easy ways to move those thousands of applications they might have into the cloud without having to necessarily rewrite them to take advantage of cloud native services and that's a key thing that we built EFS for to make it easy to just pick up the application and drop it into the cloud without the application even needing to know that it's now running in the cloud okay so that's transparent to the to the to the application and the workload and it absolutely is we built it deliberately using NFS so that the application wouldn't even need to know that it's now running in the cloud and we also built it to be elastic and simple for the same reason so customers don't have to worry about provisioning the storage they need it just works NFS is hard making making NFS simple and elastic is not a trivial engineering task is it it hadn't been done until we did it a lot of people said it couldn't be done how could you make something that truly was elastic in the cloud but still support that NFS but we've been able to do that for tens of thousands of customers successfully and and what's the real challenge there is it to maintain that performance and the recoverability from a technical standpoint an engineering standpoint what's yes sir it's all of the above people expect a certain level of performance whether that's latency throughput and I ops that their application is dependent on but they also want to be able to take advantage of that pay-as-you-go cloud model that AWS created back with s3 13 years ago so that elasticity that we offer to customers means they don't have to worry about capex they don't have to plan for exactly how much storage they need to provision the file system grows and shrinks as they add and remove data they pay only for what they're using and we handle all the heavy lifting for them to make that happen this this opens up a huge new set of workloads for your customers doesn't it it absolutely does and a big part of what we see is customers wanting to go on that journey through the cloud so initially there starting with lifting and shifting those applications as we talked about it but as they mature they want to be able to take advantage of newer technologies like containerization and ultimately even service all right let's talk about EFS ia infrequently access files is really what it's designed for tell us more about it right so one of the things that we heard a lot from our customers of course is can you make it cheaper we love it but we'd like to use more of it and what we discovered is that we could develop this infrequent access storage class and how it works is you turn on a capability we call lifecycle management and it's completely automated after that so we know from industry analysts and from talking to customers that the majority of data perhaps as much as 80% goes pretty cold after about a month and it's rarely touched again so we developed the infrequent access storage class to take advantage of that so once you enable it which is a single click in the console or one API call you pick a policy 14 days 30 days and we monitor the readwrite IO to every file individually and once a file hasn't been read from or written to in that policy period say 30 days we automatically and transparently move it to the infrequent access storage class which is 92% cheaper than our standard storage class it's only two and a half cents in our u.s. East one region as opposed to 30 cents for our standard storage class two and a half cents per per gigabyte per gigabyte month we've done about four customers that were particularly excited about is that it remains active file system data so we move your files to the infrequent access storage class but it does not appear to move in the file system so for your applications and your users it's the same file in the same directory so they don't even need to be aware of the fact that it's now on the infrequent access storage class you just get a bill that's 92 percent cheaper for storage for that file like that ok and it's and it's simple to set up you said it's one click and then I set my policy and I can go back and change my that's exactly right we have multiple policies available you can change it later you can turn off lifecycle management if you decide you no longer need it later so how do you see customers taking advantage of this what do you expect the adoption to be like and what are you hearing from them well what we heard from customers was that they like to keep larger workloads in their file systems but because the data tends to go cold and isn't frequently accessed it didn't make economic sense to say to keep large amounts of data in our standard storage class but there's advantages to them in their businesses for example we've got customers who are doing genomic sequencing and for them to have a larger set of data always available to their applications but not costing them as much as it was allows them to get more results faster as one example you obviously see that yeah what we're what we're trying to do all the time is help our customers be able to focus less on the infrastructure and the heavy lifting and more on being able to innovate faster for their customer so Duncan Duncan some of the sort of fundamental capabilities of EFS include high availability and durability tell us more about that yeah when we were developing EFS we heard a lot from customers that they really wanted higher levels of durability and availability than they typically been able to have on Prem it's super expensive and complex to build high availability and high durability solutions so we've baked that in as a standard part of EFS so when a file is written to an EFS file system and that acknowledgement is received back by the client at that point the data is already spread across three availability zones for both availability and durability what that means is not only are you extremely unlikely to ever lose any data if one of those AZ's goes down or becomes unavailable for some reason to your application you continue to have full read/write access to your file system from the other two available zones so traditionally this would be a very expensive proposition it was sort of on Prem and multiple data centers maybe talk about how it's different in the clouds yeah it's complex to build there's a lot of moving parts involved in it because in our case with three availability zones you were talking about three physically distinct data centers high-speed networking between those and actually moving the data so that it's written not just to one but to all three and we handled that all transparently under the hood in EFS it's all included in our standard storage to your cost as well so it's not something that customers have to worry about more either a complexity or a cost point of view it's so so very very I guess low RPO and an RTO and my essentially zero if you will between the three availability zones because once your client gets that acknowledgement back it's already durably written to the three availability zones all right we'll give you last word just in the world of file services what should we be paying attention to what kinds of things are you really trying to achieve I think it's helping people do more for less faster so there's always more we can do and helping them take advantage of all the services AWS has to offer spoken like a true Amazonian Duncan thanks so much for coming on the queue for thank you good all right and thank you for watching everybody be back from storage day in Boston you watching the cute

>> Narrator: Live from San Francisco, celebrating 10 years of high tech coverage, it's theCUBE, covering VMworld 2019. Brought to you by VMware and its ecosystem partners. >> Well, welcome back everyone. Live CUBE coverage here in San Francisco, California for VMworld 2019. I'm John Furrier, Dave Vellante, Dave 10 years continues, day one of three days of wall to wall coverage. Mark Lohmeyer, Senior Vice President, Cloud Platform Business Unit and general manager at the VMware, manage cloud for VMware. Great to see you again. >> Great to see you, yeah, thank you. >> So you got, you're managing all the VMware manage cloud on AWS and Dell EMC? >> Right. >> Which was a big part of today's keynote. Obviously a big part of your investments, so you know, you always look at someone's commitment to something. How they spend their resources and their time. So give us an update obviously a lot of resources on the VMware side. >> Mark: Right. >> To make this run, what customers want. Give us an update on what's going on. >> Yeah, yeah I mean so first of all VMware Cloud and AWS, I mean, we're really pleased with the momentum we're seeing for that in the marketplace. So, we compared what it looks like today versus a year ago. And we were talking about it, a year ago and we've increased the number of customers by 4x on the service. We've increased the numbers of VM's on the service by 9x. That's kind of interesting 'cause it shows you that you know, we're adding both new customers as well as existing customers are expanding their investment. So, that's great to see, right? And it's powered by a lot of the compelling Use Cases. You may have heard Pat or others talk about most notably, cloud migrations. You know from an investment perspective which is I think where you sort of started the question you know, significant investment from both VMware as well as AWS the end of the service. You know we say it's jointly engineered and that is absolutely the case. I mean we literally have hundreds of engineers that are optimizing the VMware software to be delivered as a service on top of the AWS infrastructure. >> And that's a lot just to get nuance on this point. Because in the press coverage, I've seen all the press coverage from the Microsoft and the Google. This is different than just Cloud Foundation because you're talking about something completely different. This is jointly engineered. These are specific, unique things. >> Yeah, I mean with the sort of distinction I would sort of articulate there is that in the case of VMware Cloud on AWS, it's a VMware managed, operated, supported, delivered service. Right, so it's our engineers that are pushing the bits into production in AWS. It's our engineers if there's an incident that deal with the you know, with the situation. You know, it's literally a service operated by us. In the case of what we're doing with Azure and GCP, you know first of all from a customer perspective what we heard them telling us is, I think many customers are using Azure, many customers are using GCP and they'd like to have the ability to have that same VMware consistent software stack on those clouds. But the operational model is different. So in those two cases there's a partner called CloudSimple. Who's a VCPP partner and they're taking our standard VMware Cloud Foundation software that customers use on Prem and they are operating and delivering that as a Cloud service on top of those Cloud platforms. >> Just to review so VMware Cloud on AWS and Outposts both your responsibility, there's two way street there? >> Yup. (laughing) >> Which is rare with Amazon usually it's a one way street. My words not yours. But so, and, so you manage both sides of that? Is that correct? >> Mark: Yeah, that's right, that's right. >> So you're happy to sell either one? >> Absolutely, yup. >> Right, and then the Dell EMC version is kind of the on Prem version of Outposts, if you will. Is that a fair characterization? >> Mark: Yeah, yeah, so. >> Without the public cloud. >> Yeah, I mean absolutely, I think one of the interesting things was you know, we've been in market now with the VMware Cloud on AWS for a couple years. And, you know it's going great but one of the things we've heard from customers was, "Hey, we sort of really like this VMware managed cloud model where you're taking all of the heavy lifting of worrying about the Lifecycle of the VMware software. Worrying about the you know upgrades to the hardware, you're taking that all off of our plate. But why can't we have that same cloud delivery model back on Prem?", right and so, that was the impetus for what we originally announced as Project Dimension and now we're launching this week as VMware Cloud on Dell EMC. >> So all the benefits go with the Dell infrastructure hardware? >> So, I got to ask you, so one are the attributes of those those solutions, is they're highly homogenous, right? And, Andy Jassy made a big deal about that same Control Plane, same Data Plane. >> Mark: Right. >> So my question is, help me square the circle with MultiCloud which is highly heterogeneous? (laughing) So, can I have my cake and eat it, too? Can I have this, you know unified vision of the world? This controlled, same compliance, government security, EDIx, management etc, and have all this heterogeneity? How does that? >> Yeah, so I think, I mean to me it starts from what the customer would like to do, right? And what we're seeing from customers is it's increasingly a MultiCloud world, right. That expands spans private cloud, public cloud and Ed. >> Dave: You're smiling when you say that. >> Mark: Yeah, now, now-- >> The chaos is an opportunity for VM. (laughing) >> Yeah, but it's a challenge for customers, right? And so, if you look at how VMware is trying to help there if you say sort of square the circle. I think that first piece is this idea of consistent operations, right. Then we have these management tools that you can use to consistently operate those environments, whether they're based on a VMware based infrastructure or whether they're based on a native cloud infrastructure. Right, so if you look at our cloud health platform for example, it's a great example where that service can help you under, get visibility to your cloud spend across different cloud platforms. Also B service platforms. It can help you reduce that spend over time. So that's sort of what we refer to as consistent operations. Right, which can span any cloud. You know what my team is responsible for is more in the consistent infrastructures base and that's really all about how do we deliver consistent compute network and storage service that spans on Prem, multiple public clouds and Edge. So that's really where we're bringing that same VMware Cloud Foundation stack to all those different environments. >> Mark, I want to get your thoughts on what Pat Gelsinger said on the keynote. He said, "modernize and migrate or migrate and modernize" he also mentioned live migrate as a big feature. >> Mark: Yes, yes. >> On the modernize and migrate and migrate then modernize, they basically pick one and people are doing both. >> Mark: Right, right, right. >> What's he mean by that give us some examples and then what's the impact to the customer? Is it just the behavior of the customer? >> Yeah, I mean, it varies a little bit based on what the customer's trying to accomplish. But you know the one thing I'll say is that, you know, historically it was a little bit tough to have that choice. Right, so you know the sort of the thought was, hey I have to like re-factor and re-platform everything upfront just to be able to get it to the public cloud. And then once it's there I can sort of start to modernize. I think in that can be a multi-year process, right? >> Yeah. >> I think one of the really interesting opportunities that we've opened up for customers with VMware Cloud on AWS is you don't necessarily have to re-factor everything just to be able to get to the public cloud. We could help them migrate to the public cloud very quickly without requiring any changes if they don't want to. And then when they're there, they can modernize at their own pace based on the needs of the business. All right, and so I think having that additional option is actually quite useful for customers that want to get to the cloud quickly and then from there begin to modernize. >> So two main paths with migration and modernize as the easiest one given the managed service. >> Yeah, yeah, and but you know that being said, I think also you see a set of customers that say "Look, sort of digital transformation and modernization is my primary goal." Right, and for them by enabling some of these things like Native Kupernetes as a service in vSphere and in VMware Cloud and AWS by enabling this AI and ML workloads with a Nivida partnership for that classic customers, they can also just start with the modernization piece, right? Directly on the-- >> So the migrate to modernize would be a lift in shift essentially and then modernize? >> Mark: Ah-hm. >> And that's what Amazon wants you to do? But, you're giving customers a choice, is what I'm-- >> Mark: We have, yeah no, I mean look at the end of the day I think both VMware and AWS believe strongly in understanding what customers are looking for and making sure we're delivering that value to them. And I think you know, this is one of the compelling new options that we've enabled for customers, I think with VMworld Cloud on AWS is that we could take a migration project that would have previously taken three years and we could do it in a few months. >> You know Mark I had a chance to talk to Carl Eschenbach two weeks ago before the show. He came in for an interview Sequoia Capital, Carl Eschenbach, former COO of VMware been there for years. He was part of the deal with AWS, graphing that deal. We were talking about the moment and time where your stock price started to move up this October 2016. That's right when the deal was announced. Since then the stock price has been up. For a lot of reasons, we've talked on theCUBE before. The question I have for you is, what have you learned? What surprises you from this relationship? Because one the clarity was easy, meet Cloud Air, no more. This is our cloud strategy. All on AWS and MultiCloud as it develops you certainly have had to clarify with customers. But now that you entered the managed service, what new things have popped up that might not have been on your radar? What did you expect? What are some surprises from this relationship from a customer behavior standpoint? >> Yeah, that's a real interesting question. So, I think you know in the early days we sort of had this concept of "Hey, let's enable the full VMware capabilities on AWS." And we were sort of talking about it as a tech, almost like a technical solution, right? And what, what we could enable. I think sort of what quickly became apparent is hey, sort of behind that technical approach there's actually some really compelling Use Cases here. And I think that, if I think back to two years ago, I don't think we fully anticipated how compelling this cloud migration Use Case would be. I mean I don't think we really realized internally within VMware how hard it was for customers before to do that. And, I think customers didn't realize sort of how much easier and faster and lower cost that we could make it for them with this type of service. So I think that one, although we were maybe talking about it a little bit in the early days. I think it surprised me at least at how sort of broad based the customer interest was in that type of capability. >> Any other broader market interest on things that were surprises or not surprises that are compelling? >> I mean, you know the other thing I wouldn't say it's a surprise per se, but I mean, I think the partnership with AWS has been fantastic. Right, I mean we sort of went into it, I think in the right way between Pat and Andy and focused on doing something meaningful together. The relationship has only gotten sort of deeper and deeper over time. And, one of the interesting things about it is that relationship spans not just engineering and product management and product strategy which is sort of my neck of the woods. But also the marketing organizations, the sales organizations, the support organizations. So it's, it's become I think a very deep partnership. We're able to speak to each other very openly and trying to solve together the, you know the problems that customers are putting in front of us. >> And what's with Outposts, what's the new update on Outposts? >> Yeah, yeah so you know no news on Outposts today obviously but we're working very closely with AWS to enable the VMware Cloud on AWS Outposts model second half of this year. And, the customer interest has just been fantastic, right. And in many ways it's basically the exact same value prop of VMC on AWS in terms-- >> In reverse. >> But, but in reverse and anywhere you want, right, at your door step, right, any Edge, any data center, so. >> I got to ask you, back to the AWS relationship. We were big fans of it always have been. Learned from both sides and believe in it. Having said that, EC2 is the bread and butter for Amazon despite it's hundreds and hundreds of services. That's where their revenue comes from, and compute, your compute business is you know, significant. So my question is, is it a zero some game long-term or when you look at the tam do you see all these other services that you can sell longer term providing you know, the growth engine for your respective companies? Or, does this whole you know, rising tide lift both boats, what are your thoughts on that? >> Yeah, I mean it's clearly rising tide lifts both boats. I mean, again I'll, I always bring it back to the customer right, 'cause that's the way I like to view the world and AWS-- >> And you've got some evidence now that's why I'm asking. >> Yeah and I mean what you're seeing is actually I mean if you take some of these customer examples. Let me give you one from the UK. So, Stagecoach. I don't know if you heard about these guys. But they're a major, so they provide transportation services in the UK, and other countries as well. So, they run a network of buses, trains and they're responsible for the transportation of three million commuters every day in the UK. So, they have this really mission critical application that they're building that is basically responsible for scheduling those buses and those trains and scheduling the conductors and the operators. So you can imagine this application is super mission critical for their business, right. And, they chose to run that application on VMware Cloud on AWS and one of the reasons they chose that is because we have a unique capability called stretch clustering. >> Sure. >> Which says "Hey, even if there's an issue in one AZ we can restart that application in a second AZ. So there's a really good reason for the customer to choose it. But now back to your question, right? If you think about the opportunity in that for both VM or in AWS, it's meaningful, right? You know, for us, we're selling the entire VMware Cloud on AWS service to that customer across those two AZ's for mission critical workload that's core to their business. For AWS, they're able to of course not only supply the infrastructure that we run on top of but also as that customer looks to do more interesting things they can attach an additional native AWS services, right? So, you know I think that's a great example where delivering value to the customer and if you focus on that the right things will kind of flow back to the companies that help make that possible. >> Good partnering helps you reduce friction and get to market faster. Thinking about the intense effort that both you know, Pat's described, Andy Jassy described, you've described in terms of that partnership, that deep engineering. Can you do multiples of those or is it that you don't because of the respect for the partnership or is it too intense and it's too resource intensive? How many of these types of partnerships can you actually have? >> Well I mean and I think Pat has said it pretty clearly, right? I mean AWS is our primary preferred partner, right. And, what we're doing with them is very unique, right? And it's something that we want to make sure that we have the right level of investment in and that we do an amazingly good job of, right. And I think they feel the same way. And so having that focus together between the two companies. I think is what, has allowed us to be you know, achieve some of the level of success we've had to date and we expect to do that going forward. >> Mark, final question for you. What's your objective this year in your business unit? What's your focus? What are some of the things that you're working on that people should know about? >> Yeah, so first of all. I had VMware Cloud VD but that's just to wrap that up I think the big thing we're focused on going forward is really this modernization kind of piece of the story. How do we enable Native Kupernetes in the service? How do we enable ML and AI workloads in this service? How do we do a better job of connecting to all of the AWS services? So, you're going to see a big kind of focus, there. Beyond VMware Cloud AWS, I mean we're really excited about bringing this VMC model back on Prem both with Dell and on top of AWS Outposts. I mean the customer interest has been, you know fantastic, right? And, you think about all the reasons that customers want to be able to run their applications, you know on Prem, data locality, latency, compliance, all sorts of really good reasons. We think that those services have really hit a sweet spot of that market. >> IT as a managed service, what an interesting idea, don't you think? (laughing) >> Mark: Yeah. >> Whole nother level same game, whole new ball game, right? >> Absolutely! >> Mark, thanks for sharing your insight. Congratulations on your success and we'll be following it. VMware Manage Solutions AWS certainly a big hit. Changed the game for the company and now they're bringing Dell EMC among other potential business model opportunities for customers. As Cloud 2.0 comes as theCUBE's coverage. Live at VMworld 2019, be right back with more from San Francisco after this short break. (bright music)

>> Narrator: Live from New York, it's theCube! Covering AWS Global Summit 2019, brought to you by Amazon Web Services. >> Welcome back, we're here at the Javits Center in New York City for AWS Summit, I'm Stu Miniman, my cohost is Corey Quinn and happy to welcome to the program Scott Mullins, who's the head of Worldwide Financial Services Business Development with Amazon Web Services based here in The Big Apple, thanks so much for joining us. >> Thanks for having me, Stu, thanks for having me, Corey. >> All right so we had obviously financial services big location here in New York City. We just had FINRA on our program, had a great conversation about how they're using AWS for their environments, but give us a thumbnail if you will about your business, your customers and what you're seeing there. >> Sure, we're working with financial institutions all the way from the newest FinTech startups, all the way to organizations like FINRA, the largest exchanges and brokers dealers like Nasdaq, as well as insurers and the largest banks. And I've been here for five years and in that time period I actually went from being a customer speaking at the AWS Summit here in the Javits Center on stage like Steve Randich was today to watching more and more financial institutions coming forward, talking about their use in the cloud. >> Yeah before we get into technology, one of the biggest trends of moving to cloud is I'm moving from CapEx more to OpEx and oh my gosh there's uncertainty because I'm not locking in some massive contract that I'm paying up front or depreciating over five years but I've got flexibility and things are going to change. I'm curious what you're seeing as the financial pieces of how people both acquire and keep on the books what they're doing. >> Yeah it can be a little bit different, right, then what most people are used to. They're used to kind of that muscle memory and that rhythm of how you procured technology in the past and there can be a stage of adjustment, but cost isn't really the thing that people I think look to the most when it comes to cloud today, it's all about agility and FINRA is a great example. Steve has talked about over and over again over the last several years how they were able to gain such business agility and actually to do more, the fact that they're now processing 155 billion market events every night and able to run all their surveillance routines. That's really indicative of the value that people are looking for. Being able to actually get products to market faster and reducing development cycles from 18 months to three months, like Allianz, one of our customers over in Europe has been able to do. Being able to go faster I think actually trumps cost from the standpoint of what that biggest value driver that we're seeing our customers going after in financial services. >> We're starting to see such a tremendous difference as far as the people speaking at these keynotes. Once upon a time you had Netflix and folks like that on stage telling a story about how they're using cloud to achieve all these amazing things, but when you take a step back and start blinking a little bit, they fundamentally stream movies and yes, produce some awesome original content. With banks and other financial institutions if the ATM starts spitting out the wrong number, that's a different point on the spectrum of are people going to riot in the street. I'm not saying it's further along, people really like their content but it's still a different use case with a different risk profile. Getting serious companies that have world shaking impact to trust public cloud took time and we're seeing it with places like FINRA, Capital One has been very active as far as evangelizing their use of cloud. It's just been transformative. What does that look like, from being a part of that? >> Well you know it's interesting, so you know you just said it, financial services is the business of risk management. And so to get more and when you see more and more of these financial institutions coming forward and talking about their use of cloud, what that really equates to is comfort, they've got that muscle memory now, they've probably been working with us in some way, shape or form for some great period of time and so if you look at last year, you had Dean Del Vecchio from Guardian Life Insurance come out on stage at Reinvent and say to the crowd "Hey we're a 158 year old insurance company but we've now closed our data center and we're fully on AWS and we've completed the transformation of our organization". The year before you saw Goldman Sachs walk out and say "Yeah we've been working with AWS for about four years now and we're actually using them for some very interesting use cases within Goldman Sachs". And so typically what you've seen is that over the course of about a two year to sometimes a four year time period, you've got institutions that are working deeply with us, but they're not talking about it. They're gaining that muscle memory, they're putting those first use cases to begin to scale that work up and then when they're ready man, they're ready to talk about it and they're excited to talk about it. What's interesting though is today we're having this same summit that we're having here in Cape Town in Africa and we had a customer, Old Mutual, who's one of the biggest insurers there, they just started working with us in earnest back in May and they were on stage today, so you're seeing that actually beginning to happen a lot quicker, where people are building that muscle memory faster and they're much more eager to talk about it. You're going to see that trend I think continue in financial services over the next few years so I'm very excited for future summits as well as Reinvent because the stories that we're going to see are going to come faster. You're going to see more use cases that go a lot deeper in the industry and you're going to see it covering a lot more of the industry. >> It's very much not, IT is no longer what people think of in terms of Tech companies in San Francisco building products. It's banks, it's health care and these companies are transitioning to become technology companies but when your entire, as you mentioned, the entire industry becomes about risk management, it's challenging sometimes to articulate things when you're not both on the same page. I was working with a financial partner years ago at a company I worked for and okay they're a financial institution, they're ready to sign off on this but before that they'd like to tour US East one first and validate that things are as we say they are. The answer is yeah me too, sadly, you folks have never bothered to invite me to tour an active AZ, maybe next year. It's challenging to I guess meet people where they are and speak the right language, the right peace for a long time. >> And that's why you see us have a financial services team in the first place, right? Because your financial services or health care or any of the other industries, they're very unique and they have a very specific language and so we've been very focused on making sure that we speak that language that we have an understanding of what that industry entails and what's important to that industry because as you know Amazon's a very customer obsessed organization and we want to work backwards from our customers and so it's been very important for us to actually speak that language and be able to translate that to our service teams to say hey this is important to financial services and this is why, here's the context for that. I think as we've continued to see more and more financial institutions take on that technology company mindset, I'm a technology company that happens to run a bank or happens to run an exchange company or happens to run an insurance business, it's actually been easier to talk to them about the services that we offer because now they have that mindset, they're moving more towards DevOps and moving more towards agile. And so it's been really easy to actually communicate hey, here are the appropriate changes you have to make, here's how you evolve governance, here's how you address security and compliance and the different levels of resiliency that actually improve from the standpoint of using these services. >> All right so Scott, back before I did this, I worked for some large technology suppliers and there were some groups on Wall Street that have huge IT budgets and IT staffs and actually were very cutting edge in what they were building, in what they were doing and very proud of their IT knowledge, and they were like, they have some of the smartest people in the industry and they spend a ton of money because they need an edge. Talking about transactions on stock markets, if I can translate milliseconds into millions of dollars if I can act faster. So you know, those companies, how are they moving along to do the I need to build it myself and differentiate myself because of my IT versus hey I can now have access to all the services out there because you're offering them with new ones every day, but geez how do I differentiate myself if everybody can use some of these same tools. >> So that's my background as well and so you go back that and milliseconds matter, milliseconds are money, right? When it comes to trading and actually building really bespoke applications on bespoke infrastructure. So I think what we're seeing from a transitional perspective is that you still have that mindset where hey we're really good at technology, we're really good at building applications. But now it's a new toolkit, you have access to a completely new toolkit. It's almost like The Matrix, you know that scene where Neo steps into that white room and hey says "I need this" and then the shelves just show up, that's kind how it is in the cloud, you actually have the ability to leverage the latest and greatest technologies at your fingertips when you want to build and I think that's something that's been a really compelling thing for financial institutions where you don't have to wait to get infrastructure provisioned for you. Before I worked for AWS, I worked for large financial institutions as well and when we had major projects that we had to do that sometimes had a regulatory implication, we were told by our infrastructure team hey that's going to be six months before we can actually get your dev environment built so you can actually begin to develop what you need. And actually we had to respond within about thirty days and so you had a mismatch there. With the cloud you can provision infrastructure easily and you have an access to an array of services that you can use to build immediately. And that means value, that means time to market, that means time to answering questions from customers, that means really a much faster time to answering questions from regulatory agencies and so we're seeing the adoption and the embrace of those services be very large and very significant. >> It's important to make sure that the guardrails are set appropriately, especially for a risk managed firm but once you get that in place correctly, it's an incredible boost of productivity and capability, as opposed to the old crappy way of doing governance of oh it used to take six weeks to get a server in so we're going to open a ticket now whenever you want to provision an instance and it only takes four, yay we're moving faster. It feels like there's very much a right way and a wrong way to start embracing cloud technology. >> Yeah and you know human nature is to take the run book you have today and try to apply it to tomorrow and that doesn't always work because you can use that run book and you'll get down to line four and suddenly line four doesn't exist anymore because of what's happened from a technological change perspective. Yeah I think that's why things like AWS control tower and security hub, which are those guardrails, those services that we announced recently that have gone GA. We announced them a couple of weeks ago at Reinforce in Boston. Those are really interesting to financial services customers because it really begins to help automate a lot of those compliance controls and provisioning those through control tower and then monitoring those through security hub and so you've seen us focus on how do we actually make that easier for customers to do. We know that risk management, we know that governance and controls is very important in financial services. We actually offer our customers a way to look from a country specific angle, add the different countries and the rule sets and the requirements that exist in those countries and how you map those to our controls and how you map those into your own controls and all the considerations that you have, we've got them on our public website. If you went to atlas.aws right now, that's our compliance center, you could actually pick the countries you're interested in and we'll have that mapping for you. So you'll see us continue to invest in things like that to make that much easier for customers to actually deploy quickly and to evolve those governance frameworks. >> And things like with Artifact, where it's just grab whatever compliance report you need, submit it and it's done without having to go through a laborious process. It's click button, receive compliance in some cases. >> If you're not familiar with it you can go into the AWS console and you've got Artifact right there and if you need a SOC report or you need some other type of artifact, you can just download it right there through the console, yeah it's very convenient. >> Yeah so Scott you know we talked about some of the GRC pieces in place, what are you seeing trends out there kind of globally, you know GDRP was something that was on everybody's mind over the last year or so. California has new regulations that are coming in place, so anything specific in your world or just the trends that you're seeing that might impact our environments-- >> I think that the biggest trends I would point to are data analytics, data analytics, data analytics, data analytics. And on top of that obviously machine learning. You know, data is the lifeblood of financial services, it's what makes everything go. And you can look at what's happening in this space where you've got companies like Bloomberg and Refinitiv who are making their data products available on AWS so you can get B-Pipe on AWS today, you can also get the elektron platform from Refintiv and then what people are trying to do in relation to hey I want to organize my data, I want to make it much easier to actually find value in data, both either from the standpoint of regulatory reporting, as you heard Steve talk about on stage today. FINRA is building a very large data repository that they have to from the standpoint of a regulatory perspective with CAT. Broker dealers have to actually feed the CAT and so they are also worried about here in the US, how do I actually organize my data, get all the elements I have to report to CAT together and actually do that in a very efficient way. So that's a big data analytic project. Things that are helping to make that much easier are leg formations, so we came up with leg formation last year and so you've got many financial institutions that are looking at how do you make building a data leg that much easier and then how do you layer analytics on top of that, whether it's using Amazon elastic map reduce or EMR to actually run regulatory reporting jobs or how do I begin to leverage machine learning to actually make my data analytics from a standpoint of trade surveillance or fraud detection that much more enriched and actually looking for those anomalies rather than just looking for a whole bunch of false positives. So data analytics I think is what I would point to as the biggest trend and how to actually make data more useful and how to get to data insights faster. >> On the one end it seems like there's absolutely a lot of potential in this, on the other it feels in many cases with large scale data analytics, it's we have all these tools for machine learning and the rest that we can wind up passing out to you but you need to figure out what to do with them, how to make it work and it's unclear outside of a few specific use cases and I think you've alluded to a couple of those how to take in a typical business that maybe doesn't have an enormous pile of data and start applying machine learning to it in a way that makes intelligent sense. That feels right now like a storytelling failure to some extent industry wide. We're starting to see some stories emerge but it still feels a little "Gold Rush"-y to some extent. >> Yeah I would say, and my advice would be don't try to boil the ocean or don't try to boil the data leg, meaning you want to do machine learning, you've got a great amount of earnestness about that but picture use case, really hone in on what you're trying to accomplish and work backwards from that. And we offer tooling that can be really helpful in that, you know with stage maker you can train your models and you can actually make data science available to a much broader array of people than just your data scientists. And so where we see people focusing first, is where it matters to their business. So if you've got a regulatory obligation to do surveillance or fraud detection, those are great use cases to start with. How do I enhance my existing surveillance or fraud detection, so that I'm not just wading again through a sea of false positives. How do I actually reduce that workload for a human analyst using machine learning. That's a one step up and then you can go from there, you can actually continue to work deeper into the use cases and say okay how do I treat those parameters, how do I actually look for different things that I'm used to with the rules based systems. You can also look at offering more value to customers so with next best offer with Amazon Personalize, we now have encapsulated the service that we use on the amazon.com retail site as a service that we offer to customers so you don't have to build all that tooling yourself, you can actually just consume Personalize as a service to help with those personalized recommendations for customers. >> Scott, really appreciate all the updates on your customers in the financial services industry, thanks so much for joining us. >> Happy to be here guys, thanks for having me. >> All right for Corey Quinn, I'm Stu Miniman, back with more here at AWS Summit in New York City 2019, thanks as always for watching theCube.

from Gillette Stadium in Foxborough Massachusetts it's the cube covering Vita winter warmer 2019 brought to you by silicon angle media hi I'm Stu minimun and this is the cube at V tug winter warmer 2019 at Gillette Stadium home of the New England Patriots the AFC Championship team going to the Super Bowl third year in a row yet again Randall right yeah paying it's my Los Angeles Rams oh so happy to welcome to the program Randall hunt who's a software engineer with AWS did a keynote this morning I believe it was a hundred AWS features in 50 minutes and felt like you we added a couple more than 100 and went a little over 50 minutes but I think we probably hit 57 minutes that was what the slide counter said but yeah I added a couple of the updates since reinvent you know reinvent is not the end of our innovation we continued releasing new stuff after that all right so our program we're not going to be showing JavaScript we're gonna take a deep breath and slow down a little bit because you know our audience absolutely knows Amazon I tell you this show remember like four years ago first time AWS presented me at Microsoft and AWS here and people heard cloud 101 and I was like come on I could have given this presentation and they were walking around like oh my god I just you know found out that you know who you know horseless carriages and I can do that do them and things like this so you know cloud we've been there for a decade but we're still I believe you know day zero day one is what Amazon always likes this is day one it's always day one so there's no way we can shove the entire reinventing keynote into this discussion so you know want to start first Tulsa rent a little bit about yourself your role what you work on and what customers you talk to sure so I studied physics and then I found out physicists don't really make any money so I became a software engineer and I worked at NASA I worked at SpaceX and worked with this company called MongoDB back then it was called Tianjin and then I am an Amazon I was my second time around in Amazon I'm a software engineer there but I'm also a Technical Evangelist and what that means is I get to travel around the world and make make all of the demos and chat with all of our customers and kind of solicit feedback from them and then kind of try to act as the voice of the customer for the service teams whenever I can get them to listen yeah so probably not going to go into open source versus software licensing of things with you because we want to make sure that we can publish I tell you space is one of those things I love it when I've interviewed people that have been in space I've talked to lots of companies that have our code in space Amazon you have I loved you know robotics and space are hard and we make it easy and I kind of laugh cuz I was an engineer as an undergrad I mean I studied a little bit of you know what it takes to break gravity and understand I always love watching you know all the shows about space and track SpaceX would you work for and things like that give me a break you haven't made space easy well I think space as a whole is getting easier this industry is becoming more approachable one of the things that we launched to reinvent this year was a ground station and this is something where if you have an S band or UHF you know satellite and leo which is low Earth orbit or mio which is medium Earth orbit you can basically down stream that data to one of these ground stations which is you know essentially attach to a region you know in this case us East 2 which is in a like Ohio area and you can go and say hey just stream this data into s3 for me or you know let me access this from my V PC which is pretty gnarly if you think about it you know you have a you have an IP address which is a satellite in space yeah I love I worked on replication technology 15 years ago and it was like okay can the application take the ping off the satellite or you know how do we do this so look we're leveraging satellites a little bit more I understand it's a great tagline to make those useful and more readily just you know it's amazing you think about when you think about my availability zones and regions it's now you know that things aren't just on the Terra Firma well I'm looking forward to the first availability zone on the on the moon or on Mars that that'll be you know when we have utopia planitia 1a that'll be the really cool AZ alright we heard the first blue origins working to Mars no well the latency you know if you have 300,000 and fit three hundred fifty thousand kilometers on average between the Earth and the moon so you know you can go around the earth it would speed of light 7.5 times every second to go to the moon is a fool I hang it's like six seven seconds or so so the latency requirements become a little bit harder there I roll more my wrong pin I have I have the Grace Hopper nanosecond which is the wit which is you know curled up and if you follow the white thing it's how long light would take to travel that and it does it in two nanoseconds so you got me I'm a physics lover and love space as does a lot of our audience so bring it down to the thing one of the things that amazon has done really well is I don't need to be a physics geek to be able to use this technology we're having arguments as to you know if I'm starting out or if I want to restart my career today do I go code or heck you know let me just use lambda and all these wonderful things that Amazon have and I might not even need to know traditional coding I mean when I learned programming you know it was you learned logic and wrote lines of code and then when you went to coding it's pulling pieces and modifying things and in the future it's it seems like serverless goes even further along that spectrum I definitely think there's opportunities for folks who have just you know I don't want to say modest coding abilities but people who were kind of you know industry adjacent scientists you know data scientists folks like that who may not necessarily be software engineers or have the they couldn't recite in Big O notation for mergesort and things like that from scratch you know but they know how to write basic code there's a lot of opportunity now for those developers and I'll call them developers to go and write a lambda function and just have it accomplishing a large portion of their business logic for their whole company I think the you know you have a spectrum of compute options you have you know ec2 on the one side and then you have containers and then as you move towards service you get this this you know spectrum between Fargate and lambda and lambda being the the chief level of abstraction but I I think in a couple cases you can you know even go further than that with things like amplify which is a service that well it's an open source project that we launched and it's also a service that we launched and it takes together a bunch of different AWS services things like app sank and kognito and lambda and it merges them all together with one CLI call you can go and say hey spin up a static site for me like a Hugo static site or something and it'll build the code pipeline build all that stuff for you without you having to you know worry about all the stuff and if developers are starting new today you know I remember when I started I really had to go deep on some of the networking stuff you know I had to learn all these different routers and like how to program them and these like the industry router so you know the million dollar ones and having to rack and stack this stuff and the knowledge is not really needed to operate of large-scale enterprise you know if you if you know a Ralph's table and you you you know V pcs you know you can run you know a multi-billion dollar company if you want yeah it's been interesting to watch too and you know I think the last five years the proliferation of services in AWS got to a point where is like oh my gosh if I wanted to kind of configure a server for my datacenter or configure an equivalent something that I wanted at AWS there was more choices in the public cloud than there was there and people like oh my gosh how do I learn it how do I do this but what we start to see is it's more don't need to do that because what do I want to do if there's an application that I can run where services that will help make it easier for me to do that because the whole it's not let me replicate what I was doing here and do it there but I have to kind of start with a clean sheet of paper and say okay well what what's the goal what data do I need what applications do I need to build and start there I'm curious what you see and how do you help companies through that so that this is a really common scenario so I this is a kind of key point here is enterprises and companies have existed since before the cloud was really around so why do we keep seeing so much uptick why do we keep seeing so many customers moving into the cloud and how do we make it easier for customers to get into the cloud with their existing workloads so along that same spectrum if you have greenfield projects if I were running my own company and I were doing everything I would absolutely start in the cloud and I would build everything as kind of cloud native and if you want to migrate these existing workloads that's part of the one of the things that we launched this year in partnership with VMware is VMware kind of interface for AWS so you can use your native vCenter and vSphere kind of control plane to access EBS to access route 53 and ec2 and all the other kind of underlying stuff that you are interested in run it you can even do RDS on VMware in my environment so that line is definitely blurring between my stuff and my stuff somewhere else and when people are talking about migrating workloads right you know you can take the lowest hanging fruit the most orthogonal piece of your infrastructure and you can say hey let me take this piece as an experimental proof of concept workload and what kind of lift and shift it into the cloud and then let me build the accoutrement the glue and all the other stuff that kind of is associated with that workload cloud native and you'll get additional agility your you know 1:1 ops person can manage this whole suite of things across 19 20 regions of AWS and you know there's kind of global availability and all this kind of good stuff that typically comes with the cloud and in addition to that as you keep moving more and more workloads over it's not like it's a static thing you know you can evolve you can adjust the application you can add new features and you can build new stuff as your move these applications over to the cloud yeah and it's interesting because just the dynamics are changing so much so there's been there's still so much movement to the cloud and then oh well some people I'm pulling stuff back and then you see you have a WS outposts so later 2019 we expect to Amazon to have you know footprint in people's environments and then you know Jeff just to make things even more complicated well the whole edge computing IOT and the like which you know everything from snowball and these pieces so the answer is it gets even more complicated but you know your your AWS I know is trying to help simplify this for use right the board I think I can say anything at all about AWS it's that if a customer is asking us to build something we are gonna do our best to make that customer happy we take customer feedback so incredibly seriously in all of our meetings all of our service team meetings you know we that voice of the customer is very strong and so if people are saying hey I want a AWS in my own datacenter you know that's kind of the genesis of outpost and it's this idea that well we have this control plane we have this hardware let's figure out how we can get it to more customers and customers are saying hey I want into my data center I want to just be able to plug in some fiber and plug in some power and I want it to work and that's the idea right we're gonna when I think of every company that I've watched there's usually something that people will gripe about and what I've been very impressed with Amazon Amazon absolutely listens and moves pretty fast to be able to address things and if you see you know if I'm a competitor of Amazon I'm like oh well you know this is the way that we get in there you know where we think we have an advantage chances are that Amazon is addressing it looking to you know move past it and you know absolutely the Amazon of 2019 is sure not the Amazon of 2018 or you know when you thought about it you know 2015 and it's big challenge for people as to because usually I think of something and you never get a second chance to make a first impression but it changes so much right everything changes that you know I need to revisit it it's like oh well this is the way I do things well Amazon has five different ways you can do that now um you know which one fits you best and I think that's important is different applications gonna have different characteristics that you want to be able to pull in and run in different ways yeah you know honestly I'm a huge fan of service I I think service is where a ton of different workloads are going to move into the future and I just see more and more companies migrating their existing you know everything from elastic Beanstalk applications so like vdq you know VMware images into the service environment and I like seeing that kind of uptick and someone recently I I can't remember who it was someone sent me a screenshot of their console with their ec2 instances in 2010 and maybe it was part of this 10-year challenge thing on Twitter where it's 2009 versus 2019 but they sent me you know they're in one large and the screenshot of the console from back then and they sent me a screenshot of 2019 and Wow things really have changed and you don't really notice it as much when you're using it every day but I can imagine you know their their Ops teams where they haven't logged into the console in three years because you know everything is done kind of in an automated fashion they set up their auto scaling group you know three years ago and then the only time they ever log in is to update to new instance types or something for the cost savings and I get messages on Twitter sometimes from people who are like whoa console got an update this is so cool and then sometimes we we get messages from people where you know we changed the EBS volume snapshotting things we had somebody who had it was like 130,000 EBS snapshots or something and they were like hey you removed my ability for me to select multiple snapshots it what it's like well you have a hundred and thirty thousand so we went in into the UI and we added a little icon that works better for large groups of snapshots you know if there's a customer pain point we will do everything we can to address it all right Randall Hunt really appreciate you sharing with us your experience what's going on with customers and absolutely that 10-year challenge we know things change fast we used to measure in decades I say now it's usually more like you know 18 to 24 months before between everything AWS in 2029 it's gonna be crazy and I can't I can't imagine what its gonna look like then all right well the cube we started broadcasting from in 2010 we appreciate you staying with us through 2019 check out the cube net for all of our programming I'm Stu minimun and thanks so much for watching the key

(bright instrumental music) >> Hi everyone, I'm John Furrier. Here in the Cube Studios in Palo Alto, for a special Cube conversation on some big news from PureStorage. We're here with Chadd Kenney, who's the Vice President of Product and Solutions at PureStorage. Big Cloud news. A historic announcement from PureStorage. One of the fastest growing startups in the storage business. Went public, I've been following these guys since creation. Great success story in Silicon Valley and certainly innovative products. Now announcing a Cloud product. Cloud data services, now in market. Chadd, this is huge. >> It's exciting time. Thank you so much for having us. >> So you guys, obviously storage success story, but now the reality is changed. You know we've been saying in the Cube, nothing changes, you get storage computer networking, old way, new way in the Cloud. Game is still the same. Storage isn't going away. You got to store the data somewhere and the data tsunami is coming. Still coming with Edge and a bunch of other things. Cloud more important than ever. To get it right is super important. So, what is the announcement of Cloud Data Service. Explain what the product is, why you guys built it, why now. >> Awesome. So, a couple different innovations that are part of this launch to start with. We have Cloud Block Store which is taking Purity, which is our operating system found on-prem and actually moving it to AWS. And we spent a bunch of time optimizing these solutions to make it so that, we could actually take on tier one, mission critical applications. A key differentiator is that most folks were really chasing after test-dev and leveraging the Cloud for that type of use case. Whereas Cloud Block Storage, really kind of industry strength and ready for mission critical applications. We also took protection mechanisms from FlashArray on-premises and actually made it so that you could use CloudSnap and move and protect data into the public Cloud via portable snapshot technology. Which we can dig into a little bit later. And then the last part is, we thought it was really ripe to change data protection, just as a whole. Most people are doing kind of disc to disc, to tape, and then moving tape offsite. We believe the world has shifted. There's a big problem in data protection. Restoring data is not happening in the time frame that its needed, and SLAs aren't being met, and users are not happy with the overall solution as a whole. We believe that restorations from Flash are incredibly important to the business, but in order to get there you have to offset the economics. So what we're building is a Flash to Flash to Cloud solution which enables folks to be able to take the advantages of the economics of Cloud and be able to then have a caching mechanism of Flash on-premises. So that they can restore things relatively quickly for the predominant set of data that they have out there. >> And just so I get everything right here. You guys only been on-premises only, this is now a cloud solution. It's software. >> Correct. >> Why now? Why wait 'til now, is the timing right? What's the internal conversation? And why should customers know, is this the right time. >> So, the evolution of cloud has been pretty interesting as we've gone through it. Most customers went from kind of a 100% on-premises, the Cloud came out and said, hey, I'm going to move everything to the Cloud. They found that didn't work great for enterprise applications. And so they kind of moved back and realized that hybrid cloud was going to be a world with they wanted to leverage both. We're seeing a lot of other shifts in the market. VMware already having RDS in platform. Now it's true hybrid cloud kind of playing out there. Amazon running an AWS. It's a good mixture just to showcase where people really want to be able to leverage the capabilities of both. >> So it's a good time because the customers are re-architecting as well. >> It's all about- >> Hybrid applications are definitely what people want. >> 100% and the application stack, I think was the core focus that really shifted over time. Instead of just focusing on hybrid cloud infrastructure, it was really about how applications could leverage multiple types of clouds to be able to leverage the innovation and services that they could provide. >> You know, I've always been following the IT business for 30 years or so and it's always been an interesting trend. You buy something from a vendor and there's a trade-offs. And there's always the payback periods, but now I think with this announcement that's interesting is you got the product mix that allows customers to have choice and pick what they want. There's no more trade-offs. If they like cloud, they go to cloud. If they like on-premise, you go on-premises. >> It sounds like an easy concept, but the crazy part to this is the Cloud divide is real. They are very different environments. As we've talked to customers, they were very lost on how it was going to take and enterprise application and actually leverage the innovations within the Cloud. They wanted it, they needed it, but at the same time, they weren't able to deliver up on it. And so, we realized that the data layer, fundamentally was the area that could give them that bridge between those two environments. And we could add some core values to the Cloud for even the next generation developer who's developing in the Cloud to bring in, better overall resiliency. Management and all sorts of new features that they weren't able to take advantage of in traditional public cloud. >> You know Chugg wants to do minimal about the serviceless trend and how awesome that is. It's just, look at the resource pool as a serviceless pool of resource. So is this storageless? >> So it's still backed by storage, obviously. >> No, I was just making a joke. No wait, that you're looking at it as what serviceless is to the user. You guys are providing that same kind of storage pool, addressable through the application of, >> Correct >> as if it's storageless. And what's great about taking 100% software platform and moving it to the Cloud is, customer can spin this up in like minutes. And what's great about it is, they can spend many, many, many instances of these things for various different use cases that they have out there, and get true utility out of it. So they're getting the agility that they really want while not having to offset the values that they really come to love about PureStorage on-premises. Now they can actually get it all on the public cloud as well. >> I want to dig into the products a little bit. Before we get there, I want you to answer the question that's probably on people's minds. I know you've been at Pure, really from the beginning. So, you've seen the history. Most people look at you guys and say, well you're a hardware vendor. I have Pure boxes everywhere, you guys doing a great job. You've pioneered the Flash, speed game on storage. People want, kill latency as they say. You guys have done a great job. But wait a minute, this is software. Explain how you guys did this, why it's important. People might not know that this is a software solution. They might be know you for hardware. What's the difference? Is there a difference? Why should they care and what's the impact? >> So, great question. Since we sell hardware products, most people see us as a hardware company. But at the end of the day, the majority of vinge and dev is software. We're building software to make, originally, off the shelf components to be enterprise worthy. Over time we decided to optimize the hardware too, and that pairing between the software and hardware gets them inherently great values. And this is why we didn't just take our software and just kind of throw it into every cloud and say have it, to customers. Like a lot of folks did. We spent a lot of time, just like we did on our hardware platform, optimizing for AWS to start with. So that we could truly be able to leverage the inherent technologies that they have, but build software to make it even better. >> It's interesting, I interviewed Andy Bechtolsheim at VMworld, and he's a chairman of Arista. He's called, Les Peckgesem calls him the Rembrandt of motherboards. And he goes, "John, we're in the software business." And he goes, "Let me tell ya, hardware's easy. Software's hard." >> I agree. >> So everyone's pretty much in the software business. This is not a change for Pure. >> No, this is the same game we've been in. >> Great. Alright, let's get into the products. The first one is Cloud Block Store for AWS. Which is the way Amazon does the branch. So it's on Amazon, or for Amazon as they say. They use different words. So this is Pure software in the Cloud. Your company, technically Pure software. >> Yup. >> In the Cloud as software, no hardware. >> Yup. >> A 100% storage, API support, always encrypted, seamless management and orchestration, DR backup migration between clouds. >> Yup. >> That's kind of the core premise. So what does the product do, what's the purpose of the product. On the Amazon piece, if I'm a customer of Pure or a prospect for Pure, what does the product give me? What's the capabilities? >> Great. I would say that the biggest thing that customers get is just leverage for their application stack to be able to utilize the Cloud. And let me give you a couple of examples 'cause they're kind of fun. So first off, Cloud Block Storage is just software that sits in the Cloud that has many of the same utilities that run on-premises. Any by doing so, you get the ability to be able to do stuff like I want to replicate, as a DR target. So maybe I don't have a secondary site out there, and I want to have a DR target that spin up in the event of a disaster. You can easily set up bi-directional replication to the instance that you have running in the Cloud. It's the exact same experience. The exact same APIs and you get our cloud data management with Pure1 to be able to see both sites. One single pane of glass, and make sure everything is up and running and doing well. You could also though, leverage a test-dev environment. So let's saying I'm running production on-premises, I can then go ahead and replicate to the Cloud, spin up an instance for test-dev, and running reporting, run analytics. Run anything else that I wanted on top of that. And spin up compute relatively quickly. Maybe I don't have it on-prem. Next, we could focus on replicating for protection. Let's say for compliance, I want to have many instances to be able to restore back in the event of a disaster or in the event that I just want to look back during a period of time. The last part is, not just on-prem to the Cloud, but leveraging the Cloud for even better resiliency to take enterprise applications and actually move them without having to do massive re-architecture. If you look at what happens, Amazon recommends typically, that you have data in two different availability zones. So that when you put an application on top of it, it can be resilient to any sort of failures within an AZ. What we've done is we've taken our active cluster technology which is active-active replication between two instances, and made it so that you can actually replicate between two availability zones. And your application now doesn't need to be re-architected whatsoever. >> So you basically, if I get this right, you had core software that made all that Flash, on the box which is on-premise, which is a hardware solution. Which sounds like it was commodity boxes so this, components. >> Just like the Cloud. >> You take it to the Cloud as an amazing amount of boxes out there. They have tons of data centers. So you treat the Cloud as if it's a virtual device, so to speak. >> Correct. I mean the Cloud functionally is just compute and storage, and networking on the back end has been abstracted by some sort of layer in front of it. We're leveraging compute resources for our controllers and we're leveraging persistent storage media for our storage. But what we've done in software is optimize a bunch of things. An example just as one is, in the Cloud when you, procure storage, you pay for all of it, whether you leverage it or not. We incorporate de-dupe, compression, thin provisioning, AES 256 encryption on all data arrest. These are data services that are just embedded in that aren't traditionally found in a traditional cloud. >> This makes so much sense. If you're an application developer, you focus on building the app. Not worrying about where the storage is and how it's all managed. 'Cause you want persistent data and uni-managed state, and all this stuff going on. And I just need a dashboard, I just need to know where the storage is. Is it available and bring it to the table. >> And make it easy with the same APIs that you were potentially running on, on-premises. And that last part that I would say is that, the layered services that are built into Purity, like our snapshot technology and being able to refresh test-dev environments or create 10 sandboxes for 10 developers in the Cloud and add compute instances to them, is not only instantaneous, but it's space saving as you actually do it. Where as in the normal cloud offerings, you're paying for each one of those instances. >> And the agility is off the charts, it's amazing. Okay, final question on this one is, how much is it's going to cost? How does a customer consume it? Is it in the marketplace? Do I just click a button, spin up things? How's the interface? What's the customer interaction and engagement with the product? How they buy it, how much it costs? Can you share the interaction with the customer? >> So we're just jumping into beta, so a lot of this is still being worked out. But what I will tell you is it's the exact same experience that customers have come to love with Pure. You can go download the Cloud formation template into your catalog with an AWS. So you can spin up instances. The same kind of consumption models that we've built on-prem will be applied to cloud. So it will be a very similar consumption model, which has been super consumer friendly that customers have loved from us over the years. And it will be available in the mid part of next year, and so people will be able to beta it today, test it out, see how it works, and then put it into full production in mid part of next year. >> And operationally, in the work flows, the customers don't skip a beat. It's the same kind of format, languages and the words, the word flow. It feels like Pure all the way through. >> Correct. And not only are we a 100% built on a rest API, but all of the things we've built in with, Python libraries that automate this for developers, to PowerShell toolkits, to Ansible playbooks. All the stuff we've built on codeupyourstorage.com are all applicable to both sites and you get Pure1, our Cloud based management system to be able to see all of it in one single pane of glass. >> Okay, let's move on. So the next piece I think is interesting. I'll get your thoughts on this is that the whole protection piece. On-premises, really kind of held back from the Cloud, mainly to protect the data. So you guys got CloudSnap for AWS, what does this product do? Is this the protection piece? How does this work? What is the product? What's the features and what's the value? >> So, StorReduce was a recent acquisition that we did that enables de-duplication on top of an S3 target. And so it allows you to store an S3 de-duplicated into a smaller form factor and we're pairing that with both an on-premises addition which will have a flash plate behind it for super fast restores. So think of that as a caching tier for your backups, but then also be able to replicate that out to the public cloud and leverage store reduce natively in the public cloud as well. >> So that's the store reduce product. So store reduce on it is that piece. As an object store? >> It is, yes. And we pair that with CloudSnap which is natively integrated within FlashArray, so you can also do snapshots to a FlashBlade for fast restores for both NFS, and you can send it also to S3 in the public cloud. And so you get the inherent abilities to even do, VM level granularity or volume level granularity as well from a FlashArray directly, without needing to have any additional hardware. >> Okay so the data services are the; Block Storage, Store Reduce and CloudSnap on a four AWS. >> Correct. >> How would you encapsulate this from a product and solution standpoint? How would you describe that to a customer in an elevator or just a quick value statement? What's in it for them? >> Sure. So Pure's been seen by customers as innovation engine that optimized applications and allowed them to do, I would say, amazing things into the enterprise. What we're doing now, is we're evolving that solution out of just an on-premises solution and making it available in a very agile Cloud world. We know this world is evolving dramatically. We know people really want to be able to take advantage of the innovations within the Cloud, and so what we're doing is we're finally bridging the gap between on-premises and the Cloud. Giving them the same user experience that they've come to love with Pure and all of the Clouds that they potentially need to develop in. >> Okay so from the announcement standpoint, you guys got Cloud Block Storage limited public beta, right out of the gate. GA in mid 2019. CloudSnap is GA at announcement and Store Reduce is going into beta, first half of 2019. >> Correct, we're excited about it. >> So for the skeptics out there who are- Hey you know, Chadd, I got to tell ya. I love the Cloud, but I'm a little bit nervous. How do I test and get a feeling for- this is going to be simple, if I'm going to jump in and look at this. What should I look at first? What sequence, should I try this? Do you guys have a playbook, for them to either kick the tires or how should they explore to get proficient in the new solution. >> Good question. Right, so for one if you're a FlashArray customer, CloudSnap gives you the ability to be able to take this new entity, called a portable Snapshot. Which is data paired with metadata, and allow you to be able to move data off of a FlashArray. You can put it to an NFS target or you can send it to the Cloud. And so that's the most logical one that folks will probably leverage first because it's super exciting for them to be able to leverage the Cloud and spin up instances, if they'd like to. Or protect back to their own prem. Also, Cloud Block Storage, great because you can spin it up relatively quickly and test out applications between the two. One area that I think customers are going to be really excited about is you could run an analytics environment in the Cloud and spin up a bunch of compute from your production instance by just replicating it up into the Cloud. The last part is, I think backup is not super sexy. Nobody like to talk about it, but it's a significant pain point that's out there, and I think we can make some major in-roads in helping businesses get better SLAs. We're very, very interested to see the great solutions people bring with- >> So, I'm going to put you on the spot here and ask you, there's always the, love the cliche, is it a vitamin or is it an Asprin. Is there a pain point? So obviously backup, I would agree. Backup and recovery, certainly with the disaster, you see the wildfires going on here in California. You can't stop thinking about what the, disaster recovery plan and then you got top line growth with application developers. The kind of the vitamin, if you will. What are the use cases, low hanging fruit for someone to like test this out from a pain point standpoint. Is it backup and what's the growth angle? I wanted to test out this new solution, what should I look at first? What would you recommend? >> It's a very tough question. So, CloudSnap is obviously the easy one. I'd say Cloud Block Store is one that I think, people will. I look at my biggest, customers biggest challenges out there it's how do I get application portable. So I think Cloud Block Store really gives you the application portability. So I think it's finally achieving that whole, hybrid cloud world. But at the end of the day, backup is really big pain point that the enterprise deals with, like right this second. So there's areas where we believe we can add inherent values to them with being able to do fast restores from Flash. That meets SLA's very quickly and is an easy fix. >> And you guys feel good about the data protection aspect of this? >> Yes, very much so. >> Awesome. I want to get your personal take on this. You were early on in Pure. What's the vibe inside the company? This is Cloud and people love Cloud. There's benefits for Cloud, as well as on-premises. What's the mood like inside PureStorage? You've seen from the beginning, now you're a public company and growing up really, really fast. What's the vibe like inside PureStorage? >> It's funny, it hasn't really changed all that much, in the cultural side of the thing, of the business. I love where I work because of the people. The people bring so much fun to the business, so much innovation and we have a mindset that's heavily focused on customer first. And that's one of the things. I always tell this kind of story is, when we first started, we sat in a room on a whiteboard and wrote up, what is everything that sucks about storage. And instead of trying to figure out how we make a 2.0 version of some storage array, we actually figured out what are all the customer pain points that we needed to satisfy and then we built innovations to go do that. Not go chase the competition, but actually go alleviate customer challenges. And we just continue to kind of focus on customer first and so the whole company kind of, rallies around that. And I think you see a very different motion that what you do in most companies because we love hearing about customer results of our products. Engineering just will rally around when a customer shows up just to hear exactly their experience associated to it. And so with this, I think what they see is a continued evolution of the things we've been doing and they love seeing and providing customer solutions in areas that they were challenged to deal with in the past. >> What was some of the customer feedback when you guys started going, hey, you've got a new product, you're doing all of that early work. And you got to go talk to some people and knock on the, hey, what do you think, would you like the Cloud, a little bit of the Cloud. How would you like the Cloud to be implemented? What was some of the things you heard from customers? >> A lot of them said, if you can take your core tenets, which was simplicity, efficiency, reliability, and customer focus around consumption, and if you could give that to me in the Cloud, that would be the Nirvana. So, when we looked at this model, that's exactly what we did. We said, let's take what people love about us on-prem, and give 'em the exact same experience in the Cloud. >> That's great and that's what you guys have done. Congratulations. >> Thanks so much. >> Great to hear the Cloud story here Chadd Kenney, Vice President of Products and Solutions at PureStorage. Taking the formula of success on-premises with Flash and the success there, and bringing it to the Cloud. That's the big deal in this announcement. I'm John Furrier here in the Palo Alto studios, thanks for watching. (upbeat instrumental music)

[Music] [Music] [Music] [Music] ladies and gentlemen please welcome Red Hat senior vice president of engineering Matt Hicks [Music] welcome back I hope you're enjoying your first day of summit you know for us it is a lot of work throughout the year to get ready to get here but I love the energy walking into someone on that first opening day now this morning we kick off with Paul's keynote and you saw this morning just how evolved every aspect of open hybrid cloud has become based on an open source innovation model that opens source the power and potential of open source so we really brought me to Red Hat but at the end of the day the real value comes when were able to make customers like yourself successful with open source and as much passion and pride as we put into the open source community that requires more than just Red Hat given the complexity of your various businesses the solution set you're building that requires an entire technology ecosystem from system integrators that can provide the skills your domain expertise to software vendors that are going to provide the capabilities for your solutions even to the public cloud providers whether it's on the hosting side or consuming their services you need an entire technological ecosystem to be able to support you and your goals and that is exactly what we are gonna talk about this afternoon the technology ecosystem we work with that's ready to help you on your journey now you know this year's summit we talked about earlier it is about ideas worth exploring and we want to make sure you have all of the expertise you need to make those ideas a reality so with that let's talk about our first partner we have him today and that first partner is IBM when I talk about IBM I have a little bit of a nostalgia and that's because 16 years ago I was at IBM it was during my tenure at IBM where I deployed my first copy of Red Hat Enterprise Linux for a customer it's actually where I did my first professional Linux development as well you and that work on Linux it really was the spark that I had that showed me the potential that open source could have for enterprise customers now iBM has always been a steadfast supporter of Linux and a great Red Hat partner in fact this year we are celebrating 20 years of partnership with IBM but even after 20 years two decades I think we're working on some of the most innovative work that we ever have before so please give a warm welcome to Arvind Krishna from IBM to talk with us about what we are working on Arvind [Applause] hey my pleasure to be here thank you so two decades huh that's uh you know I think anything in this industry to going for two decades is special what would you say that that link is made right Hatton IBM so successful look I got to begin by first seeing something that I've been waiting to say for years it's a long strange trip it's been and for the San Francisco folks they'll get they'll get the connection you know what I was just thinking you said 16 it is strange because I probably met RedHat 20 years ago and so that's a little bit longer than you but that was out in Raleigh it was a much smaller company and when I think about the connection I think look IBM's had a long long investment and a long being a long fan of open source and when I think of Linux Linux really lights up our hardware and I think of the power box that you were showing this morning as well as the mainframe as well as all other hardware Linux really brings that to life and I think that's been at the root of our relationship yeah absolutely now I alluded to a little bit earlier we're working on some new stuff and this time it's a little bit higher in the software stack and we have before so what do you what would you say spearheaded that right so we think of software many people know about some people don't realize a lot of the words are called critical systems you know like reservation systems ATM systems retail banking a lot of the systems run on IBM software and when I say IBM software names such as WebSphere and MQ and db2 all sort of come to mind as being some of that software stack and really when I combine that with some of what you were talking about this morning along hybrid and I think this thing called containers you guys know a little about combining the two we think is going to make magic yeah and I certainly know containers and I think for myself seeing the rise of containers from just the introduction of the technology to customers consuming at mission-critical capacities it's been probably one of the fastest technology cycles I've ever seen before look we completely agree with that when you think back to what Paul talks about this morning on hybrid and we think about it we are made of firm commitment to containers all of our software will run on containers and all of our software runs Rell and you put those two together and this belief on hybrid and containers giving you their hybrid motion so that you can pick where you want to run all the software is really I think what has brought us together now even more than before yeah and the best part I think I've liked we haven't just done the product in downstream alignment we've been so tied in our technology approach we've been aligned all the way to the upstream communities absolutely look participating upstream participating in these projects really bringing all the innovation to bear you know when I hear all of you talk about you can't just be in a single company you got to tap into the world of innovation and everybody should contribute we firmly believe that instead of helping to do that is kind of why we're here yeah absolutely now the best part we're not just going to tell you about what we're doing together we're actually going to show you so how every once you tell the audience a little bit more about what we're doing I will go get the demo team ready in the back so you good okay so look we're doing a lot here together we're taking our software and we are begging to put it on top of Red Hat and openshift and really that's what I'm here to talk about for a few minutes and then we go to show it to you live and the demo guard should be with us so it'll hopefully go go well so when we look at extending our partnership it's really based on three fundamental principles and those principles are the following one it's a hybrid world every enterprise wants the ability to span across public private and their own premise world and we got to go there number two containers are strategic to both of us enterprise needs the agility you need a way to easily port things from place to place to place and containers is more than just wrapping something up containers give you all of the security the automation the deploy ability and we really firmly believe that and innovation is the path forward I mean you got to bring all the innovation to bear whether it's around security whether it's around all of the things we heard this morning around going across multiple infrastructures right the public or private and those are three firm beliefs that both of us have together so then explicitly what I'll be doing here number one all the IBM middleware is going to be certified on top of openshift and rel and through cloud private from IBM so that's number one all the middleware is going to run in rental containers on OpenShift on rail with all the cloud private automation and deployability in there number two we are going to make it so that this is the complete stack when you think about from hardware to hypervisor to os/2 the container platform to all of the middleware it's going to be certified up and down all the way so that you can get comfort that this is certified against all the cyber security attacks that come your way three because we do the certification that means a complete stack can be deployed wherever OpenShift runs so that way you give the complete flexibility and you no longer have to worry about that the development lifecycle is extended all the way from inception to production and the management plane then gives you all of the delivery and operation support needed to lower that cost and lastly professional services through the IBM garages as well as the Red Hat innovation labs and I think that this combination is really speaks to the power of both companies coming together and both of us working together to give all of you that flexibility and deployment capabilities across one can't can't help it one architecture chart and that's the only architecture chart I promise you so if you look at it right from the bottom this speaks to what I'm talking about you begin at the bottom and you have a choice of infrastructure the IBM cloud as well as other infrastructure as a service virtual machines as well as IBM power and IBM mainframe as is the infrastructure choices underneath so you choose what what is best suited for the workload well with the container service with the open shift platform managing all of that environment as well as giving the orchestration that kubernetes gives you up to the platform services from IBM cloud private so it contains the catalog of all middle we're both IBM's as well as open-source it contains all the deployment capability to go deploy that and it contains all the operational management so things like come back up if things go down worry about auto scaling all those features that you want come to you from there and that is why that combination is so so powerful but rather than just hear me talk about it I'm also going to now bring up a couple of people to talk about it and what all are they going to show you they're going to show you how you can deploy an application on this environment so you can think of that as either a cloud native application but you can also think about it as how do you modernize an application using micro services but you don't want to just keep your application always within its walls you also many times want to access different cloud services from this and how do you do that and I'm not going to tell you which ones they're going to come and tell you and how do you tackle the complexity of both hybrid data data that crosses both from the private world to the public world and as well as target the extra workloads that you want so that's kind of the sense of what you're going to see through through the demonstrations but with that I'm going to invite Chris and Michael to come up I'm not going to tell you which one's from IBM which runs from Red Hat hopefully you'll be able to make the right guess so with that Chris and Michael [Music] so so thank you Arvind hopefully people can guess which ones from Red Hat based on the shoes I you know it's some really exciting stuff that we just heard there what I believe that I'm I'm most excited about when I look out upon the audience and the opportunity for customers is with this announcement there are quite literally millions of applications now that can be modernized and made available on any cloud anywhere with the combination of IBM cloud private and OpenShift and I'm most thrilled to have mr. Michael elder a distinguished engineer from IBM here with us today and you know Michael would you maybe describe for the folks what we're actually going to go over today absolutely so when you think about how do I carry forward existing applications how do I build new applications as well you're creating micro services that always need a mixture of data and messaging and caching so this example application shows java-based micro services running on WebSphere Liberty each of which are then leveraging things like IBM MQ for messaging IBM db2 for data operational decision manager all of which is fully containerized and running on top of the Red Hat open chip container platform and in fact we're even gonna enhance stock trader to help it understand how you feel but okay hang on so I'm a little slow to the draw sometimes you said we're gonna have an application tell me how I feel exactly exactly you think about your enterprise apps you want to improve customer service understanding how your clients feel can't help you do that okay well this I'd like to see that in action all right let's do it okay so the first thing we'll do is we'll actually take a look at the catalog and here in the IBM cloud private catalog this is all of the content that's available to deploy now into this hybrid solution so we see workloads for IBM will see workloads for other open source packages etc each of these are packaged up as helm charts that are deploying a set of images that will be certified for Red Hat Linux and in this case we're going to go through and start with a simple example with a node out well click a few actions here we'll give it a name now do you have your console up over there I certainly do all right perfect so we'll deploy this into the new old namespace and will deploy notate okay alright anything happening of course it's come right up and so you know what what I really like about this is regardless of if I'm used to using IBM clout private or if I'm used to working with open shift yeah the experience is well with the tool of whatever I'm you know used to dealing with on a daily basis but I mean you know I got to tell you we we deployed node ourselves all the time what about and what about when was the last time you deployed MQ on open shift you never I maybe never all right let's fix that so MQ obviously is a critical component for messaging for lots of highly transactional systems here we'll deploy this as a container on the platform now I'm going to deploy this one again into new worlds I'm gonna disable persistence and for my application I'm going to need a queue manager so I'm going to have it automatically setup my queue manager as well now this will deploy a couple of things what do you see I see IBM in cube all right so there's your stateful set running MQ and of course there's a couple of other components that get stood up as needed here including things like credentials and secrets and the service etc but all of this is they're out of the box ok so impressive right but that's the what I think you know what I'm really looking at is maybe how a well is this running you know what else does this partnership bring when I look at IBM cloud private windows inches well so that's a key reason about why it's not just about IBM middleware running on open shift but also IBM cloud private because ultimately you need that common management plane when you deploy a container the next thing you have to worry about is how do I get its logs how do I manage its help how do I manage license consumption how do I have a common security plan right so cloud private is that enveloping wrapper around IBM middleware to provide those capabilities in a common way and so here we'll switch over to our dashboard this is our Griffin and Prometheus stack that's deployed also now on cloud private running on OpenShift and we're looking at a different namespace we're looking at the stock trader namespace we'll go back to this app here momentarily and we can see all the different pieces what if you switch over to the stock trader workspace on open shipped yeah I think we might be able to do that here hey there it is alright and so what you're gonna see here all the different pieces of this op right there's d b2 over here I see the portfolio Java microservice running on Webster Liberty I see my Redis cash I see MQ all of these are the components we saw in the architecture picture a minute ago ya know so this is really great I mean so maybe let's take a look at the actual application I see we have a fine stock trader app here now we mentioned understanding how I feel exactly you know well I feel good that this is you know a brand new stock trader app versus the one from ten years ago that don't feel like we used forever so the key thing is this app is actually all of those micro services in addition to things like business rules etc to help understand the loyalty program so one of the things we could do here is actually enhance it with a a AI service from Watson this is tone analyzer it helps me understand how that user actually feels and will be able to go through and submit some feedback to understand that user ok well let's see if we can take a look at that so I tried to click on youth clearly you're not very happy right now here I'll do one quick thing over here go for it we'll clear a cache for our sample lab so look you guys don't actually know as Michael and I just wrote this no js' front end backstage while Arvin was actually talking with Matt and we deployed it real-time using continuous integration and continuous delivery that we have available with openshift well the great thing is it's a live demo right so we're gonna do it all live all the time all right so you mentioned it'll tell me how I'm feeling right so if we look at so right there it looks like they're pretty angry probably because our cache hadn't been cleared before we started the demo maybe well that would make me angry but I should be happy because I mean I have a lot of money well it's it's more than I get today for sure so but you know again I don't want to remain angry so does Watson actually understand southern I know it speaks like eighty different languages but well you know I'm from South Carolina to understand South Carolina southern but I don't know about your North Carolina southern alright well let's give it a go here y'all done a real real know no profanity now this is live I've done a real real nice job on this here fancy demo all right hey all right likes me now all right cool and the key thing is just a quick note right it's showing you've got a free trade so we can integrate those business rules and then decide to I do put one trade if you're angry give me more it's all bringing it together into one platform all running on open show yeah and I can see the possibilities right of we've not only deployed services but getting that feedback from our customers to understand well how well the services are being used and are people really happy with what they have hey listen Michael this was amazing I read you joining us today I hope you guys enjoyed this demo as well so all of you know who this next company is as I look out through the crowd based on what I can actually see with the sun shining down on me right now I can see their influence everywhere you know Sports is in our everyday lives and these guys are equally innovative in that space as they are with hybrid cloud computing and they use that to help maintain and spread their message throughout the world of course I'm talking about Nike I think you'll enjoy this next video about Nike and their brand and then we're going to hear directly from my twitting about what they're doing with Red Hat technology new developments in the top story of the day the world has stopped turning on its axis top scientists are currently racing to come up with a solution everybody going this way [Music] the wrong way [Music] please welcome Nike vice president of infrastructure engineering Mike witig [Music] hi everybody over the last five years at Nike we have transformed our technology landscape to allow us to connect more directly to our consumers through our retail stores through Nike comm and our mobile apps the first step in doing that was redesigning our global network to allow us to have direct connectivity into both Asia and AWS in Europe in Asia and in the Americas having that proximity to those cloud providers allows us to make decisions about application workload placement based on our strategy instead of having design around latency concerns now some of those workloads are very elastic things like our sneakers app for example that needs to burst out during certain hours of the week there's certain moments of the year when we have our high heat product launches and for those type of workloads we write that code ourselves and we use native cloud services but being hybrid has allowed us to not have to write everything that would go into that app but rather just the parts that are in that application consumer facing experience and there are other back-end systems certain core functionalities like order management warehouse management finance ERP and those are workloads that are third-party applications that we host on relevent over the last 18 months we have started to deploy certain elements of those core applications into both Azure and AWS hosted on rel and at first we were pretty cautious that we started with development environments and what we realized after those first successful deployments is that are the impact of those cloud migrations on our operating model was very small and that's because the tools that we use for monitoring for security for performance tuning didn't change even though we moved those core applications into Azure in AWS because of rel under the covers and getting to the point where we have that flexibility is a real enabler as an infrastructure team that allows us to just be in the yes business and really doesn't matter where we want to deploy different workload if either cloud provider or on-prem anywhere on the planet it allows us to move much more quickly and stay much more directed to our consumers and so having rel at the core of our strategy is a huge enabler for that flexibility and allowing us to operate in this hybrid model thanks very much [Applause] what a great example it's really nice to hear an IQ story of using sort of relish that foundation to enable their hybrid clout enable their infrastructure and there's a lot that's the story we spent over ten years making that possible for rel to be that foundation and we've learned a lot in that but let's circle back for a minute to the software vendors and what kicked off the day today with IBM IBM s one of the largest software portfolios on the planet but we learned through our journey on rel that you need thousands of vendors to be able to sport you across all of your different industries solve any challenge that you might have and you need those vendors aligned with your technology direction this is doubly important when the technology direction is changing like with containers we saw that two years ago bread had introduced our container certification program now this program was focused on allowing you to identify vendors that had those shared technology goals but identification by itself wasn't enough in this fast-paced world so last year we introduced trusted content we introduced our container health index publicly grading red hats images that form the foundation for those vendor images and that was great because those of you that are familiar with containers know that you're taking software from vendors you're combining that with software from companies like Red Hat and you are putting those into a single container and for you to run those in a mission-critical capacity you have to know that we can both stand by and support those deployments but even trusted content wasn't enough so this year I'm excited that we are extending once again to introduce trusted operations now last week we announced that cube con kubernetes conference the kubernetes operator SDK the goal of the kubernetes operators is to allow any software provider on kubernetes to encode how that software should run this is a critical part of a container ecosystem not just being able to find the vendors that you want to work with not just knowing that you can trust what's inside the container but knowing that you can efficiently run that software now the exciting part is because this is so closely aligned with the upstream technology that today we already have four partners that have functioning operators specifically Couchbase dynaTrace crunchy and black dot so right out of the gate you have security monitoring data store options available to you these partners are really leading the charge in terms of what it means to run their software on OpenShift but behind these four we have many more in fact this morning we announced over 60 partners that are committed to building operators they're taking their domain expertise and the software that they wrote that they know and extending that into how you are going to run that on containers in environments like OpenShift this really brings the power of being able to find the vendors being able to trust what's inside and know that you can run their software as efficiently as anyone else on the planet but instead of just telling you about this we actually want to show you this in action so why don't we bring back up the demo team to give you a little tour of what's possible with it guys thanks Matt so Matt talked about the concept of operators and when when I think about operators and what they do it's taking OpenShift based services and making them even smarter giving you insight into how they do things for example have we had an operator for the nodejs service that I was running earlier it would have detected the problem and fixed itself but when we look at it what really operators do when I look at it from an ecosystem perspective is for ISVs it's going to be a catalyst that's going to allow them to make their services as manageable and it's flexible and as you know maintainable as any public cloud service no matter where OpenShift is running and to help demonstrate this I've got my buddy Rob here Rob are we ready on the demo front we're ready awesome now I notice this screen looks really familiar to me but you know I think we want to give folks here a dev preview of a couple of things well we want to show you is the first substantial integration of the core OS tectonic technology with OpenShift and then the other thing is we are going to dive in a little bit more into operators and their usefulness so Rob yeah so what we're looking at here is the service catalog that you know and love and openshift and we've got a few new things in here we've actually integrated operators into the Service Catalog and I'm going to take this filter and give you a look at some of them that we have today so you can see we've got a list of operators exposed and this is the same way that your developers are already used to integrating with products they're right in your catalog and so now these are actually smarter services but how can we maybe look at that I mentioned that there's maybe a new view I'm used to seeing this as a developer but I hear we've got some really cool stuff if I'm the administrator of the console yeah so we've got a whole new side of the console for cluster administrators to get a look at under the infrastructure versus this dev focused view that we're looking at today today so let's go take a look at it so the first thing you see here is we've got a really rich set of monitoring and health status so we can see that we've got some alerts firing our control plane is up and we can even do capacity planning anything that you need to do to maintenance your cluster okay so it's it's not only for the the services in the cluster and doing things that you know I may be normally as a human operator would have to do but this this console view also gives me insight into the infrastructure itself right like maybe the nodes and maybe handling the security context is that true yes so these are new capabilities that we're bringing to open shift is the ability to do node management things like drain and unscheduled nodes to do day-to-day maintenance and then as well as having security constraints and things like role bindings for example and the exciting thing about this is this is a view that you've never been able to see before it's cross-cutting across namespaces so here we've got a number of admin bindings and we can see that they're connected to a number of namespaces and these would represent our engineering teams all the groups that are using the cluster and we've never had this view before this is a perfect way to audit your security you know it actually is is pretty exciting I mean I've been fortunate enough to be on the up and shift team since day one and I know that operations view is is something that we've you know strived for and so it's really exciting to see that we can offer that now but you know really this was a we want to get into what operators do and what they can do for us and so maybe you show us what the operator console looks like yeah so let's jump on over and see all the operators that we have installed on the cluster you can see that these mirror what we saw on the Service Catalog earlier now what we care about though is this Couchbase operator and we're gonna jump into the demo namespace as I said you can share a number of different teams on a cluster so it's gonna jump into this namespace okay cool so now what we want to show you guys when we think about operators you know we're gonna have a scenario here where there's going to be multiple replicas of a Couchbase service running in the cluster and then we're going to have a stateful set and what's interesting is those two things are not enough if I'm really trying to run this as a true service where it's highly available in persistent there's things that you know as a DBA that I'm normally going to have to do if there's some sort of node failure and so what we want to demonstrate to you is where operators combined with the power that was already within OpenShift are now coming together to keep this you know particular database service highly available and something that we can continue using so Rob what have you got there yeah so as you can see we've got our couch based demo cluster running here and we can see that it's up and running we've got three members we've got an off secret this is what's controlling access to a UI that we're gonna look at in a second but what really shows the power of the operator is looking at this view of the resources that it's managing you can see that we've got a service that's doing load balancing into the cluster and then like you said we've got our pods that are actually running the software itself okay so that's cool so maybe for everyone's benefit so we can show that this is happening live could we bring up the the Couchbase console please and keep up the openshift console both sides so what we see there we go so what we see on the on the right hand side is obviously the same console Rob was working in on the left-hand side as you can see by the the actual names of the pods that are there the the couch based services that are available and so Rob maybe um let's let's kill something that's always fun to do on stage yeah this is the power of the operator it's going to recover it so let's browse on over here and kill node number two so we're gonna forcefully kill this and kick off the recovery and I see right away that because of the integration that we have with operators the Couchbase console immediately picked up that something has changed in the environment now why is that important normally a human being would have to get that alert right and so with operators now we've taken that capability and we've realized that there has been a new event within the environment this is not something that you know kubernetes or open shipped by itself would be able to understand now I'm presuming we're gonna end up doing something else it's not just seeing that it failed and sure enough there we go remember when you have a stateful application rebalancing that data and making it available is just as important as ensuring that the disk is attached so I mean Rob thank you so much for you know driving this for us today and being here I mean you know not only Couchbase but as was mentioned by matt we also have you know crunchy dynaTrace and black duck I would encourage you all to go visit their booths out on the floor today and understand what they have available which are all you know here with a dev preview and then talk to the many other partners that we have that are also looking at operators so again rub thank you for joining us today Matt come on out okay this is gonna make for an exciting year of just what it means to consume container base content I think containers change how customers can get that I believe operators are gonna change how much they can trust running that content let's circle back to one more partner this next partner we have has changed the landscape of computing specifically with their work on hardware design work on core Linux itself you know in fact I think they've become so ubiquitous with computing that we often overlook the technological marvels that they've been able to overcome now for myself I studied computer engineering so in the late 90s I had the chance to study processor design I actually got to build one of my own processors now in my case it was the most trivial processor that you could imagine it was an 8-bit subtractor which means it can subtract two numbers 256 or smaller but in that process I learned the sheer complexity that goes into processor design things like wire placements that are so close that electrons can cut through the insulation in short and then doing those wire placements across three dimensions to multiple layers jamming in as many logic components as you possibly can and again in my case this was to make a processor that could subtract two numbers but once I was done with this the second part of the course was studying the Pentium processor now remember that moment forever because looking at what the Pentium processor was able to accomplish it was like looking at alien technology and the incredible thing is that Intel our next partner has been able to keep up that alien like pace of innovation twenty years later so we're excited have Doug Fisher here let's hear a little bit more from Intel for business wide open skies an open mind no matter the context the idea of being open almost only suggests the potential of infinite possibilities and that's exactly the power of open source whether it's expanding what's possible in business the science and technology or for the greater good which is why-- open source requires the involvement of a truly diverse community of contributors to scale and succeed creating infinite possibilities for technology and more importantly what we do with it [Music] you know what Intel one of our core values is risk-taking and I'm gonna go just a bit off script for a second and say I was just backstage and I saw a gentleman that looked a lot like Scott Guthrie who runs all of Microsoft's cloud enterprise efforts wearing a red shirt talking to Cormier I'm just saying I don't know maybe I need some more sleep but that's what I saw as we approach Intel's 50th anniversary these words spoken by our co-founder Robert Noyce are as relevant today as they were decades ago don't be encumbered by history this is about breaking boundaries in technology and then go off and do something wonderful is about innovation and driving innovation in our industry and Intel we're constantly looking to break boundaries to advance our technology in the cloud in enterprise space that is no different so I'm going to talk a bit about some of the boundaries we've been breaking and innovations we've been driving at Intel starting with our Intel Xeon platform Orion Xeon scalable platform we launched several months ago which was the biggest and mark the most advanced movement in this technology in over a decade we were able to drive critical performance capabilities unmatched agility and added necessary and sufficient security to that platform I couldn't be happier with the work we do with Red Hat and ensuring that those hero features that we drive into our platform they fully expose to all of you to drive that innovation to go off and do something wonderful well there's taking advantage of the performance features or agility features like our advanced vector extensions or avx-512 or Intel quick exist those technologies are fully embraced by Red Hat Enterprise Linux or whether it's security technologies like txt or trusted execution technology are fully incorporated and we look forward to working with Red Hat on their next release to ensure that our advancements continue to be exposed and their platform and all these workloads that are driving the need for us to break boundaries and our technology are driving more and more need for flexibility and computing and that's why we're excited about Intel's family of FPGAs to help deliver that additional flexibility for you to build those capabilities in your environment we have a broad set of FPGA capabilities from our power fish at Mac's product line all the way to our performance product line on the 6/10 strat exten we have a broad set of bets FPGAs what i've been talking to customers what's really exciting is to see the combination of using our Intel Xeon scalable platform in combination with FPGAs in addition to the acceleration development capabilities we've given to software developers combining all that together to deliver better and better solutions whether it's helping to accelerate data compression well there's pattern recognition or data encryption and decryption one of the things I saw in a data center recently was taking our Intel Xeon scalable platform utilizing the capabilities of FPGA to do data encryption between servers behind the firewall all the while using the FPGA to do that they preserve those precious CPU cycles to ensure they delivered the SLA to the customer yet provided more security for their data in the data center one of the edges in cyber security is innovation and route of trust starts at the hardware we recently renewed our commitment to security with our security first pledge has really three elements to our security first pledge first is customer first urgency we have now completed the release of the micro code updates for protection on our Intel platforms nine plus years since launch to protect against things like the side channel exploits transparent and timely communication we are going to communicate timely and openly on our Intel comm website whether it's about our patches performance or other relevant information and then ongoing security assurance we drive security into every one of our products we redesigned a portion of our processor to add these partition capability which is adding additional walls between applications and user level privileges to further secure that environment from bad actors I want to pause for a second and think everyone in this room involved in helping us work through our security first pledge this isn't something we do on our own it takes everyone in this room to help us do that the partnership and collaboration was next to none it's the most amazing thing I've seen since I've been in this industry so thank you we don't stop there we continue to advance our security capabilities cross-platform solutions we recently had a conference discussion at RSA where we talked about Intel Security Essentials where we deliver a framework of capabilities and the end that are in our silicon available for those to innovate our customers and the security ecosystem to innovate on a platform in a consistent way delivering that assurance that those capabilities will be on that platform we also talked about things like our security threat technology threat detection technology is something that we believe in and we launched that at RSA incorporates several elements one is ability to utilize our internal graphics to accelerate some of the memory scanning capabilities we call this an accelerated memory scanning it allows you to use the integrated graphics to scan memory again preserving those precious cycles on the core processor Microsoft adopted this and are now incorporated into their defender product and are shipping it today we also launched our threat SDK which allows partners like Cisco to utilize telemetry information to further secure their environments for cloud workloads so we'll continue to drive differential experiences into our platform for our ecosystem to innovate and deliver more and more capabilities one of the key aspects you have to protect is data by 2020 the projection is 44 zettabytes of data will be available 44 zettabytes of data by 2025 they project that will grow to a hundred and eighty s data bytes of data massive amount of data and what all you want to do is you want to drive value from that data drive and value from that data is absolutely critical and to do that you need to have that data closer and closer to your computation this is why we've been working Intel to break the boundaries in memory technology with our investment in 3d NAND we're reducing costs and driving up density in that form factor to ensure we get warm data closer to the computing we're also innovating on form factors we have here what we call our ruler form factor this ruler form factor is designed to drive as much dense as you can in a 1u rack we're going to continue to advance the capabilities to drive one petabyte of data at low power consumption into this ruler form factor SSD form factor so our innovation continues the biggest breakthrough and memory technology in the last 25 years in memory media technology was done by Intel we call this our 3d crosspoint technology and our 3d crosspoint technology is now going to be driven into SSDs as well as in a persistent memory form factor to be on the memory bus giving you the speed of memory characteristics of memory as well as the characteristics of storage given a new tier of memory for developers to take full advantage of and as you can see Red Hat is fully committed to integrating this capability into their platform to take full advantage of that new capability so I want to thank Paul and team for engaging with us to make sure that that's available for all of you to innovate on and so we're breaking boundaries and technology across a broad set of elements that we deliver that's what we're about we're going to continue to do that not be encumbered by the past your role is to go off and doing something wonderful with that technology all ecosystems are embracing this and driving it including open source technology open source is a hub of innovation it's been that way for many many years that innovation that's being driven an open source is starting to transform many many businesses it's driving business transformation we're seeing this coming to light in the transformation of 5g driving 5g into the networked environment is a transformational moment an open source is playing a pivotal role in that with OpenStack own out and opie NFV and other open source projects were contributing to and participating in are helping drive that transformation in 5g as you do software-defined networks on our barrier breaking technology we're also seeing this transformation rapidly occurring in the cloud enterprise cloud enterprise are growing rapidly and innovation continues our work with virtualization and KVM continues to be aggressive to adopt technologies to advance and deliver more capabilities in virtualization as we look at this with Red Hat we're now working on Cube vert to help move virtualized workloads onto these platforms so that we can now have them managed at an open platform environment and Cube vert provides that so between Intel and Red Hat and the community we're investing resources to make certain that comes to product as containers a critical feature in Linux becomes more and more prevalent across the industry the growth of container elements continues at a rapid rapid pace one of the things that we wanted to bring to that is the ability to provide isolation without impairing the flexibility the speed and the footprint of a container with our clear container efforts along with hyper run v we were able to combine that and create we call cotta containers we launched this at the end of last year cotta containers is designed to have that container element available and adding elements like isolation both of these events need to have an orchestration and management capability Red Hat's OpenShift provides that capability for these workloads whether containerized or cube vert capabilities with virtual environments Red Hat openshift is designed to take that commercial capability to market and we've been working with Red Hat for several years now to develop what we call our Intel select solution Intel select solutions our Intel technology optimized for downstream workloads as we see a growth in a workload will work with a partner to optimize a solution on Intel technology to deliver the best solution that could be deployed quickly our effort here is to accelerate the adoption of these type of workloads in the market working with Red Hat's so now we're going to be deploying an Intel select solution design and optimized around Red Hat OpenShift we expect the industry's start deploying this capability very rapidly I'm excited to announce today that Lenovo is committed to be the first platform company to deliver this solution to market the Intel select solution to market will be delivered by Lenovo now I talked about what we're doing in industry and how we're transforming businesses our technology is also utilized for greater good there's no better example of this than the worked by dr. Stephen Hawking it was a sad day on March 14th of this year when dr. Stephen Hawking passed away but not before Intel had a 20-year relationship with dr. Hawking driving breakthrough capabilities innovating with him driving those robust capabilities to the rest of the world one of our Intel engineers an Intel fellow which is the highest technical achievement you can reach at Intel got to spend 10 years with dr. Hawking looking at innovative things they could do together with our technology and his breakthrough innovative thinking so I thought it'd be great to bring up our Intel fellow Lema notch Minh to talk about her work with dr. Hawking and what she learned in that experience come on up Elina [Music] great to see you Thanks something going on about the breakthrough breaking boundaries and Intel technology talk about how you use that in your work with dr. Hawking absolutely so the most important part was to really make that technology contextually aware because for people with disability every single interaction takes a long time so whether it was adapting for example the language model of his work predictor to understand whether he's gonna talk to people or whether he's writing a book on black holes or to even understand what specific application he might be using and then making sure that we're surfacing only enough actions that were relevant to reduce that amount of interaction so the tricky part is really to make all of that contextual awareness happen without totally confusing the user because it's constantly changing underneath it so how is that your work involving any open source so you know the problem with assistive technology in general is that it needs to be tailored to the specific disability which really makes it very hard and very expensive because it can't utilize the economies of scale so basically with the system that we built what we wanted to do is really enable unleashing innovation in the world right so you could take that framework you could tailor to a specific sensor for example a brain computer interface or something like that where you could actually then support a different set of users so that makes open-source a perfect fit because you could actually build and tailor and we you spoke with dr. Hawking what was this view of open source is it relevant to him so yeah so Stephen was adamant from the beginning that he wanted a system to benefit the world and not just himself so he spent a lot of time with us to actually build this system and he was adamant from day one that he would only engage with us if we were commit to actually open sourcing the technology that's fantastic and you had the privilege of working with them in 10 years I know you have some amazing stories to share so thank you so much for being here thank you so much in order for us to scale and that's what we're about at Intel is really scaling our capabilities it takes this community it takes this community of diverse capabilities it takes two births thought diverse thought of dr. Hawking couldn't be more relevant but we also are proud at Intel about leading efforts of diverse thought like women and Linux women in big data other areas like that where Intel feels that that diversity of thinking and engagement is critical for our success so as we look at Intel not to be encumbered by the past but break boundaries to deliver the technology that you all will go off and do something wonderful with we're going to remain committed to that and I look forward to continue working with you thank you and have a great conference [Applause] thank God now we have one more customer story for you today when you think about customers challenges in the technology landscape it is hard to ignore the public cloud these days public cloud is introducing capabilities that are driving the fastest rate of innovation that we've ever seen in our industry and our next customer they actually had that same challenge they wanted to tap into that innovation but they were also making bets for the long term they wanted flexibility and providers and they had to integrate to the systems that they already have and they have done a phenomenal job in executing to this so please give a warm welcome to Kerry Pierce from Cathay Pacific Kerry come on thanks very much Matt hi everyone thank you for giving me the opportunity to share a little bit about our our cloud journey let me start by telling you a little bit about Cathay Pacific we're an international airline based in Hong Kong and we serve a passenger and a cargo network to over 200 destinations in 52 countries and territories in the last seventy years and years seventy years we've made substantial investments to develop Hong Kong as one of the world's leading transportation hubs we invest in what matters most to our customers to you focusing on our exemplary service and our great product and it's both on the ground and in the air we're also investing and expanding our network beyond our multiple frequencies to the financial districts such as Tokyo New York and London and we're connecting Asia and Hong Kong with key tech hubs like San Francisco where we have multiple flights daily we're also connecting Asia in Hong Kong to places like Tel Aviv and our upcoming destination of Dublin in fact 2018 is actually going to be one of our biggest years in terms of network expansion and capacity growth and we will be launching in September our longest flight from Hong Kong direct to Washington DC and that'll be using a state-of-the-art Airbus a350 1000 aircraft so that's a little bit about Cathay Pacific let me tell you about our journey through the cloud I'm not going to go into technical details there's far smarter people out in the audience who will be able to do that for you just focus a little bit about what we were trying to achieve and the people side of it that helped us get there we had a couple of years ago no doubt the same issues that many of you do I don't think we're unique we had a traditional on-premise non-standardized fragile infrastructure it didn't meet our infrastructure needs and it didn't meet our development needs it was costly to maintain it was costly to grow and it really inhibited innovation most importantly it slowed the delivery of value to our customers at the same time you had the hype of cloud over the last few years cloud this cloud that clouds going to fix the world we were really keen on making sure we didn't get wound up and that so we focused on what we needed we started bottom up with a strategy we knew we wanted to be clouded Gnostic we wanted to have active active on-premise data centers with a single network and fabric and we wanted public clouds that were trusted and acted as an extension of that environment not independently we wanted to avoid single points of failure and we wanted to reduce inter dependencies by having loosely coupled designs and finally we wanted to be scalable we wanted to be able to cater for sudden surges of demand in a nutshell we kind of just wanted to make everything easier and a management level we wanted to be a broker of services so not one size fits all because that doesn't work but also not one of everything we want to standardize but a pragmatic range of services that met our development and support needs and worked in harmony with our public cloud not against it so we started on a journey with red hat we implemented Red Hat cloud forms and ansible to manage our hybrid cloud we also met implemented Red Hat satellite to maintain a manager environment we built a Red Hat OpenStack on crimson vironment to give us an alternative and at the same time we migrated a number of customer applications to a production public cloud open shift environment but it wasn't all Red Hat you love heard today that the Red Hat fits within an overall ecosystem we looked at a number of third-party tools and services and looked at developing those into our core solution I think at last count we had tried and tested somewhere past eight different tools and at the moment we still have around 62 in our environment that help us through that journey but let me put the technical solution aside a little bit because it doesn't matter how good your technical solution is if you don't have the culture and the people to get it right as a group we needed to be aligned for delivery and we focused on three core behaviors we focused on accountability agility and collaboration now I was really lucky we've got a pretty fantastic team for whom that was actually pretty easy but but again don't underestimate the importance of getting the culture and the people right because all the technology in the world doesn't matter if you don't have that right I asked the team what did we do differently because in our situation we didn't go out and hire a bunch of new people we didn't go out and hire a bunch of consultants we had the staff that had been with us for 10 20 and in some cases 30 years so what did we do differently it was really simple we just empowered and supported our staff we knew they were the smart ones they were the ones that were dealing with a legacy environment and they had the passion to make the change so as a team we encouraged suggestions and contributions from our overall IT community from the bottom up we started small we proved the case we told the story and then we got by him and only did did we implement wider the benefits the benefit through our staff were a huge increase in staff satisfaction reduction and application and platform outage support incidents risk free and failsafe application releases work-life balance no more midnight deployments and our application and infrastructure people could really focus on delivering customer value not on firefighting and for our end customers the people that travel with us it was really really simple we could provide a stable service that allowed for faster releases which meant we could deliver value faster in terms of stats we migrated 16 production b2c applications to a public cloud OpenShift environment in 12 months we decreased provisioning time from weeks or occasionally months we were waiting for hardware two minutes and we had a hundred percent availability of our key customer facing systems but most importantly it was about people we'd built a culture a culture of innovation that was built on a foundation of collaboration agility and accountability and that permeated throughout the IT organization not those just those people that were involved in the project everyone with an IT could see what good looked like and to see what it worked what it looked like in terms of working together and that was a key foundation for us the future for us you will have heard today everything's changing so we're going to continue to develop our open hybrid cloud onboard more public cloud service providers continue to build more modern applications and leverage the emerging technology integrate and automate everything we possibly can and leverage more open source products with the great support from the open source community so there you have it that's our journey I think we succeeded by not being over awed and by starting with the basics the technology was key obviously it's a cool component but most importantly it was a way we approached our transition we had a clear strategy that was actually developed bottom-up by the people that were involved day to day and we empowered those people to deliver and that provided benefits to both our staff and to our customers so thank you for giving the opportunity to share and I hope you enjoy the rest of the summer [Applause] I got one thanks what a great story would a great customer story to close on and we have one more partner to come up and this is a partner that all of you know that's Microsoft Microsoft has gone through an amazing transformation they've we've built an incredibly meaningful partnership with them all the way from our open source collaboration to what we do in the business side we started with support for Red Hat Enterprise Linux on hyper-v and that was truly just the beginning today we're announcing one of the most exciting joint product offerings on the market today let's please give a warm welcome to Paul correr and Scott Scott Guthrie to tell us about it guys come on out you know Scot welcome welcome to the Red Hat summer thanks for coming really appreciate it great to be here you know many surprises a lot of people when we you know published a list of speakers and then you rock you were on it and you and I are on stage here it's really really important and exciting to us exciting new partnership we've worked together a long time from the hypervisor up to common support and now around hybrid hybrid cloud maybe from your perspective a little bit of of what led us here well you know I think the thing that's really led us here is customers and you know Microsoft we've been on kind of a transformation journey the last several years where you know we really try to put customers at the center of everything that we do and you know as part of that you quickly learned from customers in terms of I'm including everyone here just you know you've got a hybrid of state you know both in terms of what you run on premises where it has a lot of Red Hat software a lot of Microsoft software and then really is they take the journey to the cloud looking at a hybrid of state in terms of how do you run that now between on-premises and a public cloud provider and so I think the thing that both of us are recognized and certainly you know our focus here at Microsoft has been you know how do we really meet customers with where they're at and where they want to go and make them successful in that journey and you know it's been fantastic working with Paul and the Red Hat team over the last two years in particular we spend a lot of time together and you know really excited about the journey ahead so um maybe you can share a bit more about the announcement where we're about to make today yeah so it's it's it's a really exciting announcement it's and really kind of I think first of its kind in that we're delivering a Red Hat openshift on Azure service that we're jointly developing and jointly managing together so this is different than sort of traditional offering where it's just running inside VMs and it's sort of two vendors working this is really a jointly managed service that we're providing with full enterprise support with a full SLA where the you know single throat to choke if you will although it's collectively both are choke the throats in terms of making sure that it works well and it's really uniquely designed around this hybrid world and in that it supports will support both Windows and Linux containers and it role you know it's the same open ship that runs both in the public cloud on Azure and on-premises and you know it's something that we hear a lot from customers I know there's a lot of people here that have asked both of us for this and super excited to be able to talk about it today and we're gonna show off the first demo of it just a bit okay well I'm gonna ask you to elaborate a bit more about this how this fits into the bigger Microsoft picture and I'll get out of your way and so thanks again thank you for coming here we go thanks Paul so I thought I'd spend just a few minutes talking about wouldn't you know that some of the work that we're doing with Microsoft Asher and the overall Microsoft cloud I didn't go deeper in terms of the new offering that we're announcing today together with red hat and show demo of it actually in action in a few minutes you know the high level in terms of you know some of the work that we've been doing at Microsoft the last couple years you know it's really been around this this journey to the cloud that we see every organization going on today and specifically the Microsoft Azure we've been providing really a cloud platform that delivers the infrastructure the application and kind of the core computing needs that organizations have as they want to be able to take advantage of what the cloud has to offer and in terms of our focus with Azure you know we've really focused we deliver lots and lots of different services and features but we focused really in particular on kind of four key themes and we see these four key themes aligning very well with the journey Red Hat it's been on and it's partly why you know we think the partnership between the two companies makes so much sense and you know for us the thing that we've been really focused on has been with a or in terms of how do we deliver a really productive cloud meaning how do we enable you to take advantage of cutting-edge technology and how do we kind of accelerate the successful adoption of it whether it's around the integration of managed services that we provide both in terms of the application space in the data space the analytic and AI space but also in terms of just the end-to-end management and development tools and how all those services work together so that teams can basically adopt them and be super successful yeah we deeply believe in hybrid and believe that the world is going to be a multi cloud and a multi distributed world and how do we enable organizations to be able to take the existing investments that they already have and be able to easily integrate them in a public cloud and with a public cloud environment and get immediate ROI on day one without how to rip and replace tons of solutions you know we're moving very aggressively in the AI space and are looking to provide a rich set of AI services both finished AI models things like speech detection vision detection object motion etc that any developer even at non data scientists can integrate to make application smarter and then we provide a rich set of AI tooling that enables organizations to build custom models and be able to integrate them also as part of their applications and with their data and then we invest very very heavily on trust Trust is sort of at the core of a sure and we now have more compliant certifications than any other cloud provider we run in more countries than any other cloud provider and we really focus around unique promises around data residency data sovereignty and privacy that are really differentiated across the industry and terms of where Iser runs today we're in 50 regions around the world so our region for us is typically a cluster of multiple data centers that are grouped together and you can see we're pretty much on every continent with the exception of Antarctica today and the beauty is you're going to be able to take the Red Hat open shift service and run it on ashore in each of these different locations and really have a truly global footprint as you look to build and deploy solutions and you know we've seen kind of this focus on productivity hybrid intelligence and Trust really resonate in the market and about 90 percent of Fortune 500 companies today are deployed on Azure and you heard Nike talked a little bit earlier this afternoon about some of their journeys as they've moved to a dot public cloud this is a small logo of just a couple of the companies that are on ashore today and what I do is actually even before we dive into the open ship demo is actually just show a quick video you know one of the companies thing there are actually several people from that organization here today Deutsche Bank who have been working with both Microsoft and Red Hat for many years Microsoft on the other side Red Hat both on the rel side and then on the OpenShift side and it's just one of these customers that have helped bring the two companies together to deliver this managed openshift service on Azure and so I'm just going to play a quick video of some of the folks that Deutsche Bank talking about their experiences and what they're trying to get out of it so we could roll the video that'd be great technology is at the absolute heart of Deutsche Bank we've recognized that the cost of running our infrastructure was particularly high there was a enormous amount of under utilization we needed a platform which was open to polyglot architecture supporting any kind of application workload across the various business lines of the third we analyzed over 60 different vendor products and we ended up with Red Hat openshift I'm super excited Microsoft or supporting Linux so strongly to adopting a hybrid approach we chose as here because Microsoft was the ideal partner to work with on constructs around security compliance business continuity as you as in all the places geographically that we need to be we have applications now able to go from a proof of concept to production in three weeks that is already breaking records openshift gives us given entities and containers allows us to apply the same sets of processes automation across a wide range of our application landscape on any given day we run between seven and twelve thousand containers across three regions we start see huge levels of cost reduction because of the level of multi-tenancy that we can achieve through containers open ship gives us an abstraction layer which is allows us to move our applications between providers without having to reconfigure or recode those applications what's really exciting for me about this journey is the way they're both Red Hat and Microsoft have embraced not just what we're doing but what each other are doing and have worked together to build open shift as a first-class citizen with Microsoft [Applause] in terms of what we're announcing today is a new fully managed OpenShift service on Azure and it's really the first fully managed service provided end-to-end across any of the cloud providers and it's jointly engineer operated and supported by both Microsoft and Red Hat and that means again sort of one service one SLA and both companies standing for a link firmly behind it really again focusing around how do we make customers successful and as part of that really providing the enterprise-grade not just isolates but also support and integration testing so you can also take advantage of all your rel and linux-based containers and all of your Windows server based containers and how can you run them in a joint way with a common management stack taking the advantage of one service and get maximum density get maximum code reuse and be able to take advantage of a containerized world in a better way than ever before and make this customer focus is very much at the center of what both companies are really centered around and so what if I do be fun is rather than just talk about openshift as actually kind of show off a little bit of a journey in terms of what this move to take advantage of it looks like and so I'd like to invite Brendan and Chris onstage who are actually going to show off a live demo of openshift on Azure in action and really walk through how to provision the service and basically how to start taking advantage of it using the full open ship ecosystem so please welcome Brendan and Chris we're going to join us on stage for a demo thanks God thanks man it's been a good afternoon so you know what we want to get into right now first I'd like to think Brandon burns for joining us from Microsoft build it's a busy week for you I'm sure your own stage there a few times as well you know what I like most about what we just announced is not only the business and technical aspects but it's that operational aspect the uniqueness the expertise that RedHat has for running OpenShift combined with the expertise that Microsoft has within Azure and customers are going to get this joint offering if you will with you know Red Hat OpenShift on Microsoft Azure and so you know kind of with that again Brendan I really appreciate you being here maybe talk to the folks about what we're going to show yeah so we're going to take a look at what it looks like to deploy OpenShift on to Azure via the new OpenShift service and the real selling point the really great part of this is the the deep integration with a cloud native app API so the same tooling that you would use to create virtual machines to create disks trade databases is now the tooling that you're going to use to create an open chip cluster so to show you this first we're going to create a resource group here so we're going to create that resource group in East us using the AZ tool that's the the azure command-line tooling a resource group is sort of a folder on Azure that holds all of your stuff so that's gonna come back into the second I've created my resource group in East us and now we're gonna use that exact same tool calling into into Azure api's to provision an open shift cluster so here we go we have AZ open shift that's our new command line tool putting it into that resource group I'm gonna get into East us alright so it's gonna take a little bit of time to deploy that open shift cluster it's doing a bunch of work behind the scenes provisioning all kinds of resources as well as credentials to access a bunch of different as your API so are we actually able to see this to you yeah so we can cut over to in just a second we can cut over to that resource group in a reload so Brendan while relating the beauty of what you know the teams have been doing together already is the fact that now open shift is a first-class citizen as it were yeah absolutely within the agent so I presume not only can I do a deployment but I can do things like scale and check my credentials and pretty much everything that I could do with any other service with that that's exactly right so we can anything that you you were used to doing via the my computer has locked up there we go the demo gods are totally with me oh there we go oh no I hit reload yeah that was that was just evil timing on the house this is another use for operators as we talked about earlier today that's right my dashboard should be coming up do I do I dare click on something that's awesome that was totally it was there there we go good job so what's really interesting about this I've also heard that it deploys you know in as little as five to six minutes which is really good for customers they want to get up and running with it but all right there we go there it is who managed to make it see that shows that it's real right you see the sweat coming off of me there but there you can see the I feel it you can see the various resources that are being created in order to create this openshift cluster virtual machines disks all of the pieces provision for you automatically via that one single command line call now of course it takes a few minutes to to create the cluster so in order to show the other side of that integration the integration between openshift and Azure I'm going to cut over to an open shipped cluster that I already have created alright so here you can see my open shift cluster that's running on Microsoft Azure I'm gonna actually log in over here and the first sign you're gonna see of the integration is it's actually using my credentials my login and going through Active Directory and any corporate policies that I may have around smart cards two-factor off anything like that authenticate myself to that open chef cluster so I'll accept that it can access my and now we're gonna load up the OpenShift web console so now this looks familiar to me oh yeah so if anybody's used OpenShift out there this is the exact same console and what we're going to show though is how this console via the open service broker and the open service broker implementation for Azure integrates natively with OpenShift all right so we can go down here and we can actually see I want to deploy a database I'm gonna deploy Mongo as my key value store that I'm going to use but you know like as we talk about management and having a OpenShift cluster that's managed for you I don't really want to have to manage my database either so I'm actually going to use cosmos DB it's a native Azure service it's a multilingual database that offers me the ability to access my data in a variety of different formats including MongoDB fully managed replicated around the world a pretty incredible service so I'm going to go ahead and create that so now Brendan what's interesting I think to me is you know we talked about the operational aspects and clearly it's not you and I running the clusters but you do need that way to interface with it and so when customers are able to deploy this all of this is out of the box there's no additional contemporary like this is what you get when you create when you use that tool to create that open chef cluster this is what you get with all of that integration ok great step through here and go ahead don't have any IP ranges there we go all right and we create that binding all right and so now behind the scenes openshift is integrated with the azure api's with all of my credentials to go ahead and create that distributed database once it's done provisioning actually all of the credentials necessary to access the database are going to be automatically populated into kubernetes available for me inside of OpenShift via service discovery to access from my application without any further work so I think that really shows not only the power of integrating openshift with an azure based API but actually the power of integrating a Druze API is inside of OpenShift to make a truly seamless experience for managing and deploying your containers across a variety of different platforms yeah hey you know Brendan this is great I know you've got a flight to catch because I think you're back onstage in a few hours but you know really appreciate you joining us today absolutely I look forward to seeing what else we do yeah absolutely thank you so much thanks guys Matt you want to come back on up thanks a lot guys if you have never had the opportunity to do a live demo in front of 8,000 people it'll give you a new appreciation for standing up there and doing it and that was really good you know every time I get the chance just to take a step back and think about the technology that we have at our command today I'm in awe just the progress over the last 10 or 20 years is incredible on to think about what might come in the next 10 or 20 years really is unthinkable you even forget 10 years what might come in the next five years even the next two years but this can create a lot of uncertainty in the environment of what's going to be to come but I believe I am certain about one thing and that is if ever there was a time when any idea is achievable it is now just think about what you've seen today every aspect of open hybrid cloud you have the world's infrastructure at your fingertips and it's not stopping you've heard about this the innovation of open source how fast that's evolving and improving this capability you've heard this afternoon from an entire technology ecosystem that's ready to help you on this journey and you've heard from customer after customer that's already started their journey in the successes that they've had you're one of the neat parts about this afternoon you will aren't later this week you will actually get to put your hands on all of this technology together in our live audience demo you know this is what some it's all about for us it's a chance to bring together the technology experts that you can work with to help formulate how to pull off those ideas we have the chance to bring together technology experts our customers and our partners and really create an environment where everyone can experience the power of open source that same spark that I talked about when I was at IBM where I understood the but intial that open-source had for enterprise customers we want to create the environment where you can have your own spark you can have that same inspiration let's make this you know in tomorrow's keynote actually you will hear a story about how open-source is changing medicine as we know it and literally saving lives it is a great example of expanding the ideas it might be possible that we came into this event with so let's make this the best summit ever thank you very much for being here let's kick things off right head down to the Welcome Reception in the expo hall and please enjoy the summit thank you all so much [Music] [Music]