 Hello, I am Jaromir Vysoglat, I am an intern at Redhead and let me introduce you to a project I am working on which is using locking to collect and store locks from open stacks in locking. You might ask yourself, why do we need to do that? Well, let me first briefly tell you what open stack actually is. It's a cloud operating system which controls pools of bare metal machines, virtual machines and containers. And each of them produces a lot of locks. It would be quite inconvenient if you had to check locks on each of the machines separately. So that's why we collect locks from each individual open stack machine and transport them to common storage. What do we use for that common storage? We use a lock aggregation system called locking, which inspired the name of our project, locking. Let's finally take a look at how all this works and what exactly locking does. On the client side, we use RC's lock on each of the open stack machine to collect its locks and put them on a common bus which transfers them to OpenShift which acts as a server side for our project. On the server side, we use our component called SG Bridge to take the locks from the bus and make them available for locking. Locking parses the locks and sends them to Loki for storage. But what is it good for to just store the locks right? After we store the locks, we can then use tools like Grafana which allows us to query Loki and find exactly the locks that we need. Here you can see I specified the cloud name and the command I want to look at and over here I got exactly what I wanted. And if we connect it to our other project called stf, we can then easily use Grafana to look at corresponding events and metrics for each lock too. So now that I explained you how everything works, let me show you a short demo of the project. Here I configured code ready containers with a QP bus. I also have Loki and running and I have Loki there. And I'm gonna be using this machine instead of OpenStack just to make it a little bit easier. Over here you can see the arsis lock configuration. It's sending locks through the bus to Loki and so let's try to generate some locks. We can do that for example by typing sudo and failing to authenticate and this should send locks to Loki and through that to Loki and we should be able to see them in Grafana. Inside Grafana we can choose the explore option and as you can see I have the Loki and selected and we can query for the locks. I have this machine named as cloud one so let's see what we get. As you can see we get a lot of locks even from only one machine so thankfully we can specify the query and if we search for only sudo we get exactly the locks that we are looking for. I showed you how Loki and works and how it might be used to make viewing OpenStack locks easier. I hope you liked the talk and thank you for your attention.