Book Image

The DevOps 2.1 Toolkit: Docker Swarm

By : Viktor Farcic
Book Image

The DevOps 2.1 Toolkit: Docker Swarm

By: Viktor Farcic

Overview of this book

Viktor Farcic's latest book, The DevOps 2.1 Toolkit: Docker Swarm, takes you deeper into one of the major subjects of his international best seller, The DevOps 2.0 Toolkit, and shows you how to successfully integrate Docker Swarm into your DevOps toolset. Viktor shares with you his expert knowledge in all aspects of building, testing, deploying, and monitoring services inside Docker Swarm clusters. You'll go through all the tools required for running a cluster. You'll travel through the whole process with clusters running locally on a laptop. Once you're confident with that outcome, Viktor shows you how to translate your experience to different hosting providers like AWS, Azure, and DigitalOcean. Viktor has updated his DevOps 2.0 framework in this book to use the latest and greatest features and techniques introduced in Docker. We'll go through many practices and even more tools. While there will be a lot of theory, this is a hands-on book. You won't be able to complete it by reading it on the metro on your way to work. You'll have to read this book while in front of the computer and get your hands dirty.
Table of Contents (22 chapters)
Title Page
Credits
About the Author
www.PacktPub.com
Customer Feedback
Preface
11
Embracing Destruction: Pets versus Cattle

Setting up ElasticSearch as the logging database


As in quite a few cases before, we'll start by creating the already familiar nodes (swarm-1, swarm-2, and swarm-3):

cd cloud-provisioning

git pull

scripts/dm-swarm.sh

Note

All the commands from this chapter are available in the 08-logging.sh (https://gist.github.com/vfarcic/c89b73ebd32dbf8f849531a842739c4d) Gist.

The first service we'll create is Elastic Search (https://hub.docker.com/_/elasticsearch). Since we'll need it to be accessible from a few other services, we'll also create a network called elk:

eval $(docker-machine env swarm-1)

docker network create --driver overlay elk

docker service create \
    --name elasticsearch \
    --network elk \
    --reserve-memory 500m \
    elasticsearch:2.4

After a few moments, the elasticsearch service will be up and running.

We can check the status using the service ps command:

docker service ps elasticsearch

The output is as follows (IDs and ERROR PORTS columns are removed for brevity):

NAMEIMAGENODE...