March 7, 2016

Resizing MySQL Instances and Volumes using OpenStack Trove Database as a Service

Anyone with experience managing databases knows that they often grow over time – requiring additional resources on the machine where the database is running. A common practice is over-provisioning machine resources right from the start though, of course, that could be wasteful.

Here, we’ll show you just how easy it is to re-size a MySQL database running in private cloud DBaaS using the Tesora Database as a Service Platform, which is based on OpenStack Trove.

Step 1: To use OpenStack Trove, first you will need to have Guest Images for each datastore. These images are loaded to OpenStack Glance (where virtual machine images are stored) and registered with Trove. Some guest images for development and testing are available for download from OpenStack at If you’re looking for more information, check out this article, Building a database guest image for OpenStack Trove.

Step 2: Next, using the Tesora DBaaS platform dashboard, log in as the admin user. In our example, let’s say that the MySQL database instance you need to re-size is currently allocated 3 gigabytes. Use the “Actions” pulldown on your database instance and select “Resize Volume”. Simply specify the new amount, for example, let’s say 4 gigabytes and that is it.

Step 3: Next, you can scale up the instance by going back to the “Actions” pulldown on the database instance and this time selecting “Resize Instance”. Use the pulldown to select a larger size. In our example, let’s say the existing database was specified as “Trove Medium” so now we select “Trove Medium Resize”. This automatically changes the memory allocation from 1 gigabyte to 1.3 gigabytes.

To see this in action, we’ve created this “Configuring & Managing MySQL Instances: Resizing Instances and Volumes” video so you can see for yourself how easy it is to re-size existing MySQL database instances using the Tesora DBaaS platform -- database as a service based on OpenStack Trove.

Click Here!