Bug 1702831

Summary:	[Docs] Test and document oVirt to RHV migration
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Marina Kalinin <mkalinin>
Component:	Documentation	Assignee:	Germano Veit Michel <gveitmic>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Novotny <pnovotny>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	amayberr, ctomasko, fgarciad, gveitmic, jwoods, lleistne, logank, lsurette, lsvaty, michal.skrivanek, mtessun, mwest, pelauter, pnovotny, sbonazzo, sfroemer, sgoodman, simon.coter, srevivo, vinicius
Target Milestone:	ovirt-4.4.5	Keywords:	Documentation
Target Release:	4.4.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-19 04:16:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marina Kalinin 2019-04-24 21:45:23 UTC

There is an interest in migrating oVirt environments to RHV, and we would like to have an official procedure tested by QE for this.

At this point it should not be part of any official RHV guide, but a separate knowledgebase article or technical note or a white paper.

We do not intend in this bug to test all possible combinations of oVirt to RHV versions and we assume it is same version on both sides. This is more proof of concept that this procedure works and can be done. 

The procedure should be:
Replace nodes one by one, by reinstalling them with RHVH. 
Reinstall the engine with backup / restore on RHEL.


We can mention another option of importing Data Domain to a brand new RHV environment, but this option has two big disadvantages: (1) VMs downtime; (2) It would not import any configuration settings or third party providers.

Comment 5 Steve Goodman 2019-10-23 07:44:21 UTC

Lukas, please assign someone to this, so I know who to turn to.

Comment 6 Lucie Leistnerova 2019-10-24 09:09:57 UTC

Done.

Comment 16 Steve Goodman 2021-01-10 15:06:07 UTC

I created a draft solution in the knowledge center. 

https://access.redhat.com/solutions/5693941

Moving to QA for verification.

Comment 23 Steve Goodman 2021-01-28 16:43:52 UTC

Let me correct myself from the previous comment: The severity and priority have not dropped.

Nonetheless, the rest of my comment stands.

Comment 25 Steve Goodman 2021-02-02 14:25:36 UTC

Following up on comment 22, I'm reassigning this to Germano, as he has made the most recent edits.

Germano, if you don't want to be the assignee, maybe you can speak with Marina. I think that we've gotten this most of the way. When you feel that it's ready, I would be happy to review it.

This is currently ON_QA, so QE needs to test it.

Comment 26 Germano Veit Michel 2021-02-03 04:54:46 UTC

(In reply to Steve Goodman from comment #25)
> Following up on comment 22, I'm reassigning this to Germano, as he has made
> the most recent edits.
> 
> Germano, if you don't want to be the assignee, maybe you can speak with
> Marina. I think that we've gotten this most of the way. When you feel that
> it's ready, I would be happy to review it.

No problem wrt assignee.

I think the current state is OK, we don't want to be too specific as the steps
are already covered in the Docs (and linked). We just outline the general steps
and give a few hints.

> This is currently ON_QA, so QE needs to test it.
OK.

Comment 27 Marina Kalinin 2021-02-19 04:16:50 UTC

Check the KCS: https://access.redhat.com/solutions/5693941 for solution.