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

Initializing MongoDB replica set through a swarm service


Let's try to define a better and easier way to set up a MongoDB replica set.

We'll start by creating three mongo services. Later on, each will become a member of a Mongo replica set:

for i in123; do
    docker service create --name go-demo-db-rs$i \
        --reserve-memory 100m \
        --network go-demo \
        mongo:3.2.10 mongod --replSet "rs0"

    MEMBERS="$MEMBERS go-demo-db-rs$i"
done

The only difference, when compared with the previous command we used to create mongo services, is the addition of the environment variable MEMBERS. It holds service names of all MongoDBs. We'll use that as the argument for the next service.

Since the official mongo image does not have a mechanism to configure Mongo replica sets, we'll use a custom one. Its purpose will be only to configure Mongo replica sets.

The definition of the image is in the conf/Dockerfile.mongo (https://github.com/vfarcic/cloud-provisioning/blob/master/conf/Dockerfile.mongo...