So our story started pretty early. Demonware has been around for over 20 years providing services to games. Activision acquired them, so they were providing games before that. But we originally just ran on bare metal. It was quite normal back then to do that. As time progressed and the internet grew, we had to change how we did things. So we introduced sharding to our bare metal databases, and it worked for a while. As time went on and our catalog grew, we had to adapt. So we thought, hey, why don't we use KVM and LXC to make it more flexible and build an orchestration layer in there and make it more manageable. And that was good until we hit thousands of databases and it became kind of unmanageable. So we started building something on top of that, which managed the connections and managed the failovers and errors and all that. It worked, but we were kind of still a little bit stressed by it. So as we continued through there, we investigated some different things, and it came that we kind of figured out the challenges that we were looking for. So Vlad is going to talk about that. Yeah, we started seeing multiple operational issues, which were challenges for us when we started to find solutions how to fix them. What we did is we worked with multiple service teams and we identified few key areas of the issues that those teams were seeing. The first area was around scalability. Activision launches several AAA game titles every year. A game launch is very important even for us, where many billions of players will show up at the same date around the same time. And this is maybe a very pleasant problem to have for a business, but it's a very big technical challenge to solve. To have a smooth experience for the game launch, we prepared many months before and we spent a lot of time low testing, low testing how the new game client behaves, what are the new workloads that we are seeing from the new game title. But we also tried to predict how many players will show up on the launch date. It's not always possible to predict exactly how many players will show up, so what we tend to do is we over-built our database platform to handle any potential peak that we might be seeing during the launch. You would think as the time goes and the workload decreases after the game is launched, you would think that we would decrease the capacity of the database in order to save resources. That sounds logical. It's not that easy though. We were able to scale out our database in a certain hacky way, but we weren't really able to scale down without having a significant player impact. That's why we actually never or very long time ago scaled down our database after we had launched. Another scalability issue which I would mention is about connections. Since our application layer has no database connection pooling at all, we were seeing databases running with more than 10,000 connections, which was extremely painful and was causing MySQL performance issues related to CPU and the memory. Another area is about operational burden. At our scale, we see hardware failures happening every day, those affect databases. We had quite thorough automation in place to automatically remediate a primary failover. If MySQL primary went down, it would have been automatically failed over to one of the replicas. Still, there was a lot of operational overhead for on-call that had to run a manual Ansible automation to replace missing MySQL node. We run on-premise, we run in a data center that we've rarely seen large-scale issues with, but I'm not saying we haven't had any issues. We had few large-scale infrafailers that resulted in many engineering hours to fix broken MySQL replicas. What we saw is that MySQL replicas, at least in our case, broke in ways that they couldn't have been used as the new potential primaries. We just had to replace them and we had to replace several hundreds of such broken replicas. If such thing happened, it was extremely painful. As I mentioned earlier, we were lacking a robust scaling solution. We were able to scale out, but only by doubling number of charts. That was not ideal because scaling by doubling is probably not very resource efficient if you just want to add only, let's say, 10%. The last area which we identified was about the setup complexity. Demolware operates in multiple platform and service teams. Service teams own their own database operations. As such, each team is required to have at least a certain level of database operations experience. That's not always true for every team and some teams were delayed by this because they had to wait for help from other teams. The large-scale database build-out and we are talking about the database with over 100 charts took a very long time. It took between two and three days and this was not acceptable for development agility when you wanted to iterate on the database quickly. When you wanted to change configuration, try different things. For example, build database, build database, it was delaying us. Schema migrations were also hard to execute by certain teams. Those required high experience running database in production. They required very careful planning and execution that often led to delays in development workflows. That led us to finding a solution that would address these key areas. The next section is the Tech Adoption. I ran the Tech Adoption for Vitesse at Demolware. We started by doing a next-gen DB evaluation.  This is six of them, but I think we had 100 in the spreadsheet. We went through many different products. All of them were working at some level, but we decided that the major things that we wanted were the SQL query compatibility, so that the application didn't really have to change anything. We wanted it to run my SQL on the back-end, if possible. Currently, when we started this, we were looking at our platform and we were saying, everything is moving towards Kubernetes internally in the company. It would be nice if we found something that was Kubernetes native. A bonus feature would be that it provides an operator. After taking these all into account, we evaluated and a test came out as a pretty clear winner. When we started the adoption process, we discovered that Vitesse was a near drop in replacement for most of the services that we had targeted.  Those people, when we had problems, we could just be like, hey, we're seeing this thing, what's going on? 99% of the time it wasn't a problem with Vitesse. It was like, hey, we can change this or do this, this way, and it was fine. Another big thing was that there were a lot of success stories from other companies just in the community we heard about. We joined the Vitesse Slack and random people would come out and see us asking questions and just be like, hey, what's going on? I reached out to a bunch of people and was just like, oh, I see you asking questions. It was a pretty lively community. We're going to talk about two main parts of the adoption. The small service, which was a social service that was not critical path. And a large service, which was fairly business critical. So I ran the first track of the small service where we were doing a lot of platform things and Vlad ran the large service. So small service wise, why we chose it? The backstory of this is actually a little bit different. We had targeted to do a large service and we were like, okay, well, if we can do our most complex service, then we can do any service. And as time progressed, we were like, no, that's actually not going to work. So I was actually walking on the seawall in Vancouver with one of my coworkers and he was like, why don't you take our group service? And just like, it's new, it doesn't have any data. Just use that. And I was like, okay, let's do that. So like a few days later, we had started working on it. We got to start with fresh data, which was quite nice. We didn't have to do a migration. As I mentioned in the previous slide, it wasn't in the critical login path. So if something did happen with it during the proof of concept, it wasn't going to block players from logging in. Another feature of it was it was very easy to make architectural changes to it. So we didn't end up making that many architectural changes, but we made some and it was much easier to do to a service that was not in production. What this did, though, was give us an opportunity to see what a service would look like running on our Kubernetes platform. So we had to do a lot of work with how volumes were managed, how the pod disruption budgets, work all of those things out. We couldn't just go say, hey, we're going to run the test on our Kubernetes cluster because it wasn't going to work. So we spent a bit of time building this and integrating it into our platform, which built a good baseline for other services. So the timeline, when we first started looking at this for v0, we weren't very serious about adopting it at the time. We were like, hey, we should build a proof of concept. There was a few engineers and we were like, we should build a proof of concept of this and see what it looks like running. So we were like, if we're going to build this and move it into our Kubernetes platform, maybe we build it parallel to what we have now, see how it runs and then migrate that into the Kubernetes platform. We didn't get super far with that. So we started doing it. We got it running, but it just didn't seem like there was no magic moment. So a little bit of time passed and we were taking it a little more seriously. And we moved to a v1, which was using the now deprecated helm charts and on our Kubernetes platform. And I think we kind of had it like that magic moment where it was like, okay, this works. And we started, we had tied this setup into the small service that I was talking about. We had run queries against it. We had done even, I believe, some like minor load tests and we were like, okay, this is, this is, this is real. And as we continued, we were like, okay, now we need to figure out like these operational burdens and the other things that we're talking about, you know, what, how are we going to deal with that? So the helm chart was working good, but we just, you know, it was missing something. So we decided to be early adopters of the operator, which, you know, it was, it worked out of the box. It was, it was, you know, we could just throw our cluster definition in and we had a, a working system there. It still, it was, it was great. And we were like, okay, this is like almost on par with what we have like right now. But it's still like, we like why this, this feels like a vertical move and not like an upgrade. So we decided to be, we may have been one of the first adopters of Vtorque, which we were, we were, we were confused at how well it worked. We were doing bad things to clusters and it just wouldn't, it wouldn't die. So we ended up shipping with our, this V3 into production for both the small service and the large service. And yeah. So the proof of concept, how it actually went was it was like the previous slide with the timeline. It was pretty slow to start because there was a lot of different ways we could do things. There was a lot of, you know, it felt like it wasn't just something who Google because there was not really anybody that, you know, was, was running it like how we were running it.  It turned out that our platform team was great and they ended up, you know, helping quite a bit and it went pretty smoothly. Once we had it like fully working and everything we started on the testing of the small service. And it was ruthless because this is when the people come out of the woodwork and they're like, what about this small edge case? Like what, you know, what's going to happen when this happens? And it's like, yeah, I can, I think this and they're like, have you tested it? And I'm like, no. So there was a lot of edge case testing, which turned out to be very helpful at the end. We ended up testing shard expansion up and down during one of the larger betas. And it worked flawlessly for us. We did vertical scaling. We tested that adding CPUs, adding memory, no issues. And we did a lot of recovery and error handling testing, just deleting, deleting shards, deleting parts of shards, deleting everything, bringing it back. And it was, it was the first time it happened. I actually did it accidentally. And then I went to the washroom and came back and I was like, why is this still running? I deleted it. And I was like looking at my history and looking at the events. And I was like, okay, this is, I was like, I didn't realize that the backups were something that were automatically triggered when the anyways, it was, it was unexpected. But like quite nice. We started the load testing and it went pretty well. And, you know, during all of this, we started building quite good relationships with the open source community. It was, you know, really, really helpful to have them. They helped out a lot. And then we launched and it was so successful that nobody talked about it until January when they were like, okay, we're going to look at a much bigger service here. And we're going to try and implement it for that, which Vlad was mainly working on and he will take over. We had very great experience from adoption on this small, small service. As Greg mentioned, we were thinking, okay, what's next? What are our biggest pain? What's our biggest pain and where which service has the biggest pain? So we were absolutely clear about that we, we are continuing with a large business critical service. Which you may think like, oh, that's, that's really crazy.  Like, why are you picking the business critical service? Well, the main reason was that we just recently finished execution of manual scaling operation that had been very stressful and painful operation that took several sleepless nights to finish. And we, we had committed ourselves that we don't want to repeat those nights again. And we want to fully automate the next scaling operation for this large service. What do we picked? We picked what we call inventory service. What is this service doing? It stores, it mainly stores player items. So you can think of inventory of what a player owns in the game. Examples would be guns attachments, like various modifications. There are like, even things that you would not really consider to be items. So like anything in the game that can be related to a player and it's in a way granted by certain achievements. It's huge. The database is huge. I'm not saying like we've reached these numbers in one year. Like it was over, it was over a few years. But at recent launch, this database saw peak requests at half million requests per second. And the data size has been a pain too. We are seeing nearly two times increase in size every two years, which makes it like additional challenge on top of the request rate that we are seeing. How we tackle this? We identified few adoption, high level adoption stages. We knew that it's not going to be easy. This service has been around for more than eight years. It's a big monolith application with very complex business logic, full of transactions, uses foreign keys in the database. So we knew that it's going to take some time to get there. And if possible, what we were trying to define is what actually an MVP for an existing service would mean in our case of adoption VTES. So we came up with a definition of core functionality of the service that we needed to be running on VTES. It sounds easy. You identify, okay, this is important to my application, but how do you confirm that such thing actually runs without any disruptions on your new database? Fortunately, we had a very good unit and integration test coverage. So we decided, yeah, why don't we use those tests to confirm that our integration works on VTES? Initially, when we run our first attempt, it looked scary. About 50% of the tests were failing and we were really, I'm not saying like, we were not ready to give up. But it felt overwhelming. What we did is we tried to, like obviously, I need to mention that it's about 4,000 unit tests that this service has. And like when you have 2,000 tests failing, you won't go one by one. Instead, we tried to find similarities like why these tests are failing. And we were slowly coming up with similar patterns and similar issues. And we were able to group these unit tests into a few smaller set of issues. And we started tackling the problem of adaptation in a more systematic way. MVP took about two months to finish. We were able to resolve all these issues that we set ourselves for this basic MVP. And along this way, we found ourselves stuck a few times where, as Greg mentioned earlier, it was a really great experience for us to work with the community. We want to share what we learned along the way. We are mentioning only like few incompatible, few sequel incompatibilities or a different behavior, which was not necessary a blocker for us, but like it required some, I would say, minor work to update our application code. The first one that I'm showing here is about the MySQL name blocks. The application was full of them. We were having multiple places where we needed to stay synchronized to protect the data and stay consistent. What we learned with Vitas was that at least with version 14, that's what we are still using in production. Vitas implements name blocks using the first chart, which turned out to be, I'm not saying like a blocker, but a potential performance bottleneck. What we did was to look around the displaces and we updated the application code to the reduced number of logs that we are acquiring per second. Another one is about the foreign keys. I mentioned that the application is full of them. Tables use foreign key constraints to implement certain business rules and Vitas does not fully support the foreign keys. It doesn't mean they don't work. They do for us and they work well. It's just certain scenarios where things were failing for us. Actually, it was only one, which was about when we were scaling, so adding more charts. The operation was failing on those foreign key checks when the database schema was being created. We worked around it by temporarily disabling the foreign key checks on the target new charts. This didn't put data into any risk because the new charts were not receiving live data at that moment, so we felt absolutely safe about this workaround we had chosen. These are just examples. Replace into was heavily used in our data layer abstraction in the application. The problem was that replace into statement by definition requires all columns to be included. This means that you had to include even chart key, but you just can't update chart key in a charting solution because that would just mean that you are expecting to data to start moving between different charts. That just doesn't make sense. It made sense why this is not supported, but we had to update our application to work again. What we did, we just simply switched to using insert on duplicate and that worked. We continued with load testing. We needed to feel confident that the new database solution will handle the traffic that we expect on the game lounge. We already had a lot of experience from the previous years with load testing MySQL workloads, so we knew that MySQL is behind, so we don't really need to focus on those parts. Instead, we focused on the VITAS components that were new to us. We are basically trying to confirm that VITAS components that are on the query path, that they scale linearly with adding more charts and that we would not hit any performance bottleneck. We basically confirmed those assumptions. What we also learned is that the new solution will require some additional CPU resources, which was kind of expected. Anytime you run additional proxies somewhere or sidecars to your applications, of course it will take more resources, but the benefits that we were about to get from the new platform are much more provided the additional resources that we were bringing into the platform. What we learned is that the component which is a sidecar to the MySQL runs on the data nodes, at least in our case, requires about the same CPU resources as the MySQL process itself. That was kind of surprised to us, but we were also positively surprised by the fact that the connection pooling that is provided by VITAS greatly offsets CPU utilization that is on the MySQL process itself. The fact that we were not having over 10,000 connections on the MySQL process anymore, so we went from 10,000, 15,000 to something around 300, 400 connections per database that greatly helped for MySQL to start breeding again. We were done with the load testing, so all our expectations were confirmed, so we went to the last stage where we needed to prove that we will be able to operate the new database at scale and that the database remains stable in certain failure scenarios. We already did a lot of failure testing before and during the small service adoption, but we continued further, we went even more aggressive. Again, we were doing very bad things to the database and it was always able to recover, which was magical. We very much focused on configuration deployment testing, so we really wanted to make sure that changing a database configuration should be seen by people as a normal change, as you would be changing configuration to your application. That seemed to be a huge difference compared to the past where we felt like, oh, database is something precious that you are not touching if you really absolutely don't have to touch. We wanted to change this model, so we really wanted to enable not even database operations people to run these configuration changes. As a result of this work, we came up with tuned with this configuration that we are mentioning a few features that we used and it was stable. What I would like to highlight on this slide is the key points, what has changed. We went from shards defined in the application configuration, so we had pretty much every shard defined in the config. We went to a single database endpoint where the shards are abstract to the application. Previously, shards were defined in the config that allowed us to make certain assumptions when we were designing database queries. Some queries were just too shard aware and there were implicit assumptions that you are working just with the single shard data. Such kind of queries were not running efficiently with Vitas at the first stage, but when we learned that we just need to give a hint to Vitas that, hey, you need to target a specific shard by just including a aware condition that helps Vitas query planner to route your query to just one or subset of the shards instead of all of them. Where we spent a bit of time was figuring out how to expire data with Vitas. Previously, we were hitting the shards individually and we were running delete with limit on the shards in a serial or a parallel manner. When you have a single database endpoint and shards are abstracted, I guess that's the reason why delete with limit is not supported by Vitas, because if you think about it like you can't really identify which rows you really want to delete from those shards. It makes total sense that it just can't be supported for the safety reason. What we did instead is Vitas still supports a way to talk to the shards individually, even though it's definitely not the best practice, but that's what we have chosen to address this issue and we kind of in our data layer we implemented what we call shard walking, where we do pretty much what we were doing before, but we do it with Vitas now. Alright, so yeah, we can get some conclusions from all this information. So the benefits that we had, we now had tested it a bunch, tested it in production scenarios and we had a very proven method of sharding up and sharding down. The shard tools were provided by the upstream Vitas team, which is pretty great. The on call burden that we were talking about earlier was greatly reduced. When we were creating these slides, I was thinking like, okay, there's going to be at least one escalation before this happens. But yeah, to my knowledge, there has been no escalations to our production for test cluster. The operator and orchestrator have just kind of taken care of anything. But take this with a grain of salt. If you do do this and something happens, please don't blame me. The database setup is using our GitOps model, which the rest of the Kubernetes services are using. So the rest of the company is quite happy with that. Yeah, it's overall the benefits that we were looking for have been, we can see them quite there. So I guess did it work? Yes, it worked to our expectations. So much so that we're building a team around supporting it. And currently there were, I would say about one year into opening it up to multiple teams. And there's about 60 separate Vitas clusters running in our different environments. And as of like, I would say about two months ago, Vitas has become the default database solution for anything that we, any new products. And a lot of our teams are kind of jealous of the people running it. So they're starting to talk about migrating their data into it. Thank you for coming here. Thank you to everyone at Demonware who helped make this possible. And thank you to PlanetScale for helping us along the way. And yeah, if anybody has questions. How does this work? We will repeat the question. Yeah. Yes, we started fresh on both. So the, the thing was, was like we had an opportunity to start fresh. So right now we're in our adoption process. We're, we're figuring out the best ways to do data migrations, but it is, you know, it's different kind of for every service. So yeah, we're, we're, we're working on that right now. And it looks quite promising. I think I was wondering if you could speak a little, you mentioned that you use Ceph. I don't know if everything is using Ceph. But if you could speak a little to the Ceph configuration and what the performance is like on Ceph. Sure. So yeah, he's asking what is the performance like on Ceph and what do we use Ceph for? So were you, we initially just used Ceph for the SED backing because the way that the operator had set it up, it was kind of expecting network storage. But then we were like, why don't we move less performance volumes into Ceph storage? So it, right now, I think we only have some test clusters running with the actual data backed Ceph, but it seems to be fine. I don't think we will ever run any like high performance requirement stuff, Ceph backed, potentially just dev environments and, and some staging environments. Is that answer? Yeah. So then I guess my follow up question would be is what's the stored back end for like the prod, the test? Yeah. So we use local storage. So we have our own disk provisioner. And I guess that this is actually the question that a lot of people who've talked to me have asked, because they're like, how do you actually do this? We're trying to solve this. Yeah, we have an in house thing that we use that just pre provisions volumes. And we just create a PVC and it pulls it in. So each server has the PVs available. And then we just say, hey, we want this PVC and they're all pre formatted. They're all everything. So it's, it's not very flexible, but it actually ended up working quite well because with the way we have it set up, we can, it's, it's like, I'm calling it like persistent ephemeral, persistently ephemeral. So, you know, we, we can treat the volumes as ephemeral volumes, but they're quite persistent as well. Okay. I have two, if you have time. So first question is, are you using any high availability, like primitives that the tests provides and like, have you having the troubles with them? And second is when you scale the video tablets, do you see any trouble with the time it takes the video tablet to start and restore from a backup and the load is gone already? So the question was, are we using any high availability tools like cells and like multi-regions things? No, no, no form for that. That's fine. No for the multi-region, but Vitas itself has great high availability built in mechanisms itself. So the proxy layer is, is fully reddened and you just keep adding replicas in the deployment. And the shard is highly available by using MySQL replicas and VT Orc automatically fails over that the primary to one of the chosen replicas. The question about the tablet resizing, I think that that was the question. Yeah. I mean, like we use VT tablets and sometimes we have like load spikes. So we want to have more database, but by the time we restore like a terabyte of data, the spike is gone. So we need to vertically scale and not horizontally scale. Yeah. If you see something like that. So I think what greatly helps in our case is that we use Ceph that is locally in our network and is extremely fast. I don't remember the numbers. We're on like a hundred gigabit backbone so we can just like pull it. It's very fast. And what we also did to, I totally get your question because that was one of our implementation requirements to make sure that the replica gets recreated even including ketchup. MySQL replication ketchup under 10 minutes. So like with this large scale database, the new replica gets up under 10 minutes. Thank you. I think we should cut it there. And if anybody has questions, just find us and we will be happy to talk. Thank you.


Let's begin bro. I'm so worried to react to this, but I'm also like so excited Yo, when am I gonna title this this YouTube video lolly con reacts?  I don't know what jobless reincarnation means What was he jobless like most of the people that hate on my videos here? We go the adventure begins Can you hear me? Oh?   Oh wait. He was hit by a truck. That's my prediction So you're telling me truck coon killed him truck coon strikes again Whoa, whoa, whoa, whoa, whoa, whoa Two high school students thought to have also been hit. He's gonna be reincarnated with three high school students What does a recluse mean like a shut in all right introvert like me so I'm a I'm a recluse God speaking of Wakanda knees Just speaking of Wakanda and now he's gonna open his eyes is gonna be in this new world ready To take my soul to you Oh my god, it begins.   I was joking you fuckheads. I never watch this the accusations aren't gonna stop oh My god, this is gonna turn into a four-hour reaction for two episodes.  I want to go to this world Okay, she's my mom.  I Might cop a field did he really just they say that in Japan All right, so he's a baby now and he's sucking on titties.  Would that be the first thing you say? Well, it looks like I'm reincarnated.   I wonder what he would Google on the computer as if he doesn't have enough titties here.   The tits are gigantic. I this is this is insanity It's bigger than my future Those are insane. They better have a freesome in here and I'm not with the kids like with the with the girl Lillia It's a rabbit Hawk or a Rebok Maho Maho.  This is his origin. All right, so he's finding his way in this new world. It ain't earth I like the OST. There's more panties in there watch More stains for him to sniff out It's a magic book we're learning how to do it The magic manual. Oh my god, I was right. Oh my god. No, I swear I never watched it Bro, this is just Gonna turn out that his parents are or magical beings and now he's a magical being and he could summon like this green magic from his End just like his eyes All right, Mishuko Tensai used you I mean Rudy Rudy you splash nice.  I gotta stop talking like this, bro. No, no, no, this is this anime It's okay to talk like this It's okay. I don't know how I'm gonna edit this for you, bro edit this on YouTube. It's gonna look like this. I'll show y'all Like this.  Look at the mommy milk. Oh, she's got a damn Let me compliment the animation because the animation is pretty solid Even though they're showing a liquid Wow This kid's already at it man trying to use my whole so he's learning how to use bubble beans So that's it.   They just show any twitch employees in here How do I even black that out? Oh, I could like that on YouTube, bro Me use my face put it over his I can't even complete these sentences man.   Oh, he actually said I choose which if you were hearing that The parents were squeezing one out in the toilet. That's what it didn't show anything. So we don't know what happened There's an uncensored version. Oh, we got to watch that bro said that to me on my Twitter DM me that I bet there's a there's a real version to I'm sorry man I missed like 80% of the dialogue so far in his anime. I still know what's going on somehow Guys learning how to use magic and his parents Fucking role-playing in the bathroom. Oh, we swing in a short wish sword. Okay Now what? That was his wife last night.   I can watch what's inside for free He's fingering them.  Let's go celebrate husband I Next level animation man. Hey look, it's it's the next main character getting off the horse. Nice Oh, he spends all night swinging the score, too All right, so Gandalf is coming.   I thought I misread that We were talking about bushy beards and then I thought I glanced at it I thought I heard this I thought I saw this and he actually said it She looks like her bush hasn't grown in yet. You remember you looked at a child and said that not number I can't even like that.  They're better be eyes on us I'll trust this kid behind both doors. Oh god. We're gonna do yours now guys if you were becoming a mage Would you want her to train you need bet don't even answer it don't don't why do I why do I get asked? What do I ask?  I mean he busted the wall through a house My mom worked hard to raise that tree. So I think she'll get mad.  Nice property damage, bro. We just busted through a house.  What are we building boats? I'll see water.      Roxy and Rudy think those are cute names that go together. I ship them Don't He's doing he doing the Subaru Purple-haired wizard comes over and knocks down trees. Nice.  If I if I was like an An anime cat kid, can I complete a sentence?  Will I end up like this?   I'm into it. I'm into this shit, bro I'm into it has me on the edge of our seat the entire time.  Why are the tish this is a lot of you could relate to this don't lol This is him. Is this him. Oh god. Is this him. Is this him before he died guilty gear? We're gonna see oh, don't please don't tell me this is him. Please don't tell me that I'll never look at him the same Rudy. Are they actually showing how we got it? Oh My god, it's him. That's his boy Oh, it's the three teenagers that they mentioned in the first episode along with him Truck who picked the wrong people man. Oh God no, I can't look at him the same anymore man. Yeah, what's going on in the background again?  What does that mean Why don't I join them oh god no no What in the name of Noah's Ark and my I'm about to witness Is she I'm watching porn it's sweat How do people really upload their reactions to YouTube whenever it's nighttime in his anime I have to like lower the volume I'm paying attention to the environment No If it's on the bucket sky gets black I have to have a heart attack No, no, I'm not pausing on it.  I Imagine saying that to a three-year-old when you're 13, maybe I'll smash oh they're definitely gonna be Dog at it.  Yeah, she pre-ordered him. Oh, he has all the man in the world. Look who he's surrounded by He's four guys She said that to a four-year-old remember that in 10 years. Maybe you could say it to me when you're 14 things change You're a man Wait, what? Oh god, he says in ptsd seven ptsd when he was a kid.  He's going and that's where he's gonna end up. He's going to magic university. Definitely He's going to school.  Oh, we're gonna find out those three high school students Are literally right here. It's the two parents Or or they're gonna be three other of the students learning magic with him the university That's why it's called master. Thank god. I mean he was master baiting at the beginning of the episode double entendre Oh god, we're back in the house. This is the house of sin Oh, thanks given nice You become an adult at 15. No, no, you don't What is this the five-star restaurant? All right, he's five now guys. He's almost an adult. He's halfway there Guys, remember when it was your fifth birthday and your dad stood up with his sword and started swinging it Remember when your dad swallowed the sword at the dinner table Someone's gonna be swallowing the sword tonight in this house Yeah, your sword's bigger than him. Thanks dad Wow, did father with with w advice Damn, he's jealous. He's jealous of his son. Where has that one been, man?   Man, I thought japan was wholesome and respectful Look, they got this motherfucker tied up to the chair left. Is it a boss like a pig?   That's a cool dynamic, bro.  That was this show is cool, man Close your eyes.  We're gonna find out one of the high school kids that died by truck It might knock some trees down.  Look at this this little 360 shot right here. Okay camera, man Wait, is she finally wearing pants?      Jesus Christ.  Of course. He has got to your powers That was a congratulations. Wow. No one ever congratulated me like that Bye Roxy. We'll see you in the end of this season when we need your help Does he look like a Paul? Damn, you taught him a lot. No, bro. Look at him now. You can summon the hurricane Katrina I swear her hair color changes every time I see her, bro Now it looks but now now it looks um dark blue. Is he going to the university to learn more? Nani does not this guy don't leave. I bet people cried at this part That's as wholesome as you're gonna get without with a night scene in this anime.   Why why do we transition to this? Had it like like I'm like people are crying in my chat right now.  Thank you. I'm gonna keep her panties That's the end of the episode. Is that how we end the episodes in Mushuko Tensai?   What's wrong with y'all? I'm not gonna lie, man I pretty I like it. It's easy to get into It's easy to understand You know, it's it. I think it's fun for me to watch. I think now I know why people want me to watch it This is like the perfect anime for me. Y'all know how I am I'm telling you, bro If Mushuko Tensai ever gets beat to 3000 viewers or no, no, no when I upload this video to youtube My first reaction to Mushuko Tensai if that reaches 100 000 views I will watch redo of healer because apparently redo of healer is something people want me to watch now Clip that shit, bro. I mean it. I mean it patreon only. I think it might have to be patreon only man. I don't know


I'm going to talk a little bit about the road ahead for OpenShift and some of the stuff I'm going to go through quickly because I've talked about it, I've gotten the opportunity to talk about it in the panel and a few people have talked about some of it already. So we really talk a lot about OKD today, I tried really to reiterate this, but it is, this is how we deliver OpenShift, we build it from that open source upstream project and we push it out into there.  It's a great source of information and so it's official, you've all been blessed and I've said OKD many, many times and over beer you'll all say OKD with me and we'll have a toast and I'll think oh they're all listening and agreeing with me. OpenShift in the marketplace and where OpenShift is right now I think we can say that the industry has really standardized on Kubernetes and we've seen it, the growing groups of people if you go to cncf.io and look at the membership there and the people who are part and parcel of the community, I don't think there's anyone who's going to disagree with me around that. Where we are and you know depending on which adoption lifecycle, whether you're looking at the Gartner one and in the hype cycle we might be not quite in the trough of disillusionment yet that we're still in that excited period early but we're still, we're really seeing that it's now being uptake by the pragmatists, hopefully the conservative folks and we're even seeing in the banking and finance industry some of those folks are really taking Kubernetes on and OpenShift as well. So what we've really tried to express today is that OpenShift now is the Kubernetes platform for your big ideas. It really has matured from a platform as a service and containers as a service and it's really taken that multi-cloud thing. But it's really, we used to joke about HTML in the early days, I did mention that I worked on some of that and I'm older than Dirt and XML. But we always, when we had HTML around, we always used to say we'll be really happy when nobody cares about what HTML is and slowly that happened and slowly Kubernetes will become just part and parcel of your infrastructure and it won't be anything. And so we're seeing that happen and coming and I look forward to the day where I'm not explaining Kubernetes anymore. But all of you and you've heard some of the stories here have different starting points. Some of the folks today were running OpenShift on OpenStack. Some people are all about the microservices and cloud native stuff and you come to it for different reasons and different starting points and I think that's what makes your stories interesting is that no two of you are completely the same but there is a common thread through them all around going cloud native and using containers and taking that new cultural shift and making that effective for you all. And it's not just one specific industry or one set of groups of people, it's lots of people. So one thing you should never feel is that you're alone in this. The big news this year really has been the OpenShift's CoreOS integration and I hope you all are aware that this happened because it happened in January, it was a big wonderful acquisition and the CoreOS folks have been really amazing people to work with and collaborate with and they've brought some really interesting innovations to bring into the team and one of the, you know, we talked a little bit about it. I just wanted, nobody really mentioned this but as we've, people have heard of Atomic and Container Linux, those two things are being brought together and that's what will be CoreOS and will be our minimal Linux distribution. We didn't talk a lot about Red Hat Quay but there are, as I always say, wonderful OpenShift Commons briefings on Quay, the container registry. That was a case of the big fish eating the next fish eating the smaller fish, the CoreOS acquired Quay, so in the acquisition of CoreOS Red Hat Got Quay it's a wonderful platform for hosting container registries and scanning them and it's very full blown and then this new thing that we call operators and I really, I think that for me is the next game changer for automating all of the infrastructure. And there's, we've had a couple of slides about this. You can come, I really highly encourage you if you are thinking about operators or wanting to use one or if there's one that's missing, please let us know or come to the operator SIG. You can find it on commons.openshift.org under the interest and just click through and you'll find it. There's lots of ISVs that are working with us to get their operators certified on REL but there's also lots of community ones. If you go to the operators repo you can find this thing called awesome operators and there's a list of about 50 to 60 community operators that are out there already and we'll be moving some of that onto the landing page for the operators SIG shortly. So there's, you know, there's lots of things coming together and some of the stuff from Tectonic that's getting integrated in the next and the coming releases. Merrick who has had to leave us a little early today unfortunately covered a lot of some of the new features that are in 3.10. There are some great briefings that I again on 3.10 and there'll be some upcoming with the next release. We'll have an OpenShift Commons briefing from the product managers on 3.11. If you're all trying to take pictures of this and the fine print is too small don't worry I'll post the link to the slides and to their roadmap stuff but there's a lot of synergies between what the CoreOS folks were doing and where we wanted to go. So this has become a really wonderful relationship and it's been great. But when we have to ask have we really crossed the chasm and I think today from what everybody has shared with you I think we know that containers in production are real and they're real and people are doing these things real on Red Hat today. So in some ways we have definitively crossed the chasm. In other ways there are a lot of people that we need to bring along with us in the community and to help learn from the lessons and the war stories and the things that you did and so thank you to the folks today that have shared from Elisa and from that other company whose name I'm not going to try and pronounce but from Arrow's team. Thank you very much for sharing your stories. There's still a lot of people who are working on this. There's a lot of dynamics in this landscape. There's people who still are who are doing it themselves. There's still some traditional pauses out there or pauses depending on what your accent is. There's a number of startups. We're not going to say that OpenShift is the end-all answer to everybody's solution but we are all going to work together on lots of different platforms to help solve these problems for you and to roll them out and incorporate the lessons and the things we learn. We saw today Tony talking about the wonderful things that Microsoft and Red Hat are doing together. There's lots more to come. If you come to KubeCon North America there'll be even more because it's downtown Seattle so I'm sure the Microsoft and Red Hat team will be there in force. People like Red Hat and IBM have been doing a lot of stuff and a lot of great partnering is going on so there's tons of information out there. If you're looking for stuff like WebSphere and DB2 or MQ, reach out. We can connect you with the people at IBM as well and get them moving. I started the whole day with this architecture slide with the four Cs. I think really what we've proven today with your participation and with the feedback that we've gotten that it really is the four Cs plus community that are really making the difference for OpenShift and for Kubernetes and for all of you and so we're really pleased that you've joined us here today. I know there's beer out there but I'm going to ask you one more time and remind you one more time to join OpenShift Commons so that you can share your stories and learn from other folks. Please do. And now another word about the beer. The beer should be out there. It should be... You have to first register to the Commons. No, well, you know, I'd like to force you to do that but I'm not in sales, all right? I'm in community and it's open community but it's really wonderful. The other thing that I was going to say about OpenShift Commons that's different than other open source communities is that we really ask you not to be anonymous. One of the things that's really helped us is that everyone who signs up, signs up using their organizational name or their corporate sponsor's name or the company that they work for's name in their email and in their Slack profiles. So everybody knows who you're from. So if you have an agenda or you have something... So it's kind of interesting because GitHub is really anonymous. Most everybody, including myself, signed up for GitHub with their Gmail account or some of you with Hotmail or if you still have that or something like that. But the Commons is really about self-identifying in a very positive way. We know when we're talking to someone who's a vendor, we know when we're talking to someone who has an agenda or a point of view but as long as you're open about it and honest about where you're coming from, it makes the conversation a whole lot richer and it's also easier to go and find somebody who knows about a domain if you know where they're working or you've heard a story from them. So now you know how to track down the people from Elyssa easily. So you can go into Slack and find them. If you'd like to join the Slack, let me know and I will sign you up for that today too. I want to just one more time thank all of our sponsors without Arrow and Microsoft and New Relic, this would not have happened today. And it really makes a huge difference to have participation from these Commons members. If you are ever on the road somewhere and you want to get connected with someone, let us know. We'll definitely make sure that happens because it is really all about the peer-to-peer network. Even more than it is about code contribution, it's about connecting you to your peers and that's what OpenShift Commons is all about. So I invite you to come and have a beer with your peers and with the Red Haters who are here and all of you who did not ask a question during the Q&A because you have that thing going on in Finland. Please ask those questions at the booth and thank our sponsors for us. So thank you very much.


Our first talk today is called Der Drei und Dreisig Jahre-Rückblick and it will be quite meta as it will backtrack through the titles and abstracts from 1984 to today, analyze apparent patterns and turning points in the subject. To do so, we have Maxi Gas, who has a PhD for Masters Degrees and through Bachelor Degrees. Hello, welcome to the translation channel of this conference on the 33rd Jahre-Rückblick or Jahre-Rückblick, so carried out by Corféry, hello, and Ron Feist, your translator for this presentation. As the French translation is in beta, we will ask you to share with us your remarks on the translation on the Twitter account hashtag C3T or by email hello at c3lingo.org. Thank you. We started a couple of weeks ago and it's a project we started a few years ago to look at how the relationship of technology and politics was like to look at the relationship of politics in relation to the Congress. It's a kind of meta talk. Why were we interested in this question? It's of course because there is never a debate within the Congress, with the techie-hardcore, what kind of politics should be presented to the Congress, what is the interesting technical content that should be presented. And at the same time, these are scientific and social questions that are important between the relationship between society and politics. So what we did is that we came back to the beginning and we looked at the titles of all the sessions and we tried to categorize them and show you that. And so we had to look at various archives and we worked on a lot of archives and we would like to share with you a video. That was screened in 1986, documenting the second Congress of 1986. Chaos-communications-Congress 1985 in Hamburg. The entry is 20 euros for the members, 30 euros for the others and 100 for the companies. It didn't scare anyone. The controls were very frequent because the enemies were numerous and the control was called GILP. Here, the phones are managed, it was a bit like the exchange of data and communication. The hacker movements are there to inform you and produce a lot of written content. They understand the technology, the structure of the database and the structure of the data. Here, you have the right to hack, quite legally. The hacker needs a computer, a phone and a connection between the two. You can start with an acoustic coupler or a modem. From this moment on, you can start to move data. Of course, the owners of computers don't necessarily like when other people walk on their devices, such as protection by password or secret numbers. This is also one of the main subjects of the Congress, security. Almost all conferences took place at another time than the planned time. We are not like announced five hackers coming from a few countries before. We are a little bit more. When we want to exchange ideas, ideas are important. Beautiful phrases like this, we would like to hear them at the UN or at a parliamentary meeting. I don't see why it changes. Could there be a way to make the whole population move? A nice utopia. So we had a vision of a club founder. So here is a cloud of words from the terms that we saw in the description of the talks. You can see that most of them are technical terms, but a lot of them are still in a more political or more romantic way. We can see that there is this word that we find in the talks on political techniques, the term of Gauchemar, which is on the top left. And what we looked at, what we wanted to see, was in the end of the years, how these technical terms and policies were developed, and what it can teach us about the universe of the Chaos Computer Club and the European hacking scene. And another question was how this evolution was linked to deeper societal transformations. For example, what was the impact on these words and on this tendency of the fall of the Berlin Wall? So we chose an example quite evident and important in our search for the word key. It was the word key NSA. So you might not be able to read the years, but we can see that we talked in 2004 and 2005, and then not at all until 2013. And from a point of view of what I perceived, I thought we would have talked about it. In 2013, everyone said, I told you, we talked about it for a long time. And when you look at the topics of the conference, you don't see that at all. And as Maxi Gasladi said, what we want to do here is to talk about the people and the goals that we had. And we were still interested in finding other proofs that it might not be visible in the presentation of the congress, but that we talked about it elsewhere. So where do we get the data we have? Before 1992, it was the most difficult. We tried the Congress Archive on the CCC website, but it's no longer available now. Fortunately, the Web Archive had a copy. Another source was the Dattenschleuder archive, which unfortunately is no longer available, but we found some PDFs scanned that we had copied by hand. So for example, this is the Dattenschleuder from 1984. There was an agenda more or less complete of the first congress. So that was pretty easy to copy. And there were others that said, bring your identity. And this one from 1991 was more difficult to read, but still possible. Of course, there is no longer a summary of the conferences, so it wasn't necessarily easy to guess or understand what the conferences were talking about.  We couldn't find any fair plans or planning or presentation lists. And so what we did here is that we read this summary and tried to understand what the conferences were. Was it a conference, a workshop, what people were talking about, what subjects we were talking about. And we tried to build the fair plan from that. So after 1992, there was already the World Wide Web, the web. And the fair plans, the agenda of the congress were generally published on the web in HTML. And so we were able to write scripts to analyze these plans. We keep in mind that no regular expression was born and injured during the implementation of this work. So the first plans were in Ascii Art, with ready-made bales in the HTML. From 2002, we had programs that were read by the machines in AICAL or in XML. So that's the most structured data that we could find. These planning has other problems than what we found before. Encoding problems. In some years, there was no complete summary of the presentations. So that was other problems that we still had to solve for our analysis. All we used to generate our dataset. And the datasets we generated are available on this Git depot. And we hope to be able to quickly put them available on Open Science Framework or other projects that allow us to access them more easily. As we said, of course, we tried to discern what should be considered technical, what should be considered political. And we had to introduce other categories to take into account the other abstract types, more controversial. So we looked at 2300 presentations in CSV efficiency, and we asked three people to categorize them. And we would like to say thank you to Fumiko who helped us a lot to work on all these talks. So we didn't use the categories that are used by the conference tracks. Already because the categories have changed over the years. But also because these categories are not necessarily a reflection of the question that we wanted to ask you. So of course the most difficult part of this debate will be how we define technology and politics. We just assumed that everything that comes into the Congress has something to do with that. We are part of the principle that about everything that happens in Congress has something to do with technology. Well, it is not just about, for example, the technologies of certain legislation. The question was, does there have a social impact? Not necessarily just the technical aspects of a particular law. But how does this law impact society? For which group of people? Is it good or bad? So we had presentations where we didn't have to summarize. For example, there was this one called THC++. We don't know what it was about. We have our hypotheses, but we can't say for sure if it was technical or political. There are also non-presentations like the Hacker Joe Parley, DJ sets, music, theater, that we also excluded from our political and technical dichotomy. And then there were also presentations that were a little controversial. And that illustrates the fact that the distinction between political and technical is not necessarily easy in Congress. For example, this presentation on the objects under the form of software, revolution, and when we look at the presentation, it looks technical, but when we read the summary, we see that this technique speaks of how the objects are made with CNC machines, 3D machines, etc. And so we can say from there that this presentation with a political or societal approach. So we have preliminary results. Of course, it was done from the tagging that we had on one dataset. And to have more information, we joined the datasets together. We found things that were coherent. We found, for example, that presentations are about 50-50, a little more technical. If we look at our first datasets, it's a little more technical, but it's almost 50-50 between technical and political.  For example, in 2007, we can see that the number of presentations decreased. And that wasn't because we had changed places. The number of participants didn't change either. We don't really know where it comes from. If you know, please let us know. If we keep it here, that's all the presentation over the years. In 1987-1988, we didn't find any information at all. No comments, no planning. And we also found things in the data. More participants don't necessarily want to say more talks, more presentations. In 1989, we saw that there was, for the first time, less technical and political talks. What we see in this graph. So we see here the technical curve that goes under the political curve. So there could be an adaptation to that when we go to merge the tags. And we see that today the political talks are going up. So the blue are the technical talks and the green are the political talks. So we're going to show you how we decided to proceed. So we're asking you to help us, maybe improve the code. Or to be willing to categorize the talks. You can put a request for just a few talks. Or you can sit down and spend about 12 hours watching all the talks and analyze everything. You can also re-write and re-structure the code or the database. In the United States, we also have one of the biggest conferences on hacking. And it would be interesting to know how they proceed there. At some point, there was an official congress paper published in 1989. There is also mentions of an electronic newspaper that was circulated. So references to Legendary Chaos Archive in 1991. Discuss these questions and to continue the discussion. And to continue this discussion in a talk tomorrow at 4 pm. In the A2 room, you can come to discuss with us about all these points. As I said, we have to see how the three categorized datasets can be merged. Then you can complete the datasets and clean the code.  It was really just a first step to find a simple category. We would like to spend more time to really qualify and quantify the data. So we would like to create groups to focus on subjects and to use statistics to start the discussions. On the ideas about technology that are circulated inside the congress or how these two categories are. How these two categories are linked to each other as well. Thank you very much. You can see our text here. You can see our email address here and our coordinates. And the slides are also available on our website. You can see the link here. I would like to ask the audience who attended our congress in the 1980s. There are some people here who raise their hands. I really hope that some of you can join our workshop tomorrow. Because we really don't have much evidence of these conferences written. Thank you for the questions. So you can go to the microphones. Yes, thank you very much for this very interesting talk. My question is that you didn't want to use the categories that the congress uses, the categories of the fair plan. That's good, but I would be interested to know how these categories have evolved over time. Do you have any observations on this? No, we didn't look at this side. But what I can say is that there were potentially a lot of technical discussions which in the end talked about social implications, or offered a campaign, or talked about a conflict between social groups. And for example, if a conference is on the security of the fair plan, it will automatically be classified as a technical talk. And on the contrary, we saw talks on the political track of the fair plan and which were actually animated by researchers in security. And if, for example, it is a presentation that simply gives a review of the law that is in place on a given subject, without any discussion of the impact that this law has on freedoms, private life, for example, for the population. In this case, we, for example, categorized them as technical. Thank you very much. The statistic between 2004 and 2007, in relation to the number of workshops that decreased, I would like to emphasize that it was due to the number of rooms that were available to deliver the workshops.


This is Conrad Nagel inviting you to stay tuned for the next half hour for one of radio's outstanding dramatic productions on Proudly We Hail Proudly We Hail Now another Proudly We Hail one of radio's outstanding dramatic half hours transcribe coast to coast in cooperation with this station and presented by your army and your Air Force From Radio City, New York here is your host and star on Proudly We Hail the distinguished star of the theater screen radio and television Conrad Nagel Thank you, Kenneth Banghardt. Hello everyone. Welcome again to Proudly We Hail Conrad I believe you said this story has a surprise ending that it has Ken and it's an intriguing story to boot Our play is entitled the trial of Gregory Winslow And our first act curtain will rise after this very important message Air Force enlistments have been restricted for a long time, but they're open again now Go to your nearest United States Army and United States Air Force recruiting station and enlist in the United States Air Force today And now with your star Conrad Nagel in the role of Gregory Winslow Your army and your Air Force present the Proudly We Hail production the trial of Gregory Winslow Gregory Winslow was one of the most brilliant lawyers that ever stood before a jury Had he turned his talents to acting there's no doubt he would have ranked among the theater greats of his time But Winslow chose the courtroom for his stage The judge the jury the spectators his audience because of his skill Gregory Winslow was a wealthy and envied man However, he was not a well-liked man whether he acted in the interest of the defense or the prosecution But two urges drove him the desire for wealth and the desire to win regardless of the tactics used Each fed upon the other and fill Gregory Winslow with a hunger he could never seem to satisfy Put her in the courtroom order I say if I hear another outbreak such as this I'll have the court cleared You may proceed mr. Winslow. Thank you your honor I have little else to add to my summation I'm ready to leave the whole thing in your hands ladies and gentlemen of the jury Is she guilty or is she not? I say she is I think I have proved that though she may sit there before you looking crushed and defeated I am convinced that in the cold viciousness of her heart. She feels no pity no remorse for what she's done I say it is we who should feel pity for her Well enough of this My case stands now it's for you to decide Thank you I Suppose I should congratulate you not necessary another brilliant case with a great mr. Winslow What's the matter ruin? Aren't you good loser? You don't care that she wasn't guilty. Do you was your job to prove? Don't come crying to me because you couldn't do it. Jury found her guilty You know you took from that woman the only thing in this world. She really cares about you were making me weep It's the first time I've hit anyone since I was a kid in school I'm sorry.   Winslow Here's your money You'll find that I've added a bit to the original sum What you did is worth it. Well, it's nice of you, mr. I'd always like to please you you're magnificent. I'd heard you were good but never dreamed that good You know you nearly had me believing you If I'd really been good, I'd have had you believing it. I Something the matter mr. Winslow No, no, I guess not I Yeah, it's got a little dizzy for a second. I'd be all right. Let me get you a drink. Yes. That might help funny. I Never felt like this before some you ate probably Yes, yes, that must be it Mr. Winslow, mr. Winslow, what is it? Yes, you may roll him in. Yes, doctor Will you tell dr. Fryberg we're running? Well, where am I? What what what's the matter?  Winslow just keep calm But but what happened? I I don't understand. We're going to operate on you mr. Winslow You're here in the hospital. Hey The hospital That doesn't make sense. Where's hunt where just relax and breathe deeply Uh try counting to 10. Oh, no, but I count to 10 mr. Winslow one two three So wait a minute what goes on here? What's the idea?  Mr. Gregory Winslow, isn't it? Yes, that's right, but I want mr. Winslow You have been brought before this court on a very serious charge. I have Are you choking? What court is this anyway? Mr. Winslow? I'll have to ask you to remain silent until I've finished. I have no desire to hold you in contempt You have been accused mr. Winslow of one of the gravest crimes known to mankind I What crime the crime of inhumanity? How do you plead mr. Winslow guilty? Or not guilty.  I beg your pardon your honor, but In all my years of practicing law. I've never heard of anything like this. Is this a joke? This is no joke, mr. Winslow You may not have heard of such a crime However here in this court You are to be tried on the charge of inhumanity How do you plead sir? Well? Well, I I'm not guilty of course the defendant pleads not guilty to the charge I think we are ready to proceed You may sit down mr. Winslow I assume being a lawyer you will wish to plead your own case. I yeah. Yes. Yes, that's right your honor Um May I ask what court this is? This is the court of every man mr. Winslow Will the prosecution proceed Your honor We have found there are 62 witnesses for the prosecution However to save the court's time We've narrowed this number down to four For these four witnesses and one other we shall prove to the court satisfaction But the defendant Gregory Winslow Is guilty as charged Will miss mary rogers, please step to the stand I don't get it. I've never seen a courtroom like this There must be thousands of people out there Uh, where's the jury? They're all the jury. What? Mr. Winslow, this is the last time i'll caution you your honor If i'm to be tried on this this trumped up charge When do I get a chance to prepare my case when your turn comes mr. Winslow? You shall have all the time you need We do things a bit differently here as you shall soon have the opportunity to see Continue sir your name is Mary rogers. How long have you been here miss rogers nearly four years? Do you recognize the defendant? Yes Gregory winslow objection. I've never seen this woman before in my life objection overruled Continue Would you mind telling the court miss rogers? When it was and under what circumstances you met mr. Winslow It was nearly four years ago. I came to his office Well sit down miss miss rogers. Is that it? Yes Thank you. No, how can I be of service? Well, my brother is This frank rogers. There there miss rogers calm yourself Frank rogers Oh, you you want me to defend it.  No, I know he didn't do you have any proof? No, but but I just know how much can you pay miss rogers I have a little money saved up and I can borrow some It's not very much. I don't work for love, you know It's not an easy thing to defend a man accused of murder, especially when it seems like such an open and shut cage I know but you Oh, mr. Winslow You you must take the case. Please miss rogers. No tears. Say them to the courtroom How much can you pay right now about about five hundred dollars five hundred? My dear young lady I'm afraid you've come to the wrong office. I know it's not much to you, but You have so much. Please couldn't you find it in your heart to do this? I might find it in my heart miss rogers, but certainly not in my pocket and all things i'm guided by my pocket The court will assign a good lawyer to brother and if he's innocent he'll go free He won't do it. No. No, I can't do it. I can't afford it If I did this once then everyone with a cross to bear would be flocking in here to see me now, excuse me I'm an appointment Then what did you do miss rogers? I went back to the prison and saw frank. I told him He was very despondent. Anyway, he didn't seem to care anymore Later they they tried him and he was convicted to serve a life sentence. I couldn't stand it I came here Thank you miss rogers your witness Miss uh Miss rogers. I'm sorry. I didn't remember when I first saw you. I see so many people Um, miss rogers. Did anyone ever prove your brother was innocent objection? Frank rogers is not on trial here, honor I'm merely trying to point out that I can in no way be judged for not taking a case that was doubtful to begin with My doubts were verified later by 12 good men and true mr. Winslow You are accused of inhumanity If you can question the witness to prove otherwise do so If not, I'll ask the prosecution to proceed but your honor. What is inhuman about refusing a case that is for the court to decide miss rogers Did you feel it was inhuman of me not to accept your case?  I don't think it would have hurt so much But you were cruel and cold and utterly heartless You were more interested in your pocket I can't answer your second question I think I would have done what I could to help I should like to call my next witness Henry tyler, Henry tyler, Henry tyler What did I made him I wish I could figure this thing out. I don't like it seems more like a dream a nightmare. What is your name? Henry tyler, how long have you been here? Three years. Are you recognized the defendant? Yes, sir He's right over there. Would you mind telling the court when it was and under what circumstances you met the defendant? It was a little more than three years ago It was about my property This is my property mr. Winslow and they're trying to take it away from me. Yes, I see You realize such a case will be quite expensive. My fee is low, mr. tyler And I I figured that I I've got some bonds some life insurance I can cash in on Would five thousand dollars cover it? No, no, I'm afraid it wouldn't Not in a case of this sort I'll just have to get another lawyer. Yes, guess you will. I shouldn't think you'd have too much trouble though You're not really interested in helping out folks. Are you of course? I am mr. tyler The right folks What happened after that mr. tyler? The case went to court I lost They took my house everything I had Soon after that I came here. Who was the lawyer who argued the case against your claim? He was Gregory Winslow That will do your witness Mr tyler Was there anything inhuman against my not taking your case? No Not on the face of it. Was there anything inhuman then in my representing the client who opposed you? No, I guess there wasn't But you knew it was my property and you nothing of the sort In fact, I proved contrary your honor as long as this question is arisen I should like to point out that the prosecution was about to prove That the defendant deliberately approached the client he represented because he knew the client could pay well If mr. Winslow would like me to bring witnesses to prove this point I'll be glad to Do you deny that mr. Winslow? No No, I don't deny it Well, is there anything wrong in trying to earn a living? The court will now recess We shall Conrad Nagel starring in the role of Gregory Winslow in the proudly we hail production The trial of Gregory Winslow will return in just a moment for the second act I have a message for the young men of america Enlist in the united states air force by doing this right now when the air force is expanding You have the opportunity to really get ahead The air force needs specialists in radar radio weather aircraft maintenance and numerous other technical fields Yes, the air force can train you for one of its many technical jobs Go to the nearest army and air force recruiting station. Have a talk with the recruiting sergeant Find out for yourself the advantages you can gain by enlisting in the air force now You are listening to proudly we hail and now with your star conrad nagel in the title role We present the second act of the trial of Gregory Winslow Court will come to order prosecution may proceed. I should like to call for my next witness Alice graham Alice graham How long have you been here? A little over two years. Do you recognize the defendant? I do Would you tell the court where and under what circumstances you met? It was a little over two years ago Well miss graham Aren't you in the wrong office?   Listen, mr. Winslow If there's one thing in this world that means anything to me, it's my baby if you take him away from me Well, Mrs. Graham your husband retained me He wants the child and it's my job to see that that's just what he gets. I know that And that's why I came here to to see if there was anything that would make you drop the case If I've committed a crime it was to marry the wrong man.  Yes, but what can he do against you? I'm flat. Oh, stop it How much money will you take for you to drop the case? Very unethical, you know Your husband is paying me 50,000. I have about one quarter of that. Well, that's too bad. I'd really like to help you You won't drop the case under the circumstances No, and you'll go into that court tomorrow and prove that I'm an An evil woman when you know perfectly well that I'm not I'll go into court tomorrow to win for my client That's all. No, that's not all you'll win and he'll get my baby and you'll kill me Come now after all perhaps some arrangement can be made so that you can visit the child once in a while There's nothing to make you change your mind. No, no, I'm afraid not miss graham. I see you in court What happened there for that mrs. Graham? He won the case for my husband. I lost my child I had a weak heart. The strain was too much. I didn't care anyway I came here Your witness, uh, mrs. Graham What do you mean when you say You came here. Well, don't you know I mean that I'm just That has nothing to do with the case objection sustain Continue mr. Winslow. I Oh, I I have no more questions For my next witness, I'd like to call john merlin John merlin I've never heard that name before. I know it Look, maybe I'm going crazy, but But am I dead your name is john merlin? That's right. How long have you been here? Not quite a year. Do you know the defendant? No, I don't. Would you tell the court how you got here? I was a teller in the first national There was a holder A man named filth kramer shot me Would you care to ask the witness any questions mr. Winslow? Why? Uh No, very well Step down mr. Merlin My final witness is the defendant himself mr. Gregory winslow Me But that's not that will you please take the stand Your name? Well, don't I get sworn in? That's not necessary in this court. Oh My name is Gregory winslow. You've not been here before before No, no, not that I know I've did you recognize mr. Merlin. He told you he didn't know me I don't know him, but you did recognize the name philip kramer, didn't you? Yes Yes, it was one of my biggest cases. I defended it and the jury found him not guilty of the charge Which I believe was murder mr. Winslow was philip kramer guilty as charged Jury didn't think so that does not answer my question I refuse to answer it very well since you refused He will show the court the answer This scene took place in mr. Winslow's home On the night Who's there you winslow what the devil do you mean breaking into a man's house in the middle of the night I want to hire My office hours are not from midnight till four.  What's the charge? Murder anybody see you do it? No, I don't think so but they'll pick me up on it. It's a long story. You want to hear it? For a hundred grand I could be persuaded. You don't come cheap, do you not to get a man off for murder? I don't Would the prosecution please tell the court what this scene has to do with the witness john murland? Yes your honor Because gregory winslow was able to convince the court that philip kramer was innocent He was set free A month later john murland was shot and killed by the same kramer Had winslow refused to take his case and turn the moment of the police This never would have happened then Then I am dead There is no need here to dwell on a long summation I think the evidence speaks for itself Gregory winslow a brilliant and gifted man Use this talents not for good But for evil He had no love for his fellow man. No desire to help anyone Although it is true. Mr. Winslow defended many innocent people It was always done for a price And not for an honest desire to see justice done As he himself said he was more interested in his pocket than his heart An empty pocket And an empty heart I asked the court to bring in a verdict of guilty I asked for the maximum penalty Thank you. Mr. Winslow Do you care to say anything? Yes Yes, I would your honor People of the court I should first like to change my plea from not guilty To guilty Yes Yes, I am guilty as charged Guilty of all you say It's a shocking and terrible thing to see the scenes of your crimes passed before you When you'd all but forgotten them I have no excuse for the things I did I was driven by an urge that was evil And I was too weak to overcome it I can call no witness in my defense for there are none I do have a plea however I don't know what your sentence will mean to me but But I think I can guess Whatever it is There'll not be another chance to do any good for my fellow man I know now that that I had many chances and destroyed them So I'm asking the court for another Let me go back Let me go back And in the time I have left I shall work as I never have before For the benefit of mankind I know I can't undo what I've done But there will be many I can help If if you refuse to let me return I'm lost forever And what I could do And never did do Will be lost too I I That's all I have to say your honor Mr. Winslow will you please face the court As the court reached a verdict they have your honor How do you find the defendant? Well doctor that was a close one wasn't it I thought we were going to lose mr. Winslow It's tougher than he appears Strange how these things work You do everything you can And it looks like it's not going to be enough And then somehow for some reason it is enough It's beyond me for my skill The star conrad negal will return in just a moment with a word about next week's show You air force veterans listening to our show doesn't all the noise these planes you hear in the background make you a little bit homesick Well, if it does here's some good news for you For you veterans with experience and special training are needed now You could enlist with your old grade or better skip basic training and be assigned initially to a nearby air force base And this deal holds good for veterans of other branches of the service too If they've had the kind of special training the air force needs If you've had training and experience in such fields as radio radar maintenance weather armament photography and many others You can build a fine future in our fast growing air force But why not get all the facts just stop at your nearest united states army and united states air force recruiting station And find out where you are needed in the world's greatest air force Enlist now Presented transcribed in cooperation with this station by the united states army and the united states air force recruiting service Proudly we hail stars conrad negal the trial of gregarry windslow was written by duit cop The music was composed and conducted by john guanieri This program was produced under the supervision of charles and rogers productions and directed by charles wilkes This is kenneth banghardt speaking and here again is your host and star Conrad negal well friends. We hope you'll join us next week again on proudly We hail for a thrilling adventure of the french foreign legion We will meet the besieged garrison at fort buah dell in the french moroccan desert until then Goodbye