Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: gdeploy should not create thinpool without making sure user is aware of it, and also asking admin for what percentage to extend by, and at what point it should extend. gdeploy should set the values in lvm.conf upon receiving them from admin during installation Additional info: in lvm.conf, # Configuration option activation/thin_pool_autoextend_threshold. # Auto-extend a thin pool when its usage exceeds this percent. # Setting this to 100 disables automatic extension. # The minimum value is 50 (a smaller value is treated as 50.) # Also see thin_pool_autoextend_percent. # Automatic extension requires dmeventd to be monitoring the LV. # # Example # Using 70% autoextend threshold and 20% autoextend size, when a 1G # thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds # 840M, it is extended to 1.44G: # thin_pool_autoextend_threshold = 70 # Configuration option activation/thin_pool_autoextend_percent. # Auto-extending a thin pool adds this percent extra space. # The amount of additional space added to a thin pool is this # percent of its current size. # # Example # Using 70% autoextend threshold and 20% autoextend size, when a 1G # thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds # 840M, it is extended to 1.44G: # thin_pool_autoextend_percent = 20 # Also relevant might be # Using 70% autoextend threshold and 20% autoextend size, when a 1G # snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds # 840M, it is extended to 1.44G: # snapshot_autoextend_threshold = 70 # # Configuration option activation/snapshot_autoextend_percent. # Auto-extending a snapshot adds this percent extra space. # The amount of additional space added to a snapshot is this # percent of its current size. # # Example # Using 70% autoextend threshold and 20% autoextend size, when a 1G # snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds # 840M, it is extended to 1.44G:
(In reply to nikhil from comment #0) > Description of problem: > gdeploy should not create thinpool without making sure user is aware of it, > and also asking admin for what percentage to extend by, and at what point it > should extend. Nikhil, can you elaborate the requirement, I think I am getting you wrong. Below is my understanding. Currently as per the perf recommendation we use the entire disk for the brick and there is no space to extend. Also, gdeploy is non-interactive, and thinpool is created if user provides a configuration and user is aware of it. For example for the below configuration we create a thinpool and once with the below configuration we do not ask for confirmation. ================== [vg1] action=create vgname=RHGS_vg1 pvname=vdb [lv1] action=create vgname=RHGS_vg1 lvname=engine_lv lvtype=thick size=10GB mount=/rhgs/brick1 [lv2] action=create vgname=RHGS_vg1 poolname=lvthinpool lvtype=thinpool poolmetadatasize=10MB chunksize=1024k size=30GB [lv3] action=create lvname=lv_vmaddldisks poolname=lvthinpool vgname=RHGS_vg1 lvtype=thinlv mount=/rhgs/brick2 virtualsize=9GB ============================ I think I am not getting your requirement,
I'm closing this bug since we will not be implementing new features in gdeploy. Please re-open in case of any questions.