Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
OpenStack Cloud Computing Cookbook, Third Edition

You're reading from   OpenStack Cloud Computing Cookbook, Third Edition Over 110 effective recipes to help you build and operate OpenStack cloud computing, storage, networking, and automation

Arrow left icon
Product type Paperback
Published in Aug 2015
Publisher
ISBN-13 9781782174783
Length 436 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Cody Bunch Cody Bunch
Author Profile Icon Cody Bunch
Cody Bunch
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Keystone – OpenStack Identity Service 2. Glance – OpenStack Image Service FREE CHAPTER 3. Neutron – OpenStack Networking 4. Nova – OpenStack Compute 5. Swift – OpenStack Object Storage 6. Using OpenStack Object Storage 7. Administering OpenStack Object Storage 8. Cinder – OpenStack Block Storage 9. More OpenStack 10. Using the OpenStack Dashboard 11. Production OpenStack Index

Checking cluster health


We can measure the health of our cluster by using the swift-dispersion-report tool. This is done by checking the set of our distributed containers to ensure that the objects are in their proper places within the cluster.

Getting ready

Ensure you are logged in to the swift-proxy nodes. If you created this node with Vagrant, you can access it by using the following command:

vagrant ssh swift-proxy

How to do it...

Carry out the following steps to set up the swift-dispersion tool to report on cluster health:

  1. We create the configuration file (/etc/swift/dispersion.conf) required by the swift-dispersion tool, as follows:

    [dispersion] 
    auth_url = https://192.168.100.200:5000/v2.0
    auth_user = cookbook:admin
    auth_key = openstack
    auth_version = 2.0
    keystone_api_insecure = yes

    Tip

    We're using keystone_api_insecure in this environment because we are using a self-signed certificate for our keystone endpoint. This skips the validation of the certificate.

  2. Now, we need to create containers...

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
Banner background image