Skip to main content

Log 18 🛫

· 2 min read

Objective​

Deploy watsonx.ai on self-managed AWS infrastructure for customer software evaluation

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

Today's Acomplishments​

  • CP4D Final Preparations
    • Added options to the CPD VARS file
    • Recreation of work dir

Summary​

  • Trobuleshooting the CP4D CLI
  • Awaiting entitlement key approval

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

Lesons Learned​

  • Preparation for Cloud Pak for Data on OpenShift sizing needed to be adjusted to reflect an under-provisioning of CPU resources

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

Next Steps​

  • Integrate agent based workflows into guided workflows (langchain agents)
  • Investigate if its possible to improve table parsing
  • 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
  • Application configurations
  • Application validations