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
The default should be the same as in GDeploy.
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
(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.
(In reply to Yaniv Lavi from comment #3) > (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. Not gdeploy - but invoking ansible playbook during host-deploy, the same way that it's done for creating firewall rules on hosts
(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 From the engine, CPUQuota is set based on the available cores in the host. Gluster is alloted 1/3rd. Does that meet requirements?
(In reply to Sahina Bose from comment #5) > (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 > > From the engine, CPUQuota is set based on the available cores in the host. > Gluster is alloted 1/3rd. Does that meet requirements? 1/3 is again a statically configured value. It should be made more flexible for user to opt for custom value based on requirement. I will log another RFE to make it flexible for custom value. But this value of 1/3 of cores should be work for now
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
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.