[ovirt-users] SHE upgrade from 4.3 to 4.4 doubts

Hello, I would like to get some clarifications about the SHE environment upgrade from 4.3.10 to 4.4.4. Example scenario two hosts, both configured as HE hosts. Interested both in iSCSI environment and in FC environment. Going through here: https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_the_Manager_... I have some doubts: 1) general one between step 5 and 6 in section 4.4, actually the current 4.3 engine VM is still running its OS (even if with ovirt-engine service stopped) and the VM is running on the host you are going to scratch. So I think before scratching the host and reinstalling it (step 6), it should be clarified some step like - shutdown engine VM - shutdown host (is it ok in clean way or do I have to simply power off it....?) - install from scratch ovirt-ng node 4.4.4 on host 2) general one why in external engine upgrade guide it is not specified to stop ovirt-engine service before executing the backup, while in SHE it is specified? See steps on section 2.3 here: https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 expected different behaviour? Or any change needed in the doc? 3) SHE when iSCSI and FC It is clear that one new domain is to be provided, intended for the new engine 4.4 VM It is clear that during install of the new host in 4.4 it is safe to have shared LUNs masked / not accessible so that you don't risk to corrupt current 4.3 data It is not clear in my opinion what to do before running the step 8 of 4.4 section: hosted-engine --deploy --restore-from-file=backup.bck a) iSCSI in general the configured iSCSI sessions are activated only when the host is being activated. So for example when you put host into maintenance, they are logged off. In this stage of upgrade what is expected I execute before running the hosted-engine --deploy command? Will the command log in into iSCSI sessions during itsmexecution (because of the restore) or do I have to create / log in the connections before running it? b) FC what should I have on host before running the command? Only the current LUns (+ the new one intended for new hosted engine VM) visible, so that I see all of them as output of "multipath -l" command and then the hosted-engine --deploy command would mount the related filesystems and so on..? Possibly it would be nice to have an example output of the hosted-engine --deploy --restore-from-file=backup.bck command inside the doc page.... to see its expected workflow Thanks for reading, Gianluca