====================== RFE TEMPLATE =========================

1. Proposed title of this feature request

RFE for allowing to change the settings globally through the gui for all RHEV-H


3. What is the nature and description of the request?

>Customer wants to open a feature request on being able to push configs to all rhevh machines. Especially in a large environment changing the config on every rhevh machine would be a fairly daunting task. That or allow you to change the settings globally in the gui which would be even better.

 For example: Customer was asked to increase the "migration_max_bandwidth" and "migration_timeout" parameters in "/etc/vdsm/vdsm.conf" file. He came back mentioning the above. 

4. Why does the customer need this? (List the business requirements here)

> Customer Reply: Single location to manage all hypervisors makes deployments in large enviroments much easier, if you have to edit every rhevh machine on by one every time you do an update it makes errors much more likely. Also changing rhevh manually does make it so that its not the "clean room" hypervisor that it is when its a pure install.


5. How would the customer like to achieve this? (List the functional requirements here)

> Customer Reply: The real issue is that migrations can time out when the VM has high usage, (see ticket Case 01022182) we were able to work-around the issue by changing the timeout on the migration while also changing the max bandwidth. As I can assume there is technical reasons for those defaults being able to change them would make it possible to migrate higher usage vm's.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

> No

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

> Customer Reply: Sooner the better :)

9. Is the sales team involved in this request and do they have any additional input?

10. List any affected packages or components.

11. Would the customer be able to assist in testing this functionality if implemented?

> Yes.