Cloud Pak for Data 4.0 Air Gap installation Key Points (part II)

Recommendation: Review the first part of Cloud Pak for Data 4.0 Air Gap installation Key Points (Part I) here.

We had already mirror images to the local docker repository, then we will focus on Cloud Pak for Data installation on this part.

Key Points 1: Create Catalog Source

[root@api.cpd401.cp.fyre.ibm.com ~]# cloudctl case launch \
>   --case ${OFFLINEDIR}/ibm-cp-common-services-1.6.0.tgz \
>   --inventory ibmCommonServiceOperatorSetup \
>   --namespace openshift-marketplace \
>   --action install-catalog \
>   --args "--registry myrepositroy:port --inputDir ${OFFLINEDIR} --recursive"
Welcome to the CASE launcher
Attempting to retrieve and extract the CASE from the specified location
[✓] CASE has been retrieved and extracted
Attempting to validate the CASE
[✓] CASE has been successfully validated
Attempting to locate the launch inventory item, script, and action in the specified CASE
[✓] Found the specified launch inventory item, action, and script for the CASE
Attempting to check the cluster and machine for required prerequisites for launching the item
Checking for required prereqs...
No requires section specified.
Required prereqs result: OK
Checking user permissions...
No user rules specified.
[✓] Cluster and Client Prerequisites have been met for the CASE
Running the CASE ibmCommonServiceOperatorSetup launch script with the following action context: installCatalog
Executing inventory item ibmCommonServiceOperatorSetup, action installCatalog : launch.sh
Checking arguments for install catalog action
-------------Create catalog source-------------
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: opencloud-operators
  namespace: openshift-marketplace
spec:
  displayName: IBMCS Operators
  publisher: IBM
  sourceType: grpc
  image: myrepositroy:port/cpopen/ibm-common-service-catalog:latest
catalogsource.operators.coreos.com/opencloud-operators created
check for any existing operator group in openshift-marketplace ...
no existing operator group found
-------------Create operator group-------------
operatorgroup.operators.coreos.com/common-service created
[✓] CASE launch script completed successfully
OK

[root@api.cpd401.cp.fyre.ibm.com ~]# oc get catalogsource -n openshift-marketplace opencloud-operators \
> -o jsonpath='{.status.connectionState.lastObservedState} {"\n"}'
READY ​

1.2  Create the IBM Cloud Pak for Data catalog source in openshift-marketplace namespace

[root@api.cpd401.cp.fyre.ibm.com ~]# cloudctl case launch \
>   --case ${OFFLINEDIR}/ibm-cp-datacore-2.0.3.tgz \
>   --inventory cpdPlatformOperator \
>   --namespace openshift-marketplace \
>   --action install-catalog \
>   --args "--inputDir ${OFFLINEDIR} --recursive"
Welcome to the CASE launcher
Attempting to retrieve and extract the CASE from the specified location
[✓] CASE has been retrieved and extracted
Attempting to validate the CASE
[✓] CASE has been successfully validated
Attempting to locate the launch inventory item, script, and action in the specified CASE
[✓] Found the specified launch inventory item, action, and script for the CASE
Attempting to check the cluster and machine for required prerequisites for launching the item
Checking for required prereqs...
No requires section specified.
Required prereqs result: OK
Checking user permissions...
No user rules specified.
[✓] Cluster and Client Prerequisites have been met for the CASE
Running the CASE cpdPlatformOperator launch script with the following action context: installCatalog
Executing inventory item cpdPlatformOperator, action installCatalog : launch.sh
-------------Installing catalog source-------------
Checking arguments for install catalog action
orig - icr.io/cpopen/ibm-cpd-platform-operator-catalog:2.0.0-amd64-134
mod - icr.io/cpopen/ibm-cpd-platform-operator-catalog:2.0.0-amd64-134
catalogsource.operators.coreos.com/cpd-platform created
[✓] CASE launch script completed successfully
OK

1.3 Create catalogsources for each servcies that you want to installed on Cloud Pak for Data ( please follow https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=tasks-configuring-your-cluster-pull-images#preinstall-cluster-setup__catalog-source)

Key Point 2: Install IBM Cloud Pak foundational services

If you are using Express installation, then you can skip this step.
IBM Cloud Pak® foundational services is a prerequisite for IBM® Cloud Pak for Data. IBM Cloud Pak foundational services is installed one time on the cluster and is used by any instances of Cloud Pak for Data or other IBM Cloud Paks that are installed on the cluster.

Follow the guide here
https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=tasks-installing-cloud-pak-foundational-services

• The IBM Cloud Pak foundational services operator installs the Operand Deployment Lifecycle Manager operator and the IBM NamespaceScope operator in the ibm-common-services project.
• The IBM Cloud Pak foundational services operator creates the CommonService custom resource.
• The Operand Deployment Lifecycle Manager operator creates the OperandRegistry, OperandConfig, and the OperatorBindInfo instances in the ibm-common-services project.

[root@api.cpd401.cp.fyre.ibm.com ~]# oc --namespace ibm-common-services get csv
NAME                                          DISPLAY                                VERSION   REPLACES                                      PHASE
ibm-common-service-operator.v3.10.0           IBM Cloud Pak foundational services    3.10.0    ibm-common-service-operator.v3.9.0            Succeeded
ibm-namespace-scope-operator.v1.4.0           IBM NamespaceScope Operator            1.4.0     ibm-namespace-scope-operator.v1.3.0           Succeeded
operand-deployment-lifecycle-manager.v1.8.0   Operand Deployment Lifecycle Manager   1.8.0     operand-deployment-lifecycle-manager.v1.7.0   Succeeded

Key Point 3:Creating operator subscriptions

3.1 Creating an operator subscription for the IBM Cloud Pak for Data platform operator

3.2 Creating operator subscriptions for Cloud Pak for Data Services operator

You can follow the guide here
https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=tasks-creating-operator-subscriptions

Key Point 4: Installation of CPD control panel 
4.1 Enable the IBM Cloud Pak for Data platform operator and the IBM Cloud Pak foundational services operator to watch the project where you will install IBM Cloud Pak for Data:

4.2 Create a custom resource to install Cloud Pak for Data.

4.3 Verify the installation

Once the installation is done, you can get the route and admin password to login. Please note that for CPD 4.x, the admin password is not to set "password"  by default like CPD 3.x before.  You can get the initial password for the admin user by

oc extract secret/admin-user-details --keys=initial_admin_password --to=-

Please follow the guide here
https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=installing-cloud-pak-data


Key Point 5: Installation of  Cloud Pak for Data services

Normally, we need to create corresponding custom resource for each service.
Please follow the guide here
https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=integrations-services