Red Hat Bugzilla – Bug 1290866
[RFE][vdsm] document backup solution for vdsm/mom/... for host reinstallation
Last modified: 2017-06-07 14:46:47 EDT
Description of problem:
document backup solution for vdsm/mom/... (for host reinstallation). there is nothing in docs.
(we are in POC to support migration from RHEL 6.x host to RHEL 7.x host, ie. 3.5 vdsm to 3.6 vdsm, and redhat-upgrade-tool does the job. but there could be situations where a customer could choose clean reinstall and then just to restore few mandatory files [vdsm certs for example]. thus it would be nice to have such backup flow documented.)
i was not successful with this (clean reinstall, restore) flow till now :/
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install a host
2. backup some files
3. clean reinstall and restore files
undocumented flow, unknown files list for backup
mandatory hosts files should be documented and flow for clean reinstall, restore should be documented as well and tested
customers can have their own reason why they want to keep old vdsm.id and certs. iiuc 'Reinstall' would regenerate the certs.
(In reply to Jiri Belka from comment #1)
> customers can have their own reason why they want to keep old vdsm.id and
> certs. iiuc 'Reinstall' would regenerate the certs.
The certificates are internal to oVirt, and same as vdsm.id.
The customer shouldn't rely on any of those.
Re-install should make the environment ready to use.
So, not sure what kind of documentation you had in mind.
Dan - do we even support such "backup/restore" for VDSM configuration?
I did not try backup/restore of Vdsm configuration myself (or heard of anyone doing this before), but I see merit in trying it out and listing all files that need update. A user may prefer to recreate an existing host instead of adding a new one. One case mentioned was a host with a big local storage domain.
vdsm.id should clearly be one of the things backed up, as Engine uses the uuid therein as the identifier of the host.
Closing old RFEs.