Cloud Pak for Data Group

 View Only

Questionnaire for Upgrade (3.5.X -> 4.0.Y)

By Hong Wei Jia posted Tue March 29, 2022 05:59 AM

  
Questionnaire for Upgrade (3.5.X -> 4.0.Y)

The purpose of this questionnaire is to help get an overview of CPD 3.5 usage information before the upgrade. Basically, it will include CPD services, OpenShift version and Storage related information. This information can help to make the upgrade plan.

1.What’s the target version you plan to upgrade to?

 

2.What’s the platform that your Cloud Pak for Data cluster built on? Please choose from the following options.

BareMetal, VMware, AWS, IBM Cloud or Azure

 

3.Is it internet-connected or air-gapped environment?

 

4.Collect current Cloud Pak for Data cluster information

Note: you have to run the following commands with the cluster administrator role.

#Collect information about your current OpenShift version

oc version

#Collect information about the number of master nodes and worker nodes in your current OpenShift cluster.

oc get nodes

#Collect information about the hardware configuration for each worker node (the number of CPUs and MEM capacity) in your current OpenShift cluster.

oc describe nodes

#Collect information about the storage used in your current OpenShift cluster.

oc get sc

# If the storage is ocs, get more details of the ocs storage with the command

# oc describe cephcluster ocs-storagecluster-cephcluster -n openshift-storage

# If the storage is portwox, get more details of the portworx storage with the command

#PX_POD=$(kubectl get pods -l name=portworx -n kube-system -o jsonpath='{.items[0].metadata.name}')

#kubectl exec $PX_POD -n kube-system -- /opt/pwx/bin/pxctl status

 

#Get a list of all current Cloud Pak for Data services and their versions

./cpd-cli status -n your-cp4d-namespace

5. Collect Cloud Pak for Data 3.5 usage information

For production upgrade, there's high chance that the upgrade has to be completed within a time window. The prioritization of the assemblies to be upgraded can help to reduce the risk of upgrade failure. The following table as an example can help to have an overview of the Cloud Pak for Data usage information. Based on this table, maybe you can upgrade the assemblies in use and also of high importance firstly and then proceed with the upgrade for other assemblies.

Service/Assembly name

Used (Y/N)

Size (Default/Small/Medium/Large)

 Level of importance High/Medium/Low

Lite

Y

Large

High

WSL

Y

Default

High

WML

Y

Default

High

WKC

Y

Large

High

Jupyter Notebooks for GPU

N

N/A

N/A

R Studio

Y

Default

High

Spark

N

N/A

N/A

SPSS Modeler

Y

Default

Medium

Data Virtualization

N

N/A

N/A

Db2Warehouse

N

N/A

N/A

Data Management Console

N

N/A

N/A

Cognos Dashboard

N

N/A

N/A

Watson Discovery

N

N/A

N/A

Watson Assistant

N

N/A

N/A

……

    

 

 

Streams

N

N/A

N/A

……

  

  

 

Summary
All the above information is for making the upgrade plan and getting prepared for it. And it can help to collect the must gather information which is directly related to logistics, planning, and preparation steps: 

  • Location of CPD installation (on-prem, which cloud, etc.):
  • In-place upgrade or on 2 different clusters?:
  • Current OCP version:
  • Target OCP version:
  • Current CPD version:
  • Target CPD version:
  • Number of nodes:
  • Node configuration (role of each node, CPU/Mem of each node):
  • List of CP4D services (and version of each) installed:
  • Number of CPD instances:
  • Any other applications running on top of CPD:
  • Current Storage type/version:
  • Storage to be upgraded (Y/N)?
  • Target storage type/version:
  • Data size:
  • Air-gapped or non-air-gapped?
  • Type of environment(s) (dev/test, staging, production):
  • Any application that uses CP4D services?
  • Target starting date of upgrade:
  • Upgrade venue (remote, on-site, etc.):
  • Others:

For any questions about the above must gather information, you can engage IBM Support by opening a CSP (Salesforce) case either using the CSP Console or IBM Support. 

0 comments
13 views

Permalink