3. What is the nature and description of the request?
Customer would like the ability to change ALL rhev admin related password(s) without the need to restart the ovirt-engine service
4. Why does the customer need this?
For any admin account used, there should be controlled process for obtaining password, logging use of password, and resetting password after use, such that no human knows the password beyond the period of necessary use.
5. How would the customer like to achieve this?
Cloakware software which stores passwords and has connectors to supply passwords for use and change passwords after use with the ability to allow for scripting of the password change process.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Information on what RH consulting has done to accommodate this can be found in the attached RHEV-Password-Management-v1.9 document (private)
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)?
The cloakware connectors will be implemented in RHEV 3.2 but customer will continue using this when they migrate to 3.4 or 3.5
9. Is the sales team involved in this request and do they have any additional input?
Yes
10. List any affected packages or components.
ovirt-engine
11. Would the customer be able to assist in testing this functionality if implemented?
Yes.