DEVOPs days at DeepTech

DevOps ROLEs

There are many roles that a developer does those are essential for a project's rapid development, testing, deployment, and maintenance. And all these operations need to be streamlined so that testing can be done after developing a feature. After a successful tests including the regression tests, the code changes for the feature need to go to mainline of the project's GIT repository. These streamlined operations are usually called DevOps Pipelines. These roles are typically available in the Software Industry. Each of the below mentioned skill-sets are essential tools for- being a good Software Engineer.

DevOps Architect:

Decides how to use available tools in the Cloud to set up the CI/CD pipelines.

Makes pipelines for DevOps processes

And facilitates automation so that a lot can be achieved without intervention.

Cloud Architect:

Makes decisions in designing the cloud computing for the application.

Uses cloud tools to facilitate the DevOps within the team

for example in the context of the Azure: designing Azure DevOps Pipelines.

Release Manager:

Engineering releases and Master builds

Manages the Software release cycles.

Maintains the GIT mainline and resolves any issues with respect to the master branch.

SRE {Site Reliability Engineering}:

The product should be stable enough to use. The site should not break down when a wrong input is given. If the site is down, the downtime should be very less and it must be operational quickly. The SREs should know the operational best practices for the site. The site should not be slow.

DevOps Engineer:

Works along with the DevOps Architect to carry out the automation scripts, set up DevOps pipelines using Azure DevOps, GIT, Jenkins or CircleCI and makes the system stable.

Build and Release Engineer:

Manages the releases like "Engineering Builds" for smoke-testing just built features and makes arrangement for the "Release Builds" after the changes have gone through the "regression testing". They grow to be release managers.

Agile Scrum Master:

The Scrum Team is managed by the Scrum master. He should take the views of the members.He should conduct the Sprint Planning, and check the progress as decided by the team and should also conduct the Sprint Retrospectives at the end of the sprint. He should use Rally, Version1 or Azure Board or any other Agile tool to overview the DevOps implementation of the project.

Our Training Offerings

We provide training for all the below topics round the year. There are 12 important topics here and we charge only 3000.00 INR per topic per month. We typically cover one of these tools per month in 4 Saturdays. And Classes happen in the hybrid mode: mostly offline and online for some.

Here is a link to Pay for the same.

GIT: Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

No modern software project can work happily without a git repository. A good hand in git is the reflection of a great software engineer. Until you have mastered GIT, you cannot be called a great Software Guru. Because, git is so intricately associated with source code changes and its management, it is impossible to be better in one and be worse in another.

Git is our favourite way of dealing with the Software Changes, or even any textual. We are here leaving you with a few important and must have CHEAT-SHEETS for GIT.

GitHub is a publicly available git server used as Remote Origin, i.e it is used for pushing changes and for safekeeping those.

PRO-GIT.pdf : For the complete documentation on Git.

Atlassian-GIT-Cheat-Sheet and GIT-HUB GIT CHEAT-SHEET .

Gitlab is an alternative of GitHub.

JENKINS :

The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project.

We will focus on:

Building Jenkins Pipelines

Managing Jenkins

Securing Jenkins

DOCKER : Docker is a software platform that allows you to build, test, and deploy applications quickly. Docker packages software into standardized units called containers that have everything the software needs to run including libraries, system tools, code, and runtime. Using Docker, you can quickly deploy and scale applications into any environment and know your code will run.

We will focus on creating the container instances.

Running containerized Apps with Azure Container Instances

Deploy an image from Azure Container Registry