Trove/use-datastore-version-when-considering-configs
Contents
Description
Trove currently can use different config files for each datastore, but uses the same configs for each datastore version. This blueprint is to add the tiny bit of functionality to allow an operator to optionally use different configs each datastore version.
Justification/Benefits
As versions of a datastore change, it makes sense to offer different config values.
Impacts
Configuration
Today a template is loaded by looking in the path "{manager}/config.template".format(manager=datastore.manager). We can allow for this new functionality by creating instead a list option in the configs which contains different name patterns to look for. Each one will be tried in order to see if there's a match. I propose these defaults:
['{manager}/{version}/{flavor_ram}.config.template', '{manager}/{version}/config.template', '{manager}/config.template']
Database
No impact.
Public API
No impact.
CLI interface
No impact.
ReST Part
No impact.
Internal API
No impact.
RPC API description
No impact.
Guest Agent
No impact.