Oracle Cloud Infrastructure Documentation

Creating a Migration Project

Create a migration project including an initial migration plan and inventory assets.

Before you select the migration wizard option, ensure that inventory is populated with assets from the source environment. The wizard enables you to perform the following tasks:

  • Create a migration project.
  • Configure a replication schedule for the migration project.
  • Create migration assets in the migration project.
  • Create a migration plan.

Creating a Simple Migration Project

Create a migration project and configure replication schedules, create migration assets, and create migration plans later.

    1. Open the navigation menu  and select Migration & Disaster Recovery. Under Cloud Migrations, select Migrations.
    2. On the Migrations projects list page, select Create migration project.
    3. Select Create a simple migration project, and then select Create migration project.
    4. In the Create migration panel, provide the following details:
      • Enter a display name, for example, vSphere6.5Migration. Avoid entering confidential information.
      • Select the compartment where you want to create the migration project.
      • To enable the migration type as OLVM, switch on the OLVM Migration Project toggle.
      • Advanced Options (Optional):
        • Network Configuration (Optional): Under Network configuration select a network configuration to specify a subnet for your Hydration Agent. If you select None, a VCN, subnet, and associated networking resources are created in the tenancy to access the public EBS direct API over the Internet. Fore more information on the requirements, see Hydration Agents for AWS Replication.
        • Tags (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 the administrator.
    5. Select Submit.

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

    oci cloud-migrations migration 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.

    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

    --is-completed [boolean]

    Indicates whether migration is marked as complete.

    --max-wait-seconds [integer]

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

    --migration-type [text]

    Type of migration project (OCI/OLVM). This determines the target environment for the migration.

    --replication-schedule-id [text]

    Replication schedule identifier

    --wait-for-state [text]

    This operation creates, modifies or deletes a resource that has a defined lifecycle state. Specify this option to perform the action and then wait until the resource reaches a given lifecycle 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 1is returned.

    Accepted values are:
    ACTIVE, CREATING, DELETED, DELETING, FAILED, NEEDS_ATTENTION, UPDATING

    --wait-interval-seconds [integer]

    Check every --wait-interval-seconds to see whether the resource has reached the lifecycle 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 and appropriate 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
                            
                            oci cloud-migrations migration create --compartment-id $compartment_id --display-name $display_name

    To get all the commands for migration, run:

    oci cloud-migrations migration -h

    To get help for the create command, run:

    oci cloud-migrations migration create -h

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

  • To create a migration project, use the CreateMigration operation.