Bug 2049863

Summary: 1.7 State Transfer must support a Stage + Migration workflow that can be easily integrated into gitops
Product: Migration Toolkit for Containers Reporter: Erik Nelson <ernelson>
Component: GeneralAssignee: Pranav Gaikwad <pgaikwad>
Status: CLOSED ERRATA QA Contact: Xin jiang <xjiang>
Severity: urgent Docs Contact: Steve Goodman <sgoodman>
Priority: urgent    
Version: 1.7.0CC: ernelson, midays, rjohnson
Target Milestone: ---   
Target Release: 1.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-24 06:32:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Erik Nelson 2022-02-02 20:02:31 UTC 
As of 1.7, migrations have been split into three different migration types:

Intercluster full workload stage and migrate
In-place storageclass conversions
State transfer

With the way that state transfer functions currently, we need to ensure that
the repeated stage + final cutover fits the original use-case cleanly of
integrating state transfser with applications that are managed outside the cluster
by an external CD system.

Imagine you have a workload on the source cluster that is versioned and ready
to be deployed to a target cluster using the gitops flow, but you need a solution
to help you get your state to the target cluster. With 1.7, I should be able
to do the following:

* Run a stage state transfer that gets all of my PVCs to the target namespace
without anything else. This gets the bulk of my data to the target without having
to accept downtime for my source app.

* Run a cutover state transfer that is effectively exactly a stage transfer (i.e.
incremental data transfer into the pvcs that are alrady present on the target
from the inital stage), but it *quiesces the source workloads first*

* I use my CD system to deploy into the namespace with my data waiting for me
in my PVCs

Right now cutover migrations will actually bring over application resources, when
they should only be doing data transfers.
Comment 6 errata-xmlrpc 2022-03-24 06:32:50 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Migration Toolkit for Containers (MTC) 1.7.0 release advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1043