From 8b9d5e522208d7a928222bfb746e3520a245c38a Mon Sep 17 00:00:00 2001 From: "Adam.Hayden" Date: Wed, 8 May 2024 16:38:10 -0500 Subject: [PATCH 01/10] Fixed worker storage size --- .../scripts/Install-OCP-UPI/cloudformation/worker-template.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/static/scripts/Install-OCP-UPI/cloudformation/worker-template.yaml b/static/scripts/Install-OCP-UPI/cloudformation/worker-template.yaml index 8770a472..c35e0062 100644 --- a/static/scripts/Install-OCP-UPI/cloudformation/worker-template.yaml +++ b/static/scripts/Install-OCP-UPI/cloudformation/worker-template.yaml @@ -145,7 +145,7 @@ Resources: BlockDeviceMappings: - DeviceName: /dev/xvda Ebs: - VolumeSize: 5300" + VolumeSize: 500" VolumeType: "gp3" Encrypted: 'true' InstanceType: !Ref WorkerInstanceType From b8e87c475bc0f6a3e15bab53635995e5f428efba Mon Sep 17 00:00:00 2001 From: Ross Kramer Date: Wed, 10 Apr 2024 17:27:07 -0400 Subject: [PATCH 02/10] Updated the architecture to reflect updates to local storage requirements for worker nodes and added the installation instructions for Watsonx.ai --- docs/1-GettingStarted/1-Architecture.mdx | 12 ++--- docs/3-Installation/1-CP4D.mdx | 7 +++ docs/3-Installation/2-wxai.mdx | 60 ++++++++++++++++++++++++ 3 files changed, 73 insertions(+), 6 deletions(-) create mode 100644 docs/3-Installation/2-wxai.mdx diff --git a/docs/1-GettingStarted/1-Architecture.mdx b/docs/1-GettingStarted/1-Architecture.mdx index b266c5b4..b94d6914 100644 --- a/docs/1-GettingStarted/1-Architecture.mdx +++ b/docs/1-GettingStarted/1-Architecture.mdx @@ -35,12 +35,12 @@ For now we recommend the following: #### Infrastructure -|Flavor | Count | vCPU | RAM | GPU Count | GPU RAM | -|--|--|--|--|--|--| -|m5.2xlarge|3|24 (8 cores x Count)|96G (32G x Count)|0|0| -|m6i.8xlarge|6|192 (32 cores x Count)|768G (128G x Count)|0|0| -|p4d.24xlarge|1|96|1152G|8|320G| -|**Totals**|13|336|2112G|8|320G| +|Flavor | Count | vCPU | RAM | GPU Count | GPU RAM | Local Storage | +|--|--|--|--|--|--|--| +|m5.2xlarge|3|24 (8 cores x Count)|96G (32G x Count)|0|0| 300Gb | +|m6i.8xlarge|6|192 (32 cores x Count)|768G (128G x Count)|0|0| 500Gb | +|p4d.24xlarge|1|96|1152G|8|320G| 500Gb | +|**Totals**|13|336|2112G|8|320G| 3500Gb | #### Networking diff --git a/docs/3-Installation/1-CP4D.mdx b/docs/3-Installation/1-CP4D.mdx index fade0329..b1c67c55 100644 --- a/docs/3-Installation/1-CP4D.mdx +++ b/docs/3-Installation/1-CP4D.mdx @@ -863,6 +863,13 @@ cpd-cli manage apply-cr \ --license_acceptance=true ``` +Verify the installation +```tsx +cpd-cli manage get-cr-status \ +--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ +--components=ws +``` + ### IBM Knowledge Catalog Run the following command to create the required OLM objects for IBM Knowledge Catalog in the operators project for the instance: diff --git a/docs/3-Installation/2-wxai.mdx b/docs/3-Installation/2-wxai.mdx new file mode 100644 index 00000000..90f12273 --- /dev/null +++ b/docs/3-Installation/2-wxai.mdx @@ -0,0 +1,60 @@ +--- +id: WXAI +sidebar_position: 2 +title: Watsonx ai installation +custom_edit_url: null +--- + +:::note +Associated links with this section + +[Installing Multicloud Object Gateway](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.8.x?topic=watsonxai-installing) +::: + +## Login to the cluster with cpd-cli + +Source the env file + +`source cpd_vars_48.sh` + +login with cpd-cli +``` +cpd-cli manage login-to-ocp \ +--username=${OCP_USERNAME} \ +--password=${OCP_PASSWORD} \ +--server=${OCP_URL} +``` + +## Installing OLM + +The following services are automatically installed when you install the IBM watsonx.ai service, presuming you haven't installed them already. +- Watson Studio +- Watson Machine Learning + +Run the following command to create the required OLM objects for IBM watsonx.ai in the operators project for the instance: + +```tsx +cpd-cli manage apply-olm \ +--release=${VERSION} \ +--cpd_operator_ns=${PROJECT_CPD_INST_OPERATORS} \ +--components=watsonx_ai +``` + +## Install the CR + +```tsx +cpd-cli manage apply-cr \ +--components=watsonx_ai \ +--release=${VERSION} \ +--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ +--block_storage_class=${STG_CLASS_BLOCK} \ +--file_storage_class=${STG_CLASS_FILE} \ +--license_acceptance=true +``` + +## Verifying the installation +```tsx +cpd-cli manage get-cr-status \ +--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ +--components=watsonx_ai +``` From f889b2a99ba7e877021730911a782deee016a082 Mon Sep 17 00:00:00 2001 From: Ross Kramer Date: Thu, 11 Apr 2024 11:24:35 -0400 Subject: [PATCH 03/10] Adding flight log for this week --- flight-logs/2024-04-12-cocreate.mdx | 65 +++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+) create mode 100644 flight-logs/2024-04-12-cocreate.mdx diff --git a/flight-logs/2024-04-12-cocreate.mdx b/flight-logs/2024-04-12-cocreate.mdx new file mode 100644 index 00000000..42d194ae --- /dev/null +++ b/flight-logs/2024-04-12-cocreate.mdx @@ -0,0 +1,65 @@ +--- +title: Log 19 🛫 +description: Flight Log of Co-Creation Activities +slug: flight-log-19 +tags: [log] +--- + +## Objective +Deploy watsonx.ai on self-managed AWS infrastructure for customer software evaluation + +```mermaid +flowchart LR + A(Deploy bootnode) --> B(Deploy infrastructure) + B -->C(Deploy OCP) + subgraph "You are here" + D(Prepare CP4D & watsonx ai cartdridge) + end + C -->D + D -->E(Install CP4D) + E -->F(Deploy watsonx.ai) +``` + + +## Milestones +1. Deploy and configuration of boot node to establish a beach-head into the customer AWS environment + - Complete +2. Deploy OCP using the documented UPI installation steps + - Complete +3. Install Cloud Pak for Data + - In Progress +4. Deploy and configure watsonx.ai on self-managed AWS infrastructure on ref environment and document + - In Progress + +### Summary +- Awaiting entitlement key approval on customer side + +## Decisions and Action Items (DAI) +- Software evaluation awaiting customer's approval process. This blocks our ability to download software from cp.icr.io + - Customer to provide by EOD Monday +- Worker nodes shutdown until approval comes through +- Drafted and sent instructions for the customer to resize the worker node disks for when the cluster is brought back online +- Drafted and sent instructions for the customer to order a GPU Node + - GPU node to be added to the cluster and then cordoned, drained, and shutdown + +## Lessons Learned +- Preparation for Cloud Pak for Data on OpenShift sizing needed to be adjusted to reflect an under-provisioning of CPU resources +- watsonx.ai service requires larger local disks on worker nodes (500Gb) +- The GPU node required for watsonx.ai seems to be a limited resource + +## Next Steps +- License and configure Cloud Pak for Data + - Cloud Pak Considerations + - Security scans needed on container images + - Customer requires on-prem, offline install + - Customer uses their own container registry that might introduce extra effort or compatability issues + - Version compatibility with OpenShift (e.g. 4.10 required and customer has 4.11) + - Supported storage not available + - Multiple cloudpaks on the same cluster + - custom connections to data sources not supported OOTB + - AWS-specific: IAM users required for install/deploy and are not allowed + - OpenShift specific: CoreOS requirement for control nodes + - Automatic updating of Cloud Pak, this can interrupt engagements (solution is to always remove update polling from operators) + - Resize local disks for worker nodes + - Customer to order a GPU node and attach it to the cluster +- Deploy watsonx.ai \ No newline at end of file From 9ca923108e6c055aa5c65635089350ae30c68c19 Mon Sep 17 00:00:00 2001 From: Nikhil Gopal Date: Thu, 11 Apr 2024 10:12:41 -0500 Subject: [PATCH 04/10] added 4/5 FL --- flight-logs/2024-04-05-cocreate.mdx | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/flight-logs/2024-04-05-cocreate.mdx b/flight-logs/2024-04-05-cocreate.mdx index 60117045..aa952215 100644 --- a/flight-logs/2024-04-05-cocreate.mdx +++ b/flight-logs/2024-04-05-cocreate.mdx @@ -60,4 +60,21 @@ flowchart LR - AWS-specific: IAM users required for install/deploy and are not allowed - OpenShift specific: CoreOS requirement for control nodes - Automatic updating of Cloud Pak, this can interrupt engagements (solution is to always remove update polling from operators) -- Deploy watsonx.ai \ No newline at end of file +- Deploy watsonx.ai + +# RAG Portion + +## Objective +- Start building guided workflows +- Attempt to improve parsing of unstructured tables with WDU (Watson Document Understanding) + +## Milestones +1. Designed some guided workflow concept ideas +2. Coded flask app to expose an API to send emails to users from the Watsonx Assistant +3. Table parsing with WDU sucesfully configured + +## Lessons learned + +## Next Steps +- Integrate agent based workflows into guided workflows (langchain agents) +- Investigate if its possible to improve table parsing \ No newline at end of file From 82bc4954a9b46717a5a5882ebfe06235020d9e86 Mon Sep 17 00:00:00 2001 From: Ross Kramer Date: Thu, 2 May 2024 10:05:26 -0400 Subject: [PATCH 05/10] Reorganized the docs a bit and added a section for use cases --- docs/1-GettingStarted/1-Architecture.mdx | 12 +++++++++++- .../{ => 1-Infrastructure}/1-Installation.mdx | 0 .../{ => 1-Infrastructure}/2-UPI_Install.mdx | 0 docs/2-Deployment/1-Infrastructure/README.mdx | 6 ++++++ docs/2-Deployment/1-Infrastructure/_category_.json | 6 ++++++ .../3-Software}/1-CP4D.mdx | 0 .../3-Software}/2-wxai.mdx | 0 .../3-Software}/README.mdx | 4 ++-- docs/2-Deployment/3-Software/_category_.json | 6 ++++++ docs/3-Use-Cases/RAG.mdx | 6 ++++++ docs/3-Use-Cases/README.mdx | 6 ++++++ docs/{3-Installation => 3-Use-Cases}/_category_.json | 2 +- 12 files changed, 44 insertions(+), 4 deletions(-) rename docs/2-Deployment/{ => 1-Infrastructure}/1-Installation.mdx (100%) rename docs/2-Deployment/{ => 1-Infrastructure}/2-UPI_Install.mdx (100%) create mode 100644 docs/2-Deployment/1-Infrastructure/README.mdx create mode 100644 docs/2-Deployment/1-Infrastructure/_category_.json rename docs/{3-Installation => 2-Deployment/3-Software}/1-CP4D.mdx (100%) rename docs/{3-Installation => 2-Deployment/3-Software}/2-wxai.mdx (100%) rename docs/{3-Installation => 2-Deployment/3-Software}/README.mdx (53%) create mode 100644 docs/2-Deployment/3-Software/_category_.json create mode 100644 docs/3-Use-Cases/RAG.mdx create mode 100644 docs/3-Use-Cases/README.mdx rename docs/{3-Installation => 3-Use-Cases}/_category_.json (75%) diff --git a/docs/1-GettingStarted/1-Architecture.mdx b/docs/1-GettingStarted/1-Architecture.mdx index b94d6914..11cfde78 100644 --- a/docs/1-GettingStarted/1-Architecture.mdx +++ b/docs/1-GettingStarted/1-Architecture.mdx @@ -25,12 +25,22 @@ For now we recommend the following: - Watson Machine Learning - IBM Knowledge Catalog - Foundational Models - - mixtral + - mixtral-8x7b-instruct-v01-q - llama2 - ibm-granite-chat-v2.1 ## Bill of Materials +### Foundational Model requirements for watsonx.ai + +One of the following types of GPUs is required to support the use of foundation models in IBM watsonx.ai: + +- NVIDIA A100 80 GB +- NVIDIA H100 80 GB +- NVIDIA L40S 48 GB + +Currently this the A100 GPU are available in the P4 flavor ec2 instance in AWS. + ### AWS Requirements #### Infrastructure diff --git a/docs/2-Deployment/1-Installation.mdx b/docs/2-Deployment/1-Infrastructure/1-Installation.mdx similarity index 100% rename from docs/2-Deployment/1-Installation.mdx rename to docs/2-Deployment/1-Infrastructure/1-Installation.mdx diff --git a/docs/2-Deployment/2-UPI_Install.mdx b/docs/2-Deployment/1-Infrastructure/2-UPI_Install.mdx similarity index 100% rename from docs/2-Deployment/2-UPI_Install.mdx rename to docs/2-Deployment/1-Infrastructure/2-UPI_Install.mdx diff --git a/docs/2-Deployment/1-Infrastructure/README.mdx b/docs/2-Deployment/1-Infrastructure/README.mdx new file mode 100644 index 00000000..ab90332d --- /dev/null +++ b/docs/2-Deployment/1-Infrastructure/README.mdx @@ -0,0 +1,6 @@ +--- +sidebar_position: 1 +slug: /infrastructure +title: 'Infrastructure' +custom_edit_url: null +--- \ No newline at end of file diff --git a/docs/2-Deployment/1-Infrastructure/_category_.json b/docs/2-Deployment/1-Infrastructure/_category_.json new file mode 100644 index 00000000..b0a5098a --- /dev/null +++ b/docs/2-Deployment/1-Infrastructure/_category_.json @@ -0,0 +1,6 @@ +{ + "label": "Infrastructure", + "position": 1, + "collapsed": false, + "link": {"type": "doc", "id": "README"} +} \ No newline at end of file diff --git a/docs/3-Installation/1-CP4D.mdx b/docs/2-Deployment/3-Software/1-CP4D.mdx similarity index 100% rename from docs/3-Installation/1-CP4D.mdx rename to docs/2-Deployment/3-Software/1-CP4D.mdx diff --git a/docs/3-Installation/2-wxai.mdx b/docs/2-Deployment/3-Software/2-wxai.mdx similarity index 100% rename from docs/3-Installation/2-wxai.mdx rename to docs/2-Deployment/3-Software/2-wxai.mdx diff --git a/docs/3-Installation/README.mdx b/docs/2-Deployment/3-Software/README.mdx similarity index 53% rename from docs/3-Installation/README.mdx rename to docs/2-Deployment/3-Software/README.mdx index 949eb348..747998f0 100644 --- a/docs/3-Installation/README.mdx +++ b/docs/2-Deployment/3-Software/README.mdx @@ -1,6 +1,6 @@ --- sidebar_position: 3 -slug: /installation -title: 'Installation' +slug: /software +title: 'Software' custom_edit_url: null --- \ No newline at end of file diff --git a/docs/2-Deployment/3-Software/_category_.json b/docs/2-Deployment/3-Software/_category_.json new file mode 100644 index 00000000..767edfd1 --- /dev/null +++ b/docs/2-Deployment/3-Software/_category_.json @@ -0,0 +1,6 @@ +{ + "label": "Software", + "position": 1, + "collapsed": false, + "link": {"type": "doc", "id": "README"} +} \ No newline at end of file diff --git a/docs/3-Use-Cases/RAG.mdx b/docs/3-Use-Cases/RAG.mdx new file mode 100644 index 00000000..96e749dd --- /dev/null +++ b/docs/3-Use-Cases/RAG.mdx @@ -0,0 +1,6 @@ +--- +id: use-cases +sidebar_position: 1 +title: RAG Use Cases +custom_edit_url: null +--- \ No newline at end of file diff --git a/docs/3-Use-Cases/README.mdx b/docs/3-Use-Cases/README.mdx new file mode 100644 index 00000000..ed557407 --- /dev/null +++ b/docs/3-Use-Cases/README.mdx @@ -0,0 +1,6 @@ +--- +sidebar_position: 2 +slug: /use-cases +title: 'Use Cases' +custom_edit_url: null +--- \ No newline at end of file diff --git a/docs/3-Installation/_category_.json b/docs/3-Use-Cases/_category_.json similarity index 75% rename from docs/3-Installation/_category_.json rename to docs/3-Use-Cases/_category_.json index 09a2baed..e7bc2023 100644 --- a/docs/3-Installation/_category_.json +++ b/docs/3-Use-Cases/_category_.json @@ -1,5 +1,5 @@ { - "label": "Installation", + "label": "Use Cases", "position": 3, "collapsed": false, "link": {"type": "doc", "id": "README"} From ed69d82a98d4393ee95add6f34621d3de29d91fa Mon Sep 17 00:00:00 2001 From: Ross Kramer Date: Tue, 7 May 2024 10:32:30 -0400 Subject: [PATCH 06/10] Adding specific references for getting the ibm entitlement key --- docs/1-GettingStarted/2-Prequisites.mdx | 6 ++++++ docs/2-Deployment/3-Software/1-CP4D.mdx | 4 ++++ 2 files changed, 10 insertions(+) diff --git a/docs/1-GettingStarted/2-Prequisites.mdx b/docs/1-GettingStarted/2-Prequisites.mdx index 4013426c..2c9568c6 100644 --- a/docs/1-GettingStarted/2-Prequisites.mdx +++ b/docs/1-GettingStarted/2-Prequisites.mdx @@ -46,6 +46,12 @@ You can now log into https://console.redhat.com/openshift/install/pull-secret an +## IBM Requirements + +CP4D and watsonx.ai are part of IBM's entitled software program. In order to download and install it you will need your IBM entitlement key which can be retrieved [here](https://myibm.ibm.com/products-services/containerlibrary). + +You will need your valid IBM id in order to login. + ## AWS Requirements ### IAM User Requirements diff --git a/docs/2-Deployment/3-Software/1-CP4D.mdx b/docs/2-Deployment/3-Software/1-CP4D.mdx index b1c67c55..ad9d77f4 100644 --- a/docs/2-Deployment/3-Software/1-CP4D.mdx +++ b/docs/2-Deployment/3-Software/1-CP4D.mdx @@ -310,6 +310,7 @@ OCP_PASSWORD IBM_ENTITLEMENT_KEY ``` + By default we set our storage classes to the `nfs-client` storage class. Your mileage may vary. If you are an IBM employee, entitlement key can be fetched from [here](https://myibm.ibm.com/products-services/containerlibrary) @@ -337,8 +338,11 @@ cpd-cli manage login-to-ocp \ --password=${OCP_PASSWORD} \ --server=${OCP_URL} ``` + ### Add the entitlement key +The key can be retrieved from [here](https://myibm.ibm.com/products-services/containerlibrary) + ```tsx cpd-cli manage add-icr-cred-to-global-pull-secret \ --entitled_registry_key=${IBM_ENTITLEMENT_KEY} From 41f137ad58854150d4abd6319b5c47140150ebcc Mon Sep 17 00:00:00 2001 From: Ross Kramer Date: Tue, 7 May 2024 10:33:51 -0400 Subject: [PATCH 07/10] Adding specific references for getting the ibm entitlement key --- docs/2-Deployment/3-Software/1-CP4D.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/2-Deployment/3-Software/1-CP4D.mdx b/docs/2-Deployment/3-Software/1-CP4D.mdx index ad9d77f4..10ed93b3 100644 --- a/docs/2-Deployment/3-Software/1-CP4D.mdx +++ b/docs/2-Deployment/3-Software/1-CP4D.mdx @@ -313,8 +313,6 @@ IBM_ENTITLEMENT_KEY By default we set our storage classes to the `nfs-client` storage class. Your mileage may vary. -If you are an IBM employee, entitlement key can be fetched from [here](https://myibm.ibm.com/products-services/containerlibrary) - The `OCP_URL` can be pulled with this command: ```tsx oc cluster-info From e4fc24e77b0f8f32a4fb27de59f1e5dc0b48cc0d Mon Sep 17 00:00:00 2001 From: Ross Kramer Date: Tue, 7 May 2024 15:46:00 -0400 Subject: [PATCH 08/10] Fixing broken links to allow to build --- docs/1-GettingStarted/2-Prequisites.mdx | 4 ++-- docs/2-Deployment/3-Software/1-CP4D.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/1-GettingStarted/2-Prequisites.mdx b/docs/1-GettingStarted/2-Prequisites.mdx index 2c9568c6..90830bb3 100644 --- a/docs/1-GettingStarted/2-Prequisites.mdx +++ b/docs/1-GettingStarted/2-Prequisites.mdx @@ -754,11 +754,11 @@ The following parameters must be gathered from the AWS infrastructure in order t - no_proxy: - KeyPairName: :::note - Key Pair generation instructions [here](/Deployment/preparation#create-aws-keypair) + Key Pair generation instructions [here](/Deployment/Infrastructure/preparation#create-aws-keypair) ::: - RedhatPullSecret: :::note - RedHat Pull Secret instructions [here](/Deployment/preparation#obtain-redhat-pull-secret) + RedHat Pull Secret instructions [here](/Deployment/Infrastructure/preparation#obtain-redhat-pull-secret) ::: - DomainName: - ClusterName: diff --git a/docs/2-Deployment/3-Software/1-CP4D.mdx b/docs/2-Deployment/3-Software/1-CP4D.mdx index 10ed93b3..d0683f76 100644 --- a/docs/2-Deployment/3-Software/1-CP4D.mdx +++ b/docs/2-Deployment/3-Software/1-CP4D.mdx @@ -691,7 +691,7 @@ export INSTANCE_NAME="wa-instance" ``` :::note -You should have followed the steps [here](/Installation/CP4D#generate-a-cpd-cli-profile) to generate a profile. +You should have followed the steps [here](/Deployment/Software/CP4D#generate-a-cpd-cli-profile) to generate a profile. The example profile we created we called `wxai`. ::: From 4857d665dd0f974878a598998025311ae721ed98 Mon Sep 17 00:00:00 2001 From: Ross Kramer Date: Wed, 8 May 2024 15:31:39 -0400 Subject: [PATCH 09/10] Adding flight log for today --- flight-logs/2024-05-08-cocreate.mdx | 63 +++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+) create mode 100644 flight-logs/2024-05-08-cocreate.mdx diff --git a/flight-logs/2024-05-08-cocreate.mdx b/flight-logs/2024-05-08-cocreate.mdx new file mode 100644 index 00000000..e9e409ee --- /dev/null +++ b/flight-logs/2024-05-08-cocreate.mdx @@ -0,0 +1,63 @@ +--- +title: Log 20 🛫 +description: Flight Log of Co-Creation Activities +slug: flight-log-20 +tags: [log] +--- + +## Objective +Deploy watsonx.ai on self-managed AWS infrastructure for customer software evaluation + +```mermaid +flowchart LR + A(Deploy bootnode) --> B(Deploy infrastructure) + B -->C(Deploy OCP) + subgraph "You are here" + D(Prepare CP4D & watsonx ai cartdridge) + end + C -->D + D -->E(Install CP4D) + E -->F(Deploy watsonx.ai) +``` + + +## Milestones +1. Deploy and configuration of boot node to establish a beach-head into the customer AWS environment + - Complete +2. Deploy OCP using the documented UPI installation steps + - Complete +3. Install Cloud Pak for Data + - In Progress +4. Deploy and configure watsonx.ai on self-managed AWS infrastructure on ref environment and document + - In Progress + +### Summary +- Customer has approved required contracts and procedures have been followed to attain an entitlement key. + +## Decisions and Action Items (DAI) +- Customer has worked with us to spin up a new cluster + - Previous cluster had been deleted to save AWS credits + - IBM to provide tighter instruction for the deployment of CP4D +- Customer received a GPU reservation + - GPU node has been ordered and deployed + - Costs associated with GPU resources are discounted, but the meter is running once the reservation is accepted. + +## Lessons Learned +- watsonx.ai service requires larger local disks on worker nodes (500Gb) +- The GPU node required for watsonx.ai seems to be a limited resource +- Had to replace the nodes in the cluster as the attached disks were incorrect + +## Next Steps +- License and configure Cloud Pak for Data + - Cloud Pak Considerations + - Security scans needed on container images + - Customer requires on-prem, offline install + - Customer uses their own container registry that might introduce extra effort or compatability issues + - Version compatibility with OpenShift (e.g. 4.10 required and customer has 4.11) + - Supported storage not available + - Multiple cloudpaks on the same cluster + - custom connections to data sources not supported OOTB + - AWS-specific: IAM users required for install/deploy and are not allowed + - OpenShift specific: CoreOS requirement for control nodes + - Automatic updating of Cloud Pak, this can interrupt engagements (solution is to always remove update polling from operators) +- Deploy watsonx.ai \ No newline at end of file From 404f55e366105c6b855eba0e7188181214e1a1b8 Mon Sep 17 00:00:00 2001 From: Ross Kramer Date: Wed, 8 May 2024 16:17:32 -0400 Subject: [PATCH 10/10] Modified the order of things slightly so we install the cp4d cli BEFORE actually running anything with it --- docs/2-Deployment/3-Software/1-CP4D.mdx | 104 ++++++++++++------------ 1 file changed, 52 insertions(+), 52 deletions(-) diff --git a/docs/2-Deployment/3-Software/1-CP4D.mdx b/docs/2-Deployment/3-Software/1-CP4D.mdx index d0683f76..d771e9d2 100644 --- a/docs/2-Deployment/3-Software/1-CP4D.mdx +++ b/docs/2-Deployment/3-Software/1-CP4D.mdx @@ -98,58 +98,6 @@ You can create only the standalone Multicloud Object Gateway component while dep 1. Click **Workloads → Pods** from the OpenShift Web Console. 1. Select `openshift-storage` from the **Project** drop-down list and verify pods are in Running state. -### Create required secrets for Services - -If we're planning on installing the following: - -- Watsonx Assistant -- Watson Discovery - -The names of all NooBaa account credentials can be retrieved with the following command -```tsx -oc get secrets -n openshift-storage | grep noobaa -``` - -Running from our linux bastion host, we need to export the following secret names: - -```tsx -export NOOBAA_ACCOUNT_CREDENTIALS_SECRET=noobaa-admin -export NOOBAA_ACCOUNT_CERTIFICATE_SECRET=noobaa-s3-serving-cert -``` - -Create the secrets that watsonx Assistant will use to connect to Multicloud Object Gateway: -```tsx -cpd-cli manage setup-mcg \ ---components=watson_assistant \ ---cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ ---noobaa_account_secret=${NOOBAA_ACCOUNT_CREDENTIALS_SECRET} \ ---noobaa_cert_secret=${NOOBAA_ACCOUNT_CERTIFICATE_SECRET} -``` - -Verify the secrets were created -```tsx -oc get secrets --namespace=${PROJECT_CPD_INST_OPERANDS} \ -noobaa-account-watson-assistant \ -noobaa-cert-watson-assistant \ -noobaa-uri-watson-assistant -``` - -Should return -```tsx -NAME TYPE DATA AGE -noobaa-account-watson-assistant Opaque 2 33s -noobaa-cert-watson-assistant Opaque 1 32s -noobaa-uri-watson-assistant Opaque 3 29s -``` - -Wash, rinse, repeat for Watson Discovery - -```tsx -cpd-cli manage setup-mcg \ ---components=watson_discovery \ ---cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ ---noobaa_account_secret=${NOOBAA_ACCOUNT_CREDENTIALS_SECRET} -``` @@ -345,6 +293,58 @@ The key can be retrieved from [here](https://myibm.ibm.com/products-services/con cpd-cli manage add-icr-cred-to-global-pull-secret \ --entitled_registry_key=${IBM_ENTITLEMENT_KEY} ``` +### Create required secrets for Services + +If we're planning on installing the following: + +- Watsonx Assistant +- Watson Discovery + +The names of all NooBaa account credentials can be retrieved with the following command +```tsx +oc get secrets -n openshift-storage | grep noobaa +``` + +Running from our linux bastion host, we need to export the following secret names: + +```tsx +export NOOBAA_ACCOUNT_CREDENTIALS_SECRET=noobaa-admin +export NOOBAA_ACCOUNT_CERTIFICATE_SECRET=noobaa-s3-serving-cert +``` + +Create the secrets that watsonx Assistant will use to connect to Multicloud Object Gateway: +```tsx +cpd-cli manage setup-mcg \ +--components=watson_assistant \ +--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ +--noobaa_account_secret=${NOOBAA_ACCOUNT_CREDENTIALS_SECRET} \ +--noobaa_cert_secret=${NOOBAA_ACCOUNT_CERTIFICATE_SECRET} +``` + +Verify the secrets were created +```tsx +oc get secrets --namespace=${PROJECT_CPD_INST_OPERANDS} \ +noobaa-account-watson-assistant \ +noobaa-cert-watson-assistant \ +noobaa-uri-watson-assistant +``` + +Should return +```tsx +NAME TYPE DATA AGE +noobaa-account-watson-assistant Opaque 2 33s +noobaa-cert-watson-assistant Opaque 1 32s +noobaa-uri-watson-assistant Opaque 3 29s +``` + +Wash, rinse, repeat for Watson Discovery + +```tsx +cpd-cli manage setup-mcg \ +--components=watson_discovery \ +--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ +--noobaa_account_secret=${NOOBAA_ACCOUNT_CREDENTIALS_SECRET} +``` ## Installing CP4D