Sign In Start Free Trial

OpenStack Essentials

By : Dan Radez

4.2 (14)

OpenStack Essentials

4.2 (14)

By: Dan Radez

Overview of this book

If you need to get started with OpenStack or want to learn more, then this book is your perfect companion. If you're comfortable with the Linux command line, you'll gain confidence in using OpenStack.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Architecture and Component Overview

1. Architecture and Component Overview

OpenStack architecture

Dashboard

Keystone

Glance

Neutron

Nova

Cinder

Swift

Ceilometer

Heat

Summary

2. RDO Installation

2. RDO Installation

Installing RDO using Packstack

Summary

3. Identity Management

3. Identity Management

Services and endpoints

Interacting with Keystone in the dashboard

Endpoints in the dashboard

Summary

4. Image Management

4. Image Management

Glance as a registry of images

Using the web interface

Building an image

Summary

5. Network Management

5. Network Management

Networking and Neutron

Open vSwitch configuration

Creating a network

Web interface management

External network access

Web interface external network setup

Summary

6. Instance Management

6. Instance Management

Managing flavors

Managing key pairs

Launching an instance

Managing floating IP addresses

Managing security groups

Communicating with the instance

Launching an instance using the web interface

Summary

7. Block Storage

7. Block Storage

Use case

Creating and using block storage

Attaching the block storage to an instance

Managing Cinder volumes in the web interface

Backing storage

Summary

8. Object Storage

8. Object Storage

Use case

Architecture of a Swift cluster

Creating and using object storage

Object file management in the web interface

Using object storage on an instance

Ring files

Summary

9. Telemetry

9. Telemetry

Understanding the data store

Definitions of Ceilometer's configuration terms

Graphing the data

Summary

10. Orchestration

10. Orchestration

About orchestration

Writing templates

Launching a stack

Autoscaling instances with Heat

LBaaS setup

Web interface

Summary

11. Scaling Horizontally

11. Scaling Horizontally

Scaling compute nodes

Installing more control and networking

Scaling control and network services

Load-balancing keystone

Glance load balancing

Scaling other services

High availability

Highly available database and message bus

Summary

12. Monitoring

12. Monitoring

Monitoring defined

Installing Nagios

Monitoring methods

Non-OpenStack service checks

Monitoring control services

Monitoring network services

Monitoring compute services

Summary

13. Troubleshooting

13. Troubleshooting

The debug command line option

Tail the server logs

Troubleshooting Keystone and authentication

Troubleshooting Glance image management

Troubleshooting Neutron networking

Troubleshooting Nova launching instances

Troubleshooting post-boot metadata

Troubleshooting console access

Troubleshooting Cinder block storage

Troubleshooting Swift object storage

Troubleshooting Ceilometer Telemetry

Troubleshooting Heat orchestration

Getting more help

Summary

Index

Index

Customer Reviews

4.2 (14)

5 star

64.3%

4 star

14.3%

3 star

0

2 star

21.4%

1 star

0

Graphing the data

Up until now, we have just seen data points flowing through our screen that may or may not be very useful to us. Wouldn't it be nice to make something visual to help display this data? There are plenty of options that could be used to plot this data. As an example, let's take a quick look at gnuplot, which is a command-line program that is packaged with most modern Linux distributions. This book has been using Fedora; to install gnuplot, simply yum install it:

control# yum install -y gnuplot

There are options that need to be fed into gnuplot to tell it how to render the graph that it creates. Let's use a configuration file that will be passed to gnuplot. Put the following content into a file. I'm going to name mine memory.cfg because I will plot the memory usage that's already been aggregated by the Ceilometer statistics command:

#memory.conf
set terminal png truecolor
set output "memory.png"
set autoscale
set xdata time
set timefmt &apos...

Search

Your notes and bookmarks