-
Story
-
Resolution: Unresolved
-
Blocker
-
None
- The user should have a single page where they can view all the "migrations" that
they have created. - These migrations are represented as groups of pipelines.
- Stateless applications (those with no PVCs as start of the migration), should
only have a single Stateless cutover pipeline. This will differ from a stateful
cutover pipeline because it doesn't require any quescing or state transfer. - For stateful applications, users should have two available pipelines. The
stage pipeline should be repeatable (as a user, I might want to do a stage several
times before a cutover. A repeated stage is effectively a data refresh on the target
as of the source at that time). After a cutover is run, a stage should no longer
be runnable. - The user needs to have a way to monitor high level status and progress of the
pipeline run that's running - The user should be able to drill into a running or completed pipeline to
see more progress. That's probably a link to the pipeline's detail page. - Users need to have a way to delete a group of pipelines, and ensure that
all pipeline runs are also cleaned up.
- blocks
-
-
- Dev Complete
-