Bare-metal Continuous Integration and Continuous Deployment with just Docker

I wanted to demonstrate how all pieces fit together in an environment with microservices. That demo is here.

I am going to use Consul, Registrator, HAProxy, Jenkins and all other good stuff. A huge Thank You goes to the folks in the Open Source Community who created the Docker Images and Documentation around them showing how to use them.

If you want to see how the Load Balancer( HAProxy) starts routing traffic to a newly discovered service, I would suggesst going through Consul and Registrator Documentation.

So let’s get started.

Get the Service Discovery Running

Get Consul Running( Change the IP to point to your Docker Host).

Now run the Registrator to create a bridge between your Docker Demon and the Service Discovery.

Run a Sample Application. You can check if it is running by hitting the container directly using cURL.

Run the Load Balancer. It should now route traffic to container hello1. So hit http://52.225.225.230/hello/v1 to check whether you can hit the container through the Load Balancer.

Now run another instance. Keep hitting the same endpoint. Notice the Load Balancer routing requests to your upstream containers in Round- Robin fashion.

Check if Everything is Okay

Consul will be running on http://52.225.225.230:8500/

Test the Load Balancer by hitting hello/v1.

Installing the Docker Registry

Check if the Registry is working.

Verify whether the image is there by using cURL.

Running Jenkins in Docker Outside of Docker( DooD)

Get the initialAdminPassword by logging into the container.

Once Jenkins is installed create a job. In the job execute the some docker command like the one below to check if everything works.

Deploy the Repo by using a Pipeline Job

You might want to modify the Source Code a little before the deployment.

Test your App

Check whether the containers are running. Two containers must be running( Acceptance and Production).

Check whether the Docker Image has been pushed to the Registry.

Hit the Acceptance Endpoint.

Hit the Production Endpoint.

Things you might want to try

Running multiple instances of the Application to see how the Load Balancer behaves
Check how the Load Balancer gets auto- configured when a new instance of an Application starts running by logging into the container( Have a look at haproxy.cfg in /etc/haproxy directory.)
Tag the Docker Image with git hash. I am using latest tag to tag all my images.
Use GitHub Organization so that your new Repositories will be automatically picked up by Jenkins. This is very useful since you can get rid of all the manual configuraions. All your Repository needs is the Jenkinsfile.