rationalize trove configuration with respect to datastore specific options for incremental backup
Bug #1354959 reported by
Amrith Kumar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Medium
|
Amrith Kumar |
Bug Description
Currently, while backup strategy is datastore specific, it appears that incremental backup strategy is a common option.
This may have been OK when all data stores looked like MySQL. That's not the case any longer.
Changed in trove: | |
assignee: | nobody → Amrith (amrith) |
Changed in trove: | |
importance: | Undecided → Medium |
milestone: | none → juno-3 |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/113155
Review: https:/