This is an exercise to highlight some more advanced features of Ansible and using these features in a practical way to build a fully functioning VPC in Amazon EC2, complete with all Elastic IPs, NAT Gateways, security groups and even some instances running in different Availability Zones.
If you have been writing scripts to install and configure things, then this post is for you. Ansible is at it’s heart an automation tool to ease the burden of deploying, configuring and managing your infrastructure, services and associated config. In this short post I will go through some of the basics that will hopefully get you started on your ansible journey.
Following on from the first post a couple of months back I wanted to add a few more advanced workflows to my “how to git” series. In the previous article I talked about git from the perspective of a single developer executing simple changes to a repo and wanting to record that change at github.com.
In this article I want to discuss multiple committers on a single repository and the use of branches.
This is a short and hopefully useful blog post on adding network latency and packet loss to nodes for testing the effect of latency and packet loss in a small local test environment. The post assumes that you already have a set of nodes running in a test environment and focusses introducing simulated latencies and other network phenomena using the unix ‘tc’ tool.