Create config value for replication backup strategy
Bug #1359387 reported by
Iccha Sethi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Triaged
|
Medium
|
Doug Shelley | ||
Bug Description
Create config value for replication backup strategy
| Changed in trove: | |
| assignee: | nobody → Peter Stachowski (peterstac) |
| Changed in trove: | |
| importance: | Undecided → Medium |
| milestone: | none → ongoing |
| status: | New → Triaged |
| Changed in trove: | |
| assignee: | Peter Stachowski (peterstac) → Alex Tomic (atomic777) |
Revision history for this message
| Alex Tomic (atomic777) wrote | #1 |
| Changed in trove: | |
| assignee: | Alex Tomic (atomic777) → Doug Shelley (0-doug) |
To post a comment you must log in.
The mysql and percona option groups in trove.common.cfg have default settings for backup_strategy and replication_
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.