Adding a database instance to an Azure AKS cluster using the Db2 Operator

Use the information in the following tables to determine the size requirements of your Db2 or Db2 Warehouse instance. Based on your selection, go to the list of Azure VM instance types to find the Azure VM instance type that's right for your database deployment. In addition to the sizing values shown in the tables, the instance type list shows other factors to consider, such as cost and region. 

For Online Transactional Processing (OLTP) database workloads, choose an instance from the General Purpose or Memory Optimized categories. 

Table 1. Sizing guidelines for Db2 OLTP on Azure AKS systems:

The following diagram show how storage is distributed in a Db2 multi-partition Warehouse formation: 

• NUM_NODES: The minimum number of VM nodes for the Azure cluster: 

  • For single-partition Db2 instances, use  1.

    export NUM_NODES=1

  • For single-partition Db2 Warehouse instances, use  1. 

    export NUM_NODES=1

  • For multi-partition (small) Db2 Warehouse instances, use 6. 

    export NUM_NODES=6

Create an Azure account 

Before you begin to create your Azure cluster, you need to have an Azure account. 

1. From a web browser, go to https://azure.microsoft.com/ . 

2. Follow the online instructions. 
   NOTE: You will be contacted by phone and be required to enter a verification code on your phone keypad.

Sign in with Azure CLI 

Azure provides numerous authentication methods. We describe the two most common methods bellow. 

• Interactively using device code flow which will open a browser page with the one-time-passcode (OTP) that you can enter into the CLI terminal to complete the login process: 

  az login

• Non-interactively by providing the credentials in the CLI command: 

  az login – u <user> -p <password>

Refer to Azure topic Sign in with Azure CLI for details on all the supported authentication methods. 

az role assignment create --assignee "${PRINCIPAL_ID}" --role "Contributor" --subscription "${SUBSCRIPTION_ID}" 

az group create --name ${RESOURCE_GROUP} --location ${LOCATION}

az aks create --resource-group ${RESOURCE_GROUP} --name ${CLUSTER} --vm-set-type VirtualMachineScaleSets --node-count 3 --node-vm-size Standard_D2_v3 --generate-ssh-keys --load-balancer-sku standard

az aks nodepool add --resource-group ${RESOURCE_GROUP} --cluster-name ${CLUSTER} --name ${NODE_POOL} --node-count ${NUM_NODES} --node-vm-size ${NODE_VM_SIZE}

az storage account create --name ${BLOCK_STORAGE_ACCOUNT} --resource-group ${RESOURCE_GROUP} --location ${LOCATION} --sku Premium_LRS --kind BlockBlobStorage 

az storage account create --name ${FILE_STORAGE_ACCOUNT} --resource-group ${RESOURCE_GROUP} --location ${LOCATION} --sku Premium_LRS --kind FileStorage

az aks update -n ${CLUSTER} -g ${RESOURCE_GROUP} --enable-disk-driver --enable-file-driver

kubectl create -f - <<EOF 
--- 
allowVolumeExpansion: true 
apiVersion: storage.k8s.io/v1 
kind: StorageClass 
metadata: 
  name: azurefile-nfs 
provisioner: file.csi.azure.com 
parameters: 
  protocol: nfs 
  skuName: Premium_LRS 
EOF 

parameters: 
  protocol: nfs 
  skuName: Premium_LRS
  storageAccount: ${FILE_STORAGE_ACCOUNT} 
  resourceGroup: ${RESOURCE_GROUP}

kubectl create -f - <<EOF 
--- 
allowVolumeExpansion: true 
apiVersion: storage.k8s.io/v1 
kind: StorageClass 
metadata: 
  name: azuredisk-premium 
provisioner: disk.csi.azure.com 
parameters: 
  skuName: Premium_LRS 
EOF 

az provider register --namespace Microsoft.NetApp --wait

az netappfiles account create --resource-group ${RESOURCE_GROUP} --location ${LOCATION} --account-name ${ANF_ACCOUNT}

#Get the NODE_RESOURCE_GROUP 

NODE_RESOURCE_GROUP=$(az aks show --name ${CLUSTER} --resource-group ${RESOURCE_GROUP} --query nodeResourceGroup -o tsv) 

#Get the vnet name for the cluster 

VNET_NAME=$(az network vnet list --resource-group ${NODE_RESOURCE_GROUP} --query [].name -o tsv)

#Get vnet id of the vnet 

VNET_ID=$(az network vnet show --resource-group ${RESOURCE_GROUP} --name ${VNET_NAME} --query "id" -o tsv)

#Create a subnet under the vnet that was created in the previous step 

az network vnet subnet create --resource-group ${RESOURCE_GROUP} --vnet-name ${VNET_NAME} --name ${ANF_SUBNET} --delegations "Microsoft.NetApp/volumes" --address-prefixes 10.0.0.0/28

az netappfiles pool create --resource-group ${RESOURCE_GROUP} --location ${LOCATION} --account-name ${ANF_ACCOUNT} --pool-name ${ANF_POOL} --size 4 --service-level Premium 

az netappfiles volume create -g ${RESOURCE_GROUP} --account-name ${ANF_ACCOUNT} --pool-name ${ANF_POOL} --name ${ANF_VOLUME} -l ${LOCATION} --service-level premium --usage-threshold 100 --file-path "unique-file-path" --vnet ${VNET_NAME} --subnet ${ANF_SUBNET} --protocol-types NFSv3 

kubectl create -f - <<EOF 
apiVersion: storage.k8s.io/v1 
kind: StorageClass 
metadata: 
  name: nfs-client 
provisioner: k8s-sigs.io/nfs-subdir-external-provisioner 
parameters: 
  archiveOnDelete: "false" 
EOF 

1. Log in to your Azure AKS cluster. 
2. Install the ibm-db2uoperator-catalog in the namespace where OLM is installed: 

   cat << EOF | kubectl create -f - 
   apiVersion: operators.coreos.com/v1alpha1
   kind: CatalogSource
   metadata:
     name: ibm-db2uoperator-catalog
     namespace: olm
   spec:
     displayName: IBM Db2U Catalog
     image: icr.io/cpopen/ibm-db2uoperator-catalog@sha256:13d8219d19d6980224200699c4c423332e64de5644b5e5564389012e1a3ff9c1
     publisher: IBM
     sourceType: grpc
     updateStrategy:
       registryPoll:
         interval: 45m
   EOF 

3. Create a namespace for installing the Db2 operator: 

   kubectl create namespace ${NAMESPACE}

4. Install an operator group in the namespace: 

   cat << EOF | kubectl create -f - 
   apiVersion: operators.coreos.com/v1 
   kind: OperatorGroup 
   metadata: 
     name: db2u-operator-group 
     namespace: ${NAMESPACE} 
   spec: 
     targetNamespaces: 
     - ${NAMESPACE} 
   EOF

5. Create a subscription in the namespace to deploy the Db2 operator:

   cat << EOF | kubectl create -f - 
   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
     name: ibm-db2uoperator-catalog-subscription
     namespace: ${NAMESPACE}
     generation: 1
   spec:
     channel: v110509.0
     name: db2u-operator
     installPlanApproval: Automatic
     source: ibm-db2uoperator-catalog
     sourceNamespace: olm
     startingCSV: db2u-operator.v110509.0.1
   EOF 

6. Check that the db2u-operator pod is deployed: 

   kubectl get pods -n ${NAMESPACE} | grep db2u-operator 

7. After the db2u-operator pod is up and running, run the YAML code to deploy your database instance. 
   Choose from the following: 

   • YAML for the Db2 instance.
   • YAML for the single-partition Db2 Warehouse instance.
   • YAML for the multi-partition Db2 Warehouse instance.
8. Check the status of your Db2uInstance: 

   kubectl get db2uinstance -n ${NAMESPACE} ${DB2U_INSTANCE}

   DB2U_INSTANCE is the name value set in the metadata section of the YAML code. For example, 

   name: db2oltp-test

9. When the STATE value returned is Ready, the instance is deployed successfully. 

   kubectl -n ${NAMESPACE} get db2uinstance ${DB2U_INSTANCE} 
   
   NAME                      STATE   MAINTENANCESTATE          AGE 
   
   db2oltp-test          Ready         None               6h8m 

10. Log on to the database engine pod as db2inst1: 

    kubectl -n ${NAMESPACE} exec -it $(oc get pods -n ${NAMESPACE} | grep ${DB2U_INSTANCE}-db2u-0 | awk '{print $1}') -- su - db2inst1

11. Connect to the database bludb on your Azure cluster: 

    db2 connect to bludb

kubectl create -f - << EOF 
--- 
apiVersion: v1 
kind: Service 
metadata: 
  name: ${LOAD_BALANCER_SVC} 
  namespace: ${NAMESPACE} 
spec: 
  ports: 
  - port: 50000 
    protocol: TCP 
    targetPort: 50000 
  selector: 
    app: ${DB2U_CLUSTER} 
    component: db2wh 
    formation_id: ${DB2U_CLUSTER} 
    role: db 
    type: engine 
  externalTrafficPolicy: Local 
  type: LoadBalancer 
EOF

kubectl get svc -n ${NAMESPACE} | grep ${LOAD_BALANCER_SVC} 
lb-db2-demo-eastus-001   LoadBalancer   10.0.247.179   20.127.178.10   50000:30856/TCP   14d 

curl -kv 20.127.178.10:50000 
*   Trying 20.127.178.10:50000... 
* Connected to 20.127.178.10 (20.127.178.10) port 50000 (#0) 
> GET / HTTP/1.1 
> Host: 20.127.178.10:50000 
> User-Agent: curl/7.79.1 
> Accept: */*