+++ This bug was initially created as a clone of Bug #1510578 +++ Description of problem: When virt and gluster services are running on the same node, there should be an option to configure cgroup/ slice configuration to limit resource consumption by gluster processes Version-Release number of selected component (if applicable): 4.1 How reproducible: NA --- Additional comment from Yaniv Lavi on 2017-11-07 14:55:09 EST --- The default should be the same as in GDeploy. --- Additional comment from SATHEESARAN on 2017-12-04 02:54:33 EST --- This requirement also needs to make sure that the number of cores allocated for gluster processes is customizable at deployment and also at run-time Currently this value is chosen is hard-coded as 400 in gdeploy. To implement it, gdeploy should first provide this flexibility. I have raised a bug[1] for the same in gdeploy [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1411902 --- Additional comment from Yaniv Lavi on 2017-12-04 09:29:55 EST --- (In reply to SATHEESARAN from comment #2) > This requirement also needs to make sure that the number of cores allocated > for gluster processes is customizable at deployment and also at run-time > > Currently this value is chosen is hard-coded as 400 in gdeploy. > To implement it, gdeploy should first provide this flexibility. > > I have raised a bug[1] for the same in gdeploy > > [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1411902 Are you planning to invoke GDeploy from the manager? A design page would be great to have.
Tested with RHV 4.2.3 and glusterfs-3.12. While adding the host to the virt+gluster service enabled cluster, the cgroups for gluster processes are set properly
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:3523