Updating a Notebook Instance

Changing an Image

ModelArts allows you to change images on a notebook instance to flexibly adjust its AI engine. Images can be changed for only stopped notebook instances.

Notes:

• After the image is changed, the notebook instance may fail to be started, as the notebook instance specifications corresponding to the image do not match. The charging rule may also change. Exercise caution when performing this operation.
• When you change the image, data in mounted directories like /home/ma-user/work or /data will not be lost. However, data in non-mounted directories such as /home/ma-user will be erased.

Procedure:

Changing the Specifications of a Notebook Instance

ModelArts allows you to change the node specifications for a notebook instance. Specifications of a notebook instance can be modified only when the notebook instance is in the Stopped, Running, or Startup failed state.

1. Log in to the ModelArts console and perform the following operations as required:
   • New console: Choose Model Build > Notebook.
   • Old console: Choose Development Space > Notebook.
2. Locate the target notebook instance in the list and choose More > Modify Instance Specifications in the Operation column.
3. On the Modify Instance Specifications page, select the target specifications, select I acknowledge the potential risks and agree to proceed with the change, and click OK.

   After the specifications are changed, you can view it in the Instance Specifications column on the notebook page.

   

   The instance specifications can be changed only when there are other options in the cluster. If no other specifications are available, the change cannot be performed.

Configuring Remote SSH Connection for a Notebook Instance

ModelArts allows you to modify the SSH configuration only when the notebook instance is stopped. Remote SSH cannot be disabled once it is enabled.

If remote SSH connection is not configured when you create the notebook instance and you want to enable it after the instance is created, go to the notebook instance details page, and enable SSH configuration. If an IAM user needs to start a notebook instance of another user's, change the key pair.

1. Log in to the ModelArts console and perform the following operations as required:
   • New console: Choose Model Build > Notebook.
   • Old console: Choose Development Space > Notebook.
2. Click the target notebook instance to access its details page. Enable Remote SSH, update the key pair, and click OK.In the Basic Information tab, enable Remote SSH, update the key pair, and click OK.

Setting Node Affinity Scheduling

You can enable, modify, or disable node affinity scheduling only for notebook instances that fail to be stopped or started and whose resource pool type is dedicated resource pool. For details about how to stop a notebook instance, see Starting, Stopping, or Deleting a Notebook Instance.

Enabling node affinity scheduling

1. Log in to the ModelArts console and perform the following operations as required:
   • New console: Choose Model Build > Notebook.
   • Old console: Choose Development Space > Notebook.
2. Enable node affinity scheduling in either of the following ways:
   • Method 1:
     1. On the Notebook page, locate the target notebook instance (stopped or fails to be started), and choose More > Node Affinity Scheduling in the Operation column.
     2. In the displayed dialog box, set the affinity type, strength, and node, and click OK.
        • If Affinity Type is set to Node Affinity and Strength is set to Weak, the system will try to schedule pods to the specified node, however, the scheduling may fail.
        • If Affinity Type is set to Node Affinity and Strength is set to Strong, the system will ensure that the pods are scheduled to the specified node. Otherwise, the pods will not be scheduled.
        • If Affinity Type is set to Node Anti-Affinity and Strength is set to Weak, the system will avoid scheduling pods to the specified node, however, this operation may fail.
        • If Affinity Type is set to Node Anti-Affinity and Strength is set to Strong, the system will ensure that the pods will not be scheduled to the specified node. Otherwise, this operation will not be performed at all. You cannot select all nodes. However, you need to reserve at least one available node. Otherwise, the scheduling policy cannot be executed.
     3. On the Notebook page, click the name of the stopped or failed notebook instance. In the Resource Information area in the Basic Information tab, you can view the node affinity scheduling configuration, indicating that node affinity scheduling has been enabled.
   • Method 2:
     1. On the Notebook page, click the target notebook instance (stopped or fails to be started).
     2. In the Resource Information area in the Basic Information tab, click Enable under Node affinity scheduling. In the displayed dialog box, select the affinity type, strength, and node as required, and click OK.
     3. If the node affinity scheduling configuration is displayed, node affinity scheduling has been enabled.

Modifying node affinity scheduling

1. Log in to the ModelArts console and perform the following operations as required:
   • New console: Choose Model Build > Notebook.
   • Old console: Choose Development Space > Notebook.
2. Modify node affinity scheduling in either of the following ways:
   • Method 1:
     1. In the Operation column on the Notebook page, choose More > Node Affinity Scheduling for the stopped or failed notebook instance.
     2. In the displayed dialog box, click Modify affinity policy, and click OK.
     3. In the Affinity-based Scheduling Policy dialog box, modify the affinity type, strength, or node as required, and click OK.
     4. On the Notebook page, click the target notebook instance (whether stopped or failed to start). In the Basic Information tab, under Resource Information, the latest node affinity scheduling config updates will be shown.
   • Method 2:
     1. On the Notebook page, click the target notebook instance (stopped or fails to be started).
     2. Under the Resource Information area in the Basic Information tab, click under Node affinity scheduling. In the dialog box that appears, click Modify affinity policy and click OK.
     3. In the Affinity-based Scheduling Policy dialog box, modify the affinity type, strength, or node as required, and click OK.
     4. If the updated node affinity scheduling configuration is displayed, the modification is successful.

Disabling node affinity scheduling

After node affinity scheduling is disabled, intelligent scheduling is performed according to system scheduling rules.

1. Log in to the ModelArts console and perform the following operations as required:
   • New console: Choose Model Build > Notebook.
   • Old console: Choose Development Space > Notebook.

1. Disable node affinity scheduling in either of the following ways:
   1. Method 1:
      1. On the Notebook page, locate the target notebook instance that is stopped or fails to be started, and choose More > Node Affinity Scheduling in the Operation column.
      2. In the displayed dialog box, disable node affinity scheduling and click OK. Then, click OK again in the displayed dialog box.
      3. On the Notebook page, locate the target notebook instance (stopped or fails to be started), and choose More > Node Affinity Scheduling in the Operation column. If a message is displayed, indicating that node affinity scheduling is not enabled, disabling node affinity scheduling is successful.
   2. Method 2:
      1. On the Notebook page, click the target notebook instance (stopped or fails to be started).
      2. Under the Resource Information area in the Basic Information tab, click under Node affinity scheduling. In the dialog box that appears, click Disable affinity policy and click OK.
      3. In the displayed dialog box, click OK.
      4. If the Enable button is displayed under Node affinity scheduling, node affinity scheduling has been disabled.

Editing a Tag

You can modify, add, or delete tags of a notebook instance.

1. Log in to the ModelArts console and perform the following operations as required:
   • New console: Choose Model Build > Notebook.
   • Old console: Choose Development Space > Notebook.
2. Edit the tags in either of the following methods:
   1. Method 1: On the Notebook page, locate the notebook instance, hover over in the Tags column, and click Edit Tag.
      Figure 1 Editing a tag
      

   2. Method 2: On the Notebook page, click the name of the target notebook instance. Under the Basic Information area in the Basic Information tab, hover over in the tag area and click Edit Tag.
3. On the Edit Tag panel, modify, add, or delete tags.
   • To modify a tag, change the tag key and value for an existing tag as required, and click OK.
   • To add a tag, click Add Tag, enter or select a tag key, enter a tag value, and click OK. A maximum of 20 tags can be added to a notebook instance.
   • To delete a tag, click Delete on the right of an existing tag and click OK.

   To add the same tag to different cloud resources, use Tag Management Service (TMS) to create predefined tags. For details, see Creating Predefined Tags.

   

   Predefined tags are available to all service resources that support tags. Customized tags are available only to the service resources of the user who has created the tags.

   You can view the modified tags in the Tags column on the Notebook page or in the Basic Information tab of the notebook instance details page.