The current buzz in the industry is how DevOps is changing the world and how the traditional role of operations is changing. Part of these discussions lead to building self-service automation tools which enable developers to actually deploy and support their own code. I want to discuss a little bit about the work I did
So I’ve spent all Labor Day Weekend playing with Deis and I have to say I am very impressed with the concept, but really I am not yet sure it’s ready for my needs yet. However we do plan on engaging with Gabriel so hopefully he can clear up some issues I’ve been having. For those
So I actually started working on a small little dashboard for AWS for another project I am working on in the office; however I decided to fork it and make this into a dashboard which could be used by many other people to get a single view of their AWS environment. Besides that I also
In my current environment (not for this blog lol) I leverage multiple ELBs to provide multi availability zone HA. We also use Zabbix to monitor our EC2 environment (in a previous post I extended the Mikoomi EC2 Zabbix plugin) so I figured I would create a way to have Zabbix alert on outages with backend
I wanted to write a blog post about something that I assume other people might be struggling with when deploying applications to EC2. Specifically how do I tell my deployment scripts (fabric in my case) to wait until puppet has finished before moving on to actually deploying my application.