Search icon CANCEL
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
OpenStack Cloud Computing Cookbook

You're reading from   OpenStack Cloud Computing Cookbook Over 100 practical recipes to help you build and operate OpenStack cloud computing, storage, networking, and automation

Arrow left icon
Product type Paperback
Published in Jan 2018
Publisher Packt
ISBN-13 9781788398763
Length 398 pages
Edition 4th Edition
Languages
Arrow right icon
Authors (4):
Arrow left icon
James Denton James Denton
Author Profile Icon James Denton
James Denton
Egle Sigler Egle Sigler
Author Profile Icon Egle Sigler
Egle Sigler
Cody Bunch Cody Bunch
Author Profile Icon Cody Bunch
Cody Bunch
Kevin Jackson Kevin Jackson
Author Profile Icon Kevin Jackson
Kevin Jackson
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

OpenStack Cloud Computing Cookbook Fourth Edition
Contributors
Preface
Another Book You May Enjoy
1. Installing OpenStack with Ansible FREE CHAPTER 2. The OpenStack Client 3. Keystone – OpenStack Identity Service 4. Neutron – OpenStack Networking 5. Nova – OpenStack Compute 6. Glance – OpenStack Image Service 7. Cinder – OpenStack Block Storage 8. Swift – OpenStack Object Storage 9. OpenStack Orchestration Using Heat and Ansible 10. Using OpenStack Dashboard Index

Configuring volume Quality of Service (QoS)


Another feature provided by Cinder is the ability to define and manage classes of service for volumes. Like volume encryption, Quality of Service (QoS) in Cinder is configured by volume type. By default, you can define values for minimum, maximum, and burst IOPS.

Getting ready

To configure volume QoS, you will need the following information:

  • An openrc file with appropriate credentials for the environment (you need to be an administrator)

  • The openstack command-line client

  • The name or ID of the volume type

  • The consumer of the QoS policy

  • Values for the following:

    • Minimum IOPS

    • Maximum IOPS

    • Burst IOPS

    Note

    Only one of the three (min, max, and burst) needs to be provided to define a minimal QoS policy.

For our example, these will be as follows:

  • Name: High IOPS

  • Consumer: both

  • Maximum IOPS: 500

How to do it…

For Cinder volumes to use QoS, an administrator needs to perform two steps: first, define the specification, and second, to associate the specification with a volume...

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