{"id":330,"date":"2016-08-27T20:54:33","date_gmt":"2016-08-27T20:54:33","guid":{"rendered":"https:\/\/rejupillai.com\/?p=330"},"modified":"2021-03-10T15:34:11","modified_gmt":"2021-03-10T15:34:11","slug":"a-date-with-docker-swarm-before-k8s","status":"publish","type":"post","link":"https:\/\/rejupillai.com\/index.php\/2016\/08\/27\/a-date-with-docker-swarm-before-k8s\/","title":{"rendered":"A date with Docker (Swarm) before K8s"},"content":{"rendered":"\n

This post is about Docker <\/strong>(Containers), the notoriously disruptive technology that has taken the software and IT industry by storm last year, and continues to rock the foundation of old-style but most practiced ways of developing and running software.<\/p>\n\n\n\n

Though I was introduced to Docker 2 years back, it was only recently that I started ‘playing’ with it, and I kind of love it. I believe developers can implement amazing use-cases stacking and weaving containers together, the extent of which is only limited by one’s imagination. It’s like creating a cocktail of software and tools that gives you an instant kick, because, with Docker<\/strong>, building, shipping, and running software is incredibly fast and surprisingly light and easy.<\/p>\n\n\n\n

Sometimes it’s just not necessary to know every bit of things under the hood to make your ‘business’ applications run. Docker <\/strong>(images) does this perfectly well. The best part is, it’s just not development. Docker is increasingly becoming popular for production deployments with automated CI\/CD pipelines.<\/p>\n\n\n\n

With PaaS solutions like Cloud-foundry and Stackato (Helion) an HPE product using Docker as the default container and Microsoft, offering both Windows and Linux based container services through it’s Azure Cloud platform,  Docker is all set to play a pivotal role in every enterprise’s IT landscape. In fact, some compare it to what VMware was 10 years back as pioneers in the world of virtualization.<\/p>\n\n\n\n

Some facts and figures of Docker’s rapid adoption can be found here – 8 surprising facts about Docker’s real adoption<\/a><\/p>\n\n\n\n

The playground <\/strong><\/h2>\n\n\n\n

In the world of sleek and slim ultra-books, sometimes having a mobile workstation as a laptop by your side is a very good thing, despite its huge size and friends and colleagues giggling at almost a kilogram of the power adapter, occasionally mistaking it for a home inverter. In hind-sight, a bunch of Ubuntu VMs on any cloud platform would have been just fine for this use case.<\/p>\n\n\n\n

The Use Case<\/strong><\/h2>\n\n\n\n

So I decided to implement a simple use-case to evaluate the 3 fundamental needs of every application – compute, storage and networking, also explore the truth behind Docker‘s<\/strong> tagline build -> ship -> run<\/strong><\/em>. <\/strong>My use case is so common, that it could be easily called the “hello world” of DevOps.<\/p>\n\n\n\n

The plan is simple – A ‘confident’ developer commits a change (as a fix for a bug identified in production), which is propagated through various quality gates and deployed to test (or prod) and made available for customers. In other-words an automated CI\/CD pipeline using containers. Now we all know it’s a far-cry in the real enterprise today, many times because of reasons beyond technical.<\/p>\n\n\n\n

\"No<\/figure>\n\n\n\n

Ingredients for the Cocktail<\/strong><\/h2>\n\n\n\n

 Git-lab (SCM), Jenkins (CI), Sonar (Quality), Nexus (Distribution), Rundeck (CD), Tomcat (Application), a pinch of Swarm and Consul “image” ( for garnish ) all of which can be found here in the Docker Hub Repository<\/a><\/p>\n\n\n\n

From the Docker<\/strong> world, the following tools are used to help realize the use-case.<\/p>\n\n\n\n