Skip to content

Commit 0a1f9d1

Browse files
committed
Updates module name in metadata and readme
Signed-off-by: Sean Sundberg <[email protected]>
1 parent 2b4ba8f commit 0a1f9d1

File tree

3 files changed

+45
-9
lines changed

3 files changed

+45
-9
lines changed

README.md

Lines changed: 43 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
1-
# CP4D - DB2 Warehourse Gitops terraform module
1+
# CP4D - DB2 Warehouse service gitops module
22

3-
### DB2WH Pre-Req
3+
This module populates a gitops repository with the resources necessary to provision the underlying DB2 Warehouse services that a pre-requisites to create a DB2 Warehouse instance. After this module is provisioned a DB2 Warehouse instance can then be created manually by following the steps below or by provisioning the [gitops-cp-db2wh](https://github.com/cloud-native-toolkit/terraform-gitops-cp-db2wh) module.
4+
5+
## DB2WH Pre-Req
46

57
Ensure that a cluster administrator completed the required Pre-installation tasks for your environment. Specifically, verify that a cluster administrator completed the following tasks:
68

@@ -72,6 +74,45 @@ Run this CLI and check if the DB2WHService completed.
7274

7375
Db2 Warehouse is ready when the command returns "Completed".
7476

77+
### Create DB2WH database instance manually
78+
79+
#### Grant additional privileges
80+
81+
You must grant additional privileges to enable the web console to validate the CPU and memory values that you select for your deployment.
82+
83+
1. To add these privileges, run the following command on the OpenShift® cluster:
84+
85+
```shell
86+
oc adm policy add-cluster-role-to-user system:controller:persistent-volume-binder system:serviceaccount:${NAMESPACE}:zen-databases-sa
87+
```
88+
89+
`${NAMESPACE}` refers where you have created the DB2OLTP instances
90+
91+
2. After you run the command, the console is able to validate your selections by checking the available number of nodes on the cluster, whether the nodes are properly labeled and tainted, and the amount of available CPU and memory.
92+
93+
#### Create the instance from the console
94+
95+
You can manually create the database for DB2WH by following the instructions https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=warehouse-creating-database-deployment
96+
97+
> This step will create the database on the cluster using CP4D Console
98+
99+
This will create a database using many of the default values. You can adjust through the process for any resources you wish to change to support your requirements.
100+
101+
![DB2WH DB Instance ](images/db2wh-db.jpg)
102+
103+
1. Login to CPD console
104+
2. From the hamburger menu select "Data->Databases"
105+
3. Click **Create a database** and select a database type. Click **Next**.
106+
4. On the "Configure" step, provide the database name, number of nodes, CPU per node, and memory per node. Click **Next**.
107+
5. On the "Advanced configuration" step, select `multiple logic nodes` and the `Analytics` workload. Click **Next**.
108+
6. On the "System storage" step, select `portworx-db2-rwx-sc` and size of `100 GB`. Click **Next**.
109+
7. On the "User storage" step, select `portworx-db2-rwx-sc (RWO with 4K block size)`, set the size to `100 GB`, and the access mode to `ReadWriteOnce`. Click **Next**.
110+
8. On the "Backup storage" step, click **Create new Storage**, select `Use storage template`, set the storage class to `portworx-db2-rwx-sc`, and set the size to `100 GB`. Click **Next**.
111+
9. On the "Transaction logs storage" step, select `Use storage template`, set the storage class to `portworx-db2-rwx-sc (RWO with 4K block size)`, and the size to `100 GB`. Click **Next**.
112+
10. On the "Temporary table spaces storage" step, select `Use storage template`, set the storage class to `portworx-db2-rwx-sc (RWO with 4K block size)`, and set the size to `100 GB`. Click **Finalize**.
113+
114+
As a result, Database for DB2WH will be created.
115+
75116
### DB2WH Service (instance) removal - Finalizer
76117
77118
Run this CLI and remove the finalizer value from the YAML as sometimes DB2WH service getting stuck.
@@ -86,4 +127,3 @@ Run this CLI and remove the finalizer value from the YAML as sometimes DB2WH ser
86127
87128
- [DB2 Warehouse Knowledge Center](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=services-db2-warehouse)
88129
89-

images/db2wh-db.jpg

327 KB
Loading

module.yaml

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
name: gitops-cp-db2wh
1+
name: gitops-cp-db2wh-service
22
type: terraform
3-
description: ""
3+
description: "Module to populate a GitOps repo with the resources to deploy the underlying DB2 Warehouse services from CP4D required to create a DB2 Warehouse instance"
44
tags:
55
- tools
66
- gitops
@@ -18,10 +18,6 @@ versions:
1818
refs:
1919
- source: github.com/cloud-native-toolkit/terraform-gitops-namespace.git
2020
version: ">= 1.0.0"
21-
# - id: gitops-db2
22-
# refs:
23-
# - source: github.com/cloud-native-toolkit/terraform-gitops-db2u-operator.git
24-
# version: ">= 0.0.1"
2521
- id: gitops-cp4d-instance
2622
refs:
2723
- source: github.com/cloud-native-toolkit/terraform-gitops-cp4d-instance.git

0 commit comments

Comments
 (0)