Trove replication verify volume size based on master
Bug #1357500 reported by
Iccha Sethi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Undecided
|
Yao Wang |
Bug Description
The slave should have minimum volume same as master. The reason why I think we should be doing this is -
the user builds master with a certain volume size because they expect it to grow atleast that much. so we should make sure the slave has volume size atleast as much as the master.
Changed in trove: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → ongoing |
Changed in trove: | |
assignee: | nobody → Shayne Burgess (shayne-burgess) |
Changed in trove: | |
assignee: | Shayne Burgess (shayne-burgess) → nobody |
status: | In Progress → Confirmed |
Changed in trove: | |
status: | Incomplete → In Progress |
To post a comment you must log in.
Completely agree. Slave storage size should be at least the same as master. That's what i pointed out when i've described 6 cases when replication code will fail. See https:/ /review. openstack. org/#/c/ 98147/23/ trove/instance/ models. py,cm