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

Modifying the instance configuration


So, we have seen how the default configuration can be modified. But what about the instances that are already available and running? Can we make configuration changes to those? The answer to this question is very much a yes.

Configuration groups

Let us look at the Trove configuration groups. These technically are some configurations that can be applied on one or more instances. It is to be noted that at any given point in time, only one configuration group can be active.

The steps in using the configuration groups are:

  1. Define the modifiable configuration parameters (in the validation-rules.json file): A copy of validation-rules is provided by default; we can modify it as needed.

  2. Upload the configuration parameters in the Trove system: This is a one-time activity that is done when validation-rules.json is changed.

  3. Create a configuration.

  4. Attach it to one or more instances.

The configuration is synchronized across the instances. This means that, once the configuration...