Laura, i do not think we need to document this for grafton as gdeploy generates the lines required to configure glusterfs slice. [service3] action=start service=glusterd slice_setup=yes
I agree, Kasturi, thankyou. Closing NOTABUG as per Kasturi's comment.
Laura, Apologies that I couldn't provide the information at the right time. This particular information about glusterfs slice and configuring it using gdeploy, should be part of RHGS admin guide, to enable our users to utilize this feature. Probably you could raise a RFE for RHGS-FUTURE and address the requirement
Laura, We need update to the text regarding the value of 'CPUQuota' Currently with gdeploy, there is no flexibility to configure the 'CPUQuota'. By default, gdeploy configures the CPUQuota to the value of 400%. This info should go in to first part of the change, as a note The second part of the change should be in the place which explains the steps for configuring slice. This should include the way to customizing the value for 'CPUQuota' based on requirement Statement for help: ------------------- 'CPUQuota' is the means of applying a CPU limit on all resources running within the glusterfs slice. A value of 400% defines a 4 cores/execution threads limit. Reference --------- Paul's blog - http://blog.gluster.org/2016/09/making-gluster-play-nicely-with-others/
Verified with the doc link. All looks good.
Fixed in RHGS 3.3 documentation.