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 2. Deploying OpenStack – DevOps and OpenStack Dual Deal FREE CHAPTER 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

Pushing the limits of the database

One of the most critical parts of OpenStack is the database. Usually, MySQL is used when there is no special configuration to prepare specifically for OpenStack to run smoothly and satisfy its multiple services. On the other hand, it becomes pretty tough to maintain your MySQL databases when your cloud keeps growing. Database inconsistency constitutes one of the biggest challenges when running OpenStack in production. For example, it could happen that you have disassociated a network from an instance but the status in the database has not been changed. Nova claims that the network is associated within the instance, while Neutron claims the opposite. In this case, you will have to edit the database manually and change the state in the database. In rare cases, manual intervention can be error-prone. Generally, it is much more difficult to keep consistency when other changes are being performed in a given database table. All of this points to another database...

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