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
Mastering OpenStack

You're reading from   Mastering OpenStack Design, deploy, and manage a scalable OpenStack infrastructure

Arrow left icon
Product type Paperback
Published in Jul 2015
Publisher
ISBN-13 9781784395643
Length 400 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Omar Khedher Omar Khedher
Author Profile Icon Omar Khedher
Omar Khedher
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Designing OpenStack Cloud Architecture FREE CHAPTER 2. Deploying OpenStack – DevOps and OpenStack Dual Deal 3. Learning OpenStack Clustering – Cloud Controllers and Compute Nodes 4. Learning OpenStack Storage – Deploying the Hybrid Storage Model 5. Implementing OpenStack Networking and Security 6. OpenStack HA and Failover 7. OpenStack Multinode Deployment – Bringing in Production 8. Extending OpenStack – Advanced Networking Features and Deploying Multi-tier Applications 9. Monitoring OpenStack – Ceilometer and Zabbix 10. Keeping Track for Logs – Centralizing Logs with Logstash 11. Tuning OpenStack Performance – Advanced Configuration Index

Choosing the storage

While dealing with the different storage systems within OpenStack, you may wonder which outfit would be the best for your storage solution. Based on our previous discussions, you should proceed into the next stage and discard a few questions and scenarios to validate your choice.

Why should your environment support block storage and why not object storage? Should you rely on the compute nodes to store your persistent storage drives? Alternatively, will the external nodes be more convenient, taking your budget into consideration? What about performance? Do the internal users need only reliable storage? Should they turn a blind eye to its performance capabilities? Do you need real redundant storage to meet the requirements of data-loss scenarios?

As you can see, we throttled a lot of questions. This can be done to a great extent. Does it sound like an investigation series? Let's keep it simple and bring our case under the microscope. Keep in mind that it will be one...

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