Trove replication verify volume size based on master

[Iccha Sethi]

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.

[Morgan Jones (6-morgan)]

Space on the master is put to a variety of uses, including holding logs. Slaves don't need those logs, and so may not need as much space as the master.

[Iccha Sethi (iccha-sethi)]

we should have logs on slave too. in case slave is later promoted to master.

[Morgan Jones (6-morgan)]

I understand what you are saying, but I don't think it is right to force 99.999% of users who will not use relay slaves to pay for storage they will never use.

[Morgan Jones (6-morgan)]

Never mind my comment about relay slaves, but it still stands that we can't force users to pay for storage they may never need.

[Peter Stachowski (peterstac)]

Based on discussions at the Trove mid-cycle, this was determined to be better represented by having the slave values default to the master values instead of asserting artificial limits. A new bug has been entered to address that explicitly - https://bugs.launchpad.net/trove/+bug/1359825 - and this bug marked as duplicate.