Hello Everyone
Today I am gonna share some amazing information that I received from the the live webinar on Industry Use Case by Mr.Rushil Sharma, Mr. Vijit Kuntal and Mr.Neeraj Bhatt organized by linuxWorld under the guide-lines of worldRecordHolder Mr.VIMAL DAGA and Mrs.PREETI DAGA.
Being a part of ARTH I got this opportunity to be a part of Industrial Use Case with Demonstration on Kubernetes.

What is CVS ?

CVS stands for Centralized Version Control System.
CVS is a server which act as a repository to store all the codes.
CVS stores each and every version of Code.
CVS is a 1990's and early 20’s technology. After the arrival of GIT in 2005 around 1600 modules were migrated to GIT.

Why CVS to GIT ?

The main issue with CVS was its built time. As compared to other technologies like GIT, CVS consumes around double built time.

CVS doesn’t work on repository or module level, it works on file system basis.
If in CVS we make a commit it is made directly to the remote server, not in your local machine hence working in a team you cannot test it as it will not be seen to everyone.

Creating Branches in GIT is easier than CVS or any other Centralized Version System.

Reconcile in CVS was very difficult but in GIT we can directly merge code from one branch to other.

CVS works on file level while GIT works on repository level which makes GIT easier to use.

How to convert from CVS to GIT ?

The most used method to convert from CVS to GIT is by using CVSIMPORT option provided by GIT itself. It was written in a way GIT can easily understand.
It uses a module cvsimport [option][option] to convert from CVS to GIT

Other mostly used module is Cvs2Git.
This module was made by someone from CVS itself.
It is one of the most powerful tool

The Use Cases :

The use cases that we studied were :

1. First Use Case was the one in which bank of Plutaws decided to go global for which they have to redesign their architecture.
   For that they had to redesign their architecture and convert their architecture from monolithic architecture to microservice based architecture, for which they uses Kubernetes Platform
2. Second Use Case was a security use case for OKD/Open Shift
   In this use case consumer wants to deploy an application in production environment with some conditions:
   a) His application must run on specific user id
   b) Should not use any linux privilege
   c) Application must not use PVC’s
   To perform this a customized SSC has to be created and applied to the application.

THANK YOU