Event driven DevOps automation is a concept based around listening for desired events and then performing a task in response. There are a wide variety of applications for the event driven 'cause and effect' relationship in both personal and enterprise environments.

In the home, upon returning  from shopping when your cellphone is detected on the network, you may want your WiFi enabled lights to come on automatically to a desired brightness depending on the time of day.

In the office, when a crucial system's data store is reaching capacity we may want to send an alert and create a Jira ticket to track remediation.

The question remains, how, or what do we use to 'listen' for these events?

Enter, StackStorm.

BitOps works well with different deployment tools and today’s focus is on Terraform. By the end of this you will have used BitOps to create a prod and test AWS VPC.

Depends on who you ask

DevOps is notoriously difficult, even controversial, to define.

Indeed, there are so many definitions of DevOps that if you ask 10 people, “What is DevOps”, you’re likely to get more than 10 answers (opensource.com).

DevOps is a broad concept that covers many areas of expertise, so it might have a different definition depending on a person’s background or point of view.

In this post, we’ll look at a few definitions of DevOps to see if they are actually describing different pieces of the same beast.

BitOps is an open source Docker image created by Bitovi that bundles popular deployment tools with the understanding of what to do with an operations repository. This coupling makes it easier than ever to set up the automated deployment of cloud infrastructure. However, BitOps requires an operations repository to work its magic.

This is part 2 of a BitOps tutorial series:

• Part 1: Introducing BitOps

Defining infrastructure as code repositories to handle complex systems with automated pipelines is difficult to manage at scale. BitOps is a solution to describe your infrastructure and the artifacts deployed onto that infrastructure for multiple environments in a single place called an Operations Repo. It was created and open-sourced by Bitovi.

This is part 1 of a BitOps tutorial series:

• Part 2: BitOps, Yo!