The mysql and percona option groups in trove.common.cfg have default settings for backup_strategy and replication_strategy. These options are picked up when placed in trove-guestagent.conf ,
The configuration file does not enable the configuration of strategies at the granularity of datastore + version, however, and this is a problem for datastores such as mysql. E.g. 5.6 should always use GTID while 5.5 may use regular binlogging.
A blueprint is probably necessary to provide the operator a way of configuring datastore and version-specific strategies.
The mysql and percona option groups in trove.common.cfg have default settings for backup_strategy and replication_ strategy. These options are picked up when placed in trove-guestagen t.conf ,
The configuration file does not enable the configuration of strategies at the granularity of datastore + version, however, and this is a problem for datastores such as mysql. E.g. 5.6 should always use GTID while 5.5 may use regular binlogging.
A blueprint is probably necessary to provide the operator a way of configuring datastore and version-specific strategies.