we've made just tremendous progress over the last several years with Microsoft you know started back in 2015 where we you know cross certified hypervisors and that's kind of a basic you know let's work together over the last couple years it's truly blossomed into a really good partnership where you know I think they've and we both gotten over this you know Linux vs. Windows thing and you know I said we've gotten over I think we both recognized you know we need to serve our customers in the best possible way and that clearly means is two of the largest infrastructure software providers working closely together and what's been interesting as we've gone forward we find more and more common ground about how we can better serve our customers whether that's you know what might sound mundane that's a big deal sequel server on realm and setting benchmarks around that or dotnet running on our platforms now all the way to really being able to deliver a hybrid cloud with a seamless experience with openshift from you know on premise - - to Azure and I mean having to H Bank on States twenty five thousand containers running in production moving back and forth - sure and I think it's more building on what I talked to you about a year ago if I remember last May May of 2018 in San Francisco so I was exposing very heavily look the world's going to move towards containers the world is already embraced Linux this is the time to have a new architecture that enables hybrid much along the lines that gem and all of the clients as well as Ginni and Sasha we're talking about on stage yesterday so you put all that together and you say that is what we mentioned last year and we were clear that is where the world is going to go nice step forward a few months from there into October of 2018 and on 29th of October we announced that IBM intends to acquire Red Hat so then you say wow we put actually our money where amount was we were talking about the strategy we were talking about Linux containers openshift the partnership we announced last May was IBM software products together with OpenShift that is we already believed in that but now this allows us coming together it's it's more like a marriage then sort of loose partners passing each other in the middle of the night we are so excited and you know having put in all the time part of this is representing all the work the team has done and the communities have done when you think about all the work that goes into a Linux distribution it is everybody it's the community's it's the partners so we released the Red Hat Enterprise Linux eight beta in November mid-november we've had 40,000 downloads of that beta since November people who have provided feedback and comments suggestions all of that fed into what we've released today as the Red Hat Enterprise Linux eight general availability so it's a big day and part of it is we're just so proud of how we've done it and what we've done and we've really redefined what are not the value of an operating system with Red Hat Enterprise limits eight tech transformation started about ten years ago bean CI over the company about ten years and frankly the first five years were just fixing the basics so getting in place what we'd call world-class systems doing a bunch of stuff on resilience and security and all of that kind of stuff and the other thing and this is the dramatic change you know ten years ago when I joined the company we were 85% outsource to managed service vendors so I had technology people that basically were signing contractors and managing service agreements if we didn't have technology DNA and so you know over those five years and the full ten years actually we've been to not about just in sourcing and rebuilding our technical muscle if you like so now we're we've gone from 85% outsource to 90% in sourced so we run build and manage our own we're at word now a technology company yeah and and five years ago we had a real big shift and you know we were we were closest to what was going on in China and so probably saw this before many many of the other banks saw this around the world of what Alibaba was doing with ant financial and $0.10 and this whole just just complete disruption of how customers interact with the banking industry so we got an early lead on this digital transformation and really for the last five six years would be doubling down on building a pure digital offering and we see ourselves as a technology company providing banking services not as a bank with some technology department in the backend open source is the innovation model going forward period end of story full stop and I think as I said in my keynote yesterday you know leading up to the the biggest acquisition ever for a software company not an open source software coming a software company that happened to be an open source software company I don't think there's any doubt that that open source has one here here today it and it's because of the pace of innovation yeah our goal is to make sure we're supporting those upstream communities so all of all of Red Hat software is open source and we work with a whole community of individuals and companies and the upstream open source software and we want to make sure that we're not just contributing features that we want but that we're a good player or that we're helping to make sure those communities are healthy and so for a number of the projects that were involved in we actually assigned a full-time Community Manager a community lead to help make sure that project is healthy so we have someone on everything from Saif and Gloucester to fedora to kubernetes I'm just making sure the community does well yeah we do a little bit of both and so a lot of it is responding to the community and that's one of the areas that Red Hat is really excelled as taking what's popular what's working upstream and helping moving along make it a stable product or stable solution that developers can use but we also have a certain agenda or certain platforms that we want to present so we start from like various runtimes to actually contain our platforms and so we want to have to kind of drive some of that initiatives on our own to help drive fill that need because we hear it from customers a lot it's like things are doing are great but like there's all these projects that need to come together sort as a product or unified experience and so we spend a lot of our time trying to bring those things together as a way to help developers do those different tasks and also focus across like not just the Java runtimes which we hit a lot of Java so you might have baked security in right I mean we have a secure supply chain and you talk about difficult things for la right every package that we that comes in that is we totally refresh everything from upstream but when they come in we have to inspect all the crypto we have to run them through security scans vulnerability scanners we've got three different vulnerability scanners that we're using we run them through penetration testing so there's a huge amount of work that just comes just to inherit all that from the upstream but in addition to that we've put a lot of work into making sure that well our crypto has to be Fitz certified right which means you've got to meet standards we also have work that's gone in to make sure that you can enable a security policy consistently across the system so that no application that you load on can violate your security policy we've got enough tables in their new firewalling Network bound disk encryption that actually it kind of ties in with a lot of the system management work that we've done so a thing that I think differentiates rl8 is we put a lot of focus on making it easy to use on day one and easy to manage day two well we're not getting there were there what that allows us to do is to take the reference designs that we have and the testing that we've we've previously validated with Intel and Red Hat and be able to snap pieces together so it's just a matter of what's different and unique for the client in the client situation and their growth pattern what's great about trueskill is that in this model is that we can predictably analyze or consumption forward based on the business growth so for example if you're using open shipped and you start with a small cluster for say one or two lines of business as they adopt DevOps methodologies going from either waterfall or agile we can we can predictably analyze the consumption forward that they're going to need so they can plan years in advance as they progress and as such the other snap-ins say uh storage that they're going to need for data and motion or data at rest so it's it's actually smarter and what that ends up doing is obviously saving the money but it saves some time you know typical model is going back to IT and saying we need these servers we need the storage and the software and bolt it all together and the IT guys are you know hair on fire running around already so so they can you know as long as IT approves it they can sort of bypass that that big heavy lift we're trying to do is create role models for women and girls who would like to participate in technology but perhaps are not sure that that's the way that they can go and they don't see people that are like them so they're less tendency to join into this type of communities so with the community award winner we're looking at a professional who's been contributing to open source for a period of time and with our academic winner we're looking to spur more people who are in university to think about it and of course the big idea is you'll all be looking at these women as people that will inspire you to potentially do more things with open source and more things with technology we've been hearing for many many years that we definitely need to have more gender diversity in tech in general in an open source and Red Hat is kind of uniquely situated to focus on the open source community and so with our role is the open source leader we really feel like we need to make that commitment and to be able to foster that right so so Sierra's a supercomputer and what's unique about these systems is that we're solving there's lots of systems that network together maybe are bigger a number of servers than us but we're doing scientific simulation and that kind of computing requires a level of parallelism and it's very tightly coupled so all the servers are running a piece of the problem they all have to sort of operate together if any one of them is running slow it makes the whole thing go slow so it's really this tightly coupled nature of supercomputers that make things really challenging you know we talked about performance if if one server is just running slow for some reason you know everything else is going to be affected by that so we really do care about performance and we really do care about just every little piece of the hardware you know performing as it should so we thought okay let's take all of these best practices that we have and build more or less a methodology around it how to make this actually works like how to do this we really broke it down into like individual sprints do dissin sprint one the distance sprint do to really have the results within three months six months 12 months whatever the places that you want to run on and then we realize talking to customers this by itself isn't still enough so that's why we started to open up this to an entire ecosystem so we brought ecosystem partners along like working closely with red a lot of other companies but also system integrators who can help us we speak up projects because we as a company are software companies we're not a services or consulting company and we do support customers and some of those engagement but if you think of like a really fortune 500 company that's a multi-year project it will keep hundreds of busy people busy so to recap like built-in methodology we built the ecosystem to deliver on that promise at scale and now the last step was we as we were doing this we also built like a reference architecture for it and was just in an internal IDE so how do we like structure this bill that reference architecture and then realize okay I think it's kind of like super helpful for customers so that this way we then decided to open source this reference architecture is fabric as well to like the entire software community so they can also use it so technically these three pieces it's the methodology it's the ecosystem and it's like the reference architecture that you can work with to help you achieve you [Music]

(upbeat music) >> Announcer: Live from Boston, Massachusetts, it's theCUBE, covering your Red Hat Summit 2019. Brought to you by Red Hat. >> And welcome back to Boston, we continue our coverage here in theCUBE of the Red Hat Summit and welcoming now to theCUBE stage for the first time, I believe, David Gledhill. Who is the group chief information officer and head of group technology and operations at DBS Bank. David, good morning to you. >> Morning, hi, it's great to be here. >> All the way from Singapore, and he was early for the segment this morning. So you get extra points for that, congratulations. >> Put that up to jet lag. (men laughing) >> Thanks for being with us. David, anymore we talk about companies in general, everybody says everybody's a tech company now, right? Not the way it used to be. How is that playing out in your world in financial services as far as how deeply ingrained you have to be with the technology? >> Yeah, so very much, we are. Tech transformation started about 10 years ago. Been CIO of the company about 10 years. And frankly, the first five years were just fixing the basics. So getting in place what we'd call world-class systems. Doing a bunch of stuff on resilience and security and all of that kind of stuff. And the other thing, and this is the dramatic change, you know 10 years ago when I joined the company, we were 85% outsourced to managed service vendors. So I had technology people that basically were signing contractors and managing service agreements. We didn't have technology DNA. Over those five years and a full 10 years actually. We've been doing a lot about just insourcing and rebuilding our technical muscle if you like. So now we're, we've gone from 85% outsourced to 90% insourced. So we run, build and manage our own. We're now a technology company. >> And five years ago, we had a real big shift and we were closest to what was going on in China and so probably saw this before many, many of the other banks saw this around the world. Of what Alibaba was doing with Ant Financial and Tencent and this whole, just complete disruption of how customers interact with the banking industry. So we got an early lead on this digital transformation and really for the last five, six years have been doubling down on building a pure digital offering and we see ourselves as a technology company providing banking services, not as a bank with some technology department in the backend. >> Yeah, I'd love if you can, a little bit, to help us dig into that because, I think back it was okay, what does digitization mean 10 years ago, it was like oh, okay, I need to make sure I have a good website and maybe a good mobile app. Which is a fine starting piece, and also the piece you talked about is when it was outsourced, I'm managing pieces but I sign up for what I need today and when the business needs something, those outsources aren't necessarily tied to them, so you're playing telephone with them. Most the companies I've talked to that have brought skills back inside, it's because the needs of the business are constantly asking for more and it can't be well, it's not part of our contract with what we have. We'll get to that in a year or two. >> Yeah, yeah, so that's a very interesting shift. It plays out in a number of different dimensions. First of all, let me go into that question of business and tech and that separation. When we were managed service, it was literally writing contracts and the specs and handing to vendors. It was just a horrible process. And how can you be a modern technology firm like that? So insourcing, for us, was one big thing to owe those people, but when you insource, then you end up with a business unit and a technology unit. And you still have got silos, so how do you break that? Because that really is a problem. If you look at the way technology companies work, they don't work like that. Five years ago when we said, okay, how do you make that flip to being the digital company? We went very deep into how some of the great technology companies operate. We wanted to understand, what is it? How does that DNA work? How does that culture work? How do they organize themselves? How do they build technology? How do they become agile, speed to market? And so we looked at, we studied Google, Amazon, Netflix Apple, LinkedIn, Facebook and we call them the Gandalf companies. And we said, how can we be more like them? Well, a Gandalf is missing a D. And fortunately at DBS, we happen to have a D. (laughing) So our goal became how do we become the D in Gandalf? And that was just like a lightening rod through the organization because all of the sudden it said to our people, forget about biz and tech and things. You need to think about how these technology comp operates and be more like them. Which means there's no separation, there are no silos we are together building great technical products for our customers so we need to re-think the organization to make sure that happens. >> There's magic. (laughing) You've got a saying, making banking joyful. >> Yep. >> All right, which is not exactly the emotion that I associate with having to deal with my bank. It's fine, but joyful? A very unusual adjective there. What's that all about? And again, at the end of the day, how does technology enhance that? How does that compliment that and really boosted that? >> Yeah, so it was quite a radical moment for us. That came up, we were at a leadership meeting and talking about what is our purpose and how do we. Lots of people talk about customer journey, thinking and stuff like that but how do you bring that to life and one of the execs there said, well what about making banking joyful? And the rest of us just looked at him like he was from a different planet. Saying, are you kidding, what do you mean by that? But as we thought about it more, it has a great meaning and a great purpose to it, that we're not there just to do transactions but we're there to enrich lives, create new businesses, to make customers feel great in their financial stability, in the way they deal with us. And it applies on so many levels. So if you're a bank teller, you understand how to make banking joyful by just that, going the extra mile, in terms of service. If you're in infrastructure, and you're dealing with data centers and servers, you understand that making banking joyful, you must be there all the time. You must have sub-second responses, you must feel great in the customers hands, so it's something that you can apply to all aspects of banking and everybody plays a part in making banking joyful for our customers. >> All right, so David, bring us inside a little bit your organization, you said transforming to a technology company. What's that mean, what technology are you using? We're here at the Red Hat Show. Open-source, not the first thing that people think about when they they think about banking. So how does that fit into the culture that you're building? >> Yeah, yeah, okay, so, this Gandalf thing that I talked about, that's great as a logo and a mindset shift, but it doesn't get you very far. And so what we came up with is five key elements that have to change. And we had to work on to become more like a technology company. And one was a shift from projects to running technology like a series of platforms. That enables you to do agile at scale, but for that you need to organize very differently, which is the third thing. And then the fourth thing is that you need to build for modern systems. The legacy way of building technology just wasn't going to get us to where we needed to be as a technology company. And then the last bit is alternate everything. So, if you want speed to market and agility, you have to alternate. That modern technology stat, it was very obvious to us that the legacy, corporate technologies that we used to build systems, were just not going to win it for us. And so that's our move to open-source. Red Hat was a fabulous partner in that and we used Red Hat extensively throughout our entire infrastructure. And so we went through this rapid modernization of moving to open-source, moving to open-source database we used Merare DD quite extensively, but also, picking up pieces of the open-source from the Gandalf companies. We've seen the way they use open-source to scale. Plus also, to provide just amazing services. So for example, Netflix. We run a bunch of banking platforms on Netflix, believe it or not. It's kind of cool, banking on Netflix is a kinda crazy concept, but we brought that do life. What is is that Netflix we loved? We loved their engineering discipline around chaos engineering and the use of chaos to really build resilient platforms. So in our whole test and deployment framework, we have a lot of Netflix chaos elements built into that to make sure that when we actually are testing, we're testing for chaos and random failures which we inject into those platforms. We don't do it in production like Netflix do quite yet. This whole concept of site reliability and chaos and excellence of service is again something we learned from the Gandalf companies. So Gandalf was not just a, oh yeah, let's pester in the heart of the business article. It was really, let's use their engineering disciplines and design principles to build our own systems. Our network, Facebook, which is, you think of it as a network company. We think of network and the infrastructure layer. And our infrastructure and our networking is designed on a bunch of concepts that Facebook have about how they build their network within their data centers. >> Can you help connect the dots, you talk about a phenomenal technologies, chaos engineering, networking like these global companies. How does that lead to the outcome that you talked about? You know, joy to your end users? >> So if you want to make banking joyful, you have to be super-reliable. You have to be on the edge of the innovation curve all the time. Which means you need to be test and learn, which means you'll be very agile. You need to be able to scale very well and the open-source technologies enable us to scale superbly. You need to be able to to perform as well, superbly well. When I joined the company, our measure of how well our applications were performing is are they up or down? And then we advanced that to, well, are they up and maybe 80% of the time they responded within four seconds. Those are terrible measures because they're not joyful. That means 20% of the time we're awful. That doesn't bring joy to a customer. So what brings joy is we've now scrapped all those things and we're starting to look at performance, for example at the 99th percentile, so anything below that is just noise and the signal is what is our worst performing 99%, because if you wanna be joyful every single time that a customer opens your application you wanna be there and respond well, et cetera, et cetera. Same thing goes for customer science. Where do you get customer drop offs and how do you fix problems? So customer science and the engineering disciplines around observing and instrumenting a platform all the time become very , very important. So it goes very, very deep. You know it's a simple concept. But totally changes the way we engineer. >> Your line of work, or your industry obviously is very security oriented, right? >> Yeah. >> I think of healthcare being another with health information what have you. But certainly financial services, so in the open-source community, how do you address this, I would say it's not a clash by any means, but it's a concern, I would think, still that you have to be micro-observant of security practices and yet this is an open-community and exchange of ideas and could be an exchange of vulnerabilities or problems, too. >> So, sure, and we absolutely do. There are certain things that we, certain places that we won't go, or we will go but only for experimentation reasons because of that question. But you know arguably, we think that open-source company can more secure over time than non-open source, because you're also getting a bunch of people fixing it the whole time. And we've seen some of the issues with some of the open-source and the heart bleed and those other bits and pieces. But they were shut down pretty quickly and found pretty quickly. So we move with caution, we're very cognoscente. We move with our eyes open and it's really the zero day vulnerabilities that we are exposed to. But equally, if you're in a proprietary state. The whole thing that came up with the X86 platform in terms of the vulnerabilities there that apply open-source or not. So yeah, security issues exist everywhere. >> Right, all right, so, David, bring us in. You talked about some of the open-sourced technologies. Where does Red Hat fit into this? What's it like, how have they advanced that journey that DBS has been on? >> So for the heavy lifting, for the big applications that we want to run, and the majority of our workload going with open-source is fine, but you want to have open-source that also you think isn't going to break or have big security vulnerabilities to your question. And that's really where a partner like Red Hat comes in because it gives us access to all the wonderful benefits of open-source with a trusted partner that's putting industrial strength quality releases out that we can really rely on and bank on. So, in awhile we used open-source, at the periphery and true open-source that we just plug it off the internet. The really very, very high demanding workloads and very secure workloads we will always work with a partner that can wrap that into an enterprise-quality offering for us. So Red Hat has gone from zero to running way over 50%, 60% of our workload. And we'll continue to put it even more on that because it's a platform we can trust. >> That's great, so, when you look at your journey overall, how far are you along that journey? Anything when you look out, what are some of the things that are exciting you looking forward? >> So while we believe we're ahead of most banks. There are some that are in the mix, Goldmans are pretty far advance, Duetsche, a couple of the others, Capital One, a few. But it's a sort of rare breed. We're about 80%, 90% done on our transformation journey to get stuff to what we'd call cloud ready or optimized. But we think we're just scratching the surface because if you think about plugging ourselves into customers lives, making banking joyful, our external brand promise for that is live more, bank less. And nobody wakes up in the morning and says, oh, I can't wait to go to my local bank branch and go and do some banking. >> (laughing) I heard Steve talking about it yesterday. >> Actually there is one place. My wife loves going there because we do some great free cookies at DBS. >> John: Oh, excellent. >> But other that my wife, the rest of the planet doesn't really do that. >> John: Fair enough. >> If you want to live more, bank less, it's how do we get the toil of banking away from customers yet embed ourselves in their journeys. And for that we believe that this whole play on ecosystems is very important. So being a creator of an ecosystem or participating so that we take the banking toil out, and yet we inject ourselves, be that leisure or travel or insurance or whatever. And you don't see the bank, the bank is invisible. Then you're live more, bank less. To do that, you need great ecosystems. And we think three things help us to plug into ecosystems. Number one is you have to be able to scale very easily. And all the work we've done on the Gandalf stack means that were no longer afraid of scale, just bring it on. The second thing you need a lot of connectivity, and DBS two years ago, we launched the world's largest banking API platform. We went live with 150 different APIs and 60 live partners at the time. That's now grown to over 350 APIs and 100s of corporates and SME partners that wanna partner with us to pug us into their offering. So the more we do that, the more we disappear and let people live more, bank less. >> Well, next time, if you wanna bring some cookies with you, by all means, okay. (David laughs) We're always up for that, David, thanks for the time. >> Sure. >> We appreciate that and good luck on the mission and the journey there at DBS. >> Sure, thanks very much and great to be here, thank you. >> David Gledhill joining us this morning here, as we continue our coverage of the Red Hat Summit. We're in Boston. You're watching theCUBE. (upbeat music)