Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 2. Enabling the model registry component
Before data scientists and AI engineers in your organization can work with the model registry and model catalog, you must ensure that the modelregistry component is enabled in OpenShift AI.
The modelregistry component is enabled by default in a new OpenShift AI 3.2 installation. However, if the model registry was not enabled in a previous version of OpenShift AI, you must enable this component after upgrading to OpenShift AI 3.2.
Prerequisites
- You have cluster administrator privileges for your OpenShift cluster.
- You have access to the data science cluster.
- You have installed the Red Hat OpenShift AI Operator on your OpenShift cluster.
- You have sufficient resources. For more information about the minimum resources required to use OpenShift AI, see Installing and deploying OpenShift AI (for disconnected environments, see Deploying OpenShift AI in a disconnected environment).
Procedure
-
In the OpenShift console, click Operators
Installed Operators. - Search for the Red Hat OpenShift AI Operator version 2.14+, and then click the Operator name to open the Operator details page.
- Click the Data Science Cluster tab.
- Click the default instance name (for example, default-dsc) to open the instance details page.
- Click the YAML tab to show the instance specifications.
Find the
spec.componentssection, and then add or update it to include the followingmodelregistrycomponent entry, with themanagementStatefield set toManaged, and theregistriesNamespacefield set torhoai-model-registries:modelregistry: managementState: Managed registriesNamespace: rhoai-model-registriesmodelregistry: managementState: Managed registriesNamespace: rhoai-model-registriesCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Click Save.
Verification
Confirm that the model registry namespace was created successfully:
-
In the OpenShift console, click Home
Projects. -
Confirm that the
rhoai-model-registriesnamespace is displayed in the Projects drop-down list.
-
In the OpenShift console, click Home
Check the status of the model-registry-operator-controller-manager pod:
- In the OpenShift console, from the Project list, select redhat-ods-applications.
-
Click Workloads
Deployments. - Search for the model-registry-operator-controller-manager deployment.
Check the status:
- Click the deployment name to open the deployment details page.
- Click the Pods tab.
View the pod status.
When the status of the model-registry-operator-controller-manager-<pod-id> pod is Running, the pod is ready to use.
Next step
OpenShift AI administrators can create, delete, and manage permissions for model registries. For more information, see Managing model registries.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}