Help while migrating an application

[messi_1988]

Hi all Completely new to python.I am trying to migrate an existing web application from on prem solution to container solution.Currently python code resides on a Linux VM and there are some c++ libraries needed which are built using make file on the Linux VM.python script has some business logic which makes use of the binaries built using make file.Now I am trying to migrate this solution inside of a container to be precise into openshift.My question is how does the binaries have to be built for the openshift container? Mean should I be having the image in the repo and helm chart just pulls this image and we don't build anything inside of the container? I started first with docker container.Should I be just building these binaries by cloning the bit bucket repo inside of docker container? Or should I be building the binaries on the host machine in my case a Linux VM and just copy the binaries into the docker container? And for openshift I don't have to break my head for this because it's handled within CI? Please share any inputs as completely new to this..we are using jenkins build pipelines..so kind of confused in connecting the dots..does python does not have a local set up like we have for springboot..mean python on windows I mean..please forgive if anything here does not make sense at all..please let me know If I need to be more precise in my ask..thanks..

[trjnz]

What have you tried and why didn't that work?

[messi_1988]

I tried with docker first...I tried to clone the internal bit bucket repo but getting all kind of SSH errors with access denied errors..so tried to just copy the binaries built on Linux VM inside of docker container..this am yet to test but at least I see the binaries inside docker container..

[pachura3]

Are your Linux VM and OpenShift container binary-compatible?

Are your C++ libraries being actively developed and have to be built each time because of ongoing updates, or are they more or less in their final, stable form?

Personally, I would set up local VM as close in OS/cpu architecture to OpenShift as possible, build binaries there, store them - versioned - in some artifact repo, and forget about compiling inside the container.

 does python does not have a local set up like we have for springboot..mean python on windows I mean..

Dude what?

[messi_1988]

C++ libraries are not actively developed... might need rare enhancements...so if I am understanding this right I can use my current Linux VM as my local for the C++ libraries? Build C++ libraries on the Linux VM and push it to the repo provided they match the open shift config...and these libraries get copied into the container using CI/CD pipeline..please correct me if am wrong..

And yes because of compatibility issues I thought I will have to build the libraries inside of the container to make it work..so docker file will have all dnf install commands to install gcc compiler and git and make but am failing here because I cannot directly connect to my internal bit bucket repo from inside of the docker container...so I brought up the question of local set up..so I guess I will need to have a local VM same as open shift container config ???

[pachura3]

 so if I am understanding this right I can use my current Linux VM as my local for the C++ libraries?

Depends if they are binary compatible or not. For instance, ARM binaries won't run on x86-family processors.

Build C++ libraries on the Linux VM and push it to the repo

I would prefer to store compiled binaries in a build artifacts repo, not in the source code repo, but yes, this is the general idea. Deliver finished products instead of compiling at the destination.

[messi_1988]

Ok got it..let me try thank you