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
OpenStack Cloud Computing Cookbook, Third Edition

You're reading from   OpenStack Cloud Computing Cookbook, Third Edition Over 110 effective recipes to help you build and operate OpenStack cloud computing, storage, networking, and automation

Arrow left icon
Product type Paperback
Published in Aug 2015
Publisher
ISBN-13 9781782174783
Length 436 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Cody Bunch Cody Bunch
Author Profile Icon Cody Bunch
Cody Bunch
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Keystone – OpenStack Identity Service FREE CHAPTER 2. Glance – OpenStack Image Service 3. Neutron – OpenStack Networking 4. Nova – OpenStack Compute 5. Swift – OpenStack Object Storage 6. Using OpenStack Object Storage 7. Administering OpenStack Object Storage 8. Cinder – OpenStack Block Storage 9. More OpenStack 10. Using the OpenStack Dashboard 11. Production OpenStack Index

Introduction


Data written to currently running instances on disks is not persistent—when you terminate such instances, any disk writes will be lost. Volumes are persistent storage that you can attach to your running OpenStack compute instances; the best analogy is that of a USB drive that you can attach to an instance. Similar to USB drives, you can only attach instances to one computer at a time.

In prior OpenStack releases, volume services were provided by nova-volume, which has evolved over time into OpenStack Block Storage; that is, Cinder. OpenStack Block Storage is very similar to Amazon EC2's Elastic Block Storage—the difference is in how volumes are presented to the running instances. In OpenStack compute, volumes can easily be managed using an iSCSI-exposed LVM volume group named cinder-volumes. So, this iSCSI volume group must be present on any host running the Cinder volume service.

At times, managing OpenStack Block Storage can be confusing as Cinder volume is the running service...

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