Mojaloop Deployment

The document is intended for an audience with a stable technical knowledge that would like to setup an environment for development, testing and contributing to the Mojaloop project.

Deployment and Setup

Mojaloop Deployment
- Deployment and Setup
  - 1. Pre-requisites
  - 2. Deployment Recommendations
  - 3. Kubernetes
    3.1. Kubernetes Ingress Controller
    3.2. Kubernetes Admin Interfaces
  - 4. Helm
    4.1. Helm configuration
  - 5. Mojaloop
    5.1. Mojaloop Helm Deployment
    5.2. Verifying Ingress Rules
    5.3. Testing Mojaloop
    5.4. Testing Mojaloop with Postman
  - 6. Overlay Services/3PPI
    6.1 Configuring a deployment for Third Party API support
    6.2 Validating and Testing the Third Party API
    6.2.1 Deploying the Simulators
    6.2.2 Provisioning the Environment
    6.2.3 Run the Third Party API Test Collection

1. Pre-requisites

Versions numbers below are hard requirements, not just recommendations (more recent versions are known not to work).

A list of the pre-requisite tool set required for the deployment of Mojaloop:

Kubernetes An open-source system for automating deployment, scaling, and management of containerized applications. Find out more about Kubernetes.
- Recommended Versions:
  Mojaloop Helm Chart release v14.1.x supports Kubernetes v1.20 - v1.24.
  Mojaloop Helm Chart release v14.0.x supports Kubernetes v1.20 - v1.21.
  Mojaloop Helm Chart release v13.x supports Kubernetes v1.13 - v1.21.
  Mojaloop Helm Chart release v12.x supports Kubernetes v1.13 - v1.20.
  Mojaloop Helm Chart release v11.x supports Kubernetes v1.13 - v1.17.
  Mojaloop Helm Chart release v10.x supports Kubernetes v1.13 - v1.15, it will fail on Kubernetes v1.16+ onwards due deprecated APIs (ref: Helm Issue #219).
- kubectl - Kubernetes CLI for Kubernetes Management is required. Find out more about kubectl:
  - Install-kubectl,
- microk8s - MicroK8s installs a barebones upstream Kubernetes for a single node deployment generally used for local development. We recommend this installation on Linux (ubuntu) OS. Find out more about microk8s and microk8s documents:
  - Install-microk8s,
- kubectx - Not required but useful. Find out more about kubectx,
- kubetail - Not required but useful. Bash script that enables you to aggregate (tail/follow) logs from multiple pods into one stream. Find out more about kubetail,
Docker Provides containerized environment to host the application. Find out more about Docker,
Helm A package manager for Kubernetes. Find out more about Helm, Recommended Versions: Helm v3.x (ref: Design Auth Issue #52).
Postman Postman is a Google Chrome application for the interacting with HTTP API's. It presents you with a friendly GUI for the construction requests and reading responces. https://www.getpostman.com/apps. Find out more about Postman.

For local guides on how to setup the pre-requisites on your laptop or desktop, refer to the appropriate link document below;

2. Deployment Recommendations

This provides environment resource recommendations with a view of the infrastructure architecture.

Resources Requirements:

Control Plane (i.e. Master Node)
https://kubernetes.io/docs/setup/cluster-large/#size-of-master-and-master-components
- 3x Master Nodes for future node scaling and HA (High Availability)
ETCd Plane:
https://etcd.io/docs/v3.3.12/op-guide/hardware
- 3x ETCd nodes for HA (High Availability)
Compute Plane (i.e. Worker Node):
TBC once load testing has been concluded. However the current general recommended size:
- 3x Worker nodes, each being:
  - 4x vCPUs, 16GB of RAM, and 40gb storage
Note that this would also depend on your underlying infrastructure, and it does NOT include requirements for persistent volumes/storage.

3. Kubernetes

This section will guide the reader through the deployment process to setup Kubernetes.

If you are new to Kubernetes it is strongly recommended to familiarize yourself with Kubernetes. Kubernetes Concepts is a good place to start and will provide an overview.

The following are Kubernetes concepts used within the project. An understanding of these concepts is imperative before attempting the deployment;

Deployment
Pod
ReplicaSets
Service
Ingress
StatefulSet
DaemonSet
Ingress Controller
ConfigMap
Secret

Insure kubectl is installed. A complete set of installation instruction are available here.

3.1. Kubernetes Ingress Controller

Install your preferred Ingress Controller for load-balancing and external access.

Refer to the following documentation to install the Nginx-Ingress Controller used for this guide: https://kubernetes.github.io/ingress-nginx/deploy/#using-helm. It is recommended that you install v0.47.0 of the Nginx-Ingress Controller due to recent changes being made to support Kubernetes v1.22.

If you are using helm, this can be done as follows:

helm install ingress-nginx ingress-nginx --version="3.33.0" --repo https://kubernetes.github.io/ingress-nginx

NOTE: If you are installing Mojaloop v12.x with an Nginx-Ingress controller version newer than v0.22.0, ensure you create a custom Mojaloop values config with the following changes prior to install:
## **LOOK FOR THIS LINE IN mojaloop/values.yaml CONFIG FILE**
mojaloop-simulator:
  ingress:
   ## nginx ingress controller >= v0.22.0 <-- **COMMENT THE FOLLOWING THREE LINES BELOW:**
   # annotations: <-- COMMENTED
   #  nginx.ingress.kubernetes.io/rewrite-target: '/$2' <-- COMMENTED
   # ingressPathRewriteRegex: (/|$)(.*) <-- COMMENTED

   ## nginx ingress controller < v0.22.0 <-- **UNCOMMENT THE FOLLOWING THREE LINES BELOW:**
   annotations:
     nginx.ingress.kubernetes.io/rewrite-target: '/'
   ingressPathRewriteRegex: "/"
This is NOT necessary if you are installing Mojaloop v13.x or newer.

List of alternative Ingress Controllers: https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/.

3.2. Kubernetes Admin Interfaces

Kubernetes Dashboards
The official Kubernetes Web UI Admin interface.
Visit the following link for installation instructions (not needed if MicroK8s is installed): Web UI (Dashboard) Installation Instructions.
IMPORTANT: Ensure (not needed if MicroK8s is installed) you configure RBAC roles and create an associated service account, refer to the following example on how to create a sample user for testing purposes only: Creating sample user.
If you have installed MicroK8s, enable the MicroK8s dashboard:
```
microk8s.enable dashboard
```
Refer to the following link for more information: Add-on: dashboard.
Remember to prefix all kubectl commands with microk8s if you opted not to create an alias.
k8sLens
A local desktop GUI based kubectl alternative which is easy to install and setup.
Visit the following link for more information: https://k8slens.dev/.

4. Helm

Please review Mojaloop Helm Chart to understand the relationships between the deployed Mojaloop helm charts.

Refer to the official documentation on how to install the latest version of Helm: https://helm.sh/docs/intro/install/.

Refer to the following document if are using Helm v2: Deployment with (Deprecated) Helm v2.

Refer to the Helm v2 to v3 Migration Guide if you wish to migrate an existing Helm v2 deployment to v3.

4.1. Helm configuration

Add mojaloop repo to your Helm config:
```
helm repo add mojaloop   https://mojaloop.io/helm/repo/
```
If the repo already exists, substitute 'add' with 'apply' in the above command.
Update helm repositories:
```
helm repo update
```

5. Mojaloop

5.1. Mojaloop Helm Deployment

Install Mojaloop:

1.1. Installing latest version:

helm --namespace demo install moja mojaloop/mojaloop --create-namespace

Or if you require a customized configuration:

helm --namespace demo install moja mojaloop/mojaloop --create-namespace -f {custom-values.yaml}

Note: Download and customize the values.yaml. Also ensure that you are using the value.yaml from the correct version which can be found via Helm Releases. You can confirm the installed version by using the following command: helm --namespace demo list. Under the CHART column, you should see something similar to 'mojaloop-{version}' with {version} being the deployed version.

 $ helm -n demo list
 NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART
 moja            demo            1               2021-06-11 15:06:04.533094 +0200 SAST   deployed        mojaloop-{version}

Note: The --create-namespace flag is only necessary if the demo namespace does not exist. You can alternatively create it using the following command: kubectl create namespace demo.

1.2. Version specific installation:

helm --namespace demo install moja mojaloop/mojaloop --create-namespace --version {version}

1.3. List of Mojaloop releases:

 $ helm search repo mojaloop/mojaloop -l
 NAME                            CHART VERSION   APP VERSION                 DESCRIPTION                                      
 mojaloop/mojaloop               {version}       {list of app-versions}      Mojaloop Helm chart for Kubernetes
 ...                             ...             ...                         ...

5.2. Verifying Ingress Rules

Update your /etc/hosts for local deployment:

Note: This is only applicable for local deployments, and is not needed if custom DNS or ingress rules are configured in a customized values.yaml.

vi /etc/hosts

Windows the file can be updated in notepad - need to open with Administrative privileges. File location C:\Windows\System32\drivers\etc\hosts.

Include the following lines (or alternatively combine them) to the host config.

The below required config is applicable to Helm release >= versions 6.2.2 for Mojaloop API Services;

 # Mojaloop Demo
 127.0.0.1   ml-api-adapter.local central-ledger.local account-lookup-service.local account-lookup-service-admin.local quoting-service.local central-settlement-service.local transaction-request-service.local central-settlement.local bulk-api-adapter.local moja-simulator.local sim-payerfsp.local sim-payeefsp.local sim-testfsp1.local sim-testfsp2.local sim-testfsp3.local sim-testfsp4.local mojaloop-simulators.local finance-portal.local operator-settlement.local settlement-management.local testing-toolkit.local testing-toolkit-specapi.local

Test system health in your browser after installation. This will only work if you have an active helm chart deployment running.
Note: The examples below are only applicable to a local deployment. The entries should match the DNS values or ingress rules as configured in the values.yaml or otherwise matching any custom ingress rules configured.
ml-api-adapter health test: http://ml-api-adapter.local/health
central-ledger health test: http://central-ledger.local/health

5.3. Testing Mojaloop

The Mojaloop Testing Toolkit (TTK) is used for testing deployments, and has been integrated into Helm utilizing its CLI to easily test any Mojaloop deployment.

Validating Mojaloop using Helm

helm -n demo test moja

Or with logs printed to console

helm -n demo test moja --logs

This will automatically execute the following test cases using the Mojaloop Testing Toolkit (TTK) CLI:

TTK Hub setup and Simulator Provisioning Collection.

Use the following command to view the provisioning Collection logs:

kubectl -n demo logs pod/moja-ml-ttk-test-setup

TTK Golden Path Test Collection.

Use the following command to view the Golden Path Collection logs:

 kubectl -n demo logs pod/moja-ml-ttk-test-validation

Example of the finally summary being displayed from the Golden Path test collection log output:

 Test Suite:GP Tests
 Environment:Development
 ┌───────────────────────────────────────────────────┐
 │                      SUMMARY                      │
 ├───────────────────┬───────────────────────────────┤
 │ Total assertions  │ 1557                          │
 ├───────────────────┼───────────────────────────────┤
 │ Passed assertions │ 1557                          │
 ├───────────────────┼───────────────────────────────┤
 │ Failed assertions │ 0                             │
 ├───────────────────┼───────────────────────────────┤
 │ Total requests    │ 297                           │
 ├───────────────────┼───────────────────────────────┤
 │ Total test cases  │ 61                            │
 ├───────────────────┼───────────────────────────────┤
 │ Passed percentage │ 100.00%                       │
 ├───────────────────┼───────────────────────────────┤
 │ Started time      │ Fri, 11 Jun 2021 15:45:53 GMT │
 ├───────────────────┼───────────────────────────────┤
 │ Completed time    │ Fri, 11 Jun 2021 15:47:25 GMT │
 ├───────────────────┼───────────────────────────────┤
 │ Runtime duration  │ 91934 ms                      │
 └───────────────────┴───────────────────────────────┘
 TTK-Assertion-Report-multi-2021-06-11T15:47:25.656Z.html was generated

Accessing the Mojaloop Testing Toolkit UI
Open the following link in a browser: http://testing-toolkit.local.
One is able to manually load and execute the Testing Toolkit Collections using the UI which allows one to visually inspect the requests, responses and assertions in more detail. This is a great way to learn more about Mojaloop.
Refer to the Mojaloop Testing Toolkit Documentation for more information and guides.

5.4. Testing Mojaloop with Postman

Postman can be used as an alternative to the Mojaloop Testing Toolkit. Refer to the Automated Testing Guide for more information.

The available Mojaloop Postman Collections are similar to the Mojaloop Testing Toolkit's Test Cases's as follows:

Postman Collection

Mojaloop Testing Toolkit

Description

and

Hub Setup and Simulator Provisioning

Golden Path Tests

Pre-requisites:

The following postman environment file should be imported or customized as required when running the above listed Postman collections: Mojaloop-Local-MojaSims.postman_environment.json.
Ensure you download the latest patch release version from the Mojaloop Postman Git Repository Releases. For example if you install Mojaloop v12.0.X, ensure that you have the latest Postman collection patch version v12.0.Y.

6. Overlay Services/3PPI

As of R.C. v13.1.0 of Mojaloop, Third Party API is supported and will be published with the official release of Mojaloop v13.1.0. which allows Third Party Payment Initiators (3PPIs) the ability to request an account link from a DFSP and initiate payments on behalf of users.

Learn more about 3PPI:
Mojaloop's Third Party API
3rd Party Use Cases:
3rd Party Account Linking
3rd Party Initiated Payments

6.1 Configuring a deployment for Third Party API support

Third Party API support is off by default on the Mojaloop deployment. You can enable it by editing your values.yaml file with the following settings:

...
account-lookup-service:
  account-lookup-service:
    config:
      featureEnableExtendedPartyIdType: true # allows the ALS to support newer THIRD_PARTY_LINK PartyIdType

  account-lookup-service-admin:
    config:
      featureEnableExtendedPartyIdType: true # allows the ALS to support newer THIRD_PARTY_LINK PartyIdType

...

thirdparty:
  enabled: true
...

In addition, the Third Party API has a number of dependencies that must be deployed manually for the thirdparty services to run. mojaloop/helm/thirdparty contains details of these dependencies, and also provides example k8s config files that install these dependencies for you.

# install redis and mysql for the auth-service
kubectl apply --namespace demo -f https://raw.githubusercontent.com/mojaloop/helm/master/thirdparty/chart-auth-svc/example_dependencies.yaml
# install mysql for the consent oracle
kubectl apply --namespace demo -f https://raw.githubusercontent.com/mojaloop/helm/master/thirdparty/chart-consent-oracle/example_dependencies.yaml

# apply the above changes to your values.yaml file, and update your mojaloop installation to deploy thirdparty services:
helm upgrade --install --namespace demo moja mojaloop/mojaloop -f values.yaml

Once the helm upgrade has completed, you can verify that the third party services are up and running:

kubectl get po | grep tp-api 
# tp-api-svc-b9bf78564-4g59d                                        1/1     Running   0          7m17s

kubectl get po | grep auth-svc
# auth-svc-b75c954d4-9vq7w                                          1/1     Running   0          8m5s

kubectl get po | grep consent-oracle
# consent-oracle-849cb69769-vq4rk                                   1/1     Running   0          8m31s


# and also make sure the ingress is exposed correctly
curl -H "Host: tp-api-svc.local" <ingress ip address>/health
# {"status":"OK","uptime":3545.77290063,"startTime":"2021-11-04T05:41:32.861Z","versionNumber":"11.21.0","services":[]}

curl -H "Host: auth-service.local" <ingress ip address>/health

# {"status":"OK","uptime":3682.48869561,"startTime":"2021-11-04T05:43:19.056Z","versionNumber":"11.10.1","services":[]}

curl -H "Host: consent-oracle.local" <ingress ip address>/health
# {"status":"OK","uptime":3721.520096665,"startTime":"2021-11-04T05:43:48.382Z","versionNumber":"0.0.8","services":[]}

You can also add the following entries to your /etc/hosts file to make it easy to talk to the thirdparty services
<ingress ip address> tp-api-svc.local auth-service.local consent-oracle.local

6.2 Validating and Testing the Third Party API

Once you have deployed the Third Party services, you need to deploy some simulators that are capable of simulating the Third Party scenarios.

6.2.1 Deploying the Simulators

Once again, you can do this by modifying your values.yaml file, this time under the mojaloop-simulator entry:

...

mojaloop-simulator:
  simulators:
  ...
    pisp:
      config:
        thirdpartysdk:
          enabled: true
    dfspa:
      config:
        thirdpartysdk:
          enabled: true
    dfspb: {}
...

The above entry will create 3 new sets of mojaloop simulators:

pisp - a PISP
dfspa - a DFSP that supports the Third Party API
dfspb - a normal DFSP simulator that doesn't support the Third Party API, but can receive payments

6.2.2 Provisioning the Environment

Once the above simulators have been deployed and are up and running, it's time to configure the Mojaloop Hub and simulators so we can test the Third Party API.

Use the Third Party Provisioning Collection from the mojaloop/testing-toolkit-test cases to provision the Third Party environment and the simulators you set up in the last step.

6.2.3 Run the Third Party API Test Collection

Once the provisioning steps are completed, you can run the Third Party Test Collection to test that the Third Party services are deployed and configured correctly.

PreviousPragmatic REST NextTroubleshooting

Last updated 2 years ago

Was this helpful?