 Hello. Hi everyone. My name is Mohan Badoo and I work as a Fedora Release Engineer. And obviously, that's the reason why I'm very much interested in raw hide. And as a release engineer, I have to ship a lot of releases. And one of them is raw hide and we ship it out every day, mostly. It's failing for the last two days. So how many of you know raw hide and how many of you are using raw hide as a daily? Wow, at least one. Okay, I'm the other one in this room actually. So I know the problems of raw hide. So let's get started. What is raw hide? It's basically a current development version of Fedora. Everything you build, it just lands in raw hide right away. Well, it takes about a day to get into the riposte. But there is no testing involved. You just build it and it's there. So that's why we fear about raw hide, untested, unstable, unreliable, all the other adjectives that goes with it. And I guess a lot of you people know Ansible, right? How many of you know Ansible and use Ansible? Few people. So, and for the people who don't know Ansible, it's just an automation engine. So basically what it does is it can automate all of your daily tasks and so that it will be taking out a lot of burden for your hands and it provides reliability and scalability. So the way that I solved this problem is basically using Ansible to automate my desktop environment. So how it all started is basically over here last year. I was giving a talk about raw hide and I was using raw hide at the time but not as a daily driver because of the obvious issues. And then I decided I should automate my desktop environment and whenever there is an issue, I can just rerun that Ansible playbook and I have my desktop environment ready. But obviously I want to be on the raw hide because it's the latest and greatest and I can help with Fedora Key with the bugs and reporting them and trying to fix those as well. So that's all it started and all that I'm doing is basically using Ansible playbook to automate my configs and all the packages that I need and other networking stuff and file system related work and I'll just run the playbook. If I cannot get back into raw hide, I'll just install the raw hide and run the playbook and I will have everything ready to get going in like maybe 30 minutes. I just created a demo and it's not showing everything that I automated. It's just a few bits and pieces that I've taken and let's see how it goes. Well, on a VM. And I installed the packages that I needed because obviously network. So basically it's getting my SSH keys and putting in the right directories and on the other power line configs that I use, VM configs that I use, BashRC, everything. Well, a bit of it right now what I'm running. Also cloning my Gitterpose for me. Yes, yes I did. No, basically what I did is right now I just unlocked it but what I did is I used Ansible Vault to encrypt my SSH keys and basically I created this Ansible and put it in my GitHub private repository. And it's done. So it should get a new session and power line things are there and it should have all the packages that kind of maintain and the other packages that I maintain in PyGor. I just picked only one or two. This is just, as I said, it's just a piece and you can automate how much ever you want and you, I want people to be on raw hide so that they can use the things that are coming into Fedora and help us test them and fix them. So this is one way that I solved this but is this the best way? Okay, these are the things I've done in my playbooks like installing packages, configs, network stuff, firewall, gate and some services and file system stuff but is this the best solution? And it's not. The best solution can be is getting raw hide builds so that we have test running so that you won't break your raw hide all the time and raw hide compose test getting so that there will be test running on every compose that we push out and if GreenWeb says it is good, we sync it to the mirrors and there is also plan to add some CR testing on the PRs in this gate whenever that happens. I mean not all of them, all of them. Basically the summary is I want all of you to use raw hide so to do that, automate your work environment setup and keep using raw hide and let us know, bugs, fixes, anything and that's it. Any questions? Yes, yes. I didn't exactly get the question. Yeah, yeah, yeah. How do you force yourself to do it directly on the file and instead change it in the Ansible Playbook? Oh, how do I... So the question is, let's say you want to change something in one of the configs and how do I force myself to update my Ansible repo rather than just changing the file in my local system? Well, I will do it actually when I change something in my local system, I'll just put it on the Git repo as well. I'm forcing myself basically to do it. Interesting, I should try that. Thank you. So the solution was basically use the sim links so that you will always have the content in the Git repo using the sim links to the configs in your local system and whenever you change the sim link, obviously it will be getting affected in the Git repo and you push it whenever you have time. And your question? Yes, silver blue is good and I don't have any problems with silver blue but other than the limitations, like not able to use slash opt and stuff, it's Chrome, sorry. Yes, it is great but that's one of the problems that I see with it but that also does solve some of the issues that you face on a daily basis. Yeah, it is raw. It's still gonna break but you can just roll back if needed. No, basically he can roll back to the previous one, right? Yes. Yes, that will solve all the problems. Any more questions? Probably not. Okay, try raw hide, please. That's all I'm going to say. Please report bugs and try to help us make Fedora even better. Thank you.