Packt+ | Advance your knowledge in tech

You're reading from The DevOps 2.1 Toolkit: Docker Swarm The next level of building reliable and scalable software unleashed

Product type Paperback

Published in May 2017

Publisher

ISBN-13 9781787289703

Length 436 pages

Edition 1st Edition

Tools

Docker

Concepts

DevOps

Author (1):

Viktor Farcic

View More author details

Table of Contents (17) Chapters

Preface

1. Continuous Integration with Docker Containers FREE CHAPTER

2. Setting Up and Operating a Swarm Cluster

3. Docker Swarm Networking and Reverse Proxy

4. Service Discovery inside a Swarm Cluster

5. Continuous Delivery and Deployment with Docker Containers

6. Automating Continuous Deployment Flow with Jenkins

7. Exploring Docker Remote API

8. Using Docker Stack and Compose YAML Files to Deploy Swarm Services

9. Defining Logging Strategy

10. Collecting Metrics and Monitoring the Cluster

11. Embracing Destruction: Pets versus Cattle

What now?

12. Creating and Managing a Docker Swarm Cluster in Amazon Web Services

13. Creating and Managing a Docker Swarm Cluster in DigitalOcean

14. Creating and Managing Stateful Services in a Swarm Cluster

15. Managing Secrets in Docker Swarm Clusters

16. Monitor Your GitHub Repos with Docker and Prometheus

Docker Swarm Mode

Docker Engine v1.12 was released in July 2016. It is the most significant version since v1.9. Back then, we got Docker networking that, finally, made containers ready for use in clusters. With v1.12, Docker is reinventing itself with a whole new approach to cluster orchestration. Say goodbye to Swarm as a separate container that depends on an external data registry and welcome the new Docker Swarm or Swarm Mode. Everything you'll need to manage your cluster is now incorporated into Docker Engine. Swarm is there. Service discovery is there. Improved networking is there. That does not mean that we do not need additional tools. We do. The major difference is that Docker Engine now incorporates all the "essential" (not to say minimal) tools we need.

The old Swarm (before Docker v1.12) used fire-and-forget principle. We would send a command to Swarm master, and it would execute that command. For example, if we would send it something like docker-compose scale go-demo=5, the old...