Skip to content

Commit

Permalink
updated flight logs
Browse files Browse the repository at this point in the history
  • Loading branch information
jcosenz committed Apr 4, 2024
1 parent df83741 commit 76f41f1
Show file tree
Hide file tree
Showing 2 changed files with 70 additions and 3 deletions.
7 changes: 4 additions & 3 deletions flight-logs/2024-04-03-cocreate.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,12 +29,13 @@ flowchart LR
- In Progress
4. Deploy and configure watsonx.ai on self-managed AWS infrastructure

## Today's Accomplishments


### Summary
- Master nodes attemting to upgrade and are in a stuck state preventing rollback of ingress changes
- Master nodes attempting to upgrade and are in a stuck state preventing rollback of ingress changes
- Attempting to deploy a new cluster
- New cluster successfully deployed via latest script
- Deploying EFS
- Installing OpenShift Data Foundation & Standalone Multicloud Object Gateway

## Decisions and Action Items (DAI)
- Software evaluation awaiting customer's approval process. This blocks our ability to download software from cp.icr.io
Expand Down
66 changes: 66 additions & 0 deletions flight-logs/2024-04-04-cocreate.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
---
title: Log 17 🛫
description: Flight Log of Co-Creation Activities
slug: flight-log-17
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

## Today's Acomplishments
- Kublet configuration update applied
- Deployed instance of Multicloud Object Gateway

### Summary
- Reinstalled NFS provisioner (Helm)
- Installed OpenShift Data Foundation Operator
- Deployed MultiCloud Object Gateway
- OpenShift portal is active and cluster appears healthy
- Configuring CP4D CLI
- Awaiting for final cluster nodes to update through machine config pool

## 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 escalate internally

## Lesons Learned
- Preparation for Cloud Pak for Data on OpenShift sizing needed to be adjusted to reflect an under-provisioning of CPU resources
- This was resolved by..

## 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

0 comments on commit 76f41f1

Please sign in to comment.