1. Cloud Native Installation and Administration Guide
  2. Deploying into Oracle Cloud Infrastructure

12 Deploying into Oracle Cloud Infrastructure

Learn how to deploy Oracle Communications Offline Mediation Controller cloud native services into Oracle Cloud Infrastructure.

Topics in this document:

Deploying into Oracle Cloud Infrastructure

Oracle Cloud Infrastructure is a set of complementary cloud services that enable you to run a wide range of applications and services in a highly available hosted environment. It offers high-performance compute capabilities (as physical hardware instances) and storage capacity in a flexible overlay virtual network that is securely accessible from your on-premises network. Among many of its services, the Offline Mediation Controller cloud native deployment is tested in an Oracle Cloud Infrastructure environment using its database and container engine for Kubernetes services on a bare metal instance.

Deploying the Offline Mediation Controller cloud native services into Oracle Cloud Infrastructure involves these high-level steps:

Note:

These are the bare minimum tasks for deploying Offline Mediation Controller cloud native services in Oracle Cloud Infrastructure. Your steps may vary from the ones listed below.

  1. Sign up for Oracle Cloud Infrastructure.

  2. Create a Kubernetes cluster and deselect the Tiller (Helm) Enabled option. The version of Helm used by Oracle Cloud Infrastructure isn't compatible with the Offline Mediation Controller cloud native software requirements.

  3. Install and configure the Oracle Cloud Infrastructure Command Line Interface (CLI).

    CLI is a small footprint tool that you can use on its own or with the Console to complete OCI tasks. It's needed here to download the kubeconfig file.

  4. Install and configure kubectl on your system to perform operations on your cluster in Oracle Cloud Infrastructure.

  5. The kubeconfig file (by default named config and stored in the $HOME/.kube directory) provides the necessary details to access the cluster using kubectl and the Kubernetes Dashboard.

    Download kubeconfig to access your cluster on Oracle Cloud Infrastructure by entering this command: 

    oci ce cluster create-kubeconfig --cluster-id ClusterId --file $HOME/.kube/config --region RegionId

    where ClusterId is the Oracle Cloud Identifier (OCID) of the cluster, and RegionId is the region identifier such as us-phoenix-1 and us-ashburn-1.

  6. Set the $KUBECONFIG environment variable to the downloaded kubeconfig file by entering this command: 

    export KUBECONFIG=$HOME/.kube/config

  7. Verify access to your cluster. You can enter this command and then match the output Internal IP Addresses and External IP Addresses against the nodes in your cluster in the Oracle Cloud Infrastructure Console.

    kubectl get node -o wide

  8. Download and configure Helm in your local system. To install Tiller on your cluster in Oracle Cloud Infrastructure, enter this command:

    helm init

  9. If you are using a password-protected registry for Docker images, Kubernetes can't pull the images unless the authentication details are provided.

    There are many ways to enable Kubernetes to pull images from a password-protected Docker registry. For example, you could do this on each worker node:

    1. Log in to the Docker registry by entering this command:

      docker login -u UserName RepoHost:RepoPort

    2. Copy the config.json file where Docker has stored the authentication details to /var/lib/kubelet.

  10. Place the Offline Mediation Controller cloud native Helm chart on your system where you have downloaded and configured kubectl and Helm. Then, follow the instructions in "Installing the Offline Mediation Controller Cloud Native Deployment Package".