NF Installation in the cluster

Introduction

This section explains the steps to be followed by NF teams to access OCCNE cluster for installing NF applications in OCCNE cluster.

Procedure Steps

Table 3-17 Procedure to install NF in OCCNE Cluster

Steps Procedure Description
1.

Access Bastion Host of OCCNE cluster Login to the Bastion Host with user account - "admusr" using the IP supplied from: Installation Preflight Checklist
2.

Configure Bastion Host to access the cluster
  1. The cluster details/configs are present in /var/occne/ folder. Modify the bashrc file using the below command.
    # su to root user
    $ sudo su
      
    # cd to /root directory
    $ cd /root
     
    # edit bashrc file to add cluster details  
    $ vi .bashrc
  2. Add the below 2 lines to the above bashrc file by substituting the cluster_name with the required cluster.
    # Add below cluster details to bashrc file 
    $ export KUBECONFIG=/var/occne/<cluster_name>/artifacts/admin.conf
  3. Source bashrc file to reflect the changes made. Command to source bashrc file:
    $source.bashrc 
3.

Install NF applications using HELM Run the HELM install command to install NF using HELM chart.

Note: The following command is a sample install command, for complete NF installation procedure, refer to specific NF Installation Guide.

# cd to the application directory
$ cd <directory for NF application>
# HELM chart should be present in the repository with the chart name specified in the below command  
$ helm install <CHART_NAME> --name <NF_NAME> --namespace <NAMESPACE_VALUE>
 
Example:
$ cd /home/admusr/ocscp/ocscp-pkg-1.2.0.0.0
$ /usr/local/bin/helm install -f ocscp_values.yaml --name ocscp ocscp --namespace ocscp
4.

Verify NF Installation
  1. Once NF application is installed using the above HELM Install command, Run the below command to check the status of NF application. Verify the NF application is deployed correctly:
    $ kubectl.sh get pods --namespace=<NAMESPACE_VALUE>
  2. To verify if the above command was executed successfully and whether the NF Application was installed properly, the output shown below can be taken as reference. Output:
    NAME READY STATUS RESTARTS AGE<NF_NAME>1/1Running098m
  3. The NF services deployed and exposed can be verified by using the below command. Verify the NF service is deployed correctly:
    $ kubectl.sh get service --namespace=<NAMESPACE_VALUE> 
  4. To verify if the above command was executed successfully and whether the NF service was installed properly, the output shown below can be taken as reference.
    NAME                   TYPE           CLUSTER-IP      EXTERNAL-IP    PORT(S)        AGE
    <NF_NAME>              ClusterIP      10.233.26.162   <none>         9200/TCP       8d
     
    Example:
    ocscp         scp-worker                                      LoadBalancer   10.233.28.222   10.75.207.193   8001:31323/TCP,8000:31903/TCP                               2d
    ocscp         scpc-config-svc                                 LoadBalancer   10.233.41.199   10.75.207.166   8081:30067/TCP                                              2d
    ocscp         scpc-pilot                                      ClusterIP      10.233.22.153   <none>          15003/TCP,15005/TCP,15007/TCP,15010/TCP,8080/TCP,9093/TCP   2d
    ocscp         scpc-soothsayer-svc                             ClusterIP      10.233.7.220    <none>          8084/TCP,8080/TCP,8082/TCP,8083/TCP,8888/TCP                2d