Book Image

OpenStack Trove Essentials

By : Alok Shrivastwa, Sunil Sarat, Doug Shelley, Amrith Kumar
Book Image

OpenStack Trove Essentials

By: Alok Shrivastwa, Sunil Sarat, Doug Shelley, Amrith Kumar

Overview of this book

OpenStack has become an extremely popular solution to build public and private clouds with. Database as a Service (DBaaS) enables the delivery of more agile database services at lower costs. Some other benefits of DBaaS are secure database deployments and compliance to standards and best practices. Trove is a DBaaS built on OpenStack and is becoming more popular by the day. Since Trove is one of the most recent projects of OpenStack, DBAs and system administrators can find it difficult to set up and run a DBaaS using OpenStack Trove. This book helps DBAs make that step. We start by introducing you to the concepts of DBaaS and how is it implemented using OpenStack Trove. Following this, we look at implementing OpenStack and deploying Trove. Moving on, you will learn to create guest images to be used with Trove. We then look at how to provision databases in self-service mode, and how to perform administration tasks such as backup and recovery, and fine-tuning databases. At the end of the book, we will examine some advanced features of Trove such as replication.
Table of Contents (15 chapters)
OpenStack Trove Essentials
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
Index

Checking for prerequisites


So, now that we are ready to provision, we need to check that the system has all that it needs to provision a database instance for us.

We will quickly check the following:

  • Flavors available: We can check this by using the command trove flavor-list, which will essentially show us the flavors and the nova instance sizes where the database will be running. We will need this information while launching new Trove instances. We will need the ID from these for whichever flavor we want to launch. The flavors simply show us the flavors defined in the nova subsystem and can also be seen using the nova flavor-list command.

  • Datastore available: This is essentially which image to boot from. We created the MySQL image in the last chapter, so this should be available for us. This can be verified by the command trove datastore-list.

  • Datastore versions available: We will also need to check that at least one datastore version is available for the datastore. We will execute the command...