Installing Policy Control Function Cloud Native Services

To install Policy Control Function (PCF) cloud native services, do this:

Download the patches you want to apply from My Oracle Support:
HTTPS://SUPPORT.ORACLE.COM
Sign in with your user name and password.
Click Patches and Updates, and search for the patch number.
Download the PCF 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,ocpcf-pkg-1.5.0.0.0.tgz
Untar the PCF package file to get PCF docker image tar file.
tar -xvzf ReleaseName-pkg-Releasenumber.tgz

The directory consists of the following:
- PCF Docker Images File:
  ocpcf-images-1.5.0.tar
- Helm File:
  ocpcf-1.5.0.tgz
- Readme txt File:
  Readme.txt (Contains cksum and md5sum of tarballs)
Load the ocpcf-images-1.5.0.tar file into the Docker system
```
docker load --input /IMAGE_PATH/ocpcf-images-1.5.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 ocpcf/pcf_smservice:1.5.0 CUSTOMER_REPO/pcf_smservice:1.5.0
docker push CUSTOMER_REPO/pcf_smservice:1.5.0
 
docker tag ocpcf/pcf_ueservice:1.5.0 CUSTOMER_REPO/pcf_ueservice:1.5.0
docker push CUSTOMER_REPO/pcf_ueservice:1.5.0
 
docker tag ocpcf/pcf-amservice:1.5.0 CUSTOMER_REPO/pcf-amservice:1.5.0
docker push CUSTOMER_REPO/pcf-amservice:1.5.0
 
docker tag ocpcf/pcf_userservice:1.5.0 CUSTOMER_REPO/pcf_userservice:1.5.0
docker push CUSTOMER_REPO/pcf_userservice:1.5.0
 
docker tag ocpcf/ocpm_pre:1.5.0 CUSTOMER_REPO/ocpm_pre:1.5.0
docker push CUSTOMER_REPO/ocpm_pre:1.5.0
 
docker tag ocpcf/diam-connector:1.5.0 CUSTOMER_REPO/diam-connector:1.5.0
docker push CUSTOMER_REPO/diam-connector:1.5.0
 
docker tag ocpcf/diam-gateway:1.5.0 CUSTOMER_REPO/diam-gateway:1.5.0
docker push CUSTOMER_REPO/diam-gateway:1.5.0 
 
docker tag ocpcf/ocpm_config_server:1.5.0 CUSTOMER_REPO/ocpm_config_server:1.5.0
docker push CUSTOMER_REPO/ocpm_config_server:1.5.0
 
docker tag ocpcf/ocpm_cm_service:1.5.0 CUSTOMER_REPO/ocpm_cm_service:1.5.0
docker push CUSTOMER_REPO/ocpm_cm_service:1.5.0
 
docker tag ocpcf/nrf_clientservice:1.5.0 CUSTOMER_REPO/nrf_clientservice:1.5.0
docker push CUSTOMER_REPO/nrf_clientservice:1.5.0

docker tag ocpcf/ocpm_queryservice:1.5.0 CUSTOMER_REPO/ocpm_queryservice:1.5.0
docker push CUSTOMER_REPO/ocpm_queryservice:1.5.0
 
docker tag ocpcf/audit_service:1.5.0 CUSTOMER_REPO/audit_service:1.5.0
docker push CUSTOMER_REPO/audit_service:1.5.0 
 
docker tag ocpcf/readiness-detector:1.5.0 CUSTOMER_REPO/readiness-detector:1.5.0
docker push CUSTOMER_REPO/readiness-detector:1.5.0
 
docker tag ocpcf/perf_info:1.5.0 CUSTOMER_REPO/perf_info:1.5.0
docker push CUSTOMER_REPO/perf_info:1.5.0
 
docker tag ocpcf/app_info:1.5.0 CUSTOMER_REPO/app_info:1.5.0
docker push CUSTOMER_REPO/app_info:1.5.0

docker tag ocpcf/ocingress_gateway:1.5.1 CUSTOMER_REPO/ocingress_gateway:1.5.1
docker push CUSTOMER_REPO/ocingress_gateway:1.5.1
 
docker tag ocpcf/ocegress_gateway:1.5.1 CUSTOMER_REPO/ocegress_gateway:1.5.1
docker push CUSTOMER_REPO/ocegress_gateway:1.5.1
 
docker tag ocpcf/configurationinit:0.3.0 CUSTOMER_REPO/configurationinit:0.3.0
docker push CUSTOMER_REPO/configurationinit:0.3.0
 
docker tag ocpcf/configurationupdate:0.3.0 CUSTOMER_REPO/configurationupdate:0.3.0
docker push CUSTOMER_REPO/configurationupdate:0.3.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 ocpcf-custom-values-1.5.0.yaml file with the required input parameters. To customize the file, see Customizing Policy Control Function.
Go to the helm chart directory:
```
cd ocpcf/
```
Install PCF by entering this command:
```
helm install HELM_CHART_PATH/pcf-1.5.0.tgz --name PCF_NAME --namespace PCF_NAMESPACE -f CUSTOM_VALUES_YAML_FILE
```
where:
HELM_CHART_PATHis the location of the helm chart extracted from ocpcf-pkg-1.5.0.tgz file

PCF_NAME is the release name used by helm command.

PCF_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/pcf-1.5.0.tgz --name ocpcf --namespace ocpcf -f ocpcf-custom-values-1.5.0.yaml
```
Refer Customizing Policy Control Function for the sample yaml file.
Check the deployment status by entering this command
```
helm ls PCF_NAME
```
where:

PCF_NAME is the release name used by helm command.
For example:
```
helm ls ocpcf
```
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 PCF_NAMESPACE
```
where:
PCF_NAMESPACE is the name space in which to create PCF Kubernetes objects. All the PCF microservices are deployed in this kubernetes namespace.
For example:
```
kubectl get pod -n ocpcf
```
You will see the status as Running for all the nodes if the deployment has been done successfully.