Until recently I was not able to clearly articulate what DevOps is. Then one day, when trying to describe what we are building at Nirmata to an investor, I said something to the effect of, "its all about enabling developers to perform operations, using automation". That made sense to them; and, I've since started using the following definition for DevOps:
Developers doing Operations using Automation
The Shutl engineering team has been operating with a DevOps mentality for over two years. We started by rebuilding our infrastructure under Chef and embedding our operations engineers into our agile product development process.
We made great progress and saw a big improvement in delivery and quality as all team members were responsible for getting things live and ensuring their long-term maintainability. But… we still had a silo. Only a few of our team were doing the lion’s share of the work when it came to maintaining our infrastructure, and on-call duties were shared by just a small number of people.
Over the past six months, we’ve changed that. So, rather than extol the virtues of this approach – there are plenty of articles doing that! – we thought we’d share some of the steps we took to make every engineer a DevOps engineer.
A simple script to backup Gitlab data. This script will backup the $gitlab_home/tmp/backups of your gitlab installation to a remote host if configured.
During the #vDM30in30 challenge I started playing with Ansible. I was curious about is the ability for Ansible to provision virtual machines to vCenter