Bug 1426494

Summary: Remove 'poolmetadatasize' from gdeploy config file, so that gdeploy can manipulate the same
Product: [oVirt] cockpit-ovirt Reporter: SATHEESARAN <sasundar>
Component: GdeployAssignee: Ramesh N <rnachimu>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 0.10.7-0.0.10CC: bugs, sabose
Target Milestone: ovirt-4.1.1Flags: rule-engine: ovirt-4.1+
rule-engine: exception+
rule-engine: planning_ack+
rnachimu: devel_ack+
sasundar: testing_ack+
Target Release: 0.10.7-0.0.13   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.10.7-0.0.13 Doc Type: Bug Fix
Doc Text:
'poolmetadatasize' size is defaulted to 16GB in the generated gdeploy configuration. This may not be the right value for smaller disks. Gdeploy computes this value based on the thinpool size, when 'poolmetadatasize' is not specified in the gdeploy config file. So removed this parameter from the generated configuration. If required, user can edit the generated configuration and add this parameter.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-21 09:36:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1277939    

Description SATHEESARAN 2017-02-24 03:08:41 UTC 
Description of problem:
-----------------------
When 'poolmetadatasize' is provided when creating the thinpool, then we need to allocate the space explicitly in addition to the sum of size of LVs.

To avoid this situation, let gdeploy manipulate the size of poolmetadatasize and that removes the space required for poolmetadatasize from the total available size.

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
cockpit-ovirt-dashboard-0.10.7-0.0.11

How reproducible:
-----------------
Often

Steps to Reproduce:
--------------------
1. Provide LVs sizes for 2 LVs

Actual results:
---------------
Thinpool is created with the size which is the sum of sizes of 2 lvs, ignoring the size of 'poolmetadatasize' ( 16GB )

Expected results:
-----------------
thin_pool size = (sum of lv size ) - (poolmetadatasize)

Additional info:
----------------
When 'poolmetadatasize' attribute/key is removed from gdeploy config file, then gdeploy takes the size of thinpool with removing the size of 'poolmetadatasize'
Comment 1 SATHEESARAN 2017-03-08 09:26:56 UTC 
Tested with cockpit-ovirt-0.10.7-0.0.13

'poolmetadatasize' is removed from thinpool creation step