Oracle Cloud Infrastructure Documentation

Creating a Migration Plan - OLVM

Create an OLVM migration plan to test different configurations, compare cost models, and so on

    1. Open the navigation menu  and select Migration & Disaster Recovery. Under Cloud Migrations, select Migrations.
    2. On the Migrations projects list page, select the active migration project for which you want to create a migration plan.
    3. On the migration project details page, select Migration plans, and then select Create migration plan.
    4. In the Basic information section, provide the following information:
      • Enter a display name for the plan, for example, vSphere6.5MigrationPlan2. Avoid entering confidential information.
      • Select the compartment where you want to create the migration plan.
      • Select a target compartment.
    5. For the Target environment step, select the following:
      • Cluster: Select the OLVM cluster from the compartment.
      • VnicProfile: Select the VnicProfile from the compartment.
      • Templates: Select the OLVM template from the compartment.
    6. (Optional) Add tags to organize the resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator.
    7. Select Create migration plan.

  • To create a migration plan, use the create command.

    oci cloud-migrations migration-plan create [OPTIONS]

    The required parameters for the create command are:
    • --compartment-id: Specifies the OCID of the compartment name.
    • --display-name: Specifies the name of the migration project.
    • --migration-id: Specifies the OCID of the associated migration.

    Optional Parameters

    --defined-tags [complex type]

    Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {“foo-namespace”: {“bar-key”: “value”}} This is a complex type whose value must be valid JSON. The value can be provided as a string on the command line or passed in as a file using the file://path/to/file syntax.

    The --generate-param-json-input option can be used to generate an example of the JSON which must be provided. We recommend storing this example in a file, modifying it as needed and then passing it back in via the file:// syntax.

    --freeform-tags [complex type]

    Simple key-value pair that is applied without any predefined name, type or scope. It exists only for cross-compatibility. Example: {“bar-key”: “value”} This is a complex type whose value must be valid JSON. The value can be provided as a string on the command line or passed in as a file using the file://path/to/file syntax.

    The --generate-param-json-input option can be used to generate an example of the JSON which must be provided. We recommend storing this example in a file, modifying it as needed and then passing it back in via the file:// syntax.

    --from-json [text]

    Provide input to this command as a JSON document from a file using the file://path-to/file syntax.

    The --generate-full-command-json-input option can be used to generate a sample json file to be used with this command option. The key names are pre-populated and match the command option names (converted to camelCase format, e.g. compartment-id –> compartmentId), while the values of the keys need to be populated by the user before using the sample file as an input to this command. For any command option that accepts multiple values, the value of the key can be a JSON array.

    Options can still be provided on the command line. If an option exists in both the JSON document and the command line then the command line specified value will be used.

    For examples on usage of this option, see our “using CLI with advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Content/API/SDKDocs/cliusing.htm#AdvancedJSONOptions.

    --max-wait-seconds [integer]

    The maximum time to wait for the work request to reach the state defined by --wait-for-state. Defaults to 1200 seconds.

    --source-migration-plan-id [text]

    Source migration plan ID to be cloned.

    --strategies [complex type]

    List of strategies for the resources to be migrated.

    This option is a JSON list with items of type ResourceAssessmentStrategy. For documentation on ResourceAssessmentStrategy, see our API reference: https://docs.cloud.oracle.com/api/#/en/migration/latest/datatypes/ResourceAssessmentStrategy. This is a complex type whose value must be valid JSON. The value can be provided as a string on the command line or passed in as a file using the file://path/to/file syntax.

    --target-environments [complex type]

    List of target environments.

    This option is a JSON list with items of type TargetEnvironment. For documentation on TargetEnvironment see our API reference:https://docs.cloud.oracle.com/api/#/en/migration/latest/datatypes/TargetEnvironment. This is a complex type whose value must be valid JSON. The value can be provided as a string on the command line or passed in as a file using the file://path/to/file syntax.

    The --generate-param-json-input option can be used to generate an example of the JSON which must be provided. We recommend storing this example in a file, modifying it as needed and then passing it back in via the file:// syntax.

    --wait-for-state [text]

    This operation asynchronously creates, modifies or deletes a resource and uses a work request to track the progress of the operation. Specify this option to perform the action and then wait until the work request reaches a certain state. Multiple states can be specified, returning on the first state. For example, --wait-for-state SUCCEEDED --wait-for-state FAILED would return on whichever lifecycle state is reached first. If timeout is reached, a return code of 2 is returned. For any other error, a return code of 1 is returned.

    Accepted values are:

    ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, NEEDS_ATTENTION, SUCCEEDED, WAITING

    --wait-interval-seconds [integer]

    Check every --wait-interval-seconds to see whether the work request has reached the state defined by --wait-for-state. Defaults to 30 seconds.

    Global Parameters

    Use oci --help for help on global parameters.

    --auth-purpose, --auth, --cert-bundle, --cli-auto-prompt, --cli-rc-file, --config-file, 
--connection-timeout, --debug, --defaults-file, --enable-dual-stack, --endpoint, 
--generate-full-command-json-input, --generate-param-json-input, --help, --interactive-cli-default,
 --latest-version, --max-retries, --no-interactive, --no-retry, --opc-client-request-id, 
--opc-request-id, --output, --profile, --proxy, --query, --raw-output, --read-timeout, 
--realm-specific-endpoint, --region, --release-info, --request-id, --version, -?, -d, -h, -i, -v

    Example using required parameter

    Copy the following CLI commands into a file named example.sh. Run the command by typing “bash example.sh” and replacing the example parameters with your own. Note that this sample will only work in the POSIX-compliant bash-like shell. You need to set up the OCI configuration andappropriate security policies before trying the examples.

    export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/cloud-migrations/migration/create.html#cmdoption-compartment-id
export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/cloud-migrations/migration/create.html#cmdoption-display-name

export migration_id=$(oci cloud-migrations migration create --compartment-id $compartment_id --display-name $display_name --query data.id --raw-output)

oci cloud-migrations migration-plan create --compartment-id $compartment_id --display-name $display_name --migration-id $migration_id

    For a complete list of flags and variable options for CLI commands, see the CLI Command Reference.

  • To create a migration plan, use the CreateMigrationPlan operation.