Creating and aborting jobs

Velostrata defines a job as an operation performed on a group of VMs defined in a runbook. Each operation that a job can run is defined in the migration lifecycle.

Starting a job on a wave

Any job can be started on a wave with a valid runbook.To start a job from the Velostrata Runbook Automation page:

  1. Click Action > New Job.
  2. Select the required operation as described in migration lifecycle.
  3. Click Start.

Aborting a job

In the event of a migration error, you can abort a job, which also aborts the migration wave. To abort a job that is in progress:

  1. Select a row and click the Abort button above the table.
  2. After clicking Abort, the Re-run button appears.
  3. Clicking Re-run continues the wave.

Aborting a job stops Velostrata from continuing whatever process was running, but it does not revert the Velostrata Manager tasks currently running or completed. After resolving issues, you can resume the job at the stage where it was aborted by clicking Re-run.

For example, suppose a wave creates five test clones in five run groups: A, B, C, D, and E. When you click abort, A and B are already running. Those test clone VMs continue to run. Test clones C, D, and E are aborted. When you re-run the operation, A and B continue running, and the operation does not create two new test clones. The wave begins again with a test clone of C, then clones D and E.

What's next?

Was this page helpful? Let us know how we did:

Send feedback about...

Velostrata - Cloud Migration Software for GCP