Add the ability to import a preconfigured Storage Data Domain into RHEV.

2. Who is the customer behind the request?
Account: name (acct #) GSS
TAM customer: yes
SRM customer: yes
Strategic: yes

3. What is the nature and description of the request?
Add the ability to import a preconfigured Storage Data Domain into RHEV.

4. Why does the customer need this? (List the business requirements here)
Scenario I:
There is a big amount of cases where customer looses his RHEV-M environment completely and we need to provide manual instructions to attach the domain to the new RHEV setup or save the VMs on it in other ways. The instructions are complicated and sometimes are not good enough to recover the information. Especially assuming the fact, that we cannot use iSCSI/FC data domain as export domain any more.
Scenario II:
Local storage defined on the host.
There is no way, afaik, to reinstall the host without loosing the information on that domain.
(Maybe this should be a different RFE to recognize preconfigured local storage on new host registration?)

5. How would the customer like to achieve this? (List the functional requirements here)
Add a new option to "Import Domain" dialogue on the Storage Tab on the Admin Portal.
Under "Domain Function / Storage Type" add new option: "Preconfigured Data Domain".
Add a red warning/confirmation message to the user, that this Domain is not in use in any other RHEV setup, otherwise it will make other setup non-operational.
Once confirmed, RHEV would clear the previous SPM status and other relevant information and add this domain to the current setup.

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

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
There is this one: https://bugzilla.redhat.com/show_bug.cgi?id=716511
It is related, but not satisfying enough.
The solution should be simple. And there is not reason not add this RFE to RHEV.

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

9. Is the sales team involved in this request and do they have any additional input?
N/A
10. List any affected packages or components.
several. overall storage team.
11. Would the customer be able to assist in testing this functionality if implemented?
Sure.