Book Image

Native Docker Clustering with Swarm

By : Fabrizio Soppelsa, Chanwit Kaewkasi
Book Image

Native Docker Clustering with Swarm

By: Fabrizio Soppelsa, Chanwit Kaewkasi

Overview of this book

Docker Swarm serves as one of the crucial components of the Docker ecosystem and offers a native solution for you to orchestrate containers. It’s turning out to be one of the preferred choices for Docker clustering thanks to its recent improvements. This book covers Swarm, Swarm Mode, and SwarmKit. It gives you a guided tour on how Swarm works and how to work with Swarm. It describes how to set up local test installations and then moves to huge distributed infrastructures. You will be shown how Swarm works internally, what’s new in Swarmkit, how to automate big Swarm deployments, and how to configure and operate a Swarm cluster on the public and private cloud. This book will teach you how to meet the challenge of deploying massive production-ready applications and a huge number of containers on Swarm. You'll also cover advanced topics that include volumes, scheduling, a Libnetwork deep dive, security, and platform scalability.
Table of Contents (18 chapters)
Native Docker Clustering with Swarm
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Dedication
Preface

Network Control Plane


Network Control Plane is a subsystem of Libnetwork to manage routing information and we need a protocol that converge quickly to do that job. For example, Libnetwork does not use BGP as the protocol (despite that BGP is great at scalability to support very large number of endpoints), because point BGP won't converge quick enough to use in the highly dynamic environment such as the software container environment.

In a container-centric world, the networking system is expected to change very quickly, especially for the new Docker service model, which requires a massive and fast IP assignation. We want the routing information to converge very rapidly as well, especially at a big scale, for example, for more than 10,000 containers. In Swarm2k and Swarm3k experiments, we really did start 10,000 containers at a time. Especially, in Swarm3k, we started 4,000 NGINX containers on the Ingress load-balancing network. Without a fine implementation, this number of scale won't work...