Book Image

The DevOps 2.2 Toolkit

By : Viktor Farcic
Book Image

The DevOps 2.2 Toolkit

By: Viktor Farcic

Overview of this book

Building on The DevOps 2.0 Toolkit and The DevOps 2.1 Toolkit: Docker Swarm, Viktor Farcic brings his latest exploration of the Docker technology as he records his journey to explore two new programs, self-adaptive and self-healing systems within Docker. The DevOps 2.2 Toolkit: Self-Sufficient Docker Clusters is the latest book in Viktor Farcic’s series that helps you build a full DevOps Toolkit. This book in the series looks at Docker, the tool designed to make it easier in the creation and running of applications using containers. In this latest entry, Viktor combines theory with a hands-on approach to guide you through the process of creating self-adaptive and self-healing systems. Within this book, Viktor will cover a wide-range of emerging topics, including what exactly self-adaptive and self-healing systems are, how to choose a solution for metrics storage and query, the creation of cluster-wide alerts and what a successful self-sufficient system blueprint looks like. Work with Viktor and dive into the creation of self-adaptive and self-healing systems within Docker.
Table of Contents (18 chapters)

Creating a scaling pipeline

Now comes the exciting part. We're about to start writing a Pipeline job that will serve as the base for the first self-adaptation script.

open "http://$(docker-machine ip swarm-1)/jenkins/newJob"

Once inside the New Job screen, please type service-scale as the item name. Select Pipeline as job type and click the OK button.

Since Jenkins service we created comes with enabled authorization, we need an authentication mechanism for triggering builds. We could use the administrative username and password. A better option is to make a trigger that will be independent of any particular user. That can be accomplished with tokens.

Please select the Trigger builds remotely checkbox from the Build Trigger section of the job configuration screen. Type DevOps22 as the Authentication Token. We'll use it to authenticate remote requests which will...