Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning CoreOS

You're reading from   Learning CoreOS

Arrow left icon
Product type Paperback
Published in Mar 2016
Publisher
ISBN-13 9781785888304
Length 190 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Shantanu Agrawal Shantanu Agrawal
Author Profile Icon Shantanu Agrawal
Shantanu Agrawal
Kingston Smiler. S Kingston Smiler. S
Author Profile Icon Kingston Smiler. S
Kingston Smiler. S
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. CoreOS, Yet Another Linux Distro? FREE CHAPTER 2. Setting Up Your CoreOS Environment 3. Creating Your CoreOS Cluster and Managing the Cluster 4. Managing Services with User-Defined Constraints 5. Discovering Services Running in a Cluster 6. Service Chaining and Networking Across Services 7. Creating a Virtual Tenant Network and Service Chaining Using OVS 8. What Next? Index

CoreOS clustering

Chapter 1, CoreOS, Yet Another Linux Distro covers CoreOS cluster architecture. We will summarize it here again. A CoreOS member or node can contain multiple Docker containers. There can be multiple CoreOS members forming a CoreOS cluster.

CoreOS uses fleet to schedule and manage the services using systemd onto the CoreOS members during initialization. This is similar to the systemd starting and managing service on Linux machines. The scope of the Linux systemd process is limited to a host node, whereas CoreOS fleetd is the init system for a complete CoreOS cluster.

CoreOS uses etcd for node discovery and storing key-value pairs of configuration items accessible across a cluster member.

It's possible to set up a cluster in two ways:

  • etcd running on all members: When the number of members of the cluster is few, then etcd can be run on all the members running the services, also called workers. This configuration is simpler as the same cloud-config can be used to start...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime