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 Administration with Ansible 2

You're reading from   OpenStack Administration with Ansible 2 Automate and monitor administrative tasks

Arrow left icon
Product type Paperback
Published in Dec 2016
Publisher Packt
ISBN-13 9781787121638
Length 230 pages
Edition 2nd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Walter Bentley Walter Bentley
Author Profile Icon Walter Bentley
Walter Bentley
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

OpenStack Administration with Ansible 2 Second Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
1. Introduction to OpenStack FREE CHAPTER 2. Introduction to Ansible 3. Creating Multiple Users/Projects 4. Customizing Your Clouds Quotas 5. Snapshot Your Cloud 6. Migrating Instances 7. Managing Containers on Your Cloud 8. Setting Up Active-Active Regions 9. Inventory Your Cloud 10. Health Check Your Cloud with Nagios

Monitoring the cloud


If allowed I would like to cover some monitoring basics before getting started here. Hopefully, the three principles I will share here are not new to you. When evaluating to monitor something, there are three base principles to keep in mind:

  • Keep it simple

  • Keep your monitoring close to your infrastructure

  • Create good monitors

The first point is pretty easy to absorb, as it is rather self-explanatory. The worst thing you could ever do is over complicate something as important as monitoring. This principle not only applies to your overall approach, but it also applies to the tool you choose to do the monitoring. If you have to create a Visio diagram of your monitoring platform, it is too complicated.

The next point of keeping your monitoring close to your infrastructure is meant to express that the tool used to monitor should physically reside close to the infrastructure/application. The monitoring platform should not have to traverse VPNs or multiple firewalls just to poll...

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