Each database engine, be it MySQL, MongoDB, Percona, and so on, has a default configuration file that the database engine looks for, when starting the service on the guest instance.
The Trove system sends this configuration file using the guest agent (we can see this if we intercept the Prepare message sent in the RabbitMQ queue as shown in the previous chapter). In this section, we will take a look at where Trove stores this information and how we could change it in order to suit our company's needs.
The default configuration that is used by all instances to start up is set in template files. trove.conf
has a configuration option called template_path
that is used to specify the folder where the datastore templates are being stored.
The default value of this in a package install is /etc/trove/templates
. On a DevStack instance that we are running, the default value is trove/templates
in the path where Trove is installed. The full path is /opt/stack...