>>Live from San Diego, California It's the Q Covering Koopa and Cloud Native Cot Brought to you by Red Cloud. Native Computing Pounding and its ecosystem >>Welcome back, toe Gorgeous. SAN Diego, California This is Q Khan Cloud Native Khan. 29 years. I'm still minimum. My co host is John Troyer, and this is the end of three days water wall coverage over 12,000 and 10 d Having a welcome to the program. Cassie, Who's the executive director at the national headquarters for v. American Red Cross. Matt. Thank you, American Red Cross. And thank you so much for joining us. >>Yeah. Thanks for having me. Uh, it's been a great conference so far. Uh, you know, we're here to share our story where as an end user on our journey with Cloud native with kubernetes Andi how that helps Red Cross do what we do, which is help people in need a cz best we can every day. >>Eso no matter what industry I talked to, everybody's dealing with change. There's always more things happening. American Red Cross. I mean, you know, it feels like I hear American Red Cross mentioned Maur a cz Time goes on because you know everything from, you know, things related to climate through, you know, global events and the like. So maybe before we get into some of the tech, just give us, you know, you know your role there and how kind of the changing world impact your organization. >>Sure. So my role is to support a few different business units. One is biomedical marketing. We try to recruit blood donors, too. Give blood at Red Cross Blood Dot or GE and other channels. That's obviously a significant part of what we d'oh were major player in the blood supply market in the US we provide service is to the armed forces, you know, in that regard as well. So that's part of it. Part of it is I work with humanitarian service is group as well to recruit financial donors on recruit volunteers. That's primarily through Red Cross. That or GE a T least as faras my group goes on, then corporate brand marketing and chapter related marketing and communications. So all that happens through Red Cross that Oregon Red Cross blood dot organ some related platforms on those our flagship brand products. >>Okay, And what led to the American Red Cross being part of this cloud. Native computing, Yeah, system. >>Our journey is a lot like, you know, a lot of other folks. We had a very, you know, monolithic type of architecture. We had all of these different business units with the different priorities, different timelines, different needs wrapped up into one big monster of a platform that, you know, kind of bundled up risk for everybody in this one platform. And, uh, you know, we'd always have collisions of priorities, mostly not to mention the resource issues of who's gonna work, you know, on what? At what time. And so a few years ago, we started talking about breaking that down. And, um, we've been lucky to have some technical leaders that are very aware of and welcoming to new cloud native technologies. We decided at that time to pursue, you know, a cloud native architecture. And what we have today in a few years later, is two years worth of being in production with a platform that runs on Amazon. We take advantage of a lot of the native orchestration tools there for running our clusters. And we've been able to service, you know, those different needs in a much more nimble way. We can release something for a Red Cross blood dot or without risking much on the financial donation side or on the volunteer recruitment side. And likewise, you know, for those other groups, we can kind of separate out the risks for each of those groups. And that's that's been a great, great benefit. >>You've been on the the vendor side. The for profit side is I t very different at the non profit. If you're looking, people are looking down, you get >>higher. Yeah, You know, I have been doing it a long time, a lot of different perspectives. But I think you know what I tried to do. And I would. I think I've seen work best is when I t is not the ticket taker, you know, integrated with the business. I'm very fortunate to have some business partners at Red Cross that collaborate. You know, every day we're having conversations every day. We have some people on our team that feel as though they're accountable for business outcomes, not just, you know, doing cool technology things, you know, For example, you know, multiyear evolution of process related to being more agile. We've got so much more integration and communication with business teams have gone from, you know, something like one release every five months now due to a weak, you know, and I think we could do more. It's just we don't have the need to do more. Um, and that's a huge, huge, big lift. You know, there's a lot of conversations that need to happen. Should make that work. >>Yeah, it's all a journey, right? We're all we're all improved. Continuous improvement, but so follow up there. So as a 90 leader for a very large organization, you know, they're one of the things people are saying this year. Wow. The conference is big. So many new technologies. So many new company somebody open source projects. You know, you're in the middle of this journey. You can't screw it up, right? That would be disastrous. So how do you How do you How did you and your organization look at new technologies and pick out which do technologies to try and incorporate them into your stack and your portfolio? >>Right. So we wanted to be a cloud native. We wanted a do, um, you know, focus on projects that where we knew there were skills in the marketplace, uh, that we could acquire at our price point. You know, we try to be good stewards of donor dollars at the end of the day, you know, all the money we have comes from folks like you and you guys who support Red Cross, you know, and thank you very much for all that generous support. And so we try to spend that money, uh, you know, very carefully. Way have some people who are, uh, you know, employees on our team made about 25 or so. But one of the great things we've been able to do with some of these technologies now is we have a program called Code for Good. It's a volunteer work force where we're here recruiting volunteers with the skill set that you know, they have a day job, but they have an interest in supporting Red Cross. Uh, maybe not financially. Maybe not with their blood, but they can give us some time on their skills, and we run it like an open source project. We set out a road map of features for six months or so. We have planning sessions, we say. Listen, you know if you can sign up for a feature that because you have two hours this week to work. Great. You have six hours. Great. You just had a baby, and you're not available for three months. Fine. You know, we we wanna have a, you know, a bench of people that can self select based on their time commitment, what to work on. And somehow it's been been working Great. You know, we started this in June. We have about 30 volunteers now on. We've already delivered an app for slack. That is kind of a workplace app where you can, you know, if your organization works with us, you can donate right from slack. You can give a schedule of blood donation, appointment, do things like that. >>I love that model. It's something that, you know we've looked at years ago. That kind of micro participation, if you will. You know, You think it's like, you know, Wikipedia wouldn't have been built if it wasn't for everybody. Just spending a little bit of time on it. Uh, I'm curious. Does something like participating with you know, this ecosystem I have generalized tools that people know and can plug in with, as opposed to, you know, having to know your direct stack Is that helpful To kind of be able to recruit people into that environment? What? What are the kind of most needed skills on dhe usages that you're recruiting? >>It is. You are learning. Curve at this point is much smaller than it was on our previous platform Because of the fact that we're using technologies people are familiar with, um, you know, things like Docker we use a lot. We just started evaluating Prometheus, another C N C F project for monitoring some non proud systems. Hopefully that'll graduate into production systems. So from a technology standpoint, yes, yes, we find that, you know, the people we talked with can walk in and be productive sooner. You know, there's still the Red Cross specific things they need to know about how we do business. But, um, you know, at least at this point, is that and not some proprietary system that they also have to learn >>any learnings that you've had participating in the c m. D. F. With the rollout of the technologies that you share with your peers, >>you know, I love the sea. NCF is very maintainer driven, You know, uh, and and user driven. I heard today at one of the analyst panels. I did. I think maybe 30% of people here are end users. >>That's a pretty >>large number. Um, you know, the fact that we can come here and learn about technologies meet people, meat vendors meet some of the people contributing code. Um, it's a lot different than you know, maybe some some summit sponsored by a for profit vendor that wants to, uh, you know, generate leads and sell you things. It feels much more community driven here and open to lots of different perspectives. >>So now what you looking forward to in the next few years? Both in terms of your stack and maybe coming back >>to Cuba? Yeah, way. It's funny. We've started to see other parts of Red Cross come to us toe, learn about kubernetes because the vendors they work with are mentioning these things. And and we have been early adopters, as far as you know, where across goes our group. Um and I think it's great if we can expand usage of, um, cloud native technologies to other parts of the organization on really get some economies of scale. So that's part of what we're trying to do is kind of internal, uh, consulting knowledge sharing collaboration on then, as far as what we're doing on our team way. Just really want to focus on. We're on a stable point in the platform, and then we want to do some things around monitoring and alerting that. Reduce those incident outages, too. Nothing. Hopefully, um, and work on that. >>You're working on a few projects that are that are being worked on here for That >>s So you have this Prometheus project. Like I said, we're piloting that, uh, you know, I would say in four or five months time, we'll know if that's going to be something we can, you know, put some more investment into >>All right, that want to give you the final word. Red cross dot org's code for good. I believe. The web. >>Yes, yes. >>What else? >>Your code for the number four. Good on. You know, if you're interested in volunteering, we need technical skills. We need team leadership skills, product owner skills, eh? So it's not just about you know, developing features and ops engineers as well. So thanks for your time. I want to say hi to my daughter, Peyton. It's late on the East Coast, so go to bed now, but thanks, folks. >>All right. What? Well, Matt, and actually, that is the final word for our day one of coverage for John Troyer. I'm stupid. And be sure to join us tomorrow. We've got two more days water wall coverage here. Lots of great speakers. Really appreciate. We've got the end users on. And, Matt, thank you so much. And, you know, great mission. The code for good. We definitely hope that the community here, you know, reaches out in connection Participates s Oh, that's it for today. Fixes all for watching.

>> From Seattle. Washington. It's the key you covering Goob Khan and Cloud Native Con North America. Twenty eighteen. Brought to you by Red Hat, the Cloud Native Computing Foundation and its ecosystem partner. >> Okay. Welcome back. It runs the cubes. Live coverage of three days Wall to wall here at Koop Khan and Cloud Native Khan, twenty eighteen in Seattle, where day three only actions happening. Mr Keep John for was to Minuteman where you have bread. French Compton, Tina. Director, Technical Market had read, had breaking down the container storage trends and directions. Costly containers are super important. That's happened. Communities has happened. Now. New things were happening around a lot of innovation. Thanks for coming on the Q. Appreciate it. >> Thanks for having me back. >> So what's the state of the art of containers of trends? Some of the market directions? What's going on around containers? >> Well, here at this show, of course, it's been all about service mesh. Right is Theo. Service mesh, dynamically dynamic discovery, dynamic invocation of services. But all of those things Well, a certain percentage of those things, according to Keynote, require some type of persistent so eso yet service message, service meshes and persistence. >> So storage is a big part of the networking and compute all working together. The cloud that's been a big part of it. What's what's important here in this show? What's going on this week. That's really impacting that piece of it. That container in storage you mentioned state versus stateless work area stateless is to find people from persistence in state become important and applications. How much conversation's been here this week on that piece >> we'll talk about this week, and then I'll talk about the last couple of weeks this week. There, there. Couple of significant thing is going on. They're going to sort of unleash innovation in persistence as it pertains to the coup bernetti subsystem. First, of course, is a container storage inter. See, you know, today, all the all of the volume plug ins have been entry. You want to change. You know, some vendor wants to change their their storage capabilities. They need to re compile the binaries. Very slow. Very, very non agile. Of course, with the advent of the container storage interface, it's okay. Here's the common interface. All the all the volume plugging providers right to that interface so they could. Then they Khun Iterated to their heart's content without having to change the the entry >> source. So the impact is what? Speed, agility, >> agility of innovation, allowing all those guys t innovate Kind of the second thing. That's so that's man of discussion this week. Another thing's been a discussion you've seen in the in some of the sessions and stuff is the operator framework, you know, coming a champion by the Coral West guys, of course. Now part of Red hat, the operator framework in terms of effectively automating things that human operators would do for complex subsystems. Such a CZ storage. Eso basic installation based basic upgrades, you know, monitoring those services. So when you know something falls over, what do you do with that type of stuff? So I'd say C s I container storage interface as well as operator from me. Those are some of the things have been talked about this week. I still want to go back. Talk about last week, but go ahead. >> I wonder if you could tease this out a little before. So, you know, lost five years. You know, container ization, Cooper Netease. You know, massive change the way we think about architectures. Things like networking in storage. I have often been the anchor to kind of hold us down to be ableto make changes faster. Virtual ization helped some, but you know, container ization. We're gonna have to fix some of these same things. What conversations you're having with customers, You know, give us the latest on the, you know, the state versus state falls we heard in the keynote. It was They said forty percent of deployments have, you know, st full applications out there spending on numbers. And, you know, it's definitely has been growing. And at least I can do it as opposed to, you know, two years ago, it was like, Okay, we're doing containers, but we're just going to stateless for now, and we'll try to figure out what architectures goingto work. Even a year ago at this show, I heard in the back rooms there were lots of arguments as to which one of the storage projects was going to lead and seems seems like we're getting some maturity. I hope we hope to give us some visibility is where we are, and you know what's working and what still needs to be done. >> So although the industry talks about serve earless there, not yet talking about data lists, the or storage lists. I mean, you know, if we threw out the basic principle of data gravity data is the sun around which applications services rotate And so even I mean, even stateless aps stateless app Still do I owe frequently? The io of stateless apse is, you know, be arrest Will puts and gets to an object store that actually brings me. So let's let's talk about let's unpack the stateless and then let's go to St ful. So I'm gonna come back. Tio some of the conversations. A couple of weeks ago, Red had announced the acquisition of Nuba and Israeli Company. So when you think about what new Bob Plus sef due to provide stateless aps with a common set of Davis, a common set of David data services across the hybrid and multi cloud so those stateless app saying, Okay, I'm going to do I'm going to rest well puts and gets. But, man, it's complicated. If I'm gonna have to develop to various proprietary protocols I've got, you know, the is your blob protocol. I've got a W. S s three. I'm talking Teo Google persistent disc. And then if I want to run hybrid, I'm also talking to SEF objects storage on premises. And if I'm a developer I'm thinking, man, Wouldn't it be nice if I had a common set of David data services, including common protocol to talkto all of those different cloud storage back end? So, Nuba some people kind of call it a cloud storage controller provides that kind of common data services. So things like common FBI protocol? Um, things like mirroring. So you you want to write, right Once you're uprights once and it smeared across the various cloud object storage back ends to facilitate easy migration. The second one I wanna uproot to move over here. Your data is already there. So that's, uh that's a couple of reasons. And some of the conversation from a couple weeks ago about how Nuba plus self are helping stateless aps get Teo hybrid and multi cloud >> this. I think that is a great point. You have a hybrid cloud and multi cloud coming around the corner, which is about choice, Right? But see, I CD pipe lining of having a consistent developer environment clearly is one of the main benefits we're seeing in this community here. Okay, I got some sulfur developers with crank teams move around that consistency, no matter where were the environment is just really good goodness. Their storage is interesting and data is that because you're right, the sun is the data and every is orbiting around it. That's the Holy Grail. This is what people want. They want addressable data. They wanted real time. They wanna have an access. They don't want to do all this code to configure manage data, and it's complicate. Got data warehouses? You got time. Siri's data so date is getting more complicated, but it needs to be simple. So this is kind of challenge of the industry. How are you guys seeing that with open ship? How is your container piece fit in? How do you guys make that easy for customers to say? Look, I want to have that data like I wanted intelligent, that brick of access to data. So my abs don't have to do all the heavy lifting almost like Dev ops for data. It's like day tops, like I need to have programmable data on the absolutely which, which have thoughts on that. >> So first I wanna I wanna address that in two ways. The first is about open shipped itself that what you described is in fact, the sweet spot of what open shift is providing a common set of Cooper Nettie Services. Plus. See, I see the pipeline services for developers and operation staff independent of your cloud infrastructures. So whether open shift is running on top of a heavy west, whether it's running on top of his your whether it's running on top of the G, C. P. Whether it's running on premises on bare metal, you know, common set of cou bernetti services and CD pipeline services. Okay, that so what you described there's wanted to just highlight that That is open ship hybrid multi >> valuable check. That's awesome data >> now coming down. Coming down to data. So, in fact, open shift container storage is the mirror analog to open shift for that, providing a common set of Cooper Netease volume services. Independent of what? The storage substrate. ID. So think about it. If you're If you're inside of eight of us, you've got CBS is what's you know? When in Rome, act as the Romans. You've got E. B s there when you're inside of eight of us. Well, the type of communities volumes service of the CBS provides natively differed them for instance, when you're on premises and it's surfacing via and NFS plug in, maybe different. Likewise. We're inside of a CZ. You're with your persistent disco, so open shift container storage device the same type of abstraction Lee are providing a common set of cou bernetti communities volumes services independent of what? The storage server layer is so >> cool you guys was tracked away the complexity. So the APP developer doesn't do anything about storage on those discreet platforms, >> doesn't know anything about storage and provides a common set of services instead of Well, let's see, this is running on this cloud. I don't have the have a different set of services, so common set of services. >> So one of things I love about talking right out of the shows is you actually have a lot of customers that are doing this way. Actually, we spoke to one of your customers yesterday. Talk about how you know communities is helping them create sustainable data centers over in Europe. In the Nordics, especially so communities is awesome. But what's really awesome is the things that we can do on top of it. I wonder if you've got, you know, help connect some of this toe. You know, your customers really things, you know? How does this, you know, change the game? How does it change their teams? You know, what can you share with us? >> One of things that I can't. What's what's top of mind. So what's not top of mind for me at the moment is you know what kind of knew how their reinventing the world what is top of mind with me right now? We've just been studying. Our our results is we look back and this is a little bit of a A Okay? It's a trend, but it's a different kind of friend you're talking about. In the last six quarters, we've had six hundred percent growth with open ship container storage. Um, so And now we send last six quarters were also at a point. Now we're seeing some of those same folks from the Nordics here. You're describing that are coming back now, you know, they have experimented on, So there are some There are Cem Cem cruise ship. There's a cruise ship company that is deployed this on on ships. What we're now seeing. What's very gratifying for us is they're coming back now for a second pass. Now, a year into it, it's okay. Clearly, it must be providing enough value that you come back. Okay. I want to buy this for another ship or more shifts. That's gratifying for us. The first year was, let's see. Let's try this uber Netease, this open ship container store stuff out. But, you know, coming back to the trough for another take, It's good for us. >> And what's going around the corner? He opens shifting, doing great. I love this abstraction layer we're seeing for the first time in the industry, clear visibility and a real value proposition. When I were joking yesterday, you know, we were at open stack years ago, or even Cube con three years ago. We would ask the question If you had a magic wand, what would you hope to have happened? It's actually some of the things that are actually happening. I mean, clean, heavy lifting is gone, and all the developer side consistency, productivity, better advantage on the application development side and then taking away all the hassles of having that she trained people on multiple clouds. So this is kind of happening. What's next? So what's the next next, uh, bowling pin to fall down? What's the, you know, Hit the front ten. What's next? What's going on? How do you guys see the next innovation around Open ship and storage containers, >> cloud independent data services and mobility. So independent of the clouds. And again, it's hybrid, too. So you don't want to be locked into your own cloud either. So cloud independent data services and mobility. So he said, Listen, I want to be I want to have a common de doop compression mirroring, but I want to sit in the layer above my clouds back to the data gravity thing. I want to ensure that my data is where I need it on different clouds. So I'm elevating to a new layer this this cloud storage controller, this this cloud independent set of data services way. Think that's where the pucks going? >> Yeah, I think the data date is critical, I think. Way said years ago. Data ops. There's a Dev ops model for data. You look at that way's not just putting into a data lake actually making it useful. Yeah, Thanks. Come on. Cuba. Here. Bringing all the data here. The Cube. We're sharing it here. Live in Seattle. Is our third year coop coming there from the beginning? That's the cubes coverage of Cloud Native Khan and Coop gone. Bring all the action here. Was red hot on the Cube. Back with more live coverage. Stay with us. Day three, three days ago off the wall. Coverage will be back after this short break.