This January I was at DevConf as speaker. The thing is, this was my first "big" talk in english, and also my first DevConf, so I will try to describe the experience I had there and some of the interesting things I've seen there.
Posts in Fleet Commander
During my stance at Brno I had the pleasure of working with some of the guys at the SPICE team. The goal was to know more in depth how SPICE works and to know how to use the SPICE channels for communicating information in Fleet Commander instead of using our own service for that.
During last 6 months, Alberto Ruiz, Miroslav Chodil and myself have been working on having the 0.8.0 release of Fleet Commander up and working.
Now we finally achieved it, and we released the Fedora packages and also an EPEL7 copr for CentOS and RHEL.
If you want to test it you can do it following the instructions in the Fleet Commander Wiki.
There are some new interesting features in this release. Lets see what is incoming!
Recently I was at GUADEC and had the oportunity to hang out with Cockpit folks in their BoF.
We were talking with Andreas Nilsson and Dominic Perpeet about the design of our cockpit plugin, giving us useful resources and ideas like patterns for visualizing our info and resources like the patterns examples plugins.
Also I sit with Steff Walter for talking about how to use cockpit as a bridge from a websocket to a real tcp socket in our machine and be able to connect to our virtual machines using spice-html5.
When I was migrating Fleet Commander to a cockpit plugin, I had to face a problem with the spice-html5 client we were using to connect to the virtual machines, and It was that the browser was denying some request to Cockpit because of that operations were not specificly allowed.
During this year, I started to migrate the project I'm working on to a Cockpit plugin. Our idea is to convert Fleet Commander Admin into a Cockpit tool plugin. That will allow us to focus on the development of features, leaving the authentication, session management etc. to an already existing application.
First of all let me talk a bit about Fleet Commander and Cockpit:
Fleet commander is intended as a tool to create and deploy user profiles with configuration for applications based on gsettings for Linux. Right now you have an admin web application that allows you to create and deploy the profiles, and a client that has to be installed in the user machines to get, load and apply the profiles intended to your users.
Cockpit is a web application to manage and administer linux servers. In this post I will explain how to create a basic plugin and how to use the Dbus client that comes with Cockpit.