Introduction

Acme Air is a full-fledged sample application for a fictitious airline called Acme Air which handles flight bookings with thousands of entries in its database. The implementation can support running on a variety of runtime platforms including virtual machines (VMs), Red Hat® OpenShift®, Docker containers, IBM Cloud®, and other Kubernetes environments. This tutorial shows you how to deploy the application on Red Hat OpenShift Container Platform on IBM Power Systems™ and to build your own images and perform updates on a running deployment.

The project consists of five components as shown in Figure 1. The front-end and deployment scripts are in the Main Service project.

Figure 1. Major components of Acme Air

Prerequisites

You need to make sure that the following prerequisites are fulfilled before deploying the sample Acme Air application.

A running OpenShift Container Platform 4.x cluster must be set up on an IBM Power Systems server
A Re Hat Quay.io account
Note: Quay.io is a container registry that contains the images for the Acme Air application.

Estimated time

The approximate time to deploy the sample Acme Air application and make updates to the images is around 30 minutes.

Deploy the application

Perform the following steps to deploy the application on OpenShift on an IBM Power Systems server.

Clone the https://github.com/ocp-power-demos/acmeair-mainservice-java repository and run the deployToOpenshift.sh script. The script does not require any input parameters.

The GitHub repositories for acme air in the ocp-power-demos organization are a fork of https://github.com/blueperf
```
git clone https://github.com/ocp-power-demos/acmeair-mainservice-java
cd acmeair-mainservice-java
./scripts/deployToOpenshift.sh
```
After successful completion, the output as shown in Figure 2 is displayed.

Figure 2. The namespace and URL information are provided at the end of the deployment

Run the following command to check the status of the pods. Notice that the pods are in the Running state.

$ oc get pods

NAME                                      READY   STATUS    RESTARTS   AGE
acmeair-authservice-58459f88c9-bdmt6      1/1     Running   0          2m50s
acmeair-booking-db-66d696dfd4-5lw7k       1/1     Running   0          2m50s
acmeair-bookingservice-7fdd8789c4-6h28l   1/1     Running   0          2m50s
acmeair-customer-db-6f4d998ffb-qfb9w      1/1     Running   0          2m50s
acmeair-customerservice-fffd899d5-27jb7   1/1     Running   0          2m50s
acmeair-flight-db-54684fb648-sdvsl        1/1     Running   0          2m50s
acmeair-flightservice-5566cc7d79-vnqgx    1/1     Running   0          2m50s
acmeair-mainservice-7f846794d5-5nmk4      1/1     Running   0          2m50s

To access the application, open the URL provided in the output of the script in a browser. Click the Configure the Acme Air environment link to load the database and start using the application.

Figure 3. Acme Air homepage for Version 1.0

Build your own images for Acme Air

Each repository for Acme Air is present in https://github.com/ocp-power-demos organization. You can make updates to the application across the five components and can deploy seamlessly without uninstalling the application.

Code updates and image creation

To demonstrate, we will make a version change to the front end of the application dashboard. After an update is performed, the change will be reflected on the browser without having to uninstall the application.

Perform a rolling update

Each deployment for Acme Air has a rolling update strategy. You may update fields for RollingUpdate during deployment with the required values.

StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge

Run the following command to perform the rolling update:

$ oc set image deployments/acmeair-mainservice acmeair-mainservice-java=quay.io/<quay.io account>/acmeair-mainservice-java:1.1 --record

deployment.apps/acmeair-mainservice image updated

Track the status of the rolling update.

$ oc rollout status deployment acmeair-mainservice

deployment "acmeair-mainservice" successfully rolled out

Open the Acme Air URL provided in Figure 2 in a browser. Note that the version has changed to 1.1.

Figure 16. Acme Air home page with the updated version 1.1

Notice that a new pod for mainservice is created for the newly updated deployment. The new image will also be reflected in the deployment.

$ oc get pods

NAME                                      READY   STATUS    RESTARTS   AGE
acmeair-authservice-58459f88c9-qdxjd      1/1     Running   0          18h
acmeair-booking-db-66d696dfd4-ngb4x       1/1     Running   0          18h
acmeair-bookingservice-7fdd8789c4-wh52r   1/1     Running   0          18h
acmeair-customer-db-6f4d998ffb-2grwv      1/1     Running   0          18h
acmeair-customerservice-fffd899d5-s95dj   1/1     Running   0          18h
acmeair-flight-db-54684fb648-mn6zk        1/1     Running   0          18h
acmeair-flightservice-5566cc7d79-gjnrv    1/1     Running   0          18h
acmeair-mainservice-657594bdb4-hgtgf      1/1     Running   0          64m

Summary

You can perform similar steps to build images for all the five projects as required. Making updates and deploying this sample application can help you to discover and understand the different features of OpenShift on IBM Power Systems servers. You can also perform performance benchmark tests, change the update strategy, and add in your own set of features to the application.

Links to all five Acme Air projects

Deploying Acme Air microservices application on Red Hat OpenShift Container Platform

Deploying Acme Air microservices application on Red Hat OpenShift Container Platform