Managing Notebook Resources

Prerequisites

• Runtime environment
  • You have purchased a notebook resource group. For details, see Managing Notebook Resource Groups.
  • A system image is available. For details about how to view an image, see Managing Images.
• Compute resources
  • You have created an MRS cluster before binding MRS Spark compute resources.
  • You have created a compute resource workspace and endpoint before binding Fabric SQL compute resources.

Notes and Constraints

• Runtime environments
  • You can create a maximum of 10 notebooks in the current workspace.
  • The permissions of preset roles are as follows:
    • If you are the administrator of the current workspace or have the DAYU Administrator or Tenant Administrator permissions, you can create runtime environments owned by yourself and delete, operate, query, and edit all runtime environments in the workspace. To create a runtime environment for another user, you need to create a runtime environment owned by yourself first, and then change the environment owner to the target user.
    • As a developer, you can create, delete, operate, query, and edit runtime environments owned by yourself. However, you cannot modify the runtime environments owned by others.
  • If you are assigned a custom role and have the create permission, you can only create and manage runtime environments owned by yourself. If you have the delete, operate, query, and edit permissions, you can perform the corresponding operations on all runtime environments in the workspace. The query permission is the prerequisite for performing other operations. You cannot delete or edit runtime environments for which you do not have the query permission. You can change the owner of a runtime environment only if you have the edit permission on the environment. For details about how to create a custom role, see (Optional) Defining a Workspace Role.
  • If you are assigned both a preset role and a custom role, you have permissions of both roles.
• Compute resources
  • The permissions of preset roles are as follows:
    • You can bind, unbind, query, and edit compute resources only if you are the workspace administrator or have the DAYU Administrator or Tenant Administrator permissions.
    • As a developer, you can only view compute resources.
    • As an operator, you can view and edit compute resources.
  • If you are assigned a custom role and have the create, delete, query, and edit permissions, you can bind, unbind, query, and edit all compute resources in the workspace. For details about how to create a custom role, see (Optional) Defining a Workspace Role.
  • If you are assigned both a preset role and a custom role, you have permissions of both roles.
  • Only MRS Spark and Fabric SQL resources are supported.
  • To bind an MRS compute engine, you must create an MRS 3.5.1-LTS cluster first. Spark 3.3.1 is supported.

Creating a Runtime Environment

1. Log in to the DataArts Studio console.

   For details, see Accessing the DataArts Studio Instance Console.

2. On the DataArts Studio console, locate a workspace and click Management Center.
3. In the navigation pane on the left, choose Notebook Resources. On the displayed page, click the Notebook Runtime Environment tab.
   Figure 1 Notebook Runtime Environment
   

4. Click Create Runtime Environment and configure the parameters listed in Table 1.

   Table 1 Parameters for creating a runtime environment

   Parameter	Description
   Name	Name of the runtime environment
   Owner	Owner of the runtime environment. The default value is the user who created the environment.
   Resource Group	Resource group to which the notebook belongs. The runtime environment obtains resources from the resource group for executing notebook scripts. If you have not purchased a notebook resource group, purchase one by referring to Managing Notebook Resource Groups.
   Runtime Resource Specifications	Resource specifications for running notebook jobs
   Image	Image. For details about how to view system images, see Managing Images.
   Auto stop	If you select this option, the runtime environment will automatically stop if no operation is performed within the specified period. Enter a value from 1 to 72, in hours. The default value is 1 hour.
   Description (Optional)	Description. A maximum of 1,000 characters are allowed.

5. Click Create.

   After the runtime environment is created, click Enable in the Operation column to activate the notebook job development and runtime environment. Then you can develop notebook jobs in DataArts Factory. For details about how to develop notebook jobs, see Using a Notebook Instance for Online Development and Debugging.

Managing Runtime Environments

• Running a runtime environment: Click Run in the Operation column to enable a runtime environment for notebook job development.
• Stopping a runtime environment: Click Stop in the Operation column to stop a runtime environment for notebook job development.
• Deleting a runtime environment: Click Delete in the Operation column, enter DELETE, and click OK to delete a runtime environment. After a runtime environment is deleted, all the job development scripts created in the environment will also be deleted. Exercise caution when performing this operation.
• Editing a runtime environment: Locate a runtime environment in stopped state and click Edit in the Operation column. You can change the owner of an environment only if you are the current workspace administrator, have the permissions of the DAYU Administrator or Tenant Administrator, or have been assigned a custom role that has the edit permission of the environment.
• Viewing details about a runtime environment: Click the name of a runtime environment to view its details.

Binding or Unbinding a Compute Resource

Binding a Compute Resource

1. Log in to the DataArts Studio console.

   For details, see Accessing the DataArts Studio Instance Console.

2. On the DataArts Studio console, locate a workspace and click Management Center.
3. In the navigation pane on the left, choose Notebook Resources. On the displayed page, click the Compute Resources tab.
   Figure 2 Computing Resources
   

4. Click Bind Compute Resource and configure the parameters listed in Table 2.

   Table 2 Parameters for binding compute resources

   Parameter	Description
   Resource Type	Compute engine for notebook job development. MRS Spark and Fabric SQL are supported.
   Resource Name	Compute resource name
   MRS Cluster	If you select MRS Spark for Resource Type, select an MRS cluster. For details about how to buy a cluster, see Buying MRS Clusters. After the MRS cluster is created, you can view the basic information about the MRS cluster in Active Clusters.
   Compute Resource Workspace	This parameter is mandatory when Fabric SQL is selected for Resource Type. A workspace is the basic unit of Fabric. Select a workspace for Fabric SQL. You can create a resource workspace on the DataArts Fabric console. For details about how to create a workspace, see Creating a Workspace.
   Endpoint	If you select Fabric SQL for Resource Type and select a compute resource workspace, configure an endpoint, which is the compute resource required for running SQL tasks. For details about how to create a SQL endpoint, see Creating a SQL Endpoint.

5. Click OK to bind the compute resource.

Unbinding a Compute Resource

Click Unbind Compute Resource in the Operation column of a compute resource. In the displayed dialog box, enter UNBIND and click OK to unbind the compute resource. After the compute resource is unbound, it can no longer be used for notebook job development. Exercise caution when performing this operation.

Managing Compute Resources

• Editing a compute resource: Click Edit in the Operation column of a compute resource. The resource type cannot be changed.
• Viewing compute resource details: Click the name of a compute resource to view its details.