Okay. Thanks everyone for joining us.  I'm Libby Schultz and I'll be moderating today's webinar. I'm going to read our code of conduct and then hand over to Michael Cade, Field CTO, and Mark Lobby, Senior Cloud Product Manager both with cast and by Veeam. Mark, I hope I didn't just really butcher that. No, you're good. Thank you. Okay. A few housekeeping items before we get started. During the webinar, you are not able to speak as an attendee, but there is our chat box. Feel free to drop your questions in there. Say hi to us and where you are listening from. Just leave your questions here. We'll get to as many as we can throughout and at the end. This is an official webinar of the CNCF and as such, is subject to the CNCF code of conduct. Please do not add anything to the chat or questions that would be in violation of that code of conduct. Please be respectful of all of your fellow participants and presenters. Please also note that the recording will be available later today, as well as the slides on the CNCF Online Programs page at community.cncf.io under Online Programs. They're also available via your registration link, and the recording will be on our Online Programs YouTube playlist on the CNCF channel later today as well. With that, I will hand things over to Michael and Mark. Take it away. Awesome.  Great. Thank you, Libby. Thank you, Michael. Hi, everybody. I'm Mark Lavey, and I'm the Principal Cloud Manager at Castin. Now Castin is a business unit of Veeam. So you will see us say Castin by Veeam. And certainly we have commercial products, but we've been long involved in the community of Kubernetes with engineering efforts in the CNCF and et cetera. And so we'll be focusing our open source project, which will just be joining the CNCF as a sandbox project canister today. I'm responsible for working with our communities and our external resources and our upstream and downstream projects. Over to you, Michael. Yeah, cheers, Mark. And hey, everyone. Yeah, so I've been at Veeam software for just over eight and a half years now. So my full focus is around data protection of all the different platforms that we know and love. So whether it be physical, virtual, cloud, cloud native, if there's data in it, then we generally probably need to be protecting it. And, but over the last two, three years, it's been a huge focus around the cloud and cloud native environments, workloads, platforms, et cetera. So what we kind of want to get to today is talking about canister and giving a refresh off of where we are from a canister perspective, but also some community project that I created as part of a hackathon, but really it's about visualizing the status quo of canister with inside your cluster. So with that, I think we can, I can pass it back over to Mark for the first few slides, at least, I think. Great, Michael, you'll be my virtual clicker. All right, so we've already gotten the introductions aside. So our goal today is to talk about data protection on Kubernetes. We'll talk about the problem space that canister addresses and also give you some updates on how the project is progressing. We'll certainly demonstrate this and we'll show you exactly how to visualize the blueprints which are kind of our artifacts of operations and orchestration with the blueprint visualizer that Michael has created. We'll wrap up with some references to all of the points that we've made and ask you to join our project and conclude with any Q and A if we don't address it along the way. So let's get started. Michael, why don't you address this? Yeah, so this was a slide that we put together based on the whole stateless versus stateful conversation that we've had for a long time within the community. And this is what I always go back to in terms of if we think about the Kubernetes from a release point of view, we have three releases a year and generally speaking over the last three, four, five years we've had something relative to storage within our cluster. Now granted that might have been the CSI it might have been the entry provisioner and it might have been some things that we don't even use anymore and they've been deprecated out of our Kubernetes code. But as we get more towards today in maturity we see things like the volume snapshot going GA and even more stuff over the last few years around volume health monitoring and cloning technologies and the enhancements around the CSI the container storage interface and what we can do there. And it's no longer and I don't want to still mark thunder over the next few slides but it's no longer a is it a stateless versus stateful because really what the conversation is is in the cluster or is the state outside of the cluster because there's not many of us that are running just simply stateless workloads within our Kubernetes cluster because that website or that static website is going to be attached to some sort of storage whether it be a database or some sort of data service to hold that information. So really this is to highlight that storage in Kubernetes is a first-class citizen people are putting storage up there from a data service point of view within their cluster as well as outside as well and we'll get to that later on as well. All right, let's go to the next slide. So yes, what are those stateful workloads we see from number two on all the way downwards and this is from the data dog container report their databases for the most part there's certainly many, many, many more persistent workloads out there but databases are pretty much what we see coming on to Kubernetes clusters. Let's move on. Just one thing to add there, Mark is I basically have that conversation about especially if it's someone in the community using stateless workload or thinking that their Kubernetes cluster is stateless I have the conversation do you have any persistent volume claims in your cluster and that soon unravels to things like observability Prometheus metrics, et cetera. Well, are they important? Should we be protecting them? But ultimately we find out well, there is some state in that. And I think that's, and that's, it's okay. It's okay to run staple workloads within your Kubernetes cluster. Certainly, we have many, many cluster many, many different customers and use cases. And so we'll cover three kind of major patterns that we've seen. These dash boxes represent Kubernetes cluster with multiple pods and workloads, staple or stateless. And in the first case on the left we basically have databases and everything completely over the network off of the cluster. Second middle case here pretty much is where we have databases. Well, they're in, they're on the cluster but they're in separate pods maybe with dedicated storage or even dedicated workers and so on, right? Isolated in that regard. But really where we see development and test and really the most agile workloads and operations and coding and development practices is when the databases are co-located with and in the same pods on the same cluster as the workloads and can be deployed as a whole atomic unit. Usually this is great for development and testing. You might scale it differently for production. However, for making it a quick atomic load this is the most efficient way that almost all of our developers are evolving today. Everything on the cluster, everything declarable through Kubernetes and controllable through Kubernetes and cloud native operations including the storage and everything that's considered. So we see people very much going from off cluster to on cluster to in pod as a whole unit of deployment. Yeah, I think to add to that is it really depends the skill sets that you have and the performance required because the further right you get here will generally mean that you're gonna have your data service right next to your application which is gonna give you the most control because you're gonna have all the access to the database and the data service.  So that's the control. Now, if you've come from a virtual machine that's hosting that database then it might be easier to offload that control and administration to a PaaS based service such as Amazon RDS or another PaaS MongoDB Atlas or something along them lines and then that middle ground could be a dedicated infrastructure Kubernetes cluster alongside your application clusters and that infrastructure cluster is serving out storage to all of your individual applications that require that storage there. So three different options as to what we see out there in the wild but the big thing that we'd like you to take away is that it doesn't matter whether it's inside the cluster a dedicated infrastructure cluster or using a PaaS based system. We still need to think about protecting that workload. Data protection is key from a backup point of view. Backup is relatively boring. I've worked in it for long enough for me to be able to say that but the recovery is ultimately gonna get us out of a lot of trouble when bad things happen and I don't generally mean the topical stuff the ransomware stuff. Yes, that is a bad thing in a failure scenario but I mean we all make mistakes, generally make mistakes and that's when we tend to want to go to our recovery points. Right, and as you'll see canister can address all of these situations especially for orchestrating off of cluster concerns. So great, we've already started to address stateful is the reality and if it isn't for you it probably will be because you've been successful with Stateless today and we've seen this increasingly growing. We also see customers saying, hey, I have GitOps I don't need to take care of all this but the truth is the cluster has state you need to deal with forensics you probably need to deal with auditability and so on. Those again are persistent artifacts that we need to basically get off of the cluster because you can't prove that the deployed state actually was unless you audit it. And then yes, everybody's like, well I already have RDS I already have Azure I already have these workloads on clusters with a managed service provider Well, the truth is everybody has outages and all of the cloud providers recommend that you have disaster recovery so that means taking your data off of those workloads and those persistence and those artifacts need to come off of those clusters out of those clouds to another party and maybe come back into those clouds certainly but there needs to be an independent way no single point of failure that's basic disaster recovery 101. We'll talk a little bit more about that now but please carry on my Yeah, no, so with that myth three mark I was going to say about the public cloud I was just at AWS re-invent last week and they're very vocal about the shared responsibility model. Yes, they're going to keep the infrastructure up they're going to keep the lights on for you but that data is your data if you drop a table if you make any bad mistakes and you accidentally delete something that's your problem that's your you've made that deletion it's the shared responsibility and then from the Github's perspective is if you lose the cluster then that's great you might have all of your application in Github or some sort of source code repository but that database won't be stored in there so how do we go from version one to version two of our application? That's great. We've got that all in our source code repository but the database is the key important part and probably the most critical data that you have within that application as well. Okay, get you to this one. So yes, a lot of people then say at CD backup is my way of backing up a cluster certainly that's the right way and we want to basically bust this myth. I believe that yes, at CD backup is a requirement for most everybody however it is not a disaster recovery solution for restoring the state of your applications because of the persistence that we've already mentioned but more to the point I've never seen anybody actually restore it directly and then get what they needed because the cluster drips, the applications drips, the data on disk drips and you will not get that from at CD. So yes, at CD is part of the solution however it needs to be put in the right context and the truth is we really put it in the forensics and modability context not for backup and disaster recovery. All right, so one more thing because we have a lot of developers here bringing their applications to Kubernetes and they need to know a little bit about data protection and the three to one backup rule is the kind of ordained way to look at disaster recovery. Michael, do you want to tackle this? Yeah, I think this is fundamental and think of this as a methodology as well like it doesn't matter whether you're using canister K10 as a commercial project or any other data protection tool across any different platform. The key thing to take away is that one we need to have backup because we need to be able to recover from a certain failure scenario that we may have and it might be a dramatic one that makes the news but it equally might be one that we make we make our own mistakes and something happens. So, and this actually came from a photographer way back I don't know if you know the name Mark I can't remember that. I'm drawing a blank. I will add that reference later on. But the methodology stands the same is that if we make sure that we've got three copies of our data on two different media types and one of which is offsite and immutable I would add there it means that we have pretty much covered across any failure scenario in that if you think about the three copies of data I have my production that we're working on right now I have a backup of that in a different media type maybe that is off to object storage maybe that is a snapshot as well for really fast recovery point but then I make sure that I have one of those offsite and away from my original copy and I make sure that I'm leveraging immutable functions whether that be object like API from an S3 point of view or some sort of immutability lock on Linux or Microsoft Azure Blob Storage there's a lot of different options that we have out there from that offsite and that will protect us if something happens of production on a different to that media of the production but also to have that offsite as well which then leads us into the next piece of why, why do we need to keep this? Because if we think about that failure scenario that I mentioned whether that is the accidental deletion or the topical ransomware attack we have that failure now if we're only taking a backup every 24 hours and we have a recovery time or we would like a recovery time of X amount of minutes or hours we have to consider how much, what that, how far back we need to go because 24 hours it means that we're well if you make a mistake now you've got to go back 24 hours or to the last backup as the recovery point which then leads us onto or how long does it then take us to actually recover the workload recover the data now if that's petabytes of data it's going to take a lot longer but ultimately you've got to be aware that that gap in the middle there where how far, how long is really going to define how much data you lose but how long your cost like your business your application is actually offline so just a very easy simple diagram to say is that traditionally and I'm traditionally saying about back in the physical world we would say about backing up every day and maybe you would take the tape off site and it would live in your car foot welfare for the evening or maybe even the week and then you'd come back the next day and it would go again from an admin's point of view now that we're in the world of cloud and virtualization and other pass by services maybe we don't have to do that every 24 hours maybe we can actually get down to the minutes and maybe we can get down to the hours on some work clothes that we don't necessarily see as really important so it's about squashing that RPO RTO down the failure is going to happen whether whatever failure that may be so thinking about how far back we need to go from the last backup and how long it then is going to take to recover and where as well you have to think about that because if the failure scenario is a catastrophic one we've lost a certain site then we have to think about okay how do we build that new site how do we then recover that data from that offsite location and there are all things to be thinking about when it comes to data management Mark over to you. Sure. So let's now talk about this because if we were talking about three to one right, three snapshots and you know CSI snapshots of my persistent volumes on the cluster two of those getting off of the cluster at the very least, right? Two copies or two a second place and then one of those has to be way out of that availability zone, right? You know, just geographically so that's the way to think about three to one but now what is the backup, right? With Kubernetes we now have all of the infrastructure concerns and all of the application concerns together plus a lot more with network and storage providers in the mix of the entire stack so traditionally back in the bare metal and the VM days, you know just taking stunning the VM with a hypervisor and then take a snapshot of the disk was good enough for a crash consistent backup but with Kubernetes we can get to application consistent backup because it is not good enough to just snapshot a disk because we still have to get all of the data at rest on that disk and so that requires potentially the entire application so we have a lot of methodologies a lot of techniques and they progressively can be added together to get to whatever granularity or tool or methodology we need and sometimes it's a combination of these factors in order to get us to an application consistent backup because those databases and the website and the front end and the backend logic and all the load balancing and any other sort of stateful information needs to be persisted and needs to be at rest before we can even use say the snapshots that are built into Kubernetes for container storage initiative providers but again, if we haven't frozen everything and again, this is where Canister comes in to help us orchestrate all these concerns we can finally then take a snapshot but you may need to get a logical dump from the application because we're not dealing with one piece of data on one node, we're probably talking about a distributed database if we're doing this properly so yeah, there's no such thing as a snapshot of just one little shard of a cluster not going to work so we need to have probably logical tooling to persist all of a snapshot onto disk and then we can use system sort of tools or snapshots or a combination thereof such that we can get this all persisted to disk and then we can get a snapshot off of it we can use advanced technologies like change block tracking to make this an efficient backup so it doesn't take up a lot of time therefore decreasing our RPOs and doesn't take up a lot of storage therefore not growing our bills exorbitantly and therefore it can also be transmitted over the network effectively for two in our one right in our three two one backup rules to make sure that we have disaster recovery so there's a lot of concerns to balance Canister helps us address all of these and in conjunction and in orchestration together let's move on so yeah, as soon as some people start to address with how do I back up my persistent volumes they start scripting it and using the storage provider tools but this rapidly becomes a single point of failure in coding as well because we've targeted all of the pets or all of the single points of failure or all the single providers in a solution which in a disaster recovery situation may be on a different provider different zone, different availability different quotas, different storage providers in fact, even migrating between clusters we consider almost like a disaster recovery event so all of those challenges mean that the scripts are going to be very brittle bespoke, not well managed and not well managed and distributed like a cloud native application and all of that manageability and those enterprise needs for disaster recovery a small script will not meet the needs meet the temporary needs just to get started but rapidly we get to where the need for canister happens to change all these factors so let's move on. Cool, so let's get into we've met me and Mark have both mentioned probably canister 25 times now but we haven't told you what it is so Mark do you want to take it stab at this one first then I'll take. Sure, so in the interest of telling you what we're going to tell you and then telling you and then telling you what we've told you we've already told you that persistent workloads primarily databases but not exclusively are really here and a concern for almost all of our customers and all of our adopters of the project certainly of canister and canister allows data protection operations to be done in a completely cloud native way an extensible way to achieve application consistent backup and recovery has been an open source project since 2017 and we'll go into it but we already have example blueprints that deal with many of the community blueprints that are needed for many of the databases out there and database passes and services but we see this growing to other customers asking us like how do I deal with my new vector databases and so on is there a canister blueprint for that well we want to collaborate and we want to solve this problem in a cloud native manner for all persistent workloads from this point onwards so we're hinting at blueprints and we're about to go there next Yeah, exactly that the other thing I just always have to highlight is the ability this doesn't always have to be inside of the Kubernetes cluster so services like Amazon RDS and if you notice the innovation MongoDB Atlas and just basically any external database to the Kubernetes cluster can still be captured by a blueprint and we'll talk about what that blueprint enables us to do as well. You remember there's three kind of major patterns of deployment with stateful workloads and yes, canister accommodates all of that. Yeah, so from an execution walkthrough and I'm just going to be very brief here because I know we've covered this in the past but canister as a standalone project is a home chart deployment. Super simple, you'll see on the right hand side here that we have a Helm repo add a canister repository within Helm QCTL create namespace of canister and then a Helm install command and then you'll see that we're made up of or canister is made up of CRDs or custom resource definitions and that's what we're really going to dive into but the key part and the extensibility of canister really comes from those example blueprints or blueprints in general and you can see that we have a list of examples down on the left hand side from the GitHub site if you go to canister.io that will get you to the GitHub and then there's examples in there that you can go and use either straight out of the back or you can modify that and you should modify that towards your data service as well. So in order for us to instruct a print to go and do something so within a blueprint we have three actions we have a backup, we have a restore and we have a delete we require an action set an action set is a kind of an if this then that and it's gonna call on that blueprint to go and do something. So an action set is an instruction to what we're going to do you can kind of see it as a job however a job would be a continually orchestrated affair that happens on a scheduled basis these aren't scheduled unless you use something like a cron job and each time you're gonna be creating a new action set on that but the action set is the instruction that we're going to tell the controller to trigger and that'll be via a blueprint that we want to do. That blueprint will then use that function to QS that workload within that database service in or outside of the cluster and then we would offload that if you wished we do have some that are snapshot orientated examples as well but generally speaking to adhere to that 321 rule we would drop one out into the object storage or cloud snapshot type environment and then we report back to our action set to say that everything is good we would also use that same action set if we wanted to a restore process as well. So breaking down the blueprint as it's kind of the key part if you haven't noticed and this kind of just summarizes what Mark just touched on around consistent so crash consistent I like to talk about if you remember physical systems or maybe even your physical PC if you were to pull the power cable out maybe not so much today but definitely 20 years ago the likelihood of that coming back in a fresh clean state would be impressive it would probably come back if it was Windows it would probably come back with a blue screen of death and would have to do some sort of check disk to confirm that everything is good so crash consistent might be all we can achieve it might be just a case of going right I need a storage snapshot and bang we take that because there's no other option but we know that there's a risk that when we bring that back especially if it's transactional workloads in there it might not come back in a good state we might lose some of those orders we might lose some of that important data what we really wanna start getting to is the application consistent where we start freezing some stuff or start freezing the data service and then offloading that to a storage snapshot and then I'm freezing that data service yes there's gonna be a bit of a delay there where we're freezing but then we let things go again now that's it's a bit better than crash consistent now where we talk about database consistent that's gonna give us the ability to leverage logical dumps via something like PG dump or Mongo database or Mongo DB dump and that's gonna allow us to offload a full copy of that database in a consistent fashion off to that object storage location that's great but every time you do that to 100 gigs worth of files it's gonna be a hundred gig every single time which takes time but again that might be all we can get to or we might be looking at the full application capture and we might use a combination of tools and layers to achieve that within that so as I mentioned when Canister is deployed within our Kubernetes cluster as a Helm chart deployment we or Blueprint are seen as custom resources there's three customers there's actually four but I'm gonna talk about three three custom resources in that we've got Blueprints we've got action sets and we have profiles action sets are the instructions that I mentioned Blueprints are the how we do something and the profiles is where we're going to store that so these would be seen as YAML files but YAML manifests within our Kubernetes cluster now within the Blueprint as I mentioned as well we have three different actions we have a backup action and if you can see here and I'll try and describe what's happening is under that backup action we have a set of instructions that says this is what I want you to do when this is triggered to my Mongo database in this instance so I'm going to hit the stable set name which hits the pods within my stable set and it then connects into that uses a dump command of MongoDB it then archives that out to a profile now all of that profile and everything is already defined as part of our action set but really what we're doing here is we're instructing this container image to take a copy of that or a backup of that in a consistent state and offload that into our profile our object storage profile when it comes to our restore action so you're only triggering these every time you need them so if it's a backup action set if it's a restore action set or a delete for retention period then you're only going to be calling on these actions as and when you need them so a restore action set is if you hadn't guessed it's a reverse option or reverse operation we're going to take that copy of data that we stored in our profile and we're going to pull that back and we're going to dump that back into our or we're going to restore that into our data service so again here we're using native tools such as Mongo Restore to bring that consistent copy back into our data service which also could be used from a migration point of view we could use this from one cluster to another so we can start using that copy of data for clone purposes and then finally again quite simple is the delete action think about the delete action is probably around the retention period we could continually do these action sets on a daily basis for the next 100 years you probably don't want to keep that many so we want to start introducing a retention period deletion out of that so we could do that with the delete action as well okay anything to add there Mark did I miss anything? No, keep going Cool, so that brings me on to a little hackathon project that I created so so far the screenshots that you've seen are all CLI I do have access to a cluster that has canister installed so we can jump into there as well but one of the things that I wanted to do so command line is great, yeah if you're familiar with that I come from an operations infrastructure background and I tend to quite like UIs maybe not to the a lot of people do like CLI's but I feel like you can get a lot of you can get a lot of output from or feedback from a visualizer so as part of this hackathon it was 24 hours long I'm no developer by any stretch but when we look at the command line yes I can go through here you can see that I've got several blueprints you can see that I've got several action sets some are restores and some are backups I've got some profiles so you can see that I've got some in Azure some in GCP, some in AWS and some S3 compatible storage great stuff, now I can interact with that I can start using CanDo which is a CLI command tool for canister maybe that's for the next hackathon as well is how can I incorporate that but basically what I wanted to do is a way to visualize these resources and not so much the profiles and the blueprints they don't tend to change too much but I want to see what's on my cluster what I did want to see though was these action sets because these are what's running on a scheduled cron job basis so as you can see with that action set and I'll touch on this a bit more but I wanted a little bit more visual feedback on okay if it's good then we're all green because everyone knows green is good however if it's bad then I wanna see when it's bad so I can drill down into that and go and work out what that is and a stretch goal for this was to hover over that action set and understand a little bit more give me the QCTL describe on that action set to understand what the problem is and maybe next hackathon we'll get to that so let me just walk you through a very simple print and again forgive me I'll share a link to the GitHub repo and don't judge me too much I'm not a developer, I'm a hacker at best but I wanted a way in which we had a navigation pane to get to our canister resources so that would be our GitHub, that would be canister.io it would be our docs.canister.io as well as our Slack channel that Mark is very active in to speak to the rest of the canister community so really that was a navigation bar that I just wanted there for a quick win to get around I wanted to display my profiles and notice I used some icon graphics to distinguish what cloud they were potentially in and they're gonna give me the details of that so I can see what marries up to my object storage locations. Again, I'm gonna have my blueprints so here I have four or five blueprints that I've added and again they use some if selections in the code and then uses some icons to dictate what the workload is that that blueprint is protecting and I'll show in the demo there's a load more that I've factored into that and then finally around action sets as I mentioned I wanted that visual so I wanted to know what the status was I wanted to know what type of action set that was I wanted to know what particular namespace that was protecting so which application and I wanted to know what profile it was using so kind of marrying up that profile to what we see over on the left hand side. So with that, hopefully this will allow me to do play as soon as we see the mouse moving, yeah it's moving. Okay, so on the GitHub repo you'll see a read me this walks you through how to get started on this really there's two key ways in which we can deploy this and use this with our Achilles Custer one is we could deploy it with the ammo files that you see within the bucket, sorry within repo and the other is to run it locally either in a Docker container or using the binary locally and what this does is this will connect into the cube config or it will be deployed within your environment so basically what this read me does is give you two options as to how and where you want to deploy it. Now what I've done is I've deployed it within my Kubernetes cluster within my canister namespace it runs alongside my canister deployment as well. I feel like this is stopping. So yeah, so I've gone that you can see that we've got the manifests so what we do here is we create a deployment a role-based access control we create a service account and a service and the service is what we can gain access to. If we go to canister.vzilla.co.uk you'll see a live version of this you won't get into the cluster but there is a live version of this that you can get to. Again, if you wanted to use a Docker file you could do that as well because not everyone wants to run that binary locally. So again, I went down the route and it also does go through the canister deployment options as well. So if anyone that is just getting started that just wants to get hands-on with canister and start playing around with some examples then it also talks about how do we deploy canister using that home chart. It also talks about adding profiles into our cluster now documentation does as well but for this project I wanted to be clear and concise to the hackathon to try and win the hackathon. So as you can see, we use canctl is the CLI that I touched on earlier and these are the example blueprints that we have within the canister GitHub. I've just simplified them so that I can quickly show what that looks like as part of the UI. So if I go kubectl get pods you'll see that I have a canister visualizer pod already running. It's been running for four days as up to this demo, very simple deployment. Nothing too fancy, no persistence on this. And I also have a service which if you can copy this quick enough you can get there as well but canister.vizila.co.uk will get you there as well. So this is in an EKS cluster. And as you can see my canister visualizer and my canister deployment has nothing in as part of this demo. If you went there now you would see a different story. Obviously like all good developers I put a dark mode into my interface to get extra points. And then I also added a button over on the left-hand side that gives us an about project. Now you can read through that but ultimately it's what I'm telling you now it's a visualizer that allows us to see what that CLI is. And then it goes through these options these web links that I touched on the navigation bars but what we really wanna see is actually some profiles, some blueprints and some action sets in our cluster. So with that, if we come back into here we've also got an application that we run in here. In fact, before we do that we're gonna add our profiles we're gonna add our blueprints and we're not going to create our action set. But as you can see here just a very simple bash script so I'm not sharing any secret keys it going through it's adding your S3 profile your Azure blob, your Google storage and a couple of blueprints. And we can now go and create those action sets but we'll need that profile name. So I wanted to display that as part of that. So with that, if we refresh this page, magic and we've now got some profiles to send our backups to we've got some blueprints to associate to our workloads but we have no action sets we have nothing sending anything anywhere we have no backup plan to that. But you can see here, yeah I've got one in Azure, one in GCP just to show the agnosticity of where we can send our backups from a canister perspective. You've got blueprints for MySQL for Elasticsearch for Redis if you go and look at that example you'll see a lot of these and a lot more logos are coming later on. If we don't have the icon for that blueprint we're gonna use that top one that's why I had that in there for so if it's a bespoke blueprint that is not listed then it's just gonna use that. Now, if I wanna go and create that action set a backup of my mission to collaboration so let's just see. Okay, so I have a MySQL test obviously MySQL test is very important to me and I wanna make sure that the data is Let's see if Michael comes back. There he is. Oh, sorry. I don't know where he got that. So, I've got that MySQL test mission critical application that I want to protect and I'm saying from the namespace canister take this blueprint MySQL blueprint pointed to the staple set MySQL test MySQL release and then I'm hitting this profile probably a S3 W65QL and I'm gonna use a secret so I can get inside of that mission critical SQL environment. So I've run that and you can see, yeah, all good or in fact, it's running. Again, I wanted to show a progress bar in there. The fact is there's not enough data in here for it to really show too much. So by the time I refresh this and go and have another look, it will be done. It tells me the profile that I'm sending that to what namespace it is. I think demo me should click refresh now and we see that it's complete. Good stuff, all green. However, I'm now gonna simulate a, do I simulate a restore first or a failure? Maybe it's a restore. Okay, so let's say that I dropped some data I didn't dive into the MySQL database but in theory, it's gonna be this process. This process, we've made mistakes, mistakes were made. So we would then simply say action set, which is a type of restore now. And again, if we go into here, it shouldn't take very long. You see that we're already complete because there's really no data in there. But in theory, as a longer demo, I would go in, I would show you some important data. I would take it back up. I would then cause a problem and then restore that. So now let's create a action set that I know will fail. So I'm gonna actually call another blueprint against my MySQL database. Well, that's not gonna work because it doesn't have the capability to be able to protect that. So let's run it. And again, this was allowing me to test that that status is now red. I can visually see that so that I know that there's a problem and I can go and investigate what that is. Okay, so what else did I show? I'm sorry. I've never been so happy to see a failure. What's that, sorry? I've never been so happy to see a failure result. Yeah, and again, this comes down to me showing from a hackathon point of view that testing is important to understand that. Yeah, I've showed you that much. I've showed you the profiles. That's a good demo. We ready to move on? I wanted to stretch goal to go, right? Is when I went to that action set and it was failed, like to hover over that and say, could not render object reference, failed to render template app not found. Just something like that that would give you a pointer to be able to go and investigate what that needed to be. I think what I do is actually add a stream of blueprints, all of the examples that we have available to us into the interface, but maybe I do that very much at the end. I'm conscious of time as well. I know that we've got, no, maybe I didn't. Okay, let's not play it again. So there was one more slide around like how to get involved in that. It's on my own GitHub at the moment. I would love feedback about what to do next or if there's anything we should be doing on that and collaborating on. Yeah, and then I think over to you, Mark, for the wrap up. All right then. Okay, so Canister is a project that we started back in 2017 and open source back then and it's grown a small community and we worked with the CNCF to submit it as a sandbox project just back in June. The vote was in September. It was accepted and we're working on all of the onboarding now. We've also got a press release announcing this. This happened with KubeCon Chicago just a few weeks back and we also announced our first independent software vendor ISV support of a Canister Blueprint. That's EnterpriseDB with their Postgres database. And we also had some of our adopters also give a customer testimony, if you will, of what they've been using Canister for. So check that out. We'll have a slightly more updated version of these slides which have all these references so you can follow through on that. But our community is growing. We have bi-weekly Zoom meetings and we have an active Slack channel where our engineering team and other contributors are answering questions for all the new people who are coming in and learning about this brand new sandbox project. We have a number of example blueprints. I think we showed you a bunch of icons but go check them out. And this is where the community is contributing updates and improvements and new workloads all of the time. We've also pointed to a number of slides earlier if we're pointing out to these references and we're actively involved in the data protection working group of Kubernetes. As a CNCF Platinum member, our mission is not only to the community and not just to open source but to advance Kubernetes engineering as well. And this is our contribution, Canister being part of it in addition to all of our commercial activities. And so when we drive things forward such as other CNCF projects like Qvert and how are those backed up? How are VMs managed properly? You can now guess behind the scenes, Canister is one of the tools that we put in our arsenal for doing data protection of any type of Kubernetes staple workload. And Canister is that escape valve that allows us to orchestrate any concern on cluster, off cluster with built-in tools or with inside car containers with any logical tooling that Canister doesn't have in itself. We've really built an extensible system that really defeats the need to do this the wrong way or in a proprietary way but in completely in a vendor neutral cloud native way for application consistent backup and recovery. And so that's been our contribution to the entire community. And please join us, please come to canister.io. I've put in the link in our chat for how to get to Michael's visualizer, I can't speak right now, visualizer instance and we will point to all of the code base as well. So we also, this is our second Canister webinar. If you wanted to see a more extensive demonstration of how we set up and all that stuff I'll point you to our July one here. And this set of slides is already in our GitHub repo. So go to canister.io, click over to the get repositories maybe go back up to the demo repository and you will see the details of all of these links. We also have a hands-on lab at cube campus. We have a nearly 70 page white paper taking you through the how to become a blueprint maintainer and creator. It's focused around our elastic blueprint. That's a way paper requires registration or hands-on lab requires registration but almost everything else is purely open source. And if you have any questions come and join us in our Slack instance and we're happy to get you on board. So I thank you for your attention today. Thank you Michael so much. Thank you Libby so much for hosting us. We're really excited to kind of grow Canister with you and we're really excited to solve application consistent backup and recovery for staple workloads on Kubernetes. This is why we contributed it and this is just the tip of the iceberg for how to solve this problem. Thank you so much. Thanks Michael, thanks Mark. Great presentation. Thanks everyone for participating. You know where to find everyone if you wanna follow up and we'll go ahead and wrap up. The recording will be online later today. Again, you can access it through this link or by visiting our YouTube channel for CNCF and everybody have a great rest of your day. We'll see you again next time for another CNCF live webinar. Thanks so much, cast and crew. Thank you everybody.


Everybody Matt here for late in sports cards ripping one box of 2022 top stadium club baseball hobby This is for Steven H. Good luck Steven box topper is Nice one. That is Seya Suzuki Rookie oversized box topper one. I want to see a big hit. We've seen some nice stuff at a stadium club so far today There's a black and white KC mice baseball Tube a that is nice. That is black foil auto Wade Boggs Nice chicken, man. I think that's gonna be the 25 That is one of 25 Tate's team of the future Seya Suzuki rookie. There's Jayrod rookie Brian Reynolds Cal Ripken Babe Ruth you also know it's Ken Griffey junior power zone Awesome Chris appreciate it. Yeah, let's get that filled up one to go now on optic Wonder rookie Mondesi Ashby TJ Friedel. That's a rookie red foil missing the rookie in our rookie logo, though Although his auto has the rookie logo on it touching. It's Josh Lowe rookie black foil Shawn Manaya Palmer Kenzie Gore and rookie auto Louise Frias That's Chisholm Spencer Torkelson. I think that optic on the fly is sold out Brandon Crawford I'll do those two tops chrome black and then we'll do the optic on the fly Nice that is rookie chrome seya Suzuki.  There's Jeremy Pena rookie Thomas Justin Turner red. All right. Last pack Good box here. There's Shohei Otani black foil Com Brian Reynolds and that will do it for your box. Good stuff Steven appreciate the purchase. We'll get these right out to you


Hey, so what we're gonna do this morning is we are going to call a huge Titans fan Ron happens to be at Ohio State fan alum. So he gets the first call Let's see. Hey, Ron Is Ron there? Hey, Ron. This is coach variable from the Titans. How are you man? Well, you sound great they said you're how old are you said you're in the late 80s, I Tell you what you sound pretty darn good to be 87 Play and saw Yeah, I tell you what man, you saw a lot of good Buckeyes go through Ohio State in your time We're doing great. I'm doing great. I just wanted to call and check in on you make sure You're doing okay. See how you're feeling I'm very great lost my wife in September and then we came down to see you and Kerry coos and so forth when we had that on our state all night. Yeah Over at the stadium. Yeah, we raised a lot. We raised a lot of money for the For the scholarship fund for Middle Tennessee for Ohio State So what? First of all, you know, I'm sorry to hear about your wife. Did you was she a Buckeye fan and a Titans fan, too? You met her at Ohio State Yep Love it sounds like sounds like Jen I don't know if I'm gonna make it to 87, but I met Janet Ohio State, too She didn't she doesn't have any choice. She has to be a Titans fan, too Yep, and I'll tell you what where did you grow up in Ohio? Right there behind Ken McKinley, huh Yeah, well right behind the stadium. Yeah, right behind a stadium. They that that stadium. Have you seen it since they remodeled it? Back there for quite a while. I think mr. Benson before he passed away gave a lot of money to it and they renamed it In his name. Really? Yeah. Yeah, they've got a new stands new stadium new turf It looks really really nice and I think and I don't quote. I know the Cowboys are playing I think the Cowboys and Steelers might be playing This year in the Hall of Fame game Oh, really? Yeah it must have expanded the stands because When we were going to school there was only 17,000 which is pretty big at that time Yeah for high school. Let's I think they actually do I think they played a state championship there a little bit in and football too So, you know, we're trying to stay busy, you know, we're I don't think we're gonna be You know, we're gonna be working remotely We're gonna be concentrating on his draft right now. We signed a few free agents Got some of our guys back. So We're on to the draft now. You got any suggestions other than take a bunch of house day players That's what you want to ask and put hiring coaches from our house they get players Well, I appreciate it that means a lot and I don't know any other Way to do it. So that's what I'll keep doing. I'll keep coaching them and and trying to teach them every every chance I get We won't I'll tell I'll tell I'll tell John Robinson. I say Ron once this takes many buck eyes as we can get Well, I appreciate your support and you know once we get back to work man You come down and see us at OTA's and come hang out for a day. Okay Okay, thanks for your support Ron You got it buddy tighten up


This thing is really cool. What is today's question gonna be? Okay, so in this video I want to talk about superpowers. Specifically I want to talk about how to actually fly in a lucid dream. Because this is something that a lot of people find difficult. And I think there's a common misconception with how this is done. So firstly, let me just change the angle of this. It's not quite right though. Right, so the first misconception about flying is that you need to exert some sort of physical strength with your muscles in terms of how you're gonna fly. Now, we've heard of people flapping their hands or their arms to try and fly higher. Now while that can work, and I don't doubt that that works, like if that works for you, I'm not debating that. What I would say is that it's not as effective, or at least I've found it not as effective as actually using mental effort or expectation and belief. So what I mean by that is instead of flapping your arms to try and fly higher, because you've got to think like in a dream you're not governed by, I was watching The Matrix last night and that sort of emphasised it further, you're not governed by actual forces as such, it's just your expectation and your understanding of the rules.  But in a dream you don't need to believe that, that's not an empowering belief and in fact that will hold you back. So don't enter this with the expectation that flying should be hard, it should be easy, because if you're lucid, if you're actually aware of the fact you're dreaming, you should know that it's a dream and therefore you should know that you're in control and you can decide whether you fly or not, it's as simple as that. And while beginners can find it difficult, I understand that, if you switch from, and this is something that I teach in my lucid superpowers book in great detail, there's a link in the description if you want to check that out and have more superpowers and stuff like that.  Because just like in The Matrix you're not actually breathing air in a lucid dream, you don't actually have muscles and you don't have any sort of physical strength in a lucid dream.  So that's really important by the way, I'm going to say that again, you don't have physical muscles in a lucid dream, you just have what your brain thinks you have.  This is exactly, I don't know if you've seen The Matrix, you should have done because it's a classic film, especially for lucid dreamers, but if you've seen a scene where Morpheus fights Neo for the first time, and you see Morpheus is moving very fast, he knows all the moves, but he's not breathing, he's not out of breath in the same way that Neo is because he understands that if you expect to be able to do it, you'll be able to do it. You don't need to be out of breath because you're not using your physical strength, it's a projection, the whole thing is a projection, and in the same way in a lucid dream, you shouldn't be out of breath, it shouldn't be a challenge, if you've set your mindset up in the right, I don't want to touch my cheek then, I normally touch my head when I do that, if you set your mindset up in the right way, you'll find it so much easier, you really will find it so much easier. So that's it guys, if you want to learn more about this stuff and if you want to really master flying, then go and check out the Lucid Superpowers Guide, there'll be a link in the description, if not I'll see you tomorrow, done. So it's fine now right, or subscribed or gone onto my website or something like that.


The Equitable Life Assurance Society presents This Is Your FBI. This Is Your FBI. The official broadcast from the files of the Federal Bureau of Investigation. Presented transcribed as a public service by the Equitable Life Assurance Society of the United States and the Equitable Society's representative in your community. If your plans include sending your youngster to college or providing for a pleasant, comfortable life after 60, owning your own home free and clear years ahead of time, we have a plan. By we, I mean the Equitable Life Assurance Society of the United States and its 8,000 representatives from coast to coast. It will pay you to get acquainted with your local Equitable Representative. He's friendly, helpful, and he knows the answers. In about 13 minutes, I'd like to tell you more about him and how he may help you to enjoy the many advantages of membership in the Equitable Society. Tonight, the subject of our FBI file, homicide. It's titled, The Death Cruise. It is the proud record of your FBI that 97% of those the Bureau apprehends and takes to court are later found guilty and sentenced. That record indicates a thoroughness and a basic respect for detail in every investigation. Because it often happens that the only testimony for the prosecution is given by special agents of your FBI. After conviction, the file on that case is marked closed. Those files are records of jobs well done, records of which the Bureau is justifiably proud. For that reason, it is understandable that your FBI does not like to reopen a file that has been marked closed, does not like to have to do its job all over again. That does not happen very often, but as you will see in tonight's case, it does happen. Tonight's FBI file opens on the mouth of a river located in one of our eastern seaboard states. A cabin cruiser courses slowly down the stream. Rounding a bend, it noses into a weather-worn dock. Its pilot, a young man in his middle 20s, ties the boat to a stanchion and walks down the dock to a dilapidated waterfront hotel. He opens a sun-warped stream door and enters the lobby. Anyone here? What do you want? Are you in charge here? Yes, why? I'm, uh, looking for information. What about? One of the boats that's tied to the dock out there. Which one? Seamade 2nd. Who owns it, you know? No. Yeah, isn't that, uh, dock connected with your hotel? No, everybody uses it. Oh. Well, look, mister, if you just came here to ask questions, I haven't got the time. Oh, wait, please. Well, what is it? The, uh, Seamade passed me an hour or so ago upstream. I thought I recognized its pilot. Did, did you see the boat tie up? No, I didn't. Well, uh, perhaps you know this man. He's about my size, blond hair, moustache. His name is Sanderson. I never heard of him. Well, if he uses this dock, you... Well, I told you anybody can use it. Well, he couldn't have docked more than 10 or 15 minutes ago. Where could he have gone from here, do you know? Well, to town maybe. What town? Fairport, Clear Falls, Cedar Point. They're all near here. I see. Well, I guess I'll just have to wait for him. Sometimes people leave their boats here for days. I'll wait. Who's there? Alice. Well, what is it? What do you want? All right, come in. I told you, Alice, that I wanted to take a nap. I know. Well, why do you disturb me? Well, a man was here looking for you. Who was he? I don't know. What did he want? He didn't say. Did he ask for me by name? Yes. He said you passed him in your boat upstream. He thought he recognized you and followed you down here. Where is he now? He left. He returned to his boat. What did you tell him? That I didn't know who you were or where you'd gone. I see. But he's going to wait for you anyway. This is bad. Well, I tried my best to get rid of him, John. Raise the window, Shade. Sure. Adjust the travel. How's that? Fine. Now, which one is his boat? Well, it's at the very end of the dock there, you see? Yes. He must be below. Where's your husband? He went into town. As soon as he returns, send him up here. Hello, aboard there. Are you the owner of this boat? Yeah. Let's see your license. Boat license? Nope. License for using this dock. Uh-oh. Oh, I didn't know one was necessary. It's a town ordinance. Who are you? Deputy Sheriff. See? Well, look, could I arrange to get a license from you? Nope. Got to get one in town. Are they open this time of night? Nope. And what do I do? Leave the dock. I couldn't do that. Look, mister, that's an order. Sheriff, I might as well tell you why I'm here. All I'm interested in is a license. Listen, that, uh, boat right over there. That's Seamade 2nd. I followed down the river this afternoon. There was a man aboard it. I think I recognized. Huh? I know that government agents would be very anxious to apprehend him if he's the man I think he is. Are you a government agent? No. Any kind of policeman? No. And why are you so interested? I was in army intelligence during the war. Buddy, the war is all over. Yes, but... Look, which boat are you talking about? That one down there. The black hole. Her name ain't Seamade 2nd. Yes, it is. That's the Ebony Queen. I'm sorry you're wrong. Come on, have a look for yourself. I'll prove to you that's the Ebony Queen. Owned by a man named Smith who lives at Cedar Point. He ain't been in no trouble with the government ever. This Smith about my size. Blonde hair, moustache. No, sir. He's short, fat, and bald. Well, would anyone else be using his boat? No. Well, what does that say there? Ebony Queen. Yeah. I don't understand. That's the boat I followed. Look, mister, your story just don't make no sense.  Oh, sorry, sir. I'm staying. Some 50 miles away in an FBI field office, Special Agent Jim Taylor is just approaching the desk of the agent in charge. Mr. McComb. Yes, Jim. Can I see you for a minute, sir? Well, surely. What's on your mind? I received a phone call late this afternoon from a friend of mine named Ed Bartlett. No. Ed was in army intelligence during the war. We worked together on a number of cases involving enemy aliens. That was when I was with the New York office. I see. One of the men we picked up at the beginning of the war was a Nazi named John Sanderson. He'd been engaged in subversive activity. He was convicted on several counts and sent to a federal prison. I remember hearing about him. Well, you may also recall, sir, that Sanderson was released at the end of the war and deported to Germany. Yes, yes, I do. But what's this got to do with your friend's phone call? Well, Ed's been out on his boat on a fishing trip for the past week. This afternoon, a small pleasure cruiser passed him. Ed was almost certain the man at the wheel was John Sanderson. What? Yeah, he said he followed the boat to a dock down near Cedar Point. No one was aboard her, so he inquired at a nearby hotel as to where the man had gone. He couldn't learn anything there. Well, Jim, this sounds more like a case of mistaken identity. I thought so myself at first, sir, but Ed insisted he had the right man. Knowing him, I'm inclined to believe him. Well, we have a file on Sanderson here. Check it. It's possible we were both mistaken. Maybe he wasn't deported. Sir, I've already checked. He was sent out of the country over five years ago. I see. Where's your friend now? He's standing by down there waiting for the man to return. Has he contacted the local police? I advised him to. I'm not so sure that he will. Mr. McComb. Yeah? I wonder if you'd give me permission to get out of there. If this is a false lead, I'll be back by tomorrow night. Go ahead, Jim. Yes? It's me, Henry. Come in. What happened? Weren't you watching from the window? It was too dark to see, but I didn't hear his boat pull away. He ain't going. Why not? He just said he was going to wait until you came back. Did you impersonate a deputy sheriff? Yep. Well, didn't you threaten to arrest him? Yep. He just said, go ahead. What about the boat? Did you repaint the name? Mm-hmm. But he's still going to stay. What did you find out about him? He said he was an army intelligence during the war. Oh. Also said the government agents would be very happy to grab you. He's really going to be difficult to get rid of. Yep. Where's Alice? Downstairs. Bring her up here. Can you see all right, Mr? Yeah. Yeah, I'll just lead the way. When did this man come to your hotel? About 20 minutes ago. He took a room for the night. His name is Sanderson. That's right. And he's got blond hair and a mustache, just like the fellow that you were looking for. Mm-hmm. That's why I came right down to your boat to get you. Oh, I appreciate it. Oh, here's the back door. You can go in this way. Right. Now, his room is right at the head of these stairs. Thanks. Wait. Yeah? Well, I just happened to think, now there ain't going to be any trouble between you two, is there? Well, to tell you the truth, there might be. Oh, well, then I'd better get the sheriff. He's right out front in the lobby. Yeah, that might not be a bad idea. Bring him up to the room. Okay. Yes? Hello, Mr. Sanderson. You remember me? Yes, of course. You're the young man who was in army intelligence. That's right. What brings you here? Your boat passed mine on the river today. I recognized you. So you were deported from this country about five years ago, weren't you, Sanderson? That's right. Then how did you get back here? Illegally. Well, you admit that, huh? Yes. I'm going to have to see to it that you're deported again. Really? How? By turning you over to the FBI. Have you with the authority to make an arrest? No. Then how are you going to do it? Well, this should be your answer. Come in. Here's the sheriff. Good. Come in, Sheriff. Okay. You wanted to see me? Yes, Sheriff. This is the man I was looking for. Well? He's in this country illegally. He should be arrested and turned over to the FBI. Did you hear that, Sheriff? Yep. Well, what are you going to do about it? Well, now, let me see. You should obey the man, you know. You think so? Of course. What is this? Show him, Henry. Okay. Nice work, Sheriff. We will return in just a moment to tonight's exciting case from the official files of your FBI. But right now, here's a question. When was the last time you saw your doctor for a complete physical checkup? Everybody should see his doctor regularly. Keeping healthy is protection for your family. Just as the right kind of life insurance is protection for your loved ones no matter what happens in the future. What is the right kind of protection? Perhaps the experience of Mr. Frank Murphy may help you. Mr. Murphy, before you became a member of the Equitable Life Assurance Society, what was your problem? Protection for my wife and kids. You see, I make a comfortable living, I've got big money. My social security would help, but it certainly isn't enough to keep my family well fed, well housed, and well clothed until my youngest gets through high school. So when I heard you talk about a plan that would provide me with that kind of security, I got interested. That's our Equitable Family Security Plan. Right, and a good name for it, too. So, as you suggested, I called my local Equitable Representative and he came right over. He didn't try to sell me anything. I made it simple and easy for me to figure how much more income my wife would need to keep her and the kids in comfort. That's the famous Equitable Fact finding chart for fathers and mothers. Incidentally, there's no charge for this chart. It's available to everyone who wants to know exactly how much protection his family needs. The chart was a big help, and our Equitable Man was a bigger help. Now that my family is secure, I'd advise anybody to call up his Equitable Man. They're good men to do business with. They are. You see, Equitable Men are more than life insurance men. They're interested in your problems and in presenting a plan that fits your needs and your budget. So please remember, no matter what your insurance problem may be, talk it over with your local Equitable Society Representative. Ask him for your free copy of the Fact Finding Chart for Fathers and Mothers. Consult your local telephone directory for the name of this friendly, helpful neighbor, your local representative of the Equitable Society. That's E-Q-U-I-T-A-B-L-E. The Equitable Life Assurance Society of the United States. And now back to tonight's FBI file, The Death Crew. The desire to see that justice is done is strong in almost every one of us. But sometimes that desire leads to trying to take the law into your own hands. As tonight's case from the files of your FBI illustrates, that is the wrong course of action. In every city there is a local police force. In every state there are state troopers. And in every section of the country there are field officers of your FBI. It is their job to see that laws are enforced, that justice is dealt out fairly. Your job as a citizen is to respect and obey those laws. And when, as will sometimes happen, you know of a crime that has been committed or a criminal who has gone unpunished. This is from the responsibility of seeing justice done. Your responsibility ends when you have done your duty. When you have notified your local police. Tonight's file continues at the police station in the town of Cedar Point. Special Agent Jim Taylor has just introduced himself to the chief of police. Sit down, Mr. Taylor. Thanks. Now, what can I do for you? Did a man named Ed Bartlett contact you any time yesterday or this morning? Bartlett? No, he didn't. Why? Well, he called me yesterday afternoon. He'd been out on his boat on the river. I thought he recognized a man who had been deported from this country some five years ago. Where was this? On the river. This man was in another boat and he trailed him to a dock about two miles north of there. The one near the Ocean View Hotel? Yeah, that's right. I told him to contact the police. I thought he might have come to you. He didn't. Have you tried the Fairport police? Yes, I have. How about Clearford? No, they hadn't heard from him either. Have you looked for him? Yeah, I went out of the dock. I couldn't find any trace of his boat, though. Did the man took off again and Bartlett followed him? Yeah, that's very possible. Did he give you a description of the other boat, the one suspect was on? No, no, he didn't. Well, I'm afraid. Excuse me. Sure. Chief Jenkins. Yes? Yeah. What's that? Where was this? I see. What's the name of the boat? All right. Thanks a lot. I'll be right down there. Mr. Taylor, what does Bartlett look like? He's about six feet tall, dark hair. Was the name of his boat the Lucky Star? It sounds like it, yeah. I'm afraid I have some bad news for you. What is it? The body of a man of that general description was just found in the boat named the Lucky Star. Oh, no. We can't be sure that it's Bartlett, of course. Where was this? About 10 miles downstream. It drifted in the shore. Let's get down there at once. That you, Henry? Yeah. We're here in the back room. Did you go into the village? Yeah. Any news of the boat? Nope. It'll probably be found sometime this afternoon. That soon? I imagine so. But what do we do? I'll leave tonight, just as I plan. I suppose the police should come here. I don't know what it means to make it appear that his death was accidentally. Look, Alice, stop worrying. Everything is going to be okay. There's the body right over there, Mr. Tiller. Yeah, I said. Yeah, I said Bartlett, right? Too bad. I guess we'll have to examine him.  Yeah, I see. Say there's blood in the back of that boat hook there. From the position of the body, he could have very easily slipped and fallen against it. Yeah, he could have, but I don't think he did. I'd say this is very carefully staged to appear that way. You think he caught up with the man he was looking for? Ah. If he'd only contacted your chief, instead of trying to do the job alone. Yeah. Well, shall we go below? Oh, boy, I'd want to search his pockets first. It's just barely possible. You might have left a note of some kind. Telling you more about this man he was following? Uh-huh. If we just had a description of his boat... Yeah, I know. Find anything? Ah, just this book of matches might be of some help to us. How's that? Well, they're from the Ocean View Hotel. That's the place for the dock, isn't it? Mm-hmm. Well, then you must have gone in there at some time. You, uh, you know the people who run it? Yeah, it's a couple named Fowler. Well, they might be able to give us some information. Well, we can follow it. There's some blue painter on the deck. See it? Yeah. It's a very odd shade of blue. It didn't spill here. Looks like it rubbed off or something. Mm-hmm. I'm going to scrape a few flecks of it off. You want a knife? No, I've got one. Thanks.  I'll finish up here.  Police Jenkins, Mrs. Fowler. Oh, hello, Mr. Jenkins. Oh, this is Mr. Taylor, Mrs. Fowler. Howdy-do. Mr. Taylor is a special agent of the FBI. I see. You might be able to help him. How? Well, yesterday afternoon a man named Ed Bartlett put his boat into that dock outside there. Ed Bartlett? That's right. He's a man about six feet tall, dark hair, slightly broken nose. You see him by any chance? No, sir. Is there a reason to believe he came here to your hotel? Well, I didn't see anybody that looked like him. Did you see his boat? It was called the Lucky Star. No, sir. Oh, it is Mr. Fowler. He might be able to help us. Mr. Fowler? Oh, hello, Chief. Hello, this is Mr. Taylor. He's from the FBI. Hi. We're looking for information, Mr. Fowler, about a man named Ed Bartlett who docked his boat outside here yesterday afternoon. It's called the Lucky Star. Do you see it? No, I didn't. Maybe you saw him. He was six feet tall, dark hair, slightly broken nose. Nope. Didn't see him. All right, Chief, I'm afraid this is a bad lead. We'd better be going. Thanks a lot anyway, folks. Come on, Chief. Okay. All right. Henry? Hmm? Get upstairs and tell John who was here. Let's head out here to the end of the dock, Chief. Okay. Say, don't you think we should question the Fowlers a little more? I purposely cut that interview short. Why? Do you notice Fowler's trousers? No, I didn't. There was a streak of blue paint on the right leg. I'm certain it was the same color paint that I scraped off the deck of Bartlett's boat. Well... It reminded me of where I'd seen that paint before. I noticed a can of it yesterday when I came out here under the dock. Where about? It's right alongside this boat up here. Man, there's a pink can. Yeah, I think that's the one. Hey, it's that same odd shade of blue. Yeah. Now, I wonder if you... Wait a minute. Shine your light again on the stern of the boat there. Right there? Yeah. Hold it. Fuck, Chief, the name on that boat's been freshly painted. Heavenly Queen. All right. I suppose it was called something else before. The name was changed to avoid suspicion. Well, if it was, then that's Sanison's boat. There's whole paint-cycle ties together. You think Fowler's mixed up in it, too? Yeah. Well, you go board and search the boat. Okay. I'm heading for the nearest phone to call my office. I want to see if anyone named Fowler's ever been mixed up with Sanison. Is that you, Mr. Taylor? Kindly put up your hands. What are you doing on this boat? I'm Chief of Police Jenkins. You haven't answered my question. Who are you? That doesn't matter. Would your name be Sandison? Yes. And you know why I'm here? Yes, but it isn't going to do you any good. What do you mean? I'm about to take a trip down the river. I need to change. You won't get very far. I will if I travel alone. Is that you, Henry? Yep. Come below. We have company. We have to take care of them. Go above and cast off the line first. I would prefer that this happen while we're out in the river. Well, do as I say. I can't. Why not? Because I've got a gun in his back. Drop your Sanison. All right, pick up his gun, Chief. Okay. Well, I was told that Fowler was Sanison's brother-in-law. I dropped by, picked him up, and brought him down here. Sure glad you did. Now I can place them both under arrest. It was probed that although Ed Bartlett was assaulted in the hotel, his death occurred on the boat. Therefore, Sanderson was convicted in federal court for murder on the high seas and sentence to be executed. Henry and Alice Fowler were convicted as accomplices and given a life prison term in a federal penitentiary. This time your FBI marked its file not closed, but dead. And it was able to do that only because of the shrewd powers of observation of a special agent who remembered where he had seen an offshade of fate. Sanderson is not a talent that anyone is born with, but they are a talent that can be developed that has been developed. That has been developed in the course of study that every special agent must pass before he becomes a qualified member of your FBI, before he goes to work for you, the American people. One primary cause of much needless worry is money. Husbands worry about the future security of their wives and children. Others worry about poverty in old age. Others worry about assuring their children's education. Now there is one man who can help you enjoy freedom from such worries. He is your local equitable representative, the friendly, helpful neighbor who knows the answers to your problem. Consult your local telephone directory for the name of your local representative of the Equitable Life Assurance Society of the United States. Next week we will dramatize another case from the files of the Federal Bureau of Investigation. It is a project homicide. It's titled The Astrological Breakout. The incidents used in tonight's Equitable Life Assurance Society's broadcast are adapted from the files of the Federal Bureau of Investigation. However, all names used are fictitious and any similarity thereof to the names of places or persons living or dead is accidental. Tonight the music was composed and conducted by Frederick Steiner. Your narrator was William Woodson and Taylor was played by Stacey Harris. Others in the cast were Herb Butterfield, Lamont Johnson, Bill Johnstone, Mary Ann Cape, Lou Merrill and Vernon Ridge. This is your FBI is a Jerry Devine production. This is Larry Keating speaking for the Equitable Life Assurance Society of the United States and the Equitable Society's representative in your community and inviting you to tune in again next week at this same time to bring you another thrilling transcribe story from the files of the Federal Bureau of Investigation. The Astrological Breakout on This Is Your FBI.


What's going on everybody? If you read the title of this video you know that I am going to be singing a song, the very first song on the channel. Is it perfect? No, but I had a lot of fun making it and I hope that you enjoy and know that I wrote these lyrics from the bottom of my heart. I hope that they touch your heart as well. Let's go have a listen. All the stuff in here is what I said. I don't know anything, the truth is I google almost everything. Stack Overflow is my best friend, I'll be using it until the bitter end. I don't want to lie to you and say I know it all. That's the truth about my job. I get to work and I settle in and my boss comes over with a question saying these numbers look great can you show me how you got them? Click around and I pull up my script and we start to look over it and here is what I was thinking. I don't know anything, the truth is I google almost everything. Stack Overflow is my best friend, I'll be using it until the bitter end. I don't want to lie to you and say I know it all. That's the truth about my job. I get over to my mama's house, she's cooking and I settle down, she says someone's so proud of you. That kind of stuff makes me groan, how did you learn that all in your own and I didn't have the heart to tell her. Stack Overflow is my best friend, I'll be using it until the bitter end. I don't want to lie to you and say I know it all. That's the truth about my job. That's the truth about my job.


What is approval voting? Simply put, it's a better way to run an election. Let's take a trip to Plantsville. It's election time and Mayor Blueberry is campaigning hard for a second term in office. She won the last election with 65% against her opponent, Mr. Squash, and she still enjoys strong support. Once again, Mr. Squash is quick to challenge Ms. Blueberry, but this time they're joined by a third challenger, Mr. Peach, who shares similar views with Mayor Blueberry. Mr. Peach sweet talks almost half of Blueberry's supporters into switching their vote to him, while Mr. Squash holds the same 35% he had last time. The votes are counted. And what's this? Mr. Squash wins? Blueberry and Peach have split the fruit vote. How did this happen? Peach's supporters also like Blueberry, but couldn't say so on their ballots. A simple solution is to change the ballot from vote for one to vote for one or more, allowing everyone to state all the candidates they support. This is called approval voting. With approval voting, the election would have gone quite differently. Peach's supporters no longer fear that a vote for Peach will help elect Squash. Instead, they show their sincere support for Peach and also Blueberry. They want to prevent Mr. Squash from winning, and they do. And approval voting accurately reflects Peach's support. Mayor Blueberry wins the election. Democracy is restored. Approval voting is more than just a smart idea in plan spell. It's a smart idea anywhere you vote. Approval voting is used by organizations across the globe, and for good reason. It's democratic because the candidate with the most support wins. It removes the spoiler effect. Even losing candidates get an accurate reflection of support. And voting your favorite never hurts you. Start the conversation on approval voting and share this video. Then join the Center for Election Science at electology.org. Better voting starts with you.


Hello, and welcome to a video summarizing Sir Arthur Conan Doyle's novella, The Sign of the Four. In this video, I will walk you through the story's narrative structure, and I'll summarize each chapter of this novella, highlighting key quotes to memorize for every single chapter. This video is especially useful as you'll get a broad overview of the novella, but also, if you're studying this text on a last-minute basis for your coursework or exams, then you'll find this summary gets straight to the heart of all the events in the novella. Do bear in mind that we have an in-depth Sign of the Four course that covers everything, including context, plot and structure, themes, characters, and Conan Doyle's use of language, and most importantly, you will get access to top level nine month law answers, and you will learn how to write top responses for your coursework or exams. So let's get started. Now when it comes to the narrative framework of this novella, one thing to bear in mind is a striking feature of The Sign of the Four, as well as other Sherlock Holmes stories, is the use of Watson as the first person narrator. Now many novelists, especially at the time, such as Jane Austen in Pride and Prejudice, used omniscient narrators who are not characters in the novel, but instead are written in the third person by an unnamed narrator, providing an all-knowing, all-seeing point of view and able to comment on the thoughts and actions of many characters. Other novelists, however, use first person narrator, who are the main characters or protagonists in novels, such as Charles Dickens, his use of Pip in Great Expectations, and this allows us as readers to follow the tale completely through the point of view of one main character. Now in this novella, Conan Doyle does employ first person narrator, but instead of seeing the story from Sherlock Holmes' point of view, we see the mystery from the perspective of his devoted follower, Watson. Now this was done to sustain suspense in the stories, as Holmes's thoughts are not always revealed to us as they occur. If we as readers arrived at solutions as quickly as the protagonist Sherlock Holmes does, the novel then lacks mystery and it can end very abruptly. However, with Watson as our narrator, we trace the plot in the same way as a reasonably intelligent and sensible person might, but without Sherlock Holmes as rapid genius. So this has led many critics to believe that Watson serves as a proxy for us as readers and we're able to marvel at Sherlock Holmes' talents in a similar way to him. Also, during the age of realism, Watson provides an excuse for writing the tales by explaining that he's written about previous adventures for publication and he makes clear in the narrative that he's recounting something that happened in the past while occasionally referring to the present, such as his wife reminding him of what happened on the trip to the Lyceum Theatre and what this does is it does to some degree remove a sense of suspense as it reveals that both Watson and Mary will survive this encounter and later they will be together. Now when it comes to the structure of this novella, do bear in mind that this is detective fiction and thus detective fiction must involve crime or mystery that needs to be solved, but unlike other mysteries, the initial focus is usually on the detective. Now this story often begins with Holmes and Watson in Baker Street with Watson offering an admiring and sometimes exasperated description of Sherlock Holmes and his remarkable ability, which serves as the novel's initial exposition. Next, structurally speaking, a client arrives presenting a crime or mystery that must be sufficiently interesting for Sherlock Holmes as well as us and this provides what we call a catalyst for the subsequent actions. A series of puzzling clues such as for instance the mysterious son of four notes is presented and there must be obstacles or complications that prevent a quick and straightforward solution such as a murder within a locked room and then an exciting climax is needed which may involve chasing and trapping the criminal followed by a full confession of the criminal which serves as a novel's denouement, the end. And so of course this story follows this typical structure of detective fiction. However, do bear in mind structurally speaking that there is a subplot. So alongside the main plot of the mystery in this story there's a subplot of romance between Watson and Mary. So although many fewer words spent on this subplot by Sir Arthur Conan Doyle than the mystery, this subplot still provides a vital counterpoint to the main story and it reveals the differences between the characters of Sherlock Holmes and Watson. So over the course of the novel, Watson is immediately attracted to Mary, he grows to admire her, he has his hopes dashed by the prospect of her inheritance and then upon learning that the treasure has vanished he proposes to her. And the last chapter ends with Watson's happy announcement of his impending marriage contrasting with Holmes' slipping back into a somewhat dark depression. So now let's look at the plot in a nutshell. Beginning with chapter one. So the chapter called The Science of Reduction begins with Dr. Watson, the novel's narrator who bemoans Sherlock Holmes's tendency to indulge in artificial stimulants and in this case, cocaine. Holmes says he craves mental exaltations and is often bored because he doesn't currently have a case for detection and he proudly experienced his position as world's only unofficial consulting detective helping out the professionals when they are out of their depth. And as a challenge, Dr. Watson hands him a watch and asks him to deduce who this owner is and Holmes correctly reads the clues in the watch and announces that it belonged to Watson's unfortunate deceased brother. And the chapter ends with the announcement that a young woman has arrived and wants to see Holmes. Now, in terms of key quotes to remember from this chapter, the first one would be but I aboard the dull routine of existence are crave for mental exaltation and of course this is Sherlock Holmes talking about why he takes drugs. Also he talks about being an unofficial consulting detective. Also eliminate all other factors and the one which remains must be the truth. This is the process of deduction and finally I'd forgotten how personal and painful a thing might be to you. This is when he talks very dispassionately about this watch and Watson's brother. Now in chapter two, which is the statement of the case, the mysterious lady is Miss Mary Morstan and she's a 26 year old governess who enters Holmes's room and explains the baffling case of her father. So he'd been an officer in an Indian regiment and after mother's death had placed Miss Morstan in a boarding school. 10 years ago when she was 17, he returned to England and asked her to meet him at the Langham Hotel in London, but he disappeared mysteriously before they were reunited. She contacted her father's closest friend Major Sholto who claimed not to know that her father was in England and after answering an advertisement requesting her address, she had for the past six years upon the same date, received a box containing a single rare pearl. To add to the mystery on that morning, she received a letter saying she was a wronged woman and this letter asked her to come to the Lyceum Theatre and advised her that she could bring two friends and of course Holmes and Watson agreed to accompany her to this meeting. And the quotations to remember from this chapter are, you really are an automaton. This is Watson describing Holmes. The client to me is a mayor unit. This is Charlotte Holmes talking about his perspective on clients and the description of Mary Morstan is a very attractive woman. Chapter three, which is titled Inquest of a Solution shows Holmes who's discovered that major Sholto, the late Captain Morstan's friend, passed away six years ago. Holmes believes that Sholto's heir must know something about the mystery and perhaps is hoping to compensate Miss Mary Morstan. They're set off for the meeting at the Lyceum Theatre and Miss Morstan shows Holmes a curious paper, which she's discovered in her late father's belongings and this paper has a diagram, various notations including a curious hieroglyphic of four crosses and the phrase of the son of the four, along with four names. At the theatre, they're then met by a man who ushers them into a carriage, drives into a terraced house in the southern suburbs of London. An Asian servant answered the door and a voice from within asks that they be shown in. And the quotations from this chapter is curious paper. There was something airy and ghostlike in the endless process of faces which split it across these narrow bars of light. This is describing the airy images that they see as they go through London in the darkness and driving to an unknown place on an unknown errand. Now, chapter four, which is titled the story of the bald-headed man. Now, there's a bald-headed man of the chapter who we learn is the dais Sholto, one of Major Sholto's sons and he's actually the first half of two twins, Bartholomew Sholto being his other twin. He's an eccentric character who has turned his outwardly ordinary house into a luxurious and exotic apartment. He explains that his father returned from India very wealthy man, but he was also fearful of being attacked and frightened by men with wooden legs to the point of paranoia. On his deathbed he confessed that he and Captain Morstan had argued over the division of the treasure from India and that Morstan had died suddenly of a heart attack, fearing that he'd be accused of murder. Major Sholto and his man-servant hid Captain Morstan's body and deprived Miss Morstan of her inheritance and regretting this, Major Sholto wanted his twin sons, the dais and Bartholomew to make reparation, but just as he was going to reveal the location for the rest of the treasure, he was startled by a mysterious face at the window and suddenly died and the dais arranged for the pearls to be sent to Miss Morstan as a small reparation, but now Bartholomew has discovered the rest of the treasure and the dais arranged for them to all travel to Pondicherry Lodge to demand Miss Morstan's share, which would make her a wealthy heiress. Now the key quotations from this chapter are in that sorry house it looked as out of place as a diamond of the first water in a setting of brass to describe the dais Sholto's home, the cursed greed which has been my besetting sin and it was a bearded hairy face with wild eyes describing the dais Sholto's appearance. Chapter 5 called the tragedy of Pondicherry Lodge. Now upon arriving at Pondicherry Lodge there are signs that the grounds were dug up by Bartholomew when looking for the treasure. The housekeeper Mrs Bernstone is heard crying, she then explains that Bartholomew had locked himself in his room and wouldn't answer her. Homes in Watson then break down the door and discovered that Bartholomew was dead and on the table near the dead man is a mysterious hammer-like object and a piece of paper with a sign of the fall on it and stuck near the dead man's ear is something that looks like a thorn and the dais notices that the treasure is missing and Homes sends him off to report the crime to the police and the quotations for this chapter are the vast size of the building with its gloom and its deadly silence struck a chill to the heart. Also I wonder a subtle thing is love and the features were set in a horrible smile a fixed and unnatural grin to describe Bartholomew's dead body. Chapter 6 called Sherlock Homes gives a demonstration. Here we see Homes examining the room and discovering that two people must have committed the murder. A man with a wooden leg would have entered through the window using a rope thrown down by the second person who entered through a hole on the roof. The footprints of the second person were unusually small like those of a child. The dead man is thought to have been poisoned by the thorn which is actually a poisoned dart that was found on his head. Anthony Jones a police detective arrives he comes to a number of false conclusions in his intent on arresting the dais for the murder of his brother. Homes says that he can clear the dais's names as well as Jonathan Small who he names as the wooden legged ex-convict who had been in the room the previous evening and he asks what sent her escort Miss Murray-Morston to her home and then bring back Toby a dog with a good scent and a good way of finding convicts. The key quotations to remember are you see that I'm leaving my way around the dais this is what Anthony Jones says when he's mistakenly assuming that the dais killed his brother. I shall study the great Jones's method this is sarcasm on Holmes's part describing Anthony Jones and the most amazing power of scent. Chapter 7 is called the episode of the barrel now after returning Miss Morston to her home Watson borrows Toby the dog and returns to Pondicherry Lodge. The police detective Jones has arrested not only the dais but most other members of the household giving Watson and Holmes the opportunity to explore the area and possible escape routes for the murderers. Toby smells the creosote that one of the murderers stepped in and they follow the dogs lead throughout the night as he chases a scent across much of South London. During this journey Holmes explains how he knew so much about Jonathan Small who's the wooden legged ex-convict they're pursuing along with his mysterious companion and after some indecision Toby leads them to a large barrel full of creosote. Now the key quotations to remember from this chapter are how small we fill with our petty ambitions and strivings in the presence of the great elemental forces of nature and Toby seems to advance but began to run backward and forward the very picture of canine indecision of course describing Toby the dog who's trying to decipher these smells. Chapter 8 is called the Baker Street Irregulars. Now retracing their steps they once again pick up the trail of the suspects but find it leads them to a riverside landing stage where boats are available for hire. Sherlock Holmes tricks the wife of the owner of one of the boats to reveal that a wooden legged man has been associating with her husband Mordecai Smith and that they are on a steamboat called the Aurora. Returning to Baker Street Holmes and Watson read a newspaper article which praises police detective Jones's single and vigorous masterful mind and his handling of the case in the Baker Street Irregulars a noisy group of street urchins employed by Holmes arrive and he orders them to find the Aurora. Holmes reveals that he knows about Jonathan Small's companion who is an aborigine from the Anderman Islands and the quotations from this chapter are a swift patchering of naked feet upon the stairs a clatter of high voices this of course describes these Baker Street Irregulars and pay attention to the onomatopoeia that's used also the describes his rugged little street Arabs and great agility small poison darts. Chapter 9 is titled A Break in the Chain so in this chapter Watson returns Toby to his owner and goes to see Miss Moreston and her employer Mrs. Forrester relating to them the facts of the case known to him so far. Upon returning to Baker Street the landlady Mrs. Hudson tells him of her concern about Holmes' health as he has been particularly agitated. In the morning Holmes decides to go out to discover the Aurora himself he leaves Watson as his representative at the flat and Watson sees that Holmes has placed an advertisement in the newspaper offering a reward for information to help locate Mordecai Smith and his son Jim. Athene Jones arrives in response to a telegram from Holmes while waiting for Holmes to return an ancient sailor arrives claiming to have knowledge of Mordecai Smith which he refuses to tell anyone but Sherlock Holmes and after being persuaded to remain the sailor removes his disguise and reveals himself to be Sherlock Holmes. He asks Jones to be under my orders when they go to arrest the culprits and says Jones will be welcome to all the official credit and Holmes insists that the three of them have done it together and the quotations remember for chapter 9 are this infernal problem is consuming me and was it not possible that his nimble and speculative mind had built up his wild theory upon 40 premises? Chapter 10 is titled the end of the islander so after dinner the three men set off in a police launch in pursuit of the aurora. Holmes explains that he has realized that Mordecai Smith must have put the boat in with the repairer to hide it while the men made arrangements to escape abroad have indicated the shipyard to follow the aurora as it speeds away the spot Jonathan sport at the stern as was his small companion. When Tonga raises a blowpipe to his lips Holmes and Watson both shoot him and falls into the river trying to escape small jumps off the boat onto the money banks but his wooden leg sinks into the sodden soil. He and the Smiths are captured and Holmes and Watson locate the treasure chest returning to the police launch they notice a murderous dart and realize how close to death they had been and the quotations remember for this chapter are individuals vary but percentages remain constant.  Now chapter 11 is titled The Great Agrar Treasure so the captured small is given a cigar and a drink by Holmes who begins to question him. Small tells the men that their key to the treasure chest is at the bottom of the river. Watson is entrusted to bring the chest to Miss Moreston. He tells her of the adventure they've had and presents her with a treasure chest. Using a poker from the fireplace Watson opens the chest and they discover that it's empty. Without thinking he exclaims thank God. He admits that he loves her and now that her riches are no longer an obstacle he feels that he can declare this. She replies then I say thank God too and Watson draws her close to him. Now the key quotations to remember from this chapter are it seemed to me that there was more sorrow than anger in his rigid and contained countenance and whoever had lost the treasure I knew that night I had gained one. Now the final chapter is chapter 12 and it's called The Strange Story of Jonathan Small. So Small dominates this chapter recounting the events leading up to his imprisonment, his escape and his desire for revenge. He admits that he's thrown the treasure into the Thames since if he couldn't have it he wanted to make sure that no one else did. He tells his story starting with his days in Worcestershire his enlisting in the army and then being posted to India. There through an unfortunate encounter with a crocodile he lost his leg. After a series of adventures he found himself guarding an entrance to a fort where two Sikh gods convinced him to take part in a robbery and murder organised by another Sikh. These became the four in the sign of the four. They hid the treasure but were convicted of the murder. While in prison Small assisted a doctor and learned new skills he also overheard the conversations of the officers and doctor when they were playing card and discovered that Major Sholto was in financial difficulties. He proposed that if Sholto helped Small escape Sholto and his friend Captain Moreston could have a share in the treasure. However it was double crossed when Sholto stole the treasure and returned to England without fulfilling any of his obligation. Small used his skills to save Tonga's life the small aborigine who became his faithful friend and they escaped to England together seeking revenge upon Major Sholto and Small confirms Holmes' version of Sholto's death and is taken away by Jones. Watson confesses that he has proposed to Miss Moreston to Holmes' distinct lack of enthusiasm and the novel ends with Holmes returning to his previous boredom and reaching out for a cocaine bottle and the key quotations to remember from this chapter are we each held a secret which might have put each of us in a palace if we could only have made use of it a fitting wind-up to an extremely interesting case and love is an emotional thing and whatever is emotional as opposed to that true cold reason which I place above all things and of course this is Sherlock Holmes' own words So that's all If you found this video useful make sure you sign up for our Sign of the Fall course where we'll go over the novella its characters, themes but most importantly I'll show you how to write top level 9 model answers for your coursework or exams Thank you so much for listening