Bug 1523615

Summary:	[RFE][hc][dalton] - Set up cgroup for gluster processes in HC mode from the engine
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Sahina Bose <sabose>
Component:	rhhi	Assignee:	Sahina Bose <sabose>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhhi-1.1	CC:	bugs, rcyriac, rhs-bugs, sasundar
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	RHHI-V 1.5
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Limits are now set on Red Hat Gluster Storage resource usage as part of the deployment process, to ensure that Red Hat Gluster Storage processes do not consume too many resources.	Story Points:	---
Clone Of:	1510578	Environment:
Last Closed:	2018-11-08 05:37:25 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:	1510578
Bug Blocks:	1520833, 1548985

Description Sahina Bose 2017-12-08 11:53:42 UTC

+++ 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.

Comment 3 SATHEESARAN 2018-05-16 07:59:18 UTC

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

Comment 6 errata-xmlrpc 2018-11-08 05:37:25 UTC

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