IBM - 在 OpenShift 平台上部署应用

Experiment Overview
Experiment Manual

Experiment Name: 在 OpenShift 平台上部署应用 of OpenShift on z/VM

Experiment Content:

Experiment Resources:

在 OpenShift 平台上部署应用 of OpenShift on z/VM

The following content is displayed on the same screen for your experiment so that you can make any necessary reference in experiment. Start your experiment now!

Product overview and registry
OpenShift is a containerization software solution developed by Red Hat and it is a Platform as a Service (PaaS) based on enterprise level Kubernetes management. The latest version is OpenShift 4. In addition to traditional X86 servers, it also supports some mainstream cloud platforms like Azure and AWS, and at the same time, supports the IBM LinuxONE platform. OpenShift supports application deployment through various methods, such as the use of S2I through Operators or Git, and direct use of the mirror of Image Registry.

Enter cscdemo(XX) in Username and demo123 in Password, and click Log in to enter the graphic interface of OpenShift
Check the project and deploy the Git server
On the navigation bar on the left, select Projects, then you can see one project (PR) cscdemoXX on the list on the right. Click cscdemoXX project, then you can view the Overview of the project. Click Workloads, then you can check the applications deployed in the project. Currently, it is empty.

Click the Administrator pull-down menu at the top of the navigation on the left and switch to the Developer view (Note: In case of any Restricted Access error, please change “Project: default” pull-down menu above into “Project: cscdemoXX”);
Choose From Catalog from the deployment modes on the right;
Select Git Server (Ephemeral)from the deployable projects;
Click Instantiate Template to prepare for the deployment;
Fill in Application Hostname with git-XX.apps.zvm-ocp.example.com, and confirm the correctness before clicking Create to start the deployment;
By clicking Events in the navigation bar on the left, you can view important events during the deployment process.

Click Developer pull-down menu at the top of the navigation bar on the left and Switch to the Administrator view;
After clicking Projects, click cscdemoXX on the right;
Click Workloads to open the tab;
Click the DC projects listed under git-server-example, then you can see the details of the Git server application just deployed;
Click Resources tab to confirm the state of P resource in the Pods group. The Running state indicates a deployment success.
At the bottom of Resources, you can see the group information of Routes, where Location is Application Hostname input when we just deployed;
click the link to open the page, if you see a page indicating 403 Forbidden, it means it operates properly.
Deploy NodeJS MongoDB applications
Background story: The developers have finished one of the NodeJS applications in the project and submitted it to our git server. Now they need to deploy it to an OpenShift environment for testing. The location of the application on the git server is /git/nodejs.git.

Click the Administrator pull-down menu at the top of the navigation bar on the left to switch to the Developer view;
Click +Add menu item and select From Catalog from the deployment modes on the right;
Select Template filter conditions under TYPE and just display the template projects;
Select Node.js + MongoDB (Ephemeral) from the deployable projects;
Click Instantiate Template to prepare for deployment;
Fill in Git Repository URL with http://git-(Project Name).apps.zvm-ocp.example.com/git/nodejs.git
After it is confirmed correct, click Create to start deployment.

Click the Developer pull-down menu at the top of the navigation bar on the left and switch to the Administrator view;
Click Projects, then click cscdemoXX on the right for a view;
Click Workloads to open the tab;
Click (DC) nodejs-mongodb-example project to see the information of the Node.JS application just deployed;
Click Resources tab, then you can see the running state of Build tasks under the Builds group,
Click the View Logs behind the Build group tasks, you can see the running log of Build tasks.
A few minutes later, Push successful will appear on the bottom line, indicating success;
Return to the Resources tab page to confirm that the P resources are in Running state;
Then at the bottom of the resources, you can see information of the Routes group. Click the link given in Location. When “Welcome to your Node.js....” appears at the top of the confirmation page, it means the deployment is a success
Deploy Java MySQL applications
Background story: The developers have finished one of the Java applications in the project and submitted it to our git server. Now they need to deploy it to an OpenShift environment for testing. The location of the application on the git server is /git/java.git.

Click the Administrator pull-down menu at the top of the navigation bar on the left to switch to the Developer view;
Click+Add menu item and select From Catalog from the deployment modes on the right;
Select Template filter conditions under TYPE and just display the template projects,
Select OpenJDK + MySQL (Ephemeral)from the deployable projects,
Click Instantiate Template to prepare for deployment,
Fill in Git Repository URLwith http://git-(Project Name).apps.zvm-ocp.example.com/git/java.git empty the content in Context Directory,
and after it is confirmed correct, click Create to start deployment.

Click the Developer pull-down menu at the top of the navigation bar on the left to switch to the Developer view;
Click Projects and then click cscdemoXX on the right for a view;
Click Workloads to open the tab;
Click (DC) openjdk-app-mysql project, then you can see the information of the Java application just deployed.
By clicking Resources tab, you can see the running state of Build tasks under the Build group,
Click View Logs behind the Build tasks, you can check the running log of Build tasks.
A few minutes later, Push successful will appear on the bottom line, indicating a success;
Return to the Resources tab page to confirm that the P resources in the Pods group is in Running state.
At the bottom of the resources, you can see the information of the Routes group. Click the link given in Location. If Welcome to your Node.js....” appears on the top of the page, it means the deployment is a success
Automatic deployment after the code change
Background story: Due to the rapid iteration of codes, in order to accelerate the development, it is hoped that after their submission, the new codes can be automatically deployed without manual intervention. In OpenShift, only Webhook method is needed to trigger this function. The following experiment demonstrates how to obtain the URL of Webhook and the automatic deployment.

First click Applcations->Terminal Emulator on the top right of the desktop to start the terminal window, and then run the following command to clone the java code base and confirm the cloning success.
ls
git clone http://git-(Project Name).apps.zvm-ocp.example.com/git/java.git
ls
cd java

Go back to the Administrator interface of OpenShift and select Build Configs item under Builds on the navigation bar on the left,
Click openjdk-app-mysql item on the page on the right,
Then at the bottom of the page, you can see Webhooks group.
Click Copy URL with Secret under Generic, and copy the URL of Webhook;

Return to the terminal window, create webhook files with vi, and paste the copied URL to a file before saving and exiting.
vi webhook
Then use vi to modify the original java file src/main/java/org/openshift/quickstarts/undertow/servlet/PhoneBookServlet.java file
vi src/main/java/org/openshift/quickstarts/undertow/servlet/PhoneBookServlet.java
change
name = "NONE";
in the 87th line into
name = "NULL";
upon the modification, run the following command to submit the change
git add .
git commit -m "Test auto build"
git push
If there are prompts for username and password, enter git as the username and demo as the password

Go back to the Administrator interface of OpenShift,
select cscdemoXX under Projects,
open Workloads tab,
after selecting (DC) openjdk-app-mysql,
open Resources tab to view task items under the Builds group and you will see a new Build task is in operation. After the operation, the projects in the Running State in the Pods group will be stopped and new projects will be regenerated. When the new projects enter the Running state, click the Location link in the Routes Group at the bottom, the page output has changed from Number for user 'NONE' is not found into
Number for user 'NULL' is not found