Procedure

1. Log in to the OpenShift console as a cluster administrator.
2. In the Administrator perspective, click Home → API Explorer.
3. In the search bar, enter OdhDashboardConfig to filter by kind.
4. Click the OdhDashboardConfig custom resource (CR) to open the resource details page.
5. Select the redhat-ods-applications project from the Project list.
6. Click the Instances tab.
7. Click the odh-dashboard-config instance to open the details page.

8. Click the YAML tab. Here is an example OdhDashboardConfig file showing default values:

   apiVersion: opendatahub.io/v1alpha
   kind: OdhDashboardConfig
   metadata:
     name: odh-dashboard-config
   spec:
     dashboardConfig:
       enablement: true
       disableBYONImageStream: false
       disableClusterManager: false
       disableISVBadges: false
       disableInfo: false
       disableSupport: false
       disableTracking: true
       disableProjects: true
       disablePipelines: true
       disableModelServing: true
       disableProjectSharing: true
       disableCustomServingRuntimes: false
       disableAcceleratorProfiles: true
       modelMetricsNamespace: ''
       disablePerformanceMetrics: false
     notebookController:
       enabled: true
     notebookSizes:
       - name: Small
         resources:
           limits:
             cpu: '2'
             memory: 2Gi
           requests:
             cpu: '1'
             memory: 1Gi
       - name: Medium
         resources:
           limits:
             cpu: '4'
             memory: 4Gi
           requests:
             cpu: '2'
             memory: 2Gi
       - name: Large
         resources:
           limits:
             cpu: '8'
             memory: 8Gi
           requests:
             cpu: '4'
             memory: 4Gi
     modelServerSizes:
       - name: Small
         resources:
           limits:
             cpu: '2'
             memory: 8Gi
           requests:
             cpu: '1'
             memory: 4Gi
       - name: Medium
         resources:
           limits:
             cpu: '8'
             memory: 10Gi
           requests:
             cpu: '4'
             memory: 8Gi
       - name: Large
         resources:
           limits:
             cpu: '10'
             memory: 20Gi
           requests:
             cpu: '6'
             memory: 16Gi
     groupsConfig:
       adminGroups: 'odh-admins'
       allowedGroups: 'system:authenticated'
     templateOrder:
       - 'ovms'
     templateDisablement:
       - 'ovms'

9. Edit the values of the options that you want to change.
10. Click Save to apply your changes and then click Reload to make sure that your changes are synced to the cluster.

Procedure

1. Log in to the OpenShift console as a cluster administrator.
2. In the Administrator perspective, click Home → API Explorer.
3. On the API Explorer page, search for the OdhApplication kind.
4. Click the OdhApplication kind to open the resource details page.
5. On the OdhApplication details page, select the redhat-ods-applications project from the Project list.
6. Click the Instances tab.
7. Click Create OdhApplication.

8. On the Create OdhApplication page, copy the following code and paste it into the YAML editor.

   apiVersion: dashboard.opendatahub.io/v1
   kind: OdhApplication
   metadata:
     name: examplename
     namespace: redhat-ods-applications
     labels:
       app: odh-dashboard
       app.kubernetes.io/part-of: odh-dashboard
   spec:
     enable:
       validationConfigMap: examplename-enable
     img: >-
       <svg width="24" height="25" viewBox="0 0 24 25" fill="none" xmlns="http://www.w3.org/2000/svg">
       <path d="path data" fill="#ee0000"/>
       </svg>
     getStartedLink: 'https://example.org/docs/quickstart.html'
     route: exampleroutename
     routeNamespace: examplenamespace
     displayName: Example Name
     kfdefApplications: []
     support: third party support
     csvName: ''
     provider: example
     docsLink: 'https://example.org/docs/index.html'
     quickStart: ''
     getStartedMarkDown: >-
       # Example
   
       Enter text for the information panel.
   
     description: >-
       Enter summary text for the tile.
     category: Self-managed | Partner managed | {org-name} managed

9. Modify the parameters in the code for your application.

   Tip

   To see example YAML files, click Home → API Explorer, select OdhApplication, click the Instances tab, select an instance, and then click the YAML tab.

10. Click Create. The application details page appears.
11. Log in to OpenShift AI.
12. In the left menu, click Applications → Explore.
13. Locate the new tile for your application and click it.
14. In the information pane for the application, click Enable.

Procedure

1. Log in to the OpenShift console as a cluster administrator.

2. Open the dashboard configuration file:

   1. In the Administrator perspective, click Home → API Explorer.
   2. In the search bar, enter OdhDashboardConfig to filter by kind.
   3. Click the OdhDashboardConfig custom resource (CR) to open the resource details page.
   4. Select the redhat-ods-applications project from the Project list.
   5. Click the Instances tab.
   6. Click the odh-dashboard-config instance to open the details page.
   7. Click the YAML tab.
3. In the spec:dashboardConfig section, set the value of enablement to false to disable the ability for dashboard users to add applications to the dashboard.
4. Click Save to apply your changes and then click Reload to make sure that your changes are synced to the cluster.

Procedure

1. Log in to the OpenShift console as a cluster administrator.
2. In the Administrator perspective, click Home → API Explorer.
3. On the API Explorer page, search for the OdhApplication kind.
4. Click the OdhApplication kind to open the resource details page.
5. On the OdhApplication details page, select the redhat-ods-applications project from the Project list.
6. Click the Instances tab.
7. Click Create OdhApplication.

8. On the Create OdhApplication page, copy the following code and paste it into the YAML editor.

   apiVersion: dashboard.opendatahub.io/v1
   kind: OdhApplication
   metadata:
     name: examplename
     namespace: redhat-ods-applications
     labels:
       app: odh-dashboard
       app.kubernetes.io/part-of: odh-dashboard
   spec:
     enable:
       validationConfigMap: examplename-enable
     img: >-
       <svg width="24" height="25" viewBox="0 0 24 25" fill="none" xmlns="http://www.w3.org/2000/svg">
       <path d="path data" fill="#ee0000"/>
       </svg>
     getStartedLink: 'https://example.org/docs/quickstart.html'
     route: exampleroutename
     routeNamespace: examplenamespace
     displayName: Example Name
     kfdefApplications: []
     support: third party support
     csvName: ''
     provider: example
     docsLink: 'https://example.org/docs/index.html'
     quickStart: ''
     getStartedMarkDown: >-
       # Example
   
       Enter text for the information panel.
   
     description: >-
       Enter summary text for the tile.
     category: Self-managed | Partner managed | Red Hat managed

9. Modify the parameters in the code for your application.

   Tip

   To see example YAML files, click Home → API Explorer, select OdhApplication, click the Instances tab, select an instance, and then click the YAML tab.

10. Click Create. The application details page appears.
11. Log in to OpenShift AI.
12. In the left menu, click Applications → Explore.
13. Locate the new tile for your application and click it.
14. In the information pane for the application, click Enable.

Procedure

1. Log in to the OpenShift console as a cluster administrator.

2. Open the dashboard configuration file:

   1. In the Administrator perspective, click Home → API Explorer.
   2. In the search bar, enter OdhDashboardConfig to filter by kind.
   3. Click the OdhDashboardConfig custom resource (CR) to open the resource details page.
   4. Select the redhat-ods-applications project from the Project list.
   5. Click the Instances tab.
   6. Click the odh-dashboard-config instance to open the details page.
   7. Click the YAML tab.
3. In the spec:notebookController section, set the value of enabled to false to hide the Jupyter tile from the list of Enabled applications.
4. Click Save to apply your changes and then click Reload to make sure that your changes are synced to the cluster.

Procedure

1. From the OpenShift AI dashboard, click Settings → Cluster settings.
2. Under PVC size, enter a new size in gibibytes. The minimum size is 1 GiB, and the maximum size is 16384 GiB.
3. Click Save changes.

Procedure

1. From the OpenShift AI dashboard, click Settings → Cluster settings.
2. Click Restore Default to restore the default PVC size of 20GiB.
3. Click Save changes.

Procedure

1. Log in to OpenShift Cluster Manager (https://console.redhat.com/openshift/).

2. Click Clusters.

   The Clusters page opens.

3. Click the name of the cluster you want to allocate additional resources to.
4. Click Actions → Edit node count.
5. Select a Machine pool from the list.
6. Select the number of nodes assigned to the machine pool from the Node count list.
7. Click Apply.

Procedure

1. On the page that opens when you launch Jupyter, click the Administration tab.

2. On the Administration tab, perform the following actions:

   1. In the Users section, locate the user whose notebook server you want to start.
   2. Click Start server beside the relevant user.
   3. Complete the Start a notebook server page.
   4. Optional: Select the Start server in current tab checkbox if necessary.

   5. Click Start server.

      After the server starts, you see one of the following behaviors:

      • If you previously selected the Start server in current tab checkbox, the JupyterLab interface opens in the current tab of your web browser.

      • If you did not previously select the Start server in current tab checkbox, the Starting server dialog box prompts you to open the server in a new browser tab or in the current tab.

        The JupyterLab interface opens according to your selection.

Procedure

1. On the page that opens when you launch Jupyter, click the Administration tab.

2. On the Administration page, perform the following actions:

   1. In the Users section, locate the user that the notebook server belongs to.
   2. Click View server beside the relevant user.
   3. On the Notebook server control panel page, click Access notebook server.

Procedure

1. On the page that opens when you launch Jupyter, click the Administration tab.

2. Stop one or more servers.

   • If you want to stop one or more specific servers, perform the following actions:

     1. In the Users section, locate the user that the notebook server belongs to.

     2. To stop the notebook server, perform one of the following actions:

        • Click the action menu (⋮) beside the relevant user and select Stop server.

        • Click View server beside the relevant user and then click Stop notebook server.

          The Stop server dialog box appears.

     3. Click Stop server.

   • If you want to stop all servers, perform the following actions:

     1. Click the Stop all servers button.
     2. Click OK to confirm stopping all servers.

Procedure

1. From the OpenShift AI dashboard, click Settings → Cluster settings.
2. Under Stop idle notebooks, select Stop idle notebooks after.
3. Enter a time limit, in hours and minutes, for when idle notebooks are stopped.
4. Click Save changes.

Procedure

1. From the OpenShift AI dashboard, click Settings → Notebook images.

   The Notebook images page appears. Previously imported notebook images are displayed. To enable or disable a previously imported notebook image, on the row containing the relevant notebook image, click the toggle in the Enable column.

   Note

   If you have already configured an accelerator identifier for a notebook image, you can specify a recommended accelerator for the notebook image by creating an associated accelerator profile. To do this, click Create profile on the row containing the notebook image and complete the relevant fields. If the notebook image does not contain an accelerator identifier, you must manually configure one before creating an associated accelerator profile.

2. Click Import new image. Alternatively, if no previously imported images were found, click Import image.

   The Import Notebook images dialog appears.

3. In the Image location field, enter the URL of the repository containing the notebook image. For example: quay.io/my-repo/my-image:tag, quay.io/my-repo/my-image@sha256:xxxxxxxxxxxxx, or docker.io/my-repo/my-image:tag.
4. In the Name field, enter an appropriate name for the notebook image.
5. Optional: In the Description field, enter a description for the notebook image.
6. Optional: From the Accelerator identifier list, select an identifier to set its accelerator as recommended with the notebook image. If the notebook image contains only one accelerator identifier, the identifier name displays by default.

7. Optional: Add software to the notebook image. After the import has completed, the software is added to the notebook image’s meta-data and displayed on the Jupyter server creation page.

   1. Click the Software tab.
   2. Click the Add software button.
   3. Click Edit ( ).
   4. Enter the Software name.
   5. Enter the software Version.
   6. Click Confirm ( ) to confirm your entry.
   7. To add additional software, click Add software, complete the relevant fields, and confirm your entry.

8. Optional: Add packages to the notebook images. After the import has completed, the packages are added to the notebook image’s meta-data and displayed on the Jupyter server creation page.

   1. Click the Packages tab.
   2. Click the Add package button.
   3. Click Edit ( ).
   4. Enter the Package name.
   5. Enter the package Version.
   6. Click Confirm ( ) to confirm your entry.
   7. To add an additional package, click Add package, complete the relevant fields, and confirm your entry.
9. Click Import.

Procedure

1. Determine the IDs of the persistent volumes (PVs) that you want to back up.

   1. In the OpenShift Dedicated web console, change into the Administrator perspective.
   2. Click Home → Projects.

   3. Click the rhods-notebooks project.

      The Details page for the project opens.

   4. Click the PersistentVolumeClaims in the Inventory section.

      The PersistentVolumeClaims page opens.

   5. Note the ID of the persistent volume (PV) that you want to back up.

      Note

      The persistent volumes (PV) that you make a note of are required to identify the correct EBS volume to back up in your AWS instance.

2. Locate the EBS volume containing the PVs that you want to back up.

   See Amazon Web Services documentation: Create Amazon EBS snapshots for more information.

   1. Log in to AWS (https://aws.amazon.com) and ensure that you are viewing the region that your OpenShift Dedicated cluster is deployed in.
   2. Click Services.
   3. Click Compute → EC2.

   4. Click Elastic Block Storage → Volumes in the side navigation.

      The Volumes page opens.

   5. In the search bar, enter the ID of the persistent volume (PV) that you made a note of earlier.

      The Volumes page reloads to display the search results.

   6. Click on the volume shown and verify that any kubernetes.io/created-for/pvc/namespace tags contain the value rhods-notebooks, and any kubernetes.io/created-for/pvc/name tags match the name of the persistent volume that the EC2 volume is being used for, for example, jupyter-nb-user1-pvc.

3. Back up the EBS volume that contains your persistent volume (PV).

   1. Right-click on the volume that you want to back up and select Create Snapshot from the list.

      The Create Snapshot page opens.

   2. Enter a Description for the volume.

   3. Click Create Snapshot.

      The snapshot of the volume is created.

   4. Click Close.

Procedure

1. Determine the IDs of the persistent volumes (PVs) that you want to back up.

   1. In the OpenShift Dedicated web console, change into the Administrator perspective.
   2. Click Home → Projects.

   3. Click the rhods-notebooks project.

      The Details page for the project opens.

   4. Click the PersistentVolumeClaims in the Inventory section.

      The PersistentVolumeClaims page opens.

   5. Note the ID of the persistent volume (PV) that you want to back up.

      The persistent volume (PV) IDs are required to identify the correct persistent disk to back up in your GCP instance.

2. Locate the persistent disk containing the PVs that you want to back up.

   1. Log in to the Google Cloud console (https://console.cloud.google.com) and ensure that you are viewing the region that your OpenShift Dedicated cluster is deployed in.
   2. Click the navigation menu (≡) and then click Compute Engine.

   3. From the side navigation, under Storage, click Disks.

      The Disks page opens.

   4. In the Filter query box, enter the ID of the persistent volume (PV) that you made a note of earlier.

      The Disks page reloads to display the search results.

   5. Click on the disk shown and verify that any kubernetes.io/created-for/pvc/namespace tags contain the value rhods-notebooks, and any kubernetes.io/created-for/pvc/name tags match the name of the persistent volume that the persistent disk is being used for, for example, jupyterhub-nb-user1-pvc.

3. Back up the persistent disk that contains your persistent volume (PV).

   1. Select CREATE SNAPSHOT from the top navigation.

      The Create a snapshot page opens.

   2. Enter a unique Name for the snapshot.
   3. Under Source disk, verify the persistent disk you want to back up is displayed.
   4. Change any optional settings as needed.

   5. Click CREATE.

      The snapshot of the persistent disk is created.

Procedure

1. From the OpenShift AI dashboard, click Settings → Cluster settings.
2. Locate the Usage data collection section.
3. Select the Allow collection of usage data checkbox.
4. Click Save changes.

Procedure

1. From the OpenShift AI dashboard, click Settings → Cluster settings.
2. Locate the Usage data collection section.
3. Deselect the Allow collection of usage data checkbox.
4. Click Save changes.