Writing about yourself seems to always be challenge but somehow I need to put something on this page. Mainly I created this site as a blog, where I could share with others.

I live in Norwich, UK and I am working for Red Hat (IBM) as part of the OpenStack team.

Nowadays, I do code mostly in Python, Ansible and whatever else it takes to get the things done.

As I do like to give back to the community, I am a core contributor or maintainer in few Python-based open source projects like:

• Ansible related projects:

  • ansible-lint - a project that helps you write better roles and playbooks by checking style and common usage mistakes.
  • ansible molecule and related plugins - playbooks and role testing framework for Ansible that orchestrates virtualized testing resources using local or cloud providers
  • vscode-ansible A new vscode/codium extension that helps people edit Ansible content. It does integrate ansible-lint and a new set of schemas for validating the content and providing auto-complete.
  • ansible-schemas - aims to build JSON Schemas for Ansible. Its primary consumer is the vscode-ansible extension.
  • tox-ansible - Exposes molecule scenarios and ansible-test commands as tox commands, allowing you to use them without having to maintain complex tox.ini config files.
  • pytest-molecule - a small plugin I made that enables pytest to detect and run molecule test scenarios. This precedes tox-ansible which I do recommend now instead of this one. Still, there is a good number of users using it as it has the ability to run multiple scenarios in a single run, something that the other one does not allow yet.

• selinux - a small python shim library that unlocks access to system python selinux bindings when running inside virtual-environments. This library requires the presence of the original selinux binding library to be installed at the system level to work. This is fixing a very common issue people had with use of Ansible from inside such environments.

• Other Python projects:

  • tox-bindep - runs bindep before running tox tests.
  • tox-extra - assure that tox returns an error if tests modify the source code or produce untracked files (git dirty check).
  • cookiecutter - create projects from templates
  • pytest-plus - adds extra functionality to pytest
  • pytest-testinfra - write unit tests in Python which check the actual state of your servers configured by management tools
  • jira - client library and CLI for communicating with JIRA Issue Tracker
  • jenkins-job-builder and python-jenkins - used to automate
  • git-review - the client that eases interaction between git and Gerrit
  • doc8 - style checker for RST
  • hacking - OpenStack blend of flake8 and some plugins that can safely be used to lint projects. The projects is used to control the versions being installed, users still call flake8.

There are also few other projects which I am involved with:

• bashate
• flake8
• pre-commit
• pytest
• pytest-cov
• pytest-html
• pytest-xdist
• tox

I would also recommend few interesting python libraries, listed alphabetically:

• click
• jsonschema
• pydantic
• pyyaml
• rich
• tenacity
• typer
• typeshed

You may also want to check the list of tools I use and occasionally fix a bug or two in those too.

Website timeline

• 2019-12: I decided to migrate to Hugo from GitBook and, at least for the moment use the hugo-theme-pure. The theme has lots of issues but most of them seem solvable.
• 2018: I move from Medium to GitBook.
• ????: I use Jekyll and Git Pages for a while.
• 2008: I opened this blog for posting articles related to software internationalization. It is likely that some of the articles are going to be specific to my native language, Romanian. During the years spend in software internationalization and localization managed to made me see software with many kinds of eyes, I still happily offer my support to those that in need of help in that area. At that time I used WordPress…