Installing the Binding Support Function Cloud Native Deployment Package

3 Installing the Binding Support Function Cloud Native Deployment Package

This chapter describes how to install the BSF cloud native deployment package on a cloud native environment.

Installing Binding Support Function Cloud Native Services

To install Binding Support Function (BSF) cloud native services, do this:

Go to the Oracle software delivery Web site:
http://edelivery.oracle.com
Sign in with your user name and password.
Search for Binding Support Function and select the BSF software pack from the search results.
Download the BSF package file. Package is named as follows:
ReleaseName-pkg-Releasenumber.tgz

where:

ReleaseName is a name which is used to track this installation instance.

Releasenumber is the release number.

For example,ocbsf-pkg-1.4.0.0.0.tgz
Untar the BSF package file to get BSF docker image tar file.
tar -xvzf ReleaseName-pkg-Releasenumber.tgz

This command results into ReleaseName-pkg-Releasenumber directory.

The directory consists of the following:
- BSF Docker Images File:
  ocbsf-images-1.4.0.tar
- Helm File:
  ocbsf-1.4.0.tgz
- Readme txt File:
  Readme.txt (Contains cksum and md5sum of tarballs)
Load the ocbsf-images-1.4.0.tar file into the Docker system
```
docker load --input /IMAGE_PATH/ocbsf-images-1.4.0.tar
```
Verify that the image is loaded correctly by entering this command:
```
docker images
```

Create a new tag for each imported image and push the image to the customer docker registry by entering this command:

docker tag ocbsf/bsf_management_service:1.4.0 CUSTOMER_REPO/bsf_management_service:1.4.0
docker push CUSTOMER_REPO/bsf_management_service:1.4.0
 
docker tag ocbsf/diam-connector:1.4.0 CUSTOMER_REPO/diam-connector:1.4.0
docker push CUSTOMER_REPO/diam-connector:1.4.0
  
docker tag ocbsf/diam-gateway:1.4.0 CUSTOMER_REPO/diam-gateway:1.4.0
docker push CUSTOMER_REPO/diam-gateway:1.4.0
 
docker tag ocbsf/readiness-detector:1.4.0 CUSTOMER_REPO/readiness-detector:1.4.0
docker push CUSTOMER_REPO/readiness-detector:1.4.0
 
docker tag ocbsf/ocpm_cm_service:1.4.0 CUSTOMER_REPO/ocpm_cm_service:1.4.0
docker push CUSTOMER_REPO/ocpm_cm_service:1.4.0
  
docker tag ocbsf/nrf_clientservice:1.4.0 CUSTOMER_REPO/nrf_clientservice:1.4.0
docker push CUSTOMER_REPO/nrf_clientservice:1.4.0
  
docker tag ocbsf/ocpm_config_server:1.4.0 CUSTOMER_REPO/ocpm_config_server:1.4.0
docker push CUSTOMER_REPO/ocpm_config_server:1.4.0
  
docker tag ocbsf/perf_info:1.4.0 CUSTOMER_REPO/perf_info:1.4.0
docker push CUSTOMER_REPO/perf_info:1.4.0
 
docker tag ocbsf/app_info:1.4.0 CUSTOMER_REPO/app_info:1.4.0
docker push CUSTOMER_REPO/app_info:1.4.0
 
 
docker tag ocbsf/apigateway:1.0.0 CUSTOMER_REPO/ocpm_apigateway:1.4.0
docker push CUSTOMER_REPO/ocpm_apigateway:1.4.0

where:

CUSTOMER_REPO is the docker registry address having Port Number, if registry has port attached.

Note:

For OCCNE, copy the package to bastion server and use localhost:5000 as CUSTOMER_REPO to tag the images and push to bastion docker registry.

Note:

You may need to configure the Docker certificate before the push command to access customer registry via HTTPS, otherwise, docker push command may fail.

Create the customize ocbsf-custom-values-1.4.0.yaml file with the required input parameters. To customize the file, see Customizing Binding Support Function .
Go to the helm chart directory:
```
cd ocbsf-pkg-1.4.0.0.0
```
Install BSF by entering this command:
```
helm install HELM_CHART_PATH/bsf-1.4.0.tgz --name BSF_NAME --namespace BSF_NAMESPACE -f CUSTOM_VALUES_YAML_FILE
```
where:
HELM_CHART_PATHis the location of the helm chart extracted from ocbsf-pkg-1.4.0.tgz file

BSF_NAME is the release name used by helm command.

BSF_NAMESPACE is the deployment namespace used by helm command.

CUSTOM_VALUES_YAML_FILE - is the name of the custom values yaml file (including location).
For example:
```
helm install /home/cloud-user/bsf-1.4.0.tgz --name ocbsf --namespace ocbsf -f ocbsf-custom-values-1.4.0.yaml
```
Check the deployment status by entering this command
```
helm status --name BSF_NAME
```
where:

BSFNAME is the release name used by helm command.
For example:
```
helm status --name ocbsf
```
You will see the status as DEPLOYED if the deployment has been done successfully.
Execute the following command to get status of pods
```
kubectl get pod -n BSF_NAMESPACE
```
where:
BSF_NAMESPACE is the name space in which to create BSF Kubernetes objects. All the BSF microservices are deployed in this kubernetes namespace.
For example:
```
kubectl get pod -n ocbsf
```
You will see the status as Running for all the nodes if the deployment has been done successfully.