From f3e70a6c6ee38962347a49c48d7651b143d49ca1 Mon Sep 17 00:00:00 2001 From: oyelakin mercy Date: Nov 08 2020 10:53:05 +0000 Subject: Update README.md --- diff --git a/README.md b/README.md index 0a501ef..5a32ba1 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,15 @@ # python-app-on-openshift-2 -Planning and preparations \ No newline at end of file +Write a Dockerfile and run oc new-app /path/to/Dockerfile, that’s it!! But if you want implement a full fledged modern CI/CD using Jenkins and openshift, you need to do little more than that. So let’s dive into it. +Deployment structure +In this deployment, our python program will be running inside a container. That program will be served through a Gunicorn server. We will reverse proxy this server from NGINX, running in the same container. The following diagram shows our application structure: +![](https://ruddra.com/content/images/2018/08/Screen-Shot-2018-08-12-at-3.32.20-PM_huca5c070c9e0c081e5eb9701caf4aaec1_55663_720x0_resize_q100_box.jpg) + The OpenShift Cluster will have three project spaces, CI/CD, DEV and STAGE. CI/CD will contain the Jenkins file, running pipelines inside it. DEV and STAGE projects will have applications running inside them. Next diagram will show what we intend to do in this CI/CD project: + +![](https://ruddra.com/content/images/2018/08/Screen-Shot-2018-08-12-at-3.28.36-PM_hu37b35a0b035cae16fad774ea54fc2b4f_62873_720x0_resize_q100_box.jpg) + +# Preparations +For implementing this CI/CD project, we need to prepare few things beforehand. Let us go through them one by one. + +## A ‘Python’ application +NB: if you have a python application, which runs through gunicorn and has tests runable through nosetests(or any xml test result exporter) then please skip this section. \ No newline at end of file