This is Trove in the real world, ventures and running production code on upstream code. My name's Andrew Conrad, I'm an engineering manager with HP, working on the Helium Dev platform, all of our platform services. I'll let Nikhil introduce himself. Hi, my name is Nikhil Manchanda, and I'm the project technical lead for Trove, for Keelow. I also work at HP on the Helium developer platform. So we'll jump right in, here's our agenda today. We're gonna talk about the real world, and that is explicitly not DevStack. We're gonna be very clear about that. We're gonna talk about disasters, that seems like a pretty open-ended topic, but we're gonna hit on disasters a little bit. We're gonna talk about how to use Trove in Juno stable upstream code to survive disasters. We're gonna talk, well, Nikhil will talk a little bit about Trove with Keelow and beyond.  At the end, all the code samples we show today are gonna be available on GitHub, so we'll tell you where that's available.  Any real-time discussion or comments about the talk, we have a Twitter account you can post to. It's at Helium developer. We may show some of this up on the screen, and so please write something your grandmother would be proud of, because we may be displaying some of this. Okay, so let's, whoops. Do we drop a slide? I don't think so, I'm not sure. Is, well, let's just go right into it.  And one thing we always talk about in DevStack is everything just works in DevStack, and we know why that is, because it's a single process, it's on a single box, you don't have any hardware failures. Just everything always works. You know, Keele's one of the engineers that works on one of my engineering teams, and one of my favorite quotes from him is quote, but it worked on DevStack, right, on my box. So, we're gonna try to get away from that today, and we're gonna talk a lot about the real world, where everything fails. Failure, okay, so there is a slide here, just pretend it's here. The real world's all about embracing failure. Failure is not a corner case, it's the common case. Everything fails all the time, you have to assume that. Basically, when we build Trove and some other other platform services, that's what we're thinking about most of the time. Like, you're not thinking about the perfect case, you're thinking about the failure case. So, I wanna talk a little thing about, bad things happen all the time. Database world specifically is probably not a surprise to most people in the world. Database is crash. Network partitions happen. VMs crash. Hardware fails. Occasionally, a tornado may hit your data center. It's kind of a rarity, but it is a possibility. Two rules about databases. Data is always durable. The data must survive everything. And then the data store must always be available. So, this is availability and durability. The two keys in Trove, the two keys in most database services, including what we're shipping with HP Healing. So, we want you to help us create a disaster today. So, we're gonna have some audience participation here. We want you to tweet. And there's two options here. We realize we're in the city of love, the city of light, Paris. So, we have, the first option is please use the hashtag, I love Trove and Paris. And specifically, you have to say L-U-V. So, we're in Paris, so I'm trying to speak a little bit of French. So, that's the nice option. For the ones in here that are a little more aggressive, a little more, I don't know what the right word is, but we have another option. We have blow up Trove and Paris. So, actually what's gonna happen is depending on which tweet gets the most, or which hashtag gets the most tweets, we're actually gonna bring down our master database that Nikhil's gonna nicely set up in a second. So, we're actually gonna destroy this thing and we need your help to do it. So, I'm gonna hand it off to Nikhil now. He's gonna talk a little bit about the code that was put into, into Juno for Trove, and it will be part of our demo today. Excuse me. Thank you, Andy. So, before we sort of dive into the demo, I just wanna give folks a bit of background into the MySQL asynchronous replication support that when Juno, which forms sort of the backbone of how we're going to do this failover. So, Trove has support for async replication, as a few of you already know, and the way you do that is through the Trove create API, it now takes this optional parameter called replica of, that you just pass it the master UUID, and then Trove goes ahead, takes a snapshot of your master, provisions a slave based on that and sets up replication between the two. So, that will sort of form the basis for our having another instance with the same data that we can failover to. And then also on when something bad happens to the master, we'll go a manual detach of the slave needs to happen so that you can use that as its own promote that to master. And so, to do that we have the Trove update API where you can call the slave and say, hey update yourself and detach yourself from the replica source because I want you to not be read only and be your own, be a new master. So, going to quickly walk through the demo. So, over here this is a Trove box. Unfortunately I couldn't get this running on the cluster or anything, so Andy it's gonna have to be DevStack over here. It works in DevStack. So, but since it's DevStack and everything works perfectly well we're gonna have to simulate the failure. So, just as a reminder tweet, I love Trove in Paris or blow up Trove in Paris and we'll have to create that. So, we did try all these scripts on our real production systems before we came here but for the sake of the demo we decided to do it on DevStack. Okay, so I'm going to go ahead. So, there's a master DB. It has an application running. It's a very simple application. It just shows the OpenStack services and I am going to create a slave based on that. Just trying to make sure, sorry one second, that the screen here is showing something different from the screen there. So, make sure we're on the same page and you guys can see what I'm doing. So, I'm going to create a Trove slave. It's going to be a replica of this master. So, I'm just going to post the replica over there and that will take a few minutes to build and as you can see, Trove is taking a snapshot of the master and the slave is starting to build. And so. Now, Nikhil, did you create the slave across the different AZ when you did that? Oh, no, so, excuse me, this is DevStack. So, no, in production what you'd want to do is you'd actually want to create the slave in a completely different AZ because your AZs might have the same power source and in case one power source goes down, you'd still want to make sure that your slave instance is up and then you can fail over to the slave. So, in this case, I don't have AZ support for the demo, but in the real world, you'd actually want to create the slave in a different AZ, absolutely. Want to give you guys a bit of background on how the failover is actually going to happen. So, if you notice here, when I did a DevStack create, the host name that came back is actually a DNS host name. And so, we're using Designate under the covers here, Designate's an OpenStack incubated project now. And so, we're going to use DNS in the system to do the failover, so the application is actually going to talk to the master using DNS. I just noticed that the resolve.conf is not going to the right name server, so I'm just going to go ahead and correct that. Also, it might be better if some of you guys can see this. Since this is local DNS, so I'm just going to make the local. This is a disaster we didn't plan. So, no, I just want to make sure that the application is actually up and running. There we go. So, DNS is working, Designate is working as it should. And so, the application is talking to the master using the DNS host name. And since it was all this actually going to the local box to the DNS resolution, things are working. So, let's check on the status of our slave quickly. Slave is still building. It takes a couple minutes to build, so we can check what the... So, this up here is the slave's DNS name. And then, if you look at the same thing on the master, you'll see the DNS name that we provisioned for the master. Okay, so let's go back to the presentation and talk about what's actually happening a bit over here under the covers. So, when Trove is setting up your instance, Trove has inbuilt support. So, the Trove guest agent that gets provisioned on the instance sends heartbeats back to the Trove control plane through the Trove conductor, which basically checks on the status of the data store on the instance. So, if it's MySQL, it checks port through 306, make sure MySQLD is running, and then says, okay, you're active. People can actually connect to you. So, we use those heartbeats from Trove as a means to figure out that the instance is active, and so automatically monitor those heartbeats. And so, there's really two cases here where failover, what failover looks like, right? So, failover or what failure looks like. So, you can consider it a failure if the guest agent is actively monitoring MySQL and sending back a heartbeat saying, hey, I can't actually talk to the data store, the data store's not up, or Andy mentions, as he mentioned, VM's crashed. So, there might not be something on the guest agent's side to actually send that heartbeat back. So, in that case, absence of a heartbeat also, after some threshold, you'd want to characterize as a failure, so you'd want to use that to failover. So, the idea here is monitor heartbeats, and if you get a bad heartbeat, or if you get no heartbeat, then that's a failure, so. Disaster time, why don't you- So, should we make sure the slave came up before we do the test? So, for your demo, you're monitoring the master. You could be monitoring both the master and the slave. Right, so right now for this demo, we're monitoring the master, and then we're monitoring heartbeats on the master, and I'll walk through the code that we're actually using to do this. It's an extension of the Trove Task Manager, so the way we've written Trove is Trove is pluggable. You can extend the current Task Manager, you can make it do other things, or, but I mean, when we walk through the code, it's all using standard OpenStack client APIs, so the reason I'm extending the Task Manager is because it has a periodic task that you can leverage to do this, and you can extend the current one with some new functionality and plug it right back in, so it looks like our slave came up, so, in that case. So, you wanna create the disaster, hopefully you've tweeted by now. Either I love Trove in Paris or blow up Trove in Paris, so let's go see what kind of audience you are. So, this is a little script that Andy wrote here to see basically pulls the Twitter stream and either shows the results for I love Trove in Paris or blow up Trove in Paris, and so it looks like we have a few people who have tweeted I love Trove in Paris, but, oh, there's only three for blow up Trove in Paris, come on guys, you can do better than that. Looks like there's more people who are falling for the beauty of Paris, the city of love, so I love Trove in Paris. So, as most. Once you hit it one more time, we'll see if we get any results. Okay, are there any? We're not talking about database consistency today, Twitter is not the most consistent database in the world, so you get some random results. Oh, there you have a few more, all right. Oh, it's a tie, this is a hard one. XG78150, just though. Why don't you show how we're gonna blow up the database and then we'll come back and check one more time. Okay, so basically, to blow up the database, what we're gonna do is we're going to go ahead and stop MySQL on the database, crash it, and so the guest agent, which is still running, would send back a shutdown, a shutdown, hard beat saying MySQL is shut down, it's not coming back up, I don't know what to do. This is my status, right, so, and as most failures, excuse me, most failures don't come with what we've built here, which is a big red button, that I'm gonna go ahead and press and that's going to cause the database to fail. So, I'm tending towards I Love Troven Paris. We'll run it one more time. Okay, let's see if that's what the audience is feeling, so. Uh-oh. Oh, let's see, so what's our final, whoa, whoa. Oh, wow. How did that happen? It's that kind of audience. All right, all right. Well, we'll have to fall back to plan B. Blow up Troven Paris, so. I'm not entirely sure. Okay, let me go hit the button and close my eyes. Andy, tell me if this goes well. Uh-oh. Wow. Okay, let's see what happened here. Uh-oh. Well, it's a hard beat, so it happens on a schedule, but our application should actually have been taken down at this point, right, so. So the Trove hard beats happen every two minutes, so hopefully, there we go. You can see master DB right now, shut down, can't reach my sequel, so the hard beat has come back and can't reach my sequel at all, so if we, so this is the case where the failure scenario should kick in, and let's go look at our monitoring task manager that I'll shortly show you guys the code for to see, to show what's going on under the covers. Oh, and look at that, so it's not able to connect remotely to, it's not able to connect to the MySQL master, so it should have gone through and actually kicked off the failover code, so let's see what happened. Oh, our application's back up, so if we actually look at the state of the Trove instances here, our master's shut down, our application is talking to the slave, and if you look at the slave show, a very interesting thing has happened, the host name of the slave is now been switched out and that's actually the host name of the master, so you're under the covers, we're using DNS to do this failover, so I've always been wanting to say this in Paris, so et voila. Let me quickly go back to the slides, and so that was the failover demo, I promised I'd walk you through some of this code that we have, so yeah, if you have questions, go ahead. Yes, you do, so there's two ways of doing this and you could either use DNS, so the way we've set it up, we have the DNS servers and we're talking directly to that particular DNS server, so we don't have to deal with DNS replication and the TTLs are set really low so that if something happens and you're using it for failover, your host is not caching the DNS record and going to the old host, so you absolutely have to deal with that. There's another way of doing this, you can use floating IPs to do this, so you basically give the master and the slave public IPs and then you switch the IPs over when you take the failover and again, that would depend on what you want to go with, the Trove has APIs that supports both and if your DNS infrastructure allows it, you could go DNS or with floating IPs. Any other questions, just feel free to raise your hand and yes, so Trove is monitoring the database, so Trove standard today in Juno monitors the database based on the heartbeats, and so it sends back status saying I'm up and running, I'm a data store shutdown, so that's what the shutdown thing you guys saw was, but we've extended Trove, the regular Trove task manager to also do this monitoring part and that's the extension that I'm sort of showing you here. So this is the monitoring manager and we've configured Trove task manager module to use this, this basically just extends the task manager and it's the crux of the code that was doing the failovers in this part, which is monitor HA, which is a periodic task that goes ahead and monitors Trove instances. So first it finds a list of master instances that have slaves that it wants to, it identifies that it wants to watch for failover scenarios, for failures and then once it's done that, there's this condition to when it should engage failover and like I had mentioned earlier, if you go back to see what's happening there over here, there's really two scenarios, right? There's an active failover or there's a failover where it's actually failed. So in the case of where it's failed, you know something bad is happening, your timeout over there is probably shorter, but in the case of where it's active, it's still active but you haven't heard from it and haven't had a heartbeat, you might want a different timeout there just because it might just be a network issue or latency or things like that that the heartbeats are not getting across. So that would have detected the case when the VM just dropped. All right. Would it be what you called? It wouldn't have made for a very good demo though because the timeout I have it set at is 15 minutes. Yeah, fair enough. Right. So we'd be waiting here for a long time before it would have detected that, I mean the VM is crashed under us, but yes. So your script basically, you detect something bad happens, don't ask any questions and just switch over. Right. So coming to the meat of this script which is actually doing the switchover part. So we've identified that failover needs to happen. This just goes ahead, authenticates a bunch of open stack clients, not very interesting. This was that failover API that I showed earlier where you call instances edit and you attach replica source. And basically at that point, your slave is no longer a slave or getting data from the master, it's its own master. So that's equivalent of promotion. And then this is talking to designate to actually switch the DNS records underneath to do the failover so that all your applications can now talk to your slave instead of going to the master. Also one more step after that, all of these functions are up here and this code will be posted on GitHub if you guys want to choose to see what's going on. And we want to update Trove to make sure the records in Trove are consistent with the designate records. So we wanna make sure that we go ahead and say the master has this new DNS and the slave has this new DNS. I think we have a question back here. Oh, sorry, the lights are bright so I might not always see your hand. That's really awesome. That's a great question. So these are some of the questions that we're actually sort of coming up with when we're designing this, like some of the Trove design sessions that we have because what we're finding is it's really up to the deployment and the environment and the sort of applications running on it. There's a lot of people who are saying, hey, I can wait longer if it's just a temporary network outage that will fix itself in five minutes, that's okay for my application. But there's other people who are more sensitive that says at the very first time, I know it's starting to fail, I want it right out of there. So I mean, and what we're finding more and more is that really we need to provide the knobs rather than actually providing the solution, one size fits all. So we need to build in ways in which those monitoring controls can be tweaked in Trove rather than have one size fits all solution there. So this is basically, so what Fillower's done, now you're talking to the slave, are we done? Well, not really. There's some other stuff that needs to go on. You want to do some more stuff and the script can be extended to do this today using the standard tooling. You promoted your slave to master, you've used DNS and floating IPs to failover, but a reset also needs to happen. Your new master now doesn't have a slave attached to it. So if this were to happen again, you're leaving yourself vulnerable to that. But your Fillower strategy could also consist of spinning up a new Trove VM just as how I showed you as a slave of the new master. And then the other good thing is like, I know at least the team in Seattle that I work with is very DevOps-oriented. And so the old master is still around and you can go take a look at SSHN or do whatever you need to do to figure out why did it go down in the first place. So it's still around for Portsmortem debugging and analysis, right, so. I'm not a big DevOps guy, but I don't consider that a party, but you should try it sometime, Andy. It becomes a way of life. So this specifically talks about asynchronous MySQL replication. I'll talk a bit more about what we're doing in Trove specifically to handle that. I think there's a lot of, then there's a slide in this where I want to talk to specifically to that. There's a lot of state-of-the-art technology already out there that we're looking to sort of leverage. We built a clustering API in Juneau that we're looking to extend as well. I'll get to it. So, but actually that's a good segue. So failover in HA in Trove, right? So right now we have the tools or the APIs to actually do this, but we don't do this in Trove. Somebody said, like, wish for you to write the code to actually for Trove to do this in default. We're absolutely looking at this and this is what we have, plan for Kilo. We're still trying to go through all of the designs to figure out what's right for Trove to do. There's a lot of ways in which Trove can actually do this monitoring and from an open stack perspective, there's no clear solution. Should Trove use a third-party solution to do this monitoring? Should we do it based on our heartbeats? I think heartbeats is a good first step and it's already baked into Trove, so there's a lot of talk about making that solution pluggable as well. So attend the, if you're interested in these areas, attend the design summit sessions on Thursday. There's a specific one on failover. There's another specific one on clustering. So you mentioned the split-brain scenario specifically, so in order to target some of that, async MySQL replication might not be the way you wanna do that. You might actually want to spin up a Galera cluster or something like that, where you have three instances and then there's already technology out there that solves this for us. So how can we make Trove leverage some of that? We have a clustering API today, but we only have Mongo clusters. In Kilo, we're absolutely gonna start looking at provisioning Galera clusters. And hopefully, my view is that by the end of Kilo, we'll be there and we'll have at least a three-node Galera cluster up and running, or Trove will have the ability to do that. So that's on the roadmap. Again, if you're interested, the design sessions are on Thursday. So it sounds like you're promising that everything we showed today plus clustering will land in Kilo. So Andy, let me, this is OpenStack, right? So OpenSource works in its own beast. So I'm not sure if I can say promise is the real world. We're gonna do our best to make sure we get there, but. That's cool. I mean, I think the point we're trying to make today is everything you need is in Trove. You just need to write some code outside of Trove. And we're gonna make a lot of it available. We're actually gonna extend a little bit of what Nick Kilo showed today. And we'll just have that as free samples that people can download and use. Obviously like Nick Kilo said, eventually all this should just be part of Trove. And it shouldn't be stuff that you have to run externally from Trove. So the location for the code samples is right there. We're gonna leave this slide up during the Q&A so you can copy that down. There's a bunch of design sessions, both Thursday and Friday. Is there any ones you specifically wanna talk to? If you're interested in failover, definitely make it to the replication V2. Talk the design session that we're gonna be talking about failover. And if you're interested in clusters and Galera clusters, building out Trove clusters is the place you wanna be at. If you wanna contribute to Trove and not interested in either of these, we're still, I mean, we'd love to have you. There's a lot of things going on in Trove other than failover and clusters. And if you're not able to, if you have conflicts, not able to make any of the design sessions, definitely come to the contributors meet up on Friday morning. We'd love to have you. Also, find us, if you can't make any of them, find us on FreeNode hash open stack dash Trove, so. And also, if you want us to explain more about the demos we showed today, the support that we'll show up in Kilo. Our contact information is there. We're both here through the end of day, Friday. So feel free to contact us. You can also, we'll be watching the Twitter account. So if people have questions, feel free to post there. And we'll, as much as we can, we'll answer the questions. There's two more Trove sessions. Unfortunately, one already happened on Monday. But there's also one at 520 today. Another one of our HP contributors, Vipple, where's Vipple, right there. He's gonna be giving a talk about the PCORNA server features in open stack and then doing ops with that. And that's at 520. It's the last session of the day. So that's our contact information. Feel free to contact us, like I said. And that's all we have for you today. We'll take questions now for a few minutes. Why don't we leave that slide up so people can copy. Today we don't have any Trove APIs that support that. We should probably discuss how often that scenario comes up and if that's something that we need to handle, we should talk about a way in which we can get that going. So if you find out that it's, so sorry, the question was, if the master's out of rotation, is there any way of putting that very same instance back in as a slave of the one that just got promoted? Can we do that? We don't have a way of doing that today. And I mean, if it was just an intermittent network failure or something and you diagnose it that it's not really a problem with the instance, then if that's the scenario that we want to be able to support, we should talk about having an API to do that, but we don't do it currently. Great question. Question. So Trove supports multiple slaves to the same master. You just have to issue multiple create calls and you can use passing the same master UUID. So you have one master with end slaves. We were trying to do some benchmarking to see if it sort of fails over at some point and what that point is, but we've built it in such a way, we've done it in such a way that you can have end slaves. So the question is, is this integrated in heat? The answer is so Trove has configuration that you can switch to tell Trove to use heat to do the provisioning or not to do the provisioning. So you can either provision your instance directly using heat or you can provision your instance by going to the individual OpenStack services themselves. So the task manager, which is the component of Trove that actually does this provisioning, I don't remember the exact configuration value, but if you switch it over, it can either talk to the Nova, Cinder, endpoints directly or through the heat API. So this is not running using heat. Specifically, I don't know of any bug that would not let you do that because underneath the actual configuration of the slave is everything that is the guest agent is handling. So heat is basically just being used to create the instance up and running and put the Trove guest on there and then it's up to the guest to do all of the configuration. So it should just work. That said, the demo itself is not using heat and I don't believe there's a bug with that, but if there is, then definitely put in a launchpad ticket and we'll look at it. It is supported. Very interesting question. So again, this comes back to the same thing of like, these are questions that are coming up in a lot of the design sessions and how do we build a set of knobs to allow people to pick a certain slave as this is the slave to actually fail over to when the master goes down. These are things that we're going through and trying to figure out during the design session as well. So come to the design session. I do want to mention, we actually shipped Healing Dev Platform with replication. It just went on a couple of days ago. We're also, is it any day now our public cloud will be updated with the same bits? People are working on it as we speak. So you can actually go up to the HP public cloud and play with this script and do that the same thing that Nikhil did today. So I believe, are we the first public cloud with replication that we know of? Any other questions? Comments, they're very interesting. So feedback, it's a hot topic. There's folks looking at it as we speak. I know there's Amroth, I don't know if he's in the room somewhere. It's blinding. Oh, there is Amroth and Dennis. There's a bunch of folks actually talking out scenarios and working through it, trying to figure out how we can use, build Cassandra clusters using the current row of clusters API as well. So that's also part of the design session that we're going to be talking at, so great question. Cool, that's all we had in terms of the demo. And thank you for blowing up Trove in Paris and thank you.


Hi, my name is Vergy Togar and I'm the author of The Self-Love Revolution, Radical Body Positivity for Girls of Color. I thought that I would read you the dedication to the book to give you kind of a sense of what the book is about. For every girl who has felt ugly, wrong, bad, weak, you are beautiful, you are right, you are good, you are powerful beyond imagination. The Self-Love Revolution is really a book that's written for girls to help them understand that they are powerful beyond imagination regardless of their body size or shape. The book is available at the San Francisco Public Library if you want to check it out or any indie local bookstore. Bye!


Alrighty. Here we go. Hello, hello, everyone. Welcome to the Kickoff Reading Sprints for the Continu-a-thon. I'm Laura from Laura's Little Library. Unfortunately, Hugo and Jane both have some things going on, so they're not actually able to make it right now. But you know what? That is A-okay, so we're just going to go ahead and start the sprints with just us. So if you haven't heard of the Continu-a-thon, it is a read-a-thon happening from April 2 to 15, and we are focusing on finishing and continuing series, duologies, trilogies, even companion novels. So yeah. So I'm going to start off with these reading sprints by Reading the Toll by Neal Schusterman. This is the final book in the Ark of the Scythe trilogy, and I've been putting off reading this because I really love the first and second book, and I didn't want the world to end. I didn't want to stop reading the characters, so I stopped and didn't read the third one. But now I'm finally going to pick it up, and I'm finally going to finish the story, and I am super excited for it. It's also super intimidating because it's a bit of a brick. It's a little bit of a chunky one, so that's why I'm forcing myself to read it now with the sprints, because otherwise I will probably never start this. So what are you guys reading or doing if you're going to do other things? Yes, I have found it to be really good. I don't read a lot of sci-fi, but I very much enjoyed this. I used to read a lot of dystopian when I was younger, and so this kind of fits the vibe while being something new and interesting. Tales from the Shadow Hunter Academy? Oh, that's awesome. I have not been keeping up with Cassandra Clare at all, but I should at some point because I did very much enjoy the original series, The City of Bones. That's really cool. Let me know how you like it, because isn't it more of a companion to the series or is it still like an actual novel? Frankenstein? Nice. Yeah, I really need to reread that one. I don't remember a majority of what happened, because I tried to read it in a day to finish it in the last of a readathon, so that's awesome. I hope it's as good as the first time you read it. Also, completely realized that I'm wearing the wrong glasses. Best I will not be able to see the book. That's very fun. Alrighty. Well, I think we should probably get started with actually reading these books. I'm probably going to get started with a 30-minute sprint just to kind of get started, get into the books, but if you want to do like a longer or shorter sprint, just let me know and we can do that next time. So let me just quick get that set up. Getting it all set up. Happy reading, everybody. Okay. Am I back? Are we back? This was crazy. I think it may have been the timer that did it. Okay. So yeah. So basically, Chrome decided to stop responding for a hot minute there. I think it may have been a little too much on my computer, but we still got eight and a half minutes left of the reading sprint.  I won't share the timer screen again because I don't want this to happen again, but I will let you know when the timer is done. So continue reading. Have fun. Alrighty. That was 30 minutes of a sprint with one little interruption. But yeah, how did everybody do with their reading? I got to chapter two. I got to page 32, which is pretty good. Yeah, I'm liking it so far. I've definitely forgotten quite a few of the smaller details. I remember the big main idea of the last book, but I'm slowly remembering smaller details, but I'm liking it so far. So yeah. Yeah. And we had a question about one of the, about the prompts. So I'm just going to like vocalize it so that everybody can know the answer if they had the same question. So for the start and finish a series entirely prompt, that is meant to be like one of the harder, like kind of more bonus prompts. So that would be starting a series. So four or more books in line with each other. Starting and finishing it within these two weeks, rather than like a duology or a trilogy, just because there are prompts for those already. But you know, it's for some people, it's a lot easier to do duologies within two weeks. So I wanted there to be a little bit more of a challenging prompt to keep a little interesting. But yes, my computer's decided to freeze, but that's okay. Yeah, translated fiction can be interesting just with what languages fiction is translated into and what ones it isn't. So if it's not your native language, that can be really difficult. But I commend you for doing that. I have not read too many books in other languages that I somewhat speak. But I really should. I need to do more of that. Nice, nice. So how are we feeling in terms of doing more reading sprints? Do we want to do like longer ones, shorter ones, another 30 minute one? Yeah, I was thinking about maybe bumping it up to a 45 minute one, because now that I've like gotten started, I really want to just sit and get immersed into it. But you know, if other people want to do like shorter ones, that's totally fine too. I don't know if I'll be able to do the timer on the screen again, just because I don't want to lose the connection. But 45 minute one. Is that good? Go ahead and set the timer. Honestly, I might just do, I'm going to actually end up doing a timer on my phone, because my computer does not want to load. I'm just trying to butt me out again. Okay. Well, it seems like it's still streaming, even if my computer says it isn't. So I'm just going to go ahead and start the 45 minute sprint now, and hopefully we can make some more good progress. We love technical difficulties. They make life so easy.


This would give you an idea. First three starts, rough, you know, four-and-a-third innings, last four starts, so five-and-two-thirds. The Velo's coming back. Today was his best.  And what is it about him being back home in Chicago? Well, he's going to be throwing on the side, on the south side, every time he gets back there. He didn't want to leave there. He was some kind of pitcher there, so many multiple all-star teams. If he's healthy, I'm not worried about Chris Sell because he's one of the best I've ever seen do it. But last year, he pitched for the first time deep in October, and I'm sure fatigue and hangover was there for him. But what I saw today was a normal Chris Sell, big breaking slider down and then fastball 95. He was painting the spot and watch out. Yeah, I agree with what Frank said. I, you know, you go through a long season like Chris did last year and through all those innings. And of course, you know, it pitched deep into October.   Tonight, he had the slider was coming back, velocity was up, he's going to be fine. What were you looking for more? Was it the velocity of the command tonight?  And I think if he starts commanding his pitches, you know, where he wants to do with me, sometimes you just got to be a command guy when you're trying to build up your arm strength again. But tonight, I saw him throw 94, 95 tonight, so you know, the velocity's coming. And when that comes back and the command of that slider comes back, he's going to take off. Oh, listen, Frank's feeling pretty good. The White Sox have walked off three of their last six games. They got some work to do, though. Yeah, it would be a huge effort if they did it tonight. You know, we talk about the Cubs, Frank, remember, we were we were talking so much first two weeks, are we worried about them? What's going on? What were they, two and seven, two and eight? So how much do you think this series against the first place Cardinals that they need confidence wise? They need this. They've hit their stride. They've won 15 out of 20 of their 20 last games. They're starting pitching. They took over. They started pitching deep in the ballgame. They knew they were having problems in the bullpen. But all of their starters have held this team accountable. And they in the rest of his office is jump on the starters back. But they do have great veteran starters who can get it done. And they prove themselves early in the season for the Cubs. You know, it's interesting. So coming out of that hole, here they are. Look, they've been in the playoffs every year into Joe Madden, right, Terry? And I'm just curious from a manager perspective, obviously, you know, Joe Madden, he was on your bench when you were here managing in Anaheim. He doesn't have a contract for next year. It's rare, as you know, usually you extend the guy. So it's not they don't have the whole lame duck thing.  Well, if you know, if you know Joe Madden, he's not going to be upset by not having a contract. This guy's got great confidence in what he do, what he does, what he brings to the team. He's got a veteran club. They've won. All his job is right now is to keep the attitude up and keep him positive. He's not going to change anything. They're going to still have the loud music during batting practice. They're still going to bring the zoo animals into pet once in a while. Joe is not changing. Joe is not going to change. He's not worried about anything. And for some strange reason, he's not the manager of the Chicago Cubs. Next year, he'll have another uniform on from somebody else. Yeah, there you go. What's look like the message has been calm. Cubs are playing really, really well.


Hey guys, it's Tilly and today I am back with a top 10 favourite YA contemporaries video. So in 10th place we have The Unexpected Everything by Morgan Mattson. This is my first ever Morgan Mattson book and I was so amazed by her writing. It was amazing. So this book is about Andy and she has her entire life planned out.  She has no plans. She's got her amazing friends and then all of a sudden her life changes.  But still she ends up finding and walking this big fluffy dog here who currently belongs to this amazing beautiful guy called Clark and they end up, you know, getting a little bit of romance happening between them and basically you just follow her summer in this book with her friends and Clark and her job and it's a really fun, easy summery read and it was so breezy and it was just so good. I laughed in it and I was sad during it and it's just amazing. In ninth place we have You Know Me Well by Nila Caw and David Leatherthin. This is a really good LGBT read but one of the things that I really liked about it most is it has such a big friendship aspect in it and I do enjoy my romance books but I love books even more that have a strong basis for friendship. So you have Mark and Kate and they both go to school together. Mark is gay and Kate is a lesbian but they don't really know each other that well until they see each other out during Pride Week and basically it is the night of their lives because Mark is in love with his best friend who is not sure feels the same way and Kate is basically going to meet the girl of her dreams but she's so terrified that she actually runs away and so they both help each other to pretty much complete their dreams. In eighth place and I might be cheating a little bit but it is the Honor and the French Kiss trilogy. So you have Honor and the French Kiss, Lola and the Boy Next Door and Eila and the Happily Ever After and this is by Stephanie Perkins. Basically this is like pure romance, happy, go lucky books and it all features different characters but all the books do have strings intertwined between them all so some of the characters in the first book appear in the last book and basically if you guys read them you'll see how they're all connected. So Honor and the French Kiss is the first one so the first book is about Anna and she is sent to France by her dad to go to a boarding school. She's originally from the USA and she has no idea what she's doing. She can't speak French and she has no friends and it's basically her journey at school there especially when she meets beautiful Etaine Sainte-Claire and she develops a crush on him but he has a girlfriend but things are just never as what they seem. Seventh place is a book that I hold really close to my heart. I love this one and this author's writing is amazing. I actually wrote a fanfiction for when this book ends which I'll leave a link to below. It's just like a small chapter, it's nothing big because I just couldn't do justice as much as this book did and that is Eleanor and Park by Rainbow Rowell and for those of you who know Rainbow Rowell is like a genius when she comes to writing she is really witty and funny and charismatic and she writes the stories that just flow so well and you read them so quickly and you just enjoy every second of them. So this book revolves around Eleanor who is this crazy redhead girl who comes from a really tough family. She doesn't have much money, she doesn't have any friends, her family's having a lot of problems so she's got yeah really rough life and then you have Park who basically, he doesn't have any friends either but he's got Paris, I love him and this home and their lives become intertwined when Park stands up for Eleanor one day when she's being bullied and they pretty much just have this adorable little romance and this friendship too that evolves between them and it's so heartbreaking but also just so cute at the same time. Next I'll be having another one of my favorite books ever and that is On the Jellico Row by Melinda Marquetta. She's also an Australian author so get behind that. She's written so many amazing books too like The Pipe of Sun, Saving Francesca and Looking for Ella Brandy but this one is my favorite out of them all and it was just so good. Basically you have two different timelines in this book. One that has set 15 years give or take before and then you also have The Present Time. So you have Taylor who basically like is the leader of this boarding school and she is rivalry with another boarding school and the Townies kids as well and they all did these different games to pretty much keep up territory wars that happen. This territory game was created longer for them. Hannah who is Taylor's friend has gone missing and so she also has this kind of mystery part of trying to figure out what happened to her friend or also finding other clues about a story that happened in this book as well. So it's real mystery but it's also really fun and also terribly heartbreaking in parts and I probably am not doing that justice but trust me you guys need to read this. This is where I got super half me. These top five books are like some of the best books I have ever read in my entire life and you guys need to read all of them but in fifth place we have Burnt by Crystal Chan and I did not know what to expect when I got this book. The cover is very plain but also very beautiful at the same time and so I really had no idea what I was getting into but this book is about a young girl called Jewel and the day that she was born her brother actually passed away and so her family believes it's kind of like some sort of curse. Her granddad has never spoken a word since she was born and it's just super heartbreaking and you're reading this book and you just want to drive through the pages and give Jewel a hug and tell her it's going to be okay but then one day Jewel meets a strange boy who becomes her friend and her only friend and her life starts to change. Her mother comes out of a shell, her granddad and her like they have this friendship and basically it's honestly I was in tears by the end of this book and I cannot tell you but you have to read it. Like it is nothing that I have ever read before and I was so amazed Crystal Chan has amazing writing and if you guys do anything read this book. I read this book a very long time ago but one thing I remember is absolutely boiling my eyes out and feeling so hollow once I've finished it and that is the last time we say goodbye by Cynthia Hand. So the main character is Lex and her brother has recently killed himself and her entire life has changed after that moment. So it's basically a story of Lex trying to put her life together but there is one thing that is stopping her and it is the fact that she has one missed call and a message from her brother the night that he killed himself and she can't bring herself to face that yet and it was just so sad. Like I know I've used the word heartbreaking so many times but this truly was. You are following the story of this girl who is just trying to survive this tragic thing that happened and her struggles and her successes and it was just so real. I just want to give an honorable mention to Love Let's to the Dead. I completely forgot about this book but it was like sitting right there. I don't know how I missed it. This one probably would have been on par with the last time we say goodbye. Basically you follow this girl called Laurel whose sister passed away and no one is sure if it was suicide or whether it was an accident but Laurel basically writes this in a format where she writes to people who have died so basically it starts off with her saying Dear Kurt Cobain and then talking about the story but little does ever know there's a deep secret that happened to Laurel that had to do with her sister and so she has never forgiven her sister and so she's not entirely sure how to mourn her without forgiving her first. So you go on this absolutely gut-wrenching journey with this poor girl who is trying to decide what's right, what's wrong and how she can forgive her sister. Third place we have one of my all-time favorite authors and that is The Messenger by Marcus Suzak. I have three copies of this book because I absolutely adore Marcus Suzak. He also wrote The Book Thief and When Dogs Cry but this one is seriously an underrated book by him and more people should totally read it. It is completely different from The Book Thief but it is just as amazing. So you have Ed Kennedy who is a stock standard guy. He has no girlfriend. He has a dog. He has a rundown house and he's lobbled on of his best friends but one day he accidentally helps to stop a bank robber and that is when his entire life changes. An ace which is like a card shows up with instructions on who he should help or hurt to better people's lives and basically he becomes The Messenger but no one knows what his complete mission is. He was sending these cards and you follow his journey and it was just so great. I absolutely love the story and I'm sure you guys will too. This was such a hard decision trying to choose between these two because I have two different reasons to completely love these books and it's so hard to pick so I have to do it though. So in second place we have The Sidekicks by Wilka Starkas and Wilka Starkas who's another Australian author. He's absolutely amazing. He wrote the first third and I think it's lola something. He's gonna hate me for not remembering that one but it was his first book but basically The Sidekicks is my all time favourite book by him and it was so good. This book really hit home to me but it also helped me to open up my heart and accept something that happened in my life that is very similar to this book. So you have three main characters that have three perspectives that go on through this book. So you have Ryan, Harley and Miles and they all had one common friend and that was Isaac and unfortunately Isaac passes away early on in this book and we have to read the aftermath that happens between for these three boys who are completely different from each other. I like to subscribe as the swimmer, the rebel and the nerd and it's tough because these characters all believe that Isaac was what made them them and so they have to try to figure out their lives without him who they are and who their real friends are too and it was just so good and laugh at loud funny and absolutely tear jerking at the same time. And for the book in first place you guys can probably guess it I absolutely boast about this book all the time. It is my all time favourite book and I just absolutely love it and if you guys are going to take any book out of this pile to read read this one but also read many of the other ones because that's just as amazing and that one is Aristotle and Dante Discover The Secrets of the Universe by Benjamin Elia Sainz and guys you need to read this absolutely beautiful breathtaking book that is not only written in the most amazing form ever but it has characters that you will absolutely fall in love with and realness in it that you just can't help but let hit home. My heart swelled two times as big when I read this book I am absolutely in love with it and the characters and just everything. So you have two characters who are basically contrast of each other you've got Aristotle who is this troubled little kid who can't swim he's got a poor family and his brothers in jail and things just aren't going too well for him he's a little bit of like a troubled child and then you meet Dante who is this absolutely perfect child with his family who just loves him and he's so kind and gentle and we all love him so much and these boys become really good friends at this local swimming pool and you follow their story of their friendship Dante helps Aristotle to like learn more about himself and come to terms with things that have happened and honestly like I had no idea what to expect this book is a little slow to get into but if you just push through I can assure you you guys will absolutely love this book so it is not only a book that deals with friendship and family and love and first beginnings and like puberty and everything it deals with like mental issues depression and oh it is it's everything in one book I think this is a book that almost everybody should read because it not only helps you to learn about these characters but also you can compare it to your own situations and learn from yourself there is something that everybody can take out of this book so please please please read this book as you can see it has many awards it deserves every single one of them and more it is amazing and it totally deserves first place on my top 10 YA contemporary list I hope you guys have enjoyed this video I should hopefully be back with one soon and until then tell me guys what your favorite all-time YA contemporary book is and why or if you guys agree with any of the books on my list I'm so happy to talk about absolutely any of them thank you guys for watching and I hope you guys have a wonderful bookish day and great things happen to you and until then I will see you later so this is the fifth book in the friend of glass series basically we pick up after Aileen has saved Dorian from getting his collar broken off


I was excited when I learned that I have been offered a PhD position in Ohus University in Denmark. But on the other hand, I was nervous too that I have to pack my bags and move to a new place called Denmark with my family, where I didn't know anyone. I had many concerns, for instance, how it would be to work in a foreign country. How would the people and colleagues will be in Denmark? Will they accept my family over there? Or will my wife have a good life over there? How about my kids? Are they going to get stable and settle over to a new place? If only I would have known better, it would be much easier for me and my wife here. Denmark is really a lovely country with a lot of opportunities, social security and time for many things along with your work life. So please make your choice and I will try to answer the questions that you have in your mind.


Sounds great. Anyway, thanks for your patience and thanks for being here. Thanks for still having the patience to listen to me at 3.45pm. I'll try to keep it as lively as possible. Can you hear me OK? Yeah. Great. So today, we are going to talk about open sourcing financial services. I know it sounds like an oxymoron, but the reality is that's not the case anymore. And I'd love to walk you through a little bit of our history and how we got here. And most importantly, why we're seeing what I'm hoping can be defined as a renaissance of open sourcing financial services. So I'm Gabriel Golumbra. I'm the executive director of FINAS, the Fintech Open Source Foundation. We are the umbrella foundation under the Linux Foundation for financial services. We joined about a year ago. This is the first time I see many of my colleagues in person, and this is my first talk after a long time. So forgive me if I'm a little rusty. I'm not sure what's the protocol anymore to look at people in their eyes, shake hands, and stuff like that. With FINAS, we have almost 50 members, and most importantly, over 50 projects, standard projects, software projects, and special interest groups. Apart from being a pretty logo slide, I'm very proud to have in our foundation, and of course members of the Linux Foundation, financial institutions, increasingly retail banks, software vendor, Fintech vendors, hopefully more and more, and of course, also our associate members. We are seeing a lot of power in helping existing consortia in the industry to embrace open source in the very same way we've done with individual institutions. But as I said, as an Open Source Foundation, we are focused on building projects and valuable projects, hopefully, for the industry and beyond. And so we're really happy to have now over 50 projects in our foundation. If you want to learn more, you probably are familiar with the concept of landscape in the Linux Foundation. So if you go to landscape.finas.org, you can have a look at the over 50 projects and special interest groups that we discussed. What we are experiencing, especially in the last two years, has been a pretty outstanding growth, not only in terms of members, but in terms of projects. We've now passed 50, and especially in terms of contributors, which is pretty unprecedented, if you think about contributions from banks and financial institutions have been pretty sparse, to say the least, in the last few decades. And so we have now reached, over time, over 1,000 contributors. And what I hope to walk you through today is really how we go here, and what are the macro trends that we're seeing in the industry that are motivating such a contribution. Before I go there, though, I think it's particularly important to understand that our contributions are largely coming from financial institutions. And that, again, I think it's something that is very new, until, even as a foundation, when we started in 2018, the very core of the contributions will come from vendors, will come from technology vendors, which are, of course, way more familiar with open source and open source contribution in particular. In 2020, eight out of 10 top contributors to Finnaz come from pretty well-known financial institutions like Goldman Sachs, JP Morgan, Morgan Stanley, Citi Deutsche Bank. And again, this is what makes us think that open source and open source contribution is here to stay in the industry. But it hasn't always been the case. You just need to go back eight years to find articles like this one being pretty much the norm. Some people would not trust open source. Some people would flat out say in this industry they hate open source. Now, I think it's fair to say that, apart from cultural reasons, open source was considered too big of a risk. And it's still, in large part of the industry, still considered too big of a risk. This is, again, an article from nine years ago. Not sure how many of you are familiar with this case, but there was a big lawsuit between Goldman Sachs and one of their developers that actually allegedly stole code and uploaded it to a subversion repository. Now, the defense was on the other side that this was largely open source code that was taken from the high-frequency trading platform of Goldman Sachs. But this was a big moment in the industry that, for whatever reason, associated open source to this notion of risk, to this notion of, again, even more than what culturally the industry had already as a very highly competitive industry, as a very regulated industry. This was one of those sort of objections that was generally brought up when, especially early in the days, we were discussing about open source contribution. But then somewhere, I would say middle of the last decade, 2014, 2015, things started to shift, kind of bringing back an example of Goldman Sachs. On the left side, I don't know how many of you are familiar with the platform called SecDB, the Securities Database. That's basically a platform that is used throughout Goldman Sachs to represent securities and providing API access to basically the whole firm on, again, instruments of the day trade. Well, this platform was widely regarded, that's the article on the left in 2013, was widely regarded as Goldman Sachs secret sauce. What was their competitive differentiator with respect to other firms that had a much more fragmented representation of their securities? Now, if you only fast forward four years, same publication, same platform, that was starting to be seen as a weakness. Why is that? Well, fundamentally, this is a fully proprietary platform based actually on a language. There is an internal language called slang for which there exists no talent out there. And so on one hand, the lack of talent in maintaining and evolving that platform was considered the weakness. But beyond that, other competitive institutions started building their own single dealer platforms on open source languages like Python, for example. And if you pair that with the vast ecosystem of AI and ML libraries that is built every day by the open source community on Python, well, then it's pretty clear how in just four years, the very same secret sauce was starting to be regarded as a liability in the industry, as a potential weakness moving forward. And so we've seen the industry starting dipping their toes in open source. And to be clear here, the industry has always consumed open source. They might tell you that they didn't, which actually opens up a whole different conversation on compliance and regulation. But what never happened or at least never happened to the extent that we're seeing it today was open source contribution. And so I would say mid last decade, we've seen, for example, the AMQP project, open source by JP Morgan with the help of our friends, Red Hat. We've seen Open Mama, actually, a project under the Linux Foundation who is now under Phinos, being open sourced by, again, JP Morgan, Deutsche Bank, and several of these firms. We've even seen examples of collaboration or creating foundations around open source that haven't been necessarily successful. The article on the top right, you don't see the name there, but it's an effort called Loadstone, which was really an effort between Deutsche Bank and HSBC to try an open source. Really, the capital markets infrastructure, the basics of the capital market infrastructure, in a way that they would basically disintermediate some of the vendors that are very much incumbent in the industry. Unfortunately, that approach didn't really work well. It wasn't set up as well as the Linux Foundation. It sets up governance and structure around a truly level playing field. But it was at least an attempt and an understanding that open source could be really a counterbalance for an industry that is very much dominated by incumbents. And then I'm particularly familiar with the example on bottom left. The Symphony Software Foundation, in fact, is the predecessor of Venus. It's the foundation that I had the honor to start running in December 2015. And that was actually a fair attempt at creating a chat collaboration platform that would be providing basically an infrastructure for banks and buy side and the sell side to really trade and very much the business is now based on chat. But if you think about the exchanges, that is not necessarily how it happens anymore. There is a lot of communications that happens over different media. Chat is really the backbone. Most of it happens in Bloomberg. And so 12 institutions kind of joined together to create an open source alternative to Bloomberg. Now, let's say that there were some good things around the Symphony Software Foundation, including creating the trust and the awareness that a foundation and new throat third party was needed to really disintermediate an industry that, again, is very, very culturally competitive, culturally risk averse. And so we think that's really the beginning of what we're seeing right now in terms of active contribution from financial institutions. I want to stop for a second to analyze some of the trends and the reasons why we're seeing beyond the talent aspect that we discussed. Why are we seeing financial institutions taking the leap into open source? First of all, if you're familiar with how the industry has been going the last 10 years, now 12 years since the crisis in 2008, certainly the margins have been shrinking, both in terms of the top line. I don't have my presenter notes in front of me, but over the last 10 years, the revenue of the top 12 investment banks went down. I don't remember what was the number, but it's basically like JP Morgan and Goldman Sachs disappeared in terms of how much the revenue is being threatened by, of course, ETFs and other electronic trading instruments. On the flip side, the bottom line, after Dodd-Frank and the regulation in 2009, there has been a huge amount of increased spend, I think 30%, 40% growth in terms of the regulatory spend of these institutions. And so there's simply not as much money to throw at technology problems as there used to be 10, 15 years ago. And so I think this is one fundamental aspect as to why we're seeing firms looking for more and more efficient ways of innovating in their technology organizations. The second undeniable factor is what you would refer to as the democratization of the industry, which is still at the very beginning. But if you pair the fintech wave and the amount of investment that is going into smaller, vertically focused, customer-centric focused ventures, as well as the decentralized ecosystem, we have our sister foundation Hyperledger, who has really made a huge impact into the growth of that ecosystem. Well, then that clearly threatens the very definition of what it means to be a financial institution. And so while, of course, there's been a lot of reluctance to embrace this world, there's also the clear awareness that something has to change in the way these institutions run their business and, of course, run their technology stacks. And, of course, number three, I think it's pretty obvious by now, most of financial institutions consider themselves technology companies or want to be technology companies. I think there's still a fair road ahead there. But they are undeniably very technology-centric. This is a pretty much fully digital business at this point. And so the move to cloud, all of the organizations are going through cloud, the fight for talent between East Coast and West Coast. I mean, there is this interesting hate and love relationship between the East Coast and the West Coast, whereby on one hand, banks are angry at the West Coast for stealing their business. But on the other hand, they keep on trying to imitate them and taking executives on a daily basis from Amazon, Google, Microsoft. And so whether this is, definitely I'm not saying that this is a process that is complete, but it's certainly a process that is driving a more and more mind share. And open source in my mind is one of the sort of least kept secrets of the West Coast in terms of how they continue gaining a competitive advantage with respect to financial institutions. And so in 2018, based on what we had created through the Symphony Software Foundation, first and foremost, the trust among these financial institutions, we realized that there was, the timing was right to launch an entity that became FinNOS, the FinTech Open Source Foundation, that could really become the steward for open source collaboration in financial services. Now, let alone that it's not a platform, it's a foundation, but that's what you got from press. And you're going to take it, since it's on Forbes. And that was really the beginning of what we know today as FinNOS. I'm not going to go through the whole history. I think you guys haven't heard enough presentations today. So I'm not going to go through the whole busy slide here. But what I want to highlight around the history is we started really with 12 major financial institutions with the goal of enabling them to do open source. And so in the first couple of years, contributions were mostly from vendors. The banks were simply not ready to contribute to open source. I mean, I don't know how many of you work in financial institutions, but a developer at Goldman Sachs or JP Morgan could not access GitHub in 2018. It's almost like when I was a consultant and I couldn't access Google at my customers. It was pretty much useless. Then in 2000, so the first two years were really about enabling open source readiness. And we'll talk a bit more about that in the next slides. But what really changed with the major switch happened in 2020. And I think you probably heard this line before, but the pandemic has provided some degree of digital acceleration to this industry. Certain trends that were already started, as we saw earlier in this decade, definitely accelerated, including, for example, I can now use Zoom in my meetings with banks, which was, I had to use Webex for several years. Again, nothing against Webex, but it's good to be able to sort of adopt new technologies. And I think in the same way banks got more comfortable with remote working, we were very well positioned as a naturally distributed community to show them how it's possible to be productive in a technology organization while working in a completely distributed remote way. And so in 2020, we started seeing this uptick of contributions from institutions that, frankly, hadn't done much of that before. We've seen Goldman Sachs, JP Morgan, Morgan Starley, Deutsche Bank, and Citi contributing years and years of intellectual property, and not only so, starting to work in an open source first way. And I'm going to come back to that as to what that means. Now, before we go into a couple of these examples, a couple of these projects that we have the honor to host in Phoenix, I just want to kind of manage expectations here. This year, in partnership with the fantastic team at the Linux Foundation Research and some of our partners, we pro GitHub and ScottLogic. We've ran our inaugural state of open source and financial services survey. We really want to create a baseline in terms of where the industry stands. Of course, we have qualitative information having been in there for a while now. But it's always, I'm a number guy. I'm a data guy. And we want to create a baseline as to where the industry is when it comes to consumption, contribution, culture, and just really readiness of the industry to collaborate in the open. The reason why I bring this up here, and I'll show you a couple of slides, is, yes, there is clearly a much stronger realization of what the benefits of open source are for the industry. We'll talk about those. But we're still far away and certainly lagging other industries when it comes to policy, when it comes to the corporate structure and the really ownership of open source within these organizations. And this is not surprising, but I guess it's really good to have hard data on it that we can work and improve over the next years. Particularly, I think, again, this is something that just a few years ago, having had to sort of pitch to several of these institutions, it wasn't well understood that innovation, time to market, reduced total cost of ownership, talent retention, were top motivators for any technology-centric company to really engage in open source. And now, if you look at this data, again, this is a sneak peek to a survey that is going to be released next week, over 75%, 80% of the respondents of this survey, and this was over 300 respondents, a pretty good sample across the industry, do understand the value of open source. And again, that's a big thing from what we were even five years ago, where open source was mostly considered a risk. And the industry is starting to structure for it. I know this might be a little small to read, but this is showing how many of our respondents had consumption of policies within their organization for consuming open source. And among sort of different degrees of completion, completeness, over 70% of the respondents have a policy for consumption. Again, this is something that even a few years ago was probably not as clear. When it comes to having an OSPO, not surprisingly, the industry still probably only one of three respondents has a formal OSPO. That said, I have personally seen five to 10 large institutions this year hiring an open source program office lead to a certain degree, not extremely senior, but quite senior organization, sort of quite senior leader to structure their open source program. And so again, in terms of managing expectations, there's still a long way to go. Several of our respondents, I would say still the majority, still see a fear of lacking intellectual property, legal licensing concerns, clear lack of ROI as reasons for not fully enabling a firm-wide open source contribution policy. And so again, I think this reinforces very much the work we've been doing over the last few years, shameless plug here, around open source readiness. We're super excited to have five-plus financial institutions actively contributing to the foundation. On the other hand, there's still a long tail of institution, as we've just discussed, that still either don't value open source, the strategic value that we think you should have in such technology-centric companies, still don't have internal policies, or still sort of leave of a cultural background that is still very much brisk averse and there's still very much siloed. And so we continue to run in-finance, now in partnership with the Linux Foundation, with the Tudu Group, and the several other initiatives around this area that exist in the LF ecosystem, what we call our open source readiness program. We're really working to get banks to the place they should be to be able to contribute to open source. And with the realization that there is something particular about this industry when it comes to regulatory requirements, regulatory concerns, before they're ready to sort of prime time. Now, the reason why we continue investing in open source readiness is really because we have seen firms gain more and more value from open source as they increase their open source maturity. So unsurprisingly, when we started, most of our projects were very much focused on the technology organization. For the values, for the sort of value proposition that you probably are very familiar with, whether it is talent acquisition or retention, whether it is efficiency through mutualization of common technology, whether it is de-risking the investment on a commercial open source vendor. And so the earlier projects and some of our special interest groups continue to evolve in that direction. Open source readiness, DevOps mutualization, cloud service certification, inner source. There's a lot of sort of practice that I think we think in this institution, it's still lagging what probably you guys are used to. And the open source community at large is used to. But especially over the last two years, we have seen that those firms who have a much clearer understanding of the strategic value of open source and have at least started the journey of structuring their internal organizations to be able to allow developers to not only consume but contribute to open source projects, are now realizing that there is power in open source collaboration beyond code, driven directly by business needs, whether it is a faster interaction with their clients and a better, more efficient interaction with their clients. I'm thinking banks and wealth management, whether it is a better collaboration with regulators.  We'll talk about it in a little bit. Whether it is, again, just collaborating with their peers in sort of uncommon industry challenges, even basic data standardization, it's been a huge issue. If you think about it, this is an industry that by nature needs to interact with each other. They're trading on the same instruments and they need to report to the regulators sort of on common requirements. So it's an industry that at least in principle has a lot to gain through open source. And then finally, again, this is probably, I'll count the firms on sort of one hand probably, but we are seeing some of those really starting to see open source as a strategic pillar of their technology strategy. And in a way, becoming more and more akin to financial, sort of to technology organizations, to big tech. We're seeing more and more platforms being rolled out and I'm a personal believer that platform goes very well hand in hand with open source. Open APIs, open standards, SDKs for your developers that you want to maximize usage of and therefore open source really works well as a companion if you're trying to sort of do a platform play. So once again, another validation of why we continue to invest in open source maturity of this industry. Now, the last 10, 15 minutes, just a quick overview of how we do this and some of the key projects that we've seen these banks collaborating on. It's pretty similar to, I think any foundation under DLF. We have infrastructure. We have a very structured and proven to be successful software and standards governance. We talked about the open source readiness initiative and then I think one kind of realization is that we need to do maybe a little bit more work ourself as a team than in more mature open source communities and so together with our member success really trying to make our member realize the value of open source. We have a lot of focus on project success. We'll probably gain a bit more hands-on than for example, a Linux kernel development community as a team. Now, I wanna show you a couple of the projects that we've received over the last years. Very much all the projects that you see here minus one have been contributed by financial institutions. Perspective was contributed by JP Morgan in 2019. Walt was contributed by Deutsche Bank in 2020. Legend, it's our biggest project contributed by Goldman Sachs this year. Sorry, last year. Morpher comes from Morgan Stanley. Again, last year, 2020. Cloud service certification is JP Morgan. FDC3 is the one project that was contributed by a vendor but is now used by several financial institutions. And again, Plexus, Deutsche Bank. So again, just to show we think that there is power in end user driven open source communities and we continue to invest in fostering banks to open source intellectual property and to hopefully build on each other's achievements. I wanna touch quickly on Legend which is by far the largest project that we have. This is a logical modeling visual, logical modeling platform. Open Source by Goldman Sachs in 2020. It has an underlying language. It has a visual editor. And not only have we seen other financial institutions now adopting it and using it internally but we as a foundation are actually hosting this platform and we are inviting business folks to directly collaborate in the open. And so kind of going back to the technology organization and the business level value. It's not only about your typical mutualization of open source, say yes. Goldman Sachs has open source this platform. By the way, deployed on Maven Central on Docker Hub. This is open first. Goldman Sachs, this is not a dump and run to be clear. Goldman Sachs deleted their branches internally so they are really consuming from the open and we're seeing contributions now coming from other institutions. But I think the interesting bit is we've also seen by the means of hosting it in Finos, we have been able to invite business folks to collaborate directly on the platform with the output of collaboration being a data model. A standardized data model that can be used across the organizations and potentially can be used with regulators for the regulatory reporting. And in fact, that's why we're also investing in our relationship with regulators. So I think this is a really powerful platform. Love for you to try it. Again, you don't even have to download it. If you go to legend.finos.orgslashstudio, we'd be happy to provision access to it as long as you have a CLA. The other project kind of going on the other end of the spectrum, a standard project. FDC3 stands for financial desktop collaboration and connectivity consortium. I realize it's a bit of a mouthful. But it was, if you're familiar with how traders work with their like five screens and 50 applications running, well, this is the standard that is trying to create a common connective tissue for these apps to interoperate with each other and interoperate with the underlying desktop environment that they're running on. It was originally open sourced by a vendor and now we're working to have financial institutions define what the use cases are for the next version of the standard. Once again, very much end user driven. I think a testament to it is that I'm actually able to show those logos out there. It's not that easy to get a logo from financial institutions, even though they're all using them, but having them on the record and being able to promote the fact that they've been using it, it's pretty big. I think CT has come to one of our meetings telling us that they use it for about 900 applications internally. So pretty mature and we hope valuable project moving forward. We talked about ROI quickly before and some concerns that there are still in the industry around ROI. Perspective is a real time visualization library, open source by JP Morgan, over a thousand starts on GitHub, so truly open source project. These are the numbers that were shared by one of our platinum members about two years ago in terms of the savings and efficiency and ROI that they got by using this software. Now, I realize it's a pretty high level, it's a pretty rough set of metrics. We could spend probably a whole other hour session on discussing the ROI of open source, but I think it's pretty powerful again to see a financial institution, which shall rename unnamed, sharing the over $3 million savings that they had by using this library. I'm not gonna spend too much time or at least some time for questions in terms of our special interest groups, but again, this is a concept that actually we didn't have until we joined the Linux Foundation. We realized that there is room for basically coalescing common interests in our foundation whereby maybe certain organization are not ready to contribute code or to work directly on an open source project, but they certainly have common challenges, whether it comes to, again, open source readiness or mutualizing or conjugating the notion of DevOps in a regulated industry or working together on common regulatory implementation. The hope is, of course, that the special interest groups will spawn off into actual open source projects and open standards, not just remain talking groups, but that's really something that we launched October last year, and we've had already five being started and being pretty lively. The one that I am personally most excited about is our OpenRectec. Now, in principle, mutualizing open source regulation seems like an obvious concept, meaning when we collaborate in the open, we collaborate on areas where the requirements are common across multiple parties, and regulation sort of tick that box. We typically collaborate on areas where there could be some cost savings by collaborating, and as we discussed before, the cost of regulatory implementation for these institutions has become huge over the last years. Think about MIFIP too. So where we started was really to try and enable banks to mutualize regulatory implementations. Now, there is the hope that maybe when my grandkids grow up, we could have also the regulators themselves produce machine-readable open source regulation. But again, I wanna manage expectations here, and I have to wait for my grandkids to grow. That said, we've had really good engagement from regulators, like the financial institutions there also on a spectrum, I'm not saying the spectrum, on a spectrum of maturity when it comes to open source. Some are really familiar, some they have their own GitHub organizations, some others, we had to restart the conversation from what is a computer. But this is an area where we expect to continue investing in the next years, and we see a lot of potential to really become indispensable in the industry. One of the projects that is really related to mutualizing regulation is our cloud service certification project. The goal is to really have a truly open source framework for proving compliance to financial regulation when it comes to cloud deployments. We are working on a partnership with another organization called CDMC, Cloud Data Management Capability. But in the meanwhile, I exhort you to take a look at our cloud service certification project. We have JP Morgan, Deutsche Bank, and several vendors already working on it. Again, with the idea of this is a journey that every financial institution is undergoing, and there's no reason why each institution should be doing their own financial regulation implementation when it comes to cloud. And we certainly could use the help of technologists who are very familiar from tech companies with these issues, and have clearly invested interest there. Now, just to, as I wrap, there's much more to open sourcing financial services. In Phoenix, we've had one new project contributed every month this year, but admittedly, there's much more than this. Only this year, we've seen, if you're familiar with Move, it's an open source, basically embedded finance platform, truly open source with the building blocks being completely open. I just came across two weeks ago to Game Stunk Terminal, I don't know if you guys are familiar, is an alternative to Bloomberg that really came out with the frenzy of GameStop, and the democratization of retail investors. So it's really lively space, and we think that there's a major opportunity at the crossroads of open source and fintech. So looking forward, and hopefully I can leave a couple of minutes for questions. These are our themes for next year. We continue to enable these firms to become tech companies, leapfrog into tech companies if they need be, cloud and open source readiness, and finally, the developer centricity that we're seeing in the industry. I have to say I've had the luck of always working in open source, and when five years ago I understood how the developer experience of certain developers within some institutions, you know, I took it personally, I took it at heart. I think there is a liberatory aspect to open source in the industry. Ecosystem interoperability, API and data standards, we talked about legend that continues to be a cornerstone for us, and in the way we work with regulators, and certainly the business of open source. We're seeing more and more business-driven initiatives. Ultimately open source, it's a collaboration model that goes way beyond code, and I think we're finally sort of cracking that knot when it comes to financial services.  Open source in financial services is a positive sum game. I'm gonna skip the build here and just do a final shameless plug. We are back in person. This is my first conference as I said after a year and a half, so forgive me if I was a little rusty. But our conference, the Open Source Strategy Forum, powered by the Linux Foundation, is coming back in person. Not sure you're gonna be able to be in London next week. I will, or in New York, hopefully, in a month from now. But this is the sole conference for open source in financial services, and I'm so excited to get back to seeing our community in person. OpenSourceStrategyForum.org, I hope to see you there. And with that, I am done. Is there any question? I know I spoke a lot and we are at the end of the day, so I won't be offended. Got the guy back there. That's a really good question. I would say there are, as I said, two or three companies that I can think are already in that stage, and I think it's a combination of, one, they are generally a little bit more nimble than some others. For example, I think that's a really good question. I think that's a really good question. I would say there are, as I said, two or three companies that I can think are already in that stage, and some others, for example, well, let's just be kosher here, but they are generally smaller than some of the bigger ones, especially some of those are, for example, just investment banking versus investment banking plus retail, and when they are, even when you are talking, say, 20,000 people versus 100,000 people, makes a big difference in the way they can move. I think, secondly, they have embraced this process much earlier than others, maybe 10, 15 years ago. I do think that open source readiness and what we've done helped, but it cannot be the sole driver. I think there is an executive leadership that has a much clearer idea of why open source, at least from my perspective, stands pretty much like cloud, should be a technology pillar for their sort of overall technology strategy. That would be, so I think size, executive leadership, and just, to an extent, culture. So the executive leadership enables the culture to evolve faster, I would say. Any other question? Please. Is how do you see this being driven by the development team or is it just for you to see this? It's a really good question. I would say when we started, about five years ago, I constantly got questions from developers saying, please help us to talk with our lawyers. Please, they just talk a different language. Can you help us sort of mediate the conversation that, I mean, five years ago, I mean, still, but five years ago, GPL was not a word that you could say in any of these conversations.  But so I would say it started developer driven. It started sort of bottoms up. Two or three years ago, even five maybe, talent, like the quest for talent and just the, you know, I don't have infinite amount of money to throw at technology problems, really help the conversation with executives. So it was developers. I think then we gained support of the executives. The hardest part still remains the frozen middle, like those 20 layers in between maybe the individual developers and the executive, whereby the skew between sort of cost benefit or risk and reward, it's still very much skew towards sort of being risk averse. Like why would I risk to put this piece of code out there when I don't have yet a direct incentive from my boss or sort of a company mandate to do so. So that I would say still originally driven by the technology organization, developer first executives, and now we're trying to tackle sort of the frozen middle more from the business side of the house because that has to sort of fundamentally change their incentive model. Does that make sense? You're welcome. Any other question? I think of course, they're being so nimble and they're doing the whole industry. Are these big guys trying to find, they can't change so easily. They're not going to go over so that they can see the future coming and they can't change what. Yeah, I mean, it's an interesting question. I would love also Daniela's opinion here from Hyperledger, but I would say it's still a hate and love relationship from where I sit, meaning there is this sort of curiosity and understanding that they can't just ignore this whole movement, whether it is the fintech, broadly the fintech movement, or even further sort of the decentralized DLT crypto space. But at least from my perspective, it's been really hard to see them like taking a substantial leap into bringing those technologies into production. There's pilots right and left, especially when it comes to DLT. There's investments in several fintech companies. I think they still see it more as a VC-backed or VC-type activity where they invest in different companies, but I don't know that I've seen sort of a full strategy to how do we evolve our business into that or how do we prevent us from being ran out of business. Again, there's plenty of attempts. One of my grievances, especially with fintech, maybe less with DLT is I have the fear that we're moving from a centralized mass to a decentralized mass. Like right now we have a centralized mass of heavily siloed stacks where each one has his own ledger and each one has to reconcile at the end of the day and there's clearing and the settlement and maybe because I'm used to instant payments in Europe, I kind of still get a little peaved by needing to wait 72 hours to send money here in the US to someone, but I also see all this sort of very vertically focused fintechs coming up with their own, they're perfect on one specific use case, but there's no data standard, there's no common APIs, so we're kind of moving to a different scenario which ultimately I'm not sure if it's gonna be incredibly better unless I hope open source and open standards can sort of bring it together. So I think to your question, the jury's still out from my perspective, whether they're more trying to stop that movement or whether they're trying to, I think in the last couple of years I've seen much more sort of positive signs of integrating and evolving their business. I think one final point is it's for what I've learned is much easier for them to adopt these new technologies on a new use case versus ripping off a legacy of 20, 30 years where again, it might just be no worth, it might be very risky to change a completely sort of established business process and organization. And so I think where there is potential is on really new use cases and new regulatory requirements and something that is net new, then I see a lot of potential to sort of work through a fintech or work through DLT and hopefully evolve incrementally if that makes sense. That's a really good question. I mean, I think there are one of the areas where we are investing a lot is open rectangle because I think regulation and regulators have to play a key role in innovating the industry and not just sort of potentially slowing down change but especially I'm less familiar with Asia. We have less Asia members although I know they're doing amazing work, especially with the Monetary Authority of Singapore in the payment space. Again, I think there are better qualified folks than me to speak to that. But when it comes to Europe and the US, I think for better and for worse, European regulators are a bit more empowered to impose change. Again, whether it comes of course with other side effects but I do think that having international standards that apply to everyone does indeed help this process. And so I think in the US, it's still very much left to the private sector to innovate and sometimes the incentives of the private sector might not always be fully aligned with sort of macro systemic improvement. And so again, I think it's, we're getting into sort of political conversations here ultimately but I do think that there is an advantage, maybe because I'm European as you can hear from my accent but there is an advantage of having regulators that can help setting standards and hopefully we can implement them in the open so that they don't become too much of a burden. Ultimately, there is a third way between regulation and the regulation and we hope open source regulation is that. Any final questions? I'm getting a nagging, so I think, thank you. Please, Daniela. Yep. Yep. Yep, you're welcome. Yes. Yes. That is amazing. Thank you, Daniela. I really appreciate the feedback. Thank you, everyone.


Dear colleagues and friends, WHO is proud to partner with the Patient Safety Movement Foundation in our efforts to eliminate harm in health care. The WHO Global Patient Safety Action Plan 2021-2030 is premised on the principle that patients should always receive safe and respectful care, no matter who they are or where they live. This year's World Patient Safety Day is dedicated to eliminating avoidable harm in maternal and newborn care.  Far too often, this is the result of unsafe care. Moreover, most of these deaths and harm disproportionately affect people in least developed countries and among disadvantaged populations in every country. Due to inequities in access to safe and quality care, no woman or baby should be harmed in health care. That's why WHO is launching guidance for health care facilities and providers around the world on best practices for maternal and newborn safety, particularly around childbirth. WHO calls on all partners to act now for safe and respectful childbirth. We invite you to join us in lighting up a monument in orange in solidarity with women and newborns everywhere. I thank you.