FOSS

Citellus: Detecting common pitfalls of deployments https://github.com/citellusorg/citellus Recording at https://www.youtube.com/watch?v=SDzzqrUdn5A What is Citellus? Citellus is a framework populated by community-contributed scripts that automate detecting problems, including configuration issues, conflicts with package versions, and more. History: how did was it started? The tool, started by Robin Černín after a long weekend shift checking one and over again several sosreports for the same data on different hosts. It started with some tests + shell wrapper, and was added a python wrapper by Pablo Iranzo to bring in more powerful features. ...

Presentation at DevConf.cz 2018! As highlighted in the prior edition of the ‘What’s new’, we got a slot for DevConf.cz 2018. During that slot, my colleagues Martin, Pablo and myself were presenting on the history and basics of Citellus and how it helps on debugging issues and providing faster analysis of already known ones. It is possible to watch the recording at https://www.youtube.com/watch?v=SDzzqrUdn5A and the slides used at: https://github.com/citellusorg/citellus/blob/master/doc/devconfcz2018-presentation-revealmd.md Enjoy! (and if you do, you can Buy Me a Coffee ) ...

What’s new? During recent weeks we’ve been coding and performing several changes to Citellus and Magui. Checking the latest logs or list of issues open and closed on github is probably not an easy task or the best way to get ‘up-to-date’ with changes, so I’ll try to compile a few here. First of all, we’re going to present it at DevConf.cz 2018, so come stop-by if assisting :-) Some of the changes include… ...

Introduction In order to improve Citellus and Magui, we did implement some Unit testing to improve code quality. The tests written were made in python and with some changes it was also possible to validate the actual tests. Also, we did prepare the strings in python using gettext library so the actual messages can be translated to the language of choice (defaults to en, but can be changed via --lang modifier of citellus). ...

Why? While working on Citellus and Magui it soon became evident that Unit testing for validating the changes was a requirement. Initially, using a .travis.yml file contained in the repo and the free service provided by https://travis-ci.org we soon got https://github.com repo providing information about if the builds succeeded or not. When it was decided to move to https://gerrithub.io to work in a more similar way to what is being done in upstream, we improved on the code commenting (peer review), but we lost the ability to run the tests in an automated way until the change was merged into github. ...