The purpose of this questionnaire is to help get an comprehensive overview of the Cloud Pak for Data environment before the upgrade. It is comprised of Cloud Pak for Data services, OpenShift cluster, storage and infrastructure related information. This information is critical for making a comprehensive upgrade plan to secure a successful outcome.
Note:
Some commands are provided below to help you collect the information. To run these commands, log into the OpenShift cluster as the cluster administrator role is required.
1. Current CPD version
2. Target CPD version
3. Current OCP version
Check the OpenShift cluster version with oc client
oc get clusterversion
4.Target OCP version
5. Current storage type and version (ODF/OCS, Fusion Data Foundation, Spectrum Scale, Portworx, NFS, etc)
1) If the storage is ODF (renamed from OCS), get more details of the ODF storage with the command:
oc describe cephcluster ocs-storagecluster-cephcluster -n openshift-storage
2) If the storage is Spectrum Scale, is the Spectrum Scale Container Native (with CSI driver) used? If yes, what's the version of the Spectrum Scale storage cluster (remote cluster)?
3) 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
Note:
Separate license (Portworx Enterprise) is required starting from CP4D 4.5
4) If the storage is NFS, what's the version of the NFS protocol in use ?
6. Target storage type and version
7. Number of CPD instances
How many CPD instances are sharing the same OCP cluster?
8. List of CPD services (and version of each) installed in each CPD instance’s namespace
1) If the current CPD version is 3.5.x, get a list of all current CPD services and their versions with below command.
cpd-cli status -n <cpd-namespace>
Note: You need to replace the placeholder accordingly when running this command.
2) If the current CPD version is 4.0.x or above, get a list of all current CPD services and their versions with below command.
Log into OCP
cpd-cli manage login-to-ocp /
--username=${OCP_USERNAME} /
--password=${OCP_PASSWORD} /
--server=${OCP_URL}
or
cpd-cli manage login-to-ocp /
--server=${OCP_URL} /
--token=${OCP_TOKEN}
Get CPD components status
cpd-cli manage get-cr-status /
--cpd_instance_ns=${PROJECT_CPD_INSTANCE}
If you have problem with cpd-cli command, use this alternative command to get CPD components status
oc project <cpd-namespace>
for i in $(oc get crd | grep cpd.ibm.com | awk '{ print $1 }'); do oc get $i | grep -v "NAME" ; oc get $i $(oc get $i | grep -v "NAME" | awk '{ print $1 }') -o jsonpath="{.spec.scaleConfig}{'\n'}" ; oc get $i $(oc get $i | grep -v "NAME" | awk '{ print $1 }') -o jsonpath="{.status}{'\n'}";echo "---------$i------------" ;done
9. Is CPD System installed? If yes, please run "ap version" and share the output.
Note: CPDS may need to be upgraded first if it is running at an incompatible version with the target CPD version.
10. Is it in-place upgrade or the upgrade on 2 separate clusters with one acting as staging environment?
11. Collect Cloud Pak for Data usage information
For production upgrade, there's high chance that the upgrade has to be completed within a time window. The prioritization of the services 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, you can upgrade the services of high importance firstly and then proceed with the upgrade for other services.
|
Service name
|
Used (Y/N)
|
Size (Default/Small/Medium/Large)
|
Level of importance （High/Medium/Low）
|
|
WS (sample)
|
Y
|
Default
|
High
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
12. Number of OpenShift nodes
Collect information about the number of master nodes and worker nodes in your OpenShift cluster.
oc get nodes --show-labels
13. The location of your Cloud Pak for Data installation (On-premise, which cloud, etc)
14. Operating System of the Bastion node
Bastion node is also known as the client workstation on which you can run the oc client to operate the OpenShift cluster.
Note: RHEL V8 or equivalent is recommended.
15. Private container registry
1)Is there an private container registry available to be used by the Cloud Pak for Data?
Strongly recommend the use of private container registry. If you already have one, please indicate amount of available free storage space, 500GB ~ 800G is recommended, and the required storage space is vary from the CPD componenets and services to be upgraded.
Note: You cannot use the integrated OpenShift Container Platform registry. It does not support multi-architecture images and is not compliant with the Docker Image Manifest Version 2, Schema 2.
16. Internet access
Does the OpenShift cluster have internet access? If not, is there a proxy for accessing white-listed sites?
17. Type of environment(s) (Dev/Test, Staging or Production)
18. Any application that uses CPD services?
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.
19. Target starting date and expected ending date of the upgrade?
20. Please share relevant information if applicable (optional):
- Any RSI patches or Hotfixes applied in the cluster? If yes, please share the detailed information accordingly.
- If Db2 Warehouse or Db2 OLTP installed, any dedicated worker nodes used?
- If Data Virtualization (renamed as Watson Query since CPD 4.6) service is deployed, is it using external JDBC driver?
- Any custom images used? If yes, please share the detailed information accordingly.
#CloudPakforData
#Highlights-home#data-highlights-home