Book Image

Learning CoreOS

By : Kingston Smiler. S, Shantanu Agrawal
Book Image

Learning CoreOS

By: Kingston Smiler. S, Shantanu Agrawal

Overview of this book

CoreOS is an open source operating system developed upon the Linux kernel. The rise of CoreOS is directly related to the rise of Docker (a Linux container management system). It is a minimal operating system layer and takes a different approach to automating the deployment of containers. The major difference between CoreOS and other Linux distributions is that CoreOS was designed to deploy hundreds of servers. CoreOS immensely helps the users to create systems, which are easy to scale and manage, making life easier for all, be it developer, QA, or deployer. This book is all about setting up, deploying, and using CoreOS to manage clusters and clouds. It will help you understand what CoreOS is and its benefits as a cloud orchestration platform. First, we’ll show you how to set up a simple CoreOS instance with single node in the cluster and how to run a Docker container inside the CoreOS instance. Next, you’ll be introduced to Fleet and systemd, and will deploy and distribute Docker services across different nodes in cluster using Fleet. Later, you’ll be briefed about running services in a cluster with constraints, publishing the services already running on the cluster to new services, and making your services interact with each other. We conclude by teaching you about advanced container networking. By the end of the book, you will know the salient features of CoreOS and will be able to deploy, administrate, and secure a CoreOS environment.
Table of Contents (15 chapters)
Learning CoreOS
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
Index

Introduction to Flannel/Rudder


Similar to Weave, Flannel also assigns an IP address to a container that can be used for container to container communication by creating an overlay mesh network. Flannel internally uses etcd to store the mapping between the assigned container IP address and host IP address. It doesn't have elaborate features like Weave and can be used if other feature sets provided by Weave are not required. For example, Flannel doesn't provide automatic service discovery through DNS and still requires application coding or instrumentation to discover service endpoints.

By default, each container is assigned an IP address in the /24 subnet. Subnet size can be configured. Flannel uses UDP to encapsulate traffic to transmit to a destination.

In later sections, we will learn about using Flannel. Flannel was previously referred to as Rudder.

Integrating Weave with CoreOSWeave is rather simple to install. The standalone installation is as simple as pulling the Weave script from the...