IBM Db2® Warehouse is a high-performing analytic engine that combines in-memory processing with integrated parallel in-database analytics. Db2 Warehouse provides users with the flexibility to leverage the infrastructure of their choice in a private cloud environment. In-database analytics capabilities in Db2 Warehouse include open source analytics with R and Apache Spark, out-of-the-box analytic stored procedures, and geo-spatial analytic functions.

IBM Cloud Private is an application platform for developing and managing containerized on-premises applications. It is an integrated environment for managing containers and includes the container orchestrator Kubernetes, a private image repository, a management console, and
monitoring frameworks. IBM Cloud Private also includes a GUI providing a centralized location from where you can deploy, manage, monitor, and scale your applications.

This tutorial provides step-by-step instructions for deploying Db2 Warehouse on IBM Cloud Private 2.1.0. The instructions here apply to Db2 Warehouse Developer-C Edition and Db2 Warehouse Enterprise.

In this tutorial, you will install, configure, and deploy:

Installing IBM Cloud Private

The first step is to install and configure IBM Cloud Private in your private cloud environment. To do this, refer to the Installing IBM Cloud Private documentation.

Your IBM Cloud Private administrator will provide a URL for you to access your cluster’s dashboard (shown in the screenshot below) after you complete the installation.

IBM Cloud Dashboard private

Now it’s time to set up Db2 Warehouse.

Persistent storage volume creation

Persistent storage volume is required if dynamic provisioning is not set up. You can create a persistent storage volume via the IBM Cloud Private interface or through a YAML file.

Create a persistent storage volume

Log in to the IBM Cloud Private console with the URL and logon credentials provided by the administrator. The default port is 8443 (sample URL: https://9.37.194.130:8443/console).

log in screen

There are two options for managing persistent storage volume:

  • Using a pre-defined PersistentVolume or PersistentVolumeClaim setup prior to the deployment of Db2 Warehouse chart
  • Using Kubernetes dynamic provisioning

When defining the persistent volume, choose these default values:

  • Enable persistence for this deployment: true (default)
  • Use dynamic provisioning for persistent volume: false (default)

Create a PersistentVolume within the IBM Cloud Private UI: Platform > Storage > Create Persistent Volume.

In the Create PersistentVolume window, add the following to the General tab, as shown below:

  • Name (storage volume)
  • Capacity (Storage): 25 (or more)
  • Unit: Gi
  • Access modes: Read write once
  • Reclaim policy: Retain
  • Storage type: Host path

Create PersistentVolume window

On the Parameters tab: The root path defaults to /mnt/clusterfs, but this can be any path, depending on the available storage. The volume name is lowercase. Click Create and the persistent storage volume is created.

Install Db2 Warehouse Developer-C from the ICP catalog

From the dashboard, on the menu on the left, click Catalog.

catalog

The catalog opens to show you the various installation choices.

Click ibm-db2warehouse-dev (Db2 Warehouse Developer-C).

Catalog choices

After you click ibm-db2warehouse-dev, a window opens, showing you additional details about prerequisites and setup options. Click Configure.

Configure

Accept the licenses and configure

After accepting the license terms, specify values for the following
parameters or accept the defaults. Items in bold are mandatory; the rest
have defaults you can choose.

  • Name: BLUADMPASS:
  • password: “changemeplease” — Password is used for the bluadmin user
  • persistenceVolume: useDynamicProvisioning: false
  • persistenceVolumeClaimSettings1: storageClassName: “”
  • persistenceVolumeClaimSettings2: existingClaimName: “”
  • persistenceVolumeClaimSettings3: size: 25Gi — Cannot be less than specified default, 25Gi.
  • Resources: requests: cpu: 1000m memory: 8Gi — For both MEMORY and CPU, cannot be less than the specified default, 1000m and 8Gi.

configuration

At this point, the Db2 Warehouse Developer-C container is pulled and ready for install. The progress can be monitored on the IBM Cloud Private dashboard.

installation complet

Helm releases

Monitor deployment and configure the client for kubectl operations.

Installing kubectl

kubectl is usually installed on the IBM Cloud Private master node. If you are running the commands from the master node, kubectl is already installed.

On the IBM Cloud Private dashboard, click Configure client from the top right-hand side of the page.

Dashboard

Copy the commands in the Configure kubectl window and paste them in to a putty session of the node.

Configure kubectl

The next steps are to monitor the setup and ensure the installation is complete. After you set up the Kubenertes CLI environment, you need to get the name of the container.

Note: The plan for future releases is to provide the ability to monitor progress via a console, so some of these steps might be redundant.

Get the container name

To get the name of the pod (/container), use a putty session, connect to the host node, and run the following command:

-bash-4.2# kubectl get pod
NAME READY STATUS RESTARTS AGE
db2w-release-ibm-db2warehouse-dev-304866531-rbw0s 0/1
ContainerCreating 0 6m
-bash-4.2#

Log on to the Db2 Warehouse node using the IP address and run kubectl exec -it <pod name> bash to check the progress of the instance creation.

Putty window

From the menu options on the top left-hand of the console, click Workloads > Deployment. A list of deployment results displays.

deployments

From the list that results, verify that the Db2 Warehouse container is created. You can click on it to see the node details, as shown below.

nodes

Db2 Warehouse deployment is complete

Now that you’ve verified that the deployment is complete, the console logon opens. Click the Db2 Warehouse container endpoint link (access port 8443) to log on. You have to manually type https:// on the URL of the newly opened page.

Note: In the next release, https:// will be embedded in the URL when port8443-https is clicked.

expose details

The installation is complete.

Log on using bluadmin and the password you set earlier.

log on window

Db2 Warehouse Developer-C SMP is now available on IBM Cloud Private for further exploration.

welcome to IBM Db2 Warehouse window

You will see that on the panel Workloads > Deployments > <nameofapplication> that Db2 Warehouse is now available for use.

IBM Cloud Private makes managing your Db2 databases easy by creating an ecosystem where you can deploy Data Server Manager (DSM) within the same cluster.

Conclusion

We hope this step-by-step tutorial helped you install Db2 Warehouse onto your IBM Cloud Private 2.1 cluster. You are now ready to explore the power of analytics. Feel free to post any comments or questions below.

Additional resources

Knowledge Center

Db2 learning center

Webinar: IBM Db2 for IBM Cloud Private

Data Warehousing on Private Cloud and beyond

by Mitesh Shah, Product Manager, Hybrid Data Management Platform, IBM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mitesh Shah is the product manager for Hybrid Data Management platform of offerings, mainly Data Warehousing solutions, uniquely positioned for virtual private clouds and platforms that support Docker container technology. He has broad experience around various facets of software development along with business systems analysis, and program testing; known for ability to analyze complex issues with an analytical mindset, incubate and streamline innovative solutions, and promote a consensus-driven work environment that contributes to on-time and on-budget delivery. Throughout his career, Mitesh has enjoyed a focus on helping clients address their data management and solution architecture needs.

Join The Discussion

Your email address will not be published. Required fields are marked *