Description of problem: with the current version of cockpit-ovirt arbiter brick size is set to 10GB. With 10GB arbiter bricks, we can support maximum 10TB bricks with 4MB shards(10TB/4MB *4KB = 10GB). We need to change this and do the size calculation based on the brick size . Discussion points from vijay's email: =================================== There is also a need to accommodate growth of data brick size. Maybe we could use this formula for determining arbiter brick size with Cockpit: min (200 GiB, 2 * (brick-size/shard-size) * 4KB) This uses a multiplicative factor 2 to account for future expansion in data brick size. Version-Release number of selected component (if applicable): cockpit-ovirt-dashboard-0.10.7-0.0.15.el7ev.noarch How reproducible: Steps to Reproduce: 1. create arbiter bricks using cockpit-ovirt 2. 3. Actual results: Arbiter bricks are created with a size of 10GB. Expected results: size of arbiter bricks should be calculated dynamically based on the formula given in the description. Additional info:
Verified with build cockpit-ovirt-dashboard-0.10.7-0.0.18.el7ev.noarch. I see that arbiter brick size is calculated dynamically using the formula max(20GB, 2 * (bricksizeinKB)/shardsizeKB) * 4). When the brick size is 12000GB, arbiter brick size is 24GB.