2 Planning Your Installation
The Oracle Communications Offline Mediation Controller cloud native deployment package includes Docker images and Helm charts to help you deploy and manage pods of product services in Kubernetes.
Overview of the Offline Mediation Controller Deployment Package
The Offline Mediation Controller cloud native deployment package includes the following:
-
Ready-to-use images and Helm charts to help you orchestrate containers in Kubernetes.
-
Sample Dockerfiles and scripts that you can use as a reference for building your own images.
You can use the images and Helm charts to help you deploy and manage pods of Offline Mediation Controller product services in Kubernetes. Communication between pods of services of Offline Mediation Controller products is preconfigured in the Helm charts.
About Offline Mediation Controller Pods and Images
Table 2-1 lists the pods and images for Offline Mediation Controller whose containers are created, and services are exposed through them.
Table 2-1 Offline Mediation Controller Pods and Images
| Pod | Replica Type | Image Name | Container Port |
|---|---|---|---|
|
ocomc-admin-server-0 |
Single |
oc-cn-ocomc-core:15.1.0.0.0 |
55105 |
|
nm-cc-0 |
Multiple |
oc-cn-ocomc-core:15.1.0.0.0 |
55109 |
|
ocomc-rsm-54c56bf4c4-7b8td |
Multiple |
oc-cn-ocomc-rsm:15.1.0.0.0 |
8080 |
|
mediation-ui-6dc7556f9-9cbgf |
Single |
oc-cn-ocomc-mediation-ui:15.1.0.0.0 |
8080 |
About Offline Mediation Controller Services
Table 2-2 lists the services for Offline Mediation Controller.
Table 2-2 Offline Mediation Controller Services
| Service | Service Type | Port | Notes |
|---|---|---|---|
|
nm-cc-0 |
ClusterIP |
55105 |
Client on same worker node. |
|
nm-cc-0-metrics |
ClusterIP |
9090 |
Client on same worker node. |
|
nm-epdc-0 |
ClusterIP |
55109 |
Client on same worker node. |
|
nm-epdc-0-metrics |
ClusterIP |
9090 |
Client on same worker node. |
|
ocomc-admin-server |
ClusterIP |
31200, 31201, 31202 |
Client on same worker node.
31200 is the default service port, 31201 is the firewall port and 31202 is the callback port. |
|
ocomc-rsm |
NodePort | 31250 | Client on Windows system. |
To connect to the Administration Server running in a Kubernetes cluster, you must install the Administration Client outside of the Kubernetes cluster and then connect it to the service and port of the Administration Server.
-
If the Administration Client is installed on the same node where the Administration Server pod is running, use a clusterIP service type with the Administration Server.
-
If the Administration Client is located remotely or is on a Windows system, use a NodePort service type with the Administration Server.
For more information about connecting the Administration Client, see "Connecting Your Administration Client".