 Well, my name is Oliver Gutierrez, I've been working for Red Hat Science last year. My main purpose there was to work on this project, Flick Commander, that it's intended to be a tool for deploying configuration profiles for users in big network deployments. So right now, the state of the art is that the large workstation deployments are really a help for the SITS admins. You know, you have to put the machines with their software, the operating system, all the configuration you have for every user in the network, so you have to take care of a lot of things. And right now, for deploying the machines, we have very good tools for configuration management systems like Ansible, Chef, Puppet or whatever. But we didn't have, well, we have some tools for doing this work, but they were very old or maybe they were custom made by the SITS admins. So the thing was we tried to fix the whole thing of deploying the configuration for the users. And our aim with Flick Commander is to make it easy to manage the profiles, to make it easy to add settings for whatever kind of applications you want for that profiles. And I see to deploy them in the network because right now, if you want to do that, you have to load some information from another place with a custom script, write the information in your home directory or whatever. So the idea is to have also a transparent experience for the final user because the final user is sometimes seeing some scripts running here and there or whatever and they notice that it's happening something, but they don't want to take care about that. Yes, they want to do the work. So in the part of making it easy to manage the profiles, we wanted to create a tool that with a graphic session you can create the configuration you want for your profile. For example, the financials profile would want to, for example, have some kind of settings in LibreOffice or whatever tool you want. So we were using Spice, Libre and SSH for technologies for that in a way that you create a template virtual machine with the base configuration of all your network and with that template machine, you have the base for starting to create the profiles you need. So from Flick Commander, the Flick Commander Armin specifically, you can connect using Spice to that virtual machine and just do the configuration graphically and then select the changes you want to use for them. I will go on that later. And for specific configurations like special programs or special things of the operating system like, for example, the highlighted applications, we are using web forms for specifying that because it's easier to do that directly in the interface and not to configure it in the graphic session. Easy to deploy because the idea is to have a minimal installation of software that can be just made to install a package and forget completely about configuring anything. So we just installed that in the client computers. The idea is to make them able to retrieve the profiles without any configuration. So the IT team just install all the computers the same way and the users get the profiles transparently. Well, basically Flick Commander has three parts. One of them is the admin where you create the profiles and you manage them. There is also the logger where its function is basically in the graphic session to lock all the configuration changes you are doing for later selecting the ones you want for the profiles. That's the client that is installed on every computer in your network deployment. Well, more or less is what I have said. The Flick Commander admin is for preferred management and it's web based. Right now it's a copy plugin so you don't have to install another infrastructure for using it. Just you can install it and use it in the usual copy stance you are using for network monitoring. And in the back end part we are using a Divas activities service for using it as a base for... Right now Flick Commander is deploying the profiles using an HTTP server. And that HTTP server is in that service. So we are trying to change that because we are integrating it with free IPA so in later versions it will disappear. The Flick Commander logger basically locks the configuration changes and transfers that changes to the browser for you to be able to select them when you are creating your profiles. It's a piece of software that needs to be installed in the template machine and will be only activated if you are starting that machine from the Flick Commander session. If you install for example it, you means install it in whatever machine it will not be any difference. The Flick Commander client is for all the machines you have in your network and it downloads the profiles but right now when we finish the free IPA integration that will be work free IPA to get the profile information, not Flick Commander one. It compiles all the profiles to generate a final profile because you can have several profiles that apply to the same user and it puts all the configuration changes you want in order to the final configuration that will be applied. Right now the support settings using Flick Commander are in the web interface and the non-software highlighted applications for the non-software tools to highlight several applications that you want to be displayed on the front page. Also the non-line accounts but it is in progress because we have time for passing the changes to the UI so we are on it. The lift session, almost any settings based application is support. Also LibreOffice is support and the network manager you can pre-configure VPN or Wi-Fi or whatever for have that network profiles already installed in the machines you are deploying. Well in future release the idea is to integrate with free IPA. We are almost there so I think maybe in the next, during this year we will end up having that option in Flick Commander and there are several enhancements we can do in the UI and for the user experience so I think this year we will keep that also. Well I wanted to do a short demo so I will try to create a basic profile and also I want to show you how the settings apply to another user so you enter your copied session and here are tools you have Flick Commander as a plugin if you install it you can install it as it is currently in Fedora so you can install it very easily. So here you have to configure the Libre Machine well the Libre Machine that will have the template virtual machine you will be using for creating the settings so I have configured it in localhost in this case localhost I put my username and you have to select if you want the system or the session mode for Libre so I use the session. This is an old setting that will be removed in the future but we needed it for special configurations where the Libre Machine is not the same where you are executing the copied thing so you have to specify the address of that and then I can install the public key for not having to put the password every time I am logging in the virtual machine so I put my password once for installing the public key ok it's installed so right now it is configured I save the configuration and now I can create the profiles for example I will create a test profile that is called test profile and the users that will apply is user for example so I can save it I have my profile here so I can edit it or delete or whatever so in edit this is one of the things we need to enhance in the UX I mean sorry it's very small maybe ok I will try it give me one sec ah ok yeah it's easier yeah you are right it doesn't work yeah I was trying to do it but it's not working I don't know if it is because I have the dialog open neither the here it's ok I think a bit less will be sufficient ok so I can edit the profile so I have these three buttons that are for adding settings to that profile this is one of the things we have to fix in the UX I mean so I can add for example normal line accounts for example the Google account with contacts and file synchronization mail for example or whatever so you have here the list of accounts that applies to that user profile well for this to work we need right now especially built normal line accounts it is in development so I can show you it working but the other things I can so the live session that it's because I am running out of time it's the most impressive one so I can just start the virtual machine session inside the browser this is my template this suppose that all the machines in the network are this type of machine so ok I enter with the user in this case the username doesn't matter in this case because you are creating the profile just that and every time you close this machine the configuration resets to the base template so for example I will open ShotWall and in ShotWall I will set up the background color I will put it completely white so ok so I save this setting and I have a button that is right now here because I did zoom in where I have all the changes that were taking place while I was in the graphic session so I will take this one that is the one I wanted to save to set you also have the LibreOffice changes you can make in this section and also the network manager ones here but for the sake of the talk it's easier just to show one ok so I have created my profile I have set up this setting so the next step is ok all the users logging in in their computers will get that setting well all the users called user will get that setting in the configuration so if I start a virtual machine I have here with the client installed let it boot ok I have the user profile so I enter and I have not configured it to do it automatically I will do it manually but if I execute the fleet commander client terminal and also I will put well I think I have to put the pseudo in front of it ok the fleet commander client executes and it starts to download the profile information from my computer because it is configured in the self computer and checks whether we can write the settings to the former deconf database so as soon as it is execute when I open Shotwell it will be white ok it's ok because usually it's grey well it's more or less this is the idea so if you create several profiles for several users etc. you will have that settings well set up for all the users in your network any questions or whatever this is my first task please be gentle yeah please ok no the idea is that right now we are using all we are ok sorry they are asking me what kind of integration is supposed to be taking place with free IPA so well right now fleet commander you create the profile etc. but you have to deploy it with fleet commander or an HTTP server because the profile information is saved in JSON files ok so our idea is to integrate it with free IPA so you just create the profiles and save them directly in free IPA so it's free IPA the one that is taking care what users apply, what groups apply etc. so SSD that is the other piece of the whole thing will download the profiles that only apply to that user that is logging in at the moment so the idea is to use free IPA for that yeah exactly yeah it makes easier for us to focus on make the effort on preparing the profiles and you know the proper configuration set for the user rather than trying to make to download the information check that is ok or whatever please ok you are asking that how fleet commander manage to the changes to the configuration are made by the users right now we ignored them basically if the user changed the settings ok the settings we have right now in fleet commander are supposed to be forced by the system administrator so if you change anything or whatever if it is set by the administrator it will be rewritten but you know the idea is to make some kind of policy for that in the future but right now the tool is very young you know what I mean any other questions? we have time have you considered Ansible for distribution as alternative for SSSD and IPA for cases where IPA is not used? yes but well it's they are asking that if we are considering for example using Ansible or another tool for deploying the configuration settings well instead of free IP and SSSD well yeah we can use it but the thing is the free IPA is mostly used in large works later on deployment and large environments so we suppose that the fleet commander will be also deployed in that kind of environment so it is easier for us to use a tool that is already there not trying to well that was our first well we were on that first so right now we are trying to finish that and later maybe use another thing please Steph sorry? the fleet commander will be a very high level with one line change okay well the question is the real question the final question is that if we are using BNC or iSPICE we are using SPICE no it's the master branch it's mainly I implemented the part for transferring the the settings using a custom channel and I used the SPICE HTML5 master branch for using it the best thing of using copied in this case is that we can use the route channels for not having to connect to a specific port we can use the same interface used for web sockets for connected really so we get rid of a lot of pieces of software that were you know failing points in that case are there more questions? no? thank you very much I will be around so if you have another question or want to talk to me you know just ping me thank you