Added links to RHOAI

Author: pabel-rh

artifacts/attributes.adoc

@@ -178,4 +178,4 @@
 :openshift-ai-connector-for-rhdh-title: Integrate {product} with {openshift-ai-connector-name} to leverage AI models
 
 :openshift-ai-connector-name: OpenShift AI Connector for {product}
-:openshift-ai-connector-name-short: OpenShift AI Connector for {product-very-short}
+:openshift-ai-connector-name-short: OpenShift AI Connector for {product-very-short}

modules/openshift-ai-connector-for-rhdh/con-understand-how-ai-assets-map-to-rhdh-catalog.adoc

@@ -5,4 +5,6 @@
 
 include::{docdir}/artifacts/snip-developer-preview-rhoai.adoc[]
 
-The {openshift-ai-connector-name} ({openshift-ai-connector-name-short}) serves as a crucial link, enabling the discovery and accessibility of AI assets managed within the {rhoai-brand-name} offering directly within your {product-very-short} instance.
+The {openshift-ai-connector-name} ({openshift-ai-connector-name-short}) serves as a crucial link, enabling the discovery and accessibility of AI assets managed within the {rhoai-brand-name} offering directly within your {product-very-short} instance.
+
+For more information on model registry components, see https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/2.25/html/enabling_the_model_registry_component/overview-of-model-registries_model-registry-config[Overview of model registries and model catalog].

modules/openshift-ai-connector-for-rhdh/proc-setting-up-openshift-ai-connector-for-rhdh-with-rhoai.adoc

@@ -7,16 +7,18 @@ The installation of the {openshift-ai-connector-name} requires manual updates to
 
 .{rhoai-short} Prerequisites
 
-* To have Model Cards from the Model Catalog imported as TechDocs, you must use {rhoai-short} version 2.25 or later, and the *Model Catalog* dashboard and a Model Registry need to be enabled (they are both disabled by default).
-* If you employed Model Catalog at earlier versions of {rhoai-short}, Tech Doc propagation does not work for any models you registered into the Model Registry while at those earlier versions; only models registered into Model Registry from a 2.25 (or later) Model Catalog have their Model Cards transferred to {product-very-short} as TechDocs.
-* For the rest of the features, version 2.20 or later suffices. Enabling Model Registry and its associated dashboard allows for a user experience that more directly allows for customizing AI Model metadata.
+* To import model cards from the model catalog as TechDocs, you must use {rhoai-short} version 2.25 or later, and you must ensure that the model registry component is enabled. 
 
-//connect with Lindsey to update the above prereqs
+* If you employed model catalog at earlier versions of {rhoai-short}, TechDocs propagation does not work for any models you registered into the model registry while at those earlier versions; only models registered into model registry from a 2.25 (or later) model catalog have their model cards transferred to {product-very-short} as TechDocs.
+
+* For the rest of the features, version 2.20 or later suffices. Enabling model registry and its associated dashboard allows for a user experience that more directly allows for customizing AI Model metadata.
+
+For more details, see link:https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/2.25/html-single/enabling_the_model_registry_component/index[Enabling the model registry component].
 
 .Procedure
 
 . Configure {rhoai-short}-related RBAC and credentials.
-A Kubernetes `ServiceAccount` and a `service-account-token` Secret are required for the connector to retrieve data from {rhoai-short}. The following resources must be created, replacing namespace names (`ai-rhdh` for {product-very-short}, `rhoai-model-registries` for {rhoa``}) as needed:
+A Kubernetes `ServiceAccount` and a `service-account-token` Secret are required for the connector to retrieve data from {rhoai-short}. The following resources must be created, replacing namespace names (`ai-rhdh` for {product-very-short}, `rhoai-model-registries` for {rhoai-short}) as needed:
 ** `ServiceAccount` (`rhdh-rhoai-bridge`)
 ** `ClusterRole` and `ClusterRoleBinding` (`rhdh-rhoai-bridge`) to allow access to OCP resources like `routes`, `services`, and `inferenceservices`.
 ** `Role` and `RoleBinding` to allow ConfigMap updates within the {product-very-short} namespace.

modules/openshift-ai-connector-for-rhdh/proc-troubleshooting-connector-functionality.adoc

@@ -5,6 +5,8 @@
 
 The connector system consists of the two dynamic plugins and the three Model Catalog Bridge sidecar containers. Generally speaking, the logs collected should be provided to {company-name} Support for analysis.
 
+The actual contents of the diagnostic data are not part of any product guaranteed specification, and can change at any time.
+
 == Checking Dynamic Plugins status
 
 Validate that the dynamic plugins have been successfully installed into your {product-very-short} project Pod by using the following command:

modules/openshift-ai-connector-for-rhdh/ref-model-to-entity-mapping.adoc

@@ -3,32 +3,30 @@
 [id="ref-model-to-entity-mapping_{context}"]
 = Model-to-Entity mapping
 
-This offering interfaces with the {openshift-ai-connector-name-short}, Model Catalog, and KServe-based Model Deployments (InferenceServices) to create familiar {backstage} entities.
+This offering interfaces with the {openshift-ai-connector-name-short}, model catalog, and KServe-based Model Deployments (InferenceServices) to create familiar {backstage} entities.
 
 |===
 |{rhoai-short} Artifact |{product-very-short}/{backstage} Entity Kind |{product-very-short}/{backstage} Entity Type |Purpose
 
 |Model Server (InferenceService)
 |Component
 |`model-server`
-|Represents a running, accessible AI model endpoint. //Requires RHOAI 2.20 or later to obtain this mapping.
+|Represents a running, accessible AI model endpoint. See https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/2.25/html/configuring_your_model-serving_platform/index[Configuring your model-serving platform].
 
 |AI Model (Model Registry Version)
 |Resource
 |`ai-model`
-|Represents the specific AI model artifact (e.g., Llama-3-8B). Requires RHOAI 2.20 or later to obtain this mapping.
+|Represents the specific AI model artifact, for example, `Llama-3-8B`.
 
 |Model Server API Details
 |API
 |`openapi` (Default)
-|Provides the OpenAPI/Swagger specification for the model's REST endpoint. Requires RHOAI 2.20 or later to obtain this mapping.
+|Provides the OpenAPI/Swagger specification for the REST endpoint of the model. See https://access.redhat.com/articles/7047935[Red Hat OpenShifT AI: API Tiers]
 
 |Model Cards
 |TechDocs
 |N/A
-|Model Cards from the {rhoai-short} Model Catalog are associated with the Component and Resource entities. Requires RHOAI 2.25 to obtain this mapping.
+|Model cards from the {rhoai-short} model catalog are associated with the Component and Resource entities. See https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/2.25/html/working_with_the_model_catalog/registering-a-model-from-the-model-catalog_working-model-catalog[Registering a model from the model catalog].
 |===
 
-Once the {openshift-ai-connector-name-short} is installed and connected with {rhoai-short}, the transfer of information commences automatically.
-
-//To connect with Lindsey to update links here
+Once the {openshift-ai-connector-name-short} is installed and connected with {rhoai-short}, the transfer of information commences automatically.

modules/openshift-ai-connector-for-rhdh/ref-openshift-ai-model-registry-and-model-catalog-queries.adoc

@@ -1,46 +1,46 @@
 :_mod-docs-content-type: REFERENCE
 
 [id="ref-openshift-ai-model-registry-and-model-catalog-queries_{context}"]
-= OpenShift AI Model Registry and Model Catalog queries
+= OpenShift AI model registry and model catalog queries
 
-To access the same {rhoai-short} data as the connector, use `curl` to query the {rhoai-short} Model Registry and Model Catalog APIs, ensuring the ServiceAccount token has correct access control:
+To access the same {rhoai-short} data as the connector, use `curl` to query the {rhoai-short} model registry and model catalog APIs, ensuring the `ServiceAccount` token has correct access control:
 
-* Example: Fetch Registered Models
+* Example: Fetch registered models
 +
 [source,bash]
 ----
 curl -k -H "Authorization: Bearer $TOKEN" $RHOAI_MODEL_REGISTRY_URL/api/model_registry/v1alpha3/registered_models | jq
 ----
 
-* Example: Fetch Model Versions
+* Example: Fetch model versions
 +
 [source,bash]
 ----
 curl -k -H "Authorization: Bearer $TOKEN" $RHOAI_MODEL_REGISTRY_URL/api/model_registry/v1alpha3/model_versions | jq
 ----
 
-* Example: Fetch Model Artifacts
+* Example: Fetch model artifacts
 +
 [source,bash]
 ----
 curl -k -H "Authorization: Bearer $TOKEN" $RHOAI_MODEL_REGISTRY_URL/api/model_registry/v1alpha3/model_artifacts | jq
 ----
 
-* Example: Fetch Inference Services
+* Example: Fetch inference services
 +
 [source,bash]
 ----
 curl -k -H "Authorization: Bearer $TOKEN" $RHOAI_MODEL_REGISTRY_URL/api/model_registry/v1alpha3/inference_services | jq
 ----
 
-* Example: Fetch Serving Environments
+* Example: Fetch serving environments
 +
 [source,bash]
 ----
 curl -k -H "Authorization: Bearer $TOKEN" $RHOAI_MODEL_REGISTRY_URL/api/model_registry/v1alpha3/serving_environments | jq
 ----
 
-* Example: Fetch Catalog Sources
+* Example: Fetch catalog sources
 +
 [source,bash]
 ----

modules/openshift-ai-connector-for-rhdh/ref-out-of-the-box-details-from-rhoai.adoc

@@ -9,8 +9,8 @@ The connector propagates the following key data:
 ** URL of the OpenShift Route (if exposed).
 ** URL of the Kubernetes Service.
 ** Authentication requirement status.
-* Model Registry (Resource type `ai-model`):
+* Model registry (Resource type `ai-model`):
 ** Model description, artifact URIs, and author/owner information.
-* Model Catalog:
+* Model catalog:
 ** Links to the Model Card (as {product-very-short} TechDocs).
 ** Model license URL.