These are some of the (small) contributions I made to the Open Source community.
• Lately I've been working a lot with Ansible so these are some roles I created
• In the recent past I also worked with Puppet for which I created some modules
• and contributed to some other projects
• I've also created some Varnish vcl templates
• Varnish 3 Wordpress
• Varnish 4
These are the websites I have created so far.
I have been active in the IT business for 10 years. This means that I have built up a large spectrum of skills and knowledge. This is a list of the skills and experience I have gathered over the years.
• Operating Systems: Debian, Red Hat, CloudLinux, Mac OSX, Windows Server (2003, 2008, 2012)
• Configuration management: Puppet, Chef, Ansible
• Hosting: Amazon AWS, DigitalOcean, Profound knowledge of Belgian hosting providers
• Hosting control panels: Plesk, DirectAdmin
• Virtualisation: VMware ESXi, Xen, Virtuozzo/OpenVZ, Vagrant
• Networking: IPtables, Juniper firewall, Juniper SSL VPN, Barracuda spam filter
• Web servers: Apache, Nginx, Lighttpd, IIS
• Scripting: Bash, PHP(basic), Ruby(basic), HTML
• Database servers: MySQL, MariaDB, PostgreSQL, MongoDB, SQL Server
• Mail servers: Postfix, Sendmail, Exim
• FTP servers: Vsftpd, ProFTPD
• Backup tools: Veeam, Legato networker, Bacula
• Collaboration tools: Git, Gitlab, JIRA, Confluence
• CMS: Wordpress, Drupal, Grav, Magento
• Monitoring and graphing: Nagios, Munin, Cacti, BaseN
• Mac tools: Homebrew, RVM, Chruby, Sublime Text, Alfred, Oh My Zsh
• Other tools and skills: Veewee, Packer, Varnish Cache, Redis, RabbitMQ, SSL, LVM, Asterisk
During my career I have worked on a lot of projects and these are some of the most recent ones I have worked on.
In the first phase of the project at Foto.com I was responsible for creating an inventory of all the servers and services that were being used by the company. Based on that inventory we created and executed the necessary plans to optimize the hardware infrastructure resulting in the downscaling of the used infrastructure.
• Bayer CropScience
My project time at Bayer CropScience consisted of 2 phases. The first phase was aimed at migrating different web-based application platforms (perl, python and apache) to one consolidated environment.
During the second phase I was responsible for the optimisation and migration of the Puppet 2.7 environment to a new Puppet Enterprise 3.3 platform. This meant that I needed to refactor a lot of Puppet modules to be compliant to the new platform. Together with Puppetlabs we also retaught and refactored the entire way Puppet was used at Bayer CropScience.
• Instructor Linux Fundamentals
I presented a course of 1 week named Linux fundamentals to corporate employees looking to improve their general knowledge on Linux.
• Telenet shared Linux hosting platform
During my first months at Telenet I was immediately appointed technical lead of the new Linux hosting platform project. The purpose was to build a new hosting platform where all the basic services such as web-, database- and ftp-services were scalable to our needs.
We also had to keep in mind that we wanted this platform to be reproducible on a smaller scale for our direct customers who also want to provide these services to their customers.
Another important form-factor was the ability to plug in and improve new services on this platform. This is why we built our own API that was standing in between our customers' control panel and our Puppet environment. This gives us great control of all the different aspects of our platform and this also provides enough freedom to extend the functionalities in the future.
Some of the technology-buzzwords we used: Puppet, r10k, MCollective, Ruby, Grape, Swagger, Liquid Templating, CloudLinux, Gitlab,...
• Pinwin.io infrastructure
The pinwin.io project was a startup where I had some direct involvement in and where I got the freedom to help design and build the platform to host the web and mobile applications as well as the APIs and backends. So the entire platform from A to Z.
This platform was built on top of an OpenStack cluster and consisted of one control server that was responsible for the rollout and management of the entire platform by Ansible. So there was no need to log in to each node because every tiny bit of this platform was managed with my self-written Ansible roles and playbooks.
The frontend consisted of 2 webnodes running NodeJS and Supervisord to spin up the NodeJS application. Another webnode was just a basic Nginx with PHP-FPM setup for the control panel for our users. These servers spoke to our API servers also running Nginx with PHP-FPM, Supervisord and Golang. These servers in their part connected to the backend cluster that was running a Redis replication set with Sentinels and a RabbitMQ cluster. We also used MongoDB and Elasticsearch but these were, for the time being, cloud services.
Unfortunately this project never kicked of entirely so this had to be shut down.