Category Archives: Uncategorized
“There are many ways to provide for failover and clustered services. One very specific way to achieve high availability that allows for leap-frog releases cycles is blue-green deployments. The idea is to have a mirrored setup where release code runs one one environment and pre-release code runs on the other. This creates an environment that provides rollback, reliability, failover and a host of other capabilities.”
“Blue-green deployment allows you to upgrade production software without downtime. You deploy the new version into a copy of the production environment and change routing to switch.”
Source: BlueGreenDeployment
“Another quick reference card on Continuous Integration Patterns. Automation of builds is not a new practice, why not learn how to consistently describe and develop it.”
Continuous Integration is the process of building software with every change committed to a project’s version control repository. CI can be explained via patterns (i.e., ineffective approaches used to “fix” the specific problem) and anti-patterns associated with the process. This DZone Refcard will walk you through 40 different Patterns and Anti-patterns associated with CI and expands the notion of CI to include concepts such as Deployment and Provisioning. The end result is learning whether you are capable of delivering working software with every source change.
I have never been a big believer in patterns for software development. As I have grown in my understanding of tools and how consistency plays a part in velocity it is becoming more apparent to me that practical/pragmatic patterns are a good thing. Here is one article I have read recently regarding SCM patterns. Not rocket science, but its undeniable the amount of redundant “discovery” taking place when teams believe they are inventing the wheel.
“Software Configuration Management can mean the difference between clarity and confusion in the development cycle. The 16 patterns discussed in this card together serve as potential ways to increase team agility, and they are further enhanced by the inclusion of some general guidelines for improved SCM, as well as a list of useful resources. These patterns are described in further detail in Steve Berczuk’s book, Software Configuration Management Patterns: Effective Teamwork, Practical Integration.”
Source: Software Configuration Management Patterns – DZone – Refcardz
What is BusyBox? The Swiss Army Knife of Embedded Linux Coming in somewhere between 1 and 5 Mb in on-disk size (depending on the variant), BusyBox is a very good ingredient to craft space-efficient distributions. BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however, t
During the creation of the preceding posts on kubernetes, coreos, and docker, I have encountered something called ‘BusyBox’
Many sites assume you know what this is. Let me explain just in case your not entirely sure.
Wouldn’t it be great to have a Linux box that fits inside a single executable and is less than 5mb in size? That’s BusyBox.
The beautiful thing about where we are in container education is we found an even easier and more consistent way to get, use and extend BusyBox… watch carefully…
docker run -it –rm busybox
Thats it – your dropped into a ‘shell’ and can run most linux commands (limited subset of switches for some). It sure beats downloading cygwin for quick and dirty jobs.
CoreOS creates and maintains open source projects for Linux Containers.
Source: CoreOS is Linux for Massive Server Deployments
I have started to experiment with kubernetes in my off time. First things first, I need to know a little more about CoreOS. The folks at CoreOS have made it exceedingly easy to pull the system down and get it running.
Simply change the config.rb to have the number of instances and change the user-data to include a link to the etcd directory where your key value pairs will exist for the cluster, and away you go.
I now have a 3 node CoreOS cluster running inside vagrant/virtualbox. I plan to test out some container distribution to see how quickly one can recover from loss of a system.
If you would like to follow along with me, what you need is VirtualBox and Vagrant to start with and then clone the CoreOS. Tweak the user-data and config file and then “vagrant up” as always.