diff --git a/rhods-admin/1.33/chapter1/dependencies-install-web-console.html b/rhods-admin/1.33/chapter1/dependencies-install-web-console.html index bd703aa..b4f53d8 100644 --- a/rhods-admin/1.33/chapter1/dependencies-install-web-console.html +++ b/rhods-admin/1.33/chapter1/dependencies-install-web-console.html @@ -143,7 +143,7 @@

Installing Dependencies Using the Web Console

-

As described in the General Information about Installation section you may need to install other operators depending on the components and features of OpenShift AI you want to use. This section will discuss installing and configuring those components.

+

As described in the General Information about Installation section, you may need to install other operators depending on the components and features of OpenShift AI you want to use. This section will discuss about installing and configuring those components.

It is generally recommended to install any dependent operators prior to installing the Red Hat OpenShift AI operator.

@@ -237,7 +237,7 @@

-For assistance installing OpenShift Pipelines from YAML or via ArgoCD, refer to examples found in the redhat-cop/gitops-catalog/openshift-pipelines-operator GitHub repo. +For assistance in installing OpenShift Pipelines from YAML or via ArgoCD, refer to examples found in the redhat-cop/gitops-catalog/openshift-pipelines-operator GitHub repo. @@ -264,7 +264,7 @@

-Node Feature Discovery and the NVIDIA GPU Operator can both be installed in a cluster that does not have a node with a GPU. This can be helpful when you plan to add GPUs at a later date. If a GPU is not present in the cluster the Dashboard will not present the user an option to deploy using a GPU. +Node Feature Discovery and the NVIDIA GPU Operator can both be installed in a cluster that does not have a node with a GPU. This can be helpful when you plan to add GPUs at a later date. If a GPU is not present in the cluster, the Dashboard will not present the user an option to deploy using a GPU. @@ -370,7 +370,7 @@

-For assistance installing the Node Feature Discovery Operator from YAML or via ArgoCD, refer to examples found in the redhat-cop/gitops-catalog/nfd GitHub repo. +For assistance in installing the Node Feature Discovery Operator from YAML or via ArgoCD, refer to examples found in the redhat-cop/gitops-catalog/nfd GitHub repo. diff --git a/rhods-admin/1.33/chapter1/uninstalling-rhods.html b/rhods-admin/1.33/chapter1/uninstalling-rhods.html index c8c2955..1fa9cea 100644 --- a/rhods-admin/1.33/chapter1/uninstalling-rhods.html +++ b/rhods-admin/1.33/chapter1/uninstalling-rhods.html @@ -157,7 +157,7 @@

Demo: Uninstalling -These steps are for demonstration purposes only! Do NOT run these steps in your classroom because you will continue to work with the installed version of the product in the hands on labs in the course. +These steps are for demonstration purposes only! Do NOT run these steps in your classroom because you will continue to work with the installed version of the product in the hands-on labs in the course. @@ -177,7 +177,7 @@

Demo: Uninstalling
  1. -

    Log in to Red  OpenShift web console using a user which has the cluster-admin role assigned.

    +

    Log in to Red Hat OpenShift web console using a user which has the cluster-admin role assigned.

  2. Delete the DataScienceCluster object.

    @@ -213,7 +213,7 @@

    Demo: Uninstalling
    Figure 2. Delete DSCI Resource

-

alternatively you can delete the DCSI objects from the CLI.

+

Alternatively you can delete the DCSI objects from the CLI.

@@ -268,7 +268,7 @@

Demo: Uninstalling

  • Delete the namespaces that the Operator created during installation. They are labeled with label opendatahub.io/generated-namespace=true. -Deleting namespace rhods-notebooks leads to Persistent Volume Claims (PVC) being used by Workbench get deleted as well.

    +Deleting namespace rhods-notebooks leads to Persistent Volume Claims (PVC) being used by Workbench getting deleted as well.

    Navigate to Administration → Namespaces, filter the namespaces using the label opendatahub.io/generated-namespace=true and delete them.

    @@ -317,7 +317,7 @@

    If you have installed some dependencies you can remove them as long as they are not used by other deployments. -The following demonstration shows uninstallation of the Red Hat OpenShift Pipelines operator

    +The following demonstration shows uninstallation of the Red Hat OpenShift Pipelines operator.

    Demo: Uninstallation of the Red Hat OpenShift Pipelines operator

    @@ -338,7 +338,7 @@

    Demo: Unins

  • -

    In the pop-up window scroll down, check Delete all operand instances for this operator and click on Uninstall

    +

    In the pop-up window scroll down, check Delete all operand instances for this operator and click on Uninstall.

    piplines uninstall confirm diff --git a/rhods-admin/1.33/chapter1/upgrading-rhods.html b/rhods-admin/1.33/chapter1/upgrading-rhods.html index 11b534d..468acc9 100644 --- a/rhods-admin/1.33/chapter1/upgrading-rhods.html +++ b/rhods-admin/1.33/chapter1/upgrading-rhods.html @@ -146,7 +146,7 @@

    Upgrading Red Hat OpenShift AI

    Red Hat OpenShift AI upgrades are handled by the Red Hat OpenShift AI operator.

    -

    When an upgrade is available OLM creates an Installplan for the new version.

    +

    When an upgrade is available, OLM creates an Installplan for the new version.

    @@ -169,7 +169,7 @@

    Upgrading Red Hat OpenShift AI

    -

    Installplan is approved either automatically when a new version is available without user’s intervention or requires a manual approval. Whether the approval is automatic or manual depends on the value of the installPlanApproval attribute of the operator’s subscription. When it is set to Automatic the installplan is approved automatically and installation starts without user’s intervention. Manual value requires a manual approval.

    +

    Installplan is approved either automatically when a new version is available without user’s intervention or requires a manual approval. Whether the approval is automatic or manual, depends on the value of the installPlanApproval attribute of the operator’s subscription. When it is set to Automatic the installplan is approved automatically and installation starts without user’s intervention. Manual value requires a manual approval.

    Approvals can be set from the web console as well as from the CLI.

    @@ -189,7 +189,7 @@

    -These steps are for demonstration purposes only! Do NOT run these steps in your classroom because you will continue to work with the stable version of the product in the hands on labs in the course. +These steps are for demonstration purposes only! Do NOT run these steps in your classroom because you will continue to work with the stable version of the product in the hands-on labs in the course. diff --git a/rhods-admin/1.33/chapter2/resources.html b/rhods-admin/1.33/chapter2/resources.html index dd926b1..ec626d1 100644 --- a/rhods-admin/1.33/chapter2/resources.html +++ b/rhods-admin/1.33/chapter2/resources.html @@ -151,7 +151,7 @@

    Managing Resources

    Kubernetes Resources

    -

    The majority of actions taken in the OpenShift AI will create a kubernetes object based on that action. This section will discussion the different components supported by OpenShift AI and the different resources they create or interact with.

    +

    The majority of actions taken in the OpenShift AI will create a kubernetes object based on that action. This section will discuss the different components supported by OpenShift AI and the different resources they create or interact with.

    Data Science Projects

    @@ -175,7 +175,7 @@

    Data Science Project

    projects.project.openshift.io

    No

    -

    A Data Science Project is synonym with an OpenShift Project or a Namespace. See the users section for more information on how to create and manage Data Science Projects

    +

    A Data Science Project is synonym with an OpenShift Project or a Namespace. See the users section for more information on how to create and manage Data Science Projects.

    Users

    @@ -397,7 +397,7 @@

    Managing Workbench and Model Server Sizes

    -

    When launching Workbenches or Model Servers from the Dashboard, users are presented with several default sizes they can select from. The default options may not suit your organizations needs

    +

    When launching Workbenches or Model Servers from the Dashboard, users are presented with several default sizes they can select from. The default options may not suit your organizations needs.

    diff --git a/rhods-admin/1.33/chapter2/users.html b/rhods-admin/1.33/chapter2/users.html index 8f3cc51..ec2723a 100644 --- a/rhods-admin/1.33/chapter2/users.html +++ b/rhods-admin/1.33/chapter2/users.html @@ -237,7 +237,7 @@

    -

    It is highly recommended that dedicated admin users are configured for OpenShift AI and that organizations do not rely on the cluster-admin role for exclusive permissions to admin configurations of OpenShift AI. Dedicated Admin users should be added to the existing rhods-admins group, or another group which already contains the correct users should be configured in lieu of the rhods-admins group.

    +

    It is highly recommended that dedicated admin users are configured for OpenShift AI and that organizations do not rely on the cluster-admin role for exclusive permissions to admin configurations of OpenShift AI. Dedicated Admin users should be added to the existing rhods-admins group, or another group which already contains the correct users that should be configured in lieu of the rhods-admins group.

    @@ -254,10 +254,10 @@

    -

    Updating the access in the User and group settings in the Dashboard will only impact a users abilities to access the Dashboard, and will not impact any permissions granted by regular Kubernetes based RBAC.

    +

    Updating the access in the User and group settings in the Dashboard will only impact a user’s abilities to access the Dashboard, and will not impact any permissions granted by regular Kubernetes based RBAC.

    -

    For example, if the normal user group is updated to only allow specific users to access the Dashboard, and a user that is not part of that group has admin may still have the ability to create Data Science related objects such as Notebooks, Data Science Pipelines, or Model Servers in a namespace they have permission in using the associated k8s objects without the UI.

    +

    For example, if the normal user group is updated to only allow specific users to access the Dashboard, and a user that is not part of that group as admin may still have the ability to create Data Science related objects such as Notebooks, Data Science Pipelines, or Model Servers in a namespace they have permission in using the associated k8s objects without the UI.

    diff --git a/rhods-admin/1.33/chapter3/custom.html b/rhods-admin/1.33/chapter3/custom.html index 4d1e916..0a59a94 100644 --- a/rhods-admin/1.33/chapter3/custom.html +++ b/rhods-admin/1.33/chapter3/custom.html @@ -154,7 +154,7 @@

    Default OpenShift AI notebooks repository. This repository contains the source code, pre-built images, and examples to help you create your own image.

    -

    Additional images are available at the ODH contributions repository (opendatahub-io-contrib/workbench-images) This is a place to source additional images, as well as a great resource for best practices for building custom images. Workbench and runtime images are available as well as a script to generate custom images (https://github.com/opendatahub-io-contrib/workbench-images#building-an-image)

    +

    Additional images are available at the ODH contributions repository (opendatahub-io-contrib/workbench-images). This is a place to source additional images, as well as a great resource for best practices for building custom images. Workbench and runtime images are available as well as a script to generate custom images (https://github.com/opendatahub-io-contrib/workbench-images#building-an-image).

    diff --git a/rhods-admin/1.33/chapter3/importcustom.html b/rhods-admin/1.33/chapter3/importcustom.html index 86bf580..4462ae0 100644 --- a/rhods-admin/1.33/chapter3/importcustom.html +++ b/rhods-admin/1.33/chapter3/importcustom.html @@ -152,7 +152,7 @@

    1. -

      Before we import the image into OpenShif AI we need to set the quay repository we just created to public. In a browser login to quay.io and go to the rhods-admin-custom-image repository. Select the Settings gear icon.

      +

      Before we import the image into OpenShif AI we need to set the quay repository we just created to public. In a browser, login to quay.io and go to the rhods-admin-custom-image repository. Select the Settings gear icon.

      Quay Repository Settings diff --git a/rhods-admin/1.33/chapter3/index.html b/rhods-admin/1.33/chapter3/index.html index 1a8aa86..d500279 100644 --- a/rhods-admin/1.33/chapter3/index.html +++ b/rhods-admin/1.33/chapter3/index.html @@ -151,7 +151,7 @@

      Building Custom Notebook Images

      Create custom notebook images

    2. -

      How to import custom notebook images into OpenShift AI

      +

      Import custom notebook images into OpenShift AI

    diff --git a/rhods-admin/1.33/index.html b/rhods-admin/1.33/index.html index 49eb998..f5f5326 100644 --- a/rhods-admin/1.33/index.html +++ b/rhods-admin/1.33/index.html @@ -416,10 +416,10 @@

    Prerequisit

    Basic knowledge of OpenShift (or Kubernetes) administration

  • -

    Building and deploying container images

    +

    Ability to build and deploy container images

  • -

    OpenShift User and Role administration

    +

    Knowledge of OpenShift User and Role administration

  • Basic knowledge of AWS EC2 and S3 services

    @@ -437,19 +437,19 @@

    Objectives

    • -

      Installing RedHat OpenShift AI using the web console and CLI

      +

      Install RedHat OpenShift AI using the web console and CLI

    • -

      Upgrading RedHat OpenShift AI components

      +

      Upgrade RedHat OpenShift AI components

    • -

      Managing RedHat OpenShift AI users and controlling access

      +

      Manage RedHat OpenShift AI users and controlling access

    • -

      Enabling GPU support in RedHat OpenShift AI

      +

      Enable GPU support in RedHat OpenShift AI

    • -

      Stopping idle notebooks

      +

      Stop idle notebooks

    • Create and configure a custom notebook image