It has been 270 days since my last post, so what I have been doing with my time? Well, I have been busy writing, just not this blog. Not only have I wrote and released Learn Ansible external link, but also I have updated the Second Edition of Mastering Docker external link bringing it up to date with the release of the Third Edition of Mastering Docker external link which is now available from Packt Publishing external link....
I am not sure if this a bug or not, but I spent an hour scratching my head today trying to figure out why part of playbook which was working seemingly suddenly stopped. I have a playbook which executes each morning to create a staging version of a site from the previous night’s snapshots. Each weekday morning at 0730am it … Bootstraps an AWS environment (VPC, ELB and all the other acronyms) Launches a RDS instance from the previous nights snapshot Launches an instances and deploys an application and then creates an AMI Creates an auto-scaling group and launches three instances using the new AMI behind an ELB The base operating system is Red Hat Enterprise Linux 7 which does not ship with any AWS tools installed by default, so before the tasks which start interacting with the instance and application I run the following;...
The two books I wrote about Docker are available for 50% off today from the Packt web site, click here to goto the deal external link.
More and more I am having to not only think about how I would ensure that the infrastructure a service I am deploying on is highly available but also how I can manage its entire life-cycle in code. I have tried several tools for this such as Terraform external link, Puppet and Ansible, however over the last six months or so I have settled on Ansible. After I first looked at it back in December 2014 external link it has come on quite a lot, especially after the version 2 release at the start of this year external link....
Yesterday the following email dropped into my inbox … … I spend a lot of the day job looking at and talking about Amazon Web Services (AWS) so this had got my interest. In my last book external link I covered Amazon’s Elastic Container Service (ECS) and I have to admit that it wasn’t the most greatest service Amazon had released, especially compared the ease you can now launch Swarm Clusters using Docker....
As mentioned a few weeks ago I have been part of the Docker for macOS (as its now known) beta for a while. I didn’t pay much attention to the update last night until I just caught up on the tweets from Docker Con and noticed that they have built in orchestration straight into the core Docker Engine. They said it was there now and it will take no time to run so I decided to give it ago;...
Earlier in the week I wrote about the new Docker Swarm functionality, as i didn’t have much time I was just using the Docker for Mac external link beta. Launching a Swarm cluster To test more of the new features we are going to need a few servers so rather than launching them locally I decided to write an Ansible playbook to launch x number of droplets in Digital Ocean external link. Once the droplets have launched the playbook goes on to perform the following tasks;...
Earlier this week I wanted to show someone a copy of Rancher external link running but I realized that I didn’t have a local lab configured. I managed to quickly launch a few machines in Digital Ocean external link meaning I could do the demo. Rancher is described as being … From the ground up, Rancher was designed to solve all of the critical challenges necessary to run all of your applications in containers....