Description of problem: Current efforts rely on existing tools, see [1]. It seems we need a tool to assist this migration. This tool, let's say it will be called 'engine-migrate', will have two modes: * engine-migrate --mode=source To be done on the source machine. Will stop the engine, run backup, prevent the engine from running accidentally (e.g. disable the service, touch some file that will tell the engine service to not start, etc) * engine-migrate --mode=target To be done on the target machine after copying the backup file. Will run restore, engine-setup, other fixes that are (currently?) not done by engine-setup. It's not hosted-engine specific - it can be used whenever someone wants to move an engine between machines. [1] http://www.ovirt.org/Migrate_to_Hosted_Engine
Didi, for 3.3.0 release note and/or message to the user are good enough. For 3.4 we need the proper tool. So updating this bz for 3.4, and please make sure to have something done for 3.3.0.
Currently closing. 'engine-backup --mode=restore && engine-setup' should be good enough. Please reopen if needed. Note that it's probably not specific to hosted-engine but relevant to any migration.