Go to primary content
Oracle® Communications Service Communication Proxy (SCP) Cloud Native Installation Guide
Release 1.0
F12352-01
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Prerequisites

Following are the prerequisites to install and configure SCP:

SCP Software

Following software are required as must to deploy SCP:

Table 2-1 SCP Software

Software Version
Kubenetes v1.12.5
HELM v2.11.0

Other services may need to be deployed according to the requirement of services. Following are software details:

Table 2-2 SCP Services

Software Chart Notes
elasticsearch elasticsearch-1.21.1 Needed for Logging
elastic-curator elasticsearch-curator-1.2.1 Needed for Logging
elastic-exporter elasticsearch-exporter-1.1.2 Needed for Logging
logs fluentd-elasticsearch-2.0.7 Needed for Logging
kibana kibana-1.5.2 Needed for Logging
grafana grafana-2.2.0 Needed for Metrics
prometheus prometheus-8.8.0 Needed for Metrics
prometheus-node-exporter prometheus-node-exporter-1.3.0 Needed for Metrics
metallb metallb-0.8.4 Needed for External IP
metrics-server metrics-server-2.4.0 Needed for Metric Server
tracer jaeger-0.8.3 Needed for Tracing

Note:

In case above services are needed and software are not installed in CNE. Install all the required software before proceeding for SCP Installation.

Network access

The Kubernetes cluster hosts must have network access to:

  • Local docker image repository where the SCP images are available
  • Local helm repository where the SCP helm charts are available
  • Service FQDN of SCP-Worker must be discoverable from outside of the cluster (i.e. publicly exposed so that ingress messages to SCP can come from outside of Kubernetes).
  • Helm must have access to create ClusterRole and ClusterRoleBinding resources.

Note:

All the kubectl and helm related commands used in this guide need to be executed on some machine depending on the infrastructure/deployment. It may be some client machine.

Client machine requirements

There are some requirements for the laptop/desktop where the deployment commands needs to be executed:
  • It should have network access to the helm repository and docker image repository.
  • Helm repository must be configured on the client.
  • It should have network access to the Kubernetes cluster.
  • It should have necessary environment settings to run the kubectl commands. The environment should have privileges to create namespace in the Kubernetes cluster.
  • It should have helm client installed with the push plugin. The environment should be configured so that the helm install command deploys the software in the Kubernetes cluster.