+++ This bug was initially created as a clone of Bug #1201740 +++ Description of problem: As of now rhsc host-deploy overrides the existing tuned profile on RHS nodes and sets it to rhs-virtualization and because of this the values of vm.dirty_ratio and dirty_background_ratio changes to 5 and 2 and does not remain the RHEL default values 20 and 10. UI should provide an option where user is able to select the profile which he wants to set on the node. Version-Release number of selected component (if applicable): rhsc-3.0.4-1.25.el6rhs.noarch How reproducible: Always. Steps to Reproduce: 1. Install RHS 3.0.4 ISO. 2. Now add the node to rhsc. 3. Actual results: host-deploy overrides the existing profile to rhs-virtualization and because of this vm.dirty_ratio and dirty_background_ratio changes to 5 and 2 and there might be some performance impact because of this. Expected results: Either UI should provide an option where user is able to select the profile which he wants to set on the node. Additional info: --- Additional comment from RHEL Product and Program Management on 2015-03-13 08:02:46 EDT --- Since this issue was entered in bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. --- Additional comment from Rejy M Cyriac on 2015-03-16 07:15:49 EDT --- pm_ack had previously been set for the 'rhs‑future' release flag. Resetting the pm_ack to '?' since release flag has since been changed to 'rhs-3.1.0' --- Additional comment from Pavithra on 2015-03-17 03:21:09 EDT --- Ramesh, Can you please review the edited doc text and clear the needinfo flag? --- Additional comment from Ramesh N on 2015-03-17 05:00:25 EDT --- Doc text looks good to me --- Additional comment from Darshan on 2015-04-02 06:26:47 EDT --- Currently by default rhs-virtualization profile is set for RHS nodes. One approach is to change this default to rhs-high-throughput profile, which is recommended for RHS nodes. The other option is to ask user to choose the profile during cluster creation in RHSC, and set the profile accordingly. --- Additional comment from Darshan on 2015-04-07 06:33:16 EDT --- As discussed in triage meeting, the solution for this issue; User would be provided an option to choose the tuned profile during cluster creation.
Tested with RHEV 3.6.3.3 by adding RHGS 3.1.2 RC node to 3.5 compatible cluster 1. Choosing the tuned profile is available at the cluster level 2. dirty* params are not over-written forcefully when the node was added to the cluster