Migrating Standard Dedicated Resource Pools and Networks to Other Workspaces

Background

The workspace of a dedicated resource pool is associated with an enterprise project, which involves bill collection. ModelArts provides workspaces to isolate resource operation permissions of different IAM users.

ModelArts allows you to migrate resource pools and networks to a target workspace. Once migrated, the resource pools will be associated with the workspace for you to manage and use. To ensure that resource pools are running properly in the target workspace, migrate the related networks together.

Constraints

• IAM users can only migrate resource pools and networks in their own workspaces.
• The resource pool must be running with no running jobs or tasks. Stop or migrate the running jobs if there are any.
• During the migration, do not perform other operations on the resource pool, such as scaling and job submission. Otherwise, the migration result may be affected.

Migrating the Workspace for a Resource Pool

1. Log in to the ModelArts console. In the navigation pane on the left, choose Standard Cluster under Resource Management.
2. Locate the target resource pool in the list and choose > Migrate Workspace.

   

3. In the displayed dialog box, select the target workspace, enter YES, and click OK.

   Go to the target workspace. In the navigation pane on the left, choose Standard Cluster under Resource Management. If the resource pool is running in the target workspace, the migration is successful.

Migrating the Workspace for a Network

1. Log in to the ModelArts console. In the navigation pane on the left, choose Network under Resource Management.
2. In the network list, choose More > Migrate Workspace in the Operation column of the target network.
3. In the displayed dialog box, select the target workspace and click OK.

   Go to the target workspace. In the navigation pane on the left, choose Network under Resource Management. If the network is available in the target workspace, the migration is successful.

   Figure 1 Migrating the workspace
   

FAQ

What will happen if the resource pool is migrated to another workspace yet the network is not migrated?

• Inconsistent network configurations: The resource pool will still use the network configurations of the original workspace when running in the target workspace. If the network environments of the original and target workspaces are different, the resource pool may fail to connect to the network resources in the target workspace.
• Network access issues: The resource pool may fail to access other resources or services in the target workspace when it is running in the target workspace.
• Security policy conflicts: The target workspace may have different security policies from the original workspace. In this case, the resource pool may fail to meet the new security policy requirements in the target workspace, resulting in restricted access or other security problems.
• Restricted job types: The job types supported by the resource pool, such as training jobs, inference services, and development environments, may depend on specific network configurations. If the network is not migrated, some job types may not run properly.