Managing Notebook Resources

Prerequisites

• Runtime environment
  • You have purchased a notebook resource group. For details, see Managing Notebook Resource Groups.
  • A system image or custom image is available. For details about how to view and create an image, see Managing Images.
• Compute resources
  • You have created an MRS cluster before binding MRS Spark compute resources.
  • You have created a DLI queue and agency before binding DLI 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.
  • You can create and manage all notebook runtime environments only if you are a workspace administrator or developer, or if you have the DAYU Administrator or Tenant Administrator permissions. As a developer, you can only create and manage runtime environments for yourself. As an operator or viewer, you can only view environments.
• Compute resources
  • You can bind, unbind, and edit compute resources only if you are a 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.
  • Only MRS Spark, DLI 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.
  • To bind a DLI compute engine, you must create a DLI queue for general purpose first. Spark 3.3.1 is supported.

Creating a Runtime Environment

1. Log in to the DataArts Studio console by following the instructions in 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. Only the owner has the permission to manage the runtime environment. NOTE: If you are a workspace administrator or have the DAYU Administrator or Tenant Administrator permissions, you can specify an environment owner. If you are a developer, you can only select yourself as the environment owner.
   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	You can select a system image or a custom image. For details about how to view system images and create custom 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. The period ranges from 10 min to 120 min, and is 10 min by default.
   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 to Develop and Debug Code Online.

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.
• 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 by following the instructions in 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, DLI 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.
   DLI Queue	This parameter is mandatory when DLI Spark is selected for Resource Type. In DLI, queues are compute resources.
   Agency	This parameter is mandatory when DLI Spark is selected for Resource Type. You can use the compute resource only after adding an agency. For details about how to create an agency, see Creating a Custom DLI Agency.
   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.