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! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
OpenStack Essentials

You're reading from   OpenStack Essentials Demystify the cloud by building your own private OpenStack cloud

Arrow left icon
Product type Paperback
Published in May 2015
Publisher
ISBN-13 9781783987085
Length 182 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Dan Radez Dan Radez
Author Profile Icon Dan Radez
Dan Radez
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

OpenStack Essentials
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Architecture and Component Overview FREE CHAPTER 2. RDO Installation 3. Identity Management 4. Image Management 5. Network Management 6. Instance Management 7. Block Storage 8. Object Storage 9. Telemetry 10. Orchestration 11. Scaling Horizontally 12. Monitoring 13. Troubleshooting Index

Scaling control and network services


When more compute services are added to the cluster, OpenStack's scheduler distributes the new instances appropriately. When new control or network services are added, traffic has to be deliberately sent to them. There isn't anything in OpenStack that handles traffic being distributed across the API services. There is a load-balancing service called HAProxy that can do this for us. HAProxy can be run anywhere it can access the endpoints that you will be balancing. It could go on its own node or it could be put on a node that already has a bit of OpenStack installed on it. Let's put it on the first control node in our example. Start by installing it:

control# yum install -y haproxy

HAProxy has a concept of frontends and backends. The frontends are where HAProxy listens for incoming traffic, and the backends define where the incoming traffic will be sent to and balanced across. Some of the services will need additional configuration beyond HAProxy to be...

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 $15.99/month. Cancel anytime
Visually different images