To connect Db2
Big SQL to an IBM Storage Scale object store, you must configure Db2
Big SQL to enable path style access for the object
store connection.
About this task
Best practice: You can run the commands in
this task exactly as written if you set up environment variables. For instructions, see
Setting up installation environment
variables.
Ensure that you source the
environment variables before you run the commands in this task.
Procedure
- Log in to Red Hat®
OpenShift® Container Platform as an instance
administrator.
${OC_LOGIN}
Remember:
OC_LOGIN is an alias for the oc login
command.
- Identify the Db2
Big SQL instance ID:
oc get cm -l component=db2bigsql -o custom-columns="Instance Id:{.data.instance_id},Instance Name:{.data.instance_name},Created:{.metadata.creationTimestamp}"
-
Back up the Db2
Big SQL service custom
resource:
oc get bigsql bigsql-<instance-id> -o yaml > bigsql-<instance-id>-bak.yaml
- Open the custom resource for editing:
oc edit bigsql bigsql-<instance-id>
- In the
s3 section, locate the line for the endpoint, and after this
line, set pathStyleAcess to true by adding the following line
after the endpoint:
Important: Make sure that the indentation is in line with the endpoint.
endpoint: s3.eu-central-1.amazonaws.com
pathStyleAccess: true
- Save the update and exit the editor:
- Wait 2 minutes for the Db2
Big SQL
custom resource state to return Ready:
oc get bigsql bigsql-<instance-id>
-
Get the name of the Db2
Big SQL head
pod:
head_pod=$(oc get pod -l app=bigsql-<instance_id>,name=dashmpp-head-0 --no-headers=true -o=custom-columns=NAME:.metadata.name)
- Set the required signing-algorithm for the object store connection by running the
following command:
oc exec -i $head_pod -- bash -c 'db2uctl adm bigsql config --key fs.s3a.signing-algorithm --value S3SignerType'
- Restart Db2
Big SQL:
oc exec -i $head_pod -- sudo su - db2inst1 -c "bigsql stop; bigsql start"
- Optional: Run a smoke test:
oc exec -i $head_pod -- sudo su - db2inst1 -c "source ~/.bashrc; bigsql-admin -smoke -o<bucketname>"