Bug 1450902

1. Proposed title of this feature request
'ovirt-hosted-engine-setup' should be able to do upgrades from non-hosted-engine setups.

2. see private comment.

3. What is the nature and description of the request?
From existing setups the rhev-engine will most likely be running on a separated machine as VM or even on bare-metal. As the hosted-environment is a common use-case, customers will like to migrate to a hosted-engine environment during the upgrade. This has to be done in a two-step process as of now.

4. Why does the customer need this? (List the business requirements here)
The current process of upgrading to RHV-4.0 requires a fresh installation of a RHEL7 system, as RHEL6 is no longer supported for the engine.
The supported upgrade path are as follows:
* Either the engine is upgraded to 4.0 - which will be on a fresh installed RHEL7 system - followed by the migrating to the self-hosted environment
* Or the engine has to be migrated to a self-hosted environment prior upgrading to RHV-4.0 which will also require an additional step for the hosted-envionment for RHEV-3.6.

As the engine would need to have a backup restored in both scenarios, this additional step should be eliminated.

5. How would the customer like to achieve this? (List the functional requirements here)
One idea would be to extend the functionality of "ovirt-hosted-engine-setup" with an update flag which will then set the relevant options during install or "ovirt-hosted-engine-setup" would read the backup-data from the existing environment and set the options accordingly.


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

- ovirt-hosted-engine-setup --upgrade
  -> o-h-e-s asks for the existing management bridge
  -> o-h-e-s installs the hosted-engine image which is supported for the upgrade (ask previous version?)
  -> o-h-e-s does NOT start engine-setup in case of an upgrade

- ovirt-hosted-engine-setup --upgrade --dbdump=<dump_of_running_rhev>
  -> o-h-e-s inspects dump and finds relevant information from dump
  -> o-h-e-s starts restore of dump
  -> o-h-e-s invokes engine-setup afterwards

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)?
No, but a solution for upcoming RHEV3.6 migrations would be good.

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

10. List any affected packages or components.
ovirt-hosted-engine-setup


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